RE: NTBackup, VSS & Shadow Copy Problem

Same problem here.

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
----------------------------------------------------
"Mike" wrote:

> We have a nightly job that runs NTBackup to dump the system state to a file,
> which we then include in our full nightly backups. Suddenly one of our PDCs
> have stopped backing up, we end up with a 2K file and the messages below in
> the Event Log and the NTBackup log.
>
> This did not happen before we installed SP1 this week. Both servers are
> running W2K3 + SP1, but only one is having this problem, however the one
> having the problem also has SQL Server installed, but I was not aware that
> it was even included in the shadow copy as we do our own daily dumps of
> those database anyways.
>
> Does anyone have any advice on what to look for here? I really need to get
> this nightly backup working again.
>
> Thanks,
> Michael
>
> ~~~~~~~~~~~~~~~~~~~~~
> Event Type: Error
> Event Source: VSS
> Event Category: None
> Event ID: 6005
> Date: 4/7/2005
> Time: 8:41:45 AM
> User: N/A
> Computer: PSBSRV2
> Description:
> Sqllib error: Database %1 is stored on multiple volumes, only some of which
> are being shadowed.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 2d 20 43 6f 64 65 3a 20 - Code:
> 0008: 53 51 4c 53 4e 41 50 43 SQLSNAPC
> 0010: 30 30 30 30 30 33 39 39 00000399
> 0018: 2d 20 43 61 6c 6c 3a 20 - Call:
> 0020: 53 51 4c 53 4e 41 50 43 SQLSNAPC
> 0028: 30 30 30 30 30 33 30 37 00000307
> 0030: 2d 20 50 49 44 3a 20 20 - PID:
> 0038: 30 30 30 30 35 39 38 38 00005988
> 0040: 2d 20 54 49 44 3a 20 20 - TID:
> 0048: 30 30 30 30 35 30 34 34 00005044
> 0050: 2d 20 43 4d 44 3a 20 20 - CMD:
> 0058: 43 3a 5c 57 49 4e 44 4f C:\WINDO
> 0060: 57 53 5c 53 79 73 74 65 WS\Syste
> 0068: 6d 33 32 5c 76 73 73 76 m32\vssv
> 0070: 63 2e 65 78 65 20 20 20 c.exe
> 0078: 2d 20 55 73 65 72 3a 20 - User:
> 0080: 4e 54 20 41 55 54 48 4f NT AUTHO
> 0088: 52 49 54 59 5c 53 59 53 RITY\SYS
> 0090: 54 45 4d 20 20 20 20 20 TEM
> 0098: 2d 20 53 69 64 3a 20 20 - Sid:
> 00a0: 53 2d 31 2d 35 2d 31 38 S-1-5-18
>
> ~~~~~~~~~~~~~~~~~~~~~
>
> Backup Status
> Operation: Backup
> Active backup destination: File
> Media name: "ADSRV2.bkf created 4/7/2005 at 8:41 AM"
>
> Volume shadow copy creation: Attempt 1.
> "MSDEWriter" 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.
>
> ----------------------
>
>
>
.

Relevant Pages

  • Re: Cannot backup Exchange VSS Error
    ... How much space do you have allocated for shadow copies? ... and exchange backup at the same time, you get a conflict like this. ... Task Category: Database Header Validation ... Keywords: Classic ...
    (microsoft.public.exchange.admin)
  • RE: Backups have Shadow Copy Problems
    ... with volume Shadow Copy error 800423f4. ... You back up data from a volume that contains a Microsoft SQL Server ... The recovery model of the SQL Server database is configured to use an ... It just ensures backup will continue without reporting the error. ...
    (microsoft.public.windows.server.sbs)
  • RE: Schedual NtBackup not working after I used UPHClean
    ... If the NTBackup process hangs in "Preparing to backup using shadow ... >normal, but when the Volume Shadow Copy service starts, NTBackup hangs. ...
    (microsoft.public.windows.server.sbs)
  • RE: vssadmin list volumes Error 0x8000ffff
    ... VSS and NTbackup do not work normally. ... The last node of the registry key path will vary for each volume on the ... Backup Logs. ... | vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool ...
    (microsoft.public.windows.server.sbs)
  • VSS errors logged ID 20 & ID 8 - vssadmin reports no writers
    ... We've had problems with VSS for a couple of weeks now. ... The company previously used Backup Exec, and after installing a new Dell PE ... NTBackup (I had used it at my previous location without a problem and always ... Volume shadow copy creation: Attempt 1. ...
    (microsoft.public.windows.server.sbs)