>There are also ways to configure the TSM client to facilitate Win2K (and
Win2k3) dissimilar hardware restores.

And they are? This server runs a daily incremental with ALL-LOCAL. Is there
something I should do as a PRESCHED for Active Directory? I did find an AD
Recovery paper on Microsoft, but haven't gotten through the entire document.

Bill Boyer
DSS, Inc.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Stapleton, Mark
Sent: Tuesday, September 16, 2003 7:30 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: BMR of an Active Directory server


From:   Christian Svensson [mailto:christian.svensson AT CRISTIE DOT SE]
>The error you got is normal when you run that kind of restore of your AD
Server. What you need to do is.
Start your Windows 2000/2003 Server in AD repair mode (F8)
Logon as local admin.
Start the TSM Client and restore the system object again.
When the restore if finish.
Reboot your server and the machine is up and runing.

But you can do your BMR solution much faster with a 3rd part BMR tool.<


Third-party BMR tools (trying to sneak that advertisement in, aren't cha?
;oP) aren't really necessary for AD (or domain controller) restores. What
*is* necessary is a thorough understanding of how AD works, and how to
recover it.

Microsoft's web site is chock-full of white papers on DR processes for AD
databases. There are also ways to configure the TSM client to facilitate
Win2K (and Win2k3) dissimilar hardware restores.

--
Mark Stapleton (stapleton AT berbee DOT com)