Академический Документы
Профессиональный Документы
Культура Документы
1:
Administration –
Lesson Book
THIS PUBLICATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE
EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC
SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE
FURNISHING, PERFORMANCE, OR USE OF THIS PUBLICATION. THE INFORMATION CONTAINED HEREIN
IS SUBJECT TO CHANGE WITHOUT NOTICE.
No part of the contents of this book may be reproduced or transmitted in any form or by any means
without the written permission of the publisher.
For specific country offices Veritas World Headquarters © 2018 Veritas Technologies LLC. All
rights reserved. Veritas and the Veritas
and contact numbers, please 500 East Middlefield Road
Logo are trademarks or registered
visit our website at Mountain View, CA 94043 USA
trademarks of Veritas Technologies LLC
www.veritas.com. +1 (650) 933 1000 or its affiliates in the U.S. and other
www.veritas.com countries. Other names may be
trademarks of their respective owners.
ii
Not for Distribution
Table of Contents
Course Introduction
Course Introduction .............................................................................................................. Intro-2
Table of Contents v
Course Introduction
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Course Introduction” in the “Veritas NetBackup 8.1: Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
For additional information about topics not covered by this course, see the “Veritas
Education’s core data protection curriculum for NetBackup” section of this introduction.
Course prerequisites
Students attending this course should be familiar with:
• UNIX or Windows system administration
• Storage area network (SAN) concepts
• Data protection concepts and terminology
After completing this course, you will be able to perform the tasks listed on this slide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The lessons covered in the NetBackup 8.0 Administration course are shown on the slide.
The course is structured by going through a number of general steps:
Lessons 1-5 set the framework for understanding NetBackup, covering basic concepts
such as storage units, backup policies, and how to perform backups and restores of file
systems.
Lessons 6-9 show how to configure and manage various storage types, including
AdvancedDisk, NetBackup deduplication, and tape libraries.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Lessons 10-11 cover the protection and recovery of virtual machines, highlighting
VMware backup and recovery in detail.
Lesson 12 covers duplicating backups, and storage lifecycle policies (SLP) specifically.
Lesson 13 discusses the management of backup images and protection of the
NetBackup catalog.
Lesson 14 covers many features to optimize backups to file systems through change
tracking, and other NetBackup features.
Lesson 15 shows how to collect logs and other diagnostic information, setting the
ground work for troubleshooting, and contacting Veritas Support.
Virtual On-Demand Training (VODT) combines video, recorded lectures with on-
demand, remote access to hands-on labs and access to experts upon request.
VODT includes the following:
• On-demand labs: Lab access for 45 days, which includes a varying amount of lab
hours depending on course length and course content.
• Recorded video lectures: Access to videos for the duration of the offering, which
includes the recordings of expert instructors.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Participant guide and lab guide PDFs: Equivalent to the same content and books
used and provided in Instructor-Led Training (ILT) and Virtual Instructor-Led Training
(VILT).
• Self-help lab resources: Includes introductory videos for the VODT environment and
that specific course, and also includes Frequently Asked Questions (FAQs)
documents.
• Ask the Experts: Ability to ask questions to expert Instructors and Subject Matter
Experts via email.
• User Support: Email support for user access or technical issues in running labs or
videos.
For more information on how Virtual On-Demand Training works, view the VODT
datasheet, found online on the Veritas Education website at
https://www.veritas.com/services/education-services/vodt-course-list.
The Veritas Open eXchange allows customers and users of Veritas products to network
get help and learn more about industry-leading solutions. Veritas Open eXchange is a
customer-focused resource, intended to help you design and implement a utility
computing strategy to provide availability, performance, and automation for your
storage, servers, and applications.
Veritas Open eXchange provides the following resources:
• Technical documents, such as articles, white papers, and product specs
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Interactive services, such as the discussion forum, where members can discuss
current topics, share tips and tricks, and help one another troubleshoot problems
Best of all, it is free. Sign up to become a member at https://vox.veritas.com/.
Veritas Services and Operations Readiness Tools (SORT) is a set of Web-based tools that
optimizes the end to end experience for Veritas products, such as Storage Foundation
and NetBackup.
SORT for NetBackup provides information on whether your environment is compatible
with a NetBackup installation or upgrade, and gives you links to the latest
documentation and software.
SORT for NetBackup is available at http://sort.veritas.com/netbackup.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Intro-8
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
Topic Objective
Data Protection and the NetBackup Discuss considerations for data protection, and identify the
Environment components of a NetBackup environment and their functions.
Define common terms used in the NetBackup product, and describe
NetBackup concepts
how NetBackup backs up and restores data.
Using the NetBackup Administration
Navigate the NetBackup Administration Console.
Console
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to discuss considerations for
data protection, and identify the components of a NetBackup environment
and their functions.
After completing this topic, you will be able to discuss considerations for data
protection, and identify the components of a NetBackup environment and their
functions.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
needed.
• Because you must be able to scale up your solution to manage your entire
organization, simple automated policies that maintain efficient, organized records
that can be readily accessed and used are essential. Also, the backed up data and
these metadata records must be protected against damage or loss.
A variety of technologies are available, and usually a combination of techniques
provides the best solution.
The Veritas NetBackup product suite provides a rich set of tools and technologies that
address these issues.
Synchronous Clustering
Traditional replication
Snapshot Standard
backups Asynchronous technologies restore
Snapshot replication
technologies Bare Metal
Restore
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.
Recovery
methods Retention
period
A data protection plan outlines the importance of an organization’s data, and the
methods used to protect it. The plan is based on service level agreements (SLAs), which
define factors such as your recovery point objective and recovery time objective.
By defining data protection in terms of recovery, you are able to build a backup strategy
to support the data protection plan.
The backup strategy should take into account factors such as:
• The number and types of systems and applications in an environment
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The systems that have data to be backed up are called clients. Veritas NetBackup Client
software must be installed on each client.
Veritas NetBackup server software that controls the environment and accesses backup
storage devices comes in a few different flavors. A single host can provide more than
one of these server roles.
• The master server controls the backup and recovery activities for the clients
assigned to it. Master servers track what files are backed up to which backup media.
Additionally, the master server centralizes services that manage and allocate the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
resources required for all NetBackup operations. This includes the NetBackup
database (sometimes abbreviated as NBDB), which centralizes information about
the backup environment. The NBDB is shown on the slide as a dual-colored cylinder,
next to the master server.
• Media servers have some form of storage attached to them—either directly or
through the network. Media servers perform the writing and reading of data to and
from media (disk or tape). They combine clients’ data into GNU tar files called
backup images. One master can control several media servers.
• Clients include all hosts that have data backed up, including the media server and
master server themselves. Clients can be both physical servers, or virtual servers. In
many cases the NetBackup client software is installed on the client system, however
in some cases, such as with virtual machines, the NetBackup client software may not
be necessary.
Media
Clients servers
NetBackup domain
Clients
Client data
Backup data
Resource Management NetBackup domain
The NetBackup server software supports two hierarchies, determined by your need, but
differentiated by the license purchased.
• NetBackup Server is a specific product licensed for smaller environments, where a
single computer plays the role of both the master server and media server.
OpsCenter may also be installed on this system as well.
• NetBackup Enterprise Server serves the needs of larger enterprises, because it
enables you to spread the load among multiple media servers controlled by a
separate master server. A NetBackup Enterprise Server license is required for each of
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Master
servers
Clients
10
The collection of clients and media servers managed by a single master is called a
NetBackup domain. NetBackup domains can be segregated based on geographic,
organizational, performance, or administrative reasons.
Sometimes you want to segregate clients into distinct collections for administrative or
performance reasons.
• With NetBackup, you can put each of these separate client groups in its own
NetBackup domain. Each domain has its own master and collection of media
servers.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• A single OpsCenter server can communicate with every master server and so help
you coordinate all of your NetBackup domains.
After completing this topic, you will be able to define common terms used
in the NetBackup product, and describe how NetBackup backs up and
restores data.
11
After completing this topic, you will be able to define common terms used in the
NetBackup product, and describe how NetBackup backs up and restores data.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Schedules When do backups occur? Include all data or only changes? How long is backup data retained?
Backup
Which data is backed up?
Selections
Application-
How are database backups handled? How are virtual machine backups handled?
specific tabs
12
Policies define the rules that NetBackup follows when data from clients are backed up.
A backup policy can apply to one or more clients. The best approach is to divide clients
into groups according to the backup requirements, and creating a policy for each group.
In a policy you define attributes, schedules, a client list, and a backup selections list.
• Attributes answer questions, such as: How should the files be backed up? Are there
any special backup behaviors? Where is the backup storage location?
• Schedules answer: What is the backup time and type? On which schedule should
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Tapes
Disk
Client’s
backup data
(in an image)
Local SAN NetBackup appliance
disk storage or OST-based storage
Cloud
13
The backup data from a client is stored as a backup image, and must be saved
somewhere.
Removable media, such as tape, is very cost effective. Robotic libraries automate
operation, and can be shared to provide redundancy and efficient allocation of
resources. Although disk is becoming more popular, removable media still serves a
valuable purpose, such as for long term or off-site storage. Additionally, many modern
tape libraries and removable media devices have competitive performance with disk.
Images can be stored on local or networked disks for rapid access, but increasingly
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
complex permanent storage solutions are built around disk – such as deduplication –
which can be used alone, or in combination with removable media. You can configure
NetBackup to implement and maintain these optimized solutions.
If you have an account with a supported cloud storage service, NetBackup can store
your images there efficiently and safely.
Master server
NetBackup
catalog
14
NetBackup catalogs are information stores that contain information about the
NetBackup configuration and backups, including records of the files that have been
backed up and the media on which the files are stored.
The NetBackup catalogs reside on the NetBackup master server and consist of the
following components:
• The NetBackup database (NBDB) is a relational database that uses SAP SQL
Anywhere. The NBDB stores data for several NetBackup services, including media
and device data, backup image headers, authentication and authorization. Bare
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Metal Restore (BMR) data is also stored in a Sybase database if the BMR option is
used. Because the first service to use the relational database was the Enterprise
Media Manager in earlier releases of NetBackup, the database is sometimes
referred to as the EMM database.
• The NetBackup configuration files include policies, schedules, and other files used by
NetBackup. These are sometimes referred to as flat files because they are not stored
in a relational database, and are stored in simple files on the file system of the
NetBackup master server.
A critical NetBackup component is the image database, which stores backup image
metadata. This metadata is stored in two locations: the image header data is stored in
the relational database (NBDB), and the image file list is still stored as flat files in the
NetBackup configuration files. Because the image file lists contain the path to every file
backed up, this is usually the largest component of the NetBackup catalogs.
NetBackup
logs and NetBackup
reports 4
master
1 server and
catalog
NetBackup
3
media
server
2
NetBackup Storage
Client Backup
client destination
data image
15
Using NetBackup, you create policies and schedules for backing up data periodically
(such as every hour or every day). The policy and schedule information is maintained in
the NetBackup database. The policy identifies how the backups occur, where the
backups occur, when the backups occur, which clients are backed up, and which files
and directories are backed up from those clients.
The following flow is described on this diagram:
1. When a policy is run, the master server interprets the policy, allocates resources,
and connects to the requested media server.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2. The media server prepares the allocated storage resources and then passes on the
requirements of the backup to the client. The client processes the files to be backed
up and transfers them in the form of a tar backup image over the network to the
media server. The media server writes the file image to the allocated storage.
3. The media server also passes information about the backup to the master server
which then stores the information into the backup catalog.
4. During the backup status information is sent to the NetBackup master server, and
NetBackup keeps status information in various log files, enabling you to monitor or
report on the backup. Information is also pulled from the master server by the
OpsCenter server on a periodic basis, based on the OpsCenter configuration.
1
NetBackup
logs and NetBackup
reports 4
master
server and
2 catalog
NetBackup
media
server
3
NetBackup Storage
Client Backup
client destination
data image
16
No backup is worth anything unless the data it contains is available to be restored when
needed. Restores can be performed from the master server by an administrator to
restore the data to the destination client machine. Restores can also be performed at
the request of a user.
The restore flow is described in this diagram.
1. To restore data, use OpsCenter or the NetBackup Backup, Archive, and Restore
interface. The NetBackup master server catalog contains information on what files
and folders have been backed up, and provides the information that the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Virtual systems
Leading hypervisors including VMware vSphere and Microsoft Hyper-V
Storage systems
Data at the storage system level, integrating with snapshot, replication, and NDMP facilities from EMC,
HP, Hitachi, IBM, NetApp, and others
Cloud platforms
Backup and recovery of workloads within many cloud environments, including Microsoft Azure, Amazon
Web Services, Rackspace, and more
Refer to the NetBackup Master Compatibility List at http://netbackup.com/compatibility 17
After completing this topic, you will be able to navigate the NetBackup
Administration Console.
18
After completing this topic, you will be able to navigate the NetBackup Administration
Console.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Details pane
Object tree
area
19
• Details (right) pane, which on the slide contains the configuration wizards and
details specific to the utility that is selected in the object tree pane.
The default program location for the NetBackup Administration Console is
/usr/openv/java/jnbSA on UNIX, and for Windows is located as C:\Program
Files\Veritas\Java\nbjava.bat.
Note that the NetBackup Administration Console is not natively run on a NetBackup
appliance, even if that appliance is a NetBackup master server. Instead, install the
NetBackup Administration Console on a separate system, and remotely connect to it.
Always install the latest version of the NetBackup Administration Console software, and
use the correct version of the console for the version of the master server being
interacted with.
20
The Jobs tab in the Activity Monitor displays information about NetBackup queued,
active, waiting, suspended, incomplete and completed jobs. Functions you can perform
on jobs include canceling, suspending, resuming, or restarting a job.
The following tabs are visible in the details pane of the Activity Monitor:
• The Jobs tab: If you double-click a job listed under the Jobs tab, you obtain valuable
job detail information, including policy, file list, status, kilobytes written, number of
files written, percent complete, and start, elapsed, and end times, which are used to
derive kilobytes per seconds statistics.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• The Daemons tab: Provides status and control for those programs that typically start
whenever the system reboots.
• The Processes tab: Provides visibility to NetBackup process status.
• The Drives tab: Displays the status of NetBackup tape drives associated with the
NetBackup domain controlled by the master server being monitored.
21
This graphic shows the master server host attributes that can be configured on the
Global Attributes dialog box.
The Global Attributes properties apply to the currently selected master server. The
Global Attributes properties affect all operations for all policies and clients. The default
values are adequate for most installations but can be changed. Changes to Global
Attributes properties cascade across all component systems in the backup environment.
Note: See the Veritas NetBackup Administrator’s Guide for additional master server
properties.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
22
host properties (MEDIA_SERVERS in bp.conf) will not have permission to run these
commands.
On Windows, the default installation path for install_path is C:\Program
Files\VERITAS. To simplify command execution, append the paths shown on the
slide to your PATH environment variable.
Command Help
Command help is available as follows:
• UNIX: Use the online man pages and ensure that the MANPATH includes
/usr/openv/man or use the Veritas NetBackup Commands Reference Guide.
• Windows: Use the Veritas NetBackup Commands Reference Guide.
After completing this topic, you will be able to describe the NetBackup
appliance offerings.
23
After completing this topic, you will be able to describe the NetBackup appliance
offerings.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Optimized Hardware
Redundant Storage
24
• Hardware optimally configured by Veritas, with help from Intel, for NetBackup’s
predictable and consistent performance.
• Storage Foundation at no additional cost, which provides an industry-leading storage
management infrastructure, built for high-performance and resiliency.
• A Linux-based operating system, optimized for NetBackup and hardened by Veritas,
eliminating the cost of deploying and maintaining the operating system and
applications.
• A built-in WAN Optimization driver that provides the ability to replicate to
appliances on remote sites or to the cloud, up to 10 times faster over high latency
links.
• Symantec Data Center Security, which provides non-signature based Host Intrusion
Prevention, zero-day attacks, user and device controls, and more with, pre-defined
policies.
• Single patch updates that upgrade everything in the appliance.
Up to
1-250TB Up to 1374 TB*
1PB
Up to 1920 TB*
Up to 294TB
Media Server Cloud Catalyst
14TB-27TB 240TB
229TB
0.5-16TB
Media Server
4TB
Master/Media Media Server
Server Enterprise Appliance with storage Enterprise Appliance with storage
Master Server with storage
environments with smaller data protection requirements that require minimal on-site
infrastructure management expertise. Media server virtual appliances can scale up in
the number of instances and storage capacity to meet the growing requirement of
data protection in data centers. Either type of virtual appliance can replicate data to
other sites for disaster recovery.
• NetBackup 5240: A scalable integrated backup appliance that can function as either a
master or a media server and can scale from 4TB to 294TB of storage.
27
The NetBackup 5240 fulfills the needs of the low to mid-range performance and
capacity tiers in the NetBackup Appliance product line. It improves performance and
greatly increases the maximum capacity from the previous generation, the NetBackup
5230. As with the previous NBU52xx generations, the NetBackup 5240 appliance
supports internal storage as well as external storage shelves, and can be configured as
either media server, master server or both.
The NetBackup 5240 storage shelf supports SAS-3 as well as SES-3, significantly
improving bus speed as well as supportability. Each shelf formats to 49.14 TB. Since the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5240 supports up to 6 shelves, total storage options include 53 TB, 102 TB, 151 TB, 200
TB, 249 TB and 298 TB. This assumes the use of a 4 TB appliance, which is the norm
when using expansion shelves. The 14 TB and 27 TB appliances are designed to be used
as standalone appliances for environments which need more than 4 TB of dedupe
storage but less than 49 TB.
Compute Unit
• Has multiple I/O options: VERITAS 5340
(2U)
Number Type
4 1 GbE ports
✓ ✓
X X
Storage Shelf
• Storage options:
✓ ✓
X X
(5U)
Z Z
Z
✓
X
Z
TM
Z
X
Z (5U)
28
Enterprise scale NetBackup 5330 appliances start at 120TB of usable disk space and are
expandable up to 1920 TB making them ideal for large data centers.
NetBackup 5340 appliances can be deployed as media servers complementing either a
5240 appliance master server, or a traditional master server. addition to increased
capacity and performance, the 5340 has Dual RAID controllers and multiple data paths
to deliver greater data protection and system availability.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Software and appliance functionality is normally equivalent, but may not be identical
Compatibility • Refer to http://netbackup.com/compatibility, in the NetBackup Appliances section.
29
When licensing deduplication from Veritas, you pay only once for each TB of data
protected, regardless of how many copies you make. This can result in drastically
reduced costs for appliances, disk pools or tape libraries used solely to hold replicated
data.
Licenses are perpetual and transferable. Which means you don’t pay the cost of the
deduplication engine again every time you refresh hardware. It also means that existing
DPOO licenses for disk pools can be used if you migrate from legacy servers to
appliances.
Licenses are based on the amount of data you protect, not the capacity of the
appliance. Which means you can buy an appliance with extra storage capacity with an
eye towards future growth without paying for storage you are not using.
5230 Appliances can also be licensed as traditional Master or Media servers if, for
example, you will not be using the appliance to deduplicate any data.
After completing this topic, you will be able to navigate the OpsCenter
console.
31
After completing this topic, you will be able to navigate the OpsCenter console.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
32
33
To access the OpsCenter console, start a web browser on a system that has network
connectivity to the OpsCenter server. Type the following URL:
https://opscenterhost/opscenter where opscenterhost is the fully qualified domain
name of the OpsCenter server or the IP address of the OpsCenter server.
Note: If there is a conflict due to an already existing Web server (for example, IIS on
Windows), OpsCenter may have chosen a different port number to avoid conflict. The
default OpsCenter web address may use this non-default port number; for example:
https://opscenterhost:port/opscenter. For more information, see the NetBackup
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
34
Before you can use OpsCenter to monitor and manage your NetBackup environment,
you must configure data collection for NetBackup:
1. Add a master server to the OpsCenter console:
a. In the OpsCenter console, select Settings > Configurations > NetBackup.
b. Click Add, and fill in the fields. Optionally click the Test Connection button to
ensure the data is correct.
2. Enable data collection for a master server:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
a. Use the check box to select one or more master servers from the Master Server
Name column.
b. Click Enable Data Collection.
35
past 60 days; the licensed option has no limit on the age of reporting data.
This course only covers OpsCenter. For additional information on using OpsCenter
Analytics, see the Veritas OpsCenter Administrator’s Guide and Veritas Education’s
OpsCenter training.
Note: In prior releases of OpsCenter, the Java View Builder was only available with
OpsCenter Analytics. In OpsCenter 7.5 and later, the Java View Builder is included with
the base product.
• Key points
– In this lesson, you learned concepts about how to protect the data in your environment using
NetBackup.
– You are also aware of basic terms that relate to NetBackup, and can identify the major NetBackup
options and agents used to customize your backup environment.
– In addition, you learned to use the NetBackup Administration Console.
– Finally, you learned to describe the NetBackup Appliance offerings, and about the OpsCenter console.
• Reference materials
– NetBackup Administrator’s Guide
– NetBackup Release Notes
– NetBackup Commands Reference Guide
– NetBackup OpsCenter Administrator’s Guide
– http://www.veritas.com/support
36
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
37
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
38
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
39
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
40
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. True
B. False
41
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. True
B. False
42
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
43
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The correct answer is B. Basic OpsCenter functionality is included with NetBackup, and additional functionality can be
added by purchasing the OpsCenter Analytics option.
44
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-45
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Configuring NetBackup Storage” lesson in the “Veritas NetBackup 8.1:
Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
Define the terms storage device, storage unit, and storage unit
NetBackup storage device concepts
group.
Configuring and managing a basic
Configure and manage a basic disk storage unit.
disk storage unit
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to define the terms storage
device, storage unit, and storage unit group.
After completing this topic, you will be able to define the terms storage device, storage
unit, and storage unit group.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Storage device
• Physical tape and disk devices to which data is written to and restored from
Storage unit
It is important that you know the differences between storage devices, storage units,
storage unit groups, and storage lifecycle policies, so that you can plan and configure
NetBackup to operate most effectively.
• Storage devices are tapes and disk devices to which data can be written and stored.
When discussing storage devices, we are normally referring to the physical devices
as seen by the server.
• Storage units are logical entities that refer to a storage device of a specific type.
Properties of a storage unit define how data is written to media. Additionally,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
storage units are a way of defining both the media server(s) and storage destination
for a backup. Note that a storage unit can be tape drives, a path to a disk volume, or
a disk pool (which can be deduplicated disk or cloud storage). Storage units are used
as a backup destination, a location where a backup policy sends a backup.
• Storage unit groups and Storage lifecycle policies (SLPs) are two additional storage
destinations that will be described. Storage unit groups are discussed elsewhere in
this lesson, and SLPs are discussed in the Duplicating Backups lesson.
Within a backup policy, you define a storage destination, which is where NetBackup will
send the backup data. This can be a storage unit, a storage unit group, or a storage
lifecycle policy, depending on your needs . You cannot send a backup directly to a
storage device that is not configured as a storage unit.
The slide lists disk storage types in NetBackup (listed by the corresponding disk type
identification categories used in NetBackup). Disk storage types include:
• BasicDisk consists of a directory or folder in a file system that is locally- or network-
attached to the media server. This disk type does not require any additional licenses.
• AdvancedDisk consists of a disk pool, which is a collection of disk volumes, that is
managed by a NetBackup media server or NetBackup appliance. AdvancedDisk has
better management capabilities than BasicDisk.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• OpenStorage uses the Veritas OpenStorage API to control functions and integrate
backup functionality for intelligent third-party disk appliances that support this API.
• PureDisk consists of a specialized disk pool and services that perform deduplication
of backup storage, and reside on a NetBackup media server or NetBackup appliance.
BasicDisk is included with NetBackup and does not require additional licensing. The
other disk types require the NetBackup Data Protection Optimization Option.
This lesson only covers the configuration of BasicDisk. For other disk types, refer to the
appropriate lessons in this course or the appropriate NetBackup documentation, as
listed on the slide.
After completing this topic, you will be able to configure and manage a
basic disk storage unit.
After completing this topic, you will be able to configure and manage a basic disk
storage unit.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bpstuadd -label
9
To configure storage units, or to copy an existing storage unit configuration and use it as
a template for a new storage unit, perform the following steps:
1. In the object tree pane of the NetBackup Administration Console, expand
NetBackup Management > Storage.
Storage unit information is displayed in the details pane.
2. Add the storage unit using one of the following methods:
• Select Actions > New > New Storage Unit.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bpstuadd -label
10
When creating a Disk storage unit type, you must supply the following properties:
• Storage unit name: A unique name that is used in backup policies and schedules.
• Storage unit type: The type of storage that this storage unit uses, for example, Disk.
• On demand only: Specifies whether the storage unit is only available when a policy
attribute or policy schedule is explicitly configured to use this storage unit. The
storage unit will not be used when the Any Available storage destination is selected.
• Disk type: Specifies the type of disk storage unit to be created. By default: BasicDisk.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bpstulist
11
After initially configuring a basic disk storage unit, you can subsequently open the basic
disk storage unit to change existing parameters (such as the maximum concurrent jobs,
or water marks). You will notice that certain parameters cannot be modified, such as the
storage unit name, storage unit type, or disk type.
Clicking on the View Properties button shows details for the file system on which the
basic disk folder resides, such as capacity and available space.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12
After completing this topic, you will be able to configure storage unit
groups.
13
After completing this topic, you will be able to configure storage unit groups.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Storage device
• Physical tape and disk devices to which data is written to and restored from
Storage unit
14
It is important that you know the differences between storage devices, storage units,
storage unit groups, and storage lifecycle policies, so that you can plan and configure
NetBackup to operate most effectively.
• Storage devices are tapes and disk devices to which data can be written to, stored,
and restored from. When discussing storage devices, we are normally referring to
the physical devices as seen by the server.
• Storage units are logical entities that refer to a storage device of a specific type.
Properties of a storage unit define how data is written to media.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Storage unit groups are two or more storage units that have been grouped together.
This enables you to address multiple storage units as a single entity when creating a
policy. You may set the priority of the storage units within the group, and the type of
load balancing and failover behavior desired.
• Storage lifecycle policies (SLP) are additional backup destinations with
comprehensive storage plans that include supporting multiple destinations,
including snapshots, duplications, and replications. SLPs are discussed in the
Duplicating Backups lesson.
Within a backup policy, you define a storage destination, which is where NetBackup will
send the backup data. This can be a storage unit, a storage unit group, or a storage
lifecycle policy, depending on your needs . You cannot send a backup directly to a
storage device that is not configured as a storage unit.
✓ ✓ ✓ ✓ ✓
15
Prior to the concept of storage unit groups, NetBackup used functions known as On
demand only and Any available to be able to send backups to different storage units,
based on availability.
When configuring a backup policy, if you select Any_available as the storage destination
for your backup, backup data is directed to an available storage unit designated as Any
available. These are all storage units that are not marked as On demand only.
NetBackup tries locally attached storage units first, and if none are found, the storage
units are tried in alphabetical order. NetBackup uses the first storage unit that meets the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
following requirements:
• The storage unit must not be designated as on demand only.
• The storage unit must have available drives.
• The storage unit must have available storage (tape or disk resources) resources.
When you configure a storage unit as On demand only, the storage unit is only used if it
is specified directly within the backup policy, or backup policy schedule.
Since the introduction of storage unit groups in NetBackup, it is no longer
recommended to use Any available as the means of sending backups to different
storage units.
bpstuadd -group
16
A storage unit group allows you to configure multiple storage units which act as a single
destination for backup jobs.
To create a new storage unit group, navigate to NetBackup Management > Storage >
Storage Unit Group, and select Action > New Storage Unit Group. Similarly, you can
right-click in the console and select New Storage Unit Group or click on the new storage
unit group button.
The bpstuadd command can be used to create storage unit groups. See the NetBackup
Commands guide for syntax and details.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
17
To configure a storage unit group, provide a unique storage unit group name, and select
which storage units to add to that group. The order in which storage units are used
within a group depends on the storage unit selection option
In the Storage unit selection area, you choose how storage units are selected within the
group as follows:
• Prioritized: Choose the first storage unit in the list that is not busy, down, or out of
media.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Failover: Choose the first storage unit in the list that is not down or out of media.
• Round Robin: Choose the least recently selected storage unit in the list.
• Media Server Load Balancing: Choose the best available media server based on a
ranking system.
Note that the Media Server Load Balancing selection does not support basic disk
storage, and is discussed in more detail in the Configuring Disk Pools lesson.
Group priority:
1. ms1_tape_STU
2. ms2_tape_STU
3. ms3_tape_STU
ms1_tape_STU ms2_tape_STU ms3_tape_STU
Job 1 Job 3 Job 5
Job 2 Job 4 Job 6
Job 7
Job 8
18
The total number of concurrent jobs that can go to a specific storage unit will depend on
the storage unit’s configuration, specifically the maximum concurrent jobs that is
configured. The slide shows tape-based storage units (a library with two tape drives)
connected to each media server, however they could just as easily be disk-based storage
that accept two concurrent backups.
Prioritized storage unit groups choose the first storage unit in the list that is not busy
with other jobs, down (physically unavailable), or out of tape media (in the case of tape
libraries). It then fills that storage unit with active jobs, and then moves on to the next
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
available storage unit in the list. If all storage units are busy, any subsequent jobs will
queue, and wait for the next available storage unit in the group.
In the example on the slide, media server ms1 is shown with more memory and system
resources than media server ms2, which additionally has more resources than media
server ms3. Using a prioritized storage unit group means that ms1_tape_STU will always
be used first, until it is busy. Storage unit ms2_tape_STU will fill with jobs next, and
finally ms3_tape_STU.
Group priority:
1. ms1_tape_STU
2. ms2_tape_STU
3. ms3_tape_STU
ms1_tape_STU ms2_tape_STU ms3_tape_STU
Job 1 Job 2 Job 3
Job 4 Job 5 Job 6
Job 7
Job 8
19
Round robin storage unit groups choose the least recently used storage unit in the list
that is available.
In the example on the slide, all three media servers are shown with identical memory
and system resources, and using a round robin storage unit group means that initially
the jobs will be distributed evenly amongst the storage units. Once all storage units are
in use, additional jobs will queue and wait for any available storage unit in the group.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Group priority:
1. ms1_bdisk_STU
2. ms2_tape_STU
Only used if primary
ms1_bdisk_STU* ms2_tape_STU storage unit is down or
Job 1 out of media
Job 2
Job 3
Job 4
A failover storage unit group chooses the first storage unit in the list that is not down or
out of media. All other jobs will queue waiting for this storage unit, even if it is busy. If
the storage unit ever goes down (or runs out of media), then the jobs will fail over to
the next available storage unit in the group.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Spanning STU-C
not
supported
STU-D
STU group 2
21
A backup may span storage units if a disk full condition is detected. Backups can span
from one BasicDisk storage unit to another BasicDisk storage unit if the storage units are
in the same storage unit group. The storage units must also share the same media
server.
The following destinations support disk spanning:
• A BasicDisk storage unit spanning to a BasicDisk storage unit. These storage units
must be within a storage unit group.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
22
Basic disk spanning is enabled in the media server’s Host Properties under Media, using
the Allow backups to span disk property.
The default is that this property is enabled. The Allow backups to span disk property
does not apply to AdvancedDisk or OpenStorage storage units, since backups span disk
volumes within disk pools automatically. These storage units are discussed in more
detail in the Configuring Disk Pools lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Storage unit groups Storage > Storage Unit bpstulist –go –U Manage > Storage >
Groups Storage Unit Group
23
The table on this slide summarizes the storage unit reporting tools using the NetBackup
Administration Console, NetBackup commands, and OpsCenter.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Key points
– In this lesson, you learned about disk-based storage and how it is used.
– You also learned how to configure basic disk storage units, monitor the status of, and view reports for,
basic disk storage.
– Finally, you learned how to configure storage unit groups.
• Reference materials
– NetBackup System Administrator’s Guide
– NetBackup Commands Reference Guide
– http://www.veritas.com/support
24
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
26
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Catalog
B. Policy
C. Storage unit
D. Selection list
27
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Catalog
B. Policy
C. Storage unit
D. Selection list
The correct answer is C. The logical destinations for a NetBackup client’s data include storage units, storage unit groups,
and storage lifecycle policies.
28
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Failover
B. Priority
C. First-in First-out
D. Round Robin
29
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Failover
B. Priority
C. First-in First-out
D. Round Robin
The correct answer is C. The four storage unit group selections include Failover, Priority, Round Robin, and Media Server
Load Balancing.
30
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
31
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The correct answer is B. Configure Allow backups to span disks in the media server host properties. Ensure that all the
basic disk storage units is configured on the same media server.
32
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2-33
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Configuring Policies and Schedules” lesson in the “Veritas NetBackup 8.1:
Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
Define which client files and directories to backup up, and create
Creating backup selections
exclude and include lists.
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to explain how data protection
relates to a policy.
After completing this topic, you will be able to explain how data protection relates to a
policy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Policy configuration is flexible enough to meet the various needs of all the clients in a
NetBackup environment. To take advantage of this flexibility, take time to plan before
starting to configure the policies within NetBackup.
Include the following tasks in your planning and preparation:
• Gather client information.
• Group the clients based on backup requirements.
• Consider the storage requirements.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Schedules When do backups occur? Include all data or only changes? How long is backup data retained?
Backup
Which data is backed up?
Selections
Application-
How are database backups handled? How are virtual machine backups handled?
specific tabs
Policies define the rules that NetBackup follows when data from clients are backed up.
A backup policy can apply to one or more clients. The best approach is to divide clients
into groups according to the backup requirements, and creating a policy for each group.
In a policy you define attributes, schedules, a client list, and a backup selections list.
• Attributes answer questions, such as: How should the files be backed up? Are there
any special backup behaviors? Where is the backup storage location?
• Schedules answer: What is the backup time and type? On which schedule should
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to identify basic policy types,
and configure policy attributes.
After completing this topic, you will be able to identify basic policy types, and configure
policy attributes.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Command Line
• Provided with bppolicynew command.
• Can be used in script-based policy setup.
bppolicynew
10
Attributes determine the basic characteristics of all the backups that NetBackup
performs for the policy. You can view and configure a policy’s attributes using the
NetBackup Administration Console.
The Attributes tab answers the questions “How is the policy going to perform the
backup?” and “Where are the storage units and volume pools to which the backup data
is to be sent?”
The Policy type determines the type of clients that can be part of the policy and, in
some cases, the types of backups that can be performed on the clients. Select the Policy
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11
The number of policy types available varies depending on which NetBackup options are
installed. Each policy type offers a unique combination of attributes.
The two policy types shown on this slide are basic NetBackup policy types. Each of these
policy types is distinguished by the types of clients that can be part of the policy, and
what is backed up when a backup job is run.
• Standard policy type
Used for clients and file systems that are UNIX-based, this includes UNIX, Linux, and
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Used for clients and file systems that are Windows-based, supported Windows
operating system levels.
Supported OS levels can be found on the support website at the following link:
http://www.veritas.com/docs/000115691.
12
The Policy storage drop-down menu specifies the default storage unit or storage unit
group for backups of this policy. This is the storage unit that is used by default by all
schedules in this policy. However, schedules may be configured to override the policy
storage destination.
The Policy volume pool drop-down menu specifies the volume pool for backups of this
policy. Select the desired volume pool name from the drop-down list. The list displays all
previously configured volume pools. Whenever a new volume is required for either a
robotic or stand-alone drive, it is allocated to NetBackup from the requested volume
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
pool.
Policy storage and volume pools are covered in more detail in a later lesson.
After completing this topic, you will be able to describe backup schedules
types, and create and configure both frequency-based and calendar-based
schedules.
13
After completing this topic, you will be able to describe backup schedules types, and
create and configure both frequency-based and calendar-based schedules.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14
The Schedule tab answers, among other things, the question “When is this policy to be
run?”
Use the following procedures to create a new schedule using the Administration
Console:
1. In the left pane of the NetBackup Administration Console, select Master Server >
NetBackup Management > Policies.
2. Double-click a policy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15
of a scheduled task and the next attempt. In addition to hours, days, and weeks,
NetBackup 8.0 introduced the ability to set frequency in minutes and seconds.
• Destination pane
Multiple copies: Used to create inline copies. This is discussed in the Duplicating
Backups lesson.
Override policy storage selection and Override policy volume pool: Override the
storage unit or volume pool for this schedule, so that it differs from the one
specified in the policy’s Attribute tab.
Retention: The time that the image is to be held in the images catalog. By default,
NetBackup does not mix retention levels on a single volume.
For more information about other options on the Schedule dialog box Attributes tab,
see the NetBackup Administrator’s Guide.
Full
16
list for the policy that have changed since the last successful incremental or full
backup. All files are backed up if no prior backup has been performed. A complete
restore requires the last full and all of the differential incremental backups since the
last full or the last full, the last cumulative incremental and all of the differential
incremental backups since the last cumulative incremental.
• Cumulative incremental backup
Cumulative incremental backups back up all files specified in the backup selections
list for a policy that have changed since the last successful full backup. All files are
backed up if no prior backup has been performed. A complete restore requires the
last full backup and the last cumulative incremental. Cumulative incremental
backups generate more files per backup, but complete restoration is quicker.
17
The Start Window tab provides controls for setting time windows during which
NetBackup can start automatic backups, archives, or disk staging relocation when using
this schedule. Configure the start windows so that they satisfy the requirements
necessary to start a task or job. If the start windows closes before the backup has
started it does not run. Once a backup has started, it runs to completion even if the
start window closes. The start window is not used for manual backups.
For example, for backups, you can create a different window that opens each day for a
specific amount of time, or you can keep the window open all week.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
For more information about the options on the Schedule dialog box Start Window tab,
see the NetBackup Administrator’s Guide.
Client 1 21:01
Start Window: when
backups may start
21:00 - 01:00 Client 2 22:39
Client 3 23:40
Client 4 00:52
18
The example on this slide demonstrates the effect of start window duration on a backup
schedule.
In the example, backups for Client 1 through Client 4 are started within the backup start
window. Client 4 does not finish before the window closes, but because it starts within
the window, the backup is completed. Client 5 did not start within the window, so its
backup does not run. Client 5 is automatically the first client backup that is attempted in
the next run of this schedule.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
19
You can exclude specific dates, such as January 1, from your backup schedule.
Under the Exclude Dates tab, define the dates you want to exclude from the schedule.
Dates can be excluded by using Recurring Week Days, Recurring Days of the Month or
Specific Dates.
Exclude dates applies to both frequency-based and calendar-based schedules.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
20
21
Calendar-based scheduling provides several run day options for use in scheduling when
a task runs.
A backup can run on Specific Dates rather than follow a recurring schedule, and specific
dates can be added to a recurring schedule. You can schedule specific dates in any
month of any year up to and including December 31, 2037.
Define specific calendar days as run days by clicking in the date on the calendar. This
specification causes the backup to run on the specified day during the valid window that
is defined for that day.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Recurring Week Days option provides a matrix that enables you to schedule a task for
certain days of each week, weeks of each month, or days on particular weeks of the
month. For example, use this option to schedule a task on the first and third Thursday of
every month. Or, schedule a task that runs the last week in every month.
The week day matrix is not a calendar; it is simply a matrix used to select days and
weeks in a month. A check mark entered for a day indicates that the task is scheduled to
run on that day of its respective week. By default, no days are selected. For example, to
define specific run days based on recurring days of the week, such as every Friday, click
Fri on the matrix, and every Friday is automatically selected.
The Recurring Days of the Month option provides a matrix that you can use to schedule
a task for certain days of the month. You can also schedule a task to occur on the last
day of the month, regardless of the actual date.
bpretlevel
22
The retention period in a policy’s schedule determines how long NetBackup retains the
backups images created by that schedule. NetBackup 8.0 and later supports 100
separately defined retention levels. The Retention Periods properties, found in the
master server host properties, define the length of time associated with each level. All
of these retention levels are configurable, with the exception of level 9 and level 25,
which have fixed retention period values. Veritas recommends leaving retention levels
0-8 at the default values. Change higher levels which are currently set to infinite, if you
want to customize.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to specify which clients are to
be used in a policy.
23
After completing this topic, you will be able to specify which clients are to be used in a
policy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
silentclient.cmd
Before adding a client to a policy, ensure that the NetBackup software is successfully
installed on that client. There are five ways to distribute NetBackup client software:
1. Local installation: In a local installation the NetBackup client software can be
installed on the machine by providing a copy of the NetBackup client software.
2. Silent installation: A silent installation is a process that does not require interactive
input. You must first modify the silentclient.cmd script.
3. Installation from a file share: To install NetBackup client software from a file share
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
simply put a copy of the NetBackup client software on a file server and any client on
the network can install the software to itself.
4. UNIX server to UNIX client: A NetBackup UNIX master or media server can push
UNIX client software, using standard protocols such as ssh, and sftp. These
protocols are available in a combination of the NetBackup Administration Console,
and in the install_client_files script.
5. Windows server to Windows client: Any Windows server that has a copy of the
NetBackup software, can push the NetBackup client software to other Windows
clients out on the network.
25
The Clients tab contains the list of clients that are backed up or affected by this policy.
This answers the question, “Which system is to be backed up?”
To add clients to a policy using the NetBackup Administration Console, click the Clients
tab and click New. You are prompted to provide the name of the client, as well as the
hardware and operating system type. You can either select the Detect client operating
system check box or select the appropriate hardware and operating system for the
client in the drop-down menu.
Note: To be able to use the auto-detect feature, the NetBackup client software must
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
already be installed on the client, and the master server needs to be allowed to connect
to the client by having an appropriate SERVER entry in the client’s server list. This is
accomplished when you enter the master server name during the installation of the
client software on the host.
For detailed instructions on adding a client to a policy, see the NetBackup
Administrator’s Guide.
After completing this topic, you will be able to define which client files and
directories to backup up, and create exclude and include lists.
26
After completing this topic, you will be able to define which client files and directories
to backup up, and create exclude and include lists.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• All clients in the policy, but all files do not have to exist for every client
27
Under the Backup Selections tab, you name the files and directories that NetBackup
includes in automatic scheduled backups for clients in this policy. The backup selections
list does not apply to user backups or archives because in those instances the user
selects the files.
NetBackup uses the same backup selections list for all clients in the policy, but it is not
required that all files exist on all clients. NetBackup backs up the files that it finds.
However, each client must have at least one of the files in the backup selections list, or
the client backup fails with a status code 71. Backup selections are processed serially for
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
each client. It is possible, however, to back up more than one client (or policy) in
parallel.
Related items are listed on the exclude and include lists. You can create an exclude list
on a client to specify files that you do not want to include in automatic and manual
backups of that client. You can also create an include list for a client to back up a file or
directory that would otherwise be excluded by an exclude list. Many administrators
have a standard exclude list that is copied to all clients, and then use include lists to
customize clients that have exceptions to the standard exclude list.
Windows UNIX
Creating a backup
Administration Console or bpplinclude
selections list
• Use one path per line
Entries • Maximum path length of 1,023 characters
• All paths must be absolute
Path restrictions Start all paths with a drive letter Start all paths with a slash (/)
Wildcards supported *, ? *, ?, { }, [ ]
28
When defining files for your policy, the backup selection list can be set using either the
NetBackup Administration Console or the bpplinclude command.
It is important that you follow the conventions and rules used to specify backup
selection lists:
• Enter one path per line, with a maximum path length of 1,023 characters.
• All paths must be absolute. Local paths on Windows must start with the drive letter
followed by a colon and a backslash (:\). The drive letter can be either upper- or
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bpplinclude
29
The backup selections list under the Backup Selections tab names the files, directories,
directives, scripts, and templates that NetBackup includes in automatic backups of
clients covered by the policy. NetBackup uses the same backup selections list for all
clients backed up according to the policy.
This answers the question “What is to be backed up?”
To build a backup selections list when creating a policy using the NetBackup
Administration Console, click the Backup Selections tab and click New. You are then
prompted to provide a new path or directive.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
For example, you can use C:\ or /home for a path and ALL_LOCAL_DRIVES for a
directive.
For detailed information on adding an entry to the Backup Selections list, see the
NetBackup Administrator’s Guide.
30
as the registry, Active Directory, and other information not fully protected when backing
up the file system alone. The System State:\ directive can still be found, and is used for
versions which do not support Shadow Copy Components, such as Windows XP.
The NEW_STREAM directive is available when the Allow multiple data streams
attribute is enabled for the policy. This directive is discussed in greater detail in the
Optimizing File System Backups lesson. Refer to that lesson for further details.
Some directives apply only to specific policy types and appear only in backup selections
lists for those policies. NetBackup passes these directives to the clients along with the
backup selections list, which then perform appropriate action according to the directive.
The UNSET and UNSET_ALL directives interrupt the streaming of policy-specific
directives so that it is not passed with any additional streams.
Public network
NetBackup NetBackup
media server Windows client
NFS
mount
/ /usr /nfs_home /home
31
The next few slides show further settings that can be configured to control backup
selections. These settings can be found under the Policy Attributes tab.
The Follow NFS attribute applies only to UNIX clients in certain policy types, and
NetBackup enables you to select it in only those instances.
The Follow NFS attribute specifies that you want NetBackup to back up or archive any
NFS mounted files that are named in the backup selection list, or by the user in the case
of a user backup or archive. Clear the check box to prevent the backup or archive of NFS
mounted files.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
This attribute forces the client to back up NFS-mounted drives within the path. It is
important to understand the advantages and disadvantages of the Follow NFS attribute
setting.
Public network
NetBackup NetBackup
media server UNIX client
CIFS
share
C:\ D:\ E:\ F:\
32
The Backup Network Drives attribute applies only to certain policy types.
The Backup Network Drives attribute was intended to be used on single-user systems—
Win95, Win98, and ME. These operating systems are not supported with this version of
NetBackup. For a computer that is not a NetBackup client, the preferred method for
backing up data is to use UNC paths. UNC paths are more precise and indicate exactly
what should be backed up.
For detailed information on using UNC paths in the Backup Selections list, see the
NetBackup Administrator’s Guide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
NetBackup NetBackup
UNIX client Windows client
/ C:\ D:\
/home C:\data
33
Another policy attribute is Cross mount points. When enabled, this attribute forces the
client to back up locally mounted drives within the path. The Cross mount points check
box controls whether NetBackup crosses file system boundaries during a backup or
archive on UNIX clients or whether NetBackup enters volume mount points during a
backup or archive on Windows clients.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Exclude list
Include list
34
On UNIX NetBackup clients, you can exclude specific files from automatic backups by
specifying them in an exclude list on the client.
You can also create an include list to add certain files to the backup. An include list is
useful, for example, if you want to exclude an entire directory except for one file.
It is recommended that policy names do not include a “.” (period) character, because of
the exclude and include list file naming structure.
Note: You can create policy- and schedule-specific lists. NetBackup ignores the general
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Exclude list
Include list
35
Exclude lists for NetBackup clients can be used to prevent files that are found within the
backup selection from being backed up. The Exclude Lists properties apply to currently
selected clients running NetBackup. Note: You can create policy- and schedule-specific
lists. NetBackup ignores the general list if a specific list is present.
The properties in the Exclude Lists pane include:
• Use case sensitive exclude list: Indicates that the files and directories listed for
exclusion or exception are case-sensitive.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Exclude list: Displays files and directories to exclude from backups. By default there
are no exclusions except for a short list of NetBackup-related exclusions.
• Exceptions to the exclude list: This list displays policies, schedules, files and
directories that are excepted from the Exclude list. When the policies on the
Exceptions to the exclude list run, the files and directories on the list are backed up.
This is useful if you want to exclude all files in a directory but one. This is equivalent
to the include list found on UNIX.
• The Add, Add to All, Change, Remove, Copy and Paste buttons each perform
different functions, depending on whether they are used from the Exclude list or
from the Exceptions to the exclude list. Note: The Add to Exclude List dialog box, as
shown on the slide, appears to have drop-down selections for policy and schedule
name, however these are actually text-entry fields.
36
In the Backup, Archive, and Restore interface, which is found on every NetBackup client,
select File > NetBackup Client Properties from the menu bar. Click on the Exclusions tab
to modify files to exclude from backup, and click on the Inclusions tab for files to
include within the excluded files.
Note that modifying the exclude and include lists in the Backup, Archive, and Restore
interface modifies the exact same lists as those in the client host properties, shown on
the previous slide. On Windows, these settings are stored in the Windows registry.
For detailed instructions on creating an include or exclude list, see the NetBackup
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Administrator’s Guide.
After completing this topic, you will be able to view, edit, and copy existing
policies.
37
After completing this topic, you will be able to view, edit and copy an existing policy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
38
The easiest way to view and edit policies is by using the Policies utility in the NetBackup
Administration console. To run the Policy utility:
1. In the NetBackup Administration Console, in the object tree pane, expand
NetBackup Management > Policies
2. Within the Policy utility, you can perform the following tasks:
• To see a hierarchical view of the policies, select Policies in the object tree pane.
• To display the details of a single policy, select the policy name in the All Policies
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bppolicynew
39
You can copy an entire policy from an existing policy to a new one. Use the Copy
to New option to save time creating policies. This option is especially useful for the
policies that contain many of the same policy attributes, schedules, clients, or backup
selections.
To copy a policy to create a new one:
1. In the NetBackup Administration Console, in the left pane, expand NetBackup
Management > Policies.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
40
You can also use the Copy to New option to save time creating schedules. Use this
option to copy a schedule into the same policy or different policy.
To copy a schedule to create a new one:
1. In the NetBackup Administration Console, in the left pane, expand NetBackup
Management > Policies.
2. In the middle pane, expand a policy and select the Schedules node that contains the
schedule that you want to copy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3. In the right pane, select the schedule that you want to copy.
4. Right click and select Copy to New.
5. In the Copy Schedule dialog box, enter the name of the new schedule.
6. Use the menu to select the name of the policy to which you want to paste the
schedule. You can paste the schedule into the same policy or a different policy.
7. Click OK. The Change Schedule dialog box opens for the new schedule.
• Key points
– You now learned how to create a basic policy that is used to back up files in a file system.
– You learned about the types of schedules that are available in a policy.
– You learned how to define the clients that are backed up by the policy and the files and directories to be
backed up.
– You also learned how to manage policies using the NetBackup Administration Console.
• Reference materials
– NetBackup Administrator’s Guide
– NetBackup Commands Reference Guide
– Article 100019744: A method for centrally managing exclude and include list for UNIX and Linux clients
– http://www.veritas.com/support
41
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
43
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. 1,000
B. 500
C. Unlimited
D. None of the above
44
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. 1,000
B. 500
C. Unlimited
D. None of the above
The correct answer is C. NetBackup does not limit the number of policies that you can configure. However, the best
approach to setting up policies is to divide clients into groups according to their backup and archiving requirements, and
then create policies that are appropriate for each group.
45
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Differential incremental
B. Cumulative incremental
C. Accumulation incremental
D. Differences incremental
46
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Differential incremental
B. Cumulative incremental
C. Accumulation incremental
D. Differences incremental
47
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. True
B. False
48
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. True
B. False
49
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-50
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Performing File System Backups” lesson in the “Veritas NetBackup 8.1:
Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
Using and customizing the Use and customize the Activity Monitor, and suspend, resume,
NetBackup Activity Monitor restart, and prioritize jobs.
Performing manual backup Initiate a manual backup job, and monitor backup jobs using the
operations Activity Monitor.
Configure and perform user-directed backups using the Backup,
Performing user-directed backups
Archive, and Restore console.
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to use and customize the
Activity Monitor, and suspend, resume, restart, and prioritize jobs.
After completing this topic, you will be able to customize the Activity Monitor, and
suspend, resume, restart, and prioritize jobs.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Icon Legend
Successful
Partially
successful
Active
Queued
Failed
Incomplete
Suspended
The Jobs tab within the Activity Monitor provides a listing of jobs that are queued, are
currently running, have completed successfully (status code 0), have completed partially
successfully (status code 1), or have failed.
The Activity Monitor periodically deletes completed jobs that are more than three days
old (specifically any completed jobs older than 78 hours). To keep jobs in the Activity
Monitor longer than the default value, for example by changing the timeframe from 78
hours to 192 hours, use one of the following methods:
• On a Windows or UNIX master server, run the command:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
You can use the Activity Monitor in the NetBackup Administration Console to monitor
and control NetBackup jobs.
To display job information, in the NetBackup Administration Console, click Activity
Monitor. Summary information about all jobs is displayed under the Jobs tab in the
details pane.
By default, not all columns are displayed. The following procedure describes how to
show or hide columns:
1. In the Activity Monitor, select View > Column > Layout.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Show / hide
custom filters
Filtering jobs in the Activity Monitor simplifies troubleshooting and reporting. For
example, you can filter for jobs that were started before a specific date, queued jobs, or
jobs with status completion codes within a specified range.
The Filter dialog can be viewed in by accessing the View > Filter menu option, or by
clicking on the Show or Hide Custom Filter button in the top-right corner of the Activity
Monitor. Clicking on the View All button clears currently applied filters and displays all
original rows again.
To create a filter:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1. In the Activity Monitor, show the custom filter pane as shown on the slide.
2. Click Create, and in the Create Filter dialog box provide a name for the filter.
3. Under the Advanced tab, select the Field, Comparison, and Value desired.
4. Click Add to List to add your selections to the filtering criteria.
5. Click Save to create the filter. The filter is immediately applied.
You can edit an existing filter operation with the Edit button. Once the filter is modified,
save the filter by either choosing Save or Save And Apply Filter. There is also
functionality to export and import filters as a binary file, to share frequently used filters
with other hosts and users.
A NetBackup administrator can cancel a job at any time from both the Activity Monitor
and from the command line. A NetBackup administrator can suspend a job that has
checkpoint restart enabled. In the example on the slide, Suspend Job is greyed out, this
means the job cannot be suspended as there are no checkpoints enabled in the policy
configuration.
Jobs cancelled “cleanly” as described here, exit with NetBackup status code 150
(termination requested by administrator).
If you cancel a scheduled backup job, but the number of retries is not yet exceeded and
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Job priorities provide a method to help determine which jobs get available resources.
This can be used to help administrators prioritize certain high priority clients and data
against other clients with a lower priority.
Job priorities can be set as a default value for different job types in the policy, before the
job runs, or on jobs that have already been added to the Activity Monitor in NetBackup.
The NetBackup Resource Broker (nbrb) uses the job priorities to determine which job is
assigned available backup resources, in addition to other factors, such as multiplexing
requirements. The NetBackup resource broker re-evaluates resource requests every five
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10
This slide shows how to set job priorities on a policy and on running jobs.
Note that although you can change the job priority of a running job, because it has
already started, this priority has no effect. However, if the job fails, and then gets re-
queued for another attempt, it is re-queued with this new priority.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
ckpt1 ckpt3 ckpt5 ckpt7 ckpt9 ckpt11 ckpt13 ckpt15 ckpt17 ckpt19 ckpt21 1
Backup fails
ckpt2 ckpt4 ckpt6 ckpt8 ckpt10 ckpt12 ckpt14 ckpt16 ckpt18 ckpt20 ckpt22
The job is marked
as incomplete
HOURS
HOURS
SS
TT EE 3
AA 11 22 33 44 55 66
NN Job is
RR DD
TT done
2 Job resumes
Job starts from the point in the file system ckpt22 ckpt24 ckpt26 ckpt28
indicated in the last checkpoint: “ckpt22”
ckpt23 ckpt25 ckpt27
11
The Take checkpoints every check box indicates whether NetBackup takes checkpoints
during backup jobs based on this policy at the frequency indicated.
Taking checkpoints during a backup is beneficial in the event that a backup based on this
policy fails. Without Take checkpoints every enabled, a failed backup based on this
policy is restarted from the beginning of the job. By taking checkpoints periodically
during the backup, NetBackup can retry a failed backup from the last checkpoint rather
than restarting the entire job.
The number of times that NetBackup automatically reattempts a failed backup is
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
configured by the Schedule Backup Attempts property located in the Master Server
Properties > Global Attributes dialog box.
Policy types MS-Windows (for Windows clients) and Standard (for UNIX clients) support
checkpoints for backup jobs. Job types that do not support checkpoint restart include
catalog backups, duplication jobs, Vault jobs, import jobs, synthetic backup jobs, and
most database agents.
How often NetBackup takes a checkpoint during a backup is configurable. The
administrator determines on a policy-by-policy basis how to balance more frequent
checkpoints with the likelihood of less time lost in resuming a backup because of more
checkpoints. The default is checkpoints every 15 minutes. The minimum supported
value is every 5 minutes, and maximum is every 180 minutes (every 3 hours).
12
Note that if incomplete jobs are not resolved after 3 hours, by default, then their state
changes from Incomplete to Done. This settings can be changed in the master server
host properties under the Clean-up tab. A screenshot of that setting is shown on the
slide.
Windows system
• No checkpoints are taken.
state backup
Disk-image (raw)
• No checkpoints are taken.
backup
NTFS resumed • Archive bits cleared for files backed up after the resume.
incremental backup • Archive bits not cleared for files backed up prior to the resume.
13
minimum of disk, cache, and backup media overhead. For more information on NTFS
single-instance store, see the Knowledge Base on the Microsoft Web site at
https://technet.microsoft.com/en-us/library/dd573308%28v=ws.10%29.aspx.
On a Windows client's NTFS file system, when a differential incremental backup is
resumed and then completes successfully, the archive bits are cleared for the files
backed up since the resume, but not for the files backed up prior to the resume.
This means that the files backed up prior to the resume are backed up again on the next
differential incremental backup.
After completing this topic, you will be able to initiate a manual backup job,
and monitor backup jobs using the Activity Monitor.
14
After completing this topic, you will be able to initiate a manual backup job, and
monitor backup jobs using the Activity Monitor.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Manual (immediate)
• Initiated from the NetBackup Administration Console
• Initiated from OpsCenter
• Initiated from command line on a NetBackup server
User-directed
• Initiated by users or scripts on the client
• Performed on authorized NetBackup clients only
15
• Testing a configuration
• Resubmitting a missed or failed backup
• Preserving an old configuration prior to upgrading
16
A manual backup is not dependent on the policy’s backup window or the time specified
by the schedule. That is why it is also called immediate. In fact, you can create a policy
schedule without an open window and run only manual backups defined by that policy,
as needed.
Since you can invoke a manual backup outside a policy’s normal backup window, a
successful manual backup job can affect a frequency-based schedule because it qualifies
as a successful backup. Consider that frequency-based schedules are based on the
amount of time (frequency) since the last successful backup job. This may therefore
mean that an automatic backup does not run when you next intended it to.
bpbackup -i
17
If you do not select any schedules, NetBackup uses the schedule that runs least
often. For Automatic schedules, the Frequency is generally used. If there are
multiple equivalent candidates, then schedule with the highest retention level is
chosen. It is therefore recommended to explicitly specify the schedule that you wish
to use.
If you do not select any clients, NetBackup backs up all clients.
If a User schedule exists, they are not displayed in the schedules list and cannot be
manually backed up because they do not have a backup selection list (the user
selects the files). These types of backups are run from the client system, either by an
application or script, or an administrator (user).
4. Click OK to start the backup.
18
You can expect backup success to be the norm in a properly configured and well-
maintained NetBackup environment. NetBackup is a very robust application in terms of
detecting and reporting errors, therefore, when problems do occur, you should be able
to track them down and correct them quite reliably.
A status code 0 (and the accompanying success icon: ) in the Activity Monitor
indicates that a backup job has completed successfully. Any other status code or icon
indicates that a backup was only partially successful or has failed. There are other
methods by which you can determine if a problem has occurred with a backup job,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
19
To view the details for a specific job, double-click the job under the Jobs tab. The Job
Details dialog box is displayed. Detailed job information is contained under three tabs:
• Job Overview provides a high level view of the job.
• Detailed Status lists the step by step actions performed during the job.
Under the Detailed Status tab, a Troubleshooter button is available to launch the
Troubleshooter, which can help determine the cause of the problem and
recommend corrective actions.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Job Hierarchy shows the job hierarchy, discussed in more detail on the following
slide.
20
Hierarchical jobs, when one job is a parent of one or more child jobs, is a behavior seen
frequently with Storage Lifecycle Policies, snapshot jobs, catalog backup jobs, and many
other job types.
The Activity Monitor in the NetBackup Administration Console can optionally show a
hierarchical job view. There is a button on the toolbar which enables this functionality,
or you can select View > Jobs in Hierarchical Manner from the menu bar to toggle this
view.
You can get this information by moving the Parent Job ID column, which by default is
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
placed to the far right, close to the Job ID column. In that manner you could see the job
associations. However, the hierarchical job view makes this easier to visualize.
The job hierarchy can also be seen in the Job Hierarchy tab of the job details.
21
In some cases backup jobs may initially fail, but then, when retried by NetBackup, they
succeed in a future attempt. You are able to see the details for each job attempt in the
Detailed Status tab of the job details. Simply use the up and down arrows to the right of
the Attempt field.
The slide displays one of these cases, where the first attempt to run a backup job
resulted in a status code 157: suspend requested by Administrator. The second attempt
at running the job succeeded and exited with a status code 0.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to configure and perform user-
directed backups using the Backup, Archive, and Restore console.
22
After completing this topic, you will be able to configure and perform user-directed
backups using the Backup, Archive, and Restore console.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
23
The policy must have a user backup schedule that defines the start window during
which users can initiate a backup. The client must be in the policy’s client list. Users
select files and directories to back up. NetBackup ignores the policy’s backup selections
list.
Clients can obtain status information using progress logs, e-mail notifications, and the
activity monitor.
User-directed backups and archives can be initiated by:
• An interactive user, such as a file owner, system administrator, or DBA by using the
BAR console, or NetBackup commands
• A backup script launched at regular intervals
• An event trigger that kicks off a backup script
24
User-directed backups require a backup policy that contains a User Backup schedule,
and the client names added into the Clients tab of that policy.
Consider the following:
• When you establish a user backup schedule, you provide users with a start window
during which they can perform their own backups or archives. Users can start
backups and archives only during the times permitted under the schedule’s Start
Window tab. When you set the start window, consider the times that users typically
are at work and likely to need to initiate user-directed backups. If a user starts a
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
25
Users can initiate backups and archives using the Backup, Archive, and Restore interface
on the client machine. These operations can be performed without administrator
intervention, and the user does not need to log on to any of the NetBackup servers.
When performing user-directed operations using the NetBackup BAR console, only files
for which the logged-in user has rights are shown.
Perform the following steps to start a user backup operation:
1. From the BAR console, click Select for Backup.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2. Select the desired files and folders for backup by selecting the check box to the left
of the file or folder. To mark all files and folders that currently appear, select Edit >
Mark Displayed Files.
3. Start the backup operation by clicking the Backup button.
The Backup Options window is displayed. The NetBackup server drop-down allows
you to select the master server you wish to use for this backup, if more than one
master server exists for this client.
If a specific policy or schedule should be used, use the Action> Specify Policy and
Schedule dialog prior to clicking on the Backup button.
4. Confirm the backup selection and click Start Backup.
BAR
console
Activity
Monitor
26
The View Status dialog box enables you to view the progress of a NetBackup operation.
The status is displayed in the top pane. Select the job that you want to monitor. The
lower pane reflects the progress of the item selected in the upper pane.
The NetBackup operation is finished when the status changes to Successful. If
NetBackup is unable to back up all of the requested files, a status code is displayed a
few lines before the end of the progress report. The NetBackup Status Codes Reference
Guide lists the meaning of the final status code.
You can also monitor user-directed jobs using the Activity Monitor in the NetBackup
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to identify common backup job-
related status codes.
27
After completing this topic, you will be able to identify common backup job-related
status codes.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Misdefined schedules
Schedule issues • Status code 196 (The client backup was not attempted because the
start window closed.)
28
The slide describes some common backup policy issues and troubleshooting.
For additional troubleshooting assistance, refer to the NetBackup Troubleshooting
Guide, to the NetBackup Status Code Reference Guide, or attend the Veritas NetBackup
Maintenance and Troubleshooting course.
• Schedule issues
Problems with schedules typically involve incorrect definitions of policy elements.
Misdefined schedules, clients, or backup selections can lead to a backup failure.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The most common status code associated with policy schedule errors is:
Status code 196: The client backup was not attempted
because the backup window closed.
Due diligence is required on your part to verify that such oversights are corrected.
Evaluate and adjust the policy attributes, as necessary. Extend the backup window to
avoid errors resulting from the backup window being closed.
• Client issues
The slide highlights some common client issues. Some of these are configuration
issues, and a common problem is trying to back up a client which has not had the
NetBackup client software installed, in which case NetBackup cannot communicate
with any NetBackup processes on that client.
30
The slide highlights some common NetBackup job status codes that indicate that there
was an issue encountered when running a backup job.
NetBackup status code: 1 indicates that the backup was partially successful. With this
status code, you know that at least one file was backed up, but beyond that a problem
occurred.
NetBackup status code: 71 indicates that none of the files in the policy’s backup
selections list exist. Verify the policy file list to ensure that the file names are correct. If
a single client is the source of the error, consider moving it to a different policy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
NetBackup status code: 196 indicates that the backup job was queued, but the start
window closed before the backup could run. A 196 error is usually indicative of a
resource issue, such as there is not enough time for all backups to complete, the
network can be slow, or there may not be enough tape drives to handle the data load.
NetBackup status code: 2111 indicates that the job has requested any available storage
unit, but all storage units are configured with On Demand Only. This can occur in
environments with only disk storage units, where no specific storage unit, storage unit
group, or storage lifecycle policy was specified as a backup storage destination.
For a detailed explanation of these and other status codes, see the NetBackup Status
Codes Reference Guide.
31
The table on this slide summarizes how backup jobs can be managed using the
NetBackup Administration Console (GUI), NetBackup commands (CLI), and NetBackup
OpsCenter.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
32
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
34
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Immediate
B. Automatic scheduled
C. Manual
D. User-directed
35
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Immediate
B. Automatic scheduled
C. Manual
D. User-directed
36
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. True
B. False
37
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. True
B. False
38
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
39
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
40
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4-41
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Performing File System Restores” lesson in the “Veritas NetBackup 8.1:
Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
Describe the restore process and the restore methods used within
Introduction to Restores
NetBackup.
Performing Restore Operations Restore files and monitor restore operations using the Backup,
Using the BAR Interface Archive, and Restore (BAR) interface.
Performing Restore Operations
Restore files and monitor restore operations using OpsCenter
Using OpsCenter Operational
Operational Restore.
Restore
Monitor restore operations, and identify common restore-related
Restore Job-Related Tips
status codes.
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to describe the restore process
and the restore methods used within NetBackup.
After completing this topic, you will be able to describe the restore process and the
restore methods used within NetBackup.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Synchronous Clustering
Traditional replication
Snapshot Standard
backups Asynchronous technologies restore
Snapshot replication
technologies Bare Metal
Restore
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
NetBackup
logs and NetBackup
reports 4
master
server and
2 catalog
NetBackup
media
server
3
NetBackup Storage
Client Backup
client destination
data image
No backup is worth anything unless the data it contains is available to be restored when
needed. Restores can be performed from the master server by an administrator to
restore the data to the destination client machine. Restores can also be performed at
the request of a user.
The restore flow is described in this diagram.
1. To restore data, use OpsCenter or the NetBackup Backup, Archive, and Restore
interface. The NetBackup master server catalog contains information on what files
and folders have been backed up, and provides the information that the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Server-directed restores
Client-directed restores
• Only the client that backs up files to restore those files, by default
• Disable all restrictions with the No.Restrictions setting
• Allow specific clients with altnames settings
The default behavior for NetBackup is to allow NetBackup administrators running the
NetBackup Administration Console, which is connected to a master server, to be able to
restore to any client in that environment.
To prevent server-directed restore on a NetBackup client:
• On Windows clients: In the Backup, Archive, and Restore interface, in the toolbar,
select File > NetBackup Client Properties > General, then clear the Allow server-
directed restores check box.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
NetBackup Backup
Archive and Restore
(BAR) interface
Windows Backup
Archive and Restore
(BAR) interface
OpsCenter
Operational Restore
There are four different ways to perform restore operations within NetBackup.
• Restores can be initiated from the NetBackup Backup Archive and Restore (BAR)
interface, or by using the Windows Backup Archive and Restore (BAR) interface.
Note: Although the Windows Administration console is no longer supported since
NetBackup 7.7, the Windows BAR tool is still supported, primarily for user backups
of Windows clients. Detailed information about using the Windows BAR console is
provided in Appendix D of this course.
To perform an administrator-directed restore to a specific client, use the Backup,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Archive, and Restore interface on the master server that backs up the source client.
To perform a client-directed restore, use the Backup, Archive, and Restore interface
on a client machine.
• Administrator restores can be initiated from OpsCenter. See the NetBackup
OpsCenter Administrator’s Guide.
• Experienced administrators may prefer to use the bprestore command. See the
NetBackup Commands Reference Guide.
After completing this topic, you will be able to restore files and monitor
restore operations using the Backup Archive and Restore (BAR) interface.
After completing this topic, you will be able to restore files and monitor restore
operations using the Backup, Archive, and Restore (BAR) interface.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
10
To perform a restore using the Backup, Archive, and Restore interface, follow the steps
shown on this slide. This procedure is demonstrated in detail in this topic.
You can start the BAR interface either using the NetBackup Administration Console (by
selecting Backup, Archive, and Restore in the object tree pane), or as a standalone
application. On a Windows client, open nbwin.exe (or click on the Backup, Artchie,
and Restore shortcut), and on a UNIX client, use the jbpSA & command.
By default, NetBackup clients are configured to allow NetBackup administrators on a
master server to direct restores to any clients. These are referred to as Server-directed
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
11
One of the first steps is specifying the NetBackup hosts and policy types by selecting
Actions > Specify NetBackup Machines and Policy Type from the menu, or clicking on
the corresponding button. For normal user-directed restores to the original client,
accept the default settings.
• Server to use for backups and restores: This setting defines the master server used
for restore (not the media server). If you need to add a master server to the drop-
down list, click Edit Server List, and add the master server to that list, and then
select that server.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
12
Select the appropriate restore type from the drop-down menu under the Restore Files
tab. Restore type selections include:
• Normal Backups
• Archived Backups
• Raw Partition Backups
• True Image Backups
•
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
13
After you specify a restore type, you need to identify the backups you want to view. This
is performed by setting a date range which NetBackup uses to limit the backup images
examined for restores. Instead of specifying a date range, you can choose your backup
from a list. This changes the date range based on the selected images. From these
backups, you eventually select the files for restore.
The Backup, Archive, and Restore interface provides two ways to set this date range:
• Specify a date range
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
You can specify a range of dates for the backups you want to view. Click the Use
calendar to set date range button, and the Date Range dialog box is displayed. Select
a Start Date and an End Date and click OK.
• Backup list
Click the List Backups button to display a list of backups. Select the full backup, as
well as the subsequent differential or cumulative incremental backups. Effectively,
this just sets the start date and end date that NetBackup uses to examine prior
backups.
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
14
After selecting the backup images you wish to restore from, you should see a list of files
and folders you can restore from at the bottom pane. If a timeframe was selected that
includes multiple backup images, then it is possible that multiple versions of a file or
folder can be restored. By default, the Backup, Archive, and Restore console displays the
most recent version of the file, for the backup images that are currently selected by the
date range specified.
If you want a list of all files from the selected backups, including files for which there are
multiple versions from different dates, click the Show all backup in the specified date
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
range button. If you want to return to view only the latest version of the files, click the
Show most recent backup in the specified date range button.
To search for files in a backup, click the Find items to restore button.
To browse for files in a particular location, set the Browse directory as appropriate.
Note that the default browse directory may be set in a manner which does not
correspond to files or folders that have been backed up. Set it to “/” manually, if
necessary.
To determine which files can be restored, you may need to refresh the screen. Select
View > Refresh. The items you can restore are displayed in the Contents of selected
directory list. From this list, determine which files you can restore.
It is possible that a restore requires data stored on multiple backup images. Examples of
such a distribution of backup images include:
• Restore from full and incremental backups.
The following example filters out a directory of files that were backed up.
bplist –C train2 –l –s 01/01/10 –R D:\myfiles
The –t option enables bplist to reference different policy types. The following
example is for bplist syntax for Microsoft Exchange backups.
bplist –C train2 –t 16 –l –s 01/01/10 –R /
For a detailed explanation of the options you can use with the bplist command, see
the NetBackup Commands Reference Guide.
Technical Article 100016074: A listing of policy types and how they are used with bplist
and other NetBackup commands (http://www.veritas.com/docs/100016074) describes
policy types and how they are used with bplist and other NetBackup commands.
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
16
To mark a folder for backup or restore, select the check box to the left of the folder.
• A checked box ( ) indicates that all of the files and subfolders within that folder
are marked.
• A partially checked (forward slash mark) box ( ) indicates that only some of the
files or subfolders within that folder are marked.
• To mark all the files (and folders) that are currently displayed, select Edit > Mark
Displayed Files.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5
Mark files to Disk
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
17
After selecting the files and folders to restore, click the Preview button.
The Media Required dialog box is displayed with a list of the media required to perform
the restore. Use the contents of this dialog box to verify which media are required to
perform the restore. This helps you determine if you require a tape that is currently
offsite or otherwise unavailable.
Note that for disk-based media, the Preview button is not necessary, and returns the
message “No media is required for restore. Images are on Disk.” If the backups are on
disk, instead an informational message is provided to inform you that no media is
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Mark files to
5
restore
Preview required
6
media
Set destination /
7 Initiate the
restore options
restore
8 Initiate restore
9 Monitor restore
18
The Destination pane of the Restore Marked Files dialog box grants you varying levels
of control over the placement of the files:
• Restore everything to its original location (Default): Restores items to the file or
path from which they were backed up
• Restore everything to a different location (maintaining existing structure): Restores
items to a file or path other than the path from which they were backed up
• Restore individual directories and files to different locations: Restores items to
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
paths other than the path from which they were backed up
• Create and restore to a new virtual hard disk file: For Windows 2008 R2 clients and
Windows 7 clients, you can restore marked items to a new, virtual hard disk (VHD)
file. If you select this option, you must specify a new VHD file. You cannot restore to
an existing VHD file with this option.
When you enter the destination path and the file name for the new VHD file, do not
include the .vhd extension. The extension is added automatically.
After you enter the new destination path and the file name, click Setting. Set the
VHD file size and select the behavior of the file as follows:
• Virtual hard disk size: Select the VHD file size. Ensure that you do not exceed
the maximum available amount of space.
• Dynamically expanding (default): If you select this option, the VHD file expands
up to the specified virtual hard disk size.
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
20
You can monitor the progress of the restore operation from the Task Progress tab in the
Backup, Archive, and Restore interface.
Here you see the progress of the restore job as it executes. If an error is encountered,
determine the cause of the problem and perform corrective actions.
Restores can also be monitored from the Activity Monitor in the Administration
Console.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to restore files and monitor
restore operations using OpsCenter Operational Restore.
21
After completing this topic, you will be able to restore files and monitor restore
operations using OpsCenter Operational Restore.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
22
Operational Restore provides a simplified search and retrieval mechanism that works
across multiple NetBackup domains, and was introduced in NetBackup OpsCenter 7.5.
Although it requires an OpsCenter server, it comes at no cost and does not require any
license.
This feature enables restores to be initiated using the OpsCenter Web console and
removes the need to install the BAR console on customer workstations. The search
capabilities facilitate searches without requiring specialized knowledge of the backup
environment.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Operational Restore includes enhanced filtering selection, the ability to use wildcards
for search, and manual browsing of directory and sub-directory structures of backed-up
images for files with specific metadata. Additionally, a restore cart enables you to view
file selections from multiple search and browse operations and restore them at a later
time, or to preview the media required. No additional licensing or infrastructure is
necessary.
For additional information on using Operational Restore, see the NetBackup OpsCenter
Administrator’s Guide.
24
After clicking the Restore Files and Directories link, the Files and Directories Restore
wizard is displayed.
The Files and Directories Restore wizard consists of three panels:
• Select Files or Directories enables you to perform simple or advanced search
operations for locating specific files or directories that you want to restore.
• Restore Options enables you to select a number of restore options, such as
destination client, destination path, and overwrite options for the selected client.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• The Summary displays the list of files or directories that you have selected for
restore.
Under the Select Files or Directories tab, the Search tab is displayed.
3. Make your search selections based on the following search criteria:
• Select a time frame that you want to search. The default time frame is Month.
• File or Directory name: Enter a full path using a path delimiter of forward slash (/)
on UNIX or back slash (\) on Windows, or enter a specific file or directory name.
Alternatively, if the exact directory or file name is not known, use the * (any number
of any characters) and ? (any one character) wildcards.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Search within Clients: Specify the set of clients whose backup information you want
to search. You can search multiple clients from multiple master servers.
• Select a view from the View drop-down list.
• Select a master server from the Master Server drop-down list. All NetBackup
master servers that are a part of the selected view are displayed.
• Specify the clients whose backup information you want to search.
When you click Browse and select clients, the Browse Clients dialog box is displayed.
The following options are displayed in the dialog box:
• Selected View: The view that you selected from the View drop-down list is
displayed. If you select a view of type Master Server, all NetBackup master servers
that are added to the view are displayed under the Name column. If you select a
client-type view, the clients are displayed under the selected view in the Name
column.
To perform an advanced search, you can specify advanced search criteria in addition to
the simple search criteria. The Advanced Search criteria are optional. For more
information about the advanced search criteria, see the NetBackup OpsCenter
Administrator’s Guide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4. After you have made all of your search selections, click Search.
It may take some time for OpsCenter to display the search results. The time to
display the search results may increase with the number of selected clients.
OpsCenter highlights the search results at the bottom of the pane in a table.
This slide presents the procedure to browse the protected files and directories on a
client. This method enables you to select the client to be browsed and specify a time
frame for backup selection. You can select only one client at a time. The most recent
backup in the specified date range is shown by default.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Under the Search tab, you can see that the search has completed successfully. Search
results are displayed while the search is in progress.
The filter button ( ) at the top of the search results table enables you to further filter
the search results. The result is a filtered subset of the last search result from the
OpsCenter database.
You can also customize the search results table to display sort order, page size, columns
displayed, and column order. Click the Change Table Settings ( ) icon at the top of the
search results table to access the table customizations page.
By default, the search results table lists the following default columns: File or Directory
Name, File or Directory Path, Backup History, Last Backup Time, Modified Time, Client,
and Size. Operational Restore enables you to add Master Server, Last Accessed Time,
and Backup ID columns to the table.
If there are additional results, the number of rows and pages is displayed.
5. To select one or more files or directories to restore, mark the check box next to the
file or directory.
• To restore the files or directories now, click Restore now.
• If you want to add the selected files and directories to the Restore Cart and
restore them at a later time, click Add to Restore Cart.
To display the backup history, click the Backup History Selection link for the file or
directory that interests you. The Backup Timeline window is a timeline view of backups
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
for a specific file or directory. At the top of the Backup Timeline window, the name and
location of the selected backup’s file or directory are displayed. The timeline displays
icons that each represent a different backup or snapshot. By default, the primary
backup copy of the most recent backup for this file or folder is selected, however this
window enables an alternate backup copy to be chosen by clicking on that icon.
The Backup table in the middle of the window displays information about the backup
that is selected from the timeline view. It displays information, such as backup time,
policy name, policy type, backup type, and so on. Click an icon to view the details of the
specific backup in the Backup table. After you select the specific backup image that you
want to restore from the Backup table, the copies that are associated with the backup
image are displayed in another table at the bottom of the window. The Copies of
Selected Backup table displays information about the copies that are associated with
the selected backup image. By default, the primary copy is selected.
files from the Restore Cart. For more information about performing operations on the
Restore Cart, see the NetBackup OpsCenter Administrator's Guide.
When you click Restore now, the Restore Options panel is displayed.
You can specify restore options for the files and directories that you selected, such as
destination client and paths, and overwrite and access control options. This panel
enables you to specify the restore options for each source client from which a file or
directory has been selected to be restored.
7. Prior to initiating the restore, click Preview Media to view the media required for
the restore operation and to determine the availability of the required media.
The Preview Media dialog box is displayed. This helps you determine whether the
required tape is in the library. If the selected backups are all on disk, this option is
not applicable.
When you have finished with the Preview Media dialog box, click Close.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The Summary panel displays the list of files and directories that have been selected for
restore. It also displays information about the current location of these files and
directories and where they are to be restored.
The Summary panel shows a table that includes the source file name, the source file
path, the source client, the destination file path, and the destination client.
At this point, you have one last opportunity to remove files or directories from the
Summary panel. To remove files or directories that you do not want to restore, click the
Remove files or directories button.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8. In the Summary panel, click Restore to restore all the files or directories.
The corresponding restore jobs are triggered, and the File or Directory Restore
Launch Status dialog box is displayed. This dialog box identifies the job ID of the
restore job, the name of the master server that is associated with the client on
which the file resides, and the name of the source client.
Click OK to navigate to the OpsCenter Monitor > Jobs tab and view the job progress
details.
The Monitor > Jobs view provides details about NetBackup jobs. In this example,
detailed information about Job ID 264, the restore job, is displayed. Notice that the job
is selected in the content pane, and additional information is displayed in the details
pane.
After completing this topic, you will be able to monitor restore operations,
and identify common restore-related issues.
34
After completing this topic, you will be able to monitor restore operations, and identify
common restore-related status codes.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
35
You can also monitor the progress of the restore operation from the NetBackup
Administration Console Activity Monitor.
Suspending and resuming a restore job
If you are a NetBackup administrator, you can suspend a checkpointed restore job and
resume the job at a later time.
For example, while running a restore job for several hours, you may receive a request
for a second restore of a higher priority that requires the resources being used by the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
first job. You can suspend the first job, start the second restore job, and let it complete.
You can later resume the first job from the Activity Monitor and let that job complete.
To suspend a restore job, right-click the job in the Activity Monitor and select Suspend.
To restart the job, right-click the suspended job and select Resume. You can also use the
Suspend ( ) and Resume ( ) buttons in the toolbar.
Limitations to Checkpoint Restart for restore jobs include the following:
• The restore restarts at the beginning of the last checkpointed file only, not within
the file.
• Only the backups that are created using Standard or MS-Windows policy types are
supported.
• Third Party Copy and Media Server Copy images that use Standard policy types are
supported, but cannot be suspended or resumed if the backup image has changed
blocks.
Issue Resolution
Incorrect interpretation of • Check the spelling of the path, file name, and exclude rule.
restore directives • Ensure no information is missing.
Insufficient disk space Ensure there is sufficient space on the destination client or file system.
Improper file permissions Ensure you have read permission for files in the backup image and write
permission for the restore destination.
Access control lists (ACLs) • Ensure the restore is not cross-platform.
• Ensure the tar file is a NetBackup-modified tar file.
Restore from non- Change the primary copy image from tape to disk or from offsite to onsite.
preferred location
Incorrect restore criteria Confirm the policy type, server and client names, restore type, browse
directory, and date range.
37
/usr/openv/netbackup/logs/bplist/
/usr/openv/netbackup/logs/bprestore/
• Windows
install_path\NetBackup\logs\bplist
install_path\NetBackup\logs\bprestore
Create these directories with public-write access. The commands create debug logs
within the respective directories, which you can use for detailed troubleshooting.
If a non-root user is specified under USEMAIL = mail_address in the $HOME/bp.conf
file of a NetBackup UNIX client, NetBackup sends an e-mail containing the restore
completion status to mail_address. This message is sent when the restore process
completes.
39
When attempting a restore, you may receive an error stating No Files Found. This is a
common occurrence when some of the restore fields aren’t set correctly for the data in
question. Some parameters to check include:
• Source client: Make sure to use the correct host name for the source client. If the
image was registered under the short name, console, then use the short name. If
the backup was done using the FQDN, console.example.com, use the FQDN
• NetBackup server: Ensure that the correct master server name is used.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Date range: Enter the date range for valid backups. If the date range you are using
doesn’t yield any results, verify that backups completed for that client, during that
time.
• Browser directory: The directory needs to be set so that it is valid for the backup
data. If the default directory shown is for data that was not included in the backup,
then no files will be found. Change the folder to one that is relevant to your backup.
This primarily applies to UNIX and Linux-based images.
• Restore type: If a restore type is chosen that doesn't match your backup, then no
data will be shown. For many backup types, the Normal Backups restore type
should be chosen.
• Keyword: Ensure this entry is clear, if keywords are not being used. Otherwise the
backup images shown will be limited to those using the keywords selected.
40
The table on this slide summarizes how restore jobs can be managed using the
NetBackup Administration Console, NetBackup commands, and OpsCenter.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Key points
– You now know how to initiate and monitor restore operations using the Backup, Archive, and Restore
interface and Operational Restore.
– You also know how to monitor restore jobs.
– Finally, you learned how to identify common restore-related status codes.
• Reference materials
– NetBackup Administrator’s Guide
– NetBackup Commands Reference Guide
– NetBackup Status Codes Reference Guide
– NetBackup Troubleshooting Guide
– NetBackup Backup, Archive, and Restore Getting Started Guide
– OpsCenter Administrator’s Guide
– http://www.veritas.com/support
41
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
42
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
43
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. True
B. False
44
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. True
B. False
45
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
46
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
47
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
48
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
49
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-50
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Configuring Disk Pools” lesson in the “Veritas NetBackup 8.1:
Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
Understanding disk pools and Describe disk-based storage, including disk pools and AdvancedDisk
AdvancedDisk storage.
Configure storage servers, AdvancedDisk disk pools, and
Configuring AdvancedDisk
AdvancedDisk storage units.
Monitor and report on configured AdvancedDisk disk pool devices,
Managing AdvancedDisk storage
as well as perform common AdvancedDisk management tasks.
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to describe disk-based storage,
including disk pools and AdvancedDisk storage.
After completing this topic, you will be able to describe disk-based storage, including
disk pools and AdvancedDisk storage.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
PureDisk Usesspanning
a Media Server Deduplication Pool (MSDP).
disk volumes
• Scalable: Easily expand
• Lesson: Configuring Media Server Deduplication capacity; Handles unlimited
• Document: NetBackup Deduplication Guide
theoretical
• License: NetBackup Data Protection Optimization Optioncapacity
The slide reviews disk storage types in NetBackup (listed by the corresponding disk type
identification categories used in NetBackup), including BasicDisk, AdvancedDisk,
OpenStorage and PureDisk.
This lesson discusses the AdvancedDisk storage type, specifically using simple disk pools
of multiple disk volumes, on a single media server.
Creating disk pools in NetBackup offers several benefits over basic disk storage units.
Resources are used more efficiently by logically combining disk resources on a single
server or across multiple servers. Using disk pools unlocks a number of additional
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Disk
enclosure Storage server
(logical)
OpenStorage
Technology (OST)
Disk
volume Disk pool Media
server
(physical)
storage media. Traditionally, the storage media may be either disk or tape media.
• OpenStorage Technology (OST) is a Veritas API that allows NetBackup to
communicate and manage various storage implementations to integrate backup
functionality, including share disks, balance load and performance, use the disk
appliance capabilities such as deduplication, provision storage, and optimize
duplication and replication.
• A Storage server is an entity that was created in NetBackup to write the data to and
read the data from the disks that support OST. In some cases, such as NetBackup
AdvancedDisk, the storage server and the media server reside on the same
NetBackup system. In other cases, the NetBackup media server communicates with
a storage server provided by Veritas or another storage vendor using NetBackup
OST.
NetBackup Appliances:
• Simplify initial configuration and daily management of
the backup environment.
• Perform the role of storage server and media server in
one.
• Allow configuration of both AdvancedDisk and
deduplication (MSDP) disk pools using the included
storage disk volumes.
• Come in multiple form factors, such as the NetBackup
5240 and 5330 appliance, with continually increasing
performance and storage capabilities.
• Have additional capabilities that include deduplication,
multiple connectivity options (Ethernet and Fibre
channel), and replication.
The NetBackup appliance is a solution that simplifies the initial configuration and daily
management of your backup environment. The goal is to provide a solution that
eliminates the need to provide dedicated individuals to manage the backup
environment.
NetBackup appliance deployment consists of the complete installation and
configuration of all appliance components to create a backup environment that is ready
to use. NetBackup appliances can be easily integrated into an existing NetBackup
environment.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Use vendor-supplied software plug-in, installed on media servers that communicate with
the OST server
• To find supported functionality and capabilities:
– Refer to the Hardware and Cloud Storage Compatibility List (HCL) at
http://www.netbackup.com/compatibility
– Includes OpenStorage - Supported Functionality:
OpenStorage is a Veritas API that enables NetBackup to communicate with the storage
implementations that conform to the API. Disk appliance vendors participate in the
Veritas OpenStorage Partner Program. Veritas qualifies their storage solutions for the
OpenStorage API. The vendor's storage controls the storage format, the location where
the images reside on the storage, and the data transfer method. As a result,
performance and storage utilization are highly optimized.
Third-party OpenStorage servers include disk appliance vendors that provide a software
plug-in that is installed on the NetBackup media server. NetBackup media servers use
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
In the event that third-party OpenStorage vendors are being used in a NetBackup
environment, the OpenStorage vendor’s disk array is considered the disk enclosure and
the disk pool. The disk array is also the storage server, since it is responsible for the I/O
to and from disk.
To be able to communicate correctly with the OpenStorage vendor’s disk array, the
NetBackup media server need to ensure that a NetBackup plug-in, which is provided by
the third-party vendor, is installed.
This is an environment where the media server and storage server are not contained in
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10
OST Cloud Storage plug-ins enable Veritas NetBackup to access Cloud Storage Solutions.
Either the storage vendor or Veritas provides a software plug-in, which is installed on
each NetBackup Media Server that is connected to the cloud solution.
Supported vendors may include ACP, Amazon, AT&T, China Mobile, China Telecom,
Chunghwa Telecom, Cloudian, Datish Systems (OpenDedup), Deutsche Telekom, EMC,
Fujitsu, Google, HGST, Hitachi, Huawei, IBM, Microsoft, NetApp, Oracle, Quantum,
Rackspace, Red Hat, Scality, StorReduce, SUSE, SwiftStack, Telefonica, and Veritas.
OST Cloud support information, including a detailed list of supported vendors, solutions,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
and functionality, is listed in the Hardware and Cloud Storage Compatibility List (HCL) at
http://www.netbackup.com/compatibility.
WAN LAN
Cloud storage
vendor Master
Media
servers server
Cloud storage
• Disk pool
data mover
• Disk enclosure
• Storage server
Clients
11
In an environment using a cloud storage vendor, the storage server is the cloud vendors
server. The data movers are the NetBackup media servers, which are assigned to the
storage units that target the disk pool with the cloud storage server.
Multiple cloud storage data movers can target the same cloud storage disk pool, to
assist with load balancing the client’s data.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to configure storage servers,
AdvancedDisk disk pools, and AdvancedDisk storage units.
12
After completing this topic, you will be able to configure storage servers, AdvancedDisk
disk pools, and AdvancedDisk storage units.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Internal
storage
13
An AdvancedDisk disk pool enables several disk volumes to be combined into one
logical storage destination in NetBackup. The pool is accessed by a single storage server,
which must also be a NetBackup media server. These disk volumes may exist across
multiple physical disk arrays or internal storage disk volumes on a storage server.
Generally, pooling disks from a server into a single pool is a good idea, however, Veritas
recommends placing disks of significantly different sizes or speeds into separate pools.
Even though high-performing SAN disks and slower drives could go into the same pool,
separating them into separate disk pools allows for predictable performance behavior.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
An AdvancedDisk storage unit must be configured to target a single disk pool, and it
cannot specify individual disk volumes in a pool. However, more than one storage unit
can be configured for a single disk pool. This may be performed to allow higher priority
policies to have additional concurrent write streams.
NetBackup assumes exclusive control of all disk volumes configured within a disk pool,
enabling NetBackup to manage and report disk capacity accurately. A disk volume
cannot exist in more than one disk pool.
If NetBackup is unable to write an image to a single disk volume in a disk pool, the
backup spans to the next available disk volume. Spanning can occur from any volume to
any other volume in that disk pool. It is not possible for a single backup image to span
multiple disk pools, even if the disk pools exist in a storage unit group.
14
The slide on this page provides an overview of the steps involved to configure a usable
disk pool and corresponding AdvancedDisk storage server.
1. First, determine whether or not the target media server is already configured as an
AdvancedDisk storage server. This process only needs to be performed once per
media server, regardless of the number of AdvancedDisk storage pools hosted on
the media server.
2. Run the Configure a Disk Storage Server wizard if the host needs to be configured as
a storage server, or in other words, if this is the first time the host is being
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
nbdevconfig –creatests
15
Before you can create an AdvancedDisk pool, you must configure an AdvancedDisk
storage server. To do this, use the Storage Server Configuration Wizard.
You can also use the nbdevconfig -creatests command to create a storage
server from the command line. The nbdevconfig command and syntax is discussed
in the NetBackup Commands Reference Guide. The nbdevconfig command is found
in the following directory:
• UNIX: /usr/openv/netbackup/bin/admincmd
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Windows: install_path\bin\admincmd
The Disk Pool Configuration Wizard can be started by clicking on Configure Disk Pool,
however this requires that the media server has already been configured as a storage
server first.
The first screen of the Storage Server Configuration Wizard has you select the disk
type. Select AdvancedDisk and click Next.
nbdevconfig –creatests
16
On the next screen you need to select the media server you are configuring as the
storage server. Each media server will only need to be configured once as an
AdvancedDisk storage server, even if multiple disk pools are created for that storage
server.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
17
The Storage Server Configuration Status will then show if the storage server is
configured successfully.
By default the wizard will then go on to help you create a disk pool for that storage
server. You can alternatively close the wizard without this checkbox, and run the disk
pool configuration wizard manually, at a later time.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
nbdevconfig –createdp
18
The Disk Pool Configuration Wizard is automatically started, by default, when you click
Next at the end of the Storage Server Configuration Wizard.
To create a disk pool outside of the wizard, from the NetBackup Administration Console,
expand Media and Device Management > Devices. Right-click Disk Pools and select
New Disk Pool. The Disk Pool Configuration Wizard is displayed. You may also access
the Disk Pool Configuration Wizard by clicking the master server in the Administration
Console.
You may also use the nbdevconfig command to configure a new disk pool from the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
command line.
No disk pools exist by default.
Select the disk volumes to be included in the disk pool. A disk volume must be
formatted and mounted within the operating system before it can be selected for an
AdvancedDisk storage unit. Do not select disk volumes that have already been
configured in another pool.
Note that the entire disk volume will be used by the AdvancedDisk pool, and that no
directory or folder can be specified in the configuration.
nbdevconfig –createdp
19
Assign a name to the pool and optionally add comments about its function. Configure
additional disk pool information as follows:
• High water mark: The percentage of used capacity at which NetBackup considers a
disk volume in the pool to be full.
A disk volume within a disk pool is assigned fewer backup jobs as it approaches the
high water mark.
• Low water mark: The percentage of used capacity at which a clean-up operation
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
stops purging backup images as a result of the disk pool reaching the high water
mark
• Maximum I/O Streams: Limits the number of streams that can be directed to a disk
simultaneously. It is used to avoid disk thrashing, which is the result of too many
jobs writing to the same disk simultaneously.
The default is that there is no limit, at the disk pool, however there are limits that
are enforced at the storage unit. A storage unit supports up to 4096 streams, with a
default of 1 concurrent job running. However, because you can setup multiple
storage units for one disk pool, this value allows you to control the maximum I/O
streams to the disk pool, regardless of any storage unit limits.
For more information on these properties, click on the Help button in the Wizard.
20
The Disk Pool Configuration Status will then show if the disk pool is configured
successfully.
By default the wizard will then go on to help you create a storage unit for that disk pool.
You can alternatively close the wizard without this checkbox, and create a storage unit
manually in the NetBackup Administration Console.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bpstuadd
21
Next, configure the properties of the storage unit for this disk pool.
A Media Server option is available to limit the storage unit to specific media servers.
In most cases, you must increase the Maximum concurrent jobs setting from the
default setting of 1. For example, on the slide we have changed the maximum
concurrent jobs to 3, to correspond to the number of jobs that the three separate disk
volumes (G:\, H:\, and I:\) in this pool should be able to concurrently run without issue.
The Maximum fragment size setting normally does not need to be changed. Changing
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
this value may impact backup and restore times, and should be tested if any changes
are made.
If you chose to configure the storage unit, no additional configuration is required. The
storage unit created for the disk pool may now be selected as a destination within a
backup policy.
The disk pool configuration is complete.
nbdevquery -liststs
22
After a storage server has been configured, it may be viewed in the NetBackup
Administration Console by expanding Media and Device Management > Credentials >
Storage Servers. Notice that the Administration Console does not list BasicDisk storage
servers because all media servers support BasicDisk by default.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
nbdevquery -listdp
nbdevconfig
23
To view disk pools using the NetBackup Administration Console, expand Media and
Device Management > Devices and select Disk Pools to list all configured disk pools.
The columns display the general configuration for the storage unit, in addition to a
percentage full value, showing the total used capacity of the disk pool.
Right-click the disk pool and select Change to modify disk pool settings, such as water
marks, and limiting the number of I/O streams.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bpstulist
24
After an AdvancedDisk storage unit has been configured, it can be viewed in the
NetBackup Administration Console by expanding NetBackup Management > Storage
and selecting Storage Units. Notice that the master_advdisk_pool_stu AdvancedDisk
storage unit is displayed with a Storage Unit Type of Disk.
Right-click and select Change to modify storage unit settings, such as maximum
concurrent jobs.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to monitor and report on
configured AdvancedDisk disk pool devices, as well as perform common
AdvancedDisk management tasks.
25
After completing this topic, you will be able to monitor and report on configured
AdvancedDisk disk pool devices, as well as perform common AdvancedDisk
management tasks.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bpminlicense
Article 100024025: NetBackup Traditional and
nbdeployutil Capacity License Deployment Utility (nbdeployutil)
26
Many licensed options in NetBackup are capacity-based; this means that these options
license a specific amount of data storage of a particular type. The Flexible Disk Option,
which tracks space usage for AdvancedDisk pools, is capacity-based.
Access the NetBackup License Keys dialog box, select Help > License Keys, and
determine if you have the Flexible Disk Option.
Capacity-based licensing applies only to the used capacity (active backup images),
rather than the total capacity of the storage units or disk pools.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
To report on the actual disk space usage and NetBackup capacity compliance, you will
need to run the nbdeployutil command. For assistance, refer to Article 100004107:
Late Breaking News for the Capacity Licensing Utility (nbdeployutil), found online at
http://www.veritas.com/docs/100004107 and Article 100024025: NetBackup
Traditional and Capacity License Deployment Utility (nbdeployutil), found online at
http://www.veritas.com/docs/100024025.
27
For backups targeting a disk pool, NetBackup estimates the size of a backup before
selecting a backup destination. The estimate is based on the size of the most recent
similar backup using the policy, schedule, client, and stream (the file list for a specific
job) as criteria. NetBackup adds 20 percent to this size, and it seeks an appropriate
storage destination.
The disk volume in the disk pool with the most free space is used. If the disk does not
have enough space to store the entire image, the job still runs, and the backup image
will span across multiple disk volumes in that disk pool.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After a disk volume is selected, the estimated backup size is reserved on the selected
volume within NetBackup. If new backup jobs are initiated while all disk space is
reserved, the new backup jobs queue until the reserving jobs complete.
A disk pool is configured with high and low water mark values, affecting both the pool
as a whole and its individual disk volumes. At the disk volume level, when the used
capacity percentage exceeds the high water mark value, jobs are no longer assigned to
that disk volume. NetBackup considers a pool to be full when all of its disk volumes
have reached the high water mark value.
When a disk volume contains staged backup images (from a Storage Lifecycle Policy),
the images are considered potential free space if they have already been duplicated.
This is discussed in further detail in the Duplicating Backups lesson. Images that are
staged, but not yet duplicated, are considered used space.
28
NetBackup tracks status information for all disk volumes in a disk pool, and a status for
the disk pool itself. When everything is working properly, the disk volumes will be in an
UP state, and the disk pool will also be in an UP state.
If there is a problem with one disk volume, it will be put into a DOWN state. This can
also be performed manually by the administrator in the case of disk volume
maintenance. The disk pool can still be in a usable UP state as long as there are other,
available disk volumes. Backups jobs should run normally, as long as there is available
space, however restore jobs that use those specific DOWN volumes will fail.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
If the entire disk pool becomes unavailable it will be in the DOWN state. This can also be
performed manually by the administrator in the case of disk pool maintenance. In this
case the state of the disk volume is irrelevant, and any backup or restore jobs using this
disk pool will return with a status 2073: Disk pool is down. Note that if the disk pool is
brought down manually by an administrator (for maintenance for example), the disk
volumes will normally still appear in the UP state, despite the fact that they cannot be
accessed for backups.
29
The state of both disk pools and disk volumes can be set UP or DOWN, which is similar
to the state of a tape device. To change the state of a disk pool using the Administration
Console, right-click the disk pool in the Device Monitor, and select Up Disk Pool or
Down Disk Pool.
You can also use the nbdevconfig command to change the state of disk pools or disk
volumes as follows:
nbdevconfig -changestate
-dp pool_name
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
-stype storage_type
-state UP|DOWN|RESET
nbdevconfig –changestate
-dp pool_name
–dv disk_volume_name
-stype storage_type
–state [UP|DOWN|RESET]
When a disk pool or disk volume is in a DOWN state, NetBackup considers it to be
unavailable to receive new backups. Typically, this feature is used to prevent backups to
a disk pool, or to prevent backups to an individual disk volume in a disk pool during
maintenance.
30
• Disk Logs: Shows log messages related to NetBackup disk activity. This is equivalent
to running bperror –DiskPool.
• Disk Storage Unit Status: Shows storage unit information. This is equivalent to
running bpstulist.
• Disk Pool Status: Shows disk pool status, such as whether the disk pool is in an UP or
DOWN state. This is equivalent to running nbdevquery –listdp for disk pool
status and nbdevquery –listdv for disk volume status (which cannot be seen
in the NetBackup Administration Console).
✓
1
Server rank based on CPU,
processes, and memory
2
Fewest number of
NetBackup jobs ms1_advdisk_stu ms2_advdisk_stu ms3_advdisk_stu
LoadBalance_stu_group
3
Least reserved space
4
Least recently used Job
31
When a backup jobs is sent to a storage unit group, NetBackup must decide on which
storage unit to use for that job. Storage unit group methods include Prioritized, Failover,
Round Robin, and Media Server Load Balancing. The first three of these methods were
discussed in the Configuring NetBackup Storage lesson.
Media Server Load Balancing chooses the best available media server based on a
ranking system. NetBackup chooses the server based on various criteria. If two or more
servers share the best available rank, NetBackup continues to apply additional criteria
until one media server remains. The order of examined criteria is:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
32
When configuring a storage unit group, the Storage unit selection area defines how the
storage units will be selected during a backup:
• Prioritized: Choose the first storage unit in the list that is not busy, down, or out of
media.
• Failover: Choose the first storage unit in the list that is not down or out of media.
• Round Robin: Choose the least recently selected storage unit in the list.
• Media Server Load Balancing: Choose the best available media server based on a
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
ranking system.
The first three of these methods were discussed in more detail in the Configuring
NetBackup Storage lesson.
Note: Media Server Load Balancing selection supports most storage types including
AdvancedDisk, tape storage, and deduplication storage, but does not support basic disk
storage.
Task Procedure
1. Source a new disk volume that is not used by another process or application
Add volumes to
2. Add the disk to the disk pool using the command:
a disk pool
nbdevconfig –adddv
33
The slide mentions some other disk pool management tasks that you may need to
perform, such as adding volumes to a disk pool, removing volumes, or removing the
entire disk pool.
To add a volume to an existing disk pool, simply source an empty disk volumes (ensuring
it isn’t used by any other process or application), and use the command shown on the
slide to add it to the disk pool. Prior to NetBackup 7.5, an option to add disk volumes
did not exist. Instead, a procedure to create and merge disk pools was required. Refer to
the documentation for your version of NetBackup for details.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Alternatively, you can increase the storage space in a disk pool by resizing the existing
disk volumes. NetBackup will recognize the additional storage the next time the disks
are scanned by the NetBackup processes. You can manually cause NetBackup to
reexamine the storage by running an Inventory Disk Pool in the NetBackup
Administration Console, or with the nbdevconfig –inventorydp command.
Removing disk volumes can be performed as long as no current NetBackup backup
images exist on the disk volumes, and the disk pool and disk volume are in a DOWN
state and not in use. In addition, before you remove a disk pool, you must remove all
associated storage units.
To delete an entire disk pool, you must remove all active backup images, and all
associated storage units.
Disk pools Devices > Disk Pools nbdevquery -listdp –U Monitor > Devices > Disk
Reports > Disk reports > Disk Pools
pool status Reports > Report Templates
> Backups > Disk Pool
Reports
Reports > Report Templates
> Disk Based Data
Protection > Current Disk
Usage
Disk volume status nbdevquery -listdv -U
-stype disk_type
-dp pool_name
-dv volume_name
34
The table on this slide summarizes the advanced disk and disk pool reporting tools using
the NetBackup Administration Console, NetBackup commands, and OpsCenter.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Key points
– You now know what disk-based storage is and how it is used. You can describe disk pools,
AdvancedDisk, and OpenStorage.
– You can now configure and manage storage servers, AdvancedDisk disk pools, and AdvancedDisk
storage units.
– You now know how to monitor the status of configured devices and view reports for configured devices.
• Reference materials
– NetBackup System Administrator’s Guide
– NetBackup AdvancedDisk Storage Solutions Guide
– NetBackup OpenStorage Storage Solutions Guide for Disk
– NetBackup Commands Reference Guide
– http://sort.veritas.com/netbackup
– http://www.veritas.com/support
35
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
37
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
38
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
39
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Disk enclosure
B. Logical grouping of media servers
C. Collection of disk volumes presented as a single entity
D. None of the above
40
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Disk enclosure
B. Logical grouping of media servers
C. Collection of disk volumes presented as a single entity
D. None of the above
41
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
42
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
43
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
6-44
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Configuring Media Server Deduplication” lesson in the “Veritas NetBackup
8.1: Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
Introduction to NetBackup
Describe what NetBackup deduplication is and how it works.
deduplication
Configuring NetBackup media server Configure a media server for deduplication, including creating a
deduplication media server deduplication disk pool
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to describe what NetBackup
deduplication is and how it works.
After completing this topic, you will be able to describe what NetBackup deduplication
is and how it works.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
backup, which normally goes to tape or disk, is identical to that of the previous backups.
In addition to the storage savings that come with only storing unique data, which are
significant, time and other resources are saved. Although many vendors and solutions
provide the ability to deduplicate at the target, usually at the backup storage location or
appliance, being able to deduplicate at the source (the clients) provides the ability to
significantly reduce bandwidth use, and also speeds up the entire backup process. This
is especially true when backing up clients over a WAN or slow connection.
Similar to normal backups, the first step is to determine which data needs to be backed
up. After a list of files that require processing has been established, the following high-
level procedure is used for the files:
1. The file metadata, including file permissions, directory location, file name, and so
on, is separated from the actual content of the file. The file metadata is stored by
NetBackup.
2. The file contents are logically separated into 128K segments. For file less than 128K
in size, or for the last segment of a large file, the segment is smaller than 128K.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Client-side deduplication
• Combined with MSDP, distributes deduplication work to the client.
• Reduces network bandwidth and enables higher parallelization.
• MSDP on a NetBackup Appliance: NetBackup 52xx and 53xx appliances are easy-to-
configure media servers that can also perform deduplication. NetBackup appliances
use dedicated hardware and software to optimize performance, and therefore also
support higher capacities of deduplication pools, in excess of 600 TB, depending on
the model used. The deduplication used in NetBackup appliances is also MSDP, the
same technology as discussed in this lesson.
• NetBackup client-side deduplication: Deduplicating at the source, often known as
client-side deduplication or client deduplication, is supported with NetBackup. This
feature is discussed elsewhere in this lesson.
• Third-party appliances supporting OpenStorage Technology (OST): Third-party
deduplication appliance vendors that support OpenStorage Technology (OST) can
also be managed as a NetBackup storage destination.
Load Client-side
balancing deduplication
media
MSDP server
NetBackup
storage
clients
server
MSDP
storage
8
configure and use MSDP load balancing servers. These NetBackup media servers do
not need to be configured as storage servers, but instead get the full stream of data
from the client, and perform the fingerprinting work before sending unique data to
the storage server. Minor bandwidth use is required for storage and media server
communication during this process.
• Client-side deduplication: Using this method means that the client performs the
fingerprinting and communicates with the deduplication storage server as to whether
the data is unique or has been stored previously. If the data is unique, the data is sent
over the network to the media server for storage. Minimal network bandwidth is
required.
Deduplication Deduplication
engine (spoold) manager (spad)
11
NetBackup provides the stream handlers that process various backup data stream types.
Stream handlers improve backup deduplication rates by processing the underlying data
stream.
For data that has already been deduplicated, the first backup with a new stream handler
produces a lower deduplication rate. After that first backup, the deduplication rate
should surpass the rate from before the new stream handler was used.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Client-side
deduplication
3
Clients
1 Deduplication 2 Remote
Media Server
Deduplication
Pool
Load Balancing
Server
12
their own data do not need to access these ports, and only need the standard
NetBackup ports to be open.
13
performed at the target, the deduplication media server. The deduplication server’s
CPU becomes the limiting factor of how many concurrent jobs can run. The CPU of
the client is only minimally impacted by a backup.
• Load balancing media servers: By using load balancing media servers you can also
increase the overall bandwidth. This option is great for storage servers that are
reaching CPU capacity, and in environments where you don’t want to use, or can’t
use, the NetBackup client-side deduplication feature. This prevents impacting CPU
on some heavily loaded application servers, while still distributing deduplication load.
• NetBackup OpenStorage Option: If you already have deduplication appliances
deployed in your environment, this option allows NetBackup to use and manage
them within the NetBackup infrastructure.
After completing this topic, you will be able to configure a media server for
deduplication, including creating a media server deduplication disk pool.
After completing this topic, you will be able to configure a media server for
deduplication, including creating a media server deduplication disk pool.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15
The slide provides an overview of the steps to configure a deduplication media server.
You learn how to perform each of these steps in the following slides.
The NetBackup Deduplication Guide provides much greater details around planning and
configuring the media server deduplication pool. Some of those steps includes
understanding and putting in place optimizations that are discussed elsewhere in this
lesson (such as fingerprint cache behavior) and in the Managing and Protecting the
NetBackup Catalog lesson (such as MSDP catalog protection).
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
16
To create a deduplication media server, you need to consider server and storage
prerequisites. Because fingerprinting is process-intensive, the most important factor in
deduplication performance is CPU, followed by memory size and speed, and storage
speeds.
The storage server CPU and memory constrain how many jobs can run concurrently. The
storage server requires enough capability for deduplication and for storage
management. Reducing CPU use on the storage server is possible with load balancing
servers and client deduplication.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Processors for deduplication should have a high clock rate and high floating point
performance. Furthermore, high throughput per core is desirable. Each backup stream
uses a separate core. Intel and AMD have similar performance and perform well on
single core throughput.
For greater details see the Planning your MSDP deployment section of the NetBackup
Deduplication Guide.
Note: Veritas recommends that you do not use the master server as a deduplication
storage server. Master server activity and media server deduplication activity on the
same host degrades performance. In some environments, a single host can function as
both a NetBackup master server and as a deduplication server. Such environments
typically run fewer than 100 total backup jobs a day.
17
18
The next step in activating and configuring media server deduplication is to create a
deduplication media server with a media server deduplication pool. Use the Storage
Server Configuration Wizard to do this. Veritas recommends using this wizard to create
this pool. There is also a command line method that can be used, but it is not
recommended unless your MSDP will be more than 64TB. See the NetBackup
Deduplication Guide for details.
Because it is difficult to reconfigure the media server deduplication pool after it has
been created, and after backups have been written to it, it is extremely important to
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
nbdevconfig –creatests
19
The Welcome screen is the first screen of the Storage Server Configuration Wizard. The
screen reminds you to ensure that you have physically deployed all storage devices prior
to starting this setup. It also reminds you to ensure that all software plug-ins are
installed on the media servers that will be communicating with the storage server. The
media server deduplication plug-ins are installed automatically by the NetBackup
installation.
The first screen of the Storage Server Configuration Wizard has you select the disk
type. Select Media Server Deduplication Pool and click Next.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
nbdevconfig –creatests
20
On the Add Storage Server screen, you select the media server on which to create the
storage server. You also define credentials for the selected media server. These
credentials are specific to the deduplication media server, not the operating system.
These credentials are used by the storage engine to connect to the deduplication
engine. It is important to keep these credentials in a secure and accessible location.
If you need to later change these credentials, this can be performed using the
spauser command (if the password is known) or with some additional commands and
spadb and tpconfig commands. For specific steps on reseting the password, refer
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
nbdevconfig –creatests
21
Specify the storage path on this dialog box. You may only select one storage path per
media server. You can set two additional parameters on this screen:
• Use alternate path for deduplication database
This refers to the content router index. The content router index decreases the
amount of space available on the storage server on which it is installed. Veritas
recommends moving this database to improve performance.
• Use specific network interface
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Mark this check box to specify a network interface on the media server. If the media
server that is being used has multiple interfaces, with one that should be used for
the backup network, this setting forces NetBackup to connect to the deduplication
media server using only the named interface.
Note: On Windows, you must specify a folder within the drive letter, as the wizard will
not let you continue if you only specify a drive letter.
Caution: Do not create the directories on the server prior to specifying them in the
wizard, but instead allow the Storage Server Configuration Wizard to create those
directories to ensure correct permissions are assigned.
Note: Use care when making these selections, as they cannot later by changed. Changes
to the storage server require deleting and recreating the storage server.
nbdevconfig –creatests
22
The Deduplication Load Balancing screen is only displayed if additional media servers
are available.
When you use additional media servers for deduplication load balancing, the
fingerprinting process is shared between multiple media servers, and the fingerprinting
process is more efficient. The single copy of the deduplication database and indexes
that are created continue to reside on the storage server; using multiple media servers
does not result in multiple indexes.
Clicking Next will bring you to the a screen that displays a summary of the settings that
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
nbdevconfig –creatests
23
This screen displays the progress as the storage server is created. During this time, the
Next button is disabled. After the process completes, the Next button is enabled.
By default, there is a checkbox enabled stating Create a disk pool using the storage
server that you have created. By clicking Next you start the Disk Pool Configuration
Wizard.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
nbdevconfig –createdp
24
The next step in creating the media server deduplication pool is to create a disk pool. If
you run the Disk Pool Configuration Wizard separately from the Storage Server
Configuration Wizard, you need to select a disk pool type to create of PureDisk.
You may also use the nbdevconfig command to configure a new disk pool from the
command line, however Veritas does not recommend using the command line, and
instead recommends only using the wizard to ensure accuracy during configuration.
On this screen, Select the PureDisk disk volume to be included in the disk pool. There
should be only one disk volume per server, as was configured in the storage server
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
nbdevconfig –createdp
25
In the Additional Disk Pool Information screen, configure the properties of the disk
pool. Assign a name to the pool and optionally add comments about its function.
Configure additional disk pool information as follows:
• High water mark: The percentage of used capacity at which NetBackup considers a
disk volume in the pool to be full. A disk volume pool within a storage unit group is
assigned fewer backup jobs as it approaches the high water mark.
• Low water mark: For most disk types this is the percentage of used capacity at
which a clean-up operation stops purging backup images as a result of the disk pool
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
reaching the high water mark. This value is not used for deduplication pools.
• Maximum I/O Streams: Limits the number of streams that can be directed to a disk
simultaneously. It is used to avoid disk thrashing, which is the result of too many
jobs writing to the same disk simultaneously.
Any disk pool limit that you apply here will affect the total number of jobs that
associated storage units would be able to run.
Vertias recommends you place a limit here to prevent the server from being
overloaded with too many simultaneous backup jobs. A common limit to start with
is “20”. From there you can test higher values as you test the hardware’s capacity.
26
The Disk Pool Configuration Status will then show if the disk pool is configured
successfully.
By default the wizard will then go on to help you create a storage unit for that disk pool.
You can alternatively close the wizard without this checkbox, and create a storage unit
manually in the NetBackup Administration Console.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bpstuadd
27
Finally, configure the properties of the storage unit for this disk pool.
In most cases, you will want to increase the Maximum concurrent jobs setting from the
default setting of 1. Veritas recommends that you increase the Maximum concurrent
jobs value gradually. Doing so provides information about the total deduplication load.
The initial backup jobs (also known as initial seeding) require more CPU and memory
than successive jobs. After initial seeding, the storage server can process more jobs
concurrently. You can then gradually increase the jobs value over time.
Every environment's effective maximum concurrent jobs value is different. To find the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
best performance raise or lower this value until best performance is achieved.
A Media Server option is available to limit the storage unit to specific media servers.
After the storage unit configuration is complete, no additional configuration is required.
The storage unit created for the deduplication disk pool may now be selected as a
destination within a backup policy.
28
After a storage server has been configured, the NetBackup media server deduplication
processes are visible in the Running state, under the Activity Monitor Daemons tab. The
two processes that are displayed are the NetBackup deduplication manager (spad) and
the NetBackup deduplication engine (spoold). Prior to MSDP configuration, these
processes should not be found in the Running state.
For more information on the functions of these two processes, see the NetBackup
MSDP components section of this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
nbdevquery -liststs
29
After a storage server has been configured, it may be viewed in the NetBackup
Administration Console by expanding Media and Device Management > Credentials >
Storage Servers. Notice that the Administration Console does not list BasicDisk storage
servers because all media servers support BasicDisk by default.
Note that NetBackup appliances will also be listed as PureDisk storage servers in this
list, and will not look any different than media servers configured with a media server
deduplication pool.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
nbdevquery -listdp
30
To view disk pools using the NetBackup Administration Console, expand Media and
Device Management > Devices and select Disk Pools to list all configured disk pools.
The columns display the general configuration for the storage unit, in addition to a
percentage full value, showing the total used capacity of the disk pool.
Right-click the disk pool and select Change to modify disk pool settings, such as water
marks, and limiting the number of I/O streams.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bpstulist
31
After a PureDisk storage unit has been configured, it can be viewed in the NetBackup
Administration Console by expanding NetBackup Management > Storage and selecting
Storage Units. Notice that the master_msdp_stu storage unit is displayed with a
Storage Unit Type of Disk, and a Disk Type of either PureDisk or Disk Pool.
Right-click and select Change to modify storage unit settings, such as maximum
concurrent jobs.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to configure client-side deduplication.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
33
This slide provides an overview of the steps to configure client-side deduplication. You
have already learned how to configure the NetBackup client software and a
deduplication storage destination, such as MSDP.
To actually configure client-side deduplication, you only need to verify the client-side
deduplication requirements, and configure the option in the Client Attributes. You learn
how to perform each of these steps in this topic.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
CPU
NetBackup version
Operating system
34
Because fingerprinting is very process-intensive, the CPU on the client is affected by the
backup process. Veritas recommends performing tests to ensure that client applications
are not adversely impacted.
For supported operating systems, refer to Operating System Compatibility Lists, found
online at http://www.netbackup.com/compatibility.
•Always
Alwaysuseusethe
the mediaDisables client-side
server: Disables deduplication
client-side (default)
deduplication
media server
(default)
•Prefer
Prefertotouse
useclient- If deduplication
client-side deduplication:plug-in is active, use
If deduplication client-side.
plug-in is
side deduplication
active, use client-side. Otherwise,
Otherwise,useuse media
mediaserver
serverdeduplication.
deduplication.
•Always
Alwaysuseuseclient-
client-sideIfdeduplication:
deduplication Ifplug-in
deduplication
is active,plug-in is active,
use client-side.
usededuplication
side client-side. Otherwise, fail andfail
Otherwise, retry
andthe job.the job.
retry
35
To establish a client for client-side deduplication, set up the client in the Client
Attributes on the master server. Begin by adding the client to the list of clients that are
displayed in the dialog box. Next, under the General tab, configure the Deduplication
Location that is to be used:
• Always use the media server
This mode turns client-side deduplication off. Deduplication operations are
performed by the media server. This is the default behavior.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
36
In the NetBackup policy Attribute tab, there is a Disable client-side deduplication policy
attribute. By default, this attribute is disabled.
When you enable this attribute, all backups that are run by this policy use media server
deduplication, regardless of other deduplication settings.
This can be used in a situation where client-side deduplication is configured for some
clients, but should not be used in the case of certain backup policies by those same
clients.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to monitor the results of
deduplication in NetBackup.
After completing this topic, you will be able to monitor the results of deduplication in
NetBackup.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
38
The Deduplication Rate column under the Jobs tab in the Activity Monitor displays the
rate at which deduplication occurs for backups. This Deduplication Rate column is
displayed to the far right, by default, but can moved by rearranging the columns in the
Activity Monitor. This column displays the storage savings that are realized by using
deduplication.
In this example, a backup policy was used that has a storage destination which is a
deduplication pool (master_msdp_stu).
Job 43 was the first backup job for winmaster.example.com using this deduplication
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
destination. The deduplication rate is 59.4%. Although you may expect a very low
deduplication rate, often times even the initial data may have many duplicate blocks. In
this case we backed up a very large file that contained repeating data, and therefore the
deduplication rate was high for an initial backup.
Job 46 is a second occurrence of the backup performed in Job 43. This time, the
deduplication rate is 99.8% because the same data was written as was written in the
previous job and only a small amount of unique data was found.
Job 47 is the first time that winmedia.example.com was backed up to the deduplication
storage. Even though this is the first backup for this client, because it has almost
identical data to winmaster.example.com, the deduplication rate is very high, at 99.8%.
The results of deduplication are also displayed under the Detailed Status tab of the Job
Details dialog box for a deduplicated backup. The Detailed Status tab includes a line of
text that reflects the details of the backup to the deduplication storage server.
nbdevquery –listdp
41
Within the NetBackup Administration Console, under Media and Device Management,
there are two easy ways to report on deduplication disk pool capacity.
The first method involves looking at the disk pool properties. The command line method
uses the nbdevquery -listdp options. Reporting on the deduplication disk pool
in this manner provides a view of the disk pool capacity because it is cached by the
EMM server.
The second method involves looking at the storage server properties. The command line
method uses the nbdevquery -liststs options. With a deduplication disk pool,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
this method lists real-time data, pulled from the storage server when the command is
run.
It is important to understand that reporting and managing space in a deduplication disk
pool may not be as simple as on a non-deduplicating disk. After a single backup image in
a non-deduplicating disk pool expires, the space taken by the backup image is freed. In a
deduplicating disk pool, however, that space may not be so easily reclaimed.
43
Within the Administration Console, under NetBackup Management, capacity results are
also displayed in the Disk Pool Status report.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
44
As well as viewing disk pool capacity in OpsCenter, you can also view a variety of
deduplication reports. In Veritas NetBackup OpsCenter 8.1, the following deduplication
reports come with the product:
• Deduplication Rates by Master Server
• Deduplication Rates by Policy Type
• Deduplication Size Savings
• Deduplication Size Factor
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Compression
• Use these features in the deduplication client, not in the NetBackup policy
and • By default: Compression is enabled; Encryption is disabled
encryption
Virtual
machine Use the Enable file recovery from VM backup option for best deduplication rates
backups
45
On each NetBackup host that deduplicates data, a pd.conf file contains the various
configuration settings that control the operation of deduplication. The pd.conf file
resides in the following directories:
• UNIX: /usr/openv/lib/ost-plugins/
• Windows: install_path\NetBackup\bin\ost-plugins
Compression and Encryption
NetBackup provides compression and encryption as part of the deduplication process.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The options on the NetBackup policy for these features should not be used because
they can cause performance issues with deduplication backups.
By default, files are compressed as part of deduplication stream. To turn off
compression, add the value COMPRESSION = 0 to the pd.conf file.
By default, deduplication encryption is disabled. To turn on data encryption, add
ENCRYPTION = 0 to the pd.conf file.
The following is the behavior for the encryption that occurs during the deduplication
process:
• If you enable encryption on a client that deduplicates its own data, the client
encrypts the data before it sends it to the storage server. The data remains
encrypted on the storage.
• Data also is transferred from the client over a Secure Sockets Layer (SSL) to the
server regardless of whether or not the data is encrypted, so that the data is
protected, even if data encryption is not used.
before querying the storage server. A high cache hit rate indicates significantly reduced
network communication between the client and storage server, which is important
when using client direct to back up remote clients over high latency networks.
Pre-populating this cache can significantly reduce the data and fingerprint checking that
needs to be performed over the network. Several solutions exist, depending on the
NetBackup release level. For details and configuration options for other NetBackup
releases, see Article 100003816: NetBackup deduplication client WAN backup: how to
seed the fingerprint cache to speed up the initial backup, found online at:
http://www.veritas.com/docs/100003816.
• Key points
– In this lesson, you learned what NetBackup deduplication is and how it works.
– You are also learned how to configure a media server for deduplication, including creating a media
server deduplication disk pool, and configuring client-side deduplication.
– Finally, you learned how to monitor the results of deduplication.
• Reference materials
– NetBackup Deduplication Guide
– NetBackup compatibility at http://www.netbackup.com/compatibility
– Article 100003816: Seeding fingerprint cache to speed up the initial backup
– http://www.veritas.com/support
47
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
49
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Fingerprinting of data can be performed on the server side as well as the client side.
B. Deduplication can be performed at the disk block level.
C. Deduplication uses a capacity-based license.
D. Media server deduplication has only been available since NetBackup 7.5.
50
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Fingerprinting of data can be performed on the server side as well as the client side.
B. Deduplication can be performed at the disk block level.
C. Deduplication uses a capacity-based license.
D. Media server deduplication has only been available since NetBackup 7.5.
The correct answer is B. Deduplication can be performed at the file and sub-file (segment) level.
51
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
52
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
53
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. True
B. False
54
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. True
B. False
The correct answer is B (False). Because NetBackup media servers already contain the deduplication plug-in required to
assist in fingerprinting, any NetBackup media server can be a load balancing server.
55
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-56
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Configuring Tape Storage” lesson in the “Veritas NetBackup 8.1:
Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
Understanding Media Manager
Define media manager storage unit concepts.
storage units
Configuring tape devices Use the Device Configuration Wizard to configure new tape devices.
Verifying tape storage Monitor devices using the NetBackup Administration Console.
NetBackup media concepts Describe volumes, volume pools, and volume groups.
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to define media manager
storage unit concepts.
After completing this topic, you will be able to define media manager storage unit
concepts.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
NetBackup refers to tape devices as Media Manager devices, because they are managed
by a component of NetBackup known as Media Manager.
Robotic or standalone
NetBackup interacts differently with robotically controlled devices and stand alone
devices. Stand alone devices require an operator or human assistance when the tape
media is loaded to and unloaded from the device. Robotic controlled devices are
generally automated, and load and unload tape media without the aid of an operator,
normally from tape slots in the library.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
In both scenarios, NetBackup needs to know the device path, which describes how the
media server sees the device. These device paths are operating system-specific. In the
case of a robotically-controlled tape library, NetBackup also requires the device path to
the library’s robot, to be able to control that robot.
Device and media compatibility
Besides being robotically controlled or stand alone, media manager devices have
another characteristic. The read/write or I/O device (the tape drive) is actually
separated from the recording media (the tapes).
Not all tapes are compatible with all tape drives. If an incompatible tape gets loaded
into a tape drive, then I/O errors can occur. NetBackup needs to be able to match
appropriate media type for the media (tapes) and devices (tape drives).
NetBackup needs to be told about the tape drives that can be used by media servers for
backup and restore operations.
From earlier modules we have seen that NetBackup’s primary backup destination is the
storage unit and that a storage unit refers to one or more physical devices with common
attributes. For backups going to tape, we need to have media manager storage units
which refer to the tape drives connected to a media server that NetBackup is aware of.
We have also been introduced to the Storage Unit Group which is a named list of
storage units. NetBackup can target either a storage unit or a storage unit group as a
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
backup destination. When a storage unit group is the target, only one of the storage
units defined in the group will be chosen as the target.
Not only does this slide review the differences between devices, storage units and
storage unit groups, it also introduces some of the media manager specific attributes
that media manager devices must have in order to be referenced by the same media
manager storage unit. If two media manager storage devices have differences in these
attributes, then multiple storage units will be required. But, those storage units could
be members of the same storage unit group. And, media manager storage units can
exist with non-media manager storage units within the same storage unit group.
With robotically controlled tape drives, each tape drive and the robot control device
appear as separate devices to a NetBackup server. A tape library with four tape drives
properly connected to NetBackup server should show five devices in the NetBackup
server: four tape drives and a robotic device. A robot is also sometimes referred to as a
medium changer on Windows hosts.
A NetBackup server uses the tape drive interface to perform operation such as
positioning the tape to a tape file, reading data from the tape, or writing data to the
tape.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The robot control interface/device is used to perform operations such as moving tapes
from library slots into drives or moving tapes from drives back into their slots.
For libraries that are dedicated to a single NetBackup media server, that NetBackup
media server will be considered the robot control host, and completely control the robot
through the appropriate interfaces. The robot control host is designated in the
NetBackup configuration and is the NetBackup server that is responsible for directly
interfacing with the robot control interface, and moves the tapes from library slots to
drives, and back again.
A robotic tape library and it’s drives do not have to be dedicated to a single NetBackup
server, especially in a storage area network (SAN). A tape library that is configured to be
accessed by multiple servers is sometimes called a shared library. In these cases all the
tape drives may be seen by all servers, or there may be some tape drives that are
dedicated to specific servers.
Robot control interfaces, due to a limitation of the hardware, do not respond properly
when multiple servers attempt to access them simultaneously. A single NetBackup
server must be defined as the robot control host: the server responsible for directly
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
interfacing with the robot control interface. Any other server that wishes to move tapes
between slots and drives within the library does so by making a request, over TCP/IP, to
the robot control host., which then issues commands to control the tape robot. Data
movement operations, such as tape positioning, reading data from a tape in a drive, or
writing data to a tape in a drive, is performed directly by each NetBackup server that is
directly accessing the tape device.
It should be noted that in some cases the robot control host is not a NetBackup server.
An example would be Automated Cartridge System (ACS) libraries, where the library is
controlled by ASCLS software that runs on another host. For ACS libraries, NetBackup
servers interact with the ACSLS host to perform robotic control.
Do not confuse a shared library with the NetBackup-licensed Shared Storage Option
(SSO), which allows multiple NetBackup servers to access the same tape drives.
NetBackup NDMP
server host
Tape
library
Tape Stand-alone
library tape drives
10
ms1_tape_stu ms2_tape_stu
Drives 1-3 Drives 4-6
Media Media
server 1 server 2
LAN
NetBackup
clients
11
Media manager storage units can also control what media server is used. If the device
configuration wizard is used, after devices are discovered, associated storage units are
created. One storage unit per robot per drive type per media server is created.
In the example on this slide, the tape library has 6 tape drives, all of type LTO4. Three of
the tape drives are visible to media server 1 and the other three are visible to media
server 2. The device configuration wizard creates two storage units. The first, STU-A,
refers to the three LTO4 drives in the robot known to Media Server 1, while the other
storage unit, STU-B, refers to the other LTO4 tape drives known to Media Server 2.
On Drive Selection from a media manager storage unit: At the time that a backup job
needs a drive, if the storage unit refers to multiple available, idle tape drives, NetBackup
uses a LRU/round robin mechanism to determine which drive it should assign to that
job.
tapelib1_stu
LAN
NetBackup
clients
12
Storage units can be manually created as well. A single storage unit could have been
created that refers to the three tape drives known to Media server 1 and to the other
three tape drives known to Media server 2, since all six tape drives use the same type of
media and are under the control of the same robotic library. This storage unit would not
have a specific media server configured in the storage unit, but instead be configured in
the storage unit to use Any Available media server. Note that that the storage unit is
still restricted to a single tape robot, drive density, and so forth, so only all media
servers related to those properties will be used.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Media manager storage units designating Any Available media server allow NetBackup
to choose which media server and drives would be used. However, in our example, each
specific tape drive is still assigned to only one media server. If one media server is shut
down, only half the tape drives would be available for use.
ms1_tape_stu ms2_tape_stu
Drives 1-6 Drives 1-6
Media Media
server 1 server 2
LAN
NetBackup
clients
13
The shared storage option, a license extension, allows NetBackup to share tape drives
between two or more media servers instead of having the drives dedicated to a specific
media server. Each shared tape drive can be registered with more than one media
server that can physically see the drive. When such a drive is being used by one media
server, for example to run a backup or restore job, that tape drive is not available to the
other media servers. But once the job on that media server is finished, the tape drive
can be used by other media servers for other jobs.
This diagram shows a NetBackup configuration where all 6 drives are known to both
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
media servers. We are also showing two storage units. Use of STU-A would cause a job
to use Media Server 1 and any of the 6 tape drives while use of STU-B would case a job
to use Media Server 2 and any of the same 6 tapes drives. Regardless of the storage
units used, the drives would be one of the same 6 available to both media servers.
If one of the media servers was shut down, the other media servers would still be able
to use any of the shared tape drives.
Like with non-shared storage, we can also created a storage unit that allows NetBackup
to use any available media server.
After completing this topic, you will be able to use the Device Configuration
Wizard to configure new tape devices.
14
After completing this topic, you will be able to use the Device Configuration Wizard to
configure new tape devices.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2 Install drivers /
device files
3 Confirm devices
available in O/S
4 Verify with
NetBackup utilities
15
Complete the following tasks before you configure devices with NetBackup:
1. Ensure that devices are correctly, physically attached to the system.
2. Ensure that the appropriate drivers are installed within the server operating system.
On UNIX, use a SCSI pass-through driver. This is a SCSI driver that passes through
non-drive-specific SCSI commands instead of blocking them. This pass-through is
required in order to handle the robot control commands. Some operating systems
don’t have a SCSI pass through driver, and require NetBackup to install these drivers.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3. If the operating system does not see the devices, neither will NetBackup. Confirm
that the devices are available through operating system tools, such as:
• HP-UX: ioscan
• AIX: lsdev
• Linux: cat /proc/scsi/scsi, lsscsi
• Windows: Device Manager (devmgmt.msc)
4. After NetBackup is installed, use the scan, tpautoconf –t, and tpautoconf –r
NetBackup utilities to verify the operating system devices. NetBackup on Solaris will
additionally have the sgscan utility.
5. At this point, if you do not see the devices, troubleshoot the problem using standard
operating system tools or vendor specific utilities until you can see the devices. For
example, check your SAN zoning or persistent binding configuration.
17
Veritas recommends that you use the Device Configuration Wizard to configure robots
and tape drives. The wizard configures a robot, its drives, and a storage unit. This wizard
discovers the robots and tape drives that are available, and is the preferred method of
device configuration. For the robot types that support device serialization, the wizard
discovers the positions of the drives within the library.
The wizard also provides the ability to customize drive naming rules, robot and drive
properties, SAN clients, and storage units.
The wizard works by querying available device paths on each media server for devices
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
and for each discovered device (drives and robots), collects information about those
devices, such as serial numbers, type of device, and so on. Device serial numbers are
used to find out which tape drives are controlled by which robots (tape libraries) and
are visible to which media server and if a drive is shared between two or more media
servers. The use of the device serial numbers to correlate drives, robotic libraries and
media servers is called device serialization. The wizard then updates the NetBackup
database with the collected information and assigns device names, robot control hosts
and NetBackup device types for the discovered devices.
Using the device configuration wizard is the preferred method for device configuration.
Devices can be manually configured as well, however the user would be required to
collect the same information and manually update the NetBackup database with the
information. Refer to the Veritas NetBackup Device Configuration Guide for details.
After completing this topic, you will be able to monitor devices using the
NetBackup Administration Console.
18
After completing this topic, you will be able to monitor devices using the NetBackup
Administration Console.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
tpconfig -d
19
After the Device Configuration Wizard runs, you can view the properties of the drives
that were configured. To do this:
1. Expand Media and Device Management > Devices and select Drives.
2. In the details pane, select the drive you want to view, and press Enter. You can also
right-click and select Change.
You can also use the command, tpconfig –d on each NetBackup server to report on
what devices have been registered to that server in NetBackup’s enterprise media
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
manager.
tpconfig -d
20
There needs to a robotic entry for each media server that needs to communicate with a
library. These can be added manually but as we can see, the Device Configuration
wizard adds the required entries as part of its processing.
After the Device Configuration Wizard runs, you can view the properties of the robots
that were configured. To do this:
1. Expand Media and Device Management > Devices and select Robots.
2. In the details pane, select the robot you want to view, and press Enter. You can also
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
lnxmaster lnxmedia
Robot
Robot control
host
21
This example shows entries for a robot that is ‘shared’ between two media servers.
Unlike tape drives which can be directly accessed by multiple NetBackup media servers,
the robotic control interface can not, a robot control host must exist. Every media
server that needs access to a robot including the robot control host, will have an entry
in the enterprise media manager for that robot but only one of those entries will be for
the robot control host. The other entries will indicate that that particular media server
must contact the robot through the control host.
In the example above, there are two entries for the robot known as TLD(0). The entry
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
for winmaster.example.com shows this it is the robot control host (chosen by the device
configuration wizard). The other entry is for winmedia.example.com and was created
by the wizard because winmedia.example.com sees a tape drive that is controlled by
the robot, TLD(0) so needs to communicate with winmaster.example.com as the robots
robotic control host. In our environment, both winmaster and winmedia can be robot
control hosts but the wizard chose winmaster because it scanned winmaster first.
Again, the output from tpconfig –d can show robot entries based on the server it is
executed on. For a robot control host, it will show the path to the robotic control
interface. If executed from a NetBackup server that is registered with the robot in
NetBackup, but that is not the robot control host, the output identifies what host is the
robot control host.
vmoprcmd
22
You can use the Device Monitor to determine a drive’s properties and characteristics,
such as its name, host (the media server to which it sends its backup data), and type
(such as DLT). You can also control drives using the Actions menu or by right-clicking a
drive and selecting an action from the drop-down menu. Such actions include activating
a downed drive, resetting a drive, manually invoking drive cleaning, and changing the
comments associated with a drive. To display details about a particular drive, from the
Device Monitor, right-click a drive and select Drive Details from the drop-down menu.
The control column shows the state of the drive:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• TLX/SCAN-TLX (where X depends on robot type) indicates the drive under robotic
control and available for use.
• DOWN-TLX indicates the drive is under robot control is not available for use.
• AVR/SCAN indicates the drive is not under robotic control or robot control daemon is
not running but the drive is available.
• DOWN indicates the drive is not under robotic control or the robot control daemon is
not running and the drive is not available.
The vmoprcmd command enables you to perform operator functions on drives. For
example, to bring a drive up from the command line, enter:
vmoprcmd -up drive_index [-h device_host]
bpstulist
23
The value of Media Server shows that winmaster.example.com will be the media server
used. Clicking on the Media server dropdown field displays a list of all the media
servers configured to have access to HCART tape drives within the TLD(0) library.
The media server value of Any Available configures the storage unit to use any of the
media servers that see this type of drive within the specified library. If, at a later time, a
new media server is configured for these drives in this library, it will automatically be
used with this storage unit.
A similar result can be obtained by creating individual storage units for each library, per
drive type, and per media server, and then adding those storage units to a storage unit
group. However, if a new media server is given access to the library, a new storage unit
would need to be created and it would have to be manually added to the storage unit
group.
List configured tape Media and Device tpconfig –d Monitor > Devices
drives and robots Management > Manage > Devices >
Devices Robot | Drives
Monitor the state and Media and Device vmoprcmd Monitor > Devices
availability of tape drives Management > Device Manage > Devices >
Monitor Drives
List devices that would scan
be found and configured tpautoconf –t
by the device
configuration wizard if it tpautoconf –r
were to be run.
24
This slide shows some of the ways you can query NetBackup about your device
configuration.
tpconfig –d queries the Enterprise media manager for devices that have been registered
with the media server the command is run from. You run this command from a
NetBackup server. It can also be used to manually register a device with a NetBackup
server.
vmoprcmd queries all of the ltid processes to report the status of drives on all
NetBackup servers in a domain. It can also be used to manage the state of drives
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
(up/down).
scan/tpautoconf –t/tpautoconf –r are commands that scan a hosts device endpoints
and report the devices that are present. Devices reported by these commands will be
picked up by the device configuration wizard and configured into the enterprise media
manager.
After completing this topic, you will be able to describe volumes, volume
pools, and volume groups.
25
After completing this topic, you will be able to describe volumes, volume pools, and
volume groups.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
26
Media Manager volumes are tapes that have been assigned media IDs and other
attributes, which are recorded in NetBackup database.
You should know the following about volumes:
• A piece of media becomes a volume when Media Manager assigns a media ID (also
known as the Recorded Volume Serial Number or RVSN).
• NetBackup requests volumes from Media Manager using the media ID.
• NetBackup writes a label to the media that contains the media ID.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• If a tape cartridge has a recognized external barcode, this is also recorded in the
NetBackup database, and used to generate the media ID for a new tape. The
barcode is sometimes referred to as the EVSN or External Volume Serial Number.
Note: The media ID is limited to six characters, and NetBackup only reads thirteen
characters on a bar code label.
To control how media IDs are generated from barcode values, define media ID
generation rules that specify which characters of a bar code on a cartridge are to be
used to generate a media ID. Multiple media ID generation entries can be specified,
allowing media ID generation to be specific for each robot and length of barcode, and
offering flexibility for multimedia.
NetBackup assigns each volume a unique media ID. This media ID may be assigned
manually, or it may be automatically generated using bar codes and a process known as
robotic inventory. Considering the large number of tapes in an enterprise backup
environment, most environments use bar codes and robotic inventory. Manually
assigning media IDs is only performed in special circumstances.
The maximum length of a media ID is six characters and is typically based on the bar
code. If the bar code is longer than six characters, by default NetBackup uses the last six
characters as the media ID, as shown in the slide on this page. Customizing this behavior
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
NetBackup organizes volumes in volume pool. The volume pool used by a backup job is
specified as part of the backup policy definition.
The following volume pools exist, by default:
• NetBackup: The default volume pool used by most policies initially and the pool new
tapes discovered by robotic inventory are assigned to by default.
• DataStore: The default volume pool for some integrated third-party applications.
• CatalogBackup: The default volume pool for storing NetBackup catalog backups.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• None: The volume pool used for tapes NetBackup should not write to, such as
cleaning tapes and non-NetBackup tapes.
In addition to these predefined pools, you can create your own pools to segregate
backups to different tapes, such as for backup images staying onsite and images being
sent offsite, or for backups of different types of applications.
The scratch pool is an optional volume pool that you can configure to store unused, free
tapes.
29
The scratch pool is an optional volume pool that you can configure. You can have only
one scratch volume pool per NetBackup domain. Any media manager storage unit can
have volumes that are in the scratch pool. If the scratch pool is configured, NetBackup
moves volumes from that pool to other pools that do not have volumes available, when
required. The name of the scratch pool does not matter. However Veritas recommends
creating a pool with a defining name, such as Scratch or free_tapes.
NetBackup does not assign volumes while they are in a scratch pool, and the scratch
pool cannot be targeted by a backup policy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A volume moved from the scratch pool to another volume pool due to backup needs,
remains in the other pool until it is unassigned (all image reach their retention).
NetBackup moves volumes back to the scratch volume pool after the volume is
unassigned. To disable this feature, update the NetBackup database using the following
command:
nbemmcmd -changesetting
-return_unassigned_media_to_scratch_pool no
-machinename master_server
TLD0
Eject Vault
Volume Group:
---
Volume Group:
Volume Group:
OFFSITE
000_00000_TLD
30
A volume group is a logical group of volumes that are located at the same physical
location. This allows NetBackup to track media by location.
Each robotic library can have one or more pre-defined volume groups with a name
based upon the robot number, robot type, and media type. For example, the first library
defined might have the library name “TLD0”, which would have the volume group
000_00000_TLD.
If a volume is in a the 000_00000_TLD volume group, it is considered to be resident in
the TLD0 library. If another tape is in the same library but of a different media type (in
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
other words, in a different media manager storage unit) then that tape will be assigned
to another volume group such as 001_00000_TLD.
These volumes are resident in the robot, so the robot can automatically load the
volume for backup and restore operations. When robotic inventory is run and
NetBackup identifies volumes moved into the library, by default, NetBackup will assign
each volume to an appropriate robotic volume group based on the robot the tape was
found in and the media type of the tape.
The following are the rules for assigning volume groups:
• A volume can be assigned to only one volume group.
• All volumes in a group must be the same media type. However, a media type and its
corresponding cleaning media type are allowed in the same volume group (such as
DLT and DLT_CLN).
Volume groups allow you to group media by its location. Volume pools are used when
you want or need different backups to be placed onto different sets of tapes. The
reason for separating backups are dependent on your needs and problems you need to
overcome. For example, enabling parallel restore of two extremely critical systems by
making sure the backups of those two systems don’t go to the same tape. Another
example is having a local set of backups kept onsite but also having copies of those
same backups stored at an offsite location for long term retention.
However, one needs to be judicious here. The more volume pools you create, the more
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to use the Robot Inventory to
configure new media.
33
After completing this topic, you will be able to configure media using Robot Inventory
and configure barcode and media ID generation rules.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Command Line
• Provided by Media Manager commands.
• Use vmadd, vmupdate, and vmchange commands.
34
Volume Pools
• Create scratch pool
• Create other volume pools
• Perform before running inventory
Barcode Rules
• Assigns density, volume pool, and other properties
ABC* according to barcode
Media type: HCART3 • Create before or during inventory
Volume Pool: dups
Media ID
Generation Rules • Assigns Media ID according to barcode
ABC123L4 • Create before or during inventory
Media ID: ABC123
35
Using robot inventory enables accurate tracking of volumes within robotic libraries,
including determining which volumes are in a robot and their exact slot location.
The steps on this slide describes tasks that need to be performed either before or
during the robotic inventory. These tasks include creating all custom volume pools, bar
code rules, and media ID generation rules that may be needed. Newly configured rules
are not applied to media that already exists in NetBackup. For any media that was
added before the rules were created, either manually update the media or delete the
media and re-run the robot inventory. At that point, the rules will be applied.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A bar code rule specifies criteria for assigning attributes to new robotic volumes.
NetBackup assigns these attributes by using the bar code for the volumes cartridge that
the robotic library provides along with your bar code rules. After bar code rules are
established, NetBackup automatically assigns media, based on the bar code tag, to a
specific volume pool and media type.
Media ID generation rules enable you to override the default media ID naming method
that NetBackup uses for new tapes that have barcodes. The default method uses the
last (rightmost) six characters of the bar code provided by the robot to generate the
media ID. Use the rule to control how NetBackup creates media IDs by specifying which
characters of a bar code are used in the media ID. In addition, you can specify that
alphanumeric characters are to be inserted into the ID. Multiple rules can be used to
accommodate different robots and bar code lengths.
vmpool
36
Pool name: A unique volume pool name; Up to 20 alphanumeric characters long and
is case-sensitive.
• Description: A brief description of the volume pool.
• Maximum number of partially full media: The number of partially full media (for
each retention level) that NetBackup will allow backup to concurrently write to in
the pool. The default number (0) places no limit on partially full media in the pool.
• Scratch Pool: Allows the pool to be used as a scratch pool. After defining the scratch
pool, add empty volumes to the pool. Only one pool can have this attribute.
• Catalog backup pool: A dedicated pool used for backups of the NetBackup catalog,
to be used for NBU-Catalog policies. Multiple catalog backup pools are allowed.
vmupdate
37
To start a robot inventory, use the NetBackup Administration Console to invoke the
Inventory Robot function:
1. In the left pane, select Media and Device Management > Media > Robots.
2. Select the robotic library desired. If there are multiple entries for the same robot,
choose the entry for host that is the robotic control host.
3. Right-click the robot and select Inventory Robot, or select Actions > Inventory
Robot.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
If you are planning on discovering and adding tapes in a library media or cartridge
access port (MAP or CAP), insert one or more volumes into the robotic library prior to
running the robot inventory, and ensure there are available slots in the library.
Robot
control
host
38
When the Robot Inventory dialog is shown, it allows for various inventory operations to
be performed. Each operation communicates with the robot control host. You need to
make sure that the Device Host field shows the name of the robot control host for the
robot you wish to inventory. If you selected the wrong entry from the Robots list in the
Object tree, this gives you a chance to change the value.
Selecting the Show contents radio button and clicking Start runs the Show Contents
inventory operation. This function initiates the most basic NetBackup inventory
operation requesting the robotic library for a list of its slot contents. This function
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
simply displays the response from the robotic Library. Most modern robotic libraries
cache this information so the operation is relatively fast. However, some older robotic
libraries will physically pole each slot at the time of the request so it could take longer.
The Show Contents inventory operation is useful for determining the contents of a
robot as follows:
• If the robot has a bar code reader and contains media with bar codes, the report
displays whether each slot has media and lists the bar code for the media.
• If the robot does not have a bar code reader or does not contain media with bar
codes, the report displays whether each slot has media.
• If the robot is an API robot (like an ACS robot), the report displays a list of media
found in the robot.
39
The Compare Contents with volume configuration function is similar to the Show
Contents operation but takes the operation a step further. Instead of simply displaying
the response of the robotic library, it compares the response with the contents as is
stored in the NetBackup.
The comparison is displayed in the Results field and shows discrepancies between what
the robot reported and what the NetBackup configuration thinks should be in the
library. Each discrepancy is indicated by a value of yes in the Mismatch Detected
column of the output. This output includes the Media ID value since this operation
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
accesses not only the library but also the information in the NetBackup database.
40
The Preview volume configuration changes inventory function, like Show Contents,
requests a slot inventory from the robotic library, and like Compare contents with
volume configuration, compares the response from the robot with what is registered in
NetBackup.
However, instead of displaying the results or the discrepancies, based on the
discrepancies found, this function derives a set of operations, that if applied to
NetBackup, would update the database to reflect what is currently in the robot and
displays the proposed changes. Note that no changes are actually performed. This
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
operation simply displays what would be done if the operations were executed.
Also take note that with this inventory operation selected, the Advanced Options
button is now available. This allows you to see some of the effect using advanced
options would have on the database like the effect media id generation rules would
have on the value of the generated Media ID for new media discovered without actually
making the changes to the database.
41
The Advanced Robot Inventory Options dialog has various tabs. The Media Settings tab
is separated into two sections: the Existing media frame and the New media frame.
The Existing media frame allows you to specify volume groups for media already known
to NetBackup for the purposes of tracking the location of the media. As stated
previously, a volume group identifies the physical location where media should be
found.
• The Media which have been removed from the robot should be assigned to the
volume group field is used to set the volume group when a tape is later found to be
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
missing during a robot inventory. By default the volume group for a tape will be set
to --- (3 dashes), which does little to inform the NetBackup administrator as to
where the tape is physically found. By setting a value, tapes from the library that are
not found (normally those that have been ejected) will be placed in that volume
group. Even though this field looks like a drop-down box, it is also an entry field; By
typing a new value, a volume group gets created when the first volume is placed
there. The volumes in any group mentioned in this field must all be of the same type
and, based on the inventory, not in any robot.
• The selection list always has the following choices:
• DEFAULT: Allow Media Manager to select the volume group – generally clears
the volume group label.
vmrule
43
A bar code rule specifies criteria for assigning attributes to new volumes discovered by
robotic inventory. The attributes are assigned based on what barcode tag matches the
barcode label of a given volume.
• The Barcode tag is a string used to match the left-most portion of the barcode label.
If the barcode label matches multiple tags then the rule whose tag matches the
largest portion of the barcode label is used. There are two special barcode tag
designations: NONE which matches any cartridge where a barcode label could not
be read and DEFAULT which is used if none of the other barcode tags match the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
barcode label. The DEFAULT barcode tag is often used to change NetBackup default
behavior of placing new volumes into the NetBackup volume pool. Without this
barcode tag, any new volume not matching any barcode tags will be assigned to the
NetBackup volume pool and be given a media type based on the drive types within
the robot. Note: The actual text of the BARCODE tag input are the letters DEFAULT
but that NetBackup displays this RULE’s tag as <DEFAULT>. The NONE barcode tag
works the same.
• Maximum Cleanings/Maximum Mounts is used by NetBackup as a usage limit so
tapes and cleaning cartridges do not get overused. A value of zero indicates that no
limit exists. This field allows an initial value to be specified for new tapes discovered
through robotic inventory. These limits can be changed after the tape is made
known to NetBackup at any time. Tapes whose labels do not match any of the tags
or tapes that were inventoried with barcode rules enabled get zero as the default.
45
Every volume used by NetBackup needs to have a unique, six character media id. For
robotic libraries with barcode reading abilities, the value of the barcode label read by
the robot’s barcode reader can be used to derive the media id for newly discovered
media.
By default, NetBackup uses the right-most 6 characters of the barcode label as the
media id that is assigned to the new tape. This can cause problems for two or more
tapes with barcode labels longer than six characters, if the resulting media ids would
not be unique. If two tapes each had the barcode label values S00006L1 and D00006L1,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
NetBackup would try to assign both tapes the same media id 0006L1, and the inventory
process would produce errors.
Media ID generation rules allow you to specify what characters of the barcode are used
to generate the media ID.
To create a new media ID generation rule, click the Media ID Generation tab and click
the New button, and then specify the properties as follows:
• Robot number: The number associated with a robot. TLD(0), for example is robot
number 0.
• Bar code length: The length of barcode this rule applies to. Barcodes of lengths
other than this value will not use this rule.
Some examples of media ID generation rules are given in the table on the slide.
47
Like Preview volume changes, this operation allows access to the Advanced Options
properties.
vmquery –a -b
nbemmcmd –listmedia –allrecords -brief
48
Select Media and Device Management > Media to display all media in your
environment. Notice the Volume Pool and Volume Group columns.
To display volumes, including the volume pools and volume groups to which they
belong, use the following commands:
vmquery -a -b
nbemmcmd -listmedia -allrecords -brief
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
49
If you are adding volumes to a robotic tape library, you can have NetBackup inventory
the robot and use the information to update the volume catalog.
The table on this slide presents an overview of the process of adding volumes using the
inventory update function.
There is no command line interface for creating media id generation rules.
Note: The first three rows in the table on this slide do not modify the volume database.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Key points
– In this lesson, you learned about the Device Configuration Wizard.
– You also learned how to define media manager storage units, and to use the Volume Configuration
Wizard and Robot Inventory to configure new media.
– Finally, you also learned how to monitor devices and media using the NetBackup Administration
Console.
• Reference materials
– NetBackup Device Configuration Guide
– NetBackup Administrator’s Guide
– NetBackup for NDMP Administrator’s Guide
– NetBackup Shared Storage Guide
– NetBackup Commands Reference Guide
– http://www.veritas.com/support
50
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
52
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
53
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
54
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
55
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
56
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. NetBackup
B. DataStore
C. None
D. Scratch
57
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. NetBackup
B. DataStore
C. None
D. Scratch
58
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-59
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Managing and Optimizing Tape Storage” lesson in the “Veritas NetBackup
8.1: Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
View and change robot and tape drive settings, including drive
Managing robots and tape drives status, and perform drive cleaning and running robot and drive
diagnostics.
Identify and monitor NetBackup media states, and understand
Monitoring media and media states
NetBackup media selection and lifecycle.
Perform media management, including moving, ejecting, changing,
Managing tapes
sharing, erasing, and deleting volumes.
Media- and device-related tips Identify tape device and media reports.
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to view and change robot and
tape drive settings, including drive status, and perform drive cleaning.
After completing this topic, you will be able view and change robot and tape drive
settings, including drive status, and perform drive cleaning.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Path properties
General drive
properties
tpconfig -d
5
drive manually or through the device discovery wizard, you can use drive name
rules.
• Host and path information defines the hosts and that host’s specific device path to
this tape drive. If the drive is shared, there will be one entry for every media server
accessing this drive.
• Drive Information allows you to specify the following information:
• The Drive type specifies the type of drive you are adding.
• Use the Cleaning Frequency (In hours) property to set the desired number of
mount hours between drive cleanings, for drives that do not support TapeAlert.
• Drive is in a robotic library specifies whether the drive is in a robotic library.
• The Robotic library specifies a robot that controls the drive.
stopltid UNIX
ltid
After you configure a robot or drive, you are prompted to stop and restart the device
daemons or services. If you choose to do this later, you can stop and restart the
daemons or services using the Media and Device Management interface.
1. Select Actions > Stop/Restart Media Manager Device Daemon.
2. Complete the dialog box as follows:
a. Select a device host. The status of the selected daemon or service is shown
under Current Status.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
b. In the Action pane, you can start, stop, or stop/restart the service. Select the
action you want to perform.
c. The Options pane enables you to eject media from a stand-alone drive and
control the level of debug logging. Select the options you want to perform.
3. Click OK or Apply.
You can also use the stopltid and ltid commands to manage the Media Manager
daemons or services. The stopltid command stops ltid, avrd, and the robotic
services; ltid starts ltid, avrd, and the robotic services.
On Windows you can also stop and start the Media Manager services using Windows
Computer Management, by restarting the NetBackup Device Manager service.
The robtest utility allows you to control a robot using the robot’s control interface,
on the robot control host. It lets the user issue low level robotic control commands to
control the robotic arm, change access to mail slots, transport media between locations
in the robot (slots, drives, mail ports) and query information about the robot just like
NetBackup does. You can use robtest, for example, to see if the robot is receiving or
executing robot control commands, view contents of slots, drives, and mail ports, find
out how many drives, slots and mail slots are available, if there is a barcode reader, and
so on.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The robtest program searches the NetBackup database and presents a menu of
available robots physically controlled by a host. You must run robtest on the media
server that is the robot control host, by running the following command:
• UNIX: /usr/openv/volmgr/bin/robtest
• Windows: install_path\Veritas\Volmgr\bin\robtest.exe
When you select a robot, robtest invokes the device-specific test tool (such as
tldtest for a TLD type robot). From each test utility, you can obtain a list of available
test commands by entering a question mark (?).
init
Initiating INITIALIZE_ELEMENT_STATUS
INITIALIZE_ELEMENT_STATUS complete
mode
First transport addr = 1, Number transport elements = 1
First storage addr = 4096, Number storage elements = 15
First media access port addr = 16, Number media access port
elements = 5
First drive addr = 256, Number drive elements = 2
Library does have a barcode reader
MODE_SENSE complete
Warning: The init command reinitializes the library and may take a long time to run.
Caution: Do not leave robtest running in your production environment. Doing so can
lead to device errors and prevent any access to the library for backups, restores, and
inventory. While robtest is running, NetBackup cannot communicate with the device
control host to control the robot for backup jobs.
Caution: If you use robtest to load a tape into a drive, you need to remove the tape
using robtest. NetBackup does not autoeject a tape that has been loaded by any
other utility.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
m s4 d1
Initiating MOVE_MEDIUM from address 4099 to 256
MOVE_MEDIUM complete
s s
slot 1 (addr 4096) contains Cartridge = yes
Source address = 256
Barcode = 090000L1
slot 2 (addr 4097) contains Cartridge = yes
Barcode = 090001L1
slot 3 (addr 4098) contains Cartridge = yes
Barcode = 090002L1
slot 4 (addr 4099) contains Cartridge = no
slot 5 (addr 4100) contains Cartridge = yes
Barcode = 090004L1
slot 6 (addr 4101) contains Cartridge = yes
Barcode = 090005L1
slot 7 (addr 4102) contains Cartridge = yes
Barcode = 090006L1
slot 8 (addr 4103) contains Cartridge = yes
Barcode = 090007L1
slot 9 (addr 4104) contains Cartridge = yes
Barcode = 090008L1
slot 10 (addr 4105) contains Cartridge = yes
Barcode = 090009L1
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
vmoprcmd
11
You can use the Device Monitor to determine a drive’s properties and characteristics,
such as its name, host (the media server to which it sends its backup data), and type
(such as DLT). You can also control drives using the Actions menu or by right-clicking a
drive and selecting an action from the drop-down menu. Such actions include activating
a downed drive, resetting a drive, manually invoking drive cleaning, and changing the
comments associated with a drive. You can also use the Device Monitor to determine
robot types and numbers.
To change a drive path operating mode:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Windows
UNIX
12
The Drive Details screen lets you examine the all of the details of a specific drive in one
screen. This information is available in the Device Monitor but is not available in a
single screen. A user would need to use the scroll bar or rearrange columns in the
details pain to see all the available information. The Drive Details screen displays all
this information on a single screen.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
13
Media Manager drive and robot diagnostic functions enable you to execute and manage
drive and robot diagnostic tests. The diagnostic test steps are executed in an ordered
sequence to verify the functionality of hardware devices configured for use with
NetBackup. These tests help you to troubleshoot robotic library or tape drive problems.
Before running drive diagnostics, use the available_media script to confirm that
there is an Available tape in the NetBackup volume pool.
To execute diagnostic tests within the NetBackup Administration Console:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1. Select Media and Device Management > Devices > Drives or select Media and
Device Management > Devices > Robots.
2. Select a device or a robot.
3. Select Actions > Drive Diagnostics or Actions > Robot Diagnostics.
In either the Drive Diagnostics or Robot Diagnostics dialog box, click Start to run the
drive or robot diagnostic tests. The results of the tests are displayed in the Results pane.
Note that drive diagnostics will perform I/O to an available tape (a tape without data
already on it) in the NetBackup volume pool.
Robot diagnostics will not perform any I/O, however will move tapes from slots to
drives, and back.
14
Routine maintenance of devices includes cleaning drives to ensure that they continue to
write to and read from the media properly. Although cleaning is important, be careful to
neither overclean nor underclean your drives. Undercleaning can result in excess
residue on the tape drive heads. Overcleaning can cause undue wear on the drive
heads. Either can result in data loss.
Refer to the drive manufacturer’s recommended cleaning schedule. You can establish a
cleaning schedule through NetBackup accordingly.
Using a cleaning tape
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Drive cleaning is accomplished using cleaning tapes. Media Manager tracks the usage of
a cleaning tape by the number of times it has been used. For each cleaning tape, you
can specify the number of cleanings that remain. You can change the number of
cleanings at any time in Media Manager. Each time the tape is used, that number
decreases by one. When the number of cleanings reaches zero, Media Manager stops
using the cleaning tape.
To configure a cleaning tape:
1. Specify the Media type setting for the cleaning tape’s designation (such as
DLT_cleaning_tape).
Note: The cleaning tape is automatically assigned to the None volume pool.
2. Set the number of cleanings. (The default setting is 25.)
TapeAlert
TapeAlert notifies Media Manager that the drive needs to be cleaned.
Frequency-based
The drive is cleaned according to an administrator-defined frequency.
Manual (operator-initiated)
• Manually invoked in the Device Monitor or with tpclean.
• Use robotic device controls directly.
15
This slide shows the various methods you can use to perform drive cleaning.
• Robotic controlled cleaning: Some robotic tape libraries have automatic drive
cleaning functionality. This is also referred to as hardware-based cleaning, library-
based cleaning, or auto-cleaning.
With robotic automatic cleaning, the tape drive sends an alert to the robot, notifying
the robot that the drive requires cleaning. After a backup tape is unmounted, the
robot mounts the cleaning tape and cleans the drive. NetBackup is not involved in
this process.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• TapeAlert: Another method of automatic cleaning uses the TapeAlert feature, which
allows reactive cleaning for some drive types that support the TapeAlert capability.
This method is also called reactive cleaning.
Note: Hardware-based cleaning is not coordinated with NetBackup without
TapeAlert. Because TapeAlert and robot-controlled cleaning provide the same type of
cleaning, Veritas recommends disabling library-based cleaning when using TapeAlert.
• Frequency-based cleaning: One NetBackup drive setting is the cleaning frequency:
the number of hours a drive is used between drive cleanings. Refer to the drive
manufacturer’s recommended cleaning frequency before setting this value.
NetBackup updates the total mount time for a drive each time a tape is unmounted
(only for time when the media is actually assigned to a process, and is in use). If the
drive is in a robot that supports cleaning, and a cleaning tape is configured in that
robot, cleaning occurs when the accumulated mount time exceeds the cleaning
frequency.
alone drive, it must contain a cleaning tape and a mount request is issued. Clean
Now resets the mount time to zero.
• Reset Mount Time: Reset the mount time for the selected drive to zero, even if
a cleaning was not performed.
• Set Cleaning Frequency: Set the desired number of mount hours between each
drive cleaning.
Alternatively, to perform drive cleaning using the command line, the tpclean
command enables you to monitor Media Manager tape drive usage and optionally
configure tape drives to be automatically cleaned (except drives in ACS, ODL, or TLH
robots, or QIC drives).
17
After completing this topic, you will be able to perform media management, including
moving, ejecting, changing, sharing, erasing, and deleting volumes.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Volume expiration
• How long you want to use the physical media.
• Optional setting that limits the lifespan of the physical media.
• Normally based on vendor recommendations or departmental
policies.
Image retention
• How long the image is available for restores.
• Required setting on backup policy schedules
• Typically based on the restore service level agreement (SLA) for
the data.
18
There are two distinct types of expiration in NetBackup: volume expiration and image
expiration. Likewise, the volume expiration date and the image expiration date have
distinct meanings.
Volume expiration
You can change the expiration date for volumes. The volume expiration date refers to
the age of the tape media and is the time at which the tape is considered too old to be
reliable. When the expiration date has passed, a volume can still be read but is not
mounted for a write.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
19
This slide is a reminder that the volume expiration date is set in the Expiration date
section of the Change Volumes dialog box. This slide also shows that the retention
period is displayed in the Schedule section of the policy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
ABC123
EOM
Image
NetBackup database
database
Valid Ret Volume Media Header
Media ID Assigned .f file
Images Level Pool State info
ABC123 N 0 --- scratch AVAILABLE
20
When a backup job is initiated, NetBackup selects the required piece of media based on
the parameters of that specific backup job. The policy and schedule dictate the required
storage unit, volume pool, and retention level. The actual media selected is discussed
elsewhere in this lesson.
The example on this and the following slides shows the life cycle of a tape—from
unassigned, to assigned, and then unassigned again.
In this example, a backup job is requesting a tape from the servers pool with a two-
week retention. If a tape is not available in the servers pool that meets all the necessary
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
criteria, NetBackup will attempt to move a tape from the scratch pool to the servers
pool for use in the backup.
Also, this example shows a tape that has already been labelled with media ID ABC123.
Following the label (sometimes known as the media header), is a mark that shows the
logical end of the tape. This is sometimes known as an End of Data (EOD) or End of
Media (EOM) mark, and indicates to any tape drive reading the tape that no more
pertinent data exists past this mark, even though it is not the physical end of the tape.
When the tape is first added to NetBackup, an entry is made in the EMM database. The
entry includes the media ID of the tape. Initially, the tape is unassigned and the media
state is AVAILABLE.
ABC123
Image1 Image2 Image3
EOM
EOM
EOM
EOF
EOF
EOF
BH
BH
BH
2 week retention 2 week retention 2 week retention
21
After the first backup is written to the tape, the NetBackup database is updated so that:
• The tape is now assigned, and there is one valid image.
• The retention level of the backup is set, in this case to two weeks. The default is not
to mix retention periods on media.
The NBDB and Image database are also updated to contain the metadata about the
backup job. These are represented by Image1 and Image1.f in the slide. Image1 and
Image1.f are sample names. The actual name of the image is stored in the format of
policyname_ctime_schedule, where ctime is the creation time of the image.
Before a backup is written, a NetBackup backup header (BH) is placed on the tape. At
the end of a backup, an End of File (EOF) marker is written. If NetBackup is not writing
further data in this session, an End of Media (EOM) marker is also written, to indicate
the logical end point of this tape.
When the second image is written, the EOM marker is overwritten by the backup
header of the next image, and a new EOM marker will be written at the end of the
backup. The NetBackup database now indicates there are two images on the tape. This
same process occurs for the third image written to the tape.
ABC123
Image1 9.46
Image2 Image3
EOF
EOT
EOF
EOF
BH
BH
BH
2 week retention 2 week retention 2 week retention
22
An End of Tape (EOT) indicates that the physical end of a tape is reached
In this example, the third backup is written to the end of tape (EOT). In most cases, the
backup image will not fit exactly on the tape, and the third backup may actually be
continued on further media.
At this point, the media state is now set to FULL in NetBackup.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
ABC123
Image1 Image2 Image3
EOF
EOT
EOF
EOF
BH
BH
BH
2 week retention 2 week retention 2 week retention
Image
NetBackup database
database
Valid Ret Volume Media Header
Media ID Assigned .f file
Images Level Pool State info
ABC123 Y 3
2
1
0 2 wk servers FULL
Y 2 wk servers FULL Image1 Image1.f
Y 2 wk servers FULL Image2 Image2.f
Y 2 wk servers FULL Image3 Image3.f
23
The image cleanup job determines which images have met their retention period and
are expired. Expired images are removed from the NetBackup databases.
In this example, two weeks have passed from when the first image was written. At that
point, Image1 has met its retention level and is ready to be expired. Note that after
Image1 expires, NetBackup no longer records information about that backup in the
NetBackup database, so restores of that backup are no longer possible without further
actions (such as an Import operation, discussed elsewhere in this lesson). Although
Image1 is removed from the database, the data for Image1 still physically resides on the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
ABC123
Image1 Image2 Image3
EOF
EOT
EOF
EOF
BH
BH
BH
2 week retention 2 week retention 2 week retention
Image
NetBackup database
database
Valid Ret Volume Media Header
Media ID Assigned .f file
Images Level Pool State info
ABC123 N
Y 0 2---
wk scratch
servers AVAILABLE
FULL
After all the images are expired and the NetBackup database indicates there are no
longer any valid images associated with the media ID, the media is ready to become
unassigned, and have its media state set to AVAILABLE. This occurs during the
NetBackup image cleanup. Image cleanup occurs after each successful backup session
(during any short period of backup inactivity after backups have run). However, even if
there is no inactivity, due to a busy backup environment, a cleanup interval occurs every
12 hours, by default. This value is set in the NetBackup master server host properties >
Clean-up > Image cleanup interval.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
If the media originally came from the scratch pool, then it will be returned to that pool.
The media life cycle process begins again.
Even though the data on the tape is expired and is no longer being tracked in the
NetBackup catalogs, the actual data on the tape is not erased. The physical data
continues to exist on the tape. If the tape has not been reassigned, the data can be
imported using NetBackup, if necessary.
If the media has been reassigned and rewritten, or manually re-labeled, then the old
data will be overwritten by new backup images. At this point, with third-party software
and tools it may be possible to extract the old data from the tape, but this is outside the
scope of what is possible with NetBackup. The data is considered unrecoverable.
25
All volumes have a media state, which changes based on a number of factors, such as
how much the volume is used or the type of backup written to it.
The most common media states are:
• AVAILABLE indicates that no active backup images are currently associated with this
tape. This can happen if:
• This is a new tape; NetBackup has never written data to it.
• NetBackup has used this tape, but all images on the tape have met their
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
NetBackup
• Use Media and Device Management > Media
Administration • Use NetBackup Management > Reports
Console
27
NetBackup provides various reporting methods by which you can determine the status
of media. Use any of the following interfaces to determine the media status.
• Available media: The available_media script reports on all media in the environment
that is usable by NetBackup. This report also indicates the current media states.
• The NetBackup Administration Console: When you use the NetBackup
Administration Console to determine status information, you use the Media and
Device Management > Media and the NetBackup Management > Reports
interfaces.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
None pool
scratch_pool pool
server_tapes pool
UNIX: /usr/openv/netbackup/bin/goodies/available_media
Windows: install_path\NetBackup\bin\goodies\available_media.cmd
28
Located in the goodies directory, the available_media script lists all the media IDs that
are available on the server where you run the script. Within the report, the
available_media script displays the status of each piece of media.
• UNIX: /usr/openv/netbackup/bin/goodies/available_media
• Windows:
install_path\NetBackup\bin\goodies\available_media.cmd
This script can be invoked from any administrative server.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Note: An asterisk (*) in the ret level column indicates the media has images written to it
with multiple retention periods. The default for NetBackup is one retention period per
media.
29
Using the Media interface of the NetBackup Administration Console, you can obtain
information about your media. This screen shot shows the volume catalog. Use it to
quickly determine if a piece of media is used. If the Time Assigned field for a piece of
media is empty, then the piece of media is not currently in use and would be reported
as Available in the available_media script. If the administration console has been
running for a while, the information displayed in the details may be stale. Use the
refresh button to refresh the contents.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
30
You can run various reports from the NetBackup Administration Console and from the
command line to gather information about media used in the NetBackup environment.
To access the media reports using the NetBackup Administration Console, expand
NetBackup Management and expand Reports > Tape Reports. Click the report you want
to generate.
The example on the slide shows a Tape Summary Report, which summarizes active and
non-active volumes for the specified media owner (server) according to expiration date.
It also shows how many volumes are at each retention level. In verbose mode, the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
32
After completing this topic, you will be able to perform media management, including
moving, ejecting, changing, sharing, erasing, and deleting volumes.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
33
All volumes have a media state. The media state can change based on a number of
factors, such as how much the volume is used or the type of backup written to it.
NetBackup automatically controls the media state of a volume, but in some cases, you
can override the NetBackup setting.
You can override some media states using the NetBackup Administration Console. To do
so, expand Media and Device Management > Media. In the details pane, select a piece
of media and select Actions. From the Actions drop-down menu, select Freeze,
Unfreeze, Suspend, or Unsuspend. Media that is available (no time assigned) cannot
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
have it’s media state manually changed and attempts to freeze or suspend unassigned
media generates an error.
When a tape has at least one unexpired backup image, it is said to be Assigned. New
images are appended to these assigned (active) tapes. When all of the images on the
tape have expired, the tape automatically unassigned by NetBackup at midnight.
You can override some media states using the bpexpdate and bpmedia commands.
If you wish to reuse a tape with images before they naturally expire, you can use the
bpexpdate command with the –m media_id option to select the tape, and –d 0
option to set the date for all backup images on the tape to expire immediately. This
command additionally de-assigns the tape, so it becomes immediately available, even if
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Move Change
Sets volume group (location) Modifies properties
Eject Delete
Physically ejects tape from library, and Removes tape from configuration
sets volume group
• Must not contain valid backup
? images
• Used for removed, missing, or
corrupt tapes
36
There are various operations that you may want to perform on tape media:
• Move: Moving a tape involves changing the media’s volume group, which defines
where it physically resides. Note that this does not physically move the tape. It
simply allows the administrator to set and track the tape’s location.
• Eject: Ejecting a tape physically causes it to leave the library. This function does
require a tape library that supports an eject function with a media access port. You
can simultaneously set the volume group for the media, as when using the Move
function.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Change: Changing media includes changing properties such as setting the tape’s
physical expiration date (when it no longer deemed to be good hardware used for
writing new backups), the volume pool the tape is in, or the maximum mounts (the
number of times it can be used).
• Delete: Deleting a tape is performed when a tape should no longer be tracked by
NetBackup, such as when it has been lost, or the data is corrupt and cannot be
restored from. Note that a tape must be made available (by expiring all images on
the tape) prior to deleting it.
TLD(0) (no power), the record describing 0C0000 will still show as being in slot TLD(0) so
your attempts to inventory TLD(1) fail when the inventory sees the 0C0000L1 barcode
which is associated with that tape 0C0000.
The solution to this conundrum is MOVE. You can MOVE 0C0000 to STAND-ALONE
which simply updates the record in the NBDB describing 0C0000 so that it shows as not
being in any library. Then you can inventory TLD(1) which should now successfully
update 0C0000 to reflect that it is now in TLD(1).
39
Ejection physically transfers media from slots within the robot to media access ports or
mail-slots, and additionally updated NetBackup to reflect the change of residence.
To eject a volume using the NetBackup Administration Console:
1. In the object tree pane of the NetBackup Administration Console, select Media and
Device Management > Media.
2. In the right pane, right-click the desired volume and select Eject Volumes From
Robot, or select the volumes and then select Actions > Eject Volumes From Robot
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
vmchange
40
There may be times when you need to modify a volume that has already been
configured. For example, you may need to change the volume pool to which the volume
belongs, change the volume’s expiration date, or assign a media description to the
volume so you can easily locate the volume if you need to restore from it.
To change a volume attributes:
1. In the object tree pane of the NetBackup Administration Console, select Media and
Device Management > Media.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2. In the right pane, right-click the desired volume and select Change, or select the
desired volumes and select Edit > Change.
You can change the following attributes for your volumes:
• Maximum mounts
This option controls the number of times that the volume can be mounted. When a
volume reaches its maximum mounts, Media Manager considers this tape non-
writable and ignores it as a destination for further backup and duplication jobs.
However, the volume is still readable so can be used as a source for imports,
duplications and restores.
• If a cleaning tape is selected, this option will be greyed out.
• Do not change: Select this option to keep the current setting.
• Unlimited: Select this option to allow an unlimited number of mounts.
Unlimited is the default setting.
Use this option to increase or decrease the number of uses remaining for a cleaning
volume.
• Do not change: Select this option to keep the current setting.
• New count: Select this option and type a number to define the number of
cleanings remaining for the volumes.
vmdelete
42
Deleting a volume removes the record that describes the volume from the NetBackup
database (NBDB). This operation does nothing to any physical data that may be on the
tape. In order to delete the record describing the tape from the NBDB, the tape must
be AVAILABLE, that is, unassigned.
If the tape is assigned, you must first expire all copies of the backups that NetBackup
has a record of on that tape and allow the tape to be unassigned, for example with the
bpexpdate -m media_id -d 0 command. This command expires those copies
of images that reside on the tape and de-assigns the tape. Trying to delete an assigned
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
volume will result in the error message: “Cannot delete assigned volume”.
Some of the reasons you may want to delete a volume are:
• Unusable because of repeated media errors.
• Past its expiration date or has too many mounts and contains no relevant backups.
• Lost and you want to clean up the NetBackup database.
Note: Deleting a volume removes it’s entry from the NBDB so the eject operation
cannot be used to remove the volume. Either manually remove the volume from the
robot or eject the volume using the eject operation before deleting the volume from
NetBackup’s NBDB database.
EOM
EOF
EOF
MH
BH
BH
Image1 Image2
EOM
EOM
EOF
EOF
MH
BH
BH
Image1 Image2
EOM
EOF
EOF
EOT
MH
BH
BH
Image1 Image2
EOM
bplabel –erase –l
EOM
EOF
EOF
MH
BH
BH
Image1 Image2
bplabel -erase
43
There are various methods available to erase physical data on a tape in NetBackup.
Note that if a tape is assigned (contains unexpired backup images), NetBackup will not
allow you to erase the tape. You will need to wait until the images expire, or to manually
expire those images with the bpexpdate –m media_id -d 0 command.
For comparison, the slide uses an illustration of a tape with previously written data. The
data is shown faded because the images are expired in the NetBackup catalog. Although
the data physically exists on the tape, NetBackup considers this an unassigned tape.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
44
By default, assigned media is owned by a single media server. Only backup and
duplication jobs running on a the media server that owns the tape can append more
images to that tape. The media sharing feature in NetBackup enables tape media
sharing among any number of media servers and NDMP tape servers. Appending to
tape is no longer restricted to a single media server. This capability is included in the
base NetBackup product at no additional cost. The benefits of media sharing include:
• Reduced media costs by minimizing the number of required tapes
• Improved media utilization by minimizing the number of partially full tapes (media
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
to share all media (share everything). This approach allows multiple media servers
to write a tape with incompatible block sizes. Media cataloged in the EMM database
shows UNRESTRICTED_SHARING_GROUP in the Server Group column within the
media records.
• Media Sharing Groups are an alternative unrestrictive sharing, instead using server
groups to allow logically (and physically) related groups of servers to share and own
media. By creating server groups, you gain more granular control over which media
servers can write to media. After server groups are configured, you configure a
policy to use a specific group of servers media sharing server group. The media
written by such policies is owned by the group instead of the individual media server
so any of the servers in that server group can write future backup and duplication
jobs to the media.
Win_Servers Scratch
46
A NetBackup backup request specifies a specific storage unit and volume pool, as
defined by the backup policy.
When media management receives the request, NetBackup selects a volume based on a
number of rules and priorities. In order:
1. Active volumes in the volume pool
NetBackup first searches the database for an active volume in the specified volume
pool. This volume must be in the library that is in the storage unit being used. The
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
volume must not have exceeded its maximum number of mounts nor its volume
expiration date (which are settable, volume specific attributes used by NetBackup to
determine when NetBackup can no longer write to the volume).
Additional criteria includes making sure that the retention level matches that of the
images that are already on the tape. Note that you can override this with the media
server host property > Media > Allow multiple retentions per media, however
Veritas does not recommend using this setting without understanding the
implications of mixed retention images on media.
Next, a volume will be selected that is owned by the media server. By default media
servers own any tapes they have previously written to, however you can override
this with the master server host property > Enable unrestricted media sharing for all
media servers, or with server media Server Groups.
After completing this topic, you will be able to identify tape device and
media reports.
48
After completing this topic, you will be able to identify tape device and media reports.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Destruction of media
49
A common physical problem is unreadable bar code labels on your media. Inspect the
labels on your tapes for torn or worn labels and for signs of smearing, smudging, or
fading of the ink. Replace the labels as necessary.
Other physical media problems are stretched, jammed, or broken tapes. Tapes can be
erased when exposed to strong electrical fields, so ensure that your robotic tape library
is not located near such a field.
Drives that need cleaning can manifest media related problems.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
If you encounter media problems that you cannot correct using NetBackup, physically
inspect the volume itself to check it for these or similar problems.
An additional media issue is that a volume can be completely destroyed. For example,
consider what can happen to a tape left inside your car on a hot summer afternoon.
To help circumvent potential physical media issues, it is recommended that you make
multiple copies of all crucial backup images using duplication, inline copies, or vaulting.
Drive properties and Devices > Drives tpconfig -d Monitor > Devices
characteristics Device Monitor vmoprcmd Manage > Devices >
scan –tape Drive
50
The table on this slide summarizes how to report on tape devices using the NetBackup
Administration Console, NetBackup commands, and OpsCenter.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Problem and status NetBackup Management > bpmedialist Monitor > Media, filter
information Reports > Tape Reports > bpimmedia by Full Media, Frozen
Media Logs, Tape Media, Suspended
Summary bperror Media, or Other Media
bpimagelist Run Media Reports to
nbemmcmd identify media status
vmquery and problems.
51
The table on this slide summarizes how media can be managed using the NetBackup
Administration Console, NetBackup commands, and the OpsCenter Web console.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
52
The table on this slide summarizes the methods for changing media using the
NetBackup Administration Console, NetBackup commands, and the OpsCenter Web
console.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
53
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
54
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
55
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. FROZEN
B. SUSPENDED
C. FULL
D. EMPTY
56
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. FROZEN
B. SUSPENDED
C. FULL
D. EMPTY
The correct answer is D. EMPTY is not a valid status. When a tape doesn’t have any NetBackup data on it, it is considered
AVAILABLE (in the available_media script) or ACTIVE without a time assigned (in most NetBackup media reports).
57
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. More than one media server can append to the same tape.
B. More than one master server has the same tape in its catalog.
C. More than one backup application can write data to a tape.
D. Data from more than one client can be written to a tape.
58
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. More than one media server can append to the same tape.
B. More than one master server has the same tape in its catalog.
C. More than one backup application can write data to a tape.
D. Data from more than one client can be written to a tape.
59
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
60
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
61
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-62
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Performing Virtual Machines Backups” lesson in the “Veritas NetBackup 8.1:
Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
Introduction to virtual machine Describe virtual machines and discuss support for virtual machines
backups in VMware.
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to describe virtual machines
and discuss support for virtual machines in VMware.
After completing this topic, you will be able to describe virtual machines and discuss
support for virtual machines in VMware.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Using virtualization, a host server performs the job of multiple computers sharing the
physical host’s resources.
• Each virtual machine (VM):
– Runs its own operating system and applications
– Is encapsulated and isolated from other VMs
– Uses its own emulated resources (such as CPU,
disks, and network connection)
• The virtualization layer, or hypervisor, is software that enables virtual machines to use
the host’s physical resources.
• The hardware layer consists of the physical components of the host server, and is shared
across the running virtual machines.
• Review document NB_70_80_VE: Support for NetBackup in virtual environments
Virtual machines, sometimes referred to as VMs, enable the sharing of the underlying
physical machine resources between virtual machines, each running its own operating
system. The software layer providing the virtualization is called a virtual machine
monitor or hypervisor. A hypervisor can run on bare hardware (native VM) or on top of
an operating system (hosted VM). An example of a hypervisor running on bare hardware
is VMware ESX Server. An example of a hypervisor running on top of an operating
system is VMware Server and Workstation. In the case of Microsoft Hyper-V, the
hypervisor runs on a special version of the Windows operating system.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Modern CPUs have features built in for system protection. These protections keep
different programs from writing into each others’ memory regions. CPUs also have
privileged instructions: Instructions only executable by the operating system.
The structure of virtualization is to allow multiple operating systems to run on the same
set of CPUs. In order to allow multiple operating systems to run, the virtualization
mechanism has to properly handle privileged instruction execution.
There are different methods virtualization systems use to handle privileged instructions.
VMware and Hyper-V use virtualization features of the CPU: Intel VT and AMD-V. The
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
hypervisor signals the CPU that certain processes are virtual machines, and allows the
privileged instruction to execute. Prior to this CPU technology, the hypervisor
intercepted privileged calls and executed software to manage access to the privileged
instructions. This virtualization technology model is more efficient and reliable.
Citrix XenServer uses para-virtualization: the operating system is modified to
accommodate the privileged instruction execution.
The hypervisor virtualizes networks, network switching, interrupts, and disk storage.
A hypervisor control application manages and monitors the creation, operation, and
lifecycle of virtual machines. Often, this control application runs on a separate host, to
remotely and centrally manage the virtualization servers.
VMware vSphere ✓ ✓ ✓ ✓ ✓
Microsoft Hyper-V ✓ ✓ ✓ ✓
RedHat Enterprise
Virtualization ✓
Citrix XenServer ✓
Solaris zones ✓
Oracle Solaris
virtualization ✓
Hypervisor
control system
SAN
Control API
CLI
Web Interface
Storage
Cloud
orchestration
Virtualization
Web Client
backup solutions. There are limitations and requirements, based on the software and
the environment. For example, in some cases the guest (VM) operating system may
need to have the NetBackup client installed to allow for advanced backup and recovery
features, such as one-pass VMware backups that simultaneously allow for granular
application recovery.
The specific architecture used in a virtual environment should be well understood.
Veritas solutions support a subset of many varieties of virtualization storage and guest
operating system architectures. Be sure to examine and evaluate the support and
limitations of both the virtualization vendor and the Veritas NetBackup solution in
designing your backup strategy for virtual environments.
Intelligent Policy with VM query builder VMware policy type Hyper-V policy type
NetBackup support for VMware vSphere and Microsoft Hyper-V are summarized in the
table on the slide.
Both products are supported with full VM recovery, or individual file and folder level
restores, from single-pass backups performed by NetBackup. Both VMware and Hyper-V
policy types exist, that include automatic VM selection using a query builder, as well as
simplification of VM-specific backup configuration. Settings exist to limit and control
backup impact on the environment, to ensure performance is not adversely affected.
Full and incremental backups are supported, including block-level incremental backups
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
(BLIB) that avoid backing up unused space. BLIB is supported with VMware Change
Block Tracking (CBT) and Hyper-V Windows Management Instrumentation (WMI).
NetBackup for VMware also supported application-aware single-pass backups for
granular recovery of Microsoft Exchange, and SharePoint, and provide log truncation for
Microsoft SQL and Exchange. NetBackup for VMware also supports instant virtual
machine recovery, which is discussed in more detail in the Performing Virtual Machine
Restores lesson.
Off-host backups of VMs are supported in VMware using VMware vSphere Storage APIs
– Data Protection (VADP), reducing processing load on the VM server, and preventing
the need to install a NetBackup client on the VMs. Hyper-V also supports some off-host
/ alternate client backups, but requires some additional configuration steps, as provided
in the documentation.
Centralized management and web consoles are supported, which include VMware
vSphere web client, vCenter servers, and the Hyper-V System Center Virtual Machine
Manager (SCVMM).
After completing this topic, you will be able to configure VMware backups.
After completing this topic, you will be able to configure VMware backups.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11
The slide lists VMware components and components used by NetBackup when backing
up VMware. The first four components list VMware servers and components, and the
bottom four components list NetBackup components.
The VMware vCenter server is not required for NetBackup to perform VMware virtual
machine backups; however, certain features may not be available or alternate
configurations may need to be used.
The VMware backup host has certain operating system restrictions. These are discussed
on the following slide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Note: The VMware backup host was referred to as the VMware backup proxy server in
some prior releases.
To perform backups that enable full VM and file-level recovery, the NetBackup client
does not need to be installed in the VM.
The NetBackup client needs to be installed in the following circumstances:
• Performing individual file restores directly to the virtual machine
• Performing Application backups with a VMware backup policy
NetBackup
client
Datastore
(VMDK files)
14
The process within NetBackup for VMware-based backups follows these general steps:
1. The NetBackup master server starts the backup and initiates a VMware snapshot by
communicating with the VMware server. Note that in VMware, the snapshot causes
the original VM image – represented on the slide as VMDK – to become static. A new
VM image file – represented on the slide as VMDK.1 – continues to record new
data.
2. The VMware backup host (in many cases the Windows media server) reads the
static VMDK files (represented on the slide as VMDK), maps their contents using the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
vStorage APIs to index individual files and ensure only used space is being written,
and writes the backup directly to disk or tape.
3. After the backup completes successfully, the VMware snapshot is deleted. On the
slide, the changes recorded in the VMDK.1 VM file are rolled into the static data
held by the VMDK VM file. Note that by default NetBackup will only remove previous
snapshots created by NetBackup, and will not modify any other VMware snapshots
in the environment.
15
This slide shows an overview of the VMware and NetBackup configuration required to
create VMware backups managed by NetBackup. These steps are discussed in the
NetBackup for VMware Administrator’s Guide, and are shown in more detail in the
following slides.
VMware configuration
The VMware configuration is not based on the NetBackup environment, and the
VMware documentation should be used for all VMware specific installation and
configuration.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The VMware Tools package is often installed on virtual machines, and does enable
NetBackup to perform backups of virtual machines without the NetBackup client
software installed on the VM. Although not technically required, issues like crash-
consistent backups may occur.
Additionally, NetBackup integrates with VMware components such as vCenter and
vSphere, as is discussed elsewhere in this course.
NetBackup configuration
The NetBackup configuration steps shown on the slide are discussed in more details in
the following slides in this lesson.
• Review tips in Veritas NetBackup for VMware Administrator’s Guide: NetBackup for
VMware best practices
• Best practices may include:
– Upgrade to the latest version of VMware vSphere or Virtual Infrastructure.
– Use the same VM name for both host name and display name.
If the policy’s Primary VM identifier option is changed, the existing entries under the policy’s Clients tab are still
valid.
– Add additional VMware backup hosts for scalability.
– Use VMware resource limits
For example, allow less than 4 concurrent backup jobs / snapshots per datastore.
– Attempt to use a single backup policy per datastore.
16
Before configuring NetBackup, Veritas recommends that you configure or modify the
VMware environment.
Before configuring the NetBackup for your VMware environment, Veritas recommends
reviewing the Veritas NetBackup for VMware Administrator’s Guide in the NetBackup for
VMware best practices section.
Some VMware best practices are given on the slide.
Note that NetBackup does not require any modifications to existing vSphere
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
environments.
17
The VMware backup host requires the NetBackup client software. For details refer
to both the NetBackup for VMware Administrator’s Guide: NetBackup for VMware
best practices. Some recommendations include:
• For a more efficient backup, install the NetBackup media server and the VMware
backup host on the same host.
• Ensure that the VMware backup host has enough memory to handle the number
of simultaneous backups that occur. Monitor active memory usage on the
backup host during backups and add memory if needed.
• Add additional backup hosts to increase backup throughput, when needed.
3
Add VMware backup
host to NetBackup
18
3. Add any VMware backup hosts to the Host Properties for the master server:
a. Click Host Properties > Master Servers, double-click the NetBackup master
server, and click VMware Access Hosts.
b. Click Add, enter the VMware backup host, and click Add.
c. When you are finished adding hosts, click Close.
In the policy’s VMware backup host drop-down list, select Backup Media Server to use
any available media server. If this option is used, make sure that all media servers in the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
storage unit referenced by this policy are valid VMware backup hosts.
19
Optionally, set limits on the use of VMware resources by navigating to the Resource
Limit tab of the master server’s Host Properties. Click in the Resource Limit column to
set the maximum NetBackup usage for the resource type. The settings apply to all
VMware policies that use a VMware Intelligent Policy query to select clients. VMware
Intelligent Policy queries are discussed elsewhere in this lesson.
The default for all resource limits, indicated in the NetBackup Administration Console by
a blank value in the Resource Limit column, is unlimited. The screen shot shows a
maximum of four simultaneous backup jobs to any ESX server at a given time.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
For details on resource limit types and behavior, see the NetBackup for VMware
Administrator’s Guide: Setting global limits on the use of VMware resources.
Note that you may want to adjust or tune the resource limits according to the transport
mode you select.
4
Add VMware credentials
to NetBackup
vCenter server or
ESX server
20
c. In the Add Virtual Machine Server dialog box, enter the name of a virtual
machine server (vCenter server or ESX server).
d. In the Credentials pane of the Virtual Machine Server dialog box, enter the
following, then click OK:
• Virtual machine server type: Select VMware Virtual Center server, VMware
ESX Server, or VMware Restore ESX Server. Note that VMware Restore ESX
Server designates an ESX server to which NetBackup can restore virtual
machines, however NetBackup will not back up virtual machines from that
restore server.
• Username and Password
• If the default port number has changed, mark the Connect using port
number check box, and enter the port number.
5
Use the VMware
policy type
22
5. To create a backup policy, use either the Policy Configuration Wizard or the Policies
utility in the NetBackup Administration Console.
The VMware policy type was introduced in NetBackup 7.5. When it is selected, a
new VMware tab is displayed in the policy configuration dialog. This tab contains
VMware-specific parameters. Veritas recommends using the VMware policy type.
This policy type is discussed in this lesson.
Note: Prior to NetBackup 7.5, the FlashBackup-Windows policy type was used to
back up virtual machines. Veritas does not recommend using this policy type to back
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
up virtual machines unless it is required, because this policy type does not support
newer backup functionality and features.
To migrate FlashBackup-Windows policies that were created in prior versions to use
the new VMware policy type, see the nbplupgrade utility in the NetBackup
Commands Reference Guide.
Attributes Schedules
• Many options don’t apply • Supports full, differential, and cumulative
incrementals
• Supports full VM and file-level incrementals for all
schedules
– Set Enable file recovery from VM backup on the
VMware tab
• Optionally use block-level incremental backups
(BLIB):
– Requires ESX server 4.0 and later, and Virtual machine
at vmx-07 or later
– Set Enable block-level incremental backup option
23
For VMware type policies, many attributes found under the policy Attributes tab are
disabled. Most relevant VMware-specific options are found under the VMware tab,
discussed elsewhere in this lesson. VMware policies support NetBackup Accelerator,
which is discussed in the Optimizing File System Backups lesson.
VMware policies support full, differential incremental, and cumulative incremental
schedules. If you are simply backing up the virtual machine disk (VMDK) files, these
schedules normally all back up the entire file. By setting the Enable file recovery from
VM backup option under the VMware tab, NetBackup can recover the entire virtual
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
machine from these VMDK files, as well as perform individual file recovery. This ensures
that incremental backups only back up the changed files, while still providing the ability
to restore the entire virtual machine. Note that file-level recovery is only available on
supported guest operating systems and file systems. For more details, refer to
NetBackup Support in Virtual Environments, found online at
https://www.veritas.com/content/support/en_US/doc/NB_70_80_VE.
Additionally, block-level incremental backups (BLIB) are enabled using the Enable block-
level incremental backup option. This improves performance further by backing up data
at a block-level, instead of at a file-level. This functionality requires ESX server 4.0 and
later, and virtual machines with hardware version vmx-07 or later.
24
When assigning clients for a VMware policy, you can select whether to select clients
manually or to have them automatically selected using a query that you construct.
To manually specify clients, navigate to the Clients tab, select Select Manually, and click
New. The Browse for Virtual Machines dialog box is displayed. Select Browse and
Select Virtual Machines to see a drop down hierarchy of virtual machines. Select the
virtual machine or machines you are interested in protecting.
Note: If your VMware environment contains many VMware servers and virtual
machines, it may take too long to search and list all of them. To limit the VMware
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
servers that are browsed, follow the directions provided in the NetBackup for VMware
Administrator’s Guide under the section titled: Limiting the VMware servers that
NetBackup searches when browsing for virtual machines.
Note that a policy where virtual machines are manually selected does not work with the
VMware virtual machine limits specified in the master server host properties.
Example queries:
• Back up all VMs in Power On state
• Back up all VMs where the OS type is Windows 2012
• Back up all VMs where the display name starts with “Vmprod”
• Back up all VMs in the Dev folder that belong to cluster Cluster03
• Back up all VMs in Power On state in datastore Storage 1 where
the OS type is RedHat Linux
25
Starting with NetBackup 7.1, VMware-based policies allow for automatic virtual
machine selection. Queries are built around virtual machine attributes to determine
which virtual machines to back up. These queries can be combined with filters to create
more complex queries and limit the results.
If you want to use the new intelligent policy functionality instead of performing a
manual configuration, set the Virtual machine selection to Select automatically
through query. Next, set the VMware discovery host. Although this does not need to be
the same as the VMware backup host, in many environments this may be the same
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
server. The VMware discovery host has the same requirements as a backup host: be a
supported operating system and have NetBackup software installed.
In this query builder, you build the virtual machine selection query. If you do not select
any query filters, the default behavior is to discover all virtual machines, and back them
all up.
The slide shows some examples of possible virtual machine selection queries. Some
examples show queries that use multiple query filters that are combined to narrow the
resulting virtual machines.
Join: Clear
• Not
• And Value(s)
• And Not
Operator:
• Or Field: • AnyOf
• Or Not VMware-related fields, such as • Contains
Cluster, Datacenter, Datastore, • EndsWith
Displayname, ESXserver, Tag, • Equal
VMGuestOS, and many more. • Greater
• GreaterEqual
• IsSet
• Less
• LessEqual
• NotEqual
• StartsWith
26
all possible values from the VMware configuration. Depending on the size of the
environment, this can take some time. You can then select from the results and they are
added automatically to the Value(s) field.
The slide shows examples for the variables that make up the selection queries, including
the Join, Field, and Operator fields.
The buttons on the right help select values and form complex queries:
• The Browse button is used to discover available values based on the fields and the
available VMware resources.
• The Add button is used to add this filter to the query.
• The Clear button clears these fields, enabling you to start again.
27
VMware Tag operations require vCenter Server 6.0 or later. The NetBackup master
server and all discovery hosts must be at NetBackup 7.7.1 or later. When using media
server load balancing, all media servers that are associated with the storage unit group
must be at 7.7.1 or later.
Any Windows host with only the NetBackup client software installed, that is also
defined in the VMware policy's Client tab as the NetBackup host to perform automatic
virtual machine selection, must have NetBackup Java installed. Install the NetBackup
Remote Administration Console to install NetBackup Java.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
If the tag field is not required to satisfy the query, tags will not be collected and backed
up. In such a case, the tags will not be restored in a successful restore.
Note: Invalid queries or data that cannot be processed by basic mode (such as
parenthesis for precedence) may prevent being able to return to basic mode.
28
Instead of using the query builder’s Basic Mode, click the Advanced button to use the
Advanced Mode. In this mode, you can customize the query manually and use
functionality, such as parenthesis, to establish query order and precedence.
When converting from basic mode to advanced mode, the existing query is converted
and can be used as a starting point.
Note that while in advanced mode, you can also click on the Basic button to revert to
basic mode. This function does not work if the query contains invalid data, or data that
is not supported by basic mode (such as parenthesis).
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
29
When your query is formed, there is a Test Query button to execute and test the query.
After the test returns, the Test Query Results display every virtual machine found, and
identify whether the current filter value results in the virtual machine being included or
excluded.
If the query is not working as desired in providing the correct virtual machines for the
policy, the query can be modified and retested.
In an environment with large numbers of virtual machines, a query can take many
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
minutes. During that duration, the console cannot be closed or used to monitor other
operations. A command line utility, nbdiscover (found in the NetBackup bin
directory) can be used to check the search terms of a query outside of using the
NetBackup console. This frees the console for monitoring and other work. This utility
uses the name of the policy as an argument.
For more details, refer to Veritas NetBackup for VMware Administrator’s Guide in the
Query format and examples for searching virtual machine backups section.
30
The Reuse VM selection query results parameter enables the administrator to control
the virtual center interaction by specifying how old the query results need to be, before
NetBackup queries the virtual center server for virtual machine discovery information
again.
This parameter does not have any effect on backup scheduling. Similarly, backup job
scheduling does not affect when virtual machine discovery takes place. In the example
on the slide, discovery queries the virtual center every 8 hours, regardless of when jobs
are scheduled. When the policy is scheduled to run, the virtual machines that were
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
31
When you use manual virtual machine selection, the Backup Selections list simply
shows ALL_LOCAL_DRIVES.
When you use automatic virtual machine selection, the virtual machine selection query
that was created is listed under the Backup Selections list, as shown in the slide:
vmware:/?filter=VMGuestOS Equal “rhel6_64Guest” AND
ESXserver Equal “esx1.example.com”
In either circumstance, the policy backs up all local drives from each listed virtual
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
machine. To exclude certain drive types, such as swap, boot, or data drives, use the
Virtual disk selection setting under the VMware Advanced Attributes setting. This
setting is discussed elsewhere in this lesson.
32
When VMware is selected as the policy type a VMware tab is displayed in the policy
configuration dialog box which contains many VMware-specific settings.
These settings are discussed in the following slides.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Example configuration
winmaster winmedia ESX server
LAN
SAN
Datastore
STU1 STU2
33
The VMware backup host is a NetBackup host that performs backups on behalf of the
virtual machines. Possible choices include:
• Backup Media Server: This option instructs NetBackup to use the media server of
the backup job as the VMware backup host as well.
Note: The storage unit that is specified in the policy must be unique to media
servers supported as backup hosts. In these cases, if the storage unit is also available
for a media server that is not supported as a backup host, the snapshot cannot
succeed.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
When the Backup Media Server option is selected, NetBackup cannot determine a
host to perform policy validation. To validate the policy, temporarily select one of
the possible media servers as the backup host (do not select Backup Media Server).
When the policy validates successfully, reset the backup host to Backup Media
Server.
• A specific backup host, which selects a particular backup host to perform the
backup.
Note: The backup hosts (but not backup media servers) must be identified in the
master server’s host properties under VMware Access Hosts.
34
This Primary VM identifier specifies how NetBackup recognizes VM names, for backup:
• VM hostname: This is the network host name for the virtual machine. This option is
the default. This option requires running and functioning VMware Tools in the VM.
• VM display name: This is the name of the VM as displayed in the VMware interface.
Character restrictions apply; Refer to the NetBackup for VMware Administrator’s
Guide.
• VM BIOS UUID: This is the ID assigned to the VM when it is created. This ID may or
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
35
The following options set the type and scope of the VMware virtual machine backup:
• Enable file recovery from VM backup: This option enables restores of individual
files from the backup. Additionally, it provides the best deduplication rates with
NetBackup deduplication. With or without this option, you can restore the entire
VM.
• Enable block-level incremental backup: Block-level backups (BLIB) reduce the size
of full and incremental backups by tracking and only backing up the blocks that have
changed since the last backup. BLIB works with VMware’s Changed Block Tracking
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
(CBT) in vSphere to track the block-level changes, and requires ESX server 4.0 and
later, and VM hardware version vmx-07 or later. If this checkbox is enabled,
NetBackup will automatically enable CBT in the VM.
Note: When selecting Use Accelerator on the Attributes tab, the block-level
incremental backups selection will be selected and greyed out so that it cannot be
unselected.
• Exclude deleted blocks: This option uses proprietary mapping technology to reduce
the size of the backup image by excluding any unused or deleted blocks within the
file system on the VM. Windows NTFS, and Linux ext2, ext3, and ext4 are supported.
37
Administrator’s Guide.
When you enable one or more of these Application Protection options, the backup job
automatically initiates an Application State Capture (ASC) job for each virtual machine
listed in the policy. These ASC jobs help determine if the applications are running in
those virtual machines. Because these ASC jobs require additional overhead, it is not
recommended to simply enable these options for policies that back up all VMs. Instead,
create a new VMware policy specifically for those virtual machines that are running
these applications, and enable the Application Protection option for that policy.
This is covered in greater detail in the NetBackup Advanced Administration course.
Datastore Datastore
HOTADD
LAN
Media ESX
server server
SAN
Backup
host
Datastore
Article 100030882: VMware Transport Modes: Best practices and troubleshooting
39
The transport modes determine how the snapshot data travels from the VMware
datastore to the VMware backup host. The appropriate mode depends on your
environment. By default, all modes are selected. NetBackup tries each transport mode
in order, from top to bottom. It uses the first mode that succeeds for all disks in the VM.
The following transport modes are available:
• san: For unencrypted transfer over Fibre Channel (SAN) or iSCSI. Note: This mode is
not supported for VMs that use VMware Virtual Volumes (VVols).
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• hotadd: Lets you run the VMware backup host in a virtual machine. This feature
requires ESX 3.5 Update2 or later. Note: For virtual machines that use VVols, they
must reside on the same VVol datastore as the backup host (hotadd) VM.
• nbd: For unencrypted transfer over a local network that uses the Network Block
Device (NBD) driver protocol. This mode is usually slower than Fibre Channel (san).
• nbdssl: For encrypted transfer (SSL) over a local network that uses the Network
Block Device (NBD) driver protocol. This mode is usually slower than Fibre Channel
(san).
Use the Move Up and Move Down buttons to change the order in which NetBackup
tries each selected mode. For more best practices and suggestions on these modes,
refer to Article 100030882: VMware Transport Modes: Best practices and
troubleshooting, found online at http://www.veritas.com/docs/100030882.
Optionally set
Post events to vCenter
40
This dialog box is displayed when you click Advanced under the VMware policy tab. You
can use the VMware Advanced Attributes dialog to set the following additional
parameters. In most situations, the best settings are the defaults.
• Virtual machine quiesce: This option is enabled by default. I/O on the virtual
machine is quiesced before NetBackup creates the snapshot. This helps guarantee
data consistency in the snapshot. Veritas does not recommend that you disable
quiesce.
• Virtual disk selection: This option determines the kind of disks on the VM that are
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
included in the backup. This option can reduce the size of the backup, but should be
used with care., and is only intended for VMs that have multiple virtual disks.
• Ignore diskless VMs: This option directs NetBackup not to back up any VM that has
no VMDK file assigned to it; for example, a replicated virtual machine in passive
mode in a VMware vCenter Site Recovery Manager (SRM) environment.
• Post events to vCenter: This option enables NetBackup to send backup-related
events to the vCenter server. More information is available on how to view the
events in the NetBackup for VMware Administrator’s Guide.
• VMware server list: Specifies a colon (:) delimited list of VMware servers that
NetBackup communicates with for this policy. VM queries will only go to these
servers, which helps improve performance in large virtual environments.
Example:
scsi0-0,ide0-0,sata0-0,nvme0-0
41
The Exclude Disks tab determines the kind of disks on the VM that are excluded from
the backup. These options can reduce the size of the backup, but should be used with
care. Available options include:
• No disks excluded backs up all VM disks configured for the virtual machine.
• Exclude boot disk excludes only the boot disk (for example the C drive)
• Exclude all data disks includes only the boot disk and excludes all data disks.
• Perform custom attribute based exclusion excludes disks based on VMware custom
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
attributes. If you select this option, you must also enter the name of the Custom
Attribute, which NetBackup then uses to determine which disks to exclude.
The default value for this attribute is NB_DISK_EXCLUDE_LIST or you can enter the
name of the VMware custom attribute. This VMware custom attribute is created
using the Exclude Disk Wizard through the NetBackup plug-in for vSphere Web Client.
NetBackup excludes the disks defined by the attributes listed in the policy. The
attribute must have a comma-separated list of device controllers of the disks to be
excluded, for example:
scsi0-0,ide0-0,sata0-0,nvme0-0
If the custom attribute is not populated or does not exist on the VM, than none of
the disks are excluded. If disks are removed from the custom value between the
differential backups then only those files that changed since the last backup are
available to restore individually. If disks are added to the custom attribute value
between the differential backups then those disks are excluded from the next
backup.
43
The new NetBackup plug-in for vSphere Web Client now contains a Virtual Disk
Exclusion Wizard. This is an easy way to set custom attributes for VMware hosts and
their virtual disks. Once the wizard is launched enter a Custom Attribute name or leave
the default setting, NB_DISK_EXLUDE_LIST. Next, search for the desired virtual host
name and select the host name(s) from the resulting list.
Next, select the disk(s) to which you want to apply the Custom Attribute. If a disk is
excluded already, a warning icon appears in the Exclude disk column.
From the Review Selections screen, select the virtual machine then select Set
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Supports datastores of types: NFS, NFS41, SAN, iSCSI, vsan, VVOL, Local
• Refer to the NetBackup Hardware Compatibility List
• Refer to Veritas NetBackup for VMware Administrator’s Guide: Notes on
VMware Virtual Volumes (VVols)
44
For backup or restore of VMs on VVol datastores, NetBackup supports the following
transport modes: nbd, nbdssl, hotadd. Due to a VMware VDDK limitation, san transport
is not supported.
To restore a virtual machine with the hotadd transport mode: VMware requires that the
virtual machine and the restore host virtual machine reside on the same VVol datastore.
Otherwise, the restore must use a different transport mode (not hotadd).
For a restore to standard (non-VVol) datastores, the NetBackup job creates a vSphere
snapshot of the virtual machine while NetBackup restores the data.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Note: For a restore to a VVol datastore, NetBackup restores the data to the virtual
machine without creating a vSphere snapshot.
When troubleshooting backups of virtual machines on VVols, note the following:
• Each NetBackup snapshot job creates a vSphere snapshot of the virtual machine.
• Licensing requirements for vSphere snapshots vary from one type of VVol storage to
another, depending on the array vendor. Ensure that you have the required snapshot
license from the array vendor; otherwise, snapshot creation may fail.
Refer to Veritas NetBackup for VMware Administrator’s Guide: Notes on VMware Virtual
Volumes (VVols).
After completing his topic, you will be able to monitor VMware backup.
After completing his topic, you will be able to monitor backup, and view process
activities.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• The first parent job runs with the discovery host as Client and resolves virtual machines
with the query in the File list.
• Each VM has a parent snapshot and child backup job.
46
When using automatic VMware client selection, client discovery is required when the
backup runs.
An initial parent job runs the client discovery, showing the job’s client as the discovery
host, and the job’s file list as the query that is being used.
After this initial parent job, each virtual machine is displayed as a standard virtual
machine backup, which normally has an initial parent snapshot job and a child backup
job.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
47
NetBackup can record backup activity for virtual machines in VMware vCenter. You can
view the events in vSphere Client at the level of any parent object (such as folder,
datacenter, cluster, or host). You can also view the events for the entire virtual machine.
Ensure that the policy’s Post events to vCenter option is enabled under the VMware
tab’s advanced options.
To view backup events and the last backup time in vSphere Client:
1. Open the vSphere Client and connect to the VMware server.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
48
Traditionally, virtual machine snapshots do not quiesce Linux virtual machines, and the
backup uses snapshots that are crash consistent. Crash consistent means that the
backup of the system will be roughly equivalent to how the system would appear after a
system crash. Because of file system consistency tools, such as journaling, the system
should be usable, however this is not an optimum way of backing up your servers.
Prior versions of NetBackup provided a tool, SYMCquiesce, that would quiesce some
linux VMs. In NetBackup 8.1 SYMCQuiesce is discontinued since this same functionality
is now present in Open VM Tools for various Operating systems. More info about Open
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Key points
– In this lesson, you learned about virtual machines and support for virtual machines in VMware.
– You also learned to configure and run VMware backups.
• Reference materials
– NetBackup for VMware Administrator’s Guide
– NetBackup for Hyper-V Administrator’s Guide
– Document NB_70_80_VE: Support for NetBackup in virtual environments
– http://www.veritas.com/support
49
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
50
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
51
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. vCenter server
B. Datastore
C. vStorage API
D. VMware tools
52
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. vCenter server
B. Datastore
C. vStorage API
D. VMware tools
The correct answer is B. The datastore contains virtual machine data for the ESX servers.
53
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Windows 2008
B. SUSE Linux 11
C. Solaris 11
D. RedHat Linux 6
54
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Windows 2008
B. SUSE Linux 11
C. Solaris 11
D. RedHat Linux 6
The correct answer is C. Solaris is not supported as a platform for the backup host, regardless of the
NetBackup version. For the latest information, refer to Article TECH127089: Support for NetBackup 7.x in
virtual environments, or the latest NetBackup for VMware documentation.
55
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Oracle
B. Microsoft Exchange
C. Microsoft SharePoint
D. Microsoft SQL
56
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Oracle
B. Microsoft Exchange
C. Microsoft SharePoint
D. Microsoft SQL
The correct answer is A. You can select Microsoft Exchange, Microsoft SharePoint, and Microsoft SQL for Application
Protection under the VMware policy tab.
57
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-58
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Performing Virtual Machines Restores” lesson in the “Veritas NetBackup 8.1:
Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
Using VMware Instant Recovery Run VMware restores using Instant Recovery.
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to describe virtual machine
restore concepts.
After completing this topic, you will be able to describe virtual machine restore
concepts.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
VMware ✓ ✓ ✓ ✓
Microsoft Hyper-V ✓ ✓ ✓
RedHat Enterprise
Virtualization (RHEV) ✓
Citrix XenServer ✓
Solaris zones ✓
Oracle Solaris
virtualization ✓
5
LAN
SAN VM VM
Master Media
server server server storage
After the restore, the VM server can optionally be directed to start the virtual machine.
LAN
NetBackup
client VM VM
Master Media
server server server storage
NetBackup has the capability of performing one-pass backups for virtual machines that
also records metadata allowing for individual file restores. This feature is both time
efficient in allowing for a single-pass backup, and space efficient in requiring only one
copy of the backup for both full VM recovery and individual file recovery.
Recovery of individual files must be performed to a host running the NetBackup client
software. If the virtual machines in your environment are not running NetBackup client
software, you will need to stage the recovery. Some customers have NetBackup clients
(physical or virtual) dedicated to this purpose. Recovering individual files must be
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to run VMware restores using
the Backup, Archive, and Restore console.
After completing this topic, you will be able to run VMware restores using the Backup,
Archive, and Restore console.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
To restore a virtual machine, launch the Backup, Archive, and Restore console. This can
be launched on the master server or on the virtual machine backup host that is
configured to communicate with, and take the data stream from, the ESX server.
1. Set the source and destination clients.
From the File menu, select Specify NetBackup Machines and Policy Type.
2. Set the Source client for restores (or virtual client for backups) as the virtual
machine you wish to restore.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10
Clicking the Search VM Clients button in the Specify NetBackup Machines and Policy
Type dialog brings up the Browse and Search Virtual Machines for Restore dialog box.
The example on the slide shows a sample view when Browse Virtual Machines:
vSphere view is selected.
Select the type of view for browsing:
• vCloud view: Shows the virtual objects as they appear in vCloud Director.
• vSphere view: Shows the virtual objects as they appear in vSphere Client.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11
Select the appropriate restore type under the Select for Restore button:
• Normal Backups: This option is used to view and restore individual files.
• Virtual Machine Backup: This option is used to restore the entire virtual machine.
• Virtual Disk Restore: This option is used to restore one or more virtual disk.
These options are shown in more details on the following slides.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12
The Restore type of Normal Backups is used to view and restore individual files.
Specify the destination as the virtual machine’s host name (not the display name or
UUID).
Note that restoring individual files to a virtual machine requires that the NetBackup
client is installed on that VM. Alternatively, restore to a shared folder that can be
accessed by the virtual machine client.
To restore directly to a virtual machine, the ESX server name that is specified for the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
restore must match the ESX server’s official hostname. The name must be in the same
format in which it is registered in DNS and in the VMware server. The restore fails if ESX
servers are configured with short host names and if the backup and restore are through
a vCenter server.
Note that you can restore Windows files to a Windows guest operating systems, but not
to Linux. Similarly you can restore Linux files to supported Linux guest operating systems
but not to Windows.
If a Linux file system was not quiesced before the snapshot, some files may be
inconsistent. This issue is discussed elsewhere in this lesson.
13
The Restore type of Virtual Machine Backup is used to restore the entire virtual
machine.
To recover the complete virtual machine, select the VMDK files you wish to restore.
If you are restoring from physical tape, click the Preview button to see which tapes are
needed for the restore.
When ready, click the Restore button.
After selecting a Restore type of Virtual Machine Backup, clicking the Restore button
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
starts the Virtual Machine Recovery Wizard. The following slides explore this wizard.
14
The Virtual Machine Recovery wizard guides you through the process of recovering a
complete virtual machine.
The first screen displays the original settings of the virtual machine at the time it was
backed up. Review the settings and decide whether you want to recover the virtual
machine to its original location or to an alternate location.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15
• nbd: For unencrypted transfer over a local network that uses the Network Block
Device (NBD) driver protocol (i.e. the LAN)
• nbdssl: For encrypted transfer over a local network that uses the Network Block
Device (NBD) driver protocol (i.e. the LAN)
• hotadd: Requires that the VMware recovery host is itself a virtual machine. This
feature requires ESX 3.5 Update2 or later.
16
17
restore.
To monitor the restore, click View Status from the Backup, Archive, and Restore
interface or use the Activity Monitor in the NetBackup Administration Console.
18
The Restore type of Virtual Disk Restore is used to restore individual VMWare virtual
machine disks to the following destinations:
• Original virtual machine: Either overwrite the original disks or attach virtual disks
without overwriting them. NetBackup creates a temporary VM to which the virtual
disks are restored to, attaches the virtual disks to the existing, target VM, and finally
deletes the temporary VM after the disks are attached successfully.
• Alternate virtual machine: NetBackup creates a temporary VM to which it restores
the virtual disks, then attaches the virtual disks to the existing, target VM, and finally
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
19
The new Restore Virtual Machine Disks wizard is launched from the Backup, Archive
and Restore interface when you select Restore. The Select Virtual Disks screen shows
all of the virtual disks that were in the VM at backup-time, even those disks that were
excluded from the backup. By default, the wizard displays the virtual disks. Select File
System to show the file system disks. Select the disk(s) you wish to restore, then select
Next.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
20
Select where you want to recover the virtual disk(s) to: Original, Alternate, or a New
(temporary) virtual machine. From the Advanced Restore Options you can Delete
Restored staging VM on error and adjust the Wait time for VM shutdown.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
21
Virtual Disk Destination details are displayed. All options are grayed out since the
Original Virtual Machine was selected as the recovery destination. If an Alternate was
selected then you would have an option to select a different virtual machine. You also
have the option to Power on the virtual machine after restore.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
22
When you select to Recover the virtual disk(s) to a New (temporary) virtual machine
you can set the parameters on this screen.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Original
• Thick Lazy Zeroed
• Thick Eager Zeroed
• Thin
• Custom
• No
• Yes
• Custom
23
The Storage Destination screen shows you the settings for all the virtual disk. Notice the
value for Restored virtual disk provisioning is set to Original (which is the default) and
the Provisioning column displays Thin. This is because the virtual disk being restored
was thin provisioned. If you choose the checkbox for Overwrite the drop-down menu
for Overwrite all virtual disks automatically changes to Yes.
Refer to VMware documentation for more information on disk provisioning types.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
24
The Recovery Summary screen displays the parameters of the recovery. Verify the
setting for the recovery.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
25
Virtual machines in VMware running the Linux operating system are also supported for
full and block-level incremental backups. The most popular Linux distributions are also
supported for NetBackup Single File Recovery (SFR), as long as the following
prerequisites are met:
• vSphere APIs are in use
• The operating system is RHEL 4 or later, or SUSE 10 or later
• ext2, ext3, and ext4 file systems are used
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to run VMware restores with
Instant Recovery.
26
After completing this topic, you will be able to run VMware Instant Recovery restores.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
27
Instant recovery for VMware (IRV) is a capability that allows a VMware infrastructure to
use the NetBackup backup location as a data store.
No data transfer from NetBackup to ESX or vCenter is done. The virtual machine can
start up and begin processing data almost immediately.
In normal mode the virtual machine will be migrated to a production data store. Using
VMware storage vMotion migration can be accomplished while the virtual machine is
running.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
LAN
vCenter
SAN ESX server
Master Media Datastore
server server servers (VMDK files)
28
1. Instant Recovery for VMware uses a Network File System on the media server as a
Datastore
2. VMware starts the recovery VM
3. VMware Storage vMotion may be used to migrate to a production Datastore
LAN
vCenter
SAN ESX server
Master Media NFS Datastore
server server (Datastore) servers (VMDK files)
29
Instant Recovery for VMware uses a Network File System mount served by the
NetBackup media server as a VMware datastore. The ESX server uses the vmdk on this
NetBackup storage to start the recovery virtual machine.
Once the recovery virtual machine is running, VMware vMotion can be used to migrate
the virtual machine to a production datastore.
Instant recovery should not be used as a disaster recovery solution. The load put on the
media server for a full scale disaster recovery will negatively impact backup and
recovery operation.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• SAN connection from the NetBackup media server and its disk storage unit.
– For fibre channel, a minimum speed of 4 Gb/second is recommended
– For iSCSI, a minimum speed of 1 Gb/second is recommended.
• For disaster recovery testing, Veritas recommends that you restore no more than 3 or 4
virtual machines per media server.
• Migrate one VM with Storage vMotion at a time per media server.
30
A SAN connection between the media server and the backup storage is recommended.
The minimum recommended speed for both fibre channel and iSCSI SAN, in gigabits per
second, is given on the slide. Note that NetBackup appliances do not support iSCSI.
For disaster recovery Veritas recommends no more than four virtual machines for each
media server due to the I/O traffic required for operation. The migration may be slow if
you simultaneously migrate multiple virtual machines per media server.
In any disaster recovery the backup system is a key component in its effective operation
is essential to success. Overloading the backup system with IRV operations may prove
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
counter-productive. The number to restore depends on the I/O load on the media
server.
NFS vmdk is
read-only
LAN
SAN
Write
Media NFS ESX Datastore Access
server Datastore servers (VMDK files) DS
1 2
NetBackup File System Service VM is created with write
(NBFSD) mounts the disk storage access to a existing
unit as NFS Read-Only Datastore. datastore (DS)
31
In normal operation for instant recovery for VMware the media server exports the
datastore, making the backup image available as an NFS mount.
ESX server will import that NFS mount, establishing it as a datastore.
A snapshot of the VM is made. ESX sets up temporary write access to local data store
for any changes needed by the VM.
ESX infrastructure will then start virtual machine. The NFS VMDK remains read only.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
LAN
SAN
Write
Media NFS ESX Datastore Access
server Datastore servers (VMDK files) temp DS
32
After the machine is up and running it can be used for normal file recovery. It is a fully
functioning virtual machine so it can actually be used to process data.
In many cases the virtual machine will be migrated to production storage. Production
storage is generally highly available and higher performance than an NFS datastore
exported from a NetBackup media server.
The NFS datastore is unmounted when no longer needed.
Note that the slide illustrates the process assuming that the NetBackup media server is
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
also the VMware restore host. In the case where the media server and restore host do
not reside on the same server, each is responsible for different behaviors during this
process:
1. NBFSD on the media server handles the export phase of NFS of Instant Recovery for
VMware (IRV). The VM will reside on the file system on the media server.
2. NBFSD on the restore host handles the mount phase of NFS of IRV.
3. bpVMutil on the restore host handles the VM activation.
33
Requirements for instant recovery for VMware require network file system operation on
the media server and any restore host.
• The target ESX server for the restore must be vSphere 5.0 and later.
• The client for NFS service has to be operational on the NetBackup restore host.
• The media server must use IPv4.
• There has to be access between NetBackup and the vCenter server in order to
access the VADP API that underlies the service.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
34
In NetBackup 7.7 and later Instant Recovery can be performed using the NetBackup
plug-in for the vSphere Web Client or from the command line using the nbrestorevm
command. The plug-in supports standard recovery, instant recovery and monitoring of
backups of virtual machines that vCenter servers manage.
The NetBackup plug-in for vSphere recovery wizard has the following requirements:
• NetBackup 7.7 and later.
• vCenter Server 5.5 and later.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
This VMware vSphere Client (not the vSphere Web Client) resource map shows the
resources and the noted connections.
This diagram shows, the ESX Server (esx2.example.com), the datastores (INT_ESX2_DS1
and INT_ESX2_DS2), the network, and virtual machines (winvm1 and lnxvm2) prior to
activating an instant recovery. Currently the two virtual machines are located on the
INT_ESX2_DS1 datastore.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The Instant Recovery was successful. In this example, a new temporary NFS datastore,
NBU_IR_winmaster, is recognized and used by ESX for the new virtual machine,
clonelnxvm2, that was added to the environment.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Recovery
Workflow
37
Navigating to the Symantec NetBackup section, there are five available selections:
• Recovery Wizard is used to perform a standard recovery (restore) of virtual
machines.
• Instant Recovery Wizard is used to perform an instant recovery of virtual machines.
• Instant Recovery Cleanup is used to power off and delete virtual machines created
by Instant Recovery which are no longer needed
• Virtual Disk Exclusion Wizard is used to configure and apply a Custom Attribute to a
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
virtual machine or multiple virtual machines for excluding disk(s) from NetBackup
backups
• Register Master Servers is used to register NetBackup master servers with the
vSphere plug-in. This is a pre-requisite for using either of the recovery wizards.
• Settings is used to configure recovery wizard settings
38
Adding a backup server to the vSphere Web Client requires you to generate an
authorization token on the NetBackup master server.
The authorization token is generated using the manageclientsCerts command,
Execute the manageclientsCerts command from a Command prompt, not a
Windows Explorer window.
Use the -create option and the name of the host as the argument.
Once that authorization token has been generated you'll need to transport it over to the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
vCenter machine using a shared drive. You then upload it into the vSphere Web Client to
permit the vSphere NetBackup Web Client to communicate securely to the NetBackup
Master.
39
The settings window allows you adjust the settings that the recovery wizards use.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
40
The Instant Recovery Wizard provides a graphical interface that allows you to instantly
recover VM’s from the VMware vSphere Web Client. The Instant Recovery Wizard
provides five steps to determine important aspects of how a recovery is going to be
carried out. You can see the similarity between these steps and the steps used in Instant
Recovery from the command line using nbrestorevm on the NetBackup master
server.
You can select which vCenter Server and which NetBackup master server to query and
then search for a machine using its display name, UUID, DNS name or hostname. There
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
41
After clicking the Add Virtual Machines button, the number of VMs selected is shown at
the top of the screen. Click the Next button to continue.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
42
Use the Change link to select the specific image you wish to use as the source for the
Instant Recovery. The slide above shows only three images but in a production
environment you would likely have many images to choose from. Details about each
image can be viewed in the Backup Details pane.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
43
Select the destination for Instant Recovery. Destination selection permits alternate
directory and alternate client choices.
Once the VM is recovered, applications can immediately be started or the local
administrator can recover files and objects. The case may be that only a subset of the
recovery is wanted.
Alternate Data Center selection and resource pool gives greater flexibility in recovery
operations. The recovery could be part of a non-production exercise and it would be
contrary to enterprise data center policy to have non-production virtual machines
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
44
45
The recovery settings are displayed. Review the selections you have made and run the
pre-recovery check for a report on access and resources available for the recovery.
A number of resource allocations are checked in this and potential problems of the
recovery are uncovered. As virtual machines in real world production can span multiple
terabytes, discovery of problems early in the process is highly desirable.
At this point all resource checks have returned successful and the restore is ready to
start. Click the Finish button to exit the wizard and recover the VM. The virtual machine
will be powered on from the backup storage and is available for use when the Activate
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Instant Recovery job in the NetBackup Activity Monitor completes. Note that the VM
Instant Recovery job will remain in the Active state until it is deactivated by running the
Instant Recovery Cleanup wizard.
46
The progress and status of the instant recovery job is reported in the Activity Monitor.
The Detailed Status pane includes the key details of the restore job, including the
VMware identifier.
This VMware identifier is used in other commands and is reported in the
nbrestorevm –ir_listvm command to list details about activated virtual
machines, as is shown on the following slides.
The VMware identifier is used as a parameter to some nbrestorevm commands. It is
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
47
The new VM, clonelnxvm2, is now associated with 2 datastores, INT_ESX2_DS2 and
NBU_IR_winmaster_esx2. The NBU_IR_winmaster_esx2 is the temporary NFS
datastore where the backup image of the virtual host is located. The INT_ESX2_DS2 in
the temporary datastore for all write requests for the recovered virtual machine. If the
VM is to remain operational for any length of time it should be migrated (vMotion) off
the temporary datastores (INT_ESX2_DS2 and NBU_IR_winmaster_esx2) and then
Instant Recovery Cleanup can be run to complete the Instant Recovery job. It is not
recommended to leave recovered VM on the temporary datastores.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
48
Once the Activate Instant Recovery job in the NetBackup Activity Monitor has
completed successfully, the VM can be used for any purpose. Applications can be
started and/or files can be copied off the recovered VM. Since the VM is running off of
the backup storage performance will likely be degraded. If the VM is to remain
operational for any length of time, it is best to use vMotion to migrate the VM to a
production datastore.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
49
The Instant Recovery Cleanup screen has three options you can select for a recovered
VM:
• Instant Recovery Done: Use this operation to complete the instant recovery
operation after you have performed the Storage vMotion of the virtual machines to
a different datastore. This utility completes the virtual machine instant recovery
operation after the vMotion migration of the virtual machine is completed. When
the datastore is removed, its resources are released on the NetBackup media server.
• Deactivate: Use this option when you are done with the restore and do not intend
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
to retain the restored virtual machine. This action removes the virtual machine from
the ESX host. If no other virtual machine is using the NetBackup datastore, this
option removes that datastore and releases its resources on the NetBackup media
server.
• Reactivate: Use this operation when connection to the virtual machine was
interrupted. The interruption may occur due to a network disconnect between the
NetBackup media and the ESX server. This utility reactivates a restored virtual
machine by remounting the NetBackup datastore. It also registers the restored
virtual machines on the ESX host.
50
At this point, vMotion can be use to migrate the recovered virtual machine to a
production datastore. From the Instant Recovery Cleanup screen you can initiate a
Instant Recovery Done, which completes the virtual machine instant recovery operation
and the resources are released on the NetBackup media server. The NetBackup Activity
Monitor now shows that all Instant Recovery operations are complete. Other options on
the screen are the Deactive, which deletes the restored virtual machine and the
Reactivate which reactivates a restored virtual machine by remounting the NetBackup
datastore. It also registers the restored virtual machine on the ESX host.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Are you sure you want to deactivate or delete the virtual machine with identifier 5
y/n (n)?y
VM Instant recovery deactivate request returned with status = 0
51
52
This VMware vSphere Client resource map shows the resources and the noted
connections.
After the nbrestorevm –ir_deactivate is successfully executed, the virtual
machine is deleted.
The NFS data store is also unmounted if the virtual machine identified with the VMware
Recovery ID is the last one to use a vmdk file on that mount.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
-ir_done ir_ID Complete the VM instant recovery job after the data is migrated
-ir_reactivate ir_ID
Reactivate a VM that was interrupted during recovery
[-force]
-vmpo Power on the VM
53
The command set options of –ir_done will end an instant recovery job. The VM will
be stopped, then deleted. The imported NFS mount from the media server will be
unmounted by the ESX host. The function of ir_done and ir_deactivate are
identical, if the datastore does not support other active IRV virtual machines.
If the VM recovery ID is gone due to a ir_deactivate option in a command, the
ir_reactivate will fail.
There is a –force option that suppresses command prompts “yes or no” in the
command lines.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Other options to the nbrestorevm command allow you to power on the virtual
machine, remove the virtual network interface from the virtual machine, or invoke a
rename file.
In the rename file the virtual machine host, resource pools, and networks can all be
changed. Example syntax of this file is shown on the slide. There is a specific syntax that
must be followed in the rename file.
• Key points
– In this lesson, you learned about restoring VMware virtual machines and support for Instant Recovery
– You also about Instant Recovery for VMWare
• Reference materials
– NetBackup for VMware Administrator’s Guide
– NetBackup Plug-in for VMware vSphere Web Client Guide
– Article 000006177: Support for NetBackup 7.x and 8.x in virtual environments
– http://www.veritas.com/support
54
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
56
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
57
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The correct answer is B. Both VMware and Hyper-V virtual machine backups support restoring selected files or
directories from full backups, as long as the virtual machine backup was performed with the Enable file recovery from
VM backup policy option.
58
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
59
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The correct answer is B. Whatever identifier was used in the backup policy should be used. This is sometimes the
hostname but it might also be a different identifier such as the Display Name or UUID.
60
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
61
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The correct answer is C. The graphical Instant Recovery and Instant Recovery Cleanup wizards are found in the
NetBackup Plug-in for VMware vSphere Web Client
62
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-63
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Duplicating Backups” lesson in the “Veritas NetBackup 8.1: Administration”
course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
Backup duplication concepts Identify backup duplication concepts such as inline backups, manual
duplication, basic disk staging, and storage lifecycles.
Storage lifecycle policy concepts Describe configuration options for storage lifecycle policies.
Using storage lifecycle policies Create and initiate a storage lifecycle policy.
Additional Storage Lifecycle Policy Explain additional benefits and features of SLP, such as optimized
features and benefits duplication, Auto Image Replication, and Data Classification.
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to identify backup duplication
concepts such as inline backups, manual duplication, basic disk staging, and
storage lifecycles.
After completing this topic, you will be able to identify the duplication backup types,
including inline, manual duplication, basic disk staging, and storage lifecycle.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Client data
Onsite
Backup Duplicate
The default behavior for most backup applications is to configure a client backup to a
backup storage destination, which results in a backup image. Although this provides the
ability to perform a restore, what happens when that backup image is unavailable, or
destroyed, or corrupted?
Duplicating backup images allows for redundancy, and for other restore requirements to
be met. There are a number of duplication strategies available.
One of the simplest and oldest strategies is to duplicate images that have already been
created. This is the traditional solution when you are faced with a tight backup window.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Backup images are created during the backup window, and the duplication is performed
at a later time. Because there is no impact to the clients for duplication, the duplication
was traditionally performed during business hours when tape drives were idle. This may
be a solution if your environment has strict windows during which backups need to
complete.
Client data
Onsite
Backup
Multiple inline copies refers to creating simultaneous backup images at the time of the
backup. This strategy is very efficient because data from client to media server only
travels across the backup infrastructure once. This strategy also provides excellent data
protection because copies may be sent offsite immediately after the backup has
completed.
The disadvantages of this strategy are that it requires additional resources during
backup time, and the overall backup speed is equal to that of the slowest media to
which data is being written.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Also, features are restricted based on the lowest level of backup destination. For
example, you cannot run a Granular Restore Technology (GRT)-based backup, which
normally requires a disk destination, to both disk and tape.
Client data
Onsite Offsite
Vaulting generally refers to the movement of long term storage, normally tapes, to an
off-site location, or vault. The vault provides a level of site-redundancy, so that even if
there is a primary site failure, all the backup data can be restored from the secondary
site.
In some cases, the backup software may assist with this process, and in other ejecting
tapes and managing tape rotation must be performed manually by the administrator.
Traditionally, the term “vaulting” referred to the process of moving tapes offsite,
implying that the target location was similar to a protected, physical vault. In modern
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
parlance, “vaulting” refers to the process of getting backup images to an offsite location
that provides redundancy from primary site failure. In cases where this data is disk-
based, it normally involves sending the data through the network, and may not involve
physically moving tapes.
In NetBackup, replication is copying data from one storage location to another, between
different NetBackup domains. Note that different backup and storage vendors may use
the term replication in different ways, which may or may not match the NetBackup
definition.
Optimized duplication is NetBackup’s ability to take advantage of features within the
disk appliance to:
• Copy an image between appliances without sending data through a separate media
server.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Reduce workload on the NetBackup media servers, which allows more backups to
be performed.
• Perform duplication faster, in the background, simultaneously with ongoing backup
jobs.
• Used during duplication and replication jobs.
Optimized duplication takes advantage of NetBackup Open Storage Technology (OST) to
use the features available in the disk appliance to optimize the duplication or
replication.
One of the main restrictions of optimized duplication is that the source and target disk
appliances need to support each other. In most cases, this means that the technologies
must be identical.
• Combine multiple features to meet service level agreement (SLA) and redundancy
requirements:
– Inline copies, duplications, and staging for onsite redundancy
– Replication to remote sites for offsite redundancy
– Duplication at remote site to provide vaulting without shipping tapes
• NetBackup Storage Lifecycle Policies (SLP) are built to easily support a consolidated
approach.
Client data
Onsite Offsite
Vault
Backup
Replicate Duplicate
For many environments, choosing a combination of strategies is the best way to meet
service level agreements and redundancy requirements.
NetBackup storage lifecycle policies help to automate and provide flexibility in designing
a disaster recovery strategy for backup data that facilitate a combined approach. SLPs
also support additional NetBackup functionality, such as Replication Director and Auto
Image Replication, and can automate tape duplication on remote sites to avoid
manually vaulting tapes. These features are discussed elsewhere in this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10
NetBackup has a number of features that support duplicating backups, many which
were introduced in different versions of the product. Some general strategies include:
• Manual duplications are performed in the NetBackup Administration Console or
with the bpduplicate command. Although this normally requires manual work, in
some cases a third-party scheduler can be used to automate these functions.
• Traditional inline copies are configured in the backup policy’s Schedule window.
This allows up to four simultaneous copies of a backup to be performed.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Basic disk staging storage units (DSSU) provides a method to initially send backup
images to a disk and then later (as specified in the disk staging schedule) copy the
images to another media type. It provides little configurability, and the same backup
destination folder, schedule, and retention are used for all duplication jobs.
• NetBackup Vault provides functionality for automated duplication of backups, and
ejecting of tapes, but does not support more sophisticated features such as inter-
domain replication, third-party snapshots, or NetBackup Data Classification.
• Storage Lifecycle Policies combine duplication features in one consolidated view
that provides inline copies, immediate or scheduled duplications, intra- or inter-
domain replication, support of some third-party snapshot technologies, and support
for NetBackup’s Data Classification feature. The only limitation with SLPs is that they
do not support BasicDisk storage units. SLPs are the focus of this lesson.
2
1
bpchangeprimary
bpduplicate –npc primary_copy –backupid backup_id
11
One backup in the NetBackup catalog is assigned as the primary copy. NetBackup uses
the primary copy to satisfy restore requests from the GUI. When using the command
line, it is possible to specify the copy to use. Normally the first backup image created
successfully for a specific backup job is the primary copy. If the primary copy expires
first, the second copy is automatically promoted to become the primary copy. If the
primary copy is unavailable and you have created a duplicate copy of that backup, select
a copy of the backup and set it to be the primary copy. Setting a backup to be the
primary copy is a function of the image catalog only; it is not a function of the media.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12
After completing this topic, you will be able to describe configuration options for
storage lifecycle policies.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Who? What?
When? How?
Where? = Backups + Duplicates
Backup Storage
Storage unit Back up to tape, Duplicate to tape, retain 6
policy 1 1 1
lifecycle retain 1 month months
Backup
policy 2 Back up to disk, Duplicate to:
Storage
Storage unit
2 2
retain until • Disk, retain 2 months
lifecycle
Backup duplicated • Tape, retain 1 year
policy 3
13
A storage lifecycle policy is an automated, reusable backup storage plan. Combined with
features inherent in storage units, and additional features such as Data Classification
with AdvancedDisk storage, SLPs allow for greater control in basing your backup strategy
on the business value of the data.
Storage lifecycle policies may also be called SLPs, storage lifecycles, or lifecycles.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Reduced risk
• Automated duplication job restarts after failures
• Less opportunity for administrative errors
• Data does not expire until copy is successfully created
More configurability
• Additional staging locations: All except for basic disk
• Additional retentions: Fixed, capacity managed, staged, and expire after copy
14
Storage lifecycles policies (SLPs) enable you to create a storage plan for similar types of
data. After an SLP is created and configured, it can be used as often as it is needed. This
reduces administration errors. SLPs also provide a single place to view the storage plan.
Prior to SLPs, administrators needed to look in several places to view similar
information.
Using an SLP guarantees that all destinations in the lifecycle are written. The
destinations are retried as necessary until the SLP is satisfied or until the backup or
duplication is cancelled by the administrator. SLP images that have not been successfully
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
written do not expire, even if they have passed their retention, until all destinations
have been satisfied.
Using SLPs, you can now write the primary copy of the (temporary) staged image to all
supported disk types (except basic disk), including tapes and virtual tape libraries (VTL).
Additionally each lifecycle destination can have its own retention.
SLPs have the following characteristics:
• Destinations: The location where the backup or duplication copy is sent.
• Destination type: This can be a backup, duplication, replication, snapshot, and
import, depending on the function that is desired.
• Retention type: Each destination in the lifecycle can be configured for a unique
retention and retention type (Fixed retention, Staged capacity managed, or Expire
after copy). Retention types are described in more detail elsewhere in this lesson.
After completing this topic, you will be able to create and initiate a storage
lifecycle policy.
15
After completing this topic, you will be able to create and initiate a storage lifecycle
policy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4
Configure any
relevant host Such as data classifications.
properties
16
The slide shows tasks that must be performed before you create storage lifecycles.
1. Design a data protection strategy. Consider these best practices:
• Do not write capacity-managed images and fixed-retention images to the same
volume in a disk storage unit. The volume may fill with fixed-retention images
and not allow the space management logic to operate as expected.
• Do not write images to a volume in a disk storage unit within a lifecycle and to
the same volume (by the storage unit) directly from a policy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Mark all disk storage units that are used with lifecycles as On demand only.
• Check any storage unit groups to ensure that fixed and capacity-managed
images cannot be written to the same volume in a disk storage unit.
2. Ensure that all physical resources have been recognized by the OS and configured in
NetBackup, including robots, tape drives, tapes, and disks.
3. Create and configure all of the logical resources, including volume pools, disk pools,
storage servers, storage units, storage unit groups, and server groups.
4. Configure the Maximum backup copies (only required in versions prior to
NetBackup 7.6.1) and Data Classification master server host properties before
creating storage lifecycles.
17
18
Note: The data classification of the backup policy and the storage lifecycle must
match. Storage lifecycles of different classifications are not available as backup
destinations in the policy.
The New Operation dialog box is displayed. The options available in the dialog box
depend upon the type of operation (backup, snapshot, import, duplication, and so on)
and the type of storage unit (tape or disk). Many of these operation types are
introduced in this lesson.
Disk
19
• Expire after copy: Select this retention type to have this backup expire after the
duplication has finished.
• Capacity managed (AdvancedDisk only): Select this retention type to enable
NetBackup to manage the space on the disk. This retention type is used in
conjunction with data classifications. The Desired cache period is the desired
time for the backup image to remain on the disk.
20
Customized windows
allow for start windows
and exclude dates
21
22
children.
Non-hierarchical duplication destinations no longer exist in current versions of
NetBackup, however earlier releases allowed you to specify a Duplication which did not
have a strictly defined parent. In these cases, a parent backup was chosen for you, as
any backup that is marked as the primary copy can provide the source for a non-
hierarchical duplication destination.
• SLP versions:
– Allow SLPs to be modified safely any time.
– Tagged within a running job (and viewed using nbstl command).
Already running jobs continue to use the corresponding SLP version.
– Cleaned up per SLP Parameters host properties, when no longer used.
23
The ability to create SLP versions lets administrators safely modify a definition without
waiting until all of the copies that are associated with the SLP have been processed.
Each copy that an SLP manages is tagged with the SLP name and the SLP version
number. These two attributes are written into the image header, in the NetBackup
image catalog. Whenever an administrator creates or changes an SLP, NetBackup
creates a new version (between 0 and n). New jobs use the most recent SLP version.
When a new job is submitted, it is tagged with the most recent SLP version number. The
processing of a copy that is associated with a version remains fixed according to that
version of the SLP definition. It is fixed at job time and does not change, unless the
administrator uses the nbstl command to modify an existing version. Old, unused SLP
versions are cleanup up according to master server host properties > SLP Parameters.
(1 month)
master_msdp_stu
NetBackup master
Client data / media server
Backup
Backup Duplicate
master_advdisk_stu master_tape_stu
(Expire after copy) (3 months)
24
This slide illustrates a scenario in which a storage lifecycle policy is used. The following
steps describe the scenario.
1. Perform a backup of a client. In this scenario the backup image is written to an
AdvancedDisk storage unit, master_advdisk_stu. The backup image created on
master_advdisk_stu has an expire after copy retention.
2. Simultaneously, another copy of the backup image is written to the deduplication
storage master_msdp_stu. The retention of the backup image created on there is 1
month.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3. After the backup job completes, the SLP causes a duplication of the backup image
that resides on master_advdisk_stu. This duplicate copy is written to a Media
Manager storage unit, master_tape_stu, and has an assigned retention of 3 months.
Note: After the duplication job has run and the copy is created on tape, the source copy
for the backup which resides on master_advdisk_stu is deleted.
25
To configure the scenario, the LAB12-console-test-slp1 backup policy uses the LAB12-
SLP1_test lifecycle policy storage. The LAB12-SLP1_test policy storage contains the
following destinations:
• A backup goes to the master_msdp_stu storage unit, with a fixed retention of 1
month.
• A backup goes to the master_advdisk_stu storage unit, with retention set to expire
after copy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
177. Parent for both backup jobs: Requests all Backup operation resources
178. Primary backup job: Writes to primary Backup operation
179. Inline copy backup job: Writes to second Backup operation
180. Duplication job scheduled by SLP:
– Requests primary Backup and Duplication operation resources
– Even though the lifecycle policy name is Lab12_SLP1_test, the prefix “SLP_” always precedes it in the Job
Policy shown in the Activity Monitor.
– Job Schedule is the SLP window: Business_Hours.
181. Image cleanup: Removes any backups with retention Expire after copy
26
When LAB12-console-test-slp1 runs, the jobs shown in the slide are initiated.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
This slide shows a storage lifecycle policy in the NetBackup Administration Console, with
the corresponding output from the nbstl –L command.
You can see from the output of nbstl on this slide that the Backup operations have a
Source listed of the client directly. The Duplication operation’s source shows the
operation from which it is to be duplicated, based on the SLP hierarchy (in this case,
Operation 1, the backup to AdvancedDisk).
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
28
• Extended image retry interval indicates, after the initial three retries, how long
NetBackup waits before an image copy is added to the next duplication job. Default:
2 hours. Minimum: 1 hour.
• Minimum size per duplication job indicates the size that the batch of images should
reach before one duplication job is run for the entire batch. The SLP only requests a
duplication job when this size is met, or until the Force interval for small job time
has passed. Default: 8 GB.
• Maximum size per duplication job determines how large the batch of images is
allowed to grow before no more images are added to the batch. Default: 100 GB.
• Force interval for small job If the minimum batch size is not reached by the time
indicated, the SLP requests a duplication job regardless. Default: 30 minutes.
* Caution: Will prevent dependent lifecycles, which may result in loss of backup copies.
29
Use the nbstlutil command to view and manage the duplication automation in
storage lifecycles. The slide shows some of the options that can be used with this
command:
• cancel: Cancels pending lifecycle operations on selected image copies. When you
cancel a specific destination, you also cancel the pending operations at destinations
that depend on the source copy from that destination. These images will not later
be considered for duplication by the lifecycle.
• inactive: Deactivates future lifecycle operations on the image copies, but retains
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
30
keep the SLP environment from getting too far behind. In the slide example, the SLPs
have not been processing the images; therefore, the backlog has built up to the point
where the Created Images equal the Unfinished Images, showing that a large backlog
exists.
Data for the SLP Backlog report is not real time, and is collected from the OpsCenter
database on a periodic basis. Because SLP processing generally takes hours, this typically
does not impact the report’s effectiveness. Most backlogs in a properly sized
environment are resolved eventually, so minute-by-minute monitoring is not a good
indication of general backlog issues. Consistent or growing backlog over the span of
days and weeks indicates that either too much data is in the SLP process, or that there is
not enough infrastructure to handle the amount of information.
After completing this topic, you will be able to explain additional benefits
and features of SLP, such as optimized duplication, Auto Image Replication,
and Data Classification.
31
After completing this topic, you will be able to explain additional benefits and features
of SLP, such as optimized duplication, Auto Image Replication, and Data Classification.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
32
The use of storage lifecycle policies (SLPs) also provide a number of other features and
benefits:
• Optimized duplication is NetBackup’s ability to take advantage of features within the
underlying storage or software to efficiently copy a backup image without having to
send all the image data, reducing the workload on the NetBackup media servers.
Optimized duplication relies on the source and target storage supporting each other,
which in most cases means the technologies must be identical. Although it can be
used in SLPs, it is also supported with other duplication features, such as the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
33
To understand optimized duplication and how to configure it, you need to understand
the prerequisites, how to perform optimized duplication, and how to control its
behavior. These issues are discussed on the following slides.
Ensure prerequisites are met
For most disk appliance types, the source and destination must be identical.
For OpenStorage vendors that support optimized duplication, refer to the OST
supported vendor for their hardware and version restrictions.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
To configure optimized duplication, one or more media servers must have credentials to
both the source and destination storage. This could be either the source or target MSDP
storage server, or a media server that is separate from both disk storage appliances. The
role of this media server is to initiate, monitor, and then finally verify the copy
operation.
34
Because optimized duplication is used by default when the prerequisites are met, no
other specific configuration needs to be performed.
When deciding to duplicate to multiple destinations, the behavior depends on the
duplication method:
• Storage lifecycle policies
In the case of SLPs, multiple optimized duplication jobs are supported, as long as
the multiple target storage locations support optimized duplication from the source
storage. A separate job is created for each of these jobs.
• Other duplication methods
With other duplication types, multiple, simultaneous optimized duplications are not
supported, and normal duplication are used for all destinations.
35
36
Introduced in NetBackup 7.1, Auto Image Replication enables the replication of backup
images from one NetBackup domain to another. This feature is enabled by using Storage
Lifecycle Policies, or SLPs, with OpenStorage Technology (OST) based storage.
Supported storage includes NetBackup deduplication, such as Media Server
Deduplication Pools (MSDP) and NetBackup appliances, as well as storage vendors that
support and are qualified for OST.
Auto Image Replication uses Optimized Duplication, which allows NetBackup to
minimize the use of wide area network (WAN) bandwidth that is normally at a premium
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
between sites. Only new, unique data is transferred between sites. After an image is
duplicated to the target domain, standard duplication copies that backup image to tape.
In this way, a vaulted copy of the backup is created without having to ship tapes.
Auto Image Replication supports various disaster recovery models, including simple
one-to-one, many-to-one and one-to-many replication. Targeted Auto Image Replication
allows selective replication of images.
Refer to the NetBackup Administrator’s Guide, or the NetBackup: Advanced
Administration course.
* The use of the term “domain” in this topic refers to NetBackup domains.
37
Auto Image Replication works by going through the following basic steps:
1. Run and create a backup image in the source domain.
2. Replicate the backup image to the target domain, generally using a method called
optimized duplication, which is supported with NetBackup deduplication and with
OpenStorage vendors, and takes advantage of the replication features in these
products. This process involves storing the backup image with the backup metadata
so that the import process on the target domain is performed quickly.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3. After the backup image, which includes the backup metadata, has been duplicated
to the target domain, the target master server imports the metadata.
Because the metadata can be easily and quickly imported, this is referred to as a fast
import. This is much preferred to the traditional, much slower method of having to
re-catalog the entire backup image.
4. Optionally, additional duplication jobs can be configured. These can be duplications
to local storage, or additional replication jobs.
Storage lifecycles Storage > Storage Lifecycle nbstl -L Manage > Storage >
Policies Storage Lifecycle Policy
38
The table on this slide summarizes how storage lifecycle information can be displayed
using the NetBackup Administration Console, NetBackup commands, and OpsCenter.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Key points
– You can now identify the duplication backup types, including inline, manual duplication, basic disk
staging, and storage lifecycle policies.
– You can describe the configuration options for storage lifecycle policies, and you can create and initiate
a storage lifecycle policy.
• Reference materials
– NetBackup Administrator’s Guide, Volume I and Volume II
– NetBackup Commands Reference Guide
– NetBackup Troubleshooting Guide
– NetBackup Vault Administrator’s Guide
– Article 100032502: Storage Lifecycle Policy (SLP) Cheat Sheet
– http://www.veritas.com/support
39
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
40
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
41
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Simultaneous copy
B. Inline copy
C. Storage life backup
D. Duplication backup
42
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. Simultaneous copy
B. Inline copy
C. Storage life backup
D. Duplication backup
The correct answer is B. An inline copy is when backup data is sent to multiple storage destination simultaneously during
a backup. In NetBackup, a duplication is when a backup image is copied to a new destination after the original backup
had already been completed.
43
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
44
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
45
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. 30 seconds
B. 1 minute
C. 5 minutes
D. Immediately
46
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. 30 seconds
B. 1 minute
C. 5 minutes
D. Immediately
47
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-48
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Managing and Protecting the NetBackup Catalog” lesson in the “Veritas
NetBackup 8.1: Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
Describe the location, and explain the importance of NetBackup
Introduction to NetBackup catalogs
catalog backups.
Describe the difference between image retention and image
Managing images
expiration, and how to import, verify, and expire images.
List the steps that are required to recover from a disaster situation,
Disaster recovery strategies and recover the NetBackup catalog using the NetBackup Catalog
Recovery Wizard.
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to describe the location, and
explain the importance of NetBackup catalog backups.
After completing this topic, you will be able to describe the location, and explain the
importance of NetBackup catalog backups.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Master server
NetBackup
catalog
NetBackup catalogs are information stores that contain information about the
NetBackup configuration and backups, including records of the files that have been
backed up and the media on which the files are stored.
The NetBackup catalogs reside on the NetBackup master server and consist of the
following components:
• The NetBackup database (NBDB) is a relational database that uses SAP SQL
Anywhere. The NBDB stores data for several NetBackup services, including media
and device data, backup image headers, authentication and authorization. Bare
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Metal Restore (BMR) data is also stored in a Sybase database if the BMR option is
used. Because the first service to use the relational database was the Enterprise
Media Manager in earlier releases of NetBackup, the database is sometimes
referred to as the EMM database.
• The NetBackup configuration files include policies, schedules, and other files used by
NetBackup. These are sometimes referred to as flat files because they are not stored
in a relational database, and are stored in simple files on the file system of the
NetBackup master server.
A critical NetBackup component is the image database, which stores backup image
metadata. This metadata is stored in two locations: the image header data is stored in
the relational database (NBDB), and the image file list is still stored as flat files in the
NetBackup configuration files. Because the image file lists contain the path to every file
backed up, this is usually the largest component of the NetBackup catalogs.
Although you can recover your data without the catalogs, doing so takes considerably
longer and involves more work than if the catalogs were available. Therefore, backing
up the catalogs efficiently and regularly is of paramount importance.
To protect your catalogs:
• Make at least two copies of the catalog backup images.
• Store one copy of the catalog backup offsite.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Database files
• DARS_DATA.db UNIX: /usr/openv/db/data
• DARS_INDEX.db Windows: install_path\NetBackupDB\data
• DBM_DATA.db
• DBM_INDEX.db
• EMM_DATA.db Configuration files
• EMM_INDEX.db
• server.conf
• JOBD_DATA.db
• databases.conf
• NBAZDB.db
• NBAZDB.log
• NBDB.db
UNIX: /usr/openv/var/global
• NBDB.log Windows: install_path\NetBackupDB\conf
• SLP_DATA.db
• SLP_INDEX.db
• vxdbms.conf
The NetBackup database (NBDB) is created during the installation of the master server.
The NBDB stores information used by the master server, and runs on SAP SQL
Anywhere.
The NBDB consists of database files, configuration files and a transaction log.
NetBackup database bp.conf or Registry entry
During installation, a VXDBMS_NB_DATA entry is created in the bp.conf file (UNIX) or
the Registry (Windows). This entry identifies the directory where NBDB.db and
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
install_path
UNIX /usr/openv/
NetBackup Windows C:\Program Files\Veritas
db
The configuration files consist of directories that also contain flat files located on the
master server disk. The directories that comprise the configuration files include:
• class: Directories that contain policy information
• client: Contains master server client attributes
• cloud: Cloud configuration files
• cltmp: Contain temporary policy information
• config: Contain information about host properties and data classification
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
images
winclient.example.com Client name Each backup has a filelist (.f) file
named using policy name,
Creation timestamp timestamp, and schedule type
1483000000
clients_to_master_bdisk_1483603201_FULL.f
clients_to_master_tape_1483548217_FULL.f
9
A critical NetBackup component is the image database, which stores backup image
metadata. The image metadata is stored in two locations:
1. The image header data is stored in the relational database (NBDB)
2. The image file list is still stored as flat files in the NetBackup configuration files area.
Because the image file lists contain the path to every file in every active backup
image, this is usually the largest component of the NetBackup catalogs.
The image file lists are located in the NetBackup configuration area, in a folder called
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
images. Under the images folder, there are subdirectories for each client that is backed
up by NetBackup, including the master server and any media servers, and additional
subfolders named after timestamps, as shown in the example on the slide.
These folder contain the following files:
• Image .f files are files that are used to store the detailed information about each
file backup.
• The .lck files are files used to prevent simultaneous updates on images.
• The db_marker.txt file is used to ensure that access to the db directory is valid
when the NetBackup Database Manager starts. Do not delete this file.
After completing this topic, you will be able to describe the difference
between image retention and image expiration, and how to import, verify,
and expire images.
10
After completing this topic, you will be able to describe the difference between image
retention and image expiration, and how to import, verify, and expire images.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bpimmedia –U [-disk|-tape]
11
When a backup job is initiated, NetBackup selects the required piece of media based on
the parameters of that specific backup job. The policy and schedule dictate the required
storage unit, volume pool, and retention level.
The Images on Media report lists all backup images for a specific NetBackup client, or
all clients. The corresponding Images on Tape and Images on Disk reports can be used
to narrow the search to a particular tape or disk storage unit.
These reports can be run using the bpimmedia command, as shown on the slide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Provides visibility
into the backup
image database
12
Select NetBackup Management > Catalog to search for backup images. You may want
to search for a backup image to:
• Verify the backup contents with what is recorded in the NetBackup catalog.
• Duplicate the backup image to create up to ten copies.
• Promote a copy of a backup to be the primary backup copy.
• Expire backup images.
•
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Media
ABC123
EOT
EOF
EOF
EOF
Image1 Image2 Image3
BH
BH
BH
• Read each block of the media
• Compare written image headers with NetBackup Catalog
NetBackup Catalog
NBDB NBDB Image database
(media ID) (header info) (.f file)
Image1 Image1.f
ABC123 Image2 Image2.f
13
NetBackup can verify the contents of a backup by reading the volume and comparing its
contents to what is recorded in the images catalog. This operation does not compare
the data on the volume with the contents of the client disk. However, it does read each
block in the image, thereby verifying that the volume is readable.
NetBackup verifies only one backup at a time and tries to minimize media mounts and
positioning time.
Most modern tape drives have built-in read-after-write (RAW) verification.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bpverify
14
3. From the list of backup images you have created, right-click the image that you want
to verify and select Verify from the shortcut menu.
You will see a Confirm Verify message window, which gives you the option to log all
files found in verified images.
4. Click OK to continue.
15
proceeds.
bpexpdate -backupid
16
Expiring the image using this procedure only expires that specific copy of the backup.
Additional copies would need to be found and manually expired individually.
Expiring a disk image removes both the entry for the image in the NetBackup image
catalog, and the backup image itself, from the disk storage unit.
Alternatively, you can use the bpexpdate command to expire a backup image (or to
change the expiration date) of a single backup:
bpexpdate -backupid backup_id –d date | 0 | infinity
[-client client_name] [-copy number] [-force]
[-M master_server[,...,]]
Preparing to import
Performing an import
17
A NetBackup master server may not have any record of the data on a piece of backup
media. This may happen if the backup has reached its retention, or if it was written by a
different NetBackup server in another NetBackup domain.
To access data in these situations requires the use of the import feature. Importing a
backup refers to the process of examining the backup on a media and importing the
metadata into the NetBackup catalog on the master server. This allows NetBackup to
access and restore from this data.
Before performing an import operation, it is important to:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Ensure that the media is available on the media server performing the import.
• Ensure the correct media ID is being used, if this is a tape. Doing a physical inventory
using the NetBackup vmphyinv command, which is described in the NetBackup
Commands Guide, determines the media ID by mounting the tape and reading the
tape header, as opposed to reading a barcode (which may be incorrect).
• Ensure that the file systems and volumes are mounted, for disk-based backups.
In prior versions of NetBackup that are no longer supported, there was compatibility for
reading Backup Exec tapes. This functionality is no longer supported. For more detail,
refer to Article 100000926: Statement of support for the importing of Backup Exec
images in NetBackup 7.x using the Backup Exec Tape Reader, found online at
http://www.veritas.com/docs/100000926.
Tape
Disk
bpimport -create_db_info
18
During an import operation, NetBackup re-creates NetBackup catalog entries for the
backups on the imported volume. Use the following procedure to initiate the import:
1. In the Administration Console, expand NetBackup Management > Catalog.
2. Select Actions > Initiate Import. The Initialize Import dialog box is displayed.
3. Complete the Initialize Import dialog box by entering the following information
a. In the Media Server field, specify the media server where the import will occur,
and that currently has access to the media with the images that are going to be
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
imported.
b. In the Image Type field, specify if it is Tape or Disk.
• For Tape, then specify the Media ID.
• For Disk, then specify the Disk Type field (Basic Disk, Advanced Disk, or
PureDisk). Depending on the disk type selected, you either need to specify
the Path (for BasicDisk), or the Disk Pool and Volume for a disk pool.
c. Click OK. The Confirm Initiate Import dialog box is displayed. Click OK to
proceed.
4. The process of reading the catalog information from the source volume begins.
bpimport
19
5. Click the Results tab to watch as NetBackup scans each image on the tape or disk to
determine if the image already exists or needs to be imported. The job is also
displayed in the Activity Monitor as an Import type. Select the import job log that
was just created to view the job results.
Note: Because it is necessary to mount and read the tape at this phase, reading the
catalog and building the list can take some time to complete.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
bpimport
20
During Phase II, you select and import images from the list of images that were
completed in Phase I.
1. In the NetBackup Administration Console, expand NetBackup Management >
Catalog.
2. Set up the search criteria to find imported images by setting the search action to
Import. Select a date range that includes the images you want to import and click
Search Now.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Note: The date range specified must encompass the date the original backup was
written, even if the image to be imported is a copy.
bpimport
21
3. Select the images you want to import and select Actions > Import.
The Confirm Import dialog box is displayed.
4. Click OK.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
22
5. To view the log, click the Results tab, and then select the import job log that was
just created.
When importing backups that have fragments on multiple tapes, do not start the Import
(Phase II) until you have run the Initiate Import (Phase I) to read the catalog for all the
tapes containing fragments. If this is not performed, the import fails with a message
such as:
Unexpected EOF or Import of backup_ID failed, fragments
are not consecutive.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
All copies of an image must be expired before the image can be imported. The import
reports that an image is bypassed if a copy already exists.
When an image is imported, the new expiration date and time of the imported image is
determined by adding the retention period associated with the image to the current
date and time. For example, if an image with a two-week retention is imported on
January 09, 2017 at 6:39 A.M, the expiration date of the imported image is January 23,
2017 at 6:39 A.M.
Task Description
Search Search for backup images.
23
The table on this slide summarizes the image-related tasks that you can perform. See
the NetBackup Administrator’s Guide for more information about these tasks.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Step Action
24
If the image database grows too large on a static UNIX partition, you can move the
image database to another partition as follows:
1. Back up the NetBackup catalogs, to ensure that you can recover image information
in case something is accidentally lost during the move.
2. Ensure that no backups are in progress using the Activity Monitor or enter:
/usr/openv/netbackup/bin/bpdbjobs
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
Step Action
25
If the image database grows too large on a static Windows partition, you can move the
image database to another partition as follows:
1. Back up the NetBackup catalogs to ensure that you can recover image information in
case something is accidentally lost during the move.
2. Ensure that no backups or restores are in progress by using the Jobs tab in the
Activity Monitor. If backup or other jobs are running, either wait for them to end or
stop them by using the Jobs tab in the Activity Monitor.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3. Stop the NetBackup services, for instance by running the bpdown command, to
prevent jobs from starting and the database from being modified while you are
moving the image database.
4. Create the new file system and optionally any directories to which you intend to
move the image information. For example:
E:\NetBackup\alternate_db\images\client_name
5. Move all files and directories to the new location. Note that if you are planning to
use the ALTPATH method of setting an alternate location, you need to move the
image files for specific NetBackup clients into a folder for that client.
installation.
After completing this topic, you will be able to configure a catalog backup
policy.
27
After completing this topic, you will be able to configure a catalog backup policy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Catalog backups
28
Backup data is vulnerable to loss during hardware and site failures, which can
compromise an organizations recovery objectives.
To protect backup data, you can configure multiple copies of your backups, and store
some of these backups offsite. This provides a level of redundancy that allows an
organization to survive many types of software, hardware, and site failures.
Additionally, the NetBackup infrastructure should also be protected, as it is critical in
being able to quickly restore an organizations data. This is best done by configuring
catalog backups, which are used to back up and recover the NetBackup catalog in the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• UNIX: /usr/openv/db/staging
• Windows:
install_path\NetBackupDB\staging
3. Back up
configuration
files
2 3
2. Back up
the NBDB
Staging
area NetBackup
configuration
1
1. Stage the NBDB, overwriting the
prior contents of the staging area
NBDB
29
Veritas best practice is to schedule catalog backups to run regularly, in case of failures
with the master server or its catalogs and databases. Additionally, run manual catalog
backups prior to and immediately after any upgrade, including patch upgrades.
This slide describes what happens during a catalog backup. After a parent job starts to
manage the entire process, the following additional jobs run:
1. A child job copies the NBDB files to the staging location, as shown on the slide.
During each catalog backup, the files in the staging area are overwritten. Until they
are overwritten, they can be used for disaster recovery.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2. A child job starts, which backs up the files from the staging directory to the storage
unit specified in the catalog backup policy. This job backs up the files in a single
stream.
3. Another child job starts, which backs up the NetBackup configuration files. This
includes the Image database, policies, configuration, and other catalogs on the
master server.
In previous versions of NetBackup, the files in the staging directory were deleted at the
end of the successful catalog backup.
The NetBackup database truncates the NBDB transaction log automatically during
database checkpoints, separate from the catalog backup schedule.
• Contains the Certificate Authority Certificate, Host ID and Hostname Certificate, encryption
keys, and database table unload data
• Used to recover master server identity during disaster recovery
DR package • Encrypted with DR passphrase
• Available in NetBackup 8.1 and later
• Example filename: NBU_catalog_1501149670_FULL.drpkg
30
Starting in NetBackup 8.1 when a NetBackup Catalog backup is performed two Disaster
Recover (DR) files are created: the DR file and the DR package.
• The DR file is the same file created in prior releases of NetBackup, and lists the
location containing the corresponding catalog backup, including locations for the
most recent Critical Policy backups.
• The DR package is included in NetBackup 8.1 and later, contains identity information
about the master server, and is used to recover a master server’s identity in the event
disaster recovery needs to be performed. Without the DR package,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
31
any frequency for resetting. Valid and invalid characters are shown on the configuration
page in the NetBackup Administration Console.
NetBackup does not validate the passphrase at the time of creation so it is strongly
recommended to use the nbhostidentity -testpasspharse command to test the validity
of the DR package and DR passphrase after the first catalog backup and any time after
changing the passphrase. The output of the command will either display “valid” or
“invalid”. For more details, refer to Article 100040029: About NetBackup 8.1 catalog
passphrases, found online at http://www.veritas.com/docs/100040029.
32
The passphrase can be changed at any time. However, when changing a DR passphrase
Veritas highly recommends that you keep track of which passphrase belongs to which
DR package as NetBackup does NOT keep record of this. The correct passphrase is
required to restore the DR package at the time the DR package was created.
During a disaster recovery of the master server, if the passphrase is lost then the
identity certificates need to be regenerated for all hosts in the NetBackup domain to re-
establish the trust connection. This is accomplished through command line. For details
on this process, refer to Article 100033743: Getting your environment up and running
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
after a disaster when the disaster recovery package passphrase is lost, found online at
http://www.veritas.com/docs/100033743.
For security reasons NetBackup catalog backups do not backup the DR package, DR
passphrase or any identity information.
33
To create a NetBackup catalog backup, create a standard backup policy, selecting NBU-
Catalog from the Policy Type drop-down list.
Select the desired storage unit from the Policy storage drop-down list. Note that if a
disk target is used, it should not be a deduplication disk target and should not reside on
the master server. This way if NetBackup or the master server is inaccessible, you are
not prevented from getting to your catalog backup.
Notice that selecting a policy type of NBU-Catalog results in a policy with three tabs:
Attributes, Schedules, and Disaster Recovery. The Clients tab is not needed because we
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
are backing up the catalog from the master server. Additionally, the Backup Selection
tab is not needed because we know what is being backed up: The NetBackup catalogs.
34
Create schedules under the Schedules tab. Full backup schedules are created as normal.
Incremental backup schedules have most of the normal options, however have an new
schedule type in addition to the Calendar and Frequency based schedules: After each
backup session. A backup session is a period of continuous backup activity, and ends
when all backup activity ceases for some period of time. This allows a catalog backup to
occur every time a set of backup jobs have completed.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
35
The Disaster Recovery tab is provides the ability to set catalog backup settings.
Creating a catalog backup involves creating disaster recovery (DR) files that provide
information on how to perform recovery, and what media is involved in that recovery.
Enter the Path where each disaster recovery image file and package can be saved on
disk, and additionally enter the logon and password information if the disk location is on
a network file system. Note: Veritas recommends saving the DR files to a network share
or a removable device, as opposed to a location on the local machine.
Optionally enter any e-mail addresses to send recovery information to, using a comma-
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
36
The screen shot on this slide shows NetBackup Activity Monitor with the catalog backup
jobs that have just completed.
Also notice that in regards to the Image Cleanup job status, if a catalog backup is not
configured, the image cleanup returns a status code of 1 (partially successful). When a
catalog backup job is configured, the image cleanup returns a status code of 0
(successful). This was put in place to give customers adequate warning when catalog
backups had not been configured.
The image cleanup job that runs periodically and returns a partial success status code of
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1 should have the following text in the job details to provide this warning:
Warning bpdbm (pid=process_ID) Hot catalog backup is not
configured for ‘master_server_name', catalog cleanup
returns partial success until hot catalog backup is
configured.
After a catalog backup policy is configured, this warning is no longer displayed.
After completing this topic, you will be able to list the steps that are
required to recover from a disaster situation, and recover the NetBackup
catalog using the NetBackup Catalog Recovery Wizard.
37
After completing this topic, you will be able to list the steps that are required to recover
from a disaster situation, and recover the NetBackup catalog using the NetBackup
Catalog Recovery Wizard.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
38
• There are additionally other disaster recovery strategies, including things such as
catalog replication with products such as Veritas Volume Replicator (VVR), or
NetBackup master server clustering with products such as Veritas Cluster Server, or
virtual machine high availability. For additional information, refer to the NetBackup
in Highly Available Environments Administrator's Guide.
39
The table on this slide shows the high-level procedure to follow to recover your
environment after a disaster, such as a full site failure. This procedure makes the
assumption that the backup data has been restored to the site, either from tapes that
have been vaulted and brought back to the primary site, or similar disk backup storage
has been made available.
This includes the following steps:
1. Reload a minimal operating system to the new systems, including the master and
media servers that are to be used to restore application and server backup data.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Command line
Use the bprecover -nbdb command to recover only NBDB.
40
The slide shows two functionally equivalent methods for performing catalog recovery.
This topic covers performing a catalog recovery using the Netbackup Catalog Recovery
Wizard.
Here are some important points regarding disaster recovery:
• Catalog recovery relies on disaster recovery information generated during the online
catalog backup. Save the disaster recovery files created by the online catalog backup
to a network share or removable device.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Configure the online, hot catalog backup policy to send an e-mail copy of the
disaster recovery information as part of every catalog backup.
• Specify the most recent disaster recovery file available, unless some form of
corruption occurred and you want to restore to an earlier state of the catalog.
• If the most recent catalog backup was an incremental backup, use the disaster
recovery file from the incremental backup. There is no need to restore the full
backup followed by the incremental backup.
• To read the media that contains the catalog backup, first configure a robot and drive
and perform a robot inventory.
• If the catalog backup media is on a remote media server, restart NetBackup on the
remote media server after the master server has been reinstalled (after the
recovery).
41
Recover the entire catalog by using the NetBackup Catalog Recovery Wizard as follows:
1. To start the NetBackup Catalog Recovery Wizard from the NetBackup
Administration Console, click Recover the Catalog.
The Welcome panel is displayed.
2. Click Next on the Welcome panel to display the Catalog Disaster Recovery File
panel.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
42
3. Specify where the disaster recovery file is stored by entering the fully qualified path
to the disaster recovery file.
Obtain the disaster recovery file path information from the disaster recovery e-mail.
In most cases, you specify the most recent disaster recovery information file
available. If the most recent catalog backup is an incremental backup, use the
disaster recovery file from the incremental backup. (There is no need to first restore
the full backup and then follow with the incremental backup.) If some form of
corruption has occurred, you may want to restore to an earlier state of the catalog.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
If the DR file is not available, refer to Article 100037884: How To: Recover the
catalog without a DR file, found online at http://www.veritas.com/docs/100037884.
Click Next. The wizard waits while NetBackup searches for the necessary media
sources. The wizard then informs you if the necessary backup ID of the disaster
recovery image is located. If the media is not located, the wizard lists which media is
needed to update the database.
If necessary, follow the wizard instructions to insert the media that is indicated and
run an inventory to update the NetBackup database. The information that is
displayed on this panel depends on whether the recovery is from a full backup or an
incremental backup.
43
4. When the required media sources are all found, click Next to display the Disaster
Recovery Method panel.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
44
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.
45
46
bpmedia -unfreeze
47
After the catalogs have been recovered, NetBackup freezes the media containing the
catalog backup. This is to prevent accidental overwriting of the final catalog backup
image.
After a successful catalog recovery, you can unfreeze media using the Administration
Console as follows:
1. Under Device and Media Management, select Media.
2. In the details pane, right-click the frozen media.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3. Select Unfreeze.
You can also use the command line to unfreeze media. Display frozen media in the
CatalogBackup volume pool by using the available_media script. The status of the
volume in the CatalogBackup volume pool is FROZEN. Enter the following command to
unfreeze the media:
bpmedia -unfreeze -m media_id -h nbu_server
• Reconfigure devices, if the device configuration differs from the restored configuration
• Configure media server override or media server failover, if necessary
– Configure master server host properties > Restore Failover
– Configure master server host properties > General Server > Media Host Override
• Deactivate any policies with automatic schedules that you do not want to have run
during recovery operations
Select all policies under NetBackup Management > Policies > Summary of All Policies, and select Action >
Deactivate
48
The slide lists some additional steps that may be useful after recovery of the NetBackup
master and media servers, and prior to the recovery of application and server backup
data.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Automated replication of backup images from one NetBackup domain to another using
storage lifecycle policies (SLP)
• Assists in designing a disaster recovery (DR) solution:
– Provides the ability to automatically vault backups offsite
– Uses optimized duplication to minimize network use
– Allows the elimination of shipping physical tapes
– Supports hub and spoke model data centers where remote offices send data to a central data center
– Combined with catalog backups, allows for easily maintained off-site copies of the catalog, to help
facilitate disaster recovery
49
Auto Image Replication is a NetBackup feature that enables the replication of backup
images from one NetBackup domain to another. This feature is enabled by using storage
lifecycle policies (SLPs) with OpenStorage Technology (OST)-based storage.
Supported storage includes:
• NetBackup deduplication: Media Server Deduplication Pools (MSDP) and NetBackup
appliances
• Storage vendors that support and are qualified for OST
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After an image has been replicated to the target domain, standard duplication can be
used to copy that backup image to tape. In this way, a vaulted copy of the backup is
created without having to ship tapes.
Auto Image Replication supports the ability to create “hub and spoke” data centers,
where remote offices send data to a central location, as well as other DR models.
50
The NetBackup Deduplication Guide describes how to perform the following tasks:
• Creating a policy to back up the MSDP catalog
• Restoring the MSDP catalog from a shadow copy
• Recovering from an MSDP storage server disk failure
• Recovering from an MSDP storage server failure
• Recovering the MSDP storage server after NetBackup catalog recovery
See the NetBackup Deduplication Guide for these specific procedures. Note that many
of these procedures may be version specific, so check for the guide specific to your
version of NetBackup. There is more detailed coverage of this topic in the NetBackup
Advanced Administration course.
Media used for catalog Reports > Tape Reports > bpimagelist
backups Tape Summary –media
Search on the –policy
CatalogBackup volume catalog_policy_name
pool. -L
51
The table on this slide summarizes how catalog-related information using the
NetBackup Administration Console, NetBackup commands, and OpsCenter.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Key points
– In this lesson you learned where the catalog backups reside and why catalog backups are important.
– You also learned the difference between image retention and image expiration, and how to import
expired images.
– Additionally, you learned how to back up your NetBackup catalogs, and how to recover them, using the
NetBackup Catalog Recovery Wizard.
– Finally, you learned know how to diagnose common catalog-related issues.
• Reference materials
– NetBackup Administrator’s Guide, Volume I and Volume II
– NetBackup in Highly Available Environments Administrator's Guide
– NetBackup Commands Reference Guide
– NetBackup Troubleshooting Guide
– http://www.veritas.com/support
52
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
53
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
54
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. According to frequency
B. According to calendar
C. After each backup session
D. All of the above
55
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. According to frequency
B. According to calendar
C. After each backup session
D. All of the above
The correct answer is D. NetBackup catalog backups can be schedule as a frequency- or calendar-based, as well as after
each backup session. Session end means that no backups are running (excluding catalog backup jobs).
56
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. True
B. False
57
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A. True
B. False
The correct answer is B. During a catalog backup, the configuration files are backed up directly to the storage unit,
however a copy of the NBDB is first placed in a staging location on the master server prior to being backed up.
58
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
59
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The correct answer is C. NetBackup performs online catalog backups, which can be sent to disk or tape, and the backup
can span multiple tapes if necessary. The catalog files that are sent to the staging location are no longer deleted after a
successful catalog backup (although prior versions of NetBackup did delete the staging files after a successful catalog
backup).
60
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
13-61
Not for Distribution
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Optimizing File System Backups” lesson in the “Veritas NetBackup 8.1:
Administration” course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Topic Objective
File system backup challenges Discuss solutions to today’s backup challenges.
Optimizing file system backups Enable NTFS and VxFS change logs, and synthetic full backups to
optimize file system backups.
Optimizing file system backups with Configure and manage NetBackup Accelerator.
NetBackup Accelerator
Using multiple data streams Configure a policy to take advantage of multiple data streams.
Optimizing tape drive performance Configure backups for optimum tape drive performance using
using multiplexing multiplexing.
Handling busy files on UNIX and Configure the way that NetBackup handles busy files on UNIX and
Windows file systems Windows, including using Windows Volume Shadow-copy Services
(VSS).
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After completing this topic, you will be able to discuss solutions to today’s
backup challenges.
After completing this topic, you will be able to discuss solutions to today’s backup
challenges.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The table on this slide lists some of the challenges that administrators face and the
solutions that NetBackup has to offer. Some of these solutions are discussed in the
topics of this lesson. Some topics may be covered in more detail elsewhere, such as the
appropriate NetBackup documentation for that feature, and the NetBackup Advanced
Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Restores the files that existed in the folders, during a TIR restore
– TIR does not restore deleted files.
– Normal restores will restore files that were deleted but had existed in the prior full or prior incremental
backups.
• Makes a list of the files that are in each directory at the time of backup
• Places list in a separate TIR file, which is backed up with the backup image
• Supported policy types: MS-Windows, Standard, NBU-Catalog
• Can be enabled with move detection
The purpose of True Image Restore is to ensure that when a full restore is performed
(which includes the last full backup plus all incrementals up to the recovery point),
NetBackup restores only those files that were present in the file system at the time of
the last backup. In other words, files that were deleted prior to the last backup in the
selected backup set, will not be restored. A normal restore would restore those files.
TIR guarantees that the restore will not overflow the file system during the restore, as a
normal restore may try to restore more files than ever existed in the file system at one
time, since it includes deleted files. Additionally, the user will not find files that he or
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The example in the slide shows a series of backups starting with a full backup on Sunday
followed by daily incremental backups. The files listed in each daily column show the
files in the file system and the actions performed on the file: modified, deleted, created
or left unchanged.
In the TIR information table, each column contains a list of the files that are present in
the file system at the time of each backup. These are the files that will be included in
the TIR file for that backup.
On Saturday you are asked to perform a full restore of the file system with Friday as the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
recovery point. To do this you will need the Sunday full backup and each of the
incremental backups through Friday.
If you select the Normal Backups restore type, the files shown in the first column are
the files that would be restored without using TIR. The files that are restored include
files that were deleted prior to the backup on Friday.
If you select the True Image Backups restore type, the files shown in the second column
are the files that would be restored using TIR. The files that are restored are those that
were listed in the TIR file for the Friday backup. Any files that were not present in the
file system on Friday will not be restored.
After completing this topic, you will be able to enable NTFS and VxFS
change logs, and synthetic full backups to optimize file system backups.
After completing this topic, you will be able to enable NTFS and VxFS change logs to
optimize file system incremental backups.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Even though an incremental backup backs up only those files that have changed,
NetBackup still has to examine every file in the file system to determine which files have
changed. This may involve examining millions of files to determine that only one file
needs to be backed up, which is unnecessarily time consuming.
One way to optimize incremental backups is to take advantage of change tracking logs
which are offered as a feature by some file systems. These logs record which files have
been modified or added since the last backup. With the log in place, NetBackup no
longer has to examine each file, instead it looks at the log file and backs up only those
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Both of these log types require some configuration within NetBackup and at the file
system level.
11
NetBackup can be configured to monitor the Windows Change Journal and use the
information discovered within the Change Journal during backups. To do this,
NetBackup will create and maintain its own databases with data mined from the Change
Journal. NetBackup will then use its databases to assist in the discovery of files and
directories that have been changed between backups.
To configure NetBackup to monitor the Change Journal, from the Client Properties for a
client, expand Windows Client and select Client Settings. Mark the Use Change Journal
check box. This needs to be done individually for each NetBackup Windows client.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
After enabling Use Change Journal, there will be a period of time before the Windows
Change Journal data can actually be used during backup. NetBackup requires a brief
period of time to establish its own change journal databases. If a backup is executed
during this time, error messages will be logged to the ‘Job Details’ indicating the reason
why the change journal data could not be used.
This option works together with the Use accelerator policy attribute and the
Accelerator forced rescan schedule attribute, discussed elsewhere in this lesson.
Week 1 S M T W Th F Sa
Week 2 S M
Synthetic full generation takes place on the media server, any
time before the next incremental on Monday night.
Client + =
Backup 1. Baseline 2. Incremental 3. Synthetic full
schedule: full backup backups backup
Mon 21:00 Fri 21:00
Time of Mon 07:30
Tue 21:00 Sat 21:00
backup: Sun 21:00 Wed 21:00 Sun 21:00 (Recorded time:
Thu 21:00 Sun 21:00:01)
12
The synthetic full backup feature eliminates the need to perform full backups of a client
machine for supported resource types.
1. During week one, perform a full backup, also known as a baseline backup. This is a
normal full backup operation.
2. Between this first full backup and the schedule for the next full backup, perform
incremental backups on the changes that occur. This is a normal backup procedure
and is usually performed daily.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3. During the next schedule for a full backup, instead of running a normal full backup,
run an incremental backup. In the example on the slide, instead of running a full
backup on the second Sunday at 9 P.M., an incremental backup was run.
4. Some time between this last incremental backup (on Sunday night, in the example)
and the next incremental backup (on Monday night), a synthetic full backup is run.
The synthetic full backup operation occurs on the media server, leaving the client free.
Because the synthetic full backup is executed on the media server without accessing the
client machine, it can be performed outside of the time-critical backup window,
reducing the overall backup window and associated network bandwidth requirements.
The newly created synthetic full backup replaces the baseline full backup and becomes
the baseline full backup for subsequent synthetic full backup operations.
Set Collect true image restore information with move detection on the
policy:
2. Configure TIR
13
After completing this topic, you will be able to configure and manage
NetBackup Accelerator.
14
After completing this topic, you will be able to configure and manage NetBackup
Accelerator.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15
NetBackup Accelerator is a licensed NetBackup feature that increases the speed of full
backups by using platform-agnostic file system change tracking track logs on the client
to identify changes that have occurred since the last backup. During an accelerator
enabled backup only the changed data are transferred to the deduplication storage .
On the storage, a new optimized synthetic full backup is created by combining the
changed data with pointers to the unchanged data from previous backups. This process
removes the need to transfer all the client data across the network.
This methodology uses less network bandwidth and reduces the overhead on client
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Versions NetBackup 7.5 or later for master servers, media server, and clients
16
The slide lists the requirements for NetBackup Accelerator. The feature is supported
starting in NetBackup 7.5 and later, and requires that all servers in the backup path
(master servers, media servers, and clients) are running a minimum of NetBackup 7.5.
Although the Windows Change Journal is not required, it can configured to work with
NetBackup Accelerator and additionally improve performance.
Note that OST vendors qualified for NetBackup Accelerator support are listed in the
Hardware Compatibility List. Refer to the NetBackup Master Compatibility List, found
online at http://www.netbackup.com/compatibility. Those that support Accelerator for
file and folder backups will show ”Accelerator”, and those that support Accelerator for
VMware will show “Accel_VMware”. Recent versions of NetBackup also support
Accelerator for additional data types, so you may also see “Accel_NDMP”, “Accel_Hyper-
V”, and possibly others in your NetBackup release.
14-16
How NetBackup Accelerator works
17
14-17
2. The client then sends a data stream to the media server consisting of the data for
the changed segments of each file and the metadata for the unchanged file
segments. This metadata will describe the backup ID and the data extents which
contain the unchanged segments.
3. The media server then creates a new optimized synthetic full backup by combining
each file’s changed segments with pointers to the file’s unchanged segments from
previous backups. Upon completion, there is a new backup image on the storage.
To summarize, only changed files are open and read, and only changed data segments
are sent to create the new backup image.
In addition, only changed file catalog information is sent, and the NetBackup catalog
backup image is also synthetically created reducing the meta data sent with each
backup.
14-18
NetBackup Accelerator operation modes
Operation
Windows UNIX Description
mode
• Uses the client track log to identify changes to the file system between
backups
Standard ✓ ✓ • Is enabled with the Use accelerator option under the backup policy
Attributes tab
• Uses checksums of the file contents during the backup for change
detection to establish a new baseline for the next Accelerator backup
Accelerator
forced rescan ✓ ✓ • Results in a slower backup
• Enabled with the Accelerator forced rescan option under the policy
Schedules tab
19
The standard operation mode uses the client track log to identify which files have
changed and exactly which segments of those files have changed. This functionality is
enabled by selecting the Use accelerator option under the backup policy attributes tab.
NetBackup 7.5 introduced a new client property called Use Change Journal to be used
in conjunction with the Accelerator feature. When this option is enabled, bpinetd.exe
generates a custom Change Journal Database which depends on the Windows NTFS or
ReFS change journal. The NetBackup generated database files are located on the root of
each lettered volume. These files are used to quickly identify which files have changed
since the previous backup. The use of the change journal is enabled by going to the Host
Properties on the master server and selecting Clients > Windows Client > Client
Settings and selecting the Use Change Journal option.
When selected, Accelerator forced rescan causes NetBackup Accelerator to use
checksums of the file contents during the backup for change detection to establish a
new baseline for the next Accelerator backup. This will cause the backup to run slower.
This feature is enabled with the Accelerator forced rescan option under the policy
Schedule tab.
14-19
Configuring NetBackup Accelerator
20
The accelerator feature is enabled for a policy by selecting the Use Accelerator option in
the policy attributes. During the first backup after the feature has been enabled, a track
log will be created on each of the clients configured in the policy. The track log will be
specific for the policy, client and backup selections.
14-20
Optionally use the Windows Change Journal
21
When the Use Change Journal option and the Use Accelerator are enabled together,
bpinetd will create the NetBackup change log databases to monitor the Windows NTFS
or ReFS change journal for changes in the file system metadata and to determine which
files are to be included in the backup. The bpbkar32 process will use this information to
create the list of files that need to be backed up, eliminating the need to examine each
file in the volume and speeds up the backup. This behavior is discussed in more detail
in a prior topic.
This option works together with the Use accelerator policy attribute and the
Accelerator forced rescan schedule attribute.
14-21
Job detail messages related to NetBackup Accelerator and NTFS
change journal
Without NetBackup Accelerator or Use change journal enabled
...
archive bit processing:<disabled>
not using change journal data for <E:\data>: not configured for use
22
During a backup, the Detailed Status report in the Job Details will display various
messages depending on what feature is or is not enabled for that backup.
The slide shows the messages displayed when:
1. Neither the Use Accelerator nor the Use Change Journal features are enabled.
2. Only the Use Accelerator feature is enabled.
3. Both the Use Accelerator and Use Change Journal features are enabled.
Additional messages will be displayed if errors are encountered during the backup.
An example of a the full Job Details from an incremental backup job with both
NetBackup Accelerator and the Use change journal setting, is provided here, and
continues on the next page:
Dec 14, 2016 1:42:22 PM - Info nbjm (pid=2981) starting backup job (jobid=145)
for client console.example.com, policy LAB14-test-accelerator, schedule diff
Dec 14, 2016 1:42:22 PM - Info nbjm (pid=2981) requesting STANDARD_RESOURCE
resources from RB for backup job (jobid=145, request id:{0C9B33A2-C22D-11E6-
A149-9851E32BCF38})
Dec 14, 2016 1:42:22 PM - requesting resource master_msdp_stu
Dec 14, 2016 1:42:22 PM – requesting resource
lnxmaster.example.com.NBU_CLIENT.MAXJOBS.console.example.com
Dec 14, 2016 1:42:22 PM - requesting resource
lnxmaster.example.com.NBU_POLICY.MAXJOBS.LAB14-test-accelerator
Dec 14, 2016 1:42:22 PM - granted resource
lnxmaster.example.com.NBU_CLIENT.MAXJOBS.console.example.com
Dec 14, 2016 1:42:22 PM - granted resource
lnxmaster.example.com.NBU_POLICY.MAXJOBS.LAB14-test-accelerator
14-22
Dec 14, 2016 1:42:22 PM - granted resource
MediaID=@aaaai;DiskVolume=PureDiskVolume;DiskPool=master_msdp_dpool;Path=Pur
eDiskVolume;StorageServer=lnxmaster.example.com;MediaServer=lnxmaster.exampl
e.com
Dec 14, 2016 1:42:22 PM - granted resource master_msdp_stu
Dec 14, 2016 1:42:22 PM - estimated 0 kbytes needed
Dec 14, 2016 1:42:22 PM - Info nbjm (pid=2981) started backup
(backupid=console.example.com_1481740942) job for client
console.example.com, policy LAB14-test-accelerator, schedule diff on storage
unit master_msdp_stu
Dec 14, 2016 1:42:22 PM - started process bpbrm (pid=9508)
Dec 14, 2016 1:42:24 PM - Info bpbrm (pid=9508) console.example.com is the host
to backup data from
Dec 14, 2016 1:42:24 PM - Info bpbrm (pid=9508) reading file list for client
Dec 14, 2016 1:42:24 PM - Info bpbrm (pid=9508) accelerator enabled
Dec 14, 2016 1:42:25 PM - connecting
Dec 14, 2016 1:42:26 PM - Info bpbrm (pid=9508) starting bpbkar on client
Dec 14, 2016 1:42:26 PM - connected; connect time: 0:00:00
Dec 14, 2016 1:42:29 PM - Info bpbkar (pid=5176) Backup started
Dec 14, 2016 1:42:29 PM - Info bpbrm (pid=9508) bptm pid: 9569
Dec 14, 2016 1:42:29 PM - Info bpbkar (pid=5176) change time
comparison:<enabled>
Dec 14, 2016 1:42:29 PM - Info bpbkar (pid=5176) accelerator enabled backup,
archive bit processing:<disabled>
Dec 14, 2016 1:42:29 PM - Info bpbkar (pid=5176) will attempt to use change
journal data for <E:\data>
Dec 14, 2016 1:42:30 PM - Info bptm (pid=9569) start
Dec 14, 2016 1:42:30 PM - Info bptm (pid=9569) using 262144 data buffer size
Dec 14, 2016 1:42:30 PM - Info bptm (pid=9569) using 30 data buffers
Dec 14, 2016 1:42:30 PM - Info bptm (pid=9569) start backup
Dec 14, 2016 1:42:30 PM - Info bptm (pid=9569) backup child process is pid 9573
Dec 14, 2016 1:42:30 PM - begin writing
Dec 14, 2016 1:42:49 PM - Info bpbkar (pid=5176) using change journal data for
<E:\data>
Dec 14, 2016 1:42:49 PM - Info bpbkar (pid=5176) accelerator sent 3066880 bytes
out of 3063808 bytes to server, optimization 0.0%
Dec 14, 2016 1:42:49 PM - Info bptm (pid=9569) waited for full buffer 2 times,
delayed 1221 times
Dec 14, 2016 1:42:49 PM - Info bptm (pid=9569) EXITING with status 0 <---------
-
Dec 14, 2016 1:42:49 PM - Info lnxmaster.example.com (pid=9569)
StorageServer=PureDisk:lnxmaster.example.com; Report=PDDO Stats for
(lnxmaster.example.com): scanned: 2995 KB, CR sent: 1638 KB, CR sent over
FC: 0 KB, dedup: 45.3%, cache disabled
Dec 14, 2016 1:42:49 PM - Info bpbrm (pid=9508) validating image for client
console.example.com
Dec 14, 2016 1:42:50 PM - Info bpbkar (pid=5176) done. status: 0: the requested
operation was successfully completed
Dec 14, 2016 1:42:50 PM - end writing; write time: 0:00:20
the requested operation was successfully completed (0)
14-23
Client track log files details
• Location on client:
– UNIX: /usr/openv/netbackup/track/master_server/
storage_server/client/policy_name/backup_selection
– Windows: install_path\NetBackup\track\master_server\
storage_server\client\policy_name\backup_selection
24
After the Use Accelerator feature is enabled in the NetBackup policy it is necessary to
run a full backup. This full backup will be a standard full backup. During the backup a
client track log will be created and information about all of the files in the full backup
will be logged in the track log. Subsequent backups will use the track log to determine
what file segments have changed and need to be backed up. Also, the track log will be
used to determine what file segments have not changed, and this information will also
be transferred to the storage. The information about what has changed and what has
not changed will be used to create the optimized synthetic backup.
The track log is located on the client in the netbackup directory and is unique for each
client, policy and backup selection for that policy. Because of this, if a client is in more
than one policy , a track log will be created for each instance of that client in the
different policies. The file path for the track log ensures that the track logs are unique.
The slide shows the full track log path for UNIX and Windows clients.
The size of the track log will vary depending on the number of files and the total amount
of used disk space. The slide shows a formula for estimating the size of a client track log.
To change the track log location, refer to Article 100038114: How to redirect the
NetBackup Accelerator track log to a different location, found online at
http://www.veritas.com/docs/100038114.
14-24
Using NetBackup Accelerator with additional policies
14-25
NetBackup FlashBackup
• Enables backups of raw partitions with the ability to restore individual files.
– Reads the entire disk, block by block, whether they contain data or are empty disk blocks.
– Works best when the file system contains a large number of files, and is predominately full
• Configured with FlashBackup and FlashBackup-Windows policy types.
26
FlashBackup is a policy type that combines the speed of raw-partition backups with the
ability to restore individual files. The features that distinguish FlashBackup from other
raw-partition backups and standard file system backups are these:
• Increases backup performance as compared to standard file-ordered backup
methods. For example, a FlashBackup of a file system completes faster than other
types of backups when the file system contains a large number of files, and if most
of the file system blocks are allocated.
• Enables restore of individual files from raw-partition backups.
• Backs up the following file systems: VxFS (Solaris, HP, Linux, AIX), ufs (Solaris), Online
JFS (HP), and NTFS (Windows).
• Supports multiple data streams, to further increase the performance of raw-
partition backups when multiple devices are in the Backup Selections list.
For a complete list of supported platforms, snapshot methods, and data types, see the
NetBackup Snapshot Client Compatibility, found online at
http://www.netbackup.com/compatibility.
Restoring from a FlashBackup policy is the same as for any other backup. In the Backup,
Archive, and Restore interface, set the policy type to FlashBackup for UNIX clients and
FlashBackup-Windows for Windows clients.
A FlashBackup (or FlashBackup-Windows) backup supports both individual file restore
and raw partition restore. You can do either type of restore from the same backup. To
restore individual files, select Normal Backups on the Restore Files tab; to restore an
entire raw partition, select Raw Partition Backups.
14-26
Comparing NetBackup Accelerator and FlashBackup
NetBackup NetBackup
Issue
Accelerator FlashBackup
Backs up empty space:
Backup capacity Does not back up empty space • Efficient for relatively full file systems
• Not efficient for empty file systems
Compatibility Broad file system support More restrictive file system support
27
Both NetBackup Accelerator and NetBackup FlashBackup may significantly improve the
performance of large file system with many files. The question of which feature to use
may arise. The answer to that question will depend on the characteristics of your client
and file system.
The slide covers some general guidelines based on file system properties:
• Backup capacity: NetBackup Accelerator simply tracks and backs up changed files.
FlashBackup, however, backs up the entire raw device, which means even empty
blocks in the file system are backed up. File systems that are not relatively full may
require long backup times due to these empty blocks.
• Compatibility: NetBackup Accelerator has broad file system support. FlashBackup
has more restrictive support, and doesn’t support encrypted file systems such as
deduplicated NTFS, and ReFS.
• Change rate: Although NetBackup Accelerator works well for normal file change
rates of file systems, for file systems with very high change rates FlashBackup may
work more efficiently.
• Full recovery: NetBackup Accelerator does not provide any advantage to full
recovery, as it is impacted by restoring the metadata for individual files, and
therefore time consuming when restoring all files. FlashBackup does have an
advantage in that raw data recovery is extremely fast, when restoring the entire data
set.
14-27
Topic: Using multiple data streams
After completing this topic, you will be able to configure a policy to take
advantage of multiple data streams.
28
After completing this topic, you will be able to configure a policy to take advantage of
multiple data streams.
14-28
Allowing multiple data streams
Client
File system 1 Job #1
29
Multiple data streams is a policy setting which allows NetBackup to create separate
backup jobs for entries in the backup selection list. This functionality is enabled by
marking the Allow multiple data streams check box on the policy’s Attribute tab. The
jobs are in separate data streams and can run concurrently.
Whether multiple backup jobs start for each client and how the backup selections are
divided into separate jobs are determined by the directives that you specify in the
backup selections list. The total number of streams and how many can run concurrently
are determined by the number of available storage units, multiplex settings, and the
maximum jobs parameters.
There are two main advantages to multiple data streams: independent data streams and
increased backup speed.
Because each stream is treated as a separate job, the data streams are independent. If
one of the streams or jobs fails, the other job is unaffected and can still complete
successfully. Only the failed jobs need to be restarted.
The other advantage of multiple data streams is increased backup speed, which occurs
when the multiple jobs can run concurrently. This means that, in theory, twice the
amount of data can be backed up in half the time. However, a reduction in backup
speed is also possible, for example, when the jobs are both running concurrently and
accessing the same source disks.
14-29
Configuring the jobs per client settings
30
By default, NetBackup allows only one job to run at a time for an individual client. In the
case where two backup policies run simultaneously for the same client, this may
protection you from disk thrashing that would cause bad performance.
However, if you want to take advantage of performance benefits by having multiple data
streams, than you will need to override this default behavior.
The Maximum jobs per client setting (found in the master server host properties under
the Global Attributes tab) has a default value of 1. Change this value to be the
maximum number of concurrent jobs you want to allow for any client in your
environment.
To change the number of jobs for an individual client, modify the Maximum data
streams setting, which is found under the master server host properties under Client
Attributes. Add the client to the Clients list, and then modify the Maximum data
streams parameter by checking the box, and then setting the desired value.
14-30
Job behavior with and without multiple data streams (MDS)
• One job is created for each client in the • For each client, one job is created for
policy. each backup selection.
• All files in the backup selections are • Backup selections can be grouped into
backed up in a single stream. jobs using a special directive.
• Parent jobs are used to manage the
overall backup for a client.
Without multiple data streams With multiple data streams
Windows client:
Job 1 (Parent job)
Job 2
Job 1 Job 3
Job 4
UNIX client:
Job 5 (Parent job)
Job 6
Job 2 Job 7
Job 8
31
Parallel backup streams from a single client can significantly improve backup
performance. Parallelism is enabled by selecting Allow multiple data streams in the
policy attributes. Parallel data streams are managed within the backup selections list
definition.
The number of data streams that can be created and queued depends on the:
• Directives included in the Backup selections list of the policy
• Limit jobs per policy parameter for the policy
• Maximum jobs per client global attribute
Note: You can override this attribute on a per-client basis by using the
bpclient -max_jobs number command option.
The number of jobs that are displayed in the Activity Monitor is one for each stream for
a specific client, as well as a parent job that manages the streams for that client.
14-31
When to use multiple data streams
• When different backup selections share the same physical disk, as multiple
data streams may decrease performance.
• If network or drive performance is affected adversely.
32
Multiple data streams can reduce the time for large backups. The reduction is achieved
by splitting the data to be backed up into multiple streams, and then processing those
streams concurrently by the same, or different, backup storage destinations.
Additional benefits are reduced retry times in the case of failures, as each backup
selection can be sent as a separate stream, and an individual backup stream failure does
not impact the other backup streams.
As you fine-tune multiple data streams, it is very easy to reduce performance instead of
improving it by inadvertently enabling multiple data streams for multiple data sets that
reside on a single disk. This results in the disk “thrashing” as the backups are performed.
Overall performance in this case is often worse than if the systems on the disk were
backed up sequentially.
Enabling multiple data streams produces more concurrent backup jobs, which in turn
use additional network bandwidth and require more tape drives (or a higher level of
multiplexing). Use caution you do not overwhelm your network environment.
Note that if you want to take advantage of independent data streams for individual
backup job restarts, but do not want parallel backup jobs, simply limit the number of
concurrent jobs using the maximum jobs per policy, or the storage unit settings.
14-32
Configuring multiple data streams: Example 1
The number of streams determined by the Backup Selections list.
3 disk drives
Windows
client
C:\ E:\
4 jobs
L:\ 225 – Parent
226 – Child with C:\Data
227 – Child with E:\Data
228 – Child with F:\Data (waiting for drive)
33
The number of data streams can be established using a list of file paths, optionally with
wild cards. Each path defined or expanded by a wild card is placed in its own data
stream.
In the example on this slide, the Allow multiple data streams check box is marked
under the Attributes tab. The Backup Selections list contains three disk drives: C:\, E:\
and L:\. The Allow multiple data streams option together with the list of three disk
drives will generate four jobs in the Activity Monitor: one parent job and one job for
each drive or mount point.
Auto-discovery streaming mode is invoked if the Backup selections list contains either
the ALL_LOCAL_DRIVES directive or wildcards (without the NEW_STREAM directive). In
this mode, the Backup selections list is sent to the client, which preprocesses the list
and splits the backup into streams as follows:
• For ALL_LOCAL_DRIVES directive, NetBackup backs up the entire client, with each
drive volume (Windows) or mount point (UNIX) into its own backup stream.
• If wildcards are used, the expansion of the wildcards results in one stream per
wildcard expansion.
If the Backup selections list contains neither ALL_LOCAL_DRIVES nor wildcards, auto-
discovery mode is not used. In this case, the server performs the preprocessing (rather
than the client) and each Backup selections list entry becomes a separate stream.
14-33
Configuring multiple data streams: Example 2
The number of streams determined by the Backup Selections list.
NEW_STREAM directive
Windows
client
C:\ E:\
3 jobs
L:\ 229 – Parent
230 – Child with C:\Data and E:\Data
231 – Child with L:\Data
34
In the previous example we backed up three drives in three separate streams. If C:\ and
E:\ were logical partitions on the same physical disk you would not want to back them
up in separate streams. Doing so could cause excessive head movement on the drive as
it attempts to satisfy simultaneous read requests from different drive locations and
possibly result in poorer backup performance. The better method would be to put
drives C:\ and E:\ into one stream and the L:\ drive in a separate stream.
This is referred to as administrator-defined streaming mode, and can be accomplished
by using the NEW_STREAM directive.
Use of the NEW_STREAM directive follows these rules:
• The first use of this directive must be on the first line of the Backup selections list.
• A backup is split into a separate data stream at each point in the backup selections
list where the NEW_STREAM directive occurs. All file paths defined between
NEW_STREAM directives appear in the same data stream. The end of each stream is
defined by the start of a new stream (the NEW_STREAM directive).
• The last stream in the list is terminated by the end of the Backup selections list. A
NEW_STREAM directive is not required.
14-34
Configuring multiple data streams: Example 3
The number of streams determined by the Backup Selections list.
ALL_LOCAL_DRIVES
Windows directive
client
10 jobs
232 – Parent
C:\ H:\
233 – Shadow Copy Components
E:\ I:\ 234 – C:\ 238 – I:\
F:\ J:\ 235 – E:\ 239 – J:\
236 – F:\ 240 – K:\
G:\ K:\ 237 – G:\ 241 – H:\
(All drives on client)
35
The example in the slide shows a backup using the Allow multiple data streams option
combined with the ALL_LOCAL DRIVES directive in the Backup Selections list. The client
has nine local drives, each of which is backed up in a separate stream.
The ALL_LOCAL_DRIVES directive backs up all local and SAN attached disk drives
(Windows) and mounted file systems (UNIX). Drives using removable media are
automatically excluded as are NFS mounted file systems.
Using the ALL_LOCAL_DRIVES directive ensures that all of a client’s disks and file
systems are backed up even if new disks are added between backups.
Using ALL_LOCAL_DRIVES and Allow multiple data streams follows these rules:
• Can only be used for Standard and MS-Windows policy types.
• A new stream (backup job) is created for each disk drive or file system present on
the client.
• On Windows: An additional, separate stream is created to back up the System State
or Shadow Copy Components (depending on the client’s Windows version).
• File systems that are in a client’s exclude list may cause a backup job to appear in
the Activity Monitor but no files will be backed up. Refer to Article 100000779 for
details, found online at http://www.veritas.com/docs/100000779.
14-35
Topic: Optimizing tape drive performance using
multiplexing
After completing this topic, you will be able to configure backups for
optimum tape drive performance using multiplexing.
36
After completing this topic, you will be able to configure backups for optimum tape
drive performance using multiplexing.
14-36
Writing backups using multiplexing
Disk
Media server
Client B Removable media
Disk
Client C
MH BH BH BH
Disk
Tape contains media header (MH), backup headers (BH),
and multiplexed (interleaved) images from each client.
37
NetBackup multiplexing sends concurrent backups from one or several clients to a single
storage device. NetBackup multiplexes the backups onto the media. Multiplexed and
unmultiplexed backups can reside on the same volume.
No special action is required to restore a multiplexed backup. NetBackup locates the
media and restores the requested backup.
• Slow networks and slow clients
The parallel data streams take advantage of whatever network capacity is available.
• Many short backups (for example, incremental backups)
In addition to providing parallel data streams, multiplexing reduces the time each
job spends waiting for a device to become available, and, therefore, better uses the
transfer rate of storage devices.
It is important to note that multiplexing can have an effect on restore times. This effect
can be positive or negative depending on the number of interleaved images, the type
and number of restores, and whether those restores are being performed concurrently.
Ensure that you use testing to determine the maximum effective multiplexing level that
still supports your backup and restore requirements.
14-37
Configuring multiplexing
• Set multiplexing on both the storage unit and the schedule:
Setting Defaults Why set MPX here?
38
Multiplexing must be set in two places in the NetBackup configuration: the storage unit
and the policy schedule. Note that if you change these values, the changes do not take
effect until the next time a schedule runs.
• The Maximum multiplexing per drive setting for a storage unit specifies how many
backups NetBackup can multiplex onto any single drive in the storage unit. You set
this value for each storage unit. The number can range from 1 through 32, where 1
is the default and specifies no multiplexing. The maximum number of concurrent-
backup jobs that NetBackup is allowed to attempt equals the sum of the concurrent-
backup jobs that can run on the storage units. Choose a value based on the ability of
your media server to handle parallel jobs. Testing may be required to find an
optimum value.
• The Media multiplexing setting on a policy’s schedule also limits how many streams
can be interleaved for a multiplexed job, where the default is set to 1 (no
multiplexing). This allows you to set the multiplexing ability at the storage unit, but
restrict it for specific backup policies and schedules.
To reduce the impact on restoring individual files from multiplexing backup, set a
fragment size on the storage unit. This is set in kilobytes (KB). A rule of thumb can be
the amount of data a drive can write in 10 minutes
14-38
Topic: Handling busy files on UNIX and Windows file
systems
After completing this topic, you will be able to configure the way that
NetBackup handles busy files on UNIX and Windows, including using
Windows Volume Shadow-copy Services (VSS).
39
After completing this topic, you will be able to configure the way that NetBackup
handles busy files on UNIX and Windows, including using Windows Volume Shadow-
copy Services (VSS).
14-39
Handling busy files on UNIX clients
bp.conf options:
BUSY_FILE_PROCESSING
BUSY_FILE_ACTION
40
During backups, NetBackup may encounter what is referring to as busy files. On some
operating systems, a busy file – a file that is currently in use by an application or process
– may prevent copying and backing up the data.
On UNIX and Linux, busy files do not normally cause issues, however there are facilities
in NetBackup to customize the behavior when encountering files that can’t be backed
up.
Configure busy-file settings for UNIX clients using the NetBackup Administration Console
under client host properties > UNIX Client > Busy File Settings. Set the appropriate
actions.
Alternatively, you can configure busy-file processing as follows:
1. Add the BUSY_FILE_PROCESSING option to the client’s
/usr/openv/netbackup/bp.conf file on the master server. This enables
busy-file processing.
2. Add other busy-file options to control the processing of busy files. These other
options can exist in both the client’s bp.conf file and the user’s
$HOME/bp.conf file. The user’s bp.conf file takes precedence when the
options are in both places.
Different users on the same client can have different configurations for that client. In
this case, these configurations are saved in the $HOME/bp.conf file.
14-40
Handling busy files on Windows clients
Add clients to
customized settings
41
On Windows, busy files can often cause NetBackup to not have access to a file, and
result in status code 1 errors for backups. Open file backup options, which allow for
busy file processing, are set for each client in the Client Attributes section of the master
server host properties. List the clients for which you want to control the open file
backup options in the Clients section of this dialog box. After the client is added to the
Clients list, you can manipulate the settings. Note that by default no clients appear in
this list, and it is the responsibility of the administrator to add clients here manually.
In current versions of NetBackup, the default snapshot provider used for Microsoft
Windows clients is Volume Shadow Copy Service (VSS), which is provided by Microsoft.
Snapshot usage and error control settings are set here. Individual drive snapshot usage
takes a snapshot of each item in your files list individually. Global drive snapshot usage
takes a single snapshot of all items in your files list together. When using VSS, consider
how snapshots of drives are taken for each client when making this setting. Snapshot
error control can be set to either abort a backup when a snapshot fails, or disable the
snapshot for that backup and continue when a snapshot operation fails.
NetBackup versions prior to version 7.x used the Veritas Snapshot Provider (VSP) as the
default method of backing up open and active files on Microsoft Windows clients. Refer
to the appropriate NetBackup documentation for information on VSP, or using it with
older Windows versions that do not support VSS.
14-41
VSS configuration tips
42
Microsoft Volume Shadow Copy Service (VSS) is supported on systems running Windows
Server 2003 and later. VSS runs on various Windows client operating systems, but
cannot be configured or customized on all Windows versions. Third-party software
vendors provide additional components that work in conjunction with VSS.
Specifications for configuration and use of VSS differ according to the nature of the
hardware on which it is running, the purpose of the machine, and many other
configuration factors.
VSS shadow copies for different volumes are set through the Disk Management utilities
of the Windows server on which they are installed. An example of the Shadow Copies
settings are shown on this slide. Shadow Copy settings can also be made from the
command line using the vssadmin utility. The vshadow utility is also included in
Software Deployment Kits for Windows Vista and later versions, such as Windows 2008.
Either of these utilities can be used from the command line to configure VSS.
It is not possible to make general recommendations for the configuration and use of
VSS, but the following are useful general tips:
• Create the shadow copy for a particular volume on a separate volume. This is so that
a shadow copy does not fill up its own volume.
• Do not set a Maximum size limit for the shadow copy volume. After a volume fills
up, VSS automatically deletes expired shadow copy images.
14-42
Lesson summary
• Key points
– In this lesson, you learned how NetBackup provides solutions to some of today’s backup challenges.
– You also learned the benefits of the NTFS and VxFS change logs, and how to enable NetBackup
Accelerator.
– Finally, you learned how to configure a policy to use multiple data streams and the benefits of handling
busy files and using VSS.
• Reference materials
– NetBackup Administrator’s Guide
– NetBackup Commands Reference Guide
– NetBackup Snapshot Client Administrator’s Guide
– http://www.veritas.com/support
43
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
14-43
Lab 14: Optimizing File System Backups
Lab objectives
• Configuring and using NetBackup Accelerator
• Configuring for and using multiple data streams
• (Optional) Configuring and performing multiplexed backups
44
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
14-44
What did you learn?
You are about to be asked a series
of questions related to the current
lesson.
45
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
14-45
Question 1: NetBackup Accelerator requirement
What must be enabled for NetBackup Accelerator?
46
14-46
Answer 1: NetBackup Accelerator requirement
What must be enabled for NetBackup Accelerator?
The correct answer is D. The NTFS change journal is an optional feature that can enhance the speed of a NetBackup
Accelerator backup; but it is not required. Veritas File System (VxFS) is not yet supported as a change log type with
NetBackup Accelerator. TIR is not a required feature with NetBackup Accelerator.
47
14-47
Question 2: When to use MDS
When is it most appropriate to use multiple data streams?
48
14-48
Answer 2: When to use MDS
When is it most appropriate to use multiple data streams?
The correct answer is B. Each tape drive can receive a data stream from a different disk. Requesting data from multiple
directories on the same disk can cause disk thrashing. When performing backups over a network, multiple streams can
add network contention. Small backup jobs complete too quickly to greatly benefit from multiple data streams.
49
14-49
End of presentation
14-50
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Collecting Logs and Diagnostic Information” lesson in the “Veritas
NetBackup 8.1: Administration” course.
15-1
Lessons in this course
1. Introduction to NetBackup 13. Managing and Protecting the NetBackup Catalog
2. Configuring NetBackup Storage 14. Optimizing File System Backups
3. Configuring Policies 15. Collecting Logs and Diagnostic Information
4. Performing File System Backups
5. Performing File System Restores
6. Configuring Disk Pools
7. Configuring Media Server Deduplication
8. Configuring Tape Storage
9. Managing Tape Storage
10. Performing Virtual Machines Backups
11. Performing Virtual Machines Restores
12. Duplicating Backups Using Storage Lifecycle
Policies
15-2
Lesson objectives
Topic Objective
Performing basic NetBackup Perform very basic troubleshooting for NetBackup environments.
troubleshooting
Identifying NetBackup processes, Identify and manage the NetBackup processes and services that run
services, and daemons on NetBackup master servers, media servers, and clients.
NetBackup logging overview Describe legacy and unified NetBackup logs.
Using the support utilities Use the NBSU and NBCPLOGS utilities, and describe the Logging
Assistant.
Using NetBackup support resources Identify available resources for NetBackup troubleshooting.
The table on this slide lists the topics and objectives for this lesson.
15-3
Topic: Performing basic NetBackup troubleshooting
After completing this topic, you will be able to perform very basic
troubleshooting for NetBackup environments.
After completing this topic, you will be able to perform very basic troubleshooting for
NetBackup environments.
15-4
A NetBackup troubleshooting checklist
Before contacting support
1. Define the problem
For example, for failed backup jobs: Note the status code, examine the Detailed Status report,
and determine what hosts are involved.
2. Examine the NetBackup reports
3. Verify services/daemons running on NetBackup hosts
4. Answer: “Has this backup ever worked?”
• If no: Check the initial configuration (policy, storage units, and so on)
• If yes: Check what has changed (upgrades, network, devices)
5. Depending on type of failure, contact internal groups, such as database
administrators (DBAs), network or storage groups
6. Note any patterns to the failure: Time of day? Network segment? Operating
system type? Storage units?
If the Activity Monitor shows a failed job, use this checklist to investigate the cause of
the failure.
1. Define the problem: Note the status code, examine the Detailed Status report in the
Job Details, and identify the servers involved in the backup .
2. Examine the NetBackup reports
3. Confirm that all services or daemons are running
4. Answer the question “Is this the first attempt?” for what appears to have caused the
error.
• If yes check the configuration for errors that may have caused this issue.
• If no review and note any changes made to the NetBackup configuration or
system environment.
5. Discuss problem with relevant internal groups (DBA,s network or storage group)
6. Note any patterns to the failure: time of day? Network segment? OS type? Storage
unit?
These steps should be undertaken before calling support. If the problem persists, open
a case with Veritas technical support. Gather all known details about the problem, and
be prepared to collect debug logging information.
15-5
Detailed Status report
One place to start your investigation of a failed job is in the Detailed Status report in the
Job Details.
This report will show the processes (and PIDs) involved in the backup as well as other
useful details.
In this example the job failed with status code 58: Can’t connect to client. The bpbrm
(backup and restore manager) process on the media server was unable to connect to
the bpcd (client service) process on the client. These processes will be discussed later in
this lesson.
15-6
Using the NetBackup Reports utility
Use the Reports utility in the NetBackup Administration Console to generate reports to
verify, manage, and troubleshoot NetBackup operations. NetBackup reports display
information according to job status, client backups, and media contents.
The reports draw upon a variety of sources including various NetBackup databases and
logs.
This lesson focuses on the Status of Backups report, the Problems report, the Media
Logs report and the All Log Entries report. These reports come from the error catalog
located in install_path\netbackup\db\error on Windows and under
/usr/openv/netbackup/db on UNIX. The first three reports are subsets of the
entire catalog and are created by using filters to select only certain parts of the entire
catalog. The All Log Entries report will display the entire catalog contents.
The catalog is a log which is automatically setup and enabled at installation. Error logs
are created on a 24-hour cycle. At midnight each day, the daily log is closed and a new
one is opened for the next days events. By default the logs are kept for 28 days. This can
be configured in the master server host properties under the Clean-up tab.
See the NetBackup Commands Reference Guide for more information about running
commands.
15-7
The All Log Entries report
The All Log Entries report displays logging information captured by NetBackup. The
information in this report is derived from the error catalog on the master server. Unlike
the detailed debug logs, the logging recorded to the error catalog is always active;
therefore, information is always available in this report. This report displays all the
information in the error catalog, including routine messages and events and problems.
When possible, NetBackup displays a severity for each message.
To access the information in this report from the command line, type:
bperror -all -U
15-8
The Status of Backups report
The Status of Backups report shows status and error information about the jobs that
completed within the specified time period. If an error occurred, a short explanation of
the error is included in the report.
The format is similar to that presented in the Activity Monitor, however, the two are
independent. Deleting a job from the Activity Monitor will have no affect on the output
of this report. Additionally, the Status of Backups report does not have any job details
for each job attached, as the Activity Monitor does.
The report can be filtered by specifying a time and date range, the media server, the
client or the job ID.
To access the information in this report from the command line, type:
bperror -backstat -U
15-9
The Problems report
10
The Problems report displays logging information from the error catalog on the master
server. The Problems report is basically a filter for the All Log Entries report. The
Problems report only displays messages that appear to be errors or problems; routine
messages are not displayed. This report can be very helpful in troubleshooting failed
jobs because there is less output to sort through, and the output is more likely to be
relevant.
The report can be filtered by specifying a time and date range, the media server, the
client or the job ID.
To access the information in this report from the command line, type:
bperror -problems -U
15-10
The Media Logs report
11
The Media Logs report displays errors that are specifically related to backup media, for
example, physical errors related to tape or disk media. The Media Logs report is another
filter of the All Log Entries report, and derives its information from the error catalog on
the master server.
Note that there are also separate reports for Tape Logs and Disk Logs, which filter the
results to display only errors related to tape or disk media, respectively. Having separate
reports for tape and disk enables you to identify problems quickly without sorting
through a large amount of information. It is also convenient if the responsibility for disk
backups and tape backups are assigned to different operators.
The report can be filtered by specifying a time and date range or the media server.
To access the information on this report from the command line, type:
bperror -media -U
15-11
Exporting reports
Windows
Unix
12
There may be times when you would like to have a copy of a report outside of the
NetBackup administration console. The Export option allows you to export a copy of the
report to a text file on disk. From there the report can be printed, imported to a
different application or distributed to other interested stakeholders.
The slide shows the process on both UNIX and Windows master servers.
Clicking on File in the toolbar displays a drop down menu. Selecting the option Export
will allow you to name the export file and specify where the file is to be created.
You can achieve a similar result from the command line by redirecting the output to a
file
bperror -media -U > file.txt
15-12
Topic: Identifying NetBackup services, daemons and
processes
After completing this topic, you will be able to identify and manage the
NetBackup services, daemons and processes that run on NetBackup master
servers, media servers, and clients.
13
After completing this topic, you will be able to identify and manage the NetBackup
services, daemons and processes that run on NetBackup master servers, media servers,
and clients.
15-13
Introduction to NetBackup processes
14
In multitasking computer operating systems, there are some computer programs that
run in the background and are always active. On UNIX, these are often referred to as
daemons. On Microsoft Windows systems, these types of programs are called services.
In NetBackup, daemons/services can be found on the master server, media servers and
clients. Because of the many administrations tasks and backup operations performed on
the master server you will find a large number of daemons/services running there. The
media servers and clients will have far fewer daemons/services running.
The term process refers to a program that is inactive until summoned by a
daemon/service.
Unless a specific distinction is required, the term process is frequently used in the
general sense to denote both daemons/services and processes.
Note of interest: The word daemon comes from the ancient Greek and is an older form
of our word demon. In modern English demons are definitely from the dark side but in
ancient Greece, daemons were neither good nor evil. Their job was to help define a
person’s character or personality. Ancient Greeks had personal daemons, not unlike the
guardian angels some people claim to have today. It has been said that UNIX has both
daemons and demons.
15-14
Monitoring services/daemons in the Activity Monitor
15
You can use the NetBackup Activity Monitor to monitor the services/daemons which are
currently running:
1. Invoke the NetBackup Administration Console.
2. Verify that you are monitoring the master server.
3. Click Activity Monitor in the object tree area.
4. In the details pane, click the Daemons tab.
From here, you can view the details of the active services and daemons.
15-15
Monitoring processes in the Activity Monitor
16
15-16
Viewing NetBackup services in Windows Services
17
On Windows servers, the Windows Services tool (also started with services.msc) shows
persistent NetBackup services configured for the NetBackup host. The master server
services, with the associated executable name, most closely associated with backup
operations include:
Service name Executable name
NetBackup Request Manager bprd
NetBackup Jobs Manager bpjobd
NetBackup Data Base manager bpdbm
NetBackup Proxy Service nbproxy
NetBackup Job Manager nbjm
NetBackup Resource Broker nbrb
NetBackup Enterprise Media Manager nbemm
This slide shows an example screenshot for a master server. On media servers or clients
the list of NetBackup services will be much shorter, and not include many of these
services.
For more details, refer to Article 100002166: How to verify the required NetBackup
daemons / services are up running on a master server, found online at
http://www.veritas.com/docs/100002166.
15-17
Viewing processes using the bpps utility
18
NetBackup provides a command line utility called bpps that displays active NetBackup
processes. The ps part of bpps indicates that it runs similarly to the UNIX ps
command.
The bpps utility is located in the following directory:
• Windows: install_path\NetBackup\bin\bpps
• UNIX: /usr/openv/netbackup/bin/bpps
The command options for bpps depend on the operating system platform. Examples of
some command options are listed on the slide. There is also a similar command for
Media Manager processes on UNIX, vmps.
The Windows version of bpps is quite powerful, similar to a resource kit utility for the
amount of information it can reveal about processes. For more help on bpps for
Windows, type: bpps -?
Run bpps on the system when it is idle and then again when a backup is running to
determine which processes become active for the backup.
For more details, refer to Article 100002166: How to verify the required NetBackup
daemons / services are up running on a master server, found online at
http://www.veritas.com/docs/100002166.
15-18
Verifying daemons before device configuration
19
The master server has many NetBackup daemons which run persistently. The slide
shows a subset of these, including important processes such as bprd, bpdbm, nbpem,
and so on.
The number of NetBackup daemons that run on a media server is highly dependent on
what devices have been configured for that media server. When first installed, a media
server has far fewer active services than a master server. These initial services include:
Service name Executable name
NetBackup Client Service bpcd
NetBackup Volume Manager vmd
NetBackup Remote Manager and Monitor Service nbrmms
A client has even fewer NetBackup daemons, which includes only those services that
you will also find on any NetBackup host (including the master and media servers):
Service name Executable name
NetBackup Client Service bpcd
NetBackup Veritas Networking Daemon vnetd
NetBackup Legacy Client Service (Windows only) bpinetd
The slide shows the daemons that you’d expect to see running after installing
NetBackup, but prior to configuring any backup devices on the media servers.
15-19
Verifying daemons after tape device configuration
20
On this slide, a number of additional daemons are shown on the media server. These
daemons start running after tape devices are configured, and include:
Service name Executable name
Logical Tape Interface Daemon ltid
Tape Library DLT (Robot) Control Daemon tldcd
Tape Library DLT (Drive) Daemon tldd
Automatic Volume Recognition Daemon avrd
Note that the name for the tldcd and tldd process depends on the type of library and
drives configured, and you may see more than just the one process if you have multiple
different devices configured. For example, some LTO drives are configured with the
NetBackup “Half-inch” designation, and would result in the tlhcd and tlhd processes.
15-20
Verifying daemons after MSDP configuration
21
On this slide, a number of additional daemons are shown on the media server. These
daemons start running after a Media Server Deduplication pool is configured, and
include:
Service name Executable name
NetBackup Deduplication Manager spad
NetBackup Deduplication Engine spoold
15-21
Verifying daemons during a backup
bpbrm
bptm
22
During some operations you will expect to see additional processes. As an example,
during a simple backup you may see the following processes appear on the media
server:
Service name Executable name
NetBackup Backup and Restore Manager bpbrm
NetBackup Tape Manager bptm
Note that although the process has the name “Tape Manager”, it is used for backups
that go to disk storage units as well.
During a backup, you will also see this process on the client:
Service name Executable name
NetBackup Backup and Archive Process bpbkar
For other operations, such as duplication and restore jobs, you may see different
processes. This is discussed further in the NetBackup Administration Guides as well as
the NetBackup Maintenance and Troubleshooting course.
15-22
Managing processes using commands and scripts
Stop all processes, daemons, and console processes bp.kill_all (UNIX only)
Start all processes, daemons, and console processes bp.start_all (UNIX only)
23
15-23
Topic: NetBackup logging overview
After completing this topic, you will be able to describe legacy and unified
NetBackup logs.
24
After completing this topic, you will be able to describe legacy and unified NetBackup
logs.
15-24
NetBackup debug logs and support
25
The following slides are designed to help you understand how NetBackup logging works
so that you can better assist support in the resolution of your NetBackup problem.
In order to investigate the problem support may request debug logs of the processes
associated with the problem. In addition, support may request the output of certain
NetBackup utilities such as nbsu. Other evidence such as operating system files and
logs may also be requested.
The process of log collection can be facilitated if you understand how NetBackup logging
works. In the following slides you will learn how to enable, configure and collect
NetBackup logs.
NetBackup customers are not expected to read and interpret logs. That is the job of the
support engineer who is working your case. They have the knowledge, skills, tools and
experience to examine and process the logs.
The number of logs requested will depend on the nature of the problem. If the problem
is ill defined or the source of the problem is not readily obvious, more logs may be
requested. If the problem is well defined and specific, then fewer logs will be required.
15-25
Understanding NetBackup debug log types
26
Every NetBackup process (including daemons and services) has a detailed debug log
associated with it. This is in addition to the default information that NetBackup logs to
the error catalog on the master server. Each log is a text-based file containing detailed
output from its associated process.
In NetBackup, there are two kinds of processes, each using a different logging method:
• Most NetBackup processes and components that have been added to NetBackup
since the NetBackup 6.0 release use unified logs. In general, these include processes
that begin with nb, and components that use the Private Branch Exchange (PBX) to
communicate. These logs are turned on all the time and are very configurable.
• Processes that existed prior to the NetBackup 6.0 release and continue to be used
today are referred to as legacy processes. These processes often start with bp (for
example bprd or bptm). The debug logs for these processes are referred to as legacy
logs and are not active by default. Legacy logs are less configurable than the newer,
unified logs, but are still very useful for troubleshooting. Best practice says to only
activate these logs when needed for troubleshooting purposes. They can grow very
large and can also affect performance.
There is one process, nbproxy, which uses legacy logs even though it is not a legacy
process.
15-26
Enabling and managing NetBackup logs
Legacy logs Unified logs
27
Enabling NetBackup logs depends on the type of logs you are managing. The slide
discusses both methods.
Legacy logs
Legacy debug logs provide a record of NetBackup activity related to specific services and
processes. The table on this slide shows the general process for enabling legacy logs.
1. Legacy debug logs are created by a process only if a subdirectory for that process
has been created. In general, these directories have the format:
• UNIX: /usr/openv/netbackup/logs/process_name
• Windows: install_path\NetBackup\logs\process_name
Legacy logging processes creates one or more debug log file per day, with the
format:
• UNIX: username.mmddyy_seqnum.log
• Windows: domainname@username.mmddyy_seqnum.log or
ALL_ADMINS.mmddyy_seqnum.log
The mklogdir script, found in the logs folder, can be used to create some, or all
the legacy logging directories. Because this script can creates log directories for all
possible daemons and processes and increase disk I/O, it is instead recommended
to run the command with the named directory as an argument.
Note: Earlier versions of NetBackup used a different naming convention, which did
not include the username.
15-27
Note: Refer to Robust Logging settings for details on number of log files created
each day.
2. Various logging parameters are configured in the NetBackup host properties for the
host. For example, NetBackup retains debug logs for the number of days specified by
the Duration to Keep Logs global attribute (default:28 days).
Log files can grow very large. Enable these files only if unexplained problems exist.
Delete logs and the directory when they are no longer needed. Veritas recommends
only to increase bprd and bpdbm logging levels under guidance of Support.
3. Starting in NetBackup 7.6 many services/daemons dynamically update within 60
seconds of the time they are changed. There is no need to restart NetBackup
services/daemons, as logging starts automatically.
Prior to NetBackup 7.6, to activate the logs, restart the process in question. For
example. a persistent daemon or service, such as bprd or bpdbm, must be stopped
and restarted to activate logging. On UNIX systems, use netbackup stop and
netbackup start to start all of the daemons. On Windows systems, use the
bpdown and bpup commands to start the entire NetBackup system.
4. A transient process, such as bpcd or bptm, logs to its directory the next time the
process runs. This means that logging some processes requires you to restart the
task associated with the process or issue, such as re-running the backup or restore
job.
Media manager processes do require a restart, and do not perform logging dynamically.
Logging for these media manager processes is configured in the volmgr directory:
• UNIX: /usr/openv/volmgr/logs/logging_dir_name
• Windows: install_path\VolMgr\logs\logging_dir_name
Unified logs
Unified logging creates log file names and messages in a format that is standardized
across Veritas products. Many NetBackup processes use unified logging.
1. Unified logs are enabled automatically and the logs are written into user definable
directories. The default directory on UNIX systems is /usr/openv/logs. On
Windows systems the logs are written in install_path\NetBackup\logs.
2. Various properties of the logs are defined in the nblog.conf configuration file
located in the /usr/openv/netbackup and install_path\NetBackup
directories. The nblog.conf file is configured using the vxlogcfg command.
Features such as log location, log size, number of logs to keep, roll over mode and
logging levels can be configured using vxlogcfg. In addition, the debug logging
level for nbpem, nbjm and nbrb can be configured through the master server Host
Properties. Doing this will update nblog.conf.
Making changes to the logging properties does not require a restart of
daemons/services.
15-28
Setting logging host properties
nbsetconfig
29
The Logging host properties apply to currently selected master servers, media servers,
and clients. The available properties differ between a server and a client.
Access the host properties from within the NetBackup Administration Console for the
host, and select the Logging tab.
The Global logging level setting is used for setting the debug level for all legacy debug
logs. Alternatively, Process specific overrides can be used to specifically set levels for
some individual processes, different from the global level.
It is possible to change logging level in the host properties, or by modifying the
bp.conf configuration file in UNIX.
Check your specific version of NetBackup for supported logging levels in the host
properties and the bp.conf file. Eight logging levels are supported in NetBackup 7.7:
no logging (-2), minimum logging (-1), same as global level (0), or low to maximum
debugging (1-5).
Logging for critical processes creates logs for critical NetBackup processes automatically
by creating the appropriate log directories. Check your version of NetBackup for a
specific list of processes. NetBackup 8.0 lists processes for the the master server (bprd,
bpdbm), media server (bpbrm, bptm, bpdm) and the client (bpfis), as long as they are
running NetBackup 7.7 or later.
15-29
Using commands for unified logs
Configure unified logging with vxlogcfg
• Configure debug logging level for nbpem:
vxlogcfg –a –p nb –o nbpem –s DebugLevel=3
• Configure the default maximum number of log files :
vxlogcfg –a –p nb –o Default –s NumberOfLogFiles=6
30
The vxlogcfg command is used to change the logging settings. Settings can be
changed for individual processes which are identified in the command by their
originator ID (OID). The OID can be in the form of a name (nbpem, nbjm, etc) or a
number (116, 117, etc.). A list of OID name and numbers can be found in the NetBackup
Troubleshooting Guide.
Similarly, the nblog.conf configuration file, which is located in the
/usr/openv/netbackup (UNIX) and install_path\NetBackup (Windows)
directories, can be used to identify originator IDs and the short names for processes.
Note that this file should only be changed using the vxlogcfg command. Do not edit
it manually.
Here are some sample lines from nblog.conf showing the OID and settings for nbjm:
# 117. Job Manager
117.L10nResource=nbjm
117.NtEventLogSourceName=nbjm
117.OIDNames=nbjm
117.LogDirectory=nbjm
Settings can also be changed for ALL processes. Finally, the Default value for a given
setting can be changed.
15-30
Disabling debug logs
Note: Minimize the logging level or disable debug logs unless you are actively troubleshooting.
31
Unless you are actively trying to capture a failure scenario, it is recommended to keep
logging at a minimum. Logs can have a tremendous impact on NetBackup performance
and disk space on the volume where logs exist.
Disable and purge legacy NetBackup logs by deleting the folder for the corresponding
logs in the NetBackup logs directory. The AltPath and user_ops folders, if present,
are part of normal NetBackup operations, and they must not be deleted. Also, do not
delete the mklogdir script.
Unified logs cannot be completely disabled, but the amount of detail logged and the
corresponding performance overhead varies based on the verbose settings.
The following commands revert debug and diagnostic unified log messages to
their default verbosity levels:
vxlogcfg –a –p 51216 –o Default –s DiagnosticLevel=6
vxlogcfg –a –p 51216 –o Default –s DebugLevel=1
Veritas recommends setting logging levels to their default settings versus
disabling them. Setting DebugLevel=0 and DiagnosticLevel=0 should
not be performed.
15-31
Making the most of NetBackup logging
32
The most efficient way to enable logging in NetBackup and to quickly gather the
required information from debug logs is to understand how NetBackup inter-process
communication works, and the direction of communication and data within the
NetBackup architecture. This information is best garnered over time and with
experience, but can be assisted by attending the Veritas NetBackup Advanced
Administration and Veritas NetBackup: Maintenance and Troubleshooting courses, by
reviewing the NetBackup Troubleshooting Guide, and by contacting Veritas Support.
15-32
High-level NetBackup process flow of a simple backup
Master Request Daemon Scheduler Job Manager Resource Broker
server (bprd) (nbpem) (nbjm) (nbrb)
Media Communications
Device Manager Backup/Restore (bpcd) Client
server Communications
(ltid) Manager
(bpcd)
(bpbrm)
Metadata
Backup and Archive
Tape Manager Client (bpbkar)
or
(bptm) Data
Client’s data
33
This slide shows the connections among the major processes of the master server, the
media server, and the client, during a standard backup job. By understanding this
architecture, you can get a better idea of where to apply logging. For example, if you
believe that NetBackup is having a communication or authentication problem during
backups, then applying logging to the bpcd, bpbrm, bpbkar, and bptm processes may
make sense. If you think that NetBackup is having problems allocating media or devices
during a backup, then logging of nbrb, nbemm (which is part of NBDB), and nbjm would
be appropriate.
In the diagram on the slide, some processes have been colored slightly differently to
show that they are persistently running while NetBackup is running. In NetBackup these
are also known as daemons or services: bprd, bpdbm, nbpem, nbjm, nbrb, nbemm,
bpcd, and ltid. Other more transient processes, represented by boxes with a dashed
outline, only start running when a backup job occurs: bpbrm, bptm, and bpbkar. In
addition, the dashed lines represent the flow of data, the dotted lines represent the
flow of metadata, and the solid lines represent the flow of communication to complete
a backup job.
For additional information, see the NetBackup Troubleshooting Guide and attend the
Veritas NetBackup: Maintain and Troubleshoot course.
15-33
Topic: Using the support utilities
After completing this topic, you will be able to use the NBSU and NBCPLOGS
utilities, and describe the Logging Assistant.
34
After completing this topic, you will be able to use the NBSU and NBCPLOGS utilities,
and describe the Logging Assistant.
15-34
Describing the NetBackup Support Utility (NBSU)
• Collects information about the operating system, network, and NetBackup environment
• Runs various operating system and NetBackup commands, based on switches and
NetBackup host role
• Frequently requested by Support
• Located in:
UNIX /usr/openv/netbackup/bin/support
Windows install_path\NetBackup\bin\support
35
The NetBackup Support Utility (NBSU) is a Veritas utility used to gather diagnostic
information. By default, NBSU gathers appropriate diagnostic information based on the
operating system and NetBackup environment. The amount of information gathered by
NBSU can be qualified using command-line switches. The path to the NBSU command is
shown on the slide.
NetBackup Support may request for the output of NBSU to be e-mailed or submitted to
them.
NBSU results are written to the following directories:
• UNIX: ./output/nbsu/hostname-role-YYYYMMDD_HHMMSS
• Windows:
C:\Users\username\output\nbsu\hostname-
role_YYYYMMDD_HHMMSS
Output can be redirected to a different output directory by using the command:
nbsu –odir destination_directory
15-35
Running NBSU
36
NBSU switches enable the collection of selective information. The following table
describes the switches used in the examples in the table on the slide:
Switch Description
-l List the diagnostic commands that are selected to run.
-d name Run the specified diagnostic commands or procedures. Use nbsu -l
to obtain a list of commands and procedures.
Note: Multiple -d options can be listed, for example:
-d OS_general -d OS_env
See the online help provided by nbsu –H for details on usage and nbsu –L for the
complete list of diagnostics and commands.
15-36
Example NBSU output on Windows
• Stored in a CAB file
• Includes many separate files
containing collected information
Sample of registry
information collected
37
This screenshot shows the text files which are packed into the CAB file. The names of
the individual files suggest the type of information collected.
This screenshot shows the contents of one of these files. The example displayed shows
the values collected for the
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
NT\CurrentVersion registry key.
15-37
Example NBSU output on UNIX
• Stored in a gzipped tar file
• Includes many separate files
containing collected information
38
This screenshot shows the text files which are packed into the compressed (.tar.gz)
file. The names of the individual files suggest the type of information collected.
This screenshot shows the contents of one of these files. The example displayed shows
some operating system environment information.
15-38
Describing nbcplogs
When you open a case with support, support may ask you to collect various logs to help
debug the issue. The requested logs, such as legacy logs, Unified logs, and so on, may be
in many places.
Examples include the NetBackup relational DB logs (NBDB logs), Activity logs (used to
generate NetBackup reports), Legacy logs, PBX logs, True Image Restore (TIR)
information, Jobs try logs, NetBackup Vault logs, Media Manager logs, VM mapping logs
(file mapping for virtual machine backups), Unified logs, Webserver logs, Windows
Event logs, and VxFI logs (logs for snapshot providers).
nbcplogs is a NetBackup utility which makes the collection of these logs much easier.
nbcplogs gathers NetBackup and system logs into a tar format file and then compresses
them to facilitate the uploading of the tar bundle to the Veritas Evidence Server. By
default, nbcplogs searches for all logs generated during the last 24 hours. There are
switches you can use to override the defaults.
Prior to NetBackup 8.0, this utility was also used to upload files to support. Because of
security changes to the Veritas FTP server, this feature has been removed from the
nbcplogs utility and the Logging Assistant. Logs must be manually uploaded.
To learn more about the methods to upload logs, refer to the Article 100038665:
Methods to provide data for Technical Support cases, found online at
http://www.veritas.com/docs/100038665.
15-39
Understanding nbcplogs command line syntax
With start and end date nbcplogs --start MM/DD --end MM/DD path
40
This slide shows a sample of the nbcplogs command line syntax. The variable path
signifies the folder or directory used. For more details refer to the NetBackup
Commands Reference Guide. All NetBackup documentation can be downloaded from
the SORT website at https://sort.veritas.com/netbackup.
15-40
Collecting nbcplogs on Windows and UNIX
Windows UNIX
accelerator.vmware-logs\ accelerator.vmware-logs/
allwebapps-logs\ Logs allwebapps-logs/
dberror-logs\ collected dberror-logs/ nbsu
db-logs\ db-logs/ output
eventlog-logs\ extra-logs/
nb-logs\ lnxmaster_master_20180128_124517.tar.gz
pbx-logs\ nb-logs/
purdisk.Agent_extra_paths_log-logs\ pbx-logs/
purdisk.Agent-logs\ purdisk.Agent_extra_paths_log-logs/
telemetry.dataset-logs\ purdisk.Agent-logs/
telemetry.domaininfo-logs\ puredisk.mtstrm-logs/
telemetry.runtime-logs\ telemetry.dataset-logs/
trylogs-logs\ telemetry.runtime-logs/
vault-logs\ trylogs-logs/
vxfi-logs\ vault-logs/
vxul-logs\ vxul-logs/
webconsoel-logs\ webconsoel-logs/
winmaster_master_20180128_114122.tar
nbsu Logs
output collected
41
This slide shows the output generated by running the nbcplogs command on both
UNIX and Windows. This command collects all logs and also runs the nbsu utility.
The output is written to the destination directory, as defined in the command.
15-41
Introduction to the Logging Assistant
42
The Logging Assistant is a helpful tool that can shorten the time that is required to set
up and collect debug logs and other information. Because Logging Assistant
automatically performs a number of functions, you can avoid the problems that are
associated with manually logging into NetBackup hosts, creating log directories, and
changing logging levels.
The Logging Assistant uses a series of wizards to help quickly troubleshoot a problem.
Depending on the category of NetBackup problem, the tool suggests the possible hosts
that may be involved in the problem and the logs that should be enabled on those
hosts. The tool also collects NetBackup debug logs, nbsu diagnostic information, as well
as additional evidence such as operating system files related to troubleshooting.
To use the Logging Assistant, make sure that NetBackup (7.6 or later) is installed on all
NetBackup hosts involved in the process. No special licensing is required. However, you
must have root permissions for UNIX, and administrator privileges for Windows, to use
the Logging Assistant. For more details, refer to the NetBackup Administration Guide.
Note: With NetBackup 8.0, the feature for uploading logs to the FTP server has been
removed from the nbsu and nbcplogs utilities and the Logging Assistant. Logs that have
been collected by the Logging assistant and the other support utilities can be manually
uploaded to the Veritas Evidence Server.
For more information, refer to Article 100028985: Logging Assistant FAQ, found online
at http://www.veritas.com/docs/100028985.
15-42
Topic: Using NetBackup support resources
After completing this topic, you will be able to identify available resources
for NetBackup troubleshooting.
43
After completing this topic, you will be able to identify available resources for
NetBackup troubleshooting.
15-43
Useful guides for troubleshooting
44
NetBackup has a rather extensive set of documentation. The entire documentation set
can be downloaded through the NetBackup SORT website at
https://sort.veritas.com/netbackup.
Three guide books are particularly useful for troubleshooting. These are the NetBackup
Status Code Reference Guide, the NetBackup Logging Reference Guide and the
NetBackup Troubleshooting Guide.
The NetBackup Troubleshooting Guide is very useful in learning how NetBackup works
under the covers. Understanding how NetBackup inter-process communication works,
and the direction of communication and data within the NetBackup architecture is key
to troubleshooting problems within NetBackup. This information is best garnered over
time and with experience, but can be assisted by reading the available documentation
and by attending the Veritas NetBackup Advanced Administration and Veritas
NetBackup: Maintain and Troubleshoot courses.
In addition, the NetBackup SORT website provides links to online NetBackup
communities and forums. Also consider joining your local NetBackup user group and
attending Vision, Veritas’s annual user and technical conference. For more information
on Vision, visit the Veritas Open Exchange website at https://vox.veritas.com/.
15-44
Escalating problem to NetBackup support
Contacting support
1. If problem persists, open a support case:
• Go to https://support.veritas.com
• Sign in or register
• Create a new case or manage an existing case
2. Be prepared to collect debug logging information
3. Upload requested logs and data to support
For information about support policies and options refer to Support Fundamentals:
https://www.veritas.com/content/support/en_US/terms/support-fundamentals.html
45
The slide lists some simple steps when contacting NetBackup support.
1. If you cannot resolve the problem on your own, open a support case. First go the
Veritas Support web site at https://support.veritas.com. At that site, sign in or
register for a new account, and then create a new case or manage an existing case.
2. Be prepared to collect debug logging information.
3. Upload the debug logging information to support.
Information about support policies and options can be found online at
https://www.veritas.com/content/support/en_US/terms/support-fundamentals.html.
15-45
Accessing the Veritas support website
46
Various methods may be available to upload and download a small number of files
direct to an existing Veritas Support case. Examples include:
• Direct file transfer to an existing case via the Veritas Support web portal using
existing Veritas Account credentials.
• Direct file transfer using a file transfer website (https://mft.veritas.com)
• Direct file transfer using SecureFTP (sftp://sftp.veritas.com).
• FTP transfer to a designated folder using credentials provided by Technical Support.
Please contact your support engineer, if you are unsure about which method to use.
For more information, refer to Article 100038665: Methods to provide data for Technical
Support case, found online at http://www.veritas.com/docs/100038665.
15-46
Lesson summary
• Key points
– In this lesson, you learned to perform very basic troubleshooting for NetBackup environments, including
how to identify and manage the NetBackup processes and services that run on NetBackup master
servers, media servers, and clients.
– You also learned to describe legacy and unified NetBackup logs, and how to use the NBSU and nbcplogs
utilities, and describe the Logging Assistant.
– Finally, you learned how identify available resources for NetBackup troubleshooting.
• Reference materials
– NetBackup Administrator’s Guide
– NetBackup Commands Reference Guide
– NetBackup Troubleshooting Guide
– NetBackup Logging Reference Guide
– http://www.veritas.com/support
47
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
15-47
Lab 15: Collecting Logs and Diagnostic Information
Lab objectives
• Viewing, stopping and starting the NetBackup services
• Running NetBackup reports for troubleshooting
• Using the nbsu and nbcplogs commands
• (Optional) Viewing and setting debug logging properties
• (Optional) Enabling NetBackup legacy debug logging
• (Optional) Viewing debug logging levels for unified logs
48
The slide shows the objectives for the lab associated with this lesson. Refer to the
corresponding lab guide for specific instructions and lab steps.
15-48
What did you learn?
You are about to be asked a series
of questions related to the current
lesson.
49
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
15-49
Question: Starting NetBackup services on Windows
Which command starts the NetBackup services on Windows?
50
15-50
Answer: Starting NetBackup services on Windows
Which command starts the NetBackup services on Windows?
The correct answer is A. None of the other commands are valid on a Windows NetBackup host, although some are valid
on a UNIX NetBackup host.
51
15-51
Question: Reading NetBackup logs
Which statement is correct?
52
15-52
Answer: Reading NetBackup logs
Which statement is correct?
The correct answer is D. The unified logs are not stored in plain text. Legacy logs are created in plain text and can be
viewed in any text editor, like Notepad. You can set the logging levels in NetBackup Administration Console. OpsCenter is
used to generate reports and monitor NetBackup.
53
15-53
Question: About the nbcplogs utility
Which statement best describes the nbcplogs utility?
54
15-54
Answer: About the nbcplogs utility
Which statement best describes the nbcplogs utility?
The correct answer is B. The nbcplogs utility collects a variety of log files. For example, nbcplogs collects unified logs,
legacy logs, NBDB logs, TIR info, PBX logs, web service logs and more.
55
15-55
End of presentation
15-56
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Introduction to Application and Database Backups” appendix in the “Veritas
NetBackup 8.1: Administration” course.
A-1
Lesson objectives
Topic Objective
Application protection concepts Discuss application backup types, and the features of Granular
Restore Technology (GRT) and Block Level Incremental Backups
(BLIB).
Introduction to database backups Discuss database backup and restore concepts.
Introduction to enterprise Discuss options for backing up and restoring Exchange, Active
application backups Directory, SharePoint, and Enterprise Vault.
The table on this slide lists the topics and objectives for this lesson.
A-2
Topic: Application protection concepts
After completing this topic, you will be able to discuss application backup
types, and the features of Granular Restore Technology (GRT) and Block
Level Incremental Backups (BLIB).
After completing this topic, you will be able to discuss application backup types, and the
features of Granular Restore Technology (GRT) and Block Level Incremental Backups
(BLIB).
A-3
Application backup concerns
Data consistency
0110 1101 • Is the data consistent for recovery?
• Does the backup require application state changes?
Scheduling
• Who is initiating the backup: NetBackup or the application?
• Are there restrictions on when the backup runs?
Automation
• How is the application put into and out of a backup state?
• What additional automation or notification is required?
This slide describes the high level concerns you need to consider when preparing for
application backups. At a minimum, you should ask and answer the questions shown on
the slide. For many of the popular databases, such as Oracle, Microsoft Exchange, and
Microsoft SQL, there are NetBackup agents that answer these questions and simplify
the configuration and running of backups and restores of these databases.
A-4
How backups are initiated in NetBackup
Automatically
• Scheduled in NetBackup with frequency, calendar, or automatic schedule types
• Started by the NetBackup scheduler
Manually
• Sometimes referred to as immediate backup
• Run manually from the NetBackup Administration Console, OpsCenter, or command line
• May be automated with a script, cron (UNIX), Task Scheduler (Windows), or a third-party job
scheduler
A-5
NetBackup policy types
Data type Policy type examples Description
• Standard
File system Perform UNIX and Windows file system backups
• MS-Windows
NetBackup NBU Catalog Protect the NetBackup master server catalogs
• VMware
Virtualization Performs backups of virtual machines
• Hyper-V
• MS-SQL-Server
• Oracle
Databases Perform online backups of databases
• Sybase
• DB2
• MS-Exchange-Server
• MS-SharePoint
Applications Perform online backups of enterprise applications
• Lotus-Notes
• Enterprise-Vault
As shown on the slide, there are many policy types in NetBackup, which correspond to
different ways of handling different types of data:
• File system data
File system backups tend to use either Standard or MS-Windows policy types to
back up UNIX or Windows file systems, respectively.
• NetBackup data
The NBU-Catalog policy type is special, and used specifically to back up the
NetBackup master server configuration, databases, and catalogs.
• Offsite data copies
The Vault policy type is used with the NetBackup Vault feature, for making and
tracking offsite copies of data for disaster recovery purposes.
• Databases, applications, and virtual machines
Many of the other policy types are used to back up specific applications, file
systems, or virtual machines. The policy type helps NetBackup determine how to
communicate and collect data. It performs this in coordination with the application,
sometimes with the goal of higher availability or automation of tasks, such as
controlling the starting and stopping of services, log truncation, or enabling online
backup methods.
A-6
Choosing a policy type (Oracle example)
Database and Database and
associated files associated files
Backups Restore
A-7
Database backup types
bpbkar-based Stream-based Intelligent
Database backups are divided into three types: bpbkar-based and script-based.
Some examples of bpbkar-based database backups are Exchange, SharePoint, Lotus
Domino, and Enterprise Vault. The backup process flow for bpbkar-based database
backups is similar to other standard file system backups.
Script-based backups can be split into two different types, stream based and Intelligent
Policy. Both types use a script. Stream based use a script that is written using the
database backup and restore utilities. Examples of script-based database backups are
Oracle, Sybase, Informix, DB2, and SQL Server.
Intelligent policies still use a script but the script is generated at run time using the data
that is entered in the NetBackup policy. Examples of intelligent policies are Oracle and
SQL Server.
The process flow for stream based and intelligent policy backups are significantly
different from the standard backup process flow.
A-8
How databases are backed up in NetBackup
bpbkar- Stream-
Schedule type Intelligent
based based
Frequency- or calendar-based *
• Backup initiated by NetBackup scheduler
• Most common types
User
• Backup initiated by user or application
• NetBackup restricts backup windows
• Application determines backup data
Application
• Variant of the User schedule
• Backup initiated by NetBackup as directed by Application
• Schedule determines backup retention
Automatic
• Backup initiated by database script on client, run by
NetBackup.
• This can be optional.
• Contains no backup data.
* Available schedules are Full, Incremental, and Logs 9
This slide compares and contrasts the schedules for bpbkar-based backups, script-based
backups and intelligent policies.
In general, bpbkar-based backups are scheduled as normal file system backups. They
can be controlled automatically with a frequency- or calendar-based schedule that
NetBackup initiates, or with a User Backup schedule that enables the client to initiate
the backup.
With script-based backups, an Application Backup schedule is created that enables the
application to initiate the backup. The backup is usually initiated when the application
runs a script that defines attributes of the backup.
Additionally, if you wish to configure NetBackup to control the schedule of these script-
based backups, use an Automatic Backup schedule that directs the application to run
the script, which then initiates the backup.
With intelligent policies, the schedule type can be Full, Incremental or be a special Logs
type for backing up Oracle Archive logs or SQL Server T-Logs.
The schedule initiates the backup and uses the same NetBackup schedule to store the
data removing the need for separate Application Schedules
A-9
Application backup-related features
10
A-10
Topic: Introduction to database backups
After completing this topic, you will be able to discuss database backup and
restore concepts.
11
After completing this topic, you will be able to discuss options for backing up and
restoring Oracle and MS-SQL and how transactions logs can be affected.
A-11
Database overview
12
Definitions for a database, database system, and database management system (DBMS)
are provided on the slide.
Some well-known DBMSs are also listed.
Some basic database backup and restore concepts are discussed on the following slides.
A-12
Database failures and resiliency
13
A-13
Determining your backup strategy
14
A-14
• Databases and partial backups
Other factors to consider when performing physical backups are database size and
tablespace traffic. Complete database backups take longer and require large
amounts of storage space. If you structure your database so that only certain data
files or tablespaces are modified regularly, you can save time and storage space by
backing up only the elements that change.
When you perform a database backup, all constituent files of the database are
backed up as a coherent whole.
An individual tablespace can be backed up independent of the remainder of the
database. Because tablespaces can consist of multiple data files, backing up
tablespaces is more common than backing up individual data files. Backing up a
tablespace is generally an online backup.
As with a tablespace backup, individual data files can be backed up independent of
the remainder of the database. If a tablespace consists of only one file, this is
identical to a tablespace backup. Otherwise, the effect is to back up only a portion
of a tablespace. Backing up a data file is generally an online backup.
• Full and incremental backups
Running full backups can be prohibitive when the data set is very large. Use
incremental backups that take advantage of database transaction logs to shorten
the backup window and automate database log maintenance. Additionally, Oracle
supports block level incremental (BLI) backups to provide increased performance
and reduced resource usage.
• Backup storage destination
One of the key advantages of having NetBackup manage the database backups is
that they can be sent to any of the storage methods supported by NetBackup,
including tape-based, disk-based, or deduplication-based storage.
• Physical destination
Another advantage of using NetBackup is the range of physical destinations and
strategies that are supported, including automated duplication to any supported
storage destination, automation and management of offsite media storage, and
various replication features and technologies.
NetBackup agents optimize the performance of critical databases and applications by
providing the ability to use all of these backup strategies and technologies.
A-15
Database backup using an Application schedule
1
2
16
The graphic on this slide describes the process for backing up a database using an (BLIB)
schedule.
In this procedure:
1. The database attempts to initiate a backup with the master server by using a backup
script.
2. NetBackup uses the Application schedule to ensure there is an open window in
which to run the database backup, and then build the backup job.
3. The database backup job runs when the resources become available.
A-16
Database backup using an Automatic schedule
17
The graphic on this slide describes the process for backing up a database using an
Automatic schedule.
In this procedure:
1. NetBackup runs an Automatic schedule to initiate the backup script.
2. The database attempts to initiate a backup with the master server using a backup
script.
3. NetBackup uses the Application schedule to ensure there is an open window in
which to run the database backup, and then build the backup job.
4. The database backup job runs when the resources become available.
A-17
Topic: Introduction to enterprise application backups
After completing this topic, you will be able to discuss options for backing
up and restoring Exchange, Active Directory, SharePoint, and Enterprise
Vault.
18
After completing this topic, you will be able to discuss options for backing up and
restoring Exchange, Active Directory, SharePoint, and Enterprise Vault.
A-18
Database backups for Microsoft Exchange Server
19
A-19
• NetBackup can back up and restore storage groups and databases within the storage
group.
• For snapshot backups, NetBackup uses the Microsoft consistency check API to check
the consistency of databases and transaction logs and to provide additional details.
This speeds up a snapshot backup because it allows the backup to proceed in
parallel with the consistency check.
• NetBackup for Exchange can perform backups and restores of Exchange objects with
snapshot methodology. With a separate Snapshot Client license, you can perform
off-host backups, Instant Recovery backups, and backups with a hardware provider.
• Exchange 2007 and later backups can be restored to another database or another
storage group on the local server or on a different server. Exchange 2003 snapshot
backups can be restored to an identical storage group on a different server.
• Exchange 2007 and later backups can be redirected to the recovery database or
recovery storage group (RSG). Streaming backups of Exchange 2003 can be
redirected to the RSG.
• The NetBackup for Exchange Server agent supports Microsoft Cluster Server (MSCS)
environment and Veritas Cluster Server (VCS).
For additional details, see the NetBackup for Microsoft Exchange Server Administrator’s
Guide.
A-20
Enterprise agent example: Microsoft Exchange
21
This is an example of an enterprise agent for NetBackup. Enterprise agents use special
directives in the Backup Selections list to define what is protected. In this example,
Microsoft Exchange is being protected. The NetBackup administrator added a user
backup schedule in addition to an automatic full backup. Note that having a user backup
schedule is not mandatory to protect Microsoft Exchange, but it does provide increased
flexibility.
A-21
Database backups for Microsoft SharePoint Server
22
A-22
Database backups for Microsoft Active Directory
23
Active Directory (AD) is a directory service created by Microsoft for Windows domain
networks. Active Directory serves as a central location for network administration and
security. It is responsible for authenticating and authorizing all users and computers
within a network of Windows domain type. Administrators can use Active Directory for
assigning and enforcing security policies for all computers in a network, and for
installing or updating software on network computers. Server computers with Active
Directory running are called domain controllers.
NetBackup can be used to restore individual objects and attributes in the Active
Directory, instead of restoring the entire Active Directory. Administrators can also
restore deleted objects, known as tombstone objects, from the Active Directory.
Active Directory granular NetBackup restores are supported on Windows 2003 R2 SP2,
Windows 2008, Windows 2008 R2, and more. Check the NetBackup documentation to
find out which version of Windows support Active Directory granular restores.
A-23
Granular Recovery Technology (GRT)
24
Granular Recovery Technology (GRT) enables the ability to restore individual objects,
such as mailbox and public folder items in Exchange, from full database backups.
This type of backup can serve both kinds of recovery situations. From the same backup
image, you can restore entire storage groups or databases, or you can select individual
objects within that backup. This backup replaces the existing MAPI mailbox backup,
sometimes referred to as a brick-level backup, which took a significant amount of time
with Microsoft Exchange.
You can restore individual items using GRT from the following types of backups:
• Full or user-directed backups (Incremental backups are not yet supported.)
• Local snapshot backups
• Off-host snapshot backups
• Instant recovery backups, when the schedule copies the snapshot to a storage unit
• Replica snapshot backups
• Streaming backups (Exchange 2007 and earlier)
A-24
Database backups for Veritas Enterprise Vault
25
Veritas Enterprise Vault enables an organization to store messaging and file system data
automatically in centrally-held archives. Clients and users can retrieve selected items
easily and quickly when required.
Enterprise Vault can archive any of the following types of data:
• Items in Microsoft Exchange user and journal mailboxes
• Items in Domino mail files and journal databases
• Files held on network file servers
• Documents held on Microsoft SharePoint servers
• Instant Messages, Bloomberg messages, and SMTP messages
The NetBackup Enterprise Vault agent consists of the components that enable you to
protect the Enterprise Vault configuration and archived data.
The Enterprise Vault agent enables you to back up and restore the Enterprise Vault file
system data and the Enterprise Vault SQL data. These types of data can reside on
different systems or devices, such as NTFS or NAS devices.
The Enterprise Vault agent also serves as a disaster recovery solution for data that is
archived using Enterprise Vault. Recovery of the archived data is not dependent on the
archive source, such as Exchange Server or a specific file system.
A-25
Lesson summary
• Key points
– You learned how to discuss the types of application backups and you can describe the features of GRT
and BLIB.
– You also learned to discuss general options for backing up and restoring databases.
– Finally, you learned the advantages for backing up and restoring Exchange, Active Directory, SharePoint,
and Enterprise Vault using NetBackup agents.
• Reference materials
– NetBackup Administrator’s Guide
– NetBackup for Microsoft Exchange Server Administrator’s Guide
– NetBackup for Microsoft SharePoint Server Administrator’s Guide
– http://www.veritas.com/support
26
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas Support web site frequently.
A-26
What did you learn?
You are about to be asked a series
of questions related to the current
lesson.
27
The next section is a quiz. In this quiz, you are asked a series of questions related to the
current lesson.
A-27
Question: About block level incremental backups (BLIB)
Which of the following statements about block level incremental backups (BLIB) is
correct?
28
A-28
Answer: About block level incremental backups (BLIB)
Which of the following statements about block level incremental backups (BLIB) is
correct?
The correct answer is B. Block level incremental backups (BLIB) backs up changed data for Oracle. This method does not
apply to Exchange
29
A-29
Question: Backup Selections list for an Oracle backup policy
What is in the Backup Selections list for an Oracle backup policy?
30
A-30
Answer: Backup Selections list for an Oracle backup policy
What is in the Backup Selections list for an Oracle backup policy?
The correct answer is D. This technique is also common to other databases, such as Microsoft SQL Server.
31
A-31
Question: Microsoft Exchange backups
Which statement about Microsoft Exchange backups is true in NetBackup?
32
A-32
Answer: Microsoft Exchange backups
Which statement about Microsoft Exchange backups is true in NetBackup?
The correct answer is D. Granular Recovery Technology provides this functionality for Exchange.
33
A-33
End of presentation
A-34
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
This is the “Protecting and Recovering Hyper-V Virtual Machines” appendix in the
“Veritas NetBackup 8.1: Administration” course.
B-1
Lesson objectives
Topic Objective
Introduction to virtual machine Describe virtual machines and discuss support for virtual machines
backups in Hyper-V.
Configuring Hyper-V backups Configure NetBackup to protect Hyper-V virtual machines.
Performing Hyper-V restores with Perform Hyper-V restores with the NetBackup Add-in for SCVMM.
the NetBackup Add-in for SCVMM
The table on this slide lists the topics and objectives for this lesson.
B-2
Topic: Introduction to virtual machine backups
After completing this topic, you will be able to describe virtual machines
and discuss support for virtual machines in Hyper-V.
After completing this topic, you will be able to describe virtual machines and discuss
support for virtual machines in Hyper-V.
B-3
Machine virtualization overview
• Using virtualization, a host server performs the job of multiple computers sharing the
physical host’s resources.
• Each virtual machine (VM):
– Runs its own operating system and applications
– Is encapsulated and isolated from other VMs
– Uses its own emulated resources (such as CPU,
disks, and network connection)
• The virtualization layer, or hypervisor, is software that enables virtual machines to use
the host’s physical resources.
• The hardware layer consists of the physical components of the host server, and is shared
across the running virtual machines.
• Review Article 000006177: Support for NetBackup in virtual environments
Virtual machines, sometimes referred to as VMs, enable the sharing of the underlying
physical machine resources between virtual machines, each running its own operating
system. The software layer providing the virtualization is called a virtual machine
monitor or hypervisor. A hypervisor can run on bare hardware (native VM) or on top of
an operating system (hosted VM). An example of a hypervisor running on bare hardware
is VMware ESX Server. An example of a hypervisor running on top of an operating
system is VMware Server and Workstation. In the case of Microsoft Hyper-V, the
hypervisor runs on a special version of the Windows operating system.
NetBackup support for virtual machines
VMs consist of a number of files, including the critical virtual hard disk file (VMDK in
VMware, and VHD or VHDX in Hyper-V), which contains the operating system and data
for that VM. Traditionally, backing up the virtual hard disk file enables you to easily
restore the VM but does not provide the ability to perform individual file restores.
Conversely, backing up files from the VM as a normal client prevents easily restoring the
full virtual hard drives in the case of disaster recovery. NetBackup provides the ability to
easily back up and restore the virtual hard disk, while alternatively allowing for granular,
individual file restore.
Review support details in Article 000006177: Support for NetBackup in virtual
environments, found online at http://www.veritas.com/docs/000006177.
B-4
How Virtualization Works
Modern CPUs have features built in for system protection. These protections keep
different programs from writing into each others’ memory regions. CPUs also have
privileged instructions: Instructions only executable by the operating system.
The structure of virtualization is to allow multiple operating systems to run on the same
set of CPUs. In order to allow multiple operating systems to run, the virtualization
mechanism has to properly handle privileged instruction execution.
There are different methods virtualization systems use to handle privileged instructions.
VMware and Hyper-V use virtualization features of the CPU: Intel VT and AMD-V. The
hypervisor signals the CPU that certain processes are virtual machines, and allows the
privileged instruction to execute. Prior to this CPU technology, the hypervisor
intercepted privileged calls and executed software to manage access to the privileged
instructions. This virtualization technology model is more efficient and reliable.
Citrix XenServer uses para-virtualization: the operating system is modified to
accommodate the privileged instruction execution.
The hypervisor virtualizes networks, network switching, interrupts, and disk storage.
A hypervisor control application manages and monitors the creation, operation, and
lifecycle of virtual machines. Often, this control application runs on a separate host, to
remotely and centrally manage the virtualization servers.
B-5
Supported NetBackup virtual machine backup solutions
VMware vSphere ✓ ✓ ✓ ✓ ✓
Microsoft Hyper-V ✓ ✓ ✓ ✓
RedHat Enterprise
Virtualization ✓
Citrix XenServer ✓
Solaris zones ✓
Oracle Solaris
virtualization ✓
B-6
Understanding the virtual data center implementation
Hypervisor
control system
SAN
Control API
CLI
Web Interface
Storage
Cloud
orchestration
Virtualization
Web Client
B-7
Overview of NetBackup support for VMware vSphere and
Microsoft Hyper-V
Feature VMware vSphere Microsoft Hyper-V
Intelligent Policy with VM query builder VMware policy type Hyper-V policy type
NetBackup support for VMware vSphere and Microsoft Hyper-V are summarized in the
table on the slide.
Both products are supported with full VM recovery, or individual file and folder level
restores, from single-pass backups performed by NetBackup. Both VMware and Hyper-
V policy types exist, that include automatic VM selection using a query builder, as well
as simplification of VM-specific backup configuration. Settings exist to limit and control
backup impact on the environment, to ensure performance is not adversely affected.
Full and incremental backups are supported, including block-level incremental backups
(BLIB) that avoid backing up unused space. BLIB is supported with VMware Change
Block Tracking (CBT) and Hyper-V Windows Management Instrumentation (WMI).
NetBackup for VMware also supported application-aware single-pass backups for
granular recovery of Microsoft Exchange, and SharePoint, and provide log truncation for
Microsoft SQL and Exchange. NetBackup for VMware also supports instant virtual
machine recovery, which is discussed in more detail in the Performing Virtual Machine
Restores lesson.
Off-host backups of VMs are supported in VMware using VMware vSphere Storage APIs
– Data Protection (VADP), reducing processing load on the VM server, and preventing
the need to install a NetBackup client on the VMs. Hyper-V also supports some off-host
/ alternate client backups, but requires some additional configuration steps, as provided
in the documentation.
Centralized management and web consoles are supported, which include VMware
vSphere web client, vCenter servers, and the Hyper-V System Center Virtual Machine
Manager (SCVMM).
B-8
Topic: Configuring Hyper-V Backups
After completing this topic, you will be able to configure NetBackup to protect Hyper-V
virtual machines.
B-9
Example NetBackup for Hyper-V environment: Media servers and
Hyper-V servers
Master Media Hyper-V
server server servers
LAN
SAN
Virtual machines
Each Hyper-V server requires
one NetBackup client.
10
B-10
Example NetBackup for Hyper-V environment: Hyper-V servers as
SAN media servers
Media and
Master Hyper-V
server server LAN
SAN
11
B-11
Example NetBackup for Hyper-V environment: Hyper-V servers as
SAN clients
Master Hyper-V
server server LAN
SAN
12
B-12
Comparing VSS and WMI
13
Backing up and restoring virtual machines, much like other live data, requires a method
for ensuring data consistency. The original Microsoft solution was to use Volume
Shadow Copy Service (VSS) technology for Hyper-V VM backups and restores
VSS-based backups of VMs has the following limitations, which affect scalability,
reliability, and availability:
• Creates a snapshot of the entire storage volume on which the VM resides.
• Requires serialized snapshots due to limitations in VSS framework.
• Consists of many separate components, such as the VSS framework, Hyper-V VSS
writer, and third-party VSS providers, impacting the reliability of the overall solution.
• Requires Linux VMs or VMs without integration services to be put in saved state
during the backup, to ensure consistency, causing downtime.
The new WMI-based backup method, introduced by Microsoft in Hyper-V 2016 and
later, addresses all the above limitations, as well as provides additional feature support.
For example, change block tracking allows for the use of features such as NetBackup
Accelerator.
Note that the VSS backup method is not deprecated. Users of NetBackup 8.0 and later
can select either VSS or WMI as the backup method while configuring the Hyper-V
policies for Hyper-V 2016. It is highly recommended to use the WMI method for better
scalability and reliability.
B-13
NetBackup for Hyper-V components
Component Description
Virtual machine • Sometimes referred to as a VM
• Configured as a NetBackup client in the NetBackup policy
• Does not require the NetBackup client being installed
• Requires the NetBackup client when restoring individual files to a VM, or when using
Hyper-V pass-through disks
Hyper-V server • A Windows hypervisor-based virtualization system which hosts the VM guests
• Must have the NetBackup client installed
Hyper-V integration • Provides integration between the Hyper-V server and the VMs
services • Hyper-V servers must have Hyper-V backup integration services enabled
SCVMM • System Center Virtual Machine Manager
• Centralizes management for the Hyper-V virtualized datacenter
Media server • Reads and writes backup data
• For efficiency, should be installed on the Hyper-V server
NetBackup client • Installed on the Hyper-V server
• Generally not required in the virtual machine
14
This slide lists Hyper-V components and components used by NetBackup when backing
up Hyper-V.
B-14
Configuring Hyper-V backups
NetBackup configuration
Install
Create a
NetBackup
Add Enterprise Set Resource NetBackup
client or Media
Client license Limits policy for
Server on
Hyper-V
Hyper-V server
15
Configuring Hyper-V backups is covered in detail in the Veritas NetBackup for Hyper-V
Administrator’s Guide. See the documentation for detailed steps, notes, and limitations.
B-15
Understanding Hyper-V intelligent policies
16
Hyper-V intelligent policy in NetBackup 8.0 introduce new features, such as the query
capability, for selecting VMs based on a combination of attributes, rather than simply
the VM name. The VM browse capability available in prior versions is also available.
In order to optimize both application service and backup and recovery needs, intelligent
policies allow you to limit Hyper-V resources for use in backup jobs.
Additionally, these policy improves the backup administrator’s efficiency and
effectiveness., reducing the detailed analysis and tracking that are required if VM
backups are managed by browsing and manual selection. The Hyper-V intelligent policy
enables backup administrators, managers, and other stakeholders to focus on higher
level issues: recovery point objectives (RPO), recovery time objectives (RTO), and policy
coverage.
The requirements, installation and operation of the Hyper-V intelligent policy include a
supported operating system on the Discovery Host, and a .NET 3.5 runtime on the
Discovery Host.
Additionally, in order for the Hyper-V intelligent policy to function properly, the
NetBackup Legacy Network Service makes requests of the Hyper-V server. Valid logon
credentials needs to be delivered to the Hyper-V server. To modify credentials, the
NetBackup Legacy Network Service is accessed through the Services interface. Proper
logon credentials are supplied in the LogOn tab permitting query operations.
B-16
NetBackup configuration: Set resource limits
17
Veritas highly recommends setting limits on the use of Hyper-V resources to prevent
serious performance issues on your virtual servers.
Set limits by navigating to the Resource Limit tab of the master server’s Host
Properties. Select Hyper-V in the Application column. Click in the Resource Limit
column to set the maximum NetBackup usage for the resource type. The settings apply
to all Hyper-V policies that use a Hyper-V Intelligent Policy query to select clients.
The default for all resource limits, indicated in the NetBackup Administration Console by
a blank value in the Resource Limit column, is unlimited. The screen shot shows a
maximum of four simultaneous active snapshots per Hyper-V server at a given time.
For details on resource limit types and behavior, see the NetBackup for Hyper-V
Administrator’s Guide.
Note that you may want to adjust or tune the resource limits according to the transport
mode you select.
B-17
NetBackup configuration: Create a Hyper-V policy
Use the
Hyper-V
policy type
18
To create a backup policy, use either the Policy Configuration Wizard or the Policies
utility in the NetBackup Administration Console.
The Hyper-V policy type was introduced in NetBackup 7.5. When it is selected, a new
Hyper-V tab is displayed in the policy configuration dialog. This tab contains Hyper-V
specific parameters.
Note: Prior to NetBackup 7.5, the FlashBackup-Windows policy type was used to back
up virtual machines. In 7.7 and later FlashBackup policies may no longer be used to
protect Hyper-V.
To migrate FlashBackup-Windows policies that were created in prior versions to use the
Hyper-V policy type, see the nbplupgrade utility in the NetBackup Commands
Reference Guide.
B-18
Hyper-V policies: Attributes and schedules
Attributes Schedules
• Many options don’t apply • Supports full, differential, and cumulative
incrementals
• Supports full VM and file-level incrementals for all
schedules
Set Enable file recovery from VM backup on the Hyper-
V tab
19
For Hyper-V type policies, many attributes found under the policy Attributes tab are
disabled. Most relevant Hyper-V specific options are found under the Hyper-V tab,
discussed elsewhere in this lesson.
Hyper-V policies support full, differential incremental, and cumulative incremental
schedules. If you are simply backing up the virtual machine disk (VHD/VHDX) files, these
schedules normally all back up the entire file. By setting the Enable file recovery from
VM backup option under the Hyper-V tab, NetBackup can recover the entire virtual
machine from these files, as well as perform individual file recovery. This ensures that
incremental backups only back up the changed files, while still providing the ability to
restore the entire virtual machine. Note that file level recovery is only available on
supported guest operating systems.
B-19
Hyper-V policies: Client Manual Selection
20
When assigning clients for a Hyper-V policy, you can select whether to select clients
manually or to have them automatically selected using a query that you construct.
To manually specify clients, navigate to the Clients tab, select Select Manually, and click
New. The Browse for Virtual Machines dialog box is displayed. Select Browse and
Select Virtual Machines to see a drop down hierarchy of virtual machines. Select the
virtual machine or machines you are interested in protecting.
Note that a policy where virtual machines are manually selected does not honor the
resource limits specified in the master server host properties.
B-20
Hyper-V policies: Client automatic selection
Example queries:
• Back up all VMs in Power On state
• Back up all VMs where the display name starts with “Vmprod”
• Back up all VMs that are clustered
• Back up all VMs in Power On state in Hyper-V Server HyperV1
except where the Notes contain “QA”
21
Starting with NetBackup 7.7, Hyper-V policies allow for automatic virtual machine
selection. Queries are built around virtual machine attributes to determine which virtual
machines to back up. These queries can be combined with filters to create more
complex queries and limit the results.
If you want to use the new intelligent policy functionality instead of performing a
manual configuration, set the Virtual machine selection to Select automatically
through query. In this query builder, you build the virtual machine selection query. If
you do not select any query filters, the default behavior is to discover all virtual
machines, and back them all up.
The slide shows some examples of possible virtual machine selection queries. Some
examples show queries that use multiple query filters that are combined to narrow the
resulting virtual machines.
B-21
Hyper-V policies: Running a test query
22
When your query is formed, there is a Test Query button to execute and test the query.
After the test returns, the Test Query Results display every virtual machine found, and
identify whether the current filter value results in the virtual machine being included or
excluded. The slide highlights the results that were included, meaning that those virtual
machines matched the query, and would be backed up by this backup policy.
If the query is not working as desired in providing the correct virtual machines for the
policy, the query can be modified and retested.
In an environment with large numbers of virtual machines, a query can take many
minutes. During that duration, the console cannot be closed or used to monitor other
operations. A command line utility, nbdiscover (found in the NetBackup bin
directory) can be used to check the search terms of a query outside of using the
NetBackup console. This frees the console for monitoring and other work.
B-22
Hyper-V policies: Clients and Backup Selections list
23
When you use manual virtual machine selection, the Backup Selections list simply
shows ALL_LOCAL_DRIVES.
When you use automatic virtual machine selection, the virtual machine selection query
that was created is listed under the Backup Selections list, as shown in the slide:
hyperv:/?filter=Powerstate Equal poweredOff
In either circumstance, the policy backs up all local drives from each listed virtual
machine.
B-23
Hyper-V policy tab: Optimizations
24
B-24
Hyper-V policy tab: Primary VM identifier
How NetBackup
identifies VM’s
25
This setting specifies the type of name by which NetBackup recognizes virtual
machines when it selects them for backup.
• VM Hostname: Specifies the network host name for the virtual machine. The host
name is available only when the virtual machine is running. If you select VM
hostname but the virtual machine is not running at the time of the backup, the
backup may fail.
• VM Display Name: Specifies the name of the virtual machine as it appears in the
Hyper-V Manager console.
Note: NetBackup for Hyper-V does not currently support the virtual machine display
names that contain non-US-ASCII characters. If the display name contains such
characters, select VM hostname or VM GUID.
• VM GUID: Specifies the unique ID assigned to the virtual machine when the virtual
machine was created.
Keep the following considerations in mind when making your selection:
• If you create a policy and then change the Primary VM identifier, you may have to
delete the virtual machine selections on the Clients tab. Otherwise, NetBackup may
no longer be able to identify the virtual machines to back up.
• When creating virtual machines, use the same name for both the host name and the
display name. If the Primary VM identifier is changed, the existing entries on the
Clients tab still work.
B-25
• For the policies that select virtual machines automatically: A space in a display name
is converted to "%20" in the test query results if the virtual machine is listed as
included.
• When selecting VM’s by Display Name: certain characters are not allowed in the
virtual machine display name by NetBackup. If the name contains the wrong
characters, the backup may fail. For NetBackup, the following characters are allowed
in virtual machine display names:
• Uppercase and lowercase ASCII characters
• Numbers
• Period (.)
Note however that a display name cannot end with a period.
• Hyphen (-)
• Underscore (_)
• Plus sign (+)
• Percent sign (%)
• Left and right parentheses ( ( and ) )
• Spaces
Note: No other characters are allowed.
B-26
Hyper-V policy tab: VSS and cluster settings
27
B-27
Hyper-V policy tab: Advanced option
28
The Provider Type configuration parameter determines the type of VSS snapshot
provider that creates the snapshot:
• Auto: Attempts to select the available provider in this order: hardware, software,
system.
• System: Uses the Microsoft system provider, for a block-level copy on write
snapshot. Unlike the Hardware type, the System provider does not require any
specific hardware.
• Software: This option is not used in the current NetBackup release, but may provide
future functionality.
• Hardware: Uses the hardware provider for a disk array. A hardware provider
manages the VSS snapshot at the hardware level by working with a hardware
storage adapter or controller.
The Snapshot Attribute parameter determines the type of VSS snapshot that is created.
• Unspecified: Uses the default snapshot type of the VSS provider.
• Differential: Uses a copy-on-write type of snapshot. For example, to back up an EMC
CLARiiON array with an EMC CLARiiON SnapView Snapshot, select Differential.
• Plex: Uses a clone snapshot or mirror snapshot. For example, to back up an HP EVA
array with an HP EVA Snapclone snapshot, select Plex.
B-28
Sequence of Hyper-V Backup
Phase Description
Phase 1: NetBackup master server initiates the backup.
Initiate
Phase 2: NetBackup client on the Hyper-V server initiates a snapshot.
Snapshot
Phase 3: • VSS Hyper-V writer quiesces the Windows VM and creates the snapshot on the
Snapshot Execution host volume.
• If the Hyper-V writer cannot quiesce the VM, the VM is placed in the Saved
state before creation of the snapshot.
Phase 4: • NetBackup client reads the data from the snapshot of the VM and transfers the
Data Movement data to the media server.
• NetBackup media server writes the data to the NetBackup storage unit.
Phase 5: If the VM was placed in the Saved state, Hyper-V returns the virtual machine to its
State Restore original state.
29
B-29
Topic: Performing and Monitoring Hyper-V backups
After completing this topic, you will be able to perform and monitor Hyper-
V backups.
30
After completing this topic, you will be able to perform and monitor Hyper-V backups.
B-30
Hyper-V backup example with client discovery
• The first parent job runs with the discovery host as Client and resolves virtual machines
with the query in the File list.
• Each virtual machine has a parent snapshot and child backup job.
31
When using automatic Hyper-V client selection, client discovery is required when the
backup runs.
An initial parent job runs the client discovery, showing the job’s client as the discovery
host, and the job’s file list as the query that is being used.
After this initial parent job, each virtual machine is displayed as a standard virtual
machine backup, which normally has an initial parent snapshot job and a child backup
job.
B-31
Limitations with Hyper-V Backups
SAN Client SAN Client feature must be installed on the Hyper-V server, not the VM.
NetBackup for Hyper-V does not support restores with the Fibre Transport data
SAN restores transfer method.
Linux file
Hyper-V provides no mechanism for quiescing file system activity on Linux virtual
system machine clients.
quiesce
32
Refer to the Veritas NetBackup for Hyper-V Administrator's Guide for complete
information on requirements, procedures, best practices and troubleshooting advice.
B-32
Topic: Performing Hyper-V restores
After completing this topic, you will be able to perform Hyper-V restores.
33
After completing this topic, you will be able to perform Hyper-V restores.
B-33
Initiating a Hyper-V restore
34
To restore a virtual machine, launch the Backup, Archive, and Restore console. This can
be launched on the master server or on the Hyper-V server.
1. Set the source and destination clients.
From the File menu, select Specify NetBackup Machines and Policy Type.
2. Set the Source client for restores as the virtual machine you wish to restore. Be sure
to identify the source client exactly as it was backed up (using the appropriate
hostname, display name or GUID)
3. Select the Destination client for restores. Always use a hostname as the
destination, never a display name or GUID. Note that this field is ignored for full VM
restores; for full VM restores the destination is specified in the restore wizard later
in the process.
4. Select the Policy type for restores, ensuring you select Hyper-V to display all Hyper-
V backups.
MS-Windows and Standard do not display backups from virtual machines that were
backed up with Hyper-V policies.
B-34
Selecting the Restore type
35
Select the appropriate restore type under the Select for Restore button:
• Normal Backups: This option is used to view and restore individual files.
• Virtual Machine Backup: This option is used to restore the entire virtual machine.
These options are shown in more details on the following slides.
B-35
File and folder recovery of Hyper-V virtual machine
36
The Restore type of Normal Backups is used to view and restore individual files.
Specify the destination as the virtual machine’s host name (not the display name or
GUID).
Note that restoring individual files to a virtual machine requires that the NetBackup
client is installed on that VM. Alternatively, restore to a shared folder that can be
accessed by the virtual machine client.
Note that you can restore Windows files to a Windows guest operating systems, but not
to Linux. Similarly you can restore Linux files to supported Linux guest operating
systems, but not to Windows.
If a Linux file system was not quiesced before the snapshot, some files may be
inconsistent.
B-36
Full VM Recovery of Hyper-V virtual machine
Notes:
• The source must be the VM identifier (host name, display
name, or GUID) that was used during the backup.
• The destination client field is ignored, and is selected later
in the Virtual Machine Recovery wizard.
37
The Restore type of Virtual Machine Backup is used to restore the entire virtual
machine.
In the Directory Structure pane, click on the Hyper-V backup, then click the check box.
You must select the entire virtual machine.
If you are restoring from physical tapes, click the Preview button to see which tapes are
needed for the restore.
When ready, click the Restore button.
B-37
Full Hyper-V VM Recovery Options
38
When you restore the virtual machine to its original location with the Overwrite virtual
machine option, note: The same virtual machine on the Hyper-V server is automatically
turned off and deleted before the restore. The .vhd or .vhdx files of the virtual machine
on the Hyper-V server are overwritten by the .vhd or .vhdx files from the backup image.
If any new .vhd or .vhdx files were created after the backup, those files are not
removed.
B-38
Notes on full VM restores on Hyper-V
39
A backup of the full virtual machine can be restored only to Windows Server 2008 or
later with the Hyper-V role enabled.
By default, the NetBackup client on the Hyper-V server does not have Windows
Administrator privileges. You can restore a full virtual machine from the NetBackup
server. You cannot restore a full virtual machine from a NetBackup client that does not
have Administrator privileges.
When you restore the virtual machine to its original location with the Overwrite virtual
machine option, note: The same virtual machine on the Hyper-V serve is automatically
turned off and deleted before the restore. The .vhd or .vhdx files of the virtual machine
on the Hyper-V server are overwritten by the .vhd or .vhdx files from the backup image.
If any new .vhd or .vhdx files were created after the backup, those files are not
removed.
When you restore the virtual machine to a Hyper-V server that has a virtual machine of
the same GUID, you must select the Overwrite virtual machine option. Otherwise, the
restore fails.
B-39
Notes on individual file restores on Hyper-V
Linux Windows
40
To restore files to a shared location on the virtual machine, note: Virtual machines must
be in the same domain as the NetBackup client and master and media server.
To restore Windows encrypted files, the NetBackup Client Service must be logged on as
Administrator on the target host for the restore. Under services on the control panel,
change the logon for the NetBackup Client Services from Local System Account to
Administrator.
B-40
Topic: Performing Hyper-V restores with the NetBackup
Add-in for SCVMM
After completing this topic, you will be able to perform Hyper-V restores
with the NetBackup Add-in for SCVMM.
41
After completing this topic, you will be able to perform Hyper-V restores with the
NetBackup Add-in for SCVMM.
B-41
Using the NetBackup Add-in for System Center Virtual Machine
Manager (SCVMM)
Supported:
• Recover VM to original or alternate location
• Monitor the progress of VM recovery
Unsupported:
• Restoring individual files, or to a staging location
• Generating a new VM ID or VM name during restore
42
NetBackup 8.0 introduces an add-in for the System Center Virtual Machine Manager
(SCVMM). NetBackup provides a Recovery Wizard in the SCVMM console to restore a
VM from its NetBackup backup image. In NetBackup 8.0, you can use the add-in to:
• Recover the full virtual machine to its original location or to an alternate location.
• Monitor the progress of recovery jobs that the add-in initiated.
Note that the NetBackup Recovery Wizard is for the restore of an entire VM, not for
restoring of individual files, and also does not support restore to a staging location. To
restore individual files from the VM backup, or to restore the VM to a staging location,
use the NetBackup Backup, Archive, and Restore interface.
Changes that are made through Hyper-V Manager on individual Hyper-V hosts or
clusters can take up to 24 hours to be reflected in the SCVMM Console. Until then, the
NetBackup add-in Recovery Wizard may not have the latest VM configuration state. In
that case, the Recovery Wizard's pre-recovery checks related to the VM’s location may
not be based on the most recent data in SCVMM.
Note also that the NetBackup 8.0 Administration Console introduces enhancements for
restoring a VM, which are not provided in the SCVMM add-in Recovery Wizard:
• A new VM GUID is generated by default when you restore a VM to an alternate
location.
• A new VM display name can be specified when you restore a VM.
B-42
Running the recovery wizard: VM selection
43
The following slides show the NetBackup add-in being used to restore a Hyper-V virtual
machine. This screenshot shows the first screen in the recovery wizard: Virtual Machine
Selection.
First, use the drop-down list to select the master server that made the backup. If the
master server is not in the drop-down, you must add the server to the master server
list.
Next, for the VM Identifier, enter the display name, host name, or GUID of the virtual
machine that you want to restore. Note: This field is not case-sensitive.
When you are done, click Next to go to the next screen of the wizard.
B-43
Running the recovery wizard: Backup image selection
44
By default, the most recent backup image is displayed, listing the information about the
VM backup image.
Click Select Another Image option to select a different backup image. Use this option to
find a backup image, then select the image in the lower pane and click Select Backups
can easily be viewed by date ranges: Last 7 Days, Last 14 Days, Last 30 Days, or by
setting a custom date range.
The Virtual Machine Attributes lists the information about the VM at the time it was
backed up. Virtual Machines Files lists the files that are included in the VM image.
B-44
Running the recovery wizard: Restore options
45
The screenshot shows the Restore Options screen in the NetBackup Recovery Wizard
for SCVMM.
The VM identifier is given, and cannot be changed in this recovery wizard in NetBackup
8.0. Use the NetBackup Backup, Archive, and Restore interface to restore a VM while
simultaneously changing the restore VM identifier used.
Also listed is the Hyper-V server on which to restore the VM. The default is the original
server, however this can be changed by clicking the Change button.
You can set the restore destination, which is set to the original location, by default. Click
Browse to change it. Note: To create a new directory for the restore location, click the
Explore directory link at the bottom of the Select Destination Folder dialog.
Administrator privileges may be required.
If a virtual machine with the same display name exists at the destination, that VM must
be deleted before the restore begins. Otherwise, the restore fails. Select the Overwrite
existing virtual machine option to delete the existing VM.
B-45
Running the recovery wizard: Review settings
46
Use this screen to review the settings that are used for the recovery and to start the
recovery.
Click the Recover button to start the restore job.
B-46
Checking the status of a recovery job
47
In the SCVMM console, open the Jobs workspace to view Running jobs. The Status
column shows the job’s percentage completion.
B-47
Listing recent recovery jobs
48
For a listing of recent jobs and past jobs, click History, and select a time range from the
top ribbon.
B-48
Lesson summary
• Key points
– In this lesson, you learned about virtual machines and support for virtual machines in Hyper-V.
– You also learned how to configure NetBackup to protect Hyper-V virtual machines, and backup Hyper-V
virtual machines.
– Finally, you learned how to restore Hyper-V virtual machines in the NetBackup interface, as well as the
NetBackup Add-in for SCVMM.
• Reference materials
– NetBackup for Hyper-V Administrator’s Guide
– NetBackup Add-in for Microsoft SCVMM Console Guide
– http://www.veritas.com/support
49
For more information about the topics discussed in this lesson, refer to the resources
listed on the slide and remember to check the Veritas support Web site frequently.
B-49
End of presentation
B-50
Veritas NetBackup 8.1: Administration
© 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC
or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.
C-1
Topic: Configuring NetBackup BasicDisk Staging
After completing this topic, you will be able to configure disk staging with
BasicDisk storage units.
After completing this topic, you will be able to configure disk staging with BasicDisk
storage units.
C-2
Understanding BasicDisk staging
Final
2. Relocation destination
Source: Disk staging storage unit
storage unit schedule
1. Backup
Source: Policy 3. Deletion
When: High watermark
1 3 is reached
Temporary
storage for disk
staging
Client
Disk staging provides a method to initially send backup images to a disk and then later
copy the images to another media type. The media type for the final destination is
typically tape, but can also be disk. Although BasicDisk storage units can perform disk
staging, NetBackup’s preferred method of disk staging is using Storage Lifecycle Policies.
NetBackup BasicDisk disk staging is conducted in three separate operations:
1. Clients are backed up by a policy that specifies a BasicDisk storage unit as the
backup destination. The policy’s schedule specifies when this operation occurs.
2. Images are then copied from the BasicDisk storage unit to the final destination
storage unit. The images are duplicated based on the relocation schedule configured
in the BasicDisk storage unit configuration.
3. The images will continue to exist on both the disk staging storage unit and the
destination storage unit, until either the image expires, or the BasicDisk storage
unit’s high water mark (HWM) is reached. Reaching the HWM indicates that the
storage unit is full, at which point it pauses the backup, finds images that have been
successfully copied to the destination storage unit, and expires these image copies.
Images are deleted until the low water mark (LWM) is reached, or until there are no
more valid images to expire.
Although NetBackup 8.1 documentation has stated that oldest images are deleted first,
this is not correct. For more information, refer to Article 100037434: Documentation
error: image deletion on a Disk Staging Storage Unit (DSSU) when the High Water Mark
(HWM) is reached does not work as documented, found online at
http://www.veritas.com/docs/100037434.
C-3
Temporary staging area
To configure a BasicDisk storage unit for disk staging, first create the BasicDisk storage
unit. Alternatively, you can modify an existing BasicDisk storage unit.
Within the properties of a BasicDisk storage unit, you mark the Enable Temporary
Staging Area. Copy data to its final destination according to its staging schedule. check
box. When you mark this check box, the Staging Schedule button becomes active.
BasicDisk storage units configured for staging require a staging schedule, which is
configured by clicking the Staging Schedule button.
C-4
Disk staging schedule attributes
The Staging Schedule button opens the Add Schedule - Disk Staging dialog, which looks
similar to the scheduling dialog when configuring policies. Parameters include:
• Name: Defaults to (and is required to be) the name of the storage unit.
• Priority of relocation jobs started from this schedule: Specifies the priority assigned
to duplication jobs for this policy, ranging from 0 (default) to 99999 (highest
priority).
• Final destination storage unit: The name of the storage unit where the images are
copied from the disk staging storage unit.
• Final destination volume pool: The name of the volume pool on the final
destination storage unit where the images are to be copied, if the final destination is
a Media Manager storage unit (tape), or is set to Any Available.
• Final destination media ownership: The owner of the backup images after the
relocation process.
• Use alternate read server: Specifies the server to be used to read a backup image
that was originally written by a different media server. Veritas offers a number of
products, such as Veritas Cluster Server and Volume Replication, that enable two or
more computers to access a common set of disk-stored data.
Notice that similar to a policy’s schedule, either a calendar or frequency based schedule
type can be selected.
C-5
Disk staging schedule start window
The Start Window tab provides control for setting time periods during which NetBackup
can start the duplication process of copying backup images on disk to its final
destination. Just like a policy schedule, this is a start window, and although duplication
jobs will start within this time window, they do not need to complete within the
window.
C-6
Manual relocation of a BasicDisk staging storage unit
A relocation schedule may be started manually to copy images to the final destination
before the schedule is due to run.
To initiate a relocation schedule:
1. In the NetBackup Administration Console, select NetBackup Management > Storage
> Storage Units.
2. In the right pane, select a BasicDisk staging storage unit.
3. Select Actions > Manual Relocation to Final Destination to initiate the schedule.
If the relocation schedule finds data that can be copied, NetBackup creates a jobs to
copy the data to the final destination storage unit.
The image then exists on both storage units until the disk staging storage unit becomes
full and the oldest images are deleted.
C-7
Staging jobs for a BasicDisk staging storage unit
The Activity Monitor in the NetBackup Administration Console can be used to monitor
disk staging jobs. The slide shows two Backup jobs that were run to the BasicDisk
staging storage unit, job IDs 174 and 175.
At a later point in time, the disk staging job runs. It is listed as type Backup, and has the
Job Policy listed as _DSSU_POLICY_storage_unit_name. This is job ID 177.
A child job with type Duplication is listed under that backup job, with job ID 178. This
job may have many backup images associated with it, all of which are being copied from
the original storage unit, in this case master_bdisk_stu, to the destination storage unit,
in this case master_tape_stu.
C-8
End of presentation
C-9