Module 5 - NetWorker end to end workflow
NetWorker end to end workflow
This lesson will allow you to practice Cyber Recovery and CyberSense with NetWorker file-system backups. It covers everything from protecting files, replicating them to the vault and analyzing them with CyberSense, and then simulating a malware attack, analysis of the attacked data and gathering information about the attack using the CyberSense UI.
1
In this module you will run a NetWorker end-to-end workflow which includes:
\-Run a fresh backup of **client1.demo.local (/data)** using production NetWorker
\-Create a Cyber Recovery Policy
\-Secure Copy Analyze the data using Cyber Recovery and CyberSense
\-Run [infect.sh](http://infect.sh) script to infect the data in the **/data** directory on **client1.demo.local**
\-Run another backup of the infected data on **client1.demo.local (/data)** using production NetWorker
\-Secure Copy Analyze the data using Cyber Recovery and CyberSense
Recovery Sandbox cleaning from previous module
2
In case this lab session was used for the Networker Automated Recovery module, you need to delete the existing **NetWorker Recovery Sandbox** first:
3
In the Cyber Recovery UI, navigate to **Recovery --> Recovery Sandboxes**, select the NetWorker sandbox and click **Cleanup**
4
NetWorker Backup Settings Update
5
Login to Production NetWorker UI using Google Chrome bookmark **NetWorker-Prod**
6
Use the following credentials:
**Username:** administrator\
**Password:** Password123!
7
Navigate to **Protection** **--> Clients.**
Select **client1.demo.local** and click **Edit**
8
Scroll down in the **General** tab, and change the directory you will protect from **/temp** to **/data** in the Save Sets box.
Click **Save**
Change the Destination Pool
9
The file-system backup of client1.demo.local and the NetWorker Server DR backup are stored on a destination pool that's using the MTree /data/col1/NW-FS which is replicated to the vault. You used this replication context in the previous module.
In this module you'll use a different replication context (that is already created an initialized), but you will need to change the Destination Pool of the client1.demo.local and server DR backups so they are saved on the other MTree being replicated to the vault (**/data/col1/nve** on prod replicated to **/data/col1/nve-repl** on the vault)
10
Navigate to **Protection** **--> Policies**.
Click on **Filesystem**
11
Click on **Filesystem**
12
Select **Traditional: backup** and click **Edit**
13
Select the **Data Movement** tab, and change the destination pool from NW-FS to **Data Domain Default.**
Click **Save**
14
From the **Polices** page click on **Server Protection** to change the server DR destination pool
15
Click on **Server backup**
