Backup Windows Server 2003 Active Directory
Backing up Active Directory is essential to maintain the proper health of the Active Directory database. You can backup Active Directory by using the NTBACKUP tool that comes built-in with Windows Server 2003, or use any 3rd-party tool that supports this feature. Backing up the Active Directory is done on one or more of your Active Directory domain Controllers (or DCs), and is performed by backing up the System State on those servers. The System State contains the local Registry, COM+ Class Registration Database, the System Boot Files, certificates from Certificate Server (if it’s installed), Cluster database (if it’s installed), NTDS.DIT, and the SYSVOL folder.
To ensure your ability to actually use this backup, you must be aware of the tombstone lifetime. By default, the tombstone is 60 days (for Windows 2000/2003 DCs), or 180 days (for Active Directory based upon Windows Server 2003 SP1 DCs).
Passwords Haven’t Disappeared Yet
123456. Qwerty. Iloveyou. No, these are not exercises for people who are brand new to typing. Shockingly, they are among the most common passwords that end users choose in 2021. Research has found that the average business user must manually type out, or copy/paste, the credentials to 154 websites per month. We repeatedly got one question that surprised us: “Why would I ever trust a third party with control of my network?
Note: Longer tombstone lifetime decreases the chance that a deleted object remains in the local directory of a disconnected DC beyond the time when the object is permanently deleted from online DCs. The tombstone lifetime is not changed automatically when you upgrade to Windows Server 2003 with SP1, but you can change the tombstone lifetime manually after the upgrade. New forests that are installed with Windows Server 2003 with SP1 have a default tombstone lifetime of 180 days. Read my “Changing the Tombstone Lifetime Attribute in Active Directory” article for more info on that.
Any backup older than 60/180 days is not a good backup and cannot be used to restore any DC. You do not need to backup all your DCs’ System States, usually backing up the first DC in the Forest + the first DCs in each domain is enough for most scenarios.
Purpose of Performing Regular Backups
You need a current, verified, and reliable backup to:
- Restore Active Directory data that becomes lost. By using an authoritative restore process, you can restore individual objects or sets of objects (containers or directory partitions) from their deleted state. Read my “Recovering Deleted Items in Active Directory” article for more info on that.
- Recover a DC that cannot start up or operate normally because of software failure or hardware failure.
- Install Active Directory from backup media (using the dcpromo /adv command). Read my “Install DC from Media in Windows Server 2003” article for more info on that.
- Perform a forest recovery if forest-wide failure occurs.
All these are reasons to have good working and reliable backups.
Note: One of the Active Directory features that was introduced in Windows Server 2003 with Service Pack 1 was the Directory Service Backup Reminders. With this reminder, a new event message, event ID 2089, provides the backup status of each directory partition that a domain controller stores. This includes application directory partitions and Active Directory Application Mode (ADAM) partitions. If halfway through the tombstone lifetime a partition has not been backed up, this event is logged in the Directory Service event log and continues daily until the partition is backed up.
Note: You can only back up the System State data on a local computer. You cannot back up the System State data on a remote computer.
Method #1: Using NTBACKUP
- Open NTBACKUP by either going to Run, then NTBACKUP and pressing Enter or by going to Start -> Accessories -> System Tools.
- If you are prompted by the Backup or Restore Wizard, I suggest you un-check the “Always Start in Wizard Mode” checkbox, and click on the Advanced Mode link.
- Inside NTBACKUP’s main window, click on the Backup tab.
- Click to select the System State checkbox. Note you cannot manually select components of the System State backup. It’s all or nothing.
- Enter a backup path for the BKF file. If you’re using a tape device, make sure NTBACKUP is aware and properly configured to use it.
- Press Start Backup.
- The Backup Job Information pops out, allowing you to configure a scheduled backup job and other settings. For the System State backup, do not change any of the other settings except the schedule, if so desired. When done, press Start Backup.
- After a few moments of configuration tasks, NTBACKUP will begin the backup job.
- When the backup is complete, review the output and close NTBACKUP.
Next, you need to properly label and secure the backup file/tape and if possible, store a copy of it on a remote and secure location.
Method #2: Using the Command Prompt
You can use the command line version of NTBACKUP in order to perform backups from the Command Prompt.
For example, to create a backup job named “System State Backup Job” that backs up the System State data to the file D:\system_state_backup.bkf, type:
ntbackup backup systemstate /J "System State Backup Job" /F "D:\system_state_backup.bkf"
For Microsoft’s official documentation on Active Directory backups, see: Active Directory Operations Guide – Active Directory Backup and Restore