none
Unable to Add Items to Protection Groups RRS feed

  • Question

  • I'm using DPM 2012 R2 & while attempting to add items to a protection group

    (VMs/Volumes/States etc.), I'm getting the following error : 

    __________________________________________________________________________

    Modify Protection Group: <Name Here>
    Error 207: An unexpected error occured on the DPM server machine during a VSS operation.
    Error details : VssError: Shadow copying the specified volume is not supported (0x8004230C)

    Recommended Action: Retry the operation.

    Allocate replica for <Name Here>
    Error 207: An unexpected error occured on DPM server machine during a VSS operation.
    Error details : VssError: Shadow copying the specified voulme is not supported (0x8004230C)

    Recommended Action: Retry the operation.

    ___________________________________________________________________________

    All machines involved are running Windows Server 2012 R2.

    I am seeing this error for standalone hosts as well as for the cluster.

    Some of the things I've tried include the following : 

    1. Installing the latest updates on the concerned hosts/dpm server
    2. Checking if the VSS, MSVMM and DPM Services are running (they're using the Local System account)
    3. Performing the following to list applicable volumes and listing out status of providers/writers : 
        vssadmin list writers/provider/volumes
        Restarted the concerned machines quite a few times & there are no errors at the provider/writer level.

        All the volumes are listed as aplicable for VSS.

    4. Executing Shadow Copies from the volumes on the hosts directly & reverting - was also able to create Windows Server Backups for the System State on each of the hosts.
    5. The disks presented to DPM have around 10TB Unallocated & the protection 
        groups are set to automatically grow the allocated space.


    Tuesday, June 10, 2014 4:12 AM

All replies

  • Hi,

    The problem seems to be on the DPM Server while trying to configure shadow copy storage for the new replica volume created when adding a new data source.

    I would concentrate efforts on the DPM storage pool disks.  How many disks are in the storage pool and were any added lately ?

    Can you run get-dpmdisk from DPM powershell - then run diskpart.exe - then list disk and show me the results.


    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, June 10, 2014 10:01 PM
    Moderator
  • Hi Mike,

    The results are as follows : 

    get-dpmdisk

    Name  DiskStatus  NtDiskId  TotalCapacityLabel UnallocatedSpaceLabel DiskTypeLab
    WDC WD20EARX-00P... Healthy      3             1863 GB                0 GB        Basic
    MSFT Virtual HD ... Healthy       5             8335 GB             6811 GB       Dynamic
    Microsoft Storag... Healthy       4             7449 GB             4316 GB       Dynamic

    diskpart.exe followed by list disk

    Microsoft DiskPart version 6.3.9600

    Copyright (C) 1999-2013 Microsoft Corporation.
    On computer: HG

    DISKPART> list disk

      Disk ###  Status                Size           Free     Dyn     Gpt
      --------  -------------             -------         -------        ---      ---
      Disk 0         Online            73 GB             0 B
      Disk 3         Online        1863 GB             0 B
      Disk 4         Online        7450 GB     4316 GB          *        *
      Disk 5         Online               8 TB     6811 GB          *        *

    Thanks,
    Rishi

    Wednesday, June 11, 2014 9:10 PM
  • Hi,

    OK - nothing out of place there. Lets see if we can duplicate the error outside of DPM.

    1) Using windows disk management - make two new simple volumes of 10GB each, one on each disk (4 and 5) and assign them drive letters G: and H: or other available drive letters.

    2) From an administrative command prompt run the following command.

    VSSADMIN ADD SHADOWSTORAGE /ON=H: /FOR=G:
    VSSADMIN ADD SHADOWSTORAGE /ON=G: /FOR=H:

    3) Run diskshadow.exe - then issue the following commands.

    Set Verbose on
    add volume G:
    Create  (wait for shadow copy to get created)
    delete shadows volume G:

    4) Repeat but see if we can make shadowcopy for H:

    Add volume H:
    Create (wait for shadow copy to get created)
    Delete shadows volume H:

    5) Delete the G: and H: volumes in disk management.

    Let me know the results.


    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.

    Wednesday, June 11, 2014 9:44 PM
    Moderator
  • Hi Mike,

    I created two volumes (I: and J:) & ran the commands as shown below:

    ____________________________________________________________________________________

    Adding associations

    PS C:\Windows\system32> vssadmin add shadowstorage /on=I: /for=J: /maxsize=unbounded
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Successfully added the shadow copy storage association
    PS C:\Windows\system32> vssadmin add shadowstorage /on=J: /for=I: /maxsize=unbounded
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Successfully added the shadow copy storage association

    Create & delete shadows on volume I:

    DISKSHADOW> Set Verbose On

    DISKSHADOW> add volume I:

    DISKSHADOW> create
    Excluding writer "Shadow Copy Optimization Writer", because all of its components have been excluded.
    Excluding writer "Dedup Writer", because all of its components have been excluded.
    Excluding writer "BITS Writer", because all of its components have been excluded.
    Component "\TasksStore" from writer "Task Scheduler Writer" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\WriterMetadataStore" from writer "VSS Metadata Store Writer" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\PerformanceCounters" from writer "Performance Counters Writer" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\System Files" from writer "System Writer" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\Win32 Services Files" from writer "System Writer" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\BCD\BCD" from writer "ASR Writer" is excluded from backup,
    because it requires volume  which is not in the shadow copy set.
    Component "\aeb91e8d-56dc-45ca-abe4-079cd4fc747d" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VS
    S Writer\vol_a3409587-aa29-42fb-9a4a-2ae35f0b2497\ which is not in the shadow copy set.
    Component "\5752b13f-9e9c-41a0-b07e-0a832cc2672a" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\$Recycle.Bin\S-1-5-21-1390887109-539995910-1985184860-1106\$RB800JH\ which is not in the s
    hadow copy set.
    Component "\98633769-9452-4e0e-879a-0f3b8d96ec58" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VS
    S Writer\vol_bc4567b3-b831-425b-b6d8-0a67bf36e9f9\ which is not in the shadow copy set.
    Component "\304c17f9-3015-4bfb-83c0-1ad392b4d679" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VS
    S Writer\vol_a6c20085-feaf-41ef-a5a0-8738dfa95372\ which is not in the shadow copy set.
    Component "\d2bdcbbb-6c5f-41db-aa3f-24e024a91f87" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VS
    S Writer\vol_5f47ebbf-e8d3-4e63-80eb-f4ce4092322d\ which is not in the shadow copy set.
    Component "\00fd5035-b4f6-4d13-9989-3c1257dbb207" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\File System\vol_e187
    7e8a-79bf-4751-b76e-5776dfffbd68\ which is not in the shadow copy set.
    Component "\8f92e304-57b8-4a2a-bacf-5088906a77cc" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Non VSS Datasource W
    riter\vol_0c4f8fc4-6189-4cd1-aa01-b312bfd9f47a\ which is not in the shadow copy set.
    Component "\8cadb791-711e-4918-a1f8-53e63a129bee" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\File System\vol_8d20
    289a-5d96-4f2d-b40d-fadc3fa96ecd\ which is not in the shadow copy set.
    Component "\af8b1a0c-8ed3-443e-90e0-5e565a02355f" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\$Recycle.Bin\S-1-5-21-1390887109-539995910-1985184860-1106\$RIUUUV6\ which is not in the s
    hadow copy set.
    Component "\3d5fc8f9-b065-45d6-b04e-7f7c00582140" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VS
    S Writer\vol_c9b9a16a-5d7b-4611-8c80-1824d08bc284\ which is not in the shadow copy set.
    Component "\5e31870a-2e13-49b5-913f-83716a89aa16" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\$Recycle.Bin\S-1-5-21-1390887109-539995910-1985184860-1106\$RZ727AO\ which is not in the s
    hadow copy set.
    Component "\3ec5a685-0441-4380-9167-997241bdafbe" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Non VSS Datasource W
    riter\vol_0c4f8fc4-6189-4cd1-aa01-b312bfd9f47a\ which is not in the shadow copy set.
    Component "\afdf2295-f758-406b-8ef0-9b183d08c32d" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\SqlServerWriter\vol_
    54af1de0-f008-4271-9fc2-db2dd3203329\ which is not in the shadow copy set.
    Component "\eb74f3f3-ee1e-485e-946e-9f05acf59723" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VS
    S Writer\vol_2dd8a2cd-d3d3-4974-81d6-e9c0909bc4bd\ which is not in the shadow copy set.
    Component "\44ca95fe-720a-4e86-af61-a0cf232be367" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Non VSS Datasource W
    riter\vol_0c4f8fc4-6189-4cd1-aa01-b312bfd9f47a\ which is not in the shadow copy set.
    Component "\81354ce1-63e6-473e-994d-aaa3cf19dfcd" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\File System\vol_6d8d
    c1ca-e7f7-4d98-8dba-4867241d3670\ which is not in the shadow copy set.
    Component "\5ae78654-500d-40a2-9bdd-b211817c67df" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\File System\vol_6c70
    bacc-df8e-4dd8-859b-dfc52b6a8aab\ which is not in the shadow copy set.
    Component "\05831590-0cfc-46ad-84db-c4fee8a17b09" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VS
    S Writer\vol_6c239bc2-f7c5-49c7-b3ad-fd6f3b873d06\ which is not in the shadow copy set.
    Component "\a3622ae5-200c-460d-b6a1-cef50d140678" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VS
    S Writer\vol_6e216d9e-f33c-4270-ac30-732bc7c19990\ which is not in the shadow copy set.
    Component "\1925762f-1c5b-4628-8c3c-d87d5a75cf56" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\$Recycle.Bin\S-1-5-21-1390887109-539995910-1985184860-1106\$RIUUUV6\ which is not in the s
    hadow copy set.
    Component "\a66ce633-0e0f-4557-9fbc-dd510bcfc677" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VS
    S Writer\vol_f36e265a-d054-4319-8d9b-fca78ea32659\ which is not in the shadow copy set.
    Component "\eec15c52-da00-43c4-bb30-de133aab6f1e" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VS
    S Writer\vol_6c401a8a-0074-4a79-8a99-204ac8430a29\ which is not in the shadow copy set.
    Component "\55a79680-1ccb-48ea-824c-f2c7e15746a1" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\File System\vol_c843
    2680-608c-47c6-bf85-932b2088bf39\ which is not in the shadow copy set.
    Component "\8cc556ad-202a-44cd-b923-f5732cf90593" from writer "DPM Writer" is excluded from backup,
    because it requires volume C:\Program Files\Microsoft System Center 2012 R2\DPM\DPM\Volumes\Replica\Microsoft Hyper-V VS
    S Writer\vol_85b024b7-4530-4b65-9873-6e8c47551a89\ which is not in the shadow copy set.
    Component "\HG\master" from writer "SqlServerWriter" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\HG\model" from writer "SqlServerWriter" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\HG\msdb" from writer "SqlServerWriter" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\HG\ReportServer" from writer "SqlServerWriter" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\HG\ReportServerTempDB" from writer "SqlServerWriter" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\HG\DPMDB_HG" from writer "SqlServerWriter" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\WMI" from writer "WMI Writer" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\Registry" from writer "Registry Writer" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\COM+ REGDB" from writer "COM+ REGDB Writer" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    Component "\Host Component" from writer "Microsoft Hyper-V VSS Writer" is excluded from backup,
    because it requires volume C:\ which is not in the shadow copy set.
    The writer "Task Scheduler Writer" is now entirely excluded from the backup,
    because it does not contain any components that can be included.
    The writer "VSS Metadata Store Writer" is now entirely excluded from the backup,
    because it does not contain any components that can be included.
    The writer "Performance Counters Writer" is now entirely excluded from the backup,
    because it does not contain any components that can be included.
    The writer "System Writer" is now entirely excluded from the backup,
    because it does not contain any components that can be included.
    The writer "ASR Writer" is now entirely excluded from the backup because the top-level
    non selectable component "\BCD\BCD" is excluded.
    The writer "DPM Writer" is now entirely excluded from the backup because the top-level
    non selectable component "\8f92e304-57b8-4a2a-bacf-5088906a77cc" is excluded.
    The writer "SqlServerWriter" is now entirely excluded from the backup,
    because it does not contain any components that can be included.
    The writer "WMI Writer" is now entirely excluded from the backup,
    because it does not contain any components that can be included.
    The writer "Registry Writer" is now entirely excluded from the backup,
    because it does not contain any components that can be included.
    The writer "COM+ REGDB Writer" is now entirely excluded from the backup,
    because it does not contain any components that can be included.
    The writer "Microsoft Hyper-V VSS Writer" is now entirely excluded from the backup,
    because it does not contain any components that can be included.

    Alias VSS_SHADOW_1 for shadow ID {51c7129d-c3b8-4f7e-8ced-b561b3fdd1b1} set as environment variable.
    Alias VSS_SHADOW_SET for shadow set ID {f4ac2fd0-35e2-4b89-ad1c-a06d67a1c31b} set as environment variable.
    Inserted file Manifest.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file BCDocument.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM0.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM1.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM2.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM3.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM4.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM5.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM6.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM7.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM8.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM9.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM10.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM11.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM12.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file WM13.xml into .cab file 2014-12-06_22-17-07_HG.cab
    Inserted file DisBCBD.tmp into .cab file 2014-12-06_22-17-07_HG.cab

    Querying all shadow copies with the shadow copy set ID {f4ac2fd0-35e2-4b89-ad1c-a06d67a1c31b}

            * Shadow copy ID = {51c7129d-c3b8-4f7e-8ced-b561b3fdd1b1}               %VSS_SHADOW_1%
                    - Shadow copy set: {f4ac2fd0-35e2-4b89-ad1c-a06d67a1c31b}       %VSS_SHADOW_SET%
                    - Original count of shadow copies = 1
                    - Original volume name: \\?\Volume{6b9a7d35-f1a4-11e3-80fb-1c7ee510b236}\ [I:\]
                    - Creation time: 12/06/2014 10:17:06 a.m.
                    - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy164
                    - Originating machine: <DPM Server>
                    - Service machine: <DPM Server>
                    - Not exposed
                    - Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
                    - Attributes:  Auto_Release Differential

    Number of shadow copies listed: 1

    DISKSHADOW> delete shadows volume I:
    Deleting shadow copy {51c7129d-c3b8-4f7e-8ced-b561b3fdd1b1} on volume \\?\Volume{6b9a7d35-f1a4-11e3-80fb-1c7ee510b236}\
    from provider {b5946137-7b9f-4925-af80-51abd60b20d5} [Attributes: 0x00020000]...

    Number of shadow copies deleted: 1

    Create & delete shadows on volume J:

    DISKSHADOW> add volume J:
    A RESET is required to perform this operation.

    DISKSHADOW> reset

    DISKSHADOW> add volume J:

    DISKSHADOW> create
    Alias VSS_SHADOW_1 for shadow ID {6ebb40cc-8488-4b2c-af22-33af65345173} set as environment variable.
    Alias VSS_SHADOW_SET for shadow set ID {f20eb7c8-183d-43eb-b140-a192e2059bb1} set as environment variable.

    Querying all shadow copies with the shadow copy set ID {f20eb7c8-183d-43eb-b140-a192e2059bb1}

            * Shadow copy ID = {6ebb40cc-8488-4b2c-af22-33af65345173}               %VSS_SHADOW_1%
                    - Shadow copy set: {f20eb7c8-183d-43eb-b140-a192e2059bb1}       %VSS_SHADOW_SET%
                    - Original count of shadow copies = 1
                    - Original volume name: \\?\Volume{6b9a7d3e-f1a4-11e3-80fb-1c7ee510b236}\ [J:\]
                    - Creation time: 12/06/2014 10:22:55 a.m.
                    - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy165
                    - Originating machine: <DPM Server>
                    - Service machine: <DPM Server>
                    - Not exposed
                    - Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}
                    - Attributes:  Auto_Release Differential

    Number of shadow copies listed: 1

    DISKSHADOW> delete shadows volume J:
    Deleting shadow copy {6ebb40cc-8488-4b2c-af22-33af65345173} on volume \\?\Volume{6b9a7d3e-f1a4-11e3-80fb-1c7ee510b236}\
    from provider {b5946137-7b9f-4925-af80-51abd60b20d5} [Attributes: 0x00020000]...

    Number of shadow copies deleted: 1

    Wednesday, June 11, 2014 10:33 PM
  • Hi,

    OK - That all worked and those are basically the same steps that DPM does when you add a new data source to an existing or new protection group.  It makes two new volumes, adds VSS shadowstorage - creates an initial replica, then makes a VSS shadow copy.  So I'm at a loss as to why VSS is throwing that error when DPM does the work.


    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.

    Wednesday, June 11, 2014 10:47 PM
    Moderator
  • Hi Mike,

    It seems like the errors are thrown for the first shadow copy but any subsequent ones work without errors.

    I'm still getting the same error in DPM though - might have to re-pave the machine.

    Thanks,

    Rishi

    Wednesday, June 11, 2014 11:01 PM
  • I was getting error 207 0x8004230c on a brand new install.

    It was a brand new build with one 4 drive storage spaces parity array (4 x 3TB drives) and two stand alone hitachi 4TB drives.

    The fix for me was to remove the Hitachi drives when setting up my initial protection groups.

    The clue was found here: https://social.technet.microsoft.com/Forums/en-US/8dd187fb-d32c-482c-a784-448ad0209523/trouble-with-two-storage-pools?forum=dpmstorage

    It would appear DPM isn't smart enough yet to create protection groups across DPM storage that has a mix of 512 and 4K (http://msdn.microsoft.com/en-us/library/windows/desktop/hh848035(v=vs.85).aspx) disks.


    -=Chris

    Friday, November 14, 2014 5:50 PM