MABS Database Backup and Restore: DPMDB Recovery Runbook

Protect the DPMDB

Include the MABS database in a protection strategy and keep the backup procedure separate from assumptions about the MABS application server itself.

Record the MABS version

The restored database and the MABS installation used for recovery need compatible versions. Record the MABS version and update rollup as part of your recovery documentation.

Protect the recovery prerequisites

Store the required vault credentials and encryption passphrase securely. The recovery process can fail if the credentials belong to the wrong vault or the passphrase does not match the original MABS configuration.

Restore the database

Microsoft documents restoring the MABS database and then synchronizing it with the installed MABS instance. Keep the restored database location and SQL instance details documented.

Run DpmSync

After restoring the database, use DpmSync to synchronize the database with the storage pool and installed protection agents. Validate the console, protection groups and recovery points after synchronization.

Test the complete procedure

A backup that has never been restored is an assumption. Perform a controlled recovery test and document each dependency, credential and version requirement.

Useful commands

DpmSync -RestoreDb
DpmSync -Sync

Production checklist: capture the original state, test one dependency at a time, make the smallest controlled change and validate the original symptom before closing the incident.

What good troubleshooting looks like

Use evidence before configuration changes. Record the symptom, test result, change made and validation result so another engineer can repeat the procedure.

Workflow
Symptom → hypothesis → direct test → controlled change → validation → documentation

Frequently asked questions

What should I check first?

Start with the exact failed path or dependency and test it directly before changing configuration.

Should I change production configuration immediately?

No. Capture the current state first and make one controlled change at a time.

How should I document the fix?

Record the symptom, commands, result, configuration change and validation result.

Related TechRunbook guides

Primary reference

This guide was independently written for TechRunbook. Technical details were checked against current Microsoft documentation. Microsoft Learn reference →

Need more infrastructure runbooks?

Explore the TechRunbook article library for Windows Server, VMware, Hyper-V, Azure, PowerShell and MABS troubleshooting.

Browse all articles →