A pre-flight checklist for MABS protection compatibility, including storage, VM, domain and unsupported data considerations.
01

Check the MABS version

Confirm the MABS release and protection matrix before designing the protection group. Supported workloads and features can change between releases.

02

Check the workload and storage

Verify the workload type, operating system, storage format and deployment model. For example, MABS protection has specific requirements for supported volumes and VM workloads.

03

Review unsupported data

Microsoft lists unsupported data types and configurations, including several reparse-point and mount-point scenarios. Identify these before the first replica is created.

04

Check domain changes

A protected computer changing domains can disrupt protection. Plan domain migrations as a protection change rather than assuming existing replicas will automatically follow the new identity.

05

Check shared VHD scenarios

Some shared-disk configurations are not supported for VM protection. Validate the workload architecture against the current protection matrix.

06

Document the result

Record the MABS version, workload, protection group, storage type, retention policy and any exceptions. This becomes the baseline for future troubleshooting.

Useful commands

Get-DPMProtectionGroup
Get-DPMDatasource
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.
07

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
08

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.

09
MABS Database Backup and Restore: DPMDB Recovery Runbook →MABS Modern Backup Storage: Planning and Troubleshooting →MABS System State and BMR Backup Troubleshooting →
10

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 →

Explore more TechRunbook guides

Browse practical troubleshooting guides, PowerShell scripts, checklists and infrastructure resources for your environment.

Browse all articles →
TechRunbook · Practical infrastructure knowledge, ready when it matters.