Rules to Better Data Protection Manager (DPM)

Hold on a second! How would you like to view this content?
Just the title! A brief blurb! Gimme everything!
  1. Do you know why to use Data Protection Manager (DPM)?

    Every company needs a business continuity and disaster recover plan. DPM is a robust backup solution used in many enterprises it can give you piece of mind knowing that your data is backed up, safe and easily restorable. It allows for backing up of:​

    • Hyper-V 
    • Physical Machines
    • Application Aware Backups
      • Exchange
      • SQL
      • SharePoint

    It also allows for the storage over many platforms:

    • Disk
    • Tape
    • Cloud​
  2. Do you know the best way to install DPM?

    ​It might make sense in your environment to install a DPM Server inside a Virtual Machine. While it is supported by Microsoft, there are a few limitations you need to be aware of.
    • The Hyper-V role cannot be installed on the DPM server when it has been virtualized. This prevents you doing item level restores from inside Hyper-V virtual machines
    • You are unable to use hardware tape libraries inside the Virtual Machine. You are still able to use iSCSI or Virtual Tape libraries though
    • ​Storage of your backups should not be on the SAN where you are running all of your servers

    Further to this, it is also recommend that you use iSCSI or Pass-Through disks if you are going to be using DPM inside a Virtual Machine. Using VHD’s in the storage pool is going to give you poor performance.

    WARNING: Although Microsoft recommend running the latest OS (being Windows Server 2019 and DPM 2019). SSW recommends Windows Server 2012 R2 with DPM 2019. 

    The reason for this is currently there are some known issues with the use of ReFS files structure in current versions of DPM (2016/2019). When installed on Windows Server 2016 and 2019 ReFS is used as default and there is no option given to use another file structure. The issues are causing backups to take exceptionally long times and in a lot of cases failing. E.g:

    • Exchange VM taking 100+ hours to backup and then failing when running Windows 2016 and DPM 2016
    • Exchange VM taking <3 hours to backup when running Windows 2012 R2 and DPM 2019

    Microsoft have released many updates to fix ReFS but people are still seeing issues, so it is recommended until this is resolved to continue operating DPM on Windows Server 2012 R2 as it allows you to continue using NTFS which is working without issues.​

    Related link: https://social.technet.microsoft.com/Forums/en-US/7e4e4da4-1168-46cd-900f-9ca2bc364d5a/dpm-2016-mbs-performance-downward-spiral​

  3. Do you setup SharePoint backups in the correct order?

    DPM is great for backing up SharePoint data, but when you select to back up the SharePoint role of a server, DPM will only backup the SharePoint_Config database and the content databases, which is less than ideal.
    To back up the SharePoint Server properly in DPM:

    1. Create a new Protection Group, for our example we will call it SharePoint Protection
    2. In the new Protection Group, add protection for the for the SharePoint role on your SharePoint server:

      Notice that SharePoint protection only selects the SharePoint_Config and Content databases.
      Notice that SharePoint protection only selects the SharePoint_Config and Content databases.
    3. Now browse to the SQL Server and add the entire SharePoint SQL Instance to the SharePoint Protection group. You will notice that you are unable to select some of the databases, as they are already being protected by SharePoint role protection.

      Ensure you back up the remaining databases in the SharePoint SQL Instance
      Ensure you back up the remaining databases in the SharePoint SQL Instance

    After following these steps you will have full protection of your SharePoint databases.