EMC DES-3128 Practice Test Questions Answers

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

The steps to create a client "ABO" to back up critical volumes for disaster recovery and to use the feature that allows for a single high-density file system to be split into multiple concurrent save sets are as follows:

Create the client:

On the NetWorker server, open the NetWorker Management Console.

Go to the Clients tab.

Click on the Add button.

In the Client Name field, enter "ABO".

In the Client Address field, enter the IP address or hostname of the client.

In the Platform field, select the appropriate platform for the client.

Click on the OK button to create the client.

Configure the client:

Go to the Clients tab.

Click on the ABO client.

Go to the File Systems tab.

Click on the Add button.

In the File System field, enter the path of the critical volume that needs to be backed up.

In the Save Set field, enter a name for the save set.

Check the Include all blocks that are in use option. This will ensure that all blocks that are in use in the file system are backed up.

Click on the OK button to add the file system.

Configure the save set:

Go to the Clients tab.

Click on the ABO client.

Go to the Save Sets tab.

Click on the save set that you just created.

Go to the Advanced tab.

In the Save Set Options field, enter "PSS:streams_per_ss=6". This tells NetWorker to split the save set into 6 concurrent save sets and send them simultaneously in a backup.

Click on the OK button to save the changes.

Schedule the backup:

Go to the Clients tab.

Click on the ABO client.

Go to the Schedules tab.

Click on the Add button.

Select the appropriate schedule for the backup.

In the Save Set field, select the save set that you just created.

Click on the OK button to schedule the backup.

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 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

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.