Module 3 - PPDM Automated Recovery
This module provides an overview of the PPDM Automated Recovery using the Cyber Recovery UI
Vault PPDM Recovery
1
Login to a PPDM OVA deployment in the Vault that has a different hostname and IP address than the production PPDM server. From the desktop open the Google Chrome browser and click the **PPDM-Vault** link from bookmarks bar.
2
3
To Login type "admin" as the username and password "Password123!"
Production PPDM
In this lesson you will recover from a known good copy (which was analyzed by Cyber Detect and found that the copy is likely not infected) to a vault PPDM server
4
Access the Production PPDM through Chrome using the following credentials: **Username:** admin \ **Password:** Password123!
5
Navigate to **Protection --> Protection Policies**. \ Review that the **Linux_Pre-FS** Policy is writing **client.demo.local (/temp)** data to MTree **/data/col1/Linux_Pre-FS-ppdm-f954c** on the Production DD ddveprod.demo.local.
Data
6
We have already replicated the **Good** and **Infected** PPDM Data from Production to Vault DD and ran **Copy Lock** in Module 1.\ \ After that, we analyzed the copy using Cyber Detect and that new copy was **INFECTED**. We will use the previous available **GOOD** Copy to recover data in Vault PPDM server.
Add PPDM as Vault Application to CR
7
This lesson explains how to add a vault PPDM instance to Cyber Recovery. Although the vault PPDM is already configured in the current environment, the following steps can be used as a reference for future deployments.
8
Navigate to **Assets --> Applications** tab
9
Click **Add** to add the PPDM server using the following information: Application Type: **PPDM** Nickname : **PPDM-Vault** FQDN or IP Address: **ppdm.vault.local**
10
Click Next
11
Input the Application username and password, which are the current application credentials of the vault PPDM.\ \ Type "admin/ Password123!" and click on Verify Certificate
12
Click Accept
13
Click Done
14
Click Next
15
Input the post recovery application authentication details.\ \ Type "admin/ Password123!"\ \ Click Next
16
Click Finish
17
18
Vault PPDM added successfully.
PowerProtect Data Manager Automated Recovery
19
Navigate to the Recovery page to select the **PPDM-FS-Linux** policy **GOOD** copy and start the Recovery Process.
20
Navigate to the **Recovery** page and click on **Application.**
21
Select the Vault PowerProtect Data Manager Application as **Application Host**
22
Click "Focusing on remote session"
23
Click "Focusing on remote session"
24
Select the **PPDM-FS-Linux** policy **GOOD** copy and start the Recovery Process.
25
Navigate to Jobs page to see the Recovery job progress. It will take 15-30 minutes to complete the Job. Users can wait or proceed to the next module while PowerProtect Data Manager recovery is in progress.
26
Users can login to the CR Management Host and connect using SSH with the RoyalTS application in the taskbar to see the commands which are run in the background on Vault PPDM during the Recovery Process. Run the following command to watch the progress: **# tail -100f /opt/dellemc/cr/var/log/apps/apps.log**
27
Navigate back to the CR UI to check the Recovery progress. When the Recovery is completed:
Login to the recovered vault PPDM
28
Login again to the **Vault PPDM** server **ppdm.vault.local** to confirm that we are able to list the Protection Policies pointing to the Vault Data Domain storage **ddvevault.vault.local** Login to the Vault PPDM using the following credentials: \ **Username:** admin \ **Password:** Password123!
29
30
The Vault PPDM system will remain in **Restricted Mode** after the recovery and will have the Vault Data Domain for its Storage. All the scheduled workflows are disabled in **Restricted Mode**. Users can perform client recoveries inside the Vault using the Vault PPDM server before making the system **Fully Operational**.
31
Below steps shows the recovered Vault PPDM is capable of restoring the workloads backed up in Production.
32
Click "Focusing on remote session"
33
Click "Focusing on remote session"
34
Click "Focusing on remote session"
35
Click "Focusing on remote session"
36
Click "Focusing on remote session"
Cleaning up after a PPDM recovery
37
After the PPDM recovery operation is complete, Navigate to **Restore** and select **Recovery Sandboxes** option to perform cleanup. Select the sandboxes and click on "**Cleanup**"
38
Navigate to **Jobs** page to see the Recovery job progress. During this cleanup all sandboxes within application host Vault_PPDM will be permanently deleted and the system will be reverted to the snapshot created when recovery was initiated.
39
Successfully completed cleanup jobs:
Conclusion
40
This concludes the PPDM Automated Recovery Module. In case our Production data is compromised including the Production PPDM and DD, we can use the replicated copy on the Vault DD to perform a PPDM Automated Recovery. During the process, all the PPDM Protection Policies and client data will be recovered on the Vault PPDM server and users will be able to recover the data from the available client copies.
Module 3 - PPDM Automated Recovery
This module provides an overview of the PPDM Automated Recovery using the Cyber Recovery UI
Vault PPDM Recovery
1
Login to a PPDM OVA deployment in the Vault that has a different hostname and IP address than the production PPDM server. From the desktop open the Google Chrome browser and click the **PPDM-Vault** link from bookmarks bar.
2
3
To Login type "admin" as the username and password "Password123!"
Production PPDM
In this lesson you will recover from a known good copy (which was analyzed by Cyber Detect and found that the copy is likely not infected) to a vault PPDM server
4
Access the Production PPDM through Chrome using the following credentials: **Username:** admin \ **Password:** Password123!
5
Navigate to **Protection --> Protection Policies**. \ Review that the **Linux_Pre-FS** Policy is writing **client.demo.local (/temp)** data to MTree **/data/col1/Linux_Pre-FS-ppdm-f954c** on the Production DD ddveprod.demo.local.
Data
6
We have already replicated the **Good** and **Infected** PPDM Data from Production to Vault DD and ran **Copy Lock** in Module 1.\ \ After that, we analyzed the copy using Cyber Detect and that new copy was **INFECTED**. We will use the previous available **GOOD** Copy to recover data in Vault PPDM server.
Add PPDM as Vault Application to CR
7
This lesson explains how to add a vault PPDM instance to Cyber Recovery. Although the vault PPDM is already configured in the current environment, the following steps can be used as a reference for future deployments.
8
Navigate to **Assets --> Applications** tab
9
Click **Add** to add the PPDM server using the following information: Application Type: **PPDM** Nickname : **PPDM-Vault** FQDN or IP Address: **ppdm.vault.local**
10
Click Next
11
Input the Application username and password, which are the current application credentials of the vault PPDM.\ \ Type "admin/ Password123!" and click on Verify Certificate
12
Click Accept
13
Click Done
14
Click Next
15
Input the post recovery application authentication details.\ \ Type "admin/ Password123!"\ \ Click Next
16
Click Finish
17
18
Vault PPDM added successfully.
PowerProtect Data Manager Automated Recovery
19
Navigate to the Recovery page to select the **PPDM-FS-Linux** policy **GOOD** copy and start the Recovery Process.
20
Navigate to the **Recovery** page and click on **Application.**
21
Select the Vault PowerProtect Data Manager Application as **Application Host**
22
Click "Focusing on remote session"
23
Click "Focusing on remote session"
24
Select the **PPDM-FS-Linux** policy **GOOD** copy and start the Recovery Process.
25
Navigate to Jobs page to see the Recovery job progress. It will take 15-30 minutes to complete the Job. Users can wait or proceed to the next module while PowerProtect Data Manager recovery is in progress.
26
Users can login to the CR Management Host and connect using SSH with the RoyalTS application in the taskbar to see the commands which are run in the background on Vault PPDM during the Recovery Process. Run the following command to watch the progress: **# tail -100f /opt/dellemc/cr/var/log/apps/apps.log**
27
Navigate back to the CR UI to check the Recovery progress. When the Recovery is completed:
Login to the recovered vault PPDM
28
Login again to the **Vault PPDM** server **ppdm.vault.local** to confirm that we are able to list the Protection Policies pointing to the Vault Data Domain storage **ddvevault.vault.local** Login to the Vault PPDM using the following credentials: \ **Username:** admin \ **Password:** Password123!
29
30
The Vault PPDM system will remain in **Restricted Mode** after the recovery and will have the Vault Data Domain for its Storage. All the scheduled workflows are disabled in **Restricted Mode**. Users can perform client recoveries inside the Vault using the Vault PPDM server before making the system **Fully Operational**.
31
Below steps shows the recovered Vault PPDM is capable of restoring the workloads backed up in Production.
32
Click "Focusing on remote session"
33
Click "Focusing on remote session"
34
Click "Focusing on remote session"
35
Click "Focusing on remote session"
36
Click "Focusing on remote session"
Cleaning up after a PPDM recovery
37
After the PPDM recovery operation is complete, Navigate to **Restore** and select **Recovery Sandboxes** option to perform cleanup. Select the sandboxes and click on "**Cleanup**"
38
Navigate to **Jobs** page to see the Recovery job progress. During this cleanup all sandboxes within application host Vault_PPDM will be permanently deleted and the system will be reverted to the snapshot created when recovery was initiated.
39
Successfully completed cleanup jobs:
Conclusion
40
This concludes the PPDM Automated Recovery Module. In case our Production data is compromised including the Production PPDM and DD, we can use the replicated copy on the Vault DD to perform a PPDM Automated Recovery. During the process, all the PPDM Protection Policies and client data will be recovered on the Vault PPDM server and users will be able to recover the data from the available client copies.
