LABS

v01: NBU10ADM - Lab 01: Introducing NetBackup (Linux)

3 Hr 49 Min Remaining

Instructions Resources Help 100%

Exercise A: Creating Users and Groups

Beginning with NetBackup 8.0, the NetBackup Master/Primary server includes a configured web server to support
critical backup operations. This web server operates under user account elements with limited privileges. These
user account elements must be available on each Master/Primary server.

In this exercise, you will create the users and groups required for installing the NetBackup Master/Primary server
software.

1. Sign in to the console system using the following credentials.

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the PuTTY shortcut located on the desktop of the console system.
3. In the PuTTY Configuration window, double-click the preconfigured entry for the Master/Primary
server, lnxmaster.vrtsedu.lab.
4. Log in to the lnxmaster.vrtsedu.lab system using the credentials below.
o Username: root
o Password: P@ssw0rd

5. In the root@lnxmaster:~ terminal window, execute the below command to create a user group.

Command: groupadd nbwebgrp

The above command returns no output. You will be returned to the shell prompt after the command is
executed.

6. Execute the below command to verify that the nbwebgrp user group has been created.

Command: getent group | grep -i nbwebgrp

7. Execute the below command to create a new user and add it to the nbwebgrp user group.

Command: useradd -G nbwebgrp -c 'NetBackup Web Management Console service user' -d /usr/openv/wmc
nbwebsvc

The above command returns no output. You will be returned to the shell prompt after the command is
executed.
8. Execute the below command to verify that the nbwebsvc user has been created and has been added to
the nbwebgrp user group.

Command: id nbwebsvc

The expected output of the above command is displayed below.

uid=1000 (nbwebsvc) gid=1001 (nbwebsvc) groups=1001 (nbwebsvc), 1000 (nbwebgrp)

Starting with NetBackup 10.0, NetBackup can run most of the Master/Primary server services as non-root,
which is highly encouraged.

In the next steps, you will create a new user account (nbsvc) which will be used as a service account for
running the NetBackup services on the Master/Primary server.

The nbwebsvc created earlier in this lab should not be used as the service user.

9. In the root@lnxmaster:~ terminal window, execute the below command to create a new user account for
running the NetBackup services on the Master/Primary server.

Command: useradd nbsvc

The above command returns no output. You will be returned to the shell prompt after the command is
executed.

10. Execute the below command to verify that the nbsvc user account has been created.

Command: id nbsvc

The expected output of the above command is displayed below.

uid=1001 (nbsvc) gid=1002 (nbsvc) groups=1002 (nbsvc)

11. Execute the below command to add user nbsvc to the nbwebgrp user group.

Command: usermod -G nbwebgrp nbsvc

The above command returns no output. You will be returned to the shell prompt after the command is
executed.

nbwebgrp must be set as the secondary group for the user that will be used for running services on the
NetBackup Master/Primary server. The nbwebgrp is set as the primary group, the installation might fail.

12. Execute the below command to verify that user nbsvc has been added to the nbwebgrp user group.

Command: id nbsvc
 The expected output of the above command is displayed below.

uid=1001 (nbsvc) gid=1002 (nbsvc) groups=1002 (nbsvc), 1000 (nbwebgrp)

13. Remain logged in to the lnxmaster.vrtsedu.lab system.

You will return to it later in this lab.

Exercise B: Installing the NetBackup Master/Primary Server Software

In this exercise, you install the NetBackup 10.0 Master/Primary server software on
the lnxmaster.vrtsedu.lab system.

The resources required to install the Master/Primary server software are copied in
the /NetBackup10.0_files directory on the lnxmaster.vrtsedu.lab system.

1. Access the root@lnxmaster:~ window that is open on the console system.

2. In the terminal window, execute the below command to change the current working directory
to NetBackup10.0_files.

Command: cd /NetBackup10.0_files

3. Execute the ls -l command to list the contents of the NetBackup10.0_files directory.

The expected output of the above command is displayed below.

total 192
dr-xr-xr-x. 2 root root 41 Jun 17 2:13 Doc
-r-xr-xr-x. 1 root root 25609 Jun 17 2:13 LICENSE
-r-xr-xr-x. 1 root root 14873 Jun 17 2:13 NBInstallAnswer-client.template
-r-xr-xr-x. 1 root root 8570 Jun 17 2:13 NBInstallAnswer-master.template
-r-xr-xr-x. 1 root root 12841 Jun 17 2:13 NBInstallAnswer-media.template
-r-xr-xr-x. 1 root root 114483 Jun 17 2:13 install
-rw-r--r--. 1 root root 50 Jun 21 14:05 license.txt
dr-xr-xr-x. 4 root root 32 Jun 17 2:14 linuxR_x86
-rw-r--r--. 1 root root 1273 Jun 21 14:05 veritas_customer_registration_key.json

The license.txt file contains the NetBackup 10.0 license key and the veritas_customer_registration_key file
contains the Veritas Usage Insights registration key in JSON format.

If the license.txt and the veritas_customer_registration_key files are not present in

the NetBackup10.0_files directory, execute the /edu/scripts/lic.sh command to download these files.

4. Execute the below command to start the NetBackup installer.

 Command: ./install

5. At the Do you wish to continue prompt, type y and press Enter.

6. At the Is this host the master server prompt, type y and press Enter.
7. When asked if you are performing a disaster recovery of a Master/Primary server, type n and press Enter.
8. When asked to enter the name of the service account to be used to start the daemons, type nbsvc and
press Enter.

The nbsvc service account was created earlier in this lab.

9. When asked to enter the path for the customer registration key,
enter /NetBackup10.0_files/veritas_customer_registration_key.json and press Enter.
10. At the Do you want to install NetBackup and Media Manager files prompt, type y and press Enter to
continue.

At this point, the installer starts to install the NetBackup packages.

This process might take 10-12 minutes to complete.

After the NetBackup packages are installed, you will be asked to enter the NetBackup license key.

11. When asked to enter the license key, minimize (do not close) the root@lnxmaster:~ window.

You will return to it later in this lab.

12. Double-click the Command Prompt shortcut located on the desktop of the console system.
13. In the Administrator: Command Prompt window, execute the below command to copy the NetBackup
license key to your clipboard.

*Command: plink -ssh lnxmaster.vrtsedu.lab -l root -pw P@ssw0rd -batch "cat

/NetBackup10.0_files/license.txt" | clip

14. After executing the above command, minimize the Administrator: Command Prompt window.
15. Access the root@lnxmaster:~ window that is open on the console system.
16. In the root@lnxmaster:~ window, right-click to paste the license key from the clipboard.
17. At the Do you want to add additional license keys now prompt, type n and press Enter.
18. When asked if you want to use lnxmaster.vrtsedu.lab as the NetBackup server name, press Enter to
continue.

Incorrect information for the domain name results in failures during the configuration of Authentication
Broker and NetBackup Access Controls

19. At the Do you want to add any media servers now prompt, type y and press Enter.
20. When asked to enter the FQDN of the Media Server, enter the below server name and press Enter.

Media server: lnxmedia.vrtsedu.lab

After the first Media Server is added, the Enter the fully qualified name of a media server prompt is
returned. This allows you to add more than one Media Server.

21. Type q and press Enter at the Enter the fully qualified name of a media server prompt to continue
without adding additional Media Servers.

At this point, the:

o NetBackup database and the authorization database is created.

o NetBackup Authentication (nbatd) service is configured and started.
o Required certificates are deployed and a few NetBackup services are started.
It might 3-5 minutes for the above to complete.

22. When asked if you want to start the job-related NetBackup daemons, type y and press Enter.

Wait for the job-related services to start.

After the job-related services are started, you will be asked to enter the OpsCenter server name.

23. At the Enter the OpsCenter server prompt, enter the below server name and press Enter.

OpsCenter server: console.vrtsedu.lab

The installation completes after registering the OpsCenter server with NetBackup and messages similar to the
following are displayed.

NetBackup server installation complete. Running install analysis tool.

File /usr/openv/tmp/install_trace.xxxx contains a trace of this install. That

file can be deleted after you are sure the install was successful.

24. In the terminal window, execute the below command to check the status of all NetBackup services.

Command: /usr/openv/netbackup/bin/bpps -x

25. Review the output of the above command.

Note that the service account for most of the NetBackup services has been set to nbsvc.

To change the service account after the installation is complete, use the nbserviceusercmd --
changeUser command. This command is located in the /usr/openv/netbackup/bin/goodies directory.
26. Execute the below command to view the contents of the bp.conf file.

Command: cat /usr/openv/netbackup/bp.conf

27. Review the configuration information available in the bp.conf file.

28. Type exit and press Enter to log out of the lnxmaster.vrtsedu.lab system.

The root@lnxmaster:~ window is closed and you are returned to the desktop of the console system.

Exercise C: Installing the NetBackup Java Remote Administration Console

In this exercise, you will install the NetBackup Java Remote Administration Console on the console system.

1. Access the desktop of the console system.

2. Double-click the File Explorer shortcut located on the desktop of the console system.
3. Navigate to Downloads folder and double-click the NetBackup_10.0_win folder to view its contents.
4. When the contents of the folder are displayed, double-click the Browser.exe file to start the NetBackup
installer.
5. In the Veritas DVD Browser window, in the navigation pane, click Installation.
6. On the Installation screen, click the NetBackup Java Remote Administration Console Installation link.
7. In the Veritas NetBackup dialog box, read the warning message that is displayed and click Yes to
continue.

The NetBackup Java Remote Administration Console window is displayed.

8. In the NetBackup Java Remote Administration Console window, on the Welcome screen, read the
information that is displayed and click Next.
9. On the License Agreement screen, perform the following:

a. Read the Veritas Software License Agreement.

b. Select the Agree with the Veritas Software License Agreement radio button.

c. Click Next.

10. On the Install Type screen, ensure that the Install to this computer only and the Typical
Installation radio buttons are selected and click Next.

The Custom installation option available on the Install Type screen enables you to:

o Change the installation directory.

 o Change the service account and startup options.
o Select safe abort for reboot cases.

11. On the Ready to Install screen, ensure that the settings are as expected and click Install to start the
installation.

The installation might take 5-7 minutes to complete.

Wait for this installation to complete before proceeding.

12. After the installation is complete, click Finish to close the NetBackup Java Remote Administration
Console window.
13. Close the Veritas DVD Browser window.
14. Minimize (do not close) the This PC explorer window.

You will return to it later in this lab.

Exercise D: Installing the NetBackup Media Server Software

In this exercise, you will install the NetBackup Media Server software on the lnxmedia.vrtsedu.lab system.

1. Access the desktop of the console system.

2. Double-click the PuTTY shortcut located on the desktop of the console system.
3. In the PuTTY Configuration window, double-click the preconfigured entry for the Master/Primary
server, lnxmedia.vrtsedu.lab.
o Username: root
o Password: P@ssw0rd

4. In the root@lnxmedia:~ terminal window, execute the below command to change the current working
directory to NetBackup_10.0_files.

Command: cd /NetBackup10.0_files

5. Execute the ls -l command to list the contents of the NetBackup10.0_files directory.

The output of the above command should be similar to the one displayed below.

total 192
dr-xr-xr-x. 2 root root 41 Jun 17 2:16 Doc
-r-xr-xr-x. 1 root root 25609 Jun 17 2:16 LICENSE
-r-xr-xr-x. 1 root root 14873 Jun 17 2:16 NBInstallAnswer-client.template
-r-xr-xr-x. 1 root root 8570 Jun 17 2:16 NBInstallAnswer-master.template
 -r-xr-xr-x. 1 root root 12841 Jun 17 2:16 NBInstallAnswer-media.template
-r-xr-xr-x. 1 root root 114483 Jun 17 2:16 install
-rw-r--r--. 1 root root 50 Jun 21 14:04 license.txt
dr-xr-xr-x. 4 root root 32 Jun 17 2:14 linuxR_x86

The license.txt file contains the NetBackup 10.0 license key.

If the license.txt file is not present in the NetBackup_10.0_files directory, execute

the /edu/scripts/lic.sh command to download it.

6. Execute the below command to start the NetBackup installer.

Command: ./install

7. At the Do you wish to continue prompt, type y and press Enter.

8. At the Is this host the master server prompt, type n and press Enter.
9. When asked if you want to use lnxmedia.vrtsedu.lab as the NetBackup server name, press Enter to
continue.
10. When asked to enter the FQDN of the Master/Primary server, enter the below server name and
press Enter.

Master/Primary server: lnxmaster.vrtsedu.lab

11. At the Do you want to install NetBackup and Media Manager files prompt, type y and press Enter to
continue.

At this point, the CA certificate is retrieved from the Master/Primary server and you are asked to verify the
fingerprint for the retrieved certificate.

12. At the Is this correct prompt, type y and press Enter to confirm the certificate fingerprint for the
Master/Primary server, lnxmaster.vrtsedu.lab.

After you confirm the certificate fingerprint, the host certificate for the Media Server, lnxmedia.vrtsedu.lab is
generated and saved in the NetBackup certstore on the Media Server.

You can execute the nbcertcmd -listcacertdetails command on the Master/Primary server to validate the CA
certificate fingerprint that is retrieved.

You will learn about NetBackup CA and external certificates in the NetBackup Certificate
Administration lesson.

13. When asked if you want to install Java GUI and JRE, type 2 and press Enter to exclude the Java GUI and
JRE installation.

At this point, the installer starts to install the NetBackup packages.

 This process might take 5-7 minutes to complete.

After the NetBackup packages are installed, you will be asked to enter the NetBackup license key.

14. When asked to enter the license key, minimize (do not close) the root@lnxmedia:~ window.

You will return to it later in this lab.

15. Access the Administrator: Command Prompt window that is open on the console system.
16. In the Administrator: Command Prompt window, execute the below command to copy the NetBackup
license key to your clipboard.

*Command: plink -ssh lnxmedia.vrtsedu.lab -l root -pw P@ssw0rd -batch "cat

/NetBackup10.0_files/license.txt" | clip

17. After executing the above command, minimize (do not close) the Administrator: Command
Prompt window.

You will return to it later in this lab.

18. Access the root@lnxmedia:~ window that is open on the console system.
19. In the root@lnxmedia:~ window, right-click to paste the license key from the clipboard.
20. At the Do you want to add additional license keys now prompt, type n and press Enter.

The installation completes after starting the NetBackup services and messages similar to the following are
displayed.

NetBackup server installation complete. Running install analysis tool.

File /usr/openv/tmp/install_trace.xxxx contains a trace of this install. That

file can be deleted after you are sure the install was successful.

21. In the terminal window, execute the below command to check the status of all NetBackup services.

Command: /usr/openv/netbackup/bin/bpps -x

22. Review the output of the above command.

23. Execute the below command to view the contents of the bp.conf file.

Command: cat /usr/openv/netbackup/bp.conf

24. Review the configuration information available in the bp.conf file.

25. Type exit and press Enter to log out of the lnxmedia.vrtsedu.lab system.
 The root@lnxmedia:~ window is closed automatically and you are returned to the desktop of
the console system.

Exercise E: Installing the NetBackup Client Software

In this exercise, you will install the NetBackup Client software on the console.vrtsedu.lab system.

1. Access the desktop of the console system.

2. Access the This PC file explorer window that is open on the console system.
3. Navigate to Downloads folder and double-click the NetBackup_10.0_Win folder to view its contents.
4. Double-click Browser.exe file to start the NetBackup installer.
5. In the Veritas DVD Browser window, in the navigation pane, click Installation.
6. On the Installation screen, click the NetBackup Client Software Installation link.
7. In the Veritas NetBackup dialog box, read the warning message that is displayed and click Yes to
continue.

The Veritas NetBackup Client window is displayed.

8. In the Veritas NetBackup Client window, on the Welcome screen, read the information that is displayed
and click Next.
9. On the License Agreement screen, perform the following:

a. Read the Veritas Software License Agreement.

b. Select the Agree with the Veritas Software License Agreement button.

c. Click Next.

10. On the Install Type screen, ensure that the Install to this computer only and the Typical
Installation radio buttons are selected and click Next.

The Custom installation option available on the Install Type screen enables you to:

o Change the installation directory.

o Change the service account and startup options.
o Select safe abort for reboot cases.

11. On the NetBackup System Names screen, perform the following:

. Ensure that console.vrtsedu.lab is displayed in the Client Name field.

a. Enter lnxmaster.vrtsedu.lab in the Master Server Name field.

 b. Enter lnxmedia.vrtsedu.lab in the Additional Servers field.

c. Click Next.

At this point, the CA certificate is retrieved from the Master/Primary server and you are asked to verify the
fingerprint for the retrieved certificate.

12. On the NetBackup Certificate screen, select the I recognize the fingerprint for this host… radio button
and then click Next.

After you confirm the certificate fingerprint, the CA certificate is saved in the NetBackup certstore on the
client.

You can execute the nbcertcmd -listcacertdetails command on the Master/Primary server to validate the CA
certificate fingerprint that is retrieved.
You will learn about NetBackup CA and external certificates in the NetBackup Certificate
Administration lesson.

13. When asked to enter the authorization token, minimize (do not close) the Veritas NetBackup
Client window.

You will return to it later in this lab.

14. Access the Administrator: Command Prompt window that is open on the console system.
15. In the Administrator: Command Prompt window, execute the below command to generate and copy
the authorization token to your clipboard.

Command: powershell -File C:\Automation\Scripts\get-token.ps1 | clip

16. After executing the above command, close the Administrator: Command Prompt window.
17. Access the Veritas NetBackup Client window that is open on the console system.
18. On the Authorization Token screen, right-click in the Token field and then click Paste to paste the
authorization token from the clipboard.

In this lab, a script is used to generate the authorization token. In a later lab, you will learn to generate the
authorization and reissue tokens using the NetBackup web user interface.

If you continue without an authorization token, a host certificate for the client is not generated during the
install and must be generated manually after the install to allow communication between the client and the
NetBackup Master/Primary server.

19. After pasting the authorization token in the Token field, click Next to proceed.

At this point, a host certificate is generated for the client and saved in the NetBackup certstore on the client.
 You will learn about host certificates in the NetBackup Certificate Administration lesson.

20. On the Security Certificate Status screen, verify that the host certificate has been deployed successfully
and click Next.
21. On the Ready to Install screen, ensure that the settings are as expected and click Install to start the
installation.

The installation might take 5-7 minutes to complete.

Wait for the installation to complete before proceeding.

22. After the installation is complete, click Finish to close the Veritas NetBackup Client window.
23. Close the Veritas DVD Browser window.
24. Close the This PC explorer window.

Exercise F: Exploring the NetBackup Administration Console

In this exercise, you will locate and identify the tasks the can be performed using the NetBackup Administration
Console by viewing the layout of the user interface.

1. Access the desktop of the console system.

2. Double-click the File Explorer shortcut located on the desktop of the console system.
3. In the This PC explorer window, navigate to C:\Program Files\Veritas\Java.
4. Double-click the nbjava.bat file located in the C:\Program Files\Veritas\Java directory to launch
the NetBackup Administration Console.

After installing the NetBackup Java Remote Administration Console a shortcut for accessing
the NetBackup Administration Console is created in the C:\ProgramData\Microsoft\Windows\Start
Menu\Programs\Veritas NetBackup folder and can be used to access the NetBackup Administration
Console.
Do not close the Command Prompt window that is launched with the NetBackup Administration
Console as doing so will close the NetBackup Administration Console.

5. In the NetBackup Administration Console window, perform the following:

a. Change Host name to lnxmaster.vrtsedu.lab.

When you launch the NetBackup Administration Console for the first time, the Host name defaults to
the hostname of the system where the administration console is launched.

b. In the Login using section, ensure that the User name and password radio button is selected.
 c. Enter root in the User name field and P@ssw0rd in the Password field.
d. Click Login.
6. In the NetBackup Administration Console dialog box, read the warning message that is displayed and
click Yes to continue.

The NetBackup Administration Console is divided into three sections. The toolbar, the object tree, and the
details view.

The object tree contains various navigation branches. The details pane contains the configuration wizards and
details specific to the utility that is selected in the object tree. The toolbar contains shortcuts for menu
commands.

7. Collapse all entries in the left pane (object tree) of the Administration Console – so that a minimum
number of entries are displayed.

After the entries in the object tree are collapsed, the object tree should look similar to the following:

lnxmaster.vrtsedu.lab (Master server)

Backup, Archive, and Restore

Activity Monitor

NetBackup Management

Media and Device Management

Security Management

Deployment Management

Vault Management

Bare Metal Restore Management

Logging Assistant
 When the Master/Primary server entry is selected in the object tree, the details pane displays the following
wizards:

Wizard Description:

Getting Started Used to configure NetBackup for the first time.

Configure Storage Devices Used to configure tape storage.

Configure Disk Storage Servers Used to configure Disk storage servers.

Configure Cloud Storage Server Used to configure Cloud Storage servers.

Configure Disk Pool Used to configure disk pools.

Used to perform inventory or create volumes for use in standalone

Configure Volumes
tape drives.

Configure the Catalog Backup Used to configure a catalog backup.

Create a Policy Used to configure backup policies.

Recover the catalogs Used to recover catalogs.

Introducing Veritas NetInsights Used to access the NetInsights Console or the NetBackup web user
Console interface.

8. In the object tree, click Backup, Archive, and Restore.

The Backup, Archive, and Restore console is displayed in the details pane and allows you to perform user
initiated backups, restores, and view progress of user initiated backups or restores.

9. In the object tree, click Activity Monitor.

The Activity Monitor is displayed in the details pane and is used for monitoring active, completed, or failed
jobs of all types.
10. In the object tree, expand the NetBackup Management node.

From the NetBackup Management node, you can perform the following:

o Run NetBackup reports.

o Create and manage backup policies.
o Create and manage storage units, storage unit groups, storage lifecycle policies, and SLP windows.
o Search backup images in the NetBackup catalog and perform verify, duplicate, or import operations.
o View and configure host properties for the NetBackup Master/Primary, Media, and Client servers.
o Manage application instances (Oracle and Microsoft SQL Server only).

11. In the object, expand the Media and Device Management node.

The Media and Device Management contains utilities used to manage the volumes, pools, and devices that
NetBackup uses to store backups. You can also configure credentials for NDMP hosts, Snapshot management
servers, virtual machine servers, and so on.

12. In the object tree, expand the Security Management node.

What operations can be performed from the Security Management node?

The Security Management node allows you to perform the following:

o View security events.

o Manage hosts mappings.
o View host certificates and create security tokens.
o Configure global security settings and set disaster recovery passphrase.
o Configure access management.

13. In the object tree, expand the Deployment Management node.

You can create or manage deployment polices from the deployment management node. Deployment policies
can be used to update NetBackup Clients and Media Servers.

14. In the object tree, click Vault Management.

If Vault Robots are configured, they are displayed and can be managed from the details pane.

Vault is an extension to NetBackup that automates selection and duplication of backup images. It also
automates ejection of media for transfer to and from a separate, off-site storage facility.

15. In the object tree, expand the Bare Metal Restore Management node.

BMR related operations like configuring boot servers, creating shared resource trees, perform VM
conversions, and so on can be performed from the Bare Metal Restore Management node.
 16. In the object tree, click Logging Assistant.

You can create support logs using the Logging Assistant. A Logging Assistant record is used throughout
the process of troubleshooting a NetBackup problem.

You will use the NetBackup Administration Console and the NetBackup web user interface (covered in the
next lesson) throughout this course for performing NetBackup administration tasks.

17. Close the NetBackup Administration Console and log out of the console system.

Lab 02: Working with the NetBackup Web UI

Exercise A: Accessing and Navigating the NetBackup Web User Interface

In this exercise, you access and familiarize yourself with the NetBackup web user interface.

Accessing the NetBackup web user interface

1. Sign in to the console system using the following credentials:

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system to
launch the NetBackup web user interface.

The Netbackup web user interface can be accessed by navigating to the following URL:
https://Primary server hostname or IP/webui/login.
For the purpose of this lab, a web shortcut is preconfigured for accessing the NetBackup web user interface.

3. If a security warning is displayed, click Advanced > Accept the Risk and Continue.
4. Sign in to the NetBackup web user interface using the following credentials:
o Username: root
o Password: P@ssw0rd

Navigating the NetBackup web user interface

When you sign into the NetBackup web user interface for the first time, a Welcome to Veritas NetBackup splash
page is displayed. The splash page includes shortcuts for configuring storage, discovering assets, creating
protection plans, and so on.
5. If the Welcome to Veritas NetBackup splash page is displayed, click X to close the splash page.

When a user logs into the NetBackup web user interface, a Dashboard including the following dashboard
widgets is displayed by default:

o JOBS
o MALWARE DETECTION
o ANOMALY DETECTION
o CERTIFICATES
o TOKENS
o USAGE REPORTING
o SECURITY EVENTS
The USAGE REPORTING dashboard is displayed only after closing the Veritas NetInsights Console widget.

6. Review the information that is displayed in each dashboard widget.

Some of the dashboard widgets might not display any information at this time.

7. In the NetBackup web user interface, in the navigation pane, click Activity monitor.

The Activity monitor page is displayed and includes the following tabs:

o Jobs - Displays a list of all backup jobs.

o Daemons - Displays a list of all NetBackup Daemons and their status.
o Processes - Displays a list of all NetBackup processes along with the PID, Start time, and the Process
size (MB).
o Background tasks -Displays a list of background tasks (if any).

To view detailed status for a job, click the job id displayed in the Job ID column or select the job and
click the View details option.

8. Review the information and options displayed on the Activity monitor page.
9. In the NetBackup web user interface, in the navigation pane, click Recovery.

The Recover page is displayed and allows you to start a new restore.

Currently, recovery can be performed only for Standard and MS-Windows and Universal-Share policy
types.

10. In the navigation pane, click Protection > Protection plans.

The Protection plans page is displayed in the right pane of the NetBackup web user interface. You can view
existing protection plans or create a new protection plan on the Protection plans page.
11. On the Protection plans page, click Add.
12. On the Create protection plan page, click the Workload drop-down list to view the available options.

What options are displayed in the Workload drop-down list?

The workload drop-down list displays the following options:

o Cloud
o Microsoft SQL Server
o AHV
o Red Hat Virtualization
o VMware
o Kubernetes
Currently, the NetBackup web user interface allows creating a protection plan only for the above listed
workloads.

13. In the navigation pane, click Protection > Policies.

The Policies page is displayed in the right pane of the NetBackup web user interface. You can view existing
NetBackup classic policies or create new policies on this page. To view details of an existing policy (Attributes,
Schedules, etc.), click the policy name displayed in the Name column.

14. On the Policies page, click Add.

15. On the Create policy page, in the Attributes tab, click the Policy type drop-down list to view the
available options.

What options are displayed in the Policy type drop-down list?

The Policy type drop-down list displays the following options:

o MS-Windows
o Standard
o MS-SQL-Server
o Oracle
o NDMP
o VMware
o Universal-Share
Currently, the NetBackup web user interface allows creating classic policies only for the above listed policy
types.

16. In the NetBackup web user interface, in the navigation pane, expand the Workloads node.
 What options are available under the Workloads node?

The Workloads node in the NetBackup web user interface provides the ability to add and
manage Oracle, SaaS,Microsoft SQL Server, VMware, RHV, Cloud, Nutanix AHV, OpenStack,
and Kubernetes workloads.

17. In the NetBackup web user interface, in the navigation pane, click Storage > Storage configuration.

The Storage configuration page is displayed and includes the following tabs:

o Storage servers - View details of existing storage servers or create new storage servers.
o Disk pools - View details of existing disk pools or create new disk pools.
o Storage units - View details of existing storage units or create new storage units.
o Universal shares - View details of existing universal shares or create new universal shares.

18. On the Storage configuration page, select the Storage servers tab and then click Add.

What type of storage can be configured using the NetBackup web user interface?

The NetBackup web user interface allows you to configure AdvancedDisk, Cloud, Media Server
Deduplication Pool (MSDP), and OpenStorage storage servers, disk pools, and storage units. It also allows
you to configure MSDP for image sharing.

19. In the NetBackup web user interface, in the navigation pane, click Storage > Storage lifecycle policies.

The Storage lifecycle policies page is displayed and allows you to view or edit existing or configure
new Storage lifecycle policies. It also allows you to configured SLP windows for Storage lifecycle policies.

20. In the navigation pane, click Credential management.

The Credential management page is displayed and provides the ability to create and manage credentials for
the following systems:

o An external key management service (KMS) server

o Microsoft SQL Server
o Cloud instance
o Kubernetes
o AHV
o Callhome proxy
o NDMP

21. In the navigation pane, click Resiliency.

The Resiliency page is displayed and allows to integrate Veritas NetBackup with Veritas Resiliency
Platform to manage your disaster recovery operations.
 Integrating NetBackup and Resiliency Platform lets you leverage the capabilities, such as complete
automation, visualizing and monitoring DR specific information for all resiliency operations for the virtual
machines in your data center.

22. In the navigation pane, expand the Security node.

What options are available under the Security node?

The Security node in the NetBackup web user interface provides the ability to:

o Manage role-based access control.

o Manage security certificates.
o View security events and audit logs.
o Manage hosts.
o Manage tokens.
o Create API keys.
o Manage user sessions.
Some of these operations are discussed in detail in a later lab.

23. In the navigation pane, click Usage.

The Usage reporting page displays usage details of the Master/Primary servers in your environment.It also
includes a shortcut to access the Veritas NetInsights Console.

No information might be displayed on the Usage reporting page at this time.

24. Minimize the Mozilla firefox window to return to the desktop of the console system.

Do not log out of the NetBackup web user interface or close the browser window, you will return to it later in
this lab.

Exercise B: Configuring Role-based Access Control

In this exercise, you authenticate an active directory domain with NetBackup, create a new RBAC role, and add
domain users to the new RBAC role.

Adding an active directory domain in NetBackup

1. Double-click the PuTTY shortcut located on the desktop of the console system.
2. In the PuTTY configuration window, double-click the preconfigured entry for the Master/Primary
server,lnxmaster.vrtsedu.lab.
3. Log in to the lnxmaster.vrtsedu.lab system using the following credentials:
o Username: root
o Password: P@ssw0rd

4. In the root@lnxmaster:~ terminal window, execute the following command to authenticate the active
directory domain with NetBackup.

Command: vssat addldapdomain -d vrtsedu.lab -s ldap://vrtsedu.lab -u "DC=vrtsedu,DC=lab" -g

"DC=vrtsedu,DC=lab" -m "CN=Administrator,CN=Users,DC=vrtsedu,DC=lab" -t msad

The vssat command is located in the /usr/openv/netbackup/sec/at/bin directory on the

Master/Primary server, lnxmaster.vrtsedu.lab. In this lab environment, this directory is added to
the PATH variable on the lnxmaster.vrtsedu.lab system and therefore the command can be executed
without using the absolute path.

5. When prompted for the password, enter P@ssw0rd as the password and press Enter.

The expected output of the above command is displayed below:

Using data dir: /usr/openv/var/global/vxss/eab/data

Enter password for CN=Administrator,CN=Users,DC=vrtsedu,DC=lab:
Successfully added LDAP domain.

6. Verify that the ldap domain was added successfully by executing the below command:

Command: vssat listldapdomains

The expected output of the above command is displayed below:

Using data dir: /usr/openv/var/global/vxss/eab/data

listldapdomains
---------------------
---------------------

Found: 1

Domain Name : vrtsedu.lab

Server URL : ldap://vrtsedu.lab
SSL Enabled : No
Schema Type : msad
User Base DN : DC=vrtsedu,DC=lab
User Object Class : user
User Attribute : sAMAccountName
User GID Attribute : memberOf
User Display Name Attribute : objectSid
User Description Attribute : description
 Group Base DN : DC=vrtsedu,DC=lab
Group Object Class : group
Group Attribute : sAMAccountName
Group GID Attribute : cn
Group Display Name Attribute : displayName
Group ID Attribute : objectSid
Group Description Attribute : description
Group GID Attribute Type :
Auth Type : BOB
Admin User : CN=Administrator,CN=Users,DC=vrtsedu,DC=lab
Admin User Password :
Search Scope : SUB

7. In the terminal window, type clear and press Enter to clear the screen.
8. Minimize the root@lnxmaster:~ window to return the desktop of the console system.

Do not close the root@lnxmaster:~ window, you will return to it later in this lab.

Creating a new RBAC role

9. Access the NetBackup web user interface that is open on the console system.
10. In the NetBackup web user interface, in the navigation pane, click Security > RBAC.

The Role-based access control page is displayed and lists the default RBAC roles available with NetBackup
10.0.

11. Read the description for the default RBAC roles to understand the capabilities the role provides.
12. On the Role-based access control page, click Add to create a new RBAC role.

The Add role page, you can select one of the default roles as a template for creating the new role. For the
purpose of this lab, we are going to create a custom role so that we can assign permissions manually.

13. On the Add role page, click the Custom role radio button and then click Next.

Assigning role permissions

14. Enter AD-users in the Role name field and click Assign on the Select permissions card.
15. On the Assign permissions page, click the Global tab and then select the following permissions:
o All permissions listed under the NetBackup Management category.
o All permissions listed under the Protection category.
o All permissions listed under the Storage category.

16. On the Assign permissions page, click the Assets tab and then select all permissions for VMware assets.
17. On the Assign permissions page, click the Protection plans tab and select all permissions for Protection
plans.
18. On the Assign permissions page, click Assign to assign the selected permissions to the role.
19. On the Add role page, Verify that Assets, Protection plans, and Global permissions are displayed on
the Select permissions card.
20. On the Add role page, click Assign on the Select workloads card.

The cards on the Add role page are enabled only if relevant permissions are selected. For example, the Select
workloads and Select protection plans cards are enabled only after selecting Asset and Protection
plan permissions.

21. On the Assign assets page, click the VMware tab, select the Apply select permissions to all future
VMware Assets option, and click Assign.

Access to particular assets can be restricted on the Assign assets page but for the purpose of this lab, we will
apply permissions to all assets.

22. On the Add role page, click Assign on the Select protection plans card.
23. On the Assign protection plans page, select the Apply permissions to new and existing protection
plans option and click Assign.

Access to particular protection plans can be restricted on the Assign protection plans page but for the
purpose of this lab, we will apply permissions to all protection plans.

Adding domain users to the new RBAC role

24. On the Add role page, click Assign on the Users card.
25. On the Assign users page, enter RAAdams@vrtsedu.lab in the User or group field and click Add to
list to add user Ryan Adams to the RBAC role.

When adding domain users to a RBAC role, the user principal name should be used.

26. On the Assign users page, enter Engineering@vrtsedu.lab in the User or group field and click Add to
list to add the Engineering group to the RBAC role.

When adding domain groups to a RBAC role, the group email should be used.

27. On the Assign users page, verify that user RAAdams and group Engineering are listed.
28. On the Assign users page, click Assign.
29. On the Add role page, click Add role to add the new RBAC role.
30. On the Add role page, verify that the role configuration was successful and click Close to return to
the Role-based access control page.
31. On the Role-based access control page, verify that the AD-users role is listed along with the default
RBAC roles.
Verifying RBAC role creation

32. In the NetBackup web user interface, click the user profile menu located on the title bar and click Sign
out to sign out of the NetBackup web user interface.
33. Sign in to the NetBackup web user interface using the credentials below.
o Username: RAAdams@vrtsedu.lab
o Password: P@ssw0rd

34. On the Welcome to Veritas NetBackup splash page, click X to close the splash page.
35. In the NetBackup web user interface, note the following:
o The Certificates, Tokens, and Security events dashboard widgets are not available for
user RAAdams@vrtsedu.lab because permissions to manage security were not assigned to this user.
o The user cannot access or manage the Microsoft SQL Server, RHV, Nutanix AHV, OpenStack,
and Kubernetes workloads. These options are no longer available under the Workloads node
because permissions to manage these workloads were not granted to this user.
o The Credential management node is not displayed because permissions to manage credentials were
not granted to this user.
o The following options are not displayed under the Security node in the navigation pane because
permissions to manage security were not granted to this user:
 RBAC
 Certificates
 Security events
 Tokens
 API keys
 User sessions

36. In the NetBackup web user interface, click the user profile menu located on the title bar and click Sign
out to sign out of the NetBackup web user interface.
37. Sign in to the NetBackup web user interface using the credentials below.
o Username: TMGarcia@vrtsedu.lab
o Password: P@ssw0rd
User Tristan Garcia with user ID TMGarcia@vrtsedu.lab is a member of the Engineering group that was
added to the AD-users RBAC role earlier in this lab exercise.

38. On the Welcome to Veritas NetBackup splash page, click X to close the splash page.
39. In the NetBackup web user interface, note that user Tristan Garcia has the same permissions as
user Ryan Adams (RAAdams@vrtsedu.lab) because the AD-users RBAC role is assigned to user Ryan
Adams and also to the Engineering group.
40. In the NetBackup web user interface, click the user profile menu located on the title bar and click Sign
out to sign out of the NetBackup web user interface.
41. Sign in to the NetBackup web user interface using the credentials below.
o Username: root
 o Password: P@ssw0rd

Creating a second RBAC role

42. In the NetBackup web user interface, in the navigation pane, click Security > RBAC.
43. On the Role-based access control page, click Add to create a new RBAC role.
44. On the Add role page, click the Custom role radio button and then click Next.
45. Enter SAML-users in the Role name field and click Assign on the Select permissions card.
46. On the Assign permissions page, click the Global tab and then select the following permissions:
o All permissions listed under the NetBackup Management category.
o All permissions listed under the Protection category.
o All permissions listed under the Storage category.

47. On the Assign permissions page, click Assign to assign the selected permissions to the role.

Do not select any permissions for Assets, Protection plans, or Credentials.

48. On the Add role page, click Add role to add the new RBAC role.

Do not add any users or groups to this RBAC role.

49. On the Add role page, verify that the role configuration was successful and click Close to return to
the Role-based access control page.
50. On the Role-based access control page, verify that the SAML-users role is listed along with the default
RBAC roles and the AD-users role.
51. Minimize the Mozilla firefox window to return to the desktop of the console system.

Do not log out of the NetBackup web user interface or close the browser window, you will return to it later in
this lab.

Exercise C: Configuring NetBackup for Single Sign-On

In this exercise, you establish trust between the NetBackup Master/Primary server and the Identity provider (IDP),
add and enable IDP configuration on the NetBackup Master/Primary server, and enroll the NetBackup
Master/Primary server as a service provider (SP) with the IDP. You will also add SAML users to the RBAC role
created in the previous lab exercise.

Microsoft Active Directory Federation Services (ADFS) is pre-configured in this lab environment.
Downloading the IDP metadata XML file

1. Access the root@lnxmaster:~ terminal window that is open on the console system.
2. In the terminal window, execute the following commands in sequence to download the IDP metadata XML
file and save it to the root users home directory.

Command: cd ~

Command: curl https://fs.vrtsedu.lab/federationmetadata/2007-06/federationmetadata.xml -o

federationmetadata.xml --insecure --silent

3. Execute the following command to verify that the IDP metadata.XML file was downloaded successfully.

Command: ls -l *.xml

Below is the expected output of the above command.

-rw-r--r--. l root root 70324 Oct 11 12:01 federationmetadata.xml

The time and date in the above expected output might change depending on when you are performing this
lab.

Adding a SAML Java Keystore (JKS)

4. In the terminal window, execute the following command:

Command: bpnbat -login -loginType WEB

The bpnbat command is located in the /usr/openv/netbackup/bin directory on the Master/Primary

server, lnxmaster.vrtsedu.lab. In this lab environment, this directory is added to the PATH variable on
the lnxmaster.vrtsedu.lab system and therefore the command can be executed without using the absolute
path.

Use the information provided below to complete the WEB login.

Authentication Broker: lnxmaster.vrtsedu.lab

Authentication port: Accept the default value
Authentication type: unixpwd
Domain: lnxmaster.vrtsedu.lab
Login Name: root
Password:P@ssw0rd

The expected output of the above command is displayed below:

Authentication Broker: lnxmaster.vrtsedu.lab

Authentication port [0 is default]:
 Authentication type (NIS, NISPLUS, WINDOWS, vx, unixpwd, ldap): unixpwd
Domain: lnxmaster.vrtsedu.lab
Login Name: root
Password:
Operation completed successfully.

5. After the web login is complete, execute the following command to configure an external CA-signed
SAML keystore.

Command: nbidpcmd -cECACert -uECA

The expected output of the above command is displayed below.

Configuring the external CA-signed SAML keystore. You may have to update the
metadata in the IDP server.
Successfully configured external CA-signed SAML keystore.

If NetBackup CA-signed certificates are used in your NetBackup environment, then a NetBackup CA JKS
should be created. For additional information, refer to the NetBackup Web UI Administrator's Guide.
If you are using a combination of an ECA and NetBackup CA in your environment, by default, the ECA is
considered while establishing trust with the IDP server.

Adding and enabling IDP configuration on the NetBackup Master/Primary server

6. In the terminal window, execute the below command to add the IDP configuration on the NetBackup
Master/Primary server.

Command: nbidpcmd -ac -n vrtsedu -mxp federationmetadata.xml

The federationmetadata.xml was downloaded earlier in this lab exercise.

The nbidpcmd command is located in the /usr/openv/netbackup/bin directory on the Master/Primary
server, lnxmaster.vrtsedu.lab. In this lab environment, this directory is added to the PATH variable on
the lnxmaster.vrtsedu.lab system and therefore the command can be executed without using the absolute
path.

The expected output of the above command is displayed below.

Successfully added the configuration for the identity provider.

7. After adding the IDP configuration, execute the below command to enable the IDP configuration.

Command: nbidpcmd -uc -n vrtsedu -e true

The expected output of the above command is displayed below.

Successfully updated the details for the configured identity provider with the
specified name.
8. After enabling the IDP configuration, execute the below command to verify the IDP configuration.

Command: nbidpcmd -sc -n vrtsedu

The expected output of the above command is displayed below.

Identity provider name: [vrtsedu]

Identity provider type: [SAML2]
Enabled: [true]

9. In the terminal window, type exit and press Enter to end the SSH session.

Downloading the service provider (SP) metadata XML file

10. Double-click the Firefox shortcut located on the desktop of the console system to launch Firefox.
11. In the browser window, enter the following URL in the address bar and press Enter.

URL: https://lnxmaster.vrtsedu.lab/netbackup/sso/saml2/metadata

12. In the Opening sp-metadata.xml dialog box, select the Save File radio button and click OK.
13. Close the browser window to return to the desktop of the console system.

You might have to wait for the sp-metadata.xml to download before you can close the browser window.

Enrolling NetBackup as a SP with the IDP

14. On the console system, click Start and then select Server Manager.
15. In the Server Manager window, click Tools and then click AD FS Management to launch the AD
FS console.
16. In the AD FS console, right-click Relying Party Trusts and select Add Relying Party Trust…
17. In the Add Relying Party Trust Wizard, on the Welcome screen, select the Claims aware radio button
and then click Start.
18. On the Select Data Source screen, select the Import data about the relying party from a file option
and click Browse.
19. In the Browse for Metadata File… dialog box, click Downloads and then click the sp-metadata.xml file
as illustrated in the figure below.
20. In the Browse for Metadata File… dialog box, click Open.
21. On the Select Data Source screen, click Next.
22. In the AD FS Management dialog box, read the warning message that is displayed and click OK.
23. On the Specify Display Name screen, enter NetBackup-SP in the Display name field and click Next.
24. On the Choose Access Control screen, select Permit everyone in the Choose and access control
policy section and click Next.
25. On the Ready to Add Trust screen, click Next without making any changes.
26. On the Finish screen, deselect the Configure claims issuance policy for this application option and
click Close to return to the AD FS console.
27. In the AD FS console, click Relying Party Trusts.
28. In the middle pane of the AD FS console, right-click NetBackup-SP and select Edit Claim Issuance
Policy…
29. In the Edit Claim Issuance Policy for NetBackup-SP window, click Add Rule.
30. In the Add Transform Claim Rule Wizard, on the Choose Rule Type screen, verify that the Send LDAP
Attributes as Claims option is selected in the Claim rule template drop-down list and click Next.
31. On the Configure Claim Rule screen, enter NetBackup-Claim-Rule in the Claim rule name field and
select Active Directory in the Attribute Store drop-down list.

32. On the Configure Claim Rule screen, in the Mapping of LDAP attributes to outgoing claim types section,
perform the following:
o Select User-Principal-Name in the first field under LDAP Attribute and type userPrincipalName in
the first field under Outgoing Claim Type.
o Select User-Principal-Name in the second field under LDAP Attribute and type Name ID in the
second field under Outgoing Claim Type.
o Select Is-Member-Of-DL in the third field under LDAP Attribute and type memberOf in the third
field under Outgoing Claim Type.

The expected result is illustrated in the figure below:

33. On the Configure Claim Rule screen, click Finish to add the claim rule and return to the Edit Claim
Issuance Policy for NetBackup-SP window.
 34. In the Edit Claim Issuance Policy for NetBackup-SP window, click Apply and then click OK to return to
the AD FS console.
35. Close the AD FS console and the Server Manager.

Adding SAML users to an existing RBAC role

36. Access the open NetBackup web user interface that is open on the console system.
37. In the NetBackup web user interface, in the navigation pane, click Security > RBAC.
38. On the Role-based access control page, click the SAML-users RBAC role.
39. On the SAML-users page, click the Users tab.
40. Select SAML user in the Sign-in type drop-down list, enter TEArcher@vrtsedu.lab in the User or
group field, and click Add to list.
41. Verify that user Tracy Archer with user ID TEArcher@vrtsedu.lab is now listed under the users section.
42. In the NetBackup web user interface, click the user profile menu located on the title bar and click Sign
out to sign out of the NetBackup web user interface.

Verifying SSO configuration

43. On the NetBackup web user interface sign in page, click the Sign in with single sign-on (SSO) option.
44. On the Veritas Education Services page that displayed, sign in using the credentials below.
o Username: TEArcher@vrtsedu.lab
o Password: P@ssw0rd

After the user is validated, the NetBackup web user interface is displayed. The options that are available for
user Tracy Archer are defined by the permissions configured for the SAML-users RBAC role.

45. On the Welcome to Veritas NetBackup splash page, click X to close the splash page.
46. In the NetBackup web user interface, click the user profile menu located on the title bar and click Sign
out to sign out of the NetBackup web user interface.

Exercise D: Viewing and Configuring Notifications

In this exercise, you will view alerts notifications and configure NetBackup to send email notifications when job
failures occur.

Viewing alert notifications

1. On the NetBackup web user interface sign in page, sign in using the credentials below.
 o Username: root
o Password: P@ssw0rd

2. In the NetBackup web user interface, click the Notifications icon located on the title bar and then
click Show all.
3. On the Notifications page, click a notification to view its details.

What details are displayed for the selected notification?

The details include the full description and extended attributes.

By default, NetBackup runs event notification cleanup tasks every 4 hours. Up to 10,000 event records are
stored for up to 3 days in the event database. During the cleanup tasks, NetBackup removes the older
notifications from the database. If no notifications are displayed on the Notifications page, proceed to the
next step.

4. In the NetBackup web user interface, in the navigation pane, click Storage > Storage configuration.
5. On the Storage configuration page, perform the following:

a. Click the Storage units tab, select the master_advdisk_stu storage unit and click Delete on
the Actions menu.

b. In the Delete dialog box, click Yes to delete the selected storage unit.

c. Click the Disk pools tab, select the master_advdisk_dpool disk pool and click Delete on
the Actions menu.

d. In the Delete dialog box, click Yes to delete the selected disk pool.

e. Click the Storage servers tab, select the lnxmaster.vrtsedu.lab storage server of
type AdvancedDisk and click Delete on the Actions menu.

f. In the Delete dialog box, click Yes to delete the selected storage server.

6. In the NetBackup web user interface, note that a number is displayed along with the Notification icon.

The number displayed along with the Notification icon indicates how many unseen critical messages exist
and is reset after the notifications are viewed.

7. Click the Notification icon and then click Show all.

8. On the Notifications page, click the notification that has a Critical severity level assigned to it.

Each event has a category for its NetBackup or external component and is assigned a severity level. The event
that has a Critical severity level was generated when the master_advdisk_stu storage unit was deleted. No
events were generated when the diskpool and the storage server for deleted because the storage server and
disk pool event types are not yet supported with Notifications. For additional information, refer to
the NetBackup Web UI Administrator’s Guide.
 The Filter available on the Notifications page allows you to filter events based on the Severity or Time
frame. You can also sort events by clicking the column headings.

9. Review the details that are displayed for the selected notification before proceeding.

Specific types of NetBackup event notifications that appear in the NetBackup web user interface can be
disabled or their severity and priority can be modified by making changes to the eventlog.properties file
located on the NetBackup Master/Primary server. For additional information, refer to the NetBackup Web UI
Administrator’s Guide.

Configuring email notifications

10. In the NetBackup web user interface, click Settings located on the title bar and then select Email
Notifications.
11. On the Alerts and notification settings page, click the Email notifications tab and then click the toggle
switch next to Send email notification to enable email notification.
12. On the Alerts and notification settings page, enter the following details and click Save.
o Send emails to: administrator@vrtsedu.lab
o Send emails from: administrator@vrtsedu.lab
o Name of email sender: NetBackup Web UI
o SMTP server: console.vrtsedu.lab
o Port: 25
o User name: administrator@vrtsedu.lab
o Password: P@ssw0rd

13. Verify that the email settings were saved successfully.

Verifying email configuration

14. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
15. On the Policies page, select the PRE-clients-to-master-advdisk policy and click Manual backup on
the Actions menu.
16. In the Manual backup window, select the Full backup schedule and the lnxmaster.vrtsedu.lab client.
17. In the Manual backup window, click OK to start the backup.
18. In the NetBackup web user interface, click Activity monitor.
19. On the Activity monitor page, note that the latest backup job failed with status 219.
20. Minimize the NetBackup web user interface to return to the desktop of the console system.
21. Double-click the Mozilla Thunderbird shortcut located on the desktop of the console system to
launch Mozilla Thunderbird email client.
22. In the email client window, in the navigation pane, click administrator@vrtsedu.lab > Inbox.

The messages available in the Inbox are displayed in the right pane of the email client window.
 It might take 2-3 minutes for the message to appear in the email client.
If the message does not appear in the email client after 2-3 minutes, restart the NetBackup Web
Management Console service on the NetBackup master and run another manual backup using the PRE-
clients-to-master-advdisk policy.

23. Double-click the latest email message received from NetBackup Web UI to view the message in a new
browser tab.

The From field is not displayed by default in the email client. To view the From field, right-click any of the
column heading displayed in the right pane (For example: Subject) and then select the From column.

24. View the contents of the email message that was received and close the email client window to return to
the desktop of the console system.

Excluding specific error codes from email notifications

25. Access the NetBackup web user interface that is open on the console system.
26. In the NetaBackup web user interface, click Settings located on the title bar and then select Email
Notifications.
27. On the Alerts and notification settings page, click the Exclude status codes tab.
28. In the Do not generate email notifications for the following status codes field, type 10 and click Save.
29. Verify that the settings were saved successfully.

Do not log out of the NetBackup web user interface or close the browser window, you will return to it later in
this lab.

Exercise E: Managing User Sessions

In this exercise, you will configure user account settings and manage user sessions.

Configuring when idle session timeout

1. In the NetBackup web user interface, in the navigation pane, click Security > User sessions.
2. On the User sessions page, click User account settings.
3. On the User account settings page, click the toggle switch located next to Session idle timeout to
configure this setting.
4. In the Edit session idle timeout dialog box, set the timeout to 15 minutes and click Save to return to
the User account settings page.
5. On the User account settings page, verify that the session idle timeout setting is set to 15 minutes.
Configuring maximum concurrent user sessions

6. On the User account settings page, click the toggle switch located next to Maximum concurrent
sessions to configure this setting.
7. In the Edit maximum concurrent sessions dialog box, set the number of concurrent sessions per user
to 5 and click Save to return to the User account settings page.
8. On the User account settings page, verify that the number of concurrent sessions per user is set to 5.

Configuring maximum failed sign-in attempts

9. On the User account settings page, verify that the User account lockout setting is enabled.
10. Click Edit to edit the Number of failed sign-in attempts allowed.
11. In the Edit user account lockout dialog box, set the Number of failed sign-in attempts to 1 and
the Unlock locked accounts after setting to 5 minutes.
12. In the Edit user account lockout dialog box, click Save to return to the User account settings page.
13. On the User account settings page, verify that the Number of failed sign-in attempts allowed and
the Unlock locked accounts after settings are configured correctly.

Configuring a login banner

14. On the User account settings page, click the toggle switch located next to Sign-in banner
configuration to configure this setting.
15. In the Edit sign-in banner dialog box, Enter Attention in the Heading field.
16. Enter the following text in the Body text field.

This system is for authorized users only.

17. Select the Include "Agree" and "Disagree" buttons on the sign-in banner option and click Save to
return to the User account settings page.
18. On the User account settings page, verify the sign-in banner is configured correctly.
19. In the NetBackup web user interface, click the user profile menu located on the title bar and click Sign
out to sign out of the NetBackup web user interface.

Unlocking a locked user account

20. Sign in to the NetBackup web user interface using the credentials below.
o Username: RAAdams@vrtsedu.lab
o Password: IncPass
The password for user Ryan Adams listed above is incorrect. Do not use the correct password for user Ryan
Adams.
21. After the authentication failed error message is displayed, try to sign in again with the user name and
the incorrect password listed above.

What error message is displayed when user Ryan Adams tries to sign-in with an incorrect password for the
second time?

Your NetBackup account is locked because you exceeded the permitted logon
attempts. Contact your NetBackup administrator for assistance

This error message is expected, because the Number of failed sign-in attempts allowed setting was set to 1
earlier in this lab.

22. Sign in to the NetBackup web user interface using the credentials below.
o Username: root
o Password: P@ssw0rd
23. On the login banner, review the information that is displayed and click Agree to proceed.

The login banner was configured earlier in this lab exercise.

24. In the NetBackup web user interface, in the navigation pane, click Security > User sessions.
25. On the User sessions page, click the Locked users tab.
26. Select user RAAdams and click Unlock to unlock user Ryan Adam's account.
27. In the Unlock user dialog box, click Unlock.
28. Verify that user RAAdams is no longer listed under the Locked users tab.

Terminating user sessions

29. On the User sessions page, click the Active sessions tab.
30. Select all the user sessions for user root and click Terminate sessions.
31. In the Terminate sessions dialog box, click Terminate sessions.

You will be logged out of the NetBackup web user interface.

32. In the Session terminated dialog box, click OK.

33. Optionally, sign in to the NetBackup web user interface as user Ryan Adams to verify that the user's
account has been unlocked successfully.
34. Close the browser window and log out of the console system.
Lab 03: Performing NetBackup Certificate Administration

Exercise A: Viewing NetBackup Certificates

In this exercise, you view the global security settings, the NetBackup CA (NBCA) certificate details, and the
NetBackup host ID-based certificate details.

Viewing global security settings

1. Log in to the console system using the credentials below.

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system to
launch the NetBackup web user interface.

The Netbackup web user interface can be accessed by navigating to the following URL:
https://Primary server hostname or IP/webui/login.
For the purpose of this lab, a web shortcut is preconfigured for accessing the NetBackup web user interface.

3. If a security warning is displayed, click Advanced > Accept the Risk and Continue.
4. Sign in to the NetBackup web user interface using the credentials below.
o Username: root
o Password: P@ssw0rd

5. If the Welcome to Veritas NetBackup splash page is displayed, click X to close the splash page.
6. In the NetBackup web user interface, click Settings located on the title bar and then click Global security.
7. On the Global security settings page, take a note of the information that is displayed.

What types of certificate authorities (CA) are supported by this NetBackup domain?

This NetBackup domain currently supports only the NetBackup Certificate Authority (NBCA).
 What is the current security level for certificate deployment?

The security level for certificate deployment is set to High.

Depending on the security level, an authorization token may or may not be required for a non-master
NetBackup host to obtain a host ID-based certificate.

8. On the Global security settings page, note that communication with NetBackup 8.0 or earlier hosts is
allowed. Also, note that NetBackup is configured to automatically map NetBackup host ID to host names.

NetBackup allows communication with NetBackup 8.0 and earlier hosts that are present in the environment.
However, this communication is insecure. For increased security, it is recommended to upgrade all NetBackup
hosts to the current version and disable this setting. This action ensures that only secure communication is
possible between NetBackup hosts.
For successful communication between NetBackup hosts, all relevant host names and IP addresses should be
mapped to the respective host IDs. The Automatically map NetBackup host ID to host names setting allows
NetBackup to automatically map all the host ID to the respective host name (and IP addresses). Disabling this
setting allows a NetBackup security administrator to manually verify the mappings before approving them.
You can also execute the nbcertcmd -getsecconfig command on the NetBackup Master/Primary server to
view the global security settings.

Viewing CA certificate details

9. In the NetBackup web user interface, in the navigation pane, click Security > Certificates.
10. On the Certificate Management page, click Certificate Authority.

The certificate authority details are displayed on the Certificate authority details page.

The Certificate Authority option is located immediately below the NetBackup certificates tab.

11. Take a note of the following important information that is displayed for the certificate authority on
the Certificate authority details page.

Subject name
CN=nbatd,OU=root@lnxmaster.vrtsedu.lab

Expires
September 17, 2040 12:27 PM

SHA-1 fingerprint 98:63:71:94:39:F3:CE:E1:21:B1:F8:C2:6A:17:A2:A0:3A:63:CA:56

SHA-256 fingerprint
5E:C4:62:08:D8:B8:4F:C4:0A:77:49:C1:88:26:39:C3:8A:85:4C:D8:89:93:1D:83:D3:FF:79:77:75:0C:95:3E

The NetBackup CA certificates are valid for 20 years.

 Alternatively, you can also use the nbcertcmd -listcacertdetails command to view details of the NetBackup
CA certificate. Below is an example output of the nbcertcmd -listcacertdetails command.

Subject Name : /CN=nbatd/OU=root@lnxmaster.vrtsedu.lab/O=vx

Start Date : Sep 22 18:12:27 2020 GMT
Expiry Date : Sep 17 19:27:27 2040 GMT
SHA-1 Fingerprint : 98:63:71:94:39:F3:CE:E1:21:B1:F8:C2:6A:17:A2:A0:3A:63:CA:56
SHA-256 Fingerprint :
5E:C4:62:08:D8:B8:4F:C4:0A:77:49:C1:88:26:39:C3:8A:85:4C:D8:89:93:1D:83:D3:FF:79
:77:75:0C:95:3E
Key Strength : 2048
Subject Key Identifier :
50:C6:99:BC:C4:B7:F8:8C:2A:07:C6:2C:86:DC:E6:6B:21:23:8E:AB

The certificate fields displayed in the examples/illustrations above may vary for your lab instance and is not a
cause for concern.

12. Make a note of the SHA-1 and SHA-256 fingerprints for the NetBackup CA certificate.
13. Click 'x' located in the right corner of the Certificate authority details page to return to the Certificate
Management page.

Viewing host ID-based certificate details

14. On the Certificate Management page, click the console.vrtsedu.lab client.

The details of the host-ID based certificate issued to this client are displayed on the Certificate details page.

15. Take a note of the following important information that is displayed on the Certificate details page.

Days Remaining
363

Host ID
b691167e-2d65-485b-9639-c81bab058275

Valid Between
July 2, 2021 8:47:20 AM to July 2, 2022 10:02:20 AM

The host ID-based certificates are issued to NetBackup Media Servers and clients by the NetBackup CA
(Master/Primary server). These certificates are valid for one year from the date of issue and are automatically
renewed 6 months before expiry.

Alternatively, you can also use the nbcertcmd -listcertdetails command to view details of the host ID-based
certificate.

The certificate fields displayed in the examples/illustrations above may vary for your lab instance and is not a
cause for concern.
16. Click 'x' located in the right corner of the Certificate Details page to return to the Certificate
Management page.

You can also view the global security settings, the NetBackup CA certificate details, and the host ID-based
certificate details in the NetBackup Administration Console.

17. Remain logged in to the NetBackup web user interface.

You will return to it later in this lab.

Exercise B: Manually deploying NetBackup certificates

In this exercise, you will use the NetBackup web user interface and the nbcertcmd command to deploy NetBackup
CA and host ID-based certificates on a NetBackup Client.

The NetBackup CA and host ID-based certificates are deployed on the client (by providing an authorization token)
when the NetBackup Client software is installed. If you have skipped the certificate deployments during install,
then the certificate must be deployed manually to enable connectivity between the client and the NetBackup
Master/Primary server.

Manually deploying the CA certificate on a NetBackup Client

1. Double-click the RDP Profiles (Windows systems) folder located on the desktop of the console system.
2. In the file explorer window, double-click the winvm1.vrtsedu.lab.rdp file to access the winvm1 system.

You will be automatically logged in to the winvm1 system using a domain administrator account.

3. Double-click the Command Prompt shortcut located on the desktop of the winvm1 system.
4. In the Administrator: Command prompt window, execute the below command to test connectivity
between this client and the NetBackup Master/Primary server.

Command: bpclntcmd -pn -verbose

The expected output of the above command is displayed below.

A certificate entry was not found for the requested server.: 5949
[PROXY] Encountered error (CERT_PROTOCOL_SELECT_COMMON_CA_ROOT) while
processing(CertProtocol).: 4
Can't connect to host lnxmaster.vrtsedu.lab: cannot connect on socket (25)
 The winvm1 system is currently unable to communicate with the NetBackup Master/Primary server. The error
message displayed in the output of the bpclntcmd command indicates that the NetBackup certificates are
missing or inaccessible.

Both the NetBackup CA certificate and the host ID-based certificate are required to enable connectivity
between the client and the NetBackup Master/Primary server.

5. Execute the below command to check if a NetBackup CA certificate is already present on

the winvm1 system.

Command: nbcertcmd -listcacertdetails

The nbcertcmd -listcacertdetails command must return the following:

Operation completed successfully.

EXIT STATUS 5949: Certificate does not exist.

The above status code is expected as the NetBackup CA certificate is currently not present on
the winvm1 system.

Before you can deploy a host-ID based certificate, the NetBackup CA certificate must be present on the client
system.

6. Execute the below command to deploy the NetBackup CA certificate on the winvm1 system.

Command: nbcertcmd -getcacertificate

The SHA-1 and SHA-256 fingerprint of the NetBackup CA certificate is displayed.

7. Verify that the SHA-1 and SHA-256 fingerprint matches with the fingerprints noted earlier in this lab.
8. After verifying the NetBackup CA certificate fingerprints, type y and press Enter to store the NetBackup
CA certificate on the winvm1 system.
9. Execute the below command to view details of the NetBackup CA certificate.

Command: nbcertcmd -listcacertdetails

An example output of the above command is displayed below.

Subject Name : /CN=nbatd/OU=root@lnxmaster.vrtsedu.lab/O=vx

Start Date : Sep 22 18:12:27 2020 GMT
Expiry Date : Sep 17 19:27:27 2040 GMT
SHA-1 Fingerprint : 98:63:71:94:39:F3:CE:E1:21:B1:F8:C2:6A:17:A2:A0:3A:63:CA:56
SHA-256 Fingerprint :
5E:C4:62:08:D8:B8:4F:C4:0A:77:49:C1:88:26:39:C3:8A:85:4C:D8:89:93:1D:83:D3:FF:79
:77:75:0C:95:3E
Key Strength : 2048
Subject Key Identifier :
50:C6:99:BC:C4:B7:F8:8C:2A:07:C6:2C:86:DC:E6:6B:21:23:8E:AB
 The certificate fields displayed above may vary for your lab instance and is not a cause for concern.

Manually deploying the host ID-based certificate on a NetBackup Client

10. In the Administrator: Command prompt window, execute the below command to deploy the host ID-
based certificate on the winvm1 system.

Command: nbcertcmd -getcertificate

The expected output of the above command is displayed below.

nbcertcmd: The -getCertificate operation failed for server

lnxmaster.vrtsedu.lab.
EXIT STATUS 5955: The host name is not known to the master server.

The Master/Primary server was unable to issue a host ID-based certificate to the winvm1 system because it is
not known to the Master/Primary server. A host is considered to be known to the Master/Primary server if the
host can be found in the following entities:

o If the host is listed against any of the following options in the NetBackup configuration file (Windows
registry or the bp.conf file on UNIX):
 APP_PROXY_SERVER
 DISK_CLIENT
 ENTERPRISE_VAULT_REDIRECT_ALLOWED
 MEDIA_SERVER
 NDMP_CLIENT
 SERVER
 SPS_REDIRECT_ALLOWED
 TRUSTED_MASTER
 VM_PROXY_SERVER
o If the host is listed as a client name in the altnames file (ALTNAMESDB_PATH).
o If the host appears in the EMM database of the Master/Primary server.
o If at least one catalog image of the client exists that is less than 6 months old.
o If the client is listed in at least one backup policy.
o If the client is a legacy client. That is, a client is listed in Host Properties > Master server > Client
Attributes.

Currently, the winvm1 system does not meet any of the requirements to be considered as a known host.
Based on the currently configured security level (High), if the host is not known to the Master/Primary server,
a reissue token is required to obtain the host ID-based certificate from the Master/Primary server. Without a
reissue token, the certificate can't be deployed.

11. Minimize (do not close) the Administrator: Command Prompt window.
12. Minimize (do not close) the RDP session window.

You will be returned to the console system after minimizing the RDP session window.

13. Access the NetBackup web user interface that is open on the console system.
14. In the NetBackup web user interface, in the navigation pane, click Security > Certificates.
15. On the Certificate Management page, click the winvm1.vrtsedu.lab client.

The details of the host-ID based certificate issued to this client are displayed on the Certificate details page.

As displayed on the Certificate details page, a host ID-based certificate is available for the winvm1 system
but the certificate is missing from the winvm1 system.

NetBackup generates the Host ID for a client only once and therefore the existing host-ID based certificate
must be deployed on the winvm1 system.

In this scenario, a reissue token will be required. An authorization token will not work because it is used for a
new client for which a Host ID was never generated.

16. On the Certificate details page, click Generate Reissue Token located in the top right corner.
17. In the Generate Reissue Token window, enter winvm1 in the Token Name field and click Generate.
18. In the Reissue Token Created Successfully dialog box, click the Copy to clipboard option (displayed
next to the Token Value) to copy the reissue token to the clipboard.
19. Click Close to close the Reissue Token Created Successfully dialog box.
20. Minimize (do not close) the NetBackup web user interface.

You will return to it later in this lab.

21. Access the RDP session window that is open on the console system to access the winvm1 system.
22. Access the Administrator: Command Prompt window that is open on the winvm1 system.
23. In the Administrator: Command prompt window, execute the below command to deploy the host ID-
based certificate on the winvm1 system.

Command: nbcertcmd -getcertificate -token token value

Replace the token value in the above command with the token value copied to the clipboard.

The expected output of the above command is displayed below.

Host certificate and certificate revocation list received successfully from

server lnxmaster.vrtsedu.lab.

The output of the nbcertcmd command confirms that the host ID-based certificate is deployed on
the winvm1 system.
24. Execute the below command to view details of the host ID-based certificate.

Command: nbcertcmd -listcertdetails

An example output of the above command is displayed below.

Master Server : lnxmaster.vrtsedu.lab

Host ID : 78b2cd2f-54ed-4b24-8775-7e408a9fe9f6
Issued By : /CN=broker/OU=root@lnxmaster.vrtsedu.lab/O=vx
Serial Number : 0x477bf4ad0000001e
Expiry Date : Jul 05 18:44:49 2022 GMT
SHA-1 Fingerprint : 3B:44:07:7D:DA:85:06:85:29:30:B4:55:82:26:98:82:DC:BB:5A:39
SHA-256 Fingerprint :
A0:DA:32:9D:53:F0:34:CE:44:DA:6F:E1:71:E8:9F:1D:99:8E:4B:1D:20:37:4B:46:CE:AE:68
:F4:11:46:1E:C6
Key Strength : 2048
Subject Key Identifier :
B8:EE:9F:90:EB:A8:3F:16:45:7B:D4:0D:61:32:F4:12:7F:3D:31:68
Authority Key Identifier :
98:55:0B:79:BD:2C:74:A1:B5:01:D8:66:8E:24:4B:C7:EF:E9:9D:D3

The certificate fields displayed above may vary for your lab instance and is not a cause for concern.

25. Make a note of the Host ID displayed in the above output.

26. Execute the below command to test connectivity between this client and the NetBackup Master/Primary
server.

Command: bpclntcmd -pn -verbose

The expected output of the above command is displayed below.

expecting response from server lnxmaster.vrtsedu.lab

127.0.0.1:50151 -> 127.0.0.1:50155 PROXY 10.10.2.22:50153 -> 10.10.2.13:1556
LOCAL_CERT_ISSUER_NAME = O=vx,OU=root@lnxmaster.vrtsedu.lab,CN=broker
LOCAL_CERT_SUBJECT_COMMON_NAME = 23805fd8-0384-49f0-bab6-b91ea637be0d
PEER_CERT_ISSUER_NAME = /CN=broker/OU=root@lnxmaster.vrtsedu.lab/O=vx
PEER_CERT_SUBJECT_COMMON_NAME = 78b2cd2f-54ed-4b24-8775-7e408a9fe9f6
PEER_IP = 10.10.2.22
PEER_PORT = 50153
PEER_NAME = winvm1.vrtsedu.lab
POLICY_CLIENT = NULL
Old Domain Service Type VNET_DOMAIN_SERVER_TYPE and Hint
New Domain Service Type VNET_DOMAIN_SERVER_TYPE and Hint 23805fd8-0384-49f0-
bab6-b91ea637be0d

As displayed in the output of the bpclntcmd command, after deploying the NetBackup CA certificate and the
host ID-based certificate on the winvm1 system, it can communicate with the NetBackup Master/Primary
server.

27. Close the Administrator: Command Prompt window and log out of the winvm1 system.
 28. Access the NetBackup web user interface that is open on the console system.
29. In the NetBackup web user interface, on the Certificate Details page that displays the details of the host
ID-based certificate for the winvm1 system, compare the Host ID with the Host ID noted in step 25.
30. Click 'x' located in the right corner of the Certificate Details page to return to the Certificate
Management page.
31. Minimize (do not close) the NetBackup web user interface.

You will return to it later in this lab.

Exercise C: Revoking and Reissuing Host ID-based Certificates

In this exercise, you revoke the host ID-based certificate for a client, observe the effects of a revoked certificate,
and use the auto reissue certificate option to reissue the host ID-based certificate to a revoked client.

Testing connectivity between the client and the Master/Primary server

1. Double-click the PuTTY shortcut located on the desktop of the console system.
2. In the PuTTY Configuration window, double-click the preconfigured entry for the Master/Primary
server, lnxmaster.vrtsedu.lab.
3. Log in to the lnxmaster.vrtsedu.lab system using the credentials below.
o Username: root
o Password: P@ssw0rd

4. In the root@lnxmaster:~ terminal window, execute the below command to test connectivity between the
client, lnxvm1.vrtsedu.lab and the Master/Primary server, lnxmaster.vrtsedu.lab.

Command: bptestbpcd -client lnxvm1.vrtsedu.lab -debug -verbose

The expected (filtered output) of the above command is displayed below.

00:33:37.324 [60515] <2> bptestbpcd: VERBOSE = 0

00:33:37.324 [60515] <2> ConnectionCache::connectAndCache: Acquiring new
connection for host lnxmaster.vrtsedu.lab, query type 223
…
00:33:37.500 [60515] <2> logconnections: PROXY CONNECT FROM 10.10.2.13.39495 TO
10.10.2.23.1556 fd = 5
00:33:37.500 [60515] <2> logconnections: BPCD CONNECT FROM 127.0.0.1.43369 TO
127.0.0.1.41898 fd = 5
00:33:37.501 [60515] <2> vnet_connect_to_vnetd_bpcd: js_bpcd_info: 0x2439770
00:33:37.502 [60515] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded
…
1 1 1
127.0.0.1:43369 -> 127.0.0.1:41898 PROXY 10.10.2.13:39495 -> 10.10.2.23:1556
 127.0.0.1:43369 -> 127.0.0.1:41912 PROXY 10.10.2.13:53625 -> 10.10.2.23:1556
…
LOCAL_CERT_ISSUER_NAME = O=vx,OU=root@lnxmaster.vrtsedu.lab,CN=broker
LOCAL_CERT_SUBJECT_COMMON_NAME = eebd4d50-095b-4894-b6be-8d08d4717e8d
PEER_CERT_ISSUER_NAME = O=vx,OU=root@lnxmaster.vrtsedu.lab,CN=broker
PEER_CERT_SUBJECT_COMMON_NAME = 23805fd8-0384-49f0-bab6-b91ea637be0d
PEER_NAME = lnxmaster.vrtsedu.lab
HOST_NAME = lnxvm1.vrtsedu.lab
CLIENT_NAME = lnxvm1.vrtsedu.lab
…
MASTER_SERVER = lnxmaster.vrtsedu.lab
EMM_SERVER = lnxmaster.vrtsedu.lab
NB_MACHINE_TYPE = CLIENT
…
PROCESS_HINT = 23805fd8-0384-49f0-bab6-b91ea637be0d
…
00:33:53.219 [60515] <2> bptestbpcd: EXIT status = 0

As displayed in the output above, the Master/Primary server can to communicate with
the lnxvm1.vrtsedu.lab system the using the host ID-based certificate.

5. Minimize (do not close) the root@lnxmaster:~ terminal window.

You will return to it later in this lab.

Revoking a host ID-based certificate

6. Access the NetBackup web user interface that is open on the console system.
7. In the NetBackup web user interface, in the navigation pane, click Security > Certificates.
8. On the Certificate Management page, click the lnxvm1.vrtsedu.lab client.

The details of the host-ID based certificate issued to this client are displayed on the Certificate details page.

9. On the Certificate details page, click Revoke Certificate located in the top right corner.
10. In the Revoke certificate dialog box, ensure that Unspecified is selected in the Reason drop-down list
and click Yes to revoke the host ID-based certificate for the lnxvm1.vrtsedu.lab client.

After the certificate is revoked, the status of the host ID-based certificate for the lnxvm1.vrtedu.lab client
changes from Active to Revoked. The updated status is displayed on the Certificate details page.

11. Click 'x' located in the right corner of the Certificate Details page to return to the Certificate
Management page.
12. Minimize (do not close) the NetBackup web user interface.

You will return to it later in this lab.

Updating the Certificate Revocation List (CRL) on the Master/Primary server

13. Access the root@lnxmaster:~ terminal window that is open on the console system.
14. In the root@lnxmaster:~ terminal window, execute the below command to update the Certificate
Revocation List (CRL).

Command: nbcertcmd -getcrl

The expected output of the above command is displayed below.

Successfully refreshed certificate revocation list for lnxmaster.vrtsedu.lab.

Successfully refreshed security level for lnxmaster.vrtsedu.lab.

Observing the effects of a revoked certificate

15. After updating the CRL, execute the below command to test connectivity between the
client, lnxvm1.vrtsedu.lab and the Master/Primary server, lnxmaster.vrtsedu.lab.

Command: bptestbpcd -client lnxvm1.vrtsedu.lab -debug -verbose

The expected (filtered output) of the above command is displayed below.

00:47:05.368 [62691] <2> bptestbpcd: VERBOSE = 0

00:47:05.368 [62691] <2> ConnectionCache::connectAndCache: Acquiring new
connection for host lnxmaster.vrtsedu.lab, query type 223
…
00:47:05.468 [62691] <2> vnet_proxy_protocol_from_legacy_ex:
remote_proxy_version = 0
00:47:05.469 [62691] <16> dump_proxy_info: statusmsg: The peer host certificate
is revoked. Revocation Reason Code : 0(Unspecified), Revocation Time : Jul 06
07:39:03 2021 GMT, Serial Number : 0x670AE3B60000001B, nbu status = 7653,
severity = 2
…
PEER_NAME = lnxmaster.vrtsedu.lab
HOST_NAME = lnxvm1.vrtsedu.lab
<16>bptestbpcd main: Function ConnectToBPCD(lnxvm1.vrtsedu.lab) failed: 7653
00:47:05.470 [62691] <16> bptestbpcd main: Function
ConnectToBPCD(lnxvm1.vrtsedu.lab) failed: 7653
<16>bptestbpcd main: The Peer Certificate is revoked
…
…

After revoking the certificate and updating the CRL, the Master/Primary server is unable to connect to the
client system and a message stating that the certificate for the lnxvm1.vrtsedu.lab client is revoked is
displayed.

16. Minimize (do not close) the root@lnxmaster:~ terminal window.

You will return to it later in this lab.

Allowing automatic reissue of a host ID-based certificate

17. Access the NetBackup web user interface that is open on the console system.
18. In the NetBackup web user interface, in the navigation pane, click Security > Hosts Mappings.
19. On the Host Mappings page, select the vertical ellipses next to the lnxvm1.vrtsedu.lab host and then
click the** Allow auto reissue certificate option** displayed on the menu.
20. In the Allow auto reissue certificate window, enter Testing in the Audit reason field and click Allow.
21. On the Host Management page, click the lnxvm1.vrtsedu.lab host to view its details.
22. On the page that displays the details for the lnxvm1.vrtsedu.lab host, note the date and time displayed
in the Allow auto reissue certificate validity field.

With the Allow auto reissue certificate option enabled, the host ID-based certificate can be reissued without
a token within the expiry date displayed in the Allow auto reissue certificate validity field. By default, the
expiry for reissuing certificates without a token is set to 48 hours.

23. Click 'x' located in the right corner of the details page to return to the Certificate Management page.
24. Sign out of the NetBackup web user interface and close the browser window.

Reissuing the host ID-based certificate to a revoked client

25. Double-click the PuTTY shortcut located on the desktop of the console system.
26. In the PuTTY Configuration window, double-click the preconfigured entry for the
client, lnxvm1.vrtsedu.lab.
27. Log in to the lnxvm1.vrtsedu.lab system using the credentials below.
o Username: root
o Password: P@ssw0rd

28. In the root@lnxvm1:~ terminal window, execute the below command to view details of the host ID-
based certificate.

Command: nbcertcmd -listcertdetails

An example output of the above command is displayed below.

Master Server : lnxmaster.vrtsedu.lab

Host ID : eebd4d50-095b-4894-b6be-8d08d4717e8d
Issued By : /CN=broker/OU=root@lnxmaster.vrtsedu.lab/O=vx
Serial Number : 0x79a564740000001f
Expiry Date : Jul 06 10:06:40 2022 GMT
SHA-1 Fingerprint : 89:66:A3:05:21:44:BE:1F:29:25:46:61:59:81:D9:E1:01:9F:BE:7E
SHA-256 Fingerprint :
7B:6C:2F:ED:22:9B:48:4C:20:00:8F:21:B6:6B:50:4E:CC:74:E4:5C:20:57:8E:34:16:5B:64
:B9:95:A3:19:9F
Key Strength : 2048
Subject Key Identifier :
1F:AF:27:BC:8E:17:E4:3B:24:18:38:04:EE:6F:F6:6A:4D:C0:3F:B4
 Authority Key Identifier :
98:55:0B:79:BD:2C:74:A1:B5:01:D8:66:8E:24:4B:C7:EF:E9:9D:D3

The certificate fields displayed above may vary for your lab instance and is not a cause for concern.

29. Execute the below command to test connectivity between this client and the NetBackup Master/Primary
server.

Command: bpclntcmd -pn -verbose

As displayed in the output of the bpclntcmd command, after revoking the host ID-based certificate, the host
is no longer able to communicate with the Master/Primary server even when the host ID-based certificate is
present on the host.

30. Execute the below command to deploy the host ID-based certificate on the lnxmv1 system.

Command: nbcertcmd -getcertificate

As displayed in the output, the nbcertcmd command did not deploy the host ID-based because an existing
host ID-based certificate is already present.

31. Execute the nbcertcmd -getcertificate command again but this time add -force option to overwrite the
existing host ID-based certificate.

The expected output of the nbcertcmd -getcertificate -force command is displayed below.

Host certificate and certificate revocation list recieved successfully from

server lnxmaster.vrtsedu.lab.

32. Execute the below command to verify that the connectivity between the lnxvm1 system and the
Master/Primary server has been restored.

Command: bpclntcmd -pn -verbose

The expected output of the above command is displayed below.

expecting response from server lnxmaster.vrtsedu.lab

127.0.0.1:54177 -> 127.0.0.1:50484 PROXY 10.10.2.23:35986 -> 10.10.2.13:1556
LOCAL_CERT_ISSUER_NAME = O=vx,OU=root@lnxmaster.vrtsedu.lab,CN=broker
LOCAL_CERT_SUBJECT_COMMON_NAME = 23805fd8-0384-49f0-bab6-b91ea637be0d
PEER_CERT_ISSUER_NAME = /CN=broker/OU=root@lnxmaster.vrtsedu.lab/O=vx
PEER_CERT_SUBJECT_COMMON_NAME = eebd4d50-095b-4894-b6be-8d08d4717e8d
PEER_IP = 10.10.2.23
PEER_PORT = 35986
PEER_NAME = lnxvm1.vrtsedu.lab
POLICY_CLIENT = lnxvm1.vrtsedu.lab
Old Domain Service Type VNET_DOMAIN_SERVER_TYPE and Hint
New Domain Service Type VNET_DOMAIN_SERVER_TYPE and Hint 23805fd8-0384-49f0-
bab6-b91ea637be0d
 33. Minimize (do not close) the root@lnxvm1:~ window.

You will return to it later in this lab.

Exercise D: Using External Certificates with NetBackup

In this exercise, you will configure NetBackup to use external CA signed certificate.

Configuring NetBackup to use external certificates for all communications is a serious undertaking. It involves
configuring external certificates on each Master/Primary server, Media Server, and clients. After configuring
external certificates, NetBackup will no longer be responsible for managing certificates on the master, media and
client. The NetBackup administrators will be responsible for managing certificates for the entire environment.

Configuring an external certificate for the NetBackup web user interface

1. Access the root@lnxmaster:~ terminal window that is open on the console system.
2. In the root@lnxmaster:~ terminal window, execute the command to list the contents of
the /certs directory.

Command: ls -l /certs

There are 3 files in the /certs directory on the Master/Primary server. The cacert.cer contains the CA
certificate for the External Certificate Authority. The cert.pem file contains the host certificate for the
Master/Primary server, lnxmaster.vrtsedu.lab. The host certificate is signed by the external CA.
The privatekey.pem file contains the private key for the host certificate.

You will use these files to configure external certificates in NetBackup.

3. Execute the below command to view the certificate that is currently used by the NetBackup web user
interface.

Command: vxsslcmd s_client -connect lnxmaster.vrtsedu.lab:443 -showcerts

Note the following in the output of the above command.

subject=/CN=lnxmaster.vrtsedu.lab/OU=TOMCAT@lnxmaster.vrtsedu.lab/O=vx
issuer=/CN=broker/OU=root@lnxmaster.vrtsedu.lab/O=vx

The current certificate that is used for the NetBackup web user interface is issued by the NetBackup
CA, lnxmaster.vrtsedu.lab.

4. Press Ctrl + C to stop the vxsslcmd script.

5. Execute the below nbsetconfig command to add the required configuration information in
the bp.conf file on the Master/Primary server.

Command echo "ECA_CERT_PATH = /certs/cert.pem" | nbsetconfig && echo "ECA_TRUST_STORE_PATH =

/certs/cacert.cer" | nbsetconfig && echo "ECA_PRIVATE_KEY_PATH = /certs/privatekey.pem" | nbsetconfig &&
echo "ECA_CRL_CHECK = 0" | nbsetconfig

6. Verify that the required configuration information has been added by executing the below command.

Command: nbgetconfig | grep -i ECA_

Note the following in the output of the nbgetconfig command.

ECA_CERT_PATH = /certs/cert.pem
ECA_TRUST_STORE_PATH = /certs/cacert.cer
ECA_PRIVATE_KEY_PATH = /certs/privatekey.pem
ECA_CRL_CHECK = DISABLE

7. After verifying the configuration, execute the below command to perform a ECA health check to ensure
that no issues are present in the certificates that are configured.

Command: nbcertcmd -ecahealthcheck

The health check should complete successfully.

8. Execute the below command to configure external certificate for the NetBackup web user interface.

Command: /usr/openv/wmc/bin/install/configureWebServerCerts -addExternalCert -webUI -certpath

/certs/cert.pem -privatekeypath /certs/privatekey.pem -truststorepath /certs/cacert.cer

The expected output of the above command is displayed below.

Performing eca health check…

ECA Health Check was successful.
The certificate is successfully added.
Restart the NetBackup Web Management Console service for the changes to take
effect.

After configuring the external certificate for the NetBackup web user interface, you must restart the
NetBackup Web Management Console service for the changes to take effect.

9. Restart the NetBackup Web Management Console service by executing the below command.

Command: nbwmc -terminate && nbwmc -start

It might take 2-3 minutes for the NetBackup Web Management Console service to restart.
10. After the NetBackup Web Management Console service restarts, execute the below command to view the
certificate that is currently used by the NetBackup web user interface.

Command: vxsslcmd s_client -connect lnxmaster.vrtsedu.lab:443 -showcerts

Note the following in the output of the above command.

Server certificate subject=/C=US/ST=California/L=Santa

Clara/O=Veritas/OU=Education Services/CN=lnxmaster.vrtsedu.lab
issuer=/DC=lab/DC=vrtsedu/CN=vrtsedu-ROOT-CA

The NetBackup web user interface is now using an external certificate.

Configuring an external certificate for all communications

11. In the root@lnxmaster:~ terminal window, execute the command to view the certificate that is currently
used for communicating with the clients.

Command: bptestbpcd -client lnxvm1.vrtsedu.lab -debug -verbose

Note the following in the output of the bptestbpcd command.

… LOCAL_CERT_ISSUER_NAME = O=vx,OU=root@lnxmaster.vrtsedu.lab,CN=broker
LOCAL_CERT_SUBJECT_COMMON_NAME = eebd4d50-095b-4894-b6be-8d08d4717e8d
PEER_CERT_ISSUER_NAME = O=vx,OU=root@lnxmaster.vrtsedu.lab,CN=broker
PEER_CERT_SUBJECT_COMMON_NAME = 23805fd8-0384-49f0-bab6-b91ea637be0d …

Currently, the NetBackup CA signed certificates are used for communicating with NetBackup Clients.

12. Execute the below command to configure external certificate for all communications.

Command: /usr/openv/wmc/bin/install/configureWebServerCerts -addExternalCert -all -certpath

/certs/cert.pem -privatekeypath /certs/privatekey.pem -truststorepath /certs/cacert.cer
The expected output of the above command is displayed below.

Performing eca health check…

ECA Health Check was successful.
The certificate is successfully added.
Restart the NetBackup Web Management Console service for the changes to take
effect.

After configuring the external certificate for all NetBackup communications, you must restart the NetBackup
Web Management Console service for the changes to take effect.

13. Restart the NetBackup Web Management Console service by executing the below command.

Command: nbwmc -terminate && nbwmc -start

 It might take 2-3 minutes for the NetBackup Web Management Console service to restart.

14. After the NetBackup Web Management Console service restarts, execute the below command to enroll
the external certificate on the Master/Primary server.

Command: nbcertcmd -enrollcertificate

The expected output of the above command is displayed below.

Performing eca health check…

ECA Health Check was successful.
The host certificate is successfully enrolled with master server
lnxmaster.vrtsedu.lab.

Starting NetBackup 8.2, certificates are auto-enrolled and there is no need to enroll the certificates manually
by executing the nbcertcmd -enrollcertificate command. This command is executed in this lab environment
for demonstration purposes only.

15. Execute the below command to view the certificate that is currently used for communicating with the
clients.

Command: bptestbpcd -client lnxvm1.vrtsedu.lab -debug -verbose

Note that NetBackup is still using the NetBackup CA signed certificates for communicating with the client.

… LOCAL_CERT_ISSUER_NAME = O=vx,OU=root@lnxmaster.vrtsedu.lab,CN=broker
LOCAL_CERT_SUBJECT_COMMON_NAME = eebd4d50-095b-4894-b6be-8d08d4717e8d
PEER_CERT_ISSUER_NAME = O=vx,OU=root@lnxmaster.vrtsedu.lab,CN=broker
PEER_CERT_SUBJECT_COMMON_NAME = 23805fd8-0384-49f0-bab6-b91ea637be0d …

After configuring external certificates, they have preference over the NetBackup signed certificates but if the
client does not have external certificates configured, NetBackup uses NetBackup CA signed certificates for
communicating with the client.

This behaviour is observed only if the security configuration is in Mixed mode. If only external certificates are
allowed, then the communication would fail if no external certificates are present on the client system.

16. Minimize (do not close) the root@lnxmaster:~ terminal window.

Configuring an external certificate on a NetBackup Client

17. Access the root@lnxvm1:~ terminal window that is open on the console system.
18. In the root@lnxvm1:~ terminal window, execute the command to list the contents of
the /certs directory.

Command: ls -l /certs
 There are 3 files in the /certs directory on the NetBackup Client server. The cacert.cer contains the CA
certificate for the External Certificate Authority. The cert.pem file contains the host certificate for the
NetBackup Client server, lnxvm1.vrtsedu.lab. The host certificate is signed by the external CA.
The privatekey.pem file contains the private key for the host certificate.

You will use these files to configure external certificates on this client.

19. Execute the below nbsetconfig command to add the required configuration information in
the bp.conf file on the client server.

Command echo "ECA_CERT_PATH = /certs/cert.pem" | nbsetconfig && echo "ECA_TRUST_STORE_PATH =

/certs/cacert.cer" | nbsetconfig && echo "ECA_PRIVATE_KEY_PATH = /certs/privatekey.pem" | nbsetconfig &&
echo "ECA_CRL_CHECK = 0" | nbsetconfig

20. Verify that the required configuration information has been added by executing the below command.

Command: nbgetconfig | grep -i ECA_

Note the following in the output of the nbgetconfig command.

ECA_CERT_PATH = /certs/cert.pem
ECA_TRUST_STORE_PATH = /certs/cacert.cer
ECA_PRIVATE_KEY_PATH = /certs/privatekey.pem
ECA_CRL_CHECK = DISABLE

21. After verifying the configuration, execute the below command to perform a ECA health check to ensure
that no issues are present in the certificates that are configured.

Command: nbcertcmd -ecahealthcheck

22. After the heath check completes, execute the below command to enroll the external certificate with the
NetBackup Master/Primary server.

Command: nbcertcmd -enrollcertificate

Starting NetBackup 8.2, certificates are auto-enrolled and there is no need to enroll the certificates manually
by executing the nbcertcmd -enrollcertificate command. This command is executed in this lab environment
for demonstration purposes only.

23. In the root@lnxvm1:~ terminal window, type exit and press Enter to log out of the lnxvm1 system and
close the root@lnxvm1:~ terminal window.
24. Access root@lnxmaster:~ terminal window that is open on the console system.
25. Execute the below command to view the certificate that is currently used for communicating with the
clients.

Command: bptestbpcd -client lnxvm1.vrtsedu.lab -debug -verbose

 The expected output of the above command is displayed below.

LOCAL_CERT_ISSUER_NAME = CN=vrtsedu-ROOT-CA,DC=vrtsedu,DC=lab
LOCAL_CERT_SUBJECT_COMMON_NAME = lnxvm1.vrtsedu.lab
PEER_CERT_ISSUER_NAME = CN=vrtsedu-ROOT-CA,DC=vrtsedu,DC=lab
PEER_CERT_SUBJECT_COMMON_NAME = lnxmaster.vrtsedu.lab

Note that NetBackup is now using external signed certificates for communicating with the client.

26. Execute the below command to view the certificate authorities (CA) supported by this NetBackup domain.

Command: nbcertcmd -getsecconfig -causage

Note that both NBCA and ECA are enabled. If the client is configured to use external certificate then
NetBackup will use the same for communicating with the client else NetBackup will use the NetBackup CA
certificates to communicate with the client.

After configuring all NetBackup Clients to use external certificates, the NetBackup certificates can be removed
from the Master/Primary server, the Media Server, and the clients so that only external certificates are used
for communications.

NetBackup CA can be disabled by execting the configureWebServerCerts -removeNBCert command on the

Master/Primary server.

Do not disable NetBackup CA certificates unless all clients are configured to use external certificates.

27. In the root@lnxmaster:~ terminal window, type exit and press Enter to log out of the lnxmaster system
and close the root@lnxmaster:~ window.
28. Log out of the console system.

Lab 04: Configuring Basic and Advanced Disk Storage

Exercise A: Configuring a BasicDisk Storage Unit

In this exercise, you use tools provided by the operating system to view disk storage that resides on the Media
Server system. You also use the NetBackup Administration Console to configure a Basic Disk Storage Unit
associated with your Media Server system.

Viewing disk storage on a NetBackup Media Server system

1. Log in to the console system using the following credentials.

 o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the PuTTY shortcut located on the desktop of the console system.
3. In the PuTTY Configuration window, double-click the preconfigured entry for the Media
Server, lnxmedia.vrtsedu.lab.
4. Log in to the lnxmedia.vrtsedu.lab system using the following credentials.
o Username: root
o Password: P@ssw0rd

5. In the root@lnxmedia:~ terminal window, execute the following command to view details of all mounted
partitions.

Command: df -h

Following is the expected output of the above command.

The output identifies the file systems and their associated mount points on the lnxmedia system. Many of
these file systems were pre-configured to serve as storage destinations for NetBackup backup images.

6. Take note of the /dev/sda5 file system, and its associated mount point, /bdisk.

You use the /bdisk partition later in this lab for configuring a basic disk storage unit.

7. Minimize (do not close) the root@lnxmedia:~ window.

You will return to it later in this lab.

Configuring a BasicDisk storage unit

8. Double-click the NetBackup 10.0 Administration Console shortcut located on the desktop of
the console system.
9. In the NetBackup Administration Console window, perform the following:

a. Ensure that lnxmaster.vrtsedu.lab is displayed in the Host name field.

b. In the Login using section, ensure that the User name and password radio button is selected.

c. Enter root in the User name field and P@ssw0rd in the Password field.

d. Click Login.

10. In the NetBackup Administration Console, navigate to NetBackup Management > Storage > Storage
Units.

The right pane of the Administration Console displays the list of storage units that have been pre-configured
for this course. All the pre-configured storage units are associated with the storage devices on the
Primary/Master server.

11. On the NetBackup Administration Console toolbar, click Actions > New > Storage Unit.
12. In the New Storage Unit window, perform the following:

a. Enter media_bdisk_stu in the Storage unit name field.

b. Select Disk in the Storage unit type drop-down list.

c. Ensure that BasicDisk is selected in the Disk type drop-down list.

d. Select lnxmedia.vrtsedu.lab in the Media server drop-down list.

e. Enter /bdisk in the Absolute pathname to directory field.

f. Leave all the other options at their defaults and click OK to create the storage unit.

After the new storage unit is created, it is listed in the details pane (right-pane) of the NetBackup
Administration Console.

13. Minimize (do not close) the NetBackup Administration Console.

You will return to it later in this lab.

Exercise B: Configuring AdvancedDisk Storage

In this exercise, you identify disk storage on your Media Server system that has been allocated for use by the
NetBackup AdvancedDisk feature. You also use the NetBackup web user interface to configure an advanced disk
storage server, disk pool, and storage unit.

Identifying disk storage allocated for AdvancedDisk

1. Access the root@lnxmedia:~ window that is open on the console system.

2. In the root@lnxmedia:~ terminal window, execute the following command to view details of all mounted
partitions.

Command: df -h

Following is the expected output of the above command.

The output identifies the file systems and their associated mount points on the lnxmedia system. Many of
these file systems were pre-configured to serve as storage destinations for NetBackup backup images.

3. Take note of the /dev/sda7, /dev/sda8, and /dev/sda2 file systems, and their associated mount
points, /advdisk1, /advdisk2, and /advdisk3.

You will use these partitions later in this lab for configuring advanced disk storage.

4. In the root@lnxmedia:~ terminal window, type exit and press Enter to log out of the Media Server and
close the terminal window.
Configuring an AdvancedDisk storage server

5. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system to
launch the NetBackup web user interface.

The Netbackup web user interface can be accessed by navigating to the following URL:
https://Primary server hostname or IP/webui/login.
For the purpose of this lab, a web shortcut is preconfigured for accessing the NetBackup web user interface.

6. If a security warning is displayed, click Advanced > Accept the Risk and Continue.
7. Sign in to the NetBackup web user interface using the following credentials.
o Username: root
o Password: P@ssw0rd

8. In the NetBackup web user interface, in the navigation pane, click Storage > Storage configuration.
9. On the Storage configuration page, click Add.
10. In the Add storage server window, select the AdvancedDisk radio button and click Start.
11. In the Select a media server window, select the lnxmedia.vrtsedu.lab radio button and click Select.

After the storage server is created, a success message is displayed in the web user interface along with a
shortcut to launch the disk pool configuration wizard.

Configuring an AdvancedDisk disk pool

12. Click the Add disk pool shortcut displayed with the success message to start the disk pool configuration
wizard.
13. On the Add disk pool > Disk pool options page, perform the following:

a. Ensure that lnxmedia.vrtsedu.lab is selected as the storage server.

b. Enter media_advdisk_dpool in the Disk pool name field.

c. Select the Limit I/O streams checkbox.

d. Ensure that the number of streams is set to 2 per volume.

e. Ensure that the high and low water mark are set to 98% and 80% respectively.

f. Click Next.

14. On the Add disk pool > Volumes page, select the /advdisk1 and the /advdisk2 mount points and
click Next to proceed.
15. On the Add disk pool > Review page, verify the information displayed is correct, and then click Finish to
configure the disk pool.
 After the disk pool is created, a success message is displayed in the web user interface along with a shortcut
to launch the storage unit configuration wizard.

Configuring an AdvancedDisk storage unit

16. Click the Add storage unit shortcut displayed with the success message to start the storage unit
configuration wizard.
17. On the Add AdvancedDisk storage unit > Basic properties page, perform the following:

a. Enter media_advdisk_stu in the Name field.

b. Change the Maximum concurrent jobs setting to 4.

c. Retain the default fragment size and click Next.

18. On the Add AdvancedDisk storage unit > Disk pool page, select the media_advdisk_dpool disk pool
and click Next.
19. On the Add AdvancedDisk storage unit > Media server page, click Next without making any changes.
20. On the Add AdvancedDisk storage unit > Review page, verify the information displayed is correct, and
then click Save to create the storage unit.

After the storage unit is created, a success message is displayed in the web user interface.

Verifying AdvancedDisk configuration

21. In the NetBackup web user interface, on the Storage configuration page, click the Storage servers tab.
22. Verify that the AdvancedDisk storage server, lnxmedia.vrtsedu.lab exists in the list of configured
storage servers.

Two of the storage servers listed were pre-configured for this course (an AdvancedDisk and
a PureDisk storage server on the Primary/Master server, lnxmaster.vrtsedu.lab).

23. On the Storage configuration page, click the Disk pools tab.
24. Verify that the disk pool, media_advdisk_dpool configured earlier in this exercise exists in the list of
configured disk pools.
25. Click the media_advdisk_dpool entry to view its details.
26. Review the information displayed for the disk pool on the details page.

Only certain disk pool parameters can be modified. For an AdvancedDisk disk pool, these include the
description, I/O streams, high, and low water mark used by the disk pool.

27. Click 'x' located in the top right corner of the details page to return to the Storage configuration page.
28. On the Storage configuration page, click the Storage units tab.
29. Verify that the storage unit, media_advdisk_stu configured earlier in this exercise exists in the list of
configured storage units.
30. Click the media_advdisk_stu entry to view its details.
31. Review the information displayed for the storage unit on the details page.

Only certain storage unit parameters can be modified. For an AdvancedDisk storage unit, these include the
On demand only, the Maximum concurrent jobs, and the Maximum fragment size parameters.

32. Click 'x' located in the top right corner of the details page to return to the Storage configuration page.
33. Sign out of the NetBackup web user interface and close the browser window.

Exercise C: Monitoring and Managing AdvancedDisk Storage

In this exercise, you use the nbdevquery and the nbdevconfig command line utilities to manage and monitor
Advanced Disk storage.

Using the nbdevquery command

NetBackup provides commands that can be used to verify the configuration and status of storage servers, disk
pools, and storage units.

In the steps that follow, you will connect to the Primary/Master server system and view the configuration and
status of NetBackup entities such as storage servers, disk pools, and mount points.

1. Double-click the PuTTY shortcut located on the desktop of the console system.
2. In the PuTTY Configuration window, double-click the preconfigured entry for the Primary/Master
server, lnxmaster.vrtsedu.lab.
3. Log in to the lnxmaster.vrtsedu.lab system using the following credentials.
o Username: root
o Password: P@ssw0rd

4. In the root@lnxmaster:~ terminal window, execute the following command to view information about
the nbdevquery command.

Command: nbdevquery -help

5. Note the many nbdevquery command options and arguments.

 To facilitate the execution of NetBackup commands without the need to navigate to the folder or directory
that houses the command, it is recommended that you set the PATH environment variable on NetBackup
servers to include the folders and directories that house commonly used NetBackup commands.
In this lab environment, the PATH environment variable has already been set on the Primary/Master server
and Media Server systems.

Using nbdevquery to view storage server information

6. In the root@lnxmaster:~ terminal window, execute the following command to list the
configured AdvancedDisk storage servers.

Command: nbdevquery -liststs -stype AdvancedDisk

7. Note the output of the command, including the entry for the AdvancedDisk storage server that was
configured on the Media Server system, lnxmedia.vrtsedu.lab earlier in this lab.
8. Execute the nbdevquery command again, this time adding the -U command option as shown.

Command: nbdevquery -liststs -stype AdvancedDisk -U

9. Scroll through the command output to locate information for the AdvancedDisk storage server on the
Media Server system, lnxmedia.vrtsedu.lab.
10. Take note of the information that is included in the command output.

Using nbdevquery to view disk pool information

You can use options of the nbdevquery command to view the configuration and status of all disk pools or selected
disk pools.

11. Execute the nbdevquery command, using the -listdp command option to view disk pool information.
Execute the command with the syntax shown.

Command: nbdevquery -listdp -stype AdvancedDisk

12. Take note of the command results.

13. Execute the nbdevquery command using the given command syntax, to obtain information on a specific
disk pool name.

Command: nbdevquery -listdp -stype AdvancedDisk -U -dp media_advdisk_dpool

The output of this command provides information about the specified disk pool.

14. Take note of the current status of the** media_advdisk_dpool** disk pool.

The current status of the disk pool should be "UP".

Using the nbdevconfig command to change the status of a disk pool

You can use the nbdevconfig command to change the status of a specified disk pool.

15. Execute the following command to change the status of the media_advdisk_dpool from "UP" to
"DOWN".

Command: nbdevconfig -changestate -stype AdvancedDisk -dp media_advdisk_dpool -state DOWN

16. Note the output of the nbdevconfig command.

17. Execute the following nbdevquery command to view the status of the media_advdisk_dpool disk pool

Command: nbdevquery -listdp -stype AdvancedDisk -U -dp media_advdisk_dpool

18. Take note of the current status of the media_advdisk_dpool disk pool.

The current status of the disk pool should be "DOWN".

19. Execute the following command to change the status of the media_advdisk_dpool from "DOWN" to
"UP".

Command: nbdevconfig -changestate -stype AdvancedDisk -dp media_advdisk_dpool -state UP

20. Note the output of the nbdevconfig command.

21. Execute the following nbdevquery command to view the status of the media_advdisk_dpool disk pool

Command: nbdevquery -listdp -stype AdvancedDisk -U -dp media_advdisk_dpool

22. Take note of the current status of the media_advdisk_dpool disk pool.

The current status of the disk pool should be "UP".

It might take a minute or two for the disk pool status to change to UP. Do not continue until you have
returned the media_advdisk_dpool to a status of "UP".

Using nbdevquery to view mount points for disk volumes

You can use the nbdevquery command to list the mount points for disk volumes associated with all disk pools or
with a specific disk pool.

23. Use the following nbdevquery command to list the mount points for all disk volumes associated
with AdvancedDisk disk pools on the Media Server, lnxmedia.vrtsedu.lab.

Command: nbdevquery -listmounts -U -dp media_advdisk_dpool

24. Note the results of the above command.

The media_advdisk_dpool disk pool includes 2 mount points, /advdisk1 and /advdisk2. These mount points
were added by you in the previous exercise.

Using nbdevquery to view the logical disk media ID

You can use the nbdevquery command to list the logical disk media IDs that NetBackup assigns to the volumes
associated with the disk pools.

25. Use the given nbdevquery command syntax to list detailed information about the disk volumes in the
specified disk pool.

Command: nbdevquery -listdv -dp media_advdisk_dpool -stype AdvancedDisk -U

26. Note the logical Disk Media ID that NetBackup assigns for both disk volumes associated with this disk
pool.

Adding a disk volume to an AdvancedDisk disk pool

You may add one or more additional disk volumes to an existing AdvancedDisk disk pool to increase the available
capacity of the disk pool.

The nbdevconfig command provides the --adddv option to add a disk volume to a disk pool.

27. Execute the following command to add the new disk volume (/advdisk3) to
the media_advdisk_dpool disk pool.

Command: nbdevconfig -adddv -stype AdvancedDisk -dp media_advdisk_dpool -dv /advdisk3

Following is the expected output of the above command.

One or more disk volumes have been successfully added to disk pool
media_advdisk_dpool.

28. Execute the following nbdevquery command to display the volumes currently in
the media_advdisk_dpool.

Command: nbdevquery -listmounts -U -dp media_advdisk_dpool

29. Verify that the disk pool now contains three disk volumes (/advdisk1, /advdisk2, and /advdisk3).
30. In the root@lnxmaster:~ terminal window, type exit and press Enter to log out of the Primary/Master
server and close the terminal window.
Exercise D: Configuring a Storage Unit Group

In this exercise, you use the NetBackup Administration Console to create a storage unit group.

1. Access the NetBackup Administration Console that is open on the console system.
2. In the NetBackup Administration Console, navigate to NetBackup Management > Storage > Storage
Unit Groups.

The right pane of the Administration Console displays the storage unit group that has been pre-configured
for this course. The pre-configured storage unit group is associated with the storage devices on the
Primary/Master server.

3. On the NetBackup Administration Console toolbar, click Actions > New > Storage Unit Group.
4. In the New Storage Unit Group window, perform the following:
a. Enter media_bdisk-advdisk_stugroup in the Storage unit group name field.
b. Click media_bdisk_stu in the Available storage units section and then click Add to add this storage
unit to the storage unit group.
c. Click media_advdisk_stu in the Available storage units sections and then click Add to add this
storage unit to the storage unit group.
d. Select the Failover radio button in the Storage unit selection section.

With the Storage unit selection set to Failover, the first storage unit in the storage unit group is used if
it is available.)

Following are some reasons why a storage unit can be considered unavailable:

 The storage unit is busy.

 The storage unit is down.
 The storage unit is out of media (applies to tape storage units only.)
 The storage unit has no available space.

A backup may span storage units if a disk full condition is detected. Backups can span from one
BasicDisk storage unit to another BasicDisk storage unit if the storage units are in the same
storage unit group and share the same Media Server.

By default, NetBackup allows backups to span disk but this setting can be modified by accessing
the Master Server Properties, and deselecting the Allow backups to span disk option available
under the Media tab.

 The storage unit has reached the Maximum concurrent jobs setting.
e. Click OK to create the storage unit group.
 5. Verify that the storage unit group, media_bdisk-advdisk_stugroup is in the list of configured storage
units.
6. Close the NetBackup Administration Console window and log out of the console system.

Lab 05: Configuring NetBackup Policies and Schedules

Exercise A: Configuring a Policy to use a Frequency-based Schedule

In this exercise, you use the NetBackup web user interface to configure a policy that uses a frequency-based
schedule to perform client backups.

In this lab, The NetBackup machine takes approximately 10 minutes to fully start up after a Lab profile is launched.
Wait for 10 minutes and then proceed with the Lab exercises.

Accessing the NetBackup web user interface

1. Log in to the console system using the following credentials.

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system to
launch the NetBackup web user interface.

The Netbackup web user interface can be accessed by navigating to the following URL:
https://Primary server hostname or IP/webui/login.
For the purpose of this lab, a web shortcut is preconfigured for accessing the NetBackup web user interface.

3. If a security warning is displayed, click Advanced > Accept the Risk and Continue.
4. Sign in to the NetBackup web user interface using the following credentials.
o Username: root
o Password: P@ssw0rd

Creating a policy

5. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
6. On the Policies page, click Add to start creating a new backup policy.

The Create policy page is displayed and the Attributes tab is selected by default.
Configuring policy Attributes

7. On the Create policy page, in the Attributes tab, perform the following:
a. Enter LAB-clients-to-media-bdisk in the Policy name field.
b. Ensure that Standard is displayed in the Policy type drop-down list.

The operating system of the client is what dictates the Policy type selected in the policy. UNIX and
Windows clients should not share the same policy.

c. Select media_bdisk_stu in the Policy storage drop-down list.

d. Retain the default settings for all other attributes and click the Schedules tab.

Configuring policy Schedules

8. On the Create policy page, in the Schedules tab, click Add in the Backup schedules section to add a
new policy schedule.
9. In the Add schedule window, perform the following:

a. Enter full_frequency in the Name field.

b. Ensure that Full Backup is selected in the Type of backup drop-down list.

c. Ensure that the Frequency radio button is selected in the Schedule type section.

d. Change the frequency to 6 hours.

e. Ensure that the Retention is set to 2 weeks (Retention Level 1).

f. Retain the default settings for all other schedule attributes and click the Start window tab.

g. Perform the following in the Start window tab:

i. Select today's day (e.g. Monday) in the Start day drop-down list.

ii. Set the Start time to 10:00:00 PM.

iii. Select tomorrow's day (e.g. Tuesday) in the End day drop-down list.

iv. Set the End time to 02:00:00 AM.

h. Click Add in the Add schedule window to save the schedule.

10. Verify that an entry for the full_frequency schedule is visible in the Backup schedules section under
the Schedules tab.

The figure illustrates the entry for the full_frequency schedule.

 The colored lines (representing the start windows for various types of schedules) in the top half of the
Schedules tab appear after the schedule is saved.

11. In the Schedules tab, click Add in the Backup schedules section to add a second policy schedule.
12. In the Add schedule window, perform the following:

a. Enter diffincr_frequency in the Name field.

b. Select Differential Incremental Backup in the Type of backup drop-down list.

c. Ensure that the Frequency radio button is selected in the Schedule type section.

d. Change the frequency to 3 hours.

e. Ensure that the Retention is set to 2 weeks (Retention Level 1).

f. Retain the default settings for all other schedule attributes and click the Start window tab.

g. Perform the following in the Start window tab:

i. Select tomorrow's day (e.g. Tuesday) in the Start day drop-down list.

ii. Set the Start time to 10:00:00 PM.

iii. Select day after tomorrow's day (e.g. Wednesday) in the End day drop-down list.

iv. Set the End time to 12:00:00 AM.

h. Click Add in the Add schedule window to save the schedule.

13. Verify that an entry for the diffincr_frequency schedule is visible in the Backup schedules section under
the Schedules tab.

The following figure illustrates entries for the full_frequency and diffincr_frequency schedules.

The colored lines (representing the start windows for various types of schedules) in the top half of the
Schedules tab appear after the schedule is saved.

Modifying a schedule

14. In the Schedules tab, in the Backup schedules section, select the checkbox next to
the diffincr_frequency schedule and then click Edit on the actions menu.
15. In the Edit Schedule window, click the Start window tab.

As currently configured, differential incremental backup jobs are allowed to start between Tuesday,
at 10:00:00 PM, and midnight (Wednesday, 12:00:00 AM).

16. Modify the Start window for the diffincr_frequency schedule, so that the differential incremental
backups are allowed to run on the days and times indicated in the following table.

Start Day Start Time End Day End Time

Tuesday 10PM (22:00:00) Wednesday midnight (00:00:00)

Wednesday 10PM (22:00:00) Thursday midnight (00:00:00)

 Start Day Start Time End Day End Time

Thursday 10PM (22:00:00) Friday midnight (00:00:00)

Friday 10PM (22:00:00) Saturday midnight (00:00:00)

17. You can use the Duplicate button to duplicate the existing start window for all the days of the week. To
remove the start window for a given day of the week, select the start window for that day and click
the Delete button. This removes the start window for that given day. The Clear button removes all the start
windows for the entire schedule.
18. After modifying the Start window for the diffincr_frequency schedule, click Add to update the schedule.

After modifying and saving the schedule, the Backup schedule preview under the Schedules tab should
appear as illustrated in the following figure.

Adding clients to the policy

18. On the Create policy page, click the Clients tab and then click Add to add clients to the policy.
19. In the Add client window, perform the following:
a. Enter lnxmaster.vrtsedu.lab in the Client name field.
b. Select the Detect client operating system checkbox.

Selecting the Detect client operating system checkbox instructs NetBackup to discover the operating
system of the client. NetBackup can detect the operating system if the NetBackup client software is
installed on the system prior to filling out the policy information.
 c. Click Add.

After the client is added, you are returned to the Create policy page.

20. On the Create policy page, in the Clients tab, click Add to add a second client to the policy.
21. In the Add client window, perform the following:

a. Enter lnxmedia.vrtsedu.lab in the Client name field.

b. Select the Detect client operating system checkbox.

c. Click Add.

After the client is added, you are returned to the Create policy page.

22. On the Create policy page, verify that entries for two clients -- the clients on your Master/Primary and
Media server systems -- are displayed under the Clients tab.
23. Take note of the contents of the Hardware and Operating System columns under the Clients tab.

The information in these columns was automatically determined by NetBackup by querying the client system.

Adding Backup Selections to a policy

24. On the Create policy page, click the Backup selections tab and then click Add to begin adding backup
selections to the policy.
25. In the Add backup selection window, perform the following:
a. Click browse (folder icon) located next to the Pathname or directive field.

A new Add backup selection window is displayed.

b. In the new Add backup selection window, click lnxmaster.vrtsedu.lab in the left (navigation) pane.

The directories/partitions available on the lnxmaster.vrtsedu.lab system are displayed in the right pane
of the Add backup selection window.

c. Locate and select the checkbox next to the data folder (as illustrated in the following figure) and
click Add.
 The selected backup selections are applied to all the clients in the policy.

d. Verify that /data is listed in the List of pathnames and directives to add to the selection
list textbox and click Add to add the backup selection to the policy and return to the Create
policy page.

You can also enter the pathname by typing the path directly in the List of pathnames and directives to
add to the selection list textbox.

26. On the Create policy page, select each of the tabs -- Attributes, Schedules, Clients, and Backup
Selections -- and briefly verify the contents of each tab.
27. After verifying the contents of each tab, click Create to create the backup policy.

After the backup policy is created, a success message is displayed in the NetBackup web user interface and
you are returned to the Policies page.

28. On the Policies page, verify that the LAB-clients-to-media-bdisk policy is listed along with other pre-
configured backup policies.
29. Remain logged in to the NetBackup web user interface.

You will return to it later in this lab.

Exercise B: Configuring a Policy to use a Calendar-based Schedule

In this exercise, you use the NetBackup web user interface to configure a policy that uses a calendar-based
schedule to perform client backups.
Creating a policy

1. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
2. On the Policies page, click Add to start creating a new backup policy.

The Create policy page is displayed and the Attributes tab is selected by default.

Configuring policy Attributes

3. On the Create policy page, in the Attributes tab, perform the following:
a. Enter LAB-console-to-media-advdisk in the Policy name field.
b. Select MS-Windows in the Policy type drop-down list.

The operating system of the client is what dictates the Policy type selected in the policy. UNIX and
Windows clients should not share the same policy.

c. Select media_advdisk_stu in the Policy storage drop-down list.

d. Retain the default settings for all other attributes and click the Schedules tab.

Configuring policy Schedules

4. On the Create policy page, in the Schedules tab, click Add in the Backup schedules section to add a
new policy schedule.
5. In the Add schedule window, perform the following:
a. Enter full_calendar in the Name field.
b. Ensure that Full Backup is selected in the Type of backup drop-down list.
c. Select the Calendar radio button in the Schedule type section.
d. Ensure that the Retries allowed after the run day option is not selected.
e. Ensure that the Retention is set to 2 weeks (Retention Level 1).
f. Retain the default settings for all other schedule attributes and click the Start window tab.
g. Perform the following in the Start window tab:

i. Select Tuesday in the Start day drop-down list.

ii. Set the Start time to 02:00:00 AM.

iii. Select Tuesday in the End day drop-down list.

iv. Set the End time to 05:00:00 AM.

h. Click the Exclude dates tab.

i. In the Exclude dates tab, in the Recurring days of the month section, click Last to exclude the last
day of the month.
 You may need to scroll to the end of the Exclude dates tab to view the Recurring days of the
month section.

j. Click the Include dates tab.

k. In the Include dates tab, in the Recurring week days section, mark each Tuesday of the month.

You may need to scroll to the end of the Include dates tab to view the Recurring week days section.
Any dates that are selected in the Exclude Dates tab are automatically displayed with the red dot
symbol in the Include Dates tab of the schedule. This is so you can see if there is a conflict of dates.

l. Click Add in the Add schedule window to save the schedule.

6. Verify that an entry for the full_calendar schedule is visible in the Backup schedules section under
the Schedules tab.
 The figure illustrates the entry for the full_calendar schedule.

The colored lines (representing the start windows for various types of schedules) in the top half of
the Schedules tab appear after the schedule is saved.

7. In the Schedules tab, click Add in the Backup schedules section to add a second policy schedule.
8. In the Add schedule window, perform the following:
a. Enter diffincr_calendar in the Name field.
b. Select Differential Incremental Backup in the Type of backup drop-down list.
c. Select the Calendar radio button is selected in the Schedule type section.
d. Ensure that the Retries allowed after the run day option is not selected.
e. Ensure that the Retention is set to 2 weeks (Retention Level 1).
f. Retain the default settings for all other schedule attributes and click the Start window tab.
g. Perform the following in the Start window tab:
i. Select Monday in the Start day drop-down list.
ii. Set the Start time to 02:00:00 AM.
iii. Select Monday in the End day drop-down list.
iv. Set the End time to 05:00:00 AM.
v. After entering the details above, click Duplicate to duplicate the schedule.
vi. Click the blue blocks (denoting active window) in the Sunday row and then click Delete.
vii. Click the blue blocks (denoting active window) in the Saturday row and then click Delete.

After completing the above configuration, the active schedule displayed under the Start
window tab should look similar to the following.
h. Click the Exclude dates tab.
i. In the Exclude dates tab, perform the following:
i. In the Recurring week days section, mark each Tuesday of the month.
ii. In the Recurring days of the month section, click Last to exclude the last day of the month.

You may need to scroll to the end of the Exclude dates tab to view the Recurring week days and
the Recurring days of the month sections.

j. Click the Include dates tab.

k. In the Include dates tab, in the Recurring week days section, mark each weekday except for
Tuesday.
 You may need to scroll to the end of the Include dates tab to view the Recurring week days section.

l. Click Add in the Add schedule window to save the schedule.

9. Verify that an entry for the diffincr_calendar schedule is visible in the Backup schedules section under
the Schedules tab.

The following figure illustrates entries for the full_calendar and diffincr_calendar schedules.

The colored lines (representing the start windows for various types of schedules) in the top half of the
Schedules tab appear after the schedule is saved.

Adding clients to the policy

10. On the Create policy page, click the Clients tab and then click Add to add clients to the policy.
11. In the Add client window, perform the following:
 a. Enter console.vrtsedu.lab in the Client name field.
b. Select the Detect client operating system checkbox.

Selecting the Detect client operating system checkbox instructs NetBackup to discover the operating
system of the client. NetBackup can detect the operating system if the NetBackup client software is
installed on the system prior to filling out the policy information.

c. Click Add.

After the client is added, you are returned to the Create policy page.

12. On the Create policy page, verify that client, console.vrtsedu.lab is displayed under the Clients tab.
13. Take note of the contents of the Hardware and Operating System columns under the Clients tab.

The information in these columns was automatically determined by NetBackup by querying the client system.

Adding Backup Selections to a policy

14. On the Create policy page, click the Backup selections tab and then click Add to begin adding backup
selections to the policy.
15. In the Add backup selection window, perform the following:
a. Ensure that Windows is selected in the Pathname or directive set drop-down list.
b. Click inside the List of pathnames and directives to add to the selection list textbox and
type E:\data.
c. Verify that E:\data is listed in the List of pathnames and directives to add to the selection
list textbox and click Add to add the backup selection to the policy and return to the Create
policy page.
16. On the Create policy page, select each of the tabs -- Attributes, Schedules, Clients, and Backup
Selections -- and briefly verify the contents of each tab.
17. After verifying the contents of each tab, click Create to create the backup policy.

After the backup policy is created, a success message is displayed in the NetBackup web user interface and
you are returned to the Policies page.

18. On the Policies page, verify that the LAB-console-to-media-advdisk policy is listed along with other
pre-configured backup policies.
19. Remain logged in to the NetBackup web user interface.

You will return to it later in this lab.

Exercise C: Managing NetBackup Policies

In this exercise, you explore and use the different options available in the NetBackup web user interface for
managing backup policies.

1. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
2. On the Policies page, select the checkbox next to the LAB-clients-to-media-bdisk policy.

After selecting the policy, an action menu with options to manage the selected policy is displayed.

The available options include Edit, Copy policy, Delete, Deactivate, and Manual backup.

The options on the action menu change based on the status of the policy that is selected. For example, if a
deactivated policy is selected, the options on the action menu change to Edit, Copy policy, Delete,
and Activate.

3. On the actions menu, click the Copy policy option.

4. In the Copy policy window, enter LAB-clients-to-media-stugroup in the New policy field and
click Copy.

A new policy LAB-clients-to-media-stugroup is created and contains the same settings as the original
policy.

5. On the Policies page, select the checkbox next to the LAB-clients-to-media-stugroup policy.

If the LAB-clients-to-media-bdisk policy is still selected, deselect it before selecting the LAB-clients-to-
media-stugroup policy.

6. After selecting the policy, click Edit on the actions menu to open the policy for editing.
7. On the Edit policy page, in the Attributes tab, select media_bdisk-advdisk_stugroup (Group) in
the Policy storage drop-down list.
8. Click Save without making any other changes to update the policy and return to the Policies page.
9. On the Policies page, select the checkbox next to the LAB-clients-to-media-stugroup policy and then
click Deactivate on the actions menu to deactivate this policy.

A deactivated policy is denoted by a gray 'x' icon in the NetBackup web user interface.

10. Select the checkbox next to the LAB-clients-to-media-stugroup policy and this time click Delete on the
actions menu to delete this policy.
11. In the Delete policy dialog box, click Delete to confirm the deletion.
12. Verify that the LAB-clients-to-media-stugroup policy is no longer listed on the Policies page.
13. Refer to the steps above and deactivate the following policies.
o PRE-clients-to-master-tape
o PRE-clients-to-master_disk-tape_stugroup
 A deactivated policy can be activated by using the Activate option available on the actions menu after
selecting the policy.

14. Select the checkbox next to the LAB-clients-to-media-bdisk policy and click Manual backup on the
actions menu.

The Manual backup option allows you to perform a manual (on-demand) backup of the clients included in
the backup policy.

15. In the Manual backup window, take a note of the available options.
16. Click Cancel in the Manual backup window to return to the Policies page.

Do not perform a backup at this time. You will perform manual backups in the next lab.

17. Sign out of the NetBackup web user interface and close the browser window.
18. Log out of the console system.

Lab 06: Protecting File Systems

Exercise A: Using and Customizing the Activity Monitor

In this exercise, you view and sort jobs in the Activity Monitor. You also modify the column layout and use the job
filters available in the Activity Monitor.

In this lab, The NetBackup machine takes approximately 10 minutes to fully start up after a Lab profile is launched.
Wait for 10 minutes and then proceed with the Lab exercises.

Viewing jobs in the Activity Monitor

1. Log in to the console system using the following credentials.

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system to
launch the NetBackup web user interface.

The Netbackup web user interface can be accessed by navigating to the following URL:
https://Primary server hostname or IP/webui/login.
For the purpose of this lab, a web shortcut is preconfigured for accessing the NetBackup web user interface.
3. If a security warning is displayed, click Advanced > Accept the Risk and Continue.
4. Sign in to the NetBackup web user interface using the following credentials.
o Username: root
o Password: P@ssw0rd

5. In the NetBackup web user interface, in the navigation pane, click Activity monitor.

The Activity monitor page is displayed and includes the following tabs:

o Jobs - Displays a list of all backup jobs.

o Daemons - Displays a list of all NetBackup Daemons and their status.
o Processes - Displays a list of all NetBackup processes along with the PID, Start time, and the Process
size (MB).
o Background tasks - Displays the list of background tasks along with start time, username, status .

When you access the Activity Monitor, the Jobs tab is selected by default.

6. View the jobs that are listed in the Jobs tab of the Activity Monitor page.

It is likely that the only job types that are currently displayed on the Activity Monitor page
are Backup and Image Cleanup job types. However, the jobs listed may vary substantially. This is expected.

The following figure illustrates an example Activity Monitor jobs list.

The figure above is an example of the Activity Monitor jobs list. Your Activity Monitor jobs list will
show Image Cleanup jobs exiting with a status code of 1, and it may or may not contain entries for failed
jobs, as illustrated in the figure.
Sorting the job list

You can sort the jobs list in the Activity Monitor according to any column that is displayed, simply by clicking on
the heading for the column. You may find that sorting jobs according to a specific column heading can be
beneficial.

By default, jobs are listed in descending numerical order in the Activity Monitor according to their Job ID. This
means that the most recent jobs (those with the highest Job ID, are listed at the top of the Jobs list).

You can change the order in which the jobs are listed in the Activity Monitor based upon the Job ID of the jobs.
The jobs can either be sorted in ascending order (lowest-numbered jobs listed first - at the top of the list), or in
descending order.

7. On the Activity Monitor page, click the heading of the Job ID column to change the job listing to the
ascending order (lowest-numbered jobs listed first -- at the top of the list).
8. Verify that the jobs are now listed in ascending order.
9. Click the heading of the Job ID column again, to change the job listing to the descending order -- with
most recent jobs listed at the top of the jobs list.
10. Verify that the jobs are now listed in descending order.

You can also sort the order in which jobs are listed in the Activity Monitor based upon the policy that was
used to perform the job.

Sorting by use of the Policy name column is done alphabetically, either in descending order (from Z to A), or
in ascending order (from A to Z). Some jobs are not controlled by a policy. Those jobs are either listed first
(when sorting jobs is ascending order by the Policy name), or last (when sorting jobs by descending order by
the Policy name).

Jobs are not normally sorted according to their Policy name -- but rather by their Job ID. There may be
situations where sorting jobs by their Policy name is desirable.

11. On the Activity Monitor page, click the heading of the Policy name column to sort the job list by policy
name.

The Policy name column is displayed to the right of the Status column. You may need to change the column
width to view the Policy name column.

Take note of the order in which the jobs are listed.

12. Click the heading of the Policy name column again, to change the job list sort order.

Take note of the order in which the jobs are listed.

Feel free to experiment with sorting the jobs list by clicking on various column headings, and note the results.
13. Click the heading of the Job ID column to return to sort the jobs according to their Job IDs.
14. Click the heading of the Job ID column until the jobs are sorted in descending order (with most recent
jobs at the top of the jobs list).

Viewing and modifying the Activity Monitor column layout

15. On the Activity Monitor page, click the Show or hide columns option located in the top right corner of
the Activity Monitor page.

The precise location of the Show or hide columns option is illustrated in the following figure.

16. Take note of the large number of Activity Monitor columns that are available for selection.

For Example, the following columns are selected.

o Job ID
o Type
o Client or display name
o Job state
o Status code
o Policy name
o Schedule
o Schedule type
o Elapsed time

17. Select the following additional columns to be displayed.

o Start time
o End time
o Estimated files

18. Deselect the following columns so that they are no longer displayed.
o Type
o Client or display name
o Schedule
o Schedule type
o Elapsed time

19. After making the above changes, click the Show or hide columns option to return to the Activity
Monitor page.
 Note the columns that are displayed.

20. Arrange the columns in the following order.

Column number Column name

1 Job ID

2 Policy name

3 Job state

4 Status code

5 Start time

6 End time

7 Estimated files

21. To re-arrange columns, simply drag and drop the column headings to the desired column location.
22. Selecting the columns to display and the order in which they are displayed is a matter of personal preference
of the NetBackup Administrator.

Creating and using job filters

NetBackup enables backup administrators to create job filters to filter the list of jobs that are displayed on
the Activity Monitor page. In the next steps, you create a simple Activity Monitor job filter.

22. View the list of jobs that are displayed on the Activity Monitor page.

At the current time, there should be two job types that are displayed, Backup and Image Cleanup jobs.

23. Click the Filter option located in the top right corner of the Activity Monitor page. And click Create
filter.

The Filter option is located to the left of the Show or hide columns option.

24. In the Filters pop-up window, Provide the name to the filter Partial jobs.
25. In the queary section, click the first drop-down arrow and select status code.
26. Use the last up-down arrow and set the value to 1.
27. Click Save and apply.
28. Upon applying the filter, it is immediately applied to the list of Activity Monitor jobs, to alter the list of
jobs displayed.
29. Verify that the job filter that you created performs as expected, and that only partially successful jobs are
displayed in the Activity Monitor.
30. To come-out from the filtered jobs and to see all the jobs, click All jobs which is present just before the
the filter you created.

31. Verify that the Activity Monitor jobs list displays the jobs that were previously not displayed, due to the
jobs filter.
32. Remain logged in to the NetBackup web user interface.

You will return to it later in this lab.

Exercise B: Performing Manual Backups

In this exercise, you perform manual backups using the backup policies created in the previous lab. You also use
the Activity Monitor to monitor and view details of the jobs.

Performing a manual backup

1. Access the NetBackup web user interface that is open on the console system.
2. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
3. Select the checkbox next to the LAB-clients-to-media-bdisk policy and click Manual backup on the
actions menu.
4. Note that there are two schedules and two clients listed in the Manual Backup window.
5. Click the radio button next to the full_frequency schedule then click OK to start the backup.

If multiple clients are included in the policy (as displayed in the clients section of the Manual
Backup window), and if no client entries are selected in the Manual Backup window, then backups will be
performed of each client that is included in the policy.

In this case, NetBackup initiates backup jobs for each client that was included in the clients section of
the Manual Backup window.

Viewing job details in the Activity Monitor

6. In the NetBackup web user interface, in the navigation pane, click Activity monitor.
7. On the Activity Monitor page, locate the most recent backup jobs that were performed using the LAB-
clients-to-media-bdisk policy.

These job was initiated in earlier in this exercise. The Job State for the job may still be Active. Wait for these
jobs to complete before proceeding.

8. Click the Backup job with the highest numbered Job ID.
9. On the actions menu, click View details to open the Job Details for the selected job.

The Job Details are displayed on a new page and contains three tabs: Overview, Details and Job hierarchy.
The Overview tab is selected by default.

10. In the Overview tab, take a note of the important fields that contain information about the selected job.
11. Make note of the contents of the Backup Type field, located on the Overview tab.

What is the Backup type for this job?

Immediate

What is the significance of this Backup type?

An "immediate" backup is performed as a result of a manual backup operation that was initiated by a backup
administrator.

Viewing the contents of the Details tab

12. On the page that displays the details for the selected job, click the Details tab.
 The Details tab provides information that is useful when troubleshooting failed jobs. Entries posted to
the Details tab track the progress of the job and identify many of the important NetBackup processes and
process IDs that are specifically used to perform the job. This information is useful if it becomes necessary to
analyze NetBackup log files.

13. Make note of the storage unit and the Media server information provided in the Details tab of the job.
14. Click the Log type drop-down list available in the Details tab and make a note of the options that are
available.

The Log type drop-down allows to filter the messages in the Details tab based on their severity level. For
example, selecting Error in the Log type drop-down list will display only error messages. By default, all
messages are displayed.

15. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity Monitor page.

Viewing status code information

16. On the Activity Monitor page, click to select one of the Image Cleanup jobs.
17. On the actions menu, click View details to open the Job Details for the selected job.
18. On the page that displays the details for the selected job, ensure that the Overview tab is selected.
19. In the Overview tab, locate the Status section and then click the status code to view information about
this status code.

The Veritas Support Site is launched in a new browser tab and displays information for the selected status
code.

20. Read the information that is displayed on the Veritas Support Site and close the browser tab to return to
the NetBackup web user interface.
21. In the NetBackup web user interface, click 'x' located in the right corned of the page that displays the
details for the selected job, to close the job details page and return to the Activity Monitor page.

Full and Incremental backup jobs

Gaining an understanding of how NetBackup works with regards to Full and Incremental backups is important. The
lab steps that follow demonstrate an important truth about Full and Incremental backup behavior.

22. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
23. Select the checkbox next to the LAB-console-to-media-advdisk policy and click Manual backup on the
actions menu.
24. Note that there are two schedules (full_calendar and diffincr_calendar) and one client
(console.vrtsedu.lab) listed in the Manual Backup window.
25. Click the radio button next to the diffincr_calendar schedule then click OK to start the backup.
26. In the NetBackup web user interface, in the navigation pane, click Activity monitor.
27. On the Activity Monitor page, locate the most recent backup job that was performed using the LAB-
console-to-media-advdisk policy.

The Job State for the job may still be Active. Wait for this job to complete before proceeding.

It might take 3-5 minutes for this backup to complete.

28. After the backup is complete, click the Backup job with the highest numbered Job ID and then click View
Details to open the Job Details for the selected job.
29. On the page that displays the details for the selected job, click the Details tab.
30. Make note of the Bytes transferred and Files written information provided in the Details tab of the job.

The number of files and size of the files that were backed up by the first job are the same as the total size (in
KB) and number of files that are resident in the E:\data directory on the client system.

Although the schedule used to perform the backup was a Differential Incremental Backup schedule, the
entire contents of the E:\data directory on the client was backed up (as specified in the Backup Selections of
the policy).

An important concept is that, when an incremental backup is due to run (Differential or Cumulative
Incremental), if a Full Backup has not yet been run using that policy, then the incremental backup will back
up the entire contents of the client, as defined in the Backup selections tab of the policy.

31. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
32. Select the checkbox next to the LAB-console-to-media-advdisk policy and click Manual backup on the
actions menu.
33. In the Manual backup window, click the radio button next to the diffincr_calendar schedule then
click OK to start the backup.
34. In the NetBackup web user interface, in the navigation pane, click Activity monitor.
35. On the Activity Monitor page, locate the most recent backup job that was performed using the LAB-
console-to-media-advdisk policy.

The Job State for the job may still be Active. Wait for this job to complete before proceeding.

It might take upto a minute for this backup to complete.

36. After the backup is complete, click the Backup job with the highest numbered Job ID and then click View
Details to open the Job Details for the selected job.
37. On the page that displays the details for the selected job, click the Details tab.
38. Make note of the Bytes transferred and Files written information provided in the Details tab of the job.
39. Compare the Bytes transferred and Files written information for this backup job with the Bytes
transferred and Files written information recorded for the first backup job.
 The size of the data and the number of files that were backed up by this Differential Incremental job were
substantially smaller than the number/size of files that were backed up by the first Differential Incremental
job. This second backup job is truly an incremental backup.

40. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity Monitor page.
41. Minimize (do not close) the NetBackup web user interface.

You will return to it later in this lab.

Exercise C: Performing User-initiated Backups

In NetBackup, a user-initiated backup is generally a backup job that is initiated by an end-user (the owner of the
data to be backed up), rather than by a backup administrator.

The ability to perform user-initiated backups must specifically be granted to a client by the creation of a policy
that includes a schedule that has a "Type of backup" equal to User Backup (or User Archive). The Start
Window of the User Backup schedule must define the time period or periods during which user backups are
allowed.

NetBackup user-initiated backup jobs are primarily initiated in one of two ways:

 Using the Backup, Archive, and Restore user interface.

 From the command line, using the bpbackup command.

In this exercise, you use the Backup, Archive, and Restore (BAR) user interface to initiate and monitor a user-
initiated backup job.

Understanding the Backup, Archive, and Restore user interface (for performing user-initiated
backups)

Before performing a backup operation using the NetBackup-provided Backup, Archive, and Restore (BAR) user
interface, it is important to understand an important concept related to the use of that interface to perform user-
initiated backup operations:

IMPORTANT CONCEPT: When using the Backup, Archive, and Restore (BAR) user interface to perform a user-
initiated backup, the user is only able to access and perform backup operations of the local system to which the
BAR user interface is connected.
User-initiated backup scenario

The end-user on the console.vrtsedu.lab system wants to perform a user-initiated backup of an important folder
on that Windows system, which is also the system from which a backup administrator normally launches
the NetBackup Administration Console.

Perform the steps that follow to test Backup, Archive, and Restore user interface behavior for user-initiated
backup operations.

1. Double-click the NetBackup 10.0 Administration Console shortcut located on the desktop of
the console system.
2. In the NetBackup Administration Console window, perform the following:

a. Ensure that lnxmaster.vrtsedu.lab is displayed in the Host name field.

b. In the Login using section, ensure that the User name and password radio button is selected.

c. Enter root in the User name field and P@ssw0rd in the Password field.

d. Click Login.

3. In the NetBackup Administration Console, in the object tree, click Backup, Archive, and Restore.

The Backup, Archive, and Restore interface is displayed in the right pane of the Administration Console and
provides three tabs: Backup Files, Restore Files, and Task Progress.

The Restore Files tab is selected by default.

4. To perform a user-initiated backup operation, click the Backup Files tab in the right pane of the
Administration Console.
5. Note that the Directory Structure pane of the BAR user interface displays the directory structure of the
system to which the BAR user interface is connected.

In this case, the BAR user interface is connected to the Primary/Master server system, lnxmaster.vrtsedu.lab.

6. On the NetBackup Administration Console toolbar, click Actions > Specify NetBackup Machines and
Policy Type.
7. In the Specify NetBackup Machines window, verify that the host name of the Primary/Master server is
listed in the Server to use for backups and restores drop-down list.

This entry refers to the host name of the Primary/Master server to which the user-initiated backup request will
be sent (from the client system).

8. Click Cancel, to cancel the operation without making any changes to the backup server that is specified.
 IMPORTANT CONCEPT REPEATED: When the Backup, Archive, and Restore interface is used from
the NetBackup Administration Console to perform a user-initiated backup operation (Backup Files tab
selected), the operation is performed against the NetBackup Server that the Administration Console is
connected to, NOT the host on which the Administration Console is launch from.

IMPORTANT CONCEPT APPLIED: If the Backup, Archive, and Restore user interface is launched from
the NetBackup Administration Console (connected to a Primary/Master server), the BAR user interface can
only be used to perform a user-initiated backup of the Primary/Master server to which it is connected.

A NetBackup administrator cannot use the Backup, Archive, and Restore user interface to perform user-
initiated backups of remote clients.

CONCLUSION: To satisfy this scenario, where a user wishes to perform a user-initiated backup of their client
system (console.vrtsedu.lab), the Backup, Archive, and Restore user interface must be launched from the
client itself and not accessed from the NetBackup Administration Console.
The Backup, Archive, and Restore user interface on a Windows client is the file, nbwin.exe.

9. Close the NetBackup Administration Console window to return to the desktop of the console system.

Accessing the Backup, Archive, and Restore user interface on a client system

10. Double-click the Backup, Archive, and Restore shortcut located on the desktop of the console system.

The Backup, Archive, and Restore user interface may take a few moments to load before it is ready for use.

Specifying NetBackup Machines and Policy Type

11. In the BAR interface, click File > Specify NetBackup Machines and Policy Type.
12. In the Specify NetBackup Machines and Policy Type window, perform the following:
a. Select lnxmaster.vrtsedu.lab in the Server to use for backups and restores drop-down list.
b. Ensure that console.vrtsedu.lab is selected in the Source client for restores drop-down list.
c. Ensure that MS-Windows is selected in the Policy type for restores drop-down list.
d. Click OK without making any other changes.
 When preparing to perform a user-initiated backup, the most important field in the Specify NetBackup
Machines and Policy Type window is the Server to use for backups and restores field. This field
determines the hostname of the Primary/Master server to which the backup request is sent.

Performing a user-initiated backup

13. In the BAR interface, click Select for Backup.

Note the following in the Backup window of the Backup, Archive, and Restore user interface:

o The All Folders pane of the user interface displays top-level entries for disk drives and other entities
on the client system that can be selected for backup.
o The "Contents of…" pane displays the detailed contents of the disk drive or other entity that is
highlighted in the All Folders pane.

14. Highlight (do not select the check box) the entry for the C drive, in the All Folders pane.
15. Select the check box for Documents and Settings in the Contents of C:\ pane.
16. Click Actions > Backup.
17. In the Backup Files window, perform the following:

a. Ensure that lnxmaster.vrtsedu.lab is selected in the NetBackup server drop-down list.

b. Ensure that C:\Documents and Settings\ is listed in the Files marked for backup section.

c. Click Start Backup to initiate the backup of the client.

18. In the NetBackup Message dialog box, click Yes to view the progress of the backup.

It may take a few moments for the NetBackup Message dialog box to be displayed.

19. In the View Status window, mark the check box for Verbose to view detailed information about the
backup job.

The Progress pane of the View Status window indicates that a failure has occurred. The Server status for
this failure is 240.

20. Take note of the explanation of this failure, as described in the Progress pane of the View Status window.

The user-initiated backup job failed because there was no schedule of the correct type (User Backup) in any
NetBackup policy in which this client was listed as a client.

21. Close the View Status window.

22. Minimize (do not close) the Backup, Archive, and Restore window.

You will return to it later in this lab.

Correcting the problem

23. Access the NetBackup web user interface that is open on the console system.

To enable the user-initiated backup of a client, there must be at least one policy in which the client name is
included in the Clients tab of the policy. That policy must have a schedule that meets two criteria:

o The policy must include a schedule that has a Backup type of User Backup.
o The User Backup schedule in the policy must have a Start Window that is open at the time that the
user-initiated backup is requested.

24. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
25. Select the checkbox next to the LAB-console-to-media-advdisk policy and click Edit on the actions
menu.
26. On the Edit policy page, click the Schedules tab.
27. In the Schedules tab, in the Backup schedules section, click Add to add a new schedule.
28. In the Add schedule window, perform the following:

a. Enter user_backup in the Name field.

b. Select User Backup in the Type of backup drop-down list.

c. Ensure that the Retention is set to 2 weeks (Retention Level 1).

d. Retain the default settings for all other schedule attributes and click the Start window tab.

e. Perform the following in the Start window tab:

i. Select Sunday in the Start day drop-down list.

ii. Set the Start time to 12:00:00 AM.

iii. Select Sunday in the End day drop-down list.

iv. Set the End time to 11:59:00 PM.

v. Click Duplicate to duplicate the start window.

f. Click Add in the Add schedule window to save the schedule.

29. Verify that an entry for the user_backup schedule is visible in the Backup schedules section under
the Schedules tab.
30. On the Edit policy page, click the Clients tab to verify that console.vrtsedu.lab is listed.
31. Click Save to update the policy and return to the Policies page.
32. Minimize (do not close) the NetBackup web user interface.

You will return to it later in this lab.

Re-testing the user-initiated backup

33. Access the Backup, Archive, and Restore window that is open on the console system.
34. Verify that the Documents and Settings entry in the Contents of C:\ pane of the Backup, Archive, and
Restore user interface is still selected (checked).
35. Click Actions > Backup.
36. In the Backup Files window, perform the following:

a. Ensure that lnxmaster.vrtsedu.lab is selected in the NetBackup server drop-down list.

b. Ensure that C:\Documents and Settings\ is listed in the Files marked for backup section.

c. Click Start Backup to initiate the backup of the client.

37. In the NetBackup Message dialog box, click Yes to view the progress of the backup.

It may take a few moments for the NetBackup Message dialog box to be displayed.

38. In the View Status window, select the entry for the newest (most recent) Backup operation.
39. Monitor the progress of the Backup operation until it is completed.
40. Verify that the Backup operation is completed successfully.
41. After the backup completes, review the messages displayed in the Progress section of the View
Status window.

Note the policy and the schedule that was used for this backup request.

42. Close the View Status window.

43. Close the Backup window of the Backup, Archive, and Restore user interface, as illustrated in the
following figure.
 44. Click File and then Exit to close the Backup, Archive, and Restore user interface.

Exercise D: Restoring Client Files to their Original Location

In this exercise, you delete files from the console.vrtsedu.lab system and use the NetBackup web user interface to
restore the deleted files to their original location using the backup image that were created earlier in this lab using
the LAB-console-to-media-advdisk policy.

Preparing the client system (console.vrtsedu.lab) for the restore

1. Double-click the File Explorer shortcut located on the desktop of the console system.
2. In the This PC explorer window, double-click the DATA drive (drive letter E) to view its contents.
3. Double-click the data folder located in the DATA drive.

The sub-folders of the data folder are displayed.

4. Right-click the smallfiles folder and, in the resulting menu, click Delete.

The E:\data directory on the console system was backed up using the LAB-console-to-media-advdisk policy
earlier in this lab.

5. Minimize (do not close) the file explorer window.

You will return to it later in this lab.

Restoring client files to their location

6. Access the NetBackup web user interface that is open on the console system.
7. In the NetBackup web user interface, in the navigation pane, click Recovery.
8. On the Recover page, click Regular recovery.
9. On the Recover > Basic properties page, perform the following:
a. Select console.vrtsedu.lab in the Source client drop-down list.

The Source client parameter is used to specify the name of the source client whose backup images will
be browsed in preparation for a restore operation.

 A typical NetBackup client is allowed only to browse backup images and perform the restore of
data that was backed up from their own system. For example, NetBackup users on
clientname.vrtsedu.lab can only browse for and select for restore from backup images created
from clientname.vrtsedu.lab resident data.
 In contrast, NetBackup backup administrators using the NetBackup web user interface for
performing restores may browse for backup images and restore data to any client in the
Primary/Master server's NetBackup domain.

b. Ensure that console.vrtsedu.lab is displayed in the Destination client field.

The host name of the client to which files are to be restored must be entered in the Destination
client field.

 A typical NetBackup client is allowed only to restore data that is backed up from their own client
system to their own client system. The user is unable to restore files or folders to another client
system.
 A NetBackup backup administrator using the NetBackup web user interface for performing
restores is allowed to restore client data from backup images to any client in the NetBackup
Primary/Master server domain, unless prevented from doing so by the configuration of the client
system. (The NetBackup client property, Allow server-directed restores, is enabled on clients by
default, but can be used to prevent the administrator from performing a restore operation to the
client.)
c. Ensure that MS-Windows is selected in the Policy type drop-down list.

The Policy type drop-down list specifies the Policy type that was used to back up the source client, and
is the policy type that the Primary/Master server uses when searching its backup image catalog for the
client that can be restored from. If the policy type is not set properly, the Primary/Master server may be
unable to locate backup images for the client system.

d. After selecting and verifying the source and destination client, the policy type, click Next to proceed.

The options available on Recover > Basic properties page closely resembles the options available in
the Specify NetBackup Machines and Policy Type window. The Specify NetBackup Machines and
Policy Type window is accessed from the Backup, Archive, and Restore interface available in
the NetBackup Administration Console.
10. On the Recover > Add files page, note that the Restore type is set to Normal backup and cannot be
changed.

As oppossed to the NetBackup Administration Console, the NetBackup web user interface can be used to
perform restores only for the Standard and MS-Windows policy types and therefore other restore types are
not currently available.

11. On the Recover > Add files page, perform the following:
a. Set the Start date to 1st June 2021 and the start time to 12:00:00 AM.
b. Set the End date to today's date and the end time to 11:59:00 PM.

The Start date and End date specify the date range that the Primary/Master server will use to search its
backup image catalog for backup images for the client. The results of this search will display a listing of
the backup images from which files and folders can be selected for restore to the client.

c. After setting the start and end dates and time, click Backup history.

The Backup History window is displayed, as illustrated in the following figure.

The Backup History window shows the backup images for the selected client, and enables you to select
a backup image or set of backup images (i.e., Full Backup image plus Incremental backup images) to use
for a restore operation.

To select multiple backup images from the Backup History window, select the checkbox available next
to the backup image. By default, all backup images are selected.

d. In the Backup history window, deselect the image where the Schedule type is set
to USER_BACKUP.
e. Leave all the other backup images selected and click Select to close the Backup history window and
return to the Recover > Add files page.
f. After selecting the backup images, click Add files.

As a result of selecting the backup images in the Backup history window, the NetBackup client sends a
request to the Primary/Master server to retrieve a list of the contents of the selected backup images. The
results are displayed in the Add files window.

g. In the Add files and folders window, perform the following:

i. Expand the console.vrtsedu.lab node and then expand the E node.
ii. Click the data folder in the left pane and then select the smallfiles directory displayed in the
right pane of the Add files and folders window.
iii. After selecting the smallfiles directory, click Add in the Add files and folders window to select
the files for restore and return to the Recover > Add files page.
h. Verify that the smallfiles folder selected for restore is now listed on the Recover > Add files page
and click Next.
12. On the Recover > Recovery target page, ensure that the Restore everything to the original
directory radio button is selected and click Next.
13. On the Recover > Recovery options page, click Next without making any changes.
14. On the Review page, check the information and click Start recovery.

You are automatically redirected to the Activity Monitor page after initiating the restore.

15. Monitor the progress of the restore operation until it runs to successful completion.
16. After the restore is complete, click the Restore job and then click View Details on the actions menu to
open the Job Details for this job.
17. In the Overview tab, take a note of the important fields that contain information about the restore job.

When restoring files to the same directory, you should note the following items.

From the Overview tab you can see the Job Type is marked as Restore. The Client is console.vrtsedu.lab,
the Primary server is lnxmaster.vrtsedu.lab. The Files List shows the files (/E/data/smallfiles/) being
restored.

18. On the page that displays the details for the restore job, click the Details tab.

From the Details tab note the Job PID. This is the process ID of bprd (NetBackup Request Daemon).
The Media server used in this restore is lnxmaster.vrtsedu.lab. Notice the Storage Unit section is blank.
Unlike a backup that uses a specific storage unit, during restores storage units are not utilized. From the log
message you can determine the data being restored was stored on disk. Look for the entry that states
"granted resource". This line reveals the MediaID, DiskVolume, DiskPool, Path, StorageServer, and Media
Server.

Additionally make note of the Bytes transferred and Files written information provided in the Details tab of
the job.

How many files were written to the client system?

1001 files were written to the client system.

19. Click 'x' located in the right corner of the page that displays the details for the restore job, to close the job
details page and return to the Activity Monitor page.
20. Minimize (do not close) the NetBackup web user interface.

You will return to it later in this lab.

Verifying the restored folder and files on the client

20. Access the file explorer window that is open on the console system.
21. Verify that the smallfiles folder deleted earlier in this exercise has been restored.
 22. Double-click the smallfiles folder to view its contents.

The folder should contain 1000 files, file000.txt -- file999.txt.

NetBackup restored 1 directory and 1000 files. NetBackup sees these as the same entity so therefore reports
that it restored 1001 files.

23. Close the file explorer window.

Exercise E: Restoring Client Files to an Alternate File System Location

In this exercise, you use the NetBackup web user interface to restore files to an alternate location on the original
client system (from which the files were backed up). You use the backup images created using the LAB-console-
to-media-advdisk policy for this restore.

Preparing the client system (console.vrtsedu.lab) for the restore

1. Double-click the File Explorer shortcut located on the desktop of the console system.
2. In the This PC explorer window, double-click the DATA drive (drive letter E) to view its contents.

Currently, the data and the FILESHARE folders are the only accessible folders present at the root of
the E:\ drive on the client system. In the steps that follow, you restore the smallfiles folder and its contents to
a new folder at the root of the E:\ drive.

3. Minimize (do not close) the file explorer window.

You will return to it later in this lab.

Performing the restore of client files

4. Access the NetBackup web user interface that is open on the console system.
5. In the NetBackup web user interface, in the navigation pane, click Recovery.
6. On the Recover page, click Regular recovery.
7. On the Recover > Basic properties page, perform the following:

a. Select console.vrtsedu.lab in the Source client drop-down list.

b. Ensure that console.vrtsedu.lab is displayed in the Destination client field.

c. Ensure that MS-Windows is selected in the Policy type drop-down list.

 d. After selecting and verifying the source and destination client, the policy type, click Next to proceed.

8. On the Recover > Add files page, perform the following:

a. Set the Start date to 1st June 2021 and the start time to 12:00:00 AM.

b. Set the End date to today's date and the end time to 11:59:00 PM.

c. After setting the start and end dates and time, click Backup history.

d. In the Backup history window, deselect the image where the Schedule type is set
to USER_BACKUP.

e. Leave all the other backup images selected and click Select to close the Backup history window and
return to the Recover > Add files page.

f. After selecting the backup images, click Add files.

g. In the Add files and folders window, perform the following:

i. Expand the console.vrtsedu.lab node and then expand the E node.

ii. Click the data folder in the left pane and then select the smallfiles directory displayed in the
right pane of the Add files and folders window.

iii. After selecting the smallfiles directory, click Add in the Add files and folders window to select
the files for restore and return to the Recover > Add files page.

h. Verify that the smallfiles folder selected for restore is now listed on the Recover > Add files page
and click Next.

9. On the Recover > Recovery target page, select the Restore everything to a different directory radio
button.
10. Enter E:\alternate-directory\smallfiles in the Directory for restore field and click Next.
11. On the Recover > Recovery options page, click Next without making any changes.
12. On the Review page, check the information and click Start recovery.

You are automatically redirected to the Activity Monitor page after initiating the restore.

13. Monitor the progress of the restore operation until it runs to successful completion.
14. After the restore is complete, minimize (do not close) the NetBackup web user interface.

You will return to it later in this lab.

Verifying the restored folder and files on the client

14. Access the file explorer window that is open on the console system.
 Note that a new folder named alternate-directory is present at the root of the *E:* drive. This directory was
created by the restore job that was initiated earlier in this exercise.

15. Double-click the alternate-directory folder to view its contents.

16. Verify that the smallfiles sub-folder is present in the E:\alternate-directory folder.
17. Double-click the smallfiles folder to view its contents.

The folder should contain 1000 files, file000.txt -- file999.txt.

18. Close the file explorer window.

Exercise F: Restoring Client Files to an Alternate Client System

In this exercise, you use the NetBackup web user interface to restore files backed up from one Linux client system
to an alternate Linux client system. You will use the backup images created using the LAB-clients-to-media-
bdisk policy for this restore.

Viewing the folders on the alternate client system

1. Double-click the PuTTY shortcut located on the desktop of the console system.
2. In the PuTTY Configuration window, double-click the preconfigured entry for the Primary/Master
server, lnxmaster.vrtsedu.lab.
3. Log in to the lnxmaster.vrtsedu.lab system using the following credentials.
o Username: root
o Password: P@ssw0rd

4. In the root@lnxmaster:~ terminal window, execute the following command.

Command: ls -l / | grep data

Following is the expected output of the above command.

drwxr-xr-x. 8 root root 103 Sep 20 2020 data

drwxr-xr-x. 14 root root 169 Jun 15 08:06 msdpdata

In this restore operation, you restore data that was backed up from the Doc_files directory on the
client, lnxmedia.vrtsedu.lab, to the /alternate-client-data directory on the client
system, lnxmaster.vrtsedu.lab. As you can see in the output of the above command, the /alternate-client-
data directory does not currently exist on the lnxmaster.vrtsedu.lab system.

5. Minimize (do not close) the root@lnxmaster:~ window.

 You will return to it later in this lab.

Performing the restore of client files

6. Access the NetBackup web user interface that is open on the console system.
7. In the NetBackup web user interface, in the navigation pane, click Recovery.
8. On the Recover page, click Regular recovery.
9. On the Recover > Basic properties page, perform the following:
a. Select lnxmedia.vrtsedu.lab in the Source client drop-down list.
b. Enter lnxmaster.vrtsedu.lab in the Destination client field.
c. Ensure that Standard is selected in the Policy type drop-down list.
d. After selecting and verifying the source and destination client, the policy type, click Next to proceed.

You have selected to browse the Primary/Master server image catalog to look for backup images of the
client, lnxmedia.vrtsedu.lab that will be restored to the client, lnxmaster.vrtsedu.lab.

10. On the Recover > Add files page, perform the following:

a. Set the Start date to 1st June 2021 and the start time to 12:00:00 AM.

b. Set the End date to today's date and the end time to 11:59:00 PM.

c. After setting the start and end dates and time, click Backup history.

d. In the Backup history window, verify that the latest image created using the LAB-clients-to-media-
bdisk is selected and click Select to close the Backup history window.

e. After verifying the selected backup image, click Add files.

f. In the Add files and folders window, perform the following:

i. Expand the lnxmedia.vrtsedu.lab node and then click the data folder.

ii. Select the Doc_files directory displayed in the right pane of the Add files and folders window.

iii. After selecting the Doc_files directory, click Add in the Add files and folders window to select
the files for restore and return to the Recover > Add files page.

g. Verify that the Doc_files folder selected for restore is now listed on the Recover > Add files page
and click Next.

11. On the Recover > Recovery target page, select the Restore everything to a different directory radio
button.
12. Enter /alternate-client-data/Doc_files in the Directory for restore field and click Next.
13. On the Recover > Recovery options page, click Next without making any changes.
14. On the Review page, check the information and click Start recovery.
 You are automatically redirected to the Activity Monitor page after initiating the restore.

15. Monitor the progress of the restore operation until it runs to successful completion.
16. After the restore is complete, click the Restore job with the highest numbered Job ID and then click View
Details on the actions menu to open the Job Details for this job.
17. In the Overview tab, take a note of the important fields that contain information about the restore job.

Some items to make note of.

From the Overview tab you can see the Client is lnxmaster.vrtsedu.lab, the Primary
server is lnxmaster.vrtsedu.lab. The Files List shows the files (/data/Doc_files) being restored.

18. On the page that displays the details for the restore job, click the Details tab.

From the Details tab note the Media Server used in this restore is lnxmaster.vrtsedu.lab. From the log
messages, look at the third (3rd) line entry, "restoring from image lnxmedia.vrtsedu.lab_XXXXXXXXXX". This is
the only reference to the name of the host in which this data was backed up.

Note that the Activity Monitor does not list the directory to which the data is being restored to. This
information can be seen in the Task Progress tab of the BAR GUI.

19. Click 'x' located in the right corner of the page that displays the details for the restore job, to close the job
details page and return to the Activity Monitor page.
20. Minimize (do not close) the NetBackup web user interface.

You will return to it later in this lab.

Viewing restored files on the alternate client

20. Access the root@lnxmaster:~ window that is open on the console system.
21. In the root@lnxmaster:~ terminal window, execute the following command.

Command: ls -l / | grep data

Following is the output of the above command.

drwxr-xr-x. 3 root root 23 Jul 1 16:34 alternate-client-data

drwxr-xr-x. 8 root root 103 Sep 20 2020 data
drwxr-xr-x. 14 root root 169 Jun 15 08:06 msdpdata

22. Note that following the most recent restore operation, the /alternate-client-data directory is present on
the lnxmaster.vrtsedu.lab system.
23. In the terminal window, execute the following command to list the contents of the /alternate-client-
data directory.
 Command: ls -R /alternate-client-data

As you can see from the output of the ls command, the Doc_files directory and its contents have been
restored to the /alternate-client-data directory on the lnxmaster.vrtsedu.lab system.

24. In the terminal window, type exit and press Enter to log out of the lnxmaster.vrtsedu.lab system and
close this window.

Deactivating policies on the Primary/Master server

In the steps that follow, you deactivate policies that you created in the previous lab, to prevent the automatic
initiation of backup jobs by these policies.

25. Access the NetBackup web user interface that is open on the console system.
26. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
27. On the Policies page, select the checkbox next to the LAB-clients-to-media-bdisk and the LAB-console-
to-media-advdisk policies and then click Deactivate on the actions menu.
28. In the Deactivate policy dialog box, click Yes to deactivate these policies.
29. Verify that the LAB-clients-to-media-bdisk and the LAB-console-to-media-advdisk policies are
deactivated.

A deactive policy is denoted by a gray 'x' icon in the NetBackup web user interface.

30. Sign out of the NetBakcup web user interface and close the browser window.
31. Log out of the console system.

Lab 07: Configuring Media Server Deduplication

Exercise A: Configuring NetBackup Media Server Deduplication

In this exercise, you use the NetBackup web user interface to configure NetBackup MSDP storage.

MSDP configuration consists of the following three main tasks:

 Configuring the MSDP storage server.

 Configuring the MSDP disk pool.
 Configuring the MSDP storage unit.

Viewing disk storage on a NetBackup Media server system

1. Sign in to the console system using the following credentials.

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the PuTTY shortcut located on the desktop of the console system.
3. In the PuTTY Configuration window, double-click the preconfigured entry for the Media
server, lnxmedia.vrtsedu.lab.
4. Log in to the lnxmedia.vrtsedu.lab system using the following credentials.
o Username: root
o Password: P@ssw0rd

5. In the root@lnxmedia:~ terminal window, execute the following command to view details of all mounted
partitions.

Command: df -h

The expected output of the above command is displayed below.

The output identifies the file systems and their associated mount points on the lnxmedia system. Many of
these file systems were pre-configured to serve as storage destinations for NetBackup backup images.
6. Take note of the /dev/sda3 and /dev/sda9 file systems, and their associated mount
points, /msdpdata and /msdpcat.

You will use these partitions later in this lab for configuring MSDP storage.

7. In the root@lnxmedia:~ terminal window, type exit and press Enter to log out of the Media server and
close the terminal window.

Configuring MSDP storage server

8. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system to
launch the NetBackup web user interface.

The Netbackup web user interface can be accessed by navigating to the following URL:
https://Primary server hostname or IP/webui/login.
For the purpose of this lab, a web shortcut is preconfigured for accessing the NetBackup web user interface.

9. If a security warning is displayed, click Advanced > Accept the Risk and Continue.
10. Sign in to the NetBackup web user interface using the following credentials:
o Username: root
o Password: P@ssw0rd

11. In the NetBackup web user interface, in the navigation pane, click Storage > Storage configuration.
12. On the Storage configuration page, click Add.
13. In the Add storage server window, select the Media Server Deduplication Pool (MSDP) radio button
and click Start.
14. On the Add MSDP storage server > Basic properties page, perform the following:

a. Click the Media server field.

b. In the Select media server window, select the lnxmedia.vrtsedu.lab radio button and then
click Select.

c. Enter dedup in the Username field.

d. Enter P@ssw0rd in the Password and Re-enter password fields.

e. Click Next.

15. On the Add MSDP storage server > Storage server options page, perform the following:

. Enter /msdpdata in the Storage path field.

a. Enter /msdpcat in the Use alternate path for deduplication database field.

b. Click Next without making any other changes.

16. On the Add MSDP storage server > Media servers page, click Next without adding any additional
Media servers.
17. On the Add MSDP storage server > Review page, verify the information displayed is correct, and then
click Save to create the MSDP storage server.

It might take 3-5 minutes for creating the MSDP storage server.

After the storage server is created, a success message is displayed in the web user interface along with a
shortcut to launch the disk pool configuration wizard.

Configuring MSDP disk pool

18. Click the Add disk pool shortcut displayed with the success message to start the disk pool configuration
wizard.
19. On the Add disk pool > Disk pool options page, perform the following:

a. Ensure that lnxmedia.vrtsedu.lab is selected as the storage server.

b. Enter media_msdp_dpool in the Disk pool name field.

c. Select the Limit I/O streams checkbox.

d. Ensure that the number of streams is set to 2 per volume.

e. Ensure that the high and low water mark are set to 98% and 80% respectively.

f. Click Next.

20. On the Add disk pool > Volumes page, select the PureDiskVolume and click Next to proceed.
21. On the Add disk pool > Replication page, click Next without adding any replication targets.
22. On the Add disk pool > Review page, verify the information displayed is correct, and then click Finish to
configure the disk pool.

After the disk pool is created, a success message is displayed in the web user interface along with a shortcut
to launch the storage unit configuration wizard.

Configuring MSDP storage unit

23. Click the Add storage unit shortcut displayed with the success message to start the storage unit
configuration wizard.
24. On the Add MSDP storage unit > Basic properties page, perform the following:

a. Enter media_msdp_stu in the Name field.

b. Change the Maximum concurrent jobs setting to 4.

c. Retain the default fragment size and click Next.

25. On the Add MSDP storage unit > Disk pool page, select the media_msdp_dpool disk pool and
click Next.
26. On the Add MSDP storage unit > Media server page, click Next without making any changes.
27. On the Add MSDP storage unit > Review page, verify the information displayed is correct, and then
click Save to create the storage unit.

After the storage unit is created, a success message is displayed in the web user interface.

Verifying MSDP configuration

28. In the NetBackup web user interface, on the Storage configuration page, click the Storage servers tab.
29. Click the MSDP storage server entry for the Media server, lnxmedia.vrtsedu.lab.

The details of the storage server are displayed on a new page.

30. Review the information displayed for the storage server on the details page.
31. Click Edit in the Troubleshooting properties section.

What two options can be modified in the Troubleshooting properties window? See the following answers:

The SPA log retention and the Verbose level options can be modified in the Troubleshooting
properties window.

32. Click Cancel in the Troubleshooting properties window to close this window and return to the storage
server details page.
33. Click Add in the Media servers section.
34. In the Select media servers window, you can select additional Media servers to load balance the
deduplication workload.

Additional Media servers can be used to perform the hash calculations for backups being stored in the Media
server deduplication pool. By selecting a Media server in the Select media servers window, you allow the
selected Media server to access the Media server deduplication pool. After selecting the Media server in
the Select media servers window, the Media server appears in the storage unit's Media server selection list.

35. Click Cancel in the Select media servers window to close this window and return to the storage server
details page.
36. Click 'x' located in the top right corner of the details page to return to the Storage configuration page.
37. On the Storage configuration page, click the Disk pools tab.
38. Verify that the disk pool, media_msdp_dpool configured earlier in this exercise exists in the list of
configured disk pools.
39. Take a note of the information displayed in the Used space and the Volume columns for
the media_msdp_dpool disk pool.
40. Click the media_msdp_dpool entry to view its details.
41. Review the information displayed for the disk pool on the details page.
42. Click Edit in the Disk pool options section.
43. In the Disk pool options window, take a note of the disk pool parameters that can be modified.
44. Click Cancel in the Disk pool options window to close this window and return to the disk pool details
page.
45. Click Add in the Replication targets section.
46. Take a note of the information and the options available in the Add replication targets window.

The settings in the Add replication targets window apply only to AIR between NetBackup domains.

47. Click Cancel in the Add replication targets window to close this window and return to the disk pool
details page.
48. Click 'x' located in the top right corner of the details page to return to the Storage configuration page.
49. On the Storage configuration page, click the Storage units tab.
50. Verify that the storage unit, media_msdp_stu configured earlier in this exercise exists in the list of
configured storage units.
51. Click the media_msdp_stu entry to view its details.
52. Review the information displayed for the storage unit on the details page.

Only certain storage unit parameters can be modified. For an MSDP storage unit, these include the Maximum
concurrent jobs, the Maximum fragment size, and the On demand only parameter. You can also select
specific or multiple Media servers that can access the storage unit on the details page.

53. Click 'x' located in the top right corner of the details page to return to the Storage configuration page.
54. Remain logged in to the NetBackup web user interface.

You will return to it later in this lab.

Exercise B: Configuring a Policy to use MSDP storage

In this exercise, you use the NetBackup web user interface to configure a policy that writes backup images to the
MSDP storage that has been configured on your Media server system.

Creating a policy

1. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
2. On the Policies page, click Add to start creating a new backup policy.
 The Create policy page is displayed and the Attributes tab is selected by default.

Configuring policy Attributes

3. On the Create policy page, in the Attributes tab, perform the following:
a. Enter LAB-console-to-media-msdp in the Policy name field.
b. Select MS-Windows in the Policy type drop-down list.

The operating system of the client is what dictates the Policy type selected in the policy. UNIX and
Windows clients should not share the same policy.

c. Select media_msdp_stu in the Policy storage drop-down list.

d. Retain the default settings for all other attributes and click the Schedules tab.

Configuring policy Schedules

4. On the Create policy page, in the Schedules tab, click Add in the Backup schedules section to add a
new policy schedule.
5. In the Add schedule window, perform the following:

a. Enter full_frequency in the Name field.

b. Ensure that Full Backup is selected in the Type of backup drop-down list.

c. Ensure that the Frequency radio button is selected in the Schedule type section.

d. Change the frequency to 6 hours.

e. Ensure that the Retention is set to 2 weeks (Retention Level 1).

f. Retain the default settings for all other schedule attributes and click the Start window tab.

g. Perform the following in the Start window tab:

i. Select today's day (e.g. Monday) in the Start day drop-down list.

ii. Set the Start time to 10:00:00 PM.

iii. Select tomorrow's day (e.g. Tuesday) in the End day drop-down list.

iv. Set the End time to 02:00:00 AM.

h. Click Add in the Add schedule window to save the schedule.

6. Verify that an entry for the full_frequency schedule is visible in the Backup schedules section under
the Schedules tab.

The figure illustrates the entry for the full_frequency schedule.

 The colored lines (representing the start windows for various types of schedules) in the top half of
the Schedules tab appear after the schedule is saved.

Adding clients to the policy

7. On the Create policy page, click the Clients tab and then click Add to add clients to the policy.
8. In the Add client window, perform the following:
a. Enter console.vrtsedu.lab in the Client name field.
b. Select the Detect client operating system checkbox.

Selecting the Detect client operating system checkbox instructs NetBackup to discover the operating
system of the client. NetBackup can detect the operating system if the NetBackup client software is
installed on the system prior to filling out the policy information.

c. Click Add.

After the client is added, you are returned to the Create policy page.

9. On the Create policy page, verify that client, console.vrtsedu.lab is displayed under the Clients tab.
10. Take note of the contents of the Hardware and Operating System columns under the Clients tab.

The information in these columns was automatically determined by NetBackup by querying the client system.

Adding Backup Selections to a policy

11. On the Create policy page, click the Backup selections tab and then click Add to begin adding backup
selections to the policy.
12. In the Add backup selection window, perform the following:
a. Ensure that Windows is selected in the Pathname or directive set drop-down list.
 b. Click inside the List of pathnames and directives to add to the selection list textbox and
type E:\data.
c. Verify that E:\data is listed in the List of pathnames and directives to add to the selection
list textbox and click Add to add the backup selection to the policy and return to the Create
policy page.
13. On the Create policy page, select each of the tabs -- Attributes, Schedules, Clients, and Backup
Selections -- and briefly verify the contents of each tab.
14. After verifying the contents of each tab, click Create to create the backup policy.

After the backup policy is created, a success message is displayed in the NetBackup web user interface and
you are returned to the Policies page.

15. On the Policies page, verify that the LAB-console-to-media-msdp policy is listed along with other pre-
configured backup policies.
16. Remain logged in to the NetBackup web user interface.

You will return to it later in this lab.

Exercise C: Performing Backups to MSDP storage

In this exercise, you use the LAB-console-to-media-msdp policy to perform manual backups of
the console.vrtsedu.lab client to MSDP storage, and use the Activity Monitor to monitor the progress and
results of the backup jobs.

Performing a manual backup to MSDP storage

1. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
2. Select the checkbox next to the LAB-console-to-media-msdp policy and click Manual backup on the
actions menu.
3. Click OK in the Manual backup window to start the backup.

Because the LAB-console-to-media-msdp policy contains only one schedule and one client entry it is
unnecessary to make schedule or client selections in the Manual Backup window.

Monitoring the backup job and viewing the results

4. In the NetBackup web user interface, in the navigation pane, click Activity monitor.
5. On the Activity Monitor page, locate the most recent backup job that was performed using the LAB-
console-to-media-msdp policy.
 The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 3-5 minutes for this backup to complete.

6. After the job completes, click the Backup job with the highest numbered Job ID.
7. On the actions menu, click View details to view the details for the selected job.

The job details are displayed on a new page and contains two tabs: Overview and Details.

8. Examine the contents of the Overview and the Details tabs and compare your observations with the
following information.

What Deduplication Rate was achieved for the backup job?

73.5% deduplication rate. Your answers may vary.

What is the size of the data that was backed up (according to the Bytes transferred field of the Details
tab)?

805.84 MB. Your answer may vary.

How long did the backup take to complete?

The time required to complete the job may vary (3-4 minutes).

9. View the log messages displayed in the Details tab and locate the entry that includes: Report=PDDO
Stats for xxxmedia.vrtsedu.lab: scanned: xxxxxxx KB, CR sent: xxxxxxx KB. Compare the values of the
“scanned” KB and “sent” KB to the values that follow below.

KB scanned: 826814 KB. Your observations may vary.

KB sent: 219242 KB. Your observations may vary

KB scanned displays the amount of data that the deduplication plug-in scanned and the KB sent is the
amount of data sent from the deduplication plug-in to the component that stores the data. In NetBackup, the
NetBackup Deduplication Engine stores the data.

10. Along with the above, also take note of the following important information displayed in the log
messages for this job.

dedup space saving: 46.2%

dedup space savings denotes the percentage of space saved by data deduplication (data is not written
again).

compression space saving: 27.3%

 compression space savings denotes the percentage of space that is saved because the deduplication engine
compressed some data before writing it to storage.

11. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity Monitor page.

Running and monitoring another manual backup

12. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
13. Select the checkbox next to the LAB-console-to-media-msdp policy and click Manual backup on the
actions menu.
14. Click OK in the Manual backup window to start the backup.
15. After initiating the backup job, select the Activity Monitor entry in the left pane of the NetBackup web
user interface.
16. On the Activity Monitor page, locate the most recent backup job that was performed using the LAB-
console-to-media-msdp policy.

The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 3-5 minutes for this backup to complete.

17. After the job completes, click the Backup job with the highest numbered Job ID.
18. On the actions menu, click View details to view the details for the selected job.
19. Examine the contents of the Overview and the Details tabs and compare your observations with the
information provided in the following table.

What Deduplication Rate was achieved for the backup job?

99.7% deduplication rate. Your answers may vary.

What is the size of the data that was backed up (according to the Bytes transferred field of the Details tab)?

805.84 MB. Your answer may vary, but should be the same KB size as that backed up during the first MSDP
backup job.

How long did the backup take to complete?

The time required to complete the job may vary (3-4 minutes).

22. View the log messages displayed in the Details tab and locate the entry that includes: Report=PDDO
Stats for xxxmedia.vrtsedu.lab: scanned: xxxxxxx KB, CR sent: xxxxxxx KB. Compare the values of the
“scanned” KB and “sent” KB to the values that follow below.
 KB scanned: 826814 KB. Your observations may vary.
KB sent: 2219 KB. Your observations may vary

23. Along with the above, also take note of the following important information displayed in the log
messages for this job.

dedup space saving: 74.9 %

compression space saving: 24.8 %
cache hits: 100 %

cache hits displays the percentage of data segments in the backup that is represented in the local fingerprint
cache. The deduplication plug-in did not have to query the database about those segments.
If the pd.conf file FP_CACHE_LOCAL parameter is set to 0 on the storage, the cache hits output is not
included for the jobs that run on the storage server.

24. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity Monitor page.

Running and monitoring a third manual backup

23. Refer the steps above and initiate another manual backup of the console.vrtsedu.lab client using
the LAB-console-to-media-msdp policy.
24. After initiating the backup job, select the Activity Monitor entry in the left pane of the NetBackup web
user interface.
25. On the Activity Monitor page, locate the most recent backup job that was performed using the LAB-
console-to-media-msdp policy.

The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 3-5 minutes for this backup to complete.

26. After the job completes, click the Backup job with the highest numbered Job ID.
27. On the actions menu, click View details to view the details for the selected job.
28. Examine the contents of the Overview and the Details tabs and compare your observations with the
following information:

What Deduplication Rate was achieved for the backup job?

99.7% deduplication rate. Your answers may vary.

What is the size of the data that was backed up (according to the Bytes transferred field of the Details
tab)?

805.84 MB. Your answer may vary.

 How long did the backup take to complete?

The time required to complete the job may vary (2-3 minutes).

29. View the log messages displayed in the Details tab and locate the entry that includes: Report=PDDO
Stats for xxxmedia.vrtsedu.lab: scanned: xxxxxxx KB, CR sent: xxxxxxx KB. Compare the values of the
“scanned” KB and “sent” KB to the values that follow below.

KB scanned: 826814 KB. Your observations may vary.

KB sent: 2219 KB. Your observations may vary

30. Along with the above, also take note of the following important information displayed in the log
messages for this job.

dedup space saving: 74.9 %

compression space: 24.8 %
cache hits: 100 %

31. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity Monitor page.
32. Compare your observations of the MSDP feature and the results of the backups that were performed of
the console.vrtsedu.lab client with the following information.

The backup images for these jobs were written to MSDP storage on the Media server, lnxmedia.vrtsedu.lab.

o The first backup of a client that is written to MSDP storage achieves a lower data deduplication rate
because the MSDP server has not calculated fingerprints for many of the data segments that are
backed up. Some degree of deduplication may occur during the first backup to MSDP storage --
depending on the situation.
o The first backup of the client to MSDP storage is likely to take somewhat longer than subsequent
backups of the client to MSDP storage.
o The second backup of the client to MSDP storage -- assuming the data on the client has not changed
substantially -- should achieve a very high deduplication rate, approaching 100%. The amount of data
that is "backed up" is far greater than the actual amount of data that is written to MSDP storage (as
many data segments from the client already exist in MSDP storage). It is not necessary to write the
duplicate data segments to MSDP storage again -- these data segments are deduplicated.
o The second backup of the client to MSDP storage should require less time, barring changes in other
factors such as network traffic loads and CPU utilization on the client and Media server systems that
are beyond the control of the MSDP feature.
o Performance and deduplication differences between the second backup of a client to MSDP storage
and subsequent backups of the client may obtain much the same results, unless the data on the client
changes substantially between backup job executions.
33. Minimize (do not close) the NetBackup web user interface.

You will return to it later in this lab.

Exercise D: Configuring and using Client-side Deduplication

In this exercise, you configure a NetBackup client to perform deduplication of the client backup data. This is a
NetBackup feature referred to as client-side deduplication. Client-side deduplication reduces the deduplication
workload on the Media server system, and results in a reduced volume of backup data that is transferred over the
network.

Enabling client-side deduplication for a client

1. Double-click the NetBackup 10.0 Administration Console shortcut located on the desktop of
the console system.
2. In the NetBackup Administration Console window, perform the following:

a. Ensure that lnxmaster.vrtsedu.lab is displayed in the Host name field.

b. In the Login using section, ensure that the User name and password radio button is selected.

c. Enter root in the User name field and P@ssw0rd in the Password field.

d. Click Login.

3. In the NetBackup Administration Console, navigate to NetBackup Management > Host Properties >
Master Servers.
4. In the right pane of the NetBackup Administrator Console, double-click lnxmaster.vrtsedu.lab.
5. In the Master Server Properties window, in the navigation pane, click the Client Attributes entry.

The Client Attributes screen is displayed in the right pane of the Master Server Properties window.

6. Take note that the Client Attributes pane contains a Clients pane that may contain entries for various
clients.
7. On the Client Attributes screen, click Add to add a new client.

The Add button is located immediately below the Clients pane.

8. In the Add Client window, enter console.vrtsedu.lab in the Enter Client Name field and click Add.
9. Click Close in the Add Client window to return to the Client Attributes screen.
10. Verify that the client, console.vrtsedu.lab is now listed in the Clients pane.
11. Click to select the entry for console.vrtsedu.lab in the Clients pane.
12. With the entry for the console.vrtsedu.lab client highlighted, click the drop-down arrow for
the Deduplication location field.
13. Verify the options for the Deduplication location in the drop-down menu are as listed in the following
table.
 1 Always use the media server

2 Prefer to use client-side deduplication

3 Always use client-slide deduplication

14. Select Always use client-side deduplication in the Deduplication location drop-down list.

The Deduplication location selection applies only to the console.vrtsedu.lab client in this situation. To
make the selection for other clients you must first add the clients to the Clients pane, and then set
the Deduplication location for each client.
The default Deduplication location selection for all clients is to "Always use the media server" (to perform
deduplication of the client backup data).

15. Click Apply to save the changes to the Client Attribute setting for the console.vrtsedu.lab client.
16. Click OK to close the Master Server Properties window.
17. In the Restart Daemons dialog box, click OK to close this dialog box.

A restart of the NetBackup daemons is not required to implement the change to the Deduplication
location for the console.vrtsedu.lab client.

18. Minimize (do not close) the NetBackup Administration Console.

You will return to it later in this lab.

Testing client-side deduplication backups

19. Access the NetBackup web user interface that is open on the console system.
20. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
21. Select the checkbox next to the LAB-console-to-media-msdp policy and click Manual backup on the
actions menu.
22. Click OK in the Manual backup window to start the backup.
23. After initiating the backup job, select the Activity Monitor entry in the left pane of the NetBackup web
user interface.
24. On the Activity Monitor page, locate the most recent backup job that was performed using the LAB-
console-to-media-msdp policy.

The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 3-5 minutes for this backup to complete.

25. After the job completes, click the Backup job with the highest numbered Job ID.
26. On the actions menu, click View details to view the details for the selected job.
27. Examine the contents of the Overview and the Details tabs and compare your observations with the
following information:

What Deduplication Rate was achieved for the backup job?

99.7% deduplication rate. Your answers may vary.

What is the size of the data that was backed up (according to the Bytes transferred field of the Details
tab)?

805.84 MB. Your answer may vary.

How long did the backup take to complete?

The time required to complete the job may vary (2-3 minutes).

28. View the log messages displayed in the Details tab and locate the entries that includes: Report=PDDO
Stats for xxxmedia.vrtsedu.lab: scanned: xxxxxxx KB, CR sent: xxxxxxx KB.

How many sets of scanned/sent information are listed?

There are two sets of scanned/sent information listed in the log messages for a client-side deduplication job.

The first set as displayed in the following example is the deduplication rate for the client data.

Info lnxmedia.vrtsedu.lab (pid=28967)

StorageServer=PureDisk:lnxmedia.vrtsedu.lab; Report=PDDO Stats (multi-threaded
stream used) for (lnxmedia.vrtsedu.lab): scanned: 825521 KB, CR sent: 2197 KB,
CR sent over FC: 0 KB, dedup: 99.7%, cache hits: 17142 (100.0%), where dedup
space saving:75.0%, compression space saving:24.7%

The second set as displayed in the following example is the deduplication rate for the metadata (disk image
header and True Image Restore information (if applicable)).

Info lnxmedia.vrtsedu.lab (pid=28967)

StorageServer=PureDisk:lnxmedia.vrtsedu.lab; Report=PDDO Stats for
(lnxmedia.vrtsedu.lab): scanned: 1292 KB, CR sent: 22 KB, CR sent over FC: 0
KB, dedup: 98.3%, cache disabled, where dedup space saving:22.7%, compression
space saving:75.6%

29. Along with the above, also take note of the following important information displayed in the log
messages for this job.

dedup space saving: 75% for both client data and the metadata.
compression space: 24.7% for the client data and 75.6% for the metadata.
cache hits: 100% for the client data and disabled for the metadata.
 If the pd.conf file FP_CACHE_LOCAL parameter is set to 0 on the storage, the cache hits output is not
included for the jobs that run on the storage server.

30. Also note the following information in the detailed messages for this job.

Info lnxmedia.vrtsedu.lab (pid=28967) Using OpenStorage client direct to backup

from client console.vrtsedu.lab to lnxmedia.vrtsedu.lab

The Using OpenStorage client direct … message indicates that the backup travelled over the client-direct
data path and did not use NetBackup Media server components to process the data.

From the results of the backup job, you can see that the change from performing deduplication of the client
data at the storage server (Media server) to performing the backup data deduplication at the client was the
result of setting of the Deduplication location parameter in the Client Attributes for the client in
the Master Server Host Properties.
For the client, console.vrtsedu.lab, the Deduplication location is set to perform backup data deduplication
at the client for all backup images that are written to deduplication storage (MSDP), or to any storage that
uses the OST plug-in. Backup images of the client data that are written to other non-deduplication storage
are not affected by the Deduplication location parameter.

31. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity Monitor page.

Overriding the Deduplication location host property setting using a NetBackup policy attribute

32. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
33. On the Policies page, select the checkbox next to the LAB-console-to-media-msdp policy.
34. On the actions menu, click the Copy policy option.
35. In the Copy policy window, enter LAB-console-to-media-msdp-override in the New policy field and
click Copy.

A new policy LAB-console-to-media-msdp-override is created and contains the same settings as the
original policy.

36. On the Policies page, select the checkbox next to the LAB-console-to-media-msdp-override policy.

If the LAB-console-to-media-msdp policy is still selected, deselect it before selecting the LAB-console-to-
media-msdp-override policy.

37. After selecting the policy, click Edit on the actions menu to open the policy for editing.
38. On the Edit policy page, in the Attributes tab, select the Disable client-side deduplication option.
39. Click Save without making any other changes to update the policy and return to the Policies page.
Performing another backup to MSDP storage

40. On the Policies page, select the checkbox next to the LAB-console-to-media-msdp-override policy and
click Manual backup on the actions menu.
41. Click OK in the Manual backup window to start the backup.
42. After initiating the backup job, select the Activity Monitor entry in the left pane of the NetBackup web
user interface.
43. On the Activity Monitor page, locate the most recent backup job that was performed using the LAB-
console-to-media-msdp-override policy.

The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 3-5 minutes for this backup to complete.

44. After the job completes, click the Backup job with the highest numbered Job ID.
45. On the actions menu, click View details to view the details for the selected job.
46. Examine the contents of the Details tabs and note the following.

Deduplication of the client backup data occurred on the Media server (lnxmedia.vrtsedu.lab) for this backup
job. The message containing "Using OpenStorage client direct …" is absent from the log messages in
the Details pane. This message provides the best indication that client-side deduplication was performed. The
absence of the message indicates that deduplication occurred on the Media server.

47. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity Monitor page.

The Deduplication location setting to "Always use client-side deduplication" in the Client Attributes for a
client in the Master Server Host Properties can be overridden by selecting the Disable client-side
deduplication policy attribute. The Disable client-side deduplication policy attribute setting overrides
client-side deduplication only for backups of the client that use that policy (in which the Disable client-side
deduplication policy attribute was set).
Enabling the Deduplication location parameter to "Always use client-side deduplication" for a client may
have negative, unintended consequences if that client is also backed up to storage that does not support the
use of the OST plug-in -- such as AdvancedDisk storage. After configuring a client to always use client-side
deduplication (also called client-direct), if the client is backed up to NetBackup storage units that do not
support the OST plug-in, those backup jobs will fail with a status 83 (media open error). Therefore it is
important to set the Disable client-side deduplication policy attribute for backup policies that are targeted
to storage units that do not support the OST plug-in.

48. Remain logged in to the NetBackup web user interface.

You will return to it later in this lab.

Exercise E: Managing and Monitoring NetBackup MSDP storage

In this exercise, you view the global deduplication ratio, view MSDP process on the storage server, use NetBackup
provided commands to view information about MSDP storage server and disk pool, and view storage usage within
MSDP container files.

Monitoring the MSDP deduplication rate

1. Access the NetBackup web user interface that is open on the console system.
2. In the NetBackup web user interface, in the navigation pane, click Storage > Storage configuration.
3. Click the MSDP storage server entry for the Media server, lnxmedia.vrtsedu.lab.
4. Take note of the used capacity and raw size displayed in the Storage pool used space field.

The information displayed in the Storage pool used space field enables the backup administrator to monitor
NetBackup for situations where storage space in a disk pool is running low.

5. Click More to view additional details of the MSDP storage server.

6. Take note of the global deduplication ratio displayed in the Deduplication ratio field.

The global deduplication ratio is the percentage of data that was stored already. That data is not stored again.

7. Sign out of the NetBackup web user interface and close the browser window.

Monitoring MSDP processes

8. Double-click the PuTTY shortcut located on the desktop of the console system.
9. In the PuTTY Configuration window, double-click the preconfigured entry for the Media
server, lnxmedia.vrtsedu.lab.
10. Log in to the lnxmedia.vrtsedu.lab system using the following credentials:
o Username: root
o Password: P@ssw0rd

11. In the root@lnxmedia:~ terminal window, execute the following command view MSDP processes that are
started on the storage server (in this case, lnxmedia.vrtsedu.lab) after configuring MSDP.

Command: bpps -x | grep -E "spad|spoold|mtstrms"

Review the output of the above command.

The NetBackup Deduplication Engine (spoold) is one of the storage server core components. It manages
the data container files (write/read data from the datastore, compact/remove containers, and so on). It also
manages the fingerprint cache, processes the transaction queue, checks integrity of the data, and resolves
integrity problems, if any.
 The NetBackup Deduplication Manager (spad) maintains the configuration and controls internal processes,
optimized duplication, security, and event escalation. It checks the storage space every 20 seconds and
compacts the space available inside the container files.

The NetBackup Deduplication Multi-Threaded Agent (mtstrms) provides multiple communications

pipelines between the MSDP deduplication plug-in and the MSDP storage server, and enables improved
backup performance.

Using nbdevquery to view storage server information

12. In the root@lnxmedia:~ terminal window, execute the following command to list the
configured MSDP storage servers.

Command: nbdevquery -liststs -stype PureDisk

13. Note the output of the command, including the entry for the MSDP storage server that was configured on
the Media server system, lnxmedia.vrtsedu.lab earlier in this lab.
14. Execute the nbdevquery command again, this time adding the -U command option as shown below.

Command: nbdevquery -liststs -stype PureDisk -U

15. Scroll through the command output to locate information for the MSDP storage server on the Media
server system, lnxmedia.vrtsedu.lab.
16. Take note of the information that are included in the command output.

Using nbdevquery to view disk pool information

You can use options of the nbdevquery command to view the configuration and status of all disk pools or of
selected disk pools.

17. Execute the nbdevquery command, using the -listdp command option to view disk pool information.
Execute the command with the syntax shown below.

Command: nbdevquery -listdp -stype PureDisk

18. Take note of the command results.

19. Execute the nbdevquery command using the command syntax shown below, to obtain information on a
specific disk pool name, as shown below.

Command: nbdevquery -listdp -stype PureDisk -U -dp media_msdp_dpool

The output of this command provides information about the specified disk pool.

20. Take note of the current status of the media_msdp_dpool disk pool.
 The current status of the disk pool should be "UP".

Using the nbdevconfig command to change the status of a disk pool

You can use the nbdevconfig command to change the status of a specified disk pool.

21. Execute the below command to change the status of the media_msdp_dpool from "UP" to "DOWN".

Command: nbdevconfig -changestate -stype PureDisk -dp media_msdp_dpool -state DOWN

22. Note the output of the nbdevconfig command.

23. Execute the below nbdevquery command to view the status of the media_msdp_dpool disk pool

Command: nbdevquery -listdp -stype PureDisk -U -dp media_msdp_dpool

24. Take note of the current status of the media_msdp_dpool disk pool.

The current status of the disk pool should be "DOWN".

25. Execute the below command to change the status of the media_msdp_dpool from "DOWN" to "UP".

Command: nbdevconfig -changestate -stype PureDisk -dp media_msdp_dpool -state UP

26. Note the output of the nbdevconfig command.

27. Execute the below nbdevquery command to view the status of the media_msdp_dpool disk pool

Command: nbdevquery -listdp -stype PureDisk -U -dp media_msdp_dpool

28. Take note of the current status of the media_msdp_dpool disk pool.

The current status of the disk pool should be "UP".

It might take a minute or two for the disk pool status to change to UP. Do not continue until you have
returned the media_msdp_dpool to a status of "UP".

Viewing storage usage within MSDP container files

The NetBackup crcontrol command can be used to report on storage usage within containers.

29. Execute the below command to view storage usage within MSDP container files.

Command: /usr/openv/pdde/pdcr/bin/crcontrol --dsstat

From the output of the crcontrol --dsstat command, you can determine the following:
 RAW The raw size of the storage

The size of the storage that NetBackup can use: the Raw size of the storage minus the file system
Size
Reserved space

The amount of deduplicated data that is stored on the file system. NetBackup obtains the file
Used
system used space from the operating system

Avail The Size minus the Used space.

Use% The Used space divided by the Size.

30. In the root@lnxmedia:~ terminal window, type exit and press Enter to log out of the lnxmedia system.
31. Log out of the console system.

Lab 08: Configuring Cloud Storage

Exercise A: Performing Preliminary Tasks

In this exercise, you verify that MinIO is running on the cloud1 system. You also view the contents of the directory
that will be the target directory for backups to the cloud.

In this lab environment, the MinIO application is installed and configured on the cloud1 system and is used to
simulate cloud storage.

Verifying MinIO on cloud1

1. Sign in to the console system using the following credentials.

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the PuTTY shortcut located on the desktop of the console system.
3. In the PuTTY configuration window that is displayed, double-click the preconfigured entry for the cloud
server, cloud1.vrtsedu.lab.
 4. If a PuTTY Security Alert dialog box is displayed, click Yes to trust the cloud1 system.
5. Login to the cloud1 system using the credentials below.
o Username: root
o Password: P@ssw0rd

6. In the root@cloud1:~ terminal window, execute the following command to verify that
the MinIO application is running.

Command: systemctl status minio

The expected output of the above command is displayed in the figure below.

If the MinIO application is not running, start the application by executing the systemctl start minio command.

7. Execute the below command to view details of the minio process.

Command: ps -ef | grep -i minio

The expected output of the above command is displayed in the figure below.

The process IDs (PIDs) shown in the command output might differ from those shown in the screenshots
above.

Viewing cloud storage on cloud1

In the steps that follow, you view the contents of the directory that will be the target directory for backups to the
cloud.
8. In the root@cloud1:~ terminal window, execute the following command to view the contents of
the minio.conf file.

Command: cat /opt/minio/minio.conf

The expected output of the above command is displayed in the figure below.

The /opt/minio/data directory is configured as the filesystem base directory and will be the target directory
for backups to the cloud.

9. Execute the following command to view the contents of the /opt/minio/data directory.

Command: ls -l /opt/minio/data

The expected output of the above command is displayed in the figure below.

The three directories (nb-bucket1, nb-bucket2, and nb-bucket3) present in the /opt/minio/data directory
are presented as S3 buckets to NetBackup. You will use one of these directories to configure cloud storage in
NetBackup.

10. Execute the below command one at a time to verify that the nb-bucket1, nb-bucket2, nb-
bucket3 directories do not contain any data.

Command: ls -l /opt/minio/data/nb-bucket1 /opt/minio/data/nb-bucket2 /opt/minio/data/nb-bucket3

The expected output of the above command is displayed in the figure below.
11. Minimize the root@cloud1:~ window to return to the desktop of the console system. You will return to it
later in this lab.

Exercise B: Configuring Cloud Storage in NetBackup

In this exercise, you use the NetBackup web user interface to configure a cloud storage server, disk pool, and
storage unit.

Accessing the NetBackup web user interface

1. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system to
launch the NetBackup web user interface.

The Netbackup web user interface can be accessed by navigating to the following URL:
https://Primary server hostname or IP/webui/login.
For this lab, a web shortcut is preconfigured for accessing the NetBackup web user interface.

2. If a security warning is displayed, click Advanced > Accept the Risk and Continue.
3. Sign in to the NetBackup web user interface using the credentials below.
o Username: root
o Password: P@ssw0rd

Configuring a cloud storage server

4. In the NetBackup web user interface, in the navigation pane, click Storage > Storage configuration.
5. On the Storage configuration page, click Add.
6. In the Add storage server window, select the Cloud storage radio button and click Start.
7. On the Add cloud storage server > Basic properties page, perform the following:
a. Enter amazon-cp in the Storage server name field.
b. Click the Cloud storage provider field to open the Select cloud storage provider window.
c. In the Select cloud storage provider window, perform the following:
i. Type Amazon in the Search field.
ii. From the list of cloud storage providers, select Amazon.
 The figure above displays the Select cloud storage provider window with the Amazon provider
selected.

iii. Click Select to close the Select Cloud storage provider window.
d. Verify that the Storage API type is set to Amazon S3.
e. Ensure that Standard is selected in the Storage class drop-down list.

This option is available only for Amazon and Amazon GovCloud cloud providers.

f. Click Add available in the Region section to add a new region.

g. In the Add a region window that is displayed, perform the following:
i. Enter US-West (Oregon) in the Region name field.
ii. Enter us-west-2 in the Location constraint.
iii. Enter cloud1.vrtsedu.lab in the Service URL field.
iv. Select Path style in the Endpoint access style drop-down list.
v. Change the HTTP port to 9000.
vi. Verify that the HTTPS port is set to 443.
vii. Click Add to add the region and close the Add a region window.
 The figure above displays the Add a region window with the above listed settings configured.

h. Click the Select a media server field to open the Select media server window.
i. In the Select media server window, click the radio button next to lnxmedia.vrtsedu.lab ,and then
click Select
j. In the Region section, select the radio button next to the newly configured service
host, cloud1.vrtsedu.lab.

The new region will be listed as the first entry in the Region section.

k. Click Next without making any other changes.

8. On the Add cloud storage server > Access settings page, perform the following:
a. Ensure that the Access details for Amazon account radio button is selected.
b. Enter AKIAIBF7UPBYCBBWEWQA in the Access key ID field.
c. Enter FjpA1FZ25Orl+j5us6WLoBUO/O3kcd2xQa2YgjRp in the Secret access key field.
d. Deselect the Use SSL option in the Advanced settings section.
e. Leave the Use proxy server option unchecked.
 The figure above displays the Access settings page with the above listed settings configured.

f. Click Next.
9. On the Add cloud storage server > Storage server options page, click Next without making any
changes to the object size, compression, and encryption settings.

During backup, NetBackup divides the backup image data into chunks called objects. PUT request is made for
each object to move it to the cloud storage.

By setting a custom Object Size, you can control the amount of PUT and GET requests that are sent to and
from the cloud storage. The reduced number of PUT and GET requests help in reducing the total charges that
are incurred for the requests.

Once you set the Object Size for a cloud storage server, you cannot change the value. If you want to set a
different Object Size, you must recreate the cloud storage server.
NetBackup Media servers that are older than the 7.7.3 version do not support data compression. Therefore, if
you have selected an older Media server, the compression option does not appear on the panel.

10. On the Add cloud storage server > Media servers page, click Next to proceed without adding any
additional Media servers.

The NetBackup Media servers that you use for cloud storage backup the NetBackup clients and then send
that backup data to the cloud storage server. The storage server then writes the data to storage.
 The NetBackup Media servers also can move data back to primary storage (the client) during restores and
from secondary storage to tertiary storage during duplication. These Media servers are also known as data
movers. They host a software plug in that they use to communicate with the storage implementation.

You can add additional Media servers to backup clients. They can help balance the load of the backups that
you send to the cloud storage.

11. On the Add cloud storage server > Review page, verify the information displayed is correct, and then
click Finish to create the cloud storage server.

It might take 1-2 minutes for creating the cloud storage server.

After the storage server is created, a success message is displayed in the web user interface along with a
shortcut to launch the disk pool configuration wizard.

Configuring a Disk Pool for the cloud

12. Click the Add disk pool shortcut displayed with the success message to start the disk pool configuration
wizard.
13. On the Add disk pool > Disk pool options page, perform the following:

a. Ensure that the storage server is set to amazon-cp.

b. Enter media_cloud_dpool in the Disk pool name field.

c. Select the Limit I/O streams checkbox.

d. Ensure that the number of streams is set to 2 per volume.

e. Click Next.

14. On the Add disk pool > Volumes page, select nb-bucket1 as illustrated in the figure below and
click Next.
 Buckets are not available for use in NetBackup if the bucket name does not comply with the bucket naming
convention.

15. On the Add disk pool > Review page, verify the information displayed is correct, and then click Finish to
configure the disk pool.

After the disk pool is created, a success message is displayed in the web user interface along with a shortcut
to launch the storage unit configuration wizard.

Configuring a Storage Unit for the cloud

16. Click the Add storage unit shortcut displayed with the success message to start the storage unit
configuration wizard.
17. On the Add Cloud storage unit > Basic properties page, perform the following:

a. Enter media_cloud_stu in the Name field.

b. Change Maximum concurrent jobs to 2.

c. Do not make any changes to the Maximum fragment size.

d. Click Next.

18. On the Add Cloud storage unit > Disk pool page, select media_cloud_dpool and click Next.
19. On the Add Cloud storage unit > Media server page, click Next without making any changes.
20. On the Add Cloud storage unit > Review page, verify the information displayed is correct, and then
click Save to create the storage unit.

After the storage unit is created, a success message is displayed in the web user interface.
Verifying Cloud configuration

21. In the NetBackup web user interface, on the Storage configuration page, click the Storage servers tab.
22. Click the Cloud storage server entry for the storage server, amazon-cp.

The details of the storage server are displayed on a new page.

23. Review the information that is displayed for the storage server on the details page.

What properties/options can you add/change for a cloud storage server on the details page?

You can only add/remove additional Media servers from the details page.

24. Click 'x' located in the top right corner of the details page to return to the Storage configuration page.
25. On the Storage configuration page, click the Disk pools tab.
26. Verify that the disk pool, media_cloud_dpool configured earlier in this exercise exists in the list of
configured disk pools.
27. Note that no information is displayed in the Used space column for the media_cloud_dpool disk pool.

No information is displayed in the Used space column for a cloud disk pool because these values are derived
from the storage capacity, which cannot be fetched from the cloud provider.

28. Click the media_cloud_dpool entry to view its details.

29. Review the information that is displayed for the disk pool on the details page.
30. Click Edit in the Disk pool options section.
31. In the Disk pool options window, take a note of the disk pool parameters that can be modified.
32. Click Cancel in the Disk pool options window to close this window and return to the disk pool details
page.
33. Click 'x' located in the top right corner of the details page to return to the Storage configuration page.
34. On the Storage configuration page, click the Storage units tab.
35. Verify that the storage unit, media_cloud_stu configured earlier in this exercise exists in the list of
configured storage units.
36. Click the media_cloud_stu entry to view its details.
37. Review the information that is displayed for the storage unit on the details page.

Only certain storage unit parameters can be modified. For an cloud storage unit, these include the Maximum
concurrent jobs, the Maximum fragment size, and the On demand only parameter. You can also add/remove
Media servers that can access the storage unit on the details page.

38. Click 'x' located in the top right corner of the details page to return to the Storage configuration page.
39. Remain logged in to the NetBackup web user interface.
 You will return to it later in this lab.

Exercise C: Configuring and Performing Backups to the Cloud

In this exercise, you create a backup policy and initiate a manual backup to backup data to the cloud storage
configured earlier in this lab. After initiating the backup job, you monitor the resulting job and verify the successful
completion of the job.

Creating a policy

1. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
2. On the Policies page, select the checkbox next to the LAB-console-to-media-msdp policy.
3. On the actions menu, click the Copy policy option.
4. In the Copy policy window, enter LAB-console-to-cloud in the New policy field and click Copy.

A new policy LAB-console-to-cloud is created and contains the same settings as the original policy.

5. On the Policies page, select the checkbox next to the LAB-console-to-cloud policy.

If the LAB-console-to-media-msdp policy is still selected, deselect it before selecting the LAB-console-to-
cloud policy.

6. After selecting the policy, click Edit on the actions menu to open the policy for editing.
7. On the Edit policy page, select media_cloud_stu in the Policy storage drop-down list.
8. Click Save without making any other changes to update the policy and return to the Policies page.
9. On the Policies page, select the checkbox next to the LAB-console-to-cloud policy.
10. After selecting the policy, click Activate on the actions menu to activate this policy.

Initiating a manual backup to cloud storage

11. On the Policies page, select the checkbox next to the LAB-console-to-cloud policy and click Manual
backup on the actions menu.
12. Click OK in the Manual backup window to start the backup.

Because the LAB-console-to-cloud policy contains only one schedule and one client entry it is unnecessary
to make schedule or client selections in the Manual Backup window.
Monitoring the backup job and viewing the results

13. In the NetBackup web user interface, click Activity monitor.

14. On the Activity monitor page, locate the most recent backup job that was performed using the LAB-
console-to-cloud policy.

The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 2-4 minutes for this backup to complete.

15. After the job completes, click the Backup job with the highest numbered Job ID.
16. On the actions menu, click View details to view the details for the selected job.

The job details are displayed on a new page and contains two tabs: Overview and Details.

17. Briefly view the the contents of the Overview and the Details tabs.
18. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity monitor page.
19. Minimize (do not close) the NetBackup web user interface.

You will return to it later in this lab.

Viewing the cloud-based storage

20. Access the root@cloud1:~ PuTTY window that is open on the console system.
21. In the root@cloud1:~ terminal window, execute the below command to list the contents of
the /opt/minio/data/nb-bucket1 directory.

Command: ls -l /opt/minio/data/nb-bucket1

22. Note that the directory contains two files (assuming that only a single backup job was performed).

The two files are the backup image files for the backup of the client, console.vrtsedu.lab, that used the LAB-
console-to-cloud backup policy.

23. In the root@cloud1:~ terminal window, type exit and press Enter to log out of the cloud1 system.

Exercise D: Restoring Client Data from Cloud-based Storage

In this exercise, you use a NetBackup backup image that was written to cloud storage to perform a restore of client
data.

Preparing the client system (console.vrtsedu.lab) for the restore

1. Double-click the File Explorer shortcut located on the desktop of the console system.
2. In the This PC explorer window, double-click the DATA drive (drive letter E) to view its contents.
3. Double-click the data folder located in the DATA drive.

The sub-folders of the data folder are displayed.

4. Right-click the smallfiles folder and, in the resulting menu, click Delete.

The E:\data directory on the console system was backed up using the LAB-console-to-cloud policy earlier in
this lab.

5. Minimize (do not close) the file explorer window.

You will return to it later in this lab.

Restoring client data from a cloud-based backup image

6. Access the NetBackup web user interface that is open on the console system.
7. In the NetBackup web user interface, in the navigation pane, click Recovery.
8. On the Recover page, click Regular Recovery.
9. On the Recover > Basic properties page, perform the following:

a. Select console.vrtsedu.lab in the Source client drop-down list.

b. Ensure that console.vrtsedu.lab is displayed in the Destination client field.

c. Ensure that MS-Windows is selected in the Policy type drop-down list.

d. After selecting and verifying the source and destination client, the policy type, click Next to proceed.

10. On the Recover > Add files page, perform the following:

a. Set the Start date to today's date and the start time to 12:00:00 AM.

b. Set the End date to today's date and the end time to 11:59:00 PM.

c. After setting the start and end dates and time, click Backup history.

d. In the Backup history window, ensure that the backup image created using the LAB-console-to-
cloud policy is the only image that is selected.
 e. Click Cancel in the Backup history window to return to the Recover > Add files page.

f. Click Add files.

g. In the Add files and folders window, perform the following:

i. Expand the console.vrtsedu.lab node and then expand the E drive.

ii. Click the data folder in the left pane and then select the smallfiles directory displayed in the
right pane of the Add files and folders window.

iii. After selecting the smallfiles directory, click Add in the Add files and folders window to select
the files for restore and return to the Recover > Add files page.

h. Verify that the smallfiles folder selected for restore is now listed on the Recover > Add files page
and click Next.

11. On the Recover > Recovery target page, ensure that the Restore everything to the original
directory radio button is selected and click Next.
12. On the Recover > Recovery options page, click Next without making any changes.
13. On the Recover > Review page, click Start Recovery to start the restore.

You are automatically redirected to the Activity monitor page after initiating the restore.

14. Monitor the progress of the restore operation until it runs to successful completion.
15. After the restore is complete, sign out of the NetBackup web user interface and close the browser window.

Viewing restored files on the client system

16. Access the file explorer window that is open on the console system.
17. Verify that the smallfiles folder deleted earlier in this exercise has been restored.
18. Double-click the smallfiles folder to view its contents.

The folder should contain 1000 files, file000.txt -- file999.txt.

19. Close the file explorer window.

20. Log out of the console system.
Lab 09: Optimizing Filesystem Backups

Exercise A: Configuring and Performing Synthetic Backups

In this exercise, you configure, perform, and monitor Synthetic backups.

Configuring Synthetic backups

1. Sign in to the console system using the following credentials:

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system to
launch the NetBackup web user interface.

The Netbackup web user interface can be accessed by navigating to the following URL:
https://Primary server hostname or IP/webui/login.
For the purpose of this lab, a web shortcut is preconfigured for accessing the NetBackup web user interface.

3. If a security warning is displayed, click Advanced > Accept the Risk and Continue.
4. Sign in to the NetBackup web user interface using the following credentials:
o Username: root
o Password: P@ssw0rd

5. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
6. On the Policies page, click Add to start creating a new backup policy.

The Create policy page is displayed and the Attributes tab selected by default.

7. On the Create policy page, in the Attributes tab, perform the following:
a. Enter LAB-synthetic-backup in the Policy name field.
b. Select MS-Windows in the Policy type drop-down list.

The operating system of the client is what dictates the Policy type selected in the policy. UNIX and
Windows clients should not share the same policy.
Only Standard and MS-Windows policy types are supported for a synthetic backup policy.

c. Select media_bdisk_stu in the Policy storage drop-down list.

Synthetic backups targeted to a MSDP storage unit are known as Optimized Synthetic backups and are
faster than regular synthetic backups. For the purpose of this lab, we will use a BasicDisk storage unit for
performing synthetic backups.
 d. Retain the default settings for all other attributes and click the Schedules tab.

A minimum of three backup schedules must be included in a synthetic backup policy. A traditional full backup
schedule, a differential or a cumulative incremental backup schedule, and a synthetic full backup schedule.

8. In the Schedules tab, click Add in the Backup schedules section to add a full backup schedule.
9. In the Add schedule window, perform the following:

. Enter full_traditional in the Name field.

a. Ensure that Full Backup is selected in the Type of backup drop-down list.

b. Ensure that the Frequency radio button is selected in the Schedule type section.

c. Ensure that the frequency is set to 1 week.

d. Select 1 week (Retention Level 0) in the Retention drop-down list.

e. Retain the default settings for all other schedule attributes and click Save and add another in
the Add schedule window to save this schedule and add an incremental backup schedule.

10. In the Add schedule window, perform the following:

. Enter diffincr in the Name field.

a. Select Differential Incremental Backup in the Type of backup drop-down list.

b. Ensure that the Frequency radio button is selected in the Schedule type section.

c. Change the frequency to 12 hours.

d. Select 1 week (Retention Level 0) in the Retention drop-down list.

e. Retain the default settings for all other schedule attributes and click Add in the Add
schedule window to save the schedule.

11. In the Schedules tab, Verify that entries for the full_traditional and the diffincr schedules is visible in
the Backup schedules section.
12. Click Add in the Backup schedules section to add a synthetic full backup schedule.
13. In the Add schedule window, note that the Synthetic backup option is disabled.

Synthetic backup can be enabled only if the Collect true image restore information and the with move
detection policy attributes are selected.

14. In the Add schedule window, click Cancel and then click Attributes tab.
15. In the Attributes tab, select the Collect true image restore information and the with move
detection policy attributes, and then click the Schedules tab.
16. In the Schedules tab, click Add in the Backup schedules section to add a synthetic full backup schedule.
17. In the Add schedule window, perform the following:

. Enter full_synthetic in the Name field.

a. Ensure that Full Backup is selected in the Type of backup drop-down list.

b. Select the Synthetic backup option.

c. Ensure that the Frequency radio button is selected in the Schedule type section.

d. Ensure that the frequency is set to 1 week.

e. Ensure that the Retention is set to 2 weeks (Retention Level 1).

f. Retain the default settings for all other schedule attributes and click Add in the Add
schedule window to save the schedule.

18. In the Schedules tab, verify that the full_synthetic schedule is listed in the Backup schedules section
along with the full_traditional and the diffincr schedule.
19. On the Create policy page, click the Clients tab and then click Add to add clients to the policy.
20. In the Add client window, perform the following:
. Enter console.vrtsedu.lab in the Client name field.
a. Select the Detect client operating system checkbox.

Selecting the Detect client operating system checkbox instructs NetBackup to discover the operating
system of the client. NetBackup can detect the operating system if the NetBackup client software is
installed on the system prior to filling out the policy information.

b. Click Add.

After the client is added, you are returned to the Create policy page.

21. On the Create policy page, click the Backup selections tab and then click Add to begin adding backup
selections to the policy.
22. In the Add backup selection window, perform the following:
. Ensure that Windows is selected in the Pathname or directive set drop-down list.
a. Click inside the List of pathnames and directives to add to the selection list textbox and
type E:\data\simple.
b. Verify that E:\data\simple is listed in the List of pathnames and directives to add to the
selection list textbox and click Add to add the backup selection to the policy and return to the Create
policy page.
23. On the Create policy page, select each of the tabs -- Attributes, Schedules, Clients, and Backup
Selections -- and briefly verify the contents of each tab.
24. After verifying the contents of each tab, click Create to create the backup policy.
 After the backup policy is created, a success message is displayed in the NetBackup web user interface and
you are returned to the Policies page.

25. On the Policies page, verify that the LAB-synthetic-backup policy is listed along with other backup
policies.

Performing a traditional full backup

26. Select the checkbox next to the LAB-synthetic-backup policy and click Manual backup on the actions
menu.
27. Note that there are three schedules and one client (console.vrtsedu.lab) listed in the Manual
Backup window.
28. Click the radio button next to the full_traditional schedule, then click OK to start the backup.
29. In the NetBackup web user interface, in the navigation pane, click Activity monitor.
30. On the Activity monitor page, locate the most recent backup job that was performed using the LAB-
synthetic-backup policy.

The Job State for the job may still be Active. Wait for these jobs to complete before proceeding.

It might take a minute for this backup to complete.

31. Click the Backup job with the highest numbered Job ID
32. On the actions menu, click View details to view the details for the selected job.
33. In the Overview tab, note that the Data movement is set to Standard.
34. Click the Details tab.
35. Note the backupid created for the client during the full backup. The backupid is included in a log
message similar to the following.

Info nbjm (pid=xxxx) started backup (backupid=console.vrtsedu.lab_1625972393)

job for client console.vrtsedu.lab, policy LAB-synthetic-backup, schedule
full_traditional on storage unit media_bdisk_stu

The backupid for your lab instance may vary.

36. Also note the following log messages displayed in the Details tab.

Info bpbrm (pid=xxxx) starting bpbkar on client

Info bpbkar (pid=xxxx) Backup started
…
Info bpbkar (pid=xxxx) change time comparision:
Info bpbkar (pid=xxxx) archive bit processing:
…
Info bpbkar (pid=xxxx) not using change journal data for : not enabled
…
Info bpbkar (pid=xxxx) done. status 0: the requested operation was successfully
completed
 The above messages indicate the during a traditional full backup, the bpbkar is started on the client and it
reads and sends client data to the Media server to write to the storage.

37. Additionally, take a note of the values displayed in the Bytes transferred and the Files written fields.
38. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity monitor page.
39. Minimize (do not close) the NetBackup web user interface.

You will return to it later in this lab.

Preparing to perform an incremental backup

40. Double-click the Command Prompt shortcut located on the desktop of the console system.
41. In the Administrator: Command Prompt window, execute the following command to view contents of
the E:\data\simple directory.

Command: dir /s E:\data\simple

Note that the simple directory in the E:\data folder only contains one text file named readme.txt.

42. Execute the following command to create a new text file in the E:\data\simple directory.

Command: fsutil file createnew E:\data\simple\synthetic-incr.txt 2097152

The above command will create a file named synthetic-incr.txt of size 2 MB in the E:\data\simple directory.

43. Execute the following command to verify that the synthetic-incr.txt file has been created in
the E:\data\simple directory.

Command: dir /s E:\data\simple

44. Minimize (do not close) the Administrator: Command Prompt window.

You will return to it later in this lab.

Performing an incremental backup

45. Access the NetBackup web user interface that is open on the console system.
46. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
47. Select the checkbox next to the LAB-synthetic-backup policy and click Manual backup on the actions
menu.
48. Click the radio button next to the diffincr schedule, and then click OK to start the backup.
49. In the NetBackup web user interface, in the navigation pane, click Activity monitor.
50. On the Activity monitor page, locate the most recent backup job that was performed using the LAB-
synthetic-backup policy.

The Job State for the job may still be Active. Wait for these jobs to complete before proceeding.

It might take a minute for this backup to complete.

51. Click the Backup job with the highest numbered Job ID
52. On the actions menu, click View details to view the details for the selected job.
53. In the Overview tab, note that the Data movement for the incremental backup job is also set
to Standard.
54. Click the Details tab.
55. Note the backupid created for the client during the incremental backup. The backupid is included in a
log message similar to the following.

Info nbjm (pid=xxxx) started backup (backupid=console.vrtsedu.lab_1625974135)

job for client console.vrtsedu.lab, policy LAB-synthetic-backup, schedule
diffincr on storage unit media_bdisk_stu

The backupid for your lab instance may vary.

56. Also note that the bpbkar process was also started during the incremental backup job. Additionally, note
the values for the Bytes transferred and the File written fields.

The synthetic-incr.txt file created earlier in this lab is backed up by the incremental backup and therefore
the Bytes transferred by the incremental backup were higher than the Bytes transferred by the full backup.
The full backup does not include the synthetic-incr.txt file as it was created after the full backup was
performed.

57. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity monitor page.

Performing a Synthetic backup

58. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
59. Select the checkbox next to the LAB-synthetic-backup policy and click Manual backup on the actions
menu.
60. Click the radio button next to the full_synthetic schedule, and then click OK to start the backup.
61. In the NetBackup web user interface, in the navigation pane, click Activity monitor.
62. On the Activity monitor page, locate the most recent backup job that was performed using the LAB-
synthetic-backup policy.

The Job State for the job may still be Active. Wait for these jobs to complete before proceeding.
 It should only take a couple of seconds for this backup to complete.

63. Click the Backup job with the highest numbered Job ID
64. On the actions menu, click View details to view the details for the selected job.
65. In the Overview tab, note that the Data movement for the synthetic backup is set to Synthetic.

A synthetic job is distinguished from traditional backups by the notation that is indicated in the Data
Movement field of the Activity monitor. Synthetic jobs display Synthetic as the Data Movement type while
traditional backups display Standard.

66. Click the Details tab.

67. Note the following log messages displayed in the Details tab.

…
begin synthetic writer to console.vrtsedu.lab_1625974136
Info nbjm (pid=xxxx) starting backup job (jobid=xx) for client
console.vrtsedu.lab, policy LAB-synthetic-backup, schedule full_synthetic
Info nbjm (pid=xxxx) requesting NO_STORAGE_UNIT resources from RB for backup job
…
…
granted resource MediaID=@aaaak;Path=/bdisk;MediaServer=lnxmedia.vrtsedu.lab
granted resource media_bdisk_stu
begin synthetic reader 1 for 1 extents from console.vrtsedu.lab_1625974135 on
/bdisk
end Synthetic: Execute Script; elapsed time 0:00:01
…
begin synthetic reader 2 for 1 extents from console.vrtsedu.lab_1625972393 on
/bdisk
…

As displayed in the above log message, the synthetic backup combined images created by the full and the
incremental backup (backupid console.vrtsedu.lab_1625972393 and backup
id console.vrtsedu.lab_1625974135) into a new independent backup image (backup
id console.vrtsedu.lab_1625974136). For performing a point in time restore, the synthetic full backup image
can be used instead of restoring the full and incremental backup images as the synthetic backup image
includes files from both the full and incremental backups.

The backupid's for your lab instance may vary.

Also note that the bpbkar process was not started during the synthetic backup. The log message indicating
the start of the bpbkar process is absent in the log messages for the synthetic backup.

Traditional backups are created by scanning the data on the client system, and then copying the data from
the client system to the backup Media server. This is done with the help of the bpbkar process on the client.

Synthetic backups do not interact with the client system at all, but are instead synthesized on the Media
server and therefore the "starting bpbkar on client" log message is absent from the log messages for a
synthetic backup.
 Because the backup processing takes place on the Media servers instead of the clients, synthetic backups help
to reduce the network traffic.

In addtion, restores using a synthetic full backup are faster as compared to restores from traditional backups
because the number of images to be restored are less as compared to traditional backups.

68. Note the values for the Bytes transferred and the Files written fields and compare the values with
the Bytes transferred and Files written fields noted for the traditional full and incremental backup.
69. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity monitor page.
70. Remain logged in to the NetBackup web user interface.

You will return to it later in this lab.

Exercise B: Optimizing Backups using the NetBackup Accelerator

In this exercise, you configure the NetBackup Accelerator feature, and perform client backups with and without the
Accelerator feature to observe the impact of this feature on backup performance.

Configuring a policy for NetBackup Accelerator

1. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
2. On the Policies page, select the checkbox next to the LAB-console-to-media-msdp policy.

The LAB-console-to-media-msdp policy was created in the Configuring Media Server Deduplication lab.
The policy includes a single full backup schedule for client, console.vrtsedu.lab and it using
the media_msdp_stu MSDP storage unit.

3. On the actions menu, click the Copy policy option.

4. In the Copy policy window, enter LAB-accelerator in the New policy field and click Copy.

A new policy LAB-accelerator is created and contains the same settings as the original policy.

5. On the Policies page, select the checkbox next to the LAB-accelerator policy.

If the LAB-console-to-media-msdp policy is still selected, deselect it before selecting the LAB-
accelerator policy.

6. After selecting the policy, click Activate on the actions menu to activate this policy.
Performing a non-Accelerator backup of the client

7. On the Policies page, select the checkbox next to the LAB-accelerator policy and click Manual
backup on the actions menu.
8. Click OK in the Manual backup window to start the backup.

Because the LAB-accelerator policy contains only one schedule and one client entry it is unnecessary to
make schedule or client selections in the Manual Backup window.

9. After initiating the backup job, select the Activity monitor entry in the left pane of the NetBackup web
user interface.
10. On the Activity monitor page, locate the most recent backup job that was performed using the LAB-
accelerator policy.

The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 2-4 minutes for this backup to complete.

11. After the job completes, click the Backup job with the highest numbered Job ID.
12. On the actions menu, click View details to view the details for the selected job.
13. Click the Details tab and view the contents of the Details tab, taking note of the information shown in the
following table:

Bytes transferred 807.84 MB

Files written 11135

14. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity monitor page.

Enabling NetBackup Accelerator in a policy

15. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
16. On the Policies page, select the checkbox next to the LAB-accelerator policy.
17. After selecting the policy, click Edit on the actions menu to open the policy for editing.
18. On the Edit policy page, in the Attributes tab, perform the following:

a. Select the Use Accelerator checkbox to enable accelerator for this policy.

b. Enter ACCELERATOR in the Keyword phrase (optional) field.

19. Click Save without making any other changes to update the policy and return to the Policies page.

Performing and monitoring Accelerator-enabled backups

20. On the Policies page, select the checkbox next to the LAB-accelerator policy and click Manual
backup on the actions menu.
21. Click OK in the Manual backup window to start the backup.
22. After initiating the backup job, select the Activity monitor entry in the left pane of the NetBackup web
user interface.
23. On the Activity monitor page, locate the most recent backup job that was performed using the LAB-
accelerator policy.

The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 2-4 minutes for this backup to complete.

24. After the job completes, click the Backup job with the highest numbered Job ID.
25. On the actions menu, click View details to view the details for the selected job.
26. Click the Details tab and locate the log messages that contain:

Info bpbrm (pid=xxxx) accelerator enabled

Info bpbrm (pid=xxxx) There is no complete backup image match with track
journal, a regular full backup will be performed

Since this is the first Accelerator-enabled backup of the client, there is no track log which NetBackup can use
to discover changes in the files. The track log is created by NetBackup during this backup and will be used for
future backups.
The first Accelerator-enabled backup of a client may take longer to run to completion than a non-Accelerator
backup. This is due to the processing overhead required to generate the track log for the client.

27. In the Details tab, locate the following log message:

Info bpbkar (pid=xxxx) accelerator sent xxxxxxxxx bytes out of xxxxxxxxx bytes
to server, optimization 0.0 %

The first Accelerator-enabled backup of the client using the policy will achieve an accelerator optimization of
zero percent. This is expected.

28. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity monitor page.

Performing a second Accelerator-enabled backup

29. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
30. On the Policies page, select the checkbox next to the LAB-accelerator policy and click Manual
backup on the actions menu.
31. Click OK in the Manual backup window to start the backup.
32. After initiating the backup job, select the Activity monitor entry in the left pane of the NetBackup web
user interface.
33. On the Activity monitor page, locate the most recent backup job that was performed using the LAB-
accelerator policy.

The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 2-4 minutes for this backup to complete.

34. After the job completes, click the Backup job with the highest numbered Job ID.
35. On the actions menu, click View details to view the details for the selected job.
36. Click the Details tab and locate the following log message:

Info bpbkar (pid=xxxx) accelerator sent xxxxxxxxx bytes out of xxxxxxxxx bytes
to server, optimization 100.0 %

The second Accelerator-enabled backup of the client using the policy will achieve an accelerator optimization
of 100 percent. This is expected.

37. Take note of the number of bytes sent by the accelerator, as displayed in the above log message.
38. Compare the Bytes transferred and the number of bytes sent by the accelerator from the client to the
NetBackup Media server.

The value of the Bytes transferred field far exceeds the number of bytes sent (as indicated in the log
message displayed in the Details tab) for the job. This indicates that the backup image that was written to the
storage unit was created using the contents of previous backup images of the client plus only the changed
files that were transferred by the accelerator from the client system to the Media server.

In the file system on the client, no changes were made to the files between the two accelerator-enabled
backup jobs. This is because limited data had to be sent to the storage unit on the Media server which
resulted in a faster backup. However, the resulting full backup image recorded to the Media server storage
unit still includes all the files in the client file system. If files on the client were changed, the amount of data
transferred would have been greater. This transferred data would still be less than the data transferred during
a full, non-accelerator backup operation.

39. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity monitor page.

Viewing the Accelerator-enabled backup image contents

40. In the NetBackup user interface, in the navigation pane, click Recovery.
41. On the Recover page, click Start.
42. On the Recover > Basic properties page, perform the following:

a. Select console.vrtsedu.lab in the Source client drop-down list.

b. Ensure that console.vrtsedu.lab is displayed in the Destination client field.

c. Ensure that MS-Windows is selected in the Policy type drop-down list.

d. After selecting and verifying the source and destination client, the policy type, click Next to proceed.

43. On the Recover > Add files page, perform the following:
a. Set the Start date to today's date and the start time to 12:00:00 AM.
b. Set the End date to today's date and the end time to 11:59:00 PM.
c. After setting the start and end dates and time, click Backup history.
d. In the Backup History window, select the entry for the most recently created backup image that was
created using the LAB-accelerator policy, as shown in the following figure:

e. Note of the Size (KB) of the selected backup image, as indicated in the Backup History window.

This Size (KB) is far greater than the number of bytes that were transferred from the client to the Media
server during the most recent Accelerator-enabled backup job.

f. After selecting the most recently created backup image using the LAB-accelerator policy,
click Select in the Backup History window.
g. Click Add files.
h. In the Add files and folders window, perform the following:
i. Expand the console.vrtsedu.lab node and then expand the E node.
ii. Click the data folder in the left pane.
 The contents of the data folder that are present in the selected backup image are displayed in the
right pane of the Add files and folders window.

iii. Note that the contents of the data directory pane includes all the files and directories that were
present in the client's file system at the time of the most recent Accelerator-enabled backup job.
iv. Click Cancel in the Add files and folders window.
i. Click Cancel on the Recover > Add files page.

Using the Accelerator forced rescan option

44. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
45. On the Policies page, select the checkbox next to the LAB-accelerator policy.
46. After selecting the policy, click Edit on the actions menu to open the policy for editing.
47. On the Edit policy page, click the Schedules tab.
48. In the Schedules tab, click Add in the Backup schedules section to add a new backup schedule.
49. In the Add schedule window, perform the following:
a. Enter full_rescan in the Name field.
b. Ensure that Full Backup is selected in the Type of backup drop-down list.
c. Select the Accelerator forced rescan option located below the Type of backup drop-down list.

This option creates a checksum of the content of each file during backup. It uses the checksums for
change detection. It provides a safety net by establishing a new baseline for the next accelerator backup.

The Accelerator forced rescan option detects the following events:

 The file's data changes but the file's metadata does not change.
 The file's metadata becomes corrupted such that it does not indicate that the file has changed.
 A malicious user or application changes the file's metadata such that it does not indicate that the
file has changed.
If Accelerator forced rescan is enabled, NetBackup uses the Windows change journal to help determine if
a file has changed. NetBackup also examines the file system metadata for each file to help detect which
files have changed.
For the most efficient use of accelerator, accelerator policies must include at least two full-backup
schedules: one full schedule with the Accelerator forced rescan option disabled, and another full
schedule with Accelerator forced rescan enabled.

d. Ensure that the Frequency radio button is selected in the Schedule type section.
e. Set the frequency for this schedule to 1 month.
f. Select 1 week (Retention Level 0) in the Retention drop-down list.
g. Retain the default settings for all other schedule attributes and click Save to save this schedule.
50. In the Schedules tab, in the Backup schedules section, verify that an entry for the full_rescan schedule is
visible along with the full_frequency schedule.
51. On the Edit Policy page, click Save to update the backup policy.
52. On the Policies page, select the checkbox next to the LAB-accelerator policy and click Manual
backup on the actions menu.
53. In the Manual backup window, select the full_rescan radio button and then click OK to start the backup.
54. After initiating the backup job, select the Activity monitor entry in the left pane of the NetBackup web
user interface.
55. On the Activity monitor page, locate the most recent backup job that was performed using the LAB-
accelerator policy.

The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 2-4 minutes for this backup to complete.

56. After the job completes, click the Backup job with the highest numbered Job ID.
57. On the actions menu, click View details to view the details for the selected job.
58. Click the Details tab and locate the following log messages:

Info bpbrm (pid=xxxx) Accelerator enabled backup with "Accelerator forced

rescan", all data will be scanned and processed. Backup time will be longer than
a normal Accelerator enabled backup
Info bpbkar (pid=xxxx) accelerator sent xxxxxxxxx bytes out of xxxxxxxxx bytes
to server, optimization 95.3 %

The backup speed on the client is less when the rescan option is selected as compared with the selection of
only the Use Accelerator option. This is due to the checksum processing on the client. The speed reduction
depends on the client's configuration and its current processing load. If the client is busy with multiple jobs
when the accelerator backup begins, checksum processing reduces backup speed.

For an MS-Windows or Standard policy (to back up files and folders), all the data on the client is read.
However, NetBackup sends only the changed data over the network to be included in the backup image.
Sending only the changed data is similar to a regular accelerator full backup. Thus, for an Accelerator forced
rescan backup, the optimization percentage is similar to a regular accelerator full backup. Note that the
duration of the backup falls somewhere between a non-accelerator full backup and a regular accelerator full
backup.

59. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity monitor page.
60. Remain logged in to the NetBackup web user interface.

You will return to it later in this lab.

Exercise C: Optimizing Backups using NetBackup FlashBackup

In this exercise, you configure, perform and monitor backups using a NetBackup FlashBackup policy.

Configuring a policy for NetBackup FlashBackup

1. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
2. On the Policies page, select the checkbox next to the LAB-console-to-media-msdp policy.

The LAB-console-to-media-msdp policy was created in the Configuring Media Server Deduplication lab.
The policy includes a single full backup schedule for client, console.vrtsedu.lab and it using
the media_msdp_stu MSDP storage unit.

3. On the actions menu, click the Copy policy option.

4. In the Copy policy window, enter LAB-flashbackup in the New policy field and click Copy.

A new policy LAB-flashbackup is created and contains the same settings as the original policy.

5. On the Policies page, select the checkbox next to the LAB-flashbackup policy.

If the LAB-console-to-media-msdp policy is still selected, deselect it before selecting the LAB-
flashbackup policy.

6. After selecting the policy, click Activate on the actions menu to activate this policy.
7. Sign out of the NetBackup web user interface and close the browser window.
8. Double-click the NetBackup 10.0 Administration Console shortcut located on the desktop of
the console system.
9. In the NetBackup Administration Console window, perform the following:

a. Ensure that lnxmaster.vrtsedu.lab is displayed in the Host name field.

b. In the Login using section, ensure that the User name and password radio button is selected.

c. Enter root in the User name field and P@ssw0rd in the Password field.

d. Click Login.

10. In the NetBackup Administration Console, navigate to NetBackup Management > Policies.
11. Double-click the LAB-flashbackup policy in the All Policies pane to open the policy for editing.
12. In the Change Policy window, perform the following:

a. Select Flashbackup-Windows in the Policy type drop-down list.

b. Ensure that media_msdp_stu is selected in the Policy storage drop-down list.

 c. Ensure that the Perform snapshot backups checkbox is selected and then click Options.

d. In the Snapshot Options window, ensure that auto is selected in the Snapshot method for this
policy drop-down list and click OK.

13. Click the Schedules tab and verify that a Full Backup schedule (full_frequency) is present.

FlashBackup policies support full and incremental types only.

14. Click the Clients tab and verify that the client, console.vrtsedu.lab is added to the policy.
15. Click the Backup Selections tab and perform the following:

a. Click E:\data displayed in the Backup Selection List and then click Delete.

b. After clicking Delete, the Backup Policy Management dialog box is displayed. Click Yes to proceed.

c. Click New to create a new backup selection.

d. In the Pathname or directive field, type \\.\E: and then click OK.

e. Verify that \\.\E: is listed in the Backup Selection List.

For a FlashBackup policy, the backup selections must be mounted volume (Windows) or a raw device path
(UNIX). Typical backup selections used with MS-Windows or Standard policies are not supported with
a FlashBackup policy.
A full FlashBackup backs up the entire disk or raw partition that is added in the Backup Selections tab. An
incremental backup backs up individual files that have changed since their last full backup, and also backs up
their parent directories. The incremental backup does not back up files in parent directories unless the files
have changed since the last full backup.

16. In the Change policy window, select each of the tabs -- Attributes, Schedules, Clients, and Backup
Selections -- and briefly verify the contents of each tab.
17. After verifying the contents of each tab, click OK to update the backup policy.

Performing and monitoring a backup using the FlashBackup policy

18. In the All Policies pane, right-click the LAB-flashbackup policy and then click Manual Backup.
19. In the Manual Backup window, click OK to start the backup.
20. In the NetBackup Administration Console, in the object tree, click Activity Monitor.
21. In the Activity Monitor, locate the job(s) that were started as a result of the manual backup operation
that was performed using the LAB-flashbackup policy.

How many jobs were started as a result of the manual backup that was performed using the LAB-
flashbackup policy?

Two jobs were started: one Snapshot and one Backup job.
 The Snapshot job which ran ahead of the Backup job created a snapshot of the E:\ volume (added in the
backup selection). The Snapshot method used for creating the snapshot was automatically determined by
NetBackup.

The Backup job which ran after the Snapshot job, backed up the snapshot that was created by
the Snapshot job.

After the snapshot is backed up, it is deleted.

22. Double-click the the Backup job with the highest numbered Job Id to view its details.
23. In the Job Details window, view the contents of the Job Overview tab.

What Data Movement mode was used by the FlashBackup job?

The Data Movement used by the FlashBackup job is Instant Recovery Disk.

How long did the FlashBackup job take to complete?

The FlashBackup job took just over a minute to complete.

FlashBackup increases backup performance as compared to standard file-ordered backup methods and it the
recommended method for a system that contains a large number of files and most of the file system blocks
are allocated. It is a policy type that combines the speed of raw-partition backups with the ability to restore
individual files.

24. In the Job Details window, click the Detailed Status tab and briefly view the information that is
displayed.

Are there any specific log messages in the Detailed Status tab which identifies this backup as a
FlashBackup?

No, the log messages that appear in the Detailed Status tab are similar to the messages that appear for MS-
Windows or Standard policy types.

25. Close the Job Details window.

26. Remain logged in to the NetBackup Administration Console.

You will return to it later in this lab.

Exercise D: Configuring and using Multiple Data Streams

In this exercise, you configure a NetBackup policy to enable the Allow multiple data streams feature and then
modify the Backup selections list prior to a backup in order to investigate the impact these two settings have on
the way backups are performed.
Configuring a policy to use multiple data streams

1. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
2. On the Policies page, select the checkbox next to the LAB-console-to-media-msdp policy.
3. On the actions menu, click the Copy policy option.
4. In the Copy policy window, enter LAB-multiple-data-streams in the New policy field and click Copy.

A new policy LAB-multiple-data-streams is created and contains the same settings as the original policy.

5. On the Policies page, select the checkbox next to the LAB-multiple-data-streams policy.
6. After selecting the policy, click Activate on the actions menu to activate this policy.
7. Select the LAB-multiple-data-streams again and click Edit.
8. On the Edit policy - LAB-multiple-data-streams page, in the Attributes tab, select the Allow multiple
data streams checkbox and click Backup Selections.
9. On the Backup Selections page, perform the following:
a. Select E:\data displayed in the Backup Selection List and then click Delete.
b. In the Delete Backup Selection List, click Yes to proceed.
c. Click Add to create a new backup selection.
d. In the Add Backup Selection window, in the List of pathnames and directives to add to the
selection list , add the following selections:

E:\data\smallfiles

C:\data2\smallfiles

F:\data3\smallfiles

e. Click Add and then click Save to save the changes.

Performing and monitoring a multiple data streams backup

10. On the Policies page, select the checkbox next to the LAB-multiple-data-streams policy and
click Manual backup on the actions menu.
11. Click OK in the Manual backup window to start the backup.
12. Immediately after initiating the manual backup, select the Activity Monitor entry in the left pane of the
NetBackup WebUI interface.
13. Pay close attention to the Job State column contents for the new backup jobs in the Activity Monitor.
14. Take note of the following information regarding how and when each of the backup jobs become Active.

Four jobs were initiated. A parent job, and three child jobs.
 The first job (lowest numbered job) and the second job become Active immediately. These are the parent job
and the first child job.

The State for the jobs that are in the Queued state says "Limit has been reached for requested resource…"

When the second job (the first child job) reaches the Done state, the third job (second child job) goes Active.

When the third job (the second child job) reaches the Done state, the fourth job (third child job) goes Active.

15. Allow all the backup jobs to run to successful completion.

In previous steps, you observed that only one child backup job is Active at a time - the child jobs are the jobs
that perform the actual backup of client data.

Factors that impact job concurrency: Maximum jobs per client

16. In the NetBackup web user interface, select Hosts>Host properies.

17. Select the checkbox next to lnxmaster.vrtsedu.lab and click Connect.
18. Once connected, select Edit primary server.

The properties of the Primary Server are displayed.

19. Click the Global attributes entry in the left pane of the Properties window.

The Global Attributes for the selected Master/Primary server are displayed in the right pane of the Master
Server Properties window.

Note the current value (1) of the Maximum jobs per client setting.

20. Change the value of the Maximum jobs per client setting to 3.
21. Click Save to save the settings.
22. Successfully updated the host properties message is displayed.

Testing the Maximum jobs per client setting

23. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
24. Select the LAB-multiple-data-streams policy and then click Manual Backup.
25. After initiating the backup job, select the Activity monitor entry in the left pane of the NetBackup web
user interface.

Give close attention to the Job State column contents for the new backup jobs in the Activity Monitor.
 After changing the Maximum jobs per client setting to a value of 3, when a backup is performed using the
policy that allows multiple data streams from the client, four backup jobs are still initiated -- a parent job, and
three child jobs.

However, now two of the child jobs are Active at the same time, while the third child job is Queued. The
Maximum jobs per client setting was set to a value of 3? Why was the third child job Queued, instead of
Active? Continue with the lab steps to investigate further.

26. Allow all the backup jobs to run to successful completion.

Factors that impact job concurrency: Storage unit configuration

27. In the NetBackup web user interface, in the navigation pane, click Storage>Storage configuration.
28. Under the Storage Configuration, select Storage units
29. Click the media_msdp_stu storage unit to view its properties.
30. Under the Basic Properties, Note the value for the Maximum concurrent jobs settings.

Based on the Maximum concurrent jobs settings, the the maximum number of concurrently Active backup
jobs for the storage unit is two (2).

31. Click Edit and Change the value for the Maximum concurrent jobs settings to 3 and click Save to save
the settings.

Testing the Maximum concurrent jobs setting

32. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
33. Select the LAB-multiple-data-streams policy and then click Manual Backup.
34. After initiating the backup job, select the Activity monitor entry in the left pane of the NetBackup web
user interface.

Give close attention to the Job State column contents for the new backup jobs in the Activity Monitor.

After changing the Maximum concurrent jobs setting to a value of 3, when a backup is performed using the
policy that allows multiple data streams from the client, four backup jobs are still initiated -- a parent job, and
three child jobs.

However, still only two of the child jobs are Active at the same time, while the third child job is Queued.
The Maximum jobs per client and the Maximum concurrent jobs setting for the storage unit was set to a
value of 3? Why was the third child job Queued, instead of Active? Continue with the lab steps to investigate
further.

35. Allow all the backup jobs to run to successful completion.

Factors that impact job concurrency: Disk pool configuration

36. In the NetBackup web user interface, in the navigation pane, click Storage>Storage configuration.
37. Under the Storage Configuration, click Disk pools
38. Click the media_msdp_dpool disk pool to view its properties.
39. Note that the Limit I/O streams is enabled and the value for the same is set to 2 per volume.

If using a storage unit that is associated with a disk pool, the value for the Maximum I/O streams should be
taken into consideration when calculating the total number of potential concurrent streams written to or read
from a given storage pool from all operations such as backups, duplications, replications, and so on.

40. Click Edit and change the value for the Limit I/O streams setting to 3 and click Save save the settings.

Testing the Limit I/O streams setting

41. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
42. Select the LAB-multiple-data-streams policy and then click Manual Backup.
43. After initiating the backup job, select the Activity monitor entry in the left pane of the NetBackup web
user interface.

Give close attention to the Job State column contents for the new backup jobs in the Activity Monitor.

Note that after changing the Limit I/O streams setting to a value of 3, all child jobs are Active at the same
time.

44. Allow all the backup jobs to run to successful completion.

Modifying policy Backup Selections to affect backup streams

45. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
46. Select the LAB-multiple-data-streams policy and then click Edit.
47. In the Edit Policy-LAB-multiple-data-streams page, select Backup Selections.
48. Select E:\data\smallfiles displayed in the Backup Selection List and then click Insert.
49. In the Insert Backup Selection window, select NEW_STREAM in the Pathname or directive drop-down
list. Click the + sign and then click Insert.
50. Select C:\data2\smallfiles displayed in the Backup Selection List and then click Insert.
51. In the Insert Backup Selection window, select NEW_STREAM in the Pathname or directive drop-down
list. Click the + sign and then click Insert.
52. After performing the above steps, the two NEW_STREAM directives will be inserted before and after the
E:\data\smallfiles backup selection.
 One parent and two child backup jobs will be generated. The first child job will back up the entry between the
first NEW_STREAM and second NEW_STREAM entry in the Backup Selections tab. The second child job will
back up the entries that exists after the second NEW_STREAM entry in the Backup Selections tab.

53. After making the changes in the Backup Selections tab, click Save to save the policy and close the Edit
Policy window.

Testing the NEW_STREAM directive

54. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
55. Select the LAB-multiple-data-streams policy and then click Manual Backup.
56. Immediately after initiating the manual backup, select the Activity Monitor entry in the left pane.
57. In the Activity Monitor, note the following:
o Three backup jobs were initiated as a result of the manual backup request, a parent job, and two child
jobs.
o All the backup jobs run concurrently, because we have previously set the Maximum jobs per
client, Maximum concurrent jobs, and the Limit I/O streams settings to a higher value (3).
o The first child job's Files List shows E:\data\simplefiles.
o The second child job's Files List shows C:\data2\simplefiles and F:\data3\simplefiles.
58. Close the NetBackup web user interface and sign out of the console system.

Pre-configuration Lab Task

As a preconfiguration lab task, you are required to install vCenter Server Appliance (VCSA) 7.0.

1. Sign in to the console system using the following credentials.

o User name: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Locate and double-click the shortcut for File Explorer.

3. Double-click DVD Drive (D:) VMware VCSA.
4. Navigate to vcsa-ui-installer>>win32.
5. Double-click installer.exe file.
6. In the vCenter Server 7.0 Installer screen,click Install to install a new vCenter Server.
7. In the Introduction, click NEXT.
8. Check I accept the terms of the license agreement > Next.
9. In the vCenter Server deployment target , provide following information:

ESXi host or vCenter Server name : esx1.vrtsedu.lab

HTTPS port: 443

User name: root

Password: P@ssw0rd

10. Click NEXT to continue.

11. The Certificate Warning is displayed. Click Yes to continue.
12. In the Set up vCenter Server VM, provide following information:

VM name: Accept the default name.

Set root password: P@ssw0rd

Confirm root password: P@ssw0rd

13. Click NEXT to continue.

14. Accept the default values in the Select deployment size screen and click NEXT.
15. In the Select datastore screen, check the option Enable Thin Disk Mode. Do not make any other
changes and click NEXT.
16. In the Configure Network Settings screen, enter the following information:

Network – Default

IP version – IPv4

IP assignment – static

FQDN – Leave Blank

IP address – 10.10.2.99

Subnet mask or prefix length – 255.255.255.0

 Default gateway – 10.10.2.1

DNS servers – 10.10.2.6

Common Ports- Accept the default values.

17. Click NEXT.

18. In the Ready to Complete stage1 screen, click FINISH.

Stage 1: Deploy vCenter Server process takes around 20-30 minutes most of the time. Do not click CANCEL.

19. Click CONTINUE when the following message appears.

20. Stage2: Set Up vCenter Server begins. Click NEXT to continue.
21. In the Time synchronization mode, select Synchronize time with the ESXi host and click NEXT.
22. In the SSO Configuration screen, select Create a new SSO domain and provide following information:

Single sign-On domain name : vsphere.local

Single sign-On user name: administrator

Single sign-On password: P@ssw0rd

Confirm password: P@ssw0rd

23. Click NEXT.

24. In the Configure CEIP screen, uncheck the Join the VMware’s Customer Experience Improvement
Program (CEIP) and then click NEXT.
25. Click FINISH in the Ready to complete screen.
26. Read the Warning and click OK.
27. Install- Stage 2 begins.

This stage may take around 20-30 minutes.

28. When the Install-Stage2: Complete message is displayed, click the URL that is displyed to access the
vCenter Server.
29. In the warning page that is displayed, click Advanced>Accept the risk and Continue.
30. Click LAUNCH VSPHERE CLIENT (HTML 5).
31. Provide the following credentials and click LOGIN.

administrator@vsphere.local

P@ssw0rd
32. In the vSPhere Client, in the left pane, right-click the 10.2.2.99 and select New Datacenter.
33. Provide the name of the DataCenter as DC1 and click OK.
34. In the left pane, expand 10.10.2.99. Right-click DC1 and select Add Host.
35. Enter the following information in the Add Host page:
a. In the Add Host>Name and location screen, provide following information and click NEXT.
i. Host name or IP address: esx1.vrtsedu.lab
ii. Location: DC1
b. In the Connection settings, enter following details and click NEXT.

i. User name: root

ii. Password: P@ssw0rd

iii. Accept the Security Alert by clicking YES.

c. Click NEXT in the Host Summary.

d. In the Assign License window, select the Evaluation License and click NEXT.
e. In the Lockdown Mode screen, ensure that Disabled option is selected.
f. Do not make any changes in the VM location screen and click NEXT.
g. Click FINISH in the Ready to complete screen.
h. Ensure that the Add Standalone host task completes scucessfully.
i. Minimize the vSphere Client console.

Lab Part A: Protecting VMware Environments

Exercise A: Configuring NetBackup to Perform VMware Backups

In this exercise, you configure NetBackup to enable NetBackup systems to access the VMware vCenter server.
Configuring this access allows NetBackup to perform backup and restore operations in the VMware environment.
You also set resource limits to prevent backup operations from overtaxing a VMware environment.

Configuring credentials to enable access to VMware

In the steps that follow, you configure credentials that enable NetBackup systems to access VMware systems.
These steps are necessary to enable NetBackup to perform backup and restore operations in VMware.
1. Sign in to the console system using the following credentials. (If required.)
o User name: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system to
launch the NetBackup web user interface.
3. If a security warning is displayed, click Advanced > Accept the Risk and Continue.
4. Sign in to the NetBackup web user interface using the following credentials.
o Username: root
o Password: P@ssw0rd

5. In the NetBackup web user interface, in the navigation pane, go to Workloads > VMware then click
the VMware servers tab.

The tab shows the vCenters and ESXi servers that you can access.

6. Click Add to add a server.

No VMware virtual machine servers are currently configured in NetBackup.

7. In the Add VMware server window use the information provided in the table below to populate the
fields.

Parameter Parameter setting / value

Server type vCenter

Host 10.10.2.99

Port 443

Username administrator@vsphere.local

Password P@ssw0rd

Backup host for validation lnxmedia.vrtsedu.lab

8. After completing the entries in the Add VMware server window, click Save to save the changes.
 The discovery of VMs and other objects in the vCenter or ESXi server begins when server credentials are
added or updated through the web UI or an API. However, the server's VMs and other objects might not
appear in the UI immediately. They appear after the discovery process for the VMware server completes.
Discovery also occurs at set intervals. (The default interval is every 8 hours.)

9. After the vCenter is added successfully, you will see the list under the VMware servers list.
10. To validate the credentials, locate and select the VMware server and in the row with that server,
click Validate.
11. Once credentials are validated, you will see the Credentials column value as Valid.

Setting resource limits for VMware backups

In the steps that follow, you configure resource limits to limit the number of simultaneous backup jobs that can
run against a VMware resource. Proper use of these limits will prevent your VMware environment from being
overstressed by a backup activity.

12. In the NetBackup web user interface, on the top right corner, select VMware settings > Resource limits.

For each resource, the default value is 0 (No limit).

13. In the VMware Resource limits page, locate ESXserver in the VMware resource Type column.
14. Click Edit to change the value.
15. In the Edit ESXi server limit window, change the Limits column value to 4.
16. Click Save to save the change.
17. Close the VMware resource limits window.

Exercise B: Configuring a VMware Policy

In this exercise, you configure a VMware policy in NetBackup to enable automatic discovery of VMware virtual
machines to be backed up, and to perform backups of the discovered virtual machines.

Creating a VMware policy

In the steps that follow, you begin the creation of a new policy that will be used to back up VMware virtual
machines.

1. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.

The policies that are currently configured are listed in the Policies pane of the NetBackup web user interface.
 2. To create a new policy, click Add.

The Create policy page is displayed.

Configuring the policy Attributes

In the steps that follow, you configure the Policy name, Policy type, and Policy Storage in the Attributes tab of the
policy.

3. Type the name of the new policy, VMware_policy, in the Policy name field of the Create policy page.
4. In the policy Attributes tab, select the drop-down arrow for the Policy type field and select VMware.

You may have to use the scroll bar in the Policy type drop-down menu to locate the VMware policy type
selection.

5. Use the information below to make the following additional changes to the policy's Attributes tab
parameter settings.

Attribute Parameter Parameter setting / value

Policy storage media_msdp_stu

All other policy Attributes leave at default settings

6. Take notice that two new tabs are added to the policy as a result of changing the Policy type to VMware.

When the Policy type attribute is set to VMware, and the policy Attributes are saved (applied),
the VMware tab and Exclude disks tab are added to the Create policy page.

Configuring the policy Schedule

In the steps that follow, you configure a full schedule for the VMware_policy policy.

7. Click the Schedules tab in the Create policy page.

8. In the Schedules tab, under Backup schedules click Add.

The Add schedule window is displayed.

9. Create a new schedule using the parameters provided in the table below.
 Schedule Attributes tab Value / setting

Name Full

Type of backup Full Backup

All other schedule Attributes Use default settings

Start window tab Use all defaults (no start window)

Exclude dates tab Use all defaults (no exclusions)

Retention 6 Months

10. In the Add Schedule window, click Add to add the Full schedule.
11. After the schedule is created successfully, you can see the Full schedule under Backup schedules.

Configuring the policy VMware tab selections

In the steps that follow, you view the parameters that are available for selection in the VMware tab of VMware-
type policy and modify one parameter setting to enable successful virtual machine discovery in this lab
environment.

12. Click the VMware tab in the Create policy window.

13. Briefly view the parameters that are available for selection in the VMware tab. Take note of the selections
available for the VMware backup host parameter.

Do not change this setting from the default setting (Backup media server).
By default, NetBackup uses one of the Backup Media Servers (that are associated with the target storage unit
for the policy) as the "backup host". If one of the Media Servers IS NOT supported as a backup host (for
example, Solaris, HP-UX, AIX), then it is necessary to configure another system, that is running a supported OS
and that has the NetBackup client software installed to serve as the VMware backup host (VMware access
host).

14. Click the drop-down arrow for the Primary VM identifier field on the VMware tab and change the value
from VM hostname to VM display name.

The default selection in the Primary VM identifier field is VM hostname.

15. Verify that the Primary VM identifier field is set to the value of VM display name before continuing.

Successful identification and selection of virtual machines for backup, when the VM hostname is the Primary
VM identifier, relies upon the ability of NetBackup to perform successful reverse name lookups from a
Domain Name Server (DNS). Because of the dynamic nature of many virtual machine environments, it may be
necessary to change the Primary VM identifier to use another setting, such as the VM display name. Use of
the VM display name as the Primary VM identifier does not require reverse name lookups in DNS in order
to identify VMware virtual machines for backup.
If the VM hostname was used as the Primary VM identifier in this lab environment, virtual machines would
have to be powered on in order to be discovered by the NetBackup VM discovery process.

16. Leave all other settings at their default values.

17. Expand the VMware advanced attributes, located at the bottom of the VMware tab.
18. Briefly view the parameters that can be set in the VMware advanced attributes section.

Manually selecting virtual machines for backup

In the steps that follow, you view and manually select VMware virtual machines for backup.

19. Click the Clients tab in the Create policy window.

20. Click the Select manually radio button, located in the Virtual machines for backup section.

When you choose the Select manually radio button, a Virtual machines for backup dialog box is displayed.
This dialog box enables you to confirm that you are changing the policy from the use of VipQuery to manual
virtual machine selection.

21. Click Continue in the Virtual machines for backup dialog box, to confirm the selection.
22. Click Add, located under the Clients section of the Clients tab.

The Browse for virtual machines window is displayed.

23. Click the Browse virtual machines radio button in the Browse for virtual machines window.

Within a few moments, the left pane of the Browse virtual machines window is updated to display
a VMware servers entry, with an entry for the vCenter Server, 10.10.2.99, displayed beneath it.

The VMware servers entry has an entry for the vCenter Server, 10.10.2.99, beneath it. NetBackup has
obtained the structure of the VMware environment by querying the vCenter Server.

24. Expand the entry for the vCenter Server, 10.10.2.99. Then expand the entry for the DC1 Data Center,
using the symbols located to the left of the names of these VMware entities.

When the DC1 entry is expanded, an entry for the ESX server, esx1.vrtsedu.lab is displayed.
25. Click the entry for esx1.vrtsedu.lab, located in the left pane of the Browse virtual machines window.

The right pane of the Browse virtual machines window displays entries for the virtual machines that are
hosted by the ESX server, esx1.vrtsedu.lab. The checkboxes present on the left side of the VM hostname
enable you to manually select the virtual machines that you want to back up using this policy.

26. View the virtual machines that are available for backups on the esx1.vrtsedu.lab server. Do not mark the
check box for any virtual machine.

In general, due to the dynamic nature of VMware virtual machine environments, it is advised to configure the
VMware policy to automatically detect and select VMware virtual machines to back up.

27. Click the Cancel button in the Browse for virtual machines window, to cancel the manual selection of
virtual machines to back up.

You are not going to select the virtual clients to back up using the manual method.

Creating a query to select virtual machines to backup

In the steps that follow, you configure the VMware_policy to use an automated query to identify and select virtual
machines to back up. This capability uses a NetBackup feature called VMware Intelligent Policy or VIP.

28. Select the radio button for Select automatically through VMware Intelligent policy query, located in
the Virtual machines for backup section under the Clients tab.

When you choose the Select automatically through VMware Intelligent policy query radio button,
a Virtual machines for backup dialog box is displayed, to allow you to confirm that you are changing the
policy from the use of manual virtual machine selection to VipQuery selection.

29. Click Continue in the Virtual machines for backup dialog box, to confirm your selection.

The Clients tab changes to display the Query builder that enables you to create an automated query to
discover VMware virtual machines to back up.

In the steps that follow, you create a two-part automated query using the Query Builder(Basic mode).

o The first part of the query selects a virtual machine using the virtual machine Display name.
o The second part of the query selects VMs whose name starts with a particular keyword.
30. In the Query builder section under Basic mode, click Add query. Build the query using the information
provided in the following table.
 Query Builder field Setting

Join --vacant field--

Field displayName

Operator Equal

Value 'lnxvm1'

31. Click Save to save the query.

32. Verify the query is added to the Queries (Basic mode) section.

Note that the Values for the queries are enclosed in single quotes (' ').

33. In the Query builder section under Basic mode, click Add query to add the second part to the query using
the information provided in the table below.

Query Builder field Setting

Join or

Field displayName

Operator StartsWith

Value(s) 'win'

34. Click Save to save the query.

35. Verify the second part of the query is added to the Queries (Basic Mode) section.
36. Click the Test query button, located at the bottom of the Clients tab.

The Test query for policy: VMware_policy dialog box is displayed with the Test query results.
37. Verify that the test query results show the four VMs were
discovered, winvm1, lnxvm1, vcenter2 and lnxvm3, and two VMs were Included (for backup) by the query
operation.

The Test Query may take a minute or more to complete.

38. Click the Close button to close the Test query for policy: VMware_policy window.

Verifying the policy Backup selections

When a policy uses an automated query(VipQuery) to discover the virtual machines to back up, the Backup
Selections tab of the policy is automatically populated with an entry that shows the query that is used.

39. Verify the Backup selections tab is greyed out that describes the automated query that will be used by
the policy to discover the VMware virtual machines.

You cannot modify the contents of the Backup selections tab for a VMware policy that uses an automated
query(VipQuery) to discover VMware virtual machines to back up. The buttons that normally enable you to
change the contents of the Backup Selections are disabled for a VMware policy that uses an Intelligent Query
to select VMs that will be backed up using the policy.

Saving the policy changes

In the steps that follow, you save all the changes that were applied to the VMware_policy policy.

40. Click Create located at the right bottom side in the Create policy window to save
the VMware_policy policy changes, and to close the Create Policy window.

NetBackup validates the setting of the policy. If a problem is encountered with the policy, an error dialog box
is displayed.

41. Verify that the VMware_policy policy is added to the list of policies that is displayed in the Policies page
of the NetBackup Web UI.

In this exercise, you created a NetBackup policy, named VMware_policy that enables manual, full backups of
VMware virtual machines that are discovered by NetBackup using an automated query(VipQuery). The virtual
machines that meet the criteria of the automated query are backed up by the policy to AdvancedDisk storage
that is configured on the Master/Primary server, lnxmaster.vrtsedu.lab.

Exercise C: Performing and Monitoring VMware Virtual Machine Backups

In this exercise, you use the VMware_policy policy that you created earlier in this lab activity, to perform a manual
backup operation. Then, you use the NetBackup Activity monitor to view the resulting backup jobs.

In the steps that follow, you initiate a manual backup of the VMware_policy policy and monitor the backup until
completion.

1. In the Protection > Policies, select the entry for the VMware_policy policy, located in the Policies pane,
then select Manual Backup.

The Select one or more clients you want to back up section of the Manual backup window contains the
entry, MEDIA_SERVER. This entry denotes that the MEDIA_SERVER (BACKUP HOST) will use the automated
query of the VMware Intelligent Policy to select the VMware virtual machines that will be backed up by the
policy.

2. Click OK button in the Manual backup window without making any other selections, to initiate the
manual backup operation.

Successfully sent backup request message is displayed.

3. Select the Activity monitor entry in the left pane of the NetBackup Web UI.
4. View the Jobs tab of the Activity monitor and take note of the number of jobs that are added as a result
of the manual backup operation that you initiated.

These jobs are all controlled by the VMware_policy policy.

It may take several minutes for all the resulting jobs to be added to the Activity monitor.

5. Take note of the information about the jobs that were initiated, based on their Job IDs, and as identified in
the table below.

Jobs Job type Client backed up

First job (lowest job number) Backup job (parent job) listed as media server

Second job Snapshot winvm1

Third job Snapshot lnxvm1

Fourth job Backup lnxvm1

Fifth job Backup winvm1

 6.
7. Allow all the jobs to run to completion before continuing.

In some cases, it may take a while (10 -15 minutes) for all jobs to run to completion.

8. Verify that all the jobs run to successful completion. If one or more of the jobs fail, record the status code
or status codes and seek assistance.
9. View the Job Details for each of the jobs that resulted from the manual backup of
the VMware_policy policy.
10. To view Job Details for a job, click on the Job ID for the respective job and then select the Details tab.

A parent Backup job is launched first. The initial parent job is the parent of two Snapshot jobs --
one Snapshot job for each of the VMware virtual machines that will be backed up in this lab environment
(winvm1, lnxvm1).

Each Snapshot job becomes the parent of a Backup job that is used to back up a virtual machine from the
snapshot that was created of the virtual machine. The second Snapshot job remains in the Queued state until
the first Snapshot job and its associated Backup job run to completion. At that time, the
second Snapshot job goes Active, and the associated Backup job becomes visible in the Activity
monitor and goes Active. The concurrency of the jobs, or the lack thereof, is related to the number of
concurrent jobs that is configured for the target storage unit for the jobs.

Jobs might take 10-15 minutes to complete.

11. Close any open Job Details windows.

12. Minimize the NetBackup Web UI as you will use it in a later exercise.

Exercise D: Excluding Disks from a VMware Virtual Machine Backup

In this exercise, you first install and configure the plug-in for vSphere client. You then configure a VMware Custom
Attribute through the vSphere Web Client to exclude a disk located on the VMware client, winvm1. Then, you
configure a policy, Exclude_disks, to apply the Custom Attribute to the policy.
Installing and configuring vSphere client plug-in

1. Locate and launch the PuTTY shortcut present on the desktop.

2. Connect to lnxmaster using the following credentials:
o User name: root
o Password: P@ssw0rd

3. Execute the following command to begin the plugin installation:

/usr/openv/netbackup/bin/goodies/vwcp_manage

4. Minimize the PuTTY window.

5. The vwcp_manage is a Java GUI application. Registration of the plugin starts with the End User License
Agreement.
6. Click Accept.
7. Provide following information in the VMware vCenter Server Details:

Hostname: 10.10.2.99

Username: administrator@vrtsedu.lab

Password: P@ssw0rd

Port:443

8. Click Validate.
9. In the Plug-in Registration window, verify the name of the NetBackup server and click Register.
10. A security alert appears. Read the information carefully and click Continue.
11. Ensure the plugin is successfully registered. Click Close.
12. Launch a new window in the Firefox Web browser. Enter the following URL to download the vCenter CA
certificates:

https://10.10.2.99/certs/download.zip

13. Verify the certificates are downloaded in the downloads folder.

14. Minimize the Firefox web browser.
15. Using the File explorer, navigate to the downloads folder. Right-click the download.zip folder and
select Extract all.
16. Extract the contents to the default path.
17. Next, you are required to copy the certificate file from this zip folder to the NetBackup Primary server.
18. From the desktop of the Console vm, locate and double-click the shortcut for Command Prompt.
19. Enter the following commands:

cd \users\administrator\downloads\download\certs\lin

pscp dbad4059.0 root@lnxmaster.vrtsedu.lab:/tmp

20. When promted for the password, enter the password as P@ssw0rd.
21. Ensure the file is successfully copied to /tmp directory on the master server.

22. Access the PuTTY session connected to lnxmaster.

23. Enter the following command to get the store key:

cat /usr/openv/var/global/jkskey

24. You need to copy the store key that is displayed. This vale will be used in the next steps.
25. Enter the following command, however update the value of storepass which you copied earlier.

/usr/openv/java/jre/bin/keytool -storetype BCFKS -providerpath /usr/openv/wmc/webserver/lib/ccj-3.0.1.jar -

providerclass com.safelogic.cryptocomply.jcajce.provider.CryptoComplyFipsProvider -importcert -trustcacerts
-file /tmp/dbad4059.0 -keystore /usr/openv/var/global/wsl/credentials/truststoreVWCP.bcfks -storepass
87324987439 -alias VMwareCA
26. Type yes and press Enter, when Trust this certificate? appears.
27. Ensure that the Certificate was added to keystore message is displayed.
28. Close the Command prompt window.

Configuring a VMware custom attribute to exclude virtual disks

In the following steps, you create a Custom Attribute using the vSphere Web Client to exclude a virtual disk on the
VMware client, winvm1.

29. Access the web browser from console.vrtsedu.lab system and connect to the VMware vsphere client. If
you are already logged in, you need to log out and login again. Alternatively, you can type the following
address:

https://10.10.2.99/ui

Use the following credentials:

o User name: administrator@vsphere.local

o Password: P@ssw0rd

Within a few moments, the vSphere Web Client is connected to the vCenter server.

30. From Menu drop-down list select Veritas NetBackup tab.

 If the vSphere Web Client is not displayed in the Home screen, click the Home icon located under Menu.

31. Login to the plug-in using the following credentials:

Select a NetBackup Primary server: lnxmaster.vrtsedu.lab

Username: root

Password: P@ssw0rd

32. Select the Virtual Disk Exclusion tab.

33. Click the RUN VIRTUAL DISK EXCLUSION WIZARD button. In the Virtual Disk Exclusion
Wizard screen, verify that the vCenter Server entry is set to 10.10.2.99.
34. In the Search field, type winvm1 and then click Search.
35. From the Search Results, select winvm1, and then click the ADD VIRTUAL MACHINE button.

One virtual machine is added to the Custom Attribute as shown in the figure below.

36. Verify that one (1) Virtual Machine was added in the Virtual Disk Exclusion Wizard.
37. Click Next.
38. In the Available Disks for winvm1 section, mark the checkbox for Hard disk 2, scsi0-1.
 In the Available Disks section, select Hard disk 2 (scsi 0:1) for this option.

39. Click Next.

40. In the Virtual Machines and Excluded Disks section, click the EXCLUDE DISKS button.

41. After the "Successfully set virtual disk exclusions" message is displayed, click FINISH.

You have created a VMware Custom Attribute to exclude Hard disk 2 for the virtual machine, winvm1.

42. Log out from the vSphere Web Client user interface, and close the Web browser window.
Configuring a policy to exclude disks from a VMware backup

In the steps that follow, you configure a VMware policy, Exclude_disk, to exclude virtual disks with a custom
attribute that was created in the previous exercise.

43. Access the desktop of the console system.

44. Access the minimized NetBackup Web UI.
45. Select Policies in the navigation pane of the NetBackup Web UI.

The policies that are currently configured are listed in the Policies pane.

46. Select the check box on the left side of the VMware_policy policy and select Copy policy.
47. In the Copy policy pop-up window type Exclude_disk in the New policy field, then click Copy to create a
new policy.
48. After the policy is created you can see the Exclude_disk policy in the Policies pane.
49. Select the check box on the left side of the Exclude_disk policy and click Edit to edit the policy.

The Edit policy - Exclude_disk page is displayed.

50. In the Edit policy - Exclude_disk page, click the Clients tab.
51. In the Query builder (Basic mode) section, remove the query, displayName eq 'lnxvm1' by clicking
the Remove button present at the right end of the query.

Only the startswith(displayName,'win' entry remains in the Query builder (Basic Mode) section.

52. Click the Test Query button, and verify that winvm1 is the only virtual machine host to be included when
this policy is used to perform a backup operation.
53. Click Close to close the Test query for policy: Exclude_disk pop-up window.
54. Click the Exclude disks tab.
55. In the Exclude virtual disk from backup section, select the radio button for the Perform custom attribute
based exclusion option.
56. In the Custom Attribute field, type exclude_vm_disk.

The custom attribute name in the policy must match the name of the custom attribute that was created it in
the Disk Exclusion Wizard in the vSphere Web Client interface (in the previous exercise).

57. Click Save to save the policy.

Performing and monitoring a VMware backup

In the steps that follow, you initiate a manual backup of the Exclude_disk policy and monitor the backup job until
completion.
58. Select Policies in the navigation pane of the NetBackup web user interface.
59. Select the check box on the left side of the Exclude_disk policy and click Manual backup.
60. Click OK button in the Manual Backup pop-up window without making any other selections, to initiate
the manual backup operation.
61. Select the Activity monitor in the navigation pane of the NetBackup web user interface to monitor the
backup job.
62. View the Jobs tab of the Activity monitor and take note of the number of jobs that are added as a result
of the manual backup operation that you initiated.

Three jobs are initiated as a result of this backup.

It may take a couple of minutes for all the resulting jobs to be added to the Activity monitor.

63. Click the Job ID of the backup job that has the Schedule of Full associated with it. This should be the job
with the highest Job ID.
64. View the Job Details of this job, and verify that the job completes successfully (status 0).
65. To view the Job Details for a job, click on the Job ID for the respective job and then select
the Details tab.
o If the job completes successfully, continue to the next step.
o If any of the VMware jobs that use the Exclude_disk policy fail (end in a non-zero status), view
the Detailed Status for the failed job and attempt to identify the cause of the problem. Attempt to
resolve the issue, and repeat the backup jobs using the Exclude_disk policy. If problems persist, seek
technical assistance.

One way to verify that the disk exclusion worked as planned is to compare the contents of the Bytes
transferred and Files written values in the Details tab of the most recent backup job of the virtual machine,
with the contents of the same field from the previous backup job of the virtual machine (backed up in Exercise
C). The Bytes transferred and Files written values for the most recent job should be less than in the previous
job (which did not exclude disks from the virtual machine backup). Additionally, you can compare the values
of scanned KB and sent KB displayed in the Details tab.
The job may take 10-15 minutes to complete.

66. Close any open Job details windows.

Exercise E: Configuring Continuous Data Protection

In this exercise, you configure Continuous data protection (CDP) gateway and create a Continuous data
protection-based protection plan for your VMware workload. Finally, you protect the required VMs with the
protection plan and monitor the jobs.
Prerequisites for using Continuous data protection CDP have been pre-configured in this lab. Refer to
the NetBackup Web UI VMware Administrator's Guide, Continuous data protection topic for detailed information.

Configuring a VM Storage Policy

1. From the console vm, login to the VMware vSphere Client.

2. Select Menu>Policies and Profiles.
3. Select VM Storage Policies and click CREATE.
4. Provide the Name as vtstap and click NEXT.

5. On the Policy structure page, under Host based services, select the checkbox Enable host based
rules and then click NEXT.
6. On the Host based services page, click the tab Replication.
7. Select the option Custom. Ensure that the Provider is set to vtstap and the encoding value is set to 2.
8. CLick NEXT.
9. On the Storage compatibility page, it will list compatible datastores.Click NEXT to continue.
10. On the Review and finish page,click FINISH.

Assigning the VM storage Policy to a VM

11. In the VMware vSphere client, access the Menu and click Inventory.
12. Browse to 10.10.2.99>DC1>esx1.vrtsedu.lab>.
13. Right-click lnxvm3. Select VM Policies>>Edit VM policies.
14. In the Edit VM Storage Policies, under the VM storage policy, select the policy vtstap and click OK.
Defining the Continuous data protection (CDP) gateway.

In the steps that follow, you define a gateway for your Continuous data protection (CDP) deployment, before you
can protect any VMs. You can define the Continuous data protection (CDP) gateway in a VM that is a NetBackup
Media or Primary Server.

15. In the NetBackup web user interface, in the navigation pane, click VMware under Workloads.
16. On the top right, click VMware settings, and click Continuous data protection gateway.
17. In the Continuous data protection gateway page, click Add.
18. In the Add Continuous data protection gateway page, enter the following details.
o Host name - lnxmedia.vrtsedu.lab
o Storage path - /cdpfs
19. Click Next to proceed.
20. Review the information message displayed on the Add Continuous data protection gateway page.
Expand the Advanced tab and review all the settings. Do not make any changes.
21. Click Save to add the Continuous data protection gateway.
22. After the gateway is added successfully, you can see the gateway name, Recommended number of VMs
and Total VMs subscribed in the Continuous data protection gateway page.

Creating a CDP enabled protection plan

In the steps that follow, you create a CDP enabled protection plan.

23. In the Netbackup web user interface, in the navigation pane, click Protection Plans under Protection.
24. In the Protection plans page, click Add. The Create protection plan window is displayed.
25. In the Basic properties tab, perform the following steps:
a. Enter the Name as: cdp_enabled.
b. Click the drop-down arrow for Workload and select VMware
c. Mark the check box for Enable Continuous Data Protection.
d. Click Next to continue.
26. In the Schedules tab, verify the details. Leave all the options at default and click Next to continue.
27. In the Storage options tab, in the Backup storage field, click Edit.

The Select Backup Storage window is displayed.

28. In the Select Backup Storage window, select the storage name as media_msdp_stu.

Click the Use selected storage button.

29. You are returned to the Storage options tab. Click Next to continue.
30. In the Backup options tab, select the lnxmedia.vrtsedu.lab server in the Continuous data protection
gateway section.
 Click Next to continue.

31. In the Permissions tab, retain the default values and click Next to continue.
32. In the Review tab, review all the details and click Finish.
33. Ensure that the protection plan cdp_enabled is displayed in the Protection plans page.

Adding virtual machines to CDP enabled protection plan

In the steps that follow, you add a CDP enabled protection plan to the virtual machine.

34. In the Netbackup web user interface, in the navigation pane, click VMware under Workloads.
35. In the VMware page, click Virtual machines tab.

Take a look at the Protected by column values. All three VMs value is Not protected.

36. Mark the check box present on the left side of the virtual machine lnxvm3 and Click Add protection.
37. In the Choose a protection plan - Assets: lnxvm3 page, verify cdp_enabled protection plan is selected.

Click Next to continue.

38. Verify all the details and click Protect.

As soon as Protection plan is created you will see backup jobs for the protected virtual machine in Activity
monitor.

39. In the Subscribe assets to protection plan - Assests: lnxvm3 page, you can see lnxvm3 is added to the
plan.

The selected assets have been succesfully subscribed to the protection plan message is displayed.

40. Click Close to close the Subscribe assets to protection plan - Assests: lnxvm3 page.
41. In the VMware page, under Virtual machines tab you can see lnxvm3 is now protected
by cdp_enabled protection plan.

Monitoring CDP jobs

In the steps that follow, you monitor CDP jobs that have been initiated using the CDP enabled protection plan.

42. In the Netbackup web user interface, in the navigation pane, click Activity monitor. (It may take 2-3
minutes for the job to appear.)
43. In the Activity monitor, you will see the following jobs.
o Parent backup job - discovery job to discover the VM information.
o Preparing For Backup job - identify the point in time data for the VM.
 o Backup job - move data from the staging path to the backup storage.
You might see extra jobs getting triggered for CDP enabled protection plan. Jobs
having vm_consistency_level=0 will be shown as recovery points. Check the Overview tab of Backup job to
verify the vm_consistency_level.
The jobs may take 10-15 minutes to complete.

44. View the Job Details for each of the jobs that resulted from the cdp_enabled protection plan.
45. To view Job Details for a job, click on the Job ID for the respective job and then select the Details tab.
46. Close any open Job Details windows.

Lab Part B: Recovering VMware Environments

Exercise A: Recovering Virtual Machine Files (Agent-based)

In this exercise, you perform the steps to recover individual VMware virtual machine files to a VMware virtual
machine using the Backup, Archive, and Restore user interface. The Backup, Archive, and Restore user
interface is launched from the NetBackup Administration Console that is logged on to your NetBackup Master
Server.

Launching Backup, Archive, and Restore from the NetBackup Administration Console

In this exercise, you restore virtual machine files directly to the Linux-based virtual machine, lnxvm1, using
the Backup, Archive, and Restore user interface which you launch from the NetBackup Administration
Console.

Restoring individual file and folder contents to a VMware virtual machine requires that:

 The virtual machine must be powered on.

 The NetBackup Client software must be installed on the VM.

If you are restoring individual files to a VMware virtual machine on which the NetBackup client software
is not installed, you must use a two-step process:
o Step one: Use NetBackup to restore the individual VM files to an alternate NetBackup client
system.
o Step two: Move (or copy) the restored VM files from the alternate client to the original VMware
virtual machine. This step occurs outside of NetBackup and does not use NetBackup.
In this lab activity, you will not perform a two-stage restore of virtual machine files.
1. Locate and double-click the NetBackup 10.0 Administration Console shortcut, located on the desktop
of the console.vrtsedu.lab system, to launch the NetBackup Administration Console, if not already open.
2. Login using the following credentials.
o Host name: lnxmaster.vrtsedu.lab
o User name: root
o Password: P@ssw0rd

3. View the top entry in the left pane of the NetBackup Administration Console window to verify that you
are connected to your Master Server, lnxmaster.vrtsedu.lab.
4. If the NetBackup Administration Console is not connected to your Master Server, click the "Launch a
new instance …" button to connect to your Master Server.
5. Click the Backup, Archive, and Restore entry, located in the left pane.

The right pane of the Administration Console displays the Backup, Archive, and Restore user interface.

Using NetBackup to restore individual VMware virtual machine files to a VMware VM

In the steps that follow, you use the Backup, Archive, and Restore user interface -- launched from
the NetBackup Administration Console -- to restore VMware virtual machine files directly to the original folder
location on the VM, lnxvm1.

15. From the Backup, Archive, and Restore pane, verify that the Restore Files tab is selected.
16. Click the 'pointing finger' icon located at the top right side to access the Specify NetBackup Machines
and Policy Type window.
17. In the Specify NetBackup Machines and Policy Type window, change the Policy type for
restores to VMware.
18. Click the Search VM Clients button in the Specify NetBackup Machines and Policy Type window.
19. When the Browse and Search Virtual Machines for Restore screen is displayed, click the Browse virtual
machines and vSphere view radio buttons.

Click Next to continue.

20. On the Browse and Search Virtual Machines for Restore screen, expand the entries
for vcenter1.vrtsedu.lab (vCenter server) and the /DC1 data center.
21. Click to select the esx1.vrtsedu.lab entry which reveals entries for the virtual machines that have been
backed up.
22. Click the entry for the virtual machine, lnxvm1, and then click Select to continue.

You are returned to the Specify NetBackup Machines and Policy Type window.

23. In the Destination client for restores field, verify that lnxvm1 is listed.

If lnxvm1 is not present in the Destination client for restores drop-down list, see the following Note.
 If an entry for lnxvm1 is not present in the drop-down list for the Destination client for restores field, click
the Edit Client List button, and add an entry for lnxvm1 to the client list.

24. Check the values that you have specified in the Specify NetBackup Machines and Policy Type window
as follows.
o Server to use for backups and restores: lnxmaster.vrtsedu.lab
o Source client for restores: lnxvm1
o Destination client for restores: lnxvm1
o Policy type for restores: VMware
25. Click OK to save the Specify NetBackup Machines and Policy Type window entries.
26. If a message is displayed stating 'no files are found', click OK to acknowledge the message and continue.

From the Actions menu, click Set Date Range, and then click Backup History.

27. In the Restore type field, verify the Normal Backups entry is selected in the drop down menu.

Normal Backups is the default selection.

28. If / (forward slash) is not already present in the Browse Directory field, type a / in the Browse
directory field, and press Enter.
29. Expand the contents of the root Directory Structure pane so that the etc folder is visible in the directory
structure of the backup image.
30. In the Directory Structure pane, click the entry for the, etc folder (but do not select the check box for the
folder).

Note that the contents of the folder are displayed in the Contents of selected directory pane (the right pane
of the Backup, Archive, and Restore user interface).

31. In the Contents of selected directory pane, click the checkboxes for the hostname file to select the file
for restore.
32. Click the Restore button.

The Restore Marked Files window is displayed.

33. When the Restore Marked Files screen is displayed, verify that the Restore everything to its original
location radio button is selected.
34. In the Options area of the Restore Marked Files window, click the check box for the Overwrite existing
files parameter.

35. Leave all other settings of the Restore Marked Files window at the default settings, and click the Start
Restore button, to start the restore operation.
 You may need to resize the Restore Marked Files window to view the Start Restore button at the bottom of
the window.

36. In the View Progress dialog box, click Yes to observe the progress of the restore operation.
37. Monitor the progress of the restore operation in the Task Progress tab of the Backup, Archive, and
Restore user interface.

You can also use the NetBackup Activity monitor to monitor the restore progress.

38. Verify that the restore operation is completed successfully before continuing.
o If the restore job is successful, continue to the next step.
o If the restore operation fails, take note of error messages that may be displayed in the Results of the
Task Selected Above pane of the Task Progress pane. You may also view the details of the most
recent Restore job in the Activity monitor for information on the failure. Attempt to correct the
issue, and then repeat the restore operation. If the restore operation continues to fail, seek technical
assistance.

At this point, you have restored a file that was backed up from the lnxvm1 virtual machine to the original
folder location of the files on the client.

39. Minimize the NetBackup Administration Console window.

You will access the NetBackup Administration Console window again in a later exercise.

Exercise B: Recovering a VMware Virtual Machine Disk

In this exercise, you use the new Restore Virtual Machine Disks wizard to restore an individual virtual disk for the
VMware virtual machine, winvm1, from the backup.

Restoring an individual virtual disk

In the steps that follow, you first delete data on the virtual host, winvm1, then you perform an individual virtual
disk restore.

1. On the desktop of console.vrtsedu.lab, double-click the shortcut for winvm1.rdp.

2. Click Cancel to close the Shutdown Event Tracker pop-up window.
3. On the desktop of winvm1, double-click File Explorer.
4. Navigate to the F:\data3 directory.
5. Click the smallfiles directory in the left pane.
6. Press the Shift + Delete key to permanently delete the smallfiles directory.
7. Click Yes to confirm the deletion, and verify that the smallfiles directory has been deleted.
8. Close the File Explorer window.
9. Minimize the RDP Profiles (Windows systems) window to winvm1.
10. Access the NetBackup 10.0 Administration Console window on console.vrtsedu.lab and select
the Backup, Archive, and Restore entry in the left pane.
11. Select the Restore Files tab, if it is not already selected.
12. Click Actions, and then click Specify NetBackup Machines and Policy Type.
13. In the Specify NetBackup Machines and Policy Type window, from the Policy type for restores drop-
down menu, select VMware.
14. Click Search VM Clients.
15. In the Selection Method section verify that Search virtual machines is selected, then click Next.
16. Type winvm in the Browse and Search Virtual Machines for Restore, then click Next.
17. From the resulting search, select the winvm1 host, then click Select.
18. After you have verified the host names are selected in the Specify NetBackup Machines and Policy
Type window -- as following, click OK to save the changes.

Server: lnxmaster.vrtsedu.lab
Source client: winvm1
Destination client: winvm1
Policy type for restores: VMware

DO NOT use the hostname winvm1.vrtsedu.lab for Source and Destination clients for this restore
operation. The backup image that is required to perform this restore was created using the client
name, winvm1 (the short name of the client), therefore the short name of the client must be used to search
for the backup image to use for the restore.

Click OK in the No Files Found dialog box.

19. From the Actions menu, click Set Date Range, and then click Backup History.
20. Select the backup that belongs to the Exclude_disk policy, then click OK.

Click OK in the No Files Found dialog box.

21. From the Restore type drop-down menu select Virtual Disk Restore.

Click OK in the No Files Found dialog box.

22. In the Browse directory field type a / (forward slash) and press Enter.
23. From the Contents of winvm1 pane locate the Policy column.

You may need to scroll to the right to locate the Policy column.

24. Click the Policy heading until a right side up triangle appears.
 The sort order for the data in the Policy Column should be from A-Z.

25. Drag the Policy column to the right of the Name column.

The Directory Structure pane only lists the hostname, winvm1, and the Contents pane lists 3 VMDK
files: winvm1_1.vmdk, winvm1_2.vmdk, and winvm1.vmdk. You may need to expand the Name column to
see the full name.

26. In the Directory Structure pane, mark the checkbox for winvm1 and then click Restore….

A Restore Virtual Machine Disks wizard is launched.

27. In the Select Virtual Disks window, take note that there are three (3) Virtual Disks listed.

28. In the Select Disks pane, mark the checkbox for the Virtual Disk listed
as [datastore2] winvm1/winvm1_2-000002.vmdk, then click Next.

The disk with the yellow caution symbol indicates this virtual disk has no data to be restored. In a previous
exercise, a VMware Custom Attribute was created that excluded this disk, scsi0-1. Then, a policy was created to
exclude any disks associated with that Custom Attribute.

29. Review the Recovery Destination screen options, but leave all settings at their default values.

Click Next to continue.

30. Review the Virtual Disk Destination screen options, then click Next to continue.
31. From the Storage Destination screen, mark the checkbox to overwrite the existing data.

The dropdown menu for Overwrite all virtual disks changes from the default of No to Yes when the
checkbox is selected.
The Restored virtual disks provisioning is set to Original and the Provisioning column associated with the
virtual disk is set to Thin. This means that the virtual disks will be restored to their original provisioned state -
Thin.

32. Click Next, then click OK, to acknowledge that you have selected to overwrite the virtual disks.
33. Review the Recovery Summary screen contents, then click Start Recovery.
34. Click Yes to view the progress of the restore.
35. On the Task Progress tab, mark the Full Contents checkbox, and monitor the restore operation until it
completes successfully.
 DO NOT proceed until the restore job is successful. If the restore job fails, review any failure information that
is provided, and attempt to correct the problem. Then repeat the steps to perform the restore. If failures
persist, seek technical assistance.

You can also view the progress of the restore job using the Activity monitor.

36. On the desktop of console.vrtsedu.lab, double-click the RDP Profiles (Windows systems) folder.
37. In the RDP Profiles (Windows systems) folder, double-click the winvm1.vrtsedu.lab.rdp profile to
launch a remote session to winvm1.
38. If required, when the Windows Security window is displayed, verify the logon account is set
to VRTSEDU\Administrator and in the Password field type P@ssw0rd. Click OK.
39. From the desktop of winvm1, double-click File Explorer shortcut.
40. Navigate to F\:data3 directory and verify the smallfiles directory and its contents have been restored.
41. Close the RDP session to winvm1.

Exercise C: Recovering the Entire VMware Virtual Machine

In this exercise, you use the NetBackup Web UI to recover an entire VMware virtual machine to its original
datastore location on a VMware ESX server.

Deleting a VMware virtual machine

In the next steps, you delete a VM from the VMware ESX server, esx1.vrtsedu.lab.

1. From the desktop of console.vrtsedu.lab access the vSphere Web Client user interface
(https://10.10.2.99) using the following credentials.
o User name: administrator@vsphere.local
o Password: P@ssw0rd

If you have previously logged in to the vCenter Server using the vSphere Web Client and have not accessed
the user interface for a while, the connection will time out, and display the login screen. It will be necessary to
log in to the vSphere Web Client again.

2. In the vSphere Web Client's navigation pane, right-click the virtual machine lnxvm1, and select Power >
Power Off.
3. In the Confirm Power Off window that is displayed, click YES to power off the virtual machine.
4. Right-click the virtual machine lnxvm1, and select Delete from Disk.

VMware only allows the deletion of virtual machines that are powered off.
5. When the Confirm Delete dialog box is displayed, click Yes to confirm the delete operation.
6. Verify that the entry for the lnxvm1 virtual machine is no longer visible in the left pane of the vSphere
Web Client.
7. Minimize the vSphere Web Client window as you return to the vSphere Web Client window later in this
exercise.

Restoring an entire VMware virtual machine

In the following steps, you use the Recovery points tab to restore the virtual machine, lnxvm1.

8. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system to
launch the NetBackup web user interface.

The Netbackup web user interface can be accessed by navigating to the following URL:
https://master server hostname or IP/webui/login.
For this lab, a web shortcut is preconfigured for accessing the NetBackup web user interface.

9. If a security warning is displayed, click Advanced > Accept the Risk and Continue.
10. Sign in to the NetBackup web user interface using the following credentials.
o Username: root
o Password: P@ssw0rd

11. In the NetBackup web user interface, in the navigation pane, go to Workloads > VMware then click the
Virtual machines tab.
12. Click the lnxvm1 virtual machine from the list.
13. Click the Recovery points tab, in the calendar view on the left, select the date on which the backup
occurred.

The available images are listed in rows with the backup timestamp for each image.

14. Click Recover, from the resulting menu select Restore virtual machine option.
15. In the Recovery target tab verify the following details.
o Display name- lnxvm1
o ESXi server or cluster- esx1.vrtsedu.lab
o Resources pool or vApp- /DC1/host/esx1.vrtsedu.lab/Resources
o Datastore or datastore cluster- datastore2

Do not modify any values and click Next to continue.

16. In the Recovery options tab, mark the check box for Allow overwrite of existing virtual machine. Leave
all other settings to their default.
17. Click Next to continue.
18. In the Review tab, verify that the Pre-recovery check is successful.
 19. Click Start recovery to start the recovery of the virtual machine.
20. After starting the recovery, you will be redirected to the Restore activity tab. You can monitor a job's
progress in this tab.

Select a specific Job ID to view its details.

21. Alternatively, you can also check the Activity monitor to view the job progress. Monitor the restore
operation until it completes successfully.

DO NOT proceed until the restore job is successful. If the restore job fails, review any failure information that
is provided, and attempt to correct the problem. Then repeat the steps to perform the restore. If failures
persist, seek technical assistance.

Verifying the VM recovery using the VMware vSphere Web Client

In the following steps you, verify the virtual machine, lnxvm1, is restored.

22. Access the open VMware vSphere Web Client window on console.vrtsedu.lab.
23. Verify that the lnxvm1 virtual machine has been recovered to the esx1.vrtsedu.lab ESX server.
24. Allow the vSphere Web Client window to remain open on console.vrtsedu.lab. You return to this
window later in this lab activity.

Exercise D: Using VMware Agentless Restore

In this exercise, you perform VMware agentless restore. You use the NetBackup web user interface to restore
individual files. You can use this method to restore multiple files as well as folders.

The agentless restore lets you restore individual files and folders to virtual machines where the NetBackup client is
not installed. By using VxUpdate, NetBackup can deploy the recovery tool to the virtual machines, restore files and
folders, and perform the required cleanup. NetBackup does not require a connection to the target virtual machine
to recover the files. All recovery is handled through the ESX server using VMware vSphere Management APIs.
You must provision VxUpdate packages for all platforms for which you have virtual machines where you want to
perform agentless recovery. Use the nbrepo command to add the VxUpdate packages to the NetBackup package
repository.

Deleting a file from virtual machine

In the next steps, you delete a file from the virtual machine, winvm1.

1. On the desktop of console.vrtsedu.lab, double-click the shortcut for winvm1.rdp.

2. On the desktop of winvm1, double-click File Explorer.
3. Navigate to the C:\data\simple directory.
4. Click the readme.txt file in the right pane.
5. Press the Shift + Delete key to permanently delete the readme.txt file.
6. Click Yes to confirm the deletion, and verify that the readme.txt file has been deleted.
7. Close the File Explorer window.
8. Minimize the RDP Profiles (Windows systems) window to winvm1.
9. Access the NetBackup web user interface window on console.vrtsedu.lab.

Restoring individual file using VMware agentless restore

For restoring individual files using VMware agentless restore, supported destination VM operating systems are
Windows, Red Hat, and SUSE.

10. In the NetBackup web user interface, in the navigation pane, go to Workloads > VMware then click the
Virtual machines tab.
11. Click the winvm1 virtual machine from the list.
12. Click the Recovery points tab, in the calendar view on the left, select the date on which the backup
occurred.

The available images are listed in rows with the backup timestamp for each image.

13. Click Recover, from the resulting menu select the Restore files and folders option.
14. In the Add files tab, click Add to select the files or folders for restore.
15. In the Add files and folders pop-up window, navigate to C:\data\simple directory and
select readme.txt file.
16. Click Add to add the file to the selection list.
17. Click Next to continue.
18. In the Recovery target tab, ensure that the Target VM is winvm1, the File restore option is kept
as Restore everything to the original directory and the target VM credentials are as follows:
o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

19. Click Next to continue.

20. In the Recovery options tab, leave all the settings to their default values and click Next.
21. In the Review tab, verify that the Pre-recovery check is successful.
22. Click Start recovery to start the recovery of the individual file.

For a detailed agentless restore process, refer to the NetBackup Web UI VMware Administrator's Guide, About
VMware agentless restore topic.

23. After starting the recovery, you will be redirected to the Restore activity tab. You can monitor a job's
progress in this tab.
 Select a specific Job ID to view its details.

24. Alternatively, you can also check the Activity monitor to view job progress.

Using job Details you can identify the job was an agentless restore. Look for bpVMutil messages in the
job Details tab.

25. Verify that the restore operation is completed successfully before continuing.

The Job will take 5-10 minutes to complete.

Verifying the individual file recovery

In the following steps you, verify the individual file is restored on the virtual machine, winvm1.

28. On the desktop of console.vrtsedu.lab, double-click the RDP Profiles (Windows systems) folder.
29. In the RDP Profiles (Windows systems) folder, double-click the winvm1.vrtsedu.lab.rdp profile to
launch a remote session to winvm1.
30. If required, when the Windows Security window is displayed, verify the logon account is set
to VRTSEDU\Administrator and in the Password field type P@ssw0rd. Click OK.
31. On the desktop of winvm1, double-click File Explorer.
32. Navigate to the C:\data\simple directory.
33. Verify readme.txt file is present under C:\data\simple directory.
34. Close the File Explorer window on winvm1.
35. Close the RDP session to winvm1.

Exercise E: Downloading Files and Folders from a Virtual Machine Backup Image

In the following steps, you download files and folders from a VM backup image created by the traditional VMware
backup policy.

NetBackup browse an instant access image of the VM to download files and folders. Instant access virtual machine
feature is supported with backup copies that are created from protection plans using the web UI or from classic
policies that are created with the NetBackup Administration Console. This feature is supported for NetBackup
Appliance, NetBackup Virtual Appliance, Flex Appliance, and Build Your Own (BYO) server.
For detailed information on the Instant access feature, refer to the NetBackup Web UI VMware Administrator's
Guide, Instant access topic.

1. Access the NetBackup web user interface.

2. In the NetBackup web user interface, in the navigation pane, go to Workloads > VMware then click
the Virtual machines tab.

Take a look at the Protected by column value for lnxvm1 virtual machine

3. Click the lnxvm1 virtual machine from the list.

4. Click the Recovery points tab, in the calendar view on the left, select the date on which the backup
occurred.

The available images are listed in rows with the backup timestamp for each image.

5. Click Recover, from the resulting menu select the Download files and folders option.

Mounting in progress message is displayed. NetBackup browse an instant access image of the VM to
download files and folders.

6. In the Add files tab, click Add.

7. In the Add files and folders pop-up window, navigate to data > simple directory.
8. Mark the check box for the readme.txt file and click Add.
9. To add a folder to the download list, In the Add files tab, click Add.
10. In the Add files and folders pop-up window, click on the data directory in the left pane.
11. In the right pane, mark the check box for the smallfiles directory and click Add.
12. Verify that you can see the readme.txt file and smallfiles directory in the Add files tab.
13. Click Next to continue.
14. In the Create download package tab, verify that The download package was created and is ready for
download message is displayed.
15. In the Create download package tab, verify that the Selected files and folders section displays
the readme.txt file and smallfiles directory.
16. Click Download to download the package.
17. If required, click Advanced and Accept the Risk and Continue.
18. Click Resend.
19. A package file download is started, wait for the download to complete.
20. Open the File Explorer and navigate to the Downloads folder. The package is downloaded in .zip format.
21. Extract the .zip file and verify the contents.
22. After verifying the contents of the download package file, close all the File explorer windows.
Exercise F: Creating an Instant Access Virtual Machine from a NetBackup Backup
Image

In the following steps, you create an Instant access virtual machine from the traditional VMware backup policy.

You can create an instant access VM from a NetBackup backup image. The VM is available almost instantaneously,
achieving a near-zero recovery time objective. NetBackup mounts the VM's snapshot directly on the backup
storage device to allow your ESXi host or cluster to treat the snapshot as a normal VM.
This feature is supported for NetBackup Appliance, NetBackup Virtual Appliance, Flex Appliance, and Build Your
Own (BYO) server. This feature requires that the NetBackup backup image is stored on a Media Server
Deduplication Pool (MSDP) storage device.

1. Access the NetBackup web user interface.

2. In the NetBackup web user interface, in the navigation pane, go to Workloads > VMware then click
the Virtual machines tab.

Take a look at the Protected by column value for lnxvm1 virtual machine

3. Click the lnxvm1 virtual machine from the list.

4. Click the Recovery points tab, in the calendar view on the left, select the date on which the backup
occurred.

The available images are listed in rows with the backup timestamp for each image. Select the recent one.

5. Click Recover, from the resulting menu select Create instant access virtual machine option.
6. In the Recovery target tab use the following values.
o Display name- lnxvm1-IA-recovered
o ESXi server or cluster- esx1.vrtsedu.lab
o Resources pool or vApp- /DC1/host/esx1.vrtsedu.lab/Resources

After recovery, the recovered virtual machine name will be lnxvm1-IA-recovered.

7. Click Next to continue.

8. In the Recovery options tab, verify the details. Leave all the settings to their default values.
9. Click Next to continue.
10. In the Review tab, verify all the details.

NetBackup generates a snapshot of the selected backup image and creates an instant access mount point.
This mount point lets you power on the virtual machine immediately from your selected ESXi server.

11. Click Start recovery to start the creation of Instant access virtual machine.
12. After starting the recovery, you will be redirected to the Restore activity tab. You can monitor a job's
progress in this tab.
 Select a specific Job ID to view its details.

13. Alternatively, you can also check the Activity monitor to view job progress.
14. View the Job Details of this job, and verify that the job completes successfully (status 0).

Verifying the Instant access virtual machine recovery using the VMware vSphere Web Client

In the following steps you, verify the virtual machine, lnxvm1-IA-recovered, is restored.

15. Locate and double-click the vSphere Client shortcut present on the desktop of console.vrtsedu.lab to
launch the VMware vSphere Web Client.
16. Login using the following credentials.
o User name: vsphere.local\administrator
o Password: P@ssw0rd

17. In the navigation pane to the left, verify that you can see the Instant access virtual machine lnxvm1-IA-
recovered on the esx1.vrtsedu.lab ESX server.
18. In the vSphere Web Client's navigation pane, right-click the virtual machine lnxvm1-IA-recovered, and
select Power > Power Off.
19. In the Confirm Power Off window that is displayed, click YES to power off the virtual machine.
20. Allow the vSphere Web Client window to remain open on console.vrtsedu.lab. You return to this window
later in this lab activity.

Exercise G: Performing Instant Rollback for Virtual Machines

In this exercise, you create a new VMware policy, add new files on the lnxvm1 virtual machine and then perform a
full backup. After backup, you create another set of new files. Finally, you use the Roll back instantly feature to roll
back the lnxvm1 virtual machine from a VM backup image.

Creating a VMware backup policy

In the following steps, you create a new VMware backup policy which will be used for the Instant Rollback feature
later in this exercise.

1. Access the NetBackup web user interface.

2. Select Policies in the navigation pane of the NetBackup Web UI.

The policies that are currently configured are listed in the Policies pane.

3. Select the check box on the left side of the VMware_policy policy and select Copy policy.
4. In the Copy policy pop-up window type Instant_rollback in the New policy field, then click Copy to create
a new policy.
5. After the policy is created you can see the Instant_rollback policy in the Policies pane.
6. Select the check box on the left side of the Instant_rollback policy and click Edit to edit the policy.

The Edit policy - Instant_rollback page is displayed.

7. In the Edit policy - Instant_rollback page, click the Clients tab.

8. In the Query builder (Basic mode) section, remove the query, or startswith(displayName, 'win') by
clicking the Remove button present at the right end of the query.

Only the displayName eq 'lnxvm1' entry remains in the Query builder (Basic Mode) section.

9. Click the Test Query button, and verify that lnxvm1 is the only virtual machine host to be included when
this policy is used to perform a backup operation.
10. Click Close to close the Test query for policy: Instant_rollback pop-up window.
11. Click Save to save the policy.

Creating new files on the virtual machine

In the following steps, you create new files on the lnxvm1 virtual machine before running the backup using the
newly created backup policy Instant_rollback.

12. On the desktop of console.vrtsedu.lab, double-click the PuTTY shortcut.

13. Double-click the entry for lnxvm1.vrtsedu.lab.
14. Log in to the lnxvm1.vrtsedu.lab system using the following credentials.
o Username: root
o Password: P@ssw0rd

15. Navigate to /etc directory using cd /etc command.

16. In the /etc directory create a new folder named Backup_1 using mkdir Backup_1 command.
17. Change the directory to Backup_1 directory using cd Backup_1 command.
18. Run the following command to create new files under Backup_1 directory
o touch File1 File2 File3 File4

19. Verify file creation of files using ls -l command.

20. Minimize the PuTTY window.

Performing and monitoring a VMware backup

In the steps that follow, you initiate a manual backup of the Instant_rollback policy and monitor the backup job
until completion.
 21. Access the NetBackup web user interface.
22. Select Policies in the navigation pane of the NetBackup Web UI.
23. Select the check box on the left side of the Instant_rollback policy and click Manual backup.
24. Click OK button in the Manual Backup pop-up window without making any other selections, to initiate the
manual backup operation.
25. Select the Activity monitor in the navigation pane of the NetBackup web user interface to monitor the
backup job.
26. View the Jobs tab of the Activity monitor and take note of the number of jobs that are added as a result
of the manual backup operation that you initiated.

Three jobs are initiated as a result of this backup.

It may take a couple of minutes for all the resulting jobs to be added to the Activity monitor.

27. View the Job Details of this job, and verify that the job completes successfully (status 0). Monitor the
backup operation until it completes successfully.

Do not proceed until the backup job is successful. If the restore job fails, review any failure information that is
provided, and attempt to correct the problem. Then repeat the steps to perform the restore. If failures persist,
seek technical assistance.

Creating new files on the virtual machine after backup

In the following steps, you create new files on the lnxvm1 virtual machine after running the backup using the
newly created backup policy Instant_rollback.

28. Access the minimized PuTTY session for lnxvm1.vrtsedu.lab system.

29. Verify you are still in the /etc/Backup_1 directory.
30. Run the following command to create new files under Backup_1 directory
o touch NewFile5 NewFile6 NewFile7 NewFile8

31. Verify file creation of files using ls -l command.

32. Close the PuTTY window.

Performing Instant Rollback

In the following steps, you perform the Instant Rollback of lnxvm1 virtual machine using the Roll back instantly
feature.

33. Access the NetBackup web user interface.

34. In the NetBackup web user interface, in the navigation pane, go to Workloads > VMware then click
the Virtual machines tab.
35. Click the lnxvm1 virtual machine from the list.
 36. Click the Recovery points tab, in the calendar view on the left, select the date on which the backup
occurred.

The available images are listed in rows with the backup timestamp for each image. Select the latest backup
image which got created after running the Instant_rollback policy.

In the Activity monitor check the backup start time and end time of Instant_rollback policy. Match the time
frame with images available in Recovery points tab.

37. Click Recover, from the resulting menu select Roll back instantly option.
38. In the Roll back instantly pop up window, verify the selected options and take a look at the message
which is being displayed. Leave the values to their default settings.
39. Click Roll back button to start the Instant Rollback process.

For detailed Instant rollback from a VM backup image process, refer to the NetBackup Web UI VMware
Administrator's Guide, Instant rollback topic.

40. After starting the rollback process, you will be redirected to the Restore activity tab. You can monitor a
job's progress in this tab.

Select a specific Job ID to view its details.

41. Alternatively, you can also check the Activity monitor to view job progress.

You can view the job type Instant Rollback which resulted from the roll back process.

42. Verify that the job completes successfully (status 0).

DO NOT proceed until the restore job is successful. If the restore job fails, review any failure information that
is provided, and attempt to correct the problem. Then repeat the steps to perform the restore. If failures
persist, seek technical assistance.

43. Minimize the NetBackup web user interface.

Verifying Instant Rollback

In the following steps, you verify the Instant Rollback of the lnxvm1 virtual machine.

After the rollback is completed, all data after the selected recovery point is no longer available. The files which
have been created after the backup will not be visible after rollback.

44. On the desktop of console.vrtsedu.lab, double-click the PuTTY shortcut.

45. Double-click the entry for lnxvm1.vrtsedu.lab.
46. Log in to the lnxvm1.vrtsedu.lab system using the following credentials.
 o Username: root
o Password: P@ssw0rd

47. Navigate to /etc/Backup_1 directory using cd /etc/Backup_1 command.

48. List the available files using ls -l command.
o You will see the files [ File1 File2 File3 File4 ] which have been created before backup.
o You will not see the files [ NewFile5, NewFile6, NewFile7, NewFile8 ] which have been created after
backup.

49. This concludes that, after the rollback is completed, all data after the selected recovery point is no longer
available.

Files [ NewFile5, NewFile6, NewFile7, NewFile8 ] have been created after the recovery point.

50. Close the PuTTY window.

Exercise H: Performing Restores from a Continuous Data Protection Backup

In this exercise, you recover the virtual machines protected by Continuous data protection (CDP). You also create
instant access virtual machine from CDP backup. Finally, you use the Download files and folders and Restore files
and folders feature for CDP protected backups.

Restoring an entire VMware virtual machine protected by (CDP)

In the following steps, you restore the lnxvm3 virtual machine protected by CDP to a different datastore. In the
previous lab (Lab 10: Protecting VMware Environments (Windows and Linux), Exercise E: Configuring Continuous
data protection), you have configured the Continuous data protection-based protection plan and
subscribed lnxvm3 to the protection plan.

1. Access the NetBackup web user interface.

2. In the NetBackup web user interface, in the navigation pane, go to Workloads > VMware then click
the Virtual machines tab.

Take a look at the Protected by column value for lnxvm3 virtual machine

3. Click the lnxvm3 virtual machine from the list.

4. Click the Recovery points tab, in the calendar view on the left, select the date on which the backup
occurred.

The available images are listed in rows with the backup timestamp for each image.
5. Click Recover, from the resulting menu select the Restore virtual machine option.
6. In the Recovery target tab use the following values.
o Display name- lnxvm3-recovered
o ESXi server or cluster- esx1.vrtsedu.lab
o Resources pool or vApp- /DC1/host/esx1.vrtsedu.lab/Resources
o Datastore or datastore cluster- datastore2

After recovery, the recovered virtual machine name will be lnxvm3-recovered and the datastore will
be datastore2

7. Click Next to continue.

8. In the Recovery options tab, verify the details. Leave all the settings to their default values.
9. Click Next to continue.
10. In the Review tab, verify that the Pre-recovery check is successful.
11. Click Start recovery to start the recovery of the virtual machine.
12. After starting the recovery, you will be redirected to the Restore activity tab. You can monitor a job's
progress in this tab.

Select a specific Job ID to view its details.

13. Alternatively, you can also check the Activity monitor to view job progress.
14. View the Job Details of this job, and verify that the job completes successfully (status 0).

DO NOT proceed until the restore job is successful. If the restore job fails, review any failure information that
is provided, and attempt to correct the problem. Then repeat the steps to perform the restore. If failures
persist, seek technical assistance.

Verifying the VM recovery using the VMware vSphere Web Client

In the following steps you, verify the virtual machine, lnxvm3-recovered, is restored.

15. Access the open VMware vSphere Web Client window on the console.vrtsedu.lab.
16. Verify that the lnxvm3-recovered virtual machine has been recovered to the esx1.vrtsedu.lab ESX server.
17. In the vSphere Web Client's navigation pane, right-click the virtual machine lnxvm3-recovered, and
select Power > Power Off.
18. In the Confirm Power Off window that is displayed, click YES to power off the virtual machine.
19. Allow the vSphere Web Client window to remain open on the console.vrtsedu.lab. You return to this
window later in this lab activity.

Creating Instant access virtual machine from CDP backup

In the following steps, you create an Instant access virtual machine from CDP backup.
20. Access the NetBackup web user interface.
21. In the NetBackup web user interface, in the navigation pane, go to Workloads > VMware then click
the Virtual machines tab.

Take a look at the Protected by column value for lnxvm3 virtual machine

22. Click the lnxvm3 virtual machine from the list.

23. Click the Recovery points tab, in the calendar view on the left, select the date on which the backup
occurred.

The available images are listed in rows with the backup timestamp for each image.

24. Click Recover, from the resulting menu select Create instant access virtual machine option.
25. In the Recovery target tab use the following values.
o Display name- lnxvm3-IA-recovered
o ESXi server or cluster- esx1.vrtsedu.lab
o Resources pool or vApp- /DC1/host/esx1.vrtsedu.lab/Resources

After recovery, the recovered virtual machine name will be lnxvm3-IA-recovered.

26. Click Next to continue.

27. In the Recovery options tab, verify the details. Leave all the settings to their default values.
28. Click Next to continue.
29. In the Review tab, verify all the details.

NetBackup generates a snapshot of the selected backup image and creates an instant access mount point.
This mount point lets you power on the virtual machine immediately from your selected ESXi server.

30. Click Start recovery to start the creation of Instant access virtual machine.
31. After starting the recovery, you will be redirected to the Restore activity tab. You can monitor a job's
progress in this tab.

Select a specific Job ID to view its details.

32. Alternatively, you can also check the Activity monitor to view job progress.
33. View the Job Details of this job, and verify that the job completes successfully (status 0).

Verifying the Instant access virtual machine recovery using the VMware vSphere Web Client

In the following steps you, verify the virtual machine, lnxvm3-IA-recovered, is restored.

34. Access the open VMware vSphere Web Client window on the console.vrtsedu.lab.
35. Verify that you can see the Instant access virtual machine lnxvm3-IA-recovered on
the esx1.vrtsedu.lab ESX server.
36. In the vSphere Web Client's navigation pane, right-click the virtual machine lnxvm3-IA-recovered, and
select Power > Power Off.
37. In the Confirm Power Off window that is displayed, click YES to power off the virtual machine.
38. Allow the vSphere Web Client window to remain open on the console.vrtsedu.lab. You return to this
window later in this lab activity.

Download files and folders from a VM backup image

In the following steps, you download files and folders from a VM backup image created by CDP.

39. Access the NetBackup web user interface.

40. In the NetBackup web user interface, in the navigation pane, go to Workloads > VMware then click
the Virtual machines tab.

Take a look at the Protected by column value for lnxvm3 virtual machine

41. Click the lnxvm3 virtual machine from the list.

42. Click the Recovery points tab, in the calendar view on the left, select the date on which the backup
occurred.

The available images are listed in rows with the backup timestamp for each image.

43. Click Recover, from the resulting menu select the Download files and folders option.

Mounting in progress message is displayed. NetBackup browse an instant access image of the VM to
download files and folders.

44. In the Add files tab, click Add.

45. In the Add files and folders pop-up window, navigate to data > simple directory.
46. Mark the check box for the readme.txt file and click Add.
47. To add a folder to the download list, In the Add files tab, click Add.
48. In the Add files and folders pop-up window, click on the data directory in the left pane.
49. In the right pane, mark the check box for the smallfiles directory and click Add.
50. Verify that you can see the readme.txt file and smallfiles directory in the Add files tab.
51. Click Next to continue.
52. In the Create download package tab, verify that The download package was created and is ready for
download message is displayed.
53. In the Create download package tab, verify that the Selected files and folders section displays
the readme.txt file and smallfiles directory.
54. Click Download to download the package.
55. A package file download is started, wait for the download to complete.
56. Open the File Explorer and navigate to the Downloads folder. The package will get downloaded in .zip
format.
57. Extract the .zip file and verify the contents.
58. After verifying the contents of the download package file, close all the File explorer windows.

Restore files and folders from a VM backup image

In the following steps, you restore files and folders from a VM backup image created by CDP.

59. Access the NetBackup web user interface.

60. In the NetBackup web user interface, in the navigation pane, go to Workloads > VMware then click
the Virtual machines tab.

Take a look at the Protected by column value for lnxvm3 virtual machine

61. Click the lnxvm3 virtual machine from the list.

62. Click the Recovery points tab, in the calendar view on the left, select the date on which the backup
occurred.

The available images are listed in rows with the backup timestamp for each image.

63. Click Recover, from the resulting menu select the Restore files and folders option.

Mounting in progress message is displayed. NetBackup browse an instant access image of the VM to restore
files and folders.

64. In the Select files tab, click Add.

65. In the Add files and folders pop-up window, navigate to data > Doc_files directory.
66. Mark the check box for the NetBackup7.6.1_RelNotes.pdf file and click Add.
67. To add a folder to the list, In the Select files tab, click Add.
68. In the Add files and folders pop-up window, click on the data directory in the left pane.
69. In the right pane, mark the check box for the smallfiles directory and click Add.
70. Verify that you can see the NetBackup7.6.1_RelNotes.pdf file and smallfiles directory in the Select
files tab.
71. Click Next to continue.
72. In the Recovery target tab, verify Target VM is lnxvm3.
a. In the File restore options section, select Restore everything to a different directory radio button.

In the Directory for restore field enter /tmp/restore.

b. In the Target VM Credentials, enter the following credentials.

  Username- root
 Password- P@ssw0rd

73. Click Next to continue.

74. In the Recovery options tab, leave the settings at their default values.
75. Click Next to continue.
76. In the Review tab, verify all the details.
77. Click Start recovery to restore the files.
78. After starting the recovery, you will be redirected to the Restore activity tab. You can monitor a job's
progress in this tab.

Select a specific Job ID to view its details.

79. Alternatively, you can also check the Activity monitor to view job progress.
80. View the Job Details of this job, and verify that the job completes successfully (status 0).

If the job completes successfully, continue to the next step.

81. Minimize the NetBackup web user interface.

Verifying the Restored files and folders

In the following steps, you verify the restored files and folders on the lnxvm3 virtual machine.

82. On the desktop of console.vrtsedu.lab, double-click the PuTTY shortcut.

83. Double-click the entry for lnxvm3.vrtsedu.lab.
84. Log in to the lnxvm3.vrtsedu.lab system using the following credentials.
o Username: root
o Password: P@ssw0rd

85. Navigate to /tmp/restore directory using cd /tmp/restore command.

86. In the /tmp/restore directory list the files and folders using ls -l command.
87. Verify the contents of the restored files and folders from /tmp/restore/data directory.
88. After verifying the contents, minimize the PuTTY window.
Lab Part C: Performing Instant Recovery for VMware (Windows and
Linux)

Exercise A: Performing Non-NetBackup Pre-requisite Tasks for IRV

There are several preliminary non-NetBackup tasks that must be performed in a production NetBackup
environment to enable the Instant Recovery for VMware (IRV) feature.

These tasks have been pre-performed in this lab environment. However, the tasks are documented in this lab
guide for your reference.

While the non-NetBackup steps described in the exercise have been pre-performed for your convenience, it is
important to understand that the steps are NOT OPTIONAL. These steps must be performed in a production
NetBackup environment, to enable the use of the NetBackup Instant Recovery for VMware feature.

There are four primary non-NetBackup requirements to enable the use of the NetBackup Instant Recovery for
VMware (IRV) feature in this lab environment:

 Adding the Web Server (IIS) role on the console.vrtsedu.lab system.

 Installing Java on the console.vrtsedu.lab system.
 Adding the Network File System (NFS) role on the Windows-based NetBackup master
server, winmaster.vrtsedu.lab. (This step is only required on Windows-based NetBackup servers that are
acting as the recovery host for Instant Recovery for VMware (IRV) operations, and/or on any Windows-
based NetBackup server that holds the virtual machine backup image that will be used during an Instant
Recovery operation.)
 Enabling vMotion on the ESX Server (esx1.vrtsedu.lab)

The tasks listed above have been pre-performed in this lab environment.

 If you are not interested in reviewing the detailed steps to perform the non-NetBackup pre-requisite tasks,
click the link to skip to Exercise B: Performing NetBackup pre-requisite tasks for IRV.
 Click the link to view the steps in Exercise X: Detailed non-NetBackup prerequisite steps to enable Instant
Recovery for VMware (IRV).

Exercise B: Performing Instant Recovery for VMware Using the vSphere Web
Client

In this exercise, you use the NetBackup Instant Recovery for VMware (IRV) feature of the NetBackup plug-in for
vSphere Web Client to recover a VMware virtual machine. After recovering the virtual machine to a NetBackup-
provided NFS datastore,
VMware vMotion is used to migrate the recovered virtual machine from the NFS datastore on the NetBackup
server to a 'production' datastore on the esx1.vrtsedu.lab virtual machine server.

Deleting the lnxvm1 VM from the ESX Server

In the steps that follow, you delete the lnxvm1 virtual machine from the ESX Server in preparation for recovering it
using the NetBackup Instant Recovery for VMware feature.

1. In the vSphere Web Client, click vSphere Client.

2. From the Shortcuts>Inventories, select Hosts and Clusters.
3. In the left-pane, navigate to 10.10.2.99 > DC1 > esx1.vrtsedu.lab.
4. If the lnxvm1 virtual machine is not powered-off, in the vSphere Web Client's navigation pane, right-click
the virtual machine lnxvm1, and select Power > Power Off.
5. In the Confirm Power Off window that is displayed, Click YES to power off the virtual machine.
6. Right-click the virtual machine lnxvm1, and select the Delete from Disk entry in the menu.

VMware only allows the deletion of virtual machines that are powered off.

7. When the Confirm Delete dialog box is displayed, click the YES to confirm the delete operation.
8. Verify that the entry for the lnxvm1 virtual machine is no longer visible in the left pane of the vSphere
Web Client.

Using Instant Recovery for VMware (IRV) to recover a VM

In the steps that follow, you use the NetBackup Instant Recovery for VMware (IRV) feature to recover a VMware
virtual machine.

 Instant Recovery for VMware enables a NetBackup backup image of a VMware virtual machine to be
mounted on NFS data storage on a NetBackup media server.
 The NFS datastore is viewed as a temporary datastore by a VMware ESX Server. When the backup image is
mounted on the NFS datastore it is a fully-functional virtual machine.
 As a second operation, VMware vMotion can be used to move (migrate) the virtual machine to a
permanent datastore on the ESX Server, thus completing the recovery of the virtual machine.

9. In the vSphere Web Client select Menu > Veritas NetBackup.

10. Enter the following credentials (if required) in the Veritas NetBackup plug-in page and click LOGIN.
o Select a NetBackup primary server : lnxmaster.vrtsedu.lab
o Username: root
o Password: P@ssw0rd
11. Veritas NetBackup Recovery Wizard is displayed.
12. Scroll down and then click the RUN RECOVERY WIZARD button.
13. In the Recovery Wizard, on the Virtual Machine Selection screen, perform the following actions:
a. Select the VMware Server : 10.10.2.99 (auto populates.)
 b. Type lnxvm1 in the Search field and click SEARCH.
c. In the Search results, entry of one virtual machine is found.
d. Select lnxvm1 and then click NEXT.
14. On the Recovery Points screen, the latest available backup is displayed.

If you see the No IR ready image in last 7 days, then change the From Date to 01/01/2021 and
click SEARCH RECOVERY POINTS.

15. Under the Recovery options, select the option Instant virtual machine recovery and click NEXT.
16. On the Recovery Target screen, accept the default values and click NEXT.
17. On the Recovery Options screen, deselect the Power on after recovery checkbox. Do not make any
other changes and click NEXT.
18. On the Review Instant Virtual Machine Recovery section screen, click the RUN PRE-RECOVERY
CHECK button to start a pre-recovery check.
19. Wait for the check to complete. Scroll down to view the results.
20. Click the START RECOVERY button. Recovery Job Initiated message is displayed. Read the message and
click OK.
21. Allow the vSphere Web Client window to remain open on console.vrtsedu.lab.

Viewing the Instant Recovery jobs

In the steps that follow, you access the NetBackup Administration Console to view the jobs that were initiated as
a result of the Instant Recovery of the VMware virtual machine.

It has been intermittently observed that after resuming a lab, the IRV job fails with error "Restore failed completely
(5)." If you receive the same error, reboot esx1.vrtsedu.lab to initiate the IRV job once again.

22. Access the NetBackup WebUI.

23. Select the Activity Monitor entry from the left pane.

Two jobs have been created as a result of Instant Recovery.

o VM Instant Recovery
o Activate Instant Recovery

24. Monitor the jobs until the Activate Instant Recovery job is completed successfully.

The recovered virtual machine (lnxvm1, in this case) is ready for use as soon as the Activate Instant
Recovery job is done. The VM Instant Recovery job remains in the Active state until a deactivation or
completion request is received.

25. Access the open vSphere Web Client window on console.vrtsedu.lab, and click the Menu button.
26. Click Inventory.
27. In the left-pane, expand the tree to show the entries under Datacenter1 > esx1.vrtsedu.lab
 The lnxvm1 virtual machine is now visible.

28. In the left-pane, click the entry for lnxvm1.

Details about the lnxvm1 VM are displayed. The VM is powered off, due to the options selected in
the Instant Recovery wizard.

29. Click the Datastores tab, to locate the temporary datastore to which the lnxvm1 VM was restored.

The lnxvm1 VM was restored to datastore2 .

Using VMware vMotion to migrate the recovered VM to another datastore on the ESX Server

In the steps that follow, you use VMware vMotion to migrate the virtual machine lnxvm1, from the temporary
datastore to a production datastore on the ESX Server, esx1.vrtsedu.lab.

32. On the console.vrtsedu.lab system, access the open vSphere Web Client window
33. In the left-pane, select the lnxvm1 VM and click the Summary tab in the right-pane.

Details about the lnxvm1 VM are displayed. The VM is powered off, due to the options selected in
the Instant Recovery wizard. In addition, note the storage that lnxvm1 is using.

34. Right-click the entry for lnxvm1 and from the menu, click Migrate.

The lnxvm1 - Migrate screen is displayed.

35. In the Select a migration type screen, click the Change storage only radio button.

This allows you to move the virtual machine's storage to another datastore.

36. In the Select a migration type screen, click NEXT.

The virtual machine is currently resident on a datastore provided by an NFS mount from the media server that
was used to back up the virtual machine. This operation moves the virtual machine to a production datastore
on the ESX Server.

37. From the Select storage screen, select datastore1.

When you select the datastore, VMware checks the compatibility of the virtual machine to the new datastore.

38. When the compatibility checks are completed successfully, click NEXT to continue.

The Ready to complete screen is displayed.

39. Review the information on the Ready to complete screen, and then click FINISH.
40. Click lnxvm1 and then click the Monitor tab.
41. Under Tasks and Events, click Tasks and monitor the Relocate virtual machine task.

The relocation task might take 10-15 minutes to complete. Wait until this task is complete. If the progress of
the Relocate virtual machine task is not updated automatically, click the refresh button located on the top
bar to refresh the page.

42. After the relocation task is complete, click the Summary tab.
43. On the Summary tab, if the Virtual machine Consolidation message is displayed for lnxvm1,
click Acknowledge.
44. Right-click lnxvm1 and select Snapshots > Consolidate.

The Consolidate window is displayed.

45. On the Consolidate | lnxvm1, click OK to confirm the consolidation.

46. Click the Refresh icon on the grey banner bar to refresh the screen.

Verify that the lnxvm1 virtual machine no longer has a disk consolidation warning message associated with
the virtual host.

47. Review the Related Objects section on the Summary tab.

The lnxvm1 virtual machine is now located on datastore1.

Ending the Instant Recovery for VMware session

In the steps that follow, you terminate the IRV session and the VM backup image is un-mounted from the NFS disk
volume.

55. On console.vrtsedu.lab, open the vSphere Web Client, if not already open.
56. Click the Menu icon, and then select Veritas NetBackup.
57. Click the Instant Recovery Cleanup tab.

The Instant Recovery details page is displayed.

58. On the Instant Recovery details page, select the Instant Recovery Cleanup sub-tab.
59. Scroll down to the Active Instantly Recovered Virtual Machines section and select lnxvm1 virtual
machine.
60. Click the Initiate Instant Recovery Done button and click Yes in the Veritas NetBackup dialog box to
continue.
61. In the Veritas NetBackup dialog box, click OK.
Verifying the end of the Instant Recovery jobs

In the following steps, you verify that the jobs that were initiated to perform the Instant Recovery of the VMware
VM, and to clean up the Instant Recovery jobs, have been completed.

62. In the NetBackup WebUI, click the Activity Monitor entry in the left-pane, if necessary.
63. Note that a Stop Instant Recovery job is displayed and is in the Done state. Also, the Activate Instant
Recovery and VM Instant Recovery jobs, created earlier, have completed successfully.

Exercise X: Detailed non-NetBackup prerequisite steps to enable Instant Recovery for VMware
(IRV)

The detailed procedures provided on this and the following are required pre-requisite steps to enable the
NetBackup Instant Recovery for VMware (IRV) feature.

While these steps are required to enable in a NetBackup environment, they have been pre-performed in this lab
environment, but are documented here for your reference.

There are four primary non-NetBackup requirements to enable the use of the NetBackup Instant Recovery for
VMware (IRV) feature:

 Adding the Web Server (IIS) role on the console.vrtsedu.lab

 Enabling vMotion on the ESX Server

To skip the non-NetBackup prerequisite details (which have been pre-performed in this lab environment) and
return to the required tasks of this lab activity, click the link to go to Exercise B: Performing NetBackup prerequisite
tasks for IRV.

Continue to the following steps to view the detailed non-NetBackup prerequisite procedures.

Adding the Web Server IIS role on console vrtsedu lab

These steps have been pre-performed on the console.vrtsedu.lab system in this lab environment. There is no
requirement for you to perform the steps. The following procedure is provided for your reference only.

The steps that follow document the installation of the Web Server (IIS) role on the console.vrtsedu.lab system.

1. Access the desktop of console.vrtsedu.lab.

 💻 console.vrtsedu.lab UserID: VRTSEDU\Administrator Password: P@ssw0rd

2. Log in to console.vrtsedu.lab (if necessary) using the credentials shown above.

3. Click the Windows button located on the left end of the Windows task bar.
4. Click Server Manager.

5. In the Server Manager window, click Add roles and features.

6. In the Before you begin screen, click Next, if displayed.

7. In the Installation Type, verify the radio button for Role-based or feature-based installation is selected.

8. In the Server Selection screen, verify console.vrtsedu.lab is listed in the Server Pool pane.

9. In the Server Roles screen, click the check box next to the Web Server (IIS) entry.

10. In the Add Roles and Features Wizard click the Add Features button.

11. Click the Next button on the Select Server Roles screen.
12. In the Features screen, click Next.
13. When the Web Server (IIS) screen is displayed, click Next.
14. When the Select Role Services screen is displayed, click Next without making any changes to the screen
contents.
15. When the Confirm Installation Services window is displayed, click the Install button, to begin the
installation.
16. Monitor the progress of the installation in the Installation Progress screen.
 Note: The installation of the Web Server (IIS) will take a few minutes to complete.

17. Verify that an "Installation succeeded" message is displayed.

18. Click the Close button to close the Add Roles Wizard screen.
19. Close the Server Manager window on console.vrtsedu.lab.

You have completed the installation of the Web Server (IIS) role on console.vrtsedu.lab.

Continue to the Install JAVA on console.vrtsedu.lab steps or return to the Summary of non-NetBackup pre-
requisite tasks.

OR

Click the link to skip the remainder of the non-NetBackup prerequisite task details and go to Exercise E:
Performing NetBackup prerequisite tasks for IRV

Enabling vMotion on the ESX Server

As described by VMware, Storage vMotion is a component of VMware vSphere that allows the live migration of a
running virtual machine\'s file system from one storage system to another, with no downtime for the VM or service
disruption for end users.

As related to NetBackup's Instant Recovery for VMware (IRV) feature, vMotion can be used by a VMware
administrator to move a recovered virtual machine from a NetBackup-provided NFS datastore (to which the VM
was recovered) to a production VMware datastore. Storage vMotion is enabled in the VMware ESX Server.

These steps have been pre-performed on the VMware ESX Server, esx1.vrtsedu.lab, system in this lab
environment. There is no requirement for you to perform the steps. The procedure is provided below for your
reference only.

1. Access the desktop of console.vrtsedu.lab.

💻 console.vrtsedu.lab Username: VRTSEDU\Administrator Password: P@ssw0rd

2. Log in to console.vrtsedu.lab (if necessary) using the credentials shown above.

3. Locate and double-click the vSphere Web Client shortcut, located on the desktop
of console.vrtsedu.lab, to launch the vSphere Web Client in a Firefox browser window.
4. When the vSphere Web Client log screen is displayed, enter the
Username, vsphere.local\Administrator, and the Password, P@ssw0rd, and click Login.
5. When the vSphere Web Client user interface is displayed, click the Menu located on the top bar.
 6. Click Hosts and Clusters in the resulting menu to navigate to the Hosts and Clusters view.
7. In the left pane, expand the DC1 (data center) entry then select esx1.vrtsedu.lab.
8. Select the Configure tab and then under Networking click VMkernel adapters.
9. Click the entry for the vmk0 device then click the Edit Settings icon (the pencil icon).
10. In the resulting vmk0 -- Edit Settings window, in the Available services settings, click to mark the check
box for the vMotion parameter.
11. Click OK to save the setting changes, and to close the vmk0 -- Edit Settings window.

You have enabled the vMotion feature on the ESX Server, esx1.vrtsedu.lab.

12. Allow the vSphere Web Client window to remain open on console.vrtsedu.lab. You use this window in
the next section of this lab activity.
13. Click the link to return to the Summary of non-NetBackup pre-requisite tasks.

OR

Click the link to go to Exercise E: Performing NetBackup prerequisite tasks for IRV.

Lab 12: Duplicating and Replicating Backups

Exercise A: Configuring a Storage Lifecycle Policy

In this exercise, you configure a Storage Lifecycle Policy (SLP) to perform three operations:

 A backup to MSDP storage. The backup images created by the backup operation are retained for one
month.
 A backup to AdvancedDisk storage. The backup images created by this backup operation are retained
until they have been successfully duplicated to cloud storage, and are then deleted.
 A duplication of the second backup image to cloud storage. The copies of the backup images that are
written to cloud storage are retained for three (3) months.

Creating a Storage Lifecycle Policy

In the steps that you follow, you create a Storage Lifecycle policy.

1. Sign in to the console system using the following credentials.

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd
2. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system to
launch the NetBackup web user interface.

The Netbackup web user interface can be accessed by navigating to the following URL: https://master server
hostname or IP/webui/login. For the purpose of this lab, a web shortcut is preconfigured for accessing the
NetBackup web user interface.

3. If a security warning is displayed, click Advanced > Accept the Risk and Continue.
4. Sign in to the NetBackup web user interface using the following credentials.
o Username: root
o Password: P@ssw0rd

5. In the NetBackup web user interface, in the left navigation pane, go to Storage > Storage lifecycle
policies.

The lists of currently configured Storage lifecycle policies are displayed on the Storage lifecycle policies
page under the Storage lifecycle policies tab.

No Storage lifecycle policies are currently configured.

6. In the Storage lifecycle policies tab, click Add to add a new Storage lifecycle policy.

The Storage lifecycle policy page is displayed.

7. Enter the information provided in the table below on the Storage lifecycle policy page.

Storage Lifecycle Policy Parameter Value

Storage lifecycle policy name OnPrem_to_Cloud

Data classification no data classification (default)

Priority for secondary operations 0 (default)

State of secondary operation processing Active (default)

Adding the first operation to the SLP

In the steps that you follow, you add the properties for the first operation to be performed by the new Storage
Lifecycle Policy.
8. Click the Add button to add the first operation to the SLP.

The New operation page is displayed.

9. Enter the information provided in the table below to complete the configuration of the first storage
operation for the SLP.

New operation properties Value

Operation Backup (Default setting)

Destination storage master_msdp_stu (change this setting)

Volume pool n/a

Media owner n/a

Retention type Fixed (Default setting)

Retention period 1 month (Retention Level 3) (change this setting)

10. Click Create to create the first operation to the SLP.

Verify that the Backup operation entry is added to the Operation list of the OnPrem_to_Cloud Storage
Lifecycle Policy.

Adding the second operation to the SLP

In the steps that you follow, you add the properties for the second operation to be performed by the new Storage
Lifecycle Policy.

11. On the Storage lifecycle policies page, click the Add button to add the second operation to the SLP.
12. Use the information in the table below to configure the second SLP operation.

New operation properties Value

Operation Backup (Default setting)

 New operation properties Value

Destination storage master_advdisk_stu

Volume pool n/a

Media owner n/a

Retention type Expire after copy (change this setting)

13. Click Create to create the second operation to the SLP.

Verify that the second Backup operation entry is added to the Operation list of
the OnPrem_to_Cloud Storage Lifecycle Policy.

The left margins of the first and second Backup operation entries are aligned, as illustrated in the illustration
below. This orientation indicates that the operations are independent of one another.

Adding the third operation to the SLP

In the steps that you follow, you add the properties for the third operation to be performed by the new Storage
Lifecycle Policy.

14. Click the entry for the second Backup operation entry in the SLP, to highlight the entry.
 Verify that the entry for the second Backup operation is highlighted.

15. Click the Actions (ellipsis button) and select Add child to add a child operation to the
second Backup operation.

The New operation page is displayed.

16. Use the information provided in the table below to complete the configuration of the third SLP operation.

New operation properties Value

Source storage master_advdisk_stu (Backup)

Operation Duplication (default)

Destination storage media_cloud_stu (change this setting)

Volume pool NetBackup (default)

Media owner Any (default)

Retention type Fixed (default)

3 months (Retention Level 5) (change this

Retention period
setting)

Alternate read server None (default)

Preserve multiplexing Not selected(default)

Postpone creation of this copy until the source is about

Not selected (default)
to expire

17. In this lab environment, the MinIO application is installed and configured on the cloud1 system and is used
to simulate cloud storage.
18. Click Create to create the third operation to the SLP.
 Verify that the Duplication operation entry is added to the Operation list of the OnPrem_to_Cloud Storage
Lifecycle Policy.

This figure illustrates the OnPrem_to_Cloud SLP with three operations included.

The left margin of the Duplication operation is indented from the entry for the second Backup operation, as
illustrated in the figure above, indicating that the Duplication operation is derived from the
second Backup operation.

19. Click Create to create the OnPrem_to_Cloud Storage Lifecycle Policy.

Successfully added storage lifecycle policy message is displayed.

20. Verify that entry for the OnPrem_to_Cloud storage lifecycle policy is visible in the list of SLPs that is
displayed in the right pane of the NetBackup web user interface.

Exercise B: Configuring a Policy to Use a Storage Lifecycle Policy

In this exercise, you configure a policy that uses the OnPrem_to_Cloud SLP to automatically perform the
operations specified in the SLP.

1. Error! Not a valid embedded object.In the NetBackup web user interface, in the left navigation pane,
click Protection > Policies.
2. Error! Not a valid embedded object.On the Policies page, click Add to create a new policy.

The Create policy page is displayed.

3. Error! Not a valid embedded object.Use the information provided in the table below to configure the
policy Attributes settings.

Attributes parameter Value

Policy name OnPrem_to_Cloud_Policy

Policy type MS-Windows

Policy storage OnPrem_to_Cloud (Storage lifecycle policy) (change this setting)

All other policy attributes Use default settings -- do not change

4. Click the Schedules tab on the Create policy page.

5. In the Schedules tab, under Backup schedules click Add.

The Add schedule window is displayed.

6. Error! Not a valid embedded object.Configure the Schedule Attributes using the information provided in
the table below.

Schedule parameter Value

Schedule name Full_slp

Type of Backup Full Backup (default)

Calendar Not selected (default)

Frequency 1 week (default)

Override policy storage selection Not checked (default)

Media multiplexing 1 (default)

7. Error! Not a valid embedded object.In the Add Schedule window, click Add to add the Full_slp schedule.

No start window has been set up for this schedule. Only manual backups can be run using this schedule.

8. Error! Not a valid embedded object.Verify that the entry for the Full_slp schedule is displayed in
the Backup schedules tab.
9. Click the Clients tab on the Create policy page.
10. Click Add to add a client to the policy.
11. In the Add client - Policy OnPrem_to_Cloud_Policy dialog box use the following values.
o Client name - console.vrtsedu.lab
o Detect client operating system - Mark the check box

12. Click Add to add the console.vrtsedu.lab client to the Clients list for this policy.
13. Verify that an entry for console.vrtsedu.lab is added to the Clients tab.
14. Click the Backup Selections tab on the Create policy page.
15. Click Add to add the desired backup selection to the policy.
16. In the Add backup selection dialog box, click the folder icon present under Pathname or
directive section.
17. In the left pane of the directory structure navigate to E:\data\ directory.
18. Select the smallfiles directory in the right pane and click Add.
19. Verify that the E:\data\smallfiles entry is displayed in the List of pathnames and directives to add to
the selection list.
20. Click Add to add the selected path to the Backup selection list.
21. Click Create to save the OnPrem_to_Cloud_Policy policy.
22. Verify that the OnPrem_to_Cloud_Policy policy is included in the list of policies displayed on
the Policies page of the NetBackup web user interface.

Exercise C: Customizing Storage Lifecycle Policy Settings

In this exercise, you customize different SLP settings, located under Storage > Storage lifecycle policies in
the NetBackup web user interface.

The SLP settings in the NetBackup web user interface allow administrators to customize how storage lifecycle
policies are maintained and how SLP jobs run. The properties apply to the SLPs of the currently logged in Primary
Server.

1. In the NetBackup web user interface, in the left navigation pane, click Storage > Storage lifecycle
policies.
2. In the Storage lifecycle policies page, click SLP settings present on the top right corner.

The SLP settings page displays the default values for all Storage Lifecycle Property.
 To save time in this lab activity, you customize some of the Storage Lifecycle Property values to minimize
the wait time that would normally occur between the Backup and automatic Duplication operations
(controlled by the Storage Lifecycle Policy).

3. Select the Value entry for the Force interval for small job parameter, and modify the value to 10
(seconds).

The default setting for the Force interval for small job is 30 minutes. This parameter prevents small
duplication jobs from running too frequently.

4. Select the Value entry for the Job Submission Interval parameter, and modify the value to 10 (seconds).

The default setting for the Job Submission Interval parameter is 5 minutes. This parameter controls how
often SLP processing jobs are submitted for execution.

5. Select the Value entry for the Image processing interval parameter, and modify the value to 10
(seconds).

The default setting for the Image processing interval parameter is 5 minutes. This parameter controls how
often new SLP-managed images are recognized and set up for SLP processing.

6. Click Save to save the Storage Lifecycle Property changes.

Successfully updated the SLP settings message is displayed.

Exercise D: Viewing and Monitoring Storage Lifecycle Policy Operations

In this exercise, you use the OnPrem_to_Cloud_Policy policy to initiate the operations indicated in
the OnPrem_to_Cloud Storage Lifecycle Policy. Then, you monitor the SLP operations using the
NetBackup Activity monitor.

Performing a manual backup that uses an SLP

1. In the NetBackup web user interface, in the left navigation pane, click Protection > Policies.
2. In the Policies page, mark the check box present on the left side of the policy
name OnPrem_to_Cloud_Policy, then select Manual Backup.
3. Click OK button in the Manual backup window without making any other selections, to initiate the manual
backup operation.

Successfully sent backup request message is displayed.

4. Select the Activity monitor in the left pane of the NetBackup Web UI.

Note the most recent job entries in the Activity monitor that use the OnPrem_to_Cloud_Policy policy.

5. View the Jobs tab of the Activity monitor and take note of the number of jobs that are added as a result
of the manual backup operation that you initiated.

you see three Backup jobs for the policy OnPrem_to_Cloud_Policy.

6. Verify that all the jobs run to successful completion. If one or more of the jobs fails, record the status code
or status codes and seek assistance.
7. View the Job Details for each of the jobs that resulted from the manual backup of
the OnPrem_to_Cloud_Policy policy.
8. To view Job Details for a job, click on the Job ID for the respective job and then select the Details tab
and take note of the following.

Initially, three jobs using the OnPrem_to_Cloud_Policy policy are displayed.

The first job is a parent Backup job. The next two jobs are child Backup jobs that perform the backup
operations specified in the OnPrem_to_Cloud SLP.

All three (3) of the initial jobs that use the OnPrem_to_Cloud_Policy policy have a Job Type of Backup.

The first child Backup job uses the master_msdp_stu storage unit.

The second child Backup job uses the master_advdisk_stu storage unit.

A few minutes after the Backup jobs run to completion, a Duplication job is run using
the media_cloud_stu storage unit.

9. Allow the Duplication job to run to completion, and then wait another few minutes.

You should find that an Image Cleanup job has now run.

10. View the Job Details of the Image Cleanup jobs that ran soon after the completion of
the Duplication job.
11. In the Job Details tab of the Image Cleanup job, take note of the disk volume that is identified, and the
activity that is being performed on that disk volume.

One task performed by the Image Cleanup job (that ran after the completion of the Duplication job) was to
expire and delete the backup image that had been written to the master_advdisk_stu by the second
child Backup job (controlled by the SLP). This image was duplicated from the master_advdisk_stu to
the media_cloud_stu during the Duplication operation (under the control of the SLP). The Retention of the
backup image of the second Backup operation (in the SLP) was set to Expire after copy. This retention
 setting caused the backup image to be expired and then be deleted from the master_advdisk_stu storage
unit after the successful duplication of the backup image.

The Duplication job was initiated within a few minutes after the backup jobs were completed. By default,
NetBackup uses the SLP settings parameters configured in Primary Server to determine the interval at which
the SLP manager process is called. The SLP manager looks for images to be duplicated and
initiates Duplication jobs as needed. To save time in this lab environment, the interval was changed to 10
seconds in an earlier lab exercise.

12. Close any open Job Details windows in the Activity monitor.

SLP operations summary

The following jobs were initiated by the OnPrem_to_Cloud_Policy policy, using the operations defined in
the OnPrem_to_Cloud Storage Lifecycle Policy (SLP):

 A parent Backup job.

o This job controlled two child Backup jobs.
o The first child Backup job ran under the control of the OnPrem_to_Cloud Storage Lifecycle Policy
and wrote a backup image to master_msdp_stu.
o The second child Backup job ran under the control of the OnPrem_to_Cloud Storage Lifecycle
Policy and wrote a backup image to the master_advdisk_stu. The Retention of this backup image
was set to Expire after copy.
 A Duplication job.
o This job was initiated a few minutes after the completion of the Backup operations that were
initiated by the SLP (OnPrem_to_Cloud).
o The Storage Lifecycle Property, Image processing interval, determines how often NetBackup
calls its Duplication Manager process, to look for backup images to be processed, and the Force
interval for small job Storage Lifecycle Property sets the minimum wait time that must elapse
before a small duplication or replication job can be submitted.
o The Duplication job caused the duplication of the backup image or backup images created by the
second child Backup job to be duplicated from
the master_advdisk_stu to media_cloud_stu (specified in the SLP operations).
 After the Duplication job was completed, an Image Cleanup job was initiated.
o This job performs all backup image cleanup due at the time that the job is initiated.
o The Image Cleanup job was not specifically related to the jobs that were performed by the SLP.
Because the Retention that was set in the second Backup operation of the SLP was Expire after
copy, as soon as the backup image was successfully duplicated during the Duplication job, the
source backup image (on the master_advdisk_stu) was marked for cleanup.
o When the Image Cleanup job was called, it expired and then deleted the backup image from the
NetBackup image catalog, and the master_advdisk_stu disk volume.
Exercise E: Using Storage Lifecycle Policies to Perform MSDP Optimized
Duplication

In this exercise, you configure a Storage lifecycle policy (SLP) to perform MSDP optimized duplication.

Performing preliminary tasks

In the steps that you follow, you add the source Media Server to the list of target storage server Media Server list.

For optimized Media Server Deduplication Pool duplication within the same domain, the source storage and the
destination storage must have at least one Media Server in common. The common server initiates, monitors, and
verifies the duplication operation. The common server requires credentials for both the source storage and the
destination storage. (For deduplication, the credentials are for the NetBackup Deduplication Engine, not for the
host on which it runs.)

1. In the lnxmaster.vrtsedu.lab NetBackup web user interface, in the left navigation pane, click Storage >
Storage configuration

Lists of configured Storage servers are displayed.

2. On the Storage configuration page, click the last entry for lnxmedia.vrtsedu.lab which has
the Category value as MSDP.
3. In the lnxmedia.vrtsedu.lab storage server page, scroll down to Media servers section, and click Add.
4. In the Select media servers dialog box, select the entry for lnxmaster.vrtsedu.lab and click Add.

Successfully updated lnxmedia.vrtsedu.lab storage server message is displayed.

In this lab activity, lnxmaster.vrtsedu.lab is acting as source storage server and common Media
Server. lnxmedia.vrtsedu.lab is the target storage server. By adding the lnxmaster.vrtsedu.lab to the target
storage server Media Server list, it will have the credentials for both the source storage and the destination
storage to perform the MSDP optimized duplication.

5. Verify that the lnxmaster.vrtsedu.lab is added to the Media servers list of

the lnxmedia.vrtsedu.lab storage server page.
6. Click the close icon to close the lnxmedia.vrtsedu.lab storage server page.

Creating a Storage Lifecycle Policy

In the steps that you follow, you create a Storage Lifecycle policy.

7. In the NetBackup web user interface, in the left navigation pane, go to Storage > Storage lifecycle
policies.
 The lists of currently configured Storage lifecycle policies are displayed on the Storage lifecycle policies
page under the Storage lifecycle policies tab.

8. In the Storage lifecycle policies tab, click Add to add a new Storage lifecycle policy.

The Storage lifecycle policy page is displayed.

9. Enter the information provided in the table below on the Storage lifecycle policy page.

Storage Lifecycle Policy Parameter Value

Storage lifecycle policy name Opt_Dup

Data classification no data classification (default)

Priority for secondary operations 0 (default)

State of secondary operation processing Active (default)

Adding the first operation to the SLP

In the steps that you follow, you add the properties for the first operation to be performed by the new Storage
Lifecycle Policy.

10. Click the Add button to add the first operation to the SLP.

The New operation page is displayed.

11. Enter the information provided in the table below to complete the configuration of the first storage
operation for the SLP.

New operation properties Value

Operation Backup (Default setting)

Destination storage master_msdp_stu (change this setting)

 New operation properties Value

Volume pool n/a

Media owner n/a

Retention type Fixed (Default setting)

Retention period 1 month (Retention Level 3) (change this setting)

12. Click Create to create the first operation to the SLP.

Verify that the Backup operation entry is added to the Operation list of the Opt_Dup Storage Lifecycle
Policy.

Adding the second operation to the SLP

In the steps that you follow, you add the properties for the second operation to be performed by the new Storage
Lifecycle Policy.

13. Click the entry for the first Backup operation entry in the SLP, to highlight the entry.

Verify that the entry for the first Backup operation is highlighted.

14. Click the Actions (ellipsis button) and select Add child to add a child operation to the
first Backup operation.

The New operation page is displayed.

15. Use the information provided in the table below to complete the configuration of the second SLP
operation.

New operation properties Value

Source storage master_msdp_stu (Backup)

Operation Duplication (default)

 New operation properties Value

Destination storage media_msdp_stu (change this setting)

Volume pool NetBackup (default)

Media owner Any (default)

Retention type Fixed (default)

3 months (Retention Level 5) (change this

Retention period
setting)

Alternate read server None (default)

Preserve multiplexing Not selected(default)

Postpone creation of this copy until the source is about

Not selected (default)
to expire

16. In this lab environment, MSDP storage is configured on

the lnxmaster.vrtsedu.lab and lnxmedia.vrtsedu.lab servers. Optimized duplication relies on the source and
target storage supporting each other, which in most cases means the technologies must be identical.
17. Click Create to create the second operation to the SLP.

Verify that the Duplication operation entry is added to the Operation list of the Opt_Dup Storage Lifecycle
Policy.

This figure illustrates the Opt_Dup SLP with two operations included.
 The left margin of the Duplication operation is indented from the entry for the first Backup operation, as
illustrated in the figure above, indicating that the Duplication operation is derived from the
first Backup operation.

18. Click Create to create the Opt_Dup Storage Lifecycle Policy.

Successfully added storage lifecycle policy message is displayed.

19. Verify that entry for the Opt_Dup storage lifecycle policy is visible in the list of SLPs that is displayed in
the right pane of the NetBackup web user interface.

Configuring a policy to use an SLP

In the steps that you follow, you configure a policy that uses the Opt_Dup SLP to automatically perform the
operations specified in the SLP.

19. In the NetBackup web user interface, in the left navigation pane, click Protection > Policies.

The policies that are currently configured are listed on the Policies page.

20. Select the check box for the OnPrem_to_Cloud_Policy policy and select Copy policy.
21. In the Copy policy dialog box type Opt_Backup in the New policy field, then click Copy to create a new
policy.
22. After the policy is created you can see the Opt_Backup policy in the Policies pane.
23. Select the check box for the Opt_Backup policy and click Edit to edit the policy.

The Edit policy - Opt_Backup page is displayed.

24. In the Edit policy - Opt_Backup page, click the Attributes tab.
25. In the Attributes tab, change the Policy storage to the newly created SLP Opt_Dup (Storage lifecycle
policy).

Leave all the policy settings to their default values.

26. Click Save to save the policy.

27. Verify that the Opt_Backup policy is included in the list of policies displayed on the Policies page of the
NetBackup web user interface.

Performing a manual backup that uses an SLP

In the steps that you follow, you perform a manual backup of the policy Opt_Backup.

28. In the NetBackup web user interface, in the left navigation pane, click Protection > Policies.
29. In the Policies page, mark the check box present on the left side of the policy name Opt_Backup, then
select Manual Backup.
30. Click OK button in the Manual backup window without making any other selections, to initiate the manual
backup operation.

Successfully sent backup request message is displayed.

31. Select the Activity monitor in the left pane of the NetBackup Web UI.

Note the most recent job entries in the Activity monitor that use the Opt_Backup policy.

32. View the Jobs tab of the Activity monitor and take note of the number of jobs that are added as a result
of the manual backup operation that you initiated.

You see only one Backup job for the policy Opt_Backup.

33. Verify that the job runs to successful completion. If the jobs fail, record the status code or status codes
and seek assistance.
34. View the Job Details for the job that resulted from the manual backup of the Opt_Backup policy.
35. To view Job Details for a job, click on the Job ID for the respective job and then select the Details tab
and take note of the following.

The backup job performs the backup operation on the master_msdp_stu storage unit specified in
the Opt_Dup SLP.

A few minutes after the Backup job run to completion, a Duplication job is run using
the media_msdp_stu storage unit.

36. Allow the Duplication job having Policy name as SLP_Opt_Dup to run to completion.
37. View the Job Details of the Duplication job having Policy name as SLP_Opt_Dup that ran soon after the
completion of the Opt_Backup policy Backup job.
38. In the Job Details tab of the Duplication job, take note of the message Initiating optimized duplication.

The Duplication job was initiated within a few minutes after the backup jobs were completed. By default,
NetBackup uses the SLP settings parameters configured in Primary Server to determine the interval at which
the SLP manager process is called. The SLP manager looks for images to be duplicated and
initiates Duplication jobs as needed. To save time in this lab environment, the interval was changed to 10
seconds in an earlier lab exercise.

The Actual job will have different values for Job id, date, and time.

39. Close any open Job Details windows in the Activity monitor.

SLP operations summary

The following jobs were initiated by the Opt_Backup policy, using the operations defined in the Opt_Dup Storage
Lifecycle Policy (SLP):

 A Backup job.
o The Backup job ran under the control of the Opt_Dup Storage Lifecycle Policy and wrote a backup
image to master_msdp_stu.
 A Duplication job.
o This job was initiated a few minutes after the completion of the Backup operations that were
initiated by the SLP (Opt_Dup).
 o The Storage Lifecycle Property, Image processing interval, determines how often NetBackup
calls its Duplication Manager process, to look for backup images to be processed, and the Force
interval for small job Storage Lifecycle Property sets the minimum wait time that must elapse
before a small duplication or replication job can be submitted.
o The Duplication job caused the duplication of the backup image or backup images created by
the Backup job to be duplicated from the master_msdp_stu to media_msdp_stu (specified in the
SLP operations).
o The Duplication job Details tab provides a clear indication that the duplication job was optimized
duplication.

Exercise F: Configuring Storage Lifecycle Policies for Replicating Backup Images

In this exercise, you configure the Storage lifecycle policy to replicate the backup image from one NetBackup
Domain to another NetBackup Domain

Configuration notes

 Two NetBackup Domains have been configured.

 Source NetBackup Domain contains lnxmaster.vrtsedu.lab [Primary Server]
and lnxmedia.vrtsedu.lab [Media Server].
 Target Netbackup Domain contains winmaster.vrtsedu.lab [Primary Server]
and winmedia.vrtsedu.lab [Media Server].
 All the required storage servers, disk pools, and storage units have been pre-configured in both the
NetBackup Domains.
 In this lab activity, lnxmaster.vrtsedu.lab will act as the Source server, and winmaster.vrtsedu.lab will act
as the Target server for replicating backup images.

Performing preliminary tasks

In the steps that you follow, you add the entry of the Trusted primary server into both the NetBackup Domains.
you also add the replication target in the source MSDP pool.

1. In the lnxmaster.vrtsedu.lab NetBackup web user interface, click the settings icon present at the top
right corner and select the Global security option.
2. On the Global security settings page, click the Trusted primary servers tab.
3. In the Trusted primary servers tab, click Add.
4. In the Add trusted primary server dialog box, enter winmaster.vrtsedu.lab in the Remote primary
server field and click Next.
5. Take a look at the note that is displayed and click Create trust.

In this lab activity, you are using an External CA.

 Successfully added the trusted primary server winmaster.vrtsedu.lab message is displayed.

6. Verify that the winmaster.vrtsedu.lab entry is listed in the Primary server list under the Trusted primary
servers tab.
7. Minimize the lnxmaster.vrtsedu.lab NetBackup Web UI Firefox window.
8. Locate and launch the Firefox shortcut present on the desktop of the console system.
9. In the address bar, enter the URL https://winmaster.vrtsedu.lab/webui.

In the following steps, you add the Trusted primary server entry in winmaster.vrtsedu.lab Primary server.

10. Sign in using the following credentials and click Sign in.
o Username - Administrator
o Password - P@ssw0rd

11. Click the close icon to close the Welcome to Veritas NetBackup dialog box.
12. In the NetBackup web user interface, click the settings icon present at the top right corner and select
the Global security option.
13. On the Global security settings page, click Trusted primary servers tab.
14. In the Trusted primary servers tab, click Add.
15. In the Add trusted primary server dialog box, enter lnxmaster.vrtsedu.lab in the Remote primary server
field and click Next.
16. Take a look at the note that is displayed and click Create trust.

In this lab activity, we are using an External CA.

Successfully added the trusted primary server lnxmaster.vrtsedu.lab message is displayed.

17. Verify that the lnxmaster.vrtsedu.lab entry is listed in the Primary server list under the Trusted primary
servers tab.
18. Minimize the winmaster.vrtsedu.lab NetBackup Web UI Firefox window. you will return to it later in this
lab.
19. Maximize the lnxmaster.vrtsedu.lab NetBackup Web UI Firefox window.
20. In the NetBackup web user interface, in the left navigation pane, click Storage > Storage configuration
21. On the Storage configuration page, click the Disk pools tab.
22. Click the media_msdp_dpool entry, the media_msdp_dpool page is displayed.
23. In the media_msdp_dpool page scroll down to the bottom. In the Replication targets section click Add.
24. In the Add replication targets dialog box, select the winmaster.vrtsedu.lab entry in the Select trusted
primary server section.
25. Select the winmedia.vrtsedu.lab entry in the Select target storage server section.
26. In the Login credentials for the replication target storage server section enter the following details.
o Username - dedup
o Password - P@ssw0rd
27. Click Add in the Add replication targets dialog box.

Successfully added replication target on selected volume message is displayed.

28. Verify that winmedia.vrtsedu.lab entry is listed under the Replication targets section of the
media_msdp_dpool page.

You have successfully added a replication target. In this lab activity, you perform replication on a specific
target.

If replicating to specific targets, you must create the Import SLP before creating the Auto Image Replication
SLP in the originating domain.

29. Click the close icon on the top right corner to close the media_msdp_dpool page.
30. Minimize the lnxmaster.vrtsedu.lab NetBackup Web UI Firefox window.

Creating Import SLP in Target domain

In the steps that you follow, you create an Import SLP in the target domain.

31. Maximize the winmaster.vrtsedu.lab NetBackup Web UI Firefox window.

32. In the NetBackup web user interface, in the left navigation pane, click Storage > Storage lifecycle
policies.
33. In the Storage lifecycle policies tab, click Add to add a new Storage lifecycle policy.

The Storage lifecycle policy page is displayed.

34. Enter the information provided in the table below on the Storage lifecycle policy page.

Storage Lifecycle Policy Parameter Value

Storage lifecycle policy name Import-AIR

Data classification no data classification (default)

Priority for secondary operations 0 (default)

State of secondary operation processing Active (default)

Adding the first operation to the SLP

In the steps that you follow, you add the properties for the first operation to be performed by the new Storage
Lifecycle Policy.

35. Click the Add button to add the first operation to the SLP.

The New operation page is displayed.

36. Enter the information provided in the table below to complete the configuration of the first storage
operation for the SLP.

New operation properties Value

Operation Import (change this setting)

Destination storage media_msdp_stu (change this setting)

Retention type Target retention (Default setting)

37. Click Create to create the first operation to the SLP.

Verify that the Import operation entry is added to the Operation list of the Import-AIR Storage Lifecycle
Policy.

38. Click Create to create the Import-AIR Storage Lifecycle Policy.

Successfully added storage lifecycle policy message is displayed.

39. Verify that entry for the Import-AIR storage lifecycle policy is visible in the list of SLPs that is displayed in
the right pane of the NetBackup web user interface.

Customizing SLP settings in Target domain

In the steps that you follow, you customize different SLP settings, located under Storage > Storage lifecycle
policies in the NetBackup web user interface.

The SLP settings in the NetBackup web user interface allow administrators to customize how storage lifecycle
policies are maintained and how SLP jobs run. The properties apply to the SLPs of the currently logged in Primary
Server.
40. In the winmaster.vrtsedu.lab NetBackup web user interface, in the left navigation pane, click Storage >
Storage lifecycle policies.
41. In the Storage lifecycle policies page, click SLP settings present on the top right corner.

The SLP settings page displays the default values for all Storage Lifecycle Property.
To save time in this lab activity, you customize some of the Storage Lifecycle Property values to minimize
the wait time that would normally occur between the Backup and automatic Replication operations
(controlled by the Storage Lifecycle Policy).

42. Select the Value entry for the Force interval for small job parameter, and modify the value to 10
(seconds).

The default setting for the Force interval for small job is 30 minutes. This parameter prevents small
replication jobs from running too frequently.

43. Select the Value entry for the Job Submission Interval parameter, and modify the value to 10 (seconds).

The default setting for the Job Submission Interval parameter is 5 minutes. This parameter controls how
often SLP processing jobs are submitted for execution.

44. Select the Value entry for the Image processing interval parameter, and modify the value to 10
(seconds).

The default setting for the Image processing interval parameter is 5 minutes. This parameter controls how
often new SLP-managed images are recognized and set up for SLP processing.

45. Click Save to save the Storage Lifecycle Property changes.

Successfully updated the SLP settings message is displayed.

46. Minimize the winmaster.vrtsedu.lab NetBackup Web UI Firefox window. You will return to it later in this
exercise.

Creating Auto Image Replication SLP in Source domain

In the steps that you follow, you create an AIR SLP in the source domain. This SLP will backup the data in the
source domain and with help of Auto Image Replication (AIR), the backup image will get replicated in the target
domain.

47. Maximize the lnxmaster.vrtsedu.lab NetBackup Web UI Firefox window.

48. In the NetBackup web user interface, in the left navigation pane, go to Storage > Storage lifecycle
policies.

The lists of currently configured Storage lifecycle policies are displayed on the Storage lifecycle policies
page under the Storage lifecycle policies tab.
49. In the Storage lifecycle policies tab, click Add to add a new Storage lifecycle policy.

The Storage lifecycle policy page is displayed.

50. Enter the information provided in the table below on the Storage lifecycle policy page.

Storage Lifecycle Policy Parameter Value

Storage lifecycle policy name AIR

Data classification no data classification (default)

Priority for secondary operations 0 (default)

State of secondary operation processing Active (default)

Adding the first operation to the SLP

In the steps that you follow, you add the properties for the first operation to be performed by the new Storage
Lifecycle Policy.

51. Click the Add button to add the first operation to the SLP.

The New operation page is displayed.

52. Enter the information provided in the table below to complete the configuration of the first storage
operation for the SLP.

New operation properties Value

Operation Backup (Default setting)

Destination storage media_msdp_stu (change this setting)

Volume pool n/a

 New operation properties Value

Media owner n/a

Retention type Fixed (Default setting)

Retention period 1 month (Retention Level 3) (change this setting)

53. Click Create to create the first operation to the SLP.

Verify that the Backup operation entry is added to the Operation list of the AIR Storage Lifecycle Policy.

Adding the second operation to the SLP

In the steps that you follow, you add the properties for the second operation to be performed by the new Storage
Lifecycle Policy.

54. Click the entry for the first Backup operation entry in the SLP, to highlight the entry.

Verify that the entry for the first Backup operation is highlighted.

55. Click the Actions (ellipsis button) and select Add child to add a child operation to the
first Backup operation.

The New operation page is displayed.

56. Use the information provided in the table below to complete the configuration of the second SLP
operation.

New operation properties Value

Source storage media_msdp_stu (Backup)

Operation Replication (change this setting)

Destination storage attributes A specific primary server (change this setting)

 New operation properties Value

Target primary server winmaster.vrtsedu.lab

Target import SLP Import-AIR

Retention type Fixed (default)

3 months (Retention Level 5) (change this

Retention period
setting)

Postpone creation of this copy until the source is about

Not selected (default)
to expire

57. Click Create to create the second operation to the SLP.

Verify that the Replication operation entry is added to the Operation list of the AIR Storage Lifecycle Policy.

This figure illustrates the AIR SLP with two operations included.

The left margin of the Replication operation is indented from the entry for the first Backup operation, as
illustrated in the figure above, indicating that the Replication operation is derived from the
first Backup operation.
58. Click Create to create the AIR Storage Lifecycle Policy.

Successfully added storage lifecycle policy message is displayed.

59. Verify that entry for the AIR storage lifecycle policy is visible in the list of SLPs that is displayed in the right
pane of the NetBackup web user interface.

Configuring a policy to use an SLP

In the steps that you follow, you configure a policy that uses the AIR SLP to automatically perform the operations
specified in the SLP.

60. In the NetBackup web user interface, in the left navigation pane, click Protection > Policies.

The policies that are currently configured are listed on the Policies page.

61. Select the check box for the OnPrem_to_Cloud_Policy policy and select Copy policy.
62. In the Copy policy dialog box type Rep_Backup in the New policy field, then click Copy to create a new
policy.
63. After the policy is created you can see the Rep_Backup policy in the Policies pane.
64. Select the check box for the Rep_Backup policy and click Edit to edit the policy.

The Edit policy - Rep_Backup page is displayed.

65. In the Edit policy - Rep_Backup page, click the Attributes tab.
66. In the Attributes tab, change the Policy storage to the newly created SLP AIR (Storage lifecycle policy).

Leave all the policy settings to their default values.

67. Click Save to save the policy.

68. Verify that the Rep_Backup policy is included in the list of policies displayed on the Policies page of the
NetBackup web user interface.

Performing a manual backup that uses an SLP

In the steps that you follow, you perform a manual backup of the policy Rep_Backup.

69. In the NetBackup web user interface, in the left navigation pane, click Protection > Policies.
70. In the Policies page, mark the check box present on the left side of the policy name Rep_Backup, then
select Manual Backup.
71. Click OK button in the Manual backup window without making any other selections, to initiate the manual
backup operation.
 Successfully sent backup request message is displayed.

72. Select the Activity monitor in the left pane of the NetBackup Web UI.

Note the most recent job entries in the Activity monitor that use the Rep_Backup policy.

73. View the Jobs tab of the Activity monitor and take note of the number of jobs that are added as a result
of the manual backup operation that you initiated.

You see only one Backup job for the policy Rep_Backup.

74. Verify that the job runs to successful completion. If the jobs fail, record the status code or status codes
and seek assistance.
75. View the Job Details for the job that resulted from the manual backup of the Rep_Backup policy.
76. To view Job Details for a job, click on the Job ID for the respective job and then select the Details tab
and take note of the following.

The backup job performs the backup operation on the media_msdp_stu storage unit specified in
the AIR SLP.

A few minutes after the Backup job run to completion, a Replication job is run using
the media_msdp_stu storage unit.

The Backup operation is performed on the source Media Server MSDP pool and the Replication operation is
performed on the target Media Server MSDP pool. In this lab, the source and target MSDP pool have the
same name. View the Job Details for each job to see more details.

77. Allow the Replication job having Policy name as SLP_AIR to run to completion.
78. View the Job Details of the Replication job having Policy name as SLP_AIR that ran soon after the
completion of the Rep_Backup policy Backup job.
79. In the Job Details tab of the Replication job, take note of the message Using OpenStorage to replicate the
backup id.
 The Replication job was initiated within a few minutes after the backup jobs were completed. By default,
NetBackup uses the SLP settings parameters configured in Primary Server to determine the interval at which
the SLP manager process is called. The SLP manager looks for images to be duplicated and
initiates Duplication jobs as needed. To save time in this lab environment, the interval was changed to 10
seconds in an earlier lab exercise.

The Actual job will have different values for Job id, date, and time.

80. Close any open Job Details windows in the Activity monitor.
81. Minimize the lnxmaster.vrtsedu.lab NetBackup Web UI Firefox window.

Verifying Import Job in Target Domain

In the steps that you follow, you verify the Import job is visible after successful replication.

82. Maximize the winmaster.vrtsedu.lab NetBackup Web UI Firefox window.

83. In the NetBackup web user interface, in the left navigation pane, click Activity monitor.
84. Verify that the Import job is visible in the Jobs list.

Click the Refresh icon to refresh the job list in the Activity monitor.

85. Verify that the Import job runs to successful completion. If the jobs fail, record the status code or status
codes and seek assistance.
86. View the Import Job Details for the job that resulted from the Replication job from the source domain.
87. To view Job Details for a job, click on the Job ID for the respective job and then select the Details tab
and take note of the following.
 The Import job Imported the backup image in the target domain replicated from the source domain specified
in the AIR SLP.

The Actual job will have different values for Job id, date, and time.

SLP operations summary

The following jobs were initiated by the Rep_Backup policy, using the operations defined in the AIR Storage
Lifecycle Policy (SLP):

 A Backup job.
o The Backup job ran under the control of the AIR Storage Lifecycle Policy and wrote a backup
image to media_msdp_stu.
 A Replication job.
o This job was initiated a few minutes after the completion of the Backup operations that were
initiated by the SLP (AIR).
o The Storage Lifecycle Property, Image processing interval, determines how often NetBackup
calls its Duplication Manager process, to look for backup images to be processed, and the Force
interval for small job Storage Lifecycle Property sets the minimum wait time that must elapse
before a small duplication or replication job can be submitted.
o The Replication job caused the replication of the backup image or backup images created by
the Backup job to be replicated from the media_msdp_stu (source domain)
to media_msdp_stu (target domain) (specified in the SLP operations).
Lab 13: Protecting the NetBackup Catalog

Exercise A: Verifying Catalog Configuration Files

In this exercise, you use CLI commands to verify (check) the NetBackup and Catalog configuration files location.

Verifying Relational database files

1. Sign in to the console system using the following credentials.

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double click the PuTTY icon located on the desktop of console system, and connect
to lnxmaster.vrtsedu.lab using the following credentials.
o Username: root
o Password: P@ssw0rd

3. Navigate to this location and run the following commands to verify the list of Relational database files.

cd /usr/openv/db/data

ls

ls -l

If required, use the cat command to verify the contents of the files. But do not modify the content or
permissions of the files located in the Data directory.
 o NetBackup installs SAP SQL anywhere during the Primary/Master server installation as a private, non-
shared server for the NetBackup database.
o The relational database resides in the \NetBackupDB\data directory on Windows systems and in the
/usr/openv/db/data on UNIX/Linux systems.
o It consists of a number of table spaces, which are tied to the main database, NBDB.
o Other databases such as BMR, Authorization (NBAZDB) and Search databases are also stored in this
directory, but are not required for core functionality.
o Netbackup image database contains the following files: Image files, Image .f files, .lck files,
db_marker.txt
o The image database contains subdirectories for each client that is backed up by NetBackup, including
the Primary/Master server and any media servers.
o It contains the files, such as: Image files, Image .f files, .lck files, db_marker.txt.
o The image database is the largest part of the NetBackup catalog.

Verifying NetBackup configuration files

4. Navigate to this location, run the following commands to verify the list of the NetBackup config files.
o There are three main configuration files that should be noted, which are as
follows: server.conf, databases.conf, vxdbms.conf.

cat /usr/openv/var/global/server.conf | more

cat /usr/openv/var/global/databases.conf | more

cat /usr/openv/db/data/vxdbms.conf | more

 o Server.conf: The file is read when the SQLAnywhere service is started. The service gets all its
configuration information from this file. NetBackup may not start if the server.conf is edited.
o Databases.conf: This file contains the locations of the main database files and the database names
for automatic startup when the SQL Anywhere service is started. If this file becomes corrupt then
NetBackup will not know where to go find the databases and thus the NetBackup database services
will not start.
o Vxdbms.conf: This file maintains information such as the name of the Primary/Master server as it was
originally installed. It also contains the SQL password needed to log into the NetBackup databases.
Lastly this file contains the location of where you can find the NetBackup data, index and tlogs, and
staging directory.

Verifying NetBackup Catalog configuration files

5. Navigate to this location, run the following commands to verify the list of the Catalog config files.
o There are three catalog configuration files that should be noted, which are as
follows: class, class_template, config.

cd /usr/openv/netbackup/db/

ls

ls -l class/
ls -l class_template/

ls -l config/

The following screenshot displays an example of the NetBackup catalog directory structure in a typical
NetBackup installation on a Linux system.
 6. Minimize the putty window.

Exercise B: Configuring and Running NetBackup Catalog Backups

In this exercise, you configure a policy to enable NetBackup to perform a catalog backup operation. Then, you
perform catalog backup and catalog restore operations, and monitor the results of each operation.

Creating a Disaster Recovery passphrase

In the steps that follow, you create a NetBackup Disaster Recovery passphrase. This passphrase can be used to
recovery the security certificate identity of the Primary/Master server during a re-installation of the NetBackup
server software.

1. Double-click the NetBackup 10.0 Administration Console shortcut located on the desktop of console
system.
2. In the NetBackup Administration Console, login using the following credentials:

a. Host name: lnxmaster.vrtsedu.lab is displayed in the field.

b. Username: root

c. Password: P@ssw0rd
3. Select Security Management in the left pane of the Administration Console, and then select Global
Security Settings.
4. Select the Disaster Recovery tab at the bottom of the Administration Console.
o You can select Disaster Recovery tab from the Web UI interface (also): select settings (on the top
right corner) > Global security > Disaster recovery.
o For creating a policy and Host property settings on Catalog, it can be performed from an Admin
console (only).

5. In the Passphrase and Confirm Passphrase field type: Tra1n!ng.

6. Click Save then click OK.

Creating a Catalog Backup policy

In the steps that follow, you create a catalog backup policy, LAB-catalog-to-media-bdisk, to protect the
NetBackup catalog configuration.

8. Select Policies in the left pane of the Administration Console.

9. Right-click in the white space of All Policies and select New Policy.
10. In the Policy name field, of the Add a New Policy dialog box, type LAB-catalog-to-media-bdisk, and
click OK.
11. In the Change Policy window, configure the policy Attributes using the information provided in the
table.
 Policy Attributes for LAB-catalog-to-media-bdisk

Attributes Tab

Policy type NBU-Catalog

Policy storage: media_bdisk_stu

Policy volume pool: CatalogBackup (auto-populates)

All other policy Attributes: use default settings

12. A policy with a Policy type of NBU-Catalog has only three tabs: the Attributes, Schedules, and Disaster
Recovery tabs.
13. Click the Schedules tab.
14. Create a Full Backup schedule using the parameters described in the following table.

Schedule 1 parameter settings:

Attributes tab:

Schedule name: WEEKLY-FULL

Type of backup Full Backup

Schedule Type Frequency

Frequency: 1 weeks

Attributes Retention 2 weeks (Retention Level 1) (default)

Start Window: none (only manual backups)

15. Create a Cumulative Incremental Backup schedule using the parameters described in the following
table.

Schedule 2 parameter settings

Attributes tab:

Schedule Name: DAILY-CUMULATIVE

Type of backup: Cumulative Incremental Backup

Schedule Type: Frequency (default)

Frequency: 1 days

Retention 2 weeks(Retention Level 1) (default)

Start Window: none (only manual backups)

16. Create a Differential Incremental Backup schedule using the parameters described in the following
table.

Schedule 3 parameter settings

Attributes tab:

Schedule Name: SESSION-DIFFERENTIAL

Type of backup: Differential Incremental Backup

Schedule type: After each backup session (radio button)

Retention: 2 weeks(Retention Level 1) (default)

 Schedule 3 parameter settings

Start Window: 7 days per week/24 hours per day

17. Verify all the three schedules you have created are visible in the Schedules tab of the policy.

18. Click the Disaster Recovery tab.

19. Enter the Disaster Recovery parameters as provided in the following table:

Disaster Recovery tab settings

Path /mnt/dr_recovery_files

Logon:

Password:

Send in an E-mail attachment check box selected (Default] setting)

E-mail address administrator@vrtsedu.lab

20. In this lab environment, the Disaster Recovery Path listed in the tables point to a shared folder
on lnxmaster.vrtsedu.lab, /mnt/dr_recovery_files.
21. Do not enter login credentials, for this step you use nbsvc account. An entry of nbsvc account is already
provided in /etc/fstab (on lnxmaster system). Enter the DR path and email address parameters (only).
22. Setting the "Send in an E-mail attachment" parameter, and including the email address, causes NetBackup
to send an email message at the end of the backup of the catalog. In this lab kit, the email message can be
viewed using Mozilla Thunderbird to open the mail message.
23. Click OK to save the changes to the Disaster Recovery tab parameters.

You may need to resize the Change Policy window to view the OK button.
24. Verify that an entry for the LAB-catalog-to-media-bdisk policy is displayed in the All Policies pane of
the Administration Console.

Performing manual NetBackup catalog backups

In the steps that follow, you initiate manual backups of the NetBackup catalogs using the LAB-catalog-to-media-
bdisk policy, and monitor the results.

21. From the Policies pane initiate a manual backup using the LAB-catalog-to-media-bdisk policy and
the WEEKLY-FULL schedule.
22. Access the Activity Monitor to view the backup jobs that occur as a result of the manual backup request
that used the LAB-catalog-to-media-bdisk policy.

It may take a few minutes for all the Backup jobs to be displayed in the Activity Monitor Jobs pane.

If any of the backup jobs fail - ends with any non-zero (0) status -- view the detailed status for the job (by
double-clicking the entry for the Job ID), and view the information for the failed job. Perform basic
troubleshooting and attempt to resolve the problem. Then, repeat the backup operation. If the job continues
to fail then seek assistance.

23. Using Notepad++ or a pen and paper answer the questions listed in the following table.

Catalog backup job

questions

Q1: How many jobs were performed as a result of the manual backup request?

Q2: What was the job Type for the jobs?

Q3: Were any of the jobs the parent job to other Catalog Backup jobs?

From the Status pane of the Detailed Status of the first child job, what was the
Q4:
purpose of that job?
 Catalog backup job
questions

From the Job Details for the second child job, what was the purpose of the second
Q5:
catalog backup child job?

Q6: What does the third child catalog backup job do?

Catalog backup
job - Answers

Q1: How many jobs were performed as a result of the manual backup request?

A1: Four jobs were initiated

Q2: What was the job Type for the jobs?

A2: The jobs all had the job Type of Catalog Backup

Q3: Were any of the jobs the parent job to other Catalog Backup jobs?

Yes. The first job (lowest-numbered job) was the parent job to the other three jobs. You
A3: can determine this by looking in the Job hierarchy tab of the Job Details window for any
of the jobs.

From the Status pane of the Detailed Status of the first child job, what was the purpose
Q4:
of that job?

It appears the job states the catalog backup to the staging folder, and validates the
A4:
contents of the staging folder.

From the Job Details for the second child job, what was the purpose of the second
Q5:
catalog backup child job?
 Catalog backup
job - Answers

It appears the job backs up a specific part of the NetBackup catalog (DARS_DATA.db) to
A5:
media from the staging folder.

Q6: What does the third child catalog backup job do?

It is unclear what portion of the NetBackup catalogs are backed up by this job but it
A6:
writes a backup image to media.

25. Close any open Job Details windows.

26. Run manual backup for DAILY CUMULATIVE and SESSION-DIFFERENTIAL schedule and verify that
those jobs run to successful completion.

DAILY CUMULATIVE backup job output:

SESSION-DIFFERENTIAL backup job output:

Viewing the Disaster Recovery directory contents

In the steps to follow, you access the disaster recovery directory to verify the contents of the catalog backup job.

26. Access the desktop of console.vrtsedu.lab.

27. Open the putty window of lnxmaster.vrtsedu.lab, and check the listing of /mnt/dr_recovery_files.
28. Take note of the contents of the dr_recovery_files folder.

ls -l /mnt/dr_recovery_files

Currently, the directory contains two files. Both these files have the file name with the format,
[policy_name]_[ctimestamp}_[schedule type}.

vrtsedu: LAB-catalog-to-media-bdisk_1515794398_FULL

o The file without the extension is known as the DR file.

o The second file is the DR package file that contains the security certificates for the Primary/Master
server should the Primary/Master server software ever need to be re-installed. These files are created
by the Catalog Backup job.
o The DR package file is available in NetBackup.

The DR file is an ASCII text file that can be displayed in a text editor. Do not modify the contents of the file.
Every time a Catalog Backup is performed -- whether a Full Backup or an Incremental Backup of the catalogs,
two DR files are created in the Disaster Recovery path specified in the Disaster Recovery tab of the Catalog
Backup policy.
It is common in a production NetBackup environment to move the Catalog Backup DR Files to an offsite
location, or at least to a system that is remote from the Primary/Master server.

29. Minimize the putty window you need to access it in the next exercise.
30. Locate and launch the Mozilla Thunderbird shortcut present on the desktop.
31. Verify the successful catalog backup notifications email.
32. Select the first Full backup catalog message (notification) and ensure that two DR files got attached, and
that you verified the same Full backup DR files in step 28.

33. If required, verify the other backup messages information and minimize the Mozilla browser window.
Exercise C: Recovering the Catalogs Using the NetBackup Catalog Recovery
Wizard

In this exercise, you perform a NetBackup catalog recovery operation using the DR_FILE that was written by the
most recent Catalog Backup job and the NetBackup Catalog Recovery Wizard.

Using the Catalog Recovery Wizard

In the steps that follow, you use the NetBackup Catalog Recovery wizard to recover the NetBackup catalogs.

1. From the lnxmaster.vrtsedu.lab putty window, on console.vrtsedu.lab, note down the LAB-
catalog…_FULL file name.

2. Minimize the lnxmaster.vrtsedu.lab window.

3. Access the NetBackup Administration Console, select Policies option and perform these steps.
a. Select LAB-console-to-media-msdp-override policy, right-click the policy and deactivate this
policy.

b. Also, delete this LAB-console-to-media-msdp-override policy.

you recover this deleted policy in the next steps.

4. Again, access the open NetBackup Administration Console and click the NetBackup
Management entry in the left pane.

A list of NetBackup wizards is displayed in the right pane of the Administration Console.

5. Click the Recover the catalogs wizard entry.

The NetBackup Catalog Recovery Wizard window is displayed.

6. Click Next in the welcome screen of the wizard to continue.

7. Use the following table to fill in the path for the Specify the full pathname to the disaster recovery
file field, and use the browse option to locate and paste the DR file name.

Primary/Master server name DR file path

lnxmaster.vrtsedu.lab /mnt/dr_recovery_files/<DR_files_name_FULL>

8. Use the browse function, to upload the DR filename (that you noted in a previous step -- step 1), into the
field.
9.
10. Click Next to continue.

The Retrieving Disaster Recovery File screen displays a message in the Action Required pane, as
illustrated.

If you did not receive a message like the one shown here, click the Back button, and verify you have entered
the correct location to the file and copied the correct file name in the Catalog Disaster Recovery File screen.
If problems persist, then seek assistance.

11. Click Next on the Retrieving Disaster Recovery File screen to continue.
12. When the Disaster Recovery Method screen is displayed, accept the default entries (to Recover an
entire NetBackup catalog), and click Next to continue.

The Recovering Catalog screen is displayed.

The NetBackup catalog recovery process is initiated. This may take several minutes to complete.

13. Take note of the contents of the Logs pane of the Recovering Catalog screen as the catalog recovery
process continues.

When the Next button becomes available for selection, the Catalog Recovery operation is complete. Before
continuing, scroll through the Log File pane to observe key activities that occur during the restore and
recovery operation.

14. After the catalog recovery is complete, click Next in the Recovering Catalog screen.

15. Click Finish to close the NetBackup Catalog Recovery Wizard.

16. Close the NetBackup Administration Console window.

After performing a catalog recovery, it is necessary to stop and start the NetBackup services.
Stop/Restart NetBackup on the Primary/Master server

To complete the catalog recovery of the NetBackup catalogs on the Primary/Master server it is necessary to stop
and restart the NetBackup daemons on the Primary/Master server.

15. Access the lnxmaster.vrtsedu.lab putty window.

16. In the Terminal window, type the following command to stop the NetBackup daemons on the
Primary/Master server.

Command: netbackup stop

17. When the terminal window is returned, type the following command to verify that the NetBackup
daemons have been shut down.

Command: bpps -x

It is expected that the auth.conf and pbx_exchange process will still be running.

18. When the terminal window is returned, type the following command to start the NetBackup daemons.

Command: netbackup start

19. When the terminal window is returned, type the following command to verify that all the NetBackup
daemons have been started.

Command: bpps -x

It has been observed in this virtualized lab environment, that after recovering the NetBackup catalogs on the
Linux Primary/Master server, lnxmaster.vrtsedu.lab, that the NetBackup Web Management Console (nbwmc)
may not start reliably, leaving NetBackup in a non-operational state.
If you encounter this situation, stop the NetBackup services on the Primary/Master server, and then perform a
reboot of the lnxmaster.vrtsedu.lab system.

20. Minimize the lnxmaster.vrtsedu.lab putty window.

Final recovery procedures

In the steps that follow, you verify the operation of the NetBackup environment and perform a few final tasks as a
follow-up to the recovery of the NetBackup catalogs.

21. Double-click the NetBackup 10.0 Administration Console shortcut, located on the desktop
of console.vrtsedu.lab.
22. Login using the following credentials.
 NetBackup Primary/Master server name User name Password

lnxmaster.vrtsedu.lab root P@ssw0rd

23. Briefly navigate through the various panes of the Administration Console to verify that the NetBackup
configuration is intact following the catalog recovery:
o Activity Monitor
o NetBackup Management > Policies

Verify that LAB-console-to-media-msdp-override policy is created (again), using the Catalog file
(Full DR file).

o NetBackup Management > Storage > Storage Units

o NetBackup Management > Storage > Storage Unit Groups
o NetBackup Management > Storage > Storage Lifecycle Policies
o Media and Device Management > Device Monitor
o Media and Device Management > Media
o Media and Device Management > Devices > Drives
o Media and Device Management > Devices > Robots
o Media and Device Management > Devices > Media Servers
o Media and Device Management > Devices > Disk Pools
o Media and Device Management > Credentials > Storage Servers
o Media and Device Management > Credentials > Virtual Machine Servers
24. Minimize the NetBackup Administration console.
o You can perform the NetBackup catalog recovery operation using the following command: bprecover
-wizard (CLI wizard).
o The following steps are involved in this catalog recovery process, if you use the CLI method:
a. The backup media is read.
b. The NetBackup configurations files are recovered.
c. The NBDB files are written to the staging directory for: UNIX/Linux: /usr/openv/db/staging
d. The database files are copied to the database production area for: UNIX/Linux:
/usr/openv/db/data

Exercise D: Performing Catalog Operations

In this exercise, you perform the following catalog operations:

 Verify the catalog recovery files (catalog backup files).

 Duplicate the catalog backup file.
 Perform the NetBackup Catalog consistency checks on lnxmaster server.
Verifying the Catalog backup (recovery) files

1. Access the minimized NetBackup Administration Console.

2. In the NetBackup Administration Console, navigate to NetBackup Management>Catalog.
3. In the right pane, ensure the Action is set to Verify. Do not make any other changes and click Search
Now.
4. In the search results, observe the values of the catalog backup files. Ensure that Full catalog recovery file is
selected. If required map this ID with the PuTTY window output.
 From the lnxmaster.vrtsedu.lab putty window, note down the LAB-catalog…_FULL file name.

Map both the recovery IDs for Full file in Admin console and PuTTY window, and select the exact catalog
recovery file to perform the next steps.

Duplicating the Catalog backup image

4. In the NetBackup Administration console, select catalog in the left pane.

5. Ensure the Action is set to Duplicate. Do not make any other changes and click Search Now.
6. Right-click the Full catalog image, which is noted down in step 3 and select Duplicate.
7. In the Setup Duplication Variables dialogue box, select the storage unit as master-advdisk-stu storage
unit, select the checkbox for copy 1: and click OK.

For this step, use master-advdisk-stu storage unit location as the duplicate copy.

8. Click OK in the Confirm Duplicate window.

9. Use the Activity Monitor to ensure that the duplication job completes successfully.
10. Navigate back to Catalog tab and right-click the backup image which is DAILY-CUMULATIVE schedule.
Select Expire to expire the backup image.
11. Click Yes in the Expire Images dialogue box.

Using CLI to perform the catalog consistency checks

12. From lnxmaster.vrtsedu.lab putty window, run the following command to check the contents of the
image catalog against the EMM_DATA.db file.

/usr/openv/netbackup/bin/bpdbm -consistency

Use the bpdbm –consistency command to compare the contents of the image catalog against the
EMM_DATA.db file.

13. Minimize all the windows.

Exercise E: Configuring a Policy for Catalog Archive

In this exercise, you configure a policy for catalog archive.

Deactivating Catalog policy

In the steps that follow, you deactivate NetBackup catalog policy that was created in the earlier exercises of this
course.

You take these steps to prevent excessive numbers of automated backup jobs from being performed.
When no active NetBackup catalog backup schedule exists, Image Cleanup jobs that NetBackup performs
automatically end with "status 1" (incomplete). This is expected, and not a cause for concern.

1. Access the NetBackup Administration Console window on console.vrtsedu.lab.

2. Deactivate the LAB-catalog-to-media-bdisk policy.
a. Select the Policies entry in the left pane of the Administration Console window.
b. Locate and right-click the LAB-catalog-to-media-bdisk policy entry.
c. Click Deactivate in the menu.
d. Verify that the LAB-catalog-to-media-bdisk policy has been de-activated.
3. Verify that the LAB-catalog-to-media-bdisk policy is de-activated.

Creating a Catalog Archive policy

In the steps that follow, you create a catalog archiving policy, catarc, to protect the NetBackup catalog
configuration. There are several features that are specific to a catalog archiving policy.

4. Access the open NetBackup Administration Console, and navigate to NetBackup Management >
select Policies in the left pane of the console
5. Right-click in the white space of All Policies and select New Policy.
6. In the Policy name field, of the Add a New Policy dialog box, type catarc, and click OK.
7. In the Change Policy window, configure the policy Attributes using the information provided in the
following table.

Policy Attributes for catalog-archive

Attributes Tab

Policy type Standard

 Policy Attributes for catalog-archive

Policy storage: master_bdisk_stu

Go into affect at:: Do not select this option (clear the Go into effect at: check box)

All other policy Attributes: use default settings

8. Clear the Go into effect at: check box. The policy is not run by the scheduler. Rather the bpcatarc command
activates this special policy to perform a catalog backup job, then deactivates the policy after the job is done.
9. Accept the defaults for all the other options in the Attributes tab of the policy
10. Click the Schedules tab.
11. Create a User Backup schedule using the parameters described in the following table.

Schedule 1 parameter settings:

Attributes tab:

Schedule name: catarc

Type of backup User Backup

Schedule Type

Frequency:

Retention 1 year (Retention level 8)

Start Window: 7 days per week/24 hours per day

o Select a retention level for the catalog archive. This must be at least as long as the longest retention
period being archived.
o Failure to set the retention level of the catalog archive for a time at least as long as the longest
retention period of the backups being archived can result in the loss of catalog data.

12. Verify that catarc schedule you have created is visible in the Schedules tab of the policy.
13. Select the clients tab. Enter lnxmaster.vrtsedu.lab as the client. Select the Detect client operating
system option.

Verify that lnxmaster.vrtsedu.lab is added successfully in the Clients tab.

14. Select the Backup Selections tab.

Enter the list of pathname to the section list as: /usr/openv/netbackup/db/images

If required, use the browse option to select this directory in the pathname section and add this line in the list
of pathnames pane.

Verify the path is selected successfully in the Backup Selections tab.

15. Verify each tab again and click OK to save the changes and close the catalog-archive policy.

You may need to resize the Change Policy window to view the OK button.

16. Verify that an entry for the catalog-archive policy is displayed in the All Policies pane of the
Administration Console.

Quering the catalog data

16. Access the lnxmaster.vrtsedu.lab putty window.

17. Enter the following command to query the catalog and see what images are available to be archived.

bpcatlist -client lnxmaster.vrtsedu.lab -since April 01 2022

The catarcid column indicates whether the .f file is not currently backed up (0) or the catarcid of the backup
of that image.

Running the catalog archive

In the steps that follow, you run the catalog archive using the bpcatlist command then pipe the output
through bpcatarc and bpcatrm, and monitor the results.

Before running the catalog archive, create a backup policy named catarc. The policy is required for
the bpcatarc command to successfully process images. The name of the policy reflects that the purpose of the
schedule is for catalog archiving.

18. Enter the following command to run the catalog archive.

bpcatlist -client lnxmaster.vrtsedu.lab -since April 01 2022 | bpcatarc | bpcatrm

19. Maximize the NetBackup Administration console and click Activity Monitor

you see Backup job with Job Policy named catarc, which activated automatically after running the bpcatlist
command then pipe the output through bpcatarc and bpcatrm.

A new job appears in the Activity Monitor. The command waits until the backup completes before it returns
the prompt. The command reports an error only if the catalog archive fails, otherwise the commands return to
the prompt. The File List: section of the Job Details in the Activity Monitor displays a list of image files that
have been processed. When the job completes with a status 0, the bpcatrm command removes the
corresponding .f files. If the job fails, no catalog .f files are removed. If bpcatlist is piped to bpcatarc but the
results are not piped to bpcatrm, then the backup occurs but the .f files are not removed from disk. The same
bpcatlist command can then be rerun and piped to bpcatrm to remove the .f files.

20. Run the following command to determine what images have been previously archived and removed from
disk.
 bpcatlist -offline

you see the archived backup images.

Lab 14: Mitigating Impact of Ransomware (Windows and Linux) - Part A

(Using Flex Appliance)
Configuration Notes

This lab uses following configuration:

nbu5150ma VM: Has a NetBackup Primary/Master server (which is also a media server) instance running.

Console VM: Has NetBackup Java Console, NetBackup WebUI installed.

nbu5150w VM: Has a NetBackup WORM storage server (which is a preconfigured WORM Storage Server) instance
running.

Exercise A: Configuring a Disk Pool and WORM Storage Unit

In this exercise, you configure a disk pool and storage unit which is WORM capable.

Viewing the storage server details

1. Sign in to the console system using the following credentials.

o computer: console.vrtsedu.lab
o User name: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the Veritas Flex Appliance Console shortcut located on the desktop of the console system.

If you receive the Warning message, click Advanced and click Accept Risk and Continue to proceed further.

3. Sign in to the Flex Appliance console using the following credentials.

o Username: admin
o Password: V4ts3Du!
4. Click System topology icon at the left pane (second option from the left pane, as illustrated). Following
instances are seen:
 o nbu5150ma VM: Has a NetBackup Primary/Master server (which is also a media server) instance
running.
o nbu5150w VM: Has a NetBackup WORM Storage Server (which is a preconfigured WORM storage
server) instance running.

5. Verify that nbu5150ma and nbu5150w instances are in ONLINE state. If any of the instance is OFFLINE,
select the instance and click Start.

It may take 2-3 minutes to start the instance.

6. Make a note of the login credentials for both the VMs (do not login to any VM, for now).

For nbu5150ma VM: NetBackup Master and Media server is same.

o Host Name: nbu5150ma.vrtsedu.lab

o User Name: appadmin
o Password: Veritas@123

For nbu5150w VM: NetBackup WORM Storage server.

o Host Name: nbu5150w.vrtsedu.lab (IP address is: 10.10.2.153)

o User Name: wadmin
o Password: Veritas@1234567890
You will not login to nbu5150w VM (either using PuTTY or NBU Admin console), but you are recommended to
make a note of these login details.

7. Minimize the Veritas Flex Appliance Console window.

8. Double-click the NetBackup 10.0 Administration Console shortcut located on the desktop of
the console system.
9. Login using the following credentials:
o Host Name: nbu5150ma.vrtsedu.lab
o User Name: appadmin
o Password: Veritas@123
10. In the left pane, navigate to Media and Device Management > Credentials > Storage Servers
11. In the right pane, double-click the storage server nbu5150w.vrtsedu.lab entry.
12. Click Properties tab. Scroll down in until you find the property wormmode. What is the value displayed?

The value is set to compliance.

13. Click Cancel to close the properties of storage server.

14. Minimize the NetBackup Administration Console.
Configuring the disk pool and WORM capable storage unit

16. Double-click the NetBackup Web UI login shortcut, located on the console desktop.

If you receive the Warning message, click Advanced and click Accept Risk and Continue to proceed further.

17. Sign in using the following credentials:

Host Name URL: nbu5150ma.vrtsedu.lab

User Name: appadmin

Password: Veritas@123

18. In the left pane, navigate to Storage > Storage Configuration.

19. From the right pane, select Storage Servers tab.
o Ensure that nbu5150w.vrtsedu.lab (MSDP Storage server, WORM capable type) was configured
successfully.
o If required, scroll the horizontal bar (to the right side) to verify the other parameters
of nbu5150w WORM storage server.

20. Select Disk pools tab, click + Add button to launch the Add disk pool tab.
21. Enter the following values in the Add disk pool tab:
o Storage server name: nbu5150w.vrtsedu.lab (select this value using Change button)
o Disk pool name: worm_dpool
 o Description: worm_dpool
o Limit I/O streams: mark the checkbox and type the I/O value as 35 per volume (change this value)
o Retain other default values.

22. Click Next.

23. In the Volumes tab, select the default PureDiskVolume option and click Next.

24. In the Replication tab, do not select any value and click Next.
25. Verify the Review details and click Finish to configure worm_dpool disk pool.
26. Ensure that worm_dpool is created successfully. Click Add storage unit button (on the top green bar
option).

27. In the Basic Properties tab enter the following values:

o storage unit name: worm-stu
 o Maximum concurrent jobs: 35
o click Next.

28. In the Disk Pool tab, select the worm_dpool radio button and mark the checkbox for Enable
WORM (Lock until expiration), and click Next.

29. In the Media Server tab, select the Manually select option and mark the checkbox
for nbu5150ma.vrtsedu.lab media server and click Next.

30. In the Review tab, verify the contents of worm-stu MSDP storage unit details and click Save.
31. In the storage configuragation tab, ensure that worm-stu is created successfully.

32. Minimize the NetBackup web user interface.

33. In the NetBackup Administration Console, navigate to NetBackup Management > Storage > Storage
Units.
34. In the right pane, double-click the storage unit worm_stu.
35. Select View Properties and verify the WORM Capable parameter is set to Yes.
36. Click Close and then click Cancel to close the Storage Unit properties.
37. Minimize the NetBackup Administration Console.

Exercise B: Configuring a NetBackup policy

In this exercise, you create a NetBackup policy and use the WORM capable storage unit for backup. You then run a
manual backup using this policy.

1. Maximize the NetBackup Web UI.

2. In the NetBackup Web UI, navigate to Protection >Policies.
3. Click + Add.
4. Enter the policy name as Console_to_worm.
5. Refer to the following information, to create the policy.

Attribute Value

Policy Type MS-Windows

Policy Storage worm-stu

Go into effect set the current date as a previous day (If the current day is 16th July 2021, then set the
at previous date as 14th or 15th July 2021.)

Client console.vrtsedu.lab

Hardware and Operating System: Windows-x64, Windows

Backup
E:\data\simple
Selection

Schedules Full

(Add a Full schedule with default parameters)

6. If you receive the "Unable to connect to NetBackup host" error while adding
the console.vrtsedu.lab client to the backup policy, execute the nbcertcmd -getcrl command on
the console.vrtsedu.lab system to renew the CRL.
7. Click Create to save the policy.
8. The following error message is displayed:

9. Read the message carefully.

10. Select the Full schedule checkbox to change/edit it.
11. Edit the schedule again and set the retention level to 2 hours (Retention level 12).

In the lab environment, this level is pre-configured for you.

12. Click Save to update Schedule change.
13. Click Create to save (or update) the changes to the policy.

Performing Manual Backup to the WORM STU

14. Select the console-to-worm policy checkbox and select Manual Backup.

Run the manual backup; based on the date is set at step 6 for Go into effect at attribute for activating the
policy.

15. Click OK in the Manual Backup window.

16. Use the Activity Monitor (from the left pane) to monitor the progress of the backup.
17. Ensure the backup completes successfully. Mark the checkbox of the backup job and click View
details option.
18. Select the Details tab of the backup job to view the job details.

19. Look for the information which talks about WORM LOCKS.

What is the duration of WORM lock applied to the backup image?

> It is set to 7200 seconds i.e 2 hours.

20. Click X to close the job details.

21. Minimize the NetBackup Web UI.

Exercise C: Understanding Catalog Operations on the WORM Image Copy

In this exercise, you perform the Catalog operations on WORM image copy.

1. Maximize the NetBackup Administration Console.

2. In the NetBackup Administration Console, navigate to NetBackup Management > Catalog.
3. In the right pane, ensure the Action is set to Verify. Do not make any other changes and click Search
Now.
4. In the search results, observe the values for 3 columns named Immutable, Indelible and WORM Unlock
Time.

5. Right-click the backup image which is Immutable and Indelible. Select Expire.
6. Click Yes in the Expire images dialogue box.
7. Following error is displayed. Click OK.

Duplicating the backup image from WORM stu to non-WORM stu

10. In the NetBackup Administration console, select catalog in the left pane.
11. Ensure the Action is set to Duplicate. Do not make any other changes and click Search Now.
12. Right-click the first backup image which is Immutable and Indelible and select Duplicate.
13. In the Setup Duplication Variables dialogue box, select the storage unit as AdvDisk-stu storage unit,
select the checkbox for copy 1: and click OK.

For this step, use the same AdvDisk-stu storage unit location as the duplicate copy.
14. Click OK in the Confirm Duplicate window.
15. Use the Activity Monitor to ensure the duplication job completes successfully.

Extending the expiration/unlock time of the copy using bpexpdate command

As long as you are honouring the Min-Max retention lock time, you can use the bpexpdate command to change
the expiration date of the backup image written to WORM_STU.

16. In the NetBackup Administration Console, Click Catalog option.

17. Ensure the Action is set to Verify. Click Search now.
18. Highlight the first backup image which is Immutable and Indelible. Notedown the Backup ID and WORM
unlock time for this image.

You may need to right-click the highlighted image and select copy to clipboard. Paste the information in
Notepad and then copy only the backupid to the clipboard.
o If you did not find the values of WORM Unlock time, Immutable, and Indelible (on recent Catalog
backup image), perform another Manual backup (using Console_to_worm policy).
o Later, select the latest Catalog backup image and copy the parameters of "Backup ID and WORM
Unlock time" in a notepad and then continue with next step 19.

19. Minimize the NetBackup Administration Console.

20. Locate and launch the PuTTY shortuct present on the console desktop.
21. Connect to the nbu5150ma.vrtsedu.lab server using the saved sessions.
22. Login using the following credentials:
o User Name: appadmin
o Password: Veritas@123
23. Execute the following commands:
a. Change the directory to admincmd

cd /usr/openv/netbackup/bin/admincmd

b. Add 30 minutes to the WORM unlock time which you noted earlier. For example, if the time you
noted earlier is "10/27/2020 06:12:18", new WORM unlock time will be "10/27/2020 06:42:18"

Execute the following bpexpdate command:

sudo ./bpexpdate -backupid paste_the_backupid_here -d "new WORM unlock time " -extend_worm_locks

24. It should be noted that unlock time cannot be shortened.

 25. Refer to following example:

26.
27. When prompted for password, enter the password as: Veritas@123
28. Enter y when the Are you sure you want to change to expire on ? question appears.

29. If you receive the Open Storage WORM lock error meassage, its because of WORM indelibility for the
duration of the desired NetBackup retention level may not be possible due to vendor-defined or storage SLA-
derived WORM constraints.

Solution is:

You might have set the WORM unlock time which does not fall under WORM Lock intervals (i.e. Min retention
level is 2 hours, Max is 4 hours, WORM Unlock time). Refer to the above example step 22b and enter the
proper values.
Additional information on WORM lock error:
o After changing the minimum or maximum WORM lock intervals on storage, refresh the corresponding
diskpool using nbdevconfig -updatedp command with appropriate -dp and -stype options or
the Refresh button in the JavaUI of 'Change Disk Pool'. Then manually initiate, or wait for, the next
image cleanup process for the data to be WORM-locked.
o If storage WORM constraints cannot be changed, retention levels for the offending NetBackup SLPs in
the source domain should be updated to reflect valid WORM constraints. Backup data on the target
made prior to this change will be made immutable when enough time has passed such that the
maximum WORM lock interval is satisfied and cleanup job is run.

30. Return to the NetBackup Administration Console. Click the Catalog.

31. Ensure the Action is set to Verify. Click Search now.
32. Highlight the backup image which you had referred to and verify that its WORM Unlock Time has been
modified.
33. Minimize the NetBackup Administration Console.
Exercise D: Configuring and Identifying Backup Anomaly

In this exercise, your configure NetBackup Anomaly and will run the backup job to identify the anomalies within
the backup metadata.

This exercise provides the workflow and the procedure that enable the Primary/Master server (same for media) to
detect backup anomalies.

1. Maximize the nbu5150ma.vrtsedu.lab Putty session.

2. Run the following command to check the status of nbanomaly service on Primary/Master server:
nbu5150ma.

bpps -x | grep -i nbanomaly

3. Minimize the nbu5150ma.vrtsedu.lab Putty session.

4. Maximize the NetBackup Web UI.
5. In the NetBackup Web UI, click Detection and reporting > Anomaly detection in the left pane.
6. In the Anomaly detection page, click Anomaly detection settings.
7. In the Anomaly detection settings page, click Edit for Enable anomaly detection activities.
8. In the Enable anomaly detection dialog box, select the radio button for Enable anomaly data
gathering, detection service and events.
9. Click Save in the Enable anomaly detection dialog box.
10. Close the Anomaly detection settings page.
11. Minimize the NetBackup Web UI.
12. Maximize the nbu5150ma.vrtsedu.lab Putty session.
13. Create the following script to run multiple manual backups (at a time).
o console_backup_35jobs.sh: This scirpt is used to run Console-to-worm policy with full schedule for
35 times.

14. Create this backup job script console_backup_35jobs.sh on nbu5150ma server.

sudo mkdir /netbackup_scripts

If required, enter the passwaord as: Veritas@123

cd /netbackup_scripts

sudo vi console_backup_35jobs.sh
 Copy this simple script in console_backup_35jobs.sh.
#/usr/bin/bash
##This script is for running 35 backup jobs.

x=0
while [ $x -le 35 ]
do
sudo /usr/openv/netbackup/bin/bpbackup -i -p Console_to_worm -s Full -h
console.vrtsedu.lab -S nbu5150ma.vrtsedu.lab
((x++))
done
Save this file using :wq!

o Provide the execute (RW) permissions to execute this file.

sudo chmod +x console_backup_35jobs.sh

The same file console_backup_35jobs.sh is copied on Console desktop. If required, copy the script content and
using vi mode paste the lines in console_backup_35jobs.sh file.

15. Run the console_backup_35jobs.sh script without making any modifications in policy or script.

sudo ./console_backup_35jobs.sh

If required, enter the password: Veritas@123

16. From the Activity monitor, ensure that all the jobs (35 jobs) were successful.

It takes 15-20 mins to finish all the 35 backup jobs in complete (Done) state, then only continue with the next
step.

17. On Console desktop, right-click the createfiles.ps1 file and click Run with PowerShell option.

This createfiles.ps1 script is used to create 100 Anomaly test files and later these files are copied to:
E:\data\simple (on Console client). Run this script after all the 35 backup jobs were successful (only).
18. Maximize the NetBackup Web UI, click Protection > Policies.
19. In the Policies page, select Console_to_worm policy and perform one more manual backup job (after 5
mins).

Perform this single backup job after creating the 100 test files (only), as explained in the previous step.

20. Ensure the job complete successfully.

21. In the NetBackup Web UI, select Detection and reporting > Anomaly detection.
o It takes more time (15-30 mins) to display the anomaly data.
o If required, reload the Web UI browser (after 15 mins) for several times to verify the Anomaly data.

22. Select the latest Job ID and verify the Anomaly data (as illustrated.)

Anomalies output:

23. Verify the output.

24. You can mark the anomaly as:
o Mark as ignore
o Confirm as anomaly
o Report as false positive
Lab 14: Mitigating Impact of Ransomware (Windows and Linux) - Part B
(Using AWS S3)

Exercise A: Configuring a Disk Pool and WORM Storage Unit

In this exercise, you configure a disk pool and storage unit which is WORM capable.

Creating the cloud immutable volume using msdpcldutil tool

1. Sign in to the console system using the following credentials.

o computer: console.vrtsedu.lab
o User name: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the PuTTY shortcut located on the desktop of the console system.
3. Double-click the entry for lnxmaster.vrtsedu.lab under Saved Sessions.
4. Login to lnxmaster.vrtsedu.lab using the following credentials:
o User Name: root
o Password: P@ssw0rd

5. Ensure you obtain an Amazon S3 cloud provider IAM user account. You are going to use it to create a
cloud immutable storage.

Make sure that Amazon cloud administrators have the Required permissions.

6. Set the following environment variables by replacing "xxxx" and "yyyyyyyyyyyyy" with the AWS access key
associated with an IAM user and secret key associated with the access key.
o export MSDPC_ACCESS_KEY=xxxx
o export MSDPC_SECRET_KEY=yyyyyyyyyyyyy
o export MSDPC_REGION=us-east-1
o export MSDPC_PROVIDER=amazon
For Amazon S3, MSDPC_ACCESS_KEY is the AWS access key associated with an IAM
user. MSDPC_SECRET_KEY is the secret key associated with the access key. MSDPC_REGION is the AWS
region where the bucket will be created or accessed.
7. Create a cloud immutable volume using the following command:

/usr/openv/pdde/pdcr/bin/msdpcldutil create -b bucketname -v volumename --mode GOVERNANCE --min

1D --max 30D --live 2022-12-31

Replace the bucketname with the desired bucket name and volumename with the desired volume name.
Ensure both the values are unique.

The volume has live period property, which is a timestamp. The backup image retention time must be less
than this timestamp. If the live period expires, the volume stops and the backup job fails
If the command fails with The diffrence between the request time and the current time is too large error
message. Restart the chronyd service using the following command and retry the operation.

systemctl restart chronyd

8. Ensure that volume is created successfully message is displayed before proceeding to the next step.

9. List the cloud volumes using the following command:

/usr/openv/pdde/pdcr/bin/msdpcldutil list
10. Minimize the PuTTY session for lnxmaster.vrtsedu.lab.

Configuring the WORM capable disk pool and storage unit

10. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system.
11. Sign in to NetBackup Web UI using the following credentials:
o User Name: root
o Password: P@ssw0rd

12. In the left pane, navigate to Storage > Storage Configuration.

13. From the right pane, select Storage servers tab.
o Ensure that lnxmaster.vrtsedu.lab MSDP Storage server is WORM capable.
14. Select Disk pools tab, click Add.
15. Enter the following values in the Add disk pool page:
o Storage server name: lnxmaster.vrtsedu.lab (select this value using Change button)
o Disk pool name: worm_dpool
o Description: worm_dpool
o Limit I/O streams: mark the checkbox and type the I/O value as 35 per volume (change this value)
o Retain other default values.
16. Click Next.
17. In the Volumes tab, from the Volume drop-down list select Add volume.
18. Enter the volume name which was provided in step 6.
19. In the Cloud storage provider, select Amazon.

20. In the Region, select the appropriate region.

Select the Region where the cloud volume and bucket is residing.

21. Scroll down and enter the Access key ID and Secret acces key in the Access credentials section.
22. Scroll down and select the check box for Use object lock under WORM section.
23. Scroll down and click Retrive list under Cloud buckets section.

Ensure that bucket created in step 6 is visible.

24. Select the bucket and click Next.
25. In the Replication tab, do not select any value and click Next.
26. Verify the Review details and click Finish to configure worm_dpool disk pool.
27. Ensure that worm_dpool is created successfully. Click Close.

28. Click Add storage unit button. The Add MSDP storage unit page is displayed.
29. In the Basic Properties tab enter the following values and click Next.
o Storage unit name: worm-stu
o Maximum concurrent jobs: 35

30. In the Disk Pool tab, select the worm_dpool radio button and mark the checkbox for Lock until
expiration under Enable WORM section, and click Next.
31. In the Media Server tab, select the Manually select option and mark the checkbox
for lnxmaster.vrtsedu.lab server and click Next.
32. In the Review tab, verify the contents of worm-stu MSDP storage unit details and click Save.
33. In the Storage configuragation tab, ensure that worm-stu is created successfully.

Ensure that the Use WORM column displays the green tick mark for the newly created worm-stu.

Exercise B: Configuring a NetBackup policy

In this exercise, you create a NetBackup policy and use the WORM capable storage unit for backup. You then run a
manual backup using this policy.

Creating NetBackup policy

1. In the NetBackup Web UI, navigate to Protection > Policies.

2. On the Policies page, click Add.
3. Enter the policy name as Console_to_worm.
4. Refer to the following information, to create the policy.

Attribute Value

Policy Type MS-Windows

 Attribute Value

Policy Storage worm-stu

Go into effect set the current date as a previous day (If the current day is 16th July 2021, then set the
at previous date as 14th or 15th July 2021.)

Client console.vrtsedu.lab

Detect client operating system

Backup
E:\Anomaly
selection

Schedules Full

Retention: 1 week (Retention level 0)

5. Click Create to save the policy.

Performing Manual Backup to the WORM STU

6. Select the Console_to_worm policy checkbox and select Manual Backup.

7. Click OK in the Manual Backup window to start the backup job.
8. Click the Activity Monitor to monitor the progress of the backup job.
9. Ensure that the backup completes successfully. Mark the checkbox of the backup job and click View
details option.
10. Select the Details tab of the backup job to view the job details.
11. In the Details tab, use the Search bar to search worm lock information. In the Search bar type worm locks
and view the details.
 What is the duration of WORM lock applied to the backup image?

> It is set to 604800 seconds i.e 7 days.

This is the same value which you have set in the Retention period.

12. Click X to close the job details.

Exercise C: Understanding Catalog Operations on the WORM Backup Image

In this exercise, you perform the Catalog operations on WORM image copy.

1. In the NetBackup Web UI, in the left pane, click Catalog.

2. In the right pane, ensure the Action is set to Verify. Do not make any other changes and click Search.
3. Scroll down, in the results section click Show or hide columns drop down and mark the check boxes
for Immutable, Indelible and WORM Unlock time columns.
 Observe the values for 3 columns named Immutable, Indelible and WORM Unlock time for the first job
listed in the results. This is the job which you have initaited in Exercise B.

4. Mark the check box for the Backup ID which is Immutable and Indelible and click Expire.

5. In the Expire images dialog box, click Expire.

You will receive an Image Expire Error message.

6. Click View details button to view the error details.

 Backup image can not be expired because it is using WORM storage unit and the Retention period for this
backup image is set to 1 week. You can not expire the backup image before 1 week.

7. Click Close to close the Error details dialog box.

Exercise D: Configuring and Identifying Backup Anomaly

In this exercise, your configure NetBackup Anomaly and will run the backup job to identify the anomalies within
the backup metadata.

Viewing and Modifying Anomaly detection settings

1. In the NetBackup Web UI, in the left pane, click Detection and reporting > Anomaly detection.
2. In the Anomaly detection page, review the default values for each section.
3. In the Anomaly detection settings page, click Edit for Enable anomaly detection activities section.
4. In the Enable anomaly detection dialog box, select the radio button for Enable anomaly data
gathering, detection service and events.
5. Click Save in the Enable anomaly detection dialog box.
6. Close the Anomaly detection settings page.
7. Minimize the NetBackup Web UI.
8. Maximize the lnxmaster.vrtsedu.lab Putty session.

Starting multiple backup jobs

9. Navigate to the scripts directory using the following command:

cd /root/scripts

10. List the contents of the scripts directory using the following command:

ls -l
11. Run the console_backup_35jobs.sh script located in the scripts directory using the following command:

./console_backup_35jobs.sh

The script runs 35 manual backup jobs for the Console_to_worm policy with full schedule.

12. Minimize the lnxmaster.vrtsedu.lab Putty session.

13. Maximize the NetBackup Web UI.
14. In the NetBackup Web UI, in the left pane, click Activity monitor, ensure that all the jobs initiated by the
script are successful.

It may take 15-20 mins to finish all the 35 backup jobs. Do not proceed until all the backup jobs are complete.

15. Minimize the NetBackup Web UI.

Creating Test Anomaly files

16. On Console desktop, right-click the createfiles.ps1 file and click Run with PowerShell option.

This createfiles.ps1 script is used to create 200 Anomaly test files and later these files are copied
to: E:\Anomaly\anomaly2 directory on the Console client. Run this script after all the 35 backup jobs are
successful.

17. Maximize the NetBackup Web UI, click Protection > Policies.
18. In the Policies page, select Console_to_worm policy and click Manual backup.
19. In the Manual backup dialog box, click OK to start the manual backup job.
20. In the NetBackup Web UI, in the left pane, click Activity monitor, ensure that the backup job initiated in
the previous step is successful.

Ensure the job complete successfully.

Verifying Backup Anomaly

21. In the NetBackup Web UI, in the left pane, select Detection and reporting > Anomaly detection.
 o It may take 15-30 minutes to display the anomaly data.
o If required, use the Refresh button to refresh the Anomaly detection page for several times to verify
the Anomaly data.
o Do not proceed until you see the data.

22. Select the latest Job ID and verify the Anomaly data as illustrated.

Anomalies output:

23. Verify the output and take a look at each column data.

In Summary,
o You enabled the Anomaly detection settings to capture the various anomalies.
o You ran multiple backup jobs for a policy to create base data for the anomaly detection. The backup
job was backing up only single text file having size of 1 KB.
o You then created 200 anomaly files (size of each file was 4 MB), in the same directory which was the
backup selection for the policy you used to run multiple backup jobs.
o You ran another manual backup job of the same policy, this time backup job included those 200
anomaly files in the backup.
o NetBackup detect anomalies in backup metadata. It can detect any unusual job data in the data
backup flow. For example, it can detect a file count or a file size that is different than the usual count
or size.

24. You can mark the anomaly as:

o Mark as ignore
o Confirm as anomaly
o Report as false positive
Before moving to the next lab exercise ensure that you are deleting all the cloud resources which have been
created and used in this lab.

Exercise E: Configuring and Using NetBackup Malware Scanner

In this exercise, your configure NetBackup Malware Scanner settings and run the malware scan to find malware in
supported backup images and find the last good-known image which is malware free.

Configuration notes: Following are the tasks which have been pre-configured in this lab.

 NFS server is configured on lnxmedia.vrtsedu.lab

 NFS client is configured on lnxmaster.vrtsedu.lab
 NetBackup Malware Scanner is configured on lnxmaster.vrtsedu.lab

For configuration details refer to NetBackup Security and Encryption Guide

Configuring the malware detection settings

1. In the NetBackup Web UI, in the left pane, select Detection and reporting > Malware detection.
2. In the Malware detection page, click Configure a scanner host pool.
3. In the Malware scanner host pools page, click Add to add a new host pool.
4. In the Add malware scanner host pools page, enter the following details:
o Host pool name: MalwarePool
o Malware Scanner: NetBackup Malware Scanner
o Type of share: NFS

5. Click Save and add hosts button.

Adding a new host in a scan host pool

6. In the Manage malware scanner hosts page, click Add new.

7. In the Add malware scanner host page, enter Host name as lnxmaster.vrtsedu.lab.

8. Click Save and manage credentials button.

Managing credentials

9. In the Manage credentials page, select the radio button for Select existing credentials and click Next.
 Credentials have been pre-configured in this lab.

10. In the Select credentials section, select the radio button for Malware-scan-host-cred and click Select.
11. Click Finish to save the changes.

Running Manual backup

12. In the NetBackup Web UI, in the left pane, select Protection > Policies.
13. In the Policies page, type malware in the search bar to search the policy.

Malware-Test backup policy have been pre-configured in this lab.

14. Mark the check box for Malware-Test backup policy and click Activate.

Malware-Test backup policy is now activated.

15. Mark the check box for Malware-Test backup policy and click Manual backup.
16. In the Manual backup dialog box, click OK.
17. In the NetBackup Web UI, in the left pane, click Activity monitor.

Ensure the backup job for Malware-Test backup policy is successful. Do not proceed until job is succesful.

18. Minimize the NetBackup Web UI after job is successful.

Creating malware file

18. On the console desktop, double-click the PuTTY shortcut.

19. Double-click the entry for lnxmedia.vrtsedu.lab present under Saved Sessions.
20. Login to the lnxmedia.vrtsedu.lab server using the following credentials:
o Username: root
o Password: P@ssw0rd

21. Navigate to /etc/malwarefile directory using the following command:

cd /etc/malwarefile

Malicious Test File have been pre-configured in this lab.

22. List the contents of the /etc/malwarefile directory using the following command:

ls -l
23. Move the file present in the /etc/malwarefile directory to the /etc/testfolder/ using the following
command:

mv eicar.com /etc/testfolder/

24. List the contents of the /etc/testfolder/ directory using the following command:

ls -l /etc/testfolder/

You will have two files present named eicar.com and testfile.txt.

25. Minimize the lnxmedia.vrtsedu.lab PuTTY session.

Running Manual backup with malware file

25. Maximize the NetBackup Web UI

26. In the NetBackup Web UI, in the left pane, select Protection > Policies.
27. In the Policies page, type malware in the search bar to search the policy.
28. Mark the check box for Malware-Test backup policy and click Manual backup.
29. In the Manual backup dialog box, click OK.
30. In the NetBackup Web UI, in the left pane, click Activity monitor.

Ensure the backup job for Malware-Test backup policy is successful. Do not proceed until job is succesful.

Performing Malware scanning

31. In the NetBackup Web UI, in the left pane, select Detection and reporting > Malware detection.
32. In the Malware detection page, click Scan now.
33. In the Malware scan page, select the radio button for lnxmedia.vrtsedu.lab client and click Next.
34. In the Malware scan page, click select scan host pool present under Select a malware scanner host
pool.
35. In the Select a malware scanner host pool dialog box, select the radio button for MalwarePool and
click Select.
36. Leave all other values to their default value and click Scan now.
37. You will be automatically directed to Malware detection page.
38. You will see two malware scan jobs in the Malware detection page.

Malware scan jobs may take 10-15 minutes to complete. One job will have Scan result as Not Impacted and
the other job will have Scan result as Impacted.
Viewing Malware scanning result

39. In the Malware scan page, You will see one job is having Scan result as Not Impacted and the other job
is having Scan result as Impacted.
40. Click the vertical ellipsis for the Impacted job and select View infected files.

41. In the Infected files diaog box, you will see the infected file name.
 This is the file you have moved in step 23.

42. Click Close to close the Infected files diaog box.

In Summary,
o You configured the malware detection settings.
o You added a new host in a scan host pool.
o You ran manual backup which was having single text file as a backup selection.
o You created a test malicious file and moved that file to the same backup location.
o You ran another manual backup which was having single text file and the test malicious file as a
backup selection.
o You performed malware scan on those two backup images.
o You viewed the malware scan result for the Impacted backup image.
o The backup image which is Not Impacted can be treated as a last known good backup.
Before ending the lab ensure that you are deleting all the cloud resources which have been created and used in
this lab.

Lab 15: Generating NetBackup Reports

Exercise A: Using the NetBackup Reports Utility

In this exercise, you run several NetBackup reports that can provide useful information for troubleshooting
NetBackup-related problems. These reports include the:

 Status of Backups report

 Client Backups report
 Problems report
 All log entries report
 Media Logs report
 Tape Reports
 Disk Reports
 Vault Reports

The policies in this lab environment have a limited retention period. After the retention period is over, the images
are deleted from the backup media and are not be available for reports. If you are not able to find the required
backup images, re-run the manual backup job as explained in Lab 07: Configuring Media Server Deduplication
(Exercise C).
You are recommended to perform the following reports on NetBackup Administration Console.
Running the Status of Backups report

In the steps that follow, you initiate the Status of Backups report from the NetBackup Administration
Console and view the report output.

1. Sign in to the console system using the following credentials.

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Locate and double-click the NetBackup 10.0 Administration Console shortcut, located on the desktop
of the console.vrtsedu.lab system.
3. In the NetBackup Administration Console, login using the following credentials:
o Host name: lnxmaster.vrtsedu.lab
o Username: root
o Password: P@ssw0rd

4. Select NetBackup Management and then select Reports in the left pane of the Administration Console.
5. Expand the Reports entry in the left pane of the Administration Console.

The following reports are listed below the expanded reports object:

o Status of Backups
o Client Backups
o Problems
o All Log Entries
o Images on Media
o Media Logs
o Tape Reports
o Disk Reports
o Vault Reports
6. Click the entry for the Status of Backups report in the left pane of the Administration Console.

The right pane of the Administration Console displays the Report Settings that can be used to filter the
output of the report.

7. Under the Date/Time Range, click the check box for Earliest available.
8. Click the Run Report button.

The output of the report is displayed on the bottom half of the right pane of the Administration Console.
 The backups that were performed in previous labs may not be present in the output of the reports as they
had limited retention period.

9. View the output of the report, and take note of the information that is provided by the report
10. If you wish, change the Report Settings for the report, and run the report again to see impact on the
report output.
11. Note that you can change the report settings to obtain output such as:
o List all the jobs that ran in a specified time period.
o List all the jobs that used a specified NetBackup media server.
o List all the jobs that were associated with a specific NetBackup client.
o Run the report to find the entry for a specific Job ID.
12. Under Status of Backups pane (in the right pane), select the required rows of the report you want to
copy by holding down the Shift or Ctrl key.
13. Right-click on any one of the selected row and click Copy to Clipboard option.
14. Open Notepad and paste the selected rows that you copied in previous step 13. Save the text file on the
desktop with name as StatusOfBackups_Report.txt file.
15. Review the contents of the copied reports (you copied in step 14) and later close the text file.

Whenever you run the reports for any feature, you can repeat these steps 13-15 for the upcoming exercises.

Running the Client Backups report

In the steps that follow, you initiate the Client Backups report from the NetBackup Administration Console and
view the report output.

16. Select the entry for the Client Backups report in the left pane of the Administration Console.

The right pane of the Administration Console displays the Report Settings that can be used to filter the
output of the report.

17. In the Date/Time Range section, check the Earliest available check box.
18. Leave the rest of the report settings at their defaults, and click the Run Report button to run the Client
Backups report.
19. View the output of the report, and take note of the information that is provided by the report.
 The backups that were performed in previous labs may not be present in the output of the reports as they
had limited retention period.

Running the Problems report

In the steps that follow, you initiate the Problems report from the NetBackup Administration Console and view
the report output.

20. Select the entry for the Problems report in the left pane of the Administration Console.

The right pane of the Administration Console displays the Report Settings that can be used to filter the
output of the report.

21. Click the Run Report button to run the Problems report using the default settings.

If no information is displayed then select the Earliest available check box and re-run the report again.

22. View the output of the report, and take note of the information that is provided by the report. Most of the
entries are probably warnings and not serious problems.
Running the All Log Entries report

In the steps that follow, you initiate the All Log Entries report from the NetBackup Administration Console and
view the report output.

23. Select the entry for the All Log Entries report in the left pane of the Administration Console.

The right pane of the Administration Console displays the Report Settings that can be used to filter the
output of the report.

24. Click the Run Report button to run the All Log Entries report using the default settings.

If no information is displayed then select the Earliest available check box and re-run the report again.

25. View the output of the report, and take note of the information that is provided by the report.
Running the Media Logs report

In the steps that follow, you initiate the Media Logs report from the NetBackup Administration Console and
view the report output.

26. Select the entry for the Media Logs report in the left pane of the Administration Console.

The right pane of the Administration Console displays the Report Settings that can be used to filter the
output of the report.

27. In the Date/Time Range section, check the Earliest available check box.
28. Click the Run Report button to run the Media Logs report using the default settings.
29. View the output of the report, and take note of the information that is provided by the report.
Similarly, you can perform the same task for these reports: Tape Reports, Disk Reports, and Vault Reports.

For Example:

Disk Reports > Images on Disk

Disk Reports > Disk Logs
Exercise B: Configuring OpsCenter Data Collection for NetBackup

In this exercise, you configure OpsCenter data collection for NetBackup.

Adding an OpsCenter server in the NetBackup Administration Console

1. In the NetBackup Administration Console, from the left pane navigate to NetBackup
Management > Host Properties > Master Servers.
2. From the right pane, right-click on lnxmaster.vrtsedu.lab and select Properties.

If required, right-click on lnxmaster.vrtsedu.lab and select Connect, then select the Properties option.

3. In the Properties pane, click Servers.

4. From the right pane select OpsCenter Servers tab, and then click Add.
5. Enter the server name as console.vrtsedu.lab (which is OpsCenter VM name), and click Add.

6. Click Close to exit the window.

7. Click Apply and later click OK to update the Master server properties window.
8. Minimize the NetBackup Administration Console.
9. Double click the PuTTY icon located on the desktop of console system, and connect
to lnxmaster.vrtsedu.lab using the following credentials.
 o Username: root
o Password: P@ssw0rd
10. Run the following command and verify that OpsCenter server entry is added in the bp.conf file.

cat /usr/openv/netbackup/bp.conf | grep -i name

11. Minimize the putty window.

Adding a Primary/Master server in the OpsCenter console

12. Locate and double-click the NetBackup OpsCenter Login shortcut, located on the desktop of console
system.

Upon startup, it may take some time for the OpsCenter services to start, and to become available for the Web
browser connection. If you receive a connection error, wait a few moments and attempt the browser
connection again. If you still receive the connection error, restart all OpsCenter services using Services.

13. Click Advanced at the Warning message and click Accept the Risk and Continue to proceed.
14. When the Veritas NetBackup OpsCenter Analytics Version 10.0 login screen is displayed, login to
OpsCenter using the following credentials:
o Username: admin
o Password: P@ssw0rd
o Domain: OpsCenterUsers(vx)

If you receive an error message while trying to connect to the OpsCenter Server, then refresh the Web
browser or close the Firefox Web browser and launch NetBackup OpsCenter Login shortcut again.

Within a few moments the OpsCenter Web user interface is displayed in the browser window.
15. In the OpsCenter console, select Settings > Configuration > NetBackup .
16. Click Add button.
17. Enter the following details to add NetBackup Master server to OpsCenter.
o NetBackup Master Server Name: lnxmaster.vrtsedu.lab
o Display Name: lnxmaster.vrtsedu.lab (auto-populates)
o NetBackup User Name: root
o NetBackup Password: P@ssw0rd

18. Click the Test Connection button to validate the information that you entered. This would validate the
credentials for the Primary/Master server.
19. Click Save and Close to save and update the Primary/Master server details in OpsCenter.
20. Select lnxmaster checkbox and click Enable Data Collection option. OpsCenter utilize this option to
collect the data from NetBackup master server: lnxmaster.

21. Once the data collection is completed, OpsCenter takes few mins (3-5 mins) to update the status.
 22. Select the Monitor tab and ensure that lnxmaster was added under ALL MASTER SERVERS column, from
the right pane verify that job summary status are displayed in the graphical representation mode.

How OpsCenter collects data from NetBackup? OpsCenter is used to monitor, manage, and report on
NetBackup master and media servers, clients, and policies. To perform the monitoring, management, and
reporting functions, OpsCenter collects data from the NetBackup master servers. The NetBackup data
collection and management logic that OpsCenter uses is built into NetBackup master servers. This logic is
included in the NetBackup Service Layer (NBSL). OpsCenter only uses the NBSL on master servers for data
collection. Though NBSL is also included on media servers, OpsCenter does not use it. You must add only
master servers to the OpsCenter console. You must not add any media servers to the OpsCenter console.

Exercise C: Generating Reports Using OpsCenter

This exercise is created for those who are interested in using OpsCenter to monitor and manage their NetBackup
environments.

The policies in this lab environment have a limited retention period. After the retention period is over, the images
are deleted from the backup media and are not be available for reports. If you are not able to find the required
backup images, re-run the manual backup job as explained in Lab 07: Configuring Media Server Deduplication
(Linux) (in Exercise C).
In this Exercise C, you monitor the reports on Deduplication Reports feature, the report task will be similar for other
NetBackup Reports. For detailed information on OpsCenter Reports you are recommended to verify the
NetBackup OpsCenter Reporting Guide.
The report data sheet will vary based on the date and time you provided while generating the report.

Running deduplication-related reports in OpsCenter

1. Click the Reports tab in the OpsCenter console.

2. Under the Report Templates folder, displayed in the left column of the OpsCenter user interface, locate
and expand the entries for the Deduplication Reports and for the Disk & Tape Device Activity Reports.
3. The list of standard Deduplication Reports is displayed, as illustrated in the figure below.

Deduplication Reports

4. Click the entry for the Deduplication Size Savings report to run the report.
5. Note the output of the report that is displayed in the right pane of the OpsCenter Web interface.
6. Click the entry for the Pre vs. Post Deduplication Size report, to run the report.
7. Note the output of the report that is displayed in the right pane of the OpsCenter Web interface. Also,
verify that the report is generated in graphical representation view.
8. You may run other standard Deduplication Reports that are provided in OpsCenter as time permits.

If required, try to run the reports for Audit, Backup, Catalog, Client, and Media etc. By selecting the required
report options (under Report Templates) from the left pane of NetBackup OpsCenter console.

Disk and Tape Device Activity Reports

9. Under the Disk & Tape Device Activity Reports folder in the left pane of the OpsCenter Web user
interface click the entry for the Current Disk Pool Usage report, to run the report.
10. Note the output of the report that is displayed in the right pane of the OpsCenter Web interface.
11. Click the entry for the Storage Unit Usage report (located in the Disk & Tape Device Activity
Reports folder), to run the report.
12. Note the output of the report that is displayed in the right pane of the OpsCenter Web interface.
13. Click the entry for the Disk Usage report (located in the Disk & Tape Device Activity Reports folder), to
run the report.

14. Again, click the entry for the Current Disk Pool Usage report (located in the Disk & Tape Device
Activity Reports folder), to run the report.
15. Select Save As Report option.

16. A new Save Report window is displayed, enter the following values and click OK to close the window.
o Report Name: Disk Pool usage Report
o Description: Disk pool usage Report
o Folder: Private Reports
o Overwrite if report already exists in the selected folder : select the check box
17. From the right pane select Export Report option.
18. Click OK to save this report in PDF format and in tabular content method.

19. Select the Save File option and click OK to save.

20. In the ExportReportAction.spring window, click on Download icon to download the report.
21. Click Save to Save the report.
22. Open the downloaded PDF report in Acrobat format and view the contents of the Disk Pool usage report.
23. Close the PDF and minimize the File Explorer window.

The reports you have run are just a few of the standard reports that are provided in OpsCenter. Run
additional OpsCenter reports as time permits.

24. Close the firefox window.

Creating a Report using an existing report template

25. Locate and double-click the NetBackup OpsCenter Login shortcut, located on the desktop of console
system.
26. Click Advanced at the Warning message and click Accept the Risk and Continue to proceed.
27. When the Veritas NetBackup OpsCenter Analytics Version 10.0 login screen is displayed, login to
OpsCenter using the following credentials:
o Username: admin
o Password: P@ssw0rd
o Domain: OpsCenterUsers(vx)
28. Navigate back to OpsCenter console, select Reports > select My Reports tab > click on Create New
Report option.
29. In the Select Report Creation Option screen, select the default Use an existing report template option.
Click Next to continue.

For custom report creation you will require a licensed verion of OpsCenter.

30. In the Select Report template option screen, select Deduplication Reports, select Deduplication Size
Savings option and click Next to continue.
31. In the Select Parameters option screen, select Absolute TimeFrame period, and set the from date
as 31/March/2021 and to the current date.
32. In the Time Frame Grouping pane, set the value as follows:

Time Frame Group by: 1 Months of Year (from drop-down list select this option)

33. In the Filters pane, set the following values:

View: ALL MASTER SERVERS, lnxmaster.vrtsedu.lab

Master Server: Column as Master Server, Operator as =, Value as lnxmaster.vrtsedu.lab

Media Server: Column as Media Server, Operator as =, Value as lnxmaster.vrtsedu.lab ->

lnxmedia.vrtsedu.lab
34. Retain the other default values and click Next to continue.

For this Filters step, you select View, Master Server, and Media Server options (only).

35. In the Modify Display Options screen retain the default values and click Next to continue.
36. In the View Report Data screen, check the Historical and Ranking tab options to check the graphical
representation of the report data. Click Next to continue.
37. In the Save Report screen, enter the following values and retain other default settings and
click Save option to save the report.
o Report name: Lab 15: Deduplication Report
o Description: Deduplication Report
o Folder: My Reports > Private Reports
38. Click Finish to generate the report.

The report data sheet will vary based on the date and time you provided during the step 4.

Creating a Custom Report

39. Navigate back to OpsCenter console, select Reports > select My Reports tab > click on Create New
Report option.
40. In the Select Report Creation Option screen, select Create a custom report option and click Next to
continue.

41. In the Select Report Category screen, enter the following values and click Next to continue.
o Category: Backup/Recovery
o Subcategory: Job/Image/Media/Disk
o Report View Type: Tabular
42. In the Select Parameters option screen, select Absolute TimeFrame period, and set the from date
as 31/March/2021 and to the current date. Retain the other default values.
43. In the Filters pane, set the following values:

View: ALL MASTER SERVERS, lnxmaster.vrtsedu.lab

Master Server: Column as Master Server, Operator as =, Value as lnxmaster.vrtsedu.lab

Media Server: Column as Media Server, Operator as =, Value as lnxmaster.vrtsedu.lab ->

lnxmedia.vrtsedu.lab

44. Click Next to continue.

45. In the Modify Display Options screen, enter the following values:
 o Description: This is the Backup/Recovery report.
o Report On: <Default Option>
o Time Basis: Job End Time
o Display Unit: MB
o Time Duration: Days

46. Select the check box for these four Available Columns: Master Server, Media Server, Deduplication
Enabled, and Deduplication Rate. Do not select other columns which is not required for this report.
47. Click the Add button and move the Deduplication and backup properties to the Selected Columns list
and enter the following values:
o Master Server: Master Server, Ascending, Distinct Count
o Media Server: Media Server, Ascending, Distinct Count
o Deduplication Enabled: Deduplication Enabled, Ascending, Total
o Deduplication Rate: Deduplication Rate, Ascending, Percentage
48. Select the check box for these four Selected Columns: Master Server, Media Server, Deduplication
Enabled, and Deduplication Rate.

49. Retain the default values in the Conditions section and click Next to continue.
50. In the View Report Data Screen, click Show Report Query option to veirfy the dedupe data list.
51. Verify the Backup and recovery report and close the window. Click Next to continue.

52. In the Save Report screen, enter the following values and retain other default settings and
click Save option to save the report.
o Report name: Deduplication Report
o Description: Backup and Recovery Report
o Folder: My Reports > Public Reports

53. Click Finish to generate the report.

Creating a report using SQL query

54. Navigate back to OpsCenter console, select Reports > select My Reports tab > click on Create New
Report option.
55. In the Select Report Creation option screen, select Run SQL Query option and click Next to continue.
56. In the SQL Query screen, enter the following SQL query command to view all NetBackup master servers
that monitored and managed by OpsCenter. Click Next to continue.

select * from domain_masterserver

57. View the report and click Next to continue.

58. In the Save Report screen, enter the following values and retain other default settings and
click Save option to save the report.
o Report name: SQL Report
o Description: NetBackup SQL Report
o Folder: My Reports > Public Reports
59. Click Finish to generate the report.
60. Run another SQL query using the following SQL command:

SELECT domain_JobArchive.policyname as "Policy", domain_JobArchive.statuscode as "Status",

UTCBigIntToNomTime(domain_JobArchive.startTime) as 'Start Time',
UTCBigIntToNomTime(domain_JobArchive.endTime) as 'End Time' FROM domain_jobarchive WHERE
domain_JobArchive.type in (0) AND (domain_JobArchive.parentjobid = domain_JobArchive.id) ORDER
BY 'Start Time'
61. Ensure that you will view the similar report:

62. Click the Logout button, located in the upper-right corner of the OpsCenter Web user interface to log
out of the OpsCenter Server.
63. Close the Mozilla Firefox browser window.

Lab 16: Upgrading and Updating NetBackup

Exercise A: Populating the Repository with NetBackup Packages

In this exercise, you add VxUpdate packages to the NetBackup package repository.

Download Veritas Netbackup approved media server and client packages

VxUpdate formatted packages are available from the myveritas.com licensing portal. You can download the
packages and place them in a location accessible to the Primary/Master server.

For the purpose of this lab, the packages have already been downloaded to the Primary/Master
server, winmaster.vrtsedu.lab.

We will now add the packages to the Netbackup package repository. The VxUpdate command can be used only if
Veritas signed packages are added to the NetBackup package repository.
Add packages to the NetBackup package repository

In the steps that follow, you add the VxUpdate packages to the Netbackup repository.

1. Log in to the winmaster system using the following credentials:

o UserID: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the Command Prompt shortcut located on the desktop of

the winmaster.vrtsedu.lab system to launch Command Prompt.
3. In the Command Prompt window, enter the following command and press Enter.

Command: nbrepo

o The nbrepo command is used to manage the NetBackup package repository.

o You can add, validate, and delete packages, obtain package identifier and other information on
packages in the repository.

The nbrepo command is located in the install_path\NetBackup\var\global\repo directory on the

Primary/Master server. In this lab environment, this directory is added to the PATH variable on the
Primary/Master server system and therefore the command can be executed without using the absolute path.

In this exercise, we add packages for both the Windows and Linux clients to the NetBackup repository. These
packages will be used further in this lab.

4. In the Command Prompt window, enter the following command to add the Windows client package and
press Enter.

Command: nbrepo -a E:\VxUpdateFiles\vxupdate_nb_10.0_windows_x64.sja

This operation takes a few minutes.

The command syntax to add a package is nbrepo -a package_path. In this lab environment, the VxUpdate
packages are already copied to the location, E:\VxUpdateFiles, on this system.
5. In the Command Prompt window, a message is displayed saying that package has been successfully
added to the repository.
6. To add the Linux client package to the NetBackup repository, enter the following command and
press Enter.

Command: nbrepo -a E:\VxUpdateFiles\vxupdate_nb_10.0_redhat_x64.sja

This operation takes a few minutes.

7. In the Command Prompt window, a message is displayed saying that package has been successfully
added to the repository.

Verify the presence of VxUpdate packages in the NetBackup repository

8. In the Command Prompt window, type the following command to list the VxUpdates packages available
on the Primary/Master server.

Command: nbrepo -l

Two packages that were added earlier are displayed. Observe the ID number associated with the client
packages.
o Windows server and client package ID: 1
o Linux server and client package ID: 8

9. You can also view the details for a particular VxUpdate package. In the Command Prompt window,
execute the following command to view the details of the Windows client package.

Command: nbrepo -p 1

10. Execute the following command to view details of the Linux client package.

Command: nbrepo -p 8

Deleting the VxUpdate packages in the NetBackup repository

You can remove packages from the repository either when they are no longer needed or to conserve disk space.

In this exercise, we are only mentioning the command to delete packages from the NetBackup repository. Do not
execute the command in the this lab.

To delete a VxUpdate package from the NetBackup repository, the command syntax is nbrepo -d package
identifier.
Exercise A: Populating the Repository with NetBackup Packages

In this exercise, you add VxUpdate packages to the NetBackup package repository.

Download Veritas Netbackup approved media server and client packages

VxUpdate formatted packages are available from the myveritas.com licensing portal. You can download the
packages and place them in a location accessible to the Primary/Master server.

For the purpose of this lab, the packages have already been downloaded to the Primary/Master
server, winmaster.vrtsedu.lab.

We will now add the packages to the Netbackup package repository. The VxUpdate command can be used only if
Veritas signed packages are added to the NetBackup package repository.

Add packages to the NetBackup package repository

In the steps that follow, you add the VxUpdate packages to the Netbackup repository.

1. Log in to the winmaster system using the following credentials:

o UserID: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the Command Prompt shortcut located on the desktop of

the winmaster.vrtsedu.lab system to launch Command Prompt.
3. In the Command Prompt window, enter the following command and press Enter.

Command: nbrepo

o The nbrepo command is used to manage the NetBackup package repository.

o You can add, validate, and delete packages, obtain package identifier and other information on
packages in the repository.
 The nbrepo command is located in the install_path\NetBackup\var\global\repo directory on the
Primary/Master server. In this lab environment, this directory is added to the PATH variable on the
Primary/Master server system and therefore the command can be executed without using the absolute path.

In this exercise, we add packages for both the Windows and Linux clients to the NetBackup repository. These
packages will be used further in this lab.

4. In the Command Prompt window, enter the following command to add the Windows client package and
press Enter.

Command: nbrepo -a E:\VxUpdateFiles\vxupdate_nb_10.0_windows_x64.sja

This operation takes a few minutes.

The command syntax to add a package is nbrepo -a package_path. In this lab environment, the VxUpdate
packages are already copied to the location, E:\VxUpdateFiles, on this system.

5. In the Command Prompt window, a message is displayed saying that package has been successfully
added to the repository.
6. To add the Linux client package to the NetBackup repository, enter the following command and
press Enter.

Command: nbrepo -a E:\VxUpdateFiles\vxupdate_nb_10.0_redhat_x64.sja

This operation takes a few minutes.

7. In the Command Prompt window, a message is displayed saying that package has been successfully
added to the repository.

Verify the presence of VxUpdate packages in the NetBackup repository

8. In the Command Prompt window, type the following command to list the VxUpdates packages available
on the Primary/Master server.

Command: nbrepo -l

Two packages that were added earlier are displayed. Observe the ID number associated with the client
packages.
o Windows server and client package ID: 1
o Linux server and client package ID: 8

9. You can also view the details for a particular VxUpdate package. In the Command Prompt window,
execute the following command to view the details of the Windows client package.

Command: nbrepo -p 1
 10. Execute the following command to view details of the Linux client package.

Command: nbrepo -p 8

Deleting the VxUpdate packages in the NetBackup repository

You can remove packages from the repository either when they are no longer needed or to conserve disk space.

In this exercise, we are only mentioning the command to delete packages from the NetBackup repository. Do not
execute the command in the this lab.

To delete a VxUpdate package from the NetBackup repository, the command syntax is nbrepo -d package
identifier.

Exercise B: Configuring a Deployment Policy

In this exercise, you create a deployment policy.

1. Log in to the console.vrtsedu.lab system using the following credentials.

o UserID: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the NetBackup 10.0 Administration Console shortcut located on the desktop of
the console.vrtsedu.lab system to launch the NetBackup Administration Console.
3. In the NetBackup Administration Console window displayed, login using the following credentials:
o Host name: winmaster.vrtsedu.lab
o User name: VRTSEDU\Administrator
o Password: P@ssw0rd

4. In the Netbackup Administration Console, on the left-pane, select Deployment Management >
Deployment Policies.

Currently, no deployment policy is configured on the NetBackup Administration Console.

In this lab, we deploy two separate policies for Windows and Linux client systems. First we will deploy the
policy for windows client.

5. Under the Deployment Policies field, right-click and select New Deployment Policy from the short-cut
menu.
6. In the Add a New Deployment Policy dialog box, enter the Policy
name as Deploy_Policy_winclient and click OK.

The Change Deployment Policy - Deploy_Policy_winclient dialog box is displayed.

 In this lab, we deploy policies for Windows and Linux client systems.

7. In the Change Deployment Policy - Deploy_Policy_winclient dialog box, under the Attributes tab,
perform the following actions:
o Package: Click the drop-down arrow and select NetBackup 10.0 Client.
o Media server: Ensure that the winmaster.vrtsedu.lab is selected.
o Java GUI and JRE: Retain the default selection.
o In the Select host field, a list of available hosts is displayed. Perfrom the following steps:
o Select the hosts, winvm1.vrtsedu.lab
o Click the Add >> button.

The client virtual machine is added to the Selected hosts field.

8. Click the Schedules tab.

9. Click New. The Add Deployment Schedule - Policy Deploy_Policy_winclient is displayed.
10. In the Add Deployment Schedule - Policy Deploy_Policy_winclient dialog box, enter the following
information:
o Name: Schedule
o Type: Click the drop-down arrow and select Install
o Duration: 7 days
o Starts: Current time + 4 hours

You can find the current time on the taskbar of console.vrtsedu.lab.

11. In the Add Deployment Schedule - Policy Deploy_Policy_winclient dialog box, click OK.
12. In the Change Deployment Policy - Deploy_Policy_winclient dialog box, click OK.

Now configure the deployment policy for linux clients.

13. Under the Deployment Policies field, right-click and select New Deployment Policy from the short-cut
menu.
14. In the Add a New Deployment Policy dialog box, enter the Policy
name as Deploy_Policy_lnxclient and click OK.

The Change Deployment Policy - Deploy_Policy_lnxclient dialog box is displayed.

15. In the Change Deployment Policy - Deploy_Policy_lnxclient dialog box, under the Attributes tab,
perform the following actions:
o Package: Click the drop-down arrow and select NetBackup 10.0 Client.
o Media server: Ensure that the winmaster.vrtsedu.lab is selected.
o Java GUI and JRE: Retain the default selection.
o In the Select hosts field, a list of available hosts is displayed. Perfrom the following steps:
o Select the host lnxvm1.vrtsedu.lab.
o Click the Add >> button.
 The client virtual machine is added to the Selected hosts field.

16. Click the Schedules tab.

17. Click New. The Add Deployment Schedule - Policy Deploy_Policy_lnxclient is displayed.
18. In the Add Deployment Schedule - Policy Deploy_Policy_lnxclient dialog box, enter the following
information:
o Name: Schedule
o Type: Click the drop-down arrow and select Install
o Duration: 7 days
o Starts: Current time + 4 hours

You can find the current time on the taskbar of console.vrtsedu.lab.

19. In the Add Deployment Schedule - Policy Deploy_Policy_lnxclient dialog box, click OK.
20. In the Change Deployment Policy - Deploy_Policy_lnxclient dialog box, click OK.

Exercise C: Manually Initiating Upgrades from the Primary Server Using

VxUpdate

In this exercise, we manually upgrade the client on the winvm1.vrtsedu.lab system from version 9.1 to 10.0.”

First, The client winvm1.vrtsedu.lab will be upgraded using the existing deployment
policy Deploy_Policy_winclient from the NetBackup Administration Console.

1. In the NetBackup Administration Console, click Security Management > Host Management.

Observe that the NetBackup software version on the

clients, winvm1.vrtsedu.lab and lnxvm1.vrtsedu.lab is 9.1.

Manually upgrading the media servers or clients in a policy from the NetBackup Administration
Console

2. Select Deployment Policies and right-click Deploy_Policy_winclient.

3. From the context menu, select Manual Deployment…

You can also run the policy by selecting Actions > Manual Deployment

4. The Manual Deployment dialog box is displayed.

Ensure the following:

 o Schedule is listed under the Select the schedule you want to use field.
o In the Select one or more hosts you want to upgrade. If you select no hosts, all hosts are
upgraded field, the following host is listed:
 winvm1.vrtsedu.lab

Select the host winvm1.vrtsedu.lab.

5. In the Manual Deployment dialog box, click OK.

6. In the NetBackup Administration Console, click Activity Monitor.
7. Ensure that the deployment job is successfully executed.

The operation takes a few minutes.

8. In the NetBackup Administration Console, click Security Management > Host Management.
9. Click the Refresh icon and observe the NetBackup software version on the client, winvm1.vrtsedu.lab has
changed to 10.0.

Exercise D: Initiating Upgrades from the Client Using VxUpdate

In this exercise, you initiate an upgrade from the client using VxUpdate. You will initiate a deployment job based
on an existing policy. We will use the nbinstallcmd command to initiate the deployment policies from the
command line. This command is located on all hosts in the NetBackup environment.

1. Double-click the PuTTY shortcut located on the desktop of the console.vrtsedu.lab system.
2. When the PuTTY Configuration window is displayed, double-click the pre-configured entry for the
client, lnxvm1.vrtsedu.lab to open an SSH session with the Linux-based system.
o NetBackup client server name: lnxvm1.vrtsedu.lab
o User name: root
o Password: P@ssw0rd

3. Enter the following command in the terminal window,

Command: nbinstallcmd -policy Deploy_Policy_lnxclient -schedule Schedule -master_server

winmaster.vrtsedu.lab

The nbinstallcmd is present in the following directory,

o Windows: install_path\netbackup\bin
o Linux: /usr/openv/netbackup/bin

Command syntax: nbinstallcmd -policy policy name -schedule schedule name -master_server master
server name

If the job initiated successfully, you are returned to the command prompt without any error message.
 4. In the NetBackup Administration Console, click Activity Monitor.
5. Ensure that the deployment job is successfully executed.

The operation takes a few minutes.

6. In the NetBackup Administration Console, click Security Management > Host Management.
7. Click the Refresh icon and observe the NetBackup software version on the client, lnxvm1.vrtsedu.lab has
changed to 10.0.

It will take a few moments for the version to be updated in the NetBackup Administration console.

Exercise E: Viewing Deployment Job Status

In this exercise, you check the status of the deployment job.

1. Log in to the console.vrtsedu.lab system.

2. Launch the NetBackup 10.0 Administration Console window, if not already launched.
3. Select Activity Monitor in the left-pane of the Administration Console window.

The Deployment jobs that were executed in this lab are listed. The jobs are listed as a Deployment type.

4. Double-click the deployment job for the client, winvm1.vrtsedu.lab.

5. The Job Details dialog box is displayed.

Observe the status message.

The client is winvm1.vrtsedu.lab and Primary/Master Server is winmaster.vrtsedu.lab

6. In the Job Details dialog box, click the Detailed Status tab.
7. Scroll in the Status field and observe the various operations that have been executed during the job.

You can also view the details for the deployment job for the lnxvm1.vrtsedu.lab system.

8. Close the Job Details dialog box.

Lab 17: Collecting Logs and Diagnostic Information

Exercise A: Viewing the NetBackup Services

In this exercise, you use the Activity Monitor to view the status of NetBackup services on NetBackup server
systems.

1. Login to the console system using the following credentials.

User name: VRTSEDU\Administrator

Password: P@ssw0rd

2. Double-click the NetBackup Web UI login shortcut located on the desktop of the console.vrtsedu.lab
system.
3. Sign in to the NetBackup web user interface using the following credentials.

User name: root

Password: P@ssw0rd

4. In the NetBackup web user interface, in the navigation pane, click Activity monitor.

The Activity monitor is displayed in the right pane and it has three tabs. Jobs, Daemons and Processes.

5. Click the Daemons tab.

6. Take note of the Daemons or Services that are listed.

Some daemons listed may have a status of Stopped or Disabled. This may be normal, as some daemons are
enabled only when a particular NetBackup feature is licensed or enabled. Also remember that some daemons
run only on the Primary/Master server and will always be shown as Disabled on media servers.
Interdependencies exist between NetBackup Services and Daemons. It is advised to use the NetBackup-
provided command line tools to stop and restart NetBackup. These command line tools stop and start
NetBackup Services and Daemons in the proper sequence.
You can also use the NetBackup-provided command, bpps, to view the NetBackup processes and services
that are running on a NetBackup server or client system. On Linux-based systems, the bpps -x command
syntax is useful, and on Windows-based systems, simply use the command, bpps.
Do not stop or start any NetBackup services or daemons at this time.

7. Minimize the **NetBackup web user interface. You will return to it in the next exercise.
Exercise B: Using the nbsu and nbcplogs Commands

Collection of debug logs and other associated NetBackup troubleshooting information is an activity that should
always be undertaken with the guidance of a Veritas NetBackup Technical Support Engineer or of technical
support personnel of a Veritas Support Partner.

In this exercise, you use the NetBackup Support Utility (nbsu) and NetBackup Copy Logs (nbcplogs)
commands to collect troubleshooting information and NetBackup log files.

The output files generated by these NetBackup utilities can be uploaded to Veritas, for analysis by NetBackup
technical support representatives to assist you in solving NetBackup and NetBackup-related problems.

Running the NetBackup Support Utility (nbsu)

The NetBackup Support Utility (nbsu) queries the system on which it is executed and gathers NetBackup and
operating system diagnostic information. The nbsu utility provides a wide range of control over the types of
diagnostic information gathered.

1. Double-click the PuTTY shortcut located on the desktop of the console.vrtsedu.lab system.
2. In the PuTTY configuration window that is displayed, double-click the preconfigured entry for the
Primary/Master server, lnxmaster.vrtsedu.lab.
3. Log in to the lnxmaster.vrtsedu.lab system using the following credentials.

User name: root

Password: P@ssw0rd

4. In the Terminal window, type the following command and press Enter, to display help information on the
use of the nbsu utility.

Command: nbsu -help

nbsu -help displays an extensive description of the utility and of the options that are available when
performing the command.
To facilitate the execution of NetBackup commands without the need to navigate to the folder or directory
that houses the command, it is recommended that you set the PATH environment variable on NetBackup
servers to include the folders and directories that house commonly used NetBackup commands.
In this lab environment, the PATH environment variable has already been set on the Primary/Master server
and media server systems to include the folder location to the nbsu and nbcplogs utilities.
The following table provides a brief description of the phases that are performed during the execution of
the nbsu utility.
 Phase Description

Phase I Determine operating system environment information

Phase II Determine NetBackup environment information

Phase III Gather diagnostic lists

Phase IV Select the diagnostic commands or procedures to execute

Phase V Execute the selected diagnostic commands or procedures

Phase VI nbsu final processing

By default, nbsu writes the information to a gzipped tar file located in an output directory located directly
below the directory in which you run the command.

Which nbsu command line option can you use to see a list of diagnostic commands that nbsu will run?

The –l command line option (lowercase L) can be used to see a list of diagnostic commands that nbsu will
run.

Which nbsu command option can be used to choose the role of the system on which the diagnostic
commands or procedures are to run?

The –r command line option, followed by the NetBackup role can be used to choose the role of the system
on which the diagnostic commands or procedures are to run.

Further information about nbsu is provided in the NetBackup Commands Reference Guide.

5. Change the current folder or directory in the Terminal window, as shown:

Command: cd /home/nbsvc/

6. Run the nbsu utility with no command options or arguments, as shown below.

Command: nbsu

7. Monitor the nbsu command output that is displayed in the Terminal window.
 It may take several minutes (5-10 minutes) for the command to complete, and for the command prompt to
be returned.

8. Allow the command to run to completion before proceeding.

9. List the contents of the current directory in Terminal window.

Command: ls -al

10. Verify that it contains the output file that was created by nbsu and it's format will be
NBSU_hostname_role_mmddyyyy_timestamp.tgz.

In a troubleshooting situation, you would provide the output file (.tgz file) to Veritas technical support for
analysis.

11. Minimize the Terminal window, you will return to it in the next exercise.

Using the NetBackup Copy Logs (nbcplogs) command

In the steps that follow, you use the nbcplogs (NetBackup log gatherer) to gather logs files and troubleshooting
information in preparation for transfer to Veritas technical support for analysis.

nbcplogs gathers log files generated by NetBackup and its components on the system on which the command is
initiated, and creates a package that can be transferred to Veritas technical support for analysis.

14. Access the Terminal window that is connected to the lnxmaster.vrtsedu.lab system.

By default, nbcplogs runs the nbsu utility to gather troubleshooting information, and includes
the nbsu output in the package that is created for transfer to Veritas.
Because nbcplogs includes nbsu data collection, there is no need to use both commands. Run nbcplogs to
gather the troubleshooting information and log files.

15. In the Terminal window, type the command shown below, and press Enter.

Command: nbcplogs --help-long | more

The command output explains the usage of the nbcplogs command. Additional information and examples
about the command can be found in the NetBackup Commands Reference Guide.

16. Type the following command and press Enter to gather troubleshooting information (using nbsu), and to
gather log files for the last 15 minutes of the current day.

Command: nbcplogs -d 15min /support/nbcplogs-out

17. Monitor the progress of the nbcplogs command execution in the Terminal window.
 When the command is ready to write its output file, it prompts: is there at least XX.X M (MB disk space
available on /support)? (Y/N)

Type Y, and press Enter.

nbcplogs proceeds to gather and write its output file, including the output of the nbsu command. This may
take several minutes, depending upon the size of the log files that are gathered. When the creation of the
command output is completed, you are returned to the command prompt.

18. When the command completes, navigate to /support/nbcplogs-out using:

Command: cd /support/nbcplogs-out

19. Examine the names of the log directories that have been collected by nbcplogs, and the name of the
large tar file that is present in the folder.

Command: ls -al

The output of the nbcplogs file is ready to send to Veritas.

The nbcplogs utility gathers troubleshooting and log information only from the system on which it was
executed. In a NetBackup production environment, it is often necessary to collect troubleshooting and log
information from other NetBackup systems, from media servers and clients, in addition to collecting the
information from the Primary/Master server.

Feel free to experiment further with the use of the nbsu and nbcplogs commands to gather troubleshooting
information.

20. Minimize the Terminal window. You will return to it later in this lab.
Exercise C: Viewing and Setting Debug Logging Properties

Collection of debug logs and other associated NetBackup troubleshooting information is an activity that should
always be undertaken with the guidance from a Veritas NetBackup Technical Support Engineer, or the technical
support personnel of a Veritas Support Partner. This includes setting logging levels and properties for NetBackup
services, daemons, and processes.

In this exercise, you view the NetBackup configuration parameters that are used to configure NetBackup log files.

Setting debug log properties

NetBackup debug logs provide important information to enable technical support personnel to troubleshoot the
more complex NetBackup and NetBackup-related problems. The level of detail provided in the NetBackup logs
can be adjusted by setting the log verbosity.

For many problems, the default log verbosity may be sufficient to gather the log entries needed to identify a
problem. In some cases, NetBackup support personnel may request that you increase the logging levels of all logs,
or for the logs of a specific service, daemon, or process.
If in doubt, contact a technical support representative to inquire whether debug log verbosities should be
increased.

1. Access the desktop of the console.vrtsedu.lab system.

2. Double click the NetBackup 10.0 Administration Console shortcut located on desktop.
3. In the NetBackup Administration Console window that is displayed, log in using the following credentials:

Hostname: winmaster.vrtsedu.lab

User name: root

Password: P@ssw0rd

4. In the NetBackup Administration Console, navigate to NetBackup Management > Host Properties >
Master Servers.

The master server, lnxmaster.vrtsedu.lab is displayed in the list of master servers in the right pane of the
Administration Console.

5. Double-click lnxmaster.vrtsedu.lab displayed in the right pane of NetBackup Administrator Console.

The Master Server Host Properties window is displayed.

6. In the left pane of the Master Server Properties window, click Logging.

The right pane of the Master Server Host Properties window displays the Logging parameters that can be
set for the selected master server.
 7. The default logging level settings are currently displayed in the Logging pane of the Master Server Host
Properties window.
o The Global logging level setting, located near the top of the Logging window affects the debug
logging levels for both legacy-style and unified-style logs.
o The Process specific overrides section of the Logging pane contains logging level settings for some
of the most important master server services and daemons that use legacy-style debug logging*. If
altered, these settings override* the Global logging level for the specified service or daemon.
o The Debug logging levels for NetBackup services section of the Logging pane contains debug
logging level settings for some of the most important master server services and daemons that use
unified logging. If altered, these settings override the Global logging level for the specified service.
8. For now, allow all the settings in the Logging pane to remain at the default settings.
9. Leave the Master Server Host Properties window open for use in the next exercise.

When gathering information and log files to send to technical support, the NetBackup technical support
representative may direct you to change the logging levels. Due to the amount of log information that may
be captured, the size of the log files can grow very quickly. You are advised not to increase the logging
levels unless directed to do so by a NetBackup technical support representative.
Logging levels for legacy-style logs are stored in the /usr/openv/netbackup/bp.conf file on UNIX or Linux-
based NetBackup systems.
Logging levels for Unified-style logs are stored in the /usr/openv/netbackup/nblog.conf file on UNIX or
Linux-based NetBackup Primary/Master server systems.
Refer to the Veritas NetBackup Logging Reference Guide for complete details on setting logging verbosity.

Logging for critical processes

In this steps that follow you use the Administration Console to enable the most critical logs and to manage the
amount of disk space they consume. Unlike the logging assistant, which is usually used as part of troubleshooting
a specific problem, these settings can be used to enable the most critical logs to be enabled at all times, reducing
the amount of time it takes to get logs to Veritas support.

10. From the Master Server Host Properties window, locate the Logging for critical processes: label and
click the Enable button.

The Alert: Logging for critical processes window opens. Review the information in this window before
proceeding.

11. Click Yes to enable logging and to close the Alert: Logging for critical processes window.

The Alert: Logging for critical processes window is closed.

From the Master Server Host Properties window, note that the Enable button is no longer present and the
label has changed to Logging for critical processes: Enabled.

12. From the Master Server Host Properties window, review the settings for Keep Logs for: and Keep logs
up to: in the Retention area.
 The Keep logs up to: setting was automatically enabled when we activated logging for critical processes. This
setting does not require critical logging to be enabled, but it is especially useful with critical logging enabled.
Proper use of these settings, along with verbosity, allows critical legacy logs to be on at all times without
consuming excessive disk space.

13. Click OK to close the Master Server Host Properties window.

The Restart Daemons window is displayed.

14. Click OK to close the Restart Daemons window.

It is not necessary to restart the NetBackup Daemons/Services for this setting to take effect.

15. Access the Terminal window that is connected to the lnxmaster.vrtsedu.lab system.
16. Navigate to the NetBackup logging directory using the following command:

Command: cd /usr/openv/netbackup/logs

17. Check to see if the critical log bpbrm currently exists using the appropriate command:

Command: ls -al bp*

The bpbrm directory may not exist. Because bpbrm is not a service, it does not run all the time; it runs only
when a Media or Master/Media server is actively running jobs. We will explore this log in more detail in the
next exercise.
The bpbrm directory will be created the next time a job runs that uses the Primary/Master server as a media
server (e.g., a backup or restore job). It is expected that no backup or restore jobs have run in the time since
critical logging was enabled. If the directory does exist there is no cause for concern; it will not interfere with
the rest of the lab.

18. Leave the Terminal window open. You access this window again in the next exercise.

Exercise D: Enabling NetBackup Legacy Debug Logging

Collection of debug logs and other associated NetBackup troubleshooting information is an activity that should
always be undertaken with the guidance from a Veritas NetBackup Technical Support Engineer, or the technical
support personnel of a Veritas Support Partner. This includes setting logging levels and properties for NetBackup
services, daemons, and processes.

In this exercise, you enable legacy logging for a legacy service and a legacy process on the Primary/master server
system. This exercise illustrates the principals of legacy logging.
Enabling NetBackup legacy logging

1. Access or the open Terminal window that is connected (via PuTTY) from the console.vrtsedu.lab to the
master server, lnxmaster.vrtsedu.lab.
2. If you are not already in the NetBackup logs folder, then change to that directory and list the contents
using the following commands:

Command: cd /usr/openv/netbackup/logs

Command: ls -al

The logs folder may contain several sub-folders,

including: ALTPATH, bmrd, bmrsetup, nbars, nbaudit, nbemm, and many others – depending on the
Operating System of the NetBackup server. UNIX/Linux-based NetBackup servers store unified log files in a
different directory location than Windows-based servers.

These folders house the unified log files on the Windows-based master server and other configuration
information. UNIX/Linux-based master servers house the unified logs in /usr/openv/logs.

Viewing the mklogdir script

The mklogdir is a script that can be used to create log folders for all NetBackup processes that use legacy-style
logs. In the steps that follow, you briefly view the contents of the mklogdir script.

3. In the Terminal window, view the contents of the mklogdir file using the appropriate command as
shown:

Command: more mklogdir

The contents of the mklogdir (or mklogdir.bat) file are displayed.

4. Use the space bar to advance the display of the file contents one screen-at-a-time and briefly examine the
file contents.

Enabling logging for the large number of processes that use legacy logging indiscriminately will consume disk
space and impact performance unnecessarily. Troubleshooting should generally use and enable logging in a
more targeted manner, as directed by Veritas NetBackup Technical Support.
The mklogdir script file can be used to create a large number of log directories for the legacy processes. If
that is your intent, you can run the batch file with no additional arguments to create all possible logging
directories. Or, if you only wish to create directories for specific logs, you can add the names of the logs you
wish to create as arguments when you enter the mklogdir command. In either case, the next time the service
or process for which a log directory is created is active, it will start logging to a log file in its log directory.
In general, enable only the logs requested by your NetBackup Technical Support representative.

5. Type Ctrl +C on your keyboard to close the mklogdir file, and return to the prompt.
 Command: CTRL + C

6. Allow the Terminal window to remain open. You access this window in the next exercise.

Creating log folders for legacy-style logging

In the steps that follow, you use mklogdir to selectively create a log folder for a NetBackup service that uses
legacy-style debug logging.

NetBackup uses the logs directory tree not only for the recording of troubleshooting information, but for progress
and communication updates to users and other NetBackup applications. Restrictive permissions on these
directories can not only disable the collection of troubleshooting data, but also prevent the application itself from
functioning correctly. Backup and restore operations fail when permissions are too restrictive. In a production
environment, Veritas recommends the use of the mklogdir script to ensure permissions are set correctly. If you do
create directories manually instead of using the script make sure that any directories you create in the logs
directory are readable and writeable by all users (777 permissions). If security requirements prohibit global read-
write access, you can run the mklogdir script and specify directories that already exist and the script will set
permissions on the directory to the minimum necessary settings.

7. In the Terminal window, use mklogdir to create the bprd directory in the logs directory on the master
server:

Command: ./mklogdir bprd

The bprd directory will be created with the proper permissions.

o bprd (NetBackup Request Daemon) is a NetBackup service that runs only on the master
server. bprd runs continually on the master server system whenever NetBackup is running.

8. Verify that you have successfully created the bprd directory using the appropriate command:

Command: ls -al bprd

The new bprd directory is currently empty. When logging commences for the bprd service, a file is created
each day that has the file name format, user_name.mmddyy.log (i.e., All_Admins.101216.log). All legacy log
files are ASCII text files.

9. Leave the Terminal window open. You will return to it in later in this lab.

Running a backup job

In the steps that follow, you perform a manual backup that writes to a disk storage on the master server system.

10. Access the NetBackup web user interface that is open on the console system.
11. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
12. On the Policies page, select the checkbox next to the PRE-clients-to-master-advdisk policy.
 13. Click Manual backup in on the actions menu.

The Manual backup window is displayed.

14. In the Manual backup window, click to select lnxmaster.vrtsedu.lab and click OK.
15. After initiating the backup, navigate to the Activity monitor page and monitor the progress of the most
recent backup job.
16. Verify that the job runs to successful completion.

It might take a couple of minutes for the backup job to complete.

Verifying the creation of the log files

In previous steps of this exercise, you created the log folder for the bprd service on your Primary/Master server. In
the steps that follow, you view the log files in the bprd folder.

17. Access or the open Terminal window that is connected (via PuTTY) from the console.vrtsedu.lab to the
master server, lnxmaster.vrtsedu.lab.
18. In the Terminal window, navigate to the directory indicated, if not already there:

Command: cd /usr/openv/netbackup/logs

19. List the contents of the bprd directory using the appropriate command:

Command: ls -al bprd

You should observe the following:

A log file is present in the folder. The filename of the file is user_name.mddyy.log (e.g., root.021217.log).
The user name will be root.

20. List the contents of the bpbrm directory using the following command:

Command: ls -al bpbrm

The bpbrm directory pre-existed in this lab environment.

You should observe the following:

A log file is present in the folder – unless a problem occurred on the Primary/Master server that prevented
the bpbrm process from being initiated.

The filename of the file is user_name.mddyy.log (e.g., root.021217.log).

The date of the file corresponds to today’s date (assuming you complete all parts of this lab on the same day).
 Because a backup, restore, or other operation that requires the bpbrm process has been directed to this
media server, the bpbrm log file should have been created on the system – even in most situations where the
job failed.

When a backup job is performed on the Primary/Master server, the backup job requires the use of
the bpbrm process on that system. In the steps that follow, you verify that the bpbrm log file has been
created on the Primary/Master server system.
The bpbrm log was enabled in the previous exercise: Logging for critical processes. If you skipped that
exercise, the log will not be present and you should proceed to Exercise F: (Optional) Viewing debug logging
levels for unified logs.
bpbrm (Backup and Restore Manager) is a media server process that only runs during backup and restore
jobs. Your Primary/Master server is configured as a media server so this process will also run on the
Primary/Master server when a backup or restore operation directs backup activity to backup storage on that
system.

21. Use the more command in the Terminal window to view the contents of the bpbrm log file.

Command: more /usr/openv/netbackup/logs/bpbrm/[file_name]

Example:
more /usr/openv/netbackup/logs/bpbrm/root.052418_00001.log

22. Examine the bpbrm log file contents briefly.

In a real-world environment, use of a more robust text editor will enhance the reading of log files.

23. Close the bpbrm log file using CRTL+C.

24. Leave the Terminal window open, you will return to it later in this lab.

Exercise E: Viewing Debug Logging Levels for Unified Logs

Collection of debug logs and other associated NetBackup troubleshooting information is an activity that should
always be undertaken with guidance from a Veritas NetBackup Technical Support Engineer, or technical support
personnel of a Veritas Support Partner. This includes setting logging levels and properties for NetBackup services,
daemons, and processes.

Unified logging is enabled by default for all NetBackup services and daemons that use unified logging. There is no
need to manually enable or initiate unified logging.

In this exercise, you view the configuration file for unified logs, set the unified logging levels for unified log debug
and diagnostic messages, and observe the results.
Unified logging

In this exercise, you perform the following tasks on the master server, lnxmaster.vrtsedu.lab:

 View the configuration file for unified logs

 Set the unified logging levels for unified log debug and diagnostic messages
 Observe the results of these operations.

1. Access the Terminal window (opened using PuTTY) from the console.vrtsedu.lab system to your Linux-
based master server, lnxmaster.vrtsedu.lab.
2. In the Terminal window, change directory to the /usr/openv/logs directory.

Command: cd /usr/openv/logs

The logs directory contains the unified logs that most directly affect NetBackup.

3. Type the following command, and press Enter, to view the contents of the log directory.

Command: ls -al

4. Locate the nbpem, nbjm and nbrb directories. These are the logging directories for the NetBackup
services; Policy Execution Manager (nbpem), the Job Manager (nbjm), and the Resource Broker (nbrb),
respectively.
5. Type the following command, and press Enter, to change to the nbpem directory.

Command: cd nbpem

6. Examine the contents of the directory.

Command: ls -al

The log files in the nbpem folder are the nbpem (OID=116) log files. The log naming convention for unified
logs is:
[Product ID]-[Originator ID]-[Host ID]-[Date]-[Rollover Number]
In the commands that require the entry of the NetBackup Product ID, the Product ID can be entered
as 51216 or nb.

Viewing default logging settings for unified logs

In the steps that follow, you view and modify the default logging settings for NetBackup unified debug logs.

7. Change directory to the /usr/openv/netbackup directory, and list the contents of the directory.

Command: cd /usr/openv/netbackup
 Locate the nblog.conf file. This is the configuration file for unified logging.

8. Type the more command to read the contents of nblog.conf.

Command: more nblog.conf

Take note of the message located at the top of the nblog.conf file.

Do not edit the nblog.conf file to change its contents. Unified logging configuration changes are made using
the vxlogcfg command.

9. Press the Enter key to move downward through the nblog.conf file one page at-a-time until you locate
the DiagnosticLevel and DebugLevel entries.
 This section defines the default settings for the unified logs. The key
words DiagnosticLevel and DebugLevel (case is significant) define the logging levels for diagnostic and
debug messages. By default, the DiagnosticLevel is set to 6 (maximum) and the DebugLevel is set to 1
(minimum).

10. Type q to exit the more command.

11. To change the Debug logging level for Unified logs type the following command and press Enter.

Command: vxlogcfg -p nb -a -o Default -s DebugLevel=6

The command above sets the default DebugLevel for NetBackup unified logging to 6.
The vxlogcfg command parameters are case-sensitive.

If you do not receive the response message: “The configuration settings were added successfully”, check
your typing and try the command again.

12. After entering the first vxlogcfg command successfully, type the following command to view the Unified
logging levels.

Command: vxlogcfg -p nb -l -o Default (-L is lowercase)

The command output displays the default DebugLevel and DiagnosticLevel settings for unified logging on
the master server.

The DebugLevel and the DiagnosticLevel are now set to 6.

Setting unified logging levels using the Administration Console

In the steps that follow, you use the NetBackup Administration Console to set the debug logging levels for
specific NetBackup master server services that use unified logging.

13. Access the open NetBackup Administration Console that is connected to the master
server, lnxmaster.vrtsedu.lab.
14. Select NetBackup Management and then select Host Properties, Master Servers in the left pane of the
Administration Console.
15. Double-click the entry for lnxmaster.vrtsedu.lab, to open the Master Server Host Properties window.
16. Click the Logging entry, if necessary, located in the left pane of the Master Server Host
Properties window.
17. Set the logging levels for the Policy Execution Manager (nbpem), the Job Manager (nbjm),
and Resource Broker (nbrb) services to Debug logging level = 2.
18. Click the OK button in the Logging pane of the Master Server Host Properties window, to save the
settings.
19. When the Restart Daemons dialog box is displayed, click the OK button to acknowledge the message
and to close the dialog box.
Verifying the unified logging settings

After changing the debug logging levels for nbpem, nbjm, and nbrb using the NetBackup Administration
Console, in the steps that follow you verify the settings for those services in the nblog.conf file.

20. Return to the Terminal window.

21. In the Terminal window, change to the /usr/openv/netbackup directory if not already in that directory.

Command: cd /usr/openv/netbackup

22. Use the more command to view the contents of the nblog.conf file.

Command: more nblog.conf

23. Use the Enter to scroll down through the nblog.conf file until you find the entries for the Policy
Execution Manager, Job Manager, and Resource Broker services.
 The portion of the nblog.conf file illustrated above identifies the logging level settings for the individual
NetBackup services (OIDs) that use unified logging.

24. Observe that the DebugLevel for each of the three processes (nbpem, nbjm and nbrb) has been set to 3.

You set the logging levels to 2. However, legacy logs use a 0-5 scale and unified logs use a 1-6 scale.
Therefore, a logging level setting of 2 for a legacy log equates to a logging level setting of 3 for a
unified log.
The individual logging level setting for a service overrides the default logging level setting. As logging is
currently configured, nbpem, nbjm, and nbrb will log debug messages at level 3. All other processes will log
debug messages at the default setting of level 6.

25. Type q to exit the more command.

Changing the diagnostic logging level settings

The next steps describe the method for changing the diagnostic logging levels for services that use unified
logging.

26. Type the following command to change the DiagnosticLevel setting for the nbpem service to 3.

Command: vxlogcfg -p nb -a -o nbpem -s DiagnosticLevel=3

Wait for the command prompt to be returned. If you do not see the message: “The configuration settings
were added successfully”, check your typing and try the command again.

27. Type the following command to display the changes.

Command: vxlogcfg -p nb -l -o nbpem (lowercase L)

This command displays the settings for the Policy Execution Manager (nbpem).

Take note of the settings for DebugLevel and DiagnosticLevel parameters for nbpem. Both settings should
be set to level 3.

28. Type the following command to reset the default DebugLevel and DiagnosticLevel logging levels to
their original values.

Command: vxlogcfg -p nb -a -o Default -s DiagnosticLevel=6 –s DebugLevel=1

29. Verify that the message, “The configuration settings were added successfully” is returned in response
to the command before continuing. If necessary, check the command syntax and try the command again.
30. Reset the DiagnosticLevel setting for the nbpem service back to 6, by executing the following command.

Command: vxlogcfg -p nb -o nbpem -r -s DiagnosticLevel

 31. Verify that the message, “The configuration settings were removed successfully” is returned in
response to the command before continuing. If necessary, check the command syntax and try the command
again.

Resetting unified logging levels for nbpem, nbjm, nbrb

31. Access the open NetBackup Administration Console.

32. Select NetBackup Management and then select Host Properties, Master Servers in the left pane of the
Administration Console.
33. Double-click the entry for lnxmaster.vrtsedu.lab, to open the Master Server Host Properties window.
34. Click the Logging entry, if necessary, located in the left pane of the Master Server Host
Properties window.
35. Set the Debug logging levels for the Policy Execution Manager, the Job Manager, and Resource
Broker services to “Same as global”.
36. Click the OK button in the Logging pane of the Master Server Host Properties window, to save the
settings.
37. When the Restart Daemons dialog box is displayed, click the OK button to acknowledge the message
and to close the dialog box.

Exercise F: Using the Logging Assistant

The Logging Assistant is helpful to shorten the time required to setup and collect debug logs and other
information. It is recommended to use the logging assistant under the guidance of Veritas support.

In this exercise, first you use the logging assistant to create the nbsu logs.

1. Access the desktop of console server.

2. In NetBackup Administration Console, select Logging Assistant in the left pane.
3. Right click in the right pane and select New Logging Assistant Record.
4. In the Logging Assistant record ID type nbsu-logs.

It is recommended to use a support case ID as the Logging assistant record id to more easily track the record
during troubleshooting process.

5. In Actions, select Collect nbsu diagnostic information and click OK.

6. Select the Collect nbsu output from Master Server checkbox and click Next.
7. Verify the output location and click Next
8. Read the information displayed in the Operation Details section, and then click Finish.
9. Monitor the progress of the log collection task. The task progress is displayed in the Progress column.

This task may take 5-7 minutes to complete. Wait for this task to complete before proceeding.

10. After the task completes, verify that the log files are generated in the output location specified while
creating the log record.

By default log records are generated in /usr/openv/netbackup/logs/nblastaging/

Use of Logging Assistant to collect the debug log for failed job.

11. In NetBackup Administration Console, select Logging Assistant in the left pane.
12. Right click in the right pane and select New Logging Assistant Record.
13. In the Logging Assistant record ID type Logs-for-job-failure.
14. In Actions, select Setup debug logging and click OK.
15. Click Next twice.
16. Select checkbox for Setup debugging logging on Master Server and Clieck Next.
17. On the Master Server Debug Logging Selection screen, select the Backup problem category and
click Next.
18. On the Summary screen, verify that the debug logging selections are correct and click Next.
19. On the Results screen, ensure that the debug logging was setup successfully and click Finish
20. In the right pane of the NetBackup Administration Console, right-click the Logs-for-job-failure logging
assistance record, and then click Setup Debug Logging.
21. Click Next twice.
22. On the Host Selection screen, ensure that the Setup debug logging on Master Server checkbox is selected,
and click Next.
23. In Confirm (or select) required debug logging select checkbox for Backup and click Next.
24. Review the Summary and click Next.
25. Review the Results and click Finish.
26. To initiate the backup click Policies and right click policy PRE-clients-to-master-tape.
27. Click Manual Backup.
28. Check the backup status in Activity Monitor. The job will Fail.
29. To collect the debug logs, click Logging Assistant.
30. Right click logs-for-job-failure and click collect debug logs.
31. Click Next twice.
32. Verify Collect available logs is selected.
33. Check the location where the logs will be saved.
34. Check the Operation Details in Result page and click Finish.
35. Debug log collected at given location and folder name format will be Logging Assistant record
id-date-time
 Use these logs for troubleshooting or share it with Veritas support.

Exercise G: Using the NetBackup Smart Diagnostics Utility

In this exercise, you configure the Smart Diagnosis utility to get the performance issues if any, like CPU utilization,
high memory usage and deadlocks for registered Netbackup processes.

1. On the console system, double click the PuTTY icon located on the Desktop.
2. Double click on lnxmaster.vrtsedu.lab and login with following credentials.

💻 lnxmaster.vrtsedu.lab User ID: root Password: P@ssw0rd

3. To install the diagnosis utility on Primary/Master server type the following command and press Enter.

nbsmartdiag -install

4. Verify that the message, “Performed the install operation successfully” is returned in response to the
command.

Defined the NBSD_EVIDENCE_PATH before starting the netbackup smart diagnosis process.

5. Type the command bpsetconfig and press Enter.

bpsetconfig prompt will appear.

6. Type command NBSD_EVIDENCE_PATH = /usr/openv/netbackup/ and press Enter.

7. Press Ctrl+D to exit from the bpsetconfig.
8. To check the entry in bp.conf, type the command cat /usr/openv/netbackup/bp.conf
9. To start the NetBackup Smart Diagnosis Service, Type the following command and press Enter

nbsmartdiag -start

10. Verify that the message “Performed the start operation successfully” is returned in response to the
command.
11. Check and observe the log file located at /usr/openv/netbackup/logs

By default processes will be monitored after every 600 seconds. You can change the time interval by
changing NBSD_POLL_INTERVAL parameter. Also whenever nbsmartdiag detects the issue it will collect the
evidence at defined path. Refer the NetBackup Command Reference Guide for more details.

12. To stop the diagnosis process type the following command and press Enter.

nbsmartdiag -terminate

13. Verify that the message, “Performed the stop operation successfully.” is returned in response to the
command.
Lab - Appendix A: Protecting NAS Data

Configuration notes

This lab is performed using the following virtual machines:

 console.vrtsedu.lab - Active Directory/Domain Controller, DNS, and NTP server.

 lnxmaster.vrtsedu.lab - NetBackup 10.0 Master/Primary server.
 lnxmedia.vrtsedu.lab - NetBackup 10.0 Media server (Linux).
 winmedia.vrtsedu.lab - NetBackup 10.0 Media server (Windows).
 esx1.vrtsedu.lab - VMware ESXi server.

The following virtual machines used in this lab are running on the ESXi server, esx1.vrtsedu.lab:

 netapp1.vrtsedu.lab - First node in the Data ONTAP cluster (netapp-cluster) running ONTAP Software
Version 9.3P15.
 netapp2.vrtsedu.lab - Second node in the Data ONTAP cluster (netapp-cluster) running ONTAP Software
Version 9.3P15.

There are two storage virtual machines in the ONTAP cluster. Storage virtual machine vsrv1 is running on
the netapp1 host and storage virtual machine vsrv2 is running on the netapp2 host. CIFS shares
(share1 and share2) are created on storage virtual machine, vsrv1 and NFS shares (share3 and share4) are
created on storage virtual machine, vsrv2.

Exercise A: Authorizing NetBackup Access to NDMP hosts

In this exercise, you generate and add NDMP credentials in NetBackup.

Adding credentials for the vserver, vsrv1.vrtsedu.lab

1. Log in to the console system using the following credentials.

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the NetBackup Web UI login shortcut located on the desktop of the console system to
launch the NetBackup web user interface.

The Netbackup web user interface can be accessed by navigating to the following URL:
https://Primary server hostname or IP/webui/login.
For the purpose of this lab, a web shortcut is preconfigured for accessing the NetBackup web user interface.
3. If a security warning is displayed, click Advanced > Accept the Risk and Continue.
4. Sign in to the NetBackup web user interface using the following credentials.
o Username: root
o Password: P@ssw0rd

5. In the NetBackup web user interface, in the navigation pane, click Credentail Management.
6. On the Credential Management page, click the Client credentials tab.
7. In the Client credentials tab, click Add.
8. In the Add NDMP host window, enter vsrv1.vrtsedu.lab in the NDMP host name field.
9. Select the Use the following credentials for this NDMP host on all media servers option.
10. Enter vsadmin in the Username field.

Do not close the Add NDMP host window, you will return to it after generating the password for
the vsrv1.vrtsedu.lab system.

11. Minimize (do not close) the NetBackup web user interface.
12. Double-click the Command Prompt shortcut located on the desktop of the console system.
13. In the Administrator: Command Prompt window, execute the following command to generate and copy
the password for the vsrv1.vrtsedu.lab system to your clipboard.

Command: powershell -F C:\Automation\Scripts\vsrv1.ps1 | clip

14. After executing the above command, minimize the Administrator: Command Prompt window.
15. Access the NetBackup web user interface open on the console system.
16. In the NetBackup web user interface, in the Add NDMP host window, right-click the Password field and
then click Paste to paste the password for the vsrv1.vrtsedu.lab system.
17. Click Add in the Add NDMP host window to validate and add the credentials.

After the credentials are validated they are added to NetBackup and a success message is displayed in the
NetBackup web user interface.

Adding credentials for the vserver, vsrv2.vrtsedu.lab

18. On the Credential management page, in the Client credentials tab, click Add.
19. In the Add NDMP host window, enter vsrv2.vrtsedu.lab in the NDMP host name field.
20. Select the Use the following credentials for this NDMP host on all media servers option.
21. Enter vsadmin in the Username field.

Do not close the Add NDMP host window, you will return to it after generating the password for
the vsrv2.vrtsedu.lab system.

22. Minimize (do not close) the NetBackup web user interface.
23. Access the Administrator: Command Prompt window open on the console system.
24. In the Administrator: Command Prompt window, execute the following command to generate and copy
the password for the vsrv2.vrtsedu.lab system to your clipboard.

Command: powershell -F C:\Automation\Scripts\vsrv2.ps1 | clip

25. After executing the above command, minimize the Administrator: Command Prompt window.
26. Access the NetBackup web user interface open on the console system.
27. In the NetBackup web user interface, in the Add NDMP host window, right-click the Password field and
then click Paste to paste the password for the vsrv2.vrtsedu.lab system.
28. Click Add in the Add NDMP host window to validate and add the credentials.

After the credentials are validated they are added to NetBackup and a success message is displayed in the
NetBackup web user interface.

29. On the Credential management page, in the Client credentials tab, verify that both the vserver's
(vsrv1.vrtsedu.lab and vsrv2.vrtsedu.lab) are listed.
30. Remain logged in to the NetBackup web user interface.

You will return to it later in this lab.

Exercise B: Configuring and Performing NDMP Backups

In this exercise, you will use the NetBackup web user interface to configure, perform, and monitor NDMP backups.

Creating a backup policy

1. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
2. On the Policies page, click Add to start creating a new backup policy.

The Create policy page is displayed and the Attributes tab selected by default.

3. On the Create policy page, under the Attributes tab, perform the following:

a. Enter LAB-nas-backup in the Policy name field.

b. Select NDMP in the Policy type drop-down list.

c. Select lnxmedia_msdp_stu in the Policy storage drop-down list.

d. Retain the default settings for all other attributes and click the Schedules tab.

4. In the Schedules tab, click Add in the Backup schedules section to add a full backup schedule.
5. In the Add schedule window, perform the following:

a. Enter full_frequency in the Name field.

b. Ensure that Full Backup is selected in the Type of backup drop-down list.

c. Ensure that the Frequency radio button is selected in the Schedule type section.

d. Ensure that the frequency is set to 1 week.

e. Select 1 week (Retention Level 0) in the Retention drop-down list.

f. Retain the default settings for all other schedule attributes and click Add in the Add
schedule window to save the schedule.

6. In the Schedules tab, verify that an entry for the full_frequency schedule is visible in the Backup
schedules section.
7. On the Create policy page, click the Clients tab and then click Add to add clients to the policy.
8. In the Add client window, select the radio button for the vsrv1.vrtsedu.lab host and then click Add.
9. On the Create policy page, click the Backup selections tab and then click Add to begin adding backup
selections to the policy.
10. In the Add backup selection window, perform the following:
a. Click browse (folder icon) located next to the Pathname or directive field.
b. Ensure that vsrv1.vrtsedu.lab is selected in the Browse and select volumes on the following
host drop-down list.
c. Select the checkbox for the vsrv1_cifs volume.

It might take a couple of seconds for the volumes to be discovered and displayed in the Add backup
selection window.

d. After selecting the vsrv1_cifs volume, click Add.

e. Verify that /vsrv1/vsrv1_cifs/ is listed in the List of pathnames and directives to add to the
selection list textbox and click Add to add the backup selection to the policy.
11. On the Create policy page, select each of the tabs -- Attributes, Schedules, Clients, and Backup
Selections -- and briefly verify the contents of each tab.
12. After verifying the contents of each tab, click Create to create the backup policy.

After the backup policy is created, a success message is displayed in the NetBackup web user interface and
you are returned to the Policies page.

13. On the Policies page, verify that the LAB-nas-backup policy is listed along with other configured backup
policies.
Performing and monitoring an NDMP backup

14. On the Policies page, select the checkbox next to the LAB-nas-backup policy and click Manual
backup on the actions menu.
15. Click OK in the Manual backup window to start the backup.

Because the LAB-nas-backup policy contains only one schedule and one client entry it is unnecessary to
make schedule or client selections in the Manual Backup window.

16. After initiating the backup job, select the Activity monitor entry in the left pane of the NetBackup web
user interface.
17. On the Activity monitor page, locate the most recent backup job that was performed using the LAB-nas-
backup policy.

The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 3-5 minutes for this backup to complete.

18. After the job completes, click the Backup job with the highest numbered Job ID.
19. On the actions menu, click View details to view the details for the selected job.
20. Briefly view the contents of the Overview and the Details tab.
21. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity monitor page.
22. Remain logged in to the NetBackup web user interface.

You will return to it later in this lab.

Exercise C: Using NetBackup Accelerator for NDMP

In this exercise, you enable the NetBackup Accelerator feature for NDMP backups, and perform NDMP backups
with and without the Accelerator feature to observer the impact of this feature on backup performance.

Creating a backup policy

1. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
2. On the Policies page, select the checkbox next to the LAB-nas-backup policy.
3. On the actions menu, click the Copy policy option.
4. In the Copy policy window, enter LAB-nas-accelerator in the New policy field and click Copy.

A new policy LAB-nas-accelerator is created and contains the same settings as the original policy.
5. On the Policies page, select the checkbox next to the LAB-nas-accelerator policy.

If the LAB-nas-backup policy is still selected, deselect it before selecting the LAB-nas-accelerator policy.

6. After selecting the policy, click Edit on the actions menu to open the policy for editing.
7. On the Edit policy page, in the Attributes tab, select the Use Accelerator checkbox.
8. Enter NDMP ACCELERATOR in the Keyword phrase (optional) field.
9. Click Save without making any other changes to update the policy and return to the Policies page.

Performing and monitoring Accelerator-enabled backups

10. On the Policies page, select the checkbox next to the LAB-nas-accelerator policy and click Manual
backup on the actions menu.
11. Click OK in the Manual backup window to start the backup.
12. After initiating the backup job, select the Activity monitor entry in the left pane of the NetBackup web
user interface.
13. On the Activity monitor page, locate the most recent backup job that was performed using the LAB-nas-
accelerator policy.

The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 3-5 minutes for this backup to complete.

14. After the job completes, click the Backup job with the highest numbered Job ID.
15. On the actions menu, click View details to view the details for the selected job.
16. Click the Details tab and locate the log messages that contain:

Info bpbrm (pid=xxxx) accelerator enabled

…
Info ndmpagent (pid=xxxx) accelerator optimization is off, unable to locate
accelerator tracklog

Because this is the first Accelerator-enabled NDMP backup, there is no track log which NetBackup can use to
discover changes in the files. The track log is created by NetBackup during this backup and will be used for
future backups.
The first Accelerator-enabled NDMP backup may take longer to run to completion than a non-Accelerator
backup. This is due to the processing overhead required to generate the track log for the client.

17. In the Details tab, locate the following log message:

Info ndmpagent (pid=xxxx) accelerator sent xxxxxxxxx bytes out of xxxxxxxxx

bytes to server, optimization 0.0 %

The first Accelerator-enabled NDMP backup using the policy will achieve an accelerator optimization of zero
percent. This is expected.
18. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity monitor page.

Performing a second Accelerator-enabled NDMP backup

19. In the NetBackup web user interface, in the navigation pane, click Protection > Policies.
20. On the Policies page, select the checkbox next to the LAB-nas-accelerator policy and click Manual
backup on the actions menu.
21. Click OK in the Manual backup window to start the backup.
22. After initiating the backup job, select the Activity monitor entry in the left pane of the NetBackup web
user interface.
23. On the Activity monitor page, locate the most recent backup job that was performed using the LAB-nas-
accelerator policy.

The Job state for the job may still be Active. Wait for the job to complete before proceeding.

It might take 3-5 minutes for this backup to complete.

24. After the job completes, click the Backup job with the highest numbered Job ID.
25. On the actions menu, click View details to view the details for the selected job.
26. Click the Details tab and locate the following log message:

Info ndmpagent (pid=xxxx) accelerator sent xxxxxxxxx bytes out of xxxxxxxxx

bytes to server, optimization 100.0 %

The second Accelerator-enabled NDMP backup using the policy will achieve an accelerator optimization of
100 percent. This is expected.

27. Take note of the number of bytes sent by the accelerator, as displayed in the above log message.
28. Compare the Bytes transferred and the number of bytes sent by the NDMP accelerator to the NetBackup
Media server.

The value of the Bytes transferred field far exceeds the number of bytes sent (as indicated in the log
message displayed in the Details tab) for the job. This indicates that the backup image that was written to the
storage unit was created using the contents of previous backup images of the NDMP host plus only the
changed files that were transferred by the NDMP accelerator to the Media server.

Because no changes were made to the files on the NDMP host between the two accelerator-enabled backup
jobs, very little data had to be sent to the storage unit on the Media server. This resulted in a faster backup.
However, the resulting full backup image recorded to the Media server storage unit still includes all the files
in the NDMP volume that was backed up. Had files been changed on the NDMP host, the amount of data
transferred would have been greater, but still less than would have been transferred during a full, non-
accelerator backup operation.
29. Click 'x' located in the right corner of the page that displays the details for the selected job, to close the
job details page and return to the Activity monitor page.
30. Sign out of the NetBackup web user interface and close the browser window.

Exercise D: Performing NDMP Restores

In this exercise, you delete files from the NDMP host and use the NetBackup Administration Console to restore
the deleted files using the backup image that were created earlier in this lab using the LAB-nas-
accelerator policy.

Preparing the NDMP host (vsrv1.vrtsedu.lab) for the restore

1. Double-click the vsrv1 CIFS-share1 shortcut located on the desktop of the console system.

The contents of the CIFS share, share1 are displayed in a new file explorer window.

If the share is not accessible, using command prompt run the following two commands one by one.
plink -ssh -l admin -pw P@ssw0rd -batch netapp-cluster.vrtsedu.lab "vserver stop -vserver vsrv1"
plink -ssh -l admin -pw P@ssw0rd -batch netapp-cluster.vrtsedu.lab "vserver start -vserver vsrv1"

The CIFS share, share1 resides in the vsrv1_cifs volume on vserver, vsrv1.vrtsedu.lab. This volume was
backed up earlier in this lab using the LAB-nas-backup and the LAB-nas-accelerator policies.

2. In the file explorer window, right-click the simple folder and the click Delete.
3. In the Delete Folder dialog box, click Yes to delete the simple folder from the share.
4. Close the file explorer window.

Restoring files

5. Double-click the NetBackup 10.0 Administration Console shortcut located on the desktop of
the console system.
6. In the NetBackup Administration Console window, perform the following:

a. Ensure that lnxmaster.vrtsedu.lab is displayed in the Host name field.

b. In the Login using section, ensure that the User name and password radio button is selected.

c. Enter root in the User name field and P@ssw0rd in the Password field.

d. Click Login.

7. In the NetBackup Administration Console, in the object tree, click Backup, Archive, and Restore.
 The Backup, Archive, and Restore interface is displayed in the right pane of the Administration Console and
provides three tabs: Backup Files, Restore Files, and Task Progress.

8. Ensure that the Restore Files tab is selected.

9. On the NetBackup Administration Console toolbar, click Actions > Specify NetBackup Machines and
Policy Type.
10. In the Specify NetBackup Machines and Policy Type window, perform the following:

a. Ensure that lnxmaster.vrtsedu.lab is selected in the Server to use for backups and restores drop-
down list.

b. Select vsrv1.vrtsedu.lab in the Source client for restores drop-down list.

c. Ensure that vsrv1.vrtsedu.lab is selected in the Destination client for restores drop-down list.

d. Select NDMP in the Policy type for restores drop-down list.

e. Click OK.

11. In the No Files Found dialog box, click OK.

12. On the NetBackup Administration Console toolbar, click Actions > Set Keyword.
13. In the Keyword Phrase dialog box, enter NDMP ACCELERATOR in the New keyword phrase field and
click OK.
14. In the No Files Found dialog box, click OK.
15. On the NetBackup Administration Console toolbar, click Actions > Set Date Range > Backup History.

The two backup images created earlier in this lab using the LAB-nas-accelerator policy are displayed in
the Backup History window.

16. Select only the latest backup image (listed as the first entry) and click OK.
17. In the No Files Found dialog box, click OK.
18. Enter / in the Browse directory field and press Enter.
19. In the Directory Structure pane, perform the following:

a. Expand the / node and then expand the vsrv1 node.

b. Expand the vsrv1_cifs node and then click (do not select) share1.

The contents of the CIFS share, share1 are displayed in the Contents of selected directory pane.

20. In the Contents of selected directory pane, select the checkbox next to the simple folder to select this
folder for restore.
21. After selecting the simple folder in the Contents of selected directory pane, click Restore.
22. In the Restore Marked Files window, take a note of the options that are available and click Start
Restore without making any changes to the restore options.
 23. In the View Progress dialog box, click Yes to view the progress of the restore.
24. In the Task Progress tab, monitor the restore task.

It might take 3-5 minutes for the restore to complete.

Wait for this restore to complete before proceeding.

25. After the restore completes, minimize (do not close) the NetBackup Administration Console.

Verifying the restored files

26. Double-click the vsrv1 CIFS-share1 shortcut located on the desktop of the console system.

The contents of the CIFS share, share1 are displayed in a new file explorer window.

If you are unable to access the CIFS share, launch a Command Prompt on the console system and execute
the following commands one after another to restart the vsrv1 storage virtual machine.

Command 1: plink -ssh -l admin -pw P@ssw0rd -batch netapp-cluster.vrtsedu.lab "vserver stop -vserver
vsrv1"

Command 2: plink -ssh -l admin -pw P@ssw0rd -batch netapp-cluster.vrtsedu.lab "vserver start -vserver
vsrv1"

27. In the file explorer window, verify that the smallfiles folder has been restored.
28. Close the file explorer window.

Exercise E: Performing Prerequisite Tasks for D-NAS Configuration

In this exercise, you perform the prerequisites tasks for D-NAS configuration. These tasks include:

 Configuring a Snapshot Management Server (CloudPoint Server) in NetBackup.

 Configuring the CloudPoint plugin.
 Change the service account for NetBackup services on a Windows Media server.
 Configuring Backup Host Pools.
 Configuring Storage Lifecycle Policies.

Configuring a Snapshot Management Server (CloudPoint Server) in NetBackup

1. Access the NetBackup Administration Console open on the console system.

2. In the NetBackup Administration Console, navigate to Media and Device Management > Credentials
> Snapshot Management Servers.
3. With the Snapshot Management Servers entry selected in the object tree, click Actions > New > New
Snapshot Server.
4. In the New Snapshot Management Server window, enter cp1.vrtsedu.lab in the CloudPoint Host
Name field and then click Validate Server.
5. In the Validate Certificate Authority: cp1.vrtsedu.lab dialog box, click Yes to verify the certificate
fingerprint.
6. In the New Snapshot Management Server window, enter admin in the User name field
and P@ssword in the Password field.
7. Click OK in the New Snapshot Management Server window to add the CloudPoint server in NetBackup.
8. After the CloudPoint server is added, click OK in the New Snapshot Management Server dialog box.
9. Verify that cp1.vrtsedu.lab is listed in the list of Snapshot Management Servers displayed in the right
pane of the NetBackup Administration Console.

Configuring the CloudPoint plugin

10. Click cp1.vrtsedu.lab listed in the right pane of the NetBackup Administration Console.

After you click the cp1.vrtsedu.lab entry in the right pane, a new pane listing configured CloudPoint
Plugins is displayed to the right of details pane.

Currently there are no CloudPoint Plugins configured.

11. Right-click the whitespace in the CloudPoint Plugins pane and then click New CloudPoint Plugin.
12. In the Add new Plugin window, select NetApp Storage Array in the Available Plugins drop-down list
and click Next.
13. In the Configure Plugin window, perform the following:

a. Enter netapp1 in the Enter Plugin ID field.

b. Enter netapp-cluster.vrtsedu.lab in the Array IP Address field.

c. Enter admin in the Username field.

d. Enter P@ssw0rd in the Password field.

e. Click OK.

It might take a minutes for the plugin to be added in NetBackup.

14. In the Configure Plugin dialog box, click OK.

The plugin, netapp1 is now listed in the CloudPoint Plugins pane. The Status of the plugin changes
from Configuring > Discovered.

Wait for the status to change to Discovered before proceeding.

 If the updated status is not displayed in the CloudPoint Plugins pane, use the refresh option available in
the NetBackup Administration Console to refresh the view.

15. Minimize (do not close) the NetBackup Administration Console.

You will return to it later in this lab.

Configuring NetBackup services on a Windows Media server

16. Access the winmedia system.

17. Log in to the winmedia system using the following credentials.
o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

18. Double-click the Command Prompt shortcut located on the desktop of the winmedia system.
19. In the Command Prompt window, execute the following command to launch the Services console.

Command: services.msc

20. In the Services console, locate and double-click the NetBackup Client Service to access its properties.
21. In the NetBackup Client Service Properties window, click the Log On tab.
22. In the Log On tab, select the This account radio button.
23. Enter VRTSEDU\Administrator in the This account text box.
24. Enter P@ssw0rd in the Password and the Confirm password fields.
25. Click Apply and then in the Services dialog box, click OK.
26. Click OK in the second Services dialog box displayed.
27. Click OK in the NetBackup Client Service Properties window.
28. Right-click the NetBackup Client Service and then click Restart.
29. In the Restart Other Services dialog box, click Yes.

Wait for the service to restart.

30. In the Services console, verify that the NetBackup Client Service is now running under the domain
administrator (VRTSEDU\Admininstrator) account. This information is displayed in the Log On As column.
31. Refer to steps 20-30 and change the service account for the NetBackup Legacy Network Service.
32. After changing the service account for the NetBackup Client Service and the NetBackup Legacy
Network Service, close the Services console.
33. Close the Administrator: Command Prompt window and log out of the winmedia system.

Configuring Backup Host Pools

34. Access the console system.

35. Access the NetBackup Administration Console open on the console system.
36. In the NetBackup Administration Console, navigate to NetBackup Management > Host Properties >
Master Servers.

The Master/Primary server host, lnxmaster.vrtsedu.lab is displayed in the right pane of the Administration
Console.

37. Double-click the entry for the Master/Primary server in the right pane of the Administration Console.

The Master Server Properties window is displayed.

38. Click the Backup Host Pools entry in the left pane of the Master Server Properties window.

The Backup Host Pools for the selected Master/Primary server are displayed in the right pane of the Master
Server Properties window.

Currently no Backup Host Pools exist on the Master/Primary server, lnxmaster.vrtsedu.lab.

39. Click Add in the right pane of the Master Server Properties window to add a new backup host pool.
40. In the Add Backup Host Pool window, perform the following:

a. Enter DNAS_Linux in the Backup Host Pool Name field.

b. Select Linux in the OS Type drop-down list.

c. In the Backup Hosts section, select the checkbox next to lnxmedia.vrtsedu.lab to include it in the
pool.

d. Click OK.

41. Click Add in the right pane of the Master Server Properties window to add a second backup host pool.
42. In the Add Backup Host Pool window, perform the following:

a. Enter DNAS_Windows in the Backup Host Pool Name field.

b. Select Windows in the OS Type drop-down list.

c. In the Backup Hosts section, select the checkbox next to winmedia.vrtsedu.lab to include it in the
pool.

d. Click OK.

43. Verify that DNAS_Linux and the DNAS_Windows backup host pools are listed in the right pane of
the Master Server Properties window.

NetBackup Master/Primary server running on Veritas Flex Appliance is not supported as a backup host for
the NAS-Data-Protection policy.
 All the hosts in the backup host pool, must be on the same OS version. So that, each host has the same
version of NFS or SMB for consistent backups.

44. Click Apply and then click OK to save the settings and close the Master Server Properties window.

Configuring Storage Lifecycle Policies

45. In the NetBackup Administration Console, navigate to NetBackup Management > Storage > Storage
Lifecycle Policies.
46. With the Storage Lifecycle Policies entry selected in the object tree, click Actions > New > Storage
Lifecycle Policy.
47. In the New Storage Lifecycle Policy window, perform the following:

a. Enter DNAS_NFS in the Name field and click Add to add a new operation.

b. In the New Operation window, perform the following:

i. Select Snapshot in the Operation drop-down list.

ii. Ensure that No Storage Unit is selected in the Destination storage drop-down list.

iii. Select Fixed in the Retention type drop-down list.

iv. Ensure 2 weeks (Retention Level 1) is selected in the Retention period drop-down list.

v. Click OK.

c. Click Add to add a second operation.

d. In the New Operation window, perform the following:

i. Select Backup From Snapshot in the Operation drop-down list.

ii. Ensure that lnxmedia_msdp_stu is selected in the Destination storage drop-down list.

iii. Ensure that Fixed is selected in the Retention type drop-down list.

iv. Ensure 2 weeks (Retention Level 1) is selected in the Retention period drop-down list.

v. Click OK.

e. Verify that two SLP operations (Snapshot and Backup From Snapshot) are listed in the New
Storage Lifecycle Policy window and click OK to save the lifecycle policy.

48. Verify that an entry for the DNAS_NFS storage lifecycle policy is displayed in the right-pane of
the NetBackup Administration Console.
49. Right-click the DNAS_NFS storage lifecycle policy displayed in the right-pane of the NetBackup
Administration Console and then click Copy.
50. In the Copy Storage Lifecycle Policy window, perform the following:
 a. Change the Storage lifecycle policy name to DNAS_SMB.

b. Double-click the Backup From Snapshot operation to edit this operation.

c. In the Change Storage Operation window, change the Destination

storage to winmedia_msdp_stu and click OK without making any other changes.

51. In the Change Storage Lifecycle Policy window, click OK to save the storage lifecycle policy.
52. Verify that an entry for the DNAS_SMB storage lifecycle policy is displayed in the right-pane of
the NetBackup Administration Console.
53. Remain logged in to the NetBackup Administration Console.

You will return to it later in this lab.

Exercise F: Configuring and Performing DNAS Backups

In this exercise, you configure two seperate backup policies to backup SMB and NFS share on a NetApp filer using
the NetBackup Dynamic NAS (D-NAS) feature.

Creating a policy to backup SMB shares using the D-NAS feature

1. Access the NetBackup Administration Console open on the console system.

2. In the NetBackup Administration Console, navigate to NetBackup Management > Policies.
3. With the Policies entry selected in the object tree, click Actions > New > Policy.
4. In the Add a New Policy window, enter LAB-dnas-smb-backup in the Policy name field and click OK.
5. In the Change Policy window, in the Attributes tab, perform the following:

a. Select NAS-Data-Protection in the Policy type drop-down list.

b. Select the DNAS_SMB storage lifecycle policy in the Policy storage drop-down list.

c. Leave all the other options at their default and click the Schedules tab.

6. In the Schedules tab, click New.

7. In the Add Schedule window, enter full in the Name field and click OK without making any other
changes.
8. Click the Clients tab.
9. In the Clients tab, perform the following:

a. Ensure that NetApp Storage Array is selected in the NAS supported vendor drop-down list.

b. Click New.

c. In the NAS Array and Array Head Selection window, perform the following:
 i. In the Browse for NAS filers section, click (do not select) netapp-cluster.vrtsedu.lab.

ii. In the NAS Assets Selection section, select the checkbox next to vsrv1 and click OK.

d. Verify that vsrv1 is listed in the Clients tab and click the Backup Selections tab.

10. In the Backup Selections tab, perform the following:

a. Select SMB in the Choose Protocol section.

b. Select DNAS_Windows in the Backup Host Pool section.

c. Click New.

d. In the Add Backup Selection window, perform the following:

i. Click Browse.

ii. Click (do not select) vsrv1 in the Browse for NAS volumes section.

iii. In the NAS Assets Selection section, select the checkbox next to the vsrv1_cifs volume and
click OK.

e. Verify that the vsrv1_cifs volume is listed in the Backup Selections tab and click the Exclude
Volumes tab.

11. In the Exclude Volumes tab, enter vsrv1_r* in the Volumes to exclude field and click Add.
12. Verify that vsrv1_r* is listed in the Volumes excluded from backup selections section.
13. In the Change Policy window, select each of the tabs -- Attributes, Schedules, Clients, Backup
Selections, and Exclude Volumes -- and briefly verify the contents of each tab.
14. After verifying the contents of each tab, click OK to save the backup policy.
15. Verify that a entry for the LAB-dnas-smb-backup policy is listed in the All Policies pane.

Creating a policy to backup NFS shares using the D-NAS feature

16. Right-click the LAB-dnas-smb-backup policy in the All Policies pane and then click Copy To New.
17. In the Copy a Policy window, enter LAB-dnas-nfs-backup in the New policy field and click OK.
18. In the Change Policy window, in the Attributes tab, select the DNAS_NFS storage lifecycle policy in
the Policy storage drop-down list and click the Clients tab.
19. In the Clients tab, perform the following:

a. Click the vsrv1 entry and then click Delete.

b. Click New.

c. In the NAS Array and Array Head Selection window, perform the following:

i. In the Browse for NAS filers section, click (do not select) netapp-cluster.vrtsedu.lab.
 ii. In the NAS Assets Selection section, select the checkbox next to vsrv2 and click OK.

d. Verify that vsrv2 is listed in the Clients tab and click the Backup Selections tab.

20. In the Backup Selections tab, perform the following:

a. Click the vsrv1_cifs volume and then click Delete.

b. In the Backup Policy Management window, click Yes.

c. Select NFS in the Choose Protocol section.

d. Select DNAS_Linux in the Backup Host Pool drop-down list.

e. Click New.

f. In the Add Backup Selection window, perform the following:

i. Click Browse.

ii. Click (do not select) vsrv2 in the Browse for NAS volumes section.

iii. In the NAS Assets Selection section, select the checkbox next to the vsrv2_nfs volume and
click OK.

g. Verify that the vsrv2_nfs volume is listed in the Backup Selections tab and click the Exclude
Volumes tab.

21. In the Exclude Volumes tab, select the vsrv1_r* entry listed in the Volumes excluded from backup
selections section and click Delete.
22. Enter vsrv2_r* in the Volumes to exclude field and click Add.
23. Verify that vsrv2_r* is listed in the Volumes excluded from backup selections section.
24. In the Change Policy window, select each of the tabs -- Attributes, Schedules, Clients, Backup
Selections, and Exclude Volumes -- and briefly verify the contents of each tab.
25. After verifying the contents of each tab, click OK to save the backup policy.
26. Verify that a entry for the LAB-dnas-nfs-backup policy is listed in the All Policies pane.

Performing and monitoring D-NAS backups

27. In the All Policies pane, right-click the LAB-dnas-smb-backup policy and then click Manual Backup.
28. In the Manual Backup window, click OK to start the backup.
29. In the NetBackup Administration Console, in the object tree, click Activity Monitor.
30. In the Activity Monitor, locate the job(s) that were started as a result of the manual backup operation
that was performed using the LAB-dnas-smb-backup policy.

You should see the following jobs in the Activity Monitor:

 o A parent and a child Snapshot job.

The Snapshot job instructs CloudPoint to create a snapshot of the volume included for backup in the
backup policy. The snapshot of the volume is then stagged for the backup on one of the backup host
in the Backup Host Pool.

o A parent Backup From Snapshot job and four Backup From Snapshot child jobs.

It might take a couple of seconds for the Backup From Snapshot jobs to appear in the Activity
Monitor.

The number of backup streams can be controlled by modifying the Maximum number of streams
per volume setting available in backup policy under the Attributes tab. By Default, the value for this
setting is set to 4 per volume. Since the LAB-dnas-smb-backup policy includes only one volume in
its Backup Selections, four Backup From Snapshot jobs were started as a result of the manual
backup operation.

In this case, each NAS volume or share is read over SMB (as oppossed to NDMP used with traditional
NDMP backups), and backed up using the configured number of backup streams.

Another setting, the Maximum number of files in a batch available int the backup policy under the
Attributes tab can be used to control the number of files that will be include in each backup stream.
By Default, the value for this setting is set to 500 files per stream.

Wait for all the Backup From Snapshot jobs to complete.

It might take a 10-12 minutes for this backup to complete.

31. Optionally, after the backup from snapshot jobs complete, double-click each job and review the contents
in the Job Overview and Detailed Status tabs.
32. Close any Job Details windows that you might have opened.
33. In the NetBackup Administration Console, in the object tree, click Policies.
34. In the All Policies pane, right-click the LAB-dnas-nfs-backup policy and then click Manual Backup.
35. In the Manual Backup window, click OK to start the backup.
36. In the NetBackup Administration Console, in the object tree, click Activity Monitor.
37. In the Activity Monitor, locate the job(s) that were started as a result of the manual backup operation
that was performed using the LAB-dnas-nfs-backup policy.

You should see the following jobs that you saw when you ran a manual backup using the LAB-dnas-smb-
backup policy. The only difference between these two jobs is the protocol that is used for transferring data. In
this case, the NFS protocol is used for reading the data.

Wait for all the Backup From Snapshot jobs to complete.

It might take a 10-12 minutes for this backup to complete.

 38. Optionally, after the backup from snapshot jobs complete, double-click each job and review the contents
in the Job Overview and Detailed Status tabs.
39. Close any Job Details windows that you might have opened.
40. Remain logged in to the NetBackup Administration Console.

You will return to it later in this lab.

Exercise G: Restoring Files from DNAS Backups

In this exercise, you will restore files using one of the backup images that were created earlier in this lab by
performing manual backups of the LAB-dnas-smb-backup and the LAB-dnas-nfs-backup backup policies.

Restoring files

1. In the NetBackup Administration Console, in the object tree, click Backup, Archive, and Restore.
2. Click the Restore Files tab in the right-pane of the NetBackup Administration Console.
3. On the NetBackup Administration Console toolbar, click Actions > Specify NetBackup Machines and
Policy Type.
4. In the Specify NetBackup Machines and Policy Type window, perform the following:
a. Ensure that lnxmaster.vrtsedu.lab is selected in the Server to use for backups and restores drop-
down list.
b. Select netapp-cluster.vrtsedu.lab@vsrv1 in the Source client for restores drop-down list.

If the netapp-cluster.vrtsedu.lab@vsrv1 entry is not visible in the Source client for restores drop-
down list, click Refresh in the Specify NetBackup Machines and Policy Type window.

c. Select lnxmaster.vrtsedu.lab in the Destination client for restores drop-down list.

Restores to the original located are not supported for the NAS-Data-Protection policy. Also the
destination client used for restores should be a NetBackup host.

d. Select NAS-data-Protection in the Policy type for restores drop-down list.

e. Click OK.
5. In the No Files Found dialog box, click OK.
6. On the NetBackup Administration Console toolbar, click Actions > Set Keyword.
7. In the Keyword Phrase dialog box, delete any keywords that are present and click OK.

To delete a keyword, select and delete the entry displayed in the Keyword Phrase dialog box.
8. In the Directory Structure pane, perform the following:
a. Expand the / node and then expand the vsrv1_cifs node.
b. Click (do not select) share1.

The contents of the CIFS share, share1 are displayed in the Contents of selected directory pane.

9. In the Contents of selected directory pane, select the checkbox next to the Doc_files folder to select this
folder for restore.
10. After selecting the Doc_files folder in the Contents of selected directory pane, click Restore.
11. In the Restore Marked Files window, deselect the Rename hard links and the Rename soft links option
and then click Start Restore.
12. In the View Progress dialog box, click Yes to view the progress of the restore.
13. In the Task Progress tab, monitor the restore task.

Wait for this restore to complete before proceeding.

It might take 8-12 minutes for the restore to complete.

14. Close the NetBackup Administration Console.

Verifying the restored files

15. Double-click the PuTTY shortcut located on the desktop of the console system.
16. In the PuTTY Configuration window, double-click the preconfigured entry for the Master/Primary
server, lnxmaster.vrtsedu.lab.
17. Log in to the lnxmaster.vrtsedu.lab system using the following credentials.
o Username: root
o Password: P@ssw0rd

18. In the root@lnxmaster:~ terminal window, execute the following command to list contents of
the / partition.

Command: ls -l /

After the restore a structure similar to the following will be created.

\\10.10.2.132\vsrv1_cifs\share1\Doc_files\

19. Execute the following command view the contents of the Doc_files directory that was restored.

Command: ls -l //\\10.10.2.132/vsrv1_cifs/share1/Doc_files/

Note that the files backed up using the D-NAS feature are successfully restored to a NetBackup host.
 20. In the root@lnxmaster:~ terminal window, type exit and press Enter to log out of the lnxmaster system.
21. Log out of the console system.

Lab - Appendix B: Managing and Configuring Tape Storage

Exercise A: Verifying and Discovering Tape Devices

The tape drives and the robotic library have already been configured on the master server
system, lnxmaster.vrtsedu.lab. However, the tape devices have not been configured for use on the media
server, lnxmedia.vrtsedu.lab.

In this exercise, you:

 Verify that the media server operating system can detect the attached tape devices.
 Verify that NetBackup can discover the tape devices that are visible to the media server operating system.
 Discover that the tape devices that are visible to the media server operating system are the same tape
devices that are visible to and configured for use on the master server system.

Verifying tape devices on the media server

In the steps that follow, you verify that your media server operating system can see the tape devices (tape drives
and robotic control). These devices are not yet configured for use by this NetBackup media server system.

1. Sign in to the console system using the following credentials.

o Username: VRTSEDU\Administrator
o Password: P@ssw0rd

2. Double-click the PuTTY shortcut located on the desktop of the console.vrtsedu.lab system, to
launch PuTTY.

Within a moment the PuTTY Configuration window is displayed.

3. Double-click the pre-configured entry for the media server system, lnxmedia.vrtsedu.lab.
4. Login to the media server system using the following credentials.
o Username: root
o Password: P@ssw0rd
5. Type the following command, and press Enter, to verify that the operating system detects the tape drives.

Command: ls /dev/nst*

The above command lists non-rewinding tape devices.

The output of the ls command should be similar to that as shown here.

The output of the command identifies two tape drives that are visible to the operating system of the media
server, nst0 and nst1. The various letters that follow the nst entries (l, a, m) denote various compression
methods that can be used for the tape drives.

6. Type the following command, and press Enter, to view the tape devices that are configured for use by the
Linux media server system.

Command: /usr/openv/volmgr/bin/tpconfig -d

The output of the tpconfig command is similar to that as illustrated.

 The command output indicates that no tape devices (tape drives or media changers) are configured for use
by the Linux NetBackup media server, lnxmedia.vrtsedu.lab. This is expected.

7. Type the following NetBackup-provided command, and press Enter, to view information for the media
changer(s) that are detectable by the command.

Command: /usr/openv/volmgr/bin/scan -changer

The output of the scan command is similar to that displayed in the following figure.

8. Type the following command, and press Enter, to view the information for the tape drives that are
detectable by the command.

Command: /usr/openv/volmgr/bin/scan -tape

The output of the scan command is similar to that displayed in the following figure. Note that the output of
the scan command shown is cut off, so that only a portion of the information for the second tape drive is
visible.

Take note of the information for the media changer and tape drives associated with the media server system.

Tape devices attached to lnxmedia.vrtsedu.lab:

Device Device Name Serial Number

 Tape devices attached to lnxmedia.vrtsedu.lab:

Changer /dev/sg3 XYZZY_B

Tape Drive /dev/nst0 XYZZY_B2

Tape Drive /dev/nst1 XYZZY_B1

If the robotic library (changer) and tape drives are visible to the NetBackup-provided scan command on the
media server system, you can be confident that the NetBackup Device Configuration Wizard will be able to
configure the devices for use by NetBackup.

The scan command shows that the devices (changer and tape drives) are detectable by NetBackup. However,
in this scenario, (based on the output of the tpconfig command) the devices are not yet configured for use
by your NetBackup media server, lnxmedia.vrtsedu.lab.

9. Close the Terminal window to return to the desktop of the console.vrtsedu.lab system.

Tape devices attached to the master server

For purposes of this course, tape devices (media changer and tape drives) have been pre-configured for use by
NetBackup on the lnxmaster.vrtsedu.lab master server.

In the steps that follow, you access the master server, lnxmaster.vrtsedu.lab and use NetBackup-provided
commands to view the tape devices that are configured for use on that system.

10. Access the desktop of the console.vrtsedu.lab system.

11. Double-click the PuTTY shortcut located on the desktop of the console.vrtsedu.lab system to
launch PuTTY.

Within a moment the PuTTY Configuration window is displayed.

12. Locate and double-click the pre-configured entry for the master server, lnxmaster.vrtsedu.lab.
13. Login to the master server system using the following credentials.
o Username: root
o Password: P@ssw0rd

14. Type the following command, and press Enter, to view the tape devices that are configured for use by the
Linux master server system.

Command: /usr/openv/volmgr/bin/tpconfig -d
 The output of the tpconfig command is similar to the output illustrated.

The output of the tpconfig command on the master server indicates that two tape drives and a robotic
control device (media changer) are configured in NetBackup for use by the master server.

15. Type the following command, and press Enter, to view the information for the media changer(s) that are
detectable on the Linux master server.

Command: /usr/openv/volmgr/bin/scan -changer

16. Type the following command, and press Enter, to view the information for the tape drives that are
detectable by the command.

Command: /usr/openv/volmgr/bin/scan -tape

17. Take note of the media changer information associated with the master server and media server systems,
as shown in the following tables.

Tape devices attached to lnxmedia.vrtsedu.lab:

Device Device Name Serial Number

Changer /dev/sg3 XYZZY_B

 Tape devices attached to lnxmedia.vrtsedu.lab:

Tape Drive /dev/nst0 XYZZY_B2

Tape Drive /dev/nst1 XYZZY_B1

Tape devices attached to lnxmaster.vrtsedu.lab:

Device Device Name Serial Number

Changer /dev/sg3 XYZZY_B

Tape Drive 1 /dev/nst0 XYZZY_B2

Tape Drive 2 /dev/nst1 XYZZY_B1

19. Compare the information for the tape devices that are attached to the media server, with the tape devices
that are attached to the master server. Pay special attention to the serial numbers of the devices.

Your observations of the comparison of the scan command output on the media server and master server
systems should indicate that the serial numbers of all the devices (changer, Tape Drive 1, and Tape Drive 2)
detected by the scan command on the media server are the same as the serial numbers of the devices that
are detected by the scan command on the master server. It appears that both the master server and media
server systems can "see" the same tape devices

Based on the commands you executed on the master server and media server, you have verified that the
master server has tape devices that are configured in NetBackup, and that the media server's operating
system can "see" the tape devices, but these devices are not yet configured in NetBackup.
The scan command on the master and media server systems shows that the media changer and tape drives
that are attached are the same devices.
The NetBackup Shared Storage Option enables tape drives and media changer devices to be shared
between NetBackup master and media servers that exist in the same NetBackup backup domain.

20. Close the Terminal window to return to the desktop of the console.vrtsedu.lab system.
Exercise B: Viewing Configured Tape Devices

In this exercise, you use the NetBackup Administration Console to view the tape devices (robots and tape drives)
that have been pre-configured on the master server.

Viewing configured tape drives and robots

In the steps that follow, you view the tape drives and robots (media changers) that have been configured (pre-
configured for this course) in NetBackup.

1. On the desktop of the console.vrtsedu.lab system, double-click the NetBackup 10.0 NetBackup
Administration Console shortcut to launch the NetBackup Administration Console.
2. In the NetBackup Administration Console login window that is displayed, login using the following
credentials.
o Host name: lnxmaster.vrtsedu.lab
o User name: root
o Password: P@ssw0rd

3. In the left pane of the NetBackup Administration Console, select Media and Device Management and
then select Devices > Drives.

The tape drives that are currently configured in NetBackup are displayed in the right pane of the NetBackup
Administration Console.

4. Take note information for the configured tape drives as shown in the following table.

Drive Name Device Host Drive Type Robot Type Robot # Robot drive #

IBM.ULT3580-TD5.000 lnxmaster.vrtsedu.lab HCART2 TLD 0 2

IBM.ULT3580-TD5.001 lnxmaster.vrtsedu.lab HCART2 TLD 0 1

5. Select Media and Device Management and then Devices > Robots in the left pane of the NetBackup
Administration Console
6. Take note of the information for the configured robot in the following table.

Robot Name Device Host Robot Type Robot Number

 TLD(0) lnxmaster.vrtsedu.lab TLD 0

7. In the preceding steps, you identified the robot (media changer) and tape drives that are already configured
in NetBackup (these were pre-configured for this course). All these devices are associated with the master
server, lnxmaster.vrtsedu.lab.
8. There are currently no tape devices (robots or tape drives) configured for use by NetBackup on the media
server system, lnxmedia.vrtsedu.lab.

Viewing configured Media Manager storage units

In NetBackup terms, a storage unit that uses NetBackup-configured tape drives for backup and restore-related
operations has the storage unit type of Media Manager.

In the steps that follow, you view the Media Manager storage units that have been configured (pre-configured for
this course) for use by NetBackup.

7. In the left pane of the NetBackup Administration Console, Select NetBackup Management and then
select Storage > Storage Units.

The Storage Units that are currently configured in NetBackup are displayed in the right pane of the
NetBackup Administration Console.

Some of the storage units listed were pre-configured for this course. You may have created other storage
units in previous lab activities.

8. Locate the Storage Unit Type column in the right pane of the NetBackup Administration Console.
9. Take note of the information for the storage unit that has a Storage Unit Type of "Media Manager" in
the following table.

Robot Robot Max. Concurrent

Name Media Servers
Type Number Drives

master_tape_stu lnxmaster.vrtsedu.lab TLD 0 2

10. Double-click the entry for the master_tape_stu storage unit, to open the storage unit for editing.

The Change Storage Unit window is displayed and displays the current configuration settings for
the master_tape_stu storage unit.

11. Briefly view the current settings for the storage unit, and then click Cancel to close the Change Storage
Unit window without making any changes to the storage unit configuration.
 In the previous steps you verified that a single Media Manager type storage unit exists. This storage unit is
associated with the master server and uses tape drives (two) configured on the master server to perform
NetBackup-related operations to tape storage.

The Media Manager type storage unit that currently exists was pre-configured for use in this course.

Exercise C: Configuring Tape Devices

As it currently exists, NetBackup is configured to use the tape drives and robot (media changer) that are associated
with the master server system to perform NetBackup operations to tape storage. To enable NetBackup operations
that write to tape storage, a Media Manager-type storage unit has been configured on the master server.

In this exercise, you use the NetBackup Device Configuration Wizard to configure tape devices.

Configuring tape devices (using the wizard)

In the steps that you follow, you use the NetBackup Device Configuration Wizard to configure tape devices and
a storage unit associated with the robot and tape drives for the media server system.

1. Click the entry for the master server, lnxmaster.vrtsedu.lab, located at the top of the left pane of the
NetBackup Administration Console window.

The list of NetBackup wizards that are available on a master server are displayed in the right pane of the
NetBackup Administration Console.

2. Locate and click the Configure Storage Devices entry, located in the right pane of the NetBackup
Administration Console.

A Device Configuration Wizard window is displayed.

The Device Configuration Wizard is used specifically for configuring tape devices and Media
Manager storage units for use by NetBackup.

3. Click Next in the wizard to continue.

The wizard Device Hosts screen is displayed.

This screen contains entries/selections for both media servers in your lab
environment, lnxmaster.vrtsedu.lab and lnxmedia.vrtsedu.lab.

4. Verify that the selections for both the master server host and media server host are selected on
the Device Hosts screen (the default), and then click Next to continue.
 The Scanning Hosts screen is displayed.

After a few moments, the wizard displays the number and types of devices - robots and tape drives - that
were discovered on each Device Host that was scanned.

5. Click Next on the Scanning Hosts screen to continue.

The SAN Clients screen is displayed, that enables you to configure the SAN Client feature.

6. Click Next to continue, without making any changes on the SAN Clients screen.

The Backup Devices screen is displayed, and lists the tape devices (tape drives and robots) that have been
discovered.

The Backup Devices screen is divided into two sections. The top half of the screen lists the backup devices
(tape drives and robots) that have been discovered. The bottom half of the screen provides the Host and
path configuration for a device, when a device entry is selected (clicked) in the Backup Devices section of
the screen.

When the entry for a tape drive is selected in the Backup Devices section of the screen, the host and path
configuration information for that tape drive is displayed in the Host and path configuration section of the
screen, as illustrated.
7. Click each tape drive and robot entry in the Backup Devices pane, one-at-a time, and view the Host and
path configuration information that is displayed for that device.
8. Click the Properties button to view detailed properties as shown in the following screenshot.

An example of the Properties window for a device is illustrated.

9. Click Cancel to close the Drive Properties window.
10. View the Properties window for each of the devices listed in the Backup Devices list, one-at-a-time.

While viewing the information provided in the Properties windows, take note of the following information.

The Properties window for each device identifies the device type clearly.

For a robot, the Properties window identifies the Robot number, the Robot type, and the number of
drives in the robot.

For tape drives, the Properties window provides the Drive name, Drive type, Robot (with which the drive is
associated), and the Robot drive number (drive position within the robot).

When you view the Properties of the robot, one media server is designated as the Device Host, while the
other (or all others) is identified as a Remote Host.

IMPORTANT CONCEPT: In NetBackup, the term that is used to describe the Device Host that controls the
robotic arm is the Robot Control Host. Other media servers (Device Hosts) in the same NetBackup
environment make robotic requests (mount, unmounts tapes) by sending them to the Robot Control Host.

In this lab environment, take note of which media server (Device Host) is acting as the Robot Control host?
 The lnxmaster.vrtsedu.lab system is acting as the Robot Control host in this lab environment.

11. Close any open Properties window.

If the Backup Devices screen shows limitations, those should first be resolved before continuing with wizard.

12. Click Next in the Backup Devices screen, to continue.

The Drag and Drop Configuration screen is displayed. This screen associates the discovered tape drives with
the robot (tape library and robotic control arm).

If a tape drive cannot be associated with a robot, it will be displayed as a standalone tape drive. If that is the
case, it will be up to the backup administrator to manually associate the tape drive (drag and drop) with the
appropriate robot (and drive position within the robot).

In this lab environment, NetBackup is able to properly associate the discovered tape drives with their
positions within the robot (tape library).

13. Click Next in the Drag and Drop Configuration screen to continue.

The Continue? window is displayed, prompting you to confirm that you wish to commit these changes to the
NetBackup database.

14. Click Continue in the Continue? window to commit the changes to the NetBackup database.

The Updating Device Configuration screen is displayed.

When the Updating Device Configuration screen is displayed, NetBackup begins updating the device
configuration information in its database (NBDB) with the information you have provided using the Device
Configuration Wizard. Updates to the database could take a few moments to complete. When completed,
the Next button becomes available for selection.

15. Click Next in the Updating Device Configuration screen to continue and proceed to the Configuring
storage units section in this exercise.

Configuring storage units (using the wizard)

In the next steps, you use the Device Configuration Wizard to configure a storage unit (or storage units) that are
associated with the newly configured tape hardware.

When you clicked Next on the Updating Device Configuration screen, the Device Configuration
Wizard displayed the Configure Storage Units screen.

The following figure illustrates how the Device Configuration Wizard should currently appear with the Configure
Storage Units screen being displayed.
The Configure Storage Units screen of the Device Configuration Wizard lists the storage units that it proposes
to create, based on the newly configured tape devices (that were just configured by the wizard).

Because the robot and tape drives on the master server had already been configured (prior to running the wizard),
and because the Media Manager storage unit was already configured on the master server, the Configure
Storage Units screen displays its intent to create only a single storage unit for the tapes drives on the media
server system.

16. Click the entry for the Storage Unit listed on the Configure Storage Units screen, lnxmedia-hcart2-
robot-tld-0, and then click the Properties button.

The Change Storage Unit Properties window is displayed.

17. Change the properties for the new storage unit, using the parameter values provided in the following
table.

Parameter Parameter value / setting

Storage unit name: media_tape_stu (change this setting)

Media server: ** lnxmedia.vrtsedu.lab

Storage unit type: ** Media Manager

On demand only: not selected (default)

 Parameter Parameter value / setting

Storage Device: ** TLD(0) – HCART2

Robot type: ** TLD – Tape Library DLT

Density: ** hcart2 – ½ Inch Cartridge 2

Robot number: ** 0

Maximum concurrent write drives: 2

Maximum multiplexing per drive: 1

Reduce fragment size to (checkbox): Not selected (default)

1048576 (not changeable unless Reduce fragment

MB (fragment size):
size checkbox is selected)

** You cannot change this setting for the

storage unit

18. It is not required that the name of the storage unit is changed, however we have established a storage unit
naming convention for this lab environment. The storage unit name is changed to adhere to that naming
convention.
19. After making the changes to the storage unit, click OK to save the changes, and to close the Change
Storage Unit Properties window.
20. Verify that the Configure Storage Units screen of the Device Configuration Wizard contains the entry
for the new storage unit, media_tape_stu.
21. Click Next on the Configure Storage Units screen to continue.

The Device Configuration Wizard displays the Finished screen.

22. Click Finish to close the Device Configuration Wizard.

Viewing the new tape devices and storage unit entries

In the steps that follow, you use the NetBackup Administration Console to briefly view the entries for the newly
created robot, tape drives, and storage unit.

22. Select Media and Device Management and then select Devices > Drives in the left pane of
the NetBackup Administration Console.

The right pane of the NetBackup Administration Console displays the list of configured tape drives.

23. Note that the right pane of the NetBackup Administration Console is split into two panes --
the Drives pane (top pane) and the Paths for selected drives pane (bottom pane).
24. Click the entry for one of the tape drives in the top pane, and note that the bottom pane changes to
display the tape drive path information for the selected tape drive.

Note that the information in the Paths the selected drive pane (bottom pane) contains two entries for each
of the configured tape drives. One of the entries is for the master server (lnxmaster.vrtsedu.lab) and the
other entry is for the media server (lnxmedia.vrtsedu.lab). This means that each of the tape drives is shared
by the master and media servers, and is available for use by both the master and media server. This illustrates
the tape drive configuration of the NetBackup Shared Storage Option.

25. Click the entry for the other tape drive in the top pane, and note that the bottom pane changes to display
the tape drive path information for the selected tape drive.
26. Select Media and Device Management and then select Devices > Robots in the left pane of the
NetBackup Administration Console.

The right pane of the NetBackup Administration Console displays entries for the robots (media changers) that
are currently configured in NetBackup.

There should be two (2) robot entries are listed in the right pane of the NetBackup Administration Console.

The first Device Host listed for each of the robot entries should be the master server and the second Device
Host entry should be for the media server.

You should note that the system (Device Host) that is listed as the Robot Control Host is the master server.

In this lab environment, there is a single tape library with two tape drives that is shared between the master
server and media server systems. The robotic arm in the library is controlled directly by only one of the Device
Hosts (media servers). That Device Host operates in the role of Robotic Control Host. When the other Device
Host (media server) requires the mounting or unmounting of a tape in a tape drive, it makes the request to
the Robot Control Host, which completes the requested activity.

27. Select NetBackup Management and then select Storage > Storage Units in the left pane of the
NetBackup Administration Console.
 The storage units that are currently configured in NetBackup are displayed in the right pane of the NetBackup
Administration Console.

28. Locate the entry for the newly configured storage unit, media_tape_stu.
29. Verify that the media_tape_stu is associated with your media server, lnxmedia.vrtsedu.lab, as it is
a Media Manager type (tape-based) storage unit, and is configured for access to a maximum of two
concurrent tape drives.

Exercise D: Configuring Volume Pools

In this exercise, you configure volume pools that will house tape media that is allocated for use by NetBackup for
various customer-defined purposes.

1. Select Media and Device Management and then select Media > Volume Pools in the left pane of the
NetBackup Administration Console.

NetBackup provides four volume pools by default. The entries for the default pools are visible in the right
pane of the NetBackup Administration Console.

o CatalogBackup
o DataStore
o NetBackup
o None
2. Create the volume pools shown in the following tables.

The following table provides parameters for volume pools to be created.

Max number of partially full Scratch Catalog backup

Pool Name Description
media pool pool

scratch_tapes available tapes 0 checked cleared

file system
server_tapes 0 cleared cleared
backups

copies of
duplicate_tapes 0 cleared cleared
backups

hidden_tapes unavailable tapes 0 cleared cleared

Refer to the following table for the detailed steps to create a volume pool.
 Step
Step description
#

Select Media and Device Management > Media > Volume Pools in the left pane of the
1
NetBackup Administration Console.

2 Select Actions > New > Volume Pool.

The New Volume Pool window is displayed.

Enter the parameters for the new volume pool in the fields of the New Volume Pool window.
3
The Pool name is the only required volume pool parameter.

4 Click OK to save the volume pool, and to close the New Volume Pool window.

3. As you save each volume pool, verify that an entry for the new pool is visible in the right pane of the
NetBackup Administration Console.
4. Repeat the steps to create the new volume pools until all pools have been created.

Only one scratch pool can be created per NetBackup domain. NetBackup will issue an error message if
additional scratch pools are created.

As a result of performing the above steps, the NetBackup Administration Console displays the list of volume
pools, as illustrated in the following figure.

5. Note that the scratch_tapes volume pool is designated as a Scratch pool, and that
the CatalogBackup volume pool is designated as a Catalog Backup volume pool.
Exercise E: Configuring Media

In NetBackup terms, media refers to "removable media", which most commonly takes the form of magnetic tape.
Here is a brief summary of important media details.

 Tape media comes in a variety of physical packages, based upon the type of tape drive in which the media
is used.
 The data capacity of a tape is determined by the characteristics of the tape drive that is used to write the
data.
 Tapes, or tape volumes, are identified in NetBackup by their unique Media ID.
 NetBackup media IDs are six alpha-numeric characters in length.
 Tape media often use a barcode label that is affixed to the tape cartridge, to enable automatic
identification of the tape by a tape library.
 Barcode labels can vary in length, with common barcode lengths being six or eight alpha-numeric
characters.
 Media IDs can be added manually in NetBackup, or automatically by performing an Inventory Robot
operation in NetBackup.
 In order for NetBackup to properly generate Media IDs for tapes using the Inventory Robot operation, it is
generally necessary to create rules that define how NetBackup will interpret and apply barcodes of varying
lengths.
 When NetBackup uses a tape for the first time it writes a header to the tape that includes the Media ID
that has been assigned to the tape.

Preparing to configure media with Robot Inventory

One method of configuring tape media in NetBackup is to load tapes (with barcode labels affixed) into the tape
library, and to initiate the Inventory Robot operation to automatically create and add entries for the tapes into the
NetBackup catalog.

To enable the Inventory Robot operation to correctly identify and create media IDs for tapes, two prerequisite
tasks are generally required:

 Creating a Media ID generation rule

 Creating one or more barcode rules

The steps that follow guide you through the process of performing these tasks in preparation for completing the
robot inventory operation.

1. Access the NetBackup Administration Console that is open on the console.vrtsedu.lab system.
2. Select Media and Device Management and then select Media in the left pane of the NetBackup
Administration Console.

The tapes that are currently configured in NetBackup are displayed in the right pane.

3. Select Actions and then select Inventory Robot.

 The Robot Inventory window is displayed.

The following figure illustrates the top half of the Robot Inventory window.

4. Note the following elements listed in the Robot Inventory window.

o Device Host: The name of the NetBackup server that directly controls the robot.
o Robot: The robot name (as assigned in NetBackup). If more than one robot is configured in
NetBackup, you must specify the robot that is to be inventoried.

Note the four primary operations available from the Robot Inventory window listed.

o Show contents (of the robot)

o Compare contents with volume configuration (in the NetBackup media database)
o Preview volume configuration changes (that will be made to the NetBackup media database if you
proceed with the robot inventory operation)
o Update volume configuration (in the NetBackup media database)

Note that there two additional operations located under the Update volume configuration operation
that are currently greyed out (not selectable).

o Advanced Options
o Empty media access port prior to update
5. Verify the Show contents radio button is selected, then click the Start button in the Robot
Inventory window.

The following figure provides an example of the results of the Show contents operation, as displayed in
the Results pane of the Robot Inventory window.
6. Note the Results of the Show contents operation list as follows.
o This robot (tape library) has thirty-nine (39) tape slots, numbered 1-39.
o Only 13 of the 39 slots are currently occupied by tapes.
o The barcode labels on the tapes are eight alpha-numeric characters in length.
o The final two characters of the barcodes of all the tapes are identical (L5).
o The tapes in slots 22 and 23 of the robot have different characters in the first three positions of their
barcode labels than all the other tapes. For your information, these two tapes are cleaning tapes. The
cleaning tapes used by this customer all have barcode labels beginning with the characters CLN.

If you wish you can use the Clear Results button (located in the lower right corner) to clear the data from the
previous query.

7. Click to select the Compare contents with volume configuration radio button in the Robot
Inventory window, and then click the Start button.

The Results pane of the Robot Inventory screen is updated to show the results of the Compare
contents… operation, as illustrated in the following figure.
 The Compare contents with volume configuration operation compares the current contents of the robot
(tape library) with the entries in the NetBackup media database, to determine if entries for the tapes already
exist in the database or if new entries should be created.

8. Note the following in the Results pane of the Robot Inventory window.
o The tapes that reside in slots 1, 2, and 3 of the robot are already known to NetBackup (there are
entries for these tapes in the NetBackup media database).
o NetBackup is using the first six digits of the barcode of the tapes in slots 1 -- 3 as the Media ID for
the tapes, to uniquely identify them in NetBackup.
o The tapes that reside in slots 1 -- 11 and 22 - 23 of the robot are not known to NetBackup (there is
no entry for any of these tapes in the NBDB). As a result, the Robot Inventory reports a "Mismatch
Detected" for these tapes. A Mismatch Detected can be displayed for various other reasons, such as
detecting a known tape in an unexpected slot location.
9. Click the Preview volume configuration changes radio button in the Robot Inventory window, to select
that operation, and then click the Start button.

The Results pane of the Robot Inventory screen is updated to show the results of the Preview volume
configuration operation.

The Preview volume configuration operation identifies and lists the changes that NetBackup proposes to
make to the NetBackup media database -- if the Robot Inventory is allowed to proceed.
10. Note the following in the Results pane of the Robot Inventory window:
o NetBackup proposes to add new entries to its media database for the ten (10) tapes, located in slots 1
-- 11 and 22 -- 23, of the robot.
o NetBackup proposes to use the last six digits of the barcode for each tape to create the Media ID
that will identify the tape in NetBackup.
o The tapes in slot 22 -- 23 are cleaning tapes and cannot be used to write backup images.
o The backup administrator is aware that the barcode labels for all cleaning tapes used by this customer
begin with the characters CLN. NetBackup must use some method to automatically identify this tape
as a cleaning tape.

IMPORTANT: The default media ID generation rule in NetBackup (used to automatically generate media IDs
during a robot inventory operation) uses the last six digits of a tape's barcode to generate the media ID for
the tape.

IMPORTANT: It is critical that the backup administrator understand whether the default media ID
generation rule used by NetBackup will reliably generate Media IDs that are unique. Six-digit Media
IDs must be unique in the NetBackup media database.

In the example, the fact that all barcode labels for the tapes end in the same two alpha-numeric characters
(L5), means that these two digits provide no value in generating unique Media IDs. In a scenario such as
this, it is important that a new Media ID Generation Rule be created in NetBackup, so that other digits of the
barcode labels (such as the first six digits) are used during a robot inventory to automatically generate the
Media IDs for the tapes.

IMPORTANT: If a customer uses special barcode labels to identify tapes used for a unique purpose (i.e.,
cleaning tapes, tapes of a particular media density), NetBackup must provide a method to use the unique
barcode of the tapes to identify and allocate those tapes for their unique purpose. This capability is provided
in NetBackup through the use of Barcode Rules.

In the example shown here, the backup administrator should create a Barcode Rule that identifies all tapes
with barcode labels beginning with the characters, CLN, as ½-inch cleaning tape cartridges.
 In the steps that follow, you perform the steps to create a Media ID Generation Rule and to create
a Barcode Rule in NetBackup.

Creating a Media ID Generation Rule

In the steps that follow, you perform a Robot Inventory to update the volume configuration for the robotic library.

11. Click the Update volume configuration radio button in the Robot Inventory window, to select that
operation.
12. Click the Advanced Options button, located immediately below the Update volume
configuration operation entry, as illustrated.

The following figure highlights the Advanced Options button of a Robot Inventory.

When you click the Advanced Options button, the Advanced Robot Inventory Options window is
displayed.

The following figure illustrates the Advanced Robot Inventory Options window.
13. Click the Media ID Generation tab, located near the top of the Advanced Robot Inventory
Options window.

The contents of the Media ID Generation tab are illustrated.

14. Use the information provided in the following tables to create a new Media ID Generation Rule that uses
the first six characters of eight-character barcode labels of tapes to automatically generate the Media IDs
for the tapes.

Media ID Generation parameter Parameter value /setting

Robot number: 0

Barcode length: 8

Media ID generation rule: 1:2:3:4:5:6

15. The following table provides detailed steps for creating a Media ID Generation Rule.
16. To create a Media ID Generation Rule, follow the steps.

Step
Step details
#

Select Media and Device Management > Media in the left pane of the NetBackup Administration
1
Console.

2 Select Actions > Inventory Robot.

3 Click to mark the Update volume configuration radio button.

4 Click the Advanced Options button.

5 In the Advanced Robot Inventory Options window, click the Media ID Generation tab.

6 In the Media ID Generation tab, click the New button.

Enter the values for the new media ID generation rule in the fields of the New Media ID Generation
7
Rule window.

Click OK in the New Media ID Generation Rule window, to save the values for the new rule, and to
8
close the window.

17. After saving the new Media ID generation rule, and closing the New Media ID Generation Rule window,
verify that the rule is visible in the Media ID Generation tab.

You have configured a Media ID generation rule that NetBackup uses to automatically interpret the barcode
labels on tapes in the library to generate the six-digit NetBackup media ID that NetBackup uses to identify
the tapes.

You have not yet configured NetBackup barcode rules. Before you take that step, complete the Robot
Inventory operation to view the results provided by the creation of the Media ID generation rule -- as
described in the steps that follow.
Completing the first Robot Inventory operation

In the steps that follow, you perform the steps to complete the first robot inventory operation using
the NetBackup Administration Console.

16. Click OK to close the Advanced Robot Inventory Options window.

17. Verify that you are returned to the Robot Inventory window, and that the Update volume
configuration radio button is still selected.
18. Click the Start button in the Robot Inventory window, to initiate the update of the NetBackup media
database to add entries for the new tapes that were discovered in the robot (using the Media ID generation
rule that you created).

The Results pane of the Robot Inventory screen is updated to show the results of the Update volume
configuration operation, as illustrated in the following figure.

19. Note the following in the Results pane of the Robot Inventory window:
o NetBackup created Media ID entries for the tapes in the robot.
o The Media IDs created are six alpha-numeric characters in length, using the first six characters of the
barcode labels that are affixed to the tapes. (Recall that all of the barcode labels are eight characters
in length, with the last two characters being L5 (i.e., E02003L5 (Linux)).
o The Media IDs that were created are associated with the appropriate tape slot location in the robot (in
which the tapes are currently resident.
20. Click Close to close the Robot Inventory window on console.vrtsedu.lab.
21. Verify the following items listed:
o The NetBackup Administration Console is displayed.
 o The Media and Device Management > Media entry is selected in the left pane of the NetBackup
Administration Console.
o The right pane of the NetBackup Administration Console displays the list of Volumes that are
currently configured in NetBackup.
22. Take note that new entries have been added for the Media IDs:
o On lnxmaster.vrtsedu.lab: Media IDs E02001 -- E02011, and CLN201 -- CLN202

23. Take note of and compare the Media ID and Barcode for each of the tapes that are listed. Record your
observations and conclusions in the following table.

The Media IDs were created by the Robot Inventory operation using the first six digits of the barcode label,
and excluding the last two digits of the barcode labels -- which in this scenario are always 'L5'.

The Media ID Generation Rule that was created performed according to plan, resulting in the generation of
Media IDs that are unique for each new tape that was inventoried. Media IDs that already existed in the
NetBackup media database, and that were listed in the NetBackup Administration Console prior to the Robot
Inventory, were not affected.

Based upon your observations and conclusions in the previous step, the Media ID Generation Rule that you
created performed as expected. All tapes belong to the NetBackup volume pool and are of Media Type
'HCART2'.

IMPORTANT: There are two issues with the Robot Inventory operation that must be resolved:

o When new, unassigned Media IDs are added in NetBackup in this lab environment, they should be
added to the SCRATCH pool, so that as a new tape is needed for a write operation, NetBackup can
automatically move a tape from the SCRATCH pool into the volume pool that has been requested (i.e.,
as identified in the Policy volume pool parameter in the policy Attributes tab). Earlier in the lab
activity, you created a SCRATCH pool named scratch_tapes.
o Not all tapes that were inventoried in the previous Robot Inventory operation are HCART2 (½-inch
tape 2) cartridges that are appropriate for writing backup images. In this scenario, any tape that has a
barcode label that begins with the characters, CLN, is a ½" cleaning tape.

In some production backup environments, the use of a scratch pool may not be allowed. The implementation
of a scratch pool in NetBackup is optional. In this environment, we elect to use a scratch pool.

Preparing for a second Robot Inventory operation

To correct the issues identified in the previous exercise and to prepare for a second Robot Inventory operation,
you must first delete the Media IDs that were created by the first Robot Inventory operation.

In the steps that follow, you complete the task of deleting the Media IDs in NetBackup.

24. Access the NetBackup Administration Console window on console.vrtsedu.lab.

25. Select Media and Device Management and then select Media in the left pane of the NetBackup
Administration Console.
 The right pane of the NetBackup Administration Console displays the list of Volumes that are currently
configured in NetBackup.

26. Click the entry for the first/top Media ID, for the master server, lnxmaster.vrtsedu.lab:
o Click the entry for Media ID CLN201.

27. While pressing the SHIFT key on your keyboard, click the entry for the last/bottom Media ID, for the
master server, lnxmaster.vrtsedu.lab:
o Click the entry for Media ID E02011.

28. Verify that all 13 tapes are highlighted.

If the sort order of the tapes differs in your lab environment just make sure all 13 tapes are selected, as shown
in the following figure.

29. Right-click and select Delete.

30. When the Delete Volumes dialog box is displayed, verify the list of volumes to be deleted, and click
the OK button.
31. NetBackup may issue a Delete Volume message (as shown in the following figure) that states one or
more volumes cannot be deleted as it is assigned.

If backups were performed from a policy that used a Media Manger storage unit (tape) then NetBackup is
currently tracking data on these volumes (they are "Assigned") and they cannot be deleted. This is expected
NetBackup behavior. The number of tapes and the Media ID's for which the "cannot delete…" message is
displayed may differ from the following figure.
32. If necessary, click the close (X) icon to the close the Delete Volumes window.
33. Verify the other Volumes were removed from the list of media being displayed in the right pane of the
NetBackup Administration Console.

Now you are ready to repeat the Robot Inventory operation, this time creating barcode rules that address the
two issues that were identified previously.

Creating new barcode rules

In the steps that follow you create two new barcode rules, for the purposes as described:

 The first barcode rule enables NetBackup to automatically identify a ½-inch cleaning tape cartridge, based
upon the first three characters of the barcode label that is affixed (by the backup administrator) to this
type of tape cartridge.
 The second barcode rule assigns all new, non-cleaning tapes that are discovered in the robot during a
Robot Inventory operation to be assigned to the SCRATCH volume pool (The scratch_tapes volume pool
in this scenario).

34. Select Media and Device Management and then select Media in the left pane of the NetBackup
Administration Console.
35. Select Actions and then select Inventory Robot.

The Robot Inventory window is displayed.

36. Verify that the robot, TLD(0) -- lnxmaster.vrtsedu.lab is selected in the Robot field of the Robot
Inventory window.
37. Click to select the Update volume configuration radio button on the Robot Inventory window.
38. Click the Advanced Options button, located directly below the Update volume configuration operation
on the Robot Inventory window.
39. Verify that the Advanced Robot Inventory Options window is displayed.
40. Click the Barcode Rules tab in the Advanced Robot Inventory Options window.
Creating the first barcode rule

In the steps that follow, you create a barcode rule that properly recognizes ½-inch cleaning tape 2 cartridges
during a Robot Inventory, based on the prefix of the barcode label that is affixed (by the backup administrator) to
this type of tape cartridge.

41. Use the information provided in the following table to create a new barcode rule.

This new barcode rule will automatically identify any tape with a barcode that begins with the
characters, CLN, as a ½-inch 2 cleaning tape.

Barcode Rule parameter Parameter value /setting

Barcode tag: CLN

Maximum mounts: 25 - This field is automatically populated when you select the Media type.

Media type ½" cleaning tape 2

Volume pool: None (always used for cleaning tapes)

Description: cleaning tapes

The following table provides the detailed steps for creating a Barcode Rule.

To create a new barcode rule:

Step
Step details
#

Select Media and Device Management > Media in the left pane of the NetBackup Administration
1
Console.

2 Select Actions > Inventory Robot.

3 Click to mark the Update volume configuration radio button.

 Step
Step details
#

4 Click the Advanced Options button.

5 In the Advanced Robot Inventory Options window, click the Barcode Rules tab.

6 In the Barcode Rules tab, click the New button.

7 Enter the values for the new barcode rule in the New Barcode Rule window.

8 Click OK in the New Barcode Rule window, to save the barcode new rule.

42. After saving the barcode rule, verify that the rule is visible in the Barcode Rules tab.

Creating the second barcode rule

In the steps that follow, you create a barcode rule that assigns all new, non-cleaning tapes that are found in the
robot during a Robot Inventory to the scratch_tapes volume pool (which is the SCRATCH volume pool in this
NetBackup environment).

43. Use the information provided in the following table to create a new barcode rule.

This new barcode rule will automatically assign all new, non-cleaning tapes that are found in the robot during
a Robot Inventory to the scratch_tapes volume pool.

Barcode Rule parameter Parameter value /setting

Barcode tag: DEFAULT

Maximum mounts: 0 (leave at the default setting)

Media type DEFAULT

Volume pool: scratch_tapes

 Barcode Rule parameter Parameter value /setting

Description: from scratch pool

44. Click OK to save the new barcode rule, and to close the New Barcode Rule window.
45. Verify that the second barcode rule is visible in the list of barcode rules that are displayed in
the Advanced Robot Inventory Options window.

46. Click OK to close the Advanced Robot Inventory Options window.

Completing the Robot Inventory operation

Having completed the creation of Media ID generation rules and barcode rules, in the steps that follow, you
complete the robot inventory operation and verify the results.

After closing the Advanced Robot Inventory Options window, you are returned to the Robot Inventory window.

47. Verify that the Update volume configuration radio button is still selected.
48. Click the Start button in the Robot Inventory window.

This will initiate the update of the NetBackup media database to add entries for the new tapes discovered in
the robot (using the Media ID generation rule and the barcode rules that you created).

The Results pane of the Robot Inventory screen is updated to show the results of the Update volume
configuration operation, as illustrated.
 49. Note the information listed in the Results pane of the Robot Inventory window.
o NetBackup created Media ID entries for the tapes in the robot.
o The Media IDs created are six alpha-numeric characters in length, using the first six digits of the
barcode labels that are affixed to the tapes. (Recall that all of the barcode labels are eight digits in
length, with the last two characters being L5 (i.e., E02004L5).
o The Media IDs that were created are associated with the appropriate tape slot location in the robot (in
which the tapes are currently resident).
50. Click Close to close the Robot Inventory window on console.vrtsedu.lab.
51. Verify the following:
o The NetBackup Administration Console is displayed.
o The Media and Device Management > Media entry is selected in the left pane of the NetBackup
Administration Console.
o The right pane of the NetBackup Administration Console displays the list of Volumes that are
currently configured in NetBackup.

Verifying the successful creation of Media ID entries

In the final steps of this exercise, you view the Media ID entries that were added, to verify the effective use of the
Media ID generation and barcode rules that you created.

52. Access the NetBackup Administration Console window on console.vrtsedu.lab.

53. In the right pane of the NetBackup Administration Console window, note that new Media ID entries have
been added by the Robot Inventory operation:
o Media IDs E02001 -- E02011, and CLN201, CLN202
54. Take note of the information listed.
o The first six digits of the barcode labels were used to create the NetBackup Media IDs for the newly
created volumes.
o The Media Type for volumes in slots 4-11 are HCART2 (1/2-inch cartridge tape 2)
o The Media Type for the CLN101 or CLN 201 volumes, located in slot 22 is HC2_CLN (1/2-inch cleaning
tape 2)
o The newly created HCART2 volumes belong to the scratch_tapes (the SCRATCH pool for this
NetBackup environment)
o The cleaning tapes (CLN201, CLN202 on Linux) belong to the None pool (cleaning tapes are always
members of the None pool.)

Exercise F: Viewing Tape Drive and Robot Configuration Settings

In this exercise, you use the NetBackup Administration Console to examine details of the robot and tape drives
that are configured in NetBackup.

Examining tape drive parameters

In the steps that you follow, you will use the NetBackup Administration Console to view the drive parameters
configured on your system.

1. Navigate to Media and Device Management > Devices > Drives and click Refresh display button.
2. Right-click the entry for either tape drive in the Drives right pane of the NetBackup Administration
Console.
3. Note the entries that are available in the resulting menu.
4. Click Change in the menu.

The Change Tape Drive window is displayed.

5. Which of the tape drive parameters displayed in the Change Tape Drive window cannot be changed? See
the information listed for the correct answer.

The drive Serial number is the only tape drive parameter that cannot be changed.

Manually changing the parameters for a tape drive should be approached with caution. The preferred method
for updating tape drive configuration is to use the NetBackup Device Configuration wizard.

Examining drive path parameters

In the steps that you follow, you will use the NetBackup Administration Console to examine the drive path
parameters configured on your system.

5. In the Host and path information section of the Change Tape Drive window, select the entry for the
lnxmaster.vrtsedu.lab and click the Change button.

The Change Path window is displayed.

Note that both the Enable host path and Override SCSI reserve path parameters can be changed.

6. Click Cancel in the Change Path window to close the window without making any changes to the drive
path settings.
7. Click Cancel in the Change Tape Drive window to close the window without making any changes to the
tape drive settings.

Examining Robot parameters

In the steps that follow, you examine NetBackup robotic tape library information.

8. Select the Media and Device Management and then select Devices, Robots entry in the left pane of the
NetBackup Administration Console.

Media and Device Management > Devices > Robots

The right pane of the NetBackup Administration Console displays robotic library entries. In this lab
environment two entries are displayed.

Both robot entries are associated with the same robot, named TLD(0). The two entries exist because the tape
drives in the robotic library are accessible by two NetBackup servers - the master server and the media server
- and therefore each of the NetBackup servers require the ability to make requests to the robotic control of
the library.
9. Locate the robot entry in which the Device Host column displays the name of your media server
(lnxmedia.vrtsedu.lab).
10. Use the scroll bar in the right pane to scroll to the right, and locate, and take note of the Robot Control
Host column.

Although both NetBackup servers in the environment require the services of the robot to mount and
unmount tapes in the tape drives of the robotic tape library, only one of the NetBackup servers controls the
robotic arm of the robot. This NetBackup server is referred to as the Robot Control Host.

11. Right-click the robot entry for lnxmaster.vrtsedu.lab Device Host in the right pane of the NetBackup
Administration Console, and click Change.

The Change Robot window is displayed.

12. Verify that the Robot is controlled locally by this device host radio button is already marked.
13. Briefly view the other parameter settings that are available in the Change Robot window.
14. Click Cancel to close the Change Robot window for this device host without making any changes to the
robot settings.
15. Right-click the robot entry for lnxmedia.vrtsedu.lab Device Host in the right pane of the NetBackup
Administration Console and, in the resulting menu, click Change.

The Change Robot window for this device host is displayed.

16. Verify that the Robot control is handled by a remote host radio button is already marked, and note that
the information represents the Robot Control parameter for the media server Device Host.
17. Click Cancel to close the Change Robot window for this device host without making any changes to the
robot settings

The steps you have just completed confirmed the host name of the Device Host that is acting as the Robot
Control Host in this NetBackup environment. It is important to note that any NetBackup server with access to
a configured robot has the capacity to act as the Robot Control Host.

Exercise G: Using the Device Monitor to Monitor and Manage Tape Drives

In this exercise, you use the NetBackup Device Monitor to view and monitor tape drives, and observe the effect
that the tape drive state has on NetBackup jobs.

Investigating the relationship between the Device Monitor and the Media and Device Manager

In the steps that follow, you use the Device Monitor to monitor tape drives and manage their operational state --
up or down.

1. Access the NetBackup Administration Console window on the console.vrtsedu.lab system.

2. Select the Media and Device Management and then select the Device Monitor entry in the left pane of
the NetBackup Administration Console.

The Device Monitor user interface is displayed in the right pane of the NetBackup Administration Console.

3. Verify that the Drives tab is selected at the bottom of the Device Monitor user interface (right pane of
NetBackup Administration Console).
4. Verify the tape drives are in an UP status in the Drives pane (upper pane).
5. Note that the Device Monitor user interface is divided into two panes.

The top pane displays an entry for the configured tape Drives, and the bottom pane displays an entry for the
drive Paths for the tape drive entry that is selected in the top pane.
 When no tape drive entry is selected in the Drives (top) pane, the Paths (bottom) pane of the Device
Monitor contains no drive path entries.
You can adjust the height of the Drives (top) and Paths (bottom) panes of the Device Monitor by dragging
the bar that separates the panes by clicking and dragging the bar that separates the two panes upwards or
downwards, as illustrated previously.

6. Take note of the Device Monitor contents, specifically the following items .

There are two tape drive entries displayed in the Drives (top) pane of the Device Monitor.

When the top (first) tape drive entry is selected in the Drives pane, two drive path entries are displayed in
the Paths (bottom) pane. One of the path entries is for the master server, and the other is for the media
server.

When the bottom (second) tape drive entry is selected in the Drives pane, two drive path entries are
displayed in the Paths (bottom) pane of the Device Monitor.

7. Select Media and Device Management and then select Devices, Media Servers in the left pane of the
NetBackup Administration Console.
8. Refresh the information in the right pane of the NetBackup Administration Console.

View > Refresh or click the Refresh icon on the tool bar.

Note that can also press the F5 key on your keyboard to refresh the current view.

9. Use the information from the right pane (Hosts pane) of the NetBackup Administration Console to
confirm the host names and Status of each of your media server systems as shown in the following table.

Media Server Name Current Status

lnxmaster.vrtsedu.lab Active for Tape and Disk

lnxmedia.vrtsedu.lab Active for Tape and Disk

10. The master server, lnxmaster.vrtsedu.lab is also configured to act as a media server.

Stopping the Media Manager Device Daemon on the media server

In the steps that follow, you stop the Media and Device Manager Daemon on your media server system and
then view tape drives and see the impact it has on drive status.

10. Select Media and Device Management and then select Devices and then Media Servers in the left pane
of the NetBackup Administration Console.
 Media and Device Management > Devices > Media Servers

The right pane of the NetBackup Administration Console displays the Hosts pane, which contains entries for
each of your configured media servers.

11. Perform the steps to stop the Media and Device Manager Daemon on your media server system, using
the following detailed steps.

Step
Detailed Steps
#

Right-click the entry for your media server (lnxmedia.vrtsedu.lab) in the Hosts pane of the
1
NetBackup Administration Console.

2 In the menu, click the Stop/Restart Media Manager Device Daemon entry.

The Stop/Restart Media Manager Device Daemon window is displayed.

Verify that the Device host field of the Stop/Restart Media Manager Device Daemon window
3
contains the host name of your media server system.

4 Click the radio button in the Action box for the Stop action.

5 Verify that the Stop action has been selected (the radio button is marked).

Leave all other Options in the Stop/Restart Media Manager Device Daemon window at their
6
default selections.

Click the OK button in the Stop/Restart Media Manager Device Daemon window, to stop the
7
NetBackup Media Manager Device Daemon on your media server system.

12. The Stop/Restart Media Manager Device Daemon dialog is illustrated.

13.
14. Click the Refresh button on the tool bar to update the contents of the right pane of the NetBackup
Administration Console.

You can also select View > Refresh.

15. Take note of the host names and current Status of each of your media server systems as shown in the
following table.
 OS of your master server Media Server Name Current Status

Linux lnxmaster.vrtsedu.lab Active for Tape and Disk

lnxmedia.vrtsedu.lab Active for Disk

16. The updated Status of your media server should be Active for Disk.
17. Select the Media and Device Management and then select Device Monitor entry in the left pane of the
NetBackup Administration Console.
18. Click the Refresh button on the NetBackup Administration Console tool bar to update the Device
Monitor user interface contents.

You can also select View > Refresh.

19. Click the top tape drive entry in the Drives (top) pane of the Device Monitor and note the information
illustrated.

When the top (first) tape drive entry is selected in the Drives pane, one drive Path entry is listed.

The drive path is for the tape drive on the master server, lnxmaster.vrtsedu.lab (Linux).

The second drive path is missing because the Media Manager Device Daemon is stopped (not running) on
the media server system.

20. Click the bottom tape drive entry in the Drives (top) pane of the Device Monitor and note the
information illustrated.

When the bottom (second) tape drive entry is selected in the Drives pane, one drive Path entry is listed.

The drive path is for the tape drive on the master server, lnxmaster.vrtsedu.lab (Linux).

The second drive path is missing because the Media Manager Device Daemon is stopped (not running) on
the media server system.

At this time, the Device Monitor displays only the drive Paths that are active and available for use. Because
the Media Manager Device Daemon is stopped on the media server system, the Paths for the media server
tape drives are not displayed in the Device Monitor.

21. Select Media and Device Management and then select the Devices, Drives entry in the left pane of the
NetBackup Administration Console.

Media and Device Management > Devices > Drives

 The right pane of the NetBackup Administration Console is split into two panes -- the Drives (top) pane, and
the Paths (bottom) pane.

22. Click the entry for the first (top) tape drive, located in the Drives pane, and take note of the number
of Path entries that are displayed for the drive in the Paths pane.
23. Click the entry for the second (bottom) tape drive, located in the Drives pane, and take note of the
number of Path entries that are displayed for the drive in the Paths (bottom) pane.

The Device Monitor only shows the active and usable tape drive Paths. The Media and Device
Management > Devices > Drives UI displays entries for drive paths that are configured in NetBackup, active
and usable, or not.

Restarting the Media Manager Device Daemon on the media server

In the steps that follow, you restart the Media and Device Manager Daemon on your media server system and
then view tape drives and see the impact it has on drive status.

21. Select Media and Device Management and then select Devices, Media Servers in the left pane of the
NetBackup Administration Console.

The right pane of the NetBackup Administration Console displays the Hosts pane.

Media and Device Management > Devices > Media Servers

22. Perform the following steps to start the Media and Device Manager Daemon on your media server
system (lnxmedia.vrtsedu.lab).

Step
Detailed Steps
#

Right-click the entry for your media server (lnxmedia.vrtsedu.lab) in the Hosts pane of the
1
NetBackup Administration Console.

2 In the resulting menu, click the Stop/Restart Media Manager Device Daemon entry.

The Stop/Restart Media Manager Device Daemon window is displayed.

Verify that the Device host field of the Stop/Restart Media Manager Device Daemon window
3
contains the host name of your media server system.
 Step
Detailed Steps
#

4 Click the radio button in the Action box for the Start action.

5 Verify that the Start action has been selected (the radio button is marked).

Leave all other Options in the Stop/Restart Media Manager Device Daemon window at their
6
default selections.

Click the OK button in the Stop/Restart Media Manager Device Daemon window, to start the
7
NetBackup Media Manager Device Daemon on your media server system.

23. Click the Refresh button on the tool bar to update the contents of the right pane of the NetBackup
Administration Console.
24. Take note of the information in the following table showing the host names and current Status of each of
your media server systems.

OS of your master server Media Server Name Current Status

Linux lnxmaster.vrtsedu.lab Active for Tape and Disk

lnxmedia.vrtsedu.lab Active for Tape and Disk

Configuring a policy to write backups to tape storage on the media server

To prepare for the upcoming steps, create a new policy that writes backup images to tape storage on your media
server system.

25. Select NetBackup Management and then select Policies in the left pane of the NetBackup
Administration Console.
26. Copy the PRE-clients-to-master-tape policy to create a new policy that has the name, Appendix-B-
clients-to-media-tape.

In this lab environment, the policy PRE-clients-to-master-tape is deactivated. You will activate the newly
created policy.

The detailed steps to copy a policy to create a new policy are shown in the following table.
 Step
Detailed Steps
#

Right-click the entry for source policy, PRE-clients-to-master-tape, in the All Policies pane of the
1
NetBackup Administration Console.

2 In the resulting menu, click the Copy to New entry.

The Copy a Policy window is displayed.

In the Copy a Policy window, type the name of the new policy, Appendix-B-clients-to-media-tape,
3
in the New policy field.

4 Verify the policy name, and click OK in the Copy a Policy window.

5 The new policy is displayed for editing in the Change Policy window.

27. In the policy Attributes tab of the Appendix-B-clients-to-media-tape policy, modify the Policy
storage parameter to select the media_tape_stu storage unit and click OK to save the policy.
28. Right-click the policy-Appendix-B-clients-to-media-tape and select Activate.

Do not make any other changes to in the Change Policy window.

Using the Device Monitor to change the status of tape drives

In the steps that follow you use the NetBackup Device Monitor UI to change the status of the tape drives that are
associated with your media server system.

28. Select the Media and Device Management and then select Device Monitor entry in the left pane of the
NetBackup Administration Console.

The right pane of the Device Monitor pane is divided into two panes. The top pane is the Drives pane. The
bottom pane is the Paths pane.

29. Select View and then Refresh, or click the Refresh icon on the tool bar, to refresh the contents of
the Device Monitor.
30. In the Drives (top) pane of the Device Monitor, click the entry for the first (top) tape drive. -
- IBM.ULT3580-TD5.000.
 With the entry for a tape drive selected in the Drives (top) pane, the bottom pane lists the drive Paths that
are associated with the selected tape drive.

In this lab environment, two drive path entries for the selected tape drive are listed in the Paths (bottom)
pane of the Device Monitor.

31. In the Paths (bottom) pane, locate and right-click the path entry that is associated with the Device
Host for your media server (lnxmedia.vrtsedu.lab).
32. In the resulting menu, click Down Path.
33. In the Drives (top) pane of the Device Monitor, click the entry for the second (bottom) tape drive -
- IBM.ULT3580-TD5.001.

With the entry for a tape drive selected in the Drives (top) pane, the bottom pane lists the drive Paths that
are associated with the selected tape drive.

The following figure illustrates the menu that is displayed when you right-click the entry for a drive path in
the Paths (bottom) pane of the Device Monitor UI.

34. In the Paths (bottom) pane, locate and right-click the path entry that is associated with the Device
Host for your media server (lnxmedia.vrtsedu.lab).
35. In the resulting menu, click Down Path, as shown above.
36. Click the Refresh button on the NetBackup Administration Console tool bar (or select View and
then Refresh), to update the contents of the Device Monitor UI.

It may take a few moments for the Device Monitor to register the change in the Drives and Paths pane of
the user interface. In some cases, it may be necessary to click Refresh to update the Device Monitor UI more
than one time.
37. Use the information provided in the following table to confirm the Drive and Path "Control" information
-- based on the contents of the Drives and Paths panes.

Drives (top) pane of Device Monitor

Drive Name Control Shared

IBM-ULT3580-TD5.000 <Mixed> Yes

IBM-ULT3580-TD5.001 <Mixed> Yes

Paths (bottom) pane of Device Monitor

With Drive IBM-ULT3580-TD1.000 selected in the top pane

Drive Name Device Host Control

IBM-ULT3580-TD5.000 lnxmaster.vrtsedu.lab SCAN-TLD

IBM-ULT3580-TD5.000 lnxmedia.vrtsedu.lab DOWN-TLD

With Drive IBM-ULT3580-TD1.001 selected in the top pane

Drive Name Device Host Control

IBM-ULT3580-TD5.001 lnxmaster.vrtsedu.lab SCAN-TLD

IBM-ULT3580-TD5.001 lnxmedia.vrtsedu.lab DOWN-TLD

38. The tape drives and drive paths associated with the master server (lnxmaster.vrtsedu.lab) are currently up
and operational; the drive paths for the media server (lnxmedia.vrtsedu.lab) are DOWN.
39. Click the entry for the Drive Name, IBM-ULT3580-TD5.001, located in the Drives pane of the Device
Monitor.
40. Right-click the entry for the drive path for that drive for the master server Device Host in
the Paths (bottom) pane of the Device Monitor.
41. In the resulting menu, click Down Path.
42. Click the Refresh button on the NetBackup Administration Console tool bar (or select View and then
select Refresh), to update the contents of the Device Monitor UI.

It may take a few minutes for the drive path to be reported as DOWN.

43. View the results in the Drives and Paths panes of the Device Monitor, as illustrated.

The illustration shows the results of taking the second (and final) drive PATH for a tape drive DOWN.

When all paths for a drive are DOWN, the "Control" column entry for the tape drive in the Drives pane of the
Device Monitor is DOWN-XXX (i.e., DOWN-TLD), and the green "up" arrow changes to a red "down" arrow,
as illustrated in the figure above. In other situations, the "Control" contains <Mixed>, as when some drive
paths are up and others are down, or SCAN-xxx (i.e., SCAN-TLD), or XXX (i.e., TLD), when all paths for the drive
are UP.
 When all drive paths for a tape drive are DOWN, the "Control" column entries in the Paths pane of the Device
Monitor contain DOWN-XXX, as illustrated in the figure above.

44. Select the entry for the IBM-ULT3580-TD5.001 drive in the Drives pane.

With the drive highlighted, locate and right-click the entry for the drive path for that drive for the master
server Device Host, lnxmaster.vrtsedu.lab, in the Paths (bottom) pane of the Device Monitor.

45. In the resulting menu, click Up Path.

46. Click the Refresh button on the NetBackup Administration Console tool bar (or select View and then
select Refresh), to update the contents of the Device Monitor UI.
47. Verify that the Control column for the IBM.ULT3580-TD5.001 drive in the Drives pane of the Device
Monitor now contains <Mixed>.
48. Verify that the Control column entry for the drive path for the lnxmaster.vrtsedu.lab Device Host in
the Paths pane contains SCAN-TLD.

Running a manual backup that writes to master server tape storage

In the following steps, you run a manual backup of a client using a policy that writes backup images to tape
storage controlled by the master server, and observe the results.

48. Run a full manual backup of the client, lnxmaster.vrtsedu.lab, using the PRE-clients-to-master-
tape policy.

The detailed steps to perform the manual backup are described in the following table.

Step
Step details
#

Select NetBackup Management > Policies in the left pane of the NetBackup Administration
1
Console.

2 Right-click the entry for PRE-clients-to-master-tape and select Activate.

3 Select Actions > Manual Backup.

The Manual Backup window is displayed.

4 Click the entry for the client, lnxmaster.vrtsedu.lab, in the Manual Backup window.
 Step
Step details
#

5 Click OK to initiate the backup operation.

49. Select the entry for the Activity Monitor in the left pane of the NetBackup Administration Console.
50. Locate the Backup job entry for the most recent backup job that used the PRE-clients-to-master-
tape policy.
51. Monitor the job, and verify that it runs to successful completion (status 0).

If the job fails, record the status code and seek assistance. Do not continue until you correct the issue causing
the failure, and can run the backup job successfully.

Running a manual backup that writes to media server tape storage

In the following steps, you run a manual backup of a client using a policy that writes backup images to tape
storage controlled by the media server, and observe the results.

52. Run a full manual backup of the client, lnxmaster.vrtsedu.lab, using the Appendix-B-clients-to-media-
tape policy.

If necessary, refer to the detailed steps described in table in the Running a manual backup that writes to
master server tape storage section in this exercise, to perform the manual backup. This time, however, use
the Appendix-B-clients-to-media-tape policy to perform the backup.

53. Access the Activity Monitor to monitor the progress of the backup job.
54. Take note of the following information about job.

The backup job fails with a Status code of 2009. The State of the job (when viewing the Activity
Monitor State column) is "Waiting for Retry".

Changing the status of a drive path using the Device Monitor

In the following steps, you use the Device Monitor to change the status of a tape drive path.

55. Select Media and Device Management and then select Device Monitor in the left pane of the
NetBackup Administration Console.
56. Select the entry for the first (top) drive, IBM-ULT358-TD5.000, in the Drives (top) pane of the Device
Monitor.
57. In the Paths (bottom) pane of the Device Monitor, right-click the drive path entry for the IBM-ULT3580-
TD5.000 drive associated with the Device Host, lnxmedia.vrtsedu.lab.
58. In the resulting menu, click Up Path.
59. Select the entry for the second (bottom) drive, IBM-ULT358-TD1.001, in the Drives (top) pane of
the Device Monitor.
60. In the Paths (bottom) pane of the Device Monitor, right-click the drive path entry for the IBM-ULT3580-
TD5.001 drive associated with the Device Host, lnxmedia.vrtsedu.lab
61. In the resulting menu, click Up Path.
62. Click the Refresh button on the NetBackup Administration Console tool bar to update the contents of
the Device Monitor user interface.

It may take a few moments for the update of the Device Monitor panes to complete. In some cases, it may
be necessary to refresh the Device Monitor more than one time.

63. Select the entry for each tape drive in the Drives pane, one-at-a-time, and verify that the contents of
the Control column of the Device and Paths panes has changed.

In the Drives pane, the Control column should contain TLD for both tape drive entries.
In the Paths pane, the Control column for the drive path associated with the media
server, lnxmedia.vrtsedu.lab should contain TLD.

64. Select the entry for the Activity Monitor in the left pane of the NetBackup Administration Console.
65. Take note of the current status of the Backup job that used the Appendix-B-clients-to-media-
tape policy and read the following information.

Read the following section carefully.

There are a number of situations you may encounter in this scenario, depending upon how quickly you UP'ed
the drive after the initial backup job failed, and how quickly you accessed the Activity Monitor. Read the
description of the possible scenarios.
 o The Backup job may be in the "Waiting for Retry" state. If the Backup job is in the Waiting for
Retry state when the paths for the tape drives on the media server come UP, the job will
automatically be re-tried.

If the job is still Waiting for Retry, continue to wait until the job starts, then view the entry for the
job in the Activity Monitor. (If you grow impatient waiting for the job to automatically restart, you can
manually restart it, by right-clicking the entry for the job and, in the resulting menu, click the Restart
Job entry.)

o The Backup job may be in the Active or Done states. This indicates that the Backup job was in
the Waiting for Retry state when the drives came up, and NetBackup's automatic retry restarted the
job.

If the job has already been started, (is Active) or has been completed (is Done) view the entry for the
job in the Activity Monitor. Depending upon how quickly you accessed the Activity Monitor the job
may have already run to completion.

o The Backup job may be in the Failed state. This occurs if the tape drives did not come UP before the
NetBackup job retry timeout expired (see Note).

If the job has a Failed status, manually restart the job. To do so, right click the entry for the job and
in the resulting menu, click Restart Job. Then view the entry for the job.

The original Backup job that used the Appendix-B-clients-to-media-tape policy failed with a status 2009. By
default, NetBackup performs two attempts every 12 hours, waiting 10 minutes between failed attempts. The
first automatic retry occurs within ten (10) minutes of the time that the initial job failed.

66. In the Activity Monitor, view the most recent entry for the Backup job that used the Appendix-B-
clients-to-media-tape policy and verify that the job runs to successful completion.
o If the job runs successfully, continue to Exercise H: Managing Media.
o If the job fails, record the status code and attempt to resolve the issue. Re-run the backup job and
monitor the results. Do not continue until you correct the issue causing the failure, and can run the
backup job successfully. If the backup continues to fail, seek assistance.
Exercise H: Managing Media

In this exercise, you monitor and manage media using NetBackup user interfaces.

1. Copy the Appendix-B-clients-to-media-tape policy to create a new policy named Appendix-B-small-

clients-to-media-tape using the detailed steps are provided in the following table.

Step
Step details
#

1 Select NetBackup Management > Policies in the left pane of the NetBackup Administration Console.

In the All Policies pane, right-click the entry for the policy that you want to make a copy of, in this
2
case, Appendix-B-clients-to-media-tape.

3 Select Copy to New in the resulting menu.

In the Copy a Policy dialog box, type the name of the new policy Appendix-B-small-clients-to-
media-tape in the New policy field.

4 Click OK in the Copy a Policy dialog box.

5 The new policy is displayed for editing in the Change Policy window.

2. Edit the Appendix-B-small-clients-to-media-tape policy, and make (only) the changes identified in the
following table that follows.

Attributes tab Attribute Settings:

Policy volume pool server_tapes (change to this setting)

All other Attribute settings: no changes

Schedules tab: no changes

 Clients tab no changes

Backup Selections tab: /data/smallfiles (change entry to this)

3. After making the changes to the Appendix-B-small-clients-to-media-tape policy, click OK to save the
policy and to close the Change Policy window.

Observing media availability impact on backup jobs

In the following steps, you use the policy created in the previous steps to run several manual backup jobs, and
create a scenario in which you observe NetBackup behavior when backup media is not available.

4. Access the NetBackup Administration Console that is open on the console.vrtsedu.lab system.
5. Use the Appendix-B-small-clients-to-media-tape policy to perform a manual, full backup of the
client, lnxmaster.vrtsedu.lab.

The detailed steps are described in the following table.

Step
Step details
#

1 Select NetBackup Management > Policies in the left pane of the NetBackup Administration Console.

Click the entry for the Appendix-B-small-clients-to-media-tape policy. The policy entry is located in
2
the All Policies pane of the NetBackup Administration Console.

3 Select Actions > Manual Backup.

The Manual Backup window is displayed.

Click the entry for the lnxmaster.vrtsedu.lab client to be backed up, located in the Manual
4
Backup window.

5 Click OK to initiate the backup operation.

6. Select the Activity Monitor entry in the left pane of the NetBackup Administration Console window.
7. Locate the entry for the most recent Backup job that used the Appendix-B-small-clients-to-media-
tape policy, and monitor the progress of the job.
8. Verify that the Backup job runs to successful completion. If the job fails, record the status of the job and
seek assistance.
9. Select the Media and Device Management and then select Media entry in the left pane of the
NetBackup Administration Console.
10. Click the Refresh button (or select View and then Refresh) to update the contents of the right pane of
the NetBackup Administration Console.
11. Observe that there is one tape in the server_tapes volume pool. This is the tape to which the most recent
backup image was written.

Running a backup job when no media is available

In the following steps, you create a scenario in which there are no tapes available in the server_tapes volume pool
that is specified for use in the policy.

12. Move all tapes that are currently in the server_tapes volume pool out of the robot (but do not eject the
tapes).

The detailed steps are described in the following table.

Step
Step details
#

Select Media and Device Management > Media > Volume Pools > server_tapes in the left pane of
1
the NetBackup Administration Console.

2 Click the Refresh icon in the NetBackup Administration Console window.

All tapes (Media IDs) that reside in the server_tapes volume pool are listed in the right pane of the
NetBackup Administration Console.

Select the entry (or entries) for all tapes in the server_tapes pool, as listed in the right pane. Click
3 the entry for the first (top) Media ID, hold the SHIFT key, and click the entry for the last (bottom)
Media ID.

4 Select Actions > Move.

The Move Volumes window is displayed.

 Step
Step details
#

- If the Volume is in a robotic library check box is marked, uncheck it.

5 - If the Volume is in a robotic library check box IS NOT checked, click the check box, and then
immediately click it again, to unmark the check box.

6 Verify that the Volume is in a robotic library check box is not marked.

7 Click OK to initiate the move operation.

13. Select Media and Device Management and then select Media in the left pane of the NetBackup
Administration Console.
14. Click the Refresh button (or select View and then Refresh) to update the contents of the right pane of
the NetBackup Administration Console.
15. Verify that all tapes that are members of the server_tapes volume pool no longer are associated with
a Robot Number or Slot, and have the NONE entry in the Robot Type column.

These tapes are considered "non-robotic" at this time, but have not been ejected from the tape library.

16. Move all tapes that are currently members of the scratch_tapes volume pool out of the robot (but do not
eject the tapes).

The detailed steps are described in the following table.

Step
Step details
#

Select Media and Device Management > Media > Volume Pools > scratch_tapes in the left pane of
1
the NetBackup Administration Console.

All tapes (Media IDs) that reside in the scratch_tapes volume pool are listed in the right pane of the
NetBackup Administration Console.

Select the entry (or entries) for all tapes in the scratch_tapes pool, as listed in the right pane. To
2 accomplish this, click the entry for the first (top) Media ID in the scratch_tapes pool, hold
the SHIFT key, and click the entry for the last (bottom) Media ID in the scratch_tapes pool.
 Step
Step details
#

3 Select Actions > Move.

The Move Volumes window is displayed.

- If the Volume is in a robotic library check box is marked, uncheck it.

4 - If the Volume is in a robotic library check box IS NOT checked, click the check box, and then
immediately click it again, to unmark the check box.

5 Verify that the Volume is in a robotic library check box is not marked.

6 Click OK to initiate the move operation.

17. Select Media and Device Management and then select Media in the left pane of the NetBackup
Administration Console.
18. Click the Refresh button to update the contents of the right pane of the NetBackup Administration
Console.
19. Verify that all tapes that are members of the scratch_tapes volume pool no longer are associated with
a Robot Number or Slot, and have the NONE entry in the Robot Type column.

Running a manual backup using the Appendix-B-small-clients-to-media-tape policy

In the following steps, you run a backup and note the results when there are no tapes available for use by the
policy.

20. Use the Appendix-B-small-clients-to-media-tape policy to perform another manual, full backup of the
master server client.
21. After initiating the manual backup of the lnxmaster.vrtsedu.lab client, select the Activity Monitor entry
for the current job, and monitor the progress of the backup job.
22. Observe the results of the Backup job.
23. Double-click the entry for the job to view the Job Details for the job.
24. Your observations should include the following information.

The backup job failed with a status 96. The initial explanation provided in the Status pane of the Job
Overview says "(96) unable to allocate new media for backup, storage unit has none available". If you
cancelled the job while it was "Waiting for retry", then the failure status would be 150 (operation cancelled by
user).
 The Troubleshooter entry for status 96 says, "The NetBackup Resource Broker (nbrb) did not allocate a new
volume for backups. This error indicates that the storage unit has no more volumes available in the volume
pool that is specified for this backup. Note that NetBackup does not change storage units during the backup."

Further, the Troubleshoot tab of the Troubleshooter provides a substantial amount of information and ideas
on how to analyze this problem.

If you cancel the job while it was "Waiting for retry", then the failure status would be 150 (operation cancelled
by user).

25. Click the Troubleshooter button in the Detailed Status tab of the Job Details, and note the information
relating to the failure status code for the job.
26. Close the Troubleshooter window for the failed job, and then close the Job Details window.

The backup job failed because there is no media in the robotic library that meets the requirements for the job
(as specified in the policy). This simulates a scenario in which new tapes have been placed into the tape
library, but the inventory of the library (robot) has not been updated.

27. If the State of the failed job in the Activity Monitor contains Waiting for Retry, right-click the entry for
the job, and click Cancel Job in the resulting menu.

Click Yes if a confirmation window appears.

28. When the State of the failed job is displayed as Done, continue to the next step.

Resolving the problem by updating the robot inventory

In the steps that follow, you resolve the problem you encountered by updating the inventory of the robotic tape
library.

29. Update the inventory of the tape library by performing a Robot Inventory.

The detailed steps are described in the following table.

Step
Step details
#

Select Media and Device Management > Media in the left pane of the NetBackup Administration
1
Console.

Right-click the Media entry in the left pane of the NetBackup Administration Console, and
2
click Inventory Robot in the resulting menu.
 Step
Step details
#

The Robot Inventory window is displayed.

3 Verify that the Device host field is set to the host name of your master server.

Verify that the Robot field is set to the name of your robot (in this case, TLD(0)-
4
lnxmaster.vrtsedu.lab.

5 Click to mark the Update Volume Configuration radio button.

6 Verify that the Update Volume Configuration radio button is marked.

7 Click the Start button to update the volume configuration of the tape library.

View the Results pane of the Robot Inventory window to verify that the volume configuration was
8
updated.

9 Click Close to close the Robot Inventory window.

30. Select Media and Device Management and then select Media in the left pane of the NetBackup
Administration Console.
31. Click the Refresh button (or select View and then Refresh) to update the contents of the right pane of
the NetBackup Administration Console.
32. Verify that all tapes that are members of the server_tapes and scratch_tapes volume pools have an
associated Slot number in the robot.
33. Verify that the Robot Type column for the tapes contains TLD.

NOTE: It is important to use the Update Volume Configuration task of the Robot Inventory to
automatically update NetBackup's media database entries, so that the tapes in the tape library are correctly
associated with the correct tape slots in the library. Attempting to manually update the volume configuration
is not advised.
Re-running the failed backup job

In this exercise, you verify that the inventory of the robotic tape library you performed in the previous exercise
resolves the media problem.

34. Select the Activity Monitor entry in the left pane of the NetBackup Administration Console.
35. Locate and right-click the entry for the Job ID for the most recent failed that used the Appendix-B-small-
clients-to-media-tape policy.
36. In the resulting menu, click Restart Job.

The failed Job ID is not actually re-started. A new Backup job is initiated, that has a new Job ID.

37. Monitor the new Backup job, and verify that the job runs to successful completion.
38. If the job fails, record the status code and seek assistance. Do not continue until the problem is resolved,
and the backup job runs to successful completion.

Modifying the column layout of the Volumes pane

In the steps that follow, you will perform the steps necessary to re-arrange the order of the tape volume
information displayed for tape media.

39. In the left pane of the NetBackup Administration Console, select Media and Device Management, and
then select Media.

The Volumes (right) pane of the NetBackup Administration Console displays entries for all the volumes
(tapes) that are included in the NetBackup media catalog -- including tapes that are currently in a tape library
and tapes that are not in a tape library.

40. Click the entry for a tape volume in the right pane of the NetBackup Administration Console.
41. Select View and then select Columns, Layout.

You may also right-click a tape volume entry, and select Columns > Layout from the menu that is presented).

The Column Layout window is displayed, that enables you to re-arrange the order in which the columns of
the Volumes pane are displayed.

42. Re-arrange the order in which the first ten columns are displayed to match the order provided in the
following table.

Arrange columns 11 and following in any order you prefer. Detailed steps to arrange the column order are
described in the following table.
 Column heading Order listed

Media ID 1st

Barcode 2nd

Volume Pool 3rd

Time Assigned 4th

Media Status 5th

Media Owner 6th

Robot Number 7th

Slot 7th

Media Type 8th

Images 9th

Valid Images 10th

All remaining column headings in any order

The following table describes the steps to change the Volumes pane Column Layout.

Step
Step details
#

NOTE: In the Column Layout window, the columns are listed, from top-to-bottom, in the order they
will appear from left-to-right in the Volumes pane.
 Step
Step details
#

In the Column Layout window, click the entry for a Column that you wish to move to a new position
1
in the column list.

Click the Move Up or Move Down button as many times as necessary to move the column into the
2
desired position in the Column list.

Select the next Column entry you wish to move, and use the Move Up and Move Down buttons to
3
relocate the column heading in the Column list.

Repeat steps 1-3 until you have arranged the columns 1-10 in the order specified in the preceding
4
table.

5 Arrange the order of columns 11 and following in any order.

6 Click OK to save the Column Layout changes, and to close the Column Layout window.

43. View the Volumes pane and verify the following:

Verify that the first ten columns are displayed in the following order:

Media ID, Barcode, Volume Pool, Time Assigned, Media Status, Media Owner, Robot Number, Slot,
Media Type, Images, and Valid Images.

The remaining columns can be arranged in any order you prefer.

The order in which the columns of the Volumes pane are displayed is a matter of preference of the backup
administrator, and should be arranged according to the needs of the organization. The order presented in the
preceding steps is for example purposes only.

44. Select Media and Device Management and then select Media, Volume Pools and then server_tapes in
the left pane of the NetBackup Administration Console.
45. Click the Refresh button (or select View and then Refresh) to update the contents of the right pane of
the NetBackup Administration Console.
46. View the information displayed in the Volumes pane.

Take note of the information as identified in the following table using either paper and pencil or the Notepad
application (available on the desktop of the console host) for the server_tapes volume pool.
 Information for server_tapes volume pool Answers

Media ID or IDs of tapes in the server_tapes volume pool?

How many tapes in server_tapes pool with non-empty Time Assigned?

How many tapes in server_tapes pool with empty Time Assigned?

Running a backup job - #1

47. Initiate a manual full backup of the lnxmaster.vrtsedu.lab client using the Appendix-B-small-clients-to-
media-tape policy.
48. Select the Activity Monitor entry in the left pane of the NetBackup Administration Console.
49. Monitor the progress of the most recent Backup job that used the Appendix-B-small-clients-to-media-
tape policy.
50. Allow the backup job to run to completion, and verify that the job is completed successfully.

If the job fails, record the status code and seek assistance. Do not proceed until the problem is corrected, and
the backup job has run successfully.

Viewing the results in the volume pool - #1

51. Select Media and Device Management and then select Media, Volume Pools, and
select server_tapes in the left pane of the NetBackup Administration Console.

Media and Device Management > Media > Volume Pools > server_tapes

52. Click the Refresh button (or select View and then Refresh) to update the contents of the right pane of
the NetBackup Administration Console.
53. Note the information about the tapes in the server_tapes pool.

It is likely there has been no change to the number of tapes that are resident in the server_tapes volume
pool. The amount of data that is backed for a single client using the Appendix-B-small-clients-to-media-
tape policy is relatively small, so that it will take multiple backup images to fill the tape to capacity. However,
the Images and Valid Images column contents of the NetBackup Administration Console will reflect a
change in the tape's contents.
Suspending tapes - #1

In the steps that follow, you use the NetBackup Administration Console to suspend all tapes that are resident in
the server_tapes volume pool.

54. With the server_tapes entry selected in the left pane of the NetBackup Administration Console, select the
entries for all volumes (tapes) that are listed in the Volumes in Volume Pool (right) pane.

Media and Device Management > Media > Volume Pools > server_tapes

o Click the entry for the first (top) volume listed in the pane
o Hold the Ctrl key down on your keyboard, and…
o Click the entries for each additional volume listed in the pane.
55. With the entries for all volumes in the server_tapes pool highlighted, select Actions and then
select Suspend, as illustrated.

The Suspend window is displayed.

56. Verify that all volumes that are members of the server_tapes volume pool are listed in
the Suspend window, and click OK to suspend the tapes.
57. Click the Refresh button to update the contents of the right pane of the NetBackup Administration
Console.
58. Note the contents of the Media Status column for the volumes in the server_tapes volume pool.

All tapes in the server_tapes volume pool should have a Media Status of Suspended.

Running a backup job - #2

59. Initiate another manual full backup of the lnxmaster.vrtsedu.lab client (lnxmaster.vrtsedu.lab) using
the Appendix-B-small-clients-to-media-tape policy.
60. Select the Activity Monitor entry in the left pane of the NetBackup Administration Console.
61. Monitor the progress of the most recent Backup job that used the Appendix-B-small-clients-to-media-
tape policy.
62. Allow the backup job to run to completion, and verify that the job is completed successfully.

If the job fails, record the status code and notify your instructor. Do not proceed until the problem is
corrected, and the backup job has run successfully.

Viewing the results in the volume pool - #2

63. Select Media and Device Management and then select Media, Volume Pools and then server_tapes in
the left pane of the NetBackup Administration Console.
64. Click the Refresh button (or select View and then select Refresh) to update the contents of the right
pane of the NetBackup Administration Console.
65. Compare your observations regarding the changes in the server_tapes volume pool to those listed.
o As a result of the most recent backup job, another tape (volume) has been added to
the server_tapes volume pool.
o The new tape was used because the server_tapes had no tapes in it that were usable for the backup
(all tapes previously in the pool had been suspended).
o The tape that was added to the server_tapes pool was automatically re-assigned by NetBackup from
the scratch_tapes pool.

Another volume (tape) was assigned to the server_tapes volume pool as a result of the most recent backup
job.

Suspending tapes - #2

In the steps that follow, you suspend all Active tapes that are resident in the server_tapes volume pool.

66. Select Media and Device Management and then select Media, Volume Pools and
then server_tapes entry selected in the left pane of the NetBackup Administration Console.
67. Select the entries for all Active volumes (tapes) that are listed in the Volumes in Volume Pool (right)
pane.
o Click the entry for the first (top) Active volume listed in the pane
o Hold the Ctrl key on your keyboard, and…
o Click the entries for each additional Active volume listed in the pane.
68. With the entries for all Active volumes in the server_tapes pool highlighted, select Actions and then
select Suspend.

The Suspend window is displayed.

69. Verify that all Active volumes that are members of the server_tapes volume pool are listed in
the Suspend window, and click OK to suspend the tapes.
70. Click the Refresh button (or select View and then Refresh) to update the contents of the right pane of
the NetBackup Administration Console.
71. Verify that all volumes in the server_tapes volume pool have a Media State of Suspended.
72. Using a pencil and paper or the Notepad application (located on the desktop), record the information
requested for tapes in the server_tapes volume pool as shown in the following table.

Information for server_tapes volume pool Media ID Media Owner (media server that owns the volume)

First volume: Varies lnxmedia.vrtsedu.lab

Second volume: Varies lnxmedia.vrtsedu.lab

Third volume (if present): Varies lnxmedia.vrtsedu.lab

73. The Media Owner of the tapes that are members of the server_tapes volume pool is the media
server, lnxmedia.vrtsedu.lab. The Media Owner is the media server that has written all the backup images
to the tape. By default, NetBackup allows only one media server to write backup images to an assigned tape
volume.

Using the NetBackup Administration Console to unsuspend a volume

In the steps that follow, you use the NetBackup Administration Console to unsuspend the first volume listed in
the table shown above.

73. Select server_tapes from the volume pools in the left pane of the NetBackup Administration Console.
74. Click the Refresh button to update the contents of the right pane of the NetBackup Administration
Console.
75. Click the volume entry for the tape volume listed as the "first volume".
76. With the volume entry for the tape highlighted, select Actions and then select Unsuspend and
click Unsuspend in the resulting menu.

The Unsuspend window is displayed.

77. Take note of the Media ID of the first volume displayed in the Unsuspend window, and then click OK to
unsuspend the volume.
78. Click the Refresh button to update the contents of the right pane of the NetBackup Administration
Console.
79. Verify that the entry for the volume that is listed as the "first volume" has a Media State of Active in the
right pane of the NetBackup Administration Console.

Changing the volume pool of a tape

80. Select the Media and Device Management and then select the Media entry in the left pane of the
NetBackup Administration Console.
81. Click the Refresh button to update the contents of the right pane of the NetBackup Administration
Console.
82. Identify the Media ID of a tape (volume) that is currently resident in the scratch_tapes volume pool, and
right-click the entry for that volume.
83. In the resulting menu, click Change.
84. In the Change Volumes window, click the New Pool radio button.
85. In the drop-down menu for the Volume Pool, click the entry for the server_tapes volume pool.
86. Click OK to save the change, and to close the Change Volume window.
87. Click the Refresh button to update the contents of the right pane of the NetBackup Administration
Console.
88. Verify that the Media ID that you selected (in step 3) is now resident in the server_tapes volume pool.
89. Select server_tapes in the left pane of the NetBackup Administration Console.

Media and Device Management > Media > Volume Pools > server_tapes

90. Click the Refresh button and update the contents of the right pane of the NetBackup Administration
Console.
91. Verify that the Media ID that you "changed" is visible in the list of volumes that is displayed in the list of
tapes in the right pane of the NetBackup Administration Console.

The tape that you changed from the scratch_tapes pool to the server_tapes pool is not assigned. No entry
exists in the Time Assigned column for the tape.
It is not generally recommended to manually move tapes from a scratch pool into another pool. NetBackup
uses a scratch pool to automatically allocate tapes from the scratch pool to volume pools that are requested
for by a policy or SLP for backup, duplication, replication and other operations.
Attempting to move an assigned volume to another pool

92. Identify the Media ID of a volume in the server_tapes volume pool that has been assigned (there is an
entry in the Time Assigned column for the volume).
93. Right-click the entry for the Media ID identified in the previous step and, in the resulting menu,
click Change.
94. In the Change Volumes window, click the New Pool radio button.
95. In the drop-down menu for the Volume Pool, click the entry for the scratch_tapes volume pool.
96. Click OK to save the change, and to close the Change Volume window.
97. Note the results of the operation.

A Change Volume message is posted in the Messages pane, located at the bottom of the right pane of the
NetBackup Administration Console. The Change Volumes message says, "Change pool of [media ID] failed
(91). Cannot change media pool of an assigned media".

98. Close the Change Volumes message window.

Exercise I: Using the Robtest Utility

In this exercise, you use the NetBackup-provided robtest (robot test) utility to test the operation of a robotic tape
library.

Running robtest from a non-Robot Control Host system

In the steps that follow, you run the robtest utility from a NetBackup server that is not the robot control host and
observe the results.

NOTE: In this lab environment, your master server (lnxmaster.vrtsedu.lab) is acting as the Robot Control
Host for the robotic control of the tape library.

1. Access the desktop of the console system.

2. Locate and launch the Putty shortcut.
3. In Putty configuration window, double-click the entry for lnxmedia.vrtsedu.lab.
4. Login using the following credentials.
o computer: lnxmedia.vrtsedu.lab
o Username: root
o Password: P@ssw0rd

5. Using putty window, access the command line on the Linux media server, lnxmedia.vrtsedu.lab.
6. Enter the following command, and press Enter.
 Command: /usr/openv/volmgr/bin/scan -changer

7. Note that the output of the scan -changer command shows that the media server can "see" the robotic
control, as illustrated.

8. Execute the tpconfig command, as illustrated, to verify that the robot is configured for use by the media
server, but that the media server is not the Robot Control Host.

Command: /usr/openv/volmgr/bin/tpconfig -d

9. Note the output of the tpconfig -d command.

10. Type the robtest command (illustrated), and press Enter.

Command: /usr/openv/volmgr/bin/robtest

11. Note the output of the robtest command as illustrated.

The message "No locally-controlled robots with test utilities are configured" is displayed.

As you can see from the output of the robtest command, the media server is not the Robot Control Host for
the robot. For this reason, robtest cannot be used on this media server to test the robot operation.

CONCLUSION: The **robtest command should be executed on the media server that is configured to serve
as the Robot Control host for the robot.

12. Close the putty window to return to the desktop of the console.vrtsedu.lab system.

Identifying a tape to use during robtest operations

In the steps that follow, you prepare to use robtest by using the NetBackup Administration Console to identify the
Media ID of a tape that is ASSIGNED in NetBackup.

10. Access the open NetBackup Administration Console window on the console.vrtsedu.lab system.
11. Select Media and Device Management and then select Media in the left pane of the NetBackup
Administration Console.

The list of Media IDs that are known to NetBackup (for which entries exist in the NetBackup database) is
displayed in the right pane of the NetBackup Administration Console.
12. Click the Refresh button (or select View and then select Refresh) to update the contents of the right
pane of the NetBackup Administration Console.
13. Locate the entry for a Media ID for which the Time Assigned column contains a date and time stamp (a
tape that is ASSIGNED in NetBackup), as illustrated.

14. Record information for an assigned tape using paper and pencil or the NotePad application located on
the desktop of the system.

Record the Media ID, Barcode, Volume Pool, Time Assigned, Media Status, and Slot information for the
tape, along with any other information you feel is important.

A tape that is assigned contains one or more active NetBackup backup images.
You can optionally create a Filter to filter the list of Media IDs that are displayed in the NetBackup
Administration Console. Filters can be created that use a wide variety of filter criteria. To begin creating a
filter, click the entry for any Media ID (in the right column of the NetBackup Administration Console), and
then select View > Filter. You use the resulting Filter window to create, modify, or delete a filter.

Viewing the status of the tape drives

In the steps that follow, you use the NetBackup Administration Console to view the status of the tape drives that
are configured for use by NetBackup.

15. Select the Media and Device Management and then select Device Monitor entry in the left pane of the
NetBackup Administration Console.

The Device Monitor is displayed in the right pane of the NetBackup Administration Console.
16. Click the Refresh button (or select View and then Refresh) to update the contents of the right pane of
the NetBackup Administration Console.
17. View the contents of the Drives (top) pane of the Device Monitor.

Take note of the Recorded Media ID, External Media ID, Ready, and Write Enabled columns of the tape
drives, as illustrated in the following figure.

18. Allow the NetBackup Administration Console window to remain open on console.vrtsedu.lab.

Running robtest on the Robot Control Host

In the steps that follow, you run robtest on the system that is the configured Robot Control Host, and observe
the use and behavior of this NetBackup-provided utility.

19. Access your master server system, lnxmaster.vrtsedu.lab using the steps listed.

a. Double-click the PuTTY shortcut located on the desktop of the console.vrtsedu.lab system to
launch PuTTY.

Within a moment the PuTTY Configuration window is displayed.

b. Locate and double-click the pre-configured entry for the Linux master server, lnxmaster.vrtsedu.lab.

Within a moment a PuTTY window is displayed that will enable you to log in to lnxmaster.vrtsedu.lab.

c. Log on to the master server using the following credentials.

 computer: lnxmaster.vrtsedu.lab
 Username: root
 Password: P@ssw0rd

20. In the PuTTY window, type the command illustrated, and press Enter.

Command: /usr/openv/volmgr/bin/robtest

NetBackup-provided commands reside in sub-directories under the installation directory on the NetBackup
system. For purposes of this course, the PATH environment variable has been set to include the directories
 in which commonly-used NetBackup commands are located, to avoid the need to navigate to the directory
where the command is located.

21. A simple Robot Selection menu is displayed.

22. Type 1, and press Enter.

If the host you run robtest on is the Robot Control Host for more than one robotic library, then
the robtest menu will show an entry for each robot the host controls. You choose the robot to test by
selecting the numeric value associated with the robot from the menu.
From this point on, robtest does not display a command prompt symbol. If you are unsure of the choices
available, type ? to obtain help.

Type ?, and press the Enter key.

23. Take note of the output of the robtest help (?) command.

Performing robtest operations

In the steps that follow, you use robtest commands to verify the operation of the robot.

24. Type the following robtest command, and press Enter, to show the contents of the tape slots in the
robotic library.

Robtest command: s s (Enter) Usage = show slots

The output of the show slots operation is illustrated.

 The show slots operation pauses after displaying a small number of tape library slots. You must
press return (Enter) to continue displaying slots.

25. Press return (Enter) to continue to the end of the tape slot listing. Depending upon the number of slots in
the library, you may have to press Enter multiple times.

When you see the "READ_ELEMENT_STATUS complete" message, you have reached the end of the slot
listing, as illustrated next.

The following figure illustrates the "READ_ELEMENT_STATUS complete" message.

26. Read the following note and type the following robtest command, and press Enter.

In a previous lab step (Exercise E-2, step 6) you recorded the information for a tape that has been assigned
for use by NetBackup. Use the location information for that tape as input for the next command.

Robtest command: s s # (Enter) Usage = show slot [slot number]

The following figure illustrates an example of the "show slot [slot number]" output.

27. Compare the barcode of the tape listed with the barcode of the tape in the "show slot [slot number]"
command output (s s #). The barcodes should be the same.
28. Type the following robtest command, and press Enter, to show the contents of the tape drives in the tape
library.

Robtest command: s d (Enter)

(Usage = show drives)

The following figure illustrates an example of the show drives (s d) output.

 The output of the previous "show drives" command shows that there are currently no tapes in the tape drives
of the library.

29. Type the following robtest command, and press Enter, to move the tape from the tape slot into tape
drive 1 in the tape library.

Robtest command: m s# d1 (Enter)

Usage = move tape from slot(#) to drive(#)

The following figure illustrates an example of the move command (m s2 d1) output.

30. Type the following robtest command, and press Enter, to show the contents of a single tape slot in the
tape library (the slot from which you moved the tape in the previous step).

Robtest command: s s # (Enter)

Usage = show contents of specific slot

Note the results of the previous command. The tape slot that you moved the tape from should be empty
(contains cartridge = no).

31. Type the following robtest command, and press Enter, to show the contents of the tape drives in the tape
library.

Robtest command: s d (Enter)

Usage = show contents of the tape drives

Note the results of the command. The command output should show that drive 1 contains a tape with the
barcode matching the barcode of the tape you recorded.

32. Type q, and press Enter (to quit robtest).

The Robot Selection menu is displayed.

33. Type 2 (none/quit), and press Enter (to close robtest).

The robtest utility session is ended, and you are returned to the command prompt.
 34. Leave the Putty window open.

Viewing the Media ID (that was moved in robtest) in the Device Monitor

In the steps that follow, you use the NetBackup Device Monitor to view the media ID that was moved (in the
previous exercise, using robtest).

33. Access the open NetBackup Administration Console window on the console.vrtsedu.lab system.
34. Select Media and Device Management and then select Device Monitor in the left pane of the
NetBackup Administration Console.

Media and Device Management > Device Monitor

The Device Monitor is displayed in the right pane of the NetBackup Administration Console.

35. Click the Refresh button (or select View and then select Refresh) to update the contents of the right
pane of the NetBackup Administration Console.
36. View the Drives (top) pane of the Device Monitor and note that one of the drives contains an entry in
the Recorded Media ID column, as illustrated.

The tape that you moved into the tape drive using robtest is shown as loaded in the tape drive in the Device
Monitor GUI. The Drive Name that is associated with d1 (in robtest) may vary, you can ignore it.

37. Allow the NetBackup Administration Console window to remain open on console.vrtsedu.lab. You return
to this window later in this lab activity.

Returning to robtest

In the steps that follow, you use robtest to move the media ID back to its original slot in the tape library.

38. Access the master server, lnxmaster.vrtsedu.lab.

39. Access the open Terminal window on the master server.
40. In the Terminal window, type the command illustrated, and press Enter.

Command: /usr/openv/volmgr/bin/robtest

41. In the Robot Selection menu that is displayed, type 1, and press Enter.
42. Type the following robtest command, and press Enter, to move the tape from drive 1 back into the
original tape slot in the tape library.

Robtest command: m d1 s# (Enter)

Usage = move tape from drive(#) to slot(#)

43. Use the "show slot [slot number]" (s s #) and "show drive" (s d) commands to verify that the tape drive has
been returned to its original tape slot.
44. Type q, and press Enter (to quit robtest).

The Robot Selection menu is displayed.

45. Type 2 (none/quit), and press Enter (to close robtest).

The robtest utility session is ended, and you are returned to the command prompt.

46. Leave the Terminal window open.

Viewing the Media ID (that was moved in robtest) in the Device Monitor

In the steps that follow, you use the NetBackup Device Monitor to view the media ID that was moved back to its
original slot in the tape library (in the previous exercise, using robtest).

43. Access the open NetBackup Administration Console window on the console.vrtsedu.lab system.
44. Select Media and Device Management and then select Device Monitor in the left pane of the
NetBackup Administration Console.

The Device Monitor is displayed in the right pane of the NetBackup Administration Console.

45. Click the Refresh button (or select View and then select Refresh) to update the contents of the right
pane of the NetBackup Administration Console.
46. View the Drives (top) pane of the Device Monitor.

It may take a few moments for NetBackup to display that the tape drive no longer contains a tape, as
evidenced by the fact that the Recorded Media ID column is now blank for both tape drives.

Exiting robtest

In the steps that follow, you observe why it is imperative that you exit the robtest utility when you have completed
your testing of robotic operations.

47. Access the master server, lnxmaster.vrtsedu.lab.

48. Access the open Terminal window on the master server.
49. In the Terminal window, type the command illustrated, and press Enter.
 Command: /usr/openv/volmgr/bin/robtest

50. In the Robot Selection menu that is displayed, type 1, and press Enter.
51. Minimize the Terminal window.
52. Access the open NetBackup Administration Console window on console.vrtsedu.lab.
53. Select Media and Device Management and then select Media in the left pane of the NetBackup
Administration Console.
54. Right-click the Media entry in the left pane of the NetBackup Administration Console and, in the resulting
menu click Inventory Robot.

The Robot Inventory window is displayed.

55. Verify that the Show Contents radio button is selected, and then click the Start button.

Your observations should be similar to those listed.

The "Show Contents" operation in Robot Inventory hangs. No results are generated.

This occurs because when robtest is running (with a robot selected in robtest) robtest hangs on to the robotic
control interface and all other requests to use the robotic control are blocked. You must exit robtest to
prevent regular NetBackup requests to the robot from being blocked.

56. Allow the Robot Inventory (that is hung while attempting to perform a Show Contents operation) to
remain open in the NetBackup Administration Console window.
57. Access the master server system (lnxmaster.vrtsedu.lab).
58. Access the open PuTTY (Linux) window on the master server.

robtest should still be running in the Terminal window.

59. Type q, and press Enter (to quit robtest).

The Robot Selection menu is displayed.

60. Type 2 (none/quit), and press Enter (to close robtest).

The robtest utility session is ended, and you are returned to the command prompt.

61. Type exit, and press Enter to close the Terminal window.

Verifying the results in the Robot Inventory window

In a previous step you initiated a Robot Inventory operation from the NetBackup Administration
Console on console.vrtsedu.lab. That Robot Inventory operation was hung up, because the robtest utility was
running on the Robot Control Host (the master server).
In the steps that follow, you verify that a robot inventory can be performed after the robtest utility has been
terminated.

57. Access the open NetBackup Administration Console window on console.vrtsedu.lab.

The Robot Inventory window, that was displayed previously, should still be open.

58. View the contents of the Results pane in the Robot Inventory window.

The contents of the robot (Slot numbers with Barcodes of tapes occupying the slots) should be displayed in
the Results pane.

CONCLUSION: When robtest was running, it blocked other attempts to access the robotic control of the tape
library, including requests from NetBackup. When robtest was exited, other pending requests to the robotic
control were allowed to proceed, including the request from NetBackup to show the contents of the tape
slots.

It is imperative that, when testing of a tape library's robotic control with robtest is completed, that robtest be
exited promptly, to prevent unnecessary delays of NetBackup requests to the use the robotic control.

59. Click Close in the Robot Inventory window on console.vrtsedu.lab, to close the window without
proceeding further with the inventory operation.

Exercise J: Running NetBackup Reports from the Command Line

NetBackup enables the running of its reports from the command line. In the steps that follow, you run a few of
those reports and view the results.

Using the vmquery command

In this exercise, you use the NetBackup vmquery command and acquire a list all tapes that are listed in the
NetBackup media database on the master server.

1. Access your master server system, lnxmaster.vrtsedu.lab using the steps listed.

a. Double-click the PuTTY shortcut located on the desktop of the console.vrtsedu.lab system to
launch PuTTY.

Within a moment the PuTTY Configuration window is displayed.

b. Locate and double-click the pre-configured entry for the Linux master server, lnxmaster.vrtsedu.lab.
 Within a moment a PuTTY window is displayed that will enable you to log in to lnxmaster.vrtsedu.lab.

c. Log on to the master server using the following credentials.

 computer: lnxmaster.vrtsedu.lab
 Username: root
 Password: P@ssw0rd

2. In a PuTTY window, type the command illustrated, and press Enter.

Command: /usr/openv/volmgr/bin/vmquery -a -b

3. Note the results of the command as shown in the following example.

The form of the vmquery command used here displays all the tape volumes that are known to NetBackup
(are listed in the NetBackup media database on the master server). Compare the former output to the output
of the vmquery -a command.

Using the bpmedialist command

In this exercise, you use the NetBackup bpmedialist command to acquire a list of all tapes assigned to the master
server.

4. Use the bpmedialist command to list all the tapes that assigned to the master server. To do so, type the
command illustrated, and press Enter.

Command: bpmedialist -h lnxmaster.vrtsedu.lab

 Note the results of the command.

5. To list all the tapes that assigned to the media server, type the command illustrated, and press Enter.

Command: bpmedialist -h lnxmedia.vrtsedu.lab

6. Note the results of the command.

To list the tapes that are assigned to NetBackup on any media server in the NetBackup domain of the master
server use the bpmedialist command with no command options or arguments.

Running the Tape Summary report from the command line

In this exercise, you use the NetBackup bpmedialist command to run a tape summary report.

7. To run the command line version of the Tape Summary report, type the command illustrated, and
press Enter.

Command: bpmedialist -summary

8. Note the output of the command.

Running the available_media report

In this exercise, you use the NetBackup available_media command.

The available_media command provides a listing of tape volumes assigned to NetBackup, organized by the
volume pools the tapes in which the tapes reside.

9. Type the command illustrated, and press Enter.

Command: available_media

Note the results of the command.

10. Close the Terminal window on your master server.

Exercise K: Media State Management Using the Command Line

In this exercise, you perform media state management tasks using NetBackup-provided command line interfaces
(CLIs).
Using the bpmedialist command

In the steps that follow, you execute the bpmedialist command and examine the command output.

1. In the PuTTY window, type the command illustrated, and press Enter.

Command: bpmedialist

The output of the bpmedialist command shows the volumes (tapes) that are Assigned to NetBackup, and
includes important information about each of the tape volumes.

2. Examine the output of the bpmedialist command, and note the following information.
o The output of bpmedialist indicates the Tape Owner for each tape.
o The output of bpmedialist lists all the tapes owned by one media server first (under the heading of
"Server Host"), and then lists the tapes owned by the next media server (Server Host). In this case, we
have two media servers, so the tapes associated with the media server are listed first, followed by the
list of tapes owned by the master server.
o The output of bpmedialist indicates the Media State (Active, Full, Frozen, Suspended) of the media
listed.
o Tapes that are Active are simply listed, but those that are FULL, SUSPENDED, or FROZEN are
specifically indicated as such in the STATUS column of the command output.
3. Record the Media ID and Media Owner of one tape that is SUSPENDED using a pencil and paper or by
using the Notepad application located on the desktop.
o The Media ID may vary.
o The Media Owner should be lnxmedia.vrtsedu.lab. (the media server).

Using the bpmedia command

In the steps that follow, you execute the bpmedia command and examine the command output.

4. In the PuTTY window, type the command illustrated, and press Enter.

The command illustrated is used to UNSUSPEND the Media ID you identified in the previous lab exercise.

Command: bpmedia -unsuspend -m [media ID]

Example: bpmedia -unsuspend -m E01002

Note the results of the command.

The response, "requested media id is not assigned to this host in the EMM database" is received in
response to the command.
When using the bpmedia command to change the Media State of a tape, one of two conditions must be
met: 1) You must execute the command on the media server that is the Media Owner of the Media ID that is
affected by the command, or 2) If you are running the command on a NetBackup server that is not the Media
 Owner, [you must]{.underline} specify the Media Owner host name in the syntax of the command. This is
accomplished using the -h [*Media Owner*] command option.

5. Type the command illustrated, and press Enter to UNSUSPEND the Media ID you recorded in Answer A3
previously.

Command: bpmedia -unsuspend -m [media ID] -h lnxmedia.vrtsedu.lab

Example: bpmedia -unsuspend -m E01002 -h lnxmedia.vrtsedu.lab

Note the results of the command.

This time the bpmedia command should exit without any response. There is no indication of the success or
failure of the command.

6. Verify the results of the bpmedia command to unsuspend the tape, by typing the command illustrated,
and pressing Enter.

Command: bpmedialist

7. Verify that the Media ID that you "unsuspended" is no longer listed as SUSPENDED in the output of
the bpmedialist command.

The bpmedia command can be used to suspend/unsuspend and freeze/unfreeze tapes that are assigned in
NetBackup. Un-assigned tapes cannot be manipulated using the bpmedia command.

8. Repeat the bpmedia -unsuspend command to unsuspend any other suspended tapes shown in
the bpmedialist command output.

Verifying the results of the unsuspend using the NetBackup Administration Console

In the steps that follow, you use the NetBackup Administration Console to examine the results obtained by
executing the bpmedia command (in the previous exercise) to unsuspend a tape.

9. Access the desktop of the console.vrtsedu.lab system.

10. Access the open NetBackup Administration Console window on console.vrtsedu.lab.
11. Select the Media and Device Management and then select Media entry in the left pane of the
NetBackup Administration Console.
12. Click the Refresh button (or select View and then Refresh) to update the contents of the right pane of
the NetBackup Administration Console
13. Verify that the Media ID that was previously in the Suspended Media State is now shown as Active in
the right pane of the NetBackup Administration Console.
Attempting to suspend unassigned media

In the steps that follow, you attempt to use the NetBackup Administration Console to suspend a tape that is in the
unassigned state, and note the results.

14. Select Media and Device Management and then select Media entry highlighted in the left pane of the
NetBackup Administration Console.

Media and Device Management > Media

Identify a volume in the right pane that is currently not assigned. (The Media ID has no entry in the Time
Assigned column.)

15. In the right pane of the NetBackup Administration Console, right-click the entry for the (unassigned)
Media ID and, in the resulting menu, click Suspend.
16. Click OK in the Suspend dialog box, and note the results of this attempt to suspend the tape.

A notification is posted in the Message pane that appears at the bottom of the right pane of the NetBackup
Administration Console. The message says, "requested media id is not assigned to this host in the EMM
database (95). Media is not assigned."

17. Click the small X icon in the upper right corner of the Suspend message dialog to close it.