PowerProtect is a deduplication solution from Dell EMC which is supported within a NetWorker environment. PowerProtect provides fast and efficient deduplication of data to reduce storage costs and improve backup performance. It is designed to be easy to use, with an intuitive user interface and support for multiple operating systems and applications.

References: [1] https://www.dell.com/support/manuals/us/en/04/dell-emc-networker-9-2/emc-networker-9.2.1.5/deduplication-installation-and-configuration-guide?guid=guid-d2b5f7d2-c2f1-4e14-b70d-fefa9b8f7f1f &lang=en-us [2] https://www.dell.com/support/article/en-us/sln299633/dell-emc-networker-powerprotect-deduplication-solution?lang=en

Block-Based Backup requires that the Igtobbb package is installed on the RHEL server. If this package is not installed, then the Block-Based Backup will fail. The other options are not related to the cause of the issue.

References: [1] https://www.veritas.com/support/en_US/article.100029778  [2] https://en.wikipedia.org/wiki/Veritas_NetBackup

To create a new NSR Client "ABC 123" and PSS file system backup save sets /data01 and /data02, and a skip files directive named "Skip GO" for * .go extensions anywhere under /data02, the administrator can use the Networker CLI (Command Line Interface) to access the Networker server and create the NSR Client, PSS file system backup save sets, and skip files directive. Here are the steps:

• Log in to the Networker CLI by entering the following command:

nsr_client -C ABC 123

• Once logged in, create a new PSS file system backup save set for /data01 by running the following command:

savefs -p -s /data01

• Create a new PSS file system backup save set for /data02 by running the following command:

savefs -p -s /data02

• Create a skip files directive named "Skip GO" for * .go extensions anywhere under /data02 by running the following command:

savefs -p -s /data02 -k "* .go"

• Verify that the new NSR client, PSS file system backup save sets and skip files directive have been created by running the following command:

nsr_client -l

• Verify that the new PSS file system backup save sets are correctly associated with the new NSR client by running the following command:

nsr_client -G ABC 123

The steps to resolve the issue of the client "ClientAB" not being in the backup server's clients list are as follows:

• Verify the client name:

• On the NetWorker server, open the NetWorker Management Console.
• Go to the Clients tab.
• Verify that the client "ClientA" is present in the list of clients.
• Verify that the client "ClientAB" is not present in the list of clients.

• Update the client name:

• On the NetWorker server, open the NetWorker Management Console.
• Go to the Clients tab.
• Click on the ClientA.
• In the Client Name field, update the name to "ClientAB"
• In the Client Address field, enter the IP address or hostname of the client.
• Click on the OK button to save the changes.

• Re-schedule the backup

• Go to the Clients tab.
• Click on the ClientAB.
• Go to the Schedules tab.
• Remove the current schedule and create a new schedule for the client.
• Select the appropriate schedule for the backup.
• In the Save Set field, select the save set that you need to backup.
• Click on the OK button to schedule the backup.

• Monitor the backup process

• Monitor the backup process to ensure that it is running successfully.
• Check the logs for any errors.

To troubleshoot why a customer cannot see any files backed up when a restore operation is attempted on their 3 new Linux server named Server01, the first step should be to check the log files for any error messages. The log files are typically located in the /var/log/ directory, but the exact location may vary depending on the operating system being used.

Next, the administrator should check the configuration of the NetWorker server to ensure that the server is configured correctly. This includes checking the client configuration for the Server01 and making sure that the correct client name is being used. Additionally, the administrator should make sure that the Server01 has the correct address and port information, as well as the correct credentials.

The administrator should also check the configuration of the server to make sure that the correct backup policies are being used and that the backup schedule is configured correctly. Additionally, they should check the configuration of the actual backup device, such as the tape library or disk array, to make sure that it is configured properly.

Finally, the administrator should check the filesystem of the Server01 to make sure that the backup files are actually being written to the correct location.

To create the desired configuration, you will need to use the Data Domain CLI (Command Line Interface) to access the DD Boost device and create the new appliance. Here are the steps:

• Log in to the Data Domain CLI by entering the following command:

ssh ddboost@DD0

• Enter the password "abc123" when prompted.
• Once logged in, create a new DD Boost device named DD01.SU01 by entering the following command:

ddboost device create --name DD01.SU01 --type vmware --pool DO.VMware_Pool

• Verify that the new device has been created by running the following command:

ddboost device show --name DD01.SU01

• Configure the DD Boost device to connect to the PowerProcted DO series appliance by running the following command:

ddboost device set --name DD01.SU01 --dd-host DD0

• Verify the configuration by running the following command:

ddboost device show --name DD01.SU01