none
DPM VSS Errors RRS feed

  • Question

  • We have a PowerEdge R200 running Data Center Protection Manager 2010. It is protecting a PowerEdge R510 running Server 2008 R2 SP1 with the Hyper-V role installed. The Hyper-V server is running 16 guests. The guests are a mix of Server 2008 R2 Enterprise edition, Windows XP, Linux and Server 2003. All of the guests are being properly backed up except for one.

    We are having trouble with one VM in particular. This VM is running Windows Server 2003 SP2 and Exchange 2003 SP2. It was converted from a physical server to a virtual server a few weeks ago and now we want to protect the child partition by performing a Child Partition backup. The latest Integration tools are installed on both the Hyper-V Parent and Guest. The Hyper-V VSS requestor integration service is installed and running in the child partition. No dynamic disks are being used in the child partition.

    I have configured DPM to, "Backup using Child Partition", for this guest. When the backup runs, all Outlook clients loose connection to the server, the guest VMRC console freezes and the status of the Vm changes in the Hyper-V manager. The status reads, "Creating VSS Snapshot Set". The Console then says, "Restoring Connection". The Uptime also resets to "0" every day, after the backup takes place. It is like the VSS writer is having trouble backing up using the child partition for an online backup and is reverting to an offline Saved State Backup. There are no errors in the DPM console and the recovery points are being created successfully, but errors occur in the DPM server event log every day during the backup window. The errors are below in order of time.

    Does anybody know why this would be occurring?

    Computer: CVGHQDPM002

     

    Description:

     

    * Event Time: 19 Dec 2011 12:02:44 AM

     

     * Source: VSS

     

     * Event Log: Application

     

     * Type: Error Event

     

     * Event ID: 12310

     

     * Volume Shadow Copy Service error: The shadow copy could not be committed - operation timed out.

     

     Error context: DeviceIoControl(

     

    \\?\Volume{13f90043-1c2d-11df-b5a1-002219d5426c} - 0000000000000210,0x0053c010,0000000002494150,0,000000000248D0E0,4096,[0]).

     

     * Event Time: 19 Dec 2011 12:02:45 AM

     

     * Source: VSS

     

     * Event Log: Application

     

     * Type: Error Event

     

     * Event ID: 12298

     

     * Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume

     

    \\?\Volume{13f90043-1c2d-11df-b5a1-002219d5426c}\.

     

     The volume index in the shadow copy set is 0. Error details: Open[0x00000000], Flush[0x00000000], Release[0x80042314], OnRun[0x00000000].

     

     * Event Time: 19 Dec 2011 12:02:44 AM

     

     * Source: volsnap

     

     * Event Log: System

     

     * Type: Error Event

     

     * Event ID: 8

     

     * The flush and hold writes operation on volume C:\...icrosoft DPM\DPM\Volumes\Replica\SqlServerWriter\vol_bb67419e-c00a-470d-86e3-1eacfe472f43 timed out while waiting for a release writes command.

     

    Computer: CVGHQDPM002

     

    * Event Time: 19 Dec 2011 12:09:01 AM

     

    * Source: VSS

     

    Event Log: Application

     

    * Type: Warning Event

     

    * Event ID: 4003

     

    Operation:

     

       Gathering Writer Data

     

    Context:

     

       Writer Class Id: {0074a271-4f24-43e0-9ec7-28a44189cb80}

     

       Writer Name: DPM Writer

     

       Writer Instance ID: {ae22907b-3eba-49e8-bc4d-d1b664ce33a4}

     

    [The Event Message File(s) could not be found, so the event details above may be incomplete]

     

    * Event Time: 19 Dec 2011 12:10:38 AM

     

    * Source: VSS

     

    Event Log: Application

     

    * Type: Warning Event

     

    * Event ID: 4003

     

    Operation:

     

       Gathering Writer Data

     

    Context:

     

       Writer Class Id: {0074a271-4f24-43e0-9ec7-28a44189cb80}

     

       Writer Name: DPM Writer

     

       Writer Instance ID: {ae22907b-3eba-49e8-bc4d-d1b664ce33a4}

     

    [The Event Message File(s) could not be found, so the event details above may be incomplete]

     

     

     

    Computer: CVGHQDPM002

     

    Description:

     

    * Event Time: 19 Dec 2011 12:20:25 AM

     

    * Source: VSS

     

    Event Log: Application

     

    * Type: Warning Event

     

    * Event ID: 4003

     

    *

     

     

    Operation:

     

    Gathering Writer Data

     

     

    Context:

     

    Writer Class Id: {0074a271-4f24-43e0-9ec7-28a44189cb80}

     

    Writer Name: DPM Writer

     

    Writer Instance ID: {ae22907b-3eba-49e8-bc4d-d1b664ce33a4}

     

     

    [The Event Message File(s) could not be found, so the event details above may be incomplete]

     

     

    * Event Time: 19 Dec 2011 12:20:42 AM

     

    * Source: VSS

     

    * Event Log: Application

     

    * Type: Error Event

     

    * Event ID: 12305

     

    * Volume Shadow Copy Service error: Volume/disk not connected or not found.

     

    Error context: CreateFileW(

     

     

    \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2373\,0x80000000,0x00000003,...).

     

    * Event Time: 19 Dec 2011 12:20:42 AM

     

    * Source: VSS

     

    * Event Log: Application

     

    * Type: Error Event

     

    * Event ID: 12293

     

    * Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details PreFinalCommitSnapshots({7ba8ca05-bac8-4b4a-b345-aadde5e1e233}, 1) [hr = 0x80042308].

     

     

    Monday, December 19, 2011 4:15 PM

Answers

  • Thank you for the response!

     

    I was finally able to reboot the Exchange server and this resolved the issue. I have not received the errors since the the reboot and uptime of the server has not been reset.

     

    I'll check to see if that hotfix is installed on the server.

    Friday, December 23, 2011 1:58 AM

All replies

  • Apply this hotfix within the vm and then let me know if the issue is resolved http://support.microsoft.com/kb/833167

    Sean


    Sean
    Tuesday, December 20, 2011 11:38 PM
  • Thank you for the response!

     

    I was finally able to reboot the Exchange server and this resolved the issue. I have not received the errors since the the reboot and uptime of the server has not been reset.

     

    I'll check to see if that hotfix is installed on the server.

    Friday, December 23, 2011 1:58 AM