Windows 2008: built-in full system restore on FISMO DC and concern with USN rollback
hello,
i have 5 dcs in ad domain , rely on full system restore , replication able dc disaster recovery in case 1 of dcs failed or become corrupted.
i planning use windows built-in backup system full os backup on domain controllers , standalone certificate servers once every month , rely on able re-build dcs ca on them, bare metal.
my concern don’t understand how full system restore not cause issue update sequence number (usn) , create usn rollback problem?
how windows restore handles usn when month old dc system os backup restored?
considering vhd backup bad bad idea dcs, simplest , reliable backup , restore approach here?
thank you,
you taking right approach. hear asking is essentially "why restoring dc state month ago not put server usn rollback?" reason windows server backup automatically resets invocationid (and 1 other critical reg key) which tells other domain controllers "hey, have restored database can updates since then?"
if invocationid not reset, other dc's see have more recent updates same instantiation of database on restored dc, , claim in usn rollback.
see "domain controller restore process , the invocationid" section in blog below. (i realize you're not talking authoritative restore, logic still applies.) should explain bit more.
http://blogs.msdn.com/b/richpec/archive/2011/10/07/the-authoritative-restore-explained.aspx
Windows Server > Directory Services
Comments
Post a Comment