PowerProtect Data Manager: VM Backup Fails during Snapshot Creation with ABV0030
Summary: The PowerProtect Data Manager appliance is used to protect the vSphere environment with the virtual machine (VM) Direct Engine solution. The virtual machine backup fails with "ABV0030 msg.changetracker.MIRRORCOPYSTATUS" indicating a snapshot creation issue. ...
Symptoms
The PowerProtect Interface shows:
\
Warning: Virtual machine left locked by backup session because cleanup is required. Snapshot was not removed. Error : Backup has FAILED. Unable to create snapshot. Unable to create non-quiesced snapshot after a retry attempt. An error occurred while saving the snapshot: msg.changetracker.MIRRORCOPYSTATUS.
The backup export log shows:
... YYYY-MM-DD HH:MM:SS DEBUG: [9b1759a78f26ffe0;bc0706ee52f4711d] Sending status 'Creating snapshot of virtual machine ...' ... YYYY-MM-DD HH:MM:SS INFO: [9b1759a78f26ffe0;bc0706ee52f4711d] Creating snapshot of virtual machine ... YYYY-MM-DD HH:MM:SS DEBUG: [9b1759a78f26ffe0;bc0706ee52f4711d] Sending create snapshot request to Snapshot Manager ... YYYY-MM-DD HH:MM:SS ERROR: [9b1759a78f26ffe0;bc0706ee52f4711d] Unable to create non-quiesced snapshot after a retry attempt. An error occurred while saving the snapshot: msg.changetracker.MIRRORCOPYSTATUS. YYYY-MM-DD HH:MM:SS ERROR: [9b1759a78f26ffe0;bc0706ee52f4711d] Unable to create snapshot. ...
The virtual machine vmware.log shows a snapshot failure:
… YYYY-MM-DD HH:MM:SS In(05) vmx - SnapshotVMXTakeSnapshotComplete: Done with snapshot 'PowerProtect Backup Snapshot -- PowerProtect Data Manager': 0 YYYY-MM-DD HH:MM:SS In(05) vmx - SnapshotVMXTakeSnapshotComplete: Snapshot 0 failed: Could not get mirror copy status (5).
Cause
The VM Direct Engine issued a snapshot request to vCenter Server using the VMware Application Programming Interface (API). During snapshot creation, the ESXi hypervisor attempted to quiesce the guest operating system through VMware Tools, which returned exit status 5. This status code indicates that the guest OS quiescing operation failed, typically due to a Windows Volume Shadow Copy Service (VSS) writer failure within the VM.
Resolution
Restart the Guest OS and perform a vSphere storage migration of the affected virtual machine (VM) to another datastore. If required, contact Broadcom Support for further assistance with the Guest OS quiesce operations.