Skip to main content
Solved

Any way to avoid 17:11 errors?

  • October 15, 2021
  • 8 replies
  • 494 views

downhill
Novice
Forum|alt.badge.img+9

Hi, I’m wondering if there is any reg key that can be set for the subclients, in my case a Cloud Apps virtual client where the content rarely changes, so almost every day we get multiple 17:11 errors. Isn’t there some way to set a key that says “I don’t care if you didn’t find any content in the scan?”

thanks

Best answer by Mike Struening

Sharing solution:

17 :11 is not supposed to be major event

Solution:

DEV created HF507 to address it. It is planned in MR37

8 replies

Mike Struening
Vaulter
Forum|alt.badge.img+22

Hey @downhill , hope all is well.

I created a new thread for this.  Let me see if there’s anything we can do around that concern.


Scott Moseman
Vaulter
Forum|alt.badge.img+22

What agent type are we talking about?
 


For File System backups, I don’t believe error 17:11 is the result of unchanged data.
If a subclient cannot find content, it either doesn’t exist or perhaps has access issues.

Thanks,
Scott
 


Forum|alt.badge.img+1

But for Cloud Apps backups, which the OP specified, that’s exactly what it means: unchanged data. And I agree, it’s annoying and could camouflage more serious situations such as disappearance of previous data.


Mike Struening
Vaulter
Forum|alt.badge.img+22

@downhill , can you create a support case for this so we can have this analyzed and escalated to dev for a change?  If nothing changed, you should get an Event and job description detail…..not an error message.

Once you get the case created, share the case number so I can follow it accordingly.


downhill
Novice
Forum|alt.badge.img+9
  • Author
  • Novice
  • December 8, 2021

hi, the resolution given to me, and apparently the only feasible way to do it, was to hide that specific event id. So, that’s what I did and sure enough, no more entries in the event report.

thanks


Mike Struening
Vaulter
Forum|alt.badge.img+22

I’m not really happy with that as an answer.  We should get a CMR into dev to get the root issue addressed.

Can you share the case number with me where they gave this advice?


Mike Struening
Vaulter
Forum|alt.badge.img+22

@downhill , confirming that the new case is 211208-638?


Mike Struening
Vaulter
Forum|alt.badge.img+22

Sharing solution:

17 :11 is not supposed to be major event

Solution:

DEV created HF507 to address it. It is planned in MR37