Recently upgraded a client to a new server, running ESXi. It has 2 windows servers and a win10 backup and replication server as VMs. The old server was also ESXi only running 1 windows server and the windows agent. When I first tried to bring the new server up starting with a bare metal restore of the original server I ran into problems because Veeam would not restore the server to a functional state because it was a standalone domain controller. There were many suggestions on how to correct this but none of them worked. Finally I got around this by setting up a new windows server on the new hardware with the old server still running on the old hardware, and made it a BDC. Then when I turned off the old server and restored it to the new hardware it synced to the existing Domain Controller and worked normally.
Now I want to take backups from the same vm on the new server, and restore to the original vm on the old hardware, which will be in a different location, creating a disaster recovery machine of their accounting system in case they need it. The problem comes back to restoring a standalone server that is also a domain controller.
Previously I was doing a full bare metal recovery of the server … Is there some other type of restore I could use to restore the system drive, perhaps a volume restore of only drive c: ?
Or maybe step by step instructions on restoring a stand alone domain controller where there isn’t a a second domain controller to verify the domain data is up to date? or maybe a hidden option to tell veeam that “yes I know it’s a domain controller … go ahead and use it”?
Thanks for your help, Cla.