Best Practices on High Availability of DPM RRS feed

  • Question

  • Hi,

    Kindly suggest on the high availability best practices and methods for High Availability of DPM.

    Monday, July 6, 2020 1:17 PM

All replies

  • Hi,

    To gain high availability in DPM, you first need to ensure that the DPM's storage is redundant, avoid any single-point of failures.

    For example:

    • If using a virtual DPM server, the virtual hard drives should be placed on scaled-out file servers (SOFS).
    • If you have multiple physical sites, you may have a storage system in each site and a storage replication between each sites. So if one site goes down completely, the other site can take over and provide full access to the storage.

    To make the DPM servers highly available, you should host the DPM database (SQL Server) on a failover cluster, this ensures that if one the database nodes goes down, you still have the DPM environment fully functional.

    Note: The reporting server cannot be high available.

    Then it comes down to the DPM servers themselves, if you for example have multiple sites you configure one DPM at the primary site which backup those data to disk. Then setup a secondary DPM server at the DR site to replicate changes from primary DPM server.

    This can be done without having multiple sites as well, but you need to make sure that the servers are not dependent of each other, they can also be standalone.

    So it depends really on your setup.

    For management, the DPM console can be installed on any computer and you can manage DPM from almost anywhere.

    Best regards,

    Blog: LinkedIn:

    • Edited by Leon Laude Monday, July 6, 2020 3:30 PM
    Monday, July 6, 2020 1:43 PM
  • What Leon has suggested, will definitely help you in configuring HA DPM as a Virtual Machine. However keep in mind that DPM as an application is not Cluster aware, which means you can not create a DPM cluster instance. This is another reason why you can not keep DPM's DB in SQL AG/ Always On. Its only supported in SQL FCI.

    So if DPM application is broken in the guest or DPM server is not accessible due to any unforeseen reasons, you will not be able to continue with your protection or recovery. In this situation, you might consider configuring a secondary DPM protection for DR recovery.

    If a primary DPM server fails you can switch protection to the secondary server. After you've switched protection, you can backup data sources or perform a recovery from the secondary server.

    Refer this link for more information.

    Monday, July 6, 2020 3:50 PM
  • Hi Aayoosh,

    Thanks, I'll check this and update.

    Wednesday, July 15, 2020 11:35 AM
  • Hi Leon,

    When you say replicate data to secondary DPM server, then is it like DPM will take care of the replication or underlying storage ?

    Wednesday, July 15, 2020 11:36 AM
  • Hi Leon,

    When you say replicate data to secondary DPM server, then is it like DPM will take care of the replication or underlying storage ?

    DPM does not take care of this, your storage would have to take care of it.

    Blog: LinkedIn:

    Wednesday, July 15, 2020 11:51 AM