PowerProtect Data Manager 19.16 Virtual Machine User Guide

DD NFS share not removed after instant access restore

The NFS share might not be removed after a successful virtual machine instant access restore. When this occurs, the restore hangs and the following NFS clients appear enabled in the DD system.

If you encounter this issue, you can wait 24 hours for PowerProtect Data Manager to clean up the DD NFS shares, or you can stop the restore and clean up the DD NFS clients manually by performing the following steps:

1. Restart the VMDM service by typing /usr/local/brs/lib/vmdm/bin/vmdm restart.
2. Clean up DD NFS clients by typing nfs del <Path> <Client>.
3. In the vSphere Client's Configuration tab, manually unmount the EMC-vProxy-vm-qa-xxxxx DDNFS datastore that is mounted on the ESXi host.

Filtering virtual machine copies by File Indexing column is not available

When you select a virtual machine for restore in the PowerProtect Data Manager UI and then click View Copies to select from one of the available copies, using the filter in the File Indexing column does not return any results. Use the filters from other columns to locate the virtual machine asset copies that you want to restore.

IP address change required after successful image-level restore to a new virtual machine

After performing a successful image-level restore to a new virtual machine, ensure that you change the IP address immediately in order to avoid IP conflicts with the original virtual machine. If you do not change the IP to a unique value, subsequent data protection operations might fail on the restored virtual machine, even if that virtual machine's network interfaces are disconnected.

Removal of pre-existing snapshots required before running virtual machine restore

A virtual machine restore cannot be completed when a pre-existing VMware snapshot is present on the virtual machine. An error similar to the following appears:

Session 'session ID' is unsuccessful: There are 1 pre-existing snapshot present on this VM. Recover is not possible. Remove snapshot(s) and try again.

Verify that no pre-existing snapshots exist on the virtual machine, and then retry the restore operation from the System Jobs window of the PowerProtect Data Manager UI.

Restoring to a new virtual machine fails with ARV0007 and vMotion errors

When restoring to a new virtual machine, the following error messages are seen:

ARV0007: VM Direct engine is unable to restore the virtual machine … on …
Restore of this virtual machine to the destination vCenter was unsuccessful.
Unable to complete vMotion task … iso was not found

To resolve this issue, perform the following steps:

1. From the vCenter UI, edit the properties of the virtual machine.
2. In the Virtual Hardware tab, for each CD/DVD drive entry that has a value of Datastore ISO File, change the value to Client Device.
3. Follow the procedure in Migrate an Instant Access session.

Some operations fail for vTPM virtual machine in a DRS-enabled cluster with dedicated vCenter user account

The following operations fail for virtual Machines with a Virtual Trusted Platform Module (vTPM) when the virtual machines are in a DRS-enabled cluster and using a dedicated vCenter user account:

• The vTPM virtual machines cannot be powered on after a restore to the original virtual machine or restore to a new virtual machine , with the error Permission to perform this operation was denied displaying.
• For an instant access restore, migration is unsuccessful, with the error Unable to complete vMotion task Task:task-3785. Permission to perform this operation was denied displaying.

To avoid these issues, ensure that the privilege Cryptographic operations > Migrate is included as part of the dedicated vCenter user role. Specify the required privileges for a dedicated vCenter user account provides more information.

Virtual machine protection copy does not display under available copies

If a virtual machine protection copy does not display under the available copies in PowerProtect Data Manager, verify the following:

• Ensure that protection of the virtual machine completed successfully.
• Check that the desired copy has not expired according to the PowerProtect Data Manager protection policy.

Virtual machine restore fails when vProxyd or vrecoverd disruption occurs

A virtual machine restore hangs and VPOD will not be able to reconnect to the restore session when the following scenarios occur:

• A disruption to the vrecoverd process on any external VM Direct Engine.
• A disruption to the vProxyd process during a Restore to Original Folder and Overwrite Original Files or Create and Restore to New VM operation that uses Transparent Snapshots Data Mover (TSDM) as the protection mechanism.

After several retry attempts, VPOD marks the restore session as "Failed" and releases theVM Direct Engine associated with the restore.

If this failure occurs during a Create and Restore to New VM, you can delete the new virtual machine and restart the restore operation.

If this failure occurs during a Restore to Original Folder and Overwrite Original Files, you must remove the VM Direct Engine lock on the virtual machine from the vCenter server, and then retry the restore operation. In the vSphere Client, the VM Direct Engine lock appears as a custom attribute with the name Dell VM Direct Engine Session.

Virtual machine restore fails when the previous restore of this virtual machine is in progress or did not complete

  Error : There is another running restore operation that conflicts with this request.

If the previous restore operation for this virtual machine is still in progress, monitor the progress in PowerProtect Data Manager until the restore completes. If the virtual machine restore is complete but the task stops responding, then you must manually cancel the restore in PowerProtect Data Manager by restarting the VMDM service. You can restart the VMDM service by typing /usr/local/brs/lib/vmdm/bin/vmdm restart.

Virtual machine restore fails with error due to VM Direct corruption

 com.emc.dpsg.vproxy.client.VProxyManager - Error(createSession): javax.net.ssl.SSLException:
Unrecognized SSL message, plaintext connection

Ensure that the vproxyd service is running in PowerProtect Data Manager by typing the following command.

ps xa | grep vproxy

Ensure that the vproxy rpm is installed as expected in PowerProtect Data Manager by typing the following command.

rpm -qa | grep vProxy

When logged in as the root user, restart the vproxyd service on PowerProtect Data Manager by typing the following command.

systemctl restart vproxyd

Virtual machine restore fails with error "User UserEARA does not have proper privileges"

A virtual machine restore fails with the error "User UserEARA does not have proper privileges" when the user does not have adequate privileges to perform the restore operation.

Ensure that the PowerProtect Data Manager user performing the restore belongs to System Tenant and has the Administrator or Restore Administrator role.

Virtual machine restore fails with name resolution error

 com.emc.brs.vmdm.http.HttpsConnector - null: Temporary failure in name resolution
java.net.UnknownHostException : null: Temporary failure in name resolution

Ensure that you have proper name resolution between protection storage and either PowerProtect Data Manager or the vCenter or ESXi server.

Virtual machine restore of encrypted virtual machine to a new virtual machine completes with an exception

When restoring an encrypted virtual machine to a new virtual machine, you might see the following messages:

ARV0049 One or more errors occurred during the restore of storage policies for virtual machine … on vCenter …

The restore for this virtual machine completed but the storage policy restore was unsuccessful because one or more errors occurred.

In the vSphere client, check the virtual machine in the vCenter inventory to verify the storage policy configuration status. If there is an issue with the storage policy configuration then you can attempt to fix it manually.

This issue can occur if the size of the virtual machine is greater than 40 GB. The virtual machine is restored, but the storage policy might not be.

If you encounter this issue, check the storage policy for the restored virtual machine from the vCenter user interface. If there is a problem with the storage policy, manually configure it.

Virtual machine restore of encrypted virtual machine succeeds, but displays an ABV0025 failure message

When using TSDM to restore an encrypted virtual machine that has tags applied to it from the vSphere Client, you might see the following message:

Failed
ABV0025: VM Direct engine is unable to configure protection for the virtual machine
The VM Direct engine cannot complete protection of this virtual machine because the protection configuration was unsuccessful.
Unable to ENABLE LWD

This message can be ignored. The virtual machine is successfully restored and protected.