System Center Data Protection Manager 2007 cannot back up the system state if SQL databases are located on the system volume and logs are located on a separate volume

This article has been archived. It is offered "as is" and will no longer be updated.
You cannot set up a protection group within Microsoft System Center Data Protection Manager (DPM) 2007 to back up the system state of a SQL server. This problem occurs if the following conditions are all true:
  • The SQL server is installed.
  • The SQL databases are on the system volume.
  • The logs of the SQL server are on a different volume.
Additionally, the following events are logged in the Application log:

Event Type: Error
Event Source: NTBackup
Event Category: None
Event ID: 8019
Date: <date>
Time: <time>
User: N/A
Computer: <computer name>
Description:End Operation: Warnings or errors were encountered. Consult the backup report for more details.

Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 6005
Date: <date>
Time: <time>
User: N/A
Computer: <computer name>
Description:Sqllib error: Database %1 is stored on multiple volumes, only some of which are being shadowed.

Additionally, an error message that resembles the following is logged in the backup log:
Backup StatusOperation: BackupActive backup destination: FileMedia name: "<media name>"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:800423f0Aborting Backup.
This problem occurs because of a flaw in the Ntbackup.exe application.
To work around this problem, use either of the following workarounds.

Workaround 1

Move the SQL logs to the same volume as the SQL databases. Or, move the SQL database and logs to a volume that is not the boot volume.

Workaround 2

DPM uses only a .cmd file to start the backup of the system state. The batch file name is C:\Program Files\Microsoft Data Protection Manager\DPM\bin\DPMSystemStateBackup.cmd.

You can change the third line in this the batch file so that it resembles the following:
Start /WAIT %SystemRoot%\system32\Ntbackup.exe backup systemstate "@c:\MySelection.bks" /F %1
This line references a .bks file that tells NTBackup what to include in this backup. In this example, the .bks file is C:\MySelection.bks. The contents of this .bks file should resemble C:\Test.txtSystemState.
Note Here, C:\Test.txt is an example .txt file. You can name this file whatever you want.

We do not recommend that you create this .bks file by using notepad. It is a binary file. To create this file, follow these steps:
  1. In NTBackup, schedule the job.
  2. Find the .bks file.
  3. Copy this file to a known location.
  4. Cancel the NTBackup job.
  5. Change the C:\MySelection.bks file to point to the .bks file that you made.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Article ID: 953871 - Last Review: 01/15/2015 19:01:51 - Revision: 2.0

  • Microsoft System Center Data Protection Manager 2007
  • kbnosurvey kbarchive kberrmsg kbtshoot kbexpertiseinter kbprb KB953871