Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
Since Compressing Data getting DPM has run out of free in DPM 2007

Beantwortet Since Compressing Data getting DPM has run out of free in DPM 2007

  • Monday, March 04, 2013 1:42 PM
     
     
    Sign In to Vote
    0

    I needed more room on our main W2k8 64-bit VMare files server disk E: so I compressed the disk.  Now I keep getting errors.  See below.

    Keeps saying Recovery Point Volume Threshold Exceeded, so I incrementally increased that from 40GB to 140GB.  I also increased the Replica Volume from 350GB to 600GB to no effect.  Data size calculated is about 365GB.  Windows Explorer says Disk E: is 394GB with 305 Free now.

    The two disk arrays are at 48% & 42% Unallocated down from 54% before I started adding space to DPM 2007.

    This doesn't make any sense as it was working perfectly beofre I compressed the files.  Now I have more free space and less disk space than before.

    Should I uncheck the compress files box?  Or is there a better option?

    Here are the two recurring errors:

    Event Type: Error
    Event Source: DPM-EM
    Event Category: None
    Event ID: 1
    Date:  3/2/2013
    Time:  3:04:26 PM
    User:  N/A
    Computer: DPMServer
    Description:

    The replica of E:\ on Protected ServerProtected Server is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3163)
    DPM has run out of free space on the recovery point volume and will fail synchronization for E:\ on Protected Server in order to prevent existing recovery points from being deleted. (ID: 30195)


    DPM ID: 2^|^DPMServer^|^Replica inconsistent^|^DPM^|^Backup^|^Protected Server^|^b256f78b-914b-4c59-9f79-b22bfc40baa6

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    ERROR 2
    Event Type: Error
    Event Source: DPM-EM
    Event Category: None
    Event ID: 2
    Date:  3/1/2013
    Time:  3:47:29 PM
    User:  N/A
    Computer: DPMServer
    Description:

    The replica of E:\ on Protected Server is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. (ID: 3163)
    DPM has run out of free space on the recovery point volume and will fail synchronization for E:\ on Protected Server in order to prevent existing recovery points from being deleted. (ID: 30195)


    DPM ID: 2^|^DPMServer^|^Replica inconsistent^|^DPM^|^Backup^|^Protected Server^|^1925b0f4-c467-4a64-ad3a-c7b6a9dfe269

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Peter Jam

     

All Replies

  • Monday, March 04, 2013 6:48 PM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hi,

    The errors really do makes sense once you understand how Volume Shadow Copy Service (VSS) works to maintain previous versions of files.  Yes, you compressed all the data on the protected volume to save space, and indeed that will save the equivalent space on the DPM replica, but at the expense of needing more space on the recovery point volume.  As new data is written to new free space exposed when the replica was compressed, VSS needs to save the old blocks that represented the data that was not compressed, so in the event you need to do a recovery of the uncompressed data, it can.   This vss process is called Copy-on-write (COW) and only copies changed blocks to the shadow copy when it's about to be overwritten by new data.  This includes free space that at one time represented data that is in a valid shadow copy.  The only way to avoid the recovery point volume bloat would be to stop protection of the volume and delete replica, and re-protect the volume in an already compressed state, or reduce the retention period so it only includes recovery points after the date the data was compressed. That way VSS does not need to do COW for files when they were not compressed. 

    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, March 05, 2013 1:33 PM
     
     
    Sign In to Vote
    0

    Thanks for the explanation Mike.  As always you are a huge help.

    Peter Jam

    Mike,

    I stopped protection on that Group and it was removed.  Created a new one and it is giving me the same error almost immediately.  Did I miss something?


    • Edited by pjamme Wednesday, March 06, 2013 2:38 PM spelling
    •  
     
  • Thursday, March 07, 2013 3:19 PM
     
     
    Sign In to Vote
    0

    Mike,

    sorry I unmarked as answer since i am getting same errors.  What else do i need to do please?

    Peter Jam

    Mike,

    I did not go far enough.  I increased the Recovery Point Volume once again and finally gave it enough.  See Details below:

    Status: OK
    Replica path: Click to view details
    Latest recovery point: 3/8/2013 8:00:11 PM
    Oldest recovery point: 2/1/2013 6:00:12 PM
    Total recovery points: 17
    Disk allocation: Replica volume: 600.36 GB allocated, 338.64 GB used | Recovery point volume: 200.00 GB allocated, 170.53 GB used

    • Edited by pjamme Saturday, March 09, 2013 5:27 PM addendum
    •