Windows IT Pro is the authoritative and independent resource for windows nt, windows 2000, windows 2003, windows xp. Features a collection of resources and magazines for windows IT professionals.
  
  
  Advanced Search 


July 2004

Delayed-Replication AD Recovery

It's like turning back the hands of time
RSS
Subscribe to Windows IT Pro | See More Active Directory (AD) Articles Here | Reprints | Or get the Monthly Online Pass—only $5.95 a month!
SideBar    Including Application Partitions

Restore the object. Because the lag DC's copy of the directory still contains the object, you can restore it without the necessity of retrieving tape backups or restoring an old directory tree file. You can use Ntdsutil to increase the object's universal serial number (USN) by an increment of 100,000, thereby ensuring that the restored object will win the replication conflict.

  1. Reboot the delayed-replication DC you're using into Directory Service Restore Mode. To do so, press F8 at the OS selection screen during bootup and select the Directory Services Restore Mode option. You'll need to know the restore-mode password to log on.
  2. At a command prompt, type ntdsutil. Select the Authoritative Restore option by typing authoritative restore.
  3. Type restore object, followed by the object's DN. For example:
  4. restore object CN=jesse.sutela@hp.com,
    	OU=US,DC=wamericas,DC=wtest,
    	DC=cpqtest,DC=net
    This command should appear on one line. Wrap the DN in quotes if it contains any spaces. Press Enter.
  5. Reboot into regular mode.

Replicate the restored object into the rest of the domain. Determine which production DC in the domain is pulling updates from the delayed-replication DC by looking in the Active Directory Sites and Services snap-in. After you find the production DC that has a connection object from the delayed-replication DC you want, right-click the connection object and select Replicate Now to force the production DC to pull updates from the delayed-replication DC. The restored object should now replicate back to the production DC.

Recovering Crucial Information about the Deleted Object
If a user object has been deleted, restoring the object won't necessarily restore everything about that user. For example, when you restore a user object in Win2K, group memberships are lost. Therefore, you might also want look at the user's properties in the Active Directory Users and Computers snap-in. You can gather the group memberships for the user on the Member of tab of the account's Properties sheet. Windows 2003, in contrast, does a good job of fixing the domain group memberships after a restore. However, in either OS, membership in local groups of trusting domains will still be lost.

Keeping close track of local group memberships and logging that information will let you repopulate local groups after a user restore. This task might be tedious if you don't use some form of scripted automation. For more information about restoring groups, see "Resources," below.

Of course, other types of objects in AD might require restoration. One example is DNS data. Be mindful that DNS data might be stored within an application partition. Windows 2003 lets you move DNS data out of the default naming context and into an application. By default, application partitions aren't replicated to all DCs. For more information about how to ensure that your disaster-recovery plan includes application partitions, see the sidebar "Including Application Partitions,".

Up-Front Costs
You might think delayed replication sounds great, but the cost of having several extra servers sitting around, doing very little other than replicating once per week, will make the solution a hard sell to those in control of the IT budget. Bear in mind that a recovery site reduces the number of personnel necessary to recover a deleted object and decreases the amount of lost productivity for the affected user.

Besides using the justification that delayed replication is an insurance investment, you can further mitigate the up-front costs through the use of virtual servers. Assuming you have sufficient memory and processing power, all your recovery DCs could reside as virtual-server instances on one virtual-server host.

Turn Back Time
Recovery of deleted AD objects can be a lengthy process that involves more than one support group, particularly in midsized to large companies. Coordination of efforts and backup-tape location can lead to lengthy downtimes for users. In the event that a user account or entire subtree of objects is deleted, rapid recovery is crucial to keeping your business running smoothly. Using a delayed-replication site to facilitate the recovery of deleted objects is like turning back the hands of time.

Resources
MICROSOFT ARTICLES

"How to restore deleted user accounts and their group memberships in Active Directory"
http://support.microsoft.com/?kbid=840001

"Authoritative restore of groups can result in inconsistent membership information across domain controllers"
http://support.microsoft.com/?kbid=280079

"HOW TO: Perform an Authoritative Restore to a Domain Controller in Windows 2000"
http://support.microsoft.com/?kbid=241594

"HOW TO: Manage the Application Directory Partition and Replicas in Windows Server 2003"
http://support.microsoft.com/?kbid=322669

"How to Optimize the Location of a Domain Controller or Global Catalog That Resides Outside of a Client's Site"
http://support.microsoft.com/?kbid=306602

End of Article

   Previous  1  2  [3]  Next  


Reader Comments
perfect one!

johannes.frick July 20, 2004 (Article Rating: )


Geniality in simplicity - just have to think of it. More of these please!

Gerrekens August 05, 2004 (Article Rating: )


Absolutely Fantastic Article. Beautifully simple yet effective technique to address a real service delivery problem. JK.


joe8908 August 20, 2004 (Article Rating: )


Very nice, but this technique has a drawback: if you must reinstall a Server/XP/DC from scratch with the same name (f ex because of a major hardware issue), one must make sure the previous account is deleted from ALL DCs, including those in the delayed-replication site. Let's say you use delayed-replication on DC03, well after removing the old computer account from AD on another DC, you need to either wait for the delayed replication or delete the computer account manually on DC03.
If you do not, and join domain with the same computer name, the old computer account still exists on DC03. You will use that computer account, but it's about to be deleted and your restored server/xp/DC will soon find itself out of the domain...
Uncool. MVL.




MVL December 17, 2004 (Article Rating: )


MVL - Adding a computer to a domain will generate a new ObjectGUID so even if you use the same computer name, there shouldn't be a problem with the old computer object that's about to be deleted.

leachmj July 21, 2005 (Article Rating: )


Well, that's just the issue, because when you join domain, Windows will check if the computer name still exists on all DCs (including the "lagged" one). No new ObjectGUID is created... and tthe object gets deleted at the next replication cycle...
If one uses the netdom command and specifies the DC on which the account is created, then it's OK.

MVL November 21, 2006 (Article Rating: )


You must log on before posting a comment.

If you don't have a username & password, please register now.




Top Viewed ArticlesView all articles
Command Prompt Tricks

One reader shares his tip for setting up the command prompt to reflect a remote path. ...

How can I stop and start services from the command line?

...

PsExec

This freeware utility lets you execute processes on a remote system and redirect output to the local system. ...


Active Directory (AD) Whitepapers Sustainable Compliance: How to reconnect compliance, security and business goals

Managing Unix/Linux with Microsoft System Center Operations Manager 2007 Cross Platform Extensions Beta

Addressing the Insider Threat with NetIQ Security and Administration Solutions

Related Events Concrete Ways to Make Sure Your SharePoint Deployment Doesn't Blow Up

Introduction to Identity Lifecycle Manager "2"

Check out our list of Free Email Newsletters!

Windows OSs eBooks Understanding and Leveraging Code Signing Technologies

Keeping Your Business Safe from Attack: Monitoring and Managing Your Network Security

Windows 2003: Active Directory Administration Essentials

Related Active Directory (AD) Resources Become a VIP member of the Windows IT Pro community!
Get it all with the VIP CD and VIP access. A $500+ value for only $279!

Subscribe to Windows IT Pro!
Solve your toughest technical problems with our experts and access 10,000 + articles online. 30% off

Monthly Online Pass - Only $5.95!
Get instant access to 10,000+ articles from Windows IT Pro Magazine!

TechNet Virtual Labs
Evaluate and test Microsoft's newest products.


Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro Windows Dev Pro IT Job Hound ITTV
IT Library Technology Resource Directory Connected Home Windows Excavator Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 Copyright © 2008 Penton Media, Inc., All rights reserved. Terms and Use | Privacy Statement | Reprints and Licensing