Error although Backup Completed Successfully

@Jeremy ,

There are many critical system state components which might have got updated in the registry and in order for them to take effect a reboot of server is required. 

You can review any of these changes by exploring the following registry entry: HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations If there are items in that key, then I would recommend a reboot.

Best Regards,

Sebastien

Hi Sebastien,

Thanks for your mail! Maybe my post wasn’t that clear. I know we need to reboot the client 🙂. What I actually wanted to know is why this Backup Job get marked “Completed” so with a green mark, instead of marked “Completed with one or more errors” and with an orange mark.

At this point, we don’t know if there are other jobs with the same “error” because they are all marked completed. And if we need to go through all the Backup Job details it would take ages if you have 1000s of clients.

I’m not sure if this “expected behaviour” and “working as designed”.

Regards,

Jeremy

That’s a good question, @Jeremy .

I’ll inquire a bit internally.

This sounds just like the default behaviour with VM backups where quiescing can't be performed but job completes successful. This behavior can be altered with an additional setting so it completes with warning or error.

@Mike Struening when you ask internally, can you ask if there is an additional setting for this FS situation as well?

Jeremy, please open a ticket and ask to submit a CMR for better visibility when this scenario occurs. Concern is valid, we can’t have it result in an error code and mark it completed, knowing this is a potential issue for restoring data.

@Aplynx is my internal resource 🤣  Agreed with him on creating a support case, @Jeremy to ask for a CMR.

Hi all,

Thanks for your suggestions and solutions/workarounds. We’ll have a CMR opened and in the meantime have a look at the Job Management options as Sebastien suggested.

Thanks!

Jeremy