none
Backing up SCDPM 2019 with Veeam Backup and Replication 9.5 Community Edition RRS feed

  • Question

  • Hi, I am using SCDPM 2019 to protect critical load in test environment (very important though) - all servers are Hyper-V 2016 VMs (Hyper-V 2016 cluster (2 physical hosts) managed by SCVMM):

    1. Certification Authority
    2. Domain Controllers
    3. Microsoft Identity Manager
    4. System Center Suite Databases (SCCM, SCOM, SCO, SCSM, SCVMM, SCDPM)
    5. ...

    Since Veeam Backup and Replication Community Edition supports up to 10 protected VMs I was thinking of backing up SCDPM with VBR CE. Should I have to backup SCDPM as whole VM (containing system volume and 2 volumes dedicated for storing backup sets 1.3 TB size in total) or just SCDPM database? In case of backing up whole VM I would need at least 1 TB volume again on VBR server. If I protect just SCDPM database will that be enough to restore SCDPM and attach VHDXs (2 volumes storing backup sets)?

    Thanks in advance.

    • Edited by BoxiKG Tuesday, December 17, 2019 12:13 PM
    Tuesday, December 17, 2019 12:13 PM

All replies

  • Hi,

    The DPM database is the critical component, the volumes where the backups are located are of course also important because they contain the backup data, but if you lose the database you will not be able to either view or restore any backups.

    You could also consider installing a secondary DPM server that backs up the primary DPM server, you can find more information about this method over here: Back up the DPM server

    There are three (3) methods of backing up a DPM server:


    Primary to secondary protectionThe database and replicas stored on a primary DPM server can be backed up to a secondary DPM server. If the primary server fails the secondary server continues to back up protected workloads. If the primary server fails you can do either of the following: Rebuild the primary server and restore its database and replicas from the secondary server. Then move the protected workloads back to the primary server after the rebuild. Select to switch protection to the secondary DPM server. With this setting you then restore to the protected computer directly from the secondary server when the need arises. For instructions, see Set up secondary servers.

    DPM chainingA chain of DPM servers provide protection, and each server protects the next one in in the chain. For example: DPM1 is protected by DPM2 (DPM1 is the primary and DPM2 is the secondary). DPM2 is protected by DPM3 (DPM2 is the primary and DPM3 is the secondary) For instructions, see Set up chaining.

    Cyclic protectionOne DPM server is backed up by another DPM server, and vice versa. So that DPM1 protects DPM2, and likewise DPM2 protects DPM1. This is useful for small environments.

    If a disaster happens, and the DPM server is lost but you have backups of the DPM database, you will have to restore the DPM database to an SQL Server, then reinstall DPM and point it to the restored DPM database. Then attach the volumes where the backups are contained to the newly reinstalled DPM server.

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, December 17, 2019 12:24 PM
  • So I can "get away with" just DB backup using VBR CE and in case of disaster to attach volumes (VHDXs) to the newly reinstalled DPM server as the very last step?
    • Edited by BoxiKG Tuesday, December 17, 2019 3:36 PM
    Tuesday, December 17, 2019 2:33 PM
  • Yes, more or less any backup method works on the DPM database, even the native SQL backup would suffice.

    In case of a disaster you would:

    1. Restore the DPM database

    2. Reinstall DPM and point to the restored DPM database.

    3. Re-attach the DPM backup volumes.

    4. Run the DpmSync -Sync command.


    Blog: https://thesystemcenterblog.com LinkedIn:

    Tuesday, December 17, 2019 5:00 PM