Backup Error 0x800423F0

After using an ASR set to recover Domain Controller which went into eternal
blue screen after Server 2003 SP1 was applied. I decided to refresh all our
ASR sets. Now a machine that succesfully completed a ASR set backup prior to
SP1 is giving me an error and will not complete the backup at all.

Volume shadow copy creation: Attempt 1.
"NTDS" has reported an error 0x800423f0. This is part of System State. The
backup cannot continue.

Anyone have any ideas?

Thanks,

Bernie Walker.

 

Have the same error, cannot backup system state since SP1 applied to any
domain controller.

No answers to my post yesterday, nothing in the knowledge base. Event ID
8019 logged in Application event log.

 

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
set.)

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.

Derek Nathan

 

So much for recommending that the database and log files be on separate
drives.
How do you manually add a text file on a different drive to an ASR backup?

Thanks for the update,

Bernie.

 

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
again.

Next
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.

Next
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.


: