Nbu81 Admin Lesson Book PDF

Veritas NetBackup 8.
1:
Administration –
Lesson 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 Robert Owen

Cheryl Faulkner Jose Ignacio Colodras Paul Ransted
Sarah Fort-Kramer Graeme Gofton Asaf Sabir
Joe Gallagher Swati Joshi Sylvain Savary
John Gerhardson Stefano Lollio Stephen Williams
Tomer Gurantz
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
For specific country offices Veritas World Headquarters © 2018 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
Course Introduction
Course Introduction .............................................................................................................. Intro-2
Lesson 1: Introducing NetBackup

Data Protection and the NetBackup Environment ......................................................................1-4
NetBackup concepts ..................................................................................................................1-11
Using the NetBackup Administration Console ...........................................................................1-18
NetBackup appliance overview..................................................................................................1-23
Using NetBackup OpsCenter ......................................................................................................1-31
Lesson 2: Configuring NetBackup Storage

NetBackup storage device concepts ............................................................................................2-4
Configuring and managing a basic disk storage unit ...................................................................2-8
Configuring storage unit groups ................................................................................................2-13
Lesson 3: Configuring Policies

Introduction to backup policies ...................................................................................................3-4
Creating and configuring policy attributes ..................................................................................3-7
Creating a policy schedule .........................................................................................................3-13
Adding client to a policy.............................................................................................................3-23
Creating backup selections ........................................................................................................3-26
Managing existing policies .........................................................................................................3-37
Lesson 4: Performing File System Backups

Using and customizing the NetBackup Activity Monitor .............................................................4-4
Performing manual backup operations .....................................................................................4-14
Performing user-directed backups ............................................................................................4-22
Backup job-related tips ..............................................................................................................4-27
Lesson 5: Performing File System Restores

Introduction to restores...............................................................................................................5-4
Performing restore operations using the BAR interface .............................................................5-9
Performing restore operations using OpsCenter Operational Restore .....................................5-21
Restore job-related tips .............................................................................................................5-34
Lesson 6: Configuring Disk Pools

Understanding disk pools and AdvancedDisk ..............................................................................6-4
Configuring AdvancedDisk .........................................................................................................6-12
Managing AdvancedDisk storage...............................................................................................6-25
Table of Contents iii
© 2018 Veritas Technologies LLC. All Rights Reserved

Lesson 7: Configuring Media Server Deduplication
Introduction to NetBackup deduplication ...................................................................................7-4
Configuring NetBackup media server deduplication .................................................................7-14
Configuring client-side deduplication ........................................................................................7-32
Managing NetBackup deduplication..........................................................................................7-37
Lesson 8: Configuring Tape Storage

Understanding Media Manager storage units .............................................................................8-4
Configuring tape devices............................................................................................................8-14
Verifying tape storage................................................................................................................8-18
NetBackup media concepts .......................................................................................................8-25
Configuring media ......................................................................................................................8-33
Lesson 9: Managing Tape Storage

Managing robots and tape drives ................................................................................................9-4
Monitoring media and media states..........................................................................................9-17
Managing tapes..........................................................................................................................9-32
Media- and device-related tips ..................................................................................................9-48
Lesson 10: Performing Virtual Machines Backups

Introduction to virtual machine backups ...................................................................................10-4
Configuring VMware backups ..................................................................................................10-10
Performing and Monitoring VM Backups ................................................................................10-45
Lesson 11: Performing Virtual Machines Restores

Managing virtual machine restores ...........................................................................................11-4
Managing VMware restores ......................................................................................................11-8
Using VMware Instant Recovery ..............................................................................................11-26
Lesson 12: Duplicating Backups Using Storage Lifecycle Policies

Backup duplication concepts .....................................................................................................12-4
Storage lifecycle policy concepts .............................................................................................12-12

Using storage lifecycle policies ................................................................................................12-15
Additional Storage Lifecycle Policy features and benefits .......................................................12-31
Lesson 13: Managing and Protecting the NetBackup Catalog

Introduction to NetBackup catalogs ..........................................................................................13-4
Managing images .....................................................................................................................13-10
Configuring a catalog backup policy ........................................................................................13-27
Disaster recovery strategies ....................................................................................................13-37
iv Veritas NetBackup 8.1: Administration

Lesson 14: Optimizing File System Backups
File system backup challenges ...................................................................................................14-4
Optimizing file system backups .................................................................................................14-8
Optimizing file system backups with NetBackup Accelerator .................................................14-14
Using multiple data streams ....................................................................................................14-28
Optimizing tape drive performance using multiplexing ..........................................................14-36
Handling busy files on UNIX and Windows file systems ..........................................................14-39
Lesson 15: Collecting Logs and Diagnostic Information

Performing basic NetBackup troubleshooting ...........................................................................15-4
Identifying NetBackup processes, services, and daemons ......................................................15-13
NetBackup logging overview ...................................................................................................15-24
Using the support utilities ........................................................................................................15-34
Using NetBackup support resources........................................................................................15-43
Appendix A: Introduction to Application and Database Backups

Application protection concepts................................................................................................. A-3
Introduction to database backups ............................................................................................ A-11
Introduction to enterprise application backups ....................................................................... A-18
Appendix B: Protecting and Recovering Hyper-V Virtual Machines

Introduction to virtual machine backups .................................................................................... B-3
Configuring Hyper-V backups ..................................................................................................... B-9
Performing and Monitoring Hyper-V backups .......................................................................... B-30
Performing Hyper-V restores .................................................................................................... B-33
Performing Hyper-V restores with the NetBackup Add-in for SCVMM .................................... B-41
Appendix C: Configuring NetBackup BasicDisk Staging

Configuring NetBackup BasicDisk Staging....................................................................................C-2
Table of Contents v

Course Introduction
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Course Introduction” in the “Veritas NetBackup 8.1: Administration” course.

Intro-1
Intended audience
This course is intended for NetBackup administrators responsible for:

• Configuring devices and storage units
• Configuring and managing media
• Creating and configuring backup policies
• Performing backups and restores
• Protecting the backup data and configuration
Administering a backup environment for a company or an organization is a complicated

undertaking performed by a team of administrators, operators, and technical engineers,
each with specific tasks.
This course is intended for system or network administrators, system engineers,
technical support personnel, and system integration and development staff who are
responsible for configuring devices and storage units, configuring and managing media,
creating and configuring backup policies, performing backups and restores, and
protecting the backup data and configuration.
For additional information about topics not covered by this course, see the “Veritas
Education’s core data protection curriculum for NetBackup” section of this introduction.
Course prerequisites
Students attending this course should be familiar with:
• UNIX or Windows system administration
• Storage area network (SAN) concepts
• Data protection concepts and terminology

Intro-2
Course objectives
• Create and configure storage units and storage unit groups.

• Create backup policies that define the rules NetBackup follows.
• Back up and restore data for physical and virtual machine clients.
• Configure AdvancedDisk and NetBackup deduplication storage.
• Configure drives and robots for NetBackup.
• Configure media by defining volumes, volume pools, and volume groups.
• Protect your data with duplication and storage lifecycle policies.
• Protect your NetBackup configuration.
After completing this course, you will be able to perform the tasks listed on this slide.

Intro-3
Lessons in this course
1. Introduction to NetBackup 13. Managing and Protecting the NetBackup Catalog
2. Configuring NetBackup Storage 14. Optimizing File System Backups
3. Configuring Policies 15. Collecting Logs and Diagnostic Information
4. Performing File System Backups
5. Performing File System Restores
6. Configuring Disk Pools
7. Configuring Media Server Deduplication
8. Configuring Tape Storage
9. Managing Tape Storage
10. Performing Virtual Machines Backups
11. Performing Virtual Machines Restores
12. Duplicating Backups Using Storage Lifecycle
Policies
The lessons covered in the NetBackup 8.0 Administration course are shown on the slide.
The course is structured by going through a number of general steps:
Lessons 1-5 set the framework for understanding NetBackup, covering basic concepts
such as storage units, backup policies, and how to perform backups and restores of file
systems.
Lessons 6-9 show how to configure and manage various storage types, including
AdvancedDisk, NetBackup deduplication, and tape libraries.
Lessons 10-11 cover the protection and recovery of virtual machines, highlighting
VMware backup and recovery in detail.
Lesson 12 covers duplicating backups, and storage lifecycle policies (SLP) specifically.
Lesson 13 discusses the management of backup images and protection of the
NetBackup catalog.
Lesson 14 covers many features to optimize backups to file systems through change
tracking, and other NetBackup features.
Lesson 15 shows how to collect logs and other diagnostic information, setting the
ground work for troubleshooting, and contacting Veritas Support.

Intro-4
Virtual On-Demand Training (VODT)
https://www.veritas.com/services/education-services/vodt-course-list
On-demand labs User Support

Lab access for 45 Email support for
days with varying access or technical
number of lab hours issues in running
labs or videos
Recorded video Ask the Experts

lectures Ability to ask questions to
Access to videos for expert Instructor or Subject
duration of offering Matter Experts via email
Participant guide Self-help lab

and lab guide PDFs resources
Equivalent to those Including introductory
used in ILT and VILT videos and FAQs
5
Virtual On-Demand Training (VODT) combines video, recorded lectures with on-
demand, remote access to hands-on labs and access to experts upon request.
VODT includes the following:
• On-demand labs: Lab access for 45 days, which includes a varying amount of lab
hours depending on course length and course content.
• Recorded video lectures: Access to videos for the duration of the offering, which
includes the recordings of expert instructors.
• Participant guide and lab guide PDFs: Equivalent to the same content and books
used and provided in Instructor-Led Training (ILT) and Virtual Instructor-Led Training
(VILT).
• Self-help lab resources: Includes introductory videos for the VODT environment and
that specific course, and also includes Frequently Asked Questions (FAQs)
documents.
• Ask the Experts: Ability to ask questions to expert Instructors and Subject Matter
Experts via email.
• User Support: Email support for user access or technical issues in running labs or
videos.
For more information on how Virtual On-Demand Training works, view the VODT
datasheet, found online on the Veritas Education website at
https://www.veritas.com/services/education-services/vodt-course-list.

Intro-5
Veritas Open eXchange
https://vox.veritas.com/
• The latest technology articles

from industry experts
• Easy and fast access to technical
content and product information
• Access to premium content, such
as book previews and free sample
chapters
• Peer-to-peer discussion forums
• Training and education resources
Find out more. It’s free!
The Veritas Open eXchange allows customers and users of Veritas products to network
get help and learn more about industry-leading solutions. Veritas Open eXchange is a
customer-focused resource, intended to help you design and implement a utility
computing strategy to provide availability, performance, and automation for your
storage, servers, and applications.
Veritas Open eXchange provides the following resources:
• Technical documents, such as articles, white papers, and product specs
• Interactive services, such as the discussion forum, where members can discuss
current topics, share tips and tricks, and help one another troubleshoot problems
Best of all, it is free. Sign up to become a member at https://vox.veritas.com/.

Intro-6
SORT for NetBackup users
http://sort.veritas.com/netbackup
Veritas Services and Operations Readiness Tools (SORT) is a set of Web-based tools that
optimizes the end to end experience for Veritas products, such as Storage Foundation
and NetBackup.
SORT for NetBackup provides information on whether your environment is compatible
with a NetBackup installation or upgrade, and gives you links to the latest
documentation and software.
SORT for NetBackup is available at http://sort.veritas.com/netbackup.

Intro-7
End of presentation
Intro-8
Lesson 1: Introducing NetBackup
This is the “Introducing NetBackup” lesson in the “Veritas NetBackup 8.1:

Administration” course.

1-1
Policies
This lesson is the first lesson in this course.


1-2
Lesson objectives
Topic Objective
Data Protection and the NetBackup Discuss considerations for data protection, and identify the
Environment components of a NetBackup environment and their functions.
Define common terms used in the NetBackup product, and describe
NetBackup concepts
how NetBackup backs up and restores data.
Using the NetBackup Administration
Navigate the NetBackup Administration Console.
Console
NetBackup appliance overview Describe the NetBackup appliance offerings.
Using NetBackup OpsCenter Navigate the OpsCenter Console.
The table on this slide lists the topics and objectives for this lesson.

1-3
Topic: Data Protection and the NetBackup Environment
After completing this topic, you will be able to discuss considerations for
data protection, and identify the components of a NetBackup environment
and their functions.
After completing this topic, you will be able to discuss considerations for data
protection, and identify the components of a NetBackup environment and their
functions.

1-4
The IT administrator’s dilemma
Back up data with

minimal application
and user disruption
Minimize downtime
and data loss during
a failure or outage
Manage backups
and restores easily
and centrally
Your data is the most valuable asset you have. If you lose it, your business is in peril.
Therefore, you must be able to protect it.
Backup is the most obvious requirement. However, in a business it is not sufficient just
to have backup copies of files:
• You must minimize redundancy to keep the time required to back up your data
within a reasonable window and to reduce storage space required.
• You must be able to find your backed up data and be able to restore it quickly when
needed.
• Because you must be able to scale up your solution to manage your entire
organization, simple automated policies that maintain efficient, organized records
that can be readily accessed and used are essential. Also, the backed up data and
these metadata records must be protected against damage or loss.
A variety of technologies are available, and usually a combination of techniques
provides the best solution.
The Veritas NetBackup product suite provides a rich set of tools and technologies that
address these issues.

1-5
Data protection
Data protection and

disaster recovery Backup Outage
minimize data loss
Return to Service
and the time T-0 T-1 T-2
between outage and
return to service. Days Hrs Mins Secs Secs Mins Hrs Days
Recovery Point - RPO Recovery Time - RTO
Synchronous Clustering
Traditional replication
Snapshot Standard
backups Asynchronous technologies restore
Snapshot replication
technologies Bare Metal
Restore
Because no one wants to be forced to recover from a disaster, preventing damage to

your data is very important. However, bad things happen. Your job is to make sure that
any damage is repaired as quickly and completely as possible.
Even so, instantaneous perfect recovery of all of your organization’s data from a major
disaster is not always feasible. The cost of attempting to enable that goal would be
astronomical even if it were possible. Therefore, you must prioritize.
Not all data is of equal importance. You can afford to wait for some data; you can
reconstruct or even abandon some data, if necessary; and you must have some data as
soon as possible.
Data protection specialists talk about two important objectives that you should
consider:
• Your recovery point objective (RPO) describes how much you can afford to lose (or
how long it has been since you saved your data, the recovery point). Some
technologies leave longer gaps but these technologies tend to handle larger volumes
of data more cheaply than the alternatives.
• Your recovery time objective (RTO) is the length of time you can afford to take to
return to normal service. Again, different technologies have differing capabilities.
Most people implement a combination of technologies, making use of the advantages
of each. NetBackup can be configured to do exactly that.

1-6
Data protection plans
• Support backup and recovery

service level agreements
(SLAs), which define: Backup
Number/types
methods
– Recovery point objectives (RPO) of systems and
applications
– Recovery time objectives (RTO)
• Drive your backup strategy
• Test often
Planning a
• Update as conditions change backup
strategy
Recovery
methods Retention
period
A data protection plan outlines the importance of an organization’s data, and the
methods used to protect it. The plan is based on service level agreements (SLAs), which
define factors such as your recovery point objective and recovery time objective.
By defining data protection in terms of recovery, you are able to build a backup strategy
to support the data protection plan.
The backup strategy should take into account factors such as:
• The number and types of systems and applications in an environment
• The backup methods to be used to protect user systems

• Available data throughput in the environment
• Backup windows, which are times during which backup jobs can be run
• Retention periods, which define how long to keep backed-up data
• Recovery methods tested, and used when necessary
• Available budgets for hardware and software

1-7
NetBackup component definitions
• Initiates backup and recovery activities on the

media servers (NetBackup management)
Master
• Manages resources for backup and recovery
server
activities
• Tracks the backed up data
Media Write data from clients to storage devices as backup

servers images, and restores the data to the client
Clients Hosts that have data to be backed up
The systems that have data to be backed up are called clients. Veritas NetBackup Client
software must be installed on each client.
Veritas NetBackup server software that controls the environment and accesses backup
storage devices comes in a few different flavors. A single host can provide more than
one of these server roles.
• The master server controls the backup and recovery activities for the clients
assigned to it. Master servers track what files are backed up to which backup media.
Additionally, the master server centralizes services that manage and allocate the
resources required for all NetBackup operations. This includes the NetBackup
database (sometimes abbreviated as NBDB), which centralizes information about
the backup environment. The NBDB is shown on the slide as a dual-colored cylinder,
next to the master server.
• Media servers have some form of storage attached to them—either directly or
through the network. Media servers perform the writing and reading of data to and
from media (disk or tape). They combine clients’ data into GNU tar files called
backup images. One master can control several media servers.
• Clients include all hosts that have data backed up, including the media server and
master server themselves. Clients can be both physical servers, or virtual servers. In
many cases the NetBackup client software is installed on the client system, however
in some cases, such as with virtual machines, the NetBackup client software may not
be necessary.

1-8
NetBackup domain configurations
NetBackup Server NetBackup Enterprise Server
Master and media Master server
server
Media
Clients servers
NetBackup domain
Clients
Client data
Backup data
Resource Management NetBackup domain
The NetBackup server software supports two hierarchies, determined by your need, but
differentiated by the license purchased.
• NetBackup Server is a specific product licensed for smaller environments, where a
single computer plays the role of both the master server and media server.
OpsCenter may also be installed on this system as well.
• NetBackup Enterprise Server serves the needs of larger enterprises, because it
enables you to spread the load among multiple media servers controlled by a
separate master server. A NetBackup Enterprise Server license is required for each of
these server hosts.

Note that unless the environment is very small, Veritas recommends that the master
server role should not be mixed with other roles, such as a media server, OpsCenter
server, or run CPU intense applications, on the same server. If it is performing some
minimal media server tasks, definitely avoid CPU intense activities such as hosting a
Media Server Deduplication Pool (MSDP).
In either case, everything under the control of an individual master server, including the
media servers or storage hardware, is considered part of a single NetBackup domain.

1-9
NetBackup domains and OpsCenter
Site A domain Site B domain

master1 master2
OpsCenter
Master
servers
ms1 ms2 Media ms3

servers
Clients
10
The collection of clients and media servers managed by a single master is called a
NetBackup domain. NetBackup domains can be segregated based on geographic,
organizational, performance, or administrative reasons.
Sometimes you want to segregate clients into distinct collections for administrative or
performance reasons.
• With NetBackup, you can put each of these separate client groups in its own
NetBackup domain. Each domain has its own master and collection of media
servers.
• A single OpsCenter server can communicate with every master server and so help
you coordinate all of your NetBackup domains.

1-10
Topic: NetBackup concepts
After completing this topic, you will be able to define common terms used
in the NetBackup product, and describe how NetBackup backs up and
restores data.
11
After completing this topic, you will be able to define common terms used in the
NetBackup product, and describe how NetBackup backs up and restores data.

1-11
NetBackup policies
Attributes How do backups occur? Where do backup images go?
Schedules When do backups occur? Include all data or only changes? How long is backup data retained?
Clients Which systems are backed up?
Backup
Which data is backed up?
Selections
Application-
How are database backups handled? How are virtual machine backups handled?
specific tabs
12
Policies define the rules that NetBackup follows when data from clients are backed up.
A backup policy can apply to one or more clients. The best approach is to divide clients
into groups according to the backup requirements, and creating a policy for each group.
In a policy you define attributes, schedules, a client list, and a backup selections list.
• Attributes answer questions, such as: How should the files be backed up? Are there
any special backup behaviors? Where is the backup storage location?
• Schedules answer: What is the backup time and type? On which schedule should
the files be backed up? How long is the backup data retained?

• The Clients list identifies which clients to back up.
• The Backup Selections list identifies which files and data sets to back up.
More recent versions of NetBackup have introduced new policy tabs to assist with
application-specific backup settings. In NetBackup 8.1, these includes the following:
• Oracle policies includes the Oracle and Instances tab, and remove the Clients tab.
• MS-SQL policies includes the Microsoft SQL Server and Instances and Databases
tabs, and remove the Clients tab.
• VMware policies includes the VMware tab.
• Hyper-V policies includes the Hyper-V tab.

1-12
Backup storage types
Removable
media
Tapes
Disk
Client’s
backup data
(in an image)
Local SAN NetBackup appliance
disk storage or OST-based storage
Cloud
13
The backup data from a client is stored as a backup image, and must be saved
somewhere.
Removable media, such as tape, is very cost effective. Robotic libraries automate
operation, and can be shared to provide redundancy and efficient allocation of
resources. Although disk is becoming more popular, removable media still serves a
valuable purpose, such as for long term or off-site storage. Additionally, many modern
tape libraries and removable media devices have competitive performance with disk.
Images can be stored on local or networked disks for rapid access, but increasingly
complex permanent storage solutions are built around disk – such as deduplication –
which can be used alone, or in combination with removable media. You can configure
NetBackup to implement and maintain these optimized solutions.
If you have an account with a supported cloud storage service, NetBackup can store
your images there efficiently and safely.

1-13
The NetBackup catalog
Master server
NetBackup
catalog
• Stores data in a relational database (NBDB)

• Includes:
The NetBackup – Media and device data
database (NBDB) – Backup image header data
• Stores data in flat files

• Includes:
NetBackup – Policies, schedules, and job information
configuration files – Backup image file metadata
14
NetBackup catalogs are information stores that contain information about the
NetBackup configuration and backups, including records of the files that have been
backed up and the media on which the files are stored.
The NetBackup catalogs reside on the NetBackup master server and consist of the
following components:
• The NetBackup database (NBDB) is a relational database that uses SAP SQL
Anywhere. The NBDB stores data for several NetBackup services, including media
and device data, backup image headers, authentication and authorization. Bare
Metal Restore (BMR) data is also stored in a Sybase database if the BMR option is
used. Because the first service to use the relational database was the Enterprise
Media Manager in earlier releases of NetBackup, the database is sometimes
referred to as the EMM database.
• The NetBackup configuration files include policies, schedules, and other files used by
NetBackup. These are sometimes referred to as flat files because they are not stored
in a relational database, and are stored in simple files on the file system of the
NetBackup master server.
A critical NetBackup component is the image database, which stores backup image
metadata. This metadata is stored in two locations: the image header data is stored in
the relational database (NBDB), and the image file list is still stored as flat files in the
NetBackup configuration files. Because the image file lists contain the path to every file
backed up, this is usually the largest component of the NetBackup catalogs.

1-14
The data backup process
NetBackup
logs and NetBackup
reports 4
master
1 server and
catalog
NetBackup
3
media
server
2
NetBackup Storage
Client Backup
client destination
data image
15
Using NetBackup, you create policies and schedules for backing up data periodically
(such as every hour or every day). The policy and schedule information is maintained in
the NetBackup database. The policy identifies how the backups occur, where the
backups occur, when the backups occur, which clients are backed up, and which files
and directories are backed up from those clients.
The following flow is described on this diagram:
1. When a policy is run, the master server interprets the policy, allocates resources,
and connects to the requested media server.
2. The media server prepares the allocated storage resources and then passes on the
requirements of the backup to the client. The client processes the files to be backed
up and transfers them in the form of a tar backup image over the network to the
media server. The media server writes the file image to the allocated storage.
3. The media server also passes information about the backup to the master server
which then stores the information into the backup catalog.
4. During the backup status information is sent to the NetBackup master server, and
NetBackup keeps status information in various log files, enabling you to monitor or
report on the backup. Information is also pulled from the master server by the
OpsCenter server on a periodic basis, based on the OpsCenter configuration.

1-15
The data restore process
1
NetBackup
logs and NetBackup
reports 4
master
server and
2 catalog
NetBackup
media
server
3
NetBackup Storage
Client Backup
client destination
data image
16
No backup is worth anything unless the data it contains is available to be restored when
needed. Restores can be performed from the master server by an administrator to
restore the data to the destination client machine. Restores can also be performed at
the request of a user.
The restore flow is described in this diagram.
1. To restore data, use OpsCenter or the NetBackup Backup, Archive, and Restore
interface. The NetBackup master server catalog contains information on what files
and folders have been backed up, and provides the information that the
administrator will then use to select which data to restore.

2. The NetBackup master server uses the information in the NetBackup database to
identify where the backup images are stored, and uses information supplied by the
administrator to decide where they should be restored on the NetBackup client.
3. The appropriate image is retrieved from storage by the media server, and the
selected files are extracted onto the client.
4. Because NetBackup maintains status information about restores in its log files, you
can monitor and report on restores just like backups. Information is also pulled from
the master server by the OpsCenter server on a periodic basis, based on the
OpsCenter configuration.

1-16
Protect any workload
Operating systems
Most popular servers and clients, including Microsoft Windows, Linux, and UNIX files
Virtual systems
Leading hypervisors including VMware vSphere and Microsoft Hyper-V
Databases and applications

Leading databases and application platforms, including Microsoft SQL Server, Microsoft Exchange
Server, IBM DB2, Oracle, SAP, and more
Storage systems
Data at the storage system level, integrating with snapshot, replication, and NDMP facilities from EMC,
HP, Hitachi, IBM, NetApp, and others
Cloud platforms
Backup and recovery of workloads within many cloud environments, including Microsoft Azure, Amazon
Web Services, Rackspace, and more
Refer to the NetBackup Master Compatibility List at http://netbackup.com/compatibility 17
NetBackup provides a comprehensive selection of clients and agents to optimize the

performance and efficiency of your backup and recovery environment.
These provide high-performance online backup and recovery of business-critical
databases and applications, enable backup and recovery operations over storage area
networks, and deliver high levels of data security and complete system-level recovery.
Depending on your needs, NetBackup has flexible deployment options to fit your
environment and your budget.
For up-to-date information on compatibility, refer to

http://netbackup.com/compatibility.

1-17
Topic: Using the NetBackup Administration Console
After completing this topic, you will be able to navigate the NetBackup
Administration Console.
18
After completing this topic, you will be able to navigate the NetBackup Administration
Console.

1-18
Navigating the NetBackup Administration Console
Details pane
Object tree
area
19
The NetBackup Administration Console consists of two major screen areas:

• Object tree (left) pane with various navigation branches. The NetBackup
Management branch contains the utilities used to monitor activity, run and view
reports, configure policies and storage units, manage backup images, and perform
catalog backups. Host properties for the master server, media servers, and clients
can be remotely modified using this branch. The Media and Device Management
branch contains the utilities used to manage the volumes, pools, and devices that
NetBackup uses to store backups.
• Details (right) pane, which on the slide contains the configuration wizards and
details specific to the utility that is selected in the object tree pane.
The default program location for the NetBackup Administration Console is
/usr/openv/java/jnbSA on UNIX, and for Windows is located as C:\Program
Files\Veritas\Java\nbjava.bat.
Note that the NetBackup Administration Console is not natively run on a NetBackup
appliance, even if that appliance is a NetBackup master server. Instead, install the
NetBackup Administration Console on a separate system, and remotely connect to it.
Always install the latest version of the NetBackup Administration Console software, and
use the correct version of the console for the version of the master server being
interacted with.

1-19
NetBackup Administration Console: Activity Monitor
20
The Jobs tab in the Activity Monitor displays information about NetBackup queued,
active, waiting, suspended, incomplete and completed jobs. Functions you can perform
on jobs include canceling, suspending, resuming, or restarting a job.
The following tabs are visible in the details pane of the Activity Monitor:
• The Jobs tab: If you double-click a job listed under the Jobs tab, you obtain valuable
job detail information, including policy, file list, status, kilobytes written, number of
files written, percent complete, and start, elapsed, and end times, which are used to
derive kilobytes per seconds statistics.
• The Daemons tab: Provides status and control for those programs that typically start
whenever the system reboots.
• The Processes tab: Provides visibility to NetBackup process status.
• The Drives tab: Displays the status of NetBackup tape drives associated with the
NetBackup domain controlled by the master server being monitored.

1-20
Master server host properties: Global Attributes
Refer to the NetBackup Administrator’s

Guide for parameter information. bpconfig
21
This graphic shows the master server host attributes that can be configured on the
Global Attributes dialog box.
The Global Attributes properties apply to the currently selected master server. The
Global Attributes properties affect all operations for all policies and clients. The default
values are adequate for most installations but can be changed. Changes to Global
Attributes properties cascade across all component systems in the backup environment.
Note: See the Veritas NetBackup Administrator’s Guide for additional master server
properties.

1-21
NetBackup command locations
• NetBackup programs, client commands, notification scripts
– UNIX: /usr/openv/netbackup/bin
– Windows: install_path\NetBackup\bin
• NetBackup administration server only commands
– UNIX: /usr/openv/netbackup/bin/admincmd
– Windows: install_path\NetBackup\bin\admincmd
• Media and device management programs and utilities
– UNIX: /usr/openv/volmgr/bin
– Windows: install_path\VolMgr\bin
• Other utilities and scripts
– UNIX: /usr/openv/netbackup/bin/goodies
– Windows: install_path\NetBackup\bin\goodies
• Command help
– UNIX: Online man pages
– Windows/UNIX: Veritas NetBackup Commands Reference Guide
22
Commands can be issued interactively to administer NetBackup without using a graphic

interface, such as the NetBackup Administration Console. NetBackup commands are
often used in UNIX shell or Windows PowerShell. They can be used as a part of batch
scripts to perform reusable custom operations.
Some commands, such as those found in the admincmd directory, are only available to
NetBackup administration servers. By default, this is the master server, but also all
media servers designated as Additional Servers in the host properties (SERVERS in the
bp.conf configuration file). Media servers designated as simply Media Servers in the
host properties (MEDIA_SERVERS in bp.conf) will not have permission to run these
commands.
On Windows, the default installation path for install_path is C:\Program
Files\VERITAS. To simplify command execution, append the paths shown on the
slide to your PATH environment variable.
Command Help
Command help is available as follows:
• UNIX: Use the online man pages and ensure that the MANPATH includes
/usr/openv/man or use the Veritas NetBackup Commands Reference Guide.
• Windows: Use the Veritas NetBackup Commands Reference Guide.

1-22
Topic: NetBackup appliance overview
After completing this topic, you will be able to describe the NetBackup
appliance offerings.
23
After completing this topic, you will be able to describe the NetBackup appliance
offerings.

1-23
What is the NetBackup appliance?
NetBackup with Deduplication
Symantec Data Center Security
Built-in WAN Optimization

Veritas Storage Foundation
Veritas Hardened Operating

System
Optimized Hardware
Redundant Storage
Single Patch Updates
24
A computer appliance is a separate and discrete hardware device with integrated

software and firmware, specifically designed to provide a specific computing resource.
A NetBackup appliance is more than just NetBackup pre-installed on hardware. It is a
turnkey hardware and software solution that is designed to install in minutes, decrease
operational costs and reduce complexity.
Advantages of NetBackup appliances include:
• Redundant storage in RAID6 for storing backups
• Hardware optimally configured by Veritas, with help from Intel, for NetBackup’s
predictable and consistent performance.
• Storage Foundation at no additional cost, which provides an industry-leading storage
management infrastructure, built for high-performance and resiliency.
• A Linux-based operating system, optimized for NetBackup and hardened by Veritas,
eliminating the cost of deploying and maintaining the operating system and
applications.
• A built-in WAN Optimization driver that provides the ability to replicate to
appliances on remote sites or to the cloud, up to 10 times faster over high latency
links.
• Symantec Data Center Security, which provides non-signature based Host Intrusion
Prevention, zero-day attacks, user and device controls, and more with, pre-defined
policies.
• Single patch updates that upgrade everything in the appliance.

1-24
NetBackup Appliance Family
Up to
1-250TB Up to 1374 TB*
1PB
Up to 1920 TB*
Up to 294TB
Media Server Cloud Catalyst
14TB-27TB 240TB
229TB
0.5-16TB
Media Server
4TB
Master/Media Media Server
Server Enterprise Appliance with storage Enterprise Appliance with storage
Master Server with storage
NetBackup 5330 NetBackup 5340

NetBackup NetBackup 5240 Maximum Performance,
Virtual Resilience and Scale Resilience and Scale
Appliances Versatile Implementation
High Availability (Optional) High Availability (Optional)
* Maximum MSDP Size 916 TB in Version 3.1

25
NetBackup integrated Appliances reduce complexity by eliminating the need to analyze,

research, and procure separate infrastructure components in order to protect data.
The current appliance product family consists of:
• Virtual Appliances: a scalable data protection solution designed to integrate

NetBackup solutions into your virtual environment. They provide an alternative to
physical appliance solutions to let you leverage your existing virtual infrastructure
and NetBackup expertise. Master/media virtual appliances are a low-cost solution for
environments with smaller data protection requirements that require minimal on-site
infrastructure management expertise. Media server virtual appliances can scale up in
the number of instances and storage capacity to meet the growing requirement of
data protection in data centers. Either type of virtual appliance can replicate data to
other sites for disaster recovery.
• NetBackup 5240: A scalable integrated backup appliance that can function as either a
master or a media server and can scale from 4TB to 294TB of storage.
• NetBackup 5240 CloudCatalyst: A dedicated cloud gateway that uses MSDP

deduplication technology to upload deduplicated data to the cloud. The data is
uploaded by a CloudCatalyst storage server, which first stores data in a local cache
before uploading it to cloud storage. This cloud storage server is a dedicated host
that can be either a NetBackup appliance or a media server configured for NetBackup
CloudCatalyst.

1-25
• NetBackup 5330: A high-performance hardware and software storage system that
scales to a total of 1374 TB of usable backup capacity. The maximum MSDP pool size
in 3.1 is 916 TB; additional capacity can be used for AdvancedDisk and/or Copilot
shares. It consists of a 2U NetBackup 5330 Appliance compute node and one
externally attached 4U Primary Storage Shelf. You can add up to five optional 4U
Expansion Storage Shelves to meet your storage requirements. Veritas also offers a
high availability (HA) solution for NetBackup 5330 Appliance systems consisting of
two connected compute nodes that connect to common storage in an active/active
configuration.
• NetBackup 5340: Offering maximum performance and scalability, The NetBackup

5340 Appliance is a hardware and software storage system that can scale up to a
total of 1920TB of usable backup capacity (916TB of which can be used for MSDP in
3,1). It consists of one 2U NetBackup 5340 Appliance compute node and one
required externally attached 5U84 Primary Storage Shelf for data storage purposes.
By itself, the NetBackup 5340 Appliance compute node does not provide internal disk
space for data storage. You can add up to three optional 5U84 Expansion Storage
Shelves if you require additional data storage space. Veritas also offers a high
availability (HA) solution for NetBackup 5340 Appliance systems consisting of two
connected compute nodes that connect to common storage in an active/active
configuration.

1-26
NetBackup 5240 appliance
• Functions as a master or media server NetBacku
p
5240
• Has multiple I/O options: Appliance
Number Type (2U)
4-8 1 GbE ports
2-8 10 GbE ports
0-10 8 Gb Fibre ports 5240
0-2 10 Gb iSCSI ports Storage Shelf
• Storage options: (2U)
– 4, 14 or 27 TB internal storage
– Expandable external storage with up to six Veritas 2U12
49TB Storage Shelves
– Up to 294 TB external storage total
– Configured as MSDP, AdvancedDisk, and Share (Copilot)
• The 5240 CloudCatalyst is a 4TB 5240 that supports a
cloud storage bucket of up to 1PB.
27
The NetBackup 5240 fulfills the needs of the low to mid-range performance and
capacity tiers in the NetBackup Appliance product line. It improves performance and
greatly increases the maximum capacity from the previous generation, the NetBackup
5230. As with the previous NBU52xx generations, the NetBackup 5240 appliance
supports internal storage as well as external storage shelves, and can be configured as
either media server, master server or both.
The NetBackup 5240 storage shelf supports SAS-3 as well as SES-3, significantly
improving bus speed as well as supportability. Each shelf formats to 49.14 TB. Since the
5240 supports up to 6 shelves, total storage options include 53 TB, 102 TB, 151 TB, 200
TB, 249 TB and 298 TB. This assumes the use of a 4 TB appliance, which is the norm
when using expansion shelves. The 14 TB and 27 TB appliances are designed to be used
as standalone appliances for environments which need more than 4 TB of dedupe
storage but less than 49 TB.

1-27
NetBackup 5340 appliance
5340
• Functions as a media server Veritas
NetBackup TM
Compute Unit
• Has multiple I/O options: VERITAS 5340
(2U)
Number Type
4 1 GbE ports
✓ ✓
X X
2-10 10 GbE/iSCSI ports Z

TM
Z
0-8 8 Gb Fibre ports

00
✓
Primary
X
Storage Shelf
• Storage options:
✓ ✓
X X
(5U)
Z Z
– No internal storage for backups

– Primary storage shelf required; Up to three Expansion
storage shelves
– Up to 1920 TB storage total (120-480 TB per shelf) ✓
X
Z
✓
X
Z
TM
– Configured as MSDP, AdvancedDisk, and Share (Copilot) 00

Expansion
– Maximum MSDP Size is 916 TB in 3.1
✓
X
Storage Shelf
✓ ✓
X
Z
X
Z (5U)
28
Enterprise scale NetBackup 5330 appliances start at 120TB of usable disk space and are
expandable up to 1920 TB making them ideal for large data centers.
NetBackup 5340 appliances can be deployed as media servers complementing either a
5240 appliance master server, or a traditional master server. addition to increased
capacity and performance, the 5340 has Dual RAID controllers and multiple data paths
to deliver greater data protection and system availability.

1-28
Understanding NetBackup appliances
• Based on Front-End Terabytes (FETB)

Licensing • Separate from hardware cost
• Offers numerous advantages (replication, retention, refresh)
• Defined by hardware, firmware and software

Versioning • Uses an appliance-specific version number
• Correspond to a specific NetBackup version
• Software and appliance functionality is normally equivalent, but may not be identical
Compatibility • Refer to http://netbackup.com/compatibility, in the NetBackup Appliances section.
29
When comparing do-it-yourself NetBackup environments to using NetBackup

appliances, there are some key differences and similarities to consider.
NetBackup Appliance Licensing
All models of NetBackup appliances use the Data Protection and Optimization Option
(DPOO) license, which is based on front-end Terabytes (FETB) deduplicated by
NetBackup. Unlike most appliance vendors, Veritas keeps licensing costs separate from
hardware costs. This adds value and flexibility to Veritas appliance offerings.
When licensing deduplication from Veritas, you pay only once for each TB of data
protected, regardless of how many copies you make. This can result in drastically
reduced costs for appliances, disk pools or tape libraries used solely to hold replicated
data.
Licenses are perpetual and transferable. Which means you don’t pay the cost of the
deduplication engine again every time you refresh hardware. It also means that existing
DPOO licenses for disk pools can be used if you migrate from legacy servers to
appliances.
Licenses are based on the amount of data you protect, not the capacity of the
appliance. Which means you can buy an appliance with extra storage capacity with an
eye towards future growth without paying for storage you are not using.
5230 Appliances can also be licensed as traditional Master or Media servers if, for
example, you will not be using the appliance to deduplicate any data.

1-29
NetBackup Appliance Versioning
NetBackup appliances are Veritas-defined platforms of hardware, firmware and
software. This includes driver revisions, OS levels and patches of all devices or software
components. There are no modifications allowed without the express instructions of
Veritas Support. Modifications to the appliance in any fashion without express
instructions from Veritas Support will void warranty and result in an unsupported
configuration.
Only supported appliance-specific patches may be applied to the NetBackup appliances.
Upgrades to NetBackup appliances must follow supported procedures as given in
NetBackup documentation. Never apply operating system or individual software
updates except under the guidance of NetBackup Support.
NetBackup Appliance Compatibility
If you use a separate media server to backup the master server catalog, it must use the
same NetBackup version as the master server. See the Veritas NetBackup Installation
Guide for information about mixed version support.
Unless otherwise noted, the appliance has the same compatibility with other agents or
products as the underlying NetBackup product. For example: A 5240 Appliance master
server running 3.1 has the same compatibility as a non-appliance master server running
8.1, unless otherwise noted.
There are a few functions that are not supported in a NetBackup appliance. For
information about NetBackup appliances compatibility, see the Article 100002560:
NetBackup Appliance Compatibility Notes, found online at
http://www.veritas.com/docs/100002560 .
Refer to the NetBackup Master Compatibility List at
http://netbackup.com/compatibility, to view up-to-date information about supported
functionality, including minimum required versions and additional notes.

1-30
Topic: Using NetBackup OpsCenter
After completing this topic, you will be able to navigate the OpsCenter
console.
31
After completing this topic, you will be able to navigate the OpsCenter console.

1-31
Understanding the OpsCenter Interface
• Monitors and reports on NetBackup

operations across multiple master servers
• Uses a web-based console
• Available without an additional license
• Runs on multiple platforms
• Separate installation from NetBackup
• Cannot run on the master server
32
NetBackup OpsCenter is a web-based software application that helps organizations by

providing visibility into their data protection environment, including visibility into
NetBackup and NetBackup appliances.
In its core form, OpsCenter displays multi-level views of backup and archive resources
and produces reports for tracking backup results and other aspects of an environment.
OpsCenter is designed to be used by multiple audiences within an organization who
need to manage or monitor IT environments, as well as backup administrators and
operators who perform daily backup duties. This core form of OpsCenter is available
without an additional license.

The OpsCenter server is a web server, and the user interface is accessed through a
standard web browser. OpsCenter server software is included with NetBackup software,
but is installed independently. Additionally, NetBackup 8.0 and later restricts the
OpsCenter software from running on a NetBackup master server.
Although not strictly required by NetBackup, some advanced features are only
accessible through OpsCenter.
When run using the optionally licensed OpsCenter Analytics option, OpsCenter has
additional reporting functionality, as is discussed elsewhere in this lesson.

1-32
Accessing the OpsCenter console
Default OpsCenter address:

https://opscenterhost/opscenter
33
To access the OpsCenter console, start a web browser on a system that has network
connectivity to the OpsCenter server. Type the following URL:
https://opscenterhost/opscenter where opscenterhost is the fully qualified domain
name of the OpsCenter server or the IP address of the OpsCenter server.
Note: If there is a conflict due to an already existing Web server (for example, IIS on
Windows), OpsCenter may have chosen a different port number to avoid conflict. The
default OpsCenter web address may use this non-default port number; for example:
https://opscenterhost:port/opscenter. For more information, see the NetBackup
OpsCenter Administrator’s Guide.

To log on to the OpsCenter Console, supply logon credentials as follows:
1. Enter a user name and password, and select a domain from the Domain drop-down
list. For the initial login by an administrator, use the following values:
• User Name: admin
• Password: password
• Domain: OpsCenterUsers(vx)
2. Click Log On.
3. After the initial log on, change the user name and password. To change existing
passwords, navigate to Settings > User Preferences > MyProfile in OpsCenter.

1-33
Configuring OpsCenter data collection for NetBackup
34
Before you can use OpsCenter to monitor and manage your NetBackup environment,
you must configure data collection for NetBackup:
1. Add a master server to the OpsCenter console:
a. In the OpsCenter console, select Settings > Configurations > NetBackup.
b. Click Add, and fill in the fields. Optionally click the Test Connection button to
ensure the data is correct.
2. Enable data collection for a master server:
a. Use the check box to select one or more master servers from the Master Server
Name column.
b. Click Enable Data Collection.

1-34
Comparing OpsCenter and OpsCenter Analytics
OpsCenter OpsCenter Analytics
Advanced business-level reporting including custom and

Operational reporting
custom SQL reports.
Reporting data for last 60 days No time limit on reporting data
No additional license required Licensed option
35
Veritas OpsCenter Analytics is a separately licensed option available for OpsCenter.

Although no license is necessary to use the base OpsCenter product, the Analytics
license unlocks the following additional capabilities in OpsCenter.
• With OpsCenter, you can only perform operational reporting; with OpsCenter
Analytics, advanced, business-level reporting is available. This includes the use of
existing reports as well as custom and custom SQL reports
• There is a difference between reporting data availability in OpsCenter and
OpsCenter Analytics. The unlicensed product enables reporting on data from the
past 60 days; the licensed option has no limit on the age of reporting data.
This course only covers OpsCenter. For additional information on using OpsCenter
Analytics, see the Veritas OpsCenter Administrator’s Guide and Veritas Education’s
OpsCenter training.
Note: In prior releases of OpsCenter, the Java View Builder was only available with
OpsCenter Analytics. In OpsCenter 7.5 and later, the Java View Builder is included with
the base product.

1-35
Lesson summary
• Key points
– In this lesson, you learned concepts about how to protect the data in your environment using
NetBackup.
– You are also aware of basic terms that relate to NetBackup, and can identify the major NetBackup
options and agents used to customize your backup environment.
– In addition, you learned to use the NetBackup Administration Console.
– Finally, you learned to describe the NetBackup Appliance offerings, and about the OpsCenter console.
• Reference materials
– NetBackup Administrator’s Guide
– NetBackup Release Notes
– NetBackup Commands Reference Guide
– NetBackup OpsCenter Administrator’s Guide
– http://www.veritas.com/support
36
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.

1-36
Lab 1: Introduction to NetBackup
Lab objectives
• Identify systems in the lab environment
• Power on/off lab systems (as necessary)
• Access the desktops of remote lab systems
• Launch the NetBackup Administration Console and log in to your NetBackup master
server
• Examine the NetBackup Administration Console layout
• Use the NetBackup Administration Console to…
– Connect to your NetBackup master server
– View NetBackup server licenses
– Locate common configuration and management tasks
– Initiate and monitor a backup job
37
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.

1-37
What did you learn?
You are about to be asked a series
of questions related to the current
lesson.
38
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.

1-38
Question: Considerations in data protection planning
What are considerations in data protection planning?
A. Protecting systems and applications

B. Maximizing the availability of data
C. Backup window availability
D. Retention periods
E. All of the above
39

1-39
Answer: Considerations in data protection planning
What are considerations in data protection planning?
A. Protecting systems and applications

B. Maximizing the availability of data
C. Backup window availability
D. Retention periods
E. All of the above
The correct answer is E.
40

1-40
Question: NetBackup commands for scripts
NetBackup commands can be used in UNIX shell or Windows batch scripts to perform
reusable custom operations.
A. True
B. False
41

1-41
Answer: NetBackup commands for scripts
NetBackup commands can be used in UNIX shell or Windows batch scripts to perform
reusable custom operations.
A. True
B. False
The correct answer is A.
42

1-42
Question: About NetBackup OpsCenter
Which statement is true about NetBackup OpsCenter?
A. OpsCenter is a premium option from NetBackup that must be purchased separately.

B. Basic OpsCenter functionality is included with NetBackup.
C. OpsCenter and OpsCenter Analytics are both 100% free.
D. OpsCenter cannot be used to manage NetBackup versions prior to 7.5.
43

1-43
Answer: About NetBackup OpsCenter
Which statement is true about OpsCenter?
A. OpsCenter is a premium option from NetBackup that must be purchased separately.

B. Basic OpsCenter functionality is included with NetBackup.
C. OpsCenter and OpsCenter Analytics are both 100% free.
D. OpsCenter cannot be used to manage NetBackup versions prior to 7.5.
The correct answer is B. Basic OpsCenter functionality is included with NetBackup, and additional functionality can be
added by purchasing the OpsCenter Analytics option.
44

1-44
End of presentation
1-45
Lesson 2: Configuring NetBackup Storage
This is the “Configuring NetBackup Storage” lesson in the “Veritas NetBackup 8.1:

2-1
Policies
This lesson is the second lesson in this course.


2-2
Lesson objectives
Topic Objective
Define the terms storage device, storage unit, and storage unit
NetBackup storage device concepts
group.
Configuring and managing a basic
Configure and manage a basic disk storage unit.
disk storage unit
Configuring storage unit groups Configure storage unit groups.

2-3
Topic: NetBackup storage device concepts
After completing this topic, you will be able to define the terms storage
device, storage unit, and storage unit group.
After completing this topic, you will be able to define the terms storage device, storage
unit, and storage unit group.

2-4
NetBackup storage concepts
Storage device
• Physical tape and disk devices to which data is written to and restored from
Storage unit
• A logical entity that NetBackup associates with physical storage

• Can reference tape drives, a path to a disk volume, or a disk pool
• Identify the media server(s) and the physical storage
It is important that you know the differences between storage devices, storage units,
storage unit groups, and storage lifecycle policies, so that you can plan and configure
NetBackup to operate most effectively.
• Storage devices are tapes and disk devices to which data can be written and stored.
When discussing storage devices, we are normally referring to the physical devices
as seen by the server.
• Storage units are logical entities that refer to a storage device of a specific type.
Properties of a storage unit define how data is written to media. Additionally,
storage units are a way of defining both the media server(s) and storage destination
for a backup. Note that a storage unit can be tape drives, a path to a disk volume, or
a disk pool (which can be deduplicated disk or cloud storage). Storage units are used
as a backup destination, a location where a backup policy sends a backup.
• Storage unit groups and Storage lifecycle policies (SLPs) are two additional storage
destinations that will be described. Storage unit groups are discussed elsewhere in
this lesson, and SLPs are discussed in the Duplicating Backups lesson.
Within a backup policy, you define a storage destination, which is where NetBackup will
send the backup data. This can be a storage unit, a storage unit group, or a storage
lifecycle policy, depending on your needs . You cannot send a backup directly to a
storage device that is not configured as a storage unit.

2-5
Storage devices and storage units
Master server
ms1_bdisk_STU ms2_bdisk_STU ms2_tape_STU
Media Media Tape

library
server 1 Basic disk Basic disk server 2
storage storage
Local Area Network

NetBackup
clients
When backup jobs are run, the storage unit specifies:

• Which media server copies the data from the client to the storage device
• Which storage device is used for the backup
During a backup, NetBackup stores the backup data on the storage units that were set
up during configuration.
In the example on this slide, the storage unit specifies which media server backs up the
data (Media server 1 or Media server 2) and where the backups are written (the basic
disk storage or the tape library).

Storage units for tape libraries and robots are called Media Manager storage units, and
are discussed later in this course, in the Configuring Tape Storage lesson.

2-6
NetBackup disk storage types
BasicDisk Uses a directory to store backup data.

• Lesson: Configuring NetBackup Storage
• Document: NetBackup Administrator’s Guide Covered in this lesson
• License: None required
AdvancedDisk Uses a disk pool (a collection of disk volumes).

• Lesson: Configuring Disk Pools
• Document: NetBackup AdvancedDisk Solutions Guide
• License: NetBackup Data Protection Optimization Option
OpenStorage Used with storage supporting Veritas OpenStorage API.

• Lesson: Configuring Disk Pools and Duplicating Backups Using Storage Lifecycle Policies
• Document: NetBackup OpenStorage Solutions Guide for Disk
PureDisk Uses a Media Server Deduplication Pool (MSDP).

• Lesson: Configuring Media Server Deduplication
• Document: NetBackup Deduplication Guide
The slide lists disk storage types in NetBackup (listed by the corresponding disk type
identification categories used in NetBackup). Disk storage types include:
• BasicDisk consists of a directory or folder in a file system that is locally- or network-
attached to the media server. This disk type does not require any additional licenses.
• AdvancedDisk consists of a disk pool, which is a collection of disk volumes, that is
managed by a NetBackup media server or NetBackup appliance. AdvancedDisk has
better management capabilities than BasicDisk.
• OpenStorage uses the Veritas OpenStorage API to control functions and integrate
backup functionality for intelligent third-party disk appliances that support this API.
• PureDisk consists of a specialized disk pool and services that perform deduplication
of backup storage, and reside on a NetBackup media server or NetBackup appliance.
BasicDisk is included with NetBackup and does not require additional licensing. The
other disk types require the NetBackup Data Protection Optimization Option.
This lesson only covers the configuration of BasicDisk. For other disk types, refer to the
appropriate lessons in this course or the appropriate NetBackup documentation, as
listed on the slide.

2-7
Topic: Configuring and managing a basic disk storage unit
After completing this topic, you will be able to configure and manage a
basic disk storage unit.
After completing this topic, you will be able to configure and manage a basic disk
storage unit.

2-8
Adding a basic disk storage unit
bpstuadd -label
9
To configure storage units, or to copy an existing storage unit configuration and use it as
a template for a new storage unit, perform the following steps:
1. In the object tree pane of the NetBackup Administration Console, expand
NetBackup Management > Storage.
Storage unit information is displayed in the details pane.
2. Add the storage unit using one of the following methods:
• Select Actions > New > New Storage Unit.
• Right-click Storage Units and select New Storage Unit.

• Copy and then modify the properties of an existing storage unit:
Right-click a storage unit in the details pane and select Copy.
3. Complete the entries in the New Storage Unit dialog box.
4. Click OK to add the storage unit to the configuration.
Configuring storage units from the command line
You can create and configure storage units using the bpstuadd command. For a full
explanation of this command, including syntax, see the NetBackup Commands
Reference Guide.

2-9
Configuring a basic disk storage unit
bpstuadd -label
10
When creating a Disk storage unit type, you must supply the following properties:
• Storage unit name: A unique name that is used in backup policies and schedules.
• Storage unit type: The type of storage that this storage unit uses, for example, Disk.
• On demand only: Specifies whether the storage unit is only available when a policy
attribute or policy schedule is explicitly configured to use this storage unit. The
storage unit will not be used when the Any Available storage destination is selected.
• Disk type: Specifies the type of disk storage unit to be created. By default: BasicDisk.
• Media server: Specifies the name of the controlling media server.

• Absolute pathname to directory: Specifies the absolute path to the file system.
• View Properties button: Display information about capacity and remaining space.
• This directory can exist on the root file system or system disk: Allows the directory
to exist on the root file system (UNIX) or system disk (Windows).
• Maximum concurrent jobs: The maximum number of backups that NetBackup can
concurrently send to this disk.
• Reduce fragment size to: Specifies (in MB) the largest fragments (underlying file
sizes) created when storing backups.
• High water mark: The threshold that signals that the disk should be considered full.
• Low water mark and Enable Temporary Staging Area: Used for disk staging storage
units. Refer to the NetBackup Administrator’s Guide.

2-10
Viewing a basic disk storage unit properties
bpstulist
11
After initially configuring a basic disk storage unit, you can subsequently open the basic
disk storage unit to change existing parameters (such as the maximum concurrent jobs,
or water marks). You will notice that certain parameters cannot be modified, such as the
storage unit name, storage unit type, or disk type.
Clicking on the View Properties button shows details for the file system on which the
basic disk folder resides, such as capacity and available space.

2-11
Disk reports for BasicDisk
12
In the NetBackup Administration Console, under NetBackup Management, there is a

section for Reports. Under Disk Reports there are a number of reports that can provide
information on basic disk storage:
• Images On Disk: This report shows which backup images exist on the storage units
selected.
• Disk Logs: This report shows log entries for the storage units selected.
• Disk Storage Unit Status: This report summarizes properties and capacity
information for the storage units selected.

Notice that these reports can be used for various disk storage types, however by
selecting a Disk Type of BasicDisk, you can view only the information for basic disk
storage units.

2-12
Topic: Configuring storage unit groups
After completing this topic, you will be able to configure storage unit
groups.
13
After completing this topic, you will be able to configure storage unit groups.

2-13
Understanding storage unit groups
Storage device
• Physical tape and disk devices to which data is written to and restored from
Storage unit
• A logical entity that NetBackup associates with physical storage

• Can reference tape drives, a path to a disk volume, or a disk pool
• Identify the media server(s) and the physical storage
Storage unit group
• Lets you identify multiple storage units as belonging to a single group

• Specifies the order and manner in which storage units are used
14
It is important that you know the differences between storage devices, storage units,
storage unit groups, and storage lifecycle policies, so that you can plan and configure
NetBackup to operate most effectively.
• Storage devices are tapes and disk devices to which data can be written to, stored,
and restored from. When discussing storage devices, we are normally referring to
the physical devices as seen by the server.
• Storage units are logical entities that refer to a storage device of a specific type.
Properties of a storage unit define how data is written to media.
• Storage unit groups are two or more storage units that have been grouped together.
This enables you to address multiple storage units as a single entity when creating a
policy. You may set the priority of the storage units within the group, and the type of
load balancing and failover behavior desired.
• Storage lifecycle policies (SLP) are additional backup destinations with
comprehensive storage plans that include supporting multiple destinations,
including snapshots, duplications, and replications. SLPs are discussed in the
Duplicating Backups lesson.
Within a backup policy, you define a storage destination, which is where NetBackup will
send the backup data. This can be a storage unit, a storage unit group, or a storage
lifecycle policy, depending on your needs . You cannot send a backup directly to a
storage device that is not configured as a storage unit.

2-14
On demand only and any available
Policy1: Policy2: Policy3:

Storage = ms1_bdisk_STU Storage = Any_available Storage = ms3_tape_STU
✓ ✓ ✓ ✓ ✓
• Note: Using any_available

is not a best practice.
ms1_bdisk_STU ms1_tape_STU ms2_tape_STU ms3_tape_STU • Veritas recommends that
you use storage unit
On Demand groups to provide multiple
Only Any Available destination options for a
backup.
15
Prior to the concept of storage unit groups, NetBackup used functions known as On
demand only and Any available to be able to send backups to different storage units,
based on availability.
When configuring a backup policy, if you select Any_available as the storage destination
for your backup, backup data is directed to an available storage unit designated as Any
available. These are all storage units that are not marked as On demand only.
NetBackup tries locally attached storage units first, and if none are found, the storage
units are tried in alphabetical order. NetBackup uses the first storage unit that meets the
following requirements:
• The storage unit must not be designated as on demand only.
• The storage unit must have available drives.
• The storage unit must have available storage (tape or disk resources) resources.
When you configure a storage unit as On demand only, the storage unit is only used if it
is specified directly within the backup policy, or backup policy schedule.
Since the introduction of storage unit groups in NetBackup, it is no longer
recommended to use Any available as the means of sending backups to different
storage units.

2-15
Creating a new storage unit group
Allows configuration of multiple storage units

which act as a single destination for backup jobs.
bpstuadd -group
16
A storage unit group allows you to configure multiple storage units which act as a single
destination for backup jobs.
To create a new storage unit group, navigate to NetBackup Management > Storage >
Storage Unit Group, and select Action > New Storage Unit Group. Similarly, you can
right-click in the console and select New Storage Unit Group or click on the new storage
unit group button.
The bpstuadd command can be used to create storage unit groups. See the NetBackup
Commands guide for syntax and details.

2-16
Storage unit group configuration
For Media Server Load Balancing, refer

to the Configuring Disk Pools lesson
17
To configure a storage unit group, provide a unique storage unit group name, and select
which storage units to add to that group. The order in which storage units are used
within a group depends on the storage unit selection option
In the Storage unit selection area, you choose how storage units are selected within the
group as follows:
• Prioritized: Choose the first storage unit in the list that is not busy, down, or out of
media.
• Failover: Choose the first storage unit in the list that is not down or out of media.
• Round Robin: Choose the least recently selected storage unit in the list.
• Media Server Load Balancing: Choose the best available media server based on a
ranking system.
Note that the Media Server Load Balancing selection does not support basic disk
storage, and is discussed in more detail in the Configuring Disk Pools lesson.

2-17
Understanding prioritized storage unit groups
ms1 ms2 ms3
Group priority:
1. ms1_tape_STU
2. ms2_tape_STU
3. ms3_tape_STU
ms1_tape_STU ms2_tape_STU ms3_tape_STU
Job 1 Job 3 Job 5
Job 2 Job 4 Job 6
Job 7
Job 8
18
The total number of concurrent jobs that can go to a specific storage unit will depend on
the storage unit’s configuration, specifically the maximum concurrent jobs that is
configured. The slide shows tape-based storage units (a library with two tape drives)
connected to each media server, however they could just as easily be disk-based storage
that accept two concurrent backups.
Prioritized storage unit groups choose the first storage unit in the list that is not busy
with other jobs, down (physically unavailable), or out of tape media (in the case of tape
libraries). It then fills that storage unit with active jobs, and then moves on to the next
available storage unit in the list. If all storage units are busy, any subsequent jobs will
queue, and wait for the next available storage unit in the group.
In the example on the slide, media server ms1 is shown with more memory and system
resources than media server ms2, which additionally has more resources than media
server ms3. Using a prioritized storage unit group means that ms1_tape_STU will always
be used first, until it is busy. Storage unit ms2_tape_STU will fill with jobs next, and
finally ms3_tape_STU.

2-18
Understanding round robin storage unit groups
ms1 ms2 ms3
Group priority:
1. ms1_tape_STU
2. ms2_tape_STU
3. ms3_tape_STU
ms1_tape_STU ms2_tape_STU ms3_tape_STU
Job 1 Job 2 Job 3
Job 4 Job 5 Job 6
Job 7
Job 8
19
Round robin storage unit groups choose the least recently used storage unit in the list
that is available.
In the example on the slide, all three media servers are shown with identical memory
and system resources, and using a round robin storage unit group means that initially
the jobs will be distributed evenly amongst the storage units. Once all storage units are
in use, additional jobs will queue and wait for any available storage unit in the group.

2-19
Understanding failover storage unit groups
ms1 ms2
Group priority:
1. ms1_bdisk_STU
2. ms2_tape_STU
Only used if primary
ms1_bdisk_STU* ms2_tape_STU storage unit is down or
Job 1 out of media
Job 2
Job 3
Job 4
* The ms1_bdisk_STU storage unit has Maximum concurrent job = 2 20
A failover storage unit group chooses the first storage unit in the list that is not down or
out of media. All other jobs will queue waiting for this storage unit, even if it is busy. If
the storage unit ever goes down (or runs out of media), then the jobs will fail over to
the next available storage unit in the group.

2-20
Spanning backups in basic disk storage unit groups
• Basic disk storage units must be within a storage
unit group. STU-A
• Storage units must share the same media server. Spanning
– A disk staging storage unit cannot span to another supported
storage unit or be a target storage unit.
STU-B
• Backup policy must target the storage unit group.
STU group 1
Spanning STU-C
not
supported
STU-D
STU group 2
21
A backup may span storage units if a disk full condition is detected. Backups can span
from one BasicDisk storage unit to another BasicDisk storage unit if the storage units are
in the same storage unit group. The storage units must also share the same media
server.
The following destinations support disk spanning:
• A BasicDisk storage unit spanning to a BasicDisk storage unit. These storage units
must be within a storage unit group.
• An OpenStorage or AdvancedDisk volume spanning to another volume in the disk

pool. These storage units innately support backup images spanning to multiple
volumes, since they use disk pools. This is discussed in further detail in the
Configuring Disk Pools lesson.
For disk spanning to occur, the following conditions must be met:
• The storage units must share the same media server.
• The backup policy must target the storage unit group.
• A disk staging storage unit cannot span to another storage unit. Also, a disk staging
storage unit is not eligible as a target for disk spanning.
• Disk spanning is not supported on network-based file systems (NFS, CIFS).

2-21
Enabling basic disk spanning
22
Basic disk spanning is enabled in the media server’s Host Properties under Media, using
the Allow backups to span disk property.
The default is that this property is enabled. The Allow backups to span disk property
does not apply to AdvancedDisk or OpenStorage storage units, since backups span disk
volumes within disk pools automatically. These storage units are discussed in more
detail in the Configuring Disk Pools lesson.

2-22
Reporting on storage units and storage unit groups summary
Type of Information Administration Console Command Line OpsCenter

Storage units Storage > Storage Units bpstulist -U Manage > Storage >
Storage Unit
Storage unit groups Storage > Storage Unit bpstulist –go –U Manage > Storage >
Groups Storage Unit Group
View free space in a nbdevquery –listdv –D

BasicDisk storage unit
23
The table on this slide summarizes the storage unit reporting tools using the NetBackup
Administration Console, NetBackup commands, and OpsCenter.

2-23
Lesson summary
• Key points
– In this lesson, you learned about disk-based storage and how it is used.
– You also learned how to configure basic disk storage units, monitor the status of, and view reports for,
basic disk storage.
– Finally, you learned how to configure storage unit groups.
– NetBackup System Administrator’s Guide
24

2-24
Lab 2: Configuring NetBackup Storage
Lab objectives
• View disk storage on a NetBackup server system
• Use the NetBackup Administration Console to…
– View an existing basic disk storage unit
– Configure a basic disk storage unit and verify its creation
– Configure a storage unit group and verify its creation

2-25
What did you learn?
lesson.
26
current lesson.

2-26
Question: A logical destination for backups
What is a logical destination for a NetBackup client's backup data?
A. Catalog
B. Policy
C. Storage unit
D. Selection list
27

2-27
Answer: A logical destination for backups
What is a logical destination for a NetBackup client's backup data?
A. Catalog
B. Policy
C. Storage unit
D. Selection list
The correct answer is C. The logical destinations for a NetBackup client’s data include storage units, storage unit groups,
and storage lifecycle policies.
28

2-28
Question: Storage unit group selections
Which of the following is not a selection type of storage unit groups?
A. Failover
B. Priority
C. First-in First-out
D. Round Robin
29

2-29
Answer: Storage unit group configuration
Which of the following is not a selection type of storage unit groups?
A. Failover
B. Priority
C. First-in First-out
D. Round Robin
The correct answer is C. The four storage unit group selections include Failover, Priority, Round Robin, and Media Server
Load Balancing.
30

2-30
Question: Spanning in basic disk storage unit groups
To support spanning backups in basic disk storage unit groups, what needs to be
performed?
A. Enable unrestricted media sharing, in the host properties

B. Allow backups to span disks, in the host properties
C. Ensure each basic disk storage unit is configured on a separate media server
D. Configure the storage unit selection: Spanning
31

2-31
Answer: Spanning in basic disk storage unit groups
To support spanning backups in basic disk storage unit groups, what needs to be
performed?
A. Enable unrestricted media sharing, in the host properties

B. Allow backups to span disks, in the host properties
C. Ensure each basic disk storage unit is configured on a separate media server
D. Configure the storage unit selection: Spanning
The correct answer is B. Configure Allow backups to span disks in the media server host properties. Ensure that all the
basic disk storage units is configured on the same media server.
32

2-32
End of presentation
2-33
Lesson 3: Configuring Policies
This is the “Configuring Policies and Schedules” lesson in the “Veritas NetBackup 8.1:

3-1
Policies
This lesson is the third lesson in this course.


3-2
Lesson objectives
Topic Objective
Introduction to backup policies Explain how data protection relates to a policy.
Creating and configuring policy

Identify basic policy types, and configure policy attributes.
attributes
Describe backup schedules types, and create and configure both
Creating a policy schedule
frequency-based and calendar-based schedules.
Adding client to a policy Specify which clients are to be served by a policy.
Define which client files and directories to backup up, and create
Creating backup selections
exclude and include lists.
Managing existing policies View, edit and copy an existing policy.

3-3
Topic: Introduction to backup policies
After completing this topic, you will be able to explain how data protection
relates to a policy.
After completing this topic, you will be able to explain how data protection relates to a
policy.

3-4
Creating a backup plan
• What kinds of clients do you have?

Clients and data • How much and what type of data needs to be backed up?
• How long do your backups take to run?

Scheduling • What is your backup window?
• When does your backup need to run?
• How often do you need to backup up your data?

Restore characteristics • How long do you need to retain the backups?
• How quickly do you need to restore your data?
Policy configuration is flexible enough to meet the various needs of all the clients in a
NetBackup environment. To take advantage of this flexibility, take time to plan before
starting to configure the policies within NetBackup.
Include the following tasks in your planning and preparation:
• Gather client information.
• Group the clients based on backup requirements.
• Consider the storage requirements.
• Consider the backup schedule.

• Group clients by common attributes.
• Maximize multiplexed backups.
• Evaluate backup times.

3-5
Understanding NetBackup policies
Attributes How do backups occur? Where do backup images go?
Schedules When do backups occur? Include all data or only changes? How long is backup data retained?
Clients Which systems are backed up?
Backup
Which data is backed up?
Selections
Application-
How are database backups handled? How are virtual machine backups handled?
specific tabs
Policies define the rules that NetBackup follows when data from clients are backed up.
A backup policy can apply to one or more clients. The best approach is to divide clients
into groups according to the backup requirements, and creating a policy for each group.
In a policy you define attributes, schedules, a client list, and a backup selections list.
• Attributes answer questions, such as: How should the files be backed up? Are there
any special backup behaviors? Where is the backup storage location?
• Schedules answer: What is the backup time and type? On which schedule should
the files be backed up? How long is the backup data retained?

• The Clients list identifies which clients to back up.
• The Backup Selections list identifies which files and data sets to back up.
More recent versions of NetBackup have introduced new policy tabs to assist with
application-specific backup settings. In NetBackup 8.1, these includes the following:
• Oracle policies includes the Oracle and Instances tab, and remove the Clients tab.
• MS-SQL policies includes the Microsoft SQL Server and Instances and Databases
tabs, and remove the Clients tab.
• VMware policies includes the VMware tab.
• Hyper-V policies includes the Hyper-V tab.

3-6
Topic: Creating and configuring policy attributes
After completing this topic, you will be able to identify basic policy types,
and configure policy attributes.
After completing this topic, you will be able to identify basic policy types, and configure
policy attributes.

3-7
Policy configuration methods
NetBackup Policy Configuration Wizard

• Quickly creates a simple policy to backup clients.
• Does not provide many configuration options.
NetBackup Administration Console

• Found under NetBackup Managements > Policies.
• Recommended method to create policies.
Command Line
• Provided with bppolicynew command.
• Can be used in script-based policy setup.
This slide identifies the methods for creating policies.

• The Policy Configuration Wizard
Used in the NetBackup Administration Console to quickly define schedules and
settings for backing up one or more clients, snapshots, or virtual machines. It
creates a basic policy that may need to be modified after creation.
• The NetBackup Administration Console
Use the Policies utility under the NetBackup Management interface to create and
edit policies. This is the recommended method.

• The command-line interface
Use the bppolicynew command.
The bppolicynew command creates an empty policy which contains the default
settings for attributes, but no schedules, clients or backup selection lists. It is often
used in scripts to create multiple backup policies. bppolicynew can also be used
to copy an existing policy, similar to the Administration Console’s Copy to New
function.
The bppolicynew command is unique in that it also allows you to rename a
backup policy, a feature that is not available in the Administration Console.

3-8
Creating a policy using the Administration console
bppolicynew
Perform the following steps to manually create a backup policy:

1. In the left pane of the NetBackup Administration Console, select Master Server >
NetBackup Management > Policies.
2. Perform one of the following:
• Select Actions > New > Policy.
• Right-click the master server in the All Policies pane and select New Policy.
The Add a New Policy dialog box is displayed.

3. Enter the name of your new policy and click OK. Notice that you can activate the
Backup Policy wizard by marking the Use Backup Policy Configuration Wizard check
box.
Your new policy is added with default settings.
You can copy an existing policy by selecting a policy from the list, right-clicking it, and
selecting Copy To New. This is useful when you must establish multiple policies that
have similar properties.
Refer to the NetBackup Administrator’s Guide for more information about adding
policies.

3-9
Policy dialog box: Attributes tab
BigData
Datastore
DB2
Enterprise-Vault
FlashBackup
FlashBackup-Windows
Hyper-V
Informix-On-BAR
Lotus-Notes
MS-Exchange-Server
MS-SharePoint
MS-SQL-Server
MS-Windows
NBU-Catalog
NDMP
Oracle
PureDisk-Export
SAP
Standard
Sybase
Vault
VMware
10
Attributes determine the basic characteristics of all the backups that NetBackup
performs for the policy. You can view and configure a policy’s attributes using the
NetBackup Administration Console.
The Attributes tab answers the questions “How is the policy going to perform the
backup?” and “Where are the storage units and volume pools to which the backup data
is to be sent?”
The Policy type determines the type of clients that can be part of the policy and, in
some cases, the types of backups that can be performed on the clients. Select the Policy
type from the drop-down menu.

3-10
Basic policy types
Standard policy type

• For UNIX-based file systems
• Supports UNIX, Linux, Mac OS X
MS-Windows policy type

• For Windows clients and servers
• Support Windows 2008, 2012, 2016, Vista, or Windows 7 SP1, 8, or 10
clients
11
The number of policy types available varies depending on which NetBackup options are
installed. Each policy type offers a unique combination of attributes.
The two policy types shown on this slide are basic NetBackup policy types. Each of these
policy types is distinguished by the types of clients that can be part of the policy, and
what is backed up when a backup job is run.
• Standard policy type
Used for clients and file systems that are UNIX-based, this includes UNIX, Linux, and
Mac OS X 10.8, 10.9 and 10.10 clients.

• MS-Windows policy type
Used for clients and file systems that are Windows-based, supported Windows
operating system levels.
Supported OS levels can be found on the support website at the following link:
http://www.veritas.com/docs/000115691.

3-11
Policy storage and Policy volume pool
Volume pools are only required for tape

based storage units, and are covered in the
Configuring Tape Storage lesson.
12
The Policy storage drop-down menu specifies the default storage unit or storage unit
group for backups of this policy. This is the storage unit that is used by default by all
schedules in this policy. However, schedules may be configured to override the policy
storage destination.
The Policy volume pool drop-down menu specifies the volume pool for backups of this
policy. Select the desired volume pool name from the drop-down list. The list displays all
previously configured volume pools. Whenever a new volume is required for either a
robotic or stand-alone drive, it is allocated to NetBackup from the requested volume
pool.
Policy storage and volume pools are covered in more detail in a later lesson.

3-12
Topic: Creating a policy schedule
After completing this topic, you will be able to describe backup schedules
types, and create and configure both frequency-based and calendar-based
schedules.
13
After completing this topic, you will be able to describe backup schedules types, and
create and configure both frequency-based and calendar-based schedules.

3-13
Creating a new schedule
14
The Schedule tab answers, among other things, the question “When is this policy to be
run?”
Use the following procedures to create a new schedule using the Administration
Console:
1. In the left pane of the NetBackup Administration Console, select Master Server >
2. Double-click a policy.
3. Click the Schedule tab.

4. Click the New button to access the dialog box that you use to build your schedule.

3-14
Schedule dialog box: Attributes tab
A policy can contain more

than one schedule.
15
The Attributes tab has the following fields:

• Name: The schedule name is used to refer to a schedule within NetBackup.
• Type of backup: Select from Type of backup drop-down menu. The menu displays
only the backup types that apply to the policy being configured.
• Schedule type pane
Calendar: Allows administrators to create a job schedule based on a calendar view.
Frequency: Specify how much time must elapse between the successful completion
of a scheduled task and the next attempt. In addition to hours, days, and weeks,
NetBackup 8.0 introduced the ability to set frequency in minutes and seconds.
• Destination pane
Multiple copies: Used to create inline copies. This is discussed in the Duplicating
Backups lesson.
Override policy storage selection and Override policy volume pool: Override the
storage unit or volume pool for this schedule, so that it differs from the one
specified in the policy’s Attribute tab.
Retention: The time that the image is to be held in the images catalog. By default,
NetBackup does not mix retention levels on a single volume.
For more information about other options on the Schedule dialog box Attributes tab,
see the NetBackup Administrator’s Guide.

3-15
Backup types for automatic schedules
Cumulative Everything since the last
Incremental full backup
Full
Sun Mon Tue Wed Thu Fri Sat
Differential Everything since the last

Incremental full or incremental backup
16
The backup types for automatic schedules are:

• Full backup
A full backup backs up all files specified in the backup selections list , regardless of
when the files were last modified or backed up. If you run incremental backups, you
must also schedule periodic full backups in order to perform a complete restore.
• Differential incremental backup
A differential incremental backup backs up all files specified in the backup selections
list for the policy that have changed since the last successful incremental or full
backup. All files are backed up if no prior backup has been performed. A complete
restore requires the last full and all of the differential incremental backups since the
last full or the last full, the last cumulative incremental and all of the differential
incremental backups since the last cumulative incremental.
• Cumulative incremental backup
Cumulative incremental backups back up all files specified in the backup selections
list for a policy that have changed since the last successful full backup. All files are
backed up if no prior backup has been performed. A complete restore requires the
last full backup and the last cumulative incremental. Cumulative incremental
backups generate more files per backup, but complete restoration is quicker.

3-16
Schedule dialog box: Start Window tab
17
The Start Window tab provides controls for setting time windows during which
NetBackup can start automatic backups, archives, or disk staging relocation when using
this schedule. Configure the start windows so that they satisfy the requirements
necessary to start a task or job. If the start windows closes before the backup has
started it does not run. Once a backup has started, it runs to completion even if the
start window closes. The start window is not used for manual backups.
For example, for backups, you can create a different window that opens each day for a
specific amount of time, or you can keep the window open all week.
For more information about the options on the Schedule dialog box Start Window tab,
see the NetBackup Administrator’s Guide.

3-17
Impact of start window duration on the schedule
Client 1 21:01
Start Window: when
backups may start
21:00 - 01:00 Client 2 22:39
Client 3 23:40
Client 4 00:52
This job does

not run:
Error 196.
Client 5
X
01:45
18
The example on this slide demonstrates the effect of start window duration on a backup
schedule.
In the example, backups for Client 1 through Client 4 are started within the backup start
window. Client 4 does not finish before the window closes, but because it starts within
the window, the backup is completed. Client 5 did not start within the window, so its
backup does not run. Client 5 is automatically the first client backup that is attempted in
the next run of this schedule.

3-18
Schedule dialog box: Exclude Dates tab
19
You can exclude specific dates, such as January 1, from your backup schedule.
Under the Exclude Dates tab, define the dates you want to exclude from the schedule.
Dates can be excluded by using Recurring Week Days, Recurring Days of the Month or
Specific Dates.
Exclude dates applies to both frequency-based and calendar-based schedules.

3-19
Schedule dialog box: Attributes tab: Schedule type
Note: Veritas recommends that you do not

mix calendar-based and frequency-based
schedule types within the same policy.
20
Schedule type: Frequency

Using the Frequency schedule type, administrators specify how much time must elapse
between the successful completion of a scheduled task and the next attempt at the
task.
When you process a policy with a frequency-based schedule and an open window, a job
is created for each client in the policy client list for which a backup is due to be
performed. A backup is due if the period since the last backup exceeds the schedule’s
frequency. For details, refer to Article 100006713: How NBPEM (NetBackup Policy
Execution Manager) schedules a frequency backup, found online at

To set a frequency-based policy schedule, select the Frequency radio button and type a
number or select a value from the drop-down menu. Select a frequency of hours, days,
or weeks.
Schedule type: Calendar
Calendar-based scheduling provides you with greater flexibility in scheduling backup
jobs. You can run a backup job any day of the month.
If a backup job generated by a calendar-based schedule fails, the Retries allowed after
runday attribute determines if the retry is allowed to occur after the scheduled calendar
day. Even when Retries allowed after runday is enabled, the backup window must be
open to enable the retry to be attempted.
The Include Dates tab is displayed when Calendar is selected as the Schedule type
under the Attributes tab of the Change Schedule dialog box.

3-20
Schedule dialog box: Include Dates tab
21
Calendar-based scheduling provides several run day options for use in scheduling when
a task runs.
A backup can run on Specific Dates rather than follow a recurring schedule, and specific
dates can be added to a recurring schedule. You can schedule specific dates in any
month of any year up to and including December 31, 2037.
Define specific calendar days as run days by clicking in the date on the calendar. This
specification causes the backup to run on the specified day during the valid window that
is defined for that day.
Recurring Week Days option provides a matrix that enables you to schedule a task for
certain days of each week, weeks of each month, or days on particular weeks of the
month. For example, use this option to schedule a task on the first and third Thursday of
every month. Or, schedule a task that runs the last week in every month.
The week day matrix is not a calendar; it is simply a matrix used to select days and
weeks in a month. A check mark entered for a day indicates that the task is scheduled to
run on that day of its respective week. By default, no days are selected. For example, to
define specific run days based on recurring days of the week, such as every Friday, click
Fri on the matrix, and every Friday is automatically selected.
The Recurring Days of the Month option provides a matrix that you can use to schedule
a task for certain days of the month. You can also schedule a task to occur on the last
day of the month, regardless of the actual date.

3-21
Retention Periods: Master server properties
bpretlevel
22
The retention period in a policy’s schedule determines how long NetBackup retains the
backups images created by that schedule. NetBackup 8.0 and later supports 100
separately defined retention levels. The Retention Periods properties, found in the
master server host properties, define the length of time associated with each level. All
of these retention levels are configurable, with the exception of level 9 and level 25,
which have fixed retention period values. Veritas recommends leaving retention levels
0-8 at the default values. Change higher levels which are currently set to infinite, if you
want to customize.
The following list describes the Retention Periods properties.

• The Value specifies the retention level setting.
• The Units property specifies the units of time for the retention period. The list also
includes the special units: Infinite and Expires Immediately.
• The Retention Periods pane contains a listing of the current definitions for the 101
possible levels of retention (0 through 100). The Schedule Count column indicates
how many schedules currently use each level. If the retention period is changed for
a level, it affects all schedules that use that level.
• The Schedule(s) using this retention level pane contains a listing of the schedules
that use the currently selected retention level, and the policy to which each
schedule belongs.
Click the Impact Report button to display a summary of how changes affect existing
schedules. If you change a retention period, click Impact Report. The list displays all
schedules in which the retention period is less than the frequency period.

3-22
Topic: Adding clients to a policy
After completing this topic, you will be able to specify which clients are to
be used in a policy.
23
After completing this topic, you will be able to specify which clients are to be used in a
policy.

3-23
Methods of distributing client software
1 Local install 2 Silent install 3 Install from file share
silentclient.cmd
UNIX or Any NetBackup

Windows client Windows client File server client
4 UNIX NetBackup server to client 5 Windows server to client

push installation push installation
install_client_files
UNIX NetBackup UNIX Any Windows server Windows

server clients only with NetBackup media clients only
24
Before adding a client to a policy, ensure that the NetBackup software is successfully
installed on that client. There are five ways to distribute NetBackup client software:
1. Local installation: In a local installation the NetBackup client software can be
installed on the machine by providing a copy of the NetBackup client software.
2. Silent installation: A silent installation is a process that does not require interactive
input. You must first modify the silentclient.cmd script.
3. Installation from a file share: To install NetBackup client software from a file share
simply put a copy of the NetBackup client software on a file server and any client on
the network can install the software to itself.
4. UNIX server to UNIX client: A NetBackup UNIX master or media server can push
UNIX client software, using standard protocols such as ssh, and sftp. These
protocols are available in a combination of the NetBackup Administration Console,
and in the install_client_files script.
5. Windows server to Windows client: Any Windows server that has a copy of the
NetBackup software, can push the NetBackup client software to other Windows
clients out on the network.

3-24
Adding clients to a policy
25
The Clients tab contains the list of clients that are backed up or affected by this policy.
This answers the question, “Which system is to be backed up?”
To add clients to a policy using the NetBackup Administration Console, click the Clients
tab and click New. You are prompted to provide the name of the client, as well as the
hardware and operating system type. You can either select the Detect client operating
system check box or select the appropriate hardware and operating system for the
client in the drop-down menu.
Note: To be able to use the auto-detect feature, the NetBackup client software must
already be installed on the client, and the master server needs to be allowed to connect
to the client by having an appropriate SERVER entry in the client’s server list. This is
accomplished when you enter the master server name during the installation of the
client software on the host.
For detailed instructions on adding a client to a policy, see the NetBackup
Administrator’s Guide.

3-25
Topic: Creating backup selections
After completing this topic, you will be able to define which client files and
directories to backup up, and create exclude and include lists.
26
After completing this topic, you will be able to define which client files and directories
to backup up, and create exclude and include lists.

3-26
About backup selections
What do backup selections do?
• Identify files and directories to be backed up
Who uses backup selections?
• All clients in the policy, but all files do not have to exist for every client
What does not use backup selections?
• User backups and user archives
How are backup selections refined?
• Exclude and include lists
27
Under the Backup Selections tab, you name the files and directories that NetBackup
includes in automatic scheduled backups for clients in this policy. The backup selections
list does not apply to user backups or archives because in those instances the user
selects the files.
NetBackup uses the same backup selections list for all clients in the policy, but it is not
required that all files exist on all clients. NetBackup backs up the files that it finds.
However, each client must have at least one of the files in the backup selections list, or
the client backup fails with a status code 71. Backup selections are processed serially for
each client. It is possible, however, to back up more than one client (or policy) in
parallel.
Related items are listed on the exclude and include lists. You can create an exclude list
on a client to specify files that you do not want to include in automatic and manual
backups of that client. You can also create an include list for a client to back up a file or
directory that would otherwise be excluded by an exclude list. Many administrators
have a standard exclude list that is copied to all clients, and then use include lists to
customize clients that have exceptions to the standard exclude list.

3-27
Client backup selections list guidelines
Windows UNIX
Creating a backup
Administration Console or bpplinclude
selections list
• Use one path per line
Entries • Maximum path length of 1,023 characters
• All paths must be absolute
Path restrictions Start all paths with a drive letter Start all paths with a slash (/)
Wildcards supported *, ? *, ?, { }, [ ]
28
When defining files for your policy, the backup selection list can be set using either the
NetBackup Administration Console or the bpplinclude command.
It is important that you follow the conventions and rules used to specify backup
selection lists:
• Enter one path per line, with a maximum path length of 1,023 characters.
• All paths must be absolute. Local paths on Windows must start with the drive letter
followed by a colon and a backslash (:\). The drive letter can be either upper- or
lower-case . Network paths can be in UNC format, starting with

\\server\share\. Paths on UNIX must start with a slash (/), and are case
sensitive. Note: \\.\D: is valid for a raw partition backup on Windows.
• Best practice: If the last component in the path is a directory, also follow it with a
backslash on Windows (\) or slash on UNIX (/). The trailing slash is not required but
serves as a reminder that the file path is a directory instead of a file (for example:
F:\workfiles\).
• Use wildcards to select files of a specific type or files with common naming
elements. For example:
K:\tests\*.exe
K:\tests\test*.txt
C:\windows\system\log??_02

3-28
Creating a backup selection list
bpplinclude
29
The backup selections list under the Backup Selections tab names the files, directories,
directives, scripts, and templates that NetBackup includes in automatic backups of
clients covered by the policy. NetBackup uses the same backup selections list for all
clients backed up according to the policy.
This answers the question “What is to be backed up?”
To build a backup selections list when creating a policy using the NetBackup
Administration Console, click the Backup Selections tab and click New. You are then
prompted to provide a new path or directive.
For example, you can use C:\ or /home for a path and ALL_LOCAL_DRIVES for a
directive.
For detailed information on adding an entry to the Backup Selections list, see the
NetBackup Administrator’s Guide.

3-29
Backup selections list directives
Directive Description
ALL_LOCAL_DRIVES • Backs up every local file system (UNIX) or logical drive (Windows) on the client
machine
• Includes the system state or shadow copy components on Windows clients, below
Shadow Copy • Backs up all VSS writers for the Volume Shadow Copy component, in Windows 2003
Components:\ and later
• Backs up critical system-related components, such as the registry, Active Directory,
and other information not fully protected when backing up the file system alone
NEW_STREAM • Recognized only if Allow multiple data streams is set.
• Splits the backup splits into separate streams.
• Discussed in the Optimizing File System Backups lesson.
Policy-specific directives • Apply only to specific policy types and can appear only in backup selections lists for
those policies.
UNSET and UNSET_ALL • Interrupt the streaming of policy-specific directives.
• Requires the Allow multiple data streams policy attribute.
30
Directives on the Backup Selections list signal NetBackup to perform specific,

predefined actions when it processes the files on the selections list.
The ALL_LOCAL_DRIVES directive backs up all local drives, except for those drives that
use removable media. If used, this directive must be the only entry in the backup
selections list. For Windows clients, this directive automatically includes the system
state and shadow copy components, so including other directives is not necessary.
The Shadow Copy Components:\ directive specifies that all of the Volume Shadow Copy
component writers get backed up, backing up critical system-related components, such
as the registry, Active Directory, and other information not fully protected when backing
up the file system alone. The System State:\ directive can still be found, and is used for
versions which do not support Shadow Copy Components, such as Windows XP.
The NEW_STREAM directive is available when the Allow multiple data streams
attribute is enabled for the policy. This directive is discussed in greater detail in the
Optimizing File System Backups lesson. Refer to that lesson for further details.
Some directives apply only to specific policy types and appear only in backup selections
lists for those policies. NetBackup passes these directives to the clients along with the
backup selections list, which then perform appropriate action according to the directive.
The UNSET and UNSET_ALL directives interrupt the streaming of policy-specific
directives so that it is not passed with any additional streams.

3-30
Follow NFS (UNIX)
Configured under the policy Attributes tab
Public network
NetBackup NetBackup
media server Windows client
NFS
mount
/ /usr /nfs_home /home
31
The next few slides show further settings that can be configured to control backup
selections. These settings can be found under the Policy Attributes tab.
The Follow NFS attribute applies only to UNIX clients in certain policy types, and
NetBackup enables you to select it in only those instances.
The Follow NFS attribute specifies that you want NetBackup to back up or archive any
NFS mounted files that are named in the backup selection list, or by the user in the case
of a user backup or archive. Clear the check box to prevent the backup or archive of NFS
mounted files.
This attribute forces the client to back up NFS-mounted drives within the path. It is
important to understand the advantages and disadvantages of the Follow NFS attribute
setting.

3-31
Backup network drives (Windows)
Public network
NetBackup NetBackup
media server UNIX client
CIFS
share
C:\ D:\ E:\ F:\
32
The Backup Network Drives attribute applies only to certain policy types.
The Backup Network Drives attribute was intended to be used on single-user systems—
Win95, Win98, and ME. These operating systems are not supported with this version of
NetBackup. For a computer that is not a NetBackup client, the preferred method for
backing up data is to use UNC paths. UNC paths are more precise and indicate exactly
what should be backed up.
For detailed information on using UNC paths in the Backup Selections list, see the
NetBackup Administrator’s Guide.

3-32
Cross mount points
NetBackup NetBackup
UNIX client Windows client
/ C:\ D:\
/home C:\data
33
Another policy attribute is Cross mount points. When enabled, this attribute forces the
client to back up locally mounted drives within the path. The Cross mount points check
box controls whether NetBackup crosses file system boundaries during a backup or
archive on UNIX clients or whether NetBackup enters volume mount points during a
backup or archive on Windows clients.

3-33
Exclude and include lists for UNIX clients
Exclude list
• Location: /usr/openv/netbackup/ (on the client)

• Filename: exclude_list[.policy_name[.schedule_name]]
• Example: # this is a comment
/home/doe Article 100019744: A method for centrally
/home/*/test managing exclude and include list for UNIX
/*/temp and Linux clients (using bpsetconfig)
core
Include list
• Location: /usr/openv/netbackup/ (on the client)

• Filename: include_list[.policy_name[.schedule_name]]
• Example: # this is a comment
/home/smith/test
34
On UNIX NetBackup clients, you can exclude specific files from automatic backups by
specifying them in an exclude list on the client.
You can also create an include list to add certain files to the backup. An include list is
useful, for example, if you want to exclude an entire directory except for one file.
It is recommended that policy names do not include a “.” (period) character, because of
the exclude and include list file naming structure.
Note: You can create policy- and schedule-specific lists. NetBackup ignores the general
list if a specific list is present.

For detailed instructions on creating an include or exclude list, see the NetBackup
For detailed instructions on how to remotely manage include and exclude lists for UNIX
clients, refer to the NetBackup Commands Reference guide, and Article 100019744: A
method for centrally managing exclude and include list for UNIX and Linux clients, found
online at http://www.veritas.com/docs/100019744.

3-34
Exclude and include lists for Windows clients in the Client host
properties
Exclude list
Include list
35
Exclude lists for NetBackup clients can be used to prevent files that are found within the
backup selection from being backed up. The Exclude Lists properties apply to currently
selected clients running NetBackup. Note: You can create policy- and schedule-specific
lists. NetBackup ignores the general list if a specific list is present.
The properties in the Exclude Lists pane include:
• Use case sensitive exclude list: Indicates that the files and directories listed for
exclusion or exception are case-sensitive.
• Exclude list: Displays files and directories to exclude from backups. By default there
are no exclusions except for a short list of NetBackup-related exclusions.
• Exceptions to the exclude list: This list displays policies, schedules, files and
directories that are excepted from the Exclude list. When the policies on the
Exceptions to the exclude list run, the files and directories on the list are backed up.
This is useful if you want to exclude all files in a directory but one. This is equivalent
to the include list found on UNIX.
• The Add, Add to All, Change, Remove, Copy and Paste buttons each perform
different functions, depending on whether they are used from the Exclude list or
from the Exceptions to the exclude list. Note: The Add to Exclude List dialog box, as
shown on the slide, appears to have drop-down selections for policy and schedule
name, however these are actually text-entry fields.

3-35
Exclude and include lists for Windows clients in the Backup,
Archive, and Restore interface
Using the Backup, Archive, and Restore

interface on the NetBackup Windows client
Exclude list Include list
36
In the Backup, Archive, and Restore interface, which is found on every NetBackup client,
select File > NetBackup Client Properties from the menu bar. Click on the Exclusions tab
to modify files to exclude from backup, and click on the Inclusions tab for files to
include within the excluded files.
Note that modifying the exclude and include lists in the Backup, Archive, and Restore
interface modifies the exact same lists as those in the client host properties, shown on
the previous slide. On Windows, these settings are stored in the Windows registry.
For detailed instructions on creating an include or exclude list, see the NetBackup

3-36
Topic: Managing policies
After completing this topic, you will be able to view, edit, and copy existing
policies.
37
After completing this topic, you will be able to view, edit and copy an existing policy.

3-37
Viewing and editing a policy using the NetBackup Administration
Console
38
The easiest way to view and edit policies is by using the Policies utility in the NetBackup
Administration console. To run the Policy utility:
1. In the NetBackup Administration Console, in the object tree pane, expand
NetBackup Management > Policies
2. Within the Policy utility, you can perform the following tasks:
• To see a hierarchical view of the policies, select Policies in the object tree pane.
• To display the details of a single policy, select the policy name in the All Policies
pane. The policy details display in the far right pane.

• To open or change a policy, in the All Policies pane, double-click the policy
name. The Change Policy dialog box is displayed.
• To display information about all policies, in the All Policies pane, select
Summary of all Policies. Click the title bar of each horizontal pane to expand or
collapse it.
To edit an existing policy:
1. In the NetBackup Administration Console, in the object tree pane, expand
2. Right-click the policy name and select Change.

3-38
Copying an existing policy
bppolicynew
39
You can copy an entire policy from an existing policy to a new one. Use the Copy
to New option to save time creating policies. This option is especially useful for the
policies that contain many of the same policy attributes, schedules, clients, or backup
selections.
To copy a policy to create a new one:
1. In the NetBackup Administration Console, in the left pane, expand NetBackup
Management > Policies.
2. In the middle pane, select the policy to copy.

3. Right click and select Copy to New.
4. In the Copy a Policy dialog box, enter the name of the policy that you want to copy.
You can indicate a policy other than the one that is selected, or leave the original
named policy.
5. Enter the name for the new policy, then click OK. The only difference between the
new policy and the copied policy is the name.
Note that using the policy copy operation can be used for copying policies of the same
policy type, but should be customized after the copy operation to prevent having
policies that perform the same operations. Additionally, the policy copy operation
should probably be avoided when copying a policy to a new policy type. It is more
appropriate to simply create a new policy for the new policy type backup.

3-39
Copying an existing schedule
40
You can also use the Copy to New option to save time creating schedules. Use this
option to copy a schedule into the same policy or different policy.
To copy a schedule to create a new one:
1. In the NetBackup Administration Console, in the left pane, expand NetBackup
Management > Policies.
2. In the middle pane, expand a policy and select the Schedules node that contains the
schedule that you want to copy.
3. In the right pane, select the schedule that you want to copy.
4. Right click and select Copy to New.
5. In the Copy Schedule dialog box, enter the name of the new schedule.
6. Use the menu to select the name of the policy to which you want to paste the
schedule. You can paste the schedule into the same policy or a different policy.
7. Click OK. The Change Schedule dialog box opens for the new schedule.

3-40
Lesson summary
• Key points
– You now learned how to create a basic policy that is used to back up files in a file system.
– You learned about the types of schedules that are available in a policy.
– You learned how to define the clients that are backed up by the policy and the files and directories to be
backed up.
– You also learned how to manage policies using the NetBackup Administration Console.
– Article 100019744: A method for centrally managing exclude and include list for UNIX and Linux clients
41

3-41
Lab 3: Configuring policies and schedules
Lab objectives
• Use the NetBackup Administration Console to create NetBackup policies used to perform
backups of client file systems to pre-configured storage destinations
• Configure various types of policy schedules, including frequency-based, calendar-based,
full, incremental, and using a variety of schedule parameter settings
• Use the NetBackup Administration Console to modify a NetBackup policy
• (Optional) Complete a challenge lab to test your understanding of NetBackup policy
configuration

3-42
What did you learn?
lesson.
43
current lesson.

3-43
Question: Maximum number of policies
What is the maximum number of policies that NetBackup can be configured to use?
A. 1,000
B. 500
C. Unlimited
D. None of the above
44

3-44
Answer: Maximum number of policies
What is the maximum number of policies that NetBackup can be configured to use?
A. 1,000
B. 500
C. Unlimited
The correct answer is C. NetBackup does not limit the number of policies that you can configure. However, the best
approach to setting up policies is to divide clients into groups according to their backup and archiving requirements, and
then create policies that are appropriate for each group.
45

3-45
Question: Incremental schedules
Which incremental schedule type generates more files per backup?
A. Differential incremental
B. Cumulative incremental
C. Accumulation incremental
D. Differences incremental
46

3-46
Answer: Incremental schedules
Which incremental schedule type generates more files per backup?
A. Differential incremental
B. Cumulative incremental
C. Accumulation incremental
D. Differences incremental
The correct answer is B.
47

3-47
Question: Exclude dates and frequency schedules
Exclude dates are not available in frequency-based schedules.
A. True
B. False
48

3-48
Answer: Exclude dates and frequency schedules
Exclude dates are not available in frequency-based schedules.
A. True
B. False
49

3-49
End of presentation
3-50
Lesson 4: Performing File System Backups
This is the “Performing File System Backups” lesson in the “Veritas NetBackup 8.1:

4-1
Policies
This lesson is the fourth lesson in this course.


4-2
Lesson objectives
Topic Objective
Using and customizing the Use and customize the Activity Monitor, and suspend, resume,
NetBackup Activity Monitor restart, and prioritize jobs.
Performing manual backup Initiate a manual backup job, and monitor backup jobs using the
operations Activity Monitor.
Configure and perform user-directed backups using the Backup,
Performing user-directed backups
Archive, and Restore console.
Backup job-related tips Identify common backup job-related status codes.

4-3
Topic: Using and customizing the NetBackup Activity
Monitor
After completing this topic, you will be able to use and customize the
Activity Monitor, and suspend, resume, restart, and prioritize jobs.
After completing this topic, you will be able to customize the Activity Monitor, and
suspend, resume, restart, and prioritize jobs.

4-4
Monitoring jobs using the Activity Monitor
Icon Legend
Successful
Partially
successful
Active
Queued
Failed
Incomplete
Suspended
• Shows completed jobs < 78 hours old

bpdbjobs • Customize with KEEP_JOBS_HOURS = hours
The Jobs tab within the Activity Monitor provides a listing of jobs that are queued, are
currently running, have completed successfully (status code 0), have completed partially
successfully (status code 1), or have failed.
The Activity Monitor periodically deletes completed jobs that are more than three days
old (specifically any completed jobs older than 78 hours). To keep jobs in the Activity
Monitor longer than the default value, for example by changing the timeframe from 78
hours to 192 hours, use one of the following methods:
• On a Windows or UNIX master server, run the command:
echo KEEP_JOBS_HOURS = 192 | nbsetconfig

• On a UNIX master server, add the entry “KEEP_JOBS_HOURS = 192” to the
/usr/openv/netbackup/bp.conf file.
Alternatively, note that you can view older jobs in the NetBackup report found under
NetBackup Management > Reports > Status of Backups. The Status of Backups report
does not show job details, and only specific types of jobs, such as backup jobs.
For additional settings and details, refer to the NetBackup Administrator’s Guide.

4-5
Customizing the Activity Monitor
You can use the Activity Monitor in the NetBackup Administration Console to monitor
and control NetBackup jobs.
To display job information, in the NetBackup Administration Console, click Activity
Monitor. Summary information about all jobs is displayed under the Jobs tab in the
details pane.
By default, not all columns are displayed. The following procedure describes how to
show or hide columns:
1. In the Activity Monitor, select View > Column > Layout.
The Column Layout dialog box is displayed.

2. Select the column to display or hide by selecting its heading from the list.
• Click Show to display the column.
• Click Hide if you do not want to see the column heading.
3. To change the order in which the columns appear, select the column heading. Then,
click the Move Up or Move Down button to reorder the columns. Columns can also
be reordered from within the NetBackup Administration console by simply using
drag and drop.
4. Click OK to apply the changes.

4-6
Filtering jobs in the Activity Monitor
Show / hide
custom filters
Show all jobs Show filter

and clear results
applied filters
Filtering jobs in the Activity Monitor simplifies troubleshooting and reporting. For
example, you can filter for jobs that were started before a specific date, queued jobs, or
jobs with status completion codes within a specified range.
The Filter dialog can be viewed in by accessing the View > Filter menu option, or by
clicking on the Show or Hide Custom Filter button in the top-right corner of the Activity
Monitor. Clicking on the View All button clears currently applied filters and displays all
original rows again.
To create a filter:
1. In the Activity Monitor, show the custom filter pane as shown on the slide.
2. Click Create, and in the Create Filter dialog box provide a name for the filter.
3. Under the Advanced tab, select the Field, Comparison, and Value desired.
4. Click Add to List to add your selections to the filtering criteria.
5. Click Save to create the filter. The filter is immediately applied.
You can edit an existing filter operation with the Edit button. Once the filter is modified,
save the filter by either choosing Save or Save And Apply Filter. There is also
functionality to export and import filters as a binary file, to share frequently used filters
with other hosts and users.

4-7
Controlling jobs
A NetBackup administrator can cancel a job at any time from both the Activity Monitor
and from the command line. A NetBackup administrator can suspend a job that has
checkpoint restart enabled. In the example on the slide, Suspend Job is greyed out, this
means the job cannot be suspended as there are no checkpoints enabled in the policy
configuration.
Jobs cancelled “cleanly” as described here, exit with NetBackup status code 150
(termination requested by administrator).
If you cancel a scheduled backup job, but the number of retries is not yet exceeded and
the backup window is still open, the backup is reattempted.

Also, note that after you cancel a backup job, the cancellation process can take several
minutes. For example, if the backup is being written to tape, the tape must be rewound
and unmounted before the cancellation process is fully completed.

4-8
Understanding job priorities
• Determines which job is assigned available backup

resources
• Apply to new and queued jobs only (have no effect
Job priority
on active jobs) range is
• Set in these locations: 0 – 99999
– Default: Host Properties > Master Server > Default
Job Priorities
– Policy: Policy > Job priority
– Dynamic: Activity Monitor > Action > Change Job
Priority
Job priorities provide a method to help determine which jobs get available resources.
This can be used to help administrators prioritize certain high priority clients and data
against other clients with a lower priority.
Job priorities can be set as a default value for different job types in the policy, before the
job runs, or on jobs that have already been added to the Activity Monitor in NetBackup.
The NetBackup Resource Broker (nbrb) uses the job priorities to determine which job is
assigned available backup resources, in addition to other factors, such as multiplexing
requirements. The NetBackup resource broker re-evaluates resource requests every five
minutes, or when triggered by an external event, such as a resource release.

In Master Server Properties > Default Job Priorities, you can set the default job
priorities for different job types. The Default Job Priorities host properties list 18 job
types and the configurable default priority for each. The job priority range is 0–99999.

4-9
Setting specific job priorities
Can be set on backup policy Can be set on queued or running jobs
10
This slide shows how to set job priorities on a policy and on running jobs.
Note that although you can change the job priority of a running job, because it has
already started, this priority has no effect. However, if the job fails, and then gets re-
queued for another attempt, it is re-queued with this new priority.

4-10
Checkpoint restart
Configured under the Policy Attributes tab
ckpt1 ckpt3 ckpt5 ckpt7 ckpt9 ckpt11 ckpt13 ckpt15 ckpt17 ckpt19 ckpt21 1
Backup fails
ckpt2 ckpt4 ckpt6 ckpt8 ckpt10 ckpt12 ckpt14 ckpt16 ckpt18 ckpt20 ckpt22
The job is marked
as incomplete
HOURS
HOURS
SS
TT EE 3
AA 11 22 33 44 55 66
NN Job is
RR DD
TT done
2 Job resumes
Job starts from the point in the file system ckpt22 ckpt24 ckpt26 ckpt28
indicated in the last checkpoint: “ckpt22”
ckpt23 ckpt25 ckpt27
11
The Take checkpoints every check box indicates whether NetBackup takes checkpoints
during backup jobs based on this policy at the frequency indicated.
Taking checkpoints during a backup is beneficial in the event that a backup based on this
policy fails. Without Take checkpoints every enabled, a failed backup based on this
policy is restarted from the beginning of the job. By taking checkpoints periodically
during the backup, NetBackup can retry a failed backup from the last checkpoint rather
than restarting the entire job.
The number of times that NetBackup automatically reattempts a failed backup is
configured by the Schedule Backup Attempts property located in the Master Server
Properties > Global Attributes dialog box.
Policy types MS-Windows (for Windows clients) and Standard (for UNIX clients) support
checkpoints for backup jobs. Job types that do not support checkpoint restart include
catalog backups, duplication jobs, Vault jobs, import jobs, synthetic backup jobs, and
most database agents.
How often NetBackup takes a checkpoint during a backup is configurable. The
administrator determines on a policy-by-policy basis how to balance more frequent
checkpoints with the likelihood of less time lost in resuming a backup because of more
checkpoints. The default is checkpoints every 15 minutes. The minimum supported
value is every 5 minutes, and maximum is every 180 minutes (every 3 hours).

4-11
Resuming a suspended or incomplete job
Configured under master server

host properties > Clean-up
12
To resume a suspended or an incomplete job:

1. In the NetBackup Administration Console, open the Activity Monitor and click the
Jobs tab.
2. Select the suspended or the incomplete job you want to resume.
Only backup and the restore jobs that contain checkpoints can be suspended.
3. Select Actions > Resume Job.
Note that if incomplete jobs are not resolved after 3 hours, by default, then their state
changes from Incomplete to Done. This settings can be changed in the master server
host properties under the Clean-up tab. A screenshot of that setting is shown on the
slide.

4-12
Checkpoint restart limitations
Windows system
• No checkpoints are taken.
state backup
Disk-image (raw)
• No checkpoints are taken.
backup
NTFS single-instance • No checkpoints are taken after NetBackup encounters an NTFS

store (SIS) single-instance store.
NTFS resumed • Archive bits cleared for files backed up after the resume.
incremental backup • Archive bits not cleared for files backed up prior to the resume.
13
The following are checkpoint restart limitations:

No checkpoints are taken during the backup of a system state or shadow copy
components on a Windows client.
No checkpoints are taken during a disk-image (raw) backup.
No checkpoints are taken for the remainder of the backup after NetBackup encounters
an NTFS single-instance store (SIS).
Single-instance store is an architecture designed to maintain duplicate files with a
minimum of disk, cache, and backup media overhead. For more information on NTFS
single-instance store, see the Knowledge Base on the Microsoft Web site at
https://technet.microsoft.com/en-us/library/dd573308%28v=ws.10%29.aspx.
On a Windows client's NTFS file system, when a differential incremental backup is
resumed and then completes successfully, the archive bits are cleared for the files
backed up since the resume, but not for the files backed up prior to the resume.
This means that the files backed up prior to the resume are backed up again on the next
differential incremental backup.

4-13
Topic: Performing manual backup operations
After completing this topic, you will be able to initiate a manual backup job,
and monitor backup jobs using the Activity Monitor.
14
After completing this topic, you will be able to initiate a manual backup job, and
monitor backup jobs using the Activity Monitor.

4-14
How backups are initiated
Automatic
• Initiated based on the policy schedule
• Can be on a calendar or frequency-based schedule
Manual (immediate)
• Initiated from the NetBackup Administration Console
• Initiated from OpsCenter
• Initiated from command line on a NetBackup server
User-directed
• Initiated by users or scripts on the client
• Performed on authorized NetBackup clients only
15
Backups can be initiated:

• Automatically, based on the policy schedule
• Manually from the NetBackup Administration Console, OpsCenter or command line
on a NetBackup server.
• By users or scripts, from authorized client servers.
This type of backup is not initiated by an automatic schedule.

4-15
Manual backups
What are manual backups?
• Backups performed on automatic schedules (not user-directed schedules)

• Do not require an open start window
• Run by NetBackup administrators, or by an external scheduler
• Also known as immediate backups
• May be mistaken for user-directed backups
When to run manual backups?
• Testing a configuration
• Resubmitting a missed or failed backup
• Preserving an old configuration prior to upgrading
How to run manual backups?
• Using the NetBackup Administration Console, OpsCenter or bpbackup -i
16
A manual backup (sometimes called an immediate backup) is a manual submission of an

automatic policy. NetBackup administrators can invoke manual backups, assuming that
an appropriate policy has been defined.
Do not confuse manual backups with user-directed backups:
• Manual backups are performed from the NetBackup server by the backup
administrator and apply only to automatic schedules.
• User-directed backups are performed from the client machine.
A manual backup is not dependent on the policy’s backup window or the time specified
by the schedule. That is why it is also called immediate. In fact, you can create a policy
schedule without an open window and run only manual backups defined by that policy,
as needed.
Since you can invoke a manual backup outside a policy’s normal backup window, a
successful manual backup job can affect a frequency-based schedule because it qualifies
as a successful backup. Consider that frequency-based schedules are based on the
amount of time (frequency) since the last successful backup job. This may therefore
mean that an automatic backup does not run when you next intended it to.

4-16
Performing a manual backup using the Administration Console
bpbackup -i
17
To initiate a manual backup from the NetBackup Administration Console:

1. From the object tree pane of the NetBackup Administration Console, expand
NetBackup Management and select Policies.
2. In the All Policies pane, click the policy name and select Actions > Manual Backup.
Alternatively, right-click the policy and select Manual Backup.
The Manual Backup dialog box is displayed.
3. Select a schedule and the clients you want to back up.
If you do not select any schedules, NetBackup uses the schedule that runs least
often. For Automatic schedules, the Frequency is generally used. If there are
multiple equivalent candidates, then schedule with the highest retention level is
chosen. It is therefore recommended to explicitly specify the schedule that you wish
to use.
If you do not select any clients, NetBackup backs up all clients.
If a User schedule exists, they are not displayed in the schedules list and cannot be
manually backed up because they do not have a backup selection list (the user
selects the files). These types of backups are run from the client system, either by an
application or script, or an administrator (user).
4. Click OK to start the backup.

4-17
Verifying successful completion of backup jobs
Status Code Icon Description
0 The backup was successful.
1 The backup was partially successful.
157 A checkpoint backup was suspended manually.
Any other status code A backup has experienced a problem.
Any other status code A checkpoint backup has experienced a problem.
18
You can expect backup success to be the norm in a properly configured and well-
maintained NetBackup environment. NetBackup is a very robust application in terms of
detecting and reporting errors, therefore, when problems do occur, you should be able
to track them down and correct them quite reliably.
A status code 0 (and the accompanying success icon: ) in the Activity Monitor
indicates that a backup job has completed successfully. Any other status code or icon
indicates that a backup was only partially successful or has failed. There are other
methods by which you can determine if a problem has occurred with a backup job,
including reports and activity logging.

A status code 1 (and the accompanying partial success icon: ) in the Activity Monitor
indicates that the job has partially succeeded successfully. For file system backups, this
could mean that some of the targeted files did not get backed up. It could be only one
file was missing, or many files, and there is no indication how important these missing
files are. Look at the job details for information on which files are not included. If those
files are not important (such as temporary or cache files that aren’t needed for
recovery), consider excluding them from future backups, so that you instead complete
with status code 0. Using Windows VSS or other snapshots may fix these issues.
Other reasons may exist for status code 1 backups, and for application and database
backups, a status code 1 may indicate a larger problem, and may result in the inability to
perform restores.

4-18
Viewing job details in the Activity Monitor
19
To view the details for a specific job, double-click the job under the Jobs tab. The Job
Details dialog box is displayed. Detailed job information is contained under three tabs:
• Job Overview provides a high level view of the job.
• Detailed Status lists the step by step actions performed during the job.
Under the Detailed Status tab, a Troubleshooter button is available to launch the
Troubleshooter, which can help determine the cause of the problem and
recommend corrective actions.
• Job Hierarchy shows the job hierarchy, discussed in more detail on the following
slide.

4-19
Viewing job hierarchy in the Activity Monitor
20
Hierarchical jobs, when one job is a parent of one or more child jobs, is a behavior seen
frequently with Storage Lifecycle Policies, snapshot jobs, catalog backup jobs, and many
other job types.
The Activity Monitor in the NetBackup Administration Console can optionally show a
hierarchical job view. There is a button on the toolbar which enables this functionality,
or you can select View > Jobs in Hierarchical Manner from the menu bar to toggle this
view.
You can get this information by moving the Parent Job ID column, which by default is
placed to the far right, close to the Job ID column. In that manner you could see the job
associations. However, the hierarchical job view makes this easier to visualize.
The job hierarchy can also be seen in the Job Hierarchy tab of the job details.

4-20
Viewing jobs with multiple attempts
21
In some cases backup jobs may initially fail, but then, when retried by NetBackup, they
succeed in a future attempt. You are able to see the details for each job attempt in the
Detailed Status tab of the job details. Simply use the up and down arrows to the right of
the Attempt field.
The slide displays one of these cases, where the first attempt to run a backup job
resulted in a status code 157: suspend requested by Administrator. The second attempt
at running the job succeeded and exited with a status code 0.

4-21
Topic: Performing user-directed backups
After completing this topic, you will be able to configure and perform user-
directed backups using the Backup, Archive, and Restore console.
22
After completing this topic, you will be able to configure and perform user-directed
backups using the Backup, Archive, and Restore console.

4-22
User-directed backups
What are user backups?
• Initiated from the client host.

• Specify the files and folders to be included in the backup.
• Enabled with a User Backup schedule in the policy.
• Enabled only for clients configured in the policy.
• Have storage type and retention level as configured in the policy.
When to run user backups?
• To regularly back up a customized selection of files on a system, manually.

• To initiate backups using a script on the host or client system.
How to run user backups?
• Using the Backup, Archive, and Restore interface or using bpbackup
23
A user-directed backup is invoked by an operator on the client machine either by using

the Backup, Archive, and Restore console, the command line or by running a script. This
type of backup is ad hoc and can be initiated at any time as permitted by the start
window defined in the user backup schedule.
Although the term user backup or user-directed backup is commonly used, operations
are most likely performed by client administrators, or system administrators on the
behalf of users, and a more suitable description is client-directed or application-directed
backups. However, the term “user-directed” is used throughout the documentation.
The policy must have a user backup schedule that defines the start window during
which users can initiate a backup. The client must be in the policy’s client list. Users
select files and directories to back up. NetBackup ignores the policy’s backup selections
list.
Clients can obtain status information using progress logs, e-mail notifications, and the
activity monitor.
User-directed backups and archives can be initiated by:
• An interactive user, such as a file owner, system administrator, or DBA by using the
BAR console, or NetBackup commands
• A backup script launched at regular intervals
• An event trigger that kicks off a backup script

4-23
Setting the user schedule and client list for a user-directed backup
Backup Selections is ignored
24
User-directed backups require a backup policy that contains a User Backup schedule,
and the client names added into the Clients tab of that policy.
Consider the following:
• When you establish a user backup schedule, you provide users with a start window
during which they can perform their own backups or archives. Users can start
backups and archives only during the times permitted under the schedule’s Start
Window tab. When you set the start window, consider the times that users typically
are at work and likely to need to initiate user-directed backups. If a user starts a
backup outside of this window, the backup job fails.

• User backup schedules can be included in a policy that contains automatic backup
schedules. If you create separate policies for user backups, the considerations are
similar to those for automatic backups. Jobs running user backup schedules ignore
the policy’s backup selection list. The files backed up are specified as part of the
request to run the backup job at the time the request is made by the user.
• The policy name you choose is significant. By default, NetBackup alphabetically
searches (uppercase characters first) for the first available policy with a user backup
schedule with an open backup window, and a matching host name under the Clients
tab of the policy. If no user backup schedule is found, the backup fails with a status
code 240: no schedules of the correct type exist in this policy.

4-24
Initiating a user-directed backup from the BAR console
25
Users can initiate backups and archives using the Backup, Archive, and Restore interface
on the client machine. These operations can be performed without administrator
intervention, and the user does not need to log on to any of the NetBackup servers.
When performing user-directed operations using the NetBackup BAR console, only files
for which the logged-in user has rights are shown.
Perform the following steps to start a user backup operation:
1. From the BAR console, click Select for Backup.
2. Select the desired files and folders for backup by selecting the check box to the left
of the file or folder. To mark all files and folders that currently appear, select Edit >
Mark Displayed Files.
3. Start the backup operation by clicking the Backup button.
The Backup Options window is displayed. The NetBackup server drop-down allows
you to select the master server you wish to use for this backup, if more than one
master server exists for this client.
If a specific policy or schedule should be used, use the Action> Specify Policy and
Schedule dialog prior to clicking on the Backup button.
4. Confirm the backup selection and click Start Backup.

4-25
Viewing user-directed backup job details
BAR
console
Activity
Monitor
26
The View Status dialog box enables you to view the progress of a NetBackup operation.
The status is displayed in the top pane. Select the job that you want to monitor. The
lower pane reflects the progress of the item selected in the upper pane.
The NetBackup operation is finished when the status changes to Successful. If
NetBackup is unable to back up all of the requested files, a status code is displayed a
few lines before the end of the progress report. The NetBackup Status Codes Reference
Guide lists the meaning of the final status code.
You can also monitor user-directed jobs using the Activity Monitor in the NetBackup
Administration Console. User-directed backups display as User_backup in the Job

Schedule column. You can use this to keep track of how many user-directed backups are
being run in your environment.

4-26
Topic: Backup job-related tips
After completing this topic, you will be able to identify common backup job-
related status codes.
27
After completing this topic, you will be able to identify common backup job-related
status codes.

4-27
Common backup policy issues
• Misdefined schedules
Schedule issues • Status code 196 (The client backup was not attempted because the
start window closed.)
• Incorrect policy type or client definition

Client issues • Client software not installed
• Client connection or access
Backup • An incorrect backup selections list

selections issues • Status code 71 (None of the files in the backup selections list exist.)
28
The slide describes some common backup policy issues and troubleshooting.
For additional troubleshooting assistance, refer to the NetBackup Troubleshooting
Guide, to the NetBackup Status Code Reference Guide, or attend the Veritas NetBackup
Maintenance and Troubleshooting course.
• Schedule issues
Problems with schedules typically involve incorrect definitions of policy elements.
Misdefined schedules, clients, or backup selections can lead to a backup failure.
The most common status code associated with policy schedule errors is:
Status code 196: The client backup was not attempted
because the backup window closed.
Due diligence is required on your part to verify that such oversights are corrected.
Evaluate and adjust the policy attributes, as necessary. Extend the backup window to
avoid errors resulting from the backup window being closed.
• Client issues
The slide highlights some common client issues. Some of these are configuration
issues, and a common problem is trying to back up a client which has not had the
NetBackup client software installed, in which case NetBackup cannot communicate
with any NetBackup processes on that client.

4-28
If client connection is a problem, it could be the result of the client being shut down,
NetBackup services not running, networking issues including firewalls, and so on.
Common first steps in troubleshooting are running network testing commands such
as ping, however note NetBackup has its own set of network troubleshooting
utilities.
Refer to Article 100017942: Explanation of bpclntcmd options and recommended
troubleshooting when the commands return errors, found online at
http://www.veritas.com/docs/100017942. Also refer to the NetBackup Commands
Reference Guide for utilities such as nbsu (the NetBackup Support Utility),
bptestbpcd, nbdna, and bptestnetcon commands.
• Backup selection issues
Another common set of issues has to do with incorrectly specifying the backup
selection list. If incorrect directories are specified, or if directories or folders have
changed on the client, then what gets backed up may not match the expectations of
the organization.
If at least one file is backed up then the backup job should return either a status code
of 0 (successful) or 1 (partially successful). If no files are backed up, a status code 71
(None of the files in the backup selections list exist) is displayed.
For additional troubleshooting assistance, refer to the NetBackup Troubleshooting
Guide, to the NetBackup Status Code Reference Guide, or attend the Veritas NetBackup
Maintenance and Troubleshooting course.

4-29
Common NetBackup status codes
Status code Description

1 The backup completed, but not all files were backed up.
71 None of the files in the backup selections list exist.
196 The client backup was not attempted because the backup window closed.
A job has requested any available storage unit, but all storage units are configured with On
2111
Demand Only.
30
The slide highlights some common NetBackup job status codes that indicate that there
was an issue encountered when running a backup job.
NetBackup status code: 1 indicates that the backup was partially successful. With this
status code, you know that at least one file was backed up, but beyond that a problem
occurred.
NetBackup status code: 71 indicates that none of the files in the policy’s backup
selections list exist. Verify the policy file list to ensure that the file names are correct. If
a single client is the source of the error, consider moving it to a different policy.
NetBackup status code: 196 indicates that the backup job was queued, but the start
window closed before the backup could run. A 196 error is usually indicative of a
resource issue, such as there is not enough time for all backups to complete, the
network can be slow, or there may not be enough tape drives to handle the data load.
NetBackup status code: 2111 indicates that the job has requested any available storage
unit, but all storage units are configured with On Demand Only. This can occur in
environments with only disk storage units, where no specific storage unit, storage unit
group, or storage lifecycle policy was specified as a backup storage destination.
For a detailed explanation of these and other status codes, see the NetBackup Status
Codes Reference Guide.

4-30
Reporting on backups
Backed up or archived files Backup, Archive, and bplist

Restore console bpflist
nbfindfile
Job status Activity Monitor bpdbjobs Monitor > Jobs
Reports > Backups > Job
Browser
Reports > Backups >
Status
Reports > Job Reports
Backup status Reports > Status of bperror –backstat -U Reports > Backups >
Backups Status
Reports > Client Reports
31
The table on this slide summarizes how backup jobs can be managed using the
NetBackup Administration Console (GUI), NetBackup commands (CLI), and NetBackup
OpsCenter.

4-31
Lesson summary
• Key points
– You learned to customize the Activity Monitor and suspend, resume, restart, and prioritize jobs.
– You also became familiar with how to initiate manual backup jobs, and how to monitor backup jobs
using the NetBackup Activity Monitor.
– You learned to configure and perform user-directed backups using the Backup, Archive, and Restore
console.
– Finally, you learned how to identify common job-related status codes and to perform basic steps to
troubleshoot failed backup jobs.
– NetBackup Status Codes Reference Guide
– NetBackup Troubleshooting Guide
– OpsCenter Administrator’s Guide
32

4-32
Lab 4: Performing File System Backups
Lab objectives
• Perform tasks to become familiar with the layout and use of the NetBackup Activity
Monitor
• Manually initiate backup jobs using the Java NetBackup Administration Console
• Use the Activity Monitor to monitor and view automated and scheduled backup jobs
• Use the Backup, Archive, and Restore GUI to perform user-initiated backup jobs
• Use the Backup, Archive, and Restore GUI and the Activity Monitor to monitor the status
of user-initiated backup jobs

4-33
What did you learn?
lesson.
34
current lesson.

4-34
Question: End-user initiated backups
Which type of backup can be performed from a client machine by a user or script?
A. Immediate
B. Automatic scheduled
C. Manual
D. User-directed
35

4-35
Answer: End-user initiated backups
Which type of backup can be performed from a client machine by a user or script?
A. Immediate
B. Automatic scheduled
C. Manual
D. User-directed
The correct answer is D.
36

4-36
Question: Manual backups
Manual backups apply only to automatic schedules.
A. True
B. False
37

4-37
Answer: Manual backups
Manual backups apply only to automatic schedules.
A. True
B. False
38

4-38
Question: Methods for initiating backups
Backups can be initiated by many methods. Which method does not apply?
A. Automatically, based on a policy schedule

B. Manually from the NetBackup Administration Console
C. Manually from the command line
D. As a user scheduled backup using the NetBackup scheduler
39

4-39
Answer: Methods for initiating backups
Backups can be initiated by many methods. Which method does not apply?
A. Automatically, based on a policy schedule

B. Manually from the NetBackup Administration Console
C. Manually from the command line
D. As a user scheduled backup using the NetBackup scheduler
40

4-40
End of presentation
4-41
Lesson 5: Performing File System Restores
This is the “Performing File System Restores” lesson in the “Veritas NetBackup 8.1:

5-1
Policies
This lesson is the fifth lesson in this course.


5-2
Lesson objectives
Topic Objective
Describe the restore process and the restore methods used within
Introduction to Restores
NetBackup.
Performing Restore Operations Restore files and monitor restore operations using the Backup,
Using the BAR Interface Archive, and Restore (BAR) interface.
Performing Restore Operations
Restore files and monitor restore operations using OpsCenter
Using OpsCenter Operational
Operational Restore.
Restore
Monitor restore operations, and identify common restore-related
Restore Job-Related Tips
status codes.

5-3
Topic: Introduction to Restores
After completing this topic, you will be able to describe the restore process
and the restore methods used within NetBackup.
After completing this topic, you will be able to describe the restore process and the
restore methods used within NetBackup.

5-4
Data protection
Data protection and

disaster recovery Backup Outage
minimize data loss
Return to Service
and the time T-0 T-1 T-2
between outage and
return to service. Days Hrs Mins Secs Secs Mins Hrs Days
Recovery Point - RPO Recovery Time - RTO
Synchronous Clustering
Traditional replication
Snapshot Standard
backups Asynchronous technologies restore
Snapshot replication
technologies Bare Metal
Restore
Because no one wants to be forced to recover from a disaster, preventing damage to

your data is very important. However, bad things happen. Your job is to make sure that
any damage is repaired as quickly and completely as possible.
Even so, instantaneous perfect recovery of all of your organization’s data from a major
disaster is not always feasible. The cost of attempting to enable that goal would be
astronomical even if it were possible. Therefore, you must prioritize.
Not all data is of equal importance. You can afford to wait for some data; you can
reconstruct or even abandon some data, if necessary; and you must have some data as
soon as possible.
Data protection specialists talk about two important objectives that you should
consider:
• Your recovery point objective (RPO) describes how much you can afford to lose (or
how long it has been since you saved your data, the recovery point). Some
technologies leave longer gaps but these technologies tend to handle larger volumes
of data more cheaply than the alternatives.
• Your recovery time objective (RTO) is the length of time you can afford to take to
return to normal service. Again, different technologies have differing capabilities.
Most people implement a combination of technologies, making use of the advantages
of each. NetBackup can be configured to do exactly that.

5-5
The data restore process
1
NetBackup
logs and NetBackup
reports 4
master
server and
2 catalog
NetBackup
media
server
3
NetBackup Storage
Client Backup
client destination
data image
No backup is worth anything unless the data it contains is available to be restored when
needed. Restores can be performed from the master server by an administrator to
restore the data to the destination client machine. Restores can also be performed at
the request of a user.
The restore flow is described in this diagram.
1. To restore data, use OpsCenter or the NetBackup Backup, Archive, and Restore
interface. The NetBackup master server catalog contains information on what files
and folders have been backed up, and provides the information that the
administrator will then use to select which data to restore.

2. The NetBackup master server uses the information in the NetBackup database to
identify where the backup images are stored, and uses information supplied by the
administrator to decide where they should be restored on the NetBackup client.
3. The appropriate image is retrieved from storage by the media server, and the
selected files are extracted onto the client.
4. Because NetBackup maintains status information about restores in its log files, you
can monitor and report on restores just like backups. Information is also pulled from
the master server by the OpsCenter server on a periodic basis, based on the
OpsCenter configuration.

5-6
Understanding and modifying restore permissions
Server-directed restores
• NetBackup administrators on a master server can restore to any client, by default

• Optionally prevent server-directed restores on the NetBackup client
Client-directed restores
• Only the client that backs up files to restore those files, by default
• Disable all restrictions with the No.Restrictions setting
• Allow specific clients with altnames settings
The default behavior for NetBackup is to allow NetBackup administrators running the
NetBackup Administration Console, which is connected to a master server, to be able to
restore to any client in that environment.
To prevent server-directed restore on a NetBackup client:
• On Windows clients: In the Backup, Archive, and Restore interface, in the toolbar,
select File > NetBackup Client Properties > General, then clear the Allow server-
directed restores check box.
• On UNIX clients: Add DISALLOW_SERVER_FILE_WRITES to the NetBackup

configuration file on the client: /usr/openv/netbackup/bp.conf.
Additionally, the default behavior is that anyone with the ability to run the Backup,
Archive, and Restore interface on a specific client, can only restore that client’s data.
To change client restore permissions, first create the altnames directory on your master
server at install_path\NetBackup\db\altnames (Windows) or
/usr/openv/netbackup/db/altnames (UNIX). Then, within the directory:
• To disable all restrictions to allow any client to restore any clients data, create an
empty file with the name No.Restrictions.
• To allow individual clients to perform redirected restores, create a peername file: A
file named after the NetBackup client which has the ability to restore other clients.

5-7
Restore methods in NetBackup
NetBackup Backup
Archive and Restore
(BAR) interface
Windows Backup
Archive and Restore
(BAR) interface
OpsCenter
Operational Restore
bprestore bprestore -s 02/01/2015 06:00:00 -e 02/10/2010

command 18:00:00 E:\data\smallfiles\file001.txt
There are four different ways to perform restore operations within NetBackup.
• Restores can be initiated from the NetBackup Backup Archive and Restore (BAR)
interface, or by using the Windows Backup Archive and Restore (BAR) interface.
Note: Although the Windows Administration console is no longer supported since
NetBackup 7.7, the Windows BAR tool is still supported, primarily for user backups
of Windows clients. Detailed information about using the Windows BAR console is
provided in Appendix D of this course.
To perform an administrator-directed restore to a specific client, use the Backup,
Archive, and Restore interface on the master server that backs up the source client.
To perform a client-directed restore, use the Backup, Archive, and Restore interface
on a client machine.
• Administrator restores can be initiated from OpsCenter. See the NetBackup
OpsCenter Administrator’s Guide.
• Experienced administrators may prefer to use the bprestore command. See the
NetBackup Commands Reference Guide.

5-8
Topic: Performing Restore Operations Using the BAR
Interface
After completing this topic, you will be able to restore files and monitor
restore operations using the Backup Archive and Restore (BAR) interface.
After completing this topic, you will be able to restore files and monitor restore
operations using the Backup, Archive, and Restore (BAR) interface.

5-9
Restoring files using the Backup, Archive, and Restore interface
Step Action
Select Restore
1
Files tab
Specify machines
2
and policy type
Select restore
3
type
4 Set the view
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
10
To perform a restore using the Backup, Archive, and Restore interface, follow the steps
shown on this slide. This procedure is demonstrated in detail in this topic.
You can start the BAR interface either using the NetBackup Administration Console (by
selecting Backup, Archive, and Restore in the object tree pane), or as a standalone
application. On a Windows client, open nbwin.exe (or click on the Backup, Artchie,
and Restore shortcut), and on a UNIX client, use the jbpSA & command.
By default, NetBackup clients are configured to allow NetBackup administrators on a
master server to direct restores to any clients. These are referred to as Server-directed
restores. To perform an administrator-directed restore to a specific client, use the

Backup, Archive, and Restore interface on the master server that backs up the source
client.
For client-directed restores, by default, NetBackup permits files to be restored only from
backups of the client. The client may not restore from backups of other clients.
NetBackup ensures that the client name of the requesting client matches the peer name
that was used to connect to the NetBackup server. The NetBackup administrator can
modify this behaviour, either on a single client or for all clients. See the NetBackup
Administrator's Guide for details.

5-10
Specifying the NetBackup machines and policy type
Step Action
Select Restore
1
Files tab
Specify machines
2
and policy type
Select restore
3
type
4 Set the view
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
11
One of the first steps is specifying the NetBackup hosts and policy types by selecting
Actions > Specify NetBackup Machines and Policy Type from the menu, or clicking on
the corresponding button. For normal user-directed restores to the original client,
accept the default settings.
• Server to use for backups and restores: This setting defines the master server used
for restore (not the media server). If you need to add a master server to the drop-
down list, click Edit Server List, and add the master server to that list, and then
select that server.
• Source client for restore: When performing server-directed restores or alternate-

client restores, select the client from the drop-down list. Alternatively type the client
name. Be sure to use the correct client name that NetBackup used to backup the
client, otherwise no backup images are found.
• Destination client for restore: Use this field when performing server-directed
restores. For restores to the original client, leave the destination client as is. If you
need to change the destination client, select the corresponding client. Note that the
destination client must have the NetBackup client software installed.
• Policy type for restores: Select a policy type from the drop-down list. If an incorrect
or unused policy type is selected, no valid backups are found for restore.
After you have made all of the necessary selections, click OK.

5-11
Selecting the Restore type
Step Action
Select Restore
1
Files tab
Specify machines
2
and policy type
Select restore
3
type
4 Set the view
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
12
Select the appropriate restore type from the drop-down menu under the Restore Files
tab. Restore type selections include:
• Normal Backups
• Archived Backups
• Raw Partition Backups
• True Image Backups
•
Point in Time Rollback

• Virtual Machine Backups
• Virtual Disk Restore
• Optimized Backups
For most file and folder restores from Standard or MS-Windows policies, select Normal
Backups.

5-12
Setting the view: Modifying the date range
Step Action
Select Restore
1
Files tab
Specify machines
2
and policy type
Select restore
3
type
4 Set the view
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
13
After you specify a restore type, you need to identify the backups you want to view. This
is performed by setting a date range which NetBackup uses to limit the backup images
examined for restores. Instead of specifying a date range, you can choose your backup
from a list. This changes the date range based on the selected images. From these
backups, you eventually select the files for restore.
The Backup, Archive, and Restore interface provides two ways to set this date range:
• Specify a date range
You can specify a range of dates for the backups you want to view. Click the Use
calendar to set date range button, and the Date Range dialog box is displayed. Select
a Start Date and an End Date and click OK.
• Backup list
Click the List Backups button to display a list of backups. Select the full backup, as
well as the subsequent differential or cumulative incremental backups. Effectively,
this just sets the start date and end date that NetBackup uses to examine prior
backups.

5-13
Setting the view: Identifying restorable files
Step Action
Select Restore Most recent Show all backups
1 backup in the range
Files tab
Specify machines
2 Refresh
and policy type
Select restore
3 Search
type
backups
4 Set the view
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
14
After selecting the backup images you wish to restore from, you should see a list of files
and folders you can restore from at the bottom pane. If a timeframe was selected that
includes multiple backup images, then it is possible that multiple versions of a file or
folder can be restored. By default, the Backup, Archive, and Restore console displays the
most recent version of the file, for the backup images that are currently selected by the
date range specified.
If you want a list of all files from the selected backups, including files for which there are
multiple versions from different dates, click the Show all backup in the specified date
range button. If you want to return to view only the latest version of the files, click the
Show most recent backup in the specified date range button.
To search for files in a backup, click the Find items to restore button.
To browse for files in a particular location, set the Browse directory as appropriate.
Note that the default browse directory may be set in a manner which does not
correspond to files or folders that have been backed up. Set it to “/” manually, if
necessary.
To determine which files can be restored, you may need to refresh the screen. Select
View > Refresh. The items you can restore are displayed in the Contents of selected
directory list. From this list, determine which files you can restore.
It is possible that a restore requires data stored on multiple backup images. Examples of
such a distribution of backup images include:
• Restore from full and incremental backups.

5-14
NetBackup’s default search range is for the most recent backups since the last full
backup. You can modify the search range if you want to restore an image other than
the most recent image.
• Restore from a backup series.
Cumulative incremental backups require a full backup and the most recent
cumulative backup in the series. Differential incremental backups require a full
backup and all of the differential backups in the series.
• Restore a specific version of a file or directory.
To restore an older version of a folder or a file, specify a time range within which
you know it existed. Select only backups that include the version of the directory or
file to restore.
Alternatively, the bplist command displays a list of previously backed-up or archived
files based on the options that you specify. The file list generated by bplist shows
only the files to which you, as the user, have read access. You must also own or have
read access to all directories in the file paths. You can list files that were backed up by
another client only if you are validated to do so as a NetBackup administrator.
Directories output by bplist can be recursively displayed. The output of bplist is
directed to standard output.
bplist examples
The following example recursively lists files on train2 that were backed up on or after
February 25, 2010 in D:\myfiles:
bplist –C train2 –l –s 2/25/10 –R D:\myfiles
The following example displays all files that were backed up.
bplist –C train2 –l –s 01/01/10 –R /
The following example filters out a directory of files that were backed up.
bplist –C train2 –l –s 01/01/10 –R D:\myfiles
The –t option enables bplist to reference different policy types. The following
example is for bplist syntax for Microsoft Exchange backups.
bplist –C train2 –t 16 –l –s 01/01/10 –R /
For a detailed explanation of the options you can use with the bplist command, see
the NetBackup Commands Reference Guide.
Technical Article 100016074: A listing of policy types and how they are used with bplist
and other NetBackup commands (http://www.veritas.com/docs/100016074) describes
policy types and how they are used with bplist and other NetBackup commands.

5-15
Marking files to restore
Step Action
Select Restore
1
Files tab
Specify machines
2
and policy type
Select restore
3
type
4 Set the view
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
16
To mark a folder for backup or restore, select the check box to the left of the folder.
• A checked box ( ) indicates that all of the files and subfolders within that folder
are marked.
• A partially checked (forward slash mark) box ( ) indicates that only some of the
files or subfolders within that folder are marked.
• To mark all the files (and folders) that are currently displayed, select Edit > Mark
Displayed Files.

5-16
Preview the required media
Step Action Tape
Select Restore
1
Files tab
Specify machines
2
and policy type
Select restore
3
type
4 Set the view
5
Mark files to Disk
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
17
After selecting the files and folders to restore, click the Preview button.
The Media Required dialog box is displayed with a list of the media required to perform
the restore. Use the contents of this dialog box to verify which media are required to
perform the restore. This helps you determine if you require a tape that is currently
offsite or otherwise unavailable.
Note that for disk-based media, the Preview button is not necessary, and returns the
message “No media is required for restore. Images are on Disk.” If the backups are on
disk, instead an informational message is provided to inform you that no media is
required for the restore.

Click Restore to start the restore job. The Restore Marked Files dialog box is displayed
and you are required to define some final parameters before the restore operation
starts.

5-17
Set destination and restore options
Step Action
Select Restore
1
Files tab
Specify machines
2
and policy type
Select restore
3
type
4 Set the view
Mark files to
5
restore
Preview required
6
media
Set destination /
7 Initiate the
restore options
restore
8 Initiate restore
9 Monitor restore
18
The Destination pane of the Restore Marked Files dialog box grants you varying levels
of control over the placement of the files:
• Restore everything to its original location (Default): Restores items to the file or
path from which they were backed up
• Restore everything to a different location (maintaining existing structure): Restores
items to a file or path other than the path from which they were backed up
• Restore individual directories and files to different locations: Restores items to
paths other than the path from which they were backed up
• Create and restore to a new virtual hard disk file: For Windows 2008 R2 clients and
Windows 7 clients, you can restore marked items to a new, virtual hard disk (VHD)
file. If you select this option, you must specify a new VHD file. You cannot restore to
an existing VHD file with this option.
When you enter the destination path and the file name for the new VHD file, do not
include the .vhd extension. The extension is added automatically.
After you enter the new destination path and the file name, click Setting. Set the
VHD file size and select the behavior of the file as follows:
• Virtual hard disk size: Select the VHD file size. Ensure that you do not exceed
the maximum available amount of space.
• Dynamically expanding (default): If you select this option, the VHD file expands
up to the specified virtual hard disk size.

5-18
• Fixed size: If you select this option, the VHD file is created by using the specified
virtual hard disk size, regardless of the amount of data to be restored.
The Options pane shows the remaining options granting control over how NetBackup
handles files that may already exist:
• Overwrite existing files: This option must be enabled if the restore operation is
required to replace any existing versions of files to be restored. By default this is not
enabled.
• Restore all directories without crossing mount points: This option restricts the
restore to the contents of a single file system.
• Restore without access-control attributes (Windows clients only): An access
control list (ACL) is a table that conveys the access rights that users have to a file or
directory. Each file or directory can have a security attribute that extends or restricts
users’ access.
The option to restore file and directory data without restoring ACLs is available if the
destination client and the source of the backup are both Windows systems. To
restore files without restoring ACLs, the following conditions must be met:
• The policy that backed up the client must have been of policy type MS-Windows.
• The restore must be performed by an administrator logged in to a NetBackup
server (Windows or UNIX). The option is set from the client interface running on
the server. The option is unavailable on stand-alone clients (clients that do not
contain the NetBackup server software).
• The destination client and the source of the backup must both be systems
running supported Windows OS levels. The option is disabled on UNIX clients.
To restore files without restoring ACLs, mark the Restore without access-control
attributes (Windows clients only) check box.

• Rename hard links and Rename soft links: These options request NetBackup to
rename the appropriate links when restoring to an alternate location.
For example, if restoring to an alternative boot disk, it is necessary to rename hard
links for the system to boot from the restored disk, but soft links should not be
renamed.
• Use default progress log filename: To write the progress messages to a log file other
than the default, clear the Use default progress log filename check box, and then
enter the name of the alternative progress log.
• Override default priority: Select this option to change the priority for the current
restore operation. The available range is 0 - 99999. The higher the number, the
greater the job priority.
After you have selected all of the necessary options, click Start Restore.

5-19
Monitoring restore operations using the BAR interface
Step Action
Select Restore
1
Files tab
Specify machines
2
and policy type
Select restore
3
type
4 Set the view
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
20
You can monitor the progress of the restore operation from the Task Progress tab in the
Backup, Archive, and Restore interface.
Here you see the progress of the restore job as it executes. If an error is encountered,
determine the cause of the problem and perform corrective actions.
Restores can also be monitored from the Activity Monitor in the Administration
Console.

5-20
Topic: Performing Restore Operations Using OpsCenter
Operational Restore
After completing this topic, you will be able to restore files and monitor
restore operations using OpsCenter Operational Restore.
21
After completing this topic, you will be able to restore files and monitor restore
operations using OpsCenter Operational Restore.

5-21
Understanding OpsCenter Operational Restore
• A simplified search and retrieval feature only available in NetBackup OpsCenter

• Finds and restores files across multiple clients and domains
• Includes options similar to the Backup, Archive, and Restore (BAR) console, but with
additional search capabilities
• Includes a restore cart
• Enables previews of required media, including the ability to export this data in multiple
formats
• Does not require additional licensing or infrastructure
22
Operational Restore provides a simplified search and retrieval mechanism that works
across multiple NetBackup domains, and was introduced in NetBackup OpsCenter 7.5.
Although it requires an OpsCenter server, it comes at no cost and does not require any
license.
This feature enables restores to be initiated using the OpsCenter Web console and
removes the need to install the BAR console on customer workstations. The search
capabilities facilitate searches without requiring specialized knowledge of the backup
environment.
Operational Restore includes enhanced filtering selection, the ability to use wildcards
for search, and manual browsing of directory and sub-directory structures of backed-up
images for files with specific metadata. Additionally, a restore cart enables you to view
file selections from multiple search and browse operations and restore them at a later
time, or to preview the media required. No additional licensing or infrastructure is
necessary.
For additional information on using Operational Restore, see the NetBackup OpsCenter

5-22
Accessing the Operational Restore interface
Step Action
Click Manage >
1
Restore
Click Restore Files
2
and Directories
3 Set search criteria
4 Start the search
Select files and

5
folders to restore
Specify target and
6
restore options
Preview the
7
required media
8 Initiate restore
9 Monitor restore
23
To browse for files and directories for restore:

1. Access the Operational Restore interface in the OpsCenter console by navigating to
the Manage > Restore tab.
2. Click Restore Files and Directories.

5-23
Accessing the Operational Restore interface
Step Action
Click Manage >
1
Restore
Click Restore Files
2
and Directories
4 Start the search
Select files and

5
folders to restore
Specify target and
6
restore options
Preview the
7
required media
8 Initiate restore
9 Monitor restore nbfindfile
24
After clicking the Restore Files and Directories link, the Files and Directories Restore
wizard is displayed.
The Files and Directories Restore wizard consists of three panels:
• Select Files or Directories enables you to perform simple or advanced search
operations for locating specific files or directories that you want to restore.
• Restore Options enables you to select a number of restore options, such as
destination client, destination path, and overwrite options for the selected client.
• The Summary displays the list of files or directories that you have selected for
restore.

5-24
Performing a simple search
Step Action
Click Manage >
1
Restore
Click Restore Files
2
and Directories
4 Start the search
Select files and

5
folders to restore
Specify target and
6
restore options
Preview the
7
required media
8 Initiate restore
9 Monitor restore
25
Under the Select Files or Directories tab, the Search tab is displayed.
3. Make your search selections based on the following search criteria:
• Select a time frame that you want to search. The default time frame is Month.
• File or Directory name: Enter a full path using a path delimiter of forward slash (/)
on UNIX or back slash (\) on Windows, or enter a specific file or directory name.
Alternatively, if the exact directory or file name is not known, use the * (any number
of any characters) and ? (any one character) wildcards.
• Search within Clients: Specify the set of clients whose backup information you want
to search. You can search multiple clients from multiple master servers.
• Select a view from the View drop-down list.
• Select a master server from the Master Server drop-down list. All NetBackup
master servers that are a part of the selected view are displayed.
• Specify the clients whose backup information you want to search.
When you click Browse and select clients, the Browse Clients dialog box is displayed.
The following options are displayed in the dialog box:
• Selected View: The view that you selected from the View drop-down list is
displayed. If you select a view of type Master Server, all NetBackup master servers
that are added to the view are displayed under the Name column. If you select a
client-type view, the clients are displayed under the selected view in the Name
column.

5-25
• Filter Clients: You may want to view specific clients when the client list is large. To
filter specific clients, enter a client name, part of a client name, or add the *
wildcard.
• Name: If you select a Master Server type view, each master server is displayed with
a + sign next to it. When you expand a master server, you can see the protected
clients that are associated with it. If you select a client-type view, clients are
displayed. Mark the check box next to one or more clients and click OK.
Veritas recommends using the fully qualified domain name (FQDN) for clients, to avoid
confusion and name conflicts. The image catalog contains a directory for each client
name as specified in the policy, so the name of the client that was backed up must be
the name of the client for the source client.
After you select the clients, a table is displayed that provides the client names and the
master servers associated with the clients. If you want to remove a specific client, click
Remove.

5-26
Performing an advanced search
Step Action
Click Manage >
1
Restore
Click Restore Files
2
and Directories
4 Start the search
Select files and

5
folders to restore
Specify target and
6
restore options
Preview the
7
required media
8 Initiate restore
9 Monitor restore
27
To perform an advanced search, you can specify advanced search criteria in addition to
the simple search criteria. The Advanced Search criteria are optional. For more
information about the advanced search criteria, see the NetBackup OpsCenter

5-27
Starting the search
Step Action
Click Manage >
1
Restore
Click Restore Files
2
and Directories
4 Start the search
Select files and

5
folders to restore
Specify target and
6
restore options
Preview the
7
required media
8 Initiate restore
9 Monitor restore
28
4. After you have made all of your search selections, click Search.
It may take some time for OpsCenter to display the search results. The time to
display the search results may increase with the number of selected clients.
OpsCenter highlights the search results at the bottom of the pane in a table.
This slide presents the procedure to browse the protected files and directories on a
client. This method enables you to select the client to be browsed and specify a time
frame for backup selection. You can select only one client at a time. The most recent
backup in the specified date range is shown by default.
Under the Search tab, you can see that the search has completed successfully. Search
results are displayed while the search is in progress.
The filter button ( ) at the top of the search results table enables you to further filter
the search results. The result is a filtered subset of the last search result from the
OpsCenter database.
You can also customize the search results table to display sort order, page size, columns
displayed, and column order. Click the Change Table Settings ( ) icon at the top of the
search results table to access the table customizations page.
By default, the search results table lists the following default columns: File or Directory
Name, File or Directory Path, Backup History, Last Backup Time, Modified Time, Client,
and Size. Operational Restore enables you to add Master Server, Last Accessed Time,
and Backup ID columns to the table.
If there are additional results, the number of rows and pages is displayed.

5-28
You can also use the nbfindfile command to search files or directories based on
simple search criteria. This command can be executed from the NetBackup master
server, not the OpsCenter Server. For more information about the nbfindfile
command, see the NetBackup OpsCenter Administrator’s Guide or the NetBackup
Commands Reference Guide.

5-29
Selecting files and folders to restore
Step Action
Click Manage >
1
Restore
Click Restore Files
2
and Directories
4 Start the search
Select files and

5
folders to restore
Specify target and
6
restore options
Preview the
7
required media
8 Initiate restore
9 Monitor restore
30
5. To select one or more files or directories to restore, mark the check box next to the
file or directory.
• To restore the files or directories now, click Restore now.
• If you want to add the selected files and directories to the Restore Cart and
restore them at a later time, click Add to Restore Cart.
To display the backup history, click the Backup History Selection link for the file or
directory that interests you. The Backup Timeline window is a timeline view of backups
for a specific file or directory. At the top of the Backup Timeline window, the name and
location of the selected backup’s file or directory are displayed. The timeline displays
icons that each represent a different backup or snapshot. By default, the primary
backup copy of the most recent backup for this file or folder is selected, however this
window enables an alternate backup copy to be chosen by clicking on that icon.
The Backup table in the middle of the window displays information about the backup
that is selected from the timeline view. It displays information, such as backup time,
policy name, policy type, backup type, and so on. Click an icon to view the details of the
specific backup in the Backup table. After you select the specific backup image that you
want to restore from the Backup table, the copies that are associated with the backup
image are displayed in another table at the bottom of the window. The Copies of
Selected Backup table displays information about the copies that are associated with
the selected backup image. By default, the primary copy is selected.

5-30
Viewing the Restore Cart and specifying target and restore options
Step Action
Click Manage >
1
Restore
Click Restore Files
2
and Directories
4 Start the search
Select files and

5
folders to restore
Specify target and
6
restore options
Preview the
7
required media
8 Initiate restore
9 Monitor restore
31
6. Select the target and restore options.

The Restore Cart enables you to view file selections from multiple search and browse
operations and restore them at a later time. You may also choose to restore all the file
or directory selections at once. The Restore Cart selection persists for each user across
different OpsCenter sessions. After a file belonging to the Restore Cart is sent for
restore, it is automatically removed from the Restore Cart for the specific user.
You can perform several operations on the files and directories in the Restore Cart. You
can email or export the contents of the Restore Cart. You can also restore or remove
files from the Restore Cart. For more information about performing operations on the
Restore Cart, see the NetBackup OpsCenter Administrator's Guide.
When you click Restore now, the Restore Options panel is displayed.
You can specify restore options for the files and directories that you selected, such as
destination client and paths, and overwrite and access control options. This panel
enables you to specify the restore options for each source client from which a file or
directory has been selected to be restored.

5-31
Previewing the required media
Step Action
Click Manage >
1
Restore
Click Restore Files
2
and Directories
4 Start the search
Select files and

5
folders to restore
Specify target and Disk
6 Tape
restore options
Preview the
7
required media
8 Initiate restore
9 Monitor restore
32
7. Prior to initiating the restore, click Preview Media to view the media required for
the restore operation and to determine the availability of the required media.
The Preview Media dialog box is displayed. This helps you determine whether the
required tape is in the library. If the selected backups are all on disk, this option is
not applicable.
When you have finished with the Preview Media dialog box, click Close.

5-32
Restoring files and directories on a client using Operational
Restore
Step Action
Click Manage >
1
Restore
Click Restore Files
2
and Directories
4 Start the search
Select files and

5
folders to restore
Specify target and
6
restore options
Preview the
7
required media
8 Initiate restore
9 Monitor restore
33
The Summary panel displays the list of files and directories that have been selected for
restore. It also displays information about the current location of these files and
directories and where they are to be restored.
The Summary panel shows a table that includes the source file name, the source file
path, the source client, the destination file path, and the destination client.
At this point, you have one last opportunity to remove files or directories from the
Summary panel. To remove files or directories that you do not want to restore, click the
Remove files or directories button.
8. In the Summary panel, click Restore to restore all the files or directories.
The corresponding restore jobs are triggered, and the File or Directory Restore
Launch Status dialog box is displayed. This dialog box identifies the job ID of the
restore job, the name of the master server that is associated with the client on
which the file resides, and the name of the source client.
Click OK to navigate to the OpsCenter Monitor > Jobs tab and view the job progress
details.
The Monitor > Jobs view provides details about NetBackup jobs. In this example,
detailed information about Job ID 264, the restore job, is displayed. Notice that the job
is selected in the content pane, and additional information is displayed in the details
pane.

5-33
Topic: Restore Job-Related Tips
After completing this topic, you will be able to monitor restore operations,
and identify common restore-related issues.
34
After completing this topic, you will be able to monitor restore operations, and identify
common restore-related status codes.

5-34
Monitoring jobs using the Activity Monitor
35
You can also monitor the progress of the restore operation from the NetBackup
Administration Console Activity Monitor.
Suspending and resuming a restore job
If you are a NetBackup administrator, you can suspend a checkpointed restore job and
resume the job at a later time.
For example, while running a restore job for several hours, you may receive a request
for a second restore of a higher priority that requires the resources being used by the
first job. You can suspend the first job, start the second restore job, and let it complete.
You can later resume the first job from the Activity Monitor and let that job complete.
To suspend a restore job, right-click the job in the Activity Monitor and select Suspend.
To restart the job, right-click the suspended job and select Resume. You can also use the
Suspend ( ) and Resume ( ) buttons in the toolbar.
Limitations to Checkpoint Restart for restore jobs include the following:
• The restore restarts at the beginning of the last checkpointed file only, not within
the file.
• Only the backups that are created using Standard or MS-Windows policy types are
supported.
• Third Party Copy and Media Server Copy images that use Standard policy types are
supported, but cannot be suspended or resumed if the backup image has changed
blocks.

5-35
Cancelling a restore job
If you are a NetBackup administrator, you can cancel a restore job from the Activity Monitor
by right-clicking the job and selecting Cancel.
Consider the following ramifications of cancelling a restore job:
• Even though a restore job is cancelled and is reported as such, all files written up to that
point are considered “restored.”
NetBackup does not replace the files restored to that point with the files that existed
before the restore operation started.
• The last file written at the time of the cancellation may be corrupted.
Performing restore operations using the bprestore command
Use the bprestore command to restore backed-up or archived files, lists of files, or
directories. The bprestore command restores the files from the most recent backups
within the period you specify, except for a true image restore. See the NetBackup
Administrator’s Guide for details of this functionality.
For a detailed explanation of the bprestore command, see the NetBackup Commands
Reference Guide.
The bprestore command must include the file list to be restored, which can be specified by
using:
• The list of files following the command
• The -f parameter to specify the location of a file containing the file list
To restore a file, a user must have read access to the backed-up file and write access to the
desired destination where the file is to be placed when it is restored.

5-36
Common restore issues
Issue Resolution
Incorrect interpretation of • Check the spelling of the path, file name, and exclude rule.
restore directives • Ensure no information is missing.
Insufficient disk space Ensure there is sufficient space on the destination client or file system.
Improper file permissions Ensure you have read permission for files in the backup image and write
permission for the restore destination.
Access control lists (ACLs) • Ensure the restore is not cross-platform.
• Ensure the tar file is a NetBackup-modified tar file.
Restore from non- Change the primary copy image from tape to disk or from offsite to onsite.
preferred location
Incorrect restore criteria Confirm the policy type, server and client names, restore type, browse
directory, and date range.
37
Problems with restores can include the following:

• Incorrect interpretation of restore directives
If you are restoring by using the bprestore command, or if you manually type
information, such as a path, file name, or exclude rule, ensure that you have
correctly spelled all entries and have correctly typed all other information.
• Insufficient disk space for restores
Ensure that the destination client or file system to which you are restoring has
enough disk capacity to hold the restore.

• Improper file permissions
Ensure you can read the files that were backed up in the image and have write
permission for the restore destination
• Access control lists (ACLs)
By default, the NetBackup modified GNU tar restores ACLs along with file and
directory data. In the following situations, the ACLs cannot be restored to the file
data:
• Where the restore is cross-platform (such as restoring an AIX ACL to a Solaris
client, or restoring a Windows ACL to an HP-UX client)
• When a tar other than the NetBackup-modified tar is used to restore files

5-37
In these instances, NetBackup stores the ACL information in a series of generated
files in the root directory using the following naming form:
.SeCuRiTy.nnnn
These files can be deleted or read with the ACLs regenerated manually.
Note: You can restore files without restoring ACLs if the destination client and the
source of the backup are both Microsoft Windows systems. See the NetBackup
Administrator’s Guide for details.
• Restore from non-preferred location
Each backup is assigned a primary copy. NetBackup uses the primary copy to satisfy
restore requests. If the primary copy is not the desired copy, promote the desired
copy to the primary. For example, if the primary copy is on tape and the duplicate
copy is on disk, promoting the duplicate copy to primary ensures a faster restore.
This behavior is discussed if further detail in the Duplicating Backups lesson.
• Incorrect restore criteria
Ensure that you have defined the proper settings for the restore job, such as the
policy type and NetBackup server.
Debug logs for restore operations
The bprestore command writes informational and error messages to a progress log
file if you create the file prior to running the bprestore command and specify the file
with the -L progress_log option. You can use the progress log to find the reason
for the failure if bprestore cannot restore the requested files or directories.
You can also create debug logs for the bplist and bprestore commands by
creating the following directories on the machine from which you run the commands:
• UNIX
/usr/openv/netbackup/logs/bplist/
/usr/openv/netbackup/logs/bprestore/
• Windows
install_path\NetBackup\logs\bplist
install_path\NetBackup\logs\bprestore
Create these directories with public-write access. The commands create debug logs
within the respective directories, which you can use for detailed troubleshooting.
If a non-root user is specified under USEMAIL = mail_address in the $HOME/bp.conf
file of a NetBackup UNIX client, NetBackup sends an e-mail containing the restore
completion status to mail_address. This message is sent when the restore process
completes.

5-38
Verifying correct restore criteria
Incorrect server, client
Incorrectly set names, or policy type?
restore type?
Incorrect browse Incorrectly selected date

directory? range or backups?
39
When attempting a restore, you may receive an error stating No Files Found. This is a
common occurrence when some of the restore fields aren’t set correctly for the data in
question. Some parameters to check include:
• Source client: Make sure to use the correct host name for the source client. If the
image was registered under the short name, console, then use the short name. If
the backup was done using the FQDN, console.example.com, use the FQDN
• NetBackup server: Ensure that the correct master server name is used.
• Date range: Enter the date range for valid backups. If the date range you are using
doesn’t yield any results, verify that backups completed for that client, during that
time.
• Browser directory: The directory needs to be set so that it is valid for the backup
data. If the default directory shown is for data that was not included in the backup,
then no files will be found. Change the folder to one that is relevant to your backup.
This primarily applies to UNIX and Linux-based images.
• Restore type: If a restore type is chosen that doesn't match your backup, then no
data will be shown. For many backup types, the Normal Backups restore type
should be chosen.
• Keyword: Ensure this entry is clear, if keywords are not being used. Otherwise the
backup images shown will be limited to those using the keywords selected.

5-39
Reporting on restores

List files Backup, Archive, and bplist
Restore GUI nbfindfile
Restore job status Activity Monitor bpdbjobs Monitor > Jobs

Reports > Restore
Reports
40
The table on this slide summarizes how restore jobs can be managed using the
NetBackup Administration Console, NetBackup commands, and OpsCenter.

5-40
Lesson summary
• Key points
– You now know how to initiate and monitor restore operations using the Backup, Archive, and Restore
interface and Operational Restore.
– You also know how to monitor restore jobs.
– Finally, you learned how to identify common restore-related status codes.
– NetBackup Status Codes Reference Guide
– NetBackup Backup, Archive, and Restore Getting Started Guide
– OpsCenter Administrator’s Guide
41

5-41
Lab 5: Performing File System Restores
Lab objectives
• Become familiar with key restore settings in the Backup, Archive, and Restore GUI
• Restore files using the Backup, Archive, and Restore GUI:
– Restore files to the original client and client folder location
– Restore files to an alternate folder location on the client
– Restore files to an alternate client system
• Use the Task Progress UI to monitor progress of restore operations
• Use the Activity Monitor to monitor the progress of restore jobs
• (Optional) Perform file system restore operations using the OpsCenter Operational
Restore interface
42

5-42
What did you learn?
lesson.
43
current lesson.

5-43
Question: Initiating restores
By default, restores can be initiated by an administrator from the Backup, Archive, and
Restore interface or by a user on a client machine.
A. True
B. False
44

5-44
Answer: Initiating restores
By default, restores can be initiated by an administrator from the Backup, Archive, and
Restore interface or by a user on a client machine.
A. True
B. False
45

5-45
Question: Which restore method works across domains
Which restore method enables simplified search and retrieval across multiple
NetBackup domains?
A. The Backup, Archive, and Restore interface

B. The OpsCenter Operational Restore feature
C. The NetBackup Administration Console
D. The NetBackup Operations Manager interface
46

5-46
Answer: Which restore method works across domains
Which restore method enables simplified search and retrieval across multiple
NetBackup domains?
A. The Backup, Archive, and Restore interface

B. The OpsCenter Operational Restore feature
C. The NetBackup Administration Console
D. The NetBackup Operations Manager interface
47

5-47
Question: No backup image content is displayed
A restore using the Java BAR is being attempted. Care has been taken to select the appropriate source
client, but no backup image content is displayed. What could be a reason for this to happen?
A. The wrong policy type has been specified.

B. The date range is incorrect.
C. The path does not exist in the images that have been selected.
D. All of the above.
48

5-48
Question: No backup image content is displayed
A restore using the Java BAR is being attempted. Care has been taken to select the appropriate source
client, but no backup image content is displayed. What could be a reason for this to happen?
A. The wrong policy type has been specified.

B. The date range is incorrect.
C. The path does not exist in the images that have been selected.
D. All of the above.
49

5-49
End of presentation
5-50
Lesson 6: Configuring Disk Pools
This is the “Configuring Disk Pools” lesson in the “Veritas NetBackup 8.1:

6-1
Policies
This lesson is the sixth lesson in this course.


6-2
Lesson objectives
Topic Objective
Understanding disk pools and Describe disk-based storage, including disk pools and AdvancedDisk
AdvancedDisk storage.
Configure storage servers, AdvancedDisk disk pools, and
Configuring AdvancedDisk
AdvancedDisk storage units.
Monitor and report on configured AdvancedDisk disk pool devices,
Managing AdvancedDisk storage
as well as perform common AdvancedDisk management tasks.

6-3
Topic: Understanding disk pools and AdvancedDisk
After completing this topic, you will be able to describe disk-based storage,
including disk pools and AdvancedDisk storage.
After completing this topic, you will be able to describe disk-based storage, including
disk pools and AdvancedDisk storage.

6-4
NetBackup disk storage types
BasicDisk Uses a directory to store backup data.

• Lesson: Configuring NetBackup Storage
• Document: NetBackup Administrator’s Guide Covered in this lesson
• License: None required
AdvancedDisk Uses a disk pool (a collection of disk volumes).

• Lesson: Configuring Disk Pools
• Document: NetBackup AdvancedDisk Solutions Guide
OpenStorage Used with storage supporting Veritas OpenStorage API.

• Ease Backups
• Lesson: Configuring Disk Pools and Duplicating of management: Manages
Using Storage Lifecycle Policies multiple disk volumes as one
logical destination and supports storage lifecycle policies
• Document: NetBackup OpenStorage Solutions Guide for Disk
• Robust feature set: Support media server load balancing and
PureDisk Usesspanning
a Media Server Deduplication Pool (MSDP).
disk volumes
• Scalable: Easily expand
• Lesson: Configuring Media Server Deduplication capacity; Handles unlimited
• Document: NetBackup Deduplication Guide
theoretical
• License: NetBackup Data Protection Optimization Optioncapacity
The slide reviews disk storage types in NetBackup (listed by the corresponding disk type
identification categories used in NetBackup), including BasicDisk, AdvancedDisk,
OpenStorage and PureDisk.
This lesson discusses the AdvancedDisk storage type, specifically using simple disk pools
of multiple disk volumes, on a single media server.
Creating disk pools in NetBackup offers several benefits over basic disk storage units.
Resources are used more efficiently by logically combining disk resources on a single
server or across multiple servers. Using disk pools unlocks a number of additional
features, including capacity management, data classifications, storage lifecycle policies,

and media server load balancing.
Disk volumes can be added to a disk pool to increase capacity, and there is no inherent
limitation for capacity size of the disk pool.

6-5
Disk storage terminology
Disk
enclosure Storage server
(logical)
OpenStorage
Technology (OST)
Disk
volume Disk pool Media
server
(physical)
This slide describes basic disk backup terminology.

• A disk enclosure is a physical container with disk storage, such as a disk array.
• A disk volume is a logical unit of disk storage, as presented by the host operating
system, such as a partition or Volume Manager volume.
• A disk pool is a collection of disk volumes administered in NetBackup as a single
entity. Storage units are configured to target a single disk pool for backup.
• A media server is a NetBackup system that manages the writing of backup data to
storage media. Traditionally, the storage media may be either disk or tape media.
• OpenStorage Technology (OST) is a Veritas API that allows NetBackup to
communicate and manage various storage implementations to integrate backup
functionality, including share disks, balance load and performance, use the disk
appliance capabilities such as deduplication, provision storage, and optimize
duplication and replication.
• A Storage server is an entity that was created in NetBackup to write the data to and
read the data from the disks that support OST. In some cases, such as NetBackup
AdvancedDisk, the storage server and the media server reside on the same
NetBackup system. In other cases, the NetBackup media server communicates with
a storage server provided by Veritas or another storage vendor using NetBackup
OST.

6-6
Using NetBackup appliances
NetBackup Appliances:
• Simplify initial configuration and daily management of
the backup environment.
• Perform the role of storage server and media server in
one.
• Allow configuration of both AdvancedDisk and
deduplication (MSDP) disk pools using the included
storage disk volumes.
• Come in multiple form factors, such as the NetBackup
5240 and 5330 appliance, with continually increasing
performance and storage capabilities.
• Have additional capabilities that include deduplication,
multiple connectivity options (Ethernet and Fibre
channel), and replication.
The NetBackup appliance is a solution that simplifies the initial configuration and daily
management of your backup environment. The goal is to provide a solution that
eliminates the need to provide dedicated individuals to manage the backup
environment.
NetBackup appliance deployment consists of the complete installation and
configuration of all appliance components to create a backup environment that is ready
to use. NetBackup appliances can be easily integrated into an existing NetBackup
environment.

6-7
Using third-party OpenStorage vendors
• Use vendor-supplied software plug-in, installed on media servers that communicate with
the OST server
• To find supported functionality and capabilities:
– Refer to the Hardware and Cloud Storage Compatibility List (HCL) at
http://www.netbackup.com/compatibility
– Includes OpenStorage - Supported Functionality:
– Includes OST Storage Servers - Vendor Compatibility:
OpenStorage is a Veritas API that enables NetBackup to communicate with the storage
implementations that conform to the API. Disk appliance vendors participate in the
Veritas OpenStorage Partner Program. Veritas qualifies their storage solutions for the
OpenStorage API. The vendor's storage controls the storage format, the location where
the images reside on the storage, and the data transfer method. As a result,
performance and storage utilization are highly optimized.
Third-party OpenStorage servers include disk appliance vendors that provide a software
plug-in that is installed on the NetBackup media server. NetBackup media servers use
the plug-in to communicate with the disk appliance.

From the NetBackup master server, a disk pool is created that points to the disk
vendor’s appliance, which is now known as a storage server. NetBackup determines
when backup images are created, copied, or deleted. Images are moved, expired, or
deleted on the storage when NetBackup instructs the appliance to do so through the
API.

6-8
Topology with third-party OpenStorage vendors
OpenStorage Media Master

vendor servers server
• Disk pool • NetBackup Plug-in

• Disk enclosure installed
• Storage server • Media server
In the event that third-party OpenStorage vendors are being used in a NetBackup
environment, the OpenStorage vendor’s disk array is considered the disk enclosure and
the disk pool. The disk array is also the storage server, since it is responsible for the I/O
to and from disk.
To be able to communicate correctly with the OpenStorage vendor’s disk array, the
NetBackup media server need to ensure that a NetBackup plug-in, which is provided by
the third-party vendor, is installed.
This is an environment where the media server and storage server are not contained in
the same server.

6-9
Using cloud storage vendors
• Use vendor- or Veritas-supplied software plug-in, installed on media servers that

communicate with the cloud server
• To find supported functionality and capabilities:
– Refer to the Hardware and Cloud Storage Compatibility List (HCL) at
http://www.netbackup.com/compatibility
– Includes Cloud - Supported Technology Methods:
– Includes OST Cloud - Vendor Compatibility:
10
OST Cloud Storage plug-ins enable Veritas NetBackup to access Cloud Storage Solutions.
Either the storage vendor or Veritas provides a software plug-in, which is installed on
each NetBackup Media Server that is connected to the cloud solution.
Supported vendors may include ACP, Amazon, AT&T, China Mobile, China Telecom,
Chunghwa Telecom, Cloudian, Datish Systems (OpenDedup), Deutsche Telekom, EMC,
Fujitsu, Google, HGST, Hitachi, Huawei, IBM, Microsoft, NetApp, Oracle, Quantum,
Rackspace, Red Hat, Scality, StorReduce, SUSE, SwiftStack, Telefonica, and Veritas.
OST Cloud support information, including a detailed list of supported vendors, solutions,
and functionality, is listed in the Hardware and Cloud Storage Compatibility List (HCL) at
http://www.netbackup.com/compatibility.

6-10
NetBackup cloud storage topology
WAN LAN
Cloud storage
vendor Master
Media
servers server
Cloud storage
• Disk pool
data mover
• Disk enclosure
• Storage server
Clients
11
In an environment using a cloud storage vendor, the storage server is the cloud vendors
server. The data movers are the NetBackup media servers, which are assigned to the
storage units that target the disk pool with the cloud storage server.
Multiple cloud storage data movers can target the same cloud storage disk pool, to
assist with load balancing the client’s data.

6-11
Topic: Configuring AdvancedDisk
After completing this topic, you will be able to configure storage servers,
AdvancedDisk disk pools, and AdvancedDisk storage units.
12
After completing this topic, you will be able to configure storage servers, AdvancedDisk
disk pools, and AdvancedDisk storage units.

6-12
AdvancedDisk disk pools and storage units
Storage servers Media NetBackup
servers appliance
Disk M1 M2 5340-1
enclosures
Internal
storage
Disk pool: M1_SANdp Disk pool: M2_INTdp Disk pool: 5340-1_advdp

Storage unit: M1_SANstu STU: M2_INTstu STU: 5340-1_advdisk_stu
Veritas recommends pooling disks with similar characteristics
13
An AdvancedDisk disk pool enables several disk volumes to be combined into one
logical storage destination in NetBackup. The pool is accessed by a single storage server,
which must also be a NetBackup media server. These disk volumes may exist across
multiple physical disk arrays or internal storage disk volumes on a storage server.
Generally, pooling disks from a server into a single pool is a good idea, however, Veritas
recommends placing disks of significantly different sizes or speeds into separate pools.
Even though high-performing SAN disks and slower drives could go into the same pool,
separating them into separate disk pools allows for predictable performance behavior.
An AdvancedDisk storage unit must be configured to target a single disk pool, and it
cannot specify individual disk volumes in a pool. However, more than one storage unit
can be configured for a single disk pool. This may be performed to allow higher priority
policies to have additional concurrent write streams.
NetBackup assumes exclusive control of all disk volumes configured within a disk pool,
enabling NetBackup to manage and report disk capacity accurately. A disk volume
cannot exist in more than one disk pool.
If NetBackup is unable to write an image to a single disk volume in a disk pool, the
backup spans to the next available disk volume. Spanning can occur from any volume to
any other volume in that disk pool. It is not possible for a single backup image to span
multiple disk pools, even if the disk pools exist in a storage unit group.

6-13
AdvancedDisk configuration overview
Step Description Administration Console method
Determine whether an AdvancedDisk storage server is

1 already configured
2 Create a new storage server, if necessary
3 Create a new disk pool
4 Configure one or more storage units for the disk pool
14
The slide on this page provides an overview of the steps involved to configure a usable
disk pool and corresponding AdvancedDisk storage server.
1. First, determine whether or not the target media server is already configured as an
AdvancedDisk storage server. This process only needs to be performed once per
media server, regardless of the number of AdvancedDisk storage pools hosted on
the media server.
2. Run the Configure a Disk Storage Server wizard if the host needs to be configured as
a storage server, or in other words, if this is the first time the host is being
configured for AdvancedDisk storage.

3. If this host is already a storage server, run the Configure Disk Pool wizard to create a
new disk pool. Note that the storage server wizard will automatically start the disk
pool wizard for you after you configure a new AdvancedDisk storage server.
4. Finally, configure one or more storage units for the disk pool. Both the storage
server and disk pool wizards will allow you to create the storage unit as part of those
wizards, but this can also be performed manually in the NetBackup Administration
Console or using NetBackup commands.
You will learn how to perform each of these steps, in more detail, on the following
pages.

6-14
Storage Server Configuration Wizard: Selecting AdvancedDisk
storage type
nbdevconfig –creatests
15
Before you can create an AdvancedDisk pool, you must configure an AdvancedDisk
storage server. To do this, use the Storage Server Configuration Wizard.
You can also use the nbdevconfig -creatests command to create a storage
server from the command line. The nbdevconfig command and syntax is discussed
in the NetBackup Commands Reference Guide. The nbdevconfig command is found
in the following directory:
• UNIX: /usr/openv/netbackup/bin/admincmd
• Windows: install_path\bin\admincmd
The Disk Pool Configuration Wizard can be started by clicking on Configure Disk Pool,
however this requires that the media server has already been configured as a storage
server first.
The first screen of the Storage Server Configuration Wizard has you select the disk
type. Select AdvancedDisk and click Next.

6-15
Storage Server Configuration Wizard: Adding the storage server
Each media server will only need to be

configured once as an AdvancedDisk
storage server (even if multiple disk
pools are created).
16
On the next screen you need to select the media server you are configuring as the
storage server. Each media server will only need to be configured once as an
AdvancedDisk storage server, even if multiple disk pools are created for that storage
server.

6-16
Storage Server Configuration Wizard: Performing tasks and
starting the disk pool configuration wizard
By default, completing the wizard will then

start the disk pool configuration wizard.
17
The Storage Server Configuration Status will then show if the storage server is
configured successfully.
By default the wizard will then go on to help you create a disk pool for that storage
server. You can alternatively close the wizard without this checkbox, and run the disk
pool configuration wizard manually, at a later time.

6-17
Disk Pool Configuration Wizard: Volume selection
The entire volume is used for

AdvancedDisk (no directory
can be specified)
nbdevconfig –createdp
18
The Disk Pool Configuration Wizard is automatically started, by default, when you click
Next at the end of the Storage Server Configuration Wizard.
To create a disk pool outside of the wizard, from the NetBackup Administration Console,
expand Media and Device Management > Devices. Right-click Disk Pools and select
New Disk Pool. The Disk Pool Configuration Wizard is displayed. You may also access
the Disk Pool Configuration Wizard by clicking the master server in the Administration
Console.
You may also use the nbdevconfig command to configure a new disk pool from the
command line.
No disk pools exist by default.
Select the disk volumes to be included in the disk pool. A disk volume must be
formatted and mounted within the operating system before it can be selected for an
AdvancedDisk storage unit. Do not select disk volumes that have already been
configured in another pool.
Note that the entire disk volume will be used by the AdvancedDisk pool, and that no
directory or folder can be specified in the configuration.

6-18
Disk Pool Configuration Wizard: Additional disk pool information
Does not work correctly if the volume file

system is shared with other applications
• Limit I/O streams to manage performance

(default = no limit).
• Alternatively, set the maximum concurrent
jobs at the storage unit.
19
Assign a name to the pool and optionally add comments about its function. Configure
additional disk pool information as follows:
• High water mark: The percentage of used capacity at which NetBackup considers a
disk volume in the pool to be full.
A disk volume within a disk pool is assigned fewer backup jobs as it approaches the
high water mark.
• Low water mark: The percentage of used capacity at which a clean-up operation
stops purging backup images as a result of the disk pool reaching the high water
mark
• Maximum I/O Streams: Limits the number of streams that can be directed to a disk
simultaneously. It is used to avoid disk thrashing, which is the result of too many
jobs writing to the same disk simultaneously.
The default is that there is no limit, at the disk pool, however there are limits that
are enforced at the storage unit. A storage unit supports up to 4096 streams, with a
default of 1 concurrent job running. However, because you can setup multiple
storage units for one disk pool, this value allows you to control the maximum I/O
streams to the disk pool, regardless of any storage unit limits.
For more information on these properties, click on the Help button in the Wizard.

6-19
Disk Pool Configuration Wizard: Configuration status and initiating
storage unit creation
By default, completing the disk pool wizard

will go to the storage unit creation dialog.
20
The Disk Pool Configuration Status will then show if the disk pool is configured
successfully.
By default the wizard will then go on to help you create a storage unit for that disk pool.
You can alternatively close the wizard without this checkbox, and create a storage unit
manually in the NetBackup Administration Console.

6-20
Disk Pool Configuration Wizard: Storage unit creation
• In most cases, increase the maximum

concurrent jobs from the default of 1
• Consider increasing this further as you
gauge actual disk performance
bpstuadd
21
Next, configure the properties of the storage unit for this disk pool.
A Media Server option is available to limit the storage unit to specific media servers.
In most cases, you must increase the Maximum concurrent jobs setting from the
default setting of 1. For example, on the slide we have changed the maximum
concurrent jobs to 3, to correspond to the number of jobs that the three separate disk
volumes (G:\, H:\, and I:\) in this pool should be able to concurrently run without issue.
The Maximum fragment size setting normally does not need to be changed. Changing
this value may impact backup and restore times, and should be tested if any changes
are made.
If you chose to configure the storage unit, no additional configuration is required. The
storage unit created for the disk pool may now be selected as a destination within a
backup policy.
The disk pool configuration is complete.

6-21
Verifying AdvancedDisk storage server information
nbdevquery -liststs
22
After a storage server has been configured, it may be viewed in the NetBackup
Administration Console by expanding Media and Device Management > Credentials >
Storage Servers. Notice that the Administration Console does not list BasicDisk storage
servers because all media servers support BasicDisk by default.

6-22
Verifying and modifying AdvancedDisk disk pools
nbdevquery -listdp
nbdevconfig
23
To view disk pools using the NetBackup Administration Console, expand Media and
Device Management > Devices and select Disk Pools to list all configured disk pools.
The columns display the general configuration for the storage unit, in addition to a
percentage full value, showing the total used capacity of the disk pool.
Right-click the disk pool and select Change to modify disk pool settings, such as water
marks, and limiting the number of I/O streams.

6-23
Verifying and modifying AdvancedDisk storage units
bpstulist
24
After an AdvancedDisk storage unit has been configured, it can be viewed in the
NetBackup Administration Console by expanding NetBackup Management > Storage
and selecting Storage Units. Notice that the master_advdisk_pool_stu AdvancedDisk
storage unit is displayed with a Storage Unit Type of Disk.
Right-click and select Change to modify storage unit settings, such as maximum
concurrent jobs.

6-24
Topic: Managing AdvancedDisk storage
After completing this topic, you will be able to monitor and report on
configured AdvancedDisk disk pool devices, as well as perform common
AdvancedDisk management tasks.
25
After completing this topic, you will be able to monitor and report on configured
AdvancedDisk disk pool devices, as well as perform common AdvancedDisk
management tasks.

6-25
AdvancedDisk and NetBackup licenses
bpminlicense
Article 100024025: NetBackup Traditional and
nbdeployutil Capacity License Deployment Utility (nbdeployutil)
26
Many licensed options in NetBackup are capacity-based; this means that these options
license a specific amount of data storage of a particular type. The Flexible Disk Option,
which tracks space usage for AdvancedDisk pools, is capacity-based.
Access the NetBackup License Keys dialog box, select Help > License Keys, and
determine if you have the Flexible Disk Option.
Capacity-based licensing applies only to the used capacity (active backup images),
rather than the total capacity of the storage units or disk pools.
To report on the actual disk space usage and NetBackup capacity compliance, you will
need to run the nbdeployutil command. For assistance, refer to Article 100004107:
Late Breaking News for the Capacity Licensing Utility (nbdeployutil), found online at
http://www.veritas.com/docs/100004107 and Article 100024025: NetBackup
Traditional and Capacity License Deployment Utility (nbdeployutil), found online at

6-26
Understanding disk volume selection and capacity management in
disk pools
Disk volume selection Capacity management
• Estimates backup size based on prior backup + 20%
• Uses disk volume with most free space
• Uses disk spanning, if no volumes meet estimated
size criteria Disk volume
• Reserves space for the job on selected disk volumes Free
space
High water Potential

mark: 90%
15 GB 35 GB free
free free space
Low water
Disk pool mark: 65%
Used
25 GB 80 GB
free
✓
free
space
27
For backups targeting a disk pool, NetBackup estimates the size of a backup before
selecting a backup destination. The estimate is based on the size of the most recent
similar backup using the policy, schedule, client, and stream (the file list for a specific
job) as criteria. NetBackup adds 20 percent to this size, and it seeks an appropriate
storage destination.
The disk volume in the disk pool with the most free space is used. If the disk does not
have enough space to store the entire image, the job still runs, and the backup image
will span across multiple disk volumes in that disk pool.
After a disk volume is selected, the estimated backup size is reserved on the selected
volume within NetBackup. If new backup jobs are initiated while all disk space is
reserved, the new backup jobs queue until the reserving jobs complete.
A disk pool is configured with high and low water mark values, affecting both the pool
as a whole and its individual disk volumes. At the disk volume level, when the used
capacity percentage exceeds the high water mark value, jobs are no longer assigned to
that disk volume. NetBackup considers a pool to be full when all of its disk volumes
have reached the high water mark value.
When a disk volume contains staged backup images (from a Storage Lifecycle Policy),
the images are considered potential free space if they have already been duplicated.
This is discussed in further detail in the Duplicating Backups lesson. Images that are
staged, but not yet duplicated, are considered used space.

6-27
AdvancedDisk disk pools and disk volume status
Disk pool Disk pool Disk pool
Disk volume 1 UP Disk volume 1 DOWN Disk volume 1 UP|DOWN

Disk volume 2 UP Disk volume 2 UP Disk volume 2 UP|DOWN
Disk volume 3 UP Disk volume 3 UP Disk volume 3 UP|DOWN
Disk pool UP Disk pool UP Disk pool DOWN
Backup jobs should run; Jobs return status 2073:

restore jobs may fail Disk pool is down
28
NetBackup tracks status information for all disk volumes in a disk pool, and a status for
the disk pool itself. When everything is working properly, the disk volumes will be in an
UP state, and the disk pool will also be in an UP state.
If there is a problem with one disk volume, it will be put into a DOWN state. This can
also be performed manually by the administrator in the case of disk volume
maintenance. The disk pool can still be in a usable UP state as long as there are other,
available disk volumes. Backups jobs should run normally, as long as there is available
space, however restore jobs that use those specific DOWN volumes will fail.
If the entire disk pool becomes unavailable it will be in the DOWN state. This can also be
performed manually by the administrator in the case of disk pool maintenance. In this
case the state of the disk volume is irrelevant, and any backup or restore jobs using this
disk pool will return with a status 2073: Disk pool is down. Note that if the disk pool is
brought down manually by an administrator (for maintenance for example), the disk
volumes will normally still appear in the UP state, despite the fact that they cannot be
accessed for backups.

6-28
Monitoring and managing disk pool state
• To change the status of a disk pool, enter:

nbdevconfig –changestate –dp dpname
–state [UP|DOWN|RESET]
• To change the status of a disk volume, enter:
nbdevconfig –changestate –dv dvname
29
The state of both disk pools and disk volumes can be set UP or DOWN, which is similar
to the state of a tape device. To change the state of a disk pool using the Administration
Console, right-click the disk pool in the Device Monitor, and select Up Disk Pool or
Down Disk Pool.
You can also use the nbdevconfig command to change the state of disk pools or disk
volumes as follows:
nbdevconfig -changestate
-dp pool_name
-stype storage_type
-state UP|DOWN|RESET
nbdevconfig –changestate
-dp pool_name
–dv disk_volume_name
-stype storage_type
When a disk pool or disk volume is in a DOWN state, NetBackup considers it to be
unavailable to receive new backups. Typically, this feature is used to prevent backups to
a disk pool, or to prevent backups to an individual disk volume in a disk pool during
maintenance.

6-29
Running disk reports on AdvancedDisk storage
bpimmedia –stype AdvancedDisk

bperror –DiskPool
bpstulist
nbdevquery –listdp
nbdevquery –listdv
30
There are a number of disk-based reports in the NetBackup Administration Console.

For example, as shown on the slide, you can use the Disk Pool Status report to view the
status of your disk pools. To access this report, in the Administration Console, select
NetBackup Management > Reports > Disk Reports > Disk Pool Status.
Some of the reports, including the commands that correspond to them, include:
• Images on Disk: Shows which backup images reside on NetBackup disk storage. This
is equivalent to running bpimmedia –stype AdvancedDisk.
• Disk Logs: Shows log messages related to NetBackup disk activity. This is equivalent
to running bperror –DiskPool.
• Disk Storage Unit Status: Shows storage unit information. This is equivalent to
running bpstulist.
• Disk Pool Status: Shows disk pool status, such as whether the disk pool is in an UP or
DOWN state. This is equivalent to running nbdevquery –listdp for disk pool
status and nbdevquery –listdv for disk volume status (which cannot be seen
in the NetBackup Administration Console).

6-30
Understanding media server load balancing storage unit groups
ms1 ms2 ms3
✓
1
Server rank based on CPU,
processes, and memory
2
Fewest number of
NetBackup jobs ms1_advdisk_stu ms2_advdisk_stu ms3_advdisk_stu
LoadBalance_stu_group
3
Least reserved space
4
Least recently used Job
31
When a backup jobs is sent to a storage unit group, NetBackup must decide on which
storage unit to use for that job. Storage unit group methods include Prioritized, Failover,
Round Robin, and Media Server Load Balancing. The first three of these methods were
discussed in the Configuring NetBackup Storage lesson.
Media Server Load Balancing chooses the best available media server based on a
ranking system. NetBackup chooses the server based on various criteria. If two or more
servers share the best available rank, NetBackup continues to apply additional criteria
until one media server remains. The order of examined criteria is:
1. Server rank: Rank categories determined by number of processes running on each

CPU and memory thresholds
2. Fewest number of jobs: The server with the fewest NetBackup jobs scheduled
3. Least reserved space: The server with the least amount of reserved space, based
upon the job size estimation by NetBackup
4. Least recently used: The least recently used storage unit.
For example, of five available media servers in a storage unit group, three have a server
rank of Idle. Of those three, two are running a single job each. Of those two, the server
with the least amount of reserved space is chosen. Alternatively, if only one server had
the best rank, that server is automatically chosen.

6-31
Configuring a storage unit group with media server load balancing
• Indicates that NetBackup select a storage unit

based on a capacity-managed approach,
avoiding sending jobs to busy media servers.
• BasicDisk storage is not supported.
32
When configuring a storage unit group, the Storage unit selection area defines how the
storage units will be selected during a backup:
• Prioritized: Choose the first storage unit in the list that is not busy, down, or out of
media.
• Failover: Choose the first storage unit in the list that is not down or out of media.
• Round Robin: Choose the least recently selected storage unit in the list.
• Media Server Load Balancing: Choose the best available media server based on a
ranking system.
The first three of these methods were discussed in more detail in the Configuring
NetBackup Storage lesson.
Note: Media Server Load Balancing selection supports most storage types including
AdvancedDisk, tape storage, and deduplication storage, but does not support basic disk
storage.

6-32
Disk pool management tasks
Task Procedure
1. Source a new disk volume that is not used by another process or application
Add volumes to
2. Add the disk to the disk pool using the command:
a disk pool
nbdevconfig –adddv
1. Remove any backup images on the disk volume

Remove a
2. Place the disk pool and volume in a DOWN state.
volume from a
3. Delete the disk volume using the command:
disk pool
nbdevconfig –deletedv
1. Remove all backup images in the pool.

Remove a disk 2. Remove any storage units targeting the pool.
pool 3. Delete the disk pool using the NetBackup Administration Console or the command:
nbdevconfig –deletedp
33
The slide mentions some other disk pool management tasks that you may need to
perform, such as adding volumes to a disk pool, removing volumes, or removing the
entire disk pool.
To add a volume to an existing disk pool, simply source an empty disk volumes (ensuring
it isn’t used by any other process or application), and use the command shown on the
slide to add it to the disk pool. Prior to NetBackup 7.5, an option to add disk volumes
did not exist. Instead, a procedure to create and merge disk pools was required. Refer to
the documentation for your version of NetBackup for details.
Alternatively, you can increase the storage space in a disk pool by resizing the existing
disk volumes. NetBackup will recognize the additional storage the next time the disks
are scanned by the NetBackup processes. You can manually cause NetBackup to
reexamine the storage by running an Inventory Disk Pool in the NetBackup
Administration Console, or with the nbdevconfig –inventorydp command.
Removing disk volumes can be performed as long as no current NetBackup backup
images exist on the disk volumes, and the disk pool and disk volume are in a DOWN
state and not in use. In addition, before you remove a disk pool, you must remove all
associated storage units.
To delete an entire disk pool, you must remove all active backup images, and all
associated storage units.

6-33
Reporting on disks summary

Storage servers Credentials > nbdevquery -liststs
Storage Servers
Disk pools Devices > Disk Pools nbdevquery -listdp –U Monitor > Devices > Disk
Reports > Disk reports > Disk Pools
pool status Reports > Report Templates
> Backups > Disk Pool
Reports
Reports > Report Templates
> Disk Based Data
Protection > Current Disk
Usage
Disk volume status nbdevquery -listdv -U
-stype disk_type
-dp pool_name
-dv volume_name
34
The table on this slide summarizes the advanced disk and disk pool reporting tools using
the NetBackup Administration Console, NetBackup commands, and OpsCenter.

6-34
Lesson summary
• Key points
– You now know what disk-based storage is and how it is used. You can describe disk pools,
AdvancedDisk, and OpenStorage.
– You can now configure and manage storage servers, AdvancedDisk disk pools, and AdvancedDisk
storage units.
– You now know how to monitor the status of configured devices and view reports for configured devices.
– NetBackup System Administrator’s Guide
– NetBackup AdvancedDisk Storage Solutions Guide
– NetBackup OpenStorage Storage Solutions Guide for Disk
– http://sort.veritas.com/netbackup
35

6-35
Lab 6: Configuring Disk Pools
Lab objectives
• Use the NetBackup configuration wizards to…
– Configure an AdvancedDisk Storage Server
– Configure an AdvancedDisk Disk Pool
– Configure an AdvancedDisk Storage Unit
• Configure a policy to write backup images to AdvancedDisk storage
• Use the NetBackup Administration Console to initiate and monitor backup jobs that
write backup images to AdvancedDisk storage
• Use the NetBackup Administration Console and command line interfaces to…
– View AdvancedDisk storage servers, disk pools, and storage units
– View and manage disk pool states
– Run disk reports for AdvancedDisk storage

6-36
What did you learn?
lesson.
37
current lesson.

6-37
Question: What is a disk volume?
A disk volume is a ________________.
A. Logical unit of disk storage

B. Collection of media in a volume
C. Pool of volumes
D. DataStore pool
38

6-38
Answer: What is a disk volume?
A disk volume is a ________________.
A. Logical unit of disk storage

B. Collection of media in a volume
C. Pool of volumes
D. DataStore pool
39

6-39
Question: What is a disk pool?
A disk pool is a ___________________.
A. Disk enclosure
B. Logical grouping of media servers
C. Collection of disk volumes presented as a single entity
40

6-40
Answer: What is a disk pool?
A disk pool is a ___________________.
A. Disk enclosure
B. Logical grouping of media servers
C. Collection of disk volumes presented as a single entity
The correct answer is C.
41

6-41
Question: NetBackup appliances and storage servers
In the case of a NetBackup appliance, which of the following is true of the storage
server?
A. It is the NetBackup appliance.

B. It must be a separate NetBackup media server.
C. It must be the NetBackup master server.
D. It is the system with the NetBackup plug-in installed.
42

6-42
Answer: NetBackup appliances and storage servers
In the case of a NetBackup appliance, which of the following is true of the storage
server?
A. It is the NetBackup appliance.

B. It must be a separate NetBackup media server.
C. It must be the NetBackup master server.
D. It is the system with the NetBackup plug-in installed.
43

6-43
End of presentation
6-44
Lesson 7: Configuring Media Server Deduplication
This is the “Configuring Media Server Deduplication” lesson in the “Veritas NetBackup
8.1: Administration” course.

7-1
Policies
This lesson is the seventh lesson in this course.


7-2
Lesson objectives
Topic Objective
Introduction to NetBackup
Describe what NetBackup deduplication is and how it works.
deduplication
Configuring NetBackup media server Configure a media server for deduplication, including creating a
deduplication media server deduplication disk pool
Configuring client-side deduplication Configure client-side deduplication.
Managing NetBackup deduplication Monitor the results of deduplication.

7-3
Topic: Introduction to NetBackup deduplication
After completing this topic, you will be able to describe what NetBackup
deduplication is and how it works.
After completing this topic, you will be able to describe what NetBackup deduplication
is and how it works.

7-4
Deduplication overview
What is • Using a hash (fingerprint) to determine data uniqueness

deduplication • Storing only unique data
• Backups: Ideal due to the redundant nature of backup data

Where to
deduplicate
• During backup at the target (media servers and appliances)
• During backup at the source (clients)
• Back up faster while storing less data

Benefits
• Dramatically reduced storage costs and backup load
Deduplication is the elimination of redundant data from storage. Deduplication uses a

hash algorithm to provide a set of data with a unique identifier. This algorithm provides
the ability to prevent the data from being stored multiple times, while still allowing the
data to be restored when necessary. The term single-instance storage (SIS) or intelligent
compression, is sometimes used to describe behavior by some applications to reduce
storage use, which uses similar concepts.
Backups are an ideal candidate for deduplication due to the redundant nature of backup
data. For example, in many environments, most of the data backed up during a full
backup, which normally goes to tape or disk, is identical to that of the previous backups.
In addition to the storage savings that come with only storing unique data, which are
significant, time and other resources are saved. Although many vendors and solutions
provide the ability to deduplicate at the target, usually at the backup storage location or
appliance, being able to deduplicate at the source (the clients) provides the ability to
significantly reduce bandwidth use, and also speeds up the entire backup process. This
is especially true when backing up clients over a WAN or slow connection.

7-5
How NetBackup deduplication works
For all files requiring processing:
1. Separate file metadata and contents. Backup storage:
2. Logically separate file into segments. Metadata
File1
3. Take hash fingerprint of segments. File1|920KB|2010/02/06…
4. Store all unique segments. File2

File2|983KB|2010/02/07…
5. Process the next file.
File1 4 Content
2
Metadata
File1 1
File Content A B C D A B C D E F
Data to
3 File2
back up:
Metadata
File2
File Content A E C F
5
Similar to normal backups, the first step is to determine which data needs to be backed
up. After a list of files that require processing has been established, the following high-
level procedure is used for the files:
1. The file metadata, including file permissions, directory location, file name, and so
on, is separated from the actual content of the file. The file metadata is stored by
NetBackup.
2. The file contents are logically separated into 128K segments. For file less than 128K
in size, or for the last segment of a large file, the segment is smaller than 128K.
3. An SHA256 fingerprint is created for each segment, which is used to uniquely

identify the segment. Prior to NetBackup 8.1, an enhanced MD5 fingerprint was
used.
4. If a segment has not been previously recorded, that segment is stored in the
deduplication storage area. If a file has not been previously recorded, a new file
pointer, which points to all the data segments that comprise that file’s contents, is
created.
5. Additional files are processed similarly.
In the example on this slide, File2 has two unique segments: E and F. File2 also has
some segments that were previously backed up.

7-6
NetBackup deduplication options
Media Server Deduplication Pool (MSDP) on a media server
• A disk pool using proprietary NetBackup deduplication technology.
• Installed on a NetBackup media server.
MSDP on a NetBackup Appliance

• A high-capacity disk pool using proprietary NetBackup deduplication technology.
• Installed on a NetBackup media server with specialized hardware.
Client-side deduplication
• Combined with MSDP, distributes deduplication work to the client.
• Reduces network bandwidth and enables higher parallelization.
Third-party appliance supporting OpenStorage Technology (OST)

• Appliance vendor supporting OpenStorage Technology (OST).
• Managed as a NetBackup storage destination.
NetBackup supports a number of integrated deduplication solutions.

• Media Server Deduplication Pools (MSDP) on a media server: A NetBackup media
server and disk subsystem that meets the system and storage requirements can
easily be made to contain a MSDP. This provides a built-in method for NetBackup to
support deduplication. Prior to NetBackup 7.5, the limit of an MSDP was 32 TB. In
NetBackup 7.5, that limit was changed to 64 TB. In NetBackup 7.6.1 that limit
increased to 96 TB on SUSE Linux. In NetBackup 7.7.1 that limit increased to 96 TB
on Red Hat Linux. This is the primary method explored in this lesson.
• MSDP on a NetBackup Appliance: NetBackup 52xx and 53xx appliances are easy-to-
configure media servers that can also perform deduplication. NetBackup appliances
use dedicated hardware and software to optimize performance, and therefore also
support higher capacities of deduplication pools, in excess of 600 TB, depending on
the model used. The deduplication used in NetBackup appliances is also MSDP, the
same technology as discussed in this lesson.
• NetBackup client-side deduplication: Deduplicating at the source, often known as
client-side deduplication or client deduplication, is supported with NetBackup. This
feature is discussed elsewhere in this lesson.
• Third-party appliances supporting OpenStorage Technology (OST): Third-party
deduplication appliance vendors that support OpenStorage Technology (OST) can
also be managed as a NetBackup storage destination.

7-7
Comparing media server and client side deduplication
Media server Using load Full data stream
deduplication balancing Deduplication plug-in
Deduplication stream
NetBackup Deduplication engine
clients
Load Client-side
balancing deduplication
media
MSDP server
NetBackup
storage
clients
server
MSDP
storage
8
When deduplicating data, fingerprinting – the process of identifying unique data –

requires heavy CPU processing and memory use. To mitigate this and distribute the load
among servers, use a number of basic configuration:
• Media sever deduplication: The default behavior is that the client sends the backup
data stream over the network to the media server (requiring bandwidth use), while
the deduplication storage server performs the fingerprinting. The storage server then
only stores unique data in the MSDP storage.
• Using load balancing: To distribute the load required of the MSDP storage server,
configure and use MSDP load balancing servers. These NetBackup media servers do
not need to be configured as storage servers, but instead get the full stream of data
from the client, and perform the fingerprinting work before sending unique data to
the storage server. Minor bandwidth use is required for storage and media server
communication during this process.
• Client-side deduplication: Using this method means that the client performs the
fingerprinting and communicates with the deduplication storage server as to whether
the data is unique or has been stored previously. If the data is unique, the data is sent
over the network to the media server for storage. Minimal network bandwidth is
required.

7-8
NetBackup MSDP components
Legend
Backup data
Full data stream
Deduplicated data stream
Deduplication Catalog metadata
plug-in
Deduplication Deduplication
engine (spoold) manager (spad)
For the best performance,

configure separate storage
Storage path Database path and database disks.
Media server deduplication pool
This slide discusses some NetBackup MSDP components:

• Deduplication plug-in
The deduplication plug-in is the data interface to the NetBackup deduplication
engine on the storage server. The plug-in is responsible for separating the file’s
metadata from the file’s content, deduplicating the content (separating files into
segments), and controlling the data stream from NetBackup to the NetBackup
deduplication engine and vice versa. The plug-in runs on the deduplication storage
server. The plug-in also runs on load balancing servers and on the clients that
deduplicate their own data.

• Deduplication engine
The deduplication engine is one of the storage server core components. It stores
and manages deduplicated file data. The binary file name is spoold, which is an
abbreviation for storage pool daemon (Do not confuse it with a print spooler
daemon.) The spoold process is displayed as the NetBackup Deduplication Engine
in the NetBackup Administration Console.
• Deduplication manager
The Deduplication manager is one of the storage server core components. The
deduplication manager maintains the configuration and controls internal processes,
optimized duplication, security, and event escalation.

7-9
The deduplication manager binary file name is spad, which is an abbreviation for
storage pool authority daemon. The spad process is displayed as the NetBackup
Deduplication Manager in the NetBackup Administration Console.
• Deduplication database
The deduplication database stores and manages the metadata of deduplicated files.
The metadata includes a unique fingerprint that identifies the file’s content. The
metadata also includes information about the file, such as its owner, where it
resides on a client, when it was created, and other information.
The deduplication database is separate from the NetBackup catalog. The NetBackup
catalog maintains the usual NetBackup backup image information.
• Media server deduplication pool
Prior to NetBackup 7.5, the maximum deduplication storage was 32 TB and
NetBackup reserved 10 percent of the storage space for the deduplication database
and transaction logs.
Starting in NetBackup 7.5, the maximum deduplication storage capacity is increased
to 64 TB and NetBackup reserves 4 percent of the storage space for the
deduplication database and transaction logs. Therefore, a storage full condition is
triggered at a 96 percent threshold.
Starting in NetBackup 7.6.1 the limit increased to 96 TB on SUSE Linux, and in
NetBackup 7.7.1 the limit increased to 96 TB on Red Hat Linux.
• Storage path: The directory in which NetBackup stores the raw backup data.
• Database path: The directory in which NetBackup stores and maintains the
structure of the stored deduplicated data.
For performance optimization, Veritas recommends that you use a separate disk,
volume, partition, or spindle for the deduplication database.

7-10
Deduplication stream handlers
• Enable NetBackup to see the layout of data objects and files

• Align data to achieve better deduplication rates
• Exist for the following data types:
– File system backups Data stream without a stream handler:
– Windows System State
– Microsoft Hyper-V
– VMware vSphere
– NetApp NDMP
– EMC NDMP With a stream
(Celerra and Isilon) handler:
11
NetBackup provides the stream handlers that process various backup data stream types.
Stream handlers improve backup deduplication rates by processing the underlying data
stream.
For data that has already been deduplicated, the first backup with a new stream handler
produces a lower deduplication rate. After that first backup, the deduplication rate
should surpass the rate from before the new stream handler was used.

7-11
Deduplication and firewall configuration
• Non-deduplicating clients do not require configuration. Legend

Full data stream
• Open ports 10082 and 10102 between:
Deduplicated data
1. Media servers in the same MSDP stream
2. Optimized duplication targets
3. Client-side deduplication sources
Client-side
deduplication
3
Clients
1 Deduplication 2 Remote
Media Server
Deduplication
Pool
Load Balancing
Server
12
NetBackup deduplication components require the IP ports 10082 (spoold, the

Deduplication Engine) and 10102 (spad, the Deduplication Manager) to be opened
between specific servers in your environment, in addition to other NetBackup specific
ports, such as Private Branch Exchange (PBX).
Ports 10082 and 10102 need to be opened between the media servers and any
deduplicating targets. Deduplicating targets include remote deduplication pools (used
for replication and optimized duplication), load-balancing media servers, and hosts
using client-side deduplication. Standard NetBackup clients that do not deduplicate
their own data do not need to access these ports, and only need the standard
NetBackup ports to be open.

7-12
Deduplication planning
Use cases Recommended deduplication type
• Remote office backups

• Client-side deduplication
• LAN connected file servers
• Load balancing media servers
• Virtual machine backups (a client in a VM)
• Heavily-loaded client systems or database servers

• Media server (server-side) deduplication
• Clientless virtual machine backups
• Load balancing media servers
• NDMP devices
Deduplication appliance already deployed NetBackup OpenStorage Option
For details refer to the NetBackup Deduplication Guide
13
• NetBackup client-side deduplication: Client-side deduplication is optionally used

with media server deduplication, to provide deduplication at the source, which helps
distribute deduplication overhead. Although this works to increase the total number
of clients that can run backups concurrently, and therefore decrease backup
windows, it also means the client is working harder during the backup. This works
very well for remote offices without backup infrastructure, and local clients that
don’t have high CPU overhead, like many file servers.
• NetBackup Media Server Deduplication Option: By default, deduplication is
performed at the target, the deduplication media server. The deduplication server’s
CPU becomes the limiting factor of how many concurrent jobs can run. The CPU of
the client is only minimally impacted by a backup.
• Load balancing media servers: By using load balancing media servers you can also
increase the overall bandwidth. This option is great for storage servers that are
reaching CPU capacity, and in environments where you don’t want to use, or can’t
use, the NetBackup client-side deduplication feature. This prevents impacting CPU
on some heavily loaded application servers, while still distributing deduplication load.
• NetBackup OpenStorage Option: If you already have deduplication appliances
deployed in your environment, this option allows NetBackup to use and manage
them within the NetBackup infrastructure.

7-13
Topic: Configuring NetBackup media server
deduplication
After completing this topic, you will be able to configure a media server for
deduplication, including creating a media server deduplication disk pool.
After completing this topic, you will be able to configure a media server for
deduplication, including creating a media server deduplication disk pool.

7-14
Configuring a deduplication media server
1. Verify the MSDP requirements

2. Confirm that the license key is present
3. Install the NetBackup media server software (if it is not already installed)
4. Configure the media server as a deduplication storage server
5. Create a media server deduplication disk pool
For greater details see the Planning your MSDP deployment

section of the NetBackup Deduplication Guide
15
The slide provides an overview of the steps to configure a deduplication media server.
You learn how to perform each of these steps in the following slides.
The NetBackup Deduplication Guide provides much greater details around planning and
configuring the media server deduplication pool. Some of those steps includes
understanding and putting in place optimizations that are discussed elsewhere in this
lesson (such as fingerprint cache behavior) and in the Managing and Protecting the
NetBackup Catalog lesson (such as MSDP catalog protection).

7-15
Verifying MSDP requirements
• Review summary of MSDP server minimum requirements:
Component Storage server Load balancing server
CPU 2.2-GHz, 64-bit, 4 core* 2.2-GHz, 64-bit, 2 core
RAM 8-32GB, or more (1 GB per 1 TB storage) 4 GB
Disk 130-250 MB/s**, 0.1ms latency max N/A
O/S Must be a supported 64-bit operating system
• For details, review:

– NetBackup Deduplication Guide: Planning your MSDP deployment section
– NetBackup compatibility at http://www.netbackup.com/compatibility
• Do not combine a master server with MSDP, except in smaller environments
Such environments typically run fewer than 100 total backup jobs a day.
* 8 core recommended (8 cores required for 64TBs of storage on x86-64)

** 200 MB/s minimum recommended
16
To create a deduplication media server, you need to consider server and storage
prerequisites. Because fingerprinting is process-intensive, the most important factor in
deduplication performance is CPU, followed by memory size and speed, and storage
speeds.
The storage server CPU and memory constrain how many jobs can run concurrently. The
storage server requires enough capability for deduplication and for storage
management. Reducing CPU use on the storage server is possible with load balancing
servers and client deduplication.
Processors for deduplication should have a high clock rate and high floating point
performance. Furthermore, high throughput per core is desirable. Each backup stream
uses a separate core. Intel and AMD have similar performance and perform well on
single core throughput.
For greater details see the Planning your MSDP deployment section of the NetBackup
Deduplication Guide.
Note: Veritas recommends that you do not use the master server as a deduplication
storage server. Master server activity and media server deduplication activity on the
same host degrades performance. In some environments, a single host can function as
both a NetBackup master server and as a deduplication server. Such environments
typically run fewer than 100 total backup jobs a day.

7-16
Deduplication licensing
• Priced according to front-end TB capacity, not back-end TB

– Size of client’s data (data source)
– Not storage needed for all the client’s backups (destination)
• Covers all forms of NetBackup deduplication, on:
– The client
– The media server
– NetBackup appliances
17
In NetBackup, deduplication is licensed according to the front-end storage capacity, not

the back-end storage size. In other words, the price is determined by the amount of
source data that is actually being backed up, not the capacity of what would be needed
if all source data were deduplicated (the size of the deduplication disk pool). This
licensing covers all forms of deduplication within NetBackup: media server
deduplication and client-side deduplication.

7-17
Initiating the Storage Server Configuration Wizard
18
The next step in activating and configuring media server deduplication is to create a
deduplication media server with a media server deduplication pool. Use the Storage
Server Configuration Wizard to do this. Veritas recommends using this wizard to create
this pool. There is also a command line method that can be used, but it is not
recommended unless your MSDP will be more than 64TB. See the NetBackup
Deduplication Guide for details.
Because it is difficult to reconfigure the media server deduplication pool after it has
been created, and after backups have been written to it, it is extremely important to
initially set configuration settings correctly.

The wizard steps you through the following three separate phases:
1. Storage server configuration
2. Disk pool configuration
3. Storage unit configuration
A storage server is a NetBackup media server that mounts, reads and writes data from
disk storage. Configuration of a deduplication storage server follows the same paradigm
as configuration of all other disk storage server types. The step where the storage server
is created is where you decide and configure the physical location of the storage to be
used. You may use only a single path to the disk storage and the disk storage must be
used exclusively by NetBackup.

7-18
Storage Server Configuration Wizard: Selecting Media Server
Deduplication Pool storage type
19
The Welcome screen is the first screen of the Storage Server Configuration Wizard. The
screen reminds you to ensure that you have physically deployed all storage devices prior
to starting this setup. It also reminds you to ensure that all software plug-ins are
installed on the media servers that will be communicating with the storage server. The
media server deduplication plug-ins are installed automatically by the NetBackup
installation.
The first screen of the Storage Server Configuration Wizard has you select the disk
type. Select Media Server Deduplication Pool and click Next.

7-19
Storage Server Configuration Wizard: Adding storage server
• Specific to the deduplication media server

• Not related to the operating system
• Used by the storage engine to connect to
the deduplication engine
• Must be kept in a secure and accessible
location
• Can be changed by following steps
provided in Article 100038891: How to
reset the NetBackup authentication
password on an MSDP disk pool
20
On the Add Storage Server screen, you select the media server on which to create the
storage server. You also define credentials for the selected media server. These
credentials are specific to the deduplication media server, not the operating system.
These credentials are used by the storage engine to connect to the deduplication
engine. It is important to keep these credentials in a secure and accessible location.
If you need to later change these credentials, this can be performed using the
spauser command (if the password is known) or with some additional commands and
spadb and tpconfig commands. For specific steps on reseting the password, refer
to Technical Article 100038891: How to reset the NetBackup authentication password on

an MSDP disk pool, found online at http://www.veritas.com/docs/100038891.

7-20
Storage Server Configuration Wizard: Specifying the storage path
and network interface
Use alternate paths for storage and

database for best performance
Specify network interface if the server

has a separate backup network
21
Specify the storage path on this dialog box. You may only select one storage path per
media server. You can set two additional parameters on this screen:
• Use alternate path for deduplication database
This refers to the content router index. The content router index decreases the
amount of space available on the storage server on which it is installed. Veritas
recommends moving this database to improve performance.
• Use specific network interface
Mark this check box to specify a network interface on the media server. If the media
server that is being used has multiple interfaces, with one that should be used for
the backup network, this setting forces NetBackup to connect to the deduplication
media server using only the named interface.
Note: On Windows, you must specify a folder within the drive letter, as the wizard will
not let you continue if you only specify a drive letter.
Caution: Do not create the directories on the server prior to specifying them in the
wizard, but instead allow the Storage Server Configuration Wizard to create those
directories to ensure correct permissions are assigned.
Note: Use care when making these selections, as they cannot later by changed. Changes
to the storage server require deleting and recreating the storage server.

7-21
Storage Server Configuration Wizard: Optionally defining
deduplication load balancing
Screen only displayed if

additional media servers are
available for load balancing.
22
The Deduplication Load Balancing screen is only displayed if additional media servers
are available.
When you use additional media servers for deduplication load balancing, the
fingerprinting process is shared between multiple media servers, and the fingerprinting
process is more efficient. The single copy of the deduplication database and indexes
that are created continue to reside on the storage server; using multiple media servers
does not result in multiple indexes.
Clicking Next will bring you to the a screen that displays a summary of the settings that
have been made. Confirm these settings before continuing.

7-22
Storage Server Configuration Wizard: Performing tasks and
starting the disk pool configuration wizard
By default, completing the wizard will then

start the disk pool configuration wizard.
23
This screen displays the progress as the storage server is created. During this time, the
Next button is disabled. After the process completes, the Next button is enabled.
By default, there is a checkbox enabled stating Create a disk pool using the storage
server that you have created. By clicking Next you start the Disk Pool Configuration
Wizard.

7-23
Disk Pool Configuration Wizard: Volume selection
24
The next step in creating the media server deduplication pool is to create a disk pool. If
you run the Disk Pool Configuration Wizard separately from the Storage Server
Configuration Wizard, you need to select a disk pool type to create of PureDisk.
You may also use the nbdevconfig command to configure a new disk pool from the
command line, however Veritas does not recommend using the command line, and
instead recommends only using the wizard to ensure accuracy during configuration.
On this screen, Select the PureDisk disk volume to be included in the disk pool. There
should be only one disk volume per server, as was configured in the storage server
wizard when previously prompted for the storage path.

7-24
Disk Pool Configuration Wizard: Additional disk pool information
Limit I/O streams to manage

performance (default = unlimited)
25
In the Additional Disk Pool Information screen, configure the properties of the disk
pool. Assign a name to the pool and optionally add comments about its function.
Configure additional disk pool information as follows:
• High water mark: The percentage of used capacity at which NetBackup considers a
disk volume in the pool to be full. A disk volume pool within a storage unit group is
assigned fewer backup jobs as it approaches the high water mark.
• Low water mark: For most disk types this is the percentage of used capacity at
which a clean-up operation stops purging backup images as a result of the disk pool
reaching the high water mark. This value is not used for deduplication pools.
• Maximum I/O Streams: Limits the number of streams that can be directed to a disk
simultaneously. It is used to avoid disk thrashing, which is the result of too many
jobs writing to the same disk simultaneously.
Any disk pool limit that you apply here will affect the total number of jobs that
associated storage units would be able to run.
Vertias recommends you place a limit here to prevent the server from being
overloaded with too many simultaneous backup jobs. A common limit to start with
is “20”. From there you can test higher values as you test the hardware’s capacity.

7-25
Disk Pool Configuration Wizard: Configuration status and initiating
storage unit creation
26
The Disk Pool Configuration Status will then show if the disk pool is configured
successfully.
By default the wizard will then go on to help you create a storage unit for that disk pool.
You can alternatively close the wizard without this checkbox, and create a storage unit
manually in the NetBackup Administration Console.

7-26
Disk Pool Configuration Wizard: Storage unit creation
• Start with a low value while initial

deduplication (seeding) occurs
• Increase gradually to process more
jobs concurrently
bpstuadd
27
Finally, configure the properties of the storage unit for this disk pool.
In most cases, you will want to increase the Maximum concurrent jobs setting from the
default setting of 1. Veritas recommends that you increase the Maximum concurrent
jobs value gradually. Doing so provides information about the total deduplication load.
The initial backup jobs (also known as initial seeding) require more CPU and memory
than successive jobs. After initial seeding, the storage server can process more jobs
concurrently. You can then gradually increase the jobs value over time.
Every environment's effective maximum concurrent jobs value is different. To find the
best performance raise or lower this value until best performance is achieved.
A Media Server option is available to limit the storage unit to specific media servers.
After the storage unit configuration is complete, no additional configuration is required.
The storage unit created for the deduplication disk pool may now be selected as a
destination within a backup policy.

7-27
Deduplication processes in the Activity Monitor
28
After a storage server has been configured, the NetBackup media server deduplication
processes are visible in the Running state, under the Activity Monitor Daemons tab. The
two processes that are displayed are the NetBackup deduplication manager (spad) and
the NetBackup deduplication engine (spoold). Prior to MSDP configuration, these
processes should not be found in the Running state.
For more information on the functions of these two processes, see the NetBackup
MSDP components section of this lesson.

7-28
Verifying PureDisk storage server information
nbdevquery -liststs
29
After a storage server has been configured, it may be viewed in the NetBackup
Administration Console by expanding Media and Device Management > Credentials >
Storage Servers. Notice that the Administration Console does not list BasicDisk storage
servers because all media servers support BasicDisk by default.
Note that NetBackup appliances will also be listed as PureDisk storage servers in this
list, and will not look any different than media servers configured with a media server
deduplication pool.

7-29
Verifying and modifying PureDisk disk pools
nbdevquery -listdp
30
To view disk pools using the NetBackup Administration Console, expand Media and
Device Management > Devices and select Disk Pools to list all configured disk pools.
The columns display the general configuration for the storage unit, in addition to a
percentage full value, showing the total used capacity of the disk pool.
Right-click the disk pool and select Change to modify disk pool settings, such as water
marks, and limiting the number of I/O streams.

7-30
Verifying and modifying PureDisk storage units
bpstulist
31
After a PureDisk storage unit has been configured, it can be viewed in the NetBackup
Administration Console by expanding NetBackup Management > Storage and selecting
Storage Units. Notice that the master_msdp_stu storage unit is displayed with a
Storage Unit Type of Disk, and a Disk Type of either PureDisk or Disk Pool.
Right-click and select Change to modify storage unit settings, such as maximum
concurrent jobs.

7-31
Topic: Configuring client-side deduplication
After completing this topic, you will be able to configure client-side

deduplication.
After completing this topic, you will be able to configure client-side deduplication.

7-32
How to configure client-side deduplication
• Prior to configuring client-side deduplication:

– Install the NetBackup client software (if it is not already installed)
– Configure the deduplication storage destination
• To configure client-side deduplication:
– Verify the client-side deduplication requirements.
– Configure client-side deduplication options in the Client Attributes.
33
This slide provides an overview of the steps to configure client-side deduplication. You
have already learned how to configure the NetBackup client software and a
deduplication storage destination, such as MSDP.
To actually configure client-side deduplication, you only need to verify the client-side
deduplication requirements, and configure the option in the Client Attributes. You learn
how to perform each of these steps in this topic.

7-33
Verifying client-side deduplication requirements and
recommendations
CPU
• CPU is impacted on the client during backups.

• Perform tests to ensure the client applications are not unacceptably impacted.
NetBackup version
• At a minimum, NetBackup 7.x must be running on the client.

• No additional installation is required.
Operating system
• 64-bit operating systems are supported.

• 32-bit Windows 2008 server is also supported.
34
Because fingerprinting is very process-intensive, the CPU on the client is affected by the
backup process. Veritas recommends performing tests to ensure that client applications
are not adversely impacted.
For supported operating systems, refer to Operating System Compatibility Lists, found
online at http://www.netbackup.com/compatibility.
Additionally, see the SORT Web site at http://sort.veritas.com/netbackup.


7-34
Controlling client-side deduplication
•Always
Alwaysuseusethe
the mediaDisables client-side
server: Disables deduplication
client-side (default)
deduplication
media server
(default)
•Prefer
Prefertotouse
useclient- If deduplication
client-side deduplication:plug-in is active, use
If deduplication client-side.
plug-in is
side deduplication
active, use client-side. Otherwise,
Otherwise,useuse media
mediaserver
serverdeduplication.
deduplication.
•Always
Alwaysuseuseclient-
client-sideIfdeduplication:
deduplication Ifplug-in
deduplication
is active,plug-in is active,
use client-side.
usededuplication
side client-side. Otherwise, fail andfail
Otherwise, retry
andthe job.the job.
retry
35
To establish a client for client-side deduplication, set up the client in the Client
Attributes on the master server. Begin by adding the client to the list of clients that are
displayed in the dialog box. Next, under the General tab, configure the Deduplication
Location that is to be used:
• Always use the media server
This mode turns client-side deduplication off. Deduplication operations are
performed by the media server. This is the default behavior.
• Prefer to use client-side deduplication

In this mode, the media server determines if the NetBackup client supports client-
side deduplication. If client-side deduplication is supported, it is used. Otherwise,
media server deduplication is used for the backup.
• Always use client-side deduplication
In this mode, the backup manager on the media server determines if the NetBackup
client supports client-side deduplication. If client-side deduplication is supported, it
is used. Otherwise, the backup job fails, and is retried later, depending on your
NetBackup configuration settings.

7-35
Policy attributes to disable client-side deduplication
36
In the NetBackup policy Attribute tab, there is a Disable client-side deduplication policy
attribute. By default, this attribute is disabled.
When you enable this attribute, all backups that are run by this policy use media server
deduplication, regardless of other deduplication settings.
This can be used in a situation where client-side deduplication is configured for some
clients, but should not be used in the case of certain backup policies by those same
clients.

7-36
Topic: Managing NetBackup deduplication
After completing this topic, you will be able to monitor the results of
deduplication in NetBackup.
After completing this topic, you will be able to monitor the results of deduplication in
NetBackup.

7-37
Deduplication rate in the Activity Monitor
By default, the Deduplication Rate column is hidden.
Information about the jobs in this example:

43. Data from winmaster.example.com is sent to an MSDP storage unit for the first time.
46. The same backup occurs to the deduplication disk pool a second time. A small amount
of data has changed between the first and second backups.
47. Backup of data from winmedia.example.com is sent to the deduplication disk pool for
the first time. Even though this is the first backup for winmedia.example.com, because
the data is nearly identical between the two NetBackup clients, deduplication still
occurs.
38
The Deduplication Rate column under the Jobs tab in the Activity Monitor displays the
rate at which deduplication occurs for backups. This Deduplication Rate column is
displayed to the far right, by default, but can moved by rearranging the columns in the
Activity Monitor. This column displays the storage savings that are realized by using
deduplication.
In this example, a backup policy was used that has a storage destination which is a
deduplication pool (master_msdp_stu).
Job 43 was the first backup job for winmaster.example.com using this deduplication
destination. The deduplication rate is 59.4%. Although you may expect a very low
deduplication rate, often times even the initial data may have many duplicate blocks. In
this case we backed up a very large file that contained repeating data, and therefore the
deduplication rate was high for an initial backup.
Job 46 is a second occurrence of the backup performed in Job 43. This time, the
deduplication rate is 99.8% because the same data was written as was written in the
previous job and only a small amount of unique data was found.
Job 47 is the first time that winmedia.example.com was backed up to the deduplication
storage. Even though this is the first backup for this client, because it has almost
identical data to winmaster.example.com, the deduplication rate is very high, at 99.8%.
The results of deduplication are also displayed under the Detailed Status tab of the Job
Details dialog box for a deduplicated backup. The Detailed Status tab includes a line of
text that reflects the details of the backup to the deduplication storage server.

7-38
An example of job details for a standard backup job to a Media Server Deduplication
Pool follows:
01/27/2015 20:56:19 - begin writing
01/27/2015 20:57:13 - Info bpbkar32 (pid=4636) bpbkar waited 2
times for empty buffer, delayed 2 times.
01/27/2015 20:57:13 - Info bptm (pid=5076) waited for full buffer
898 times, delayed 2402 times
01/27/2015 20:57:14 - Info bptm (pid=5076) EXITING with status 0
<----------
01/27/2015 20:57:14 - Info winmaster.example.com (pid=5076)
StorageServer=PureDisk:winmaster.example.com; Report=PDDO Stats
for (winmaster.example.com): scanned: 1026855 KB, CR sent:
416551 KB, CR sent over FC: 0 KB, dedup: 59.4%, cache disabled
01/27/2015 20:57:14 - Info bpbrm (pid=992) validating image for
client winmaster.example.com
01/27/2015 20:57:15 - Info bpbkar32 (pid=4636) done. status: 0:
the requested operation was successfully completed
01/27/2015 20:57:15 - end writing; write time: 0:00:56
the requested operation was successfully completed (0)
Note that the deduplication rate is listed as dedup: 59.4%.


7-39
An example of job details for a client-side deduplication backup follows:
01/27/2015 21:16:07 - Info bptm (pid=6404) using 30 data buffers
01/27/2015 21:16:07 - Info winmaster.example.com (pid=6404) Using
OpenStorage client direct to backup from client
winmedia.example.com to winmaster.example.com
01/27/2015 21:16:19 - begin writing
01/27/2015 21:16:51 - Info bpbkar32 (pid=1288) bpbkar waited 0
times for empty buffer, delayed 0 times.
for (winmaster.example.com): scanned: 825518 KB, CR sent: 1311
KB, CR sent over FC: 0 KB, dedup: 97.6%, cache hits: 17140
(100.0%)
01/27/2015 21:16:51 - Info winmaster.example.com (pid=6404) Using
the media server to write NetBackup data for backup
winmedia.example.com_1422411359 to winmaster.example.com
01/27/2015 21:16:52 - Info bptm (pid=6404) EXITING with status 0
<----------
for (winmaster.example.com): scanned: 1 KB, CR sent: 0 KB, CR
sent over FC: 0 KB, dedup: 100.0%, cache disabled
01/27/2015 21:16:52 - Info bpbrm (pid=564) validating image for
client winmedia.example.com
01/27/2015 21:16:53 - Info bpbkar32 (pid=1288) done. status: 0:
the requested operation was successfully completed
01/27/2015 21:16:53 - end writing; write time: 0:00:34
Notice that there is a line in the job details showing that client-side deduplication is in
use: Using OpenStorage client direct to backup from client.
Shortly after this the backup runs, and the deduplication rate is correctly listed as
dedup: 97.6%. Later in the job details, however, the output a second entry listing
dedup: 100.0%. This entry can be ignored.

7-40
Capacity results in the NetBackup Administration Console
nbdevquery –listdp
Note: Manage storage paths so

that they do not become full. nbdevquery –liststs
41
Within the NetBackup Administration Console, under Media and Device Management,
there are two easy ways to report on deduplication disk pool capacity.
The first method involves looking at the disk pool properties. The command line method
uses the nbdevquery -listdp options. Reporting on the deduplication disk pool
in this manner provides a view of the disk pool capacity because it is cached by the
EMM server.
The second method involves looking at the storage server properties. The command line
method uses the nbdevquery -liststs options. With a deduplication disk pool,
this method lists real-time data, pulled from the storage server when the command is
run.
It is important to understand that reporting and managing space in a deduplication disk
pool may not be as simple as on a non-deduplicating disk. After a single backup image in
a non-deduplicating disk pool expires, the space taken by the backup image is freed. In a
deduplicating disk pool, however, that space may not be so easily reclaimed.

7-41
There are a number of issues to consider:
• The backup image may contain much data that is not unique and that is shared by
other backup images and cannot be freed.
• A NetBackup deduplication disk pool has regularly scheduled jobs, such as queue
processing and garbage collection, which need to run to free space. Some of these
tasks can be run manually. Refer to the NetBackup Deduplication Guide.
• These pools use a storage model based on files called containers. When a data
segment is deleted, it leaves an unused space in these containers, which is either re-
used for new segments or reclaimed during automatically-running container
compaction jobs. Container size depends on the specific MSDP implementation.
Because of these issues, when you use simple disk space reporting tools, such as those
provided by the operating system, you may not be able to accurately determine the
actual available space and capacity of a deduplication disk pool. Instead of using
operating system utilities such as df/du (UNIX) or the Windows explorer utility
(explorer.exe), use the NetBackup-provided commands that more accurately report on
deduplicated disk, as shown on the slide.
To prevent failed jobs or other issues, prevent deduplication disk pools from reaching
their capacity.

7-42
Capacity results in the Disk Pool Status report
43
Within the Administration Console, under NetBackup Management, capacity results are
also displayed in the Disk Pool Status report.

7-43
Deduplication reports in OpsCenter
44
As well as viewing disk pool capacity in OpsCenter, you can also view a variety of
deduplication reports. In Veritas NetBackup OpsCenter 8.1, the following deduplication
reports come with the product:
• Deduplication Rates by Master Server
• Deduplication Rates by Policy Type
• Deduplication Size Savings
• Deduplication Size Factor
• Pre vs. Post Deduplication Size

Refer to the NetBackup OpsCenter Administrator’s Guide for details on these reports.

7-44
Deduplication recommendations
Compression
• Use these features in the deduplication client, not in the NetBackup policy
and • By default: Compression is enabled; Encryption is disabled
encryption
Virtual
machine Use the Enable file recovery from VM backup option for best deduplication rates
backups
Deduplication • Reduces the deduplication client-server communication

cache • May be useful in some environments (a slow WAN)
45
On each NetBackup host that deduplicates data, a pd.conf file contains the various
configuration settings that control the operation of deduplication. The pd.conf file
resides in the following directories:
• UNIX: /usr/openv/lib/ost-plugins/
• Windows: install_path\NetBackup\bin\ost-plugins
Compression and Encryption
NetBackup provides compression and encryption as part of the deduplication process.
The options on the NetBackup policy for these features should not be used because
they can cause performance issues with deduplication backups.
By default, files are compressed as part of deduplication stream. To turn off
compression, add the value COMPRESSION = 0 to the pd.conf file.
By default, deduplication encryption is disabled. To turn on data encryption, add
ENCRYPTION = 0 to the pd.conf file.
The following is the behavior for the encryption that occurs during the deduplication
process:
• If you enable encryption on a client that deduplicates its own data, the client
encrypts the data before it sends it to the storage server. The data remains
encrypted on the storage.
• Data also is transferred from the client over a Secure Sockets Layer (SSL) to the
server regardless of whether or not the data is encrypted, so that the data is
protected, even if data encryption is not used.

7-45
• If you enable encryption on a load balancing server, the load balancing server
encrypts the data. It remains encrypted on storage.
• If you enable encryption on the storage server, the storage server encrypts the data.
It remains encrypted on storage. If the data is already encrypted, the storage server
does not encrypt it.
Prior to NetBackup 8.0, deduplication used the Blowfish 128bit algorithm for
encryption. Starting in NetBackup 8.0, the AES-256-CTR algorithm is used.
Although NetBackup 8.0 uses AES-256-CTR for encryption, encrypted MSDP backups
prior to upgrading to NetBackup 8.0 would still be stored using Blowfish. After
upgrading to NetBackup 8.1, NetBackup automatically performs a rolling upgrade of
these Blowfish-encrypted backups, and converts them to AES-256-CTR-encrypted
backups. This may have an impact on performance. For more information on this
process, refer to the About the rolling data conversion mechanism for MSDP section of
the NetBackup Deduplication Guide.
Virtual machine backups
For VMware backups, select the Enable file recovery from VM backup option when you
configure a VMware backup policy. The Enable file recovery from VM backup option
provides the best deduplication rates.
Deduplication caching
Use of client-side deduplication means the client compares deduplication fingerprints
that it calculates, to the fingerprints in the storage server’s database. Instead of
constantly querying this information back and forth, over a potentially slow wide area
network (WAN), the client can use a deduplication cache of fingerprints for data that
already exists on the storage server.
When subsequent backups are run, fingerprints are checked against this cache first,
before querying the storage server. A high cache hit rate indicates significantly reduced
network communication between the client and storage server, which is important
when using client direct to back up remote clients over high latency networks.
Pre-populating this cache can significantly reduce the data and fingerprint checking that
needs to be performed over the network. Several solutions exist, depending on the
NetBackup release level. For details and configuration options for other NetBackup
releases, see Article 100003816: NetBackup deduplication client WAN backup: how to
seed the fingerprint cache to speed up the initial backup, found online at:

7-46
Lesson summary
• Key points
– In this lesson, you learned what NetBackup deduplication is and how it works.
– You are also learned how to configure a media server for deduplication, including creating a media
server deduplication disk pool, and configuring client-side deduplication.
– Finally, you learned how to monitor the results of deduplication.
– NetBackup Deduplication Guide
– NetBackup compatibility at http://www.netbackup.com/compatibility
– Article 100003816: Seeding fingerprint cache to speed up the initial backup
47

7-47
Lab 7: Configuring Media Server Deduplication
Lab objectives
• Configuring NetBackup Media Server Deduplication
– Configuring the Storage Server
– Configuring the Disk Pool
– Configuring the Storage Unit
• Configuring a policy to use MSDP storage
• Performing backups to MSDP storage
• Configuring and using client-side deduplication
• Monitoring and managing NetBackup MSDP storage
• (Optional) Using OpsCenter to monitor MSDP disk pool capacity

7-48
What did you learn?
lesson.
49
current lesson.

7-49
Question: About NetBackup deduplication
Which statement is false about NetBackup deduplication?
A. Fingerprinting of data can be performed on the server side as well as the client side.
B. Deduplication can be performed at the disk block level.
C. Deduplication uses a capacity-based license.
D. Media server deduplication has only been available since NetBackup 7.5.
50

7-50
Answer: About NetBackup deduplication
Which statement is false about NetBackup deduplication?
A. Fingerprinting of data can be performed on the server side as well as the client side.
B. Deduplication can be performed at the disk block level.
C. Deduplication uses a capacity-based license.
D. Media server deduplication has only been available since NetBackup 7.5.
The correct answer is B. Deduplication can be performed at the file and sub-file (segment) level.
51

7-51
Question: About client-side deduplication
Which statement is true about client-side deduplication?
A. It requires an additional license for each client.

B. It forces the media server to perform the fingerprinting, thereby reducing the
processing work for the client.
C. It may significantly reduce the bandwidth used by backups between the client and
media server.
D. It is not a recommended deduplication option for backing up clients over a wide area
network (WAN).
52

7-52
Answer: About client-side deduplication
Which statement is true about client-side deduplication?
A. It requires an additional license for each client.

B. It forces the media server to perform the fingerprinting, thereby reducing the
processing work for the client.
C. It may significantly reduce the bandwidth used by backups between the client and
media server.
D. It is not a recommended deduplication option for backing up clients over a wide area
network (WAN).
The correct answer is C. Client-side deduplication forces the client to perform the fingerprinting, and enables only
unique data to be transferred to the
deduplication media server.
53

7-53
Question: Load balancing media server
True or False. To create a load balancing media server, you must first configure it as a
storage server.
A. True
B. False
54

7-54
Answer: Load balancing media server
True or False. To create a load balancing media server, you must first configure it as a
storage server.
A. True
B. False
The correct answer is B (False). Because NetBackup media servers already contain the deduplication plug-in required to
assist in fingerprinting, any NetBackup media server can be a load balancing server.
55

7-55
End of presentation
7-56
Lesson 8: Configuring Tape Storage
This is the “Configuring Tape Storage” lesson in the “Veritas NetBackup 8.1:

8-1
Policies
This lesson is the eighth lesson in this course.


8-2
Lesson objectives
Topic Objective
Understanding Media Manager
Define media manager storage unit concepts.
storage units
Configuring tape devices Use the Device Configuration Wizard to configure new tape devices.
Verifying tape storage Monitor devices using the NetBackup Administration Console.
NetBackup media concepts Describe volumes, volume pools, and volume groups.
Configuring media Use the Robot Inventory to configure new media.

8-3
Topic: Understanding Media Manager storage units
After completing this topic, you will be able to define media manager
storage unit concepts.
After completing this topic, you will be able to define media manager storage unit
concepts.

8-4
Media Manager device considerations
Robotic or stand alone

• Robotic devices automatically load and unload media.
• Stand alone devices require human assistance to load and unload
media.
Device and media compatibility

• The I/O device (tape drive) is separate from the recording media.
• Not all tape media (DLT, SDLT, LTO) is compatible with all tape
drives.
NetBackup refers to tape devices as Media Manager devices, because they are managed
by a component of NetBackup known as Media Manager.
Robotic or standalone
NetBackup interacts differently with robotically controlled devices and stand alone
devices. Stand alone devices require an operator or human assistance when the tape
media is loaded to and unloaded from the device. Robotic controlled devices are
generally automated, and load and unload tape media without the aid of an operator,
normally from tape slots in the library.
In both scenarios, NetBackup needs to know the device path, which describes how the
media server sees the device. These device paths are operating system-specific. In the
case of a robotically-controlled tape library, NetBackup also requires the device path to
the library’s robot, to be able to control that robot.
Device and media compatibility
Besides being robotically controlled or stand alone, media manager devices have
another characteristic. The read/write or I/O device (the tape drive) is actually
separated from the recording media (the tapes).
Not all tapes are compatible with all tape drives. If an incompatible tape gets loaded
into a tape drive, then I/O errors can occur. NetBackup needs to be able to match
appropriate media type for the media (tapes) and devices (tape drives).

8-5
To facilitate this, each media manager device must also be given a logical device type that also
corresponds to the type of media that device will use. NetBackup will never load media of
one type into a device of another type.
Simple device and media compatibility example
Normally a tape library will contain media that corresponds to the media type of its drives. For
example, if the tape library has LTO5 drives, then the library is normally filled with LTO5 tapes.
In this case the NetBackup logical drive type of HCART3 can be assigned to the tape drives,
and the NetBackup logical media type of HCART3 would be assigned to the tapes. If someone
inserted, into this library, a tape that NetBackup had previously identified as HCART2,
NetBackup would not allow the tape to be mounted in the HCART3 drives.
Device and media compatibility example with multiple drive types in a library
In some cases a tape library can have multiple tape drive types. For example, a library may
have two types of drives, both LTO4 and LTO5. The LTO4 drives may be assigned a NetBackup
drive type HCART2, and the LTO5 drives the NetBackup drive type HCART3. When making
media known to NetBackup, a corresponding NetBackup media type should be assigned to
the media that matches the drive type for the intended drive. Media intended for the LTO4
drives should be given a NetBackup media type of HCART2, while media intended for the LTO5
drives should be given a NetBackup media type of HCART3.

8-6
Media manager storage devices and storage destinations in
NetBackup
Media manager storage devices
• Physical tape drives to which data is written and restored

• Interacts with tapes (which must also be configured in NetBackup)
Media manager storage units
• A logical entity that NetBackup associates with tape storage

• Each media manager storage unit must be:
‒ Controlled by the same robot
‒ Same type and density of devices
‒ Same write properties
Storage unit groups
• Can be a mix of media manager and other storage unit types
NetBackup needs to be told about the tape drives that can be used by media servers for
backup and restore operations.
From earlier modules we have seen that NetBackup’s primary backup destination is the
storage unit and that a storage unit refers to one or more physical devices with common
attributes. For backups going to tape, we need to have media manager storage units
which refer to the tape drives connected to a media server that NetBackup is aware of.
We have also been introduced to the Storage Unit Group which is a named list of
storage units. NetBackup can target either a storage unit or a storage unit group as a
backup destination. When a storage unit group is the target, only one of the storage
units defined in the group will be chosen as the target.
Not only does this slide review the differences between devices, storage units and
storage unit groups, it also introduces some of the media manager specific attributes
that media manager devices must have in order to be referenced by the same media
manager storage unit. If two media manager storage devices have differences in these
attributes, then multiple storage units will be required. But, those storage units could
be members of the same storage unit group. And, media manager storage units can
exist with non-media manager storage units within the same storage unit group.

8-7
Robot control with dedicated libraries
LAN • Servers have dedicated tape library with

exclusive access to tape drives.
• Each server is a robot control host.
Robot control host talks directly to the library’s
robotic control interface to move tapes between
slots and drives.
• Each library is registered only once in the
NetBackup configuration.
Robot Robot
control control
host host
With robotically controlled tape drives, each tape drive and the robot control device
appear as separate devices to a NetBackup server. A tape library with four tape drives
properly connected to NetBackup server should show five devices in the NetBackup
server: four tape drives and a robotic device. A robot is also sometimes referred to as a
medium changer on Windows hosts.
A NetBackup server uses the tape drive interface to perform operation such as
positioning the tape to a tape file, reading data from the tape, or writing data to the
tape.
The robot control interface/device is used to perform operations such as moving tapes
from library slots into drives or moving tapes from drives back into their slots.
For libraries that are dedicated to a single NetBackup media server, that NetBackup
media server will be considered the robot control host, and completely control the robot
through the appropriate interfaces. The robot control host is designated in the
NetBackup configuration and is the NetBackup server that is responsible for directly
interfacing with the robot control interface, and moves the tapes from library slots to
drives, and back again.

8-8
Robot control with shared libraries
LAN • Multiple servers are physically connected

to a single library.
Tape drives may be dedicated to specific servers,
or may also be shared.
• One server that sees the robot control
interface is chosen as the robot control
host.
Veritas recommends using the master server, if
SAN connected to the library.
Robot • All other servers request tape moves by
control
host communicating with the robot control
host over TCP/IP.
• Each library is registered in the NetBackup
configuration multiple times (once for
each server connection).
9
A robotic tape library and it’s drives do not have to be dedicated to a single NetBackup
server, especially in a storage area network (SAN). A tape library that is configured to be
accessed by multiple servers is sometimes called a shared library. In these cases all the
tape drives may be seen by all servers, or there may be some tape drives that are
dedicated to specific servers.
Robot control interfaces, due to a limitation of the hardware, do not respond properly
when multiple servers attempt to access them simultaneously. A single NetBackup
server must be defined as the robot control host: the server responsible for directly
interfacing with the robot control interface. Any other server that wishes to move tapes
between slots and drives within the library does so by making a request, over TCP/IP, to
the robot control host., which then issues commands to control the tape robot. Data
movement operations, such as tape positioning, reading data from a tape in a drive, or
writing data to a tape in a drive, is performed directly by each NetBackup server that is
directly accessing the tape device.
It should be noted that in some cases the robot control host is not a NetBackup server.
An example would be Automated Cartridge System (ACS) libraries, where the library is
controlled by ASCLS software that runs on another host. For ACS libraries, NetBackup
servers interact with the ACSLS host to perform robotic control.
Do not confuse a shared library with the NetBackup-licensed Shared Storage Option
(SSO), which allows multiple NetBackup servers to access the same tape drives.

8-9
Media Manager storage unit types
NetBackup NDMP
server host
Media Manager NDMP

storage units storage unit
Tape
library
Tape Stand-alone
library tape drives
10
This slide discusses two of the storage unit types in NetBackup:

• Media Manager
A Media Manager storage unit uses either robotically controlled or stand-alone tape
or optical drives.
• NDMP
NDMP storage units are controlled by NetBackup but attach to NDMP hosts and
require that you have the NetBackup for NDMP option installed. See the NetBackup
for NDMP Administrator’s Guide for more information.

8-10
Tape devices and media manager storage units
SAN Fibre Switch

NetBackup
master server
ms1_tape_stu ms2_tape_stu
Drives 1-3 Drives 4-6
Media Media
server 1 server 2
Tape library with

6 drives
LAN
NetBackup
clients
11
A media manager storage unit is an object in NetBackup that refers to a collection of

devices that use removable media such as tape drives that have a common set of
characteristics:
1. All the devices use the same type of media. Two tape drives that used different
media, such as LTO4 and SDLT2, could not be referred to by the same storage unit.
2. All the devices referred to by the storage unit are either all stand-alone devices or
are controlled by the same robotic library.
Media manager storage units can also control what media server is used. If the device
configuration wizard is used, after devices are discovered, associated storage units are
created. One storage unit per robot per drive type per media server is created.
In the example on this slide, the tape library has 6 tape drives, all of type LTO4. Three of
the tape drives are visible to media server 1 and the other three are visible to media
server 2. The device configuration wizard creates two storage units. The first, STU-A,
refers to the three LTO4 drives in the robot known to Media Server 1, while the other
storage unit, STU-B, refers to the other LTO4 tape drives known to Media Server 2.
On Drive Selection from a media manager storage unit: At the time that a backup job
needs a drive, if the storage unit refers to multiple available, idle tape drives, NetBackup
uses a LRU/round robin mechanism to determine which drive it should assign to that
job.

8-11
Multiple overlapping media manager storage units
Use Any Available
SAN Fibre Switch media server
NetBackup
master server
tapelib1_stu

Media Media
server 1 server 2
Tape library with

6 drives
LAN
NetBackup
clients
12
Storage units can be manually created as well. A single storage unit could have been
created that refers to the three tape drives known to Media server 1 and to the other
three tape drives known to Media server 2, since all six tape drives use the same type of
media and are under the control of the same robotic library. This storage unit would not
have a specific media server configured in the storage unit, but instead be configured in
the storage unit to use Any Available media server. Note that that the storage unit is
still restricted to a single tape robot, drive density, and so forth, so only all media
servers related to those properties will be used.
Media manager storage units designating Any Available media server allow NetBackup
to choose which media server and drives would be used. However, in our example, each
specific tape drive is still assigned to only one media server. If one media server is shut
down, only half the tape drives would be available for use.

8-12
Tape drives and Shared Storage Option (SSO)
All drives are
assigned to all
SAN Fibre Switch media servers
NetBackup
master server
ms1_tape_stu ms2_tape_stu
Media Media
server 1 server 2
Tape library with

6 drives
LAN
NetBackup
clients
13
The shared storage option, a license extension, allows NetBackup to share tape drives
between two or more media servers instead of having the drives dedicated to a specific
media server. Each shared tape drive can be registered with more than one media
server that can physically see the drive. When such a drive is being used by one media
server, for example to run a backup or restore job, that tape drive is not available to the
other media servers. But once the job on that media server is finished, the tape drive
can be used by other media servers for other jobs.
This diagram shows a NetBackup configuration where all 6 drives are known to both
media servers. We are also showing two storage units. Use of STU-A would cause a job
to use Media Server 1 and any of the 6 tape drives while use of STU-B would case a job
to use Media Server 2 and any of the same 6 tapes drives. Regardless of the storage
units used, the drives would be one of the same 6 available to both media servers.
If one of the media servers was shut down, the other media servers would still be able
to use any of the shared tape drives.
Like with non-shared storage, we can also created a storage unit that allows NetBackup
to use any available media server.

8-13
Topic: Configuring tape devices
After completing this topic, you will be able to use the Device Configuration
Wizard to configure new tape devices.
14
After completing this topic, you will be able to use the Device Configuration Wizard to
configure new tape devices.

8-14
Preparing for device configuration
1
Attach hardware
2 Install drivers /
device files
3 Confirm devices
available in O/S
4 Verify with
NetBackup utilities
Refer to the NetBackup 5 Collect device

Device Configuration Guide identification data
15
Complete the following tasks before you configure devices with NetBackup:
1. Ensure that devices are correctly, physically attached to the system.
2. Ensure that the appropriate drivers are installed within the server operating system.
On UNIX, use a SCSI pass-through driver. This is a SCSI driver that passes through
non-drive-specific SCSI commands instead of blocking them. This pass-through is
required in order to handle the robot control commands. Some operating systems
don’t have a SCSI pass through driver, and require NetBackup to install these drivers.
3. If the operating system does not see the devices, neither will NetBackup. Confirm
that the devices are available through operating system tools, such as:
• HP-UX: ioscan
• AIX: lsdev
• Linux: cat /proc/scsi/scsi, lsscsi
• Windows: Device Manager (devmgmt.msc)
4. After NetBackup is installed, use the scan, tpautoconf –t, and tpautoconf –r
NetBackup utilities to verify the operating system devices. NetBackup on Solaris will
additionally have the sgscan utility.
5. At this point, if you do not see the devices, troubleshoot the problem using standard
operating system tools or vendor specific utilities until you can see the devices. For
example, check your SAN zoning or persistent binding configuration.

8-15
Device configuration in the operating system and NetBackup are discussed in great detail in
the NetBackup Device Configuration Guide for your version of NetBackup. For example, refer
to Article 100040277: NetBackup Documentation 8.1, found online at

8-16
Configuring storage devices using the Device Configuration Wizard
• Performs auto-discovery of devices

• Preferred method of device configuration
• Automatically discovers drive positions in the library
for robot types supporting device serialization:
• Can be used to configure drive naming rules, robot

properties, drive properties, and storage units
17
Veritas recommends that you use the Device Configuration Wizard to configure robots
and tape drives. The wizard configures a robot, its drives, and a storage unit. This wizard
discovers the robots and tape drives that are available, and is the preferred method of
device configuration. For the robot types that support device serialization, the wizard
discovers the positions of the drives within the library.
The wizard also provides the ability to customize drive naming rules, robot and drive
properties, SAN clients, and storage units.
The wizard works by querying available device paths on each media server for devices
and for each discovered device (drives and robots), collects information about those
devices, such as serial numbers, type of device, and so on. Device serial numbers are
used to find out which tape drives are controlled by which robots (tape libraries) and
are visible to which media server and if a drive is shared between two or more media
servers. The use of the device serial numbers to correlate drives, robotic libraries and
media servers is called device serialization. The wizard then updates the NetBackup
database with the collected information and assigns device names, robot control hosts
and NetBackup device types for the discovered devices.
Using the device configuration wizard is the preferred method for device configuration.
Devices can be manually configured as well, however the user would be required to
collect the same information and manually update the NetBackup database with the
information. Refer to the Veritas NetBackup Device Configuration Guide for details.

8-17
Topic: Verifying tape storage
After completing this topic, you will be able to monitor devices using the
NetBackup Administration Console.
18
After completing this topic, you will be able to monitor devices using the NetBackup
Administration Console.

8-18
Viewing drive properties
tpconfig -d
19
After the Device Configuration Wizard runs, you can view the properties of the drives
that were configured. To do this:
1. Expand Media and Device Management > Devices and select Drives.
2. In the details pane, select the drive you want to view, and press Enter. You can also
right-click and select Change.
You can also use the command, tpconfig –d on each NetBackup server to report on
what devices have been registered to that server in NetBackup’s enterprise media
manager.

8-19
Viewing robot properties
tpconfig -d
20
There needs to a robotic entry for each media server that needs to communicate with a
library. These can be added manually but as we can see, the Device Configuration
wizard adds the required entries as part of its processing.
After the Device Configuration Wizard runs, you can view the properties of the robots
that were configured. To do this:
1. Expand Media and Device Management > Devices and select Robots.
2. In the details pane, select the robot you want to view, and press Enter. You can also
right-click and select Change.

8-20
Comparing robot properties for Shared robots
lnxmaster lnxmedia
Robot
Robot control
host
21
This example shows entries for a robot that is ‘shared’ between two media servers.
Unlike tape drives which can be directly accessed by multiple NetBackup media servers,
the robotic control interface can not, a robot control host must exist. Every media
server that needs access to a robot including the robot control host, will have an entry
in the enterprise media manager for that robot but only one of those entries will be for
the robot control host. The other entries will indicate that that particular media server
must contact the robot through the control host.
In the example above, there are two entries for the robot known as TLD(0). The entry
for winmaster.example.com shows this it is the robot control host (chosen by the device
configuration wizard). The other entry is for winmedia.example.com and was created
by the wizard because winmedia.example.com sees a tape drive that is controlled by
the robot, TLD(0) so needs to communicate with winmaster.example.com as the robots
robotic control host. In our environment, both winmaster and winmedia can be robot
control hosts but the wizard chose winmaster because it scanned winmaster first.
Again, the output from tpconfig –d can show robot entries based on the server it is
executed on. For a robot control host, it will show the path to the robotic control
interface. If executed from a NetBackup server that is registered with the robot in
NetBackup, but that is not the robot control host, the output identifies what host is the
robot control host.

8-21
Verifying devices using the Device Monitor
vmoprcmd
22
You can use the Device Monitor to determine a drive’s properties and characteristics,
such as its name, host (the media server to which it sends its backup data), and type
(such as DLT). You can also control drives using the Actions menu or by right-clicking a
drive and selecting an action from the drop-down menu. Such actions include activating
a downed drive, resetting a drive, manually invoking drive cleaning, and changing the
comments associated with a drive. To display details about a particular drive, from the
Device Monitor, right-click a drive and select Drive Details from the drop-down menu.
The control column shows the state of the drive:
• TLX/SCAN-TLX (where X depends on robot type) indicates the drive under robotic
control and available for use.
• DOWN-TLX indicates the drive is under robot control is not available for use.
• AVR/SCAN indicates the drive is not under robotic control or robot control daemon is
not running but the drive is available.
• DOWN indicates the drive is not under robotic control or the robot control daemon is
not running and the drive is not available.
The vmoprcmd command enables you to perform operator functions on drives. For
example, to bring a drive up from the command line, enter:
vmoprcmd -up drive_index [-h device_host]

8-22
Viewing Media Manager storage unit properties
bpstulist
23
To view the properties of the storage units that were configured:

1. Expand NetBackup Management > Storage and select Storage units.
2. In the details pane, select the storage unit you want to view, and press Enter. You
can also right-click and select Change.
A Storage unit type of Media Manager refers to all tape drives of a particular density
that are either stand alone or under control of a specific robot. In the example on the
slide, this storage unit will direct backup data to HCART drives within the TLD(0) library.
The value of Media Server shows that winmaster.example.com will be the media server
used. Clicking on the Media server dropdown field displays a list of all the media
servers configured to have access to HCART tape drives within the TLD(0) library.
The media server value of Any Available configures the storage unit to use any of the
media servers that see this type of drive within the specified library. If, at a later time, a
new media server is configured for these drives in this library, it will automatically be
used with this storage unit.
A similar result can be obtained by creating individual storage units for each library, per
drive type, and per media server, and then adding those storage units to a storage unit
group. However, if a new media server is given access to the library, a new storage unit
would need to be created and it would have to be manually added to the storage unit
group.

8-23
Summary of NetBackup device-related queries
Task Administration Console Command line OpsCenter
List configured tape Media and Device tpconfig –d Monitor > Devices
drives and robots Management > Manage > Devices >
Devices Robot | Drives
Monitor the state and Media and Device vmoprcmd Monitor > Devices
availability of tape drives Management > Device Manage > Devices >
Monitor Drives
List devices that would scan
be found and configured tpautoconf –t
by the device
configuration wizard if it tpautoconf –r
were to be run.
24
This slide shows some of the ways you can query NetBackup about your device
configuration.
tpconfig –d queries the Enterprise media manager for devices that have been registered
with the media server the command is run from. You run this command from a
NetBackup server. It can also be used to manually register a device with a NetBackup
server.
vmoprcmd queries all of the ltid processes to report the status of drives on all
NetBackup servers in a domain. It can also be used to manage the state of drives
(up/down).
scan/tpautoconf –t/tpautoconf –r are commands that scan a hosts device endpoints
and report the devices that are present. Devices reported by these commands will be
picked up by the device configuration wizard and configured into the enterprise media
manager.

8-24
Topic: NetBackup media concepts
After completing this topic, you will be able to describe volumes, volume
pools, and volume groups.
25
After completing this topic, you will be able to describe volumes, volume pools, and
volume groups.

8-25
What are volumes?
Volume is NetBackup’s term for removable media.
• Each tape is a volume.

• Every volume is assigned a unique media ID in the NetBackup database.
26
Media Manager volumes are tapes that have been assigned media IDs and other
attributes, which are recorded in NetBackup database.
You should know the following about volumes:
• A piece of media becomes a volume when Media Manager assigns a media ID (also
known as the Recorded Volume Serial Number or RVSN).
• NetBackup requests volumes from Media Manager using the media ID.
• NetBackup writes a label to the media that contains the media ID.
• If a tape cartridge has a recognized external barcode, this is also recorded in the
NetBackup database, and used to generate the media ID for a new tape. The
barcode is sometimes referred to as the EVSN or External Volume Serial Number.
Note: The media ID is limited to six characters, and NetBackup only reads thirteen
characters on a bar code label.
To control how media IDs are generated from barcode values, define media ID
generation rules that specify which characters of a bar code on a cartridge are to be
used to generate a media ID. Multiple media ID generation entries can be specified,
allowing media ID generation to be specific for each robot and length of barcode, and
offering flexibility for multimedia.

8-26
Understanding Media IDs and barcodes
Default (rightmost six):

Media ID: N256S2
Bar code: JYN256S2
Customized:
Media ID: JYN256
Media ID: An unique NetBackup volume serial number
• The bar code and the Media ID are recorded in the NetBackup database.
• The media ID may be from one to six digits.
• The media ID is also recorded on the first block of the tape.
• This internal media ID is also called the tape’s label.
• You can customize media ID generation.
27
NetBackup assigns each volume a unique media ID. This media ID may be assigned
manually, or it may be automatically generated using bar codes and a process known as
robotic inventory. Considering the large number of tapes in an enterprise backup
environment, most environments use bar codes and robotic inventory. Manually
assigning media IDs is only performed in special circumstances.
The maximum length of a media ID is six characters and is typically based on the bar
code. If the bar code is longer than six characters, by default NetBackup uses the last six
characters as the media ID, as shown in the slide on this page. Customizing this behavior
is shown later in this topic.

The media ID of each volume is stored in the NBDB and is also written on the tape itself.
The location where the media ID is written is called the tape header, or label. Use
caution when assigning media IDs. To avoid confusion, Veritas recommends having the
tape’s Media ID be identical, or very similar to, its bar code. Also, to avoid problems
when restoring data, ensure that any media id generation rules you configure in your
production environment are also configured in your disaster recovery environment.
If robotic inventory is used on tape cartridges that have no barcode labels then
NetBackup assigns those tapes unique media IDs based on a simple mechanism starting
with the initial media ID A00000 (the letter A followed by 5 zeros) and incrementing the
value until a unique media ID is found.

8-27
Understanding volume pools
A volume pool is a set of volumes defined for a specific purpose.
NetBackup CatalogBackup Scratch
Default pool Catalog backups Empty tapes
Datastore None ServerBackups OffsiteCopies

Integrated3rd- Cleaning tapes
party apps
Default volume pools Administrator-defined, as required

28
NetBackup organizes volumes in volume pool. The volume pool used by a backup job is
specified as part of the backup policy definition.
The following volume pools exist, by default:
• NetBackup: The default volume pool used by most policies initially and the pool new
tapes discovered by robotic inventory are assigned to by default.
• DataStore: The default volume pool for some integrated third-party applications.
• CatalogBackup: The default volume pool for storing NetBackup catalog backups.
• None: The volume pool used for tapes NetBackup should not write to, such as
cleaning tapes and non-NetBackup tapes.
In addition to these predefined pools, you can create your own pools to segregate
backups to different tapes, such as for backup images staying onsite and images being
sent offsite, or for backups of different types of applications.
The scratch pool is an optional volume pool that you can configure to store unused, free
tapes.

8-28
The scratch volume pool
• Contains unused media.
• Can use any name. Scratch
Only one per NetBackup domain.
Empty tapes
1• Provides tapes to volume pools that
need new media during a backup.
2• Gets freed tapes back from volume 2
1
pools (if originally from scratch pool).
ServerBackups OffsiteCopies
Tape with available space
Tape with no available space
29
The scratch pool is an optional volume pool that you can configure. You can have only
one scratch volume pool per NetBackup domain. Any media manager storage unit can
have volumes that are in the scratch pool. If the scratch pool is configured, NetBackup
moves volumes from that pool to other pools that do not have volumes available, when
required. The name of the scratch pool does not matter. However Veritas recommends
creating a pool with a defining name, such as Scratch or free_tapes.
NetBackup does not assign volumes while they are in a scratch pool, and the scratch
pool cannot be targeted by a backup policy.
A volume moved from the scratch pool to another volume pool due to backup needs,
remains in the other pool until it is unassigned (all image reach their retention).
NetBackup moves volumes back to the scratch volume pool after the volume is
unassigned. To disable this feature, update the NetBackup database using the following
command:
nbemmcmd -changesetting
-return_unassigned_media_to_scratch_pool no
-machinename master_server

8-29
Understanding volume groups
• Track the physical location of volumes

• Are robotic (volumes are in a tape library) or stand-alone (volumes are not in a tape
library)
TLD0
Eject Vault
Volume Group:
---
Volume Group:
Volume Group:
OFFSITE
000_00000_TLD
30
A volume group is a logical group of volumes that are located at the same physical
location. This allows NetBackup to track media by location.
Each robotic library can have one or more pre-defined volume groups with a name
based upon the robot number, robot type, and media type. For example, the first library
defined might have the library name “TLD0”, which would have the volume group
000_00000_TLD.
If a volume is in a the 000_00000_TLD volume group, it is considered to be resident in
the TLD0 library. If another tape is in the same library but of a different media type (in
other words, in a different media manager storage unit) then that tape will be assigned
to another volume group such as 001_00000_TLD.
These volumes are resident in the robot, so the robot can automatically load the
volume for backup and restore operations. When robotic inventory is run and
NetBackup identifies volumes moved into the library, by default, NetBackup will assign
each volume to an appropriate robotic volume group based on the robot the tape was
found in and the media type of the tape.
The following are the rules for assigning volume groups:
• A volume can be assigned to only one volume group.
• All volumes in a group must be the same media type. However, a media type and its
corresponding cleaning media type are allowed in the same volume group (such as
DLT and DLT_CLN).

8-30
• All volumes in a robotic library must belong to a volume group. You cannot add
volumes to a robotic library without specifying a group or having Media Manager
generate a name for the group.
• More than one volume group can share the same location. For example, a robotic
library can contain volumes from more than one volume group and you can have
more than one stand-alone volume group.
• Volume groups are not created like volume pools. Volume groups appear when they
have at least one volume assigned to them. If all the volumes in one volume group
get assigned to other volume groups then the first volume group would no longer
appear in the interface.
• All volumes in a group must be in the same robotic library or be stand-alone. That is,
you cannot assign a volume that exists in one library to a volume group that has
volumes already assigned to it that are in another library or that are stand alone.
If a backup or restore operation is queued due to a pending media mount request,
review the volume group for the piece of media to determine the location of the tape.
For example, if a volume is in a volume group called OFFSITE, it may be that the tape is
not in the robot but was vaulted/sent to offsite storage.
Backup Exec differences
NetBackup may use different terminology than other backup software for the concepts
of volume pools (the purpose of a tape) and volume group (the location of a tape).
If you are familiar with Backup Exec terminology, here is a quick translation:
General term Backup Exec NetBackup
Tapes Media Volumes
Tape sets Media sets Volume pools
Tape location Media location Volume group

8-31
Understanding volume groups and volume pools
FileServer volume pool
Volume pools can be used to force

Database volume pool
NetBackup to place backups on
separate tape volumes for specific jobs
and backup types.
VirtualMachine volume pool
A volume group is a set of volumes

that reside at the same physical
location, such as in a specific robot or
Robot 1 Stand-alone Offsite a specific offsite location
volume group volume group volume group
32
Volume groups allow you to group media by its location. Volume pools are used when
you want or need different backups to be placed onto different sets of tapes. The
reason for separating backups are dependent on your needs and problems you need to
overcome. For example, enabling parallel restore of two extremely critical systems by
making sure the backups of those two systems don’t go to the same tape. Another
example is having a local set of backups kept onsite but also having copies of those
same backups stored at an offsite location for long term retention.
However, one needs to be judicious here. The more volume pools you create, the more
management you have to perform. Additionally, NetBackup already segregates tapes

based on retention level, by default, so creating separate volume pools for separate
retention tapes is often unnecessary.
A volume group are labels for both robotic libraries and non-robotic locations. There can
be multiple non-robotic volume groups, just as there can be multiple robotic libraries.
Changing volume group designation for a volume provides the means for NetBackup to
track a volume’s physical location. Using the vmdelete command, you can delete
volumes from the NetBackup database by specifying the group name, rather than
individual media IDs.
Multiple volume pools can exist in the same location. For example, a robotic library
may hold volumes assigned to your MSSQL_Pool (tapes for MSSQL backups) and hold
volumes assigned to your ORACLE_Pool (tapes for Oracle backups).

8-32
Topic: Configuring media
After completing this topic, you will be able to use the Robot Inventory to
configure new media.
33
After completing this topic, you will be able to configure media using Robot Inventory
and configure barcode and media ID generation rules.

8-33
Volume configuration methods
NetBackup Volume Configuration Wizard
• Runs the robot inventory
• Adds volumes found in library, into desired volume pools
• Supports barcode and media ID generation rules
NetBackup Administration Console

• Found under Media and Device Management.
• Supports the robot inventory
• Allows for manual creation of volumes
Command Line
• Provided by Media Manager commands.
• Use vmadd, vmupdate, and vmchange commands.
34
There are a number of ways to configure volumes in NetBackup:

• The Volume Configuration Wizard runs the NetBackup Robot Inventory, which
scans for tapes in available tape libraries, and can be configured to automatically
add them to the NetBackup configuration.
After you run the robot inventory to configure media, each piece of media has a
unique media ID in the NetBackup media databases. The wizard or utility creates
media that have a media type determined by the drive type. The default media type
is used.
Additionally, volumes can be added manually.

• Similar to the wizard, the NetBackup Administration console also supports the robot
inventory under the Media and Device Management section of the NetBackup
Administration Console. Additionally, methods for manually configuring volumes is
provided.
• The command-line has a number of commands that are available to perform
volume configuration tasks. There are some commands which initiate a text-menu
interfaces, such as tpconfig. Refer to the NetBackup Commands Reference Guide, or
the command man pages on UNIX, for details and syntax of NetBackup commands.

8-34
Preparing to run Robotic Inventory
Volume Pools
• Create scratch pool
• Create other volume pools
• Perform before running inventory
Barcode Rules
• Assigns density, volume pool, and other properties
ABC* according to barcode
Media type: HCART3 • Create before or during inventory
Volume Pool: dups
Media ID
Generation Rules • Assigns Media ID according to barcode
ABC123L4 • Create before or during inventory
Media ID: ABC123
35
Using robot inventory enables accurate tracking of volumes within robotic libraries,
including determining which volumes are in a robot and their exact slot location.
The steps on this slide describes tasks that need to be performed either before or
during the robotic inventory. These tasks include creating all custom volume pools, bar
code rules, and media ID generation rules that may be needed. Newly configured rules
are not applied to media that already exists in NetBackup. For any media that was
added before the rules were created, either manually update the media or delete the
media and re-run the robot inventory. At that point, the rules will be applied.
A bar code rule specifies criteria for assigning attributes to new robotic volumes.
NetBackup assigns these attributes by using the bar code for the volumes cartridge that
the robotic library provides along with your bar code rules. After bar code rules are
established, NetBackup automatically assigns media, based on the bar code tag, to a
specific volume pool and media type.
Media ID generation rules enable you to override the default media ID naming method
that NetBackup uses for new tapes that have barcodes. The default method uses the
last (rightmost) six characters of the bar code provided by the robot to generate the
media ID. Use the rule to control how NetBackup creates media IDs by specifying which
characters of a bar code are used in the media ID. In addition, you can specify that
alphanumeric characters are to be inserted into the ID. Multiple rules can be used to
accommodate different robots and bar code lengths.

8-35
Creating volume pools
vmpool
36
To create a volume pool in the NetBackup Administration Console:

1. Select Media and Device Management > Media > Volume Pools.
2. Click on the star-burst icon, or selecting the appropriate option in the Actions menu
or by right-clicking on Volume Pools in the navigation tree.
Options in the New Volume Pool dialog box include:
• Media Manager host: Displays the name of the master server.
•
Pool name: A unique volume pool name; Up to 20 alphanumeric characters long and
is case-sensitive.
• Description: A brief description of the volume pool.
• Maximum number of partially full media: The number of partially full media (for
each retention level) that NetBackup will allow backup to concurrently write to in
the pool. The default number (0) places no limit on partially full media in the pool.
• Scratch Pool: Allows the pool to be used as a scratch pool. After defining the scratch
pool, add empty volumes to the pool. Only one pool can have this attribute.
• Catalog backup pool: A dedicated pool used for backups of the NetBackup catalog,
to be used for NBU-Catalog policies. Multiple catalog backup pools are allowed.

8-36
Starting a robot inventory
vmupdate
37
To start a robot inventory, use the NetBackup Administration Console to invoke the
Inventory Robot function:
1. In the left pane, select Media and Device Management > Media > Robots.
2. Select the robotic library desired. If there are multiple entries for the same robot,
choose the entry for host that is the robotic control host.
3. Right-click the robot and select Inventory Robot, or select Actions > Inventory
Robot.
If you are planning on discovering and adding tapes in a library media or cartridge
access port (MAP or CAP), insert one or more volumes into the robotic library prior to
running the robot inventory, and ensure there are available slots in the library.

8-37
Robot Inventory: Show Contents
Robot
control
host
38
When the Robot Inventory dialog is shown, it allows for various inventory operations to
be performed. Each operation communicates with the robot control host. You need to
make sure that the Device Host field shows the name of the robot control host for the
robot you wish to inventory. If you selected the wrong entry from the Robots list in the
Object tree, this gives you a chance to change the value.
Selecting the Show contents radio button and clicking Start runs the Show Contents
inventory operation. This function initiates the most basic NetBackup inventory
operation requesting the robotic library for a list of its slot contents. This function
simply displays the response from the robotic Library. Most modern robotic libraries
cache this information so the operation is relatively fast. However, some older robotic
libraries will physically pole each slot at the time of the request so it could take longer.
The Show Contents inventory operation is useful for determining the contents of a
robot as follows:
• If the robot has a bar code reader and contains media with bar codes, the report
displays whether each slot has media and lists the bar code for the media.
• If the robot does not have a bar code reader or does not contain media with bar
codes, the report displays whether each slot has media.
• If the robot is an API robot (like an ACS robot), the report displays a list of media
found in the robot.

8-38
Robot Inventory: Compare contents
39
The Compare Contents with volume configuration function is similar to the Show
Contents operation but takes the operation a step further. Instead of simply displaying
the response of the robotic library, it compares the response with the contents as is
stored in the NetBackup.
The comparison is displayed in the Results field and shows discrepancies between what
the robot reported and what the NetBackup configuration thinks should be in the
library. Each discrepancy is indicated by a value of yes in the Mismatch Detected
column of the output. This output includes the Media ID value since this operation
accesses not only the library but also the information in the NetBackup database.

8-39
Robot Inventory: Preview volume configuration changes
40
The Preview volume configuration changes inventory function, like Show Contents,
requests a slot inventory from the robotic library, and like Compare contents with
volume configuration, compares the response from the robot with what is registered in
NetBackup.
However, instead of displaying the results or the discrepancies, based on the
discrepancies found, this function derives a set of operations, that if applied to
NetBackup, would update the database to reflect what is currently in the robot and
displays the proposed changes. Note that no changes are actually performed. This
operation simply displays what would be done if the operations were executed.
Also take note that with this inventory operation selected, the Advanced Options
button is now available. This allows you to see some of the effect using advanced
options would have on the database like the effect media id generation rules would
have on the value of the generated Media ID for new media discovered without actually
making the changes to the database.

8-40
Advanced Robot Inventory Options
41
The Advanced Robot Inventory Options dialog has various tabs. The Media Settings tab
is separated into two sections: the Existing media frame and the New media frame.
The Existing media frame allows you to specify volume groups for media already known
to NetBackup for the purposes of tracking the location of the media. As stated
previously, a volume group identifies the physical location where media should be
found.
• The Media which have been removed from the robot should be assigned to the
volume group field is used to set the volume group when a tape is later found to be
missing during a robot inventory. By default the volume group for a tape will be set
to --- (3 dashes), which does little to inform the NetBackup administrator as to
where the tape is physically found. By setting a value, tapes from the library that are
not found (normally those that have been ejected) will be placed in that volume
group. Even though this field looks like a drop-down box, it is also an entry field; By
typing a new value, a volume group gets created when the first volume is placed
there. The volumes in any group mentioned in this field must all be of the same type
and, based on the inventory, not in any robot.
• The selection list always has the following choices:
• DEFAULT: Allow Media Manager to select the volume group – generally clears
the volume group label.

8-41
• AUTO-GENERATE: Automatically generate a new volume group.
• NO VOLUME GROUP: Do not assign a volume group.
• The Media which have been moved into or within the robot should be assigned to the
volume group field specifies the volume group that Media Manager assigns to existing
media that you have inserted into the robot, or moved to a new location within the robot.
The default behavior for known media added to the library is to have the volume group set
to the volume group that is compatible with the library and the media type of the volume,
usually one of the robotic volume groups found with a numbered name formatted as
XXX_YYYYY_RRR.
The New Media frame lets you set properties used for newly discovered media.
• Use the following Media ID prefix is used when the robot does not support bar codes, or
the volume inserted does not have readable bar codes, by assigning a prefix to the new
volume’s media id. The prefix becomes the leading part of the new media id and is made
unique by appending numerals to generate a unique 6 character id.
• Label optical media is enabled only if you selected an optical robot to inventory.
• Use barcode rules tells NetBackup to consult Barcode Rules to assign volume pool and
media type designations to newly discovered media.
• Media type and Volume pool fields are used to override NetBackup’s normal volume pool
and media type assignment policies. If either of these fields are set, then the specified
value will be used even if the barcode rules check box is checked. These fields act as one
time overrides., as they will be reset to DEFAULT the next time a robot inventory is run.

8-42
Advanced Options: Barcode Rules tab
vmrule
43
A bar code rule specifies criteria for assigning attributes to new volumes discovered by
robotic inventory. The attributes are assigned based on what barcode tag matches the
barcode label of a given volume.
• The Barcode tag is a string used to match the left-most portion of the barcode label.
If the barcode label matches multiple tags then the rule whose tag matches the
largest portion of the barcode label is used. There are two special barcode tag
designations: NONE which matches any cartridge where a barcode label could not
be read and DEFAULT which is used if none of the other barcode tags match the
barcode label. The DEFAULT barcode tag is often used to change NetBackup default
behavior of placing new volumes into the NetBackup volume pool. Without this
barcode tag, any new volume not matching any barcode tags will be assigned to the
NetBackup volume pool and be given a media type based on the drive types within
the robot. Note: The actual text of the BARCODE tag input are the letters DEFAULT
but that NetBackup displays this RULE’s tag as <DEFAULT>. The NONE barcode tag
works the same.
• Maximum Cleanings/Maximum Mounts is used by NetBackup as a usage limit so
tapes and cleaning cartridges do not get overused. A value of zero indicates that no
limit exists. This field allows an initial value to be specified for new tapes discovered
through robotic inventory. These limits can be changed after the tape is made
known to NetBackup at any time. Tapes whose labels do not match any of the tags
or tapes that were inventoried with barcode rules enabled get zero as the default.

8-43
• The Media type value specifies the NetBackup media type the newly discovered tape will
be assigned for the associated barcode tag. There are two categories of media types,
regular and cleaning. Using a cleaning media types forces the Volume Pool field to be set
to NONE. DEFAULT is a regular media type that tells NetBackup to assign the media type
of the tape based on the drive type within the robot.
• The Volume Pool value allows you to specify the volume pool that will be assigned to new
media if their barcode labels match the associated barcode tag. If the value is set to NONE
and cannot be changed, then the Media Type was already set to a cleaning media type.

8-44
Advanced Options: Media ID Generation tab
Barcode Rule Media ID

ABC123L4 none C123L4
ABC123L4 1:2:3:4:5:6 ABC123
ABC123L4 1:4:5:6:7:8 A123L4
ABC123L4 #N:#Y:3:4:5:6 NYC123
45
Every volume used by NetBackup needs to have a unique, six character media id. For
robotic libraries with barcode reading abilities, the value of the barcode label read by
the robot’s barcode reader can be used to derive the media id for newly discovered
media.
By default, NetBackup uses the right-most 6 characters of the barcode label as the
media id that is assigned to the new tape. This can cause problems for two or more
tapes with barcode labels longer than six characters, if the resulting media ids would
not be unique. If two tapes each had the barcode label values S00006L1 and D00006L1,
NetBackup would try to assign both tapes the same media id 0006L1, and the inventory
process would produce errors.
Media ID generation rules allow you to specify what characters of the barcode are used
to generate the media ID.
To create a new media ID generation rule, click the Media ID Generation tab and click
the New button, and then specify the properties as follows:
• Robot number: The number associated with a robot. TLD(0), for example is robot
number 0.
• Bar code length: The length of barcode this rule applies to. Barcodes of lengths
other than this value will not use this rule.

8-45
• Media ID generation rule: The actual rule to apply. This is a string comprised of at most
six colon separated fields. Each field position species the source value for the
corresponding media id character. The first field specifies what character from the barcode
label to use as the first character of the media id, the second field specifies what character
from the barcode label will be used as the second character of the media id, and so on.
Instead of specifying the character position from the barcode label, each field can also
specify a constant character value if the field value is prefixed with the ‘#’ (hash) character.
There is the potential for conflict when you have multiple tape libraries with multiple tapes.
You can use Media ID generation rules to uniquely identify tapes and associate them with
their owning libraries.
For example, create media ID generation rule #A:2:3:4:5:6 for tapes belonging to Library A,
and create media ID generation rule #B:2:3:4:5:6 for tapes belonging to Library B. This
generates media IDs A00000, A00001, A00002, and so on for Library A, and media IDs
B00000, B00001, B00002, and so on for Library B.
The problem with this scenario is that the external bar code labels do not reflect the unique
media IDs. If all of your tapes are stored together, you cannot easily identify which tapes
belong to which library.
Two possible solutions are:
• Order tapes that have unique bar code labels.
• Color-code your bar code labels.
If a particular barcode label has a length that does not correspond to any media id generation
rules that exist for that robot then NetBackup uses it’s default behavior.
Note: There is no command line interface to manage media id generation rules.
Some examples of media ID generation rules are given in the table on the slide.

8-46
Robot Inventory: Update volume configuration
47
The Update volume Configuration operation is similar to the Preview volume

configuration changes operation in that it also queries the robot as to it’s contents,
compares the results returned by the robotic library with what is currently registered
within the Enterprise Media Manager, and from the discrepancies seen, generates a
series of changes to apply bringing the Enterprise Media Manager up to date with the
current contents of the library. However, instead of simply displaying the proposed
changes, the changes are actually executed and the Enterprise Media Manager is
updated.
Like Preview volume changes, this operation allows access to the Advanced Options
properties.

8-47
Viewing all media
vmquery –a -b
nbemmcmd –listmedia –allrecords -brief
48
Select Media and Device Management > Media to display all media in your
environment. Notice the Volume Pool and Volume Group columns.
To display volumes, including the volume pools and volume groups to which they
belong, use the following commands:
vmquery -a -b
nbemmcmd -listmedia -allrecords -brief

8-48
Summary of Robot Inventory utilities
Inventory function Administration Console Command line OpsCenter

Show the contents of the Actions > Inventory robot vmcheckxxx –list
robot
Compare the contents of Robot inventory dialog vmcheckxxx –full
the robot with the defined box: Show contents
configuration
Preview the volume Robot inventory dialog vmupdate –recommend
configuration changes box: Preview volume
configuration changes
Update the volume Robot inventory dialog vmupdate
configuration box: Update volume
configuration
Create barcode rules and Robot inventory dialog box vmrule (barcode rules only)
media ID generation rules > Advanced options
49
If you are adding volumes to a robotic tape library, you can have NetBackup inventory
the robot and use the information to update the volume catalog.
The table on this slide presents an overview of the process of adding volumes using the
inventory update function.
There is no command line interface for creating media id generation rules.
Note: The first three rows in the table on this slide do not modify the volume database.

8-49
Lesson summary
• Key points
– In this lesson, you learned about the Device Configuration Wizard.
– You also learned how to define media manager storage units, and to use the Volume Configuration
Wizard and Robot Inventory to configure new media.
– Finally, you also learned how to monitor devices and media using the NetBackup Administration
Console.
– NetBackup Device Configuration Guide
– NetBackup for NDMP Administrator’s Guide
– NetBackup Shared Storage Guide
50

8-50
Lab 8: Configuring Tape Storage
Lab objectives
• Verify that tape devices are visible to the OS of media server systems
• Configure tape devices and storage units using the Device Configuration Wizard
• Verify the tape devices and storage units configuration
• Configure volume pools
• Configure volumes using the Robot Inventory user interface provided by NetBackup and,
in the process, create barcode rules
• Verify volume and volume pool configurations

8-51
What did you learn?
lesson.
52
current lesson.

8-52
Question: Recommended configuration method
What is the recommended method to configure devices into Media Manager?
A. The Media and Device Management interface

B. The Device Management Configuration utility
C. The Command-line interface
D. The Device Configuration Wizard
53

8-53
Answer: Recommended configuration method
What is the recommended method to configure devices into Media Manager?
A. The Media and Device Management interface

B. The Device Management Configuration utility
C. The Command-line interface
D. The Device Configuration Wizard
54

8-54
Question: What is device serialization?
What is device serialization?
A. The order in which devices are configured by the wizard

B. A firmware feature that enables device identification and configuration
C. A separate interface used to configure standalone tape drives
D. A method of reporting device errors to NetBackup
55

8-55
Answer: What is device serialization?
What is device serialization?
A. The order in which devices are configured by the wizard

B. A firmware feature that enables device identification and configuration
C. A separate interface used to configure standalone tape drives
D. A method of reporting device errors to NetBackup
56

8-56
Question: Volume pool with cleaning media
Which volume pool holds cleaning media?
A. NetBackup
B. DataStore
C. None
D. Scratch
57

8-57
Answer: Volume pool with cleaning media
Which volume pool holds cleaning media?
A. NetBackup
B. DataStore
C. None
D. Scratch
58

8-58
End of presentation
8-59
Lesson 9: Managing Tape Storage
This is the “Managing and Optimizing Tape Storage” lesson in the “Veritas NetBackup
8.1: Administration” course.

9-1
Policies
This lesson is the ninth lesson in this course.


9-2
Lesson objectives
Topic Objective
View and change robot and tape drive settings, including drive
Managing robots and tape drives status, and perform drive cleaning and running robot and drive
diagnostics.
Identify and monitor NetBackup media states, and understand
Monitoring media and media states
NetBackup media selection and lifecycle.
Perform media management, including moving, ejecting, changing,
Managing tapes
sharing, erasing, and deleting volumes.
Media- and device-related tips Identify tape device and media reports.

9-3
Topic: Managing robots and tape drives
After completing this topic, you will be able to view and change robot and
tape drive settings, including drive status, and perform drive cleaning.
After completing this topic, you will be able view and change robot and tape drive
settings, including drive status, and perform drive cleaning.

9-4
Managing tape drive properties
Path properties
General drive
properties
tpconfig -d
5
To change the properties of a drive in the NetBackup Administration Console, expand

Media and Device Management > Devices, right-click the drive and select Change.
Caution: Manual configuration of tape drives is prone to human error, therefore Veritas
recommends configuring tape drives with the Device Configuration Wizard.
You can change the following properties:
• Drive name identifies the drive and must be unique. A descriptive name is
recommended; however, drive name is limited to 48 characters. When adding a new
drive manually or through the device discovery wizard, you can use drive name
rules.
• Host and path information defines the hosts and that host’s specific device path to
this tape drive. If the drive is shared, there will be one entry for every media server
accessing this drive.
• Drive Information allows you to specify the following information:
• The Drive type specifies the type of drive you are adding.
• Use the Cleaning Frequency (In hours) property to set the desired number of
mount hours between drive cleanings, for drives that do not support TapeAlert.
• Drive is in a robotic library specifies whether the drive is in a robotic library.
• The Robotic library specifies a robot that controls the drive.

9-5
• The Robot drive number indicates the physical location of the drive in the robot.
In many libraries, drive numbering begins with 1. This can be confusing as the
operating system numbering begins with 0, so it is common for the OS drive
number and the Robot Drive number to be off by one. Note that different
libraries may behave differently; for example some libraries allow you to choose
whether to begin numbering with 0 or with 1.

9-6
Stopping and restarting the Device Manager service
stopltid UNIX
ltid
net stop “NetBackup Device Manager” Windows

net start “NetBackup Device Manager”
After you configure a robot or drive, you are prompted to stop and restart the device
daemons or services. If you choose to do this later, you can stop and restart the
daemons or services using the Media and Device Management interface.
1. Select Actions > Stop/Restart Media Manager Device Daemon.
2. Complete the dialog box as follows:
a. Select a device host. The status of the selected daemon or service is shown
under Current Status.
b. In the Action pane, you can start, stop, or stop/restart the service. Select the
action you want to perform.
c. The Options pane enables you to eject media from a stand-alone drive and
control the level of debug logging. Select the options you want to perform.
3. Click OK or Apply.
You can also use the stopltid and ltid commands to manage the Media Manager
daemons or services. The stopltid command stops ltid, avrd, and the robotic
services; ltid starts ltid, avrd, and the robotic services.
On Windows you can also stop and start the Media Manager services using Windows
Computer Management, by restarting the NetBackup Device Manager service.

9-7
The robtest program
Uses a silent prompt
PS C:\Users\administrator.EXAMPLE> robtest
Configured robots with local control supporting test utilities:
m s1 d1
TLD(0) robotic path = {3,0,0,3} Initiating MOVE_MEDIUM from address 4096 to 256
MOVE_MEDIUM completem s1 d1
Robot Selection Initiating MOVE_MEDIUM from address 4096 to 256
--------------- MOVE_MEDIUM complete
1) TLD 0
2) none/quit
_
Enter choice: 1
1
Robot selected: TLD(0) robotic path = {3,0,0,3} Popular robtest commands

Invoking robotic test utility:
C:\Program Files\Veritas\Volmgr\bin\tldtest.exe -rn 0 -r {3,0,0,3} Command Description
Opening {3,0,0,3}
MODE_SENSE complete init Initialize a library
Enter tld commands (? returns help information)
? inquiry Get library vendor / model information
To exit the utility, type q or Q.
s s Obtain slot status
init - Initialize element status
initrange <d#|s#|p#|t> [#]- Init element status range
allow - Allow media removal s d Obtain drive status
prevent - Prevent media removal
extend
retract
- Extend media access port
- Retract media access port
m s4 d1 Move media from slot 4 to drive 1
mode - Mode sense
m <from> <to> - Move medium unload d1 Unload drive 1
pos <to> - Position to drive or slot
s [d|p|t|s [n]] [raw] - Read element status
inquiry - Display vendor and product ID q Quit
rezero - Rezero unit
inport
debug
- Ready inport (media access port)
- Toggle debug mode for this utility
? Help
test_ready - Send a TEST UNIT READY to the device
The robtest utility allows you to control a robot using the robot’s control interface,
on the robot control host. It lets the user issue low level robotic control commands to
control the robotic arm, change access to mail slots, transport media between locations
in the robot (slots, drives, mail ports) and query information about the robot just like
NetBackup does. You can use robtest, for example, to see if the robot is receiving or
executing robot control commands, view contents of slots, drives, and mail ports, find
out how many drives, slots and mail slots are available, if there is a barcode reader, and
so on.
The robtest program searches the NetBackup database and presents a menu of
available robots physically controlled by a host. You must run robtest on the media
server that is the robot control host, by running the following command:
• UNIX: /usr/openv/volmgr/bin/robtest
• Windows: install_path\Veritas\Volmgr\bin\robtest.exe
When you select a robot, robtest invokes the device-specific test tool (such as
tldtest for a TLD type robot). From each test utility, you can obtain a list of available
test commands by entering a question mark (?).

9-8
Sample robtest commands
The following example shows the output from entering the init command and the mode
command:
init
Initiating INITIALIZE_ELEMENT_STATUS
INITIALIZE_ELEMENT_STATUS complete
mode
First transport addr = 1, Number transport elements = 1
First storage addr = 4096, Number storage elements = 15
First media access port addr = 16, Number media access port
elements = 5
First drive addr = 256, Number drive elements = 2
Library does have a barcode reader
MODE_SENSE complete
Warning: The init command reinitializes the library and may take a long time to run.
Caution: Do not leave robtest running in your production environment. Doing so can
lead to device errors and prevent any access to the library for backups, restores, and
inventory. While robtest is running, NetBackup cannot communicate with the device
control host to control the robot for backup jobs.
Caution: If you use robtest to load a tape into a drive, you need to remove the tape
using robtest. NetBackup does not autoeject a tape that has been loaded by any
other utility.

9-9
In the following example, the m s4 d1 command moves media from slot 4 to drive 1.
The s s command displays the status of the slots. You can see that slot 4 is now empty.
The s d command confirms that drive 1 now contains the media:
m s4 d1
Initiating MOVE_MEDIUM from address 4099 to 256
MOVE_MEDIUM complete
s s
slot 1 (addr 4096) contains Cartridge = yes
Source address = 256
Barcode = 090000L1
Barcode = 090001L1
Barcode = 090002L1
slot 4 (addr 4099) contains Cartridge = no
Barcode = 090004L1
Barcode = 090005L1
Barcode = 090006L1
Barcode = 090007L1
Barcode = 090008L1
Barcode = 090009L1

Barcode = 09000AL1
<< Press return to continue, or q and return to stop >>
q
READ_ELEMENT_STATUS complete
s d
drive 1 (addr 256) access = 1 Contains Cartridge = yes
Source address = 4099 (slot 4)
Barcode = 090003L1
drive 2 (addr 257) access = 1 Contains Cartridge = no
READ_ELEMENT_STATUS complete

9-10
Using the Device Monitor
vmoprcmd
11
You can use the Device Monitor to determine a drive’s properties and characteristics,
such as its name, host (the media server to which it sends its backup data), and type
(such as DLT). You can also control drives using the Actions menu or by right-clicking a
drive and selecting an action from the drop-down menu. Such actions include activating
a downed drive, resetting a drive, manually invoking drive cleaning, and changing the
comments associated with a drive. You can also use the Device Monitor to determine
robot types and numbers.
To change a drive path operating mode:
1. In the NetBackup Administration Console, expand Media and Device Management

> Device Monitor.
2. Click the Drives tab.
In the details pane, the Drive Paths pane displays path information for drives.
3. In the Drive Paths pane, select a path or select multiple paths.
4. On the Actions menu, select the path action as Up Path ( Up Path, Operator control
applies to stand alone drives), Down Path, or Reset Path.
Note: The Media Manager Device daemon (ltid) must be running on the host being
monitored, or the lists in the Device Monitor detail panes are blank.

9-11
Drive details
Windows
UNIX
12
The Drive Details screen lets you examine the all of the details of a specific drive in one
screen. This information is available in the Device Monitor but is not available in a
single screen. A user would need to use the scroll bar or rearrange columns in the
details pain to see all the available information. The Drive Details screen displays all
this information on a single screen.

9-12
Performing drive and robot diagnostics
Drive Diagnostics: Performs I/O to an available

tape in the NetBackup volume pool
Robot Diagnostics: Tape is moved, but no I/O is

performed
13
Media Manager drive and robot diagnostic functions enable you to execute and manage
drive and robot diagnostic tests. The diagnostic test steps are executed in an ordered
sequence to verify the functionality of hardware devices configured for use with
NetBackup. These tests help you to troubleshoot robotic library or tape drive problems.
Before running drive diagnostics, use the available_media script to confirm that
there is an Available tape in the NetBackup volume pool.
To execute diagnostic tests within the NetBackup Administration Console:
1. Select Media and Device Management > Devices > Drives or select Media and
Device Management > Devices > Robots.
2. Select a device or a robot.
3. Select Actions > Drive Diagnostics or Actions > Robot Diagnostics.
In either the Drive Diagnostics or Robot Diagnostics dialog box, click Start to run the
drive or robot diagnostic tests. The results of the tests are displayed in the Results pane.
Note that drive diagnostics will perform I/O to an available tape (a tape without data
already on it) in the NetBackup volume pool.
Robot diagnostics will not perform any I/O, however will move tapes from slots to
drives, and back.

9-13
Monitoring device cleanings
Clean your tape • Do not overclean or underclean.

drives! • Follow the OEM’s recommendations.
Media Manager Media manager tracks the use of a cleaning

monitoring tape by the number of uses.
14
Routine maintenance of devices includes cleaning drives to ensure that they continue to
write to and read from the media properly. Although cleaning is important, be careful to
neither overclean nor underclean your drives. Undercleaning can result in excess
residue on the tape drive heads. Overcleaning can cause undue wear on the drive
heads. Either can result in data loss.
Refer to the drive manufacturer’s recommended cleaning schedule. You can establish a
cleaning schedule through NetBackup accordingly.
Using a cleaning tape
Drive cleaning is accomplished using cleaning tapes. Media Manager tracks the usage of
a cleaning tape by the number of times it has been used. For each cleaning tape, you
can specify the number of cleanings that remain. You can change the number of
cleanings at any time in Media Manager. Each time the tape is used, that number
decreases by one. When the number of cleanings reaches zero, Media Manager stops
using the cleaning tape.
To configure a cleaning tape:
1. Specify the Media type setting for the cleaning tape’s designation (such as
DLT_cleaning_tape).
Note: The cleaning tape is automatically assigned to the None volume pool.
2. Set the number of cleanings. (The default setting is 25.)

9-14
Device cleaning methods
Robot controlled
• Also called hardware-based, library-based, or auto cleaning.
• Robot determines when drive is cleaned (for supported robots).
TapeAlert
TapeAlert notifies Media Manager that the drive needs to be cleaned.
Frequency-based
The drive is cleaned according to an administrator-defined frequency.
Manual (operator-initiated)
• Manually invoked in the Device Monitor or with tpclean.
• Use robotic device controls directly.
15
This slide shows the various methods you can use to perform drive cleaning.
• Robotic controlled cleaning: Some robotic tape libraries have automatic drive
cleaning functionality. This is also referred to as hardware-based cleaning, library-
based cleaning, or auto-cleaning.
With robotic automatic cleaning, the tape drive sends an alert to the robot, notifying
the robot that the drive requires cleaning. After a backup tape is unmounted, the
robot mounts the cleaning tape and cleans the drive. NetBackup is not involved in
this process.
• TapeAlert: Another method of automatic cleaning uses the TapeAlert feature, which
allows reactive cleaning for some drive types that support the TapeAlert capability.
This method is also called reactive cleaning.
Note: Hardware-based cleaning is not coordinated with NetBackup without
TapeAlert. Because TapeAlert and robot-controlled cleaning provide the same type of
cleaning, Veritas recommends disabling library-based cleaning when using TapeAlert.
• Frequency-based cleaning: One NetBackup drive setting is the cleaning frequency:
the number of hours a drive is used between drive cleanings. Refer to the drive
manufacturer’s recommended cleaning frequency before setting this value.
NetBackup updates the total mount time for a drive each time a tape is unmounted
(only for time when the media is actually assigned to a process, and is in use). If the
drive is in a robot that supports cleaning, and a cleaning tape is configured in that
robot, cleaning occurs when the accumulated mount time exceeds the cleaning
frequency.

9-15
Media Manager cleans the drive immediately after the unmount. Drive cleaning
never causes an unmount in the middle of an active backup. The mount time is reset
after the drive is cleaned. The cleaning frequency value remains the same.
A cleaning can occur during a backup if the end of tape is reached before the backup
completes and a cleaning is due. After unmounting the first tape, Media Manager
cleans the drive before proceeding with the backup on a second tape.
Using TapeAlert with frequency-based cleaning ensures that a drive is cleaned at
least every x hours, depending on the setting for the cleaning frequency. In addition,
the drive can be cleaned sooner if either the CLEAN_NOW or the CLEAN_PERIODIC
TapeAlert flag is set by the drive.
• Manual drive cleaning
Manual cleaning is also known as operator-initiated cleaning. You can manually clean
a drive regardless of the cleaning frequency and accumulated mount time. Stand-
alone and robotic drives can be cleaned if a cleaning tape of the correct media type
and residence for the drive is configured in NetBackup.
Alternatively, you can manually clean a robotic drive according to the manufacturer’s
instructions. Manual cleaning can involve using the menu buttons on the front of the
device to instruct the robot to load a cleaning tape and perform drive cleaning. Check
the details for your specific robot.
To perform drive cleaning functions in the NetBackup Administration Console, select
Media and Device Management > Device Monitor. In the Drive status pane, select a
drive. Select Actions > Drive Cleaning. The Drive Cleaning submenu choices enable
you to perform the following functions:
• Clean Now: Start an operator-initiated cleaning of the selected drive, regardless
of the cleaning frequency or accumulated mount time. If the drive is a stand-
alone drive, it must contain a cleaning tape and a mount request is issued. Clean
Now resets the mount time to zero.
• Reset Mount Time: Reset the mount time for the selected drive to zero, even if
a cleaning was not performed.
• Set Cleaning Frequency: Set the desired number of mount hours between each
drive cleaning.
Alternatively, to perform drive cleaning using the command line, the tpclean
command enables you to monitor Media Manager tape drive usage and optionally
configure tape drives to be automatically cleaned (except drives in ACS, ODL, or TLH
robots, or QIC drives).

9-16
Topic: Monitoring media and media states
After completing this topic, you will be able to perform media

management, including moving, ejecting, changing, sharing, erasing, and
deleting volumes.
17
After completing this topic, you will be able to perform media management, including
moving, ejecting, changing, sharing, erasing, and deleting volumes.

9-17
Comparing volume expiration and image retention
Volume expiration
• How long you want to use the physical media.
• Optional setting that limits the lifespan of the physical media.
• Normally based on vendor recommendations or departmental
policies.
Image retention
• How long the image is available for restores.
• Required setting on backup policy schedules
• Typically based on the restore service level agreement (SLA) for
the data.
18
There are two distinct types of expiration in NetBackup: volume expiration and image
expiration. Likewise, the volume expiration date and the image expiration date have
distinct meanings.
Volume expiration
You can change the expiration date for volumes. The volume expiration date refers to
the age of the tape media and is the time at which the tape is considered too old to be
reliable. When the expiration date has passed, a volume can still be read but is not
mounted for a write.
The volume expiration date is not the same as the retention period for the backup data
(images) on the volume. The volume expiration date refers only to the physical
expiration of the volume and is independent of the backup data written on the volume.
Image retention
Image retention is the period for which NetBackup preserves a backup image. The
image expiration date is the time at which NetBackup no longer protects this data from
being overwritten and can purge metadata about the image from its database.

9-18
Configuring volume expiration and image retention
Volume expiration Image retention
(on media) (in policy schedule)
19
This slide is a reminder that the volume expiration date is set in the Expiration date
section of the Change Volumes dialog box. This slide also shows that the retention
period is displayed in the Schedule section of the policy.

9-19
Media life cycle (1 of 5): Available tape
ABC123
EOM
Image
NetBackup database
database
Valid Ret Volume Media Header
Media ID Assigned .f file
Images Level Pool State info
ABC123 N 0 --- scratch AVAILABLE
20
When a backup job is initiated, NetBackup selects the required piece of media based on
the parameters of that specific backup job. The policy and schedule dictate the required
storage unit, volume pool, and retention level. The actual media selected is discussed
elsewhere in this lesson.
The example on this and the following slides shows the life cycle of a tape—from
unassigned, to assigned, and then unassigned again.
In this example, a backup job is requesting a tape from the servers pool with a two-
week retention. If a tape is not available in the servers pool that meets all the necessary
criteria, NetBackup will attempt to move a tape from the scratch pool to the servers
pool for use in the backup.
Also, this example shows a tape that has already been labelled with media ID ABC123.
Following the label (sometimes known as the media header), is a mark that shows the
logical end of the tape. This is sometimes known as an End of Data (EOD) or End of
Media (EOM) mark, and indicates to any tape drive reading the tape that no more
pertinent data exists past this mark, even though it is not the physical end of the tape.
When the tape is first added to NetBackup, an entry is made in the EMM database. The
entry includes the media ID of the tape. Initially, the tape is unassigned and the media
state is AVAILABLE.

9-20
Media life cycle (2 of 5): Backups written to tape
ABC123
Image1 Image2 Image3
EOM
EOM
EOM
EOF
EOF
EOF
BH
BH
BH
2 week retention 2 week retention 2 week retention
BH = Backup Header (metadata)

Image
NetBackup database
database
Images Level Pool State Info
info
ABC123 N 0 --- scratch AVAILABLE
Y 1 2 wk servers ACTIVE Image1 Image1.f
21
After the first backup is written to the tape, the NetBackup database is updated so that:
• The tape is now assigned, and there is one valid image.
• The retention level of the backup is set, in this case to two weeks. The default is not
to mix retention periods on media.
• The volume pool is set to servers.
• The media state is ACTIVE.

The NBDB and Image database are also updated to contain the metadata about the
backup job. These are represented by Image1 and Image1.f in the slide. Image1 and
Image1.f are sample names. The actual name of the image is stored in the format of
policyname_ctime_schedule, where ctime is the creation time of the image.
Before a backup is written, a NetBackup backup header (BH) is placed on the tape. At
the end of a backup, an End of File (EOF) marker is written. If NetBackup is not writing
further data in this session, an End of Media (EOM) marker is also written, to indicate
the logical end point of this tape.
When the second image is written, the EOM marker is overwritten by the backup
header of the next image, and a new EOM marker will be written at the end of the
backup. The NetBackup database now indicates there are two images on the tape. This
same process occurs for the third image written to the tape.

9-21
Media life cycle (3 of 5): Tape becomes full
ABC123
Image1 9.46
Image2 Image3
EOF
EOT
EOF
EOF
BH
BH
BH
End of Tape Marker

Image
NetBackup database
database
ABC123 N
Y 0
3 2---
wk servers
scratch AVAILABLE
FULL
Y 1 2 wk servers FULL
ACTIVE Image1
Image1.f Image1.f
Image1
YY 2 2 wk servers FULL
ACTIVE Image2
Image2.f Image2.f
Image2
Y 3 2 wk servers ACTIVE
FULL Image3 Image3.f
22
An End of Tape (EOT) indicates that the physical end of a tape is reached
In this example, the third backup is written to the end of tape (EOT). In most cases, the
backup image will not fit exactly on the tape, and the third backup may actually be
continued on further media.
At this point, the media state is now set to FULL in NetBackup.

9-22
Media life cycle (4 of 5): Images expire
ABC123
EOF
EOT
EOF
EOF
BH
BH
BH
Image
NetBackup database
database
ABC123 Y 3
2
1
0 2 wk servers FULL
Y 2 wk servers FULL Image1 Image1.f
2 weeks pass Images expire
23
The image cleanup job determines which images have met their retention period and
are expired. Expired images are removed from the NetBackup databases.
In this example, two weeks have passed from when the first image was written. At that
point, Image1 has met its retention level and is ready to be expired. Note that after
Image1 expires, NetBackup no longer records information about that backup in the
NetBackup database, so restores of that backup are no longer possible without further
actions (such as an Import operation, discussed elsewhere in this lesson). Although
Image1 is removed from the database, the data for Image1 still physically resides on the
tape. No action is automatically performed to physically erase the data.

Depending on when Image2 and Image3 were written, they may also be expired and
removed during the initial image cleanup job or during a subsequent image cleanup job.
For example, if the backups were each written one day apart, Image2 will expire a day
after Image1’s backup expires, and Image3 will expire two days later. Each time images
expire, the NetBackup database is updated to reflect the number of valid images that
are still being tracked on this tape.
When Image1 expires, if Image2 and Image3 are still on the tape, the free space made
available by Image1 is not available for use. If that tape was full, only when all images
are expired is the tape made available. If the tape is not full, new backups will only be
written after the End of Media mark.

9-23
Media life cycle (5 of 5): Tape becomes available
ABC123
EOF
EOT
EOF
EOF
BH
BH
BH
Image
NetBackup database
database
ABC123 N
Y 0 2---
wk scratch
servers AVAILABLE
FULL
Housekeeping takes place during image cleanup

24
After all the images are expired and the NetBackup database indicates there are no
longer any valid images associated with the media ID, the media is ready to become
unassigned, and have its media state set to AVAILABLE. This occurs during the
NetBackup image cleanup. Image cleanup occurs after each successful backup session
(during any short period of backup inactivity after backups have run). However, even if
there is no inactivity, due to a busy backup environment, a cleanup interval occurs every
12 hours, by default. This value is set in the NetBackup master server host properties >
Clean-up > Image cleanup interval.
If the media originally came from the scratch pool, then it will be returned to that pool.
The media life cycle process begins again.
Even though the data on the tape is expired and is no longer being tracked in the
NetBackup catalogs, the actual data on the tape is not erased. The physical data
continues to exist on the tape. If the tape has not been reassigned, the data can be
imported using NetBackup, if necessary.
If the media has been reassigned and rewritten, or manually re-labeled, then the old
data will be overwritten by new backup images. At this point, with third-party software
and tools it may be possible to extract the old data from the tape, but this is outside the
scope of what is possible with NetBackup. The data is considered unrecoverable.

9-24
Media states
Visualization Media state Reason for the state
AVAILABLE Unassigned tape (NetBackup is unaware of any images).
ACTIVE Assigned tape (NetBackup is aware of at least one, unexpired image).
FULL Assigned tape, and End of Tape marker was reached.
S SUSPENDED Assigned tape, and no more images can be appended.
Cannot append images due to a invalid data format, NetBackup catalog

F FROZEN
format, or multiple tape errors.
I Assigned tape containing imported images previously expired, or from

IMPORTED
another NetBackup domain. Cannot append images.
25
All volumes have a media state, which changes based on a number of factors, such as
how much the volume is used or the type of backup written to it.
The most common media states are:
• AVAILABLE indicates that no active backup images are currently associated with this
tape. This can happen if:
• This is a new tape; NetBackup has never written data to it.
• NetBackup has used this tape, but all images on the tape have met their
retention and expired automatically.

• All of the images on the tape have been manually expired.
• ACTIVE media currently contains at least one unexpired image.
• FULL is set when end of tape (EOT) is encountered during a backup or archive. This
tape is not available for use until all backup images on the media have expired.
• SUSPENDED is set manually by an Administrator in the NetBackup Administration
Console or by using the bpmedia command. The volume is temporarily write-
protected against additional NetBackup use. You cannot use a suspended volume for
backups until it is either manually unsuspended, or until retention periods for all
backups on it have expired.

9-25
(in which case the state changes from SUSPENDED to AVAILABLE). A suspended
volume is available for restores for valid, unexpired backup images.
• FROZEN media state can be caused by a number of conditions:
• A format issue (not a NetBackup tape, or a bad tape label)
• Too many errors (3 or more errors in a 12 hour period by default)
• Manually using the command bpmedia
Use the bpmedia command, the NetBackup Administration Console, or the
OpsCenter user interface to freeze a volume and prevent the volume from being
reassigned and overwritten. The volume is write-protected and the volume does not
expire, even if the retention periods for all backups on the volume have expired.
Like suspended volumes, a frozen volume is not mounted for backups or archives,
but you can restore from a frozen volume. However, frozen volumes are never made
available automatically. Either manually expire all images on the tape using
bpexpdate –m –d 0 or use bpmedia.
Normally, NetBackup does not overwrite formatted volumes with media headers not
recognized by NetBackup. However , if ALLOW_MEDIA_OVERWRITE is configured,
formats such as tar or cpio, can be overwritten and the media can be reused
immediately. These settings are found in the NetBackup server host properties
under the Media tab.
• IMPORTED media state is set if the images on this volume have been added through
the import process. The images on this volume are available for restore only. The
volume cannot be used for backup or archive until the last image expires. Imported
images are retained for one full retention period (as recorded in the image header)
from the date of import.
Other media-related information

The following lists additional media-related information that is available.
• MPX_MEDIA is a media state that indicates that this tape contains multiplexed
backups. MPX can be associated with tapes that are Active, Full, or Imported.
Backups that use the same storage unit, volume pool and retention can be
multiplexed to the same volume, only if allowed through policy and storage unit
multiplexing settings.
• WORM is a media state that indicates that this tape is a Write-Once-Read-Many
(WORM) volume. WORM media is used to protect key data from unwanted
modification or tampering, or to meet compliance regulations. For more information
on WORM media, see the NetBackup Administrator’s Guide.
• Multi-Retlev refers to multiple Retention Level, and is a media state that indicates
that the volume contains backups of more than one retention level.
• BE is a media state that indicates that the volume contains Backup Exec images.

9-26
Determining media and volume status
Available media Use the available_media script
NetBackup
• Use Media and Device Management > Media
Administration • Use NetBackup Management > Reports
Console
• Use Reports > Media Reports > Media State

OpsCenter • Use Monitor > Media
Use media commands: bpmedialist, bpimmedia, bperror, bpimagelist,

The command line nbemmcmd, and vmquery
27
NetBackup provides various reporting methods by which you can determine the status
of media. Use any of the following interfaces to determine the media status.
• Available media: The available_media script reports on all media in the environment
that is usable by NetBackup. This report also indicates the current media states.
• The NetBackup Administration Console: When you use the NetBackup
Administration Console to determine status information, you use the Media and
Device Management > Media and the NetBackup Management > Reports
interfaces.
• OpsCenter: OpsCenter enables the administrator to view, manage and report on

NetBackup media.
• The command line: Commands used to display volume-related and image-related
information and to perform volume configuration tasks are listed on the slide.
• The text-menu interface (UNIX only): Use the bpadm command to access the
bpadm utility. Select the r option for reports, and then select the m option for
media. You can now choose from six different media-related reports.

9-27
The available_media script
# available_media
media media robot robot robot side/ ret size status
ID type type # slot face level KBytes
----------------------------------------------------------------------------
NetBackup pool
E01001 HCART2 TLD 0 1 - 1 825174 ACTIVE

E01003 HCART2 TLD 0 3 - 1 5776250 SUSPENDED
None pool
CLN101 HC_CLN TLD 0 22 - - - AVAILABLE

CLN102 HC_CLN TLD 0 22 - - - AVAILABLE
scratch_pool pool
E01008 HCART2 TLD 0 8 - - - AVAILABLE
server_tapes pool

E01005 HCART2 TLD 0 5 - 3 8202646 FULL
E01004 HCART2 TLD 0 4 - 3 8202686 FULL/FROZEN
UNIX: /usr/openv/netbackup/bin/goodies/available_media
Windows: install_path\NetBackup\bin\goodies\available_media.cmd
28
Located in the goodies directory, the available_media script lists all the media IDs that
are available on the server where you run the script. Within the report, the
available_media script displays the status of each piece of media.
• UNIX: /usr/openv/netbackup/bin/goodies/available_media
• Windows:
install_path\NetBackup\bin\goodies\available_media.cmd
This script can be invoked from any administrative server.
Note: An asterisk (*) in the ret level column indicates the media has images written to it
with multiple retention periods. The default for NetBackup is one retention period per
media.

9-28
Media and Device Management > Media
Refresh data that

is displayed
29
Using the Media interface of the NetBackup Administration Console, you can obtain
information about your media. This screen shot shows the volume catalog. Use it to
quickly determine if a piece of media is used. If the Time Assigned field for a piece of
media is empty, then the piece of media is not currently in use and would be reported
as Available in the available_media script. If the administration console has been
running for a while, the information displayed in the details may be stale. Use the
refresh button to refresh the contents.

9-29
Tape reports
Example of the Tape

Summary report
30
You can run various reports from the NetBackup Administration Console and from the
command line to gather information about media used in the NetBackup environment.
To access the media reports using the NetBackup Administration Console, expand
NetBackup Management and expand Reports > Tape Reports. Click the report you want
to generate.
The example on the slide shows a Tape Summary Report, which summarizes active and
non-active volumes for the specified media owner (server) according to expiration date.
It also shows how many volumes are at each retention level. In verbose mode, the
report shows each media ID and the expiration date.

Tape reports can be run on using command line, for commands generally located in the
/usr/openv/netbackup/bin/admincmd directory (UNIX) or in the
install_path\NetBackup\bin\admincmd directory (Windows). For full
details about each command, see the NetBackup Commands Reference Guide.
• Tape Reports > Tape Lists shows status information for volumes that have been
allocated for backups.
bpmedialist -mlist -U
• Tape Reports > Tape Contents shows the contents of a volume as read directly from
the media header and backup headers. This report lists the backup IDs (not each
individual file) that are on a single volume.
bpmedialist -mcontents -m media_id -U

9-30
• Media Logs shows media errors or informational messages that are recorded in the
NetBackup error catalog. This information is a subset of the All Log Entries report.
bperror -media -U
• Tape Reports > Tape Logs is similar to Media Log, but only for tapes.
bperror -tape -U
• Tape Reports > Tape Summary summarizes active and non-active volumes for the
specified server according to the expiration date. This report also shows the number
of volumes at each retention level, and the state (ACTIVE, FULL, SUSPENDED, or
FROZEN) of the media. In verbose mode, the report shows each media ID and its
expiration date.
bpmedialist -summary -v
• Tape Reports > Tape Written identifies volumes that were used for backups within
the specified period. This report does not show volumes that were used for
NetBackup catalog backups or volumes that were used for duplication if the original
was created prior to the specified period.
bpimagelist -A [-media -d date -e date]
• Images-on-Media lists the contents of the media as recorded in the NetBackup
image catalog.
bpimmedia -L [-mediaid media_id]
• Tape Reports > Images on Tape is similar to the Images on Media report, but only
for images on tape.
bpimmedia -tape -L [-mediaid media_id]

9-31
Topic: Managing tapes
After completing this topic, you will be able to perform media

management, including moving, ejecting, changing, sharing, erasing, and
deleting volumes.
32
After completing this topic, you will be able to perform media management, including
moving, ejecting, changing, sharing, erasing, and deleting volumes.

9-32
Overriding media state using the Administration Console
33
All volumes have a media state. The media state can change based on a number of
factors, such as how much the volume is used or the type of backup written to it.
NetBackup automatically controls the media state of a volume, but in some cases, you
can override the NetBackup setting.
You can override some media states using the NetBackup Administration Console. To do
so, expand Media and Device Management > Media. In the details pane, select a piece
of media and select Actions. From the Actions drop-down menu, select Freeze,
Unfreeze, Suspend, or Unsuspend. Media that is available (no time assigned) cannot
have it’s media state manually changed and attempts to freeze or suspend unassigned
media generates an error.

9-33
Additional methods for overriding media state
Before After How to Override the State
Use bpexpdate –m media_id –d 0
Active Available

Full Available
I
Imported Available
S • Wait for images to reach retention date, or
Suspended Available use bpexpdate –m media_id –d 0
S • Use bpmedia –m media_id –unsuspend
Suspended Active
• Use bpexpdate –m media_id –d 0
F
Frozen Available • Use bpmedia –m media_id –unfreeze
F (To prevent tapes with non-NetBackup data being marked Frozen, erase
Frozen Active the tapes or Allow media overwrite in the media server host property)
Caution: The bpexpdate commands can destroy backup data
34
When a tape has at least one unexpired backup image, it is said to be Assigned. New
images are appended to these assigned (active) tapes. When all of the images on the
tape have expired, the tape automatically unassigned by NetBackup at midnight.
You can override some media states using the bpexpdate and bpmedia commands.
If you wish to reuse a tape with images before they naturally expire, you can use the
bpexpdate command with the –m media_id option to select the tape, and –d 0
option to set the date for all backup images on the tape to expire immediately. This
command additionally de-assigns the tape, so it becomes immediately available, even if
the tape was suspended or frozen.

Caution: Use this command with caution because it deletes the backup metadata from
the images catalog, and it changes the media state to AVAILABLE.
More information on specific media states is provided here:
• Active / Full
These tapes are assigned and have unexpired backup images. After running
bpexpdate –m media_id –d 0, the backup images are removed from the
NetBackup catalog. Although the physical data is still on the tape, you must import
those images to get access to them. Refer to the Managing and Protecting the
NetBackup Catalog lesson for information on importing media.

9-34
• Imported
Imported tapes are tapes that had previously had images expire, or have come from
another NetBackup domain. In either case, NetBackup was not aware of the images
on the media, and an Import operation was performed to add them to the
configuration.
Running bpexpdate –m media_id –d 0 removes the images from the
NetBackup catalog, and once again makes the media available. Refer to the
Managing and Protecting the NetBackup Catalog lesson for information on
importing media.
• Suspended
The Suspended state only occurs when manually set by the administrator with the
bpmedia command, or with the NetBackup Vault product (which uses these
commands to suspend tapes). In either case, if you wait until the backup images on
the tape expire, then NetBackup will automatically de-assign the tape, and remove
the Suspended state from the tape. It is now available.
Running bpmedia –unsuspend –m media_id –h host will remove the
Suspended state from the tape, without affecting the data or backup images. In this
case, the tape will now be in an Active state. The host must be the media server the
tape has been assigned to. Use the bpmedialist command or Media > Media
Owner column to determine tape assignment.
Running bpexpdate –m media_id –d 0 will cause NetBackup to expire all
images and allow the tape to become available immediately.
• Frozen
The Frozen state occurs when manually set by the administrator, or when
NetBackup discovers a problem with the tape. This can happen after I/O read or
write errors, or when a tape previously thought to be empty has unrecognized

media formatting.
Running bpmedia –unfreeze –m media_id will remove the Frozen state
from the tape, without affecting the data or backup images. However, if the state
was caused by a problem such as I/O errors or formatting, and that problem isn’t
resolved, NetBackup may simply freeze the tape again when it is used.
To permanently resolve any issues, determine the cause of the problem by
examining the Tape Error Logs:
• If the problem was I/O errors on the tape, perform new backups.
• If the problem was I/O errors caused by other other hardware, unfreeze the tape
and attempt to reuse it.
• If the problem was caused by a formatting issue, such as tapes from other
vendors unrecognized by NetBackup, either re-label the tape (for example with
the bplabel command), or set the ALLOW_MEDIA_OVERWRITE media server
host property, which allows NetBackup to simply overwrite specific media
formats encountered.
9-35
Setting volume locations and properties
Move Change
Sets volume group (location) Modifies properties
• Volume expiration date

? • Maximum mounts
= • Volume pool
Eject Delete
Physically ejects tape from library, and Removes tape from configuration
sets volume group
• Must not contain valid backup
? images
• Used for removed, missing, or
corrupt tapes
36
There are various operations that you may want to perform on tape media:
• Move: Moving a tape involves changing the media’s volume group, which defines
where it physically resides. Note that this does not physically move the tape. It
simply allows the administrator to set and track the tape’s location.
• Eject: Ejecting a tape physically causes it to leave the library. This function does
require a tape library that supports an eject function with a media access port. You
can simultaneously set the volume group for the media, as when using the Move
function.
• Change: Changing media includes changing properties such as setting the tape’s
physical expiration date (when it no longer deemed to be good hardware used for
writing new backups), the volume pool the tape is in, or the maximum mounts (the
number of times it can be used).
• Delete: Deleting a tape is performed when a tape should no longer be tracked by
NetBackup, such as when it has been lost, or the data is corrupt and cannot be
restored from. Note that a tape must be made available (by expiring all images on
the tape) prior to deleting it.

9-36
Moving volume location
vmchange –res –v vol_group

37
To move a tape volume:

1. In the object tree pane of the NetBackup Administration Console, select Media and
Device Management > Media.
2. In the right pane, select one more volumes to perform the operation on.
3. Either right-click the desired volume and select Move, or highlight the desired
volumes and select Actions > Move from the menu bar.
If you select several media types in the volumes list, you see a Move Volumes dialog
box for each media type.

Elements in the Move Volumes dialog box:
• Volumes to move:
Shows the selected volumes on which the move operation will be performed.
• Volume is in a robotic library
This option is used if you are moving volumes into or out of a robot. Clear the check
box if the volume is to be made stand-alone. Check the box and fill in the associated
attributes if the volume should be registered in a robot.
• Device host: Select the device host for the robot from the pull-down menu. This
is the robot control host
• Robot: Select the robot into which you are moving the volumes from the pull-
down menu.

9-37
• Volume group
Select the group name from the pull-down menu if the volume is also changing
volume groups.
• First slot number
This field displays the first slot in the volume group to receive the volumes and is
only active if the Volume is in a robotic library check box is checked.
Note: If you are moving multiple volumes into a robot manually, NetBackup
assumes the volume slot assignments are consecutive starting from the first slot
number.
A real world move example even with functional barcode reading:
To move a volume from one robotic library to another library where both libraries are in
the same NetBackup domain, the order in which you run the inventories of the two
robots matters. Robotic inventory only “moves” known volumes into a robot that are
registered as stand-alone. If a volume with media id 0C0000 and barcode 0C0000L1, is
physically transferred from SLOT 7 of robot TLD(0) to slot 10 of TLD(1) and an inventory
of TLD(1) is performed without first running an inventory of TLD(0), then TLD(1)
inventory will fail because according to the NBDB, the tape, 0C0000, is in slot 7 of
TLD(0). By first running the inventory against TLD(0), the tape, 0C0000, is updated to
reflect that it is now stand-alone. This will allow the TLD(1) inventory to work properly
and again, modify the record in NBDB describing 0C0000 as now being in slot 10 of
TLD(1).
But, what happens if you cannot run an inventory against TLD(0) because it’s power
supply has broken (this being the reason you want to move this volume to TLD(1) so you
can perform the restore from the backup that is on this tape). You can take the tape
out of TLD(0) and place it into TLD(1) which is functional but since you cannot inventory
TLD(0) (no power), the record describing 0C0000 will still show as being in slot TLD(0) so
your attempts to inventory TLD(1) fail when the inventory sees the 0C0000L1 barcode
which is associated with that tape 0C0000.
The solution to this conundrum is MOVE. You can MOVE 0C0000 to STAND-ALONE
which simply updates the record in the NBDB describing 0C0000 so that it shows as not
being in any library. Then you can inventory TLD(1) which should now successfully
update 0C0000 to reflect that it is now in TLD(1).

9-38
Ejecting volumes
Library requires the

presence of
CAP/MAP/mailslot
vmchange –res –multi-eject
39
Ejection physically transfers media from slots within the robot to media access ports or
mail-slots, and additionally updated NetBackup to reflect the change of residence.
To eject a volume using the NetBackup Administration Console:
2. In the right pane, right-click the desired volume and select Eject Volumes From
Robot, or select the volumes and then select Actions > Eject Volumes From Robot
from the menu bar.

Generally, after the pre-checks for the eject are complete, the Media tab displays the
volumes that you selected to eject, and the Errors tab is empty. The eject may not be
possible because of an error or a hardware limitation. If an error occurs, the dialog box
is displayed with the Errors tab opened. Click Eject to execute the eject.
After clicking the Eject button, NetBackup moves ejected media to the media access
port (MAP), and a dialog box appears, stating “Remove ejected media from the media
access port. Do you wish to continue with the eject?” If multiple tapes were ejected and
not enough MAPs exist, you will need to remove the tapes from the MAP before
pressing Yes to continue. Leaving tapes in the MAP may cause errors that the MAP
already contains media, thus preventing further tapes from being ejected from the
library.

9-39
Changing volume attributes
vmchange
40
There may be times when you need to modify a volume that has already been
configured. For example, you may need to change the volume pool to which the volume
belongs, change the volume’s expiration date, or assign a media description to the
volume so you can easily locate the volume if you need to restore from it.
To change a volume attributes:
2. In the right pane, right-click the desired volume and select Change, or select the
desired volumes and select Edit > Change.
You can change the following attributes for your volumes:
• Maximum mounts
This option controls the number of times that the volume can be mounted. When a
volume reaches its maximum mounts, Media Manager considers this tape non-
writable and ignores it as a destination for further backup and duplication jobs.
However, the volume is still readable so can be used as a source for imports,
duplications and restores.
• If a cleaning tape is selected, this option will be greyed out.
• Do not change: Select this option to keep the current setting.
• Unlimited: Select this option to allow an unlimited number of mounts.
Unlimited is the default setting.

9-40
• Number: Select this option and type a number to set a specific number of
mounts. Entering 0 (zero; the default) is the same as selecting Unlimited.
• Expiration date
This option defines the expiration date for volumes. When a volume reaches its
expiration date, like with Maximum Mounts, Media Manager considers the volume
read-only and ignores it as a destination for further backup and duplication jobs but
is still readable so can be the source for import, duplication and restore jobs.
• Never: Select this option to set the expiration date to infinity.
• Date: Select this option and type a date and time (using a 24-hour clock format
MM/DD/YYYY hh:mm:ss) to define when you want to stop using the volumes.
• Description
Adding a description helps you identify a volume.
• Media description: Select this option and enter a short description in the
provided field to describe how the volumes are being used.
• Volume pool
Allows you to change the volume pool of any unassigned data storage media.
• New pool: Select this option and select a volume pool from the pull-down list to
specify the volume pool to which you want to assign the volumes.
• Number of cleanings remaining
Use this option to increase or decrease the number of uses remaining for a cleaning
volume.
• New count: Select this option and type a number to define the number of
cleanings remaining for the volumes.

9-41
Deleting volumes
vmdelete
42
Deleting a volume removes the record that describes the volume from the NetBackup
database (NBDB). This operation does nothing to any physical data that may be on the
tape. In order to delete the record describing the tape from the NBDB, the tape must
be AVAILABLE, that is, unassigned.
If the tape is assigned, you must first expire all copies of the backups that NetBackup
has a record of on that tape and allow the tape to be unassigned, for example with the
bpexpdate -m media_id -d 0 command. This command expires those copies
of images that reside on the tape and de-assigns the tape. Trying to delete an assigned
volume will result in the error message: “Cannot delete assigned volume”.
Some of the reasons you may want to delete a volume are:
• Unusable because of repeated media errors.
• Past its expiration date or has too many mounts and contains no relevant backups.
• Lost and you want to clean up the NetBackup database.
Note: Deleting a volume removes it’s entry from the NBDB so the eject operation
cannot be used to remove the volume. Either manually remove the volume from the
robot or eject the volume using the eject operation before deleting the volume from
NetBackup’s NBDB database.

9-42
Erasing and labeling volumes
Only available tapes can be erased of relabeled.
EOM
EOF
EOF
MH
BH
BH
Image1 Image2
Label: Rewrite new label.
EOM
EOM
EOF
EOF
MH
BH
BH
Image1 Image2
Long erase: Overwrite entire tape.
EOM
EOF
EOF
EOT
MH
BH
BH
Image1 Image2
bplabel Quick erase: Overwrite beginning of tape.
EOM
bplabel –erase –l
EOM
EOF
EOF
MH
BH
BH
Image1 Image2
bplabel -erase
43
There are various methods available to erase physical data on a tape in NetBackup.
Note that if a tape is assigned (contains unexpired backup images), NetBackup will not
allow you to erase the tape. You will need to wait until the images expire, or to manually
expire those images with the bpexpdate –m media_id -d 0 command.
For comparison, the slide uses an illustration of a tape with previously written data. The
data is shown faded because the images are expired in the NetBackup catalog. Although
the data physically exists on the tape, NetBackup considers this an unassigned tape.
• Label writes a new NetBackup media header label on the tape.

The command is: bplabel -m media_id -d density.
• Long erase rewinds the media and the data is overwritten with a known data
pattern. This is sometimes known as a SCSI long erase, or secure erase. A long erase
is a time-consuming operation and can take as long as two to three hours.
The command is: bplabel –erase –l -m media_id -d density.
• Quick erase rewinds the media and an erase gap is recorded on the media. The
format of this gap is drive dependent, and may be an EOM mark or a pattern the
drive does not recognize.
The command is: bplabel –erase -m media_id -d density.

9-43
What is media sharing?
• Media sharing enables multiple media

servers to write backup images to the
Media same tape.
server • The benefits of media sharing include:
– Reduced media costs
– Reduced vaulting costs
– Improved mount times
– Increased storage capacity
– No unintentional sharing of media between
Shared library
media servers and NDMP tape servers
and tapes NDMP
host
By default, media is not shared until you enable media sharing.
44
By default, assigned media is owned by a single media server. Only backup and
duplication jobs running on a the media server that owns the tape can append more
images to that tape. The media sharing feature in NetBackup enables tape media
sharing among any number of media servers and NDMP tape servers. Appending to
tape is no longer restricted to a single media server. This capability is included in the
base NetBackup product at no additional cost. The benefits of media sharing include:
• Reduced media costs by minimizing the number of required tapes
• Improved media utilization by minimizing the number of partially full tapes (media
that is not completely utilized)

• Reduced vaulting costs by consolidating duplications to few destination media,
without requiring data to be sent over the network
• Improved mount times because media does not need to be unloaded and loaded as
part of media handoff among media servers, and increased media life as a result of
reduced media wear and tear
• Increased storage capacity when there are fewer partially full tapes taking up slots in
a tape library, and reduced administrative overhead because scratch media is
injected less often

9-44
Enabling media sharing
For more granular control, create

server groups and configure policies
to use those server groups.
nbemmcmd –changesetting –unrestricted_sharing

45
Media sharing can be enabled by either of the following methods:

• Enable unrestricted media sharing for all media servers by either:
• Checking the box in the Master Server Properties dialog box, under Media.
• Execute the command nbemmcmd –changesetting –machinename
<master> -UNRESTRICTED_SHARING 0|1|no|yes
Although unrestricted media sharing is the simplest approach, it is very permissive,
allowing media servers and NDMP tape servers managed by the same master server
to share all media (share everything). This approach allows multiple media servers
to write a tape with incompatible block sizes. Media cataloged in the EMM database
shows UNRESTRICTED_SHARING_GROUP in the Server Group column within the
media records.
• Media Sharing Groups are an alternative unrestrictive sharing, instead using server
groups to allow logically (and physically) related groups of servers to share and own
media. By creating server groups, you gain more granular control over which media
servers can write to media. After server groups are configured, you configure a
policy to use a specific group of servers media sharing server group. The media
written by such policies is owned by the group instead of the individual media server
so any of the servers in that server group can write future backup and duplication
jobs to the media.

9-45
NetBackup volume selection example
Storage Unit: NBU1_LTO6_Robot0 Volume Pool: Win_Servers
Win_Servers Scratch
Active Available Available

a) Pool: Win_Servers a) Pool: Win_Servers a) Pool: SCRATCH
b) ACTIVE b) AVAILABLE b) AVAILABLE
c) In Robot0 NO c) In Robot0 NO c) In Robot0
d) Density: HCART3 d) Density: HCART3 d) Density: HCART3
e) Not over maximum # of e) Not over maximum # of e) Not over maximum # of
mounts or past the mounts or past the mounts or past the
expiration date expiration date expiration date
f) Correct retention level YES
YES NO
g) Owned by media server YES Load the media and perform Backup fails, error 96
NBU1 the backup.
46
A NetBackup backup request specifies a specific storage unit and volume pool, as
defined by the backup policy.
When media management receives the request, NetBackup selects a volume based on a
number of rules and priorities. In order:
1. Active volumes in the volume pool
NetBackup first searches the database for an active volume in the specified volume
pool. This volume must be in the library that is in the storage unit being used. The
volume must not have exceeded its maximum number of mounts nor its volume
expiration date (which are settable, volume specific attributes used by NetBackup to
determine when NetBackup can no longer write to the volume).
Additional criteria includes making sure that the retention level matches that of the
images that are already on the tape. Note that you can override this with the media
server host property > Media > Allow multiple retentions per media, however
Veritas does not recommend using this setting without understanding the
implications of mixed retention images on media.
Next, a volume will be selected that is owned by the media server. By default media
servers own any tapes they have previously written to, however you can override
this with the master server host property > Enable unrestricted media sharing for all
media servers, or with server media Server Groups.

9-46
2. Available volumes in the volume pool
If no active volumes are available, then available (empty) volumes in the volume
pool will be selected next. The same requirements apply, including being in the
correct library, of the correct density, and having not exceeded the maximum
mounts or expiration date.
Mixed retention and server ownership do not apply, since this is an available tape
that has no existing images, and has no media server owner.
3. Available volumes in the scratch pool
If no suitable available or active volumes exist in the required pool, and a scratch
pool has been configured, NetBackup searches for a tape from the scratch pool in
the storage unit that it can use (not exceeding maximum mounts or expiration
date) and if it finds one, reassigns the tape to the required pool. Media
management then issues a mount command to the robotic daemon or service
controlling the robot, and the volume is mounted. After the media has been
allocated and mounted, control is returned to NetBackup, and the media write
operation proceeds.
When choosing an active or available tape, if multiple candidates exist, the tape with
the least recent mount time is chosen. If no volumes are available, the backup job fails,
and NetBackup flags an error 96 for the backup status. The NetBackup administrator can
disable or manually configure media ownership.

9-47
Topic: Media- and device-related tips
After completing this topic, you will be able to identify tape device and
media reports.
48
After completing this topic, you will be able to identify tape device and media reports.

9-48
Physical media problems
Common physical problems
• Unreadable barcode labels

• Stretched, jammed, or broken tapes
• Erasure from exposure to strong electromagnetic fields
• Dirty tape drives
Destruction of media
• Data center fire

• Flood
• Other disaster
Single point of failure
• Make multiple copies of all backup images.
49
A common physical problem is unreadable bar code labels on your media. Inspect the
labels on your tapes for torn or worn labels and for signs of smearing, smudging, or
fading of the ink. Replace the labels as necessary.
Other physical media problems are stretched, jammed, or broken tapes. Tapes can be
erased when exposed to strong electrical fields, so ensure that your robotic tape library
is not located near such a field.
Drives that need cleaning can manifest media related problems.
If you encounter media problems that you cannot correct using NetBackup, physically
inspect the volume itself to check it for these or similar problems.
An additional media issue is that a volume can be completely destroyed. For example,
consider what can happen to a tape left inside your car on a hot summer afternoon.
To help circumvent potential physical media issues, it is recommended that you make
multiple copies of all crucial backup images using duplication, inline copies, or vaulting.

9-49
Reporting on tape devices

Robot properties and Devices > Robots tpconfig -d Manage > Devices >
characteristics scan –changer Robots
robtest
Drive properties and Devices > Drives tpconfig -d Monitor > Devices
characteristics Device Monitor vmoprcmd Manage > Devices >
scan –tape Drive
Device connectivity Devices > Topology
50
The table on this slide summarizes how to report on tape devices using the NetBackup
Administration Console, NetBackup commands, and OpsCenter.

9-50
Reporting on media

Available media Media and Device available_media Monitor > Media, filter
Management > Media, by Unassigned Media
Time Assigned and Valid
Images columns
Media in use NetBackup Management > bpmedialist Monitor > Media, filter
Reports > Tape Reports > bpimagelist by Assigned Media
Tape Written, Tape Lists
Problem and status NetBackup Management > bpmedialist Monitor > Media, filter
information Reports > Tape Reports > bpimmedia by Full Media, Frozen
Media Logs, Tape Media, Suspended
Summary bperror Media, or Other Media
bpimagelist Run Media Reports to
nbemmcmd identify media status
vmquery and problems.
51
The table on this slide summarizes how media can be managed using the NetBackup
Administration Console, NetBackup commands, and the OpsCenter Web console.

9-51
Changing media
Task Administration Console Command Line OpsCenter
Change media state Actions > Freeze, Unfreeze, bpmedia Monitor > Media
Suspend, Unsuspend
Move media Actions > Move vmchange

robtest > m
Eject media Actions > Eject volumes vmchange
Change volume attributes Actions > Change vmchange
Delete media Actions > Delete vmdelete
Erase media Actions > Label, Long bplabel

erase, Quick erase
52
The table on this slide summarizes the methods for changing media using the
NetBackup Administration Console, NetBackup commands, and the OpsCenter Web
console.

9-52
Lesson summary
• Key points
– In this lesson, you learned how to view and change robot and tape drive settings, including drive status, and
perform drive cleaning.
– You also learned to identify and monitor NetBackup media states, and understand NetBackup media selection
and lifecycle.
– Additionally, you learned how to perform media management, including moving, ejecting, changing, sharing,
erasing, and deleting volumes.
– Finally, you learned to perform drive and robot diagnostics, and identify tape device, media, and media
sharing reports.
– NetBackup Device Configuration Guide
– NetBackup for NDMP Administrator’s Guide
53

9-53
Lab 9: Managing Tape Storage
Lab objectives
• Viewing tape drive and robot configuration settings
• Using the Device Monitor to monitor and manage tape drives
• Managing media
• Running tape-based reports
• (Optional) Using the robtest utility
• (Optional) Running NetBackup reports from the command line
• (Optional) Media state management using the command line
54

9-54
What did you learn?
lesson.
55
current lesson.

9-55
Question: About valid media states
Which is not a valid media state?
A. FROZEN
B. SUSPENDED
C. FULL
D. EMPTY
56

9-56
Answer: About valid media states
Which is not a valid media state?
A. FROZEN
B. SUSPENDED
C. FULL
D. EMPTY
The correct answer is D. EMPTY is not a valid status. When a tape doesn’t have any NetBackup data on it, it is considered
AVAILABLE (in the available_media script) or ACTIVE without a time assigned (in most NetBackup media reports).
57

9-57
Question: Media sharing in NetBackup
What does media sharing mean in NetBackup?
A. More than one media server can append to the same tape.
B. More than one master server has the same tape in its catalog.
C. More than one backup application can write data to a tape.
D. Data from more than one client can be written to a tape.
58

9-58
Answer: Media sharing in NetBackup
What does media sharing mean in NetBackup?
A. More than one media server can append to the same tape.
B. More than one master server has the same tape in its catalog.
C. More than one backup application can write data to a tape.
D. Data from more than one client can be written to a tape.
The correct answer is A. However, media sharing must be enabled explicitly.
59

9-59
Question: Volumes and expiration dates
If a volume is past its expiration date or has reached its maximum number of mounts,
what is the expected behavior?
A. The tape is available for backups and restores.

B. The tape is available for backups, but not restores.
C. The tape is available for restores, but not backups.
D. The tape is not available for backups or restores.
60

9-60
Answer: Volumes and expiration dates
If a volume is past its expiration date or has reached its maximum number of mounts,
what is the expected behavior?
A. The tape is available for backups and restores.

B. The tape is available for backups, but not restores.
C. The tape is available for restores, but not backups.
D. The tape is not available for backups or restores.
61

9-61
End of presentation
9-62
Lesson 10: Performing Virtual Machines Backups
This is the “Performing Virtual Machines Backups” lesson in the “Veritas NetBackup 8.1:

10-1
Policies
This lesson is the tenth lesson in this course.


10-2
Lesson objectives
Topic Objective
Introduction to virtual machine Describe virtual machines and discuss support for virtual machines
backups in VMware.
Configuring VMware backups Configure VMware backups.
Performing and Monitoring VMware

Monitor VMware backup.
Backups

X-3
Topic: Introduction to virtual machine backups
After completing this topic, you will be able to describe virtual machines
and discuss support for virtual machines in VMware.
After completing this topic, you will be able to describe virtual machines and discuss
support for virtual machines in VMware.

10-4
Machine virtualization overview
• Using virtualization, a host server performs the job of multiple computers sharing the
physical host’s resources.
• Each virtual machine (VM):
– Runs its own operating system and applications
– Is encapsulated and isolated from other VMs
– Uses its own emulated resources (such as CPU,
disks, and network connection)
• The virtualization layer, or hypervisor, is software that enables virtual machines to use
the host’s physical resources.
• The hardware layer consists of the physical components of the host server, and is shared
across the running virtual machines.
• Review document NB_70_80_VE: Support for NetBackup in virtual environments
Virtual machines, sometimes referred to as VMs, enable the sharing of the underlying
physical machine resources between virtual machines, each running its own operating
system. The software layer providing the virtualization is called a virtual machine
monitor or hypervisor. A hypervisor can run on bare hardware (native VM) or on top of
an operating system (hosted VM). An example of a hypervisor running on bare hardware
is VMware ESX Server. An example of a hypervisor running on top of an operating
system is VMware Server and Workstation. In the case of Microsoft Hyper-V, the
hypervisor runs on a special version of the Windows operating system.
NetBackup support for virtual machines

VMs consist of a number of files, including the critical virtual hard disk file (VMDK in
VMware, and VHD or VHDX in Hyper-V), which contains the operating system and data
for that VM. Traditionally, backing up the virtual hard disk file enables you to easily
restore the VM but does not provide the ability to perform individual file restores.
Conversely, backing up files from the VM as a normal client prevents easily restoring the
full virtual hard drives in the case of disaster recovery. NetBackup provides the ability to
easily back up and restore the virtual hard disk, while alternatively allowing for granular,
individual file restore.
Review support details in document NB_70_80_VE: Support for NetBackup in virtual
environments, found online at
https://www.veritas.com/content/support/en_US/doc/NB_70_80_VE.

10-5
How Virtualization Works
Operating Operating Operating

system system system
Operating system Hypervisor
Hypervisor Control
Application
Instructions Instructions
Privileged instructions Privileged instructions
Processor memory management Processor memory management
Protected Protected Protected
Protected memory memory
memory memory
Virtual Virtual Virtual
Network NIC NIC NIC
Network
Storage storage storage storage
Storage
Physical machine stack Virtual machine stack
6
Modern CPUs have features built in for system protection. These protections keep
different programs from writing into each others’ memory regions. CPUs also have
privileged instructions: Instructions only executable by the operating system.
The structure of virtualization is to allow multiple operating systems to run on the same
set of CPUs. In order to allow multiple operating systems to run, the virtualization
mechanism has to properly handle privileged instruction execution.
There are different methods virtualization systems use to handle privileged instructions.
VMware and Hyper-V use virtualization features of the CPU: Intel VT and AMD-V. The
hypervisor signals the CPU that certain processes are virtual machines, and allows the
privileged instruction to execute. Prior to this CPU technology, the hypervisor
intercepted privileged calls and executed software to manage access to the privileged
instructions. This virtualization technology model is more efficient and reliable.
Citrix XenServer uses para-virtualization: the operating system is modified to
accommodate the privileged instruction execution.
The hypervisor virtualizes networks, network switching, interrupts, and disk storage.
A hypervisor control application manages and monitors the creation, operation, and
lifecycle of virtual machines. Often, this control application runs on a separate host, to
remotely and centrally manage the virtualization servers.

10-6
Supported NetBackup virtual machine backup solutions
VM backup; Single-pass Single-pass

Virtual machine File system NetBackup
Intelligent backup; file and integrated
technology backup Accelerator
policy full VM restore application backup*
VMware vSphere ✓ ✓ ✓ ✓ ✓
Microsoft Hyper-V ✓ ✓ ✓ ✓
RedHat Enterprise
Virtualization ✓
Citrix XenServer ✓
Solaris zones ✓
Oracle Solaris
virtualization ✓
* Supported for Microsoft SQL, Exchange, and SharePoint 7
NetBackup supports a number of host virtualization solutions.

VMware and Microsoft Hyper-V are two of the most feature rich host virtualization
platforms in the market, and NetBackup is highly integrated with these solutions. As
well as supporting backup and recovery for both files and full virtual machines,
NetBackup also supports single-pass backups of virtual machines that support individual
file restore as well. These platforms are also supported with dedicated policy types
(VMware and Hyper-V) that provide virtualization specific features and options.
Additionally, NetBackup Accelerator is supported for both VMware and Hyper-V for
faster backups using block change tracking features.

Although NetBackup also supports other virtualization platforms, such as RedHat
Enterprise Virtualization (RHEV), Citrix XenServer, Solaris zones, and Oracle Solaris
virtualization, the feature sets are more similar to standard backup policies. Technical
articles and best practices exist for these virtualization solutions.

10-7
Understanding the virtual data center implementation
NetBackup infrastructure Virtualization infrastructure

Master Media servers VM server VM server
server
Hypervisor
control system
SAN
Control API
CLI
Web Interface
Storage
Cloud
orchestration
Virtualization
Web Client
The degree of virtualization, virtualization controls, and management varies widely

across enterprises. NetBackup includes features that are flexible in order to
accommodate most implementations.
The solutions for VMware and Hyper-V leverage features built into the hypervisor
control layer. For VMware environments, NetBackup uses the VMware API for data
protection. For Hyper-V environments, NetBackup uses Windows Management
Instrumentation for Windows Server 2016, and a host of provided features.
Veritas uses the capabilities provided by the hypervisor supplier to develop VM-specific
backup solutions. There are limitations and requirements, based on the software and
the environment. For example, in some cases the guest (VM) operating system may
need to have the NetBackup client installed to allow for advanced backup and recovery
features, such as one-pass VMware backups that simultaneously allow for granular
application recovery.
The specific architecture used in a virtual environment should be well understood.
Veritas solutions support a subset of many varieties of virtualization storage and guest
operating system architectures. Be sure to examine and evaluate the support and
limitations of both the virtualization vendor and the Veritas NetBackup solution in
designing your backup strategy for virtual environments.

10-8
Overview of NetBackup support for VMware vSphere and
Microsoft Hyper-V
Feature VMware vSphere Microsoft Hyper-V
Single-pass backups with full VM or file-level restore Yes Yes
Intelligent Policy with VM query builder VMware policy type Hyper-V policy type
Block-level incremental backups Using CBT Using WMI

NetBackup Accelerator backups Starting in NetBackup 7.7 Starting in NetBackup 8.0
Allows Instant Recovery Yes No

Uses snapshot for consistency and to keep VMs fully
Yes Yes
available
Back up VMs that are powered off Yes Yes
Web client integration support vSphere Web client SCVMM

Supported with prerequisite
Off-host backups of VMs Supported with VADP
steps
NetBackup support for VMware vSphere and Microsoft Hyper-V are summarized in the
table on the slide.
Both products are supported with full VM recovery, or individual file and folder level
restores, from single-pass backups performed by NetBackup. Both VMware and Hyper-V
policy types exist, that include automatic VM selection using a query builder, as well as
simplification of VM-specific backup configuration. Settings exist to limit and control
backup impact on the environment, to ensure performance is not adversely affected.
Full and incremental backups are supported, including block-level incremental backups
(BLIB) that avoid backing up unused space. BLIB is supported with VMware Change
Block Tracking (CBT) and Hyper-V Windows Management Instrumentation (WMI).
NetBackup for VMware also supported application-aware single-pass backups for
granular recovery of Microsoft Exchange, and SharePoint, and provide log truncation for
Microsoft SQL and Exchange. NetBackup for VMware also supports instant virtual
machine recovery, which is discussed in more detail in the Performing Virtual Machine
Restores lesson.
Off-host backups of VMs are supported in VMware using VMware vSphere Storage APIs
– Data Protection (VADP), reducing processing load on the VM server, and preventing
the need to install a NetBackup client on the VMs. Hyper-V also supports some off-host
/ alternate client backups, but requires some additional configuration steps, as provided
in the documentation.
Centralized management and web consoles are supported, which include VMware
vSphere web client, vCenter servers, and the Hyper-V System Center Virtual Machine
Manager (SCVMM).

10-9
Topic: Configuring VMware backups
After completing this topic, you will be able to configure VMware backups.
After completing this topic, you will be able to configure VMware backups.

10-10
NetBackup for VMware components
Component Description
• Sometimes referred to as a VM
Virtual machine • Configured as a NetBackup client in the NetBackup policy
• Does not require the NetBackup client software to be installed
ESXi server Presents a virtualized hardware environment to multiple VMs
Datastore VMware storage containing the virtual machine data for the ESX servers
vCenter server Coordinates many ESX servers and can migrate VMs between ESX servers
• A NetBackup host that helps perform backups on behalf of VMs
Backup host • Has operating system restrictions, with the NetBackup client installed
• Requires access to the VMware datastore
• Used for the automatic selection of VMs for backup
Discovery host • Can be any host supported for NetBackup server software
• Can be the same as the backup host
• Reads and writes backup data
Backup media server
• Can operate as the backup host
NetBackup client Only required for direct file restore and integrated application backup
11
The slide lists VMware components and components used by NetBackup when backing
up VMware. The first four components list VMware servers and components, and the
bottom four components list NetBackup components.
The VMware vCenter server is not required for NetBackup to perform VMware virtual
machine backups; however, certain features may not be available or alternate
configurations may need to be used.
The VMware backup host has certain operating system restrictions. These are discussed
on the following slide.
Note: The VMware backup host was referred to as the VMware backup proxy server in
some prior releases.
To perform backups that enable full VM and file-level recovery, the NetBackup client
does not need to be installed in the VM.
The NetBackup client needs to be installed in the following circumstances:
• Performing individual file restores directly to the virtual machine
• Performing Application backups with a VMware backup policy

10-11
The VMware and NetBackup environment
Master Media NetBackup vCenter ESX

server* server* appliance* LAN server servers
LAN backup option
(encryption optional)
NetBackup
client
SAN backup option SAN

SAN
Backup
infrastructure
Datastore
(VMDK files)
* Possible VMware backup hosts 12
The VMware backup host has operating system restrictions:

• NetBackup servers or clients running a supported Windows operating system
• Starting in NetBackup 7.5.0.2, NetBackup appliances with firmware 2.5 or later
• Starting in NetBackup 7.5.0.3, certain versions of specific Linux platforms
Review the latest NetBackup for VMware documentation, for the latest information.
Note: For more efficient backups, Veritas recommends using the NetBackup media
server used to back up a VMware-based VM as the VMware backup host.

There are a number of mechanisms that a backup host can use to access the data of a
virtual machine that is being protected. Although the slide shows two, here is a
summary of the types of access mechanisms that are available:
• Local area network (LAN) access to datastore, where the backup host accesses the
VMware datastore using the ESX servers, and the datastore data travels over the
TCP/IP network. In VMware this is referred to as NBD (network block device) or
NBDSSL (encrypted).
• Storage area network (SAN) access to datastore, where the backup host accesses
the VMware datastore directly over the SAN, normally with improved performance
and less impact on the ESX servers.

10-12
• HotAdd transport creates a linked-clone virtual machine and uses the clone’s virtual
disks for backup. HotAdd is a VMware feature where devices, such as SCSI disks, can
be added “hot” while a virtual machine is running. An example of using HotAdd for
backups would be creating a Windows-based virtual NetBackup media server to act
as the backup host for the other VM’s in that datastore.
For more information about identifying VDDK/NBU mapping and understand backup
host limitations, refer to Article 000010289: How to Identify vStorage/vADP
Environment Support, found online at http://www.veritas.com/docs/100003956.

10-13
NetBackup for VMware backup process example
Step Action VMware ESX
VMware backup server
host and LAN
NetBackup initiates a NetBackup media
1 VMware snapshot. server
The NetBackup media
2 server writes data to
SAN/iSCSI
the storage unit. Datastore
2
Backup (VMDK
When the backup storage files)
3 completes, the
snapshot is deleted. VMDK 1 Snapshot
Snapshot 3 VMDK.1
deleted
14
The process within NetBackup for VMware-based backups follows these general steps:
1. The NetBackup master server starts the backup and initiates a VMware snapshot by
communicating with the VMware server. Note that in VMware, the snapshot causes
the original VM image – represented on the slide as VMDK – to become static. A new
VM image file – represented on the slide as VMDK.1 – continues to record new
data.
2. The VMware backup host (in many cases the Windows media server) reads the
static VMDK files (represented on the slide as VMDK), maps their contents using the
vStorage APIs to index individual files and ensure only used space is being written,
and writes the backup directly to disk or tape.
3. After the backup completes successfully, the VMware snapshot is deleted. On the
slide, the changes recorded in the VMDK.1 VM file are rolled into the static data
held by the VMDK VM file. Note that by default NetBackup will only remove previous
snapshots created by NetBackup, and will not modify any other VMware snapshots
in the environment.

10-14
NetBackup for VMware configuration overview
VMware 1. Install VMware Tools 2. Install vCenter server

configuration on VMs (optional)
2. Install 3. Add 4. Add

1. Add 5. Create
NetBackup NetBackup VMware VMware
Enterprise NetBackup
client on backup host credentials
configuration Client
VMware to to
policies for
license VMware
backup host NetBackup NetBackup
As described in the NetBackup for

VMware Administrator’s Guide
15
This slide shows an overview of the VMware and NetBackup configuration required to
create VMware backups managed by NetBackup. These steps are discussed in the
NetBackup for VMware Administrator’s Guide, and are shown in more detail in the
following slides.
VMware configuration
The VMware configuration is not based on the NetBackup environment, and the
VMware documentation should be used for all VMware specific installation and
configuration.
The VMware Tools package is often installed on virtual machines, and does enable
NetBackup to perform backups of virtual machines without the NetBackup client
software installed on the VM. Although not technically required, issues like crash-
consistent backups may occur.
Additionally, NetBackup integrates with VMware components such as vCenter and
vSphere, as is discussed elsewhere in this course.
NetBackup configuration
The NetBackup configuration steps shown on the slide are discussed in more details in
the following slides in this lesson.

10-15
NetBackup for VMware best practices
• Review tips in Veritas NetBackup for VMware Administrator’s Guide: NetBackup for
VMware best practices
• Best practices may include:
– Upgrade to the latest version of VMware vSphere or Virtual Infrastructure.
– Use the same VM name for both host name and display name.
If the policy’s Primary VM identifier option is changed, the existing entries under the policy’s Clients tab are still
valid.
– Add additional VMware backup hosts for scalability.
– Use VMware resource limits
For example, allow less than 4 concurrent backup jobs / snapshots per datastore.
– Attempt to use a single backup policy per datastore.
16
Before configuring NetBackup, Veritas recommends that you configure or modify the
VMware environment.
Before configuring the NetBackup for your VMware environment, Veritas recommends
reviewing the Veritas NetBackup for VMware Administrator’s Guide in the NetBackup for
VMware best practices section.
Some VMware best practices are given on the slide.
Note that NetBackup does not require any modifications to existing vSphere
environments.

10-16
NetBackup configuration: Initial steps
1• Add Enterprise Client license.
– NetBackup for VMware Administrator’s Guide: NetBackup for VMware license requirement section
– An Enterprise Client license for each ESX Server
– Application or database license for each ESX server hosting the application
2• Install NetBackup client on VMware backup host.
– Not required for NetBackup appliances, master and media servers
– Review tips in the NetBackup for VMware Administrator’s Guide: NetBackup for VMware best practices
section:
• For a more efficient backup, try to use the media server used by the backup job as the VMware backup host.
• Ensure that the VMware backup host has enough memory to handle the number of simultaneous backups that
occur.
• When a single backup host is saturated, add additional backup hosts to increase backup throughput.
17
1. Add Enterprise Client licenses.

A NetBackup Enterprise Client license is required for each ESX Server, and
NetBackup application or database licenses are required for each ESX server hosting
the application or database. For details, refer to NetBackup for VMware
Administrator’s Guide: NetBackup for VMware license requirement and contact your
Veritas Sales representative to ensure all information is up-to-date.
2. Install the NetBackup client on the VMware backup host.
The VMware backup host requires the NetBackup client software. For details refer
to both the NetBackup for VMware Administrator’s Guide: NetBackup for VMware
best practices. Some recommendations include:
• For a more efficient backup, install the NetBackup media server and the VMware
backup host on the same host.
• Ensure that the VMware backup host has enough memory to handle the number
of simultaneous backups that occur. Monitor active memory usage on the
backup host during backups and add memory if needed.
• Add additional backup hosts to increase backup throughput, when needed.

10-17
NetBackup configuration: Add VMware backup host
3
Add VMware backup
host to NetBackup
Note: This step is not required

for NetBackup media servers
and NetBackup appliances.
18
3. Add any VMware backup hosts to the Host Properties for the master server:
a. Click Host Properties > Master Servers, double-click the NetBackup master
server, and click VMware Access Hosts.
b. Click Add, enter the VMware backup host, and click Add.
c. When you are finished adding hosts, click Close.
In the policy’s VMware backup host drop-down list, select Backup Media Server to use
any available media server. If this option is used, make sure that all media servers in the
storage unit referenced by this policy are valid VMware backup hosts.

10-18
NetBackup configuration: Set resource limits
• Helps avoid serious performance

issues
• Refer to NetBackup VMware
Administrator’s Guide: Setting global
limits on the use of VMware
resources
19
Optionally, set limits on the use of VMware resources by navigating to the Resource
Limit tab of the master server’s Host Properties. Click in the Resource Limit column to
set the maximum NetBackup usage for the resource type. The settings apply to all
VMware policies that use a VMware Intelligent Policy query to select clients. VMware
Intelligent Policy queries are discussed elsewhere in this lesson.
The default for all resource limits, indicated in the NetBackup Administration Console by
a blank value in the Resource Limit column, is unlimited. The screen shot shows a
maximum of four simultaneous backup jobs to any ESX server at a given time.
For details on resource limit types and behavior, see the NetBackup for VMware
Administrator’s Guide: Setting global limits on the use of VMware resources.
Note that you may want to adjust or tune the resource limits according to the transport
mode you select.

10-19
NetBackup configuration: Add VMware credentials
4
Add VMware credentials
to NetBackup
vCenter server or
ESX server
20
4. Add VMware credentials to NetBackup.

To back up or restore virtual machines, the NetBackup server requires logon
credentials to the VMware ESX servers or the VMware vCenter servers.
In the NetBackup Administration Console, perform the following:
a. Expand Media and Device Management > Credentials > Virtual Machine
Servers.
b. Select Actions > New > New Virtual Machine Server.
c. In the Add Virtual Machine Server dialog box, enter the name of a virtual
machine server (vCenter server or ESX server).
d. In the Credentials pane of the Virtual Machine Server dialog box, enter the
following, then click OK:
• Virtual machine server type: Select VMware Virtual Center server, VMware
ESX Server, or VMware Restore ESX Server. Note that VMware Restore ESX
Server designates an ESX server to which NetBackup can restore virtual
machines, however NetBackup will not back up virtual machines from that
restore server.
• Username and Password
• If the default port number has changed, mark the Connect using port
number check box, and enter the port number.

10-20
If your site has multiple standalone ESX servers, use the Virtual Machine Server
dialog box to enter credentials for each ESX server.
Note that the account entered must have the required permissions to perform
VMWare VADP backups. For more information about the minimum required
permissions refer to Article 100001960: What are the minimum permissions needed
to properly backup and restore using vStorage API found online at

10-21
NetBackup configuration: Create a VMware policy
Use the Policy Creation Wizard or create the policy manually.
5
Use the VMware
policy type
22
5. To create a backup policy, use either the Policy Configuration Wizard or the Policies
utility in the NetBackup Administration Console.
The VMware policy type was introduced in NetBackup 7.5. When it is selected, a
new VMware tab is displayed in the policy configuration dialog. This tab contains
VMware-specific parameters. Veritas recommends using the VMware policy type.
This policy type is discussed in this lesson.
Note: Prior to NetBackup 7.5, the FlashBackup-Windows policy type was used to
back up virtual machines. Veritas does not recommend using this policy type to back
up virtual machines unless it is required, because this policy type does not support
newer backup functionality and features.
To migrate FlashBackup-Windows policies that were created in prior versions to use
the new VMware policy type, see the nbplupgrade utility in the NetBackup
Commands Reference Guide.

10-22
Configuring VMware policy attributes and schedules
Attributes Schedules
• Many options don’t apply • Supports full, differential, and cumulative
incrementals
• Supports full VM and file-level incrementals for all
schedules
– Set Enable file recovery from VM backup on the
VMware tab
• Optionally use block-level incremental backups
(BLIB):
– Requires ESX server 4.0 and later, and Virtual machine
at vmx-07 or later
– Set Enable block-level incremental backup option
• Use the VMware tab to set VMware-related

options.
23
For VMware type policies, many attributes found under the policy Attributes tab are
disabled. Most relevant VMware-specific options are found under the VMware tab,
discussed elsewhere in this lesson. VMware policies support NetBackup Accelerator,
which is discussed in the Optimizing File System Backups lesson.
VMware policies support full, differential incremental, and cumulative incremental
schedules. If you are simply backing up the virtual machine disk (VMDK) files, these
schedules normally all back up the entire file. By setting the Enable file recovery from
VM backup option under the VMware tab, NetBackup can recover the entire virtual
machine from these VMDK files, as well as perform individual file recovery. This ensures
that incremental backups only back up the changed files, while still providing the ability
to restore the entire virtual machine. Note that file-level recovery is only available on
supported guest operating systems and file systems. For more details, refer to
NetBackup Support in Virtual Environments, found online at
https://www.veritas.com/content/support/en_US/doc/NB_70_80_VE.
Additionally, block-level incremental backups (BLIB) are enabled using the Enable block-
level incremental backup option. This improves performance further by backing up data
at a block-level, instead of at a file-level. This functionality requires ESX server 4.0 and
later, and virtual machines with hardware version vmx-07 or later.

10-23
Configuring VMware policy for manual client selection
24
When assigning clients for a VMware policy, you can select whether to select clients
manually or to have them automatically selected using a query that you construct.
To manually specify clients, navigate to the Clients tab, select Select Manually, and click
New. The Browse for Virtual Machines dialog box is displayed. Select Browse and
Select Virtual Machines to see a drop down hierarchy of virtual machines. Select the
virtual machine or machines you are interested in protecting.
Note: If your VMware environment contains many VMware servers and virtual
machines, it may take too long to search and list all of them. To limit the VMware
servers that are browsed, follow the directions provided in the NetBackup for VMware
Administrator’s Guide under the section titled: Limiting the VMware servers that
NetBackup searches when browsing for virtual machines.
Note that a policy where virtual machines are manually selected does not work with the
VMware virtual machine limits specified in the master server host properties.

10-24
Configuring VMware policy for automatic client selection
• Based on virtual machine attributes

• Can be combined to narrow results
Example queries:
• Back up all VMs in Power On state
• Back up all VMs where the OS type is Windows 2012
• Back up all VMs where the display name starts with “Vmprod”
• Back up all VMs in the Dev folder that belong to cluster Cluster03
• Back up all VMs in Power On state in datastore Storage 1 where
the OS type is RedHat Linux
25
Starting with NetBackup 7.1, VMware-based policies allow for automatic virtual
machine selection. Queries are built around virtual machine attributes to determine
which virtual machines to back up. These queries can be combined with filters to create
more complex queries and limit the results.
If you want to use the new intelligent policy functionality instead of performing a
manual configuration, set the Virtual machine selection to Select automatically
through query. Next, set the VMware discovery host. Although this does not need to be
the same as the VMware backup host, in many environments this may be the same
server. The VMware discovery host has the same requirements as a backup host: be a
supported operating system and have NetBackup software installed.
In this query builder, you build the virtual machine selection query. If you do not select
any query filters, the default behavior is to discover all virtual machines, and back them
all up.
The slide shows some examples of possible virtual machine selection queries. Some
examples show queries that use multiple query filters that are combined to narrow the
resulting virtual machines.

10-25
Using query builder in basic mode
Browse
Add
Join: Clear
• Not
• And Value(s)
• And Not
Operator:
• Or Field: • AnyOf
• Or Not VMware-related fields, such as • Contains
Cluster, Datacenter, Datastore, • EndsWith
Displayname, ESXserver, Tag, • Equal
VMGuestOS, and many more. • Greater
• GreaterEqual
• IsSet
• Less
• LessEqual
• NotEqual
• StartsWith
26
Using query builder in basic mode

In the query builder’s Basic Mode, a simple query filter can be created that looks for
specific values of a VMware-related field. Additionally, the Join function can be used to
combine multiple query filters, as shown in the example in the slide:
ESXserver Equal “esx1.example.com”
AND VMGuestOS Equal “other26xLinuxGuest”
After choosing the query criteria for a specific query filter, the Browse function retrieves
all possible values from the VMware configuration. Depending on the size of the
environment, this can take some time. You can then select from the results and they are
added automatically to the Value(s) field.
The slide shows examples for the variables that make up the selection queries, including
the Join, Field, and Operator fields.
The buttons on the right help select values and form complex queries:
• The Browse button is used to discover available values based on the fields and the
available VMware resources.
• The Add button is used to add this filter to the query.
• The Clear button clears these fields, enabling you to start again.

10-26
NetBackup support for VMware Tags
• VMware tags supported for virtual machine selection.

• Only tags associated with VMs are used.
• Limitations include:
– Tags for other vCenter objects (such as Datastores) are ignored.
– Selection of VMs based on the tag category is unsupported.
– Using tags for VM selection is independent of the tag's category; Example:
• VM1 has a user-specified tag “HR” in the category Production
• VM2 has a user-specified tag “HR” in the category Test
• A policy selecting VMs with tag “HR” will back up both VM1 and VM2.
27
VMware Tag operations require vCenter Server 6.0 or later. The NetBackup master
server and all discovery hosts must be at NetBackup 7.7.1 or later. When using media
server load balancing, all media servers that are associated with the storage unit group
must be at 7.7.1 or later.
Any Windows host with only the NetBackup client software installed, that is also
defined in the VMware policy's Client tab as the NetBackup host to perform automatic
virtual machine selection, must have NetBackup Java installed. Install the NetBackup
Remote Administration Console to install NetBackup Java.
If the tag field is not required to satisfy the query, tags will not be collected and backed
up. In such a case, the tags will not be restored in a successful restore.

10-27
Using query builder in advanced mode
Note: Invalid queries or data that cannot be processed by basic mode (such as
parenthesis for precedence) may prevent being able to return to basic mode.
28
Instead of using the query builder’s Basic Mode, click the Advanced button to use the
Advanced Mode. In this mode, you can customize the query manually and use
functionality, such as parenthesis, to establish query order and precedence.
When converting from basic mode to advanced mode, the existing query is converted
and can be used as a starting point.
Note that while in advanced mode, you can also click on the Basic button to revert to
basic mode. This function does not work if the query contains invalid data, or data that
is not supported by basic mode (such as parenthesis).

10-28
Running a test query
Refer to NetBackup for VMware

Administrator’s Guide in the Query
format and examples for searching
virtual machine backups section
nbdiscover –noxmloutput –policy Lab10-vmware

+ “winvm1"
- “lnxvm2" "VM has been excluded by the discovery filter, display name = [lnxvm2], server = [10.10.2.65]."
29
When your query is formed, there is a Test Query button to execute and test the query.
After the test returns, the Test Query Results display every virtual machine found, and
identify whether the current filter value results in the virtual machine being included or
excluded.
If the query is not working as desired in providing the correct virtual machines for the
policy, the query can be modified and retested.
In an environment with large numbers of virtual machines, a query can take many
minutes. During that duration, the console cannot be closed or used to monitor other
operations. A command line utility, nbdiscover (found in the NetBackup bin
directory) can be used to check the search terms of a query outside of using the
NetBackup console. This frees the console for monitoring and other work. This utility
uses the name of the policy as an argument.
For more details, refer to Veritas NetBackup for VMware Administrator’s Guide in the
Query format and examples for searching virtual machine backups section.

10-29
Configuring the Reuse VM selection query results
• Enables the administrator to control how often vCenter is queried

• Determines the time period during which a discovery is used
• Reset when a query or policy property that affects discovery is changed
• Has no effect on job scheduling
30
The Reuse VM selection query results parameter enables the administrator to control
the virtual center interaction by specifying how old the query results need to be, before
NetBackup queries the virtual center server for virtual machine discovery information
again.
This parameter does not have any effect on backup scheduling. Similarly, backup job
scheduling does not affect when virtual machine discovery takes place. In the example
on the slide, discovery queries the virtual center every 8 hours, regardless of when jobs
are scheduled. When the policy is scheduled to run, the virtual machines that were
discovered last are used.

When a query or policy property that affects discovery is modified, the Reuse VM
selection query results time value is ignored, and a new virtual machine discovery takes
place.

10-30
Relationship between Clients and Backup Selections
31
When you use manual virtual machine selection, the Backup Selections list simply
shows ALL_LOCAL_DRIVES.
When you use automatic virtual machine selection, the virtual machine selection query
that was created is listed under the Backup Selections list, as shown in the slide:
vmware:/?filter=VMGuestOS Equal “rhel6_64Guest” AND
ESXserver Equal “esx1.example.com”
In either circumstance, the policy backs up all local drives from each listed virtual
machine. To exclude certain drive types, such as swap, boot, or data drives, use the
Virtual disk selection setting under the VMware Advanced Attributes setting. This
setting is discussed elsewhere in this lesson.

10-31
Viewing the VMware policy tab
32
When VMware is selected as the policy type a VMware tab is displayed in the policy
configuration dialog box which contains many VMware-specific settings.
These settings are discussed in the following slides.

10-32
Configuring the VMware backup host
Example configuration
winmaster winmedia ESX server
LAN
SAN
Datastore
STU1 STU2
33
The VMware backup host is a NetBackup host that performs backups on behalf of the
virtual machines. Possible choices include:
• Backup Media Server: This option instructs NetBackup to use the media server of
the backup job as the VMware backup host as well.
Note: The storage unit that is specified in the policy must be unique to media
servers supported as backup hosts. In these cases, if the storage unit is also available
for a media server that is not supported as a backup host, the snapshot cannot
succeed.
When the Backup Media Server option is selected, NetBackup cannot determine a
host to perform policy validation. To validate the policy, temporarily select one of
the possible media servers as the backup host (do not select Backup Media Server).
When the policy validates successfully, reset the backup host to Backup Media
Server.
• A specific backup host, which selects a particular backup host to perform the
backup.
Note: The backup hosts (but not backup media servers) must be identified in the
master server’s host properties under VMware Access Hosts.

10-33
Configuring the Primary VM identifier
34
This Primary VM identifier specifies how NetBackup recognizes VM names, for backup:
• VM hostname: This is the network host name for the virtual machine. This option is
the default. This option requires running and functioning VMware Tools in the VM.
• VM display name: This is the name of the VM as displayed in the VMware interface.
Character restrictions apply; Refer to the NetBackup for VMware Administrator’s
Guide.
• VM BIOS UUID: This is the ID assigned to the VM when it is created. This ID may or
may not be unique, depending on whether the VM has been duplicated.

• VM DNS Name: This is the virtual machine’s VMware DNS name. In the vSphere
Client, this appears under the virtual machine's Summary tab. This option requires
VMware Tools running in the VM as well as a properly configured DNS configuration.
• VM Instance UUID: This is the globally unique ID assigned to the VM when it is
created, even if the VM has been duplicated. The option requires backup hosts
running NetBackup 7.5 or later, and is not available in some legacy VMware releases.
Virtual machine names must be uniquely identified in a master server’s backup policies.
Additionally, the virtual machine may not be browseable under certain conditions, such
as when using the hostname as the identifier and the virtual machine is powered off, or
when the virtual machine does not have an IP address.

10-34
Configuring Optimizations
35
The following options set the type and scope of the VMware virtual machine backup:
• Enable file recovery from VM backup: This option enables restores of individual
files from the backup. Additionally, it provides the best deduplication rates with
NetBackup deduplication. With or without this option, you can restore the entire
VM.
• Enable block-level incremental backup: Block-level backups (BLIB) reduce the size
of full and incremental backups by tracking and only backing up the blocks that have
changed since the last backup. BLIB works with VMware’s Changed Block Tracking
(CBT) in vSphere to track the block-level changes, and requires ESX server 4.0 and
later, and VM hardware version vmx-07 or later. If this checkbox is enabled,
NetBackup will automatically enable CBT in the VM.
Note: When selecting Use Accelerator on the Attributes tab, the block-level
incremental backups selection will be selected and greyed out so that it cannot be
unselected.
• Exclude deleted blocks: This option uses proprietary mapping technology to reduce
the size of the backup image by excluding any unused or deleted blocks within the
file system on the VM. Windows NTFS, and Linux ext2, ext3, and ext4 are supported.

10-35
• Exclude swapping and paging files: This option reduces the size of the backup
image by excluding the data in the guest OS system paging file on Windows or the
swap file on Linux. This option does not exclude the swapping and paging files from
the backup; it only excludes the data in those files. If the files are restored, they are
restored as empty files.
To back up a VM that contains Veritas Storage Foundation volumes, disable the Enable
file recovery from VM and Exclude deleted blocks backup options.

10-36
Configuring Application Protection
Required settings for

application protection
• Provides application consistent snapshot

• Provides automatic log truncation
• Requires NetBackup client installed on VM
• May require install of Veritas VSS Writer for some functionality
37
VMware VMs running Microsoft Windows with Microsoft Exchange, MS-SQL, or

SharePoint have additional benefits when installing the NetBackup client in the VM. This
enables the ability to restore individual database files (such as individual e-mail restores
from Exchange) as well as automated log truncation.
NetBackup uses Windows Volume Shadow Copy Service (VSS) to quiesce the database
before it creates a snapshot of the virtual machine. A full backup of the database data is
performed with each backup job, even if the policy schedule is incremental.
Additionally, application protection is only available with query-based client selection on
the Clients tab.

To enable file-level recovery of the database data that resides in the VM, use the
Application Protection frame. These options apply to full backups of the VM only; they
do not apply to incremental backups. Select from the following options:
• Enable Exchange Recovery
This option enables recovery of the Exchange databases or mailbox messages from
the virtual machine backups. If this option is disabled, you can recover the entire
virtual machine from the backup, but you cannot recover the databases or mailbox
messages individually. When using the Enable Exchange Recovery option:
• Enable the Enable file recovery from VM backup option.
• Disable the Enable block-level incremental backup option.
• Use the Truncate logs option to truncate the transaction logs when the VM
snapshot is complete. Truncating the logs frees up disk space in the virtual
machine. To use this option, install the Veritas VSS provider on the VM.

10-37
For more information, including instructions on how to install the Veritas VSS
provider, refer to the NetBackup for Microsoft Exchange Server Administrator's
Guide.
• Enable SQL Server Recovery
This option enables recovery of individual MSSQL databases from the virtual
machine backup. If this option is disabled, you can recover the entire virtual
machine from the backup, but you cannot recover the SQL files individually.
When using the Enable SQL Server Recovery option:
• Use the Truncate logs option to truncate the transaction logs when the backup
occurs. Truncating the logs frees up disk space in the virtual machine.
Additional information about VMware backups using the NetBackup for Microsoft
SQL Server agent is provided in the Managing Microsoft SQL Backups lesson. The
Veritas VSS provider must be installed to support this functionality.
• Enable SharePoint Recovery
This option enables recovery of SharePoint objects from the virtual machine backup.
If this option is disabled, you can recover the entire virtual machine from the
backup, but you cannot recover the SharePoint objects individually.
When using the Enable SharePoint Recovery option:
For more information, see the NetBackup for Microsoft SharePoint Server
When you enable one or more of these Application Protection options, the backup job
automatically initiates an Application State Capture (ASC) job for each virtual machine
listed in the policy. These ASC jobs help determine if the applications are running in
those virtual machines. Because these ASC jobs require additional overhead, it is not
recommended to simply enable these options for policies that back up all VMs. Instead,
create a new VMware policy specifically for those virtual machines that are running
these applications, and enable the Application Protection option for that policy.
This is covered in greater detail in the NetBackup Advanced Administration course.

10-38
Configuring Transport modes
SAN NBD/NBDSSL
LAN LAN
Backup ESX Backup ESX
host server host server
SAN
Datastore Datastore
HOTADD
LAN
Media ESX
server server
SAN
Backup
host
Datastore
Article 100030882: VMware Transport Modes: Best practices and troubleshooting
39
The transport modes determine how the snapshot data travels from the VMware
datastore to the VMware backup host. The appropriate mode depends on your
environment. By default, all modes are selected. NetBackup tries each transport mode
in order, from top to bottom. It uses the first mode that succeeds for all disks in the VM.
The following transport modes are available:
• san: For unencrypted transfer over Fibre Channel (SAN) or iSCSI. Note: This mode is
not supported for VMs that use VMware Virtual Volumes (VVols).
• hotadd: Lets you run the VMware backup host in a virtual machine. This feature
requires ESX 3.5 Update2 or later. Note: For virtual machines that use VVols, they
must reside on the same VVol datastore as the backup host (hotadd) VM.
• nbd: For unencrypted transfer over a local network that uses the Network Block
Device (NBD) driver protocol. This mode is usually slower than Fibre Channel (san).
• nbdssl: For encrypted transfer (SSL) over a local network that uses the Network
Block Device (NBD) driver protocol. This mode is usually slower than Fibre Channel
(san).
Use the Move Up and Move Down buttons to change the order in which NetBackup
tries each selected mode. For more best practices and suggestions on these modes,
refer to Article 100030882: VMware Transport Modes: Best practices and
troubleshooting, found online at http://www.veritas.com/docs/100030882.

10-39
Configuring VMware Advanced Attributes
Virtual disk selection
drive exclusions:
– Include all disks
– Exclude boot disks
– Exclude data disks
Optionally set
Post events to vCenter
Limit VMware servers

communicated with by
this policy
40
This dialog box is displayed when you click Advanced under the VMware policy tab. You
can use the VMware Advanced Attributes dialog to set the following additional
parameters. In most situations, the best settings are the defaults.
• Virtual machine quiesce: This option is enabled by default. I/O on the virtual
machine is quiesced before NetBackup creates the snapshot. This helps guarantee
data consistency in the snapshot. Veritas does not recommend that you disable
quiesce.
• Virtual disk selection: This option determines the kind of disks on the VM that are
included in the backup. This option can reduce the size of the backup, but should be
used with care., and is only intended for VMs that have multiple virtual disks.
• Ignore diskless VMs: This option directs NetBackup not to back up any VM that has
no VMDK file assigned to it; for example, a replicated virtual machine in passive
mode in a VMware vCenter Site Recovery Manager (SRM) environment.
• Post events to vCenter: This option enables NetBackup to send backup-related
events to the vCenter server. More information is available on how to view the
events in the NetBackup for VMware Administrator’s Guide.
• VMware server list: Specifies a colon (:) delimited list of VMware servers that
NetBackup communicates with for this policy. VM queries will only go to these
servers, which helps improve performance in large virtual environments.

10-40
Excluding virtual disks with custom attributes from backups
• Enter the VMware custom attribute, or

use NB_DISK_EXCLUDE_LIST (default)
• You must register the vCenter’s
credentials with NetBackup
Example:
scsi0-0,ide0-0,sata0-0,nvme0-0
41
The Exclude Disks tab determines the kind of disks on the VM that are excluded from
the backup. These options can reduce the size of the backup, but should be used with
care. Available options include:
• No disks excluded backs up all VM disks configured for the virtual machine.
• Exclude boot disk excludes only the boot disk (for example the C drive)
• Exclude all data disks includes only the boot disk and excludes all data disks.
• Perform custom attribute based exclusion excludes disks based on VMware custom
attributes. If you select this option, you must also enter the name of the Custom
Attribute, which NetBackup then uses to determine which disks to exclude.
The default value for this attribute is NB_DISK_EXCLUDE_LIST or you can enter the
name of the VMware custom attribute. This VMware custom attribute is created
using the Exclude Disk Wizard through the NetBackup plug-in for vSphere Web Client.
NetBackup excludes the disks defined by the attributes listed in the policy. The
attribute must have a comma-separated list of device controllers of the disks to be
excluded, for example:
scsi0-0,ide0-0,sata0-0,nvme0-0
If the custom attribute is not populated or does not exist on the VM, than none of
the disks are excluded. If disks are removed from the custom value between the
differential backups then only those files that changed since the last backup are
available to restore individually. If disks are added to the custom attribute value
between the differential backups then those disks are excluded from the next
backup.

10-41
Note: You must register the vCenter server’s credentials with NetBackup. The ESXi
server credentials are not sufficient.
Note: When a virtual machine is restored from the backup, the virtual machine data
for the excluded disk may be missing or incomplete.
• Specific disk(s) to be excluded: Excludes the disks that you specify. Note that this
option gives the NetBackup administrator control over which disks are excluded from
backups.
• You must include comma-separated values of controller IDs.
• If the disks do not exist on the specified controller and device IDs, none of the
disks (except independent disks) is excluded.
• If you remove controllers from the exclusion list between the differential backups,
only those files that changed since the last backup are available to restore. All
files are available to restore after the next full backup.
• If you add controllers to the exclusion list between the differential backups, their
disks are excluded from the next backup.

10-42
Creating custom attributes using the Virtual Disk Exclusion Wizard
43
The new NetBackup plug-in for vSphere Web Client now contains a Virtual Disk
Exclusion Wizard. This is an easy way to set custom attributes for VMware hosts and
their virtual disks. Once the wizard is launched enter a Custom Attribute name or leave
the default setting, NB_DISK_EXLUDE_LIST. Next, search for the desired virtual host
name and select the host name(s) from the resulting list.
Next, select the disk(s) to which you want to apply the Custom Attribute. If a disk is
excluded already, a warning icon appears in the Exclude disk column.
From the Review Selections screen, select the virtual machine then select Set
Exclusions. The list box shows the results of the operation.

These disk(s) will be excluded each time this Custom Attribute matches the Custom
Attribute and virtual hostname in a backup policy.

10-43
VMware VVols and VSAN
VMware Virtual Volumes (VVols)
• Permit virtualization-aware management of underlying storage assets

• Access disks beneath the level of LUNs
NetBackup supports VVols as datastores
• Supports datastores of types: NFS, NFS41, SAN, iSCSI, vsan, VVOL, Local
• Refer to the NetBackup Hardware Compatibility List
• Refer to Veritas NetBackup for VMware Administrator’s Guide: Notes on
VMware Virtual Volumes (VVols)
44
For backup or restore of VMs on VVol datastores, NetBackup supports the following
transport modes: nbd, nbdssl, hotadd. Due to a VMware VDDK limitation, san transport
is not supported.
To restore a virtual machine with the hotadd transport mode: VMware requires that the
virtual machine and the restore host virtual machine reside on the same VVol datastore.
Otherwise, the restore must use a different transport mode (not hotadd).
For a restore to standard (non-VVol) datastores, the NetBackup job creates a vSphere
snapshot of the virtual machine while NetBackup restores the data.
Note: For a restore to a VVol datastore, NetBackup restores the data to the virtual
machine without creating a vSphere snapshot.
When troubleshooting backups of virtual machines on VVols, note the following:
• Each NetBackup snapshot job creates a vSphere snapshot of the virtual machine.
• Licensing requirements for vSphere snapshots vary from one type of VVol storage to
another, depending on the array vendor. Ensure that you have the required snapshot
license from the array vendor; otherwise, snapshot creation may fail.
Refer to Veritas NetBackup for VMware Administrator’s Guide: Notes on VMware Virtual
Volumes (VVols).

10-44
Topic: Performing and Monitoring VMware Backups
After completing his topic, you will be able to monitor VMware backup.
After completing his topic, you will be able to monitor backup, and view process
activities.

10-45
VMware backup example with client discovery
• The first parent job runs with the discovery host as Client and resolves virtual machines
with the query in the File list.
• Each VM has a parent snapshot and child backup job.
46
When using automatic VMware client selection, client discovery is required when the
backup runs.
An initial parent job runs the client discovery, showing the job’s client as the discovery
host, and the job’s file list as the query that is being used.
After this initial parent job, each virtual machine is displayed as a standard virtual
machine backup, which normally has an initial parent snapshot job and a child backup
job.

10-46
Viewing NetBackup activity in vSphere Client
47
NetBackup can record backup activity for virtual machines in VMware vCenter. You can
view the events in vSphere Client at the level of any parent object (such as folder,
datacenter, cluster, or host). You can also view the events for the entire virtual machine.
Ensure that the policy’s Post events to vCenter option is enabled under the VMware
tab’s advanced options.
To view backup events and the last backup time in vSphere Client:
1. Open the vSphere Client and connect to the VMware server.
2. Navigate to Home > Inventory > Hosts and Clusters.

3. Select the object (such as datacenter, host, or virtual machine) and select the Tasks
& Events tab.
4. Select the Events view.

10-47
VMware backups with Linux virtual machines
• Using Linux VM quiescence

– Allows for consistent backups
– Provided with guest OS-specific tools, such as Open VM Tools
Refer to VMware support for Open VM Tools: https://kb.vmware.com/kb/2073803
• Not using Linux VM quiescence results in crash-consistent backups
48
Traditionally, virtual machine snapshots do not quiesce Linux virtual machines, and the
backup uses snapshots that are crash consistent. Crash consistent means that the
backup of the system will be roughly equivalent to how the system would appear after a
system crash. Because of file system consistency tools, such as journaling, the system
should be usable, however this is not an optimum way of backing up your servers.
Prior versions of NetBackup provided a tool, SYMCquiesce, that would quiesce some
linux VMs. In NetBackup 8.1 SYMCQuiesce is discontinued since this same functionality
is now present in Open VM Tools for various Operating systems. More info about Open
VM Tools can be found in https://kb.vmware.com/kb/2073803.

Use a file system check (fsck) after restoring data to ensure data consistency after a
restore, for any Linux VMs that were backed up while they were running.

10-48
Lesson summary
• Key points
– In this lesson, you learned about virtual machines and support for virtual machines in VMware.
– You also learned to configure and run VMware backups.
– NetBackup for VMware Administrator’s Guide
– NetBackup for Hyper-V Administrator’s Guide
– Document NB_70_80_VE: Support for NetBackup in virtual environments
49

10-49
Lab 10: Performing Virtual Machines Backups
Lab objectives
• Verifying the VMware environment
• Configuring NetBackup servers to access the VMware vCenter server
• Installing the NetBackup Plug-in for VMware vSphere Web Client
• Configuring a VMware policy in NetBackup
• Performing and monitoring NetBackup VMware virtual machine backups
• Excluding disks from a VMware virtual machine backup
50

10-50
What did you learn?
lesson.
51
current lesson.

10-51
Question: VMware backup host component
To which VMware component does the backup host require direct access for SAN
backups?
A. vCenter server
B. Datastore
C. vStorage API
D. VMware tools
52

10-52
Answer: VMware backup host component
To which VMware component does the backup host require direct access for SAN
backups?
A. vCenter server
B. Datastore
C. vStorage API
D. VMware tools
The correct answer is B. The datastore contains virtual machine data for the ESX servers.
53

10-53
Question: About VMware backup host platforms
Which platform is unsupported as a platform for the VMware backup host?
A. Windows 2008
B. SUSE Linux 11
C. Solaris 11
D. RedHat Linux 6
54

10-54
Answer: About VMware backup host platforms
Which platform is unsupported as a platform for the VMware backup host?
A. Windows 2008
B. SUSE Linux 11
C. Solaris 11
D. RedHat Linux 6
The correct answer is C. Solaris is not supported as a platform for the backup host, regardless of the
NetBackup version. For the latest information, refer to Article TECH127089: Support for NetBackup 7.x in
virtual environments, or the latest NetBackup for VMware documentation.
55

10-55
Question: About application awareness
Which database technology is not supported by the application awareness feature,
which enables individual component restore?
A. Oracle
B. Microsoft Exchange
C. Microsoft SharePoint
D. Microsoft SQL
56

10-56
Answer: About application awareness
Which database technology is not supported by the application awareness feature,
which enables individual component restore?
A. Oracle
B. Microsoft Exchange
C. Microsoft SharePoint
D. Microsoft SQL
The correct answer is A. You can select Microsoft Exchange, Microsoft SharePoint, and Microsoft SQL for Application
Protection under the VMware policy tab.
57

10-57
End of presentation
10-58
Lesson 11: Performing Virtual Machines Restores
This is the “Performing Virtual Machines Restores” lesson in the “Veritas NetBackup 8.1:

11-1
Policies
This lesson is the eleventh lesson in this course.


11-2
Lesson objectives
Topic Objective
Managing virtual machine restores Describe virtual machine restore concepts.
Run VMware restores using the Backup, Archive, and Restore

Managing VMware restores
console.
Using VMware Instant Recovery Run VMware restores using Instant Recovery.

11-3
Topic: Managing virtual machine restores
After completing this topic, you will be able to describe virtual machine
restore concepts.
After completing this topic, you will be able to describe virtual machine restore
concepts.

11-4
Supported NetBackup virtual machine recovery options
Virtual machine File-based Full VM Single-pass backup; Instant

technology restores restores file and full VM restore recovery
VMware ✓ ✓ ✓ ✓
Microsoft Hyper-V ✓ ✓ ✓
RedHat Enterprise
Virtualization (RHEV) ✓
Solaris zones ✓
Oracle Solaris
virtualization ✓
5
NetBackup supports a number of virtual machine options, such as both file-based

restores and full virtual machine restores, including supporting both methods from a
single-pass backup of the VM. This functionality is supported on both VMware and
Microsoft Hyper-V. Additionally, VMware supports a feature known as instant recovery,
discussed elsewhere in this lesson.
For other virtual machine types, file-based restores are supported by treating the VM as
a NetBackup client, with the NetBackup client software installed in the VM.

11-5
Performing traditional virtual machine restores
• Perform recovery using supported network methods

– LAN: Unencrypted or encrypted transfer over a local area network
– SAN: Unencrypted transfer over fibre channel or iSCSI
• VM server starts the virtual machine
LAN
SAN VM VM
Master Media
server server server storage
In a traditional virtual machine restore, a virtual machine image is transferred from

backup storage to the VM server’s storage. There is generally a large data transfer time
from the media server to the VM storage, due to the size of the VMs.
Full VM backup and recovery for some virtual machine platforms, such as VMware and
Microsoft Hyper-V, does not require that the NetBackup client software is installed in
the virtual machine itself. This is due to integrated features which take advantage of a
NetBackup host that serves as a backup host for the virtual servers. Refer to the
Performing Virtual Machines Backups lesson for more details.
After the restore, the VM server can optionally be directed to start the virtual machine.

11-6
Performing file restores from single-pass virtual machine backups
• Ensure backup include Enable file recovery from VM backup

• Recovery must be performed to host running NetBackup client
– Stage file recovery to hosts without NetBackup client software installed.
– NetBackup client can be a physical or virtual host.
LAN
NetBackup
client VM VM
Master Media
server server server storage
NetBackup has the capability of performing one-pass backups for virtual machines that
also records metadata allowing for individual file restores. This feature is both time
efficient in allowing for a single-pass backup, and space efficient in requiring only one
copy of the backup for both full VM recovery and individual file recovery.
Recovery of individual files must be performed to a host running the NetBackup client
software. If the virtual machines in your environment are not running NetBackup client
software, you will need to stage the recovery. Some customers have NetBackup clients
(physical or virtual) dedicated to this purpose. Recovering individual files must be
performed over a local area network (LAN).

11-7
Topic: Managing VMware restores
After completing this topic, you will be able to run VMware restores using
the Backup, Archive, and Restore console.
After completing this topic, you will be able to run VMware restores using the Backup,
Archive, and Restore console.

11-8
Initiating a virtual machine restore
Identify virtual machine

using same identifier as
when backed up
Ignored for full
VM restores
To restore a virtual machine, launch the Backup, Archive, and Restore console. This can
be launched on the master server or on the virtual machine backup host that is
configured to communicate with, and take the data stream from, the ESX server.
1. Set the source and destination clients.
From the File menu, select Specify NetBackup Machines and Policy Type.
2. Set the Source client for restores (or virtual client for backups) as the virtual
machine you wish to restore.
Type in the client’s name, or use the Search VM Clients button.

3. Select the Destination client for restores and the Policy type for restores, ensuring
you select the correct policy type:
• VMware displays all VMware backups.
• Hyper-V displays all Hyper-V backups.
• FlashBackup-Windows displays all Hyper-V and VMware backups. This policy
type was used for VM backups prior to NetBackup 7.5. Veritas recommends
using VMware and Hyper-V policy types.
• MS-Windows and Standard do not display backups from virtual machines that
were backed up with VMware of FlashBackup-Windows policies.

11-9
Choosing a view and browsing virtual machines
10
Clicking the Search VM Clients button in the Specify NetBackup Machines and Policy
Type dialog brings up the Browse and Search Virtual Machines for Restore dialog box.
The example on the slide shows a sample view when Browse Virtual Machines:
vSphere view is selected.
Select the type of view for browsing:
• vCloud view: Shows the virtual objects as they appear in vCloud Director.
• vSphere view: Shows the virtual objects as they appear in vSphere Client.

11-10
Restoring data from a VMware Backup
File or folder recovery

Full virtual machine recovery
Virtual disk recovery
11
Select the appropriate restore type under the Select for Restore button:
• Normal Backups: This option is used to view and restore individual files.
• Virtual Machine Backup: This option is used to restore the entire virtual machine.
• Virtual Disk Restore: This option is used to restore one or more virtual disk.
These options are shown in more details on the following slides.

11-11
File and folder recovery of VMware virtual machine
• Restore to a system with the

NetBackup client installed
• Restore to a file share that can be
accessed by the VM
• Use Instant Recovery for VMware
12
The Restore type of Normal Backups is used to view and restore individual files.
Specify the destination as the virtual machine’s host name (not the display name or
UUID).
Note that restoring individual files to a virtual machine requires that the NetBackup
client is installed on that VM. Alternatively, restore to a shared folder that can be
accessed by the virtual machine client.
To restore directly to a virtual machine, the ESX server name that is specified for the
restore must match the ESX server’s official hostname. The name must be in the same
format in which it is registered in DNS and in the VMware server. The restore fails if ESX
servers are configured with short host names and if the backup and restore are through
a vCenter server.
Note that you can restore Windows files to a Windows guest operating systems, but not
to Linux. Similarly you can restore Linux files to supported Linux guest operating systems
but not to Windows.
If a Linux file system was not quiesced before the snapshot, some files may be
inconsistent. This issue is discussed elsewhere in this lesson.

11-12
Full VM Recovery of VMware virtual machine
• Source client must be the VM identifier (host

name, display name, or UUID) used during
backup.
• Destination client is ignored, and selected
later in the Virtual Machine Recovery wizard.
• Individual VMDK restore is supported.
Starts the Virtual Machine

Recovery Wizard
13
The Restore type of Virtual Machine Backup is used to restore the entire virtual
machine.
To recover the complete virtual machine, select the VMDK files you wish to restore.
If you are restoring from physical tape, click the Preview button to see which tapes are
needed for the restore.
When ready, click the Restore button.
After selecting a Restore type of Virtual Machine Backup, clicking the Restore button
starts the Virtual Machine Recovery Wizard. The following slides explore this wizard.

11-13
Virtual Machine Recovery wizard (1 of 4):
Recovery Destination
14
The Virtual Machine Recovery wizard guides you through the process of recovering a
complete virtual machine.
The first screen displays the original settings of the virtual machine at the time it was
backed up. Review the settings and decide whether you want to recover the virtual
machine to its original location or to an alternate location.

11-14
Recovery Options
15
On the Recovery Options screen:

• Select the NetBackup Recovery Host, which is the NetBackup client used to send
the data to the ESX server’s datastore. Typically, this is a NetBackup media server
(often the same media server that performed the backup).
• Select the Transport modes, and then use the Move Up and Move Down buttons to
decide which transfer types are prioritized:
• san: For unencrypted transfer over fibre channel (SAN) or iSCSI
• nbd: For unencrypted transfer over a local network that uses the Network Block
Device (NBD) driver protocol (i.e. the LAN)
• nbdssl: For encrypted transfer over a local network that uses the Network Block
Device (NBD) driver protocol (i.e. the LAN)
• hotadd: Requires that the VMware recovery host is itself a virtual machine. This
feature requires ESX 3.5 Update2 or later.

11-15
Virtual Machine Options
16
On the Virtual Machine Options screen:

• Select any applicable virtual machine restore options:
• Restore UUID
• Overwrite the existing virtual machine
• Remove backing information for devices
• Remove network interfaces
• Power on virtual machine after recovery

• Override default job priority
• Retain original hardware version
• Select any virtual disk format options
Note that thin provisioning can impact performance as new blocks are constantly
being allocated.
For more information about disk provisioning, see the article: About Virtual Disk
Provisioning Policies, available online at: https://pubs.vmware.com/vsphere-
50/topic/com.vmware.vsphere.storage.doc_50/GUID-4C0F4D73-82F2-4B81-8AA7-
1DD752A8A5AC.html

11-16
Perform Recovery
17
On the Perform Recovery screen:

1. Before starting the restore, click Run Pre-Recovery Check to perform the pre-
recovery check.
This improves your restore success rate and prevents wasted time by identifying
problems that may cause the restore to fail, such as low disk space or incorrect
permissions. Note that the pre-recovery check on the slide shows a datastore space
failure, which may cause a problem if a full VM recovery is performed.
2. After the pre-recovery check is successful, click Start Recovery to initiate the
restore.
To monitor the restore, click View Status from the Backup, Archive, and Restore
interface or use the Activity Monitor in the NetBackup Administration Console.

11-17
Virtual Disk Restore of VMware virtual machine
Disks can be restored to:
• Original VMs
• Alternate VMs
• New VMs
Starts the Virtual Machine

Disk Recovery Wizard
18
The Restore type of Virtual Disk Restore is used to restore individual VMWare virtual
machine disks to the following destinations:
• Original virtual machine: Either overwrite the original disks or attach virtual disks
without overwriting them. NetBackup creates a temporary VM to which the virtual
disks are restored to, attaches the virtual disks to the existing, target VM, and finally
deletes the temporary VM after the disks are attached successfully.
• Alternate virtual machine: NetBackup creates a temporary VM to which it restores
the virtual disks, then attaches the virtual disks to the existing, target VM, and finally
deletes the temporary VM after the disks are attached successfully.

• New virtual machine: NetBackup creates a new virtual machine and restores the
specified disks to the new VM. After the restore, the restored disks should be
attached to a VM that can support them and then delete the restore VM.
Note: If the recovery host is running a version prior to NetBackup 8.1, the original and
different VM restore destinations are not supported.
To recover a virtual machine disk, select the virtual machine. If you are restoring from
physical tape, click the Preview button to see which tapes are needed for the restore.
After selecting a Restore type of Virtual Disk Restore, clicking the Restore button starts
the Restore Virtual Machine Disks Wizard. The following slides explore this wizard.

11-18
Restore Virtual Machine Disks wizard
19
The new Restore Virtual Machine Disks wizard is launched from the Backup, Archive
and Restore interface when you select Restore. The Select Virtual Disks screen shows
all of the virtual disks that were in the VM at backup-time, even those disks that were
excluded from the backup. By default, the wizard displays the virtual disks. Select File
System to show the file system disks. Select the disk(s) you wish to restore, then select
Next.

11-19
Recovery Destination
20
Select where you want to recover the virtual disk(s) to: Original, Alternate, or a New
(temporary) virtual machine. From the Advanced Restore Options you can Delete
Restored staging VM on error and adjust the Wait time for VM shutdown.

11-20
Virtual Disk Destination – Original Virtual Machine
21
Virtual Disk Destination details are displayed. All options are grayed out since the
Original Virtual Machine was selected as the recovery destination. If an Alternate was
selected then you would have an option to select a different virtual machine. You also
have the option to Power on the virtual machine after restore.

11-21
Virtual Disk Destination – New (temporary) VM
22
When you select to Recover the virtual disk(s) to a New (temporary) virtual machine
you can set the parameters on this screen.

11-22
Storage Destination
• Original
• Thick Lazy Zeroed
• Thick Eager Zeroed
• Thin
• Custom
• No
• Yes
• Custom
23
The Storage Destination screen shows you the settings for all the virtual disk. Notice the
value for Restored virtual disk provisioning is set to Original (which is the default) and
the Provisioning column displays Thin. This is because the virtual disk being restored
was thin provisioned. If you choose the checkbox for Overwrite the drop-down menu
for Overwrite all virtual disks automatically changes to Yes.
Refer to VMware documentation for more information on disk provisioning types.

11-23
Recovery Summary
24
The Recovery Summary screen displays the parameters of the recovery. Verify the
setting for the recovery.

11-24
VMware recovery with Linux virtual machines
• Cross-platform restore of individual files is not supported.

Cannot restore Linux files to Windows, or Windows files to Linux
• If the Linux file system was not quiesced before the snapshot, some files maybe
inconsistent.
Use fsck to check and fix file systems.
• There are numerous caveats and procedures recovering ext2 and ext3 filesystem to ext4.
Refer to NetBackup for VMware Administrator's Guide.
• When restoring Linux files individually, the extended file attributes cannot be restored to
NFS-shared devices.
• When restoring a Linux VM, the ESX server may assign a new (virtual) MAC address.
After you restart the virtual machine, you may have to configure its MAC address.
25
Virtual machines in VMware running the Linux operating system are also supported for
full and block-level incremental backups. The most popular Linux distributions are also
supported for NetBackup Single File Recovery (SFR), as long as the following
prerequisites are met:
• vSphere APIs are in use
• The operating system is RHEL 4 or later, or SUSE 10 or later
• ext2, ext3, and ext4 file systems are used
• NetBackup client is installed inside the virtual machine

Additional caveats and notes are listed on the slide. Refer to the NetBackup for VMware
Administrator’s Guide for additional details.

11-25
Topic: Using VMware Instant Recovery
After completing this topic, you will be able to run VMware restores with
Instant Recovery.
26
After completing this topic, you will be able to run VMware Instant Recovery restores.

11-26
Working with Instant Recovery for VMware (IRV)
Using IRV for temporary recovery
• Files and other objects can be recovered from the machine.

• The original backup disk image is not modified.
• Instead a temporary disk on a VMware controlled datastore is used for writes.
• The recovered virtual machine can operate as normal, however with
performance impact.
Using IRV for long-term and production use
• NetBackup disk storage performance and availability impacts should be

considered.
• VMware Storage vMotion can migrate the recovered VM while it is running.
27
Instant recovery for VMware (IRV) is a capability that allows a VMware infrastructure to
use the NetBackup backup location as a data store.
No data transfer from NetBackup to ESX or vCenter is done. The virtual machine can
start up and begin processing data almost immediately.
In normal mode the virtual machine will be migrated to a production data store. Using
VMware storage vMotion migration can be accomplished while the virtual machine is
running.
Possible uses for IRV include:

• Access and restore files and folders, and then delete the virtual machine
• Test a patch on a restored VM before applying the patch to production systems
• Start a VM from its backup and use it until the production ESX server is back online
• Permanently recover the virtual machine by means of Storage vMotion
• Verify a backup image, or verify an application
It is not recommended to use instant recovery for VMware for long term production use
or as a disaster recovery method. Additionally, in the case where hundreds of virtual
machines may need to be started, the I/O load and network traffic would be too much
for the media server to handle efficiently.

11-27
VMware Virtual Machine Restore: Traditional
1. VM image (vmdk) restored to VMware Datastore

2. VMware server starts the virtual machine
3. Data transfer time from media server to Datastore takes time
LAN
vCenter
SAN ESX server
Master Media Datastore
server server servers (VMDK files)
28
In a traditional restore a vmdk image is transferred from backup storage to a VMware

datastore.
VMware server starts the VM, and then either file recovery operations or full virtual
machine operations commence.
There is always a data transfer time from the media server to the data store. That data
transfer time can be significant, as VM sizes range from gigabytes to multiple terabytes.

11-28
VMware Virtual Machine Restore: IRV
1. Instant Recovery for VMware uses a Network File System on the media server as a
Datastore
2. VMware starts the recovery VM
3. VMware Storage vMotion may be used to migrate to a production Datastore
LAN
vCenter
SAN ESX server
Master Media NFS Datastore
server server (Datastore) servers (VMDK files)
29
Instant Recovery for VMware uses a Network File System mount served by the
NetBackup media server as a VMware datastore. The ESX server uses the vmdk on this
NetBackup storage to start the recovery virtual machine.
Once the recovery virtual machine is running, VMware vMotion can be used to migrate
the virtual machine to a production datastore.
Instant recovery should not be used as a disaster recovery solution. The load put on the
media server for a full scale disaster recovery will negatively impact backup and
recovery operation.

11-29
IRV recommendations
• SAN connection from the NetBackup media server and its disk storage unit.
– For fibre channel, a minimum speed of 4 Gb/second is recommended
– For iSCSI, a minimum speed of 1 Gb/second is recommended.
• For disaster recovery testing, Veritas recommends that you restore no more than 3 or 4
virtual machines per media server.
• Migrate one VM with Storage vMotion at a time per media server.
30
A SAN connection between the media server and the backup storage is recommended.
The minimum recommended speed for both fibre channel and iSCSI SAN, in gigabits per
second, is given on the slide. Note that NetBackup appliances do not support iSCSI.
For disaster recovery Veritas recommends no more than four virtual machines for each
media server due to the I/O traffic required for operation. The migration may be slow if
you simultaneously migrate multiple virtual machines per media server.
In any disaster recovery the backup system is a key component in its effective operation
is essential to success. Overloading the backup system with IRV operations may prove
counter-productive. The number to restore depends on the I/O load on the media
server.

11-30
Instant Recovery details: VM startup
NFS vmdk is
read-only
LAN
SAN
Write
Media NFS ESX Datastore Access
server Datastore servers (VMDK files) DS
1 2
NetBackup File System Service VM is created with write
(NBFSD) mounts the disk storage access to a existing
unit as NFS Read-Only Datastore. datastore (DS)
31
In normal operation for instant recovery for VMware the media server exports the
datastore, making the backup image available as an NFS mount.
ESX server will import that NFS mount, establishing it as a datastore.
A snapshot of the VM is made. ESX sets up temporary write access to local data store
for any changes needed by the VM.
ESX infrastructure will then start virtual machine. The NFS VMDK remains read only.

11-31
Instant Recovery details: Recovery completion
IRV can be used for Storage vMotion can be used to

file recovery migrate the VM to production
LAN
SAN
Write
Media NFS ESX Datastore Access
server Datastore servers (VMDK files) temp DS
The NFS Datastore is

unmounted when no
longer needed.
32
After the machine is up and running it can be used for normal file recovery. It is a fully
functioning virtual machine so it can actually be used to process data.
In many cases the virtual machine will be migrated to production storage. Production
storage is generally highly available and higher performance than an NFS datastore
exported from a NetBackup media server.
The NFS datastore is unmounted when no longer needed.
Note that the slide illustrates the process assuming that the NetBackup media server is
also the VMware restore host. In the case where the media server and restore host do
not reside on the same server, each is responsible for different behaviors during this
process:
1. NBFSD on the media server handles the export phase of NFS of Instant Recovery for
VMware (IRV). The VM will reside on the file system on the media server.
2. NBFSD on the restore host handles the mount phase of NFS of IRV.
3. bpVMutil on the restore host handles the VM activation.

11-32
Instant Recovery for VMware setup requirements and caveats
IRV setup requirements IRV caveats

• Services for Network File System (NFS) must be • Storage unit must be BasicDisk, AdvancedDisk,
enabled on media servers and restore hosts. PureDisk or qualified OST devices.
• Client for NFS service may have to be restarted on • Supports full backups and incremental backup
the restore host. schedules with NetBackup Accelerator.
• IPv4 is required on the media server. • Does not support:
If using IPV6 add entry to the /etc/hosts file on the – VM where disks are excluded from backup.
ESX server, such as: – VM with disk in raw device mapping mode (RDM) or
10.65.33.245 esx2.example.com in Persistent mode.
• NetBackup requires login credentials for the – VM templates.
vCenter server and the restore host. • ESXi supports only NFS version 3 over TCP/IP
• Restore host can be a Windows host, Linux host, or Using UDP will fail.
NetBackup appliance • Use esxcfg VMware command line utility to
troubleshoot NFS problems in VMware ESXi.
33
Requirements for instant recovery for VMware require network file system operation on
the media server and any restore host.
• The target ESX server for the restore must be vSphere 5.0 and later.
• The client for NFS service has to be operational on the NetBackup restore host.
• The media server must use IPv4.
• There has to be access between NetBackup and the vCenter server in order to
access the VADP API that underlies the service.
Refer to the slide for information on caveats, supported, and unsupported

configurations for Instant Recovery for VMware.
Refer to the NetBackup for VMware Administrator's Guide for further caveats.

11-33
Instant Recovery Options
• NetBackup 7.7 and later

NetBackup plug-in • vCenter Server 5.5 and later
for VMware vSphere • vSphere Web Client 5.5 and later
Web Client • ESX server 6.0 and later
• Supported NetBackup master server platform
• NetBackup 7.6.1 or later

The nbrestorevm • ESX server 5.0 or later
command • Example command:
nbrestorevm –vmw –ir_activate
–C winvm1.example.com –temp_location VM-DS1
34
In NetBackup 7.7 and later Instant Recovery can be performed using the NetBackup
plug-in for the vSphere Web Client or from the command line using the nbrestorevm
command. The plug-in supports standard recovery, instant recovery and monitoring of
backups of virtual machines that vCenter servers manage.
The NetBackup plug-in for vSphere recovery wizard has the following requirements:
• NetBackup 7.7 and later.
• vCenter Server 5.5 and later.
• vSphere Web Client 5.5 and later

• ESX Server 6.0 and later
• The plug-in supports any web browser that the vSphere Web Client supports.
• The NetBackup master server's operating system must be set to the UTC time zone.
• These NetBackup master server platforms are supported: Windows, Red Hat, SUSE,
Solaris SPARC and Solaris x86.
• The NetBackup Web Services must be enabled on the NetBackup master server.
These services are enabled by default on NetBackup 8.0 and later.

11-34
Viewing VMware state prior to instant recovery
Custom Resource Map from VMware vSphere Client

35
This VMware vSphere Client (not the vSphere Web Client) resource map shows the
resources and the noted connections.
This diagram shows, the ESX Server (esx2.example.com), the datastores (INT_ESX2_DS1
and INT_ESX2_DS2), the network, and virtual machines (winvm1 and lnxvm2) prior to
activating an instant recovery. Currently the two virtual machines are located on the
INT_ESX2_DS1 datastore.

11-35
Viewing VMware state after instant recovery
NFS datastore and recovery

VM appear in VMware
vSphere client map
Custom Resource Map from VMware vSphere Client
36
The Instant Recovery was successful. In this example, a new temporary NFS datastore,
NBU_IR_winmaster, is recognized and used by ESX for the new virtual machine,
clonelnxvm2, that was added to the environment.

11-36
Accessing NetBackup Plug-In Recovery Wizards
Classic Instant
Recovery Recovery
Recovery
Workflow
37
Navigating to the Symantec NetBackup section, there are five available selections:
• Recovery Wizard is used to perform a standard recovery (restore) of virtual
machines.
• Instant Recovery Wizard is used to perform an instant recovery of virtual machines.
• Instant Recovery Cleanup is used to power off and delete virtual machines created
by Instant Recovery which are no longer needed
• Virtual Disk Exclusion Wizard is used to configure and apply a Custom Attribute to a
virtual machine or multiple virtual machines for excluding disk(s) from NetBackup
backups
• Register Master Servers is used to register NetBackup master servers with the
vSphere plug-in. This is a pre-requisite for using either of the recovery wizards.
• Settings is used to configure recovery wizard settings

11-37
Registering A Master Server in the vSphere Web Client
38
Adding a backup server to the vSphere Web Client requires you to generate an
authorization token on the NetBackup master server.
The authorization token is generated using the manageclientsCerts command,
Execute the manageclientsCerts command from a Command prompt, not a
Windows Explorer window.
Use the -create option and the name of the host as the argument.
Once that authorization token has been generated you'll need to transport it over to the
vCenter machine using a shared drive. You then upload it into the vSphere Web Client to
permit the vSphere NetBackup Web Client to communicate securely to the NetBackup
Master.

11-38
Changing NetBackup settings in the vSphere Web Client
39
The settings window allows you adjust the settings that the recovery wizards use.

11-39
Starting the Instant Recovery Wizard
40
The Instant Recovery Wizard provides a graphical interface that allows you to instantly
recover VM’s from the VMware vSphere Web Client. The Instant Recovery Wizard
provides five steps to determine important aspects of how a recovery is going to be
carried out. You can see the similarity between these steps and the steps used in Instant
Recovery from the command line using nbrestorevm on the NetBackup master
server.
You can select which vCenter Server and which NetBackup master server to query and
then search for a machine using its display name, UUID, DNS name or hostname. There
are some wildcard searches available in the selection box.

From the Search Results, select the virtual machine(s) on which you wish to perform
Instant Recovery and click the Add Virtual Machines button.

11-40
Adding a Virtual Machine for Instant Recovery
41
After clicking the Add Virtual Machines button, the number of VMs selected is shown at
the top of the screen. Click the Next button to continue.

11-41
Image Selection
42
Use the Change link to select the specific image you wish to use as the source for the
Instant Recovery. The slide above shows only three images but in a production
environment you would likely have many images to choose from. Details about each
image can be viewed in the Backup Details pane.

11-42
Destination Selection
43
Select the destination for Instant Recovery. Destination selection permits alternate
directory and alternate client choices.
Once the VM is recovered, applications can immediately be started or the local
administrator can recover files and objects. The case may be that only a subset of the
recovery is wanted.
Alternate Data Center selection and resource pool gives greater flexibility in recovery
operations. The recovery could be part of a non-production exercise and it would be
contrary to enterprise data center policy to have non-production virtual machines
running in a particular VMware Data Center.

11-43
Virtual Machine Options
44
There are virtual machine options on recovery:

• To power on the virtual machine after recovery
• To retain networks after recovery
• To change the Display Name
The display name of the virtual machine can be changed during recovery specification.
In many cases there will need to be a distinction between a Virtual Machine started for
recovery versus the same machine running in production.

11-44
Review Selections and Pre-Recovery Check Results
45
The recovery settings are displayed. Review the selections you have made and run the
pre-recovery check for a report on access and resources available for the recovery.
A number of resource allocations are checked in this and potential problems of the
recovery are uncovered. As virtual machines in real world production can span multiple
terabytes, discovery of problems early in the process is highly desirable.
At this point all resource checks have returned successful and the restore is ready to
start. Click the Finish button to exit the wizard and recover the VM. The virtual machine
will be powered on from the backup storage and is available for use when the Activate
Instant Recovery job in the NetBackup Activity Monitor completes. Note that the VM
Instant Recovery job will remain in the Active state until it is deactivated by running the
Instant Recovery Cleanup wizard.

11-45
Viewing IRV jobs in the Activity Monitor
Activity Monitor displays the

job and it’s status.
Job Details includes IR

identifier used with
nbrestorevm commands
46
The progress and status of the instant recovery job is reported in the Activity Monitor.
The Detailed Status pane includes the key details of the restore job, including the
VMware identifier.
This VMware identifier is used in other commands and is reported in the
nbrestorevm –ir_listvm command to list details about activated virtual
machines, as is shown on the following slides.
The VMware identifier is used as a parameter to some nbrestorevm commands. It is
distinct from the NetBackup Job ID.

11-46
Datastores associated with the recovered VM
INT_ESX2_DS2: temporary datastore (writes)

NBU_IR_winmaster_esx2: temporary NFS datastore (read-only)
47
The new VM, clonelnxvm2, is now associated with 2 datastores, INT_ESX2_DS2 and
NBU_IR_winmaster_esx2. The NBU_IR_winmaster_esx2 is the temporary NFS
datastore where the backup image of the virtual host is located. The INT_ESX2_DS2 in
the temporary datastore for all write requests for the recovered virtual machine. If the
VM is to remain operational for any length of time it should be migrated (vMotion) off
the temporary datastores (INT_ESX2_DS2 and NBU_IR_winmaster_esx2) and then
Instant Recovery Cleanup can be run to complete the Instant Recovery job. It is not
recommended to leave recovered VM on the temporary datastores.

11-47
Migrate the recovered VM (optional)
48
Once the Activate Instant Recovery job in the NetBackup Activity Monitor has
completed successfully, the VM can be used for any purpose. Applications can be
started and/or files can be copied off the recovered VM. Since the VM is running off of
the backup storage performance will likely be degraded. If the VM is to remain
operational for any length of time, it is best to use vMotion to migrate the VM to a
production datastore.

11-48
Instant Recovery Cleanup
49
The Instant Recovery Cleanup screen has three options you can select for a recovered
VM:
• Instant Recovery Done: Use this operation to complete the instant recovery
operation after you have performed the Storage vMotion of the virtual machines to
a different datastore. This utility completes the virtual machine instant recovery
operation after the vMotion migration of the virtual machine is completed. When
the datastore is removed, its resources are released on the NetBackup media server.
• Deactivate: Use this option when you are done with the restore and do not intend
to retain the restored virtual machine. This action removes the virtual machine from
the ESX host. If no other virtual machine is using the NetBackup datastore, this
option removes that datastore and releases its resources on the NetBackup media
server.
• Reactivate: Use this operation when connection to the virtual machine was
interrupted. The interruption may occur due to a network disconnect between the
NetBackup media and the ESX server. This utility reactivates a restored virtual
machine by remounting the NetBackup datastore. It also registers the restored
virtual machines on the ESX host.

11-49
Instant Recovery Cleanup Example
50
At this point, vMotion can be use to migrate the recovered virtual machine to a
production datastore. From the Instant Recovery Cleanup screen you can initiate a
Instant Recovery Done, which completes the virtual machine instant recovery operation
and the resources are released on the NetBackup media server. The NetBackup Activity
Monitor now shows that all Instant Recovery operations are complete. Other options on
the screen are the Deactive, which deletes the restored virtual machine and the
Reactivate which reactivates a restored virtual machine by remounting the NetBackup
datastore. It also registers the restored virtual machine on the ESX host.

11-50
Running nbrestorevm
• To list details about the activated VM use:

nbrestorevm -ir_listvm
C:\Program Files\Veritas\NetBackup\bin> nbrestorevm -ir_listvm
VM Instant Recovery ID: 5
VM Type: VMware
VM Display Name: clonelnxvm2
vCenter Server Name: 10.10.2.65
ESX Host Name: esx2.example.com
Temporary location for writes: INT_ESX2_DS2
NetBackup datastore name: NBU_IR_winmaster_esx2
Media Server Name: winmaster.example.com
Backup ID: lnxvm2_1513013050
• To deactivate or delete the VM use:

nbrestorevm -ir_deactivate instant_recovery_ID
C:\Program Files\Veritas\NetBackup\bin> nbrestorevm -ir_deactivate 5
Are you sure you want to deactivate or delete the virtual machine with identifier 5
y/n (n)?y
VM Instant recovery deactivate request returned with status = 0
C:\Program Files\Veritas\NetBackup\bin> nbrestorevm -ir_listvm

No activated VM record found
51
The nbrestorevm –ir_listvm command produces a listing of details of active

nbrestorevm jobs. The instant recovery ID is listed. The Backup ID is listed as well. You’ll
note they are different.
The nbrestorevm command with the –ir_deactivate stops the virtual

machine, deletes the virtual machine from the VMware inventory, and may unmount
the NFS file system, if no other virtual machines use the vmdk files served by the file
system.

11-51
Viewing VMware start of nbrestorevm
–ir_deactivate
• Virtual machine has been deleted
• NB_ datastore has been unmounted by ESX
52
This VMware vSphere Client resource map shows the resources and the noted
connections.
After the nbrestorevm –ir_deactivate is successfully executed, the virtual
machine is deleted.
The NFS data store is also unmounted if the virtual machine identified with the VMware
Recovery ID is the last one to use a vmdk file on that mount.

11-52
Running nbrestorevm with additional options
Command option Description
-ir_done ir_ID Complete the VM instant recovery job after the data is migrated
-ir_reactivate ir_ID
Reactivate a VM that was interrupted during recovery
[-force]
-vmpo Power on the VM
• Remove the VM network interface

-vmsn
• Avoids duplicate IP address if VM recovered on original subnet
• Restore VM to a different location

• Example file contents:
change esxhost to new_ESX_host
-R rename_file_path change resourcepool to new_res_pool
change vmname to new_VM_name
change network to new_network
53
The command set options of –ir_done will end an instant recovery job. The VM will
be stopped, then deleted. The imported NFS mount from the media server will be
unmounted by the ESX host. The function of ir_done and ir_deactivate are
identical, if the datastore does not support other active IRV virtual machines.
If the VM recovery ID is gone due to a ir_deactivate option in a command, the
ir_reactivate will fail.
There is a –force option that suppresses command prompts “yes or no” in the
command lines.
Other options to the nbrestorevm command allow you to power on the virtual
machine, remove the virtual network interface from the virtual machine, or invoke a
rename file.
In the rename file the virtual machine host, resource pools, and networks can all be
changed. Example syntax of this file is shown on the slide. There is a specific syntax that
must be followed in the rename file.

11-53
Lesson summary
• Key points
– In this lesson, you learned about restoring VMware virtual machines and support for Instant Recovery
– You also about Instant Recovery for VMWare
– NetBackup for VMware Administrator’s Guide
– NetBackup Plug-in for VMware vSphere Web Client Guide
– Article 000006177: Support for NetBackup 7.x and 8.x in virtual environments
54

11-54
Lab 11: Performing Virtual Machines Restores
Lab objectives
• Recovering virtual machine files
• Recovering a VMware virtual machine disk
• Recovering an entire VMware virtual machine
• Performing NetBackup pre-requisite tasks for Instant Recovery for VMware (IRV)
• Performing Instant Recovery for VMware (IRV)

11-55
What did you learn?
lesson.
56
current lesson.

11-56
Question: VMware and Hyper-V backups
Which statement about VMware and Hyper-V backups is true in NetBackup?
A. Users must log off virtual machines to ensure consistent backups.

B. You can restore selected files from full backups of virtual machines.
C. Virtual machines must be powered on to be backed up.
D. You can restore VMware virtual machine full backups to Hyper-V virtual machines.
57

11-57
Answer: VMware and Hyper-V backups
Which statement about VMware and Hyper-V backups is true in NetBackup?
A. Users must log off virtual machines to ensure consistent backups.

B. You can restore selected files from full backups of virtual machines.
C. Virtual machines must be powered on to be backed up.
D. You can restore VMware virtual machine full backups to Hyper-V virtual machines.
The correct answer is B. Both VMware and Hyper-V virtual machine backups support restoring selected files or
directories from full backups, as long as the virtual machine backup was performed with the Enable file recovery from
VM backup policy option.
58

11-58
Question: BAR console selection
What should be selected as the source in the BAR console for a restore of individual files
backed up using a VMWare policy?
A. The hostname of the VM.

B. The identifier for the VM used in the VMWare policy
C. The Media server that backed the client up
D. The VMWare backup host that performed the backup
59

11-59
Answer: BAR console selection
What should be selected as the source in the BAR console for a restore of individual files
backed up using a VMWare policy?
A. The hostname of the VM.

B. The identifier for the VM used in the VMWare policy
C. The Media server that backed the client up
D. The VMWare backup host that performed the backup
The correct answer is B. Whatever identifier was used in the backup policy should be used. This is sometimes the
hostname but it might also be a different identifier such as the Display Name or UUID.
60

11-60
Question: Cleanup Wizard for IR
From where is the Cleanup Wizard for Instant Recovery launched?
A. From the NetBackup Administration Console

B. From the vSphere Client for Windows
C. From the NetBackup Plug-in for VMware vSphere Web Client
D. From the command line on the NetBackup Master Server
61

11-61
Answer: Cleanup Wizard for IR
From where is the Cleanup Wizard for Instant Recovery launched?
A. From the NetBackup Administration Console

B. From the vSphere Client for Windows
C. From the NetBackup Plug-in for VMware vSphere Web Client
D. From the command line on the NetBackup Master Server
The correct answer is C. The graphical Instant Recovery and Instant Recovery Cleanup wizards are found in the
NetBackup Plug-in for VMware vSphere Web Client
62

11-62
End of presentation
11-63
Lesson 12: Duplicating Backups Using Storage Lifecycle

Policies
This is the “Duplicating Backups” lesson in the “Veritas NetBackup 8.1: Administration”
course.

12-1
Policies
This lesson is the twelfth lesson in this course.


12-2
Lesson objectives
Topic Objective
Backup duplication concepts Identify backup duplication concepts such as inline backups, manual
duplication, basic disk staging, and storage lifecycles.
Storage lifecycle policy concepts Describe configuration options for storage lifecycle policies.
Using storage lifecycle policies Create and initiate a storage lifecycle policy.
Additional Storage Lifecycle Policy Explain additional benefits and features of SLP, such as optimized
features and benefits duplication, Auto Image Replication, and Data Classification.

12-3
Topic: Backup duplication concepts
After completing this topic, you will be able to identify backup duplication
concepts such as inline backups, manual duplication, basic disk staging, and
storage lifecycles.
After completing this topic, you will be able to identify the duplication backup types,
including inline, manual duplication, basic disk staging, and storage lifecycle.

12-4
Duplication strategy: Duplicate after backup
• Provides additional copies of backup data

• May enable organizations to meet their backup windows
• Can be performed manually, or automated using various NetBackup features
Client data
Onsite
Backup Duplicate
The default behavior for most backup applications is to configure a client backup to a
backup storage destination, which results in a backup image. Although this provides the
ability to perform a restore, what happens when that backup image is unavailable, or
destroyed, or corrupted?
Duplicating backup images allows for redundancy, and for other restore requirements to
be met. There are a number of duplication strategies available.
One of the simplest and oldest strategies is to duplicate images that have already been
created. This is the traditional solution when you are faced with a tight backup window.
Backup images are created during the backup window, and the duplication is performed
at a later time. Because there is no impact to the clients for duplication, the duplication
was traditionally performed during business hours when tape drives were idle. This may
be a solution if your environment has strict windows during which backups need to
complete.

12-5
Duplication strategy: Multiple inline copies
• May enable organizations to meet their backup windows

• Up to four copies can be created in parallel, using multiple tapes or disks.
• Tape copies can be immediately vaulted offsite.
• The speed of the backup is driven by the slowest media.
Client data
Onsite
Backup
Multiple inline copies refers to creating simultaneous backup images at the time of the
backup. This strategy is very efficient because data from client to media server only
travels across the backup infrastructure once. This strategy also provides excellent data
protection because copies may be sent offsite immediately after the backup has
completed.
The disadvantages of this strategy are that it requires additional resources during
backup time, and the overall backup speed is equal to that of the slowest media to
which data is being written.
Also, features are restricted based on the lowest level of backup destination. For
example, you cannot run a Granular Restore Technology (GRT)-based backup, which
normally requires a disk destination, to both disk and tape.

12-6
Duplication strategy: Vaulting tapes
• Ensures data is available in case of site failure

• Can be managed manually, or with automated features
• May require physically moving the media
Client data
Onsite Offsite
Backup Duplicate Vault
Vaulting generally refers to the movement of long term storage, normally tapes, to an
off-site location, or vault. The vault provides a level of site-redundancy, so that even if
there is a primary site failure, all the backup data can be restored from the secondary
site.
In some cases, the backup software may assist with this process, and in other ejecting
tapes and managing tape rotation must be performed manually by the administrator.
Traditionally, the term “vaulting” referred to the process of moving tapes offsite,
implying that the target location was similar to a protected, physical vault. In modern
parlance, “vaulting” refers to the process of getting backup images to an offsite location
that provides redundancy from primary site failure. In cases where this data is disk-
based, it normally involves sending the data through the network, and may not involve
physically moving tapes.

12-7
Duplication strategy: Optimized duplication and replication
• Duplication refers to copying an image within a NetBackup domain.

• Replication refers to copying an image across NetBackup domains.
• Optimized duplication
– Performed between supported vendor storage.
– Copies an image directly between storage servers.
– Uses the underlying storage features to minimize bandwidth use.
– Used during duplication and replication jobs.
Uses
Can use
Client data optimized
Onsite duplication Offsite
Backup Duplicate Replicate
In NetBackup, replication is copying data from one storage location to another, between
different NetBackup domains. Note that different backup and storage vendors may use
the term replication in different ways, which may or may not match the NetBackup
definition.
Optimized duplication is NetBackup’s ability to take advantage of features within the
disk appliance to:
• Copy an image between appliances without sending data through a separate media
server.
• Reduce workload on the NetBackup media servers, which allows more backups to
be performed.
• Perform duplication faster, in the background, simultaneously with ongoing backup
jobs.
• Used during duplication and replication jobs.
Optimized duplication takes advantage of NetBackup Open Storage Technology (OST) to
use the features available in the disk appliance to optimize the duplication or
replication.
One of the main restrictions of optimized duplication is that the source and target disk
appliances need to support each other. In most cases, this means that the technologies
must be identical.

12-8
Duplication strategy: Combined approach
• Combine multiple features to meet service level agreement (SLA) and redundancy
requirements:
– Inline copies, duplications, and staging for onsite redundancy
– Replication to remote sites for offsite redundancy
– Duplication at remote site to provide vaulting without shipping tapes
• NetBackup Storage Lifecycle Policies (SLP) are built to easily support a consolidated
approach.
Client data
Onsite Offsite
Vault
Backup
Replicate Duplicate
For many environments, choosing a combination of strategies is the best way to meet
service level agreements and redundancy requirements.
NetBackup storage lifecycle policies help to automate and provide flexibility in designing
a disaster recovery strategy for backup data that facilitate a combined approach. SLPs
also support additional NetBackup functionality, such as Replication Director and Auto
Image Replication, and can automate tape duplication on remote sites to avoid
manually vaulting tapes. These features are discussed elsewhere in this lesson.

12-9
NetBackup duplication features
Manual • Performed in Administration Console or bpduplicate command
duplications • Requires manual or scripted execution
Traditional • Configured in policy’s Schedule window

inline copies • Only provides copy at time of backup
Basic disk • Configured in BasicDisk storage units only

staging (DSSU) • Has limited configurability and scheduling
NetBackup • Able to schedule duplications

Vault • No support for replication, third-party snapshots, Data Classification
Storage • Performs inline copies and immediate or scheduled duplication

Lifecycle • Supports replication, some third-party snapshots, and Data Classification
Policies • Supports all storage destinations except BasicDisk
10
NetBackup has a number of features that support duplicating backups, many which
were introduced in different versions of the product. Some general strategies include:
• Manual duplications are performed in the NetBackup Administration Console or
with the bpduplicate command. Although this normally requires manual work, in
some cases a third-party scheduler can be used to automate these functions.
• Traditional inline copies are configured in the backup policy’s Schedule window.
This allows up to four simultaneous copies of a backup to be performed.
• Basic disk staging storage units (DSSU) provides a method to initially send backup
images to a disk and then later (as specified in the disk staging schedule) copy the
images to another media type. It provides little configurability, and the same backup
destination folder, schedule, and retention are used for all duplication jobs.
• NetBackup Vault provides functionality for automated duplication of backups, and
ejecting of tapes, but does not support more sophisticated features such as inter-
domain replication, third-party snapshots, or NetBackup Data Classification.
• Storage Lifecycle Policies combine duplication features in one consolidated view
that provides inline copies, immediate or scheduled duplications, intra- or inter-
domain replication, support of some third-party snapshot technologies, and support
for NetBackup’s Data Classification feature. The only limitation with SLPs is that they
do not support BasicDisk storage units. SLPs are the focus of this lesson.

12-10
Promoting a copy to a primary copy
2
1
bpchangeprimary
bpduplicate –npc primary_copy –backupid backup_id
11
One backup in the NetBackup catalog is assigned as the primary copy. NetBackup uses
the primary copy to satisfy restore requests from the GUI. When using the command
line, it is possible to specify the copy to use. Normally the first backup image created
successfully for a specific backup job is the primary copy. If the primary copy expires
first, the second copy is automatically promoted to become the primary copy. If the
primary copy is unavailable and you have created a duplicate copy of that backup, select
a copy of the backup and set it to be the primary copy. Setting a backup to be the
primary copy is a function of the image catalog only; it is not a function of the media.
To promote a backup copy to a primary copy:

1. In the object tree pane of the NetBackup Administration Console, select NetBackup
Management > Catalog.
2. Set up the search criteria for the image that you want to promote to be a primary
copy.
Note: When specifying your search criteria, ensure that you indicate a copy in the
Copies field and not Primary Copy.
3. Click Search Now.
4. Right-click the image that you want to promote and select Set Primary Copy from
the shortcut menu.

12-11
Topic: Storage lifecycle policy concepts
After completing this topic, you will be able to describe configuration

options for storage lifecycle policies.
12
After completing this topic, you will be able to describe configuration options for
storage lifecycle policies.

12-12
What is a storage lifecycle policy?
AA
policy
storage
canlifecycle
be sent to
policy
a storage
is an automated,
unit backupreusable
destination,
backup
but storage
is limited
planinbased
how onbackup
the business
copies are
value
duplicated.
of the data.
Who? What?
When? How?
Where? = Backups + Duplicates
Backup Storage
Storage unit Back up to tape, Duplicate to tape, retain 6
policy 1 1 1
lifecycle retain 1 month months
Backup
policy 2 Back up to disk, Duplicate to:
Storage
Storage unit
2 2
retain until • Disk, retain 2 months
lifecycle
Backup duplicated • Tape, retain 1 year
policy 3
Also called SLP, storage lifecycles, or lifecycles
13
A storage lifecycle policy is an automated, reusable backup storage plan. Combined with
features inherent in storage units, and additional features such as Data Classification
with AdvancedDisk storage, SLPs allow for greater control in basing your backup strategy
on the business value of the data.
Storage lifecycle policies may also be called SLPs, storage lifecycles, or lifecycles.

12-13
Storage lifecycle benefits and characteristics
Reduced administration
• Automated inline copies, duplications, and replications
• Managed disk capacity and supports the Data Classification feature
Reduced risk
• Automated duplication job restarts after failures
• Less opportunity for administrative errors
• Data does not expire until copy is successfully created
More configurability
• Additional staging locations: All except for basic disk
• Additional retentions: Fixed, capacity managed, staged, and expire after copy
14
Storage lifecycles policies (SLPs) enable you to create a storage plan for similar types of
data. After an SLP is created and configured, it can be used as often as it is needed. This
reduces administration errors. SLPs also provide a single place to view the storage plan.
Prior to SLPs, administrators needed to look in several places to view similar
information.
Using an SLP guarantees that all destinations in the lifecycle are written. The
destinations are retried as necessary until the SLP is satisfied or until the backup or
duplication is cancelled by the administrator. SLP images that have not been successfully
written do not expire, even if they have passed their retention, until all destinations
have been satisfied.
Using SLPs, you can now write the primary copy of the (temporary) staged image to all
supported disk types (except basic disk), including tapes and virtual tape libraries (VTL).
Additionally each lifecycle destination can have its own retention.
SLPs have the following characteristics:
• Destinations: The location where the backup or duplication copy is sent.
• Destination type: This can be a backup, duplication, replication, snapshot, and
import, depending on the function that is desired.
• Retention type: Each destination in the lifecycle can be configured for a unique
retention and retention type (Fixed retention, Staged capacity managed, or Expire
after copy). Retention types are described in more detail elsewhere in this lesson.

12-14
Topic: Using storage lifecycle policies
After completing this topic, you will be able to create and initiate a storage
lifecycle policy.
15
After completing this topic, you will be able to create and initiate a storage lifecycle
policy.

12-15
Prerequisites to creating a storage lifecycle
1
Design a data • Do not overlap backup images between SLPs and other NetBackup duplication
protection features.
strategy • Avoid mixing capacity-managed and fixed retention images on disk volumes.
2
Configure
physical Such as tape libraries, tape drives, tapes, and disks.
resources
3
Configure logical Such as volume pools, disk pools, storage servers,
resources storage units and storage unit groups.
4
Configure any
relevant host Such as data classifications.
properties
16
The slide shows tasks that must be performed before you create storage lifecycles.
1. Design a data protection strategy. Consider these best practices:
• Do not write capacity-managed images and fixed-retention images to the same
volume in a disk storage unit. The volume may fill with fixed-retention images
and not allow the space management logic to operate as expected.
• Do not write images to a volume in a disk storage unit within a lifecycle and to
the same volume (by the storage unit) directly from a policy.
• Mark all disk storage units that are used with lifecycles as On demand only.
• Check any storage unit groups to ensure that fixed and capacity-managed
images cannot be written to the same volume in a disk storage unit.
2. Ensure that all physical resources have been recognized by the OS and configured in
NetBackup, including robots, tape drives, tapes, and disks.
3. Create and configure all of the logical resources, including volume pools, disk pools,
storage servers, storage units, storage unit groups, and server groups.
4. Configure the Maximum backup copies (only required in versions prior to
NetBackup 7.6.1) and Data Classification master server host properties before
creating storage lifecycles.

12-16
Creating a new storage lifecycle policy
17
To create a storage lifecycle policy, in the NetBackup Administration Console, expand

NetBackup Management > Storage. Right-click Storage Lifecycle Policies and select
New Storage Lifecycle Policy.
The New Storage Lifecycle Policy dialog box is displayed.

12-17
The New Storage Lifecycle Policy dialog box
18
Complete the dialog box as follows, and then click Add.

• Storage lifecycle policy name: Type the lifecycle name.
• Duplication job priority: Select the priority that the duplication jobs in the lifecycle
has in relationship to all other jobs. The range is: 0 (default) to 99999 (highest
priority).
• Data classification: Select the data classification for the storage lifecycle. The default
is No data classification.
Note: The data classification of the backup policy and the storage lifecycle must
match. Storage lifecycles of different classifications are not available as backup
destinations in the policy.
The New Operation dialog box is displayed. The options available in the dialog box
depend upon the type of operation (backup, snapshot, import, duplication, and so on)
and the type of storage unit (tape or disk). Many of these operation types are
introduced in this lesson.

12-18
Configuring backup storage operations
Tape
• Fixed: Guarantees image retention

• Expire after copy retention: Expires
image after duplication completes
Disk
Volume pool and

Media owner are only
available for tape.
Capacity managed: Expires image based

on space availability (AdvancedDisk only)
19
The following describes the options for backup storage operations:

• Volume pool: Select the volume pool for the backup (tape only).
• Media Owner: If you have server groups configured for media sharing, you can
select a server group as the media owner (tape only).
• Retention Type: Select one retention type.
• Fixed: A fixed retention is the only guaranteed retention. At least one backup or
duplication in the lifecycle must have a fixed retention period.
• Expire after copy: Select this retention type to have this backup expire after the
duplication has finished.
• Capacity managed (AdvancedDisk only): Select this retention type to enable
NetBackup to manage the space on the disk. This retention type is used in
conjunction with data classifications. The Desired cache period is the desired
time for the backup image to remain on the disk.

12-19
Configuring duplication storage operations
• Scheduled automatically after

backup jobs complete successfully
• Window tab allows customized
duplication start windows
Snapshot and Replication operation

types are discussed in the NetBackup:
Advanced Administration course.
20
The following describes options specific to duplication operations.

• Source storage: Shows the storage device where the backup was sent, from which
this duplication makes its copy.
• Alternate read server: This field specifies the name of the server that is enabled to
read a backup image that was originally written by a different media server. This
option is available for Duplication operations only.
• Preserve Multiplexing: The original backup storage destination may have used
multiplexing to interleave multiple backup streams for improved backup

performance. If this is the case, by default a duplication does not preserve that
multiplexing, and instead copies the backup image pieces one after another to
create a complete backup image for the new backup image copy. Select this
checkbox to preserve the multiplexed image.
Note: To add a Duplication operation, a Backup operation in the Storage Lifecycle Policy
dialog needs to be selected prior to clicking the Add button.

12-20
Configuring duplication windows
Default_24x7_Window allows
duplications to run as soon as
backups complete
Customized windows
allow for start windows
and exclude dates
21
Secondary operation windows allows the administrator to restrict when duplication

jobs, and other secondary operations, are allowed to start. Secondary operation
windows were introduced in NetBackup 7.6. Prior versions of NetBackup started
duplications shortly after the initial backups completed, only. This behavior is still the
default behavior when using the Default_24x7_Window.
The following describes the options for duplication, snapshot, and replication storage
operations.
• Select from saved windows: Allows you to use an existing, defined SLP window. The
default window shown is Default_24x7_Window, which allows duplications to occur

anytime. This has the effect of duplicating a backup soon after the original backup
completes.
• Create new: Allows a new SLP window to be created within the New Operation
dialog box.
• Start Window: Similar to policy schedule windows, this defines the time during
which duplication jobs are allowed to start.
• Exclude Dates: Provides the capability to exclude specific days during which
duplications do not run.

12-21
Configuring duplication hierarchy
• Backups run first, as inline copies.

• Duplications are scheduled using the backup copy to
which they are assigned in the hierarchy.
• Multiple levels of duplication hierarchy can be configured.
Buttons enable the administrator to

customize the hierarchy.
22
A hierarchical duplication destination is a duplication destination that uses a specific

source for duplication. It is always indented under a backup destination or another
duplication destination. A hierarchical duplication destination can have siblings that
duplicate based off of the same Backup operation.
The source (or parent) for a hierarchical destination is the destination that appears
above the destination in the hierarchy. The source can be a backup or a duplication
destination.
If a hierarchical duplication destination has children, it serves as the source for the
children.
Non-hierarchical duplication destinations no longer exist in current versions of
NetBackup, however earlier releases allowed you to specify a Duplication which did not
have a strictly defined parent. In these cases, a parent backup was chosen for you, as
any backup that is marked as the primary copy can provide the source for a non-
hierarchical duplication destination.

12-22
SLP restrictions
• SLP inline copies:

– Limited to four Backup operations.
– All Backup operations must go to the same media server.
– Multiple copies (traditional inline copies) setting on a policy schedule cannot be selected when using
SLPs:
• SLP versions:
– Allow SLPs to be modified safely any time.
– Tagged within a running job (and viewed using nbstl command).
Already running jobs continue to use the corresponding SLP version.
– Cleaned up per SLP Parameters host properties, when no longer used.
23
This slide discusses some SLP restrictions and additional information.

Inline copies is the process of writing a backup to multiple locations simultaneously.
There is a limit of four Backup storage destinations per storage lifecycle. NetBackup will
not allow you to save the SLP if it has more than four backup storage destinations.
Similarly, all backup copies must be directed to storage units on the same media server.
The storage units may be different, as long as they are on the same media server. If a
storage lifecycle has more than one backup destination configured, the multiple copies
option is no longer needed, and is therefore disabled in the policy schedule.
The ability to create SLP versions lets administrators safely modify a definition without
waiting until all of the copies that are associated with the SLP have been processed.
Each copy that an SLP manages is tagged with the SLP name and the SLP version
number. These two attributes are written into the image header, in the NetBackup
image catalog. Whenever an administrator creates or changes an SLP, NetBackup
creates a new version (between 0 and n). New jobs use the most recent SLP version.
When a new job is submitted, it is tagged with the most recent SLP version number. The
processing of a copy that is associated with a version remains fixed according to that
version of the SLP definition. It is fixed at job time and does not change, unless the
administrator uses the nbstl command to modify an existing version. Old, unused SLP
versions are cleanup up according to master server host properties > SLP Parameters.

12-23
Example SLP scenario
(1 month)
master_msdp_stu
NetBackup master
Client data / media server
Backup
Backup Duplicate
master_advdisk_stu master_tape_stu
(Expire after copy) (3 months)
24
This slide illustrates a scenario in which a storage lifecycle policy is used. The following
steps describe the scenario.
1. Perform a backup of a client. In this scenario the backup image is written to an
AdvancedDisk storage unit, master_advdisk_stu. The backup image created on
master_advdisk_stu has an expire after copy retention.
2. Simultaneously, another copy of the backup image is written to the deduplication
storage master_msdp_stu. The retention of the backup image created on there is 1
month.
3. After the backup job completes, the SLP causes a duplication of the backup image
that resides on master_advdisk_stu. This duplicate copy is written to a Media
Manager storage unit, master_tape_stu, and has an assigned retention of 3 months.
Note: After the duplication job has run and the copy is created on tape, the source copy
for the backup which resides on master_advdisk_stu is deleted.

12-24
SLP scenario description
• Backup policy which uses Policy storage: Lab12_SLP1_test.
• SLP contains:
– Backup: master_msdp_stu, fixed retention of 1 month
– Backup: master_advdisk_stu, expire after copy
– Duplication: master_tape_stu, fixed retention of 3 months,
performed during Business_Hours SLP window.
25
To configure the scenario, the LAB12-console-test-slp1 backup policy uses the LAB12-
SLP1_test lifecycle policy storage. The LAB12-SLP1_test policy storage contains the
following destinations:
• A backup goes to the master_msdp_stu storage unit, with a fixed retention of 1
month.
• A backup goes to the master_advdisk_stu storage unit, with retention set to expire
after copy.
• A duplicate goes to the master_tape_stu storage unit, with a fixed retention of 3

months.

12-25
SLP scenario: Monitoring jobs in the Activity Monitor
177. Parent for both backup jobs: Requests all Backup operation resources
178. Primary backup job: Writes to primary Backup operation
179. Inline copy backup job: Writes to second Backup operation
180. Duplication job scheduled by SLP:
– Requests primary Backup and Duplication operation resources
– Even though the lifecycle policy name is Lab12_SLP1_test, the prefix “SLP_” always precedes it in the Job
Policy shown in the Activity Monitor.
– Job Schedule is the SLP window: Business_Hours.
181. Image cleanup: Removes any backups with retention Expire after copy
26
When LAB12-console-test-slp1 runs, the jobs shown in the slide are initiated.

12-26
Viewing SLP details using nbstl -L
Name: LAB12_SLP1_test
Data Classification: (none specified)
Duplication Job Priority:
State:
0
active nbstl -L
Version: 1
Operation 1 Use for: 0 (backup)
Storage: master_msdp_stu
Volume Pool: (none specified)
Server Group: (none specified)
Retention Type: 0 (Fixed)
Retention Level: 3 (1 month)
...
State: active
Source: 0 (client)
Operation ID: (none specified)
Operation Index: 1
Window Name: --
Window Close Option: --
Deferred Duplication: no
Operation 2 Use for: 0 (backup)
Storage: master_advdisk_stu
Volume Pool: (none specified)
Server Group: (none specified)
Retention Type: 2 (Expire After Copy)
Retention Level: 9 (infinity)
...
State: active
Source: 0 (client)
Operation Index: 2
Window Name: --
Window Close Option: --
Deferred Duplication: no
Operation 3 Use for: 1 (duplication)
Storage: master_tape_stu
Volume Pool: duplicate_tapes
Server Group: Any
Retention Type: 0 (Fixed)
Retention Level: 5 (3 months)
...
State: active
Source: Operation 2 (backup:master_advdisk_stu)
Operation Index: 3
Window Name: Business_Hours
27
This slide shows a storage lifecycle policy in the NetBackup Administration Console, with
the corresponding output from the nbstl –L command.
You can see from the output of nbstl on this slide that the Backup operations have a
Source listed of the client directly. The Duplication operation’s source shows the
operation from which it is to be duplicated, based on the SLP hierarchy (in this case,
Operation 1, the backup to AdvancedDisk).

12-27
Customizing SLP Parameters
• Use SLP Parameters host properties to customize how the NetBackup

Storage Lifecycle Manager (nbstserv) manages SLP-related jobs.
• The values shown are the default values in NetBackup 8.1.
28
NetBackup allows customization of SLP behavior by modifying SLP Parameters, found

under the master server’s host properties in the NetBackup Administration Console.
Prior to NetBackup 7.7, a file called LIFECYCLE_PARAMETERS was used to store
these values. Some popular duplication parameters , which are highlighted on the slide,
include:
• Image processing interval indicates how frequently NetBackup looks for completed
backups and decides whether to start a duplication session. Default: 5 minutes.
Minimum: 1 minute.
• Extended image retry interval indicates, after the initial three retries, how long
NetBackup waits before an image copy is added to the next duplication job. Default:
2 hours. Minimum: 1 hour.
• Minimum size per duplication job indicates the size that the batch of images should
reach before one duplication job is run for the entire batch. The SLP only requests a
duplication job when this size is met, or until the Force interval for small job time
has passed. Default: 8 GB.
• Maximum size per duplication job determines how large the batch of images is
allowed to grow before no more images are added to the batch. Default: 100 GB.
• Force interval for small job If the minimum batch size is not reached by the time
indicated, the SLP requests a duplication job regardless. Default: 30 minutes.

12-28
Managing SLPs with nbstlutil
If you want to … Then type ….
nbstlutil cancel
Cancel storage lifecycle –lifecycle name –destination name
operations* or
-backupid image_id_value
nbstlutil inactive
Deactivate lifecycle operations –lifecycle name –destination name
(suspend) or
nbstlutil active
Activate lifecycle operations –lifecycle name –destination name
(resume) or
nbstlutil list –U
–lifecycle name –destination name
List lifecycle operations –client name –mediaid value
-mediaserver name –storageserver name
* Caution: Will prevent dependent lifecycles, which may result in loss of backup copies.
29
Use the nbstlutil command to view and manage the duplication automation in
storage lifecycles. The slide shows some of the options that can be used with this
command:
• cancel: Cancels pending lifecycle operations on selected image copies. When you
cancel a specific destination, you also cancel the pending operations at destinations
that depend on the source copy from that destination. These images will not later
be considered for duplication by the lifecycle.
• inactive: Deactivates future lifecycle operations on the image copies, but retains
the image information so that processing can resume (similar to a suspend

function).
• active: Activates the lifecycle operations on selected image copies (similar to a
resume function).
• list: Displays the contents of an image list from the NetBackup database
(primarily used as a debugging tool to assist in troubleshooting problems).
• stlilist: Displays the status for incomplete copies of lifecycle managed images.
• diskspaceinfo: Reports on the space that is used by all disk volumes, or only
the disk volumes that are used by the specified type.
For more information on the nbstlutil command functions and options, see the
NetBackup Commands Reference Guide.

12-29
Reporting on SLPs in OpsCenter
30
OpsCenter has two very useful storage lifecycle policy reports:

• SLP Status: This report provides an overall summary of the SLP status and allows you
to monitor the SLP progress by master server.
• SLP Backlog: This report illustrates what the SLP backlog looks like against the image
creation volume, including in a tabular form.
An example SLP Backlog report is shown on the slide.
Backlogs occur frequently, and can be normal, however may need to be managed to
keep the SLP environment from getting too far behind. In the slide example, the SLPs
have not been processing the images; therefore, the backlog has built up to the point
where the Created Images equal the Unfinished Images, showing that a large backlog
exists.
Data for the SLP Backlog report is not real time, and is collected from the OpsCenter
database on a periodic basis. Because SLP processing generally takes hours, this typically
does not impact the report’s effectiveness. Most backlogs in a properly sized
environment are resolved eventually, so minute-by-minute monitoring is not a good
indication of general backlog issues. Consistent or growing backlog over the span of
days and weeks indicates that either too much data is in the SLP process, or that there is
not enough infrastructure to handle the amount of information.

12-30
Additional Storage Lifecycle Policy features and benefits
After completing this topic, you will be able to explain additional benefits
and features of SLP, such as optimized duplication, Auto Image Replication,
and Data Classification.
31
After completing this topic, you will be able to explain additional benefits and features
of SLP, such as optimized duplication, Auto Image Replication, and Data Classification.

12-31
Additional Storage Lifecycle Policy features and benefits
• Copies a backup image efficiently between supported storage.

Optimized
• Uses the underlying storage features to minimize bandwidth.
duplication
• Used during duplication and replication jobs.
• Replicates backups from one NetBackup domain to another

Auto Image
• Uses minimal bandwidth with optimized duplication
Replication
• Supports many-to-one and one-to-many configurations
• Manages capacity on AdvancedDisk storage units with SLPs

Data
• Used when the business value of different backup data varies
Classification
• Configured in both the backup policy and the SLP
32
The use of storage lifecycle policies (SLPs) also provide a number of other features and
benefits:
• Optimized duplication is NetBackup’s ability to take advantage of features within the
underlying storage or software to efficiently copy a backup image without having to
send all the image data, reducing the workload on the NetBackup media servers.
Optimized duplication relies on the source and target storage supporting each other,
which in most cases means the technologies must be identical. Although it can be
used in SLPs, it is also supported with other duplication features, such as the
NetBackup bpduplicate command.

• Auto Image Replication is a function of NetBackup SLPs which allow the replication of
backup images from one NetBackup domain to another. This feature takes advantage
of optimized duplication to
Note that different backup and storage vendors may use the term replication in
different ways, which may or may not match the NetBackup definition.
• Data Classification is an optional ranking that can be assigned to backup data
according to its business value or importance, relative to other backup data. Data
classification is defined in the master server host properties, as well as optionally
used in a backup policy. For more details, refer to the NetBackup Administrator’s
Guide.

12-32
Understanding optimized duplication: Ensure prerequisites are
met
• Both the source and the destination disk pools must be the same OpenStorage vendor
type.
– Refer to the OpenStorage section of the NetBackup Hardware Compatibility List
– Refer to the OST-supported disk vendor for other restrictions
• Requires a media server that is credentialed to both the source storage server and the
destination storage server
– The media server initiates, monitors, and verifies the duplication operation.
– All data movement is done by the source or destination storage server.
– A NetBackup appliance can function as both media server and storage server.
Ensure prerequisites Use a supported Modify optimized

are met duplication method duplication behavior
33
To understand optimized duplication and how to configure it, you need to understand
the prerequisites, how to perform optimized duplication, and how to control its
behavior. These issues are discussed on the following slides.
Ensure prerequisites are met
For most disk appliance types, the source and destination must be identical.
For OpenStorage vendors that support optimized duplication, refer to the OST
supported vendor for their hardware and version restrictions.
To configure optimized duplication, one or more media servers must have credentials to
both the source and destination storage. This could be either the source or target MSDP
storage server, or a media server that is separate from both disk storage appliances. The
role of this media server is to initiate, monitor, and then finally verify the copy
operation.

12-33
Understanding optimized duplication: Use a supported duplication
method
• For single duplication copy, use a supported duplication method:
– Storage lifecycle policy (SLP)
– NetBackup Vault policy
– The bpduplicate command
• For multiple duplication copies:
– SLP creates:
• Separate optimized duplication jobs for each supported destination
• Separate normal duplication jobs for unsupported destinations
– Other duplication methods use normal duplication for all destinations.

34
Use a supported duplication method

To use optimized duplication, simply duplicate using a supported source and target
destination, using any of these duplication methods:
• A storage lifecycle policy (SLP)
• A NetBackup Vault policy
• The bpduplicate command
Because optimized duplication is used by default when the prerequisites are met, no
other specific configuration needs to be performed.
When deciding to duplicate to multiple destinations, the behavior depends on the
duplication method:
• Storage lifecycle policies
In the case of SLPs, multiple optimized duplication jobs are supported, as long as
the multiple target storage locations support optimized duplication from the source
storage. A separate job is created for each of these jobs.
• Other duplication methods
With other duplication types, multiple, simultaneous optimized duplications are not
supported, and normal duplication are used for all destinations.

12-34
Understanding optimized duplication: Modify optimized
duplication behavior
• Optimized duplication failover
– NetBackup does not re-run failed optimized duplication jobs as normal duplication jobs, by default.
– Duplicate to non-deduplication storage unit when optimized duplication fails.
• Number of optimized duplication attempts
– Unlimited when optimized duplication triggered by SLP
– Default retries when triggered by Vault or bpduplicate: 3 attempts
• Storage lifecycle policy retry wait period
– NetBackup waits in between SLP job attempts.
– Default wait period: 2 hours

35
Modify optimized duplication behavior

Settings exist to customize optimized duplication behavior. By default, NetBackup does
not try to rerun failed optimized duplication jobs as standard duplication jobs. You can
configure NetBackup to run standard duplication when optimized duplication fails by
setting the following value either in the NetBackup bp.conf file on UNIX, or with the
bpsetconfig command on UNIX and Windows:
RESUME_ORIG_DUP_ON_OPT_DUP_FAIL = TRUE
To configure the number of duplication attempts, create a file named

OPT_DUP_BUSY_RETRY_LIMIT that contains an integer that contains an integer
that specifies the number of times to retry the job before NetBackup fails the job (the
default is 3).
Place the file on the master server in the following directory:
• UNIX: /usr/openv/netbackup/db/config
• Windows: install_path\NetBackup\db\config
To configure the storage lifecycle policy wait period (the default wait period between
retries is 2 hours), modify the IMAGE_EXTENDED_RETRY_PERIOD_IN_HOURS SLP
parameter in the master server host properties.

12-35
Understanding Auto Image Replication
• Replicates backups from one NetBackup domain to another, between supported

hardware vendors and between MSDP disk pools.
• Managed using Storage Lifecycle Policies (SLPs)
• Uses minimal bandwidth with optimized duplication
• Supports simple one-to-one, many-to-one and one-to-many replication configurations
• Provides ability to vault backups without shipping physical tapes
• Refer to the NetBackup Administrator’s Guide and the NetBackup: Advanced
Administration course
36
Introduced in NetBackup 7.1, Auto Image Replication enables the replication of backup
images from one NetBackup domain to another. This feature is enabled by using Storage
Lifecycle Policies, or SLPs, with OpenStorage Technology (OST) based storage.
Supported storage includes NetBackup deduplication, such as Media Server
Deduplication Pools (MSDP) and NetBackup appliances, as well as storage vendors that
support and are qualified for OST.
Auto Image Replication uses Optimized Duplication, which allows NetBackup to
minimize the use of wide area network (WAN) bandwidth that is normally at a premium
between sites. Only new, unique data is transferred between sites. After an image is
duplicated to the target domain, standard duplication copies that backup image to tape.
In this way, a vaulted copy of the backup is created without having to ship tapes.
Auto Image Replication supports various disaster recovery models, including simple
one-to-one, many-to-one and one-to-many replication. Targeted Auto Image Replication
allows selective replication of images.
Refer to the NetBackup Administrator’s Guide, or the NetBackup: Advanced
Administration course.

12-36
How Auto Image Replication works
1. A backup image is created on the source domain.

2. The image is replicated to the target domain.
3. The image is quickly imported into the target domain.
4. There can be additional, optional duplications and replications.
Source domain * Replication Target domain *

Duplication
Image Image Image
Client Master/ OST-based OST-based Master/

media storage storage media
* The use of the term “domain” in this topic refers to NetBackup domains.
37
Auto Image Replication works by going through the following basic steps:
1. Run and create a backup image in the source domain.
2. Replicate the backup image to the target domain, generally using a method called
optimized duplication, which is supported with NetBackup deduplication and with
OpenStorage vendors, and takes advantage of the replication features in these
products. This process involves storing the backup image with the backup metadata
so that the import process on the target domain is performed quickly.
3. After the backup image, which includes the backup metadata, has been duplicated
to the target domain, the target master server imports the metadata.
Because the metadata can be easily and quickly imported, this is referred to as a fast
import. This is much preferred to the traditional, much slower method of having to
re-catalog the entire backup image.
4. Optionally, additional duplication jobs can be configured. These can be duplications
to local storage, or additional replication jobs.

12-37
Storage lifecycle reporting tools

Data classifications Host Properties > Master nbdc -L
Servers
Storage lifecycles Storage > Storage Lifecycle nbstl -L Manage > Storage >
Policies Storage Lifecycle Policy
List storage lifecycle nbstlutil list

operations
38
The table on this slide summarizes how storage lifecycle information can be displayed
using the NetBackup Administration Console, NetBackup commands, and OpsCenter.

12-38
Lesson summary
• Key points
– You can now identify the duplication backup types, including inline, manual duplication, basic disk
staging, and storage lifecycle policies.
– You can describe the configuration options for storage lifecycle policies, and you can create and initiate
a storage lifecycle policy.
– NetBackup Administrator’s Guide, Volume I and Volume II
– NetBackup Vault Administrator’s Guide
– Article 100032502: Storage Lifecycle Policy (SLP) Cheat Sheet
39

12-39
Lab 12: Duplicating Backups Using Storage Lifecycle Policies
Lab objectives
• Configuring a Storage Lifecycle Policy (SLP)
• Configuring a NetBackup policy to use a Storage Lifecycle Policy
• Modifying SLP Host Properties
• Viewing and monitoring SLP operations
40

12-40
What did you learn?
lesson.
41
current lesson.

12-41
Question: Simultaneous image copies
When NetBackup makes more than one image copy simultaneously during the backup, it
is called ____________.
A. Simultaneous copy
B. Inline copy
C. Storage life backup
D. Duplication backup
42

12-42
Answer: Simultaneous image copies
When NetBackup makes more than one image copy simultaneously during the backup, it
is called ____________.
A. Simultaneous copy
B. Inline copy
C. Storage life backup
D. Duplication backup
The correct answer is B. An inline copy is when backup data is sent to multiple storage destination simultaneously during
a backup. In NetBackup, a duplication is when a backup image is copied to a new destination after the original backup
had already been completed.
43

12-43
Question: SLP operations
A storage lifecycle policy can be configured for which operations?
A. Backup, Deduplication, Export

B. Backup, Export, Import
C. Backup, Duplication, Replication
D. Fixed, Data classification, Automatic
44

12-44
Answer: SLP operations
A storage lifecycle policy can be configured for which operations?
A. Backup, Deduplication, Export

B. Backup, Export, Import
C. Backup, Duplication, Replication
D. Fixed, Data classification, Automatic
45

12-45
Question: Duplication session
By default, how often does NetBackup check for completed backups when determining
if a duplication session should be started?
A. 30 seconds
B. 1 minute
C. 5 minutes
D. Immediately
46

12-46
Answer: Duplication session
By default, how often does NetBackup check for completed backups when determining
if a duplication session should be started?
A. 30 seconds
B. 1 minute
C. 5 minutes
D. Immediately
47

12-47
End of presentation
12-48
Lesson 13: Managing and Protecting the NetBackup

Catalog
This is the “Managing and Protecting the NetBackup Catalog” lesson in the “Veritas
NetBackup 8.1: Administration” course.

13-1
Policies
This lesson is the thirteenth lesson in this course.


13-2
Lesson objectives
Topic Objective
Describe the location, and explain the importance of NetBackup
Introduction to NetBackup catalogs
catalog backups.
Describe the difference between image retention and image
Managing images
expiration, and how to import, verify, and expire images.
Configuring a catalog backup policy Configuring a catalog backup policy.
List the steps that are required to recover from a disaster situation,
Disaster recovery strategies and recover the NetBackup catalog using the NetBackup Catalog
Recovery Wizard.

13-3
Topic: Introduction to NetBackup catalogs
After completing this topic, you will be able to describe the location, and
explain the importance of NetBackup catalog backups.
After completing this topic, you will be able to describe the location, and explain the
importance of NetBackup catalog backups.

13-4
The NetBackup catalog
Master server
NetBackup
catalog
• Stores data in a relational database (NBDB)

• Includes:
The NetBackup – Media and device data
database (NBDB) – Backup image header data
• Stores data in flat files

• Includes:
NetBackup – Policies, schedules, and job information
configuration files – Backup image file metadata
NetBackup catalogs are information stores that contain information about the
NetBackup configuration and backups, including records of the files that have been
backed up and the media on which the files are stored.
The NetBackup catalogs reside on the NetBackup master server and consist of the
following components:
• The NetBackup database (NBDB) is a relational database that uses SAP SQL
Anywhere. The NBDB stores data for several NetBackup services, including media
and device data, backup image headers, authentication and authorization. Bare
Metal Restore (BMR) data is also stored in a Sybase database if the BMR option is
used. Because the first service to use the relational database was the Enterprise
Media Manager in earlier releases of NetBackup, the database is sometimes
referred to as the EMM database.
• The NetBackup configuration files include policies, schedules, and other files used by
NetBackup. These are sometimes referred to as flat files because they are not stored
in a relational database, and are stored in simple files on the file system of the
NetBackup master server.
metadata. This metadata is stored in two locations: the image header data is stored in
the relational database (NBDB), and the image file list is still stored as flat files in the
NetBackup configuration files. Because the image file lists contain the path to every file
backed up, this is usually the largest component of the NetBackup catalogs.

13-5
Protecting the NetBackup catalogs
• Protecting the NetBackup catalogs is important, as they contain:

– The NetBackup configuration
– Information about backups that have been performed
• To protect your catalogs:
– Make multiple copies of a catalog backup.
– Store a copy of the catalog backup offsite.
Although you can recover your data without the catalogs, doing so takes considerably
longer and involves more work than if the catalogs were available. Therefore, backing
up the catalogs efficiently and regularly is of paramount importance.
To protect your catalogs:
• Make at least two copies of the catalog backup images.
• Store one copy of the catalog backup offsite.

13-6
The NetBackup database (NBDB)
Database files
• DARS_DATA.db UNIX: /usr/openv/db/data
• DARS_INDEX.db Windows: install_path\NetBackupDB\data
• DBM_DATA.db
• DBM_INDEX.db
• EMM_DATA.db Configuration files
• EMM_INDEX.db
• server.conf
• JOBD_DATA.db
• databases.conf
• NBAZDB.db
• NBAZDB.log
• NBDB.db
UNIX: /usr/openv/var/global
• NBDB.log Windows: install_path\NetBackupDB\conf
• SLP_DATA.db
• SLP_INDEX.db
• vxdbms.conf
The NetBackup database (NBDB) is created during the installation of the master server.
The NBDB stores information used by the master server, and runs on SAP SQL
Anywhere.
The NBDB consists of database files, configuration files and a transaction log.
NetBackup database bp.conf or Registry entry
During installation, a VXDBMS_NB_DATA entry is created in the bp.conf file (UNIX) or
the Registry (Windows). This entry identifies the directory where NBDB.db and
vxdbms.conf are located as follows:

• bp.conf
VXDBMS_NB_DATA = /usr/openv/db/data
• Registry
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\
Config\VXDBMS_NB_DATA
For more information about the NetBackup catalogs, please attend the NetBackup:
Maintain and Troubleshoot course.

13-7
Configuration files
install_path
UNIX /usr/openv/
NetBackup Windows C:\Program Files\Veritas
db
• class directories: Policy information • IDIRSTRUCT: Identifies structure of images

• client: Master server client attributes database
• cloud: cloud configuration files • images: Contains information about backup
images
• cltmp: Policy temporary information
• jobs: Job information
• config: Host properties, data classification
properties • media: Temporary area for media activity
• DBVERSION: NetBackup version • sched: Staging schedules
• error: Activity logs • ss: Storage lifecycle policy information
• failure_history: List of failed backups • vault: Vault properties
The configuration files consist of directories that also contain flat files located on the
master server disk. The directories that comprise the configuration files include:
• class: Directories that contain policy information
• client: Contains master server client attributes
• cloud: Cloud configuration files
• cltmp: Contain temporary policy information
• config: Contain information about host properties and data classification
• DBVERSION: Contains NetBackup version information

• error: Contains some of the activity logs.
• failure_history: Contains a list of failed backups
• IDIRSTRUCT: Identifies where to place the backup image files (default value is
“2”)
• images: Contains information about backup images
• jobs: Contains information about jobs that have run
• media: Is a temporary area for media activity
• sched: Contains staging properties
• ss: Contains storage lifecycle policy information, in some prior NetBackup releases
• vault: Contains Vault properties

13-8
The image database
• Contains information about backups that have been performed

• Has data stored in multiple locations:
– Image header data stored in the relational database (NBDB).
– Image file list stored in flat files:
Platform Image database location
UNIX /usr/openv/netbackup/db/images/client/ctime
Windows install_path\NetBackup\db\images\client\ctime
images
winclient.example.com Client name Each backup has a filelist (.f) file
named using policy name,
Creation timestamp timestamp, and schedule type
1483000000
clients_to_master_bdisk_1483603201_FULL.f
clients_to_master_tape_1483548217_FULL.f
9
metadata. The image metadata is stored in two locations:
1. The image header data is stored in the relational database (NBDB)
2. The image file list is still stored as flat files in the NetBackup configuration files area.
Because the image file lists contain the path to every file in every active backup
image, this is usually the largest component of the NetBackup catalogs.
The image file lists are located in the NetBackup configuration area, in a folder called
images. Under the images folder, there are subdirectories for each client that is backed
up by NetBackup, including the master server and any media servers, and additional
subfolders named after timestamps, as shown in the example on the slide.
These folder contain the following files:
• Image .f files are files that are used to store the detailed information about each
file backup.
• The .lck files are files used to prevent simultaneous updates on images.
• The db_marker.txt file is used to ensure that access to the db directory is valid
when the NetBackup Database Manager starts. Do not delete this file.

13-9
Topic: Managing images
After completing this topic, you will be able to describe the difference
between image retention and image expiration, and how to import, verify,
and expire images.
10
After completing this topic, you will be able to describe the difference between image
retention and image expiration, and how to import, verify, and expire images.

13-10
The Images on Media report
bpimmedia –U [-disk|-tape]
11
When a backup job is initiated, NetBackup selects the required piece of media based on
the parameters of that specific backup job. The policy and schedule dictate the required
storage unit, volume pool, and retention level.
The Images on Media report lists all backup images for a specific NetBackup client, or
all clients. The corresponding Images on Tape and Images on Disk reports can be used
to narrow the search to a particular tape or disk storage unit.
These reports can be run using the bpimmedia command, as shown on the slide.

13-11
Searching for backup images
Filters results to show images

relevant for the operation
Provides visibility
into the backup
image database
12
Select NetBackup Management > Catalog to search for backup images. You may want
to search for a backup image to:
• Verify the backup contents with what is recorded in the NetBackup catalog.
• Duplicate the backup image to create up to ten copies.
• Promote a copy of a backup to be the primary backup copy.
• Expire backup images.
•
Import expired backup images or images from another NetBackup server.

You learn how to perform many of these operations in this lesson.
Specify the specific search criteria that NetBackup is to use to build a list of backups
from which you can make your selections.

13-12
The NetBackup verification process
Media
ABC123
EOT
EOF
EOF
EOF
BH
BH
BH
• Read each block of the media
• Compare written image headers with NetBackup Catalog
NetBackup Catalog
NBDB NBDB Image database
(media ID) (header info) (.f file)
Image1 Image1.f
ABC123 Image2 Image2.f
Master server Image3 Image3.f
13
NetBackup can verify the contents of a backup by reading the volume and comparing its
contents to what is recorded in the images catalog. This operation does not compare
the data on the volume with the contents of the client disk. However, it does read each
block in the image, thereby verifying that the volume is readable.
NetBackup verifies only one backup at a time and tries to minimize media mounts and
positioning time.
Most modern tape drives have built-in read-after-write (RAW) verification.

13-13
Verifying backup images using the Administration Console
bpverify
14
To verify a backup image from the NetBackup Administration Console:

1. In the object tree pane, select NetBackup Management > Catalog.
2. In the details pane, specify criteria that NetBackup uses to build a list of backup
images from which you make your selections.
a. Select Action > Verify.
b. After you have specified your search criteria, click Search Now.
3. From the list of backup images you have created, right-click the image that you want
to verify and select Verify from the shortcut menu.
You will see a Confirm Verify message window, which gives you the option to log all
files found in verified images.
4. Click OK to continue.

13-14
Confirming the verify results
18:56:24 INF - Verifying policy LAB13-catalog-

to-master-tape, schedule DAILY_DIFF
(winmaster.example.com_1517353167), media id
E01005, created 01/30/2018 17:59:27.
18:56:28 INF - If Media id E01005 is not in a
robotic library administrative interaction
may be required to satisfy this mount
request.
18:56:28 INF - Waiting for mount of media id
E01005 on server winmaster.example.com for
reading.
18:56:35 INF - Waiting for positioning of
media id E01005 on server
winmaster.example.com for reading.
18:56:35 INF - Beginning verify on server
winmaster.example.com of client
winmaster.example.com.
18:56:36 INF - Verifying True Image Recovery
information from media id E01005.
18:56:36 INF - Verify of policy LAB13-catalog-
to-master-tape, schedule DAILY_DIFF
(winmaster.example.com_1517353167) was
successful.
15
5. To verify the results, click the Results tab.

• The top portion of the Results pane displays a list of all existing log files.
• The bottom portion of the Results pane displays the contents of a selected log
file.
6. To view a log file, select the name of the log from the list and review the details in
the bottom portion of the window.
Note: If an operation is in progress, the log file display is refreshed as the operation
proceeds.

13-15
Expiring a backup image
bpexpdate -backupid
16
To expire a backup image in the NetBackup Administration Console:

1. In the object tree pane, select NetBackup Management > Catalog.
2. In the details pane of the dialog box, set up the search criteria for the image that
you want to expire and click Search Now.
3. Right-click the image you want expired and select Expire. A message informs you
that after the backups have been expired, they can no longer be used for restores.
4. Click Yes to proceed with expiring the image.
Expiring the image using this procedure only expires that specific copy of the backup.
Additional copies would need to be found and manually expired individually.
Expiring a disk image removes both the entry for the image in the NetBackup image
catalog, and the backup image itself, from the disk storage unit.
Alternatively, you can use the bpexpdate command to expire a backup image (or to
change the expiration date) of a single backup:
bpexpdate -backupid backup_id –d date | 0 | infinity
[-client client_name] [-copy number] [-force]
[-M master_server[,...,]]

13-16
Importing backup images
What can be imported?
• Backups that have reached their retention

• Backups written in a different NetBackup domain
Preparing to import
• Ensure media is available to the media server performing the import

• For tape: Ensure the correct media ID is used; Use physical inventory (vmphyinv) if necessary
• For disk: Mount the file system with the data
Performing an import
• Phase I: Initiate Import: Generate a list of images.

• Phase II: Import: Import selected images.
17
A NetBackup master server may not have any record of the data on a piece of backup
media. This may happen if the backup has reached its retention, or if it was written by a
different NetBackup server in another NetBackup domain.
To access data in these situations requires the use of the import feature. Importing a
backup refers to the process of examining the backup on a media and importing the
metadata into the NetBackup catalog on the master server. This allows NetBackup to
access and restore from this data.
Before performing an import operation, it is important to:
• Ensure that the media is available on the media server performing the import.
• Ensure the correct media ID is being used, if this is a tape. Doing a physical inventory
using the NetBackup vmphyinv command, which is described in the NetBackup
Commands Guide, determines the media ID by mounting the tape and reading the
tape header, as opposed to reading a barcode (which may be incorrect).
• Ensure that the file systems and volumes are mounted, for disk-based backups.
In prior versions of NetBackup that are no longer supported, there was compatibility for
reading Backup Exec tapes. This functionality is no longer supported. For more detail,
refer to Article 100000926: Statement of support for the importing of Backup Exec
images in NetBackup 7.x using the Backup Exec Tape Reader, found online at

13-17
Phase I: Initiating the import
Tape
Disk
bpimport -create_db_info
18
During an import operation, NetBackup re-creates NetBackup catalog entries for the
backups on the imported volume. Use the following procedure to initiate the import:
1. In the Administration Console, expand NetBackup Management > Catalog.
2. Select Actions > Initiate Import. The Initialize Import dialog box is displayed.
3. Complete the Initialize Import dialog box by entering the following information
a. In the Media Server field, specify the media server where the import will occur,
and that currently has access to the media with the images that are going to be
imported.
b. In the Image Type field, specify if it is Tape or Disk.
• For Tape, then specify the Media ID.
• For Disk, then specify the Disk Type field (Basic Disk, Advanced Disk, or
PureDisk). Depending on the disk type selected, you either need to specify
the Path (for BasicDisk), or the Disk Pool and Volume for a disk pool.
c. Click OK. The Confirm Initiate Import dialog box is displayed. Click OK to
proceed.
4. The process of reading the catalog information from the source volume begins.

13-18
Generating a list of images
18:27:39 INF - Recreating image information

for client winmedia.example.com, policy PRE-
clients-to-master-tape, and schedule full,
done on 01/16/2018 11:13:14.
18:27:39 INF - Recreating copy 1, fragment 1
information for image.
bpimport
19
5. Click the Results tab to watch as NetBackup scans each image on the tape or disk to
determine if the image already exists or needs to be imported. The job is also
displayed in the Activity Monitor as an Import type. Select the import job log that
was just created to view the job results.
Note: Because it is necessary to mount and read the tape at this phase, reading the
catalog and building the list can take some time to complete.

13-19
Phase II: Searching for and selecting images to import
Set search information to

find imported images
bpimport
20
During Phase II, you select and import images from the list of images that were
completed in Phase I.
1. In the NetBackup Administration Console, expand NetBackup Management >
Catalog.
2. Set up the search criteria to find imported images by setting the search action to
Import. Select a date range that includes the images you want to import and click
Search Now.
Note: The date range specified must encompass the date the original backup was
written, even if the image to be imported is a copy.

13-20
Importing the selected image
bpimport
21
3. Select the images you want to import and select Actions > Import.
The Confirm Import dialog box is displayed.
4. Click OK.

13-21
Confirming the import results
18:37:52 INF - Importing policy PRE-clients-to-master-

tape, schedule full (winmaster.example.com_1516375342),
media id E01001, created on 01/19/2018 10:22:22.
18:37:57 INF - If Media id E01001 is not in a robotic
library administrative interaction may be required to
satisfy this mount request.
18:37:57 INF - Waiting for positioning of media id E01001
on server winmaster.example.com for reading.
18:37:58 INF - Beginning import on server
winmaster.example.com of client winmaster.example.com.
18:38:14 INF - Import of policy PRE-clients-to-master-
tape, schedule full (winmaster.example.com_1516375342)
was successfully completed.
22
5. To view the log, click the Results tab, and then select the import job log that was
just created.
When importing backups that have fragments on multiple tapes, do not start the Import
(Phase II) until you have run the Initiate Import (Phase I) to read the catalog for all the
tapes containing fragments. If this is not performed, the import fails with a message
such as:
Unexpected EOF or Import of backup_ID failed, fragments
are not consecutive.
All copies of an image must be expired before the image can be imported. The import
reports that an image is bypassed if a copy already exists.
When an image is imported, the new expiration date and time of the imported image is
determined by adding the retention period associated with the image to the current
date and time. For example, if an image with a two-week retention is imported on
January 09, 2017 at 6:39 A.M, the expiration date of the imported image is January 23,
2017 at 6:39 A.M.

13-22
Summary of image-related tasks
Task Description
Search Search for backup images.
Verify the contents of a backup by reading the volume, and

Verify
comparing its contents with what is recorded in the NetBackup catalog.
Duplicate Make a duplicate copy of a backup image.

Force the retention period to expire. When the retention period expires, NetBackup
Expire
deletes information about the backup.
Import expired backup images or images from another NetBackup server. NetBackup re-
Import
creates NetBackup catalog entries for the backups on the imported volume.
Set primary Promote a backup image from a copy to the primary backup copy. If the primary copy is
copy unavailable and a duplicate copy exists, set the copy to be the primary copy.
23
The table on this slide summarizes the image-related tasks that you can perform. See
the NetBackup Administrator’s Guide for more information about these tasks.

13-23
Moving the image database (UNIX)
Step Action
1 Back up the NetBackup catalogs.
2 Ensure that no backups are running.
3 Stop NetBackup daemons.
4 Create the new file system.
5 Move the image database to the new location.
Mount the new file system on the images

6 Create a symbolic link to the new location. or directory.
7 Restart NetBackup daemons.
24
If the image database grows too large on a static UNIX partition, you can move the
image database to another partition as follows:
1. Back up the NetBackup catalogs, to ensure that you can recover image information
in case something is accidentally lost during the move.
2. Ensure that no backups are in progress using the Activity Monitor or enter:
/usr/openv/netbackup/bin/bpdbjobs
3. Stop NetBackup daemons, for instance by running the netbackup stop

command, to prevent jobs from starting and the database from being modified
while you are moving the image database.
4. Create the new file system, and optionally create a directory for the image files. For
example:
mkdir /newvol/netbackup/db/images
5. Move the image database to the new location in the other file system.
6. Create a symbolic link from /usr/openv/netbackup/db/images to the new

location in the other file system, or alternatively mount the new file system on the
NetBackup images directory.
7. Restart NetBackup daemons.

13-24
Moving the image database (Windows)
Step Action
1 Back up the NetBackup catalogs.
2 Ensure that no backups are running.
3 Stop NetBackup services.
4 Create the new file system.
5 Move the image database to the new location.
Create an ALTPATH file in the image

Mount the new file system to the empty
6 database directories, and specify the new or images folder.
path location.
7 Restart NetBackup services.
25
If the image database grows too large on a static Windows partition, you can move the
image database to another partition as follows:
1. Back up the NetBackup catalogs to ensure that you can recover image information in
case something is accidentally lost during the move.
2. Ensure that no backups or restores are in progress by using the Jobs tab in the
Activity Monitor. If backup or other jobs are running, either wait for them to end or
stop them by using the Jobs tab in the Activity Monitor.
3. Stop the NetBackup services, for instance by running the bpdown command, to
prevent jobs from starting and the database from being modified while you are
moving the image database.
4. Create the new file system and optionally any directories to which you intend to
move the image information. For example:
E:\NetBackup\alternate_db\images\client_name
5. Move all files and directories to the new location. Note that if you are planning to
use the ALTPATH method of setting an alternate location, you need to move the
image files for specific NetBackup clients into a folder for that client.

13-25
For example, if the images are currently in C:\Program Files\VERITAS\
NetBackup\db\images\mars and the ALTPATH file specifies
E:\NetBackup\alternate_db\images\mars, then move all files and
directories to E:\NetBackup\alternate_db\images\mars.
6. If you are planning to use the NetBackup ALTPATH method to move image files, then
create a file named ALTPATH in the original image database directory for each
client.
For example, if NetBackup is installed in its default location and the client name is
mars, the path to the image database is:
C:\Program
Files\VERITAS\NetBackup\db\images\mars\ALTPATH
On the first line of the ALTPATH file, specify the path to the directory where you
intend to move the client’s image information. For example:
E:\NetBackup\alternate_db\images\client_name
This is the only entry in the ALTPATH file.
Alternatively, use a Windows junction point to mount the new file system (which
contains all the old image files and directories) on top of the images directory.
7. Restart the NetBackup services, for instance by running the bpup command, to
allow clients to resume backup and restore capabilities.
For additional information, refer to:
• Veritas NetBackup Administrator's Guide Volume 1: Moving the Image catalog.
• Veritas NetBackup Administrator's Guide Volume 1: Moving NBDB databse files after
installation.

13-26
Topic: Configuring a catalog backup policy
After completing this topic, you will be able to configure a catalog backup
policy.
27
After completing this topic, you will be able to configure a catalog backup policy.

13-27
Protecting your backups
Protect backup data
• Configure multiple backup copies

• Store backup copies offsite
• Protect the NetBackup catalog with catalog backups
Catalog backups
• Scheduled like regular backup policies

• Configured by creating a backup policy of type NBU-Catalog
• Run as full or incremental catalog backups
• Use the dedicated CatalogBackup volume pool, by default
• Creates a disaster recovery file and package
• Can automatically e-mail and save a disaster recovery reports
• Can be used to identify critical policies: Policies whose media is also listed in the disaster
recovery report
28
Backup data is vulnerable to loss during hardware and site failures, which can
compromise an organizations recovery objectives.
To protect backup data, you can configure multiple copies of your backups, and store
some of these backups offsite. This provides a level of redundancy that allows an
organization to survive many types of software, hardware, and site failures.
Additionally, the NetBackup infrastructure should also be protected, as it is critical in
being able to quickly restore an organizations data. This is best done by configuring
catalog backups, which are used to back up and recover the NetBackup catalog in the
event of NetBackup master server failure or corruption.

Catalog backups can be run just like normal backups, and can be run online, while
NetBackup is performing other tasks such as backups and restores. Catalog backups can
run full and incremental backups, thereby minimizing catalog backup time and space.
Catalog backup policies are slightly different from normal backups. Because NetBackup
already knows data and clients to back up, you do not need to specify the clients or
backup selections for a catalog backup. In addition, catalog backups create a disaster
recovery file and a disaster recovery package (DR package). The disaster recovery file,
which can be automatically e-mailed to the NetBackup administrators, outlines
instructions for performing a catalog restore and identifies the required tapes. The DR
package is new to NetBackup 8.1 and is used to recover a master server’s identity in the
event a DR needs to be performed.

13-28
The catalog backup process
• UNIX: /usr/openv/db/staging
• Windows:
install_path\NetBackupDB\staging
3. Back up
configuration
files
2 3
2. Back up
the NBDB
Staging
area NetBackup
configuration
1
1. Stage the NBDB, overwriting the
prior contents of the staging area
NBDB
29
Veritas best practice is to schedule catalog backups to run regularly, in case of failures
with the master server or its catalogs and databases. Additionally, run manual catalog
backups prior to and immediately after any upgrade, including patch upgrades.
This slide describes what happens during a catalog backup. After a parent job starts to
manage the entire process, the following additional jobs run:
1. A child job copies the NBDB files to the staging location, as shown on the slide.
During each catalog backup, the files in the staging area are overwritten. Until they
are overwritten, they can be used for disaster recovery.
2. A child job starts, which backs up the files from the staging directory to the storage
unit specified in the catalog backup policy. This job backs up the files in a single
stream.
3. Another child job starts, which backs up the NetBackup configuration files. This
includes the Image database, policies, configuration, and other catalogs on the
master server.
In previous versions of NetBackup, the files in the staging directory were deleted at the
end of the successful catalog backup.
The NetBackup database truncates the NBDB transaction log automatically during
database checkpoints, separate from the catalog backup schedule.

13-29
Disaster Recovery files generated during catalog backups
• Lists location containing the corresponding catalog backup

• Lists location of most recent Critical Policy backups
DR file • Simplifies disaster recovery process
• Available in all NetBackup versions
• Example filename: NBU_catalog_1501149670_FULL
• Contains the Certificate Authority Certificate, Host ID and Hostname Certificate, encryption
keys, and database table unload data
• Used to recover master server identity during disaster recovery
DR package • Encrypted with DR passphrase
• Available in NetBackup 8.1 and later
• Example filename: NBU_catalog_1501149670_FULL.drpkg
30
Starting in NetBackup 8.1 when a NetBackup Catalog backup is performed two Disaster
Recover (DR) files are created: the DR file and the DR package.
• The DR file is the same file created in prior releases of NetBackup, and lists the
location containing the corresponding catalog backup, including locations for the
most recent Critical Policy backups.
• The DR package is included in NetBackup 8.1 and later, contains identity information
about the master server, and is used to recover a master server’s identity in the event
disaster recovery needs to be performed. Without the DR package,
A NetBackup catalog policy can be configured to email these files as an attachment.

If the master server is re-installed as part of disaster recovery, the DR package is
required to bring back the identity certificate of the master server that was in place at
the time the catalog backup was performed. This restores the trust relationship
between the master server and all other hosts in the NetBackup domain. Due to the
secure nature of this process, a DR passphrase must be configured in NetBackup, and
must be supplied during the disaster recovery process. For new NetBackup installations
that passphrase must be set before creating a NetBackup catalog policy or when
upgrading NetBackup the passphrase must be set prior to initiating a NetBackup catalog
policy or it will fail.

13-30
Creating a DR passphrase
• No default value exists

• Must be 8 to 20 supported characters
• Not validated in the console
• Use nbhostidenity –testpassphrase
to validate the DR passphrase
31
A DR passphrase is configured in the NetBackup Administration Console under Global

Security Settings > Disaster Recovery. For new NetBackup installations the passphrase
must be set before creating a NetBackup catalog policy. When upgrading to NetBackup
8.1 from an earlier release, a DR passphrase must be configured for any existing
NetBackup catalog policies to run successfully.
During each NetBackup catalog backup, a DR package is created and encrypted with the
passphrase that is set by the Administrator. The passphrase must be between 8 and 20
characters in length. No default value exists nor will the passphrase ever expire or have
any frequency for resetting. Valid and invalid characters are shown on the configuration
page in the NetBackup Administration Console.
NetBackup does not validate the passphrase at the time of creation so it is strongly
recommended to use the nbhostidentity -testpasspharse command to test the validity
of the DR package and DR passphrase after the first catalog backup and any time after
changing the passphrase. The output of the command will either display “valid” or
“invalid”. For more details, refer to Article 100040029: About NetBackup 8.1 catalog
passphrases, found online at http://www.veritas.com/docs/100040029.

13-31
Security considerations for the DR package
• Passphrase can be changed at any time.

• Mapping of old passwords to DR files must be maintained.
DR package can only be decrypted with the corresponding DR passphrase that created it.
• NetBackup catalog backups do not back up the DR package or any identity information
(certificates and keys).
• During a DR install DR passphrase is required to recover security certificates.
– Without the DR passphrase, CA certificates must be regenerated manually for all hosts in the NetBackup
domain.
– Refer to Article 100033743: Getting your environment up and running after a disaster when the disaster
recovery package passphrase is lost
32
The passphrase can be changed at any time. However, when changing a DR passphrase
Veritas highly recommends that you keep track of which passphrase belongs to which
DR package as NetBackup does NOT keep record of this. The correct passphrase is
required to restore the DR package at the time the DR package was created.
During a disaster recovery of the master server, if the passphrase is lost then the
identity certificates need to be regenerated for all hosts in the NetBackup domain to re-
establish the trust connection. This is accomplished through command line. For details
on this process, refer to Article 100033743: Getting your environment up and running
after a disaster when the disaster recovery package passphrase is lost, found online at
For security reasons NetBackup catalog backups do not backup the DR package, DR
passphrase or any identity information.

13-32
Selecting the Policy type and storage
33
To create a NetBackup catalog backup, create a standard backup policy, selecting NBU-
Catalog from the Policy Type drop-down list.
Select the desired storage unit from the Policy storage drop-down list. Note that if a
disk target is used, it should not be a deduplication disk target and should not reside on
the master server. This way if NetBackup or the master server is inaccessible, you are
not prevented from getting to your catalog backup.
Notice that selecting a policy type of NBU-Catalog results in a policy with three tabs:
Attributes, Schedules, and Disaster Recovery. The Clients tab is not needed because we
are backing up the catalog from the master server. Additionally, the Backup Selection
tab is not needed because we know what is being backed up: The NetBackup catalogs.

13-33
Creating a new schedule
Full
Incr
34
Create schedules under the Schedules tab. Full backup schedules are created as normal.
Incremental backup schedules have most of the normal options, however have an new
schedule type in addition to the Calendar and Frequency based schedules: After each
backup session. A backup session is a period of continuous backup activity, and ends
when all backup activity ceases for some period of time. This allows a catalog backup to
occur every time a set of backup jobs have completed.

13-34
Specifying disaster recovery information
Path to save DR file and package
Credentials for network file systems
E-mail recipients for DR file and package
Policies whose media is

also listed in the DR report
• Additional steps required to setup

e-mail notification
• Refer to Article 100016001: How
to configure email notifications
for Windows clients using BLAT
and nbmail.cmd in NetBackup
35
The Disaster Recovery tab is provides the ability to set catalog backup settings.
Creating a catalog backup involves creating disaster recovery (DR) files that provide
information on how to perform recovery, and what media is involved in that recovery.
Enter the Path where each disaster recovery image file and package can be saved on
disk, and additionally enter the logon and password information if the disk location is on
a network file system. Note: Veritas recommends saving the DR files to a network share
or a removable device, as opposed to a location on the local machine.
Optionally enter any e-mail addresses to send recovery information to, using a comma-
separated e-mail list if there is more than one e-mail address.

Additional steps are required to configure e-mail notification in NetBackup. See the
NetBackup Administrator’s Guide for information on the nbmail.cmd and
mail_dr_info.cmd scripts. Additionally, refer to Article 100016001: How to
configure email notifications for Windows clients using BLAT and nbmail.cmd in
NetBackup, found online at http://www.veritas.com/docs/100016001.
Finally, add any critical policies desired. These are additional policies, whose media for
their most recent backups is also listed.
Note: The DR e-mail is not sent to the address specified in the Global Attributes
property. The Administrator’s e-mail address in the Global Attributes properties
specifies where NetBackup sends notifications of scheduled or manual backups.

13-35
The catalog backup jobs
Image Cleanup job status:

• Catalog backup configured
• Catalog backup not configured
36
The screen shot on this slide shows NetBackup Activity Monitor with the catalog backup
jobs that have just completed.
Also notice that in regards to the Image Cleanup job status, if a catalog backup is not
configured, the image cleanup returns a status code of 1 (partially successful). When a
catalog backup job is configured, the image cleanup returns a status code of 0
(successful). This was put in place to give customers adequate warning when catalog
backups had not been configured.
The image cleanup job that runs periodically and returns a partial success status code of
1 should have the following text in the job details to provide this warning:
Warning bpdbm (pid=process_ID) Hot catalog backup is not
configured for ‘master_server_name', catalog cleanup
returns partial success until hot catalog backup is
configured.
After a catalog backup policy is configured, this warning is no longer displayed.

13-36
Topic: Disaster recovery strategies
After completing this topic, you will be able to list the steps that are
required to recover from a disaster situation, and recover the NetBackup
catalog using the NetBackup Catalog Recovery Wizard.
37
After completing this topic, you will be able to list the steps that are required to recover
from a disaster situation, and recover the NetBackup catalog using the NetBackup
Catalog Recovery Wizard.

13-37
Disaster recovery options
• Standard method for recovery available with NetBackup.

Catalog recovery • No special options or licenses required.
• Enables the duplication of NetBackup catalog backup images to a

Auto Image remote NetBackup domain
Replication • Requires the use of OST-compliant appliances or MSDP with the
appropriate license.
Catalog replication • Require additional products and configuration.

and master server • Refer to the NetBackup in Highly Available Environments Administrator's
clustering Guide.
38
This slide presents an introduction to the available catalog recovery options.

• The general recovery method is the standard method for recovery that is available
with NetBackup. No special options or licenses are required for this option. This
method is discussed in this lesson.
• Auto Image Replication enables the duplication of any backups, including NetBackup
catalog backup images, to a remote NetBackup disaster recovery domain. Auto
Image Replication requires the use of OST-compliant appliances or MSDP, and at a
minimum, two NetBackup domains.
• There are additionally other disaster recovery strategies, including things such as
catalog replication with products such as Veritas Volume Replicator (VVR), or
NetBackup master server clustering with products such as Veritas Cluster Server, or
virtual machine high availability. For additional information, refer to the NetBackup
in Highly Available Environments Administrator's Guide.

13-38
General recovery procedure after a disaster
Recovery task Master server Media server Client
Reload a minimal operating system. ✓ ✓ ✓
Reinstall NetBackup software. ✓ ✓ ✓
Configure devices and media. ✓  
Recover NetBackup catalogs. ✓  
Restart NetBackup. ✓  
Restore other data. ✓ ✓ ✓
• Ensure the same version of NetBackup is installed during recovery

• Refer to the NetBackup Troubleshooting Guide
• Attend the Veritas NetBackup: Maintain and Troubleshoot course
39
The table on this slide shows the high-level procedure to follow to recover your
environment after a disaster, such as a full site failure. This procedure makes the
assumption that the backup data has been restored to the site, either from tapes that
have been vaulted and brought back to the primary site, or similar disk backup storage
has been made available.
This includes the following steps:
1. Reload a minimal operating system to the new systems, including the master and
media servers that are to be used to restore application and server backup data.
2. Reinstall NetBackup software to the new master and media servers.

3. Configure devices and media on the new NetBackup servers, so that they can now
access the backup storage where first, the NetBackup catalogs are stored and can be
recovered, and later, the rest of the environment data can be restored.
4. Recover NetBackup catalogs, so that the new master server has all the prior
knowledge of the previous master server, and can now restore all the available
backup data. Media server overrides may need to be configured unless media server
failover was previously configured. Additionally, Veritas recommends deactivating
any policies that should be inactive during this recovery period (to prevent
scheduled backups from starting).
5. Restart NetBackup on the NetBackup servers after the catalog recovery.
6. Restore other data in your environment to recover your applications and other
servers.

13-39
Catalog recovery methods
NetBackup Administration Console Wizard

Recover either the entire NetBackup catalog set or the NetBackup images and
configuration.
Command line
Use the bprecover -nbdb command to recover only NBDB.
Command line utility

• Use the bprecover –wizard command
• Recover either the entire NetBackup catalog set or the NetBackup images and
configuration.
40
The slide shows two functionally equivalent methods for performing catalog recovery.
This topic covers performing a catalog recovery using the Netbackup Catalog Recovery
Wizard.
Here are some important points regarding disaster recovery:
• Catalog recovery relies on disaster recovery information generated during the online
catalog backup. Save the disaster recovery files created by the online catalog backup
to a network share or removable device.
• Configure the online, hot catalog backup policy to send an e-mail copy of the
disaster recovery information as part of every catalog backup.
• Specify the most recent disaster recovery file available, unless some form of
corruption occurred and you want to restore to an earlier state of the catalog.
• If the most recent catalog backup was an incremental backup, use the disaster
recovery file from the incremental backup. There is no need to restore the full
backup followed by the incremental backup.
• To read the media that contains the catalog backup, first configure a robot and drive
and perform a robot inventory.
• If the catalog backup media is on a remote media server, restart NetBackup on the
remote media server after the master server has been reinstalled (after the
recovery).

13-40
Recovering the catalog using the NetBackup Catalog Recovery
Wizard
41
Recover the entire catalog by using the NetBackup Catalog Recovery Wizard as follows:
1. To start the NetBackup Catalog Recovery Wizard from the NetBackup
Administration Console, click Recover the Catalog.
The Welcome panel is displayed.
2. Click Next on the Welcome panel to display the Catalog Disaster Recovery File
panel.

13-41
Locate the catalog disaster recovery file
• Saved to Path during a

catalog backup
• Attached to e-mail recipients
of NBU-Catalog policy
42
3. Specify where the disaster recovery file is stored by entering the fully qualified path
to the disaster recovery file.
Obtain the disaster recovery file path information from the disaster recovery e-mail.
In most cases, you specify the most recent disaster recovery information file
available. If the most recent catalog backup is an incremental backup, use the
disaster recovery file from the incremental backup. (There is no need to first restore
the full backup and then follow with the incremental backup.) If some form of
corruption has occurred, you may want to restore to an earlier state of the catalog.
If the DR file is not available, refer to Article 100037884: How To: Recover the
catalog without a DR file, found online at http://www.veritas.com/docs/100037884.
Click Next. The wizard waits while NetBackup searches for the necessary media
sources. The wizard then informs you if the necessary backup ID of the disaster
recovery image is located. If the media is not located, the wizard lists which media is
needed to update the database.
If necessary, follow the wizard instructions to insert the media that is indicated and
run an inventory to update the NetBackup database. The information that is
displayed on this panel depends on whether the recovery is from a full backup or an
incremental backup.

13-42
Retrieve the disaster recovery file
43
4. When the required media sources are all found, click Next to display the Disaster
Recovery Method panel.

13-43
Select the disaster recovery method
44
5. Select the catalog recovery method as follows:

• Recover entire NetBackup catalog. (Recommended)
This is the recommended method for recovering the entire catalog. This method
recovers the image database, configuration files, and the NetBackup database.
• Recover only NetBackup catalog image and configuration files. (Does not
recover the NetBackup relational database)
This method recovers only the NetBackup catalog image and the configuration
files. Use this method if the NetBackup database is valid but NetBackup policy,
backup image, or configuration files are lost. You can also recover the NetBackup
relational database separately by using the bprecover -nbdb command.
6. If desired, select a Job Priority and click Next to initiate the recovery of the entire
NetBackup catalog.

13-44
Wait until the recovery job finishes
45
NetBackup restores the entire NetBackup relational databases.

The wizard displays the recovery progress and announces when the catalog has been
recovered.
When the recovery job is finished, each image file is restored to the proper image
directory, and the NetBackup relational databases have been restored and recovered.
7. Click Next to continue to the final panel.

13-45
Recovery completion message
46
8. Click Finish in the final panel.

9. Stop and restart NetBackup on all the servers.

13-46
Unfreezing frozen catalog backup media
bpmedia -unfreeze
47
After the catalogs have been recovered, NetBackup freezes the media containing the
catalog backup. This is to prevent accidental overwriting of the final catalog backup
image.
After a successful catalog recovery, you can unfreeze media using the Administration
Console as follows:
1. Under Device and Media Management, select Media.
2. In the details pane, right-click the frozen media.
3. Select Unfreeze.
You can also use the command line to unfreeze media. Display frozen media in the
CatalogBackup volume pool by using the available_media script. The status of the
volume in the CatalogBackup volume pool is FROZEN. Enter the following command to
unfreeze the media:
bpmedia -unfreeze -m media_id -h nbu_server

13-47
Additional NetBackup server post-recovery steps
• Reconfigure devices, if the device configuration differs from the restored configuration
• Configure media server override or media server failover, if necessary
– Configure master server host properties > Restore Failover
– Configure master server host properties > General Server > Media Host Override
• Deactivate any policies with automatic schedules that you do not want to have run
during recovery operations
Select all policies under NetBackup Management > Policies > Summary of All Policies, and select Action >
Deactivate
48
The slide lists some additional steps that may be useful after recovery of the NetBackup
master and media servers, and prior to the recovery of application and server backup
data.

13-48
Auto Image Replication and disaster recovery
• Automated replication of backup images from one NetBackup domain to another using
storage lifecycle policies (SLP)
• Assists in designing a disaster recovery (DR) solution:
– Provides the ability to automatically vault backups offsite
– Uses optimized duplication to minimize network use
– Allows the elimination of shipping physical tapes
– Supports hub and spoke model data centers where remote offices send data to a central data center
– Combined with catalog backups, allows for easily maintained off-site copies of the catalog, to help
facilitate disaster recovery
49
Auto Image Replication is a NetBackup feature that enables the replication of backup
images from one NetBackup domain to another. This feature is enabled by using storage
lifecycle policies (SLPs) with OpenStorage Technology (OST)-based storage.
Supported storage includes:
• NetBackup deduplication: Media Server Deduplication Pools (MSDP) and NetBackup
appliances
• Storage vendors that support and are qualified for OST
After an image has been replicated to the target domain, standard duplication can be
used to copy that backup image to tape. In this way, a vaulted copy of the backup is
created without having to ship tapes.
Auto Image Replication supports the ability to create “hub and spoke” data centers,
where remote offices send data to a central location, as well as other DR models.

13-49
NetBackup deduplication and disaster recovery
• Not protected with a catalog backup.

MSDP catalog • Maintains a shadow copy for recovery (NetBackup 7.6.1 and later)
• Provides self-healing with the shadow copy.
• Used with SLP or Auto Image Replication

Optimized • Duplicates backup images from one MSDP to another MSDP
duplication • Minimizes the data that needs to be sent
• Provides redundancy, but not recoverability of the MSDP
• Creating a policy to back up the MSDP catalog

NetBackup
• Restoring the MSDP catalog from a shadow copy
Deduplication • Recovering from an MSDP storage server or storage disk failure
Guide procedures • Recovering the MSDP storage server after catalog recovery
50
It is important to understand that the NetBackup deduplication infrastructure is not

protected with the catalog backup.
To provide for redundancy of the MSDP data, use the optimized duplication feature,
which duplicates backup images using minimum bandwidth. This feature is enabled
automatically when you use storage lifecycle policies (SLPs), and with some other
backup duplication features. This feature is also supported when using an SLP with Auto
Image Replication to duplicate backups from one NetBackup domain to another
domain.
The NetBackup Deduplication Guide describes how to perform the following tasks:
• Creating a policy to back up the MSDP catalog
• Restoring the MSDP catalog from a shadow copy
• Recovering from an MSDP storage server disk failure
• Recovering from an MSDP storage server failure
• Recovering the MSDP storage server after NetBackup catalog recovery
See the NetBackup Deduplication Guide for these specific procedures. Note that many
of these procedures may be version specific, so check for the guide specific to your
version of NetBackup. There is more detailed coverage of this topic in the NetBackup
Advanced Administration course.

13-50
Catalog reporting tools

Catalog backup status Activity Monitor bpdbjobs Monitor > Jobs
Reports > All Reports >
Standard Reports
Frozen media Reports > Tape Reports > available_media Monitor > Media, select
Tape Summary the media ID.
Media used for catalog Reports > Tape Reports > bpimagelist
backups Tape Summary –media
Search on the –policy
CatalogBackup volume catalog_policy_name
pool. -L
51
The table on this slide summarizes how catalog-related information using the
NetBackup Administration Console, NetBackup commands, and OpsCenter.

13-51
Lesson summary
• Key points
– In this lesson you learned where the catalog backups reside and why catalog backups are important.
– You also learned the difference between image retention and image expiration, and how to import
expired images.
– Additionally, you learned how to back up your NetBackup catalogs, and how to recover them, using the
NetBackup Catalog Recovery Wizard.
– Finally, you learned know how to diagnose common catalog-related issues.
– NetBackup Administrator’s Guide, Volume I and Volume II
– NetBackup in Highly Available Environments Administrator's Guide
52

13-52
Lab 13: Managing and Protecting the NetBackup Catalog
Lab objectives
• Running NetBackup catalog-related reports
• Verifying, expiring, and importing backup images
• Configuring and running NetBackup catalog backups
• Recovering the catalogs using the NetBackup Catalog Recovery wizard
53

13-53
What did you learn?
lesson.
54
current lesson.

13-54
Question: Scheduling catalog backups
Which statement describes how Catalog backups can be scheduled?
A. According to frequency
B. According to calendar
C. After each backup session
D. All of the above
55

13-55
Answer: Scheduling catalog backups
Which statement describes how Catalog backups can be scheduled?
A. According to frequency
B. According to calendar
C. After each backup session
D. All of the above
The correct answer is D. NetBackup catalog backups can be schedule as a frequency- or calendar-based, as well as after
each backup session. Session end means that no backups are running (excluding catalog backup jobs).
56

13-56
Question: Catalog backup and storage unit
During a catalog backup, the NBDB and configuration files are backed up directly to the
storage unit.
A. True
B. False
57

13-57
Answer: Catalog backup and storage unit
During a catalog backup, the NBDB and configuration files are backed up directly to the
storage unit.
A. True
B. False
The correct answer is B. During a catalog backup, the configuration files are backed up directly to the storage unit,
however a copy of the NBDB is first placed in a staging location on the master server prior to being backed up.
58

13-58
Question: Catalog backup characteristics
Which characteristic applies to a catalog backup?
A. A catalog backup shuts down the NetBackup database.

B. A catalog backup must fit on a single tape.
C. A catalog backup can be configured to send disaster recovery information to an e-
mail address.
D. Catalog staging files deleted after a successful catalog backup.
59

13-59
Answer: Catalog backup characteristics
Which characteristic applies to a catalog backup?
A. A catalog backup shuts down the NetBackup database.

B. A catalog backup must fit on a single tape.
C. A catalog backup can be configured to send disaster recovery information to an e-
mail address.
D. Catalog staging files deleted after a successful catalog backup.
The correct answer is C. NetBackup performs online catalog backups, which can be sent to disk or tape, and the backup
can span multiple tapes if necessary. The catalog files that are sent to the staging location are no longer deleted after a
successful catalog backup (although prior versions of NetBackup did delete the staging files after a successful catalog
backup).
60

13-60
End of presentation
13-61
Lesson 14: Optimizing File System Backups
This is the “Optimizing File System Backups” lesson in the “Veritas NetBackup 8.1:

14-1
Policies
This lesson is the fourteenth lesson in this course.


14-2
Lesson objectives
Topic Objective
File system backup challenges Discuss solutions to today’s backup challenges.
Optimizing file system backups Enable NTFS and VxFS change logs, and synthetic full backups to
optimize file system backups.
Optimizing file system backups with Configure and manage NetBackup Accelerator.
NetBackup Accelerator
Using multiple data streams Configure a policy to take advantage of multiple data streams.
Optimizing tape drive performance Configure backups for optimum tape drive performance using
using multiplexing multiplexing.
Handling busy files on UNIX and Configure the way that NetBackup handles busy files on UNIX and
Windows file systems Windows, including using Windows Volume Shadow-copy Services
(VSS).

14-3
Topic: File system backup challenges
After completing this topic, you will be able to discuss solutions to today’s
backup challenges.
After completing this topic, you will be able to discuss solutions to today’s backup
challenges.

14-4
NetBackup solutions for common backup and restore challenges
Short backup windows Redundant data

• Multi Data Streaming • Deduplication
• Multiplexing • NetBackup Accelerator
• Incremental / Synthetic backups
• NetBackup Accelerator
Low network throughput Dense file systems

• Synthetic backups • FlashBackup
• NetBackup Accelerator • NetBackup Accelerator
Open or busy files

• VSS integration
• Off-host backups
The table on this slide lists some of the challenges that administrators face and the
solutions that NetBackup has to offer. Some of these solutions are discussed in the
topics of this lesson. Some topics may be covered in more detail elsewhere, such as the
appropriate NetBackup documentation for that feature, and the NetBackup Advanced
Administration course.

14-5
Understanding True Image Restore
• Restores the files that existed in the folders, during a TIR restore
– TIR does not restore deleted files.
– Normal restores will restore files that were deleted but had existed in the prior full or prior incremental
backups.
• Makes a list of the files that are in each directory at the time of backup
• Places list in a separate TIR file, which is backed up with the backup image
• Supported policy types: MS-Windows, Standard, NBU-Catalog
• Can be enabled with move detection
The purpose of True Image Restore is to ensure that when a full restore is performed
(which includes the last full backup plus all incrementals up to the recovery point),
NetBackup restores only those files that were present in the file system at the time of
the last backup. In other words, files that were deleted prior to the last backup in the
selected backup set, will not be restored. A normal restore would restore those files.
TIR guarantees that the restore will not overflow the file system during the restore, as a
normal restore may try to restore more files than ever existed in the file system at one
time, since it includes deleted files. Additionally, the user will not find files that he or
she had previously deleted.

NetBackup achieves this by making a list of the files that are present in the file system
during the backup. This list is stored on disk for 24 hours (which is configurable) as well
as stored with the backup image itself on the backup destination. If the disk copy of the
list doesn’t exist during restore time, this list of files is read first from the backup image
to assist in the true image restore of the backup.
The TIR attribute can only be selected for MS-Windows and Standard policy types. It is
automatically selected, and cannot be disabled, for the NBU-Catalog policy type.
TIR can be enabled with and without move detection, which is described in a following
slide.

14-6
Restore example for True image restore (TIR):
Most recent backup
Sun Mon Tue Wed Thu Fri Recovery point Recovery point
FULL INCR INCR INCR INCR INCR without TIR with TIR
File1 File1 File1 File2 File2 File2 File1 File7
File2 File2 File2 File6 File6 File6 File2 File8
File3 File3 File3 File7 File7 File7 File3
File4 File4 File5 File8 File8 File8 File4
File5 File5 File6 File5
File6 File6 File7 File6
File7
TIR information (files in file system) File8
File1 File1 File2 File2 File2 File7
File2 File2 File6 File6 File6 File8 Legend
File Modified; backed up
File3 File3 File7 File7 File7
File Unchanged; not backed up
File4 File5 File8 File8 File Deleted file
File5 File6 File New file
File6
7
The example in the slide shows a series of backups starting with a full backup on Sunday
followed by daily incremental backups. The files listed in each daily column show the
files in the file system and the actions performed on the file: modified, deleted, created
or left unchanged.
In the TIR information table, each column contains a list of the files that are present in
the file system at the time of each backup. These are the files that will be included in
the TIR file for that backup.
On Saturday you are asked to perform a full restore of the file system with Friday as the
recovery point. To do this you will need the Sunday full backup and each of the
incremental backups through Friday.
If you select the Normal Backups restore type, the files shown in the first column are
the files that would be restored without using TIR. The files that are restored include
files that were deleted prior to the backup on Friday.
If you select the True Image Backups restore type, the files shown in the second column
are the files that would be restored using TIR. The files that are restored are those that
were listed in the TIR file for the Friday backup. Any files that were not present in the
file system on Friday will not be restored.

14-7
Topic: Optimizing file system backups
After completing this topic, you will be able to enable NTFS and VxFS
change logs, and synthetic full backups to optimize file system backups.
After completing this topic, you will be able to enable NTFS and VxFS change logs to
optimize file system incremental backups.

14-8
Features that optimize incremental backups
• Reduces scan times for NTFS and ReFS file systems.

Windows • Enabled manually with fsutil command
Change • Enabled automatically by NetBackup with a host property.
Journal • Reverts to normal scan if too many changes occur (circular log with default size = 512
MB), or Collect true image restore information enabled in the policy.
• Reduces scan times for VxFS file systems.

Veritas File • Works best for large file systems with few changes.
System • Enabled automatically by NetBackup with a host property.
Change Log • Reverts to normal scan if errors encountered while processing log, or Collect true
image restore information enabled in the policy.
Even though an incremental backup backs up only those files that have changed,
NetBackup still has to examine every file in the file system to determine which files have
changed. This may involve examining millions of files to determine that only one file
needs to be backed up, which is unnecessarily time consuming.
One way to optimize incremental backups is to take advantage of change tracking logs
which are offered as a feature by some file systems. These logs record which files have
been modified or added since the last backup. With the log in place, NetBackup no
longer has to examine each file, instead it looks at the log file and backs up only those
files listed in the log.

The Windows NTFS change journal, also known as the Update Sequence Number (USN)
change journal, is a disk file that records information about the changes made to a file
or directory within a specific volume. By reading this file, backup programs can quickly
determine which files need to be backed up during an incremental backup, thereby
eliminating the need to scan each file on the volume and speeding up the backup
process.
The change journal is created on a volume by using the Windows fsutil command:
fsutil usn createjournal [m=max_value] [a=alloc_delta]
volume_pathname
Here is a sample command:
fsutil usn createjournal m=1000 a=100 C:

14-9
NetBackup will automatically enable the change journal for you when you enable the
functionality in the client host properties, in the NetBackup Administration Console.
This is discussed elsewhere in this lesson.
The change journal supports both NTFS and the Resilient file system (ReFS), introduced
in Windows Server 2012. ReFS may eventually replace NTFS.
The change journal is a circular file with a limited amount of allocated space. Once the
file has reached this limit, older entries will be overwritten. If there are many changes to
files in the volume in between backups, you may want to allocate additional space to
the change journal, to prevent losing older entries. When older entries are overwritten,
the change journal will not be used during the subsequent incremental backup, and
instead cause a full rescan of the file system. If the Collect true image restore
information setting is enabled in the policy (on the Attribute tab), then a full rescan of
the file system will also occur.
The Veritas File System (VxFS), is a file system which is supported on a number of Unix
and Linux platforms. VxFS is used to increase the performance and availability of
production data. VxFS is part of Veritas Infoscale, which replaced Veritas Storage
Foundation, the software suite which previously contained VxFS. For more information
about Veritas InfoScale Storage, visit https://www.veritas.com/product/storage-
management/infoscale-storage.
VxFS has a feature called the change log, which, when turned on, tracks changes to files
and directories. This log can be used to greatly speed up incremental backups, as it
prevents the scan that is normally required to find changed files. This works best on
large file systems with many files, and few changes.
The VxFS change log will not be used if the backup encounters any errors while
processing log, or if the Collect true image restore information setting is enabled in the
policy (on the Attribute tab).
Both of these log types require some configuration within NetBackup and at the file
system level.

14-10
Enabling the Windows Change Journal with NetBackup
11
NetBackup can be configured to monitor the Windows Change Journal and use the
information discovered within the Change Journal during backups. To do this,
NetBackup will create and maintain its own databases with data mined from the Change
Journal. NetBackup will then use its databases to assist in the discovery of files and
directories that have been changed between backups.
To configure NetBackup to monitor the Change Journal, from the Client Properties for a
client, expand Windows Client and select Client Settings. Mark the Use Change Journal
check box. This needs to be done individually for each NetBackup Windows client.
After enabling Use Change Journal, there will be a period of time before the Windows
Change Journal data can actually be used during backup. NetBackup requires a brief
period of time to establish its own change journal databases. If a backup is executed
during this time, error messages will be logged to the ‘Job Details’ indicating the reason
why the change journal data could not be used.
This option works together with the Use accelerator policy attribute and the
Accelerator forced rescan schedule attribute, discussed elsewhere in this lesson.

14-11
Understanding synthetic full backups
Week 1 S M T W Th F Sa
Week 2 S M
Synthetic full generation takes place on the media server, any
time before the next incremental on Monday night.
Client + =
Backup 1. Baseline 2. Incremental 3. Synthetic full
schedule: full backup backups backup
Mon 21:00 Fri 21:00
Time of Mon 07:30
Tue 21:00 Sat 21:00
backup: Sun 21:00 Wed 21:00 Sun 21:00 (Recorded time:
Thu 21:00 Sun 21:00:01)
12
The synthetic full backup feature eliminates the need to perform full backups of a client
machine for supported resource types.
1. During week one, perform a full backup, also known as a baseline backup. This is a
normal full backup operation.
2. Between this first full backup and the schedule for the next full backup, perform
incremental backups on the changes that occur. This is a normal backup procedure
and is usually performed daily.
3. During the next schedule for a full backup, instead of running a normal full backup,
run an incremental backup. In the example on the slide, instead of running a full
backup on the second Sunday at 9 P.M., an incremental backup was run.
4. Some time between this last incremental backup (on Sunday night, in the example)
and the next incremental backup (on Monday night), a synthetic full backup is run.
The synthetic full backup operation occurs on the media server, leaving the client free.
Because the synthetic full backup is executed on the media server without accessing the
client machine, it can be performed outside of the time-critical backup window,
reducing the overall backup window and associated network bandwidth requirements.
The newly created synthetic full backup replaces the baseline full backup and becomes
the baseline full backup for subsequent synthetic full backup operations.

14-12
Configuring synthetic backups
• Only file system backups are supported

1. Create policy • Select Standard or MS-Windows policy type
Set Collect true image restore information with move detection on the
policy:
2. Configure TIR
• Minimum one traditional full backup

• One or more incremental backups
3. Create schedules
• One full or cumulative backup with Synthetic backup
checkbox marked
13
To use the synthetic backup feature of NetBackup:

1. Create a policy with either the Standard or the MS-Windows policy type.
2. Mark the Collect true image restore information with move detection check boxes.
3. Create the policy with at least the following three types of schedules:
• One traditional full backup: The full backup must successfully run to completion.
• At least one incremental backup: The incremental backups capture the changes
since the last full or incremental backup.

• One full or cumulative backup with the Synthetic backup check box marked: The
synthetic backup is the combination and synthesis of the original full backup
with the incremental backups.
Optimized synthetics
Note that because synthetic backups involve taking the prior full backup and applying
all the incremental changes, using a deduplication storage destination may have
additional benefits in that the new synthetic full will require very little data copy
operations when creating the new full data. This is known as an Optimized Synthetic
backup in NetBackup, and is described in Article 100022690: Configuring Optimized
Synthetic Backups to NetBackup Deduplication Pools, found online at

14-13
Topic: Optimizing file system backups with NetBackup
Accelerator
After completing this topic, you will be able to configure and manage
NetBackup Accelerator.
14
After completing this topic, you will be able to configure and manage NetBackup
Accelerator.

14-14
Understanding NetBackup Accelerator
• NetBackup option that increases the speed of full
backups
1. Track log ensures only changed files are scanned
Client Backup server during backup
2. Minimum processing required
Application
2 3. Only changed data is sent to the storage server
Backup Backup 4. Requires less storage
agent
3 server • Synthesizes new full backups using old fulls, and
new incrementals
1 • Complementary technology to deduplication
File System
• Does not require any additional software or
4 installation
Change tracking
Backup
Data storage
15
NetBackup Accelerator is a licensed NetBackup feature that increases the speed of full
backups by using platform-agnostic file system change tracking track logs on the client
to identify changes that have occurred since the last backup. During an accelerator
enabled backup only the changed data are transferred to the deduplication storage .
On the storage, a new optimized synthetic full backup is created by combining the
changed data with pointers to the unchanged data from previous backups. This process
removes the need to transfer all the client data across the network.
This methodology uses less network bandwidth and reduces the overhead on client
resources such as CPU, memory, I/O and file system cache.

Note that although not required, NetBackup client-side deduplication can add benefits
related to better bandwidth usage, and is often used together with NetBackup
Accelerator. NetBackup Accelerator should be regarded as a complimentary technology
of client deduplication, and not as a replacement for it.
No further installation is required for NetBackup Accelerator. The necessary binaries are
included with the NetBackup client files.

14-15
NetBackup Accelerator requirements
System • All supported NetBackup client operating systems

requirements • Optional: Windows Change Journal (improves performance)
Versions NetBackup 7.5 or later for master servers, media server, and clients
License NetBackup Data Protection Optimization Option
Policies • Standard and MS-Windows

supported • VMware, Hyper-V, and NDMP (NetBackup-version dependent)
• NetBackup Media Server Deduplication Pools (MSDP)

Storage units • Cloud storage plug-ins
supported • Qualified OpenStorage (OST) vendors, where the Hardware Compatibility List shows
Accelerator, Accel_VMware, Accel_Hyper-V, Accel-NDMP, and so on.
16
The slide lists the requirements for NetBackup Accelerator. The feature is supported
starting in NetBackup 7.5 and later, and requires that all servers in the backup path
(master servers, media servers, and clients) are running a minimum of NetBackup 7.5.
Although the Windows Change Journal is not required, it can configured to work with
NetBackup Accelerator and additionally improve performance.
Note that OST vendors qualified for NetBackup Accelerator support are listed in the
Hardware Compatibility List. Refer to the NetBackup Master Compatibility List, found
online at http://www.netbackup.com/compatibility. Those that support Accelerator for
file and folder backups will show ”Accelerator”, and those that support Accelerator for
VMware will show “Accel_VMware”. Recent versions of NetBackup also support
Accelerator for additional data types, so you may also see “Accel_NDMP”, “Accel_Hyper-
V”, and possibly others in your NetBackup release.
14-16
How NetBackup Accelerator works
• During the first backup:

1. A full backup is performed.
2. A client track log is created.
• During successive backups:
1. Changes since the previous backup are identified.
• Client’s file system is compared to the track log from the previous backup.
• If enabled, the Windows NTFS change journal is used.
2. Client sends the media server a data stream consisting of:
• Data for changed file segments
• Metadata for unchanged segments (previous backup ID and data extents)
3. Storage server creates an optimized synthetic full backup.
• Changed segments are read and unchanged data is located in existing backups.
• Storage server combines changed segments with pointers to unchanged segments to create a new backup image.
17
During the first backup

After setting the Use Accelerator option in the policy attributes, the next backup of that
policy will be a full backup. At that time, a client track log will be created on the client
which will identify the master server, the storage server, the client, the policy and the
files that were backed up as well as the segments which make up each file.
During successive backups the following steps are performed:
1. File and directory meta data are compared with the track log to identify files that
have changed. The following criteria are used:
• NFS (Network File System): Normally used on Unix clients, Accelerator uses
mtime, ctime, and inode number, file size.
• CIFS (Common Internet File System): Normally used by Windows client,
Accelerator uses mtime, ctime, change_time, file size.
• NTFS (New Technology File System): Normally used by Windows client as a local
file system, Accelerator uses NTFS change journal, plus mtime, ctime,
change_time, file size.
If a file has not changed, the scan continues.
If file metadata has changed, the file is open, read, and the data fingerprints for
each 128K file segment are compared to the previous track log.
14-17
2. The client then sends a data stream to the media server consisting of the data for
the changed segments of each file and the metadata for the unchanged file
segments. This metadata will describe the backup ID and the data extents which
contain the unchanged segments.
3. The media server then creates a new optimized synthetic full backup by combining
each file’s changed segments with pointers to the file’s unchanged segments from
previous backups. Upon completion, there is a new backup image on the storage.
To summarize, only changed files are open and read, and only changed data segments
are sent to create the new backup image.
In addition, only changed file catalog information is sent, and the NetBackup catalog
backup image is also synthetically created reducing the meta data sent with each
backup.
14-18
NetBackup Accelerator operation modes
Operation
Windows UNIX Description
mode
• Uses the client track log to identify changes to the file system between
backups
Standard ✓ ✓ • Is enabled with the Use accelerator option under the backup policy
Attributes tab
• Uses the Windows NTFS / ReFS change journal to speed up

Use Change incremental backups
Journal ✓  • Enabled with the Use Change Journal option under the master server
Host Properties > Clients > Windows Client > Client Settings
• Uses checksums of the file contents during the backup for change
detection to establish a new baseline for the next Accelerator backup
Accelerator
forced rescan ✓ ✓ • Results in a slower backup
• Enabled with the Accelerator forced rescan option under the policy
Schedules tab
19
The standard operation mode uses the client track log to identify which files have
changed and exactly which segments of those files have changed. This functionality is
enabled by selecting the Use accelerator option under the backup policy attributes tab.
NetBackup 7.5 introduced a new client property called Use Change Journal to be used
in conjunction with the Accelerator feature. When this option is enabled, bpinetd.exe
generates a custom Change Journal Database which depends on the Windows NTFS or
ReFS change journal. The NetBackup generated database files are located on the root of
each lettered volume. These files are used to quickly identify which files have changed
since the previous backup. The use of the change journal is enabled by going to the Host
Properties on the master server and selecting Clients > Windows Client > Client
Settings and selecting the Use Change Journal option.
When selected, Accelerator forced rescan causes NetBackup Accelerator to use
checksums of the file contents during the backup for change detection to establish a
new baseline for the next Accelerator backup. This will cause the backup to run slower.
This feature is enabled with the Accelerator forced rescan option under the policy
Schedule tab.
14-19
Configuring NetBackup Accelerator
1. Configure NetBackup 2. Optional: Configure

Accelerator in the policy. Windows change journal.
A warning message results if Use

accelerator is enabled with an
unsupported OST storage unit.
20
The accelerator feature is enabled for a policy by selecting the Use Accelerator option in
the policy attributes. During the first backup after the feature has been enabled, a track
log will be created on each of the clients configured in the policy. The track log will be
specific for the policy, client and backup selections.
14-20
Optionally use the Windows Change Journal
1. Configure NetBackup 2. Optional: Configure

Accelerator in the policy. Windows change journal.
21
When the Use Change Journal option and the Use Accelerator are enabled together,
bpinetd will create the NetBackup change log databases to monitor the Windows NTFS
or ReFS change journal for changes in the file system metadata and to determine which
files are to be included in the backup. The bpbkar32 process will use this information to
create the list of files that need to be backed up, eliminating the need to examine each
file in the volume and speeds up the backup. This behavior is discussed in more detail
in a prior topic.
This option works together with the Use accelerator policy attribute and the
Accelerator forced rescan schedule attribute.
14-21
Job detail messages related to NetBackup Accelerator and NTFS
change journal
Without NetBackup Accelerator or Use change journal enabled
...
archive bit processing:<disabled>
not using change journal data for <E:\data>: not configured for use
With only NetBackup Accelerator enabled

...
accelerator enabled
...
accelerator enabled backup, archive bit processing:<disabled>
will attempt to use change journal data for <E:\data>
...
not using change journal data for <E:\data>: not configured for use
not using change journal data for enumeration for <E:\data> but will use it for change detection
accelerator sent 308224 bytes out of 3063808 bytes to server, optimization 89.9%
With NetBackup Accelerator and Use change journal enabled

...
accelerator enabled
...
accelerator enabled backup, archive bit processing:<disabled>
will attempt to use change journal data for <E:\data>
...
using change journal data for <E:\data>
accelerator sent 308224 bytes out of 3063808 bytes to server, optimization 89.9%
22
During a backup, the Detailed Status report in the Job Details will display various
messages depending on what feature is or is not enabled for that backup.
The slide shows the messages displayed when:
1. Neither the Use Accelerator nor the Use Change Journal features are enabled.
2. Only the Use Accelerator feature is enabled.
3. Both the Use Accelerator and Use Change Journal features are enabled.
Additional messages will be displayed if errors are encountered during the backup.
An example of a the full Job Details from an incremental backup job with both
NetBackup Accelerator and the Use change journal setting, is provided here, and
continues on the next page:
Dec 14, 2016 1:42:22 PM - Info nbjm (pid=2981) starting backup job (jobid=145)
for client console.example.com, policy LAB14-test-accelerator, schedule diff
Dec 14, 2016 1:42:22 PM - Info nbjm (pid=2981) requesting STANDARD_RESOURCE
resources from RB for backup job (jobid=145, request id:{0C9B33A2-C22D-11E6-
A149-9851E32BCF38})
Dec 14, 2016 1:42:22 PM - requesting resource master_msdp_stu
Dec 14, 2016 1:42:22 PM – requesting resource
lnxmaster.example.com.NBU_CLIENT.MAXJOBS.console.example.com
Dec 14, 2016 1:42:22 PM - requesting resource
lnxmaster.example.com.NBU_POLICY.MAXJOBS.LAB14-test-accelerator
Dec 14, 2016 1:42:22 PM - granted resource
lnxmaster.example.com.NBU_CLIENT.MAXJOBS.console.example.com
lnxmaster.example.com.NBU_POLICY.MAXJOBS.LAB14-test-accelerator
14-22
MediaID=@aaaai;DiskVolume=PureDiskVolume;DiskPool=master_msdp_dpool;Path=Pur
eDiskVolume;StorageServer=lnxmaster.example.com;MediaServer=lnxmaster.exampl
e.com
Dec 14, 2016 1:42:22 PM - granted resource master_msdp_stu
Dec 14, 2016 1:42:22 PM - estimated 0 kbytes needed
Dec 14, 2016 1:42:22 PM - Info nbjm (pid=2981) started backup
(backupid=console.example.com_1481740942) job for client
console.example.com, policy LAB14-test-accelerator, schedule diff on storage
unit master_msdp_stu
Dec 14, 2016 1:42:22 PM - started process bpbrm (pid=9508)
Dec 14, 2016 1:42:24 PM - Info bpbrm (pid=9508) console.example.com is the host
to backup data from
Dec 14, 2016 1:42:24 PM - Info bpbrm (pid=9508) reading file list for client
Dec 14, 2016 1:42:24 PM - Info bpbrm (pid=9508) accelerator enabled
Dec 14, 2016 1:42:25 PM - connecting
Dec 14, 2016 1:42:26 PM - Info bpbrm (pid=9508) starting bpbkar on client
Dec 14, 2016 1:42:26 PM - connected; connect time: 0:00:00
Dec 14, 2016 1:42:29 PM - Info bpbkar (pid=5176) Backup started
Dec 14, 2016 1:42:29 PM - Info bpbrm (pid=9508) bptm pid: 9569
Dec 14, 2016 1:42:29 PM - Info bpbkar (pid=5176) change time
comparison:<enabled>
Dec 14, 2016 1:42:29 PM - Info bpbkar (pid=5176) accelerator enabled backup,
archive bit processing:<disabled>
Dec 14, 2016 1:42:29 PM - Info bpbkar (pid=5176) will attempt to use change
journal data for <E:\data>
Dec 14, 2016 1:42:30 PM - Info bptm (pid=9569) start
Dec 14, 2016 1:42:30 PM - Info bptm (pid=9569) using 262144 data buffer size
Dec 14, 2016 1:42:30 PM - Info bptm (pid=9569) using 30 data buffers
Dec 14, 2016 1:42:30 PM - Info bptm (pid=9569) start backup
Dec 14, 2016 1:42:30 PM - Info bptm (pid=9569) backup child process is pid 9573
Dec 14, 2016 1:42:30 PM - begin writing
Dec 14, 2016 1:42:49 PM - Info bpbkar (pid=5176) using change journal data for
<E:\data>
Dec 14, 2016 1:42:49 PM - Info bpbkar (pid=5176) accelerator sent 3066880 bytes
out of 3063808 bytes to server, optimization 0.0%
Dec 14, 2016 1:42:49 PM - Info bptm (pid=9569) waited for full buffer 2 times,
delayed 1221 times
Dec 14, 2016 1:42:49 PM - Info bptm (pid=9569) EXITING with status 0 <---------
-
Dec 14, 2016 1:42:49 PM - Info lnxmaster.example.com (pid=9569)
StorageServer=PureDisk:lnxmaster.example.com; Report=PDDO Stats for
(lnxmaster.example.com): scanned: 2995 KB, CR sent: 1638 KB, CR sent over
FC: 0 KB, dedup: 45.3%, cache disabled
Dec 14, 2016 1:42:49 PM - Info bpbrm (pid=9508) validating image for client
console.example.com
Dec 14, 2016 1:42:50 PM - Info bpbkar (pid=5176) done. status: 0: the requested
operation was successfully completed
Dec 14, 2016 1:42:50 PM - end writing; write time: 0:00:20
14-23
Client track log files details
• Location on client:
– UNIX: /usr/openv/netbackup/track/master_server/
storage_server/client/policy_name/backup_selection
– Windows: install_path\NetBackup\track\master_server\
storage_server\client\policy_name\backup_selection
• Sizing depends on number of files and total amount of used space

– Approximated using formula: (# of files * 220) + ((Used disk space/128K) * 20)
– Example: 1 TB file system with one million files = ~ 360 MB track logs
• If necessary, refer to Article 100038114: How to redirect the NetBackup Accelerator track log to a
different location
24
After the Use Accelerator feature is enabled in the NetBackup policy it is necessary to
run a full backup. This full backup will be a standard full backup. During the backup a
client track log will be created and information about all of the files in the full backup
will be logged in the track log. Subsequent backups will use the track log to determine
what file segments have changed and need to be backed up. Also, the track log will be
used to determine what file segments have not changed, and this information will also
be transferred to the storage. The information about what has changed and what has
not changed will be used to create the optimized synthetic backup.
The track log is located on the client in the netbackup directory and is unique for each
client, policy and backup selection for that policy. Because of this, if a client is in more
than one policy , a track log will be created for each instance of that client in the
different policies. The file path for the track log ensures that the track logs are unique.
The slide shows the full track log path for UNIX and Windows clients.
The size of the track log will vary depending on the number of files and the total amount
of used disk space. The slide shows a formula for estimating the size of a client track log.
To change the track log location, refer to Article 100038114: How to redirect the
NetBackup Accelerator track log to a different location, found online at
14-24
Using NetBackup Accelerator with additional policies
Storage unit must support optimized

synthetics (such as MSDP and some
3rd-party OST devices)
If Use Accelerator is greyed out,

verify the NetBackup Data
Supported policy types: Protection Optimization Option
• VMware license is installed.
• Hyper-V
• NDMP
25
NetBackup Accelerator, in addition to supporting file system backups, is increasingly

being supported by other policy types. NetBackup 8.0 supports NetBackup Accelerator
for VMware, Hyper-V, and NDMP.
The example on the slide shows NetBackup Accelerator support for VMware.
Accelerator dramatically improves performance for full backups of virtual machines. It
does this by using VMware Change Block Tracking (CBT) to determine which blocks have
changed in a VMware virtual machine. NetBackup VMware policies are also configured,
by default, with the Block Level Incremental Backup (BLIB) feature. VMware BLIB also
uses CBT to track changed blocks for incremental backups.
Note that although BLIB improves incremental performance, it comes with some
restrictions around not being able to use NetBackup’s Granular Restore Technology
(GRT) for coordinated application protection in a VM backup. GRT requires a full backup
of the VM with application protection enabled in the NetBackup policy. NetBackup
Accelerator does provide the same excellent performance enabled by CBT tracking, and
because it is performing a full backup, additionally provides application protection with
GRT.
The requirement for Accelerator is that the destination storage in the policy supports
optimized synthetics. Essentially the storage must support deduplication. A check is
made by NetBackup when the Policy Storage is selected. If the storage does not support
optimized synthetics, you will not be able to select the Use Accelerator checkbox.
14-25
NetBackup FlashBackup
• Enables backups of raw partitions with the ability to restore individual files.
– Reads the entire disk, block by block, whether they contain data or are empty disk blocks.
– Works best when the file system contains a large number of files, and is predominately full
• Configured with FlashBackup and FlashBackup-Windows policy types.
Snapshot Backup Restore
Backup raw Restore

device data individual files
26
FlashBackup is a policy type that combines the speed of raw-partition backups with the
ability to restore individual files. The features that distinguish FlashBackup from other
raw-partition backups and standard file system backups are these:
• Increases backup performance as compared to standard file-ordered backup
methods. For example, a FlashBackup of a file system completes faster than other
types of backups when the file system contains a large number of files, and if most
of the file system blocks are allocated.
• Enables restore of individual files from raw-partition backups.
• Backs up the following file systems: VxFS (Solaris, HP, Linux, AIX), ufs (Solaris), Online
JFS (HP), and NTFS (Windows).
• Supports multiple data streams, to further increase the performance of raw-
partition backups when multiple devices are in the Backup Selections list.
For a complete list of supported platforms, snapshot methods, and data types, see the
NetBackup Snapshot Client Compatibility, found online at
http://www.netbackup.com/compatibility.
Restoring from a FlashBackup policy is the same as for any other backup. In the Backup,
Archive, and Restore interface, set the policy type to FlashBackup for UNIX clients and
FlashBackup-Windows for Windows clients.
A FlashBackup (or FlashBackup-Windows) backup supports both individual file restore
and raw partition restore. You can do either type of restore from the same backup. To
restore individual files, select Normal Backups on the Restore Files tab; to restore an
entire raw partition, select Raw Partition Backups.
14-26
Comparing NetBackup Accelerator and FlashBackup
NetBackup NetBackup
Issue
Accelerator FlashBackup
Backs up empty space:
Backup capacity Does not back up empty space • Efficient for relatively full file systems
• Not efficient for empty file systems
Compatibility Broad file system support More restrictive file system support
• Excellent for normal change rates

Change rate • Less effective if the change rate is Works similarly with any change rates
very high
Full recovery impacted by number of
Full recovery Full recovery is fast
files
27
Both NetBackup Accelerator and NetBackup FlashBackup may significantly improve the
performance of large file system with many files. The question of which feature to use
may arise. The answer to that question will depend on the characteristics of your client
and file system.
The slide covers some general guidelines based on file system properties:
• Backup capacity: NetBackup Accelerator simply tracks and backs up changed files.
FlashBackup, however, backs up the entire raw device, which means even empty
blocks in the file system are backed up. File systems that are not relatively full may
require long backup times due to these empty blocks.
• Compatibility: NetBackup Accelerator has broad file system support. FlashBackup
has more restrictive support, and doesn’t support encrypted file systems such as
deduplicated NTFS, and ReFS.
• Change rate: Although NetBackup Accelerator works well for normal file change
rates of file systems, for file systems with very high change rates FlashBackup may
work more efficiently.
• Full recovery: NetBackup Accelerator does not provide any advantage to full
recovery, as it is impacted by restoring the metadata for individual files, and
therefore time consuming when restoring all files. FlashBackup does have an
advantage in that raw data recovery is extremely fast, when restoring the entire data
set.
14-27
Topic: Using multiple data streams
After completing this topic, you will be able to configure a policy to take
advantage of multiple data streams.
28
After completing this topic, you will be able to configure a policy to take advantage of
multiple data streams.
14-28
Allowing multiple data streams
• Configured as a policy attribute

• Causes multiple backup jobs to be created from a single client
– One data stream failure does not affect the other data streams.
– Multiple backup selections can run simultaneously to:
• Different backup destinations.
• Same disk backup destination.
• Same tape drive (with multiplexing).
Client
File system 1 Job #1
29
Multiple data streams is a policy setting which allows NetBackup to create separate
backup jobs for entries in the backup selection list. This functionality is enabled by
marking the Allow multiple data streams check box on the policy’s Attribute tab. The
jobs are in separate data streams and can run concurrently.
Whether multiple backup jobs start for each client and how the backup selections are
divided into separate jobs are determined by the directives that you specify in the
backup selections list. The total number of streams and how many can run concurrently
are determined by the number of available storage units, multiplex settings, and the
maximum jobs parameters.
There are two main advantages to multiple data streams: independent data streams and
increased backup speed.
Because each stream is treated as a separate job, the data streams are independent. If
one of the streams or jobs fails, the other job is unaffected and can still complete
successfully. Only the failed jobs need to be restarted.
The other advantage of multiple data streams is increased backup speed, which occurs
when the multiple jobs can run concurrently. This means that, in theory, twice the
amount of data can be backed up in half the time. However, a reduction in backup
speed is also possible, for example, when the jobs are both running concurrently and
accessing the same source disks.
14-29
Configuring the jobs per client settings
• For all clients:
Modify value from

the default of 1
• For an individual client:
Enable and set for a specific client,

to override the global attribute
30
By default, NetBackup allows only one job to run at a time for an individual client. In the
case where two backup policies run simultaneously for the same client, this may
protection you from disk thrashing that would cause bad performance.
However, if you want to take advantage of performance benefits by having multiple data
streams, than you will need to override this default behavior.
The Maximum jobs per client setting (found in the master server host properties under
the Global Attributes tab) has a default value of 1. Change this value to be the
maximum number of concurrent jobs you want to allow for any client in your
environment.
To change the number of jobs for an individual client, modify the Maximum data
streams setting, which is found under the master server host properties under Client
Attributes. Add the client to the Clients list, and then modify the Maximum data
streams parameter by checking the box, and then setting the desired value.
14-30
Job behavior with and without multiple data streams (MDS)
• One job is created for each client in the • For each client, one job is created for
policy. each backup selection.
• All files in the backup selections are • Backup selections can be grouped into
backed up in a single stream. jobs using a special directive.
• Parent jobs are used to manage the
overall backup for a client.
Without multiple data streams With multiple data streams
Windows client:
Job 1 (Parent job)
Job 2
Job 1 Job 3
Job 4
UNIX client:
Job 5 (Parent job)
Job 6
Job 2 Job 7
Job 8
31
Parallel backup streams from a single client can significantly improve backup
performance. Parallelism is enabled by selecting Allow multiple data streams in the
policy attributes. Parallel data streams are managed within the backup selections list
definition.
The number of data streams that can be created and queued depends on the:
• Directives included in the Backup selections list of the policy
• Limit jobs per policy parameter for the policy
• Maximum jobs per client global attribute
Note: You can override this attribute on a per-client basis by using the
bpclient -max_jobs number command option.
The number of jobs that are displayed in the Activity Monitor is one for each stream for
a specific client, as well as a parent job that manages the streams for that client.
14-31
When to use multiple data streams
Use multiple data streams to:
• Reduce backup time by splitting up large backups and running jobs

concurrently.
• Make backup streams independent.
‒ Failure in one has no effect on another.
‒ Failed backup stream can be restarted without restarting the entire backup.
Do not use multiple data streams:
• When different backup selections share the same physical disk, as multiple
data streams may decrease performance.
• If network or drive performance is affected adversely.
32
Multiple data streams can reduce the time for large backups. The reduction is achieved
by splitting the data to be backed up into multiple streams, and then processing those
streams concurrently by the same, or different, backup storage destinations.
Additional benefits are reduced retry times in the case of failures, as each backup
selection can be sent as a separate stream, and an individual backup stream failure does
not impact the other backup streams.
As you fine-tune multiple data streams, it is very easy to reduce performance instead of
improving it by inadvertently enabling multiple data streams for multiple data sets that
reside on a single disk. This results in the disk “thrashing” as the backups are performed.
Overall performance in this case is often worse than if the systems on the disk were
backed up sequentially.
Enabling multiple data streams produces more concurrent backup jobs, which in turn
use additional network bandwidth and require more tape drives (or a higher level of
multiplexing). Use caution you do not overwhelm your network environment.
Note that if you want to take advantage of independent data streams for individual
backup job restarts, but do not want parallel backup jobs, simply limit the number of
concurrent jobs using the maximum jobs per policy, or the storage unit settings.
14-32
Configuring multiple data streams: Example 1
The number of streams determined by the Backup Selections list.
3 disk drives
Windows
client
C:\ E:\
4 jobs
L:\ 225 – Parent
226 – Child with C:\Data
227 – Child with E:\Data
228 – Child with F:\Data (waiting for drive)
33
The number of data streams can be established using a list of file paths, optionally with
wild cards. Each path defined or expanded by a wild card is placed in its own data
stream.
In the example on this slide, the Allow multiple data streams check box is marked
under the Attributes tab. The Backup Selections list contains three disk drives: C:\, E:\
and L:\. The Allow multiple data streams option together with the list of three disk
drives will generate four jobs in the Activity Monitor: one parent job and one job for
each drive or mount point.
Auto-discovery streaming mode is invoked if the Backup selections list contains either
the ALL_LOCAL_DRIVES directive or wildcards (without the NEW_STREAM directive). In
this mode, the Backup selections list is sent to the client, which preprocesses the list
and splits the backup into streams as follows:
• For ALL_LOCAL_DRIVES directive, NetBackup backs up the entire client, with each
drive volume (Windows) or mount point (UNIX) into its own backup stream.
• If wildcards are used, the expansion of the wildcards results in one stream per
wildcard expansion.
If the Backup selections list contains neither ALL_LOCAL_DRIVES nor wildcards, auto-
discovery mode is not used. In this case, the server performs the preprocessing (rather
than the client) and each Backup selections list entry becomes a separate stream.
14-33
NEW_STREAM directive
Windows
client
C:\ E:\
3 jobs
L:\ 229 – Parent
230 – Child with C:\Data and E:\Data
231 – Child with L:\Data
34
In the previous example we backed up three drives in three separate streams. If C:\ and
E:\ were logical partitions on the same physical disk you would not want to back them
up in separate streams. Doing so could cause excessive head movement on the drive as
it attempts to satisfy simultaneous read requests from different drive locations and
possibly result in poorer backup performance. The better method would be to put
drives C:\ and E:\ into one stream and the L:\ drive in a separate stream.
This is referred to as administrator-defined streaming mode, and can be accomplished
by using the NEW_STREAM directive.
Use of the NEW_STREAM directive follows these rules:
• The first use of this directive must be on the first line of the Backup selections list.
• A backup is split into a separate data stream at each point in the backup selections
list where the NEW_STREAM directive occurs. All file paths defined between
NEW_STREAM directives appear in the same data stream. The end of each stream is
defined by the start of a new stream (the NEW_STREAM directive).
• The last stream in the list is terminated by the end of the Backup selections list. A
NEW_STREAM directive is not required.
14-34
ALL_LOCAL_DRIVES
Windows directive
client
10 jobs
232 – Parent
C:\ H:\
233 – Shadow Copy Components
E:\ I:\ 234 – C:\ 238 – I:\
F:\ J:\ 235 – E:\ 239 – J:\
236 – F:\ 240 – K:\
G:\ K:\ 237 – G:\ 241 – H:\
(All drives on client)
35
The example in the slide shows a backup using the Allow multiple data streams option
combined with the ALL_LOCAL DRIVES directive in the Backup Selections list. The client
has nine local drives, each of which is backed up in a separate stream.
The ALL_LOCAL_DRIVES directive backs up all local and SAN attached disk drives
(Windows) and mounted file systems (UNIX). Drives using removable media are
automatically excluded as are NFS mounted file systems.
Using the ALL_LOCAL_DRIVES directive ensures that all of a client’s disks and file
systems are backed up even if new disks are added between backups.
Using ALL_LOCAL_DRIVES and Allow multiple data streams follows these rules:
• Can only be used for Standard and MS-Windows policy types.
• A new stream (backup job) is created for each disk drive or file system present on
the client.
• On Windows: An additional, separate stream is created to back up the System State
or Shadow Copy Components (depending on the client’s Windows version).
• File systems that are in a client’s exclude list may cause a backup job to appear in
the Activity Monitor but no files will be backed up. Refer to Article 100000779 for
details, found online at http://www.veritas.com/docs/100000779.
14-35
Topic: Optimizing tape drive performance using
multiplexing
After completing this topic, you will be able to configure backups for
optimum tape drive performance using multiplexing.
36
After completing this topic, you will be able to configure backups for optimum tape
drive performance using multiplexing.
14-36
Writing backups using multiplexing
Multiplexing (MPX) is used to:

– Send concurrent backups from one or more clients to a single storage device.
– Reduce the amount of time required to complete backups.
Client A
Disk
Media server
Client B Removable media
Disk
Client C
MH BH BH BH
Disk
Tape contains media header (MH), backup headers (BH),
and multiplexed (interleaved) images from each client.
37
NetBackup multiplexing sends concurrent backups from one or several clients to a single
storage device. NetBackup multiplexes the backups onto the media. Multiplexed and
unmultiplexed backups can reside on the same volume.
No special action is required to restore a multiplexed backup. NetBackup locates the
media and restores the requested backup.
• Slow networks and slow clients
The parallel data streams take advantage of whatever network capacity is available.
• Many short backups (for example, incremental backups)
In addition to providing parallel data streams, multiplexing reduces the time each
job spends waiting for a device to become available, and, therefore, better uses the
transfer rate of storage devices.
It is important to note that multiplexing can have an effect on restore times. This effect
can be positive or negative depending on the number of interleaved images, the type
and number of restores, and whether those restores are being performed concurrently.
Ensure that you use testing to determine the maximum effective multiplexing level that
still supports your backup and restore requirements.
14-37
Configuring multiplexing
• Set multiplexing on both the storage unit and the schedule:
Setting Defaults Why set MPX here?
Storage Unit >

• Fast device that handles many jobs concurrently
Maximum streams per
• Prevent “shoe-shining” on the tape drive
drive
• Many slow clients; many short backups
Schedule >
Media multiplexing • Prevent multiplexing for this backup or schedule,
if not desired
• Use multiplexing value between 2 to 32
• Determine maximum potential concurrent jobs =
(maximum streams per drive) x (# of drives)
• Set storage units with appropriate fragment sizes
38
Multiplexing must be set in two places in the NetBackup configuration: the storage unit
and the policy schedule. Note that if you change these values, the changes do not take
effect until the next time a schedule runs.
• The Maximum multiplexing per drive setting for a storage unit specifies how many
backups NetBackup can multiplex onto any single drive in the storage unit. You set
this value for each storage unit. The number can range from 1 through 32, where 1
is the default and specifies no multiplexing. The maximum number of concurrent-
backup jobs that NetBackup is allowed to attempt equals the sum of the concurrent-
backup jobs that can run on the storage units. Choose a value based on the ability of
your media server to handle parallel jobs. Testing may be required to find an
optimum value.
• The Media multiplexing setting on a policy’s schedule also limits how many streams
can be interleaved for a multiplexed job, where the default is set to 1 (no
multiplexing). This allows you to set the multiplexing ability at the storage unit, but
restrict it for specific backup policies and schedules.
To reduce the impact on restoring individual files from multiplexing backup, set a
fragment size on the storage unit. This is set in kilobytes (KB). A rule of thumb can be
the amount of data a drive can write in 10 minutes
14-38
Topic: Handling busy files on UNIX and Windows file
systems
After completing this topic, you will be able to configure the way that
NetBackup handles busy files on UNIX and Windows, including using
Windows Volume Shadow-copy Services (VSS).
39
After completing this topic, you will be able to configure the way that NetBackup
handles busy files on UNIX and Windows, including using Windows Volume Shadow-
copy Services (VSS).
14-39
Handling busy files on UNIX clients
bp.conf options:
BUSY_FILE_PROCESSING
BUSY_FILE_ACTION
Busy file action Action meaning

MAIL Mail a busy file notification message to the BUSY_FILE_NOTIFY_USER.
REPEAT Retry the backup on the busy file. A retry count can be added.
IGNORE The file is backed up as is, and a log entry indicates the file was busy.
BUSY_FILE_NOTIFY_USER Specify the user to be notified (default mail recipient is root).
40
During backups, NetBackup may encounter what is referring to as busy files. On some
operating systems, a busy file – a file that is currently in use by an application or process
– may prevent copying and backing up the data.
On UNIX and Linux, busy files do not normally cause issues, however there are facilities
in NetBackup to customize the behavior when encountering files that can’t be backed
up.
Configure busy-file settings for UNIX clients using the NetBackup Administration Console
under client host properties > UNIX Client > Busy File Settings. Set the appropriate
actions.
Alternatively, you can configure busy-file processing as follows:
1. Add the BUSY_FILE_PROCESSING option to the client’s
/usr/openv/netbackup/bp.conf file on the master server. This enables
busy-file processing.
2. Add other busy-file options to control the processing of busy files. These other
options can exist in both the client’s bp.conf file and the user’s
$HOME/bp.conf file. The user’s bp.conf file takes precedence when the
options are in both places.
Different users on the same client can have different configurations for that client. In
this case, these configurations are saved in the $HOME/bp.conf file.
14-40
Handling busy files on Windows clients
Enabled by default for

Windows clients
Add clients to
customized settings
41
On Windows, busy files can often cause NetBackup to not have access to a file, and
result in status code 1 errors for backups. Open file backup options, which allow for
busy file processing, are set for each client in the Client Attributes section of the master
server host properties. List the clients for which you want to control the open file
backup options in the Clients section of this dialog box. After the client is added to the
Clients list, you can manipulate the settings. Note that by default no clients appear in
this list, and it is the responsibility of the administrator to add clients here manually.
In current versions of NetBackup, the default snapshot provider used for Microsoft
Windows clients is Volume Shadow Copy Service (VSS), which is provided by Microsoft.
Snapshot usage and error control settings are set here. Individual drive snapshot usage
takes a snapshot of each item in your files list individually. Global drive snapshot usage
takes a single snapshot of all items in your files list together. When using VSS, consider
how snapshots of drives are taken for each client when making this setting. Snapshot
error control can be set to either abort a backup when a snapshot fails, or disable the
snapshot for that backup and continue when a snapshot operation fails.
NetBackup versions prior to version 7.x used the Veritas Snapshot Provider (VSP) as the
default method of backing up open and active files on Microsoft Windows clients. Refer
to the appropriate NetBackup documentation for information on VSP, or using it with
older Windows versions that do not support VSS.
14-41
VSS configuration tips
• Recommendations depend on the VSS provider.

In most cases default settings are appropriate.
• In some cases, place the shadow copy on a separate
volume, for example:
VSSAdmin Add ShadowStorage /For=C: /On=D:
/MaxSize=3GB
• In a virtual machine, place the shadow copy on the same
volume (itself).
• Refer to :
– Microsoft TechNet article: Best Practices for Shadow Copies of
Shared Folders:
https://technet.microsoft.com/en-us/library/cc753975(v=ws.11).aspx
42
Microsoft Volume Shadow Copy Service (VSS) is supported on systems running Windows
Server 2003 and later. VSS runs on various Windows client operating systems, but
cannot be configured or customized on all Windows versions. Third-party software
vendors provide additional components that work in conjunction with VSS.
Specifications for configuration and use of VSS differ according to the nature of the
hardware on which it is running, the purpose of the machine, and many other
configuration factors.
VSS shadow copies for different volumes are set through the Disk Management utilities
of the Windows server on which they are installed. An example of the Shadow Copies
settings are shown on this slide. Shadow Copy settings can also be made from the
command line using the vssadmin utility. The vshadow utility is also included in
Software Deployment Kits for Windows Vista and later versions, such as Windows 2008.
Either of these utilities can be used from the command line to configure VSS.
It is not possible to make general recommendations for the configuration and use of
VSS, but the following are useful general tips:
• Create the shadow copy for a particular volume on a separate volume. This is so that
a shadow copy does not fill up its own volume.
• Do not set a Maximum size limit for the shadow copy volume. After a volume fills
up, VSS automatically deletes expired shadow copy images.
14-42
Lesson summary
• Key points
– In this lesson, you learned how NetBackup provides solutions to some of today’s backup challenges.
– You also learned the benefits of the NTFS and VxFS change logs, and how to enable NetBackup
Accelerator.
– Finally, you learned how to configure a policy to use multiple data streams and the benefits of handling
busy files and using VSS.
– NetBackup Snapshot Client Administrator’s Guide
43
14-43
Lab 14: Optimizing File System Backups
Lab objectives
• Configuring and using NetBackup Accelerator
• Configuring for and using multiple data streams
• (Optional) Configuring and performing multiplexed backups
44
14-44
What did you learn?
lesson.
45
current lesson.
14-45
Question 1: NetBackup Accelerator requirement
What must be enabled for NetBackup Accelerator?
A. True Image Restore (TIR) with move detection

B. NTFS change journal
C. VxFS change log
46
14-46
Answer 1: NetBackup Accelerator requirement
What must be enabled for NetBackup Accelerator?
A. True Image Restore (TIR) with move detection

B. NTFS change journal
C. VxFS change log
The correct answer is D. The NTFS change journal is an optional feature that can enhance the speed of a NetBackup
Accelerator backup; but it is not required. Veritas File System (VxFS) is not yet supported as a change log type with
NetBackup Accelerator. TIR is not a required feature with NetBackup Accelerator.
47
14-47
Question 2: When to use MDS
When is it most appropriate to use multiple data streams?
A. When different backup selections are on the same disk

B. When backing up ALL_LOCAL_DRIVES to multiple tape drives
C. When performing backups over a network that is very busy
D. When you have very small backup jobs
48
14-48
Answer 2: When to use MDS
When is it most appropriate to use multiple data streams?
A. When different backup selections are on the same disk

B. When backing up ALL_LOCAL_DRIVES to multiple tape drives
C. When performing backups over a network that is very busy
D. When you have very small backup jobs
The correct answer is B. Each tape drive can receive a data stream from a different disk. Requesting data from multiple
directories on the same disk can cause disk thrashing. When performing backups over a network, multiple streams can
add network contention. Small backup jobs complete too quickly to greatly benefit from multiple data streams.
49
14-49
End of presentation
14-50
Lesson 15: Collecting Logs and Diagnostic Information
This is the “Collecting Logs and Diagnostic Information” lesson in the “Veritas
15-1
Policies
This lesson is the fifteenth lesson in this course.
15-2
Lesson objectives
Topic Objective
Performing basic NetBackup Perform very basic troubleshooting for NetBackup environments.
troubleshooting
Identifying NetBackup processes, Identify and manage the NetBackup processes and services that run
services, and daemons on NetBackup master servers, media servers, and clients.
NetBackup logging overview Describe legacy and unified NetBackup logs.
Using the support utilities Use the NBSU and NBCPLOGS utilities, and describe the Logging
Assistant.
Using NetBackup support resources Identify available resources for NetBackup troubleshooting.
15-3
Topic: Performing basic NetBackup troubleshooting
After completing this topic, you will be able to perform very basic
troubleshooting for NetBackup environments.
After completing this topic, you will be able to perform very basic troubleshooting for
NetBackup environments.
15-4
A NetBackup troubleshooting checklist
Before contacting support
1. Define the problem
For example, for failed backup jobs: Note the status code, examine the Detailed Status report,
and determine what hosts are involved.
2. Examine the NetBackup reports
3. Verify services/daemons running on NetBackup hosts
4. Answer: “Has this backup ever worked?”
• If no: Check the initial configuration (policy, storage units, and so on)
• If yes: Check what has changed (upgrades, network, devices)
5. Depending on type of failure, contact internal groups, such as database
administrators (DBAs), network or storage groups
6. Note any patterns to the failure: Time of day? Network segment? Operating
system type? Storage units?
If the Activity Monitor shows a failed job, use this checklist to investigate the cause of
the failure.
1. Define the problem: Note the status code, examine the Detailed Status report in the
Job Details, and identify the servers involved in the backup .
2. Examine the NetBackup reports
3. Confirm that all services or daemons are running
4. Answer the question “Is this the first attempt?” for what appears to have caused the
error.
• If yes check the configuration for errors that may have caused this issue.
• If no review and note any changes made to the NetBackup configuration or
system environment.
5. Discuss problem with relevant internal groups (DBA,s network or storage group)
6. Note any patterns to the failure: time of day? Network segment? OS type? Storage
unit?
These steps should be undertaken before calling support. If the problem persists, open
a case with Veritas technical support. Gather all known details about the problem, and
be prepared to collect debug logging information.
15-5
Detailed Status report
• Job failed with status code 58: Can’t

connect to client.
• The bpbrm process on the media
server failed to connect to the client
One place to start your investigation of a failed job is in the Detailed Status report in the
Job Details.
This report will show the processes (and PIDs) involved in the backup as well as other
useful details.
In this example the job failed with status code 58: Can’t connect to client. The bpbrm
(backup and restore manager) process on the media server was unable to connect to
the bpcd (client service) process on the client. These processes will be discussed later in
this lesson.
15-6
Using the NetBackup Reports utility
• Shows information from various NetBackup database

and log sources
– Error logs created on a 24-hour cycle
– Logs management in master server host properties > Clean-up
– Error logs located in:
UNIX /usr/openv/netbackup/db/error
Windows install_path\NetBackup\db\error
• Can be run on the command line
Refer to the NetBackup Commands References Guide
Use the Reports utility in the NetBackup Administration Console to generate reports to
verify, manage, and troubleshoot NetBackup operations. NetBackup reports display
information according to job status, client backups, and media contents.
The reports draw upon a variety of sources including various NetBackup databases and
logs.
This lesson focuses on the Status of Backups report, the Problems report, the Media
Logs report and the All Log Entries report. These reports come from the error catalog
located in install_path\netbackup\db\error on Windows and under
/usr/openv/netbackup/db on UNIX. The first three reports are subsets of the
entire catalog and are created by using filters to select only certain parts of the entire
catalog. The All Log Entries report will display the entire catalog contents.
The catalog is a log which is automatically setup and enabled at installation. Error logs
are created on a 24-hour cycle. At midnight each day, the daily log is closed and a new
one is opened for the next days events. By default the logs are kept for 28 days. This can
be configured in the master server host properties under the Clean-up tab.
See the NetBackup Commands Reference Guide for more information about running
commands.
15-7
The All Log Entries report
Displays the contents of the

entire error catalog
bperror -all -U
The All Log Entries report displays logging information captured by NetBackup. The
information in this report is derived from the error catalog on the master server. Unlike
the detailed debug logs, the logging recorded to the error catalog is always active;
therefore, information is always available in this report. This report displays all the
information in the error catalog, including routine messages and events and problems.
When possible, NetBackup displays a severity for each message.
To access the information in this report from the command line, type:
bperror -all -U
15-8
The Status of Backups report
Displays history of completed job

information and status codes
bperror -backstat -U
The Status of Backups report shows status and error information about the jobs that
completed within the specified time period. If an error occurred, a short explanation of
the error is included in the report.
The format is similar to that presented in the Activity Monitor, however, the two are
independent. Deleting a job from the Activity Monitor will have no affect on the output
of this report. Additionally, the Status of Backups report does not have any job details
for each job attached, as the Activity Monitor does.
The report can be filtered by specifying a time and date range, the media server, the
client or the job ID.
bperror -backstat -U
15-9
The Problems report
Lists problems the server has

logged
bperror -problems -U
10
The Problems report displays logging information from the error catalog on the master
server. The Problems report is basically a filter for the All Log Entries report. The
Problems report only displays messages that appear to be errors or problems; routine
messages are not displayed. This report can be very helpful in troubleshooting failed
jobs because there is less output to sort through, and the output is more likely to be
relevant.
The report can be filtered by specifying a time and date range, the media server, the
client or the job ID.
bperror -problems -U
15-10
The Media Logs report
Displays media errors and

messages
bperror -media -U
11
The Media Logs report displays errors that are specifically related to backup media, for
example, physical errors related to tape or disk media. The Media Logs report is another
filter of the All Log Entries report, and derives its information from the error catalog on
the master server.
Note that there are also separate reports for Tape Logs and Disk Logs, which filter the
results to display only errors related to tape or disk media, respectively. Having separate
reports for tape and disk enables you to identify problems quickly without sorting
through a large amount of information. It is also convenient if the responsibility for disk
backups and tape backups are assigned to different operators.
The report can be filtered by specifying a time and date range or the media server.
To access the information on this report from the command line, type:
bperror -media -U
15-11
Exporting reports
Windows
Unix
Example: bperror -media -U > file.txt
12
There may be times when you would like to have a copy of a report outside of the
NetBackup administration console. The Export option allows you to export a copy of the
report to a text file on disk. From there the report can be printed, imported to a
different application or distributed to other interested stakeholders.
The slide shows the process on both UNIX and Windows master servers.
Clicking on File in the toolbar displays a drop down menu. Selecting the option Export
will allow you to name the export file and specify where the file is to be created.
You can achieve a similar result from the command line by redirecting the output to a
file
bperror -media -U > file.txt
15-12
Topic: Identifying NetBackup services, daemons and
processes
After completing this topic, you will be able to identify and manage the
NetBackup services, daemons and processes that run on NetBackup master
servers, media servers, and clients.
13
After completing this topic, you will be able to identify and manage the NetBackup
services, daemons and processes that run on NetBackup master servers, media servers,
and clients.
15-13
Introduction to NetBackup processes
• Typically start automatically when the system starts up.

Daemons / • Typically remain active in the background until manually
Services stopped, or the system is shut down.
• Run on the master server, media servers and clients.
• Inactive until summoned by a daemon or service, or by

another process.
Processes
• Typically active during specific tasks, such as backups or
restores.
14
In multitasking computer operating systems, there are some computer programs that
run in the background and are always active. On UNIX, these are often referred to as
daemons. On Microsoft Windows systems, these types of programs are called services.
In NetBackup, daemons/services can be found on the master server, media servers and
clients. Because of the many administrations tasks and backup operations performed on
the master server you will find a large number of daemons/services running there. The
media servers and clients will have far fewer daemons/services running.
The term process refers to a program that is inactive until summoned by a
daemon/service.
Unless a specific distinction is required, the term process is frequently used in the
general sense to denote both daemons/services and processes.
Note of interest: The word daemon comes from the ancient Greek and is an older form
of our word demon. In modern English demons are definitely from the dark side but in
ancient Greece, daemons were neither good nor evil. Their job was to help define a
person’s character or personality. Ancient Greeks had personal daemons, not unlike the
guardian angels some people claim to have today. It has been said that UNIX has both
daemons and demons.
15-14
Monitoring services/daemons in the Activity Monitor
15
You can use the NetBackup Activity Monitor to monitor the services/daemons which are
currently running:
1. Invoke the NetBackup Administration Console.
2. Verify that you are monitoring the master server.
3. Click Activity Monitor in the object tree area.
4. In the details pane, click the Daemons tab.
From here, you can view the details of the active services and daemons.
15-15
Monitoring processes in the Activity Monitor
16
To monitor which processes are currently running:

1. Invoke the NetBackup Administration Console.
2. Verify that you are monitoring the master server.
3. Click Activity Monitor in the object tree pane.
4. In the details pane, click the Processes tab.
From here, you can view the details of processes.
15-16
Viewing NetBackup services in Windows Services
Article 100002166: How to verify the required NetBackup

daemons / services are up running on a master server
17
On Windows servers, the Windows Services tool (also started with services.msc) shows
persistent NetBackup services configured for the NetBackup host. The master server
services, with the associated executable name, most closely associated with backup
operations include:
Service name Executable name
NetBackup Request Manager bprd
NetBackup Jobs Manager bpjobd
NetBackup Data Base manager bpdbm
NetBackup Proxy Service nbproxy
NetBackup Job Manager nbjm
NetBackup Resource Broker nbrb
NetBackup Enterprise Media Manager nbemm
This slide shows an example screenshot for a master server. On media servers or clients
the list of NetBackup services will be much shorter, and not include many of these
services.
For more details, refer to Article 100002166: How to verify the required NetBackup
daemons / services are up running on a master server, found online at
15-17
Viewing processes using the bpps utility
If you want to … On Windows, enter… On UNIX, enter…
Display active NetBackup and Media Manager

bpps bpps -a
processes
Display detailed NetBackup processes list (Windows

bpps –l n/a
only)
Display active NetBackup processes by server role bpps –i NB_CLIENT_ALL

n/a
(Windows only) bpps –i NB_SERVER_ALL
Display NetBackup, Media Manager and shared
n/a bpps -x
processes (UNIX only)
Display Media Manager processes only bpps –i MM_ALL vmps
Article 100002166: How to verify the required NetBackup

daemons / services are up running on a master server
18
NetBackup provides a command line utility called bpps that displays active NetBackup
processes. The ps part of bpps indicates that it runs similarly to the UNIX ps
command.
The bpps utility is located in the following directory:
• Windows: install_path\NetBackup\bin\bpps
• UNIX: /usr/openv/netbackup/bin/bpps
The command options for bpps depend on the operating system platform. Examples of
some command options are listed on the slide. There is also a similar command for
Media Manager processes on UNIX, vmps.
The Windows version of bpps is quite powerful, similar to a resource kit utility for the
amount of information it can reveal about processes. For more help on bpps for
Windows, type: bpps -?
Run bpps on the system when it is idle and then again when a backup is running to
determine which processes become active for the backup.
For more details, refer to Article 100002166: How to verify the required NetBackup
daemons / services are up running on a master server, found online at
15-18
Verifying daemons before device configuration
Master server Media server Client

bprd bpcd bpcd
bpjobd vmd vnetd
bpdbm nbrmms bpinetd
nbproxy (Windows only)
nbpem
nbjm
nbrb
nbemm
…
bpcd
vmd
19
The master server has many NetBackup daemons which run persistently. The slide
shows a subset of these, including important processes such as bprd, bpdbm, nbpem,
and so on.
The number of NetBackup daemons that run on a media server is highly dependent on
what devices have been configured for that media server. When first installed, a media
server has far fewer active services than a master server. These initial services include:
NetBackup Client Service bpcd
NetBackup Volume Manager vmd
NetBackup Remote Manager and Monitor Service nbrmms
A client has even fewer NetBackup daemons, which includes only those services that
you will also find on any NetBackup host (including the master and media servers):
NetBackup Client Service bpcd
NetBackup Veritas Networking Daemon vnetd
NetBackup Legacy Client Service (Windows only) bpinetd
The slide shows the daemons that you’d expect to see running after installing
NetBackup, but prior to configuring any backup devices on the media servers.
15-19
Verifying daemons after tape device configuration

bprd bpcd bpcd
bpjobd vmd vnetd
nbpem ltid
nbjm tldcd
nbrb tldd
nbemm avrd
…
bpcd
vmd
20
On this slide, a number of additional daemons are shown on the media server. These
daemons start running after tape devices are configured, and include:
Logical Tape Interface Daemon ltid
Tape Library DLT (Robot) Control Daemon tldcd
Tape Library DLT (Drive) Daemon tldd
Automatic Volume Recognition Daemon avrd
Note that the name for the tldcd and tldd process depends on the type of library and
drives configured, and you may see more than just the one process if you have multiple
different devices configured. For example, some LTO drives are configured with the
NetBackup “Half-inch” designation, and would result in the tlhcd and tlhd processes.
15-20
Verifying daemons after MSDP configuration

bprd bpcd bpcd
bpjobd vmd vnetd
nbpem ltid
nbjm tldcd
nbrb tldd
nbemm avrd
…
bpcd spad
vmd spoold
21
On this slide, a number of additional daemons are shown on the media server. These
daemons start running after a Media Server Deduplication pool is configured, and
include:
NetBackup Deduplication Manager spad
NetBackup Deduplication Engine spoold
15-21
Verifying daemons during a backup

bprd bpcd bpcd
bpjobd vmd vnetd
nbpem ltid
nbjm tldcd bpbkar
nbrb
nbemm
Metadata tldd
avrd
Data
…
bpcd spad
vmd spoold
bpbrm
bptm
22
During some operations you will expect to see additional processes. As an example,
during a simple backup you may see the following processes appear on the media
server:
NetBackup Backup and Restore Manager bpbrm
NetBackup Tape Manager bptm
Note that although the process has the name “Tape Manager”, it is used for backups
that go to disk storage units as well.
During a backup, you will also see this process on the client:
NetBackup Backup and Archive Process bpbkar
For other operations, such as duplication and restore jobs, you may see different
processes. This is discussed further in the NetBackup Administration Guides as well as
the NetBackup Maintenance and Troubleshooting course.
15-22
Managing processes using commands and scripts
If you want to … Then enter …

netbackup stop (UNIX)
Stop all processes gracefully
bpdown –f -v (Windows)
netbackup [start] (UNIX)
Start all processes
bpup –f -v (Windows)
Stop the Device Manager stopltid
Stop all processes, daemons, and console processes bp.kill_all (UNIX only)
Start all processes, daemons, and console processes bp.start_all (UNIX only)
The shutdown command may be specific to your version of

NetBackup. Refer to the documentation for details.
23
As was mentioned previously, daemons/services are active as long as NetBackup is

running. The only way to stop daemons/services is to shut down NetBackup altogether.
You can stop daemons or services individually without shutting down NetBackup in the
NetBackup Administration Console. The table on this slide lists some command-line
equivalents of these actions.
The first few commands show how to stop and start NetBackup processes gracefully for
both UNIX and Windows NetBackup servers.
Individual daemons or services have different commands by which you can terminate
and restart them. For example, to terminate ltid (the Device Manager), enter the
stopltid command.
See the NetBackup Commands Reference Guide for detailed information about how to
stop and restart specific daemons/services.
Consider that stopping certain daemons or services may impact other daemons or
services. For example, stopping the NetBackup Request Daemon (bprd) stops all future
backup and restore activity. Jobs already running are able to complete because they no
longer depend on bprd.
NetBackup provides a the bp.kill_all and bp.start_all scripts that are
intended to stop and start all daemons when no backup or restore operation is in
progress.
15-23
Topic: NetBackup logging overview
After completing this topic, you will be able to describe legacy and unified
NetBackup logs.
24
After completing this topic, you will be able to describe legacy and unified NetBackup
logs.
15-24
NetBackup debug logs and support
• NetBackup support may request:

– Debug logs related to the investigated problem.
– Output from NetBackup utilities such as nbsu.
– Evidence such as operating system files and logs.
• Knowledge of how to enable, configure and collect logs is useful.
• Customers are not expected to read and interpret debug logs.
• Number of logs requested will depend on how well defined and understood the problem
is.
• In a production environment, logs should be enabled with the guidance of support.
25
The following slides are designed to help you understand how NetBackup logging works
so that you can better assist support in the resolution of your NetBackup problem.
In order to investigate the problem support may request debug logs of the processes
associated with the problem. In addition, support may request the output of certain
NetBackup utilities such as nbsu. Other evidence such as operating system files and
logs may also be requested.
The process of log collection can be facilitated if you understand how NetBackup logging
works. In the following slides you will learn how to enable, configure and collect
NetBackup logs.
NetBackup customers are not expected to read and interpret logs. That is the job of the
support engineer who is working your case. They have the knowledge, skills, tools and
experience to examine and process the logs.
The number of logs requested will depend on the nature of the problem. If the problem
is ill defined or the source of the problem is not readily obvious, more logs may be
requested. If the problem is well defined and specific, then fewer logs will be required.
15-25
Understanding NetBackup debug log types
• Every NetBackup process has an available debug log.

• These logs are commonly requested by Support.
• There are two types of logs in NetBackup:
Legacy logs Unified logs
• Example process: bprd • Example process: nbpem

• Limited control of logs • Greater control of logs
• Must be manually enabled • Enabled automatically
• Debug messages only • Application, diagnostic, and debug messages
• Can be read with any editor • Require separate utilities to read, manage and
• Logging level set in Host Properties configure logs
26
Every NetBackup process (including daemons and services) has a detailed debug log
associated with it. This is in addition to the default information that NetBackup logs to
the error catalog on the master server. Each log is a text-based file containing detailed
output from its associated process.
In NetBackup, there are two kinds of processes, each using a different logging method:
• Most NetBackup processes and components that have been added to NetBackup
since the NetBackup 6.0 release use unified logs. In general, these include processes
that begin with nb, and components that use the Private Branch Exchange (PBX) to
communicate. These logs are turned on all the time and are very configurable.
• Processes that existed prior to the NetBackup 6.0 release and continue to be used
today are referred to as legacy processes. These processes often start with bp (for
example bprd or bptm). The debug logs for these processes are referred to as legacy
logs and are not active by default. Legacy logs are less configurable than the newer,
unified logs, but are still very useful for troubleshooting. Best practice says to only
activate these logs when needed for troubleshooting purposes. They can grow very
large and can also affect performance.
There is one process, nbproxy, which uses legacy logs even though it is not a legacy
process.
15-26
Enabling and managing NetBackup logs
Legacy logs Unified logs
1. Create directories, under: 1. Logs automatically created in:

– UNIX: /usr/openv/netbackup/logs – UNIX: /usr/openv/logs
– Windows: install_path\NetBackup\logs – Windows: install_path\NetBackup\logs
2. Set or verify log levels: 2. Set or verify log levels:
– In host properties – In host properties (for nbpem, nbjm and nbrb only)
– Using the nbsetconfig command – Using vxlogcfg utility (all unified log processes)
3. Wait for processes to start logging – In the nblog.conf file in the NetBackup
automatically within 60 seconds install_path (verify only)
4. For intermittent processes, restart the task

(such as the backup) which starts those
processes
27
Enabling NetBackup logs depends on the type of logs you are managing. The slide
discusses both methods.
Legacy logs
Legacy debug logs provide a record of NetBackup activity related to specific services and
processes. The table on this slide shows the general process for enabling legacy logs.
1. Legacy debug logs are created by a process only if a subdirectory for that process
has been created. In general, these directories have the format:
• UNIX: /usr/openv/netbackup/logs/process_name
• Windows: install_path\NetBackup\logs\process_name
Legacy logging processes creates one or more debug log file per day, with the
format:
• UNIX: username.mmddyy_seqnum.log
• Windows: domainname@username.mmddyy_seqnum.log or
ALL_ADMINS.mmddyy_seqnum.log
The mklogdir script, found in the logs folder, can be used to create some, or all
the legacy logging directories. Because this script can creates log directories for all
possible daemons and processes and increase disk I/O, it is instead recommended
to run the command with the named directory as an argument.
Note: Earlier versions of NetBackup used a different naming convention, which did
not include the username.
15-27
Note: Refer to Robust Logging settings for details on number of log files created
each day.
2. Various logging parameters are configured in the NetBackup host properties for the
host. For example, NetBackup retains debug logs for the number of days specified by
the Duration to Keep Logs global attribute (default:28 days).
Log files can grow very large. Enable these files only if unexplained problems exist.
Delete logs and the directory when they are no longer needed. Veritas recommends
only to increase bprd and bpdbm logging levels under guidance of Support.
3. Starting in NetBackup 7.6 many services/daemons dynamically update within 60
seconds of the time they are changed. There is no need to restart NetBackup
services/daemons, as logging starts automatically.
Prior to NetBackup 7.6, to activate the logs, restart the process in question. For
example. a persistent daemon or service, such as bprd or bpdbm, must be stopped
and restarted to activate logging. On UNIX systems, use netbackup stop and
netbackup start to start all of the daemons. On Windows systems, use the
bpdown and bpup commands to start the entire NetBackup system.
4. A transient process, such as bpcd or bptm, logs to its directory the next time the
process runs. This means that logging some processes requires you to restart the
task associated with the process or issue, such as re-running the backup or restore
job.
Media manager processes do require a restart, and do not perform logging dynamically.
Logging for these media manager processes is configured in the volmgr directory:
• UNIX: /usr/openv/volmgr/logs/logging_dir_name
• Windows: install_path\VolMgr\logs\logging_dir_name
Unified logs
Unified logging creates log file names and messages in a format that is standardized
across Veritas products. Many NetBackup processes use unified logging.
1. Unified logs are enabled automatically and the logs are written into user definable
directories. The default directory on UNIX systems is /usr/openv/logs. On
Windows systems the logs are written in install_path\NetBackup\logs.
2. Various properties of the logs are defined in the nblog.conf configuration file
located in the /usr/openv/netbackup and install_path\NetBackup
directories. The nblog.conf file is configured using the vxlogcfg command.
Features such as log location, log size, number of logs to keep, roll over mode and
logging levels can be configured using vxlogcfg. In addition, the debug logging
level for nbpem, nbjm and nbrb can be configured through the master server Host
Properties. Doing this will update nblog.conf.
Making changes to the logging properties does not require a restart of
daemons/services.
15-28
Setting logging host properties
nbsetconfig
29
The Logging host properties apply to currently selected master servers, media servers,
and clients. The available properties differ between a server and a client.
Access the host properties from within the NetBackup Administration Console for the
host, and select the Logging tab.
The Global logging level setting is used for setting the debug level for all legacy debug
logs. Alternatively, Process specific overrides can be used to specifically set levels for
some individual processes, different from the global level.
It is possible to change logging level in the host properties, or by modifying the
bp.conf configuration file in UNIX.
Check your specific version of NetBackup for supported logging levels in the host
properties and the bp.conf file. Eight logging levels are supported in NetBackup 7.7:
no logging (-2), minimum logging (-1), same as global level (0), or low to maximum
debugging (1-5).
Logging for critical processes creates logs for critical NetBackup processes automatically
by creating the appropriate log directories. Check your version of NetBackup for a
specific list of processes. NetBackup 8.0 lists processes for the the master server (bprd,
bpdbm), media server (bpbrm, bptm, bpdm) and the client (bpfis), as long as they are
running NetBackup 7.7 or later.
15-29
Using commands for unified logs
Configure unified logging with vxlogcfg
• Configure debug logging level for nbpem:
vxlogcfg –a –p nb –o nbpem –s DebugLevel=3
• Configure the default maximum number of log files :
vxlogcfg –a –p nb –o Default –s NumberOfLogFiles=6
Manage unified logs with vxlogmgr

• Show all nbpem log files from the last 24 hours:
vxlogmgr –s –p nb –o nbpem –t 24
• Delete logs from last 12 hours:
vxlogmgr –d –p nb –t 12
View unified logs with vxlogview

• View unified log entries associated with Job ID 1150:
vxlogview –d all -X "jobid=1150" > job1150.txt
30
The vxlogcfg command is used to change the logging settings. Settings can be
changed for individual processes which are identified in the command by their
originator ID (OID). The OID can be in the form of a name (nbpem, nbjm, etc) or a
number (116, 117, etc.). A list of OID name and numbers can be found in the NetBackup
Troubleshooting Guide.
Similarly, the nblog.conf configuration file, which is located in the
/usr/openv/netbackup (UNIX) and install_path\NetBackup (Windows)
directories, can be used to identify originator IDs and the short names for processes.
Note that this file should only be changed using the vxlogcfg command. Do not edit
it manually.
Here are some sample lines from nblog.conf showing the OID and settings for nbjm:
# 117. Job Manager
117.L10nResource=nbjm
117.NtEventLogSourceName=nbjm
117.OIDNames=nbjm
117.LogDirectory=nbjm
Settings can also be changed for ALL processes. Finally, the Default value for a given
setting can be changed.
15-30
Disabling debug logs
Disabling legacy logging

• Delete the relevant debug log folder in the NetBackup log folder.
• Do not delete the AltPath or the user_ops folders, if present.
• Do not delete the mklogdir script
Disabling unified logging

• Application-level messages cannot be disabled.
• Use vxlogcfg to modify diagnostic and debug-level messages.
• Use vxlogmgr to purge existing logs to reclaim disk space.
Note: Minimize the logging level or disable debug logs unless you are actively troubleshooting.
31
Unless you are actively trying to capture a failure scenario, it is recommended to keep
logging at a minimum. Logs can have a tremendous impact on NetBackup performance
and disk space on the volume where logs exist.
Disable and purge legacy NetBackup logs by deleting the folder for the corresponding
logs in the NetBackup logs directory. The AltPath and user_ops folders, if present,
are part of normal NetBackup operations, and they must not be deleted. Also, do not
delete the mklogdir script.
Unified logs cannot be completely disabled, but the amount of detail logged and the
corresponding performance overhead varies based on the verbose settings.
The following commands revert debug and diagnostic unified log messages to
their default verbosity levels:
vxlogcfg –a –p 51216 –o Default –s DiagnosticLevel=6
vxlogcfg –a –p 51216 –o Default –s DebugLevel=1
Veritas recommends setting logging levels to their default settings versus
disabling them. Setting DebugLevel=0 and DiagnosticLevel=0 should
not be performed.
15-31
Making the most of NetBackup logging
• An understanding of NetBackup processes and process flow is essential in knowing

where and when to apply logging.
• Support can assist in debug log gathering and troubleshooting.
• Reset logging to minimum levels when not troubleshooting.
• For additional troubleshooting information:
– Refer to the NetBackup Troubleshooting Guide, NetBackup Status Code Reference Guide, NetBackup
Commands Reference Guide, and NetBackup Logging Reference Guide
– Attend the NetBackup: Advanced Administration course.
– Attend the NetBackup: Maintenance and Troubleshooting course.
32
The most efficient way to enable logging in NetBackup and to quickly gather the
required information from debug logs is to understand how NetBackup inter-process
communication works, and the direction of communication and data within the
NetBackup architecture. This information is best garnered over time and with
experience, but can be assisted by attending the Veritas NetBackup Advanced
Administration and Veritas NetBackup: Maintenance and Troubleshooting courses, by
reviewing the NetBackup Troubleshooting Guide, and by contacting Veritas Support.
15-32
High-level NetBackup process flow of a simple backup
Master Request Daemon Scheduler Job Manager Resource Broker
server (bprd) (nbpem) (nbjm) (nbrb)
Database Manager Communications

Image
catalog (bpdbm) (bpcompatd)
NetBackup Database
Metadata (NBDB)
Media Communications
Device Manager Backup/Restore (bpcd) Client
server Communications
(ltid) Manager
(bpcd)
(bpbrm)
Metadata
Backup and Archive
Tape Manager Client (bpbkar)
or
(bptm) Data
Client’s data
33
This slide shows the connections among the major processes of the master server, the
media server, and the client, during a standard backup job. By understanding this
architecture, you can get a better idea of where to apply logging. For example, if you
believe that NetBackup is having a communication or authentication problem during
backups, then applying logging to the bpcd, bpbrm, bpbkar, and bptm processes may
make sense. If you think that NetBackup is having problems allocating media or devices
during a backup, then logging of nbrb, nbemm (which is part of NBDB), and nbjm would
be appropriate.
In the diagram on the slide, some processes have been colored slightly differently to
show that they are persistently running while NetBackup is running. In NetBackup these
are also known as daemons or services: bprd, bpdbm, nbpem, nbjm, nbrb, nbemm,
bpcd, and ltid. Other more transient processes, represented by boxes with a dashed
outline, only start running when a backup job occurs: bpbrm, bptm, and bpbkar. In
addition, the dashed lines represent the flow of data, the dotted lines represent the
flow of metadata, and the solid lines represent the flow of communication to complete
a backup job.
For additional information, see the NetBackup Troubleshooting Guide and attend the
Veritas NetBackup: Maintain and Troubleshoot course.
15-33
Topic: Using the support utilities
After completing this topic, you will be able to use the NBSU and NBCPLOGS
utilities, and describe the Logging Assistant.
34
After completing this topic, you will be able to use the NBSU and NBCPLOGS utilities,
and describe the Logging Assistant.
15-34
Describing the NetBackup Support Utility (NBSU)
• Collects information about the operating system, network, and NetBackup environment
• Runs various operating system and NetBackup commands, based on switches and
NetBackup host role
• Frequently requested by Support
• Located in:
UNIX /usr/openv/netbackup/bin/support
Windows install_path\NetBackup\bin\support
• Writes results to the following directories:

UNIX ./output/nbsu/hostname_host-role_YYYYMMDD_HHMMSS
Windows C:\users\username\output\nbsu\hostname_host-
role_YYYYMMDD_HHMMSS
35
The NetBackup Support Utility (NBSU) is a Veritas utility used to gather diagnostic
information. By default, NBSU gathers appropriate diagnostic information based on the
operating system and NetBackup environment. The amount of information gathered by
NBSU can be qualified using command-line switches. The path to the NBSU command is
shown on the slide.
NetBackup Support may request for the output of NBSU to be e-mailed or submitted to
them.
NBSU results are written to the following directories:
• UNIX: ./output/nbsu/hostname-role-YYYYMMDD_HHMMSS
• Windows:
C:\Users\username\output\nbsu\hostname-
role_YYYYMMDD_HHMMSS
Output can be redirected to a different output directory by using the command:
nbsu –odir destination_directory
15-35
Running NBSU
If you want to … Then enter …
Run nbsu using default options nbsu
Lists the available diagnostics in an unzipped output file. No

nbsu –l -nozip
diagnostics are run.
Select an individual diagnostic command to run. The output
nbsu -d NBU_bpmedialist
file is zipped by default.
Select the network group of diagnostics to run, but skip the
nbsu -g NET -s NET_dd
NET_dd diagnostic.
Select the diagnostics associated with the NetBackup exit
nbsu -nbu_e 41
status code 41.
36
NBSU switches enable the collection of selective information. The following table
describes the switches used in the examples in the table on the slide:
Switch Description
-l List the diagnostic commands that are selected to run.
-d name Run the specified diagnostic commands or procedures. Use nbsu -l
to obtain a list of commands and procedures.
Note: Multiple -d options can be listed, for example:
-d OS_general -d OS_env
-nozip Do not compress the output files.

-g group_name Run the diagnostic commands or procedures related to the group
name. Diagnostic groups are OS, DEV, NET, NBU, and MM.
Note: Multiple -g options can be listed, for example: -g OS -g
DEV
-s name Skip the diagnostic command, procedure, or group listed.
-nbu_e number Run only the diagnostic commands or procedures related to the
specified NetBackup exit status.
See the online help provided by nbsu –H for details on usage and nbsu –L for the
complete list of diagnostics and commands.
15-36
Example NBSU output on Windows
• Stored in a CAB file
• Includes many separate files
containing collected information
Sample of registry
information collected
37
This screenshot shows the text files which are packed into the CAB file. The names of
the individual files suggest the type of information collected.
This screenshot shows the contents of one of these files. The example displayed shows
the values collected for the
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion registry key.
15-37
Example NBSU output on UNIX
• Stored in a gzipped tar file
• Includes many separate files
containing collected information
Sample of general environment

information collected
38
This screenshot shows the text files which are packed into the compressed (.tar.gz)
file. The names of the individual files suggest the type of information collected.
This screenshot shows the contents of one of these files. The example displayed shows
some operating system environment information.
15-38
Describing nbcplogs
• Log collection utility, which includes logs such as:

NetBackup legacy logs NBDB logs Windows Event logs
NetBackup Unified logs Web server logs Private Branch Exchange logs
NetBackup Activity logs Job try logs Virtual machine mapping logs
NetBackup Vault logs VxFI logs True Image Restore (TIR) information
• Copies logs from various locations to a common area
• Runs the nbsu utility, by default
• Allows specification of start and end times for log data
• Allows for compression and bundling of logs
• Does not upload the data to NetBackup Support
To learn more about the methods to upload logs, refer to
Article 100038665: Methods to provide data for Technical Support cases
39
When you open a case with support, support may ask you to collect various logs to help
debug the issue. The requested logs, such as legacy logs, Unified logs, and so on, may be
in many places.
Examples include the NetBackup relational DB logs (NBDB logs), Activity logs (used to
generate NetBackup reports), Legacy logs, PBX logs, True Image Restore (TIR)
information, Jobs try logs, NetBackup Vault logs, Media Manager logs, VM mapping logs
(file mapping for virtual machine backups), Unified logs, Webserver logs, Windows
Event logs, and VxFI logs (logs for snapshot providers).
nbcplogs is a NetBackup utility which makes the collection of these logs much easier.
nbcplogs gathers NetBackup and system logs into a tar format file and then compresses
them to facilitate the uploading of the tar bundle to the Veritas Evidence Server. By
default, nbcplogs searches for all logs generated during the last 24 hours. There are
switches you can use to override the defaults.
Prior to NetBackup 8.0, this utility was also used to upload files to support. Because of
security changes to the Veritas FTP server, this feature has been removed from the
nbcplogs utility and the Logging Assistant. Logs must be manually uploaded.
To learn more about the methods to upload logs, refer to the Article 100038665:
Methods to provide data for Technical Support cases, found online at
15-39
Understanding nbcplogs command line syntax
To run nbcplogs… Run…
With all default options nbcplogs path
To bundle and compress nbcplogs path –B -c
With start and end date nbcplogs --start MM/DD --end MM/DD path
For recent timeframe

nbcplogs –d 5m path
(example: last 5 minutes)
To select only NetBackup and unified

nbcplogs –l nbu,vxul path
(VxUL) logs
To display short help nbcplogs --help
40
This slide shows a sample of the nbcplogs command line syntax. The variable path
signifies the folder or directory used. For more details refer to the NetBackup
Commands Reference Guide. All NetBackup documentation can be downloaded from
the SORT website at https://sort.veritas.com/netbackup.
15-40
Collecting nbcplogs on Windows and UNIX
Windows UNIX
accelerator.vmware-logs\ accelerator.vmware-logs/
allwebapps-logs\ Logs allwebapps-logs/
dberror-logs\ collected dberror-logs/ nbsu
db-logs\ db-logs/ output
eventlog-logs\ extra-logs/
nb-logs\ lnxmaster_master_20180128_124517.tar.gz
pbx-logs\ nb-logs/
purdisk.Agent_extra_paths_log-logs\ pbx-logs/
purdisk.Agent-logs\ purdisk.Agent_extra_paths_log-logs/
telemetry.dataset-logs\ purdisk.Agent-logs/
telemetry.domaininfo-logs\ puredisk.mtstrm-logs/
telemetry.runtime-logs\ telemetry.dataset-logs/
trylogs-logs\ telemetry.runtime-logs/
vault-logs\ trylogs-logs/
vxfi-logs\ vault-logs/
vxul-logs\ vxul-logs/
webconsoel-logs\ webconsoel-logs/
winmaster_master_20180128_114122.tar
nbsu Logs
output collected
41
This slide shows the output generated by running the nbcplogs command on both
UNIX and Windows. This command collects all logs and also runs the nbsu utility.
The output is written to the destination directory, as defined in the command.
15-41
Introduction to the Logging Assistant
• Shortens time required to set up, collect, and upload

debug logs
• Provides Wizards to quickly troubleshoot a problem
• Collects 3 categories of data:
– Debug logs
– NBSU diagnostic information
– Additional evidence
• Provides ability to set logging on inaccessible clients
• Refer to Article 100028985: Logging Assistant FAQ
42
The Logging Assistant is a helpful tool that can shorten the time that is required to set
up and collect debug logs and other information. Because Logging Assistant
automatically performs a number of functions, you can avoid the problems that are
associated with manually logging into NetBackup hosts, creating log directories, and
changing logging levels.
The Logging Assistant uses a series of wizards to help quickly troubleshoot a problem.
Depending on the category of NetBackup problem, the tool suggests the possible hosts
that may be involved in the problem and the logs that should be enabled on those
hosts. The tool also collects NetBackup debug logs, nbsu diagnostic information, as well
as additional evidence such as operating system files related to troubleshooting.
To use the Logging Assistant, make sure that NetBackup (7.6 or later) is installed on all
NetBackup hosts involved in the process. No special licensing is required. However, you
must have root permissions for UNIX, and administrator privileges for Windows, to use
the Logging Assistant. For more details, refer to the NetBackup Administration Guide.
Note: With NetBackup 8.0, the feature for uploading logs to the FTP server has been
removed from the nbsu and nbcplogs utilities and the Logging Assistant. Logs that have
been collected by the Logging assistant and the other support utilities can be manually
uploaded to the Veritas Evidence Server.
For more information, refer to Article 100028985: Logging Assistant FAQ, found online
at http://www.veritas.com/docs/100028985.
15-42
Topic: Using NetBackup support resources
After completing this topic, you will be able to identify available resources
for NetBackup troubleshooting.
43
After completing this topic, you will be able to identify available resources for
NetBackup troubleshooting.
15-43
Useful guides for troubleshooting
Can be downloaded from the NetBackup SORT

website at https://sort.veritas.com/netbackup
44
NetBackup has a rather extensive set of documentation. The entire documentation set
can be downloaded through the NetBackup SORT website at
https://sort.veritas.com/netbackup.
Three guide books are particularly useful for troubleshooting. These are the NetBackup
Status Code Reference Guide, the NetBackup Logging Reference Guide and the
NetBackup Troubleshooting Guide.
The NetBackup Troubleshooting Guide is very useful in learning how NetBackup works
under the covers. Understanding how NetBackup inter-process communication works,
and the direction of communication and data within the NetBackup architecture is key
to troubleshooting problems within NetBackup. This information is best garnered over
time and with experience, but can be assisted by reading the available documentation
and by attending the Veritas NetBackup Advanced Administration and Veritas
NetBackup: Maintain and Troubleshoot courses.
In addition, the NetBackup SORT website provides links to online NetBackup
communities and forums. Also consider joining your local NetBackup user group and
attending Vision, Veritas’s annual user and technical conference. For more information
on Vision, visit the Veritas Open Exchange website at https://vox.veritas.com/.
15-44
Escalating problem to NetBackup support
Contacting support
1. If problem persists, open a support case:
• Go to https://support.veritas.com
• Sign in or register
• Create a new case or manage an existing case
2. Be prepared to collect debug logging information
3. Upload requested logs and data to support
For information about support policies and options refer to Support Fundamentals:
https://www.veritas.com/content/support/en_US/terms/support-fundamentals.html
45
The slide lists some simple steps when contacting NetBackup support.
1. If you cannot resolve the problem on your own, open a support case. First go the
Veritas Support web site at https://support.veritas.com. At that site, sign in or
register for a new account, and then create a new case or manage an existing case.
2. Be prepared to collect debug logging information.
3. Upload the debug logging information to support.
Information about support policies and options can be found online at
https://www.veritas.com/content/support/en_US/terms/support-fundamentals.html.
15-45
Accessing the Veritas support website
Access Veritas Support directly at https://support.veritas.com

or through SORT at https://sort.veritas.com/netbackup
46
Various methods may be available to upload and download a small number of files
direct to an existing Veritas Support case. Examples include:
• Direct file transfer to an existing case via the Veritas Support web portal using
existing Veritas Account credentials.
• Direct file transfer using a file transfer website (https://mft.veritas.com)
• Direct file transfer using SecureFTP (sftp://sftp.veritas.com).
• FTP transfer to a designated folder using credentials provided by Technical Support.
Please contact your support engineer, if you are unsure about which method to use.
For more information, refer to Article 100038665: Methods to provide data for Technical
Support case, found online at http://www.veritas.com/docs/100038665.
15-46
Lesson summary
• Key points
– In this lesson, you learned to perform very basic troubleshooting for NetBackup environments, including
how to identify and manage the NetBackup processes and services that run on NetBackup master
servers, media servers, and clients.
– You also learned to describe legacy and unified NetBackup logs, and how to use the NBSU and nbcplogs
utilities, and describe the Logging Assistant.
– Finally, you learned how identify available resources for NetBackup troubleshooting.
– NetBackup Logging Reference Guide
47
15-47
Lab 15: Collecting Logs and Diagnostic Information
Lab objectives
• Viewing, stopping and starting the NetBackup services
• Running NetBackup reports for troubleshooting
• Using the nbsu and nbcplogs commands
• (Optional) Viewing and setting debug logging properties
• (Optional) Enabling NetBackup legacy debug logging
• (Optional) Viewing debug logging levels for unified logs
48
15-48
What did you learn?
lesson.
49
current lesson.
15-49
Question: Starting NetBackup services on Windows
Which command starts the NetBackup services on Windows?
A. The bpup command

B. The netbackup start command
C. The start services command
D. The bpup all command
E. The bp.start_all command
50
15-50
Answer: Starting NetBackup services on Windows
Which command starts the NetBackup services on Windows?
A. The bpup command

B. The netbackup start command
C. The start services command
D. The bpup all command
E. The bp.start_all command
The correct answer is A. None of the other commands are valid on a Windows NetBackup host, although some are valid
on a UNIX NetBackup host.
51
15-51
Question: Reading NetBackup logs
Which statement is correct?
A. You can read NetBackup logs in the NetBackup Administration Console.

B. You can read NetBackup logs in OpsCenter.
C. You can read NetBackup legacy logs using vxlogview.
D. You can read NetBackup unified logs using vxlogview.
52
15-52
Answer: Reading NetBackup logs
Which statement is correct?
A. You can read NetBackup logs in the NetBackup Administration Console.

B. You can read NetBackup logs in OpsCenter.
C. You can read NetBackup legacy logs using vxlogview.
D. You can read NetBackup unified logs using vxlogview.
The correct answer is D. The unified logs are not stored in plain text. Legacy logs are created in plain text and can be
viewed in any text editor, like Notepad. You can set the logging levels in NetBackup Administration Console. OpsCenter is
used to generate reports and monitor NetBackup.
53
15-53
Question: About the nbcplogs utility
Which statement best describes the nbcplogs utility?
A. It copies NetBackup logs to the OpsCenter server.

B. It collects a variety of log files.
C. It makes backup copies of NetBackup logs.
D. It compresses NetBackup log files.
54
15-54
Answer: About the nbcplogs utility
Which statement best describes the nbcplogs utility?
A. It copies NetBackup logs to the OpsCenter server.

B. It collects a variety of log files.
C. It makes backup copies of NetBackup logs.
D. It compresses NetBackup log files.
The correct answer is B. The nbcplogs utility collects a variety of log files. For example, nbcplogs collects unified logs,
legacy logs, NBDB logs, TIR info, PBX logs, web service logs and more.
55
15-55
End of presentation
15-56
Appendix A: Introduction to Application and Database

Backups
This is the “Introduction to Application and Database Backups” appendix in the “Veritas
A-1
Lesson objectives
Topic Objective
Application protection concepts Discuss application backup types, and the features of Granular
Restore Technology (GRT) and Block Level Incremental Backups
(BLIB).
Introduction to database backups Discuss database backup and restore concepts.
Introduction to enterprise Discuss options for backing up and restoring Exchange, Active
application backups Directory, SharePoint, and Enterprise Vault.
A-2
Topic: Application protection concepts
After completing this topic, you will be able to discuss application backup
types, and the features of Granular Restore Technology (GRT) and Block
Level Incremental Backups (BLIB).
After completing this topic, you will be able to discuss application backup types, and the
features of Granular Restore Technology (GRT) and Block Level Incremental Backups
(BLIB).
A-3
Application backup concerns
Data consistency
0110 1101 • Is the data consistent for recovery?
• Does the backup require application state changes?
Scheduling
• Who is initiating the backup: NetBackup or the application?
• Are there restrictions on when the backup runs?
Automation
• How is the application put into and out of a backup state?
• What additional automation or notification is required?
This slide describes the high level concerns you need to consider when preparing for
application backups. At a minimum, you should ask and answer the questions shown on
the slide. For many of the popular databases, such as Oracle, Microsoft Exchange, and
Microsoft SQL, there are NetBackup agents that answer these questions and simplify
the configuration and running of backups and restores of these databases.
A-4
How backups are initiated in NetBackup
Automatically
• Scheduled in NetBackup with frequency, calendar, or automatic schedule types
• Started by the NetBackup scheduler
Manually
• Sometimes referred to as immediate backup
• Run manually from the NetBackup Administration Console, OpsCenter, or command line
• May be automated with a script, cron (UNIX), Task Scheduler (Windows), or a third-party job
scheduler
On an application or user schedule

• Timing originates from the client
• Runs and is managed by NetBackup
Backups can be initiated in a number of ways in NetBackup:

• Most backups start automatically based on the schedules defined by the NetBackup
administrator. These include full schedules, incremental schedules (both differential
and cumulative), and automatic schedules, used by some NetBackup agents to
control when the application schedule runs. These schedules tend to be based on
frequency or on a calendar.
• Manual backups enable you to perform the backup immediately, on demand. For
this reason, they are sometimes known as immediate backups. Manual backups can
be initiated from any of the NetBackup administrative interfaces, including the
Administration Console, the command line, and OpsCenter. Manual backups can
also be run by schedulers outside of NetBackup, such as scripts, the cron utility, or
the Windows Task Scheduler.
• Application or user schedules, including user backups and archives, are client-
requested backups that enable the end-user or application on the NetBackup client
to control when a backup runs and which information is contained in the backup. By
default, users and applications on the client do not have permission to request
backups: the NetBackup administrator must create specific schedules to allow this,
and may choose to limit client requested backups to specific hosts or at specific
times of the day. Client requested backups do not use the policy’s Backup Selections
list; the user or application always chooses what is to be protected at the time the
backup runs. Some application backups may be initiated by special automatic
schedules by the NetBackup scheduler.
A-5
NetBackup policy types
Data type Policy type examples Description
• Standard
File system Perform UNIX and Windows file system backups
• MS-Windows
NetBackup NBU Catalog Protect the NetBackup master server catalogs
• VMware
Virtualization Performs backups of virtual machines
• Hyper-V
• MS-SQL-Server
• Oracle
Databases Perform online backups of databases
• Sybase
• DB2
• MS-Exchange-Server
• MS-SharePoint
Applications Perform online backups of enterprise applications
• Lotus-Notes
• Enterprise-Vault
As shown on the slide, there are many policy types in NetBackup, which correspond to
different ways of handling different types of data:
• File system data
File system backups tend to use either Standard or MS-Windows policy types to
back up UNIX or Windows file systems, respectively.
• NetBackup data
The NBU-Catalog policy type is special, and used specifically to back up the
NetBackup master server configuration, databases, and catalogs.
• Offsite data copies
The Vault policy type is used with the NetBackup Vault feature, for making and
tracking offsite copies of data for disaster recovery purposes.
• Databases, applications, and virtual machines
Many of the other policy types are used to back up specific applications, file
systems, or virtual machines. The policy type helps NetBackup determine how to
communicate and collect data. It performs this in coordination with the application,
sometimes with the goal of higher availability or automation of tasks, such as
controlling the starting and stopping of services, log truncation, or enabling online
backup methods.
A-6
Choosing a policy type (Oracle example)
Database and Database and
associated files associated files
Backups Restore
• Option 1: NetBackup file level

1. Shut down the Oracle database.
2. Use a Standard/MS-Windows policy to back up the Oracle database files.
3. Restart the Oracle database.
• Option 2: RMAN controlled
1. Create a backup in RMAN that backs up the Oracle database to backup files.
2. Use a Standard/MS-Windows policy to back up the backup files.
• Option 3: NetBackup for Oracle agent
Use an Oracle policy type with the NetBackup agent for Oracle, which enables RMAN to perform backups
directly to NetBackup and restore directly from NetBackup.
When configuring your environment to back up an application, it is important to note

that there may be multiple ways of achieving the same goal: being able to back up and
restore data.
When choosing the appropriate type of policy, consider the following:
• What kind of clients are going to be backed up by this policy?
• What type of files are going to be backed up?
• How much intervention can you tolerate when restoring the data?
This slide shows three ways you can choose to back up an Oracle database:
1. The database is shut down completely, and the database files are backed up as
standard files in a file system. When the backup is complete, the database can be
restarted. Database shutdown must be automated through scheduling or scripting.
2. The Oracle Recovery Manager (RMAN) is used to automate the process of dumping
the database to files in the file system. NetBackup is scheduled to systematically
archive these files with a normal file system backup policy.
3. The NetBackup Agent for Oracle contains everything that is needed to successfully
back up and restore an Oracle database by using APIs to control RMAN and back up
the database on NetBackup’s schedule, without affecting database downtime. This
method requires additional NetBackup licensing.
A-7
Database backup types
bpbkar-based Stream-based Intelligent
• Exchange • Oracle • Oracle

• SharePoint • Sybase • SQL Server
• Lotus Domino • Informix
• Enterprise Vault • DB2
• SQL Server
Database backups are divided into three types: bpbkar-based and script-based.
Some examples of bpbkar-based database backups are Exchange, SharePoint, Lotus
Domino, and Enterprise Vault. The backup process flow for bpbkar-based database
backups is similar to other standard file system backups.
Script-based backups can be split into two different types, stream based and Intelligent
Policy. Both types use a script. Stream based use a script that is written using the
database backup and restore utilities. Examples of script-based database backups are
Oracle, Sybase, Informix, DB2, and SQL Server.
Intelligent policies still use a script but the script is generated at run time using the data
that is entered in the NetBackup policy. Examples of intelligent policies are Oracle and
SQL Server.
The process flow for stream based and intelligent policy backups are significantly
different from the standard backup process flow.
A-8
How databases are backed up in NetBackup
bpbkar- Stream-
Schedule type Intelligent
based based
Frequency- or calendar-based *
• Backup initiated by NetBackup scheduler
• Most common types
User
• Backup initiated by user or application
• NetBackup restricts backup windows
• Application determines backup data
Application
• Variant of the User schedule
• Backup initiated by NetBackup as directed by Application
• Schedule determines backup retention
Automatic
• Backup initiated by database script on client, run by
NetBackup.
• This can be optional.
• Contains no backup data.
* Available schedules are Full, Incremental, and Logs 9
This slide compares and contrasts the schedules for bpbkar-based backups, script-based
backups and intelligent policies.
In general, bpbkar-based backups are scheduled as normal file system backups. They
can be controlled automatically with a frequency- or calendar-based schedule that
NetBackup initiates, or with a User Backup schedule that enables the client to initiate
the backup.
With script-based backups, an Application Backup schedule is created that enables the
application to initiate the backup. The backup is usually initiated when the application
runs a script that defines attributes of the backup.
Additionally, if you wish to configure NetBackup to control the schedule of these script-
based backups, use an Automatic Backup schedule that directs the application to run
the script, which then initiates the backup.
With intelligent policies, the schedule type can be Full, Incremental or be a special Logs
type for backing up Oracle Archive logs or SQL Server T-Logs.
The schedule initiates the backup and uses the same NetBackup schedule to store the
data removing the need for separate Application Schedules
A-9
Application backup-related features
Granular Recovery Technology (GRT)

•Enables individual object restores from one-pass full backups
•Supported with Microsoft Exchange, SharePoint, and Active Directory
Block-level incremental backups (BLIB)

•Used mainly for VMWare backups.
•Enables NetBackup to back up only changed data blocks.
•Extremely efficient for large files that have few changes.
•For Oracle backups, uses VxFS Storage Checkpoint technology to significantly
reduce time, CPU, and network overhead, but does not use RMAN.
10

Granular Recovery Technology (GRT) enables the ability to restore individual objects,
such as mailbox and public folder items in Exchange, from full database backups.
Block-level incremental backups (BLIB)
The block-level incremental backup interface extends the capabilities of NetBackup to
back up only changed data blocks.
Block level incremental backups are used mainly for VMWare backups. This allows
incremental backups to use the VMware Change Block Tracking , via the vStorage API, to
make the incremental backup fast as only changed blocks are backed up. Used in
conjunction with NetBackup Accelerator, this can create full backups from the block
level incremental backup.
Oracle has integration with VxFS Storage Checkpoint to enable changed block
identification in real time. BLI backup does not need to search the entire database for
the modified blocks, which saves time, decreases the amount of backup media that is
required, and significantly reduces CPU and network overhead during backups.
BLIB backups for Oracle are not widely used nowadays as there is no integration into
RMAN.
A-10
Topic: Introduction to database backups
After completing this topic, you will be able to discuss database backup and
restore concepts.
11
After completing this topic, you will be able to discuss options for backing up and
restoring Oracle and MS-SQL and how transactions logs can be affected.
A-11
Database overview
• A database is an organized collection of data.

• A database system implies that the data is managed to some level of quality, measured
in terms of accuracy, availability, usability, and resilience.
• A database management system (DBMS) is software that controls the creation,
maintenance, and use of a database
• Well known DBMSs include:
– Oracle
– Microsoft SQL Server
– Sybase
– IBM DB2
– Others such as Microsoft Access, PostgreSQL, MySQL, and SQLite
12
Definitions for a database, database system, and database management system (DBMS)
are provided on the slide.
Some well-known DBMSs are also listed.
Some basic database backup and restore concepts are discussed on the following slides.
A-12
Database failures and resiliency
Failures can be caused by: Resiliency is provided with:

• A process accessing the database incorrectly • Database transaction or redo logs
• A network disconnection • Storage redundancy and mirroring
• A system crash • Snapshot technologies
• Syntax errors in a complex database SQL • Data backups
statement • Replication to offsite storage
• A logical error caused either by a user entering
invalid data
or by an application error
• A disk failure or other external error that causes NetBackup can manage
data loss backups to, and restores
from, many of these data
resiliency methods.
13
Database failures can be caused by a number of physical and logical problems. A

sampling of these is listed in the left side of the slide.
Recovering from these failures is achieved using a number of different strategies, such
as:
• Database transaction logs
• Database redo logs
• Storage redundancy and mirroring
• Snapshot technologies
• Data backups
• Replication
Each of these strategies can protect against some of the failure types. Each of them also
provides advantages and disadvantages, such as backup performance, restore
performance, and the minimization of database downtime. None of these methods
protects against all types of failures, and it is only with a comprehensive strategy that
takes into account all of these methods, that you are best equipped to handle a disaster.
NetBackup provides the advantage of not only managing data backups, but also being
able to initiate restores within the application to take advantage of transaction and redo
logs, snapshots, and some replication features.
A-13
Determining your backup strategy
• Physical or logical data backups?

• Hot (online) or cold (offline) backups?
• Back up the database, tablespace, or individual datafile?
• Full backups only, or full and incremental backups?
• Storage destination
– Tape
– Disk
– Deduplication
• Physical destination
– Duplication
– Offsite media storage
– Replication
14
You have numerous options and choices when backing up a database:

• Physical or logical data backups
One of the first choices you must make is how to execute the backup process. How
you choose to back up your database influences other choices later in the process.
The most common backup method is a physical backup of a database. This method
creates a mirror image of the database that is complete in detail down to the
physical location of the data blocks. You can occasionally perform a logical backup,
which exports a snapshot of the data from the database but does not record the
physical structure of the database.
• Cold (offline) backups
A consistent backup is commonly referred to as a cold backup because the database
must be shut down (offline) while the backup is performed. With a cold backup,
recovery actions are not needed to restart the database after a restore.
• Hot (online) backups
An inconsistent backup is commonly referred to as a hot backup because the
database is open and operational (online) while the backup is performed.
The database must maintain an updated record of transactions that occur while the
backup is performed. With a hot backup, recovery actions are necessary before you
can restart the database after a restore, which usually involve using the previously
recorded set of transactions to assist in recovering the data to a consistent state.
A-14
• Databases and partial backups
Other factors to consider when performing physical backups are database size and
tablespace traffic. Complete database backups take longer and require large
amounts of storage space. If you structure your database so that only certain data
files or tablespaces are modified regularly, you can save time and storage space by
backing up only the elements that change.
When you perform a database backup, all constituent files of the database are
backed up as a coherent whole.
An individual tablespace can be backed up independent of the remainder of the
database. Because tablespaces can consist of multiple data files, backing up
tablespaces is more common than backing up individual data files. Backing up a
tablespace is generally an online backup.
As with a tablespace backup, individual data files can be backed up independent of
the remainder of the database. If a tablespace consists of only one file, this is
identical to a tablespace backup. Otherwise, the effect is to back up only a portion
of a tablespace. Backing up a data file is generally an online backup.
• Full and incremental backups
Running full backups can be prohibitive when the data set is very large. Use
incremental backups that take advantage of database transaction logs to shorten
the backup window and automate database log maintenance. Additionally, Oracle
supports block level incremental (BLI) backups to provide increased performance
and reduced resource usage.
• Backup storage destination
One of the key advantages of having NetBackup manage the database backups is
that they can be sent to any of the storage methods supported by NetBackup,
including tape-based, disk-based, or deduplication-based storage.
• Physical destination
Another advantage of using NetBackup is the range of physical destinations and
strategies that are supported, including automated duplication to any supported
storage destination, automation and management of offsite media storage, and
various replication features and technologies.
NetBackup agents optimize the performance of critical databases and applications by
providing the ability to use all of these backup strategies and technologies.
A-15
Database backup using an Application schedule
• Policy for database Database 3

NetBackup
– Application schedule
1
2
1 The database attempts to initiate a backup using a backup script.
2 NetBackup uses the Application schedule to ensure there is an open window

and then build the backup job.
3 The database backup job runs when resources are available.
16
The graphic on this slide describes the process for backing up a database using an (BLIB)
schedule.
In this procedure:
1. The database attempts to initiate a backup with the master server by using a backup
script.
2. NetBackup uses the Application schedule to ensure there is an open window in
which to run the database backup, and then build the backup job.
3. The database backup job runs when the resources become available.
A-16
Database backup using an Automatic schedule
• Policy for database Database 4

NetBackup
– Application schedule
1
– Automatic schedule
2
3
1 NetBackup runs an Automatic schedule to initiate the backup script.
2 The database attempts to initiate a backup using the backup script.
3 NetBackup uses the Application schedule to ensure there is an open window

and then build the backup job.
4 The database backup job runs when resources are available.
17
The graphic on this slide describes the process for backing up a database using an
Automatic schedule.
In this procedure:
1. NetBackup runs an Automatic schedule to initiate the backup script.
2. The database attempts to initiate a backup with the master server using a backup
script.
3. NetBackup uses the Application schedule to ensure there is an open window in
which to run the database backup, and then build the backup job.
4. The database backup job runs when the resources become available.
A-17
Topic: Introduction to enterprise application backups
After completing this topic, you will be able to discuss options for backing
up and restoring Exchange, Active Directory, SharePoint, and Enterprise
Vault.
18
After completing this topic, you will be able to discuss options for backing up and
restoring Exchange, Active Directory, SharePoint, and Enterprise Vault.
A-18
Database backups for Microsoft Exchange Server
• NetBackup for Microsoft Exchange:

– Enables non-disruptive mechanisms to protect
Exchange data
– Provides the performance and flexibility required
for effective backup and recovery operations
within large Exchange-based environments
• Features and benefits:
– Online backups: Complete, non-disruptive protection of the Exchange database and mailbox
components, including mailbox-level backup
– Flexible restore options: Rapid, granular recovery of databases and mailboxes, including support for
performing individual message restores
– Eliminate MAPI backups: Enable granular recovery of the full application and a single email with only
one backup pass and one copy stored
– One-pass GRT-enabled backups of Exchange running in VMware
19
NetBackup for Microsoft Exchange Server extends the capabilities of NetBackup to

include online backups and restores of Exchange databases when Exchange Server is
installed. Some key advantages to using the NetBackup agent for Microsoft Exchange
include:
• Exchange Server data and transaction logs can be backed up without taking the
Exchange Server offline. Exchange services and data remain available.
• Exchange Server backups can be saved directly to a wide variety of storage devices
that the NetBackup master server supports.
• NetBackup supports all Exchange Server backup methods, including full, cumulative
incremental, and differential incremental backups.
• From one-pass backups of Exchange, Granular Restore Technology (GRT) can be used
to create consistent full backups, as well as restore Exchange storage groups or
databases and individual database objects. This backup takes much less time than
prior MAPI-based (brick-level) backups.
• From a one-pass backup of a virtual machine running Exchange, a GRT-enabled
backup can be created for full restore or granular restore ability.
• NetBackup for Exchange supports backups of Exchange 2010 stand-alone servers
and Exchange 2010 Database Availability Groups (DAGs).
A-19
• NetBackup can back up and restore storage groups and databases within the storage
group.
• For snapshot backups, NetBackup uses the Microsoft consistency check API to check
the consistency of databases and transaction logs and to provide additional details.
This speeds up a snapshot backup because it allows the backup to proceed in
parallel with the consistency check.
• NetBackup for Exchange can perform backups and restores of Exchange objects with
snapshot methodology. With a separate Snapshot Client license, you can perform
off-host backups, Instant Recovery backups, and backups with a hardware provider.
• Exchange 2007 and later backups can be restored to another database or another
storage group on the local server or on a different server. Exchange 2003 snapshot
backups can be restored to an identical storage group on a different server.
• Exchange 2007 and later backups can be redirected to the recovery database or
recovery storage group (RSG). Streaming backups of Exchange 2003 can be
redirected to the RSG.
• The NetBackup for Exchange Server agent supports Microsoft Cluster Server (MSCS)
environment and Veritas Cluster Server (VCS).
For additional details, see the NetBackup for Microsoft Exchange Server Administrator’s
Guide.
A-20
Enterprise agent example: Microsoft Exchange
21
This is an example of an enterprise agent for NetBackup. Enterprise agents use special
directives in the Backup Selections list to define what is protected. In this example,
Microsoft Exchange is being protected. The NetBackup administrator added a user
backup schedule in addition to an automatic full backup. Note that having a user backup
schedule is not mandatory to protect Microsoft Exchange, but it does provide increased
flexibility.
A-21
Database backups for Microsoft SharePoint Server
• NetBackup for Microsoft SharePoint:

– Extends the capabilities of NetBackup to include
online backups and restores SharePoint Server
– Provides the ability to back up SharePoint
Server online, without disruption of services.

– Easy to use: One console can be used to protect SharePoint
and Windows services; includes server farm configuration
and single sign-on for databases
– Granular recovery: Save time and storage by recovering SharePoint files, including different versions of a
file, sites, sub-sites, and lists such as calendars and links
– One-pass GRT-enabled backups of SharePoint running in VMware
22
NetBackup for SharePoint extends the capabilities of NetBackup to include online

backups and restores of a SharePoint server. The NetBackup agent for Microsoft
SharePoint Server is an optional, add-on component to the NetBackup for Windows
client software. Some key advantages include:
• SharePoint Server objects can be backed up without taking the SharePoint Server
offline. SharePoint services and data are available during the backup.
• NetBackup supports full and differential-incremental backups of SharePoint.
• NetBackup for SharePoint supports the backup and recovery of multiple SharePoint
Server installations from a central location.
• Auto discovery is used where the topology is read from the SharePoint front-end
Web server and the backup selections list is automatically built.
• A user can perform backups of SharePoint Server resources through the Backup,
Archive, and Restore client interface on the front-end Web server.
• VMware backups that protect SharePoint Server provide granular recovery,
complete protection of the farm, and protection of the components in the files
system.
For additional details, see the NetBackup for Microsoft SharePoint Server
A-22
Database backups for Microsoft Active Directory
• NetBackup provides comprehensive protection

of Microsoft Active Directory, which is integral
in managing network services.

– Recover any Active Directory item: Granular recovery including the ability to recover all items with full
attributes, such as users, servers, and printers, to satisfy both daily and disaster recovery (DR)
requirements with one backup image
– Eliminate Active Directory server reboot: Minimize downtime and keep the application up and running
– Ease of use and control: Leverage Microsoft VSS system state backup for ease of use and control
23
Active Directory (AD) is a directory service created by Microsoft for Windows domain
networks. Active Directory serves as a central location for network administration and
security. It is responsible for authenticating and authorizing all users and computers
within a network of Windows domain type. Administrators can use Active Directory for
assigning and enforcing security policies for all computers in a network, and for
installing or updating software on network computers. Server computers with Active
Directory running are called domain controllers.
NetBackup can be used to restore individual objects and attributes in the Active
Directory, instead of restoring the entire Active Directory. Administrators can also
restore deleted objects, known as tombstone objects, from the Active Directory.
Active Directory granular NetBackup restores are supported on Windows 2003 R2 SP2,
Windows 2008, Windows 2008 R2, and more. Check the NetBackup documentation to
find out which version of Windows support Active Directory granular restores.
A-23
• Enables individual object restores from one-pass full backups

• Supports Microsoft Exchange, SharePoint, and Active Directory.
• Provides both the entire storage group / database restore, or individual object restores
such as mailbox folders or items in Exchange
24
Granular Recovery Technology (GRT) enables the ability to restore individual objects,
such as mailbox and public folder items in Exchange, from full database backups.
This type of backup can serve both kinds of recovery situations. From the same backup
image, you can restore entire storage groups or databases, or you can select individual
objects within that backup. This backup replaces the existing MAPI mailbox backup,
sometimes referred to as a brick-level backup, which took a significant amount of time
with Microsoft Exchange.
You can restore individual items using GRT from the following types of backups:
• Full or user-directed backups (Incremental backups are not yet supported.)
• Local snapshot backups
• Off-host snapshot backups
• Instant recovery backups, when the schedule copies the snapshot to a storage unit
• Replica snapshot backups
• Streaming backups (Exchange 2007 and earlier)
A-24
Database backups for Veritas Enterprise Vault
• NetBackup automates the protection and

recovery of Enterprise Vault environments.
• Features and benefits

– Simplified protection: Automatically discover Enterprise Vault servers and components that need
protection, including partitions and their associated databases
– Leverage snapshot technology: The backup of the snapshot is done quickly and efficiently, eliminating
the need for manual scripts or the manipulation of registry settings
– Effective disaster recovery: Centrally manage the disaster recovery process of the Enterprise Vault
partitions and databases
25
Veritas Enterprise Vault enables an organization to store messaging and file system data
automatically in centrally-held archives. Clients and users can retrieve selected items
easily and quickly when required.
Enterprise Vault can archive any of the following types of data:
• Items in Microsoft Exchange user and journal mailboxes
• Items in Domino mail files and journal databases
• Files held on network file servers
• Documents held on Microsoft SharePoint servers
• Instant Messages, Bloomberg messages, and SMTP messages
The NetBackup Enterprise Vault agent consists of the components that enable you to
protect the Enterprise Vault configuration and archived data.
The Enterprise Vault agent enables you to back up and restore the Enterprise Vault file
system data and the Enterprise Vault SQL data. These types of data can reside on
different systems or devices, such as NTFS or NAS devices.
The Enterprise Vault agent also serves as a disaster recovery solution for data that is
archived using Enterprise Vault. Recovery of the archived data is not dependent on the
archive source, such as Exchange Server or a specific file system.
A-25
Lesson summary
• Key points
– You learned how to discuss the types of application backups and you can describe the features of GRT
and BLIB.
– You also learned to discuss general options for backing up and restoring databases.
– Finally, you learned the advantages for backing up and restoring Exchange, Active Directory, SharePoint,
and Enterprise Vault using NetBackup agents.
– NetBackup for Microsoft Exchange Server Administrator’s Guide
– NetBackup for Microsoft SharePoint Server Administrator’s Guide
26
A-26
What did you learn?
lesson.
27
current lesson.
A-27
Question: About block level incremental backups (BLIB)
Which of the following statements about block level incremental backups (BLIB) is
correct?
A. They can speed up backups of Exchange servers.

B. They can speed up backups of Oracle databases.
C. They enable restore of individual objects for Exchange.
D. They enable restore of individual objects for Oracle.
28
A-28
Answer: About block level incremental backups (BLIB)
Which of the following statements about block level incremental backups (BLIB) is
correct?
A. They can speed up backups of Exchange servers.

B. They can speed up backups of Oracle databases.
C. They enable restore of individual objects for Exchange.
D. They enable restore of individual objects for Oracle.
The correct answer is B. Block level incremental backups (BLIB) backs up changed data for Oracle. This method does not
apply to Exchange
29
A-29
Question: Backup Selections list for an Oracle backup policy
What is in the Backup Selections list for an Oracle backup policy?
A. The device names or drive letters of the disks

B. The file names of the transaction logs
C. The file names of all files used by Oracle
D. A script to be interpreted by Oracle
30
A-30
Answer: Backup Selections list for an Oracle backup policy
What is in the Backup Selections list for an Oracle backup policy?
A. The device names or drive letters of the disks

B. The file names of the transaction logs
C. The file names of all files used by Oracle
D. A script to be interpreted by Oracle
The correct answer is D. This technique is also common to other databases, such as Microsoft SQL Server.
31
A-31
Question: Microsoft Exchange backups
Which statement about Microsoft Exchange backups is true in NetBackup?
A. Exchange must be shut down to be backed up consistently.

B. The entire Exchange database must be restored as a whole.
C. Individual Exchange mailboxes can be restored, but not individual messages.
D. Individual mail messages can be restored.
32
A-32
Answer: Microsoft Exchange backups
Which statement about Microsoft Exchange backups is true in NetBackup?
A. Exchange must be shut down to be backed up consistently.

B. The entire Exchange database must be restored as a whole.
C. Individual Exchange mailboxes can be restored, but not individual messages.
D. Individual mail messages can be restored.
The correct answer is D. Granular Recovery Technology provides this functionality for Exchange.
33
A-33
End of presentation
A-34
Appendix B: Protecting and Recovering Hyper-V Virtual

Machines
This is the “Protecting and Recovering Hyper-V Virtual Machines” appendix in the
“Veritas NetBackup 8.1: Administration” course.
B-1
Lesson objectives
Topic Objective
Introduction to virtual machine Describe virtual machines and discuss support for virtual machines
backups in Hyper-V.
Configuring Hyper-V backups Configure NetBackup to protect Hyper-V virtual machines.
Performing and Monitoring Hyper-V Perform and monitor Hyper-V backups

backups
Performing Hyper-V restores Perform Hyper-V restores.
Performing Hyper-V restores with Perform Hyper-V restores with the NetBackup Add-in for SCVMM.
the NetBackup Add-in for SCVMM
B-2
Topic: Introduction to virtual machine backups
After completing this topic, you will be able to describe virtual machines
and discuss support for virtual machines in Hyper-V.
After completing this topic, you will be able to describe virtual machines and discuss
support for virtual machines in Hyper-V.
B-3
Machine virtualization overview
• Using virtualization, a host server performs the job of multiple computers sharing the
physical host’s resources.
• Each virtual machine (VM):
– Runs its own operating system and applications
– Is encapsulated and isolated from other VMs
– Uses its own emulated resources (such as CPU,
disks, and network connection)
• The virtualization layer, or hypervisor, is software that enables virtual machines to use
the host’s physical resources.
• The hardware layer consists of the physical components of the host server, and is shared
across the running virtual machines.
• Review Article 000006177: Support for NetBackup in virtual environments
Virtual machines, sometimes referred to as VMs, enable the sharing of the underlying
physical machine resources between virtual machines, each running its own operating
system. The software layer providing the virtualization is called a virtual machine
monitor or hypervisor. A hypervisor can run on bare hardware (native VM) or on top of
an operating system (hosted VM). An example of a hypervisor running on bare hardware
is VMware ESX Server. An example of a hypervisor running on top of an operating
system is VMware Server and Workstation. In the case of Microsoft Hyper-V, the
hypervisor runs on a special version of the Windows operating system.
NetBackup support for virtual machines
VMs consist of a number of files, including the critical virtual hard disk file (VMDK in
VMware, and VHD or VHDX in Hyper-V), which contains the operating system and data
for that VM. Traditionally, backing up the virtual hard disk file enables you to easily
restore the VM but does not provide the ability to perform individual file restores.
Conversely, backing up files from the VM as a normal client prevents easily restoring the
full virtual hard drives in the case of disaster recovery. NetBackup provides the ability to
easily back up and restore the virtual hard disk, while alternatively allowing for granular,
individual file restore.
Review support details in Article 000006177: Support for NetBackup in virtual
environments, found online at http://www.veritas.com/docs/000006177.
B-4
How Virtualization Works
Operating Operating Operating

system system system
Operating system Hypervisor
Hypervisor Control
Application
Instructions Instructions
Privileged instructions Privileged instructions
Processor memory management Processor memory management
Protected Protected Protected
Protected memory memory
memory memory
Network NIC NIC NIC
Network
Storage storage storage storage
Storage
Physical machine stack Virtual machine stack
5
Modern CPUs have features built in for system protection. These protections keep
different programs from writing into each others’ memory regions. CPUs also have
privileged instructions: Instructions only executable by the operating system.
The structure of virtualization is to allow multiple operating systems to run on the same
set of CPUs. In order to allow multiple operating systems to run, the virtualization
mechanism has to properly handle privileged instruction execution.
There are different methods virtualization systems use to handle privileged instructions.
VMware and Hyper-V use virtualization features of the CPU: Intel VT and AMD-V. The
hypervisor signals the CPU that certain processes are virtual machines, and allows the
privileged instruction to execute. Prior to this CPU technology, the hypervisor
intercepted privileged calls and executed software to manage access to the privileged
instructions. This virtualization technology model is more efficient and reliable.
Citrix XenServer uses para-virtualization: the operating system is modified to
accommodate the privileged instruction execution.
The hypervisor virtualizes networks, network switching, interrupts, and disk storage.
A hypervisor control application manages and monitors the creation, operation, and
lifecycle of virtual machines. Often, this control application runs on a separate host, to
remotely and centrally manage the virtualization servers.
B-5
Supported NetBackup virtual machine backup solutions
VM backup; Single-pass Single-pass

Virtual machine File system NetBackup
Intelligent backup; file and integrated
technology backup Accelerator
policy full VM restore application backup*
VMware vSphere ✓ ✓ ✓ ✓ ✓
Microsoft Hyper-V ✓ ✓ ✓ ✓
RedHat Enterprise
Virtualization ✓
Solaris zones ✓
Oracle Solaris
virtualization ✓
* Supported for Microsoft SQL, Exchange, and SharePoint 6
NetBackup supports a number of host virtualization solutions.

VMware and Microsoft Hyper-V are two of the most feature rich host virtualization
platforms in the market, and NetBackup is highly integrated with these solutions. As
well as supporting backup and recovery for both files and full virtual machines,
NetBackup also supports single-pass backups of virtual machines that support individual
file restore as well. These platforms are also supported with dedicated policy types
(VMware and Hyper-V) that provide virtualization specific features and options.
Additionally, NetBackup Accelerator is supported for both VMware and Hyper-V for
faster backups using block change tracking features.
Although NetBackup also supports other virtualization platforms, such as RedHat
Enterprise Virtualization (RHEV), Citrix XenServer, Solaris zones, and Oracle Solaris
virtualization, the feature sets are more similar to standard backup policies. Technical
articles and best practices exist for these virtualization solutions.
B-6
Understanding the virtual data center implementation
NetBackup infrastructure Virtualization infrastructure

Master Media servers VM server VM server
server
Hypervisor
control system
SAN
Control API
CLI
Web Interface
Storage
Cloud
orchestration
Virtualization
Web Client
The degree of virtualization, virtualization controls, and management varies widely

across enterprises. NetBackup includes features that are flexible in order to
accommodate most implementations.
The solutions for VMware and Hyper-V leverage features built into the hypervisor
control layer. For VMware environments, NetBackup uses the VMware API for data
protection. For Hyper-V environments, NetBackup uses Windows Management
Instrumentation for Windows Server 2016, and a host of provided features.
Veritas uses the capabilities provided by the hypervisor supplier to develop VM-specific
backup solutions. There are limitations and requirements, based on the software and
the environment. For example, in some cases the guest (VM) operating system may
need to have the NetBackup client installed to allow for advanced backup and recovery
features, such as one-pass VMware backups that simultaneously allow for granular
application recovery.
The specific architecture used in a virtual environment should be well understood.
Veritas solutions support a subset of many varieties of virtualization storage and guest
operating system architectures. Be sure to examine and evaluate the support and
limitations of both the virtualization vendor and the Veritas NetBackup solution in
designing your backup strategy for virtual environments.
B-7
Overview of NetBackup support for VMware vSphere and
Microsoft Hyper-V
Feature VMware vSphere Microsoft Hyper-V
Single-pass backups with full VM or file-level restore Yes Yes
Intelligent Policy with VM query builder VMware policy type Hyper-V policy type
Block-level incremental backups Using CBT Using WMI

NetBackup Accelerator backups Starting in NetBackup 7.7 Starting in NetBackup 8.0
Allows Instant Recovery Yes No

Uses snapshot for consistency and to keep VMs fully
Yes Yes
available
Back up VMs that are powered off Yes Yes
Web client integration support vSphere Web client SCVMM

Supported with prerequisite
Off-host backups of VMs Supported with VADP
steps
NetBackup support for VMware vSphere and Microsoft Hyper-V are summarized in the
table on the slide.
Both products are supported with full VM recovery, or individual file and folder level
restores, from single-pass backups performed by NetBackup. Both VMware and Hyper-
V policy types exist, that include automatic VM selection using a query builder, as well
as simplification of VM-specific backup configuration. Settings exist to limit and control
backup impact on the environment, to ensure performance is not adversely affected.
Full and incremental backups are supported, including block-level incremental backups
(BLIB) that avoid backing up unused space. BLIB is supported with VMware Change
Block Tracking (CBT) and Hyper-V Windows Management Instrumentation (WMI).
NetBackup for VMware also supported application-aware single-pass backups for
granular recovery of Microsoft Exchange, and SharePoint, and provide log truncation for
Microsoft SQL and Exchange. NetBackup for VMware also supports instant virtual
machine recovery, which is discussed in more detail in the Performing Virtual Machine
Restores lesson.
Off-host backups of VMs are supported in VMware using VMware vSphere Storage APIs
– Data Protection (VADP), reducing processing load on the VM server, and preventing
the need to install a NetBackup client on the VMs. Hyper-V also supports some off-host
/ alternate client backups, but requires some additional configuration steps, as provided
in the documentation.
Centralized management and web consoles are supported, which include VMware
vSphere web client, vCenter servers, and the Hyper-V System Center Virtual Machine
Manager (SCVMM).
B-8
Topic: Configuring Hyper-V Backups
After completing this topic, you will be able to configure NetBackup to

protect Hyper-V virtual machines.
After completing this topic, you will be able to configure NetBackup to protect Hyper-V
virtual machines.
B-9
Example NetBackup for Hyper-V environment: Media servers and
Hyper-V servers
Master Media Hyper-V
server server servers
LAN
SAN
Virtual machines
Each Hyper-V server requires
one NetBackup client.
10
This slide shows a NetBackup for Hyper-V environment.

To use the NetBackup Hyper-V policy type, a NetBackup 7.5 or later client must exist on
each Hyper-V server.
For the optional off-host backup approach, a NetBackup client must be installed on the
alternate client.
Note: In most cases, the NetBackup client does not need to be installed on any virtual
machine. For exceptions, see the Veritas NetBackup for Hyper-V Administrator’s Guide.
B-10
Example NetBackup for Hyper-V environment: Hyper-V servers as
SAN media servers
Media and
Master Hyper-V
server server LAN
SAN
Configuring the Hyper-V server

as a SAN Media Server allows a
LAN-free backup
11
This slide shows an optimized NetBackup for Hyper-V environment.

Installing the Media Server software instead of the client software on the Hyper-V
server allows it to send backup data directly to tapes or disk storage units across the
SAN.
B-11
Example NetBackup for Hyper-V environment: Hyper-V servers as
SAN clients
Master Hyper-V
server server LAN
SAN
Configuring the Hyper-V server as a

SAN client reduces the NetBackup
footprint and allows a LAN-free
backup
12
This slide shows an optimized NetBackup for Hyper-V environment.

In this example we are using the SAN Client feature to send data across the SAN to a
NetBackup media server (in this example, a NetBackup appliance). SAN client provides
the same benefit that SAN Media server does, but with a reduced footprint on the
Hyper-V server. SAN client and SAN media Server are both available with the Enterprise
Client license, which Hyper-V requires anyway.
B-12
Comparing VSS and WMI
• Default framework for VM backup/restore prior to Hyper-V 2016.

• Impacts scalability and availability due to limitations:
‒ Creates snapshot of entire storage volume where VM resides.
Volume Shadow Copy ‒ Must be serialized.
Service (VSS) ‒ Consists of many components (VSS framework, Hyper-V VSS writer, 3rd party VSS
providers).
‒ Requires Linux VMs or VMs without integration services to be put in saved state
(offline backup).
• Addresses the limitations of VSS for VMs.

Windows Management • Introduced for Hyper-V 2016 and later.
Instrumentation (WMI)
• Supported by NetBackup 8.0 and later.
13
Backing up and restoring virtual machines, much like other live data, requires a method
for ensuring data consistency. The original Microsoft solution was to use Volume
Shadow Copy Service (VSS) technology for Hyper-V VM backups and restores
VSS-based backups of VMs has the following limitations, which affect scalability,
reliability, and availability:
• Creates a snapshot of the entire storage volume on which the VM resides.
• Requires serialized snapshots due to limitations in VSS framework.
• Consists of many separate components, such as the VSS framework, Hyper-V VSS
writer, and third-party VSS providers, impacting the reliability of the overall solution.
• Requires Linux VMs or VMs without integration services to be put in saved state
during the backup, to ensure consistency, causing downtime.
The new WMI-based backup method, introduced by Microsoft in Hyper-V 2016 and
later, addresses all the above limitations, as well as provides additional feature support.
For example, change block tracking allows for the use of features such as NetBackup
Accelerator.
Note that the VSS backup method is not deprecated. Users of NetBackup 8.0 and later
can select either VSS or WMI as the backup method while configuring the Hyper-V
policies for Hyper-V 2016. It is highly recommended to use the WMI method for better
scalability and reliability.
B-13
NetBackup for Hyper-V components
Component Description
Virtual machine • Sometimes referred to as a VM
• Configured as a NetBackup client in the NetBackup policy
• Does not require the NetBackup client being installed
• Requires the NetBackup client when restoring individual files to a VM, or when using
Hyper-V pass-through disks
Hyper-V server • A Windows hypervisor-based virtualization system which hosts the VM guests
• Must have the NetBackup client installed
Hyper-V integration • Provides integration between the Hyper-V server and the VMs
services • Hyper-V servers must have Hyper-V backup integration services enabled
SCVMM • System Center Virtual Machine Manager
• Centralizes management for the Hyper-V virtualized datacenter
Media server • Reads and writes backup data
• For efficiency, should be installed on the Hyper-V server
NetBackup client • Installed on the Hyper-V server
• Generally not required in the virtual machine
14
This slide lists Hyper-V components and components used by NetBackup when backing
up Hyper-V.
B-14
Configuring Hyper-V backups
NetBackup configuration
Install
Create a
NetBackup
Add Enterprise Set Resource NetBackup
client or Media
Client license Limits policy for
Server on
Hyper-V
Hyper-V server
15
The general NetBackup for Hyper-V configuration steps include:

1. Installing the NetBackup master and media servers and environment
2. Adding the Enterprise Client license
3. Installing the NetBackup client or media server software on the Hyper-V servers
4. Setting Resource Limits in the Master Server Host Properties
5. Creating NetBackup policies for Hyper-V virtual machines
Configuring Hyper-V backups is covered in detail in the Veritas NetBackup for Hyper-V
Administrator’s Guide. See the documentation for detailed steps, notes, and limitations.
B-15
Understanding Hyper-V intelligent policies
What is a Hyper-V Intelligent Policy?
• Automatically protects VMs, using rules

• Dynamically protects newly created or moved/removed VMs
• Filter VMs on various attributes (VM name, Display name, Guest OS)
• Protects Hyper-V VMs managed by standalone Hyper-V Server or Windows Failover Cluster
• Ability to set resources limits for backup jobs to control system load and performance
What is required for Hyper-V Intelligent Policies?
• NetBackup 7.7 or later client on the Discovery Host

• Hyper-V host running Windows 2012 and later for discovery
• .NET 3.5 runtime on the Hyper-V Discovery host
• LogOn property must be set for the NetBackup Legacy Network Service to perform Hyper-V
server queries
16
Hyper-V intelligent policy in NetBackup 8.0 introduce new features, such as the query
capability, for selecting VMs based on a combination of attributes, rather than simply
the VM name. The VM browse capability available in prior versions is also available.
In order to optimize both application service and backup and recovery needs, intelligent
policies allow you to limit Hyper-V resources for use in backup jobs.
Additionally, these policy improves the backup administrator’s efficiency and
effectiveness., reducing the detailed analysis and tracking that are required if VM
backups are managed by browsing and manual selection. The Hyper-V intelligent policy
enables backup administrators, managers, and other stakeholders to focus on higher
level issues: recovery point objectives (RPO), recovery time objectives (RTO), and policy
coverage.
The requirements, installation and operation of the Hyper-V intelligent policy include a
supported operating system on the Discovery Host, and a .NET 3.5 runtime on the
Discovery Host.
Additionally, in order for the Hyper-V intelligent policy to function properly, the
NetBackup Legacy Network Service makes requests of the Hyper-V server. Valid logon
credentials needs to be delivered to the Hyper-V server. To modify credentials, the
NetBackup Legacy Network Service is accessed through the Services interface. Proper
logon credentials are supplied in the LogOn tab permitting query operations.
B-16
NetBackup configuration: Set resource limits
• Helps avoid serious performance issues

• Refer to NetBackup for Hyper-V Administrator’s Guide
17
Veritas highly recommends setting limits on the use of Hyper-V resources to prevent
serious performance issues on your virtual servers.
Set limits by navigating to the Resource Limit tab of the master server’s Host
Properties. Select Hyper-V in the Application column. Click in the Resource Limit
column to set the maximum NetBackup usage for the resource type. The settings apply
to all Hyper-V policies that use a Hyper-V Intelligent Policy query to select clients.
The default for all resource limits, indicated in the NetBackup Administration Console by
a blank value in the Resource Limit column, is unlimited. The screen shot shows a
maximum of four simultaneous active snapshots per Hyper-V server at a given time.
For details on resource limit types and behavior, see the NetBackup for Hyper-V
Note that you may want to adjust or tune the resource limits according to the transport
mode you select.
B-17
NetBackup configuration: Create a Hyper-V policy
Use the
Hyper-V
policy type
18
To create a backup policy, use either the Policy Configuration Wizard or the Policies
utility in the NetBackup Administration Console.
The Hyper-V policy type was introduced in NetBackup 7.5. When it is selected, a new
Hyper-V tab is displayed in the policy configuration dialog. This tab contains Hyper-V
specific parameters.
Note: Prior to NetBackup 7.5, the FlashBackup-Windows policy type was used to back
up virtual machines. In 7.7 and later FlashBackup policies may no longer be used to
protect Hyper-V.
To migrate FlashBackup-Windows policies that were created in prior versions to use the
Hyper-V policy type, see the nbplupgrade utility in the NetBackup Commands
Reference Guide.
B-18
Hyper-V policies: Attributes and schedules
Attributes Schedules
• Many options don’t apply • Supports full, differential, and cumulative
incrementals
• Supports full VM and file-level incrementals for all
schedules
Set Enable file recovery from VM backup on the Hyper-
V tab
• Use the Hyper-V tab to set Hyper-V related

options.
19
For Hyper-V type policies, many attributes found under the policy Attributes tab are
disabled. Most relevant Hyper-V specific options are found under the Hyper-V tab,
discussed elsewhere in this lesson.
Hyper-V policies support full, differential incremental, and cumulative incremental
schedules. If you are simply backing up the virtual machine disk (VHD/VHDX) files, these
schedules normally all back up the entire file. By setting the Enable file recovery from
VM backup option under the Hyper-V tab, NetBackup can recover the entire virtual
machine from these files, as well as perform individual file recovery. This ensures that
incremental backups only back up the changed files, while still providing the ability to
restore the entire virtual machine. Note that file level recovery is only available on
supported guest operating systems.
B-19
Hyper-V policies: Client Manual Selection
20
When assigning clients for a Hyper-V policy, you can select whether to select clients
manually or to have them automatically selected using a query that you construct.
To manually specify clients, navigate to the Clients tab, select Select Manually, and click
New. The Browse for Virtual Machines dialog box is displayed. Select Browse and
Select Virtual Machines to see a drop down hierarchy of virtual machines. Select the
virtual machine or machines you are interested in protecting.
Note that a policy where virtual machines are manually selected does not honor the
resource limits specified in the master server host properties.
B-20
Hyper-V policies: Client automatic selection
• Based on virtual machine attributes

• Can be combined to narrow results
Example queries:
• Back up all VMs in Power On state
• Back up all VMs where the display name starts with “Vmprod”
• Back up all VMs that are clustered
• Back up all VMs in Power On state in Hyper-V Server HyperV1
except where the Notes contain “QA”
21
Starting with NetBackup 7.7, Hyper-V policies allow for automatic virtual machine
selection. Queries are built around virtual machine attributes to determine which virtual
machines to back up. These queries can be combined with filters to create more
complex queries and limit the results.
If you want to use the new intelligent policy functionality instead of performing a
manual configuration, set the Virtual machine selection to Select automatically
through query. In this query builder, you build the virtual machine selection query. If
you do not select any query filters, the default behavior is to discover all virtual
machines, and back them all up.
The slide shows some examples of possible virtual machine selection queries. Some
examples show queries that use multiple query filters that are combined to narrow the
resulting virtual machines.
B-21
Hyper-V policies: Running a test query
nbdiscover –noxmloutput –policy LAB-HyperV

+ "hyperwinvm1"
- "emptyvm2" "VM has been excluded by the discovery filter, display name =
[emptryvm2], server = []."
22
When your query is formed, there is a Test Query button to execute and test the query.
After the test returns, the Test Query Results display every virtual machine found, and
identify whether the current filter value results in the virtual machine being included or
excluded. The slide highlights the results that were included, meaning that those virtual
machines matched the query, and would be backed up by this backup policy.
If the query is not working as desired in providing the correct virtual machines for the
policy, the query can be modified and retested.
In an environment with large numbers of virtual machines, a query can take many
minutes. During that duration, the console cannot be closed or used to monitor other
operations. A command line utility, nbdiscover (found in the NetBackup bin
directory) can be used to check the search terms of a query outside of using the
NetBackup console. This frees the console for monitoring and other work.
B-22
Hyper-V policies: Clients and Backup Selections list
23
When you use manual virtual machine selection, the Backup Selections list simply
shows ALL_LOCAL_DRIVES.
When you use automatic virtual machine selection, the virtual machine selection query
that was created is listed under the Backup Selections list, as shown in the slide:
hyperv:/?filter=Powerstate Equal poweredOff
In either circumstance, the policy backs up all local drives from each listed virtual
machine.
B-23
Hyper-V policy tab: Optimizations
24
Enable file recovery from VM backup

This option allows the restore of individual files from the backup. With or without this
option, you can restore the entire virtual machine.
Use this option for incremental backups (differential incremental backup or cumulative
incremental backup).
To perform a Hyper-V backup to a deduplication storage unit, select this option. This
option provides the best deduplication rates.
B-24
Hyper-V policy tab: Primary VM identifier
How NetBackup
identifies VM’s
25
This setting specifies the type of name by which NetBackup recognizes virtual
machines when it selects them for backup.
• VM Hostname: Specifies the network host name for the virtual machine. The host
name is available only when the virtual machine is running. If you select VM
hostname but the virtual machine is not running at the time of the backup, the
backup may fail.
• VM Display Name: Specifies the name of the virtual machine as it appears in the
Hyper-V Manager console.
Note: NetBackup for Hyper-V does not currently support the virtual machine display
names that contain non-US-ASCII characters. If the display name contains such
characters, select VM hostname or VM GUID.
• VM GUID: Specifies the unique ID assigned to the virtual machine when the virtual
machine was created.
Keep the following considerations in mind when making your selection:
• If you create a policy and then change the Primary VM identifier, you may have to
delete the virtual machine selections on the Clients tab. Otherwise, NetBackup may
no longer be able to identify the virtual machines to back up.
• When creating virtual machines, use the same name for both the host name and the
display name. If the Primary VM identifier is changed, the existing entries on the
Clients tab still work.
B-25
• For the policies that select virtual machines automatically: A space in a display name
is converted to "%20" in the test query results if the virtual machine is listed as
included.
• When selecting VM’s by Display Name: certain characters are not allowed in the
virtual machine display name by NetBackup. If the name contains the wrong
characters, the backup may fail. For NetBackup, the following characters are allowed
in virtual machine display names:
• Uppercase and lowercase ASCII characters
• Numbers
• Period (.)
Note however that a display name cannot end with a period.
• Hyphen (-)
• Underscore (_)
• Plus sign (+)
• Percent sign (%)
• Left and right parentheses ( ( and ) )
• Spaces
Note: No other characters are allowed.
B-26
Hyper-V policy tab: VSS and cluster settings
For guest OS that does not

support VSS (e.g. Linux) For Windows 2008 R2
Hyper-V servers only
27
Enable offline backup for non-VSS VMs

This option determines whether or not NetBackup is allowed to perform an offline
backup of a virtual machine. This option is intended for the guest operating systems that
do not support VSS (such as Linux).
Note: Online vs. offline backup are Microsoft backup types and are not configured in
NetBackup.
If this option is enabled, NetBackup can perform an offline backup of a virtual machine.
In certain situations, if the virtual machine cannot be quiesced for an online backup, the
virtual machine must be placed in the Saved state. The backup is thus performed offline.
User access to the virtual machine may be interrupted during the backup. After the
backup is completed, the virtual machine is returned to its original state. If this option is
disabled, NetBackup is not allowed to perform an offline backup of a virtual machine. If
an online backup cannot be done, the backup job fails with status 156
Cluster shared volumes timeout
For clusters on Windows server 2008 R2: This option applies to backups of the virtual
machines that are configured in a Microsoft Cluster that uses cluster shared volumes
(CSV). The timeout determines how long the backup job waits, in case another cluster
node backs up the same shared volume at the same time. A wait of 3 hours (the
default) is recommended if you have multiple virtual machines on one CSV.
B-27
Hyper-V policy tab: Advanced option
28
The Provider Type configuration parameter determines the type of VSS snapshot
provider that creates the snapshot:
• Auto: Attempts to select the available provider in this order: hardware, software,
system.
• System: Uses the Microsoft system provider, for a block-level copy on write
snapshot. Unlike the Hardware type, the System provider does not require any
specific hardware.
• Software: This option is not used in the current NetBackup release, but may provide
future functionality.
• Hardware: Uses the hardware provider for a disk array. A hardware provider
manages the VSS snapshot at the hardware level by working with a hardware
storage adapter or controller.
The Snapshot Attribute parameter determines the type of VSS snapshot that is created.
• Unspecified: Uses the default snapshot type of the VSS provider.
• Differential: Uses a copy-on-write type of snapshot. For example, to back up an EMC
CLARiiON array with an EMC CLARiiON SnapView Snapshot, select Differential.
• Plex: Uses a clone snapshot or mirror snapshot. For example, to back up an HP EVA
array with an HP EVA Snapclone snapshot, select Plex.
B-28
Sequence of Hyper-V Backup
Phase Description
Phase 1: NetBackup master server initiates the backup.
Initiate
Phase 2: NetBackup client on the Hyper-V server initiates a snapshot.
Snapshot
Phase 3: • VSS Hyper-V writer quiesces the Windows VM and creates the snapshot on the
Snapshot Execution host volume.
• If the Hyper-V writer cannot quiesce the VM, the VM is placed in the Saved
state before creation of the snapshot.
Phase 4: • NetBackup client reads the data from the snapshot of the VM and transfers the
Data Movement data to the media server.
• NetBackup media server writes the data to the NetBackup storage unit.
Phase 5: If the VM was placed in the Saved state, Hyper-V returns the virtual machine to its
State Restore original state.
29
The slide shows the sequence of events during a Hyper-V backup.
B-29
Topic: Performing and Monitoring Hyper-V backups
After completing this topic, you will be able to perform and monitor Hyper-
V backups.
30
After completing this topic, you will be able to perform and monitor Hyper-V backups.
B-30
Hyper-V backup example with client discovery
• The first parent job runs with the discovery host as Client and resolves virtual machines
with the query in the File list.
• Each virtual machine has a parent snapshot and child backup job.
31
When using automatic Hyper-V client selection, client discovery is required when the
backup runs.
An initial parent job runs the client discovery, showing the job’s client as the discovery
host, and the job’s file list as the query that is being used.
After this initial parent job, each virtual machine is displayed as a standard virtual
machine backup, which normally has an initial parent snapshot job and a child backup
job.
B-31
Limitations with Hyper-V Backups
Encryption • NTFS encryption/compression is supported.

and • NetBackup policy encryption/compression are not supported.
compression • Encryption/compression for Linux guest VMs are not supported.
SAN Client SAN Client feature must be installed on the Hyper-V server, not the VM.
NetBackup for Hyper-V does not support restores with the Fibre Transport data
SAN restores transfer method.
Linux file
Hyper-V provides no mechanism for quiescing file system activity on Linux virtual
system machine clients.
quiesce
32
Refer to the Veritas NetBackup for Hyper-V Administrator's Guide for complete
information on requirements, procedures, best practices and troubleshooting advice.
B-32
Topic: Performing Hyper-V restores
After completing this topic, you will be able to perform Hyper-V restores.
33
After completing this topic, you will be able to perform Hyper-V restores.
B-33
Initiating a Hyper-V restore
Identify virtual machine

using same identifier as
when backed up
Ignored for full

VM restores
34
To restore a virtual machine, launch the Backup, Archive, and Restore console. This can
be launched on the master server or on the Hyper-V server.
1. Set the source and destination clients.
From the File menu, select Specify NetBackup Machines and Policy Type.
2. Set the Source client for restores as the virtual machine you wish to restore. Be sure
to identify the source client exactly as it was backed up (using the appropriate
hostname, display name or GUID)
3. Select the Destination client for restores. Always use a hostname as the
destination, never a display name or GUID. Note that this field is ignored for full VM
restores; for full VM restores the destination is specified in the restore wizard later
in the process.
4. Select the Policy type for restores, ensuring you select Hyper-V to display all Hyper-
V backups.
MS-Windows and Standard do not display backups from virtual machines that were
backed up with Hyper-V policies.
B-34
Selecting the Restore type
File or folder recovery
Full virtual machine recovery
35
Select the appropriate restore type under the Select for Restore button:
• Normal Backups: This option is used to view and restore individual files.
• Virtual Machine Backup: This option is used to restore the entire virtual machine.
These options are shown in more details on the following slides.
B-35
File and folder recovery of Hyper-V virtual machine
• Restore to a system with the

NetBackup client installed
• Restore to the Hyper-V server
• Restore to a file share that can be
accessed by the VM
36
The Restore type of Normal Backups is used to view and restore individual files.
Specify the destination as the virtual machine’s host name (not the display name or
GUID).
Note that restoring individual files to a virtual machine requires that the NetBackup
client is installed on that VM. Alternatively, restore to a shared folder that can be
accessed by the virtual machine client.
Note that you can restore Windows files to a Windows guest operating systems, but not
to Linux. Similarly you can restore Linux files to supported Linux guest operating
systems, but not to Windows.
If a Linux file system was not quiesced before the snapshot, some files may be
inconsistent.
B-36
Full VM Recovery of Hyper-V virtual machine
Notes:
• The source must be the VM identifier (host name, display
name, or GUID) that was used during the backup.
• The destination client field is ignored, and is selected later
in the Virtual Machine Recovery wizard.
37
The Restore type of Virtual Machine Backup is used to restore the entire virtual
machine.
In the Directory Structure pane, click on the Hyper-V backup, then click the check box.
You must select the entire virtual machine.
If you are restoring from physical tapes, click the Preview button to see which tapes are
needed for the restore.
B-37
Full Hyper-V VM Recovery Options
38
When you restore the virtual machine to its original location with the Overwrite virtual
machine option, note: The same virtual machine on the Hyper-V server is automatically
turned off and deleted before the restore. The .vhd or .vhdx files of the virtual machine
on the Hyper-V server are overwritten by the .vhd or .vhdx files from the backup image.
If any new .vhd or .vhdx files were created after the backup, those files are not
removed.
B-38
Notes on full VM restores on Hyper-V
• A backup of the full virtual machine can be

restored only to Windows Server 2008 or later
with the Hyper-V role enabled. Windows 2008
• If you restore a virtual machine without the

Overwrite virtual machine option, you must
remove the current virtual machine.
vm1 vm1
• Restoring two VMs with a shared drive can

?
result in a race condition, with one of the
restores failing.
39
A backup of the full virtual machine can be restored only to Windows Server 2008 or
later with the Hyper-V role enabled.
By default, the NetBackup client on the Hyper-V server does not have Windows
Administrator privileges. You can restore a full virtual machine from the NetBackup
server. You cannot restore a full virtual machine from a NetBackup client that does not
have Administrator privileges.
When you restore the virtual machine to its original location with the Overwrite virtual
machine option, note: The same virtual machine on the Hyper-V serve is automatically
turned off and deleted before the restore. The .vhd or .vhdx files of the virtual machine
on the Hyper-V server are overwritten by the .vhd or .vhdx files from the backup image.
If any new .vhd or .vhdx files were created after the backup, those files are not
removed.
When you restore the virtual machine to a Hyper-V server that has a virtual machine of
the same GUID, you must select the Overwrite virtual machine option. Otherwise, the
restore fails.
B-39
Notes on individual file restores on Hyper-V
• Cross platform restores not supported
Linux Windows
• Files greater than 2GB require a NetBackup

client at the destination
• There is no mechanism for quiescence of a NetBackup >2GB

Client
Linux VM on Hyper-V
– The snapshot is made and backups succeed, but may
contain inconsistent files.
– A NetBackup.lost+found directory is created for each
volume.
40
To restore files to a shared location on the virtual machine, note: Virtual machines must
be in the same domain as the NetBackup client and master and media server.
To restore Windows encrypted files, the NetBackup Client Service must be logged on as
Administrator on the target host for the restore. Under services on the control panel,
change the logon for the NetBackup Client Services from Local System Account to
Administrator.
B-40
Topic: Performing Hyper-V restores with the NetBackup
Add-in for SCVMM
After completing this topic, you will be able to perform Hyper-V restores
with the NetBackup Add-in for SCVMM.
41
After completing this topic, you will be able to perform Hyper-V restores with the
NetBackup Add-in for SCVMM.
B-41
Using the NetBackup Add-in for System Center Virtual Machine
Manager (SCVMM)
Supported:
• Recover VM to original or alternate location
• Monitor the progress of VM recovery
Unsupported:
• Restoring individual files, or to a staging location
• Generating a new VM ID or VM name during restore
42
NetBackup 8.0 introduces an add-in for the System Center Virtual Machine Manager
(SCVMM). NetBackup provides a Recovery Wizard in the SCVMM console to restore a
VM from its NetBackup backup image. In NetBackup 8.0, you can use the add-in to:
• Recover the full virtual machine to its original location or to an alternate location.
• Monitor the progress of recovery jobs that the add-in initiated.
Note that the NetBackup Recovery Wizard is for the restore of an entire VM, not for
restoring of individual files, and also does not support restore to a staging location. To
restore individual files from the VM backup, or to restore the VM to a staging location,
use the NetBackup Backup, Archive, and Restore interface.
Changes that are made through Hyper-V Manager on individual Hyper-V hosts or
clusters can take up to 24 hours to be reflected in the SCVMM Console. Until then, the
NetBackup add-in Recovery Wizard may not have the latest VM configuration state. In
that case, the Recovery Wizard's pre-recovery checks related to the VM’s location may
not be based on the most recent data in SCVMM.
Note also that the NetBackup 8.0 Administration Console introduces enhancements for
restoring a VM, which are not provided in the SCVMM add-in Recovery Wizard:
• A new VM GUID is generated by default when you restore a VM to an alternate
location.
• A new VM display name can be specified when you restore a VM.
B-42
Running the recovery wizard: VM selection
43
The following slides show the NetBackup add-in being used to restore a Hyper-V virtual
machine. This screenshot shows the first screen in the recovery wizard: Virtual Machine
Selection.
First, use the drop-down list to select the master server that made the backup. If the
master server is not in the drop-down, you must add the server to the master server
list.
Next, for the VM Identifier, enter the display name, host name, or GUID of the virtual
machine that you want to restore. Note: This field is not case-sensitive.
When you are done, click Next to go to the next screen of the wizard.
B-43
Running the recovery wizard: Backup image selection
44
By default, the most recent backup image is displayed, listing the information about the
VM backup image.
Click Select Another Image option to select a different backup image. Use this option to
find a backup image, then select the image in the lower pane and click Select Backups
can easily be viewed by date ranges: Last 7 Days, Last 14 Days, Last 30 Days, or by
setting a custom date range.
The Virtual Machine Attributes lists the information about the VM at the time it was
backed up. Virtual Machines Files lists the files that are included in the VM image.
B-44
Running the recovery wizard: Restore options
45
The screenshot shows the Restore Options screen in the NetBackup Recovery Wizard
for SCVMM.
The VM identifier is given, and cannot be changed in this recovery wizard in NetBackup
8.0. Use the NetBackup Backup, Archive, and Restore interface to restore a VM while
simultaneously changing the restore VM identifier used.
Also listed is the Hyper-V server on which to restore the VM. The default is the original
server, however this can be changed by clicking the Change button.
You can set the restore destination, which is set to the original location, by default. Click
Browse to change it. Note: To create a new directory for the restore location, click the
Explore directory link at the bottom of the Select Destination Folder dialog.
Administrator privileges may be required.
If a virtual machine with the same display name exists at the destination, that VM must
be deleted before the restore begins. Otherwise, the restore fails. Select the Overwrite
existing virtual machine option to delete the existing VM.
B-45
Running the recovery wizard: Review settings
46
Use this screen to review the settings that are used for the recovery and to start the
recovery.
Click the Recover button to start the restore job.
B-46
Checking the status of a recovery job
47
In the SCVMM console, open the Jobs workspace to view Running jobs. The Status
column shows the job’s percentage completion.
B-47
Listing recent recovery jobs
48
For a listing of recent jobs and past jobs, click History, and select a time range from the
top ribbon.
B-48
Lesson summary
• Key points
– In this lesson, you learned about virtual machines and support for virtual machines in Hyper-V.
– You also learned how to configure NetBackup to protect Hyper-V virtual machines, and backup Hyper-V
virtual machines.
– Finally, you learned how to restore Hyper-V virtual machines in the NetBackup interface, as well as the
NetBackup Add-in for SCVMM.
– NetBackup for Hyper-V Administrator’s Guide
– NetBackup Add-in for Microsoft SCVMM Console Guide
49
listed on the slide and remember to check the Veritas support Web site frequently.
B-49
End of presentation
B-50
Appendix C: Configuring NetBackup BasicDisk Staging
This is the “Configuring NetBackup BasicDisk Staging” appendix in the “Veritas

C-1
Topic: Configuring NetBackup BasicDisk Staging
After completing this topic, you will be able to configure disk staging with
BasicDisk storage units.
After completing this topic, you will be able to configure disk staging with BasicDisk
storage units.
C-2
Understanding BasicDisk staging
Final
2. Relocation destination
Source: Disk staging storage unit
storage unit schedule
1. Backup
Source: Policy 3. Deletion
When: High watermark
1 3 is reached
Temporary
storage for disk
staging
Client
Disk staging provides a method to initially send backup images to a disk and then later
copy the images to another media type. The media type for the final destination is
typically tape, but can also be disk. Although BasicDisk storage units can perform disk
staging, NetBackup’s preferred method of disk staging is using Storage Lifecycle Policies.
NetBackup BasicDisk disk staging is conducted in three separate operations:
1. Clients are backed up by a policy that specifies a BasicDisk storage unit as the
backup destination. The policy’s schedule specifies when this operation occurs.
2. Images are then copied from the BasicDisk storage unit to the final destination
storage unit. The images are duplicated based on the relocation schedule configured
in the BasicDisk storage unit configuration.
3. The images will continue to exist on both the disk staging storage unit and the
destination storage unit, until either the image expires, or the BasicDisk storage
unit’s high water mark (HWM) is reached. Reaching the HWM indicates that the
storage unit is full, at which point it pauses the backup, finds images that have been
successfully copied to the destination storage unit, and expires these image copies.
Images are deleted until the low water mark (LWM) is reached, or until there are no
more valid images to expire.
Although NetBackup 8.1 documentation has stated that oldest images are deleted first,
this is not correct. For more information, refer to Article 100037434: Documentation
error: image deletion on a Disk Staging Storage Unit (DSSU) when the High Water Mark
(HWM) is reached does not work as documented, found online at
C-3
Temporary staging area
To configure a BasicDisk storage unit for disk staging, first create the BasicDisk storage
unit. Alternatively, you can modify an existing BasicDisk storage unit.
Within the properties of a BasicDisk storage unit, you mark the Enable Temporary
Staging Area. Copy data to its final destination according to its staging schedule. check
box. When you mark this check box, the Staging Schedule button becomes active.
BasicDisk storage units configured for staging require a staging schedule, which is
configured by clicking the Staging Schedule button.
C-4
Disk staging schedule attributes
The Staging Schedule button opens the Add Schedule - Disk Staging dialog, which looks
similar to the scheduling dialog when configuring policies. Parameters include:
• Name: Defaults to (and is required to be) the name of the storage unit.
• Priority of relocation jobs started from this schedule: Specifies the priority assigned
to duplication jobs for this policy, ranging from 0 (default) to 99999 (highest
priority).
• Final destination storage unit: The name of the storage unit where the images are
copied from the disk staging storage unit.
• Final destination volume pool: The name of the volume pool on the final
destination storage unit where the images are to be copied, if the final destination is
a Media Manager storage unit (tape), or is set to Any Available.
• Final destination media ownership: The owner of the backup images after the
relocation process.
• Use alternate read server: Specifies the server to be used to read a backup image
that was originally written by a different media server. Veritas offers a number of
products, such as Veritas Cluster Server and Volume Replication, that enable two or
more computers to access a common set of disk-stored data.
Notice that similar to a policy’s schedule, either a calendar or frequency based schedule
type can be selected.
C-5
Disk staging schedule start window
The Start Window tab provides control for setting time periods during which NetBackup
can start the duplication process of copying backup images on disk to its final
destination. Just like a policy schedule, this is a start window, and although duplication
jobs will start within this time window, they do not need to complete within the
window.
C-6
Manual relocation of a BasicDisk staging storage unit
A relocation schedule may be started manually to copy images to the final destination
before the schedule is due to run.
To initiate a relocation schedule:
1. In the NetBackup Administration Console, select NetBackup Management > Storage
> Storage Units.
2. In the right pane, select a BasicDisk staging storage unit.
3. Select Actions > Manual Relocation to Final Destination to initiate the schedule.
If the relocation schedule finds data that can be copied, NetBackup creates a jobs to
copy the data to the final destination storage unit.
The image then exists on both storage units until the disk staging storage unit becomes
full and the oldest images are deleted.
C-7
Staging jobs for a BasicDisk staging storage unit
174. A backup to the BasicDisk storage unit

175. A backup to the BasicDisk storage unit
177. The disk staging job which initiates duplications
– Note the Job Policy is listed as __DSSU_POLICY_storageunitname.
178. A duplication job which copies the backup images to the final storage destination
– In this case the duplicated images go to storage unit master_tape_stu.
The Activity Monitor in the NetBackup Administration Console can be used to monitor
disk staging jobs. The slide shows two Backup jobs that were run to the BasicDisk
staging storage unit, job IDs 174 and 175.
At a later point in time, the disk staging job runs. It is listed as type Backup, and has the
Job Policy listed as _DSSU_POLICY_storage_unit_name. This is job ID 177.
A child job with type Duplication is listed under that backup job, with job ID 178. This
job may have many backup images associated with it, all of which are being copied from
the original storage unit, in this case master_bdisk_stu, to the destination storage unit,
in this case master_tape_stu.
C-8
End of presentation
C-9

Nbu81 Admin Lesson Book PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nbu81 Admin Lesson Book PDF

Uploaded by

Copyright:

Available Formats

Veritas NetBackup 8.

Not for Distribution

Course Developer Technical Contributors and Reviewers

Bill Drazkowski Chris Amidei Robert Owen

Lesson 1: Introducing NetBackup

Lesson 2: Configuring NetBackup Storage

Lesson 3: Configuring Policies

Lesson 4: Performing File System Backups

Backup job-related tips ..............................................................................................................4-27

Lesson 5: Performing File System Restores

Lesson 6: Configuring Disk Pools

Table of Contents iii

© 2018 Veritas Technologies LLC. All Rights Reserved

Not for Distribution

Lesson 8: Configuring Tape Storage

Lesson 9: Managing Tape Storage

Lesson 10: Performing Virtual Machines Backups

Lesson 11: Performing Virtual Machines Restores

Lesson 12: Duplicating Backups Using Storage Lifecycle Policies

Storage lifecycle policy concepts .............................................................................................12-12

Lesson 13: Managing and Protecting the NetBackup Catalog

iv Veritas NetBackup 8.1: Administration

© 2018 Veritas Technologies LLC. All Rights Reserved

Not for Distribution

Lesson 15: Collecting Logs and Diagnostic Information

Appendix A: Introduction to Application and Database Backups

Appendix B: Protecting and Recovering Hyper-V Virtual Machines

Appendix C: Configuring NetBackup BasicDisk Staging

© 2018 Veritas Technologies LLC. All Rights Reserved

Not for Distribution

Not for Distribution

This course is intended for NetBackup administrators responsible for:

Administering a backup environment for a company or an organization is a complicated

Not for Distribution

• Create and configure storage units and storage unit groups.

Not for Distribution

Not for Distribution

On-demand labs User Support

Recorded video Ask the Experts

Participant guide Self-help lab

Not for Distribution

• The latest technology articles

Not for Distribution

Not for Distribution

Lesson 1: Introducing NetBackup

This is the “Introducing NetBackup” lesson in the “Veritas NetBackup 8.1:

Not for Distribution

This lesson is the first lesson in this course.

Not for Distribution

NetBackup appliance overview Describe the NetBackup appliance offerings.

Using NetBackup OpsCenter Navigate the OpsCenter Console.

Not for Distribution

Not for Distribution

Back up data with

Not for Distribution

Data protection and

Recovery Point - RPO Recovery Time - RTO

Because no one wants to be forced to recover from a disaster, preventing damage to

Not for Distribution

• Support backup and recovery

• The backup methods to be used to protect user systems

Not for Distribution

• Initiates backup and recovery activities on the