=====
SymptomsWhen using System Center Data Protection Manager 2007 (DPM) to protect system state you may notice one or more of the following symptoms:
Symptom 1: While trying to add system state for a protected server to a protection group, the system state icon to check is not present under the expanded protected server. The result is that you cannot protect the systemstate for that server.
Symptom 2: While protecting system state of a protected server you receive the following errors in the ALERTS and FAILED JOBS on the DPM 2007 server:
ALERT
=====
Affected area: Computer\SystemState
Occurred since:
Description: Recovery point creation jobs for System State Computer\SystemState on Protected_server.domain.com have been failing. The number of failed recovery point
creation jobs = 1. (ID 3114)
Failed to create the System State backup. (ID 30214 Details: Internal error code: 0x809909FB)
Recommended action: Check the event log on the protected computer ComputerName.domain.com and fix any errors reported.
Create a recovery point...
Resolution: To dismiss the alert, click below
Inactivate alert
FAILED JOB
==========
Type: Recovery point
Status: Failed
Description: Failed to create the System State backup. (ID 30214 Details: Internal error code: 0x809909FB)
End time:
Start time:
Time elapsed:
Data transferred: 0 MB
Cluster node -
Recovery Point Type Express Full
Source details: Computer\SystemState
Protection group: Systemstate
NOTE: KB949779 adds support for Windows 2008 systemstate backup so this may also occur while protecting systemstate for Windows 2008 servers.
Symptom 3: If you try to perform a systemstate backup on a Windows Server 2008 based DPM 2007 server using wbadmin, or if you are protecting system state of a Windows Server 2008 based DPM 2007 server from a secondary DPM server, the system state backup fail and the VSS dpmwriter will be in a failed state:
ErrorID: 4212: DpmWriter service encountered an error during PrepareBackup as more
than one component is selected for backup in the same snapshot set.
The event viewer entry:
Log Name: Microsoft-Windows-Backup
Source: Microsoft-Windows-Backup
Date:
Event ID: 9
Task Category: None
Level: Error
Description:
Backup started at '{49a5bd25-7a2c-4835-8153-a42a2c262210}' failed as Volume Shadow
copy operation failed for backup volumes with following error code '2155348129'.
Symptom 4:
Windows Server 2008 system state backup fails with this error:
"DPM cannot create a backup because Windows Server Backup on the protected computer encountered an error (WSB: 546 WSB Error:: 0x807800B4) ID 30229 Details: Internal Error 0x809909FB"
Resolution
Solution to Symptom 1: Make sure the PSdataSourceConfig.xml file is located in the DPM agent install path under the datasources folder (e.g. C:\Microsoft Data Protection Manager\DPM\datasources). The Agent Install path can be checked in the registry under:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Setup\InstallPath
If the file is in the wrong path or missing all together, you can copy it from another protected server and male sure it's in the correct location.
See
http://technet.microsoft.com/en-us/library/bb809015.aspx
for more details.
Solution to Symptom 2:
PROTECTED SERVER APPLICATION EVENT LOG
Windows Server 2003:
Event Type: Error
Event Source: NTBackup
Event Category: None
Event ID: 8019
Date:
Time:
User: N/A
Computer:
Description:
End Operation: Warnings or errors were encountered.
Consult the backup report for more details.
Windows Server 2008:
Log Name: Microsoft-Windows-Backup
Source: Microsoft-Windows-Backup
Date:
Event ID: 5
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer:
Description:
Backup started at '<time/date>' failed with following error code '2155348165'.
Windows Server 2003 ntbackup logs for system state backup are stored in C:\Document and Settings\Default User\Application Data\Microsoft\NTBackup.
The Log files will be named BackupXX.log, Backup01.log, and so forth, look at the time stamp of the file to determine which one matches the failed job.
Windows Server 2008 backup logs are located in the %windir%\logs\WindowsServerBackup folder
The log files are named "SystemStatebackup date time.log"
You can view these logs to help resolve any issues that occur with the system state backup.
EXAMPLE NTBACKUP BACKUP01.LOG
Backup Status
Operation: Backup
Active backup destination: File
Media name: "FS01.bkf created 12/24/2007 at 8:01 PM"
Volume shadow copy creation: Attempt 1.
Error returned while creating the volume shadow copy:0x80042316.
Error returned while creating the volume shadow copy:80042316
Aborting Backup.
----------------------
The operation did not successfully complete.
----------------------
Where 0x80042316 = VSS_E_SNAPSHOT_SET_IN_PROGRESS - so it looks like in this case if you had systemstate in a separate protection group, you would need to modify the protection group to start the systemstate recovery point at an earlier or later time so the snapshot creation does not collide with other protection groups that may be protecting data on the O.S. (C:) drive.
NOTE: This is a known issue and is fixed in Windows 2008 R2.
NOTE: If you are protecting both systemstate and data on the Windows O.S. (C:) drive or any other volumes that contain systemstate component in the same protection group, then DPM should schedule the recovery points for each data source seperately and not try to backup the data on C: and Systemstate at the same time. Look to see if DPM incorrectly scheduled / started the systemstate backup job before the job for protected data on C: completed. As a workaround - If you cannot get the systemstate to succeed, try putting it in its own protection group and schedule it for an earlier time than the original protection group it came from.
NOTE: If the DPM server itself gets into a condition that it cannot create a snapshot for the same reason, recovery point jobs will fail with this error:
Cannot create a recovery point because another recovery point creation is in progress. (ID 211)
SOLUTION:
See this article, but perhaps SQL backups are scheduled first, thus causing systemstate backup to fail.
971807 - Data Protection Manager 2007 jobs to protect a SQL Server may remain in synchronizing ...
If you use vssadmin list shadows, you may or may not see shadow copies of type:Backup. To stop any in progress snapshots, try stopping and restarting the Volume Shadow Copy service. If that does not work, reboot the system, then retry your DPM job.
If the error in the backup report is different than 0x80042316 then follow the steps below:
TROUBLESHOOTING
1) Check the application and system event log of the Protected server to see why the backup of systemstate failed.
a. Look for VSS or Volsnap errors in the application and system event logs respectively.
b. For Windows 2008 - look in BOTH the Windows Logs - Application and the Services Logs-Microsoft-Backup-Operational event log.
2) For Windows 2008 - Make sure Windows 2008 has the backup feature installed.
3) VSS errors are one of the most common problems encountered, see the following article for WSB troubleshooting
http://blogs.technet.com/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backu...
4) Make sure there is enough free space on C: volume to hold the PS_SERVER_NAME.BKF file located in the C:\DPM_SYSTEM_STATE folder.
Note: For Windows Server 2008 the systemstate is stored in drive:\WindowsImagebackup folder. For Windows 2008, systemstate backup may require ~10GB or MORE free space.
5) You can move (redirect) the systemstate backup location to another volume by modifying the \Microsoft Data Protection Manager\DPM\datasources\PSdataSourceConfig.xml file. See http://technet.microsoft.com/en-us/library/bb809015.aspx for details.
If you move it, unprotect systemstate then re-protect it on the DPM server so it re-reads the new location from the PSdataSourceConfig.xml file.
6) Try to make a manual systemstate backup and troubleshoot any errors that occur.
On Windows Server 2003, DPM executes the C:\program file\Microsoft Data Protection Manager\DPM\bin\DPMSystemstatebackup.cmd <drive-letter:> - you can run that and see what errors occur. On Windows Server 2008, DPM executes the C:\program file\Microsoft Data Protection Manager\DPM\bin\LHSystemstatebackup.cmd <drive-letter:> - you can run that and see what errors occur.
For Windows Server 2008 you can also try the following native backup command. The backup logs are located in C:\Windows\logs\WindowsServerBackup folder.
Wbadmin start systemstatebackup -backuptarget:c:
NOTE: Shadow copies for the target drive cannot be redirected to another volume or backup will not start. Use vssadmin list shadowstorage to confirm.
7) For Windows Server 2008, make sure this registry setting is enabled (which is added when a DPM agent is installed to a Windows 2008 server).
HKLM\Systtem\CurrentControlSet\Services\wbengine\SystemStateBackup\AllowSSBToAnyVolume:REG_DWORD:0x1
Once a manual NTBACKUP / Wbadmin Systemstate backups work, re-try the creating the recovery point.
Solution to Symptom 3:
A) Find out the writer ID of the writer you wish to exclude. You can use vssadmin list writers for this. The DPM writer is always going to be: {0074a271-4f24-43e0-9ec7-28a44189cb80}.
B) Open regedit, the under the regkey "HKLM\Software\Microsoft\Windows NT\CurrentVersion\SPP", create a new MULTI_SZ-value with the name
"DisabledWriters".
C) Enter the writer guid with braces {0074a271-4f24-43e0-9ec7-28a44189cb80} as the value.
D) Shut down wbengine service if it’s running.
E) Try to create a new systemstate backup now, it should succeed.
Solution to Symptom 4:
This issue is typically caused by locating the system state component on a volume larger than 2 TB in size. All volumes containing a system state component like Sysvol and AD must be located on a volume less that 2TB in order to be protected.
=====
J.C. Hornbeck | System Center Knowledge Engineer
The App-V Team blog:
http://blogs.technet.com/appv/
The WSUS Support Team blog:
http://blogs.technet.com/sus/
The SCMDM Support Team blog:
http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog:
http://blogs.technet.com/configurationmgr/
The OpsMgr Support Team blog:
http://blogs.technet.com/operationsmgr/
The SCVMM Team blog:
http://blogs.technet.com/scvmm/
The MED-V Team blog:
http://blogs.technet.com/medv/
The DPM Team blog:
http://blogs.technet.com/dpm/
The OOB Support Team blog:
http://blogs.technet.com/oob/
The Opalis Team blog:
http://blogs.technet.com/opalis
