none
Inactive protection in DPM RRS feed

  • Question

  • How do I shrink the recovery point volume from an agent which is present in inactive protection group?
    Monday, May 11, 2015 12:41 PM

Answers

  • Hi,

    You will need to use the Windows Diskpart.exe utility to manually shrink the recovery point volume.

    1) Under Inactive Protection  - Locate the data source you want to shrink the recovery point volume.

    2) Highlight the data source, then click on the "Click to view details" for the Replica path: - and copy the path into notepad.

    It will be in the form of the below:

    PS_server.contoso.com\User data   C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8\e96ce814-cda8-45ea-a797-f286aacb3473\Full

    Note the path to the replica volume:

       C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8    [This represents mounted volume path for the replica volume]


    3) Open a command prompt with administrative privilages

    4) Modify the properties of the window so it's  Screen buffer size is 9999 and it's Windows Size Width is 200.

    5) Run DISKPART.EXE - then LIST VOLUMES

    6) In the list Locate the Destination path C:\Program file\Microsoft DPM\DPM\DIFFAREA\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8  string from step two - make a note of the Volume # associated with the DIFFAREA.

    In the example below it is Volume 6

    EXAMPLE
    =======

    C:\Tools\IC>diskpart
    Microsoft DiskPart version 6.1.7600
    Copyright (C) 1999-2008 Microsoft Corporation.
    On computer: LC2-DPMLIB1

    DISKPART> list vol

      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 0         DPM-vol_3c2  NTFS   Simple        25 GB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\Microsoft Hyper-V VSS Writer\vol_3c2e337a-dc0a-45ce-9d3b-8410de4e4466\
      Volume 1         DPM-vol_3c2  NTFS   Simple       100 GB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Microsoft Hyper-V VSS Writer\vol_3c2e337a-dc0a-45ce-9d3b-8410de4e4466\
      Volume 2         DPM-vol_705  NTFS   Simple      7760 MB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\SqlServerWriter\vol_70595f52-1beb-40e1-bd25-b39ad3702d97\
      Volume 3         DPM-vol_705  NTFS   Simple        10 GB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\SqlServerWriter\vol_70595f52-1beb-40e1-bd25-b39ad3702d97\
      Volume 4     S   DPM-vol_7e2  NTFS   Simple      1030 MB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\File System\vol_7e21e4aa-bf4f-40b7-9a14-afd9a112aa43\
      Volume 5         DPM-vol_7e2  NTFS   Simple      1610 MB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\File System\vol_7e21e4aa-bf4f-40b7-9a14-afd9a112aa43\
      Volume 6         DPM-vol_571  NTFS   Simple        12 GB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\Non VSS Datasource Writer\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8\
      Volume 7     T   DPM-vol_571  NTFS   Simple        30 GB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8\
      Volume 8         DPM-vol_1f8  NTFS   Simple      3440 MB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\File System\vol_1f8883b9-8ef7-4b29-9422-fc12768f0646\
      Volume 9         DPM-vol_1f8  NTFS   Simple        26 GB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\File System\vol_1f8883b9-8ef7-4b29-9422-fc12768f0646\
      Volume 10    D                       DVD-ROM         0 B  No Media
      Volume 11    C   OSDisk       NTFS   Partition     66 GB  Healthy    Boot
      Volume 12    A   ACCESS       NTFS   Partition   5000 MB  Healthy
      Volume 13    E   New Volume   NTFS   Partition    161 GB  Healthy
      Volume 14    B   BDEDrive     NTFS   Partition    298 MB  Healthy    System


    DISKPART> sel vol 6      (select volume 6)

    Volume 6 is the selected volume.

    DISKPART> shrink querymax    (see how much space can me reclaimed)

    The maximum number of reclaimable bytes is:    9 GB (9948 MB)


    DISKPART> shrink   (try to shrink it)

    DiskPart successfully shrunk the volume by:  9 GB (9948 MB)

     


    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.


    Monday, May 11, 2015 5:16 PM
    Moderator
  • Hi,

    If a data source is in an active protection group, you can shrink the recovery point volume in the GUI by modifying disk allocation.  However once you stop protection and retain the replica, that data source will be placed in an inactive protection group and you no longer have the GUI option to modify disk allocation.  Because of this, you need to use the Windows Diskpart.exe utility to shrink it manually using the method I described above.


    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.

    • Marked as answer by PreethiC Wednesday, May 13, 2015 7:39 AM
    Tuesday, May 12, 2015 5:58 PM
    Moderator
  • Hi,

    Diskpart.exe is a windows utility and has no knowledge of what a volume is used for, so yes you can use if for any volume on a system.  With that said, if you shrink the replica volume, you run the risk of bloating the recovery point volume or in extreme cases losing all the shadow copies. This is because as you move files around on the replica VSS copy on write (COW) has to maintain the active snapshot and if the recovery point volume does not have enough free space to accommodate those writes you get unpredictable results.    f you are going to attempt to shrink the replica, do it before shrinking recovery point volume so it has plenty of free space to accommodate the COW. 


    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.

    • Marked as answer by PreethiC Thursday, May 14, 2015 2:18 PM
    Wednesday, May 13, 2015 2:19 PM
    Moderator
  • Hi,

    Shrink command uses the Windows Defrag engine to move files away from the back of the volume so the volume size can be reduced.  Certain files cannot be moved like NTFS metadata files.  If this is a Windows 2008 R2 or later system then the results of the Defrag will be logged in the application log and will show you the file that is preventing the shrink.


    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.

    • Marked as answer by PreethiC Tuesday, May 19, 2015 8:56 AM
    Monday, May 18, 2015 5:10 PM
    Moderator

All replies

  • Hi,

    You will need to use the Windows Diskpart.exe utility to manually shrink the recovery point volume.

    1) Under Inactive Protection  - Locate the data source you want to shrink the recovery point volume.

    2) Highlight the data source, then click on the "Click to view details" for the Replica path: - and copy the path into notepad.

    It will be in the form of the below:

    PS_server.contoso.com\User data   C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8\e96ce814-cda8-45ea-a797-f286aacb3473\Full

    Note the path to the replica volume:

       C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8    [This represents mounted volume path for the replica volume]


    3) Open a command prompt with administrative privilages

    4) Modify the properties of the window so it's  Screen buffer size is 9999 and it's Windows Size Width is 200.

    5) Run DISKPART.EXE - then LIST VOLUMES

    6) In the list Locate the Destination path C:\Program file\Microsoft DPM\DPM\DIFFAREA\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8  string from step two - make a note of the Volume # associated with the DIFFAREA.

    In the example below it is Volume 6

    EXAMPLE
    =======

    C:\Tools\IC>diskpart
    Microsoft DiskPart version 6.1.7600
    Copyright (C) 1999-2008 Microsoft Corporation.
    On computer: LC2-DPMLIB1

    DISKPART> list vol

      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
      ----------  ---  -----------  -----  ----------  -------  ---------  --------
      Volume 0         DPM-vol_3c2  NTFS   Simple        25 GB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\Microsoft Hyper-V VSS Writer\vol_3c2e337a-dc0a-45ce-9d3b-8410de4e4466\
      Volume 1         DPM-vol_3c2  NTFS   Simple       100 GB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Microsoft Hyper-V VSS Writer\vol_3c2e337a-dc0a-45ce-9d3b-8410de4e4466\
      Volume 2         DPM-vol_705  NTFS   Simple      7760 MB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\SqlServerWriter\vol_70595f52-1beb-40e1-bd25-b39ad3702d97\
      Volume 3         DPM-vol_705  NTFS   Simple        10 GB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\SqlServerWriter\vol_70595f52-1beb-40e1-bd25-b39ad3702d97\
      Volume 4     S   DPM-vol_7e2  NTFS   Simple      1030 MB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\File System\vol_7e21e4aa-bf4f-40b7-9a14-afd9a112aa43\
      Volume 5         DPM-vol_7e2  NTFS   Simple      1610 MB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\File System\vol_7e21e4aa-bf4f-40b7-9a14-afd9a112aa43\
      Volume 6         DPM-vol_571  NTFS   Simple        12 GB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\Non VSS Datasource Writer\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8\
      Volume 7     T   DPM-vol_571  NTFS   Simple        30 GB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\Non VSS Datasource Writer\vol_571ad355-e8b0-4fd8-be1d-766ccb7002a8\
      Volume 8         DPM-vol_1f8  NTFS   Simple      3440 MB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\DiffArea\File System\vol_1f8883b9-8ef7-4b29-9422-fc12768f0646\
      Volume 9         DPM-vol_1f8  NTFS   Simple        26 GB  Healthy
        C:\Program Files\Microsoft DPM\DPM\Volumes\Replica\File System\vol_1f8883b9-8ef7-4b29-9422-fc12768f0646\
      Volume 10    D                       DVD-ROM         0 B  No Media
      Volume 11    C   OSDisk       NTFS   Partition     66 GB  Healthy    Boot
      Volume 12    A   ACCESS       NTFS   Partition   5000 MB  Healthy
      Volume 13    E   New Volume   NTFS   Partition    161 GB  Healthy
      Volume 14    B   BDEDrive     NTFS   Partition    298 MB  Healthy    System


    DISKPART> sel vol 6      (select volume 6)

    Volume 6 is the selected volume.

    DISKPART> shrink querymax    (see how much space can me reclaimed)

    The maximum number of reclaimable bytes is:    9 GB (9948 MB)


    DISKPART> shrink   (try to shrink it)

    DiskPart successfully shrunk the volume by:  9 GB (9948 MB)

     


    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.


    Monday, May 11, 2015 5:16 PM
    Moderator
  • Hi Mike,

    Thanks a lot for your reply. I have a query, though. Does diskpart apply to agents in inactive protection group too? I mean, the agents that have been made inactive. It works for active agents as far as I know. Can you help me clear my doubt?

    Thanks and Regards,

    Preethi C


    Tuesday, May 12, 2015 2:38 PM
  • Hi,

    If a data source is in an active protection group, you can shrink the recovery point volume in the GUI by modifying disk allocation.  However once you stop protection and retain the replica, that data source will be placed in an inactive protection group and you no longer have the GUI option to modify disk allocation.  Because of this, you need to use the Windows Diskpart.exe utility to shrink it manually using the method I described above.


    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.

    • Marked as answer by PreethiC Wednesday, May 13, 2015 7:39 AM
    Tuesday, May 12, 2015 5:58 PM
    Moderator
  • Hi Mike,

    One more query. Does diskpart not apply only to the replica volume? Please, correct me if I am wrong.

    Thanks and Regards,

    Preethi C

    Wednesday, May 13, 2015 2:10 PM
  • Hi,

    Diskpart.exe is a windows utility and has no knowledge of what a volume is used for, so yes you can use if for any volume on a system.  With that said, if you shrink the replica volume, you run the risk of bloating the recovery point volume or in extreme cases losing all the shadow copies. This is because as you move files around on the replica VSS copy on write (COW) has to maintain the active snapshot and if the recovery point volume does not have enough free space to accommodate those writes you get unpredictable results.    f you are going to attempt to shrink the replica, do it before shrinking recovery point volume so it has plenty of free space to accommodate the COW. 


    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.

    • Marked as answer by PreethiC Thursday, May 14, 2015 2:18 PM
    Wednesday, May 13, 2015 2:19 PM
    Moderator
  • Hi Mike,

    Thanks a lot for the insight. It was really helpful.

    Preethi C

    Thursday, May 14, 2015 2:19 PM
  • Hi Mike,

    When I am trying to run the command "shrink querymax", it shows that maximumnumber of reclaimable bytes is 0 GB. Can you suggest me what needs to be done next?

    Thanks and Regards,

    Preethi C

    Friday, May 15, 2015 12:16 PM
  • Hi Mike,

    When I am trying to run the command "shrink querymax" for the inactive protection group, it shows that maximum number of reclaimable bytes is 0 GB. The allocated space in recovery point volume is 7.63 TB whereas the used space is around 6 TB.Can you suggest what needs to be done in order to reclaim the remaining space ?

    Thanks and Regards,

    Preethi C

    Friday, May 15, 2015 12:59 PM
  • Hi,

    Shrink command uses the Windows Defrag engine to move files away from the back of the volume so the volume size can be reduced.  Certain files cannot be moved like NTFS metadata files.  If this is a Windows 2008 R2 or later system then the results of the Defrag will be logged in the application log and will show you the file that is preventing the shrink.


    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.

    • Marked as answer by PreethiC Tuesday, May 19, 2015 8:56 AM
    Monday, May 18, 2015 5:10 PM
    Moderator
  • Hello,

    I got the following error description for replica inconsistent error :

    "Number of files skipped for synchronization due to errors has exceeded the maximum allowed limit of 100 files on this data source (ID 32538 Details: Internal error code: 0x809909FE)"

    And, the following recommended action :

    "Review the failure errors for individual files from the log file \\?\Volume{cb7882ff-1715-11e5-bac9-ac162d84ee1b}\682031db-5824-4146-9a74-6ef90a2d19a6\FailedFilesLog.txt and take appropriate action. If some files fail consistently, you can exclude the folders containing these files by modifying the protection group or moving the files to another location"

    However, when I tried to navigate to the volume mentioned above, I could not find it. Can you please suggest as to what needs to be done?

    Thanks and Regards,

    Preethi Nair


    • Edited by PreethiC Wednesday, July 1, 2015 7:52 AM
    Wednesday, July 1, 2015 7:52 AM
  • This post is off topic, please open a new post with your question.

    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, July 1, 2015 1:03 PM
    Moderator