Unison wrote: I dont see how veeam could make the DC recovery process any easier/better, but maybe at the very least, Veeam could release an extensive technical document/OS that could walk through step by step in detail exactly what SHOULD happen when you recover a DC (what the veeam developers expect through the whole process).....it should show what Veeam is in control of, when veeam is in control, what veeam changes in the OS, at what points those changes are made, when changes are changed back if they are changed back, at what point the OS takes over DC recovery, what the OS is looking for, what changes the OS makes (like setting new identifiers), when reboots should happen, how many reboots should happen, why a reboot happens, rough time periods between events etc etc etc.....with a detailed document like this, at least we could have a fighting chance of tracking down what is NOT happening when a DC recovery is unsuccessful.
Fiskepudding wrote:What would be ideal, would be to restore 1 DC first… and be able to choose restore mode (the first one you select, authorative restore)
I guess when you pick restore on a VM, Veeam can check some metadata and see if it is an DC, and give your these choices during restore dialogue.
Even if Veeam can't check if it is an DC druing the restore dialog, there cold maybe be a Advanced optoin containing these DC restore choices??...:
Is there no other DCs running in your enviroinment (autthorative restore) ( ) Radio button
There are at least one running DC in your environment (non-authorative restore) () Radio button
Unison wrote:It might be worth a shot to change your DNS config on your NICs - depending on who you talk to, best practice is to have DCs point to themselves as primary DNS.....others say not to point to themselves as primary. Changing the NIC config for DNS on your DCs specially short term wont cause you any issues because just the order is changing - both DNS servers have the same data anyway. Ive made the DCs point to themselves for primary DNS purely for this purpose, could it be the difference... maybe it is helping that when the DC comes online it will try its self for DNS first and eventually accept that....causing one of the DCs to become authoritative and then brining everything else back online successfully.
Unison wrote:How am i (and assume im not alone...) able to successfully recover all DCs and the AD environment without manually forcing one of the recovered DCs into 'authoritative mode'?
Unison wrote:Tom, do you think this document might still be months/years away based on where you got up to with it? A lot of detail on this subject can now be found in these posts - but that would take someone so long to read and patch together.
When it does come along - will you post about it here and maybe even get Gostev to release it in his newsletter emails? Thanks for your efforts Tom!
Fiskepudding wrote:Different AD tools works for periodes, then dont work for periodes, then work again....
Lots of errors (Netlogon,DFS service and group policy) in event viewer.
tsightler wrote:So the rebirth of this thread has reignited my efforts to create this document. I'll see about putting together a draft in the next couple of weeks as long as I can find enough time to test the recovery scenarios. It may take a little time from that point to become an officially published doc, which would be my goal, but I'll provide something in the interim. Ideally I can coax a few people in this thread to test the procedures I write up as that's part of the challenge. It's easy enough to create a lab and test things, but real world environments have a tendency to shake out additional issues.
If you don't see a draft posted in this thread in the next couple of weeks, ask for an update or shoot me a PM. I think the bulk of the information is here in the thread now, so it's just a matter of formalizing it and testing the documented procedure.
Users browsing this forum: Google [Bot], serkantek and 44 guests