Symptoms

The PowerProtect VM Direct Engine solution is used to protect the vSphere environment. The FULL virtual machine and IA restore operation fails with error code ARV0007 during the VM creation.The restore details show: ARV0007: VM Direct engine is unable to restore the virtual machine 'MY-VM-NAME' on vCenter 'MY-VCENTER-NAME'. Restore of this virtual machine to the destination vCenter was unsuccessful. Review the error details and summary log in the Jobs window, or review the log files at /var/log/brs/vmdm for more detailed information to troubleshoot the issue. Session '86355c76-935e-44e6-bb38-350b12182ba0' is unsuccessful: Unable to update vmx file's 'nvram' entry. The backup session log shows: ... YYYY-MM-DD HH:MM:SS YYYY-MM-DD HH:MM:SS INFO: [85264ba048364b27;825aae2bee866c86] Host 'vx-poa01.ecds.local' is running VMware ESXi 7.0.3 build-19898904. YYYY-MM-DD HH:MM:SS INFO: [85264ba048364b27;825aae2bee866c86] Creating directory for storage type "vsan". YYYY-MM-DD HH:MM:SS INFO: [85264ba048364b27;825aae2bee866c86] Created datastore directory '[MY-DATASTORE-NAME] MY-VM-NAME'. YYYY-MM-DD HH:MM:SS WARN: [85264ba048364b27;825aae2bee866c86] Did not find nvram entry in vmx file. YYYY-MM-DD HH:MM:SS ERROR: [85264ba048364b27;825aae2bee866c86] Unable to update vmx file's 'nvram' entry. YYYY-MM-DD HH:MM:SS ERROR: [85264ba048364b27;825aae2bee866c86] Unable to upload the configuration files: "Unable to update vmx file's 'nvram' entry." YYYY-MM-DD HH:MM:SS WARN: [85264ba048364b27;825aae2bee866c86] RecoverVMSessions "86355c76-935e-44e6-bb38-350b12182ba0" cleaning up running recover session due to error. YYYY-MM-DD HH:MM:SS INFO: [85264ba048364b27;825aae2bee866c86] Successfully removed folder/file "[MY-DATASTORE-NAME] MY-VM-NAME". YYYY-MM-DD HH:MM:SS INFO: [85264ba048364b27;825aae2bee866c86] Disconnected from session on vCenter 'MY-VCENTER-NAME.my-domain.local'. YYYY-MM-DD HH:MM:SS ERROR: [85264ba048364b27;825aae2bee866c86] Unable to recover to a new VM. Unable to update vmx file's 'nvram' entry. ... Other VM restores in the environment successfully complete.

Cause

This is a known PowerProtect VM Protection solution limitation. The VM backup workflow protects the VM configuration file (*.vmx). The *.vmx file did not contain the nvram attribute entry during the time of the asset backup copy. The restore workflow retrieves the *.vmx file nvram information for the VM creation operation, but the workflow fails due to the missing attribute.

Resolution

The PowerProtect 19.13.0-20 is enhanced to handle the missing nvram attribute (PPDM-216122) from the VM configuration file. Install the latest PowerProtect Data Manager release to resolve the symptom. The newest available releases are available on the PowerProtect Data Manager Drivers & Downloads page.

Support Cases