PowerProtect Data Manager 19.13 Cyber Recovery User Guide

Performing postrecovery steps for a PowerProtect Data Manager recovery

After the PowerProtect Data Manager recovery is completed, perform postrecovery steps.

1. To validate success, click Launch App to access the PowerProtect Data Manager UI in the Cyber Recovery vault.

   The Welcome to PowerProtect Data Manager window opens.

   NOTE: For Version 19.5 and later deployments, a PowerProtect Data Manager recovery disables all services. When you access the PowerProtect Data Manager UI after the recovery, it displays an alert that indicates that the services are not running. Click the alert to restart the services.
2. If the recovered PowerProtect Data Manager IP address or FQDN is the same as the production PowerProtect Data Manager system, you can perform on-demand manual protection jobs and also centralized restore and recovery of an application directly without manual intervention.
3. If the recovered PowerProtect Data Manager IP address or FQDN is not the same as on the production PowerProtect Data Manager system, verify the recovery for SQL, Oracle, and file system workloads:
   • For Windows deployments:
     1. Go to C:\Program Files\DPSAPPS\AgentService.
     2. Run the unregister.bat command to unregister the agent.
     3. If necessary, delete the ssl folder from the Agent Service folder.
     4. Run the register.bat command to register the host with PowerProtect Data Manager again.
     5. From the PowerProtect Data Manager Main Menu, go to Protection > Protection Policies. Select the policy and click Set Lockbox to run the configuration job again.
   • For Linux deployments:
     1. Go to /opt/dpsapps/agentservice.
     2. Run the unregister.sh command to unregister the agent.
     3. If necessary, delete the ssl folder from the Agent Service folder.
     4. Run the register.sh command to register the host with PowerProtect Data Manager again.
     5. From the PowerProtect Data Manager Main Menu, go to Protection > Protection Policies. Select the policy and click Set Lockbox to run the configuration job again.