Surebackup Domain Controller

[flaco216]

In the KB 1066 http://www.veeam.com/kb1066 i read this for the Surebackup Roles:


..."In addition if the Global Catalog or Domain Controller roles are selected for the VM, then the following modification will be done in the registry:

Veeam sets global BurFlags registry key located inHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup to d2

That means a nonauthoritative restore mode will be activated.

Please refer to support.microsoft.com/kb/290762 for details."...



MMMMHH.... i think is authoritative in SureBackup environment...in the logs of my Sure Backup Jobs for DCs (withe the DC GC and DNS roles for surebackup checked) i can see in the [PrepareDC]:
"Burflags"=dword:000000D4 for the key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
and also:
[PrepareDC] Finishing 'Authoritative Restore' processing engine

This is authoritative for me... correct??

thank you!!

[ori]

I would like to join this question. My SureReplica log shows D4 (which is the desirable state - authoritative) but Ntfrs on the DC acts as non-authoritative - eventid 13565 is logged in the "File Replication Service" event log instead of eventid 13566 (https://support.microsoft.com/en-us/kb/308406). Can anyone confirm it is working for him as expected?

[foggy]

I can confirm that SureBackup performs an authoritative restore of the DC in the application group.

That means a nonauthoritative restore mode will be activated.

Apparently, this is a mistake in KB, I will pass this to a proper person for correction.

I would like to join this question. My SureReplica log shows D4 (which is the desirable state - authoritative) but Ntfrs on the DC acts as non-authoritative - eventid 13565 is logged in the "File Replication Service" event log instead of eventid 13566 (https://support.microsoft.com/en-us/kb/308406). Can anyone confirm it is working for him as expected?

I recommend to let our support engineers take a look at your setup as this is not an expected behavior.