Administrator Guide
NOTE: The DPM Central Console is integrated with Operations Manager (and does not show up as a separate interface). It
enables you (through the System Center 2012 R2 Data Protection Manager node) to monitor all DPM servers, and to take
actions in response to alerts. For more information, see the following topics in the TechNet Library:
• Monitor DPM (http://technet.microsoft.com/library/jj628024.aspx)
• Manage multiple DPM servers with Central Console(http://technet.microsoft.com/library/jj860391.aspx)
As described in Recovering DPM from DPM failures, recovering a DPM server includes leveraging DPM database backups. Each DPM
server is congured as follows:
• Backs up the DPM database to the E:\ drive on the same VM.
• Scheduled to back up the database every four hours by using the Windows DPMDBBackup Task Scheduler job.
Because this backup job can fail for many reasons, you should regularly monitor the status of this job on all DPM servers. The most
common possible failures include the following.
Table 29. Backup failures
Issue Symptom Resolution
The request to SQL Server to export and
copy the DPM database to the E:\ drive
fails.
Event Viewer displays a SQL Server
database error.
Fix the SQL Server error, and then run the
DPMDBBackup job again.
Drive E:\ runs out of space. Event Viewer displays a Disk Full error. Delete the oldest le on the E:\ drive (and make
a copy if necessary). Then, run the
DPMDBBackup job again.
Using the Dell Hybrid Cloud System for Microsoft data
consistency runbooks
Dell Hybrid Cloud System for Microsoft includes runbooks that you can use to detect and, in some cases, to automatically recover from
data inconsistencies between the databases of the components that are deployed as part of Dell Hybrid Cloud System for Microsoft.
Specically, the Invoke-DataConsistency runbook (and its associated child runbooks) detects and tries to recover from inconsistencies
between components’ states.
Dell recommends that you use the Dell Hybrid Cloud System for Microsoft data consistency runbooks for detection and recovery after you
restore a management component database from backup. For example, you may have restored a database to x data corruption. The
detection runbooks can report inconsistencies between the Windows Azure Pack, SPF, and VMM database components, that is, objects
associated with the VM Cloud Resource Provider.
The detection runbooks can report inconsistencies between the Windows Azure Pack, SPF, and VMM database components, that is,
objects associated with the VM Cloud Resource Provider.
Overview of the data consistency master and child runbooks
The data consistency runbooks include a master runbook, which in turn triggers a set of child runbooks.
The master runbook, Invoke-DataConsistency, is the main runbook to use for detection and recovery. When you run it, you must specify a
subsystem. This triggers the associated child runbooks for that subsystem. To understand what the subsystem targets, see the information
in the following table.
96
Operations