none
DPM 2010 inconsistent replica all the time RRS feed

  • Question

  • We are having problems to backup a Windows 2003 server using DPM 2010. We are backup about 40GB data but the replica will just use 90MB. it always reports the replica is inconsistent.

    The latest update rollup 7 has been applied on the server and the agent version is 3.0.8195.

    The error log from the agent:

    0AC8 05A4 08/22 14:03:59.084 31 vsssnapshotrequestor.cpp(347) [00C11BF0] 47775C23-0B59-4DB7-BD74-F099CF0E5090 NORMAL CVssSnapshotRequestor::AddVolumeForSnapshot [00C11BF0]

    0AC8 05A4 08/22 14:03:59.084 31 vsssnapshotrequestor.cpp(379) 47775C23-0B59-4DB7-BD74-F099CF0E5090 NORMAL ssLocalVolumeGuid = [\?\Volume{b71e166a-6ff3-11db-83e4-0015c5e9b572}], ssClusterVolGuid=[\?\Volume{b71e166a-6ff3-11db-83e4-0015c5e9b572}]

    0AC8 05A4 08/22 14:03:59.084 31 vsssnapshotrequestor.cpp(390) [00C11BF0] 47775C23-0B59-4DB7-BD74-F099CF0E5090 NORMAL CVssSnapshotRequestor: AddVolumeForSnapshot - Marked volume \?\Volume{b71e166a-6ff3-11db-83e4-0015c5e9b572}\ to be snapshot

    0AC8 05A4 08/22 14:03:59.084 31 vsssnapshotrequestor.cpp(424) [00C11BF0] 47775C23-0B59-4DB7-BD74-F099CF0E5090 NORMAL CVssSnapshotRequestor::StartPrepareForBackup [00C11BF0]

    0AC8 05A4 08/22 14:03:59.131 31 vssbaserequestor.cpp(1070) [00C11BF0] 47775C23-0B59-4DB7-BD74-F099CF0E5090 NORMAL CVssBaseRequestor::StartGatherWriterStatus [00C11BF0]

    0AC8 05A4 08/22 14:04:00.131 31 vssbaserequestor.cpp(946) [00C11BF0] NORMAL QueryStatus returned 0x4230a, Releasing VssAsync [0071A280]

    0AC8 05A4 08/22 14:04:00.131 31 vssbaserequestor.cpp(1103) [00C11BF0] NORMAL CVssBaseRequestor::CheckWriterStatus [00C11BF0]

    0AC8 05A4 08/22 14:04:00.131 31 filterwrapper.cpp(68) [0262FC5C] NORMAL CreateBitmap: {74B5196F-3934-4588-B613-8618A80CA453}

    0AC8 05A4 08/22 14:04:00.131 31 vsssnapshotrequestor.cpp(529) [00C11BF0] NORMAL CVssSnapshotRequestor::StartDoSnapshot [00C11BF0]

    0AC8 05A4 08/22 14:04:26.215 31 vssbaserequestor.cpp(946) [00C11BF0] NORMAL QueryStatus returned 0x8004231f, Releasing VssAsync [00719710]

    0AC8 05A4 08/22 14:04:26.215 31 vastatemachineutils.cpp(406) [00BF4D28] WARNING Failed: Hr: = [0x8004231f] : F: lVal : hrStatus

    0AC8 05A4 08/22 14:04:26.215 05 fsmstate.cpp(167) [00BB3AF0] WARNING Failed: Hr: = [0x8004231f] : F: lVal : pTransition->Execute(pEvent)

    0AC8 05A4 08/22 14:04:26.215 05 genericfsm.cpp(225) [00BB32A0] WARNING Failed: Hr: = [0x8004231f] : F: lVal : m_pCurrentState->SendEvent(pEvent, pNextState)

    0AC8 05A4 08/22 14:04:26.215 05 fsmtransition.cpp(111) [006FFC40] WARNING Failed: Hr: = [0x8004231f] HasEventErrorCode: completion: 0x27, signature: 0xaabbcc00

    0AC8 05A4 08/22 14:04:26.215 31 aasubtask.cpp(1373) [00BB5FE8] WARNING Updating task status with hr: 8004231f8x, dls error code:30014

    0AC8 1600 08/22 14:04:26.215 31 aasubtask.cpp(913) [00BB5FE8] WARNING

    0AC8 1600 08/22 14:04:26.215 31 aasubtask.cpp(913) [00BB5FE8] WARNING 0\?\Volume{b71e166a-6ff3-11db-83e4-0015c5e9b572}\D:\

    0AC8 1600 08/22 14:04:26.215 03 runtime.cpp(1599) [00B7F808] FATAL Subtask failure, sending status response XML=[

    0AC8 1600 08/22 14:04:26.215 03 runtime.cpp(1599) [00B7F808] FATAL 0\?\Volume{b71e166a-6ff3-11db-83e4-0015c5e9b572}\D:\

    0AC8 1600 08/22 14:04:26.215 03 runtime.cpp(1599) [00B7F808] FATAL ]

    Thank a lot

    Regard RW

    Thursday, August 22, 2013 2:37 PM

Answers

  • Hi,

    ErrorCode: 0x8004231F (-2147212513): VSS_E_INSUFFICIENT_STORAGE: Insufficient storage available to create either the shadow copy storage file or other shadow copy data.

    On the protected server, run the following from an administrative command prompt - That will list the shadowcopy storage associations and size.

      C:\>VSSADMIN LIST SHADOWSTORAGE

    You can adjust the size using:

    c:\>vssadmin resize shadowstorage /for=D: /on=D: /maxsize=XXGB  (where xx = number of GB to reserve)

    HELP OUTPUT
    =========

    Resize ShadowStorage /For=ForVolumeSpec /On=OnVolumeSpec /MaxSize=MaxSizeSpec
        - Resizes the maximum size for a shadow copy storage association between
        ForVolumeSpec and OnVolumeSpec.  Resizing the storage association may cause shadow
        copies to disappear.  As certain shadow copies are deleted, the shadow copy storage
        space will then shrink.  If MaxSizeSpec is set to the value UNBOUNDED, the shadow copy
        storage space will be unlimited.  MaxSizeSpec can be specified in bytes or as a
        percentage of the ForVolumeSpec storage volume.  For byte level specification,
        MaxSizeSpec must be 320MB or greater and accepts the following suffixes: KB, MB, GB, TB,
        PB and EB.  Also, B, K, M, G, T, P, and E are acceptable suffixes.  To specify MaxSizeSpec
        as percentage, use the % character as the suffix to the numeric value.  If a suffix is not
        supplied, MaxSizeSpec is in bytes.

        Example Usage:  vssadmin Resize ShadowStorage /For=C: /On=D: /MaxSize=900MB
                        vssadmin Resize ShadowStorage /For=C: /On=D: /MaxSize=UNBOUNDED
                        vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=20%


    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, August 22, 2013 2:51 PM
    Moderator

All replies

  • We are having problems to backup a Windows 2003 server using DPM 2010. We are backup about 40GB data but the replica will just use 90MB. it always reports the replica is inconsistent.

    The latest update rollup 7 has been applied on the server and the agent version is 3.0.8195.

    The error log from the agent:

    0AC8 05A4 08/22 14:03:59.084 31 vsssnapshotrequestor.cpp(347) [00C11BF0] 47775C23-0B59-4DB7-BD74-F099CF0E5090 NORMAL CVssSnapshotRequestor::AddVolumeForSnapshot [00C11BF0]

    0AC8 05A4 08/22 14:03:59.084 31 vsssnapshotrequestor.cpp(379) 47775C23-0B59-4DB7-BD74-F099CF0E5090 NORMAL ssLocalVolumeGuid = [\?\Volume{b71e166a-6ff3-11db-83e4-0015c5e9b572}], ssClusterVolGuid=[\?\Volume{b71e166a-6ff3-11db-83e4-0015c5e9b572}]

    0AC8 05A4 08/22 14:03:59.084 31 vsssnapshotrequestor.cpp(390) [00C11BF0] 47775C23-0B59-4DB7-BD74-F099CF0E5090 NORMAL CVssSnapshotRequestor: AddVolumeForSnapshot - Marked volume \?\Volume{b71e166a-6ff3-11db-83e4-0015c5e9b572}\ to be snapshot

    0AC8 05A4 08/22 14:03:59.084 31 vsssnapshotrequestor.cpp(424) [00C11BF0] 47775C23-0B59-4DB7-BD74-F099CF0E5090 NORMAL CVssSnapshotRequestor::StartPrepareForBackup [00C11BF0]

    0AC8 05A4 08/22 14:03:59.131 31 vssbaserequestor.cpp(1070) [00C11BF0] 47775C23-0B59-4DB7-BD74-F099CF0E5090 NORMAL CVssBaseRequestor::StartGatherWriterStatus [00C11BF0]

    0AC8 05A4 08/22 14:04:00.131 31 vssbaserequestor.cpp(946) [00C11BF0] NORMAL QueryStatus returned 0x4230a, Releasing VssAsync [0071A280]

    0AC8 05A4 08/22 14:04:00.131 31 vssbaserequestor.cpp(1103) [00C11BF0] NORMAL CVssBaseRequestor::CheckWriterStatus [00C11BF0]

    0AC8 05A4 08/22 14:04:00.131 31 filterwrapper.cpp(68) [0262FC5C] NORMAL CreateBitmap: {74B5196F-3934-4588-B613-8618A80CA453}

    0AC8 05A4 08/22 14:04:00.131 31 vsssnapshotrequestor.cpp(529) [00C11BF0] NORMAL CVssSnapshotRequestor::StartDoSnapshot [00C11BF0]

    0AC8 05A4 08/22 14:04:26.215 31 vssbaserequestor.cpp(946) [00C11BF0] NORMAL QueryStatus returned 0x8004231f, Releasing VssAsync [00719710]

    0AC8 05A4 08/22 14:04:26.215 31 vastatemachineutils.cpp(406) [00BF4D28] WARNING Failed: Hr: = [0x8004231f] : F: lVal : hrStatus

    0AC8 05A4 08/22 14:04:26.215 05 fsmstate.cpp(167) [00BB3AF0] WARNING Failed: Hr: = [0x8004231f] : F: lVal : pTransition->Execute(pEvent)

    0AC8 05A4 08/22 14:04:26.215 05 genericfsm.cpp(225) [00BB32A0] WARNING Failed: Hr: = [0x8004231f] : F: lVal : m_pCurrentState->SendEvent(pEvent, pNextState)

    0AC8 05A4 08/22 14:04:26.215 05 fsmtransition.cpp(111) [006FFC40] WARNING Failed: Hr: = [0x8004231f] HasEventErrorCode: completion: 0x27, signature: 0xaabbcc00

    0AC8 05A4 08/22 14:04:26.215 31 aasubtask.cpp(1373) [00BB5FE8] WARNING Updating task status with hr: 8004231f8x, dls error code:30014

    0AC8 1600 08/22 14:04:26.215 31 aasubtask.cpp(913) [00BB5FE8] WARNING

    0AC8 1600 08/22 14:04:26.215 31 aasubtask.cpp(913) [00BB5FE8] WARNING 0\?\Volume{b71e166a-6ff3-11db-83e4-0015c5e9b572}\D:\

    0AC8 1600 08/22 14:04:26.215 03 runtime.cpp(1599) [00B7F808] FATAL Subtask failure, sending status response XML=[

    0AC8 1600 08/22 14:04:26.215 03 runtime.cpp(1599) [00B7F808] FATAL 0\?\Volume{b71e166a-6ff3-11db-83e4-0015c5e9b572}\D:\

    0AC8 1600 08/22 14:04:26.215 03 runtime.cpp(1599) [00B7F808] FATAL ]

    Thank a lot

    Regard RW

    Thursday, August 22, 2013 2:38 PM
  • Hi,

    ErrorCode: 0x8004231F (-2147212513): VSS_E_INSUFFICIENT_STORAGE: Insufficient storage available to create either the shadow copy storage file or other shadow copy data.

    On the protected server, run the following from an administrative command prompt - That will list the shadowcopy storage associations and size.

      C:\>VSSADMIN LIST SHADOWSTORAGE

    You can adjust the size using:

    c:\>vssadmin resize shadowstorage /for=D: /on=D: /maxsize=XXGB  (where xx = number of GB to reserve)

    HELP OUTPUT
    =========

    Resize ShadowStorage /For=ForVolumeSpec /On=OnVolumeSpec /MaxSize=MaxSizeSpec
        - Resizes the maximum size for a shadow copy storage association between
        ForVolumeSpec and OnVolumeSpec.  Resizing the storage association may cause shadow
        copies to disappear.  As certain shadow copies are deleted, the shadow copy storage
        space will then shrink.  If MaxSizeSpec is set to the value UNBOUNDED, the shadow copy
        storage space will be unlimited.  MaxSizeSpec can be specified in bytes or as a
        percentage of the ForVolumeSpec storage volume.  For byte level specification,
        MaxSizeSpec must be 320MB or greater and accepts the following suffixes: KB, MB, GB, TB,
        PB and EB.  Also, B, K, M, G, T, P, and E are acceptable suffixes.  To specify MaxSizeSpec
        as percentage, use the % character as the suffix to the numeric value.  If a suffix is not
        supplied, MaxSizeSpec is in bytes.

        Example Usage:  vssadmin Resize ShadowStorage /For=C: /On=D: /MaxSize=900MB
                        vssadmin Resize ShadowStorage /For=C: /On=D: /MaxSize=UNBOUNDED
                        vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=20%


    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, August 22, 2013 2:51 PM
    Moderator
  • Hi Mike,

    You are a star. It has been fixed. I have got another one


    0C18	1F94	08/27	08:46:19.782	05	defaultsubtask.cpp(680)	[00B8DA68]	8D24DA18-7781-4064-BC68-A739FC1074A7	WARNING	Failed: Hr: = [0x809909b0] : F: lVal : CommandReceived(pAgentOvl)
    0C18	1F94	08/27	08:47:21.394	29	radefaultsubtask.cpp(356)	[00B8DA68]	8D24DA18-7781-4064-BC68-A739FC1074A7	WARNING	Failed: Hr: = [0x809909b0] : CRADefaultSubTask: WorkitemID does not exist, {3A4ADC12-3564-485A-9D3A-6FA8DD684BAB}
    0C18	1F94	08/27	08:47:21.394	05	defaultsubtask.cpp(459)	[00B8DA68]	8D24DA18-7781-4064-BC68-A739FC1074A7	WARNING	Failed: Hr: = [0x809909b0] : F: lVal : CommandReceivedSpecific(pCommand, pOvl)
    0C18	1F94	08/27	08:47:21.394	03	runtime.cpp(1599)	[006FCFC0]	8D24DA18-7781-4064-BC68-A739FC1074A7	FATAL	Subtask failure, sending status response XML=[<?xml version="1.0"?>
    0C18	1F94	08/27	08:47:21.394	03	runtime.cpp(1599)	[006FCFC0]	8D24DA18-7781-4064-BC68-A739FC1074A7	FATAL	<Status xmlns="http://schemas.microsoft.com/2003/dls/StatusMessages.xsd" StatusCode="-2137454160" Reason="Error" CommandID="RAGetWorkItemInfo" CommandInstanceID="cae0e398-f66b-4421-8c50-9007a9252b5f" GuidWorkItem="3a4adc12-3564-485a-9d3a-6fa8dd684bab" TETaskInstanceID="8d24da18-7781-4064-bc68-a739fc1074a7"><ErrorInfo xmlns="http://schemas.microsoft.com/2003/dls/GenericAgentStatus.xsd" ErrorCode="2001" DetailedCode="-2137454160" DetailedSource="2"><Parameter Name="AgentTargetServer" Value="xxxxx"/></ErrorInfo></Status>
    0C18	1F94	08/27	08:47:21.394	03	runtime.cpp(1599)	[006FCFC0]	8D24DA18-7781-4064-BC68-A739FC1074A7	FATAL	]

    Any ideas?

    Thanks a lot

    Regards Ruoyu



    • Edited by rw888 Tuesday, August 27, 2013 10:12 AM
    Tuesday, August 27, 2013 10:11 AM
  • Please open a new thread and include the failed job details.  The above is just telling me that the work item does not exist which is normal after the fact, the failure occurred earlier.

    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.

    Tuesday, August 27, 2013 2:28 PM
    Moderator
  • Mike

    I am having the same problem but with DPM 2012 R2.

    If I use the VSSADMIN LIST SHADOWSTORAGE I see there are two shadow copies. One for each of the drives I want backed up. Presumable the DPM software set this up automatically as I did not create them.

    My problem is that the output from the VSSADMIN LIST SHADOWSTORAGE command shows max storage space as quite low. As follows

    Shadow Copy Storage association
       For volume: (E:)\\?\Volume{1f3f295b-ff75-11e2-940a-00155d003906}\
       Shadow Copy Storage volume: (E:)\\?\Volume{1f3f295b-ff75-11e2-940a-00155d003906}\
       Used Shadow Copy Storage space: 12.3 MB (0%)
       Allocated Shadow Copy Storage space: 640 MB (0%)
       Maximum Shadow Copy Storage space: 12.7 GB (10%)

    Shadow Copy Storage association
       For volume: (C:)\\?\Volume{b1daa434-98b5-11e2-93e7-806e6f6e6963}\
       Shadow Copy Storage volume: (C:)\\?\Volume{b1daa434-98b5-11e2-93e7-806e6f6e6963}\
       Used Shadow Copy Storage space: 243 MB (0%)
       Allocated Shadow Copy Storage space: 697 MB (0%)
       Maximum Shadow Copy Storage space: 10.2 GB (10%)

    Do I need to manually change the size or does DPM 2012 R2 manage this for me?


    prd

    Thursday, July 10, 2014 1:29 PM
  • Hi prd,

    DPM does not assign shadow copy storage space on protected servers, so it must have been setup by someone else.

    You can safely delete the associations and then defaults will be used.

    vssadmin delete shadowstorage /for=C: /on=C:
    Vssadmin delete shadowstorage /for=E: /on=E:

    Alternately - you can resize it to give it more space.

    vssadmin Resize ShadowStorage /For=C: /On=C: /MaxSize=80%
    vssadmin Resize ShadowStorage /For=E: /On=E: /MaxSize=80%

     

    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, July 10, 2014 4:26 PM
    Moderator