none
Replica creation fails, error 30115 RRS feed

  • Question

  • I have recently set up a HA cluster with three VMs. Two of them are backing up without issue, one has not been able to create a replica. The process starts, and fails shortly after with the below error. If I try to run a consistency check, I receive the same error (ID 30115). I have tried removing the VM from the protection group and deleting data, then re-adding (same result). Any suggestions would be greatly appreciated.

    Type: Replica creation
    Status: Failed
    Description: DPM failed to synchronize changes for Microsoft Hyper-V \Backup Using Child Partition Snapshot\[vmname] on [vmname].[clustername].[domain].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))
    More information
    End time: 12/19/2012 7:18:02 AM
    Start time: 12/19/2012 7:17:37 AM
    Time elapsed: 00:00:24
    Data transferred: 0 MB
    Cluster node [clusternode].[domain].local
    Source details: \Backup Using Child Partition Snapshot\[vmname]
    Protection group: Protection Group 1

    Wednesday, December 19, 2012 12:41 PM

Answers

  • I believe I have found the cause. \\?\Volume{3c6b38e5-46e3-11e2-b14a-00155d01c900}\ (the only volume that didn't contain the VHDs of the other VMs) was 100 GB in size and contained a (roughly) 100 GB VHD, meaning there are practically no free space. I'm guessing that this is what was preventing snapshots from being created. It wasn't an issue before the volume was converted to a CSV, but seems to be now. I extended the volume by 10 GB to a total of 110 GB, tried creating the replica, and data is transferring now. I don't want to speak too soon, but this is a great sign. I'll post back to confirm once it has completed.
    • Marked as answer by av_tiuk Thursday, December 20, 2012 6:11 PM
    Thursday, December 20, 2012 1:43 PM

All replies

  • Hi,

    The problem seems to be on the protected server, run vssadmin list shadowstorage and check what volume is configured to hold the snapshot for the volume that guest is located while the backup is taken.  Also make sure that the maximumshadow copy storage space is sized large enough.

    SAMPLE OUTPUT:

    Shadow Copy Storage association
       For volume: (C:)\\?\Volume{05abb0d3-759d-11e0-a684-806e6f6e6963}\
       Shadow Copy Storage volume: (C:)\\?\Volume{05abb0d3-759d-11e0-a684-806e6f6e6963}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: 27.856 GB (10%)

    To change it use the following:

    PS C:\Program Files\Microsoft DPM\DPM\bin> vssadmin resize shadowstorage /for=c: /on=c: /maxsize=40GB
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Successfully resized the shadow copy storage association


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, December 20, 2012 12:24 AM
    Moderator
  • C:\>vssadmin list shadowstorage
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2005 Microsoft Corp.

    Shadow Copy Storage association
       For volume: (\\?\Volume{edc90405-44a8-11e2-aa63-806e6f6e6963}\)\\?\Volume{edc
    90405-44a8-11e2-aa63-806e6f6e6963}\
       Shadow Copy Storage volume: (\\?\Volume{edc90405-44a8-11e2-aa63-806e6f6e6963}
    \)\\?\Volume{edc90405-44a8-11e2-aa63-806e6f6e6963}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: 32 MB (32%)

    Shadow Copy Storage association
       For volume: (\\?\Volume{3c6b38e5-46e3-11e2-b14a-00155d01c900}\)\\?\Volume{3c6
    b38e5-46e3-11e2-b14a-00155d01c900}\
       Shadow Copy Storage volume: (\\?\Volume{3c6b38e5-46e3-11e2-b14a-00155d01c900}
    \)\\?\Volume{3c6b38e5-46e3-11e2-b14a-00155d01c900}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: UNBOUNDED (100%)

    Shadow Copy Storage association
       For volume: (\\?\Volume{78e12ea9-a7eb-4431-90ba-4a2dd71a02da}\)\\?\Volume{78e
    12ea9-a7eb-4431-90ba-4a2dd71a02da}\
       Shadow Copy Storage volume: (\\?\Volume{78e12ea9-a7eb-4431-90ba-4a2dd71a02da}
    \)\\?\Volume{78e12ea9-a7eb-4431-90ba-4a2dd71a02da}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: UNBOUNDED (718861458%)

    Shadow Copy Storage association
       For volume: (C:)\\?\Volume{edc90406-44a8-11e2-aa63-806e6f6e6963}\
       Shadow Copy Storage volume: (C:)\\?\Volume{edc90406-44a8-11e2-aa63-806e6f6e69
    63}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: 27.927 GB (10%)

    \\?\Volume{edc90405-44a8-11e2-aa63-806e6f6e6963}\ is System Reserved

    \\?\Volume{3c6b38e5-46e3-11e2-b14a-00155d01c900}\ is a CSV that holds a VHD that is attached to a VM (the one that won't backup) via the SCSI controller

    \\?\Volume{78e12ea9-a7eb-4431-90ba-4a2dd71a02da}\ is a CSV that contains the boot and data VHDs for all three VMs. Two out of these three are backing up successfully.

    As you can see, both volumes that contain VHDs have unbounded shadowstorage. I am unsure where to proceed from here.

    Thursday, December 20, 2012 12:28 PM
  • I believe I have found the cause. \\?\Volume{3c6b38e5-46e3-11e2-b14a-00155d01c900}\ (the only volume that didn't contain the VHDs of the other VMs) was 100 GB in size and contained a (roughly) 100 GB VHD, meaning there are practically no free space. I'm guessing that this is what was preventing snapshots from being created. It wasn't an issue before the volume was converted to a CSV, but seems to be now. I extended the volume by 10 GB to a total of 110 GB, tried creating the replica, and data is transferring now. I don't want to speak too soon, but this is a great sign. I'll post back to confirm once it has completed.
    • Marked as answer by av_tiuk Thursday, December 20, 2012 6:11 PM
    Thursday, December 20, 2012 1:43 PM
  • The replica creation finished successfully, looks like the volume being almost full was the cause (not enough free space for shadow copies).
    Thursday, December 20, 2012 6:12 PM