DPM SP1: Error 2043

If you are running DPM 2006 SP1 and encounter error 2043, "insufficient shadow copy space", the alert details refer you to Knowledge Base (KB) article 922510. The product team is working to publish that KB article as soon as possible, but in the meantime, here are the instructions for resolving the issue:

In DPM 2006, when the amount of space required for shadow copies exceeded the allocated space, all shadow copies could be deleted without notification to the user. DPM SP1 will ensure that at least the latest shadow copy is retained and generate an alert to increase the disk allocation for shadow copies.

However, DPM will stop protection of the affected protection group member, and you must manually change the disk allocations and create a new shadow copy of the affected protection group member to continue protection.

To continue protection of the affected protection group member

1. In the Protection task area, select the protection group that contains the affected protection group member and then click Modify disk allocation.

2. In the Modify disk allocation dialog box, select the affected protection group member and then click Change.

3. Modify disk allocations for the protection group member as follows:

   • Increase the replica area to 150% of the size of the protected data.
   • Increase the shadow copy to 20% of the modified replica area.
     For example, if the protected data is 100 GB, increase the replica area to 150 GB and increase the shadow copy area to 30 GB.

4. In the Protection task area, obtain the replica path information for the affected protection group member from the Details pane.

5. Create a new shadow copy of the replica volume on the DPM server by running the following command:

   vssadmin create shadow /For=<<REPLICA point Mount>>

   The replica mount point is the replica path, truncated to the GUID. For example, when the replica directory path is:

   c:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FileServerName\E-1ed88a75-1b71-11da-b87c-806e6f6e6963\ReplicaDir\Test

   The resulting replica mount point is:

   c:\Program Files\Microsoft Data Protection Manager\DPM\Volumes\Replica\FileServerName\E-1ed88a75-1b71-11da-b87c-806e6f6e6963

6. Run Consistency Check.

Comments

• Anonymous
  January 01, 2003
  Tolico, I don't expect a patch for this issue. DPM V2 uses a different approach for managing shadow copies so this won't be a problem in V2.

• Anonymous
  January 01, 2003
  Thank you for publishing it. I checked the KB. It is unclear whether this behavior of DPM is considered a bug or not... Is the problem planned to be fixed? The most annoying part of the problem was that after increasing the disk allocation, I had to invoke vssadmin command by hand and perform a sync with consistency check. I think that once the disk allocation is adjusted, DPM should recover automatically. The step 5 of KB was not very much helpful to my case. It says the shadow copy area should be increased to 20% of the replica area. My replica area is 800GB and the shadow copy area had to be increased from 340GB to 360GB.

• Anonymous
  January 01, 2003
  I recently posted about an SP1 error that refers the user to a Knowledge Base article, KB 922510. Sometimes

• Anonymous
  January 01, 2003
  Glad you found it, and you're welcome!

• Anonymous
  December 28, 2006
  I was looking for KB922510 to resolve errors on my DPM... and this blog is the only resource I've found. Thank you for writing it. Hope the KB gets published soon.