POWERPROTECT DATA

MANAGER
TROUBLESHOOTING

PARTICIPANT GUIDE

PARTICIPANT GUIDE
 PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page i

Table of Contents

PowerProtect Data Manager Troubleshooting........................................ 4

PowerProtect Data Manager Troubleshooting Introduction .................................................. 5

Troubleshooting Network Setup .............................................................. 6

Troubleshooting Network Setup ........................................................................................... 7

Troubleshooting PowerProtect Agent Service Installation ................... 8

Troubleshooting PowerProtect Agent Service Installation .................................................... 9

Troubleshooting PowerProtect Agent Service Operations ................. 10

Troubleshooting PowerProtect Agent Service Operations .................................................. 11

Troubleshooting PowerProtect Data Manager Upgrade ...................... 12

Troubleshooting PowerProtect Data Manager Upgrade ..................................................... 13

Troubleshooting Protection Policy for PowerProtect DD Storage Unit14

Troubleshooting Protection Policy for PowerProtect DD Storage Unit ................................ 15

Monitoring Storage Capacity Thresholds ........................................................................... 16

Troubleshooting Kubernetes Cluster Protection ................................. 17

Troubleshooting Kubernetes Cluster Backup ..................................................................... 18

Troubleshooting Kubernetes Cluster Restore..................................................................... 21

Troubleshooting Virtual Machine Backup............................................. 23

Troubleshooting Virtual Machine Backup ........................................................................... 24

Troubleshooting Virtual Machine Backup ........................................................................... 28
Troubleshooting Virtual Machine Backup ........................................................................... 31

PowerProtect Data Manager Troubleshooting-SSP

Page ii © Copyright 2021 Dell Inc.

Troubleshooting Virtual Machine Restore ............................................ 34

Troubleshooting Virtual Machine Restore .......................................................................... 35

Troubleshooting Virtual Machine Restore .......................................................................... 38
PowerProtect Data Manager Certification Map .................................................................. 40

Course Completion .................................................................................................. 42

You Have Completed This eLearning................................................................................. 43

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page iii

PowerProtect Data Manager Troubleshooting

PowerProtect Data Manager Troubleshooting-SSP

Page 4 © Copyright 2021 Dell Inc.

PowerProtect Data Manager Troubleshooting Introduction

Upon completion of this course, you should be able to:

→ Troubleshoot PowerProtect Agent Service installation and operations issues.
→ Troubleshoot PowerProtect agent service installation and operations.
→ Troubleshoot PowerProtect protection policy for PowerProtect DD storage
unit.
→ Troubleshoot virtual machines backup and restore issues.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 5

Troubleshooting Network Setup

PowerProtect Data Manager Troubleshooting-SSP

Page 6 © Copyright 2021 Dell Inc.

Troubleshooting Network Setup

vCenter registration and VM Direct Engine deployment fails if the PowerProtect

Data Manager server is deployed in the same private network as the internal
Docker network.

PowerProtect Data Manager uses an internal private Docker network. If the

PowerProtect Data Manager server is deployed in the same private network as the
internal Docker network, or if some data sources have already been deployed
within the private network, PowerProtect Data Manager fails to protect the data
sources.

To resolve this issue, deploy the PowerProtect Data Manager server and other
data sources in a different network. If you cannot modify the deployed network, run
a script tool within PowerProtect Data Manager to switch the private Docker
network to a different network.

To switch the private Docker network to a different network:

1. SSH into PowerProtect Data Manager: Log in with operating system admin
credentials, and then use the su command to become root.
2. Modify the Docker network by running the following command:

− /usr/local/brs/puppet/scripts/docker_network_switch.sh
subnet gateway
subnet: describes the new network in the format 172.25.0.0/24
gateway: is the gateway for the private network. For example: 172.25.0.1

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 7

Troubleshooting PowerProtect Agent Service
Installation

PowerProtect Data Manager Troubleshooting-SSP

Page 8 © Copyright 2021 Dell Inc.

Troubleshooting PowerProtect Agent Service Installation

PowerProtect Agent Service installation might fail with the following error message:

 Service 'PowerProtect Agent Service' (AgentService) could

not be installed. Verify that you have sufficient
privileges to install system services.

Possible causes of the installation failure are as follows:

• The installation was attempted on a passive node of a Failover Cluster Instance

(FCI).
• The installation was canceled, and a rollback left some stale entries of
PowerProtect agent services.

Workaround:

• Clean up the PowerProtect agent service entries, and retry the installation.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 9

Troubleshooting PowerProtect Agent Service
Operations

PowerProtect Data Manager Troubleshooting-SSP

Page 10 © Copyright 2021 Dell Inc.

Troubleshooting PowerProtect Agent Service Operations

To troubleshoot the PowerProtect Agent Service operations, check the agent

service log file OpAgentSvc-<timestamp>.log. The agent service log file
OpAgentSvc-<timestamp>.log is located:

• On Windows: <agent_service_installation_location>\logs
• On Linux: <agent_service_installation_location>/logs

To change the log level and retention of temporary files, you can modify specific
parameter settings in the config.yml file with a text editor.

To modify the log level and retention of temporary files, you can perform the
following steps:

1. Stop the PowerProtect agent service.

2. Open the config.yml file in a text editor.
3. Modify the log-level settings in the following parameters, as required:
− DEBUG
− INFO
− WARNING
− ERROR
− CRITICAL
4. To retain the temporary files, set the keepTempFiles parameter to True in the
config.yml file.
5. Start the PowerProtect agent service.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 11

Troubleshooting PowerProtect Data Manager Upgrade

PowerProtect Data Manager Troubleshooting-SSP

Page 12 © Copyright 2021 Dell Inc.

Troubleshooting PowerProtect Data Manager Upgrade

Mounting a read-only file system results in failed upgrade

If you mount a read-only file system under the /home/admin or /home/sysadmin

directories on the PowerProtect Data Manager node, the upgrade cannot complete
successfully. Ensure that you remove read-only file system mounts before
upgrading PowerProtect Data Manager.

Ensure that certificates existing on the preupgrade system also exist on the
postupgrade system

1. Log in to the PowerProtect Data Manager operating system with administrator

credentials.
2. Run the upgrade command:
o /usr/local/brs/lib/secretsmgr/bin/secretsmgr-tls-upgrade
o The system displays the external system certificates.
3. Verify each certificate as trusted or untrusted: At the prompt for each certificate,
type Y to accept.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 13

Troubleshooting Protection Policy for PowerProtect DD
Storage Unit

PowerProtect Data Manager Troubleshooting-SSP

Page 14 © Copyright 2021 Dell Inc.

Troubleshooting Protection Policy for PowerProtect DD
Storage Unit

When adding a protection policy in PowerProtect Data Manager, creation of a

Storage Unit on the selected PowerProtect DD system fails if you reach the
maximum MTree and Users count on the PowerProtect DD system. See the
PowerProtect DD documents for detailed information.

PowerProtect Data Manager enables you to finish adding the protection policy
without the PowerProtect DD system Storage Unit. However, if you later run a
backup of this protection policy, the backup process is suspended indefinitely with
no error message.

Workaround:

To continue backup operations on this device, you must perform a cleanup on the
PowerProtect DD system.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 15

Monitoring Storage Capacity Thresholds

PowerProtect Data Manager periodically monitors DD system usage and reports

alerts when the system reaches two capacity thresholds. As a best practice, check
for these alerts and respond before the system exhausts storage capacity.

At 80% capacity, PowerProtect Data Manager generates a weekly warning alert. At

this threshold, you should develop a strategy to add capacity or move protection
policies to another storage target.

At 95% capacity, PowerProtect Data Manager generates a daily critical alert. At this
threshold, capacity exhaustion is imminent.

Changing the capacity alerting thresholds requires contacting Dell EMC Support.

PowerProtect Data Manager Troubleshooting-SSP

Page 16 © Copyright 2021 Dell Inc.

Troubleshooting Kubernetes Cluster Protection

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 17

Troubleshooting Kubernetes Cluster Backup

The following topics provide information about troubleshooting Kubernetes cluster

backup:

To learn how to resolve each possible failure, click each tab.

Only native Kubernetes resources are supported

PowerProtect Data Manager supports the protection of native Kubernetes

resources only. If a namespace contains any Kubernetes distribution-specific
resource or any other kind of custom resource, backup and recovery operations
might fail.

Ensure that you do not include such namespaces in PowerProtect Data Manager
Kubernetes protection policies.

Backups of persistent volumes on FCD fail

The PowerProtect controller configures itself and Velero for the protection of
persistent volumes on first class disks (FCDs) if the controller detects a storage
class with the VMware CSI provisioner csi.vsphere.vmware.com.

If the VMware CSI driver and storageclass are installed after the Kubernetes
cluster is added as an asset source to PowerProtect Data Manager, FCD backups
fail with an error indicating failed to create backup job.

To resolve this issue, restart the PowerProtect controller by running the following
commands:

PowerProtect Data Manager Troubleshooting-SSP

Page 18 © Copyright 2021 Dell Inc.

• kubectl get pod -n powerprotect
• kubectl delete pod pod name obtained above -n powerprotect

Missing PVC cause namespace backups to fail

If a Kubernetes namespace contains a pod that is in pending state because the

pod references a PVC that is not present, the backup of that namespace fails.

To resolve this issue, perform one of the following:

• Create the missing PVC.

• Delete the pod if it is no longer required.

Add alternate storage class mapping for temporary PVCs created from
snapshot during non-FCD backup

In some scenarios, the storage class of the PVC being backed up might not be the
most appropriate storage class for the temporary PVC created from the snapshot
during the backup.

For example, when creating a volume from a snapshot, a dedicated storage class
that does not allocate space for the temporary PVC might be preferred. This can be
useful for backing up NFS PVs and use a storageclass with rootclient enabled.

To add an alternate storage class mapping for temporary PVCs, perform the
following:

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 19

1. Create a ConfigMap ppdm-snapshot-storage-class-mapping in the
PowerProtect namespace.
2. In the data section of the ConfigMap, add a storage class mapping in the
following format:

a. storage class of PVC being backed up: storage class to

use for snapshot PVC
b. For example, in the mapping xio-csi-sc: xio-csi-sc-snapshot-promoter, if the
PVC being backed up uses
the storage class xio-csi-sc, the snapshot PVC is created using the storage
class xio-csi-sc-snapshotpromoter.

PowerProtect Data Manager Troubleshooting-SSP

Page 20 © Copyright 2021 Dell Inc.

Troubleshooting Kubernetes Cluster Restore

The following topics provide information about troubleshooting Kubernetes cluster

restore:

To learn how to resolve each possible failure, click each tab.

Application pods might not appear in running state

When performing a Kubernetes restore to a new namespace that has a different

name than the namespace the backup copy was created from, the application pods
might not appear in running state after restoring in some scenarios.

For example, this can occur if the application has environment variables or other
configuration elements that adhere to the namespace from which the backup copy
was created, such as variables that point to services using FQDN in the form my-
svc.mynamespace.svc.cluster-domain.example or headless services
using FQDN in the form pod-name.my-headlesssvc.my-
namespace.svc.cluster-domain.example.

If this issue occurs, manually edit the deployments after the restore.

"Failed to create Proxy Pods" error appears during restore

If the restore operation fails with the error message -- Failed to create Proxy Pods.
Creating Pod exceeds the safeguard limit of 10 minutes, verify that the CSI driver is
functioning properly, and can dynamically provision volumes.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 21

Kubernetes HA clusters fail when API server not configured to send
ROOT certificate

If the Kubernetes cluster is set up in high availability mode and the Kubernetes API
server is not configured to send the ROOT certificate as part of the TLS
communication setup, backup and restore operations might fail with the following
error:

javax.net.ssl.SSLHandshakeExcept ion:
sun.security.validator.Validator Exception: PKIX path
building failed: sun.security.provider.certpath.S
unCertPathBuilderException: unable to find valid
certification path to requested target

To resolve the error, perform the following steps:

1. Copy the root certificate of the Kubernetes cluster to the PowerProtect Data
Manager server.
2. As an administrator on the PowerProtect Data Manager server, import the
certificate to the PowerProtect Data Manager trust store by running the
following command:

• ppdmtool -importcert -alias certificate alias -file file

with certificate -type BASE64 | PEM
o i or importcert: Imports the certificate.
o a or alias: Certificate alias is used to specify the file with the
certificate.
o f or file: Specify the certificate file.
o t or type: Specify the certificate type. Default type is PEM.

PowerProtect Data Manager Troubleshooting-SSP

Page 22 © Copyright 2021 Dell Inc.

Troubleshooting Virtual Machine Backup

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 23

Troubleshooting Virtual Machine Backup

The following topics provide information about troubleshooting virtual machine

backup failures:

To learn how to resolve each possible failure, click each tab.

VM Direct Engine limitations

VMware Distributed Resource Scheduler cluster support limitations

The PowerProtect Data Manager server is supported in a VMware Distributed

Resource Scheduler (DRS) cluster, with the following considerations:

• During backup of a virtual machine, host-vmotion or storage-vmotion is

not permitted on the virtual machine. The option to migrate will be disabled in
the vSphere Client UI.
• If the VM Direct proxy is in use for a backup or restore with Hot Add disks that
are attached, then storage-vmotion of the vProxy is not permitted during these
operations.

Thin provisioning not preserved during NFS datastore recovery

When backing up thin-provisioned virtual machines or disks for virtual machines on

NFS datastores, an NFS datastore recovery does not preserve thin provisioning.
VMware knowledge base article 2137818 at https://kb.vmware.com/kb/2137818
provides more information.

Network configuration settings are not restored with virtual machine after recovery
of a vApp backup

Network configuration settings are not backed up with the virtual machine as part of
a vApp backup. As a result, when you restore a vApp backup, you must manually
reconfigure the network settings.

PowerProtect Data Manager Troubleshooting-SSP

Page 24 © Copyright 2021 Dell Inc.

Names cannot contain special characters

Using special characters in the virtual machine names, datastore names, or data
center names can cause problems with the VM Direct Engine, such as failed
backups and restores. Special characters include the following: % & * $ # @ ! \ / : *
? " < > | ;, and so on.

VM Direct Engine limitations

Hot Add mode backups fail when datacenter names contain special characters

Virtual machine backups fail when the data center name contains special
characters and the transport mode that is specified for VM Direct backups is Hot
Add only.

Avoid using special characters in the data center name, for example,
"Datacenter_#2@3", or specify Hot add with fallback to Network Block Device for
the transport mode.

SAN transport mode not supported

VM Direct Engine supports only the Hot Add and NBD transport modes. The Hot
Add mode is the default transport mode. For a protection policy, you can specify to
use only Hot Add mode, only NBD mode, or Hot Add mode with fallback to NBD if
Hot Add is not available.

Independent disks are not supported by VM Direct Engine

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 25

When using independent disks, you cannot perform VMware snapshot for backup.

Lock placed on virtual machine during backup and recovery operations continues
for 24 hours if VM Direct Engine fails

During VM Direct backup and recovery operations, a lock is placed on the virtual
machine. If a VM Direct appliance failure occurs during one of these sessions, the
lock is extended to a period of 24 hours, during which full backups and transaction
log backups fail with the following error until the lock is manually released.

Cannot lock VM 'XXXXXX-YYY-ZZZ' (AA-BBB): Another EMC vProxy

operation 'Backup' is active on VM AA-BBB.

To manually release the lock on the virtual machine:

1. Open the vSphere Client.

2. Select the virtual machine and select Summary.
3. Select Custom attribute and click Edit.
4. Remove the attribute EMC VM Direct Session.

Deleting vCenter or moving ESXi

When you delete a vCenter Server asset source from PowerProtect Data Manager
without removing any vProxy/Search Nodes that the vCenter is hosting, the Nodes
will become non-operational and move into Failed status upon the next health
check. As a result, PowerProtect Data Manager upgrades fail. This issue also
occurs when you move the ESXi hosting the vProxy/Search Nodes from one
vCenter to another vCenter.

To correct this issue, you can perform one of the following actions:

PowerProtect Data Manager Troubleshooting-SSP

Page 26 © Copyright 2021 Dell Inc.

• Manually delete the vProxy/Search Nodes.
• Return the vProxy/Search Nodes to an Operational/Ready state using the
vproxymgmt and infranodemgmt tools. Choose this action if you want to add
the vCenter again, or you want to add the vCenter that the ESXi has been
moved to.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 27

Troubleshooting Virtual Machine Backup

The following topics provide information about troubleshooting virtual machine

backup failures:

To learn how to resolve each possible failure, click each tab.

Failed to lock Virtual Machine for backup

The following error message appears when a backup fails for a virtual machine or
when a previous backup of the virtual machine was abruptly ended and the VM
annotation string was not cleared:

Failed to lock Virtual Machine for backup: Another EMC VM

Direct operation 'Backup' is active on VM

To resolve this issue, clear the annotation string value for the virtual machine:

1. Connect to the vCenter server and navigate Home > Inventory > Hosts and
Clusters.
2. Select the virtual machine, and then select the Summary tab.
3. Clear the value that appears in the EMC Proxy Session field.

SQL databases skipped during transaction log backup

When an advanced application-consistent policy is enabled with transaction log

backup, the msvmagent_appbackup.exe program evaluates databases to
determine if transaction log backup is appropriate.

If transaction log backup is not appropriate for a database, the database will
automatically be skipped.

PowerProtect Data Manager Troubleshooting-SSP

Page 28 © Copyright 2021 Dell Inc.

All skipped databases are backed up as part of the next full backup. Also, a
skipped database will not result in msvmagent_appbackup.exe failure. The only
instance in which msvmagent_appbackup.exe would potentially fail is if all
databases failed to back up.

The msvmagent_appbackup.exe program generates a history report of the

databases, if the database backup status was success/skipped/failed, and a reason
if they were skipped or failed if applicable. This history report is visible in the action
logs for the VM Direct Engine, which are available as part of the appbackup logs.

Support for encrypted virtual machines

Backup and restore of encrypted virtual machines is supported in PowerProtect

Data Manager, with the following limitations:

• In order to use Hot Add transport mode, all VM proxies with access to the
encrypted virtual machine's datastore must be encrypted as well. For example,
if encrypted virtual machines reside in an ESXi cluster, all VM proxies deployed
on the cluster must also be encrypted.
• Restoring encrypted virtual machines to a different vCenter Server is not
supported. You must perform the restore to the original virtual machine or a new
virtual machine in the same vCenter.
• Restoring an encrypted virtual machine backup to a new virtual machine in the
original vCenter Server restores the virtual machine disks (VMDKs) in clear text
if the VMDKs are not encrypted.
• In order to backup and restore encrypted virtualization-based security (VBS)
and virtual Trusted Platform Module 2.0 (vTPM) virtual machines, vCenter 7.0
U1 or later is required.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 29

PowerProtect vSphere plug-in

After you replace the default self-signed security certificates, you may see the
following errors in the vSphere client PowerProtect portlet when you select virtual
machines:

• Service Unavailable: Please contact your administrator.

• No healthy upstream.

To correct this issue, reinstall the PowerProtect plug-in to apply the new
certificates.

PowerProtect Data Manager Troubleshooting-SSP

Page 30 © Copyright 2021 Dell Inc.

Troubleshooting Virtual Machine Backup

The following topics provide information about troubleshooting virtual machine

backup failures:

To learn how to resolve each possible failure, click each tab.

Lock placed on virtual machine

During the VM Direct backup and recovery operations, a lock is placed on the
virtual machine. If a VM Direct appliance failure occurs during one of these
sessions, the lock is extended to a period of 24 hours, during which full backups
and transaction log backups fail with the following error until the lock is manually
released:

Cannot lock VM 'W2K8R2-SQL-2014' (vm-522): Another EMC vProxy

operation 'Backup' is active on VM vm-522.

To manually release the lock on the virtual machine:

1. Open the vSphere Web Client.

2. Select the virtual machine and select Summary.
3. Select Custom attribute and click Edit.
4. Remove the attribute EMC vProxy Session.

SQL Server application-consistent backups fail

SQL Server application-consistent virtual machine backups might fail with the
following error when the disk.EnableUUID variable for the virtual machine is set
to False.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 31

Unable to find VSS metadata files in directory C:\Program
Files\DPSAPPS\MSVMAPPAGENT\tmp\VSSMetadata.xxxx.

To resolve this issue, ensure that the disk.EnableUUID variable for the virtual
machines included in an SQL Server application-consistent backup is set to True.

SQL application-aware backup displays an disk.EnableUUID error

A SQL Server application-aware virtual machine backup succeeds but displays the
following error when the disk.EnableUUID variable for the virtual machine is set
to TRUE:

VM '<asset_name>' configuration parameter 'disk.EnableUUID'

cannot be evaluated. Map item 'disk.EnableUUID' not found.
(1071)

To resolve this issue, after you set the disk.EnableUUID variable to TRUE,
reboot the virtual machine.

Delete vProxy/Search nodes

Perform the following procedure when you delete a vCenter server as an asset
source in PowerProtect Data Manager and you will not be re-adding the vCenter:

1. Run the following command to source the environment file:

a. source /opt/emc/vmdirect/unit/vmdirect.env

PowerProtect Data Manager Troubleshooting-SSP

Page 32 © Copyright 2021 Dell Inc.

2. For vProxy removal:
a. Obtain the list of vProxies that require removal by running
/opt/emc/vmdirect/bin/vproxymgmt get
b. Make note of the ID of any vProxy that needs to be deleted
c. Use the vproxymgmt tool to delete vProxies by running
/opt/emc/vmdirect/bin/vproxymgmt delete -
vproxy_id ProxyID
3. For Search Node removal:
a. Obtain the list of Search Nodes that require removal by running
/opt/emc/vmdirect/bin/infranodemgmt get
b. Make note of the ID of any Search Node that must be deleted
c. Use the infranodemgmt tool to delete Search Nodes by running
/opt/emc/vmdirect/bin/infranodemgmt
delete -node_id NodeID
4. In the PowerProtect Data Manager UI, ensure that any sessions have been
removed for both the vProxy/Search Node.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 33

Troubleshooting Virtual Machine Restore

PowerProtect Data Manager Troubleshooting-SSP

Page 34 © Copyright 2021 Dell Inc.

Troubleshooting Virtual Machine Restore

The following topics provide information about troubleshooting virtual machine

restore failures:

To learn how to resolve each possible failure, click each tab.

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 completes successfully.

• Check that the copy is not expired according to the PowerProtect Data Manager
protection policy.

Virtual machine Instant Access restore failures

An instant access restore consists of two stages. First, a virtual machine is made
available in the UI as an instant access virtual machine without moving the virtual
machine to permanent storage. Second, storage vMotion is initiated to migrate the
virtual machine to permanent storage.

If at any point during the migration a restore failure occurs, the instant access
session is not automatically removed until after the expiration period for an instant
access virtual machine restore, which is 7 days by default. This behavior is
intentional for the following reasons:

• To avoid data loss, since changes might have been made to the virtual machine
during that time.
• To provide you with the opportunity to fix the issue (for example, to free up
space on the restore destination or choose a different datastore) and then take
the appropriate action.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 35

When the cause of the failure is determined and/or fixed, you can use the Instant
Access Sessions window of the UI to retry the migration, or save the data and
delete the instant access virtual machine, as required.

Virtual machine restore fails with name resolution error

A virtual machine restore might fail with the following error due to network issues
between the PowerProtect DD system and PowerProtect Data Manager or the
vCenter/ESXi.

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 the PowerProtect DD
system and PowerProtect Data Manager, and vCenter/ESX.

DD NFS share is not removed after restores to original

The DD NFS share might not be removed after a successful virtual machine
restores to the original. When this occurs, the restore stops responding and the
following DD NFS clients appear enabled in the DD system.

Double-click the image to enlarge.

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.

PowerProtect Data Manager Troubleshooting-SSP

Page 36 © Copyright 2021 Dell Inc.

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.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 37

Troubleshooting Virtual Machine Restore

The following topics provide information about troubleshooting virtual machine

restore failures:

To learn how to resolve each possible failure, click each tab.

Virtual machine restore fails due to VM Direct corruption

A virtual machine restore might fail with the following error due to corruption of the
VM Direct that is running in PowerProtect Data Manager:

Ensure that the vproxyd service is running in PowerProtect Data Manager by typing
the command: ps xa | grep vproxy

Ensure that the VM Direct rpm is installed as expected in PowerProtect Data

Manager by typing the command: rpm -qa | grep vProxy

Log in as the root user, and restart the vproxyd service on PowerProtect Data
Manager by typing the command: systemctl restart vproxyd

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

A virtual machine restore fails with the error "User EARA 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 Export and Recovery Admin role.

PowerProtect Data Manager Troubleshooting-SSP

Page 38 © Copyright 2021 Dell Inc.

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

A virtual machine restore fails with the following error if the previous restore
operation for the same virtual machine is still in progress or did not complete
successfully:

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, you must
manually cancel the restore in PowerProtect Data Manager by restarting the Virtual
Machine Data Management (VMDM) service. VMDM is a PowerProtect internal
service which acts as an interface for Workflow Manager and VM Direct Engine.

You can restart the VMDM service by using the command,

/usr/local/brs/lib/vmdm/bin/ vmdm restart.

IP address change that is required after image-level restore

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.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 39

PowerProtect Data Manager Certification Map

The proven exam DES-3521 is required to earn the Specialist – Implementation

Engineer, PowerProtect Data Manager certification. The mentioned curriculum
includes on-demand courses and on-demand labs that enable you to acquires
various skills, such as deploy, configure, troubleshoot, integrate, and upgrade a
PowerProtect Data Manager solution.

You must complete 18 hours of on-demand courses and 4 hours of on-demand

labs before you attempt the DES-3521 proven exam. Also, when you register for
on-demand labs you get 24 hours access to complete each lab.

Product version in DES-3521 proven exam for PowerProtect Data Manager is 19.8.

PowerProtect Data Manager Troubleshooting-SSP

Page 40 © Copyright 2021 Dell Inc.

 Implementation Engineer, PowerProtect Data Manager

A. PowerProtect Concepts (C, VC, ODC)

B. PowerProtect Data Manager Concepts (C, VC, ODC)
C. PowerProtect Data Manager Features (C, VC, ODC)
D. PowerProtect Data Manager Implementation (C, VC, ODC)
E. PowerProtect Data Manager MS SQL Integration (C, VC, ODC)
F. PowerProtect Data Manager MS Exchange Integration (C, VC, ODC)
G. PowerProtect Data Manager VM Integration (C, VC, ODC)
H. PowerProtect Data Manager Oracle Integration (C, VC, ODC)
I. PowerProtect Data Manager SAP HANA Integration (C, VC, ODC)
J. PowerProtect Data Manager Kubernetes Integration (C, VC, ODC)
K. PowerProtect Data Manager Troubleshooting (C, VC, ODC)
L. PowerProtect Data Manager Upgrade (C, VC, ODC)
M. PowerProtect Data Manager Implementation On-Demand Lab (ODL)
N. PowerProtect Data Manager VM Integration On-Demand Lab (ODL)
O. PowerProtect Data Manager Oracle Integration On-Demand Lab (ODL)
P. PowerProtect Data Manager MS SQL Integration On-Demand Lab (ODL)
Q. PowerProtect Data Manager SAP HANA Integration On-Demand Lab (ODL)

Information Storage and Management Data Protection and Management

A. Information Storage and Management A. Data Protection and Management (ODC)

(C, VC, ODC)

(C) - Classroom

(VC) - Virtual Classroom

(ODC) - On Demand Course

(ODL) - On Demand Lab

For more information, browse: http://dell.com/certification

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 41

Course Completion

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 42

You Have Completed This eLearning.

Click the Save Progress and Exit button below to record this
eLearning as complete.
Go to the next eLearning or assessment, if applicable.

PowerProtect Data Manager Troubleshooting-SSP

© Copyright 2021 Dell Inc. Page 43