Quick post about a small problem you may ran into from time to time!
Error Messages
You recevie the following error message in the DPM-console:
DPM failed to synchronize changes for SQL Server 2012 database SQL01\SQLIN03\DPMDB on SQL01.contoso.local because the snapshot volume did not have sufficient storage space to hold the churn on the protected computer (ID 30115 Details: VssError:Insufficient storage available to create either the shadow copy storage file or other shadow copy data.(0x8004231F))And the following event is logged in the System log on the protected server:
When preparing a new volume shadow copy for volume E:, the shadow copy storage on volume C:\...\{volume-GUID} could not be located in non-critical space. Consider using a shadow copy storage volume that does not have any shadow copies.Cause
The Shadow Copy Service is allocated limited amount of space which is not sufficient for the creation of a snap.
Solution
- Right click the volume (in my case E:) in disk management.
- Go to the Shadow Copies-tab and located the volume (still E:) in the "Select a volume"list.
- Press settings and increase the "Maximum size:" or configure it with "No limit:"
- Press OK in the Settings-window and re run your job from the DPM-console
Best Regards
Markus Eliasson
Great solution. In my scenario, it was local DPM storage that was complaining (I use file shares as target storage for unsupported workloads). I was getting the Snapshot error, but we don't use Hyper-V on our DPM server.
ReplyDeleteFor our install, Server 2016, there are no controls for Shadow Copy on the volume. I thought this was strange. Turns out, on the C drive you can select each drive and set VSS properties there.
Hope this helps someone!
Also check the drives of the SQL Server machine. In my case it was the C drive on my SQL server that was corrupt. I ran Checkdisk and DPM was happy after that.
ReplyDelete