Microsoft Office Tutorials and References
In Depth Information
Backing up DPM using third-party software
If this was SQL we would see .mdf and . ldf files. If it was Hyper-V you would see
.vhd files or if it was just word documents that were being protected you would see
.docx files. We need to see this to get a better understanding of what the replicas are
and to see how important it is to back them up along with the DPM database. This is
where your actual data resides and where the DPM configuration is. Other items that
you can include in your DPM backup are:
• DPM reporting database ReportServer.mdf .
bin folder located at: %systemdrive%\Program Files\Microsoft DPM\
DPM\bin . This may contain custom PowerShell scripts you utilize for DPM.
These items are not required to recover a DPM server. Now let's look at restoring
the DPM database and the replicas. This will essentially be the same across any
third-party software you choose. In the following examples we will act as if the DPM
server failed and you have new hardware that will become your new DPM server.
You will need to use a command-line tool called DpmSync . It is used to restore the
DPM database to a SQL instance and to synchronize the DPM database with the
replicas in the storage pool.
Follow these steps to restore a DPM database:
1.
Rebuild your server with the OS and prepare your SQL instance if you plan
to use a remote one.
2.
Install DPM on the replacement hardware.
3.
Make a folder to store the DPM database restores in.
4.
Recover the DPM database that you have backed up to this folder.
5.
Now you must use the DPMSync tool to reattach the DPM database. Here is
the syntax for this:
DpmSync–RestoreDb –DbLocLOCATIONOFYOURBACKEDUPDPMDB–
InstanceNameNAMEOFSQLINSTANCEYOUWILLUSE
When this runs the DPM service will be stopped and then restarted.
Before you can even restore a replica, its status in DPM needs to be set as manual
replica creation pending . The following steps will show you how to restore
DPM replicas:
1. Run DpmSync–sync to finish the database restore process and start the replica
restore process. Running DpmSync–sync will change the replicas status to
manual replica creation pending .
2. Run DpmSync–ReallocateReplica to reformat replicas that are marked as
missing and change their status to manual replica creation pending . This is
actually reallocating disk space from the storage pool for the replicas.
 
Search JabSto ::




Custom Search