ID 30115: VssError: Insufficient storage available to create either the shadow copy storage file or other shadow copy data.(0x8004231F)

Hi folks,

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

Troubleshoot ID 30111: VssError: The specified object was not found

Hi folks,

Here's a quick solution how to fix the following error in DPM in a scenario where you have configured Online Snapshot-protection of a virtual machine:

The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError: The specified object was not found. (0x80042308))

Troubleshooting steps:

1. Verify that the virtual machine is not deleted in Hyper-V/VMM.
2. Modify the protection group where you configured protection for the virtual machine.
3. Expand your Hyper-V cluster and locate your virtal machine in the "Modify Group"-wizard.
4. Expand the virtual machine and make sure the checkbox for "Hyper-V\Online\ServerName" is checked.
5. Complete the "Modify Group"-wizard by clicking Next untill it updates the configuration.
6. When you succesfully have created a recovery point for the virtual machine; Stop the protection of the failing datasource.

Problem cause:

This problem will occur when a virtual machine gets clooned or deleted and then recreated again with the same name.

//Markus