I would highly suggest not to image your Dc's. As soon as you do that and restore on it is an unsupported configuration. MS does not support imaging a DC for DR purposes. You are better off having another DC off site or just use system state backups.
On Sat, Mar 7, 2009 at 4:14 PM, Bob Muzzy <[email protected]> wrote: > Sorry if my shorthand was unclear. I'm aware that holding the FSMO roles > isn't the same as being a PDC but by that very token, every DC is NOT just a > DC, they just all have writable copies of the AD data. > > Both my DCs are GCs and have DNS in AD. My issue may well be replication or > perhaps I didn't give it enough time. I'll verify with netdiag and the utils > you suggested. > > The point of my exercise is developing a disaster recovery plan. I want to > use True Image to make nightly image backups of servers. I can script it to > consolidate the full and differential files and to then convert the image > file into a .vhd file. My idea is to be able to bring a failed server back > up as a virtual machine. This would get the server to a functional state > quickly, and would permit working on the server during business hours, when > tech support and vendors are available. > > In my proposed scenario, if the restored server were an AD DC, it could be > as much as 24 hrs out of sync. So I want to verify it can update user > records by one means or another. > ~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~ > ~ <http://www.sunbelt-software.com/product.cfm?id=400> ~ > ~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~ ~ <http://www.sunbelt-software.com/product.cfm?id=400> ~
