DPM is a great product to protect Microsoft workloads, and now that we can use Azure as long-term repository, to protect the vast majority of workloads (such as Exchange for example). There is one little detail that we must pay attention which is the protection of DPM database (which is on SQL Server), and without it we can’t do much with our protected data in case of a major failure of DPM.
There are several (no kidding, at least 5 different ways) to protect the DPM database, and in this Tutorial we are going go to use the built-in utility called dpmbackup.
In order to protect the DPM database we should know the SQLServerName, InstanceName and DPM Database Name. Since SQL and DPm can be installed in different ways, such as SQL and DPM, DPM and remote SQL, DPM and Remote SQL Cluster and so forth. We will assume that we have the DPM and SQL installed on the same server.
dpmbackup.exe –db –sqlServerName . –instanceName <SQL-Instance> –dpmdbname DPMDB_<DPM-Server-Name>
Note: By default the dpmdbname is always DPMDB_ plus the DPM Server name.
After getting a message Backup created successfully then we can check a .bak file on the DPM installation folder under DPM\Volumes\ShadowCopy\Database Backups location.
Using this procedure one can easily protect their DPM database, but make sure that you move that folder to a different location and in a secure place.