SureBackup DC Error since Update 4

[ASG]

Hi,

since Update 4 our SureBackup can't restore our DC. The DC is reboots just fine as it should but stays in recovery mode. Steps taken as KB1277 says works and SureBackup continues. However we didn't have the problem (and have to take manual actions) prior to installing Update 4.

Case #03431871

Any Idea?

[wishr]

Hi ASG,

This is not the expected behavior. Please keep working with our technical support on the case, we'll keep an eye on the request either.

Thank you

[ASG]

Hi,

As I've noticed before the DC is rebootet by Veeam during the "restore/SureBackup" timeframe - but it seems the script to disable safeboot is not run or not successfull. This behaviour changed from Update 3a to Update 4 and since then we have this error.

It's exact the same Problem as stated here (which is from 2014 but the same Problem):
vmware-vsphere-f24/windows-2012-r2-dc-f ... 23379.html

I even did the same steps stated in the other Thread and get nearly the same results: "I've tried extending the time to 10 minutes and that doesn't help. When I watch the console, it boots up into safe mode and then never leaves that state. It just sits there until 10 minutes passes and the lab fails. If I login to the console and manually run the commands that I think is supposed to happen automatically, and it reboots all is fine. But then the next time I run it again it fails unless I manually do this."

However: My machine is rebootet as I can see from the console! This is something that OP in the other thread didn't notice. But even after the reboot the machine is still in recovery mode.

However with Update3a everything worked fine - the Problem only started to appear with Update 4. As the fix in the above thread was a dll replacement inside the veeam application maybe this is a bug in Update4?

[wishr]

Hi ASG,

Thank you for your efforts!

I think It's too early to assume what's the root cause or even judging whether it's a U4 bug or not and if it is related to the "old case" you mentioned, but we'll be able to do so once have all the necessary information - please keep sharing it.

Regards,
Fedor

[foggy]

However with Update3a everything worked fine - the Problem only started to appear with Update 4. As the fix in the above thread was a dll replacement inside the veeam application maybe this is a bug in Update4?

The final fix in the above thread was a registry value, though it was disabled by default. If you neither have replaced the dll nor altered the registry value, this is not your case, but rather something new, specific to U4. Please continue investigating with support.

[ASG]

Everything about SureBackup is stock 9.5U4 - no fixes or anything else.

However the response times are a bit of a problem... it's taking quite some time to get a response and I'm not happy that I'm losing time again (and i fear it's another day) since the Support did ask me how I got the logfiles from the SureBackup Machine (after requesting the files)...

What I did notice upon reading the GuestHelper.log from the surebackup machine:

Code: Select all

27.02.2019 11:10:17   1428  WARN            UseGranularBcdRestore registry value is not set. Using default value: false
27.02.2019 11:10:17   1428                      Restoring Boot Configuration Data from backup.
27.02.2019 11:10:17   1428                          BCD backup file path: [C:\ProgramData\Veeam\Backup\bcd.bkp].
27.02.2019 11:10:17   1428                      Restoring Boot Configuration Data from backup.. Ok.
27.02.2019 11:10:17   1428                      Collecting the current value of the FRS BUR flag.
27.02.2019 11:10:17   1428  INFO                    Current value of the FRS BUR flag is [212].
27.02.2019 11:10:17   1428                      Collecting the current value of the FRS BUR flag.. Ok.
27.02.2019 11:10:17   1428                  Custom NTFRS detected.
27.02.2019 11:10:17   1428              Restoring components of the following reboot group: [EAdRestoreGrp].. Ok.
27.02.2019 11:10:17   1428  WARN    The machine reboot is required. All other restores will be performed after the system restart.
27.02.2019 11:10:17   1428              Initiating reboot of the local host.
27.02.2019 11:10:17   1428                      Enabling SE_SHUTDOWN privilege.
27.02.2019 11:10:17   1428                      Enabling SE_SHUTDOWN privilege.. Ok.
27.02.2019 11:10:17   1428              Initiating reboot of the local host.. Ok.

The Machine is rebooting after this, but maybe the bcd.bkp is holding the wrong value? The bcdorig.xml on the production machine contains <SafeBootOrigValue SafeBootValue="0"/> - however this is the setting that is not set on the surebackup machine.

[wishr]

Hi ASG,

This information could be useful for the support team, and while we appreciate your efforts sharing it here on the forums as well, I would really suggest sharing it with the support engineer either since the initial analysis is performed on the technical support end.

Thank you,
Fedor

[ASG]

Hi Fedor,

Sorry - the support has all files needed. I understand that this is not the right place for this - I'll be reporting back when there is a fix for my problem!

Thanks!
ASG

[wishr]

No worries, as far as I see now the support team has all the necessary info that is being processed at the moment. We do keep a track of the request either.

Regards,
Fedor

[ASG]

Update:

Since we've had a power outage and had to power everything back on yesterday the issue is gone when using the latest backup as a surebackup source. As the production vm hade no issues rebooting etc... during normal use I can't really pinpoint anything that was the problem.

Case is closed since the error is not reproducable anymore using backup from tonight.

[wishr]

Hi ASG,

Thanks for sharing the result! Sounds a bit strange, however, I'm glad to see the issue is solved now.

Regards,
Fedor