Testing AD DS Recovery and running into a strange problem


hi,

hopefully right place pose question.  i'm testing process of recoving ad , ad ds in event of disaster.  have backup of windows 2008 sp1 dc hosts 5 fsmo roles.  i'm able restore backup using bmr process.  problem run this.  i'm not restoring exact same hardware current dc running on.  when restored server boots , login have install driver nic card , re-assign ip address server.  after doing end folder named ntfrs_preexisting_see_eventlog under sysvol folder , login shares not present when @ machine.  if modify burflag under hklm\system\currentcontrolset\services\ntfrs\parameters\backup/restore\process @ startup , set d4 , reboot sysvol goes looking should (as far can tell) , login shares return.

is doing - doing full bmr to different hardware for dc supported?  if not recommended way recovering ad?  should build new machine scratch , restore ad backup?

also, have 2 other dcs have backups well.  best recovery policy rebuild scratch , let ad replicate new servers?  or should use bmr process restore servers well?

thanks , if wrong forum let me know , i'll repost question.

nick

hi nick

there many different ways skin particular cat.

personally, keep things simple , if dc fails replace performing a metadata cleanup of old dc, removing old dc sites , services , dns, seizing fsmo roles dc, , promoting new server (optionally same name , ip address).  need ensure metadata cleanup of old dc has replicated other dcs before introducing new dc same name.

bmr fine if you're comfortable it, wouldn't ever consider doing different hardware.


tony


Windows Server  >  Directory Services



Comments

Popular posts from this blog

Edit Group Policy

Hyper-V VM not reaching OS 'Logon' screen

DNS question...