Professional Documents
Culture Documents
8.1.2: Administration
(Lessons)
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
About this course .........................................................................................................................0-2
Education and support resources ...............................................................................................0-6
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.2: Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
0-1
This course is designed to help technical professionals responsible for the design,
configuration, operation, monitoring, or support of Veritas NetBackup 8.1.2.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
0-2
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
0-3
The lessons covered in the NetBackup 8.1.2 Administration course are displayed on the
slide. The course is structured by going through a number of general steps:
• Lessons 1-5 set the framework for understanding NetBackup, covering basic concepts
such as storage units, backup policies, and how to perform backups and restores of
file systems.
• Lessons 6-9 show how to configure and manage various storage types, including
AdvancedDisk, NetBackup deduplication, and tape libraries.
• Lessons 10-11 cover the protection and recovery of virtual machines, highlighting
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
0-4
After completing this course, you will be able to perform the tasks listed on this slide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
0-5
This topic describes Veritas Education offerings and other Veritas resources
available to help you design, configure, operate, monitor, or support Veritas
NetBackup 8.1.2.
This topic describes Veritas Education offerings and other Veritas resources available to
help you design, configure, operate, monitor, or support Veritas NetBackup 8.1.2.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
0-6
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:
0-7
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.
0-8
MyVeritas is your single destination that allows you to access all of your Veritas
enterprise services and information. Visit https://www.veritas.com/support/en_US.html
to view this page.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
0-9
Visit the Veritas Education Services page to learn more about Veritas product training
and certification at: https://www.veritas.com/services/education-services.html. This
slide displays links related to curriculum paths, Veritas certification, and other training
related information.
0-10
End of presentation
0-11
© 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.
1-1
1-2
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-3
After completing this topic, you will be able to discuss considerations for
data protection, and identify the components of a NetBackup environment
and their functions.
1-4
Your data backup is the most obvious requirement. However, in a business it is not
sufficient just to have backup copies of files; most valuable asset you have. If you lose it,
your business is in peril. Therefore, you must be able to protect it:
• You must minimize redundancy to keep the time required to back up your data
within a reasonable window and to reduce storage space required.
• You must be able to find your backed up data and be able to restore it quickly when
needed.
• You must be able to scale up your solution to manage your entire organization -
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
1-5
Synchronous Clustering
Traditional replication
Snapshot Standard
backups Asynchronous technologies restore
Snapshot replication
technologies Bare Metal
Restore
Not all data is of equal importance. You can afford to wait for some data; you can
reconstruct or even abandon some data, if necessary; and you must have some data as
soon as possible. Data protection specialists talk about two important objectives that
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• 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.
1-6
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:
1-7
The systems that have data to be backed up are called clients. Veritas NetBackup Client
software must be installed on each client. Veritas NetBackup server software that
controls the environment and accesses backup storage devices comes in a few different
flavors. A single host can provide more than one of these server roles.
• The master server controls the backup and recovery activities for the clients
assigned to it. Master servers track what files are backed up to which backup media.
Additionally, the master server centralizes services that manage and allocate the
resources required for all NetBackup operations. This includes the NetBackup
database (sometimes abbreviated as NBDB), which centralizes information about
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
the backup environment. The NBDB is shown on the slide as a dual-colored cylinder,
next to the master server.
• Media servers have some form of storage attached to them—either directly or
through the network. Media servers perform the writing and reading of data to and
from media (disk or tape). They combine clients’ data into GNU tar files called
backup images. One master can control several media servers.
• Clients include all hosts that have data backed up, including the media server and
master server themselves. Clients can be both physical servers, or virtual servers. In
many cases the NetBackup client software is installed on the client system, however
in some cases, such as with virtual machines, the NetBackup client software may not
be necessary.
1-8
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.
recommends that the master server role should not be mixed with other roles, such
as a media server, OpsCenter server, or run CPU intense applications, on the same
server. If it is performing some minimal media server tasks, definitely avoid CPU
intense activities such as hosting a Media Server Deduplication Pool (MSDP).
In either case, everything under the control of an individual master server, including the
media servers or storage hardware, is considered part of a single NetBackup domain.
1-9
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.
• A single OpsCenter server can communicate with every master server and so help
you coordinate all of your NetBackup domains.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-10
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
1-11
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
Backup policies provide the instructions that NetBackup follows to back up clients. A
backup policy can apply to one or more clients. The best approach is to group the clients
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: What type of client to back up? Where to
store the backup? How should the files be backed up? Are there any special backup
behaviors?
• Schedules answer questions, such as: What is the backup type? When and how
frequently to perform the backup? How long is the backup data retained?
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
More recent versions of NetBackup have introduced new policy tabs to assist with
application-specific backup settings. In NetBackup 8.1.2, these includes the following:
• Oracle policies includes the Oracle and Instances and Databases tab, and removes
the Clients tab.
• MS-SQL policies includes the Microsoft SQL Server and Instances and Databases
tabs, and removes the Clients tab.
1-12
1-12
Tapes
Disk
Client’s
backup data
(in an image)
Local SAN NetBackup appliance
disk storage or OST-based storage
Cloud
13
The backup data from a client is stored as a backup image, and must be saved
somewhere. Removable media, such as tape, is very cost effective. Robotic libraries
automate operation, and can be shared to provide redundancy and efficient allocation
of resources. Although disk is becoming more popular, removable media still serves a
valuable purpose, such as for long term or off-site storage. Additionally, many modern
tape libraries and removable media devices have competitive performance with disk.
Images can be stored on local or networked disks for rapid access, but increasingly
complex permanent storage solutions are built around disk – such as deduplication –
which can be used alone, or in combination with removable media. You can configure
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-13
NetBackup 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
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A critical NetBackup component is the image database, which stores backup image
metadata. This metadata is stored in two locations: the image header data is stored in
the relational database (NBDB), and the image file list is still stored as flat files in the
NetBackup configuration files. Because the image file lists contain the path to every file
backed up, this is usually the largest component of the NetBackup catalogs.
1-14
NetBackup
logs and NetBackup
reports 4
master
1 server and
catalog
NetBackup
3
media
server
2
NetBackup Storage
Client Backup
client destination
data image
15
Using NetBackup, you create policies and schedules for backing up data periodically
(such as every hour or every day). The policy and schedule information is maintained in
the NetBackup database. The policy identifies how the backups occur, where the
backups occur, when the backups occur, which clients are backed up, and which files
and directories are backed up from those clients. The following flow is described on this
diagram:
1. When a policy is run, the master server interprets the policy, allocates resources,
and connects to the requested media server.
2. The media server prepares the allocated storage resources and then passes on the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
requirements of the backup to the client. The client processes the files to be backed
up and transfers them in the form of a tar backup image over the network to the
media server. The media server writes the file image to the allocated storage.
3. The media server also passes information about the backup to the master server
which then stores the information into the backup catalog.
4. During the backup status information is sent to the NetBackup master server, and
NetBackup keeps status information in various log files, enabling you to monitor or
report on the backup. Information is also pulled from the master server by the
OpsCenter server on a periodic basis, based on the OpsCenter configuration.
1-15
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 about what
files and folders have been backed up, and provides the information that the
administrator will then use to select which data to restore.
2. The NetBackup master server uses the information in the NetBackup database to
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
identify where the backup images are stored, and uses information supplied by the
administrator to decide where they should be restored on the NetBackup client.
3. The appropriate image is retrieved from storage by the media server, and the
selected files are extracted onto the client.
4. Because NetBackup maintains status information about restores in its log files, you
can monitor and report on restores just like backups. Information is also pulled from
the master server by the OpsCenter server on a periodic basis, based on the
OpsCenter configuration.
1-16
17
One of the hallmarks of enterprise IT is its heterogeneity. The wide variety of platforms,
applications, and infrastructure often grows with the size of the enterprise. NetBackup
supports a vast array of environments and integrates with every layer of the
infrastructure stack to unify your entire data protection strategy.
1-17
1-17
After completing this topic, you will be able to describe the NetBackup
appliance offerings.
18
1-18
Optimized Hardware
Redundant Storage
19
1-19
Up to
1-250TB Up to 1374 TB*
1PB
Up to 1920 TB*
Up to 294TB
Media Server Cloud Catalyst
14TB-27TB 240TB
229TB
0.5-16TB
Media Server
4TB
Master/Media Media Server
Server Enterprise Appliance with storage Enterprise Appliance with storage
Master Server with storage
• NetBackup 5240: A scalable integrated backup appliance that can function as either a
master or a media server and can scale from 4 TB to 294 TB of storage.
1-20
1-21
22
The NetBackup 5240 fulfills the needs of the low to mid-range performance and
capacity tiers in the NetBackup Appliance product line. It improves performance and
greatly increases the maximum capacity from the previous generation, the NetBackup
5230. As with the previous NBU52xx generations, the NetBackup 5240 appliance
supports internal storage as well as external storage shelves, and can be configured as
either media server, master server or both.
The NetBackup 5240 storage shelf supports SAS-3 as well as SES-3, significantly
improving bus speed as well as supportability. Each shelf formats to 49.14 TB. Since the
5240 supports up to 6 shelves, total storage options include 53 TB, 102 TB, 151 TB, 200
TB, 249 TB and 298 TB. This assumes the use of a 4 TB appliance, which is the norm
when using expansion shelves. The 14 TB and 27 TB appliances are designed to be used
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-22
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)
23
Enterprise scale NetBackup 5330 appliances start at 120 TB 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. In 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.
1-23
• Software and appliance functionality is normally equivalent, but may not be identical
Compatibility • Refer to http://netbackup.com/compatibility, in the NetBackup Appliances section.
24
appliances, disk pools or tape libraries used solely to hold replicated data.
Licenses are perpetual and transferable. Which means, you don’t pay the cost of the
deduplication engine again every time you refresh hardware. It also means that existing
DPOO licenses for disk pools can be used if you migrate from legacy servers to
appliances. Licenses are based on the amount of data you protect, not the capacity of
the appliance. Which means you can buy an appliance with extra storage capacity with
an eye towards future growth without paying for storage you are not using. 5230
Appliances can also be licensed as traditional Master or Media servers if, for example,
you will not be using the appliance to deduplicate any data.
1-24
1-25
After completing this topic, you will be able to navigate the NetBackup
Administration Console.
26
1-26
Details pane
Object tree
27
• Object tree (left) pane with various navigation branches. The NetBackup
Management branch contains the utilities used to monitor activity, run and view
reports, configure policies and storage units, manage backup images, and perform
catalog backups. Host properties for the master server, media servers, and clients
can be remotely modified using this branch. The Media and Device Management
branch contains the utilities used to manage the volumes, pools, and devices that
NetBackup uses to store backups.
• Details (right) pane, contains the configuration wizards and details specific to the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-27
28
The Jobs tab in the Activity Monitor displays information about NetBackup queued,
active, waiting, suspended, incomplete and completed jobs. Functions you can perform
on jobs include canceling, suspending, resuming, or restarting a job. The following tabs
are visible in the details pane of the Activity Monitor:
• The Jobs tab: If you double-click a job listed under the Jobs tab, you obtain valuable
job detail information, including policy, file list, status, kilobytes written, number of
files written, percent complete, and start, elapsed, and end times, which are used to
derive kilobytes per seconds statistics.
• The Daemons tab: Provides status and control for those programs that typically start
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-28
bpconfig
29
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.
1-29
30
1-30
After completing this topic, you will be able to use the NetBackup web user
interface, discuss Role-Based Access Control (RBAC), and navigate the
Veritas Smart Meter portal.
31
1-31
32
NetBackup 8.1.2 introduces a new web user interface, which provides the following
features:
1-32
Certificates
Displays information about the host ID-based security
certificates in your environment.
Tokens
Displays the information about the authorization
tokens in your environment.
33
The NetBackup dashboard provides a quick view of the details that are related to your
role in your organization.
• Jobs: Lists job information, including the number of active and queued jobs, and the
status of attempted and completed jobs.
• Security events: The Access history view includes a record of login events. The Audit
events view includes events that are related to tokens, certificates, and the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-33
Access rules associate a user or a user group with a role and an object group.
Object groups define the assets and the NetBackup objects a user can access.
RBAC is only available for the web UI and the APIs. Other access control methods for NetBackup are not supported for the web UI and APIs, with the
exception of Enhanced Auditing (EA). Users that are configured with EA have full permissions for the web UI and APIs. You cannot use the web UI if you
have NetBackup Access Control (NBAC) enabled.
34
The NetBackup web user interface (web UI) provides the ability to apply role-based
access control to grant access to the web UI. This access control includes the tasks a
user can perform and the assets the user can view and manage. Access control is
accomplished through access rules.
• Access rules associate a user or a user group with a role and an object group.
Multiple access rules can be created for a single user or group, allowing for full and
flexible customization of user access.
• Roles define the permissions a user has.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Object groups define the assets and NetBackup objects a user can access. You can
use object groups to define groups of assets or application servers or to indicate the
protection plans that users can view or manage. For example, you can grant access
for VMware administrators by creating an object group with specific VMware
application servers. Also add to the object group the specific protection plans that
the VMware administrator can choose to protect VMware assets.
Note: RBAC is only available for the web UI and the APIs. Other access control methods
for NetBackup are not supported for the web UI and APIs, with the exception of
Enhanced Auditing (EA). Users that are configured with EA have full permissions for the
web UI and APIs. You cannot use the web UI if you have NetBackup Access Control
(NBAC) enabled.
1-34
USER
AUDIT
RBAC users can perform common tasks for their business role, but are restricted
from accessing other NetBackup areas and features.
PASSWORD
SECURITY
PYSICAL
SYSTEM RBAC is available in the NetBackup web user interface and NetBackup APIs.
CONTROL
LOGIN
ACCESS
IDENTIFICATION
AUTHORIZATION
ROLE-BASED
CREDENTIALS
KEYS
READER
LOCKS
35
The following are the important features of Role Based Access Control (RBAC):
• Predefined roles in RBAC allow users to perform common tasks for a system
administrator, backup administrator, or workload administrator. Or, create custom
roles to fit the role of your users. Root users and administrators still have full
permissions in all NetBackup interfaces and in the APIs.
• RBAC users can perform common tasks for their business role, but are restricted from
accessing other NetBackup areas and features. RBAC controls the assets that users
can view or have access to. For example, a backup administrator can only manage
backup images and jobs for the assets for which they have been given access.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• RBAC is available in the NetBackup web user interface and NetBackup APIs, which are
installed with NetBackup starting with version 8.1.2.
• NetBackup audits successful RBAC events. These events include when access rules,
roles, or object groups are created, updated, or deleted.
• RBAC currently supports a limited number of workflows. In NetBackup 8.1.2, this
support includes access control of VMware and Cloud workflows.
• RBAC settings are protected with the NetBackup catalog.
• Enhanced Auditing is supported across all interfaces. You can continue to use the
authorization (auth.conf) configurations with the NetBackup Administration Console
and the CLIs. With these older interfaces you can manage access to workflows that
are not yet supported in the NetBackup web UI and NetBackup APIs.
1-35
Backup Administrator
• Manage all jobs activity.
• Configure NetBackup to send email notifications to the ticketing system when
certain job failures occur.
• Configure protection plans for the workload administrator.
• View the usage reporting details on backup data size for NetBackup master
servers.
Workload Administrator
• Manage the jobs that they initiate.
• Manage the assets they are granted access to.
• Monitor protection status and subscribes assets to protection plans.
• Perform the recovery for assets they manage.
If the default NetBackup roles for RBAC do not meet your needs, you can configure a role with custom role permissions. Note, however, that customer
roles do have certain limitations.
36
With the NetBackup RBAC default roles you can delegate for tasks like NetBackup
security management, protection plan configuration and job management, and
protection and recovery of assets. Role permissions only determine what kinds of
actions a user can perform. A user’s access rules also determine the assets, application
servers, or protection plans (defined in an object group) that a user can view or manage.
For example, if a user has recovery permissions, that user can only recover assets for
which they are granted access.
• Manages role-based access control. This user can delegate access to NetBackup. This
task includes managing the users that can access NetBackup, the role or permissions
that users have, and the NetBackup assets that users can access.
• Oversees the security management. This task includes managing NetBackup hosts
and certificates, managing global security settings, and viewing security events.
Backup administrator: The backup administrator performs the following tasks in the
NetBackup environment:
• Manages all jobs activity. Monitors all job operations. Able to cancel, suspend,
resume, restart, and delete jobs.
• The backup administrator can also configure NetBackup to send email notifications to
1-36
If the default NetBackup roles for RBAC do not meet your needs, you can configure a
role with custom role permissions. Note that customer roles do have certain
limitations.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-36
While creating custom roles, enable minimal number of permissions that allow a user to sign in and use the Web UI
37
• Some permissions are only available with default RBAC roles or for custom roles
configured with the NetBackup APIs.
• A user can only manage Hosts settings, if that user has the Security administrator
role.
• A user can only manage Alerts and notifications and view Usage reporting, if that
user has the Backup administrator role.
• A user with the Security administrator role also has certain “view” permissions so
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
that user can find and add assets, application servers, and protection plans to an
object group. If you want a user with a custom role to create access rules, be sure
to select the appropriate view permissions for the custom role.
• Some individual permissions do not have a direct correlation with a screen in the
web UI. Users that attempt to sign in but only have a permission of this kind receive
an “Unauthorized” message. When you create custom roles, be sure to enable the
minimal number of permissions so the user can sign in to and use the web UI.
1-37
The Usage reporting application lists the size of the backup data for the NetBackup master servers in your organization.
This reporting is useful for planning when you use capacity licensing. NetBackup gathers and reports usage and trend
information on a weekly basis.
Usage reporting does not apply to the traditional licensing method and for manually generated capacity license reports.
38
The Usage reporting application lists the size of the backup data for the NetBackup
master servers in your organization. This reporting is useful for planning when you use
capacity licensing. NetBackup gathers and reports usage and trend information on a
weekly basis. This application also includes a link to the Veritas Smart Meter. This portal
allows NetBackup customers to proactively manage their license use through real-time
visibility of consumption patterns. Usage reporting does not apply to the traditional
licensing method also If you manually generate capacity license reports, the data does
not display in the usage report in the NetBackup web UI. Only automatic, scheduled
reports display in the web UI. Policy types supported for usage reporting are: BigData,
Informix, Oracle, VMware, MS-Exchange-Server, MS-SQL-Server, Standard, Hyper-V,
NDMP, and Sybase.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-38
Accurate, near real-time reporting Usage trends that are shown in a Consumption assessments to alert
of terabytes protected graphical display before licensed capacity is
exceeded
39
Veritas Smart Meter helps you manage your NetBackup deployment more efficiently,
spot trends, and plan for the future. With accurate, near real-time reporting, it reveals
the total amount of data that is backed up. Smart Meter alerts you if you are close to
exceeding your licensed capacity limits. Smart Meter requires Veritas NetBackup 8.1.2
or later. Smart Meter provides:
1-39
40
There are multiple ways to access the Veritas Smart Meter portal:
1. Open a web browser, enter the portal address https://taas.veritas.com and then
press Enter. The Veritas Account Login screen is displayed. Note that you must have
a Veritas Account Manager ID that is linked to your Veritas Entitlement Management
System to access and use Veritas Smart Meter.
2. Login to the Veritas NetBackup administration console, click the master server entry
located at the top of the object pane and then click Introducing Veritas Smart
Meter in the details pane. The Veritas Smart Meter window will be displayed. Click
the link located below Launch Veritas Smart Meter to launch the Veritas Smart
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Meter portal.
3. Login to the Veritas NetBackup web user interface, click the Launch Veritas Smart
Meter link included in the Veritas Smart Meter widget to launch the Veritas Smart
Meter portal. Alternatively, you can also click the Launch Veritas Smart Meter link
on the Usage and reporting page.
1-40
1-40
After completing this topic, you will be able to navigate the OpsCenter
console.
41
1-41
42
The OpsCenter server is a web server, and the user interface is accessed through a
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
standard web browser. OpsCenter server software is included with NetBackup software,
but is installed independently. Additionally, NetBackup 8.0 and later restricts the
OpsCenter software from running on a NetBackup master server. Although not strictly
required by NetBackup, some advanced features are only accessible through OpsCenter.
When run using the optionally licensed OpsCenter Analytics option, OpsCenter has
additional reporting functionality, which is discussed later in this lesson.
1-42
43
To access the OpsCenter console, start a web browser on a system that has network
connectivity to the OpsCenter server. Type the following URL:
https://opscenterhost/opscenter where opscenterhost is the fully qualified domain
name of the OpsCenter server or the IP address of the OpsCenter server.
Note: If there is a conflict due to an already existing Web server (for example, IIS on
Windows), OpsCenter may have chosen a different port number to avoid conflict. The
default OpsCenter web address may use this non-default port number; for example:
https://opscenterhost:port/opscenter. For more information, see the NetBackup
OpsCenter Administrator’s Guide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
To log on to the OpsCenter Console, provide the necessary logon credentials as follows:
1. Enter a user name and password, and select a domain from the Domain drop-down
list. For the initial login by an administrator, use the following values:
• User Name: admin
• Password: password
• Domain: OpsCenterUsers(vx)
2. Click Log On.
3. After the initial log on, change the user name and password. To change existing
passwords, navigate to Settings > User Preferences > MyProfile in OpsCenter.
1-43
44
Before you can use OpsCenter to monitor and manage your NetBackup environment,
you must configure data collection for NetBackup. To configure data collection for
NetBackup:
1. Add a master server to the OpsCenter console:
a. In the OpsCenter console, select Settings > Configurations > NetBackup.
b. Click Add, and fill in the fields. Optionally click the Test Connection button to
ensure the data is correct.
2. Enable data collection for a master server:
a. Use the check box to select one or more master servers from the Master Server
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Name column.
b. Click Enable Data Collection.
1-44
45
• With OpsCenter, you can only perform operational reporting; with OpsCenter
Analytics, advanced, business-level reporting is available. This includes the use of
existing reports as well as custom and custom SQL reports.
• There is a difference between reporting data availability in OpsCenter and
OpsCenter Analytics. The unlicensed product enables reporting on data from the
past 60 days; the licensed option has no limit on the age of reporting data.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
This course only covers OpsCenter. For additional information on using OpsCenter
Analytics, see the Veritas OpsCenter Administrator’s Guide and Veritas Education’s
OpsCenter training. Note: In prior releases of OpsCenter, the Java View Builder was only
available with OpsCenter Analytics. In OpsCenter 7.5 and later, the Java View Builder is
included with the base product.
1-45
• Key points
– In this lesson, you learned how to protect the data in your environment using NetBackup.
– In addition, you learned the basic terms that relate to NetBackup, and the NetBackup options and
agents used to customize your backup environment.
– You also learned about the NetBackup Appliance offerings.
– Finally, you learned to use the NetBackup Administration Console, the NetBackup web user interface,
the Veritas Smart Meter portal, and 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
46
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.
1-46
47
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.
1-47
47
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.
1-48
48
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-49
49
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-50
A. True
B. False
50
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-51
A. True
B. False
51
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-52
A. True
B. False
52
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-53
A. True
B. False
The correct answer is B. Access rules associate a user or a user group with a role and an object group.
53
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-54
A. BigData
B. SAP
C. NDMP
D. All of the above
54
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-55
A. BigData
B. SAP
C. NDMP
D. All of the above
The correct answer is A and C. Policy types supported for usage reporting are: BigData, Informix, Oracle, VMware, MS-
Exchange-Server, MS-SQL-Server, Standard, Hyper-V, NDMP, and Sybase.
55
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-56
56
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-57
The correct answer is B. Basic OpsCenter functionality is included with NetBackup, and additional functionality can be
added by purchasing the OpsCenter Analytics option.
57
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1-58
End of presentation
1-59
© 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.2:
Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2-1
2-2
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.
2-3
After completing this topic, you will be able to define the terms storage
device, storage unit, and storage unit group.
2-4
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,
storage units are a way of defining both the media servers and storage destination
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
for a backup. Note that a storage unit can be tape drives, a path to a disk volume, or
a disk pool (which can be deduplicated disk or cloud storage). Storage units are used
as a backup destination, a location where a backup policy sends a backup.
• Storage unit groups and Storage lifecycle policies (SLPs) are two additional storage
destinations that will be described. Storage unit groups are discussed elsewhere in
this lesson, and SLPs are discussed in the Duplicating Backups lesson.
Within a backup policy, you define a storage destination, which is where NetBackup will
send the backup data. This can be a storage unit, a storage unit group, or a storage
lifecycle policy, depending on your needs. You cannot send a backup directly to a
storage device that is not configured as a storage unit.
2-5
• Which media server copies the data from the client to the storage device.
• Which storage device is used for the backup.
During a backup, NetBackup stores the backup data on the storage units that were set
up during configuration. In the example on this slide, the storage unit specifies which
media server backs up the data (Media server 1 or Media server 2) and where the
backups are written (the basic disk storage or the tape library). Storage units for tape
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
libraries and robots are called Media Manager storage units, and are discussed later in
this course, in the Configuring Tape Storage lesson.
2-6
The slide lists disk storage types in NetBackup (listed by the corresponding disk type
identification categories used in NetBackup). Disk storage types include:
backup functionality for intelligent third-party disk appliances that support this API.
• PureDisk consists of a specialized disk pool and services that perform deduplication
of backup storage, and reside on a NetBackup media server or NetBackup appliance.
BasicDisk is included with NetBackup and does not require additional licensing. The
other disk types require the NetBackup Data Protection Optimization Option. This
lesson only covers the configuration of BasicDisk. For other disk types, refer to the
appropriate lessons in this course or the appropriate NetBackup documentation, as
listed on the slide.
2-7
After completing this topic, you will be able to configure and manage a
basic disk storage unit.
This is the Configuring and managing a basic disk storage unit topic.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2-8
bpstuadd -label
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:
• Copy and then modify the properties of an existing storage unit: Right-click a
storage unit in the details pane and select Copy.
3. Complete the entries in the New Storage Unit dialog box.
4. Click OK to add the storage unit to the configuration.
You can create and configure storage units from the command line using the
bpstuadd command. For a full explanation of this command, including syntax, see the
NetBackup Commands Reference Guide.
2-9
bpstuadd -label
10
When creating a Disk storage unit type, you must supply the following properties:
• Storage unit name: A unique name that is used in backup policies and schedules.
• Storage unit type: The type of storage that this storage unit uses, for example, Disk.
• On demand only: Specifies whether the storage unit is only available when a policy
attribute or policy schedule is explicitly configured to use this storage unit. The
storage unit will not be used when the Any Available storage destination is selected.
• Disk type: Specifies the type of disk storage unit to be created. By default: BasicDisk.
• Media server: Specifies the name of the controlling media server.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Absolute pathname to directory: Specifies the absolute path to the file system.
• View Properties button: Displays information about capacity and remaining space.
• This directory can exist on the root file system or system disk: Allows the directory
to exist on the root file system (UNIX) or system disk (Windows).
• Maximum concurrent jobs: The maximum number of backups that NetBackup can
concurrently send to this disk.
• Reduce fragment size to: Specifies (in MB) the largest fragments (underlying file
sizes) created when storing backups.
• High water mark: The threshold that signals that the disk should be considered full.
• Low water mark and Enable Temporary Staging Area: Used for disk staging storage
units. Refer to the NetBackup Administrator's Guide.
2-10
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 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.
2-11
12
• Images On Disk: This report shows which backup images exist on the storage units
selected.
• Disk Logs: This report shows log entries for the storage units selected.
• Disk Storage Unit Status: This report summarizes properties and capacity
information for the storage units selected.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Notice that these reports can be used for various disk storage types, however by
selecting a Disk Type of BasicDisk, you can view only the information for basic disk
storage units.
2-12
After completing this topic, you will be able to configure storage unit
groups.
13
2-13
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.
2-14
✓ ✓ ✓ ✓ ✓
15
Prior to the concept of storage unit groups, NetBackup used functions known as On
demand only and Any available to be able to send backups to different storage units,
based on availability. When configuring a backup policy, if you select Any_available as
the storage destination for your backup, backup data is directed to an available storage
unit designated as Any available. These are all storage units that are not marked as On
demand only. NetBackup tries locally attached storage units first, and if none are found,
the storage units are tried in alphabetical order. NetBackup uses the first storage unit
that meets the following requirements:
• The storage unit must not be designated as on demand only.
• The storage unit must have available drives.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• The storage unit must have available storage (tape or disk resources) resources.
When you configure a storage unit as On demand only, the storage unit is only used if it
is specified directly within the backup policy, or backup policy schedule. Since the
introduction of storage unit groups in NetBackup, it is no longer recommended to use
Any available as the means of sending backups to different storage units.
2-15
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.
2-16
17
To configure a storage unit group, provide a unique storage unit group name, and select
which storage units to add to that group. The order in which storage units are used
within a group depends on the storage unit selection option. In the Storage unit
selection area, you choose how storage units are selected within the group as follows:
• Prioritized: Choose the first storage unit in the list that is not busy, down, or out of
media.
• Failover: Choose the first storage unit in the list that is not down or out of media.
• Round Robin: Choose the least recently selected storage unit in the list.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Media Server Load Balancing: Choose the best available media server based on a
ranking system.
Note that the Media Server Load Balancing selection does not support basic disk
storage, and is discussed in more detail in the Configuring Disk Pools lesson.
2-17
Group priority:
1. ms1_tape_STU
2. ms2_tape_STU
3. ms3_tape_STU
ms1_tape_STU ms2_tape_STU ms3_tape_STU
Job 1 Job 3 Job 5
Job 2 Job 4 Job 6
Job 7
Job 8
18
The total number of concurrent jobs that can go to a specific storage unit will depend on
the storage unit’s configuration, specifically the maximum concurrent jobs that is
configured. The slide shows tape-based storage units (a library with two tape drives)
connected to each media server, however they could just as easily be disk-based storage
that accept two concurrent backups.
Prioritized storage unit groups choose the first storage unit in the list that is not busy
with other jobs, down (physically unavailable), or out of tape media (in the case of tape
libraries). It then fills that storage unit with active jobs, and then moves on to the next
available storage unit in the list. If all storage units are busy, any subsequent jobs will
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
queue, and wait for the next available storage unit in the group.
In the example on the slide, media server ms1 is shown with more memory and system
resources than media server ms2, which additionally has more resources than media
server ms3. Using a prioritized storage unit group means that ms1_tape_STU will always
be used first, until it is busy. Storage unit ms2_tape_STU will fill with jobs next, and
finally ms3_tape_STU.
2-18
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.
2-19
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.
2-20
Spanning STU-C
not
supported
STU-D
STU group 2
21
A backup may span storage units if a disk full condition is detected. Backups can span
from one BasicDisk storage unit to another BasicDisk storage unit if the storage units are
in the same storage unit group. The storage units must also share the same media
server. The following destinations support disk spanning:
• A BasicDisk storage unit spanning to a BasicDisk storage unit. These storage units
must be within a storage unit group.
• An OpenStorage or AdvancedDisk volume spanning to another volume in the disk
pool. These storage units innately support backup images spanning to multiple
volumes, since they use disk pools. This is discussed in further detail in the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2-21
22
Basic disk spanning is enabled in the media server’s Host Properties under Media, using
the Allow backups to span disk property. By default, 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.
2-22
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.
2-23
• 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.
2-24
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.
2-25
25
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.
2-26
A. Catalog
B. Policy
C. Storage unit
D. Selection list
26
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2-27
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.
27
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2-28
A. Failover
B. Priority
C. First-in First-out
D. Round Robin
28
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2-29
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.
29
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2-30
30
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2-31
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.
31
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
2-32
End of presentation
2-33
© 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 lesson in the Veritas NetBackup 8.1.2: Administration
course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-1
3-2
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.
3-3
After completing this topic, you will be able to explain how data protection
relates to a policy.
3-4
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:
3-5
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
Backup policies provide the instructions that NetBackup follows to back up clients. A
backup policy can apply to one or more clients. The best approach is to group the clients
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: What type of client to back up? Where to
store the backup? How should the files be backed up? Are there any special backup
behaviors?
• Schedules answer questions, such as: What is the backup type? When and how
frequently to perform the backup? How long is the backup data retained?
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
More recent versions of NetBackup have introduced new policy tabs to assist with
application-specific backup settings. In NetBackup 8.1.2, these includes the following:
• Oracle policies includes the Oracle and Instances and Databases tab, and removes
the Clients tab.
• MS-SQL policies includes the Microsoft SQL Server and Instances and Databases
tabs, and removes the Clients tab.
• VMware policies includes the VMware and Exclude Disks tab.
3-6
3-6
After completing this topic, you will be able to identify basic policy types,
and configure policy attributes.
3-7
Command Line
• Provided with bppolicynew command.
• Can be used in script-based policy setup.
3-8
bppolicynew
1. In the left pane of the NetBackup Administration Console, select Master Server >
NetBackup Management > Policies.
2. Perform one of the following:
• Select Actions > New > Policy.
• Right-click the master server in the All Policies pane and select New Policy.
The Add a New Policy dialog box is displayed.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3. Enter the name of your new policy and click OK. Notice that you can activate the
Backup Policy wizard by marking the Use Backup Policy Configuration Wizard check
box.
Your new policy is added with default settings.
You can copy an existing policy by selecting a policy from the list, right-clicking it, and
then selecting Copy To New. This is useful when you must establish multiple policies
that have similar properties. Refer to the NetBackup Administrator’s Guide for more
information about adding policies.
3-9
10
Attributes determine the basic characteristics of all the backups that NetBackup
performs for the policy. You can view and configure a policy’s attributes using the
NetBackup Administration Console.
• The Attributes tab answers the questions “How is the policy going to perform the
backup?” and “Where are the storage units and volume pools to which the backup
data is to be sent?”
• The Policy type determines the type of clients that can be part of the policy and, in
some cases, the types of backups that can be performed on the clients. Select the
Policy type from the drop-down menu.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-10
11
NetBackup installs all the options but the policy types available vary depending on the
licenses purchased. Each policy type offers a unique combination of attributes. The two
policy types shown on this slide are basic NetBackup policy types. Each of these policy
types is distinguished by the types of clients that can be part of the policy, and what is
backed up when a backup job is run.
• Standard policy type: Used for clients and file systems that are UNIX-based, this
includes UNIX, Linux, and Mac OS X 10.8, 10.9 and 10.10 clients.
• MS-Windows policy type: Used for clients and file systems that are Windows-based,
supported Windows operating system levels.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-11
12
The Policy storage drop-down menu specifies the default storage unit or storage unit
group for backups of this policy. This is the storage unit that is used by default by all
schedules in this policy. However, schedules may be configured to override the policy
storage destination.
The Policy volume pool drop-down menu specifies the volume pool for backups of this
policy. Select the desired volume pool name from the drop-down list. The list displays all
previously configured volume pools. Whenever a new volume is required for either a
robotic or stand-alone drive, it is allocated to NetBackup from the requested volume
pool. Policy storage and volume pools are covered in more detail in a later lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-12
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
3-13
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.
3. Click the Schedule tab.
4. Click the New button to access the dialog box that you use to build your schedule.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-14
15
Frequency: Specify how much time must elapse between the successful
completion of a scheduled task and the next attempt. In addition to hours, days,
and weeks, NetBackup 8.0 introduced the ability to set frequency in minutes and
seconds.
• Destination pane:
• Multiple copies: Used to create inline copies. This is discussed in the Duplicating
Backups lesson.
• Override policy storage selection and Override policy volume pool: Override
the storage unit or volume pool for this schedule, so that it differs from the one
specified in the policy’s Attribute tab.
• Retention: The time that the image is to be held in the images catalog. By
default, NetBackup does not mix retention levels on a single volume.
3-15
3-15
Full
16
• Full backup: A full backup backs up all files specified in the backup selections list ,
regardless of when the files were last modified or backed up. If you run incremental
backups, you must also schedule periodic full backups in order to perform a
complete restore.
• Differential incremental backup: A differential incremental backup backs up all files
specified in the backup selections list for the policy that have changed since the last
successful incremental or full backup. All files are backed up if no prior backup has
been performed. A complete restore requires the last full and all of the differential
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
incremental backups since the last full or the last full, the last cumulative
incremental and all of the differential incremental backups since the last cumulative
incremental.
• Cumulative incremental backup: Cumulative incremental backups back up all files
specified in the backup selections list for a policy that have changed since the last
successful full backup. All files are backed up if no prior backup has been performed.
A complete restore requires the last full backup and the last cumulative incremental.
Cumulative incremental backups generate more files per backup, but complete
restoration is quicker.
3-16
17
The Start Window tab provides controls for setting time windows during
which NetBackup can start automatic backups jobs, and users can initiate manual
backups or archives when using this schedule. Configure the start windows so that they
satisfy the requirements necessary to start a task or job. If the start windows closes
before the backup has started it does not run. Once a backup has started, it runs to
completion even if the start window closes. The start window is not used for manual
backups. For example, for backups, you can create a different window that opens each
day for a specific amount of time, or you can keep the window open all week.
For more information about the options on the Schedule dialog box - Start Window tab,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-17
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.
3-18
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.
3-19
20
number or select a value from the drop-down menu. Select a frequency of hours, days,
or weeks.
The Include Dates tab is displayed when Calendar is selected as the Schedule type,
3-20
3-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.
The Recurring Week Days option provides a matrix that enables you to schedule a task
for certain days of each week, weeks of each month, or days on particular weeks of the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
month. For example, use this option to schedule a task on the first and third Thursday of
every month. Or, schedule a task that runs the last week in every month. The week day
matrix is not a calendar; it is simply a matrix used to select days and weeks in a month.
A check mark entered for a day indicates that the task is scheduled to run on that day of
its respective week. By default, no days are selected. For example, to define specific run
days based on recurring days of the week, such as every Friday, click Fri on the matrix,
and every Friday is automatically selected.
The Recurring Days of the Month option provides a matrix that you can use to schedule
a task for certain days of the month. You can also schedule a task to occur on the last
day of the month, regardless of the actual date.
3-21
bpretlevel
22
The retention period in a policy’s schedule determines how long NetBackup retains the
backups images created by that schedule. NetBackup 8.0 and later supports 100
separately defined retention levels. The Retention Periods properties, found in the
master server host properties, define the length of time associated with each level. All
of these retention levels are configurable, with the exception of level 9 and level 25,
which have fixed retention period values. Veritas recommends leaving retention levels
0-8 at the default values. Change higher levels which are currently set to infinite, if you
want to customize. The following list describes the Retention Periods properties.
• The Units property specifies the units of time for the retention period. The list also
includes the special units: Infinite and Expires Immediately.
• The Retention Periods pane contains a listing of the current definitions for the 101
possible levels of retention (0 through 100).
• The Schedule Count column indicates how many schedules currently use each level.
If the retention period is changed for a level, it affects all schedules that use that
level.
• The Schedule(s) using this retention level pane contains a listing of the schedules
that use the currently selected retention level, and the policy to which each
schedule belongs.
3-22
3-22
After completing this topic, you will be able to specify which clients are to
be used in a policy.
23
3-23
silentclient.cmd
24
Before adding a client to a policy, ensure that the NetBackup software is successfully
installed on that client. There are five ways to distribute NetBackup client software:
3-24
25
The Clients tab contains the list of clients that are backed up or affected by this policy.
This answers the question, “Which system is to be backed up?” To add clients to a policy
using the NetBackup Administration Console, click the Clients tab and click New. You
are prompted to provide the name of the client, as well as the hardware and operating
system type. You can either select the Detect client operating system check box or
select the appropriate hardware and operating system for the client in the drop-down
menu.
Note: To be able to use the auto-detect feature, the NetBackup client software must
already be installed on the client, and the master server needs to be allowed to connect
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
to the client by having an appropriate SERVER entry in the client’s server list. This is
accomplished when you enter the master server name during the installation of the
client software on the host. For detailed instructions on adding a client to a policy, see
the NetBackup Administrator’s Guide.
3-25
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
3-26
• 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 each client. It is possible, however, to back up more than one
client (or policy) in parallel.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Related items are listed on the exclude and include lists. You can create an exclude list
on a client to specify files that you do not want to include in automatic and manual
backups of that client. You can also create an include list for a client to back up a file or
directory that would otherwise be excluded by an exclude list. Many administrators
have a standard exclude list that is copied to all clients, and then use include lists to
customize clients that have exceptions to the standard exclude list.
3-27
Windows UNIX
Creating a backup
Administration Console or bpplinclude
selections list
• Use one path per line
Entries • Maximum path length of 1,023 characters
• All paths must be absolute
Path restrictions Start all paths with a drive letter Start all paths with a slash (/)
Wildcards supported *, ? *, ?, { }, [ ]
28
When defining files for your policy, the backup selection list can be set using either the
NetBackup Administration Console or the bpplinclude command. It is important
that you follow the conventions and rules used to specify backup selection lists:
• Enter one path per line, with a maximum path length of 1,023 characters.
• All paths must be absolute. Local paths on Windows must start with the drive letter
followed by a colon and a backslash (:\). The drive letter can be either upper- or
lower-case . Network paths can be in UNC format, starting with
\\server\share\. Paths on UNIX must start with a slash (/), and are case
sensitive. Note: \\.\D: is valid for a raw partition backup on Windows.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Best practice: If the last component in the path is a directory, also follow it with a
backslash on Windows (\) or slash on UNIX (/). The trailing slash is not required but
serves as a reminder that the file path is a directory instead of a file (for example:
F:\workfiles\).
• Use wildcards to select files of a specific type or files with common naming
elements. For example:
• K:\tests\*.exe
• K:\tests\test*.txt
• C:\windows\system\log??_02
3-28
bpplinclude
29
The backup selections list under the Backup Selections tab names the files, directories,
directives, scripts, and templates that NetBackup includes in automatic backups of
clients covered by the policy. NetBackup uses the same backup selections list for all
clients backed up according to the policy. This answers the question “What is to be
backed up?”
To build a backup selections list when creating a policy using the NetBackup
Administration Console, click the Backup Selections tab and click New. You are then
prompted to provide a new path or directive. For example, you can use C:\ or /home
for a path and ALL_LOCAL_DRIVES for a directive. For detailed information on adding an
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
entry to the Backup Selections list, see the NetBackup Administrator’s Guide.
3-29
30
The ALL_LOCAL_DRIVES directive backs up all local drives, except for those drives that
use removable media. If used, this directive must be the only entry in the backup
selections list. For Windows clients, this directive automatically includes the system
state and shadow copy components, so including other directives is not necessary.
The Shadow Copy Components:\ directive specifies that all of the Volume Shadow Copy
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
component writers get backed up, backing up critical system-related components, such
as the registry, Active Directory, and other information not fully protected when backing
up the file system alone. The System State:\ directive can still be found, and is used for
versions which do not support Shadow Copy Components, such as Windows XP.
The NEW_STREAM directive is available when the Allow multiple data streams
attribute is enabled for the policy. This directive is discussed in greater detail in the
Optimizing File System Backups lesson. Refer to that lesson for further details.
Some directives apply only to specific policy types and appear only in backup selections
lists for those policies. NetBackup passes these directives to the clients along with the
backup selections list, which then perform appropriate action according to the directive.
3-30
3-30
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.
3-31
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.
3-32
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. It is recommended not to select the Cross mount
points attribute for policies where you use the ALL_LOCAL_DRIVES directive.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-33
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
list if a specific list is present.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
For detailed instructions on creating an include or exclude list, see the NetBackup
Administrator’s Guide. For detailed instructions on how to remotely manage include and
exclude lists for UNIX clients, refer to the NetBackup Commands Reference guide, and
Article 100019744: A method for centrally managing exclude and include list for UNIX
and Linux clients at: http://www.veritas.com/docs/100019744.
3-34
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.
3-35
3-35
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 Administrator’s Guide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-36
After completing this topic, you will be able to view, edit, and copy existing
policies.
37
3-37
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:
• To open or change a policy, in the All Policies pane, double-click the policy
name. The Change Policy dialog box is displayed.
• To display information about all policies, in the All Policies pane, select
Summary of all Policies. Click the title bar of each horizontal pane to expand or
collapse it.
3-38
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:
4. In the Copy a Policy dialog box, enter the name of the policy that you want to copy.
You can indicate a policy other than the one that is selected, or leave the original
named policy.
5. Enter the name for the new policy, then click OK. The only difference between the
new policy and the copied policy is the name.
Note that using the policy copy operation can be used for copying policies of the same
policy type, but should be customized after the copy operation to prevent having
policies that perform the same operations. Additionally, the policy copy operation
should probably be avoided when copying a policy to a new policy type. It is more
appropriate to simply create a new policy for the new policy type backup.
3-39
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:
3-40
• 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.
3-41
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.
3-42
42
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.
3-43
A. 1,000
B. 500
C. Unlimited
D. None of the above
43
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-44
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.
44
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-45
A. Differential incremental
B. Cumulative incremental
C. Accumulation incremental
D. Differences incremental
45
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-46
A. Differential incremental
B. Cumulative incremental
C. Accumulation incremental
D. Differences incremental
46
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-47
A. True
B. False
47
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-48
A. True
B. False
48
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3-49
End of presentation
3-50
© 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.2:
Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4-1
4-2
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.
4-3
After completing this topic, you will be able to use and customize the
Activity Monitor, and suspend, resume, restart, and prioritize jobs.
This is the Using and customizing the NetBackup Activity Monitor topic.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4-4
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:
Alternatively, note that you can view older jobs in the NetBackup report found under
NetBackup Management > Reports > Status of Backups. The Status of Backups report
does not show job details, and only specific types of jobs, such as backup jobs. For
additional settings and details, refer to the NetBackup Administrator’s Guide.
4-5
You can use the Activity Monitor in the NetBackup Administration Console to monitor
and control NetBackup jobs. To display job information, in the NetBackup
Administration Console, click Activity Monitor. Summary information about all jobs is
displayed under the Jobs tab in the details pane. By default, not all columns are
displayed. The following procedure describes how to show or hide columns:
1. In the Activity Monitor, select View > Column > Layout. The Column Layout dialog
box is displayed.
2. Select the column to display or hide by selecting its heading from the list.
• Click Show to display the column.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4-6
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 box can be
viewed in by accessing the View > Filter menu option, or by clicking on the Show or
Hide Custom Filter button in the top-right corner of the Activity Monitor. Clicking on the
View All button clears currently applied filters and displays all original rows again. To
create a filter:
1. In the Activity Monitor, show the custom filter pane, as shown on the slide.
2. Click Create, and in the Create Filter dialog box provide a name for the filter.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3. Under the Advanced tab, select the Field, Comparison, and Value desired.
4. Click Add to List to add your selections to the filtering criteria.
5. Click Save to create the filter. The filter is immediately applied.
You can edit an existing filter operation with the Edit button. Once the filter is modified,
save the filter by either choosing Save or Save And Apply Filter. There is also
functionality to export and import filters as a binary file, to share frequently used filters
with other hosts and users.
4-7
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
or if enabled a checkpoint hasn't been reached. Jobs cancelled “cleanly” as described
here, exit with NetBackup status code 150 (termination requested by administrator). If
you cancel a scheduled backup job, but the number of retries is not yet exceeded and
the backup window is still open, the backup is reattempted. Also, note that after you
cancel a backup job, the cancellation process can take several minutes. For example, if
the backup is being written to tape, the tape must be rewound and unmounted before
the cancellation process is fully completed.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4-8
Job priorities provide a method to help determine which jobs get available resources.
This can be used to help administrators prioritize certain high priority clients and data
against other clients with a lower priority. Job priorities can be set as a default value for
different job types in the policy, before the job runs, or on jobs that have already been
added to the Activity Monitor in NetBackup. The NetBackup Resource Broker (nbrb)
uses the job priorities to determine which job is assigned available backup resources, in
addition to other factors, such as multiplexing requirements. The NetBackup resource
broker re-evaluates resource requests every five minutes, or when triggered by an
external event, such as a resource release.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
In Master Server Properties > Default Job Priorities, you can set the default job
priorities for different job types. The Default Job Priorities host properties list 18 job
types and the configurable default priority for each. The job priority range is 0–99999.
4-9
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.
4-10
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.
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.
4-11
12
1. In the NetBackup Administration Console, open the Activity Monitor and click the
Jobs tab.
2. Select the suspended or the incomplete job you want to resume. Only backup and
the restore jobs that contain checkpoints can be suspended.
3. Select Actions > Resume Job.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Note that if incomplete jobs are not resolved after 3 hours, by default, their state
changes from Incomplete to Done. This settings can be changed in the master server
host properties under the Clean-up tab. A screenshot of that setting is shown on the
slide.
4-12
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
No checkpoints are taken during the backup of a system state or shadow copy
components on a Windows client.
No checkpoints are taken during a disk-image (raw) backup.
No checkpoints are taken for the remainder of the backup after NetBackup encounters
an NTFS single-instance store (SIS).
Single-instance store is an architecture designed to maintain duplicate files with a
minimum of disk, cache, and backup media overhead. For more information on NTFS
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
4-13
After completing this topic, you will be able to initiate a manual backup job,
and monitor backup jobs using the Activity Monitor.
14
4-14
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
4-15
• Testing a configuration
• Resubmitting a missed or failed backup
• Preserving an old configuration prior to upgrading
16
• Manual backups are performed from the NetBackup server by the backup
administrator and apply only to automatic schedules.
• User-directed backups are performed from the client machine.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A manual backup is not dependent on the policy’s backup window or the time specified
by the schedule. That is why it is also called immediate. In fact, you can create a policy
schedule without an open window and run only manual backups defined by that policy,
as needed.
Since you can invoke a manual backup outside a policy’s normal backup window, a
successful manual backup job can affect a frequency-based schedule because it qualifies
as a successful backup. Consider that frequency-based schedules are based on the
amount of time (frequency) since the last successful backup job. This may therefore
mean that an automatic backup does not run when you next intended it to.
4-16
bpbackup -i
17
1. From the object tree pane of the NetBackup Administration Console, expand
NetBackup Management and select Policies.
2. In the All Policies pane, click the policy name and select Actions > Manual Backup.
Alternatively, right-click the policy and select Manual Backup.
The Manual Backup dialog box is displayed.
3. Select a schedule and the clients you want to back up.
• If you do not select any schedules, NetBackup uses the schedule that runs least
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
often. For Automatic schedules, the Frequency is generally used. If there are
multiple equivalent candidates, then schedule with the highest retention level is
chosen. It is therefore recommended to explicitly specify the schedule that you
wish to use.
• If you do not select any clients, NetBackup backs up all clients.
• If a User schedule exists, they are not displayed in the schedules list and cannot
be manually backed up because they do not have a backup selection list (the user
selects the files). These types of backups are run from the client system, either by
an application or script, or an administrator (user).
4. Click OK to start the backup.
4-17
18
You can expect backup success to be the norm in a properly configured and well-
maintained NetBackup environment. NetBackup is a very robust application in terms of
detecting and reporting errors, therefore, when problems do occur, you should be able
to track them down and correct them quite reliably.
A status code 0 (and the accompanying success icon) in the Activity Monitor indicates
that a backup job has completed successfully. Any other status code or icon indicates
that a backup was only partially successful or has failed. There are other methods by
which you can determine if a problem has occurred with a backup job, including reports
and activity logging.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A status code 1 (and the accompanying partial success icon) in the Activity Monitor
indicates that the job has partially succeeded. For file system backups, this could mean
that some of the targeted files did not get backed up. It could be only one file was
missing, or many files, and there is no indication how important these missing files are.
Look at the job details for information on which files are not included. If those files are
not important (such as temporary or cache files that aren’t needed for recovery),
consider excluding them from future backups, so that you instead complete with status
code 0. Using Windows VSS or other snapshots may fix these issues.
Other reasons may exist for status code 1 backups, and for application and database
backups, a status code 1 may indicate a larger problem, and may result in the inability
to perform restores.
4-18
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:
slide.
4-19
20
Hierarchical jobs, when one job is a parent of one or more child jobs, is a behavior seen
frequently with Storage Lifecycle Policies, snapshot jobs, catalog backup jobs, and many
other job types. The Activity Monitor in the NetBackup Administration Console can
optionally show a hierarchical job view. There is a button on the toolbar which enables
this functionality, or you can select View > Jobs in Hierarchical Manner from the menu
bar to toggle this view.
You can get this information by moving the Parent Job ID column, which by default is
placed to the far right, close to the Job ID column. In this way, you can see the job
associations. However, the hierarchical job view makes this easier to visualize. The job
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
hierarchy can also be seen in the Job Hierarchy tab of the job details.
4-20
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.
4-21
After completing this topic, you will be able to configure and perform user-
directed backups using the Backup, Archive, and Restore console.
22
4-22
23
The policy must have a user backup schedule that defines the start window during
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
which users can initiate a backup. The client must be in the policy’s client list. Users
select files and directories to back up. NetBackup ignores the policy’s backup selections
list. Clients can obtain status information using progress logs, e-mail notifications, and
the activity monitor. User-directed backups and archives can be initiated by:
• An interactive user, such as a file owner, system administrator, or DBA by using the
BAR console, or NetBackup commands.
• A backup script launched at regular intervals.
• An event trigger that kicks off a backup script.
4-23
24
User-directed backups require a backup policy that contains a User Backup schedule,
and the client names added into the Clients tab of that policy. Consider the following:
• When you establish a user backup schedule, you provide users with a start window
during which they can perform their own backups or archives. Users can start
backups and archives only during the times permitted under the schedule’s Start
Window tab. When you set the start window, consider the times that users typically
are at work and likely to need to initiate user-directed backups. If a user starts a
backup outside of this window, the backup job fails.
• User backup schedules can be included in a policy that contains automatic backup
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
schedules. If you create separate policies for user backups, the considerations are
similar to those for automatic backups. Jobs running user backup schedules ignore
the policy’s backup selection list. The files backed up are specified as part of the
request to run the backup job at the time the request is made by the user.
• The policy name you choose is significant. By default, NetBackup alphabetically
searches (uppercase characters first) for the first available policy with a user backup
schedule with an open backup window, and a matching host name under the Clients
tab of the policy. If no user backup schedule is found, the backup fails with a status
code 240: no schedules of the correct type exist in this policy.
4-24
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:
4-25
BAR
console
Activity
Monitor
26
The View Status dialog box enables you to view the progress of a NetBackup operation.
The status is displayed in the top pane. Select the job that you want to monitor. The
lower pane reflects the progress of the item selected in the upper pane. The NetBackup
operation is finished when the status changes to Successful. If NetBackup is unable to
back up all of the requested files, a status code is displayed a few lines before the end of
the progress report. The NetBackup Status Codes Reference Guide lists the meaning of
the final status code. You can also monitor user-directed jobs using the Activity Monitor
in the NetBackup Administration Console. User-directed backups display as
User_backup in the Job Schedule column. You can use this to keep track of how many
user-directed backups are being run in your environment.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4-26
After completing this topic, you will be able to identify common backup job-
related status codes.
27
4-27
• Mis-defined 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.
part to verify that such oversights are corrected. Evaluate and adjust the policy
attributes, as necessary. Extend the backup window to avoid errors resulting from the
backup window being closed.
• Client issues: The slide highlights some common client issues. Some of these are
configuration issues, and a common problem is trying to back up a client, which has
not had the NetBackup client software installed, in which case NetBackup cannot
communicate with any NetBackup processes on that client.
4-28
• Backup selection issues: Another common set of issues has to do with incorrectly
specifying the backup selection list. If incorrect directories are specified, or if
directories or folders have changed on the client, then what gets backed up may not
match the expectations of the organization.
If at least one file is backed up then the backup job should return either a status code
of 0 (successful) or 1 (partially successful). If no files are backed up, a status code 71
(None of the files in the backup selections list exist) is displayed.
4-29
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.
4-30
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.
4-31
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.
4-32
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.
4-33
33
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.
4-34
A. Immediate
B. Automatic scheduled
C. Manual
D. User-directed
34
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4-35
A. Immediate
B. Automatic scheduled
C. Manual
D. User-directed
35
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4-36
A. True
B. False
36
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4-37
A. True
B. False
37
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4-38
38
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4-39
39
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
4-40
End of presentation
4-41
© 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.2:
Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-1
5-2
Topic Objective
Describe the restore process and the restore methods used within
Introduction to restores
NetBackup.
Performing restore operations using Restore files and monitor restore operations using the Backup,
the BAR interface Archive, and Restore (BAR) interface.
Performing restore operations using Restore files and monitor restore operations using OpsCenter
OpsCenter Operational Restore Operational 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.
5-3
After completing this topic, you will be able to describe the restore process
and the restore methods used within NetBackup.
5-4
Synchronous Clustering
Traditional replication
Snapshot Standard
backups Asynchronous technologies restore
Snapshot replication
technologies Bare Metal
Restore
Not all data is of equal importance. You can afford to wait for some data; you can
reconstruct or even abandon some data, if necessary; and you must have some data as
soon as possible. Data protection specialists talk about two important objectives that
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• 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.
5-5
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 (BAR)
interface. The NetBackup master server catalog contains information on what files
and folders have been backed up, and provides the information that the
administrator will then use to select which data to restore.
2. The NetBackup master server uses the information in the NetBackup database to
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
identify where the backup images are stored, and uses information supplied by the
administrator to decide where they should be restored on the NetBackup client.
3. The appropriate image is retrieved from storage by the media server, and the
selected files are extracted onto the client.
4. Because NetBackup maintains status information about restores in its log files, you
can monitor and report on restores just like backups. Information is also pulled from
the master server by the OpsCenter server on a periodic basis, based on the
OpsCenter configuration.
5-6
Client-directed restores
• Only the client that backs up files to restore those files, by default
• Disable all restrictions with the No.Restrictions setting
• Allow specific clients with altnames settings
The default behavior for NetBackup is to allow NetBackup administrators running the
NetBackup Administration Console, which is connected to a master server, to be able to
restore to any client in that environment. To prevent server-directed restore on a
NetBackup client:
• On Windows clients: In the Backup, Archive, and Restore interface, in the toolbar,
select File > NetBackup Client Properties > General, then clear the Allow server-
directed restores check box.
• On UNIX clients: Add DISALLOW_SERVER_FILE_WRITES to the NetBackup
configuration file on the client: /usr/openv/netbackup/bp.conf.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Additionally, the default behavior is that anyone with the ability to run the Backup,
Archive, and Restore interface on a specific client, can only restore that client’s data.
To change client restore permissions, first create the altnames directory on your master
server at install_path\NetBackup\db\altnames (Windows) or
/usr/openv/netbackup/db/altnames (UNIX). Then, within the directory:
• To disable all restrictions to allow any client to restore any clients data, create an
empty file with the name No.Restrictions.
• To allow individual clients to perform redirected restores, create a peername file: A
file named after the NetBackup client which has the ability to restore other clients.
5-7
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, Archive, and Restore interface on the master
server that backs up the source client. To perform a client-directed restore, use the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-8
After completing this topic, you will be able to restore files and monitor
restore operations using the Backup Archive and Restore (BAR) interface.
This is the Performing restore operations using the BAR interface topic.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-9
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, Archive, and Restore
shortcut), and on a UNIX client, use the jbpSA & command. By default, NetBackup
clients are configured to allow NetBackup administrators on a master server to direct
restores to any clients. These are referred to as Server-directed restores. To perform an
administrator-directed restore to a specific client, use the Backup, Archive, and Restore
interface on the master server that backs up the source client.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
For client-directed restores, by default, NetBackup permits files to be restored only from
backups of the client. The client may not restore from backups of other clients.
NetBackup ensures that the client name of the requesting client matches the peer name
that was used to connect to the NetBackup server. The NetBackup administrator can
modify this behaviour, either on a single client or for all clients. See the NetBackup
Administrator's Guide for details.
5-10
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
11
One of the first steps is specifying the NetBackup hosts and policy types by selecting
Actions > Specify NetBackup Machines and Policy Type from the menu, or clicking on
the corresponding button. For normal user-directed restores to the original client,
accept the default settings.
• Server to use for backups and restores: This setting defines the master server used
for restore (not the media server). If you need to add a master server to the drop-
down list, click Edit Server List, and add the master server to that list, and then
select that server.
• Source client for restore: When performing server-directed restores or alternate-
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
client restores, select the client from the drop-down list. Alternatively type the client
name. Be sure to use the correct client name that NetBackup used to backup the
client, otherwise no backup images are found.
• Destination client for restore: Use this field when performing server-directed
restores. For restores to the original client, leave the destination client as is. If you
need to change the destination client, select the corresponding client. Note that the
destination client must have the NetBackup client software installed.
• Policy type for restores: Select a policy type from the drop-down list. If an incorrect
or unused policy type is selected, no valid backups are found for restore.
After you have made all of the necessary selections, click OK.
5-11
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
12
Select the appropriate restore type from the drop-down menu under the Restore Files
tab. Restore type selections include:
• Normal Backups
• Archived Backups
• Raw Partition Backups
• True Image Backups
• Point in Time Rollback
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
For most file and folder restores from Standard or MS-Windows policies, select Normal
Backups.
5-12
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
13
After you specify a restore type, you need to identify the backups you want to view. This
is performed by setting a date range which NetBackup uses to limit the backup images
examined for restores. Instead of specifying a date range, you can choose your backup
from a list. This changes the date range based on the selected images. From these
backups, you eventually select the files for restore. The Backup, Archive, and Restore
interface provides two ways to set this date range:
• Specify a date range: You can specify a range of dates for the backups you want to
view. Click the Use calendar to set date range button, and the Date Range dialog box
is displayed. Select a Start Date and an End Date and click OK.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Backup list: Click the List Backups button to display a list of backups. Select the full
backup, as well as the subsequent differential or cumulative incremental backups.
Effectively, this just sets the start date and end date that NetBackup uses to examine
prior backups.
5-13
Mark files to
5
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
14
After selecting the backup images you wish to restore from, you should see a list of files
and folders you can restore from at the bottom pane. If a timeframe was selected that
includes multiple backup images, then it is possible that multiple versions of a file or
folder can be restored. By default, the Backup, Archive, and Restore console displays the
most recent version of the file, for the backup images that are currently selected by the
date range specified. If you want a list of all files from the selected backups, including
files for which there are multiple versions from different dates, click the Show all
backup in the specified date range button. If you want to return to view only the latest
version of the files, click the Show most recent backup in the specified date range
button.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
5-14
• Restore from full and incremental backups. NetBackup’s default search range is for
the most recent backups since the last full backup. You can modify the search range
if you want to restore an image other than the most recent image.
• Restore from a backup series. Cumulative incremental backups require a full backup
and the most recent cumulative backup in the series. Differential incremental
backups require a full backup and all of the differential backups in the series.
• Restore a specific version of a file or directory. To restore an older version of a folder
or a file, specify a time range within which you know it existed. Select only backups
that include the version of the directory or file to restore.
bplist examples
The following example recursively lists files on train2 that were backed up on or after
February 25, 2010 in D:\myfiles:
bplist –C train2 –l –s 2/25/10 –R D:\myfiles
The following example displays all files that were backed up.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 commands
(http://www.veritas.com/docs/100016074) describes policy types and how they are
used with bplist and other NetBackup commands.
5-15
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-16
5
Mark files to Disk
restore
Preview required
6
media
Set destination /
7
restore options
8 Initiate restore
9 Monitor restore
17
After selecting the files and folders to restore, click the Preview button. The Media
Required dialog box is displayed with a list of the media required to perform the
restore. Use the contents of this dialog box to verify which media are required to
perform the restore. This helps you determine if you require a tape that is currently
offsite or otherwise unavailable. Note that for disk-based media, the Preview button is
not necessary, and returns the message “No media is required for restore. Images are
on Disk.” If the backups are on disk, instead an informational message is provided to
inform you that no media is required for the restore. Click Restore to start the restore
job. The Restore Marked Files dialog box is displayed and you are required to define
some final parameters before the restore operation starts.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-17
Mark files to
5
restore
Preview required
6
media
Set destination /
7 Initiate the
restore options
restore
8 Initiate restore
9 Monitor restore
18
The Destination pane of the Restore Marked Files dialog box grants you varying levels
of control over the placement of the files:
• Restore everything to its original location (Default): Restores items to the file or
path from which they were backed up.
• Restore everything to a different location (maintaining existing structure): Restores
items to a file or path other than the path from which they were backed up.
• Restore individual directories and files to different locations: Restores items to
paths other than the path from which they were backed up.
• Create and restore to a new virtual hard disk file: For Windows 2008 R2 clients and
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Windows 7 clients, you can restore marked items to a new, virtual hard disk (VHD)
file. If you select this option, you must specify a new VHD file. You cannot restore to
an existing VHD file with this option.
When you enter the destination path and the file name for the new VHD file, do not
include the .vhd extension. The extension is added automatically.
After you enter the new destination path and the file name, click Setting. Set the VHD
file size and select the behavior of the file as follows:
• Virtual hard disk size: Select the VHD file size. Ensure that you do not exceed the
maximum available amount of space.
• Dynamically expanding (default): If you select this option, the VHD file expands
up to the specified virtual hard disk size.
5-18
The Options pane shows the remaining options granting control over how NetBackup
handles files that may already exist:
• Overwrite existing files: This option must be enabled if the restore operation is
required to replace any existing versions of files to be restored. By default this is not
enabled.
• Restore all directories without crossing mount points: This option restricts the
restore to the contents of a single file system.
• Restore without access-control attributes (Windows clients only): An access
control list (ACL) is a table that conveys the access rights that users have to a file or
directory. Each file or directory can have a security attribute that extends or restricts
users’ access. The option to restore file and directory data without restoring ACLs is
available if the destination client and the source of the backup are both Windows
systems. To restore files without restoring ACLs, the following conditions must be
met:
• The policy that backed up the client must have been of policy type MS-Windows.
• The restore must be performed by an administrator logged in to a NetBackup
server (Windows or UNIX). The option is set from the client interface running on
the server. The option is unavailable on stand-alone clients (clients that do not
contain the NetBackup server software).
• The destination client and the source of the backup must both be systems
running supported Windows OS levels. The option is disabled on UNIX clients.
To restore files without restoring ACLs, mark the Restore without access-control
attributes (Windows clients only) check box.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Rename hard links and Rename soft links: These options request NetBackup to
rename the appropriate links when restoring to an alternate location. For example, if
restoring to an alternative boot disk, it is necessary to rename hard links for the
system to boot from the restored disk, but soft links should not be renamed.
• Use default progress log filename: To write the progress messages to a log file other
than the default, clear the Use default progress log filename check box, and then
enter the name of the alternative progress log.
• Override default priority: Select this option to change the priority for the current
restore operation. The available range is 0 - 99999. The higher the number, the
greater the job priority.
After you have selected all of the necessary options, click Start Restore.
5-19
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.
5-20
After completing this topic, you will be able to restore files and monitor
restore operations using OpsCenter Operational Restore.
21
This is the Performing restore operations using OpsCenter Operational Restore topic.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-21
Includes options similar to the Backup, Archive, and Restore (BAR) console, but with additional search
capabilities
Enables previews of required media, including the ability to export this data in multiple formats
22
Operational Restore provides a simplified search and retrieval mechanism that works
across multiple NetBackup domains, and was introduced in NetBackup OpsCenter 7.5.
Although it requires an OpsCenter server, it comes at no cost and does not require any
license. This feature enables restores to be initiated using the OpsCenter Web console
and removes the need to install the BAR console on customer workstations. The search
capabilities facilitate searches without requiring specialized knowledge of the backup
environment.
Operational Restore includes enhanced filtering selection, the ability to use wildcards
for search, and manual browsing of directory and sub-directory structures of backed-up
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
5-22
23
5-23
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:
5-24
25
Under the Select Files or Directories tab, the Search tab is displayed.
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
5-25
5-25
Veritas recommends using the fully qualified domain name (FQDN) for clients, to avoid
confusion and name conflicts. The image catalog contains a directory for each client
name as specified in the policy, so the name of the client that was backed up must be
the name of the client for the source client. After you select the clients, a table is
displayed that provides the client names and the master servers associated with the
clients. If you want to remove a specific client, click Remove.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-26
27
To perform an advanced search, you can specify advanced search criteria in addition to
the simple search criteria. The Advanced Search criteria are optional. For more
information about the advanced search criteria, see the NetBackup OpsCenter
Administrator’s Guide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-27
28
4. After you have made all of your search selections, click Search. It may take some
time for OpsCenter to display the search results. The time to display the search
results may increase with the number of selected clients. OpsCenter highlights the
search results at the bottom of the pane in a table.
This slide presents the procedure to browse the protected files and directories on a
client. This method enables you to select the client to be browsed and specify a time
frame for backup selection. You can select only one client at a time. The most recent
backup in the specified date range is shown by default. Under the Search tab, you can
see that the search has completed successfully. Search results are displayed while the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
5-28
You can also use the nbfindfile command to search files or directories based on
simple search criteria. This command can be executed from the NetBackup master
server, not the OpsCenter Server. For more information about the nbfindfile
command, see the NetBackup OpsCenter Administrator’s Guide or the NetBackup
Commands Reference Guide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-28
29
5. To select one or more files or directories to restore, mark the check box next to the
file or directory.
• To restore the files or directories now, click Restore now.
• If you want to add the selected files and directories to the Restore Cart and
restore them at a later time, click Add to Restore Cart.
To display the backup history, click the Backup History Selection link for the file or
directory that interests you. The Backup Timeline window is a timeline view of backups
for a specific file or directory. At the top of the Backup Timeline window, the name and
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
location of the selected backup’s file or directory are displayed. The timeline displays
icons that each represent a different backup or snapshot. By default, the primary
backup copy of the most recent backup for this file or folder is selected, however this
window enables an alternate backup copy to be chosen by clicking on that icon.
The Backup table in the middle of the window displays information about the backup
that is selected from the timeline view. It displays information, such as backup time,
policy name, policy type, backup type, and so on. Click an icon to view the details of the
specific backup in the Backup table. After you select the specific backup image that you
want to restore from the Backup table, the copies that are associated with the backup
image are displayed in another table at the bottom of the window. The Copies of
Selected Backup table displays information about the copies that are associated with
the selected backup image. By default, the primary copy is selected.
5-29
30
The Restore Cart enables you to view file selections from multiple search and browse
operations and restore them at a later time. You may also choose to restore all the file
or directory selections at once. The Restore Cart selection persists for each user across
different OpsCenter sessions. After a file belonging to the Restore Cart is sent for
restore, it is automatically removed from the Restore Cart for the specific user.
You can perform several operations on the files and directories in the Restore Cart. You
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
can email or export the contents of the Restore Cart. You can also restore or remove
files from the Restore Cart. For more information about performing operations on the
Restore Cart, see the NetBackup OpsCenter Administrator's Guide.
When you click Restore now, the Restore Options panel is displayed. You can specify
restore options for the files and directories that you selected, such as destination client
and paths, and overwrite and access control options. This panel enables you to specify
the restore options for each source client from which a file or directory has been
selected to be restored.
5-30
31
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.
5-31
The Summary panel displays the list of files and directories that have been selected for
restore. It also displays information about the current location of these files and
directories and where they are to be restored. The Summary panel shows a table that
includes the source file name, the source file path, the source client, the destination file
path, and the destination client. At this point, you have one last opportunity to remove
files or directories from the Summary panel. To remove files or directories that you do
not want to restore, click the Remove files or directories button.
8. In the Summary panel, click Restore to restore all the files or directories.
The corresponding restore jobs are triggered, and the File or Directory Restore
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Launch Status dialog box is displayed. This dialog box identifies the job ID of the
restore job, the name of the master server that is associated with the client on
which the file resides, and the name of the source client.
Click OK to navigate to the OpsCenter Monitor > Jobs tab and view the job progress
details.
The Monitor > Jobs view provides details about NetBackup jobs. In this example,
detailed information about Job ID 264, the restore job, is displayed. Notice that the job
is selected in the content pane, and additional information is displayed in the details
pane.
5-32
After completing this topic, you will be able to monitor restore operations,
and identify common restore-related issues.
33
5-33
34
You can also monitor the progress of the restore operation from the NetBackup
Administration Console Activity Monitor.
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.
• The restore restarts at the beginning of the last checkpointed file only, not within
the file.
• Only the backups that are created using Standard or MS-Windows policy types are
supported.
• Third Party Copy and Media Server Copy images that use Standard policy types are
supported, but cannot be suspended or resumed if the backup image has changed
blocks.
5-34
• Even though a restore job is cancelled and is reported as such, all files written up to that
point are considered “restored.”
NetBackup does not replace the files restored to that point with the files that existed
before the restore operation started.
• The last file written at the time of the cancellation may be corrupted.
To restore a file, a user must have read access to the backed-up file and write access to the
desired destination where the file is to be placed when it is restored.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-35
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.
36
5-36
• UNIX
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
/usr/openv/netbackup/logs/bplist/
/usr/openv/netbackup/logs/bprestore/
• Windows
install_path\NetBackup\logs\bplist
install_path\NetBackup\logs\bprestore
Create these directories with public-write access. The commands create debug logs
within the respective directories, which you can use for detailed troubleshooting. If a
non-root user is specified under USEMAIL = mail_address in the $HOME/bp.conf file
of a NetBackup UNIX client, NetBackup sends an e-mail containing the restore
completion status to mail_address. This message is sent when the restore process
completes.
5-37
38
When attempting a restore, you may receive an error stating No Files Found. This is a
common occurrence when some of the restore fields are not set correctly for the data
in question. Some parameters to check include:
• Source client: Make sure to use the correct host name for the source client. If the
image was registered under the short name, console, then use the short name. If
the backup was done using the FQDN, console.example.com, use the FQDN.
• NetBackup server: Ensure that the correct master server name is used.
• Date range: Enter the date range for valid backups. If the date range you are using
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
doesn’t yield any results, verify that backups completed for that client, during that
time.
• Browser directory: The directory needs to be set so that it is valid for the backup
data. If the default directory shown is for data that was not included in the backup,
then no files will be found. Change the folder to one that is relevant to your backup.
This primarily applies to UNIX and Linux-based images.
• Restore type: If a restore type is chosen that doesn't match your backup, then no
data will be shown. For many backup types, the Normal Backups restore type
should be chosen.
• Keyword: Ensure this entry is clear, if keywords are not being used. Otherwise the
backup images shown will be limited to those using the keywords selected.
5-38
39
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.
5-39
• Key points
– You learned how to initiate and monitor restore operations using the Backup, Archive, and Restore
interface and Operational Restore.
– You also learned 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
40
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.
5-40
41
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.
5-41
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.
5-42
A. True
B. False
42
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-43
A. True
B. False
43
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-44
44
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-45
45
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-46
46
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-47
47
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
5-48
End of presentation
5-49
© 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.2: Administration
course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
6-1
6-2
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.
6-3
After completing this topic, you will be able to describe disk-based storage,
including disk pools and AdvancedDisk storage.
6-4
PureDisk Usesspanning
a Media Server Deduplication Pool (MSDP).
disk volumes
• Scalable: Easily expand
• Lesson: Configuring Media Server Deduplication capacity; Handles unlimited
• Document: NetBackup Deduplication Guide
theoretical
• License: NetBackup Data Protection Optimization Optioncapacity
The slide reviews disk storage types in NetBackup (listed by the corresponding disk type
identification categories used in NetBackup), including BasicDisk, AdvancedDisk,
OpenStorage and PureDisk. This lesson discusses the AdvancedDisk storage type,
specifically using simple disk pools of multiple disk volumes, on a single media server.
Creating disk pools in NetBackup offers several benefits over basic disk storage units.
Resources are used more efficiently by logically combining disk resources on a single
server or across multiple servers. Using disk pools unlocks a number of additional
features, including capacity management, data classifications, storage lifecycle policies,
and media server load balancing. Disk volumes can be added to a disk pool to increase
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
capacity, and there is no inherent limitation for capacity size of the disk pool.
6-5
Disk
enclosure Storage server
(logical)
OpenStorage
Technology (OST)
Disk
volume Disk pool Media
server
(physical)
• A disk enclosure is a physical container with disk storage, such as a disk array.
• A disk volume is a logical unit of disk storage, as presented by the host operating
system, such as a partition or Volume Manager volume.
• A disk pool is a collection of disk volumes administered in NetBackup as a single
entity. Storage units are configured to target a single disk pool for backup.
• A media server is a NetBackup system that manages the writing of backup data to
storage media. Traditionally, the storage media may be either disk or tape media.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
6-6
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.
6-7
OpenStorage is a Veritas API that enables NetBackup to communicate with the storage
implementations that conform to the API. Disk appliance vendors participate in the
Veritas OpenStorage Partner Program. Veritas qualifies their storage solutions for the
OpenStorage API. The vendor's storage controls the storage format, the location where
the images reside on the storage, and the data transfer method. As a result,
performance and storage utilization are highly optimized.
Third-party OpenStorage servers include disk appliance vendors that provide a software
plug-in that is installed on the NetBackup media server. NetBackup media servers use
the plug-in to communicate with the disk appliance. From the NetBackup master server,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
a disk pool is created that points to the disk vendor’s appliance, which is now known as
a storage server. NetBackup determines when backup images are created, copied, or
deleted. Images are moved, expired, or deleted on the storage when NetBackup
instructs the appliance to do so through the API.
6-8
In the event that third-party OpenStorage vendors are being used in a NetBackup
environment, the OpenStorage vendor’s disk array is considered the disk enclosure and
the disk pool. The disk array is also the storage server, since it is responsible for the I/O
to and from disk. To be able to communicate correctly with the OpenStorage vendor’s
disk array, the NetBackup media server need to ensure that a NetBackup plug-in, which
is provided by the third-party vendor, is installed. This is an environment where the
media server and storage server are not contained in the same server.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
6-9
10
OST Cloud Storage plug-ins enable Veritas NetBackup to access Cloud Storage Solutions.
Either the storage vendor or Veritas provides a software plug-in, which is installed on
each NetBackup Media Server that is connected to the cloud solution. Supported
vendors may include ACP, Amazon, AT&T, China Mobile, China Telecom, Chunghwa
Telecom, Cloudian, Datish Systems (OpenDedup), Deutsche Telekom, EMC, Fujitsu,
Google, HGST, Hitachi, Huawei, IBM, Microsoft, NetApp, Oracle, Quantum, Rackspace,
Red Hat, Scality, StorReduce, SUSE, SwiftStack, Telefonica, and Veritas.
OST Cloud support information, including a detailed list of supported vendors, solutions,
and functionality, is listed in the Hardware and Cloud Storage Compatibility List (HCL) at:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
http://www.netbackup.com/compatibility.
6-10
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.
6-11
After completing this topic, you will be able to configure storage servers,
AdvancedDisk disk pools, and AdvancedDisk storage units.
12
6-12
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.
An AdvancedDisk storage unit must be configured to target a single disk pool, and it
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
cannot specify individual disk volumes in a pool. However, more than one storage unit
can be configured for a single disk pool. This may be performed to allow higher priority
policies to have additional concurrent write streams. NetBackup assumes exclusive
control of all disk volumes configured within a disk pool, enabling NetBackup to manage
and report disk capacity accurately. A disk volume cannot exist in more than one disk
pool.
If NetBackup is unable to write an image to a single disk volume in a disk pool, the
backup spans to the next available disk volume. Spanning can occur from any volume to
any other volume in that disk pool. It is not possible for a single backup image to span
multiple disk pools, even if the disk pools exist in a storage unit group.
6-13
14
The slide provides an overview of the steps involved to configure a usable disk pool and
corresponding AdvancedDisk storage server.
1. First, determine whether or not the target media server is already configured as an
AdvancedDisk storage server. This process only needs to be performed once per
media server, regardless of the number of AdvancedDisk storage pools hosted on
the media server.
2. Run the Configure a Disk Storage Server wizard if the host needs to be configured as
a storage server, or in other words, if this is the first time the host is being
configured for AdvancedDisk storage.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3. If this host is already a storage server, run the Configure Disk Pool wizard to create a
new disk pool. Note that the storage server wizard will automatically start the disk
pool wizard for you after you configure a new AdvancedDisk storage server.
4. Finally, configure one or more storage units for the disk pool. Both the storage
server and disk pool wizards will allow you to create the storage unit as part of those
wizards, but this can also be performed manually in the NetBackup Administration
Console or using NetBackup commands.
You will learn how to perform each of these steps, in more detail, in subsequent topics.
6-14
nbdevconfig –creatests
15
Before you can create an AdvancedDisk pool, you must configure an AdvancedDisk
storage server. To do this, use the Storage Server Configuration Wizard. You can also
use the nbdevconfig -creatests command to create a storage server from the
command line. The nbdevconfig command and syntax is discussed in the NetBackup
Commands Reference Guide. The nbdevconfig command is found in the following
directory:
• UNIX: /usr/openv/netbackup/bin/admincmd
• Windows: install_path\bin\admincmd
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 requires you to
select the disk type. Select AdvancedDisk and click Next.
6-15
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.
6-16
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.
6-17
nbdevconfig –createdp
18
The Disk Pool Configuration Wizard is automatically started, by default, when you click
Next at the end of the Storage Server Configuration Wizard.
To create a disk pool outside of the wizard, from the NetBackup Administration Console,
expand Media and Device Management > Devices. Right-click Disk Pools and select
New Disk Pool. The Disk Pool Configuration Wizard is displayed. You may also access
the Disk Pool Configuration Wizard by clicking the master server in the Administration
Console. You may also use the nbdevconfig command to configure a new disk pool
from the command line.
No disk pools exist by default. Select the disk volumes to be included in the disk pool. A
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
disk volume must be formatted and mounted within the operating system before it can
be selected for an AdvancedDisk storage unit. Do not select disk volumes that have
already been configured in another pool. Note that the entire disk volume will be used
by the AdvancedDisk pool, and that no directory or folder can be specified in the
configuration.
6-18
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
stops purging backup images as a result of the disk pool reaching the high water
mark
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Maximum I/O Streams: Limits the number of streams that can be directed to a disk
simultaneously. It is used to avoid disk thrashing, which is the result of too many
jobs writing to the same disk simultaneously. The default is that there is no limit, at
the disk pool, however there are limits that are enforced at the storage unit. A
storage unit supports up to 4096 streams, with a default of 1 concurrent job
running. However, because you can setup multiple storage units for one disk pool,
this value allows you to control the maximum I/O streams to the disk pool,
regardless of any storage unit limits.
For more information on these properties, click on the Help button in the Wizard.
6-19
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.
6-20
bpstuadd
21
Next, configure the properties of the storage unit for this disk pool. A Media Server
option is available to limit the storage unit to specific media servers.
In most cases, you must increase the Maximum concurrent jobs setting from the
default setting of 1. For example, on the slide we have changed the maximum
concurrent jobs to 3, to correspond to the number of jobs that the three separate disk
volumes (G:\, H:\, and I:\) in this pool should be able to concurrently run without issue.
The Maximum fragment size setting normally does not need to be changed. Changing
this value may impact backup and restore times, and should be tested if any changes
are made. If you chose to configure the storage unit, no additional configuration is
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
required. The storage unit created for the disk pool may now be selected as a
destination within a backup policy. The disk pool configuration is complete.
6-21
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.
6-22
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.
6-23
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.
6-24
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
6-25
bpminlicense
Article 100024025: NetBackup Traditional and
nbdeployutil Capacity License Deployment Utility (nbdeployutil)
26
Many licensed options in NetBackup are capacity-based; this means that these options
license a specific amount of data storage of a particular type. The Flexible Disk Option,
which tracks space usage for AdvancedDisk pools, is capacity-based.
Access the NetBackup License Keys dialog box, select Help > License Keys, and
determine if you have the Flexible Disk Option. Capacity-based licensing applies only to
the used capacity (active backup images), rather than the total capacity of the storage
units or disk pools. To report on the actual disk space usage and NetBackup capacity
compliance, you will need to run the nbdeployutil command.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
For assistance, refer to Article 100004107: Late Breaking News for the Capacity
Licensing Utility (nbdeployutil) at: http://www.veritas.com/docs/100004107 and
Article 100024025: NetBackup Traditional and Capacity License Deployment Utility
(nbdeployutil) at: http://www.veritas.com/docs/100024025.
6-26
27
For backups targeting a disk pool, NetBackup estimates the size of a backup before
selecting a backup destination. The estimate is based on the size of the most recent
similar backup using the policy, schedule, client, and stream (the file list for a specific
job) as criteria. NetBackup adds 20 percent to this size, and it seeks an appropriate
storage destination.
The disk volume in the disk pool with the most free space is used. If the disk does not
have enough space to store the entire image, the job still runs, and the backup image
will span across multiple disk volumes in that disk pool. After a disk volume is selected,
the estimated backup size is reserved on the selected volume within NetBackup. If new
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
backup jobs are initiated while all disk space is reserved, the new backup jobs queue
until the reserving jobs complete.
A disk pool is configured with high and low water mark values, affecting both the pool
as a whole and its individual disk volumes. At the disk volume level, when the used
capacity percentage exceeds the high water mark value, jobs are no longer assigned to
that disk volume. NetBackup considers a pool to be full when all of its disk volumes
have reached the high water mark value. When a disk volume contains staged backup
images (from a Storage Lifecycle Policy), the images are considered potential free space
if they have already been duplicated. This is discussed in further detail in the Duplicating
Backups lesson. Images that are staged, but not yet duplicated, are considered used
space.
6-27
28
NetBackup tracks status information for all disk volumes in a disk pool, and a status for
the disk pool itself. When everything is working properly, the disk volumes will be in an
UP state, and the disk pool will also be in an UP state. If there is a problem with one disk
volume, it will be put into a DOWN state. This can also be performed manually by the
administrator in the case of disk volume maintenance. The disk pool can still be in a
usable UP state as long as there are other, available disk volumes. Backups jobs should
run normally, as long as there is available space, however restore jobs that use those
specific DOWN volumes will fail.
If the entire disk pool becomes unavailable it will be in the DOWN state. This can also be
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
performed manually by the administrator in the case of disk pool maintenance. In this
case the state of the disk volume is irrelevant, and any backup or restore jobs using this
disk pool will return with a status 2073: Disk pool is down. Note that if the disk pool is
brought down manually by an administrator (for maintenance for example), the disk
volumes will normally still appear in the UP state, despite the fact that they cannot be
accessed for backups.
6-28
29
The state of both disk pools and disk volumes can be set UP or DOWN, which is similar
to the state of a tape device. To change the state of a disk pool using the Administration
Console, right-click the disk pool in the Device Monitor, and select Up Disk Pool or
Down Disk Pool. You can also use the nbdevconfig command to change the state of disk
pools or disk volumes as follows:
nbdevconfig -changestate
-dp pool_name
-stype storage_type
-state UP|DOWN|RESET
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
nbdevconfig –changestate
-dp pool_name
–dv disk_volume_name
-stype storage_type
–state [UP|DOWN|RESET]
6-29
30
There are a number of disk-based reports in the NetBackup Administration Console. For
example, as shown on the slide, you can use the Disk Pool Status report to view the
status of your disk pools. To access this report, in the Administration Console, select
NetBackup Management > Reports > Disk Reports > Disk Pool Status. Some of the
reports, including the commands that correspond to them, include:
• Images on Disk: Shows which backup images reside on NetBackup disk storage. This
is equivalent to running bpimmedia –stype AdvancedDisk.
• Disk Logs: Shows log messages related to NetBackup disk activity. This is equivalent
to running bperror –DiskPool.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Disk Storage Unit Status: Shows storage unit information. This is equivalent to
running bpstulist.
• Disk Pool Status: Shows disk pool status, such as whether the disk pool is in an UP or
DOWN state. This is equivalent to running nbdevquery –listdp for disk pool
status and nbdevquery –listdv for disk volume status (which cannot be seen
in the NetBackup Administration Console).
6-30
✓
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:
For example, of five available media servers in a storage unit group, three have a server
rank of Idle. Of those three, two are running a single job each. Of those two, the server
with the least amount of reserved space is chosen. Alternatively, if only one server had
the best rank, that server is automatically chosen.
6-31
32
When configuring a storage unit group, the Storage unit selection area defines how the
storage units will be selected during a backup:
• Prioritized: Choose the first storage unit in the list that is not busy, down, or out of
media.
• Failover: Choose the first storage unit in the list that is not down or out of media.
• Round Robin: Choose the least recently selected storage unit in the list.
• Media Server Load Balancing: Choose the best available media server based on a
ranking system.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The first three of these methods were discussed in more detail in the Configuring
NetBackup Storage lesson.
Note: Media Server Load Balancing selection supports most storage types including
AdvancedDisk, tape storage, and deduplication storage, but does not support basic disk
storage.
6-32
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 displays some other disk pool management tasks that you may need to
perform, such as adding volumes to a disk pool, removing volumes, or removing the
entire disk pool. To add a volume to an existing disk pool, simply source an empty disk
volumes (ensuring it isn’t used by any other process or application), and use the
command shown on the slide to add it to the disk pool. Prior to NetBackup 7.5, an
option to add disk volumes did not exist. Instead, a procedure to create and merge disk
pools was required. Refer to the documentation for your version of NetBackup for
details.
Alternatively, you can increase the storage space in a disk pool by resizing the existing
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
6-33
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.
6-34
• Key points
– You learned what disk-based storage is and how it is used.
– You also learned about disk pools, AdvancedDisk, and OpenStorage.
– You learned how to configure and manage storage servers, AdvancedDisk disk pools, and AdvancedDisk
storage units.
– Finally, you learned 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.
6-35
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.
6-36
36
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.
6-37
37
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
6-38
38
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
6-39
A. Disk enclosure
B. Logical grouping of media servers
C. Collection of disk volumes presented as a single entity
D. None of the above
39
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
6-40
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.
6-41
41
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
6-42
42
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
6-43
End of presentation
6-44
© 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.2: Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-1
7-2
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.
7-3
After completing this topic, you will be able to describe what NetBackup
deduplication is and how it works.
7-4
Backups are an ideal candidate for deduplication due to the redundant nature of backup
data. For example, in many environments, most of the data backed up during a full
backup, which normally goes to tape or disk, is identical to that of the previous backups.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
In addition to the storage savings that come with only storing unique data, which are
significant, time and other resources are saved. Although many vendors and solutions
provide the ability to deduplicate at the target, usually at the backup storage location or
appliance, being able to deduplicate at the source (the clients) provides the ability to
significantly reduce bandwidth use, and also speeds up the entire backup process. This
is especially true when backing up clients over a WAN or slow connection.
7-5
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 segments. Starting NetBackup 8.1.1,
variable-length deduplication is used. This enables to get higher deduplication ratios.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
In the example on this slide, File2 has two unique segments: E and F. File2 also has
some segments that were previously backed up.
7-6
Client-side deduplication
• Combined with MSDP, distributes deduplication work to the client.
• Reduces network bandwidth and enables higher parallelization.
configure media servers that can also perform deduplication. NetBackup appliances
use dedicated hardware and software to optimize performance, and therefore also
support higher capacities of deduplication pools, in excess of 600 TB, depending on
the model used. The deduplication used in NetBackup appliances is also MSDP, the
same technology as discussed in this lesson.
• NetBackup client-side deduplication: Deduplicating at the source, often known as
client-side deduplication or client deduplication, is supported with NetBackup. This
feature is discussed elsewhere in this lesson.
• Third-party appliances supporting OpenStorage Technology (OST): Third-party
deduplication appliance vendors that support OpenStorage Technology (OST) can
also be managed as a NetBackup storage destination.
7-7
Load Client-side
balancing deduplication
media
MSDP server
NetBackup
storage
clients
server
MSDP
storage
• Media sever deduplication: The client sends the backup data stream over the
network to the media server (requiring bandwidth use), while the deduplication
storage server performs the fingerprinting. The storage server then only stores
unique data in the MSDP storage.
• Using load balancing: To distribute the load required of the MSDP storage server,
configure and use MSDP load balancing servers. These NetBackup media servers do
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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: The client performs the fingerprinting and communicates
with the deduplication storage server as to whether the data is unique or has been
stored previously. If the data is unique, the data is sent over the network to the
media server for storage. Minimal network bandwidth is required.
7-8
Deduplication Deduplication
engine (spoold) manager (spad)
components. It stores and manages deduplicated file data. The binary file name is
spoold, which is an abbreviation for storage pool daemon (do not confuse it with a
print spooler daemon). The spoold process is displayed as the NetBackup
Deduplication Engine in the NetBackup Administration Console.
• Deduplication manager: The Deduplication manager is one of the storage server
core components. The deduplication manager maintains the configuration and
controls internal processes, optimized duplication, security, and event escalation.
The deduplication manager binary file name is spad, which is an abbreviation for
storage pool authority daemon. The spad process is displayed as the NetBackup
Deduplication Manager in the NetBackup Administration Console.
7-9
For performance optimization, Veritas recommends that you use a separate disk,
volume, partition, or spindle for the deduplication database.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-10
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.
7-11
Client-side
deduplication
3
Clients
1 Deduplication 2 Remote
Media Server
Deduplication
Pool
Load Balancing
Server
12
7-12
13
• Load balancing media servers: By using load balancing media servers you can also
increase the overall bandwidth. This option is preferred for storage servers that are
reaching CPU capacity, and in environments where you do not want to use, or cannot
use, the NetBackup client-side deduplication feature. This prevents impacting CPU on
some heavily loaded application servers, while still distributing deduplication load.
• NetBackup OpenStorage Option: If you already have deduplication appliances
deployed in your environment, this option allows NetBackup to use and manage
them within the NetBackup infrastructure.
7-13
After completing this topic, you will be able to configure a media server for
deduplication, including creating a media server deduplication disk pool.
7-14
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.
7-15
16
To create a deduplication media server, you need to consider server and storage
prerequisites. Because fingerprinting is process-intensive, the most important factor in
deduplication performance is CPU, followed by memory size and speed, and storage
speeds. The storage server CPU and memory constrain how many jobs can run
concurrently. The storage server requires enough capability for deduplication and for
storage management. Reducing CPU use on the storage server is possible with load
balancing servers and client deduplication.
Processors for deduplication should have a high clock rate and high floating point
performance. Furthermore, high throughput per core is desirable. Each backup stream
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
uses a separate core. Intel and AMD have similar performance and perform well on
single core throughput. For greater details see the Planning your MSDP deployment
section of the NetBackup Deduplication Guide.
Note: Veritas recommends that you do not use the master server as a deduplication
storage server. Master server activity and media server deduplication activity on the
same host degrades performance. In some environments, a single host can function as
both a NetBackup master server and as a deduplication server. Such environments
typically run fewer than 100 total backup jobs a day.
7-16
17
7-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 64 TB. See the NetBackup
Deduplication Guide for details. Because it is difficult to reconfigure the media server
deduplication pool after it has been created, and after backups have been written to it,
it is extremely important to initially set configuration settings correctly. The wizard steps
you through the following three separate phases:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A storage server is a NetBackup media server that mounts, reads and writes data from
disk storage. Configuration of a deduplication storage server follows the same paradigm
as configuration of all other disk storage server types. The step where the storage server
is created is where you decide and configure the physical location of the storage to be
used. You may use only a single path to the disk storage and the disk storage must be
used exclusively by NetBackup.
7-18
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 enables you to
select the disk type. Select Media Server Deduplication Pool and click Next.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-19
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 resetting the password, refer
to Technical Article 100038891: How to reset the NetBackup authentication password
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-20
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: Select 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
to connect to the deduplication media server using only the named interface.
Note: On Windows, you must specify a folder within the drive letter, as the wizard will
not let you continue if you only specify a drive letter.
Caution: Do not create the directories on the server prior to specifying them in the
wizard, but instead allow the Storage Server Configuration Wizard to create those
directories to ensure correct permissions are assigned.
Note: Use care when making these selections, as they cannot later by changed. Changes
to the storage server require deleting and recreating the storage server.
7-21
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 take you to the screen that displays a summary of the settings that
have been made. Confirm these settings before continuing.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-22
23
NetBackup provides encryption for the deduplicated data. It is separate from and
different than NetBackup policy-based encryption. By default, MSDP encryption is
disabled. On the Storage Server Encryption panel, you can enable encryption and KMS
for Media Server Deduplication Pool. The Enable KMS option is available when you
select Enable Encryption. If you select Enable KMS for the first time, as a one-time KMS
configuration, you must enter the KMS server name, Host master key (HMK)
passphrase, Host master key id, Key protection key (KPK) passphrase, Key protection key
id, Key name, and a Key passphrase. If you select Enable KMS and if KMS is already
configured on the Master Server, you must enter the Key name and the Key passphrase.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
For backups, the deduplication plug-in encrypts the data after it is deduplicated. The
data remains encrypted during transfer from the plug-in to the NetBackup Deduplication
Engine on the storage server. The Deduplication Engine writes the encrypted data to the
storage. For restore jobs, the process functions in the reverse direction.
Note: Do not enable backup encryption by selecting the Encryption option on the
Attributes tab of the Policy dialog box. If you do, NetBackup encrypts the data before it
reaches the plug-in that deduplicates it. Consequently, deduplication rates are very low.
Also, NetBackup does not use the Deduplication Multi-Threaded Agent if policy-based
encryption is configured.
7-23
nbdevconfig –creatests
24
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.
7-24
nbdevconfig –createdp
25
The next step in creating the media server deduplication pool is to create a disk pool. If
you run the Disk Pool Configuration Wizard separately from the Storage Server
Configuration Wizard, you need to select a disk pool type to create of PureDisk. You
may also use the nbdevconfig command to configure a new disk pool from the
command line, however Veritas does not recommend using the command line, and
instead recommends only using the wizard to ensure accuracy during configuration.
On this screen, select the PureDisk disk volume to be included in the disk pool. There
should be only one disk volume per server, as was configured in the storage server
wizard when previously prompted for the storage path.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-25
nbdevconfig –createdp
26
In the Additional Disk Pool Information screen, configure the properties of the disk
pool. Assign a name to the pool and optionally add comments about its function.
Configure additional disk pool information as follows:
• High water mark: The percentage of used capacity at which NetBackup considers a
disk volume in the pool to be full. A disk volume pool within a storage unit group is
assigned fewer backup jobs as it approaches the high water mark.
• Low water mark: For most disk types this is the percentage of used capacity at
which a clean-up operation stops purging backup images as a result of the disk pool
reaching the high water mark. This value is not used for deduplication pools.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• 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”. You can test higher values as you test the hardware’s capacity.
7-26
27
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.
7-27
bpstuadd
28
Finally, configure the properties of the storage unit for this disk pool. In most cases, you
will want to increase the Maximum concurrent jobs setting from the default setting of
1. Veritas recommends that you increase the Maximum concurrent jobs value gradually.
Doing so provides information about the total deduplication load. The initial backup
jobs (also known as initial seeding) require more CPU and memory than successive jobs.
After initial seeding, the storage server can process more jobs concurrently. You can
then gradually increase the jobs value over time.
Every environment's effective maximum concurrent jobs value is different. To find the
best performance raise or lower this value until best performance is achieved.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A Media Server option is available to limit the storage unit to specific media servers.
After the storage unit configuration is complete, no additional configuration is required.
The storage unit created for the deduplication disk pool may now be selected as a
destination within a backup policy.
7-28
29
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.
7-29
nbdevquery -liststs
30
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.
7-30
nbdevquery -listdp
31
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.
7-31
bpstulist
32
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.
7-32
7-33
34
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.
7-34
NetBackup version
Operating system
35
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 at: http://www.netbackup.com/compatibility. Additionally,
see the SORT Web site at: http://sort.veritas.com/netbackup.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-35
36
To establish a client for client-side deduplication, set up the client in the Client
Attributes on the master server. Begin by adding the client to the list of clients that are
displayed in the dialog box. Next, under the General tab, configure the Deduplication
Location that is to be used:
• Always use the media server: This mode turns client-side deduplication off.
Deduplication operations are performed by the media server. This is the default
behavior.
• Prefer to use client-side deduplication: In this mode, the media server determines if
the NetBackup client supports client-side deduplication. If client-side deduplication
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-36
37
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.
7-37
After completing this topic, you will be able to monitor the results of
deduplication in NetBackup.
7-38
39
The Deduplication Rate column under the Jobs tab in the Activity Monitor displays the
rate at which deduplication occurs for backups. This Deduplication Rate column is
displayed to the far right, by default, but can moved by rearranging the columns in the
Activity Monitor. This column displays the storage savings that are realized by using
deduplication.
In this example, a backup policy was used that has a storage destination which is a
deduplication pool (master_msdp_stu). Job 43 was the first backup job for
winmaster.example.com using this deduplication destination. The deduplication rate is
59.4%. Although you may expect a very low deduplication rate, often times even the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
initial data may have many duplicate blocks. In this case we backed up a very large file
that contained repeating data, and therefore the deduplication rate was high for an
initial backup. Job 46 is a second occurrence of the backup performed in Job 43. This
time, the deduplication rate is 99.8% because the same data was written as was written
in the previous job and only a small amount of unique data was found. Job 47 is the first
time that winmedia.example.com was backed up to the deduplication storage. Even
though this is the first backup for this client, because it has almost identical data to
winmaster.example.com, the deduplication rate is very high, at 99.8%.
The results of deduplication are also displayed under the Detailed Status tab of the Job
Details dialog box for a deduplicated backup. The Detailed Status tab includes a line of
text that reflects the details of the backup to the deduplication storage server.
7-39
7-40
Notice that there is a line in the job details showing that client-side deduplication is in
use: Using OpenStorage client direct to backup from client.
Shortly after this the backup runs, and the deduplication rate is correctly listed as
dedup: 97.6%. Later in the job details, however, the output a second entry listing
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-41
nbdevquery –listdp
42
Within the NetBackup Administration Console, under Media and Device Management,
there are two easy ways to report on deduplication disk pool capacity. The first method
involves looking at the disk pool properties. The command line method uses the
nbdevquery -listdp options. Reporting on the deduplication disk pool in this
manner provides a view of the disk pool capacity because it is cached by the EMM
server.
The second method involves looking at the storage server properties. The command line
method uses the nbdevquery -liststs options. With a deduplication disk pool,
this method lists real-time data, pulled from the storage server when the command is
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-42
• The backup image may contain much data that is not unique and that is shared by
other backup images and cannot be freed.
• A NetBackup deduplication disk pool has regularly scheduled jobs, such as queue
processing and garbage collection, which need to run to free space. Some of these
tasks can be run manually. Refer to the NetBackup Deduplication Guide.
• These pools use a storage model based on files called containers. When a data
segment is deleted, it leaves an unused space in these containers, which is either re-
used for new segments or reclaimed during automatically-running container
compaction jobs. Container size depends on the specific MSDP implementation.
Because of these issues, when you use simple disk space reporting tools, such as those
provided by the operating system, you may not be able to accurately determine the
actual available space and capacity of a deduplication disk pool. Instead of using
operating system utilities such as df/du (UNIX) or the Windows explorer utility
(explorer.exe), use the NetBackup-provided commands that more accurately report on
deduplicated disk, as shown on the slide. To prevent failed jobs or other issues, prevent
deduplication disk pools from reaching their capacity.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-43
44
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.
7-44
45
As well as viewing disk pool capacity in OpsCenter, you can also view a variety of
deduplication reports. In Veritas NetBackup OpsCenter 8.1.2, the following
deduplication reports come with the product:
Refer to the NetBackup OpsCenter Administrator’s Guide for details on these reports.
7-45
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
46
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
• 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
7-46
7-46
Prior to NetBackup 8.0, deduplication used the Blowfish 128 bit algorithm for
encryption. Starting in NetBackup 8.0, the AES-256-CTR algorithm is used. Although
NetBackup 8.0 uses AES-256-CTR for encryption, encrypted MSDP backups prior to
upgrading to NetBackup 8.0 would still be stored using Blowfish. After upgrading to
NetBackup 8.1, NetBackup automatically performs a rolling upgrade of these Blowfish-
encrypted backups, and converts them to AES-256-CTR-encrypted backups. This may
have an impact on performance. For more information on this process, refer to the
About the rolling data conversion mechanism for MSDP section of the NetBackup
Deduplication Guide.
Deduplication caching
Use of client-side deduplication means the client compares deduplication fingerprints
that it calculates, to the fingerprints in the storage server’s database. Instead of
constantly querying this information back and forth, over a potentially slow wide area
network (WAN), the client can use a deduplication cache of fingerprints for data that
already exists on the storage server. When subsequent backups are run, fingerprints are
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
checked against this cache first, before querying the storage server. A high cache hit rate
indicates significantly reduced network communication between the client and storage
server, which is important when using client direct to back up remote clients over high
latency networks. Pre-populating this cache can significantly reduce the data and
fingerprint checking that needs to be performed over the network. Several solutions
exist, depending on the NetBackup release level. For details and configuration options
for other NetBackup releases, see Article 100003816: NetBackup deduplication client
WAN backup: how to seed the fingerprint cache to speed up the initial backup at:
http://www.veritas.com/docs/100003816.
7-47
• 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
48
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.
7-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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-49
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.
7-50
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.
7-51
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.
7-52
52
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-53
53
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-54
A. True
B. False
54
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
7-55
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
End of presentation
7-57
© 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.2:
Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-1
8-2
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.
8-3
After completing this topic, you will be able to define media manager
storage unit concepts.
8-4
NetBackup refers to tape devices as Media Manager devices, because they are managed
by a component of NetBackup known as Media Manager.
robotically-controlled tape library, NetBackup also requires the device path to the
library’s robot, to be able to control that robot.
Device and media compatibility: Besides being robotically controlled or stand alone,
media manager devices have another characteristic. The read/write or I/O device (the
tape drive) is actually separated from the recording media (the tapes). Not all tapes are
compatible with all tape drives. If an incompatible tape gets loaded into a tape drive,
then I/O errors can occur. NetBackup needs to be able to match appropriate media type
for the media (tapes) and devices (tape drives).
8-5
Device and media compatibility example with multiple drive types in a library
In some cases a tape library can have multiple tape drive types. For example, a library may
have two types of drives, both LTO4 and LTO5. The LTO4 drives may be assigned a NetBackup
drive type HCART2, and the LTO5 drives the NetBackup drive type HCART3. When making
media known to NetBackup, a corresponding NetBackup media type should be assigned to
the media that matches the drive type for the intended drive. Media intended for the LTO4
drives should be given a NetBackup media type of HCART2, while media intended for the LTO5
drives should be given a NetBackup media type of HCART3.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-6
NetBackup needs to be told about the tape drives that can be used by media servers for
backup and restore operations. In earlier modules we have seen that NetBackup’s
primary backup destination is the storage unit and that a storage unit refers to one or
more physical devices with common attributes. For backups going to tape, we need to
have media manager storage units, which refer to the tape drives connected to a media
server that NetBackup is aware of. We have also been introduced to the Storage Unit
Group which is a named list of storage units. NetBackup can target either a storage unit
or a storage unit group as a backup destination. When a storage unit group is the target,
only one of the storage units defined in the group will be chosen as the target.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Not only does this slide review the differences between devices, storage units and
storage unit groups, it also introduces some of the media manager specific attributes
that media manager devices must have in order to be referenced by the same media
manager storage unit. If two media manager storage devices have differences in these
attributes, then multiple storage units will be required. But, those storage units could be
members of the same storage unit group. And, media manager storage units can exist
with non-media manager storage units within the same storage unit group.
8-7
With robotically controlled tape drives, each tape drive and the robot control device
appear as separate devices to a NetBackup server. A tape library with four tape drives
properly connected to NetBackup server should show five devices in the NetBackup
server: four tape drives and a robotic device. A robot is also sometimes referred to as a
medium changer on Windows hosts.
A NetBackup server uses the tape drive interface to perform operation such as
positioning the tape to a tape file, reading data from the tape, or writing data to the
tape. The robot control interface/device is used to perform operations such as moving
tapes from library slots into drives or moving tapes from drives back into their slots. For
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
libraries that are dedicated to a single NetBackup media server, that NetBackup media
server will be considered the robot control host, and completely control the robot
through the appropriate interfaces. The robot control host is designated in the
NetBackup configuration and is the NetBackup server that is responsible for directly
interfacing with the robot control interface, and moves the tapes from library slots to
drives, and back again.
8-8
A robotic tape library and it’s drives do not have to be dedicated to a single NetBackup
server, especially in a storage area network (SAN). A tape library that is configured to be
accessed by multiple servers is sometimes called a shared library. In these cases all the
tape drives may be seen by all servers, or there may be some tape drives that are
dedicated to specific servers.
Robot control interfaces, due to a limitation of the hardware, do not respond properly
when multiple servers attempt to access them simultaneously. A single NetBackup
server must be defined as the robot control host: the server responsible for directly
interfacing with the robot control interface. Any other server that wishes to move tapes
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
between slots and drives within the library does so by making a request, over TCP/IP, to
the robot control host., which then issues commands to control the tape robot. Data
movement operations, such as tape positioning, reading data from a tape in a drive, or
writing data to a tape in a drive, is performed directly by each NetBackup server that is
directly accessing the tape device. It should be noted that in some cases the robot
control host is not a NetBackup server. An example would be Automated Cartridge
System (ACS) libraries, where the library is controlled by ASCLS software that runs on
another host. For ACS libraries, NetBackup servers interact with the ACSLS host to
perform robotic control. Do not confuse a shared library with the NetBackup-licensed
Shared Storage Option (SSO), which allows multiple NetBackup servers to access the
same tape drives.
8-9
Tape
library
Tape Stand-alone
library tape drives
10
• Media Manager: A Media Manager storage unit uses either robotically controlled or
stand-alone tape or optical drives.
• NDMP: NDMP storage units are controlled by NetBackup but attach to NDMP hosts
and require that you have the NetBackup for NDMP option installed. See the
NetBackup for NDMP Administrator’s Guide for more information.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-10
ms1_tape_stu ms2_tape_stu
Drives 1-3 Drives 4-6
Media Media
server 1 server 2
LAN
NetBackup
clients
11
1. All the devices use the same type of media. Two tape drives that used different
media, such as LTO4 and SDLT2, could not be referred to by the same storage unit.
2. All the devices referred to by the storage unit are either all stand-alone devices or
are controlled by the same robotic library.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Media manager storage units can also control what media server is used. If the device
configuration wizard is used, after devices are discovered, associated storage units are
created. One storage unit per robot per drive type per media server is created. In the
example on this slide, the tape library has 6 tape drives, all of type LTO4. Three of the
tape drives are visible to media server 1 and the other three are visible to media server
2. The device configuration wizard creates two storage units. The first, STU-A, refers to
the three LTO4 drives in the robot known to Media Server 1, while the other storage
unit, STU-B, refers to the other LTO4 tape drives known to Media Server 2.
On Drive Selection from a media manager storage unit: At the time that a backup job
needs a drive, if the storage unit refers to multiple available, idle tape drives, NetBackup
uses a LRU/round robin mechanism to determine which drive it should assign to that
job.
8-11
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.
Media manager storage units designating Any Available media server allow NetBackup
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
to choose which media server and drives would be used. However, in our example, each
specific tape drive is still assigned to only one media server. If one media server is shut
down, only half the tape drives would be available for use.
8-12
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
media servers. We are also showing two storage units. Use of STU-A would cause a job
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
to use Media Server 1 and any of the 6 tape drives while use of STU-B would case a job
to use Media Server 2 and any of the same 6 tapes drives. Regardless of the storage
units used, the drives would be one of the same 6 available to both media servers. If
one of the media servers was shut down, the other media servers would still be able to
use any of the shared tape drives. Like with non-shared storage, we can also created a
storage unit that allows NetBackup to use any available media server.
8-13
After completing this topic, you will be able to use the Device Configuration
Wizard to configure new tape devices.
14
8-14
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:
that the devices are available through operating system tools, such as:
• HP-UX: ioscan
• AIX: lsdev
• Linux: cat /proc/scsi/scsi, lsscsi
• Windows: Device Manager (devmgmt.msc)
4. After NetBackup is installed, use the scan, tpautoconf –t, and tpautoconf –r
NetBackup utilities to verify the operating system devices. NetBackup on Solaris will
additionally have the sgscan utility.
5. At this point, if you do not see the devices, troubleshoot the problem using standard
operating system tools or vendor specific utilities until you can see the devices. For
example, check your SAN zoning or persistent binding configuration.
8-15
8-15
16
Veritas recommends that you use the Device Configuration Wizard to configure robots
and tape drives. The wizard configures a robot, its drives, and a storage unit. This wizard
discovers the robots and tape drives that are available, and is the preferred method of
device configuration. For the robot types that support device serialization, the wizard
discovers the positions of the drives within the library.
The wizard also provides the ability to customize drive naming rules, robot and drive
properties, SAN clients, and storage units. The wizard works by querying available
device paths on each media server for devices and for each discovered device (drives
and robots), collects information about those devices, such as serial numbers, type of
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
device, and so on. Device serial numbers are used to find out which tape drives are
controlled by which robots (tape libraries) and are visible to which media server and if a
drive is shared between two or more media servers. The use of the device serial
numbers to correlate drives, robotic libraries and media servers is called device
serialization. The wizard then updates the NetBackup database with the collected
information and assigns device names, robot control hosts and NetBackup device types
for the discovered devices.
Using the device configuration wizard is the preferred method for device configuration.
Devices can be manually configured as well, however the user would be required to
collect the same information and manually update the NetBackup database with the
information. Refer to the Veritas NetBackup Device Configuration Guide for details.
8-16
After completing this topic, you will be able to monitor devices using the
NetBackup Administration Console.
17
8-17
tpconfig -d
18
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.
8-18
tpconfig -d
19
There needs to a robotic entry for each media server that needs to communicate with a
library. These can be added manually but as we can see, the Device Configuration
wizard adds the required entries as part of its processing. After the Device
Configuration Wizard runs, you can view the properties of the robots that were
configured. To do this:
1. Expand Media and Device Management > Devices and select Robots.
2. In the details pane, select the robot you want to view, and press Enter. You can also
right-click and select Change.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-19
lnxmaster lnxmedia
Robot
Robot control
host
20
This example shows entries for a robot that is ‘shared’ between two media servers.
Unlike tape drives which can be directly accessed by multiple NetBackup media servers,
the robotic control interface can not, a robot control host must exist. Every media server
that needs access to a robot including the robot control host, will have an entry in the
enterprise media manager for that robot but only one of those entries will be for the
robot control host. The other entries will indicate that that particular media server
must contact the robot through the control host.
In the example above, there are two entries for the robot known as TLD(0). The entry
for winmaster.example.com shows this it is the robot control host (chosen by the device
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
configuration wizard). The other entry is for winmedia.example.com and was created by
the wizard because winmedia.example.com sees a tape drive that is controlled by the
robot, TLD(0) so needs to communicate with winmaster.example.com as the robots
robotic control host. In our environment, both winmaster and winmedia can be robot
control hosts but the wizard chose winmaster because it scanned winmaster first.
Again, the output from tpconfig –d can show robot entries based on the server it is
executed on. For a robot control host, it will show the path to the robotic control
interface. If executed from a NetBackup server that is registered with the robot in
NetBackup, but that is not the robot control host, the output identifies what host is the
robot control host.
8-20
vmoprcmd
21
You can use the Device Monitor to determine a drive’s properties and characteristics,
such as its name, host (the media server to which it sends its backup data), and type
(such as DLT). You can also control drives using the Actions menu or by right-clicking a
drive and selecting an action from the drop-down menu. Such actions include activating
a downed drive, resetting a drive, manually invoking drive cleaning, and changing the
comments associated with a drive. To display details about a particular drive, from the
Device Monitor, right-click a drive and select Drive Details from the drop-down menu.
The control column shows the state of the drive:
• TLX/SCAN-TLX (where X depends on robot type) indicates the drive under robotic
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The vmoprcmd command enables you to perform operator functions on drives. For
example, to bring a drive up from the command line, enter:
vmoprcmd -up drive_index [-h device_host]
8-21
bpstulist
22
A Storage unit type of Media Manager refers to all tape drives of a particular density
that are either stand alone or under control of a specific robot. In the example on the
slide, this storage unit will direct backup data to HCART drives within the TLD(0) library.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The value of Media Server shows that winmaster.example.com will be the media server
used. Clicking on the Media server dropdown field displays a list of all the media servers
configured to have access to HCART tape drives within the TLD(0) library.
The media server value of Any Available configures the storage unit to use any of the
media servers that see this type of drive within the specified library. If, at a later time, a
new media server is configured for these drives in this library, it will automatically be
used with this storage unit. A similar result can be obtained by creating individual
storage units for each library, per drive type, and per media server, and then adding
those storage units to a storage unit group. However, if a new media server is given
access to the library, a new storage unit would need to be created and it would have to
be manually added to the storage unit group.
8-22
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.
23
This slide shows some of the ways you can query NetBackup about your device
configuration. tpconfig –d queries the Enterprise media manager for devices that have
been registered with the media server the command is run from. You run this command
from a NetBackup server. It can also be used to manually register a device with a
NetBackup server.
vmoprcmd queries all of the ltid processes to report the status of drives on all
NetBackup servers in a domain. It can also be used to manage the state of drives
(up/down).
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-23
After completing this topic, you will be able to describe volumes, volume
pools, and volume groups.
24
8-24
25
Media Manager volumes are tapes that have been assigned media IDs and other
attributes, which are recorded in NetBackup database. You should know the following
about volumes:
• A piece of media becomes a volume when Media Manager assigns a media ID (also
known as the Recorded Volume Serial Number or RVSN).
• NetBackup requests volumes from Media Manager using the media ID.
• NetBackup writes a label to the media that contains the media ID.
• If a tape cartridge has a recognized external barcode, this is also recorded in the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
NetBackup database, and used to generate the media ID for a new tape. The
barcode is sometimes referred to as the EVSN or External Volume Serial Number.
Note: The media ID is limited to six characters, and NetBackup only reads thirteen
characters on a bar code label.
To control how media IDs are generated from barcode values, define media ID
generation rules that specify which characters of a bar code on a cartridge are to be
used to generate a media ID. Multiple media ID generation entries can be specified,
allowing media ID generation to be specific for each robot and length of barcode, and
offering flexibility for multimedia.
8-25
26
NetBackup assigns each volume a unique media ID. This media ID may be assigned
manually, or it may be automatically generated using bar codes and a process known as
robotic inventory. Considering the large number of tapes in an enterprise backup
environment, most environments use bar codes and robotic inventory. Manually
assigning media IDs is only performed in special circumstances.
The maximum length of a media ID is six characters and is typically based on the bar
code. If the bar code is longer than six characters, by default NetBackup uses the last six
characters as the media ID, as shown in the slide on this page. Customizing this behavior
is shown later in this topic.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The media ID of each volume is stored in the NBDB and is also written on the tape itself.
The location where the media ID is written is called the tape header, or label. Use
caution when assigning media IDs. To avoid confusion, Veritas recommends having the
tape’s Media ID be identical, or very similar to, its bar code. Also, to avoid problems
when restoring data, ensure that any media id generation rules you configure in your
production environment are also configured in your disaster recovery environment.
If robotic inventory is used on tape cartridges that have no barcode labels then
NetBackup assigns those tapes unique media IDs based on a simple mechanism starting
with the initial media ID A00000 (the letter A followed by 5 zeros) and incrementing the
value until a unique media ID is found.
8-26
NetBackup organizes volumes in volume pool. The volume pool used by a backup job is
specified as part of the backup policy definition. The following volume pools exist, by
default:
• NetBackup: The default volume pool used by most policies initially and the pool new
tapes discovered by robotic inventory are assigned to by default.
• DataStore: The default volume pool for some integrated third-party applications.
• CatalogBackup: The default volume pool for storing NetBackup catalog backups.
• None: The volume pool used for tapes NetBackup should not write to, such as
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
In addition to these predefined pools, you can create your own pools to segregate
backups to different tapes, such as for backup images staying onsite and images being
sent offsite, or for backups of different types of applications. The scratch pool is an
optional volume pool that you can configure to store unused, free tapes.
8-27
28
The scratch pool is an optional volume pool that you can configure. You can have only
one scratch volume pool per NetBackup domain. Any media manager storage unit can
have volumes that are in the scratch pool. If the scratch pool is configured, NetBackup
moves volumes from that pool to other pools that do not have volumes available, when
required. The name of the scratch pool does not matter. However Veritas recommends
creating a pool with a defining name, such as Scratch or free_tapes.
NetBackup does not assign volumes while they are in a scratch pool, and the scratch
pool cannot be targeted by a backup policy. A volume moved from the scratch pool to
another volume pool due to backup needs, remains in the other pool until it is
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
unassigned (all image reach their retention). NetBackup moves volumes back to the
scratch volume pool after the volume is unassigned. To disable this feature, update the
NetBackup database using the following command:
nbemmcmd -changesetting
-return_unassigned_media_to_scratch_pool no
-machinename master_server
8-28
TLD0
Eject Vault
Volume Group:
---
Volume Group:
Volume Group:
OFFSITE
000_00000_TLD
29
A volume group is a logical group of volumes that are located at the same physical
location. This allows NetBackup to track media by location. Each robotic library can have
one or more pre-defined volume groups with a name based upon the robot number,
robot type, and media type. For example, the first library defined might have the library
name “TLD0”, which would have the volume group 000_00000_TLD. If a volume is in a
the 000_00000_TLD volume group, it is considered to be resident in the TLD0 library. If
another tape is in the same library but of a different media type (in other words, in a
different media manager storage unit) then that tape will be assigned to another
volume group such as 001_00000_TLD.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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:
8-29
8-30
Volume groups allow you to group media by its location. Volume pools are used when
you want or need different backups to be placed onto different sets of tapes. The reason
for separating backups are dependent on your needs and problems you need to
overcome. For example, enabling parallel restore of two extremely critical systems by
making sure the backups of those two systems don’t go to the same tape. Another
example is having a local set of backups kept onsite but also having copies of those
same backups stored at an offsite location for long term retention.
However, one needs to be judicious here. The more volume pools you create, the more
management you have to perform. Additionally, NetBackup already segregates tapes
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
based on retention level, by default, so creating separate volume pools for separate
retention tapes is often unnecessary.
A volume group are labels for both robotic libraries and non-robotic locations. There can
be multiple non-robotic volume groups, just as there can be multiple robotic libraries.
Changing volume group designation for a volume provides the means for NetBackup to
track a volume’s physical location. Using the vmdelete command, you can delete
volumes from the NetBackup database by specifying the group name, rather than
individual media IDs. Multiple volume pools can exist in the same location. For
example, a robotic library may hold volumes assigned to your MSSQL_Pool (tapes for
MSSQL backups) and hold volumes assigned to your ORACLE_Pool (tapes for Oracle
backups).
8-31
After completing this topic, you will be able to use the Robot Inventory to
configure new media.
32
8-32
Command Line
• Provided by Media Manager commands.
• Use vmadd, vmupdate, and vmchange commands.
33
• The Volume Configuration Wizard runs the NetBackup Robot Inventory, which
scans for tapes in available tape libraries, and can be configured to automatically
add them to the NetBackup configuration. After you run the robot inventory to
configure media, each piece of media has a unique media ID in the NetBackup
media databases. The wizard or utility creates media that have a media type
determined by the drive type. The default media type is used. Additionally, volumes
can be added manually.
• Similar to the wizard, the NetBackup Administration console also supports the robot
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
inventory under the Media and Device Management section of the NetBackup
Administration Console. Additionally, methods for manually configuring volumes is
provided.
• The command-line has a number of commands that are available to perform
volume configuration tasks. There are some commands, which initiate a text-menu
interfaces, such as tpconfig. Refer to the NetBackup Commands Reference Guide, or
the command man pages on UNIX, for details and syntax of NetBackup commands.
8-33
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
34
Using robot inventory enables accurate tracking of volumes within robotic libraries,
including determining which volumes are in a robot and their exact slot location. The
steps on this slide describes tasks that need to be performed either before or during the
robotic inventory. These tasks include creating all custom volume pools, bar code rules,
and media ID generation rules that may be needed. Newly configured rules are not
applied to media that already exists in NetBackup. For any media that was added before
the rules were created, either manually update the media or delete the media and re-
run the robot inventory. At that point, the rules will be applied.
A bar code rule specifies criteria for assigning attributes to new robotic volumes.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
NetBackup assigns these attributes by using the bar code for the volumes cartridge that
the robotic library provides along with your bar code rules. After bar code rules are
established, NetBackup automatically assigns media, based on the bar code tag, to a
specific volume pool and media type.
Media ID generation rules enable you to override the default media ID naming method
that NetBackup uses for new tapes that have barcodes. The default method uses the
last (rightmost) six characters of the bar code provided by the robot to generate the
media ID. Use the rule to control how NetBackup creates media IDs by specifying which
characters of a bar code are used in the media ID. In addition, you can specify that
alphanumeric characters are to be inserted into the ID. Multiple rules can be used to
accommodate different robots and bar code lengths.
8-34
vmpool
35
1. Select Media and Device Management > Media > Volume Pools.
2. Click on the star-burst icon, or selecting the appropriate option in the Actions menu
or by right-clicking on Volume Pools in the navigation tree.
8-35
vmupdate
36
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.
8-36
Robot
control
host
37
When the Robot Inventory dialog box is displayed, it allows for various inventory
operations to be performed. Each operation communicates with the robot control host.
You need to make sure that the Device Host field shows the name of the robot control
host for the robot you wish to inventory. If you selected the wrong entry from the
Robots list in the Object tree, this gives you a chance to change the value.
Selecting the Show contents radio button and clicking Start runs the Show Contents
inventory operation. This function initiates the most basic NetBackup inventory
operation requesting the robotic library for a list of its slot contents. This function
simply displays the response from the robotic Library. Most modern robotic libraries
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
cache this information so the operation is relatively fast. However, some older robotic
libraries will physically pole each slot at the time of the request so it could take longer.
The Show Contents inventory operation is useful for determining the contents of a
robot as follows:
• If the robot has a bar code reader and contains media with bar codes, the report
displays whether each slot has media and lists the bar code for the media.
• If the robot does not have a bar code reader or does not contain media with bar
codes, the report displays whether each slot has media.
• If the robot is an API robot (like an ACS robot), the report displays a list of media
found in the robot.
8-37
38
The Compare Contents with volume configuration function is similar to the Show
Contents operation but takes the operation a step further. Instead of simply displaying
the response of the robotic library, it compares the response with the contents as is
stored in the NetBackup. The comparison is displayed in the Results field and shows
discrepancies between what the robot reported and what the NetBackup configuration
thinks should be in the library. Each discrepancy is indicated by a value of yes in the
Mismatch Detected column of the output. This output includes the Media ID value
since this operation accesses not only the library but also the information in the
NetBackup database.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-38
39
The Preview volume configuration changes inventory function, like Show Contents,
requests a slot inventory from the robotic library, and like Compare contents with
volume configuration, compares the response from the robot with what is registered in
NetBackup. However, instead of displaying the results or the discrepancies, based on
the discrepancies found, this function derives a set of operations, that if applied to
NetBackup, would update the database to reflect what is currently in the robot and
displays the proposed changes. Note that no changes are actually performed. This
operation simply displays what would be done if the operations were executed.
Also take note that with this inventory operation selected, the Advanced Options
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
button is now available. This allows you to see some of the effect using advanced
options would have on the database like the effect media id generation rules would
have on the value of the generated Media ID for new media discovered without actually
making the changes to the database.
8-39
40
The Advanced Robot Inventory Options dialog has various tabs. The Media Settings tab
is separated into two sections: the Existing media frame and the New media frame.
The Existing media frame allows you to specify volume groups for media already known
to NetBackup for the purposes of tracking the location of the media. As stated
previously, a volume group identifies the physical location where media should be
found.
• The Media which have been removed from the robot should be assigned to the
volume group field is used to set the volume group when a tape is later found to be
missing during a robot inventory. By default the volume group for a tape will be set
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-40
The New Media frame lets you set properties used for newly discovered media.
• Use the following Media ID prefix is used when the robot does not support bar codes, or
the volume inserted does not have readable bar codes, by assigning a prefix to the new
volume’s media id. The prefix becomes the leading part of the new media id and is made
unique by appending numerals to generate a unique 6 character id.
• Label optical media is enabled only if you selected an optical robot to inventory.
• Use barcode rules tells NetBackup to consult Barcode Rules to assign volume pool and
media type designations to newly discovered media.
• Media type and Volume pool fields are used to override NetBackup’s normal volume pool
and media type assignment policies. If either of these fields are set, then the specified
value will be used even if the barcode rules check box is checked. These fields act as one
time overrides., as they will be reset to DEFAULT the next time a robot inventory is run.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-41
vmrule
42
A bar code rule specifies criteria for assigning attributes to new volumes discovered by
robotic inventory. The attributes are assigned based on what barcode tag matches the
barcode label of a given volume.
• The Barcode tag is a string used to match the left-most portion of the barcode label.
If the barcode label matches multiple tags then the rule whose tag matches the
largest portion of the barcode label is used. There are two special barcode tag
designations: NONE which matches any cartridge where a barcode label could not
be read and DEFAULT which is used if none of the other barcode tags match the
barcode label. The DEFAULT barcode tag is often used to change NetBackup default
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
behavior of placing new volumes into the NetBackup volume pool. Without this
barcode tag, any new volume not matching any barcode tags will be assigned to the
NetBackup volume pool and be given a media type based on the drive types within
the robot. Note: The actual text of the BARCODE tag input are the letters DEFAULT
but that NetBackup displays this RULE’s tag as <DEFAULT>. The NONE barcode tag
works the same.
• Maximum Cleanings/Maximum Mounts is used by NetBackup as a usage limit so
tapes and cleaning cartridges do not get overused. A value of zero indicates that no
limit exists. This field allows an initial value to be specified for new tapes discovered
through robotic inventory. These limits can be changed after the tape is made
known to NetBackup at any time. Tapes whose labels do not match any of the tags
or tapes that were inventoried with barcode rules enabled get zero as the default.
8-42
8-43
44
Every volume used by NetBackup needs to have a unique, six character media id. For
robotic libraries with barcode reading abilities, the value of the barcode label read by
the robot’s barcode reader can be used to derive the media id for newly discovered
media. By default, NetBackup uses the right-most 6 characters of the barcode label as
the media id that is assigned to the new tape. This can cause problems for two or more
tapes with barcode labels longer than six characters, if the resulting media ids would
not be unique. If two tapes each had the barcode label values S00006L1 and D00006L1,
NetBackup would try to assign both tapes the same media id 0006L1, and the inventory
process would produce errors.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Media ID generation rules allow you to specify what characters of the barcode are used
to generate the media ID. To create a new media ID generation rule, click the Media ID
Generation tab and click the New button, and then specify the properties as follows:
• Robot number: The number associated with a robot. TLD(0), for example is robot
number 0.
• Bar code length: The length of barcode this rule applies to. Barcodes of lengths
other than this value will not use this rule.
8-44
There is the potential for conflict when you have multiple tape libraries with multiple tapes.
You can use Media ID generation rules to uniquely identify tapes and associate them with
their owning libraries. For example, create media ID generation rule #A:2:3:4:5:6 for tapes
belonging to Library A, and create media ID generation rule #B:2:3:4:5:6 for tapes belonging
to Library B. This generates media IDs A00000, A00001, A00002, and so on for Library A, and
media IDs B00000, B00001, B00002, and so on for Library B. The problem with this scenario is
that the external bar code labels do not reflect the unique media IDs. If all of your tapes are
stored together, you cannot easily identify which tapes belong to which library. Two possible
solutions are:
If a particular barcode label has a length that does not correspond to any media id generation
rules that exist for that robot then NetBackup uses it’s default behavior.
Note: There is no command line interface to manage media id generation rules.
Some examples of media ID generation rules are given in the table on the slide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-45
46
8-46
vmquery –a -b
nbemmcmd –listmedia –allrecords -brief
47
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.
8-47
48
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.
8-48
• 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
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.
8-49
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.
8-50
50
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.
8-51
51
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-52
52
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-53
53
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-54
54
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-55
A. NetBackup
B. DataStore
C. None
D. Scratch
55
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-56
A. NetBackup
B. DataStore
C. None
D. Scratch
56
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
8-57
End of presentation
8-58
© 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 Tape Storage lesson in the Veritas NetBackup 8.1.2:
Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-1
9-2
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.
9-3
After completing this topic, you will be able to view and change robot and
tape drive settings, including drive status, and perform drive cleaning.
9-4
Path properties
General drive
properties
tpconfig -d
Caution: Manual configuration of tape drives is prone to human error, therefore Veritas
recommends configuring tape drives with the Device Configuration Wizard.
drive manually or through the device discovery wizard, you can use drive name
rules.
• Host and path information defines the hosts and that host’s specific device path to
this tape drive. If the drive is shared, there will be one entry for every media server
accessing this drive.
• Drive Information allows you to specify the following information:
• The Drive type specifies the type of drive you are adding.
• Use the Cleaning Frequency (In hours) property to set the desired number of
mount hours between drive cleanings, for drives that do not support TapeAlert.
• Drive is in a robotic library specifies whether the drive is in a robotic library.
• The Robotic library specifies a robot that controls the drive.
9-5
9-6
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.
You can also use the stopltid and ltid commands to manage the Media Manager
daemons or services. The stopltid command stops ltid, avrd, and the robotic
services; ltid starts ltid, avrd, and the robotic services. On Windows you can also stop
and start the Media Manager services using Windows Computer Management, by
restarting the NetBackup Device Manager service.
9-7
The robtest utility allows you to control a robot using the robot’s control interface,
on the robot control host. It lets the user issue low level robotic control commands to
control the robotic arm, change access to mail slots, transport media between locations
in the robot (slots, drives, mail ports) and query information about the robot just like
NetBackup does. You can use robtest, for example, to see if the robot is receiving or
executing robot control commands, view contents of slots, drives, and mail ports, find
out how many drives, slots and mail slots are available, if there is a barcode reader, and
so on.
The robtest program searches the NetBackup database and presents a menu of
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 (?).
Note: It is recommended to use robtest only when the tape device is not in use by
9-8
9-8
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.
9-9
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
slot 11 (addr 4106) contains Cartridge = yes
Barcode = 09000AL1
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-10
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:
Note: The Media Manager Device daemon (ltid) must be running on the host being
monitored, or the lists in the Device Monitor detail panes are blank.
9-11
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.
9-12
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. The script is located in <install
path>\VERITAS\NetBackup\bin\goodies on a windows master/media server and in
/usr/openv/netbackup/bin/goodies on a UNIX master/media server.
1. Select Media and Device Management > Devices > Drives or select Media and
Device Management > Devices > Robots.
2. Select a device or a robot.
3. Select Actions > Drive Diagnostics or Actions > Robot Diagnostics.
In either the Drive Diagnostics or Robot Diagnostics dialog box, click Start to run the
drive or robot diagnostic tests. The results of the tests are displayed in the Results pane.
Note that drive diagnostics will perform I/O to an available tape (a tape without data
already on it) in the NetBackup volume pool. Robot diagnostics will not perform any
I/O, however will move tapes from slots to drives, and back.
9-13
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.
a cleaning tape by the number of times it has been used. For each cleaning tape, you
can specify the number of cleanings that remain. You can change the number of
cleanings at any time in Media Manager. Each time the tape is used, that number
decreases by one. When the number of cleanings reaches zero, Media Manager stops
using the cleaning tape. To configure a cleaning tape:
1. Specify the Media type setting for the cleaning tape’s designation (such as
DLT_cleaning_tape).
Note: The cleaning tape is automatically assigned to the None volume pool.
2. Set the number of cleanings. (The default setting is 25.)
9-14
TapeAlert
TapeAlert notifies Media Manager that the drive needs to be cleaned.
Frequency-based
The drive is cleaned according to an administrator-defined frequency.
Manual (operator-initiated)
• Manually invoked in the Device Monitor or with tpclean.
• Use robotic device controls directly.
15
This slide shows the various methods you can use to perform drive cleaning.
• Robotic controlled cleaning: Some robotic tape libraries have automatic drive
cleaning functionality. This is also referred to as hardware-based cleaning, library-
based cleaning, or auto-cleaning. With robotic automatic cleaning, the tape drive
sends an alert to the robot, notifying the robot that the drive requires cleaning. After
a backup tape is unmounted, the robot mounts the cleaning tape and cleans the
drive. NetBackup is not involved in this process.
• TapeAlert: Another method of automatic cleaning uses the TapeAlert feature, which
allows reactive cleaning for some drive types that support the TapeAlert capability.
This method is also called reactive cleaning.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-15
• Set Cleaning Frequency: Set the desired number of mount hours between each
drive cleaning.
Alternatively, to perform drive cleaning using the command line, the tpclean
command enables you to monitor Media Manager tape drive usage and optionally
configure tape drives to be automatically cleaned (except drives in ACS, ODL, or TLH
robots, or QIC drives).
9-16
17
9-17
Image retention
• How long the image is available for restores.
• Required setting on backup policy schedules
• Typically based on the restore service level agreement (SLA) for
the data.
18
There are two distinct types of expiration in NetBackup: volume expiration and image
expiration. Likewise, the volume expiration date and the image expiration date have
distinct meanings.
Volume expiration: You can change the expiration date for volumes. The volume
expiration date refers to the age of the tape media and is the time at which the tape is
considered too old to be reliable. When the expiration date has passed, a volume can
still be read but is not mounted for a write. The volume expiration date is not the same
as the retention period for the backup data (images) on the volume. The volume
expiration date refers only to the physical expiration of the volume and is independent
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-18
19
This slide is a reminder that the volume expiration date is set in the Expiration date
section of the Change Volumes dialog box. It also shows that the retention period is
displayed in the Schedule section of the policy.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-19
ABC123
EOM
Image
NetBackup database
database
Valid Ret Volume Media Header
Media ID Assigned .f file
Images Level Pool State info
ABC123 N 0 --- scratch AVAILABLE
20
When a backup job is initiated, NetBackup selects the required piece of media based on
the parameters of that specific backup job. The policy and schedule dictate the required
storage unit, volume pool, and retention level. The actual media selected is discussed
elsewhere in this lesson. The example on this and the following slides shows the life
cycle of a tape—from unassigned, to assigned, and then unassigned again.
In this example, a backup job is requesting a tape from the servers pool with a two-
week retention. If a tape is not available in the servers pool that meets all the necessary
criteria, NetBackup will attempt to move a tape from the scratch pool to the servers
pool for use in the backup. Also, this example shows a tape that has already been
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
labelled with media ID ABC123. Following the label (sometimes known as the media
header), is a mark that shows the logical end of the tape. This is sometimes known as
an End of Data (EOD) or End of Media (EOM) mark, and indicates to any tape drive
reading the tape that no more pertinent data exists past this mark, even though it is not
the physical end of the tape. When the tape is first added to NetBackup, an entry is
made in the EMM database. The entry includes the media ID of the tape. Initially, the
tape is unassigned and the media state is AVAILABLE.
9-20
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 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.
9-21
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.
9-22
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 Image database. 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 Image database, so
restores of that backup are no longer possible without further actions (such as an
Import operation, discussed elsewhere in this lesson). Although Image1 is removed
from the database, the data for Image1 still physically resides on the tape. No action is
automatically performed to physically erase the data.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Depending on when Image2 and Image3 were written, they may also be expired and
removed during the initial image cleanup job or during a subsequent image cleanup job.
For example, if the backups were each written one day apart, Image2 will expire a day
after Image1’s backup expires, and Image3 will expire two days later. Each time images
expire, the Image database is updated to reflect the number of valid images that are still
being tracked on this tape. When Image1 expires, if Image2 and Image3 are still on the
tape, the free space made available by Image1 is not available for use. If that tape was
full, only when all images are expired is the tape made available. If the tape is not full,
new backups will only be written after the End of Media mark.
9-23
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 Image database indicates there are no longer
any valid images associated with the media ID, the media is ready to become
unassigned, and have its media state set to AVAILABLE. This occurs during the
NetBackup image cleanup. Image cleanup occurs after each successful backup session
(during any short period of backup inactivity after backups have run). However, even if
there is no inactivity, due to a busy backup environment, a cleanup interval occurs every
12 hours, by default. This value is set in the NetBackup master server host properties >
Clean-up > Image cleanup interval. If the media originally came from the scratch pool,
then it will be returned to that pool. The media life cycle process begins again.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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,
manually re-labeled, or erased then the old data will be overwritten by new backup
images. At this point, with third-party software and tools it may be possible to extract
the old data from the tape, but this is outside the scope of what is possible with
NetBackup. The data is considered unrecoverable.
9-24
25
All volumes have a media state, which changes based on a number of factors, such as
how much the volume is used or the type of backup written to it. The most common
media states are:
• AVAILABLE indicates that no active backup images are currently associated with this
tape. This can happen if:
• This is a new tape; NetBackup has never written data to it.
• NetBackup has used this tape, but all images on the tape have met their
retention and expired automatically.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-25
• MPX_MEDIA is a media state that indicates that this tape contains multiplexed
backups. MPX can be associated with tapes that are Active, Full, or Imported.
Backups that use the same storage unit, volume pool and retention can be
multiplexed to the same volume, only if allowed through policy and storage unit
multiplexing settings.
• WORM is a media state that indicates that this tape is a Write-Once-Read-Many
(WORM) volume. WORM media is used to protect key data from unwanted
modification or tampering, or to meet compliance regulations. For more information
on WORM media, see the NetBackup Administrator’s Guide.
• Multi-Retlev refers to multiple Retention Level, and is a media state that indicates
that the volume contains backups of more than one retention level.
• BE is a media state that indicates that the volume contains Backup Exec images.
9-26
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.
9-27
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
Note: An asterisk (*) in the ret level column indicates the media has images written to it
with multiple retention periods. The default for NetBackup is one retention period per
media.
9-28
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.
9-29
30
You can run various reports from the NetBackup Administration Console and from the
command line to gather information about media used in the NetBackup environment.
To access the media reports using the NetBackup Administration Console, expand
NetBackup Management and expand Reports > Tape Reports. Click the report you want
to generate. The example on the slide shows a Tape Summary Report, which
summarizes active and non-active volumes for the specified media owner (server)
according to expiration date. It also shows how many volumes are at each retention
level. In verbose mode, the report shows each media ID and the expiration date.
Tape reports can be run on using command line, for commands generally located in the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Tape Reports > Tape Lists shows status information for volumes that have been
allocated for backups.
bpmedialist -mlist -U
• Tape Reports > Tape Contents shows the contents of a volume as read directly from
the media header and backup headers. This report lists the backup IDs (not each
individual file) that are on a single volume.
bpmedialist -mcontents -m media_id -U
9-30
9-31
32
9-32
33
All volumes have a media state. The media state can change based on a number of
factors, such as how much the volume is used or the type of backup written to it.
NetBackup automatically controls the media state of a volume, but in some cases, you
can override the NetBackup setting. You can override some media states using the
NetBackup Administration Console. To do so, expand Media and Device Management >
Media. In the details pane, select a piece of media and select Actions. From the Actions
drop-down menu, select Freeze, Unfreeze, Suspend, or Unsuspend. Media that is
available (no time assigned) cannot have it’s media state manually changed and
attempts to freeze or suspend unassigned media generates an error.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-33
34
When a tape has at least one unexpired backup image, it is said to be Assigned. New
images are appended to these assigned (active) tapes. When all of the images on the
tape have expired, the tape automatically unassigned by NetBackup at midnight. You
can override some media states using the bpexpdate and bpmedia commands.
If you wish to reuse a tape with images before they naturally expire, you can use the
bpexpdate command with the –m media_id option to select the tape, and –d 0
option to set the date for all backup images on the tape to expire immediately. This
command additionally de-assigns the tape, so it becomes immediately available, even if
the tape was suspended or frozen.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Caution: Use this command with caution because it deletes the backup metadata from
the images catalog, and it changes the media state to AVAILABLE.
9-34
• If the problem was I/O errors on the tape, perform new backups.
• If the problem was I/O errors caused by other hardware, unfreeze the tape and
attempt to reuse it.
• If the problem was caused by a formatting issue, such as tapes from other
vendors unrecognized by NetBackup, either re-label the tape (for example with
the bplabel command), or set the ALLOW_MEDIA_OVERWRITE media server
host property, which allows NetBackup to simply overwrite specific media
formats encountered.
9-35
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.
9-36
37
1. In the object tree pane of the NetBackup Administration Console, select Media and
Device Management > Media.
2. In the right pane, select one more volumes to perform the operation on.
3. Either right-click the desired volume and select Move, or highlight the desired
volumes and select Actions > Move from the menu bar.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
If you select several media types in the volumes list, you see a Move Volumes dialog
box for each media type. Elements in the Move Volumes dialog box:
• Volumes to move: Shows the selected volumes on which the move operation will
be performed.
• Volume is in a robotic library: This option is used if you are moving volumes into or
out of a robot. Clear the check box if the volume is to be made stand-alone. Check
the box and fill in the associated attributes if the volume should be registered in a
robot.
• Device host: Select the device host for the robot from the pull-down menu. This
is the robot control host
• Robot: Select the robot into which you are moving the volumes from the pull-
9-37
down menu.
9-37
But, what happens if you cannot run an inventory against TLD(0) because it’s power
supply has broken (this being the reason you want to move this volume to TLD(1) so you
can perform the restore from the backup that is on this tape). You can take the tape
out of TLD(0) and place it into TLD(1) which is functional but since you cannot inventory
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
TLD(0) (no power), the record describing 0C0000 will still show as being in slot TLD(0) so
your attempts to inventory TLD(1) fail when the inventory sees the 0C0000L1 barcode
which is associated with that tape 0C0000.
The solution to this conundrum is MOVE. You can MOVE 0C0000 to STAND-ALONE
which simply updates the record in the NBDB describing 0C0000 so that it shows as not
being in any library. Then you can inventory TLD(1) which should now successfully
update 0C0000 to reflect that it is now in TLD(1).
9-38
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
from the menu bar.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Generally, after the pre-checks for the eject are complete, the Media tab displays the
volumes that you selected to eject, and the Errors tab is empty. The eject may not be
possible because of an error or a hardware limitation. If an error occurs, the dialog box
is displayed with the Errors tab opened. Click Eject to execute the eject. After clicking
the Eject button, NetBackup moves ejected media to the media access port (MAP), and
a dialog box appears, stating “Remove ejected media from the media access port. Do
you wish to continue with the eject?” If multiple tapes were ejected and not enough
MAPs exist, you will need to remove the tapes from the MAP before pressing Yes to
continue. Leaving tapes in the MAP may cause errors that the MAP already contains
media, thus preventing further tapes from being ejected from the library.
9-39
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.
2. In the right pane, right-click the desired volume and select Change, or select the
desired volumes and select Edit > Change.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-40
9-40
9-41
vmdelete
42
Deleting a volume removes the record that describes the volume from the NetBackup
database (NBDB). This operation does nothing to any physical data that may be on the
tape. In order to delete the record describing the tape from the NBDB, the tape must
be AVAILABLE, that is, unassigned. If the tape is assigned, you must first expire all copies
of the backups that NetBackup has a record of on that tape and allow the tape to be
unassigned, for example with the bpexpdate -m media_id -d 0 command.
This command expires those copies of images that reside on the tape and de-assigns
the tape. Trying to delete an assigned volume will result in the error message: “Cannot
delete assigned volume”. Some of the reasons you may want to delete a volume are:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Note: Deleting a volume removes it’s entry from the NBDB so the eject operation
cannot be used to remove the volume. Either manually remove the volume from the
robot or eject the volume using the eject operation before deleting the volume from
NetBackup’s NBDB database.
9-42
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
bplabel
bplabel –erase –l
bplabel -erase Quick erase: Overwrite beginning of tape.
EOM
EOM
EOF
EOF
MH
BH
BH
Image1 Image2
43
There are various methods available to erase physical data on a tape in NetBackup. Note
that if a tape is assigned (contains unexpired backup images), NetBackup will not allow
you to erase the tape. You will need to wait until the images expire, or to manually
expire those images with the bpexpdate –m media_id -d 0 command. For
comparison, the slide uses an illustration of a tape with previously written data. The
data is shown faded because the images are expired in the NetBackup catalog. Although
the data physically exists on the tape, NetBackup considers this an unassigned tape.
• Label writes a new NetBackup media header label on the tape. The command is:
bplabel -m media_id -d density.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Long erase rewinds the media and the data is overwritten with a known data
pattern. This is sometimes known as a SCSI long erase, or secure erase. A long erase
is a time-consuming operation and can take as long as two to three hours. The
command is: bplabel –erase –l -m media_id -d density.
• Quick erase rewinds the media and an erase gap is recorded on the media. The
format of this gap is drive dependent, and may be an EOM mark or a pattern the
drive does not recognize. The command is: bplabel –erase -m media_id
-d density.
9-43
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:
9-44
to write a tape with incompatible block sizes. Media cataloged in the EMM database
shows UNRESTRICTED_SHARING_GROUP in the Server Group column within the
media records.
• Media Sharing Groups are an alternative unrestrictive sharing, instead using server
groups to allow logically (and physically) related groups of servers to share and own
media. By creating server groups, you gain more granular control over which media
servers can write to media. After server groups are configured, you configure a
policy to use a specific group of servers media sharing server group. The media
written by such policies is owned by the group instead of the individual media server
so any of the servers in that server group can write future backup and duplication
jobs to the media.
9-45
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 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
level matches that of the images that are already on the tape. Note that you can
override this with the media server host property > Media > Allow multiple
retentions per media, however Veritas does not recommend using this setting
without understanding the implications of mixed retention images on media. Next, a
volume will be selected that is owned by the media server. By default media servers
own any tapes they have previously written to, however you can override this with
the master server host property > Enable unrestricted media sharing for all media
servers, or with server media Server Groups.
9-46
When choosing an active or available tape, if multiple candidates exist, the tape with
the least recent mount time is chosen. If no volumes are available, the backup job fails,
and NetBackup flags an error 96 for the backup status. The NetBackup administrator can
disable or manually configure media ownership.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-47
After completing this topic, you will be able to identify tape device and
media reports.
48
9-48
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.
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
happen to a tape left inside your car on a hot summer afternoon. To help circumvent
potential physical media issues, it is recommended that you make multiple copies of all
crucial backup images using duplication, inline copies, or vaulting.
9-49
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.
9-50
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.
9-51
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.
9-52
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.
9-53
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.
9-54
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.
9-55
A. FROZEN
B. SUSPENDED
C. FULL
D. EMPTY
55
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-56
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).
56
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-57
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.
57
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-58
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.
9-59
59
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-60
60
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
9-61
End of presentation
9-62
© 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 Machine Backups lesson in the Veritas NetBackup 8.1.2:
Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-1
10-2
Topic Objective
Introduction to virtual machine Describe virtual machines and discuss support for virtual machines
backups in VMware.
Protecting VMware Assets using the Understand protection plans and use them to protect VM’s and VM
web UI groups.
Performing and monitoring VMware
Monitor VMware backup.
backups
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
X-3
After completing this topic, you will be able to describe virtual machines
and discuss support for virtual machines in VMware.
10-4
• 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.
VMs consist of a number of files, including the critical virtual hard disk file (VMDK in
VMware, and VHD or VHDX in Hyper-V), which contains the operating system and data
for that VM. Traditionally, backing up the virtual hard disk file enables you to easily
restore the VM but does not provide the ability to perform individual file restores.
Conversely, backing up files from the VM as a normal client prevents easily restoring the
full virtual hard drives in the case of disaster recovery. NetBackup provides the ability to
easily back up and restore the virtual hard disk, while alternatively allowing for granular,
individual file restore. Review support details in document NB_70_80_VE: Support for
NetBackup in virtual environments at:
https://www.veritas.com/content/support/en_US/doc/NB_70_80_VE.
10-5
Modern CPUs have features built-in for system protection. These protections keep
different programs from writing into each others’ memory regions. CPUs also have
privileged instructions: Instructions only executable by the operating system. The
structure of virtualization is to allow multiple operating systems to run on the same set
of CPUs. In order to allow multiple operating systems to run, the virtualization
mechanism has to properly handle privileged instruction execution.
There are different methods virtualization systems use to handle privileged instructions.
VMware and Hyper-V use virtualization features of the CPU: Intel VT and AMD-V. The
hypervisor signals the CPU that certain processes are virtual machines, and allows the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-6
VMware vSphere ✓ ✓ ✓ ✓ ✓
Microsoft Hyper-V ✓ ✓ ✓ ✓
RedHat Enterprise
Virtualization ✓
Citrix XenServer ✓
Solaris zones ✓
Oracle Solaris
virtualization ✓
10-7
Hypervisor
control system
SAN
Control API
CLI
Web Interface
Storage
Cloud
orchestration
Virtualization
Web Client
Veritas uses the capabilities provided by the hypervisor supplier to develop VM-specific
backup solutions. There are limitations and requirements, based on the software and
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
10-8
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
10-9
10-9
After completing this topic, you will be able to configure VMware backups.
10-10
11
The slide lists VMware components and components used by NetBackup when backing
up VMware. The first four components list VMware servers and components, and the
bottom four components list NetBackup components. The VMware vCenter server is
not required for NetBackup to perform VMware virtual machine backups; however,
certain features may not be available or alternate configurations may need to be used.
The VMware backup host has certain operating system restrictions. These are discussed
on the following slide.
Note: The VMware backup host was referred to as the VMware backup proxy server in
some prior releases.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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:
10-11
NetBackup
client
Datastore
(VMDK files)
Review the latest NetBackup for VMware documentation, for the latest information.
Note: For more efficient backups, Veritas recommends using the NetBackup media
server to back up a VMware-based VM as the VMware backup host.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
There are a number of mechanisms that a backup host can use to access the data of a
virtual machine that is being protected. Although the slide shows two, here is a
summary of the types of access mechanisms that are available:
• Local area network (LAN) access to datastore, where the backup host accesses the
VMware datastore using the ESX servers, and the datastore data travels over the
TCP/IP network. In VMware this is referred to as NBD (network block device) or
NBDSSL (encrypted).
• Storage area network (SAN) access to datastore, where the backup host accesses
the VMware datastore directly over the SAN, normally with improved performance
and less impact on the ESX servers.
10-12
For more information about identifying VDDK/NBU mapping and understand backup
host limitations, refer to Article 000010289: How to Identify vStorage/vADP
Environment Support at: http://www.veritas.com/docs/100003956.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-13
14
The process within NetBackup for VMware-based backups follows these general steps:
1. The NetBackup master server starts the backup and initiates a VMware snapshot by
communicating with the VMware server. Note that in VMware, the snapshot causes
the original VM image – represented on the slide as VMDK – to become static. A new
VM image file – represented on the slide as VMDK.1 – continues to record new
data.
2. The VMware backup host (in many cases the Windows media server) reads the
static VMDK files (represented on the slide as VMDK), maps their contents using the
vStorage APIs to index individual files and ensure only used space is being written,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-14
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.
issues like crash-consistent backups may occur. Additionally, NetBackup integrates with
VMware components such as vCenter and vSphere, as is discussed elsewhere in this
course.
NetBackup configuration: The NetBackup configuration steps shown on the slide are
discussed in more details in the following slides in this lesson.
10-15
• Review tips in Veritas NetBackup for VMware Administrator’s Guide: NetBackup for
VMware best practices
• Best practices may include:
– Upgrade to the latest version of VMware vSphere or Virtual Infrastructure.
– Use the same VM name for both host name and display name.
If the policy’s Primary VM identifier option is changed, the existing entries under the policy’s Clients tab are still
valid.
– Add additional VMware backup hosts for scalability.
– Use VMware resource limits
For example, allow less than 4 concurrent backup jobs / snapshots per datastore.
– Attempt to use a single backup policy per datastore.
16
Before configuring NetBackup, Veritas recommends that you configure or modify the
VMware environment. Before configuring the NetBackup for your VMware
environment, Veritas recommends reviewing the Veritas NetBackup for VMware
Administrator’s Guide in the NetBackup for VMware best practices section. Some
VMware best practices are given on the slide. Note that NetBackup does not require any
modifications to existing vSphere environments.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-16
17
1. Add Enterprise Client licenses. A NetBackup Enterprise Client license is required for
each ESX Server, and NetBackup application or database licenses are required for
each ESX server hosting the application or database. For details, refer to NetBackup
for VMware Administrator’s Guide: NetBackup for VMware license requirement and
contact your Veritas Sales representative to ensure all information is up-to-date.
2. Install the NetBackup client on the VMware backup host. The VMware backup host
requires the NetBackup client software. For details refer to both the NetBackup for
VMware Administrator’s Guide and the NetBackup for VMware best practices. Some
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
recommendations include:
• For a more efficient backup, install the NetBackup media server and the VMware
backup host on the same host.
• Ensure that the VMware backup host has enough memory to handle the number
of simultaneous backups that occur. Monitor active memory usage on the
backup host during backups and add memory, if needed.
• Add additional backup hosts to increase backup throughput, when needed.
10-17
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
any available media server. If this option is used, make sure that all media servers in the
storage unit referenced by this policy are valid VMware backup hosts.
10-18
19
Optionally, set limits on the use of VMware resources by navigating to the Resource
Limit tab of the master server’s Host Properties. Click in the Resource Limit column to
set the maximum NetBackup usage for the resource type. The settings apply to all
VMware policies that use a VMware Intelligent Policy query to select clients. VMware
Intelligent Policy queries are discussed elsewhere in this lesson.
The default for all resource limits, indicated in the NetBackup Administration Console by
a blank value in the Resource Limit column, is unlimited. The screen shot shows a
maximum of four simultaneous backup jobs to any ESX server at a given time. For
details on resource limit types and behavior, see the NetBackup for VMware
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Administrator’s Guide: Setting global limits on the use of VMware resources. Note that
you may want to adjust or tune the resource limits according to the transport mode you
select.
10-19
4
Add VMware credentials
to NetBackup
vCenter server or
ESX server
20
a. Expand Media and Device Management > Credentials > Virtual Machine
Servers.
b. Select Actions > New > New Virtual Machine Server.
c. In the Add Virtual Machine Server dialog box, enter the name of a virtual
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-20
10-21
5
Use the VMware
policy type
22
5. To create a backup policy, use either the Policy Configuration Wizard or the Policies
utility in the NetBackup Administration Console. The VMware policy type was
introduced in NetBackup 7.5. When it is selected, a new VMware tab is displayed in
the policy configuration dialog. This tab contains VMware-specific parameters.
Veritas recommends using the VMware policy type. This policy type is discussed in
this lesson.
Note: Prior to NetBackup 7.5, the FlashBackup-Windows policy type was used to
back up virtual machines. Veritas does not recommend using this policy type to back
up virtual machines unless it is required, because this policy type does not support
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-22
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.
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 at:
https://www.veritas.com/content/support/en_US/doc/NB_70_80_VE.
Additionally, block-level incremental backups (BLIB) are enabled using the Enable block-
level incremental backup option. This improves performance further by backing up data
at a block-level, instead of at a file-level. This functionality requires ESX server 4.0 and
later, and virtual machines with hardware version vmx-07 or later.
10-23
24
When assigning clients for a VMware policy, you can select whether to select clients
manually or to have them automatically selected using a query that you construct. To
manually specify clients, navigate to the Clients tab, select Select Manually, and click
New. The Browse for Virtual Machines dialog box is displayed. Select Browse and
Select Virtual Machines to see a drop down hierarchy of virtual machines. Select the
virtual machine or machines you are interested in protecting.
Note: If your VMware environment contains many VMware servers and virtual
machines, it may take too long to search and list all of them. To limit the VMware
servers that are browsed, follow the directions provided in the NetBackup for VMware
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Administrator’s Guide under the section titled: Limiting the VMware servers that
NetBackup searches when browsing for virtual machines.
Note that a policy where virtual machines are manually selected does not work with the
VMware virtual machine limits specified in the master server host properties.
10-24
Example queries:
• Back up all VMs in Power On state
• Back up all VMs where the OS type is Windows 2012
• Back up all VMs where the display name starts with “Vmprod”
• Back up all VMs in the Dev folder that belong to cluster Cluster03
• Back up all VMs in Power On state in datastore Storage 1 where
the OS type is RedHat Linux
25
Starting with NetBackup 7.1, VMware-based policies allow for automatic virtual
machine selection. Queries are built around virtual machine attributes to determine
which virtual machines to back up. These queries can be combined with filters to create
more complex queries and limit the results. If you want to use the new intelligent policy
functionality instead of performing a manual configuration, set the Virtual machine
selection to Select automatically through query. Next, set the VMware discovery host.
Although this does not need to be the same as the VMware backup host, in many
environments this may be the same server. The VMware discovery host has the same
requirements as a backup host: be a supported operating system and have NetBackup
software installed.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
In this query builder, you build the virtual machine selection query. If you do not select
any query filters, the default behavior is to discover all virtual machines, and back them
all up. The slide shows some examples of possible virtual machine selection queries.
Some examples show queries that use multiple query filters that are combined to
narrow the resulting virtual machines.
10-25
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
After choosing the query criteria for a specific query filter, the Browse function retrieves
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
all possible values from the VMware configuration. Depending on the size of the
environment, this can take some time. You can then select from the results and they are
added automatically to the Value(s) field. The slide shows examples for the variables
that make up the selection queries, including the Join, Field, and Operator fields. The
buttons on the right help select values and form complex queries:
• The Browse button is used to discover available values based on the fields and the
available VMware resources.
• The Add button is used to add this filter to the query.
• The Clear button clears these fields, enabling you to start again.
10-26
27
VMware Tag operations require vCenter Server 6.0 or later. The NetBackup master
server and all discovery hosts must be at NetBackup 7.7.1 or later. When using media
server load balancing, all media servers that are associated with the storage unit group
must be at 7.7.1 or later. Any Windows host with only the NetBackup client software
installed, that is also defined in the VMware policy's Client tab as the NetBackup host to
perform automatic virtual machine selection, must have NetBackup Java installed.
Install the NetBackup Remote Administration Console to install NetBackup Java. If the
tag field is not required to satisfy the query, tags will not be collected and backed up. In
such a case, the tags will not be restored in a successful restore.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-27
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.
10-28
29
When your query is formed, there is a Test Query button to execute and test the query.
After the test returns, the Test Query Results display every virtual machine found, and
identify whether the current filter value results in the virtual machine being included or
excluded. If the query is not working as desired in providing the correct virtual machines
for the policy, the query can be modified and retested.
In an environment with large numbers of virtual machines, a query can take many
minutes. During that duration, the console cannot be closed or used to monitor other
operations. A command line utility, nbdiscover (found in the NetBackup bin
directory) can be used to check the search terms of a query outside of using the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 the Veritas NetBackup for VMware Administrator’s Guide - the
Query format and examples for searching virtual machine backups section.
10-29
30
The Reuse VM selection query results parameter enables the administrator to control
the virtual center interaction by specifying how old the query results need to be, before
NetBackup queries the virtual center server for virtual machine discovery information
again. This parameter does not have any effect on backup scheduling. Similarly, backup
job scheduling does not affect when virtual machine discovery takes place. In the
example on the slide, discovery queries the virtual center every 8 hours, regardless of
when jobs are scheduled. When the policy is scheduled to run, the virtual machines that
were discovered last are used. When a query or policy property that affects discovery is
modified, the Reuse VM selection query results time value is ignored, and a new virtual
machine discovery takes place.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-30
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 on the slide:
In either case, the policy backs up all local drives from each listed virtual machine. To
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
exclude certain drive types, such as swap, boot, or data drives, use the Virtual disk
selection setting under the VMware Advanced Attributes setting. This setting is
discussed elsewhere in this lesson.
10-31
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.
10-32
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.
10-33
34
This Primary VM identifier specifies how NetBackup recognizes VM names, for backup:
• VM hostname: This is the network host name for the virtual machine. This option is
the default. This option requires running and functioning VMware Tools in the VM.
• VM display name: This is the name of the VM as displayed in the VMware interface.
Character restrictions apply; Refer to the NetBackup for VMware Administrator’s
Guide.
• VM BIOS UUID: This is the ID assigned to the VM when it is created. This ID may or
may not be unique, depending on whether the VM has been duplicated.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• VM DNS Name: This is the virtual machine’s VMware DNS name. In the vSphere
Client, this appears under the virtual machine's Summary tab. This option requires
VMware Tools running in the VM as well as a properly configured DNS configuration.
• VM Instance UUID: This is the globally unique ID assigned to the VM when it is
created, even if the VM has been duplicated. The option requires backup hosts
running NetBackup 7.5 or later, and is not available in some legacy VMware releases.
Virtual machine names must be uniquely identified in a master server’s backup policies.
Additionally, the virtual machine may not be browseable under certain conditions, such
as when using the hostname as the identifier and the virtual machine is powered off, or
when the virtual machine does not have an IP address.
10-34
35
The following options set the type and scope of the VMware virtual machine backup:
• Enable file recovery from VM backup: This option enables restores of individual
files from the backup. Additionally, it provides the best deduplication rates with
NetBackup deduplication. With or without this option, you can restore the entire
VM.
• Enable block-level incremental backup: Block-level backups (BLIB) reduce the size
of full and incremental backups by tracking and only backing up the blocks that have
changed since the last backup. BLIB works with VMware’s Changed Block Tracking
(CBT) in vSphere to track the block-level changes, and requires ESX server 4.0 and
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-35
To back up a VM that contains Veritas Storage Foundation volumes, disable the Enable
file recovery from VM and Exclude deleted blocks backup options.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-36
37
• Enable Exchange Recovery: This option enables recovery of the Exchange databases
or mailbox messages from the virtual machine backups. If this option is disabled,
you can recover the entire virtual machine from the backup, but you cannot recover
the databases or mailbox messages individually. When using the Enable Exchange
Recovery option:
10-37
10-37
When you enable one or more of these Application Protection options, the backup job
automatically initiates an Application State Capture (ASC) job for each virtual machine
listed in the policy. These ASC jobs help determine if the applications are running in
those virtual machines. Because these ASC jobs require additional overhead, it is not
recommended to simply enable these options for policies that back up all VMs. Instead,
create a new VMware policy specifically for those virtual machines that are running
these applications, and enable the Application Protection option for that policy.
This is covered in greater detail in the NetBackup Advanced Administration course.
10-38
Datastore Datastore
HOTADD
LAN
Media ESX
server server
SAN
Backup
host
Datastore
Article 100030882: VMware Transport Modes: Best practices and troubleshooting
39
The transport modes determine how the snapshot data travels from the VMware
datastore to the VMware backup host. The appropriate mode depends on your
environment. By default, all modes are selected. NetBackup tries each transport mode
in order, from top to bottom. It uses the first mode that succeeds for all disks in the VM.
The following transport modes are available:
• san: For unencrypted transfer over Fibre Channel (SAN) or iSCSI. Note: This mode is
not supported for VMs that use VMware Virtual Volumes (VVols).
• hotadd: Lets you run the VMware backup host in a virtual machine. This feature
requires ESX 3.5 Update2 or later. Note: For virtual machines that use VVols, they
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 at: http://www.veritas.com/docs/100030882.
10-39
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
included in the backup. This option can reduce the size of the backup, but should be
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
used with care., and is only intended for VMs that have multiple virtual disks.
• Ignore diskless VMs: This option directs NetBackup not to back up any VM that has
no VMDK file assigned to it; for example, a replicated virtual machine in passive
mode in a VMware vCenter Site Recovery Manager (SRM) environment.
• Post events to vCenter: This option enables NetBackup to send backup-related
events to the vCenter server. More information is available on how to view the
events in the NetBackup for VMware Administrator’s Guide.
• VMware server list: Specifies a colon (:) delimited list of VMware servers that
NetBackup communicates with for this policy. VM queries will only go to these
servers, which helps improve performance in large virtual environments.
10-40
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. The available options include:
• No disks excluded backs up all VM disks configured for the virtual machine.
• Exclude boot disk excludes only the boot disk (for example the C drive).
• Exclude all data disks includes only the boot disk and excludes all data disks.
• Perform custom attribute based exclusion excludes disks based on VMware custom
attributes. If you select this option, you must also enter the name of the Custom
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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, none of the
disks are excluded. If disks are removed from the custom value between the
differential backups then only those files that changed since the last backup are
available to restore individually. If disks are added to the custom attribute value
between the differential backups then those disks are excluded from the next
backup.
10-41
10-42
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 disks to which you want to apply the Custom Attribute. If a disk is
excluded already, a warning icon appears in the Exclude disk column.
From the Review Selections screen, select the virtual machine then select Set
Exclusions. The list box shows the results of the operation. These disks will be excluded
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
each time this Custom Attribute matches the Custom Attribute and virtual hostname in
a backup policy.
10-43
• 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.
• 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.
10-44
10-44
After completing his topic, you will be understand protection plans and use
them to protect VM’s and VM groups.
10-45
Note: Before you create a protection plan, you must configure all storage options in the NetBackup Administration Console.
46
A protection plan defines when backups are performed, how long the backups are
retained, and the type of storage to use. Once you have set up a protection plan, you
can subscribe assets to that protection plan. Before you create a protection plan, you
must configure all storage options in the NetBackup Administration Console.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-46
1 2 3
47
1. On the left pane, click VMware and then click the Servers tab. The tab shows the
vCenters and ESXi servers that you can access.
2. Click Add to add a server. Select the server type, and enter its host name and
credentials. Note: The NetBackup web UI does not validate the server's host name
or credentials. If the server name or credentials are not correct, the web UI cannot
perform the operations that require access to the server.
3. Click Save.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Note: The discovery of VMs and other objects in the vCenter or ESXi server occurs at set
intervals according to the VMWARE_AUTODISCOVERY_INTERVAL option (the default is 8
hours). Depending on that interval, the server's VMs and other objects may not appear
immediately after the server is added. To discover the VMs and other objects
immediately, restart the NetBackup discovery service.
10-47
Protection status
48
You can view the current protection plans that VMs or VM groups are subscribed to. To
view the protection status of VMs or VM groups:
If the asset is not currently protected, the screen displays that, and you can click
Configure protection to subscribe it to a plan.
10-48
49
You can create an intelligent VM group based on a set of filters called queries.
NetBackup automatically selects virtual machines based on the queries and adds them
to the group. You can then apply protection to the group. Note that an intelligent group
automatically reflects changes in the VM environment and eliminates the need to
manually revise the list of VMs in the group. To create an intelligent VM group:
10-49
Note: When you click Preview or save the group, the query options are treated as case-
sensitive when the VMs are selected for the group. Under Virtual machines, if you click
on a VM that was not selected for the group, the Member of virtual machine groups
field reads none. However, when you add the group to a protection plan, some of the
query options are treated as case-insensitive when the protection plan’s backup runs.
As a result, the same VM may now be included in the group and is backed up.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-50
cluster
datacenter
datastore
displayName Ends with Value for the
host Contains selected condition
tag = (Plain text only)
dnsName !=
hostname
instanceUuid
51
Keyword Description
10-51
Operator Description
10-52
1 3
53
When you subscribe an asset (VMs or intelligent VM groups) to a protection plan, you
assign predefined backup settings to the asset. The following are the requirements for
protecting VM’s or VM intelligent groups:
• You must have access to the VMs by means of the appropriate role-based access
control (RBAC) that the NetBackup security administrator assigned to you.
• You must have access to the protection plans that the backup administrator has
granted you access to (by means of RBAC).
• The appropriate services on the master server must be running and the web UI must
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
be accessible.
10-53
5. To subscribe the VM or VM group to the selected plan, click Protect. The results of
your choices are displayed under Virtual machines or Intelligent VM groups.
10-53
After completing his topic, you will be able to monitor VMware backup.
10-54
• 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.
55
When using automatic VMware client selection, client discovery is required when the
backup runs. An initial parent job runs the client discovery, displaying 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.
10-55
56
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:
3. Select the object (such as datacenter, host, or virtual machine) and select the Tasks
& Events tab.
4. Select the Events view.
10-56
57
Traditionally, virtual machine snapshots do not quiesce Linux virtual machines and the
backup uses snapshots that are crash consistent. The term Crash consistent denotes
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.
For any Linux VMs that were backed up while they were running. Use a file system
check (fsck) after restoring data to ensure data consistency after a restore,
10-57
• 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
58
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.
10-58
59
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.
10-59
59
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.
10-60
A. vCenter server
B. Datastore
C. vStorage API
D. VMware tools
60
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-61
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.
61
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-62
A. Windows 2008
B. SUSE Linux 11
C. Solaris 11
D. RedHat Linux 6
62
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-63
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.
63
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-64
A. Oracle
B. Microsoft Exchange
C. Microsoft SharePoint
D. Microsoft SQL
64
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-65
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.
65
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
10-66
End of presentation
10-67
© 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 Machine Restores lesson in the Veritas NetBackup 8.1.2:
Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-1
11-2
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.
11-3
After completing this topic, you will be able to describe virtual machine
restore concepts.
11-4
VMware ✓ ✓ ✓ ✓
Microsoft Hyper-V ✓ ✓ ✓
RedHat Enterprise
Virtualization (RHEV) ✓
Citrix XenServer ✓
Solaris zones ✓
Oracle Solaris
virtualization ✓
11-5
LAN
SAN VM VM
Master Media
server server server storage
11-6
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 which enables individual file restores. This feature is both time
efficient in allowing for a single-pass backup, and space efficient in requiring only one
copy of the backup for both full VM recovery and individual file recovery. Recovery of
individual files must be performed to a host running the NetBackup client software. If
the virtual machines in your environment are not running NetBackup client software,
you will need to stage the recovery. Some customers have NetBackup clients (physical
or virtual) dedicated to this purpose. Recovering individual files must be performed over
a local area network (LAN).
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-7
After completing this topic, you will be able to run VMware restores using
the Backup, Archive, and Restore console.
11-8
To restore a virtual machine, launch the Backup, Archive, and Restore console. This can
be launched on the master server or on the virtual machine backup host that is
configured to communicate with, and take the data stream from, the ESX server.
1. Set the source and destination clients. From the File menu, select Specify
NetBackup Machines and Policy Type.
2. Set the Source client for restores (or virtual client for backups) as the virtual
machine you wish to restore. Type in the client’s name, or use the Search VM
Clients button.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
3. Select the Destination client for restores and the Policy type for restores. Ensure
that you select the correct policy type:
11-9
10
Clicking the Search VM Clients button in the Specify NetBackup Machines and Policy
Type dialog box, displays 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-10
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.
11-11
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 the NetBackup client to
be installed on that VM. Alternatively, you can restore to a shared folder that can be
accessed by the virtual machine client.
To restore directly to a virtual machine, the ESX server name that is specified for the
restore must match the ESX server’s official hostname. The name must be in the same
format in which it is registered in the 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
through a vCenter server. Note that you can restore Windows files to a Windows guest
operating systems, but not to Linux. Similarly you can restore Linux files to supported
Linux guest operating systems but not to Windows. If a Linux file system was not
quiesced before the snapshot, some files may be inconsistent. This issue is discussed
elsewhere in this lesson.
11-12
13
The Restore type - 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 - Virtual Machine Backup, clicking the Restore button starts the Virtual
Machine Recovery Wizard. The following slides explore this wizard.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-13
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.
11-14
15
• Select the NetBackup Recovery Host, which is the NetBackup client used to send
the data to the ESX server’s datastore. Typically, this is a NetBackup media server
(often the same media server that performed the backup).
• Select the Transport modes, and then use the Move Up and Move Down buttons to
decide which transfer types are prioritized:
• san: For unencrypted transfer over fibre channel (SAN) or iSCSI.
• nbd: For unencrypted transfer over a local network that uses the Network Block
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-15
16
On the Virtual Machine Options screen, select any of the applicable virtual machine
restore options:
• Restore UUID
• Overwrite the existing virtual machine
• Remove backing information for devices
• Remove network interfaces
• Power on virtual machine after recovery
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Also, select any virtual disk format options. Note that thin provisioning can impact
performance as new blocks are constantly being allocated. For more information about
disk provisioning, see the article: About Virtual Disk Provisioning Policies at:
https://pubs.vmware.com/vsphere-
50/topic/com.vmware.vsphere.storage.doc_50/
GUID-4C0F4D73-82F2-4B81-8AA7-1DD752A8A5AC.html
11-16
17
1. Before starting the restore, click Run Pre-Recovery Check to perform the pre-
recovery check. This improves your restore success rate and prevents wasted time
by identifying problems that may cause the restore to fail, such as low disk space or
incorrect permissions. Note that the pre-recovery check on the slide shows a
datastore space failure, which may cause a problem if a full VM recovery is
performed.
2. After the pre-recovery check is successful, click Start Recovery to initiate the
restore.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
To monitor the restore, click View Status from the Backup, Archive, and Restore
interface or use the Activity Monitor in the NetBackup Administration Console.
11-17
18
The Restore type - Virtual Disk Restore option is used to restore individual VMWare
virtual machine disks to the following destinations:
• Original virtual machine: Either overwrite the original disks or attach virtual disks
without overwriting them. NetBackup creates a temporary VM to which the virtual
disks are restored to, attaches the virtual disks to the existing target VM, and finally
deletes the temporary VM after the disks are attached successfully.
• Alternate virtual machine: NetBackup creates a temporary VM to which it restores
the virtual disks, then attaches the virtual disks to the existing target VM, and finally
deletes the temporary VM after the disks are attached successfully.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• New virtual machine: NetBackup creates a new virtual machine and restores the
specified disks to the new VM. After the restore, the restored disks should be
attached to a VM that can support them and then delete the restore VM.
Note: If the recovery host is running a version prior to NetBackup 8.1, the original and
different VM restore destinations are not supported.
To recover a virtual machine disk, select the virtual machine. If you are restoring from
physical tape, click the Preview button to see which tapes are needed for the restore.
When ready, click the Restore button. After selecting the Restore type - Virtual Disk
Restore, clicking the Restore button starts the Restore Virtual Machine Disks Wizard.
The following slides explore this wizard.
11-18
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 the time of backup, 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 disks you wish to restore, then click
Next.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-19
20
Select where you want to recover the virtual disks 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.
11-20
21
Virtual Disk Destination details are displayed. All the options are grayed-out since the
Original Virtual Machine was selected as the recovery destination. If Alternate was
selected, you would have the 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.
11-21
22
When you opt to recover the virtual disks to a New (temporary) virtual machine you
can set the parameters displayed on this screen.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-22
• Original
• Thick Lazy Zeroed
• Thick Eager Zeroed
• Thin
• Custom
• No
• Yes
• Custom
23
The Storage Destination screen shows the settings for all the virtual disks. Notice that
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.
11-23
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.
11-24
25
VMware Virtual machines 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:
Additional caveats and notes are listed on the slide. Refer to the NetBackup for VMware
Administrator’s Guide for additional details.
11-25
After completing this topic, you will be able to run VMware restores with
Instant Recovery.
26
11-26
27
Instant recovery for VMware (IRV) is a capability that allows VMware infrastructure to
use the NetBackup backup location as a data store. No data transfer from NetBackup to
ESX or vCenter is done. The virtual machine can start up and begin processing data
almost immediately. In normal mode, the virtual machine will be migrated to a
production data store. Using VMware storage vMotion migration can be accomplished
while the virtual machine is running. Possible uses for IRV include:
• Access and restore files and folders, and then delete the virtual machine.
• Test a patch on a restored VM before applying the patch to production systems.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Start a VM from its backup and use it until the production ESX server is back online.
• Permanently recover the virtual machine by means of Storage vMotion.
• Verify a backup image, or verify an application.
It is not recommended to use instant recovery for VMware for long term production use
or as a disaster recovery method. Additionally, in the case where hundreds of virtual
machines may need to be started, the I/O load and network traffic would be too much
for the media server to handle efficiently.
11-27
LAN
vCenter
SAN ESX server
Master Media Datastore
server server servers (VMDK files)
28
11-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 placed 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.
11-29
• 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 and its effective operation is essential
for success. Overloading the backup system with IRV operations may prove counter-
productive. The number to restore depends on the I/O load on the media server.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-30
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 a 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.
11-31
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 has higher performance than an NFS datastore exported
from a NetBackup media server. The NFS datastore is unmounted when it is no longer
needed.
Note that the slide illustrates the process assuming that the NetBackup media server is
also the VMware restore host. In the case where the media server and restore host do
not reside on the same server, each is responsible for different behaviors during this
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
process:
1. NBFSD on the media server handles the export phase of NFS in 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 for IRV.
3. bpVMutil on the restore host handles the VM activation.
11-32
33
Instant Recovery for VMware requires network file system operations on the media
server and any restore host.
• The target ESX server for the restore must be vSphere 5.0 or later.
• The client for NFS service must be operational on the NetBackup restore host.
• The media server must use IPv4.
• There must 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.
11-33
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:
11-34
The VMware vSphere Client (not the vSphere Web Client) resource map shows the
resources and the connections. It displays 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.
11-35
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.
11-36
Recovery
Workflow
37
backups.
• Register Master Servers is used to register NetBackup master servers with the
vSphere plug-in. This is a pre-requisite for using either of the recovery wizards.
• Settings is used to configure recovery wizard settings.
11-37
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, and 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 will need to transport it over to the vCenter
machine using a shared drive. You then upload it into the vSphere Web Client to permit
the vSphere NetBackup Web Client to communicate securely with the NetBackup
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Master.
11-38
39
The settings window allows you modify the settings that the recovery wizards uses.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-39
40
The Instant Recovery Wizard provides a graphical interface that allows you to instantly
recover VM’s from the VMware vSphere Web Client. The Instant Recovery Wizard
provides five steps to determine important aspects of how a recovery is going to be
carried out. You can see the similarity between these steps and the steps used in Instant
Recovery from the command line using nbrestorevm on the NetBackup master
server.
You can select which vCenter Server and which NetBackup master server to query and
then search for a machine using its display name, UUID, DNS name, or hostname. There
are some wildcard searches available in the selection box. From the Search Results,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
select the virtual machines on which you wish to perform Instant Recovery and click
Add Virtual Machines.
11-40
41
After clicking Add Virtual Machines, the number of VMs selected is shown at the top of
the screen. Click Next to continue.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-41
42
Use the Change link to select the specific image you wish to use as the source for the
Instant Recovery. The slide 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.
11-42
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. In some
cases, only a subset of the recovery is required.
Alternate Data Center selection and resource pool provides greater flexibility in recovery
operations. The recovery could be part of a non-production exercise and it would be
contrary to the enterprise data center policy to have non-production virtual machines
running in a particular VMware Data Center.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-43
44
The display name of the virtual machine can be changed during recovery specification.
In many cases, there will need to be a distinction between a Virtual Machine started for
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-44
45
The recovery settings are displayed on the slide. 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 and potential problems of the
recovery are uncovered. As virtual machines in real world production can span multiple
terabytes, discovery of problems early in the process is highly desirable.
At this point, all resource checks have returned successful and the restore is ready to
start. Click the Finish button to exit the wizard and recover the VM. The virtual machine
will be powered on from the backup storage and is available for use when the Activate
Instant Recovery job in the NetBackup Activity Monitor completes. Note that the VM
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Instant Recovery job will remain in the Active state until it is deactivated by running the
Instant Recovery Cleanup wizard.
11-45
46
The progress and status of the instant recovery job is reported in the Activity Monitor.
The Detailed Status pane includes the key details about 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 in the following slides. The VMware identifier is used as a
parameter for some nbrestorevm commands. It is distinct from the NetBackup Job
ID.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-46
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 is
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.
11-47
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.
11-48
49
The Instant Recovery Cleanup screen has three options that can be select for a
recovered VM:
• Instant Recovery Done: Use this option to complete the instant recovery operation
after you have performed the Storage vMotion of the virtual machines to a different
datastore. This utility completes the virtual machine instant recovery operation after
the vMotion migration of the virtual machine is completed. When the datastore is
removed, its resources are released on the NetBackup media server.
• Deactivate: Use this option when you are done with the restore and do not intend
to retain the restored virtual machine. This action removes the virtual machine from
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 option when connection to the virtual machine was
interrupted. The interruption may occur due to a network disconnect between the
NetBackup media and the ESX server. This utility reactivates a restored virtual
machine by remounting the NetBackup datastore. It also registers the restored
virtual machines on the ESX host.
11-49
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.
11-50
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
11-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.
11-52
-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.
machine host, resource pools, and networks can be changed. An example syntax of this
file is shown on the slide. There is a specific syntax that must be followed in the rename
file.
11-53
• 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.
11-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.
11-55
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.
11-56
56
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-57
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.
57
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-58
58
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-59
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.
59
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-60
60
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-61
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
61
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
11-62
End of presentation
11-63
© 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 Using Storage Lifecycle Policies lesson in the Veritas
NetBackup 8.1.2: Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-1
12-2
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.
12-3
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.
12-4
Client data
Onsite
Backup Duplicate
Duplicating backup images allows for redundancy and for other restore requirements to
be met. There are a number of duplication strategies available.
One of the simplest and oldest strategies is to duplicate images that have already been
created. This is the traditional solution when you are faced with a tight backup window.
Backup images are created during the backup window, and the duplication is performed
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
at a later time. Because there is no impact to the clients for duplication, the duplication
was traditionally performed during business hours when the tape drives were idle. This
may be a solution if your environment has strict windows during which backups need to
complete.
12-5
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 the client to the 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 is that it requires additional resources
during backup time, and the overall backup speed is equal to that of the slowest media
to which data is being written. Also, features are restricted based on the lowest level of
the 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-6
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. In other cases,
ejecting tapes and managing tape rotation must be performed manually by the
administrator.
Traditionally, the term “vaulting” referred to the process of moving tapes offsite,
implying that the target location was similar to a protected, physical vault. In modern
parlance, “vaulting” refers to the process of getting backup images to an offsite location
that provides redundancy from primary site failure. In cases where this data is disk-
based, it normally involves sending the data through the network, and may not involve
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-7
In NetBackup, replication is copying data from one storage location to another, between
different NetBackup domains. Note that different backup and storage vendors may use
the term replication in different ways, which may or may not match the NetBackup
definition. Optimized duplication is NetBackup’s ability to take advantage of features
within the disk appliance to:
• Copy an image between appliances without sending data through a separate media
server.
• Reduce workload on the NetBackup media servers, which allows more backups to
be performed.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-8
• 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 facilitates 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.
12-9
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:
images to a disk and then later (as specified in the disk staging schedule) copy the
images to another media type. It provides little configurability, and the same backup
destination folder, schedule, and retention are used for all duplication jobs.
• NetBackup Vault provides functionality for automated duplication of backups, and
ejecting of tapes, but does not support more sophisticated features such as inter-
domain replication, third-party snapshots, or NetBackup Data Classification.
• Storage Lifecycle Policies combine duplication features in one consolidated view
that provides inline copies, immediate or scheduled duplications, intra- or inter-
domain replication, support of some third-party snapshot technologies, and support
for NetBackup’s Data Classification feature. The only limitation with SLPs is that they
do not support BasicDisk storage units. SLPs are the focus of this lesson.
12-10
2
1
bpchangeprimary
bpduplicate –npc primary_copy –backupid backup_id
11
One backup in the NetBackup catalog is assigned as the primary copy. NetBackup uses
the primary copy to satisfy restore requests from the GUI. When using the command
line, it is possible to specify the copy to use. Normally, the first backup image created
successfully for a specific backup job is the primary copy. If the primary copy expires
first, the second copy is automatically promoted to become the primary copy. If the
primary copy is unavailable and you have created a duplicate copy of that backup, select
a copy of the backup and set it to be the primary copy. Setting a backup to be the
primary copy is a function of the image catalog only; it is not a function of the media. To
promote a backup copy to a primary copy:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
1. In the object tree pane of the NetBackup Administration Console, select NetBackup
Management > Catalog.
2. Set up the search criteria for the image that you want to promote to be a primary
copy. Note: When specifying your search criteria, ensure that you indicate a copy in
the Copies field and not Primary Copy.
3. Click Search Now.
4. Right-click the image that you want to promote and select Set Primary Copy from
the shortcut menu.
12-11
12
12-12
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 can also be called SLPs,
storage lifecycles, or lifecycles.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-13
Reduced risk
• Automated duplication job restarts after failures
• Less opportunity for administrative errors
• Data does not expire until copy is successfully created
More configurability
• Additional staging locations: All except for basic disk
• Additional retentions: Fixed, capacity managed, staged, and expire after copy
14
Storage lifecycles policies (SLPs) enable you to create a storage plan for similar types of
data. After an SLP is created and configured, it can be used as often as it is needed. This
reduces administration errors. SLPs also provide a single place to view the storage plan.
Prior to SLPs, administrators needed to look in several places to view similar
information. Using an SLP guarantees that all destinations in the lifecycle are written.
The destinations are retried as necessary until the SLP is satisfied or until the backup or
duplication is cancelled by the administrator. SLP images that have not been successfully
written do not expire, even if they have passed their retention, until all destinations
have been satisfied.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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:
12-14
After completing this topic, you will be able to create and initiate a storage
lifecycle policy.
15
12-15
4
Configure any
relevant host Such as data classifications.
properties
16
The slide displays tasks that must be performed before you create storage lifecycles.
• 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.
12-16
17
12-17
18
Complete the New Storage Lifecycle Policy by specifying the following and then click
Add:
Note: The data classification of the backup policy and the storage lifecycle must
match. Storage lifecycles of different classifications are not available as backup
destinations in the policy.
The New Operation dialog box is displayed. The options available in the dialog box
depend upon the type of operation (backup, snapshot, import, duplication, and so on)
and the type of storage unit (tape or disk). Many of these operation types are
introduced in this lesson.
12-18
Disk
19
• Volume pool: Select the volume pool for the backup (tape only).
• Media Owner: If you have server groups configured for media sharing, you can
select a server group as the media owner (tape only).
• Retention Type: Select one retention type.
• Fixed: A fixed retention is the only guaranteed retention. At least one backup or
duplication in the lifecycle must have a fixed retention period.
•
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Expire after copy: Select this retention type to have this backup expire after the
duplication has finished.
• Capacity managed (AdvancedDisk only): Select this retention type to enable
NetBackup to manage the space on the disk. This retention type is used in
conjunction with data classifications. The Desired cache period is the desired
time for the backup image to remain on the disk.
12-19
20
• Source storage: Shows the storage device where the backup was sent, from which
this duplication makes its copy.
• Alternate read server: This field specifies the name of the server that is enabled to
read a backup image that was originally written by a different media server. This
option is available for Duplication operations only.
• Preserve Multiplexing: The original backup storage destination may have used
multiplexing to interleave multiple backup streams for improved backup
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
performance. If this is the case, by default a duplication does not preserve that
multiplexing, and instead copies the backup image pieces one after another to
create a complete backup image for the new backup image copy. Select this
checkbox to preserve the multiplexed image.
Note: To add a Duplication operation, a Backup operation in the Storage Lifecycle Policy
dialog box needs to be selected prior to clicking the Add button.
12-20
Customized windows
allow for start windows
and exclude dates
21
• Select from saved windows: Allows you to use an existing, defined SLP window. The
default window shown is Default_24x7_Window, which allows duplications to occur
anytime. This has the effect of duplicating a backup soon after the original backup
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
completes.
• Create new: Allows a new SLP window to be created within the New Operation
dialog box.
• Start Window: Similar to policy schedule windows, this defines the time during
which duplication jobs are allowed to start.
• Exclude Dates: Provides the capability to exclude specific days during which
duplications do not run.
12-21
22
If a hierarchical duplication destination has children, it serves as the source for the
children. Non-hierarchical duplication destinations no longer exist in current versions of
NetBackup, however earlier releases allowed you to specify a Duplication which did not
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
have a strictly defined parent. In these cases, a parent backup was chosen for you, as
any backup that is marked as the primary copy can provide the source for a non-
hierarchical duplication destination.
12-22
• SLP versions:
– Allow SLPs to be modified safely any time.
– Tagged within a running job (and viewed using nbstl command).
Already running jobs continue to use the corresponding SLP version.
– Cleaned up per SLP Parameters host properties, when no longer used.
23
This slide discusses some SLP restrictions and additional information. Inline copies is the
process of writing a backup to multiple locations simultaneously. There is a limit of four
Backup storage destinations per storage lifecycle. NetBackup will not allow you to save
the SLP if it has more than four backup storage destinations. Similarly, all backup copies
must be directed to storage units on the same media server. The storage units may be
different, as long as they are on the same media server. If a storage lifecycle has more
than one backup destination configured, the multiple copies option is no longer needed,
and is therefore disabled in the policy schedule.
The ability to create SLP versions lets administrators safely modify a definition without
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
waiting until all of the copies that are associated with the SLP have been processed.
Each copy that an SLP manages is tagged with the SLP name and the SLP version
number. These two attributes are written into the image header, in the NetBackup
image catalog. Whenever an administrator creates or changes an SLP, NetBackup
creates a new version (between 0 and n). New jobs use the most recent SLP version.
When a new job is submitted, it is tagged with the most recent SLP version number. The
processing of a copy that is associated with a version remains fixed according to that
version of the SLP definition. It is fixed at job time and does not change, unless the
administrator uses the nbstl command to modify an existing version. Old, unused SLP
versions are cleanup up according to master server host properties > SLP Parameters.
12-23
(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:
3. After the backup job completes, the SLP causes a duplication of the backup image
that resides on master_advdisk_stu. This duplicate copy is written to a Media
Manager storage unit, master_tape_stu, and has an assigned retention of 3 months.
Note: After the duplication job has run and the copy is created on tape, the source copy
for the backup, which resides on master_advdisk_stu is deleted.
12-24
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:
months.
12-25
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.
12-26
27
This slide shows a storage lifecycle policy in the NetBackup Administration Console, with
the corresponding output from the nbstl –L command. You can see from the output of
nbstl on this slide that the Backup operations have a Source listed of the client
directly. The Duplication operation’s source shows the operation from which it is to be
duplicated, based on the SLP hierarchy (in this case, Operation 1, the backup to
AdvancedDisk).
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-27
28
• Image processing interval indicates how frequently NetBackup looks for completed
backups and decides whether to start a duplication session. Default: 5 minutes.
Minimum: 1 minute.
• Extended image retry interval indicates, after the initial three retries, how long
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
NetBackup waits before an image copy is added to the next duplication job. Default:
2 hours. Minimum: 1 hour.
• Minimum size per duplication job indicates the size that the batch of images should
reach before one duplication job is run for the entire batch. The SLP only requests a
duplication job when this size is met, or until the Force interval for small job time
has passed. Default: 8 GB.
• Maximum size per duplication job determines how large the batch of images is
allowed to grow before no more images are added to the batch. Default: 100 GB.
• Force interval for small job - If the minimum batch size is not reached by the time
indicated, the SLP requests a duplication job regardless. Default: 30 minutes.
12-28
* Caution: Will prevent dependent lifecycles, which may result in loss of backup copies.
29
Use the nbstlutil command to view and manage the duplication automation in
storage lifecycles. The slide shows some of the options that can be used with this
command:
• cancel: Cancels pending lifecycle operations on selected image copies. When you
cancel a specific destination, you also cancel the pending operations at destinations
that depend on the source copy from that destination. These images will not later
be considered for duplication by the lifecycle.
• inactive: Deactivates future lifecycle operations on the image copies, but retains
the image information so that processing can resume (similar to a suspend
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
function).
• active: Activates the lifecycle operations on selected image copies (similar to a
resume function).
• list: Displays the contents of an image list from the NetBackup database
(primarily used as a debugging tool to assist in troubleshooting problems).
• stlilist: Displays the status for incomplete copies of lifecycle managed images.
• diskspaceinfo: Reports the space that is used by all disk volumes, or only the
disk volumes that are used by the specified type.
For more information on the nbstlutil command functions and options, see the
NetBackup Commands Reference Guide.
12-29
30
• SLP Status: This report provides an overall summary of the SLP status and allows you
to monitor the SLP progress by master server.
• SLP Backlog: This report illustrates what the SLP backlog looks like against the image
creation volume, including in a tabular form.
An example SLP Backlog report is shown on the slide. Backlogs occur frequently and can
be normal, however they may need to be managed to keep the SLP environment from
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
getting too far behind. In this example, the SLPs have not been processing the images;
therefore, the backlog has built up to the point where the Created Images equal the
Unfinished Images, showing that a large backlog exists.
Data for the SLP Backlog report is not real time, and is collected from the OpsCenter
database on a periodic basis. Because SLP processing generally takes hours, this typically
does not impact the report’s effectiveness. Most backlogs in a properly sized
environment are resolved eventually, so minute-by-minute monitoring is not a good
indication of general backlog issues. Consistent or growing backlog over the span of
days and weeks indicates that either too much data is in the SLP process, or that there is
not enough infrastructure to handle the amount of information.
12-30
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
This is the Additional Storage Lifecycle Policy features and benefits topic.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-31
32
The use of storage lifecycle policies (SLPs) also provide a number of other features and
benefits:
• Auto Image Replication is a function of NetBackup SLPs which allow the replication
of backup images from one NetBackup domain to another. This feature takes
advantage of optimized duplication to use minimal bandwidth. Note that different
backup and storage vendors may use the term replication in different ways, which
may or may not match the NetBackup definition.
• Data Classification is an optional ranking that can be assigned to backup data
according to its business value or importance, relative to other backup data. Data
classification is defined in the master server host properties, as well as optionally
used in a backup policy. For more details, refer to the NetBackup Administrator’s
Guide.
12-32
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 that the following
prerequisites are met:
• For most disk appliance types, the source and destination must be identical.
• For OpenStorage vendors that support optimized duplication, refer to the OST
supported vendor for their hardware and version restrictions.
• To configure optimized duplication, one or more media servers must have credentials
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
to both the source and destination storage. This could be either the source or target
MSDP storage server, or a media server that is separate from both disk storage
appliances. The role of this media server is to initiate, monitor, and then finally verify
the copy operation.
12-33
34
To use optimized duplication, simply duplicate using a supported source and target
destination, using any of these duplication methods:
Because optimized duplication is used by default when the prerequisites are met, no
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Storage lifecycle policies: In the case of SLPs, multiple optimized duplication jobs are
supported, as long as the multiple target storage locations support optimized
duplication from the source storage. A separate job is created for each of these jobs.
• Other duplication methods: With other duplication types, multiple, simultaneous
optimized duplications are not supported, and normal duplication are used for all
destinations.
12-34
35
RESUME_ORIG_DUP_ON_OPT_DUP_FAIL = TRUE
• UNIX: /usr/openv/netbackup/db/config
• Windows: install_path\NetBackup\db\config
To configure the storage lifecycle policy wait period (the default wait period between
retries is 2 hours), modify the IMAGE_EXTENDED_RETRY_PERIOD_IN_HOURS SLP
parameter in the master server host properties.
12-35
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.
duplicated to the target domain, standard duplication copies that backup image to tape.
In this way, a vaulted copy of the backup is created without having to ship tapes. Auto
Image Replication supports various disaster recovery models, including simple one-to-
one, many-to-one and one-to-many replication. Targeted Auto Image Replication allows
selective replication of images. Refer to the NetBackup Administrator’s Guide, or the
NetBackup: Advanced Administration course.
12-36
* The use of the term “domain” in this topic refers to NetBackup domains.
37
to the target domain, the target master server imports the metadata. Because the
metadata can be easily and quickly imported, this is referred to as a fast import. This
is much preferred to the traditional, much slower method of having to re-catalog the
entire backup image.
4. Optionally, additional duplication jobs can be configured. These can be duplications
to local storage, or additional replication jobs.
12-37
Storage 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.
12-38
• Key points
– You learned to identify the duplication backup types, including inline, manual duplication, basic disk
staging, and storage lifecycle policies.
– You also learned how to configuration options for storage lifecycle policies and create 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.
12-39
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.
12-40
40
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.
12-41
A. Simultaneous copy
B. Inline copy
C. Storage life backup
D. Duplication backup
41
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-42
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.
42
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-43
43
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-44
44
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-45
A. 30 seconds
B. 1 minute
C. 5 minutes
D. Immediately
45
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-46
A. 30 seconds
B. 1 minute
C. 5 minutes
D. Immediately
46
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
12-47
End of presentation
12-48
© 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.2: Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
13-1
13-2
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.
13-3
After completing this topic, you will be able to describe the location, and
explain the importance of NetBackup catalog backups.
13-4
NetBackup 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
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
13-5
Although you can recover your data without the catalogs, doing so 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:
13-6
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.
• bp.conf
VXDBMS_NB_DATA = /usr/openv/db/data
• Registry
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config\
VXDBMS_NB_DATA
For more information about the NetBackup catalogs, attend the NetBackup: Maintain
and Troubleshoot course.
13-7
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 the
following:
13-8
images
winclient.example.com Client name Each backup has a filelist (.f) file
named using policy name,
1483000000 Creation timestamp timestamp, and schedule type
clients_to_master_bdisk_1483603201_FULL.f
clients_to_master_tape_1483548217_FULL.f
A critical NetBackup component is the image database, which stores backup image
metadata. The image metadata is stored in two locations:
The image files are located in the NetBackup DB in the images directory. Under the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
images folder, there are subdirectories for each client that is backed up by NetBackup,
including the master server and any media servers, and additional subfolders named
after timestamps, as shown in the example on the slide. These folder contain the
following files:
• Image .f files are files that are used to store the detailed information about each
file backup.
• The .lck files are files used to prevent simultaneous updates on images.
• The db_marker.txt file is used to ensure that access to the db directory is valid
when the NetBackup Database Manager starts. Do not delete this file.
13-9
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
13-10
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.
13-11
Provides visibility
into the backup
image database
12
Select NetBackup Management > Catalog to search for backup images. You may want
to search for a backup image to:
• Verify the backup contents with what is recorded in the NetBackup catalog.
• Duplicate the backup image to create up to ten copies.
• Promote a copy of a backup to be the primary backup copy.
• Expire backup images.
• Import expired backup images or images from another NetBackup server.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
You learn how to perform many of these operations in this lesson. Specify the exact
search criteria that NetBackup is to use to build a list of backups from which you can
make your selections.
13-12
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.
13-13
bpverify
14
to verify and select Verify from the shortcut menu. You will see a Confirm Verify
message window, which gives you the option to log all files found in verified images.
4. Click OK to continue.
13-14
15
13-15
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:
13-16
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:
• 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
In prior versions of NetBackup that are no longer supported, there was compatibility for
reading Veritas 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 at:
http://www.veritas.com/docs/100000926.
13-17
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:
13-18
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.
13-19
bpimport
20
During Phase II, you select and import images from the list of images that were
completed in Phase I.
Note: The date range specified must encompass the date the original backup was
written, even if the image to be imported is a copy.
13-20
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.
13-21
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.
13-22
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.
13-23
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
command, to prevent jobs from starting and the database from being modified
while you are moving the image database.
4. Create the new file system, and optionally create a directory for the image files. For
example:
mkdir /newvol/netbackup/db/images
5. Move the image database to the new location in the other file system.
13-24
25
If the image database grows too large on a static Windows partition, you can move the
image database to another partition as follows:
1. Back up the NetBackup catalogs to ensure that you can recover image information in
case something is accidentally lost during the move.
2. Ensure that no backups or restores are in progress by using the Jobs tab in the
Activity Monitor. If backup or other jobs are running, either wait for them to end or
stop them by using the Jobs tab in the Activity Monitor.
3. Stop the NetBackup services, for instance by running the bpdown command, to
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
prevent jobs from starting and the database from being modified while you are
moving the image database.
4. Create the new file system and optionally any directories to which you intend to
move the image information. For example:
E:\NetBackup\alternate_db\images\client_name
5. Move all files and directories to the new location. Note that if you are planning to
use the ALTPATH method of setting an alternate location, you need to move the
image files for specific NetBackup clients into a folder for that client.
13-25
13-26
After completing this topic, you will be able to configure a catalog backup
policy.
27
13-27
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.
like normal backups, and can be run online, while NetBackup is performing other tasks
such as backups and restores. Catalog backups can run full and incremental backups,
thereby minimizing catalog backup time and space.
Catalog backup policies are slightly different from normal backups. Because NetBackup
already knows the data and clients to back up, you do not need to specify the clients or
backup selections for a catalog backup. In addition, catalog backups create a disaster
recovery file and a disaster recovery package (DR package). The disaster recovery file,
which can be automatically e-mailed to the NetBackup administrators, outlines
instructions for performing a catalog restore and identifies the required tapes. The DR
package is new to NetBackup 8.1 and later and is used to recover a master server’s
identity in the event a DR needs to be performed.
13-28
• 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
The Veritas recommended best practice is to schedule catalog backups to run regularly,
in case of failures with the master server or its catalogs and databases. Additionally, run
manual catalog backups prior to and immediately after any upgrade, including patch
upgrades. This slide describes what happens during a catalog backup. After a parent job
starts to manage the entire process, the following additional jobs run:
1. A child job copies the NBDB files to the staging location, as shown on the slide.
During each catalog backup, the files in the staging area are overwritten. Until they
are overwritten, they can be used for disaster recovery.
2. A child job starts, which backs up the files from the staging directory to the storage
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 flat file NetBackup Database (DB). This
includes the Image database, policies, configuration, and other catalogs on the
master server.
In previous versions of NetBackup, the files in the staging directory were deleted at the
end of the successful catalog backup. The NetBackup database truncates the NBDB
transaction log automatically during database checkpoints, separate from the catalog
backup schedule.
13-29
• 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.
13-30
31
During each NetBackup catalog backup, a DR package is created and encrypted with the
passphrase that is set by the Administrator. The passphrase must be between 8 and 20
characters in length. No default value exists nor will the passphrase ever expire or have
any frequency for resetting. Valid and invalid characters are shown on the configuration
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 at: http://www.veritas.com/docs/100040029.
13-31
32
The passphrase can be changed at any time. However, when changing a DR passphrase
Veritas recommends that you keep track of which passphrase belongs to which DR
package as NetBackup does NOT keep record of this. The correct passphrase is required
to restore the DR package at the time the DR package was created.
During a disaster recovery of the master server, if the passphrase is lost then the
identity certificates need to be regenerated for all hosts in the NetBackup domain to re-
establish the trust connection. This is accomplished through command line. For details
on this process, refer to Article 100033743: Getting your environment up and running
after a disaster when the disaster recovery package passphrase is lost at:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
http://www.veritas.com/docs/100033743.
Note: For security reasons NetBackup catalog backups do not backup the DR package,
DR passphrase or any identity information.
13-32
33
To create a NetBackup catalog backup, create a standard backup policy, selecting NBU-
Catalog from the Policy Type drop-down list. Select the desired storage unit from the
Policy storage drop-down list. Note that if a disk target is used, it should not be a
deduplication disk target and should not reside on the master server. This way, if
NetBackup or the master server is inaccessible, you are not prevented from getting to
your catalog backup.
Notice that selecting a policy type of NBU-Catalog results in a policy with three tabs:
Attributes, Schedules, and Disaster Recovery. The Clients tab is not needed because we
are backing up the catalog from the master server. Additionally, the Backup Selection
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
tab is not required because we know what is being backed up - the NetBackup catalogs.
13-33
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.
13-34
35
The Disaster Recovery tab provides the ability to set catalog backup settings. Creating a
catalog backup involves creating disaster recovery (DR) files that provide information
about 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Optionally enter any email addresses to send recovery information to, using a comma-
separated email list if there is more than one email address. Additional steps are
required to configure email notification in NetBackup. See the NetBackup
Administrator’s Guide for information about the nbmail.cmd and
mail_dr_info.cmd scripts. Additionally, refer to Article 100016001: How to
configure email notifications for Windows clients using BLAT and nbmail.cmd in
NetBackup at: http://www.veritas.com/docs/100016001. Finally, add any critical
policies desired. These are additional policies, whose media for their most recent
backups is also listed.
Note: The DR email is not sent to the address specified in the Global Attributes
property. The Administrator’s email address in the Global Attributes properties specifies
13-35
13-35
36
The screen shot on this slide shows NetBackup Activity Monitor with the catalog backup
jobs that have just completed. Also notice that in regards to the Image Cleanup job
status, if a catalog backup is not configured, the image cleanup returns a status code of
1 (partially successful). When a catalog backup job is configured, the image cleanup
returns a status code of 0 (successful). This was put in place to give customers adequate
warning when catalog backups had not been configured.
The image cleanup job that runs periodically and returns a partial success status code of
1 should have the following text in the job details to provide this warning:
Warning bpdbm (pid=process_ID) Hot catalog backup is not
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
13-36
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
13-37
38
• The general recovery method is the standard method for recovery that is available
with NetBackup. No special options or licenses are required for this option. This
method is discussed in this lesson.
• Auto Image Replication enables the duplication of any backups, including NetBackup
catalog backup images, to a remote NetBackup disaster recovery domain. Auto
Image Replication requires the use of OST-compliant appliances or MSDP, and at a
minimum, two NetBackup domains.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
13-38
39
The table on this slide shows the high-level procedure to follow to recover your
environment after a disaster, such as a full site failure. This procedure makes the
assumption that the backup data has been restored to the site, either from tapes that
have been vaulted and brought back to the primary site, or similar disk backup storage
has been made available. This includes the following steps:
1. Reload a minimal operating system to the new systems, including the master and
media servers that are to be used to restore application and server backup data.
2. Reinstall NetBackup software to the new master and media servers and ensure that
the exact same catalog paths are used on the master server including recreating the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
directory structure if the paths were altered (symbolic links) or if the catalog was
moved (nbdb_move).
3. Restore the disaster recovery package after NetBackup installation by running the
nbhostidentity -import -inifile file_path command.
4. Configure devices and media on the new NetBackup servers, so that they can now
access the backup storage where first, the NetBackup catalogs are stored and can be
recovered, and later, the rest of the environment data can be restored.
5. Recover NetBackup catalogs, so that the new master server has all the prior
knowledge of the previous master server, and can now restore all the available
backup data. Media server overrides may need to be configured unless media server
failover was previously configured. Additionally, Veritas recommends deactivating
any policies that should be inactive during this recovery period (to prevent
13-39
13-39
Command line
Use the bprecover -nbdb command to recover only NBDB.
40
This slide shows two functionally equivalent methods for performing catalog recovery.
This topic covers performing a catalog recovery using the Netbackup Catalog Recovery
Wizard. Here are some important points regarding disaster recovery:
• Catalog recovery relies on disaster recovery information generated during the online
catalog backup. Save the disaster recovery files created by the online catalog backup
to a network share or removable device.
• Configure the online, hot catalog backup policy to send an email copy of the disaster
recovery information as part of every catalog backup.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• Specify the most recent disaster recovery file available, unless some form of
corruption occurred and you want to restore to an earlier state of the catalog.
• If the most recent catalog backup was an incremental backup, use the disaster
recovery file from the incremental backup. There is no need to restore the full
backup followed by the incremental backup.
• To read the media that contains the catalog backup, first configure a robot and drive
and perform a robot inventory.
• If the catalog backup media is on a remote media server, restart NetBackup on the
remote media server after the master server has been reinstalled (after the
recovery).
13-40
41
Recover the entire catalog by using the NetBackup Catalog Recovery Wizard as follows:
13-41
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 email.
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 at: http://www.veritas.com/docs/100037884.
Click Next. The wizard waits while NetBackup searches for the necessary media
sources. The wizard then informs you if the necessary backup ID of the disaster
recovery image is located. If the media is not located, the wizard lists which media is
needed to update the database. If necessary, follow the wizard instructions to insert
the media that is indicated and run an inventory to update the NetBackup database.
The information that is displayed on this panel depends on whether the recovery is
from a full backup or an incremental backup.
13-42
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.
13-43
44
6. If desired, select a Job Priority and click Next to initiate the recovery of the entire
NetBackup catalog.
13-44
45
NetBackup restores the entire NetBackup relational databases. The wizard displays the
recovery progress and lets you know when the catalog has been recovered. When the
recovery job is finished, each image file is restored to the proper image directory and
the NetBackup relational databases have been restored and recovered.
13-45
46
13-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:
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:
13-47
• 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.
13-48
• 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:
After an image has been replicated to the target domain, standard duplication can be
used to copy that backup image to tape. In this way, a vaulted copy of the backup is
created without having to ship tapes. Auto Image Replication supports the ability to
create “hub and spoke” data centers, where remote offices send data to a central
location, as well as other DR models.
13-49
50
See the NetBackup Deduplication Guide for these specific procedures. Note that many
of these procedures may be version specific, so check for the guide specific to your
version of NetBackup. There is more detailed coverage of this topic in the NetBackup
Advanced Administration course.
13-50
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 catalog-related information using the NetBackup
Administration Console, NetBackup commands, and OpsCenter.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
13-51
• 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.
13-52
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.
13-53
53
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.
13-54
A. According to frequency
B. According to calendar
C. After each backup session
D. All of the above
54
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
13-55
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).
55
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
13-56
A. True
B. False
56
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
13-57
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.
57
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
13-58
58
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
13-59
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).
59
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
13-60
End of presentation
13-61
© 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.2:
Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-1
14-2
Topic Objective
File system backup challenges Discuss solutions for 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.
The table on this slide lists the topics and objectives for this lesson.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-3
After completing this topic, you will be able to discuss solutions for today’s
backup challenges.
14-4
This slide lists some of the common backup and restore 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 respective
feature and the NetBackup Advanced Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-5
• 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 (TIR) 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. A
normal restore may try to restore more files that ever existed in the file system at one
time, since it includes deleted files. Additionally, users will not find files that they had
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
previously deleted. NetBackup achieves this by making a list of the files that are present
in the file system during the backup. This list is stored on disk for 24 hours (which is
configurable) as well as stored with the backup image itself on the backup destination. If
the disk copy of the list does not exist during restore time, this list of files is read first
from the backup image to assist in the true image restore of the backup.
The TIR attribute can only be selected for MS-Windows and Standard policy types. It is
automatically selected and cannot be disabled, for the NBU-Catalog policy type. TIR can
be enabled with and without move detection, which is described in a following slide.
14-6
The example on the slide shows a series of backups starting with a full backup on
Sunday followed by daily incremental backups. The files listed in each daily column
show the files in the file system and the actions performed on the file: modified,
deleted, created or left unchanged. In the TIR information table, each column contains a
list of the files that are present in the file system at the time of each backup. These are
the files that will be included in the TIR file for that backup.
On Saturday you are asked to perform a full restore of the file system with Friday as the
recovery point. To do this you will need the Sunday full backup and each of the
incremental backups through Friday. If you select the Normal Backups restore type, the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
files shown in the first column (Recovery point without TIR) 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 (Recovery point with TIR) are the files that would be
restored using TIR. The files that are restored are those that were listed in the TIR file
for the Friday backup. Any files that were not present in the file system on Friday will
not be restored.
14-7
After completing this topic, you will be able to enable NTFS and VxFS
change logs, and synthetic full backups to optimize file system backups.
14-8
Even though an incremental backup backs up only those files that have changed,
NetBackup still has to examine every file in the file system to determine which files have
changed. This may involve examining millions of files to determine that only one file
needs to be backed up, which is unnecessarily time consuming.
One way to optimize incremental backups is to take advantage of change tracking logs,
which are offered as a feature by some file systems. These logs record which files have
been modified or added since the last backup. With the log in place, NetBackup no
longer has to examine each file, instead it looks at the log file and backs up only those
files listed in the log.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The Windows NTFS change journal, also known as the Update Sequence Number (USN)
change journal, is a disk file that records information about the changes made to a file
or directory within a specific volume. By reading this file, backup programs can quickly
determine which files need to be backed up during an incremental backup, thereby
eliminating the need to scan each file on the volume and speeding up the backup
process. The change journal is created on a volume by using the Windows fsutil
command:
14-9
The Veritas File System (VxFS), is a file system which is supported on a number of Unix
and Linux platforms. VxFS is used to increase the performance and availability of
production data. VxFS is part of Veritas InfoScale, which replaced Veritas Storage
Foundation, the software suite which previously contained VxFS. For more information
about Veritas InfoScale Storage, visit: https://www.veritas.com/product/storage-
management/infoscale-storage.
VxFS has a feature called the change log, which when turned on, tracks changes to files
and directories. This log can be used to greatly speed up incremental backups, as it
prevents the scan that is normally required to find changed files. This works best on
large file systems with many files, and few changes. The VxFS change log will not be
used if the backup encounters any errors while processing log, or if the Collect true
image restore information setting is enabled in the policy (on the Attribute tab). Both
of these log types require some configuration within NetBackup and at the file system
level.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-10
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. Select the Use Change
Journal check box. This needs to be done individually for each NetBackup Windows
client. After enabling Use Change Journal, there will be a period of time before the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Windows Change Journal data can actually be used during backup. NetBackup requires a
brief period of time to establish its own change journal databases. If a backup is
executed during this time, error messages will be logged to the ‘Job Details’ indicating
the reason why the change journal data could not be used. This option works together
with the Use accelerator policy attribute and the Accelerator forced rescan schedule
attribute, discussed elsewhere in this lesson.
14-11
Week 1 S M T W Th F Sa
Week 2 S M
Synthetic full generation takes place on the media server, any
time before the next incremental on Monday night.
Client + =
Backup 1. Baseline 2. Incremental 3. Synthetic full
schedule: full backup backups backup
Mon 21:00 Fri 21:00
Time of Mon 07:30
Tue 21:00 Sat 21:00
backup: Sun 21:00 Wed 21:00 Sun 21:00 (Recorded time:
Thu 21:00 Sun 21:00:01)
12
The synthetic full backup feature eliminates the need to perform full backups of a client
machine for supported resource types.
1. During week one, perform a full backup, also known as a baseline backup. This is a
normal full backup operation.
2. Between this first full backup and the schedule for the next full backup, perform
incremental backups on the changes that occur. This is a normal backup procedure
and is usually performed daily.
3. During the next schedule for a full backup, instead of running a normal full backup,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
run an incremental backup. In the example on the slide, instead of running a full
backup on the second Sunday at 9 P.M., an incremental backup was run.
4. Some time between this last incremental backup (on Sunday night, in the example)
and the next incremental backup (on Monday night), a synthetic full backup is run.
The synthetic full backup operation occurs on the media server, leaving the client free.
Because the synthetic full backup is executed on the media server without accessing the
client machine, it can be performed outside of the time-critical backup window,
reducing the overall backup window and associated network bandwidth requirements.
The newly created synthetic full backup replaces the baseline full backup and becomes
the baseline full backup for subsequent synthetic full backup operations.
14-12
Set Collect true image restore information with move detection on the
policy:
2. Configure TIR
13
1. Create a policy with either the Standard or the MS-Windows policy type.
2. Mark the Collect true image restore information with move detection check boxes.
3. Create the policy with at least the following three types of schedules:
• One traditional full backup: The full backup must successfully run to completion.
• At least one incremental backup: The incremental backups capture the changes
since the last full or incremental backup.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• One full or cumulative backup with the Synthetic backup check box marked: The
synthetic backup is the combination and synthesis of the original full backup
with the incremental backups.
Optimized synthetics
Note that because synthetic backups involve taking the prior full backup and applying
all the incremental changes, using a deduplication storage destination may have
additional benefits in that the new synthetic full will require very little data copy
operations when creating the new full data. This is known as an Optimized Synthetic
backup in NetBackup, and is described in Article 100022690: Configuring Optimized
Synthetic Backups to NetBackup Deduplication Pools at:
http://www.veritas.com/docs/100022690.
14-13
After completing this topic, you will be able to configure and manage
NetBackup Accelerator.
14
This is the Optimizing file system backups with NetBackup Accelerator topic.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-14
15
NetBackup Accelerator is a licensed NetBackup feature that increases the speed of full
backups by using platform-agnostic file system change tracking track logs on the client
to identify changes that have occurred since the last backup. During an accelerator
enabled backup only the changed data are transferred to the deduplication storage.
On the storage, a new optimized synthetic full backup is created by combining the
changed data with pointers to the unchanged data from previous backups. This process
removes the need to transfer all the client data across the network. This methodology
uses less network bandwidth and reduces the overhead on client resources such as
CPU, memory, I/O and file system cache. Note that although not required, NetBackup
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
client-side deduplication can add benefits related to better bandwidth usage, and is
often used together with NetBackup Accelerator. NetBackup Accelerator should be
regarded as a complimentary technology of client deduplication, and not as a
replacement for it. No further installation is required for NetBackup Accelerator. The
necessary binaries are included with the NetBackup client files.
14-15
Versions NetBackup 7.5 or later for master servers, media server, and clients
16
This 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 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
17
During the first backup - After setting the Use Accelerator option in the policy
attributes, the next backup of that policy will be a full backup. At that time, a client track
log will be created on the client, which will identify the master server, the storage
server, the client, the policy and the files that were backed up as well as the segments
which make up each file. During successive backups the following steps are performed:
1. File and directory meta data are compared with the track log to identify files that
have changed. The following criteria are used:
• NFS (Network File System): Normally used on Unix clients, Accelerator uses
mtime, ctime, and inode number, file size.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
If a file has not changed, the scan continues. If file metadata has changed, the file is
open, read, and the data fingerprints for each 128K file segment are compared to
the previous track log.
14-17
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-18
• 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-19
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-20
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 this 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-21
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
14-22
14-22
14-23
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 at:
http://www.veritas.com/docs/100038114.
14-24
25
Note that although BLIB improves incremental performance, it comes with some
restrictions around not being able to use NetBackup’s Granular Restore Technology
(GRT) for coordinated application protection in a VM backup. GRT requires a full backup
of the VM with application protection enabled in the NetBackup policy. NetBackup
Accelerator does provide the same excellent performance enabled by CBT tracking, and
because it is performing a full backup, additionally provides application protection with
GRT. The requirement for Accelerator is that the destination storage in the policy
supports optimized synthetics. Essentially the storage must support deduplication. A
check is made by NetBackup when the Policy Storage is selected. If the storage does not
support optimized synthetics, you will not be able to select the Use Accelerator
checkbox.
14-25
• 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:
• 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 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
14-26
14-26
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-27
After completing this topic, you will be able to configure a policy to take
advantage of multiple data streams.
28
14-28
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
selecting 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 is 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
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
protect you from disk thrashing that would cause bad performance. However, if you
want to take advantage of performance benefits by having multiple data streams, 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
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:
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 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
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
selected 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
this mode, the Backup selections list is sent to the client, which preprocesses the list
and splits the backup into streams as follows:
• For ALL_LOCAL_DRIVES directive, NetBackup backs up the entire client, with each
drive volume (Windows) or mount point (UNIX) into its own backup stream.
• If wildcards are used, the expansion of the wildcards results in one stream per
wildcard expansion.
If the Backup selections list contains neither ALL_LOCAL_DRIVES nor wildcards, auto-
discovery mode is not used. In this case, the server performs the preprocessing (rather
than the client) and each Backup selections list entry becomes a separate stream.
14-33
NEW_STREAM directive
Windows
client
C:\ E:\
3 jobs
L:\ 229 – Parent
230 – Child with C:\Data and E:\Data
231 – Child with L:\Data
34
In the previous example we backed up three drives in three separate streams. If C:\ and
E:\ were logical partitions on the same physical disk you would not want to back them
up in separate streams. Doing so could cause excessive head movement on the drive as
it attempts to satisfy simultaneous read requests from different drive locations and
possibly result in poorer backup performance. The better method would be to put
drives C:\ and E:\ into one stream and the L:\ drive in a separate stream. This is referred
to as administrator-defined streaming mode, and can be accomplished by using the
NEW_STREAM directive. Use of the NEW_STREAM directive follows these rules:
• The first use of this directive must be on the first line of the Backup selections list.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• A backup is split into a separate data stream at each point in the backup selections
list where the NEW_STREAM directive occurs. All file paths defined between
NEW_STREAM directives appear in the same data stream. The end of each stream is
defined by the start of a new stream (the NEW_STREAM directive).
• The last stream in the list is terminated by the end of the Backup selections list. A
NEW_STREAM directive is not required.
14-34
ALL_LOCAL_DRIVES
Windows directive
client
10 jobs
232 – Parent
C:\ H:\
233 – Shadow Copy Components
E:\ I:\ 234 – C:\ 238 – I:\
F:\ J:\ 235 – E:\ 239 – J:\
236 – F:\ 240 – K:\
G:\ K:\ 237 – G:\ 241 – H:\
(All drives on client)
35
The example on 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:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-35
After completing this topic, you will be able to configure backups for
optimum tape drive performance using multiplexing.
36
14-36
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
Storage Unit > • Fast device that handles many jobs concurrently
Maximum streams per
• Prevent “shoe-shining” on the tape drive
drive
• Many slow clients; many short backups
Schedule >
• Prevent multiplexing for this backup or schedule,
Media multiplexing
if not desired
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
After completing this topic, you will be able to configure the way that
NetBackup handles busy files on UNIX and Windows.
39
This is the Handling busy files on UNIX and Windows file systems topic.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-39
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 features in NetBackup to customize the
behavior when encountering files that cannot 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:
14-40
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
• 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-43
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-44
44
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.
14-45
45
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-46
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.
46
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-47
47
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-48
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.
48
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
14-49
End of presentation
14-50
© 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.2: Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-1
15-2
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-3
After completing this topic, you will be able to perform very basic
troubleshooting for NetBackup environments.
15-4
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?” What appears to have caused the
error.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• 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? operating system
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
A 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-6
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
The All Log Entries report will display the entire catalog contents. The catalog is a log,
which is automatically setup and enabled at installation. Error logs are created on a 24-
hour cycle. At midnight each day, the daily log is closed and a new one is opened for the
next days events. By default the logs are kept for 28 days. This can be configured in the
master server host properties under the Clean-up tab. See the NetBackup Commands
Reference Guide for more information about running commands.
15-7
The All Log Entries report displays 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, 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-8
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-9
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-10
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
access the information on this report from the command line, type:
bperror -media -U
15-11
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.
From the File menu, select Export. Name the export file and specify where the file is to
be saved. You can achieve a similar result from the command line by redirecting the
output to a file: bperror -media -U > file.txt
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-12
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
15-13
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.
15-14
15
You can use the NetBackup Activity Monitor to monitor the services/daemons which are
currently running:
From here, you can view the details of the active services and daemons.
15-15
16
15-16
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:
This slide shows a screenshot for a master server. On media servers or clients the list of
NetBackup services will be much smaller 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 at:
http://www.veritas.com/docs/100002166.
15-17
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 at: http://www.veritas.com/docs/100002166.
15-18
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:
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):
15-19
15-19
20
This slide displays a number of additional daemons on the media server. These daemons
start running after tape devices are configured, and include:
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
21
This slide displays a number of additional daemons on the media server. These daemons
start running after a Media Server Deduplication pool is configured, and include:
15-21
bpbrm
bptm
22
During some operations you will see additional processes. For example, during a simple
backup you may see the following processes on the media server:
During a backup, you will also see this process on the client:
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
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
The first few commands show how to stop and start NetBackup processes gracefully for
both UNIX and Windows NetBackup servers. Individual daemons or services have
different commands by which you can terminate and restart them. For example, to
terminate ltid (the Device Manager), type the stopltid command. See the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
NetBackup Commands Reference Guide for detailed information about how to stop and
restart specific daemons/services.
Consider that stopping certain daemons or services may impact other daemons or
services. For example, stopping the NetBackup Request Daemon (bprd) stops all future
backup and restore activity. Jobs already running are able to complete because they no
longer depend on bprd. NetBackup provides the bp.kill_all and bp.start_all
scripts that are intended to stop and start all daemons when no backup or restore
operation is in progress.
15-23
After completing this topic, you will be able to describe legacy and unified
NetBackup logs.
24
15-24
25
The following slides are designed to help you understand how NetBackup logging works
so that you can better assist Veritas Technical 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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, fewer logs will be required.
15-25
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 configurable.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• 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. As a best practice 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
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:
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• 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
15-27
15-27
• 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
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.
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 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
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.
it manually. Some sample lines from nblog.conf showing the OID and settings for
nbjm are as follows:
Settings can also be changed for ALL processes. Finally, the Default value for a given setting can be
changed
15-30
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-31
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 Technical
Support.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-32
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, 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, 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
After completing this topic, you will be able to use the NBSU and NBCPLOGS
utilities, and describe the Logging Assistant.
34
15-34
• 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
emailed or submitted to them.
• UNIX: ./output/nbsu/hostname-role-YYYYMMDD_HHMMSS
• Windows: C:\Users\username\output\nbsu\hostname-
role_YYYYMMDD_HHMMSS
The output can be redirected to a different output directory by using the command:
nbsu –odir destination_directory
15-35
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
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-37
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-38
39
When you open a case with Veritas Technical 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 is 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 at: http://www.veritas.com/docs/100038665.
15-39
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-40
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-41
42
The Logging Assistant is a helpful tool that can shorten the time 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 at: http://www.veritas.com/docs/100028985.
15-42
After completing this topic, you will be able to identify available resources
for NetBackup troubleshooting.
43
15-43
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
15-44
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. 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 for support.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
46
Various methods may be available to upload and download a small number of files
directly to an existing Veritas Support case. These methods 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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 at: http://www.veritas.com/docs/100038665.
15-46
• 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-47
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-48
48
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.
15-49
49
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-50
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.
50
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-51
51
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-52
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.
52
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-53
53
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-54
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.
54
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
15-55
End of presentation
15-56
© 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.2: Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-1
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-2
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
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-4
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
• Most backups start automatically based on the schedules defined by the NetBackup
administrator. These include full schedules, incremental schedules (both differential
and cumulative), and automatic schedules, used by some NetBackup agents to
control when the application schedule runs. These schedules tend to be based on
frequency or on a calendar.
• Manual backups enable you to perform the backup immediately, on demand. For
this reason, they are sometimes known as immediate backups. Manual backups can
be initiated from any of the NetBackup administrative interfaces, including the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Administration Console, the command line, and OpsCenter. Manual backups can
also be run by schedulers outside of NetBackup, such as scripts, the cron utility, or
the Windows Task Scheduler.
• Application or user schedules, including user backups and archives, are client-
requested backups that enable the end-user or application on the NetBackup client
to control when a backup runs and which information is contained in the backup. By
default, users and applications on the client do not have permission to request
backups: the NetBackup administrator must create specific schedules to allow this,
and may choose to limit client requested backups to specific hosts or at specific
times of the day. Client requested backups do not use the policy’s Backup Selections
list; the user or application always chooses what is to be protected at the time the
backup runs. Some application backups may be initiated by special automatic
schedules by the NetBackup scheduler.
A-5
As shown on the slide, there are many policy types in NetBackup, which correspond to
different ways of handling different types of data:
A-6
Backups Restore
This slide shows three ways you can choose to back up an Oracle database:
1. The database is shut down completely, and the database files are backed up as
standard files in a file system. When the backup is complete, the database can be
restarted. Database shutdown must be automated through scheduling or scripting.
2. The Oracle Recovery Manager (RMAN) is used to automate the process of dumping
the database to files in the file system. NetBackup is scheduled to systematically
archive these files with a normal file system backup policy.
3. The NetBackup Agent for Oracle contains everything that is needed to successfully
back up and restore an Oracle database by using APIs to control RMAN and back up
the database on NetBackup’s schedule, without affecting database downtime. This
method requires additional NetBackup licensing.
A-7
Database 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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
10
blocks are backed up. Used in conjunction with NetBackup Accelerator, this can create
full backups from the block level incremental backup.
Oracle has integration with VxFS Storage Checkpoint to enable changed block
identification in real time. BLI backup does not need to search the entire database for
the modified blocks, which saves time, decreases the amount of backup media that is
required, and significantly reduces CPU and network overhead during backups. BLIB
backups for Oracle are not widely used nowadays as there is no integration into RMAN.
A-10
After completing this topic, you will be able to discuss database backup and
restore concepts.
11
A-11
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-12
13
Data backups
• Replication
Each of these strategies can protect against some of the failure types. Each of them also
provides advantages and disadvantages, such as backup performance, restore
performance, and the minimization of database downtime. None of these methods
protects against all types of failures, and it is only with a comprehensive strategy that
takes into account all of these methods, that you are best equipped to handle a disaster.
NetBackup provides the advantage of not only managing data backups, but also being
able to initiate restores within the application to take advantage of transaction and redo
logs, snapshots, and some replication features.
A-13
14
• Physical or logical data backups: One of the first choices you must make is how to
execute the backup process. How you choose to back up your database influences
other choices later in the process. The most common backup method is a physical
backup of a database. This method creates a mirror image of the database that is
complete in detail down to the physical location of the data blocks. You can
occasionally perform a logical backup, which exports a snapshot of the data from
the database but does not record the physical structure of the database.
• Cold (offline) backups: A consistent backup is commonly referred to as a cold backup
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
because the database must be shut down (offline) while the backup is performed.
With a cold backup, recovery actions are not needed to restart the database after a
restore.
• Hot (online) backups: An inconsistent backup is commonly referred to as a hot
backup because the database is open and operational (online) while the backup is
performed. The database must maintain an updated record of transactions that
occur while the backup is performed. With a hot backup, recovery actions are
necessary before you can restart the database after a restore, which usually involve
using the previously recorded set of transactions to assist in recovering the data to a
consistent state.
A-14
providing the ability to use all of these backup strategies and technologies.
A-15
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-16
17
The graphic on this slide describes the process for backing up a database using an
Automatic schedule. In this procedure:
A-17
After completing this topic, you will be able to discuss options for backing
up and restoring Exchange, Active Directory, SharePoint, and Enterprise
Vault.
18
A-18
19
• Exchange Server data and transaction logs can be backed up without taking the
Exchange Server offline. Exchange services and data remain available.
• Exchange Server backups can be saved directly to a wide variety of storage devices
that the NetBackup master server supports.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• NetBackup supports all Exchange Server backup methods, including full, cumulative
incremental, and differential incremental backups.
• From one-pass backups of Exchange, Granular Restore Technology (GRT) can be used
to create consistent full backups, as well as restore Exchange storage groups or
databases and individual database objects. This backup takes much less time than
prior MAPI-based (brick-level) backups.
• From a one-pass backup of a virtual machine running Exchange, a GRT-enabled
backup can be created for full restore or granular restore ability.
• NetBackup for Exchange supports backups of Exchange 2010 stand-alone servers
and Exchange 2010 Database Availability Groups (DAGs).
A-19
For additional details, see the NetBackup for Microsoft Exchange Server Administrator’s
Guide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-20
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-21
22
• SharePoint Server objects can be backed up without taking the SharePoint Server
offline. SharePoint services and data are available during the backup.
• NetBackup supports full and differential-incremental backups of SharePoint.
• NetBackup for SharePoint supports the backup and recovery of multiple SharePoint
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
For additional details, see the NetBackup for Microsoft SharePoint Server
Administrator’s Guide.
A-22
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Check the NetBackup documentation to find out which version of Windows support
Active Directory granular restores.
A-23
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:
A-24
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:
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
• 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-26
27
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-27
28
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-28
The correct answer is B. Block level incremental backups (BLIB) backs up changed data for Oracle. This method does not
apply to Exchange
29
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-29
30
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-30
The correct answer is D. This technique is also common to other databases, such as Microsoft SQL Server.
31
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-31
32
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-32
The correct answer is D. Granular Recovery Technology provides this functionality for Exchange.
33
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
A-33
End of presentation
A-34
© 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.2: Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-1
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-2
After completing this topic, you will be able to describe virtual machines
and discuss support for virtual machines in Hyper-V.
B-3
• 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.
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
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-5
VMware vSphere ✓ ✓ ✓ ✓ ✓
Microsoft Hyper-V ✓ ✓ ✓ ✓
RedHat Enterprise
Virtualization ✓
Citrix XenServer ✓
Solaris zones ✓
Oracle Solaris
virtualization ✓
Technical articles and best practices exist for these virtualization solutions.
B-6
Hypervisor
control system
SAN
Control API
CLI
Web Interface
Storage
Cloud
orchestration
Virtualization
Web Client
Veritas uses the capabilities provided by the hypervisor supplier to develop VM-specific
backup solutions. There are limitations and requirements, based on the software and
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
B-7
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).
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-8
B-9
SAN
Virtual machines
Each Hyper-V server requires
one NetBackup client.
10
This slide shows a NetBackup for Hyper-V environment. To use the NetBackup Hyper-V
policy type, a NetBackup 7.5 or later client must exist on each Hyper-V server. For the
optional off-host backup approach, a NetBackup client must be installed on the
alternate client. Note: In most cases, the NetBackup client does not need to be installed
on any virtual machine. For exceptions, see the Veritas NetBackup for Hyper-V
Administrator’s Guide.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-10
SAN
11
This slide shows an optimized NetBackup for Hyper-V environment. Installing the Media
Server software instead of the client software on the Hyper-V server allows it to send
backup data directly to tapes or disk storage units across the SAN.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-11
SAN
12
This slide shows an optimized NetBackup for Hyper-V environment. In this example we
are using the SAN Client feature to send data across the SAN to a NetBackup media
server (in this example, a NetBackup appliance). SAN client provides the same benefit
that SAN Media server does, but with a reduced footprint on the Hyper-V server. SAN
client and SAN media Server are both available with the Enterprise Client license, which
Hyper-V requires anyway.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-12
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:
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
14
This slide lists Hyper-V components and components used by NetBackup when backing
up Hyper-V.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-14
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
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.
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
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-17
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-19
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 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-20
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-21
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,
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
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:
In either circumstance, the policy backs up all local drives from each listed virtual
machine.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-23
24
Enable file recovery from VM backup: This option allows the restore of individual files
from the backup. With or without this option, you can restore the entire virtual
machine.
Use this option for incremental backups (differential incremental backup or cumulative
incremental backup). To perform a Hyper-V backup to a deduplication storage unit,
select this option. This option provides the best deduplication rates.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-24
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
B-25
B-25
B-26
27
Enable offline backup for non-VSS VMs: This option determines whether or not
NetBackup is allowed to perform an offline backup of a virtual machine. This option is
intended for the guest operating systems that do not support VSS (such as Linux).
Note: Online vs. offline backup are Microsoft backup types and are not configured in
NetBackup.
If this option is enabled, NetBackup can perform an offline backup of a virtual machine.
In certain situations, if the virtual machine cannot be quiesced for an online backup, the
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
virtual machine must be placed in the Saved state. The backup is thus performed offline.
User access to the virtual machine may be interrupted during the backup. After the
backup is completed, the virtual machine is returned to its original state. If this option is
disabled, NetBackup is not allowed to perform an offline backup of a virtual machine. If
an online backup cannot be done, the backup job fails with status 156
Cluster shared volumes timeout: For clusters on Windows server 2008 R2: This option
applies to backups of the virtual machines that are configured in a Microsoft Cluster
that uses cluster shared volumes (CSV). The timeout determines how long the backup
job waits, in case another cluster node backs up the same shared volume at the same
time. A wait of 3 hours (the default) is recommended if you have multiple virtual
machines on one CSV.
B-27
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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.
B-28
29
B-29
After completing this topic, you will be able to perform and monitor Hyper-
V backups.
30
B-30
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-31
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-32
After completing this topic, you will be able to perform Hyper-V restores.
33
B-33
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.
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
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.
B-35
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-36
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-37
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-38
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-40
After completing this topic, you will be able to perform Hyper-V restores
with the NetBackup Add-in for SCVMM.
41
This is the Performing Hyper-V restores with the NetBackup Add-in for SCVMM topic.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-41
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
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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:
B-42
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-43
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-44
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-46
47
In the SCVMM console, open the Jobs workspace to view Running jobs. The Status
column shows the job’s percentage completion.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-47
48
For a listing of recent jobs and past jobs, click History, and select a time range from the
top ribbon.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-48
• 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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
B-49
End of presentation
B-50
© 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 BasicDisk Staging appendix in the Veritas NetBackup
8.1.2: Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
C-1
After completing this topic, you will be able to configure disk staging with
BasicDisk storage units.
C-2
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
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
C-3
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
C-4
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• 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
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
C-6
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:
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
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.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
C-8
End of presentation
C-9
© 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 Instant Access Feature for VMware appendix in the Veritas NetBackup 8.1.2:
Administration course.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
D-1
After completing this topic, you will be able to configure disk staging with
BasicDisk storage units.
D-2
NetBackup mounts the VM's snapshot directly on the backup storage device to allow your ESXi host or cluster to treat
the snapshot as a normal VM. The mounted VM snapshot can be used for a variety of purposes.
Note: The instant access feature is supported only for NetBackup appliances and requires that the NetBackup backup image is stored on a Media Server Deduplication Pool (MSDP) storage device.
It is now possible to create an instant access VM from a NetBackup backup image using
the Instant Access Feature for VMware. The VM is available almost instantaneously,
achieving a near-zero recovery time objective. NetBackup mounts the VM's snapshot
directly on the backup storage device to allow your ESXi host or cluster to treat the
snapshot as a normal VM.
The mounted VM snapshot can be used for a variety of purposes. For example:
• Recovering files from the VM, or copying a vmdk file.
• Running tests on the VM, such as testing a patch.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
Note: The instant access feature is supported only for NetBackup appliances and
requires that the NetBackup backup image is stored on a Media Server Deduplication
Pool (MSDP) storage device.
D-3
Note the following about the Instant access virtual machines feature:
• This feature is supported with backup copies that are created from protection plans
using the web UI.
• Classic policies that are created with the NetBackup Administration Console also
support instant access when the policy uses the VM instance UUID as the Primary
VM identifier.
• This feature supports only the VMware policy type in NetBackup. For the policy types
that the web UI protection plans use, contact the backup administrator.
• This feature is supported only for NetBackup appliances.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
D-4
This feature does not support For Windows single file restore,
This feature does not support VMs that have a disk in raw LDM volumes and the ReFS file
VMs that have disks that were device mapping mode (RDM) or system are not supported, and
excluded from the backup. that have a disk in Persistent the Access Control Lists (ACLs) are
mode. not preserved.
• This feature does not support VMs that have disks that were excluded from the
backup. On the NetBackup policy's Exclude Disks tab, the No disks excluded option
must be selected.
• This feature does not support VMs that have a disk in raw device mapping mode
(RDM) or that have a disk in Persistent mode.
• For Windows single file restore, LDM volumes and the ReFS file system are not
supported, and the Access Control Lists (ACLs) are not preserved.
• The version of the ESXi server that is used to create a VM using Instant access virtual
machines must be equal to or newer than the version of the ESXi server that contains
the VM backup images.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
• This feature supports single file restore of file sizes up to 1 GB. For larger files, you
can use the Download option, or start the VM and copy the required file. For single-
file download with the Download option, the NetBackup web UI must be able to
access the media server with the same name or IP address that the master server
uses to connect to that media server.
• If the media server appliance uses a third-party certificate, you need to create certain
configurations on the NetBackup master server before you use this feature. For more
information, refer to the "Third-party certificates" and "Implementing third-party SSL
certificates" sections in the NetBackup Appliance Security Guide, available here:
http://www.veritas.com/docs/000003214
D-5
After completing this topic, you will be able to configure disk staging with
BasicDisk storage units.
This is the Creating and recovering files from an instant access VM topic.
Copyright @ 2018 Veritas Technologies LLC. All rights reserved.
D-6
D-7
5
Review the recovery settings and
make changes if needed
D-8
D-9
Enter the user name and password for the VM and the destination path in the
VM (the default is the
5
original file path).
Note: The web UI does not currently support restoring the file to a
different VM or to a different VMware server.
7. Click Restore.
10
D-10
End of presentation
D-11