"NTDS" has reported an error 0x800423f0 - The backup cannot continue.

Discussion in 'Windows Server' started by Christopher Yorke, Apr 19, 2005.

  1. After I installed Service Pack 1 on my Windows Server 2003 domain
    controllers, 1 domain controller would not complete a backup using ntbackup.
    I receive the following report:

    Backup Status
    Operation: Backup
    Active backup destination: File
    Media name: "ad03tst.bkf created 4/19/2005 at 5:13 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.


    The operation did not successfully complete.


    After google'ing the error, I found this resolution:

    I have got a resolution from microsoft Product support.

    It is a bug with SP1. The resolution is as follows.

    Option 1 or Option 2. I found option 2 easier as option 1 requires a server
    restart and will mean AD DB & Log are both on C: drive.

    1. Moving the AD log files back to the default location ("C:").

    2. Select "D:" (or a file in that volume) to force a shadow copy on it.
    This, in turn will suppress the NTDS writer error. (I created a dummy text
    file on the drive where my NTDS Log files were and included in the backup

    The likely reason behind those error messages is that AD is configured such
    that it keeps the databases and the logs on separate volumes.
    The AD writer (NTDS) will report an error if you try to create a shadow copy
    set that has one of the volumes but not the other.
    The problem is that in this configuration (AD databases and logs are on a
    different volume) NTBackup doesn't pick up the correct set of volumes.
    By selecting system state, NTBackup requests for a shadow copy to be created
    on the boot volume.
    By the time NTBackup requests for the location of the AD database and logs,
    the shadow copy has already been created.
    Thus, NTBackup will not create a snapshot on "D:".
    This throws the NTDS writer off, thinking that NTBackup is not going to pick
    up all its data on D: thus causing an error.

    I chose option #2, created a txt file on the partition with my log files and
    selected the file during backup. The backup completed successfully.

    I just thought I would share this in case anyone else comes accross it.
    Otherwise, my SP1 installation went very well. :)

    Christopher Yorke, Apr 19, 2005
    1. Advertisements

  2. Christopher Yorke

    James White Guest

    There is more to the solution than meets the eye

    Check your scheduled Jobs,
    they must reference a bks file in the form "@c:\pathname\filename.bks"
    If your job is in the form
    C:\WINDOWS\system32\ntbackup.exe backup systemstate /n "Monday... you need
    to change it to
    C:\WINDOWS\system32\ntbackup.exe backup "@c:\pathname\filename.bks" /n "Monday

    When you apply the changes, you will probably need to add the job password

    Use NTBACKUP to load that bks selection file, and in the selections, as well
    as SYSTEM State ticked, a file on the same drive as your ADLOGs must be
    ticked, optionally tick a dummy file on all drives. If you were not using a
    selections file before, you need to save thse selections and go back to step
    1 above to reference this file - note the "@" is ESSENTIAL, or you will just
    backup the bks file.

    Test run your sheduled Job

    I note that the Job type should be normal or copy e.g." /m normal" in the
    scheduled job command line, otherwise if the file is not changed since the
    last archive the attribute will not be set and this MAY cause the file to be
    ignored and the System state to fail as well as no shadow was created- I am
    not sure.
    James White, May 4, 2005
    1. Advertisements

  3. Many thanks, it worked ! :)
    mindaugas.ardavicius, Oct 12, 2012
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.