Volume shadow Copy error:800423f0

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm getting the following error message and code when I back up (ASR) W2K3 domain controllers using NTbackup. I get it on my production DC's and Test Network DC's at work, and even on my two domain controller network at home. Appreciate any help you can give. Thanks

Error returned while creating the volume shadow copy: 800423f
Reverting to non-shadow copy backup mode

Only occurs on Domain Controllers. Can't find reference to this error code anywhere. Appreciate any clue
Thanks
 
Hi,

This specific error code (800423f0 = inconsistent VSS snapshot) is
usually specific to the VSS Active Directory writer, when used from
NTBackup. The VSS AD writer (or NTSD writer) is a VSS component that
allows Active Directory to participate in VSS-enabled backups.

This error happens when you are attempting to create a backup of your
domain controller that doesn't include all the relevant volumes in
your backup. For example, if the AD database are on C: and the AD logs
are on D: then you need to include both volumes in the backup.

If you include only C: or only D:, then you will experience the error
below. BTW - the backup should still succeed (in non-snapshot mode)
even if the VSS AD writer will show the error below.

Thanks, Adi

P.S. This posting is provided "AS IS" with no warranties, and confers
no rights.
 
Hello Adi,
I took your suggestion and selected both C: and D: and SystemState, and the shadow copy ran without errors. I then moved the NTDS log files from the D: drive to C: using NTDSUTIL and ran an ASR backup. It ran without the error. However, with the log files located on D:, and no way to select D: when running the ASR wizard, I continue to get the error and the log files are NOT backed up. Any further suggestiions short of moving all DC log files back to C:. I tried to follow "Best Practices" by placing the database and log files on seperate drives. Thanks for your help.
 
Just to let you know that even if you get a Shadow Copy error, you
should still have the AD database and logs are still backed up. The
way it works for AD is the following: NTBackup tries first to create a
shadow copy and backup its contents to the tape. If this fails (due to
800423f0 errors for example) then NTBackup will backup the AD database
and logs without the use of VSS.

Anyway, regardless of the backup methodology you use, you should
properly test the (ASR) restore to ensure that everything is
backed-up/restored correctly.

Thanks, Adi

P.S. This posting is provided "AS IS" with no warranties, and confers
no rights.


MikiPete said:
Hello Adi,
I took your suggestion and selected both C: and D: and SystemState,
Click to expand...
and the shadow copy ran without errors. I then moved the NTDS log
files from the D: drive to C: using NTDSUTIL and ran an ASR backup.
It ran without the error. However, with the log files located on D:,
and no way to select D: when running the ASR wizard, I continue to get
the error and the log files are NOT backed up. Any further
suggestiions short of moving all DC log files back to C:. I tried to
follow "Best Practices" by placing the database and log files on
seperate drives. Thanks for your help.
 
Back
Top