DPM failed to synchronize changes for SQL Server 2005 database because the snapshot volume did not have sufficient storage space to hold the churn on the protected computer
Monday, August 02, 2010 1:24 PM
I have been backing up the DPMDB for all of my primary DPM servers a couple of secondary DPM servers on a 90-day retention window and recently one of the DPMDB's for one primary server quit backing up due to the following error message:
DPM failed to synchronize changes for SQL Server 2005 database KEN-PROD-BS002\MS$DPM2007$\DPMDB on KEN-PROD-BS002.aarons.aaronrents.com because the snapshot volume did not have sufficient storage space to hold the churn on the protected computer (ID 30115 Details: Unknown error (0x8004231f) (0x8004231F))
This error is occurring not only on DPMDB but all database backups for the same primary (SQL backups for master, model, msdb, etc). These SQL backups have been running with no issue for over 90 days to disk until just now. At first I thought this error might be a disk space issue on the recovery point volume or maybe even the replica volume so I increased the size of both for all the SQL backups for the one primary to 250% the current used space and that made no difference. The primary DPM server itself is not pressed for space at all on any volume (including where DPM and SQL are installed on D:\)
I did notice in the eventlog's on the primary DPM server that a volsnap error occurs at the same time the DPM job fails so I am sure it is related to the issue but I am not sure what exactly it means:
When preparing a new volume shadow copy for volume D:, the shadow copy storage on volume D:\...9dd-4b8a-ae98-466c310de4be could not be located in non-critical space. Consider using a shadow copy storage volume that does not have any shadow copies.
Monday, August 02, 2010 2:39 PMWell oddly enough these started working this morning on a 2nd or 3rd retry. These have failed for 3 days with many, many retries so I am not sure why all of a sudden it worked. I did not make any changes other than rebooting the primary server but a couple of retries after the reboot failed as well so any ideas would be appreciated but otherwise problem resolved.
- Marked As Answer by Jeff Mathe Monday, August 02, 2010 2:39 PM
Tuesday, August 03, 2010 7:50 AMModerator
I suspect that the issue is related to the maximum size of the Volume Shadow Copy.
To change the maximum size of the VS Copy:
1. Right click the "D:" volume of the primary DPM server and choose Properties.
2. On the Shadow Copies tab, click the Settings button.
3. Change the maximum size to a larger one.