Match the MABS database version before rebuilding its server

Source facts

Microsoft Azure Backup Server stores its configuration and backup information in DPMDB. To restore that database, the MABS installation must match its version, including the applicable update rollup.

Microsoft requires DpmSync -Sync after restoring the database. The source warns that some replicas can still be marked missing after synchronization. It also conditions reuse of disk-based backups after a rebuild on the storage-pool disks having survived the outage. Microsoft Learn.

Applicability

Identify the saved database, originating MABS build, installed rollup, intended recovery server, and storage-pool condition. Review the source’s method-specific recovery procedure before restoring anything. Keep the database backup and access to protected backup data as separate recovery dependencies.

DSE recommendation

DSE recommends retaining the build and rollup evidence with the database recovery record. Confirm suitable installation media and an approved rebuild location before an incident. Assign someone to reconcile synchronization results and missing replicas instead of declaring the server recovered as soon as SQL accepts the database.

Verification

In an isolated authorized exercise, verify the installation/database version match, perform the documented restoration and synchronization, and inspect the resulting replica state. Test a representative recovery through the rebuilt service. Record unresolved replicas explicitly and preserve the observed storage-pool condition; do not generalize one successful restore to backups whose underlying disks were lost.

Official references

Microsoft Learn: Back up the MABS server. Source retrieved September 9, 2026.