SureBackup DC starts in safe mode

[redhorse]

Hello,

my DC for SureBackup starts (and stays) in safe mode and that's the reason why the whole SureBackup-Job fails. When I reboot my production DC it doesn't start in safemode so it should be an issue when it boots from the backup. This issue started after we upgraded to B&R 9 U2.

I followed the solution in KB1277 (https://www.veeam.com/kb1277) and removed the safemode flag manually (bcdedit /deletevalue safeboot) and after that the DC started correctly. Sure this is not the solution for the SureBackup-Environment, so what could be the reason for the safe mode?

Kind regards

[foggy]

Are you using application-aware image processing in the corresponding backup job? Have you selected the DC role for that VM in the SureBackup job settings?

[Vitaliy S.]

If everything above is checked and enabled, can you try another restore point from the backup chain? Does it have the same issue?

[redhorse]

Yes, both is checked.

Although nothing changes on the DC some restore points work, the same issue with a second DC.

I opened a case: #01880046

[DaStivi]

anything new on the Case? I've opened one too, same issue!

[redhorse]

The support told me to set a registry on the backup server, but that didn't work:
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\
DWORD EnsureVeeamVssSvcRegistered = 1

After a few days the issue didn't occure anymore but since today it's back again, so I startet a new support call (case #01901929)

[StefanB]

Same issue here,

Case # 01902353. Using 'bcdedit /deletevalue safeboot' and running the connectiontester.exe manually afterwards could reach every needed port for the dc running on win2012r2. V9 U2 is installed.

[hyvokar]

I have the same issue here on two different systems. Problem started when upgraded to v9 u2, before that surebackup was working fine. Please post possible solutions.

[StefanB]

Support told me to set a new reg key on affected DCs:

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication]
"UseGranularBcdRestore"=dword:00000000

And yes - after a new quick backup of the vm - the next SureBackup run with this new restore Point was successful. Will hope there are no side effects if we need to restore a dc to production Environment due to some errors...

[foggy]

Some DC recovery logic has changed in v9 Update 2, which affected DC recovery in isolated SureBackup environment. The mentioned registry value reverts the behavior back (for restore points created after editing registry), so should help in such cases.

[hyvokar]

Didnt work for me. I guess I have to start opening support tickets again

[foggy]

Yes, verifying the issue with support is recommended.

[Alec King]

Quick tip, the UseGranularBcdRestore registry key should fix the SureBackup problem - but there can be timing issues with Win2012R2 flushing data to disk. If the DC is backed up/replicated again right after the registry change, the new registry entry might not be captured.
If the DC is rebooted immediately after setting the registry key, Windows will flush all data to disk. Then run the backup/replication job again, and SureBackup / SureReplica job will verify the DC successfully.

[hyvokar]

Oh snap! I really need to learn to read. I made those changes on vbr servers, not on the DCs.

[hyvokar]

Support told me to set a new reg key on affected DCs:

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication]
"UseGranularBcdRestore"=dword:00000000

And yes - after a new quick backup of the vm - the next SureBackup run with this new restore Point was successful. Will hope there are no side effects if we need to restore a dc to production Environment due to some errors...

confirmed working on two separate environments. thanks!

[RolandSchauer]

Support told me to set a new reg key on affected DCs:

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication]
"UseGranularBcdRestore"=dword:00000000

And yes - after a new quick backup of the vm - the next SureBackup run with this new restore Point was successful. Will hope there are no side effects if we need to restore a dc to production Environment due to some errors...

works in my test environment

thanks a lot!

[bg.ranken]

It seems I'm also experiencing this same issue. Is reverting the DC recovery logic still the best solution or is there a hotfix out that resolves this issue? Or is this something that might wait till update 3 or the next version to fix?

[foggy]

Veeam B&R 9.5 will change the logic back.

[hyvokar]

Do we need to undo the registry changes made on DCs?

[foggy]

No need, since the default behavior will be the same as prescribed by the registry value (UseGranularBcdRestore = 0).

[hyvokar]

Good to hear. Thanks!

[Frosty]

I had this problem as well; can confirm that setting the Registry key fixed the SureBackup problems in our environment.