Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

PowerProtect Data Manager 19.13 Cyber Recovery User Guide

Meeting prerequisites for a PowerProtect Data Manager recovery

Ensure that the following prerequisites are met before you initiate a PowerProtect Data Manager recovery:

  • Note that if your Cyber Recovery deployment is on Amazon Web Services (AWS), a vCenter server is not required.
    NOTE: See the Dell PowerProtect Cyber Recovery AWS Deployment Guide for information about deploying and using the Cyber Recovery solution on AWS.
  • If you have updated your deployment to Cyber Recovery version 19.13, before you run a recovery, delete the snapshot that the Cyber Recovery software created for the vault PowerProtect Data Manager server.
  • Do not use PowerProtect DD Management Center (DDMC) to manage the production DD system.
  • Note that if NFS v4 is enabled on the DD system in the Cyber Recovery vault, a PowerProtect Data Manager recovery fails. The PowerProtect Data Manager server DR only supports NFS v3. Either use DD Boost for the server DR MTree or disable NFS v4 on the DD system in the Cyber Recovery vault when performing a recovery.
  • See the following documentation, which is available on the Customer Support website at https://www.dell.com/support:
    • The Preparing for and Recovering From a Disaster chapter in the PowerProtect Data Manager Administration and User Guide
    • PowerProtect Data Manager for Oracle RMAN Agent User Guide
    • PowerProtect Data Manager for Microsoft Application Agent SQL Server User Guide
  • Ensure that the Cyber Recovery vault DD system is running DD OS Version 6.2.1.50 or later.
  • Deploy the PowerProtect Data Manager appliance in the Cyber Recovery vault:
    • Only use the PowerProtect Data Manager appliance in the Cyber Recovery vault to perform recoveries.
    • Ensure that the version is the same as the version of the production system.
    • Note that the hostname and IP address of the PowerProtect Data Manager server in the Cyber Recovery vault do not have to match the hostname and IP address of the production PowerProtect Data Manager server.
    • Leave PowerProtect Data Manager in the default state. When you log in to PowerProtect Data Manager, the default state is either New Install or Restore Backup.
    • Do not modify the default passwords.
    • Modify the /etc/ssh/sshd_config file to enable password authentication:
      • Change the PasswordAuthentication field value from no to yes.
      • Run the service sshd restart command.
  • For on-premises deployments, do not use the following special characters in the VM name in vCenter, otherwise the Cyber Recovery software cannot detect the PowerProtect Data Manager VM:

    %, &, *, $, #, @, !, \, /, :, *, ?, ", <, >, [, ], |, ;, '

  • Ensure that the UIDs that are associated with the production PowerProtect Data Manager DD Boost users are available on the DD system in the Cyber Recovery vault.
  • Use either the Cyber Recovery UI or the CRCLI to define the PowerProtect Data Manager application as a Cyber Recovery application asset. When defining the PowerProtect Data Manager application:
    • Configure the application using the credentials of the PowerProtect Data Manager application on the production system.
    • For on-premises deployments, to be able to create a snapshot as part of the recovery procedure, use the same value for the FQDN or hostname that is shown in the vCenter user interface under the DNS name.
  • For on-premises deployments, ensure that there are no snapshots of the PowerProtect Data Manager virtual machine that is deployed in the vCenter server.
  • Create a Cyber Recovery policy for the VM data and DR backup.
  • Run application and DR backups in the PowerProtect Data Manager production environment. Then, perform a Secure Copy policy operation to copy data to the Cyber Recovery vault environment.
    NOTE: To recover a backup application from a Cyber Recovery copy properly, ensure that your replication window start time is after the application backup on the production system is completed, including the required metadata backup. For an intermediate replication on the production system, ensure that the intermediate replication start time is also after the production backup completion time.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\