Symantec Netbackup Education - 100-002701-A

CONFIDENTIAL - NOT FOR DISTRIBUTION
Symantec NetBackup
7.5 for Windows:
Install, Configure,
and Deploy
(Lessons)
100-002701-A
COURSE DEVELOPERS Copyright © 2012 Symantec Corporation. All rights reserved.
Cheryl Faulkner Symantec, the Symantec Logo, and VERITAS are trademarks or
Kris Faulkner registered trademarks of Symantec Corporation or its affiliates in
John Gerhardson the U.S. and other countries. Other names may be trademarks of
Lisa Goldring their respective owners.
Tomer Gurantz THIS PUBLICATION IS PROVIDED “AS IS” AND ALL
Steven Schwartze EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS
Sandy Tipper AND WARRANTIES, INCLUDING ANY IMPLIED
Robyn Winkler WARRANTY OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE
LEAD SUBJECT MATTER
DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
EXPERTS DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Christopher Amidei SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR
Peter Farley INCIDENTAL OR CONSEQUENTIAL DAMAGES IN
Bob Farnsworth CONNECTION WITH THE FURNISHING, PERFORMANCE,
Joseph Gallagher OR USE OF THIS PUBLICATION. THE INFORMATION
CONTAINED HEREIN IS SUBJECT TO CHANGE WITHOUT
Micke Ostrom
NOTICE.
Robert Owen
Kleber Saldanha No part of the contents of this book may be reproduced or
transmitted in any form or by any means without the written
Christopher Winter
permission of the publisher.
Symantec NetBackup 7.5: Install, Configure, and Deploy
TECHNICAL Symantec Corporation
CONTRIBUTORS AND World Headquarters
REVIEWERS 350 Ellis Street
The NetBackup 7.5 Mountain View, CA 94043
Advisory Board United States
http://www.symantec.com
Copyright © 2012 Symantec Corporation. All rights reserved.

2
Table of Contents
Course Introduction
Course overview...................................................................................... Intro-2
Lesson 1: Introducing NetBackup

Introduction to data protection...................................................................... 1-3
The NetBackup environment........................................................................ 1-8
NetBackup concepts .................................................................................. 1-12
NetBackup options and agents .................................................................. 1-22
Lesson 2: Installing NetBackup

Preparing for NetBackup installation and configuration ............................... 2-3
Using the preinstallation Environment Checker ......................................... 2-12
Installing your NetBackup environment...................................................... 2-15
Installing NetBackup clients ....................................................................... 2-24
Verifying your NetBackup installation......................................................... 2-29
Lesson 3: Using the NetBackup Administrative Interfaces

The NetBackup Administration Console....................................................... 3-3
Enabling administrative access from media servers .................................. 3-12
NetBackup OpsCenter ............................................................................... 3-18
Lesson 4: Configuring Tape Storage and Media

NetBackup storage device concepts ............................................................ 4-3
Configuring tape devices............................................................................ 4-14
NetBackup media concepts........................................................................ 4-25
Configuring media ...................................................................................... 4-34
Verifying tape storage ................................................................................ 4-50
Lesson 5: Configuring Disk Storage

NetBackup disk storage types...................................................................... 5-3
Configuring a basic disk storage unit ........................................................... 5-8
Configuring AdvancedDisk ......................................................................... 5-17
Verifying disk storage ................................................................................. 5-30
Lesson 6: Configuring File System Backups

Introduction to backup policies ..................................................................... 6-3
Configuring file system backup policies ....................................................... 6-6
Viewing and editing a policy ....................................................................... 6-13
Lesson 7: Performing File System Backups and Restores

Performing manual backup operations......................................................... 7-3
Performing restore operations using the BAR interface ............................. 7-13
Performing restore operations using OpsCenter Operational Restore....... 7-33
Backup and restore job-related tips............................................................ 7-48
3 Table of Contents iii
Lesson 8: Protecting Backup Data
Backup duplication concepts ........................................................................ 8-3
Storage lifecycle policy concepts................................................................ 8-12
Using storage lifecycle policies................................................................... 8-23
Introduction to NetBackup Vault ................................................................. 8-45
Lesson 9: Protecting the NetBackup Configuration

Introduction to NetBackup catalogs .............................................................. 9-3
Managing images ....................................................................................... 9-12
Performing catalog backup operations using the wizard ............................ 9-33
Disaster recovery strategies ....................................................................... 9-48
Catalog-related tips..................................................................................... 9-63

4 iv Symantec NetBackup 7.5: Install, Configure, and Deploy
5
Course Introduction

Course overview
Symantec Education’s core data protection curriculum for NetBackup
This course is the basic foundational component within the overall structure of
Symantec Education’s Data Protection curriculum. The 5-day NetBackup
Administration course is comprised of this 3-day course, Symantec NetBackup 7.5:
Install, Configure, and Deploy plus the 2-day Symantec NetBackup 7.5: Manage
and Administer course. Symantec NetBackup 7.5: Install, Configure, and Deploy is
a course covering core tasks for installing, configuring, and deploying NetBackup.
After you complete this course and gain some experience using NetBackup, you
will be ready for the Symantec NetBackup 7.5 Advanced Administration course.
This course provides experienced IT professionals with instruction on advanced
Symantec NetBackup software functionality and administrative tasks. This course
covers advanced NetBackup topics, including deduplication, advanced backup
image copies, application and database backups, virtual machine backups,

NetBackup environment security, and basic NetBackup troubleshooting.

6 Intro–2 Symantec NetBackup 7.5: Install, Configure, and Deploy
Symantec Education’s advanced data protection curriculum for
NetBackup
Advanced-level courses instruct you in additional methods you can use to
customize and maintain your NetBackup environment, such as advanced
troubleshooting methods and other high-level topics.
Because new courses are developed on an ongoing basis, see the Symantec
Education Web site at:
http://www.symantec.com/training and follow the path shown on the
slide for a complete and current list of available courses.

7 Course Introduction
Intro–3
Synopsis of lessons in the course
This section provides a synopsis of what is covered in each lesson in the course.
Symantec NetBackup 7.5: Install, Configure, and Deploy

This course is the first three days of the introductory NetBackup Administration
course for NetBackup administrators.
Lesson 1: Introducing NetBackup

This lesson serves as an introduction to the NetBackup product, explaining at a
high level what NetBackup is and how it works.
Lesson 2: Installing NetBackup

This lesson describes installing and verifying your NetBackup environment.
Lesson 3: Using the NetBackup Administrative Interfaces

In this lesson, you learn to navigate the NetBackup Administration console and to
use NetBackup OpsCenter.
Lesson 4: Configuring Tape Storage and Media

This lesson describes how to configure and verify tape devices and media using
the Device Configuration Wizard.

Lesson 5: Configuring Disk Storage
This lesson elaborates on disk storage, describing the NetBackup disk storage
types, including AdvancedDisk, and how to configure and verify them using the
Storage Server Configuration Wizard.
Lesson 6: Configuring File System Backups

This lesson describes the various basic attribute settings you can apply to policies
for backing up file systems, including how to create a policy, set up policy
schedules, add clients to a policy, and define backup selections.
Lesson 7: Performing Backups and Restores

This lesson outlines how to perform manual backup operations and how to
perform restore operations. This lesson also describes how to troubleshoot
problems with backups and restores.
Lesson 8: Protecting Backup Data

This lesson introduces you to NetBackup media server deduplication. In this
lesson, you learn about the benefits of storage lifecycles, and how to configure
NetBackup storage lifecycles. You are also introduced to Auto Image Replication
and NetBackup Vault.
Lesson 9: Protecting the NetBackup Configuration

This lesson introduces you to NetBackup catalog management, including
protecting your NetBackup catalogs, backing up and recovering your catalogs, and
troubleshooting common catalog issues.
Symantec NetBackup 7.5: Manage and Administer

Symantec Education offers a Symantec NetBackup 7.5: Manage and Administer
course, which is the final 2 days of the introductory Symantec NetBackup:
Administration course for NetBackup administrators. Symantec NetBackup 7.5:
Manage and Administer includes the following topics:
• Monitoring NetBackup
• Managing and optimizing tape storage
• Managing and optimizing disk storage

• Optimizing file system backups
• Introduction to enterprise backups
• Working with support

Intro–5
Intended audience
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:
• Installing NetBackup
• Configuring devices and storage units
• Configuring and managing media
• Creating and configuring backup policies
• Performing backups and restores
• Protecting the backup data and configuration

For additional information about topics not covered by this course, see the
“Symantec 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

Course objectives
After completing this course, you will be able to perform the tasks listed on this
slide.

Intro–7
Symantec Connect
Symantec Connect is the premier online technical community for IT professionals.
Symantec Connect has thousands of members and continues to grow rapidly.
Symantec Connect is filled with resources for IT professionals to be successful
with Symantec products. Symantec Connect 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.
Symantec Connect 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
Symantec Connect is responsive to the needs of Symantec customers. Features of

this online community are added based on feedback members provide.
Best of all, it is free. Sign up to become a member at
http://www.symantec.com/connect.

The Symantec Certified Specialist (SCS) program
Symantec offers Specialist certification credentials for many availability and
security products as a means to validate an individual's technical skills,
knowledge, and competence. Professional certification programs are a widely
recognized industry practice used to measure skills and competencies. Individuals
who are certified have demonstrated the knowledge and skills to effectively use
and manage Symantec applications and possess high-performance technical
problem solving expertise.
Although each product varies in complexity and depth, all certification exams are
created specifically for customers and cover core elements measuring technical
knowledge against factors such as installation, configuration, product
administration, day-to-day maintenance, and troubleshooting.

Intro–9

Lesson 1
Introducing NetBackup

15

16 1–2 Symantec NetBackup 7.5: Install, Configure, and Deploy
1
Introduction to data protection
This topic introduces you to general data protection concepts.
After completing this topic, you will be able to discuss data protection concepts,
and start developing a data protection plan.
The IT administrator’s dilemma
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 Symantec NetBackup 7.5 product suite provides a rich set of tools and
technologies that address these issues.

17 Lesson 1 Introducing NetBackup
1–3
Data protection
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
A data protection plan
A data protection plan outlines the importance of an organization’s data, and the
strategies and 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 users in an environment
• The backup methods to be used to protect user systems
• Backup windows, which are times during which backup jobs can be run
• Retention periods, which define how long to keep backed-up data
Developing a data protection plan is beyond the scope of this course. But as you
work through this course, you are encouraged to think about backup and recovery,
and the service level agreements to which you are committed.

1–5
Symantec data protection
Symantec offers several products that, along with NetBackup and its options, are
available to manage and maintain your organization's data protection plan. For
example:
• Bare Metal Restore
Bare Metal Restore seamlessly combines system imaging capabilities with
NetBackup’s data restoration, provides all the files and services necessary to
perform system recovery, including the ability to perform diskless network
booting, temporary OS installation, and disk configuration. This feature boasts
a complete system recovery time of approximately 15 minutes on any
platform.
• NetBackup PureDisk
NetBackup PureDisk is the deduplication engine for NetBackup, enabling
efficient, storage-optimized data protection for the data center, remote office,
and virtual environments. NetBackup PureDisk is a software-based
deduplication solution that is tightly integrated with NetBackup. PureDisk is
ideal for environments that require high performance and scalability.
• NetBackup RealTime
NetBackup RealTime provides continuous data protection (CDP) and
replication for critical applications helping to dramatically reduce recovery
time and data loss. Backup windows can be eliminated and administrators can
recover instantly or to any point in time. Unlike traditional backup methods
RealTime can recover terabytes of data in seconds without any extra storage.

• Veritas Storage Foundation from Symantec
Veritas Storage Foundation provides a complete solution for heterogeneous
online storage management. Based on the industry-leading Veritas Volume
Manager and Veritas File System, it provides a standard set of integrated tools
to centrally manage explosive data growth, maximize storage hardware
1
investments, provide data protection, and adapt to changing business
requirements.
• Veritas Cluster Server
Veritas Cluster Server is the industry’s leading cross-platform clustering
solution for minimizing application downtime. Using central management
tools, automated failover, features to test disaster recovery plans without
disruption, and advanced failover management based on server capacity,
Cluster Server enables IT managers to maximize resources by moving beyond
reactive recovery to proactive management of application availability.
• Veritas Volume Replicator
Veritas Volume Replicator provides a world-class foundation for continuous
data replication, enabling rapid and reliable recovery of critical applications at
remote recovery sites. As an option to Veritas Storage Foundation by
Symantec, Volume Replicator enables efficient replication of data over IP
networks, offering an extremely flexible, high-performance alternative to
traditional array-based replication architectures.
• Replication Director
Replication Directoradds an integrated solution for the creation, management,
and recovery of snapshots, replicated snapshots, and snapshot copies to
OpenStorage (OST)-compliant vendor’s filers and arrays. By using
NetBackup’s Storage Lifecycle Policies, Replication Director provides end-to-
end protection using snapshots and snapshot replication (disk-to-disk-to-tape,
or D2D2T).

1–7
The NetBackup environment
This topic introduces you to the NetBackup environment.
After completing this topic, you will be able to list the functions of the various
NetBackup components and describe the overall product architecture.
NetBackup component definitions

The systems that have data to be backed up are called clients. Symantec
NetBackup Client software resides on each client.
Symantec 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.
• 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
archive files called backup images. One master can control several media
servers.
• 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.
• The Enterprise Media Manager (or EMM) server is a centralized data store and
group of services that manage and allocate the resources required for all
NetBackup operations. Frequently, the EMM server is on the same host as the
master server.

1
NetBackup OpsCenter
OpsCenter is a multi-product management interface that can provide sophisticated
management functions for NetBackup, notably for reporting and restore. 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.
Although not strictly required by NetBackup, some advanced features are only
accessible through OpsCenter.

1–9
NetBackup server hierarchy options
The NetBackup server software supports two major 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 all three major roles: master server, EMM
server, and media server. OpsCenter is best 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. The EMM server is usually run on the same host as
the master.

1
NetBackup domains
The collection of clients and media servers managed by a single master is called a
NetBackup domain.
Sometimes you want to segregate clients into distinct collections for
administrative or performance reasons.
• With NetBackup Enterprise Server, 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–11
NetBackup concepts
This topic introduces NetBackup terms and concepts that are critical to your
understanding of how NetBackup works. After completing this topic, you will be
able to:
• Define common terms used in the NetBackup product.
• Describe how NetBackup backs up and restores data.
Storage types
After a media server creates an image, it must save it somewhere.
Removable media, such as tape, is most cost effective. Robotic libraries automate
operation, and can be shared to provide redundancy and efficient allocation of
resources. Rather than antiquated technology, removable media still serve a
valuable purpose, such as for long term or off-site storage.
Images can be stored on local or networked disks for rapid access, but increasingly
complex permanent storage solutions are built around disk, 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
Physical storage and logical storage
The Media Manager is an integrated part of NetBackup, but deals with the lower-
level aspect of storage management.
Volumes are logical units of storage on media that have been assigned media IDs
and other attributes. This information is recorded in the EMM database.
Note that a double-sided optical disk is actually two volumes because it can be
written on either side—each side being defined as a separate volume.
There are a lot of different kinds of storage that can hold the backed up data.
NetBackup uses a model in which any storage target is modeled as a simple entity.
The entity itself contains properties and rules that describe the storage devices and
how to access them.
The most basic logical storage destination is a storage unit.

1–13
Storage units
A storage unit consists of one or more devices of a specific type and density that
are attached to a specific media server. When backups jobs are run, the storage unit
specifies:
• Which media server will be copying the data from the client to the storage
device?
• Which storage device will be used for the backup?
In the example in the slide, the storage unit specifies which media server will back
up the data (NBU1 or NBU2) and where the backups will be written (LTO3 tapes
in a robotic library or a location on disk).
The media used can be removable or a directory on a hard disk. Removable media
can be in a robot or a stand-alone drive.

1
Volume pools
NetBackup can draw volumes from a volume pool when performing backups.
The volume pool identifies sets of volumes whose use can be reserved for specific
backup jobs. The default pools have predefined uses. You can create other pools to
help you organize your backed up data.
There are four default volume pools in NetBackup:
• NetBackup is the default pool used for adding NetBackup volumes.
• DataStore is the default pool used for adding tapes from other applications,
such as Enterprise Vault, that use NetBackup to manage their media.
• CatalogBackup is the default pool used for storing NetBackup hot, online
catalog backups.
• None is a default pool but differs in that volumes put into it are considered
unavailable for further use.

The scratch pool is a special optional volume pool that you can configure. If you
set up a scratch pool, Media Manager moves volumes from that pool to other pools
that do not have volumes available when needed.

1–15
NetBackup catalog components
NetBackup catalogs are internal databases that contain information about
NetBackup backups and configuration. The information in the catalogs includes
records of the files that have been backed up and the media on which the files are
stored. The catalogs also contain information about the media and storage devices.
The NetBackup catalog resides on the disk of the NetBackup master server. The
catalog consists of the following components:
• The NetBackup database includes policies, schedules, and other files used by
NetBackup.
• The Image database contains information about what has been backed up.
• The Relational database stores data for several NetBackup services, including
media and device data and image metadata information.

1
NetBackup policies: the heart and soul of NetBackup
Policies define the rules that NetBackup follows when clients are backed up. A
backup policy can apply to one or more clients. Every client must be in at least one
backup policy. The best approach to configure backup policies is to divide clients
into groups according to the backup requirements and archive requirements. Then
create 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?
• The Clients list identifies which clients to back up.
• The Backup Selections list identifies which files and data sets to back up.

1–17
Types of backup schedules
Schedules determine how much data is backed up, as well as when. The available
backup schedule types are shown on this slide:
• A full backup backs up all files specified in the backup selections list for the
policy, regardless of when the files were last modified or backed up. Full
backups occur automatically according to schedule criteria. If you run
incremental backups, you must also schedule a full backup in order to perform
a complete restore.
• 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. Differential incremental backups occur automatically according to
schedule criteria. A complete restore requires the last full backup, the last
cumulative incremental backup, and all differential incremental backups that

have occurred since the last full 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.
Cumulative incremental backups occur automatically according to schedule
criteria. A complete restore requires the last full backup and the last cumulative
incremental backup.
Cumulative incremental backups generate more files per backup, but
restoration is quicker.

Note: Note: Many products use different terminology for similar terms.
NetBackup defines differential and cumulative as described here.
• A user backup never starts automatically, but is initiated by the user through
1
the Backup, Archive, and Restore client interface. A user backup backs up all
files that the user specifies. Users can start backups only during the times
allowed under the schedule Start Window tab.
• A user archive is only initiated by the user through the interface on the client
and archives all files that the user specifies. An archive is a special type of
backup that first backs up the file and then deletes it from the local disk if the
backup is successful. This frees local disk space while still keeping a copy for
future use. Users can start archives only during the times that you specify in the
schedule.

1–19
Backing up data: the big picture
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
• Which files and directories are backed up
The following flow is described on this diagram:
1 A policy from the NetBackup database is interpreted, and resources are
allocated from EMM.
2 NetBackup backs up the data to a tar file image over the network to tape, disk,
or other storage devices, according to your policies.
3 During the backup, NetBackup keeps status information in its log files,
enabling you to monitor or report on the backup.
4 NetBackup stores information about what has been backed up in the Image
database and information about the media and volumes used during the backup
in the EMM database.

1
Restoring data: the big picture
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. Simply select the files to be restored.
2 NetBackup uses the information in the Image database, the NetBackup
database, and the EMM database to identify which files are available, where
the backup images are, and where they should be restored.
3 The appropriate image is retrieved from storage 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.

1–21
NetBackup options and agents
This topic provides information on the various options and agents that are
available for NetBackup 7.5. After completing this topic, you will be able to
identify the NetBackup options and agents used to customize your backup
environment.
Online agents and options resources

Both NetBackup core products, NetBackup Server and NetBackup Enterprise
Server, are wholly complete solutions, capable of serving your organization’s data
protection needs.
As your environment and data protection needs evolve, agents and options are
available that enhance NetBackup’s capabilities and how it interacts and protects
your data and applications.
This slide shows you how to list the currently available agents and options for
NetBackup. These options are briefly described on the following pages.

1
NetBackup options
NetBackup options enhance data protection environments with features that
include virtual tape library support, deduplication, offsite tape media management,
and more.
NetBackup Accelerator
NetBackup Accelerator facilitates intelligent, streamlined backups to disk by
increasing the speed of full and incremental backups. It identifies file system
changes that occurred since the last backup, therefore enabling clients to more
efficiently send only changed data to the media server. Using synthesized full
backups, a full backup is created on the media server using the new changed client
data combined with the previous backup image data.
NetBackup Bare Metal Restore (BMR)

NetBackup Bare Metal Restore automates and streamlines the server recovery
process, eliminating the need to manually reinstall operating systems or configure
hardware. With simple commands, you can run complete server restores in a
fraction of the time without extensive training or tedious administration. From the
NetBackup interface, you can execute multiple server restores in parallel to
accomplish mass-recovery operations. One option addresses the demands of
multiple platforms, eliminating the need for customized restore procedures on each
platform.

1–23
NetBackup Client Encryption
Data is encrypted at the source or client to provide a very high level of data
security while in transit over the network and on storage media. Client encryption
is ideal for protecting smaller, yet dedicated clients and databases. It supports a
variety of encryption algorithms, including 128-bit and 256-bit as well as legacy
40-bit and 56-bit encryption methods.
NetBackup Cloud
NetBackup Cloud Storage enables storing backup data to third-party commercial
cloud storage, similar to backing up to on-premise storage. NetBackup 7.5
includes enhanced Cloud Storage as a fully integrated storage alternative,
supporting four popular cloud storage service providers: Amazon, AT&T,
Nirvanix, and Rackspace.
NetBackup Deduplication
The NetBackup Deduplication option enables you to use integrated data
deduplication and replication features. This option enables you to perform
deduplication at the source with client deduplication, or to perform the equivalent
of target-based deduplication by using the NetBackup media server. You can
install and configure deduplication and also optimized duplication of images
(using replication) from the NetBackup Administration Console.
NetBackup Media Server Encryption Option (MSEO)

The NetBackup Media Server Encryption option (MSEO) helps ensure that tapes
being transported offsite cannot be read in the event they are lost, mishandled, or
stolen. MSEO provides maximum flexibility and performance by providing
parallelized and selectable encryption and compression as well as “set it and forget
it” key management.
NetBackup Microsoft Hyper-V

With NetBackup Microsoft Hyper-V, you can reduce the performance impact of
virtual machine (VM) backup and recovery using NetBackup and automatically
discover existing virtual machines as well as those not currently protected. The
NetBackup Enterprise Client delivers even more benefits, including the ability to:
• Eliminate the impact of backup with off-host/server-less backup of individual

VMs
• Protect VMs without using a client or agent inside the virtual machine
• Save time and resources: get two types of recovery—VM and file-level—from
one backup operation
• Perform faster daily backups with incremental backups of entire VMs
• Eliminate backup or recovery compromises if you back up directly to tape.

NetBackup Network Data Management Protocol (NDMP)
The NetBackup NDMP option delivers high-performance backup and recovery of
NAS systems and Internet messaging servers, such as Network Appliance, EMC,
Hitachi, NEC, ONStor, and Mirapoint. NetBackup sends NDMP messages to these
systems to initiate and control backup and recovery operations.
1
NetBackup OpenStorage
NetBackup OpenStorage supports NetBackup communication with intelligent disk
appliances. Participating hardware vendors provide an OpenStorage plug-in with a
disk appliance, which allows NetBackup to leverage the advanced features
supported by these devices. Support for vendor-specific features, such as single
instance storage and off-host appliance-resident duplications, are possible with the
OpenStorage Disk Option.
NetBackup RealTime
NetBackup RealTime provides disk-based continuous data protection (CDP) and
live IP-based replication to dramatically reduce data loss and recovery times of
critical applications. System administrators can perform recovery operations to
reconstruct the state of an application or file system to any point within the data
retention period configured by the user. NetBackup RealTime can perform CDP
and replication across any application and storage array while being integrated
with NetBackup for specific applications agents. You can purchase NetBackup
RealTime as an option to NetBackup or as a stand-alone product.
NetBackup Replication Director

With Replication Director, NetBackup adds an integrated solution for the creation,
management, and recovery of snapshots, replicated snapshots, and snapshot copies
on OpenStorage (OST)-compliant vendor’s filers and arrays. By using
NetBackup’s Storage Lifecycle Policies, Replication Director provides end-to-end
protection using snapshots and snapshot replication (disk-to-disk-to-tape, or
D2D2T). In addition, managing snapshot and snapshot replication in NetBackup
enables customers to use a single pane of glass to monitor and report on both the
traditional backup and primary storage environments.
NetBackup SAN Client

NetBackup SAN Client offloads backup traffic from the LAN and enables fast
backups over the SAN at approximately 150 MB per second. The SAN client can
send data to a variety of NetBackup disk options and enables you to back up and
restore to disk over the SAN. Data is sent to media servers using SCSI commands
over the SAN rather than TCP/IP over the LAN to optimize performance.
NetBackup SAN Media Server

Designed for customers who prefer to utilize their storage area network (SAN) for
backup operations instead of their local area network (LAN), this feature enables
LAN-free data protection with high-performance access to shared resources.

1–25
NetBackup Search
NetBackup Search provides a mechanism to index the file system metadata that is
associated with backup images. That makes searching for relevant information
simple, powerful, and fast. After information is found, the user can take actions
based on that information. NetBackup Search provides a robust legal hold
mechanism that ensures that images relevant to a legal case are not inadvertently
deleted or allowed to expire based on retention levels.
NetBackup Shared Storage Option (SSO)

The NetBackup Shared Storage option is the first heterogeneous SAN-ready
storage solution running on UNIX, Windows, and Linux. This option enables
dynamic sharing of individual tape drives—stand-alone or in an automated tape
library—by virtualizing tape resources. SSO enables you to leverage your
environment’s hardware resources and to maximize utilization and reduce overall
IT costs. The NetBackup Shared Storage Option reduces overall costs by
providing better hardware usage and optimization of resources during backup and
recovery operations. This delivers data availability for utility computing.
NetBackup Snapshot Client

NetBackup Snapshot Client software enables low-impact backups and the ability
to restore data with unprecedented speed and accuracy. This unique client delivers
integration to not only snapshot methods, but also to third-party technologies. This
means that IT departments can leverage existing investments while still providing
maximum performance.
The five features that compose the NetBackup Snapshot Client are:
• NetBackup FlashBackup, which significantly improves backup performance
for systems storing large numbers of files, while allowing for individual file
restores
• NetBackup Instant Recovery Option, which delivers all the benefits of data
protection without the need for data movement
• NetBackup Array Integration Option, which enables the use of hardware point-
in-time copy capabilities for backup and recovery operations
• NetBackup ServerFree Agent, which increases data protection and availability
through snapshot backup technology combined with server-free data

movement for advanced storage architectures
• NetBackup for Oracle Advanced BLI Agent, which delivers high-performance
protection for Oracle databases by greatly reducing the amount of data during
backup and recovery
NetBackup Vault
Use NetBackup Vault to keep mission-critical data safely offsite in the event of a
disaster by automating the complex and tedious process of backup duplication and
offsite media management. Some key benefits include:

• Increased efficiency—Automate and track the movement of backup tapes to
and from an offsite storage facility.
• Simplified duplication tasks—NetBackup Vault provides necessary
redundancy in case the primary backup tape is lost or destroyed, enabling one
copy to be kept onsite and another offsite.
1
• Elimination of manual tape ejection—Tape ejection is handled automatically
based on profiles that determine which tapes should be sent offsite each day.
NetBackup Virtual Tape Option

The NetBackup Virtual Tape option enables you to use virtual tape devices (VTLs)
with NetBackup. Using this option, you can leverage NetBackup's powerful media
management capabilities just like a standard tape drive and you can use
NetBackup to create physical tape copies of virtual tapes (requires supporting VTL
capability).
NetBackup VMware Protection

NetBackup can provide both client and virtual machine (VM) level protection
using the vStorage API. This integration enables a single backup of VMware
images to deliver granular file-level or full image-level recovery, reducing both the
time and cost of VMware data protection.
NetBackup VMware Protection:
• Improves speed by 50 percent and reduces storage by up to 40 percent versus
previous versions’ approaches with VMware Consolidate Backup. Only
NetBackup offers instant recovery of files from block-level increment backups
(BLIB).
• Offers complete deduplication across all virtual and physical systems
regardless of the backup method
• Enables you to automate and manage snapshots inside a virtual machine from
host- and array-based providers
• Eliminates backup and recovery compromises if you back up directly to tape
Symantec Desktop and Laptop Option (DLO)

The NetBackup Desktop and Laptop option provides continuous disk-based
protection and synchronization for users who are in the office or traveling. This
option automatically copies user data to existing network shares or storage,
enabling quick recovery or synchronization of data by the administrator or the user
in the event of data loss.

1–27
NetBackup agents
NetBackup agents optimize the performance of critical databases and applications.
NetBackup Enterprise Vault

NetBackup now automates the protection and recovery of Enterprise Vault
environments. Features and benefits of NetBackup Enterprise Vault include:
• Simplify protection of Enterprise Vault servers—Automatically discover the
various servers and components within your Enterprise Vault environment that
need protection, including partitions and their associated databases.
• Leverage snapshot technology—The backup of the snapshot is performed
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.
NetBackup IBM DB2 UDB Universal Database

NetBackup for DB2 facilitates quick restoration of DB2 to the point in time you
choose. Administrators can leverage tape hardware to the fullest by configuring
backups that use multiple data streams to one or many tape devices. NetBackup for
DB2 provides complete management and tracking of backup tape media, with
extensive support that includes bar code readers, autoloaders, and tape library
sharing.

NetBackup IBM Informix Dynamic Server
NetBackup for Informix delivers online, nondisruptive backup of Informix
database servers across a broad range of platforms. By integrating with Informix’s
native backup utility, ON-Bar, NetBackup leverages Informix’s inherent
parallelism, providing high-performance backup and recovery of Informix
1
environments. In addition, NetBackup manages the protection of the Informix
ONCONFIG configuration file and other critical database files and directories.
NetBackup IBM Lotus Notes and Lotus Domino Server

NetBackup for Lotus Notes provides high-performance backup and recovery of
Lotus Notes/Domino environments. Lotus services and data remain available
during backup because the database is not taken offline. Administrators may
schedule automatic, unattended backups for local or remote Lotus Notes clients
across the network and can back up and restore at the database and transaction log
levels.
NetBackup Microsoft Active Directory

For any enterprise, Microsoft Active Directory is integral in managing network
services. Therefore, the comprehensive protection and quick recovery of Active
Directory is critical. Features and benefits include:
• Recover any Active Directory item—Granular recovery includes the ability to
recover all items with full attributes (for example, user, server, 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.
NetBackup Microsoft Exchange Server

NetBackup for Microsoft Exchange Server simplifies database backup and
recovery without taking the Exchange server offline or disrupting local or remote
systems. A multilevel backup and recovery approach ensures continued
availability of Exchange services and data during backups. Central administration,
automation options, and support for all popular storage devices create the
flexibility administrators need to maximize performance.
NetBackup Microsoft Office SharePoint Server

NetBackup Microsoft Office SharePoint Server simplifies workspace backup and
recovery without taking the SharePoint portal offline. A multilevel backup and
recovery approach ensures continued availability of SharePoint services and data
during backups. Central administration, automation, and support for all popular
storage devices provide the flexibility you need to maximize you return on
investment.

1–29
NetBackup Microsoft SQL Server
NetBackup Microsoft SQL Server delivers comprehensive data protection for SQL
Server and SQL Server databases. An intuitive GUI enables you to implement and
manage consistent, enterprise-wide backup and recovery policies for database and
nondatabase files. NetBackup for Microsoft SQL Server controls all aspects of
media management, including library sharing and individual tape drive sharing.
NetBackup MySQL
Customers can now integrate MySQL databases into their NetBackup environment
by using the Zmanda Recovery Manager (ZRM) for MySQL – NetBackup Option.
This plug-in provided by Zmanda, a Symantec STEP partner, enables NetBackup
to provide centralized backup and recovery of multiple MySQL databases or
servers across Linux, Solaris, and Windows operating systems. Benefits include:
• Scheduling full, differential, and incremental backups of MySQL database
• Recovering the database easily to a required point in time or to any particular
database event
• Backup compression and encryption
• Extensive monitoring and reporting
NetBackup Oracle
The NetBackup Oracle agent simplifies the backup and recovery of all parts of the
Oracle database, virtually ensuring the availability of your Oracle data. The
NetBackup Oracle agent is tightly integrated with the Oracle Recovery Manager
(RMAN) to deliver high performance backup and recovery solutions. It supports
Oracle Real Application Clusters (RAC), offers continuous data protection, and
can clone Oracle databases from backup images.
NetBackup SAP
NetBackup SAP delivers complete SAP-certified data protection for SAP
environments running Oracle databases, virtually ensuring the availability of your
SAP data. NetBackup SAP provides integration with the SAPDBA administrative
interface, leveraging existing user knowledge and reducing training costs.
NetBackup SAP also utilizes the native SAP backup and recovery commands,
providing complete, SAP-centric data protection for customer-specific Oracle

configurations, and delivering data availability for utility computing.
NetBackup Sybase
NetBackup Sybase provides complete online data protection for Sybase. An
intuitive GUI enables organizations to implement and manage consistent,
enterprise-wide backup and recovery policies for database and nondatabase files.
NetBackup Sybase provides comprehensive media management and backup,
including tape library sharing.
NetBackup Sybase:

• Uses scheduling facilities to enable automatic, unattended full database or
incremental (transaction log) backups
• Centralizes administration using Java-based or Windows-based interfaces
• Provides detailed views of backup history that simplify restores, because
backups of databases and transaction logs are easier to track
1
• Provides transparent execution of both Sybase and regular-file-system backup
and restore operations
• Uses highly parallel data streams for fast backup and recovery operations
For more information

For more information about any of these options and agents, see the Symantec
Web site at http://www.symantec.com/support.

1–31
Labs and solutions for this lesson are located in the following appendixes:
• Appendix A provides step-by-step lab instructions.
• Appendix B provides complete lab instructions and solutions.
Lesson 2
Installing NetBackup

47

2
Preparing for NetBackup installation and configuration
This topic presents you with considerations to address before installing
NetBackup. After completing this topic, you will be able to:
• Describe general considerations before installing NetBackup.
• Administer NetBackup license keys.
Before performing installation procedures, see the Symantec NetBackup Release
Notes and the Symantec NetBackup Installation Guide.
Installation preparation
Preparing the servers

• Verify that the server hardware and operating system combination you are
using is listed as a supported system in the installation guide and the release
notes. Also, verify that the devices you plan to use are supported.
• Verify the requirements for disk space in the release notes:
– Depending on your hardware type and operating system, you may need
anywhere from 21 MB to 1735 MB for the NetBackup and the Media
Server program files under the installation directory.
– Likewise, depending on your client hardware and operating system, the
NetBackup Client may require between 9 MB and 354 MB for the program
files.
• Verify the requirements for RAM in the installation guide and the release
notes. At least 512 MB of RAM is recommended, with 256 MB available for
the Java interface program (jnbSA or jbpSA).

49 Lesson 2 Installing NetBackup
2–3
• Disable or remove any other vendor’s backup software from all servers in the
environment.
• Ensure that you have the most current operating system patches and updates
applied to your system. If you are not certain of your OS level, contact your OS
vendor and request the latest patches and upgrades.
• Verify that any extra patches that are mentioned in the NetBackup Release
Notes, the NetBackup Installation Guide, or any other NetBackup
documentation related to your operating environment are already installed on
your system.
Preparing the environment

• Connect storage peripherals and install appropriate drivers before installing
NetBackup. The operating system must be able to detect and interact with a
peripheral device before it can be configured into NetBackup. This subject is
discussed in more depth in the “Configuring Tape Devices” lesson.
Note: Ensure that you reboot the system after installing device drivers.
• Verify that all systems on which NetBackup is to be installed are able to
recognize and communicate with each other. Host name to IP address
resolution and IP address to host name resolution must be available and
working correctly.
• Determine the operating systems of all the component machines.
• For backup planning, see TechNote 332137, NetBackup 7.0 Upgrade Portal at:
http://seer.entsupport.symantec.com/docs/332137.htm.
UNIX
• Ensure that the gzip and gunzip commands are installed on the local
system.
• For Solaris systems, see the NetBackup Installation Guide for information on
how to tune kernel parameters, such as Message Queue, Semaphore, and
Shared Memory Parameters.
Preparing the system administrator

• Have all installation software ready, including all NetBackup DVDs and
required license keys. The installation process requires at least one NetBackup
license key. Additional keys for NetBackup extensions or options can also be
input at installation time or added later.

• Know the administrator password for the server.
• Ensure that you have privileged system administrator access, which is required
for a successful installation.

2
Determining the environment requirements
The following documentation will assist you in meeting NetBackup environment
requirements:
• NetBackup compatibility lists
The NetBackup compatibility lists are located online on the Symantec Support
Web site at: http://www.symantec.com/docs/TECH59978. There
are many compatibility lists, including lists for operating systems, hardware
compatibility, snapshot client, clusters, and application and database agent
support.
• Symantec NetBackup Release Notes
The Release Notes outlines the binary sizes for the NetBackup server and
client software on various platforms. In addition, they list any product
dependencies and operational notes, for example operating system patch
requirements, and the necessity of having gzip and gunzip on UNIX-based

systems.
• Symantec NetBackup Installation Guide
The NetBackup Installation Guide gives general system requirements, for
example minimum memory requirements of 2 GB. In addition there are special
guidelines for Solaris and HP-UX (mostly about kernel parameters), and
clustering guidelines for environments where NetBackup is highly available.
• Symantec NetBackup Backup Planning and Performance Tuning Guide
This guide, available on the Symantec Support Web site, contains NetBackup
capacity planning information, master and media server configuration
guidelines, and best practices, as well as performance tuning information.
2–5
Verifying compatibility
Compatibility has multiple meanings within NetBackup.
• Software compatibility factors enable NetBackup to work with specific
operating systems, databases, and other applications.
• Device compatibility means that devices have been tested and proven to work
with NetBackup.
Software compatibility
The Symantec Support Web site (http://www.symantec.com/support)
maintains compatibility lists for the following:
• Operating systems (OS) compatibility
Also known as a platform support matrix, this information (usually provided as
a TechNote) lists the available operating systems and platforms compatible
with NetBackup. Support is conditional according to the published notes

corresponding to the individual platform.
• Database agents compatibility
This list denotes the versions of databases (such as Oracle, Informix, DB2, and
Microsoft SQL Server) that are supported by the respective NetBackup agent.
This is only a partial record of the compatibility lists that are available. As with all
items on the Symantec Support Web site, these lists are prone to change. Visit the
Web site regularly to review the latest and most complete compatibility lists.

Device compatibility
Your best resource for verifying device compatibility is the NetBackup
Compatibility section of the Symantec Support Web site (http://
www.symantec.com/support). This Web site is where a complete listing of
the supported drives is maintained.
The device compatibility information provided encompasses all products that have
been tested, in addition to products that are believed to be compatible due to their
similarity with a fully tested product. The compatibility lists are categorized in
terms of hardware vendors.
2
To ensure support, devices (drives, libraries, and SAN equipment, where
applicable) must be supported by Symantec, the device manufacturer, and the
operating system vendor. Also verify that the devices have the Symantec supported
firmware levels installed.
Compatibility search results

The following graphic shows an example of the results you may see when
searching for “compatibility list” on the Symantec Support Web site.

2–7
NetBackup licensing
NetBackup requires a license key. You initially enter the license key when the
software is installed. Using license keys enables you to add more products from a
single DVD and makes it easier for you to install options and upgrade to newer
versions of the software.
During the installation process, you are prompted for a license key: Do not mix
cases when entering the license key. The dashes are required.
Note: The Windows installation program validates the license key as you type. If
you make a mistake, the status line indicates that the License Type is invalid.
The license key does not contain a 0 (numeric zero), 1 (numeric one), 5 (numeric
five), Q, spaces, or blanks. If there is any ambiguity between the characters, the
alphabet takes precedence.
After the initial installation, you can administer NetBackup licenses by using the
NetBackup Administration Console, the NetBackup License Key utility, or the
command-line interface.
For additional information about license keys, see HOWTO article 314816:
Frequently asked questions about license keys.

2
Administering license keys
Administering license keys can be necessary, for example, when enabling options
and agents or changing to a different level of NetBackup. You can also list the
licenses on a remote host.
When you install NetBackup, you are prompted to enter all keys for options and
agents. If you purchase an agent or option at a later date, you can enter new license
keys using the NetBackup License Key utility or from the command-line interface.

2–9
Administering license keys using the Administration Console
The license key is a multidigit alphanumeric string. This string contains
information on whether the key is for a server, client, agent, or option (and which
one), whether it is a permanent or an evaluation key, and how and where the key
was generated.
Adding a new license key

To add a license key using the NetBackup Administration Console:
1 Navigate to the NetBackup Administration Console.
2 Select Help > License Keys.
The NetBackup License Keys dialog box is displayed.
3 From the NetBackup License Keys dialog box, click New (Java) or click the
New icon (Windows).
4 In the Add a New License Key dialog box, enter the license key and click OK.
The new license key is displayed in the license listing.
5 After adding the license key, restart all NetBackup utilities, including the
NetBackup Administration Console.
All registered licensed keys details displays the details of the license keys that
are registered on this server. The view lists each license key, the server where the
key is registered, when the key was registered, and the features that the key
provides.

2
Active and capacity-based licensed features
The Summary of active licensed features displays a summary of the active
features that are licensed on this server. This view lists each feature and the
number of instances of the feature that are licensed.
The Summary of active capacity-based licensed features displays the storage
capacity for which the NetBackup environment is licensed and the capacity in use.
The summary also notes whether the license is in compliance. The summary does
not display the amount of physical storage space. All capacity values are
calculated based on the definition that one terabyte = 1,099,511,627,776 bytes.
The OpenStorage Disk Option, the PureDisk Storage Option, and the Virtual Tape
Option do not display all values at this time.
Evaluation periods
The NetBackup license key file is /usr/openv/var/license.txt (Java) or

C:\Program Files\VERITAS\NetBackup\var\license.txt
(Windows). The license key file is encrypted and checksummed. Only the license
library functions can access the contents of the file.
Evaluation keys are valid for 30 days. At the end of the evaluation period, all
daemons or services are shut down; however, if you add a permanent license key
to an evaluation version of NetBackup, you can continue to operate normally.
For more information on licensing, see the Symantec NetBackup Administrator’s
Guide; see TechNote 314816, Frequently asked questions about license keys; or
search for NetBackup licensing on the Symantec Support Web site.

2–11
Using the preinstallation Environment Checker
After completing this topic, you will be able to assess a system to determine if it is
ready for a new NetBackup installation or upgrade.
The preinstallation Environment Checker

The Windows preinstallation Environment Checker is a tool that is included in the
NetBackup distribution, and is sometimes called VxValidate, which is also the
name of the command line utility that starts the tool.
You can run the Environment Checker before performing an installation on a
Windows system to check the system’s suitability for running NetBackup server
software. Checks can be run either against the local system where VxValidate is
being run, or against remote systems.
The tool can be run on Windows XP SP2 or later. Because the tool runs directly
from the NetBackup distribution media, no existing NetBackup installation is

required. In this way, a new environment can be tested for compatibility before
installing NetBackup. In addition, there are no licensing requirements for the tool
to run. One restriction, however, is that IA64 systems are not supported.
The Environment Checker identifies common issues that have caused installations
to fail. The utility identifies these issues, and also provides guidance on how to
resolve these issues. Operating system checks, free disk space checks, and open
ports for communication are some of the conditions that are included in the tests.

2
Running the Environment Checker
Run the preinstallation Environment Checker before installation to identify any
notifications on specific computer environment and NetBackup environment
issues.
To run the Environment Checker and assess whether computers are ready for
NetBackup installation:
1 Start the NetBackup Installation Wizard by inserting the NetBackup for
Windows DVD in the drive. If Autorun is disabled, navigate to the DVD drive
and run Browser.exe.
2 On the Home screen, click Preinstallation.
3 On the Preinstallation screen, click Run the preinstallation Environment
Checker.
4 On the Welcome screen, review the content and click Next.
5 On the Choose screen, mark the appropriate check box to perform a local or
remote environment check.

2–13
Environment Checker Results
When all computers have been checked, the Results screen displays a summary
and a list of the checked systems with a brief result under each computer name.
Click a computer name to see the complete results for that computer. Some of the
checks performed in NetBackup 7.5 are shown on the slide and include:
• Administrator Privileges
• Operating System Version Check
• Port Availability
• CPU Speed
• Total System Memory
The default behavior creates an HTML log file that contains the results of the tests.
You can prevent the creation of this log file by clearing the appropriate check box
before running the utility.

When the Environment Checker is run against several systems simultaneously, the
tests results are collected in a single HTML file for easy viewing.
As a best practice, Symantec recommends logging into a system as a domain
administrator. After you are logged into that system, you can run the Environment
Checker against multiple machines in the environment, and it will use the same
credentials to connect to all the systems.

2
Installing your NetBackup environment
Now that you are familiar with NetBackup installation prerequisites, you can
proceed with the installation.
In this topic, you learn how to:
• Install NetBackup.
• Identify the tasks performed by the NetBackup installation script.
The master server installation process

Installing NetBackup is a relatively straightforward process.
UNIX
1 Log on as root on the master server where you are installing NetBackup.
2 Insert and mount the NetBackup software DVD in the drive.
See the NetBackup Installation Guide for directions and guidelines for
mounting the NetBackup software DVD.
3 From the root directory (/), install the server software:
a Enter the command to install the master server software.
/mountpoint/install
b Answer the prompts to proceed with the installation.
4 Enter a NetBackup license key. (See the “Notes on Entering the License Key”
section.)
5 Confirm or correct the configured name of the master server, media servers,
and Enterprise Media Manager (EMM) server.

2–15
Use the names associated with the specific network interface or the virtual
server name in a cluster.
6 Answer y to the prompt asking if you want to start processes.
Windows
1 Log on as the administrator (Windows) on the master server where you are
installing NetBackup.
2 Insert the NetBackup software DVD in the drive.
3 On the initial browser screen, select Installation.
4 On the Installation screen, select Server Software Installation.
5 Enter a NetBackup license key. (See the “Notes on Entering the License Key”
section.)
6 Select NetBackup Master Server and confirm or correct the configured name
of the master server and the EMM server.
Use the name associated with the specific network interface or the virtual
7 Click Install to install the master server.
Notes on entering the license key

• A license key is required for all servers.
• Further progress is prohibited until a valid key is entered.
• After you enter the license key, the installation options remain active. If you
are installing to remote servers, you must reenter the license key for each
server. If you do not reenter the license key, the installer enables you to
progress to the final installation step, and then fails.
• On the master server, you must enter license keys for any additional
NetBackup software product options or agents used on the server.
• The NetBackup Administration Console can be installed without a license key.

2
The media server installation process
Installing the media server is very similar to installing the master server.
UNIX
1 Log on as root on the media server where you are installing NetBackup.
2 Insert the NetBackup software DVD in the drive and start the installation.
See the NetBackup Installation Guide for UNIX and Linux for directions and
guidelines for mounting the NetBackup software DVDs.
3 From the root directory (/), install the media server software:
a Enter the command to install the media server software.
/cd_rom_directory/install
b Answer the prompts to proceed with the installation.
4 Enter a NetBackup license key. (See “The master server installation process”
section and see “Notes on entering the license key.”)

5 Confirm or correct the configured name of the media server.
6 Answer n to the prompt asking if this is the master server.
7 Enter the name of the master server.
8 Confirm or correct the name of the EMM (Enterprise Media Manager) server.
9 Answer y to the prompt asking if you want to start processes.
Windows

2–17
1 Log on as an administrator on the media server where you are installing
NetBackup.
2 Insert the NetBackup Server software DVD in the drive.
3 On the initial browser screen, select Installation.
4 On the Installation screen, select Server Software Installation.
5 Enter a NetBackup license key. (See the “Installing NetBackup Options and
Agents” section.)
6 Select NetBackup Media Server.
7 Confirm or correct the configured name of the media server.
8 Enter the configured name of the master server.
9 Confirm or correct the name of the EMM (Enterprise Media Manager) server.
10 Click Install to install the media server.

2
Starting the installation
The screen shot on this slide illustrates how to start the installation process.

2–19
Useful links during Windows installation
During the installation, some useful links are displayed, including links to:
• NetBackup SORT
http://sort.symantec.com/netbackup
• The NetBackup Upgrade Portal
http://www.symantec.com/docs/TECH74584

2
The NetBackup Product Improvement Program
During installation, an option is provided to participate in the NetBackup Product
Improvement Program. This option is enabled by default.
This program gathers information on the use and installation of NetBackup
products, with the goal of increasing insight into how the products are used and
improving Symantec’s ability to enhance these products accordingly.
For more information about the Product Improvement Program, see TechNote
169018: NetBackup Product Improvement Program at
http://www.symantec.com/docs/TECH169018.

2–21
Entering the license key

This screen shot illustrates where you enter the license keys during the
installation.Although you can add license keys later, you should enter them now. If
you add any license keys later through the NetBackup Administration Console,
you must restart the console.

2
Entering and confirming the server names
The screen shot on this slide illustrates where you enter or confirm the server
names.
• For Master Server Name, for master server installations, enter or accept the
name of the local computer. For media server installations, change the name to
the master server name to which the media server is configured.
• For Additional Servers, enter the names of any additional NetBackup master
servers and media servers that you want to communicate with this server.
Include the names of computers where you plan to install NetBackup later.
• On Windows, the Media Server Name field is displayed only for NetBackup
Enterprise media server installations. When you install media server software,
this field defaults to the local server name.
• The EMM server contains all of the information about NetBackup volume
configuration and device configuration. By default, NetBackup installs the

EMM server on the master server. The EMM Server Name is populated
automatically when you enter the master server name. This configuration is
preferred and is the most efficient.
• OpsCenter is a Web-based administration and management tool for
NetBackup. If you have an OpsCenter server or plan to install one, enter the
server name or the IP address for that server in the OpsCenter Server Name
field (not shown in the slide).

2–23
Installing NetBackup clients
After completing this topic, you will be able to install NetBackup client software
locally.
NetBackup client software

Windows client software is distributed on the NetBackup Windows DVD or using
ESD images.
UNIX server installation automatically copies the same version of client software
to the hard disk and installs it. All versions of UNIX client software are provided
on the UNIX DVD for the following two circumstances:
• Locally installing clients that are not also NetBackup servers
• Providing a client software distribution repository on a NetBackup server for
clients with a different operating system than the server

2
Methods of distributing client software
There are four ways to distribute NetBackup client software:
• Local installation
The NetBackup client software can be installed on the machine by providing a
copy of the NetBackup client software.
• Installation from a file share
By putting a copy of the NetBackup client software on a file server, any client
on the network can install the software to itself.
• UNIX server to UNIX client
A NetBackup UNIX master server can push the client software to UNIX
clients only, using standard protocols such as rsh, ftp, ssh, and sftp. These
protocols are available in a combination of the NetBackup Administration
Console, and an install_client_files script.
• Windows server to Windows client

Any Windows server that has a copy of the NetBackup software, even a
Windows server that does not have NetBackup currently installed, can push the
NetBackup client software to other Windows clients out on the network.

2–25
Local client or remote file share installation
The simplest way to install the NetBackup client is by performing a local
installation. This involves inserting the NetBackup software DVD, or a copy of it,
into the client and running the installation wizard. Initiate the wizard by running
the install script on Java, or by running the Browser.exe program on
Windows; then select the client software installation.
Additionally, the Windows client software directory contains a setup.exe
program that can be run directly. It also contains a silentclient.cmd
command script that can be modified for installations that require no user input.
If you place the NetBackup software on a file share that is accessible by the client,
these installation methods can be invoked using a remote file share.

2
Distributing client software: UNIX to UNIX
You can push install client software to UNIX clients using the NetBackup
Administration Console. This method uses rsh to transfer the client software.
In addition, you can run the install_client_files script from a
NetBackup UNIX server to push the client software using any of the following
methods:
• rsh • ftp
• ssh • sftp
For the FTP and SFTP methods there is an additional step to perform after the
install_client_files script runs. The root user on each client machine
must run the client_config script. The client_config script installs the
binaries by moving them from /tmp to /usr/openv/netbackup and

updates the /etc/services and inetd.conf files or the xinetd.d
directory, as appropriate.
To push install client software to UNIX clients using any of the push install
methods, including using the Administration Console, you must install the client
software on a UNIX master server. See the NetBackup Installation Guide for
details on these installation methods.
To push client software using the NetBackup Administration Console, the host
must be included in the clients list of any policy. Under the Clients tab, select the
client onto which you want to install client software and click Install Software.
The Install UNIX Client Software window is displayed.
2–27
Distributing client software: Windows to Windows
NetBackup provides a method of distributing the Windows NetBackup client
software remotely. When running the NetBackup client installation on a Windows
server, there is an option to install to remote computers over the network. The steps
on the slide show the sequence of events to install a remote Windows host.

2
Verifying your NetBackup installation
After completing this topic, you will be able to:
• Identify the default installation paths for the NetBackup software.
• Identify the tasks performed by the NetBackup installation script.
• Verify the NetBackup installation.
• View, stop, and start NetBackup services and daemons.
• Diagnose the most common installation issues.
Default installation paths

UNIX
On the NetBackup server, the installation directory contains the software and the
NetBackup catalog, both of which can become quite large. If space is an issue,
consider installing NetBackup on an alternate file system, such as /opt/usr/
openv. The installation allows you to select an alternate installation location, and
creates the appropriate link from /usr/openv.
The default installation paths for Windows and UNIX are shown on the slide.

2–29
What the installation script does
UNIX
• Places the name of the host in the /usr/openv/netbackup/bp.conf
file on the server
In a clustered environment, it places the virtual host name in the /usr/
openv/netbackup/bp.conf file on the server.
• Adds entries to the /etc/services file for NetBackup and Media Manager
services (for example, robotic daemons)
The /etc/services file contains UNIX TCP/UDP port definitions.
• Checks to see if your server is running Network Information System (NIS)
If it is running, you are instructed to add entries to your NIS services map.
• Adds automatic startup and shutdown scripts to the appropriate directories on
the various supported platforms
• Adds entries to the /etc/inetd.conf server file or the /etc/xinetd.d

server directory: Entries are added for bpcd, vnetd, vopied, and bpjava-msvc
The script sends inetd (or xinetd) a SIGNAL, causing it to read the updated
file. For Solaris 10, the inetd.conf entries are also converted into smf
service manifests and imported into the smf repository.
Windows
• Places the host name into the Windows registry
• Adds entries to C:\WINDOWS\system32\drivers\etc\services
for NetBackup and Media Manager services (for example, robotic services)
• Configures the appropriate Windows services
2
Verifying the NetBackup installation
There is no single way to verify a successful NetBackup or media manager
installation.
The Installation Complete dialog box provides you with one technique for
verifying your installation. Here you can add additional keys and view installation
logs files. To verify the installation, click the View installation log file button to
open the installation log. The log file is located at:
%ALLUSERSPROFILE%\Symantec\NetBackup\InstallLogs\
Within the installation log file, search for “Return Value 3,” which indicates errors.
Important log messages are color-coded with yellow for warning and red for
errors.
Another technique to verify a complete installation is to start NetBackup and
Media Manager and check that the processes are running. This verifies that the
binaries were installed successfully and are operational.
• To display the NetBackup and Media Manager processes, run
/usr/openv/netbackup/bin/bpps -a (Java) or
install_path\NetBackup\bin\bpps [-l|-s|-S] [-t
sample_time [m]] [-i|-x process_group] ...
[host_name] (Windows).
In the syntax, use -s to display a short listing, or -S to display a short listing
without headers. Use -l to display a long listing. Use -t with a sample time
(the default is one second), or -tm with a time in milliseconds.

2–31
• On the master server, ensure that nbpem, nbjm, bprd, bpdbm, bpjobd,
nbemm, and nbrb are running.
• On the master and media servers, verify that vmd is running.
You can also verify that daemons or services and processes are running using the
NetBackup Administration Console:
1 In the object tree pane, click Activity Monitor.
2 In the details pane, click the Daemons tab (Java) or the Services tab
(Windows) and check for the daemons or services that are listed.
3 Click the Processes tab and verify which processes are running.

2
Important NetBackup locations
NetBackup directories
The following directories within the NetBackup installation path contain
customizable scripts and command-line commands, as follows:
UNIX
• Executables are found in: /usr/openv/netbackup/bin
• NetBackup commands are found in:
/usr/openv/netbackup/bin/admincmd
• Sample scripts are found in: /usr/openv/netbackup/bin/goodies
• Media manager commands are found in: /usr/openv/volmgr/bin
• man pages are found in: /usr/openv/man
Windows
• Executables are found in: install_path\NetBackup\bin

• NetBackup commands are found in:
install_path\NetBackup\bin\admincmd
• Sample scripts are found in:
install_path\NetBackup\bin\goodies
• Media Manager commands are found in: install_path\Volmgr\bin
For ease of administration, these NetBackup file paths are appended to the PATH
variable.

2–33
Startup/shutdown scripts for Java
You can use system startup scripts to start the Media Manager and NetBackup
daemons when the system boots and shutdown scripts to terminate them at system
shutdown.
Note: For servers upgrading to a new release of NetBackup, any preexisting
startup and shutdown scripts are saved and the newly released versions of those
scripts are installed.
The installation process copies the netbackup and nbclient startup and
shutdown scripts (located in /usr/openv/netbackup/bin/goodies) to
the init.d directory and creates links to them from the appropriate rc directory.
The NetBackup services script (netbackup) starts or stops the NetBackup
request daemon (bprd), the Media Manager device daemon (ltid), and the Sybase
ASA server (NB_dbsrv).
The NetBackup client script (nbclient) starts or stops the NetBackup client
daemons nbftclnt and bmrbd if BMR is licensed.
The netbackup script must start before nbclient starts and stop after it stops.
The installation process installs the links to the startup and shutdown scripts on the
various platforms. Using Solaris as an example,
/etc/rc2.d/S77netbackup—>/etc/init.d/netbackup
/etc/rc0.d/K01netbackup—>/etc/init.d/netbackup
/etc/rc2.d/S95nbclient—>/etc/init.d/nbclient
/etc/rc0.d/K01nbclient—>/etc/init.d/nbclient
HP-UX, RedHat and SuSE use a similar mechanism.
For RS6000 (AIX), you must manually add appropriate calls to
/etc/rc.veritas.aix in /etc/inittab and /etc/rc.shutdown.
Java environment variables

For ease of administration, Symantec recommends that you append the NetBackup
file paths to the PATH variable and the path for the NetBackup man pages to the
MANPATH variable.
• PATH
/usr/openv/netbackup/bin
/usr/openv/netbackup/bin/admincmd
/usr/openv/netbackup/bin/goodies
/usr/openv/volmgr/bin
• MANPATH
/usr/openv/man

Startup/shutdown scripts for Windows
The scripts bpup and bpdown are used for manual startup and shutdown on
Windows. These scripts are located in install_path\NetBackup\bin.
Windows normally starts NetBackup services automatically, in the services list.
2

2–35
NetBackup command locations
On Windows, the default 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:
• Java: Use the online man pages and ensure that the MANPATH includes
/usr/openv/man.
• Windows: Use the Symantec NetBackup Commands Reference Guide.

2
Starting and stopping processes using commands and scripts
To stop all NetBackup processes, type netbackup stop (Java) or bpdown
(Windows). To start all NetBackup processes, type netbackup start (Java) or
bpup (Windows).
Individual daemons or services have different commands by which you can
terminate and restart them.
See the Symantec NetBackup Commands Reference Guide for detailed information
about how to stop and restart specific services.
Stopping all daemons (UNIX only)

NetBackup provides a script that is intended to stop all daemons when no backup
or restore operation is in progress:
/usr/openv/netbackup/bin/goodies/bp.kill_all

2–37
Common installation issues
Some common installation issues and the verifications you need to make to
prevent them are listed on the slide.

2
2–39

Lesson 3
Using the NetBackup Administrative
Interfaces

87

3
The NetBackup Administration Console
The NetBackup Administration Console is installed by default on master and
media servers. The Administration Console is a Java-based tool for UNIX and
implemented as an executable utility on Windows. After completing this topic, you
will be able to navigate the NetBackup Administration Console.
Navigating the NetBackup Administration Console

The NetBackup Administration Console consists of two major screen areas:
• Object tree (left) pane with branches
The two most notable branches in the object tree are:
– NetBackup Management branch: This 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.
– Media and Device Management branch: This branch contains the utilities
used to manage the volumes, pools, and devices that NetBackup uses to
store backups.
• Details (right) pane
This pane contains the configuration wizards and details specific to the utility
that is selected in the object tree pane.

89 Lesson 3 Using the NetBackup Administrative Interfaces
3–3
The default installation location for the NetBackup Administration console is
/usr/openv/java/jnbSA (UNIX) or
C:\Program Files\VERITAS\NetBackup\bin\NBConsole.exe
(Windows).
As you will see in this topic, the differences between the NetBackup
Administration Console and the NetBackup-Java Administration Console are
relatively minor.

3
NetBackup Administration Console: Activity Monitor
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 or Services tab
The Daemons or Services tab provides status and control for those programs
that typically start whenever the system reboots.
• The Processes tab

The processes tab provides visibility to NetBackup process status.
• The Drives tab (Windows only)
The Drives tab displays the status of NetBackup drives on the master server
that is being monitored.

3–5
NetBackup Administration Console: Reports
The NetBackup Administration Console provides a number of canned reports.
Report output columns can be included, excluded, and reordered by selecting
View > Column Layout. NetBackup reports can be exported as text or printed
exactly as displayed. Most reports can be filtered for selected content such as date/
time range, media server, client, or job ID.
The canned reports are described briefly as follows:
• Status of Backups displays the job error code and a related text description.
• Client Backups displays policy, schedule, elapsed time, number of files, and
number of kilobytes written.
• Problems is a subset of the All Log Entries report.
• All Log Entries provides comprehensive NetBackup severity and descriptive
information.
• Images on Media shows backup ID, file number on media, number of files,
number of kilobytes written, media ID or disk and media server that wrote the
backup.
• Media Logs presents the severity and a description for media issues,
identifying the client and the job ID.
• Tape Reports includes Images on Tape, Tape Logs, Tape Contents, Tape
Summary, Tape Written, and Tape Lists.
• Disk Reports includes Images on Disk, Disk Logs, Disk Storage Unit
Status, and Disk Pool Status.

• Vault reports includes reports for Vault sessions for which reports are already
generated. These include Media Going Off-site, Media Coming On-site,
Inventory, Container Inventory, Recovery, Lost Media, and Non-vaulted
Images.
3

3–7
NetBackup Administration Console: Media and Device Management
The NetBackup Administration Console provides the following Media and Device
Management utilities:
• The Device Monitor manages drives, device paths, and service requests for
operators.
• The Media branch enables the administrator to add and manage removable
media.
• The Devices branch enables the administrator to add, configure, and manage
storage devices.
• Under the Credentials branch, the administrator can add, remove, and manage
log on credentials for the following:
– NDMP hosts (requires the NetBackup for NDMP license)
– Storage servers (requires a NetBackup Deduplication Option or an
Enterprise Disk Option license)

Credentials appear only if one of these license keys is installed.

3
Accessing the NetBackup host properties
Location of NetBackup host properties

You can access most NetBackup settings using the Host Properties section of the
NetBackup Administration Console. Each of the component machines (the master
server, media servers, and clients) has its own set of properties.
UNIX
For UNIX servers, you can also configure NetBackup by editing the bp.conf
file at /usr/openv/netbackup/bp.conf and the vm.conf file at
/usr/openv/volmgr/vm.conf.
Note: The vm.conf file is not created until devices are added.
Some of the master server host properties correspond to bp.conf settings. Many
of the host properties related to the media servers correspond to vm.conf settings
on that particular host. The vm.conf file maintains Media Manager settings for
both UNIX and Windows servers.
NetBackup global attributes must be configured through the NetBackup
Administration Console or the command line.
NetBackup local attributes for the master, media, and client must be configured in
the bp.conf file on the respective machine.
Windows
In the Windows environment, attributes correspond to registry settings.

3–9
Configuring NetBackup host properties
Many properties can be changed so that your data protection solution performs
more effectively and efficiently.
As a NetBackup administrator, you can modify the host properties for any server
or client within your NetBackup environment from the master server. To access the
Host Properties from within the NetBackup Administration Console:
1 In the object tree pane, select NetBackup Management > Host Properties >
Master Servers.
2 Double-click the specific machine in the details pane, or right-click the specific
machine in the details pane, and select Properties.
To view the properties of a different master server, select File > Change
Server.

3
Master server host properties: Global Attributes
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.
For UNIX, the Global Attributes properties are stored on that master server in the
/usr/openv/netbackup/db/config directory. 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 Symantec NetBackup Administrator’s Guide for additional master
server properties.
NetBackup Administration Console vs. NetBackup-Java Administration

Console
As you have seen in this topic, the differences between the NetBackup
Administration Console and the NetBackup-Java Administration Console are
relatively minor. Throughout the remainder of this course, only the NetBackup
Administration Console will be shown, unless there are significant differences
between the two consoles.

3–11
Enabling administrative access from media servers
After completing this topic, you will be able to enable administrative access to the
NetBackup Administration Console from media servers.
Sample NetBackup 7.5 environment

The diagram on this slide shows a sample NetBackup 7.5 environment. The
servers related to enabling administrative access from a media server are described
in the following list.
• The master server is named winmaster. This server acts as a master, EMM,
and media server. It also acts as a client.
• One media server is named winserver. This server acts as a media server to
winmaster, a client, and a NetBackup OpsCenter server.
• Another media server is named winmedia. This server acts as a media server
to winmaster and as a client with MSDP.

3
Media servers configured as Additional servers
In this example, the winmedia and winserver servers are added to the winmaster
master server’s Server properties under the Additional servers tab. The Servers
properties display the NetBackup server list on the selected master server. The
server list displays the NetBackup servers that each host recognizes.
The Additional servers tab lists hosts that can remotely access the specified
Master Server. During installation, NetBackup sets the master server to the name
of the system where the server software is installed. NetBackup uses the master
server value to validate server access to the client. The master server value is also
used to determine which server the client must connect to so that files can be listed
and restored.

3–13
Changing the Administration Console to a different server
When the NetBackup Administration Console is initiated from a media server, you
need to change the server to access the console of the master server.
To do this:
1 Select the File > Change Server menu command in the NetBackup
Administration Console, or click the Change server button.
2 Enter or select the host name and click OK.

3
Accessing the NetBackup Administration Console from an Additional
server
In this example, the winmedia server is accessing the NetBackup Administration
Console. Because winmedia is listed under the Additional servers tab in the
Servers properties, this server has full access to the Administration Console
functions.

3–15
Media servers configured as Media servers
In this example, the winmedia and winserver servers are added to the winmaster
master server’s Server properties under the Media servers tab.
The Media servers tab lists the hosts that are media servers only. Hosts that are
listed as media servers can back up and restore clients, but have limited
administrative privileges.

3
Accessing the NetBackup Administration Console from a Media
server
In this example, the winmedia server is attempting to access the NetBackup
Administration Console. Because winmedia is listed under the Media servers tab
in the Servers properties, this server has no access to the Administration Console
functions.

3–17
NetBackup OpsCenter
OpsCenter is a Web-based software application that is designed to aid
organizations by providing visibility into their data protection environment. After
completing this topic, you will be able to navigate OpsCenter.
What is OpsCenter?
OpsCenter provides a single interface that can be used to monitor multiple
software applications and report on backup results and environmental conditions.
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.
OpsCenter replaces the NetBackup Operations Manager (NOM) and Veritas

Backup Reporter (VBR) software packages that were used with earlier versions of
NetBackup. The functionality of OpsCenter in its core form replaces all the
functionality of NOM and some of the functionality of VBR. This core form of
OpsCenter is available without an additional license. When run using the
optionally licensed OpsCenter Analytics option, OpsCenter completely replaces
NOM and VBR functionality.
Note: There is no direct upgrade path from NOM or VBR to OpsCenter 7.5.
NOM and VBR must be upgraded to OpsCenter 7.0 or 7.1 prior to
upgrading to OpsCenter 7.5. See the product documentation for details.

3
Accessing the OpsCenter console
To access the OpsCenter console, start a Web browser on a system that has
network connectivity to the OpsCenter server. Type the following URL: http://
host.domain/opscenter where host.domain 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: http://host.domain:8181/opscenter. For more
information, see the NetBackup OpsCenter Administrator’s Guide.
Logging into the OpsCenter Console

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 After the initial log on, change the user name and password. To change existing
passwords, use the Settings > User Preferences > MyProfile view in the
OpsCenter console.
3 Click Log On.
A monitoring overview of the NetBackup master servers is initially displayed.

3–19
The OpsCenter console components
The main sections of the OpsCenter console are:
• Tabs and sub-tabs
The main tabs provide access to the major areas of the OpsCenter console.
• Task pane windows
– The View pane is a key navigation and configuration tool in Symantec
OpsCenter. This pane enables you to select the views to control the scope
of your console views. ALL MASTER SERVERS is the default view in
the View pane.
– The Symantec ThreatCon pane displays the current ThreatCon level in
the OpsCenter console. This level is same as the ThreatCon level that is
shown on the http://www.symantec.com/
security_response/threatcon/ Web site.
– At the bottom of the Task pane, there are quick links that you can use to
access to the most common tasks in OpsCenter. These links include Oracle
Cloning, Alert Policies, NetBackup Data Collection, Views, and Users.
By default, the quick links are displayed in a maximized state. The
minimize or maximize settings are only applicable for the current session.
• The Content pane
Initially, the Content pane displays summary information for all master
servers in the OpsCenter console. Initially, a monitoring overview is displayed.
Subsequent logins display the last view you visited. The Content pane
information is context-sensitive to the current selections in the View pane, the
tabs and sub-tabs, and the time frame.
3
Configuring OpsCenter data collection for NetBackup
Before you can use OpsCenter to monitor and manage your NetBackup
environment, you must configure data collection for NetBackup. To do this, first
add a master server to the OpsCenter console as follows:
1 In the OpsCenter console, select Settings > Configurations > NetBackup.
2 Click Add.

3–21
Enabling data collection
To enable data collection for a master server, perform the following:
1 In the OpsCenter console, select Settings > Configurations > NetBackup.
2 Use the check box to select one or more master servers from the Network
Name column.
3 Click Enable Data Collection.

3
The OpsCenter console tabs
The OpsCenter console is the single, centralized monitoring and management GUI
console of OpsCenter. When you start the OpsCenter console to manage and
monitor your NetBackup environment, you open a connection to the OpsCenter
Web GUI.
This slide shows the sub-tabs under the Monitor, Manage, Reports, Search &
Hold, and Settings tabs on the OpsCenter console screen.You will have the
opportunity to explore these tabs in the lab for this lesson.

3–23
OpsCenter Analytics
Symantec 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 the creation of custom 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 how long reporting data
can be kept.
• With OpsCenter, you can create or edit data collectors for NetBackup,
NetBackup PureDisk, Backup Exec, and Enterprise Vault. With OpsCenter
Analytics, you can also configure data collectors for EMC NetWorker and
IBM Tivoli Storage Manager.
This course only covers OpsCenter. For additional information on using
OpsCenter Analytics, see the Symantec OpsCenter Administrator’s Guide and
Symantec Education’s OpsCenter training.
Note: In prior releases of OpsCenter, the Java View Builder was only available
with OpsCenter Analytics. In OpsCenter 7.5, the Java View Builder is
included with the base product.

3
3–25

Lesson 4
Configuring Tape Storage and Media

113

NetBackup storage device concepts
4
After completing this topic, you will be able to define the terms storage device,
storage unit, and storage unit group. You will also be able to identify the
NetBackup tape storage unit types.
Storage devices, storage units, and storage unit groups

It is important that you know the differences between storage devices, storage
units, and storage unit groups so that you can plan and configure NetBackup to
operate most effectively.
• Storage devices are tapes and disk devices (optical and magnetic) to which data
can be written and stored.
• Storage units are logical entities that consist of one or more storage devices of
a specific type. A storage unit is a component that you specify as part of a
policy definition. Properties of a storage unit also 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.
The order in which storage units are used within a group depends on how the
storage unit selection criteria is set. You may elect to use storage units in the
order in which they are displayed in the storage unit group dialog box, to use
each storage unit in turn, or to fail over to a different storage unit if the first
storage unit fails. This provides the ability to use a number of different storage
units in a group to ensure that the backups complete.
115 Lesson 4 Configuring Tape Storage and Media
4–3
Storage devices and storage units
A storage unit is a group of one or more storage devices of a specific type and
density that attach to a NetBackup server.
When backups 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 or archive, 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 (NBU1 or NBU2) and where the backups are written (LTO3 tapes in a
robotic library or a location on disk).
The media used can be removable or a directory on a hard disk. Removable media
can be in a robot or a stand-alone drive.

Shared tape drives (Shared Storage Option (SSO))
4
This diagram shows a NetBackup configuration where individual tape drives are
dynamically shared between multiple NetBackup media servers. Each media
server can access any of the shared drives as needed, and each server “owns” the
drives that it has active. The shared drives are automatically allocated and
deallocated as backup and restore operations dictate.
Symantec recommends using the Device Configuration Wizard, which is the
easiest method for configuring drives in a shared configuration. This wizard guides
you through the steps involved in configuring drives to be shared between device
hosts.
When you use the Device Configuration Wizard in a shared configuration, the
limitations, supported devices, and device hosts are different from those in a
configuration without shared drives. For robot types that are supported with the
Shared Storage Option (SSO), Symantec recommended that you use the Device
Configuration Wizard to add shared drives. In addition to configuring shared
drives faster, using the Device Configuration Wizard eliminates many common
mistakes made when shared devices are configured using alternate methods.
Note: On machines that use multipathing or NDMP, shared devices must be
configured using the Device Configuration Wizard.

4–5
Media Manager storage unit types
There are two media manager type storage units: Media Manager and NDMP.
• 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.

Tape storage unit layout example
4
This example shows that by grouping multiple drives into storage units, you
improve:
• Fault tolerance
• Concurrency (Multiple jobs can use multiple drives.)

4–7
Storage unit group example
This diagram shows the HQDataCenter group consisting of two storage units
prioritized as:
1 STU-A
2 STU-B
Because of the priority set for this storage unit group, backups are first directed to
STU-A. If STU-A is busy or out of service, backups are directed to STU-B.
Backups are never sent over the network to STU-C or STU-D because they are not
specified as part of the HQDataCenter group.
The second group, GlobalSites, consists of your UNIX-based and Windows-based
storage units prioritized as:
1 STU-B
2 STU-A
3 STU-C
4 STU-D
In this scenario, backups are first directed to STU-B. If STU-B is busy or out of
service, backups are directed to STU-A. If both STU-B and STU-A are
unavailable, the backup is directed over the network to STU-C. If STU-C is
unavailable, the backup is directed to STU-D.

Storage unit group configuration
4
Storage unit groups can be used to enable a backup policy to select from a specific
list of storage destinations rather than just one in particular or “any available”
storage unit.
In the Storage Unit Group dialog box, 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.
Media server load balancing: Server ranking

If multiple media servers are available for backup, NetBackup may choose the
server with the least load to perform the backup. This improves overall efficiency
and performance.
Rank assignments (0–3) are determined using an algorithm that considers the
number of active processes per CPU and the amount of available physical memory.
If the free memory drops below a determined threshold, or if the number of
running processes per CPU rises over a determined threshold, then the overall rank
of the media server drops. If a media server is engaged in memory swapping, or if
4–9
it is running an earlier version of NetBackup than the master server (for example, a
6.5 media server and a 7.0 master server), the media server’s rank is automatically
set to 0 (heavily loaded).
Media server load balancing cannot be selected for a storage unit group that
includes a BasicDisk storage unit. Also, a BasicDisk storage unit cannot be
included in an existing storage unit group with Media server load balancing
enabled.
Note: Note: The load balance option is only available when its required options
are licensed. The load balance option is not compatible with BasicDisk
storage units.

Storage unit group selection (1 of 2)
4
The order in which storage units are used within a group depends on the storage
unit selection option. The options shown in the slide are:
• Prioritized: Choose the first storage unit in the list that is not busy, down, or out
of media.
• Round robin: Choose the least recently used storage unit in the list.
• Failover: Choose the first storage unit in the list that is not down or out of
media.
In the first example, based on storage unit priority:
• Media1-SDLT is used for Jobs 1 and 2.
• Media2-SDLT is used for Jobs 3 and 4.
• Media1-SDLT will be used for Job 5.
In the second example, based on round robin:

• Media1-SDLT is used for Job 1.
• Media1-SDLT will be used for Job 5.
In the third example, based on failover:
Media1-SDLT is used for all jobs until it enters a DOWN state. At that point,
Media2-SDLT is used for all jobs until Media1-SDLT returns to an UP state.

4–11
Note: Failover does not occur when a storage unit is only busy. When the storage
unit is busy, the policy waits to write to it.
An exception to storage unit groups

An exception to storage unit groups exists if the client being backed up is a media
server with locally attached storage units. In this case, the locally attached storage
units take precedence over the defined sequence of storage unit groups.
Note: A fourth option selection within a storage unit group, load balancing, is
discussed later in this course.

Storage Unit group selection (2 of 2)
4
Media server load balancing
The fourth option is media server load balancing, which is shown in this slide.
After a server is ranked according to load, NetBackup attempts to choose a server
based upon specified criteria. If two or more servers share the best available rank,
NetBackup continues to apply additional criteria in the following order until one
media server remains:
1 Server rank: The server with the best rank
2 Fewest number of jobs: The server with the fewest jobs
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 may
have a rank of Idle. Of those three media servers, two may be running a single job
each. Of those two media servers, the server with the least amount of reserved
space is chosen.
Alternatively, if only one server has the best rank, that server is automatically
chosen.

4–13
Configuring tape devices
After completing this topic, you will be able to use the Device Configuration
Wizard to configure new tape devices.
Preparing for device configuration

Complete the following tasks before you configure devices:
1 Ensure that devices are correctly 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 nondrive-specific SCSI commands instead of blocking them. This
pass-through is required in order to handle the robot control commands.
3 Confirm that the devices are available through operating system tools.
4 After NetBackup is installed, use the following utilities as appropriate:

– Solaris: sgscan
– HP-UX: ioscan
– AIX: lsdev
– Linux: cat /proc/scsi/scsi
– Windows: Device Manager
5 If you see your devices with your appropriate utility, you are ready to configure
the devices using NetBackup. If you do not see the devices, troubleshoot the
problem using standard operating system tools until you can see the devices.

Storage device and storage unit configuration methods
4
Three interfaces are available for configuring storage devices and storage units:
• The Device Configuration Wizard
Use the NetBackup GUI to run the Device Configuration Wizard. The wizard
configures storage devices and storage units.
• The NetBackup Administration Console
Use the Media and Device Management interface to configure storage
devices and use the NetBackup Management interface to configure storage
units.
• The command-line or text-menu interface
Use the tpconfig and bpstuadd commands.

4–15
Configuring storage devices using the wizard
The Device Configuration 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 also discovers the positions of the
drives within the library.
In addition to providing a simple interface for NetBackup device configuration, the
wizard also provides the ability to customize drive naming rules, robot and drive
properties, SAN clients, and storage units.

The Device Configuration Wizard (1 of 4)
4
Symantec recommends that you use the Device Configuration Wizard to
configure robots and drives. The wizard configures a robot, its drives, and a
storage unit.
To configure robots and drives using the wizard:
1 In the NetBackup Administration Console, in the object tree pane, select the
name of the master server.
2 In the details pane, click Configure Storage Devices and follow the wizard
instructions.
The properties you can configure depend on the robot type, the host type, and the
robot control.

4–17
On this slide, you can see that the device hosts and the backup devices are
configured.

4
The Drag and Drop Configuration dialog box enables you to rearrange the drive
configuration, if necessary.
Click the Properties button in the Configure Storage Units dialog box to
configure storage unit properties.

4–19
When you click the Properties button in the Configure Storage Units dialog box,
the Change Storage Unit dialog box is displayed. In this example, the name of the
storage unit was changed.

Viewing drive properties
4
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.

4–21
Viewing robot properties
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.

Viewing Media Manager storage unit properties
4
storage units that were configured. To do this:
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.
In this example, notice that the Storage unit type is Media Manager. You can
also change the Media server field to Any Available, which is described on the
next page.

4–23
On demand only and any available
On demand only
When you configure a storage unit as On demand only, the storage unit is only
used if it is specified as an attribute in a policy or as an override storage unit within
a policy schedule.
If you select On demand only for all storage units, designate a specific storage
unit for each policy; otherwise, NetBackup is unable to find a storage unit to use.
Any available
If you do not specify a storage unit for your backup policy, your backup is directed
to any available storage unit. Any storage unit that is not flagged as On demand
only is available to any policy, either as an attribute or as an override storage unit
within a policy schedule.

If you select Any Available in the policy, 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 media available in the required volume pool.

NetBackup media concepts
4
After completing this topic, you will be able to describe volumes, volume pools,
and volume groups.
What are volumes?

Media Manager volumes are logical units of data storage or cleaning capability on
media (tapes or optical disks) that have been assigned media IDs and other
attributes, which are recorded in the EMM database.
You should know the following about volumes:
• A piece of media becomes a volume when Media Manager assigns a media ID.
• An application (such as NetBackup) requests volumes from Media Manager
using the media ID.
• The application (NetBackup) writes a label that matches the media ID.
Media Manager itself does not write anything to media, such as labels.
• An external volume serial number (EVSN) is an external reference to the
volume and is usually represented by a bar code label affixed to the volume
itself.
An EVSN can also be represented by a hard-copy label.
• A recorded volume serial number (RVSN) is a serial number that has been read
from a media header that NetBackup has physically written to the volume.
Note: The media ID is limited to six characters, and NetBackup only reads thirteen
characters on a bar code label.

4–25
To control how media IDs are created, define media ID generation rules that
specify which characters of a bar code on a tape are to be used in the media ID.
You can also specify alphanumeric characters to be inserted into the media ID.
Media ID generation rules are saved in the MEDIA_ID_BARCODE_CHARS
entry in the vm.conf file.
Multiple media ID generation entries can be specified, allowing media ID
generation to be specific for each robot, and offering flexibility for multimedia.
See the Symantec NetBackup Administrator’s Guide for details.

Media IDs
4
NetBackup assigns each volume a unique media ID. This media ID may be
assigned manually, or it may be automatically generated using bar codes.
Considering the large number of tapes in an enterprise backup environment, most
environments use bar codes. Manually assigning media IDs is only performed in
special circumstances, such as for stand-alone tape drives.
The maximum length of a media ID is six characters and is typically identical to
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 EMM database 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, Symantec
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 custom bar
code rules you configure in your production environment are also configured in
your disaster recovery environment.

4–27
What are volume pools?
NetBackup can draw volumes from a volume pool when performing backups.
The volume pool identifies sets of volumes whose use can be reserved for specific
backup jobs. The default pools have predefined uses. You can create other pools to
help you organize your backed up data.
NetBackup automatically creates the following volume pools:
• NetBackup: NetBackup is the default volume pool used for adding NetBackup
volumes.
• DataStore: DataStore is the default volume pool for integrated third-party
applications.
• CatalogBackup: CatalogBackup is the default volume pool used for storing
NetBackup hot, online catalog backups of policy type NBU-Catalog.
• None: None is the default volume pool for users of applications other than
NetBackup and Storage Migrator. None is also the pool where cleaning tapes
must be placed.

The scratch volume pool
4
The scratch pool is an optional volume pool that you can configure. You can have
only one scratch volume pool per NetBackup domain. If a scratch pool is
configured, Media Manager moves volumes from that pool to other pools that do
not have volumes available.
Media Manager does not assign volumes while they are in a scratch pool. For
example, if a NetBackup policy or schedule specifies the scratch pool, all requests
for those volumes are denied.
A volume moved from the scratch pool to another volume pool remains in the
other pool until it is unassigned. A feature of Media Manager moves volumes back
to the scratch volume pool after the volume is unassigned.
To disable this feature, update the EMM database using the following command:
nbemmcmd -changesetting
-return_unsigned_media_to_scratch_pool no
-machinename EMM_Host

4–29
Volume pools example
You assign media into logical sets of volumes called volume pools. You can use
volume pools to reserve media for specific NetBackup jobs.
NetBackup uses volume pools to set the order of precedence; that is, NetBackup
looks for media in a volume pool during a backup operation. For each backup
policy that you establish, you specify which volume pool NetBackup uses. If that
volume pool does not contain usable media (media that is at the retention level
required by the job and is not frozen, suspended, imported, or full), NetBackup
searches in the scratch volume pool (if you have established this volume pool) for
usable media.

Volume groups
4
A volume group is a logical group of volumes that are located at the same physical
location and that are used to easily track media.
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. If a volume is in the OFFSITE volume group, the volume is in a vaulted
media site.
Each robotic library has a pre-defined volume group with a name based upon the
robot number and robot type. If a volume is in a volume group, such as
000_00000_TLD, it is considered to be resident in the TLD0 library. When a
volume is resident, the robot automatically loads the resident volume for backup
and restore operations.
The following are the rules for assigning volume groups:
• 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).
• 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.
• The only way to clear a volume group name is to move the volume to stand-
alone and not specify a volume group.

143 Lesson 4 Configuring Tape Storage and Media Copyright © 2012 Symantec Corporation. All rights reserved.
4–31
• 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.
• All volumes in a group must be in the same robotic library or be stand-alone.
That is, you cannot add a group (or part of a group) to a robotic library if it
already exists in another robotic library.
Backup Exec differences

If you are familiar with Backup Exec terminology, here is a quick translation table:
General Term Backup Exec NetBackup
Tapes Media Volumes
Tape Sets Media Sets Volume Pools
Tape Location Media Location Volume Group

Volume groups and volume pools
4
Think of a volume group as a location and a volume pool as a collection of
volumes that are used for a similar purpose, such as:
• The same application and data for data separation
• The same operating system for simplicity
• The same department for ownership or security
A volume group enables you to logically move sets of volumes between robotic
libraries and non-robotic locations. There can be multiple non-robotic volume
groups, just as there can be multiple robotic libraries, such as Robot 1 and Robot 2
in the slide on this page. Delete volumes from the EMM database by specifying the
group name, rather than individual media IDs.
Multiple volume pools can share the same location. For example, a robotic library
may contain volumes from multiple volume pools.

4–33
Configuring media
After completing this topic, you will be able to use the Volume Configuration
Wizard and Robot Inventory to configure new media.
Volume configuration methods

You must configure volume pools before you can configure volumes. The three
interfaces that are available for configuring volumes are:
• The Volume Configuration Wizard or Robot Inventory
You can use the Volume Configuration Wizard or Robot Inventory to
perform the following tasks:
– Inventory your robots.
– Identify cleaning media in your robots.
– Add volumes for stand-alone drives.
– Update the Enterprise Media Manager (EMM) database.

After you run the wizard or utility to configure media, each piece of media has
a unique media ID in the EMM database that is used by Media Manager and
NetBackup to track media. The wizard or utility creates media that have a
media type determined by the drive type. The default media type is used.
• The NetBackup Administration console
Use the Media and Device Management interface to configure volumes.
• The command-line or text-menu interface
The slide lists the commands that are available to perform volume
configuration tasks.

Preparing to run the Volume Configuration Wizard
4
The table on this slide describes tasks that need to be performed either before or
during the Volume Configuration Wizard. 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 the
EMM database. For any media that was added to the EMM database before the
rules were created, either manually update the media or delete the media and rerun
the robot inventory. Then, the rules can 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 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. Using the robot inventory enables accurate
tracking of volume locations. To determine which volumes are in a robot and their
exact slot location, perform a robot inventory update.
Media ID generation rules enable you to override the default media ID naming
method that NetBackup uses. The default method uses the last 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.

4–35
Adding the scratch volume pool
You can manually configure a volume pool using the NetBackup Administration
Console:
1 In the NetBackup Administration Console, select Media and Device
Management > Media.
2 Perform one of the following:
– Select Actions > New > Volume Pool (Java) or select Actions > New >
New Volume Pool (Windows).
– Right-click Volume Pools and select New Volume Pool (Java) or select
New (Windows).
The Add a New Volume Pool (Java) or the New Volume Pool (Windows)
dialog box is displayed.
Adding a new volume pool

Four pools are automatically created when NetBackup is installed: NetBackup,
DataStore, CatalogBackup, and None. It is also a good practice to create a separate
pool for duplicates of backups. Options in the Add a New Volume Pool (Java) or
New Volume Pool (Windows) dialog box include:
• Media Manager host: This field displays the name of the Media Manager host
machine that should be the EMM server.
• Pool name: Enter a unique volume pool name; it can be up to 20 alphanumeric
characters long and is case-sensitive.
• Description: Enter a brief description of the volume pool.

• Maximum number of partially full media: NetBackup writes data only to
the specified number of partially full media. When the number is reached,
NetBackup queues backup jobs until media becomes available. If a volume
becomes full, NetBackup assigns a new volume to replace it.
The default number (0) does not limit the number of full media in the pool.
• Host name: ANYHOST is the default, enabling any host to access volumes in
this pool. This field is only active if the Permit only the specified host to
access volumes in the pool check box is marked.
Symantec recommends that you do not specify a host. Allowing ANYHOST
(default) is recommended. Never specify the name of a client as a host.
• Scratch Pool: Mark the check box if this is the scratch pool. After defining the
scratch pool, add volumes to the scratch volume pool for media types that may
need them.
• Catalog backup pool (Java) or Catalog Backup (Windows): Mark this check
box if this volume pool is to be used for hot, online backups of the NetBackup
catalog. Marking this check box creates a dedicated catalog backup pool to be
used for NBU-Catalog policies. A dedicated catalog volume pool facilitates
quicker catalog restore times. Multiple CatalogBackup volume pools are
permitted.
4

4–37
The Volume Configuration Wizard (1 of 7)
The easiest way to add volumes is to use the Volume Configuration Wizard.
Symantec recommends that you use either the Volume Configuration Wizard or
the Robot Inventory option to add volumes. NetBackup assigns media IDs and
labels the volumes automatically. Be careful when you specify properties. You
cannot change some properties later, such as the media ID or type. If you specify
them incorrectly, you must delete the volume and add it again.
To configure volumes by using the wizard:
1 In the NetBackup Administration Console, in the object tree pane, expand
Media and Device Management > Devices.
2 From the list of wizards in the details pane, click Configure Volumes and
follow the wizard instructions.
To access the Robot Inventory option:

Media and Device Management > Media.
2 On the Actions menu, select Inventory Robot.
The following pages describe the Volume Configuration Wizard.

4
In the Select Device dialog box, you select the device whose volumes you want to
configure. Select the robot you want to inventory and click Next.
In the Specify if Multiple Drive Types Exist dialog box, you specify whether the
robot has more than one drive type. Select the appropriate radio button and click
Next.

4–39
The Robot Inventory dialog box is now displayed. Click Next to start the robot
inventory. To run the Robot Inventory utility, click Advanced Options. The
Robot Inventory utility now starts.
Robot Inventory: Advanced Options

The Update volume configuration function inventories the selected robot and
compares the results with the contents of the EMM database. If there are
differences, Media Manager updates the database to match the contents of the
robot.
Updating the volume’s configuration information is useful after performing one of
the following tasks:
• Removing existing volumes from a robot
• Inserting new or existing volumes into a robot

• Physically moving existing volumes within a robot
• Physically moving volumes between a robotic device and a stand-alone device
• Physically moving volumes from one robot to another
In addition, in this step, you can define update options and set up bar code rules for
the robotic device with the bar code reader.
1 Select the Update volume configuration radio button.
2 If you want to change the update options, click Advanced Options.
The Advanced Robot Inventory Options dialog box is displayed.

4
Advanced Options: Media Settings tab
A volume group is a physical location for media. Volume groups manage groups of
tapes together for the purpose of administrative action that allows movement,
modification, and deletion of tapes in groups.
Under the Media Settings tab, you can specify the volume group for existing
media and specify media options for new media.
Complete the Advanced Robot Inventory Options Media Settings tab as
follows:
• Media which have been removed from the robot should be assigned to the
volume group
This property specifies the volume group that Media Manager assigns to
existing media that you have removed from the robot.

If the volume group is set to DEFAULT and there is an existing group with a
compatible residence for the volume, then the volume is added to that group. A
compatible residence has the same robot type, robot number, robot host, and
media type (DLT and DLT_CLN are considered equivalent in this regard). If a
suitable volume group does not currently exist, Media Manager generates a
new volume group name.
To change from DEFAULT, specify a new volume group name or select a group
from the list. The selection list always has the following choices:
– DEFAULT: Allow Media Manager to select the volume group.
– AUTO-GENERATE: Automatically generate a new volume group.
4–41
– NO VOLUME GROUP: Do not assign a volume group.
In addition, if the media type is DEFAULT, the list shows existing volume
groups that are valid for the robot’s default media type. If the media type is
not DEFAULT, the list shows the existing volume groups that are valid for
the specified media type.
• Media which have been moved into or within the robot should be assigned
to the volume group
This property 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.
If you leave the volume group set at DEFAULT and there is an existing group
with a compatible residence for the volume, the volume is added to that group.
If a suitable volume group does not exist, Media Manager generates a new
volume group name.
To change from DEFAULT, specify a new volume group name or select a group
from the list. The selection list always has the following choices:
– DEFAULT: Let Media Manager select the volume group.
– AUTO-GENERATE: Automatically generate a new volume group.
In addition, if the media type is DEFAULT, the list shows existing volume
groups that are valid for the robot’s default media type. If the media type is
not DEFAULT, the list shows the existing volume groups that are valid for
the specified media type.
Note: If the robot contains multiple media types, it is better to leave the
volume group setting as DEFAULT. If you specify a volume group and
volumes of different media types have been moved into or within the robot
since the last update, the new updates fail. This failure is because volumes of
differing media types cannot have the same volume group.
• Use the following Media ID prefix
Specify a media ID prefix if either of the following conditions exist:
– The robot does not support bar codes.
– The volume that was inserted does not have readable bar codes.
If the robotic library supports bar codes and the volume has readable bar codes,
a prefix is not required because Media Manager creates the media ID in one of
the following ways. This is true whether or not a bar code rule is used.
– By default, Media Manager assigns the last six characters of the bar code as
the media ID.
– You specify specific characters for the media ID using Media ID
generation rules. See the “Advanced Options: Media ID Generation”
section of this topic for more information.
• Label optical media (local host only):

Label optical media (local host only) is enabled only if you selected an
optical robot to inventory. The media labeling is only performed if the robot is
attached to the local host that is specified during the NetBackup Java login.
The media is labeled but is not formatted.
• Use barcode rules
Use this check box to specify whether you are using bar code rules for new
media:
– Mark the check box to cause Media Manager to search existing bar code
rules and apply the rules to new volumes that have been inserted into a
robot.
– Clear the check box to cause Media Manager to ignore bar code rules.
• Media type
Use Media type to specify the media type for new media that is being added to
a robot. The list displayed shows the media types that are valid for the robot.
See the Symantec NetBackup Administrator’s Guide for instructions on how to
select the Media type based on whether bar code rules are being used.
Note: Media type is not available for API robots (for example, an ACS robot)
because media type is always set to DEFAULT for API robots.
• Volume pool
The default volume pool is defined by the bar code rules, if they are being
4
used. Otherwise, the default is the NetBackup volume pool for data volumes
and the NONE volume pool for cleaning tapes.
If you have set up a scratch pool, you can set the default pool to be the scratch
pool. Tapes are moved from the scratch pool to the volume pool that is
specified in the backup policy as needed.

4–43
Advanced Options: Barcode Rules tab

A bar code rule specifies criteria for assigning attributes to new robotic volumes.
The attributes are assigned according to the bar code label that is read by the
robotic library. You choose whether to use bar code rules when you assign media
settings.
If your robotic library has a bar code reader and you want to establish bar code
rules, click the Barcode Rules tab and click New. The Add a New Barcode Rule
(Java) or New Barcode Rule (Windows) dialog box is displayed.
Select the options for your new bar code rule as follows:
• Barcode tag
A bar code tag can have a maximum number of characters, depending on the
robot type. In the EMM database, not all characters for the tag are used for all
robot types. You cannot use spaces or special characters that are represented as
spaces.
The following table identifies the maximum bar code length for the associated
robot type:
Robot type Maximum bar code length

ODL, TL4, TSH No bar code capability
ACS, TLH, TLM 1–6 character bar code
TL8, TLD 1–16 character bar code

The following rules can have special characters in the bar code tags:
Rule Explanation
<NONE> Volumes with unreadable bar codes or robots that do not support bar
codes are matched to this tag when bar code rules are in effect.
<DEFAULT> Bar coded volumes that do not match other bar code tags are matched
to this special tag. This is contingent upon the media type in the
<DEFAULT> rule and the media type on the Update Options tab
being compatible. If these media types are not compatible, the volume
is matched to the <NONE> tag.
• Maximum cleanings (Java) or Cleanings (Windows)

Specify the maximum number of mounts or cleanings that are allowed for this
volume. When a bar code rule is used, Media Manager adds the number you
select to the EMM database for the media ID.
For media other than cleaning tapes, select the maximum number of mounts to
allow. Zero indicates unlimited mounts. For cleaning tapes, select the number
of cleanings to allow.
• Media type
Select the media type from the drop-down menu for this bar code rule. Ensure
that the type you select matches the media type exactly.
4
• Volume pool
Select a volume pool for the volume. This is the pool in which the volume is
placed when a bar code matches the rule. If the bar code rule is used and the
Media Settings tab shows DEFAULT for the volume pool, the volume is
assigned to the pool you specified in the bar code rule. If the Media Settings
tab shows a specific volume pool, that selection overrides the pool you
specified in the bar code rule.
• Description
Enter an optional description (up to 25 characters) for the bar code rule. This
can be a description of how the bar code rule is used, or any useful description.

4–45
Advanced Options: Media ID Generation tab

Media ID generation rules enable you to override the default Media Manager
media ID naming method. The default method uses the last six characters of the
bar code label that are returned by the robot to generate the media ID. You can
control how media IDs are created by defining Media ID generation rules that
specify which characters of a bar code label are used for the media ID.
For example, two eight-character bar codes may be S00006L1 and 000006L1. If
you do not specify any media ID generation rules, the same media ID for the two
bar codes is created from the right-most six characters of the bar code.
To establish media ID generation rules, click the Media ID Generation tab and
click New.
Specify the properties for the new media ID generation rule as follows:
• Robot number
Click an arrow and select a robot number to which to apply this rule.
• Bar code length
Click an arrow and select the length of the bar code for tapes in this robotic
library and for this rule.
• Media ID generation rule

Enter a generation rule for media IDs. A rule consists of a maximum of six
fields that must be delimited by colons. Numbers in the fields of the rule define
the positions of the characters in the bar code that are to be extracted. For
example, 2 in a field extracts the second character from the bar code (The
numbering is done from the left). The numbers can be specified in any order.
Characters prefixed by # in a field result in that character being inserted in that
position in the generated ID. Any alphanumeric characters that are specified
must be valid for a media ID.
Potential conflict with media IDs

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.
4
Two possible solutions are:
• Order tapes that have unique bar code labels.
• Color-code your bar code labels.

4–47
Robot Inventory: Update volume configuration

After you have set any advanced options, you are ready to update the volume
configuration.
Ensure that the Update volume configuration radio button is selected and click
Start. Results are displayed in the Results field, and changes are written to the
EMM database.
When the update completes, click Close and the Finished! screen is displayed.

Summary of Robot inventory utilities
4
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.
Note: The first three rows in the table on this slide do not modify the volume
database.

4–49
Verifying tape storage
After completing this topic, you will be able to monitor devices and media using
the NetBackup Administration Console.
Verifying devices using the Device Monitor

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.
Note: If the Media Manager Device daemon (ltid) is not running on the host
being monitored, the lists in the Device Monitor details panes are blank.

Drive details
4
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 vmoprcmd command

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]

4–51
Viewing all media
Select Media and Device Management > Media to display all media in your
environment. Notice the Volume Pool and Volume Group columns.
To display the volume pools and volume groups using the command line, enter the
following commands:
vmquery -a
nbemmcmd -listmedia -allrecords -brief

4
4–53

Lesson 5
Configuring Disk Storage

167

NetBackup disk storage types
After completing this topic, you will be able to describe disk-based storage and
how it is used, and compare basic disk, AdvancedDisk, and deduplication pools.
Disk storage terminology

This slide describes basic disk backup terminology.
5
• 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 enclosure is a physical container with disk storage, such as a disk array.
• 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. With the advent of OpenStorage technology in NetBackup, there are
instances where the storage to which backups are written is not managed
directly by the media server. This has led to the creation of an entity referred to
as the storage server.
In some cases, such as NetBackup AdvancedDisk, the storage server and the
media server reside on the same NetBackup system. However, in other cases,
the NetBackup media server communicates with a storage server provided by
Symantec or another storage vendor using NetBackup OpenStorage
technology. The storage server writes the data to and reads the data from the
disk storage.

169 Lesson 5 Configuring Disk Storage
5–3
Disk storage types
The graphics on this slide describe the various disk-based storage unit types:
• The BasicDisk disk type consists of a directory on a locally-attached disk or a
network-attached disk that is exposed as a file system to a NetBackup media
server. NetBackup stores backup data in the specified directory.
• An AdvancedDisk disk type is used for a dedicated disk that is directly
attached to a NetBackup media server. An AdvancedDisk selection is available
only when the Flexible Disk Option is licensed.
NetBackup assumes exclusive ownership of the disk resources that comprise
an AdvancedDisk disk pool. The NetBackup media servers function as both
the data mover and the storage server.
• There are two types of PureDisk storage units: Media Server Deduplication
Pool (MSDP) and PureDisk (PDDO).
– For the MSDP type, the media server or the client deduplicates the data and
then sends the deduplicated data to a disk pool associated with that media
server. The NetBackup media server functions as both the data mover and
the storage server.
– For the PureDisk type, the media server deduplicates the data and then
sends the deduplicated data to the PureDisk environment. The NetBackup
media server functions as the data mover, and the PureDisk Storage Pool
Authority (SPA) functions as the storage server.
• The OpenStorage disk type is used for disk storage, usually provided by a
third-party vendor. The actual name of the disk type depends on the vendor. An

OpenStorage selection is available only when the OpenStorage Disk Option is
licensed.
The storage is integrated into NetBackup through an API. The storage vendor
partners with Symantec to integrate the storage into NetBackup. The storage
host is the storage server. The NetBackup media servers function as the data
movers. The storage vendor's plug-in must be installed on each media server
that functions as a data mover.
• SnapVault is used to store images on Network Attached Storage (NAS)
devices. The NetBackup media server functions as the data mover. The
SnapVault is the storage server. The SnapVault is available only when the
NetBackup Snapshot Client option is licensed.
5

5–5
Disk backup methods
The table on this slide describes the main disk backup methods.
• BasicDisk: This disk type defines a specific directory as a backup destination
on a single media server. BasicDisk enables basic disk staging operations and
spanning between storage units.
• AdvancedDisk: This disk type defines a collection of disk volumes as a backup
destination on a single media server. Under this configuration, NetBackup
assumes exclusive ownership of the backup destination. AdvancedDisk can be
used with intelligent capacity management, media server load balancing, data
classifications, and advanced disk staging. An AdvancedDisk pool can be
shared among multiple media servers. However, a shared file system, such as
Network File System (NFS) or the Symantec Storage Foundation Cluster File
System (CFS) must be used.
• MSDP (Media Server Deduplication Pool): This disk type is a NetBackup

media server that is configured to manage an embedded deduplication storage
pool. The media server can be one of a number of supported operating systems,
with storage that serves as the deduplication storage pool.
• PDDO (PureDisk Deduplication Option): This disk type is a plug-in that uses
the NetBackup OpenStorage API to enable NetBackup to write backups to a
PureDisk storage pool. All the data that is written to a PureDisk storage pool is
deduplicated by the NetBackup client or media server. The major difference
that PDDO offers over MSDP is global deduplication.
• OpenStorage: This disk type is a NetBackup API that enables NetBackup to
communicate with intelligent disk appliances. Disk appliances typically are the

hardware and the software solutions that include a host computer and the
storage. Disk appliance vendors provide the storage, and they provide a
software plug-in that you install on NetBackup media servers. The NetBackup
media servers use the plug-in to communicate with the disk appliance.
5

5–7
Configuring a basic disk storage unit
After completing this topic, you will be able to configure a basic disk storage unit
and describe the benefits of a Disk Staging Storage Unit (DSSU).
Adding a basic disk storage unit

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 Symantec NetBackup
Commands Reference Guide.

The Disk storage unit type
When creating a Disk storage unit type, you must supply the following properties:
• Storage unit name
Type a unique name for the new storage unit that describes the type of storage
you are defining. This is the name to use when specifying a storage unit for
policies and schedules.
5
• Storage unit type
The Storage unit type setting specifies the type of storage that this storage
unit uses. In this example, the storage unit type is Disk.
• On demand only
On demand only specifies whether the storage unit is available exclusively on
demand, that is, only when a policy attribute or policy schedule is explicitly
configured to use this storage unit.
Clear the On demand only check box to make the storage unit available to any
policy attribute or policy schedule that specifies Any Available as its
destination.
• Disk type
The Disk type field specifies the type of disk storage unit to be created. By
default, a disk storage unit is configured as BasicDisk. The following
specialized options are also available, depending on licensing and the
NetBackup configuration: AdvancedDisk, NearStore, OpenStorage, PureDisk,
and SharedDisk.

5–9
• Properties and Server Selection (Java) or Storage unit properties
(Windows)
– Media server
The Media server setting specifies the name of the server that is
controlling the disk storage unit.
When configuring a disk storage unit, select a single media server.
– Absolute pathname to directory
This specifies the absolute path to the file system or a volume available for
disk backups. Enter the path directly in the field. Use any location on the
disk, providing there is sufficient space available. Click the Browse button
to navigate to the directory location.
– View Properties button
Click View Properties to display information about the capacity and
remaining space on the volume.
– This directory can exist on the root file system or system disk
Mark this check box if it is acceptable for the directory being created in the
Absolute pathname to directory field to exist on the root file system or
system disk. Enabling this setting allows backups to the root file system,
possibly causing the root file system to fill up. Enabling this setting allows
the directory to be created automatically, even when the specified directory
resides in the root file system.
– Maximum concurrent jobs
For disk storage units, this property specifies the maximum number of
backups that NetBackup can concurrently send to this disk.
For example, if there are three backup jobs for this storage unit and this
property is set to two, the first two jobs start, and the third job waits.
– Reduce fragment size to
This field specifies (in megabytes) the largest fragment that NetBackup can
create when storing backups.
For disk storage units, the default maximum fragment size is 524,288
megabytes. This value can range from 20 to 524,288 megabytes.
This setting is normally used to ensure that the backup does not exceed the
maximum file size allowed by the file system.

– High water mark
The High water mark setting is a threshold that, when reached, signals to
NetBackup that the disk storage unit should be considered full. The default
value is 98%.
NetBackup does not assign a new job to a storage unit that is considered
full; however, active backups that exceed the water mark are allowed to
complete. After the capacity of the storage unit is below the High water
mark, jobs can again be assigned to the storage unit.
– Low water mark:
When a disk storage unit with staging enabled becomes full, images that
have already been duplicated to a final storage unit are purged from the
disk. These images are purged until the total disk capacity falls below the
Low water mark.
5

5–11
Basic disk staging
Basic disk staging 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. The media type for the final destination is typically tape, but can also
be disk.
This three-stage process enables the NetBackup administrator to use the
advantages of disk-based backups in the near term, while preserving the
advantages of tape-based backups for the long term.
Basic disk staging meets the following objectives:
• Allows backups when tape drives are scarce
• Allows for faster restores from disk
• Facilitates streaming to tape without image multiplexing
Basic disk staging is conducted in three separate operations:

1 In the first step of disk staging, clients are backed up by a policy that specifies
a disk staging storage unit as the destination storage unit. The storage unit
should contain one dedicated disk partition/file system for each disk staging
storage unit. The schedule for Stage I is configured like any other backup.
2 In the second step of disk staging, images are copied from the disk staging
storage unit to the final destination storage unit. The images are duplicated
based on the relocation schedule configured during the disk staging storage
unit setup.
3 The third stage is deletion. The image continues to exist on both the disk
staging storage unit and the destination storage unit. File restores are
performed from the disk staging storage unit copy, while the destination
storage unit copy can be considered the long-term copy. The image copy
continues to exist on the disk staging storage unit until either the image expires
or another staging operation requires the disk space. When a Stage I process
detects a full disk staging storage unit, it pauses the backup, finds the oldest
images that have been successfully copied to the destination storage unit, and
expires this image copy.
5

5–13
Temporary staging area
If this storage unit is to be used for staging data to disk, 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.
Disk storage units configured for staging require a staging schedule, which is
configured by clicking the Staging Schedule button.

Disk staging schedule attributes
Clicking the Staging Schedule button opens the Add Schedule–Disk Staging
dialog box. This dialog box is similar to the scheduling dialog box seen when
configuring policies; however, this dialog box does contain some differences:
• Name
The schedule name for a disk staging storage unit defaults to (and is required to
5
be) the name of the storage unit.
• Priority of duplication jobs for this schedule (Java) or Priority of
relocation jobs started from this schedule (Windows)
This attribute specifies the priority that NetBackup assigns to duplication or
relocation jobs for this policy. The range is from 0 (default) to 99999 (highest
priority).
• Final destination storage unit
The Final destination storage unit is the name of the storage unit where the
images are copied from the disk staging storage unit.
• Final destination volume pool
The Final destination volume pool is the name of the volume pool on the
final destination storage unit where the images are to be copied.
If the Final destination storage unit is a Media Manager storage unit (tape),
or if Any Available is indicated for the Final destination storage unit, the
Final destination volume pool is selectable.
• Final destination media ownership (Java) or Final destination Media
owner (Windows):

5–15
This field specifies the owner of the backup images after the relocation
process. The following options are available:
– Any: NetBackup chooses a media server.
– None: The media server that writes the image to tape owns the media.
– A server group: If any server groups are configured, one can be selected to
own the images.
• Use alternate read server
The Use alternate read server attribute applies to NetBackup Enterprise
Server only.
An alternate read server is the server to be used to read a backup image that
was originally written by a different media server. Mark this check box to use
an alternate read server.
The path to the disk or directory must be identical for each media server that is
to access the disk. To avoid sending data over the network during replication,
specify an alternate read server that is:
– Connected to the disk backup location with the source images
– Connected to the tape storage used for the destination
Symantec 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.

Configuring AdvancedDisk
After completing this topic, you will be able to configure storage servers,
AdvancedDisk pools, and AdvancedDisk storage units.
Advantages of pooling disk resources

Creating disk pools in NetBackup offers several benefits over standard disk
5
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.

5–17
AdvancedDisk disk pools
An AdvancedDisk disk pool enables several disk volumes to be combined into one
logical storage destination in NetBackup. The AdvancedDisk pool is accessed by a
single storage server, which must also be a NetBackup media server. Disk volumes
that are contained in an AdvancedDisk pool may exist across multiple physical
disk arrays or internal storage disk volumes on a storage server. This is unlike a
BasicDisk storage unit, which is limited to a single directory.
Generally, it is most efficient to pool the disk resources that are available to a
server into a single pool. However, Symantec recommends placing disk volumes
of significantly different sizes or speeds into separate pools.
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 single
disk volume cannot exist in more than one disk pool.
Spanning within a 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 one
enclosure (disk array) to another, or, for example, from external to internal storage.

By design, 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. However, other storage unit
group features, such as failover, do apply between pool-based storage units.
5

5–19
AdvancedDisk configuration overview
The slide on this page provides an overview of the steps involved to configure a
usable disk pool and corresponding AdvancedDisk storage server. You will learn
how to perform each of these steps on the following pages.

Configuring disk storage servers using the wizard (1 of 4)
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 is located at:
5
• UNIX: /usr/openv/netbackup/bin/admincmd
• Windows: install_path\bin\admincmd

5–21
1 On the Welcome screen, click Next to continue.
2 From the Select the type of disk storage to configure drop-down list, select
AdvancedDisk and click Next.

3 Select the media server from the drop-down list and click Next.
4 Confirm the storage server configuration summary and click Next to start the
configuration process.
5

5–23
5 After the wizard completes the creation of the storage server, click Next.
6 The storage server is now created. Click Next to configure a disk pool or click
Close to close the wizard.

Creating a disk pool using the wizard (1 of 5)
The Disk Pool Configuration Wizard is automatically started 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 (Java) or select New (Windows). The Disk Pool
5
Configuration Wizard is displayed. You may also access the Disk Pool
Configuration Wizard by clicking the master server in the Administration
Console.
Unlike other elements of NetBackup configuration that also offer a manual
configuration, the Disk Pool Configuration Wizard is the only way to configure
a new disk pool from the Administration Console.
No disk pools exist by default.
You may also use the nbdevconfig command to configure a new disk pool
from the command line.

5–25
1 Select the type of disk pool to create. If no disk types are listed, verify that the
storage server was created. In this example, AdvancedDisk is selected.
2 Select a storage server to associate with the disk pool. The storage server must
have physical access to the disk storage to be used. This is true for both internal
disk storage and disk arrays over a SAN. In this example, only one storage
server is selected because AdvancedDisk is being configured.

3 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.
4 Configure the properties of the disk pool. Assign a name to the pool and
5
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: 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

5–27
5 Confirm the disk pool configuration summary and click Next to start the
configuration process.
6 When the disk pool configuration completes, click Next to continue.

7 Configure the properties of the storage unit for this disk pool.
Notice that the name of the storage unit is advdisk1_stu_winmaster, in this
example. If you have chosen to create a storage unit within the disk pool, this
screen is presented to configure its properties. In most cases, you must increase
the Maximum concurrent jobs setting from the default setting of 1.
5
A Media Server option is available to limit the storage unit to specific media
servers.
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.
8 The disk pool configuration is complete. Click Finish.

5–29
Verifying disk storage
• Monitor the status of configured devices.
• View reports for configured devices.
Verifying the storage servers

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.

Verifying the disk pools
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.
5

5–31
Viewing disk pool status
To view the status of your disk pools, select Media and Device Management >
Device Monitor and click the Disk Pool tab (Java) or the Disk Pools tab
(Windows). In the example on this page, you can see that the status of all disk
pools is Up.

Viewing the AdvancedDisk storage unit
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 Administration Console does
not list BasicDisk storage servers because all media servers support BasicDisk, by
default. Also notice that the advdisk1_stu_winmaster AdvancedDisk storage unit
5
is displayed with a Storage Unit Type of Disk.

5–33
Lesson 6
Configuring File System Backups

201

Introduction to backup policies
After completing this topic, you will be able to explain how data protection relates
to a policy.
What is your backup plan?

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 in the Policies utility.
Include the following tasks in your planning and preparation.
1 Gather client information.
2 Group the clients based on backup requirements.
6
3 Consider the storage requirements.
4 Consider the backup schedule.
5 Group clients by common attributes.

6 Maximize multiplexed backups.
7 Evaluate backup times.

203 Lesson 6 Configuring File System Backups Copyright © 2012 Symantec Corporation. All rights reserved.
6–3
NetBackup policies–the heart and soul of NetBackup
NetBackup policies define the rules that NetBackup follows when backing up
clients. A policy can contain one or more clients, and every client must belong to
at least one policy. The best approach to setting up policies is to divide clients into
groups according to their backup and archiving requirements, and then create
policies as appropriate for each group. NetBackup does not limit the number of
policies that you can configure.
Policies answer the questions shown on the slide with regard to backup jobs, using
the tabs across the top of the policy’s dialog box.
• The Attributes tab
How is the policy to be backed up? Where are the storage units and volume
pools to which the backup data is to be sent? What are the characteristics of the
backup?
These questions are answered by the Attributes tab. General attributes

determine the basic characteristics of all the backups that NetBackup performs
for the policy.
• The Schedules tab
When will the backup take place? Daily? Weekly? Monthly? Or perhaps on a
specific day every month?
This is answered in the policy’s schedule settings under the Schedules tab.
Schedules control the backups for the policy.
• The Clients tab
Which client is to be backed up?

This is answered in the policy’s client list under the Clients tab. The client list
names the computers that belong to the policy. NetBackup backs up these
computers according to the backup selections, schedules, and general attributes
for the policy.
• The Backup Selections tab
Which files on the clients are to be backed up?
This is answered in the policy’s backup selections list under the Backup
Selections tab. The backup selections name the files and directories that
NetBackup includes in automatic backups for clients in this policy.
6

6–5
Configuring file system backup policies
After completing this topic, you will be able to configure a policy that backs up
files in a file system using the Policy Configuration Wizard.
Policy configuration methods

This slide identifies the methods for creating policies.
• The Policy Configuration Wizard
Use the NetBackup GUI to run the Policy Configuration Wizard. This wizard
quickly defines the schedules and settings for backing up one or more clients,
snapshots, or virtual machines.
• 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. This method is not recommended. For
information about the bppolicynew command, see the Symantec NetBackup
Commands Reference Guide.

Creating a policy using the wizard (1 of 6)
The easiest method to set up a backup policy is to use the Policy Configuration
Wizard. This wizard guides you through the setup process by automatically
choosing the best values for most configurations.
Not all policy configuration options are presented using the wizard. For example,
calendar-based scheduling and the Data Classification setting are not available.
After the policy is created, modify the policy in the Policies utility to configure the
options that are not part of the wizard.
Use the following procedure to create a policy using the Policy Configuration
Wizard.
1 In the NetBackup Administration Console, in the object tree pane, select the
6
master server.
2 In the details pane, click Create a Policy to begin the Policy Configuration
Wizard.
Click Help on any wizard panel for assistance while running the wizard.

6–7
3 Select the type of policy to create and click Next.
The choices are:
– A policy to back up file systems, databases, or applications
– A policy to create snapshots
– A policy to protect VMware or Hyper-V virtual machines
– A policy to back up NDMP hosts
In this example, a policy for a file system backup is being created.
4 Enter the policy name, select the policy type, and click Next.
The choices for policy type are:
– MS-Windows
– NBU-Catalog
– NDMP
– NetWare
– Oracle
– OS/2
– PureDisk-Export
– SAP
In this example, MS-Windows is selected.

5 To select the clients to back up with this policy, click Add.
Notice the Detect operating system when adding or changing a client check
box. If this box is not marked, you need to select the appropriate hardware and
operating system from the list. Ensure that you only add clients with the
hardware and the operating system that the policy supports. For example, do
not add a Novell NetWare client to an MS-Windows policy.
After you have added the clients, click Next.
6 To specify the files and folders to back up, click the Add button.
6

6–9
In this example, G:\data\smallfiles is selected to be backed up.
7 Click OK to return to the Policy Configuration Wizard Files dialog box and
click Next.

8 Select the backup types to include in this policy and click Next.
The default is to create a full backup schedule and an incremental backup
schedule.
9 Select the backup frequency and image retention period and click Next.
6

211 Lesson 6 Configuring File System Backups
6–11
10 Specify the backup window and click Next.
11 Your policy is now complete. Click Finish to save the policy.

Viewing and editing a policy
• View and edit an existing policy.
• Describe the types of schedules in a policy.
Viewing a policy using the NetBackup Administration Console

The easiest way to view and edit policies is by using the Policies utility in the
NetBackup Administration Console. To run the Policies utility:
NetBackup Management > Policies.
2 Within the Policies utility, you can perform the following tasks:
6
– To see a hierarchical view of the policies, select Policies in the ojbect tree
pane.
– To display the policy details of a single policy, in the ojbect tree pane,
select a policy name. The policy details display in the details pane.
– To open a policy, in the ojbect tree pane or the details pane, double-click
the policy name. The Change Policy dialog box is displayed.
– To display information about all policies, in the ojbect tree pane, select
Summary of all Policies. Click the title bar of each horizontal pane to
expand or collapse it.

6–13
Editing an existing policy
To edit an existing policy
1 In the NetBackup Administration Console, in the ojbect tree pane, expand
NetBackup Management > Policies.
2 Right-click the policy name and select Change.

Policy dialog box: Attributes tab
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 to be backed up?”
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. In this
example, the Policy type is MS-Windows.
6

6–15
Basic policy types
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.
What is backed up?

Here are examples of what is backed up using the basic policy types:
• Standard policy type
When a Standard policy is used to perform a full backup of /mydir in a
UNIX client, everything in /mydir is backed up.
• MS-Windows policy type
When an MS-Windows policy is used to perform a full backup of C:\mydir
in a Windows XP client, everything in C:\mydir is backed up.

Policy storage and Policy volume pool
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.
6

6–17
Policy dialog box: Schedules tab: Editing a schedule
The Schedules tab answers the question “When is this policy to be run?”
To view or edit an existing schedule in a policy, click the Schedules tab and then
click the Properties button.
To add a new schedule to a policy, click the New button.

Schedule dialog box: Attributes tab
The Attributes tab has the following fields:
• Name
The schedule name is used to refer to a schedule in screens and messages.
• Type of backup
The backup type specifies the type of backup that the schedule controls. Select
a backup type from the Type of backup drop-down menu. The menu displays
only the backup types that apply to the policy being configured.
• Schedule type
– Calendar
6
Select the Calendar radio button to enable administrators to select specific
days on which to run a policy.
– Frequency
Select the Frequency radio button to enable administrators to specify how
much time must elapse between the successful completion of a scheduled
task and the next attempt at the task.
This is set in increments of hours, days, or weeks.
For more information about other options on the Schedule dialog box Attributes
tab, see the Symantec NetBackup Administrator’s Guide.

6–19
Backup types for automatic schedules
The backup types for automatic schedules are:
• Full backup
A full backup backs up all files specified in the backup selections list for the
policy, 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
incrementals since the last full or the last full, the last cumulative incremental
and all of the differential incrementals 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.

Schedule dialog box: Start Window tab
The Start Window tab provides controls for setting time periods during which
NetBackup can start backups, archives, or disk staging relocation when using this
schedule. Time periods are referred to as time windows. Configure time windows
so that they satisfy the requirements necessary to complete a task or job.
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.
Note: The NetBackup Administration Console allows “drag and drop” control
over the time window.
For more information about the options on the Schedule dialog box Start
Window tab, see the Symantec NetBackup Administrator’s Guide.
6

6–21
Impact of start window duration on the schedule
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.

Schedule dialog box: Exclude Dates tab
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.
Exclude dates apply to both frequency-based and calendar-based schedules.
6

6–23
Schedule dialog box: Attributes tab: Schedule type
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.
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 or exclude a backup
job on a specific date.
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.

Schedule dialog box: Calendar Schedule tab
The Calendar Schedule tab is displayed when Calendar is selected as the
Schedule type under the Attributes tab of the Change Schedule dialog box.
Calendar-based scheduling provides several run day options for use in scheduling
when a task runs.
The Calendar Schedule tab displays a three-month calendar. Use the controls at
the top of the calendar to change the month or year.
Specific Dates
A backup can run on specific dates rather than follow a recurring schedule, and
specific dates can be added to a recurring schedule. The Specific Dates option
6
enables you to schedule specific dates on which your task runs. 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 in
the Specific Dates dialog box. This specification causes the backup to run on the
specified day during the valid window that is defined for that day.

6–25
Recurring Week Days
The 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.
To define specific run days based on recurring days of the week, such as every
Friday, click Friday on the matrix, and every Friday is automatically selected. You
may also click the row number to select the entire week.

Recurring Days of the Month
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.
In the example on this slide, backups are scheduled for the 15th and last day of the
month.
6

6–27
Retention Periods properties
When you set up a schedule, the selected retention period determines how long
NetBackup retains the backups or archives created according to that schedule.
There are 25 possible levels of retention from which to select. The Retention
Periods properties define the length of time associated with each level.
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
25 possible levels of retention (0 through 24). 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 (including schedules that do not use the retention periods that you have just
changed).

Policy dialog box: Clients tab
The Clients tab contains the list of clients that are backed up or affected by this
policy. This answers the question, “Who 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.
For detailed instructions on adding a client to a policy, see the Symantec
NetBackup Administrator’s Guide.
6

6–29
Policy dialog box: Backup Selections tab
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
Symantec NetBackup Administrator’s Guide.

About backup selections
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.
6
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.

6–31
UNIX client backup selections list guidelines
When defining files for your policy, it is important that you understand the
conventions and rules used to specify backups for UNIX clients.
• Enter one path per line. NetBackup supports a maximum path length of 1,023
characters on UNIX clients.
• Start all paths with a slash (/).
• You can use the following meta or wildcard characters in policy backup
selections lists:
*, ?, { }, and [ ]
• To use meta or wildcard characters literally, precede them with a backslash (\).
Assume, for example, that the brackets in the following path are used as literal
characters:
/home/abc/fun[ny]name
In the backup selections list, precede the brackets with a backslash:
/home/abc/fun\[ny\]name
Example
The following backup selections list uses wildcards to specify UNIX file
specifications. Can you determine what will be backed up when the policy runs?
/home/.[a-zA-Z0-9]*
/etc/*.conf

Windows client backup selections list guidelines
The following are Windows naming conventions:
• Enter one path per line.
• All paths must be absolute. Local paths must start with the drive letter followed
by a colon and a backslash (:\). The drive letter can be either upper- or lower-
case (for example: D:\). Network paths can be in UNC format, starting with
\\server\share\.
Note: c: is not a valid entry, but \\.\D: is valid for a raw partition backup.
• Precede each component in the path with a backslash (\).
• If the last component in the path is a directory, also follow it with a backslash
(\). The trailing backslash is not required but serves as a reminder that the file
6
path is a directory instead of a file (for example: F:\users\workfiles\).
• If the last component is a file, include the file extension and omit the backslash
from the end of the name (for example: K:\special\list.txt).

Note: All selections are recursive from the point specified.
• The components in the path are case-sensitive. The drive letter is not case-
sensitive.
• 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
F:\users\tombru\nbu45*.

6–33
Backup selections list directives
The backup selections list for a policy can contain directives that cause NetBackup
to perform specific actions when processing the files in the list.
Directives can be used as a replacement for specific paths, or in conjunction with
them. For example, the following backup selections combine paths with a directive
and are appropriate for a Windows 2003 or later client:
• C:\
• D:\
• Shadow Copy Components:\
For detailed instructions on the usage of these directives, see the Symantec
NetBackup Administrator’s Guide.

Common backup policy issues
Common 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 on your part is required 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.
6
Common client and backup selections issues
The following are common issues related to clients and backup selections:
• Incorrect policy type or client definition
• Client software not installed
• Client connection or access issues
• Incorrect backup selections list
• Status code 71: None of the files in the backup
selections list exist.

6–35
Lesson 7
Performing File System Backups and
Restores

237

Performing manual backup operations
• Initiate a manual backup job.
• Monitor backups jobs using the Activity Monitor.
Invoking backups
Backups can be initiated:
• Automatically, based on the policy schedule
• Manually from the NetBackup Administration Console or command line
• By users, at their clients
This kind of backup is not initiated by an automatic schedule in the relevant
policy.

239 Lesson 7 Performing File System Backups and Restores Copyright © 2012 Symantec Corporation. All rights reserved.
7–3
Manual backups
A manual backup (sometimes called an immediate backup) is a manual submission
of an automatic policy. Only NetBackup administrators connected to the master
server 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 master 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 without an open window and run only manual backups defined by
that policy, as needed.
Because 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.
You can perform an immediate backup from the command line on a NetBackup
server by using the NetBackup Administration Console or by using the following
command:
bpbackup -i -p policy [-s schedule] [-h host]

Performing a manual backup using the Administration Console
To initiate a manual backup from the NetBackup Administration Console:
1 From the ojbect tree pane of the NetBackup Administration Console, expand
NetBackup Management and select Policies.
2 In the details pane, click the policy name and perform one of the following:
– Select Actions > Manual Backup.
– 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 with the
highest retention level. If you do not select any clients, NetBackup backs up all
clients.
User schedules 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).
4 Click OK to start the backup.
7

7–5
Monitoring jobs using the Activity Monitor
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.

Viewing job details
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
two tabs: a Job Overview tab and a Detailed Status tab. Under the Detailed
Status tab, a Troubleshooter button is available to launch the Troubleshooter, a
wizard that can help determine the cause of the problem and recommend
corrective actions.

7–7
User-directed backups
A user-directed backup functions similarly to an automatic backup; however, the
backup is invoked manually by a user on a client machine from the Backup,
Archive, and Restore GUI, not automatically by the master server.
Keep in mind that although the term user backup or user-directed backup is
commonly used, these 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. However, the term user-
directed is used throughout the documentation.
Clients can initiate a user-directed backup or archive (if enabled).
The policy must have a user backup schedule that defines the window during
which users can initiate a backup. The client must be on 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 GUI or commands
• A backup script launched at regular intervals
• An event trigger that kicks off a backup script

2447–8 Symantec NetBackup 7.5: Install, Configure, and Deploy
Setting the schedule for a user-directed backup
Before a user-directed backup can be started, a user backup policy that contains a
user-directed schedule must be created. Consider the following:
• When you establish a user backup schedule, you provide users with a 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 fails with a status
code 196.
• 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. In user backup
schedules, however, no backup selection list is necessary because users select

the file and directories they want to back up before they start the backup or
archive.
• The policy name you choose is significant. By default, NetBackup
7
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.
For example, a policy name of Policy_users is selected ahead of User_policy.
After a policy is selected, the storage type, volume pool and retention period
are determined by how the policy is configured.

7–9
Initiating a user-directed backup from the BAR GUI
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 (master or media) in their environment.
When performing user-directed operations using the NetBackup GUI, 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 GUI, click Select for Backup.
2 Select the desired files and folders for backup.
a To mark a file for backup, select the check box to the left of the file.
b To mark a folder for backup, select the check box to the left of the folder.
c To mark all files and folders that currently appear, select Edit > Mark
Displayed Files.
3 Start the backup operation by clicking the Backup button (Java) or by
selecting Actions > Backup (Windows).
The Backup Options window is displayed.
4 Confirm the backup selection and click Start Backup.

Viewing user-directed backup job details
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 Symantec 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.

7–11
Verifying successful completion of backup jobs
You can expect backup success to be the norm in a properly configured and well-
maintained NetBackup environment. Because NetBackup is a very robust
application in terms of detecting and reporting errors, 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, image analysis methods, and activity logging.

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.
Accessing the Backup, Archive, and Restore (BAR) interface

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 restore (including an alternate client restore), use the Backup,
Archive, and Restore interface on a client machine.
UNIX
On a UNIX master server, you can start the Java BAR interface either using the
console or the command line. In the ojbect tree pane of the NetBackup
Administration Console, select Backup, Archive, and Restore. The interface is
displayed in the details pane. To start the BAR interface using the command line,
type jbpSA &.
On a UNIX client, you can only start the BAR interface using the jbpSA &
7
command.
Windows
On a Windows master server, from the NetBackup Administration Console, select
File > Backup, Archive, and Restore to start the BAR interface, or click the BAR
button.
To access the BAR interface on a Windows client, on the Windows Start menu,
click Programs > Symantec NetBackup > Backup, Archive, and Restore.

7–13
Restoring files using the Backup, Archive, and Restore interface
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.

Step 1: Click the Select for Restore button
In the Backup, Archive, and Restore interface, click the Restore Files tab (Java) or
the Select for Restore button (Windows). In Windows, the Select for Restore
button opens a new Restore window. If a Restore window is already open, you do
not need to open a new window.

251 Lesson 7 Performing File System Backups and Restores
7–15
Step 2: Specify the NetBackup machines and policy type
Select Actions > Specify NetBackup Machines and Policy Type (Java) or select
File > Specify NetBackup Machines and Policy Type (Windows). The Specify
NetBackup Machines and Policy Type dialog box is displayed. For normal user-
directed restores to the original client, accept the default settings.
You can modify these settings as follows:
• Server to use for backups and restores
To define the master server to use as the source of images to browse, select the
server from the drop-down list.
If you need to add a server to the list, click Edit Server List, type the name of
the server in the field, and click Add Name(s). Click OK to return to the
Specify NetBackup Machines and Policy Type dialog box.
You may need to change this entry if the client can be backed up by more than
one master server. For example, a laptop used at multiple locations may be
under the control of different NetBackup master servers at different times, so
you should select the master server that manages the backup images you need.
• Source client for restore (Java) or Source client for restores (or virtual
client for backups) (Windows)
When performing alternate-client restores or server-directed restores, select the
client to use from the drop-down list.
If you need to add a client to the list, click Edit Client List, type the name of
the client in the field, and click Add Name(s). Click OK to return to the
Specify NetBackup Machines and Policy Type dialog box.

• Destination client for restores
Use this field when performing server-directed restores. For normal restores to
the original client, leave the destination client as the current client.
If you need to change the destination client, select a client from the drop-down
list.
• Policy type for restores
Select a policy type from the drop-down list.
It is important for you to select the correct policy type, especially when the
client’s operating system and the master server’s operating system do not
match. For example, a Microsoft Windows master server trying to restore a
UNIX client can default to a policy type of MS-Windows instead of Standard.
After you have made all of the necessary selections, click OK.

7–17
Step 3: Select the restore type
Select the appropriate restore type from the drop-down menu under the Restore
Files tab (Java) or on the Select for Restore drop-down menu (Windows).
Restore type selections include:
• Normal Backups
• Archived Backups
• Raw Partition Backups
• True Image Backups
• Backup Exec Backups
• Point in Time Rollback Backups
• Virtual Machine Backups
About proxy restores

A proxy restore enables you to restore backed up files from a file server by using
the Backup, Archive, and Restore interface on your computer. A proxy restore is
useful in environments where users store their files on file servers instead of on
their local computer.
Use the following guidelines for proxy restores:
• Your NetBackup environment must be configured to allow proxy restores.
• Files can only be restored to the same file server from where they were backed
up.
• You must have write permission for the files you want to restore.

• You can view and mark any of the folders and files in a selected backup.
However, you cannot restore any items for which you do not have write access.
Use the following procedure to restore from backups as a proxy. To restore from
backups as a proxy:
1 Select File > Select Files and Folders to Restore.
2 Select a restore type from the drop-down menu.
3 In the Browse for Computer dialog box, select the file server where you want
to restore folders or files and click OK.
In the Restore window, the NetBackup server changes to the master server of
the selected file server.
4 Follow the restore instructions for the restore type you selected.

7–19
Backup types in the Backup, Archive, and Restore interface
(Windows only)
In the Backup, Archive and Restore interface on Windows, the default view of
backups is the History as a Timeline view. The advantage of this view is that you
can easily see if a backup has missed any days, as well as the sequence of backups
that has occurred. The type of backup is identified by the icon. The slide defines
icons that you commonly see in this view.
You can change this view to the History as a List of Backups view. The
advantage of this view is that you can obtain more information about each backup,
including the time of backup, backup type, and number of files. This view is very
similar to the default view of backups in the Java version of the Backup, Archive
and Restore interface.

Step 4: Set the view
After you specify a restore type, you need to identify the backups you want to
view. From these backups, you will eventually select the files for restore.
Deselect Show NetBackup History as a Timeline (Windows only)

By default, the Windows BAR interface displays NetBackup history as a timeline.
To change this setting, select View and deselect Show NetBackup History as a
Timeline.
Specify a date range (Java only)

In the Java interface, 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 (Java only)

After you specify a restore type and date range, you need to identify the backups
you want to view. To do this, click the List Backups button to display a list of
7
backups. From these backups you will eventually select the files for restore. If you
want to restore from a series of backups, select the full backup, as well as the
subsequent differential or cumulative incremental backups.

7–21
Display the backups
If you want to restore from the latest backup, click the Show most recent backup
in the specified date range button (Java) or the Show most recent backup of
files button (Windows).
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 (Java) or the Show all backup of files button
(Windows).
To search for files in a backup, click the Find items to restore button (Java) or the
Search for Items to Restore button (Windows).
Listing files using the bplist command

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 or archived by another client only
if you are validated to do so by the 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. The default policy
type is for file system.
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 Symantec NetBackup Commands Reference Guide. TechNote 27299: A
listing of policy types and how they are used with bplist and other NetBackup
commands (http://www.symantec.com/docs/TECH27299) describes
policy types and how they are used with bplist and other NetBackup
commands.

7–23
Refresh the screen
To determine which files can be restored, you may need to refresh the screen. In
Java, select View > Refresh. In Windows, the view is refreshed when you set the
view to Show Most Recent Backup; you can also manually refresh the screen by
selecting View > Refresh NetBackup History.
The items you can restore are displayed in the Contents of selected directory list.
From this list, determine which files you can restore.
Restoring from multiple images

Whenever a restore operation is warranted, it is likely that the necessary backup
images are stored on separate media. Examples of such a distribution of backup
images include:
• Restore from full and incremental backups.
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.
This type of restore relates to incremental backups:
– 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.

If you want 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 you want to restore.

7–25
Step 5: Mark the files and folders to restore
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.

Step 6: Preview the required media
After selecting the files and folders to restore, click the Preview button (UNIX) or
select Actions > Preview Media (Windows).
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 ensures that you do not request a restore
operation that requires a tape that is currently offsite or otherwise unavailable.
If you determine that the media are available, click OK (Java) or Close (Windows)
to close the Media required dialog box.

7–27
Select Actions > Restore
Click Restore (Java) or select Actions > Restore (Windows) 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.

Step 7: Select destination choices and restore options
Destination
The Destination pane (Java) or the Restore Destination Choices pane (Windows)
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 (Java) or
Restore individual folders and files to different locations (double-click to
modify) (Windows)
Restores items to paths other than the path from which they were backed up
• Create and restore to a new virtual hard disk file
7
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 Properties.
Set the VHD file size and select the behavior of the file as follows:
7–29
– 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.
– 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.
Options
The remaining options grant you control over how NetBackup handles files that
may already exist.
• 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 to NetBackup administrators from the NetBackup client interface 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 Windows 2000, Windows XP, or Windows Server 2003. 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.
• Overwrite existing files (Java) or Overwrite the existing file (Windows)
This option must be enabled if the restore operation is required to replace any
existing versions of files to be restored.
The default is to not overwrite existing files.

• Restore the file using a temporary filename (Windows)
This option restores the file using a temporary filename in the destination
directory.
• Restore all directories without crossing mount points (Java)
This option restricts the restore to the contents of a single file system.
• Rename hard links and Rename soft links (Java)
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.
• Do not restore the file (Windows)
This option prevents the file from being overwritten and is the default.
• Use default progress log filename (Java)
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.
Step 8: Initiate the restore

After you have selected all of the necessary options, click Start Restore.

7–31
Monitoring restore operations using the Backup, Archive, and
Restore interface
You can monitor the progress of the restore operation from the Task Progress tab
in the Backup, Archive, and Restore interface (Java) or the View Status dialog
box (Windows).
Here you see the progress of the restore job as it executes. If an error is
encountered, launch the Troubleshooter to determine the cause of the problem and
receive recommended corrective actions.

Performing restore operations using OpsCenter Operational
Restore
• Restore files and directories on a client using OpsCenter Operational Restore.
• Monitor restore operations using OpsCenter.
Introduction to Operational Restore

Operational Restore provides a simplified search and retrieval mechanism that
works across multiple NetBackup domains.
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
7
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 Symantec
OpsCenter Administrator’s Guide.

7–33
Restoring files using Operational Restore
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.
To perform a restore of files and directories on a client using Operational Restore,
follow the steps shown on this slide. This procedure is demonstrated in detail in
this topic.
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 (and not the OpsCenter Server). For more information about the
nbfindfile command, see the Symantec OpsCenter Administrator’s Guide.

The Operational Restore interface
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 Files and Folders Restore.
The Files and Folders Restore wizard is displayed.
The Files and Folders Restore wizard consists of three panels:
• Search Files or Folders 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. 7

7–35
Performing a simple search
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.
Select Month if you want to view files and directories that were backed up in
the last month. The time interval associated with the selected time frame is
displayed on the left side of the page. You can also adjust the time interval by
clicking the arrows on the left and right of the time interval.
• File or Directory name: The following options exist for this field:
– Enter a full path using a path delimiter of forward slash (/) on UNIX or
back slash (\) on Windows.
– Enter a specific file or directory name.
– If the exact directory (folder) or file name is not known, use the * (any
number of any characters) and ? (any one character) wildcards.
• Search within Clients: In this field, specify the set of clients whose backup
information you want to search. You can search multiple clients that are
associated with one or more views or master servers.
– Select a view from the View drop-down list.
– Select a master server from the Master Server drop-down list. All
NetBackup 7.5 master servers that are a part of the selected view are
displayed.

– Specify the clients whose backup information you want to search. If you
remember the client name, type it in the Client text box. Auto-complete
displays the client names as you type. Select the name when it appears.
If you do not remember any client names or simply want to browse through
the clients, click the Browse and select client link and select a list of
protected clients that are associated with a master server or a client-type
view.

7–37
The Browse Clients dialog box
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 7.5 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.
• 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.

Client search results
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.
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 Symantec
OpsCenter Administrator’s Guide.
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.

7–39
File or directory search results
Under the Search tab, you can see that the search has completed successfully.
Search results are displayed while the search is in progress.
By default, the search results table lists the following default columns: File or
Directory Name, File or Directory Path, Backup History, 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.
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.
If there are additional results, the number of rows and pages is displayed.
To display the backup history, click the Backup History Selection link for the file
or directory that interests you. The Backup Timeline window is displayed.

Viewing the backup history
The Backup Timeline window is a timeline view of backups for a specific file or
directory. By default, the search and browse results that are displayed in the
OpsCenter console display the most recent backup that occurred for the specific
file or directory and is the primary backup copy. The Backup Timeline window
enables you to select a previous backup in the selected time frame. It also enables
you to select a copy other than the primary copy.
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 for each
backup of the file or directory. Each icon represents a different backup or snapshot.
When you open the Backup Timeline window, the latest backup in the selected
timeline is already selected. Select another icon if you want to select a previous
backup.
The Backup table in the middle of the window displays information about the
backup that is selected from the timeline view. Click an icon to view the details of
the specific backup in the Backup table. The Backup table lists the details of each
backup image that is associated with the backup. It displays information, such as
7
backup time, policy name, policy type, backup type, and so on. 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.
Click Add to Restore Cart to add this copy to the restore cart.

7–41
Viewing the Restore Cart
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
Symantec OpsCenter Administrator's Guide.

Selecting files to restore
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.

7–43
Setting the restore options
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.
6 After you have selected the restore options, click Next.
The Summary panel is displayed.

Restore summary and preview media
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 will 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.
7 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.
7

7–45
Starting the restore
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.

Monitoring restore operations using OpsCenter
The Monitor > Jobs view provides details about NetBackup jobs. In this example,
detailed information about Job ID 111, the restore job, is displayed. Notice that the
job is selected in the content pane, and additional information is displayed in the
details pane.

7–47
Backup and restore job-related tips
• Monitor restore operations using the Activity Monitor.
• Identify common job-related status codes.
• View backup and restore reports.
• Perform basic steps to troubleshoot failed jobs.
Monitoring jobs using the Activity Monitor

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.
• Checkpoint Restart for restore jobs works only on files that are backed up
using Standard or MS-Windows policy types.
Note: Although NetWare clients use the Standard policy type, Checkpoint
Restart for restores is not supported on NetWare clients.
• Third Party Copy and Media Server Copy images that use Standard policy
types are supported, but they cannot be suspended or resumed if the backup
image has changed blocks.
• FlashBackup is not supported.
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 Symantec NetBackup Administrator’s Guide for details of this functionality.
For a detailed explanation of the bprestore command, see the Symantec
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 will be placed when it is restored.
7

7–49
Common NetBackup status codes
NetBackup status code: 96

This error indicates that NetBackup was unable to allocate new media for the
backup or that the storage unit defined for the backup policy has no available
media. If you encounter this error, check the following five factors:
• Physical aspects
Verify that there are actual media in the storage unit.
• Logical aspects
Verify that there are media allocated to the volume pool. If not, have you
created a scratch volume pool from which the policy’s volume pool can pull
media? If you do have a scratch volume pool, does it contain available
volumes? (Just because a volume pool is named scratch does not mean that it
is the scratch volume pool.)

• Retention period of the media
If media are available, what are the retention levels? Are the volumes
unavailable because they have not expired?
• Status of the media
Are the media full, frozen, or suspended? If so, determine why and correct the
problem.
• Format of the media
Do the media type, the storage unit type, and the device type all match?

This status code 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.
Troubleshooting recommendations include:
• Check the files in the policy file list for such things as having appropriate
permissions and not being locked or hidden.
• Determine if the files were open at the time of the backup.
If these files were open, check the Host Properties to determine how
NetBackup handles the open files that it encounters during a backup operation.
• Determine if the files were being written to during the backup operation (such
as with a log file).
• If the files causing the error are truly not needed (for instance, they are specific
files within a directory that do not need to be backed up), add them to the
exclude list for this client.

This status code 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.

This status code indicates that the backup job was queued, but the time window
closed before the backup could run.
Investigate why the job was unable to complete. Ask questions, such as:
• Were any previous backups unusually large, which may have delayed the start
of the failed backup?
• Was there a device problem that may have effectively reduced backup
bandwidth?
• Was there unusual network activity during the backup window, which may
have delayed the backup throughput?
• If this is a recurring error, should you consider “upsizing” your backup

environment to handle the work?
For a detailed explanation of these and other status codes, see the Symantec
7
NetBackup Status Codes Reference Guide.

7–51
Common restore issues
Problems with restores can include the following:
• Incorrect restore criteria
Ensure that you have defined the proper settings for the restore job, such as the
policy type and NetBackup server.
• 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

Verify that you have read permission for the backup image and write
permission to the destination location.
• 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
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
Symantec 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.
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 nonroot user specifies USEMAIL = mail_address in the $HOME/
bp.conf file, NetBackup sends an e-mail containing the restore completion
7
status to mail_address. This message is sent when the restore process

completes.

7–53
Reporting on backups and restores
The table on this slide summarizes how backup and restore jobs can be managed
using the NetBackup Administration Console (GUI), NetBackup commands
(CLI), and NetBackup OpsCenter.

7–55

Lesson 8
Protecting Backup Data

293

Backup duplication concepts
After completing this topic, you will be able to identify the duplication backup
types, including inline, manual duplication, basic disk staging, and storage
lifecycle.
Duplication strategy: Multiple inline copies

In many cases it is desirable to have multiple copies of a backup image. Common
practice for critical data is to maintain at least two copies of every backup image:
one onsite for restores and one offsite for disaster recovery and archival purposes.
NetBackup supports several strategies for creating multiple copies of an image.
NetBackup can duplicate backups that are already on NetBackup volumes and are
not expired. The example on this slide uses NetBackup’s Multiple Copies option,
which is also referred to as Inline Copy. This option enables you to create up to
four copies simultaneously at the time of the backup. This strategy is very efficient
because data only travels across the backup infrastructure once. This strategy also
provides excellent data protection because copies may be sent offsite immediately.
This strategy also requires more resources.
8

295 Lesson 8 Protecting Backup Data Copyright © 2012 Symantec Corporation. All rights reserved.
8–3
Duplication strategy: Disk staging
Disk staging is a very popular alternative to traditional backup strategies. When
using disk staging, sometimes called Disk-to-Disk-to-Tape, or D2D2T, backups
are initially written to a high-performance disk attached to the NetBackup media
server, often on a SAN. Backup and restore performance from the disk are both
excellent. Because there is usually not enough available disk space to store backup
images for their entire retention period, images are periodically copied from the
disk to tape. NetBackup calls this relocation, but do not be confused by the term:
images are copied, not moved. Images that are successfully relocated are
eventually deleted from the disk; this occurs when the disk is full and NetBackup
needs space to write new images.

Duplication strategy: Duplicate after backup
Another strategy for creating multiple copies 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 is often performed during business hours
when tape drives are idle. This is a good solution if your environment has strict
windows during which backups need to complete. For environments with 24/7
backup operations, other solutions, such as disk staging, are becoming more
popular. Choose one strategy or a combination of strategies to best fit your needs.
The NetBackup Vault option provides powerful functionality to assist with this
strategy, such as scheduling automatic backup duplication and ejecting tapes at
specific times. Vault also provides detailed reports that are used to manage tape
rotation. If you are not using the NetBackup Vault option, duplication is still
possible. Perform the duplication manually or schedule it using cron jobs (UNIX)
or the Task Manager (Windows).
Another method for automating duplications after backups is to use storage
lifecycle policies. A storage lifecycle policy is an automated, reusable backup
storage plan based on the business value of the data. Storage lifecycle policies are
discussed later in this lesson.
8

8–5
Setting Maximum backup copies globally
NetBackup supports up to ten backup image copies—a primary copy and up to
nine duplicates. However, by default, the Maximum backup copies global
attribute limits the number of backup image copies to two. If you require more
than two copies of an image, set this attribute to a higher number than the default.
Note: If you are using disk staging, ensure that the number of copies is correct.
Disk staging accounts for two copies. If you want two copies on tape, set the
Maximum backup copies global attribute to 3.

Creating multiple inline copies
To create multiple copies when a schedule runs:
1 From the Change Schedule window, click Configure.
2 In the Configure Multiple Copies window, specify the criteria.
Keep the following considerations in mind when selecting criteria for multiple
copies:
– The primary copy is the copy NetBackup uses for restores. Typically, this is
the copy you plan to keep onsite.
– Connect all destination storage units to the same media server. If you select
a mix of disk and tape destinations, the backup runs at the speed of the
slowest device.
– Symantec recommends sending copies to volume pools other than the
original volume pools. This enables easy determination of which tapes to
send offsite.
3 Click OK when you are finished.
8

8–7
Duplicating images manually
To duplicate an image using the NetBackup Administration Console, perform the
following steps:
1 In the ojbect tree pane of the NetBackup Administration Console, select
NetBackup Management > Catalog.
2 In the details pane, specify criteria that NetBackup uses to build a list of
backup images from which you can make your selections:
a Select Actions > Duplicate.
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 duplicate and select Duplicate from the shortcut menu.
The Setup Duplication Variables dialog box is displayed.

Setting duplication variables
4 Specify the number of copies to be created.
If there are enough drives available, the copies are created simultaneously.
Otherwise, the system may require operator intervention if, for instance, four
copies are to be created, and there are only two drives.
5 Specify the priority the duplication jobs have over other jobs in the queue (0 to
99999 (highest)).
6 The primary copy is the copy from which restores are performed.
Generally, the original backup is the primary copy. If you want one of the
duplicated copies to become the primary copy, mark the appropriate check
box; otherwise, leave the fields blank.
When the primary copy expires, a different copy automatically becomes the
primary copy. The copy chosen to be the primary is the copy with the smallest
copy number. If the primary copy is copy 1, copy 2 becomes primary copy
when copy 1 expires. If the primary copy is copy 5, copy 1 becomes the
primary copy when copy 5 expires.
7 Specify the storage unit where each copy is to be stored.
If a media manager storage unit has multiple drives, it can be used for both the
source and destination.
8 Specify the volume pool where each copy is to be stored. The volume pool
selections are based on the policy type setting that was used for the query:
– If the policy type was set to query for All Policy Types (default), both
8
catalog and noncatalog volume pools are included in the drop-down list.

301 Lesson 8 Protecting Backup Data
8–9
– If the policy type was set to query for NBU-Catalog, only catalog volume
pools are included in the drop-down list.
– If the policy type was set to query for any policy type other than NBU-
Catalog and All Policy Types, only noncatalog volume pools are included
in the drop-down list.
Note: NetBackup does not verify in advance that the media ID selected for the
duplicate copy is not the same as the media ID of the volume that contains the
original backup. Because of this potential deadlock, specify a different volume
pool to ensure that a different volume is used.
9 Select the retention level for the copy, or select No Change.
The duplicate shares many attributes of the primary copy, including backup ID.
Other attributes, such as elapsed time, apply only to the primary copy.
NetBackup uses the primary copy to satisfy restore requests.
The implications of setting the retention period are:
– If you select No Change for the retention period, the expiration date is the
same for the duplicate and source copies. You can use the bpexpdate
command to change the expiration date of the duplicate.
– If you specify a retention period, the expiration date for the copy is the
backup date plus the retention period. For example, if a backup was created
on November 14, 2009 and its retention period is one week, the new copy’s
expiration date is November 21, 2009.
10 Specify whether or not the remaining copies are to continue or fail if the
specified copy fails.
11 If the selection includes multiplexed backups and the backups are to remain
multiplexed in the duplicate, mark the Preserve multiplexing check box.
If you do not duplicate all the backups in a multiplexed group, the duplicate
has a different layout of fragments. (A multiplexed group is a set of backups
that were multiplexed together during a single multiplexing session.) By
default, duplication is performed serially, and it attempts to minimize media
mounts and positioning time. Only one backup is processed at a time.
If Preserve multiplexing is enabled, NetBackup first duplicates all backups
that cannot be multiplex-duplicated before the multiplexed backups are
duplicated. Preserve multiplexing does not apply when the destination is a
disk storage unit or disk staging storage unit. However, if the source is a
multiplexed tape and the destination is a disk storage unit or disk staging
storage unit, marking the Preserve multiplexing check box ensures that the
tape is read in only one pass rather than in multiple passes.
12 Click OK to start duplicating.
13 Click the Results tab, and then select the duplication job you just created to
view the job results.

Promoting a copy to a primary copy
Each backup is assigned a primary copy. NetBackup uses the primary copy to
satisfy restore requests. The first backup image created successfully by a
NetBackup policy is the primary backup. If the primary copy is unavailable and
you have created a duplicate, 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 images
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
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.
To promote a backup copy to a primary copy using the CLI, type:
bpchangeprimary
bpduplicate –npc primary_copy –backupid backup_id
8

8–11
Storage lifecycle policy concepts
After completing this topic, you will be able to describe configuration options for
storage lifecycle policies.
What is a storage lifecycle policy?

A storage lifecycle policy is an automated, reusable backup storage plan based on
the business value of the data.
Storage lifecycle policies may also be called SLPs, storage lifecycles, or lifecycles.

Storage lifecycle characteristics
Storage lifecycles have the following characteristics:
• Destination
A storage lifecycle can be configured to write backup data to a maximum of
ten destinations. The number of destinations cannot exceed the Maximum
backup copies setting found by selecting Host Properties > Master Servers
> Global Attributes. The default setting is two.
• Destination type
Storage lifecycles have two destination types—backups and duplications. Up
to four of the destinations can be configured as backups; the first destination is
the primary copy, and the additional destinations are considered multiple
(inline) copies. Additional destinations may be configured as duplications,
provided the total number of destinations does not exceed ten.
• Retention type
Each destination in the lifecycle can be configured for a unique retention type
and period. The retention types are:
– Fixed retention: The image does not expire until the specified retention
period has ended.
– Staged capacity managed: NetBackup tries to keep duplicated images on
disk until the desired cache period has passed. (Additional information is
provided later in this lesson.)
8
– Expire after duplication: The image is expired after it has been

duplicated. (Additional information is provided later in this lesson.)

8–13
Introduction to storage lifecycle benefits
This slide provides an overview of the benefits of storage lifecycles. Each of the
benefits shown on the slide is described in this topic.

Storage lifecycle benefits: Reduced administration
Storage lifecycles enable administrators to create a storage plan for similar types of
data. After a storage lifecycle is created and configured, it can be used as often as it
is needed. This reduces administration errors.
Storage lifecycles also provide a single place to view the storage plan. Without
storage lifecycles, administrators needed to look in several places to view similar
information, including the backup policy, the policy schedule, the disk staging
storage unit, the staging schedule, and the Vault profile.

8–15
Storage lifecycle benefits: Automatic duplication
Before storage lifecycles, an administrator had to start duplication jobs manually,
either by using the Catalog in the Administration Console (shown in the slide) or
by using the bpduplicate command.
With storage lifecycles, you can configure duplicates to be created automatically,
without manual intervention.
A single lifecycle can be configured for the primary backup copy, up to three
additional multiple (inline) copies, and a varied number of duplication copies. The
total number of backup and duplication destinations cannot exceed ten.

Storage lifecycle benefits: Reduced risk
Using a storage lifecycle guarantees that all destinations in the lifecycle are
written. The backup and duplication destinations are retried as necessary until the
storage lifecycle is satisfied or until the backup or duplication is cancelled by the
administrator.
Storage lifecycle images that have not been successfully written do not expire,
even if they have passed their retention, until all destinations have been satisfied.

8–17
Storage lifecycle benefits: Additional staging locations
Without using storage lifecycles, the primary copy of the (temporary) staged image
can only be written to a basic disk storage unit.
Using storage lifecycles, you can now write the primary copy of the (temporary)
staged image to all supported disk types (except basic disk), a VTL, or a tape.

Storage lifecycle benefits: Additional staging retentions
When using BasicDisk staging, there is no way to specify a retention within the
basic disk staging schedule.
Using lifecycles, each lifecycle destination can have its own retention.

8–19
Storage lifecycle benefits: Data classification
A data classification is an optional ranking that can be assigned to backup data.
Rank backup data according to its business value or importance, relative to your
other backup data.
For example, if your financial backup data is more important than your e-mail
backup data, you can assign a higher rank to the financial backup data and a lower
rank, or no rank, to the e-mail data.
Currently, the data classification is used by NetBackup to manage disk capacity,
which is covered in detail later in this lesson.
CAUTION The name and rank of a data classification may be changed, but a
data classification can never be deleted. Before using data
classifications, ensure that you have a well-thought-out data

protection strategy.

Storage lifecycle benefits: Managed disk capacity
When the retention type is Staged capacity managed, NetBackup uses the
Desired cache period and the data classification to manage disk capacity. The
desired cache period is also sometimes referred to as the try to keep time.
The retention period for a staged capacity managed storage destination is not
assured as it is for a fixed retention period. The desired cache period becomes a
target that NetBackup tries to maintain. If the space is not required, the backup
data can remain on the storage destination longer than the desired cache period
indicates.
Note: As a best practice, do not keep duplicated images on disk indefinitely. At the
least, set the duplicated image to expire when the largest fixed retention image
expires.
Incoming backups always have precedence over disk images that have already
been duplicated. When a disk reaches its high water mark, NetBackup must purge
duplicated images from the disk. However, NetBackup now has criteria to use to
determine which duplicated images to purge first.
NetBackup first considers purging images that are past their desired cache period.
Of these images, the ones with no data classification or the lowest data
classification are purged before images with a higher data classification. This
enables more important images to be retained longer on disk, enabling faster
restores.
8

8–21
If images must still be purged to make room for incoming backups, NetBackup
then considers images that are not past their desired cache period. As their names
imply, it is a desired cache period. The only guaranteed retention is a fixed
retention. Of these, the images closest to their desired cache period are purged
first. Again, data classifications are used to keep images with a high ranking on the
disk longer than images with no ranking or a lower ranking. (Additional
information is provided later in this lesson.)

Using storage lifecycle policies
After completing this topic, you will be able to create and initiate a storage
lifecycle policy.
Prerequisites to creating a storage lifecycle

The slide shows tasks that must be performed before you create storage lifecycles.
1 Design a data protection strategy. Consider these best practices when you are
designing your data protection strategy:
– 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.
8
4 Configure the Maximum backup copies and Data Classification master

server host properties before creating storage lifecycles.
8–23
Setting maximum backup copies
The number of destinations in the storage lifecycle cannot exceed the Maximum
backup copies value in the Global Attributes. The default value is two. The
maximum value is ten.
The graphic shows the error message that you receive if you configure more
destinations than allowed by the Maximum backup copies value.

Creating a new storage lifecycle policy
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.

8–25
The New Storage Lifecycle Policy dialog box
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 will have 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 Storage Operation dialog box is displayed. The options available in the
New Storage Operation dialog box depend upon the type of operation (backup,
snapshot or import) and the type of storage unit (tape or disk). An Import
operation in an SLP indicates that the SLP is to automatically import images into
the target master domain as part of Auto Image Replication. A Snapshot operation
creates a point-in-time, read-only, disk-based copy of a client volume.

Configuring backup storage operations
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.
– Staged capacity managed (disk 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.
– Expire after copy: Select this retention type to have this backup expire
after the duplication has occurred.

• 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. If you want a media server to read backups that it did not write, specify
the media server in this field.
8

8–27
Configuring duplication, snapshot and replication storage operations
The following describes the options for duplication, snapshot, and replication
storage operations.
• Storage unit: The storage unit selection is determined by the storage operation
selection.
– Duplication: Select a backup storage unit or a backup storage unit group.
The selection cannot be a snapshot storage unit or a snapshot storage unit
group.
– Replication: Select the storage unit that is configured to contain replicated
snapshots. The Target master option is used for Auto Image Replication
and is not selectable in a Replication Director configuration.
– Snapshot: A storage unit selection is necessary if the snapshot is to be used
by a subsequent replication operation, or if the SLP contains only one
operation and that is a snapshot operation. NetBackup uses that storage unit
to determine which media server to use to launch the snapshot job.
See the Symantec NetBackup Administrator’s Guide for more information
about snapshot operation storage unit selection.
• Volume pool: Select the volume pool for the duplication (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.

– Staged capacity managed (disk only): Select this retention type to have
NetBackup 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.
• 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. If you want a media server to read backups that it did not write, specify
the media server in this field.
Note: An alternate read server can be specified for both backup and
duplication destinations. However, to use an alternate read server as part of a
duplication operation, you must specify the name of the alternate server in the
backup destination configuration.

8–29
Configuring hierarchical duplication
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.
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.
A non-hierarchical duplication destination is a duplication destination that does
not use a specific source for duplication. It is never indented or is never a child of
another destination.
It can serve as the source for hierarchical duplication destinations. Any backup that
is marked as the primary copy can provide the source for a non-hierarchical
duplication destination.

Storage lifecycle restrictions
There is a limit of four backup storage destinations per storage lifecycle. You
cannot save the storage lifecycle if it has more than four backup storage
destinations.
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.

8–31
The multiple backups limitation
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.

Viewing lifecycle details, with hierarchy
This slide shows a storage lifecycle policy with hierarchical duplication.
You can see from the output of nbstl on this slide that the backup destinations
have a source of the client directly. The duplication destinations’ source shows the
destinations from which they will be duplicated.

8–33
Duplication tuning parameters
The duplication tuning parameters enable a system administrator to fine-tune how
the Storage Lifecycle Manager runs duplication jobs.
To use duplication tuning parameters, create a file called
LIFECYCLE_PARAMETERS at /usr/openv/netbackup/db/config
(UNIX) or install_path\NetBackup\db\config (Windows).
Available duplication parameters are:
• DUPLICATION_SESSION_INTERVAL_MINUTES
This parameter indicates how frequently NetBackup starts a duplication
session. During a duplication session, NetBackup looks for completed backups
on backup storage destinations and decides whether it is time to start a new
duplication job.
Default: 5 minutes. Minimum: 1 minute.

• IMAGE_EXTENDED_RETRY_PERIOD_IN_HOURS
All copies must be completed in a lifecycle. If necessary, NetBackup initially
tries to duplicate an image to a duplication destination three times. This
prevents NetBackup from retrying too frequently. If, after three tries, the copy
is still unsuccessful, this parameter indicates how long NetBackup waits before
an image copy is added to the next duplication job.
Default: 2 hours. Minimum: 1 hour.

• MIN_GB_SIZE_PER_DUPLICATION_JOB
This parameter indicates the size that the batch of images should reach before
one duplication job is run for the entire batch. The lifecycle does not request a
duplication job until either of the following conditions is met:
– The aggregate size of the images in a batch reaches the minimum size as
indicated by MIN_GB_SIZE_PER_DUPLICATION_JOB.
– The MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB time
has passed. This parameter determines the maximum time between batch
requests.
Default: 7 GB
• MAX_GB_SIZE_PER_DUPLICATION_JOB
This parameter determines how large the batch of images is allowed to grow.
When the size reaches the size indicated by this parameter, no more images are
added to the batch.
Default: 25 GB
• MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB
If the minimum batch size is not reached by the time indicated by this
parameter, the lifecycle requests a duplication job, regardless of the size.
Default: 30 minutes.

8–35
Managing storage lifecycles
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.
nbstlutil supports the following ways that you can intervene with storage
lifecycle operations:
• cancel
This option cancels pending lifecycle operations on selected image copies.
When you cancel a specific destination, you also cancel the pending lifecycle
operations at other destinations that depend on the source copy from that
destination.
• inactive
This option deactivates future lifecycle operations on selected image copies,
but retains the image information so that processing can resume. This function
is similar to a suspend function.
• active
This option activates the lifecycle operations on selected image copies. This
function is similar to a resume function.
• list
This option displays the contents of an image list from the EMM database. The
tables that hold the information about the images that lifecycles process can be
listed. This option is primarily a debugging tool, but support may use the
information to troubleshoot problems.

• stlilist
This option displays the status for incomplete copies of lifecycle managed
images.
• diskspaceinfo
This option 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 Symantec NetBackup Commands Reference Guide.

8–37
Storage lifecycle scenario
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, advdisk1_stu_winmaster. The backup image
created on advdisk1_stu_winmaster has a fixed retention, and expires one
month after the backup image is created.
2 Simultaneously, another copy of the backup image is written to
advdisk2_stu_winmaster. The retention of the backup image created on
advdisk2_stu_winmaster is set to Expire after copy.
Both advdisk1_stu_winmaster and advdisk2_stu_winmaster are defined on
the master server.
3 After the backup job completes, the SLP causes a duplication of the backup
image. This duplicate copy is written to a Media Manager storage unit,

tape_stu_winmaster, and has an assigned retention of six months.
Note: After the duplication job has run and the copy is created on tape, the source
copy for the second backup, which resides on advdisk2_stu_winmaster, is
deleted.

Storage lifecycle example description
In this example, the winclient_test_SLP_master backup policy uses the
lifecycle_test policy storage. The lifecycle_test policy storage contains the
following destinations:
• A backup goes to the advdisk1_stu_winmaster storage unit, with a fixed
retention of 1 month.
• A backup goes to the advdisk2_stu_winmaster storage unit, with retention set
to expire after copy.
• A duplicate goes to the tape_stu_winmaster storage unit, with a fixed
retention of 6 months.

8–39
Activity Monitor jobs
When winclient_test_SLP_master runs, the jobs shown in the graphic are
initiated. The following pages present the job detail status of each of the jobs.

The parent and primary backup jobs
This slide presents the job detail status for the parent and primary backup jobs.

8–41
The inline copy backup and duplication jobs
This slide presents the job detail status for the inline copy backup job and the
duplication job.

The image cleanup job
This slide presents the job detail status for the image cleanup job.

8–43
Storage lifecycle reporting tools
The table on this slide summarizes how storage lifecycle information can be
displayed using the NetBackup Administration Console (GUI), NetBackup
commands (CLI), and OpsCenter.

Introduction to NetBackup Vault
After completing this topic, you will be able to describe the benefits of using
NetBackup Vault.
What is NetBackup Vault?

Vault is a licensed extension to NetBackup that automates selection and
duplication of backup images and ejection of media for transfer to and from a
separate, offsite storage facility. NetBackup Vault also generates reports to track
the location and content of the media. Vault functionality does not have to be used
only for disaster recovery. You can use Vault to manage the data and the media that
you store offsite for regulatory archival purposes.

8–45
The vaulting process
Vaulting is the process of sending backup images offsite to a protected storage
location. A Vault job must select images (backups). Because the other steps are
optional, you can separate the other Vault tasks into distinct jobs to accomplish the
tasks.
1 Choose the backup images to be transferred offsite (required). You must
configure the image selection for every Vault job.
If you create multiple original images concurrently during a backup job, Vault
can send the original images offsite. If you duplicate images, Vault uses the
primary backup image as the source image for the duplication operation;
however, Vault duplicates from a nonprimary copy on disk, if one exists.
2 Duplicate the backup images to be transferred offsite (optional). Vault writes
copies of the backup images onto the media that you can eject and transfer
offsite. Because you do not have to duplicate images in Vault, you do not have
to configure the duplication step.
3 Back up the NetBackup catalog (optional). The NetBackup catalog consists of
information about backups, including records of the files and the media on
which the files are stored, and information about media sent offsite. However,
vaulting a catalog backup along with your data can help you recover from a
disaster more efficiently.
4 Eject the media and transfer it to secure storage (optional). Media can be
ejected automatically by a scheduled Vault job or manually after the job has
completed. Media can be ejected for each job individually or can be
consolidated into a single eject operation for multiple Vault jobs.

Vaulting example
This slide presents a vaulting example.
Consider a situation in which your offsite vendor (the company that transports
vaulted media to and from the offsite location) does not pick up vaulted media
every day. In this situation, configure NetBackup Vault profiles to evenly spread
the duplication workload throughout the week rather than performing all of the
duplication on one day. The duplicated media can remain in the robot until it is due
to be collected by the offsite vendor.
The table on this slide outlines the steps to configure Vault when your offsite
vendor collects vaulted media once per week on Friday.

8–47
Vault scheduling
The NetBackup administrator controls when vaulting sessions occur (on which
days and at what time of day) by configuring a NetBackup Vault policy. The
schedule in the Vault policy determines when vaulting sessions occur.
A vaulting session executes a specific profile. The profile determines which tasks
are performed during a particular session. Each profile can be configured to run
any or all of the Vault processes:
• Duplication
• Catalog backup
• Ejection of media
• Reporting
If you configure Vault to perform duplication and backup jobs to run overnight,
consider running your vaulting sessions during the day to minimize demand on
hardware resources.

Vault reports
The reports are one of the most powerful components of the Vault option.
Numerous Vault reports exist to help you track incoming and outgoing media,
inventory, lost or missing tapes, and disaster recovery. This slide shows a few of
the many reports Vault offers. The reports on the slide are commonly run during
each vaulting session.

8–49
Vault Management
As a NetBackup option, you perform Vault operations using the NetBackup
Administration Console, to configure:
• Offsite volume pools
• Vault robots
• Vaults
• Vault profiles
• Vault policies

8

8–51

Lesson 9
Protecting the NetBackup Configuration

345

9
Introduction to NetBackup catalogs
NetBackup catalogs are files that contain information about the NetBackup
configuration and information about client backups. The information in the
catalogs includes records of the files that have been backed up and the media on
which the files are stored. The catalogs also contain information about the media
and storage devices.
• Describe the location of NetBackup catalog backups.
• Explain the importance of catalog backups.
Protecting the NetBackup catalogs

NetBackup catalogs are vitally important to the success of a data protection plan.
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:
• Remove tapes immediately following the (successful) backup of the catalogs.
• Make at least two copies of the catalog backup images.
• Store one copy of the catalog backup offsite.

347 Lesson 9 Protecting the NetBackup Configuration Copyright © 2012 Symantec Corporation. All rights reserved.
9–3
NetBackup catalog components
The NetBackup catalogs reside on the disk of the NetBackup master server. The
catalogs consist of the following components:
• The image database
• Configuration files
• The NetBackup database (NBDB)
The NetBackup database is commonly called the Enterprise Media Manager
(EMM) database.

9
The image database
The files stored in the image database are very important. These files contain
information about backups that have been performed. Although its name implies
that it is a database, the image database is actually flat files located on the master
server disk. The image database contains subdirectories for each client that is
backed up by NetBackup, including the master server and any media servers.
The image database files are located at
/usr/openv/netbackup/db/images/client_name/ctime (UNIX)
or install_path\NetBackup\db\images\client_name\ctime
(Windows).
The image database contains the following files:
• The Image files are files that store only backup set summary information.
• The .lck files are files used to prevent simultaneous updates on images.
• Image .f files are files that are used to store the detailed information about
each file backup.
• 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.
Pre-NetBackup 6.x image database formats
If you are upgrading from older versions of NetBackup that use ASCII format
catalog files, convert your old catalog files from ASCII to binary by using the
cat_convert utility to save space.

9–5
Configuration files
The configuration files consist of directories that also contain flat files located on
the master server disk. The directories for the configuration files are located at
/usr/openv/netbackup/db (UNIX) or
install_path\NetBackup\db (Windows).
The directories that comprise the configuration files include:
• class
The files in the four class directories contain policy information.
• client
The client directory contains master server client attributes.
• cltmp
The files in the cltmp directory contain temporary policy information.
• config
The files in the config directory contain information about host properties
and data classification properties.
• DBVERSION
The DBVERSION file contains NetBackup version information.
• error
The error directory contains some of the activity logs.
• failure_history
The failure_history directory contains a list of failed backups.
• IDIRSTRUCT
The IDIRSTRUCT directory identifies where to place the backup image files.
The default value is 2, which uses the following location:
– UNIX:
/usr/openv/netbackup/db/images/client_name/ctime
– Windows:
9
install_path\NetBackup\db\images\client_name\ctime
• images
The images directory contains the image database, which was discussed
previously.
• jobs
The jobs directory contains information about jobs that have run.
• media
The media directory is a temporary area for media activity.
• sched
The sched directory contains staging properties.
• ss
The ss directory contains storage lifecycle policy information.
• vault
The vault directory contains Vault properties.

351 Lesson 9 Protecting the NetBackup Configuration
9–7
Backup header information (stored in NBDB)
In previous versions of NetBackup, the image metadata was stored in both the
NetBackup database (NBDB) and in flat ASCII files (in the NetBackup/db/
images directory) for many types of storage units and policies. In NetBackup
7.5, the image metadata is stored only in NBDB, providing performance
improvements for restores, policy scheduling, and image cleanups.
Upon upgrade, the image metadata is automatically migrated from the old format
to the new format. That is, the image metadata in existing EMM tables is merged
with flat files and moved to new DBM tables in \NetbackupDB\data.
You can use the cat_export command to export image metadata from the
NBDB to a flat ASCII file. This slide shows the flat file created from running the
cat_export command.
Using the cat_export command

Use the cat_export command to export image metadata from NBDB or a
staged copy of NBDB to flat ASCII image header files in a target directory. This
command organizes the data into a directory hierarchy based on the hierarchy that
is used in the NetBackup database. One flat file is created per backup image.
Images are exported to the following directory:
• Windows:install_path\NetBackup\db.export
• UNIX: /usr/openv/netbackup/db.export
For more information about the cat_export command, see the Symantec
NetBackup Commands Reference Guide and the Symantec NetBackup
Troubleshooting Guide.
9
The NetBackup database (NBDB)
The NetBackup database (NBDB) is created during the installation of the master
server. The NBDB stores information used by both the system and the EMM
server. The NBDB runs on Sybase SQL Anywhere.
Note: The NBDB is commonly called the EMM database.
Database files
The EMM database consists of database files and is supported by configuration
files and a transaction log. The following table describes the database files and
their locations.
File Name Description

The following files are located at /usr/openv/db/data (UNIX) or
install_path\NetBackup\NetBackupDB\data (Windows).
NBDB.db This database is the main NetBackup database file. NBDB.db
is considered a dbspace.
NBDB.log This log file is the transaction log for NBDB. This log is
required for database recovery. NBDB.log is truncated after
a successful full or incremental catalog backup.
EMM_DATA.db This database is the EMM database file. The EMM_DATA.db
is also considered a dbspace.
EMM_INDEX.db This database is used to enhance EMM database performance.

9–9
File Name Description
DARS_DATA.db This database is used by the Database Agent Request Service
(DARS) for Oracle database recovery and cloning purposes.
DBMS_DATA.db This database is used as an image change log by NBSL for the
OpsCenter reporting interface. This captures major changes in
backup images that occur when they are added, duplicated, or
expired by the NetBackup Database Manager (bpdbm).
JOBD_DATA.db This is an additional dbspace that contains job records data.
NBAZDB.db This is the NetBackup Authorization database that is present
regardless of whether NetBackup Access Control (NBAC) is
used.
SEARCH_DATA.db This contains the indexing configuration and the metadata
that is created while indexing or placing holds on backup
images. This data is required for the NetBackup Search
functionality.
SEARCH_INDEX.db This contains the indexes that are created in the
SEARCH_DATA tables.
vxdbms.conf This file contains configuration information specific to the
database server installation as follows:
• VXDBMS_NB_SERVER = VERITAS_NB_
server_name
• VXDBMS_NB_PORT = 13785
• VXDBMS_NB_DATABASE = NBDB
• VXDBMS_BMR_DATABASE = BMRDB
• VXDBMS_NB_DATA = /usr/openv/db/data
• VXDBMS_NB_INDEX = /usr/openv/db/data
• VXDBMS_NB_TLOG = /usr/openv/db/data
• VXDBMS_NB_PASSWORD = encrypted_password
By default, encrypted_password is set to nbusql.
The following files are located at /usr/openv/var/global (UNIX) or
install_path\NetBackup\NetBackupDB\conf (Windows).
server.conf This is the configuration file that contains configuration
information for the NetBackup database (NBDB).

CAUTION: Do not edit this file unless directed and assisted
by Symantec Technical Support. Editing this file may prevent
NetBackup from starting.
databases.conf This is the configuration file that contains the locations of the
main database files and the database names for automatic
startup when the NetBackup database (NBDB) is started.

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:
9
• 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 Symantec
NetBackup: Maintain and Troubleshoot course.

9–11
Managing images
• Describe the difference between image retention and image expiration.
• Import expired images.
Media life cycle (1 of 5)

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.
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 selects a tape from the scratch pool.
Note: Tapes in the scratch pool do not have any valid images on them.
The example on this and the following slides shows the life cycle of a tape—from
unassigned, to assigned, and then unassigned again.
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
After the first backup is written to the tape, the EMM database is updated to
indicate the following:
• The tape is now assigned.
• There is one valid image.
• The retention level of the backup is 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.
Note: Image1 and Image1.f are sample names. The actual name of the image in
the database is policyname_ctime_schedule.

At the end of each backup, an end of file (EOF) marker is written. This informs
NetBackup where to begin writing the next backup on this tape. The EOF marker
is overwritten by the backup header of the next image.
When the second image is written, the EMM database updates the valid image
field to indicate that there are now two images on the tape. The NBDB and Image
databases are also updated with the metadata of the second image.
When the third image is written to the tape, the EMM updates the valid image field
to reflect the third image. The NBDB and Image databases are also updated with
the metadata of the third image.
9–13
In this example, the third backup is written to the end of the tape. The media state
is now set to FULL.

9
It is the responsibility of the image cleanup job to determine which images have
met their retention period and are expired. Expired images need to be cleaned out
of the databases.
In this example, two weeks have passed from when the first image was written.
Therefore, Image1 has met its retention level and is ready to be expired.
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.
When the images expire, the EMM database is updated to reflect the number of
valid images that are still being tracked on this tape.

9–15
After all the images are expired and the EMM database indicates there are no
longer any valid images associated with the media ID, the media state is set to
AVAILABLE, the media is returned to the scratch pool, and the media is set to
unassigned. 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 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,
third-party software is required to extract the data from the tape.

9
The Images on Media report
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.

9–17
Searching for backup images
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 will learn how to perform all of these operations in this lesson.
You specify the specific search criteria that NetBackup is to use to build a list of
backups from which you can make your selections.

9
The NetBackup verification process
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.

9–19
Verifying backup images using the Administration Console
To verify a backup image from the NetBackup Administration Console:
1 In the ojbect 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 may see a Confirm Verify message window, which gives you the option
to log all files found in verified images.
4 Click OK to continue.

9
Confirming the verify results
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.

9–21
Comparing volume expiration and image retention
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
Volume expiration and image retention in the Administration Console
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–23
Expiring a backup image
To expire a backup image:
1 In the ojbect tree pane of the NetBackup Administration Console, select
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 that you want to expire and select Expire.
A message is displayed informing you that after the backups have been
expired, they cannot be used for restores.
4 Click Yes to proceed with expiring the image.
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.
Using the bpexpdate command to expire a backup image

To change the expiration date of a single backup, use the bpexpdate command:
bpexpdate -backupid backup_id -d date | 0 | infinity
[-client client_name] [-copy number] [-force]
[-M master_server[,...,]]

9
Importing backup images
NetBackup can import backups that have expired, backups from another
NetBackup domain, or backups that were written by Backup Exec (7.0 through
9.1). For more information about importing backups that were written by Backup
Exec, see TechNote 56544: Statement of support for the importing of Backup Exec
images in NetBackup using the Backup Exec Tape Reader at:
http://www.symantec.com/docs/TECH56544.
During an import operation, NetBackup re-creates NetBackup catalog entries for
the backups on the imported volume. Importing is useful for moving volumes from
one site to another and for re-creating NetBackup catalog entries.

9–25
Phase I: Initiating the import
The result of initiating Phase I of the import process is to create a list of expired
images from which to choose to import in Phase II. No import operations occur in
Phase I.
CAUTION Symantec strongly recommends that you physically write-protect

media before adding it to a tape library to perform an import.
Preparing to import
If you are importing Backup Exec media, run vmphyinv to update the Backup
Exec media GUID in the NetBackup Media Manager database. This needs to be
performed only once after creating the media IDs in the NetBackup Media
Manager database. Additionally, this command can be used to perform a “physical

inventory” when the recorded media ID may be different from the external media
ID (the bar code label), due to media ID generation rules. See the Symantec
NetBackup Commands Reference Guide for more information about using the
vmphyinv command.
If you are importing images from tape, make the media accessible to the media
server from which the images will be imported.
For NetBackup to generate a list of images, add the media IDs that have the
backups to Media Manager on the server where you are going to import the
backups.

How to initiate the import
Use the following procedure to initiate the import:
1 In the NetBackup Administration Console, expand NetBackup Management
> Catalog.
9
2 Select Actions > Initiate Import.
The Initialize Import dialog box is displayed.
3 Complete the Initialize Import dialog box as follows:
a In the Media Server field, specify the name of the host that contains the
volume you are going to import.
b Select whether the images to be imported are located on tape or on disk.
If images are on tape:
› In the Media ID field, type the Media ID of the volume that contains
the backups you are importing.
› Mark the The media for the import is password protected Backup
Exec media check box if you are importing password-protected
Backup Exec images. Validate the Backup Exec password by typing it
in the field provided.
If images are on disk:
› Enter the parent directory of the images in the field provided.
› If the image is on a NearStore server, mark the NearStore check box
and enter the name of the NearStore server in the field provided.
› Note that only disk backup images written in NetBackup 6.0 or later
may be imported.
c Click OK.
The Confirm Initiate Import (UNIX) or the Catalog (Windows) dialog
box is displayed.
4 Click OK to start the process of reading the catalog information from the
source volume.

9–27
Generating a list of images
5 Click the Results tab to watch as NetBackup scans each image on the tape and
determines whether an image record already exists and can 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.

9
Phase II: Searching for and selecting images to import
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.

9–29
Importing the selected image
3 Select the images you want to import and select Actions > Import.
The Confirm Import dialog box is displayed.
4 Click OK.

9
Confirming the import results
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 01/28/2012 at 9:00 A.M, the expiration date of the imported image is
2/11/2012 at 9:00 A.M.

9–31
Summary of image-related tasks
The table on this slide summarizes the image-related tasks that you can perform.
See the Symantec NetBackup Administrator’s Guide for more information about
these tasks.

9
Performing catalog backup operations using the wizard
A catalog backup backs up the components that comprise the NetBackup catalog
(image database, configuration files, EMM database). A catalog backup also
collects disaster recovery information.
After completing this topic, you will be able to back up your NetBackup catalogs
using the NetBackup Catalog Backup Wizard.
Catalog backups
Catalog backups can be run just like normal backups, and can be run online, while
NetBackup is performing other tasks and standard backups and restores.
Additionally, catalog backups can run both full and incremental types of 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
can be configured to create a disaster recovery file. This file, which can be
automatically e-mailed to the NetBackup administrators, outlines instructions for
performing a catalog restore and identifies the required tapes.
Catalog restores
Catalog restores can be performed from the NetBackup Administration Console or
from the command line. A catalog restore has one prerequisite—that NetBackup
server software is already installed on the machine where the restore is to take
place.

9–33
The catalog backup process
Symantec best practice is to schedule catalog backups to run regularly, in case of
failures with the master server or the master server catalogs and databases.
Additionally, run manual catalog backups prior to and immediately after any
upgrade, including patch upgrades.
In addition, ensure that there is enough space available for the transaction log
(NBDB.log) because this log can grow fairly large.
This graphic describes what happens during a catalog backup. A parent job starts
the backup process.
1 A child job copies the NBDB files to /usr/openv/db/staging (UNIX)
or install_path\NetBackupDB\staging (Windows).
2 A child job starts, which backs up the files from the staging directory or folder
to the storage unit specified in the catalog backup policy. This job backs up the
files in a single stream. The files do not remain in the staging directory or
folder; they are deleted automatically.
3 Another child job starts, which backs up the NetBackup catalog files. This
includes the Image database, policies, configuration, and other catalogs on the
master server. This includes the following directories:
– UNIX:
›/usr/openv/netbackup/db
›/usr/openv/var
›/usr/openv/netbackup/vault
›/usr/openv/var/global
– Windows:
›install_path\NetBackup\var
›install_path\NetBackup\db
›install_path\NetBackup\vault
9
Note: If you watch a catalog backup in the Activity Monitor, the job details
show the file list as CATALOG_DRIVEN_BACKUP.
4 After the catalog backup completes, the transaction log (NBDB.log) is
truncated to clear database transactions that were backed up.
5 During the next catalog backup, the files in the staging area are overwritten.
Until they are overwritten, they can be used for disaster recovery.
In previous versions of NetBackup, the files in the staging directory were
deleted at the end of the successful catalog backup.

9–35
Configuring the catalog backup using the NetBackup Catalog Backup
Wizard
Catalog backups only write to media in the CatalogBackup volume pool. When
you use the NetBackup Catalog Backup Wizard to configure a catalog backup, it
is assumed that a storage device is configured and that media is available in the
CatalogBackup volume pool.
To use the NetBackup Catalog Backup Wizard to configure a catalog backup:
1 In the NetBackup Administration Console, in the ojbect tree pane, click
NetBackup Management.
2 In the details pane, click Configure the Catalog Backup to launch the
NetBackup Catalog Backup Wizard.
Click Help within any wizard panel for more information on the wizard settings.

9
Welcome to the NetBackup Catalog Backup Wizard
3 Click Next on the Welcome panel.

9–37
Confirm existing catalog backup policies
4 On the NetBackup Catalog Backup Policy panel, select a policy from the list
of existing catalog backup policies, or, to create a new catalog backup policy,
mark the Create a new catalog backup policy check box. Click Next.

9
Specify the catalog backup policy name
5 In the Policy Name and Type panel, enter the policy name. Notice that NBU-
Catalog is automatically selected as the policy type. Click Next.

9–39
Set the backup schedules
6 On the Backup Types panel, select the backup type. The User Backup type
does not apply for NBU-Catalog policies. Click Next.

9
Set the frequency and retention
7 On the Frequency and Retention panel, select the rotation schedule. By
default, a frequency-based schedule is selected. A frequency-based schedule
ensures that the catalog backup has an opportunity to run in busy environments
where backup jobs are running.
The After each backup session radio button refers to a period when no regular
backup policy is running. Catalog backups can be scheduled to run
concurrently with other backup types on the master server.
Click Next.

9–41
Set the start window
8 In the Start Window panel, define a window of time during which the catalog
backup can start, and click Next.
The Scheduled window options (Off hours, Working hours, All day, and
Custom) are preset in the wizard. To change these settings, complete the
wizard and then edit the policy using the Policies utility.

9
Specify the disaster recovery file location
9 On the Catalog Disaster Recovery File panel, enter the path where each
disaster recovery image file can be saved on disk. The image file contains the
disaster recovery information. Enter the logon and password information, if
necessary.
Symantec recommends that you save the image file to a network share or a
removable device. Do not save the disaster recovery information to the local
computer.
Click Next.

9–43
Specify the disaster recovery e-mail information
Symantec recommends that you configure the NetBackup environment to send the
disaster recovery information to a NetBackup administrator. This backup-specific
information is sent after every catalog backup.
10 On the E-mail Disaster Recovery Information panel, enter one or more
addresses. To send the information to more than one administrator, separate
multiple e-mail addresses using a comma as follows:
email1@domain.com,email2@domain.com
Ensure that e-mail notification is enabled in your environment.
Note: The disaster recovery e-mail is not sent to the address that is specified in
the Global Attributes properties. The Administrator’s e-mail Address in the
Global Attributes properties specifies the addresses where NetBackup sends
notifications of scheduled backups or administrator-directed manual backups.

9
Wizard completion notice
11 The final panel of the wizard informs you that after the policy is created, you
can make changes in NetBackup Management > Policies. Click Finish to
create the policy.

9–45
The catalog backup job
The screen shot on this slide shows NetBackup Activity Monitor with the catalog
backup job running.

9
The disaster recovery e-mail
When you perform a catalog backup, a disaster recovery e-mail is sent if it has
been configured. When you need to recover your catalog, use the information in
the disaster recovery e-mail.
This screen capture shows only a portion of the disaster recovery e-mail.

9–47
Disaster recovery strategies
• List the steps that are required to recover from a disaster situation.
• Recover the NetBackup catalog using the wizard.
Catalog recovery options

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.
• Optimized duplication enables quick duplication jobs by only transferring
unique data from source to destination storage pools. To take advantage of
optimized duplication, OST-compliant hardware, such as PDDO or MSDP, and
the Data Protection Optimization license key are required.

• Auto Image Replication enables the duplication of NetBackup catalog backup
images and other important data 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.

9
General recovery procedure
The table on this slide shows the general procedure to follow to recover your
catalogs.
Note that when recovering the NetBackup catalogs, recovering all the catalogs
(image database, configuration files, EMM database) is strongly recommended.

For more information on how to restore your NetBackup catalogs, see the
Symantec NetBackup Troubleshooting Guide and attend the Symantec NetBackup:
Maintain and Troubleshoot course.

9–49
Optimized duplication
Optimized duplication is the process of copying backup images from one Media
Server Deduplication Pool (MSDP), PureDisk Deduplication Option (PDDO) Pool
or NetBackup Appliance to an MSDP, PDDO, or NetBackup appliance. The
source and the destination must use the same NetBackup master server and media
server. The optimized duplication operation is more efficient than normal
duplication because only unique, deduplicated data segments are transferred.
Optimized duplication reduces the amount of data that is transmitted over your
network.
For more information about optimized duplication, see HOWTO Article 70634:
About MSDP optimized duplication and replication at:
http://www.symantec.com/docs/HOWTO70634.

9
Auto Image Replication overview
Auto Image Replication is a NetBackup feature that enables the duplication 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),
PureDisk Deduplication Option (PDDO), and NetBackup appliances
• Storage vendors that support and are qualified for OST
Auto Image Replication is also sometimes referred to as duplication to remote
master.
After an image has been duplicated 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.
Duplication to a remote master 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.

9–51
How Auto Image replication works
Auto Image Replication works by going through the following basic steps:
1 Run and create a backup image in the source domain.
2 Duplicate the backup image to the target domain.
This duplication uses 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 duplications to other remote master
servers.

9
Catalog recovery methods
The slide shows two functionally equivalent methods for performing catalog
recovery. This topic covers performing a catalog recovery using the Netbackup
Catalog Recovery Wizard.
Disaster recovery guidelines

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 and after
the recovery.

9–53
Recovering the catalog using the NetBackup Catalog Recovery
Wizard
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.

9
Welcome to the NetBackup Catalog Recovery Wizard
2 Click Next on the Welcome panel to display the Catalog Disaster Recovery
File panel.

9–55
Locate the catalog disaster recovery file
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.
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.

9
Retrieve the disaster recovery file
4 When the required media sources are all found, click Next to display the
Disaster Recovery Method panel.

9–57
Select the disaster recovery method
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.

9
Wait until the recovery job finishes
NetBackup restores the entire NetBackup relational database, which includes the
following:
• NBDB database (including the EMM database)
• BMR database (if applicable)
• NetBackup policy files
• Backup image files
• Other configuration files
If the EMM server is located on a remote computer, the NBDB database is
recovered on the remote computer.
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 (NBDB and optionally
BMRDB) have been restored and recovered.
7 Click Next to continue to the final panel.

9–59
Recovery completion message
8 Click Finish in the final panel.
9 Stop and restart NetBackup on all the servers.

9
Unfreezing frozen media
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 master_server

9–61
Partially successful image cleanup as a catalog backup warning
The image cleanup job returns a partial success exit code of 1 if a catalog backup
job is not configured. The text in the job details provides a warning about setting
up a catalog backup policy.
After a catalog backup policy is configured, this warning is no longer displayed.

9
Catalog-related tips
After completing this topic, you will be able to diagnose common catalog-related
issues.
Moving the image database (UNIX)

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.
This ensures 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/bpps
3 Terminate bprd and bpdbm by using the Activity Monitor or enter:
/usr/openv/netbackup/bin/admincmd/bprdreq -terminate
/usr/openv/netbackup/bin/bpdbm -terminate
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 services.

9–63
Moving the image database (Windows)
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.
This ensures 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 jobs are running, either wait for them to end or stop them by using the Jobs
tab in the Activity Monitor.
3 Terminate the Request Manager (bprd) and Database Manager services
(bpdbm) by using the Services tab in the Activity Monitor.
This prevents 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.
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
9
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 will be 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 Start the NetBackup request manager and NetBackup database manager
services by using the Services tab in the Activity Monitor.
Backups and restores can now resume for the client.

9–65
Catalog reporting tools
The table on this slide summarizes how catalog-related information can be
managed using the NetBackup Administration Console (GUI), NetBackup
commands (CLI), and OpsCenter.

9
9–67


Symantec Netbackup Education - 100-002701-A

Uploaded by

Document Information

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

Symantec Netbackup Education - 100-002701-A

Uploaded by

Copyright:

Available Formats

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

Lesson 1: Introducing NetBackup

Lesson 2: Installing NetBackup

Lesson 3: Using the NetBackup Administrative Interfaces

Lesson 4: Configuring Tape Storage and Media

Lesson 5: Configuring Disk Storage

Verifying disk storage ................................................................................. 5-30

Lesson 6: Configuring File System Backups

Lesson 7: Performing File System Backups and Restores

Lesson 9: Protecting the NetBackup Configuration

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

image copies, application and database backups, virtual machine backups,

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

Symantec NetBackup 7.5: Install, Configure, and Deploy

Lesson 1: Introducing NetBackup

Lesson 2: Installing NetBackup

Lesson 3: Using the NetBackup Administrative Interfaces

Lesson 4: Configuring Tape Storage and Media

CONFIDENTIAL - NOT FOR DISTRIBUTION

Lesson 6: Configuring File System Backups

Lesson 7: Performing Backups and Restores

Lesson 8: Protecting Backup Data

Lesson 9: Protecting the NetBackup Configuration

Symantec NetBackup 7.5: Manage and Administer

• Managing and optimizing disk storage

CONFIDENTIAL - NOT FOR DISTRIBUTION

• Protecting the backup data and configuration

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

Symantec Connect is responsive to the needs of Symantec customers. Features of

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

NetBackup component definitions

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

unavailable for further use.

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

cumulative incremental backup, and all differential incremental backups that

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

CONFIDENTIAL - NOT FOR DISTRIBUTION

Online agents and options resources

CONFIDENTIAL - NOT FOR DISTRIBUTION

NetBackup Bare Metal Restore (BMR)

CONFIDENTIAL - NOT FOR DISTRIBUTION