TL;DR - I want to be able to automate authoritative domain controller restore / failover
One thing we've noticed, is that while SureBackup / SureReplica has a nifty feature to automatically test domain controllers as Authoritative, there's no simple way to restore a backup or turn on a replica as authoritative (that I can find anyways). I opened up case 02463566 to verify, and to also check and see if the mechanism / script used in SureBackup is available to us during a restore and failover (which it isn't).
What we've noticed is that when we restore a DC or turn on a replica, it boots once, then reboots in non-authoritative mode (which is great for most cases, but not all). When the VM reboots into non-authoritative, it moves all of its Sysvol contents into a folder called "NtFrs_PreExisting__See_EventLog". This is where things get hairy. If you're aware of the restore process for domain controllers (like I am now, but was not the first couple of times I had to restore an entire environment), you can go into that folder and copy your sysvol contents into a safe place. If you aren't aware of the restore process, this is an issue. When you go to flip Burflags to D4 in the registry, then run a stop / start of ntfrs, that "PreExisting" folder gets blown away almost immediately. If you didn't copy the contents to a safe place, you have to restore the folder from backup - right after you just restored your DC from backup. In my personal experience, this leads to a "Aw man, WTH is happening with domain replication?", which is never fun when you're already in a likely stressful situation. I'm glad I know what to do now, but I'm sure a lot of people don't and are in for the same "gotcha" that I got.
It would be nice during a restore or failover if you were prompted to do authoritative or non-authoritative restore, and Veeam could leverage the same technology that is baked into SureBackup.
Now this is the part where someone makes me look dumb and tells me it's already a feature.