Professional Documents
Culture Documents
Veritas Netbackup Administrator'S Guide, Volume I: For Unix and Linux
Veritas Netbackup Administrator'S Guide, Volume I: For Unix and Linux
Release 6.5
12308276
Veritas NetBackup Administrator’s Guide, Volume I
NetBackup 6.5
Symantec, the Symantec logo, and NetBackup are trademarks or registered trademarks of
Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be
trademarks of their respective owners.
Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-
Digest Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights
reserved.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THIS DOCUMENTATION 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, SYMANTEC CORPORATION SHALL
NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION
WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE
INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE
WITHOUT NOTICE.
Symantec Corporation
20330 Stevens Creek Blvd.
Cupertino, CA 95014
www.symantec.com
Technical support
For technical assistance, visit http://entsupport.symantec.com and select phone
or email support. Use the Knowledge Base search feature to access resources
such as TechNotes, product alerts, software downloads, hardware compatibility
lists, and our customer email notification service.
Contents
Chapter 1 Introduction
Overview ................................................................................................................31
Reports ...................................................................................................42
Policies ...................................................................................................43
Storage ...................................................................................................43
Catalog ...................................................................................................44
Media ......................................................................................................45
Devices ...................................................................................................45
Credentials ............................................................................................45
Chapter 3 Reports
Introduction to the Reports utility ................................................................... 72
Client ...................................................................................................... 74
Job ID ..................................................................................................... 74
Media ID ................................................................................................ 74
Path ........................................................................................................ 75
Volume ID ............................................................................................. 75
Chapter 4 Policies
Using the Policies utility .....................................................................................82
How the Cross mount points attribute interacts with Follow NFS 104
Encryption ..................................................................................................107
Collect disaster recovery information for Bare Metal Restore ........... 108
Collect true image restore information with move detection ............ 109
Retention .....................................................................................................138
10
Backup and restore of extended attribute files and named data streams
180
182
11
Path ..............................................................................................................197
Logon ...........................................................................................................197
Password .....................................................................................................197
Density .........................................................................................................229
12
Using the Maximum concurrent jobs setting to control the storage unit
Disk staging storage unit size and capacity considerations ............... 245
Finding the potential free space on a BasicDisk disk staging storage unit
246
13
MIN_KB_SIZE_PER_DUPLICATION_JOB .......................................264
MAX_KB_SIZE_PER_DUPLICATION_JOB ......................................264
MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB .......264
Prioritized ...........................................................................................267
Failover ................................................................................................267
14
294
Disaster recovery emails and the disaster recovery file .............................. 317
15
User ......................................................................................................373
Host ......................................................................................................374
Domain\Group ....................................................................................374
16
Move restore job from incomplete state to done state ................ 385
Move backup job from incomplete state to done state ................ 385
17
Rank .....................................................................................................407
Name ....................................................................................................408
Description ..........................................................................................408
18
Backup option for log files during full backups ............................ 413
Policy ...................................................................................................416
Always .................................................................................................423
19
Path ......................................................................................................445
20
Multiple masters that share one Enterprise Media Manager host 467
User ID .................................................................................................471
21
22
Chapter 9 Media
Volume operations ............................................................................................ 507
Moving volumes using the robot inventory update option ......... 525
23
Description ..........................................................................................540
Robot ....................................................................................................551
Media that have been moved into or within the robot .................559
24
Example 7: Adding existing volumes when barcodes are not used 587
Using unique drive and media types to manage WORM media . 591
Chapter 10 Devices
Device configuration prerequisites ................................................................ 593
25
State .....................................................................................................618
Description ..........................................................................................618
26
Chapter 11 Credentials
Chapter 12 Management topics
NetBackup naming conventions ..................................................................... 631
NBJAVA_CONNECT_OPTION ..........................................................665
NBJAVA_CORBA_DEFAULT_TIMEOUT ........................................665
To log the command lines that the NetBackup interfaces use ... 666
27
667
668
Is the performance better when run locally or using remote display back?
670
28
/scripts .................................................................................................703
Moving the NetBackup database from one host to another ....................... 719
29
30
Using the NearStore disk storage unit for more than one purpose ... 754
755
Troubleshooting .................................................................................................764
Index 773
Chapter 1
Introduction
The NetBackup Administrator’s Guide, Volume I describes the core NetBackup
product. This manual describes NetBackup configuration options—what they are
and how each can be used to benefit the backup needs of your environment. This
manual is organized to reflect the arrangement of the NetBackup
Administration Console.
This chapter provides an introduction to NetBackup software, the interfaces
available, and the distributed architecture of NetBackup. This chapter contains
the following sections:
■ “Overview” on page 31
■ “NetBackup administration interfaces” on page 34
■ “NetBackup Administration Console setup” on page 35
■ “Using the NetBackup Administration Console” on page 40
■ “How to configure NetBackup” on page 46
Overview
NetBackup provides a complete, flexible data protection solution for a variety of
platforms. The platforms include Microsoft Windows, UNIX, Linux, and
NetWare systems.
NetBackup administrators can set up periodic or calendar-based schedules to
perform automatic, unattended backups for clients across a network. An
administrator can carefully schedule backups to achieve systematic and
complete backups over a period of time, and optimize network traffic during
off-peak hours. The backups can be full or incremental. Full backups back up all
client files. Incremental backups back up only the files that have changed since
the last backup.
32 Introduction
Overview
The NetBackup administrator can allow users to backup, restore, or archive the
files from their computer. (An archive operation backs up a file, then deletes it
from the local disk if the backup is successful.)
NetBackup includes both the server and the client software:
■ Server software resides on the computer that manages the storage devices.
■ Client software resides on computer(s) that contain data to back up. (Servers
also contain client software and can be backed up.)
NetBackup
master server
Media servers
SAN
OpenStorage or SharedDisk
Media Manager tape BasicDisk disk pool
storage unit storage unit
NetBackup
clients
Note: The NetBackup host that is specified on the login dialog and the machine
where you start the NetBackup-Java console must run the same NetBackup
version.
Note: The default host is the last host that was successfully logged into. The
drop-down list contains the names of other hosts that have been logged into.
Master Server
The information in the
NetBackup Administration Console
applies to this server only.
Backup, Archive, and Restore
Performs the client actions for this
system.
Activity Monitor
Displays the information about
NetBackup jobs and provides some
control over the jobs.
NetBackup Management
Contains the utilities to create and
view reports, for configuring
policies, storage units, catalog
backups, and a utility for
configuring master server, media
server, and client properties.
Media and Device Management
Contains the utilities for managing
the media and devices that
NetBackup uses to store backups.
Access Management
Contents of node are viewable only
by a Security Administrator when
NetBackup access control is
configured. Additional licensed utilities Details pane
The nodes of other licensed utilities Contains the configuration wizards
appear under the main NetBackup and details specific to the utility
nodes. that is selected.
Use the Catalog Recovery Wizard in a disaster recovery situation. Use the
Catalog Recovery Wizard only if the NetBackup environment was running
the policy-based online, hot catalog backup as the catalog backup type.
Documentation for the NetBackup client is available as online Help from the
Backup, Archive, and Restore interface.
Activity Monitor
Use the Activity Monitor utility to monitor and control NetBackup jobs, services,
NetBackup Management
This manual describes the applications and the utilities that are listed under
NetBackup Management in the NetBackup Administration Console tree.
The following sections describe the items that are found under NetBackup
Management.
Reports
Use the Reports utility to compile information for to verify, manage, and
Introduction 43
Using the NetBackup Administration Console
Policies
Use the Policies utility to create and specify the backup policies that define the
rules for backing up a group of clients.
For example, the backup policy specifies when automatic backups occur for the
clients that are specified in the policy. The backup policy also specifies whether
users can perform their own backups and when. The administrator can define
any number of backup policies, each of which can apply to one or more clients. A
NetBackup client must belong to at least one backup policy to be backed up.
For more information see Chapter 4, “Policies” on page 81.
Storage
Use the Storage utility to display storage unit information and manage
NetBackup storage units. A storage unit can be part of a storage unit group as
well as part of a storage lifecycle policy, both of which are configured within the
Storage utility.
Storage units simplify administration because once defined, the NetBackup
policy points to a storage unit rather than to the individual devices it contains.
For example, if a storage unit contains two drives and one is busy, NetBackup
can use the other drive without administrator intervention.
The media can be one of the following:
■ Removable (such as tape in a robot or a stand-alone drive).
The devices in a removable-media storage unit must attach to a NetBackup
master or media server and be under control of the NetBackup Media
Manager component. The administrator first configures the drives, robots,
and media in NetBackup, then defines the storage units. During a backup,
NetBackup sends data to the storage unit that the backup policy specifies.
During a backup, Media Manager picks a device to which the NetBackup
client sends data.
■ Disk (such as a file directory within a file system or a collection of disk
volumes, either independent file systems or in an appliance).
The administrator specifies the directory, volume, or disk pool during the
storage unit setup. For BasicDisk, NetBackup sends the data to that
directory during backups. For the Enterprise Disk Options, NetBackup
sends the data to the storage server (the host that writes to the storage).
Media Manager is not involved.
For disk pool storage, the administrator first defines the storage server and
(depending on the disk type) its logon credentials. Depending on disk type,
the administrator may have to define logon credentials for the storage
itself. The administrator also selects the disk volumes that comprise the
44 Introduction
Using the NetBackup Administration Console
disk pool. To create a storage unit, the administrator selects a disk pool and
(depending on the disk type) selects the media server(s) to move the data.
Note: Only storage units that point to shareable disk can specify more than
one media server.
For more information, see Chapter 5, “Storage units, unit groups, and lifecycle
policies” on page 213.
Catalog
Use the Catalog utility to create and configure a special type of backup
NetBackup requires for its own internal databases—an offline, cold catalog
backup.
(An online, hot catalog backup can also be used, and is configured with a wizard
or through the Policies utility.)
These databases, called catalogs, are located on the NetBackup master and
media server (default location). The catalogs contain information on every client
backup. Catalog backups are tracked separately from other backups to ensure
recovery in case of a server crash.
The Catalog utility is also used for the following actions:
■ to duplicate a backup image,
■ to promote a backup image from a copy to the primary backup copy,
■ to manually expire backup images,
■ to import expired backup images or images from another NetBackup server,
■ to search for a backup image to verify the contents of the media with what is
recorded in the NetBackup catalog.
For more information, see Chapter 6, “NetBackup Catalog” on page 275.
Host Properties
Use the Host Properties utility to customize NetBackup configuration options.
Device Monitor
Use the Device Monitor utility to manage drives, device paths, and service
requests for operators. For more information, see Chapter 8, “Device Monitor”
on page 495.
Media
Use the Media utility to add and manage removable media. For more
information, see Chapter 9, “Media” on page 507.
Devices
Use the Devices utility to add, configure, and manage storage devices. For more
information, see Chapter 10, “Devices” on page 593.
Credentials
Use the Credentials utility to add, remove, and manage log-in credentials for:
■ Disk array hosts (requires an Enterprise Disk Option license).
For more information about disk array hosts and the SharedDisk disk type,
see the NetBackup Shared Storage Guide.
■ NDMP hosts (requires the Virtual Tape Option license).
For more information about NDMP, see the NetBackup for NDMP
Administrator’s Guide.
■ Storage servers (requires an Enterprise Disk Option license).
For more information about the Enterprise Disk Options, see the NetBackup
Shared Storage Guide.
Credentials appears only if one of the previously mentioned license keys is
installed.
Access Management
NetBackup administrators can protect a NetBackup configuration by defining
who may access NetBackup and what functions a user group can perform. This
access control is configured by using the Access Management utility. Access
Management is enabled when Symantec Product Authentication and
Authorization and NetBackup Access Control (NBAC) is installed and
configured.
For installation and configuration information, see Access Management in the
NetBackup Security and Encryption Guide.
46 Introduction
Using LiveUpdate to distribute NetBackup updates
appears by default.
When certain utilities are selected, a user toolbar appears. The buttons on the
toolbar provide shortcuts for menu commands. Slowly drag the pointer over a
To display or hide the standard NetBackup toolbar, click View > Show Toolbar.
50 Activity Monitor
Introduction to the Activity Monitor
Console, the bpjobd daemon supplies job activity status to the Activity Monitor.
Updates to the Activity Monitor occur as jobs are initiated, updated, and
Menu bar
Toolbar
Current master
server
Status bar
Details pane
Note: The Filter option on the View menu is useful for displaying in Activity
Monitor only those jobs with specified characteristics. For example, the jobs that
were started before a specific date; jobs in the queued state; jobs with status
completion codes within a specified range.
2 Click View > Column Layout. The Column Layout dialog box appears.
3 Select the heading you want to display or hide.
■ Select the Show button to display the heading.
■ Select the Hide button if you do not want to see the column head.
4 To change the order in which the columns appear, select the column head.
Then, click the Move Up button or the Move Down button to reorder the
columns.
5 Click OK to apply the changes.
3 Select Actions > Details. A Jobs Details dialog box appears for each job you
selected.
52 Activity Monitor
2 Select the job that has not completed that you would like to cancel. It may be
a job that is in the Queued, Re-Queued, Active, Incomplete, or Suspended
state.
3 Select Actions > Cancel Job. All selected jobs are canceled.
4 If the selected job is a parent job, all the children of that parent job are
canceled as well.
In most cases, a canceled child job cancels only that job and allows the other
child jobs to continue. One exception is multiple copies created as part of a
policy or storage lifecycle policy: canceling a child job cancels the parent job
and all child jobs.
5 To cancel all jobs in the jobs list that have not completed, click Actions >
Cancel All Jobs.
3 Select Actions > Restart Job. All selected jobs are restarted. In this case, a
new job ID is created for the job. The job details for the original job will
reference the job ID of the new job.
3 Select Actions > Suspend Job. All selected jobs are suspended.
Note: Only the backups and the restores that contain checkpoints can be
suspended.
Note: Only the backups and the restores that contain checkpoints can be
suspended.
■ Open the job details for a job, click the Detailed Status tab. Then click
Troubleshooter.
■ Right-click on the job. Select Troubleshooter.
4 The Troubleshooter dialog box appears. An explanation of the problem is
displayed on the Problems tab and a recommended action appears on the
Troubleshoot tab.
If there is no status code entered in the Troubleshooter status code field,
enter the status code of the failed job. Click Lookup to locate the
troubleshooting information. You can open the Troubleshooter at any time
and enter a status code.
Status bar
The status bar appears in the Jobs tab, at the top of the Activity Monitor Details
pane. The status bar displays the following information:
■ The master server on which the jobs reside.
■ The total number of jobs.
■ The number of jobs in each of the job states: Active, Queued, Waiting for
Retry, Suspended, Incomplete, and Done.
■ The number of jobs currently selected.
■ The number of NetBackup daemons that run.
The numbers always reflect the actual number of jobs, even when the filter is
used.
You may choose to receive confirmation warnings as you work in the Activity
Monitor:
■ Confirm job deletions: The user is prompted with a confirmation dialog box
when a job is deleted.
■ Confirm job cancellations: The user is prompted with a confirmation dialog
box when a job is cancelled.
■ Confirm stop daemons: The user is prompted with a confirmation dialog
box when a daemon is stopped.
To discontinue further confirmations, check In the future, do not show this
warning in the Warning dialog box.
Set the Maximum Details Windows value to limit the number of Activity Monitor
Check Auto Refresh periodically to refresh data on the Daemons tab and the
Processes tab and job details elapsed time. Other Jobs tab data is refreshed
Enter the rate (in seconds) at which data is refreshed in the Daemons and the
Processes tabs.
Click OK to close the dialog box and apply the changes after making any
changes.
56 Activity Monitor
Jobs tab
Jobs tab
The Jobs tab displays all jobs that are in process or have been completed for the
master server currently selected.
Note: Job selection preference is given to jobs from NetBackup 6.0 media servers
over media servers of previous versions.
Parent jobs
For some backup jobs, a parent job is used to perform pre- and post-processing.
Parent jobs display a dash (-) in the Schedule column. A parent job runs the start
and end notify scripts (PARENT_START_NOTIFY, PARENT_END_NOTIFY) from
the master server:
/usr/openv/netbackup/bin/
The role of the parent job is to initiate requested tasks in the form of children
jobs. The tasks vary, depending on the backup environment:
■ Snapshot Client: The parent job creates the snapshot, initiates children jobs,
and deletes the snapshot when complete.
Children jobs are created if the Snapshot Client settings are configured to
retain snapshots for Instant Recovery, then copy snapshots to a storage
unit. (Snapshots and copy snapshots to a storage unit is selected in the
policy Schedule Attributes tab.)
Children jobs are not created if the Snapshot Client settings are configured
to retain snapshots for Instant Recovery, but to create snapshots only. That
is, the snapshot is not backed up to a storage unit, so no children jobs are
generated. (Snapshots only is selected in the policy Schedule Attributes
tab.)
■ Bare Metal Restore: The parent job runs brmsavecfg, then initiates the
backup as a child job. If multistreaming and BMR are used together, the
parent job may start multiple children jobs.
■ Offline, cold catalog backups: The parent job initiates the bpbackupdb as a
child job.
■ Online, hot catalog backups: The parent job for hot catalog backups works
with bpdbm to initiate multiple children backup jobs: a Sybase backup, a file
system backup of the master, and backups of any 5.x media servers and BMR
database.
■ Multiple copies:
Activity Monitor 57
Jobs tab
A multiple copies job produces one parent job and multiple child jobs. Child
jobs that are part of a multiple copies parent job cannot be restarted
individually. Only the parent job (and subsequently all the children jobs)
can be restarted.
■ Multiple data streams: The parent job performs stream discovery and
initiates children jobs. A parent job does not display a schedule in the
Activity Monitor. Instead, a dash (-) is displayed for the schedule because the
parent schedule is not used and the children schedules may be different.
The children jobs display the ID of the parent job in the Activity Monitor.
■ SharePoint: The parent job runs a resolver process during which children
jobs are started. This process is similar to the stream discovery for multiple
data streams. If multiple data streams are enabled, some children jobs may
be split into multiple streams.
■ Vault: The parent job starts the Vault profile. Then, the Vault profile starts
the duplicates as jobs. The duplicates do not appear as children jobs in the
Activity Monitor.
Daemons tab
The Daemons tab displays the status of NetBackup daemons on the selected
master server.
Not all columns are displayed by default. Click View > Column Layout to show or
hide columns.
Daemon Description
Adaptive Server Anywhere Manages the NetBackup relational database. This service must be running on the
(NB_dbsrv) NetBackup Enterprise Media Manager server during all normal NetBackup
operations.
NetBackup Client Service Listens for connections from NetBackup servers in the network and when an
(bpinetd) authorized connection is made, starts the necessary NetBackup process to service
the connection.
This service cannot be stopped from the Activity Monitor because it receives data
that is displayed in the Administration Console. If it were stopped, the console
could not display the data.
Activity Monitor 59
Daemons tab
Daemon Description
NetBackup Compatibility Service that is used to communicate with legacy NetBackup services.
Service (bpcompatd)
NetBackup Database Manager Manages the NetBackup internal databases and catalogs. BPDBM must be running
(bpdbm) on the NetBackup master server during all normal NetBackup operations.
NetBackup Device Manager Starts the Volume Manager (vmd), the automatic volume recognition process
(ltid) (avrd), and any robotic processes. Processes the requests to mount and dismount
tapes in robotically controlled devices through the robotic control processes.
Mounts the volumes on the tape or optical storage devices in response to user
requests.
NetBackup Enterprise Media Accesses and manages the database where media and device configuration
Manager (nbemm) information is stored (EMM_DATA.db). nbemm.exe must be running in order for
jobs to run.
This service cannot be stopped from the Activity Monitor because it receives data
that is displayed in the Administration Console. If it were stopped, the console
could not display the data.
NetBackup Event Management Provides the communication infrastructure to pass information and events
Service (nbevtmgr) between distributed NetBackup components. Runs on the same system as the
NetBackup Enterprise Media Manager.
NetBackup Job Manager (nbjm) Accepts the jobs that the Policy Execution Manager (nbpem) submits and acquires
the necessary resources. The Job Manager then starts the job, and informs nbpem
that the job is completed.
NetBackup Policy Execution Compiles the worklist for jobs and determines when jobs are due to run. If a policy
Manager (nbpem) is modified or if an image expires, nbpem is notified and the worklist is
recompiled.
NetBackup Remote Manager Discovers and monitors disk storage on NetBackup media servers. Also discovers,
and Monitor Service (nbrmms) monitors, and manages Fibre Transport (FT) connections on media servers and
clients for the NetBackup SAN Client option. Runs on NetBackup media servers.
NetBackup Request Manager Processes the requests from NetBackup clients and servers. bprd also prompts
(bprd) NetBackup to perform automatically scheduled backups. bprd must be running
on the NetBackup master server to perform any backups or restores.
NetBackup Resource Broker Allocates the storage units, tape drives, and client reservations for jobs. nbrb
(nbrb) works with the Enterprise Media Manager (NBEMM).
60 Activity Monitor
Daemons tab
Daemon Description
NetBackup Service Layer Facilitates the communication between the NetBackup graphical user interface
(nbsl) and NetBackup logic. NBSL is required to run NetBackup Operations Manager
(NOM), an application that manages and monitors multiple NetBackup
environments.
This service cannot be stopped from the Activity Monitor because it receives data
that is displayed in the Administration Console. If it were stopped, the console
could not display the data.
NetBackup Service Monitor Monitors the NetBackup services that run on the local machine. If a service
(nbsvcmon) unexpectedly terminates, this service tries to restart the terminated service. If
nbsvcmon determines that NetBackup is configured for a cluster, the service
shuts down and the monitoring is taken over by the cluster.
This service cannot be stopped from the Activity Monitor because it receives data
that is displayed in the Administration Console. If it were stopped, the console
could not display the data.
NetBackup Status Collection The NetBackup Enterprise Media Manager starts the NetBackup Status Collection
Service (vmscd) service on the same host as the EMM server if one or more NetBackup 5.x servers
are present in the configuration. vmscd maintains a persistent connection with
NetBackup 5.x servers and monitors the status of drives that are attached to
NetBackup 5.x servers.
NetBackup Storage Lifecycle The NetBackup Storage Lifecycle Manager manages lifecycle operations including
Manager (nbstserv) duplication, staging, and image expiration.
NetBackup Vault Manager Manages NetBackup Vault. NBVAULT must be running on the NetBackup Vault
(nbvault) server during all NetBackup Vault operations.
NetBackup Volume Manager Manages the volumes (tapes) needed for backup or restore and starts local device
(vmd) management daemons and processes.
Activity Monitor 61
Daemons tab
Note: Symantec recommends that you exit all instances of the NetBackup-Java
Administration Console after restarting daemons in the Activity Monitor or by
using a command. Then restart the console with the jnbSA command. (The
jnbSA command is described in NetBackup Commands for UNIX and Linux.)
Service Description
Symantec Private Branch Exchange The Symantec Private Branch Exchange provides single-port access to
clients outside the firewall that connect to Symantec product services.
Service name: VRTSpbx.
Symantec Product Authentication The Symantec Product Authentication Service validates, identities, and
Service forms the basis for authorization and access control in Symantec
applications. Service name: VRTSat.
Symantec Product Authorization The Symantec Product Authorization Service provides access control in
Service Symantec applications. Service name: VRTSaz.
62 Activity Monitor
Processes tab
Processes tab
The Processes tab displays the NetBackup processes that run on the master
server.
Not all columns are displayed by default. Click View > Column Layout to show or
hide columns.
acsd 13702 The acsd (Automated Cartridge System) daemon runs on the NetBackup
media server and communicates mount and unmount requests to the host that
controls the ACS robotics.
acssel The NetBackup ACS storage server interface (SSI) event logger acssel logs
events.
acsssi The NetBackup ACS storage server interface (SSI) acsssi communicates with
the ACS library software host. acsssi processes all RPC communications from
acsd or from the ACS robotic test utility that are intended for the ACS library
software.
bmrd 8362 The process for the NetBackup Bare Metal Restore Master Server daemon.
bpcd 13782 The NetBackup Client daemon, this process issues requests to and from the
master server and the media server to start programs on remote hosts.
On UNIX clients, bpcd can only be run in stand-alone mode.
On Windows, bpcd always runs under the supervision of bpinetd.exe.
NetBackup has a specific configuration parameter for bpcd: if the port
number is changed within the NetBackup configuration, the software causes
the port number in the services file to be updated as well.
bpdbm 13721 The process for the NetBackup Database Manager daemon.
It responds to queries that are related to the NetBackup catalog.
bpjobd 13723 The NetBackup Jobs Database Management daemon, this process queries and
updates the jobs database.
bprd 13720 The process for the NetBackup Request Manager daemon.
It starts the automatic backup of clients and responds to client requests for file
restores and user backups and archives.
migrd 13699 The VSM request daemon (database request management) for Storage
Migrator. migrd handles communication for VSM-Java and commands.
nbemm The process for the NetBackup Enterprise Media Manager daemon.
It accesses and manages the database where media and device configuration
information is stored (EMM_DATA.db). nbemm.exe must be running in order
for jobs to run.
nbfdrv64 It controls the Fibre Transport target mode drivers on the media server. It runs
on media servers configured for NetBackup Fibre Transport.
nbftsrvr The Fibre Transport (FT) server process that runs on media servers configured
for NetBackup Fibre Transport. It does the following for the server side of the
FT connection: controls data flow, processes SCSI commands, manages data
buffers, and manages the target mode driver for the host bus adaptors.
64 Activity Monitor
Processes tab
nbpem The process for the NetBackup Policy Execution Manager daemon.
It compiles the worklist for jobs and determines when jobs are due to run. If a
policy is modified or if an image expires, NBPEM is notified and the worklist is
recompiled.
nbproxy This process that safely allows new multi-threaded NetBackup processes to
use existing multi-threaded unsafe libraries.
nbrb This process allocates storage units, tape drives, and client reservations for
jobs. nbrb works with the Enterprise Media Manager (NBEMM).
nbrmms The process for the NetBackup Remote Manager and Monitor service. Enables
NetBackup to remotely manage and monitor resources on a system that are
used for backup (or affected by backup activity).
nbstserv The process for the NetBackup Storage Lifecycle Manager. Manages storage
lifecycle policy operations and schedules duplication jobs. Monitors disk
capacity on capacity managed volumes and removes older images when
required.
nbsvcmon The process for the NetBackup Service Monitor. Monitors the NetBackup
services. When a service unexpectedly terminates, nbsvcmon attempts to
restart the terminated service.
nbvault If Vault is installed, the process for the NetBackup Vault Manager daemon.
ndmp 10000 NDMP is the acronym for Network Data Management Protocol. NDMP servers
are designed to adhere to this protocol and listen on port 10000 for NDMP
clients to connect to them.
odld 13706 The odld (Optical Disk Library) daemon runs on the host that has an optical
disk library. This process receives NetBackup Device Manager requests to
mount and unmount volumes and communicates these requests to the
robotics through SCSI interfaces.
Activity Monitor 65
Processes tab
oprd The NetBackup Volume Manager (vmd) starts the oprd operator request
daemon. This process receives requests to mount and unmount volumes and
communicates the requests to the NetBackup Device Manager ltid. The
NetBackup Device Manager communicates the requests to the robotics
through SCSI interfaces.
tl4d 13713 The tl4d process runs on the host that has a Tape Library 4MM. This process
receives NetBackup Device Manager requests to mount and unmount volumes
and communicates these requests to the robotics through SCSI interfaces.
tl8d 13705 The tl8d process runs on a NetBackup media server that manages a drive in a
Tape Library 8MM. This process receives NetBackup Device Manager requests
tl8cd
to mount and unmount volumes, and sends these requests to the
robotic-control process tl8cd.
The tl8cd process communicates with the TL8 robotics through SCSI
interfaces.
To share the tape library, tl8cd runs on the NetBackup server that provides
the robotic control.
tldd 13711 The tldd process runs on a NetBackup server that manages drive in a Tape
tldcd Library DLT. This process receives NetBackup Device Manager requests to
mount and unmount volumes, and sends these requests to the robotic-control
process tldcd.
The tldcd process communicates with the Tape Library DLT robotics through
SCSI interfaces.
To share the tape library, tldcd runs on the NetBackup server that provides
the robotic control.
tlhd 13717 The tlhd process runs on each NetBackup server that manages a drive in a
Tape Library Half-inch. This process receives NetBackup Device Manager
tlhcd
requests to mount and unmount volumes and sends these requests to the
robotic-control process tlhcd.
The tlhcd process runs on the NetBackup server that provides the robotic
control and communicates with the TLH robotics through SCSI interfaces.
tlmd 13716 The tlmd Tape Library Multimedia (TLM) daemon runs on a NetBackup server.
It communicates mount, unmount, and robot inventory requests to a
NetBackup media server that hosts ADIC DAS/SDLC software and controls the
TLM robotics.
tshd 13715 The tshd process runs on a NetBackup server that has a Tape Stacker
Half-inch. The tshd process receives requests to mount and unmount volumes
or for robot inventory and communicates these requests to the robotics
through SCSI interfaces.
66 Activity Monitor
Processes tab
vmd 13701 The process for the NetBackup Volume Manager daemon.
vnetd 13724 Veritas Network Daemon allows all socket communication to take place while
connecting to a single port. Legacy NetBackup services that were introduced
before NetBackup 6.0 use the vnetd port number.
vrts-auth-port 4032 The Veritas Authorization Service verifies that an identity has permission to
perform a specific task.
vrts-at-port 2821 The Veritas Authentication Service validates, identifies, and forms the basis
for authorization and access.
veritas_pbx 1556 The Symantec Private Branch Exchange allows all socket communication to
take place while connecting through a single port. NetBackup services that
were introduced in NetBackup 6.0 use the veritas_pbx port number.
When media is mounted for NetBackup jobs, errors can occur. Depending on the
type of error that is encountered, the request queues, or it is cancelled.
By default, the bpdbjobs process deletes all the done jobs that are more than
three days old. By default, the bpdbjobs process retains more recent done jobs
until the three-day retention period expires.
If the bprd NetBackup request daemon is active, bprd starts the bpdbjobs
process automatically when it performs other cleanup tasks. The process starts
the first time bprd wakes up after midnight. The automatic startups occur
regardless of whether you choose to run bpdbjobs at other times by using cron
or alternate methods.
Where 192 is the number of hours that successful jobs are kept in the jobs
database or Activity Monitor display.
Notes
■ The default values for KEEP_JOBS_SUCCESSFUL_HOURS and
KEEP_JOBS_HOURS is 78 hours.
■ The retention period values are measured against the time the job ended.
■ Information about successful jobs cannot be kept longer than information
about unsuccessful jobs. If KEEP_JOBS_SUCCESSFUL_HOURS is greater
than KEEP_JOBS_HOURS, bpdbjobs sets
KEEP_JOBS_SUCCESSFUL_HOURS to equal KEEP_JOBS_HOURS.
■ If KEEP_JOBS_SUCCESSFUL_HOURS is set to 0, bpjobd uses the
KEEP_JOBS_HOURS bpdbjobs value instead for successful jobs.
If the KEEP_JOBS_SUCCESSFUL_HOURS value is greater than 0 but less
than KEEP_JOBS_HOURS, KEEP_JOBS_HOURS is used for unsuccessful jobs
only.
Activity Monitor 69
Managing the jobs database
-clean”
/usr/openv/netbackup/bin/admincmd/bpdbjobs ${*}
The .bat file can be stored anywhere, as long as it is run from the appropriate
directory.
70 Activity Monitor
Managing the jobs database
[ -keep_successful_hours <hours> ] or
[ -keep_successful_days <days> ]
For example, the following command deletes unsuccessful jobs older than 720
hours.
bpdbjobs -clean -keep_hours 720
For a complete description of the bpdbjobs command, see NetBackup
Commands for UNIX and Linux.
Note: Before you use a debug log, read the guidelines in the Debug Logs section
of the NetBackup Troubleshooting Guide for UNIX and Windows.
72 Reports
Introduction to the Reports utility
Current master
server
Report descriptions
To run a report
1 In the NetBackup Administration Console, expand NetBackup Management
> Reports. A list of report types appears.
The report information is for the master server that is currently selected.
To run a report on a different master server, click File > Change Server.
For more information, see “To administer a remote master server” on
page 639.
2 Select the name of the report you would like to run. The right pane displays
various options for running the report.
3 Select the media servers and clients on which to run the report, then select
the time period for which the report runs.
4 Click Run Report. For a description of the report fields, see “NetBackup
report types” on page 76.
Reports 73
Reports window
Reports window
The Reports window contains multiple ways to view report listings and manage
report data.
Menu bar
Toolbar
Report
contents
Shortcut menus
To display a list of commands that apply to a list, right-click on a report.
Depending on which report is viewed, the shortcut list may include:
■ Column Layout: Opens the Column Layout dialog box where you can show or
hide columns. (By default, all columns are not displayed.)
■ Sort: Opens the Sort dialog box where you can specify sort criteria for the
columns.
■ Find: Opens the Find dialog box, used to find text within the report.
■ Filter: Use the Filter option to narrow in on specific data in a table. Use the
controls on the Filter dialog box to list the rows that match specified criteria.
■ Troubleshooter: Launch the Troubleshooter to enter a status code.
74 Reports
Reports window
Reports settings
Use the report settings to specify the following criteria for building a report. Not
all settings are available for every report type.
Date/Time range
Specify the time period that you want the report to encompass. By default, the
start time is one day before the report is run and the end time is the time the
report is run.
Select Earliest available to include the earliest possible data available.
Select Current time to include all the data until the present. For more
information, see “Keep logs” on page 383.
The Clean-up host property, Keep logs, determines the period of time for which
the information is available.
Client
Click the Client box and select All clients or select the client to which the report
applies.
Disk pool
Click the Disk Pool box and select All Disk Pools or the disk pool type to which
the report applies. The field is enabled only if OpenStorage, SharedDisk, or
AdvancedDisk disk pools exist in the configuration.
Disk type
Click the Disk Type box and select All Disk Types or the disk storage unit type to
which the report applies.
Job ID
Specify the Job ID for which you want the report.
Media ID
For media types of reports, specify the media ID or All Media. The Media
Contents report requires a specific ID.
Reports 75
Reports window
Media owner
Click the Media Owner box and select the owner of the media to which the report
applies. The NetBackup media servers and server groups in your environment
appear in the drop-down list.
Media server
Click the Media server box and select All Media Servers or the name of the
media server to which the report applies. The currently selected master server
and the media servers appear in the report.
Path
The Path selection appears for specific Disk Type selections. Specify the path to
include in the report.
Storage unit
Click the Storage unit box and select All Storage Units or the name of the
storage unit to which the report applies.
Verbose listing
Select Verbose listing to have NetBackup provide more details in the Media
Summary report.
Volume ID
If the Disk Type selection for a disk report is Array Disk, the Volume ID selection
appears. Select a Volume ID to include in the report.
Volume pool
For a media summary report, specify the volume pool name or All Volume Pools.
Run report
Click Run Report after you’ve selected the criteria for a report.
Stop report
Click Stop Report if a report is running, but you don’t want to wait for it to
finish.
76 Reports
NetBackup report types
Click Help within the Client Backups report window for a description of each
column.
Problems report
The Problems report lists the problems that the server has logged during the
specified time period. The information in this report is a subset of the
information that is obtained from the All Log Entries report.
Click Help within the Problems report window for a description of each column.
Note: The Images on Media report does not display information for the media
that is used for NetBackup offline, cold catalog backups.
Click Help within the Images on Media report window for a description of each
column.
Tape Reports
The following sections describe the six types of tape reports:
Note: The Tape Contents report does not apply to disk type storage units or
NetBackup offline, cold catalog backups.
78 Reports
NetBackup report types
Click Help within the Tape Contents report window for a description of each
column.
specified media owner according to expiration date. It also displays how many
volumes are at each retention level. In verbose mode, the report displays each
Only FROZEN expired volumes appear in the report. NetBackup deletes other
expired volumes from the media catalog when backups are run. Expired,
non-FROZEN volumes display if the report is run between the time the volumes
Click Help within the Tape Summary report window for a description of each
column.
You can then print the email or save it on a disk other than the one that
Click Help within the Tape Lists report window for a description of each column.
Disk Reports
The Disk Reports pertain to the information available about the images that are
Click Help within the Disk Pool Status report window for a description of each
column.
82 Policies
Using the Policies utility
Menu bar
Standard toolbar
User toolbar
Current master
server
Tree view
Select a subnode from Summary of All Policies to display Inactive policies Details pane
all possible node attributes in the right pane. For example, appear in gray
Schedules displays a list of all schedules.
simplifies the process as it automatically chooses the values that are good for
most configurations.
Note: If the schedule is to be used for a catalog archive, the policy must be
named catarc. For more information on how to configure a policy to archive the
catalog, see “Creating a catalog archiving policy” on page 319.
84 Policies
Changing policies
Changing policies
Change policies only when no backup activity is expected for the affected
policies and clients. Make adjustments before backups begin to ensure an
orderly transition from one configuration to another.
■ To add a new client, select Actions > New > Client. The Add Client
dialog appears.
■ To change an existing client, double-click the client name in the Details
pane. The Change Client dialog appears.
4 Complete the entries in the Add Client or Change Client dialog.
For more information, see “To add a client to a policy” on page 159.
Note: To configure a Vault policy, see “To create a Vault policy” on page 199.
Selections dialog.
For information on how to specify file paths for clients, see “Rules to
86 Policies
Changing policies
Note: When a client is deleted from the client list, the NetBackup client software
is not deleted or uninstalled from the client. Backups for the client can be
recovered until the backups expire.
Also, when a file is deleted from a backup selection list, the actual file is not
deleted from the client.
Policies 87
Policy Attributes tab
The settings on the Attributes tab determine the characteristics of all the
backups that NetBackup performs according to the selected policy.
The following items are a few of the attributes that are defined on the Policy
Attributes tab:
■ Whether the selected policy is currently active or what date and time the
policy goes into effect.
■ The type of backup policy, which primarily defines the type of clients the
policy backs up.
■ The priority that NetBackup gives to the backups for the selected policy
relative to other policies.
■ The storage unit that NetBackup uses to back up the clients in the selected
policy.
■ Snapshot Client attributes, if Snapshot Client is installed.
88 Policies
The following sections describe the settings on the Attributes tab. Policy
attributes are configurable depending on the type of policy and the options that
are installed.
Policy type
The Policy type attribute determines the purpose of the policy. Usually, the
Policy type determines the type of clients that can be backed up by this policy.
Not all policy types serve to back up up clients. (NBU-Catalog, for example.)
Select the type of policy from the drop-down list.
The Policy type of an existing policy may be changed. However, the existing
schedules may become invalid for the new policy type. If the schedules become
Policies 89
Policy Attributes tab
invalid, NetBackup displays an alert notice. NetBackup then either deletes the
invalid schedules or changes the schedules to an equivalent type.
DataStore A policy type that is reserved for use by Symantec or its partners to provide agents for
new applications or databases.
DB2 Use for the policies that contain only clients with the NetBackup for DB2 option. For
information on setting up this policy type, see the guide for this option.
Lotus-Notes Use for the policies that contain only clients with the NetBackup for Lotus Notes option.
For information on setting up this policy type, see the guide for this option.
MS-Exchange-Server Use for the policies that contain only clients with the NetBackup for MS-Exchange option.
For information on setting up this policy type, see the guide for this option.
MS-SQL-Server Use for the policies that contain only clients with the NetBackup for MS-SQL Server
option. For information on setting up this policy type, see the guide for this option.
MS-Windows-NT* Use for the policies that contain only Windows 2000, XP, Windows Server 2003, or
NetBackup 5.x NT clients.
NBU-Catalog Use for hot catalog backup jobs. Allows for a catalog backup while other jobs are running.
NCR-Teradata Use for the policies that contain only clients with the NetBackup for Teradata option. For
information on setting up this policy type, see the guide for this option.
NDMP Use for the policies that contain only clients with the NetBackup for NDMP option. This
policy type is available only when the NetBackup NDMP is installed and licensed. For
information on setting up this policy type, see the guide for this option.
NetWare Use for the policies that contain only NonTarget NetBackup Novell NetWare clients (this
version uses a Microsoft Windows interface).
Oracle Use for the policies that contain only clients with the NetBackup for Oracle option. For
information on setting up this policy type, see the guide for this option.
Standard* Use for the policies that contain any combination of the following:
■ UNIX clients (including Mac OS X clients), except those covered by specific such as
Oracle.
■ NetBackup Novell NetWare clients that have the target version of NetBackup
software.
Vault Use as a policy type to schedule and run a Vault job. Available only when Vault is licensed.
AFS Use for the policies that back up only AFS file systems on clients.
See “Using NetBackup with AFS,” in the NetBackup Administrator’s Guide, Volume II for
information on setting up these policies.
DataTools-SQL- Use for the policies that contain only clients with the NetBackup for
BackTrack DataTools-SQL-BackTrack option. For information on setting up this policy type, see the
guide for this option.
Informix-On-BAR Use for the policies that contain only clients with the NetBackup for Informix option. For
information on setting up this policy type, see the guide for this option.
MS-SharePoint Use to configure a policy for NetBackup for SharePoint Portal Server.
SAP Use for the policies that contain only clients with the NetBackup for SAP option. For
information on setting up this policy type, see the guide for this option.
Sybase Use for the policies that contain only clients with the NetBackup for Sybase option. For
information on setting up this policy type, see the guide for this option.
* Use the Standard or MS-Windows-NT policy to implement the following options: CheckPoint Restart for backups,
Checkpoint Restart for restores, synthetic backups, or the Collect disaster recovery information for Bare Metal
Restore option.
For more details on off-host backups, refer to the NetBackup Snapshot Client
Administrator’s Guide.
Data classification
Select a Data Classification if you want the backup to go to a storage unit that
stores backups of a particular classification. For example, a gold backup must go
to a storage unit with a gold data classification.
Policies 91
Policy Attributes tab
policy uses the storage units and groups that the Policy storage attribute
indicates.
If a data classification is selected, all the images that the policy creates are
Policy storage
The Policy storage attribute specifies the storage destination for the policy’s
data. Select the storage destination from the drop-down list. If configured, the
drop-down list may contain storage units, storage lifecycle policies, and storage
unit groups.
If configured to do so, the selection of a storage unit or a storage lifecycle policy
determines which type of disk staging is used for this policy. (See “Staging
backups to initial storage, then final storage” on page 242.)
The list includes only those lifecycles that are of the same data classification as
the policy. For example, gold backup images cannot be sent to a silver storage
lifecycle.
Images that belong to a specific data classification cannot be sent to a storage
lifecycle that does not have a classification. To select a data classification is
optional.
If Any Available is selected, NetBackup tries to store data on locally-attached
storage units first. To force NetBackup to use only a locally-attached drive,
select Must use local drive on the General Server Properties. (See “Must use
local drive” on page 432.)
If a local device is not found or if the Must use local drive attribute is not
selected, NetBackup tries to find an available storage unit alphabetically.
If Any Available is selected, NetBackup uses the first storage unit that meets the
following requirements:
■ The storage unit must not be designated as On Demand Only
■ The storage unit must have available drives
■ The storage unit must have media available in the required volume pool
An exception is the case in which a client is also a media server with
locally-attached storage units. The local storage units take precedence over the
sequence that is based on alphabetical order.
The storage unit that is selected on the Schedule tab, overrides the Policy
storage attribute. (See “Override policy storage selection” on page 137.)
92 Policies
Note: If the Scratch pool option is enabled for the volume pool, any
storage unit has access to the volumes in the volume pool. For this
method to work, do not enable Scratch pool for the volume pool.
b In the policy, set Policy volume pool to the volume pool that is defined
in the previous step.
c For all policies, set Policy storage attribute to Any Available.
■ A policy may specify a storage unit group. Make sure that one of the storage
units within the group is set to On Demand Only to satisfy the policy
requirement.
■ Online catalog backups must use media servers at version 6.0 or later to
store catalog backup data. If the installation contains 5.x media servers
hosting disk storage units, do not select Any Available for the destination
Policy storage attribute. The 5.x media server may be selected and the
backup would fail.
backups for the policy are stored. A volume pool is a group of media that is
grouped together for use by a single application. The volume pool is protected
Select a volume pool name from the list of volume pools. Whenever a new
The volume pool that is selected on the Schedule tab overrides the Policy volume
■ None: The default pool for applications, other than NetBackup and Storage
Migrator.
■ DataStore: The default pool for DataStore.
■ NetBackup: Unless otherwise specified in the policy, all backups use media
from the NetBackup pool. One exception is the NBU-Catalog policy type
(used for online, hot catalog backups) that selects the CatalogBackup volume
pool by default. Offline, cold catalog backups use media from the NetBackup
volume pool.
■ CatalogBackup: This pool is selected by default for the NBU-Catalog policy
type. It is used exclusively for online, hot catalog backups. Online, hot
catalogs are directed to a single, dedicated pool to facilitate faster catalog
restores.
Additional volume pools can be useful. Possible additional volume pools include
the following:
■ A Scratch pool from which NetBackup can automatically transfer volumes
when another volume pool does not have media available.
■ An Auto volume pool, for use by automatic backups.
■ A User volume pool, for use by user backups.
Media is assigned to the volume pools for Media Manager storage devices.
Disk-type storage devices are not allocated to a volume pool. For information
about how to create volume pools and how to add media to them, see “Volume
94 Policies
Policy Attributes tab
Note: Although NetWare clients can use the Standard policy type, checkpoint
restart for backups is not supported on NetWare clients.
Checkpoint frequency
The checkpoint frequency indicates how often NetBackup takes a checkpoint
during a backup. (Default: 15 minutes.) The administrator determines
checkpoint frequency on a policy-by-policy basis. Balance more frequent
checkpoints with the likelihood of time that is lost when a backup is resumed. If
the frequency of checkpoints impacts performance, increase the time between
checkpoints.
Client A and Client B backups can occur concurrently and back up to different devices
job and children jobs: multistreamed jobs, catalog backups, Snapshot Client
snapshots, or Bare Metal Restore jobs. (See “Parent jobs” on page 56.)
■ The number of storage devices available and multiplexing limits. To process
more than one backup job at a time, the configuration must include one of
the following:
■ Multiple storage units.
■ A storage unit with enough drives to perform more than one backup at
a time.
■ Storage units that are configured to multiplex.
concurrent jobs depends on the total number of drives in the storage units.
With disk storage, the storage device is defined as a file path and the
■ The server speed. Too many concurrent backups interfere with the
performance of the server. The best number depends on the hardware,
operating system, and applications that are running.
■ The network load. The available bandwidth of the network determines how
many backups can occur concurrently. If you encounter loading problems,
consider multiple networks for backups.
Or, configure the backup policy to use Compression. (See “Compression” on
page 105.)
When the client that is backed up is also a server, it is a special case. In this
instance, the network load is not a factor because the network is not used.
The load on the client and server, however, is still a factor.
■ Multiplexing. If multiplexing is used, set Limit jobs per policy high enough
to support the specified level of multiplexing.
Lower values can limit multiplexing within a policy if jobs from different
schedules exist within the policy. For example, Limit jobs per policy is set to
two and an incremental backup schedule is due to run for four clients. Only
two clients are backed up at one time, regardless of the multiplexing
settings.
Job priority
The Job priority attribute specifies the priority that a policy has it competes
with other policies for backup resources. To have a higher priority means that
NetBackup assigns the first available drive to the first client in the policy with
the highest priority.
Policies 99
Policy Attributes tab
To set the priority, enter a number in the Job priority field (maximum 99999).
The default for all policies is 0, the lowest priority possible. Any policy with a
priority greater than zero has priority over the default setting.
Media owner
Active only for Media Manager type storage units or if the Policy storage attribute
is Any Available.
The Media Owner property specifies which media server or server group should
own the media on which backup images for this policy are written.
Note: Mapped drive letters cannot be backed up. Drive letters do not appear in
the Backup, Archive, and Restore console when backups are browsed.
4 To run a user backup, expand the Network node in the Backup, Archive, and
Restore client interface to win_PC. Select TestData.
5 Backups run as scheduled or when a manual backup is performed.
Follow NFS
The Follow NFS attribute specifies whether NetBackup is 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.
102 Policies
Policy Attributes tab
Note: The Follow NFS attribute applies only to UNIX clients in certain policy
types. NetBackup allows it to be selected in those instances only.
Note: If Follow NFS is not selected, the backup process reads the client’s mount
table and evaluates each item in the table. NetBackup resolves any links to the
true path. NetBackup must resolve the links so it can accurately avoid backing
up any files that reside on NFS-mounted file systems.
If NetBackup cannot access a Network File System when it evaluates the mount
table, it assumes that the file system is unavailable. (The default time to access
the file system is five seconds.)
To change the default, change the UNIX master server host property, NFS
access timeout. (See “NFS access timeout” on page 483.)
Disabled Enabled Back up NFS files if the file path is (or is part of) an NFS mount.
Enabled Disabled Cross local mount points but not NFS mounts.
Enabled Enabled Follow the specified path across mount points to back up files and
directories (including NFS), regardless of the file system where
they reside.
Note: NetBackup specifically excludes mapped directories even if Follow NFS and Cross mount points are enabled.
To back up mapped directories, include the directories in the file list.
/(root)
/usr
/home /net
/home/njr /net/freddie
/net/freddie/home
d1
NFS
Disks on d2 d3 Disk on
Local System Remote System
Here, the client contains /, /usr, and /home in separate partitions on disk d1.
Another file system named /home/njr exists on disk d2 and is mounted on
/home. In addition, disk d3 contains a directory named /net/freddie/home
that is NFS-mounted on /net/freddie.
Example 1
Assume that Cross mount points and Follow NFS are not selected. Assume that
the backup selection list contains the following entries:
/
/usr
/home
NetBackup considers only the directories and files that are in the same file
system as the backup selection list entry it is processes. It does not back up
/home/njr or /net/freddie/home.
Example 2
Assume that Cross mount points and Follow NFS are selected. Assume that the
backup selection list contains only / .
In this case, NetBackup backs up all the files and directories in the tree,
including those under /home/njr and /net/freddie/home.
To back up only /usr and individual files under /, leave / out of the list and
separately list the files and directories you want to include. For example:
/usr
/individual_files_under_root
Compression
The Compression attribute specifies that the backups use the software
compression that is based on the policy. Select the check box to enable
compression. (Default: no compression.)
106 Policies
Policy Attributes tab
Note: When compression is not used, the server may receive more data than
what exists on the client. The discrepancy is due to client disk fragmentation
and the file headers that the client adds. (To tell how much space a file occupies,
run the du command. To tell how much free disk space is available, run the df
command.)
Data types that Programs, ASCII files, and unstripped binaries (typically 40% of the original size).
compress well:
Policies 107
Policy Attributes tab
Best-case compression: Files that are composed of the strings that repeat can sometimes be compressed to 1%
of their original size.
Data types that do not Stripped binaries (usually 60% of original size).
compress well:
Worst-case Files that are already compressed become slightly larger if compressed again. On UNIX
compression: clients, if a compressed file has a unique file extension, exclude it from compression by
adding it under the UNIX Client host properties. (See “Do not compress files ending
with” on page 401.)
Effect of file size: File size has no effect on the amount of compression. However, it takes longer to
compress many small files than a single large one.
Client resources that are Compression requires client computer processing unit time and as much memory as the
required: administrator configures.
Effect on client speed: Compression uses as much of the computer processing unit as available and affects
other applications that require the computer processing unit. For fast CPUs, however,
I/O rather than CPU speed is the limiting factor.
Files that are not NetBackup does not compress the following files:
compressed: ■ Files that are equal to or less than 512 bytes, because that is the tar block size.
■ On UNIX clients, the files that end with suffixes specified with the
COMPRESS_SUFFIX =.suffix option in the bp.conf file.
■ On UNIX clients, files with the following suffixes:
Encryption
The Encryption attribute determines whether the backup should be encrypted.
When the server initiates the backup, it passes on the Encryption policy
attribute to the client in the backup request.
108 Policies
Policy Attributes tab
The client compares the Encryption policy attribute to the Encryption host
properties for the client. If the encryption permissions for the client are set to
REQUIRED or ALLOWED, the policy can encrypt the backups for that client.
(See “Encryption properties” on page 409.)
For additional encryption configuration information, see the NetBackup
Security and Encryption Guide.
Note: If encrypted data is written to a storage unit that has single-instance store
(SIS) capabilities, the storage unit may not be able to use data deduplication on
the compressed or the encrypted data.
Note: Some options require that Collect true image restore information with
move detection be enabled:
- It must be enabled to create synthetic backups. (See “Synthetic backup” on
page 128.)
- It must be enabled to back up data to the NearStore disk storage units that use
the File System Export option. (See “Enable file system export” on page 752.)
The following examples show how move detection backs up the files that
otherwise would not be backed up:
110 Policies
12/04/2007 User backup file1 file2 dirA/fileA ------------- ------ dirC/fileC file4
Note: Dashes ( ------ ) indicate that the file was deleted before this backup.
■ After a regular restore, the restored directory contains all files and
directories that ever existed in /home/abc/doc/ from 12/01/2007 (last full
backup) through 12/04/2007:
file1
file2
dirA/fileA
dirB/fileB
file3
dirC/fileC
file4
■ A true image restore of the 12/04/2007 backup creates a directory that
contains only the files and directories that existed at the time of the
incremental backup (12/04/2007):
file1
file2
file4
NetBackup does not restore any of the files that were deleted before the
12/04/2007 incremental backup.
The restored directory does not include the dirA and dirC subdirectories,
even though they were backed up on 12/04/2007 with a user backup.
NetBackup did not restore these directories because they did not exist at the
time of the incremental backup. The incremental backup was the reference
for the true image restore.
■ A true image restore preserves the files that are currently in the directory
but were not present when the backup was completed. In the previous
example, assume that you created a file named file5 after the incremental
backup occurred on 12/04/2007, but before the restore. In this case, the
contents of the directory after the restore is:
file1
file2
file4
file5
Note: If this attribute is enabled, and a file system is in a client’s exclude list, a
NetBackup job appears in the Activity Monitor for the excluded file system.
However, no files in the excluded file system are backed up by the job.
Policies 113
Policy Attributes tab
Note: For best performance, use only one data stream to back up each physical
device on the client. Multiple concurrent streams from a single physical device
can adversely affect backup times. The heads must move back and forth between
tracks containing files for the respective streams.
Client
Back up each device with a
Stream separate stream that runs
Drive A
concurrently with streams
NetBackup from other devices. Then,
Server multiplex the streams or send
Stream them to separate tapes.
Drive B
Not recommended
Client
Stream
Multiple concurrent
Drive A streams from a single
Stream device can adversely affect
NetBackup backup times.
Stream Server
Drive B Stream
For example, assume the backup for a 10-gigabyte partition is split into 5
streams, each containing 2 gigabytes. If the last stream fails after writing 1.9
gigabytes (a total of 9.9 gigabytes is backed up), NetBackup retries only the last
gigabyte stream. If the 10-gigabyte partition is backed up without multiple data
streams and a failure occurs, the entire 10-gigabyte backup must be retried.
The Schedule backup attempts property in the Global Attributes properties,
applies to each stream. For example, if the Schedule backup attempts property
is set to 3, NetBackup retries each stream a maximum of three times.
(See “Schedule backup attempts” on page 435.)
The Activity Monitor displays each stream as a separate job. Use the job details
view to determine the files that are backed up by each of these jobs.
Note: For best performance, use only one data stream to back up each physical
device on the client. Multiple concurrent streams from a single physical device
can adversely affect backup times. Backup times are affected because the device
heads must move between tracks containing files for the respective streams.
unit. The maximum streams are limited to the sum of the multiplexing
limits for all drives available in the storage unit and schedule combinations.
For example, assume that two storage units have one drive in each.
Multiplexing on storage unit 1 is set to 3 and multiplexing on storage
unit 2 is set to 5. If multiplexing is set to 5 or greater in the schedules,
then 8 streams can run concurrently.
The maximum jobs settings also limit the maximum number of streams:
■ Maximum jobs per client (Host Properties > Master Servers > Global
Attributes.) (See “Maximum jobs per client” on page 436.)
■ Limit jobs per policy (policy attribute).
■ Maximum data streams (use Host Properties > Master Servers > Client
Attributes or the bpclient command -max_jobs option).
(See “Maximum data streams” on page 387.)
The maximum job settings are interdependent as follows:
■ If Maximum data streams is not set, the limit is either Maximum jobs
per client or Limit jobs per policy, whichever is lower.
■ If Maximum data streams is set, NetBackup ignores Maximum jobs per
client. Instead, NetBackup uses either Maximum data streams or Limit
jobs per policy, whichever is lower.
To specify a value for Maximum data streams with the bpclient
command:
a Determine if the client is in the client database on the master server by
running the following command on one line:
/usr/openv/netbackup/bin/admincmd/bpclient -client
name -L
b If the client is not in the client database, run the following command on
the master server on one line:
/usr/openv/netbackup/bin/admincmd/bpclient -client
c If the client is in the client database, run the following command on one
line:
/usr/openv/netbackup/bin/admincmd/bpclient -client
files on NetBackup 6.5 clients.) For more information, see the NetBackup for
Microsoft SharePoint Portal Server 2003 Administrator’s Guide.
Document-level restores can be performed only if the backup was written to a
disk storage unit.
Keyword phrase
The Keyword phrase attribute is a phrase that NetBackup associates with all
backups or archives based on the policy.
Note: Only the Windows and UNIX client interfaces support keyword phrases.
You can use the same keyword phrase for more than one policy. The same
phrase for multiple policies makes it possible to link backups from related
policies. For example, use the keyword phrase legal department documents, for
backups of multiple clients that require separate policies, but contain similar
types of data.
The phrase can be a maximum of 128 characters in length. All printable
characters are permitted including spaces and periods. (Default: no keyword
phrase.)
Clients can also specify a keyword phrase for a user backup or archive. A user
keyword phrase overrides the policy phrase.
For more information see the NetBackup Snapshot Client Administrator’s Guide.
Policies 117
Schedules tab
Schedules tab
The schedules that are defined on the Schedules tab determine when backups
occur for the policy that is selected. Each schedule also includes various criteria,
such as how long to retain the backups.
NetBackup has two categories of schedules:
■ Automatic schedules back up the items that are listed in the backup selection
list on all clients in the policy. The items are backed up according to the
timetables that are set up in the schedules.
■ User schedules specify the times when users can start user backups and
archives from the clients. A user archive is a special type of backup that
deletes the files from the user disk if the backup is successful. An archive is
useful to free disk space while keeping a copy for future use.
Note: For more information on how to change existing policies, see “To add or
change schedules in a policy” on page 84.
Name
Specify a name for the schedule by typing it in the Name field. For more
information, see “NetBackup naming conventions” on page 631.
Policies 119
Schedule Attributes tab
The schedule name appears on screens and messages about the schedule.
storage unit, the schedule name cannot be changed. The name defaults to the
For more information on basic disk staging storage units, see “Staging backups
Type of backup
The Type of backup specifies the type of backup that the schedule controls.
Select a backup type from the drop-down list. The list displays only the backup
Full backup
A full backup backs up all of the files that are specified in the backup selections
list for the policy. The files are backed up, regardless of when the files were last
modified or backed up. Full backups occur automatically according to schedule
criteria. If you run incremental backups, you must also schedule a full backup to
perform a complete restore. If you configure a policy for a raw partition backup
(formatted partitions only), select Full Backup.
120 Policies
Schedule Attributes tab
User backup
A user initiates a user backup through the Backup, Archive, and Restore client
interface. A user backup backs up all files that the user specifies. Users can start
backups only during the times that are allowed on the schedule Start Window
tab.
If the schedule is to be used for a catalog archive, User Backup must be selected
for the backup type. For more information on how to configure a policy to
archive the catalog, see “Creating a catalog archiving policy” on page 319.
User archive
A user initiates a user archive through the Backup, Archive, and Restore client
interface. A user archive backup first backs up the files that the user indicates.
Then it deletes the files from the local disk if the backup is successful. Archive
backups free local disk space while retaining a copy for future use. The copy is
kept until the retention period expires. Users can start archives only during the
times that are specified in the schedule Start Window tab.
Policies 121
Schedule Attributes tab
Caution: The NetBackup administrator should make sure that a full backup of
the client exists before a user is allowed to archive files from the client.
Application backup
An application backup is a backup type that applies to all database agent clients.
For more information on how to configure schedules for this type of backup, see
the NetBackup guide that came with the product.
Automatic backup
An automatic backup is a backup type for all database agent clients, except
NetBackup for Informix and Oracle. For more information on how to configure
schedules for this type of backup, see the NetBackup guide for the database
product.
Automatic Vault
An automatic Vault session applies only to Vault policies. The option does not
run a backup, but instead runs the command that is specified in the Vault
policy’s backup selections list. In this way it starts an automatic, scheduled vault
session or vault eject operation. Available only when Vault is licensed.
For more information on how to configure a Vault policy, see “Creating a Vault
policy” on page 199.
If the schedule is a Vault Catalog Backup type, one of two schedule attribute
Note: The selected storage unit selection should not be Any Available.
Full backup
Diff. incremental
Diff. incremental
Diff. incremental
The January 1 full backup includes all files and directories in the policy backup
selections list. The subsequent differential incremental backups include only
Policies 123
Schedule Attributes tab
the data that changed since the last full or differential incremental backup. If
the disk fails sometime on January 4 (after the backup), the full backup and all
three of the incremental backups are required for the recovery.
Full backup
Cum. incremental
Cumulative incremental
Cumulative incremental
Table 4-5 Retention requirements for differential and cumulative incremental backups
Differential Longer To restore all files requires the last full backup and all the differential incremental
backups that have occurred since the last full backup. Therefore, all the
differentials must be kept until the next full backup occurs.
Cumulative Shorter Each cumulative incremental backup contains all the changes that have occurred
since the last full backup. Therefore, a complete restore requires only the most
recent cumulative incremental in addition to the full backup.
Table 4-6 Relative backup and restore times for differential and cumulative incremental backups
Differential Shorter Longer Less data in each backup, but all differential incremental
backups are required since the last full backup for a restore.
This results in a longer restore time.
124 Policies
Table 4-6 Relative backup and restore times for differential and cumulative incremental backups
Cumulative Longer Shorter More data in each backup, but only the last cumulative
incremental is required for a complete restore (in addition to
the full).
Synthetic backup
A synthetic full or synthetic cumulative incremental backup is a backup
assembled from previous backups. The backups include one previous,
traditional full backup, and subsequent differential backups and/or a
cumulative incremental backup. (A traditional full backup means a
non-synthesized, full backup.) A client can then use the synthesized backup to
restore files and directories in the same way that a client restores from a
traditional backup.
Synthetic backups can be written to tape or to disk storage units, or a
combination of both. For more information on synthetic backups, see “More
about synthetic backups” on page 201.
Note: A policy can contain more than one schedule. Symantec recommends,
however, that calendar-based and frequency-based schedule types are not mixed
within the same policy. Under some conditions, schedule types that are
combined in one policy can cause unexpected results.
For details on how calendar-based scheduling works with time windows, see
“How calendar scheduling interacts with daily windows” on page 149.
For example, assume that a schedule is set up for a full backup with a frequency
of one week. If NetBackup successfully completes a full backup for all clients on
Monday, it does not attempt another backup for this schedule until the following
Monday.
A frequency-based relocation schedule determines how often images are swept
from the basic disk staging storage unit to the final destination storage unit. (A
relocation schedule is created as part of a basic disk staging storage unit
configuration.)
To set the frequency, select a frequency value from the drop-down list. Select a
Frequency of hours, days, or weeks.
Note: Frequency does not apply to user schedules because the user can perform
a backup or archive whenever the time window is open.
Note: A policy can contain more than one schedule. Symantec recommends,
however, that calendar-based and frequency-based schedule types are not mixed
within the same policy. Under some conditions, schedule types that are
combined in one policy can cause unexpected results.
■ Shorter the time between full backups for the files that change frequently. A
shorter frequency decreases restore time. A shorter time between full
backups can also use fewer resources: it reduces the cumulative effect of the
longer incremental backups that are necessary to keep up with frequent
changes in the files.
To achieve the most efficient use of resources, ensure that most of the files in a
given policy change at about the same rate. For example, assume that half of the
files in a policy selection list change frequently enough to require a full backup
every week. However, the remaining files seldom change and require monthly
full backups only. If all the files are in the same policy, full backups are
performed weekly on all the files. This wastes system resources because half the
files need full backups only once a month. A better approach is to divide the
backups into two policies, each with the appropriate backup schedule, or to use
synthetic backups.
Instant recovery
The Instant recovery options are available under the following conditions:
■ The Snapshot Client option is licensed and installed. Refer to the NetBackup
Snapshot Client Administrator’s Guide.
■ Perform snapshot backups is selected.
■ Retain snapshots for Instant Recovery is selected.
Snapshots only
With this attribute is enabled, the snapshot is not backed up to tape or to other
storage. NetBackup creates a snapshot on disk only. This option is required for
the NAS_Snapshot method.
The snapshot is created on the same device as the one that contains the original
data if it uses VxFS_Checkpoint method or is vxvm space-optimized. In this case,
another policy can be used to back up the data to a separate device.
With this attribute enabled, transaction logs are not be truncated at the end of
the backup.
Multiple copies
With the Multiple copies attribute enabled, NetBackup can create up to four
copies of a backup simultaneously. The storage units must be on the same media
server with sufficient resources available for each copy. For example, to create
four copies simultaneously in a Media Manager storage unit, the unit needs four
tape drives. (This option is sometimes referred to as Inline Copy.)
The Maximum backup copies property specifies the total number of backup
copies that may exist in the NetBackup catalog (2 through 10). NetBackup
creates the number of copies that is specified under Multiple copies, or the
number that the Maximum backup copies property specifies, whichever is
fewer. For more information, see “Maximum backup copies” on page 437.
To create more than four copies, additional copies may be created at a later time
using duplication.
The storage units that are used for multiple copies must be configured to allow a
sufficient number of concurrent jobs to support the concurrent copies. (The
pertinent storage unit settings are Maximum concurrent jobs and Maximum
concurrent write drives.)
132 Policies
Schedule Attributes tab
If multiple original images are created simultaneously, the backup time that is
required may be longer than for one copy. Also, if both Media Manager and disk
storage units are specified, the duration of disk write operations match that of
slower removable media write operations.
Note: The Multiple copies option does not support the following storage types:
third-party copies or optical devices. Also, Multiple copies does not support the
storage units that use a QIC (quarter-inch cartridge) drive type.
4 In the Attributes tab, select Multiple copies, then click Configure. The
Note: The Multiple Copies option may not be enabled for selection. It may
be disabled if the destination for this policy is a storage lifecycle policy. (The
destination selection is on the policy Attributes tab.) If the lifecycle has
multiple destinations configured, that implies a multiple copies operation.
NetBackup does not allow the two methods for created multiple copies to be
enabled at the same time.
Copy 1 is the primary copy. If Copy 1 fails, the first successful copy is the
primary copy.
6 Specify the priority that the duplication job has compared to other jobs in
the queue (0 to 99999).
7 Specify the storage unit where each copy is stored. Select Any_Available to
allow NetBackup to select the storage unit at runtime.
If a Media Manager storage unit contains multiple drives, the storage unit
can be used for both the original image and the copies.
8 Specify the volume pool where each copy is stored.
9 Select the retention level for each copy. For more information, see
“Retention” on page 138.
10 Select what should happen to the copy in the event that the copy does not
complete. Select whether the entire job should fail (fail all copies), or
whether the remaining copies should continue.
If a copy is configured to allow other copies to continue, and if Checkpoint
restart is selected for this policy, only the last failed copy that contains a
checkpoint can be resumed.
11 For tape media, specify who should own the media onto which NetBackup
writes the images:
Policies 135
Schedule Attributes tab
■ Any lets NetBackup choose the media owner, either a media server or
server group.
■ None specifies that the media server that writes to the media owns the
media. No media server is specified explicitly, but you want a media
server to own the media.
■ A server group. Specifying a media server group allows only those
media servers in the group to write to the media on which backup
images for this policy are written. All media server groups configured
in the NetBackup environment appear in the drop-down list.
Note: These settings do not affect images residing on disk. Images on shared
disk are not owned by any one media server. Any media server with access
to the shared pool of disk can access the images.
For example, to create four copies in the Multiple Copies dialog, the
For more information, see “Multiple copies and disk staging storage units”
on page 132.
8 Specify the storage unit where each copy is stored. If a Media Manager
storage unit has multiple drives, it can be used for both the source and the
destination.
9 Specify the volume pool where each copy is stored.
10 Select the retention level for each copy. For more information, see
“Retention” on page 138.
11 Select what should happen in the event that the copy does not complete.
Select whether the entire job should fail, or whether the remaining copies
should continue. Click OK.
If:
■ a copy is configured to allow other copies to continue, and
■ Checkpoint restart is selected for this policy, then
only the last failed copy that contains a checkpoint can be resumed.
12 For tape media, specify who should own the media onto which NetBackup
writes the images:
■ Any lets NetBackup choose the media owner, either a media server or
server group.
■ None specifies that the media server that writes to the media owns the
media. No media server is specified explicitly, but you want a media
server to own the media.
■ A server group. Specifying a media server group allows only those
media servers in the group to write to the media on which backup
images for this policy are written. All media server groups configured
in the NetBackup environment appear in the drop-down list.
Note: These settings do not affect images residing on disk. Images on shared
disk are not owned by any one media server. Any media server with access
to the shared pool of disk can access the images.
Note: Storage lifecycle policies cannot be selected within the multiple copies
configuration dialog.
■ Any lets NetBackup choose the media owner. NetBackup chooses a media
server or a server group (if one is configured).
■ None specifies that the media server that writes the image to the media
owns the media. No media server is specified explicitly, but you want a
media server to own the media.
■ A server group. A server group allows only those servers in the group to
write to the media on which backup images for this policy are written. All
server groups that are configured in the NetBackup environment appear in
the drop-down list.
To override the media owner that the Media Owner General Attribute specifies,
select the check box. Choose the media owner from the drop-down list
To use the policy media owner, do not select the check box. NetBackup uses the
media owner that is specified in the Media Owner General Attribute.
Retention
The Retention attribute specifies how long NetBackup retains the backups. To
set the retention period, select a time period (or level) from the drop-down list.
When the retention period expires, NetBackup deletes information about the
expired backup. Once the backup expires, the files in the backup are unavailable
for restores. For example, if the retention is two weeks, data can be restored
from a backup that this schedule performs for only two weeks after the backup.
If a policy is configured to back up to a lifecycle, the Retention attribute in the
schedule is not followed. The retention indicated in the lifecycle is followed
instead. (See “Adding storage destinations to a lifecycle policy” on page 255.)
outside of the retention requirement guidelines. For example, place the files and
directories with longer retention requirements in a separate. Schedule longer
retention times for the separate policies without keeping all policies for the
longer retention period.
Another consideration for data retention is off-site storage of the backup media.
Off-site storage protects against the disasters that occur at the primary site. Set
the retention period to infinite for the backups that must be kept for more than
one year.
■ One method to implement off-site disaster recovery is to use the duplication
feature to make a second copy for off-site storage.
■ Another approach is to send monthly or weekly full backups to an off-site
storage facility. To restore the data, request the media from the facility.
(Note that a total directory or disk restore with incremental backups
requires the last full backup plus all incremental backups.)
■ Consider configuring an extra set of schedules to create the backups to use
as duplicates for off-site storage.
Ensure that adequate retention periods are configured, regardless of the method
that is used for off-site storage. Use the NetBackup import feature to retrieve
expired backups.
■ NetBackup does not track backups after the retention period expires. Assign
an adequate retention period as recovering files after the retention period
expires is difficult or impossible.
■ Within a policy, assign a longer retention period to full backups than to
incremental backups. It may not be possible to restore all the files if the full
backup expires before the incremental backups.
■ Archive schedules normally use an infinite retention period.
■ For WORM (write once, read many) optical platters, or tape, set the retention
to infinite. If infinite is unacceptable because of NetBackup database space
limitations, set the retention period to match the length of time that the
data is to be retained. For the retention periods that are less than infinite,
delete the WORM media from the Media Manager configuration upon
expiration. If not deleted, Media Manager reallocates the media for future
backups. (The media is reallocated, even though WORM can be written only
once.)
If you keep only one retention level on each volume, do not use any more
retention levels than necessary. Multiple retention levels increase the number
of required volumes. For more information, see “Media properties” on page 446.
Media multiplexing
The Media multiplexing attribute specifies the number of jobs from the schedule
that NetBackup can multiplex onto any one drive. Multiplexing sends
concurrent backup jobs from one or several clients to a single drive and
Note: Some policy or some schedule types do not support media multiplexing.
The option cannot be selected in those instances.
Note: The relocation schedule that was created for the basic disk staging storage
unit is not listed under Schedules in the NetBackup Administration Console
when Policies is selected.
Policies 143
Start Window tab
The Start Window tab provides controls for setting time periods during which
NetBackup can start backups, archives, or basic disk staging relocation when
using this schedule. Time periods are referred to as time windows. Configure
time windows so that they satisfy the requirements necessary to complete a task
or job. For example, create a different window for the backups that open each
day for a specific amount of time, or keep the window open all week.
Time
window
3 Indicate how long the time window remains open by setting a duration time
or by choosing an End day and End time:
■ To indicate the duration of the time window:
Once the opening (or the start) of the window is selected, click the up
and down arrows to the right of Duration (days, hours, minutes).
■ To indicate the close (or the end) of the time window:
144 Policies
Start Window tab
Click the arrow to the right of End day and select the last day in the
time window. Then, click the up and down arrows to the right of End
time to select when the time window ends.
Time windows show as bars in the schedule display.
4 If necessary, click a time window to perform actions by the following Start
Window buttons:
■ Delete: Deletes the selected time window.
■ Clear: Removes all time windows from the schedule display.
■ Duplicate: Replicates the time window for the entire week.
■ Undo: Erases the last action.
5 Click another tab to make additional selections, or click Add or OK to add the
schedule as it is to the Schedule tab.
Duration example
The following figure represents the effect of schedule duration on two full
backup schedules. The start time for schedule B begins shortly after the end
time for previous schedule A. Both schedules have three clients with backups
due.
Client A3
Client B1
Client B3 is unable to start
Client B2 because the window has closed.
Client B3
Schedule A Schedule B
Start Time End Time Start Time End Time
The backup for client A3 in Schedule A does not finish until after the
Schedule B window has opened. Schedule A does not leave enough time for
the Schedule B backups. Client B3 must wait until the next time NetBackup
runs Schedule B.
Client A3 illustrates that if a backup starts, it runs to completion even if the
window closes while the backup is running.
Policies 145
Exclude dates tab
Use the Exclude Dates tab to exclude specific dates from a schedule. The Exclude
Dates tab displays a 3-month calendar. Use the controls at the top of the
calendar to change the month or year.
3 After the dates are selected, select another tab to make changes or click OK
to close the dialog.
146 Policies
Calendar schedule tab
The Calendar Schedule tab displays a 3-month calendar. Use the controls at the
top of the calendar to change the month or year.
Matrix
Matrix
2 In the Calendar Schedule tab, the schedule is set up to run on every week
day, Monday through Saturday.
3 No backups from the policy exist yet because it is a new policy. Since today
(Monday) is a run day, a job runs as soon as the window opens at 6 p.m.
4 At midnight, it is a new day (Tuesday) and a window is open (until 6 a.m.) so
the job is due and runs again. The backups continue to run soon after
midnight from that time forward.
Notice how the backup runs before midnight, then again immediately after
midnight. Both jobs are valid since both have different run days and windows
are open at both times (6 a.m. through 6 p.m. every day of the week). Windows
that span midnight become two separate windows for calendar schedules.
Policies 151
Calendar schedule tab
To run jobs at 6 p.m. instead of midnight, use a frequency of one day instead of
recurring days in the Calendar Schedule tab.
only on specific days. A different backup window can be specified for each day.
The days that are chosen for backups depends on how you want to distribute the
backup load. For example, to have all backups occur on Saturday, create a
backup window only for Saturday. Leave these values blank for other days.
The best times for automatic backups are usually nights and weekends, when
client and network activity is lowest. Otherwise, the backups can adversely
For details on how calendar-based scheduling works with backup windows, see
For examples of automatic schedule configuration, click the Help button in the
If the automatic backup continues to run, the user job misses the backup
window. User jobs delay automatic backups and can cause backups to miss
the backup window. See “Limit jobs per policy” on page 97 and “Maximum
jobs per client” on page 436.
■ Which storage unit should be used for user backups?
Use a different storage unit to eliminate conflicts with automatic backups.
■ Which volume pool should be used for user backups?
Use a different volume pool if you want to manage the media separate from
the automatic backup media.
Example policies
The following tables show the clients, backup selection list, and schedules of two
Policy 1 specifies that files in /usr and /home be backed up for the clients
mars, jupiter, and neptune. This policy has daily and weekly automatic
Example Policy 1
mars /usr Daily Incremental ■ Run every day between 6 p.m. and 6 a.m.
jupiter /home Backups ■ Store on 8mm tape.
neptune ■ Keep 14 days.
User Backups ■ User can run any day between 8 a.m. and 5
p.m.
■ Store on 8mm tape.
■ Keep one year.
Example Policy 2
pluto /usr Daily Incremental ■ Run every day between 6 p.m. and 6 a.m.
mercury /home Backups ■ Store on 8mm tape.
■ Keep 14 days.
Clients that are used for similar tasks generally have much in common
In some instances, you can create a single policy for each group of clients. In
other cases, you need to subdivide the clients and include them in the separate
In this example, assume that the clients are in the same work group. Initially,
we’ll try to cover all of the clients in the same backup policy.
Policy Clients
S1 mercury
WS1 mars
jupiter
neptune
The storage unit and volume pool settings apply to all files that are backed up by
the policy. If files have special storage requirements, create separate policies for
the files, even if other factors are the same, such as schedules.
Policies 155
Example policies
/h002/devexp
and
/h002/desdoc
on mercury. Those files are sent to DLT tape. Other files on mercury go on 8mm
tape. If it is necessary to keep backups for some files on separate media, create a
policy that specifies a unique volume pool for those backups. Then, add the
media for that volume pool.
/h002/projects
/people
/var
neptune /
with NFS do not affect the other clients. For more information, see “Follow
NFS” on page 101.
■ Cross Mount Points. Select this attribute if you want NetBackup to cross
mount points on UNIX or Windows clients in the policy. For more
information, see “Cross mount points” on page 103.
■ Backup Network Drives. Select this attribute to back up the files that the
client stores on network drives (applies only to MS-Windows-NT policies).
For more information, see “Backup network drives” on page 100.
■ Compression. Set this attribute if you want a client to compress its backups
before sending them to the server. Note that the time to compress can
increase backup time and make it unsuitable to use for all clients. For more
information, see “Compression” on page 105.
■ Job Priority. Use this attribute to control the order in which NetBackup
starts the backups. The clients with the higher priority are backed up first.
For more information, see “Job priority” on page 98.
In our example, no extra policies are required because of general attribute
settings.
backups.
To maximize drive use, use multiplexing for the slower clients that produce
small backups. The higher-performance clients that produce long backups are
See “Allow multiple data streams” on page 112 in this guide and “Using multiple
NetBackup master servers” in Chapter 1 of the NetBackup Administrator’s
Guide, Volume II.
/home
/var
neptune
Policies 159
Clients tab
Clients tab
The Clients tab contains a list of clients to be backed up (or acted upon) by the
selected policy. A client must be included in the list of at least one backup policy
to be backed up. A client can be placed in more than one backup policy can be
useful. For example, place the client name in two policies to back up different
sets of files on the client according to different policy rules. NetBackup software
can be installed on UNIX client machines from the Clients tab.
Note: The Clients tab does not appear for Vault or Catalog policy types.
Add only clients with the hardware and the operating systems that this
policy supports. For example, do not add a Novell NetWare client to an
MS-Windows-NT policy. If you add a client to more than one policy,
designate the same hardware and operating system in each of the policies.
Note: If the hardware and the operating system you want is not in the list,
associated client software is not installed on the server. Check the
/usr/openv/netbackup/client directory for the directories and software
that corresponds to the client you want to install. If the directories or software
are not there, rerun the installation script on the server and choose the option to
install client software. (See the NetBackup installation guide that came with
your software.)
5 Click OK. To add another client, click Add. Click Close to cancel the changes
that you have not yet added and close the Add Client dialog.
2 Select the master server name at the top of the All Policies middle pane.
3 Click Actions > Install UNIX Client Software. The Install UNIX Client
Software dialog appears.
4 In the Don’t install these clients box, select the clients you want to install
and click the right arrows. The clients are moved to the Install these clients
field.
Clients tab
Policies 163
Backup Selections tab
The Backup Selections tab lists the files, directories, directives, scripts, and the
templates that are backed up with this policy. NetBackup uses the same backup
selection list for all of the clients that are backed up according to the policy.
Every file on the list does not need to exist on all of the clients. NetBackup backs
up the files that it finds that are on the backup selections list. Each client,
however, must contain at least one of the files in the backup selections list or the
client backup fails with a status 71. The policy backup selections list does not
apply to user backups or archives. For user backups and archives, users select
the objects to back up before they start the operation.
2 Double-click the policy where you want to change the backup selections list.
The Change Policy dialog appears.
3 Click the Backup Selections tab.
4 To add an entry, click New. The Add Backup Selections dialog appears.
5 Select a path or directive:
■ Type the name of the path in the Pathname or Directive field.
For file path information, see “Pathname rules for UNIX clients” on
page 176 and “Path rules for Microsoft Windows clients” on page 170.
■ Click the drop-down arrow and select a directive in the Pathname or
Directive field. Click Add to include the path or directive to the list.
■ Shell scripts:
Specify the full path to list scripts. Be sure that the scripts that are
listed are installed on each client in the Client list.
Specifying an Oracle script example:
install_path/netbackup/ext/db_ext/oracle/samples/rman
/cold_database_backup.sh
6 To change the order of the backup selections, select one and click Up or
Down.
7 Click OK to add the selection to the selection list.
file_a
file_b
file_c
NEW_STREAM
file_d
file_e
file_f
The example produces two concurrent data streams. The first data string
contains file_a, file_b, and file_c. The second data stream contains
file_d, file_e, and file_f. For more information, see “Allow multiple data
streams” on page 112.
Note: For best performance, use only one data stream to back up each physical
device on the client. Multiple concurrent streams from a single physical device
can cause longer backup times. The tape heads must move back and forth
between tracks containing files for the respective streams.
The script can reveal mistakes in the selections list that make it impossible
for NetBackup to find the files. This results in files being skipped in the
backup.
If a path is not found, NetBackup logs a trivial (TRV) or warning (WRN)
message. However, the job may end the backup with a status code 0
(successful). Usually, to report files missing from the backup selections list
is not helpful, since not all files are expected to be present on every client.
However, check the logs or use the check_coverage script to ensure that
files are not missed due to bad or missing backup selections list entries.
The following examples show the log messages that appear when files on a
client are not found. For information on check_coverage, see the comments
in the script.
/home1[0123456789]
NetBackup backs up /home10 through /home19 if both exit. If they are not
present, the Problems report or the All Log Entries report displays a message
Note: If the paths seem correct and the message continues to appear, ensure that
no trailing spaces appear in the paths.
Policies 169
Backup Selections tab
You must resolve the symbolic link if you do not intend to back up the symbolic
link itself.
170 Policies
Rules to indicate paths in the backup selections list
The following sections discuss rules for specifying paths for each type of
NetBackup client:
■ “Pathname rules for UNIX clients” on page 176.
■ “Path rules for Microsoft Windows clients” on page 170.
■ “Path rules for NetWare NonTarget clients” on page 183.
■ “Path rules for NetWare Target clients” on page 185.
■ “Path rules for clients running extension products” on page 185.
File backups
Microsoft Windows path conventions, UNIX path conventions, or a combination
of the two can be used in the backup selections list.
Correct entry:
c:\
Incorrect entry:
c:
or
*:\ or ALL_LOCAL_DRIVES
The following drives are not backed up: floppy disks, CD-ROMs, and any
drives that are located on remote systems but mounted on a system through
the network.
■ By default, NetBackup does not back up the files that are described in “Files
that are excluded from backups by default” on page 194.
■ Exclude specific files from backups by creating an exclusion list on the
client. For more information, see “Excluding files from automatic backups”
on page 195.
The following backup selection list uses Microsoft Windows conventions:
c:\
d:\workfiles\
e:\Special\status
c:\tests\*.exe
/d/workfiles/
/e/Special/status
/c/tests/*.exe
To specify a disk-image backup, add the logical name for the drive to the policy
backup selection list. The format in the following example backs up drive C.
\\.\c:
Disk-images can be included in the same backup selection list with other
backups:
\\.\c:
d:\workfiles\
e:\Special\status
HKEY_LOCAL_MACHINE:\
To restore the backup, the user first chooses Select for restore > Restore from
Normal backup.
When the backups are listed, the disk image appears as a file with the same
name that was specified in the backup selection list. In this example:
\\.\c:
Select the disk image source, then enter the destination in the following format:
\\.\drive:
Caution: To recover the registry, do not include individual registry files or HKEY
entries in the selection list that’s used to back up the entire registry. If you use a
NetBackup exclude list for a client, do not exclude any registry files from your
backups.
To restore the registry in the case of a disk failure, see the Disaster Recovery
chapter in the NetBackup Troubleshooting Guide for UNIX and Windows.
subsequent references means that only one backup copy of the data is created,
regardless of the number of multiple hard links.
If all hard-link references are restored, the hard-linked files continue to point to
the same ID as the other files to which they are linked. However, if all the hard
links are not restored, you can encounter anomalies as shown in the following
examples.
Example 1
Assume that three hard links point to the same data.
1 During a backup of Link2 and Link3, Link2 is encountered first and backed
up. Then Link3 is backed up as a link to Link2. The three files are all
hard-linked to the same data.
Data
2 The original copies of Link2 and Link3 are backed up to tape, then deleted.
Only Link1 is left on the disk.
On Disk On Tape
Data Data
3 During a subsequent restore, Link2 and Link3 are restored. The restored
files, however, do not point to the same file ID as Link1. Instead, they are
assigned a new file ID or inode number and the data is written to a new place
on the disk. The data in the new location is an exact copy of what is in Link1.
The duplication occurs because the backup does not associate Link2 and L3
with Link1.
Data Data
Policies 175
Rules to indicate paths in the backup selections list
Example 2
Assume that you attempt to restore only Link3. Here, NetBackup cannot link
Link3 to Link2 because Link2 does not exist. The restore can complete only if it
can link to Link2. A secondary restore request to the NetBackup server
automatically restores Link2, which contains the data. Link2 can now be
successfully restored.
176 Policies
[ ]
{ }
■ On Solaris, HP-UX, AIX, Linux Red Hat 4 (and later), Linux SuSE SLE 9 (and
later), and MAC 10.4 (and later) platforms, NetBackup backs up access
control lists (ACLs).
■ NetBackup can back up and restore Sun PC NetLink files.
■ On IRIX 6.x and TRU64 Alpha platforms, NetBackup backs up extended file
attributes.
■ On IRIX platforms, NetBackup backs up and restores extended attributes
attached to XFS file system objects.
■ On TRU64 OSF/1 platforms, NetBackup backs up and restores extended
attributes attached to files on AdvFS and UFS file systems.
■ By default, NetBackup backs up and restores Solaris 9 and 10 extended
attribute files. The FlashBackup single file restore program (sfr) does not
restore extended attribute files.
■ By default, NetBackup backs up and restores named data streams for VxFS
4.0 (Solaris SPARC) and VxFS 5.0 (Solaris SPARC, HP, and AIX). The
FlashBackup single file restore program (sfr) does not restore extended
attribute files.
For more information, see “Backup and restore of extended attribute files
and named data streams” on page 180.
■ On Hewlett-Packard and Solaris SPARC platforms, NetBackup backs up VxFS
extent attributes.
Caution: Save a copy of the partition table before performing raw partition
backups so that you retain the copy for reference before to a restore. To restore
the raw partition, a device file must exist and the partition must be the same size
as when it was backed up. Otherwise, the results of the restore are
unpredictable.
You can include raw partitions in the same backup selection list as other
backups. For example:
/home
/usr
/etc
/devices/sbus@1,f8000000/esp@0,800000/sd@2,0:1h
Note: NetBackup does not distinguish between full and incremental backups
when it backs up a raw partition. The entire partition is backed up in both cases.
Raw partition backups occur only if the absolute pathname in the backup
selection list is a block or character special device file. You can specify either
block or character special device files. Character special device files are often
faster because character devices avoid the use of the buffer cache for accessed
disk data. Test both a block and character special device file to ensure the
optimum backup speed for your platform.
Ensure that you specify the actual block- or character-device files. Sometimes
these are links to the actual device files. If a link is specified, only the link is
backed up. If the device files are reached while backing up /dev, NetBackup
backs up only the inode files for the device, not the device itself.
Figure 4-9 Example of base file and extended attribute directory and files
File 1
File 1 is a base file on a Solaris or VxFS client
File 1
Extended attribute file 1
The user restores File 1 from a backup that was created when File 1 possessed
only three extended attribute files.
File 1 backup
Since Overwrite existing files is selected as a restore option, when the user
restores File 1, extended attribute files 1, 2, and 3 are overwritten. Extended
attribute file 4 remains and is not overwritten.
Restored file 1
an error message appears in the Restore Monitor to inform the user that the
extended attributes or named data streams are not restored. NetBackup then
continues with the restore job.
To disable the restore of extended attribute files and named data streams
To disable the restore of extended attribute files and named data streams, add
an empty file named IGNORE_XATTR to the client in the following directory:
/usr/openv/netbackup/
The addition affects only Solaris 9 or VxFS 4.0 clients.
File IGNORE_XATTR was formerly known as IGNORE_XATTR_SOLARIS.
Note: Only the modified GNU tar that is supplied with NetBackup is able to
restore the extended attributes or named data streams to a client. For more
information, see “Reading Backup Images with tar” in NetBackup
Administrator’s Guide, Volume II.
Where:
■ SMDR (Storage Management Data Requestor) is the name of the NetWare
file server that is running the SMDR.NLM that is used for backups. (NLM
means NetWare-loadable module.)
■ TSA (Target Service Agent) is a NetWare software module that prepares the
data for backup or restore by the SMDR. The type of TSA that is used
depends on the data. For example, NetWare file systems and DOS
workstations each have TSAs.
■ TS is the Target Service, which is the NetWare entity that contains the data
that the selected TSA handles. For example, in the case of the DOS TSA
(tsasms.com) it is a DOS workstation. In the case of a NetWare file system
TSA, it is the system with the NetWare file systems to be backed up.
■ resources are the specific resources on the target service. For example, it can
be NetWare file systems such as BINDERY, SYS, and USER.
■ directory/file is the directory and file that are in the resource (if it is a
path to a specific file).
Observe the following rules for paths:
■ Give the server access to each path or the scheduled backup fails. To provide
this access, use the Allowed scheduled access command on the Backup
menu in the NetBackup interface on the NetWare client. For more
information, see the NetBackup for Novell NetWare Client Administrator’s
Guide.
■ Enter one path per line.
■ Begin all paths with a forward slash (/).
■ Precede each component in the path with a forward slash.
If the last component in the path is a directory, follow it with a forward
slash (/). The trailing slash is not required but is a reminder that the path
points to a directory instead of a file.
/TILE/TILE.NetWare File System/TILE/SYS/DOC/
If the last component is a file, include the file extension and omit the slash
from the end of the name.
/TILE/TILE.NetWare File System/TILE/SYS/DOC/TEST.TXT
■ All components in a path must show upper and lower case letters as they
appear in the actual path on the client.
■ Wildcard usage is the same as for Windows clients. For more information,
see “Using wildcards in NetBackup” on page 632.
■ To back up all NetBackup for NetWare clients that are in the policy, enter
only one forward slash (/) on a line:
Policies 185
Rules to indicate paths in the backup selections list
■ To back up an entire NetBackup for NetWare client, enter a forward slash (/)
followed by the client name and another forward slash:
/TILE/
The following example backs up SYS, BINDERY, and USER file systems under the
file system TSA on a client that is named tile:
/TILE/TILE.NetWare File System/TILE/SYS/
Note that the Allowed scheduled access command on the NetBackup NetWare
client Backup menu must also specify access to these paths. See the NetBackup
for Novell NetWare Client Administrator's Guide.
/BINDERY/
The available directives depend on the policy type and whether the Allow
multiple data streams attribute is enabled for the policy. The following example
is a backup selections list that contains the NEW_STREAM directive. The example
is from an MS-Windows-NT policy with Allow multiple data streams enabled:
NEW_STREAM
D:\Program Files
NEW_STREAM
C:\Winnt
ALL_LOCAL_DRIVES directive
Use the ALL_LOCAL_DRIVES directive to back up all local drives except for
those drives that use removable media. The ALL_LOCAL_DRIVES directive
applies to the following policy types:
■ Standard (except for NetWare target clients)
■ MS-Windows-NT
■ NetWare (NonTarget clients only)
However, ALL_LOCAL_DRIVES is not allowed for NetWare policy types if
Allow multiple data streams is also used.
For more information, see “ALL_LOCAL_DRIVES directive and multiple
data streams” on page 192.
For information on files and the directories that NetBackup automatically
excludes from backup, see “Files that are excluded from backups by default” on
page 194.
SYSTEM_STATE directive
The System_State:\ directive is a valid directive only to back up Windows
2000/XP machines. If the machine is not Windows 2000/XP or a Windows 2003
Server, the System_State:\ directive does not have any effect.
Windows 2003 Server machines recognize the System_State:\ directive and
behave as if following the Shadow Copy Components:\ directive. A message
informs the user that this directive translation has occurred.
If the machine is Windows 2000/XP, the list of items that are backed up can
include the following:
■ Active Directory
■ COM+ Class Database
■ Cluster Database
■ IIS Database
Policies 187
Rules to indicate paths in the backup selections list
■ Registry
■ Boot Files and Protected Files
■ SYSVOL
■ Certificate Server
On Windows 2000 machines, the registry is backed up in the process of regular
file system backups. The files that comprise the registry can be found in the
following location:
%SystemRoot%\SYSTEM32\Config
The Shadow Copy Components:\ directive specifies that all of the Volume
Shadow Copy component writers get backed up. This directive ensures that all of
SKIP_SMALL_VOLUMES
Policies 189
Rules to indicate paths in the backup selections list
Except for AFS, these policy types can be used when their associated
For information on other policy types and associated backup selections list
Caution: Include policy-specific directives only in backup selections lists for the
policies that support the directives or errors can occur.
Note: For best performance, use only one data stream to back up each physical
device on the client. Multiple concurrent streams from a single physical device
can adversely affect backup times. The heads must move back and forth between
tracks containing files for the respective streams.
■ The backup is split into a separate stream at each point in the backup
selections list where the NEW_STREAM directive occurs.
■ All file paths between NEW_STREAM directives belong to the same stream.
■ The start of a new stream (a NEW_STREAM directive) defines the end of the
previous stream.
■ The last stream in the backup selections list is terminated by the end of the
backup selections list.
Note: In the following examples, assume that each stream is from a separate
physical device on the client. Multiple concurrent streams from a single physical
device can adversely affect backup times. The backup time is longer if the heads
must move back and forth between tracks containing files for the respective
streams.
/usr
/lib
NEW_STREAM
/home
/bin
after
/bin
If an incremental backup is due that night, only changed files in /var are
backed up. Add a NEW_STREAM directive before /var, to perform a full backup of
all files in /var, regardless of when the files were last changed.
Policies 191
Rules to indicate paths in the backup selections list
Before the backup begins, the client uses auto-discovery to preprocess the
backup selections list to determine how many streams are required. The first
backup that a policy performs preprocesses the backup selections list. However,
preprocessing does not necessarily occur before every backup. Whether or not it
Caution: Do not select Cross mount points for policies where you use the
ALL_LOCAL_DRIVES directive.
ALL_LOCAL_DRIVES example 1
Assume that Allow multiple data streams is enabled in the auto-discovery mode.
Assume that the client is a Windows system with two drive volumes, C:\ and
D:\. The backup selections list contains:
ALL_LOCAL_DRIVES
Policies 193
Rules to indicate paths in the backup selections list
For a UNIX client, NetBackup generates a stream for each file system.
ALL_LOCAL_DRIVES directive.
ALL_LOCAL_DRIVES example 2
Assume that Allow multiple data streams is not enabled. Assume that the client
is a Windows system with two drive volumes, C:\ and D:\. The backup
selections list contains:
ALL_LOCAL_DRIVES
Here, NetBackup backs up the entire client in one data stream that contains the
ALL_LOCAL_DRIVES directive.
UNSET
The UNSET directive interrupts a policy-specific directive so it is not passed with
any additional streams. The directive that was unset can be defined again later
in the backup selections list to be included in the current and the later streams.
UNSET_ALL
UNSET_ALL has the same effect as UNSET but unsets all policy-specific
directives in the backup selections list that have been defined up to this point.
UNSET example
In the following backup selections list, the set command is a client-specific
directive that is passed to the first and all subsequent streams.
NEW_STREAM
set destpath=/etc/home
/tmp
/use
NEW_STREAM
194 Policies
/export
NEW_STREAM
/var
For the set command to be passed to the first two streams only, use UNSET or
UNSET_ALL at the beginning of the third stream. At this location, it prevents
SET from being passed to the last stream.
NEW_STREAM
set destpath=/etc/home
/tmp
/use
NEW_STREAM
/export
NEW_STREAM
/var
You can also create an include list to add a file(s) specifically that would be
excluded. The include list is useful to exclude an entire directory except for one
Note: Exclude and include lists do not apply to user backups and archives.
The method for specifying files in the exclude and include lists depends on the
type of client:
■ On Microsoft Windows clients, specify exclude and include lists in the
Backup, Archive, and Restore client interface: Start Backup, Archive, and
Restore and click File > NetBackup Client Properties. Go to the Exclude list
or Include list tab. For further instructions, see the NetBackup user’s guide
for the client.
The Exclude list or the Include list can also be specified through the
NetBackup Administration Console on the master server. For more
information, see “Exclude Lists properties” on page 414.
■ On NetWare target clients, the exclude and include lists are specified when
the targets are added. See the NetBackup user’s guide for the client.
■ On UNIX clients, you create the exclude and include lists in the following
files on the client:
/usr/openv/netbackup/exclude_list
/usr/openv/netbackup/include_list
196 Policies
Disaster Recovery tab
Caution: Do not save the disaster recovery information to the local machine.
Symantec recommends that the image file be saved to a network share or a
removable device.
Note: Vault protects the disaster recovery data by sending the data to the Vault
site as an email attachment of the Vault report email. The separately-priced
Vault option must be installed.
Policies 197
Disaster Recovery tab
Path
The path to the directory where the disaster recovery information is saved.
Specify a local directory or NFS share.
Logon
The logon and password information that is required to access the NFS share.
Password
The password that is required to log on to the share.
Note: Critical policies should use only incremental or full backup schedules. The
Disaster Recovery report lists only the media for incremental and full backup
schedules.
198 Policies
Disaster Recovery tab
Note: When NetBackup is running with Vault, Vault includes the disaster
recovery data in the Vault Recovery Report.
Policies 199
Creating a Vault policy
Note: The Clients tab does not appear for Vault policy types.
If the vault profile name is not unique, use the following format:
vltrun robot_number/vault_name/profile_name
For more information on Vault names, profile names, and command usage,
see the Vault Administrator’s Guide.
7 Click OK.
200 Policies
Performing manual backups
Note: If the Go into effect property is set for a future date and time, the backup
does not run.
3 In the Manual Backup dialog, select the schedule and the clients that you
want to back up.
If you do not select any schedules, NetBackup uses the schedule with the
highest retention level. If you do not select any clients, NetBackup backs up
all clients.
User schedules do not appear in the schedules list. A user schedule cannot
be manually backed up because they do not have a backup selection list (the
user selects the files).
4 Click OK to start the backup.
Policies 201
More about synthetic backups
Synthetic backups can be written to tape storage units or disk storage units, or a
combination of the two. The following sections describe how synthetic backups
can be used in your NetBackup configuration.
■ The schedule that is created for a synthetic backup must have Synthetic
Backup selected.
■ The master servers, media servers, and clients must all have NetBackup
version 5.0 or later installed to synthesize backups.
■ One of the following must be available:
■ Disk storage unit(s) with adequate space available.
■ Tape library(s) with multiple drives to read and write. For more
information, see “Disk storage unit considerations” and “Tape storage
unit considerations” on page 207.
■ A combination of disk storage unit(s) and tape library(s).
Note: To configure a synthetic cumulative backup for any clients that are
archive bit-based (default), use only differential incremental backups for the
traditional, non-synthesized backups.
■ One full and/or one cumulative backup schedule with the Synthetic Backup
option selected.
Traditional Synthetic
full backup to disk (Sunday) full backup to disk (Sunday)
A B
Synthetic full
Incremental backups backup (Sunday)
Sunday’s Synthetic
to disk (Mon-Sat) full Backup
B C
Synthetic
full
backup
Incremental backups (Sunday)
(Mon-Sat) Sunday’s synthetic
full backup
C D
Incremental backups
(Mon-Sat)
The traditional full backup (A) and the incremental backups are created in the
traditional manner: data is scanned, then copied from the client’s file system to
the backup media. The synthetic backups do not interact with the client system
at all, but are instead synthesized on the media server.
204 Policies
incremental backups.
Note: The synthetic full backups in this scenario are only as current as the
Saturday incremental backup.
Cumulative and
differential
incremental backups Sunday’s synthetic
to disk (Mon-Sat) cumulative Incremental Synthetic cumulative incremental
backup backup (Sunday)
A B
Synthetic cumulative
Incremental backups incremental backup
(Mon-Sat) Sunday’s synthetic (Sunday)
cumulative incremental
backup
B C
Incremental backups
(Mon-Sat)
incremental backups.
Note: The synthetic cumulative backups in this scenario are only as current as
the Saturday incremental backup.
Reducing the gap between the last incremental backup and the
synthesized backup
Since a synthetic backup does not involve direct contact with the client, a
synthetic backup is only as current as the last incremental backup. If there is a
concern to reduce a potential gap in backup coverage, run an incremental
backup before the synthetic backup.
by sequentially older images. When two or more component images have been
written to the same tape, the tape movement may be somewhat inefficient
compared to disk-based images.
Note that this scenario is limited to single directory restores. Single file
restores and full image restores from synthetic fulls are equal or better than
from traditional full backups, as noted in previous bullets.
General notes
■ Synthetic backups are supported on all media server platforms and tier
one master server platforms.
■ The option to create multiple copies is not allowed for synthetic backups.
■ Synthetic backups are not supported if any of the component images are
encrypted.
■ A user-generated backup cannot be used to generate a synthetic image. A
backup that is generated from a User Backup schedule or a User Archive
schedule cannot be used as one of the components of a synthetic backup.
For example:
Catalog after incremental backup jobs run:
XDisk_1064417510_INCR
XDisk_1064417510_INCR.f
XDisk_1064420508_INCR
XDisk_1064420508_INCR.f
XDisk_1064421708_INCR
XDisk_1064421708_INCR.f
XDisk_1064421709_FULL
First set: Synthetic full
Timestamp differences
The catalog for a synthetic image usually has a timestamp one second later than
the most recent incremental component image. The timestamp may be more
than one second later if there were possible image name conflicts.
synthetic backup job fails with error code 136 (TIR info was pruned from the
image file). If the problem is correctable, run the synthetic backup again.
For more information, see “Keep true image restoration (TIR) information” on
page 384.
■ On the media server(s): bptm (if any tape images), bpdm (if any disk images),
bpcd
Note that several media servers may be involved if the component images
are on different nodes.
However, bpsynth is used for each stream or client. This can be inefficient with
tape images since bpsynth needs a tape drive to write the new image. Also,
bpsynth may use the same component image volumes. One may have to
complete before the next one proceeds.
Current
master
server
Right-click an object to
display a shortcut menu
Storage units
A storage unit is a label that NetBackup associates with physical storage. The
The creation of any storage unit type consists of the following general steps:
1 Name the storage unit. A configured storage unit indicates to NetBackup the
existence of underlying physical storage.
2 Choose the storage unit type: Media Manager, disk, or NDMP. (See Figure 5-2
on page 217.)
3 Select a media server. The selection indicates that the media server(s) have
permission to write to the storage unit.
4 Indicate the destination where the data is written.
■ For Media Manager storage units:
Data is written to tape robots, stand-alone tape drives, and optical disk
devices.
■ For disk storage:
NetBackup permits an unlimited number of disk storage units. Disk
storage may be one of the following types:
■ AdvancedDisk storage units: The destination is a disk pool.
■ BasicDisk storage units: The destination is a path to a volume on a
host.
■ NearStore storage units: The destination is a NearStore volume on
a storage server.
■ OpenStorage storage units: The destination is a disk pool.
■ PureDisk storage unit: The destination is a disk pool.
■ SharedDisk storage units: The destination is a disk pool.
■ SnapVault storage: The destination is a SnapVault server.
■ For NDMP storage: The NDMP protocol to is used to perform backups
and recoveries. The destination is an NDMP host.
Storage units, unit groups, and lifecycle policies 217
Storage units
3 Complete the fields on the New Storage Unit dialog box. The options are
described in “Storage unit settings” on page 228.
4 Click OK to add the storage unit to the configuration.
To delete a storage unit does not prevent files from being restored that were
written to that storage unit, provided that the storage has not been physically
■ Once the images have been expired, they cannot be restored unless the
images are imported. (See “Importing NetBackup or Backup Exec
images” on page 336.)
NetBackup automatically deletes any image fragments from a disk storage
unit or a disk pool. This generally occurs within seconds of expiring an
image. However, to make sure that all of the fragments have been deleted,
check the directory on the storage unit to make sure that it is empty.
2 Select the Storage utility, then Storage Units.
3 In the Details pane, select the storage unit you want to delete. Hold down the
Control or Shift key to select multiple storage units.
4 Select Edit > Delete.
5 In the confirmation dialog box, select the storage units to delete.
6 Click OK.
7 Modify any policy that uses a deleted storage unit to use another storage
unit.
Media Manager storage unit settings are listed alphabetically in “Storage unit
Note: NetBackup Media Manager can manage media for other applications, such
as Storage Migrator. (A tape that is assigned to Storage Migrator uses a different
format and would not be usable for NetBackup backup data.)
Settings are listed alphabetically in “Storage unit settings” on page 228. Not all
Note: Symantec recommends that quotas are not imposed on any file systems
that NetBackup uses for disk storage units. Some NetBackup features may not
work properly when file systems have quotas in place. (For example, the
capacity managed retention selection in lifecycles and staging to storage units.)
BasicDisk
A BasicDisk type storage unit consists of a directory on locally-attached disk or
network-attached disk that is exposed as a file system to a NetBackup media
server. NetBackup stores backup data in the specified directory.
Notes about the BasicDisk type storage unit:
■ Do not include the same volume or file system in multiple BasicDisk storage
units.
■ BasicDisk storage units cannot be used in a storage lifecycle policy.
AdvancedDisk
An AdvancedDisk disk type storage unit is used for dedicated disk that is
directly attached to a NetBackup media server. An AdvancedDisk selection is
available only when the Flexible Disk Option is licensed.
NetBackup assumes exclusive ownership of the disk resources that comprise an
AdvancedDisk disk pool. If the resources are shared with other users, NetBackup
cannot manage disk pool capacity or storage lifecycle policies correctly.
For AdvancedDisk, the NetBackup media server functions as both a data mover
and a storage server.
NearStore
A NearStore disk type storage unit is used to store images on Network Attached
Storage (NAS) from Network Appliance. NearStore appears as a selection only
when the OpenStorage Disk Option is licensed.
For NearStore, the NetBackup media servers function as the data movers. The
NearStore host is the storage server.
Note: NearStore storage units cannot be used as part of a storage unit group or
used in a Storage Lifecycle Policy.
OpenStorage
An OpenStorage disk type storage unit is used for disk storage on an intelligent
disk appliance. The actual name of the disk type depends on the vendor. An
OpenStorage selection is available only when the OpenStorage Disk Option is
licensed.
The disk appliance is integrated into NetBackup through an API. The storage
vendor partners with Symantec to integrate the appliance into NetBackup.
For OpenStorage, the NetBackup media servers function as the data movers. The
disk appliance is the storage server
224 Storage units, unit groups, and lifecycle policies
Storage units
PureDisk
A PureDisk disk type storage unit is used to store images on PureDisk storage
devices. The storage unit can be shared by multiple NetBackup media servers.
PureDisk appears as a selection only when the PureDisk Storage Option is
licensed.
For PureDisk, the NetBackup media servers function as the data movers. The
PureDisk Linux servers function as the storage servers.
Note: PureDisk storage units cannot be used as part of a storage unit group.
SharedDisk
A SharedDisk disk type storage unit is used to store images on a disk array that
multiple NetBackup media servers share. The SharedDisk selection is available
only when the Flexible Disk Option is licensed.
For SharedDisk, the NetBackup media servers function as both the data movers
and the storage servers.
SnapVault
A SnapVault storage unit is used to store images on Network Attached Storage
(NAS). The SnapVault selection is available only when the NetBackup Snapshot
staging operation.
For SnapVault, the NetBackup media servers function as the data movers. The
policies. Storage lifecycle policies are discussed on page 253, but mentioned
The following figure is one example of how policies can interact with volumes in
Figure 5-4 Lifecycles and disk storage units referencing disk pools
Policy_Gold Policy_Silver
The data classification for this policy is The data classification for this policy
gold. The policy is configured to write is silver. The policy is configured to
to Lifecycle_Gold. write to Any available storage unit.
Lifecycle_Gold
Lifecycle_Gold contains DSU_1 as a backup
destination.
DSU_1 DSU_2
DSU_1 references DiskPool_A. Policy_Silver writes to DSU_2.
DSU_2 references DiskPool_A.
DiskPool_A
Storage units
■ To determine the potential free space on a disk staging storage unit, see
“Finding the potential free space on a BasicDisk disk staging storage unit”
on page 246.
■ The NetBackup General Server host property Check the capacity of disk
storage units property determines how often NetBackup checks 6.0 disk
storage units for available capacity. Subsequent releases use internal
methods to monitor disk space more frequently. (See “Check the capacity of
disk storage units” on page 431.)
Storage units, unit groups, and lifecycle policies 227
Storage units
Create NDMP storage units for drives directly attached to NAS filers. Any drive
that is attached to a NetBackup media server is considered a Media Manager
storage unit, even if used for NDMP backups.
Note: Remote NDMP storage units may already be configured on a media server
from a previous release. Upon upgrade of the media server, those storage units
are automatically converted to Media Manager storage units.
See the NetBackup for NDMP Administrator’s Guide for more information.
228 Storage units, unit groups, and lifecycle policies
Storage unit settings
The following topics describe the settings that appear for all types of storage
units. The settings are listed alphabetically. Each setting does not appear for
each storage unit type.
for storage units that are not based on disk pools. For example, BasicDisk
storage units.
The setting specifies the absolute path to a file system or a volume available for
disk backups. Enter the path directly in the field, then click Add. Use any
To display properties about the directory or volume, click the Properties button.
Do not configure multiple BasicDisk storage units to use the same volume or file
system. Not only do the storage units compete for space, but different Low water
If the BasicDisk storage unit is used as a disk staging storage unit, Symantec
recommends dedicating a disk partition or file system to it. This allows the disk
AdvancedDisk storage units, which use disk pools composed of disk volumes
Use platform-specific file path separators (/ and \) and colon (:) within a drive
Caution: With this setting enabled, the root file system may fill up.
Density
The Storage device selection determines the media Density. This setting
appears for Media Manager and NDMP storage units only.
Disk pool
A Disk pool is selected for any disk storage unit with an Enterprise Disk Option
licensed. Select the disk pool that contains the storage for this storage unit. For
AdvancedDisk and SharedDisk, all NetBackup disk pools appear in the Disk pool
list. For OpenStorage, only the disk pools for that OpenStorage vendor’s
appliance appear in the list. For PureDisk, only the disk pools for the PureDisk
For information about how to create a disk pool, see the NetBackup Shared
Storage Guide.
Disk type
A Disk type is selected for a disk storage unit. A disk storage unit may be one of
the following types:
■ AdvancedDisk (NetBackup Flexible Disk Option needed)
■ BasicDisk
■ NearStore (OpenStorage Disk Option needed)
■ OpenStorage (vendor name) (NetBackup OpenStorage Disk Option needed)
■ PureDisk (PureDisk Storage Option needed)
■ SharedDisk (NetBackup Flexible Disk Option needed)
■ SnapVault (NetBackup Snapshot Client option needed). For information on
SnapVault storage units, see the NetBackup Snapshot Client Administrator’s
Guide.
Enable multiplexing
The Enable multiplexing setting allows multiple backups to multiplex onto a
single drive in a storage unit.
Note: Basic disk staging storage units may already be configured on a media
server of a previous release. Upon upgrade, the disk storage units are set with
the Low water mark at 100%. To make the best use of upgraded storage units,
adjust the level.
For disk storage units that reference disk pools, the low water mark applies to
the disk pool. For more information, see “Disk pool properties” on page 732 and
the NetBackup Shared Storage Guide.
Storage units, unit groups, and lifecycle policies 231
Storage unit settings
Note: Increase the Maximum concurrent jobs setting if the storage unit is used
for online, hot catalog backups as well as non-catalog backups. Increase the
setting to ensure that the catalog backup can proceed while regular backup
activity occurs. Where disk pools are used, increase the setting if more than one
server is in the storage unit.
Impact when two disk storage units reference one disk pool
The following example shows how the Maximum concurrent jobs settings are
combined when two disk storage units share one disk pool.
For example, in Figure 5-6:
DSU_1 is configured:
■ to use MediaServer_A.
■ to have a Maximum concurrent jobs setting of two.
■ to reference SharedDisk_pool.
DSU_2 is configured:
■ to use MediaServer_B.
■ to have a Maximum concurrent jobs setting of three.
■ to reference SharedDisk_pool.
Both storage unit reference the same SharedDisk disk pool. Combined, the
storage units have a Maximum concurrent jobs setting of five. However, only
two jobs can run concurrently on MediaServer_A; three on MediaServer_B.
Storage units, unit groups, and lifecycle policies 233
Storage unit settings
Figure 5-6 Impact when disk storage units use one disk pool but
different media servers
Maximum Maximum
DSU_1 concurrent jobs DSU_2 concurrent jobs
setting: 2 setting: 3
MediaServer_A MediaServer_B
MediaServer_A selected to move MediaServer_B selected to move
data to the pool data to the pool
If the storage units were configured to use both media servers, the media servers
could run five concurrent jobs: two from DSU_1 and three from DSU_2.
Media server
The following setting applies only to NetBackup Enterprise Server.
The Media server setting specifies one of the following:
■ The NetBackup media server where the drives in the storage unit attach.
■ The NetBackup media server that controls the disk storage unit.
■ The NetBackup media servers that can access the servers responsible for
data movement to and from the disk pool.
To make this storage unit available to any media server (default), select Any
Available. NetBackup selects the media server dynamically at the time the policy
is run.
■ Concerning BasicDisk storage:
To configure a disk storage unit, select a single media server.
■ Concerning AdvancedDisk storage units
The Media server setting specifies the NetBackup media server that can
move data to and from the disk pool.
234 Storage units, unit groups, and lifecycle policies
Only the media server that is configured as the storage server appears in
the media servers list. The disk storage must be directly attached to the
Note: Run the tpconfig command line utility directly on the media server
to configure and verify credentials.
Media servers are configured as data movers when the storage server login
To restrict the media servers that can access the storage, select Only Use
The Following Media Servers. Then select the media servers that are allowed
The following is required on each media server that accesses the storage:
NDMP host
The NDMP host setting specifies the NDMP tape server that is used to write data
to tape. Select the host name from the drop-down menu.
On demand only
The On demand only setting specifies whether the storage unit is available
exclusively on demand. That is, only when a policy or schedule is explicitly
configured to use this storage unit. Clear the On demand only check box to make
the storage unit available to any policy or schedule.
For SnapVault and NearStore storage units, On demand only is selected by
default and cannot be changed.
236 Storage units, unit groups, and lifecycle policies
Storage unit settings
Caution: If On demand only is selected for all storage units, be sure to designate a
specific storage unit for each policy or schedule. Otherwise, NetBackup is unable
to find a storage unit to use.
Properties button
Click Properties to display information about the volume or the disk pool:
Storage units, unit groups, and lifecycle policies 237
Storage unit settings
Note: OpenStorage vendors may have special requirements for the maximum
fragment size. Consult the vendor's documentation for guidance.
fragments before and including the last checkpoint are retained; the fragments
after the last checkpoint are discarded.)
Note: Basic disk staging units with different maximum fragment sizes may
already be configured on a media server from a previous release. Upon upgrade,
the disk storage units are not automatically increased to the new default of
524,287 megabytes. To make the best use of upgraded storage units, increase the
fragment size on the upgraded storage units.
Robot number
The Storage device selection determines the Robot number. It is the same robot
number used in the Media Manager configuration. For more information on
robot numbers, see “Robot number” on page 601.
Robot type
The Robot type and indicates the type of robot (if any) that the storage unit
contains. The Robot type is determined by the Storage device setting.
For the specific vendor types and models that correspond to each robot type, see
the Supported Peripherals section of the NetBackup Release Notes.
Storage device
The Storage device list contains all possible storage devices available. Storage
units can be created for the listed devices only.
The storage unit name cannot be changed after creation. The Storage unit name
is inaccessible in a Change Storage Unit operation.
Transfer throttle
The Transfer throttle setting appears for SnapVault storage units only.
This setting makes it possible to limit the amount of network bandwidth that is
used for the SnapVault transfer. (In case bandwidth needs to be reserved for
other applications.) Zero (default) means no network bandwidth limit for the
SnapVault transfer: SnapVault uses all available bandwidth. (Range: 0 to
9999999.)
A value greater than 0 indicates a transfer speed for SnapVault in kilobytes per
second. For example, a value of 1 sets a transfer speed limit for SnapVault of 1
kilobyte per second, which is a very slow transfer rate.
■ Only the media servers that are configured as storage servers appear in the
media servers list.
For OpenStorage storage:
■ A software plug-in must be installed on each media server. The software
plug-in is provided by the storage vendor.
■ Login credentials to the storage server must be configured on the media
server.
■ Only the media servers on which storage server login credentials are
configured appear in the media servers list. If a server does not appear,
verify that the software plug-in is installed and that login credentials are
configured for that media server.
For SharedDisk storage:
■ The required software plug-in is installed automatically with NetBackup.
■ Login credentials to the disk array must be configured on the media server.
■ Only the media servers that are configured as data movers for the
OpenStorage implementation appear in the media server list. (For
OpenStorage, NetBackup media servers function as data movers.) If a media
server does not appear in the list, verify that the software plug-in is
installed and that logon credentials are created.
For PureDisk storage:
■ See the Veritas NetBackup PureDisk Remote Office Edition Administrator’s
Guide for the media server requirements.
242 Storage units, unit groups, and lifecycle policies
Staging backups to initial storage, then final storage
Stage II
When the relocation schedule runs, NetBackup creates a data management job.
The job looks for any data that can be copied from the disk staging storage unit
to the final destination. The Job Details in the Activity Monitor identify the job
as one associated with basic disk staging. The Job Details list Disk Staging in the
job’s Data Movement field.
When NetBackup detects a disk staging storage unit that is full, it pauses the
backup. Then, NetBackup finds the oldest images on the storage unit that have
been successfully copied onto the final destination. NetBackup expires the
images on the disk staging storage unit to create space.
Storage units, unit groups, and lifecycle policies 245
Basic disk staging
administrator understand the life expectancy of the image on the Stage I storage
unit.
The size and use of the file system of the Stage I storage unit directly impacts
the life expectancy of the image before it is copied to the Stage II storage unit.
Symantec recommends a dedicated file system for each disk staging storage
unit.
Incremental backups are done Monday through Saturday, with full backups
done on Sunday. The full backups are sent directly to tape, and do not use basic
disk staging.
Each night’s total incremental backups are sent to a disk staging storage unit
following day the relocation schedule runs on the disk staging storage unit and
copies the previous night’s incremental backups to the final destination, a Media
following formula:
Minimum size = Max data per cycle * (1 cycle + 1 cycle for safety)
To determine the average size for the storage unit in this example, use the
following formula:
Average size = Average data per cycle * (number of cycles to keep data + 1 cycle
for safety)
2.8GB = 400MB * (6 + 1)
■ Maximum disk size for a basic disk staging storage unit
The maximum disk size is the recommended size needed to accommodate a
certain level of service. In this example, the level of service is that disk images
remain on disk for one week.
To determine the maximum size for the storage unit in this example, use the
following formula:
Maximum Size = Max data per cycle * (# of cycles to keep data + 1 cycle for
safety)
For example: 4.9 GB = 700MB * (6 + 1)
Run the nbdevquery command to display the status for the disk pool, including
the potential free space. Use the following options, where:
-stype server_type
Specifies the vendor-specific string that identifies the storage server type.
For a BasicDisk storage unit, enter BasicDisk.
-dp
Specifies the disk pool name. For a basic disk type, the disk pool name is the
name of the BasicDisk storage unit.
Storage units, unit groups, and lifecycle policies 247
Basic disk staging
name : <Internal_16>
id : <C:\>
diskpool : <NameBasic::server1::BasicDisk>
disk_media_id : <@aaaaf>
total_capacity : 0
free_space : 0
potential_free_space: 0
committed_space : 0
precommitted_space : 0
nbu_state : 2
sts_state : 0
flags : 0x6
num_read_mounts : 0
max_read_mounts : 0
num_write_mounts : 1
max_write_mounts : 1
■ Select whether this directory can reside on the root file system or
system disk. For more information, see “Directory can exist on the root
file system or system disk” on page 228.
Enter the maximum concurrent jobs that are allowed to write to this
storage unit at one time. For more information, see “Maximum
concurrent jobs” on page 231.
■ Enter a Low water mark value. For more information, see “Low water
mark” on page 230.
The High water mark does not apply to basic disk staging. For more
information, see “High water mark” on page 230.
■ Check the Enable temporary staging area option. Once the option is
enabled, the Staging Schedule button becomes enabled.
■ Click the Staging Schedule button. The Disk Staging dialog box
appears.
4 Complete the Disk Staging dialog box. The dialog box is similar to the
scheduling dialog box used to configure policies. The differences appear on
the Attributes tab:
■ The schedule name defaults to the storage unit name.
■ Select the priority that the relocation jobs that are started from this
schedule have compared to other types of jobs. For more information,
see “Priority of relocation jobs started from this schedule” on page 250.
■ Select whether to create Multiple Copies. With the Multiple copies
attribute enabled, NetBackup can create up to four copies of a backup
simultaneously. For more information, see “Multiple copies” on
page 131.
Note: For disk staging storage units, the Maximum backup copies
Global host property must include an additional copy beyond the
number of copies that are indicated in the Copies field.
■ Select a storage unit to contain the images from this storage unit upon
relocation. For more information, see “Final destination storage unit”
on page 250.
■ Select a volume pool to contain the images from this storage unit upon
relocation. For more information, see “Final destination volume pool”
on page 250.
■ Select a media owner to own the images from this storage unit upon
relocation. For more information, see “Final destination media owner”
on page 250.
Storage units, unit groups, and lifecycle policies 249
Basic disk staging
■ Select whether to use an alternate server for the images from this
storage unit upon relocation. For more information, see “Use alternate
read server” on page 251.
5 Click OK to accept the disk staging schedule.
6 Click OK to add the storage unit.
Figure 5-8 Disk Staging Schedule for a basic disk staging storage unit
Name
The schedule name for a disk staging schedule automatically defaults to the
name of the storage unit.
250 Storage units, unit groups, and lifecycle policies
Basic disk staging
The path to the disk or directory must be identical for each media server that is
If the backup image is on tape, the media servers must share the same tape
If the backup image is on a robot that is not shared or a stand-alone drive, the
media must be moved to the new location. An administrator must move the
media, inventory the media in the new robot, and execute bpmedia
To avoid sending data over the network during duplication, specify an alternate
■ Connected to the storage device that contains the original backups (the
source volumes).
■ Connected to the storage device that contains the final destination storage
units.
If the final destination storage unit is not connected to the alternate read server,
data is sent over the network.
A storage lifecycle policy is a storage plan for a set of backups. A lifecycle policy
is configured within the Storage Lifecycle Policies utility
Essentially, a lifecycle is a list of destinations where copies of the backup images
are stored, along with the prescribed retention period for each copy. After a
lifecycle is configured, the lifecycle process works to create copies of the images
on each destination. NetBackup retries the copies as necessary, to ensure that all
copies are created.
A storage lifecycle policy can also be set up to provide staging behavior.
Lifecycles offer the opportunity for users to assign a classification to the data at
the policy level. A data classification represents a set of backup requirements,
which makes it easier to configure backups for data with different requirements.
For example, email data and financial data.
3 The retention type that is selected for the destinations determines how long
the backup resides on the destination. Eventually, NetBackup deletes the
backup from the destinations to create more disk space.
Depends on high
and low watermark
settings
Note: The number of destinations that are added to the lifecycle cannot exceed
the Maximum Backup Copies setting in the Global host properties. The lifecycle
cannot be saved until the destinations is decreased, or until the Maximum
Backup Copies is increased.
Storage units, unit groups, and lifecycle policies 257
Storage Lifecycle Policies
Note: Duplication jobs can be controlled using the nbstlutil command. For
more information, see “Using nbstlutil to administrate lifecycle operations” on
page 265.
To make sure that copy 1 is written to disk, enter the disk type destination
before the tape destination.
Copy 1 on disk
Copy 2 on tape
Copy 3 on disk
Storage destinations
The storage destination list contains all the destinations (storage units and
storage unit groups) that the storage lifecycle can use. The list includes the
storage that is used for the original backups as well as storage that is used for
duplication at a later time.
■ All configured backup destinations for the storage lifecycle must be on the
same media server.
■ One of the destinations must be of a fixed retention type.
■ There must be at least one valid backup destination in the destination list.
Storage unit
Indicate the storage unit where the backups are to be written. The following
destinations can be selected:
■ Any available
■ Media Manager storage units (tape)
■ Disk storage units (no BasicDisk, SnapVault, or disk staging storage units)
■ Storage unit groups (may contain no BasicDisk, SnapVault, or disk staging
storage units). A storage lifecycle policy can point to a storage unit group
that contains a BasicDisk storage unit. However, NetBackup does not select
BasicDisk storage units from a storage group for a lifecycle policy.
Note: The storage destination list cannot contain other storage lifecycles.
Storage units or storage unit groups may appear in more than one lifecycle.
Storage units or storage unit groups may be used in a storage lifecycle while also
being used as stand-alone units.
Volume pool
The Volume pool option is enabled for tape storage units.
Media owner
A Media owner can be selected. A Media owner is a group of NetBackup servers
that are used for a common purpose. (See “Configuring server groups for media
sharing” on page 615.)
260 Storage units, unit groups, and lifecycle policies
Storage Lifecycle Policies
Note: Every lifecycle must contain at least one destination with a fixed retention
period. The destination can be a backup or a duplication destination.
The images are not deleted if all copies have not completed. For example, the
administrator selects a fixed retention for a tape device to keep images on tape
for two days. If the images have not been duplicated to all of the destinations in
the lifecycle after two days, the images are not expired. The image remains on
the tape device until all copies have been created. (Or, until the administrator
uses nbstlutil utility to intervene.)
Retention period
The Retention period specifies exactly how long NetBackup retains the backups
before the backups are expired. To set the retention period, select a time period
(or level) from the drop-down list.
Note: If more space is needed, any images that are not past the Desired cache
period may be deleted. However, an image is never deleted if it has not been
duplicated to all destinations in the lifecycle, even if the image is past its
retention period. For more information, see “Writing multiple copies using a
lifecycle” on page 256.
To see exactly when the storage destination reaches the low water mark value is
difficult. A backup can occur at the same time as the expiration process occurs.
After the backup is complete, the low water mark may be slightly greater than
its lowest possible value.
Capacity managed retention and the storage units that use Single
instance store
Staged capacity managed is selectable for any disk storage unit that is allowed
in a lifecycle. However, for the disk types that support single-instance store
(SIS), Staged capacity managed functions to various degrees. In order for
Staged capacity managed to operate, NetBackup must know how much space a
262 Storage units, unit groups, and lifecycle policies
Storage Lifecycle Policies
backup image uses. With SIS enabled on the storage unit, NetBackup cannot
know exactly how much space a particular backup image occupies.
The following storage unit configurations use SIS:
■ PureDisk storage units
■ NearStore storage units that have either the Enable file system export
option enabled or the Enable block sharing option enabled.
■ Some OpenStorage storage units, depending on the vendor characteristics.
Data classification
The Data classification allows the NetBackup administrator to classify data
based on relative importance. A classification represents a set of backup
requirements. When data must meet different backup requirements, consider
assigning different classifications.
For example, email backup data may be assigned to the silver data classification
and financial backup data backup may be assigned to the platinum
classification. The financial data is assigned to the higher classification of
platinum because backups of the financial data are consider more important.
The Data classification defines the level of data that the storage lifecycle is
allowed to process. The Data classification drop-down menu contains all of the
defined classifications. To select a classification is optional.
One data classification can be assigned to each storage lifecycle policy and
applies to all destinations in the lifecycle. A storage lifecycle is not required to
have a data classification.
Storage units, unit groups, and lifecycle policies 263
Storage Lifecycle Policies
If a data classification is selected, the storage lifecycle stores only those images
from the policies that are set up for that classification. If no classification is
indicated, the storage lifecycle accepts images of any classification or no
classification.
Then, each batch of images is copied as a set in one duplication job, instead of
The NetBackup administrator can change how large the batch files can become,
or how frequently batch jobs are requested. To do so, the administrator creates
/usr/openv/netbackup/db/config
MIN_KB_SIZE_PER_DUPLICATION_JOB
The MIN_KB_SIZE_PER_DUPLICATION_JOB parameter default is 8 gigabytes.
This parameter indicates the total size that the image batch can reach before a
duplication job is run for the batch.
The lifecycle looks for completed images to be added to a batch every five
minutes. The lifecycle does not request a duplication job until either:
■ the total size of the images in a batch reaches the minimum size as indicated
by MIN_KB_SIZE_PER_DUPLICATION_JOB, or
■ the MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB time has
passed. This parameter determines the maximum time between batch
requests.
MAX_KB_SIZE_PER_DUPLICATION_JOB
The MAX_KB_SIZE_PER_DUPLICATION_JOB parameter default is 25 gigabytes.
This parameter determines how large the image batch can grow. When the size
reaches the size as indicated by this parameter, no more images are added to the
batch.
MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB
The MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB parameter
default is 30 minutes. If the minimum batch size is not reached by the time
indicated, the lifecycle requests a duplication job, regardless of the size.
Storage units, unit groups, and lifecycle policies 265
Storage Lifecycle Policies
MIN_KB_SIZE_PER_DUPLICATION_JOB 8192
MAX_KB_SIZE_PER_DUPLICATION_JOB 25600
MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB 30
nbstlutil cannot affect the jobs that are currently running. Use the Activity
/usr/openv/netbackup/bin/admincmd/nbstlutil
■ List the contents of the EMM database. The tables about the
lifecycle-processed images can be printed. Support may request this
information to troubleshoot a lifecycle problem.
■ Cancel pending duplication operations on the selected image copies. When a
duplication job is canceled, NetBackup considers the job complete and does
not try to run another duplication job.
■ Inactivate (or suspend) pending and future lifecycle operations on selected
image copies. NetBackup retains the image information so that processing
can resume.
■ Activate (or resume) suspended lifecycle operations on selected image
copies.
See NetBackup Commands for UNIX and Linux for a description of all the
options available for nbstlutil.
Use the nbstlutil command in the case of a hardware problem that may
require more than 15 minutes to resolve. That is, the problem may take longer to
resolve than three duplication sessions five minutes apart.
For example, a duplication job fails because the library doesn’t contain enough
blank tapes. It may take longer than 15 minutes to place additional blank tapes
into the tape library. The administrator may not want to wait 24 hours for the
next duplication session. The nbstlutil command can be used to inactivate
the lifecycle while tapes are added. When ready, the lifecycle can be activated
and duplication jobs would begin.
Storage units, unit groups, and lifecycle policies 267
Storage unit groups
Storage unit groups allow you to identify specific storage units as a group. A
storage unit group name can be specified in a policy in the same way that
individual storage units can be specified. When a storage unit group is used in a
policy, only the storage units that are specified in the group are candidates for
the backup.
Prioritized
NetBackup chooses the first storage unit in the list that is not busy, down, or out
of media. Also, the storage unit must not have reached the maximum concurrent
jobs setting. When one of the specified conditions occurs, the next storage unit
in the list is examined until NetBackup finds an available storage unit. If one is
not available or if one does not have enough available space, the job fails and is
not queued. (Default.)
Failover
NetBackup chooses the first storage unit in the list that is not down, out of
media, or full. If a storage unit is only busy, the policy waits to write to it. The
other storage units are used as failovers.
NetBackup queues a job to wait for the first storage unit if the maximum
concurrent jobs setting is reached.
Round robin
NetBackup chooses the least recently selected storage unit in the list as each
new job is started. If a storage unit is not available, or if no unit has available
space, the job fails and is not queued. NetBackup does not continue to select the
same storage unit.
Load balance
The Load balance option allows NetBackup to select storage units based on a
capacity-managed approach. NetBackup avoids sending jobs to busy media
servers.
The selection is based on the following factors:
268 Storage units, unit groups, and lifecycle policies
Figure 5-11 The Load balance option cannot be selected for a storage unit group
that contains a BasicDisk storage unit
Note: Symantec recommends selecting Load balance for disk staging storage
units within a storage unit group.
storage units take precedence over the defined sequence of storage units in the
group.
You may have set up a storage unit to be On demand only. If the unit is in a
storage unit group that a policy requires, the On demand only option is satisfied
and the device is used. For more information, see “Policy storage” on page 91.
■ “Disaster recovery emails and the disaster recovery file” on page 317
NetBackup catalogs are the internal databases that contain information about
NetBackup backups and configuration. Backup information includes records of
the files that have been backed up and the media on which the files are stored.
The catalogs also contain information about the media and the storage devices.
Since NetBackup requires the catalog information to restore backups, configure
a catalog backup before using NetBackup for regular client backups. Then,
schedule the catalog backups to occur on a regular basis thereafter. Without
regular catalog backups, you risk losing regular backups if there is a problem
with the disk that contains the catalogs.
/usr/openv/
NBDB.db server.conf
EMM_DATA.db databases.conf
EMM_INDEX.db
/class /error /images /vault
NBDB.log
/class_ /config /jobs
BMRDB.db
template
/failure_history
BMRDB.log
/client /media
BMR_DATA.db
BMR_INDEX.db
/client_1 /Master
vxdbms.conf
/Media_server /client_n
Relational database Configuration files
files Image database
Image database
The image database (/usr/openv/netbackup/db/images) contains
subdirectories for each client that is backed up by NetBackup, including the
master server and any media servers.
The image database contains:
■ Image files (files that store only backup set summary information)
■ Image .f files (files that store the detailed information of each file backup)
The image database is the largest part of the NetBackup catalog. It consumes
about 99% of the total space that is required for the NetBackup catalog. While
most of the subdirectories are relatively small in the NetBackup catalogs,
/images can grow to several tens, or even hundreds of gigabytes. The image
database on the master server may grow too large to fit on a single tape. The
database growth is an important consideration for offline, cold catalog backups.
Image database growth depends on the number of clients, policy schedules, and
the amount of data that is backed up.
278 NetBackup Catalog
If the image catalog becomes too large for the current location, consider moving
it to a file system or disk partition that contains more space. For more
The image database component of the NetBackup catalog uses the .f files in
binary format for Windows, Solaris, HP_UX, Compaq Tru64 UNIX, AIX, and
Linux platforms.
database to the binary format. (See “Catalog conversion utility” on page 354.)
Image files
Each image file is an ASCII file, generally less than 1 kilobyte in size. An image
file contains only backup set summary information. For example, the backup ID,
the backup type, the expiration date, fragment information, and disaster
recovery information.
Image .f files
The binary catalog may contain one or more image .f files. This type of file is
also referred to as a files-file. The image .f file may be large because it contains
the detailed backup selection list for each file backup. Generally, image files
range in size from 1 kilobyte to 10 gigabytes.
The file layout determines whether the catalog contains one .f file or many .f
files. NetBackup configures the file layout automatically, based on the size of the
binary catalog. NetBackup uses one of two layouts: single file layout or multiple
file layout.
When the backup file of one catalog backup is less than 4 megabytes, NetBackup
stores the information in a single image.f file. The image.f file is always
Separating the additional .f files from the image .f file and storing the files in
the catstore directory improves performance while writing to the catalog.
The main image.f file is always exactly 72 bytes.
-rw- 1 root other 72 Aug 30 00:40 test_1030680524_INCR.f
-rw- 1 root other 804 Aug 30 00:08 catstore/test_1030680524_INCR.f-list
-rw- 1 root other 1489728 Aug 30 00:39 catstore/test_1030680524_INCR.f_imgDir0
-rw- 1 root other 0 Aug 30 00:40 catstore/test_1030680524_INCR.f_imgExtraObj0
-rw- 1 root other 1280176 Aug 30 00:39 catstore/test_1030680524_INCR.f_imgFile0
-rw- 1 root other 192 Aug 30 00:40 catstore/test_1030680524_INCR.f_imgHeader0
-rw- 1 root other 0 Aug 30 00:40 catstore/test_1030680524_INCR.f_imgNDMP0
-rw- 1 root other 9112680 Aug 30 00:39 catstore/test_1030680524_INCR.f_imgRecord0
-rw- 1 root other 2111864 Aug 30 00:39 catstore/test_1030680524_INCR.f_imgStrings0
-rw- 1 root other 11 Aug 30 00:40 catstore/test_1030680524_INCR.f_imgUserGroupNames0
280 NetBackup Catalog
For information about how the catalog uses Sybase ASA, see Appendix A,
“NetBackup relational database” on page 697.
NetBackup Catalog 281
What is a NetBackup catalog?
Catalog protection
In order for NetBackup to restore any file, NetBackup needs information from
the catalog to determine where the backup for the file is located. Without a
catalog, NetBackup cannot restore data.
Because the catalog plays an integral part in a NetBackup environment, a
particular type of backup--a catalog backup--protects the catalog. A catalog
backup backs up catalog-specific data as well as produces disaster recovery
information.
As additional protection for the catalog, you may consider archiving the catalog
as well. (See “Archiving the catalog” on page 318.)
Catalog backups
A catalog backup is configured separately from regular client backups by using
the Catalog Backup Wizard. The catalog can be stored on a variety of media.
Note: Configure a catalog backup before you run any regular backups.
Note: If portions of the catalog are relocated, note the changes so that
subsequent catalog backups are aware of the locations of all the catalog
components. In the event that a catalog recovery is needed, the same alterations
must be implemented before the recovery of the catalog.
Choose the catalog backup method that works best for your environment:
■ Online, hot catalog backup (recommended method)
This type of catalog backup is for active environments in which continual
backup activity occurs. It is considered an online, hot method because it can
be performed while regular backup activity occurs. This type of catalog is
policy-based and can span more than one tape. It also allows for
incremental backups, which can significantly reduce catalog backup times
for large catalogs.
NetBackup Catalog 283
Catalog protection
Online, hot catalog backups use media from the CatalogBackup volume pool
only. For more information, see “Online, hot catalog backup method” on
page 283.
■ Offline, cold catalog backup
This type of catalog backup is for environments in which periods of no
backup activity exist. It is considered an offline, cold backup because it
should not be run when regular backup activity occurs. For Sybase ASA, the
databases (NBDB and BMRDB) are shut down during the backup. This type
of catalog backup must fit on a single tape.
Offline, cold catalog backups use media from the NetBackup volume pool
only. For more information, see “Offline, cold catalog backup method” on
page 296.
See “To configure an online, hot catalog backup using the policy utility”
on page 293.
To configure an online, hot catalog backup using the catalog backup wizard
Note: Online, hot catalog policies (policy type NBU-Catalog) write only to
media in the CatalogBackup volume pool. This procedure assumes that a
storage device is configured and media is available in the CatalogBackup
volume pool. For more information, see “Adding volumes” on page 508.
4 Click Next.
NetBackup Catalog 285
Catalog protection
5 On the Catalog Backup Policy screen, select a policy from the list of existing
catalog backup policies.
6 Or, to create a new catalog backup policy, select Create a new catalog
backup policy.
Click Next to launch the Policy Name and Type screen of the Backup Policy
wizard.
7 Enter the policy name.
Notice that NBU-Catalog is automatically selected as the policy type.
Type a unique name for the new policy in the Add a New Policy dialog box.
For more information, see “NetBackup naming conventions” on page 631.
286 NetBackup Catalog
Catalog protection
Click OK.
8 Select the backup type. (User Backup does not apply for NBU-Catalog
policies.)
NetBackup Catalog 287
Catalog protection
The selection After each backup session refers to a period when no regular
backup policy is running.
By default, a frequency-based schedule is selected. A frequency-based
schedule ensures that the catalog backup has an opportunity to run in busy
environments where backup jobs are running.
Note: If online, hot catalog backups are scheduled to run concurrently with
other backup types on the master server, see “Running online, hot catalog
backups concurrently with other backups” on page 294.
10 In the Start Window screen, define a window of time during which the
catalog backup can start. The scheduled windows (Off hours, Working hours,
288 NetBackup Catalog
Catalog protection
All day) are preset in the wizard, but can be customized using the Policies
utility.
User Window selections are disabled, as regular users (those who are not
NetBackup administrators) cannot start catalog backups.
11 Select where each disaster recovery image file can be saved on disk. The
image file contains the disaster recovery information.
NetBackup Catalog 289
Catalog protection
Note: Symantec recommends that you save the image file to a network
share or a removable device. Do not save the disaster recovery information
to the local machine.
Enter the path to the directory where the disaster recovery information can
If necessary, enter the logon and password information to access the NFS
share.
Make sure that email notification is enabled in your environment. For more
information on the email and the attached disaster recovery file, see
“Disaster recovery emails and the disaster recovery file” on page 317. Also,
see “Send in an email attachment” on page 197.
Note: The disaster recovery email is not sent to the address that is specified
in the Global Attributes property. The Administrator’s email Address
specifies the addresses where NetBackup sends notifications of scheduled
backups or administrator-directed manual backups.
13 The last screen of the policy wizard lets you know that once the policy is
created, you can make changes in NetBackup Management > Policies.
14 The Catalog Backup Wizard resumes, with the new policy listed.
To configure an online, hot catalog backup using the backup policy wizard
Using the Backup Policy Wizard to create an online, hot catalog backup policy is
similar to using the Catalog Backup Wizard.
Note: Online, hot catalog policies (policy type NBU-Catalog) write only to
media in the CatalogBackup volume pool. This procedure assumes that a
storage device is configured and media is available in the CatalogBackup
volume pool. For more information, see “Adding volumes” on page 508.
Note: Symantec recommends that the image file be saved to a network share
or a removable device. Do not save the disaster recovery information to the
local machine.
Disk Information
■ Path to the disk:
For UNIX master servers, specify a local directory or NFS share.
For Windows master servers, specify a local directory or UNC path
(CIFS Windows share).
■ Logon information that is used to:
■ Access the NFS share for UNIX master servers.
NetBackup Catalog 293
Catalog protection
Note: Online catalog backups must use media servers at version 6.0 or later
to store catalog backup data. If your installation contains 5.x and 6.0 media
servers, do not select Any Available for the destination Policy Storage Unit,
since it is possible that the 5.x media server could be selected.
Note: The Clients tab does not apply to the NBU-Catalog policy and is not
displayed.
6 The Disaster Recovery tab appears for NBU-Catalog policies only. The tab
contains information regarding the location of data crucial to disaster
recovery:
■ The path to the directory where the disaster recover information can be
saved.
■ The logon and password information to the share.
■ The email address(es) where disaster recovery reports can be sent.
■ A critical policy list, which contains the names of policies that back up
critical data. Media that contains critical policy backups is listed on the
NetBackup Disaster Recovery Report that is generated when the online
catalog backup is run.
For information on the Disaster Recovery tab settings, see “Disaster
Recovery tab” on page 196.
Note: Additional child catalog jobs are created for 5.x media servers and the
BMR database if a remote EMM server is configured.
Because of this difference, running a standard policy type backup that includes
the /usr/openv/netbackup/db/images/ directory can adversely affect
incremental hot catalog backups. When standard backups run, they reset the file
access time (atime). In turn, this changes the ctime for files and directories. If
an incremental catalog backup runs, it sees that the ctime has changed and
unnecessarily backs up the files; files that may not have changed since the last
catalog backup.
To avoid additional processing during hot catalog backups, Symantec
recommends the following:
■ If incremental hot catalog backups are configured, exclude the NetBackup
/usr/openv/netbackup/db/images/ directory from standard backups.
To exclude that directory, create a
/usr/openv/netbackup/exclude_list file on the master server.
■ Cold catalog backups also change the ctime. Do not configure both cold
catalog backups and incremental hot catalog backups to run in a NetBackup
configuration.
Catalog protection
To configure an offline, cold catalog backup using the catalog backup wizard
Note: Offline, cold catalog policies write only to media in the NetBackup
volume pool. This procedure assumes that a storage device is configured
and media is available in the CatalogBackup volume pool. For more
information, see “Adding volumes” on page 508.
4 Specify the media server where the catalog backups are to be sent.
5 Select the media servers that should be backed up in this catalog backup.
Catalog protection
The catalog paths on the master server are added automatically during
installation. Generally, no action is required other than to ensure that the
directories are listed.
Verify that the catalogs of the master server and each media server are
included. Verify that the path names are correct and are in the correct
format.
The NETBACKUP_RELATIONAL_DATABASE_FILES directive automatically
includes the database files in the /usr/openv/db/data/ directory, as
well as vxdbms.conf, server.conf, and databases.conf. (If the files
have been relocated to different directories using nbdb_move, the locations
are automatically determined and the files are included.)
If NetBackup Access Control (NBAC) is used in the NetBackup
configuration, add the following directives for each host in the NBAC
domain:
[host:]nbat
[host:]nbaz
Note: For UNIX master servers, do not include the NetBackup master server
configuration file in the offline catalog backup file list.
(/usr/openv/netbackup/bp.conf) If bp.conf is included in the list, it
must not be recovered until all other catalog recovery is completed.
If NetBackup cannot find or follow a path, the entire catalog backup fails.
Notes Regarding the Catalog File Locations List
■ If you have moved the location of the catalog on the master server, the
new location must be specified.
NetBackup Catalog 301
Catalog protection
9 Select a destination volume from the drop-down list to store the catalog
backup.
Note: Note the media ID of the volume that was selected to know which
volume contains catalog backups.
302 NetBackup Catalog
Catalog protection
10 You may prefer to back up the catalog to two different locations. The catalog
backup alternates for each catalog backup.
Alternate destinations adds protection in the event that a disk or tape that
NetBackup always backs up to the media that was not used for the previous
catalog backup.
12 Enter the path to the alternate destination for the catalog backup.
Caution: Back up the catalogs often. If catalog backup files are lost, the changes
that were made between the last catalog backup and the time of the disk crash
are lost.
NetBackup Catalog 305
Catalog protection
14 The final wizard screen displays the total number of catalog backup policies
that are configured for this master server. Click Finish to complete the
wizard.
Note: Offline, cold catalog policies write only to media in the NetBackup
volume pool. This procedure assumes that a storage device is configured
and media is available in the CatalogBackup volume pool. For more
information, see “Adding volumes” on page 508.
The tab reminds the users that another type of catalog backup is available that
might serve their needs better: the online, hot catalog backup. (See “Catalog
backups” on page 282.)
NetBackup Catalog 307
Catalog protection
Media Server
The following setting applies only to NetBackup Enterprise Server:
The Media Server setting specifies the name of the media server to which
catalog backups are sent. This defaults to the master server where you are
running the NetBackup Administration Console. To choose a server, select one
from the drop-down menu. The list shows all servers that have a storage unit
that is defined on the current master server.
If you back up the catalogs to a media server, modify the NetBackup catalog
backup paths on the master server using the Catalog Files tab. (See “Catalog
files tab” on page 312.)
Ensure that the media server is named in the bp.conf file on the master server.
On NetBackup Server, Media Server cannot be changed and is the NetBackup
server where the catalogs reside.
Last Media Used
The Last Media Used setting shows the media ID (for Removable Media) or the
absolute path (for disk) that contains the last NetBackup catalog backup. The
value in this field is the value that you specified for either Media 1 or Media 2.
These are the media that NetBackup alternates between for catalog backups.
Media 1 and Media 2 Areas
308 NetBackup Catalog
Catalog protection
The Media 1 and Media 2 Areas setting specifies the media to use for the catalog
backups. You do not have to assign both Media 1 and Media 2. If you do assign
both, NetBackup alternates between the media.
Media Type
The Media Type setting specifies the media type. Select one from the drop-down
menu:
■ None: No media is assigned
■ Disk: A directory on a disk drive
■ Removable Media: A volume that is in a robot or drive under control of
Media Manager
Depending on the storage devices that are available, Symantec recommends the
following choices for Media Type:
1 If you use a robot or a tape stacker, choose Removable Media to select the
automated device.
2 If you use a stand-alone storage device for catalog backups, choose
Removable Media and use the stand-alone device.
3 If you use only one stand-alone drive (no robot or tape stacker), the most
convenient method is to choose Disk for the media type. Send the catalog
backups to a hard drive. The hard drive that you use for the catalog backup
must be different than the hard drive where the catalogs reside. By default,
the catalogs are stored in the following locations:
/usr/openv/netbackup/db
/usr/openv/var/global
/usr/openv/db/data
If you choose to back up the catalog to disk, the destination of the catalog
backup must be on a different drive.
Caution: The safest way to protect your data is to save all backups to removable
media. Move a full set of the media to off-site storage on a regular basis. A
backup that is written only to disk shares the same risks as the computers being
backed up. A natural disaster is more likely to destroy both the primary data and
the backups if the backups are written only to disk.
If the disks holding the catalogs and the catalog backup are both destroyed,
recovering your business data is much more difficult. Assuming the backups are
on tape, recovering without the catalog backup means manually importing all of
the backup tapes to rebuild the catalogs. Importing consumes the time that you
may not want to spend when you need to resume business activities.
NetBackup Catalog 309
Catalog protection
4 If you have only one stand-alone drive (no robot or tape stacker) and
inadequate space on a different hard drive, choose Removable Media. In this
situation, you must back up the catalogs to the same tape drive as the
backups of your business data. To back up to single tape drive involves
swapping tapes in and out of the drive each time the catalogs are backed up.
Swapping tapes is inconvenient, but it is required because NetBackup does
not place catalog backups and the backups of business data on the same
tape.
Media ID
If you’ve chosen Removable Media, specify a valid media ID.
The volume that is specified must be configured under Media in the same
manner as other NetBackup volumes. The media ID must appear under Media
and Device Management > Media. The volume must also meet the following
requirements:
■ The volume must be in the NetBackup volume pool. To verify, look under
Media and ensure that the Volume Pool column for the media ID displays
NetBackup.
■ The volume cannot be currently assigned to NetBackup for backups because
NetBackup does not mix catalog backups and regular backups on the same
media.
To locate an available volume, expand Media and Device Management >
Media. Find a volume where the Time Assigned column is empty and the
Status column is 0. Once a catalog backup occurs, the Time Assigned and
the Status column for the volume updates.
Note: If a column does not appear, size the columns by right-clicking in the pane
and selecting Columns from the shortcut menu.
The Last Written information under Media 1 and Media 2 indicates when the
volume that is specified in the Media ID field was last used. The value is never if
the volume has never been used for NetBackup catalog backups.
Note: If the media ID for a volume that was used for catalog backups is deleted,
then added back, NetBackup changes the Last Written date and time. However,
the contents of the volume itself are not altered until the next time the volume is
used for a backup.
The Allocated information under Media 1 and Media 2 indicate when the media
was allocated for NetBackup catalog backups.
Notes on the Media ID
310 NetBackup Catalog
Catalog protection
■ To delete the media for Media 1 or Media 2, set the Media Type value to
None. Do not use backspace to leave the Media ID box blank.
■ If you delete a volume from the catalog backup configuration, Media
Manager makes the volume available for reassignment. Reassigning the
volume can cause problems if, for example, you temporarily back up the
catalog to a different volume.
■ You must manually track the media that is used for catalog backups.
NetBackup does not keep a record of catalog backup media in its catalogs as
it does with other backup media. If NetBackup tracks catalog backup media
in the catalog, and the disk containing the catalogs crashes, the record is
lost with the catalogs.
A convenient way to track the media is to indicate an email address in the
Global Attributes properties. NetBackup sends an email that includes the
status of each catalog backup and the media ID that was used. Print the
email or save it on a disk other than the disk containing the catalogs. (See
“Global Attributes properties” on page 435.)
If the catalogs are intact, you can also find these media IDs in the Media
Manager volume listing. The Status column shows 1 for these volumes.
However, these IDs do not appear in the NetBackup media reports.
Pathname (Disk Media Type)
For disk media, the Pathname is the path to the directory where you want to
store the catalog backup. Type the path in the field. For example:
/nb/dbbackup
/usr/openv/var/global
/usr/openv/db/data
■ Ensure that the disk has adequate space for the catalogs. If the disk fills up,
the catalog backups fail.
■ Ensure that the path is a directory rather than a file. If the path is a file, an
error occurs when the backup is done (not when you specify the path).
■ The following rule applies to the path you specify:
In addition to the platform-specific file path separators (/ and \) and colon
(:) within a drive specification on Windows, follow the NetBackup naming
conventions. (See “NetBackup naming conventions” on page 631.)
Caution: Back up the catalogs often. If catalog backup files are lost, the changes
that were made between the last catalog backup and the time of the disk crash
are lost.
This schedule type requires that no jobs are running in order for the catalog
backup to run.
Click to navigate to
a directory or file
The catalog paths on the master server are added automatically during
installation. Generally, no action is required other than to ensure that the
directories are listed.
In the case of NetBackup Enterprise Server, the master server and media servers
may reside on different machines. Therefore, the paths to the NetBackup
database on the media servers are not automatically added during installation.
You must add the paths to the file list.
The NETBACKUP_RELATIONAL_DATABASE_FILES directive automatically
includes the database files in the /usr/openv/db/data/ directory, as well as
vxdbms.conf, server.conf, and databases.conf. (If the files have been
relocated to different directories using nbdb_move, the locations are
determined automatically and are included.)
NetBackup Catalog 313
Catalog protection
Note: The file names in the Catalog Files Location list are case-sensitive. The
catalog backup fails if the entries are typed without regard to case.
Note: For UNIX master servers, do not include the NetBackup master server
configuration file in the offline catalog backup file list.
(/usr/openv/netbackup/bp.conf) If bp.conf is included in the list, it
must not be recovered until all other catalog recovery is completed.
■ Make sure that the list does not contain invalid paths. Do so especially if you
have moved the catalog files, have deleted old paths, or have added new
paths to the catalog backup configuration. If NetBackup cannot find or
follow a path, the entire catalog backup fails.
■ On UNIX systems, if /usr/openv/netbackup/db/images is a symbolic
link to another file system, you must specify the true location of the images
directory here. Symbolic links do not apply to Windows.
■ The entire catalog backup fails if the final component in a UNIX path is a
symbolic link. While NetBackup follows links at other points in the path,
NetBackup does not follow a link when a link is the final component. If any
other part of a listed path is a symbolic link, NetBackup saves the actual
path during the backup.
■ The files that are associated with the NetBackup relational databases are
automatically included in the catalog backup and don’t need to be listed
here. (NBDB and BMRDB.) The paths are dynamically generated during the
backup since the locations of these files can change.
The files in the following directory contain license key and authentication
information:
/usr/openv/var
The paths that you must add depend on the version of NetBackup that was
installed on the media server.
■ For UNIX media servers running NetBackup versions earlier than 6.0, add
the following two paths:
■ media_server_name:/usr/openv/netbackup/db/media
The files in this directory contain information about the files that were
backed up or archived from client workstations.
■ media_server_name:/usr/openv/volmgr/database
The files in this directory contain information about the media and
devices being used in the configuration.
■ For UNIX media servers running NetBackup version 5.x, also include the
following path:
media_server_name:/usr/openv/var
For example, to add the paths for a UNIX NetBackup 5.x media server named elk,
create the following entries:
elk:/usr/openv/netbackup/db/media
elk:/usr/openv/volmgr/database
elk:/usr/openv/var
For example, to add the catalog files of a Windows NetBackup 5.x media server
(mars), create the following entries. Install_path is the directory where
NetBackup is installed:
mars:C:Install_path\NetBackup\db
mars:C:Install_path\Volmgr\database
mars:C:Install_path\NetBackup\var
The files in the db directory contain NetBackup error logs and all information
about the files that are backed up from client workstations.
316 NetBackup Catalog
Catalog protection
The files in the database directory contain information about the media and
the devices that are used in the configuration.
Note: Remember to use the backslash (\) in the paths for a Windows NetBackup
server.
NetBackup Catalog 317
Recovering the catalog
The catalog archiving feature helps users tackle the problems that large
amounts of catalog data can pose: large catalogs require a greater amount of
disk space and can be time-consuming to back up. Catalog archiving reduces the
size of online catalog data by relocating the large catalog .f files to secondary
storage. NetBackup administration continues to require regularly scheduled
catalog backups, but the backups are faster without the large amount of online
catalog data.
Catalog archiving is available on both UNIX and Windows platforms.
Note: When you consider whether to archive the .f files, note that additional
time is required to mount the tape and perform the restore.
Note: Running bpcatlist alone does not modify any catalog images. Only
when the bpcatlist output is piped to bpcatarc and bpcatrm are the
images modified and the image .f files removed.
3 Once the bpcatlist output correctly lists all the images to be archived,
pipe the output through bpcatarc and bpcatrm. For example:
bpcatlist -client all -before Jan 1 2006 | bpcatarc |
bpcatrm
NetBackup Catalog 319
Archiving the catalog
The command waits until the backup completes successfully before the
command returns the prompt. An error is reported if the catalog archive
fails.
The Activity Monitor displays a Job ID for the job. The File List for the job
(double-click the job in the Activity Monitor) displays a list of image files
that have been processed. When the job completes with a status 0, bpcatrm
removes the corresponding .f files. If the job fails, no catalog .f files are
removed.
4 To restore the catalog archive:
a Use bpcatlist to list the files that need to be restored.
b Once bpcatlist displays the proper files to restore, run bpcatres to
restore the actual files.
To restore all the archived files from Step 2, run the following
command:
bpcatlist -client all -before Jan 1 2006 | bpcatres
This command restores all the catalog archive files before Jan 1, 2006.
For more information on the archiving commands, see “Catalog archiving
commands” on page 321.
Policy name
Create a new policy that is named catarc. The catarc policy waits until
bpcatarc can activate it. Users do not run this policy. Instead, bpcatarc
activates this special policy to perform a catalog backup job, then deactivates
the policy after the job is done.
Deactivate policy
The catalog archive policy must be deactivated. On the Attributes tab, clear the
Active field.
320 NetBackup Catalog
Archiving the catalog
Type of backup
The type of backup that is indicated for the catalog archive policy must be User
Backup. The backup type is set in the Change Schedule dialog box on the
Attributes tab.
Note: Data can be lost if the retention level of the catalog archive is not long
enough. The retention level should be at least as long as the longest retention
period of the backups being archived.
You may find it useful to set up, then designate a special retention level for
catalog archive images.
Schedule
A schedule is required for catarc. The schedule for catarc must include in its
window the time bpcatarc command is run. If bpcatarc is run outside of the
schedule that is indicated in catarc, the operation fails.
NetBackup Catalog 321
Archiving the catalog
Files
On the Files tab, browse to the directory where catalog backup images are
placed:
/usr/openv/netbackup/db/images
Clients
On the Clients tab, enter the name of the master server.
portions of the catalog that are based on selected parameters. For example, date,
client, policy, schedule name, backup ID, the age of the backup image, or the
date range of the backup image. bpcatlist outputs the formatted image
For example, to archive (backup and delete) all of the .f files created before
bpcatrm
bpcatlist is also used to provide status information. For each catalog, it lists
the following information:
■ Backup ID (Backupid)
■ Backup date (Backup Date)
■ Catalog archive ID (Catarcid). After an .f file is successfully backed up, a
catalog archive ID is entered into the catarcid field in the image file. This
field is zero if the image has never been archived.
■ Archived status (S), indicating if the catalog has not been archived (1) or has
been archived (2)
■ Compressed status (C), indicating if the catalog is not compressed (0) or
compressed (1)
■ Catalog file name (Files file)
The following is an example of the bpcatlist output, showing all of the
backups for client alpha since October 23:
322 NetBackup Catalog
Archiving the catalog
Use the Catalog utility to create and configure catalog backups. Catalog backups
are required for NetBackup to protect NetBackup internal databases. The
catalogs contain setup information as well as critical information about client
backups. The catalog backups are tracked separately from other backups to
ensure recovery in case of a server crash.
The Catalog utility is also used to perform other operations on catalog
information. For example:
■ Search for backup images to verify the contents of media with what is
recorded in the NetBackup catalog.
■ Duplicate a backup image.
■ Promote a backup image from a copy to the primary backup copy.
■ Expire backup images.
■ Import expired backup images or images from another NetBackup server.
Current master
server
Right-click Catalog to
display menu
Search results
Messages pane
Specify Verify,
Duplicate, or Import,
depending on what
you want to do
Search for backup images using the criteria that is described in the following
table:
Action Select the action that was used to create the image: Verify, Duplicate, Import.
Media ID The media ID for the volume. Type a media ID in the box or select one from the scroll-down
list. To search on all media, select <All>.
Media Host The host name of the media server that produced the originals. Type a host name in the box or
select one from the scroll-down list. To search through all hosts, select All Media Hosts.
Disk type The type of the disk storage unit on which to search for backup images.
326 NetBackup Catalog
Disk pool The name of the disk pool on which to search for backup images.
Volume ID The ID of the disk volume in the disk pool on which to search for backup images.
NearStore Server The name of the NearStore server to search for images. Type a server name in the box or select
one from the scroll-down list. To search through all NearStore servers, select All NearStore
Servers.
Path To search for an image on a disk storage unit, enter the path to search or select All to search all
of the disk storage on the specified server. Appears if the disk type is BasicDisk or NearStore.
Date/time range The range of dates and times that includes all the backups for which you want to search. The
Global Attributes property Policy Update Interval determines the default range. (See “Global
Attributes properties” on page 435.)
Copies The source you want to search. From the scroll-down list, select either Primary or the copy
number.
Policy Name The policy under which the selected backups were performed. Type a policy name in the box
or select one from the scroll-down list. To search through all policies, select All Policies.
Client (host name) The host name of the client that produced the originals. Type a client name in the box or
select one from the scroll-down list. To search through all hosts, select All Clients.
Type of backup The type of schedule that created the backup. Type a schedule type in the box or select one
from the scroll-down list. To search through all schedule types, select All Backup Types.
Messages pane
The Messages pane displays messages about a task running as a background
process. The pane is displayed only if there in an informative message or error
NetBackup Catalog 327
Using the Catalog utility
message for the task. If the task completes normally, the pane is not displayed.
The Messages pane can be maximized, minimized, or closed.
You can also right-click the log file and select an action from the
scroll-down menu.
The following command promotes copy 2 of all backups of client_a, created after
January 1, 2007, to be the primary copy:
bpchangeprimary -copy 2 -cl client_a -sd 01/01/2007
bid
Where:
To find the volume that contains the duplicate backup, use the Images on Media
report. Specify the backup ID that is known (and also the client name if possible
to reduce the search time). The report shows information about both copies. (See
The bpduplicate command writes all output to the NetBackup logs so nothing
After the duplicate copy is promoted to the primary copy, use the client
interface on the client to restore files from the backup. For instructions, see the
NetBackup does not verify in advance whether the storage units and the drives
that are required for the duplicate operation are available for use. NetBackup
verifies that the destination storage units exist. The storage units must be
connected to the same media server.
The following lists describe the scenarios that present candidates for
duplication and scenarios in which duplication is not possible:
■ from one storage unit to another. ■ while the backup is created (unless making multiple
■ from one media density to another. copies concurrently).
■ from one server to another. ■ when the backup has expired.
■ from multiplex to nonmultiplex format. ■ by using NetBackup to schedule duplications
■ from multiplex format and retain the multiplex automatically (unless you use a Vault policy to
format on the duplicate. The duplicate can schedule duplication)
contain all or any subset of the backups that were ■ of offline NetBackup catalogs.
included in the original multiplexed group. The ■ when it is a multiplexed duplicate of the following:
duplicate is created with a single pass of the tape. – FlashBackup
(A multiplexed group is a set of backups that were – NDMP backup
multiplexed together during a single session.) – Backups from disk type storage units
– Backups to disk type storage units
– Nonmultiplexed backups
Note: Do not duplicate images while an offline, cold catalog backup is running.
This results in the catalog backup not having information about the duplication.
Note: If you duplicate an online, hot catalog backup, select all child jobs that
were used to create the catalog backup. All jobs must be duplicated to
duplicate the catalog backup.
332 NetBackup Catalog
Using the Catalog utility
7 Specify the volume pool where each copy is stored. The volume pool
selections are based on the policy type setting that was used for the query:
■ If the policy type was set to query for All Policy Types (default), all
volume pools are included in the drop-down list. Both catalog and
non-catalog volume pools are included.
■ If the policy type was set to query for NBU-Catalog, only catalog volume
pools are included in the drop-down list.
■ If the policy type was set to query for a policy type other than
NBU-Catalog or All Policy Types, only non-catalog volume pools are
included in the drop-down list.
NetBackup does not verify that the media ID selected for the duplicate copy
is not the same as the media ID of the volume that contains the original
backup. Because of this potential deadlock, specify a different volume pool
to ensure a different volume is used.
8 Select the retention level for the copy, or select No change.
The duplicate copy shares many attributes of the primary copy, including
backup ID. Other attributes apply only to the primary. (For example,
elapsed time.) NetBackup uses the primary copy to satisfy restore requests.
■ If No Change is selected for the retention period, the expiration date is
the same for the duplicate and the source copies. You can use the
bpexpdate command to change the expiration date of the duplicate.
■ If a retention period is indicated, the expiration date for the copy is the
backup date plus the retention period. For example, if a backup was
created on November 14, 2007 and its retention period is one week, the
new copy’s expiration date is November 21, 2007.
9 Specify whether the remaining copies should continue or fail if the specified
copy fails.
10 Specify who should own the media onto which you are duplicating images:
■ Any lets NetBackup choose the media owner, either a media server or
server group.
■ None specifies that the media server that writes to the media owns the
media. No media server is specified explicitly, but you want a media
server to own the media.
334 NetBackup Catalog
Using the Catalog utility
the same job). Since at least one copy successfully completed, the parent job
displays a successful (0) status.
Copy 1 was successful, but The parent job was successful because
Copy 2 failed at least one copy was successful
336 NetBackup Catalog
Note: To import Backup Exec media, run the vmphyinv physical inventory
utility to update the Backup Exec media GUID in the NetBackup Media
Manager database. The command needs to be run only once after creating
the media IDs in the NetBackup Media Manager database.
For information about using vmphyinv, See “Using the physical inventory
utility” on page 572.
■ Phase I:
NetBackup creates a list of expired catalog entries for the backups on the
imported volume. No actual import occurs in Phase I.
■ Phase II:
Images are selected for importing from the list of expired images that was
created in Phase I.
For information about using vmphyinv, See “Using the physical inventory
utility” on page 572.
1 To import Backup Exec media, run the vmphyinv physical inventory utility
to update the Backup Exec media GUID in the NetBackup Media Manager
database. The command needs to be run only once after creating the media
IDs in the NetBackup Media Manager database.
For information about using vmphyinv, See “Using the physical inventory
utility” on page 572.
2 To import the images from tape, make the media accessible to the media
server so the images can be imported.
3 In the NetBackup Administration Console, expand NetBackup Management
> Catalog.
4 Select Actions > Initiate Import. The Initialize Import dialog box appears.
■ The Master Server field indicates the master server where the images
are imported.
■ In the Media Server field, specify the name of the host that contains the
volume to import.
This media server becomes the media owner.
■ Indicate the location of the image. Under Image type, select whether
the images to be imported are located on tape or on disk.
■ In the Media ID field, type the Media ID of the volume that contains
the backups to import.
■ Check whether or not the images to import are password-protected
Backup Exec images.
338 NetBackup Catalog
■ In the Disk type field, select the type of the disk storage unit on
which to search for backup images. The disk types depend on
which NetBackup options are licensed.
■ If the disk type references a disk pool, enter or select the disk pool
and the disk volume ID.
■ For a BasicDisk type, enter the path to the images in the field
provided.
■ For a NearStore disk type, select or enter the name of the
NearStore server and the NearStore volume.
Notes:
■ If Backup Exec media is password-protected, the job fails without a
correct password. The logs indicate that either no password or an
incorrect password, was provided. If the media is not
password-protected and the user provides a password, the password is
ignored.
To import Backup Exec media if the password contains non-ASCII
characters:
■ Use the NetBackup Administration Console on Windows. (The
NetBackup-Java Administration Console cannot be used.)
■ Use the bpimport command.
■ To import an online, hot catalog backup, import all of the child jobs
that were used to create the catalog backup.
NetBackup Catalog 339
Using the Catalog utility
5 Click OK to begin reading the catalog information from the source volume.
6 Click on the Catalog Results tab to see NetBackup look at each image on the
tape. NetBackup determines whether or not each image has expired and can
be imported. The job also displays in Activity Monitor as an Import type.
Select the import job log to view the job results.
Note: In this phase, each tape must be mounted and read. It may take some time
to read the catalog and build the list of images.
Note: If you import any backups that consist of fragments on multiple tapes, run
the Initiate Import (Import Phase I) first. Phase I reads the catalog to determine
all the tapes that contain fragments. After Phase I, start the Import (Phase II). If
Phase II is run before Phase I, the import fails with a message. For example,
Unexpected EOF or Import of backup id failed, fragments are not consecutive.
340 NetBackup Catalog
Using the Catalog utility
2 Set up the search criteria to find images available to import by setting the
search action to Import. Be sure to select a date range that includes the
images you want to import.
3 Select the image(s) you want to import and select Actions > Import. The
Confirm Import dialog box appears.
NetBackup Catalog 341
Using the Catalog utility
4 To view the log, click the Results tab, then select the import job log.
/usr/openv/netbackup/bin/admincmd/bpexpdate -d 0 -m media_ID
To avoid this problem in the future, use unique prefix characters for media
Running vmphyinv
To import Backup Exec media requires vmphyinv to update the Backup Exec
media GUID in the NetBackup Media Manager database. Create the media IDs in
the NetBackup Media Manager database, run the command, then perform Phase
I and Phase II import operations.
For information about using vmphyinv, See “Using the physical inventory
utility” on page 572.
When a user selects a NetBackup file to restore, only the single file is restored.
NTFS hard links, NTFS SIS files, and Exchange SIS mail messages:
restoring
■ When Backup Exec NTFS images are restored, any directory named SIS
Common Store is restored. The directory named SIS Common Store is
restored whether or not it is the actual NTFS single instance storage
common store directory. The directory is restored even if the file was not
specifically selected for restore.
■ Under some circumstances, additional objects are sent to the client, even
though the objects were not selected for restore. The items are sent to the
client when restoring objects from any backups that contain NTFS
hardlinks, NTFS SIS files, or Exchange SIS mail messages. These additional
objects are skipped by the client and are not restored. The job is considered
partially successful because some objects (though not selected by the user),
are skipped.
■ When NTFS hard links, NTFS SIS files, or Exchange SIS mailboxes are
redirected for restore:
■ All or some of the files should be redirected to any location on the
source drive,
Or:
■ All files should be redirected to a single location on a different drive.
For example, if the following hard link or SIS files are backed up:
C:\hard_links\one.txt
C:\hard_links\two.txt
C:\hard_links\three.txt
Upon restore, either the files can be redirected to any location on C:\,
If all the files are to be redirected to a different drive, specify that C:\
Note: For the policies that collect true image restore information, an
incremental backup collects catalog information on all files (as if it were a full
backup). This changes the calculation in the example: the incremental changes
from 1200 x 7 = 8400 to 3000 x 7 = 21,000. After 12,000 is added for the full
backups, the total for the two schedules is 33,000 rather than 20,400.
that each policy can generate by using the information in Table 6-3. Substitute
the information into the following formula:
Files per Backup x Backups per Retention Period = Max Files
The following steps demonstrate the equation for policy S1:
1 Apply the following formula to policy S1:
Note: You can also run the bpbackup command from the command line to
perform an online, hot catalog backup. See NetBackup Commands for UNIX and
Linux for more information on bpbackup.
3 Select the master server for which you want to create a catalog backup and
click OK.
Note: If the volume for the catalog backup is not in a drive, a mount request
occurs. All catalog backups must wait for the mount before they can proceed.
For a scheduled catalog backup, all other backups must wait until the catalog
backup is complete.
Note: You can also run the bpbackupdb command from the command line to
perform an offline, cold catalog backup. See NetBackup Commands for UNIX and
Linux for more information on bpbackup.
email or save it on a disk other than the disk that contains the catalogs. For
more information, see “Global Attributes properties” on page 435.
■ If you send catalog backups to a robot, a tape stacker, a second stand-alone
tape drive, or to disk, choose either of the two automatic backups:
After each session of scheduled, user, or manual backups or
After each session of scheduled backups
■ If you use a single, stand-alone tape drive to back up both catalog and
regular business data, choose either:
■ After each session of scheduled backups if you run only one backup
session per day or night, or
■ Only when manually initiated if you run multiple backup sessions in a
single day or night.
Because NetBackup does not place catalog and regular backups on the same
tape, both methods require you to swap tapes.
Use the following general procedure for creating catalog backups if you
have only one stand-alone drive:
a Insert the tape that is configured for catalog backups.
b Manually start the backup. For more information, see “Backing up
catalogs manually” on page 350.
c When the backup is complete, remove the tape and store it in a safe
place.
Caution: The catalog backup tape must be removed when the backup is finished
or regular backups cannot proceed. NetBackup does not mix catalog and regular
backups on the same tape.
Note: NetBackup does not support saving the catalog to a remote file system.
Therefore, Symantec advises against moving the image catalog to a remote file
system such as NFS or CIFS.
Caution: Be certain to add the path for the image catalog and not the link name.
Without the path, NetBackup cannot back up the new location. In this example,
the path is /disk3/netbackup/db/images.
Run this command to create the following index files in each client image
directory:
IMAGE_FILES
IMAGE_INFO
IMAGE_LIST
If you choose to compress the image catalog, NetBackup uses the compress
command on the server to perform compression after each backup session. It
does not make a difference to NetBackup if the backup session was successful.
The operation occurs while NetBackup expires backups and before it runs the
session_notify script and the backup of the NetBackup catalogs.
NetBackup Catalog 357
Catalog maintenance and performance optimization
The time to perform compression depends on the server speed and the number
and size of the files being compressed. Files are compressed serially, and
temporary working space is required in the same partition.
When numerous compressed image-catalog files must be processed, the backup
session is extended until compression is complete. The additional backup time is
especially noticeable the first time you perform the compression. To minimize
the impact of the initial sessions, consider compressing the files in stages. For
example, begin by compressing the records for the backups older than 120 days.
Continue to reduce the number of days over a period of time until you reach a
comfortable setting.
Compressing the image catalog can accomplish two objectives:
■ To reduce greatly the disk space that is consumed.
■ To reduce the amount of media that is required to back up the catalog.
The amount of space that is reclaimed varies with the types of backups you
perform. Full backups result in a larger percentage of catalog compression than
incremental backups. Normally, more data is duplicated in a catalog file for a
full backup. Using catalog compression, a reduction of 80% is possible.
This reduction in disk space and media requirements is achieved at the expense
of performance when a user lists or restores files. Since the information is
uncompressed at each reference, performance degradation is in direct
proportion to the number and size of compressed files that are referenced. If the
restore requires numerous catalog files to be uncompressed, you may need to
increase the time-out value that is associated with list requests. Change the
time-out value by changing the LIST_FILES_TIMEOUT option in the bp.conf
file of the client.
4 Expand Host Properties > Master Servers. Open the properties of a host. On
the Global Attributes properties, clear the Compress Catalog Interval check
box. For more information, see “Global Attributes properties” on page 435.
5 Set the Compress Catalog Interval Global Attributes property to 0.
6 Change your working directory to /usr/openv/netbackup/bin and run
the command:
admincmd/bpimage -decompress -client name
■ “Master server, media server, and client host properties” on page 364
Menu bar
Standard toolbar
Current master
server
User toolbar
Right-click in the Details
pane to view the shortcut
menu
Details pane
The options on the Host Properties menu bar are described in the online help.
3 In the Details pane, click the server or client to view the version and
platform. Then, double-click to view the properties.
To see the properties of a different master server, click File > Change
Server.
To make sure that NetBackup uses a changed setting, restart the all
daemons and utilities (including the NetBackup Administration Console) to
ensure that the new configuration values are used.
■ Click Help for information on the properties that appear on the current
dialog box.
Required permissions
Required permissions
To change the properties on other hosts, the NetBackup server where you logged
on using the NetBackup Administration Console must be in the Servers list on
the other system.
For example, if you logged on to server_1 using the NetBackup Administration
Console and want to change a setting on client_2, client_2 must include server_1
in its Servers List.
For more information, see “To add a NetBackup server to a server list” on
page 639.
Note: All updates to a destination host (unless it is the same as the host you
logged on to using the NetBackup Administration Console) will fail if the target
host has placed a check box in Allow server file writes on the Universal Settings
properties. For more information, see “Universal Settings properties” on
page 477.
Networks list
The Networks list indicates whether specific networks can or cannot use
The names on the list are relevant only if Symantec Product Authentication and
Add button
To add a network to the Network list, click Add. The Add Network dialog box
displays.
Host properties 367
Master server, media server, and client host properties
Host/Domain
Indicate whether the network to be added is a Host name or a Domain name.
Host Name/IP
If the network is a host, enter the one of the following:
■ The host name of the remote system. (host.domain.com)
■ The IP address of the remote system. (10.0.0.29)
Domain Name/IP
If the network is a domain name, enter one of the following:
■ A dot followed by the Internet domain name of the remote systems.
(.domain)
■ The network of the remote system, followed by a dot. (10.0.0.)
Bit count
Select Bit count to indicate that the mask is based on bit count. Select from
between 1 and 32.
368 Host properties
Master server, media server, and client host properties
For example: Mask 192.168.10.10/16 has the same meaning as subnet mask
192.168.20.20:255:255:0.0
Subnet mask
Select Subnet mask to enter a subnet mask in the same the format as the IP
address.
Remove button
To delete a network, select the network name, then click Remove.
If a media server or client does not define an authentication domain, it uses the
authentication domains of its master server.
Add button
To add an authentication domain to the domain list, click Add. The Add
Authentication Domain dialog box displays. The dialog box contains the
following properties:
370 Host properties
Master server, media server, and client host properties
Domain
An Internet or Windows domain name.
Authentication mechanism
Indicate the authentication mechanism:
Note: If the authentication domain is UNIX , enter the fully qualified domain
name of the host that performs the authentication.
Broker
The operating system of the broker machine supports the domain type of the
authentication service.
Description
Include a description of the domain (optional).
Remove button
To delete an authorization domain, select the name, then click Remove.
Note: Define a host to perform authorization if configuring this tab for a media
server using Access Control.
Host name
Enter the host name or IP address of the authorization service.
372 Host properties
Master server, media server, and client host properties
Authorization properties
The Authorization properties apply to currently selected master servers and
media servers.
Click Add to add an authorized user, or click Change to change the configuration
of an existing authorized user. The New User or Change User dialog box
appears.
User
In the User text box, type the name that identifies this user to NetBackup. To
indicate any user, enter a single asterisk: *
374 Host properties
Master server, media server, and client host properties
Host
In the Host text box, type the name of the remote NetBackup Administration
Console host from which this user can use NetBackup. To indicate all hosts,
enter a single asterisk: *
Domain\Group
In the Domain\Group text box, type the Windows domain and group name in the
form domain\group. Or, type the UNIX local group name or the UNIX netgroup
name. Or, enter * to indicate for all groups.
Group/Domain type
Select whether this user is authorized to use NetBackup in a Local group or a
Network group.
Figure 7-10 Backup Exec Tape Reader host properties dialog box
The Backup Exec Tape Reader option enables NetBackup to read the media that
For more informations, see “Importing images from Backup Exec media” on
page 342.
Add button
Click Add to enter a GRFS mapping. The Add a GRFS Mapping dialog box
appears, that contains the fields that are described in the following sections.
Actual path
The Actual path maps the advertised path to the real path.
Change button
Click Change to change the selected GRFS entry.
Remove button
Click Remove to remove the selected GRFS entry.
Host properties 377
Master server, media server, and client host properties
Bandwidth properties
The Bandwidth properties apply to currently selected master servers.
Bandwidth properties specify limits for the network bandwidth that one or more
NetBackup clients of the selected server use. The actual limiting occurs on the
client side of the backup connection. By default, the bandwidth is not limited.
The bandwidth limits only restrict bandwidth during backups.
are started, the NetBackup server instructs the other NetBackup clients that run
on that subnet to decrease their bandwidth setting. Similarly, bandwidth per
client is increased if the number of clients decreases. Changes to the bandwidth
value occur on a periodic basis rather than as backups stop and start. The
periodic changes reduce the number of bandwidth value changes that are
required.
From IP address
The From IP address field specifies the beginning of the IP address range of the
clients and networks to which the entry applies. An example is 10.1.1.2
To IP address
The To IP address field specifies the end of the IP address range of the clients
and networks to which the entry applies. An example is 10.1.1.9
Bandwidth
The Bandwidth field specifies the bandwidth limitation in kilobytes per second.
A value of 0 disables the limits for an individual client or the range of IP
addresses covered by the entry.
For example, a value of 200 indicates 200 kilobytes per second.
Add button
Click the Add button to prepare an entry using the From, To, and Bandwidth
fields and add it to the bandwidth table. An entry is added for each of the
selected clients.
Host properties 379
Master server, media server, and client host properties
Remove button
Click the Remove button to remove a selected entry from the bandwidth table.
Set the file access permissions to allow group and other to execute
bpend_notify.
■ Configure a policy with a user backup schedule for the busy file backups.
This policy services the backup requests that the repeat option in the
actions file generates. The policy name is significant: by default,
NetBackup alphabetically searches (uppercase characters first) for the first
available policy with a user backup schedule and an open backup window.
Host properties 381
Master server, media server, and client host properties
Working directory
The Working directory property specifies the path to the busy-files working
directory.
On a UNIX client, the value in the user’s $HOME/bp.conf file takes precedence
/usr/openv/netbackup directory.
Add button
Click Add to add a new file entry. Enter the file and path directly, or browse to
select a file.
Remove button
Select the file or directory and click Remove to remove the file from the file
action list.
Retry count
The Retry count property specifies the number of times to try the backup.
Default retry count: 1.
Host properties 383
Master server, media server, and client host properties
Clean-up properties
Clean-up properties apply to the length of time to retain various logs and
incomplete jobs.
Keep logs
The Keep logs property specifies the length of time, in days, that the master
server keeps its error catalog, job catalog, and debug log information. NetBackup
derives the Backup Status, Problems, All Log Entries, and Media Log reports
from the error catalog. Keep logs limits the time period that these reports can
cover. When this time expires, NetBackup also deletes these logs (that exist) on
UNIX media servers and UNIX clients.
Specify how many days you’d like to keep the logs in case you need the logs to
evaluate failures. For example, if you check the backups every day you can
delete the logs sooner than if you check the backups once a month. However, the
logs can consume a large amount of disk space, so do not keep the logs any
longer than necessary. Default: 28 days.
install_path\netbackup\vault\sessions\vaultname\sidxxxx
where xxxx is the session number. This directory contains vault log files,
temporary working files, and report files.
Image cleanup
The Image cleanup property specifies the maximum interval that can elapse
before an image cleanup is run. Image cleanup is run after every successful
backup session (that is, a session in which at least one backup runs successfully).
If a backup session exceeds this maximum interval, an image cleanup is
initiated.
Note: A resumed job reuses the same job ID, but a restarted job receives a new
job ID. The job details indicate that the job was resumed or restarted.
386 Host properties
Master server, media server, and client host properties
Figure 7-15 General tab of Client Attributes host properties dialog box
Clients list
The Clients list is a list of clients in the client database on the currently selected
master server(s). A client must be in the client database before you are able to
change the client properties in the Client Attributes dialog box. The client
database consists of directories and files in the following directory:
/usr/openv/NetBackup/db/client
If a client is not listed in the Clients list, click Add to add clients. To remove a
client from the Clients list, select the client, then click Remove.
You can also create, update, list, and delete client entries by using the bpclient
/usr/openv/netbackup/bin/admincmd
The name that is entered here must match the Client Name property for the
specific client. If it does not, the client cannot browse its own backups.
For more information, see “Client name” on page 395.
Note: Use the bpclient command to add clients to the client database if
dynamic addressing (DHCP) is in use. (See “Dynamic host name and IP
addressing” on page 99 in the NetBackup Administrator’s Guide, Volume II for
instructions.)
Add button
Click Add to display the Add Client dialog box and add a client to the client
database. Type a client name in the text box.
Remove button
Select a client in the Clients list and click Remove to delete the selected client
from the client database.
General tab
The following sections describe the properties on the General tab within Client
Attributes. For more information about the Windows Open File Backup
properties, see “Windows Open File Backup tab” on page 391.
To change the setting, select Maximum data streams. Then scroll to or enter a
value up to 99. Maximum data streams interacts with the Maximum jobs per
client and Limit jobs per policy as follows:
For more information see “Maximum jobs per client” on page 436 and “Limit
jobs per policy” on page 97.
■ If Maximum data streams is not set, the limit is either Maximum jobs per
client or Limit jobs per policy, whichever is lower.
■ If Maximum data streams is set, NetBackup ignores Maximum jobs per
client. NetBackup uses either Maximum data streams or Limit jobs per
policy, whichever is lower.
Free browse
The Free Browse property applies to the privileges that are allowed to a non-root
The Free browse property specifies whether the clients can list and restore from
scheduled backups. (This setting does not affect user backups and archives.)
Root users are able to list and restore from scheduled backups as well as user
Figure 7-16 Connect Options tab of Client Attributes host properties dialog box
Ports
■ Use default connect options: Use the value that is defined in the Firewall
host properties of the client’s NetBackup server. For more information, see
“Default connect options” on page 424.
■ Reserved port: Use a reserved port number.
■ Non-reserved port: Use a non-reserved port number.
390 Host properties
Master server, media server, and client host properties
Note: If vnetd only is selected as the Daemon connection port, the BPCD connect
back setting is not applicable. If vnetd only is selected as the Daemon connection
port, Non-reserved port is always used regardless of the value of the Ports
setting.
Host properties 391
Master server, media server, and client host properties
Figure 7-17 Windows Open File Backup tab of Client Attributes host properties
dialog box
The Windows Open File Backup properties specify whether a client uses
Windows Open File Backup. The properties also specify whether Volume
Snapshot Provider or Volume Shadow Copy Service is used as the snapshot
provider.
Snapshots are a point-in-time view of a source volume. NetBackup uses
snapshots to access busy or active files during a backup job. Without a snapshot
provider, active files are not accessible for backup.
To delete a client from the list, select the client, then click Delete.
To make changes to the default settings, add the client name to the client list.
Select the client name in the client list, then make changes to the client’s
selected clients. VSS can be used for Windows Server 2003 clients only.
Configure VSS through the Microsoft’s VSS configuration dialog boxes.
drive. All the volumes that require snapshots for the backup job (or stream
For example, assume that drives C and D are to be backed up. In this situation,
This property maintains file consistency between files in different volumes. The
backup uses the same snapshot that is taken at a point in time for all volumes in
the backup.
Note: The Individual drive snapshot and Global drive snapshot properties only
apply to non multi-streamed backups using Windows Open File Backup. All
multi-streamed backup jobs share the same volumes snapshots for the volumes
in the multi-streamed policy. The volume snapshots are taken in a global
fashion.
Note: Volume snapshots typically become invalid during the course of a backup
because insufficient cache storage was allocated for the volume snapshot.
Reconfigure the cache storage configuration of the Windows Open File Backup
snapshot provider to a configuration that best suits your client’s installation.
Host properties 395
Master server, media server, and client host properties
Client name
The host that is specified in the Client name field is the NetBackup client name
for the selected client. The Client name is the name by which the client is known
to NetBackup. The name must match the name the policy uses to back up the
client. The only exception is for a redirected restore, where the name must
match that of the client whose files are to be restored. The client name is
initially set during installation.
The name that is entered here must also match the client name in the Client
Attributes dialog box for the master server. If it does not, the client cannot
browse for its own backups. For more information, see “Client Attributes
properties” on page 386.
If the value is not specified, NetBackup uses the name that is set in the following
locations:
■ For a Windows client: In the Network application from the Control Panel.
■ For a UNIX client: The name that is set by using the hostname command.
The name can also be added to a $HOME/bp.conf file on a UNIX client.
However, the name is normally added in this manner only for redirected
restores. The value in the $HOME/bp.conf file takes precedence if it exists.
396 Host properties
Master server, media server, and client host properties
Logs for user-directed operations are stored on the client system in the
following directory:
install_path\NetBackup\logs\user_ops\ loginID\logs
Note: This setting affects the software and the administration scripts that
examine a file’s access time. DO NOT use this option or
USE_CTIME_FOR_INCREMENTALS if you are running Storage Migrator on the
system. Setting these options causes the atime for files to be updated every time
they are backed up. An updated atime makes it appear as if the files are
frequently used and prevents Storage Migrator from selecting the files for
migration.
Note: This option has a reasonable default and should be changed only if
problems are encountered.
The Megabytes of memory to use for file compression property specifies the
amount of memory available on the client when files are compressed during
backup. If you select compression, the client software uses this value to
determine how much space to request for the compression tables. The more
memory that is available to compress code, the greater the compression and the
greater the percentage of machine resources that are used. If other processes
also need memory, use a maximum value of 1/2 the actual physical memory on a
machine to avoid excessive swapping. Default: 0.
Default: off.
The File Change Log (FCL) tracks changes to files and directories in a file system.
Changes may include files created, links and unlinks, files renamed, data that is
appended, data that is overwritten, data that is truncated, extended attribute
modifications, holes punched, and file property updates.
NetBackup can use the FCL to determine which files to select for incremental
backups, which can potentially save unnecessary file system processing time.
The FCL information that is stored on each client includes the backup type, the
FCL offset, and the time stamp for each backup.
The following platforms and versions are supported:
Recommended use
The advantages of this property depend largely on the number of file system
changes relative to the file system size. The performance impact of incremental
backups ranges from many times faster or slower, depending on file system size
and use patterns.
For example, enable this property for a client on a very large file system that
experiences relatively few changes. The incremental backups for the client may
complete sooner since the policy needs to read only the FCL to determine what
needs to be backed up on the client.
If a file experiences many changes, or multiple changes to many files, the time
saving benefit may not be as great.
Note: The VxFS mount point must be specified in the policy backup selections
list for this property to take effect. For more information, see “Backup
Selections tab” on page 163
■ The VxFS mount point must be specified in the policy backup selections list
in some manner:
■ By specifying ALL_LOCAL_DRIVES.
■ By specifying the actual VxFS mount point.
■ By specifying a directory at a higher level than the VxFS mount point,
provided that Cross mount points is enabled. For more information, see
“Cross mount points” on page 103.
Note: If the policy has Collect true image restore information or Collect true
image restore information with move detection enabled, the Use VxFS file
change log property on the client is ignored.
The Activity Monitor also notes when full and incremental backups are not
synchronized.
Note: If any errors are encountered while processing the FCL, NetBackup
switches to the normal files system scan. If this switch occurs, it is displayed in
the Activity Monitor.
VxFS administration
Additional VxFS commands are available to administrate the FCL. The
commands are documented in the Veritas File System Administrator’s Guide.
During a backup, NetBackup does not compress files with these extensions
Do not use wildcards to specify these extensions. For example, .A1 is allowed,
Files that are already compressed become slightly larger if compressed again. If
compressed files with a unique file extension already exist on a UNIX client,
Add button
Use the Add button to add file endings to the list of file endings that you do not
want to compress. Click Add, then type the file extension in the File Endings
dialog box. Use commas or spaces to separate file endings if more than one is
added. Click Add to add the ending to the list, then click Close the dialog box.
Remove button
Click the Remove button to remove a file extension from the list. To remove a
name, either type it in the box or click the browse button (...) and select a file
ending. Use commas or spaces to separate names. Then, click the – button.
402 Host properties
Master server, media server, and client host properties
2 Log all TCP/IP functions, including all read and write requests.
Note: Setting the TCP level to 2 or 3 can cause the status reports to be very large.
It can also slow a backup or restore operation.
Host properties 403
Master server, media server, and client host properties
relatively few files and folders. (For example, hundreds of thousands of files
and folders.) The normal file system scan is suitable under such conditions.
■ If the total number of changes on a volume exceeds from 10 to 20% of the
total objects, the volume is not a good candidate for enabling NetBackup
change journal support.
■ Be aware that virus scanning software can interfere with the use of the
change journal. Some real-time virus scanners intercept a file open for read,
scan for viruses, then reset the access time. This results in the creation of a
change journal entry for every scanned file.
Administrator’s Guide.
include files in an incremental backup only if the archive bit of the file is set. The
system sets this bit whenever a file is changed and it normally remains set until
clears the archive bit if the file is successfully backed up. The
For more information, see “Wait time before clearing archive bit” on page 403.
datetime stamp for the file has been changed since the last backup. For a
If you install or copy files from another computer, the new files retain the date
timestamp of the originals. If the original date is before the last backup date on
this computer, then the new files are not backed up until the next full backup.
Time overlap
The Time overlap property specifies the number of minutes to add to the date
range for incremental backups when using date-based backups. This value
compensates for differences in the speed of the clock between the NetBackup
client and server. Default: 60 minutes.
406 Host properties
Master server, media server, and client host properties
This value is used during incremental backups when using the archive bit and
when examining the create time on folders. This comparison is done for archive
bit-based backups as well as date-based backups.
Rank
The order of the data classifications determines the rank of the classification in
relationship to the others in the list. The lowest numbered rank has the highest
priority.
Use the Move Up and Move Down buttons to change rank and move the
classification up or down in the list.
To create a new data classification, click New. The New dialog displays. New
data classifications are added to bottom of the list. To increase the rank of a data
classification, select a line and click Move Up. To decrease the rank of a data
classification, select a line and click Move Down.
408 Host properties
Master server, media server, and client host properties
Name
NetBackup provides four data classifications by default:
■ Platinum (highest rank by default)
■ Gold (second highest rank by default)
■ Silver (third highest rank by default)
■ Bronze (lowest rank by default)
Data classification names can be modified.
Description
Enter a meaningful description for the data classification. Descriptions can be
modified.
Classification ID
The Classification ID is the GUID value that identifies the data classification and
is generated when a new data classification is added and the host property is
saved.
A data classification becomes associated with a backup image by setting the
Data Classification attribute in the policy dialog. The ID is written into the
image header. The storage lifecycles use the ID to identify the images that are
associated with classification. For more information, see “Data classification”
on page 90.
ID values may exist in image headers indefinitely, so data classifications cannot
be deleted. The name, description, and rank can change without changing the
identity of the data classification.
Encryption properties
The Encryption properties control encryption on the currently selected client.
Multiple clients can be selected and configured at one time only if all selected
clients are running the same version of NetBackup. If not, the Encryption
properties dialog box is hidden.
The separately-priced NetBackup Encryption option must be installed on the
client for these settings (other than Allowed) to take effect. For more specific
information on the Encryption option, see the NetBackup Security and
Encryption Guide.
Encryption permissions
The Encryption permissions property indicates the encryption setting on the
selected NetBackup client as determined by the master server. If it is necessary
to change this property, select one of the following options:
■ Not allowed: Specifies that the client does not permit encrypted backups. If
the server requests an encrypted backup, the backup job ends due to error.
410 Host properties
Master server, media server, and client host properties
Enable encryption
Select the Enable encryption property if the NetBackup Encryption option is
used on the selected client.
If the selected client runs NetBackup 5.1 and does not use Legacy encryption,
Client cipher
The following cipher types are available: BF-CFB, DES-EDE-CFB, AES-256-CFB,
More information on the ciphers file is found in the NetBackup Security and
Encryption Guide.
If the selected client is running a version of NetBackup earlier than 5.1, Use
Encryption strength
The Encryption strength property defines the encryption strength on the
NetBackup client when Legacy encryption is used:
■ DES_40: Specifies the 40-bit DES encryption. DES_40 is the default value for
a client that has not been configured for encryption.
■ DES_56: Specifies the 56-bit DES encryption.
Host properties 411
Master server, media server, and client host properties
Encryption libraries
The Encryption libraries property specifies the folder that contains the
encryption libraries on NetBackup clients. The default setting is generally
sufficient.
The following is the default location:
■ On Windows systems: install_path\netbackup\bin\
Where install_path is the directory where NetBackup is installed and by
default is C:\Program Files\VERITAS.
■ On UNIX systems: /usr/openv/lib
Exchange properties
The Exchange properties apply to currently selected Windows clients.
The Exchange properties specify the mailbox to associate with the NetBackup
Client Service account. Specify a mailbox only if the NetBackup client and
NetBackup Microsoft Exchange Server agent software are installed on the
Microsoft Exchange Server.
The NetBackup Client Service account must be associated with a valid Exchange
mailbox for NetBackup to access the mailboxes and folders during backups and
restores. Create a unique mailbox name for the NetBackup Client service
account. If a mailbox is not created for the NetBackup Client service, use any
existing mailbox on the Microsoft Exchange Server. The NetBackup Client
service account must have granted logon rights to the mailbox.
For more information on the mailbox settings, see the NetBackup for Microsoft
Exchange Server Administrator’s Guide.
ESEUTIL /pXXX where XXX is the value of Snapshot verification I/O throttle.
ESEUTIL defines the /p setting as a forced second-long pause after every XXX
I/Os to limit the I/O rate during database verification. See the Microsoft
Exclude list
The Exclude list displays the policies that contain schedule, file, and directory
exclusions.
When the policies on the Exceptions to the exclude list run, the files and
directories on the list are backed up. The list is useful to exclude all files in a
Add buttons
The Add button performs different functions, depending on whether it is used
from the Exclude list or from the Exceptions to the exclude list.
When the policies on the Exclude list run, the files and directories that are
specified on the list are backed up.
Remove buttons
Remove performs different functions, depending on whether it is used from the
Exclude list or from the Exceptions to the exclude list.
Policy
In the Policy field, enter the policy name that contains the files and the
directories to exclude or make exceptions for. You can also select the policy
name from the drop-down menu. To exclude or make exceptions for the backup
of specific files or directories from all policies, select <All Policies>.
Schedule
In the Schedule field, enter the schedule name that is associated with the files
and the directories to exclude or make exceptions for. You can also select the
schedule name from the drop-down menu. To exclude or make exceptions for
the backups of specific files or directories from all schedules, select <All
Schedules>.
Files/Directories
In the Files/Directories field, enter the full path to the file(s) and the directories
to exclude or make exceptions for.
a Under the Exclude List, click Add. The Add to Exclude List dialog box
appears.
b In the Policy field, select a policy name from the drop-down menu or
enter the name of a policy. Select All Policies to exclude these items
from all policies.
c In the Schedule field, select a schedule name from the drop-down menu
or enter the name of a schedule. Select All Schedules to exclude the
specified files and directories from all schedules in the policy.
d In the Files/Directories field, enter the files or directories to be
excluded from the backups that are based on the selected policy and
schedule.
e Click Add to add the specified files and directories to the exclude list.
3 To add an exception to the exclude list:
a Under the Exceptions to the Exclude List, click Add. The Add Exceptions
to the Exclude List dialog box appears.
b In the Policy field, select a policy name from the drop-down menu or
enter the name of a policy. Select All Policies to add these items back
into all policies. (In other words, these items are to be excluded from the
exclude list.)
c In the Schedule field, select a schedule name from the drop-down menu
or enter the name of a schedule. Select All Schedules to add these items
back into the schedules.
d In the Files/Directories field, enter the files or directories to be added
back into the backups that are based on the selected policy and
schedule.
e Click Add to add the specified files and directories to the Exceptions to
the Exclude List.
4 Click Apply to accept the changes. Click OK to accept the changes and close
the host properties dialog box.
In this example, NetBackup uses the first exclude list (for policy and schedule)
because it is the most specific.
Note: Symantec suggests that you always specify automounted directories and
CD-ROM file systems in the exclude list. Otherwise, if the directories are not
mounted at the time of a backup, NetBackup must wait for a timeout before
proceeding.
rather than
C:\test
\*\
\*\*\
\*\*\*\
and so on.
The following syntax rules apply only to UNIX clients:
Host properties 419
Master server, media server, and client host properties
■ Do not use patterns with links in the names. For example, assume /home is a
link to /usr/home and /home/doc is in the exclude list. The file is still
backed up in this case because the actual directory path, /usr/home/doc,
does not match the exclude list entry, /home/doc.
■ Blank lines or lines that begin with a pound sign (#) are ignored.
C:\users\doe\abc\
C:\users\*\test
C:\*\temp
core
Given the exclude list example, the following files and directories are excluded
from automatic backups:
■ The file or directory named C:\users\doe\john.
■ The directory C:\users\doe\abc\ (because the exclude entry ends with
\).
■ All files or directories named test that are two levels beneath users on
drive C.
■ All files or directories named temp that are two levels beneath the root
directory on drive C.
■ All files or directories named core at any level and on any drive.
consisted of only:
/
An exclude list of * indicates that all files are excluded from the backup.
■ However, since the include list on Windows client silk includes the following
file:
C:\WINNT
In another example, assume the following settings for a UNIX client named
hagar:
■ The backup selection list for client hagar consists of the following: /
■ The exclude list for UNIX client hagar consists of the following: /
■ The include list of UNIX client hagar consists of the following directories:
/data1
/data2
/data3
Because the include list specifies full paths and the exclude list excludes
everything, NetBackup replaces the backup selection list with the client’s
include list.
422 Host properties
Master server, media server, and client host properties
The Fibre Transport media server property applies to the SAN clients for
The Fibre Transport client properties apply to the selected SAN clients. The
defaults for clients are the property settings of the master server.
pipe is the logical connection that carries backup and restore data between an
For more information about NetBackup Fibre Transport, see the NetBackup
Preferred
The Preferred property specifies to use an FT pipe if an FT device is available
within the configured wait period in minutes. If an FT device is not available
after the wait period elapses, NetBackup uses a LAN connection for the
operation.
If you select this option, also specify the wait period for backups and for
restores.
Host properties 423
Master server, media server, and client host properties
For the global property that is specified on the master server, the default is
Preferred.
Always
The Always property specifies that NetBackup should always use an FT pipe
always for backups and restores of SAN clients. NetBackup waits until an FT
device is available before it begins the operation.
However, an FT device must be active and available. If no FT device exists,
NetBackup uses the LAN. An FT device may not exist because none is active,
none have been configured, or the SAN Client license expired.
Never
The Never property specifies that NetBackup should never use an FT pipe for
backups and restores of SAN clients. NetBackup uses a LAN connection for the
If you specify Never for the master server, Fibre Transport is disabled in the
per-client basis.
If you specify Never for a media server, Fibre Transport is disabled for the media
server.
If you specify Never for a SAN client, Fibre Transport is disabled for the client.
The default is four times the number of HBA target ports (maximum of 16).
Firewall properties
The Firewall properties describe how the selected master and media servers are
Servers are added to the host list of the Firewall properties. To configure port
usage for clients, see the Client Attributes properties. (See “Client Attributes
ports to be open.
bp.conf file.
To change any of the Default connect options, click Change. The Default
Connect Options dialog box appears that contains the following properties:
Ports
Select whether the server is connected to by a reserved or non-reserved port
number:
■ Use reserved ports: Connect to the server by a reserved port number.
■ Use non reserved ports: Connect to the server by a non-reserved port
number. If this property is selected, also enable Accept connections from
non reserved ports for the selected server.
This property is located on the Universal Settings dialog box under Host
Properties > Master Servers or Host Properties > Media Servers. For more
information, see “Accept connections on non reserved ports” on page 480.
426 Host properties
Master server, media server, and client host properties
Note: If vnetd only is selected as the Daemon connection port, the BPCD connect
back setting is not applicable. If vnetd only is selected as the Daemon connection
port, Use non reserved ports is always used regardless of the value of the Ports
setting.
Hosts list
To change the default connect options for any server, add the server to the host
list. Servers do not automatically appear on the list.
Add button
Click Add... to add a host entry to the host list. A host must be listed before it can
be selected for configuration.
Remove button
Select a host name in the list, then click Remove to remove the host from the
list.
Host properties 427
Master server, media server, and client host properties
file.
Ports
Select whether a reserved or non-reserved port number should be used to
connect to the server:
■ Use default connect options: Use the method that are specified under
Default attributes. (Use default is the default.)
■ Reserved port: Connect to the server by a reserved port number.
■ Non reserved port: Connect to the server by a non-reserved port number. If
this property is selected, also enable Accept connections from non reserved
ports for the selected server.
This property is located on the Universal Settings dialog box under Host
Properties > Master Servers or Host Properties > Media Servers. For more
information, see “Accept connections on non reserved ports” on page 480.
Note: If vnetd only is selected as the Daemon connection port, the BPCD connect
back setting is not applicable. If vnetd only is selected as the Daemon connection
port, Non reserved port is always used regardless of the value of the Ports
setting.
Note: Both servers and clients must have NetBackup version 4.5 or later
installed for vnetd to work.
1 = vnetd-only connections.
■ In the Client Attributes properties for the Master server, add an entry
for each remote client. (Host Properties > Master Servers > Selected
master server > Client Attributes.)
Under BPCD connect back, select VNETD port.
Host properties 431
Master server, media server, and client host properties
Note: This property applies to the disk storage units of 6.0 media servers only.
Subsequent releases use internal methods to monitor disk space more
frequently.
432 Host properties
Master server, media server, and client host properties
■ Two (or more) servers share a robot and each have connected drives. A
restore is requested while one of the servers is either temporarily
unavailable or is busy doing backups.
■ A media server was removed from the NetBackup configuration, and is no
longer available.
Add button
Click Add to add a host to the Media host override list. The Add Media Override
Settings dialog box contains the following fields:
Change button
To change an entry in the Media host override list, select a host name, then click
Change.
434 Host properties
Remove button
Select the host in the Media host override list and click Remove to remove the
host from the list.
Note: This attribute does not apply to user backups and archives.
The Schedule backup attempts property specifies the number of times that
NetBackup tries to complete a scheduled backup job during the specified time
period. Schedule backup attempts allows you to limit the number of tries if a
client or drive is down or media is unavailable.
If the backup window closes before the retry starts, the job fails with a status
code 196. Default: 2 tries in 12 hours.
436 Host properties
Master server, media server, and client host properties
Note: Multiplexed backup jobs are unaffected by the restore priority setting.
Client
Tape
/usr Policy B
Drive 2
Server
You can specify any number of concurrent jobs within the following constraints:
■ Number of storage devices. NetBackup can perform concurrent backups to
separate storage units or to drives within a storage unit. For example, a
single Media Manager storage unit supports as many concurrent backups as
Host properties 437
Master server, media server, and client host properties
Note: If online, hot catalog backups are scheduled to occur concurrently with
other backups for the master server, set the Maximum jobs per client value to
greater than two. The higher setting ensures that the catalog backup can
proceed while the regular backup activity occurs.
that are allowed to be active on the master server. The greater the maximum
If the active vault jobs limit is reached, subsequent vault jobs are queued and
If a duplication job or eject job waits, its status is shown as Active in the Activity
Monitor.
Note: Disaster recovery information that is created during online, hot catalog
backups is not sent to the addresses indicated here. DR information is sent to
the address indicated on the Disaster Recovery tab in the catalog backup policy.
.For more information, see “Disaster Recovery tab” on page 193.
NetBackup uses the mail transfer agent sendmail to send email notifications. If
it is not installed, install it from sendmail.org and configure your
environment accordingly so that it functions correctly.
NetBackup can send notification to specified email addresses about backups on
all client or specific clients. Choose one or both of the following notification
methods:
■ Send emails about failed backups only:
Send a message to the email address(es) of the NetBackup administrator(s)
about any backup that ends in a non-zero status. (Server sends mail host
property is enabled in Universal Settings.)
■ Send emails about successful and failed backups:
Send a message to the local administrator(s) of each client about successful
and unsuccessful backups. (Client sends mail host property is enabled in
Universal Settings.)
Both methods require that the host properties be configured with email
addresses. (See “Indicating email notification in the NetBackup host properties”
on page 439.)
-ma name@company.com
Email contents
The following represents the contents of a notification email:
Backup on client hostname by root was partially successful.
File list
---------
C:\Documents and Settings
Logging properties
The Logging properties apply to currently selected master servers, media
servers, and clients. The available properties differ between master servers,
media servers, and clients.
Types of logging
The Logging properties contain the processes that continue to use legacy
logging as well as processes that use unified logging.
install_path\NetBackup\logs (Windows).
No subdirectories are necessary for the processes that use unified logging. The
logging method for unified logging differs from the logging method for the
For details on both unified and legacy logging, refer to the “Using Logs and
To control the size and number of unified logs, use the vxlogcfg and the
Legacy logging
For those processes that use legacy logging, you must first create a log directory
for each process to be logged. A logging level selection on the Logging properties
page does not enable logging.
Create the NetBackup legacy log directories in:
■ /usr/openv/netbackup/logs/process_name (UNIX)
■ install_path\NetBackup\logs\process_name (Windows)
Create the Media Manager legacy log directories in:
■ /usr/openv/volmgr/debug (UNIX)
■ install_path\Volmgr\debug (Windows)
For more information about legacy logs, see the NetBackup Troubleshooting
Guide.
Whether Robust Logging is selected or not, the log file is pruned using
KEEP_LOGS_DAYS and DAYS_TO_KEEP_LOGS settings.
To change the debug levels, use the vxlogcfg command. Please refer to the
The following sections describe the services that use unified logging.
Job Manager
If you want to override the Global logging level, select a logging level for the Job
Manager (NBJM): 0 (minimum) through 5 (maximum). Select No logging to
produce no log for this service at all.
The Job Manager accepts the jobs that the Policy Execution Manager (NBPEM)
submits and acquires the necessary resources. This property appears for EMM
servers. This property does not appear for NetBackup hosts earlier than 6.0.
Resource Broker
If you want to override the Global logging level, select a logging level for the
Resource Broker (NBRB): 0 (minimum) through 5 (maximum). Select No logging
to produce no log for this service at all.
The Resource Broker makes the allocations for storage units, tape drives, client
reservations. This property does not appears for NetBackup hosts earlier than
6.0.
Host properties 445
Master server, media server, and client host properties
The following topics explain the settings. For more information, see the
NetBackup for Lotus Notes Administrator’s Guide.
Path
In the Path field, specify the path where the Lotus Notes program files reside on
the client. NetBackup must know where these files are to perform backup and
restore operations. The value in this box overrides the Lotus registry key, if both
are defined.
INI file
In the INI field, specify the absolute path to the NOTES.INI file. Enter the
NOTES.INI file that is associated with the server used to back up and restore
the Lotus database. Use this setting to specify the correct .INI file to back up
and restore from Domino partitioned servers. Specifying the .INI file for
non-partitioned servers is not necessary.
446 Host properties
Master server, media server, and client host properties
Media properties
The Media properties apply to selected master servers and media servers. Media
properties control how NetBackup manages media.
protection for specific media types. Normally, NetBackup does not overwrite
certain media types. To disable overwrite protection, place a check in the check
For example, place a check in the CPIO check box to permit NetBackup to
overwritten:
Caution: Ensure that all of your hardware processes SCSI persistent reserve
commands correctly. All of your hardware includes fibre-channel bridges. If the
hardware does not process SCSI persistent reserve commands correctly and
NetBackup is configured to use SCSI persistent reserve, no protection may exist.
Recommended use
All tape drive and bridge vendors support the SPC-2 SCSI reserve and release
method. NetBackup has used SPC-2 SCSI reserve since NetBackup 3.4.3, and it is
the default tape drive reservation method in NetBackup. SPC-2 SCSI reserve is
effective for most NetBackup environments.
Alternatively, the new SCSI persistent reserve method may be more effective in
either of the following environments because it provides device status detection
and correction:
■ You operate NetBackup media servers in a cluster environment. NetBackup
can recover and use a reserved drive after a failover (if NetBackup owns the
reservation). (With SPC-2 SCSI reserve, usually you must reset the drive
because the reservation owner is inoperative.)
Host properties 449
Master server, media server, and client host properties
■ You want very high drive availability. NetBackup can resolve NetBackup
drive reservation conflicts and maintain high drive availability. (SPC-2 SCSI
reserve provides no method for drive status detection.)
However, the SCSI persistent reserve method is not supported or not supported
correctly by all device vendors. Therefore, you should thoroughly analyze your
environment to ensure that all of your hardware supports SCSI persistent
reserve correctly. Symantec recommends that you carefully consider all of the
following factors before you use SCSI persistent reserve:
■ Only a limited number of tape drive vendors support SCSI persistent
reserve.
■ SCSI persistent reserve is not supported or not supported correctly by all
fibre channel bridge vendors. Incorrect support in a bridge means no access
protection. Therefore, if you use bridges in your environment, you should
not use SCSI persistent reserve.
■ If you have parallel SCSI buses, you should carefully consider the use of
SCSI persistent reserve. Usually, parallel drives are not shared, so SCSI
persistent reserve protection is not required. Also, parallel drives are usually
on a bridge, and bridges do not support SCSI persistent reserve correctly.
Therefore, if you use parallel SCSI buses in your environment, you should
not use SCSI persistent reserve.
■ You may have to configure your operating system tape drivers extensively to
use SCSI persistent reserve. For example, if your tape drives do not support
SPC-3 Compatible Reservation Handling (CRH), you must ensure that your
operating system does not issue SPC-2 reserve and release commands.
If any of your hardware does not support SCSI persistent reserve, Symantec
recommends that you do not use SCSI persistent reserve.
If the end of media is encountered and this property is not selected, the media is
set to FULL and the operation terminates abnormally. This action applies to
both robotic drives and nonrobotic drives.
■ To allow all NetBackup media servers and NDMP hosts in your NetBackup
environment to share media for writing, select this property. Do not
configure server groups for media sharing.
■ To restrict media sharing to specific server groups, clear this property, then
configure media server groups and backup policies to use media sharing.
■ To disable media sharing, clear this property and do not configure media
server groups.
By default, media sharing is disabled. (The property is cleared and no server
groups are configured.) For more information, see “Configuring server groups
for media sharing” on page 615.
another 60 seconds and checks again. If the total delay is not a multiple of 60,
the last wait is the remainder. If the delay is less than 60 seconds, NetBackup
checks only once at the end of the delay.
For example, set the delay to 150 seconds. NetBackup waits 60 seconds, checks
for ready, waits 60 seconds, checks for ready, then waits 30 seconds and checks
for ready the last time. If the delay had been 50 seconds (a short delay is not
recommended), NetBackup would have checked only once, at the end of 50
seconds.
To access the Add NDMP Host dialog, add a NDMP host under Media and Device
Management > Credentials > NDMP Hosts.
Host properties 453
Master server, media server, and client host properties
User name
The user name under which NetBackup accesses the NDMP server. This user
must have permission to run NDMP commands.
Network properties
The Network properties apply to currently selected Windows clients.
Under Network properties, set the properties that define requirements for
communications between clients and the master server.
Note: If you change this port number, remember that it must be the same for all
NetBackup servers and clients that communicate with one another.
Note: If you change this port number, remember that it must be the same for all
NetBackup servers and clients that communicate with one another.
Host properties 455
Master server, media server, and client host properties
Media Manager services include tape library control daemons, which accept
connections from daemons on other servers that share the same library. See
the services file on the media server to determine the ports that are
required for a specific library.
■ Dynamically-allocated ports are assigned as needed, from configurable
ranges in the Port Ranges host properties for NetBackup servers and clients.
In addition to the range of numbers, you can configure the following for
dynamically-allocated ports:
Host properties 457
Master server, media server, and client host properties
NetBackup randomly chooses a port from those that are free in the allowed
range. For example, if the range is from 1023 through 5000, it chooses randomly
By default, Use random port assignments is selected, and ports are randomly
chosen.
NetBackup starts with the highest number that is available in the allowed range.
For example, if the range is from 1023 through 5000, NetBackup chooses 5000
on this computer that are used for connecting to NetBackup on other computers.
configured to accept only reserved ports. (See Allow non reserved ports on the
To let the operating system determine the non-reserved port to use, enable Use
Universal Settings dialog box.) Server port window does not appear in a client
configuration.
To let the operating system determine the non-reserved port to use, enable Use
only reserved ports. (See Allow non reserved ports on the Universal Settings
dialog box.) Server reserved port window does not appear in a client
configuration.
To let the operating system determine the non-reserved port to use, enable Use
■ Two or more media servers share a robot and each has connected drives.
When a restore is requested, one of the servers is temporarily inaccessible.
■ Two or more media servers have stand-alone drives of the same type. When
a restore is requested, one of the servers is temporarily inaccessible.
In these instances, inaccessible means that the connection between bprd on the
master server and bptm on the media server (through bpcd) fails. Possible
reasons for the failure are:
■ The media server is down.
■ The media server is up but bpcd does not respond. (For example, if the
connection is refused or access is denied.)
460 Host properties
■ The media server is up and bpcd is running but bptm has problems. (For
example, if vmd is down or bptm cannot find the required tape.)
Add button
To include a NetBackup media server in the Alternate restore failover machines
list, click Add.
To add or change a media server to the alternate restore failover machine list
1 To add an entry, click Add. The Add Failover Servers dialog box appears.
To change an entry, click Change. The Change Failover Servers dialog box
appears.
2 In the Media server field, specify the media server for failover protection.
3 In the Failover restore servers field, specify the media server(s) to try if the
server that is designated in the Server field is unavailable. Separate the
names of multiple servers with a single space.
4 Click Add to add the name to the list. The dialog box remains open for
another entry.
Click OK if an entry was changed. Click Close to close the dialog box.
5 Click Apply to accept the Restore Failover property changes. Click OK to
close the host properties dialog box.
Host properties 461
Master server, media server, and client host properties
6 Stop and restart the NetBackup Request daemon on the master server where
the configuration was changed.
For more information on failover, see “Method 3: Automatic failover to alternate
server” on page 692.
Change button
To change an entry in the Alternate restore failover machines list, select a
media server, then click Change.
Remove button
To remove a NetBackup media server from the Alternate restore failover
machines list, select the media server to be removed, then click Remove.
Media server
Browse to a media server for which to configure a failover restore server(s).
Value
The Value specifies the retention level setting.
Units
The Units property specifies the units of time for the retention period. The list
includes the special units, Infinite and Expires immediately.
many schedules currently use each level. If the retention period is changed for a
level, it affects all schedules that use that level.
Schedules list
The dialog box contains a list of the schedules that use the currently selected
retention level, and the policy to which each schedule belongs.
The dialog box displays the names of all schedules that use the selected
retention level as well as the policy to which each schedule belongs.
3 Type the new retention period in the Value box.
4 Select the units of measure (days, weeks, months, years, infinite, or expires
immediately).
Note: After Units or Value is changed, an asterisk (*) appears in the Changes
Pending column to indicate that the period was changed. NetBackup does not
change the actual configuration until Apply or OK is clicked.
■ Apply: Saves the changes and leaves the dialog box open to make
further changes.
■ OK: Saves the changes since Apply was last clicked. OK also closes the
dialog box.
8 To save the changes, click OK.
Servers properties
The Servers properties display the NetBackup server list on selected master
servers, media servers, and clients. The server list displays the NetBackup
servers that each host recognizes.
Master server
The Master server property specifies the master server for the selected host.
(The name of the selected host appears in the title bar.)
Additional servers
The Additional Servers list contains the additional servers that can access the
server that is specified as Master server.
During installation, NetBackup sets the master server to the name of the system
where the server software is installed. NetBackup uses the master server value
to validate server access to the client. The master server value is also used to
determine which server the client must connect to so that files can be listed and
restored.
■ To add a server, click Add and select a server.
■ To delete a server, select a server from the list, then click Remove.
466 Host properties
Master server, media server, and client host properties
■ To change the master server, select another server from the list, then click
Make Master.
To configure access to a remote server, add to the server list the name of the
host seeking access. For more information, see “To administer a remote master
server” on page 639.
Media servers
The Media servers list specifies that the listed machines are media servers only.
Machines that are listed as media servers can back up and restore clients, but
have limited administrative privileges.
■ To add a new media server, click Add and select a server.
Run nbemmcmd -addhost to add a media server to the Enterprise Media
Manager (EMM) database of existing master server.
■ To delete a media server, select a media server from the list, then click
Remove.
Machines that are listed as media servers can back up and restore clients, but
Figure 7-42 Media Server list in Servers host properties dialog box
Consider a configuration that consists of master server oak and two media
servers—elm and pine. Set up oak as the master server and elm and pine as
media servers.
If a machine is defined as both a master server and a media server, the master
A server that is listed as both a master and a media server has consequences. It
Figure 7-43 Server that are listed as both media server and master server
SERVER entries:
■ The first SERVER entry must be the name of the master server.
The following master servers also need to be listed:
■ In order for the NetBackup Administration Console to administer other
servers, the servers must be listed. (File > Change Server.)
■ If the EMM database is on another master server, that server needs to
be listed. The table shows how meadow is listed on havarti and study.
The EMMSERVER entry must be present on all master servers that share the
EMM host. The table shows how meadow is listed as the EMMSERVER on havarti,
study, as well as on meadow.
Host properties 469
Master server, media server, and client host properties
To update the EMM database, after changing the master server for a media server, run:
2
/usr/openv/netbackup/bin/admincmd/nbemmcmd -updatehost
SharedDisk properties
The SharedDisk master server properties specify the SharedDisk storage option
properties for your NetBackup configuration.
User ID
Specify the user id for the account to use to log on to SharePoint (DOMAIN\user
name).
Password
Specify the password for the account.
index pages for each user table are included in the consistency check. The
Physical check only (SQL 2000 only): Select this property to perform a low
overhead check of the physical consistency of the SQL Server 2000 database.
This property checks the integrity of the physical structure of the page and of
record headers. It also checks the consistency between the pages’ object ID and
Use the Add button to add a host that is authorized to run restores on
SharePoint component hosts. Provide the name of the Farm front-end host and
the name of the Farm component host in the farm.
Host properties 473
Master server, media server, and client host properties
The Symantec Products properties include the subnode, “Backup Exec Tape
Reader properties” on page 375.
474 Host properties
Master server, media server, and client host properties
Timeouts properties
The Timeouts properties apply to selected master servers, media servers, and
clients.
Note: If this timeout is changed, verify that Client read timeout is set to the
same or higher value.
Host properties 475
Master server, media server, and client host properties
If File browse timeout is exceeded, the user receives a socket read failed error
even if the server is processing the request.
Note: For database-extension clients, Symantec suggests that the Client read
timeout be set to a value greater than 5 minutes. 15 minutes is adequate for
many installations. For other clients, change Client read timeout only if
problems are encountered.
Note: If this timeout is changed, verify that Client read timeout is set to the
same or higher value.
Restore retries
The Restore retries setting specifies the number of attempts a client may try to
restore after a failure. (Default: 0; the client does not attempt to retry a restore.
The client may try up to 3 times.) Change Restore retries only if problems are
encountered.
A checkpointed job is retried from the start of the last checkpointed file rather
than at the beginning of the job.
If a job fails after the maximum number of retries, the job goes into the
incomplete state. The job remains in the incomplete state as determined by the
Move restore job from incomplete state to done state property. Checkpoint
Restart for restores allows a NetBackup administrator to resume a failed restore
job from the Activity Monitor. For more information, see “Move restore job from
incomplete state to done state” on page 385.
478 Host properties
Master server, media server, and client host properties
One solution is to set Use specified network interface on fred to fred_nb. All
backup, restore, and list requests use the fred_nb interface. The server receives
requests from client fred_nb with host name fred_nb and everything works as
intended.
Another solution is to set up the master server to allow redirected restores for
client fred. Redirected restores allow the server to accept the request, but leaves
NetBackup traffic on the regular network.
requesting server is not included in the server list for the server that performs
the restore. (A progress log is an entry in the Task Progress tab of the Backup,
Without the entry in the server list, the restoring server has no access to write
■ To produce a progress log, add the requesting server to the server list:
log into the requesting server. In the NetBackup Administration Console,
expand NetBackup Management > Host Properties > Master Servers >
Double-click on master server > Servers. Add the restoring server to the
server list.
■ Log in to the restoring server. Check the Activity Monitor to determine the
success of the restore operation.
Click Add to add a server to the Proxy Server list. To delete a server from the list,
A VMWare proxy server is a server on the same SAN as a VMware ESX server
that can access the snapshot of the VMware Virtual Machine and provide access
For more information, see the NetBackup Snapshot Client Administrator’s Guide.
Host properties 485
Master server, media server, and client host properties
In order for the properties in this dialog box to affect client(s), VSP must be
selected as the snapshot provider for the client(s). VSP is the default Windows
snapshot provider.
Snapshots are a point-in-time view of a source volume. NetBackup uses
snapshots to access busy or active files during a backup job.
To make VSP the snapshot provider for a Windows client, select:
NetBackup Management > Host Properties > Master Servers > Select master
server for the client > Client Attributes > Windows Open File Backup tab > Use
Veritas Volume Snapshot Provider (VSP). For more informations, see “Client
Attributes properties” on page 386.
VSP overview
NetBackup uses VSP to back up open and active files on Windows 2000,
Windows XP, and Windows Server 2003 (32- and 64-bit) clients. For VSP to back
up open and active files, VSP first captures a snapshot of each volume to be
486 Host properties
Master server, media server, and client host properties
backed up. A virtual drive is created that represents a static copy of the volume
at a point-in-time. A corresponding VSP cache file is also created.
NetBackup backs up files using the virtual drive instead of the actual drive. For
each volume snapshot, a VSP cache file is created to maintain the integrity of
the snapshot. The cache file stores the original data that reflects the changes
that occurred during the backup. The cache file is created along with the volume
snapshot.
VSP is similar to OTM (used in previous releases) in that VSP creates volume
snapshots using a caching mechanism. However, consider the following points
when using VSP:
■ VSP uses a cache file for each volume that requires a snapshot, while OTM
uses only one cache for all snapshots.
■ Using VSP, a snapshot of a volume cannot be created if the volume already
contains a VSP cache file.
■ Using VSP, a cache file cannot be placed on a volume that has had a
snapshot taken. Or, a cache file cannot be placed on a volume that is in the
process of having a snapshot taken of it. Only when the snapshot for the
volume has been destroyed can it be used as a location for a VSP cache file.
■ All VSP cache files are placed at the root level of a volume and are removed
when its VSP snapshot has been destroyed.
■ VSP cannot be used to perform hot database backups. For more
informations, see “Using VSP with databases” on page 492.
4 Once the backup completes, NetBackup attempts to destroy the VSP volume
snapshots that were created for the backup job. It attempts to destroy the
VSP snapshots while deleting the VSP cache files for the volume snapshots.
C:\Program Files\VERITAS\NetBackup\Logs\
To create detailed log information, set the Global logging level to a higher value
in the master server host property Logging dialog box. (Host Properties >
Master Servers > Selected master server > Logging.) Eventually, the bpfis
directory can require extensive disk space. Delete the directory when the
troubleshooting is complete and reset the Global logging level to a lower value.
3 Subsequent backups cannot use C as a VSP cache file location until the VSP
volume snapshots that are created in step 2 have been destroyed.
Ramifications of the precedence of the volume list over the exclude list
The volumes in the Cache file volume list have precedence over the volumes
that are listed in the VSP volume exclude list. The Cache file volume list
overrides the VSP volume exclude list if both lists contain the same volume.
For example, C:\ is specified in the Cache file volume list and in the VSP volume
exclude list. The user prefers the C:\ volume as the location for VSP cache files,
yet would not like VSP to snap or place cache files on the volume.
Because the Cache file volume list takes precedence over the VSP volume
exclude list, NetBackup places cache files in C:\ even though it is listed in the
VSP volume exclude list. NetBackup does not create snapshots for C:\ until C:\
is removed from the VSP volume exclude list.
Using the cache file volume list and VSP volume exclude list for multiple
simultaneous backup jobs or multiple groups of multistreamed jobs
NetBackup allows a scheduled backup to be broken into several backup streams
that can run simultaneously to increase performance. For more information, see
“Allow multiple data streams” on page 112.
If a backup policy is configured to allow multiple data streams, a scheduled
client backup can be divided into multiple data streams. Each file list directive in
the policy forms a separate backup job (stream) that runs concurrently with
other streams to help complete the scheduled backup. All backup jobs (streams)
in a policy are grouped into an entity that is called a stream group. All backups
that are part of a stream group share their VSP volume snapshots between
backup jobs in the stream group.
Additionally, multiple backup jobs could also run concurrently on a single client
even if a backup policy is configured not to allow multiple data streams.
For both types of backups, use the Cache file volume list and VSP volume
exclude list to make sure that VSP snapshot creation is successful. To run these
backups, Symantec recommends that a volume be listed in both the Cache file
volume list and the VSP volume exclude list. This volume is effectively used as
Host properties 489
Master server, media server, and client host properties
the volume for all VSP cache files. However, VSP snapshots are not created for
it. All backups for the volume do not have VSP snapshots enabled.
D:\ Dir2
Policy 2:
C:\ Dir3
D:\ Dir4
the D drive was listed in both the Cache file volume list and the VSP volume
exclude list, VSP cache files for the C drive for both groups of multistreamed
jobs were placed in the D drive. Both groups of multistreamed jobs also
backed up the D drive without VSP.
If the D drive was not listed in the Cache file volume list and the VSP volume
exclude list, VSP would not have been enabled for the C and D drives for both
groups of multistreamed jobs.
Cache size
The Cache size property specifies the initial size of the VSP cache file that is
allowed for snapshots.
which no file write-activity occurs on the drive being snapped using VSP.
(Default: 5 seconds.) A value less than 5 seconds is not recommended because
the data that is backed up as a result of a low setting may become corrupted.
an inactive state, NetBackup does not perform the VSP snapshot. NetBackup
does not fail the backup when a quiescent state is not achieved. Instead,
NetBackup continues the backup as if VSP is not in use. The result is that
NetBackup skips open, active, or locked files. The backup job ends with an exit
status code 1. Status code 1 indicates that the backup job was completed but not
all files were successfully backed up.
If VSP is used to back up database environments, first back up the data and
make sure that the backup exited with a Status 0. Then, restore the database and
confirm the integrity of the data and the functionality of the database.
Using VSP to back up active databases without using a formal API presents risk.
Customers should contact the database supplier to ensure support of database
backups using point-in-time technology. Also, significant back up and restore
testing should be performed to assure database availability and reliability.
494 Host properties
Master server, media server, and client host properties
Resetting a drive
4 From the Actions menu, choose the command for the new drive operating
mode.
Up Drive, Operator control applies only to stand-alone drives.
5 If the drive is configured with multiple device paths or is a shared drive
(Shared Storage Option), a dialog box appears. The dialog box contains a list
of all device paths to the drive. Select the path to change. To change multiple
paths, select multiple paths.
Resetting a drive
Resetting a drive changes the state of the drive.
Usually, you reset a drive when its state is unknown, which can occur if an
application other than NetBackup uses the drive. When you reset the drive, it
exists on the drive, a reset operation from that host that owns the reservation
Note: A drive reset does not perform any SCSI bus or SCSI device resets.
To reset a drive
1 In the NetBackup Administration Console, select Media and Device
Management > Device Monitor.
If an Enterprise Disk Option license is installed, the Device Monitor pane
includes both a Drives tab and a Disk Pools.
2 If necessary, select the Drives tab.
3 In the Drive status pane, select a drive or select multiple drives.
4 Select Actions > Reset Drive.
If the drive is in use by NetBackup and cannot be reset, you can restart the
NetBackup Job Manager, which should free up the drive.
1 Determine which job controls the drive (that is, which job writes to or reads
from the drive).
2 In the NetBackup Administration Console, select NetBackup Management >
Activity Monitor.
Device Monitor 497
Managing drive paths
Caution: When you restart the NetBackup Job Manager, it cancels all
NetBackup jobs in progress.
request in the Pending Requests pane. Pending actions usually occur with drives
in robotic libraries.
For pending actions, NetBackup determines the cause of the problem and issues
pending action; the icon appears to the left of the request ID. The icon includes a
Resubmitting a request
After you correct the problem or problems with a pending action, you can
If the problem is a volume missing from a robot, first locate the volume, insert it
into the robot, and then update the volume configuration. Usually, a missing
To resubmit a request
1 In the NetBackup Administration Console, select Media and Device
Management > Device Monitor.
If an Enterprise Disk Option license is installed, the Device Monitor pane
includes both a Drives tab and a Disk Pools.
2 If necessary, select the Drives tab.
3 In the Pending Requests pane, select the request.
4 Select Actions > Resubmit Request.
The pending action message is removed from the Pending Requests pane
and the operation proceeds.
Denying a request
Some situations may require you to deny requests for service. For example,
when a drive is not available, you cannot find the volume, or the user is not
authorized to use the volume. When you deny a request, NetBackup sends an
appropriate status message to the user.
To deny a request
1 In the NetBackup Administration Console, select Media and Device
Management > Device Monitor.
If an Enterprise Disk Option license is installed, the Device Monitor pane
includes both a Drives tab and a Disk Pools.
2 If necessary, select the Drives tab.
Cleaning drives
The following are the default values for the error thresholds:
■ The media error threshold is 2 (that is, NetBackup freezes media on the
third media error in 12 hours).
■ The drive error threshold is 2 (that is, NetBackup downs a drive on the third
drive error in 12 hours).
■ The time window for errors is 12 hours.
You can use the NetBackup nbemmcmd command with the
-media_error_threshold, -drive_error_threshold, and
-time_window options to change the default values. For more information
about nbemmcmd, see NetBackup Commands for UNIX and Linux.
Cleaning drives
You can perform an operator-initiated cleaning of a drive regardless of the
cleaning frequency or accumulated mount time of the drive. You can clean a
stand-alone drive or a robotic drive if appropriate cleaning media are added to
the EMM database.
You can also use the Device Monitor to:
■ Reset the mount time of the drive. You should reset the mount time to zero
after you perform a manual cleaning.
■ Set the cleaning freqency. Automatic, frequency based drive cleaning is
configured when you add a drive to NetBackup. If you use the Device
Monitor to set the cleaning frequency, NetBackup updates the cleaning
frequency value for the drive.
For more information, see “Drive cleaning overview” in the NetBackup
Administrator’s Guide for UNIX and Linux, Volume II
To clean a drive
1 In the NetBackup Administration Console, select Media and Device
Management > Device Monitor.
If an Enterprise Disk Option license is installed, the Device Monitor pane
includes both a Drives tab and a Disk Pools.
2 If necessary, select the Drives tab.
Device Monitor 503
Cleaning drives
You can add a comment that describes how a drive is used or change an existing
comment. Drive comments appear in the Drive Status pane.
For shared drives, you can view the drive control mode and drive index for
each host that shares a drive. You also can view a list of hosts that share a
drive.
506 Device Monitor
Viewing drive details
Chapter 9
Media
Use Media and Device Management > Media to add and manage media (tape
volumes) to NetBackup. The media can already reside in a storage devices, or
you can add them to your storages devices when you add them to NetBackup.
For information about how to manage media in NetBackup and the logical
entities that help you manage volumes, see the following:
■ “Volume operations” on page 507
■ “Volume pool operations” on page 538
■ “Volume group operations” on page 542
For information about how to inventory robots and how to update the
NetBackup volume configuration with media changes in the robots, see the
following:
■ “Robot inventory operations” on page 544
If you have volumes without barcodes to manage, see “Using the physical
If you have WORM media, see “Using WORM media” on page 589.
Volume operations
Volumes are units of data storage or cleaning capability on removable media
(tapes or optical platters). NetBackup assigns IDs and other attributes to the
media. NetBackup uses the attributes to track and manage the media. Attributes
include the media ID, robot host, robot type, robot number, and slot location.
Volume information is stored in the EMM database.
The following are operations you can perform on volumes:
■ “Adding volumes” on page 508
508 Media
Volume operations
Adding volumes
Several methods exist to add new volumes to NetBackup, as follows:
■ “Adding volumes by using the Volume Configuration Wizard” on page 511
■ “Adding volumes using a robot inventory update” on page 511
■ “Adding volumes using the Actions menu” on page 512
To help you determine which method to use, review the following information:
Note: When you add a new volume, a volume expiration date is not assigned.
Robotic volumes
Robotic volumes are volumes located in a robot.
The easiest way to add robotic volumes is to use the Volume Configuration
Stand-alone volumes
Stand-alone volumes are volumes located in a drive that is not in a robot. To
determine a method for adding stand-alone volumes, review the following:
■ The easiest way to add stand-alone volumes is to use the Volume
Configuration Wizard. NetBackup assigns media IDs and labels the volumes
automatically. Because NetBackup does not label volumes until it uses them,
you can add a range of volumes. Then, when NetBackup requests one of the
volumes, you can insert it into the stand-alone drive and NetBackup labels
it.
■ You can also add volumes by inserting the media into a stand-alone drive
and by using Media and Device Management in the NetBackup
Adminstration Console. NetBackup assigns media IDs and labels the
volumes automatically. NetBackup uses the volume if a volume of that type
is required for a backup.
The DISABLE_STANDALONE_DRIVE_EXTENSIONS option of the nbemmcmd
command can turn off NetBackup’s automatic use of stand-alone volumes.
For more information, see NetBackup Commands for UNIX and Linux.
■ You can add additional stand-alone volumes to the NetBackup
configuration even though they do not reside in the drive. The additional
volumes are available for use if the volume in the drive becomes full or
unusable. First, use the NetBackup bplabel command to label the volume
and assign a media ID. Second, follow the instructions in “Adding volumes
using the Actions menu” on page 512.
For more information, see NetBackup Commands for UNIX and Linux.
Even if you use NetBackup’s assignment capabilities to add stand-alone
volumes, you may prevent out of media errors by adding extra
stand-alone volumes manually. For example, if a volume in a stand-alone
drive is full or unusable because of errors, NetBackup ejects (logically) the
volume. If you added another stand-alone volume, NetBackup requests that
volume and does not generate an error.
510 Media
Volume operations
you assign them to the volume pool you use for catalog backups.
After you add volumes, use the NetBackup Catalog Backup wizard to configure a
Prelabeling media
It may be beneficial to prelabel media for the following reasons:
■ A successful label operation validates that the media is usable, compatible,
and is not write-protected.
■ The recorded label may assist with media management if:
Media 511
Volume operations
After the wizard configures media, each media has a unique media ID in the
EMM database. The wizard uses the default media type for the drive to create
Review the limitations in the wizard help before you configure volumes.
Note: Be careful when you specify properties. You cannot change some
properties later, such as the media ID or type. If you specify them
incorrectly, you must delete the volume and add it again.
The Apply button adds the volume without closing the dialog or refreshing the
display. You can add another volume by modifying the dialog contents and then
click Apply or OK.
If the robot has a barcode reader, NetBackup does the following:
■ Adds the volume to the EMM database using the specified media ID.
■ Reads the barcode of each new volume.
■ Adds the barcodes as attributes in the EMM database.
Media 513
Volume operations
Volumes properties
The following sections describe the properties you can configure when you add
volumes.
Device host
NetBackup Enterprise Server only.
Specifies the name of the device host where the robot is defined.
First media ID
Appears only if the number of volumes or platters is more than one.
When you add a range of volumes, specifies the ID of the first volume in the
range of volumes. Media IDs can be from 1 to 6 characters in length.
Use the same pattern that you chose in the Media ID naming style box. Using the
pattern, NetBackup names the remaining volumes by incrementing the digits.
For information about the characters you can use in a name, see “NetBackup
naming conventions” on page 631.
Note: You cannot enter slot information for volumes in an API robot. The robot
vendor tracks the slot locations for API robot types.
NetBackup labels media when you add it. If you need to format your optical
media, refer to the tpformat command in NetBackup Commands for UNIX and
Linux.
For information about the characters you can use in a name, see “NetBackup
naming conventions” on page 631.
Media ID
Specifies the ID for the new volume. Media IDs can be from 1 to 6 characters in
length.
Media IDs for an API robot must match the barcode on the media (for API robots,
obtain a list of the barcodes before you add the volumes. You can obtain this
For information about the characters you can use in a name, see “NetBackup
Media type
For optical disk volumes that are supported on UNIX and Linux only.
Media type specifies the media type for the volume to add.
Media description
Enter a description of the media, up to 25 character maximum.
For information about the characters you can use in a name, see “NetBackup
Partner ID
Optical media only.
Specify a partner ID for optical media. The partner ID is media ID of the volume
on the other side of the optical platter.
Robot
Specifies the robotic library to add the volumes to.
To add volumes to a different robot, select a robot from the list. The list shows
robots on the selected host that can contain volumes of the selected media type.
To add volumes to a stand-alone drive, select Standalone.
Volume group
The volume group shows the location of the volume. The location can be either
the robot in which the volume resides, stand-alone, or off-site if you use the
NetBackup Vault option.
516 Media
Volume operations
If you specified a robot, you can select from a volume group already configured
for that robot. Alternatively, enter the name for a volume group; if it does not
exist, NetBackup creates it and adds the volume to it.
If you do not specify a volume group (you leave the volume group blank):
■ Stand-alone volumes are not assigned to a volume group.
■ NetBackup generates a name for robotic volumes using the robot number
and type. For example, if the robot is a TL8 and has a robot number of 50,
the group name is 000_00050_TL8.
Rules for assigning volume groups
The following are the rules for assigning volumes to groups:
■ All volumes in a group must be the same media type. However, a media type
and its corresponding cleaning media type are allowed in the same volume
group (such as DLT and DLT_CLN).
■ All volumes in a robotic library must belong to a volume group. You cannot
add volumes to a robotic library without specifying a group or having
NetBackup generate a name.
■ The only way to clear a volume group name is to move the volume to
stand-alone and not specify a volume group.
■ More than one volume group can share the same location. For example, a
robotic library can contain volumes from more than one volume group and
you can have more than one stand-alone volume group.
■ All members of a group must be in the same robotic library or be
stand-alone. That is, you cannot add a group (or part of a group) to a robotic
library if it already exists in another robotic library.
For more information, see “Volume pool and volume group overview” in the
NetBackup Administrator’s Guide for UNIX and Linux, Volume II
Volume pool
The pool to which the volume or volumes should be assigned. You can select a
volume pool you created or one of the following standard NetBackup pools:
■ None.
■ NetBackup is the default pool name for NetBackup.
■ DataStore is the default pool name for DataStore.
Media 517
Volume operations
■ CatalogBackup is the default pool name used for NetBackup hot, online
catalog backups of policy type NBU-Catalog.
When the images on a volume expire, NetBackup returns it to the scratch
volume pool if it was allocated from the scratch pool.
For more information, see “Volume pool and volume group overview” in the
NetBackup Administrator’s Guide for UNIX and Linux, Volume II
Description
Specifies how the selected volumes are used or any other relevant information
For information about the characters you can use in a name, see “NetBackup
Expiration date
Does not apply to cleaning tapes.
Specifies the age of the volume and is the date after which the volume is too old
to be reliable.
When the expiration date has passed, NetBackup reads data on the volume but
When you add a new volume, a default expiration date is not added.
The expiration date is not the same as the retention period for the backup data
on the volume. You specify data retention periods in the backup policies.
Media 519
Volume operations
Maximum mounts
Does not apply to cleaning tapes.
The number of times that the selected volumes can be mounted.
When the limit is reached, NetBackup reads data on the volume but does not
Volume pool
Does not apply to cleaning tapes.
The pool to which the volume or volumes should be assigned. You can select a
volume pool you created or one of the following standard NetBackup pools:
■ None.
■ NetBackup is the default pool name for NetBackup.
■ DataStore is the default pool name for DataStore.
■ CatalogBackup is the default pool name used for NetBackup hot, online
catalog backups of policy type NBU-Catalog.
For more information, see “Volume pool and volume group overview” in the
NetBackup Administrator’s Guide for UNIX and Linux, Volume II
box.
If you move a volume physically to a different robot, you must change the group
of the volume to reflect the move.
For more information about server groups, see “Configuring server groups for
A frozen volume is available for restores. If the backups have expired, you must
import the backups first.
Labeling media
When NetBackup labels media, it writes a record on the media; the record (or
label) includes the NetBackup media ID. Normally, NetBackup controls the
labeling of its volumes and in most cases performs this operation automatically.
However, media are not labelled automatically if:
■ They were last used for NetBackup catalog backups.
■ They contain data from a recognized non-NetBackup application and
NetBackup is configured to prohibit media overwrite for that media type.
You can label these media manually as follows:
■ If NetBackup has not assigned them
■ If they contain no valid NetBackup images
522 Media
Volume operations
If a volume has valid NetBackup images, you can deassign the volume so you can
label it.
If you want to label media and assign specific media IDs (rather than allow
Caution: If you label a volume, NetBackup cannot restore or import the data that
was on the media after you label it.
Caution: For many types of drives, you may not be able to cancel a label job from
the Activity Monitor.
For more information, see “About labeling NetBackup volumes” on page 510.
To label media
1 In the NetBackup Administration Console, select Media and Device
Management > Media.
2 In the Volumes pane, select a volume or the volumes that you want to label.
If you select multiple volumes, they all must reside in the same robot.
3 Select Actions > Label.
4 In the Label dialog, specify the properties for the label operation.
For descriptions of the properties, see “Label properties” on page 523.
5 Click OK.
6 In the warning dialog, click OK.
If you selected Verify media label before performing operation and the
actual volume label does not match the expected label, the media is not
relabeled.
Media 523
Volume operations
Label properties
The following sections describe the properties you can specify for a label
operation.
Media server
The name of the media server that controls the drive to write the label.
Note: Rescan/Update Barcodes does not apply to volumes in API robot types.
Volume operations
Rescanning/updating barcodes
To check barcodes and update the EMM database
1 In the NetBackup Administration Console, select Media and Device
Management > Media > Robots.
2 Select the robotic library that contains the volumes that you want to scan
and update.
3 In the Volumes pane, select the volumes.
4 Select Actions > Rescan/Update Barcodes.
A dialog appears that shows the volumes you selected for the rescan
operation.
Click Start to continue or Close to quit. If you select Start, the results of the
update are displayed in the output section of the dialog.
Moving volumes
When you move volumes in or out of a robotic library or from one robot to
another, you must move the volumes physically and logically:
■ Physically move volumes by inserting or by removing them. For some robot
types, you can use the NetBackup inject and eject options.
■ Logically move volumes using NetBackup, which updates the EMM database
to show the volume at the new location.
When you move volumes from one robotic library to another robotic library, you
must do the following:
■ Move the volumes to stand-alone as an intermediate step
■ Move the volumes to the new robotic library
You can perform the following types of logical moves:
■ Move single volumes
■ Move multiple volumes
■ Combinations of single and multiple volumes
■ Move volume groups
You cannot move volumes to an invalid location (for example, move DLT media
to an 8-mm robot).
Media 525
Volume operations
Symantec recommends that you perform moves by selecting and by moving only
one type of media at a time to a single destination.
Move examples
The following are several examples of when to move volumes logically:
■ A volume is full in a robotic library and no slots are available for new
volumes in the robotic library. Move the full volume to stand-alone, remove
it from the robot, and then configure a new volume for the empty slot or
move an existing volume into that slot. You can use the same process to
replace a defective volume.
■ Moving volumes from a robotic library to an off-site location or from an
off-site location into a robotic library. When you move tapes to an off-site
location, move them to stand-alone.
■ Moving volumes from one robotic library to another (for example, if a
library is down).
■ Changing the volume group for a volume or volumes.
Note: If you move a single volume, the dialog entries show the current
location of the volume.
Device host
Specifies the name of the device host where the robot is defined.
Media 527
Volume operations
Note: You cannot enter slot information for volumes in an API robot. The robot
vendor tracks the slot locations for these robot types.
Robot
Robot specifies the new robotic library for the volumes. You can specify a
The list shows the robot type, number, and control host for any robot that
Volume group
Enter or select the volume group to assign to the volumes.
If you leave the volume group blank:
■ Stand-alone volumes are not assigned a volume group.
■ Robotic volumes are assigned to a new volume group; NetBackup generates
the name by using the robot number and type. For example, if the robot is a
TL8 and has a robot number of 50, the group name is 000_00050_TL8.
The following are the rules for moving volumes between groups:
■ The new volume group must be for the type of volumes as you are moving.
■ All volumes in a robotic library must belong to a volume group. If you do not
specify a group, NetBackup generates a new volume group name by using
the robot number and type.
■ More than one volume group can share the same location. For example, a
robotic library can contain volumes from more than one volume groupm and
you can have more than one stand-alone volume group.
■ All members of a group must be in the same robotic library or be
stand-alone. That is, if volume group already exists in another robotic
library, you cannot add it (or part of a it) to a robotic library.
Volume operations
You can select a robot (see Robot) and the slot number for the volume (see First
slot number).
Volumes to move
The Volumes to move section of the dialog shows the media IDs of the volumes
If you selected one side of an optical disk platter, that side is shown but both
Erasing media
Caution: If you erase media, NetBackup cannot restore or import the data on the
media.
If a volume has valid NetBackup images, you can deassign the volume so you can
label it.
■ SCSI long erase rewinds the media and the data is overwritten with a known
data pattern. An SCSI long erase is also called a secure erase because it
erases the recorded data completely.
■ SCSI quick erase rewinds the media and an erase gap is recorded on the
media. The format of this gap is drive dependent. It may be an end-of-data
(EOD) mark or a recorded pattern that the drive does not recognize as data.
Some drives do not support a quick erase (such as QUANTUM DLT7000).
For the drives that do not support a quick erase, the new tape header that is
written acts as an application-specific quick erase.
Media 529
Volume operations
To erase media
1 In the NetBackup Administration Console, select Media and Device
Management > Media.
2 In the volumes pane, select a volume or volumes that you want to erase.
If you selected multiple volumes, they must all be in the same robot
3 For a short erase, select Actions > Quick Erase.
For a long erase, select Actions > Long Erase.
4 In the erase dialog, specify the name of the media server the name of the
media server to initiate the erase operation.
To overwrite any existing labels on the media, do not select Verify media
label before performing operation.
Click OK.
5 A dialog warns you that this action is irreversible. Click OK if you are certain
you want to start the erase action.
6 A dialog reminds you to use the Activity Monitor to view the progress and
status of the action. Click OK.
If you selected Verify media label before performing operation and the
actual volume label does not match the expected label, the media is not
erased.
Use the Activity Monitor to view the status of the action.
Caution: For many types of drives, you may not be able to cancel a label or erase
media job from the Activity Monitor.
Volume operations
Injecting volumes
Inject volumes into the robots that have media access ports by loading the
volumes in the MAP and then inventory the robot. Select Empty media access
Any volumes to be injected must be in the media access port before the
operation begins. If no volumes are in the port, you are not prompted to place
volumes in the media access port and the update operation continues.
Each volume in the MAP is moved into the robotic library. If the MAP contains
multiple volumes, they are moved to empty slots in the robotic library until the
After the volume or volumes have been moved, NetBackup updates the volume
configuration.
Some robots report only that media access ports are possible. Therefore, Empty
media access port prior to update may be available for some robots that do not
Ejecting volumes
You can eject single or multiple volumes.
Operator intervention is only required if the robotic library does not have a
media access port large enough to eject all of the selected volumes. For these
robot types, NetBackup prompts an operator to remove the media from the
For more information about eject, see “Media ejection timeout periods” on
page 532.
To eject volumes
1 In the NetBackup Administration Console, select Media and Device
Management > Media.
2 In the Volumes pane, select one or more volumes that you want to eject.
Media 531
Volume operations
4 The Eject Volumes dialog box has two tabs, described as follows.
■ After NetBackup completes prechecks for the eject, the Media tab of the
Eject Volumes dialog box shows the volumes that you selected to eject.
■ If no errors occur, the Errors tab is empty. If an error occurs or a
hardware limitation exists, the eject may not be possible; if so, the
Errors tab is opened. The following two classes of errors can occur:
■ For serious errors, the Eject button is not active; you must correct
the error before you can eject the media.
■ For other errors, the Errors tab shows an explanation of the error.
You may continue the eject action (select Eject) or exit (select
Close) depending on the type of error.
5 ACS and TLM robots only: In the Eject Volumes dialog box, select the media
access port to use for the eject.
6 In the Eject Volumes dialog box, click Eject to eject the volumes.
The robotic library may not have a media access port large enough to eject
all of the selected volumes. For most robot types, you are prompted to
remove the media from the media access port so the eject can continue with
the remaining volumes.
532 Media
Volume operations
Tape Library Half-inch (TLH) None. The robot allows an unlimited Applies only to
period to remove media. NetBackup
Enterprise
Server.
Caution: If media is not removed and a timeout condition occurs, the media is
returned to (injected into) the robot. You should inventory the robot and then
eject the media that was returned to the robot.
Some robots do not have media access ports. For these robots, the operator must
remove the volumes from the robot manually.
Note: After you add or remove media manually, use NetBackup to inventory the
robot.
Deleting volumes
You can delete volumes from the NetBackup configuration. For example, if any
of the following situations apply, you may want to delete the volume:
■ A volume is no longer used and you want to recycle it by relabeling it with a
different media ID.
■ A volume is unusable because of repeated media errors.
■ A volume is past its expiration date or has too many mounts, and you want
to replace it with a new volume.
■ A volume is lost and you want to remove it from the EMM database.
Media 533
Volume operations
After a volume is deleted, you can discard it or add it back under the same or a
Before you delete and reuse or discard a volume, ensure that it does not have any
safeguard against accidental deletion. You cannot delete such volumes if they
To delete volumes
1 In the NetBackup Administration Console, select Media and Device
Management > Media.
2 In the Volumes pane, select the volumes that you want to delete.
Note: You cannot delete any assigned volumes until any application
(NetBackup or Storage Migrator) using them deassigns them.
Note: If you selected only one side of an optical platter, the volume on other
side is also deleted.
Deassigning volumes
An assigned volume is one that is reserved for exclusive use by NetBackup or
Veritas Storage Migrator (but not both). A volume is set to the assigned state
when either applications first starts using it to store data. The time of the
assignment appears in the Time Assigned column for the volume in the Volumes
pane. When a volume is assigned, you cannot delete it or change its volume pool.
A volume remains assigned until NetBackup or Storage Migrator deassigns it.
NetBackup deassigns a volume only when the data is no longer required, as
follows:
■ For regular backup volumes, when the retention period has expired for all
the backups on the volume.
■ For catalog backup volumes, when when you stop using it for catalog
backups.
534 Media
Volume operations
backups on the volume expire. You can expire the backups on a volume by using
the bpexpdate command on the master server. After you expire a volume,
NetBackup deassigns it and does not track the backups that are on it. NetBackup
can reuse the volume, you can delete it, or you can change its volume pool.
If you expire the backup images on a volume, NetBackup does not erase those
images. You can still use the data on the volume by importing the backups into
You can expire backups regardless of the volume state (Frozen, Suspended, and
so on).
■ install_path\NetBackup\bin\admincmd (Windows)
■ /usr/openv/netbackup/bin/admincmd (UNIX)
The following is the format of the bpexpdate command:
bpexpdate -d 0 -m media id [-host hname]
media id is the media ID to be expired. hname is the name of the NetBackup
media server (or SAN media server) where the media ID was written. NetBackup
Enterprise Server only: specify hname only if your configuration uses master
servers and media servers.
The following example assumes only one NetBackup server exists and expires
all the backups on media ID ABC001:
bpexpdate -d 0 -m ABC001
Media 535
Volume operations
volumes.
can reuse the volume, you can delete it, or you can change its volume pool.
Exchanging volumes
You should exchange a volume (replace one volume with another volume) if a
volume meets any of the following conditions:
■ Full (in this case, to exchange a volume means to remove the volume from a
robotic tape library).
■ Past the maximum allowable number of mounts.
■ Old (past the expiration date).
■ Unusable (for example, because of repeated media errors).
The following are procedures for exchanging volumes, depending on whether
you want to reuse the old media ID or not.
in some instances.
Reuse a media ID only if all data on the old volume is not required and you
Caution: If you exchange a media ID for a volume that has unexpired backup
images, serious operational problems and a possible data loss may occur.
Recycling volumes
If you recycle a volume, you can use either the existing media ID or a new media
ID.
Caution: Recycle a volume only if all NetBackup data on the volume is no longer
needed or if the volume is damaged and unusable. Otherwise, you may
encounter serious operational problems and a possible loss of data.
To recycle a volume that contains unexpired backup images, you must deassign
the volume.
/usr/openv/volmgr/bin/vmchange -m media_id -n
number_of_mounts
8 Set the expiration date to the value you recorded in step 3.
See “Changing volume properties” on page 517.
Description
A brief description of the pool.
The default value is zero, which does not limit the number of full media that are
When the number of partially full media is reached, NetBackup queues backup
jobs until media becomes available. If a media becomes full, NetBackup assigns
another media for use if one is available in the pool or in a scratch pool.
Media 541
Volume pool operations
Frozen, suspended, and imported media do not count against Maximum number
of partially full media. Therefore, if you unfreeze or unsuspend the media that
are partially full, you may exceed the Maximum number of partially full media
value. Also, if you lower the Maximum number of partially full media value, you
may exceed the limit. If you exceed the Maximum number of partially full media
value, NetBackup uses all of the partially full media until the limit is reached.
This option lets you maximize your media usage. NetBackup writes data to the
media until they are full, assigns other media to which it writes data until they
are full, and so on.
This option also lets you control how many drives are used for backup jobs. For
example, if you have 10 drives and want to reserve two for restore operations,
set the Maximum number of partially full media to 8. If all of the media is in one
pool, NetBackup uses only 8 drives to write backup data. NetBackup can use the
two other drives for restore operations even while backups occur.
For more information about server groups, see “Configuring server groups for
media sharing” on page 615.
Pool name
The name for the new volume pool.
For information about the characters you can use in a name, see “NetBackup
Scratch pool
Select this option to use the pool as a scratch pool.
A scratch pool is a special volume pool from which NetBackup can transfer
volumes to another volume pool when that pool has no volumes available. When
the images on a volume expire, NetBackup returns it to the scratch volume pool
There can be only one scratch pool configured. You cannot add a scratch pool if
one exists.
pools.
Symantec recommends that you use a descriptive name for the pool name and
You should add sufficient type and quantity of media to the scratch pool to
service all scratch media requests that can occur. NetBackup requests scratch
media when media in your existing volume pools are allocated for use.
542 Media
5 After you move the volume group logically, physically move the volumes to
their new locations.
Destination
Displays the destination for the move:
■ If you move the volume group from a robotic library, Standalone is selected
as the destination.
■ If you move the volume group from stand-alone, Robot is selected as the
destination
Device host
NetBackup Enterprise Server only.
544 Media
Robot
The destination robotic library.
Volume group
The volume group to move.
Add new volumes to a robot (a new For any robot NetBackup supports, use the Update
Determine if volumes have been For robots with barcode readers and that contain
moved physically within a robot media with barcodes, use the Compare contents
with volume configuration option.
Determine the contents of a robot Use the Show contents option to determine the
media in a robot and possibly their barcode
numbers.
Determine whether new media Use the Preview volume configuration changes
have barcodes before you add option, which compares the contents of the robot
them to NetBackup with the NetBackup volume configuration
information.
After you examine the results, you can use the
Update volume configuration option to update the
volume configuration if necessary.
546 Media
Insert existing volumes into a If the robot supports barcodes and the volume has a
robot (an existing volume is one readable barcode, use the Update volume
that already has a NetBackup configuration option. NetBackup updates the
media ID) residence information to show the new robotic
location. NetBackup also updates the robot host,
robot type, robot number, and slot location. You
must specify the volume group to assign the volume
to.
If the robot does not support barcodes or the
volumes do not have readable barcodes, do one of
the following procedures:
■ “Moving volumes” on page 524
■ “Using the physical inventory utility” on
page 572
Move existing volumes between If the robotic library supports barcodes and the
robotic and stand-alone (an volume has a readable barcode, use the Update
existing volume is one that already volume configuration option. NetBackup updates
has a NetBackup media ID) the residence information to show the new robotic or
stand-alone location.
Move existing volumes from one If the robotic library supports barcodes and the
robot to another (an existing volume has a readable barcode, use the Update
volume is one that already has a volume configuration option. NetBackup updates
NetBackup media ID) the NetBackup volume configuration information.
If the robots do not support barcodes or the volumes
do not have readable barcodes, do one of the
following procedures:
■ “Moving volumes” on page 524
■ “Using the physical inventory utility” on
page 572
For either operation, you must perform two separate
updates:
■ First move the volumes to stand-alone
■ Then move the volumes to the new robot
If you do not do both updates, NetBackup cannot
update the entries and writes an “Update failed”
error.
See “Example 6: Moving existing volumes between
robots” on page 587.
Media 547
Robot inventory operations
Move existing volumes within a If the robot supports barcodes and the volume has a
robot (an existing volume is one readable barcode, use the Update volume
that already has a NetBackup configuration option. NetBackup updates the
media ID) residence information to show the new slot location.
If the robot does not support barcodes or the
volumes do not have readable barcodes, do one of
the following procedures:
■ “Moving volumes” on page 524
■ “Using the physical inventory utility” on
page 572
See Example 7: Adding existing volumes when
barcodes are not used.
Remove existing volumes from a For any robot NetBackup supports, use the Update
robot (an existing volume is one volume configuration option to update the
that already has a NetBackup NetBackup volume configuration information.
media ID)
Inventory a robot
The following are the robot inventory options you can select using the
NetBackup Administration Console:
■ Show contents. Displays the media in the selected robotic library; does not
check or change the EMM database.
■ Compare contents with volume configuration. Compares the contents of a
robotic library with the contents of the EMM database but does not change
the database.
■ Preview volume configuration changes. Compares the contents of a robotic
library with the contents of the EMM database. If differences exist,
NetBackup recommends changes to the NetBackup volume configuration.
■ Update volume configuration. Compares the contents of a robotic library
with the contents of the EMM database. If differences exist, NetBackup
updates the database to match the contents of the robot.
For examples of different volume configuration updates, see “Volume
configuration update examples” on page 579.
To inventory the robots without barcode readers or the media without readable
548 Media
To inventory a robot
1 In the NetBackup Administration Console, select Media and Device
Management > Media > Robots.
2 Select the robot you want to inventory.
3 Select Actions > Inventory Robot.
In the Robot Inventory dialog, Device host contains the name of the host
that controls the robot and Robot contains the selected robot.
4 Specify the options for the inventory.
For information about the options you can specify, see “Robot Inventory
dialog box” on page 548.
5 Click Start to begin the inventory.
Advanced options
Active if you select Update volume configuration or Preview volume configuration
changes.
Media 549
Robot inventory operations
Opens the Advanced Robot Inventory Options dialog, from which you can
For most configurations, the default settings work well. You should only change
If the robot can read barcodes, the barcodes on the media are compared to the
If the robotic library cannot read barcodes, the results show only whether a slot
contains a volume.
For API robots, the media ID and media type in the EMM database are compared
If the results show that the EMM database does not match the contents of the
Device host
The host that controls the robot.
550 Media
Robot inventory operations
begin the update, select Empty media access port prior to update.
The volumes to be injected must be in the media access port before the operation
begins. If you select Empty media access port prior to update and the MAP is
empty, you are not prompted to place volumes in the media access port.
Note: If you ejected volumes from the robot by using NetBackup, remove the
volumes from the media access port before you begin an inject operation.
Otherwise, if the inject port and eject port are the same, the ejected volumes may
be injected back into the robotic library.
Caution: If you preview the configuration changes first and then update the
EMM database, the update results may not match the results of the preview
operation. Possible causes may be changes that occur between the preview and
the update. Changes can be to the state of the robot, to the EMM database, to the
barcode rules, to the media type mappings, and so on.
Robot
The robot to inventory.
Show contents
Inventories the selected robotic library and generates a report; this operation
does not check or change the EMM database. Use this option to determine the
contents of a robot. The contents that are displayed depend on the robot type, as
follows:
Robot has a barcode reader and the Shows if each slot has media and lists the
robot contains media with barcodes. barcode for the media.
Robot does not have a barcode reader Shows if each slot has media.
barcodes.
Note: If a volume is mounted in a drive, the inventory report lists the slot that it
was in before it was moved to the drive.
For robots other than API robots that have a barcode reader, the results include
the barcode from each volume.
The following figure shows results for an ACS robot. The results for other API
552 Media
ACS robots
NetBackup Enterprise Server topic.
The results, received from ACS library software, shows:
■ The ACS library software volume ID. The NetBackup media ID corresponds
to the ACS library software volume ID.
■ The ACS media type.
■ The NetBackup Media Manager media type.
■ The mapping between the ACS library software media type and the
corresponding NetBackup Media Manager media type (without considering
optional barcode rules).
TLH robots
NetBackup Enterprise Server topic.
The results, received from the Automated Tape Library (ATL) library manager,
show:
■ The volume serial number (volser). The Media Manager media ID
corresponds to the ATL volser.
■ The ATL media type.
■ The Media Manager media type.
■ The mapping between the ATL media type and the corresponding Media
Manager media type (without considering optional barcode rules).
TLM robots
NetBackup Enterprise Server topic.
Media 553
Robot inventory operations
Note: You can select a device host only with NetBackup Enterprise Server.
The following figure shows example results for an ACS robot. Results for other
API robots are similar to this report.
Assign media settings for new and existing See “Media Settings tab” on page 555.
media.
Create media ID generation rules. See “Media ID Generation tab” on page 565.
Map media for API robots. If you do not See “Media Type Mappings tab” on
map media, default media types are used. page 566.
Media type
Media type is always set to DEFAULT for API robots. For instructions for specifying
media types for API robots, see “Media Type Mappings tab” on page 566.
Specifies the type for new media that are added to a robot. The list includes the
media types that are valid for the robot.
The following table shows the default media types for robots when drives are
not configured on the robot control host:
Table 9-2 Default media types for non-API robots
Note: If you choose DEFAULT on the Media Settings tab and DEFAULT in the
barcode rule, NetBackup assigns the default media type for the robot.
■ To use a media type other than the default, select a specific media type from
the list.
You can use one barcode rule to add media of different types, such as DLT
and half-inch cartridges (HCART) to a TLD robot. First, select a specific
media type on the Media Settings tab. Second, select DEFAULT for the
barcode rule media type when you create the barcode rule. You can perform
one update for DLT and another for half-inch cartridge, and the one barcode
rule assigns the correct media type.
If you specify any value other than DEFAULT on the Media Settings tab, the
barcode rule media type must be the same as the media or be DEFAULT. If
not, the barcode rule does not match the media (except for cleaning media).
The following table shows some example combinations of media types on
the Media Settings tab and barcode rule media types for a TLD (non-API)
robot and the results when the media are added to the volume
configuration:
The fourth row in the table shows how both cleaning cartridges and regular
volumes are added using one update operation. The following conditions all
must be true:
■ The media type on the Media Settings tab is for regular media (DLT, in
this example).
■ The barcode matches a barcode tag.
■ The media type for the barcode rule is cleaning media (DLT_CLN).
For another example, see “Example 5: Adding cleaning tapes to a robot” on
page 586.
The sixth row and seventh row in the table show how to add only a cleaning
tape. In the sixth row, you specify the cleaning media type on the Media
Settings tab and in the barcode rule. In the seventh, you specify the
cleaning media on the Media Settings tab and specify default when you
configure the barcode rule.
For more information about barcode rules, see “Barcode Rules tab” on page 562.
robot.
Tip: If the robotic library contains multiple media types, Symantec recommends
a DEFAULT setting. If you specify a volume group and volumes of different
media types have been moved into or within the robot, the new update fails:
volumes of different media types cannot have the same volume group.
For more information about media types, see “Media type” on page 556.
For more information about barcode rules, see “Barcode Rules tab” on page 562.
You should specify a Media ID prefix for any new media if either of the following
conditions exist:
Volume pool
Specifies the volume pool for the new media. The actions depend on whether
Barcode tag
The barcode tag is a unique string of characters from the barcode that identifies
the type of media. For example, you can use DLT as the barcode tag for a barcode
rule if:
■ You use DLT on your barcodes to identify DLT tapes
■ DLT is not used on any other barcodes in the robot
Similarly, if you use CLND for DLT cleaning media, you can use CLND as the
barcode tag for the rule for DLT cleaning media.
Media 563
Robot inventory operations
The barcode tag can have from 1 to 16 characters but cannot contain any spaces.
The following are special barcode rules that can match special characters in the
barcode tags:
■ NONE. Matches when rules are used and the volume has an unreadable
barcode or the robot does not support barcodes.
■ DEFAULT. For volumes with barcodes, this tag matches when none of the
other barcode tags match. However, the following must be compatible: the
media type in the DEFAULT rule and the media type on the Media Settings
tab.
You cannot change the barcode tag of a barcode rule. You must first delete the
old rule and then add a rule with a new barcode tag.
Use the Media Settings tab to set up the criteria for a robot update.
Description
A description of the barcode rule. You can enter from 1 to 25 characters.
Maximum mounts
The maximum number of mounts (or cleanings) that are allowed for the volume.
For data volumes, a value of 0 means the volume can be mounted an unlimited
number of times.
For cleaning tapes, 0 means the cleaning tape is not used. To avoid a value of 0
for cleaning tapes, use barcodes for your cleaning media that cannot be
confused with barcodes for data media.
Media type
The media type to assign to the media.
The media type that is specified on the Media Settings tab always overrides the
media type of the barcode rule. If you specify any value other than DEFAULT on
the Media Settings tab, the barcode rule media type must be the same as the
media or be DEFAULT. If not, the barcode rule does not match the media (except
for cleaning media).
For more information, see “Specifying media type when using barcode rules” on
page 557.
564 Media
Robot inventory operations
Note: When a media type is selected, the maximum mounts value may revert to
the default value for the specified media type. For example, it may revert to 0 for
unlimited when you select a non-cleaning media type.
If you specify DEFAULT, NetBackup uses the media type you select on the Media
Type Mappings tab. If you do not specify a media type on the Media Type
Mappings tab, NetBackup uses the default media type for the robot.
To enable barcode rule support for API robots, you must add an
Note: If a barcode rule contains media types that are incompatible with vendor
media types, the robot inventory update may add media with media types
inconsistent with the vendor media types. Avoid this problem by grouping
barcode rules by media type.
with the media type you select on the Media Settings tab.
Select the media type for non-API robots as explained in the following table:
If you want the media type Select the following Media type NetBackup
for the barcode rule to media type for the uses
match barcode rule
Any media type that you select DEFAULT The media type that you
on the Media Settings tab select on the Media Settings
tab.
If you also select DEFAULT on
the Media Settings tab, the
Media Manager default media
type for the robot is used.
Only when you select a The same media type The media type that you
specific media type or you select for the barcode rule.
select DEFAULT on the Media
Settings tab
Media 565
Robot inventory operations
Volume pool
Specifies the volume pool for the new media.
If you use a barcode rule and the Media Settings tab Volume pool field is set to:
■ DEFAULT, the volume is assigned to the pool you specify in this Volume pool
setting.
■ A specific volume pool, the Volume pool setting on the Media Settings tab
overrides this Volume pool setting.
Barcode length
The number of characters in the barcode for tapes in the robot.
Robot number
The number of the robot to which the rule applies.
mapping entries for that robot type and media type, NetBackup uses the default
media types and any mappings on the Media Type Mappings tab.
ACS_DLTIV = DLT2 Maps ACS DLTIV to the DLT for all ACS DLT media types,
DLT2 media type. including DLTIV
ACS_DD3A = HCART4
Table 9-3 Default and allowable media types for ACS robots
ACS media type Default Media Manager media Allowable media types
type through mappings
Table 9-3 Default and allowable media types for ACS robots (continued)
ACS media type Default Media Manager media Allowable media types
type through mappings
Table 9-3 Default and allowable media types for ACS robots (continued)
ACS media type Default Media Manager media Allowable media types
type through mappings
Table 9-4 Default and allowable media types for TLH robots
TLH media type Default Media Manager media Allowable media types
type through mappings
Table 9-4 Default and allowable media types for TLH robots (continued)
TLH media type Default Media Manager media Allowable media types
type through mappings
Table 9-5 Default and allowable media types for TLM robots
TLM media type Default Media Manager media Allowable media types
type through mappings
Table 9-5 Default and allowable media types for TLM robots (continued)
TLM media type Default Media Manager media Allowable media types
type through mappings
Note: The following TLM media types are not supported: OD_THIN, D2, VHS, CD,
TRAVAN, BETACAM, AUDIO_TAPE, BETACAMCL, DVCM, and DVCL.
Note: API robots: If a barcode rule contains media types that are incompatible
with vendor media types, the robot inventory update may add media with media
types inconsistent with the vendor media types. Avoid this problem by grouping
barcode rules by media type.
Features of vmphyinv
The vmphyinv utility has the following features:
■ Can be invoked from any master server, media server, or SAN media server.
■ Can be used with barcoded tape libraries because it verifies the contents of
the media.
■ Recognizes NetBackup, Backup Exec, and Veritas Storage Migrator (VSM)
tape formats.
■ Supports remote administration. You do not need to invoke vmphyinv from
the host to which the drives are attached.
■ Tries to use multiple drives in a robot even if the drives are attached to
different hosts.
■ Works with shared drives (NetBackup Shared Storage Option).
■ Supports all SCSI-based robot types (except optical disk libraries).
■ Can be used to inventory a single media in a stand-alone drive. Use the -u or
-n option to specify the drive; the drive must contain media and it must be
ready.
■ You insert some media that have unknown media IDs or globally unique
identifiers (GUIDs) into a robot.
For example, you insert 10 media from a different tape library in slots 11 to
20. You do not know the IDs on the tapes. Use the slot range or list option of
vmphyinv to perform the inventory operation. vmphyinv mounts the
media, reads the tape header, determines the media ID, and adds media
records to the EMM database.
■ Some of the media are misplaced and the EMM database does not reflect the
correct physical location of these media. You can inventory the robot or
inventory a subset of media in the robot by using options in vmphyinv.
range. To use these options, NetBackup volume records must exist. The
following are some examples:
-rn 4 -pn bear Only media in robot 4 and in the volume pool
bear.
-rn 5 -pn NetBackup -v mars -rc1 2 Only media in robot 5, slot range 2 to 7, in
-number 6 volume group mars, and in the NetBackup
volume pool.
■ NetBackup robot number and a list of media that belong to a specific robot.
For example, if the -rn robot_number and -ml A00001:A00002:A00003
options are specified, only the three specified media are inventoried. If any
of these media do not belong to the specified robot, the media are skipped
and are not inventoried.
To use this option, NetBackup volume records must exist.
■ NetBackup robot number and a slot range or list. Sometimes, media from a
different robot or some other source are moved to a robot and the media ID
on the tape is unknown. In these cases, you can specify a slot range option or
list option.
With these options, the NetBackup volume record does not need to exist in
the EMM database. However, you must specify the density (using the -d
option).
Note: For a robot that supports multiple media types, you should specify the
density carefully. If you specify the incorrect density, vmphyinv cannot
complete the mount and permanent drive failure can occur.
Note: The default mount timeout is 15 minutes. You can specify a different
mount time by using the -mount_timeout option.
Cleaning media
If the following conditions are all true, vmphyinv does not attempt to mount the
media. The next media in the list is mounted.
■ You do not specify the vmphyinv slot range or list option.
■ The robot contains cleaning media.
■ The media type is specified as cleaning media in the volume record (such as
4mm_clean or dlt_clean).
If the robot contains cleaning media and any of the following conditions are
true, vmphyinv tries to determine if the media is cleaning media:
■ You use the slot range or list option and the media type of volume record in
the EMM database is not a cleaning media type.
■ You use the slot range or list option, and the EMM database does not
contains a volume record that corresponds to the cleaning media.
■ You do not used the slot range or list option, and the EMM database does not
contains a volume record that corresponds to the cleaning media.
Media 577
Robot inventory operations
The vmphyinv utility tries to determine if the media is cleaning media. It uses
the SCSI parameters (sense keys, tape alert flags, and physical (SCSI) media
types) returned by the robot. If vmphyinv cannot determine if the media is
cleaning media, it tries to mount the media until the mount request times out.
Note: NetBackup may not detect the presence of cleaning media for all drives.
Some drives report the presence of cleaning media in a manner NetBackup
cannot read.
Update criteria
For valid media types, vmphyinv:
■ Changes the residence fields and description fields of any NetBackup media
record if those fields do not match the media header. The description field is
changed only if the media is Symantec Backup Exec or Veritas Storage
Migrator media.
■ Conditionally changes the media type of an unassigned NetBackup volume
record. The media type is changed only if the new media type belongs to the
same family of media types as the old media type. For example, the media
type DLT can only be changed to DLT2 or DLT3.
■ Never changes the volume pool, media type, and ADAMM_GUID of an
assigned record.
■ Never unassigns an assigned NetBackup volume.
578 Media
Robot inventory operations
■ In the NetBackup record, updates the ADAMM_GUID field with the GUID.
Also updates the Description field with the Veritas Storage Migrator
cartridge label in the tape header.
■ Changes the volume pool of the unassigned NetBackup records that are
associated with Veritas Storage Migrator media to the StorageMigrator pool.
If the StorageMigrator pool does not exist, it is created.
Error cases
The vmphyinv utility may not be able to update the EMM database correctly in
the following cases. These cases are reported as errors. If any of the following
cases are encountered, you must intervene to continue.
■ Duplicate media IDs are found. Two or more media in the same robot have
the same media ID.
■ A NetBackup volume record that belongs to a different robot is found. It
contains the same media ID as the media ID read from the tape header.
■ The media type, media GUID, or volume pool of an assigned volume record
needs to be changed.
■ The barcode of an existing volume record needs to be changed.
media ID 800001
barcode TL800001
2 Assume that you remove the volume from the robotic library, specify the
following on the Media Settings tab, and then execute the update.
media ID 800001
barcode TL800001
location in the volume group. The volume group is specified on the Media
Settings tab. The media type and volume pool remain unchanged.
The results are the same for a volume that does not have a barcode.
Note: When you move volumes from one robot to another robot, you must do
two separate updates. For procedures, see “Example 6: Moving existing volumes
between robots” on page 587.
1 The following are the volume attributes for media ID 800021, which has a
readable barcode and already exists as a stand-alone volume.
media ID 800021
barcode TL800021
2 Assume that you insert the volume into a TL8 robot, specify the following on
the Media Settings tab, and then execute the update.
582 Media
3 NetBackup recognizes that the media ID exists and changes the EMM
database to reflect the new robotic location; NetBackup does not create a
new media ID. The volume attributes for media ID 800021 are as follows:
media ID 800021
barcode TL800021
robot number 0
robot slot 1
The only setting used on the Media Settings tab is the volume group for
added or moved volumes. The media type setting was not used because this
example was for a single existing volume that already had a media type.
1 The following are the attributes for media ID 800002, which currently
resides in slot 1 of the robotic library.
media ID 800002
barcode TL800002
robot number 0
robot slot 1
2 Assume that you move the volume to empty slot 10, specify the following on
the Media Settings tab, and then execute the update.
584 Media
media ID 800002
barcode TL800002
robot number 0
robot slot 10
The updated volume attributes show the new slot number, but all other
information is unchanged.
2 The barcode on the media matches the barcode rule named TL8 and the
resulting volume attributes for the new volume are as follows:
Media ID 800002
Barcode TL800002
Robot number 0
Robot slot 1
No media ID generation rules exist. Therefore, the media ID is from the last
six characters of the barcode. The new residence information in the EMM
database shows the robot host, robot type, robot number, slot, and host. The
volume group is from the Media Settings tab. The volume pool and max
mounts allowed are from the barcode rule.
If barcode rules (or barcodes) had not been used, the media description,
volume pool, and max mounts allowed would be set to the following
defaults:
586 Media
Note: If the robot does not support barcodes or the barcode is unreadable, you
must specify a Media ID prefix on the Media Settings tab. Alternatively, you can
specify DEFAULT for the media ID. If you do not, NetBackup does not add new
media IDs.
2 You specify the following on the Media Settings tab and then execute the
update.
3 The barcodes on the regular tapes match the DL barcode rule. The media
type of the DL barcode rule matches the Media type on the Media Settings
tab. The tapes are added as DLT.
The cleaning tape matches the CLN barcode rule. NetBackup recognizes
that DLT_CLN is the cleaning tape for DLT. NetBackup adds the cleaning
tape CLN001 as DLT_CLN type media along with the regular volumes.
This example shows NetBackup’s ability to add cleaning cartridges along
with regular volumes when you use Update volume configuration.
Media 587
Robot inventory operations
If the volumes you insert include a cleaning tape, NetBackup adds the
volumes correctly if the following are true:
■ The Media type on the Media Settings tab is the regular media (DLT in
this example).
■ The barcode on the volume matches a barcode tag (CLN in this
example).
■ The media type for the barcode rule is the correct cleaning media
(DLT_CLN in this example).
To add only cleaning media, specify the cleaning media type on the Media
Settings tab and in the barcode rule (DLT_CLN in this example).
Caution: This procedure assumes that robot 2 is able to read barcodes and the
volume has readable barcodes. If not, the problem in “Example 7: Adding
existing volumes when barcodes are not used” on page 587 occurs.
Caution: This example is not recommended and is included only to illustrate the
undesirable results.
1 The following are the attributes for media ID 400021, which already exists
as a stand-alone volume.
media ID 400021
barcode -----------
2 Assume that you insert the volume into the robot, specify the following on
the Media Settings tab, and then execute the update.
media ID prefix C4
media ID C40000
barcode -----------
robot number 0
robot slot 1
Note that NetBackup assigned a new media ID to the volume (C40000). This
undesired result occurs if you use Update volume configuration and the
volumes do not have readable barcodes or the robot does not support
barcodes. Without a barcode, NetBackup cannot identify the volume and
assumes it is new. The media ID C40000 is generated from the media ID
prefix specified on the Media Settings tab.
The old media ID (400021) remains in the configuration. The information
for the new media ID (C40000) shows the robotic location, which includes
the robot host, robot type, number, slot, and host. The volume group and
volume pool are configured according to the Media Settings tab selections.
The maximum mounts allowed is set to the default (0).
For this situation, you should use the physical inventory utility.
See Using the physical inventory utility.
The NetBackup QIC/WORM tape format is used for WORM media. This format
allows NetBackup to append images to WORM tape as can be done with standard
tape.
NetBackup queries the drive to verify that drive is WORM-capable and that the
media in the drive is WORM media. NetBackup uses SCSI commands to query
drives.
Tape error recovery is disabled when using WORM media. NetBackup has job
resume logic, which tries to resume a job that has been interrupted (for example,
an interruption on the fibre channel). However, NetBackup fails a job that uses
WORM media and then retries the failed job. Symantec recommends that you
The bplabel command labels only LTO-3 WORM tapes. All other WORM media
cannot be labeled because the label cannot be overwritten when the media is
used.
590 Media
Supported drives
For information about the drives that NetBackup supports for WORM media, see
the NetBackup Hardware Compatibility List on the Symantec support Web site:
http://entsupport.symantec.com
All of the vendors, except Quantum, require the use of special WORM media.
Quantum lets NetBackup convert standard tape media to WORM media. To use
Quantum drives for WORM media on Solaris systems, you must modify the
st.conf file. For information about how to configure nonstandard tape drives
and how to edit the st.conf file, see the NetBackup Device Configuration Guide.
WORM-capable tape drive to back up and restore standard and WORM media.
Create a new volume pool and specify WORM (upper-case letters) as the first
NetBackup compares the first four characters of the volume pool name to
determine if it is a volume pool that contains WORM media. The first four
To disable the volume pool name verification, create the following touch file on
/usr/openv/netbackup/db/config/DISABLE_WORM_POOLCHECK
■ If the drive contains Quantum media that has never been used or has had all
of its NetBackup images expired, NetBackup uses the media.
WORM-capable drives cannot be used for backups with standard media even if
no WORM backups are in progress.
If you do not use WORM volume pools to manage WORM media, you should
disable the WORM volume pool name verification. To disable the volume pool
name verification, create the following touch file on the media server of the
WORM drive:
/usr/openv/netbackup/db/config/DISABLE_WORM_POOLCHECK
For more information about configuring and managing storage devices, see the
following:
■ The storage devices must be attached to the system and recognized by the
operating system before you begin NetBackup device configuration. The
server platforms that NetBackup supports may require operating system
configuration changes to allow device discovery. The NetBackup Device
Configuration Guide provides information about how to configure device
drivers for the systems that support NetBackup server software.
■ If the host on which you configure devices is not the Enterprise Media
Manager server, add it to the NetBackup additional servers list.
NetBackup hosts are added automatically to the list of additional servers if
the EMM server is running when the host is installed. If the EMM server was
not running, use the nbemmcmd -addhost command to add the host.
Note: The contents of this file do not indicate support for any of the devices,
only the ability to recognize and automatically configure them.
The files that you download are named similarly to the following files:
Mappings_6_nnnnnn.TAR and Mappings_6_nnnnnn.ZIP.
2 Download the latest external types file to the following location on the
system that hosts the EMM server:
■ /usr/openv/var/global (UNIX)
■ install_path\netbackup\var\global (Windows)
3 Use the tpext command to update the EMM database with the new version
of the device mapping file; no command-line parameters are required. The
tpext command resides in the following directory:
Devices 595
Configuring robots and tape drives
■ /usr/openv/volmgr/bin (UNIX)
■ install_path\volmgr\bin (Windows)
4 Stop and restart the Media Manager Device daemon.
For procedures, see “Stopping and restarting the device daemon” on
page 539.
Guide.
Caution: The Device Configuration Wizard stops and starts the daemons and
services. Therefore, ensure that backups are not active when you use the wizard.
Symantec recommends that you use the Device Configuration Wizard to add and
configure the following types of devices:
■ Robots, including those attached to NDMP hosts
■ Drives, including those attached to NDMP hosts
■ Shared drives (for NetBackup Shared Storage Option configurations only)
■ Storage servers that control disk storage
596 Devices
Configuring robots and tape drives
This wizard uses device discovery to add and configure devices automatically.
This wizard also uses the device mapping file during device discovery and
configuration.
In some cases, the wizard may leave some devices partially configured.
library or drive. If you deselect a discovered device from the tree view in the
For NetBackup 5.x device hosts, partially-configured drives are shown as PCD
If you have partially-configured drives, ensure that you have downloaded the
most recent device mapping file from the Symantec support Web site.
Devices 597
Configuring robots and tape drives
Be sure to review the limitations of the wizard before you configure devices.
Adding a robot
Note: Symantec recommends that you use the Device Configuration Wizard to
add storage devices. For more information, see “Using the Device Configuration
Wizard” on page 595.
Use the following procedures to add a robot manually. When you add a robot
and drives, first add the robot as explained in the following procedure and then
add the drives.
To add a drive, see “Adding or changing a drive” on page 604.
To add a robot
1 In the NetBackup Administration Console, select Media and Device
Management > Devices.
2 Select Actions > New > Robot.
3 In the Add a New Robot dialog, specify the properties for the robot.
The properties you can configure depend on robot type, host type, and robot
controls selections you make in the dialog.
For descriptions of the properties, see “Robot properties” on page 598.
598 Devices
Configuring robots and tape drives
Robot properties
The following sections describe the robot properties you can configure. The
properties you can configure depend on robot type, host type, and robot control
selections you make in the dialog.
ACSLS host
ACSLS Host applies only to NetBackup Enterprise Server.
Specify the name of the Sun StorageTek ACSLS host; the ACS library software
resides ACSLS host. On some UNIX server platforms, this host can also be a
Note: STK LibAttach software must also be installed, if the device host that has
drives under ACS robotic control is a Windows server. Obtain the appropriate
LibAttach software from STK. See the Symantec support Web site for the latest
compatibility information.
For an overview of ACS robots, see the NetBackup Device Configuration Guide.
DAS server
NetBackup Enterprise Server only.
To specify the DAS server for TLM robots that are controlled by an ADIC
For an overview of TLM robots, see the NetBackup Device Configuration Guide.
Device host
Device Host applies only to NetBackup Enterprise Server.
Specifies the host to which the device is attached.
Library name
TLH robot on NetBackup Enterprise Server only.
For UNIX device hosts (except AIX), enter the library name that is configured on
For an overview of TLH robots, see the NetBackup Device Configuration Guide.
To specify the robot control host for TL8, TLD, or TLH robots, enter the name of
For more information about robot control, see “Robot control configuration
For this type of robot control, you specify the following items:
Specifies that a host other than the device host controls the robot.
For this type of robot control, you can configure the following attributes (based
on the robot type and device host platform that you selected):
Robot device
Windows device host only.
To specify the robot device, click Browse and then select a robot from the list
that appears in the Devices dialog.
Devices 601
Configuring robots and tape drives
If the browse operation does not find attached robots, an error dialog appears.
To specify the robotic device file, click Browse and then select a robotic device
If the browse operation fails to show all of the attached robots, click More. Enter
the path of the device file in the robotic device file field.
For information about how to add device files, see the NetBackup Device
Configuration Guide.
For this type of robot control, configure the following fields (depending on the
Robot number
Specifies a unique, logical identification number for the robotic library. This
number identifies the robotic library in displays (for example, TLD (21)) and is
also used when you add media for the robot.
For NetBackup Enterprise Server environments:
■ Robot numbers must be unique for all robots on all hosts in the
configuration, regardless of the robot type or the host that controls them.
For example, if you have two robots, use different robot numbers even if
different hosts control them.
■ If you add a robot that is controlled by a remote device host, use the same
robot number for that robot on all device hosts.
■ If the robot has its robotic control and drives on different hosts, specify the
same robot number in all references to that library. That is, use the same
602 Devices
Configuring robots and tape drives
robot number on the hosts with the drives as you do on the host that has the
robotic control. A Tape Library DLT robot is one that allows separate robotic
Robot type
Specifies the type of robot. To locate the robot type to use for specific vendors
and models, see the Symantec support Web site:
http://entsupport.symantec.com
operation.
To specify the SCSI coordinates, enter the Port, Bus, Target, and LUN for the
robotic device.
Local ODL AIX, Solaris SPARC and HP-UX Robotic device file
(except HPIA64),
NDMP ACS, TL8, TLD, Windows, AIX, Solaris SPARC, NDMP host name
and TLH HP-UX (except HP IA64), and and robot device
Linux (except Linux64)
TL8
Robotic Drive 1 Drive 2
Control
Control
eel shark
EMM
Database
Note: Symantec recommends that you use the Device Configuration Wizard to
add storage devices. For more information, see “Using the Device Configuration
Wizard” on page 595.
Use the following procedures to add or change a tape or optical drive manually.
To add a drive
1 In the NetBackup Administration Console, select Media and Device
Management > Devices.
2 Select one of the following, depending on the type of drive:
■ Actions > New > Tape Drive
■ Actions > New > Optical Drive
3 Specify the properties of the drive.
The properties depend on the drive type and host server type.
For descriptions of the properties, see “Drive properties” on page 607.
To change a drive
1 In the NetBackup Administration Console, expand Media and Device
Management > Devices > Drives.
Devices 605
Configuring robots and tape drives
2 In the details pane, right-click on the drive you want to change and select
Change from the shortcut menu.
3 In the Change Drive or Change Optical Drive dialog box, change the
properties of the drive .
The properties depend on the drive type and host server type.
For descriptions of the properties, see “Drive properties” on page 607.
For information about the NetBackup Shared Storage Option, see the NetBackup
For each drive path, you can override the media server setting. The following are
the options for the Override SCSI Reserve settings drive path attribute:
■ Server Default. Use the SCSI reserve protection setting configured for the
media server.
■ SPC-2 SCSI Reserve. This option provides SCSI reserve and release
protection for SCSI devices that conform to the reserve and release
management method that is defined the SCSI Primary Commands - 2
(SPC-2) standard.
■ SCSI Persistent Reserve. This option provides SCSI persistent reserve in and
persistent reserve out protection for SCSI devices that conform to the SCSI
Primary Commands - 3 (SPC-3) standard.
Drive properties
You specify properties when you add a drive or change the properties of a drive.
The properties you can specify depend on drive type, server platforms, or
NetBackup server types.
Cleaning frequency
Applies to tape drive only.
NetBackup does not support drive cleaning in some robot types. For more
If you want to set up a frequency-based cleaning schedule for the drive, set the
number of mount hours between each drive cleaning. When you add a drive or
reset the mount time to zero, NetBackup records the amount of time that
volumes have been mounted in that drive. The default frequency is zero.
When the accumulated mount time exceeds the time you specify for cleaning
frequency, drive cleaning occurs:
■ If the drive is in a robotic library that supports drive cleaning
■ If a cleaning cartridge is defined in that robotic library
608 Devices
Configuring robots and tape drives
Data/device path
Optical drives on UNIX servers only.
The path to the device file for the optical drive.
Device files are in the /dev directory on the UNIX host. If the entries do not
If you use NDMP drives, see the NetBackup for NDMP Administrator’s Guide for
configuration information.
For more information about device paths, see “No rewind device” on page 614.
Device host
Optical drive only.
Drive status
Applies to tape drive only.
When you add a drive, the default drive status is UP, which means the drive is
available. When a drive is UP, the default mode is AVR (Automatic Volume
Recognition). Exception: optical drives on an HP9000-800 systems are in OPR
(operator control) mode when they are UP.
Devices 609
Configuring robots and tape drives
You can also change the drive status using the commands on the Actions menu
in Device Monitor.
If you select this option, you must configure the Robotic library and Robot drive
number fields.
Drive name
The name that identifies the drive. Each drive name must be unique. Descriptive
Enter a name for the drive. Alternatively, use drive name rules to create a
For information about how to configure rules for naming drives, see
For information about the characters you can use in a name, see “NetBackup
Drive type
Tape drive only.
Specifies the type of drive.
If the drive writes WORM media, see “Using WORM media” on page 589 for
more information.
3 In the Change Path dialog box, configure the properties for the drive path.
The properties you can change depend on drive type, server platform, or
NetBackup server type.
For more information about device paths, see “No rewind device” on page 614.
To configure SCSI reserve, see “Configuring SCSI reserve on a drive path” on
page 605.
Note: Robot drive number does not apply when you add drives to API robots. See
“Robot drive number for API robots” on page 613.
Specifies the physical location in the robot of the drive. When you add more
than one drive to a robot, you can add the physical drives in any order. For
example, you can add drive 2 before drive 1.
The correct robot drive number is critical to the proper mounting and utilization
of media. You must determine which logical device name (Windows) or the
device file (UNIX) identifies which physical drive in the robot. You should
correlate the drive serial number with drive serial number information from the
robot.
See “Correlating device files to physical drives when adding drives” in the
NetBackup Administrator’s Guide for UNIX and Linux, Volume II
NetBackup does not detect incorrect drive number assignment during
configuration; however, an error occurs when NetBackup tries to mount media
on the drive.
Robotic library
The robot that controls the drive.
This dialog allows you to select any configured robot that can control the drive.
Serial number
This read-only field shows the serial number of the drive.
To configure drive name rules, click Configure. For information about how to
configure rules for naming drives, see “Configuring drive name rules” on
page 611.
Devices 611
Configuring robots and tape drives
Enter the path to the volume header device file on the specified host.
Volume header device files are in the /dev directory on the UNIX host. If the
Configuration Guide.
If you use the default global rule when you add Quantum DLT8000 drives, the
first one that you add is named QUANTUM.DLT8000.000, the second one
You can update the global drive name rule. You can create local drive name rules
for specific device hosts (each device host can have its own rule). Local rules
override the global rule for the devices that are attached to the specified host.
Only one global rule can exist; it is used for all connected device hosts. The
global rule is used for the drive name unless a host-specific rule or local rule is
specified.
Drive names are limited to 48 characters. Use any of the following drive
■ Host name
■ Robot number
■ Robot type
■ Drive position
Drive position information varies depending on the robot type. Drive
position information can be ACS coordinates, TLM/TLH vendor drive name,
or the robot drive number.
■ Drive type
■ Serial number
612 Devices
■ Vendor ID
■ Product ID
■ Index
A Custom Text field is also available which accepts any of the allowable drive
name characters.
For information about the characters you can use in a name, see “NetBackup
naming conventions” on page 631.
Note: If you use <host name> in the rule and the drive is a shared drive, the
name of the first host that discovers the drive is used as the host name. The
name for a shared drive must be identical on all servers that share the drive.
Robot drive number does not apply when you add drives to the following types
of API robots:
■ ACS robots (Automated Cartridge System). See “ACS” on page 614 for more
information.
■ TLH robots (Tape Library Half-inch). See “TLH” on page 614 for more
information.
■ TLM robots (Tape Library Multimedia). See “TLM” on page 614 for more
information.
614 Devices
Configuring robots and tape drives
ACS
For Enter
ACS Number The index (in ACS library software terms) that identifies the robot
that has this drive.
LSM Number The Library Storage Module that has this drive.
Drive Number The physical number of the drive (in ACS library software terms).
TLH
TLM
No rewind device
UNIX servers only.
Although both rewind and no rewind on close device files are usually available,
versions of UNIX, the device file name may be preceded or followed by the letter
n.
Device files are in the /dev directory on the UNIX host. If the entries do not
exist, create them as explained in the NetBackup Device Configuration Guide.
Devices 615
Configuring server groups for media sharing
Note: The access control feature of Sun StorageTeck ACSLS controlled robots is
not compatible with media sharing. Media sharing restricts volume access by
the requesting hosts IP address. Use caution when you implement media
sharing in an ACSLS environment.
You can configure server groups that can share media. A server group is a group
of NetBackup servers that are used for a common purpose. A media sharing
group is a server group that shares media for write purposes. A media sharing
group can contain the following:
■ NetBackup master server
■ NetBackup media servers
■ NDMP tape servers
■ Virtual host names of NetBackup media servers in a cluster
Servers can be in more than one group. All members of a server group must have
the same NetBackup master server. Only NetBackup 6.5 and later systems can be
in server groups.
For a media sharing group, select Media Sharing. A media sharing group is a
server group that shares media for write purposes. A media sharing group can
State
The state of the server group:
■ Active. The server group is available for use.
■ Inactive. The server group is not available for use.
To change the state, select the new state from the dropdown box.
Description
A description of the media server group.
Servers in group
The servers (and their type) that belong to the group.
To remove a server from the group, select it in the Servers in Group window and
click Remove.
To add a server to the group, select it in the Servers Not in Group window and
click Add.
storage.
You can configure disk pools if you install an Enterprise Disk Option license key.
complete and you are not in a production environment, answer yes to the stop
and restart prompt.
Caution: If you stop and restart ltid, any backups, archives, or restores also are
stopped.
configured drive.
To configure and use a shared drive, a Shared Storage Option license is required
Deleting robots
Note: Any drives that are configured as residing in a robot that you delete are
changed to stand-alone drives. Any media in the deleted robot is also moved to
stand-alone.
To delete a robot
1 In the NetBackup Administration Console, select Media and Device
Management > Devices.
2 Select Robots in the tree pane.
3 Select the robotic library you want to delete from the Robots pane.
4 Select Edit > Delete.
5 Answer the delete confirmation dialog.
Deleting drives
To delete a drive
1 In the NetBackup Administration Console, select Media and Device
Management > Devices.
622 Devices
Managing your device configuration
Ensure that the library to be tested is properly configured for use with
NetBackup. Testing is conducted using the existing NetBackup robotic control
daemons or processes.
Note: The tpconfig -d or -l option may truncate drive names. Use tpconfig
-dl to obtain the full drive name.
624 Devices
Stopping and restarting the device daemon
Caution: If you stop and restart the device daemon, any backups, archives, or
restores that are in progress fail.
To use UNIX commands on a drive, the drive must be down and ltid must not be
running.
No SERVER entries A host can mange media and devices on the remote host if it
is is added to the bp.conf file of the server you logged into.
You do not need to add a SERVER entry to the vm.conf file.
Any SERVER entries You must add a SERVER entry for the host on which the
NetBackup Administration Console is running (the server
you logged into).
626 Devices
The Enterprise Media Manager server
SERVER = shark
■ The vm.conf file on yak contains the following, which allows yak to
manage its own devices and permits shark to access them:
SERVER = yak
SERVER = shark
2 Select Actions > Enterprise Media Manager Database > Remove Device
Host.
Note: Beginning with release 6.0, NetBackup allocates drives before it starts jobs
on a media server. Therefore, NetBackup 6.0 and later may pre-empt drive
selections on NetBackup 5.x media servers. To optimize resource allocation in
your environment, you should update all media servers to release 6.0 or later.
Chapter 11
Credentials
Credentials appears only if a feature that requires external credentials is
licensed.
Use Media and Device Management > Credentials to add, remove, and manage
■ Disk array hosts. For disk array host credentials, see the SharedDisk section
of the NetBackup Shared Storage Guide.
■ NDMP hosts. For NDMP host credentials, see the NetBackup for NDMP
Administrator’s Guide.
■ Storage servers. For OpenStorage server credentials, see the OpenStorage
section of the NetBackup Shared Storage Guide.
630
Credentials
Chapter 12
Management topics
This chapter contains the topics that are related to the administration and
management of NetBackup.
■ “NetBackup naming conventions” on page 631
■ Plus (+)
■ Minus (-)
■ Underscore (_)
Do not use a minus as the first character. Spaces are only allowed in a comment
for a drive.
? Wildcard for any single character (A through Z; 0 through 9). For example:
file? refers to file2, file3, file4
file?? refers to file12, file28, file89
To back up all files named log01_03, log02_03, and so on, specify:
c:\system\log??_03
{ } Use a pair of curly brackets to indicate multiple file name patterns. Separate the
patterns by commas only; no spaces are permitted. A match is made for any or all
entries. For example:
{*1.doc,*.pdf} refers to file1.doc, file1.pdf, file2.pdf
To use wildcard characters literally, precede the character with a backslash (\).
Management topics 633
To power down and reboot NetBackup servers
In the exclude list, for example, precede the brackets with a backslash:
C:\abc\fun\[ny\]name
Note: The installation process copies the appropriate startup and shutdown
script from /usr/openv/netbackup/bin/goodies to /init.d and
creates links to it from the appropriate /rc directory.
Use system startup scripts to begin the Media Manager and NetBackup
daemons when the system boots up. Use shutdown scripts to terminate the
daemons at system shutdown. See the NetBackup Installation Guide for
instructions on how to edit the script.
/usr/openv/netbackup/bin/bp.kill_all
In the following sample display, the second column contains the process IDs for
the processes.
root 303 0.0 0.2 136 264 ? S Feb 11 4:32 ltid -v
Status for the nbemm command is not shown in the output of vmps. The nbemm
status is shown in the output of the bpps script.
Note: Restart the NetBackup Administration Console after any license updates.
The OpenStorage Disk Option, the PureDisk Storage Option, and the
Virtual Tape Option do not display all values at this time.
■ All registered license keys details: Displays the details of the license
keys that are registered on this server. The view lists:
■ each license key,
■ the server where the key is registered,
■ when the key was registered,
■ the features that the key provides, and
■ whether the feature is active or inactive.
3 Perform the following tasks from the NetBackup License Keys dialog box:
■ Add a new license
■ Delete a license
■ View the properties of one license
■ Export the license list
2 In the Add a New License Key dialog box, enter the license key and click Add.
The new license key appears in the license list.
2 In the NetBackup License Keys dialog box, click the Print button. The Print
dialog box appears.
3 Make your print selections and click OK.
licenses
To start the NetBackup license key utility
Run /usr/openv/netbackup/bin/admincmd/get_license_key
command.
The License Key Utility menu appears:
License Key Utility
-------------------
A) Add a License Key
H) Help
At the prompt, enter one of the following menu selections, then press Enter:
■ Type A to add a new license key, then type the license key at the prompt.
■ Type D to delete a license from the list, then type the license key at the
prompt.
■ Type F to list only the licenses that are currently active. Expired licenses do
not appear in this listing. Specify a local or a remote host.
■ Type L to list all registered licenses—active or inactive. Specify a local or a
remote host.
■ Type H for help on the License Key Utility.
■ Type q to quit the utility.
Management topics 639
To administer a remote master server
If the site has multiple master servers, you can configure the systems so
multiple servers can be accessed from one NetBackup Administrator Console.
To access remote servers:
■ First, make the remote server accessible to the local server.
For more information, see the following section, “To add a NetBackup
server to a server list” on page 639.
■ Second, indicate the remote server you want to administer.
See “To choose a remote server to administer” on page 644.
For example, assume server grape wants to administer host apricot remotely.
grape
apricot
640 Management topics
To administer a remote master server
Grape selects File > Change Server and types apricot as the host name.
grape
If grape is not listed on the server list of apricot, grape receives an error message
indicates server grape is invalid because it does not appear on the server list of
apricot.
To add grape to the server list of apricot, follow the steps in “To add a server to a
UNIX server list.” For other reasons why a remote server may be inaccessible,
see “If you cannot access a remote server” on page 648.
Note: To log in to a remote master server through the log in dialog box, the name
of the local host does not need to appear in the server list of the remote server.
This method to log in to a remote host is explained in “To indicate a remote
system upon log in” on page 645.
Management topics 641
To administer a remote master server
4 Select Servers to display the server list. The Additional Servers list
contains, as the dialog box explains, “Servers that can access the currently
selected host.”
Since the Additional Servers list does not include server grape, apricot
considers grape to be an invalid server.
5 To add a server to the server list, click Add. The New Server dialog box
appears.
6 Type the server name (grape) in the field and click Add to add the server to
the list. Click Close to close the dialog box without adding a server to the
list.
Management topics 643
To administer a remote master server
7 Restart all daemons and utilities on the server where the host properties
were changed to ensure that the new configuration values are used. Restart
the NetBackup Administration Console as well.
Note: The bp.conf file on every UNIX server contains SERVER and possibly
MEDIA_SERVER entries. The server list in the properties dialog box represents
these entries. Hosts that are listed as media servers have limited administrative
privileges.
Note: If the user has the necessary permissions on both machines, the user can
transition from Master A to Master B without setting up trust relationships.
If the user’s identity has administrative privileges on Master B but is different
from the user’s identity on Master A, the user is required to reauthenticate.
Reauthenticate from the NetBackup Administration Console by using File >
Login as New User... for Windows. Or, close and reopen the NetBackup-Java
Administration Console.
tiger shark
NetBackup-Java capable
UNIX client or server
bear
/usr/openv/java/jnbSA
In Figure 12-2, the administrator can use the administration console on console1
to add a comment for a drive on media_server1. The administrator can manage
NetBackup on master_server1 or media_server1 from any of the systems.
Console1 must be listed in the server list on master_server1 but does not need to
be listed on media_server1 because it is a media server.
648 Management topics
console1
Windows 2000 Server list:
NetBackup Remote master_server1
Administration Console
media_server1
master_server1 media_server1
Windows 2000 UNIX
bp.conf file Server list:
Master server Media server
SERVER=master_server1 master_server1
media_server1
console1
Start the Remote Administration Console, then select File > Change Server to
change to a NetBackup server.
The following procedure assumes that all other steps to add a media server are
accomplished. For the procedures, see “Adding a media server” in the NetBackup
2 On the EMM server host, run the following command (use the host name of
the media server):
nbemmcmd -addhost -machinename hostname -machinetype media
-netbackupversion level.major_level.minor_level
Note: To avoid problems with NetBackup, ensure that the host name you
use in NetBackup matches the host name in your TCP/IP configuration.
For more information about nbemmcmd, see NetBackup Commands for UNIX and
Linux.
Management topics 651
Using the NetBackup-Java Windows display console
* ADMIN=JBP JBP=ENDUSER+BU+ARC
Note: The host that is specified in the login dialog box and the system that runs
the NetBackup Administration Console must run the same NetBackup version.
Application server
The server that is usually the object of all administrative tasks is the host
specified in the NetBackup Administration Console login dialog box.
An exception is the use of the File > Change Server capability in the NetBackup
Administration Console. The Change Server capability allows administration of
a remote server (a server other than the one specified in the NetBackup
Administration Console login dialog box).
Remote server
Regardless of the which server is administered, all administrative tasks that are
performed in the NetBackup Administration Console make requests of the
654 Management topics
Configuring the NetBackup-Java administration console
application server. All tasks are run on the application server host, whether the
server is remote or whether the server is specified on the login dialog box.
However, regardless of which NetBackup authorization method is configured,
authorization for tasks in the Administration Console is specific to the server
being administered. For example, NetBackup-Java authorization capabilities are
in use on Host_A. Use Change Server to change to Host_B. The permissions are
honored as configured in the auth.conf on Host_B.
For successful administration of a remote server, the application server host
must be included in the server list of the remote server. For more information,
see “To add a NetBackup server to a server list” on page 639.
In earlier releases, this context (to change to a remote server from the
application server) also applied to the enhanced authentication and
authorization capabilities.
NetBackup encourages the use of Symantec Product Authentication and
Authorization for NetBackup Access Control (NBAC) instead of legacy security
implementations. For information about how enhanced authorization and
authentication applies in this context, see the NetBackup 6.0 documentation.
If NetBackup Access Control is not configured, you may still authorize users of
the NetBackup-Java administration console for specific applications.
For more information, see “USE_NBJAUTH_WITH_ENHAUTH” on page 666.
NetBackup Access Control, when configured as described, always takes
precedence over the capabilities authorization of NetBackup-Java as described
in “To configure nonroot usage” on page 658.
When NetBackup Access Control is configured, but a user is not authorized as a
NetBackup administrator, the capabilities allowed to this user in the Backup,
Archive, and Restore (jbpSA) application are those specified for the user in the
auth.conf file resident on the host specified in the NetBackup-Java login
dialog box.
Users of the NetBackup-Java interfaces must log in to the NetBackup-Java
application server that is on the NetBackup host where they want to perform
administrator or user operations.
The /usr/openv/java/auth.conf file contains the authorization data for
accessing NetBackup-Java applications. This file exists only on NetBackup-Java
capable machines where the NetBackup-Java interface software is installed. The
default auth.conf file provides the following authorizations:
■ On NetBackup servers: Administration capabilities for the root user and
user backup and restore capabilities for all other users.
■ On NetBackup clients: User backup and restore capabilities for all users.
On all other UNIX NetBackup systems, the file does not exist but the
NetBackup-Java application server provides the same default authorization. To
change these defaults on other UNIX systems, you must create the
/usr/openv/java/auth.conf file.
To perform remote administration or user operations with jbpSA a user must
have valid accounts on the NetBackup UNIX server or client machine.
* ADMIN=JBP JBP=ENDUSER+BU+ARC
■ The first field of each entry is the user name that is granted access to the
rights that the entry specifies. In the released version, the first field allows
root users to use all of the NetBackup-Java applications.
An asterisk in the first field indicates that any user name is accepted and
the user is allowed to use the applications as specified. If the auth.conf
file exists, it must have an entry for each user. Or, the auth.conf file must
have an entry that contains an asterisk (*) in the username field; users
without entries cannot access any NetBackup-Java applications. Any entries
that designate specific user names must precede a line that contains an
asterisk in the username field.
Note: The asterisk specification cannot be used to authorize all users for any
administrator capabilities. Each user must be authorized by using individual
entries in the auth.conf file.
To deny all capabilities to a specific user, add a line that indicates the user
before a line that starts with an asterisk. For example:
mydomain\ray ADMIN= JBP=
* ADMIN=JBP JBP=ENDUSER+BU+ARC
asterisk means that NetBackup-Java validates any user name for access
to the Backup, Archive, and Restore client application (jbpSA).
JBP=ENDUSER+BU+ARC allows end users to back up, archive, and
restore files only.
The user name and password that is entered in the login screen must be valid on
the machine that is specified in the host field. (True for starting the
NetBackup-Java administration console or the Backup, Archive, and Restore
application (jbpSA).) The NetBackup-Java application server authenticates the
user name and password by using the system password file data for the specified
machine. The password must be the same password that was used upon login at
that machine.
For example, assume you log in with the following information:
username = joe
password = access
Here you must use the same user name and password to log into
NetBackup-Java.
Note: The NetBackup-Java login box accepts passwords greater than eight
characters. However, only the first eight are significant upon login to a
NetBackup-Java application server on a UNIX system.
You can log in to the NetBackup-Java application server under a different user
name than the name used to log in to the operating system. For example, if you
log in to the operating system with a user name of joe, you could subsequently
log in to jnbSA as root.
Upon exit, some application state information is automatically saved in the
directory of joe $HOME/.java/.userPrefs/vrts directory. (For example,
table column order.) The information is restored the next time you log in to the
operating system under account joe and initiate the NetBackup-Java application.
This login method of is useful if there is more than one administrator because it
saves the state information for each administrator.
If the user name is not valid as determined by the contents of the auth.conf
file, an error message appears. All applications are inaccessible to the user:
No authorization entry exists in the auth.conf file for username
available to you.
■ The defaults allow anyone with any valid user name to use the Backup,
Archive, and Restore client application (jbpSA).Only root users can access
the administrator applications and the administrator capabilities in jbpSA.
■ Specify entries for valid user names.
Note: The validated user name is the account the user can back up, archive or
restore files from or to. The Backup, Archive, and Restore application (jbpSA)
relies on system file permissions when to browse directories and files to back up
or restore.
Abbreviation Description
ALL Indicates that the user has administrative privileges for all of
the applications that are listed in this table.
AM Activity Monitor
CAT Catalog
DM Device Monitor
MM Media Management
REP Reports
For example, to give a user (user1) access only to the Device Monitor and
Activity Monitor, add the following entry to the auth.conf file:
user1 ADMIN=DM+AM
In order for a nonroot user to modify the files that the NetBackup-Java
Administration Console uses, run the nonroot_admin_nbjava script. The
script changes permissions on the following files:
/usr/openv/java/auth.conf
/usr/openv/java/Debug.properties
/usr/openv/java/nbj.conf
BPJAVA_PORT, VNETD_PORT
The following ports are the configured ports for the bpjava-msvc and vnetd
daemon processes. These ports are registered with the Internet Assigned
Numbers Authority (IANA).
bpjava-msvc BPJAVA_PORT=13722
vnetd VNETD_PORT=13724
Symantec recommends that these ports are not changed. If changes are
necessary, make the change on all NetBackup hosts in the relevant NetBackup
cluster as described in the NetBackup Installation Guide. The value must be set
in the corresponding nbj.conf (UNIX) or setconf.bat (Windows)
configuration option.
FIREWALL_IN
The FIREWALL_IN configuration option provides a method to use a Java
Administration Console that is outside of a trusted network to administer the
NetBackup master servers that are within a trusted network.
This option uses the following format.
On UNIX:
FIREWALL_IN= HOST1:PORT1=HOST2:PORT2[;...;HOSTn:PORTn=HOSTm:PORTm]
On Windows:
SET FIREWALL_IN=
HOST1:PORT1=HOST2:PORT2;IP_ADDR1:PORT3=IP_ADDR2:PORT4
■ Enter the port number of the bpjava service in the trusted internal
network. Then, map the private interface where the bpjava service runs to
a public interface that can be reached from outside the firewall.
■ Set up a secure shell (SSH) tunnel from the local host to the system inside
the firewall.
Example
In the following example:
■ Master server NBUMaster.symc.com is in a trusted network, behind a
firewall.
■ The IP address of NBUMaster.symc.com is 10.221.12.55.
■ The NetBackup Java Administration Console is installed on localhost.
■ SSH tunnels exist from localhost to NBUMaster.symc.com as follows:
Note: The same options are used if NBUMaster.symc.com has a public interface
(NBUMasterpub.symc.com) that can be reached from the Internet. In this case,
the administrator would replace localhost with NBUMasterPub.synm.com.
FORCE_IPADDR_LOOKUP
The FORCE_IPADDR_LOOKUP configuration option specifies whether
NetBackup performs an IP address lookup to determine if two host name strings
are indeed the same host. This option uses the following format:
FORCE_IPADDR_LOOKUP = [ 0 | 1 ]
Where:
0 = Indicates that no IP address lookup is performed to determine if two host
name strings are indeed the same host. They are considered to be the same host
if the host name strings compare equally. Or, if a short name compares equally
to the short name of a partially or fully qualified host name.
1 = Indicates that an IP address lookup is performed if the two host name strings
do not match. The lookup determines if they have the same host. The default is
to perform an IP address lookup if necessary to resolve the comparison. The IP
address lookup is not performed if the host name strings compare equally.
Note: Use a value of 1 for this option if you have the same host name in two
different domains. For example, eagle.abc.xyz and eagle.def.xyz or
using host name aliases.
INITIAL_MEMORY, MAX_MEMORY
Both INITIAL_MEMORY and MAX_MEMORY allow configuration of memory usage
for the Java Virtual Machine (JVM).
Symantec recommends that the NetBackup-Java Administration Console, the
NetBackup-Java Windows Display Console, or the NetBackup, Archive, and
Restore user interface be run on a system that contains at least 1 gigabyte of
physical memory. Make sure that 256 megabytes of memory is available to the
application.
INITIAL_MEMORY specifies how much memory is allocated for the heap when
the JVM starts. The value probably does not require changing. The default is
sufficient for quickest initialization of jnbSA, the NetBackup-Java Windows
Display Console, or jbpSA on a system with the recommended amount of
memory.
On UNIX systems, the initial memory allocation can also be specified as part of
the jnbSA or jbpSA command. For example:
jnbSA -ms 36M
Default = 36M (megabytes).
MAX_MEMORY specifies the maximum heap size that the JVM uses for
dynamically allocated objects and arrays. If the amount of data is large, consider
664 Management topics
Configuring the NetBackup-Java administration console
specifying the maximum heap size. For example, a large number of jobs in the
Activity Monitor.
On UNIX systems, the maximum memory allocation can also be specified as part
MEM_USE_WARNING
The MEM_USE_WARNING configuration option specifies the percent of memory
used compared to MAX_MEMORY, at which time a warning dialog is displayed to
the user. Default = 80%. This option uses the following format:
MEM_USE_WARNING=80
NBJAVA_CLIENT_PORT_WINDOW
The NBJAVA_CLIENT_PORT_WINDOW configuration option specifies the range
of non-reserved ports on this computer to use for connecting to the
NetBackup-Java application server. Or, to connect to the bpjobd daemon from
the NetBackup-Java Administration Console’s Activity Monitor.
This option uses the following format:
NBJAVA_CLIENT_PORT_WINDOW = n m
Where:
■ n indicates the first in a range of non-reserved ports that are used for
connecting to the bpjava processes on the NetBackup-Java application
server. Or, for connecting to the bpjobd daemon or Windows service from
theActivity Monitor of the NetBackup-Java Administration Console.
If n is set to 0, the operating system determines the non-reserved port to
use (default).
■ m indicates the last in a range of non-reserved ports that are used for
connecting to the NetBackup-Java Administration Console/NetBackup-Java
Windows Display Console.
If n and m are set to 0, the operating system determines the non-reserved
port to use (default).
The minimum acceptable range for each user is 120. Each additional concurrent
user requires an additional 120. For example, the entry for three concurrent
users might look as follows:
NBJAVA_CLIENT_PORT_WINDOW = 5000 5360
If the range is not set wide enough, jnbSA exits with an error message that
states an invalid value has occurred during initialization.
Management topics 665
Configuring the NetBackup-Java administration console
NBJAVA_CONNECT_OPTION
The NBJAVA_CONNECT_OPTION configuration option specifies how the
NetBackup-Java application server is connected to. It may be done using the
vnetd daemon (VNETD_PORT) or directly using the application server’s port
(BPJAVA_PORT). The option also specifies the callback method that the server or
the client uses when it communicates with the NetBackup-Java consoles (jnbSA,
jbpSA).
The default for NBJAVA_CONNECT_OPTION requires only that the vnetd port
be accessible through any firewall.
NBJAVA_CONNECT_OPTION = [ 0 | 1 ]
Where:
0 = Indicates a direct connection to the application server and the traditional
callback method.
1 = Indicates a connection to the application server using vnetd and the no
callback method (default).
NBJAVA_CORBA_DEFAULT_TIMEOUT
The NBJAVA_CORBA_DEFAULT_TIMEOUT configuration entry specifies the
default timeout that is used for most CORBA operations that are performed by
the Java Administration Console.
This option is present by default and uses the following format:
NBJAVA_CORBA_DEFAULT_TIMEOUT=60
NBJAVA_CORBA_LONG_TIMEOUT
The NBJAVA_CORBA_LONG_TIMEOUT configuration entry specifies the timeout
value that is used by the following areas in the Java Administration Console:
■ Device configuration wizard
■ Disk Pool configuration wizard
■ Disk Pool Inventory
NBJAVA_CORBA_LONG_TIMEOUT=1800
USE_NBJAUTH_WITH_ENHAUTH
NetBackup encourages the use of Symantec Product Authentication and
Authorization for NetBackup Access Control (NBAC) instead of legacy security
implementations.
For information about the USE_NBJAUTH_WITH_ENHAUTH configuration
option, see the NetBackup 6.0 documentation. For information on Symantec
Product Authentication and Authorization, see the NetBackup Security and
Encryption Guide.
Note: jnbSA and jbpSA don’t always use the command lines to retrieve or
update data. The interfaces have some protocols that instruct the application
server to perform tasks using NetBackup and Media Manager APIs.
/usr/openv/netbackup/logs/user_ops/_username_/logs
A directory exists for each user that uses the NetBackup-Java applications.
This option also controls how long the NetBackup-Java GUI log files are
kept in /usr/openv/netbackup/logs/user_ops/nbjlogs.
■ Consider the network communication speed and the amount of data being
transferred.
■ Consider the amount of work being performed on the relevant machines.
Run NetBackup-Java on a machine that has a low level of activity. For
example, there can be large differences in response time when other
memory-intensive applications are running on the machine. (For example,
Web browsers.) Multiple instances of NetBackup-Java on the same machine
have the same effect.
■ Run NetBackup-Java on a 1 gigabyte machine that has at least 256 MB of
RAM available to the application. In some instances, the application does
not initiate due to insufficient memory. A number of messages identify
these failures in the xterm window where the jnbSA command was run. Or,
the messages appear in the application log file. Possible messages include
the following:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Out of Memory
For more information, refer to the bp.conf options “INITIAL_MEMORY,
MAX_MEMORY” on page 663.
■ Consider the amount of physical memory on the relevant machines.
Possibly add memory on the host being administered (the console’s
application server host).
■ Consider increasing the swap space to relevant machines:
■ The console host (the host where the console is started)
■ The host being administered
Increase the amount of swap space available to the system where you are
running the applications can increase performance. Especially if there is a
great deal of other activity on the machine. More swap space can alleviate
hangs or other problems that relate to insufficient memory for the
applications.
■ Consider additional or faster CPUs to relevant machines:
■ The console host (the host where the console is started)
■ The host being administered
■ To save startup time, allow NetBackup-Java to run (iconified) rather than
exit and restart. Startup of the Java virtual machine can take longer than
other applications.
■ Consider limiting the amount of NetBackup data that is retained for long
periods of time to only that which is necessary. For example, do not retain
successfully completed jobs for more than a few hours.
670 Management topics
For more information, see “Managing the jobs database” on page 67.
Scenario 1
Assume no deficiency in either the console host’s resources or the application
server host’s resources. Assume that the amount of NetBackup configuration
data being transferred to the console host far exceeds the X-Windows pixel
display data. That is, the actual console screen being sent from the remote host.
Unfortunately, the only way to determine the viability of this situation is to try
it. Network capabilities and the proximity of the two hosts influences each
NetBackup configuration.
Scenario 2
Assume that the available resources of the application server host far exceed
that of the console host.
Assume that the console host has a very limited CPU and memory as compared
to the NetBackup master server being administered. (The console host is the
machine on which the console is started.) If the console is run on the master
server and displayed back to the desktop host, performance may be enhanced.
If the desktop host is a Windows machine, X-terminal emulation or remote
display tools such as Exceed and VNC are required.
Management topics 671
NetBackup-java performance improvement hints
File Description
The topics in this section concern aspects of how to manage restores for
NetBackup clients.
■ “Server-directed restores” on page 672
■ “Client-redirected restores” on page 673
■ “Restoring files and access control lists” on page 681
■ “To improve search times by creating an image list” on page 682
■ “Set original atime for files during restores” on page 682
■ “Checkpoint restart for restore jobs” on page 683
■ “Restoring system state” on page 684
Find related topics in Chapter 5, “Reference Topics,” in the NetBackup
Administrator’s Guide, Volume II. Incorrectly specified host names are often a
factor in file restore problems.
Server-directed restores
By default, NetBackup clients are configured to allow NetBackup administrators
■ Windows clients: Open the Backup, Archive, and Restore interface on the
client.
Select File > NetBackup Client Properties > General tab > Clear the Allow
server-directed restores checkbox.
■ UNIX clients: Add DISALLOW_SERVER_FILE_WRITES to the following file
on the client:
/usr/openv/netbackup/bp.conf
Note: On UNIX systems, the redirected restores can incorrectly set UIDs or GIDs
that are too long. The UIDs and GIDs of files that are restored from one platform
to another may be represented with more bits on the source system than on the
destination system. If the UID/GID name in question is not common to both
systems, the original UID/GID could be invalid on the destination system. In this
case, the UID/GID is replaced with the UID/GID of the user that performs the
restore.
that performs the restore. (A progress log is an entry in the Task Progress tab of
Without the entry in the bp.conf file (or the server list), the restoring server
■ To produce a progress log, add the requesting server to the server list:
log into the requesting server. In the NetBackup Administration Console,
expand NetBackup Management > Host Properties > Master Servers >
Double-click on master server > Servers. Add the restoring server to the
server list.
■ Log in to the restoring server. Check the Activity Monitor to determine the
success of the restore operation.
Note: To restore a UNIX backup that contains soft and hard links, the Backup,
Archive, and Restore client interface must be run from a UNIX machine. Only
the Java version of the client interface contains the Rename hard links and
Rename soft links restore options. Windows users can install the Windows
display console to access the Java version of the Backup, Archive, and Restore
interface from a Windows machine. (See “Running the Java-based Windows
Display Console” on page 37.)
Client-redirected restores
The Backup, Archive, and Restore client interface contains options for allowing
clients to restore the files that were backed up by other clients. The operation is
called a redirected restore.
files. NetBackup ensures that the client name of the requesting client matches
the peer name that was used to connect to the NetBackup server.
Unless clients share an IP address, the peer name is equivalent to the client’s
host name. (Clients may share an IP address due to the use of a gateway and
through a gateway, the gateway can use its own peer name to make the
connection.
The NetBackup client name is normally the client’s short host name, such as
Open Backup, Archive, and Restore and select File > Specify NetBackup
Machines and Policy Type. The client name that is selected as Source Client
for Restores is the source of the backups to be restored.
■ On NetWare target clients:
Specify the client name in the bp.ini file.
■ UNIX clients:
Open Backup, Archive, and Restore and select the client name as the Source
client for restore.
Note: The information within this section applies to restores made using the
command line, not the Backup, Archive, and Restore client interface.
Create an altnames directory in the following location, then place the empty
file inside of the directory:
/usr/openv/netbackup/db/altnames/No.Restrictions
The NetBackup client name setting on the requesting client must match the
name of the client for which the backup was created. The peer name of the
requesting client does not need to match the NetBackup client name setting.
Note: The information within this section applies to restores made using the
command line, not the Backup, Archive, and Restore client interface.
Create an altnames directory in the following location, then place the empty
file inside of the directory:
/usr/openv/netbackup/db/altnames/peername
Where peername is the client to possess restore privileges.
In this case, the requesting client (peername) can access the files that are
backed up by another client. The NetBackup client name setting on peername
must match the name of the other client.
Note: The information within this section applies to restores made using the
command line, not the Backup, Archive, and Restore client interface.
676 Management topics
Managing client restores
Caution:
Not all file system types on all machines support the same features. Problems
may be encountered when a file is restored from one file system type to another.
For example, the S51K file system on SCO machines does not support symbolic
links nor does it support names greater than 14 characters long.
You may want to restore a file to a machine that doesn’t support all the features
of the machine from which the restore was performed. In this case, all files may
not be recovered.
Note: The information within this section applies to restores made using the
command line, not the Backup, Archive, and Restore client interface.
Management topics 677
Managing client restores
Note: You must be a root user for any of the steps that must be performed on the
NetBackup server. You may also have to be a root user to make the changes on
the client.
Caution: The No.Restrictions file allows any client to restore files from
client2.
client1
NetBackup
server
client2 Token TCP
Ring Gateway
client3
In this example, restore requests from client1, client2, and client3 are
routed through the TCP gateway. Because the gateway uses its own peer name
rather than the client host names for connection to the NetBackup server,
NetBackup refuses the requests. Clients cannot restore even their own files.
Perform the following stops to correct the situation:
1 Determine the peer name of the gateway:
a Attempt a restore from the client in question. In this example, the
request fails with an error message similar to the following:
client is not validated to use the server
b Examine the NetBackup problems report and identify the peer name
that is used on the request. Entries in the report may be similar to the
following:
01/29/07 08:25:03 bpserver - request from invalid
server or client client1.dvlp.null.com
In this example, the peer name is client1.dvlp.null.com.
2 Run the touch command on the following file:
/usr/openv/netbackup/db/altnames/peername
In our example, the file is:
/usr/openv/netbackup/db/altnames/client1.dvlp.null.com
empty, client1, client2, and client3 can all access the backups that
For more information, see “To allow a single client to perform redirected
If you add the names client2 and client3 to the file, you give these two
For more information, see “To allow redirected restores of a client’s files”
on page 675.
Run the following command on the master server while logged in as root. Enter
/usr/openv/netbackup/bin/admincmd/bpimage -create_image_list
-client name
Where name is the name of the client with small backup images.
/usr/openv/netbackup/db/images/clientname
Do not edit these files. The files contain offsets and byte counts that are used to
The files require 35 to 40% more space in the client directory. The files improve
search performance only if thousands of small backup images for a client exist.
Note: If a checkpointed restore that has no end date is suspended, then resumed,
and a new backup occurs before the resume is initiated, the files from the new
backup are included in the restore.
For example, a user makes a restore request of a directory, then that restore is
suspended. The request is resumed the next day, after another backup of the
directory has been performed. The files that are restored are from the latest
backup.
Note: Although NetWare clients use the Standard policy type, Checkpoint
Restart for restores is not supported on NetWare clients.
■ Third Party Copy and the Media Server Copy images that use Standard
policy types are supported. However, they cannot be suspended or resumed
if the backup image has changed blocks. Flashbackup is not supported.
Note: The best recovery procedure depends on many hardware and software
variables that pertain to your server and its environment. A complete Windows
recovery procedure is beyond the scope of this manual; you may need to contact
Microsoft or refer to your Microsoft documentation.
Caution: Do not redirect the System State restore to a different host. System
State is computer-specific. To restore it to a different computer can result in an
unusable system.
but before the server is restarted. An authoritative restore ensures that the
Goodies scripts
Supported configurations
The next two figures show configurations where NetBackup supports alternate
server restores. All methods require that the server that is used for the restore
688 Management topics
Alternate server restores
be in the same cluster as the server that performed the original backup. The
server must also share the same Enterprise Media Manager database.
Robot
NetBackup Image Control
Catalog
Drive 2
Drive 1
Enterprise Media
Media
Manager database
Server 1
Media
Server 2
Robot 1 Robot 2
Control Control
Drive 1 Drive 1
Drive 2 Media
server 1
NetBackup image
catalog
Stand-alone drive
Enterprise Media
Manager database Drive 1
Media
Master server server 2
Note:
Media servers 1 and 2
may be off-site.
To modify catalogs when the server that wrote the media is available
1 If necessary, physically move the media. Then, update the Enterprise Media
Manager database by using move volume options in the Media Manager
administration utilities.
2 Update the NetBackup image catalog on the master server. Update the
NetBackup media catalogs on both the original NetBackup server
(oldserver) and the destination NetBackup server (newserver).
Use the following command, which can be run from any one of the
NetBackup servers. The admincmd command must be entered on one line.
■ As root on a UNIX NetBackup server:
cd /usr/openv/netbackup/bin/admincmd
bpmedia -movedb -m media_id -newserver hostname
-oldserver hostname
■ As administrator on a Windows NetBackup server:
cd install_path\NetBackup\bin\admincmd
To modify catalogs when the server that wrote the media is not available
1 If necessary, physically move the media. Then, update the Enterprise Media
Manager database by using the move volume options in the Media and
Device Management window.
2 Update only the NetBackup image catalog on the master server. Use the
following commands from the NetBackup master server. The admincmd
command must be entered on one line.
Management topics 691
Alternate server restores
cd /usr/openv/netbackup/bin/admincmd
-oldserver hostname
-oldserver hostname
Note: The override applies to all storage units on the original server. This means
that restores for any storage unit on fromhost go to tohost.
Note: The failover uses only the failover hosts that are listed in the NetBackup
configuration. (See the following procedure.) By default, the list is empty and
NetBackup does not perform the automatic failover.
Open the Restore Failover host properties dialog of the master server.
Add an entry in the Alternate Restore Failover Machines list, that lists
the media server and failover restore server(s).
■ By modifying the bp.conf file on a UNIX NetBackup server:
As root, add the following entry to the
/usr/openv/netbackup/bp.conf file:
FAILOVER_RESTORE_MEDIA_SERVERS =
failed_host host1 host2 ... hostN
where:
failed_host is the server that is not operational.
host1 ... hostN are the servers that provide failover
capabilities.
When automatic failover is necessary for a given server, NetBackup
searches through the relevant FAILOVER_RESTORE_MEDIA_SERVERS
list. NetBackup looks from left to right for the first server that is
eligible to perform the restore.
2 Stop and restart the NetBackup Request daemon on the master server.
Caution: NetBackup does not set the Storage Migrator obsoletion date for a file.
Make sure that the migrated copies are retained for at least as long as the
backups. Restores are not possible unless the copies are retained.
When NetBackup restores purged files, Storage Migrator considers the restored
files to be purged, with a file slice value of zero. If files have been selected for
migration and not yet copied to secondary storage, NetBackup backs them up.
A bparchive back up and remove operation always caches a purge file.
For more information, see “Set original atime for files during restores” on
page 682.
Note: If you use another migration product, make sure that it provides adequate
and full recoverability of the disk-resident data. Make sure that it has
transparent access to the disk files at the application level.
Installation overview
server. The master server is also the default location for the Enterprise Media
Manager (EMM) server. Since EMM is the primary user of NBDB, the NetBackup
database always resides on the same machine as the Enterprise Media Manager.
For performance reasons, the EMM server and the relational database can be
The following steps are performed automatically during installation, but can be
1 As part of the NetBackup master server installation, the Sybase ASA 9.0.1
server is created. The server parameters are set in the server.conf file:
/usr/openv/var/global/server.conf
The contents of the server.conf file are described in “server.conf” on
page 699.
2 The following entry sets the database location. It is added to the bp.conf
file:
VxDBMS_NB_DATA = /usr/openv/db/data
/usr/openv/db/data/EMM_INDEX.db
7 The Sybase ASA accounts and schema are created for each of the NetBackup
components that make use of the NetBackup database. (For example,
EMM_MAIN.)
8 The following command initializes the EMM data:
/usr/openv/volmgr/bin/tpext
699
Installation overview
host. NBDB must always be on the same host as the EMM server.
The NBDB database files can be moved from their default location in
/usr/openv/db/data.
Note: If Bare Metal Restore is installed, BMRDB must be located on the master
server.
server.conf
Caution: Symantec recommends that this file not be edited without assistance
from Technical Support. NetBackup may not start if server.conf is edited.
DBA -gl
/usr/openv/db//log/server.log -ud
-n NB_server_name
Where server_name indicates the name of the Sybase ASA server. Each
Sybase server has a unique name. Use the same name that was used during
installation. If a fully qualified name was used at that time, use a fully
qualified name here.
Caution: If this name is changed, the Enterprise Media Manager cannot connect
to the database.
700
Installation overview
-x tcpip(LocalOnly=YES;ServerPort=13785)
Indicates the maximum page size (in bytes) for the database. This
parameter is given during database creation.
-ct+
Indicates that the DBA user is the account used to start, stop, load, and
unload data.
-ti 0
Indicates the client idle time that is allowed before shutdown. By default, no
idle time is allowed, which prevents the database from shutting down.
-c 25M
Indicates the initial memory that is reserved for caching database pages and
other server information. (May be changed for performance reasons.)
-ch 500M
Indicates the number of requests the database server can handle at one
time. This parameter limits the number of threads upon startup. (May be
changed for performance reasons.)
-o /usr/openv/db/log/server.log
databases.conf
The /usr/openv/var/global/databases.conf configuration file contains
the locations of the main database files and the database names for automatic
startup when the ASA daemon is started. For example, if NBDB and BMRDB are
701
Installation overview
"/usr/openv/db/data/BMRDB.db" -n BMRDB
vxdbms_env.csh, vxdbms_env.sh
The scripts vxdbms_env.csh and vxdbms_env.sh set up the ASA
environment:
■ /usr/openv/db/vxdbms_env.csh
■ /usr/openv/db/vxdbms_env.sh
/bin
/usr/openv/db/bin contains all ASA commands and NetBackup-specific
commands:
■ create_nbdb
Used during installation and upgrades to create and upgrade the NetBackup
database, NBDB.
■ nbdb_admin
Among other things, use nbdb_admin to change the DBA and NetBackup
account passwords, or to start and stop individual databases.
■ nbdb_backup
Use to make an online or an offline backup of the ASA database files to a file
system directory.
■ nbdb_move
Use to change the location of the ASA database files from the default
location.
■ nbdb_ping
Displays the status of the ASA database.
■ nbdb_restore
Use to recover from an online or an offline backup in a file system directory
that was created using nbdb_backup.
■ nbdb_unload
Use to create a dump of all or part of the NBDB database or the BMRDB
database schema and data.
■ nbdbms_start_server
Use to start and stop the ASA daemon.
702
Installation overview
■ nbdb_upgrade
Used internally to upgrade the NetBackup and BMR databases.
Note: Commands are described in NetBackup Command for UNIX and in the
online help.
/charsets
/usr/openv/db/charsets contains ASA-specific information.
/data
/usr/openv/db/data is the default location of the database, NBDB:
■ NBDB.db
Main NetBackup database file; considered a dbspace.
■ EMM_DATA.db
An additional dbspace that contains EMM data.
■ EMM_INDEX.db
Enhances the EMM database performance.
■ NBDB.log
The transaction log for the NetBackup database, necessary for recovery.
NBDB.log is automatically truncated after a successful full or incremental
online, hot or offline, cold catalog backup of the ASA database.
■ vxdbms.conf
Contains the configuration information specific to the Sybase ASA
installation:
VXDBMS_NB_SERVER = NB_server_name
VXDBMS_NB_PORT = 13785
VXDBMS_NB_DATABASE = NBDB
VXDBMS_BMR_DATABASE = BMRDB
VXDBMS_NB_DATA = /usr/openv/db/data
VXDBMS_NB_INDEX = /usr/openv/db/data
VXDBMS_NB_TLOG = /usr/openv/db/data
VXDBMS_NB_PASSWORD = encrypted_password
The encrypted password that is used to log into both the DBA accounts for
NBDB and BMRDB, and other data accounts is stored in vxdbms.conf.
/lib
/usr/openv/db/lib contains all the ASA shared libraries. The directory also
includes ODBC libraries, used to connect to NBDB and BMRDB.
/log
/usr/openv/db/log contains the ASA server log file server.log that
contains only Sybase logs.
/res
/usr/openv/db/res contains ASA-specific information.
/scripts
/usr/openv/db/scripts contains the ASA SQL scripts that are used to
create the database. The directory also contains NetBackup SQL scripts that are
used to create the EMM and other schemas.
/staging
/usr/openv/db/staging is used as a temporary staging area during online,
hot catalog backup and recovery.
/tix
/usr/openv/db/tix contains ASA-specific information.
704
Installation overview
706
Installation overview
Clusters
Sybase ASA is supported in a clustered environment. Sybase ASA failover is
included with the NetBackup server failover solution. The software is installed
on all machines in the cluster, but the database files are created on a shared
disk.
To facilitate the shared files, database and configuration files are installed on a
shared drive:
707
Post-installation tasks
Post-installation tasks
The default password that is set during installation is nbusql. This password is
used for NBDB and BMRDB and for all DBA and application accounts. (For
example, EMM_MAIN.)
The nbdb_move command can be run at any time because it does not drop, then
recreate the database. Thus, all data is preserved.
Note: Back up NBDB and BMRDB using the catalog backup method of choice
both before and after running nbdb_move.
-data data_directory
-mlog log_mirror_directory
For extra protection, a mirrored transaction log can be used. This mirrored log
To move the existing data, index, transaction log files, and create the
mirrored transaction log, enter:
/usr/openv/db/bin/nbdb_move -data data_directory
-mlog log_mirror_directory
Caution: If the NBDB.db database already exists, to run create_nbdb does not
overwrite it. If you want to move the database, move it using the nbdb_move
command.
5 The new NBDB database is empty and does not contain the EMM data that is
loaded during a normal installation.
Make sure that you have the most current support for new devices before
the data is repopulated. New devices are added approximately every two
months.
6 Repopulate the EMM data by running the tpext utility. tpext updates the
EMM database with new versions of device mappings and external attribute
files.
/usr/openv/volmgr/bin/tpext
log_mirror_directory]
If the NBDB database files were moved from the default location using
nbdb_move, use this command to recreate them in the same location.
Specify current_data_directory.
Caution: If the location of NBDB.db has changed from the default, BMRDB.db
must also be recreated. The BMRDB.db files must reside in the same location as
the NetBackup database files.
712
Backup and recovery procedures
page 283.
more child jobs. Events for these jobs appears in the dbm log.
An overview of the hot catalog backup process consists of the following steps:
/usr/openv/db/staging
Once the copy is made, NetBackup can back up the catalog files.
2 A child job backs up files in a single stream:
■ Configuration files (server.conf, database.conf, vxdbms.conf)
■ Database files:
■ NBDB.db
■ NBDB.log
■ EMM_DATA.db
■ EMM_INDEX.db
If BMR has been installed:
■ BMRDB.db
■ BMRDB.log
■ BMR_DATA.db
■ BMR_INDEX.db
3 A second child job begins the image catalog backup.
Note: The backup of any 5.x media server displays as a separate job.
Note: If BMR is installed and a remote EMM server is in use, the backup of
the EMM server displays as a separate job.
portion of the online, hot catalog backup. One on the media server for NBDB
and one on the master server for BMRDB.
catalog backup.
An overview of the cold catalog backup process consists of the following steps:
1 The ASA databases are queried for the location of the database files
associated with the database. In the case of NBDB, the following files are
dynamically located:
■ NBDB.db
■ NBDB.log
■ EMM_DATA.db
■ EMM_INDEX.db
In the case of BMRDB, the following files are dynamically located:
■ BMRDB.db
■ BMRDB.log
■ BMR_DATA.db
■ BMR_INDEX db
If these files have been moved (using nbdb_move) from the default location
(/usr/openv/db/data), the locations are determined automatically.
2 The databases NBDB and BMRDB are shut down (if BMRDB exists). The
Sybase ASA daemon continues to run.
3 The relational database files as identified in step 1, as well as the image
catalog files, are backed up.
4 If the backup is successful, the transaction logs are truncated and the
databases are restarted. If the backup was not successful, the databases are
restarted without truncating the transaction logs.
If NBDB has been moved to a media server, the offline, cold catalog backup
includes the database files on the media server. The back up shuts downand
starts up the database remotely. Additional logs appear in the admin log on the
media server.
to both online, hot or offline, cold catalog backups.) The transaction log,
NBDB.log, is located by default in:
/usr/openv/db/data/NBDB.log
The transaction log continues to grow until it becomes truncated. The online,
hot or offline, cold catalog backups must run frequently enough so that the
transaction log doesn’t grow to fill the file system.
In addition to the default transaction log, a mirrored transaction log can be
created for additional protection of NBDB using:
/usr/openv/db/bin/nbdb_move -mlog mirrored_log_directory
The directory for the mirrored log should not be the same as the directory for
the default transaction log. Ideally, the mirrored log should be located on a file
system on a different physical disk drive.
If BMR is installed, a transaction log for BMRDB is also created by default in:
/usr/openv/db/data/BMRDB.log
The BMRDB transaction logs are backed up and truncated during the catalog
backup along with the NBDB transaction logs.
Caution: If a catalog backup is not run, the logs won’t be truncated. Truncation
must be managed in this manner as it is critical to recovery of the database.
Catalog recovery
The method that is used to recover the catalog in a disaster recovery situation
nbdb_backup
Use nbdb_backup to make either an online or an offline copy of the NBDB
database files and the BMRDB database files in a directory. The transaction log
won’t be truncated using nbdb_backup. Transaction logs are managed only by
using the catalog backup.
/usr/openv/db/bin/nbdb_backup [-dbn
Caution: The transaction logs are not truncated using nbdb_backup. A catalog
backup must be run to truncate the logs.
nbdb_restore
Use nbdb_restore to recover from a database backup that was made using
nbdb_backup.
/usr/openv/db/bin/nbdb_restore -recover source_directory
These commands are logged in the admin directory.
Where:
■ -dbn database_name
database_name is NBDB (default) or BMRDB.
■ -t table_list
Must list the owner of the table, then the table name. For EMM, the account
EMM_MAIN owns all tables.
nbdb_unload -t EMM_MAIN.EMM_Device, EMM_MAIN.EMM_Density
■ -s
Schema only is dumped; no data.
■ destination_directory
Specify the location where dump is created.
To terminate connections
5 Shut down all NetBackup daemons:
/usr/openv/netbackup/bin/bp.kill_all
718
Database unloading tool
4 Shut down NetBackup on A, B, and on all master servers and media servers
that use host A as the EMM server:
/usr/openv/netbackup/bin/bp.kill_all
5 Copy the following catalog files from their location on A to the final location
on B:
Note: The final location on B does not need to be the same as the original
location on A.
720
Moving the NetBackup database from one host to another
NBDB.db
EMM_DATA.db
EMM_INDEX.db
NBDB.log
NBDB.m.log (optional)
If the database files on A and B are in the default location and server A is
also a UNIX server, go to step 11. (The default location is
/usr/openv/db/data.)
6 Change databases.conf on A and B so that the databases don’t start
automatically when the server is started:
/usr/openv/db/bin/nbdb_admin -auto_start NONE
EMM_INDEX.db
NBDB.db
NBDB.log
NBDB.m.log (optional)
11 Change the EMMSERVER entry in the bp.conf file from A to B on all master
servers and media servers that had used A as the EMM server.
12 On A, delete the database files and configuration files:
EMM_DATA.db
EMM_INDEX.db
NBDB.db
NBDB.log
NBDB.m.log (optional)
13 On A:
■ If BMRDB does not exist on A, delete the following configuration files:
721
Moving the NetBackup database from one host to another
dataDirectoryA/vxdbms.conf
/usr/openv/var/global/databases.conf
/usr/openv/var/global/server.conf
Remove the VXDBMS_NB_DATA entry from the bp.conf file.
■ If BMRDB exists on A, execute the following command on A so that
BMRDB starts automatically when the server is started:
/usr/openv/db/bin/nbdb_admin -auto_start BMRDB
14 Start NetBackup on B:
/usr/openv/netbackup/bin/bp.start_all
15 Start NetBackup on all master servers and media servers that use B as the
EMM server:
/usr/openv/netbackup/bin/bp.start_all
NetBackup media
Directly-attached disks server
■ Data mover: An entity that moves data between the primary storage (the
NetBackup client) and the storage server. In AdvancedDisk, NetBackup
media servers function as data movers.
■ Storage server: An entity that writes data to and reads data from the disk
storage. A storage server is the entity that has a mount on the file system on
the storage. In AdvancedDisk, NetBackup media servers function as both
storage servers and data movers.
■ Disk volume: A logical unit of disk storage.
■ Disk pool: A collection of disk volumes that are administered as an entity.
Licensing AdvancedDisk
No special installation is required for the NetBackup components of
AdvancedDisk. However:
■ The NetBackup master server and all NetBackup media servers that use the
feature must be at NetBackup 6.5 or later.
■ You must activate the feature by entering the Flexible Disk Option license
key on the NetBackup master server.
You may have one license key that activates NetBackup and all of your add-on
products. Alternatively, you may have a separate license key for NetBackup and
for each add-on product such as AdvancedDisk.
If you remove the Flexible Disk Option license key or if it expires:
■ You cannot create the disk pools or the storage units that reference
AdvancedDisk disk pools.
■ NetBackup jobs that attempt to use the disk pools or the storage units that
are based on disk pools fail. The error message indicates that the feature is
not licensed.
■ NetBackup does not delete the disk pools or the storage units that reference
the disk pools. You can use them again if you enter a valid license key.
storage server the NetBackup media server host in which the disks are installed.
The storage server owns exclusive access to the storage.
If the media server does not appear in the command output as an AdvancedDisk
storage server, configure the media server as a storage server.
NetBackup assumes exclusive ownership of the disk resources that comprise the
disk pool. If you share those resources with other users, NetBackup cannot
The Disk Pool Configuration Wizard lets you create a storage unit; therefore,
you may have created a storage unit when you created a disk pool. To determine
if storage units exist for the disk pool, see the NetBackup Management >
page 730.
All disk pools of the specified Disk type appear in the Disk pool list. If no disk
729
Creating a storage unit
Media server
The Media server setting specifies the NetBackup media server that moves data
to and from the storage server. Only the NetBackup media server that is
configured as the storage server can move data to and from the disk pool.
NetBackup selects the media server to use when the policy runs.
The Maximum concurrent jobs setting specifies the maximum number of jobs
that NetBackup can send to a disk storage unit at one time. (Default: 1 job. The
job count can range from 0 to 256.) This setting corresponds to the Maximum
NetBackup queues jobs until the storage unit is available. If three backup jobs
are ready to be sent to the storage unit and Maximum concurrent jobs is set to
two, the first two jobs start and the third job waits. If a job contains multiple
copies, each copy applies toward the Maximum concurrent jobs count.
The number to enter depends on the available disk space and the server's ability
You can use maximum concurrent jobs to balance the load between disk storage
units. A higher number of concurrent jobs means that the disk can be busier
For information about how NetBackup balances storage unit and media server
load, see “Maximum concurrent jobs” in NetBackup Administrator’s Guide for
UNIX and Linux, Volume I.
Maximum fragment size
Specify the largest fragment size that NetBackup can create to store backups.
The default maximum fragment size for a disk storage unit is 524,287
megabytes. To specify a maximum fragment size other than the default, enter a
Backups to disk are usually fragmented to ensure that the backup does not
restarts from the beginning, not from the fragment where the error occurred.
(An exception is for backups for which checkpoint and restart is enabled. In that
case, fragments before and including the last checkpoint are retained; the
730
Creating a storage unit
Usage recommendations
For usage recommendations, see the following:
■ Create a backup policy for the regular clients and select the STU-NORMAL
storage unit.
The high water mark is a threshold that indicates the storage is full. It
applies to both the individual disk volumes in the pool and the disk pool, as
follows:
■ Individual volumes. When a disk volume reaches the high water mark,
NetBackup writes the data to another disk volume in the pool.
■ Disk pool. When all volumes are at the high water mark, the disk pool is
full. When a disk pool approaches the high water mark, NetBackup
reduces the number of jobs that are allowed to write to the pool.
NetBackup does not assign new jobs to a storage unit in which the disk
pool is full.
■ The low water mark for the disk pool. (The default is 80%.)
When the capacity of the disk pool returns to the low water mark,
NetBackup again assigns jobs to the storage unit. Capacity is regained as
backup images expire.
The low water mark setting cannot be greater than or equal to the high
water mark setting.
Note: Be careful when you add volumes to a disk pool. For data integrity,
NetBackup does not allow volumes to be deleted from a disk pool. Because
backup images may span disk volumes, a volume may contain valid image
fragments. To remove a disk volume, you must delete all valid backup images
and then delete the disk pool.
/usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate
If backup jobs are assigned to a disk pool, the state change fails. Cancel the
backup jobs or wait until the jobs complete.
3 Merge the disk pools. The following is the command syntax. The primary
disk pool is the one you want to retain; nbdevconfig deletes the secondary
disk pool after the merge.
/usr/openv/netbackup/bin/admincmd/nbdevconfig –mergedps -stype
disk_pool_name
4 Change the state of the primary disk pool to UP. The following is the
command syntax:
/usr/openv/netbackup/bin/admincmd/nbdevconfig/nbdevconfig
or volume.
To change the state to DOWN, the disk pool must not be busy. If backup jobs are
assigned to the disk pool, the state change fails. Cancel the backup jobs or wait
Note: For data integrity, NetBackup does not allow volumes to be deleted from a
disk pool. Because backup images may span disk volumes, a volume may contain
valid image fragments. To remove a disk volume, you must delete all valid
backup images and then delete the disk pool.
735
Managing disk pools
2 Change the disk volume state; the following is the command syntax:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate
state is UP or DOWN.
NetBackup jobs still read from and write to a disk pool that has a downed
NetBackup updates the catalog records to show the correct location of the
Prerequisites:
■ The volumes in the two disk pools must have unique names.
■ If the secondary disk pool is referenced by storage units, you must delete
those storage units.
If backup jobs are assigned to a disk pool, the state change fails. Cancel the
backup jobs or wait until the jobs complete.
2 Merge the disk pools. The following is the command syntax. The primary
disk pool is the one you want to retain; nbdevconfig deletes the secondary
disk pool after the merge.
/usr/openv/netbackup/bin/admincmd/nbdevconfig –mergedps –stype
disk_pool_name
3 Change the state of the primary disk pool to UP. The following is the
command syntax:
/usr/openv/netbackup/bin/admincmd/nbdevconfig -changestate
If a disk pool is the storage destination of a storage unit, you must first delete
736
Managing disk pools
Caution: Do not delete a disk pool that contains unexpired NetBackup images; if
you do, data loss may occur.
For more information, see NetBackup Commands for UNIX and Linux.
Option Description
-dv disk_volume Used with -listdv, it shows the properties of the specified disk
volume.
-l Produces the parsable output, one line of output per disk volume
with no headers. The first field indicates the version of the output
as an aid to create scripts. By default, nbdevquery uses the -l
option.
Option Description
-stype server_type Use this option with the following two options:
■ With -listdp, shows all disk pools of the specified storage
type.
■ With -listdv, shows all disk pools of the specified storage
type and their disk volumes.
Use AdvancedDisk for the server_type argument.
If the media server does not appear in the command output as an AdvancedDisk
storage server, configure the media server as a storage server.
738
Monitoring storage capacity and usage
Option Description
-stype server_type Use this option with the following two options:
■ With -liststs, shows all storage servers of the
specified storage type.
■ With -storage_server, shows all storage servers that
are at the specified host.
Use AdvancedDisk for the storage server type (-stype).
For usage information, see NetBackup Commands for UNIX and Linux.
■ The NetBackup Disk Pool status report. For more information, see “Disk
Reports” on page 79.
■ Media and Device Management > Devices > Disk Pools.
■ The NetBackup License Keys dialog box. Open the dialog box by selecting
Help > License Keys in the NetBackup Administration Console. Display the
summary by clicking Summary of active capacity-based license features.
The summary displays the storage capacity for which you are licensed and
the capacity used. It does not display the amount of physical storage space.
The NetBackup Operations Manager also provides information about storage
capacity and usage. For more information, see the NetBackup Operations
Manager Guide.
Troubleshooting AdvancedDisk
The following may help you troubleshoot AdvancedDisk.
-stype AdvancedDisk -U
Disk failure
If recovery mechanisms do not protect a disk that fails, the backup images on
that disk are lost. Operating system read and write errors may occur for the
volume that represents the disk. NetBackup cannot use that volume because of
the errors, and NetBackup jobs may fail.
To prevent NetBackup from trying to read from or write to the disk, you must
change the volume state to DOWN in NetBackup. If the volume represents other
disks that still function, those disks are not available because the volume state is
DOWN. You may be able to read from the volume by mounting it manually, in
which case you may be able to recover image fragments from any disks that did
not fail.
If you replace a failed disk, you can use the same mount point for the
replacement disk. Change the volume state to UP, and NetBackup uses that
volume again.
Any valid backup images on that volume are available for restores.
Appendix C
NearStore storage units
This document contains information about how to administer Network
Appliance (NetApp) NearStoreTM disk storage units using NetBackup 6.5. This
feature is also known as the SnapVault® for NetBackup solution. The NearStore
disk storage unit features introduced in this version are available on all
supported media server platforms.
This document contains the following sections:
■ “Required software, hardware, and licenses” on page 742
For general disk storage unit setup information, see Chapter 5 in this guide. See
the Data ONTAP System Administrator’s Guide for more information about any
Data ONTAP: The NetApp storage operating system provides unified data
sharing setting are enabled. NetApp also refers to this mode as context-aware
SIS.
The file system export mode adds functionality to the space optimized image
mode by enabling a file system export of the backup image. Mount the backup
image as a file system, drag-and-drop or copy files to restore location.
image mode: This mode is in effect when neither Enable block sharing or Enable
file system export are selected in the storage unit dialog box. In the image mode,
the disk storage unit acts much like a BasicDisk storage unit in how data is
stored.
qtree (quota tree): A subdirectory in a NearStore volume that acts as a virtual
subvolume with special attributes, primarily quotas and permissions.
snapshot: A read-only, point-in-time copy of the entire file volume. A snapshot
captures file modifications without duplicating file contents.
SnapVault: Allows exports of snapshot copies to another NetApp system,
providing an incremental block-level backup solution.
space optimized image mode: The space optimized image mode is in effect when
the Enable block sharing setting is enabled in the NearStore disk storage unit
dialog. This mode makes use of single-instance store (SIS) without the additional
requirement of managing snapshots. NetApp also refers to this mode as context
independent SIS or advanced single instance store. To use this mode, the
nearstore_asis1 license must be turned on for each volume.
WAFL (Write Anywhere File Layout): The file system used in all NetApp storage
servers. WAFL supports snapshot creation.
Upgrade considerations
To use the file system export mode or the space optimized image mode, both
NetBackup 6.0 MP4 and ONTAP 7.2 (or later) are required.
Use the snapvault snap unsched command to turn off the SnapVault
schedule for a set of snapshots and stop the snapshot process for the
SnapVault secondary storage system.
745
NearStore disk storage unit advantages
Note: The snapvault snap unsched command does not end the
SnapVault relationships between the secondary system qtrees and their
platform source drives or directories. To do so, run the snapvault stop
command for each qtree configured or existing on the volume to be used as
a NearStore disk storage unit.
■ A NearStore disk storage unit with the file system export option enabled
does not support user backups. NetBackup does not collect True Image
Restore information for user backups, and the file system export mode
requires that TIR information be collected. For more information, see
“Collect true image restore information” on page 108.
■ A NearStore disk storage unit with the file system export option enabled
does not support hot catalog backups. Hot catalog backups rely, in part, on
the user backup process that does not collect TIR information.
■ NearStore disk storage units cannot be included in storage unit groups.
■ NearStore disk storage units cannot operate in conjunction with the
clustering functionality in ONTAP 7.2 or earlier. Clustering is turned on by
default on some filers. To allow NearStore functionality, remove the
clustering license and reboot the filer.
747
NearStore configuration
■ NearStore disk storage units offer partial support for basic disk staging:
NearStore configuration
To make the SnapVault storage unit available for backups, add, enable, and
configure SnapVault on the secondary filer. Run the following commands on the
secondary filer:
2 Enable SnapVault:
options snapvault.enable on
3 Grant access to the primary filer and to the media servers authorized to
access the NearStore system by entering the following command:
options snapvault.access host=nbu_media_server1,
nbu_media_server2...
NearStore authentication
A NearStore user name and password must be configured in NetBackup before
the storage unit is created. NearStore authentication information is stored in
the NetBackup Enterprise Media Manager (EMM) database.
3 In the dialog box, provide the name of the secondary host. Click OK.
4 Specify the credentials on the NDMP host. Use global credentials or
credentials specific to this host.
Credentials can also be configured using the tpconfig command.
To verify that the NearStore credentials have been entered into the
NetBackup EMM database
Once the tpconfig command is run, ensure that the media server is
authenticated by running the following command:
nbemmcmd -listhosts -list_snap_vault_filers -machinename
media_server_name
For example:
749
NearStore configuration
C:\Program Files\VERITAS\NetBackup\bin\admincmd>
NBEMMCMD, Version:6.0CA(20050628)
ndmp mmnetapp.xxx.yyy.com
750
NearStore disk storage unit properties
On demand only
A NearStore disk storage unit can only be used on demand. On demand only
cannot be deselected.
751
NearStore disk storage unit properties
Disk type
Depending on what is licensed, there are a number of disk types available from
which to choose. To configure a NearStore storage unit, select NearStore.
NearStore server
The NearStore server drop-down list contains all NearStore hosts configured
and authenticated for the selected media server and available to NetBackup.
Properties button
Click the Properties button to display:
■ Volume capacity: The total capacity of the volumes on the NearStore unit.
■ Available space: The storage currently available for use on the NearStore
unit.
■ % Full: The storage that is currently in use on the NearStore unit.
Note: The 7.2 ONTAP kernel enforces a limit of 255 snapshots per volume and
200 volumes per NearStore.
Image mode
To select Enable temporary staging area (used for basic disk staging), both
Enable block sharing and Enable file system export must not be selected. In this
way, the NearStore is storing the backup using the image mode. Using this
mode, the client’s tar stream is passed to the NearStore without additional
information. Since the ONTAP kernel cannot read NetBackup’s tar format, only
basic NetBackup operations can be performed, not SIS.
Disk consumption
Snapshot creation consumes a large amount of disk space. NetBackup prepares
for this space requirement by reserving 20% of the disk space on the volume to
be used exclusively for the snapshot, and not for the active file system.
If the snapshots exceed the reserved amount, space is consumed as needed from
the active file system. The active file system cannot, however, consume disk
space reserved for snapshots.
Using the NearStore disk storage unit for more than one purpose
The volume properties of the NearStore storage unit display a value for the
storage available on the volume. A volume designated for NearStore storage
should be used exclusively for NetBackup. (See “NearStore disk storage units
and SnapVault storage units cannot share volumes” on page 744.)
755
Disaster recovery using volume SnapMirror on NearStore disk storage units
Mediaserver1 Mediaserver2
There are two basic disaster recovery scenarios for the voulmes on NearStore A:
■ The volumes on NearStoreA are unrecoverable.
If the volumes on NearStoreA have been destroyed and cannot be
recovered, the SnapMirror relationship must be manually broken, making
the replicated volumes on NearStoreB read- and write-enabled.
For each replicated volume on each media server, an entry is added in the
NetBackup bp.conf file (UNIX) or registry (Windows) that instructs
NetBackup to redirect restores, verifications, and deletions to the replicated
copy. The bpstsinfo command provides a check to identify any images
that were not replicated before the failure. After the failover, storage units
must be altered so that future backups go to volumes on the failover
NearStore.
■ The volumes on NearStoreA are recoverable.
If the volumes have not been destroyed but were temporarily unavailable,
all data backed up to NearStoreB, while NearStoreA was unavailable, can be
transferred back to NearStoreA. NetBackup can then be reconfigured to
direct restores, verifications, deletions, and backups to NearStoreA again.
Initial configuration
As in any NetBackup environment, configure NearStore storage units, create
NetBackup backup policies, and configure catalog backups.
757
Disaster recovery using volume SnapMirror on NearStore disk storage units
The following steps describe how to position NearStoreB so that it handles all
ConcurrentVersion\Config
Failover examples
The examples in the following sections are based on the environment in the
Figure C-2 on page 756.
Example 1
NearStoreA is unavailable, and NearStoreB is configured as the new NearStore
disk storage unit.
Mediaserver1 Mediaserver2
2 Change the configuration for each volume that was being failed over.
■ On each UNIX media server:
759
Disaster recovery using volume SnapMirror on NearStore disk storage units
NearStoreB:/vol/volume1
NearStoreB:/vol/volume2
The command displays differences between the contents on the catalog, and
/usr/openv/netbackup/bin/admincmd/bpstsinfo -comparedbandstu
■ No discrepancies
If no discrepancies exist between the images in the catalog and the images
on the NearStore volume, no images are listed in the output. The output
contains only debug logging:
STS: STH_ESDEBUG: comparedbandstu: libsts openp() 06/09/12
■ With discrepancies
The output contains additional information if mismatches are found. A
mismatch can exist if, for example, one image did not get replicated to
NearStoreB before NearStoreA went down.
STS: STH_ESDEBUG: comparedbandstu: libsts openp() 06/09/12
760
Disaster recovery using volume SnapMirror on NearStore disk storage units
ONLY IN CATALOG
imagename:mediaserver1_1157990060 policy:powerpoint_backup
ONLY IN CATALOG
Note: Two images are listed but they represent only one backup. There are
separate files for the header and the actual backup data. If this backup had
been enabled for True Image Restore, there would have been three images
printed out. To tell if the images are part of the same backup, look at the
imagename field. In the example, both listings have the same image name,
which indicates that they’re part of the same backup.
The entries for this image must be removed from the NetBackup catalog
bpexpdate.
/usr/openv/netbackup/bin/admincmd/bpexpdate -backupid
mediaserver1_1157990060 -d 0
Snapmirror is on.
Source: NearStoreA:volume1
Destination: NearStoreB:volume1
Status: Idle
Progress:
State: Broken-off
Lag: 00:05:28
Contents: Replica
Example 2
NearStoreA is taken down for maintenance and NearStoreB is configured as the
new NearStore disk storage unit. The administrator performs the steps outlined
in “Example 1” on page 758, to enable NearStoreB as the new temporary disk
storage unit.
When NearStoreA is back online the administrator wants to use it again as the
disk storage unit. All data backed up to NearStoreB while NearStoreA was
unavailable must be transferred to NearStoreA before re-enabling NearStoreA
as the disk storage unit.
Follow these steps to transfer data from NearStoreB to NearStoreA and use it as
the disk storage unit for NetBackup:
1 Resync the volume(s) from NearStoreB back to NearStoreA.
NearStoreA> snapmirror resync -S NearStoreB:volume1 volume1
To resync the volumes may return a message similar to the following, and
fail the resync operation:
The resync base snapshot will be:
NearStoreA(0101179629)_volume1.4
These older snapshots have already been deleted from the source
NearStoreB(0101178726)_volume1.20699
NearStoreB(0101178726)_volume1.20698
Transfer started.
[snapmirror.dst.snapDelErr:error]: Snapshot
If such a case occurs, use the following steps to resolve this issue:
a The SnapMirror resync operation replicated the volume, so break the
replica by issuing a snapmirror break:
NearStoreB> snapmirror break volume1
b Manually delete the snapshot copy in question:
NearStoreB> snap delete volume1
NearStoreB(0101178726)_volume1.20699
Change the bp.conf entry for each volume to redirect access of backups
NEARSTORE_FAILOVER_SERVER = NearStoreB:/vol/volume1
NearStoreA:/vol/volume1
NearStoreA:/vol/volume2
Value).
location:
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\
ConcurrentVersion\Config
9 Reconfigure the disk storage units that were originally configured to the
volumes on NearStoreB. Point the disk storage units to the disk storage units
on NearStoreA using the following command:
/usr/openv/netbackup/bin/admincmd/bpsturep -label <storage unit
764
Troubleshooting
Troubleshooting
progress logs.
On the NearStore, the root volume contains a NetBackup-specific log file that
filesystem. (STS_EEFSCHK)
766
Troubleshooting
Appendix D
Exporting PureDisk data to
NetBackup
NetBackup allows the export of PureDisk backups of Files and Folders data
selections to NetBackup. NetBackup can then create copies of the data in
NetBackup file format on NetBackup-supported media for possible disaster
recovery purposes.
Requirements to restore
To restore data selections from NetBackup, the following software is required:
■ NetBackup 6.0 MP5 client software
■ NetBackup 6.5 or 6.0 MP5 server software.
As part of the policy creation, note that a NetBackup policy name is entered on
the Parameters tab in the export policy. This is the NetBackup DataStore type
Select the
DataStore policy
type
■ Clients tab
In the Clients tab, add the name of the PureDisk export agent(s).
(Multiple PureDisk export agents can indicate the same NetBackup
DataStore policy. Add the export agents in the Clients tab as needed.)
Do not include the name of the originating PureDisk clients.
■ Backup Selections tab
No entries are required on the Backup Selections tab.
5 Save and close the policy.
Although the NetBackup job runs as a DataStore policy type, the job is
cataloged as a PureDisk-Export policy type under the name of the PureDisk
agent.
Select PureDisk-Export
as the policy type
Restore support
NetBackup can restore only what PureDisk supports as part of its backups. For
example, PureDisk does not provide access control list (ACL) support beyond
UNIX file or directory permissions, so NetBackup cannot restore ACLs. See the
PureDisk documentation for complete details.
Additional comments on restores:
■ While Windows and UNIX security information can be restored, one
limitation exists regarding restores to an alternate client for UNIX files:
NetBackup backs up both the user ID and user name, but PureDisk backs up
only the user ID. In non-PureDisk export backups, during a restore to an
alternate client, a user name can map to a different user ID. NetBackup
performs a search for the user name and changes the user ID appropriately.
For PureDisk export backups this ability is lost, since the user name is not
available. Files that are restored could belong to a different user.
■ Windows files can be restored to UNIX systems and UNIX files can be
restored to Windows systems. However, security information is lost when
restoring Windows file to UNIX.
772
Logging information
Standard debugging techniques apply to both PureDisk and NetBackup portion.
The VxBSA debug log is written to the pdexport directory.
Index
administrator
nonroot 658
Absolute pathname
All log entries report 76, 383, 384
property 480
browse property 386
Access Control
restore property 386
host properties
Allow multiple data streams
authorization 365
449
NetBackup 654
Allow server file writes property 364, 480
Activity Monitor
properties 460
bpdbjobs command 70
Always property in Fibre Transport host
BPDBJOBS_OPTIONS environmental
properties 423
variable 69
Announce DHCP interval property 455
killing jobs 52
archive bit 120, 202, 403, 405
monitoring jobs 51
assigned volumes 533
suspending a job 52
description 656
Reader) 376
Authentication
Reader) 376
service 61
774
Authorization
frequency
host properties
effect on priority 130
DomainGroup 374
guidelines for setting 129
Group/Domain 374
setting 129
Host 374
full 119
User 373
importing 336
Service 61
policy management window 82
automatic
Status of Backups report 76
backups 121
types of 119
cumulative incremental
user directed
backups 121
schedules 151
host properties
Bandwidth 378
host properties
To IP address 378
backups
Final destination media owner 250
activating policy 99
Final destination storage unit 250
application 121
Final destination volume pool 250
archive 120
priority of duplication jobs 135
automatic 121
relocation schedule 119, 239, 249
full 121
selection within a storage unit group 273
Vault 122
size recommendations 245
deactivating policy 99
Use alternate read server attribute 135, 251
duplicating 330
775
Server) 58
bpjava-susvc service 63
BMRDB.db
bpjobd process 63
in catalog 280
BPRD
relocating 699
logging property 443
bp.conf file
NetBackup Request Manager, description 59
BPARCHIVE_POLICY 152
Busy action property 382
BPARCHIVE_SCHED 152
Busy file
BPBACKUP_POLICY 152
Busy file action 382
BPBACKUP_SCHED 152
File action file list 381
C
bpcd daemon 62
cachefs file systems, excluding from backup 195
bpcompatd process 62
canceling uncompleted jobs 52
bpdbjobs
catalog archiving
command 70
bpcatlist command 321
debug log 70
bpcatres command 322
BPDBM
deactiving policy for 99
bpdbm process 62
bpcatarc 322
bpend 476
bpcatres 322
bpcatrm 322
776
overview 318
and synthetic backups 210
configuration 296
State 683
file paths
resuming a restore job 683
media
tape
ID 309
change cleanings allowed 519
server 307
set count 514
type 308
Clean-up
volume pool 93
Keep vault logs 383
overview 276
Move backup job from incomplete state to
uncompressing 357
Client attributes
catarc schedule 83
Allow client browse 386
changing
Client cipher property 410
777
database 387
policy attribute 179
D
moving image catalog 354
Daemon connection port property 426, 427
name 673
Daemon port only property (for selection of
peername 673
ports) 428
secure 162
daemons
Restore 108
Daily windows setting 149
compression, by software
selection in policy 90, 91, 137
advantages 106
database manager process (bpdbm) 62
disadvantages 106
database-extension clients, adding file paths
specifications 106
for 185
concurrent jobs
databases, NetBackup (see catalog backups)
on client 436
DataStore
per policy 97
policy type 89
configuring
volume pool 93
media 508
DB2 policy type 89, 122
CONNECT_OPTIONS 427
deassign volumes 533
examples 104
volume pools 542
volumes 532
778
device
down a device 501
character 608
drive
discovery 596
add comment 504
no rewind 614
cleaning 502, 503, 607
device host
no rewind device 614
Device Monitor 67
robot library, controlling drive 610
DISABLE_STANDALONE_DRIVE_EXTENSIONS 50
disaster recovery
E
collect information for 103, 108
E-mail
information 438
disaster recovery 197
tab 196
send from server 481
disk
EMM database 281
consumption 753
empty media access port prior to update 550
logs report 79
Enable block sharing storage unit setting 229, 751
pools 222
Enable encryption property 410
779
Encryption
failover
host properties
Fibre Transport
Enable standard encryption 410
host properties
Always 423
connections 423
Never 423
Preferred 422
configuration 423
file lists
escape character
on UNIX 633
NetWare clients
Exchange
nontarget 183
host properties
target 185
attachments 413
restore 413
exclude
files
.SeCuRiTy.nnnn 681
on client 419
/.rhosts 160
overview 195
Exclude list
for catalog backup 312
host properties
NOTES.INI 445
peername 675
export
filters, applying 51
Final destination
Solaris 9 177
external_types.txt 710
Firewalls
780
host properties
goodies directory 687
H
Ports 425, 427
hard links
notes on use
exporting 361
FORCE_IPADDR_LOOKUP 662
I
duplicating 330
General server
on disk report 79
host properties
on media report 76
restores 432
Incrementals based on
Global attributes
archive bit property 405
host properties
timestamp property 405
conflict 596
Inline copy option 131, 330, 333, 334
781
on PC clients 162
L
on secure clients 162
label
Instant Recovery
license keys
accessing 635
660
deleting 637
export 637
printing 636
Java
viewing the properties of one key 637
directory 657
links
interface 34
UNIX hard-linked directories 178
jobs
logical storage unit (LSU) attributes 753
filters, specifying 51
Lotus Notes
maximum
host properties
per policy 97
Path 445
K
Keep logs property 74, 383, 384
M
Keep status of user-directed backups, archives, and
Mac OS X 89
property 384
Disaster Recovery attachment, sending 197
KEEP_LOGS_DAYS 666
Windows nbmail.cmd script 438
killing jobs 52
property 413
manual backups
782
MAX_KB_SIZE_PER_DUPLICATION_JOB 264
suspend 521
MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATIO
type for new volume 515
N_JOB 264
type when not an API robot 556
maximum
unfreeze 520
mounts
failover machine list 460
media
Megabytes of memory property 398
active 78
Microsoft Volume Shadow Copy Service (VSS) 392
freeze 520
MIN_KB_SIZE_PER_DUPLICATION_JOB 264
host properties
monitoring NetBackup processes 66
mount
volume group 542
errors, canceled 67
volumes
errors, queued 67
logical move 524
nonactive 78
update volume configuration 525
recycling 537
MS-Exchange policy type 89
783
mtime 182
nbstserv process 64
multiple copies
nbsvcmon process 64
setting 131
NCR-Teradata policy type 89
tuning 114
host storage unit setting 235
multiplexing (MPX)
policy type 89
NBDB.db
NetBackup
in catalog 280
request service port (BPRD) 454
relocating 699
NetBackup Access Control (NBAC)
Manager) 59, 63
use of 479, 666
nbEvtMgr process 63
NetBackup Compatibility Service (BPCOMPATD) 59
nbftsrvr process 63
NetBackup Database Manager (BPDBM) 59
nbj.conf 660
NetBackup Device Manager (ltid) 59
NBJAVA_CLIENT_PORT_WINDOW 664
NetBackup for MS-Exchange 185
NBJAVA_CONNECT_OPTION 665
NetBackup Job Manager (NBJM) 59, 444
NBJAVA_CORBA_DEFAULT_TIMEOUT 665
NetBackup Monitor Service 60
NBJAVA_CORBA_LONG_TIMEOUT 665
NetBackup Operations Manager (NOM) 60
64, 444
Service (NBRMMS) 59
nbproxy process 64
NetBackup Request Manager (BPRD) 59
nbrb process 64
property 454
784
NETBACKUP_RELATIONAL_DATABASE_FILES
Override policy
NetWare client
Overwrite existing files 182
host properties
P
archives, and restores 396
parent jobs 56, 112
network
parent_start_notify script 56
host properties
parent_start_notify script 56
(BPRD) 454
setting (Lotus Notes) 445
properties 423
PBX (Symantec Private Branch Exchange) 66
nonactive media 78
Perform
applications 658
to change NetBackup properties 364
policies
O activating 99
785
example 153
prelabel media 510, 521
overview 81
preprocess interval 191
planning 154
preview volume configuration update 550
setting priority 98
primary copy
policy type
device configuration 623
AFS 90
job list information 53
DataStore 89
license key 636
DB2 89
Prioritized storage unit selection in group 267
FlashBackup 90
priority
FlashBackup Windows 90
of a job 98
Informix 90
of duplication jobs 135
Lotus-Notes 89
of relocation jobs started from this schedule
MS-Exchange 89
setting 250
MS-SharePoint 90
of restore jobs property 436
MS-SQL-Server 89
Private Branch Exchange 61, 66
MS-Windows-NT 89
Problems report 76, 383, 384
NBU-Catalog 89
proc file system, excluding from backups 195
NCR-Teradata 89
Process busy files property 381
NDMP 89
processes
NetWare 89
check with vmps 635
Oracle 89
monitoring 66
SAP 90
show active 634
SQL-BackTrack 90
properties
Standard 89
changing on multiple hosts 363
Sybase 90
exporting 361
Vault 89
overview 361
Port Ranges
Storage Option 224, 229
host properties
Storage Pool Authority (SPA) 229
Q
Server reserved port window 458
quick erase 529
458
quotas on file systems 222
ports
R
allowing operating system to select non
random ports, setting on server 457
properties 422
restoring 172
786
remote
restores
reports
redirected 459, 673, 675
Console 72
symbolic links on UNIX 177
Problems report 76
changing 463
running a report 72
expiration 152
requests
Retention type in lifecycle
assigning 499
Expire after duplication 262
denying 501
Fixed 260
overview 498
Retries allowed after runday policy setting 128
resubmitting 501
Retry count property 382
reset
retry restores, setting 477
restarting jobs 52
destination for move volume 527
Restore Failover
device file 601
host properties
device host 599
787
library 610
pass-through command 589, 596
number 601
persistent reserve 448
type 602
reserve, configuring 447
server
administration, backlevel 38
schedules
EMM server 280, 281
frequency 129
rebooting 633
windows 149
sends mail property 481
naming 118
setconf.bat file 660
overview 117
using 392
priority 130
shared drives
retention periods
drive operating mode 496, 497, 503
guidelines 138
SharedDisk
setting 138
host properties
scratch
show robot contents 551
volume pool 93
single file
scripts 56
layout for NetBackup catalogs 278
bpdbjobs example 69
restore program, FlashBackup 177
bpps 634
Single-Instance Storage (SIS) 96, 106, 108, 261, 413,
goodies 687
742, 752
vmps 635
788
slot number
changing server to manage 639
Snapshot Client 56, 90, 96, 116, 131, 185, 224, 229,
creation overview 216
392, 484
deleting 218, 219
744
disk storage units 222
staging
Media Manager type 220
71 163
OpenStorage disk type 223
dialog 137
SharedDisk disk type 224
optional LIFECYCLE_PARAMETERS
subnets and bandwidth limiting 377
configuration 264
Sun PC NetLink 177
operations 265
Sybase Adaptive Server Anywhere (ASA)
storage unit
starting/stopping ASA service 705
storage units
Authorization 45, 61
789
UNIX 177
tpconfig menus 605
synthetic backups
tpext utility 711
full 203
using in Activity Monitor 53
schedules 128
Error code 136 209
System State
move detection 109
backups 96
no NetBackup change journal support 404
directive 186
pruning information 209
restoring 684
with Move Detection 209
tshd daemon 65
T
tape
library
files before backing up property 396
lists report 78
Universal
logs report 77
host properties
summary report 78
Use preferred group for enhanced
written report 78
authorization 479
TapeAlert 608
settings properties 477
method 96
Keep status of user-directed backups,
Timeouts
Megabytes of memory 398
host properties
primary node in tree 482
tlmd daemon 65
usbdevfs file system, excluding from backup 195
790
property 423
vmscd
property 432
VMWare Proxy Servers host properties 484
property 479
Volume Configuration wizard 511
property 398
moving 542
USE_CTIME_FOR_INCREMENTALS 695
volume is in a robotic library
USE_NBJAUTH_WITH_ENHAUTH 666
for move volume 527
user
for new volume 516
backups 120
add volume 516
schedules
adding 539
planning 151
CatalogBackup 93
DataStore 93
V
DataStore pool 516, 519
Vault
deleting 542
policy
Volume Snapshot Provider (VSP)
creating 199
backups using Checkpoint restart 96
type 89
directory for logging messages 487
verifying backup
volumes
images 327
adding 508
Exchange) 66
assignments 93
vm.conf file
deleting (see deleting)
791
moving 524
Enable Windows Open File backups for
recycling 537
Global drive snapshot 393
replacing 535
Individual drive snapshot 393
scratch 93
Use Microsoft Volume Shadow Copy
Service) 61
Use Veritas Volume Snapshot Provider
Service) 61
Windows Terminal Services 39
VxFS
catalog backup 296
WORM media
W
WAFL qtree
cleaning up 744
wildcard characters
UNIX
Windows client
host properties
792