none
Daily, Weekly, Monthly, Yearly backup routine?

    Question

  • Hi,

    We are using DPM 2012 to back up our data. Our policies require us to make daily backups to tape. Therefore we have configured our PGs to backup to tape daily, weekly, and monthly. Unfortunately this means we are unable to use the system to automatically create and keep track of our yearly backups.

    We could of course just manually designate one of the monthly’s to be a yearly backup, but I assume DPM will then mark the tapes as overdue when they expire and they'll then stay on the Tape Management report forever, which isn't ideal and will be slightly confusing for staff in the future.

    I could just create recovery points to tape manually (I don't know how this labels the tapes?) but it appears that you have to do this manually for each item within a protection group, and that would take a long time with all our items and protection groups.

    What's the best way to tackle this issue?

    Looking forward to your thoughts,
    Alex


    Alex

    Monday, September 03, 2012 7:30 AM

Answers

  • Hi Alex,

    As noted, DPM does not have provisions for more than three long term recovery goals, so you would need to sacrifice either the weekly or monthly goals to allow for a yearly goal.

    However, with a little work at the end of the year, you could do this.

    1) install the latest rollup fix http://support.microsoft.com/kb/2706783

    2) Looking at issue 8 - add that registry key to maintain original tape expiry goals as noted below.

    Issue 8

    Expiry dates for valid datasets that are already written to tape are changed when the retention range is changed during a protection group modification.

    For example, a protection group is configured for long-term tape recovery points with custom long-term recovery goals. Recovery Goal 1 has a smaller retention range than other recovery goals. In this configuration, if a protection group is changed to remove Recovery Goal 1 and to keep other recovery goals, the datasets that were created by using Recovery Goal 1 have their retention range changed to the retention range of the other recovery goals.

    To work around this problem, create the IsDatasetExpiryDateChangeInModifyPgAllowed DWORD under the following subkey, and then set its value to 0:


    HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MediaManager

    3) In December, AFTER the normally scheduled monthly backups complete, change the monthly goal to a yearly goal in all your protection groups.

    4) Run the powershell in the below forum link and manually run goal-3 (yearly) for all your protection groups.

    http://social.technet.microsoft.com/Forums/da/dpmtapebackuprecovery/thread/92e2bd66-d9cb-454b-83e2-455dd077c8b3

    That will make yearly tape for you.

    5) Change the recovery goal back to a Monthly recovery goal after the yearly backups complete.


    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, September 03, 2012 3:05 PM

All replies

  • Hi,

    you should be able to perform the following backup routines:

    - Short Term Protection on Tape: Will be used for your daily backups

    - Long Term Protection Tape : Will be used for weekly, monthly and yearly backups.


    Doing so will let you use the tapes for 4 backups schedule.

    Monday, September 03, 2012 8:42 AM
  • Hi Jeremy,

    Thanks for your response.

    We have to take our daily tapes offsite everyday, therefore to enable quick restores we do short term to disk.  Unfortunately this means your idea would not work for us.

    Alex


    Alex

    Monday, September 03, 2012 8:48 AM
  • Hi Alex,

    As noted, DPM does not have provisions for more than three long term recovery goals, so you would need to sacrifice either the weekly or monthly goals to allow for a yearly goal.

    However, with a little work at the end of the year, you could do this.

    1) install the latest rollup fix http://support.microsoft.com/kb/2706783

    2) Looking at issue 8 - add that registry key to maintain original tape expiry goals as noted below.

    Issue 8

    Expiry dates for valid datasets that are already written to tape are changed when the retention range is changed during a protection group modification.

    For example, a protection group is configured for long-term tape recovery points with custom long-term recovery goals. Recovery Goal 1 has a smaller retention range than other recovery goals. In this configuration, if a protection group is changed to remove Recovery Goal 1 and to keep other recovery goals, the datasets that were created by using Recovery Goal 1 have their retention range changed to the retention range of the other recovery goals.

    To work around this problem, create the IsDatasetExpiryDateChangeInModifyPgAllowed DWORD under the following subkey, and then set its value to 0:


    HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MediaManager

    3) In December, AFTER the normally scheduled monthly backups complete, change the monthly goal to a yearly goal in all your protection groups.

    4) Run the powershell in the below forum link and manually run goal-3 (yearly) for all your protection groups.

    http://social.technet.microsoft.com/Forums/da/dpmtapebackuprecovery/thread/92e2bd66-d9cb-454b-83e2-455dd077c8b3

    That will make yearly tape for you.

    5) Change the recovery goal back to a Monthly recovery goal after the yearly backups complete.


    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, September 03, 2012 3:05 PM
  • Looks good.  I'll give it a shot.

    Alex

    Tuesday, September 04, 2012 6:20 AM