Nbu81 Admin Lab Book PDF

Veritas NetBackup 8.
1:
Administration –
Lab Book
Not for Distribution

Veritas NetBackup 8.1: Administration
THIS PUBLICATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE
EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC
SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE
FURNISHING, PERFORMANCE, OR USE OF THIS PUBLICATION. THE INFORMATION CONTAINED HEREIN
IS SUBJECT TO CHANGE WITHOUT NOTICE.
No part of the contents of this book may be reproduced or transmitted in any form or by any means
without the written permission of the publisher.
Course Developer Technical Contributors and Reviewers
Bill Drazkowski Chris Amidei

Cheryl Faulkner Jose Ignacio Colodras
Sarah Fort-Kramer Graeme Gofton
Joe Gallagher Swati Joshi
John Gerhardson Stefano Lollio
Tomer Gurantz Robert Owen
Paul Ransted
Sylvain Savary
Stephen Williams
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
For specific country offices Veritas World Headquarters © 2017 Veritas Technologies LLC. All
rights reserved. Veritas and the Veritas
and contact numbers, please 500 East Middlefield Road
Logo are trademarks or registered
visit our website at Mountain View, CA 94043 USA
trademarks of Veritas Technologies LLC
www.veritas.com. +1 (650) 933 1000 or its affiliates in the U.S. and other
www.veritas.com countries. Other names may be
trademarks of their respective owners.
ii
Table of Contents
Lab 1: Introduction to NetBackup

Exercise A: Identifying the lab delivery environment ..................................................................1-2
Exercise B: Introduction your Hatsize (VILT) lab kit .....................................................................1-3
Exercise C: Introduction to your VMware Workstation (ILT) lab kit ..........................................1-10
Exercise D: Introduction to your Nimbus/NextGen lab kit ........................................................1-17
Exercise E: Accessing remote lab systems .................................................................................1-28
Exercise F: Launching the NetBackup Administration Console .................................................1-33
Exercise G: Exploring the NetBackup Administration Console ..................................................1-37
Exercise H: Verifying NetBackup licenses ..................................................................................1-40
Exercise I: Identifying common Administration Console configuration items ..........................1-45
Exercise J: Initiating backup jobs using the NetBackup Administration Console ......................1-75
Exercise K: Viewing and monitoring backups jobs using the Activity Monitor ..........................1-78
Lesson 2: Configuring NetBackup storage

Exercise A: Viewing disk storage on a NetBackup server system ................................................2-2
Exercise B: Configuring a BasicDisk storage unit .........................................................................2-7
Exercise C: Configuring a storage unit group .............................................................................2-17
Lesson 3: Configuring Policies and Schedules

Exercise A: Configuring a NetBackup policy.................................................................................3-2
Exercise B: Configuring a policy to use calendar-based schedules ............................................3-17
Exercise C: Copying a policy to create a new policy ..................................................................3-24
Exercise D: (Optional) Lab Challenge .........................................................................................3-28
Lesson 4: Performing File System Backups

Exercise A: Using the Activity Monitor ........................................................................................4-2

Exercise B: Manual backups .......................................................................................................4-13
Exercise C: Viewing job details ...................................................................................................4-16
Exercise D: Deactivating and activating policies ........................................................................4-26
Exercise E: Performing user-initiated backups ..........................................................................4-29
Lesson 5: Performing File System Restores

Exercise A: Becoming familiar with key restore settings in the BAR user interface ....................5-2
Exercise B: Restoring client files to their original location ........................................................5-14
Exercise C: Restoring client files to an alternate file system location .......................................5-24
Exercise D: Restoring client files to an alternate client – Windows (only) ................................5-33
Exercise E: Restoring client files to an alternate client system – Linux (only) ...........................5-45
Exercise F: (Optional) Using the OpsCenter Operational Restore feature ................................5-59
Table of Contents iii
© 2017 Veritas Technologies LLC. All Rights Reserved

Lesson 6: Configuring Disk Pools
Exercise A: Identifying AdvancedDisk storage .............................................................................6-2
Exercise B: Configuring AdvancedDisk .........................................................................................6-7
Exercise C: Verifying AdvancedDisk configuration.....................................................................6-18
Exercise D: Configuring a policy to write backups to AdvancedDisk storage ............................6-35
Exercise E: Performing and monitoring backups to AdvancedDisk storage ..............................6-39
Exercise F: Monitoring and managing AdvancedDisk disk pools ...............................................6-42
Lesson 7: Configuring Media Server Deduplication

Exercise A: Configuring NetBackup Media Server Deduplication (MSDP) ...................................7-2
Exercise B: Configuring a policy to use MSDP storage ...............................................................7-21
Exercise C: Performing backups to MSDP storage .....................................................................7-28
Exercise D: Configuring and using client-side deduplication .....................................................7-35
Exercise E: Monitoring and managing NetBackup MSDP storage .............................................7-49
Exercise F: (Optional) Running Deduplication reports in OpsCenter.........................................7-59
Lesson 8: Configuring Tape Storage

Exercise A: Verifying tape devices are visible to the operating system of media servers ...........8-2
Exercise B: Viewing configured tape devices (using the NetBackup Administration Console) .8-27
Exercise C: Configuring tape devices using the Device Configuration wizard ...........................8-33
Exercise D: Configuring volume pools........................................................................................8-46
Exercise E: Configuring media using the Administration Console .............................................8-50
Lesson 9: Managing and Optimizing Tape Storage

Exercise A: Viewing tape drive and robot configuration settings ................................................9-2
Exercise B: Using the Device Monitor to monitor and manage tape drives ..............................9-11
Exercise C: Managing media ......................................................................................................9-32
Exercise D: Running tape-based reports ....................................................................................9-58
Exercise E: (Optional) Using the robtest utility ..........................................................................9-65
Exercise F: (Optional) Running NetBackup reports from the command line ............................9-85
Exercise G: (Optional) Media state management using the command line ..............................9-91
Lesson 10: Protecting Virtual Machines

Exercise A: Verifying the VMware environment ........................................................................10-2
Exercise B: Configuring NetBackup to perform VMware backups ............................................10-9
Exercise C: Installing the NetBackup Plug-in for VMware vSphere Web Client ......................10-16
Exercise D: Configuring a VMware policy ................................................................................10-29
Exercise E: Performing and monitoring VMware virtual machine backups ............................10-45
Exercise F: Excluding disks from a VMware virtual machine ...................................................10-49
iv Veritas NetBackup 8.1: Administration

Lesson 11: Recovering Virtual Machines
Exercise A: Recovering virtual machine files..............................................................................11-2
Exercise B: Recovering a VMware virtual machine disk ..........................................................11-14
Exercise C: Recovering an entire VMware virtual machine .....................................................11-24
Exercise D: Performing non-NetBackup pre-requisite tasks for IRV (Required, but pre-done)11-36
Exercise E: Performing NetBackup pre-requisite tasks for IRV ................................................11-38
Exercise F: Performing Instant Recovery for VMware (IRV) using the vSphere Web Client....11-57
Lesson 12: Duplicating Backups

Exercise A: Configuring a Storage Lifecycle Policy .....................................................................12-2
Exercise B: Configuring a policy to use an SLP ...........................................................................12-9
Exercise C: SLP Host Properties................................................................................................12-12
Exercise D: Viewing and monitoring SLP operations ...............................................................12-16
Lesson 13: Managing and Protecting the NetBackup Catalog

Exercise A: Running NetBackup reports ....................................................................................13-2
Exercise B: Verifying, expiring, and importing backup images ................................................13-16
Exercise C: Configuring and running NetBackup catalog backups ...........................................13-52
Exercise D: Recovering the catalogs using the NetBackup Catalog Recovery Wizard .............13-61
Lesson 14: Optimizing File System Backups

Exercise A: Optimizing backups using the NetBackup Accelerator ...........................................14-2
Exercise B: Configuring and using multiple data streams ........................................................14-15
Exercise C: (Optional) Configuring and performing multiplexed backups ...............................14-43
Lesson 15: Collecting Logs and Diagnostic Information

Exercise A: Viewing the NetBackup services .............................................................................15-2
Exercise B: Running NetBackup reports for troubleshooting ....................................................15-5
Exercise C: Using the nbsu and nbcplogs command ................................................................15-12
Exercise D: (Optional) Viewing and setting debug logging properties ....................................15-22
Exercise E: (Optional) Enabling NetBackup legacy debug logging ...........................................15-27

Exercise F: (Optional) Viewing debug logging levels for unified logs ......................................15-38
Table of Contents v

Lab 1: Introduction to NetBackup
In this lab, you perform tasks to become familiar with the NetBackup 8.1
Administration Console used in this lab environment. The slide lists the tasks that you
perform in this lab activity.
Continue to Exercise A: Identifying the lab delivery environment used for the class you
are attending .
Lab 1-1

Exercise A: Identifying the lab delivery environment
used for the class you are attending
The NetBackup 8.1: Administration course is delivered in several delivery

environments, each which uses a different environment to deliver the lab activities for
the course. The three primary course delivery types are:
• Instructor-Led Training (ILT)

̶ Lessons of the course are delivered in a classroom setting by a Veritas or Veritas
Partner’ instructor.
̶ Hands-on labs are delivered using one of three lab delivery platforms:
▪ VMware Workstation
▪ Nimbus/NextGen delivery platform
▪ Virtual Academy (Hatsize) online lab delivery platform
• Virtual Instructor-Led Training (VILT)
̶ Lessons of the course are delivered via a remote session (WebEx) by a Veritas or
Veritas Partner’ instructor.
̶ Hands-on labs are delivered using the Virtual Academy (Hatsize) online lab
delivery platform.
• Virtual On-Demand Training (VODT)
̶ Lessons of the course are delivered as recorded video sessions which are
accessed via the Hatsize VODT portal.
̶ Hands-on labs are delivered using the Veritas Education (Hatsize) VODT online
lab delivery portal.
̶ This document does not discuss the VODT lab environment.
Each of the lab environments that are used to deliver the labs of the course requires
slightly different steps to access and interact with the systems in the lab kit – varying
primarily in the startup of the lab kit systems.
Determine from your instructor and/or from your class registration material which
Veritas lab delivery environment is being used for this class. Then, click the appropriate
link below to access the introductory information for your lab kit:
• Click this link to go to Exercise B: Introduction to your Hatsize (VILT) lab kit.
• Click this link to go to Exercise C: Introduction to your VMware Workstation lab kit.
• Click this link to go to Exercise D: Introduction to your Nimbus/NextGen lab kit.
Lab 1-2

Exercise B: Introduction to your Hatsize (VILT) lab kit
The Hatsize (VILT) lab environment is a Web-based lab environment that runs on a
VMware ESX platform.
When you register for the NetBackup 8.1: Administration course that is delivered as a
Virtual Instructor-Led Training (VILT) class, the registration information that you receive
will contain the information required to connect and login to the Hatsize (VILT) lab
portal.
In this exercise, you prepare and familiarize yourself with the Hatsize (VILT) lab
environment used in this NetBackup 8.1: Administration course.
When performing the lab activities of this course you must first choose whether you will
use:
• The Windows-based NetBackup servers, winmaster.example.com and

winmedia.example.com
OR
• The Linux-based NetBackup Servers, lnxmaster.example.com and

lnxmedia.example.com.
Time will not permit you to perform the labs using both Windows-based and
Linux-based systems.
• To perform the labs in a Windows-based lab environment, continue to Exercise B-1:

Introducing the Windows-based lab environment -VILT.
• To perform the labs in a Linux-based lab environment, continue to Exercise B-2:
Introducing the Linux-based lab environment-VILT.
Lab 1-3

Exercise B-1: Introducing the Windows-based lab
environment - VILT
You have elected to perform the lab activities of this course using the Windows-based
NetBackup server systems, winmaster.example.com and winmedia.example.com.
IMPORTANT: If your intention is to use the Linux-based NetBackup server systems,

lnxmaster.example.com and lnxmedia.example.com, go to Exercise B-2: Introducing
the Linux-based lab environment – VILT.
The figure illustrates systems in the Windows-based lab environment for this course.
NetBackup 8.1 software has been pre-installed on lab systems as follows:
• winmaster – NetBackup 8.1 master server, media server, and client

• winmedia - NetBackup 8.1 media server and client
• console - NetBackup 8.1 Administration Console, 8.1 client, and OpsCenter 8.1
• vcenter2 – NetBackup 8.1 client, NetBackup plug-in for vSphere Web Client
• winvm1 - 8.1 NetBackup client software is installed
• vtl1, esx2, and lnxvm2 - No NetBackup software installed
Lab 1-4

Although the Linux-based NetBackup master and media server systems,
lnxmaster.example.com and lnxmedia.example.com, exist in your lab kit,
these systems will not be used.
In the lab kits for all Veritas Education Virtual Instructor-Led Training (VILT) classes, all
systems in the lab kits are powered on by default. Systems that are not required/not
may be powered off to conserve lab resources.
To power off the Linux-based NetBackup server systems (optional), perform the
following steps.
Great care must be used when powering off systems in the lab environment, as
powering off the wrong systems could render the lab environment inoperative.
1. Power off (shut down) lnxmaster.example.com in Hatsize/VILT.
a. In the Hatsize user interface, click the drop-down System arrow for the
lnxmaster system.
b. In the menu, click Shutdown.
Lab 1-5

2. Power off (shut down) lnxmedia.example.com in Hatsize/VILT.
a. In the Hatsize user interface, click the drop-down System arrow for the lnxmedia
system.
Continue to Exercise E: Accessing remote lab systems.

Lab 1-6

Exercise B-2: Introducing the Linux-based lab
environment - VILT
You have elected to perform the lab activities of this course using the Linux-based
NetBackup server systems, lnxmaster.example.com and lnxmedia.example.com.
IMPORTANT: If your intention is to use the Windows-based NetBackup server systems,

winmaster.example.com and winmedia.example.com, go to Exercise B-1: Introducing
the Windows-based lab environment – VILT.
The figure below illustrates systems in the Linux-based lab environment for this course.
• lnxmaster – NetBackup 8.1 master server, media server, and client

• lnxmedia - NetBackup 8.1 media server and client
• console - NetBackup 8.1 Remote Administration Console, client, and OpsCenter 8.1
• vcenter2 – NetBackup 8.1 client, NetBackup plug-in for VMware vSphere Web Client
Lab 1-7

Although the Windows-based NetBackup master and media server systems,
winmaster.example.com and winmedia.example.com, exist in your lab kit,
In the lab kits for all Veritas Education Virtual Instructor-Led Training (VILT) classes, all
systems in the lab kits are powered on by default. Systems that are not required/not
used may be powered off to conserve lab resources.
To power off the Windows-based NetBackup server systems (optional), perform the
following steps.
Great care must be used when powering off systems in the lab environment, as
powering off the wrong systems could render the lab environment inoperative.
1. Power off (shut down) winmaster.example.com in Hatsize/VILT.
winmaster system.
Lab 1-8

2. Power off (shut down) winmedia.example.com in Hatsize/VILT.
winmedia system.

Lab 1-9

Exercise C: Introduction to your VMware
Workstation (ILT) lab kit
When attending an instructor-led (ILT) NetBackup 8.1: Administration class in which the
labs are delivered using VMware Workstation, you will use a physical Windows-based
workstation or laptop on which the lab kit for the course has been deployed.
Your instructor can answer questions you may have about using VMware Workstation.
In a VMware Workstation-based lab kit, the virtual machines that comprise the lab
environment for the course are powered off, by default. It will be necessary for either
the instructor or you to manually power up the systems in the order/sequence that is
defined in this exercise.
Before powering up the lab systems, you must first decide whether you will perform the
labs using...

OR
• The Linux-based NetBackup Servers, lnxmaster.example.com and

• To perform the labs in a Windows-based lab environment, continue to Exercise C-1:

Introducing the Windows-based lab environment – VMware Workstation (ILT).
• To perform the labs in a Linux-based lab environment, continue to Exercise C-2:
Introducing the Linux-based lab environment- VMware Workstation (ILT).
Lab 1-10

Exercise C-1: Introducing the Windows-based lab
environment – VMware Workstation (ILT)

lnxmaster.example.com and lnxmedia.example.com, go to Exercise C-2: Introducing
the Linux-based lab environment – VMware Workstation (ILT).

Lab 1-11

When preparing for the labs, the virtual machines that comprise the lab kit must be
powered on manually.
1. Click the appropriate link below, depending on the current power state of the lab
systems.
̶ If the systems are already powered on (as indicated by your instructor), click the
link to go to Exercise E: Accessing remote lab systems.
̶ To power on the lab systems, continue to the next step.
2. Power on the systems of your lab kit, using the power on order/sequence described
in the table. The detailed instructions are provided in the table.
The systems must be powered on in the sequence and timing specified in the
table or you may experience problems when performing lab steps.
Startup System Detailed Instructions: IMPORTANT Sequence and Timing

order Name
1 console • Power on “console”.
• Wait until LOGIN PROMPT is displayed.
• Log in to “CONSOLE” (EXAMPLE\Administrator, train) and wait
for desktop to be displayed (with shortcuts).
• Log out (Sign out) of “console”.
• Continue to the next VM.
2 vtl1 • Power on “vtl1”

• Continue on to next VM.
3 esx2 • Power on “esx2”
• WAIT until “<F2> Customize System/View Logs”
message displayed.

-- Continued on the next page --
Lab 1-12

order Name
4 vcenter2 • Power on “vcenter2”.
• Log in to “vcenter2” (EXAMPLE\Administrator, train) and wait
Wait until VMware Services are RUNNING. Test by running the
“net start |findstr vSphere” command.
(May take 5+ minutes.) Look for “VMware vSphere Web Client”
in command output (as in the screenshot).
• Log out (Sign out) of “vcenter2”.

• Continue to next VM.
5 winmaster • Power on “winmaster”.
• Log in to “winmaster” (EXAMPLE\Administrator, train) and wait
• WAIT UNTIL NetBackup master services are RUNNING. Test by
running the “net start |findstr Execution”
command.
(May take 3+ minutes.) Look for “NetBackup Policy Execution
Manager” entry in command output (as in the screenshot).
Even though the Policy Execution Manager is displayed in the
command output, it may take an additional minute or two
before NetBackup is fully up-and-running on the system.
• Log out (Sign out) of “winmaster”.

6 winmedia • Power on “winmedia”.
• Continue to next steps.
Do not power up the lnxmaster.example.com or lnxmedia.example.com

systems, as you have elected to perform the labs using the Windows-based
systems, winmaster.example.com and winmedia.example.com.
Lab 1-13

Exercise C-2: Introducing the Linux-based lab
environment – VMware Workstation (ILT)

winmaster.example.com and winmedia.example.com, go to Exercise C-1: Introducing
the Windows-based lab environment – VMware Workstation (ILT).

Lab 1-14

systems.
̶ To power on the lab systems, continue to the steps below.
2. Power on the systems of your lab kit, using the power on order/sequence described
in the table. The detailed steps are provided in the table.
The systems must be powered on in the sequence and timing specified in the
table or you may experience problems when performing lab steps.

order Name
1 console • Power on “console”.
• Log in to “CONSOLE” (EXAMPLE\Administrator, train) and wait
• Log out (Sign out) of “console”.
• Continue to the next VM.
2 vtl1 • Power on “vtl1”

3 esx2 • Power on “esx2”
• WAIT until “<F2> Customize System/View Logs”
message displayed.
-- Continued on the next page --
Lab 1-15

order Name
4 vcenter2 • Power on “vcenter2”.
• Log in to “vcenter2” (EXAMPLE\Administrator, train) and wait
• Wait until VMware Services are RUNNING. Test by running the
“net start |findstr vSphere” command.
(May take 5+ minutes.) Look for “VMware vSphere Web Client”
in command output (as in the screenshot).
• Log out (Sign out) of “vcenter2”.

5 lnxmaster • Power on “lnxmaster”.
• Log in to “lnxmaster” (root, train).
• WAIT UNTIL NetBackup master services are RUNNING. Test by
running the “bpps |grep nbsvcmon” command.
(May take 3+ minutes.) .) Look for “nbsvcmon” in command
output (as in the screenshot). Even after nbsvcmon is displayed
in the command output it may take another minute or two
before the master server services are fully up and ready.
• Log out of “lnxmaster” (exit).

6 lnxmedia • Power on “lnxmedia”.
• Continue to next steps.
Do not power up the winmaster.example.com or winmedia.example.com

systems, as you have elected to perform the labs using the Linux-based
systems, lnxmaster.example.com and lnxmedia.example.com.
Lab 1-16

Exercise D: Introduction to your Nimbus/NextGen
lab kit
The Nimbus/NextGen lab delivery environment is a VMware ESX-based platform that is

used to deliver lab kits for Veritas Education instructor-led (ILT) classes.
When attending a class that uses the Nimbus/NextGen lab environment, you will access
your lab kit from a desktop or laptop system using a Web browser. Your instructor will
provide directions to enable you to access your lab kit.
In a Nimbus/NextGen-based lab kit, the virtual machines that comprise the lab
environment for the course are powered off, by default. It will be necessary for
either the instructor or you to manually power up the systems in the
order/sequence that is defined in this exercise.
Before powering up the lab systems, you must first decide whether you will perform the
labs using...

winmedia.example.com.
OR
• The Linux-based NetBackup servers, lnxmaster.example.com and

• To perform the labs in a Windows-based lab environment, continue to Exercise D-1:

Introducing the Windows-based lab environment – Nimbus/NextGen (ILT).
• To perform the labs in a Linux-based lab environment, continue to Exercise D-2:
Introducing the Linux-based lab environment- Nimbus/NextGen (ILT).
Lab 1-17

Exercise D-1: Introducing the Windows-based lab
environment – Nimbus/NextGen (ILT)

lnxmaster.example.com and lnxmedia.example.com, go to Exercise D-2: Introducing
the Linux-based lab environment – Nimbus/NextGen (ILT).

Lab 1-18

systems.
̶ To power on the lab systems, continue to the next page.
Lab 1-19

2. Power on the systems of your lab kit. The details are provided in the sub-steps
below.
The Nimbus/NextGen lab environments user interface enables the boot up of

all the systems (virtual machines) to be initiated with a single mouse click. The
systems in the lab kit are powered on in a pre-determined “boot order”.
a. In the Nimbus/NextGen user interface, locate and click the Power On All Virtual
Machines entry, located in the Power Controls for Entire Kit pane.
b. Monitor the startup of the lab kit systems until all systems have been started.
c. When the Power On Virtual Machines window displays the Close Window
button, click the button to close the window.
Lab 1-20

All systems in the lab kit are powered on in the sequence specified in the table
(as determined by a pre-determined boot order).
Startup Virtual Machine Name Description

order
1 console.example.com Domain Controller, DNS, NetBackup Admin
Console, NetBackup 8.1 client
2 vtl1.example.com Virtual tape library with tape drives
3 esx2.example.com VMware ESX server
4 vcenter2.example.com VMware vCenter server
5 winmaster.example.com NetBackup 8.1 master/EMM/media server
6 lnxmaster.example.com NetBackup 8.1 master/EMM/media server

7 winmedia.example.com NetBackup 8.1 media server
8 lnxmedia.example.com NetBackup 8.1 media server
You have elected to perform the Windows lab steps.
3. Power off the lnxmaster.example.com and lnxmedia.example.com systems.
The detailed steps are provided below. (See the screenshot on the next page
for an illustration of the steps).
a. In the Nimbus/NextGen user interface, click the checkboxes for the

lnxmaster.example.com and lnxmedia.example.com systems.
b. Select the Actions drop-down menu, and then click Power Change, followed by
Shutdown Selected VMs.
c. Monitor the shutdown of lnxmaster.example.com and lnxmedia.example.com.

d. When the Shutdown Virtual Machines window displays the Close Window
Lab 1-21

Lab 1-22

Exercise D-2: Introducing the Linux-based lab
environment – Nimbus/NextGen (ILT)

winmaster.example.com and winmedia.example.com, go to Exercise D-1: Introducing
the Windows-based lab environment – Nimbus/NextGen (ILT).

Lab 1-23

systems.
̶ To power on the lab systems, continue to the next page.
Lab 1-24

2. Power on the systems of your lab kit. The details are provided in the sub-steps
below.
The Nimbus/NextGen user interface enables the boot up of all systems (virtual
machines) to be initiated with a single mouse click. The systems in the lab kit
are powered on in a pre-determined “boot order”.
a. In the Nimbus/NextGen user interface, locate and click the Power On All Virtual
Machines entry, located in the Power Controls for Entire Kit pane.
b. Monitor the startup of the lab kit systems until all systems have been started.
c. When the Power On Virtual Machines window displays the Close Window
Lab 1-25

All systems in the lab kit are powered on in the sequence specified in the table
(as determined by a pre-determined boot order).
Startup Virtual Machine Name Description

order
1 console.example.com Domain Controller, DNS, NetBackup Admin
Console, NetBackup 8.1 client
2 vtl1.example.com Virtual tape library with tape drives
3 esx2.example.com VMware ESX server
4 vcenter2.example.com VMware vCenter server
5 winmaster.example.com NetBackup 8.1 master/EMM/media server
6 lnxmaster.example.com NetBackup 8.1 master/EMM/media server

7 winmedia.example.com NetBackup 8.1 media server
8 lnxmedia.example.com NetBackup 8.1 media server
You have elected to perform the Linux lab steps.
3. Power off the winmaster.example.com and winmedia.example.com systems.
The detailed steps are provided below. (See the screenshot on the next page
for an illustration of the steps).
a. In the Nimbus/NextGen user interface, click the checkboxes for the

winmaster.example.com and winmedia.example.com systems.
b. Select the Actions drop-down menu, and then click Power Change, followed by
Shutdown Selected VMs.
c. Monitor the shutdown of winmaster.example.com and

d. When the Shutdown Virtual Machines window displays the Close Window
Lab 1-26

Lab 1-27

Exercise E: Accessing remote lab systems
The lab activities of this course have been written so that most tasks are performed
from the desktop of the console.example.com system.
However, there will be occasions when it is necessary to perform tasks by accessing

another system, such as a master server or media server system. In situations where it is
necessary to perform an operation from a system other than the console.example.com
system, you have two options:
• Option 1 - Hatsize (VILT) and VMware Workstation (ILT): Access the tab for the
system that is provided by the HatSize (VILT) and VMware Workstation (ILT) user
interfaces. The Nimbus/NextGen (ILT) user interface does not provide tabs to access
the virtual machine desktops.
• Option 1 – Nimbus/NextGen: To directly access the desktops of lab systems in
Nimbus/NextGen you must RDP or PuTTY to the systems using the IP address that is
provided on the Nimbus/NextGen user interface.
• Option 2: Remotely access a system from the console.example.com system:
̶ Accessing Linux-based systems: When a task requires access to a Linux-based
system, you can open a remote shell (SSH) to the Linux-based host from the
console system using PuTTY.
̶ Accessing Windows-based system: When a task requires access to the desktop
of a Windows-based system, you can access that system using a Remote
Desktop (RDP) connection from the console.example.com system.
1. To view the instructions to use option 2 (remotely access your NetBackup master
server system, lnxmaster.example.com (Linux) or winmaster.example.com

(Windows) from the console.example.com system), click the appropriate link below.
̶ To access the command prompt of a remote Linux-based system using PuTTY,

continue to Exercise E-1: Connecting to a remote Linux-based system using
PuTTY.
̶ To access the desktop of a remote Windows-based system using Remote
Desktop (RDP), continue to Exercise E-2: Connecting to a remote Windows-based
system using RDP.
2. After testing the ability to use PuTTY or Remote Desktop (RDP) to access the master
server of your lab kit, click the link to continue to Exercise F: Launching the
NetBackup Administration Console.
Lab 1-28

Exercise E-1: Connecting to a remote Linux-based system
using PuTTY
To connect to a Linux-based system such as lnxmaster.example.com (Linux-based

master server), from console.example.com using PuTTY, perform the steps listed below.
The steps of this exercise will fail if you previously have powered off the
lnxmaster.example.com system. This is expected behavior – do not attempt to
connect to lnxmaster.example.com. If you are using the Windows-based
master server, winmaster.example.com, go to Exercise E-2: Connecting to a
remote Windows-based system with RDP.
1. Access the desktop of the console.example.com system.
console.example.com UserID: EXAMPLE\Administrator Password: train
2. Log in to console.example.com with the username, EXAMPLE\Administrator, and

the password, train.
3. Locate and double-click the REMOTE SYSTEM ACCESS folder on the desktop of the
console.example.com system, to open the folder.
4. Double-click the Putty shortcut that is located in the REMOTE SYSTEM ACCESS
folder, as highlighted in the figure below.
Continue to the next page.
Lab 1-29

Within a moment the PuTTY Configuration window is displayed.
5. Locate and double-click the pre-configured entry for the Linux-based system that
you wish to connect to, such as lnxmaster.example.com.
6. Within a moment a PuTTY window is displayed that will enable you to log in to the
selected Linux-based system.
For the lnxmaster.example.com and lnxmedia.example.com systems, log in to

the systems using the username, root, and the password, train. Login
credentials for all systems are provided in the IMPORTANT CREDENTIAL INFO
file that is located on the desktop of the console.example.com system.
7. When you have completed the tasks on the remote Linux-based system, close the
PuTTY window.
After testing the ability to use PuTTY to access the command prompt on the master
server of your lab kit (lnxmaster.example.com), click the link to continue to Exercise
F: Launching the NetBackup Administration Console.
Lab 1-30

Exercise E-2: Connecting to a remote Windows-based
system with RDP
To connect to remote a Windows-based system, such as winmaster.example.com

(Windows-based master server), from console.example.com using Remote Desktop
(RDP), follow the steps below.
The steps of this exercise will fail if you previously have powered off the
winmaster.example.com system. This is expected behavior – do not attempt to
connect to winmaster.example.com. If you are using the Linux-based master
server, lnxmaster.example.com, continue to Exercise E-1: Connecting to a
remote Linux-based system with PuTTY.
2. Log in to the console.example.com system with the username,

EXAMPLE\Administrator, and the password, train.
4. Locate and double-click the RDP Profiles (Windows systems) sub-folder, located in
the REMOTE SYSTEM ACCESS folder, to open the folder.
The RDP Profiles (Windows systems) folder contains RDP profiles for the
Windows-based systems in this lab environment, as illustrated below.
Lab 1-31

5. To open a Remote Desktop connection to a Windows-based system, such as
winmaster.example.com, locate and double-click the RDP file for the system (i.e.,
winmaster.rdp).
Within a few moments a Windows Security dialog box will be displayed, prompting
you to enter the login credentials for the system.
6. Enter the login credentials for the system.
To log in to most of the Windows-based systems in the lab environment, use

the User name = EXAMPLE\Administrator, and the password = train).
The IMPORTANT CREDENTIALS file, located on the desktop of

console.example.com, contains login credentials for all systems in the lab
environment.
7. When you have performed the desired tasks on the remote Window-based system
log out (Sign out) of the system to close the RDP session.
After testing the ability to use Remote Desktop (RDP) to access the desktop of the
master server of your lab kit (winmaster.example.com), click the link to continue to
Exercise F: Launching the NetBackup Administration Console.
Remote Desktop (RDP) can be used to access the desktop of any Windows-
based system in your lab kit (winmaster.example.com,
winmedia.example.com, vcenter2.example.com, and winvm1.example.com)
from the console.example.com system.
Lab 1-32

Exercise F: Launching the NetBackup Administration
Console
In this exercise, you perform the steps to launch the NetBackup 8.1 Administration
Console and login to your master server system.
Continue to Exercise F-1: Launching the NetBackup Administration Console.

Lab 1-33

Exercise F-1: Launching the NetBackup Administration
Console
In this exercise you will locate, launch, and log into the NetBackup Administration
Console for a master server.
2. Log on to the console.example.com system (as necessary), using the credentials

provided above.
3. Locate and double-click the NetBackup 8.1 Administration Console shortcut,

located on the desktop of console.example.com.
The figure below illustrates the Administration Console login screen.

Lab 1-34

4. Enter the Host name, User name, and Password of your preferred master server
system, and click Login. Use the information in the table below. (You can use the
drop-down arrows to select the Host name and User name.)
Operating system Master server name User Name Password

Windows-based winmaster.example.com EXAMPLE\Administrator train
Linux-based lnxmaster.example.com root train
After successfully logging in, the NetBackup Administration Console is displayed.
For a Windows-based master server (only) you may use Active Directory
credentials to log in to the NetBackup Administration Console by marking the
“Use Active Directory login credentials” check box on the login screen. Actions
that can be performed by a user are dependent on the user permissions that
are configured in NetBackup.
The NetBackup Administration Console window title bar contains the host
name of the NetBackup master server that you have logged in to, and the
NetBackup software version running on that system.
The name of the NetBackup server you are connected to is indicated at the top of
the left pane of the Administration Console. See the figure below for an example.
5. Verify that the NetBackup Administration Console is connected to your preferred

master server, winmaster.example.com or lnxmaster.example.com, before
continuing.
Lab 1-35

6. Click the down-arrow, labelled Login Activity, in the upper-right corner of the
Administration Console window.
7. Take note of the My Recent Login Activity information that is displayed. See the
figure below for an example.
The Login Activity information was added in the 8.0 version of the NetBackup
Administration Console.
8. Click Close to close the My Recent Login Activity pane.
9. Continue to Exercise G: Exploring the NetBackup Administration Console.
Lab 1-36

Exercise G: Exploring the NetBackup Administration
Console
In this exercise, you will:
• Identify the general NetBackup Administration Console layout for a master server.
• Verify NetBackup licenses in the NetBackup Administration Console.
• Verify NetBackup licenses using the NetBackup command line.
Continue to Exercise G-1: Identifying NetBackup Administration Console tasks.

Lab 1-37

Exercise G-1: Identifying NetBackup Administration
Console tasks
In the steps that follow, you locate and identify the tasks the can be performed using
the NetBackup Administration Console by viewing the layout of the user interface.
1. Collapse all entries in the left pane of the Administration Console – so that a
minimum number of entries are displayed.
2. Take note of the entries listed in the “tree” in the left pane.
3. Review the NetBackup tree entries listed in the table below.
xxxmaster.example.com (Master Server)

Backup, Archive, and Restore
Activity Monitor
NetBackup Management
Media and Device Management
Security Management
Vault Management
Bare Metal Restore Management
Logging Assistant
4. Click the symbol to the left of the NetBackup Management entry in the left pane of
the Administration Console to expand the NetBackup Management entry.
5. Take note of the entries listed below the NetBackup Management entry. These
functions and categories are listed in the table below.
Reports
Policies
Storage
Catalog
Host Properties
Applications
6. Click the name of the master server, located at the top of the left pane of the
Administration Console. (This is the entry immediately above the Backup, Archive,
and Restore entry.)
Lab 1-38

7. Take note of the names of the NetBackup wizards that are displayed in the right
pane of the Administration Console. The master server wizards are listed in the table
below.
Getting Started
Configure Storage Devices
Configure Disk Storage Servers
Configure Cloud Storage Server
Configure Disk Pool
Configure Volumes
Configure the Catalog Backup
Create a Policy
Recover the catalogs
Proceed to Exercise H: Verifying the NetBackup licenses.

Lab 1-39

Exercise H: Verifying NetBackup licenses
NetBackup licenses must be administered on each NetBackup server system.
In this training course, NetBackup evaluation licenses are used to enable all
NetBackup functionality for a limited period of time.
In the steps that follow you use the NetBackup Administration Console to view the
license key on the master server only.
Continue to Exercise H-1: Verifying licenses in the Administration Console.

Lab 1-40

Exercise H-1: Verifying licenses in the Administration
Console
In the steps that follow, you use the NetBackup Administration Console to view the
NetBackup license on your master server system.
2. Access the open NetBackup Administration Console window on

console.example.com.
If a NetBackup Administration Console window is not currently open, launch a new

Administration Console window now, by double-clicking the NetBackup 8.1
Administration Console shortcut on the desktop of console.example.com.
Operating system Master server name User Name Password

3. In the NetBackup Administration Console window, verify that you are connected to
your preferred master server, winmaster.example.com or lnxmaster.example.com.
4. Click the Help button on the tool bar of the Administration Console.
5. Click License Keys in the resulting menu. See the figure below for an example.
The NetBackup License Keys window is displayed.
Lab 1-41

6. Scroll to the Base NetBackup license entry, located at the bottom of the NetBackup
License Keys window, and click the entry for the license key.
7. With the Base NetBackup license key entry highlighted, click the Properties button.
8. In the Properties window, scroll down to locate the Host, Valid, and Expiration
license key fields (the fields are not adjacent to one another).
Scroll the Properties window contents to locate the information requested.
9. Verify that the Base NetBackup license for the master server system does not expire
before the end of this training class.
10. Click Close to close the Properties window.
11. Click Close to close the NetBackup License Keys window.
Continue to Exercise H-2: Verifying licenses from the command line.

Lab 1-42

Exercise H-2: Verifying licenses from the command line
In the steps that follow, you use the NetBackup-provided bpminlicense command to
view NetBackup licenses on your master and media server systems.
1. Access the desktop of your master server system (winmaster.example.com or

lnxmaster.example.com).
winmaster.example.com Username: EXAMPLE\Administrator Password: train
lnxmaster.example.com Username: root Password: train
2. Log in to your master server using the credentials described above.
3. Open a Command Prompt window (on winmaster.example.com), or access the

command prompt (on lnxmaster.example.com).
Viewing the master server license

By default, the PATH to folder or directory locations that contain NetBackup
commands are not set automatically when NetBackup is installed. Customers
may wish to add these folders or directories to the PATH environment variable
on NetBackup systems. In this lab environment, those paths have been added
to the PATH environment variable, enabling you to execute the command
without first having to change to the folder or directory.
4. At the Command Prompt on your master server, execute the following command to
list the NetBackup license or licenses for your master server system:
Command: bpminlicense –list_keys
5. Take note of the output of the command.
6. Repeat the bpminlicense command, using the verbose command option, as shown
below.
Command: bpminlicense –list_keys -verbose
7. Take note of the expiration date and the features that are enabled by the license.
Lab 1-43

Viewing the media server license
The bpminlicense command can be used with the option, -M [nb_server_name], to
enable viewing or adding of licenses on any NetBackup server to which the local system
has administrative access, as provided in the NetBackup Server list of the remote
NetBackup server.

8. At the Command Prompt on your master server, execute the following command to
list the NetBackup license or licenses for your media server system:
Command:
bpminlicense –list_keys –M winmedia.example.com
-verbose
or
Command:
bpminlicense –list_keys –M lnxmedia.example.com
-verbose
9. Take note of the expiration date and the features that are enabled by the license key
for your media server.
The bpminlicense command provides the -list_keys and -add_keys command

options to enable NetBackup license administration.
10. Close the Command Prompt window on your master server system, and log out of
the system (if necessary).
Proceed to Exercise I: Identifying common Administration Console configuration

items.
Lab 1-44

Exercise I: Identifying common Administration
Console configuration items
In this exercise, you perform tasks to become familiar with the layout and common
functions of the NetBackup Administration Console. Key tasks in this exercise include:
• Identifying the common NetBackup Management configuration tasks

• Identifying the common Media and Device Management configuration tasks
Continue to Exercise I-1: Identifying common NetBackup Management configuration

items.
Lab 1-45

Exercise I-1: Identifying common NetBackup
Management configuration items
In the steps that follow you locate and identify many of the configuration-related tasks
that are performed using the NetBackup Administration Console.
1. Access the NetBackup Administration Console window on console.example.com.
Your NetBackup Administration Console is connected to your NetBackup

master server – based on your OS preference, as identified in the table below.
Operating system Master server hostname User name Password

2. Verify that the Administration Console is connected to your master server system.
If it is not, launch a new Administration Console window and connect to the

master server.
3. In the left pane of the Administration Console, click to expand NetBackup

Management.
Continue to Exercise I-2: NetBackup Storage Units.

Lab 1-46

Exercise I-2: NetBackup Storage Units
In the steps that follow, you locate and identify the NetBackup storage units that have
been pre-configured in the lab environment for this course.
1. Click to expand Storage, located under NetBackup Management in the left pane of
the NetBackup Administration Console. The results are illustrated in the figure
below.
2. Click the Storage Units entry, located under Storage.
The storage units that are currently configured in your NetBackup environment are
displayed in the right pane of the Administration Console.
3. Click the first (top) Storage Unit entry that is listed in the right pane.
4. Resize the data presented in the columns.
Click View -> Columns -> Size to Data.
The column width will automatically be resized to make the contents more readable.
This option is available for most information presented as tables in the NetBackup
8.1 Administration Console. Feel free to experiment with this option throughout the
labs.
The Size to Data option is only available after you have selected an object in
the right pane of the console.
Lab 1-47

5. Take note of the storage unit information for the currently-configured storage units
listed in the table below.
Storage Unit Name Media Server Storage Unit Type Disk Type
master_tape_stu xxxmaster.example.com Media Manager n/a
master_bdisk_stu xxxmaster.example.com Disk BasicDisk
master_advdisk_stu xxxmaster.example.com Disk AdvancedDisk
master_msdp_stu xxxmaster.example.com Disk PureDisk
Continue to Exercise I-3: NetBackup Host Properties.

Lab 1-48

Exercise I-3: NetBackup Host Properties
In the steps that follow, you view the types and categories of Host Property settings
that are available for NetBackup master servers, media servers, and clients.
1. Expand the Host Properties entry, located under NetBackup Management in the left
pane of the Administration Console. The figure below illustrates the results.
2. Click the Master Servers entry, located under Host Properties.
The right pane of the Administration Console displays a master server entry.
3. Click the entry for the master server in the right pane of the Administration Console.
4. In the tool bar of the Administration Console, select Actions and then Properties.
The Master Server Properties window for your master server is displayed.
Master Server Host Properties

The left pane of the Master Server Properties window contains a list of Host Properties
categories for a master server, including: Global Attributes, Universal Settings,
Retention Periods, and many more.
When you click on a Properties category in the left pane of the Master Server
Properties window, the right pane of the window displays the parameters that
can be configured for that Properties category.
Lab 1-49

5. Click the Global Attributes entry in the left pane of the Master Server Properties
window.
6. Take note of the Global Attributes parameters that can be configured.
For now, do not change any of the Global Attributes parameter settings.
7. Click the Retention Periods entry in the left pane of the Master Server Properties
window.
8. Take note of the default Retention Periods that are associated with each standard
(default) NetBackup Retention Level.
A Retention Period is the amount of time that a backup image is retained (from
the time it was created) until it is expired. Each Retention Level is assigned a
Retention Period.
For now, do not change any of the Retention Periods parameter settings.
9. Click the Media entry in the left pane of the Master Server Properties window.
10. Take note of the Media parameters that can be configured.
For now, do not change any of the Media parameter settings.
11. Take a few minutes to browse through other Master Server Properties categories
before continuing to the next step of this lab activity.
12. Click the Properties entry, located at the top of the left pane of the Master Server
Properties window.
13. Click Cancel to close the Master Server Properties window.
Lab 1-50

Media Server Host Properties
In the steps that follow, you view media server Host Properties to become familiar with
the categories of media server properties that can be configured.
14. Click the Media Servers entry, located under Host Properties in the left pane of the
The right pane of the Administration Console displays a list of media servers that
exist in your NetBackup environment, as illustrated in the figure below.
A NetBackup master server can simultaneously serve as a media server, as is

the case in the lab environment for this course.
The right pane of your Administration Console contains two entries – one for your
master/media server, and another for your media server – as illustrated in the figure
above.
15. Double-click the entry for your media server, located in the right pane of the
Administration Console – based upon your preferred operating system. See the table
below.
Operating system Media server hostname

Windows-based winmedia.example.com
Linux-based lnxmedia.example.com
Lab 1-51

The Media Server Properties window is displayed.
16. Click the Properties entry, located at the top of the left pane of the Media Server
Properties window.
The left pane of the Media Server Properties window lists the Properties categories,
as illustrated in the figure below.
The contents of the right pane of the Media Server Properties window varies,
depending upon the Properties category that is selected in the left pane.
17. Browse the Media Server Properties categories before continuing to the next step.
18. Click the Properties entry, located at the top of the left pane of the Media Server
Properties window.
19. Click Cancel to close the Media Server Properties window.
Lab 1-52

Client Host Properties
20. In the left pane of the Administration Console, select NetBackup Management,
followed by Host Properties.
NetBackup Management > Host Properties
21. Click the Clients entry, located under Host Properties in the left pane of the
22. Double-click the entry for one of the clients (any client) that is listed in the right
pane of the Administration Console.
23. Click the Properties entry, located at the top of the left pane of the Client Properties
window.
The figure below illustrates Properties categories that are visible in the Client
Properties window.
For now, do not change any of the parameter settings in the Client Properties.
24. Click Cancel to close the Client Properties window.
Continue to Exercise I-4: NetBackup Policies.
Lab 1-53

Exercise I-4: NetBackup Policies
In the steps that follow, you locate and identify the NetBackup policies that have been
pre-configured for this course, and view the general characteristics of a policy.
1. Click Policies, located under NetBackup Management in the left pane of the
The policies that have been pre-configured on the master server for this lab
environment are displayed in the All Policies pane, as illustrated in the figure at the
top of the next page.
2. Expand the entry for the PRE-clients-to-master-bdisk policy.
3. Take note of the policy components that are displayed under the entry for the PRE-
clients-to-master-bdisk policy.
Policy components
Attributes
Schedules
Clients
Backup Selections
4. Double-click the entry for the PRE-clients-to-master-bdisk policy, located in the All
Policies pane, to open the policy.
The Change Policy window is opened to enable viewing and editing of the PRE-
clients-to-master-bdisk policy.
Lab 1-54

5. Take note of the tabs in the Change Policy window, including Attributes, Schedules,
Clients, and Backup Selections.
The Attributes tab is selected by default in the Change Policy window.
6. Take note of the large number of parameters provided in the Attributes tab,
including: Policy type, Policy storage, Policy volume pool, and many others.
For now, do not modify the contents of the Attributes tab.
7. Click the Schedules tab in the Change Policy window of the PRE-clients-to-master-
bdisk policy.
8. Take note of the schedule name and schedule type of each schedule that is listed in
the Schedules tab of the policy.
For now, do not modify the contents of the Schedules tab.
9. Click the Clients tab in the Change Policy window of the PRE-clients-to-master-bdisk
policy.
10. Take note of the client name, hardware, and operating system of each client that is
listed in the Clients tab of the policy.
For now, do not modify the contents of the Clients tab.
11. Click the Backup Selections tab in the Change Policy window of the PRE-clients-to-
master-bdisk policy.
12. Take note of the entries that are listed in the Backup Selections tab of the policy.
For now, do not modify the contents of the Backup Selections tab.
13. Click Cancel to close the Change Policy window without making modifications to the
PRE-clients-to-master-bdisk policy.
14. Take a few minutes to browse the other policies that have been pre-configured in
the lab environment.
Do not modify the contents of any policies at this time.
Continue to Exercise I-5: Identifying common Media and Device Management

objects.
Lab 1-55

Exercise I-5: Identifying common Media and Device
Management objects
In the steps that follow, you locate and identify many of the device and media related
operations that are performed using the Media and Device Management branch of the
NetBackup Devices
In the steps that follow you locate and identify the NetBackup devices and media that
have been pre-configured in the lab environment for this course.
1. Expand Media and Device Management in the left pane of the NetBackup
Administration Console. The figure below illustrates the results.
2. Expand the Devices entry, located under Media and Device Management.
The entries listed under Devices are Drives, Robots, Media Servers, Server Groups,
SAN Clients, Topology, and Disk Pools.
Lab 1-56

NetBackup Tape Drives
3. Click the Drives entry.
The Drives entry is located under Media and Device Management > Devices.
4. Review and confirm that the information for the tape drives listed in the right pane
of the Administration Console matches the information in the table below.
Drive Name Device Host Drive Type Robot Type

IBM.ULT3580-TD5.000 winmaster.example.com HCART2 TLD
or
lnxmaster.example.com
IBM.ULT3580-TD5.001 winmaster.example.com HCART2 TLD
or
By default, no tape drives are configured in NetBackup. The tape drives

identified in the previous step were pre-configured for this course.
NetBackup Robots
5. Click the Robots entry, located under Media and Device Management, in the left
pane of the NetBackup Administration Console.
Media and Device Management > Devices > Robots
The tape robot (robotic arm) that is pre-configured in this NetBackup environment is
listed in the right pane of the Administration Console.
6. Confirm that the information for the robot listed in the right pane of the
Administration Console matches the information in the table below.
Robot Name Device Host Robot Type

TLD(0) winmaster.example.com or lnxmaster.example.com TLD
The robot identified in the previous step was pre-configured for this course. By
default, robots are not configured in NetBackup.
Continue to Exercise I-6: Device Monitor.
Lab 1-57

Exercise I-6: Device Monitor
In the steps that follow, you view the NetBackup Device Monitor.
1. Click the Device Monitor entry, located in the left pane of the Administration
Console. The figure below illustrates the results.
The Device Monitor provides two tabs – the Drives tab and the Disk Pool tab.
When the Drives tab is selected, the right pane displays entries for all configured
tape drives. The drive entries contain drive status and configuration information.
2. If the tape drives displayed in the right pane are UP (as indicated by a green,
upward-pointing arrow), continue to Exercise I-9: NetBackup Media.
If one or both of the tape drives displayed in the right pane of the Administration
Console is DOWN (indicated by a downward-pointing, red arrow), take the
appropriate steps in order to bring the drive(s) to the UP status.
̶ For tape drives attached to winmaster.example.com, proceed to Exercise I-7:

Bringing tape drives UP on winmaster.example.com.
̶ For tape drives attached to lnxmaster.example.com, proceed to Exercise I-8:
Bringing tape drives UP on lnxmaster.example.com.
Lab 1-58

Exercise I-7: Bringing tape drives UP on
winmaster.example.com
The steps that follow document the procedure for bringing tape drives to the UP state
on the Windows-based NetBackup server, winmaster.example.com.
1. Access the NetBackup Administration Console window on console.example.com

that is logged in to the winmaster.example.com master server.
2. Expand Media and Device Management in the left pane of the Administration
Console window (if necessary), and then click the Device Monitor entry.
Bringing a tape drive UP using the Device Monitor

3. Right-click the entry for the first tape drive that is currently DOWN as indicated by a
red, downward-pointing arrow in the right pane of the Administration Console.
4. In the resulting menu that is displayed, click the Up Drive entry.
You could also select Actions > Up Drive.)
5. Repeat the previous step for any additional tape drive that is currently DOWN.
6. Select the Refresh icon on the Administration Console tool bar to refresh the
contents of the right pane.
View > Refresh, or the Refresh icon, or the F5 key
It may take several moments for the status icon for the tape drive(s) to change.
It may be necessary to repeat the Refresh operation one or two additional
times before the updated status of the tape drive(s) is displayed.
Lab 1-59

If the tape drive status of both tape drives is now UP as indicated by a green, upward-
pointing arrow), continue to Exercise I-9: NetBackup Media.
There are a number of reasons that the tape drive(s) may not be brought UP
using the Administration Console. This is often due to the timing of the startup
of the virtual machines in the lab environment and is not a cause for alarm.
If the status of one or both tape drives is still DOWN (indicated by a red,
downward-pointing arrow), continue to the next steps.
Bringing a tape drive UP using the NetBackup Command Line (CLI)

7. Close the NetBackup Administration Console window on console.example.com that
is connected to the master server, winmaster.example.com.
8. Access the desktop of the Windows-based master server, winmaster.example.com.
You can access winmaster.example.com by accessing the tab provided in the

lab user interface, or by RDP’ing from console.example.com).
winmaster.example.com UserID: EXAMPLE\Administrator Password: train
9. Log in to winmaster.example.com using the credentials provided above.
10. Double-click the Command Prompt shortcut, located on the desktop to open a
Command Prompt window.
11. In the Command Prompt window, type the scan command, and press Enter.
Command: scan

The NetBackup-provided scan command displays the tape devices that are
visible to NetBackup at the operating system level. If no devices are listed in
the output of the scan command, then reboot the winmaster.example.com
system.
Lab 1-60

12. If the output of the scan command shows no devices are visible to NetBackup,
reboot (restart) the winmaster.example.com system.
13. When the system has been restarted, access the Command Prompt and repeat the
scan command.
If no devices are displayed in the output of the scan command, seek assistance.
If two tape drives and a media changer (robot) are displayed in the output of
the scan command, continue to the next step.
14. In the Command Prompt window, type the tpconfig command using the command
syntax shown below, and press Enter.
Command: tpconfig -d
The NetBackup-provided tpconfig command displays the tape devices (drives

and robots) that are configured to NetBackup and the current status of the
tape drives.
15. In the output of the tpconfig command, take note of the tape drive ID the STATUS of
the tape drives, and any additional messages that may be displayed about the
devices.
16. If the tape drives are DOWN, but there are no additional error messages displayed
for the drives, complete steps 17-20.
If there is an error message indicating a MISSING PATH for the tape drives, continue
to "Stopping and Starting the NetBackup services", on winmaster.example.com, on
the next page.
Lab 1-61

17. In the Command Prompt window, type the vmoprcmd command to bring the first
tape drive UP, using the command syntax shown below, and press Enter.
Command: vmoprcmd –up [drive ID]
Example: vmoprcmd –up 0
18. In the Command Prompt window, type the vmoprcmd command to bring the
second tape drive UP, using the command syntax shown below, and press Enter.
19. In the Command Prompt window, type the tpconfig command using the command
20. View the STATUS of the tape drives in the output of the tpconfig command, and
verify that the drives have a status of UP.
21. If the STATUS of the tape drives is now UP, continue to Exercise I-9: NetBackup
Media.
If the tape drives are still DOWN, continue to the next step.
Stopping and Restarting the NetBackup services

If the steps you have taken have not resulted in the tape drives being returned to the UP
status, it may be necessary to stop and restart the NetBackup services on the NetBackup
server system (in this case, winmaster.example.com).

22. In the Command Prompt window, type the bpdown command, using the command
Command: bpdown –v -f
Lab 1-62

23. Wait for the Command Prompt to be returned before continuing. It may take a
minute or more for the command execution to be completed.
The NetBackup-provided bpdown command is used to stop the NetBackup

services on the NetBackup system on which the command is executed.
24. In the Command Prompt window, type the bpps command, using the command
Command: bpps
25. In the output of the bpps command, verify that all the NetBackup services have
been stopped.
If a NetBackup Administration Console has been left open and connected to

the master server, there will be a few services that are not stopped on the
master server system. This is not a cause for concern. Continue to the next
step.
26. In the Command Prompt window, type the bpup command, using the command
Command: bpup –v -f
The NetBackup-provided bpup command is used to start the NetBackup

services on the NetBackup system on which the command is executed.
27. Wait for the Command Prompt to be returned before continuing. It may take a
28. In the Command Prompt window, type the bpps command, using the command
Command: bpps
29. View the output of the bpps command, and verify that the NetBackup services have
been restarted on the master server, winmaster.example.com.
Lab 1-63

Verifying that the tape drives are UP
Perform the steps below to verify that the tape drives are UP.
30. Access the open Command Prompt window on winmaster.example.com.
31. In the Command Prompt window, type the tpconfig command, and press Enter.

32. View the output of the tpconfig command and verify that the tape drives have a
STATUS of UP.
If the tape drives are not UP, as indicated in the output of the tpconfig
command, notify your instructor. Do not continue the lab activity until the tape
drives are UP.

34. Log in (if necessary) to console.example.com using the credentials provided above.
36. In the Administration Console login window, log in to your master server.
Lab 1-64

37. Expand the Media and Device Management entry in the left pane of the
38. Click the Device Monitor entry in the left pane of the Administration Console.
The right pane displays the configured tape drives.
39. Verify that the tape drives are in the UP state, as indicated by green, upward-
pointing arrows next to each of the tape drive entries.
40. If the status of one or both tape drives is DOWN, seek assistance.
Continue to Exercise I-9: NetBackup Media.

Lab 1-65

Exercise I-8: Bringing tape drives UP on
The steps that follow document the procedure for bringing tape drives to the UP state
on the Linux-based NetBackup server, lnxmaster.example.com.
1. Access the NetBackup Administration Console window on console.example.com

that is logged in to the lnxmaster.example.com master server.
lnxmaster.example.com UserID: root Password: train
2. Expand Media and Device Management in the left pane of the Administration
Console window (if necessary), and then click the Device Monitor entry.
Bringing a tape drive UP using the Device Monitor

3. Right-click the entry for the first tape drive that is currently DOWN, in the right pane
of the Administration Console and, in the menu that is displayed, click the Up Drive
entry.
You could also select Actions > Up Drive.
4. Repeat the previous step for any additional tape drive that is currently DOWN.
5. Select the Refresh icon on the Administration Console tool bar to refresh the
contents of the right pane.
You could also select View > Refresh, or the Refresh icon on the Administration
Console tool bar or press the F5 key.
It may take several moments for the status icon for the tape drive(s) to change.
It may be necessary to repeat the Refresh operation one or two additional
times before the updated status of the tape drive(s) is displayed.
If the tape drive status of both tape drives is now UP (indicated by a green, upward-
pointing arrow), continue to Exercise I-9: NetBackup Media.
Lab 1-66

There are a number of reasons that the tape drive(s) may not be brought UP
using the Administration Console. This is often due to the timing of the startup
of the virtual machines in the lab environment. This is not cause for alarm.
If the status of one or both tape drives is still DOWN (indicated by a red, downward-
pointing arrow), continue with the lab steps to bring a tape drive UP using the
NetBackup Command Line (CLI).
Bringing a tape drive UP using the NetBackup Command Line (CLI)

6. Close the NetBackup Administration Console window that is connected to the
master server, lnxmaster.example.com.
7. Open a remote SSH session with your Linux-based master server,

lnxmaster.example.com.
To do so, locate and double-click the REMOTE SYSTEM ACCESS folder, located
on the desktop of console.example.com, to open the folder. Double-click the
Putty entry, in the REMOTE SYSTEM ACCESS folder. Next, in the PuTTY
Configuration window, double-click the entry for lnxmaster.example.com.
8. In the PuTTY window, log in to lnxmaster.example.com using the credentials

provided above.
9. In the lnxmaster PuTTY window, type the scan command, and press Enter.
Command: scan

The NetBackup-provided scan command displays the tape devices that are
visible to NetBackup at the operating system level.
Lab 1-67

10. If the output of the scan command shows no devices are visible to NetBackup,
reboot (restart) the lnxmaster.example.com system.
When the system has been restarted, access the PuTTY (root@lnxmaster)
window and repeat the scan command. If no devices are displayed in the
output of the scan command, notify your instructor.
If two tape drives and a media changer (robot) are displayed in the output of the
scan command, continue to the next step.
11. In the PuTTY window, type the tpconfig command using the command syntax shown
below, and press Enter.
The NetBackup-provided tpconfig command displays the tape devices (drives

and robots) that are configured to NetBackup and the current status of the
tape drives.
12. In the output of the tpconfig command, take note of the tape drive ID (displayed in
the left column of the command output)
The STATUS of the tape drives, and any additional messages that may be
displayed about the devices.
13. If the tape drives are DOWN, but there are no additional error messages displayed
for the drives, complete steps 14-17 that follow.
If there is an error message indicating a MISSING PATH for the tape drives, continue
to "Stopping and Restarting the NetBackup services" on the next page.
Lab 1-68

14. In the PuTTY window, type the vmoprcmd command to bring the first tape drive UP,
using the command syntax shown below, and press Enter.
15. In the PuTTY window, type the vmoprcmd command to bring the second tape drive
UP, using the command syntax shown below, and press Enter.
17. View the STATUS of the tape drives in the output of the tpconfig command, and
verify that the drives have a status of UP.
If the STATUS of the tape drives is now UP, continue to Exercise I-9: NetBackup Media.
If the tape drives are still DOWN, continue to the next lab steps to stop and restart
NetBackup.
Stopping and Restarting the NetBackup services

If the steps you have taken have not resulted in the tape drives being returned to the UP
status, it may be necessary to stop and restart the NetBackup services on the NetBackup
server system (in this case, lnxmaster.example.com).

18. In the lnxmaster PuTTY window, type the netbackup command, using the command
Command: netbackup stop
Lab 1-69

19. Wait for the command prompt to be returned before continuing. It may take a
The NetBackup-provided netbackup command, used with the stop option, is

used to stop the NetBackup processes on the NetBackup system on which the
command is executed.
20. In the PuTTY window, type the bpps command, using the command syntax shown
Command: bpps -a
21. In the output of the bpps command, verify that all the NetBackup processes have
been stopped.
If a NetBackup Administration Console has been left open and connected to

the master server, there will be a few processes that are not stopped on the
master server system. This is not a cause for concern. Continue to the next
step.
22. In the PuTTY window, type the netbackup command, using the command syntax
shown below, and press Enter.
Command: netbackup start
The NetBackup-provided netbackup command, used with the start option, is

used to start the NetBackup processes on the NetBackup system on which the
command is executed.
23. Wait for the command prompt to be returned before continuing. It may take a
24. In the PuTTY window, type the bpps command, using the command syntax shown
Command: bpps -a
25. View the output of the bpps command, and verify that the NetBackup processes
have been restarted on the master server.
Lab 1-70

Verifying that the tape drives are UP
Perform the steps below to verify that the tape drives are UP.
26. Access the open lnxmaster.example.com PuTTY window.

28. View the output of the tpconfig command and verify that the tape drives have a
STATUS of UP.
If the tape drives are not UP, as indicated in the output of the tpconfig
command, notify your instructor. Do not continue the lab activity until the tape
drives are UP.

30. Log in (if necessary) to console.example.com using the credentials provided above.
32. In the Administration Console login window, log in to your master server,
lnxmaster.example.com, using the Username, root, and the password, train.
33. Expand the Media and Device Management Entry in the left pane of the
Lab 1-71

34. Click the Device Monitor entry in the left pane of the Administration Console.
The right pane displays the configured tape drives.
35. Verify that the tape drives are in the UP state, as indicated by green, upward-
pointing arrows next to each of the tape drive entries.
36. If the tape drives are not UP, notify your instructor.
37. If the status of one or both tape drives is DOWN, seek assistance.
Continue to Exercise I-9: NetBackup Media.

Lab 1-72

Exercise I-9: NetBackup Media
In the steps that follow, you view the media-related items and tasks that are available
under the Media branch of the NetBackup Administration Console.
1. Expand the Media entry, located under Media and Device Management in the left
pane of the Administration Console. The figure below illustrates the results.
2. Click the Media entry.
The list of tapes that are currently configured in NetBackup is displayed in the right
Three tapes have been pre-configured for this training course.
Lab 1-73

Volume Pools
3. Expand the Volume Pools entry, located under Media in the left pane of the
Administration Console. The figure below illustrates the results.
NetBackup provides four default volume pools, including the CatalogBackup,

DataStore, NetBackup, and None volume pools.
4. Click the Volume Pools entry in the left pane of the Administration Console.
Detailed information about the default volume pools is displayed in the right pane of
the Administration Console, as illustrated in the figure below.
Continue to Exercise J: Initiating backup jobs using the NetBackup Administration

Console.
Lab 1-74

Exercise J: Initiating backup jobs using the
NetBackup Administration Console
In this exercise, you use pre-configured policies to initiate manual backup jobs that write
backup images to pre-configured storage unit destinations.
Continue to Exercise J-1: Initiating Manual Backup Jobs.

Lab 1-75

Exercise J-1: Initiating Manual Backup Jobs
In the steps that follow, you use the NetBackup Administration Console to initiate
backup jobs using pre-configured policies.
1. Access the NetBackup Administration Console on console.example.com.
2. Expand NetBackup Management in the left pane of the Administration Console.
3. Click the Policies entry, located under NetBackup Management.
4. The list of policies that were pre-configured for this course is displayed in the All
Policies pane at the center of the Administration Console user interface, as
illustrated in the figure below.
5. Click the entry for the PRE-clients-to-master-advdisk policy entry, and then, from
the Actions menu, select Manual Backup.
Actions > Manual Backup
You can also right-click the policy name, and click Manual Backup in the
resulting menu.
Lab 1-76

The Manual Backup window is displayed. The window lists the Schedules that are
available in the policy and the Clients that can be backed up using the policy.
In this example, a single schedule is listed in the Schedules list, and two client names
are listed in the Clients list of the Manual Backup window.
6. In the Manual Backup window, click the OK button without making a Client
selection.
By not selecting a specific client entry in the Manual Backup window and
clicking OK, a backup job is initiated for each client that is listed in the Clients
tab of the policy.
Proceed to Exercise K: Viewing and monitoring backup jobs using the Activity
Monitor.
Lab 1-77

Exercise K: Viewing and monitoring backup jobs
using the Activity Monitor
In the next steps, you access and use the NetBackup Activity Monitor to view the
progress of a backup job.
Proceed to Exercise K-1: Monitoring backup jobs.

Lab 1-78

Exercise K-1: Monitoring Backup Jobs
In this exercise, you will use the NetBackup Activity Monitor to view the progress of a
manual backup job.
1. Click the Activity Monitor entry in the left pane of the NetBackup Administration
Console.
The right pane displays the Activity Monitor that displays entries for jobs of all types
that have been performed recently.
By default, the Activity Monitor lists the jobs in descending numerical order,
with the most recent jobs listed first (at the top of the list).
If you click the heading of the Job ID column of the Activity Monitor, you can
change the order in which the jobs are listed. Click once to change the listing to
list jobs in ascending order – from oldest to newest. Click the Job ID column
heading again to change the job listing to descending order.
As a result of the manual backup that you initiated in the previous exercise of this
lab activity, two backup jobs were performed. These jobs are the most recent jobs
(have the highest-numbered Job IDs) listed in the Activity Monitor display.
In addition to Backup jobs, Image Cleanup jobs may also be displayed. The
Image Cleanup job type is described in more detail later in this course.
The figure below illustrates the type of entries you should see in the Activity
Monitor for the backup jobs you performed.
2. Take note of the job Type, State, Status, Job Policy, Job Schedule, and Client
information related to each of the backup jobs that were performed.
It is necessary to scroll to the right in the Activity Monitor to see some of the
information relating to the backup jobs.
3. Allow both Backup jobs to run to completion.
Lab 1-79

4. Verify that both backup jobs completed successfully. If one or both of the jobs
ended in a non-zero status, notify your instructor.
A completion status of “0” indicates that a job has completed successfully.
5. Double-click the entry for either of the backup jobs that were just performed – to
view detailed information about the job.
The Job Details window is opened for the selected job.
You can also access the Job Details by clicking on the entry for the job, and
then selecting Actions > Details.
The Job Details window contains three tabs – the Job Overview, Detailed
Status, and Job Hierarchy tabs.
6. Take a moment to browse the contents of the Job Details window – including the
Job Overview, Detailed Status, and Job Hierarchy tabs.
7. Click Close, to close the Job Details window.
8. If time permits, you may use the pre-configured policies to perform additional
backup operations and monitor the results using the Activity Monitor.
You have completed all the intended steps for this lab activity.
Lab 1-80

Lab 2: Configuring NetBackup storage
In this lab, you use the NetBackup Administration Console to configure a NetBackup
BasicDisk storage unit and a storage unit group.
Continue to Exercise A: Viewing disk storage on a NetBackup server system.
Lab 2-1

Exercise A: Viewing disk storage on a NetBackup
server system
In this exercise, you use tools provided by the operating system to view disk storage that
resides on your master server system.
Continue to the Exercise A-1: Viewing disk storage on a NetBackup Windows-based

master server system if you are performing this lab on a Windows system.
Continue to the Exercise A-2: Viewing disk storage on a NetBackup Linux-based master
server system if you are performing this lab on a Linux system.
Lab 2-2

Exercise A-1: Viewing disk storage on a NetBackup
Windows-based master server system
In this exercise, you connect to a remote Windows-based master server lab systems and
then review the disk storage information.
Windows-based systems in this lab environment.
2. If necessary, log in to the console.example.com system with the username,

3. Right-click on the REMOTE SYSTEM ACCESS folder then select Open from the
shortcut menu.
4. In the REMOTE SYSTEM ACCESS folder, right-click the RDP Profiles (Windows
systems) folder and select Open.
5. In the RDP Profiles (Windows systems) folder, right-click the RDP file,
(winmaster.rdp) and select Connect.
6. Log on to your master server using the credentials provided in the table below.
Operating System Master server name User Name Password

Lab 2-3

7. From the desktop of winmaster.example.com right-click on File Explorer and select
Open.
8. Take note of the disk volumes that are configured on this NetBackup server system.
Many of these have been configured in preparation for use as storage destinations
for NetBackup backup images. Take note specifically of the disk volume F:\ drive,
labelled as BASICDISK (F:).
9. Close the File Explorer window.
10. Close the RDP session to winmaster.example.com.
Continue to Exercise B: Configuring a BasicDisk storage unit.
Lab 2-4

Exercise A-2: Viewing disk storage on a NetBackup Linux-
based master server system
In this exercise, you connect to a remote Linux-based master server system using the
PuTTY shortcut located in the REMOTE SYSTEM ACCESS folder on the console system,
and then review the disk storage information.

3. From the desktop of the console.example.com system right-click on the REMOTE

SYSTEM ACCESS folder and select Open.
4. To connect to the Linux-based lab system, right-click the PuTTY shortcut and select
Open.
5. In the Saved Session pane select lnxmaster.example.com then click Open.
Within a moment a PuTTY window is displayed that will enable you to log in to
6. Log on to your Linux master server using the credentials provided in the table below.

lnxmaster.example.com User name: root Password: train
Lab 2-5

7. At the command prompt, type the command shown below, and press Enter.
Command: df -h
The output of the command is similar to that illustrated in the figure below.
The output of the command identifies the file systems and their associated
mount points on the lnxmaster system. Many of these file systems were pre-
configured to serve as storage destinations for NetBackup backup images.
8. Take note of the /dev/sda6 file system, and its associated mount point, /bdisk.
Continue to Exercise B: Configuring a BasicDisk storage unit.
Lab 2-6

Exercise B: Configuring a BasicDisk storage unit
In this exercise, you view basic disk storage unit settings associated with your master
server system. You then view disk storage associated with your media server. Lastly,
you create a disk storage unit associated with your media server system.
Continue to Exercise B-1: Viewing existing BasicDisk storage unit settings.

Lab 2-7

Exercise B-1: Viewing existing BasicDisk storage unit
settings
In this exercise, you log into the NetBackup Administration Console and view existing
BasicDisk storage unit settings.
2. If necessary, log on to the console.example.com system using the credentials

provided above.

If there is no open Administration Console window, locate and right-click the

NetBackup 8.1 Administration Console shortcut, then select Open. Enter the
Host name, User name, and Password in the Administration Console login
screen to connect to your master server. See the table below.
Master server name User Name Password

winmaster.example.com EXAMPLE\Administrator train
lnxmaster.example.com root train
4. View the top entry in the left pane of the Administration Console window to verify
that you are connected to your master server. See the figure below.
If the NetBackup Administration Console is not currently connected to your

master server, select File > New Console to launch a new Administration
Console login window, and log in to your master server.
Lab 2-8

5. Expand NetBackup Management in the left pane of the Administration Console.
6. Locate and expand the Storage entry, located under NetBackup Management in the
left pane of the Administration Console.
7. Click Storage Units, located under Storage in the left pane of the Administration
Console.
The right pane of the Administration Console displays the list of storage units that
have been pre-configured for this course, as illustrated in the figure below. All the
pre-configured storage units are associated with storage devices associated with
your master server (winmaster.example.com or lnxmaster.example.com).
8. Double-click the entry for the master_bdisk_stu to open the storage unit.
The Change Storage Unit window is opened, and displays the configuration settings
associated with the selected storage unit.
Lab 2-9

The table below identifies the storage unit configuration settings for this storage
unit.
Storage Unit parameter: Setting /value:

Storage unit name: master_bdisk_stu
Storage unit type: Disk
On demand only: not selected
Disk type: BasicDisk
Media server: winmaster.example.com
or
Absolute pathname to directory: F:\bdisk (Windows)
/bdisk (Linux)
Directory can exist of the root filesystem: not selected
Maximum concurrent jobs: 1
Reduce fragment size to: __ Megabytes not selected
High water mark: 98 %
Low water mark: 80 %
Enable Temporary Staging Area… not selected
9. Click Cancel to close the Change Storage Unit window without making changes to
the storage unit configuration.
If you are performing this lab on a Windows system, continue to the Exercise B-2:
Viewing a BasicDisk storage unit on a NetBackup Windows-based media server
system.
If you are performing this lab on a Linux system, continue to the Exercise B-3:
Viewing a BasicDisk storage unit on a NetBackup Linux-based media server system.
Lab 2-10

Exercise B-2: Viewing a BasicDisk storage unit on a
Windows media server system
In this lab exercise you will connect to a remote Windows-based media server system
using Remote Desktop. An RDP profile for the system is located in the REMOTE SYSTEM
ACCESS folder on the console.example.com. Then, you review the disk storage
information on that system.

3. Locate and right-click the REMOTE SYSTEM ACCESS folder and select Open.
4. Right-click the RDP Profiles (Windows system) folder and select Open.
5. When the RDP Profiles (Windows system) folder is opened, right-click the
winmedia.rdp file, the select Connect.
Within a moment a Windows Security window is displayed, that will enable you to
log in to winmedia.example.com.
6. Log on to your Windows-based media server using the credentials provided in the
table below.

Windows-based winmedia.example.com EXAMPLE\Administrator train
winmedia.example.com User name: EXAMPLE\Administrator Password: train
Lab 2-11

7. Use the File Explorer on Windows to view the drives (names/letters that have been
configured on your Windows media server.
8. Take note of the information associated with the disk drive (drive letter) that has
been configured for use as the destination for BasicDisk backups. The names of the
disk volumes should enable you to identify the correct drive.
System name Drive Name (Letter) for BasicDisk storage

winmedia.example.com BASICDISK (F:)
9. Use the File Explorer to view the contents of the drive listed in the table above, to
verify that the drive currently contains no data files or directories.
The disk drive or file system that is the target for a NetBackup disk-based
storage unit (such as Basic Disk or AdvancedDisk) should not be used to store
non-NetBackup data.
10. Close the RDP session to winmedia.example.com.
Continue to Exercise B-4: Configuring a Basic Disk Storage Unit.

Lab 2-12

Exercise B-3: Viewing a BasicDisk storage unit on a Linux
media server system
In this lab exercise you will connect to a remote Linux-based media server lab systems
and then review the disk storage information.

3. Locate and right-click the REMOTE SYSTEM ACCESS folder on the desktop of the
console.example.com system, then select Open.
4. To open an SSH session with the Linux-based system, lnxmedia.example.com, right-

click the Putty shortcut and select Open.
Within a few moments a PuTTY Configuration window will be displayed.
5. From the Saved Sessions pane select the entry for lnxmedia.example.com then click
Open.
6. Log on to your Linux-based media server using the credentials provided in the table
below.

Linux lnxmedia.example.com root train
lnxmedia.example.com Username: root Password: train
7. At the command prompt on lnxmedia.example.com, execute the ‘df’ command to

view the file systems and mount points that have been configured on the Linux-
based media server system.
Command: df -h
Lab 2-13

8. Take note of the information associated with the file system/mount point that has
been configured for use as the destination for BasicDisk backups .
File system and mount point for BasicDisk storage on lnxmedia.example.com

Linux (lnxmedia.example.com) /dev/sda6 (file system) -- /bdisk (mount point)
The names of the mount points should enable you to identify the mount point
that is configured for use as BasicDisk storage.
9. Use the ‘ls’ command to view the contents of the mount point you listed in the
table above, to verify that the drive or file system currently contains no data files or
directories.
Command: ls -l /bdisk
The disk drive or file system that is the target for a NetBackup disk-based
storage unit (such as Basic Disk or AdvancedDisk) should not be used to store
non-NetBackup data.
Continue to Exercise B-4: Configuring a Basic Disk Storage Unit

Lab 2-14

Exercise B-4: Configuring a Basic Disk Storage Unit
In the steps that follow, you use the NetBackup Administration Console to configure a
Basic Disk Storage Unit associated with your media server system (either
winmedia.example.com or lnxmedia.example.com).
1. Access the desktop of your console.example.com system.
2. Access the NetBackup Administration Console window that is open on

3. Expand NetBackup Management and select Storage Units in the left pane of the
NetBackup Management > Storage > Storage Units
4. Select Actions and then select the option to create a new Storage Unit in the
Administration Console tool bar.
Actions > New > Storage Unit
The New Storage Unit window is displayed.
Continue to next page.

Lab 2-15

5. Use the parameters provided in the table to create a new BasicDisk storage unit.
Select the storage unit parameters based on you preferred Operating System. If
you are using winmaster.example.com as your master server, use the
Windows-based parameters. If you are using lnxmaster.example.com as your
master server, use the Linux-based parameters.
Storage Unit parameter: Setting / value:

Storage unit name: media_bdisk_stu
Storage unit type: Disk
On demand only: Not selected (default)
Disk type: BasicDisk
Media server: winmedia.example.com
or
lnxmedia.example.com
Absolute pathname to directory: F:\ (Windows)
/bdisk (Linux)
Directory can exist of the root filesystem: not selected (default)
Maximum concurrent jobs: 1 (default)
Reduce fragment size to: __ Megabytes not selected (default)
High water mark: 98 % (default)
Low water mark: 80 % (default)
Enable Temporary Staging Area. not selected (default)
6. Click OK to save the new storage unit settings.
7. Verify that the new media_bdisk_stu storage unit is visible in the list of storage units
that is displayed in the right pane of the NetBackup Administration Console.
Your storage unit results should be similar to those illustrated in the figure below.
Continue to Exercise C: Configuring a storage unit group.
Lab 2-16

Exercise C: Configuring a storage unit group
In this lab, you will use the NetBackup Administration Console to create a storage unit
group.
Continue to Exercise C-1: Configuring a storage unit group.

Lab 2-17

Exercise C-1: Configuring a storage unit group
In this exercise, you log into the NetBackup Administration Console and create a
storage unit group.
2. Navigate to Storage Unit Groups under NetBackup Management in the left pane of
the Administration Console.
NetBackup Management > Storage > Storage Unit Groups
With the Storage Unit Groups entry selected, the right pane of the Administration
Console displays any storage unit groups that have been configured.
By default, no storage unit groups are configured in NetBackup. One storage

unit group, master_disk-tape_stugroup has been pre-configured for this
course.
3. Select Actions and then create a new Storage Unit Group in the Administration
Console tool bar.
Actions > New > Storage Unit Group
The New Storage Unit Group window is displayed.

4. Use the parameters provided in the table below to configure the new storage unit
group.
Storage Unit Group parameter Setting / value

Storage unit group name: bdisk-tape_stugroup
Storage unit group configured for: Backup (default)
Storage units to be used in the group: master_bdisk_stu (first)
media_bdisk_stu (second)
master_tape_stu (third)
Storage unit selection: Prioritized
Lab 2-18

5. After entering the storage unit group parameters, click OK to save the storage unit
group.
6. Verify that the bdisk-tape_stugroup entry has been added to the list of storage unit
groups displayed in the right pane of the Administration Console.
Your results should be similar to those illustrated in the figure below.
7. Allow the NetBackup Administration Console window to remain open on the

console.example.com system.
You have completed all tasks for this lab activity.

Lab 2-19

Lab 3: Configuring Policies and Schedules
In this lab, you use the NetBackup Administration Console to configure NetBackup
policies and schedules to perform backups of client file systems to pre-configured
storage destinations. The slide describes the high-level tasks to be performed.
Proceed to Exercise A: Configuring a NetBackup policy.
Lab 3-1

Exercise A: Configuring a NetBackup policy
In this exercise, you will use the NetBackup Administration Console to manually
configure a policy to perform both full and incremental backups of a client’s file
systems.
To accomplish these tasks, you will:
• Access the NetBackup Administration Console window on console.example.com,

and log in to your NetBackup master server.
• Create a new policy.
• Configure the policy Attributes using a set of provided parameters.
• Configure policy Schedules to perform full and incremental backups using sets of
provided schedule parameters.
• Configure the policy Clients using a set of provided parameters.
• Configure the policy Backup Selections using a set of provided parameters.
• Save the policy, and verify the new policy exists in the list of NetBackup policies.
Proceed to Exercise A-1: Accessing the NetBackup Administration Console.

Lab 3-2

Exercise A-1: Accessing the NetBackup Administration
Console
2. If necessary, log on to the console system using the userid and password,
EXAMPLE\Administrator, train.

console.example.com. (If no Administration Console window is open, see the Note
below.)
If there is no open Administration Console window, locate and double-click the

NetBackup 8.0 Administration Console icon, located on the desktop of the
console system, to launch the NetBackup Administration Console. Then, enter
the Host name, User name, and Password in the Administration Console login
screen to connect to your master server. See the table on the next page.

that you are connected to your master server.
5. If the NetBackup Administration Console is not currently connected to your master

server, launch a new instance of the NetBackup Administration Console and
connect the Administration Console to your master server.
File > Change Server
Continue to Exercise A-2: Creating a policy.
Lab 3-3

Exercise A-2: Creating a policy
1. From the NetBackup Administration Console select the Policies entry, located
under NetBackup Management in the left pane.
1. From the All Policies pane, right-click in the white area and select New Policy.
The Add a New Policy dialog box is displayed.
2. Type the name of the new policy, LAB03-clients-to-master-bdisk, in the Policy name
field of the Add a New Policy dialog box.
3. Click OK to continue.
The Add a New Policy dialog box is closed, and the LAB03-clients-to-master-bdisk
policy is opened in the Change Policy window.
Continue to Exercise A-3: Configuring policy attributes.
Lab 3-4

Exercise A-3: Configuring policy Attributes
The Attributes tab of the policy is selected by default
This policy will be used to back up the clients that reside on your master and media
server systems respectively, as identified in the table below.
OS preference First client host name Second client hostname

Windows-based winmaster.example.com winmedia.example.com
Linux-based lnxmaster.example.com lnxmedia.example.com
1. Use the values from the appropriate column of the table below (based on your OS
preference), and enter the parameters in the Attributes tab of the policy.
Parameter Setting: Windows Setting: Linux

Policy type: (based on OS of clients) MS-Windows Standard
Policy storage: master_bdisk_stu master_bdisk_stu
--All other Attribute parameters-- Use default settings Use default settings
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.
2. Review the changes you have made to the policy Attributes and verify that they are
configured as intended (based on the table above).
Continue to Exercise A-4: Configuring policy schedules.

Lab 3-5

Exercise A-4: Configuring policy Schedules
1. Click the Schedules tab of the LAB03-clients-to-master-bdisk policy.
2. When the Schedules tab contents are displayed, click New to create a new schedule.
3. Enter the values for the schedule in the Attributes, Start Window, and Exclude
Dates tabs of the schedule, as indicated in the table below.
Schedule Attributes parameter Setting

Name: full_frequency
Type of backup: Full Backup
Schedule type: Frequency
Frequency setting 6 hours
Retention 1 month
All other schedule Attribute parameters: Use default settings
Start Window parameter Setting
Start day: Use today’s day (e.g. Monday)
Start time: 22:00:00 (10PM)
End day: Use tomorrow’s day: (e.g. Tuesday)
End time: 02:00:00 (2AM)
--All other Start Window parameters: Use default settings
Exclude Dates parameter Setting
---All Exclude Dates parameters-- Use default settings
4. Click OK in the Add Schedule window to save the schedule.

5. Verify that an entry for the full_frequency schedule is visible in the list of schedules
displayed in the Schedules tab.
The figure on the next page illustrates the entry for the full_frequency schedule.
Lab 3-6

The colored lines (representing the start windows for various types of
schedules) in the top half of the Schedules tab may not initially appear when
you save the schedule. Click the Attributes tab, and then immediately return to
the Schedules tab. The colored lines should now be visible.
6. Click New to create another schedule.
7. Enter the values for the schedule in the Attributes, Start Window, and Exclude
Dates tabs, as indicated in the table below.

Name: diffincr_frequency
Type of backup: Differential Incremental Backup
Frequency setting 3 hours
Retention 2 weeks
Start day: Use tomorrow’s day (e.g. Tuesday)
Start time: 22:00:00 (10PM)
End day: Tomorrow’s day +1: (e.g. Wednesday)
End time: 00:00:00 (midnight)
All other Start Window parameters: Use default settings
All Exclude Dates parameter Use default settings
8. Click OK in the Add Schedule window to save the schedule.
Lab 3-7

9. Verify that an entry for the diffincr_frequency schedule you created is visible in the
list of schedules displayed in the Schedules tab
The figure below illustrates entries for the full_frequency and diffincr_frequency
schedules.
You can hold the SHIFT key down and select both schedules to see a graphical
representation of both the start windows.
The colored lines (representing the start windows for various types of
schedules) in the top half of the Schedules tab may not initially appear when
you save the schedule. Click the Attributes tab, and then immediately return to
the Schedules tab. The colored lines should now be visible.
Continue to Exercise A-5: Modifying a schedule.

Lab 3-8

Exercise A-5: Modifying a schedule
1. Double-click the entry for the diffincr_frequency schedule (or click the entry for the
schedule and then click Change), to open the schedule.
2. Click the Start Window tab of the schedule. The figure below illustrates the current
Start Window settings for the schedule.
As currently configured, differential incremental backup jobs are allowed to start

between Tuesday, at 10PM (22:00:00), and midnight (Wednesday, 00:00:00).

Lab 3-9

3. Modify the Start Window settings for the diffincr_frequency schedule, so that
differential incremental backups are allowed to run on the days and times indicated
in the table below.
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)
Thursday 10PM (22:00:00) Friday midnight (00:00:00)
Friday 10PM (22:00:00) Saturday midnight (00:00:00)
Hint: 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.
After modifying the schedule, the Start Window tab contents should appear as
Lab 3-10

4. Click OK to save the diffincr_frequency schedule and to close the Change Schedule
window.
After modifying and saving the schedule, the Schedules tab should appear as illus-
trated in the figure below.
Continue to Exercise A-6: Adding clients to the policy.

Lab 3-11

Exercise A-6: Adding clients to the policy
In the next steps, you add clients to the LAB03-clients-to-master-bdisk policy.
1. Click the Clients tab of the policy.
2. Click the New button.
The Add Client window is displayed.
3. Enter the information for the first client – the client that resides on your master
server – using the information provided in the table below.
The Client Name field is a simple text field and will not check for validity of the name
entered. Ensure the correct FQDN of the client is entered.
OS preference First client host name Detect client operating system

Windows-based winmaster.example.com checkbox selected
Linux-based lnxmaster.example.com checkbox selected
Check the Detect client operating system box to cause 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.
4. After entering the information for the first client, click Add to add the first client,
and enable you to add the second client. Add the second client – the client on your
media server – using the information provided in the table below.
OS preference Second client host name Detect client operating system

Windows-based winmedia.example.com checkbox selected
Linux-based lnxmedia.example.com checkbox selected
5. After entering the information for the second client, click OK to save the client
information and close the Add Client window.
Lab 3-12

6. Verify that entries for two clients – the clients on your master and media server
systems – are displayed in the Clients tab of the policy before continuing, as
7. Take note of the contents of the Hardware and Operating System columns in the
Clients tab. The information in these columns was automatically determined by
NetBackup by querying the client system.
Continue to Exercise A-7: Adding Backup Selections to a policy.

Lab 3-13

Exercise A-7: Adding Backup Selections to a policy
In the next steps, you add backup selections to the LAB03-clients-to-master-bdisk

policy.
1. Click the Backup Selections tab of the policy.
2. Click New to begin adding backup selections to the policy.
The Add Backup Selection window is displayed.
3. Use the information provided in the table below to set the Pathname or directive
set.
Client OS Pathname or directive set List of pathnames…

Windows-based Windows E:\data
Linux-based --not applicable-- /data

Lab 3-14

4. The pathname may be selected by clicking the Browse button and selecting the
desired path from one of the available clients, as illustrated in the figure below.
Any available client may be browsed. In your lab environment, the sample data
is present on all systems.
The Add button is initially greyed out. Entering a path in the Pathname or
directive text box activates the Add button to allow you to save the Pathname
or directive entry.
5. After selecting the Backup Selections, click OK to close the Browse window.
6. Click OK to save the backup selections, and to close the Add Backup Selections
window.
You have added all parameters for the policy.
7. Select each of the policy tabs – Attributes, Schedules, Clients, and Backup
Selections – and briefly verify the contents of each tab.
Lab 3-15

8. Click OK to save the policy, and to close the Change Policy window.
9. Verify that an entry for the LAB03-clients-to-master-bdisk policy is visible in the All
Policies window of the Administration Console, as illustrated in the figure below.
Continue to Exercise B: Configuring a policy to use calendar-based schedules.

Lab 3-16

Exercise B: Configuring a policy to use calendar-
based schedules
In this exercise, you use the NetBackup Administration Console to configure a policy
that uses calendar-based schedules to perform client backups.
Continue to Exercise B-1: Configuring the policy Attributes.

Lab 3-17

Exercise B-1: Configuring the policy Attributes
Configure the LAB03-console-to-master-advdisk policy to back up the client named

console.example.com. The console system is running the Windows Server 2012 R2
Enterprise operating system.
1. Click Policies in the left pane of the NetBackup Administration Console.
2. In the Administration Console tool bar under Actions, select the option to create a
new policy.
Actions > New > Policy
3. Type the name of the new policy, LAB03-console-to-master-advdisk, in the Policy

Name field, and click OK.
The Change Policy: LAB03-console-to-master-advdisk window is displayed.
4. Enter the parameter values listed in the table below in the appropriate fields of the
Attributes tab of the policy.
Parameter Parameter/Setting:
Policy type: (based on OS of client) MS-Windows
Policy storage: master_advdisk_stu
--All other Attribute parameters-- Use default settings
5. Review the changes you have made to the policy Attributes and verify that they are
configured as intended.
Continue to Exercise B-2: Configuring policy Schedules.
Lab 3-18

Exercise B-2: Configuring policy Schedules
Configure the LAB03-console-to-master-advdisk policy Schedules.
1. Click the Schedules tab of the LAB03-console-to-master-advdisk policy.
2. When the Schedules tab is displayed, click New to create a new schedule.
The Add Schedule window is displayed.
3. Enter the values for the schedule in the Attributes, Start Window, Exclude Dates,
and Include Dates tabs of the schedule, as indicated in the table below.

Name: full_calendar_tuesday
Schedule type: Calendar
Retries allowed after runday not selected (default)
Retention 1 month
Start day: Tuesday
Start time: 02:00:00 (2AM)
End day: Tuesday
End time: 05:00:00 (5AM)
--All other Start Window parameters: Use default settings
Recurring Week Days none selected (none excluded)

Recurring Days of the Month Exclude “Last Day”
Include Dates parameter Setting
Recurring Week Days Mark each Tuesday of the month
Recurring Days of the Month none selected
Any dates that are selected in the Exclude Dates tab are automatically
displayed with the red not symbol in the Include Dates tab of the schedule.
This is so you can see if there is a conflict of dates.
Lab 3-19

4. Click Add to save the full_calendar_tuesday schedule, and to add another schedule
to the policy.
A new Add Schedule window is displayed.
5. Enter the values for the schedule in the Attributes, Start Window, Exclude Dates,
and Include Dates tabs, as indicated in the table below.

Name: diffincr_calendar_weekdays
Schedule type: Calendar
Retention 1 month
Start day: Each weekday (Monday-Friday)
Start time: 02:00:00 (2AM)
End day: Each weekday (Monday-Friday)
End time: 05:00:00 (5AM)
--All other Start Window parameter: Use default settings
Recurring Week Days - Exclude every Tuesday of month
Recurring Days of the Month - Exclude “Last Day”
Include Dates parameter: Setting
Recurring Week Days - Mark each Monday of the month
- Mark each Wednesday of the month
- Mark each Thursday of the month
- Mark each Friday of the month

- Remove the checkboxes from Tuesday
Recurring Days of the Month none selected
6. Click Add to save the diffincr_calendar_weekdays schedule.
Lab 3-20

7. Add a third schedule to the policy using the information provided in the table on the
next page.

Name: full_manual
Schedule type: Frequency, 1 week
Retention 1 month
Start Window parameter Accept all default settings
Exclude Dates Accept all default settings
8. Click OK to save the full_manual schedule.
9. Verify that the three schedules you are configured are visible in the Schedules tab of
the LAB03-console-to-master-advdisk policy.
Continue to Exercise B-3: Adding Clients to the policy.

Lab 3-21

Exercise B-3: Adding Clients to the policy
Configure the LAB03-console-to-master-advdisk policy Clients.
1. Click the Clients tab of the policy.
2. Click the New button, located on the Clients tab screen.
The Add Client window is displayed.
3. Enter the information for the client, using the information provided in the table
below.
Client host name Client hardware and OS

console.example.com Windows x64, Windows
You may use the Detect client operating system checkbox to cause NetBackup
to automatically discover the hardware and operating system of the client.
4. Click OK to save the client information and close the Add Client window.
5. Verify that the entry for the console.example.com client is visible in the Clients tab
of the policy before continuing to the next step.
Continue to Exercise B-4: Adding Backup Selections to the policy.

Lab 3-22

Exercise B-4: Adding Backup Selections to the policy
Configure the LAB03-console-to-master-advdisk policy Backup Selections.
2. Click the New button.
The Add Backup Selection window is displayed.
3. Use the information provided in the table below to add a backup selection.
Pathname or directive set List of pathnames…

Windows E:\data
4. After entering the backup selection, click OK to save the backup selection and to
close the Add Backup Selection window.
5. View the contents of each of the tabs of the LAB03-console-to-master-advdisk

policy to verify the contents of the policy.
6. Click OK to save the policy and to close the Change Policy window.
7. Verify that the entry for the LAB03-console-to-master-advdisk policy is visible in the
All Policies pane of the NetBackup Administration Console.
Continue to Exercise C: Copying a policy to create a new policy.

Lab 3-23

Exercise C: Copying a policy to create a new policy
The NetBackup Administration Console provides a simple method of creating a new

policy, by copying an existing policy. The new policy can then be modified as needed. In
this exercise, you use that method to create a new policy.
Continue to Exercise C-1: Copying an existing policy.

Lab 3-24

Exercise C-1: Copying an existing policy
In this exercise, you will copy an existing policy to a new policy and change the policy
parameters.
1. Right-click the entry for the LAB03-clients-to-master-bdisk policy in the All Policies
2. Select Copy to New… from the resulting menu, as illustrated in the figure below.
3. When the Copy a Policy dialog box is displayed, enter the policy name, LAB03-
clients-to-master-disk-tape-stugroup, in the New Policy field, and click OK.
The new LAB03-clients-to-master-disk-tape-stugroup policy is opened for editing in

the Change Policy window.
4. Change the Policy Storage parameter on the Attributes tab, so that backups are
written by this policy to the master_disk-tape_stugroup.
Lab 3-25

5. Modify the diffincr_frequency schedule of the policy to create a 2 hour frequency
and a Start window of 24 hours per day and 7 days a week.
Attributes tab: Setting:

Frequency: 2 hours (edit the schedule to change this setting)
All other Attribute settings: no changes
Start Window tab: Setting:
Start day: Sunday (change to this)
End day: Monday (change to this)
Start time: 00:00:00 (change to this)
End time: 00:00:00 (change to this)
Select the Friday schedule then click Duplicate to
copy the schedule for the whole week, creating a
24/7 schedule.
6. After making the changes to the schedule, click OK to save the schedule.
7. Allow all other policy Attributes, Schedules, Clients, and Backup Selections
parameter settings to remain at their current settings.
8. Click OK to save and close the LAB03-clients-to-master-disk-tape-stugroup policy.
9. Verify that the LAB03-clients-to-master-disk-tape-stugroup policy is visible in the

list of policies in the All Policies pane, as illustrated in the figure below.
You have completed all required exercises for this lab activity.
Lab 3-26

If you wish, you can click the link to continue to the optional lab exercise, Exercise D:
Optional Lab challenge.
Lab 3-27

Exercise D: (Optional) Lab challenge
In this optional lab exercise, you test your ability to design and configure a NetBackup
policy that will achieve a set of desired outcomes.
There are many ways to meet the requirements of the scenario presented in
this challenge lab – especially with regard to the backup schedules that can be
created to meet the stated requirements. The schedules that you created may
not be identical to the possible scheduling options presented in the examples
provided.
Continue to Exercise D-1: Challenge scenario.

Lab 3-28

Exercise D-1: Challenge scenario
An executive in your organization has submitted a requirement that file system data on
an important Windows 2012 R2 Server-based system (console.example.com) must be
backed up.
The request specified daily backups of the entire data volume, and the ability to recover
file system data for up to one month. The recovery point objective for the system
requires that no more than one hour of data loss can be tolerated. The rate of change of
the data on the file system is about 15 percent per day. Most of the change occurs
during business hours, 7AM-7PM, Monday-Friday. As an additional requirement, the
administrator of that system has requested the ability to initiate backups of the data on
the server during business hours only. By policy, department users cannot be given
access to the NetBackup Administration Console to initiate manual backups. Because of
the priority given by your organization to reducing disk storage used for storing backup
images, you write all production backups to deduplication storage. Your team has not
finished building out the NetBackup configuration, but the disk backup storage needed
to meet this request has already been configured. Your task is to configure NetBackup
to perform backups of the DATA volume of the server to meet these requirements –
using deduplication backup storage that has already been configured.
Continue to Exercise D-2: Challenge summary.

Lab 3-29

Exercise D-2: Challenge summary
The following information is a list of high-level tasks that must be completed to

successfully complete this challenge.
• Data resides on Windows 2012 R2 Server system

• Client name is console.example.com
• Data to protect is file system data on the DATA volume (E:\data)
• Backup of entire data volume is required daily
• Data volume rate of change is up to 15 percent per day
• Data must be recoverable for up to one month
• Data change occurs primarily during business hours (7AM-7PM), Monday-Friday
• Recovery point objective is maximum of one hour
• Ability for user to initiate backups is required
• Backup data is written to deduplication storage that is already configured
Continue to Exercise D-3: Challenge policy Attributes.

Lab 3-30

Exercise D-3: Challenge policy Attributes
The policy name

Create a policy using the name, LAB03-challenge, that satisfies the outcomes identified
in the challenge scenario and challenge summary on the previous pages.
Policy Attributes
What we know about the policy Attributes from the provided challenge scenario:
• The critical data is stored on a file system (DATA volume) on the server.
• The client is Windows-based, so the Policy type for this file system is MS-Windows.
• Backup images must be written to deduplication storage (MSDP).
Other policy Attributes may apply, but are not defined in this example.
The figure below illustrates an example of the policy Attributes.

Continue to Exercise D-4: Challenge policy Schedule options.
Lab 3-31

Exercise D-4: Challenge policy Schedule options
Policy Schedules
Various scheduling methods can satisfy the requirements of the challenge scenario.
These are a few examples of different types of schedules to accomplish the backups
necessary to meet the requirements of the LAB03-challenge policy.
Frequency-based schedules - Example 1:

̶ Daily frequency-based full backup – 7 days/week – 1 month retention (off-hours)
̶ Hourly frequency-based incremental backup – 24 hours/day – 1 month retention
Calendar-based schedules – Example 2:

̶ Daily calendar-based full backup – 7 days/week – 1 month retention (off-hours)
̶ Hourly frequency-based incremental backup – 24 hours/day – 1 month retention
User backup schedule – Examples 1 and 2:

̶ User backups - Monday-Friday - 7AM-7PM – 1 month retention.
Other scheduling options could be used to meet the requirements of this

challenge scenario.
The pages that follow illustrate examples of various scheduling methods that satisfy the
requirements of the LAB03-challenge scenario.
Continue to Exercise D-5: Challenge schedule example 1.

Lab 3-32

Exercise D-5: Challenge schedule example 1
Frequency-based schedule list – used in example 1

This scheduling example uses the following combination of schedules to meet the
customer requirements:
• Daily frequency-based full backup – 7 days/week – 1 month retention (off-hours)

• Hourly frequency-based incremental backup – 24 hours/day – 1 month retention
• User-backup schedule enables user backups – Monday-Friday – 7AM-7PM

challenge scenario
The schedules in this example are illustrated below on this and the following pages.
The schedules shown in the image could be used to meet the requirements of the
LAB03-challenge scenario.
Continue to Exercise D-6: Challenge frequency-based schedules.
Lab 3-33

Exercise D-6: Challenge frequency-based schedules
The figure below illustrates the frequency-based full_frequency schedule Attributes.

The full_frequency schedule performs automated Full Backups of the client one time
per day. The backup images that are created are retained for one month.
Lab 3-34

The figure below illustrates the Start Window for the full_frequency schedule. The
full_frequency schedule allows the automatic initiation of backups between midnight
(00:00:00) and 2AM (02:00:00), Sunday-Saturday.

Lab 3-35

Schedule example 1: Frequency-based schedules (continued)
The figure below illustrates the frequency-based Full_Backup schedule Exclude Dates.

Lab 3-36

The figure below illustrates the frequency-based Differential Incremental schedule
Attributes. The diffincr_frequency schedule performs an automated Differential
Backup of the client once per hour. The backup images created are retained for one
month.
Lab 3-37

The figure below illustrates a Differential Incremental schedule Start Window.

Lab 3-38

The figure below illustrates frequency-based Differential Incremental schedule Exclude
Dates.

Lab 3-39

The figure below illustrates the Attributes for a User Backup schedule.

Lab 3-40

The figure below illustrates the Start Window for a User Backup schedule.
Continue to Exercise D-7: Challenge schedule example 2.

Lab 3-41

Exercise D-7: Challenge schedule example 2
Calendar + Frequency schedules

This scheduling example uses the following combination of schedules to meet the
customer requirements:
• Daily calendar-based full backup – All days of month – 1 month retention (00-02AM)
• Hourly frequency-based incremental backup – 24 hours/day – 1 month retention
• User-backup schedule enables user backups – Monday-Friday – 7AM-7PM

challenge scenario.
The schedules in this example are illustrated below on this and the following pages.
Lab 3-42

Schedule example 2: Calendar + Frequency schedules (continued)
The figure below illustrates the Attributes for a calendar-based Full Backup schedule.
The full_calendar_daily schedule performs an automated Full Backup of the client once
per day. The backup images created are retained for one month.

Lab 3-43

The figure below illustrates the Start Window for a calendar-based Full Backup
schedule. The full_calendar_daily schedule Start Window allows automated backups to
be initiated between midnight (00:00:00) and 2AM (02:00:00), Sunday-Saturday (each
day).

Lab 3-44

The figure below illustrates the Include Dates for a calendar-based Full Backup.
Automatic backups are enabled for each day using the full_calendar_daily schedule.

Lab 3-45

The figure below illustrates the Exclude Dates for a calendar-based Full Backup
schedule. No dates are excluded for automated backups using the full_calendar_daily
schedule.

Lab 3-46

The figure below illustrates Attributes for a frequency-based Differential Incremental
schedule. The diffincr_frequency schedule performs an automated Differential Backup
of the client once per hour. The backup images created are retained for one month.

Lab 3-47

The figure below illustrates the Start Window of a Differential Incremental schedule.

Lab 3-48

The figure below illustrates the Exclude Dates of a Differential Incremental schedule.

Lab 3-49

The figure below illustrates the Attributes of a User Backup schedule. The user_backup
schedule enables user-initiated backups. The resulting backup images are retained for
one month.

Lab 3-50

The figure below illustrates the Start Window of a User Backup schedule.
Continue to Exercise D-8: Challenge policy Clients.

Lab 3-51

Exercise D-8: Challenge policy Clients
Policy Clients
Information about the client for this policy is provided in the challenge scenario:
• The client name is console (console.example.com).

• The console system is running Windows 2012 Server (Windows-x64).
The figure below illustrates the Clients tab for the policy that meets the lab challenge
requirements.
Continue to Exercise D-9: Challenge policy Backup Selections.

Lab 3-52

Exercise D-9: Challenge policy Backup Selections
Policy Backup Selections

The backup selection information for the policy can be determined from the information
provided in the challenge scenario:
• The data to be protected resides in E:\data.

• No additional folder or file exclusions or inclusions are noted.
The figure below illustrates the Backup Selections tab for the policy that meets the lab
challenge requirements.
Continue to Exercise D-10: Deactivate the LAB03-challenge policy.

Lab 3-53

Exercise D-10: Deactivate the LAB03-challenge policy
To prevent the LAB03-challenge policy from initiating a large number of Differential

Incremental Backup jobs, perform the following steps to deactivate the policy.
console.example.com
2. Select Policies in the left pane of the NetBackup Administration Console.
The list of policies that are configured on your master server is displayed in the All
Policies pane of the Administration Console.
3. Click the entry for the LAB03-challenge policy.
4. Select Actions then Deactivate, to deactivate the policy.
Take note that the entry for the LAB03-challenge policy in the All Policies pane is
marked with a red X, and that the entry for the policy is greyed-out.
A policy that is deactivated cannot be used to perform backup operations.

You have completed all exercises for this lab activity.
Lab 3-54

Lab 4: Performing File System Backups
In this lab, you perform tasks to initiate and monitor NetBackup file system backups.
Some of the exercises in this lab contain steps that are dependent upon the
completion of LAB 03. Please make sure you have completed LAB 03 before
continuing.
Proceed to Exercise A: Using the Activity Monitor.
Lab 4-1

Exercise A: Using the Activity Monitor
A manual backup is an administrator-initiated backup operation that uses a specific

policy. In the steps that follow, you take steps to initiate a manual backup operation.
Continue to Exercise A-1: Viewing jobs in the Activity Monitor.

Lab 4-2

Exercise A-1: Viewing jobs in the Activity Monitor

console.example.com. (If no Administration Console window is open, see the Note.)

NetBackup 8.1 Admin Console shortcut, located on the desktop of
console.example.com, to launch the NetBackup Administration Console.
Then, enter the Host name, User name, and Password in the Administration
Console login screen to connect to your master server. See the table below.

3. View the top entry in the left pane of the NetBackup Administration Console, and
verify that the name of your master server is displayed there.
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.
In this exercise, you perform steps to become familiar with the layout and use of the
NetBackup Activity Monitor.
Lab 4-3

5. Click the Activity Monitor entry in the left pane of the NetBackup Administration
Console.
The Activity Monitor is displayed in the right pane of the Administration Console.
Note that there are four tabs, located at the bottom of the Activity Monitor pane.
6. Take note of the names of the additional Activity Monitor tabs as shown in the table
below.
Tab Name
Jobs
Daemons
Processes
Drives
When you access the Activity Monitor, the Jobs tab is selected by default.
7. Scroll down through the jobs that are listed in the Jobs tab of the Activity Monitor.
It is likely that the only job types that are currently displayed in the Activity Monitor
are Backup and Image Cleanup job types. However, the jobs listed in the Activity
Monitor > Jobs tab may vary substantially. This is expected.
The figure below 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.
Continue to Exercise A-2: Modifying the job sort order.
Lab 4-4

Exercise A-2: Modifying the job sort order
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.
Sorting the job list by Job ID

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.
1. From the Activity Monitor, select any job.
2. Under the View tool bar option, select Columns then Size to Data.
This expands all the columns so that the full contents can be viewed.
View > Columns > Size to Data.
3. 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).
4. Verify that the jobs are now listed in ascending order.

5. 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.
6. Verify that the jobs are now listed in descending order.
Lab 4-5

Sorting the job list by Job Policy name
You can sort the order in which jobs are listed in the Activity Monitor based upon the
name of the Job Policy that was used to perform the job.
Sorting by use of the Job Policy name 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 Job
Policy. Those jobs are either listed first (when sorting jobs is ascending order by the Job
Policy name), or last (when sorting jobs by descending order by the Job Policy name).
Jobs are not normally sorted according to their Job Policy name – but rather by
their Job ID. There may be situations where sorting jobs by their Job Policy
name is desirable.
7. Click the heading of the Job Policy column of the Activity Monitor to sort the job list
by the Job Policy name.
Take note of the order in which the jobs are listed.
8. Click the heading of the Job Policy 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.
9. Click the heading of the Job ID column to return to sorting the jobs according to
their Job IDs.
10. 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).
11. Select View from the menu then select Sort.
You can also right-click on a job in the Activity Monitor and select Sort from the
shortcut menu.
12. From the Sort window click Clear All then click OK to close the Sort window.
The Clear All button resets the sorting order of the Activity Monitor back to the
default.
Continue to Exercise A-3: Viewing and modifying the Activity Monitor column layout.
Lab 4-6

Exercise A-3: Viewing and modifying the Activity Monitor
column layout
You can modify the column layout of the Activity Monitor so that the information that is
most important to you is displayed closer to the left of the column layout.
1. Use the Activity Monitor horizontal scroll bar to scroll to the right through all
columns of the Activity Monitor.
The figure below illustrates the horizontal scroll bar location.
2. Take note of the large number of Activity Monitor columns that are displayed, and
the associated column headings.

Lab 4-7

Adjusting the column layout
3. Right-click the entry for any job that is displayed in the Activity Monitor then select
Columns and then select Layout in the resulting menu.
The Column Layout window is displayed, as illustrated in the figure below.
View > Columns > Layout
4. Use the vertical scroll bar of the Column Layout window to scroll through the list of
Columns that are available for display.
5. Of the 40 columns that are available for display in the Activity Monitor, how many
are listed? See the answer below.
All 40 columns are selected for display, by default.
In addition to using Column > Layout to change the column layout, you can also
drag and drop the column headings to the desired column location.
Selecting the columns to display and the order in which they are displayed is a
matter of personal preference of the NetBackup Administrator.
Lab 4-8

6. Use the Column Layout window, and the Move Up and Move Down buttons, to
arrange the column layout so that the columns are displayed in the order shown in
the table below.
Allow all columns to be displayed (the default setting).
Sequence / Column Sequence Column

order / order
1 Job ID 21 Operation
2 Parent Job ID 22 Kilobytes
3 Type 23 Files
4 Status 24 Pathname
5 State 25 Job PID
6 Job Policy 26 Owner
7 Job Schedule 27 Copy
8 Client 28 Active Start
9 Storage Unit 29 Active Elapsed
10 Media Server 30 Robot
11 Master 31 Vault
12 Elapsed Time 32 Profile
13 Start Time 33 Session ID
14 End Time 34 Media to Eject
15 State Details 35 Data Movement
16 Attempt 36 Off-Host Type
17 KB/Sec 37 Priority
18 Deduplication Rate 38 Transport
19 Accelerator Optimization 39 Instance or Database

20 % Completed (Estimated) 40 Share Host
The column layout proposed in the table above is for example purposes only.
7. When you have arranged the column layout as desired, click OK to save the column
layout and to close the Column Layout window.
8. Observe the Activity Monitor and verify that the column layout is as you intended.
Adjust the column layout as necessary to meet your preferences.
Continue to Exercise A-4: Creating and using job filters.
Lab 4-9

Exercise A-4: Creating and using job filters
NetBackup enables backup administrators to create job filters to filter the list of jobs
that are displayed in the Activity Monitor. In the next steps, you create a simple Activity
Monitor job filter.
1. View the list of jobs that are displayed in the Activity Monitor.
At the current time, there should be two job Types that are displayed, Backup jobs
and Image Cleanup jobs.
2. Use the parameters listed in the table below to create a job filter.
Filter parameter Parameter value

Field Status
Comparison not equal to
Value 0
Match items that contain ALL the selected
criteria (AND)
3. Perform the steps described in the table below to create the filter.
Step #: Step details:

1 Access the Activity Monitor and select any job listed.
2 Select View > Filter….
3 When the Filter window is displayed, select the Advanced tab.
4 Select the desired parameters and enter the parameter values for the filter
(as provided in the previous table).

5 Click Add to List to add the filter to the Selected Criteria.
6 Configure and add additional filter criteria, as needed.
7 Select the radio button to “AND” or “OR” the Selected Criteria (if
applicable).
8 Click OK to save the filter and to close the Filter window.
4. Upon saving the filter, it is immediately applied to the list of Activity Monitor jobs,
to alter the list of jobs displayed.
Lab 4-10

5. Think about the purpose of the filter that you created in step 3. What does this filter
accomplish? See the answer below.
The filter displays only those jobs that end in a status code that does not equal 0. As
“0” is the “successful” status code, this filter displays only the jobs that are either
partially successful (status 1), or that failed (ending with all other status codes).
6. Verify that the job filter that you created performs as expected, and that only jobs
ending in a non-zero status are displayed in the Activity Monitor.
Continue to Exercise A-5: Clearing a job filter.

Lab 4-11

Exercise A-5: Clearing a job filter
It is important to understand that a job filter remains in use until the filter is
cleared. If you do not clear the job filter you may not be able to see jobs that
are present in the NetBackup jobs list.
1. Select View and then Filter in the Activity Monitor.
View > Filter
2. When the Filter window is displayed, select the Advanced tab.
3. On the Advanced tab, click the Clear All button.
4. Click OK to close the Filter window.
5. Verify that the Activity Monitor jobs list displays the jobs that were previously not
displayed, due to the jobs filter.
If you wish to remove a filter but preserve the filter criteria for later use, click
the Remove Filter button on the toolbar of the Administration Console.
Proceed to Exercise B: Manual backups.

Lab 4-12

Exercise B: Manual backups
In the steps that follow, you perform steps to initiate a manual backup operation.
Continue to Exercise B-1: Performing a manual backup.

Lab 4-13

Exercise B-1: Performing a manual backup
1. Navigate to and select NetBackup Management > Policies in the left pane of the
The list of configured policies is displayed in the All Policies pane.
2. Click the entry for the PRE-clients-to-master-tape policy.
3. Select Actions and then select Manual Backup.
The Manual Backup window is displayed, as illustrated in the figure below.

Lab 4-14

4. Note that there is only one schedule listed in the Manual Backup window, but two
clients.
5. Click OK without making any selections in the Manual Backup window.
As there is only one schedule in the selected policy (PRE-clients-to-master-

tape), that schedule is automatically used to perform the backup operation.
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.
Proceed to Exercise C: Viewing job details.

Lab 4-15

Exercise C: Viewing job details
In this exercise, you will view the job details of various NetBackup jobs and job types.
Continue to Exercise C-1: Viewing job details in the Activity Monitor.

Lab 4-16

Exercise C-1: Viewing job details in the Activity Monitor
In this exercise, you use the NetBackup Activity Monitor to view the job details of
various NetBackup jobs and job types.
1. Select the Activity Monitor entry in the left pane of the Administration Console.
2. Locate and click the job entry for the most recent backup job that was performed
using the PRE-clients-to-master-tape policy.
This job was initiated in Exercise B. The Job State for the job may still be Active.
3. Select Actions and then Details to open the Job Details for the job.
Actions > Details
You can double-click the job entry to open the Job Details for a job.
The Job Details window contains three tabs: Job Overview, Detailed Status, and Job
Hierarchy tabs.
The Job Overview tab is selected by default.
Viewing Job Overview tab contents

4. Take note of the important Job Overview fields that contain information about the
selected job, as listed in the table below.
Information field: Information field: Information field:

Job ID Job State Backup Type

Client Master Server Job Policy
Policy Type Job Schedule Schedule Type
Priority Owner Group
Compression Data Movement Off-Host
Start Time Elapsed Time End Time
Retention Percent Complete File List
Status
Lab 4-17

5. Make note of the contents of the Backup Type field, located on the Job Overview
tab, and the meaning or significance of this Backup Type as listed below.
What is the Backup Type for the 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 Detailed Status tab contents

6. Click the Detailed Status tab.
The Status window on the Detailed Status tab provides information that is
useful when troubleshooting failed jobs. Entries posted to the Status window
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.
7. Make note of the storage unit and media information provided in the Detailed
Status tab of the job.
The storage unit used to perform the backup job was the master_tape_stu.
The Media ID used for the backup job may vary. The Media ID used for the backup is
identified in the text contained in the Status pane of the Detailed Status tab.
The Media ID used for this job may be similar to the following:
Window-based master server (winmaster): E01002
Linux-based master server (lnxmaster): E02002
Lab 4-18

Using the Troubleshooter button
8. Click the Troubleshooter button in the Detailed Status tab, as illustrated in the
figure below.
9. In the Troubleshooter window type 96, in the Status Code field, then click Lookup.
Lab 4-19

Status code 96 is a relatively common NetBackup failure status code, and is
used here simply to provide an example of the information available in the
Troubleshooter tab of the Job Details.
10. Take note of the types of information that are available for the status code in the
Problem, Troubleshoot, and Veritas Technical Support tabs of the Troubleshooter
window.
11. Close the Troubleshooter window.
Viewing the Job Hierarchy tab contents

12. Click the Job Hierarchy tab of the Job Details window, and observe the tab contents.
If the job for which you are viewing the Job Details is part of a NetBackup job
hierarchy – consisting of a parent job and potentially multiple child jobs – the
Job Hierarchy tab displays the parent and child jobs associated with the job.
The job you are currently viewing is not part of a job hierarchy.
13. Click Close to close the Job Details window for the job.
Continue to Exercise C-2: Scheduled vs. Immediate Backup Types.

Lab 4-20

Exercise C-2: Scheduled vs. Immediate Backup Types
Viewing the Job Details of a scheduled job

1. In the Activity Monitor job list, locate the most recent backup job entry for a job
that used the PRE-clients-to-master-bdisk policy.
2. Double-click the job entry for the job (that used the PRE-clients-to-master-bdisk
policy).
The Job Details window is opened for the job.
3. Take note of the contents of the Backup Type field for the job.
The Backup Type field is located near the top of the Job Overview tab.
The Backup Type, is Scheduled.
The significance of a “Scheduled” Backup Type is used to identify a backup job that
was automatically initiated by the NetBackup job scheduler mechanism, based upon
the settings of a schedule contained in a backup policy.
Earlier in this exercise you looked at the Job Details for a job that used a
Backup Type of “Immediate”. It is important to understand the distinction
between “Scheduled” and “Immediate” Backup Types.
Continue to Exercise C-3: Full and Incremental backup jobs.

Lab 4-21

Exercise C-3: Full and Incremental backup jobs
Gaining an understanding about 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.
2. Click the Activity Monitor entry in the left pane of the Administration Console.
3. Locate the entry for the first (earliest, lowest-numbered) Backup job that was
performed using the LAB03-clients-to-master-disk-tape-stugroup policy.
4. Double-click the entry for that Job ID.
5. Select Actions and then Details, to open the Job Details for the job.
The Job Details window is opened for the job
6. Take note of the information for the job, as recorded in the table below.
Use the Job Overview and Detailed Status tabs to confirm the information as shown
in the table.
Client name: winmaster or winmedia (Windows-based)

lnxmaster or lnxmedia (Linux-based)
Backup Type: Scheduled

Job Schedule: diffincr_frequency
Schedule Type: Differential Incremental Backup
Storage Unit: master_advdisk_stu (may vary because you have
specified the use of a storage unit group)
Start Time (date and time): variable
Current Kilobytes written: 825182 (Kbytes) (Windows clients) - estimated
819552 (Kbytes) (Linux clients) - estimated
Current Files Written: 11137 (Windows clients) - estimated
11135 (Linux clients) - estimated
7. Close the Job Details window for the job.
Lab 4-22

8. Navigate to Policies in the left pane of the Administration Console.
NetBackup Management > Policies
9. Double-click the entry for the LAB03-clients-to-master-disk-tape-stugroup policy, to

open the policy.
10. Examine the LAB03-clients-to-master-disk-tape-stugroup policy, and verify the

information listed in the table below, concerning the policy and its schedules.
The Policy Storage specified for use in the policy Attributes is the master_disk-
tape_stugroup storage unit. Given that the Policy Storage that was defined in
the policy, you could predict the Storage Unit that would be used to perform
the backup job.
The Policy Storage defined for the policy is a storage unit group. The storage
units included in the storage unit group all reside on the master server. The
“Storage unit selection” method is set to Prioritized for this storage unit group,
so that the storage unit that is used for backup jobs depends upon the status
and availability of the individual storage units in the group.
The backup window for the Full Backup schedule was not open at the time that
the backup job occurred – so the Full Backup schedule could not be used. The
backup window for the Differential Incremental Backup was open. That is why
the NetBackup scheduler used that schedule to perform the backup. This
assumes you are doing this lab during normal business hours. If you are doing
this lab at another time than your results may vary.
Continue to the next page

Lab 4-23

11. Close the LAB03-clients-to-master-disk-tape-stugroup policy.
You could use the Windows Explorer (Windows) or File Manager (Linux), to examine
the contents of the client file system that was backed up by the job you examined in
the previous steps. However, it is not necessary for you to do that at this time.
If you are using the Windows-based master server, the illustration below identifies
the files and folders, and the size of the data that resides in the E:\data folder on the
Windows-based clients – winmaster.example.com and winmedia.example.com-
that were backed up by the recent backup jobs that you initiated.
If you are using the Linux-based master server, the illustration below identifies the
files and directories, and the size of the data, that resides in the /data directory on
the Linux-based clients – lnxmaster.example.com and lnxmedia.example.com - that
were backed up by the recent backup jobs that you initiated.
Lab 4-24

12. Compare the “Current Files written” and “Current Kilobytes written” information
for the backup job with the directory or folder information on the client system that
was backed up.
The number of files and size of the files that were backed up by this job are the same
as the total size (in KB) and number of files that are resident in the DATA folder
(E:\data or /data) on the client system.
Although the schedule used to perform the backup was a Differential Incremental
Backup schedule, the entire contents of the 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.
One hour from the time that the most recent backup job of the client was run using the
LAB03-clients-to-master-disk-tape-stugroup policy, another Differential Incremental
Backup job will be run for that client. The size of the data and the number of files that
are backed up by the new job will be substantially smaller than the number/size of files
that were backed up by the job you have been analyzing. This second backup job is truly
an incremental backup.
The statements above assume you are doing this lab during normal business
hours for EST (GMT -5). If you are working at other times (or in different time
zones) you may see different results based on the start window of this
schedule.
Proceed to Exercise D: Deactivating and activating policies.
Lab 4-25

Exercise D: Deactivating and activating policies
NetBackup provides the capability for a backup administrator to quickly activate and de-
activate policies, using the NetBackup Administration Console.
Continue to Exercise D-1: Deactivating policies.

Lab 4-26

Exercise D-1: Deactivating policies
In this lab exercise you will de-activate policies, using the NetBackup Administration
Console.
2. Select Policies in the left pane of the NetBackup Administration Console.
The list of policies that are configured on your master server is displayed in the All
3. If the LAB03-challenge policy is not present on the master server, go directly to lab
step 8 to deactivate another policy
If you skipped the challenge exercise in lab 03, the LAB03-challenge policy does
not exist. This is no cause for concern.
4. Locate the entry for the LAB03-challenge policy, and verify that entry for the policy
is greyed out, and is marked with a red X.
If the policy name is greyed out and marked with a red X, it indicates that the
policy is deactivated. A policy that is deactivated cannot be used to perform
backup operations.
5. If the entry for the LAB03-challenge policy exists, and the policy is not deactivated,
click the entry for the policy in the All Policies pane.
6. Select Actions then Deactivate, to deactivate the policy.
7. Verify the entry for the LAB03-challenge policy in the All Policies pane is marked
with a red X, and that the entry for the policy is greyed-out.
8. In the steps that follow you deactivate the PRE-clients-to-master-bdisk and LAB03-
clients-to-master-disk-tape-stugroup policies on the master server.
You are taking this step to prevent large numbers of automated (scheduled) backups
using these policies from occurring during the remainder of this course.
Lab 4-27

9. Click the entry for the PRE-clients-to-master-bdisk policy.
10. Select Actions and then select Deactivate, to deactivate the policy.
Actions > Deactivate
11. Verify that the entry for the PRE-clients-to-master-bdisk policy in the All Policies
pane is marked with a red X, and that the entry for the policy is greyed-out.
12. Perform the steps necessary to deactivate the LAB03-clients-to-master-disk-tape-

stugroup policy.
13. Verify that the entry for the LAB03-clients-to-master-disk-tape-stugroup policy in

the All Policies pane is marked with a red X, and that the entry for the policy is
greyed-out.
A policy that is deactivated cannot be used to perform backup operations.
A deactivated policy can be activated easily by clicking on the entry for the
policy in the All Policies pane, and selecting Actions > Activate.
Proceed to Exercise E: Performing user-initiated backups.

Lab 4-28

Exercise E: 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.
Continue to Exercise E-1: Understanding the Backup, Archive, and Restore user interface
(for performing user-initiated backups).
Lab 4-29

Exercise E-1: 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.example.com system wants to perform a user-initiated
backup of an important folder on that Windows-based 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. Access the NetBackup Administration Console window on the


Lab 4-30

2. Verify that the Administration Console is currently connected to your master server.
To do so, verify that the host name of your master server is displayed as the top
entry in the left pane of the Administration Console, as illustrated in the figure
below.

server, click the “Launch a new instance…” button (illustrated in the figure above)
and select the host name of your master server, winmaster.example.com or
Launching Backup, Archive, and Restore from the NetBackup

Administration Console
4. Select the Backup, Archive, and Restore entry in the left pane of the Administration
Console.
The Backup, Archive, and Restore (BAR) user interface is displayed in the right pane
of the Administration Console.
When the BAR user interface is launched from the NetBackup Administration
Console, the user interface provides three tabs:
 Backup Files
 Restore Files
 Task Progress
The Restore Files tab is selected by default.
Lab 4-31

5. To perform a user-initiated backup operation, select the Backup Files tab in the right
6. 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, your master server system, either winmaster.example.com or

7. Select Actions and then Specify NetBackup Machines and Policy Type.
Actions > Specify NetBackup Machines and Policy Type
8. Verify the Specify NetBackup Machines window is displayed and the host name of
your master server is listed in the Server to use for backups and restore field.
This entry refers to the host name of the master server to which the user-initiated
backup request will be sent (from the client system).
9. Click Cancel, to cancel the operation without making a change to the backup server
that is specified.
IMPORTANT CONCEPT REPEATED: When the Backup, Archive, and Restore (BAR)
object of the NetBackup Administration Console interface is used 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 master

server), the BAR user interface can only be used to perform a user-initiated backup
of the 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.example.com), the Backup,
Archive, and Restore user interface must be launched from the client itself and
not accessed from the NetBackup Administration Console.
Lab 4-32

The Backup, Archive, and Restore user interface on a Windows-based client is
the file, nbwin.exe, and on a Linux-based client is the file, jbpSA.
Continue to Exercise E-2: Accessing the Backup, Archive, and Restore user interface on
the console.example.com client system.
Lab 4-33

Exercise E-2: Accessing the Backup, Archive, and Restore
user interface on the console.example.com client system
In the following steps, you locate and launch the Backup, Archive, and Restore user
interface on the Windows-based NetBackup client system, console.example.com.
1. Access the desktop of the Windows-based console.example.com system.
2. If you master server is winmaster.example.com skip to step 5. If your master server

is lnxmaster.example.com right-click on the Command Prompt shortcut and select
Open.
3. Execute the following command to update the NetBackup configuration settings on

Command: nbsetconfig C:\Files\server_list_lnx.txt
One way to view the NetBackup configuration settings on a host is to use the
command nbgetconfig. You can also use nbsetconfig command to edit the
NetBackup configuration settings. In this lab environment, for the

console.example.com host, the master server is set to
winmaster.example.com. A server_list_lnx.txt file has already been created so
that the master server points to lnxmaster.example.com. By running the
nbsetconfig command, shown in this step, on console.example.com, you are
able to update the NetBackup configuration settings so that client,
console.example.com, now points to the master server as
lnxmaster.example.com and not winmaster.example.com.
4. Close the Command Prompt window.
Lab 4-34

5. Locate and double-click the Backup, Archive, and Restore shortcut, located on the
desktop of console.example.com.
On a Linux-based NetBackup client system, the Backup, Archive, and Restore

(BAR) user interface is launched using the jbpSA binary file.
The figure below illustrates the Windows-based Backup, Archive, and Restore user
interface.
The Backup, Archive, and Restore user interface may take a few moments to
load before it is ready for use.
Continue to Exercise E-3: Configuring the Backup, Archive, and Restore (BAR) user
interface.
Lab 4-35

Exercise E-3: Configuring the Backup, Archive, and
Restore (BAR) user interface
A NetBackup client can be backed up by multiple master servers. The user can use the
Backup, Archive, and Restore user interface to specify the master server to which
backup and restore requests are sent.
Specifying NetBackup Machines and Policy Type

1. Click the Select for Backup tab, located near the top of the Windows-based Backup,
Archive, and Restore window.
2. Select File then Specify NetBackup Machines and Policy Type.
File > Specify NetBackup Machines and Policy Type
The Specify NetBackup Machines and Policy Type window is opened.

Lab 4-36

3. Use the information provided in the table below to enter the information in the
Specify NetBackup Machines and Policy Type window on your system.
Parameter Value
Server to use for backups and restores: winmaster.example.com
(Choose based upon your master server) OR
Source client for restores: console.example.com
(Defaults to local system hostname)
Destination client for restores: console.example.com (selection is
greyed out and cannot be changed)
Policy Type for restores: MS-Windows
Date/time range:
From Date / time: greyed out (default)
Oldest available: selected (default)
To Date /time: greyed out (default)
Newest available: selected (default)
4. Click OK to save your changes and to close the window.
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
master server to which the backup request is sent.
Continue to Exercise E-4: Performing a user-initiated backup.

Lab 4-37

Exercise E-4: Performing a user-initiated backup
Note the following in the open Backup window of the Backup, Archive, and Restore
user interface:
 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.
 The “Contents of…” pane displays the detailed contents of the disk drive or other
entity that is highlighted in the All Folders pane.
1. Highlight (do not select the check box) the entry for the C drive, in the All Folders
pane.
2. Select the check box for Documents and Settings in the Contents of C:\ pane.
The check box for Documents and Settings is marked in the Contents of C:\ pane.
3. Select Actions and then Backup.
Actions > Backup
The Backup Files window is displayed.
4. Verify that the NetBackup Server field of the Backup Files window contains the
name of your master server.
winmaster.example.com or lnxmaster.example.com
5. Leave other fields of the Backup Files window at their default settings.
6. Click the Start Backup button to initiate the backup of the client.
The NetBackup Message dialog box is displayed, as illustrated in the figure below.
Lab 4-38

7. Click Yes, to close the dialog box and continue.
The View Status window is displayed, as illustrated in the figure below.
8. Mark the check box for Verbose to view detailed information about the backup job.
A user-initiated backup failure

The Progress pane of the View Status window indicates that a failure has occurred. The
Server status for this failure is 240.
9. 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.
10. Close the View Status window.
11. Allow the Backup, Archive, and Restore user interface to remain open.
Lab 4-39

14. Locate the entry for the failed job that is displayed in the Activity Monitor Jobs list.
The entry for the failed job should be located at or near the top of the jobs list.
15. The Activity Monitor entry for the failed job displays information, as described in
the table below.
Job information field: Contents/value:

Status: 240
Job Policy: *NULL*
Client console.example.com
Correcting the problem

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:
 The policy must include a schedule that has a Backup type of User Backup.
 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.
16. Select NetBackup Management and then Policies in the Administration Console
window.
17. Double-click the LAB03-console-to-master-advdisk policy entry in the All Policies

pane.
Take note that this policy already supports the MS-Windows policy type and can be
used to support a User Backup schedule.
18. Select the Schedules tab in the LAB03-console-to-master-advdisk policy.
Lab 4-40

19. Add a User schedule to the policy using the information provided in the table.

Name: user_backup
Type of backup: User Backup
Schedule type: N/A
Retention 2 weeks
Start Window parameter User backups – Sunday through-
Saturday 24 hours a day
Set the Start day to Sunday and the Start time to 00:00:00. Then set the End
day to Monday and the end time to 00:00:00. Then select the Duplicate
button.
20. Click OK to save the user_backup schedule.
Note that the policy now contains four schedules, as identified in the table
below. Note the schedule type for each of these schedules.
Schedule Name Schedule Type

diffincr_calendar_weekdays Differential Incremental Backup
full_calendar_tuesday Full Backup
full_manual Full Backup
user_backup User Backup
21. Click the Clients tab to verify console.example.com is listed.

You have now satisfied the requirements for our user backup to succeed: the client
is a member of a policy that contains a User Backup schedule with an open start
window.
22. Click OK to save your changes to the LAB03-console-to-master-advdisk policy.
Re-testing the user-initiated backup

Perform the steps that follow to perform the user-initiated backup of
Lab 4-41

24. Access the Backup, Archive, and Restore window on console.example.com.
25. 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).
26. Select Actions and then Backup.
Actions > Backup
27. When the Backup Files window is displayed, click the Start Backup button without
making any changes to the parameters of the Backup Files window.
28. When the NetBackup Message dialog box is displayed, click Yes to view the progress
of the backup.
The View Status window is displayed.
29. Select the entry for the newest (most recent) Backup operation in the View Status
window.
30. Monitor the progress of the Backup operation until it is completed.
31. Verify that the Backup operation is completed successfully.
Seek assistance if the job fails.
32. Click Close to close the View Status window.

Lab 4-42

33. Close the Select for Backup window of the Backup, Archive, and Restore user
interface, as illustrated in the figure below.
34. Select File and then Exit to close the Backup, Archive, and Restore user interface.
File > Exit
36. Locate the entry for the most recent Backup job in the Activity Monitor and briefly
view the Job Details for the job.
Note that the Job Schedule used for this backup should be identified as the
user_backup schedule.
37. Close the Job Details for the Backup job.
Continue to Exercise E-5: Preparing for the next lab activity.
Lab 4-43

Exercise E-5: Preparing for the next lab activity
In preparation for the next lab activity (Lab 5), complete the steps that follow.
1. Select NetBackup Management and then Policies in the left pane of the
2. Perform a manual full backup of the console.example.com client, using the LAB03-
console-to-master-advdisk policy.
The detailed steps are described in the table that follows.
Step # Step details

1 Select NetBackup Management > Policies in the left pane of the
2 Click the entry for the policy, LAB03-console-to-master-advdisk,
located in the All Policies pane.
3 Select Actions > Manual Backup. The Manual Backup window is
displayed.
4 Select the full_manual schedule.
5 Click OK to initiate the backup operation.
3. After initiating the manual backup, select the Activity Monitor entry in the left pane
4. View the job entry for the most recent Backup job - that used the LAB03-console-to-
master-advdisk policy.
5. Monitor the progress of the job until it runs to successful completion (status 0).
6. If the job fails, record the status code and notify your instructor.
You have completed all tasks planned for this lab activity.
Lab 4-44

Lab 5: Performing File System Restores
In this lab activity, you perform and monitor file system restore jobs using various
NetBackup-provided user interfaces.
Proceed to Exercise A: Becoming familiar with key restore settings in the BAR user
interface.
Lab 5-1

Exercise A: Becoming familiar with key restore
settings in the BAR user interface
In this exercise, you view and become familiar with key settings of the Backup, Archive,
and Restore user interface, that are important when performing NetBackup restore
operations.
Continue to Exercise A-1: Accessing the NetBackup Administration Console BAR UI.
Lab 5-2

Exercise A-1: Accessing the NetBackup Administration
Console BAR UI
In the following steps, you will launch the NetBackup Administration Console and access
the Backup, Archive, and Restore (BAR) user interface.

console.example.com. (If no Administration Console window is open, see the Note.)

NetBackup 8.0 Admin Console shortcut, located on the desktop of the
console.example.com system, to launch the NetBackup Administration
Console. Then, enter the Host name, User name, and Password in the
Administration Console login screen to connect to your master server.

3. View the top entry in the left pane of the Administration Console, and verify that the
name of your master server is displayed there, as illustrated in the figure below.
The top entry in the left pane of the Administration Console displays the name of
the NetBackup server system to which the Administration Console is connected.
Lab 5-3

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. The
“Launch a new instance…” button is highlighted in the figure above.
4. Click the Backup, Archive, and Restore entry in the left pane of the NetBackup
The Backup, Archive, and Restore window is displayed in the right pane of the
Continue to Exercise A-2: Specify NetBackup Machines and Policy Type.

Lab 5-4

Exercise A-2: Specify NetBackup Machines and Policy
Type
In the following steps, you view selections in the Specify NetBackup Machines and
Policy Type window of the Backup, Archive, and Restore (BAR) user interface, to
become familiar with these settings.
1. Note the three main tabs of the Backup, Archive, and Restore (BAR) user interface,
located near the top of the user interface as illustrated below.
These tabs are the Backup Files, Restore Files, and Task Progress tabs.
The Restore Files tab of the BAR user interface is selected by default when first
opened. However, because you used the BAR user interface in a previous
exercise and had selected the Backup Files tab, the interface remembers the
tab you had previously selected. The Backup Files tab should currently be
selected.
2. Click the Restore Files tab of the BAR user interface.

Lab 5-5

The Specify NetBackup Machines and Policy Type window is displayed.
The Specify NetBackup Machines and Policy Type window allows for the selection of
four key parameters:
• Server to use for backups and restores: This is the host name of the master server
to which the BAR user interface will send backup and restore related requests.
• Source client for restores: This parameter is used to specify the name of the source
client whose backup images will be browsed in preparation for a restore operation.
• Destination client for restores: This is the host name of the client to which files are
to be restored.
• Policy type for restores: The field specifies the Policy type that was used to back up
the source client, and is the policy type that the master server uses when searching
its backup image catalog for images to be restored from. If the policy type is not set
properly, the master server may be unable to locate backup images for the client.
Lab 5-6

Details about the Specify NetBackup Machines and Policy Type
parameters
The Specify NetBackup Machines and Policy Type window allows for the selection of
four key parameters:
• Server to use for backups and restores: This is the host name of the master server
to which the BAR user interface will send backup and restore related requests. A
given NetBackup client system may be backed up by more than one master server,
and so is able to (and must) specify the host name of the master to which a specific
user-backup or restore request is directed.
•
Source client for restores: This 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.example.com can only browse for and select for
restore from backup images created from clientname.example.com resident
data.
̶ In contrast, NetBackup backup administrators running the Backup, Archive, and
Restore user interface that is connected to the master server system may
browse for backup images and restore data to any client in the master server’s
NetBackup domain.
Lab 5-7

• Destination client for restores: This is the host name of the client to which files are
to be restored.
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 that is running the Backup, Archive, and Restore
user interface that is connected to a NetBackup server system is allowed to restore
client data from backup images to any client in the NetBackup 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.)
• Policy type for restores: The field specifies the Policy type that was used to back up
the source client, and is the policy type that the 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 master server may be unable to locate backup images for the
client system.
4. Click Cancel to close the Specify NetBackup Machines and Policy Type window.
Continue to Exercise A-3: Viewing other important BAR user interface settings for
restores.
Lab 5-8

Exercise A-3: Viewing other important BAR user interface
settings for restores
In the steps that follow, you look at other important Backup, Archive, and Restore user
interface settings, related to restore operations. Each of these setting is used by the
master server when searching for backup images of the selected client that can be used
during a restore operation.
The Restore type field

1. Click the drop-down arrow for the Restore type field of the BAR user interface, as
Take note of the Restore type selections that are available, as illustrated in item #1
on the figure above.
2. Click the Normal Backups selection in the drop-down menu.
Normal is the default Restore Type selection.
You can also change the Restore type by selecting Actions > Select Restore Type
from the tool bar of the Backup, Archive, and Restore user interface.
Lab 5-9

Start date and End date
3. Take note of the Start date and End date settings on the BAR user interface, as
illustrated in item #2 of the figure below.
The Start date and End date specify the date range that the 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.
4. From the Actions drop-down menu, select Set Date Range from the tool bar of the
Backup, Archive, and Restore user interface.
Actions > Set Date Range
5. Note that two options are provided to set the date range – Calendar and Backup
History.
6. Select the Calendar option.
Lab 5-10

7. Note that a Date Range window is displayed.
The Date Range window provides two tabs that enable the selection of the Start
Date and of the End Date that are used when searching for backup images from
which to restore client data.
The Date Range window is illustrated in the figure below.
When you use the Date Range window to set the date range, the results are
displayed in the BAR user interface, as illustrated in item #2 of the figure on the
previous page.
8. Click Cancel in the Date Range window to cancel the setting of the date range.
Lab 5-11

Backup History
9. Select Backup History from the tool bar of the Backup, Archive, and Restore user
interface.
Actions > Set Date Range > Backup History
The Backup History window is displayed, as illustrated in the figure below.
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, click the entry
for the first (top) backup image, and then hold the SHIFT key while clicking the entry
for the last (bottom) backup image you wish to use for the restore.
10. Click Cancel to close the Backup History window.

You can access the Set Date Range (item #1) and Backup History (#2) using the icons
located on the BAR user interface, as highlighted by items #1 and #2 in the figure
above.
Lab 5-12

Show Most Recent Backup or Show All Backup
You can direct the master server to Show All Backups (item #4) or to Show
Most Recent Backup (item #3) using icons on the BAR user interface, as
The default selection is the Show Most Recent Backup selection.
You can also make the selection to Show Most Recent Backup or Show All Backups
in the View menu on the Backup, Archive, and Restore user interface, as illustrated
in the figure below.
11. Select View and then Show All Backups, as illustrated in the figure below.
View > Show All Backups

Proceed to Exercise B: Restoring client files to their original location.
Lab 5-13

Exercise B: Restoring client files to their original
location
In the following steps, you make selections in the Backup, Archive, and Restore user
interface to prepare for a restore of a client folder of the client, console.example.com,
from the most recent backup set (Full Backup and Differential Incremental) of backup
images for the client, to the original folder location on the client.
Continue to Exercise B-1: Preparing for the restore.

Lab 5-14

Exercise B-1: Preparing for the restore
1. Select Actions and then Specify NetBackup Machines and Policy Type in the tool
bar of the Backup, Archive, and Restore user interface.
2. Enter the information provided in the table below in the fields of the Specify
NetBackup Machines and Policy Type window.
Parameter Value
Server to use for backups and winmaster.example.com
restores: (Choose based upon your OR
master server) lnxmaster.example.com
Destination client for restores: console.example.com
The detailed steps for setting the Specify NetBackup Machines and Policy Type window
are described in the following table.
# Detailed Steps
1 Click the drop-down arrow for the Server to use for backups and restores field,
and select the entry for your master server, winmaster.example.com or
2 Click the drop-down arrow for the Source client for restores field, and select
console.example.com. Note that console.example.com is automatically
selected in the Destination client for restores field.

3 In the Policy type for restores field, use the drop-down arrow to select the
Policy type that is used to back up the client. console.example.com is backed up
using the MS-Windows policy type.
3. After making the selections in the Specify NetBackup Machines and Policy Type,
click OK to save the changes and to close the window.
4. In the Restore Files tab of the BAR user interface, set the Restore Type to Normal
Backups.
The default setting of the Restore Type field is Normal Backups.
Lab 5-15

5. From the Actions menu, select Set Date Range then Backup History.
The Backup History window is displayed, as illustrated in the figure below. The
figure below is just an example. Your lab environment may show different backups.
6. Select the entries for the most recent Full Backup and for any Differential
Incremental Backup images that might exist for the client, as illustrated in the figure
below.
To select multiple backup images to use for the restore, click the first (top) entry,
then hold the SHIFT key on your keyboard, and click the bottom entry to be
selected.
Using the Backup History window, you can select any backup image or set of
backup images that are adjacent to each other to use for the restore operation.
You cannot select images that are not adjacent to each other. Depending on
the order your backups were performed, this may result in the need to include
other images, such as a user backup, in your selection, which is not a cause for
concern.
Lab 5-16

7. Click OK to save your backup image selections, and to close the Backup History
window.
As a result of selecting the backup images in the Backup History window, the
NetBackup client sends a request to the master server to retrieve a list of the
contents of the selected backup images.
The results are displayed in the Directory Structure pane of the BAR user interface,
as illustrated in the figure below (the figure shows the view of the Directory
Structure pane after its contents have been expanded).
8. Click to expand the entry for the console.example.com system in the Directory
Structure pane to view the contents of the system that were backed up in the
selected backup images, as illustrated in the previous figure.
9. Click to expand the entry for the E drive in the Directory Structure pane.
Lab 5-17

10. Click to expand the entry for the data folder in the Directory Structure pane.
11. Click to highlight the entry for the smallfiles folder in the Directory Structure pane
(but do not click the check box for the folder).
12. The Contents of the selected directory pane displays the contents of the smallfiles
folder that were backed up.
The contents were included in the backup images that were selected for this
restore operation.
13. Click the check box for the smallfiles folder in the Directory Structure pane.
14. Note the results, as the folder and its contents are all marked for restore, as
You have prepared the BAR user interface to perform the restore operation
Lab 5-18

15. Leave the Backup, Archive, and Restore user interface window open on the
You return to this window in a few moments.
Preparing the client system (console.example.com) for the restore

Before continuing with the restore, you perform steps on the console.example.com
client system to remove the contents of the smallfiles folder on the client.
17. Double-click the File Explorer shortcut, located on the desktop of

18. When the File Explorer window is displayed, click the entry for the DATA (E:) drive,
located in the left pane of that user interface.
The data folder is displayed in the right pane of the File Explorer.
19. Double-click the data folder, to open the folder.
The sub-folders of the data folder are displayed in the right pane of the File
Explorer.
20. Click the entry for the smallfiles folder, to highlight the folder.
21. Right-click the entry for the smallfiles folder and, in the resulting menu, click Delete.
22. Allow the File Explorer window to remain open on console.example.com.
You return to this window in a few moments.
You are ready to continue the restore operation.
Continue to Exercise B-2: Performing the restore of client files.
Lab 5-19

Exercise B-2: Performing the restore of client files
In the steps that follow you complete the normal restore of a client folder and its
contents to the original client system, console.example.com.
1. Access the open NetBackup Administration Console window on the

The Backup, Archive, and Restore user interface is currently open in the right pane
of the Administration Console window, and you have previously selected the
E:\data\smallfiles folder and its contents for restore.
2. Click the Preview button on the BAR user interface to preview the media that is
required to perform the restore (based on the storage unit that was used to write
the backup images that are used for the restore).
You can also select Actions > Preview.
The Media Required window is displayed.
If the backup images to be used for the restore were written to a disk-based
storage unit, the window will contain a message, “No media required for
restore. Images are on disk”. If the backup images were written to tape, the
Media IDs that are required for the restore operation will be listed.
3. Click OK to acknowledge the contents of the Media Required window, and to close
the window.
4. Click the Restore button on the BAR user interface.
You can also select Actions > Restore. The Restore Marked Files window is
displayed.
5. Make and verify the following selections in the Restore Marked Files window:
̶ Restore everything to its original location (default selection)

̶ Options - and all other settings (use the default selections).
6. Click the Start Restore button.
Within a few moments the View Progress dialog box is displayed.
Continue to Exercise B-3: Viewing restore progress in the Task Progress tab.
Lab 5-20

Exercise B-3: Viewing restore progress in the Task
Progress tab
1. Click Yes in the View Progress dialog box to view the progress of the restore.
2. When the Task Progress tab is displayed (automatically), verify that the entry for the
most recent Restore operation is highlighted, in the Tasks Performed pane of the
user interface.
The progress of the restore is displayed in the Results of the Task Selected Above
pane of the Task Progress tab.
3. Click the Full Contents check box to see more detailed message about the selected
operation in the Results of the Task Selected Above pane.
4. Monitor the progress of the restore operation until it runs to successful completion.
If the restore fails, take note of the Status information provided and notify your
instructor.
5. If the restore operation was successful, scroll to the bottom of the Results of the
Task Selected Above pane, and take note of the number of files that were restored,
as illustrated in the figure below.
Continue to Exercise B-4: Verifying the restored folder and files on the client.
Lab 5-21

Exercise B-4: Verifying the restored folder and files on the
client
In the steps that follow, you access the console.example.com client system to verify
that the folder that had been deleted previously has been restored.
1. Access the open File Explorer window on console.example.com.
2. Navigate to the E:\data folder, and verify that the smallfiles sub-folder is present in
the data folder.
3. Double-click the smallfiles folder to open the folder and 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.
Continue to Exercise B-5: Viewing the Restore job entry in the Activity Monitor.
Lab 5-22

Exercise B-5: Viewing the Restore job entry in the Activity
Monitor
In the steps that follow, you select the NetBackup Activity Monitor and view the entry
for the most recently-completed Restore job.
1. Click the entry for the Activity Monitor in the left pane of the NetBackup
2. Locate the entry for the most recently-completed Restore job in the Activity Monitor
Jobs tab.
3. Double-click the entry for the Restore job to open the Job Details for the job.
4. Browse the contents of the Job Overview, Detailed Status, and Job Hierarchy tabs
of the Job Details.
When restoring files to the same directory, you should note the following items.
From the Job Overview tab of the Job Detail window you can see the Job Type is
marked as Restore. The Client is console.example.com, the Master Server is
winmaster or lnxmaster. The Files List shows the files (/E/data/smallfiles/) being
restored.
From the Detailed Status tab note the Job PID. This is the process ID of bprd
(NetBackup Request Daemon). The Media Server used in this restore is winmaster
or lnxmaster. 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 Status
pane 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.
5. Close the Job Details window for the restore job.
You have completed this restore operation.
Proceed to Exercise C: Restoring client files to an alternate file system location.
Lab 5-23

Exercise C: Restoring client files to an alternate file
system location
In this exercise, you use the NetBackup Backup, Archive, and Restore (BAR) user
interface to restore client file system data to an alternate folder location on the original
client system (from which the files were backed up), and monitor the restore operation
using the Task Progress user interface of the BAR user interface and the Activity
Monitor.
Continue to Exercise C-1: Preparing for the restore.

Lab 5-24

Exercise C-1: Preparing for the restore
In the steps that follow, you prepare to perform an alternate Restore to the console
client.
1. Select the Backup, Archive, and Restore entry in the left pane of the NetBackup
2. Click the Restore Files tab in the BAR user interface, displayed in the right pane of
the Administration Console window.
3. Under Actions select Specify NetBackup Machines and Policy Type in the tool bar of
the Backup, Archive, and Restore user interface.
4. Verify the information provided in the table below in the fields of the Specify
NetBackup Machines and Policy Type window.
Parameter Value
(Choose based upon your master server) OR
Destination client for restores: console.example.com
5. After making the selections in the Specify NetBackup Machines and Policy Type
window, click OK to save the settings and to close the window.
6. In the Restore Files tab of the BAR user interface, set the Restore Type to Normal
Backups.
7. Verify that the Restore Type field is set to Normal Backups.
8. Select Actions and then select Set Date Range to select the Backup History.
Lab 5-25

9. Select the entries for the most recent Full Backup and any Differential Incremental
Backup images for the client if they exist.
To select multiple backup images to use for the restore, click the first (top) entry,
then hold the SHIFT key on your keyboard, and click the bottom entry to be
selected.
10. Click OK to save your backup image selections, and to close the Backup History
window.
As a result of the backup image selections you made in the Backup History
window, the NetBackup client sends a request to the master server to retrieve
a list of the contents of the backup images.
11. Click to expand the entry for the console.example.com system in the Directory
Structure pane to view the contents of the system that were backed up in the
selected backup images.
12. Click to expand the entry for the E drive in the Directory Structure pane.
14. Click to highlight the entry for the smallfiles folder in the Directory Structure pane
(but do not click the check box for the folder).
15. Note that the Contents of the selected directory displays the contents of the
smallfiles folder that were backed up and included in the backup images that were
selected for this restore operation.
16. Click the check box for the smallfiles folder in the Directory Structure pane.
17. Note the results, as the folder and its contents are all marked for restore.
You have prepared the BAR user interface to perform the restore operation
18. Leave the Backup, Archive, and Restore user interface window open on the
console.example.com system. You return to this window in a few moments.
Lab 5-26

Preparing the client system (console.example.com) for the restore
Before continuing with the restore, you perform steps on the console.example.com
client system to prepare for the restore of the smallfiles folder and its contents to an
alternate folder location on the client.
20. Double-click the File Explorer shortcut, located on the desktop of

21. When the File Explorer window is displayed, click the entry for the DATA (E:) drive,
located in the left pane of that user interface.
The data folder is displayed in the right pane of the File Explorer.
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.
22. Allow the File Explorer window to remain open on console.example.com. You
return to this window in a few moments.
You are ready to continue the restore operation.
Continue to Exercise C-2: Performing the restore of client files.

Lab 5-27

Exercise C-2: Performing the restore of client files
In the steps that follow you complete the restore of a client folder and its contents to an
alternate folder location on the original client system, console.example.com.

The Backup, Archive, and Restore user interface is currently open in the right pane
of the Administration Console window, and you have previously selected the
E:\data\smallfiles folder and its contents for restore.
Note that you can also select Actions > Restore.
The Restore Marked Files window is displayed.
3. Make and verify the following selections in the Restore Marked Files window:
̶ Restore everything to a different location (maintaining existing structure)

Destination: E:\alternate-directory\smallfiles
̶ Options - and all other settings (use the default selections).
4. Click the Start Restore button.
Continue to Exercise C-3: Viewing the restore progress in the Task Progress tab.
Lab 5-28

Exercise C-3: Viewing the restore progress in the Task
Progress tab
2. When the Task Progress tab is displayed, verify that the entry for the most recent
Restore operation is highlighted, in the Tasks Performed pane of the user interface.
The progress of the restore is displayed in the Results of the Task Selected Above
3. Click the Full Contents check box, if it not already marked, to see more detailed
message about the selected operation in the Results of the Task Selected Above
pane.
4. Monitor the progress of the restore operation until it runs to successful completion.
If the restore fails, note the Status information provided and seek assistance.
5. If the restore operation was successful, scroll to the bottom of the Results of the
Task Selected Above pane, and take note of the number of files that were restored.
Continue to Exercise C-4: Verifying the restored folder and files on the client.
Lab 5-29

Exercise C-4: Verifying the restored folder and files on the
client
In the steps that follow, you access the console.example.com client system to verify
that the selected folder and its contents have been restored.
1. Access the open File Explorer window on console.example.com.
2. Navigate to the E:\ drive, and verify that the alternate-directory folder is present on
the E:\ drive.
3. Double-click the alternate-directory folder to open the folder.
4. Verify that the smallfiles sub-folder is present in the E:\alternate-directory folder.
5. Double-click the smallfiles folder to open the folder and view its contents.
The folder should contain 1000 files, file000.txt – file999.txt.
File Explorer can be slow to refresh. If the restored files are not immediately
visible, try closing the window and opening a new File Explorer window.
Continue to Exercise C-5: Viewing the Restore job entry in the Activity Monitor.
Lab 5-30

Exercise C-5: Viewing the Restore job entry in the Activity
Monitor
In the steps that follow, you select the NetBackup Activity Monitor and view the entry
for the most recently-completed Restore job.
1. Click the entry for the Activity Monitor in the left pane of the NetBackup
2. Locate the entry for the most recently-completed Restore job in the Activity Monitor
Jobs tab.
3. Double-click the entry for the Restore job to open the Job Details for the job.
4. Browse the contents of the Job Overview, Detailed Status, and Job Hierarchy tabs
of the Job Details.
You should note the following items.
marked as Restore. The Client is console.example.com, the Master Server is
winmaster or lnxmaster. The Files List shows the files (/E/data/smallfiles/) being
restored.
(NetBackup Request Daemon). The Media Server used in this restore is winmaster
or lnxmaster. 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 Status
pane, 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.
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.
You have completed this restore operation.
Lab 5-31

6. Click the appropriate link to go to the exercise to perform an alternate client restore,
based on the operating system of your master server.
̶ If your master serve is the Windows-based, winmaster.example.com, continue

to Exercise D: Restoring client files to an alternate client system – Windows
(only).
̶ If your master server is the Linux-based, lnxmaster.example.com, continue to
Exercise E: Restoring client files to an alternate client system – Linux (only).
Lab 5-32

Exercise D: Restoring client files to an alternate
client system - Windows (only)
If your NetBackup master server and media server systems are the Linux-based systems,
lnxmaster.example.com and lnxmedia.example.com, proceed to Exercise E: Restoring
client files to an alternate client system – Linux (only).
Perform this exercise (Exercise D) only if your master server and media server are the
Windows-based systems, winmaster.example.com and winmedia.example.com.
In this exercise, you use the NetBackup Backup, Archive, and Restore (BAR) user
interface that is launched from the NetBackup Administration Console that is
connected to your Windows-based master server, winmaster.example.com, to restore
client file system data that was backed up from one Windows-based client system to an
alternate Windows-based client system, and monitor the restore operation using the
Task Progress user interface of the BAR user interface and the Activity Monitor.
Continue to Exercise D-1: Backing up your Windows-based media server system.

Lab 5-33

Exercise D-1: Backing up your Windows-based media
server system
In the steps that follow, you perform a manual full backup of the client on the system,
winmedia.example.com using the PRE-clients-to-master-advdisk policy.

3. Select the entry for the PRE-clients-to-master-advdisk policy in the All Polices pane
4. Under Actions, select Manual Backup in the Administration Console tool bar.
The Manual Backup window is displayed.
5. Click the entry for the client, winmedia.example.com, and then click OK, to initiate
the manual backup and to close the Manual Backup window.
6. Click the entry for the Activity Monitor in the left pane of the Administration
Console.
7. Monitor the most recent backup job of the winmedia.example.com client that used
the PRE-clients-to-master-advdisk policy.
8. Allow the backup job to run to completion.
9. Verify that the job completed successfully (status 0).
If the job fails, record the status code and seek assistance. Correct the problem and
re-run the manual backup job before continuing to the next step.
10. When the backup job completes successfully, continue to the next step.
Continue to Exercise D-2: Preparing the BAR user interface for an alternate client
restore.
Lab 5-34

Exercise D-2: Preparing the BAR user interface for an
alternate client restore
In the steps that follow you prepare the Backup, Archive, and Restore user interface to
perform a restore of files backed up from one Windows-based client
(winmedia.example.com) to another Windows-based client (winmaster.example.com).

2. Select the entry for the Backup, Archive, and Restore (BAR) user interface in the left
3. Select the Restore Files tab in the BAR user interface.
5. Use the information provided in the table below to select the parameters in the
Specify NetBackup Machines and Policy Type window.
Parameter Value

(Choose based upon your master server)
Source client for restores: winmedia.example.com
Destination client for restores: winmaster.example.com
The Specify NetBackup Machines and Policy Type window provides the key
settings that enable an alternate client restore operation.
You have selected to browse the master server image catalog to look for backup
images of the client, winmedia.example.com that will be restored to the client,
winmaster.example.com.
Lab 5-35

6. When you have entered the information from the table above in the Specify
NetBackup Machines and Policy Type window, click OK to save the settings and to
close the window.
7. Set the Restore type field of the BAR user interface to Normal Backups.
8. Select Actions and then select Set Date Range and Backup History.
The Backup History window is displayed.
9. Select the entry for the most recent Full Backup image that was created using the
PRE-clients-master-to-advdisk policy.
10. Click OK to save the Backup History selection, and to close the Backup History
window.
Based on your selections, the NetBackup client sends queries to the selected master
server to obtain a list of the contents of the selected backup image.
11. Note that the Directory Structure pane of the BAR user interface displays an entry
for the contents of the backup image for the source client system,
Continue to Exercise D-3: Selecting the folders and files to restore.

Lab 5-36

Exercise D-3: Selecting the folders and files to restore
In the steps that follow, you select the folders and files that will be restored.
1. In the Directory Structure pane, click the symbol (located to the left of the client
name) to expand the entry for the winmedia.example.com client.
An entry for the E drive is displayed in the Directory Structure pane.
2. Click to expand the entry for the E drive in the Directory Structure pane and display
an entry for the data folder is displayed in the Directory Structure pane.
The sub-folders of the data folder are displayed in the Directory Structure pane.
4. Click the entry for the Doc_files folder, located in the Directory Structure pane.
5. Note that the contents of the Doc_files folder are displayed in the Contents of the
selected directory pane of the BAR user interface.
There are ten files in the Doc_files folder that were backed up.
6. Click the check box, located to the left of the Doc_files entry in the Directory
Structure pane, to select that folder and its contents for restore.
7. Note that the Doc_files folder and all of its contents (as shown in the Contents of
the selected directory pane) are marked for restore.
8. Click the Preview button on the BAR user interface, to preview the media that will
be required for the restore operation.
Within a moment, the Media Required dialog box is displayed, indicating that the
backup images or images that are to be used for this restore operation are housed
on disk-based storage, and that no media (tapes) are required.
9. Click OK to close the Media Required dialog box.
10. Allow the NetBackup Administration Console window (and the BAR user interface)
to remain open on console.example.com. You return to this window in a few
moments.
Continue to Exercise D-4: Viewing the folders on the alternate client system.
Lab 5-37

Exercise D-4: Viewing the folders on the alternate client
system
In the steps that follow, you briefly view the drive and folder location on the alternate
client system to which the restore files will be written.
1. Access the desktop of your Windows-based master server,

You can use either of two methods to access the desktop of

winmaster.example.com:
̶ You can locate and double-click the REMOTE SYSTEM ACCESS folder, located on
the desktop of console.example.com to open that folder. In the REMOTE
SYSTEM ACCESS folder, double-click to open the RDP Profiles (Windows
systems) folder. In the RDP Profiles (Windows systems) folder, double-click the
winmaster.rdp file to open an RDP session to winmaster.example.com.
̶ Click the winmaster tab provided on the user interface for your lab kit.
2. Log in to the winmaster.example.com, using the credentials provided above.
3. Double-click the File Explorer shortcut, located on desktop of

4. Double-click the entry for the DATA (E:) drive, displayed in the left pane of the File
Explorer window.
5. Note that an entry for the data folder is displayed in the right pane of the File
Explorer window.
In this restore operation, you restore data that was backed up from the Doc_files
folder on the client, winmedia.example.com, to the DATA (E:) drive of the client
system, winmaster.example.com.
6. Allow the File Explorer window to remain open on winmaster.example.com. You

return to this window in a few moments
Continue to Exercise D-5: Performing the alternate client restore.
Lab 5-38

Exercise D-5: Performing the alternate client restore
In the steps that follow, you initiate the restore of the selected client files (from
winmedia.example.com) to the selected alternate client system.
1. Access the desktop of console.example.com.

The Backup, Archive, and Restore user interface is displayed in the right pane of the
Administration Console, with the Doc_files folder and its contents already selected
for restore.
You can also select Actions > Restore.
4. Make the following selections in the Restore Marked Files window:

Destination: E:\alternate-client-data\Doc_files
̶ Options, and all other settings (no changes – use defaults)
5. After making the changes to the Restore Marked Files parameter settings, as
described in the previous step, click the Start Restore button.
Within moments the View Progress dialog box is displayed.
Continue to Exercise D-6: Viewing the restore in the Task Progress tab.
Lab 5-39

Exercise D-6: Viewing the restore in the Task Progress tab
1. Click Yes in the View Progress dialog box to view the progress of the restore
operation.
The Task Progress tab of the BAR user interface is automatically selected.
2. Locate and click the entry for the most recent Restore job in the Tasks Performed
3. Mark the Full Contents check box, if it not already marked, to see detailed
information about the restore operation in the Results of the Task Selected Above
4. Verify that the Restore task runs to successful completion.
If the Restore fails, record the status and seek assistance.
5. Scroll through the message displayed in the Results of the Task Selected Above
pane, until you reach the bottom of the pane.
6. Take note of the messages indicating the number of files that were restored
successfully.
7. Allow the Administration Console window and the BAR user interface to remain
open on console.example.com. You return to this window in a few moments.
Continue to Exercise D-7: Viewing the restored files on the alternate client.
Lab 5-40

Exercise D-7: Viewing restored files on the alternate
client
In the steps that follow, you view the folder and files that were restored to the alternate
client system, winmaster.example.com.
1. Access the desktop of the master server system, winmaster.example.com.
winmaster.example.com is also the client system to which the files were restored in
the most recent restore operation.
2. Access the open File Explorer window on winmaster.example.com.
3. Navigate to E:\ in the File Explorer window.
4. Note that the alternate-client-data folder is present in E:\.
This folder was restored to the winmaster.example.com system by the alternate

client restore operation.
5. Double-click the alternate-client-data folder, to open the folder.
6. Note that the alternate-client-data folder contains the Doc_files folder.
7. Double-click the Doc_files folder, to open the folder.

8. Verify that there are ten files present in the E:\alternate-client-data\Doc_files

folder.
9. Close the File Explorer window on winmaster.example.com.
Continue to Exercise D-8: Viewing the restore job in the Activity Monitor.
Lab 5-41

Exercise D-8: Viewing the restore job in the Activity
Monitor
In the steps that follow, you view the entry for the most recent Restore job in the

3. Select the entry for the Activity Monitor in the left pane of the Administration
Console window.
4. Locate the Jobs tab entry for the most recent Restore job.
5. Verify that the Restore job restored data to the client, winmaster.example.com.
6. Double-click the entry for the Restore job, to open the Job Details for the job.
7. Browse the Job Details for the job, including the contents of the Job Overview,
Detailed Status, and Job Hierarchy tabs.
Some items to make note of.

marked as Restore. The Client is winmaster.example.com, the Master Server is
winmaster.example.com. The Files List shows the files (/E/data/Doc_files) being
restored.
(NetBackup Request Daemon). The Media Server used in this restore is
winmaster.example.com. 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 Status pane, 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.
Lab 5-42

From the Status pane look at the third (3rd) line entry, “restoring from image
winmedia.example.com_XXXXXXXXXX”. This is about the only reference to the name
of the host in which this data was backed up.
You have completed the alternate client restore operation.
Continue to Exercise D-9: Deactivating policies on the master server.

Lab 5-43

Exercise D-9: Deactivating policies on the winmaster
master server
In the steps that follow, you deactivate polices that you created in the this and previous
lab activities, to prevent the automatic initiation of backup jobs by these policies.
You perform these steps to prevent writing backup jobs to NetBackup storage –
to avoid the potential of filling the limited backup storage image space that is
available.
2. Select Policies in the left pane of the Administration Console window.
3. Right-click on the LAB03-clients-to-master-bdisk policy entry, and select Deactivate.
4. Right-click on the LAB03-console-to-master-advdisk policy entry, and select

Deactivate.
5. Verify that the LAB03-clients-to-master-bdisk and LAB03-console-to-master-

advdisk policies have been de-activated.
When a NetBackup policy is de-activated, the entry for the policy is greyed-out
in the policy list, and is marked with a red x.
You have completed all Windows-based

required tasks for this lab activity.
Exercise F is an optional exercise, providing you with exposure to the use of the
OpsCenter operational restore feature that enables the restore of client files using the
OpsCenter user interface.
Proceed to Optional Exercise F: Using the OpsCenter Operational Restore feature.
Lab 5-44

Exercise E: Restoring client files to an alternate
client system - Linux (only)
If your NetBackup master server and media server systems are the Linux-based systems,
lnxmaster.example.com and lnxmedia.example.com, complete the steps of this
exercise to perform an alternate client restore for a Linux-based client. Continue to
“Backing up your Linux-based media server system” below.
If your NetBackup master server and media server systems are the Windows-based
systems, winmaster.example.com and winmedia.example.com, and you have not
performed an alternate client restore for a Windows-based client, proceed to Exercise
D: Restoring client files to an alternate client system – Windows (only).
If you have completed Exercise D, skip this exercise and proceed to Exercise F: Using the
OpsCenter Operational Restore feature.
Perform this exercise (Exercise E) only if your master server and media server are the
Linux-based systems, lnxmaster.example.com and lnxmedia.example.com.
Continue to Exercise E-1: Backing up your Linux-based media server system.

Lab 5-45

Exercise E-1: Backing up your Linux-based media server
system
In the steps that follow, you perform a manual full backup of the client on the system,
lnxmedia.example.com using the PRE-clients-to-master-advdisk policy.

3. Select the entry for the PRE-clients-to-master-advdisk policy in the All Policies pane
4. Select Actions and then Manual Backup in the Administration Console tool bar.
5. In the Manual Backup window, click the entry for the client,
lnxmedia.example.com. Then click OK, to initiate the manual backup.
6. Click the entry for the Activity Monitor in the left pane of the Administration
Console.
7. Monitor the most recent backup job of the lnxmedia.example.com client that used
the PRE-clients-to-master-advdisk policy.
9. Verify that the job completed successfully (status 0).
If the job fails, record the status code and seek assistance. Correct the problem and
re-run the manual backup job before continuing to the next step.
10. When the backup job completes successfully, continue to the next step.
Continue to Exercise E-2: Preparing the BAR user interface for an alternate client
restore.
Lab 5-46

Exercise E-2: Preparing the BAR user interface for an
alternate client restore
In the steps that follow you prepare the Backup, Archive, and Restore user interface to
perform a restore of files backed up from one Linux-based client
(lnxmedia.example.com) to another Linux-based client (lnxmaster.example.com).

2. Select the entry for the Backup, Archive, and Restore (BAR) user interface in the left
3. Select the Restore Files tab in the BAR user interface.
5. Use the information provided in the table below to select the parameters in the
Parameter Value
Server to use for backups and restores: lnxmaster.example.com

(Choose based upon your master server)
Source client for restores: lnxmedia.example.com
Destination client for restores: lnxmaster.example.com
Policy Type for restores: Standard
The Specify NetBackup Machines and Policy Type window provides the key
settings that enable an alternate client restore operation.
You have selected to browse the master server image catalog to look for backup
images of the client, lnxmedia.example.com that will be restored to the client,
Lab 5-47

6. When you have entered the information in the Specify NetBackup Machines and
Policy Type window, click OK to save the settings and to close the window.
7. Verify / (slash) is listed the Browse directory field.
8. Verify the Restore type field of the BAR user interface is set to Normal Backups.
9. Select the Backup History date range.
The Backup History window is displayed.
10. Select the entry for the most recent Full Backup image that was created using the
PRE-clients-master-to-advdisk policy.
11. Click OK to save the Backup History selection, and to close the Backup History
window.
Based on your selections, the NetBackup client sends queries to the selected master
server to obtain a list of the contents of the selected backup image.
12. Note that the Directory Structure pane of the BAR user interface displays an entry
for the contents of the backup image for the source client system,
Continue to Exercise E-3: Selecting the directories and files to restore.

Lab 5-48

Exercise E-3: Selecting the directories and files to restore
In the steps that follow, you select the directories and files that will be restored.
1. In the Directory Structure pane, click the symbol (located to the left of the root
directory (/) to expand the entry for the directory.
An entry for the data directory is displayed in the Directory Structure pane.
2. Click to expand the entry for the data directory in the Directory Structure pane.
The sub-folders of the data directory are displayed in the Directory Structure pane.
3. Click the entry for the Doc_files directory, located in the Directory Structure pane.
4. Note that the contents of the Doc_files directory are displayed in the Contents of
the selected directory pane of the BAR user interface.
There are ten files in the Doc_files directory that were backed up.
5. Click the check box, located to the left of the Doc_files entry in the Directory
Structure pane, to select that directory and its contents for restore.
6. Note that the Doc_files directory and all of its contents (as shown in the Contents of
the selected directory pane) are marked for restore.
You are ready to initiate the restore operation.
7. Allow the NetBackup Administration Console window (and the BAR user interface)
to remain open on console.example.com. You return to this window in a few

moments.
Continue to Exercise E-4: Viewing the folders on the alternate client system.
Lab 5-49

Exercise E-4: Viewing the folders on the alternate client
system
In the steps that follow, you briefly view the drive and folder location on the alternate
client system to which the restore files will be written.
1. Access your Linux-based master server, lnxmaster.example.com.
To do so, locate and double-click the REMOTE SYSTEM ACCESS folder on the
desktop of console.example.com. Then, in the REMOTE SYSTEM ACCESS folder,
locate and double-click the PuTTY entry. When the PuTTY Configuration window is
opened, double-click the entry for lnxmaster.example.com to open an SSH session
with the Linux-based lnxmaster.example.com master server system.
2. Log in to lnxmaster.example.com using the credentials provided above.
3. In the PuTTY (root@lnxmaster) window, type the command shown below, and press
Enter.
Command: ls –l / | grep data
The output of the ls command is illustrated in the figure below.

In this restore operation, you restore data that was backed up from the Doc_files
directory on the client, lnxmedia.example.com, to the /alternate-client-data
directory on the client system, lnxmaster.example.com. As you can see in the
output of the command in figure above, the /alternate-client-data directory does
not currently exist on lnxmaster.example.com.
Lab 5-50

4. Allow the PuTTY (root@lnxmaster) window to remain open on
lnxmaster.example.com. You return to this window in a few moments.
Continue to Exercise E-5: Performing the alternate client restore.

Lab 5-51

Exercise E-5: Performing the alternate client restore
In the steps that follow, you initiate the restore of the selected client files (from
lnxmedia.example.com) to the selected alternate client system.

The Backup, Archive, and Restore user interface is displayed in the right pane of the
Administration Console, with the Doc_files folder and its contents already selected
for restore.
Actions > Restore
4. Make the following selections in the Restore Marked Files window:

̶ Destination: /alternate-client-data/Doc_files
̶ Options, and all other settings (no changes – use defaults)
5. After making the changes to the Restore Marked Files parameter settings, as
described in the previous step, click the Start Restore button.
Within moments the View Progress dialog box is displayed.
Continue to Exercise E-6: Viewing the restore in the Task Progress tab.
Lab 5-52

Exercise E-6: Viewing the restore in the Task Progress tab
The Task Progress tab of the BAR user interface is automatically selected.
2. Verify the entry for the most recent Restore job in the Tasks Performed pane of the
Task Progress tab.
3. Verify the Full Contents check box is selected. This provides detailed information
about the restore operation in the Results of the Task Selected Above pane of the
Task Progress tab.
4. Verify that the Restore task runs to successful completion.
If the Restore fails, record the status and notify your instructor.
5. Scroll through the message displayed in the Results of the Task Selected Above
pane, until you reach the bottom of the pane.
6. Take note of the messages indicating the number of files that were restored
successfully.
7. Allow the Administration Console window and the BAR user interface to remain
open on console.example.com. You return to this window in a few moments.
Continue to Exercise E-7: Viewing the restored files on the alternate client.
Lab 5-53

Exercise E-7: Viewing restored files on the alternate client
In the steps that follow, you view the directory and files that were restored to the
alternate client system, lnxmaster.example.com.
1. Access the open PuTTY (root@lnxmaster) window on console.example.com that is

connected and logged on to lnxmaster.example.com.
lnxmaster.example.com is the alternate client system to which the files were

restored in the most recent restore operation.
2. In the terminal window, type the command shown below, and press Enter.
Command: ls –l / | grep data
3. Note the output of the ls command, as illustrated in the figure below.
4. Note that following the most recent restore operation, the /alternate-client-data
directory is present on the lnxmaster.example.com system.
5. In the terminal window, type the command shown below, and press Enter.
Command: ls –R /alternate-client-data
Lab 5-54

6. Note the output of the ls command, as illustrated in the figure below.
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
7. Close the PuTTY (root@lnxmaster) window that is connected to

lnxmaster.example.com. (Type exit, and press Enter.)
Continue to Exercise E-8: Viewing the restore job in the Activity Monitor.
Lab 5-55

Exercise E-8: Viewing the restore job in the Activity
Monitor

Console window.
4. Locate the Jobs tab entry for the most recent Restore job.
5. Verify that the Restore job restored data to the client, lnxmaster.example.com.
Your observations will vary, however, here are some items to make note of.
marked as Restore. The Client is lnxmaster.example.com, the Master Server is
lnxmaster.example.com. The Files List shows the files (/data/Doc_files) being
restored.
(NetBackup Request Daemon). The Media Server used in this restore is
lnxmaster.example.com. 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 Status pane, 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.
Lab 5-56

From the Status pane look at the third (3rd) line entry, “restoring from image
lnxmedia.example.com_XXXXXXXXXX”. This is about the only reference to the
name of the host in which this data was backed up.
You have completed the alternate client restore operation.
Continue to Exercise E-9: Deactivating policies on the master server.

Lab 5-57

Exercise E-9: Deactivating policies on the lnxmaster
master server
In the steps that follow, you deactivate polices that you created in the this and previous
lab activities, to prevent the automatic initiation of backup jobs by these policies.
You perform these steps to prevent writing backup jobs to NetBackup storage –
to avoid the potential of filling the limited backup storage image space that is
available.
3. Right-click on the LAB03-clients-to-master-bdisk policy entry, and select Deactivate.
4. Right-click on the LAB03-console-to-master-advdisk policy entry, and select

Deactivate.
5. Verify that the LAB03-clients-to-master-bdisk and LAB03-console-to-master-

advdisk policies have been de-activated.
When a NetBackup policy is de-activated, the entry for the policy is greyed-out
in the policy list, and is marked with a red x.
You have completed all the Linux-based

required tasks for this lab activity.
Exercise F is an optional exercise, providing you with exposure to the use of the
OpsCenter operational restore feature that enables the restore of client files using the
OpsCenter user interface.
If you wish to complete the optional exercise, click the link to proceed to Exercise F:
Using the OpsCenter Operational Restore feature.
Lab 5-58

Exercise F: (Optional) Using the OpsCenter
Operational Restore feature
In this optional exercise, you use the Operational Restore interface provided in
OpsCenter 8.0 to perform the restore of file system data to a Windows-based client
system.
Continue to Exercise F-1: Preparing for a restore to a Windows-based client system.

Lab 5-59

Exercise F-1: Preparing for a restore to a Windows-based
client system
In the following steps, you view the files and directories on the client system,
console.example.com, in preparation for performing a restore of client data.
1. Access the desktop of the Windows-based client, console.example.com.
2. Double-click the File Explorer shortcut, located on the desktop.
3. Double-click the entry for the DATA( E:) disk drive in the File Explorer window.
Take note of the contents of the E:\ drive.
Currently, three sub-folders exist on the E:\ drive:
̶ alternate-directory
̶ data
̶ FILESHARE
4. Allow the File Explorer window to remain open on the client. You return to this
window in a few moments to verify the results of the restore operation.
Continue to Exercise F-2: Starting the OpsCenter Server services.

Lab 5-60

Exercise F-2: Starting the OpsCenter Server services
In the steps that follow you start the OpsCenter Server services on
Because OpsCenter is used infrequently in lab activities of this course, the

OpsCenter Server services are stopped by default on console.example.com in
order to conserve system resources and optimize system performance.
To perform OpsCenter operations, you must first start the OpsCenter Server
services.
1. Access the desktop of the console.example.com system
2. Locate and double-click the OPSCENTER folder located on the desktop of

3. In the OPSCENTER folder, locate and right-click the opsadmin start.bat file,
and then click Run as Administrator in the resulting menu, as shown in the figure.
Executing the opscenter start.bat batch file opens a Command Prompt

window. When the batch file has run, the Command Prompt window closes
automatically.
Lab 5-61

It has been observed that, under certain conditions (i.e., high usage/loads in
the lab delivery environment) that the OpsCenter services can take a long time
to start on the console.example.com system, and to become ready for use.
If you encounter a situation where launching the Web browser to connect to
the OpsCenter Server takes a long time to complete, you may wish to skip the
optional lab exercise for now, and return to it at a later time.
Continue to Exercise F-3: Restoring client folders and files with OpsCenter.
Lab 5-62

Exercise F-3: Restoring client folders and files with
OpsCenter
In the steps that follow, you use the OpsCenter Web interface to browse for, select, and
restore client folders and files to a Windows-based client system.
1. Locate and double-click the OpsCenter WebUI Login shortcut, located in the
OPSCENTER folder, to launch the OpsCenter Web Interface in a Mozilla Firefox Web
browser window.
It may take a few moments for the browser to display the next screen.
2. A “This Connections is Untrusted” dialog box may be displayed. If this happens, click
the “I Understand the Risks” link, and continue to the next step.
If this screen is not displayed, skip to step 5 of this exercise.
3. Click the Add Exception button that is added to the “This Connections is Untrusted”
dialog box.
4. When the Add Security Exception window is displayed, click the Confirm Security
Exception button.
5. When the Veritas NetBackup OpsCenter Version 8.0 log on screen is displayed, log
on to OpsCenter using the following credentials:
̶ Username: admin
Password: Tra1n!ng ( Note: password is “ T r a 1 n ! n g “)
̶
̶ Domain: OpsCenterUsers(vx)
If the Domain field of the log on page is blank, you may be unable to log on
successfully. This can be an indication that the OpsCenter server services are
not running on the OpsCenter server system. Try restarting the OpsCenter
services. If you are still having issues, notify your instructor.
OpsCenter requires the use of complex passwords. The password is case-

sensitive.
After logging on, the OpsCenter Web interface is displayed.
6. Select the Manage tab.
Lab 5-63

7. Select the Restore sub-tab (under the Manage tab).
The “What do you want to restore?” page is displayed.
8. Click the Restore Files and Directories link.
The Files and Directories Restore screen is displayed.
9. Under the Select files or directories tab, and the Search sub-tab (these tabs are
selected by default), click the Browse and select clients link, highlighted in the
figure.
The Browse and select client window is displayed.

Lab 5-64

10. In the Browse and select client window, click the plus (+) symbol to the left of the
entry for your master server (winmaster OR lnxmaster), as illustrated in the figure.
You may only see your master server listed, which is ok. This is because the
other master server host is shutdown.
The list of clients that have been backed up by your master server is displayed in the
Browse Clients window.
11. Click the check box to the left of the entry for the console.example.com client. The
entry is displayed as below, depending on your master server (the master server
name is enclosed in parentheses following the client name):
̶ console.example.com (winmaster.example.com)
̶ console.example.com (lnxmaster.example.com)
Verify that the check box for console.example.com (your master server name) is
marked (checked).
12. Click OK to close the Browse Clients screen.
You are returned to the Files and Directories Restore screen.
Lab 5-65

13. Note that the name of the selected client, console.example.com, is displayed under
the Client Name entry on the screen, as illustrated in item #1 in the figure below.
14. In the File or Directory name field, illustrated as item #2 in the figure above, type
Doc_files.

Lab 5-66

15. Click Search.
When the search operation completes, OpsCenter displays the search results at the
bottom of the Select files or directories tab, as illustrated in the figure below.
Depending upon your screen resolution, it may be necessary to scroll down in

the OpsCenter Web interface to see the search results.
Note that an entry for the Doc_files folder is displayed in the search results,
as illustrated in the figure above.
16. Click the Backup History Selection link located in the Backup History column, as
illustrated in the figure above.
The Backup Timeline window is displayed, and provides a history of the backup
images that contain the directory or file name that you included in your search
criteria (in this example, Doc_files).
17. Note the three tabs that can be selected in the Backup Timeline screen:
̶ Day (the default selection)

̶ Week
̶ Month
Lab 5-67

18. Click the Week tab in the Backup Timeline window.
As a result, OpsCenter searches its catalogs and, after a short time, updates the Backup
Timeline window contents to display a graphic representation (icon) for each of the
backup images of the selected client that were created in the last week, and that
contain the directory or file that was included in the search criteria (Doc_files), as
The backup administrator can select any backup image to use as the source for
a restore operation (by clicking on the icon for the backup image on the backup
timeline).
The icon legend for the Backup Timeline identifies the type of media on which
each of the backup images is resident.
19. Click the entry or icon for the most recent backup image of the client that is listed in
the Backup Timeline, as illustrated in the figure above.
20. Note that the Details of Selection pane, located on the bottom half of the Backup
Timeline screen, displays information about the selected backup image. The radio
buttons associated with the entries for the backup image are automatically selected.
Lab 5-68

21. Click the Add to Restore Cart and Close button in the Backup Timeline window.
You are returned to the Files and Directories Restore screen.
22. Click the Restore Cart tab, as illustrated in the figure below.
The Restore Cart is displayed. The Restore Cart contains entries for all directories
and files that have been selected for restore.
The Restore Cart can contain entries selected from multiple backup images
which may originate from the same client or from multiple client systems. If
there are multiple entries in the Restore Cart and you select multiple entries
for restore, NetBackup will initiate multiple restore jobs to restore the selected
directories and files, as needed.
Entries in the Restore Cart are not selected for restore by default because the
backup administrator may wish to selectively restore the entries rather than to
initiate the restores all at one time.
The Restore Cart for this restore scenario is illustrated in the figure below. The
figure below may differ from your lab environment.
Lab 5-69

23. Click the check box for the entry for the Doc_files folder that is displayed in the
Restore Cart, as illustrated in the figure above.
The Doc_files folder entry check box is marked for restore.
24. Click Restore now button, located at the bottom of the Restore Cart screen.
It may be necessary to scroll down (or resize browser window) to see the
Restore now button.
The Restore Options screen is displayed.
25. Click the radio button to Restore all files and directories to an alternate path
location (maintaining the existing structure) on source or alternate client.
26. Enter the following parameters in the fields provided under the Restore all files and
directories to an alternate path location... entry:
̶ Specify client: console.example.com

̶ Specify file path: E:\opsc-restore
(Do not use the Browse button to select the file path as the path does not exist and
will be created at time of restore.)
Lab 5-70

27. Click Next to continue.
The List of selected files or directories for restore pane is displayed in the figure.
The figure below may differ from your lab environment.
28. Click the Restore button.
The File or Directory Restore Launch Status dialog box is displayed, as illustrated in
the figure below. The figure below may differ from your lab environment.
29. Note the Job ID of the restore job that was initiated.
30. Click OK to close the File or Directory Restore Launch Status window.
31. Note that OpsCenter automatically takes you to the Monitor > Jobs tab.
32. Locate the Job ID associated with the restore job.
If the entry for the Job ID is not displayed in Monitor > Jobs, refresh your Web
browser (press F5).
33. Monitor the entry for the restore Job ID until OpsCenter reports a job State of Done.
Lab 5-71

34. Verify that the restore job runs to successful completion.
If the job fails, record the status code and notify your instructor.
35. Click Logout to log out of OpsCenter, as illustrated in the figure below.
36. Close the Web browser window on console.example.com.
37. You have just completed the restore of a folder and its contents to the client,
console.example.com, using the OpsCenter Web user interface.
Continue to Exercise F-4: Verifying the restore of the client files.

Lab 5-72

Exercise F-4: Verifying the restore of the client files
In the following steps, you verify that the folder and files have been restored to the
specified folder location on the client system, console.example.com.
1. Access the desktop of the client system, console.example.com.
2. Access the File Explorer window on the client system. This window is open from
previous steps in this lab exercise.
3. Navigate to the E:\ folder in the File Explorer window.
4. Refresh the contents of the File Explorer window.
5. Verify that the opsc-restore folder is present in the DATA(E:) folder, as

6. Double-click the E:\opsc-restore folder, to open the folder.
Note that the E:\opsc-restore folder contains the Doc_files sub-folder.
Lab 5-73

7. Double-click the E:\opsc-restore\Doc_files folder, to view the contents of
the folder.
File Explorer can be slow to refresh. If the restored files are not immediately
visible, try closing the window and opening a new File Explorer window.
It is anticipated that the restore operation that was initiated using the
Operational Restore capability was completed successfully. If the restore was
not successful, notify your instructor.
8. Close the File Explorer window on the console.example.com system.
Continue to Exercise F-5: Viewing the restore job in the Activity Monitor.
Lab 5-74

Exercise F-5: Viewing the restore job in the Activity
Monitor

Console window.
4. Locate the Jobs tab entry for the most recent Restore job that restored data to the
console.example.com client, and verify that the Restore job was completed
successfully (status 0).

Continue to Exercise F-6: Stopping the OpsCenter Server services.
Lab 5-75

Exercise F-6: Stopping the OpsCenter Server services
In the steps that follow, you stop the OpsCenter Server services that are running on the
In this training lab environment, we stop the OpsCenter Server services to

conserve the limited system resources on console.example.com, so as to
optimize system performance.
1. Locate and double-click the OPSCENTER folder, located on the desktop of

console.example.com, to open the folder.
2. Locate and right-click the opsadmin stop.bat file in the OPSCENTER folder.
3. In the resulting menu, click, Run as Administrator, to run the batch file.
Executing the opscenter stop.bat batch file opens a Command Prompt

automatically.
The OpsCenter Server-related services are stopped on console.example.com.
You have completed the optional exercise for this lab activity.
Lab 5-76

Lab 6: Configuring Disk Pools
In this lab, you perform tasks to configure AdvancedDisk storage, perform and monitor
backups that write to AdvancedDisk storage, and use various NetBackup-provided user
interfaces to view, manage, and monitor AdvancedDisk storage.
Proceed to Exercise A: Identifying AdvancedDisk storage.
Lab 6-1

Exercise A: Identifying 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.
• If you are performing this lab on Windows-based NetBackup server systems,

continue to the Exercise A-1: Viewing disk storage on a NetBackup Windows-based
media server system .
• If you are performing this lab on Linux-based NetBackup server systems, continue to
the Exercise A-2: Viewing disk storage on a NetBackup Linux-based media server
system.
Lab 6-2

Windows-based master server system
In this lab exercise you will connect to a remote Windows-based media server lab
systems, locate and double-click the RDP Profiles (Windows systems) sub-folder, and

4. To open a Remote Desktop connection to the Windows-based system,

winmedia.example.com, locate and double-click the RDP file (winmedia.rdp).
5. Log on to your media server using the credentials provided in the table below.

winmedia.example.com UserID: EXAMPLE\Administrator Password: train
Lab 6-3

6. Locate and double-click the File Explorer shortcut, located on the desktop of
winmedia.example.com. See the figure below.
for NetBackup backup images. Take note specifically of the disk volumes labelled as
ADVDISK1 (G), ADVDISK2 (H), and ADVDISK3 (I).
9. Sign out of the Windows media server.
Proceed to Exercise B: Configuring AdvancedDisk.
Lab 6-4

based media server system
In this lab exercise you will connect to a remote Linux-based media server system using
the Putty shortcut located in the REMOTE SYSTEM ACCESS folder on the console, and

4. To connect to the Linux-based lab system, double-click the Putty shortcut located in
the REMOTE SYSTEM ACCESS folder.
5. Locate and double-click the pre-configured entry for the Linux-based master server,
6. Log on to your Linux media server using the credentials provided in the table below.

Linux-based lnxmedia.example.com root train
lnxmedia.example.com User ID: root Password: train
root@lnxmedia ~]# df -h
Lab 6-5

mount points on the lnxmedia system. Many of these file systems were pre-
configured to serve as storage destinations for NetBackup backup images.
8. Take note of the /dev/sda7, /dev/sda8, and /dev/sda9 file systems,

and their associated mount points, /advdisk1, /advdisk2, and
/advdisk3.
9. Type Exit to close the PuTTY window.

Proceed to Exercise B: Configuring AdvancedDisk.
Lab 6-6

Exercise B: Configuring AdvancedDisk
Configuring NetBackup to enable the AdvancedDisk feature consists of three primary

steps:
• Configuring an AdvancedDisk storage server.

• Configuring an AdvancedDisk disk pool.
• Configuring an AdvancedDisk storage unit.
In this exercise, you perform each of these primary steps.
Continue to Exercise B-1: Configuring an AdvancedDisk storage server.

Lab 6-7

Exercise B-1: Configuring an AdvancedDisk storage server
In the steps that follow, you use the Configure Disk Storage Server wizard to create an
AdvancedDisk storage server.
2. Log on (if necessary) to console.example.com, using the credentials provided above.

console.example.com. If no Administration Console window is open, see the Note.

NetBackup 8.1 Admin Console icon, located on the desktop of the
Administration Console login screen using the information in the table.

4. Click the top entry in the left pane of the NetBackup Administration Console
window (the top entry should be the name of your master server).
The right pane of the Administration Console displays a list of the NetBackup wizards
that are available on a master server system.
Lab 6-8

5. Click the entry for the Configure Disk Storage Servers wizard, located in the right
pane of the Administration Console, as illustrated in the figure below.
A Storage Server Configuration Wizard window is displayed.
6. Identify the types of disk storage options that are available for selection.
The disk storage types are listed in the table below.
Types of disk storage that are available for selection:

AdvancedDisk
Media Server Deduplication Pool
OpenStorage
PureDisk Deduplication Pool
7. Verify the radio button is selected for AdvancedDisk.
The Storage Server Configuration Wizard displays the Add Storage Server window.
Lab 6-9

9. Use the information provided in the appropriate table rows below to enter the
information in the fields of the Add Storage Server screen.
Choose the information to enter based upon the operating system of your media
server – Windows (use top rows of the table), or Linux (bottom rows of the table).
If you have a Windows-based media server:

Add Storage Server parameter: Parameter setting:
Media server: winmedia.example.com
Storage server type: AdvancedDisk (default)
Storage server name: winmedia.example.com (default)
If you have a Linux-based media server:

Add Storage Server parameter: Parameter setting:
Media server: lnxmedia.example.com
Storage server type: AdvancedDisk (default)
Storage sever name: lnxmedia.example.com (default)
10. After entering the information in the previous table click Next to continue.
The Storage Server Summary screen is displayed, as illustrated below.

11. Verify the information displayed on the summary screen, then the click Next button,
located near the bottom of the wizard window.
Lab 6-10

The configuration wizard creates the storage server. This may take a few moments.
When the creation of the storage server is completed, the Storage server
“xxxmedia.example.com” is successfully created message is displayed, and the
Next button becomes available for selection, as illustrated in the figure below.
12. Verify that the “storage server is successfully created” message is displayed.
13. Note the check box on the Storage Server Configuration Status screen.
If the check box is marked, when you click Next, the wizard continues on to enable
the configuration of an AdvancedDisk disk pool.
14. Click Next to continue to the configuration of the disk pool.
Continue to Exercise B-2: Configuring an AdvancedDisk disk pool.
Lab 6-11

Exercise B-2: Configuring an AdvancedDisk disk pool
In the steps that follow, you continue the use of the Storage Server Configuration
Wizard to create an AdvancedDisk disk pool.
When you continue from the Storage Server Configuration Wizard to the creation of a
disk pool, the wizard displays the Volume Selection screen. See the figures below for
illustrations of the Volume Selection screens.
The figure below illustrates a screen shot of the Volume Selection screen for the
Windows-based media server, winmedia.example.com.
Lab 6-12

The figure below illustrates the Volume Selection screen for the Linux-based media
server, lnxmedia.example.com.
1. Using the information provided in the table below, mark the check boxes for the disk
volumes to be used for the AdvancedDisk disk pool.
Storage Server name First disk volume Second disk volume

winmedia.example.com G:\ H:\
lnxmedia.example.com /advdisk1 /advdisk2
2. After selecting the volumes indicated in the table above, click Next to continue.
The Additional Disk Pool Information screen is displayed.
Lab 6-13

3. Using the values provided in the table below, enter the information in the fields of
the Additional Disk Pool Information screen.
Storage server type: AdvancedDisk

Disk Pool name: media_advdisk_dpool
Comments: AdvancedDisk disk pool on media server
High water mark: 98% (default setting)
Low water mark: 80% (default setting)
Limit I/O streams: Selected (mark the check box)
# of streams per volume: 2 per volume
4. After entering the parameter values in the fields of the Additional Disk Pool
Information screen, click Next to continue.
The Disk Pool Configuration Summary screen is displayed.

5. Verify the information displayed in the configuration summary is correct, and then
click Next to continue.
The Disk Pool Configuration Status screen is displayed. It may take a moment for
the creation of the disk pool to be completed.
Lab 6-14

6. When the creation of the disk pool is completed, the message “Disk pool
“media_advdisk_dpool” has been successfully created” is displayed, as illustrated
in the figure below.
7. Verify that the “Disk pool “media_advdisk_dpool” has been successfully created”
message is displayed before continuing.
If the check box on the Disk Pool Configuration Status screen is marked (the
default condition of the check box) – as illustrated in the figure above - when
you click Next, the Storage Server Configuration Wizard enables the
configuration of a storage unit.
8. Click Next to continue to the creation of a storage unit that is associated with the
disk pool that you have just configured.
Continue to Exercise B-3: Configuring an AdvancedDisk storage unit.
Lab 6-15

Exercise B-3: Configuring an AdvancedDisk storage unit
In the next steps, you use the Storage Server Configuration Wizard to create a storage
unit that is associated with the AdvancedDisk disk pool that you configured.
After clicking Next on the Disk Pool Configuration Status screen, the Storage Server
Configuration Wizard displays the Storage Unit Creation screen, as illustrated in the
figure below.
1. Verify that the Storage Unit Creation screen is displayed, and then proceed to the
next step.
Lab 6-16

2. Use the parameter values provided in the table below, to populate the fields of the
Storage Unit Creation screen.
Parameter Parameter setting

Disk pool: media_advdisk_dpool (cannot change)
Storage server type: AdvancedDisk (cannot change)
Storage unit name: media_advdisk_stu (change from the default name)
Media Server entries:
Use any available Not selected
media server…
Only use the Selected
selected media
server:
Media Servers: Select > winmedia.example.com (Windows-based)
or
Select > lnxmedia.example.com (Linux-based)
Maximum concurrent jobs: 4 (change from the default setting)
Maximum fragment size: 524288 Megabytes (default setting)
3. When you have entered the storage unit parameters in the Storage Unit Creation
screen, click Next to continue.
The Finished screen is displayed.
If successful, the message “You have successfully completed the NetBackup Disk
Pool Configuration Wizard” is displayed.
4. Verify that the “successful” message is displayed.
5. Click Finish to close the Storage Server Configuration Wizard window.
Proceed to Exercise C: Verifying AdvancedDisk configuration.
Lab 6-17

Exercise C: Verifying AdvancedDisk configuration
In this exercise, you verify the configuration of the AdvancedDisk storage server, disk
pool, and storage unit that you created in the previous exercise.
Continue to Exercise C-1: Verifying AdvancedDisk storage server configuration using the
Lab 6-18

Exercise C-1: Verifying AdvancedDisk storage server
configuration using the Administration Console
2. Navigate to Media and Device Management and then select Credentials and then
Storage Servers, in the left pane of the Administration Console.
Media and Device Management > Credentials > Storage Servers
With the entry for Storage Servers selected in the left pane of the Administration
Console, the list of configured storage servers is displayed in the right pane of the
3. Verify that the entry for the storage server you created (winmedia.example.com if
your master server is Windows-based or lnxmedia.example.com if your master
server is Linux-based) exists in the list of configured storage servers.
Two of the storage servers listed were pre-configured for this course (an
AdvancedDisk storage server on your master server, and a PureDisk storage
server on your master server).
If you right-click the entry for the new storage server (or click Actions in the
Administration Console tool bar), the Change option is greyed out.
Continue to Exercise C-2: Verifying AdvancedDisk disk pool configuration and status
using the Administration Console.
Lab 6-19

Exercise C-2: Verifying AdvancedDisk disk pool
configuration and status using the Administration
Console
1. Navigate to Media and Device Management and then Devices and then select Disk
Pools in the left pane of the NetBackup Administration Console.
Media and Device Management > Devices > Disk Pools
With the Disk Pools entry selected in the left pane of the Administration Console,
the right pane displays a list of the disk pools that are configured in the NetBackup
master server environment.
2. Right-click the entry for the media_advdisk_dpool disk pool, and in the resulting
menu, click Change.
The Change Disk Pool window is displayed. This window can be used to view and
modify certain parameters of the selected disk pool.
3. In this case, click Cancel to close the Change Disk Pool window without making
changes to the disk pool settings.

Lab 6-20

4. Navigate to Media and Device Management and then select Device Monitor in the
Media and Device Management > Device Monitor
When Device Monitor is selected in the left pane, the right pane provides two tabs –
Drives and Disk Pools, as illustrated in the figure below.
5. Click the Disk Pool tab, located in the right pane of the Administration Console
The right pane of the Administration Console lists the disk pools that are configured
in the master server environment.
6. Select View and then Refresh (or click the Refresh icon on the tool bar) to update
the contents of the Disk Pool pane of the Administration Console.
7. Take note of the current Status of the media_advdisk_dpool.
8. Right-click the entry for the media_advdisk_dpool, and take note of the choices that
are available in the resulting menu.
You should have the options of changing the disk pool status to either UP or Down.
9. Click the Down Disk Pool menu option.
10. Note the immediate change in the contents of the disk pool Status column, as
Lab 6-21

11. Verify that the Status of the disk pool is “Down”.
12. Right-click the entry for the media_advdisk_dpool disk pool again, and click the Up
Disk Pool option to return the disk pool to operational status.
13. Verify that the Status of the media_advdisk_dpool is “Up”.
The status of a disk pool can also be changed by using the command
nbdevconfig.
The configuration of a disk pool cannot be changed using the Device Monitor
interface of the Administration Console.
Continue to Exercise C-3: Verifying AdvancedDisk storage unit configuration using

Lab 6-22

Exercise C-3: Verifying AdvancedDisk storage unit
configuration using the Administration Console
1. Navigate to NetBackup Management and then Storage and select Storage Units in
the left pane of the NetBackup Administration Console.
With the Storage Units entry selected in the left pane of the Administration Console,
the right pane contains a list of the storage units that are currently configured in the
NetBackup environment.
2. Locate and right-click the entry for the media_advdisk_stu in the right pane of the
3. In the resulting menu, click Change.
The Change Storage Unit window is displayed.

Lab 6-23

4. See the figure below and take note of the storage unit properties and parameters,
giving special attention to the parameters that can be changed.
Only certain storage unit parameters can be modified. For an AdvancedDisk

storage unit, these include the On demand only parameter, the selection of the
Media server or servers associated with the storage unit, the Maximum
concurrent jobs, and the Maximum fragment size used by the storage unit.
5. Click Cancel to close the Change Storage Unit window without making changes to
the storage unit configuration.

console.example.com system. You return to window later in this lab activity.
Continue to Exercise C-4: Using NetBackup command line interfaces to verify storage
servers, disk pools, and storage units.
Lab 6-24

Exercise C-4: Using NetBackup command line interfaces
to verify storage servers, disk pools, and storage units
NetBackup provides commands that can be used to verify the configuration and status
of storage servers, disk pools, and storage units.
Most NetBackup configuration is housed on the master server. When using

NetBackup commands to check configuration and status of configured entities,
the commands are executed from the command line of the master server.
If you do not wish to use the NetBackup command line interface to monitor and manage
AdvancedDisk entities, such as storage servers, disk pools, and mount points, proceed to
Exercise D: Configuring a policy to write backups to AdvancedDisk storage.
1. Access the desktop of your master server system using one of the two methods
listed below. Choose your master server based upon your preferred operating
system for this course.
̶ Continue to the Exercise C-5: Accessing the Windows-based master server

system desktop.
̶ Continue to the Exercise C-6: Accessing the Linux-based master server system
command prompt.
Lab 6-25

Exercise C-5: Accessing the Windows-based master server
system desktop
In this lab exercise you will connect to a remote Windows-based master server lab


winmaster.example.com, locate and double-click the RDP file (winmaster.rdp).

6. Click the Command Prompt shortcut, located on the desktop of the Windows 2012-
based master server, winmaster.example.com.
Continue to Exercise C-7: Using the nbdevquery command.
Lab 6-26

Exercise C-6: Accessing the Linux-based master server
system command prompt
In this lab exercise, you connect to a remote Linux-based master server system using the
Putty shortcut located in the REMOTE SYSTEM ACCESS folder on the console, and then
review the disk storage information.


lnxmaster.example.com User ID: root Password: train
Continue to Exercise C-7: Using the nbdevquery command.
Lab 6-27

Exercise C-7: Using the nbdevquery command
The NetBackup nbdevquery command can be used to view the configuration and status
of NetBackup entities such as storage servers, disk pools, and mount points.
1. In the Command Prompt or terminal window, type the following NetBackup

command, and press Enter:
Command: nbdevquery -help
2. 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 master server and media server systems.

Lab 6-28

Using nbdevquery to view storage server information
3. In the Command Prompt or terminal window, type the NetBackup command show
below and press Enter, to list the configured storage servers:
Command: nbdevquery -liststs
4. Note the output of the command, including the entry for the AdvancedDisk storage
server that was configured on the media server system (winmedia.example.com or
lnxmedia.example.com).
5. Execute the nbdevquery command again, this time adding the –U command option
as shown below.
Command: nbdevquery –liststs -U
6. Scroll through the command output to locate information for the AdvancedDisk
storage server on your media server system - winmedia.example.com or
7. Take note of the types of information that are included in the command output.

Lab 6-29

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.
8. 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 –U
9. Take note of the command results. Scroll through the command output to locate the
information for the media_advdisk_dpool disk pool.
10. 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 –U –dp media_advdisk_dpool
The output of this command provides information about the specified disk
pool.
11. Take note of the current status of the media_advdisk_dpool disk pool.
The current status of the disk pool should be “UP”.

Lab 6-30

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.
12. Use the nbdevconfig command to change the status of the media_advdisk_dpool
from “UP” to “DOWN”, using the command syntax shown below.
Command: nbdevconfig –changestate –stype AdvancedDisk –dp

media_advdisk_dpool –state DOWN
13. Note the output of the nbdevconfig command.
14. Use the nbdevquery command with the –listdp option to view the status of the
media_advdisk_dpool disk pool (as shown in a previous step).
The current status of the disk pool should be “DOWN”.
16. Use the nbdevconfig command to change the status of the media_advdisk_dpool
from “DOWN” to “UP”. Use the command syntax shown below.
Command: nbdevconfig –changestate –stype AdvancedDisk –dp

media_advdisk_dpool –state UP
17. Note the output of the nbdevconfig command.
18. Use the nbdevquery command with the –listdp option to view the status of the
media_advdisk_dpool disk pool (as shown in a previous step).
The current status of the disk pool should be “UP”.
Do not continue until you have returned the media_advdisk_dpool to a status

of “UP”.
Lab 6-31

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.
20. Use the nbdevquery command syntax shown below to list mount points for all disk
volumes associated with AdvancedDisk disk pools.
Command: nbdevquery –listmounts -U
21. Note the results of this command.
22. Use the nbdevquery command syntax shown below to list mount points for the disk
volumes associated with a specific AdvancedDisk disk pool, media_advdisk_dpool,
in this case.
Command: nbdevquery –listmounts –U –dp media_advdisk_dpool
23. Note the results in the output of this command.

Lab 6-32

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.
24. Use the nbdevquery command syntax shown below to list detailed information
about the disk volumes in the specified disk pool.
Command: nbdevquery –listdv –dp media_advdisk_dpool –stype

AdvancedDisk -U
25. Note the logical Disk Media ID that NetBackup assigns for both disk volumes
associated with this disk pool.

Lab 6-33

Using bpstulist to view storage unit details
The bpstulist command can be used to view configuration information for all storage
units or for specified storage units.
26. Execute the bpstulist command using the syntax shown below, to view configuration
information for all NetBackup storage units.
Command: bpstulist -U
27. Note the results of the command.
28. Execute the bpstulist command again, using the syntax shown below, to view
configuration information for a specific NetBackup AdvancedDisk storage unit.
Command: bpstulist –label media_advdisk_stu -U
30. Exit the command prompt and log out of the Windows master server or type Exit to
close and log out of the Linux master server.
Proceed to Exercise D: Configuring a policy to write backups to AdvancedDisk

storage.
Lab 6-34

Exercise D: Configuring a policy to write backups to
AdvancedDisk storage
After configuring AdvancedDisk storage, including the storage server, disk pool, and
storage unit, the final step that is required to use this storage for backup operations is to
configure a policy that directs backup images to be written to the AdvancedDisk storage,
as specified by an AdvancedDisk storage unit.
Continue to Exercise D-1: Creating a policy that uses AdvancedDisk storage.

Lab 6-35

Exercise D-1: Creating a policy that uses AdvancedDisk
storage
In this lab exercise you will create a NetBackup policy that backs data up to an
AdvancedDisk storage unit.
2. Locate and access the open NetBackup Administration Console window.
3. Navigate to NetBackup Management and select Policies in the left pane of the
When the Policies entry is highlighted in the left pane of the Administration Console,
the All Polices pane displays a list of all policies that are currently configured.
4. Select Actions and then New and then select Policy.
Actions > New > Policy
5. In the Add a New Policy dialog box, type the name of the new policy, LAB06-
console-to-media-advdisk, in the Policy name field, and press OK.
The LAB06-console-to-media-advdisk policy is opened for editing in the Change

Policy window.
6. Use the information provided in the table below to enter the information in the
Attributes tab of the policy.
Policy Attribute Parameter value / setting

Policy type: MS-Windows
Policy storage: media_advdisk_stu
All other policy Attributes: Use default settings
7. Select the Schedules tab of the policy.
Lab 6-36

8. Use the information provided in the table below to create as single Full_Backup
schedule for the policy.
Schedule tab Parameter Value / setting

Attributes Name full_frequency
Type of Backup Full Backup
Schedule type Frequency
Frequency setting: 1 weeks (default)
Retention: 2 weeks (default)
All other Attributes: Use default values
Start Window All parameters: Use defaults – no start window –
enables only manual backups
Exclude Dates All parameters: Use defaults – no excluded dates
9. After entering the parameters for the full_frequency schedule, click OK to save the
new schedule.
10. Select the Clients tab of the policy.
11. Use the information provided in the table below to add a single client to the policy.
Client parameter Parameter value / setting

Detect client operating system: selected
Client name: console.example.com
Hardware and operating system: Windows-x64, Windows
You may wish to have NetBackup detect the Hardware and Operating System
of the client.
12. After entering the information for the client, click Add to save the client entry.
13. Click Cancel to close the Add Client window.
14. Select the Backup Selections tab of the policy.
15. Use the information provided in the table below to add a single backup selection to
the policy.
Backup Selection parameter Parameter value / setting

Pathname or directive: E:\data\complex
Lab 6-37

You may wish to use the Browse function to browse for the folder or folders to
include in the Backup Selections.
16. After entering the backup selection information, click OK to save the backup
selection entry, and to exit the Add Backup Selection window.
17. Select each of the policy tabs - Attributes, Schedules, Clients, and Backup Selections
- one-at-a-time, and verify the contents of each.
19. Verify that the LAB06-console-to-media-advdisk policy is included in the list of

policies that is displayed in the All Policies pane of the Administration Console.
Proceed to Exercise E: Performing and monitoring backups to AdvancedDisk storage.

Lab 6-38

Exercise E: Performing and monitoring backups to
AdvancedDisk storage
In this exercise, you perform a manual backup that writes to AdvancedDisk storage, and
monitor the progress and results of the backup job.
Continue to Exercise E-1: Initiating a manual backup.

Lab 6-39

Exercise E-1: Initiating a manual backup
2. Navigate to NetBackup Management and then select Policies in the left pane of the
When the Policies entry is highlighted in the left pane of the Administration Console,
the All Policies pane displays a list of all policies that are currently configured on the
NetBackup master server
1. Right-click the entry for the LAB06-console-to-media-advdisk policy, located in the

All Policies pane.
2. In the resulting menu, click Manual Backup.
3. Click OK in the Manual Backup window, without making any other selections.
Because the LAB06-console-to-media-advdisk policy contains a single schedule

entry in the Schedules tab and a single client entry in the Clients tab, there is
no need to specify the schedule or client that will be involved in the manual
backup job.
When you click OK in the Manual Backup window the window is closed and the
backup job is initiated.
Continue to Exercise E-2: Monitoring the manual backup job.
Lab 6-40

Exercise E-2: Monitoring the manual backup job
2. Locate and view the Activity Monitor entry for the most recent backup job (the job
with the highest-numbered Job ID) until the job is completed.
3. Double-click the entry for the most recent Backup job.
The Job Details window is opened for the selected job.
4. Note the information for the job (as obtained from the tabs of the Job Details
window) shown in the table below.
Job Details field Field contents

Backup type: Immediate
Job Policy: LAB06-console-to-media-advdisk
Job Schedule: full_frequency
Status: “0” – The requested operation was successful
Storage Unit: media_advdisk_stu
Media Server: winmedia.example.com (if using Windows-based master server)
lnxmedia.example.com (if using Linux-based master server)
5. If the job failed, take note of the status code for the job and seek assistance.
According to the Job Details for the job, this job was written to the AdvancedDisk
storage unit that is configured on the media server system.
6. Close the Job Details window.
Proceed to Exercise F: Monitoring and managing AdvancedDisk disk pools.
Lab 6-41

Exercise F: Monitoring and managing AdvancedDisk
disk pools
In Exercise C of this lab activity you used the NetBackup Administration Console and
NetBackup CLIs to view and manage the configuration of NetBackup entities (storage
servers, disk pools, and storage units) related to the AdvancedDisk feature.
In this exercise, you perform additional tasks related to monitoring and managing
AdvancedDisk disk pools.
Continue to Exercise F-1: Running NetBackup disk reports.

Lab 6-42

Exercise F-1: Running NetBackup disk reports
You can run NetBackup reports to check on the status and operation of AdvancedDisk
storage.
1. Navigate to NetBackup Management and then select Disk Reports from the Reports
listed in the left pane of the Administration Console.
NetBackup Management > Reports > Disk Reports
2. Expand the Disk Reports entry in the left pane of the Administration Console.
Several disk reports are listed under the entry for Disk Reports, in the left pane of
3. Note the names of the Disk Reports as listed in the table below.
Disk Report names

Images on Disk
Disk Logs
Disk Storage Unit Status
Disk Pool Status

Lab 6-43

Running the Images on Disk report
4. Click the entry for the Images on Disk report, located in the left pane of the
The right pane of the Administration Console displays the Report Settings that can
be entered in order to generate the desired report output.
5. Enter the report settings indicated in the table below into the fields of the Report
Settings pane.
Parameter Setting / value

Client: <All Clients> (default)
Disk Type: AdvancedDisk
Disk Pool: media_advdisk_dpool
Volume: <All> (default)
6. Click the Run Report button.
The output of the report is displayed in the bottom half of the right pane of the
The Images on Disk report lists all the active backup images for the specified Client
or all clients, and that reside on the selected Disk Type, Disk Pool, and disk Volume.
Careful examination of the output of this report reveals the specific disk
volume to which a given backup image was recorded, along with a substantial
amount of additional information.
Lab 6-44

Running the Disk Pool Status report
7. Click the entry for the Disk Pool Status report, located in the left pane of the
8. Enter the report settings indicated in the table below into the fields of the Report
Settings pane.
Parameter Setting / value

Disk Pool: media_advdisk_dpool (AdvancedDisk)
The output of the Disk Pool Status report shows the current Status of the selected
disk pool (Up or Down), along with other important information such as, Total
Capacity, Used Capacity, and Available Capacity of the disk pool.
Running other Disk Reports

Run the Disk Logs and Disk Storage Unit Status reports as time permits.
Continue to Exercise F-2: Adding a disk volume to an AdvancedDisk disk pool.

Lab 6-45

Exercise F-2: Adding a disk volume to an AdvancedDisk
disk pool
You may add one or more additional disk volumes to an existing AdvancedDisk disk pool
in order to increase the available capacity of the disk pool.
In the steps that follow, you execute the nbdevconfig command to add a volume to the
AdvancedDisk pool.

Lab 6-46

Viewing the current status of the disk pool
Most of the NetBackup configuration is housed in catalogs and files on the
master server. Hence, when using NetBackup commands to check or modify
configuration and status of configured entities, the commands are typically
executed from the command line of the master server.
1. Access the desktop of your Windows-based master server, winmaster.example.com

or a PuTTY (SSH) window that is connected to your Linux-based master server,
2. Access a Command Prompt window on winmaster.example.com or the PuTTY

(root@lnxmaster) window on lnxmaster.example.com.
3. Execute the following nbdevquery command to display the volumes currently in the
media_advdisk_dpool.
Command: nbdevquery -listmounts -U -dp media_advdisk_dpool
4. Note the paths (disk volumes) in the media_advdisk_dpool as shown in the table
below.
Master Server OS Type Paths

Windows-based G:\, H:\
Linux-based /advdisk1,
/advdisk2
Continue to Exercise F-3: Adding a volume to a disk pool using the nbdevconfig
command.
Lab 6-47

Exercise F-3: Adding a volume to a disk pool using the
nbdevconfig command
The nbdevconfig command provides the –adddv option to add a disk volume to a disk
pool.
1. Access a Command Prompt window on winmaster.example.com or the PuTTY

(root@lnxmaster) window on lnxmaster.example.com.
2. Identify the disk volume to be added to the disk pool as shown in the table below.
Master Server OS type Path to add

Windows-based I:\
Linux-based /advdisk3
3. At the command prompt of your master server, type the appropriate nbdevconfig
command shown below, and press Enter, to add the new disk volume to the
media_advdisk_dpool disk pool.
Enter only one of the two commands listed below – the one that matches your
master server OS type.
Windows-based Command: nbdevconfig -adddv -stype

AdvancedDisk -dp media_advdisk_dpool -dv I:\
Linux-based Command: nbdevconfig -adddv -stype AdvancedDisk

-dp media_advdisk_dpool -dv /advdisk3
Be careful with spelling when using the nbdevconfig command; some of the
command options (e.g. adddv and AdvancedDisk) are easily misspelled.
4. Verify the results of the command, as indicated in the command output.
5. Execute the following nbdevquery command to display the volumes currently in the
media_advdisk_dpool:
Command: nbdevquery -listmounts -U -dp media_advdisk_dpool
Lab 6-48

6. Verify the results of the command, as indicated in the command output.
7. Execute the following nbdevquery command to view the status of the

media_advdisk_dpool disk pool.
8. Verify that the disk pool now contains three disk volumes.
9. Close the Command Prompt window or the PuTTY (root@lnxmaster) window on

your master server.
10. Log out of (and close) any RDP sessions that may be open from
console.example.com to your master server or media server systems.

Lab 6-49

Lab 7: Configuring Media Server
Deduplication
In this lab, you perform tasks to configure, monitor, and manage NetBackup Media
Server Deduplication (MSDP) storage, configure policies and perform backup jobs that
write backup images to MSDP storage.
Continue to Exercise A: Configuring NetBackup Media Server Deduplication (MSDP).
Lab 7-1

Exercise A: Configuring NetBackup Media Server
Deduplication (MSDP)
In this exercise, you perform the steps required to configure the NetBackup Media
Server Deduplication (MSDP) feature. MSDP configuration consists of three main tasks:
• Configuring the Media Server Deduplication storage server.

• Configuring the Media Server Deduplication disk pool.
• Configuring the Media Server Deduplication storage unit.
Continue to Exercise A-1: Examining the storage to be used for MSDP.

Lab 7-2

Exercise A-1: Examining the storage to be used for MSDP
In the steps that follow, you access the media server in your lab environment to view
the disk volumes that have been allocated for use for MSDP data and catalog storage.
• If you are performing this lab using a Windows system (winmaster.example.com),

continue to the Exercise A-2: Viewing disk storage on a NetBackup Windows-based
• If you are performing this lab using a Linux system (lnxmaster.example.com),
continue to the Exercise A-3: Viewing disk storage on a NetBackup Linux-based
Lab 7-3

Windows-based media server system
In this lab exercise you will connect to a remote Windows-based media server lab
systems and then review the disk storage information.


5. Log on to your media server using the credentials provided in the table below.

Lab 7-4

6. Locate and double-click the File Explorer shortcut, located on the desktop of
winmedia.example.com. See the figure below.
for NetBackup backup images. The disk volumes MSDPCAT(J:) and MSDPDATA(K:),
that were created for use as MSDP storage.
Disk Volume for MSDP data storage K:\

Disk Volume for MSDP catalog storage J:\
9. Sign out of the Windows media server.
Continue to Exercise A-4: Configuring the storage server for MSDP.
Lab 7-5

based media server system
In this lab exercise you will connect to a remote Linux-based media server system using
the Putty shortcut located in the REMOTE SYSTEM ACCESS folder on the console, and

6. Log on to your Linux media server using the credentials provided in the table below.

Linux-based lnxmedia.example.com root train
lnxmedia.example.com User Name: root Password: train
root@lnxmedia ~]# df -h
Lab 7-6

mount points on the lnxmedia.example.com system. Many of these file
systems were pre-configured on this media server to serve as storage
destinations for NetBackup backup images.
8. Take note of the /dev/sdb10 and /dev/sdb11 file systems, and their
associated mount points, /msdpcat and msdpdata, respectively.
mount point for MSDP data storage /msdpdata

mount point for MSDP catalog storage /msdpcat
9. Type Exit to close the PuTTY window.
Continue to Exercise A-4: Configuring the storage server for MSDP.
Lab 7-7

Exercise A-4: Configuring the storage server for MSDP
In the steps that follow, you launch the NetBackup Configure Disk Storage Servers
Wizard on console.example.com to begin the configuration of the MSDP feature. The
first step is to configure the storage server that is used by the MSDP feature.
2. If necessary, log on to console.example.com using the credentials provided above.

console.example.com. If no Administration Console window is open, see the Note.

NBU 8.0 Admin Console icon, located on the desktop of the
Administration Console login screen using the information in the table below.

that you are connected to your master server. See the figure below.
Lab 7-8

server, use the “Launch a new instance…” button (or File > Change Server) to
connect the Administration Console to your master server, and log in.
6. Click the entry for hostname of the master server (winmaster.example.com or

lnxmaster.example.com), located at the top of the left pane of the Administration
Console – as highlighted in the figure below.
Within a few moments a list of the NetBackup wizards is displayed in the right pane
of the Administration Console, as illustrated in the figure below.
7. Click the entry for the Configure Disk Storage Servers wizard, located in the right
pane of the Administration Console, to launch the wizard.
A Storage Server Configuration Wizard window is opened. The first wizard screen
displayed enables you to select the type of storage server you want to configure.
8. Click the radio button to select the Media Server Deduplication Pool storage server
type, as illustrated in the figure above, and click Next to continue.
The Add Storage Server screen of the wizard is displayed.
Lab 7-9

9. Use the information provided in the table below, to enter the parameter values in
the fields of the Add Storage Server screen.
Choose the settings based upon the operating system of your media server system.
Parameter Settings for Windows-based Settings for Linux-based

lab systems lab systems
Media server winmedia.example.com lnxmedia.example.com
Storage server type: Media Server Deduplication Pool
Storage server name automatically populated
User name msdp msdp
Password train train
Confirm password: train train
10. After entering the information in the Add Storage Server screen, click Next.
The Storage Server Properties screen of the wizard is displayed.
In this lab scenario, you use one directory path of the MSDP data (Storage Path) and
another directory path for the MSDP catalogs.
11. Use the information in the following table to populate the Storage Server Properties
parameters.
Note that the subdirectories on Windows-based media servers do not exist yet, but
will be automatically created by the wizard at a later point in the process.
Parameter Settings on Windows- Settings on Linux-

based lab systems based lab systems
Storage Path: K:\msdpdata (1) /msdpdata (2)

Use alternate path for deduplication
database for performance… (check box) -checked- -checked-
Deduplication Database Path: J:\msdpcat (1) /msdpcat (2)
Use specific network interface: - not checked - - not checked -
(1) You observed these disk volumes in Exercise A-2.
(2) You observed these mount points in Exercise A-3.
12. After entering the information on the Storage Server Properties screen, click Next.
The Deduplication Load Balancing screen of the wizard is displayed.
Lab 7-10

13. Make no changes to the Deduplication Load Balancing screen and click Next to
continue.
The Storage Server Configuration Summary screen is displayed, which displays a

summary of the selections you have made using the wizard.
14. Verify the information displayed in the summary screen and, if the settings are as
expected, click Next to continue.
The Storage Server Configuration Status screen is displayed, as NetBackup proceeds

with the configuration of the storage server.
When the storage server has been successfully created, the “Storage server
“xxxmedia.example.com” is successfully created” message is displayed, and the
Next button becomes available for selection.
15. Allow the check box for the “Create a disk pool using the storage server…” to
remain selected (the default), and click Next to continue.
The creation of the storage server for MSDP has been completed. Because you
elected to “Create a disk pool using the storage server…” in the previous step, the
Storage Server Configuration Wizard continues to the configuration of the disk pool.
Continue to Exercise A-5: Configuring the MSDP disk pool.

Lab 7-11

Exercise A-5: Configuring the MSDP disk pool
The Storage Server Configuration Wizard enables you to move directly from configuring
the MSDP storage server to the configuration of the disk pool that will be used by the
Media Server Deduplication feature.
If you exit the Storage Server Configuration Wizard, you can launch the
Configure Disk Pool wizard to perform the configuration of the MSDP disk pool
In the steps that follow, you continue the use of the NetBackup Storage Server
Configuration Wizard to configure the disk pool that will be used by MSDP on the media
server system.
After completing the storage server configuration, the Storage Server Configuration
Wizard automatically displays the Volume Selection screen.
1. Make no changes on the Volume Selection screen, and click Next to continue.
The Additional Disk Pool Information screen is displayed by the wizard.
2. Use the information provided in the following table to enter the values in fields of
the Additional Disk Pool Information screen.
Parameter Setting /value

Storage server: xxxmedia.example.com (cannot change)
Storage server type: PureDisk (cannot change)
Total available space: xx.xxGB (automatically determined)
Total raw size: xx.xxGB (automatically determined)
Disk Pool name: media_msdp_dpool

Comments: disk pool for MSDP on media server
High water mark: 98 % (default)
Low water mark: 80% (default)
Limit I/O streams: (check box) selected (change this setting)
Streams per volume: 2 (default, when “limit I/O streams” set)
Lab 7-12

3. After entering the values indicated in the table shown above into the Additional
Disk Pool Information screen, click Next to continue.
The Disk Pool Configuration Summary screen is displayed, that displays a summary
of the disk pool configuration settings you have made.
4. Verify the information displayed in the Disk Pool Configuration Summary screen. If
the information is correct, click Next to continue.
The Disk Pool Configuration Status screen is displayed by the wizard.
If the disk pool was created successfully, the message “Disk pool
“media_msdp_dpool” is successfully created” is displayed.
Lab 7-13

5. Allow the check box for the “Create a storage using the disk pool…” to remain
selected (the default), and click Next to continue
Because you elected to “Create a storage unit using the disk pool…”, the Storage
Server Configuration Wizard continues to the configuration of the storage unit.
Continue to Exercise A-6: Configuring the MSDP storage unit.

Lab 7-14

Exercise A-6: Configuring the MSDP storage unit
The Storage Server Configuration Wizard enables you to move directly from configuring
the MSDP disk pool to the configuration of the MSDP storage unit.
If you exit the Storage Server Configuration Wizard, you can use the
NetBackup Administration Console to manually initiate the configuration of
the MSDP storage unit.
The Storage Server Configuration Wizard automatically displays the Storage Unit
Creation screen that enables you to configure the MSDP storage unit.
1. Use the information provided in the table below to enter the values in fields of the
Storage Unit Creation screen.
Parameter Setting /value

Disk pool: media_msdp_dpool (cannot change)
Storage server type: PureDisk (cannot change)
Storage unit name: media_msdp_stu (change this field)
Media Server
Use any available… (radio button) not selected (change to deselect)
Use only the selected media servers: selected (change to select)
(radio button)
Media server name (check box) xxxmedia.example.com (select the
name of your media server)
Maximum concurrent jobs: 1 (default)
Maximum fragment size: 51200 Megabytes (default)
2. After entering the values indicated in the table above into the Storage Unit Creation
screen, click Next to continue
When the storage unit has been successfully created, the Storage Server
Configuration Wizard displays the Finished screen.
3. Click the Finish button to close the wizard window.
Continue to Exercise A-7: Verifying the MSDP configuration.
Lab 7-15

Exercise A-7: Verifying the MSDP configuration
In the previous steps of this lab activity, you used the NetBackup Storage Server
Configuration Wizard to configure the storage server, disk pool, and storage unit that
will be used by the NetBackup Media Server Deduplication (MSDP) feature.
In the steps that follow, you view the MSDP storage server, disk pool, and storage unit
that were created using the NetBackup Administration Console.
2. Select Media and Device Management and then select Credentials, and then
Storage Servers in the left pane of the Administration Console.
Media and Device Management > Credentials > Storage Servers
With the Storage Servers entry highlighted in the left pane of the Administration
Console, the right pane displays the list of storage servers that are configured in the
master server’s backup domain.
3. Locate and right-click the storage server entry that has the Name of your media
server, xxxmedia.example.com (winmedia.example.com or
lnxmedia.example.com), and that has the Server Type, PureDisk. This is the storage
server that you created in previous steps of this exercise.
When you right-click the entry for the storage server, a menu is displayed, as
Lab 7-16

Viewing the MSDP storage server configuration
4. Click the Change entry in the menu, as highlighted in the figure on the previous
page.
The Change Storage Server window is displayed, as illustrated in the figure below.
5. Note the three tabs that are available in the Change Storage Server window; Media
Servers, Properties, and Replication.
6. Briefly view the contents of each of the three tabs (but do not change any storage
server settings).
7. What two storage server Properties can be modified using the Change Storage
Server user interface? See the answers below.
Spalogretention and verboselevel
8. Note that the current value of the Storage Pool Used Space should be less than
200MB.
9. Click Cancel in the Change Storage Server window to close the window without
making changes to the storage server configuration.
Lab 7-17

Viewing the MSDP disk pool configuration
10. Select the entry for Media and Device Management and then select Devices, and
then Disk Pools in the left pane of the Administration Console.
With the Disk Pools entry selected in the left pane of the Administration Console,
the right pane displays the list of the disk pools that are configured in the master
server’s backup domain.
11. Locate and right-click the entry for the media_msdp_dpool disk pool. This is the disk
pool that you created earlier in this exercise.
When you right-click the entry for the disk pool, a menu is displayed.
12. Click the Change entry in the menu.
The Change Disk Pool window is displayed.
13. Take note of the Total raw size and Total available space values for the disk pool.
14. Click Cancel in the Change Disk Pool window to close the window without making
changes to the disk pool configuration.

Lab 7-18

Viewing the MSDP storage unit configuration
15. Select NetBackup Management and then select Storage, Storage Units in the left
pane of the Administration Console window.
With the Storage Units entry selected in the left pane of the Administration Console,
the right pane displays a list of the storage units that are configured in the master
server’s backup domain.
16. Locate and right-click the entry for the media_msdp_stu storage unit. This is the
storage unit that you configured earlier in this exercise.
When you right-click the entry for the storage unit, a menu is displayed.
17. Click the Change entry in the menu.
The Change Storage Unit window is displayed, as illustrated in the figure below.
Lab 7-19

18. View the Change Storage Unit window briefly and take note of the storage unit
parameters that can be modified. (Note that many storage unit parameters cannot
be modified.)
19. Click Cancel to close the Change Storage Unit window without changing the storage
unit settings.
In this exercise, you used the Configure Disk Storage Servers wizard to configure the
MSDP storage server, disk pool, and storage unit for your media server system.
Then, you used the NetBackup Administration Console to review the results of the
configuration by inspecting the storage server, disk pool, and storage unit
configuration settings.
Proceed to Exercise B: Configuring a policy to use MSDP storage.

Lab 7-20

Exercise B: Configuring a policy to use MSDP storage
In this exercise, you use the NetBackup Administration Console to configure a

NetBackup policy to direct backup images to the MSDP storage that has been configured
on your media server system.
Continue to Exercise B-1: Creating the policy.

Lab 7-21

Exercise B-1: Creating the policy
2. Select the NetBackup Management > Policies entry in the left pane of the
With the Policies entry selected in the left pane of the Administration Console, the
All Policies pane displays a list of the policies that are currently configured in the
master server’s backup domain.
3. With the Policies entry selected in the left pane, select Actions > New > Policy.
4. Type the Policy name, LAB07-console-to-media-msdp, in the Add a New Policy

dialog box, and click OK.
The LAB07-console-to-media-msdp policy is opened for editing in the Change Policy

window.
Continue to Exercise B-2: Configuring the policy Attributes.

Lab 7-22

Exercise B-2: Configuring the policy Attributes
1. Configure the policy Attributes to back up the client, console.example.com. Use the
information provided in the table below to set the policy attributes.
Attribute parameter Setting /value

Policy type: MS-Windows
Policy storage: media_msdp_stu (change this field)
All other policy Attributes leave at their default values
Continue to Exercise B-3: Configuring the policy Schedules.

Lab 7-23

Exercise B-3: Configuring the policy Schedules
1. Click the Schedules tab.
2. Click New to open the Add Schedule window.
3. Configure a single schedule, named full_manual, to enable full backups of

clients.
Set the Full Backup schedule Start Window to enable only manually-initiated backup
operations.
Use the information provided in the following table to complete the schedule
configuration.

Name: full_manual
Frequency setting: (use default settings) 1 weeks
All other Attribute parameters: Use all default settings
Schedule Start Window parameter Use all default settings
Schedule Exclude Dates parameter Use all default settings
4. Set the full_manual schedule settings using the values provided in previous
Table and click OK in the Add Schedule window to save the new schedule.
5. Verify that the entry for the full_manual schedule is displayed in the list of
schedules on the Schedules tab of the Change Policy window.
Continue to Exercise B-4: Configuring the policy Clients.
Lab 7-24

Exercise B-4: Configuring the policy Clients
1. Click the Clients tab of the LAB07-console-to-media-msdp policy in the Change

Policy window.
2. Click New, to open the Add Client window.
3. In the Add Client window, add the entry for the client, console.example.com client
to the client list on the Clients tab of the policy.
The console.example.com system is a Windows-x64, Windows client system

(Hardware and operating system).
4. Click OK in the Add Client window to add the entry for the client.
5. Verify that the console.example.com client entry has been added to the client list
on the Clients tab.
Continue to Exercise B-5: Configuring the policy Backup Selections.

Lab 7-25

Exercise B-5: Configuring the policy Backup Selections
1. Click the Backup Selections tab in the Change Policy window.
2. Click New, to open the Add Backup Selection window.
3. Add the entry to back up the E:\data folder on the client to the Backup Selections
List of the policy.
4. Click the OK button in the Add Backup Selection window to add the backup
selection to the policy and to close the Add Backup Selection window.
5. Verify that the E:\data entry has been added to the Backup Selection List in the
Backup Selections tab of the Change Policy window.
Continue to Exercise B-6: Verifying and saving the policy.

Lab 7-26

Exercise B-6: Verifying and saving the policy
1. Click each of the tabs in the Change Policy window, and briefly review the contents
of each tab; Backup Selections, Clients, Schedules, and Attributes.
Verify that the important policy settings are as intended, as summarized in the table
shown below.
LAB07-console-to-media-msdp policy Important settings

Attributes
Policy type MS-Windows
Policy storage: media_msdp_stu
Schedules
Schedule name full_manual
Schedule type: Full Backup
Start window: none (manual backups only)
Clients
Backup Selections
Backup Selections List; E:\data
2. Click the OK button in the Change Policy window to save the policy settings and to
close the Change Policy window.
3. Verify that the entry for the new policy, LAB07-console-to-media-msdp, is visible in
the list of policies that is displayed in the All Policies pane of the Administration
Console.
Proceed to Exercise C: Performing backups to MSDP storage.
Lab 7-27

Exercise C: Performing backups to MSDP storage
In this exercise, you use the LAB07-console-to-media-msdp policy to perform manual

backups of the console.example.com client to MSDP storage on the media server
system, and use the NetBackup Activity Monitor to monitor the progress and results of
the backup jobs.
Continue to Exercise C-1: Performing a manual backup to MSDP storage.

Lab 7-28

Exercise C-1: Performing a manual backup to MSDP
storage
2. Select NetBackup Management and then select Policies in the left pane of the
3. Click the entry for the LAB07-console-to-media-msdp policy in the All Policies pane
5. Click OK in the Manual Backup window without making any additional selections, to
initiate the manual backup of the console.example.com client, using the
full_manual schedule.
Because the LAB07-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.
Continue to Exercise C-2: Monitoring the backup job and viewing the results.
Lab 7-29

Exercise C-2: Monitoring the backup job and viewing the
results
In the steps that follow, you modify the Activity Monitor column layout so that the
columns are displayed in the order specified, so that the Deduplication Rate information
for jobs that write to MSDP storage is more readily visible.
2. Locate the entry for the most recent Backup job that used the LAB07-console-to-
media-msdp policy.
3. Allow the backup job to run to completion, and verify that the job was completed
successfully. If the job failed, take note of the job status and seek assistance.
4. Click the entry for any job in the Jobs (right) pane of the Administration Console.
5. Select View and then select Columns and then Layout. The Column Layout window
is displayed.
View > Columns > Layout
6. Adjust the column layout of the Activity Monitor, so that the columns 1-10 are
displayed, from left-to-right, in the order listed in the table below.
Sequence / order Column

1 Job ID
2 Type
3 Status
4 State
5 Job Policy
6 Job Schedule
7 Client
8 Storage Unit
9 Deduplication Rate
10 Media Server
11 and following In any order preferred
Lab 7-30

The Activity Monitor column layout shown in this table is for example purposes
only. The column layout used in production NetBackup environments is a
matter of preference of the backup administrator.
7. When you have adjusted the column layout as desired, click OK in the Column
Layout window to save your column layout settings and to close the window.
If you have not done so previously in the labs, consider selecting View >
Columns > Size to Data to improve the readability of the column information.
8. Examine the entry for the most recent Backup job that used the LAB07-console-to-
media-msdp policy.
9. Double-click the entry for the backup job (that used the LAB-7-console-to-media-
msdp policy) to view the Job Details.
10. Examine the contents of the Job Overview and Detailed Status tabs of the Job
Details window, and compare your observations with the information provided in
the table below.
What Deduplication Rate was achieved for the backup job?

73.6% deduplication rate. Your answers may vary.
How many kilobytes were backed up (according to the Current Kilobytes
Written field of the Detailed Status tab)?
825174 KB. Your answer may vary.
How long (Attempt Elapsed) did the backup take to complete?
The time required to complete the job may vary (~1-2 minutes).
View the contents of the Status pane in the Detailed Status tab, and locate
the entry that includes: Report=PDDO Stats for xxxmedia.example.com:

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: 825521 KB. Your observations may vary.
KB sent: 217765 KB. Your observations may vary
Take note of the Backup ID for the backup job (Detailed Status pane).
console.example.com_[xxxxxxxxxx]
[client name]_[ctimestamp]. The ctimestamp is a 10-digit integer.
The Backup ID will vary, based upon the start time of the backup job.
11. Click Close to close the Job Details window for the backup job.
Continue to Exercise C-3: Running and monitoring another manual backup.
Lab 7-31

Exercise C-3: Running and monitoring another manual
backup
2. Initiate another full manual backup of the console.example.com client using the
LAB07-console-to-media-msdp policy.
3. After initiating the backup job, select the Activity Monitor entry in the left pane of
4. Allow the backup job to run to completion. Verify that the job was completed
successfully. If the job failed, record the job status and seek assistance.
media-msdp policy in the Jobs pane of the Activity Monitor.
6. View the Job Details and note the information found in the following table.

How many kilobytes were backed up (Current Kilobytes Written)?
825174 KB. Your answer may vary, but should be the same KB size as that
backed up during the first MSDP backup job.
View the Detailed Status tab Status pane, and compare the values of the
7. Close the Job Details window for the backup job.
Continue to Exercise C-4: Running and monitoring a third manual backup.
Lab 7-32

Exercise C-4: Running and monitoring a third manual
backup
1. Initiate another full manual backup of the console.example.com client using the
LAB07-console-to-media-msdp policy.
2. After initiating the backup, use the Activity Monitor to monitor the backup job.
3. Allow the backup job to run to completion, and verify that the job completed
successfully. If the job failed, take note of the job status and seek assistance.
media-msdp policy in the Jobs pane of the Activity Monitor.
5. View the Job Details and note the information provided in the table shown below.

825174 KB. Your answer may vary, but should be the same KB size as that
backed up during the first and second MSDP backup jobs.
View the Detailed Status tab Status pane, and compare the values of the

Lab 7-33

7. Compare your observations of the MSDP feature and the results of the backups that
were performed of the console.example.com client with the information below.
The backup images for these jobs were written to MSDP storage on the media
server, winmedia.example.com or lnxmedia.example.com.
̶ 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.
̶ The first backup of the client to MSDP storage is likely to take somewhat longer
than subsequent backups of the client to MSDP storage.
̶ 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.
̶ 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.
̶ 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.
Your observations may vary.
Proceed to Exercise D: Configuring and using client-side deduplication.
Lab 7-34

Exercise D: Configuring and using client-side
deduplication
In this exercise, you configure the NetBackup client, console.example.com, to perform

deduplication of the client backup data on the client. 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.
Continue to Exercise D-1: Configuring the host properties.

Lab 7-35

Exercise D-1: Configuring the host properties
2. Select NetBackup Management and then Host Properties, and then select Master
Servers in the left pane of the Administration Console.
NetBackup Management > Host Properties > Master Servers
The right pane of the Administration Console displays a list of the NetBackup Master
Servers.
3. In the Master Servers (right) pane, right-click the entry for your master server,
winmaster.example.com or lnxmaster.example.com.
A menu of options is displayed, as illustrated in the figure below.

4. Click the Properties entry in the menu.
5. Click the Client Attributes entry in the list of master server Properties that is
displayed in the left pane of the Master Server Properties window.
The Client Attributes screen is displayed in the right pane of the Master Server
Properties window.
Lab 7-36

6. Take note that the Client Attributes pane contains a Clients pane that may contain
entries for various clients, as illustrated in the figure below.
If an entry for console.example.com is not already present in the Clients pane, click
the Add button, located below the Clients pane in the Client Attributes screen, as
highlighted in the figure above.
If an entry for console.example.com is already present in the Clients pane, skip to

step 10.
7. When Add Client dialog box is displayed, type the client name,
console.example.com in the Enter Client Name field of the Add Client dialog box,
and click the Add button.
8. Click Close to close the Add Clients dialog box.
9. Verify that the entry for console.example.com is present in the Clients pane of the
Client Attributes screen.
Lab 7-37

10. Click to select the entry for console.example.com in the Clients pane of the Client
Attributes screen.
11. With the entry for the console.example.com client highlighted, click the drop-down
arrow for the Deduplication location field, as highlighted in the figure below.
12. Verify the options for the Deduplication location in the drop-down menu are as
1 Always use the media server

2 Prefer to use client-side deduplication
3 Always use client-slide deduplication
13. Click the option to Always use client-side deduplication.
Lab 7-38

14. Verify that you have selected “Always use client-side deduplication” as the
Deduplication location selection for the client, console.example.com.
The Deduplication location selection applies only to the console.example.com

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 the Help button on the Client Attributes screen.
16. Locate and click the Where deduplication should occur link, located near the
bottom (right) of the Help window.
17. Take note of the information regarding the options for the deduplication of client
data that is available in the Help window. Several additional links are provided to
enable you to learn more about NetBackup deduplication.
18. Select File and then Close to close the Help window.
File > Close
19. Click Apply to save the changes to the Client Attribute setting changes for the
console.example.com client.
20. Click OK to close the Master Server Properties window.
The Restart Daemons dialog box is displayed.

21. Click OK to close the Restart Daemons dialog box.
A restart of the NetBackup daemons is not required to implement the change

to the Deduplication location for the console.example.com client.
Continue to Exercise D-2: Testing client-side deduplication backups.
Lab 7-39

Exercise D-2: Testing client-side deduplication backups
In the steps that follow, you perform a manual, full backup of the client,
console.example.com, using the LAB07-console-to-media-msdp policy, to test the
operation of NetBackup client-side deduplication.
1. Select NetBackup Management and then Policies in the left pane of the NetBackup
2. Initiate a manual, full backup of the client, console.example.com, using the LAB07-
console-to-media-msdp policy.
3. After initiating the backup job, use the Activity Monitor to monitor the progress of
the job.
4. Allow the most recent backup of the client, console.example.com, to run to

completion.
5. Verify that the backup job completed successfully. If the job failed, record the job
status and seek assistance.
6. Open the Job Details of the most recent backup job of the client,
console.example.com that used the LAB07-console-to-media-msdp policy.

Lab 7-40

7. Observe the information provided in the Activity Monitor jobs list, and in the Job
Overview and Detailed Status tabs of the Job Details window, and compare your job
results with the information found in the table below.

99.8%, as indicated in the Deduplication Rate column in the Jobs pane of
the Activity Monitor.
825174 KB, as indicated in the Current Kilobytes Written field of the
Detailed Status tab. Your answers may vary.
Approximately one minute. Your answers may vary (~1-2 minutes).
View the Detailed Status tab Status pane, and record values of the
“scanned” KB and “sent” KB in A4 below.
Two sets of scanned/sent information are listed:
1st KB scanned entry: 825519 KB
2nd KB scanned entry: 2 KB. Your answers may vary
1st KB sent entry: 2047 KB
2nd KB sent entry: 0 KB. Your answers may vary
8. Review the Job Details and locate the information that describes where the backup
data deduplication occurred during this backup job.
The best indication that the deduplication of the client’s backup data occurred on
the client system, console.example.com, is found in the Status pane of the Detailed
Status tab.
Look for the status message that includes: “Using OpenStorage client direct to
backup from client console.example.com to xxxmedia.example.com”.
This message indicates that deduplication occurred at the client rather than at the
media server.
Lab 7-41

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.example.com, 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.
Continue to Exercise D-3: Overriding the Deduplication location host property

setting using a NetBackup policy attribute.
Lab 7-42

Exercise D-3: Overriding the Deduplication location host
property setting using a NetBackup policy attribute
In the steps that follow, you configure a policy Attribute that overrides the setting of the
Deduplication location setting for the client that was configured in the Master Server
Host Properties > Client Attributes.
2. Right-click the entry for the LAB07-console-to-media-msdp policy in the All Policies
3. In the resulting menu, click the Copy to New entry.
The Copy a Policy dialog box is displayed.
4. Type the New policy name, LAB07-console-to-media-msdp-override, and click OK in

the Copy a Policy dialog box.
5. The LAB07-console-to-media-msdp-override policy is opened for editing in the

Change Policy window.
6. Modify only one parameter setting in the policy Attributes tab: Click the check box
to select the Disable client-side deduplication policy attribute.
7. Verify that the Disable client-side deduplication policy attribute check-box is

marked.
8. Make no other changes to the policy. Click OK to save the policy and to close the
Change Policy window.
Continue to Exercise D-4: Performing another backup to MSDP storage.
Lab 7-43

Exercise D-4: Performing another backup to MSDP
storage
In the steps that follow, you perform a fifth and final manual, full backup of the
console.example.com client, this time using the policy LAB07-console-to-media-msdp-
override policy, and view the results of that backup operation.
1. Initiate a manual, full backup of the client, console.example.com, using the LAB07-
console-to-media-msdp-override policy.
2. After initiating the backup, access the Activity Monitor to monitor the progress of
the backup job.
4. Verify that the backup job was completed successfully. If the job failed, record the
status code and seek assistance.

Lab 7-44

5. Observe the information provided in the Activity Monitor jobs list, and in the Job
Overview and Detailed Status tabs of the Job Details window, and compare your job
results with the information found in the table below.

99.8%, as indicated in the Deduplication Rate column in the Jobs pane of
the Activity Monitor.
825174 KB, as indicated in the Current Kilobytes Written field of the
Detailed Status tab. Your answers may vary.
Approximately 1-2 minutes. Your answers may vary.
View the Detailed Status tab Status pane, and observe the values of the
“scanned” KB and “sent” KB in A4 below.
KB scanned: 825521 KB. Your answers may vary.
KB sent: 2047 KB. Your answers may vary
Deduplication of the client backup data occurred on the media server

(xxxmedia.example.com) for this backup job. The message containing “Using
OpenStorage client direct to backup form client…” is absent from the Status
pane in the Detailed Status pane of the Job Details. 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.
6. Close the Job Details for the backup job.
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).
Continue to Exercise D-5: Disabling the use of client-side deduplication for backups
of console.example.com.
Lab 7-45

Exercise D-5: Disabling the use of client-side
deduplication for backups of console.example.com
In the steps that follow, you modify the Master Server Host Properties  Client
Attributes for the client, console.example.com, to disable the use of client-side
deduplication. These steps reverse the configuration that you performed earlier in this
exercise (in Exercise D-1).
Enabling the Deduplication location parameter to “Always use client-side

deduplication” for a client may have negative, un-intended 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).
Because, in this course, you direct backups jobs for the console.example.com
client to other types of NetBackup storage, it is necessary to change the
Deduplication Location parameter for the client so that future backup jobs to
AdvancedDisk storage do not fail.
2. Select NetBackup Management and then Host Properties, and then select Master
NetBackup Management > Host Properties > Master Servers
The right pane of the Administration Console displays a list of the NetBackup Master
Servers.
3. In the Master Servers (right) pane, right-click the entry for your master server,
4. Click the Properties entry in the menu.
Lab 7-46

5. Click the Client Attributes entry in the list of master server Properties that is
displayed in the left pane of the Master Server Properties window.
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. Click to select the entry for console.example.com in the Clients pane of the Client
Attributes screen.
8. With the entry for the console.example.com client highlighted, click the drop-down
arrow for the Deduplication location field.
Lab 7-47

9. Verify the options for the Deduplication location in the drop-down menu are as
1 Always use the media server  Select this option

2 Prefer to use client-side deduplication
3 Always use client-slide deduplication
10. From the drop-down menu, click the option to Always use the media server.
11. Verify that you have selected “Always use the media server” as the Deduplication
location selection for the client, console.example.com.
The Deduplication location selection made in this case applies only to the
12. Click Apply to save the changes to the Client Attribute setting changes for the
14. Click OK to close the Restart Daemons dialog box.
A restart of the NetBackup daemons is not required to implement the change

to the Deduplication location for the console.example.com client.
Proceed to Exercise E: Monitoring and managing NetBackup MSDP storage.

Lab 7-48

Exercise E: Monitoring and managing NetBackup
MSDP storage
In this exercise, you use NetBackup provided user interfaces to monitor and manage
NetBackup Media Server Deduplication storage.
Continue to Exercise E-1: Monitoring disk pool capacity and status using the NetBackup
Lab 7-49

Exercise E-1: Monitoring disk pool capacity and status
using the NetBackup Administration Console
In Exercise A of this lab activity, you used the NetBackup Administration Console to
verify the configuration of the MSDP storage server, disk pool, and storage unit that
were configured on the media server system, winmedia.example.com or
In the steps that follow, you use the NetBackup Administration Console to look briefly
at the storage server and disk pool information that is provided in the Administration
Console user interface.
3. Under Media and Device Management, select Devices, and then select Disk Pools in
the left pane of the Administration Console.
The right pane of the Administration Console displays entries for each of the disk
pools that are configured in the master server’s backup domain, as illustrated in the
figure below.
the contents of the Disk Pools pane.
5. Take note of the Used Capacity, Available Space, Raw Size, and Usable Size column
contents, as highlighted in the figure above.
Lab 7-50

The information provided in the Disk Pools user interface is important, as it
enables the backup administrator to monitor NetBackup for situations where
storage space in a disk pool is running low.
Monitoring disk pool capacity using the Disk Pool Status report
6. Select NetBackup Management in the left pane of the Administration Console.
7. Expand the Reports entry, and then click the Disk Reports entry in the left pane.
NetBackup Management > Reports > Disk Reports
With the Disk Reports entry highlighted in the left pane of the Administration
Console, the list of available Disk Reports is displayed in the right pane of the
Administration Console, including:
̶ Images on Disk
̶ Disk Logs
̶ Disk Storage Unit Status
̶ Disk Pool Status
8. Double-click the entry for the Disk Pool Status report in the right pane of the
The right pane of the Administration Console is updated to display the Report
Settings for the selected report (Disk Pool Status).
the contents of the Report Settings pane.
If the drop-down menus in the Report Settings for a given report are
constricted, and do not list choices that are easily readable, select View >
Refresh (or click the Refresh icon on the tool bar) to update the Report
Settings pane contents.
10. Use the drop-down arrow for the Disk pool parameter in the Report Settings pane
to select the entry for the media_msdp_dpool (PureDisk) disk pool.
11. Click the Run Report button to run the report.
Lab 7-51

12. Observe the output of the Disk Pool Status report, as illustrated in the figure below.
Your available space may vary from the sample numbers presented here.
Use the Columns > Size to data function to display the full contents of the
report columns.
13. Allow the NetBackup Administration Console window to remain open on

console.example.com. You return to this window in later steps.
Continue to Exercise E-2: Using NetBackup commands to view MSDP storage server,
disk pool, and storage unit information.
Lab 7-52

Exercise E-2: Using NetBackup commands to view MSDP
storage server, disk pool, and storage unit information
In the steps that follow, you use NetBackup-provided commands to view information on
MSDP-related storage servers, disk pools, and storage units.
1. Access the desktop of your master server system using one of the two methods
listed below. Choose your master server based upon your preferred operating
system for this course.
̶ Continue to the Exercise E-3: Accessing the Windows-based master server

system desktop.
̶ Continue to the Exercise E-4: Accessing the Linux-based master server system
command line.
Lab 7-53

Exercise E-3: Accessing the Windows-based master server
system desktop
In this lab exercise you will connect to a remote Windows-based master server lab



6. Click the Command Prompt shortcut, located on the desktop of the Windows 2012-
based master server, winmaster.example.com.
Continue to Exercise E-5: Using nbdevquery to view MSDP storage servers.
Lab 7-54

Exercise E-4: Accessing the Linux-based master server
system command line
In this lab exercise, you connect to a remote Linux-based master server system using the
Putty shortcut located in the REMOTE SYSTEM ACCESS folder on the console, and then
review the disk storage information.


lnxmaster.example.com User Name: root Password: train
Continue to Exercise E-5: Using nbdevquery to view MSDP storage servers.
Lab 7-55

Exercise E-5: Using nbdevquery to view MSDP storage
servers
1. Type the following command to view the configured MSDP storage servers in a
master server environment and press Enter.
Command: nbdevquery –liststs –stype PureDisk

–storage_server [media_server_hostname]-U
Example 1 (Windows): nbdevquery –liststs –stype PureDisk

-storage_server winmedia.example.com –U
Example 2: (Linux) nbdevquery –liststs –stype PureDisk
-storage_server lnxmedia.example.com –U
The command syntax shown above lists the configured storage server(s) for a
specific storage server system (xxxmedia.example.com). If the
storage_server command option (-storage_server) is omitted, the
command lists all storage servers (of the stype specified) that are configured
on the master server system.
2. View the results of the nbdevquery command and take note of the information
provided, as illustrated in the figure below.
Continue to Exercise E-6: Using nbdevquery to view MSDP disk pool information.
Lab 7-56

Exercise E-6: Using nbdevquery to view MSDP disk pool
information
1. Type the following command to view status and configuration information for the
MSDP disk pools that are configured in the master server environment and press
Enter.
Command: nbdevquery –listdp –stype PureDisk –U
2. View the results of the nbdevquery command and take note of the information
that is provided, as illustrated in the figure below. You will see that two MSDP disk
pools are configured, one MSDP disk pool is configured on the media server (the disk
pool that you configured) and another is configured on the master server (a MSDP
disk pool that was pre-configured for this course).
Continue to Exercise E-7: Using bpstulist to view MSDP storage unit information.
Lab 7-57

Exercise E-7: Using bpstulist to view MSDP storage unit
information
1. Type the following command at the command prompt to view status and
configuration information for the storage units that are configured in the master
server environment and press Enter.
Command: bpstulist –show_available –verbose
2. View the results of the bpstulist command, as illustrated in the figure below.
Take note of the information that is provided. All storage unit types that are
configured in the master server environment are listed in the output of the
command, including the media_msdp_stu that you created.
The figure below shows only the portion of the bpstulist output that
contains the media_msdp_stu information.
3. Type the command shown below, and press Enter, to close the Command Prompt or
terminal window on the master server system.
Command: exit
4. If applicable, close (sign out) in the Remote Desktop (RDP) window from
console.example.com to winmaster.example.com.
You have completed all required tasks for this lab activity
If you wish to complete the optional lab exercise, click the link to continue to
Exercise F: Running Deduplication reports in OpsCenter.
Lab 7-58

Exercise F: (Optional) Running Deduplication
reports in OpsCenter
This exercise is an optional exercise, intended for those that are interested in using
OpsCenter to monitor and manage their NetBackup environments.
• If you are not interested in OpsCenter, you have completed all tasks for this lab.
• If you are interested in OpsCenter, continue to Exercise F-1: Starting the OpsCenter
Server services.
Lab 7-59

Exercise F-1: Starting the OpsCenter Server services
In the steps that follow you start the OpsCenter Server services on
Because OpsCenter is used infrequently in lab activities of this course, the

OpsCenter Server services are stopped by default on console.example.com in
order to optimize system performance.
To perform OpsCenter operations, you must first start the OpsCenter Server
services.
1. Access the desktop of the console.example.com system
2. Locate and double-click the OPSCENTER folder located on the desktop of

3. In the OPSCENTER folder, locate and right-click the opsadmin_start.bat file,

and then click Run as Administrator in the resulting menu, as shown in the figure
below.
Executing the opscenter_start.bat batch file opens a Command Prompt

automatically.
Continue to Exercise F-2: Running deduplication-related reports in OpsCenter.
Lab 7-60

Exercise F-2: Running deduplication-related reports in
OpsCenter
2. Locate and double-click the OpsCenter WEBUI Login shortcut, located in the
OPSCENTER folder, to launch the OpsCenter Web Interface in a Mozilla Firefox Web
browser window.
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.
3. A “This Connections is Untrusted” dialog box may be displayed.
If this happens, click the “I Understand the Risks” link, and continue to the next
step. If this screen is not displayed, skip to step 6.
4. Click the Add Exception button that is added to the “This Connections is Untrusted”
dialog box.
5. When the Add Security Exception window is displayed, click the Confirm Security
Exception button.
6. When the Veritas NetBackup OpsCenter Version 8.0 log on screen is displayed, log
on to OpsCenter using the following credentials:
̶ Username: admin
̶ Password: Tra1n!ng (case sensitive)
̶ 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 OpsCenter WebUI Login again.
Within a few moments the OpsCenter Web user interface is displayed in the
browser window.
Lab 7-61

7. Click the Reports tab.
8. 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.
9. The list of standard Deduplication Reports is displayed, as illustrated in the figure

below.
Continue to Exercise F-3: Deduplication Reports.

Lab 7-62

Exercise F-3: Deduplication Reports
1. Click the entry for the Deduplication Size Savings report to run the report.
2. Note the output of the report that is displayed in the right pane of the OpsCenter
Web interface.
3. Click the entry for the Pre vs. Post Deduplication Size report, to run the report.
Web interface.
5. You may run other standard Deduplication Reports that are provided in OpsCenter
as time permits.
Continue to Exercise F-4: Disk and Tape Device Activity Reports.

Lab 7-63

Exercise F-4: Disk and Tape Device Activity Reports
1. 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.
Web interface.
3. Click the entry for the Storage Unit Usage report (located in the Disk & Tape Device
Activity Reports folder), to run the report.
Web interface.
5. Click the entry for the Disk Usage report (located in the Disk & Tape Device Activity
Reports folder), to run the report.
Web interface.
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.
7. Click the Logout button, located in the upper-right corner of the OpsCenter Web
user interface to log out of the OpsCenter Server.
8. Click File and then Exit to close the Mozilla Firefox browser window.
Continue to Exercise F-5: Stopping the OpsCenter Server services.
Lab 7-64

Exercise F-5: Stopping the OpsCenter Server services
In the steps that follow, you stop the OpsCenter Server services that are running on the
In this training lab environment, we stop the OpsCenter Server services to

conserve the limited system resources on console.example.com, so as to
optimize system performance.
1. Locate and double-click the OPSCENTER folder, located on the desktop of

console.example.com, to open the folder.
2. Locate and right-click the opsadmin_stop.bat file in the OPSCENTER folder.
3. In the resulting menu, click, Run as Administrator, to run the batch file.
Executing the opscenter_stop.bat batch file opens a Command Prompt

automatically.
Lab 7-65

Lab 8: Configuring Tape Storage
In this lab, you perform tasks to configure NetBackup tape devices and removable
media – including volumes and volume pools.
Proceed to Exercise A: Verifying tape devices are visible to the operating system of
media servers.
Lab 8-1

Exercise A: Verifying tape devices are visible to the
operating system of media servers
In the lab activities of this course you are using either:
• A Windows-based master server/media server combination –

winmaster.example.com and winmedia.example.com.
or
• A Linux-based master server/media server combination – lnxmaster.example.com

and lnxmedia.example.com.
The tape drives and the robotic library have already been configured for your master
server system. However, the tape devices have not been configured for use by your
media server.
In this exercise, you will:
• 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.
The procedures and tools used to verify that tape devices are visible to the operating
system of the media server vary, depending upon the OS type.
Continue to Exercise A-1: Verifying tape devices on a Windows-based system, if your

media server is the Windows-based system, winmedia.example.com.
Continue to Exercise A-4: Verifying tape devices on a Linux-based system, if your media
server is the Linux-based system, lnxmedia.example.com.
Lab 8-2

Exercise A-1: Verifying tape devices on Windows-based
systems
If you are performing this lab activity using Linux-based master server and media server
systems, continue to Exercise A-4: Verifying tape devices on Linux-based systems.
Exercises A-1, A-2, and A-3 are related to Windows-based NetBackup servers.
If you are performing this lab activity using Windows-based master server and media
server systems, complete the steps that follow.
In the steps that follow, you access the desktop of your remote Windows-based media
server, winmedia.example.com, from console.example.com) using Remote Desktop
(RDP) to verify that your media server’s Windows-based 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.

5. The RDP Profiles (Windows systems) folder contains RDP profiles for the Windows-
based systems in this lab environment.

Lab 8-3

7. If necessary, log in to the system using the credentials provided above.
Accessing the Windows Device Manager (to determine if the tape devices
are visible to the operating system of the media server)
8. Open the Windows Server Manager application by clicking the Windows icon,
located in the task bar at the bottom of the Windows’ desktop, and then selecting
the Server Manager tile as illustrated below.
9. In the Server Manager window, select Tools, then select Computer Management, as
illustrated below.
Lab 8-4

10. In the Computer Management window, click the entry for the Device Manager,
located in the left pane, under System Tools, as shown below.
11. In the Computer Management window, verify that the top entry of the right pane
contains the hostname of your media server, as illustrated below.
The short hostname of your Windows-based media server is winmedia. The

fully-qualified name (FQDN) is winmedia.example.com.
12. Locate and expand the entries for Medium Changer devices and for Tape drives in
the right pane of the Computer Management window, as shown below.
Lab 8-5

13. Note that an entry for a Medium Changer device (Robotic library control) is visible,
as illustrated below.
14. Note that entries for two Tape drives are visible, as shown in the figure below.
15. View the properties of the Medium Changer device and the Tape drives, by right-
clicking the entry for each device, one-at-a-time, and then selecting Properties.
16. As you view the Properties for each device, take note of the Bus Number, Target ID,
and LUN information for the devices as shown in the following table.
Device Name Bus Target LUN

Medium changer ADIC Scalar 1000 Library 0 0 1
Tape drive #1 IBM ULT3480-TD1 SCSI Sequential Device 0 0 2
Tape drive #2 IBM ULT3480-TD1 SCSI Sequential Device 0 0 3
The Properties windows for the Medium Changer and Tape drives are illustrated in
the following figures.
Lab 8-6

The Properties window for the Medium Changer is illustrated below.
The Properties window for one of the two Tape drives is shown below.
17. View the properties for all tape drives that are visible in the Device Manager.
18. After viewing the properties for each device and recording the requested
information, click OK to close the Properties window.
19. In the Computer Management window, click File and then Exit to close the window.
20. Close the Server Manager window on winmedia.example.com.
Continue to Exercise A-2: Viewing tape devices on Windows-based systems using

NetBackup commands.
Lab 8-7

Exercise A-2: Viewing tape devices on Windows-based
systems using NetBackup commands
In the steps that follow, you use NetBackup-provided commands to view any tape
devices that are currently configured for use by your Windows-based media server
system, and that are discoverable by NetBackup.
1. Double-click the Command Prompt shortcut, located on the desktop of

winmedia.example.com, to open a Command Prompt window.
2. Type the following command at the command prompt, and press Enter.
NetBackup-provided commands reside in sub-directories of the NetBackup

installation directory on systems on which NetBackup is installed. For purposes
of this course, the PATH environment variable has been pre-set to include
these sub-directories so that you can execute the commands without the need
to navigate to the directory that houses the command.
3. The output of the tpconfig command is displayed, as shown here.

The output of the “tpconfig –d” command shows that no devices – tape drives
or robotic devices – are configured on the media server system at this time.
You can verify that NetBackup will discover the tape devices associated with a
Windows-based NetBackup media server (those that are visible to the Windows
Operating System), using the NetBackup-provided scan command.
Lab 8-8

4. Type the following command, and press Enter, to view the information for the
media changer (or media changers) that are detectable by the command.
Command: scan -changer
The output of the command is similar to the figure below.
5. Type the following command, and press Enter, to view the information for the tape
drives that are detectable by the command.
Command: scan -tape

Lab 8-9

6. Note the information for the media changer and tape drives that is visible to the
media server system.
Tape devices attached to winmedia.example.com

Device Device Name Serial Number Port Bus Target LUN
Changer “” XYZZY_A 3 0 0 1
Tape Drive Tape0 XYZZY_A1 3 0 0 2
If the robotic library (changer) and tape drives are visible to the NetBackup-provided
scan command of 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, winmedia.example.com.
7. Close the Command Prompt window on the Windows-based media server system,
8. Sign out of your Windows media server system.
Continue to Exercise A-3: Viewing the tape devices that are configured on the
Windows-based master server.
Lab 8-10

Exercise A-3: Viewing the tape devices that are
configured on the Windows-based master server
For purposes of this course, tape devices (media changer and tape drives) have been
pre-configured for use by your master server system.
In the steps that follow, you access the desktop of your Windows-based master server
and use NetBackup-provided commands to view the tape devices that are configured
for use on that system.

5. The RDP Profiles (Windows systems) folder contains RDP profiles for the Windows-
based systems in this lab environment.

7. Click the hyperlink below to return to the lab steps, and log in to your master server.
8. Log in (if necessary) to winmaster.example.com using the userid and password

combination, EXAMPLE\Administrator, train.
Lab 8-11

9. Double-click the Command Prompt shortcut, located on the desktop of the system,
to launch a Command Prompt window.
10. At the Command Prompt, type the following command, and press Enter, to view the
devices that have been configured for use by NetBackup on your master server
system.
The output of the tpconfig command on the master server is similar to that
illustrated on the next page.
The output of the tpconfig command on the master server indicates that two
tape drives and a robotic control device (media changer) are configured for use
by the master server.

Lab 8-12

media changer (or media changers) that are detectable on the master server.
Command: scan -tape

Lab 8-13

13. Take note of the information requested for the media changer and tape drives
visible to the media server system as noted in Exercise A-2, and shown in the table
below.
Tape devices attached to winmedia.example.com

14. See the table below (for tape devices on winmaster.example.com) and compare the
tape devices that are attached to the media server (winmedia.example.com), noting
the serial numbers of the devices.
Tape devices attached to winmaster.example.com

15. What did you observe after comparing the NetBackup scan command output on
the media server and master server systems?
The serial numbers of all the devices (Changer0, Tape0, and Tape1) 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.
Conclusion: It appears that both the master server and media server systems can
“see” the same tape devices.
Based on the output of commands you executed on the master and media
server systems, 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 they are not yet configured in NetBackup.
From the output of the NetBackup-provided scan command on the master

server and media server systems, you have determined that the media changer
and tape drives that are visible to these systems are the same devices.
Lab 8-14

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.
16. Close the Command Prompt window on winmaster.example.com.
17. Sign out of your Windows master server system.
You have completed all of Exercise A for Windows-based master and media server
systems.
Proceed to Exercise B: Viewing configured tape devices using the NetBackup

Lab 8-15

Exercise A-4: Verifying tape devices on a Linux-based
system
If you are performing this lab activity using Windows-based master and media server
systems, and have not completed Exercises A-1, A-2, and A-3, click the link to go to
Exercise A-1: Verifying tape devices on Windows-based systems. If you have already
completed Exercises A-1, A-2, and A-3, click the link to continue to Exercise B: Viewing
configured tape devices using the NetBackup Administration Console.
Exercises A-4 and A-5 are related to Linux-based NetBackup servers.
If you are performing this lab activity using Linux-based master server and media server
systems, complete the steps that follow to verify that your media server’s 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.

4. Double-click the Putty shortcut that located in the REMOTE SYSTEM ACCESS folder.
5. Locate and double-click the pre-configured entry for the Linux-based media server
system, lnxmedia.example.com.
Within a moment a PuTTY window (root@lnxmedia) is displayed.
6. Log on to the media server system (if necessary) using the credentials provided.
Lab 8-16

7. Verify that you are the root user, by examining the command prompt that is
displayed in the window as illustrated below.
You can also confirm that you are the root user by typing the id command.
Command: id

Lab 8-17

Viewing tape drives that are visible to the Linux operating system
8. Type the following command, and press Enter, to verify that the Linux 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 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.

Lab 8-18

Viewing tape drives that are visible to or configured in NetBackup
You can use the NetBackup-provided tpconfig command to view tape devices that
are configured to NetBackup.
9. Type the command shown below and press Enter, to view the tape devices that are
configured for use by the Linux-based media server system.
NetBackup-provided commands reside in sub-directories of the NetBackup

installation directory on systems on which NetBackup is installed. For purposes
of this course, the PATH environment variable has been pre-set to include
these sub-directories so that you can execute the commands without the need
to navigate to the directory that houses the command.
The output of the tpconfig command is similar to that as shown below.
The command output indicates that no tape devices (tape drives or media
changers) are configured for use by the Linux-based NetBackup media server,
lnxmedia.example.com. This is expected.
Lab 8-19

10. Type the NetBackup-provided command shown below and press Enter, to view
information for the media changer(s) that are detectable by the command.
The output of the scan command is similar to that displayed in the figure below.
Lab 8-20

Command: scan -tape
The output of the scan command is similar to that displayed in the figure below.
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.example.com

Device Device Name Serial Number
Changer /dev/sg3 XYZZY_B
Tape Drive /dev/nst0 XYZZY_B2
Lab 8-21

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.example.com.
12. Close the terminal (or PuTTY) window on the Linux-based media server system,
Continue to Exercise A-5: Tape devices attached to the Linux-based master server.
Lab 8-22

Exercise A-5: Tape devices attached to the Linux-based
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.example.com master server.
In the steps that follow, you access the desktop of your Linux-based master server and
use NetBackup-provided commands to view the tape devices that are configured for use
on that system.
To connect to the Linux-based lab system, lnxmaster.example.com, from

console.example.com using PuTTY, follow the steps below.

4. Double-click the Putty shortcut that is located in the REMOTE SYSTEM ACCESS
folder.

6. Log in (if necessary) to the master server system using credentials provided above.
7. In the PuTTY (root@lnxmaster) window, verify that you are currently the root user
by viewing the command prompt in the window (or by executing the id command).
Lab 8-23

8. Type the following command, and press Enter, to view the tape devices that are
configured for use by the Linux-based master server system.
The PATH environment variable has been pre-set on your master sever to
include the sub-directories that contain commonly-used NetBackup commands,
so that you can execute the commands without the need to navigate to the
directory that houses the command.
The output of the tpconfig command is similar to the output shown below.
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.
media changer(s) that are detectable on the Linux-based master server.
Command: scan -tape
Lab 8-24

11. Take note of the media changer information associated with the master server and
media server systems, as shown in the tables below.
Tape devices attached to lnxmedia.example.com

Tape devices attached to lnxmaster.example.com

Tape Drive 1 /dev/nst0 XYZZY_B2
Tape Drive 2 /dev/nst1 XYZZY_B1
12. 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.
13. Close the terminal or PuTTY window on the Linux-based master server system,
Lab 8-25

When you have completed these steps, proceed to Exercise B: Viewing configured
tape devices (using the NetBackup Administration Console.
Lab 8-26

Exercise B: Viewing configured tape devices (using
the NetBackup Administration Console)
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.
Continue to Exercise B-1: Viewing configured tape drives and robots.

Lab 8-27

Exercise B-1: 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.
2. Log in to console.example.com (if necessary) using the credentials described above.
A NetBackup Administration Console window may already be open from a

previous lab activity. If so, continue to step 5.
3. Launch the NetBackup Administration Console (if necessary) by double-clicking the

NetBackup 8.1 Administration Console shortcut, located on the desktop of the
4. In the Administration Console login window, enter the Host name, User name, and
Password, and click Login, to connect the NetBackup Administration Console to
your master server.
Use the information provided in the next table based upon the host name of your
master server system.
Master server host name User name Password

winmaster.example.com Administrator train
Lab 8-28

5. In the NetBackup Administration Console, verify that the Administration Console is
connected to the master server.
Check the top entry in the left pane of the Administration Console.
The top entry in the left pane should contain the host name of your master server,
winmaster.example.com or lnxmaster.example.com, as illustrated below.
6. If the Administration Console is not currently connected to the master server, close
the console and re-launch it, making sure to connect to the correct master server in
the login screen.
7. Select Media and Device Management and then select Devices, Drives in the left
Media and Device Management > Devices > Drives
The tape drives that are currently configured in NetBackup are displayed in the right
Lab 8-29

8. Take note information for the configured tape drives as shown in the table below.
For Windows-based lab environments

Drive Name Device Host Drive Robot Robot Robot
Type Type # drive #
IBM.ULT3580-TD5.000 winmaster.example.com HCART2 TLD 0 1
IBM.ULT3580-TD5.001 winmaster.example.com HCART2 TLD 0 2
For Linux-based lab environments
Drive Name Device Host Drive Robot Robot Robot
Type Type # drive #
IBM.ULT3580-TD5.000 lnxmaster.example.com HCART2 TLD 0 2
IBM.ULT3580-TD5.001 lnxmaster.example.com HCART2 TLD 0 1
9. Select Media and Device Management and then Devices, Robots in the left pane of
the Administration Console
10. Take note of the information for the configured robot in the table below.
For Windows-based lab environments:

Robot Name Device Host Robot Type Robot Number
TLD(0) winmaster.example.com TLD 0
For Linux-based lab environments:
Robot Name Device Host Robot Type Robot #
TLD(0) lnxmaster.example.com TLD 0
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, winmaster.example.com or
lnxmaster.example.com, in your lab environment.
There are currently no tape devices (robots or tape drives) configured for use by
NetBackup on your media server system, winmedia.example.com or
11. Continue to Exercise B-2: Viewing configured Media Manager storage units.
Lab 8-30

Exercise B-2: 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.
The Storage Units that are currently configured in NetBackup are displayed in the
right pane of the 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.
2. Locate the Storage Unit Type column in the right pane of the Administration
Console.
3. Take note of the information for the storage unit that has a Storage Unit Type of
“Media Manager” in the following table.
For Windows-based lab environments:

Name Media Servers Robot Robot Max. Concurrent
Type Number Drives

master_tape_stu winmaster.example.com TLD 0 2
For Linux-based lab environments:
Name Media Servers Robot Robot Max. Concurrent
Type Number Drives
master_tape_stu lnxmaster.example.com TLD 0 2
4. Double-click the entry for the master_tape_stu storage unit, to open the storage
unit for editing.
The Change Storage Unit window is opened, and displays the current configuration
settings for the master_tape_stu storage unit.
Lab 8-31

5. 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 steps on the preceding page 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.
Proceed to Exercise C: Configuring Tape Devices using the Device Configuration

wizard.
Lab 8-32

Exercise C: Configuring tape devices using the
Device Configuration wizard
As it currently exists, NetBackup is configured to use the tape drives and robot (media
changer) that are associated with the master sever 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.
Continue to Exercise C-1: Configuring tape devices (using the wizard).

Lab 8-33

Exercise C-1: Configuring tape devices (using the wizard)
In this exercise, 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 in your lab environment.

console.example.com and log in to your master server.
3. Verify that the Administration Console is connected to your master server.
4. Click the entry for the master server, located at the top of the left pane of the
The list of NetBackup wizards that are available on a master server is displayed in
the right pane of the Administration Console, as illustrated below.
5. Locate and click the Configure Storage Devices entry, located in the right pane of
A Device Configuration Wizard window is opened.
The Device Configuration Wizard is used specifically for configuring tape

devices and Media Manager storage units for use by NetBackup.
Lab 8-34

6. Click Next in the wizard’s Welcome… screen to continue.
The wizard’s Device Hosts screen is displayed. This screen contains

entries/selections for both media servers in your lab environment,
xxxmaster.example.com and xxxmedia.example.com.
7. 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.
8. Click Next on the Scanning Hosts screen to continue.
The SAN Clients screen is displayed, that enables you to configure the SAN Client
feature. We have no SAN clients in this lab environment.
9. 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.

Lab 8-35

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 below.
10. 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.
Lab 8-36

11. Click the Properties button to view detailed properties as shown in the Figures
below.
An example of the Properties window for a device is shown below.

12. Click Cancel to close the Drive Properties window.
Lab 8-37

13. 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 your NetBackup environment, take note of which media server (Device Host) is
acting as the Robot Control host?
Windows: winmaster.example.com
Linux: lnxmaster.example.com
14. Close any open Properties window.
If the Backup Devices screen shows limitations, those should first be resolved
before continuing with wizard. Seek assistance if necessary.
Lab 8-38

15. 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 your lab environment, NetBackup is able to properly associate the discovered

tape drives with their positions within the robot (tape library).
16. 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.
17. 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.
18. Click Next in the Updating Device Configuration screen to continue.
Continue to Exercise C-2: Configuring storage units (using the wizard).
Lab 8-39

Exercise C-2: 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 figure below 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).
Lab 8-40

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.
1. Click the entry for the Storage Unit listed on the Configure Storage Units screen,
xxxmedia-hcart2-robot-tld-0, and then click the Properties button.
The Change Storage Unit Properties window is displayed.
2. Change the properties for the new storage unit, using the parameter values
provided in the table below.
Parameter Parameter value / setting

Storage unit name: media_tape_stu (change this setting)
Media server: ** Windows: winmedia.example.com
Linux: lnxmedia.example.com
Storage unit type: ** Media Manager
On demand only: ** not selected (default)
Storage Device: TLD(0) – HCART2
Robot type: ** TLD – Tape Library DLT
Density: ** hcart2 – ½ Inch Cartridge 2
Robot number: ** 0
Maximum concurrent write 2
drives:
Maximum multiplexing per 1
drive:
Reduce fragment size to Not selected (default)
(checkbox):
MB (fragment size): 1048576 (not changeable unless Reduce fragment size
checkbox is selected)
** You cannot change this setting for the storage unit
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.
3. After making the changes to the storage unit, click OK to save the changes, and to
close the Change Storage Unit Properties window.
Lab 8-41

4. Verify that the Configure Storage Units screen of the Device Configuration Wizard
contains the entry for the new storage unit, media_tape_stu.
5. Click Next on the Configure Storage Units screen to continue.
The Device Configuration Wizard contains the displays the Finished screen.
6. Click Finish to close the Device Configuration Wizard.
Continue to Exercise C-3: Viewing the new tape devices and storage unit entries.
Lab 8-42

Exercise C-3: 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.
Viewing the newly configured tape drives

The right pane of the Administration Console displays the list of configured tape
drives.
2. Note that the right pane of the Administration Console is split into two panes – the
Drives pane (top pane) and the Paths for selected drives pane (bottom pane).
3. 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 (xxxmaster.example.com) and the other entry is for
the media server (xxxmedia.example.com). 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.
4. 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.
Lab 8-43

Viewing the newly configured robot entry
5. Select Media and Device Management and then select Devices, Robots in the left
The right pane of the 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
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.
Viewing the newly configured storage unit

The storage units that are currently configured in NetBackup are displayed in the
7. Locate the entry for the newly configured storage unit, media_tape_stu.
8. Verify that the media_tape_stu is associated with your media server,

xxxmedia.example.com, as is a Media Manager type (tape-based) storage unit, and
is configured for access to a maximum of two concurrent tape drives.
Lab 8-44

You have completed the device configuration portion of this lab activity.

Proceed to Exercise D: Configuring volume pools.

Lab 8-45

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.
Continue to Exercise D-1: Creating volume pools using the Administration Console.
Lab 8-46

Exercise D-1: Creating volume pools using the
In the steps that follow, you create NetBackup volume pools using the NetBackup
2. Select Media and Device Management and then select Media, Volume Pools in the
Media and Device Management > Media > Volume Pools
NetBackup provides four volume pools by default. The entries for the default pools
are visible in the right pane of the Administration Console.
̶ CatalogBackup
̶ DataStore
̶ NetBackup
̶ None

Lab 8-47

3. Create the volume pools shown in the tables below.
The table below provides parameters for volume pools to be created.
Pool Name Description Max number Scratch Catalog

of partially pool backup pool
full media
scratch_tapes available tapes 0 checked cleared
server_tapes file system backups 0 cleared cleared
duplicate_tapes copies of backups 0 cleared cleared
hidden_tapes unavailable tapes 0 cleared cleared
Refer to the table below for the detailed steps to create a volume pool.
Step # Step description

1 Select Media and Device Management > Media > Volume Pools in the left
2 Select Actions > New > Volume Pool.
The New Volume Pool window is displayed.
3 Enter the parameters for the new volume pool in the fields of the New
Volume Pool window. 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.
4. As you save each volume pool, verify that an entry for the new pool is visible in the
5. 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.
Lab 8-48

As a result of performing the above steps, the Administration Console displays the
list of volume pools, as illustrated in the figure below.
6. 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.
Proceed to Exercise E: Configuring media using the Administration Console.

Lab 8-49

Exercise E: Configuring media using the
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.
Continue to Exercise E-1: Viewing existing tapes in the Administration Console.

Lab 8-50

Exercise E-1: Viewing existing tapes in the Administration
Console
By default, when NetBackup is installed, no tape media is configured. The configuration

of media in NetBackup is a required backup administrator task.
In the steps that follow, you use the NetBackup Administration Console to view existing
tape volumes.
For purposes of this course, a small number of tapes were pre-configured.
1. Select Media and Device Management and then select Media in the left pane of the
The tapes that are currently configured in NetBackup are listed in the right pane of
2. Take note of the information for the tapes that currently are defined in NetBackup
as shown in the table below.
On winmaster.example.com master server

Media Barcode Media Robot Slot Volume Time Assigned
ID type number number pool
E01001 E01001L5 HCART2 0 1 NetBackup ** (?)
On lnxmaster.example.com master server
Media Barcode Media Robot Slot Volume Time

ID type number number pool Assigned
** You may have performed backups to tape media in previous lab activities. It is
likely that one or more tapes may be currently assigned.
Continue to Exercise E-2: Preparing to configure media with Robot Inventory.
Lab 8-51

Exercise E-2: 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 open Administration Console window on console.example.com.
The tapes that are currently configured in NetBackup are displayed in the right pane.

Lab 8-52

3. Select Actions and then select Inventory Robot.
The Robot Inventory window is displayed.
The figure below illustrates the top half of the Robot Inventory window. Keep
in mind, if your master server is lnxmaster.example.com, the EMM Server,
Device host, and Robot entries will be different than those shown in the screen
shot below.
4. Note the following elements listed below in the Robot Inventory window.
̶ Device Host: The name of the NetBackup server that directly controls the robot.
̶ 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
below.
̶ Show contents (of the robot)

̶ Compare contents with volume configuration (in the NetBackup media
database)
̶ Preview volume configuration changes (that will be made to the NetBackup
media database if you proceed with the robot inventory operation)
̶ 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).
̶ Advanced Options
̶ Empty media access port prior to update
Lab 8-53

5. Verify the Show contents radio button is selected, then click the Start button in the
Robot Inventory window.
The figure below provides an example of the results of the Show contents
operation, as displayed in the Results pane of the Robot Inventory window.
If you are doing this lab from lnxmaster the Barcodes are slightly different.
Lab 8-54

6. Note the Results of the Show contents operation list below.
̶ This robot (tape library) has thirty-nine (39) tape slots, numbered 1-39.
̶ Only 13 of the 39 slots are currently occupied by tapes.
̶ The barcode labels on the tapes are eight alpha-numeric characters in length.
̶ The final two characters of the barcodes of all the tapes are identical (L5).
̶ 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 figure below.
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.
Lab 8-55

8. Note the following in the Results pane of the Robot Inventory window.
̶ 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).
̶ 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.
̶ The tapes that reside in slots 4 – 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 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.
Lab 8-56

10. Note the following in the Results pane of the Robot Inventory window:
̶ NetBackup proposes to add new entries to its media database for the ten (10)
tapes, located in slots 4 – 11 and 22 – 23, of the robot.
̶ 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.
̶ The tapes in slot 22 – 23 are cleaning tapes and cannot be used to write backup
images.
̶ 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.
Continue to Exercise E-3: Creating a Media ID Generation Rule.
Lab 8-57

Exercise E-3: 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.
1. Click the Update volume configuration radio button in the Robot Inventory
window, to select that operation.
2. Click the Advanced Options button, located immediately below the Update volume
configuration operation entry, as illustrated.
The figure below highlights the Advanced Options button of a Robot Inventory.

Lab 8-58

When you click the Advanced Options button, the Advanced Robot Inventory
Options window is opened.
The figure below illustrates the Advanced Robot Inventory Options window.
3. 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 below.

Lab 8-59

4. Use the information provided in the tables below 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
The table below provides detailed steps for creating a Media ID Generation Rule.
To create a Media ID Generation Rule, begin at step # 6 of the detailed steps, as you
have previously performed steps 1-5.
Step # Step details

1 Select Media and Device Management > Media in the left pane of the
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.
7 Enter the values for the new media ID generation rule in the fields of the New
Media ID Generation Rule window.
8 Click OK in the New Media ID Generation Rule window, to save the values
for the new rule, and to close the window.
5. 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.
Continue to Exercise E-4: Completing the first robot Inventory operation.
Lab 8-60

Exercise E-4: 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.
1. Click OK to close the Advanced Robot Inventory Options window.
2. Verify that you are returned to the Robot Inventory window, and that the Update
volume configuration radio button is still selected.
3. 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 Update volume configuration operation, as illustrated in the figure below.
Lab 8-61

4. Note the following in the Results pane of the Robot Inventory window:
̶ NetBackup created Media ID entries for the tapes in the robot.

̶ 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., E01003L5 (Windows) or E02003L5 (Linux)).
̶ The Media IDs that were created are associated with the appropriate tape slot
location in the robot (in which the tapes are currently resident.
5. Click Close to close the Robot Inventory window on console.example.com.
6. Verify the following items listed below:
̶ The NetBackup Administration Console is displayed.

̶ The Media and Device Management > Media entry is selected in the left pane of
̶ The right pane of the Administration Console displays the list of Volumes that
are currently configured in NetBackup.
7. Take note that new entries have been added for the Media IDs (based on the
hostname of your master server):
̶ On winmaster.example.com: Media IDs E01004 – E01011, and CLN101 – CLN102

̶ On lnxmaster.example.com: Media IDs E02004 – E02011, and CLN201 – CLN202
8. 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 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’.
Lab 8-62

IMPORTANT: There are two issues with the Robot Inventory operation that must be
resolved:
• 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.
• 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.
Continue to Exercise E-5: Preparing for a second Robot Inventory operation.

Lab 8-63

Exercise E-5: 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.
The right pane of the Administration Console displays the list of Volumes that are
currently configured in NetBackup.
Deleting Media IDs in the NetBackup Administration Console

3. Click the entry for the first/top Media ID, based on the hostname of your master
server:
̶ winmaster.example.com: Click the entry for Media ID CLN101.

̶ lnxmaster.example.com: Click the entry for Media ID CLN201.
4. While pressing the SHIFT key on your keyboard, click the entry for the last/bottom
Media ID, based on the hostname of your master server:
̶ winmaster.example.com: Click the entry for Media ID E01011.

̶ lnxmaster.example.com: Click the entry for Media ID E02011.
Lab 8-64

5. 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 figure below.
6. Right-click and select Delete.
7. When the Delete Volumes dialog box is displayed, verify the list of volumes to be
deleted, and click the OK button.
8. NetBackup may issue a Delete Volume message (as shown in the figure below) that
states one or more volumes cannot be deleted as it is assigned.
In a previous lab exercise, backups were performed from a policy that used a
Media Manger storage unit (tape). Therefore, 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 figure
below.
9. Click the close (X) icon the close the Delete Volumes window.
Lab 8-65

10. Verify the other Volumes were removed from the list of media being displayed in
the right pane of the 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 on the previous page.
Continue to Exercise E-6: Creating new barcode rules.

Lab 8-66

Exercise E-6: Creating new barcode rules
In the steps that follow you create two new barcode rules, for the purposes described
below:
• 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).
2. Select Actions and then select Inventory Robot.
3. Verify that the robot, TLD(0) – xxxmaster.example.com is selected in the Robot field
of the Robot Inventory window.
4. Click to select the Update volume configuration radio button on the Robot
Inventory window.
5. Click the Advanced Options button, located directly below the Update volume
configuration operation on the Robot Inventory window.
6. Verify that the Advanced Robot Inventory Options window is opened.
7. Click the Barcode Rules tab in the Advanced Robot Inventory Options window.
Lab 8-67

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.
8. Use the information provided in the table below 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 table below provides the detailed steps for creating a Barcode Rule.
To create a new barcode rule, begin at step # 6 in the table.
Step # Step details

1 Select Media and Device Management > Media in the left pane of the
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 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.
9. After saving the barcode rule, verify that the rule is visible in the Barcode Rules tab.
Lab 8-68

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).
10. Use the information provided in the table below 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
Description: from scratch pool
11. Click OK to save the new barcode rule, and to close the New Barcode Rule window.
12. Verify that the second barcode rule is visible in the list of barcode rules that are
displayed in the Advanced Robot Inventory Options window.
13. Click OK to close the Advanced Robot Inventory Options window.
Continue to Exercise E-7: Completing the Robot Inventory operation.

Lab 8-69

Exercise E-7: 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.
1. Verify that that the Update volume configuration radio button is still selected.
2. 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 Update volume configuration operation, as illustrated below.
Lab 8-70

3. Note the information listed below in the Results pane of the Robot Inventory
window.
̶ NetBackup created Media ID entries for the tapes in the robot.

̶ 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., E010004L5 (Windows) or E02004L5 (Linux)).
̶ The Media IDs that were created are associated with the appropriate tape slot
location in the robot (in which the tapes are currently resident).
The Media IDs generated by the Robot Inventory operation differ between the
Windows-based master server and the Linux-based master server.
4. Click Close to close the Robot Inventory window on console.example.com.
5. Verify the following:
̶ The NetBackup Administration Console is displayed.

̶ The Media and Device Management > Media entry is selected in the left pane of
̶ The right pane of the Administration Console displays the list of Volumes that
are currently configured in NetBackup.
Continue to Exercise E-8: Verifying the successful creation of Media ID entries.

Lab 8-71

Exercise E-8: 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 that the effective use of the Media ID generation and barcode rules that you
created.
2. In the right pane of the Administration Console window, note that new Media ID
entries have been added by the Robot Inventory operation:
̶ On winmaster.example.com: Media IDs E01004 – E01011, and CLN101, CLN102

̶ On lnxmaster.example.com: Media IDs E02004 – E02011, and CLN201, CLN202
3. Take note of the information listed below.
̶ The first six digits of the barcode labels were used to create the NetBackup
Media IDs for the newly created volumes.
̶ The Media Type for volumes in slots 4-11 are HCART2 (1/2-inch cartridge tape 2)
̶ The Media Type for the CLN101 or CLN 201 volumes, located in slot 22 is
HC2_CLN (1/2-inch cleaning tape 2)
̶ The newly created HCART2 volumes belong to the scratch_tapes (the SCRATCH
pool for this NetBackup environment)
̶ The cleaning tapes (CLN101, CLN102 on Windows, or CLN201, CLN202 on Linux)
belong to the None pool (cleaning tapes are always members of the None pool.)
Lab 8-72

You have completed all exercises for this lab activity.

Lab 8-73

Lab 9: Managing and Optimizing Tape Storage
In this lab, use NetBackup-provided interfaces and tools to view, manage, and monitor
tape devices and media.
This lab activity assumes that you have previously completed Lab 8:
Configuring Tape Storage. If you have not completed Lab 8, some of the results
you observe in this lab will differ from those documented in the steps of this
lab.
Proceed to Exercise A: Viewing tape drive and robot configuration settings.
Lab 9-1

Exercise A: 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.
Continue to Exercise A-1: Accessing tape device information using the NetBackup
Lab 9-2

Exercise A-1: Accessing tape device information using the
NetBackup Administration Console
In this exercise, you use the NetBackup Administration Console to access the tape drive
information on your master server.
2. If you are not already logged on to the console.example.com system, log on using
the credentials provided above.
• If a NetBackup Administration Console window is already open, proceed to step 5.

• Launch the NetBackup Administration Console by double-clicking the NetBackup
8.1 Administration Console shortcut on the desktop.
4. In the NetBackup Administration Console login window, enter the information to

connect to your master server, as identified in the table below.

5. Verify that the NetBackup Administration Console is connected to your master

server by checking the top entry that is displayed in the left pane of the
The host name listed there should be the name of your master server. If the host
name of your master server is not listed in the top entry of the left pane, use the
Change Server button to connect to your master server.
Lab 9-3

The tape drives that are configured in NetBackup are displayed in the top half of the
right pane (Drives pane) of the Administration Console.
7. Refresh the screen by performing one of the two actions:
̶ Click View > Refresh.

̶ Click the Refresh button (icon) on the Administration tool bar.
8. Note that the right pane of the Administration Console is divided into two panes:
̶ The top pane (Drives pane) displays entries for each physical tape drive that is
configured.
̶ The bottom pane (Paths pane) displays drive path entries for the tape drive
whose entry is selected in the top pane.
9. Expand the Drive Name column in both the top pane (Drives) and bottom pane
(Paths) so that you can see the entire drive name in each pane.
10. In the top half of the screen (Drives pane), click the top (first) tape drive entry.
11. Notice that (with the top tape drive entry selected) the bottom half of the screen
displays the drive path entries for that tape drive.
12. In the Drives pane, click the bottom (second) tape drive entry.
13. Notice that (with the bottom tape drive entry selected) the bottom half of the
screen displays the drive path entries for that tape drive.
Lab 9-4

14. Take note of the information below.
There are two drive paths for each tape drive.
The Device Host for the first (top) drive path listed in the lower pane should be the
Windows-based master server: winmaster.example.com, for a Windows
environment, and the Linux-based master server: lnxmaster.example.com, for a
UNIX environment.
The Device Host for the second (bottom) drive path listed in the lower pane should
be the Windows-based media server: winmedia.example.com, for a Windows
environment, and the Linux-based media server: lnxmedia.example.com, for a
UNIX environment.
Each tape drive is shared for use between the master server (which is also a
media server) and the media server. Each NetBackup server that has access to
a tape drive uses a configured drive path to access the tape drive. In this case
there are two drive paths for each configured tape drive.
Continue to Exercise A-2: Examining tape drive parameters.

Lab 9-5

Exercise A-2: Examining tape drive parameters
In this exercise, you will use the NetBackup Administration Console to view the drive
parameters configured on your system.
1. Right-click the entry for either tape drive in the Drives pane of the Administration
Console.
2. Note the entries that are available in the resulting menu.
3. Click Change in the menu.

The Change Drive window is displayed.
4. Which of the tape drive parameters displayed in the Change Tape Drive window
cannot be changed? See the information listed below 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.
Continue to Exercise A-3: Examining drive path parameters.
Lab 9-6

Exercise A-3: Examining drive path parameters
In this exercise, you will use the NetBackup Administration Console to examine the drive
path parameters configured on your system.
1. In the Host and path information section of the Change Drive window, select the
entry for the master server system and click the Change button.
The top half of the Change Drive window is shown here.
The Change Path window is displayed.
Note that both the Enable host path and Override SCSI reserve path parameters can
be changed.
2. Click Cancel in the Change Path window to close the window without making any
changes to the drive path settings.
3. Click Cancel in the Change Tape Drive window to close the window without making
any changes to the tape drive settings.
Continue to Exercise A-4: Examining Robot parameters.
Lab 9-7

Exercise A-4: Examining Robot parameters
In the steps that follow, you examine NetBackup robotic tape library information.

2. Select the Media and Device Management and then select Devices, Robots entry in
The right pane of the 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.
3. Locate the robot entry in which the Device Host column displays the name of your
media server (winmedia.example.com or lnxmedia.example.com).
4. 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.
Lab 9-8

5. Right-click the robot entry for the master server Device Host in the right pane of the
Administration Console, and click Change.
The Change Robot window is displayed.

6. Verify that the Robot is controlled locally by this device host radio button is already
marked.
Lab 9-9

7. Briefly view the other parameter settings that are available in the Change Robot
window.
8. Click Cancel to close the Change Robot window for this device host without making
any changes to the robot settings.
9. Right-click the robot entry for the media server Device Host in the right pane of the
Administration Console and, in the resulting menu, click Change.
The Change Robot window for this device host is displayed.
10. 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.
11. 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.
Continue to Exercise B: Using the Device Monitor to monitor and manage tape
drives.
Lab 9-10

Exercise B: 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.
Continue to Exercise B-1: Investigating the relationship between the Device Monitor and
the Media and Device Manager.
Lab 9-11

Exercise B-1: 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.
2. Select the Media and Device Management and then select the Device Monitor
entry in the left pane of the Administration Console.
The Device Monitor user interface is displayed in the right pane of the
3. Verify that the Drives tab is selected at the bottom of the Device Monitor user
interface (right pane of Administration Console).
4. 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.
Lab 9-12

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 on the previous page.
5. Take note of the Device Monitor contents, specifically the items that are identified
below.
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?
6. Select Media and Device Management and then select Devices, Media Servers in
Media and Device Management > Devices > Media Servers
7. Refresh the information in the right pane of the 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.
8. Use the information from the right pane (Hosts pane) of the Administration Console
to confirm the host names and Status of each of your media server systems as
shown in the table below.
OS of your master server Media Server Name Current Status

Windows-based winmaster.example.com Active for Tape and Disk
winmedia.example.com Active for Tape and Disk
Linux-based lnxmaster.example.com Active for Tape and Disk
lnxmedia.example.com Active for Tape and Disk
Your master server is also configured to act as a media server.
Continue to Exercise B-2: Stopping the Media Manager Device Daemon on the
media server.
Lab 9-13

Exercise B-2: 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.
1. Select Media and Device Management and then select Devices and then Media
The right pane of the Administration Console displays the Hosts pane, which
contains entries for each of your configured media servers.
2. Perform the steps to stop the Media and Device Manager Daemon on your media
server system, using the detailed steps below.
Step # Detailed Steps

1 Right-click the entry for your media server (winmedia.example.com or
lnxmedia.example.com) in the Hosts pane of the 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.
3 Verify that the Device host field of the Stop/Restart Media Manager Device
Daemon window 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).
6 Leave all other Options in the Stop/Restart Media Manager Device Daemon
window at their default selections.
7 Click the OK button in the Stop/Restart Media Manager Device Daemon
window, to stop the NetBackup Media Manager Device Daemon on your
Lab 9-14

The Stop/Restart Media Manager Device Daemon dialog is illustrated below.
3. Click the Refresh button on the tool bar to update the contents of the right pane of
You can also select View > Refresh.

4. Take note of the host names and current Status of each of your media server
systems as shown in the table below.

winmedia.example.com Active for Disk
lnxmedia.example.com Active for Disk
The updated Status of your media server should be Active for Disk.
5. Select the Media and Device Management and then select Device Monitor entry in
Lab 9-15

6. Click the Refresh button on the Administration Console tool bar to update the
Device Monitor user interface contents.
You can also select View > Refresh.
7. Click the top tape drive entry in the Drives (top) pane of the Device Monitor and
note the information shown below.
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, winmaster.example.com
(Windows) or lnxmaster.example.com (Linux).
The second drive path is missing because the Media Manager Device Daemon is
stopped (not running) on the media server system.
8. Click the bottom tape drive entry in the Drives (top) pane of the Device Monitor and
note the information shown below.
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, winmaster.example.com
(Windows) or lnxmaster.example.com (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.
9. Select Media and Device Management and then select the Devices, Drives entry in
The right pane of the Administration Console is split into two panes – the Drives
(top) pane, and the Paths (bottom) pane.
10. 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.
Lab 9-16

11. 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.
Continue to Exercise B-3: Restarting the Media Manager Device Daemon on your
media server.
Lab 9-17

Exercise B-3: 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.
1. Select Media and Device Management and then select Devices, Media Servers in
The right pane of the Administration Console displays the Hosts pane.
2. Perform the steps below to start the Media and Device Manager Daemon on your
media server system (winmedia.example.com or lnxmedia.example.com).

1 Right-click the entry for your media server (winmedia.example.com or
lnxmedia.example.com) in the Hosts pane of the 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.
3 Verify that the Device host field of the Stop/Restart Media Manager Device
Daemon window contains the host name of your media server system.
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).
6 Leave all other Options in the Stop/Restart Media Manager Device Daemon
window at their default selections.
7 Click the OK button in the Stop/Restart Media Manager Device Daemon
window, to start the NetBackup Media Manager Device Daemon on your
3. Click the Refresh button on the tool bar to update the contents of the right pane of
Lab 9-18

4. Take note of the information in the table below showing the host names and current
Status of each of your media server systems.

winmedia.example.com Active for Tape and Disk
lnxmedia.example.com Active for Tape and Disk
Continue to Exercise B-4: Configuring a policy to write backup to tape storage on the
media server.
Lab 9-19

Exercise B-4: 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.
2. Copy the PRE-clients-to-master-tape policy to create a new policy that has the
name, LAB09-clients-to-media-tape.
The detailed steps to copy a policy to create a new policy are shown in the table
below.

1 Right-click the entry for source policy, PRE-clients-to-master-tape, in the All
2 In the resulting menu, click the Copy to New entry.
The Copy a Policy window is displayed.
3 In the Copy a Policy window, type the name of the new policy, LAB09-clients-
to-media-tape, in the New policy field.
4 Verify the policy name, and click OK in the Copy a Policy window.
5 The new policy is opened for editing in the Change Policy window.
3. In the policy Attributes tab of the LAB09-clients-to-media-tape policy, modify the

Policy storage parameter to select the media_tape_stu storage unit.
It may be necessary to scroll (up or down) through the list of configured Policy
storage destinations to locate the entry for the media_tape_stu storage unit.
Lab 9-20

4. Modify the full schedule of the LAB09-clients-to-media-tape policy, to remove the
start window from the schedule – so that backups using the schedule can only be
initiated manually.
a. Click the Schedules tab of the LAB09-clients-to-media-tape policy.

b. Double-click the entry for the full schedule, to open the schedule.
c. Click the Start Window tab of the full schedule.
d. Click the Clear button, to clear the contents of the Start Window.
e. Click OK to save the changes to the full schedule.
After changing the full schedule to remove the start window entries, this
schedule can only be used to perform manual backups. No automated backups
will occur using the LAB09-clients-to-media-tape policy.
5. Allow all other policy configuration settings to remain at their current settings.
6. Click OK to save the change to the LAB09-clients-to-media-tape policy, and to close

the Change Policy window.
Continue to Exercise B-5: Using the Device Monitor to change the status of tape
drives.
Lab 9-21

Exercise B-5: 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.
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.
2. Select View and then Refresh, or click the Refresh icon on the tool bar, to refresh
the contents of the Device Monitor.
3. 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.
4. In the Paths (bottom) pane, locate and right-click the path entry that is associated
with the Device Host for your media server.
5. In the resulting menu, click Down Path.

6. 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.
Lab 9-22

The figure below 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.
7. In the Paths (bottom) pane, locate and right-click the path entry that is associated
with the Device Host for your media server.
8. In the resulting menu, click Down Path, as shown above.
9. Click the Refresh button on the 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.
Lab 9-23

10. Use the information provided in the table below 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 xxxmaster.example.com SCAN-TLD
IBM-ULT3580-TD5.000 xxxmedia.example.com DOWN-TLD
With Drive IBM-ULT3580-TD1.001 selected in the top pane
Drive Name Device Host Control
IBM-ULT3580-TD5.001 xxxmaster.example.com SCAN-TLD
IBM-ULT3580-TD5.001 xxxmedia.example.com DOWN-TLD
The tape drives and drive paths associated with the master server
(winmaster.example.com or lnxmaster.example.com) are currently up and
operational; the drive paths for the media server (winmedia.example.com or
lnxmedia.example.com) are DOWN.
11. Click the entry for the Drive Name, IBM-ULT3580-TD5.001, located in the Drives
pane of the Device Monitor.
12. 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.
13. In the resulting menu, click Down Path.
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.
Lab 9-24

15. View the results in the Drives and Paths panes of the Device Monitor, as shown
below.
The illustration below 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.
16. 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, winmaster.example.com or
lnxmaster.example.com, in the Paths (bottom) pane of the Device Monitor.
17. In the resulting menu, click Up Path.
then select Refresh), to update the contents of the Device Monitor UI.
Lab 9-25

19. Verify that the Control column for the IBM.ULT3580-TD5.001 drive in the Drives
pane of the Device Monitor now contains <Mixed>.
20. Verify that the Control column entry for the drive path for the
xxxmaster.example.com Device Host in the Paths pane contains SCAN-TLD.
Continue to Exercise B-6: Running a manual backup that writes to master server
tape storage.
Lab 9-26

Exercise B-6: 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.
1. Run a full manual backup of the client, xxxmaster.example.com, 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

2 Click the entry for the PRE-clients-to-master-tape. The policy entry is
located in the All Policies pane of the Administration Console.
3 Select Actions > Manual Backup.
4 Click the entry for the client, winmaster.example.com or
lnxmaster.example.com, in the Manual Backup window.
Console.
3. Locate the Backup job entry for the most recent backup job that used the PRE-
clients-to-master-tape policy.
4. 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.
Continue to Exercise B-7: Running a manual backup that writes to media server tape
storage.
Lab 9-27

Exercise B-7: 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.
1. Run a full manual backup of the client, xxxmaster.example.com, using the LAB09-
clients-to-media-tape policy.
If necessary, refer to the detailed steps described in table in the previous exercise
(Exercise B-6), to perform the manual backup. This time, however, use the LAB09-
clients-to-media-tape policy to perform the backup.
2. Access the Activity Monitor to monitor the progress of the backup job.
3. 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”.
Continue to Exercise B-8: Changing the status of a drive path using the Device
Monitor.
Lab 9-28

Exercise B-8: 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.
1. Select Media and Device Management and then select Device Monitor in the left
2. Select the entry for the first (top) drive, IBM-ULT358-TD5.000, in the Drives (top)
pane of the Device Monitor.
3. 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,
xxxmedia.example.com.

5. Select the entry for the second (bottom) drive, IBM-ULT358-TD1.001, in the Drives
(top) pane of the Device Monitor.
6. 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,
xxxmedia.example.com
Lab 9-29

8. Click the Refresh button on the 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.
9. 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, xxxmedia.example.com should contain TLD.
Console.
11. Take note of the current status of the Backup job that used the LAB09-clients-to-
media-tape policy and read the information below.
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 on the next page.
Lab 9-30

• 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.)
• 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.
• 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 LAB09-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.
12. In the Activity Monitor, view the most recent entry for the Backup job that used the
LAB09-clients-to-media-tape policy and verify that the job runs to successful
completion.
̶ If the job runs successfully, continue to Exercise C: Managing Media.

̶ 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.
Proceed to Exercise C: Managing Media.
Lab 9-31

Exercise C: Managing media
In this exercise, you monitor and manage media using NetBackup user interfaces.
Continue to Exercise C-1: Creating and modifying a new policy.

Lab 9-32

Exercise C-1: Creating and modifying a new policy
1. Copy the LAB09-clients-to-media-tape policy to create a new policy named LAB09-

small-clients-to-media-tape using the detailed steps are provided in the table
below.
Step # Step details

2 In the All Policies pane, right-click the entry for the policy that you
want to make a copy of, in this case, LAB09-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
(LAB09-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 opened for editing in the Change Policy window.
2. Edit the LAB09-small-clients-to-media-tape policy, and make (only) the changes

identified in the following table that follows.
Policy name: LAB09-small-clients-to-media-tape

Attributes tab Attribute Settings:
Policy volume pool server_tapes (change to this setting)
Schedules tab: no changes
Clients tab no changes
Backup Selections tab: Backup Selection entries

For Windows clients: E:\data\smallfiles (change entry to this)
For Linux clients: /data/smallfiles (change entry to this)
3. After making the changes to the LAB09-small-clients-to-media-tape policy, click OK

to save the policy and to close the Change Policy window.
Continue to Exercise C-2: Observing media availability impact on backup jobs.
Lab 9-33

Exercise C-2: 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.
2. Use the LAB09-small-clients-to-media-tape policy to perform a manual, full backup

of the client, xxxmaster.example.com (winmaster.example.com or
The detailed steps are described in the table below.
Step # Step details

2 Click the entry for the LAB09-small-clients-to-media-tape policy. The
policy entry is located in the All Policies pane of the Administration
Console.
4 Click the entry for the xxxmaster.example.com client to be backed up,
located in the Manual Backup window.

3. Select the Activity Monitor entry in the left pane of the Administration Console
window.
4. Locate the entry for the most recent Backup job that used the LAB09-small-clients-
to-media-tape policy, and monitor the progress of the job.
5. Verify that the Backup job runs to successful completion. If the job fails, record the
status of the job and seek assistance.
Lab 9-34

6. Select the Media and Device Management and then select Media entry in the left
7. Click the Refresh button (or select View and then Refresh) to update the contents of
8. 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.
Continue to Exercise C-3: Running a backup job when no media is available.

Lab 9-35

Exercise C-3: 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.
1. Move all tapes that are currently in the in the server_tapes volume pool out of the
robot (but do not eject the tapes).
Step # Step details

1 Select NetBackup Management > Media > Volume Pools > server_tapes in
2 Click the Refresh icon in the Administration Console window.
All tapes (Media IDs) that reside in the server_tapes volume pool are listed
in the right pane of the Administration Console.
3 Select the entry (or entries) for all tapes in the server_tapes pool, as listed
in the right pane.
Click 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.
5 • If the Volume is in a robotic library check box is marked, uncheck it.
• 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.
Lab 9-36

4. 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.
5. 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

1 Select NetBackup Management > Media > Volume Pools > scratch_tapes in
All tapes (Media IDs) that reside in the scratch_tapes volume pool are listed
2 Select the entry (or entries) for all tapes in the scratch_tapes pool, as listed
in the right pane. To 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.
3 Select Actions > Move.
The Move Volumes window is displayed.
4 • If the Volume is in a robotic library check box is marked, uncheck it.
• 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.
7. Click the Refresh button to update the contents of the right pane of the
8. 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.
Continue to Exercise C-4: Running a manual backup using the LAB09-small-clients-to-

media-tape policy.
Lab 9-37

Exercise C-4: Running a manual backup using the LAB09-
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.
1. Use the LAB09-small-clients-to-media-tape policy to perform another manual, full

backup of the master server client.
2. After initiating the manual backup of the xxxmaster.example.com client, select the
Activity Monitor entry for the current job, and monitor the progress of the backup
job.
3. Observe the results of the Backup job.
4. Double-click the entry for the job to view the Job Details for the job.
5. Your observations should include the information noted below.
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 cancelled the job while it was “Waiting for retry”, then the failure status
would be 150 (operation cancelled by user).
6. 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.
Lab 9-38

7. 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.
8. 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.
9. When the State of the failed job is displayed as Done, continue to the next step.
Continue to Exercise C-5: Resolving the problem by updating the robot inventory.
Lab 9-39

Exercise C-5: 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.
1. Update the inventory of the tape library by performing a Robot Inventory.
Step # Step details

1 Select NetBackup Management > Media in the left pane of the
2 Right-click the Media entry in the left pane of the Administration
Console, and click Inventory Robot in the resulting menu.
3 Verify that the Device host field is set to the host name of your master
server.
4 Verify that the Robot field is set to the name of your robot (in this
case, TLD(0)-xxxmaster.example.com.
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.
8 View the Results pane of the Robot Inventory window to verify that
the volume configuration was updated.
9 Click Close to close the Robot Inventory window.
4. Verify that all tapes that are members of the server_tapes and scratch_tapes
volume pools have an associated Slot number in the robot.
5. Verify that the Robot Type column for the tapes contains TLD.
Lab 9-40

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.
Continue to Exercise C-6: Re-running the failed backup job.

Lab 9-41

Exercise C-6: 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.
2. Locate and right-click the entry for the Job ID for the most recent failed that used
the LAB09-small-clients-to-media-tape policy.
3. 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.
4. Monitor the new Backup job, and verify that the job runs to successful completion.
5. 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.
Continue to Exercise C-7: Modifying the column layout of the Volumes pane.
Lab 9-42

Exercise C-7: 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.
1. In the left pane of the Administration Console, select Media and Device
Management, and then select Media.
The Volumes (right) pane of the 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.
2. Click the entry for a tape volume in the right pane of the Administration Console.
3. 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.

Lab 9-43

4. Re-arrange the order in which the first ten columns are displayed to match the order
Arrange columns 11 and following in any order you prefer. Detailed steps to arrange
the column order are described below 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 table below 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.
1 In the Column Layout window, click the entry for a Column that you
wish to move to a new position in the column list.

2 Click the Move Up or Move Down button as many times as necessary
to move the column into the desired position in the Column list.
3 Select the next Column entry you wish to move, and use the Move Up
and Move Down buttons to relocate the column heading in the
Column list.
4 Repeat steps 1-3 until you have arranged the columns 1-10 in the
order specified in the preceding 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.
Lab 9-44

5. 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.
6. Select Media and Device Management and then select Media, Volume Pools and
then server_tapes in the left pane of the Administration Console.
8. View the information displayed in the Volumes pane.
Take note of the information as identified in the table below 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?
Continue to Exercise C-8: Running a backup job - #1.
Lab 9-45

Exercise C-8: Running a backup job - #1
1. Initiate a manual full backup of the xxxmaster.example.com client

(winmaster.example.com or lnxmaster.example.com) using the LAB09-small-
3. Monitor the progress of the most recent Backup job that used the LAB09-small-
4. 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 no proceed until the
problem is corrected, and the backup job has run successfully.
Continue to Exercise C-9: Viewing the results in the volume pool - #1.
Lab 9-46

Exercise C-9: Viewing the results in the volume pool - #1
1. Select Media and Device Management and then select Media, Volume Pools, and
select server_tapes in the left pane of the Administration Console.
Media and Device Management > Media > Volume Pools > server_tapes
3. 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 LAB09-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 Administration Console
will reflect a change in the tape’s contents.
Continue to Exercise C-10: Suspending tapes - #1.

Lab 9-47

Exercise C-10: 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.
1. With the server_tapes entry selected in the left pane of the Administration Console,
select the entries for all volumes (tapes) that are listed in the Volumes in Volume
Pool (right) pane.
̶ Click the entry for the first (top) volume listed in the pane
̶ Hold the Ctrl key down on your keyboard, and…
̶ Click the entries for each additional volume listed in the pane.
2. With the entries for all volumes in the server_tapes pool highlighted, select Actions
and then select Suspend, as illustrated below.
The Suspend window is displayed.
3. 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.
Lab 9-48

5. 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.
Continue to Exercise C-11: Running a backup job - #2.

Lab 9-49

Exercise C-11: Running a backup job - #2
1. Initiate another manual full backup of the xxxmaster.example.com client

(winmaster.example.com or lnxmaster.example.com) using the LAB09-small-
3. Monitor the progress of the most recent Backup job that used the LAB09-small-
4. 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 no proceed until
the problem is corrected, and the backup job has run successfully.
Continue to Exercise C-12: Viewing the results in the volume pool - #2.
Lab 9-50

Exercise C-12: Viewing the results in the volume pool - #2
then server_tapes in the left pane of the Administration Console.
2. Click the Refresh button (or select View and then select Refresh) to update the
contents of the right pane of the Administration Console.
3. Compare your observations regarding the changes in the server_tapes volume pool
to those listed below.
̶ As a result of the most recent backup job, another tape (volume) has been added
to the server_tapes volume pool.
̶ 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).
̶ 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.
Continue to Exercise C-13: Suspending tapes - #2.

Lab 9-51

Exercise C-13: Suspending tapes - #2
In the steps that follow, you suspend all Active tapes that are resident in the
server_tapes volume pool.
then server_tapes entry selected in the left pane of the Administration Console.
2. Select the entries for all Active volumes (tapes) that are listed in the Volumes in
Volume Pool (right) pane.
̶ Click the entry for the first (top) Active volume listed in the pane
̶ Hold the Ctrl key on your keyboard, and…
̶ Click the entries for each additional Active volume listed in the pane.
3. With the entries for all Active volumes in the server_tapes pool highlighted, select
Actions and then select Suspend.
The Suspend window is displayed.
4. 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.
6. Verify that all volumes in the server_tapes volume pool have a Media State of
Suspended.
7. 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 table below.
Information for server_tapes Media ID Media Owner (media server

volume pool that owns the volume)
First volume: Varies winmedia.example.com
Second volume: Varies winmedia.example.com
Third volume (if present): Varies winmedia.example.com
Lab 9-52

The Media Owner of the tapes that are members of the server_tapes volume
pool is the media server, xxxmedia.example.com (winmedia.example.com or
lnxmedia.example.com). 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.
Continue to Exercise C-14: Using the NetBackup Administration Console to

unsuspend a volume.
Lab 9-53

Exercise C-14: 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 in the previous exercise (C-13).
1. Select server_tapes from the volume pools in the left pane of the Administration
Console.
3. Click the volume entry for the tape volume listed as the “first volume”.
4. 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.
5. Take note of the Media ID of the first volume displayed in the Unsuspend window,
and then click OK to unsuspend the volume.
7. 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 Administration Console.
Continue to Exercise C-15: Changing the volume pool of a tape.
Lab 9-54

Exercise C-15: Changing the volume pool of a tape
1. Select the Media and Device Management and then select the Media entry in the
3. 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.
4. In the resulting menu, click Change.
5. In the Change Volumes window, click the New Pool radio button.
6. In the drop-down menu for the Volume Pool, click the entry for the server_tapes
volume pool.
7. Click OK to save the change, and to close the Change Volume window.
9. Verify that the Media ID that you selected (in step 3) is now resident in the
server_tapes volume pool.
10. Select server_tapes in the left pane of the Administration Console.

11. Click the Refresh button and update the contents of the right pane of the
12. 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 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.
Lab 9-55

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.
Continue to Exercise C-16: Attempting to move an assigned volume to another pool.

Lab 9-56

Exercise C-16: Attempting to move an assigned volume to
another pool
1. 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).
2. Right-click the entry for the Media ID identified in the previous step and, in the
resulting menu, click Change.
3. In the Change Volumes window, click the New Pool radio button.
4. In the drop-down menu for the Volume Pool, click the entry for the scratch_tapes
volume pool.
5. Click OK to save the change, and to close the Change Volume window.
6. 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 Administration Console. The Change Volumes message says,
“Change pool of [media ID] failed (91). Cannot change media pool of an assigned
media”.
7. Close the Change Volumes message window.
Proceed to Exercise D: Running tape-based reports.

Lab 9-57

Exercise D: Running tape-based reports
In this exercise, you run NetBackup-provided reports that provide information on

NetBackup tape status and use.
Continue to Exercise D-1: Accessing the Tape Reports.

Lab 9-58

Exercise D-1: Accessing the Tape Reports
2. Select NetBackup Management and then select Reports in the left pane of the
The Reports that are listed in the right pane of the Administration Console are:
̶ Status of Backups
̶ Client Backups
̶ Problems
̶ All Log Entries
̶ Images on Media
̶ Media Logs
3. Click to expand the Reports entry in the left pane of the Administration Console.
4. Note that, in addition to the reports named in the previous step, other report
categories are visible under Reports in the left pane of the Administration Console.
5. Click to expand the Tape Reports entry in the left pane of the Administration
Console, and then click the Tape Reports entry.
The list of available Tape Reports is displayed in the right pane, including:
̶ Images on Tape
̶ Tape Logs
̶ Tape Contents
̶ Tape Summary
̶ Tape Written
̶ Tape Lists
Continue to Exercise D-2: Running the Images on Tape report.
Lab 9-59

Exercise D-2: Running the Images on Tape report
In the steps that follow, you use the NetBackup Administration Console to initiate the
Images on Tape report.
1. Click the entry for the Images on Tape report in the left pane of the Administration
Console.
The right pane of the Administration Console displays the Report Settings screen,
and enables you to provide the parameters to use to when running the report.
2. Select the default parameters for the Images on Tape report, as shown below:
̶ Client: <All Clients>

̶ Media ID: <All Media IDs>
The output of the report is displayed on the bottom half of the right pane of
You can do simple sorting of the report output by clicking the heading of a
column to sort the report according to the contents of that column – in
ascending order or descending order.

Lab 9-60

4. To perform a complex sort of the report output, click the entry for any row in the
report output, and then select View and then select Sort.
The Sort window is displayed, as shown below.
5. Set the Sort window parameters using the information provided below.
Field Value
Sort Items by: (drop down) Media Id
Sort Items by: (radio button) Ascending
First - Then by: (drop down) File Number
First - Then by (radio button): Ascending
Second - Then by: (drop down) (none)
Third – Then by: (drop down) (none)
6. After setting the parameters in the Sort window as specified in the table, click OK to
save the Sort settings, and to close the window.
7. Note the impact of the Sort settings on the output of the Images on Tape report.
As the report name implies, the Images on Tape report lists only the backup
images that were written to tape media, and displays the layout of the images
on tape. The Images on Media report lists backup images that were written to
all types of NetBackup storage – disk-based or tape.
Continue to Exercise D-3: Running the Tape Contents report.
Lab 9-61

Exercise D-3: Running the Tape Contents report
Tape Contents report.
1. Click the entry for the Tape Contents report, in the left pane of the Console.
The right pane of the Administration Console displays the Report Settings screen,
and enables you to provide the parameters to use to when running the report
2. Use the values listed below to set the parameters for the report:
̶ Media Owner: xxxmedia.example.com (your media server host name)

̶ Media ID: any Media ID included in the drop-down list
3. Click the Run Report button, to run the report.
The Tape Contents Report window is displayed, and provides information about
how the report is generated.
4. Click OK in the Tape Contents Report window, to run the report.
The output of the report is displayed on the bottom half of the right pane of the
It may take slightly longer to generate the output of the Tape Contents report,
as NetBackup mounts the tape in a tape drive and reads the backup headers
from the tape to generate the report output.
5. Note that the output displays entries for each backup ID (backup image) that resides
on the tape.
6. Change the Media Owner parameter setting for the report to contain the name of
your master server, xxxmaster.example.com, but leave the Media ID the same as it
was previously set.
7. Click the Run Report button to run the report again.
Lab 9-62

8. When the Tape Contents Report window is displayed, click OK to run the report.
When running the Tape Contents report, the Media Owner report setting is
simply used to determine the media server that will mount and read the tape
to generate the report output.
Continue to Exercise D-4: Running the Tape Summary report.

Lab 9-63

Exercise D-4: Running the Tape Summary report
Tape Summary report.
1. Click the entry for the Tape Summary report, located in the left pane of the
The right pane of the Administration Console displays the Report Settings screen.
2. Use the default Report Settings values, and click Run Report to run the report.
3. Take note of the output of the report.
4. Click the Verbose Listing check box in the Report Settings pane.
5. Click the Run Report button, to run the report a second time.
6. Take note of the output of the report.
You have completed all the required labs for this lab activity.
If you wish, you can click the link to go to first optional exercise for this lab activity,
Exercise E: Using the robtest utility.
9 – Required Activities
Lab 9-64

Exercise E: (Optional) Using the robtest utility
In this optional exercise, you use the NetBackup-provided robtest (robot test) utility
to test the operation of a robotic tape library.
Continue to Exercise E-1: Running robtest from a non-Robot Control Host system.
Lab 9-65

Exercise E-1: 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.
In this lab environment, your master server (winmaster.example.com or

lnxmaster.example.com) is acting as the Robot Control Host for the robotic
control of the tape library.
1. Access the desktop of your media server system, winmedia.example.com or

lnxmedia.example.com, based upon your operating system preference for this
course.
2. Log in to the media server system using the userid/password combination provided
above, based upon the operating system of the media server.
3. Open a Command Prompt window on the Windows-based media server,

or
Access the command line on the Linux-based media server, lnxmedia.example.com.

Lab 9-66

4. At the Command Prompt on the media server system, type the command shown
5. Note that the output of the scan –changer command shows that the media
server can “see” the robotic control, as illustrated below.
The scan –changer command output shown above is from a Windows-

based media server. The output of the command on a Linux-based media
server is only slightly different from the example provided.
6. Execute the tpconfig command, as shown below, to verify that the robot is
configured for use by the media server, but that the media server is not the Robot
Control Host.
In the Command Prompt (Windows) or Terminal (Linux) window, type the command
Lab 9-67

7. Note the output of the tpconfig -d command.
The tpconfig -d command output shown above is from a Windows-based

media server. The output of the command on a Linux-based media server is
only slightly different from the example provided
8. In the Command Prompt (Windows) or Terminal (Linux) window, type the command
Command: robtest
9. Note the output of the robtest command as shown below.
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: robtest should be executed on the media server that is configured to

serve as the Robot Control host for the robot.
10. Close the Command Prompt window on your media server system.
Continue to Exercise E-2: Identifying a tape to use during robtest operations.
Lab 9-68

Exercise E-2: 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.
2. Locate and access the open NetBackup Administration Console window on

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 Administration Console.
5. 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 shown below.
Lab 9-69

6. 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 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 Administration Console), and then select View >
Filter. You use the resulting Filter window to create, modify, or delete a filter.
Continue to Exercise E-3: Viewing the status of the tape drives.

Lab 9-70

Exercise E-3: 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.
The Device Monitor is displayed in the right pane of the Administration Console.
3. 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 figure below.
4. Allow the Administration Console window to remain open on console.example.com.
Continue to Exercise E-4: Running robtest on the Robot Control Host.

Lab 9-71

Exercise E-4: 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.
1. Access your master server system, either winmaster.example.com or

lnxmaster.example.com, using the appropriate steps listed below.
Windows-based, winmaster.example.com
a. Locate and double-click the REMOTE SYSTEM ACCESS folder on the desktop of
the console.example.com system, to open the folder.
b. Locate and double-click the RDP file (winmaster.rdp).
Within a few moments a Windows Security dialog box will be displayed,

prompting you to enter the login credentials for the system.
c. Log on to your Windows-based master server using the credentials provided

below.
winmaster.example.com User ID: EXAMPLE\Administrator Password: train
Linux-based, lnxmaster.example.com
b. To connect to the Linux-based lab system, double-click the Putty shortcut
located in the REMOTE SYSTEM ACCESS folder.
c. Locate and double-click the pre-configured entry for the Linux-based master
server, lnxmaster.example.com.
d. Log on to your Linux-based master server using the credentials provided below.
Lab 9-72

2. In the Command Prompt (Windows) or PuTTY (Linux) window, type the command
Command: 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.
3. A simple Robot Selection menu is displayed.
4. 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.

5. Take note of the output of the robtest help (?) command.
Continue to Exercise E-5: Performing robtest operations.
Lab 9-73

Exercise E-5: Performing robtest operations
In the steps that follow, you use robtest commands to verify the operation of the
robot.
1. 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 shown below.

The show slots operation pauses after displaying a small number of tape library
slots. You must press return (Enter) to continue displaying slots.
Lab 9-74

2. 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 on the next page.
The figure below illustrates the “READ_ELEMENT_STATUS complete” message.
3. Read the note below 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 figure below illustrates an example of the “show slot [slot number]” output.
4. 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.
Lab 9-75

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.
6. 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 figure below illustrates an example of the move command (m s2 d1) output.
7. 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).
Lab 9-76

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.
9. Allow the window in which robtest is running to remain open on your master server.
Continue to Exercise E-6: Viewing the Media ID (that was moved in robtest in the
Device Monitor).
Lab 9-77

Exercise E-6: 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).

4. 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 shown below.
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 between Windows and Linux systems.
5. Allow the Administration Console window to remain open on console.example.com.

You return to this window later in this lab activity.
Continue to Exercise E-7: Returning to robtest.
Lab 9-78

Exercise E-7: 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.
1. Access the desktop of your master server system (winmaster.example.com or

2. Access the open Command Prompt or Terminal window on the master server.
robtest should still be running in the Command Prompt or Terminal window.
3. 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(#)
4. 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.
5. Allow the Command Prompt (Windows) or PuTTY (Linux) window to remain open on
your master server. You return to this window in a few moments.
Continue to Exercise E-8: Viewing the Media ID (that was moved in robtest) in the
Device Monitor.
Lab 9-79

Exercise E-8: 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).

4. View the Drives (top) pane of the Device Monitor.
Note 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.
Continue to Exercise E-9: Exiting robtest.

Lab 9-80

Exercise E-9: 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.
Currently, you have an open robtest session running on your master server.

3. Right-click the Media entry in the left pane of the Administration Console and, in the
resulting menu click Inventory Robot.
4. Verify that the Show Contents radio button is selected, and then click the Start
button.
Your observations should be similar to those listed below.
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.
5. Allow the Robot Inventory (that is hung while attempting to perform a Show
Contents operation) to remain open in the Administration Console window.
6. Access your master server system (winmaster.example.com or

Lab 9-81

7. Access the open Command Prompt (Windows) or PuTTY (Linux) window on the
master server.
robtest should still be running in the Command Prompt or Terminal window.
8. Type q, and press Enter (to quit robtest).
The Robot Selection menu is displayed.
9. Type 2 (none/quit), and press Enter (to close robtest).
The robtest utility session is ended, and you are returned to the command
prompt.
10. Type exit, and press Enter to close the Command Prompt or Terminal window.
Continue to Exercise E-10: Verifying the results in the Robot Inventory window.
Lab 9-82

Exercise E-10: 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.example.com. 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.

The Robot Inventory window, that was opened previously, should still be open.
2. 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.
Lab 9-83

3. Click Close in the Robot Inventory window on console.example.com, to close the
window without proceeding further with the inventory operation.
You have completed this optional exercise.
If you wish to continue with the optional exercises, click the link to go to the next
optional exercise of this lab activity, Exercise F: Running NetBackup reports from the
command line.
Lab 9-84

Exercise F: (Optional) 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.
Continue to Exercise F-1: Using the vmquery command.

Lab 9-85

Exercise F-1: 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, either winmaster.example.com or

lnxmaster.example.com, using the appropriate steps listed below.
Windows-based, winmaster.example.com
b. Locate and double-click the RDP file (winmaster.rdp).
Within a few moments a Windows Security dialog box will be displayed,

prompting you to enter the login credentials for the system.
c. Log on to your Windows-based master server using the credentials provided

below.
Linux-based, lnxmaster.example.com
b. To connect to the Linux-based lab system, double-click the Putty shortcut
located in the REMOTE SYSTEM ACCESS folder.
c. Locate and double-click the pre-configured entry for the Linux-based master
d. Log on to your Linux-based master server using the credentials provided below.
Lab 9-86

2. In a Command Prompt (Windows) or PuTTY (Linux) window, type the command
Command: vmquery –a -b
3. Note the results of the command as shown in the example illustration below.
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.
Continue to Exercise F-2: Using the bpmedialist command.

Lab 9-87

Exercise F-2: 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.
1. Use the bpmedialist command to list all the tapes that assigned to the master
server. To do so, type the command shown below, and press Enter.
Command: bpmedialist –h [master server name]
• Example: bpmedialist –h winmaster.example.com

• Example: bpmedialist –h lnxmaster.example.com
Note the results of the command.
2. To list all the tapes that assigned to the media server, type the command shown
Command: bpmedialist –h [media server name]
• Example: bpmedialist –h winmedia.example.com

• Example: bpmedialist –h lnxmedia.example.com
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.
Continue to Exercise F-3: Running the Tape Summary report from the command line.
Lab 9-88

Exercise F-3: Running the Tape Summary report from the
command line
In this exercise, you use the NetBackup bpmedialist command to run a tape
summary report.
1. To run the command line version of the Tape Summary report, type the command
Command: bpmedialist –summary
2. Note the output of the command.
Continue to Exercise F-4: Running the available_media report.

Lab 9-89

Exercise F-4: 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.
1. Type the command shown below, and press Enter.
Command: available_media
2. Close the Command Prompt or Terminal window on your master server.
You have completed this optional lab activity.
If you wish to continue with the optional exercises, click the link to go to the next
exercise, Exercise G: (Optional) Media state management using the command line.
Lab 9-90

Exercise G: (Optional) Media state management
using the command line
In this optional exercise, you perform media state management tasks using NetBackup-
provided command line interfaces (CLIs).
• If you are performing this lab on a Windows system, continue to the Exercise G-1:
Connecting to a NetBackup Windows-based master server system.
• If you are performing this lab on a Linux system, continue to the Exercise G-2:
Connecting to a NetBackup Linux-based master server system.
Lab 9-91

Exercise G-1: Connecting to a NetBackup Windows-based
master server system
In this exercise, you connect to a remote Windows-based master server lab systems,
locate and double-click the RDP Profiles (Windows systems) sub-folder, to enable you
to use commands for managing media.



Continue to Exercise G-3: Using the bpmedialist command.
Lab 9-92

Exercise G-2: Connecting to a NetBackup Linux-based
master server system
In this exercise, you connect to a remote Linux-based master server system using the
Putty shortcut, located in the REMOTE SYSTEM ACCESS folder on the console, to enable
you to use commands for managing media.


Continue to Exercise G-3: Using the bpmedialist command.
Lab 9-93

Exercise G-3: Using the bpmedialist command
In the steps that follow, you execute the bpmedialist command and examine the
command output.
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.
̶ The output of bpmedialist indicates the Tape Owner for each tape.
̶ 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.
̶ The output of bpmedialist indicates the Media State (Active, Full, Frozen,
Suspended) of the media listed.
̶ 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.
̶ The Media ID may vary.

̶ The Media Owner should be xxxmedia.example.com. (the media server).
Continue to Exercise G-4: Using the bpmedia command.
Lab 9-94

Exercise G-4: Using the bpmedia command
In the steps that follow, you execute the bpmedia command and examine the
command output.
The command shown below 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
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 specify the Media Owner host name in the
syntax of the command. This is accomplished using the -h [Media Owner]
command option.
2. Type the command shown below, and press Enter to UNSUSPEND the Media ID you
recorded in Answer A3 on the previous page.
Command: bpmedia –unsuspend –m [media ID} –h

xxxmedia.example.com
Example: bpmedia –unsuspend –m E01002 –h winmedia.example.com
This time the bpmedia command should exit without any response. There is
no indication of the success or failure of the command.
Lab 9-95

3. Verify the results of the bpmedia command to unsuspend the tape, by typing the
command shown below, and pressing Enter.
Command: bpmedialist
4. 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.
5. Repeat the bpmedia -unsuspend command to unsuspend any other suspended

tapes shown in the bpmedialist command output.
Continue to Exercise G-5: Verifying the results of the unsuspend using the
Lab 9-96

Exercise G-5: Verifying the results of the unsuspend using
the 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.

3. Select the Media and Device Management and then select Media entry in the left
the right pane of the Administration Console
5. Verify that the Media ID that was previously in the Suspended Media State is now
shown as Active in the right pane of the Administration Console.
Continue to Exercise G-6: Attempting to suspend unassigned media.

Lab 9-97

Exercise G-6: 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.
1. Select Media and Device Management and then select Media entry highlighted in
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.)
2. In the right pane of the Administration Console, right-click the entry for the
(unassigned) Media ID and, in the resulting menu, click Suspend.
3. 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 Administration Console. The message says, “requested media id is not
assigned to this host in the EMM database (95). Media is not assigned.”
4. Click the small X icon in the upper right corner of the Suspend message dialog to
close it.
You have completed all lab exercises for this lab activity.
Lab 9-98

Lab 10: Protecting Virtual Machines
In this lab activity, you configure NetBackup to access the VMware vCenter server,
install the new NetBackup Plug-in for VMware vSphere Web Client, Configure VMware
policies and perform backups of VMware virtual machines.
Continue to Exercise A: Verifying the VMware environment.
Lab 10-1

Exercise A: Verifying the VMware environment
In this exercise, you access the VMware vSphere Web Client user interface and login to
the VMware vCenter server, to view and become familiar with the VMware
environment used in this course.
The VMware environment includes the vCenter server, the ESX server, and two virtual
machines hosted by the ESX server.
• If you are familiar with the VMware vSphere Web Client and the VMware
environment used in this course, you can skip Exercise A and go directly to Exercise
B: Configuring NetBackup to perform VMware backups.
• To review the VMware environment used in this activity, continue to Exercise A-1:
Verifying the VMware environment.
Lab 10-2

Exercise A-1: Verifying the VMware environment
In this exercise, you access and log into the VMware vSphere Web Client user interface
to view the VMware environment used in this lab activity.
1. Access the desktop of the console.example.com system in your lab environment.
2. Log in to console.example.com, if necessary, using the username and password

combination, EXAMPLE\Administrator, train.
3. Locate and double-click the vSphere Web Client shortcut on the desktop of
console.example.com to launch the VMware vSphere Web Client user interface.
The vSphere Web Client is the VMware-provided interface for operating and
administering a VMware virtual machine environment. You use the vSphere
Web Client to observe the resources and objects that are used in this lab
activity.
It has been intermittently observed that, when attempting to connect the

vSphere Web Client to the VMware vCenter Server (vcenter2, in this case),
that a “Cannot connect to the vCenter Server” message is displayed. The typical
cause of this issue is that the VMware VirtualCenter Server services did not all
start as expected for an un-determined reason, on the vCenter Server system
(vcenter2). If you encounter this situation, access the desktop of the vcenter2
system and locate the START VCENTER SERVICES.bat file. Right-click the START
VCENTER SERVICES.bat file, and click “Run as administrator” in the menu. Wait
until the Command Prompt window closes, and until vcenter2 is up-and-
running, and repeat the attempt to login to the vCenter Server using the
VMware vSphere Web Client.
Even after starting the vCenter Server Services it may take a minute or two
before you can log in using the vSphere Web Client.
Lab 10-3

Within a few moments, the VMware vSphere Web Client log in screen is displayed,
as illustrated below.
4. Type the User name and Password for the vCenter server, vcenter2.example.com,
provided below, and click the Login button.
̶ User name: vsphere.local\Administrator

̶ Password: Tra1n!ng
Be sure to use the above credentials when logging in to the vCenter Server. The
use of other credentials may allow you to log in, but your results will not be the
same as when the correct credentials are used.
Within a few moments, the vSphere Web Client is connected to the vCenter server.
For purposes of this training the vSphere Web Client has been pre-registered
with, and connects to the vCenter server, vcenter2.example.com.
The initial screen may appear blank.

5. Click the Home icon at the top of the vSphere Web Client user interface.
Lab 10-4

6. Click the Hosts and Clusters entry in the Navigator pane of the vSphere Web Client
user interface.
7. Click the symbol to the left of the entries in the tree-view, if needed, to expand the
view.
The left pane of the vSphere Web Client user interface is updated to display an
entry for DC1 (DC = Datacenter).
The vCenter server, vcenter2.example.com, is registered as the IP address,

10.10.2.65.
Lab 10-5

8. Select the entry for esx2.example.com and notice the following tabs are available:
Getting Started, Summary, Monitor, Manage, and Related Objects tabs.
9. Click the Summary tab, if necessary, in the center pane.
Note that the resources and status of the ESX host, esx2.example.com, are
displayed in the center pane.
The Summary tab displays information about the VMware entity that is
selected in the left pane of the vSphere Web Client user interface.
Entries for the virtual machines that are hosted by the esx2.example.com ESX
server are displayed beneath the entry for esx2.example.com in the left pane
of the vSphere Web Client user interface.
In this lab environment, two VMware virtual machines exist, lnxvm2 and
winvm1. The fully-qualified domain names (FQDN) of the VMs are
winvm1.example.com and lnxvm2.example.com.
Lab 10-6

If you get lost when navigating in the vSphere Web Client user interface, click
the Home icon, located at the top of the user interface and then click the Home
option in the menu. Then click Hosts and Clusters in the left pane of the user
interface, to display the esx2.example.com and virtual machines.
10. Click the entries for each of the virtual machines, lnxvm2 and winvm1 that are
hosted by the esx2.example.com ESX server, then view the Summary tab.
Note that the center pane of the vSphere Web Client user interface displays
detailed information about the selected virtual machine.
You may have to use the scroll bars provided by the vSphere Web Client user
interface to view information available for the selected virtual machine.
The virtual machines, winvm1 and lnxvm2, are currently powered off. Do not
power on the virtual machines at this time.
In this exercise, you have taken a brief tour of the VMware environment provided
for this course, and been introduced to the vSphere Web Client user interface.
In the next exercise, you configure NetBackup to enable access to the

vcenter2.example.com and esx2.example.com servers, to enable backup and
restore operations for the VMware virtual machine environment.
Lab 10-7

11. Click the drop-down arrow to the right of the Administrator@VSPHERE.LOCAL
entry, located in the title bar of the vSphere Web Client user interface.
12. Click Logout in the drop-down menu, and then close the Web browser window.
Continue to Exercise B: Configuring NetBackup to perform VMware backups.

Lab 10-8

Exercise B: 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 will also set resource limits to
prevent backup operations from overtaxing a VMware environment.
Continue to Exercise B-1: Configuring credentials to enable access to VMware.

Lab 10-9

Exercise B-1: 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.
2. Access the NetBackup 8.1 Administration Console on console.example.com.
̶ If a NetBackup Administration Console window is already open, continue to step

3 below.
̶ If a NetBackup Administration Console window is not currently open, double-
click the NetBackup 8.1 Administration Console shortcut, located on the
desktop of the system to open the Administration Console, and then log in to
your preferred master server.
NetBackup master server name User name Password

3. Verify that the NetBackup Administration Console is logged in to your preferred

master sever, winmaster.example.com or lnxmaster.example.com.
The name of the NetBackup server you are connected to is indicated at the top
of the left pane of the Administration Console.
Lab 10-10

4. Select Media and Device Management, then Credentials, then Virtual Machine
Servers in the left pane of the NetBackup Administration Console window.
The right pane of the Administration Console displays entries for any VMware
Virtual Machine Servers that are currently configured in NetBackup.
No VMware virtual machine servers are currently configured in NetBackup.
5. Right-click on Virtual Machine Server and select New Virtual Machine Server from
the short cut menu.
The New Virtual Machine Server dialog box is displayed.
6. Type the IP address of the vCenter Server, 10.10.2.65, in the Virtual Machine Server
Name field of the New Virtual Machine Server dialog box, and then click OK.
In this case, be sure to use the IP address, 10.10.2.65, of the vCenter Server
system. This is important because it is the name that was used when the
vCenter Server software was installed on the vcenter2.example.com system.
The New Virtual Machine Server window, for vcenter2.example.com is displayed.

7. Use the information provided in the table below to populate the fields of the New
Virtual Machine Server window.
Parameter Parameter setting / value

Virtual Machine Server Name: 10.10.2.65
Credentials:
Virtual Machine Server Type: VMware Virtual Center Server
User name; vsphere.local\Administrator
Password: Tra1n!ng
For Backup Host: Any (default)
Connect using Port number: Unchecked (default)
Port Number: 443 (default)
Lab 10-11

8. After completing the entries in the Virtual Machine Servers window, click OK to save
the changes.
When you click OK in the Virtual Machine Servers window, NetBackup verifies
its ability to access and login to the virtual machine server – in this case, to
VCENTER2 (10.10.2.65). There may be a short delay as the ability to connect to
the virtual machine server is verified.
If NetBackup’s ability to connect to the virtual machine server is successfully

verified, a New Virtual Machine Server dialog box is displayed, containing the
message, “User credentials have been validated…”
9. If the “success” message is received, click OK to acknowledge the message in the

New Virtual Machine Server dialog box, and to close the dialog box.
Lab 10-12

If the validation of the connection to the virtual machine server failed, acknowledge
the “failure” message, and verify that the information was entered correctly in the
New Virtual Machine Server window (using the information provided in the table
above), and retry the operation. If the problem persists, notify your instructor.
When the dialog box containing the “success” message is closed, the New Virtual
Machine Server window is also closed.
10. Verify the Virtual Machine Servers entry for 10.10.2.65 is present.
Continue to Exercise B-2: Setting resource limits for VMware backups.

Lab 10-13

Exercise B-2: 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 backup
activity.
1. From the NetBackup Administration Console, select Host Properties, and then click
Master Servers.
2. Right-click on the host name of your master server, winmaster.example.com or

lnxmaster.example.com, and select Properties.
The Master Server Properties window opens.
3. Select the Resource Limit entry in the left pane.
The Resource Limit tab opens in the right pane of the Master Server Properties
window.
4. Select VMWare in the Application column, located in the right pane of the Master
Server Properties window.
The resources that can be limited are displayed. Note that by default, no limits are
set.
Any values entered in the Resource Limit column indicate the maximum
number of backup jobs that use that resource that can run simultaneously.
Backup jobs that meet multiple resource limits will count against the limit for
all applicable resource types.
5. Locate ESXserver in the left (Resource Type) column. Click the associated value in
the right (Resource Limit) column.
The resource limit for ESXserver changes to a text box with a value of 0, with
up/down arrows provided to change the parameter setting.
Lab 10-14

6. Change the value of the ESXserver resource limit to 4.
7. Click OK to save the change and to close the Master Server Properties window.
We will not perform enough concurrent backups in this lab to reach this limit;
we are using 4 jobs per ESX server as an example of a reasonable setting. In an
actual environment there are many factors to consider when determining the
correct resource limits to set. When in doubt about the settings to use, it is
better to be conservative and increase the limit settings only after thorough
testing.
To verify the Resource Limit setting change, with NetBackup Management >
Host Properties > Master Servers selected in the left pane of the
Administration Console, double-click the hostname of your master server
(winmaster.example.com or lnxmaster.example.com) in the right pane, to
open the Master Server Properties window. Then, in the Master Server
Properties window, click the Resource Limit entry in the left pane. Finally, click
the VMware entry in the Application column to display the VMware Resource
Limit settings.
̶ If the resource limit setting of the ESXserver resource type is set to “4”, click
Cancel to close the Master Server Properties window.
̶ If the resource limit setting of the ESXserver resource type is not currently set to
“4”, click the entry for the ESXserver in the Resource Limit column, and change
the value to “4”. Then, click OK to save the Master Server Properties and to
close the window.
8. Minimize the NetBackup Administration Console.
Continue to Exercise C: Installing the NetBackup Plug-in for the VMware vSphere
Web Client.
Lab 10-15

Exercise C: Installing the NetBackup Plug-in for
VMware vSphere Web Client
In this exercise, you install the new NetBackup 8.1 Plug-in for the VMware vSphere Web
Client.
This plug-in provides the prerequisite tools necessary for performing Exercise F:
Excluding disks from a VMware virtual machine backup of this lab activity, as
well as for the Using NetBackup Instant Recovery for VMware feature exercise
in Lab 11.
Continue to Exercise C-1: Verifying the vSphere Web Client (prior to plugin installation).
Lab 10-16

Exercise C-1: Verifying the vSphere Web Client (prior to
plugin installation)
In the steps to follow, you briefly view the vSphere Web Client user interface prior to
the installation of the NetBackup plugin for the VMware vSphere Web Client, and take
note of the absence of NetBackup icons in the vSphere Web Client user interface.
1. Access and log into console.example.com.
console.example.com Username: EXAMPLE\Administrator Password: train
2. Locate and double-click the vSphere Web Client shortcut on the desktop to launch
the vSphere Web Client in a Firefox browser window.
3. In the vSphere Web Client log screen, enter the Username,

vsphere.local\Administrator, and Password, Tra1n!ng, and click Login.
4. When the vSphere Web Client user interface is displayed, click the Home icon in the
blue title bar, if the Home tab is not already present
Lab 10-17

5. View the vSphere Web Client user interface and note the absence of NetBackup
entries or icons in the two areas that are highlighted in the screenshot below.
The absence of the NetBackup icons is an indication that the NetBackup plug-in
for the vSphere Web Client is not installed or registered with the vCenter
Server, vcenter2, to which the vSphere Web Client is currently connected.
6. Close the vSphere Web Client user interface.

If your master server is winmaster.example.com, continue to Exercise C-2: Installing

and registering the NetBackup plugin (Windows).
If your master server is lnxmaster.example.com, continue to Exercise C-3: Installing

and registering the NetBackup plugin (Linux).
Lab 10-18

Exercise C-2: Installing and registering the NetBackup
plugin (Windows)
In the steps that follow, you install and register the NetBackup Plug-in for vSphere Web
Client from the master server, winmaster.example.com, for use by the VMware Virtual
Center Server (vcenter2.example.com). This task is required in order to enable the use
the Exclude Disk Wizard as well as the NetBackup Instant Recovery for VMware (IRV)
feature.
1. Access the desktop of winmaster.example.com.
2. From the desktop, locate and double click the shortcut for File Explorer.
3. In the File Explorer window, change the directory to:
C:\Program Files\Veritas\NetBackup\bin\goodies
4. From the goodies directory locate the vwcp_manage.exe file.

If you cannot find the vwcp_manage.exe file double check to make sure you
are logged into winmaster.example.com.
Lab 10-19

5. Right-click on the vwcp_manage.exe file and select Run as administrator.
6. From the End User License Agreement window select Accept to continue with the
installation wizard.
7. From the VMware vCenter Server Details window enter the vCenter Server
password and verify the following information shown in the table below.
10.10.2.65
Hostname or IP address
vsphere.local\Administrator
Username
Tra1n!ng
Password
443
Port
Lab 10-20

During the installation of the NetBackup plug-in for vSphere Web Client, the
wizard checks to see if credentials were added for the Virtual Machine Server
to NetBackup. If so, then the installer populates the information on this
screen. If vCenter Server credentials were not added to NetBackup then the
credentials can be added at the time of installation.
8. Click Validate to install the plugin.
9. From the Plug-in package location screen review the location then click Register to
continue.
10. Review the Security Alert window, and click Continue.
11. When the Finish screen is displayed, click Close.
You have completed the installation of the NetBackup Plug-in for the vSphere Web
Client on VCENTER2 (10.10.2.65), and the registration of the plug-in on the windows
master server, winmaster.example.com.
Continue to Exercise C-4: Verifying the NetBackup plug-in installation and

registration.
Lab 10-21

Exercise C-3: Installing and registering the NetBackup
plugin (Linux)
In the steps that follow, you install and register the NetBackup Plug-in for vSphere Web
Client for the master server, lnxmaster.example.com, for use by the VMware Virtual
Center Server (vcenter2.example.com). This task is required to enable the use the
Exclude Disk Wizard and the NetBackup Instant Recovery for VMware (IRV) feature.
2. From the desktop, locate and double-click on File Explorer.
3. Navigate to C:\Tools.
4. From the Tools directory, double-click on MobaXterm_Personal_6.2.exe.
Lab 10-22

One of the requirements for installing the NetBackup 8.1 Plug-in for vSphere
Web Client on a UNIX/Linux system is that the environment support Java GUI
applications. See the Veritas NetBackup Plug-in for VMWare vSphere Web
Client Guide for further details.
5. After MobaXterm is started on console.example.com, minimize the MobaXterm

window.
In this lab environment, MobaXterm needs to be running to enable the export of the
Java display from lnxmaster.example.com to console.example.com.
6. From the desktop, locate and double click the REMOTE SYSTEM ACCESS shortcut.
7. In the Windows Explorer window, double-click the Putty shortcut to open the PuTTY
Configuration window.
8. From the Saved Sessions, double-click the lnxmaster.example.com to launch a

PuTTY session to the master server, lnxmaster.example.com.
You may need to adjust the size of the Terminal window.
9. From the Terminal window login with the following credentials: login: root
password: train.
10. From the Terminal window type the following command:
Command: export DISPLAY=10.10.2.6:0.0
Exporting the display enables the NetBackup plugin installation script to run.
11. Change the directory to /usr/openv/netbackup/bin/goodies.
Command: cd /usr/openv/netbackup/bin/goodies
Lab 10-23

12. List the files in the goodies directory and locate the vwcp_manage command.
Command: ls
13. Type the following command and press Enter, to start the NetBackup plugin
installation.
Command: ./vwcp_manage
If the NetBackup Plug-in for VMware vsphere Web Client window does not pop
up, please check the taskbar for icon show below. The plugin window may be
under other windows.
14. In the End User License Agreement window, click Accept.

Lab 10-24

15. In the VMware vCenter Server Details window, enter the vCenter Server password
and verify the following information shown in the table below.
10.10.2.65
Hostname or IP address
vsphere.local\Administrator
Username
Tra1n!ng
Password
443
Port
If you run the NetBackup plug-in for vSphere Web Client with administrator or
root privileges, the command discovers the available vCenter Servers and
presents them in the drop-down list. Otherwise, you can provide the vCenter
Server name and credentials in this window.
16. Click Validate to install and register the plugin.
17. From the Plug-in package location screen review the location then click Register to
continue.
18. Review the Security Alert window and click Continue.
Lab 10-25

19. When the Finish screen is displayed, click Close.
20. Access the minimized MobaXterm window, and then close the window.
MobaXterm was only needed while running the NetBackup plugin installation
script, to export the display from lnxmaster.example.com to
21. Close the PuTTY window to lnxmaster.example.com.
22. Close any File Explorer windows that may still be open on console.example.com.
You have completed the installation of the NetBackup Plug-in for the vSphere Web
Client on VCENTER2 (10.10.2.65), and the registration of the plug-in on the Linux
master server, lnxmaster.example.com.
Continue to Exercise C-4: Verifying the NetBackup plug-in installation and

registration.
Lab 10-26

Exercise C-4: Verifying the NetBackup plug-in installation
and registration
In the steps to follow, you view the vSphere Web Client interface that is connected to
the vCenter Server, vcenter2.example.com, to verify the installation and registration of
the NetBackup vSphere Web Client plug-in.
2. Locate and double-click the vSphere Web Client shortcut, located on the desktop of
console.example.com, to launch the vSphere Web Client window.
3. When the vSphere Web Client log screen is displayed, enter the Username,
vsphere.local\Administrator, and the Password, Tra1n!ng, and click
Login.
4. When the vSphere Web Client user interface is displayed, click the Home icon in the
blue title bar, if not already selected.
Lab 10-27

5. Verify the presence of the Veritas NetBackup entry in the Navigator pane of the
vSphere Web Client window and in the Home tab of the right pane of the window
The Veritas NetBackup entries are only present in the vSphere Web Client user
interface when the NetBackup plugin has been successfully installed and
registered.
6. If the Veritas NetBackup entries are not present in the vSphere Web Client window,
notify your instructor.
You have now successfully completed installing the NetBackup plug-in for vSphere
Web Client.
7. Close the vSphere Web Client user interface.
Continue to Exercise D: Configuring a VMware policy.
Lab 10-28

Exercise D: 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.
Continue to Exercise D-1: Creating a VMware policy.

Lab 10-29

Exercise D-1: 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.
2. Access the minimized NetBackup 8.1 Administration Console window.

The policies that are currently configured are listed in the All Policies pane of the
4. Right-click, in the white space, in the All Policies pane and select New Policy from
the shortcut menu.
5. Type the name of the new policy, LAB10-vmware, in the Policy name field of the
Add a New Policy dialog box, and then click OK.
The LAB10-vmware policy is opened for editing in the Change Policy window.
Continue to the Exercise D-2: Configuring the policy Attributes.
Lab 10-30

Exercise D-2: Configuring the policy Attributes
In the steps that follow, you will configure the Policy type and Policy Storage in the
Attributes tab of the LAB10-vmware policy.
1. In the policy Attributes tab, select the drop-down arrow for the Policy type field
and, from the drop-down list, select VMware.
You may have to use the scroll bar in the Policy type drop-down menu to
locate the VMware policy type selection.
2. 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: master_advdisk_stu
All other policy Attributes: leave at default settings
3. 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 is added to the policy.
Continue to the Exercise D-3: Configuring the policy Schedule.
Lab 10-31

Exercise D-3: Configuring the policy Schedule
In the steps that follow, you will configure a full schedule for the LAB10-vmware policy.
1. Click the Schedules tab in the Change Policy window.
2. Create a new schedule using the parameters provided in the table below.
Schedule Attributes tab

Name: full
Type of backup Full Backup
All other schedule Attributes: Use default settings
Start Window tab: Use all defaults (no start window)
Exclude tab Use all defaults (no exclusions)
3. In the Add Schedule – Policy LAB10-vmware window, click OK to save the full
schedule.
Continue to the Exercise D-4: Configuring the policy VMware tab selections.
Lab 10-32

Exercise D-4: 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.
1. Click the VMware tab in the Change Policy window.
2. 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). VMware Access Hosts
are configured in the Master Server Host Properties > VMware Access Hosts
window.
Lab 10-33

3. Click the drop-down arrow for the Primary VM identifier field on the VMware tab
and select the entry for VM display name.
The default selection in the Primary VM identifier field is VM hostname.
4. Verify that the Primary VM identifier field is set to a 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.
5. Leave all other settings at their default values.

Lab 10-34

6. Click the Advanced button, located at the bottom of the VMware tab.
7. Briefly view the parameters that can be set in the VMware - Advanced Attributes
window.
8. Click Cancel to close the VMware - Advanced Attributes window. No changes are
required.
Continue to the Exercise D-5: Manually selecting virtual machines to backup.
Lab 10-35

Exercise D-5: Manually selecting virtual machines to
backup
In the steps that follow, you view and manually select VMware virtual machines for
backup.
1. Click the Clients tab in the Change Policy window.
2. Click the Select manually radio button, located in the Virtual Machines for backup
section.
When you choose the Select manually radio button, a Backup Policy
Management dialog box is displayed. This dialog box enables you to confirm
that you are changing the policy from the use of automatic virtual machine
selection to manual virtual machine selection.
3. Click Yes in the Backup Policy Management dialog box, to confirm the selection.
4. Click the New button, located near the bottom of the Clients tab.
The Browse for Virtual Machines window is displayed.
Lab 10-36

5. Click the Browse for Virtual Machines radio button, highlighted near the top of the
Browse for Virtual Machines window.
Within a few moments, the left pane of the Browse for Virtual Machines window is
updated to display a Hosts and Clusters entry, with an entry for the vCenter Server,
10.10.2.65, displayed beneath it.
The Hosts and Clusters entry has an entry for the vCenter Server, 10.10.2.65,
beneath it. NetBackup has obtained the structure of the VMware environment
by querying the vCenter Server.
6. Expand the entry for the vCenter Server, 10.10.2.65. 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, esx2.example.com is
displayed.
7. Click to highlight the entry for esx2.example.com (but do not click the check box),
located in the left pane of the Browse for Virtual Machines window.
The right pane of the Browse for Virtual Machines window displays entries for the
virtual machines that are hosted by the ESX server, esx2.example.com. The check
boxes for the VMs enable you to manually select the virtual machines that you want
to back up using this policy.
Lab 10-37

8. View the virtual hosts that are available for backups on the esx2.example.com
server.
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.
9. 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.
Continue to Exercise D-6: Creating a query to select virtual machines to backup.

Lab 10-38

Exercise D-6: Creating a query to select virtual machines
to backup
In the steps that follow, you configure the NetBackup 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.
1. Select the radio button for Select automatically through VMware Intelligent Policy
query, located near the top of the Clients tab of the Change Policy window.
When you choose the “Select Automatically…” radio button, a Backup Policy
Management dialog box is displayed, to allow you to confirm that you are
changing the policy from the use of manual virtual machine selection to
automatic virtual machine selection.

Lab 10-39

2. Click Yes in the Backup Policy Management 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.
̶ The first part of the query selects a virtual machine using the virtual machine
Display name.
̶ The second part of the query selects VMs that are running a particular operating
system.
Lab 10-40

3. Build the first part of the query using the information provided in following table.
Query Builder field Setting:

Join: --vacant field--
Field Displayname (change)
Operator Equal (change)
Value(s) "winvm1"
(Click on the folder icon to the right of the Value(s):
field, then select winvm1).
4. Enter the settings for the query into the Query Builder fields and click the plus (+)
button, to Add the query (see below).
5. Verify the first part of the query is added to the Query (Basic Mode) pane of the
Clients tab.
Note that the Values for the queries are enclosed in double quotes (“).
6. Add a second part to the query using the information provided in the table below.
Query Builder field Setting:

Join: OR (change)
Field VMGuestOS (change)
Operator Equal (change)
Value(s) “other26xLinuxGuest”
(Click on the folder icon to the right of the
Value(s): field, then select other26xLinuxGuest).
7. Enter the settings for the query into the Query Builder fields and click the plus (+)
button, to Add the query.
Lab 10-41

8. Verify the second part of the query is added to the Query (Basic Mode) pane of the
Clients tab.
9. Click the Test Query button, located on the Clients tab.
10. Verify the test query results show the two VMs were discovered, winvm1 and
lnxvm2, and that both VMs were Included (for backup) by the query operation.
The Test Query may take a minute or more to complete.

11. Click the Close button, to close the Test Query window.
Continue to Exercise D-7: Verifying the policy Backup Selections.
Lab 10-42

Exercise D-7: Verifying the policy Backup Selections
When a policy uses an automated query 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.
1. Click the Backup Selections tab in the Change Policy window.
2. Verify the Backup Selections List contains an entry 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 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.
The actual backup selection is always ALL_LOCAL_DRIVES for VMWare

intelligent policies (that use a query to automatically discover VMs to back up).
Since this cannot be changed NetBackup uses the backup selections tab to
display the VIP query. If you manually browse to select VMware clients to back
up, you may specific VM contents to back up in the Backup Selections tab.
Continue to the Exercise D-8: Saving the policy changes.
Lab 10-43

Exercise D-8: Saving the policy changes
In the steps that follow, you will save all the changes that were applied to the LAB10-
vmware policy.
1. Click OK in the Change Policy window to save the LAB10-vmware policy changes,
and to close the Change Policy window.
NetBackup validates the setting of the policy. If a problem is encountered with

the policy, an error dialog box is displayed.
2. Verify that the LAB10-vmware policy is added to the list of policies that is displayed
in the All Policies pane of the Administration Console.
In this exercise you created a NetBackup policy, named LAB10-vmware that enables
manual, full backups of VMware virtual machines that are discovered by NetBackup
using an automated query. 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 server, xxxmaster.example.com
(winmaster.example.com or lnxmaster.example.com).
Continue to Exercise E: Performing and monitoring VMware virtual machine

backups.
Lab 10-44

Exercise E: Performing and monitoring VMware
virtual machine backups
In this exercise, you use the LAB10-vmare 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.
Continue to Exercise E-1: Initiating a manual backup.

Lab 10-45

Exercise E-1: Initiating a manual backup
In the steps that follow, you initiate a manual backup of the LAB10-vmware policy and
monitor the backup until completion.
2. Access the NetBackup 8.1 Administration Console window.

4. Right-click the entry for the LAB10-vmware policy, located in the All Policies pane,
then select Manual Backup.
The Clients pane 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.
5. Click the OK button in the Manual Backup window without making any other
selections, to initiate the manual backup operation.
6. Select the Activity Monitor entry in the left pane of the NetBackup Administration
Console window.
Lab 10-46

7. Click the View jobs in a hierarchical manner icon in the Activity Monitor tool bar, to
display the new jobs in a hierarchical view.
8. 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 LAB10-vmware policy.
It may take several minutes for all the resulting jobs to be added to the Activity
Monitor.
9. 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 Backup job (parent job) listed as master server –
number): xxxmaster.example.com
Second job: Snapshot winvm1
Third job: Snapshot lnxvm2
Fourth job: Backup winvm1
Fifth job: Backup lnxvm2
10. Allow all the jobs to run to completion before continuing.
In some cases, it may take a while (10 minutes +) for all jobs to run to
completion. Please be patient. The time required to complete the jobs is
dependent upon the lab delivery environment being used to perform the lab.
11. 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 notify your instructor.
Lab 10-47

12. View the Job Details for each of the jobs that resulted from the manual backup of
the LAB10-vmware policy. Note that the parent-child relationship of these jobs can
be clearly seen in the Job Hierarchy tab of the Job Details window, and in the
hierarchical view of the job in the Activity Monitor.
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 and lnxvm2). The
hostname of the master server is listed as the client for the parent job. This is
because the master server is the Backup Host that uses the automated query
to discover the VMs to back up.
When viewing the VMware jobs in the hierarchical view, the jobs are not
displayed in numeric order (see the screenshot above). This is expected
behavior.
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.
13. Close any open Job Details windows.
Leave the NetBackup Administration Console open as you will use it in a later
exercise.
Continue to Exercise F: Excluding disks from a VMware virtual machine backup.
Lab 10-48

Exercise F: Excluding disks from a VMware virtual
machine backup
In this exercise, you 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, LAB10_excluding_disks, to apply the Custom Attribute to the policy.
Continue to Exercise F-1: Configuring a VMware custom attribute to exclude virtual

disks.
Lab 10-49

Exercise F-1: 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.
2. Double-click on the vSphere Web Client shortcut on the desktop.
3. Log into the vSphere Web Client using the User name:
vsphere.local\Administrator and password: Tra1n!ng, click the Login
button.
Be sure to use the above credentials when logging in to the vCenter Server. The
use of other credentials may allow you to log in, but your results will not be the
same as when the correct credentials are used.
Within a few moments, the vSphere Web Client is connected to the vCenter server.
4. From the Home screen click Veritas NetBackup.

If the vSphere Web Client is not at the Home screen then click the Home icon
located at the top of the screen.
5. Select the Virtual Disk Exclusion Wizard.
Lab 10-50

6. From the Virtual Disk Exclusion Wizard verify the vCenter Server entry is set to
10.10.2.65.
7. In the Custom Attribute field, type exclude_vm_disk.
The default Custom Attribute name is set to NB_DISK_EXCLUDE_LIST, but you

are creating a unique name for this Custom Attribute.
8. In the Search field type winvm1 then click Search.
9. From the Search Results, select winvm1, then click the +Add Virtual Machines
button located in the lower right corner.
One virtual machine is added to the Custom Attribute as shown in the figure below.
Lab 10-51

10. Verify that one (1) Virtual Machine was added in the upper left corner of the Virtual
Disk Exclusion Wizard.
11. Click Next.
12. In the Available Disks section, mark the checkbox for Hard disk 1, scsi0-0.
13. Click Next.
14. In the Virtual Machines and Excluded Disks section, select winvm1, then click the
Set Exclusions button.
15. After the “Successfully set virtual disk exclusions” message is

displayed, click Finish.
You have created a VMware Custom Attribute to exclude disk1 for the virtual
machine, winvm1.
Lab 10-52

16. Log out of the vSphere Web Client user interface, and close the Web browser win-
dow.
Continue to Exercise F-2: Configuring a policy to exclude disks from a VMware

backup.
Lab 10-53

Exercise F-2: Configuring a policy to exclude disks from a
VMware backup
In the steps that follow, you configure a VMware policy, LAB10-exclude_disk, to exclude
virtual disks with a custom attribute that was created in the previous exercise.
2. Access the minimized NetBackup 8.1 Administration Console window.

4. Right-click the LAB10-vmware policy and select Copy to New… from the shortcut
menu.
5. In the New Policy field, type LAB10-exclude_disk, then click OK to create a new
policy.
6. Click the Clients tab.
Lab 10-54

7. In the Query (Basic Mode) section, click the bottom query, OR VMGuestOS Equal
“other26xLinuxGuest”, then click Remove.
8. Click Yes to confirm the removal of this entry.
Only the Displayname Equal “winvm1” entry remains in the Query (Basic Mode)
section.
9. 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.
10. Click Close to close the Test query window.
11. Click the Exclude Disks tab.
12. Select the radio button for Perform custom attribute based exclusion option.
Lab 10-55

13. 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).
14. Click OK to save the policy.
Continue to the Exercise F-3: Performing and monitoring a VMware backup.
Lab 10-56

Exercise F-3: Performing and monitoring a VMware
backup
In the steps that follow, you initiate a manual backup of the LAB10-exclude_disk policy
and monitor the backup job until completion.
1. Access the NetBackup 8.1 Administration Console window and log into your desired
master server.

3. Right-click the entry for the LAB10-exclude_disk policy, located in the All Policies
pane, then select Manual Backup.
4. Click the OK button in the Manual Backup window without making any other
selections, to initiate the manual backup operation.
5. Select the Activity Monitor entry in the left pane of the NetBackup Administration
Console window to monitor the backup job.
6. 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 couple of minutes for all the resulting jobs to be added to the
Activity Monitor.
7. Double-click the backup job that has the Job Schedule of full associated with it. This
should be the job with the highest Job Id.
Lab 10-57

8. View the Detailed Status of this job, and verify that the job completes successfully
(status 0).
̶ If the job completes successfully, continue to the next step.

̶ If any of the VMware jobs that use the LAB10-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 LAB10-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 Current Kilobytes Written field in the Detailed Status 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 E-1). The Current Kilobytes Written for the most recent job should be
substantially less than in the previous job (which did not exclude disks from the
virtual machine backup)>
9. Close any open windows.
Lab 10-58

Lab 11: Recovering Virtual Machines
In this lab, you use various NetBackup and VMware methods to restore individual files
to VMware virtual machines, restore a disk to a VMware virtual machine, recover an
entire VMware virtual machine, and perform Instant Recovery for VMware.
This lab activity depends upon backups of virtual machines that were
performed in Lab 10 of this course. If you have not completed Lab 10,
complete that lab activity before performing this lab activity.
To recover individual files to a Windows-based virtual machine, click the link to continue
to Exercise A: Recovering virtual machine files.
Lab 11-1

Exercise A: Recovering virtual machine files
You may perform this exercise using either NetBackup master sever,
winmaster.example.com or lnxmaster.example.com. Use the same master
server as you have used in previous lab exercises in this course.
If you are not interested in performing the steps to recover individual files to a VMware
virtual machine, click the link to continue to Exercise B: Recovering a VMware Virtual
Machine disk.
To recover individual files to a VMware virtual machine, continue to the steps below.
This lab activity is dependent upon backups of virtual machines that were
performed in Lab 10 of this course. If you have not completed lab 10, you must
do so before continuing with this lab activity.
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.
Continue to Exercise A-1: Powering on the winvm1 virtual machine.

Lab 11-2

Exercise A-1: Powering on the winvm1 virtual machine
In the steps that follow you use the vSphere Web client to power on the winvm1 virtual
machine.
To recover individual files to a VMware virtual machine requires that the virtual
machine be powered on. To recover individual file and folder contents to the
VM requires the NetBackup Client software to be installed on the VM. The
NetBackup 8.1 Client software has been pre-installed on winvm1.
1. Access the desktop of console.example.com
2. Locate and double-click the vSphere Web Client shortcut on the desktop of
console.example.com to launch the VMware vSphere Web Client.
3. When the vSphere Web Client login screen is displayed, type the User name and
password for the vCenter server, vcenter1.example.com, provided below, and click
the Login button.

Within a few moments, the VMware vSphere Web Client is connected to the
vCenter server and the VMware vSphere Web Client user interface is displayed.
4. Click the Home icon, in the blue banner of the VMware vSphere Web Client.
Lab 11-3

5. In the Inventories pane, click the icon labeled Hosts and Clusters.
The left pane of the VMWare vSphere Web Client also displays the Hosts and
Clusters tree.
6. Click the symbol to the left of the entries in the tree-view, if needed, to expand the
view.
The left pane of the vSphere Web Client user interface is updated to display an
entry for DC1 (DC = Datacenter).
The vCenter server, vcenter2.example.com, is registered as the IP address,

10.10.2.65.
Lab 11-4

7. Right-click the entry for winvm1, located in the left pane of the interface, and select
Power then Power On from the shortcut menu.
8. In the right pane, click the Summary tab, if it is not already displayed.
9. Monitor the Summary tab to ensure the winvm1 host is Powered On.
You may need to select the refresh button on the blue banner bar.
The virtual machine is powered on when a green arrow next to the winvm1
name in the left pane, and in the black box that represents the VM in the
Summary tab of the vSphere Web Client.
10. Allow the VMware vSphere Web Client window to remain open on
Continue to Exercise A-2: Launching Backup, Archive, and Restore from the
Lab 11-5

Exercise A-2: Launching Backup, Archive, and Restore
from the NetBackup Administration Console
In this exercise, you restore virtual machine files directly to the Windows-based virtual
machine, winvm1, 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:
• Step one: Use NetBackup to restore the individual VM files to an alternate
NetBackup client system.
• 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.

2. 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.
Continue to Exercise A-3: Using NetBackup to restore individual VMware virtual

machine files to a VMware VM.
Lab 11-6

Exercise A-3: 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, winvm1.
1. In the Backup, Archive, and Restore pane, click the Restore Files tab.
2. Click the ‘pointing finger’ icon to access the Specify NetBackup Machines and Policy
Type window.
You can also select Actions > Specify NetBackup Machines and Policy Type to
access this screen.
3. In Specify NetBackup Machines and Policy Type window, change the Policy type to
VMware.
Lab 11-7

4. Click the Search VM Clients button in the Specify NetBackup Machines and Policy
Type window.
5. When the Browse and Search Virtual Machines for Restore screen is displayed, click
the Browse virtual machines and vSphere view radio buttons.
7. On the Browse and Search Virtual Machines for Restore screen, expand the entries
for 10.10.2.65 (vCenter server) and the /DC1 data center.
8. Click to select the esx2.example.com entry which reveals entries for the virtual
machines that have been backed up – winvm1 and lnxvm2.
winvm1 and lnxvm2 were backed up during the previous lab activity (lab 10) of
this course. You must complete Lab 10 before performing this lab activity.
9. Click the entry for the virtual machine, winvm1 and click Select to continue.
You are returned to the Specify NetBackup Machines and Policy Type window.
Lab 11-8

10. In the Destination client for restores field, select winvm1.
If winvm1 is not present in the Destination client for restores drop-down list, see
the Note below.
If an entry for winvm1 is not present in the drop-down list for the Destination
client for restores field, click the Edit Client List button, and then add an entry
for winvm1 to the client list.
11. Check the values that you have specified in the Specify NetBackup Machines and
Policy Type window as described below.
̶ Server to use for backups and restores: field should contain the name of your
master server, either winmaster.example.com or lnxmaster.example.com
̶ Source client for restores: winvm1
̶ Destination client for restores: winvm1
̶ Policy type for restores: VMware
12. Click OK to save the Specify NetBackup Machines and Policy Type window entries.
13. If a message appears that says ‘no files are found’, click OK to acknowledge the
message and continue.
Lab 11-9

14. In the Restore type field, verify the Normal Backups entry is selected in the drop
down menu.
Normal Backups is the default selection.
15. If / (forward slash) is not already present in the Browse Directory field, type a / in
the Browse directory field, and press Enter.
16. Expand the contents of the Directory Structure pane so that C/data/smallfiles
folder is visible in the directory structure of the backup image.
17. In the Directory Structure pane, click the entry for the smallfiles 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).
Lab 11-10

18. In the Contents of selected directory pane, click the check boxes for the first ten
files of the smallfiles folder (file000.txt – file009.txt), to select the files
for restore.
20. When the Restore Marked Files screen is displayed, verify that the Restore
everything to its original location radio button is selected.
21. In the Options area of the Restore Marked Files window, click the check box for the
Overwrite existing files parameter.
Lab 11-11

22. 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.
23. Click the Yes button in the View Progress dialog box to observe the progress of the
restore operation.
24. 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.
25. Verify that the restore operation is completed successfully before continuing.
Lab 11-12

̶ If the restore job is successful, continue to the next step.
̶ 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 starting from Exercise A-3: page 9, step 11. If the restore
operation continues to fail, seek technical assistance.
At this point, you have restored ten (10) files that were backed up from the
winvm1 virtual machine to the original folder location of the files on the client.
26. Minimize the NetBackup Administration Console window.
You will access the NetBackup Administration Console window again in a later
exercise.
27. Allow the VMware virtual machine, winvm1, to remain powered on.
In the next exercise of this lab, you restore a virtual disk to the VMware virtual
machine, winvm1. Steps performed in that exercise require that the VM be
powered on.
Continue to Exercise B: Recovering a VMware Virtual Machine disk.

Lab 11-13

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 a backup that was
performed in Lab 10: Protecting Virtual Machines.
It is necessary to have performed Lab 10: Protecting Virtual Machines prior to

attempting to complete the steps of this exercise.
Continue to Exercise B-1: Restoring an individual virtual disk.

Lab 11-14

Exercise B-1: 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. In order to perform this exercise, you must
have completed Lab 10: Exercise B: Excluding disks from VMware backups.
1. Access the desktop of the console.example.com system a log in (if necessary) using
the credentials provided below.
console.example.com User name: Example\Administrator Password: train
2. Access the vSphere Web Client window on console.example.com.
The vSphere Web Client window may be open from a previous exercise.
̶ If the vSphere Web Client window is already open, continue to step 3.

̶ If a vSphere Web Client window is not currently open, locate and double-click
the vSphere Web Client shortcut to launch the vSphere Web Client interface.
3. Log in to the vCenter Server, vcenter2, if necessary, using the credentials provided.

4. Click the Home icon, then Hosts and Clusters.
5. Verify that the winvm1 virtual machine is powered on.

̶ If winvm1 is already powered on, continue to step 6.

̶ If winvm1 is not currently powered on, complete the sub-steps below.
a. Right-click the winvm1entry in the left pane of the vSphere Web Client window.
b. In the menu, click Power, and then click Power On, as illustrated below.
Lab 11-15

It may take several minutes for winvm1 to power on. Click the refresh icon
in the blue menu bar to update the status of the VM.
6. After verifying that winvm1 is powered on, minimize the vSphere Web Client
window.
7. On the desktop of console.example.com, double-click the REMOTE SYSTEM ACCESS

folder, to open the folder.
8. In the window that is displayed, double-click the RDP Profiles (Windows systems)
folder.
9. In the RDP Profiles (Windows systems) folder, double-click the winvm1.rdp profile
to launch a remote session to winvm1.
After the power on of winvm1, it may take several minutes before the system
is ready to accept the RDP connection. If the initial connection attempt is
unsuccessful, wait a minute and try again.
10. When the Windows Security window is displayed, verify the logon account is set to
EXAMPLE\Administrator and, in the Password field, type train. Then click OK.
11. On the desktop of winvm1, double-click File Explorer.
12. Navigate to the F:\data3\smallfiles directory.

13. Click the entry for the smallfiles directory in the left pane.
Lab 11-16

14. Press the Delete key to permanently delete the smallfiles directory.
15. Click Yes to confirm the deletion, and verify that the smallfiles directory has been
deleted.
17. Log out (Sign out) of the winvm1.example.com system.
When you log out of the winvm1 system, the RDP session and window from
console.example.com to winvm1 is closed.
18. On the desktop of console.example.com, close the RDP Profiles (Windows systems)
window.
19. In the NetBackup 8.1 Administration Console window on console.example.com,

access the Backup, Archive, and Restore.
20. Select the Restore Files tab, if it is not already selected.
21. Click Actions, then Specify NetBackup Machines and Policy Type.
22. In the Specify NetBackup Machines and Policy Type window, from the Policy type
for restores drop-down menu, select VMware.
Lab 11-17

23. Click Search VM Clients.
24. In the Selection Method section verify Search virtual machines is selected, then
click Next.
25. Type winvm in the Browse and Search Virtual Machines for Restore, then click
Next.
26. From the resulting search, select the winvm1 host, then click Select.
Lab 11-18

27. After you have verified the host names are selected in the Specify NetBackup
Machines and Policy Type window – as shown below, click OK to save the changes.
Server: your preferred master, winmaster.example.com or lnxmaster.example.com

Source client: winvm1
Destination client: winvm1
Policy type for restores: VMware
DO NOT use the hostname winvm1.example.com 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.
28. Click the Actions menu, then Set Date Range, then Backup History.
29. Select the most recent backup that belongs to the LAB10-exclude_disk policy, then
click OK.
Lab 11-19

30. From the Restore type drop-down menu select Virtual Disk Restore.
31. From the Contents of winvm1 pane locate the Policy column.
You may need to scroll to the right to locate the Policy column.
32. 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.
33. 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.
34. In the Directory Structure pane, mark the checkbox for winvm1 then click Restore….
A Restore Virtual Machine Disks wizard is launched.
35. In the Select Virtual Disks window, take note that there are three (3) Virtual Disks
listed.
Lab 11-20

36. In the Select Disks pane, mark the last checkbox listed, [INT_ESX2_DS1]
winvm1/winvm1_2.vmdk, then click Next.
The disk with the yellow caution symbol indicates this virtual disk has no
data to be restored. In Lesson 10: Protecting Virtual Machines a VMware
Custom Attribute was created that excluded this disk, scsi0-0. Then a policy
was created to exclude any disks that were associated with that Custom
Attribute.
37. Review the Recovery Destination screen options, but leave all settings at their
default values.
39. Review the Virtual Disk Destination screen options, then click Next to continue.
40. 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 tells NetBackup to
restore the virtual disks to their original provisioned state - thin.
Lab 11-21

41. Click Next, then click OK, to acknowledge that you have selected to overwrite the
virtual disks.
42. Review the Recovery Summary screen contents, then click Start Recovery.
43. Click Yes to view the progress of the restore.
44. 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 (Exercise B-1). If failures persist, seek
technical assistance.
You can also view progress of the restore job using the Activity Monitor.
45. Open a new Remote Desktop (RDP) session from console.example.com to winvm1.
b. Double-click the RDP Profiles (Windows systems) folder in the REMOTE SYSTEM
ACCESS folder.
c. Double-click the winvm1.rdp file, to open an RDP session to winvm1.
d. Log in to winvm1, with the username, EXAMPLE\Administrator, and the
password, train.
46. From the desktop of winvm1, double-click File Explorer.
47. Navigate to F\:data3 directory and verify the smallfiles directory and its contents
have been restored.
48. Close the File Explorer window on winvm1.
49. Log out (Sign out) of the winvm1 system.
When you log off the winvm1 system, the Remote Desktop (RDP) session from
console.example.com to winvm1 will be closed, and you will be returned to
the desktop of console.example.com.
Continue to Exercise B-2: Power off the winvm1 virtual machine.
Lab 11-22

Exercise B-2: Power off the winvm1 virtual machine
In the steps below, you power off the virtual machine, winvm1.
Due to the limited lab environment resources it is important to power off the
nested virtual machines when it is not required that they are powered on.
1. On the desktop of console.example.com, access the minimized VMware vSphere

Web Client window.

2. Right-click the winvm1 virtual machine entry in the left pane, click the Power entry
in the menu, followed by Shut Down Guest OS.
3. When the Confirm Shut Down dialog box is displayed, click Yes to continue.
4. From the Summary tab, monitor the winvm1 VM to verify the state of the VM
changes to Powered Off.
You may need to click the Refresh icon to update the status of the VM.
5. Minimize the VMware vSphere Web Client window on console.example.com.
Continue to Exercise C: Recovering an entire VMware virtual machine.
Lab 11-23

Exercise C: Recovering an entire VMware virtual
machine
In this exercise, you use the NetBackup Administration Console to recover an entire
VMware virtual machine to its original datastore location on a VMware ESX server.
You can perform this exercise using either the Windows-based master server,
winmaster.example.com or the Linux-based master server,
This lab activity is dependent upon backups of virtual machines that were
performed in Lab 10 of this course. If you have not completed lab 10, you must
do so before continuing with this lab activity.
Continue to Exercise C-1: Deleting a VMware virtual machine.

Lab 11-24

Exercise C-1: Deleting a VMware virtual machine
In the next steps you delete a VM from the VMware ESX server, esx1.example.com.
1. From the desktop of console.example.com access the vSphere Web Client user
interface.

If a VMware vSphere Web Client window is not open, use the shortcut on the
desktop of console.example.com to open a Web browser window and log in to
the vCenter Server, running on the system, vcenter2.example.com.
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. From the Home icon click Hosts and Clusters.
3. Expand the DC1 and esx2.example.com entries in the left pane, as necessary, to
view the entries for the 2 virtual machines, lnxvm2 and winvm1.
4. Click the entry for the lnxvm2 virtual machine.

Lab 11-25

5. Right-click the virtual machine lnxvm2, and select Delete from Disk entry in the
menu.
VMware only allows the deletion of virtual machines that are powered off.
6. When the Confirm Delete dialog box is displayed, click the Yes button to confirm the
delete operation.
7. Verify that the entry for the lnxvm2 virtual machine is no longer visible in the left
pane of the vSphere Web Client.
Lab 11-26

8. Allow the vSphere Web Client window to remain open on console.example.com,
but minimize the window.
You return to the vSphere Web Client window later in this exercise.
Continue to Exercise C-2: Preparing to recover a virtual machine using the Backup,
Archive and Restore (BAR) user interface.
Lab 11-27

Exercise C-2: Preparing to recover a virtual machine using
the Backup, Archive and Restore (BAR) user interface
In the following steps, you select the virtual machine, lnxvm2, to initiate the recovery of
the virtual machine.
1. From the NetBackup Administration Console window on console.example.com

access Backup, Archive, and Restore.
2. Select the Restore Files tab, if not already selected.
3. Click the ‘pointing finger’ icon to access the Specify NetBackup Machines and Policy
Type window.
You can also select Actions > Specify NetBackup Machines and Policy Type to
access this user interface.)
The right pane of the Administration Console displays the Backup, Archive, and
Restore user interface, as shown below.
The screen shots in this exercise illustrate the use of winmaster.example.com

as the NetBackup master server. If you are using the Linux-based master
server, the master server is lnxmaster.example.com.
Lab 11-28

4. In Specify NetBackup Machines and Policy Type window, select VMware in the
Policy type drop down menu.
5. Click the Search VM Clients button.
6. When the Browse and Search Virtual Machines for Restore screen is displayed, click
the Browse virtual machines and vSphere view radio buttons.
7. Click Next to continue
8. When the next Browse and Search Virtual Machines for Restore screen is displayed,
expand the entries for 10.10.2.65 (vCenter Server) and /DC1.
Lab 11-29

9. Click the esx2.example.com entry to reveal entries for the virtual machines that
have been backed up in this environment – winvm1 and lnxvm2.
The VMware virtual machines, winvm1 and lnxvm2, were backed up in Lab 10:
Protecting Virtual Machines.
10. Click the entry for the virtual machine, lnxvm2 (the VM that you deleted earlier in
this exercise), then click Select.
11. Verify that lnxvm2 is selected in the Destination client for restores field of the
12. Verify that the Specify NetBackup Machines and Policy Type window contains the
following entries:
̶ Server to use for backups and restores: Your master server, either
̶ Source client for restores: lnxvm2
̶ Destination client for restores: lnxvm2
̶ Policy type for restores: VMware
Lab 11-30

13. Click OK in the Specify NetBackup Machines and Policy Type window.
The Specify NetBackup Machines and Policy Type window closes and the Backup,
Archive, and Restore user interface is displayed.
14. From the Restore type field, use the drop-down menu to select Virtual Machine
Backups.
After making the Restore Type selection, note that the Directory Structure
pane contains the list of VMs that meet the criteria you have established for
the restore.
15. Click the Actions drop-down menu, and from the menu select Set Date Range, and
then select Backup History.
16. In the Backup History window, click the entry for the most recent backup image,
that was created using the LAB10-vmware policy.
17. Click OK to close the Backup History window.

18. From the Directory Structure pane mark the check box to the left of the entry for
lnxvm2 to select that virtual machine for recovery.
File selection choices are no longer visible in the Directory Structure pane.
Entries for entire virtual machines that have been backed up and that meet the
selection criteria are listed.
NetBackup launches and displays the Virtual Machine Recovery wizard.
Continue to Exercise C-3: Restoring an entire VMware virtual machine.
Lab 11-31

Exercise C-3: Restoring an entire VMware virtual machine
In the following steps you use the Virtual Machine Recovery wizard to restore the
virtual machine, lnxvm2.
1. In the Recovery Destination screen of the wizard, leave the Original Location radio
button (default) selected, and click Next.
2. In Recovery Options screen of the wizard, in the Transport mode section, clear the
check boxes for san, hotadd, and nbdssl options.
̶ NetBackup Recovery Host: Your master server, winmaster.example.com or

̶ Media Server: (Default)
̶ Transport modes: nbd: Do not encrypt the virtual disk data for over-the-network
transfers.

Lab 11-32

4. In Virtual Machine Options screen, make the following selections:
Virtual Machine Options:
̶ Restore BIOS UUID…. Instead of creating a new UUID.

̶ Overwrite the existing virtual machine
̶ Retain original hardware versions (default setting)
Format of restored virtual disks:
̶ Original Provisioning (default setting)

̶ Restores each disk to its original provisioning at the time of backup.
6. When the Perform Recovery screen of the wizard is displayed, click the Run Pre-
Recovery Check button to run the mandatory pre-recovery check.
Lab 11-33

7. Verify that the pre-recovery checks run successfully to completion, and that no
errors are posted, before continuing.
If pre-recovery check errors are encountered, take note of the errors and notify
your instructor.
8. Click the Start Recovery button to start the virtual machine recovery operation.
9. When the View Progress dialog box is displayed, click Yes to view the progress of
the virtual machine recovery operation in the Task Progress tab.
10. Monitor the most recent Restore operation and verify the job completes
successfully.
Mark the checkbox for Full Contents, if not already selected.
You may also view the virtual machine recovery operation using the NetBackup
Activity Monitor.
11. Minimize the NetBackup Administration Console window.
Continue to Exercise C-4: Verifying the VM recovery using the VMware vSphere Web
Client.
Lab 11-34

Exercise C-4: Verifying the VM recovery using the
VMware vSphere Web Client
In the following steps you, verify the virtual machine, lnxvm2, is restored.
1. Access the open VMware vSphere Web Client window on console.example.com.
2. From the Home tab click Hosts and Clusters in the vSphere Web Client window.
3. Click the Refresh icon located in the blue banner bar to update the vSphere Web
Client user interface.
4. Verify that the lnxvm2 virtual machine has been recovered to the
esx2.example.com ESX server.
5. Allow the vSphere Web Client window to remain open on console.example.com.

Continue to Exercise D: Performing non-NetBackup pre-requisite tasks for IRV.
Lab 11-35

Exercise D: Performing non-NetBackup pre-requisite
tasks for IRV (Required, but pre-done)
There are a number of 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 in order to save time in
the lab. 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.
Continue to Exercise D-1: Summary of non-NetBackup requirements for IRV.

Lab 11-36

Exercise D-1: Summary of non-NetBackup requirements
for IRV
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.example.com system.

• Installing Java on the console.example.com system.
• Adding the Network File System (NFS) role on the Windows-based NetBackup
master server, winmaster.example.com. (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.example.com)
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 E: Performing
NetBackup pre-requisite tasks for IRV on the next page.
• Click the link to view the steps in Exercise X: Detailed non-NetBackup prerequisite
steps to enable Instant Recovery for VMware (IRV).
Lab 11-37

Exercise E: Performing NetBackup pre-requisite
tasks for IRV
Summary of NetBackup pre-requisite tasks for IRV
There are several NetBackup-related tasks that must be performed to enable the
Instant Recovery for VMware (IRV) feature, using the NetBackup plugin for the vSphere
Web Client user interface.
These tasks and the instructions for performing each task are found in the following
exercises:
• Exercise E-1: Verifying the vSphere Web Client plugin installation and registration
(the plugin was installed in Lab 10).
• Exercise E-2: Creating security certificates for NetBackup master server – Windows
• Exercise E-3: Creating security certificates for NetBackup master server - Linux
• Exercise E-4: Registering the NetBackup master server (or servers) with the vCenter
Server to enable Instant Recovery for VMware (IRV) operations.
Each of the tasks listed above is a required task to enable the NetBackup
Instant Recovery for VMware feature. Do not skip any of these steps.
Continue to the next page to begin the steps to perform the pre-requisite NetBackup
tasks to enable Instant Recovery for VMware (IRV). The first task is: Exercise E-1:
Verifying the vSphere Web Client plugin installation and registration.
Lab 11-38

Exercise E-1: Verifying the vSphere Web Client plug-in
installation and registration
In this task, you view the vSphere Web Client UI that is connected to the vCenter
Server, vcenter1.example.com, to verify the installation and registration of the
NetBackup vSphere Web Client plug-in.
1. Access the open VMware vSphere Web Client window on console.example.com.
User name: vsphere.local\Administrator
Password: Tra1n!ng
2. Click the Home icon in the blue title bar of the VMware vSphere Web Client, and
then click the Home entry in the menu.

Lab 11-39

3. Verify the presence of the Veritas NetBackup entry in the Navigator (left) pane of
the vSphere Web Client window, and in the Home tab (right pane) of the window.
The Veritas NetBackup entries are only present in the vSphere Web Client user
interface when the NetBackup plugin has been successfully installed and
registered.
If the Veritas NetBackup entries are not present in the vSphere Web Client
window, please refer to Lab 10: Exercise C: installing the NetBackup Plug-in
for VMware vSphere Web Client.
4. Click the link to continue to the next exercise, depending upon the Operating System
of your preferred master server:
̶ If your preferred master server is winmaster.example.com continue to: Exercise

E-2: Creating security certificates for a NetBackup master server (winmaster).
̶ If your preferred master is lnxmaster.example.com continue to: Exercise E-3:
Creating security certificates for a NetBackup master server – (lnxmaster).
Lab 11-40

Exercise E-2: Creating security certificates for a
NetBackup master server (winmaster)
To enable a NetBackup master server to access the vCenter Server (10.10.2.65, in this
lab environment) and to use the NetBackup plugin for the vSphere Web Client to
perform Instant Recovery for VMware (IRV) operations, it is necessary to create a
security certificate for each master server that will access the vCenter Server, and then
to register the master server with the vCenter Server (by providing the security
certificate).
In the steps that follow, you perform the steps necessary to create a security certificate
for your NetBackup master server.
• To create a security certificate for lnxmaster.example.com click the link to go to

Exercise E-3: Creating security certificates for a NetBackup master server
(lnxmaster).
• To create a security certificate for winmaster.example.com, continue to the steps
below.
Complete the steps below to create a security certificate for the Windows-based
NetBackup master server, winmaster.example.com.
1. Access the desktop of winmaster.example.com.
2. Log in to winmaster.example.com using the credentials described above.

These steps must be performed on the winmaster.example.com system. Verify

that you are accessing the desktop of that system.
3. Double-click the Command Prompt shortcut on the desktop of

winmaster.example.com to open a Command Prompt window.
4. In the Command Prompt window, change directory to C:\Program

Files\Veritas\NetBackup\wmc\bin\install
Command: cd C:\Pro*\Ve*\Net*\wmc\bin\install
Lab 11-41

5. In the Command Prompt window, execute the manageClientCerts command using
the syntax below, to list any existing security certificates.
Command: manageClientCerts -list
There should be no certificates present on winmaster.example.com.
6. In the Command Prompt window, execute the manageClientCerts command, using

the syntax below, to create a new security certificate for the vCenter Server,
10.10.2.65.
Command: manageClientCerts –create 10.10.2.65
In this lab environment you use the IP address, 10.10.2.65, of the vCenter
Server system, VCENTER2, when creating the security certificate. This is
important, because 10.10.2.65 is the name that was used when this vCenter
Server was installed.
7. Take note of four important pieces of information provided in the

“manageClientCerts –create” command output:
̶ The certificate was successfully created

̶ The name of the master server associated with the certificate:
̶ The folder location of the certificate file:
C:\Program Files\Veritas\NetBackup\var\global\wsl\credentials\clients
̶ The file name of the certificate file: 10.10.2.65.zip
Lab 11-42

the syntax below, to list any existing security certificates.
Command: manageClientCerts –list
The output of the manageClientCerts command provides the expiration date of

the new certificate (one year from the date of the security certificate creation).

the syntax below, to add 2 aliases, vcenter2 and vcenter2.example.com, for the
vCenter Server, 10.10.2.65.
Command: manageClientCerts –addAlias 10.10.2.65 –HOST

vcenter2
Command: manageClientCerts –addAlias 10.10.2.65 –HOST

vcenter2.example.com
The vcenter2 and vcenter2.example.com aliases are added in the lab

environment because the IP address was used as the vCenter Server’s host
name during the installation.
the syntax below, to list the newly created aliases.
Command: manageClientCerts –listAliases 10.10.2.65
Lab 11-43

11. View the output of the manageClientCerts command and verify that vcenter2
and vcenter2.example.com have been set as aliases for the vCenter server,
10.10.2.65.
12. On the desktop of winmaster.example.com, double-click the File Explorer shortcut

to open a File Explorer window.
13. In the File Explorer window, navigate to C:\Program

Files\Veritas\NetBackup\var\global\wsl\credentials\clients.
14. Right-click on the 10.10.2.65.zip file, and select Copy from the menu.
15. Click the Run icon in the Windows’ task bar on desktop of winmaster.example.com.
16. In the Open field, type \\vcenter2\winmaster-token, and then click OK.
Lab 11-44

17. In the new File Explorer window, right-click in the white space of the right window
pane, then click Paste in the menu.
The security certificate file, 10.10.2.65.zip, that was previously created on

winmaster.example.com should now be present in the folder on
vcenter2.example.com.
18. Close the Command Prompt and File Explorer windows on

Continue to Exercise E-4: Registering the master server with the vCenter Server.
Lab 11-45

Exercise E-3: Creating security certificates for a
NetBackup master server (lnxmaster)
To enable a NetBackup master server to access the vCenter Server (10.10.2.65, in this
lab environment) and to use the NetBackup plugin for the vSphere Web Client to
perform Instant Recovery for VMware (IRV) operations, it is necessary to create a
security certificate for each master server that will access the vCenter Server, and then
to register the master server with the vCenter Server (by providing the security
certificate).
In the steps that follow, you perform the steps necessary to create a security certificate
for your NetBackup master server.
• To create a security certificate for winmaster.example.com click this link to go to

Exercise E-2: Creating security certificates for a NetBackup master server
(winmaster).
• To create a security certificate for lnxmaster.example.com continue to the steps
below.
console.example.com User ID: EXAMPLE\Administrator Password: train
2. Open a PuTTY connection from console.example.com to lnxmaster.example.com.
a. Double-click on the REMOTE SYSTEM ACCESS folder on the desktop of

b. Double-click the Putty shortcut to open the PuTTY Configuration window.

c. In the PuTTY Configuration window, double-click the lnxmaster.example.com
entry in the Saved Sessions pane.
d. From the Saved Sessions section, double-click the entry for
lnxmaster.example.com to initiate an SSH session to the system.
Lab 11-46

3. Log into lnxmaster.example.com using the following credentials:
̶ User name: root

̶ Password: train.
You may want to adjust the size of the PuTTY window to fit your screen.
4. In the PuTTY window, change directory to /usr/openv/wmc/bin/install.
Command: cd /usr/openv/wmc/bin/install
5. Execute the manageClientCerts command using the syntax below, to list any
existing security certificates.
Command: ./manageClientCerts -list
No certificates should currently be present on lnxmaster.example.com.
6. Execute the manageClientCerts command, using the syntax below, to create a new
security certificate for the vCenter Server, 10.10.2.65.
Command: ./manageClientCerts –create 10.10.2.65

In this lab environment you use the IP address, 10.10.2.65, of the vCenter
Server system, VCENTER2, when creating the security certificate. This is
important, because 10.10.2.65 is the name that was used when this vCenter
Server was installed.
Lab 11-47

7. Take note of four important pieces of information provided in the
“manageClientCerts –create” command output:
̶ The certificate was successfully created

̶ The name of the master server associated with the certificate:
̶ The folder location of the certificate file:
/usr/openv/var/global/wsl/credentials/clients
̶ The file name of the certificate file: 10.10.2.65.zip
8. Execute the manageClientCerts command using the syntax below, to list any
existing security certificates.
Command: ./manageClientCerts –list
The output of the manageClientCerts command provides the expiration date of

the new certificate (one year from the date of the security certificate creation).
9. Execute the manageClientCerts command two times, using the syntax shown below,
to add two aliases for the vCenter Server, one for vcenter2 and another for
Command: ./manageClientCerts –addAlias 10.10.2.65 –HOST

vcenter2
Command: ./manageClientCerts –addAlias 10.10.2.65 –HOST

vcenter2.example.com
Lab 11-48

The vcenter2 and vcenter2.example.com aliases are added in the lab
environment because the IP address was used as the vCenter Server’s host
name during the installation.
10. Execute the manageClientCerts command using the syntax below, to list the aliases
for the vCenter Server, 10.10.2.65.
Command: ./manageClientCerts –listAliases 10.10.2.65
11. View the output of the manageClientCerts command and verify that vcenter2
and vcenter2.example.com have been set as aliases for the vCenter server,
10.10.2.65.
12. Execute the following command to change directory to the location of the
10.10.2.65.zip certificate.
Command: cd /usr/openv/var/global/wsl/credentials/clients
13. Execute the following command to list the contents of the clients directory.
Command: ls -l
Lab 11-49

14. Execute the following command to copy the 10.10.2.65.zip certificate file to the
vCenter Server, vcenter2.
Command: cp 10.10.2.65.zip /mnt/tokens
The /mnt/tokens directory on lnxmaster.example.com is a mounted

filesystem to the shared lnxmaster-token folder on the desktop of vcenter2.
Copying the zip file to /mnt/tokens has the result of copying the file to the
vCenter Server, vcenter2.
15. Minimize the PuTTY window to lnxmaster.example.com.
16. In the Remote System Access window on console.example.com, double-click on the

RDP Profiles (Windows systems) folder.
17. Double-click the vcenter2.rdp to open a remote session from console.example.com

to vcenter2.example.com.
18. In the Windows Security window that is displayed, verify the logon account is set to
EXAMPLE\Administrator and, in the Password field, type train. Then click OK.
19. On the desktop of vcenter2, locate and double-click the lnxmaster-token folder.
20. Verify the certificate file, 10.10.2.65.zip, is present in this folder.

Continue to Exercise E-4: Registering the master server with the vCenter Server.
Lab 11-50

Exercise E-4: Registering the master server with the
vCenter Server
In the steps that follow, you perform the steps necessary to register the NetBackup
master server or master servers with the vCenter Server, vcenter2. These steps are
necessary to enable the master server to perform Instant Recovery for VMware (IRV)
operations.
To register either the Windows-based master server, winmaster.example.com, or the

Linux-based master server, lnxmaster.example.com, with the vCenter Server, vcenter2,
continue with the steps below.
1. If necessary, log into and access the desktop of the vcenter2.example.com system.
vcenter2.example.com User ID: Example\Administrator Password: train
You perform these steps on vcenter2 because the security certificate files are
present locally (and can be browsed for) on this system. Verify that you are
accessing the desktop of vcenter2.example.com before continuing.
3. Log in to the vSphere Web Client.
• Username: vsphere.local\Administrator
• Password: Tra1n!ng
Lab 11-51

4. When the vSphere Web Client is displayed, click the Home button, located at the
top of the user interface, and then click the Home entry in the menu.
5. From the Home screen of the vSphere Web Client click the entry for Veritas
NetBackup.
6. From the Veritas NetBackup screen, click Register Master Servers.
Lab 11-52

7. From the Add NetBackup Master Servers window enter the name of your master
server either, winmaster.example.com or lnxmaster.example.com.
̶ If you are performing this lab using the Windows-based master server,
winmaster.example.com, type the name of that server in the NetBackup Master
Server field: winmaster.example.com.
̶ If you are performing this lab using the Linux-based master server,
lnxmaster.example.com, type the name of that server in the NetBackup Master
Server field: lnxmaster.example.com.
Leave the Port for the NetBackup Web Services setting at the default, port
8443.
8. Click the Browse button for the Upload Authentication Token field, to browse for
the security token.
Lab 11-53

9. When the Select file to upload by vcenter2.example.com window is displayed,
navigate to the appropriate path depending on the OS of your master server.
̶ If you are performing this lab using the Windows-based master server,
winmaster.example.com, browse to the folder: Desktop\winmaster-token.
̶ If you are performing this lab using the Linux-based master server,
lnxmaster.example.com, browse to the folder: Desktop\lnxmaster-token.
10. Click the certificate file, 10.10.2.65.zip, to select the file for upload, and then click
Open.
After selecting the security token zip file (10.10.2.65.zip) for upload (to the vCenter
Server), you are returned to the Add NetBackup Master Server window.
Lab 11-54

11. Click the Add Server button.
12. Verify that the dialog box containing the “Successfully added NetBackup master
server, xxxmaster.example.com” is displayed.
The master server name displayed will vary, depending upon the master server
name that you entered.
The example shown in the screen shot above shows that the NetBackup Master
Server, winmaster.example.com, was added. If you are using the Linux master
server, you should expect to see the “Successfully added NetBackup master
server, lnxmaster.example.com” message, as illustrated below.
13. Click the OK button to close the “success” dialog window.
Lab 11-55

14. From the Validate/Remove NetBackup Master Server section of the window, click
the drop-down menu and select the hostname of your master server.
15. Click the Validate button.
You can select the entry for a master server from the drop-down menu in the
Validate/Remove NetBackup Master Server section of the window, and click
the Validate button to validate the registration of the master server, or you can
click the Remove button to unregister the master server. If you unregister a
master server, that master server will be unable to perform instant recovery of
VMware virtual machines.
16. Verify your master server has been successfully validated, then click OK.
17. Click the X in the upper right corner to close the Add NetBackup Master Servers
window.
18. Close the RDP window to vcenter2.example.com.
19. Close all open windows on console.example.com - except to the vSphere Web
Client.
You will use the vSphere Web Client window in the next exercise.
Continue to the Exercise F: Performing Instant Recovery for VMware (IRV) using the
vSphere Web Client.
Lab 11-56

Exercise F: Performing Instant Recovery for VMware
(IRV) 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.example.com virtual
machine server.
Continue to Exercise F-1: Deleting the lnxvm2 VM from the ESX Server.
Lab 11-57

Exercise F-1: Deleting the lnxvm2 VM from the ESX Server
In the steps that follow, you delete the lnxvm2 virtual machine from the ESX Server in
preparation for recovering it using the NetBackup Instant Recovery for VMware feature.
2. Access the open vSphere Web Client window on console.example.com.
If a vSphere Web Client window is not open, open a new window using the
shortcut on the desktop of console.example.com, and log in to the
vcenter2.example.com vCenter server.
3. Click the Home icon in the blue banner bar then Hosts and Clusters.
4. Select the entry for the lnxvm2 virtual machine, located in the left pane of the
vSphere Web Client window.
5. In the right pane select the Related Objects tab then select Datastores.
6. Take note of the name of the Datastore, INT_ESX2_DS1, that lnxvm2 is currently
located on.
Lab 11-58

7. Delete the virtual machine lnxvm2 by right-clicking on lnxvm2 and selecting the
Delete from Disk entry in the menu.
VMware only allows the deletion of virtual machines that are powered off.
8. When the Confirm Delete dialog box is displayed, click Yes to confirm the delete
operation.
Lab 11-59

9. Verify that the entry for the lnxvm2 virtual machine no longer exists in the left pane
of the VMware vSphere Web Client window.
It may be necessary to refresh the contents of the vSphere Web Client window
to see that the lnxvm2 VM has been deleted. Click the Refresh icon in the blue
banner bar of the vSphere Web Client window to update the window contents.
Continue to Exercise F-2: Using Instant Recovery for VMware (IRV) to recover a VM.
Lab 11-60

Exercise F-2: 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, completing the recovery of the virtual machine.
2. Access the open vSphere Web Client window on console.example.com.
If a vSphere Web Client window is not open, open a new window using the
shortcut on the desktop of console.example.com, and log in to the
vcenter2.example.com vCenter server using the User name,
vsphere.local\Administrator and the password Tra1n!ng
3. Access the Home tab of the vSphere Web Client, and the click the Veritas
NetBackup icon, located under the Administration pane.
4. When the Veritas NetBackup pane is displayed, click the Instant Recovery Wizard
entry.
Lab 11-61

5. From the Instant Recovery Wizard verify the vCenter Server field displays the entry,
10.10.2.65.
6. Verify the NetBackup Master Server field shows the name of your master server,
either winmaster.example.com or lnxmaster.example.com.
7. In the search field, type lnxvm2 and click the Search button to search for the VM.
The search results are displayed. The lnxvm2 host should be visible in the Search
Results.
8. Click the entry for lnxvm2 in the search results and click the Add Virtual Machines
button.
The Add Virtual Machines button is located in the lower right corner of the Instant
Recovery Wizard screen.
9. Note in the Virtual Machines Added pane at the top of the window that the count
of added virtual machines has increased to 1.
10. Click the View Details link to see the details about the added virtual machine, and
then click the Close button to close the details page.
Lab 11-62

11. Click Next to continue
The Image selection page opens.
12. Review the details about the selected backup image.
Note that NetBackup has selected the most recent full backup image of the virtual
machine, by default.
13. Click the Change link in the Date and Time of Backup column.
14. If you receive a message about no images are available for the instant recovery
during the selected time period, click OK.
The Search Images window opens.
15. From the top of the Search Images window, click the Select Date Range option.
16. In the Start Date field enter 12/01/2017 then select the Search Images button.
Lab 11-63

17. Select the backup image from Monday, December 11, 2017 then click the Select
Image button.
18. From the Images Available for Instant Recovery screen verify the Date and Time of
Backup is Monday, December 11, 2017.
19. Click Next.
The Destination Selection page is displayed.
20. Verify that 10.10.2.65 appears in the vCenter Server: field.

21. Click the Select button next to the Data center/ESX Server.
The ESX Server Selection window opens.
22. Expand the DC1 datacenter, select esx2.example.com and click the Select ESX
Server button.
The ESX Server Selection window closes.
Lab 11-64

23. Click the Select button next to the Temporary Datastore or Datastore Cluster.
24. Select INT_ESX2_DS2 and click the Select Datastore/Datastore Cluster button.
25. Verify the following selections on the Instant Recovery Destination screen:
̶ vCenter Server: 10.10.2.65

̶ Data center/ESX Server: /DC1/esx2.example.com
̶ Temporary Datastore or Datastore Cluster: INT_ESX2_DS2
You are restoring lnxvm2 virtual host to a temporary datastore, INT_ESX2_DS2.

This is not the original datastore that lnxvm2 was on prior to deletion.
26. Click the Next button on the Instant Recovery Destination screen to continue.
The Virtual Machine Options page opens.
27. Make the following selections on the Virtual Machine Options page:
̶ Display Name: lnxvm2

̶ Retain networks: Selected (checked)
̶ Power On: Not selected (un-checked)
̶ Retain tag associations: Not selected (un-checked)
̶ Retain hardware version: Selected (checked)
28. Click the Next button on the Virtual Machine Options page to continue.
The Review Selections page opens.
Lab 11-65

29. Click the Run Pre-recovery check button and monitor the status of the pre-recovery
check.
The check should complete successfully.
You may click the Show More Details link in the pre-recovery check pane to
see additional details about the pre-recovery check results.
30. Click the Finish button to initiate the instant recovery of lnxvm2.
The Instant Recovery Jobs Initiated dialog box is displayed.
See the Note on the Instant Recovery Jobs Initiated dialog box that warns that
the Instant Recovery operation fails if the NFS services are not enabled on the
NetBackup media server/recovery host. This task (enabling NFS) was pre-
performed in this lab environment for your convenience (and is documented in
Exercise D-1: Summary of non-NetBackup requirements for IRV.
31. Click OK to close the Instant Recovery Jobs Initiated window.
Note that it may take a few minutes for the OK button to appear.
Continue to Exercise F-3: Viewing the Instant Recovery jobs.
Lab 11-66

Exercise F-3: 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.
console.example.com UserID: EXAMPLE\Administrator password: train
2. Access and log into the NetBackup Administration Console window on

console.example.com that is connected to your master.
3. Select the Activity Monitor entry from the left pane.
Two jobs have been created as a result of the Instant Recovery.
4. Monitor the jobs until the Activate Instant Recovery job is completed successfully.
The recovered virtual machine (lnxvm2, in this case) is ready for use as soon as the
Activate Instant Recovery job is done. Note that the VM Instant Recovery job
remains in the Active state until a deactivation or completion request is received.
5. Access the open vSphere Web Client window on console.example.com, and click
the Home button.
6. Click the Hosts and Clusters button.
7. Click the Refresh button in the blue banner bar.
8. In the left pane, expand the tree to show the entries under esx2.example.com.
The lnxvm2 virtual machine is now visible.
Lab 11-67

9. Click the entry for lnxvm2 in the left pane and then click the Summary tab.
Details about the lnxvm2 VM are displayed. Note that the VM is powered off,
due to the options selected in the Instant Recovery wizard.
10. Click the Related Objects tab, and then click Datastores, to locate the temporary
datastore to which the lnxvm2 VM was restored.
Continue to Exercise F-4: Using VMware vMotion to migrate the recovered VM to

another datastore on the ESX Server.
Lab 11-68

Exercise F-4: Using VMware vMotion to migrate the
recovered VM to another datastore on the ESX Server
In this the steps that follow, you use VMware vMotion to migrate the virtual machine,
lnxvm2, from the temporary datastore to a production datastore on the ESX Server,
esx2.example.com.
1. From console.example.com, access the open vSphere Web Client window
2. Click lnxvm2 in the left pane and click the Summary tab in the right pane.
Details about the lnxvm2 VM are displayed. Note that the VM is powered off, due to
the options selected in the Instant Recovery wizard. Also note the storage that
lnxvm2 is using.
3. Right-click the entry for lnxvm2 and, in the menu, click Migrate.
Lab 11-69

4. When the lnxvm2 – Migrate window is displayed, click the Change storage only
radio button, to move the virtual machine’s storage to another datastore.
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
(winmaster.example.com or lnxmaster.example.com). This operation moves
the virtual machine to a production datastore on the ESX Server.
6. From the Select storage screen, select the INT_ESX2_DS1 datastore.

When you select the datastore, VMware checks the compatibility of the virtual
machine to the new datastore.
7. When the compatibility checks complete successfully, click Next to continue.
The lnxvm2 – Migrate screen displays the Review Selections screen.
Lab 11-70

8. Review the summary in the lnxvm2 – Migrate screen, and then click Finish.
9. If a Virtual machine Consolidation message is displayed for lnxvm2, click the

Acknowledge link in the Summary tab.
10. Right-click on lnxvm2 and select Snapshots then Consolidate.

11. Click Yes to confirm the Disk Consolidation.
12. Click the Refresh icon in the blue banner bar to refresh the screen.
Lab 11-71

13. Verify lnxvm2 no longer has a disk consolidation warning message associated with
the virtual host.
14. Monitor the migration of the virtual machine, as displayed in the Recent Tasks pane
(bottom of vSphere Web Client window), until the operation is completed.
The virtual machine migration (relocation) to the new datastore may take a
few minutes to complete.
15. From the left Navigator pane make sure lnxvm2 is selected then click the Related
Objects tab.
16. Click Datastores and verify the lnxvm2 is now on the original datastore,
INT_ESX2_DS1.
Continue to Exercise F-5: Ending the Instant Recovery for VMware session.
Lab 11-72

Exercise F-5: 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.
1. Access the vSphere Web Client from console.example.com.
2. Click the Home icon then select Veritas NetBackup.
3. Click the Instant Recovery Cleanup icon.
The Instant Recovery Cleanup window opens.
4. Click the entry for lnxvm2 in the Instant Recovery Cleanup window.
A Veritas NetBackup window is displayed.

The Active instant Recovery Virtual Machines count is “1”.
5. Click the Initiate Instant Recovery Done link.
Lab 11-73

6. Click the Yes button to complete the Instant Recovery Cleanup operation and close
the window.
Another Veritas NetBackup window is displayed.
7. Click OK to return to the Instant Recovery Cleanup window.
8. Wait a few moments, and then click the Refresh button on the Instant Recovery
Cleanup window.
The table in the Instant Recovery Cleanup window should now be empty – as the
entry for the lnxvm2 virtual machine has been removed.
The Active instant Recovery Virtual Machines count should now be 0. If it is not,
wait another minute and then click Refresh again.
9. Click the Close button to close the Instant Recovery Cleanup window.
10. Close the vSphere Web Client window on console.example.com.
Continue to Exercise F-6: Verifying the end of the Instant Recovery jobs.
Lab 11-74

Exercise F-6: 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.
1. Access the open the NetBackup Administration Console window on

2. Select Activity Monitor entry in the left pane, if necessary.
3. Note that a Stop Instant Recovery job is displayed and is in the Done state, and that
the Activate Instant Recovery and VM Instant Recovery jobs, created earlier, have
completed successfully.
4. Close all open windows on console.example.com.
You have completed all intended tasks for this lab activity.
11 – Required Exercises
You have completed all steps for this lab activity.
Lab 11-75

Lab 11: Recovering Virtual Machines – detailed
procedures
This section of the lab contains the detailed steps used to perform operations in
NetBackup.
This section is accessed only by following hyperlinks from the main section of the lab.
Lab 11-76

Exercise X: Detailed non-NetBackup prerequisite steps to
enable Instant Recovery for VMware (IRV)
The detailed procedures provided on this and the following pages 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 document 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.example.com system.

• Installing Java on the console.example.com system.
• Installing the Network File System (NFS) role on the Windows-based NetBackup
master server, winmaster.example.com.
• Enabling vMotion on the ESX Server (esx1.example.com)
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 E: Performing NetBackup prerequisite tasks for IRV.
Continue to the steps below to view the detailed non-NetBackup prerequisite

procedures.
Lab 11-77

Exercise X-1: Adding the Web Server (IIS) role on
console.example.com
These steps have been pre-performed on the console.example.com system in this lab
environment. There is no requirement for you to perform the steps. The procedure is
provided below for your reference only.
The steps that follow document the installation of the Web Server (IIS) role on the
2. Log in to console.example.com (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. When the Server Manager window is opened, click Add roles and features.
Lab 11-78
6. In the Before you begin screen, click Next.
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.example.com is listed in the Server

Pool pane.
Lab 11-79
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.
Lab 11-80
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.
Lab 11-81
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.
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.example.com.
You have completed the installation of the Web Server (IIS) role on
Lab 11-82
Continue to the Install JAVA on console.example.com 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.
Lab 11-83
Exercise X-2: Installing Java on console.example.com
These steps have been pre-performed on the console.example.com system in this lab
environment. There is no requirement for you to perform the steps. The procedure is
provided below for your reference only.
The steps that follow document the installation of JAVA on the console.example.com
system. JAVA is required to enable the registration of the NetBackup plugin for the
vSphere Web Client.
Downloading JAVA
3. Double-click the Mozilla Firefox icon, located on the desktop, to open a Firefox
browser window.
4. Click the + to open a new tab in the Firefox Web browser.
5. When the Firefox Web browser window is opened, in the address bar, type:
https://java.com/en/download, and press Enter.
Important: For your convenience, the JAVA installation file has been previously
downloaded, and is present in the C:\Downloads folder on console.example.com.
The filename is jxpiinstall.exe.
If the Java installation file had not been previously downloaded and saved, you
would proceed with the download of the Java installation file. For now,
proceed to the next step.
Lab 11-84
6. Open a File Explorer window on console.example.com.
7. In the File Explorer window, navigate to C:\Downloads.
8. Locate and double-click the jxpiinstall.exe file, to initiate the installation of JAVA on
9. When the Open File – Security Warning dialog box is displayed, click the Run
button.
10. De-select any promotional offers to install additional software that may be
presented by the Java installer.
11. When the Java Setup – Welcome dialog box is displayed, click the Install button.
Lab 11-85
12. When the Java Setup dialog box is displayed, click the “Do not update browser
settings” radio button and click the Next button.
13. Monitor the installation of Java in the Status bar of the Java Setup – Progress dialog
box.
Lab 11-86
14. When the installation of Java has been completed, the Java Setup – Complete dialog
box is displayed.
15. Click the Close button in the Java Setup – Complete dialog box.
A Web browser window that enables you to “Verify Java version” may be
displayed. Close the Web browser window without making any selections (File
> Exit).
Lab 11-87
16. Close any open Firefox Web browser windows on console.example.com (File > Exit).
17. Close any open File Explorer windows on console.example.com.
You have completed the installation of Java on console.example.com.
Disabling JAVA updates on console.example.com

For purposes of this environment we have performed the steps documented below to
disable automatic updates to Java on console.example.com. There is no need for you to
perform these steps. The steps are documented here for your reference only.
20. Click the Windows button , located on the left end of the Windows’ task bar.
21. Click the downward arrow to access the Applications screen.
22. From the Apps screen, click Configure Java.
Lab 11-88
23. When the Java Control Panel is displayed, click the Update tab.
24. On the Java Control Panel window, uncheck (to deselect) the Check for Updates
Automatically check box (to disable automatic updates of Java).
When you uncheck the checkbox, the Java Update – Warning dialog box is
displayed
25. Click the Do Not Check button in the Java Update – Warning dialog box.
In this environment, we have de-selected checking for automatic updates of

Java. This is generally not recommended in production environments.
26. Click the Apply button to apply the Java configuration changes.
27. Click OK to close the Java Control Panel window.
Continue to the Installing NFS on winmaster.example.com 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.
Lab 11-89
Exercise X-3: Installing NFS on winmaster.example.com
These steps have been pre-performed on the Windows-based NetBackup master server,
winmaster.example.com system in this lab environment. There is no requirement for
you to perform the steps. The procedure is provided below for your reference only.
The steps that follow document the installation of the Network File System (NFS) role
on the winmaster.example.com system – which is a NetBackup master/media server in
this lab environment. NFS is required on any NetBackup server system that is used as
the recovery host in Instant Recovery for VMware (IRV) operations. For example, if the
media server, winmedia.example.com, were to be used as the recovery host for IRV
operations, this procedure would have to be performed on that system.
1. Log in and access the desktop of winmaster.example.com.
2. Click the Windows icon located at the left end of the Windows’ task bar.
3. When the tiles are displayed on the desktop, click the Server Manager.
4. In the Server Manager window, click Add roles and features.
An informational window may appear stating that Windows is still collecting

information. If this happens, click OK to dismiss the window, wait a minute for
more information to load, and then repeat step 5 above.
Lab 11-90
5. When the Add Roles and Features Wizard displays the Before you Begin screen,
click Next to continue.
6. When the Select installation type screen is displayed, verify the Role-based or
feature-based installation radio button is selected then click Next.
7. When the Select destination server screen is displayed, verify that the Select a
server from the server pool radio button is selected, and the entry for
winmaster.example.com in the Server Pool pane is highlighted.
Lab 11-91
9. When the Select server roles screen of the wizard is displayed, click the arrow to
expand the entry for File and Storage Services (x of 12 installed), then File and iSCSI
Services.
10. Scroll down to locate and click the check box for Server for NFS.
When you select the Server for NFS check box, an Add Roles and Features
Wizard window is displayed, indicating the need for other features that are
required to support the Server for NFS feature.
Lab 11-92
11. Click the Add Features button in the Add Roles and Features Wizard window, while
making no additional changes to the window contents.
12. The Server for NFS check box is now selected, click the Next button.
13. On the Select features screen, locate and click the check box for Client for NFS.
15. When the Confirm installation selections screen is displayed, click the Install button
to start the installation of the selected features.
Lab 11-93
16. Observe the progress of the installation in the Installation progress window.
The installation process may take a few minutes to complete.
A restart of winmaster.example.com may be necessary to finish the

installation.
17. Click Close to close the Add Roles and Features Wizard window.
18. Close the Server Manager window on winmaster.example.com.
You have completed the installation of the NFS role on winmaster.example.com.
19. Restart winmaster.example.com if you were instructed to do so to complete the

installation of Server for NFS and Client for NFS.
Click the link to continue to the Enabling vMotion on the ESX Server
(esx1.example.com) 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.
Lab 11-94
Exercise X-4: Enabling vMotion on the ESX Server
(esx1.example.com)
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.example.com,
system in this lab environment. There is no requirement for you to perform the steps.
The procedure is provided below for your reference only.
console.example.com, 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, Tra1n!ng, and click
Login.
Lab 11-95
5. When the vSphere Web Client user interface is displayed, click the Home icon
located in the blue banner bar.
6. Click Hosts and Clusters in the VMware vSphere Web Client window.
7. In the left pane, expand the DC1 (data center) entry then select esx2.example.com.
8. Select the Manage tab and then Networking tab.
9. Click the VMkernel adapters entry.
10. Click the entry for the vmk0 device then click the Edit Settings icon (the pencil icon).
Lab 11-96
11. In the resulting vmk0 – Edit Settings window, in the Available services settings, click
to mark the check box for the vMotion traffic parameter.
12. 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.example.com.
You use this window in the next section of this lab activity.
14. 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.
11 – Detailed steps
You have completed all steps for this lab activity.
Lab 11-97
Lab 12: Duplicating Backups
In this lab, you configure and use a NetBackup Storage Lifecycle Policy to manage
NetBackup backup jobs and backup image duplication activities.
Proceed to Exercise A: Configuring a Storage Lifecycle Policy.
Lab 12-1
Exercise A: Configuring a Storage Lifecycle Policy
In this exercise, you configure a Storage Lifecycle Policy (SLP) that performs the
following operations:
• Writes a backup image to NetBackup MSDP storage.

• Writes a second backup image to AdvancedDisk storage.
• Uses the second backup image as the source image to create a duplicate copy of the
image on tape
Continue to Exercise A-1: Configuring a Storage Lifecycle Policy.
Lab 12-2
Exercise A-1: Configuring a Storage Lifecycle Policy
In the following steps, 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 tape, and
are then deleted.
̶ A duplication of the second backup image to tape storage. The copies of the
backup images that are written to tape are retained for three (3) months.
2. If necessary, log on to the console.example.com system using the credentials

provided above.


NetBackup 8.1 Administration Console shortcut, located on the desktop of the
system, to launch the NetBackup Administration Console. Then, enter the Host
name, User name, and Password in the Administration Console login screen to
connect to your master server. See the table below.

Continue to Exercise A-2: Creating a Storage Lifecycle Policy.
Lab 12-3
Exercise A-2: Creating a Storage Lifecycle Policy
In this lab exercise, you will create a Storage Lifecycle policy.
1. Select NetBackup Management and then select Storage, Storage Lifecycle Policies
in the left pane of the Administration Console.
The list of currently configured Storage Lifecycle Policies is displayed in the right
No Storage Lifecycle Policies are currently configured.
2. Select Actions and from the resulting menu, select New, and then Storage Lifecycle
Policy.
Actions > New > Storage Lifecycle Policy
The New Storage Lifecycle Policy window is displayed.
3. Enter the information provided in the table below in the New Storage Lifecycle
Policy window.
Storage Lifecycle Policy Parameter Value

Storage lifecycle policy name LAB12_SLP1_test
Data classification <no data classification>
Priority for secondary operations 0 (default)
State of secondary operation processing Active (default)
Continue to Exercise A-3: Adding the first operation to the SLP.
Lab 12-4
Exercise A-3: Adding the first operation to the SLP
In this exercise, you will add the properties for the first operation to be performed by
the new Storage Lifecycle Policy.
1. Click the Add button to add the first operation to the SLP.
The New Operation window is displayed.
2. Enter the information provided in the table below to complete the configuration of
the first storage operation for the SLP.
New Operation properties Value

Storage source --- (Default setting)
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)
3. Click OK to save the New Operation window parameter settings.
Verify that the Backup operation entry is added to the Operation list of the
LAB12_SLP1_test Storage Lifecycle Policy.
4. Click OK to save the LAB12_SLP1_test storage lifecycle policy.
Verify that an entry for the LAB12_SLP1_test storage lifecycle policy is displayed in
Continue to Exercise A-4: Adding the second operation to the SLP.
Lab 12-5
Exercise A-4: Adding the second operation to the SLP
In this exercise, you will add the properties for the second operation to be performed by
1. Right click the entry for the LAB12_SLP1_test storage lifecycle policy, located in the
right pane of the Administration Console, and select Change.
The Change Storage Lifecycle Policy window is displayed.
2. Click the Add button to add the second operation to the SLP.
3. Use the information in the table below to configure the second SLP operation.

Storage source ---
Operation Backup (Default setting)
Destination storage master_advdisk_stu
Volume pool n/a
Media owner n/a
Retention type Expire after copy (change this setting)
Verify that the second Backup operation entry is added to the Operation list of the
LAB12_SLP1_test 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.
Continue to Exercise A-5: Adding a third operation to the SLP.
Lab 12-6
Exercise A-5: Adding a third operation to the SLP
In this exercise, you will add the properties for the third operation to be performed by
1. 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.
2. Click the Add button to add a third operation to the SLP.
The New Operation window is displayed.
3. Use the information provided in the table below to complete the configuration of
the third SLP operation.

Source storage master_advdisk_stu (Backup)
Operation Duplication (Default)
Destination storage master_tape_stu (change this setting)
Volume pool duplicate_tapes (change this setting)
Media owner Any (default)
Retention type Fixed (default)
Retention period 3 months (level 5) (change this setting)
Alternate read server None (default)
Preserve multiplexing Not selected(default)
Postpone creation of this copy until Not selected (default)
the source is about to expire
The duplicate_tapes volume pool was created in lab 8. If the duplicate_tapes

volume pool does not exist, create it now.
Verify that the Duplication operation entry is added to the Operation list of the
LAB12_SLP1_test Storage Lifecycle Policy, as illustrated in the figure below.
This figure illustrates the LAB12_SLP1_test SLP with three operations included.
Lab 12-7
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.
5. Click OK in the Change Storage Lifecycle Policy window, to save the changes to the
LAB12_SLP1_test SLP, and to close the Change Storage Lifecycle Policy window.
6. Verify that entry for the LAB12_SLP1_test storage lifecycle policy is visible in the list
of SLPs that is displayed in the right pane of the Administration Console.
7. Right-click the entry for the LAB12_SLP1_test SLP.
8. Take note of the options that are displayed in the resulting menu.
9. Click anywhere outside of the menu to close the menu without making a selection.
Proceed to Exercise B: Configuring a policy to use an SLP.
Lab 12-8
Exercise B: Configuring a policy to use an SLP
In this exercise, you configure a policy that uses the LAB12_SLP1_test SLP to
automatically perform the operations specified in the SLP.
Continue to Exercise B-1: Creating a new SLP policy.
Lab 12-9
Exercise B-1: Creating a new SLP policy.
In this exercise, you will create a new backup policy that will use your new SLP.
1. Select NetBackup Management and then select Policies, New Policy in the left pane
Actions > New > New Policy.
2. Type the policy name, LAB12-console-test-slp1 in the Add a New Policy dialog box,
and click OK.
The Change Policy window is displayed.
3. Use the information provided in the table below to configure the policy Attribute
settings.
Attributes parameter Value

Policy name LAB12-console-test-slp1
Policy type MS-Windows (OS of console.example.com client)
Policy storage LAB12_SLP1_test (scroll to locate this selection)
All other policy attributes Use default settings – do not change
4. Click the Schedules tab of the policy.
5. Click the New button to add a new schedule to the policy.
The Add Schedule window is displayed.
6. 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)
Lab 12-10
7. Click OK to save the full_slp schedule.
No start window has been setup for this schedule. Only manual backups can be
run using this schedule.
8. Verify that the entry for the full_slp schedule is displayed in the Schedules tab.
9. Click the Clients tab of the LAB12-console-test-slp1 policy.
10. Add an entry for console.example.com client to the Clients list for this policy. The
console.example.com system is a Windows-x64, Windows client.
Use the method of your choice to enter the Hardware and Operating System
of the client.
11. Verify that an entry for console.example.com is added to the Clients tab.
13. Add an entry for E:\data\smallfiles to the Backup Selections of the policy.
14. Verify that the E:\data\smallfiles entry is displayed in the list of Backup
Selections of the policy.
15. Click OK to save the LAB12-console-test-slp1 policy.
16. Verify that the LAB12-console-test-slp1 policy is included in the list of policies
displayed in the All Policies pane of the Administration Console.
Proceed to Exercise C: SLP Host Properties.
Lab 12-11
Exercise C: SLP Host Properties
The SLP Parameters properties in the NetBackup Administration Console allow

administrators to customize how storage lifecycle policies are maintained and how SLP
jobs run. The properties apply to the SLPs of the currently selected master server.
Continue to Exercise C-1: Modifying SLP Host Properties.
Lab 12-12
Exercise C-1: Modifying SLP Host Properties.
In this exercise, you modify Storage Lifecycle parameter settings, located in the master
server Host Properties of the NetBackup Administration Console.
1. Select NetBackup Management and then select Host Properties, Master Servers in
An entry for the master server is displayed in the right pane of the Administration
Console.
2. Click the entry for your master server, located in the right pane of the Administration
Console, and then select Actions and then select Properties.
Actions > Properties
The Master Server Properties window is displayed.
3. Locate and click the SLP Parameters entry in the left pane (Properties) of the Master
Server Properties window.
The SLP Parameters entry is located near the bottom of the left pane of the
Master Server Properties window. You may have to scroll down to see this
entry.
The SLP Parameters are displayed in the right pane of the Master Server
Properties window. The default values for all SLP parameters are shown.
To save time in this lab activity, you modify some of the SLP Parameter values to
minimize the wait time that would normally occur between the Backup and automatic
Duplication operations (controlled by the Storage Lifecycle Policy).
4. Select the Value entry for the Force interval for small jobs parameter, and modify
the value to 1 (minute).
The default setting for the Force interval for small jobs is 30 minutes. This
parameter prevents small duplication jobs from running too frequently.
Lab 12-13
5. Verify that the Master Server Properties Force interval for small jobs parameter is
set to value to 1 (minute) – as illustrated in the figure below.
6. Select the Value entry for the Job Submission Interval parameter, and modify the
value to 1 (minute).
The default setting for the Job Submission Interval parameter is 5 minutes.
This parameter controls how often SLP processing jobs are submitted for
execution.
7. Verify that the Job Submission Interval parameter is set to value to 1 (minute).
8. Select the Value entry for the Image processing interval parameter, and modify the
value to 1 (minute).
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.
Lab 12-14
9. Verify that the Image processing interval parameter is set to value to 1 (minute).
10. Click Apply to save the SLP parameter changes.
11. Click OK to close the Master Server Properties.
A restart of the master server daemons is not required to implement the SLP
parameter changes that you have made.
12. Click OK in the Restart Daemons warning message to close the dialog box.
Proceed to Exercise D: Viewing and monitoring SLP operations.
Lab 12-15
Exercise D: Viewing and monitoring SLP operations
In this exercise, you use the LAB12-console-test-slp1 policy to initiate the operations
indicated in the LAB12_SLP1_test Storage Lifecycle Policy. Then, you monitor the SLP
operations using the NetBackup Activity Monitor.
Continue to Exercise D-1: Performing a manual backup that uses an SLP.
Lab 12-16
Exercise D-1: Performing a manual backup that uses an
SLP
2. Right-click the entry for the LAB12-console-test-slp1 policy in the All Policies pane,
and then select Actions, and then select Manual Backup.
3. Click OK in the Manual Backup window to initiate the operation.
4. Immediately click the Activity Monitor in the left pane of the Administration
Console.
Note the most recent job entries in the Activity Monitor that use the LAB12-
console-test-slp1 policy.
5. View the Job Details of the jobs that are run by the LAB12-console-test-slp1 policy
and take note of the following.
Initially, three jobs using the LAB12-console-test-slp1 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 LAB12_SLP1_test SLP.
All three (3) of the initial jobs that use the LAB12-console-test-slp1 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 to run to completion, a Duplication job is run
using the master_tape_stu storage unit.
6. 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.
7. View the Job Details of the Image Cleanup jobs that ran soon after the completion
of the Duplication job.
Lab 12-17
8. In the Status pane of the Detailed Status tab of the 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 master_tape_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 deleted
from the master_advdisk_stu storage unit after the successful duplication of the
backup image.
The Duplication job was initiated a few minutes after the backup jobs were completed.
By default, NetBackup uses the storage lifecycle parameters configured in host
properties 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 1 minute in an earlier lab
exercise. Despite this change, it is likely that it will take a few minutes for the
Duplication job to start. Remember that your lab servers are virtual machines that share
resources with other virtual servers; it is not unusual for this to add a few minutes to the
processing time.
9. Close any open Job Details windows in the Activity Monitor.
Continue to Exercise D-2: SLP operations summary.
Lab 12-18
Exercise D-2: SLP operations summary
The following jobs were initiated by the LAB12-console-test-slp1 policy, using the
operations defined in the LAB12_SLP1_test Storage Lifecycle Policy (SLP):
• A parent Backup job.

̶ This job controlled two child Backup jobs.
̶ The first child Backup job ran under the control of the LAB12_SLP1_test Storage
Lifecycle Policy, and wrote a backup image to master_msdp_stu.
̶ The second child Backup job ran under the control of the LAB12_SLP1_test
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.
̶ This job was initiated a few minutes after the completion of the Backup
operations that were initiated by the SLP (LAB12_SLP1_test).
̶ The Master Server Property setting, 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 SLP host property
setting sets the minimum wait time that must elapse before a small duplication
or replication job can be submitted.
̶ 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 master_tape_stu (specified in the SLP operations).
• After the Duplication job was completed, an Image Cleanup job was initiated.
̶ This job performs all backup image cleanup due at the time that the job is
initiated.
̶ 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.
̶ When the Image Cleanup job was called, it expired and then deleted the backup
image from the NetBackup image catalog, and from the master_advdisk_stu disk
volume.
Lab 12-19
You have completed all planned tasks for this lab activity.
Lab 12-20
Lab 13: Managing and Protecting the
NetBackup Catalog
In this lab, you perform tasks related to the management of NetBackup backup images
and the protection and recovery of the NetBackup catalogs.
Continue to Exercise A: Running NetBackup reports.
Lab 13-1
Exercise A: Running NetBackup reports
In this exercise, you configure a policy to write backup images that you use when
performing several important NetBackup catalog-related tasks in this lab activity.
Continue to Exercise A-1: Creating and modifying a new policy.
Lab 13-2
Exercise A-1: Creating and modifying a new policy
In the steps that follow, you create a new policy, LAB13-small-clients-to-media-tape, to

backup data to tape. This data will be used to run and view NetBackup reports.
If a NetBackup Administration Console window is not currently open on

console.example.com, double-click the NetBackup 8.1 Administration Console
shortcut, located on the desktop of the system to open the Administration Console.
In the NetBackup Administration Console log in screen, log in to your master server
using the credentials provided in the table below.

3. Select Policies in the left pane of the Administration Console.
Lab 13-3
4. Copy the PRE-clients-to-master-tape policy to create a new policy named LAB13-
small-clients-to-media-tape. The table below provides the detailed steps for copying
a policy to create a new policy.

1 In the All Policies pane of the Administration Console, right-click the entry for
PRE-clients-to-master-tape.
2 In the resulting menu, click the Copy to New entry.
The Copy a Policy dialog box is displayed.
3 Type the name of the new policy, LAB13-small-clients-to-media-
tape, in the New policy field.
4 Click OK to create the new policy.
The LAB13-small-clients-to-media_tape policy is opened for editing in the Change

Policy window.
5. In the Change Policy window, edit the LAB13-small-clients-to-media-tape policy to

make the changes specified in the table below.
Policy name: LAB13-small-clients-to-media-tape

Attributes tab Attribute settings:
Policy storage (destination) media_tape_stu (change to this setting)
Policy volume pool server_tapes (change to this setting)
Schedules tab: ---see step 6 on the next page ---
Clients tab no changes
Backup Selections tab: Backup Selection entries
For Windows clients: E:\data\smallfiles (change entry to this)
For Linux clients: /data/smallfiles (change entry to this)
Continue to the step 6 on the next page.
Lab 13-4
6. Modify the full schedule of the LAB13-small-clients-to-media-tape policy to remove
the start window – so that the schedule can only be run manually.
a. Click the Schedules tab of the LAB13-small-clients-to-media-tape policy.

b. Double-click the entry for the full schedule, to open the schedule.
c. Click the Start Window tab of the full schedule.
d. Click the Clear button, to clear the contents of the Start Window.
e. Click OK to save the changes to the full schedule.
After changing the full schedule to remove the start window entries, this
schedule can only be used to perform manual backups. No automated backups
will occur using the LAB13-small-clients-to-media-tape policy.
7. After making the changes to the policy Attributes, Schedules, and Backup Selections
click OK in the Change Policy window to save the policy.
8. Verify that an entry for the LAB13-small-clients-to-media-tape policy is displayed in

the list of policies in the All Policies pane of the Administration Console.
You use the LAB13-small-clients-to-media-tape policy later in this lab activity.

You return to this window in the next exercise.
Continue to Exercise A-2: Performing preliminary steps.
Lab 13-5
Exercise A-2: Performing preliminary steps
In the steps that follow, you perform a few preliminary steps to prepare for activities
you perform later in this exercise.

winmaster.example.com, or open a terminal window to your Linux-based master
You can access the desktop or command prompt of systems in your lab kit in
either of two ways:
1) By selecting the ‘tab’ that is provided for the system that is provided on the user
interface in your lab delivery environment (VMware Workstation, Hatsize), or
2) By access the system remotely from the console.example.com system in your lab
kit. The Remote System Access folder on the desktop of console.example.com
provides access to Windows-based systems using Remote Desktop (RDP), and to
Linux-based systems using PuTTY.
The use of either of the methods listed above is acceptable for accessing your
master server system.
2. Log in to your master server system, if required, using the username/password

combination specified in the table below.

3. Open a Command Prompt window on winmaster.example.com, or access the

terminal window on lnxmaster.example.com.
4. In the Command Prompt or terminal window, type the NetBackup-provided

command available_media, and press Enter.
Lab 13-6
5. Using Notepad++, or a pen and paper, record the Media IDs and status of any tapes
that are assigned to the server_tapes volume pool (status other than AVAILABLE).
The number of tapes that are assigned to the server_tapes volume pool may vary
from the results observed by others.
Notepad++ is available on console.example.com and winmaster.example.com.
6. For each Media ID you listed, execute the bpexpdate command, using the
command syntax shown below to expire all images on the tape.
Expiring the tapes will force the tapes to return them to the AVAILABLE status.
Command: bpexpdate –m [Media ID] –d 0 –force
7. Repeat the bpexpdate command for each Media ID that you recorded.
In a production NetBackup environment, the bpexpdate command should be

used with great care. The command causes NetBackup to expire all backup
images that are on a Media ID that is specified in the command syntax, making
the images on the tape unavailable for restore operations. The Media ID is
immediately unassigned, which enables the tape to be re-allocated by
NetBackup and the contents to be overwritten. Once reassigned and
overwritten the backup images can no longer be imported and recovered.
8. Run the available_media command again to verify that no tapes reside in the
server_tapes volume pool, or that all Media IDs have a status of AVAILABLE.
If necessary, repeat the use of the bpexpdate command until all Media IDs of
tapes in the server_tapes volume pool have become un-assigned (AVAILABLE),
and then continue to the next step.
9. Allow the RDP window (to winmaster.example.com) or terminal window (to

lnxmaster.example.com) to remain open.
You use this window later in this exercise.
Continue to Exercise A-3: Running backup jobs.
Lab 13-7
Exercise A-3: Running backup jobs
In the steps that follow, you initiate multiple manual backup requests using the LAB13-
small-clients-to-media-tape policy.
1. Access the NetBackup Administration Console window on the

3. Right-click the entry for the LAB13-small-clients-to-media-tape policy then click

Manual Backup.
4. When the Manual Backup window is displayed, click OK to start manual backup jobs
for each of the clients listed in the Manual Backup window.
5. Access the Activity Monitor, and monitor the progress of the two backup jobs that
are initiated.
There should be one job for each of the two clients listed in the Backup Selections
tab of the LAB13-small-clients-to-media-tape policy.
6. Allow the backup jobs to run to completion, and verify that the jobs run successfully.
If one or both 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 notify your instructor.
7. Repeat the manual backup request using the LAB13-small-clients-to-media-tape, to

back up both clients listed in the policy a second time.
Lab 13-8
8. Use the Activity Monitor to monitor the progress of the two resulting Backup jobs,
and verify that the jobs run to successful completion.
If one or both 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
9. Repeat the manual backup request using the LAB13-small-clients-to-media-tape, to

back up both clients listed in the policy a third time.
10. Use the Activity Monitor to monitor the progress of the two resulting Backup jobs,
and verify that the jobs run to successful completion.
As of now, six backup jobs have been run – three for each of the clients that
are backed up using the LAB13-small-clients-to-media-tape policy.
11. Select and expand Media and Device Management then Media then Volume Pools
from the left pane.
12. Select server_tapes in the left pane of the Administration Console.
With the server_tapes volume pool entry highlighted in the left pane of the
Administration Console, the right pane displays a list of NetBackup Volumes (by
their Media IDs) that are members of the server_tapes volume pool.
13. Click the Refresh icon on the tool bar to update the contents of the Volumes in
Volume Pool display.
14. Using Notepad++ or a pen and paper record the Media IDs that are currently
assigned to the server_tapes volume pool.
There should currently be two tapes in the server_tapes volume pool. The
Media IDs of the tapes may vary from those observed by others.
Continue to Exercise A-4: Using NetBackup Reports to view catalog data.
Lab 13-9
Exercise A-4: Using NetBackup Reports to view catalog
data
In the following steps, you will use the Report feature in the NetBackup Administration
Console to view detailed information about the contents of the NetBackup catalogs and
observe the results.
1. Select and expand NetBackup Management, and then click Reports, in the left pane
of the Administration Console window on console.example.com.
The right pane of the Administration Console lists some of the reports that are
available:
̶ Client Backups
̶ Problems
̶ All Log Entries
̶ Images on Media
̶ Media Logs
2. Click the entry for Images on Media report.
3. Accept the default settings for the report and click the Run Report button.
4. Expand the width of the Backup_ID, Policy, and Media Type columns, so that you
can see the contents of the columns.
You can alter the Column Layout of the report, as desired by dragging and dropping
the column headings in a different order so you can see the Backup_ID, Policy, and
Media Type columns without scrolling. You can also right-click on the first row of
the results and select Columns > Size to Data to increase the width of all the
columns in the report.
Lab 13-10
5. Refer to the output of the Images on Media report to answer the questions below.
Use Notepad++ or a pen and paper to make note of the answers.
Images on Media report

How many unique client names are listed in the report output?
What Media Types are listed in the report output?
How many of the Backup_IDs that are listed in the report output were created using
the LAB13-small-clients-to-media-tape policy?
Images on Media report - Answers

How many unique client names are listed in the report output?
A: answers may very but it is likely you will see at least 4 unique names.
What Media Types are listed in the report output?
A: 2. Removable media and Disk
How many of the Backup_IDs that are listed in the report output were created using
the LAB13-small-clients-to-media-tape policy?
A: 6. There should be 3 Backup IDs listed for each client that was backed up using the
LAB13-small-clients-to-media-tape policy.
6. Change the Report Settings for the Images on Media report to show only on backup
images that were created for the Client, xxxmaster.example.com
You may have to click twice on the dropdown arrow to get a list of client host names
to appear.
7. Click the Run Report button, to run the report again.
8. Note that the new output of the report shows entries only for Backup_IDs (backup
images) that were created for the client, xxxmaster.example.com
The NetBackup command that creates the equivalent of the Images on Media
report is the bpimmedia command.
9. Depending on your master server system, open RDP window for

winmaster.example.com, or the terminal (SSH) window for
Lab 13-11
10. In a Command Prompt window on winmaster.example.com, or the terminal
window on lnxmaster.example.com, type the command shown below.
This command output shows the same information as the Images on Media report
for the client.
Command: bpimmedia –client [client_name] –U
• Example 1: bpimmedia –client winmaster.example.com –U

• Example 2: bpimmedia –client lnxmaster.example.com –U
In the examples provided above, the master server system is also the client, for
which backup images are being searched.
11. Keep the RDP or terminal window open to your master server.
You will return to this window in a few moments.
13. From the Reports entry, click to expand the Tape Reports entry in the left pane of
The following Tape Reports are listed beneath the Tape Reports entry:
̶ Images on Tape
̶ Tape Logs
̶ Tape Contents
̶ Tape Summary
̶ Tape Written
̶ Tape Lists
14. Click the entry for the Images on Tape report in the left pane of the Administration
Console.
15. Use the default Report Settings and click the Run Report button.
The report output is displayed at the bottom of the right pane of the Administration
Console.
Lab 13-12
16. Scroll to the right in the Images on Tape report output, and record the highest
numbered Media ID listed in the report output.
̶ You can click the column heading for Media IDs to sort from high to low.
̶ You can use Notepad++ or a pen and paper to record the Media ID.
For winmaster.example.com the Media ID should be E010xx and for

lnxmaster.example.com the Media ID should be E020xx.
This tape is a member of the server_tapes volume pool.
17. Run the Images on Tape report again, but modify the Media ID report setting
parameter to search for images on the Media ID recorded in step 16.
You may have to click the dropdown arrow twice to view the individual Media ID’s.
Note that the report output lists the Backup_IDs for only the backup images
that reside on the specified Media ID.
You may note that the drop-down list is very small. It is a good idea to refresh
the Report Settings display (select View > Refresh, or click the Refresh icon on
the tool bar) to refresh the contents of the report’s drop-down lists.
The NetBackup command that provides the output equivalent to the output of
the Images on Tape report is the bpimmedia command, used with the
-mediaid <mediaid of tape> command option.
18. Access your Windows-based master server system, winmaster.example.com, or the

command prompt on your Linux-based master server, lnxmaster.example.com.
19. At the Command Prompt on winmaster.example.com or lnxmaster.example.com,

type the command shown below, and press Enter, to display the output of the
Images on Tape report for the Media ID that you recorded in step 16.
Command: bpimmedia –mediaid [Media ID] –U
̶ Example 1: bpimmedia –mediaid E01005 –U

̶ Example 2: bpimmedia –mediaid E02005 –U
Lab 13-13
20. Take note of how many images were written to the Media ID from the output of the
bpimmedia –mediaid command.
There should be 3 images/entries listed.
21. Allow the RDP or terminal window to remain open to your master server.
23. From the Reports entry select Disk Reports in the left pane of the Administration
Console.
24. Expand the Disk Reports entry.
The following Disk Reports are listed beneath the Disk Reports entry:
̶ Images on Disk
̶ Disk Logs
̶ Disk Storage Unit Status
̶ Disk Pool Status
25. Click the entry for the Images on Disk report.
The Report Settings for the report are displayed in the right pane.
26. Click the Refresh icon on the tool bar to update the contents of the Report Settings
drop-down lists.
27. Use the Report Settings to select the Disk Type = BasicDisk, and to set the Path field
to the path used by the master_bdisk_stu storage unit, as identified in the table
below.
Master server name Storage unit name Disk Path:

winmaster.example.com master_bdisk_stu --leave blank--
lnxmaster.example.com master_bdisk_stu /bdisk
You can examine the master_bdisk_stu storage unit configuration to verify the
disk path used by the storage unit.
Lab 13-14
28. After selecting the Report Settings, click the Run Report button to run the report.
29. Take note of the contents of the Path column in the Images on Disk report output.
The Path column of the Images on Disk report output shows the path used by
the storage unit, and appends to it the actual backup image file name that was
recorded to the disk volume used by the storage unit. The backup image name
has the format [Backup ID]_Cx_Fx, where Cx is the copy number and Fx is the
fragment number of the backup image.
Example 1: winmaster.example.com_1526382799_C1_F1
Example 2: lnxmaster.example.com_1526382799_C1_F1
The NetBackup command that provides the output equivalent to the output of
the Images on Tape report is the bpimmedia command, used with the –
disk command option.
30. Feel free to run any other reports and review the output.
31. When finished collapse the Reports entry in the NetBackup Administration Console.
Continue to Exercise B: Verifying, expiring, and importing backup images.
Lab 13-15
Exercise B: Verifying, expiring, and importing
backup images
In this exercise, you use the Catalog interface provided by the NetBackup Administration
Console to view and manage NetBackup backup images.
Continue to Exercise B-1: Populating the NetBackup catalogs.
Lab 13-16
Exercise B-1: Populating the NetBackup catalogs
In the following steps, you run a backup job to populate the NetBackup catalogs.

2. Activate the PRE-clients-to-master-bdisk policy.
a. Select the Policies entry in the left pane of the Administration Console window.
b. Locate and right-click the PRE-clients-to-master-bdisk policy entry.
c. Click Activate in the menu.
d. Verify that the PRE-clients-to-master-bdisk policy has been activated.
3. Initiate a manual, full backup operation using the PRE-clients-to-master-bdisk

policy, to back up all clients listed in the policy.
For detailed steps on how to initiate the manual backup please use the table below.
IMPORTANT: In a previous lab activity (Lab 4) you deactivated the PRE-clients-

to-master-bdisk policy. To enable you to use the policy to perform a backup,
YOU MUST ACTIVATE the policy. To do so, right-click the policy name and
select Activate in the resulting menu.
Step # Step details

2 Click the entry for the PRE-clients-to-master-bdisk policy, located in
the All Policies pane of the Administration Console.
4 Click on the FULL schedule.
4. Select the Activity Monitor and view the progress of the two, most recent backup
jobs that used the PRE-clients-to-master-bdisk policy.
Lab 13-17
5. Allow the jobs to run to completion, and verify that the jobs were completed
successfully (status 0).
Continue to Exercise B-2: Searching for backup images in the Catalog user interface.
Lab 13-18
Exercise B-2: Searching for backup images in the Catalog
user interface
In the steps that follow, you use the Catalog interface of the NetBackup Administration
Console to search the contents of the NetBackup catalog.
1. Select the Catalog entry, located under NetBackup Management in the left pane of
The right-pane of the Administration Console displays the Catalog interface.
2. Click the Refresh icon on the tool bar to update the drop-down menus of the
Catalog pane.
The Catalog interface provides two tabs: Search and Results. The Search tab of
the Catalog interface is selected by default.
3. Use the Catalog utility to search FULL backup images created by the PRE-clients-to-
master-bdisk policy that were created in the first week of last month. The table
below provides parameters to use to perform the search.
Parameter Value
Action: Verify (default)
Media ID: <All> (default)
Media host: (greyed out)
Copies: Primary Copy (default)
Policy name: (drop down) PRE-clients-to-master-bdisk
Type of backup: drop down Full Backup
Time/Date Range From: The first day of the previous month/any time.
Note: Use the Calendar icon for the From:
Date/Time Range field to select the month and
day.
Time/Date Range To: The 7th day of the previous month/any time.
Note: Use the Calendar icon for the To:
Date/Time Range field to select the month and
day.
4. After entering the parameters for the Verify operation, click the Search Now button
to perform the search of the NetBackup catalog.
Lab 13-19
The Messages pane, located at the bottom of the Catalog interface, below the
Search Results pane, displays messages relating to the most recent operation.
5. You may need to increase the size of the Messages pane to view any messages.
6. Note that the Messages pane contains a Catalog Search Information dialog box with
the message: “INF – Status=found no images or media matching
the selection criteria”.
This message appears because no backups were run in this environment during
this time. Therefore, there were no images, matching the search criteria, in the
NetBackup catalog to display.
7. Close the Catalog Search Information dialog box.
8. Change the search criteria to change the Date/Time Range to include the From:
date to the first day of this class, and the To: date of the ending date of this class.
Allow all other search criteria to remain at the current values.
9. Click the Search Now button to initiate the catalog search.
Lab 13-20
10. Note the Search Results that are displayed in the bottom pane of the Catalog
interface.
The Search Results pane should include entries for at least two Backup IDs.
These were created by the backup jobs you performed in Exercise A of this lab
activity. Depending upon other backup jobs you have performed to this point
in the course there may be entries for additional Backup IDs.
The two most recent backup images were written to the disk volume/file
system specified by the master_bdisk_stu storage unit configuration.
11. From the Search Results pane, sort the contents so that the backup images are in
descending order by the Date they were created.
To sort in descending order, click the Date column heading until a downward
pointing arrow is displayed.
12. Verify that the first (top) two entries listed in the Search Results pane are those that
were created by the most recent backup jobs that used the PRE-clients-to-master-
bdisk policy.
Verify the backup images were written today and to the master_bdisk_stu
storage unit.
Continue to Exercise B-3: Verifying backup images using the Catalog interface.
Lab 13-21
Exercise B-3: Verifying backup images using the Catalog
interface
In the steps that follow, you use the Catalog interface of the NetBackup Administration
Console to Verify the contents of selected backup images.
1. From the Search Results pane, click to select the entry for the first (top) Backup ID.
2. With the top entry highlighted, hold the SHIFT key on your keyboard, and click the
entry for the second Backup ID that is listed.
The entries for the top two Backup IDs should be highlighted in the Search
Results pane.
3. Right-click the highlighted entries and select Verify in the shortcut menu.
A Confirm Verify dialog box is displayed.
You can also select Actions (from the toolbar menu) then Verify. Be careful to
select the Actions (plural) from the toolbar menu at the top of the console and
not the Action (singular) combo box at the top of the Search tab in the right
pane of the catalog tool. It is easy to confuse these two similar-sounding
controls. Read the lab steps carefully.
4. Verify that the Log all files found in the verified image(s) check box is not selected,
and then click OK to proceed with the Verify operation.
Lab 13-22
5. Click the Results tab, located at the top of the right pane (Catalog pane) of the
The Results tab is displayed in two panes.
̶ The top pane is labelled as the Results pane, and lists entries for various
operations that have been initiated in the Catalog interface.
̶ The bottom pane shows the contents of the Log File that is associated with
the entry that is selected in the top (Results) pane.
6. Verify the top pane, Results, contains an entry, jbpVerify-yyyymmddhhmmss, and

that the entry is currently highlighted.
Example: jbpVerify-20180112114009.log
7. Verify the bottom pane contains the contents of the Log File that is associated with
the verify operation that is highlighted in the top pane.
8. Select Help > Help Topics in the Administration Console tool bar.
Lab 13-23
9. When the Documentation window is displayed, locate and click the link for Verifying
backup images, located under More Information in the right pane of the window.
10. Read the information provided under the heading, Verifying Backup Images, that is
displayed in the Documentation window.
During a Verify operation, NetBackup reads the contents of the backup image
(recorded on the backup media), and compares the backup image contents to
the records contained for the backup image in the NetBackup catalog.
11. Select File > Close to close the Documentation window.
Lab 13-24
12. Verify that the Log File pane displays the message, Status=successfully verified 2 of
2 images.
Click View > Refresh or the Refresh icon on the toolbar to refresh the results
displayed. You can also set the Refresh rate at the bottom of the window.
Continue to Exercise B-4: Viewing Verification jobs in the Activity Monitor.
Lab 13-25
Exercise B-4: Viewing Verification jobs in the Activity
Monitor
In the steps that follow, you use the Activity Monitor to view the verification job that
was performed in the last exercise.
1. Click the Activity Monitor entry in the left pane of the Administration Console.
2. Locate and double-click the entry for the most recent Media Verify job.
3. Select the Detailed Status tab to examine the log message in the Status pane.
4. Close the Job Details window when you are finished reviewing the log messages for
the Media Verify job.
the Administration Console..
The right pane should still display the Results tab, with the jbpVerify operation
highlighted in the top (Results) pane, and the contents of the verify Log File
displayed in the bottom pane.
6. Click the Search tab in the right (Catalog) pane of the Administration console.
7. In the Search Results pane (at the bottom of the right pane), click the first (top)
Backup ID that is listed.
Only one (the top) entry should be highlighted.
8. Right-click the entry for the Backup ID and select Verify in the shortcut menu.
Lab 13-26
9. When the Confirm Verify dialog box is displayed, this time mark the check box to
Log all files found in the verified image(s), and click OK to initiate the verify
operation.
10. Click the Results tab, at the top of the Catalog pane of the Administration Console.
11. Click the Refresh icon, if necessary, to update the contents of the Results tab.
12. Verify the Results (top) pane now displays entries for two jbpVerify operations.
13. Identify and click the entry for the most recent jbpVerify operation, as indicated by
the contents of the Time Requested column.
You can change the sort order of the Results pane by clicking the column
headings. By doing so in the Time Requested column, you can display the
entries for the most recent jobs first (in descending order by date).
14. Note that by selecting the Log all files found in the verified image(s), that the Log
File for the verify operation lists all the files that are present in the verified backup
image.
Continue to Exercise B-5: Expiring NetBackup disk-based backup images.
Lab 13-27
Exercise B-5: Expiring NetBackup disk-based backup
images
In the steps that follow, you use the NetBackup Administration Console’s Catalog
interface and the NetBackup command-line interface to expire backup images from the
NetBackup catalog and view the effect of these operations.
1. Select Catalog, if necessary, in the left pane of the Administration Console.
2. Click the Search tab in the right (Catalog) pane of the Administration Console.
The Search Results pane should contain the results from the most recent search for
backup images that were created using the PRE-clients-to-master-bdisk policy and
the Full Backup schedule – which you performed earlier in this exercise.
3. Using Notepad++ or pen and paper, record the Backup ID for the backup image of
the most recent backup of your master server system (winmaster.example.com or
lnxmaster.example.com) that used the PRE-clients-to-master-bdisk policy.
Example: winmaster.example.com_1515744068
Example: lnxmaster.example.com_1515744000
You will need the Backup ID in a later step.

You return to this window in a few minutes.
5. Access your Windows-based master server system, winmaster.example.com, or

your Linux-based master server, lnxmaster.example.com.
This window should be open from a previous exercise.
Lab 13-28
6. Access the open File Explorer window on winmaster.example.com, or the command
prompt on lnxmaster.example.com, and navigate to the disk volume or directory
that is the target for the master_bdisk_stu storage unit.
Detailed instructions are provided in the table below.
Steps on Windows-based master server, winmaster.example.com

1 Double-click the File Explorer shortcut located on the desktop.
2 Double-click the entry for the BASICDISK (F:) disk volume in the left pane of
the File Explorer window.
3 Click the bdisk folder to display the contents
Note: The F:\bdisk is the target volume for the master_bdisk_stu storage
unit on winmaster.example.com.
4 How many files, in the F:\bdisk directory, match the name of the Backup
ID?
Steps on Linux-based master server, lnxmaster.example.com
1 Execute the df –h command to list the file systems and mount points on
this NetBackup server system.
Command: df -h
2 Take note of the /bdisk directory, that is the target directory for the
master_bdisk_stu storage unit on lnxmaster.example.com.
3 Change directory to the /bdisk directory.
Command: cd /bdisk
4 List the contents of the /bdisk directory.
Command: ls -l
The contents of the /bdisk directory are displayed in the output of the ls
command.
5 How many files, in the /bdisk directory, match the name of the Backup ID?
Lab 13-29
You should find four files containing the Backup ID that you recorded in step 3.
This is important. When a backup image is written to NetBackup basic disk

storage, four files are created which comprise the backup image. These are the
files from which a restore of the client data is performed. Two of the files have
an .img file extension, and two of the files have an .info file extension. On
Windows, you may have to enable the display of file extensions in order to see
the file extensions.
You return to this window in a few moments
9. Select Catalog, if necessary, in the left pane of the open NetBackup Administration
Console window.
10. Verify that the Search tab is selected at the top of the right pane.
The Search Results (bottom) pane of the right pane contains the results of the most
recent search operation that you performed.
11. Click the entry for the Backup ID for the most recent backup of your master server
(xxxmaster.example.com) that was performed using the PRE-clients-to-master-
bdisk policy.
This is the Backup ID for which you identified the backup images files on the
master_bdisk_stu storage unit disk volume in previous steps.
Lab 13-30
12. Right-click on the Backup IDs and select Expire.
The Expire Images dialog box is displayed, and with the warning “The expiration of
backup images is irrevocable… Would you like to expire the selected images?”
Expiring backup images that are written to disk-based backups requires extra
caution, as expiring of the images is permanent. There is no ability to import an
image after it has been expired from disk-based storage.
13. Click Yes in the Expire Images dialog box, to continue.
14. Verify the image entry is no longer listed in the Search Results (bottom) pane of the
Administration Console:
The entry for the image that you expired should have disappeared from the Search
Results pane.
15. Access the open RDP window to your Windows-based master server system,
winmaster.example.com, or the terminal (SSH) window that is open to your Linux-
based master server, lnxmaster.example.com.
16. Search for backup image files in the F:\bdisk folder on winmaster.example.com
or type the following command to on lnxmaster.example.com, to verify the entry is
removed for the Backup_ID that you expired.
Command: ls -l
17. Are the backup image files for the Backup ID that you expired present on the disk
volume for the master_bdisk_stu storage unit?
The files that comprise the backup image on the storage unit are no longer
present on the disk volume for the storage unit.
When a backup image that was written to NetBackup disk-based storage is

expired – either automatically by NetBackup when the image reaches its
expiration date/time, or manually by a backup administrator – the backup
image is irrevocably deleted from the disk volume for the storage unit.
Lab 13-31
Continue to Exercise B-6: Expiring tape-based backup images.
Lab 13-32
Exercise B-6: Expiring tape-based backup images
In the steps that follow you use the NetBackup Catalog user interface to identify backup
images that have been written to tape media. Then, you expire the backup images using
the NetBackup Catalog user interface. In the process, you observe the contents of the
NetBackup catalogs, and of the physical tape to see the impact of image expiration on
tape-based backup images.
1. Access the NetBackup Administration Console window on desktop of

The right pane of the Administration Console displays the Catalog user interface.
The top pane contains two tabs, the Search tab and the Results tab.
3. Verify that the Search tab is selected at the top of the right pane of the
When the Search tab is selected, the bottom pane of the Catalog interface displays
the Search Results pane.
In Exercise A of this lab activity you initiated three manual backup jobs that
used the LAB13-small-clients-to-media-tape policy.
4. Click the Refresh icon on the tool bar to update the contents of the drop-down
menus of the Catalog interface.
Lab 13-33
5. In the Search tab of the Catalog interface, set the search parameters as indicated in
the table below.
Parameter Value
Action: Verify (default)
Media: Media ID: <All>
Media host: (greyed out)
Copies: Primary Copy (default)
Policy name: (drop down) LAB13-small-clients-to-media-tape
Type of backup: drop down <All Backup Types> (default)
Time/Date Range From: Set the Date/Time Range From: date of the first
day of this course.
Time/Date Range To: Set the Date/Time Range To: date of the last day
of the course.
6. Click Search Now to initiate the search of the NetBackup catalogs for backup images
that meet the search criteria.
Within a few moments the Search Results (bottom) pane of the Catalog interface
displays a list of the backup images that meet the search criteria – that were created
using the LAB13-small-clients-to-media-tape policy, in the time frame provided.
Entries for at least six Backup IDs should be listed in the Search Results pane.
All these images were written to two (2) Media IDs – three images to one tape,
and three images to another tape.
Lab 13-34
7. Using Notepad++ or a pen and paper record the Backup ID, and Media ID for the
three Backup IDs that were written to the tape having the lowest (numerical) Media
ID.
Also record the order in which the images were written to the tape, for example:
first (oldest), second, third (newest).
The Media IDs used on your lab systems may vary.
For Example: If Media ID 1004L5 and 1005L5 were used to perform the 6 backup
jobs then media 1004L5 is the lowest Media ID. Only record lowest Media ID and
the Backup ID in the order of image creation for the backup jobs.
Backup ID Media ID Order of image creation

winmaster.example.com_1515700973 1004L5 1
8. Allow the Catalog window to remain open.
You return to this window in a moment.
9. In the NetBackup Administration Console window, select File, and then New
Console.
Selecting File > New Console opens another NetBackup Administration

Console window that is connected to your master server, and can be useful
when you want to compare information from different parts of the user
interface.
10. In the second Administration Console window, select Media and Device
Management then Media.
With the Media entry selected in the left pane of the Administration Console
window, the Volumes (tapes) that are configured in NetBackup (and for which
entries exist in the NetBackup media catalog) are displayed in the right pane of the
Lab 13-35
11. Change the Column Layout of the Volumes pane (in the second Administration
Console window) to display the first five (5) columns in the order listed below.
From the left side of the Volume pane to the right. The order of the remaining
columns can be set in any order, according to your preference.
̶ Media ID
̶ Time Assigned
̶ Images
̶ Valid Images
̶ Volume Pool
̶ Remaining columns – in any order of your preference.
You can change the layout of the columns by dragging and dropping a label
(header) for a column to its desired column position.
12. Click the Refresh icon in the toolbar to update the Volumes display.
13. In the Volume pane (of the second Administration Console window), locate the
entry for the Media ID that you recorded from Step 7.
14. Using Notepad++ or pen and paper record the how many Images and Valid Images
are on the Media ID.
The Images and Valid Images columns contain information for the tapes that
were used to write the backup images for the LAB13-small-clients-to-master-
tape policy. The Media IDs used in your lab environment may vary.
The figure above is for example purposes only, and intended to highlight the
contents of the Images and Valid Images columns. Do not be concerned that
the specific information represented in the figure does not match your lab
environment.
15. Access the first Administration Console window on console.example.com.
Lab 13-36
16. The Search Results pane of this window is currently displaying the backup images
that were written by the LAB13-small-clients-to-media-tape policy.
17. Click the entry for the oldest Backup ID that was written to the Media ID identified
in Step 7.
This was the first backup image that was written to the tape.
18. Right-click on the highlighted entry and click Expire.
The Expire Images dialog box is displayed.
19. Click the Yes button to dismiss the dialog box and to expire the image.
20. Verify that within a few moments the entry for the Backup ID that you expired is
removed from the list of backup images that is displayed in the Search Results pane.
21. Access the second open NetBackup Administration Console window.
The right pane of the second Administration Console window is currently displaying
the list of Volumes that are configured in NetBackup.
22. Click the Refresh icon on the tool bar to update the contents of the Volumes pane.
Lab 13-37
23. Using Notepad++ or a pen and paper, record the current contents of the Images and
Valid Images columns for the Media ID.
You should observe that the Images column for the Media ID remains the same as
prior to the backup image expiration, but the Valid Images column has been
decremented by one. There are three images on the tape, however, NetBackup is
currently only tracking two of those three images.
Continue to Exercise B-7: View the Media ID contents in the Tape Contents report.
Lab 13-38
Exercise B-7: View the Media ID contents in the Tape
Contents report
In the steps that follow, you use the NetBackup Tape Contents report to view the
contents of the tape from which the backup images were expired.
1. Access the second open NetBackup Administration Console window on desktop of

2. From Reports select Tape Reports then Tape Contents.
The right pane of the Administration Console displays the Report Settings for the
Tape Contents report.
3. Click the Refresh icon on the tool bar to update the contents of the drop-down
menus for the Report Settings fields.
4. Set the Report Settings parameters as noted below.
̶ Media Owner: xxxmedia.example.com (winmedia.example.com or

lnxmedia.example.com)
̶ Media ID: select the entry for the Media ID from Step 7 in the previous exercise.
6. When the Tape Contents Report dialog box is displayed, click OK to acknowledge
the dialog box and to run the report.
Lab 13-39
The Tape Contents report mounts the tape and reads the tape contents (file
headers) to generate the report output. It may take a few moments for the
report output to be displayed.
7. Review the output of the report. Why are there three files on the tape when you
expired one in a previous exercise?
When a backup image is expired from a tape, the actual backup on the tape is not
affected. Expiration of the backup image that resides on a tape only removes the
information for the backup image from the NetBackup catalogs. This enables
NetBackup to import the image – which is the act of re-creating the catalog
information for the backup image in the NetBackup catalogs. However, when all
backup images are expired from a tape, the tape becomes de-assigned. When that
happens, NetBackup can reassign the tape at any time for use to record other
backup images. After the tape has been re-assigned, and use to record new backup
images, the ability to import the overwritten backup images no longer exists.
The behavior you have observed here is important. When an image is expired
from disk-based storage it is immediately and irrevocably deleted from the
storage media. When a backup image is expired from tape media, the entries
for the image are removed from the NetBackup catalog, but the image itself is
still resident on the tape to which it was written – providing the capability to
import the image. Importing the image is the operation that results in the
recreation of the NetBackup catalog information for the image.
As time elapses, it is a normal occurrence for backup images to reach their

expiration date. The expiration date for images is determined by the retention
level setting in the schedule of the policy that was used to perform the backup
of the client. If a Storage Lifecycle Policy is used the image retention is
established by the SLP that is referenced/used by the policy that was used to
create the backup image. NetBackup automatically and routinely performs
image cleanup operations to (among other tasks) expire backup images that
have reached their expiration. When the last backup image is expired from a
tape (the valid images counter for the tape reaches zero (0), a routine
(bpexpdate –deassignempty) runs once daily to move tapes from the
assigned state back to the de-assigned state.
8. Close the second NetBackup Administration Console window.
Continue to Exercise B-8: Importing NetBackup backup images.
Lab 13-40
Exercise B-8: Importing NetBackup backup images
In the previous steps of Exercise B, you used the image expiration capability of the
NetBackup Catalog user interface to expire an image from a tape, and you observed the
results in the NetBackup Administration Console, using the Media and Device
Management > Media user interface and the Tape Contents report.
In the steps that follow, you use the Import capability of the Catalog interface to import
an expired image from a tape to rebuild the catalog entries for the image in the
NetBackup catalogs.

3. Verify that the Search tab is selected at the top of the right pane of the
4. Click Refresh in the toolbar to update the contents of the drop-down menus in the
5. From the toolbar menu, select Actions then Initiate Import.
Importing backup images in NetBackup is a two-phase process. You perform

each of these phases in the steps that follow.
Lab 13-41
6. From the Initialize Import window, enter the parameters specified below.
̶ Media Server (Windows): winmaster.example.com

(Linux): lnxmaster.example.com
̶ Image Type: Tape
̶ Media ID: *(recorded earlier)
*In step 7 of Exercise: Expiring tape-based backup images, you noted that
information for a tape from which you expired an image.
7. Click OK in the Initialize Import window, to start phase 1 of the import operation,
and to close the window.
The Confirm Initiate Import dialog box is displayed.
8. Click OK to continue with the operation.
9. Click the Results tab in the Catalog (right) pane.
10. Verify there is an entry for a jbpImport1 operation displayed in the Results pane at
the top of the Catalog.
Lab 13-42
The figure above is for example purposes only. Do not be concerned about the
specific information represented in the table.
11. Click the entry for the jbpImport1 operation, and note that the bottom pane of the
Results tab, changes to show the contents of the Log File for the import operation.
12. Carefully review the contents of the Log File pane to observe what this part of the
import operation is doing.
The first phase of the import operation reads the image headers that are
present on the tape and compares them to backup image headers that exist in
the NetBackup catalogs. If an image header is detected on the tape that is not
present in the NetBackup catalogs, the backup image header is recreated in the
NetBackup catalogs. If image headers that are read from the tape are present
in the NetBackup catalog, those headers are skipped (they represent unexpired
backup images in the NetBackup catalogs).
13. Verify that the first phase of the import operation (jbpImport1) was successful
before continuing.
If the operation failed, view the log file for the failed job. Perform basic
troubleshooting and attempt to resolve the problem. Then, repeat the import
operation. If the job continues to fail then notify your instructor.
14. Click the Search tab in the right pane of the Administration Console.
15. Click the Refresh icon in the toolbar to update the contents of the drop-down menus
Lab 13-43
16. Set the parameters in the Search tab using the values provided in the table below.
Parameter Value
Action: Import
Media ID:
Media host: <All Media Hosts> (default)
Copies: <All Copies> (default)
Policy name: (drop down) <All policies> (Change parameter)
Policy type: <All Policy Types> (default)
Type of backup: drop down <All Backup Types> (default)
Client: <All Clients> (default)
Job Priority: Accept default setting
Time/Date Range From: Set the Date/Time Range From: date of the first
day of this course.
Time/Date Range To: Set the Date/Time Range To: date of the last day
of the course.
17. Click Search Now to begin the search operation for backup images that meet the
criteria provided.
The Search Results pane displays a list of backup images that have been
discovered during phase one import process, and that are eligible for the phase
two of the import operation. Note that only a single backup image is identified.
18. Click to select the entry for the Backup ID that is listed in the Search Results pane.
19. Right-click on the Backup image and select Import. (NOT Initiate Import).
The Confirm Import dialog box is displayed.
20. Click OK to precede with phase two of the import operation.
21. Click the Results tab in the right pane of the Administration Console.
22. Refresh in the toolbar to update the contents of the Results pane.
You can also increase the Refresh rate, located at the bottom of the windows, to 5
seconds.
Lab 13-44
23. Verify there is an entry for a jbpImport2 operation is displayed in the Results pane.
The figure above is for example purposes only. Do not be concerned about the
specific information represented in the table.
24. Click to highlight the entry for the jbpImport2 operation in the Results pane
25. Review the contents of the Log File for the import (phase two) operation.
Note that the Log File specifically identifies this as phase two of an import
operation. Phase two of the import operation mounts the tape from which the
backup image is being imported, reads the contents of the NetBackup backup
image on the tape, and uses the data that is read from the backup image to
reconstruct the backup image file contents in the NetBackup catalog.
There are other image import scenarios that are more complex than the one
you have performed here. An example is a situation where all the backup
images on a tape have been expired, and the tape has been moved back into
the scratch_tapes volume pool. If an import operation is required from such a
tape, immediate action is required so that the tape will not be re-assigned for
use by NetBackup. A best practice in this case is to move the tape into a new
volume pool that will not be used by any existing policy. Then, you can safely
perform phase one and phase two of the import operation without the concern
that the tape will be re-assigned and overwritten. Also, Import phases will not
work on volumes in a SCRATCH pool.
Continue to Exercise B-9: Viewing Import jobs in the Activity Monitor.
Lab 13-45
Exercise B-9: Viewing Import jobs in the Activity Monitor
In the steps that follow, you briefly access the NetBackup Activity Monitor to view
information for Import jobs.
3. Locate and double-click the entry for the Image Import job Type that has the lowest-
numbered Job ID, to open the Job Details for the job.
4. From the Job Overview, view the File List pane entry.
create_db_info [Media_ID]
The File List contains the same Media ID that you expired the Backup image from.
5. Click the Detailed Status tab for the job, and briefly view the contents of the tab.
This job performs phase one of the import operation.
7. Locate and double-click the entry for the Import job Type that has the highest-
numbered Job ID, to open the Job Details for the job.
There should only be two Import jobs that have recently been performed.
8. From the Job Overview, view the File List pane entry.
xxxmaster.example.com_[Backup_ID]
or
xxxmedia.example.com_[Backup_ID]
A single Backup ID was imported by this job.
Lab 13-46
9. Click the Detailed Status tab for the job, and briefly view the contents of the tab.
Note that the Status pane identifies the Media ID that is read to perform the import
(phase two) job.
Continue to Exercise B-10: Preparing for the next exercise.
Lab 13-47
Exercise B-10: Preparing for the next exercise
At this point in the lab activities you may be running out of tapes that can be used for
future activities. In the steps that follow you will expire all the images on two tapes to
return those tapes to the scratch_tapes volume pool, making them available for use.

winmaster.example.com, or the command prompt of your Linux-based master



4. In the Command Prompt or terminal window, type the command below then press
Enter.
Lab 13-48
5. Using Notepad++ or a pen and paper, record the Media IDs and status of any tapes
that are assigned (status other than AVAILABLE) to the server_tapes volume pool.
The number of tapes that are assigned to the server_tapes volume pool in your lab
environment will most likely vary from what is displayed in the figure below. The
figure shown below is only an example.
6. For each Media ID you recorded, execute the bpexpdate command, using the
command shown below.
This command expires all images on the tape and returns the tape to the AVAILABLE
status.
Lab 13-49
7. Repeat the bpexpdate command for each Media ID that you recorded in the table
above.

A tape may still be resident in the server_tapes pool if you manually moved a
tape from the scratch_tapes pool to the server_tapes pool. Tapes that are
manually moved out of the scratch pool will not be automatically returned to
the scratch pool.
Lab 13-50
9. If necessary, repeat the use of the bpexpdate command until all Media IDs of
tapes in the server_tapes volume pool have become un-assigned (AVAILABLE), and
then continue to the next step.
A tape may still be resident in the server_tapes pool if you manually moved a
tape from the scratch_tapes pool to the server_tapes pool. Tapes that are
manually moved out of the scratch pool will not be automatically returned to
the scratch pool.
10. Allow the RDP window (to winmaster.example.com) or terminal window (to
lnxmaster.example.com) to remain open.
Continue to Exercise C: Configuring and running NetBackup catalog backups.
Lab 13-51
Exercise C: 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.
Continue to Exercise C-1: Creating a Disaster Recovery passphrase.
Lab 13-52
Exercise C-1: 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 master server
during a re-installation of the NetBackup server software.
2. Select Security Management in the left pane of the Administration Console, and
then select Global Security Settings.
3. Select the Disaster Recovery tab at the bottom of the Administration Console.
4. In the Passphrase and Confirm Passphrase field type: Tra1n!ng.
5. Click Save then click OK.
Continue to Exercise C-2: Creating a Catalog Backup policy.
Lab 13-53
Exercise C-2: Creating a Catalog Backup policy
In the steps that follow, you create a catalog backup policy, LAB13-catalog-to-master-
tape, to protect the NetBackup catalog configuration.
3. Right-click in the white space of All Policies and select New Policy.
4. In the Policy name field, of the Add a New Policy dialog box, type LAB13-catalog-to-
master-tape, and click OK.
5. In the Change Policy window, configure the policy Attributes using the information
Policy Attributes for LAB13-catalog-to-master-tape

Attributes Tab
Policy type NBU-Catalog
Policy storage: master_tape_stu
Policy volume pool: CatalogBackup
All other policy Attributes: use default settings
A policy with a Policy type of NBU-Catalog has only three tabs: the Attributes,
Schedules, and Disaster Recovery tabs.
6. Click the Schedules tab.
7. Create a Full Backup schedule using the parameters described in the table below.
Schedule 1 parameter settings:

Attributes tab:
Schedule name: WEEKLY-FULL
Type of backup Full Backup
Schedule Type Frequency
Frequency: 1 week
Attributes Retention 2 weeks (level 1) (default)
Start Window: none (only manual backups)
Lab 13-54
8. Create a Differential Incremental Backup schedule using the parameters described
in the table below.
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(level 1) (default)
Start Window: none (only manual backups)
9. Create another Differential Incremental Backup schedule using the parameters

described in the following table.
Schedule 3 parameter settings

Attributes tab:
Schedule Name: SESSION-DIFFERENTIAL
Schedule type: After each backup session (radio button)
Retention: 2 weeks(level 1) (default)
Start Window: 7 days per week/24 hours per day
10. Verify all three schedules you have created are visible in the Schedules tab of the
policy.
11. Click the Disaster Recovery tab.
Lab 13-55
12. Enter the Disaster Recovery parameters as provided in the table that is appropriate
for your master server – winmaster.example.com or lnxmaster.example.com.
Disaster Recovery tab settings – for winmaster.example.com

Path \\console\dr_files
Logon: EXAMPLE\Administrator
Password: train
Send in an E-mail attachment check box selected (Default setting)
E-mail address NetBackup@console.example.com
Disaster Recovery tab settings – for lnxmaster.example.com

Path /mnt/dr_recovery_files
Logon: leave blank – not required
Password: leave blank – not required
Send in an E-mail attachment check box selected (Default setting)
E-mail address NetBackup@console.example.com
In this lab environment, the Disaster Recovery Path listed in the tables point to
a shared folder on console.example.com, F:\dr_files.
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 Notepad,
to open the mail message file (*.eml) that will be written to the DR email
folder on the desktop of console.example.com.
Any time you need to re-save the catalog policy you must re-type the Password
for the DR Path or an authentication failure message is displayed.
13. Click OK to save the changes to the Disaster Recovery tab parameters.
The LAB13-catalog-to-master-tape policy is closed.
14. Verify that an entry for the LAB13-catalog-to-master-tape policy is displayed in the
All Policies pane of the Administration Console.
Continue to Exercise C-3: Performing manual NetBackup catalog backups.
Lab 13-56
Exercise C-3: Performing manual NetBackup catalog
backups
In the steps that follow, you initiate manual backups of the NetBackup catalogs using
the LAB13-catalog-to-master-tape policy, and monitor the results.
2. Initiate a manual backup using the LAB13-catalog-to-master-tape policy and the

WEEKLY-FULL schedule.
3. Access the Activity Monitor to view the backup jobs that occur as a result of the
manual backup request that used the LAB13-catalog-to-master-tape 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
Lab 13-57
4. Using Notepad++ or a pen and paper answer the questions listed in the table below.
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?
Q4: From the Status pane of the Detailed Status of the first child job, what was
the purpose of that job?
Q5: From the Job Details for the second child job, what was the purpose of the
second 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?
A3: Yes. The first job (lowest-numbered job) was the parent job to the other three
jobs. You can determine this by looking in the Job hierarchy tab of the Job
Details window for any of the jobs.
Q4: From the Status pane of the Detailed Status of the first child job, what was
the purpose of that job?
A4: It appears the job states the catalog backup to the staging folder, and validates
the contents of the staging folder.
Q5: From the Job Details for the second child job, what was the purpose of the
second catalog backup child job?
A5: It appears the job backs up a specific part of the NetBackup catalog
(DARS_DATA.db) to tape from the staging folder.
Q6: What does the third child catalog backup job do?
A6: It is unclear what portion of the NetBackup catalogs are backed up by this job
but it writes a backup image to tape.
6. Verify that all the Catalog Backup jobs run to successful completion.
Continue to Exercise C-4: Viewing the Disaster Recovery directory contents.
Lab 13-58
Exercise C-4: 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.
2. Double-click File Explorer shortcut on the desktop, and navigate to F:\dr_files.
3. Take note of the contents of the dr_files folder.
Currently, the directory contains two files. Both these files have the file name with
the format, [policy_name]_[ctimestamp}_[schedule type}.
Example: LAB13-catalog-to-master-tape_1515794398_FULL
• The file without the extension is known as the DR file.

• The second file is the DR package file that contains the security certificates for
the master server should the master server software ever need to be re-
installed. These files are created by the Catalog Backup job.
• The DR package file is new in NetBackup 8.1.
Lab 13-59
4. Using Notepad++ or a pen and paper, record the file name of the DR file that is
located in the dr_files directory.
You will need the name of the DR file in the next exercise.
The DR file is an ASCII text file that can be opened 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 master server.
5. Keep the File Explorer window open as you need to access it in the next exercise.
Continue to Exercise D: Recovering the catalogs using the NetBackup Catalog

Recovery wizard.
Lab 13-60
Exercise D: Recovering the catalogs using the
NetBackup Catalog Recovery wizard
In this exercise, you will 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.
Continue to Exercise D-1: Using the Catalog Recovery Wizard.
Lab 13-61
Exercise D-1: Using the Catalog Recovery Wizard
In the steps that follow, you use the NetBackup Catalog Recovery wizard to recover the
NetBackup catalogs.
2. From the File Explorer window right-click on the DR file (the file without the file
extension) then select Properties.
3. From the General tab of the Properties window, highlight the name of the file.
4. Right-click and select Copy.
5. Click Cancel to close the Properties window.
Lab 13-62
7. In the NetBackup Administration Console, click the NetBackup Management entry
in the left pane.
A list of NetBackup wizards is displayed in the right pane of the Administration

Console.
8. Click the Recover the Catalogs wizard entry.
The NetBackup Catalog Recovery Wizard window is displayed.
9. Click Next in the welcome screen of the wizard to continue.
Lab 13-63
10. Use the table below to fill in the path for the Specify the full pathname to the
disaster recovery file field, then press CTRL + v to paste the DR file name.
Master server name DR file path

winmaster.example.com \\console\dr_files\<DR_File_name>
lnxmaster.example.com /mnt/dr_recovery_files/<DR_files_name>
After typing the folder location (\\dr_files\), use the Paste function
(CTRL + v), to paste the DR filename (that you copied in a previous step – step
4), into the field.
The Retrieving Disaster Recovery File screen displays a message in the Action
Required pane, such as the message shown below.
Lab 13-64
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, contact your instructor.
12. Click Next on the Retrieving Disaster Recovery File screen to continue.
13. When the Disaster Recovery Method screen is displayed, accept the default entries
(to Recover 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.
14. 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.
15. After the catalog recovery is complete, click Next in the Recovering Catalog screen.
16. Click Finish to close the NetBackup Catalog Recovery Wizard.
17. Close the NetBackup Administration Console window.
After performing a catalog recovery, it is necessary to stop and start the

NetBackup services.
18. Click the appropriate link below, based on the master server you are using for this
lab activity.
• If your master server is winmaster.example.com, continue to Exercise D-2:

Stop/Restart NetBackup on the master server (winmaster).
• If your master server is lnxmaster.example.com, continue to Exercise D-3:
Stop/Restart NetBackup on the master server (lnxmaster).
Lab 13-65
Exercise D-2: Stop/Restart NetBackup on the master
server (winmaster)
To complete the catalog recovery of the NetBackup catalogs on the master server it is
necessary to stop and restart the NetBackup services on the master server.
1. Access the open RDP window to your Windows-based master server system,
2. Open a Command Prompt on winmaster.example.com.
3. In the Command Prompt, type the command to stop the NetBackup services on the
master server.
Command: bpdown –v –f
The –v is for verbose so that you can see the name of each process that is being
stopped. The –f is for force.
4. When the Command Prompt is returned, type the following command to verify that
all the NetBackup services have been shut down.
Command: bpps
5. When the Command Prompt is returned, type the following command to start all
the NetBackup services.
Command: bpup –v -f
all the NetBackup services have been started.
Command: bpps
7. Minimize the RDP window to winmaster.example.com.
Continue to Exercise D-4: Final recovery procedures.
Lab 13-66
Exercise D-3: Stop/Restart NetBackup on the master
server (lnxmaster)
To complete the catalog recovery of the NetBackup catalogs on the master server it is
necessary to stop and restart the NetBackup daemons on the master server.
1. Access the terminal (SSH) window that is open to your Linux-based master server,
2. In the Terminal window, type the following command to stop the NetBackup
daemons on the master server.
Command: netbackup stop
The –v is for verbose so that you can see the name of each process that is being
stopped. The –f is for force.
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.
4. When the Command Prompt is returned, type the following command to start the
NetBackup daemons.
Command: netbackup start
all the NetBackup daemons have been started.
Command: bpps -x
Lab 13-67
It has been observed in this virtualized lab environment, that after
recovering the NetBackup catalogs on the Linux-based master server,
lnxmaster.example.com, 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 master
server, and then perform a reboot of the lnxmaster.example.com system,
using the commands shown below.
̶ Command: netbackup stop

̶ Command: shutdown -r now
6. Minimize the Terminal window to lnxmaster.example.com.
Continue to Exercise D-4: Final recovery procedures.
Lab 13-68
Exercise D-4: Final recovery procedures
In the steps that follow, you initiate the NetBackup Administration Console on
console.example.com and verify the operation of the NetBackup environment and
perform a few final tasks as a follow-up to the recovery of the NetBackup catalogs.
1. Double-click the NetBackup 8.1 Administration Console shortcut, located on the

desktop of console.example.com.
2. When the NetBackup Administration Console log in screen is displayed, log in to

your master server using the information provided in the table below.

3. Briefly navigate through the various panes of the Administration Console to verify
that the NetBackup configuration is intact following the catalog recovery:
̶ Activity Monitor
̶ NetBackup Management > Policies
̶ NetBackup Management > Storage > Storage Units
̶ NetBackup Management > Storage > Storage Unit Groups
̶ NetBackup Management > Storage > Storage Lifecycle Policies
̶ Media and Device Management > Device Monitor
̶ Media and Device Management > Media
̶ Media and Device Management > Devices > Drives
̶ Media and Device Management > Devices > Robots
̶ Media and Device Management > Devices > Media Servers
̶ Media and Device Management > Devices > Disk Pools
̶ Media and Device Management > Credentials > Storage Servers
̶ Media and Device Management > Credentials > Virtual Machine Servers
4. Select Media in the left pane of the Administration Console.
Media and Device Management > Media
Lab 13-69
5. Click the Refresh icon in the tool bar to update the Volumes information that is
6. Scroll to the right in the Volumes pane to locate the Media Status column.
7. Click and drag the Media Status heading column so that it is to the right of the
Media ID heading column.
You can also right-click in the white area of the right pane and select Columns >
Layout. Locate and click the Media Status column. Use the Move Up button to
move the Media Status column just below Media ID. Click OK to keep the changes.
8. Identify any Media ID that has the Media Status of Frozen.
9. Take note of the Volume Pool of which the Frozen Media ID is a member.
The tape that was used to perform the Catalog Recovery operation was frozen
to prevent the over-write of the catalog backup images that reside on the tape
(that Media ID is a member of the CatalogBackup volume pool).
10. Right-click the entry for the Frozen Media ID and, in the menu that is displayed, click
Unfreeze.
11. When the Unfreeze dialog box is displayed, click OK to unfreeze the tape.
12. Verify that the Media Status of the tape is changed to Active.
13. On console.example.com, logout of the Windows-based master server,

winmaster.example.com, to close the RDP window, or close the Terminal (SSH)
window that is connected to lnxmaster.example.com.
Continue to Exercise D-5: Deactivating NetBackup policies.
Lab 13-70
Exercise D-5: Deactivating policies
In the steps that follow, you deactivate NetBackup policies that were created and used
in previous 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.
2. Deactivate the PRE-clients-to-master-bdisk policy.
a. Select the Policies entry in the left pane of the Administration Console window.
b. Locate and right-click the PRE-clients-to-master-bdisk policy entry.
c. Click Deactivate in the menu.
d. Verify that the PRE-clients-to-master-bdisk policy has been de-activated.
3. Deactivate the LAB13-catalog-to-master-tape policy.
4. Verify that the LAB13-catalog-to-master-tape policy is de-activated.
5. Close the NetBackup Administration Console window on console.example.com.
Lab 13-71
Lab 14: Optimizing File System Backups
In this lab, you perform tasks to optimize NetBackup 8.1 file system backup
performance using NetBackup Accelerator, multiple data streams, and multiplexed
backups.
Proceed to Exercise A: Optimizing backups using the NetBackup Accelerator.
Lab 14-1
Exercise A: 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.
Continue to Exercise A-1: Configuring a policy for NetBackup Accelerator.
Lab 14-2
Exercise A-1: Configuring a policy for NetBackup
Accelerator
In the steps that follow you configure a policy that will be used first to observe the
performance of a backup job that does not use the Accelerator feature. Then you will
modify the policy to enable the Accelerator feature, and run backup jobs to observe the
results.
3. Copy the PRE-clients-to-master-msdp policy to LAB14-test-accelerator using the

detailed steps in the following table.
Step # Step details

1 Right-click the entry for the PRE-clients-to-master-msdp policy.
2 In the resulting menu, click the Copy to New… entry.
3 Type the name of the new policy, LAB14-test-accelerator in the New
policy field of the Copy a Policy window.
4 Click OK to create the new policy, and to close the Copy a Policy
window.
The new policy, LAB14-test-accelerator, is opened for editing in the Change

Policy window.
Lab 14-3
4. Modify the LAB14-test-accelerator using the information provided in the table
below.
Policy tab / Parameter Parameter value / setting

Attributes tab
Use Accelerator (check box) Not selected at this time
Keyword phrase: ACCELERATOR (change this setting)
All other policy Attributes: No changes
Schedules tab
FULL schedule No changes to this schedule
Clients tab (Windows-based master server)
winmaster.example.com Delete the entry for this client.
winmedia.example.com No changes to this client entry
Clients tab (Linux-based master server)
lnxmaster.example.com Delete the entry for this client.
lnxmedia.example.com No changes to this client entry
Backup Selections tab (Windows-based master server)
E:\data E:\data\ (no change)
Backup Selections tab (Linux-based master server)
/data /data (no change)
5. After making the changes to the LAB14-test-accelerator policy, click OK to save the
policy, and to close the Change Policy window.
6. Verify that the LAB14-test-accelerator policy is included in the list of policies that is
displayed in the All Policies pane of the Administration Console.
Continue to Exercise A-2: Performing a non-Accelerator backup of the client.
Lab 14-4
Exercise A-2: Performing a non-Accelerator backup of the
client
In the steps that follow, you use the new LAB14-test-accelerator policy to perform a full
backup of the client, winmedia.example.com or lnxmedia.example.com.
1. Perform a Full Backup of your media server using the LAB14-test-accelerator policy
and the detailed steps described in the following table.
Step # Step details

1 Click the entry for the LAB14-test-accelerator policy, located in the
4 Make no changes/selections in the Manual Backup window.
Click OK to initiate the backup operation.
2. After initiating the backup job, select the Activity Monitor entry in the left pane of
3. Locate the job for the most recent Backup job that used the LAB14-test-accelerator
policy.
NOTE: It has been observed intermittently that backups written may run more slowly
than expected. This may be due to conditions such as high usage of the lab kits in the
lab delivery environment. If you encounter slow backups do not be alarmed, as the
backup jobs will run to successful completion. Please be patient.
4. Monitor the progress of the Backup job until it runs to completion.
5. Verify that the Backup job completes successfully (status 0).
If the job fails, record the status code and seek assistance.
Lab 14-5
6. Access the Job Details for the backup job, and view the contents of the Detailed
Status tab, taking note of the information shown in the table below.
Number of files backed up: Windows: 11134 files

Linux: 11135 files
Current Kilobytes Written: Windows: 825174 Kbytes
Linux: 819552 Kbytes
Backup ID created Elapsed time may vary (approximately 50 seconds)
Continue to Exercise A-3: Enabling NetBackup Accelerator in a policy.
Lab 14-6
Exercise A-3: Enabling NetBackup Accelerator in a policy
In the steps that follow, you modify a policy to enable the NetBackup Accelerator
feature.

2. Navigate to NetBackup Management and then select Policies in the left pane of the
3. Locate and double-click the entry for the LAB14-test-accelerator policy, to open the
policy for editing.
4. In the policy Attributes tab, click the Use Accelerator check box, to enable the
Accelerator feature.
Make no other changes to the policy.
5. Click OK to save the policy changes, and to close the Change Policy window.
Continue to Exercise A-4: Performing and monitoring Accelerator-enabled backups.
Lab 14-7
Exercise A-4: Performing and monitoring Accelerator-
enabled backups
In the steps that follow, you initiate a manual backup of the client,
winmedia.example.com or lnxmedia.example.com using the LAB14-test-accelerator
policy. This backup uses the NetBackup Accelerator feature.
1. Click the entry for the LAB14-test-accelerator policy, located in the All Policies pane
Actions > Manual
3. Click OK in the Manual Backup window, without making any other selections, to
initiate the manual backup operation.
5. Locate the entry for the most recent Backup job that used the LAB14-test-
accelerator policy.
6. Monitor the Backup job, and verify that it runs to successful completion (status 0).
7. Double-click the entry for the Backup job to open the Job Details window.
8. Access the Detailed Status tab for the job, and view the contents of the Status pane.
Lab 14-8
9. Locate the entries in the Detailed Status pane that contain:
Info bpbrm (pid=3066) accelerator enabled
Info bpbrm (pid=3066) There is no complete backup image

match with track journal, a regular full backup will be
performed
Because 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.
10. Close the Job Details window for the Backup job.
11. Scroll to the right in the Activity Monitor, to locate the Accelerator Optimization
column for the Backup job.
12. Take note the Accelerator Optimization percentage for the job.
The first Accelerator-enabled backup of the client using the policy will achieve
an Accelerator Optimization of zero percent. This is expected.
Continue to Exercise A-5: Performing a second Accelerator-enabled backup.
Lab 14-9
Exercise A-5: Performing a second Accelerator-enabled
backup
2. Initiate a manual Full Backup of the media server client using the LAB14-test-
accelerator policy using the detailed steps provided in the following table.
Step # Step details

1 Click the entry for the LAB14-test-accelerator policy, located in the
4 Make no changes/selections in the Manual Backup window.
Click OK to initiate the backup operation.
4. Locate the entry for the most recent Backup job that used the LAB14-test-
accelerator policy.
5. Monitor the Backup job, and verify that the job runs to successful completion.
6. Scroll to the right in the Activity Monitor, to locate the Accelerator Optimization
column for this Backup job.
7. Take note of the Accelerator Optimization percentage for the second job.
The second Accelerator-enabled backup of the client using the policy will
achieve an Accelerator Optimization of 100% percent. This is expected.
Lab 14-10
8. Double-click the entry for the Backup job to open the Job Details window.
9. Select the Detailed Status tab.
10. Scroll through the contents of the Status pane, and locate the entry that is similar to
the one shown below.
Info bpbkar (pid=xxxxx) accelerator sent xxxxx bytes out

of xxxxxxxxxxxx bytes to server, optimization 100.0%
11. Take note of the number of bytes sent by the accelerator, as described in the
previous message in the Status pane.
12. Compare the Current Kilobytes Written and the number of bytes sent by the
accelerator from the client to the NetBackup media server.
The number of Current Kilobytes Written far exceeds the number of bytes sent (as
indicated in the Status pane of the Detailed Status)Linu 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.
Because no changes were made to the files in client file system 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 client file system. Had files been changed on the
client, the amount of data transferred would have been greater, but still less
than would have been transferred during a full, non-accelerator backup
operation.
13. Close the open Job Details window.
Continue to Exercise A-6: Viewing the Accelerator-enabled backup image contents.
Lab 14-11
Exercise A-6: Viewing the Accelerator-enabled backup
image contents
As a final step in this exercise, you use the Backup, Archive, and Restore (BAR) user
interface to view the contents of the second Accelerator-enabled backup image for the
client.
1. Click the Backup, Archive, and Restore entry in the left pane of the Administration
Console.
2. Select the Restore Files tab of the BAR user interface.
The settings used for the most recent restore job (performed using the BAR user
interface) are visible in the Restore Files tab.
3. Click Actions and then select Specify NetBackup Machines and Policy Type.
4. Verify the Specify NetBackup Machines and Policy Type settings, based upon the
operating system of your master server as shown in the tables below.
If your master server is Windows-based, refer to the following table.

Source client for restores: winmedia.example.com
Destination client for restores: winmedia.example.com
If your master server is Linux-based, refer to the following table.

Server to use for backups and restores: lnxmaster.example.com
Source client for restores: lnxmedia.example.com
Destination client for restores: lnxmedia.example.com
Policy Type for restores: Standard
Lab 14-12
5. After verifying the Specify NetBackup Machines and Policy Type settings, click OK to
close the window.
6. If you receive a dialog box titled No Files Found, click OK and continue to the next
step.
7. Set the Restore type field (in the Restore Files tab) to a value of Normal Backups.
8. Set the Keyword phrase to ACCELERATOR
You can also select Actions and then select Set Keyword.
It may be necessary to change the Browse directory to “/” (no quotes) in order
for contents of a backup image to be displayed in the Directory Structure pane.
9. Select Actions and then select Set Date Range and then select Backup History. The
Backup History window is displayed.
10. In the Backup History window select the entry for the most recently created backup
image that was created using the LAB14-test-accelerator policy, as shown below.
11. Take 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.
12. After selecting the backup image, click OK to close the Backup History window.
Lab 14-13
13. Expand the entries in the Directory Structure pane of the BAR user interface, until
the data folder or directory is displayed.
14. Click the entry for the data directory, located in the Directory Structure pane of the
BAR user interface.
The Contents of selected directory pane displays the contents of the data
folder that are present in the selected backup image.
15. Note that the Contents of the selected 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.
Proceed to Exercise B: Configuring and using multiple data streams.
Lab 14-14
Exercise B: 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.
It should not be presumed that the use of the NetBackup multiple data streams
feature will always result in improved backup performance when performing
client file system backups. Planning and testing of the performance benefits is
required based upon the disk layout on the client systems.
Continue to Exercise B-1: Accessing your master server.
Lab 14-15
Exercise B-1: Accessing your master server
future activities. To make more tapes available for use, you will log into your master
server and expire tapes so that the scratch_tapes pool will contain enough media for
this lab exercise.

winmaster.example.com, or access a command prompt on your Linux-based master
either of two ways:
• By selecting the ‘tab’ that is provided for the system that is provided on the user
interface in your lab delivery environment (VMware Workstation, Nimbus,
Hatsize), or
• By access the system remotely from the console.example.com system in your
lab kit. The Remote System Access folder on the desktop of
console.example.com provides access to Windows-based systems using Remote
Desktop (RDP), and to Linux-based systems using PuTTY.
Either of the methods listed above is acceptable for accessing your master server
system.
2. If you are already familiar with the methods to access the desktop of your master
server, click the link to continue to Exercise B-4: Preparing the client to test multiple
data streams.
To see the details for opening a PuTTY session to lnxmaster.example.com, or an RDP

session to winmaster.example.com, click the appropriate link below.
• To open a PuTTY session to lnxmaster.example.com, go to Exercise B-2:

Opening a terminal window (SSH) to lnxmaster.example.com using PuTTY.
• To open an RDP session to winmaster.example.com, go to Exercise B-3:
Opening an RDP session to winmaster.example.com.
Lab 14-16
Exercise B-2: Opening a terminal window (SSH) to
lnxmaster.example.com using PuTTY


4. Double-click the PuTTY shortcut that is located in the REMOTE SYSTEM ACCESS
folder.
Continue to Exercise B-4: Preparing the client to test multiple data streams.
Lab 14-17
Exercise B-3: Opening an RDP session to
To connect to remote Windows-based lab systems from console.example.com using

Remote Desktop (RDP), follow the steps below.


Continue to Exercise B-4: Preparing the Windows client to test multiple data
streams.
Lab 14-18
Exercise B-4: Preparing the client to test multiple data
streams
future activities. In the steps that follow you will expire all the images on three (3) tapes
to return those tapes to the scratch_tapes volume pool, making them available for use.



3. In the Command Prompt or terminal window, type the NetBackup-provided

command available_media, and press Enter.
4. Record the Media IDs and status of any tapes that are assigned to the server_tapes
volume pool using pencil and paper or the Notepad++ application on the desktop.
These would be the tapes with a status other than AVAILABLE, as displayed in the
output of the available_media command.
The number of tapes that are assigned to the server_tapes volume pool may vary
from the results observed by others.
Lab 14-19
5. For each Media ID you identified, execute the bpexpdate command, using the
command syntax shown below.
The command that follows will expire all images on the tape, and to return the tape
to the AVAILABLE status.
6. Repeat the bpexpdate command for each Media ID that you identified.

8. If necessary, repeat the use of the bpexpdate command until all Media IDs of
tapes in the server_tapes volume pool have become un-assigned (AVAILABLE).
Do not continue to the next step until you have confirmed that all Media IDs of
tapes in the server_tapes volume pool have become un-assigned (AVAILABLE).
9. Allow the RDP connection (Windows) or your PuTTY session (Linux) to your master
server to remain open.
You use this window in this exercise.
Lab 14-20
10. Access the desktop of your Windows-based media server, winmedia.example.com,
or a command prompt on your Linux-based media server, lnxmedia.example.com.
either of two ways:
i. By selecting the ‘tab’ that is provided for the system that is provided on the
user interface in your lab delivery environment (VMware Workstation,
Nimbus, Hatsize), or
ii. By access the system remotely from the console.example.com system in
your lab kit. The Remote System Access folder on the desktop of
console.example.com provides access to Windows-based systems using
Remote Desktop (RDP), and to Linux-based systems using PuTTY.
Either of the methods listed above is acceptable for accessing your master server
system.
11. If you are already familiar with the methods to access the desktop of your master
server, click the link to continue to Exercise B-7: Preparing the client to test multiple
data streams.
To see the details for opening a PuTTY session to lnxmedia.example.com, or an RDP

session to winmedia.example.com, click the appropriate link below.
• To open a PuTTY session to lnxmedia.example.com, go to Exercise B-5: Opening

a terminal window (SSH) to lnxmedia.example.com using PuTTY.
• To open an RDP session to winmedia.example.com, go to Exercise B-6: Opening
an RDP session to winmedia.example.com.
Lab 14-21
Exercise B-5: opening a terminal window (SSH) to
lnxmedia.example.com using PuTTY


4. Double-click the PuTTY shortcut that is located in the REMOTE SYSTEM ACCESS
folder.
Continue to Exercise B-7: Preparing the client to test multiple data streams.
Lab 14-22
Exercise B-6: Opening an RDP session to
To connect to remote Windows-based lab systems from the console system

(console.example.com) using Remote Desktop (RDP) follow the steps below.


Continue to Exercise B-7: Preparing the Windows client to test multiple data
streams.
Lab 14-23
Exercise B-7: Preparing the client to test multiple data
streams
In this exercise, your media server system will serve as the client that will be backed up
using the multiple data streams feature.
1. Log in to your media server system, winmedia.example.com or

lnxmedia.example.com, (if required) using the username/password combination
specified in the table below.

winmedia.example.com EXAMPLE\Administrator train
lnxmedia.example.com root train
2. View the drives (names/letters) or file systems/mount points that have been
configured on your media server, using the appropriate method, as described in the
tables below.
The following table provides details for viewing configured disk volumes on the
Windows-based media server, winmedia.example.com.
# Step details
1 Click File Explorer icon on the Windows’ task bar on winmedia.example.com.
A File Explorer window is opened.
2 Take note of the configured drives on the media server system.
The following table provides details for viewing configured file systems and mount
points on the Linux-based media server, lnxmedia.example.com.
# Step details
1 Access the open Terminal window on lnxmedia.example.com.
2 In the Terminal window, execute the command: df -h
3 Take note of the configured file systems and their associated mount points on
the lnxmedia.example.com system.
Continue to Exercise B-8: Copying data to use for testing the multiple data streams
feature.
Lab 14-24
Exercise B-8: Copying data to use for testing the multiple
data streams feature
In the steps that follow, you copy the data folder or directory on the media server to
additional drive and folder or directory locations on the media server, in preparation for
testing the NetBackup multiple data streams feature.
1. Copy the data folder or directory on the media server to an additional drive or file
system locations on the media server using the steps provided in the tables below.
̶ The following table provides the detailed steps to perform on the Windows-
based media server, winmedia.example.com.
̶ The table on the next page provides the detailed steps to perform on the
Linux-based media server, lnxmedia.example.com. Click the link to go to that
table.
# Step details and information – for winmedia.example.com

1 Access the open File Explorer window on winmedia.example.com.
2 Double-click to open the DATA (E:) drive in the File Explorer.
The contents of the E:\ drive are displayed.
3 Right click on the data folder, and select Copy.
4 Double-click to open the Local Disk (C:) drive in the File Explorer.
5 Right-click, and select Paste to copy the data folder to C:\
The C:\data folder is created.
6 Click to open the C:\Temp folder in the File Explorer window.
7 Right click and select Paste to copy the data folder to C:\Temp
The C:\Temp\data folder is created.
You now have the same data in three different locations: C:\, E:\ and
C:Temp\
8 Close the File Explorer window on winmedia.example.com.
Lab 14-25
The following table provides the detailed steps to perform on the Linux-based media
server, lnxmedia.example.com.
# Step details and information

1 Access an open Terminal window on lnxmedia.example.com.
2 Verify the contents of /data. Command: ls –l /data
3 Copy /data to /data2: Command: cp –r /data /data2
4 Verify the contents of /data2. Command: ls –l /data2
5 Copy /data2 to /data3: Command: cp –r /data2 /data3
6 Verify the contents of /data3. Command: ls –l /data3
The same data resides in three different directories: /data, /data2, and
/data3.
7 Close the Terminal window on lnxmedia.example.com.
In a production environment it is recommended that each stream of data being

backed from a client be from different file systems. However, in this lab
environment, we are backing up three directories that reside on two file
systems.
Continue to Exercise B-9: Configuring a policy to use multiple data streams.
Lab 14-26
Exercise B-9: Configuring a policy to use multiple data
streams
In the steps that follow you configure a policy to use the NetBackup multiple data
streams feature.

If no NetBackup Administration Console window is currently open, double-

click the NetBackup 8.1 Admin shortcut on the desktop of
console.example.com, and then login to your master server using the
username/password combination, Administrator/train (Windows) or
root/train (Linux).
4. Copy the PRE-clients-to-master-tape policy to create a new policy using the

instructions listed below.
Give the new policy the name LAB14-test-multiple-data-streams. The following

table provides the detailed steps to perform this task.
# Step details and information

1 Click the entry for the PRE-clients-to-master-tape policy in the All Policies
2 Select Actions > Copy to New.
3 In the Copy a Policy window, type the name of the new policy in the New
policy field, LAB14-test-multiple-data-streams, and click OK.
The Change Policy window is displayed, and enables you to modify the newly
created policy
Lab 14-27
5. Modify the LAB14-test-multiple-data-streams policy Attributes using the parameter
settings provided in the table below.
Attribute tab parameter Parameter value /setting

Allow Multiple Data Streams: selected (mark this check box)
All other Attribute settings: Do not change
6. From the Schedules tab select the full schedule then click Change
7. Select the Start Window then click Clear.
8. Click OK to save the full schedule.
9. Click the Clients tab.
10. Modify the contents of the Clients tab using the information provided in the table
below.
Use the entries that are appropriate for your lab environment – either for
Windows or for Linux - based upon the operating system of your master server.
Clients tab entries (on Windows) Parameter value /setting

winmaster.example.com Delete the entry for this client
winmedia.example.com Do not change this entry.
Clients tab entries (on Linux) Parameter value /setting
lnxmaster.example.com Delete the entry for this client
lnxmedia.example.com Do not change this entry.
11. After making the changes to the Clients tab, click the Backup Selections tab.
12. Modify the contents of the Backup Selections tab of the policy to add two new
entries, using the information provided in the table below.
Use the entries in the table that are appropriate to your lab environment –
either for Windows or Linux.
Backup Selection entries (Windows) Backup Selection entries (Linux)

E:\data\smallfiles (change) /data/smallfiles (change)
C:\data\smallfiles (add) /data2/smallfiles (add)
C:\Temp\data\smallfiles (add) /data3/smallfiles (add)
Lab 14-28
13. After making the changes to the Backup Selections of the policy, click OK to save the
policy and to close the Change Policy window.
14. Verify that the LAB14-test-multiple-data-streams policy is visible in the All Policies
Given the configuration of the LAB14-test-multiple-streams policy, and the disk

drives or file systems on the client system (your media server), three streams of
backup data will be generated from the client based upon the Backup Selections of
the policy, and the fact that the Allow multiple data streams policy Attribute is set.
If the Allow Multiple Data Streams policy attribute is selected, the number of
backup streams used to back up a client that is included in the policy is
determined by the makeup of the Backup Selections of the policy.
Continue to Exercise B-10: Performing a multiple data streams backup.
Lab 14-29
Exercise B-10: Performing a multiple data streams backup
In the steps that follow, you perform a manual backup of a client using the LAB14-test-
multiple-data-streams policy, and monitor the results of that backup operation.
2. Initiate a manual Full Backup operation of your media server system using the
LAB14-test-multiple-data-streams policy using the steps in the table below.
Step # Step details

2 Click the entry for the policy (LAB14-test-multiple-data-streams),
located in the All Policies pane.
4 In the Manual Backup window click OK to initiate the backup.
Continue to Exercise B-11: Monitoring the resulting backup jobs.
Lab 14-30
Exercise B-11: Monitoring the resulting backup jobs
Console, and take note of the most recent Backup job entries added to the Jobs list.
Four Backup jobs were added as a result of the manual backup operation. One
parent job was generated - which controlled each of the three child jobs. Each
of the child jobs was used to back up one stream of data generated by the
client.
2. Locate and double-click the entry for the lowest-numbered of the four jobs that
were initiated, to open the Job Details for the job.
Actions > Details
3. Note the contents of the File List pane that is displayed on the Job Overview tab of
the Job Details.
The File List pane contains three entries.
Files List for Windows-based client Files List for Linux-based client
E:\data\smallfiles /data/smallfiles
C:\data\smallfiles /data2/smallfiles
C:\Temp\data\smallfiles /data3/smallfiles
4. Click the Job Hierarchy tab in the Job Details window, and note the contents of that
tab.
The Job Hierarchy tab shows that the lowest-numbered job is a parent job to
the other three jobs.
5. Take note of the Job IDs for parent job and the three child jobs, as indicated in the
Job Hierarchy tab of the parent job.
6. Close the Job Details window for the parent Job ID.
7. Double-click the entry for the Job ID of the first child job to open the Job Details for
the job.
Lab 14-31
8. Note the contents of the Files List for the first child job as shown in the table below.
Child job Windows-based client Linux-based client

job #1 – E:\data\smallfiles /data/smallfiles
Files List:
9. Click the UP arrow button located near the bottom of the Job Details window to
view the Job Details for the second child job.
10. Note the contents of the Files List for the second child job as shown in the table
below.

job #2 – C:\data\smallfiles /data2/smallfiles
Files List:
11. Click the UP arrow button to view the Job Details for the third child job.
12. Take note of the contents of the Files List for the third child job as shown in the
table below.

job #3 – C:\Temp\data\smallfiles /data3/smallfiles
Files List:
13. Close the Job Details window for the third child job.
Lab 14-32
14. Observe the jobs and the behavior of the multiple stream backup, and answer the
question below.
Question: Based on your observations of the LAB14-test-multiple-data-streams

policy and the backup jobs that were performed as a result of the manual backup
that used the LAB14-test-multiple-data-streams policy, what is the relationship
between the contents of the Backup Selections of the policy and the jobs that are
run to backup up a client using that policy, if the Allow multiple data streams policy
attribute is enabled?
Answers and observations:
• If the Allow multiple data streams policy attribute is selected, the contents of
the Backup Selections tab of the policy determines the number of data streams
that will be used to back up each of the clients listed in the policy. NetBackup will
initiate one backup job for each backup selection list item plus an additional job
that serves as a parent job to control the child jobs for each client.
• The parent job does not back up any client data. It is the first job to start and
exits after the last of the child jobs has completed.
• If multiple clients are backed up using the policy, there will be multiple jobs
(parent job + child jobs) for each client that is backed up.
Continue to Exercise B-12: Examining factors that impact job concurrency.
Lab 14-33
Exercise B-12: Examining factors that impact job
concurrency
In the steps that follow, you initiate a second manual backup of the client, and observe
characteristics relating to job concurrency. Then, you examine various NetBackup
settings that impact the number of jobs that can be active simultaneously.
1. Perform a second manual Full Backup of the media server client using the LAB14-
test-multiple-data-streams policy.
2. Immediately after initiating the manual backup, select the Activity Monitor entry in
the left pane of the Administration Console window.
3. Pay close attention to the Job State column contents for the new backup jobs in the
Activity Monitor.
4. 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 Details for the jobs that are in the Queued jobs 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.
5. Allow all the backup jobs to run to successful completion.
If one or more of the backup jobs fail, record the failure status and seek assistance.
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.
Continue to Exercise B-13: Factors that impact job concurrency – Maximum jobs per
client.
Lab 14-34
Exercise B-13: Factors that impact job concurrency –
Maximum jobs per client
In the steps that follow you examine one factor that impacts whether backup jobs from
a client run concurrently – the master server Host Property, Maximum jobs per client.
1. Select NetBackup Management and the select Host Properties, Master Servers in
the left pane of the NetBackup Administration Console window.
The master server host name (winmaster.example.com or lnxmaster.example.com)

is displayed in the right pane of the Administration Console.
2. Click the entry for the master server in the right pane of the Administration Console.
3. Select Actions and then select Properties.
The Master Server Properties window is displayed.
4. Click the Global Attributes entry in the left pane of the Master Server Properties.
The Global Attributes for the selected master server are displayed in the right pane
5. Record the current setting of the Maximum jobs per client parameter using pencil
and paper or the Notepad++ application located on the desktop.
6. Change the value of the Maximum jobs per client parameter to “3”, and record the
new parameter setting using pencil and paper or Notepad++.
7. Click the Apply button to apply the change.
9. When the Restart Daemons dialog box is displayed, click OK to acknowledge the
message, and to close the dialog box.
A restart of the NetBackup daemons is not required to implement this

parameter change.
Continue to Exercise B-14: Testing the Maximum jobs per client parameter change.
Lab 14-35
Exercise B-14: Testing the Maximum jobs per client
parameter change
In the steps that follow, you initiate another manual backup request using the LAB14-
test-multiple-data-streams policy, to test and observe the results of changing the
Maximum jobs per client parameter setting.
1. Perform a third manual Full Backup of the media server client using the LAB14-test-
multiple-data-streams policy.
3. 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 parameter 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 parameter 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.
4. Allow all the backup jobs to run to successful completion. Then, proceed to the next
step.
If one or more of the backup jobs fail, record the failure status and seek assistance.
In the previous steps, you observed that changing the Maximum jobs per client
Global Attribute setting allowed two child jobs from the client to run
concurrently. You may have expected all three child jobs to run concurrently.
Continue to Exercise B-15: Factors that impact job concurrency – Storage unit
configuration.
Lab 14-36
Exercise B-15: Factors that impact job concurrency –
Storage unit configuration
In the steps that follow, you investigate another aspect of NetBackup configuration that
can determine whether backup jobs run concurrently – the configuration of the storage
unit to which the backup jobs sends the backup image data.
1. Examine the job entries for the most recent backup jobs that used the LAB14-test-
Note that the master_tape_stu storage unit was used to write the backup images for
the backup jobs.
The LAB14-test-multiple-data-streams policy writes backup images to tape

drives that are included in the master_tape_stu storage unit.
The right pane of the Administration Console displays the configured storage units.
unit for editing.
The master_tape_stu is opened for editing in the Change Storage Unit window.
Lab 14-37
4. Note the storage unit parameter settings for the master_tape_stu as shown in the
table below.

Maximum concurrent write drives: 2
Enable multiplexing: Not selected (default)
Maximum streams per drive: Not selectable if Enable Multiplexing
is not selected. (default)
Because there are two tape drives in the master_tape_stu, and because
multiplexing is not enabled for the storage unit, the maximum number of
concurrently Active backup jobs for the storage unit is two (2).
If the backups were being written to a disk storage unit (BasicDisk,

AdvancedDisk, or MSDP) the Maximum concurrent jobs parameter of the disk
storage unit would limit the number of concurrent backup jobs that could be
written to the storage unit.
5. Click Cancel to close the Change Storage Unit window, without making any changes
to the master_tape_stu settings.
Continue to Exercise B-16: Modifying policy Backup Selections to affect backup

streams.
Lab 14-38
Exercise B-16: Modifying policy Backup Selections to
affect backup streams
In the steps that follow, you use NEW_STREAM entries in the Backup Selections of a
policy to change the number of backup streams that are generated from the client
during a backup operation.
2. Double-click the entry for the LAB14-test-multiple-data-streams policy, to open the

policy for editing.
3. Modify the contents of the Backup Selections tab to add the NEW_STREAM
directive using the instructions in the table below.
The figure below illustrates the Backup Selections for a Windows-based client after
adding the NEW_STREAMS entries.
The figure below illustrates the Backup Selections for a Linux-based client after
adding the NEW_STREAMS entries.
Add one NEW_STREAM directive entry at the top of the Backup Selections list,
and another NEW_STREAM directive entry between the
E:\data\smallfiles and C:\data\smallfiles on Windows, or
between the /data/smallfiles and /data2/smallfiles entries on
Linux.
Lab 14-39
The detailed steps to perform this task are described below.
# Step description
1 Click the entry E:\data\smallfiles or /data/smallfiles.
2 Click the Insert button.
3 In the Insert Backup Selection window, select the drop-down arrow for
the Pathname or directive field.
4 In the drop-down list, click NEW_STREAM.
5 Click OK in the Insert Backup Selection window
6 Click the entry C\data\smallfiles or /data2/smallfiles.
7 Click the Insert button (in the Backup Selections tab).
8 In the Insert Backup Selection window, select the drop-down arrow for
the Pathname or directive field.
9 In the drop-down list, click NEW_STREAM.
10 Click OK in the Insert Backup Selection window
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.
Continue to Exercise B-17: Performing a manual backup to test the NEW_STREAM

directive.
Lab 14-40
Exercise B-17: Performing a manual backup to test the
NEW_STREAM directive
In the steps that follow, you initiate a manual full backup of the client, using the LAB14-
test-multiple-data-streams policy, to observe the impact of the use of the
NEW_STREAM directive.
1. Initiate a manual full backup of the media server client using the LAB14-test-
the left pane of the Administration Console window and note the following.
• Three backup jobs were initiated as a result of the manual backup request, a
parent job, and two child jobs.
• All the backup jobs run concurrently, because we have previously set the
Maximum jobs per client to a higher value (3), and that there are two tape
drives available in the destination storage unit.
The first child job Files List is shown below.
Windows: E:\data\smallfiles
Linux: /data/smallfiles
The second child job Files List is shown below.
Windows: C:\Temp\data\smallfiles and C:\data\smallfiles
Linux: /data2/smallfiles and /data3/smallfiles
- Required Exercises
The remaining exercise in this lab activity is optional. Continue to the optional exercise,
based on your interest in the NetBackup multiplexing backup images to tape feature.
Proceed to Exercise C: (Optional) Configuring and performing multiplexed backups.
Lab 14-41
Exercise C: (Optional) Configuring and performing
multiplexed backups
In this optional exercise, you configure NetBackup to perform multiplexed backups to a

media manager (tape) storage unit.
Multiplexed backups can provide a significant performance benefit for backups

that are written to tape storage. Multiplexing can be beneficial when the
performance characteristics of the tape hardware (tape drives) are significantly
faster than the speed at which the data from a single client stream can be read
and delivered to the tape drive.
When using multiplexing, NetBackup interleaves the backup images from

multiple streams of data onto the tape, thereby allowing the tape drive to
operate at optimum efficiency.
Testing is required to determine the number of multiplexed backup images that

are required to optimize the performance of your tape hardware.
Proceed to Exercise C-1: Preparing to perform a non-multiplexed manual backup.
Lab 14-42
Exercise C-1: Preparing to perform a non-multiplexed
manual backup
In the steps that follow, you modify a policy to perform non-multiplexed backups.

The list of policies is displayed in the All Policies pane of the Administration Console.
3. Double-click the entry for the LAB14-test-multiple-data-streams policy, to open the

policy for editing.
The policy is opened for editing in the Change Policy window.
5. In the Backup Selections tab, remove (delete) the NEW_STREAM entries, so that the
resulting Backup Selections entries appear as illustrated in the following table.
Windows-based client Linux-based client

winmedia.example.com lnxmedia.example.com
E:\data\smallfiles /data/smallfiles
C:\data\smallfiles /data2/smallfiles
C:\Temp\data\smallfiles /data3/smallfiles
6. After making the changes to the Backup Selections of the policy, click OK to save the
policy, and to close the Change Policy window.
Continue to Exercise C-2: Performing a non-multiplexed manual backup.
Lab 14-43
Exercise C-2: Performing a non-multiplexed manual
backup
In the steps that follow, you use the LAB14-test-multiple-data-streams policy to initiate
a backup operation.
3. Take note of the information for the backup jobs as listed below.
The Activity Monitor Jobs tab appears immediately after the manual backup request is
submitted as shown below.
Four Backup jobs were initiated as a result of the manual backup request – one
parent job, and three child jobs.
Three jobs are Active concurrently (simultaneously). The parent job and the first two
child jobs went Active immediately.
The third and final child job were initially in the Queued state until the first of the
child jobs was completed, and then the third child job went Active.
You can also use the hierarchical view option in the Activity Monitor to view
the parent and child jobs.
4. Verify that all backup jobs run to successful completion before continuing.
If one or more of the backup jobs fail, record the status code and seek assistance.
Lab 14-44
5. Open the Job Details for each of the child jobs, one-at-a-time, selecting the Detailed
Status tab for each job, and then view the Status pane.
The Status pane identifies the Media ID of the tape that was mounted to perform
the backup job, the Drive Index for the tape drive on which the tape was mounted,
and the file number on the tape where the backup image was recorded.
The following illustration provides an example of the information that is provided in

the Status pane of Detailed Status tab for a job.
6. Record the Media ID, Drive Index number, and file number for each of the three
child backup jobs using paper and pencil or the Notepad++ application located on
the desktop.
The three child backup jobs performed were not multiplexed onto the same
tape. The backup image for the first child job was written to a Media ID
mounted on one tape drive, and the backup image for the second child job was
written to a different Media ID that was mounted on the other tape drive in the
storage unit. When the first child job completed, the backup image for the third
child backup job was written onto the same tape as the backup image for the
first child job, but was written to the next, sequentially-higher file number on
the tape.
7. Close the Job Details window.
Continue to Exercise C-3: Enabling multiplexed backups in the storage unit.
Lab 14-45
Exercise C-3: Enabling multiplexed backups in the storage
unit
In the steps that follow, you configure NetBackup to enable multiplexed backups for a
Media Manager (tape) storage unit.
The right pane of the Administration Console displays the list of configured storage
units.
unit for editing.
3. Click the Enable multiplexing check box, to enable the multiplexing feature.
4. Verify that the Enable multiplexing check box is marked.
5. Change the Maximum streams per drive setting to a value of “2”.
6. Click OK to save the changes to the master_tape_stu storage unit, and to close the
Change Storage Unit window.
You have enabled multiplexed backups for the master_tape_stu storage unit.
Continue to Exercise C-4: Enabling multiplexed backups in the policy schedule.
Lab 14-46
Exercise C-4: Enabling multiplexed backups in the policy
schedule
In addition to enabling multiplexing in the Media Manager storage unit, you must also
enable multiplexing in the schedules of policies that you wish to use to control
multiplexed backups.
2. Double-click the entry for the LAB14-test-multiple-data-streams policy in the All

Polices pane, to open the policy for editing.
3. Click the Schedules tab of the policy, in the Change Policy window.
The Schedules tab lists the schedules for the policy. The only schedule that currently
exists is the FULL schedule.
4. Click the entry for the FULL schedule, then click Change.
The Change Schedule window is opened, enabling you to modify the schedule
parameter settings.
5. Modify the Media multiplexing parameter setting to select a value of “2”, on the
schedule Attributes tab.
6. Click OK to save the schedule.
7. Make no other changes to the policy.
8. Click OK, to save the policy and to close the Change Policy window.
Continue to Exercise C-5: Performing a multiplexed manual backup.
Lab 14-47
Exercise C-5: Performing a multiplexed manual backup
In the steps that follow, you perform a manual full backup of the client using a policy,
schedule, and storage unit that are configured to enable multiplexed backups.
the left pane of the Administration Console window
The Activity Monitor should display job entries such as those illustrated below.
You can also use the hierarchical view option in the Activity Monitor to view
the parent and child jobs.
3. Note that all four backup jobs (one parent job, and three child jobs) are Active at the
same time.
4. Allow all the backup jobs to run to successful completion, and then proceed to the
next step.
Lab 14-48
5. Open the Job Details for each of the child jobs, one-at-a-time. Select the Detailed
Status tab for each job, and view the Status pane.
The Status pane identifies the Media ID of the tape that was mounted to perform the
backup job, the Drive Index for the tape drive on which the tape was mounted, and the
file number on the tape where the backup image was recorded.
The following illustration provides an example of the of Status pane contents of

Detailed Status tab.
6. Using paper and pencil, or the Notepad++ application, record the Media ID, Drive
Index number, and file number for each of the three child backup jobs.
Your backup job results may vary from the results observed by others.
You should note that the first two child backup jobs were written to the same
tape (Media ID) by the same tape drive (Drive index), and to the same file
number on the tape. These backups were multiplexed onto the tape. The Drive
index field for the second job is empty, because the tape used is mounted on
the same drive as is used for the first job.
Because the Media Multiplexing setting for the schedule that was used to
perform the backup was set to a value of “2”, only two of the backup jobs could
be multiplexed onto the first tape. The third child job was written onto another
tape (Media ID) by a different tape drive (Drive index).
Continue to Exercise C-6: Changing the multiplexing settings.
Lab 14-49
Exercise C-6: Changing the multiplexing settings
In the steps that follow, you change the Media Manager (tape) storage unit and policy
schedule multiplexing setting to increase the number of data streams that can be
multiplexed onto a tape.
The right pane of the Administration Console displays the list of configured storage
units.
unit for editing.
3. Verify that the Enable multiplexing check box is marked.
4. Change the Maximum streams per drive setting to a value of “3”.
5. Click OK to save the changes to the master_tape_stu storage unit, and to close the
Change Storage Unit window.
Continue to Exercise C-7: Modifying the policy schedule.
Lab 14-50
Exercise C-7: Modifying the policy schedule
2. Double-click the entry for the LAB14-test-multiple-data-streams policy in the All

Polices pane, to open the policy for editing.
The Change Policy window is opened.
3. Click the Schedules tab of the policy.
The Schedules tab list the schedules for the policy. The only schedule that currently
exists is the FULL schedule.
4. Click the entry for the FULL schedule, then click Change.
The Change Schedule window is opened, enabling you to modify the schedule
parameter settings.
5. Modify the Media multiplexing parameter setting to select a value of “3”, on the
schedule Attributes tab, as illustrated below.
6. After changing the Media multiplexing setting to “3”, click OK to save the change to
the schedule, and to close the Change Schedule window.
7. Make no other changes to the policy.
8. Click OK in the Change Policy window, to save the policy and to close the Change
Policy window.
Continue to Exercise C-8: Performing another multiplexed manual backup.
Lab 14-51
Exercise C-8: Performing another multiplexed manual
backup
In the steps that follow, you perform another manual full backup of the client using a
policy, schedule, and storage unit that are configured to enable multiplexed backups.
the left pane of the Administration Console window
The Activity Monitor should display job entries for the most recently-initiated
backup job.
Note that all four backup jobs (one parent job, and three child jobs) are Active
at the same time.
3. Allow all the backup jobs to run to successful completion before continuing.
4. Open the Job Details for each of the child jobs, one-at-a-time.
Select the Detailed Status tab for each job, and view the Status pane.
The Status pane identifies the Media ID of the tape that was mounted to perform
the backup job, the Drive Index for the tape drive on which the tape was mounted,
and the file number on the tape where the backup image was recorded.
Lab 14-52
5. Use a pencil and paper or Notepad++ to identify the Media ID, Drive Index number,
and file number for each of the three child backup jobs use the information
This information will be referenced in Exercise C-9.
This information will vary from the results received by others.
Child job # Media ID used Drive index # File # on the tape

First job: varies varies varies
Second job: same as first job not listed same as first job
Third job: same as first job not listed same as first job
If configured properly, you should observe that all three child backup jobs that
were initiated by the most recent manual backup request were written to the
same Media ID (tape), by the same tape drive (drive index), and to the same
file number on the tape. The backup images were multiplexed to the tape.
6. Close all open Job Details windows.
Continue to Exercise C-9: Viewing media multiplexing in NetBackup.
Lab 14-53
Exercise C-9: Viewing media multiplexing in NetBackup
In the steps that follow, you use the NetBackup Tape Contents report to observe how
media multiplexing writes backup images to tape.

3. With the Media entry highlighted in the left pane, select View, and then select
Refresh, to update the contents of the right pane of the Administration Console.
4. Use the horizontal scroll bar in the right pane to scroll to the right until the Media
Status column contents are visible, as illustrated below.
5. Take note of the Media ID, from the last backup, which has a Media Status of Full
Multiplexed or Active Multiplexed.
Use this Media ID to perform the steps that follow.
6. Select NetBackup Management and then select Reports, Tape Reports in the left
The available NetBackup Tape Reports are listed in the right pane of the
Lab 14-54
7. Double-click the entry for the Tape Contents report in the right pane of the
The default Report Settings for the report are displayed in the right pane of the
Administration Console, as illustrated below.
8. Click the Refresh icon on the tool bar to update the contents of the Report Settings
pane.
9. Use the drop-down menu for the Media Owner field to select the name of your
master server – winmaster.example.com or lnxmaster.example.com.
10. Use the drop-down menu to select the Media ID, which was recorded earlier, from
the last multiplex backup.
12. Take note of the message posted in the Tape Contents Report window, and then OK
to run the report.
When you run the Tape Contents report, NetBackup mounts the tape in a tape
drive to read the contents of the tape.
Lab 14-55
13. Note the results of the Tape Contents report, as illustrated in the figure below.
Your observations may vary from those of others.
14. Observe the File Number and Backup ID column contents of the report output.
The following points help to explain the output of the report:
̶ Backup IDs that share the same File Number were multiplexed to that file
number on the tape.
̶ If a client system has more data to back up than will fit in a single tape fragment,
the backup image (Backup ID) will span multiple File Numbers on the tape.
̶ The fragment size used by the tape drive is defined in the storage unit settings.
15. Compare the output of your Tape Contents report, to those in the previous
illustration, and take a moment to consider the information that is provided by the
report.
If the Tape Contents report does not show any multiplexed images, meaning
you cannot identify any Backup IDs that share the same File Number, run the
Tape Contents report again using a different Media ID that you noted having a
Media Status of Active Multiplexed or Full Multiplexed.
Repeat this process until you are able to view the expected results. If you are
unable to view the expected multiplexed results in the Tape Contents report,
seek assistance.
Lab 14-56
You have completed this optional lab exercise.
- Optional Exercise
You have completed all exercises of this lab activity.
Lab 14-57
Lab 15: Collecting Logs and Diagnostic
Information
In this lab, you perform tasks related to the support and maintenance of a NetBackup
environment, including tasks to enable logging and the collection of logs and other
diagnostic information.
Proceed to Exercise A: Viewing the NetBackup services.
Lab 15-1
Exercise A: Viewing the NetBackup services
In this exercise, you use NetBackup-provided interfaces to view NetBackup services and
processes.
Continue to Exercise A-1: Viewing the NetBackup services in the Activity Monitor.
Lab 15-2
Exercise A-1: Viewing the NetBackup services in the
Activity Monitor
In the steps that follow, you use the Activity Monitor to view the status of NetBackup
services on NetBackup server systems.

located on the desktop of the console.example.com system.
3. In the NetBackup Administration Console login screen, log in to your master server
using the User name and Password information provided in the table below.
Lab environment Master server hostname User name Password

4. When the NetBackup Administration Console window is displayed, click the Activity
Monitor entry in the left pane of the Administration Console.
The Activity Monitor is displayed in the right pane of the Administration Console
and provides four tabs, as illustrated below.
Lab 15-3
5. Click the Daemons tab, located at the bottom of the Activity Monitor screen.
6. Take note of the Daemons or Services that are listed.
The NetBackup Activity Monitor allows you to stop and start NetBackup
services and daemons. Use this capability with caution. Stopping NetBackup
daemons while jobs are running may prevent the jobs from completing
successfully. Contact Veritas Technical Support if you have questions.
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 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 used the command line tools earlier in
this exercise.
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.

console.example.com. You use the Administration Console in the next exercise.
Proceed to Exercise B: Running NetBackup reports for troubleshooting.
Lab 15-4
Exercise B: Running NetBackup reports for
troubleshooting
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
Continue to Exercise B-1: Running the Status of Backups report.
Lab 15-5
Exercise B-1: 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.

3. Select NetBackup Management and then select Reports in the left pane of the
4. Expand the Reports entry in the left pane of the Administration Console.
The following reports are listed below the expanded reports object:
̶ Client Backups
̶ Problems
̶ All Log Entries
̶ Images on Media
̶ Media Logs
5. Click the entry for the Status of Backups report in the left pane of the
be used to filter the output of the report.
6. Do not modify the report settings, and click the Run Report button to run the Status
of Backups report using the default settings.
The output of the report is displayed on the bottom half of the right pane of the
7. View the output of the report, and take note of the information that is provided by
the report
Lab 15-6
8. If you wish, change the Report Settings for the report, and run the report again to
see impact on the report output.
9. Note that you can change the report settings to obtain output such as:
̶ List all the jobs that ran in a specified time period.

̶ List all the jobs that used a specified NetBackup media server.
̶ List all the jobs that were associated with a specific NetBackup client.
̶ Run the report to find the entry for a specific Job ID.
Continue to Exercise B-2: Running the Client Backups report.
Lab 15-7
Exercise B-2: Running the Client Backups report
In the steps that follow, you initiate the Client Backups report from the NetBackup
1. Select the entry for the Client Backups report in the left pane of the Administration
Console.
2. In the Date/Time Range section, check the Earliest available check box.
3. Leave the rest of the report settings at their defaults, and click the Run Report
button to run the Client Backups report.
the report.
Continue to Exercise B-3: Running the Problems report.
Lab 15-8
Exercise B-3: Running the Problems report
In the steps that follow, you initiate the Problems report from the NetBackup
1. Select the entry for the Problems report in the left pane of the Administration
Console.
2. Click the Run Report button to run the Problems report using the default settings.
the report. If you have had jobs fail in earlier labs, it is possible there may be
messages associated with those jobs. Most of the entries are probably warnings and
not serious problems.
Continue to Exercise B-4: Running the All Log Entries report.
Lab 15-9
Exercise B-4: Running the All Log Entries report
In the steps that follow, you initiate the All Log Entries report from the NetBackup
1. Select the entry for the All Log Entries report in the left pane of the Administration
Console.
2. Click the Run Report button to run the All Log Entries report using the default
settings.
the report.
Continue to Exercise B-5: Running the Media Logs report.
Lab 15-10
Exercise B-5: Running the Media Logs report
In the steps that follow, you initiate the Media Logs report from the NetBackup
1. Select the entry for the Media Logs report in the left pane of the Administration
Console.
2. Click the Run Report button to run the Media Logs report using the default settings.
the report.
Proceed to Exercise C: Using the nbsu and nbcplogs commands.
Lab 15-11
Exercise C: 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.
Proceed to Exercise C-1: Running nbsu.
Lab 15-12
Exercise C-1: Running nbsu
In the following steps, you run the nbsu command to gather troubleshooting
information for the NetBackup master server system.
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.

or a Terminal window on your Linux-based master server, lnxmaster.example.com.
2. Access or open a Command Prompt window on winmaster.example.com, or the

Terminal window on lnxmaster.example.com.
3. Type the command shown below and press Enter, to display help information on the
use of the nbsu utility.
Command: nbsu -help |more
nbsu -help displays an extensive description of the utility and of the options
that are available when performing the command.
4. To page downward through the help information, use the Enter key to advance one
line at-a-time, or the Space bar to advance one page-at-a-time.
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 master server and media server systems to include the folder location to
the nbsu and nbcplogs utilities.
Lab 15-13
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 it gathers to a cab file (on Windows-
based systems) or a gzipped tar file (on UNIX/Linux-based systems) located in
an output directory located directly below the folder/directory in which you
run the command.
5. What nbsu command line option can you use to see a list of diagnostic commands
that nbsu will run? See the answer below.
Use the –l command line option (lowercase L).
6. What nbsu command line option can you use to run only commands or procedures
that are related to the Net Backup configuration? See the answer below.
Use the –c command line option.
7. What nbsu command option can be used to choose the role of the system on which
the diagnostic commands or procedures are to run? See the answer below.
Use the –r command line option, followed by the <NBU role>.
Further information about nbsu is provided the NetBackup Commands

Reference Guide.
8. Change the current folder or directory in the Command Prompt or Terminal

window, as shown below:
Command: cd C:\ (Windows)

Command: cd /tmp (Linux)
Lab 15-14
9. Type the command shown below, and press Enter to display a list of the diagnostic
commands that nbsu will select to run on this system.
Command: nbsu –l |more (lowercase L)
View the output (multiple pages) of the command that is displayed.
Advance the output of the command one page at-a-time using the space bar.
10. When the command prompt is returned, take note of the end of the nbsu –l
command output on the screen, which describes the location of the nbsu output file
on the local system.
By default, the output of the nbsu command is written to an output folder or

directory that is created in the current folder (the folder or directory you are in when
the command is executed) as shown below.
The folder name has the format:

.\output\nbsu\<hostname>_<server_role>_<YYYYMMDD>_<HHMMSS>\
(Windows)
Example: .\output\nbsu\winmaster_master_20180105_102300\ (Windows)
or
./output/nbsu/<hostname>_<server_role>_<YYYYMMDD>_<HHMMSS>/
(UNIX/Linux)
Example: ./output/nbsu/lnxmaster_master_20180105_103845/ (UNIX/Linux)
The file name of the output file has the format:

<hostname>_<server_role>_<YYYYMMDD>_<HHMMSS>.cab (Windows),
or
<hostname>_<server_role>_YYYYMMDD>_<HHMMSS>.tar.gz (UNIX/Linux)
Example: winmaster_master_20180105_102300.cab (Windows)
Example: lnxmaster_master_20180105_103845.tar.gz (UNIX/Linux)
11. Verify the current folder or directory location in the Command Prompt
(winmaster.example.com) or Terminal (lnxmaster.example.com) window. (C:\ on
Windows) (/tmp –on Linux)
Lab 15-15
12. Run the nbsu utility with no command options or arguments, as shown below.
Command: nbsu
13. Monitor the nbsu command output that is displayed in the Command Prompt or
Terminal window.
It may take several minutes (5-10 minutes) for the command to complete, and
for the command prompt to be returned.
14. Allow the command to run to completion.
15. List the contents of the current directory in the Command Prompt or Terminal
window.
Command: dir (Windows)

Command: ls –al (UNIX/Linux)
16. Change directory into the output/nbsu folder or directory.
Command: cd output\nbsu (Windows)

Command: cd output/nbsu (UNIX/Linux)
17. List the contents of the current folder or directory.
18. Take note of the contents of the folder or directory. There will be one or more
subdirectories (one for each time you have run nbsu):
Example: winmaster_master_20180105_102300\ (Windows)

Example: lnxmaster_master_20180105_103845/ (UNIX/Linux)
The naming convention is hostname_role_date_time. The directory with the

highest time value contains the output of the most recent nbsu run.
19. Change directory into the most recent (highest numbered) folder or directory:
Example: cd winmaster_master_20180105_102300 (Windows)

Example: cd lnxmaster_master_20180105_103845 (UNIX/Linux)
Lab 15-16
20. List the contents of the current folder or directory, and verify that it contains the
output file that was created by nbsu, as illustrated in the figures below.
The figure below illustrates the nbsu output cab file on a Windows-based system.
The figure below illustrates the nbsu output tar.gz file on a Linux-based system.
In a troubleshooting situation, you would provide the output file (cab file or
tar.gz file) to Veritas technical support for analysis.
21. Close the Command Prompt window on winmaster.example.com, or the Terminal

window on lnxmaster.example.com.
Continue to Exercise C-2: Using nbcplogs.
Lab 15-17
Exercise C-2: Using nbcplogs
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.

or a Terminal window on your Linux-based master server, lnxmaster.example.com.
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.

3. In the Command Prompt or Terminal window, type the command shown below, and
press Enter.
Command: nbcplogs -–help-long | more
Lab 15-18
The figure below illustrates the help information for the nbcplogs command.
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.
4. 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.
This command writes the output files to C:\support\nbcplogs-out.
Command: nbcplogs -d 15min C:\support\nbcplogs-out (Windows)

Command: nbcplogs –d 15min /support/nbcplogs-out (Linux)
Lab 15-19
5. Monitor the progress of the nbcplogs command execution in the Command Prompt
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 C:\support (or
/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.
6. When the command completes, open a File Explorer window

(winmaster.example.com), or access the Terminal window
(lnxmaster.example.com).
7. Navigate to the C:\support\nbcplogs-out folder on winmaster.example.com, or to

/support/nbcplogs-out on lnxmaster.example.com.
Command: cd /support/nbcplogs-out (Linux)
8. 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.
The output of the nbcplogs file is ready to send to Veritas.
Lab 15-20
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 master server.
9. Close the Command Prompt or Terminal window on your master server system
Feel free to experiment further with the use of the nbsu and nbcplogs commands to
gather troubleshooting information.
If you wish to continue with the optional exercises of this lab activity, click the link to
proceed to Exercise D: (Optional) Viewing and setting debug log properties.
- Required Exercises
Lab 15-21
Exercise D: (Optional) Viewing and setting debug
logging properties

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 optional exercise, you view the NetBackup configuration parameters that are
used to configure NetBackup log files.
Continue to Exercise D-1: Setting debug log properties.
Lab 15-22
Exercise D-1: 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.

The host name of your master server is displayed in the list of master servers in the
4. Click the entry for the master server in the right pane, and then select Actions and
then select Properties.
The Master Server Host Properties window is displayed.
5. Locate and click the Logging entry, located in the left pane of Master Server Host
Properties window.
The right pane of the Master Server Host Properties window displays the Logging
parameters that can be set for the selected master server.
Lab 15-23
6. The default logging level settings are currently displayed in the Logging pane of the
Master Server Host Properties window.
̶ 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.
̶ 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.
̶ 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.
7. For now, allow all the settings in the Logging pane to remain at the default settings.
8. 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, and in the Windows registry on Windows-based NetBackup systems,
in HKLM\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config
Logging levels for Unified-style logs are stored in the

/usr/openv/netbackup/nblog.conf file on UNIX or Linux-based NetBackup
master server systems, and in <install_path>\NetBackup\nblog.conf on
Windows-based NetBackup master server systems.
Refer to the Veritas NetBackup Logging Reference Guide for complete details
on setting logging verbosity.
Continue to Exercise D-2: Logging for critical processes.
Lab 15-24
Exercise D-2: 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.
1. 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.
2. 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.
3. 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.
4. Click OK to close the Master Server Host Properties window.
The Restart Daemons window appears.
5. Click OK to close the Restart Daemons window.
6. Access the desktop of the Windows-based master server, winmaster.example.com

or open a Terminal window (using PuTTY) to your Linux-based master server,
Lab 15-25
7. Log on to the master server using the username/password combination provided

above.

9. Navigate to the NetBackup logging directory using the appropriate command:
̶ Windows: cd c:\program files\veritas\netbackup\logs

̶ Linux: cd /usr/openv/netbackup/logs
10. Check to see if the critical log bpbrm currently exists using the appropriate
command:
̶ Windows: dir bp*

̶ Linux: 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
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.
11. Leave the Command Prompt window or Terminal window open on your master
server system. You access this window again in the next exercise.
You have completed the steps for this optional exercise.
If you wish to continue with another optional exercise, click the link to proceed to
Exercise E: (Optional) Enabling NetBackup legacy logging.
Lab 15-26
Exercise E: (Optional) Enabling NetBackup legacy
debug logging

from a Veritas NetBackup Technical Support Engineer, or the technical support
In this optional exercise, you enable legacy logging for a legacy service and a legacy
process on the master server system. This exercise illustrates the principals of legacy
logging.
Continue to Exercise E-1: Enabling NetBackup legacy logging.
Lab 15-27
Exercise E-1: Enabling NetBackup legacy logging

or the open Terminal window that is connected (via PuTTY) from
console.example.com to your Linux-based master server, lnxmaster.example.com.
2. Access the open Command Prompt window on winmaster.example.com or the

3. Change directory to the NetBackup logs folder or directory using the appropriate
command, as described below.
̶ Windows: cd c:\program files\veritas\netbackup\logs

̶ Linux: cd /usr/openv/netbackup/logs
4. Verify that you are in the correct directory before continuing.
5. List the contents of the directory using the appropriate command:
̶ Windows: dir
̶ Linux: 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.
Continue to Exercise E-2: Viewing the mklogdir.bat file.
Lab 15-28
Exercise E-2: Viewing the mklogdir.bat file
The mklogdir.bat file (Windows) or mklogdir ((UNIX/Linux) 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.bat or mklogdir script.
1. In the Command Prompt or Terminal window, view the contents of the mklogdir
(or mklogdir.bat) file using the appropriate command as shown below.
̶ Windows: more mklogdir.bat

̶ Linux: more mklogdir
The contents of the mklogdir (or mklogdir.bat) file are displayed.
2. Use the space bar to advance the display of the file contents one screen-at-a-time.
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.
Lab 15-29
An excerpt of the contents of the mklogdir.bat file is illustrated in the figures
below – for Windows and Linux based systems.
3. Type Ctrl +C on your keyboard to close the mklogdir file, and return to the command
prompt.
Windows and Linux: Ctrl + C
Lab 15-30
4. Allow the Command Prompt window (on winmaster.example.com) or Terminal
window (on lnxmaster.example.com) to remain open.
You access this window in the next exercise.
Continue to Exercise E-3: Creating log folders for legacy-style logging.
Lab 15-31
Exercise E-3: 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.
1. From the Command Prompt window or the Terminal window, use mklogdir to
create the bpjobd directory in the logs directory on your master server:
Windows: mklogdir bpjobd

Linux: ./mklogdir bpjobd
The bpjobd directory will be created with the proper permissions.
bpjobd (NetBackup Jobs Daemon) is a NetBackup service that runs only on

the master server. bpjobd runs continually on the master server system
whenever NetBackup is running.
2. Verify that you have successfully created the bpjobd directory using the appropriate
command:
Windows: dir bpjobd

Linux: ls –al bpjobd
Lab 15-32
The new bpjobd directory is currently empty. When logging commences for the
bpjobd 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.
3. Allow the NetBackup Administration Console window on console.example.com to

remain open and logged in to your master sever.
4. Leave the Command Prompt window on winmaster.example.com or the Terminal

window on lnxmaster.example.com open on the master server. You will return to
this window in a few minutes.
Continue to Exercise E-4: Running a backup job.
Lab 15-33
Exercise E-4: Running a backup job
In the steps that follow, you perform a manual backup that writes to tape storage on
the master server system.
2. Access the open NetBackup 8.1 Administration Console on console.example.com.
If a NetBackup Administration Console window is not currently open, double-click

the shortcut on the desktop of console.example.com to launch the application.
When the NetBackup Administration Console log in window is displayed, enter the
credentials for your preferred master server, and click the Login button.
Host Name User name Password

4. Click the entry for the PRE-clients-to-master-tape policy, located in the All Policies
6. In the Clients pane of the Manual Backup window, click the entry for
winmaster.example.com (Windows) or lnxmaster.example.com (Linux), and click
OK.
7. Click the Activity Monitor entry in the left pane of the Administration Console, and
monitor the progress of the most recent backup job that used the PRE-clients-to-
master-tape policy.
8. Verify that the job runs to successful completion. If the job fails, record the status
code and seek assistance.
Continue to Exercise E-5: Verifying the creation of the log files.
Lab 15-34
Exercise E-5: Verifying the creation of the log files
In previous steps of this exercise, you created log folders for the bpbrm and bpjobd
services on your master server. In the steps that follow, you view the results in the log
file folders.
1. Access the open Command Prompt window on winmaster.example.com, or the

2. In the Command Prompt or Terminal window, navigate to the directory indicated

below, using the appropriate command:
Windows: cd c:\program files\veritas\netbackup\logs

Linux: cd /usr/openv/netbackup/logs
3. List the contents of the directory using the appropriate command:
Windows: dir bpjobd
Linux: ls –al bpjobd
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., ALL_ADMINS.021217.log). The user name will be ALL_ADMINS for
Windows and root for Linux.
4. Access the open Command Prompt window on winmaster.example.com or the

Lab 15-35
5. List the contents of the bpbrm directory using the appropriate command:
Windows: dir bpbrm
Linux: ls –al bpbrm
You should observe the following:
A log file is present in the folder – unless a problem occurred on the master server
that prevented the bpbrm process from being initiated.
The filename of the file is user_name.mddyy.log (e.g.,

ALL_ADMINS.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 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 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 master server is configured as a media
server so this process will also run on the master server when a backup or
restore operation directs backup activity to backup storage on that system.
6. Double-click the Notepad++ desktop icon on winmaster.example.com and open the

new log file, or use the view command in the Terminal window on
lnxmaster.example.com to view the contents of the bpbrm log file.
Lab 15-36
7. 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.
8. Close the bpbrm log file.
You have completed this exercise.
If you wish to continue with the optional exercises, proceed to Exercise F: (Optional)
Viewing debug logging levels for unified logs.
Lab 15-37
Exercise F: (Optional) Viewing debug logging levels
for unified logs

information is an activity that should always be undertaken with guidance from
a Veritas NetBackup Technical Support Engineer, or technical support
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 optional 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.
• If you are performing this lab activity on a Windows-based master server, click the
link to continue to Exercise F-1: Unified logging on Windows. Exercise F-1 through
Exercise F-6 are for Linux-based systems.
• If you are performing this lab activity on a Linux-based master server, click the link to
continue to Exercise F-7: Unified Logging on Linux. Exercise F-7 through Exercise F-12
are for Linux-based systems.
Lab 15-38
Exercise F-1: Unified logging on Windows
If you are performing this lab activity on a Linux-based master server, click the link to
continue to Exercise F-7: Unified logging on UNIX/Linux. Exercise F-7 through Exercise F-
12 are for Linux-based systems.
In this exercise, you perform the following tasks on your Windows-based master server,
winmaster.example.com:
• 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.
Continue to the steps below to perform tasks related to Unified logging on Windows.

2. Open a File Explorer window on winmaster.example.com.
3. Navigate to the C:\Program Files\Veritas\NetBackup\logs folder in the File Explorer

window on winmaster.example.com.
The logs folder contains several sub-folders, including: ALTPATH, bmrd,

bmrsetup, nbars, nbaudit, nbemm, and many others. These folders
primarily house the unified log files on the master server, although some
folders contain other data.
Lab 15-39
4. Locate and open the nbpem (Policy Execution Manager) folder in the File Explorer
window, and examine the contents of the folder.
You should see a list of files similar to the list illustrated in the figure below.
The log files in the nbpem folder are the nbpem (OID=116) log files. The log
naming convention for unified logs is as shown in the figure below.
In the commands where the NetBackup Product ID is required, the NetBackup

Product ID can be entered as 51216 or nb. This lab exercise uses the nb
syntax for the NetBackup Product ID.
Continue to Exercise F-2: Viewing default logging settings for unified logs
(Windows).
Lab 15-40
Exercise F-2: Viewing default logging settings for unified
logs (Windows)
In the steps that follow, you view and modify the default logging settings for NetBackup
unified debug logs.
1. Navigate to the C:\Program Files\Veritas\NetBackup folder on the master server.
2. Locate the nblog.conf file.
This is the configuration file for unified logging.
3. Open nblog.conf with Notepad++ or WordPad.
The Windows Operating System on winmaster.example.com may indicate that

“Windows can’t open this type of file (.conf)”. If that occurs, click Try an app on this
PC, and choose to open the file in WordPad.
Pay attention to message at the top of the nblog.conf file, as shown below.
Do not edit the nblog.conf file to change its contents. Unified logging
configuration changes are made using the vxlogcfg command.
Lab 15-41
4. Scroll through the contents of the nblog.conf file contents to locate the section that
is highlighted in the following figure.
The highlighted section in the previous figure defines the default logging
verbosity settings for the unified logs. The key words DiagnosticLevel and
DebugLevel (case is significant) define the logging levels for diagnostic and
debug messages. The default DiagnosticLevel is set to 6 (maximum) and the
default DebugLevel is set to 1 (minimum).
5. Close the nblog.conf configuration file without making changes to the file.
6. Open a Command Prompt window on the master server, winmaster.example.com.
7. In the Command Prompt window, 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 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.
Lab 15-42
8. After entering the first vxlogcfg command successfully, type the following command,
and press Enter.
Command: vxlogcfg –p nb –l –o Default (-L is lowercase)
The command output displays the default settings for unified logging on the master
server, as shown below.
Both the DebugLevel and the DiagnosticLevel are now set to 6, as a result of
the first vxlogcfg command that you executed.
9. Allow the File Explorer window to remain open on winmaster.example.com. You

return to this window later in this exercise.
Continue to Exercise F-3: Setting unified logging levels using the Administration
Console (Windows).
Lab 15-43
Exercise F-3: Setting unified logging levels using the
Administration Console (Windows)
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.
3. Double-click the entry for your Windows-based master server,

winmaster.example.com, to open the Master Server Host Properties window.
4. Click the Logging entry, located in the left pane of the Master Server Host
Properties window.
5. Set the logging levels for the Policy Execution Manager (nbpem), the Job Manager
(nbjm), and Resource Broker (nbrb) services to Debug logging level = 2.
6. Click the OK button in the Logging pane of the Master Server Host Properties
window, to save the settings.
7. When the Restart Daemons dialog box is displayed, click the OK button to
acknowledge the message and to close the dialog box.
The Master Server Host Properties window is closed.
Continue to Exercise F-4: Verifying the unified logging settings (Windows).
Lab 15-44
Exercise F-4: Verifying the unified logging settings
(Windows)
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.
1. Return to the desktop of your master server system, winmaster.example.com.
2. Access the open a File Explorer window on winmaster.example.com.
3. Navigate to the C:\Program Files\Veritas\NetBackup folder and open nblog.conf.
4. Scroll through the contents of the nblog.conf file until you find the section that is
Lab 15-45
The section of the nblog.conf configuration file illustrated in the figure on the
previous page identifies the logging level settings for the individual NetBackup
services (OIDs) that use unified logging. Notice that the DebugLevel for each of
the three processes (nbpem, nbjm and nbrb) has been set to 3. In the
Administration Console, 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.
5. Close the nblog.conf file.
Continue to Exercise F-5: Changing the diagnostic logging level settings (Windows).
Lab 15-46
Exercise F-5: Changing the diagnostic logging level
settings (Windows)
The next steps describe the method for changing the diagnostic logging levels for
services that use unified logging.
1. In a Command Prompt window on the master server, type the command shown
Command: vxlogcfg –p nb –a –o nbpem –s DiagnosticLevel=3
2. 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.
The parameters of the vxlogcfg command are case-sensitive.
Command: vxlogcfg –p nb –l –o nbpem (lowercase L)
The figure below illustrates the output of the vxlogcfg –p –nb –l –o

nbpem command.
Lab 15-47
4. Take note of the logging level settings for debug and diagnostic messages for nbpem
in the vxlogcfg command output.
They should both be set to level 3.
Command: vxlogcfg –p nb –a –o Default –s DiagnosticLevel=6

–s DebugLevel=1
This command is entered in preparation for a later exercise and will reset the default
DebugLevel and DiagnosticLevel logging levels to their original values.
6. 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.
Continue to Exercise F-6: Resetting unified logging levels for nbpem, nbjm, nbrb
(Windows).
Lab 15-48
Exercise F-6: Resetting unified logging levels for nbpem,
nbjm, nbrb (Windows)
In the steps that follow, you use the NetBackup Master Server Host Properties to set
the Debug logging levels for the Policy Execution Manager (nbpem), Job Manager
(nbjm), and Resource Broker (nbrb) services back to their default settings – the same as
the Global logging level.
3. Double-click the entry for your Windows-based master server, to open the Master
Server Host Properties window.
Properties window.
5. Set the Debug logging levels for the Policy Execution Manager, the Job Manager,
and Resource Broker services to “Same as global”.
The Master Server Host Properties window is closed.
You have completed all Windows-based steps intended for this exercise, and all
exercises of this lab activity.
- Optional Exercises (Windows)
Lab 15-49
Exercise F-7: Unified logging on UNIX/Linux
If you are performing this lab activity on a Windows-based master server, click the link
to continue to Exercise F-1: Unified logging on Windows. Exercise F-1 through Exercise F-
6 are for Windows-based systems.
In this exercise, you perform the following tasks on your Linux-based master server,
lnxmaster.example.com:
• 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.
Continue to the steps below to perform tasks related to Unified logging on Linux.
1. Access the Terminal window (opened using PuTTY) from the console.example.com
system to your Linux-based master server, lnxmaster.example.com.
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 command shown below, 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 command shown below, and press Enter, to change to the nbpem
directory.
Command: cd nbpem
Lab 15-50
6. Examine the contents of the directory.
The contents of the directory will be similar to those illustrated in the figure below.
The log files in the nbpem folder are the nbpem (OID=116) log files. The log
naming convention for unified logs is as illustrated in the figure below.
In the commands that that require the entry of the NetBackup Product ID, the
Product ID can be entered as 51216 or nb.
Continue to Exercise F-8: Viewing default logging settings for unified logs
(UNIX/Linux).
Lab 15-51
Exercise F-8: Viewing default logging settings for unified
logs (UNIX/Linux)
In the steps that follow, you view and modify the default logging settings for NetBackup
unified debug logs.
1. 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.
2. 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.
Lab 15-52
3. 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).
4. Type q to exit the more command.
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.
Lab 15-53
6. After entering the first vxlogcfg command successfully, type the following command,
and press Enter.
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, as shown below.
The DebugLevel and the DiagnosticLevel are now set to 6.
Continue to Exercise F-9: Setting unified logging levels using the Administration
Console (UNIX/Linux).
Lab 15-54
Exercise F-9: Setting unified logging levels using the
Administration Console (UNIX/Linux)
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.
3. Double-click the entry for the Linux-based master server, lnxmaster.example.com,

located in the right pane of the Administration Console.
4. Click the Logging entry in the left pane In the Master Server Host Properties
window.
The Master Server Host Properties window is displayed.
5. Set the Debug logging levels for the Policy Execution Manager (nbpem), the Job
Manager (nbjm), and the Resource Broker (nbrb) to a value of 2.
6. Click the OK button to save the settings, and to close the Master Server Host
Properties window.
Continue to Exercise F-10: Verifying the unified logging settings (UNIX/Linux).
Lab 15-55
Exercise F-10: Verifying the unified logging settings
(UNIX/Linux)
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.
1. Return to the Terminal window (opened using PuTTY) from the

console.example.com system to your Linux-based master server,
2. In the Terminal window, change to the /usr/openv/netbackup directory.
Command: cd /usr/openv/netbackup
3. Use the more command to view the contents of the nblog.conf file.
Command: more nblog.conf
4. Scroll downward through the nblog.conf file until you find the entries for the Policy
Execution Manager, Job Manager, and Resource Broker services, as illustrated in
the figure below.
Lab 15-56
The portion of the nblog.conf file illustrated above identifies the logging level
settings for the individual NetBackup services (OIDs) that use unified logging.
5. 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.
6. Type q to exit the more command.
Continue to Exercise F-11: Changing the diagnostic logging level settings

(UNIX/Linux).
Lab 15-57
Exercise F-11: Changing the diagnostic logging level
settings (UNIX/Linux)
The next steps describe the method for changing the diagnostic logging levels for
services that use unified logging.
1. Type the command shown below, and press Enter, to change the DiagnosticLevel
setting for the nbpem service to 3.
Command: vxlogcfg –p nb –a –o nbpem –s DiagnosticLevel=3

and press Enter.
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.
Command: vxlogcfg –p nb –l –o nbpem (lowercase L)
This command displays the settings for the Policy Execution Manager (nbpem), as
3. Take note of the settings for DebugLevel and DiagnosticLevel parameters for
nbpem. Both settings should be set to level 3.
Lab 15-58
5. Reset the default DebugLevel and DiagnosticLevel logging levels to their original
values.
To accomplish this, type the command shown below, and press Enter.
Command: vxlogcfg –p nb –a –o Default –s DiagnosticLevel=6

–s DebugLevel=1
6. Reset the DiagnosticLevel setting for the nbpem service back to 6, by executing the
command show below.
Command: vxlogcfg –p nb –o nbpem -r –s DiagnosticLevel
7. 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.
Continue to Exercise F-12: Resetting unified logging levels for nbpem, nbjm, nbrb
(UNIX/Linux).
Lab 15-59
Exercise F-12: Resetting unified logging levels for nbpem,
nbjm, nbrb (UNIX/Linux)
In the steps that follow, you use the NetBackup Master Server Host Properties to set
the Debug logging levels for the Policy Execution Manager (nbpem), Job Manager
(nbjm), and Resource Broker (nbrb) services back to their default settings.
the left pane of the NetBackup Administration Console.
3. Double-click the entry for your Linux-based master server, lnxmaster.example.com,

Properties window.
5. Set the Debug logging levels for the Policy Execution Manager, the Job Manager,
and Resource Broker services to Same as global.
You have completed all Linux-based steps intended for this exercise, and all
exercises of this lab activity.
- Optional Exercises (Linux)

You have completed all optional exercises for this lab activity.
Lab 15-60

Nbu81 Admin Lab Book PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Nbu81 Admin Lab Book PDF

Enviado por

Direitos autorais:

Formatos disponíveis

Veritas NetBackup 8.

Not for Distribution

Course Developer Technical Contributors and Reviewers

Bill Drazkowski Chris Amidei

Lab 1: Introduction to NetBackup

Lesson 2: Configuring NetBackup storage

Lesson 3: Configuring Policies and Schedules

Lesson 4: Performing File System Backups

Exercise A: Using the Activity Monitor ........................................................................................4-2

Lesson 5: Performing File System Restores

Table of Contents iii

© 2017 Veritas Technologies LLC. All Rights Reserved

Not for Distribution

Lesson 7: Configuring Media Server Deduplication

Lesson 8: Configuring Tape Storage

Lesson 9: Managing and Optimizing Tape Storage

Lesson 10: Protecting Virtual Machines

iv Veritas NetBackup 8.1: Administration

© 2017 Veritas Technologies LLC. All Rights Reserved

Not for Distribution

Lesson 12: Duplicating Backups

Lesson 13: Managing and Protecting the NetBackup Catalog

Lesson 14: Optimizing File System Backups

Lesson 15: Collecting Logs and Diagnostic Information

Exercise E: (Optional) Enabling NetBackup legacy debug logging ...........................................15-27

© 2017 Veritas Technologies LLC. All Rights Reserved

Not for Distribution

perform in this lab activity.

Not for Distribution

The NetBackup 8.1: Administration course is delivered in several delivery

• Instructor-Led Training (ILT)

Not for Distribution

• The Windows-based NetBackup servers, winmaster.example.com and

• The Linux-based NetBackup Servers, lnxmaster.example.com and

• To perform the labs in a Windows-based lab environment, continue to Exercise B-1:

Not for Distribution

IMPORTANT: If your intention is to use the Linux-based NetBackup server systems,

NetBackup 8.1 software has been pre-installed on lab systems as follows:

• winmaster – NetBackup 8.1 master server, media server, and client

Not for Distribution

1. Power off (shut down) lnxmaster.example.com in Hatsize/VILT.

Not for Distribution

Continue to Exercise E: Accessing remote lab systems.

Not for Distribution

IMPORTANT: If your intention is to use the Windows-based NetBackup server systems,

NetBackup 8.1 software has been pre-installed on lab systems as follows:

• lnxmaster – NetBackup 8.1 master server, media server, and client

Not for Distribution

1. Power off (shut down) winmaster.example.com in Hatsize/VILT.

Not for Distribution

Continue to Exercise E: Accessing remote lab systems.

Not for Distribution

• The Windows-based NetBackup servers, winmaster.example.com and

• The Linux-based NetBackup Servers, lnxmaster.example.com and

• To perform the labs in a Windows-based lab environment, continue to Exercise C-1:

Not for Distribution

IMPORTANT: If your intention is to use the Linux-based NetBackup server systems,

NetBackup 8.1 software has been pre-installed on lab systems as follows:

• winmaster – NetBackup 8.1 master server, media server, and client

Not for Distribution

Startup System Detailed Instructions: IMPORTANT Sequence and Timing

• Wait until LOGIN PROMPT is displayed.

• Continue on to next VM.