You cannot perform a system state backup on a domain controller that is running Windows Server 2003 SP1 (913642)
The information in this article applies to:
- Microsoft Windows Server 2003 SP1, when used with:
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
SYMPTOMSYou try to perform a system state backup on a domain controller that is running Microsoft Windows Server 2003 Service Pack 1 (SP1). However, the process that backs up the Active Directory database and the Active Directory log files fails. Additionally, an error message that resembles the following appears in the backup log: Operation: Backup Active backup destination: File Media name: "sysstate.bkf created DD/DD/YYYY at HH:MM AM|PM"
Volume shadow copy creation: Attempt 1. "NTDS" has reported an error 0x800423f0. This is part of System State. The backup cannot continue.
Error returned while creating the volume shadow copy:800423f0. Aborting Backup. CAUSEThis problem occurs if the Volume Shadow Copy Service (VSS) does not perform a volume snapshot of the drive that contains the log files. The VSS does not perform a volume snapshot if the following conditions are true: - Either the DIT volume or the volume that contains the Active Directory log files resides on the system drive.
- The Active Directory log files have been moved from the system drive, and the DIT volume resides on the system drive.
The following table lists the outcome for five scenarios in which the DIT volume, the operating system, and the log files are stored on a computer. You cannot create system state backups for scenarios 3 and 4 on a computer that is running Windows Server 2003 SP1. Scenarios | 1 | 2 | 3 | 4 | 5 | Operating System | C | C | C | C | C | Database | C | D | C | D | D | Log files | C | E | D | C | D | Outcome | Success | Success | Failure | Failure | Success | Note Letters C, D, and E represent drives on the domain controller. The drive letter assignments do not have to match the drive letter assignments in the table. The drive letters in the table indicate the relative placement of the operating system, the database, and the log files. You may not experience this issue in the original release version of Windows Server 2003. RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesTo install this hotfix, your computer must be running Windows Server 2003 Service Pack 1 (SP1). Restart requirementYou must restart your computer after you apply this hotfix. Hotfix replacement informationThis hotfix does not replace any other hotfixes. File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2003, Itanium-based version |
Ntbackup.exe | 5.2.3790.2622 | 3,592,704 | 20-Jan-2006 | 03:17 | IA-64 |
Windows Server 2003, x64-based version |
Ntbackup.exe | 5.2.3790.2622 | 1,964,032 | 20-Jan-2006 | 03:18 | x64 |
Windows Server 2003, x86-based version |
Ntbackup.exe | 5.2.3790.2622 | 1,229,312 | 20-Jan-2006 | 02:38 | x86 |
WORKAROUNDTo work around this problem, use one of the following methods: - Store the DIT volume, the operating system, and the log files on the domain controller, as shown in scenarios 1, 2, or 5 in the "Cause" section.
Note Drive letter assignments on the domain controller do not have to match the letter assignments in the scenarios table.
You may have to relocate a DIT volume or the Active Directory log files from a domain controller that has been restarted in directory services repair mode.
For more information about how to move the database and to move the log files, click the following article number to view the article in the Microsoft Knowledge Base:
816120
How to use Ntdsutil to manage Active Directory files from the command line in Windows Server 2003
- If a domain controller configuration corresponds to scenarios 3 and 4, use the Ntbackup utility to select any file on the volume that includes Active Directory database files. This file can be a dummy file. In this configuration, this volume is backed up by the Ntbackup utility.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Major | Last Reviewed: | 8/18/2006 |
---|
Keywords: | kbBug kbfix kbQFE kbhotfixserver kbpubtypekc KB913642 kbAudITPRO |
---|
|