Loading...
Loading...
The PowerProtect Data Manager virtual machine (VM) Direct Engine solution is initially used to protect the vSphere environment. The Protection Policy is being migrated to the PowerProtect Data Manager Transparent Snapshot Data Mover (TSDM) solution. The PowerProtect Data Manager User Interface (UI) "Jobs > Protection Jobs" shows that the virtual machine backup configuration fails with error ABV0038. ABV0038: VM Direct engine is unable to configure protection for the virtual machine my-vname on vCenter myvcenter.mydomain.com because one or more of the selected policy options are unsupported.The VM Direct engine cannot complete protection of the virtual machines on this host because one or more of the selected policy options are not supported with the Transparent Snapshot Data Mover (TDSM) protection mechanism. A protection policy with TSDM requires Performance optimization mode, with the Exclude swap files from backup and Enable guest file system quiescing checkboxes cleared.Configure the policy with options that are supported by the TSDM protection mechanism, or move the assset(s) that you want to protect with the TSDM protection mechanism to another policy.Read LessProtection policy options do not support the Transparent Snapshot protection mechanism. The vmdm.log shows: YYY-MM-DD HH:MM:SS INFO [vpe-thread-46] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:9a9971b3e443415a;JOB_ID:bbb88481d0c569fc][] [c.e.b.v.v.a.VPEConfigureOp.policyHasSdmSupportedFeatures(182)] - Policy doesnt have SDM supporting features. YYY-MM-DD HH:MM:SS WARN [vpe-thread-46] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:9a9971b3e443415a;JOB_ID:bbb88481d0c569fc][] [c.e.b.v.v.a.VPEConfigureOp.logErrorStack(64)] - Unable to configure my-vname com.emc.brs.vmdm.error.BadRequestException: Protection policy options do not support the Transparent Snapshot protection mechanism. at com.emc.brs.vmdm.vpe.actions.VPEConfigureOp.validateTsdmSupportedFeatures(VPEConfigureOp.java:270) at com.emc.brs.vmdm.vpe.actions.VPEConfigureOp.chooseDataMoverType(VPEConfigureOp.java:195) at com.emc.brs.vmdm.vpe.actions.VPEConfigureOp.createConfig(VPEConfigureOp.java:149) at com.emc.brs.vmdm.vpe.actions.VPEConfigureOp.execute(VPEConfigureOp.java:100) at com.emc.brs.vmdm.vpe.service.VPEActionDispatcher.execute(VPEActionDispatcher.java:349) at com.emc.brs.vmdm.vpe.service.VPEActionDispatcher.lambda$executeOp$1(VPEActionDispatcher.java:315) at com.emc.brs.vmdm.vpe.util.ResourceUtils$JobExecutorImpl.lambda$createWorkflowTask$0(ResourceUtils.java:141) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829) YYY-MM-DD HH:MM:SS ERROR [vpe-thread-46] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:9a9971b3e443415a;JOB_ID:bbb88481d0c569fc][] [c.e.b.v.v.a.VPEConfigureOp.buildWorkflowException(365)] - Unable to create configuration -- Protection policy options do not support the Transparent Snapshot protection mechanism. Parameters: { "asset" : "my-vname", "plc" : "MY PROTECTION POLICY NAME", "dataConsistency" : "CRASH_CONSISTENT", "storage" : "mydatadomain.mydomain.com", "storageUnit" : "MY STORAGE UNIT NAME", "taskId" : "043ecb64-f548-433c-a26c-325313d7db96", "vcenter" : "myvcenter.mydomain.com" } Result: { "status" : "Failure", "error" : "Protection policy options do not support the Transparent Snapshot protection mechanism." } YYY-MM-DD HH:MM:SS INFO [vpe-thread-46] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:9a9971b3e443415a;JOB_ID:bbb88481d0c569fc][] [c.e.b.v.v.s.VPEActionDispatcher.execute(351)] - Finished executing VMDM_CONFIGURATION my-vname
The solution cannot complete protection of the VM because a selected Protection Policy option is not supported with the Transparent Snapshot Data Mover (TDSM) protection mechanism. A Protection Policy with TSDM requires Performance optimization mode, with the "Exclude swap files in backup" and "Enable guest file system quiescing" checkboxes cleared.
The TSDM solution has added Capacity optimization mode to virtual machine Protection Policies starting in PowerProtect Data Manager 19.10. The "Exclude swap files from backup" and "Enable guest file system quiescing" options cause the TSDM Protection Policy to revert to VADP. There are a few options to protect the affected VM in the environment. Create a new Protection Policy with the appropriate options and move the VM to the new Protection Policy. Update the existing Protection Policy to fulfill the configuration requirements. The VM can remain in the existing protection policy but must be migrated to the VADP protection mechanism.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.