Verify the exclusion list after changing a VMware backup disk selection

Source facts

MABS V3 UR1 and later support excluding individual VMware VM disks through ExcludeDisk.ps1. Microsoft requires stopping DPMRA before running the change; otherwise the script can report success without updating the exclusion list. No jobs should be running before that service stop. For a VM already under protection, adding a disk exclusion also requires a manual consistency check. Microsoft Learn.

Applicability

Use this check only for an approved VMware disk-exclusion change on the MABS server protecting that VM. Identify the VM and exact datastore/VMDK path from its configuration; do not reuse a sample’s indexed object selection.

DSE recommendation

Treat the script result and the effective exclusion list as separate acceptance evidence. Before the maintenance window, obtain workload-owner agreement on which disk will no longer be covered by this protection. Confirm the intended alternative protection or accepted exclusion. Coordinate the service interruption around active jobs and keep the previous list available. Use the documented procedure for the actual MABS version rather than treating a success message as a complete change record.

Verification

Inspect the target VM’s exclusion list after the approved edit and compare the exact disk path with the authorized request. For an already protected VM, record the required consistency-check outcome. Verify the resulting protection selection and a representative recovery plan for the remaining disks. If the list did not change, investigate service state and target identity before repeating the operation.

Official references

Microsoft Learn: Back up VMware VMs using Azure Backup Server.