rawtaz wrote:Alright, so assuming this hasn't worked like it should, what would be the way to have it dealt with to get the DC running? Should I boot it up in DSRM myself and do whatever one does in there, and then it should be fine after a reboot? I guess this would be the sensible way to deal with it, aside from having support look at the issue of course (which I don't fancy at the moment as I would like to get going with this DC ASAP). On the other hand I have read at least once that in 2008 the DSRM is no longer needed except for in some special situations.
foggy wrote:Reading through this topic, DC recovery is fully automated and does not require any user interaction. The restored VM should first boot in safe mode and then reboot automatically immediately to boot up next time normally.
Loki wrote:We tried to log in as domain administrator but an error message told us that no server was available for logging.
Waited for the reboot that never came.
daryanx wrote:Point to note here, to avoid confusion of others who need to read this thread to reassure themselves of their DC restore. The machine boots to the "dirty shutdown" screen but DOESN'T then boot to safe mode - it actually boots normally. In other words the default option at the dirty shutdown screen is something like 'Load Windows Normally' and if the machine is not touched (as it shouldn't be) this is the boot option chosen. This is as per Veeam design although is not documented anywhere
Alessio, you do not even need to log in, just let the VM to reboot automatically. As was stated in this topic many more times, the process of the DC restore is FULLY automated and you do NOT need to do ANYTHING (even try to log in until the VM is booted the second time normally). Logging in after the first boot brakes the whole restore process.
Loki wrote:After the restore we let the VM alone for aprox 30 minutes. It didn't reboot, just stood there doing anything (we were checking CPU and disk usage on the Vmware Console).
I have been testing DR of an Active Directory 2003 domain using Failover to replica. One of the things I have come across is the need to mark SYSVOL as authoritative (BurFlags) after the domain controllers have gone through the DSRM process. The process you need to go through to do this manually is complex and adds lots of time to the recovery.
In Backup Exec/Windows Backup you can mark SYSVOL as authoritative and it sorts it out for you. My question is can Veeam provide the same functionality and thus make the whole recovery process a lot easier and smoother?
Users browsing this forum: Bing [Bot], dcb, Google [Bot] and 79 guests