6.5 Admin Guide 2 (Unix)

Veritas NetBackup™
Administrator’s Guide, Volume II
for UNIX and Linux
Release 6.5
12308278
Veritas
NetBackup Administrator’s Guide, Volume II
Copyright © 1993-2007 Symantec Corporation. All rights reserved.
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.
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.
The Licensed Software and Documentation are deemed to be “commercial computer

software” and “commercial computer software documentation” as defined in FAR
Sections 12.212 and DFARS Section 227.7202.
Symantec Corporation
20330 Stevens Creek Blvd.
Cupertino, CA 95014
www.symantec.com
Printed in the United States of America.

Third-party legal notices
Third-party software may be recommended, distributed, embedded, or bundled

with this Veritas product. Such third-party software is licensed separately by its
copyright holder. All third-party copyrights associated with this product are
listed in the accompanying release notes.
Licensing and registration

Veritas NetBackup is a licensed product. See the NetBackup Installation Guide
for license installation instructions.
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 Additional configuration

Multiplexing .........................................................................................................17
When to use multiplexing ...........................................................................18
How to configure multiplexing ..................................................................18
Maximum streams per drive for a storage unit ...............................19
Media multiplexing for a schedule ....................................................19
Other configuration settings to consider using multiplexing ......22
Demultiplexing .............................................................................................23
Using multiple NetBackup master servers ......................................................24
Using multiple media servers with one master server ..................................25
Software on each server ..............................................................................26
NetBackup catalogs .....................................................................................27
Adding a media server .........................................................................................27
Registering a media server .........................................................................29
NetBackup configuration options .....................................................................31
Syntax rules for bp.conf options ...............................................................31
bp.conf options for servers .........................................................................32
ALLOW_MEDIA_OVERWRITE ...........................................................32
ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA ..........................33
ALLOW_NON_RESERVED_PORTS ....................................................33
AUTHENTICATION_DOMAIN ...........................................................33
AUTHORIZATION_SERVICE ..............................................................34
BPBRM_VERBOSE ................................................................................35
BPDBJOBS_COLDEFS ...........................................................................36
BPDBM_VERBOSE ................................................................................38
BPRD_VERBOSE ...................................................................................39
BPTM_VERBOSE ..................................................................................39
BPEND_TIMEOUT ................................................................................40
BPSTART_TIMEOUT ...........................................................................41
CHECK_RESTORE_CLIENT ................................................................41
CLIENT_CONNECT_TIMEOUT ..........................................................41
CLIENT_PORT_WINDOW ...................................................................41
CLIENT_READ_TIMEOUT ..................................................................42
CLIENT_RESERVED_PORT_WINDOW .............................................43
CONNECT_OPTIONS ...........................................................................43
DEFAULT_CONNECT_OPTIONS ......................................................45
DISABLE_JOB_LOGGING .................................................................... 46
DISABLE_STANDALONE_DRIVE_EXTENSIONS ............................ 46
DISALLOW_BACKUPS_SPANNING_MEDIA ................................... 46
DISALLOW_CLIENT_LIST_RESTORE .............................................. 47
DISALLOW_CLIENT_RESTORE ......................................................... 47
EMMSERVER ........................................................................................ 47
ENABLE_ROBUST_LOGGING ............................................................ 48
FAILOVER_RESTORE_MEDIA_SERVERS ........................................ 48
FORCE_RESTORE_MEDIA_SERVER ................................................. 49
GENERATE_ENGLISH_LOGS ............................................................. 49
INCOMPLETE_JOB_CLEAN_INTERVAL ........................................... 50
INITIAL_BROWSE_SEARCH_LIMIT ................................................. 50
LIMIT_BANDWIDTH ........................................................................... 50
MEDIA_ID_PREFIX .............................................................................. 53
MEDIA_UNMOUNT_DELAY .............................................................. 54
MEDIA_REQUEST_DELAY ................................................................. 54
MEDIA_SERVER ................................................................................... 54
MPX_RESTORE_DELAY ...................................................................... 54
MUST_USE_LOCAL_DRIVE ............................................................... 55
NBRB_CLEANUP_OBSOLETE_DBINFO ............................................ 55
NBRB_ENABLE_OPTIMIZATIONS .................................................... 55
NBRB_FORCE_FULL_EVAL ................................................................ 55
NBRB_REEVAL_PENDING ................................................................. 56
NBRB_REEVAL_PERIOD ..................................................................... 56
NBRB_RETRY_DELAY_AFTER_EMM_ERR ..................................... 56
NBRB_MPX_GROUP_UNLOAD_DELAY ........................................... 56
RANDOM_PORTS ................................................................................ 57
RE_READ_INTERVAL ......................................................................... 57
REQUIRED_INTERFACE ..................................................................... 57
REQUIRED_NETWORK ....................................................................... 59
SERVER ................................................................................................. 59
SERVER_PORT_WINDOW ................................................................. 61
SERVER_RESERVED_PORT_WINDOW ........................................... 61
SKIP_RESTORE_TO_SYMLINK_DIR ................................................. 62
SERVER_CONNECT_TIMEOUT ......................................................... 62
UNLINK_ON_OVERWRITE ................................................................ 63
USE_VXSS ............................................................................................. 64
VERBOSE ............................................................................................... 64
VXSS_NETWORK ................................................................................. 64
bp.conf options for UNIX clients ............................................................... 66
ALLOW_NON_RESERVED_PORTS ................................................... 67
AUTHENTICATION_DOMAIN ........................................................... 67
BPARCHIVE_POLICY ........................................................................... 68
BPARCHIVE_SCHED ............................................................................68
BPBACKUP_POLICY .............................................................................68
BPBACKUP_SCHED .............................................................................69
BUSY_FILE_ACTION ...........................................................................69
BUSY_FILE_DIRECTORY ....................................................................69
BUSY_FILE_NOTIFY_USER ................................................................70
BUSY_FILE_PROCESSING ..................................................................70
CLIENT_NAME .....................................................................................70
CLIENT_PORT_WINDOW ...................................................................71
CLIENT_READ_TIMEOUT ..................................................................71
CLIENT_RESERVED_PORT_WINDOW .............................................71
COMPRESS_SUFFIX ............................................................................71
CRYPT_CIPHER ....................................................................................72
CRYPT_KIND ........................................................................................72
CRYPT_OPTION ...................................................................................73
CRYPT_STRENGTH .............................................................................73
CRYPT_LIBPATH .................................................................................74
CRYPT_KEYFILE ..................................................................................74
DISALLOW_SERVER_FILE_WRITES ................................................75
DO_NOT_RESET_FILE_ACCESS_TIME ............................................75
GENERATE_ENGLISH_LOGS .............................................................75
IGNORE_XATTR ...................................................................................76
INFORMIX_HOME ................................................................................76
INITIAL_BROWSE_SEARCH_LIMIT .................................................76
KEEP_DATABASE_COMM_FILE ........................................................76
KEEP_LOGS_DAYS ..............................................................................76
LIST_FILES_TIMEOUT ........................................................................77
LOCKED_FILE_ACTION ......................................................................77
MEDIA_SERVER ...................................................................................77
MEGABYTES_OF_MEMORY ...............................................................78
NFS_ACCESS_TIMEOUT .....................................................................78
RANDOM_PORTS .................................................................................78
RESTORE_RETRIES .............................................................................78
REQUIRED_INTERFACE .....................................................................79
SERVER_PORT_WINDOW ..................................................................79
SERVER ..................................................................................................79
SYBASE_HOME ....................................................................................80
USE_CTIME_FOR_INCREMENTALS .................................................80
USE_FILE_CHG_LOG ...........................................................................80
USE_VXSS .............................................................................................80
USEMAIL ...............................................................................................81
VERBOSE ...............................................................................................81
VXSS_NETWORK .................................................................................81
UNIX client examples .................................................................................. 82
Example /usr/openv/netbackup/bp.conf file .................................. 82
Example $HOME/bp.conf file ............................................................ 82
vm.conf options for media servers ........................................................... 82
ACS_mediatype ......................................................................................83
ACS_SEL_SOCKET ............................................................................... 83
ACS_CSI_HOSTPORT .......................................................................... 83
ACS_SSI_HOSTNAME ......................................................................... 84
ACS_SSI_INET_PORT .......................................................................... 84
ACS_SSI_SOCKET ................................................................................ 85
ACS_TCP_RPCSERVICE / ACS_UDP_RPCSERVICE ........................ 85
ADJ_LSM ............................................................................................... 85
API_BARCODE_RULES ....................................................................... 87
AUTHORIZATION_REQUIRED .......................................................... 87
AUTO_PATH_CORRECTION .............................................................. 88
AUTO_UPDATE_ROBOT .................................................................... 88
AVRD_PEND_DELAY .......................................................................... 88
AVRD_SCAN_DELAY .......................................................................... 89
CLEAN_REQUEST_TIMEOUT ............................................................ 89
CLIENT_PORT_WINDOW ................................................................... 89
CLUSTER_NAME ................................................................................. 90
CONNECT_OPTIONS ........................................................................... 90
DAS_CLIENT ......................................................................................... 91
DAYS_TO_KEEP_LOGS ....................................................................... 91
EMM_RETRY_COUNT ......................................................................... 92
EMM_CONNECT_TIMOUT ................................................................. 92
EMM_REQUEST_TIMOUT ................................................................. 92
ENABLE_ROBOT_AUTH ..................................................................... 92
INVENTORY_FILTER .......................................................................... 93
MAP_ID .................................................................................................. 93
MAP_CONTINUE_TIMEOUT ............................................................. 94
MEDIA_ID_BARCODE_CHARS .......................................................... 94
MEDIA_ID_PREFIX .............................................................................. 95
MM_SERVER_NAME ........................................................................... 95
PREFERRED_GROUP .......................................................................... 96
PREVENT_MEDIA_REMOVAL ........................................................... 96
RANDOM_PORTS ................................................................................ 96
REQUIRED_INTERFACE ..................................................................... 97
SERVER ................................................................................................. 97
SSO_DA_REREGISTER_INTERVAL .................................................. 98
SSO_DA_RETRY_TIMEOUT ............................................................... 98
SSO_HOST_NAME ............................................................................... 98
TLH_mediatype .................................................................................... 98
TLM_mediatype ....................................................................................99
VERBOSE ...............................................................................................99
Example vm.conf file ...........................................................................99
Dynamic host name and IP addressing ............................................................99
Setting up dynamic IP addresses and host names ................................101
Configuring the NetBackup master server ............................................102
Configuring a dynamic Microsoft Windows client ...............................103
Configuring a dynamic UNIX NetBackup client ....................................103
Busy file processing (UNIX clients only) ........................................................105
Getting started ...........................................................................................106
Modifying bp.conf to configure busy file processing ...........................106
BUSY_FILE_PROCESSING ................................................................106
BUSY_FILE_DIRECTORY ..................................................................107
BUSY_FILE_ACTION .........................................................................107
Creating action files ...................................................................................108
Logs directory .............................................................................................109
Modifying bpend_notify_busy .................................................................110
Configuring email notifications ......................................................................111
Specifying the locale of the NetBackup installation ....................................112
Adjusting time zones in the NetBackup-Java console ..................................113
Chapter 2 Menu user interfaces

Using the bpadm NetBackup management utility ........................................118
Data classification management .............................................................118
Defining and managing storage units and storage unit groups .........119
Defining and managing storage unit groups .................................119
Defining and managing policies ..............................................................120
Configuring an online catalog backup ............................................120
Defining NetBackup global attributes ....................................................123
Defining and managing Fibre Channel transport .................................124
Displaying reports .....................................................................................124
Performing manual backups ....................................................................125
Performing special actions .......................................................................126
Install NetBackup on all trusting clients ........................................126
Perform an offline catalog backup ..................................................126
Modifying offline catalog backup settings .....................................127
Performing manual offline catalog backups ..................................130
Redefining retention levels ..............................................................131
Defining and managing server groups ...................................................132
Using the vmadm media management utility ...............................................132
Starting vmadm ..........................................................................................132
Starting and stopping vmd .......................................................................133
The vmadm main menu ............................................................................133
10
Defining and managing volume pools .................................................... 134
Adding volumes ......................................................................................... 134
Auto-populating a robot ................................................................... 135
Displaying the volume configuration ..................................................... 136
Deleting volumes or groups ..................................................................... 136
Moving volumes or a volume group ........................................................ 136
Moving volumes or volume groups ................................................. 137
Changing a volume description ............................................................... 137
Changing a volume's volume pool ...........................................................137
Changing the expiration date for volumes ............................................ 138
Changing the volume group for volumes ............................................... 138
Change Vault attributes of volumes ....................................................... 138
Setting the maximum mounts for volumes ........................................... 139
Modifying the number of cleanings ........................................................ 139
Updating barcodes for selected volumes in a robot ............................. 140
Inventory robots ........................................................................................ 140
Inventory a robot ...............................................................................140
Configuring barcode rules ........................................................................ 143
Formatting optical disks ........................................................................... 143
Using the tpconfig device configuration utility ............................................ 144
Robot number ..................................................................................... 144
Robotic control path .......................................................................... 144
Host name ........................................................................................... 145
No rewind on close device name ...................................................... 145
Character device name ...................................................................... 145
Volume header device name ............................................................ 145
Drive status ......................................................................................... 146
Starting the tpconfig device configuration utility ............................... 146
Adding robots ............................................................................................. 147
Adding drives ............................................................................................. 148
Updating a robot configuration ............................................................... 149
Updating a drive configuration ............................................................... 150
Deleting a drive .......................................................................................... 150
Deleting a robot .......................................................................................... 151
Configuring drive paths ............................................................................ 151
Configuring host credentials ................................................................... 152
Displaying and printing your device configuration ............................. 153
Using the disk configuration utility ............................................................... 153
Managing SharedDisk ...............................................................................154
Managing OpenStorage ............................................................................ 154
Chapter 3 Reference topics

Rules for using host names in NetBackup ..................................................... 158
11
Qualifying host names ..............................................................................158
How NetBackup uses host names ............................................................158
Server and client name on UNIX servers and clients ...................158
Host names on Windows servers and PC clients ...........................159
Policy configuration ..........................................................................159
Image catalog ......................................................................................159
Error catalog .......................................................................................160
Catalog backup information .............................................................160
How to update NetBackup after a host name changes .........................160
Special considerations for Domain Name Service (DNS) .....................161
Reading backup images with tar .....................................................................162
Effects of a non-NetBackup tar ........................................................162
Files that tar generates .....................................................................165
Factors that affect backup time .......................................................................165
Total data ....................................................................................................166
Transfer rate ...............................................................................................166
Compression ...............................................................................................167
Device delays ..............................................................................................167
Determining NetBackup transfer rate ............................................................167
Network transfer rate ................................................................................167
Network transfer plus end-of-backup-processing rate ........................167
Total transfer rate .....................................................................................168
Examples .....................................................................................................168
How NetBackup builds a worklist ....................................................................169
Building the worklist (Queue) ..................................................................169
To prioritize queued jobs ..........................................................................170
Determining backup media requirements .....................................................171
NetBackup notify scripts ..................................................................................172
backup_notify .....................................................................................173
backup_exit_notify ............................................................................173
bpstart_notify (UNIX clients only) ..................................................174
bpstart_notify.bat (Microsoft Windows clients only) ..................176
bpend_notify (UNIX clients only) ....................................................178
bpend_notify.bat (Microsoft Windows clients only) ....................180
bpend_notify_busy (UNIX clients only) ..........................................183
dbbackup_notify .................................................................................183
diskfull_notify ....................................................................................184
mail_dr_info.sh ...................................................................................184
parent_end_notify .............................................................................185
parent_start_notify ............................................................................185
restore_notify .....................................................................................186
session_notify .....................................................................................186
session_start_notify ..........................................................................187
12
userreq_notify .................................................................................... 187
Media and device management best practices .............................................. 187
General practices ....................................................................................... 188
Media management ................................................................................... 188
Device management .................................................................................. 189
Performance and troubleshooting ..........................................................190
Using TapeAlert .................................................................................................190
Requirements for using TapeAlert .........................................................191
TapeAlert log codes ................................................................................... 191
Drive cleaning overview ................................................................................... 194
Reactive cleaning (TapeAlert) .................................................................. 194
TapeAlert cleaning ............................................................................ 195
TapeAlert and frequency-based cleaning ......................................195
Library-based cleaning .............................................................................195
Frequency-based cleaning ........................................................................ 196
Frequency-based cleaning limitations ........................................... 196
Operator-initiated cleaning ..................................................................... 196
Using a cleaning tape ................................................................................ 197
Volume pool and volume group overview ..................................................... 197
Volume pools .............................................................................................. 198
Volume groups ........................................................................................... 198
Rules for assigning volume groups ................................................. 198
Volume pool and volume group example ............................................... 199
Scratch volume pools ................................................................................ 200
Scratch pool example ........................................................................ 200
Scratch pool usage .............................................................................201
Barcode overview ............................................................................................... 202
Barcode advantages ................................................................................... 202
Barcode best practices ..............................................................................202
Barcode rules .............................................................................................. 203
NetBackup actions for barcodes ...................................................... 203
Checking barcodes .............................................................................204
Example barcode rules ...................................................................... 204
Media ID generation rules ........................................................................ 206
Changing your hardware configuration .........................................................206
Replacing devices ....................................................................................... 206
Decommissioning a media server ...........................................................208
How NetBackup selects drives ......................................................................... 210
How NetBackup reserves drives ...................................................................... 211
SCSI persistent reserve process .............................................................. 212
SCSI persistent reserve commands ................................................. 213
SCSI persistent reserve conflicts ..................................................... 213
SPC-2 SCSI reserve process ...................................................................... 213
13
SPC-2 SCSI reserve commands ........................................................214
SCSI reservation conflicts ................................................................215
Forcing a release ................................................................................215
Breaking a reservation ......................................................................216
SCSI reserve requirements and limitations ...........................................216
SCSI reservation logging ..........................................................................217
Server operating system limitations ......................................................218
Checking for data loss ...............................................................................218
Possible data loss causes ...................................................................218
Checking for tape and driver configuration errors ..............................218
Common configuration problems ....................................................219
Configuring SCSI reserve ..........................................................................219
How NetBackup selects media .........................................................................219
Selecting media in robots .........................................................................220
Spanning media ..................................................................................221
Selecting media in stand-alone drives ....................................................221
Media selection using stand-alone drive extensions ....................221
Media formats ....................................................................................................223
Standard tape format ................................................................................224
QIC/WORM tape format ............................................................................224
Optical media format .................................................................................224
Fragmented backups .................................................................................225
Multiplexing format ..................................................................................225
Spanning tapes ...........................................................................................225
Media Manager commands ..............................................................................226
Device discovery overview ...............................................................................228
Device serialization ...................................................................................228
Devices that can be discovered ................................................................229
Device discovery in NetBackup ................................................................229
Device discovery in the Device Configuration Wizard .........................230
Device discovery and shared tape drives ...............................................230
Viewing and verifying the device configuration ...................................231
Adding devices without discovery ...........................................................231
Device mapping file ...................................................................................231
Correlating tape drives to device files or addresses .....................................232
Correlating devices and device files on UNIX hosts .............................232
Correlating devices and names on Windows hosts ..............................233
Tape I/O commands ...........................................................................................235
Requesting tapes ........................................................................................235
drive_mount_notify script ................................................................236
tpreq example .....................................................................................236
Reading and writing tape files .................................................................237
Positioning tape files .........................................................................237
14
Rewinding tape files .......................................................................... 237
Removing tape files ................................................................................... 237
drive_unmount_notify script ...........................................................238
Using an optical disk ................................................................................. 238
External access to Media Manager controlled devices ........................ 239
User error messages .................................................................................. 240
Chapter 4 Using NetBackup with AFS

Installation ......................................................................................................... 241
System requirements ................................................................................ 241
Server and client installation .................................................................. 241
Configuration ..................................................................................................... 241
General policy attributes .......................................................................... 242
Client list ..................................................................................................... 242
Backup selections ...................................................................................... 242
Backup selection list directives ............................................................... 242
Regular expressions .................................................................................. 243
Exclude and include lists .......................................................................... 244
Backups and restores ........................................................................................ 244
Backups ....................................................................................................... 244
Automatic backup ..............................................................................244
Manual backup ................................................................................... 244
Restores ....................................................................................................... 244
Restore from the NetBackup for AFS client .................................. 244
Restore from the NetBackup master server .................................. 245
Notes about restores .......................................................................... 245
Troubleshooting .................................................................................................246
Troubleshooting backups ......................................................................... 246
Troubleshooting restores ......................................................................... 246
Chapter 5 Intelligent Disaster Recovery

Changes for NetBackup 6.0 and later ............................................................. 248
Supported Windows editions ........................................................................... 248
Requirements for IDR ....................................................................................... 249
Overview of IDR use .......................................................................................... 250
About the DR files .............................................................................................. 250
Configuring NetBackup policies for IDR ........................................................ 251
Backing up the protected computer ................................................................ 252
Creating IDR media ........................................................................................... 252
Choosing the bootable media ................................................................... 253
Creating bootable diskettes ...................................................................... 254
To modify diskette sets for use with multiple Windows 2000 computers
15
255
Creating a bootable CD image ..................................................................256
Creating IDR diskettes ..............................................................................257
Updating IDR media ..........................................................................................258
Updating a bootable CD ............................................................................258
Updating bootable diskettes .....................................................................259
Updating IDR diskettes only ....................................................................260
Using drfile.exe to create or update a DR file ........................................260
Recovering your computer ...............................................................................261
Step 1: Boot your computer ......................................................................262
Step 2: Windows setup in IDR recovery .................................................263
Step 3: Disaster recovery wizard .............................................................264
Notes on altering hard drive partition sizes ..........................................267
Notes on recovering specific platforms ..........................................................267
Recovering the dell PowerEdge 6100/200 with RAID ..........................268
Recovering IBM computers ......................................................................268
Recovering Compaq computers ...............................................................269
IDR frequently asked questions ......................................................................269
Index 271
16
Chapter 1
Additional configuration
This chapter explains settings that, in most instances, are optional. The sections
in this chapter include the following:
■ “Multiplexing” on page 17
■ “Using multiple NetBackup master servers” on page 24
■ “Using multiple media servers with one master server” on page 25
■ “Adding a media server” on page 27
■ “NetBackup configuration options” on page 31
■ “Dynamic host name and IP addressing” on page 99
■ “Busy file processing (UNIX clients only)” on page 105
■ “Configuring email notifications” on page 111
■ “Specifying the locale of the NetBackup installation” on page 112
■ “Adjusting time zones in the NetBackup-Java console” on page 113
Multiplexing
NetBackup multiplexing sends concurrent backups from one or several clients
to a single storage device. NetBackup multiplexes the backups sequentially onto
the media. Multiplexed and unmultiplexed backups can reside on the same
volume. Separate volume pools or media IDs are not necessary.
18 Additional configuration
Multiplexing
No special action is required to restore a multiplexed backup. NetBackup finds

the media and restores the requested backup.
Clients
Disk Server
Removable media or
magnetic disk
Disk
Disk
When to use multiplexing

Multiplexing is generally used to reduce the amount of time that is required to
complete backups. The performance in the following situations would be
improved by using multiplexing:
■ Slow clients. Instances in which NetBackup uses software compression,
which normally reduces client performance, are also improved.
■ Multiple slow networks. The parallel data streams take advantage of
whatever network capacity is available.
■ Many short backups (for example, incremental backups). In addition to
providing parallel data streams, multiplexing reduces the time each job
waits for a device to become available. Therefore, the storage device transfer
rate is maximized.
Multiplexing reduces performance on restores because it uses extra time to read
the images.
Note: To reduce the impact of multiplexing on restore times, set the storage unit
maximum fragment size to a value smaller than the largest allowed value. Also,
enable fast-tape positioning (locate block), if it applies to the tape drives in use.
How to configure multiplexing

Multiplexing must be set in two places in the NetBackup configuration:
Additional configuration 19
Multiplexing
■ Storage unit
■ Schedule
Note: If you change these values, it does not take effect until the next time a
schedule runs.
Maximum streams per drive for a storage unit

The Maximum Streams Per Drive setting for a storage unit specifies how many
backups NetBackup can multiplex onto any single drive in the storage unit. The
value is set for each storage unit.
For more information, see “Enable multiplexing” on page 230 in the NetBackup
Administrator’s Guide, Volume I.
The number can range from 1 through 32, where 1 is the default and specifies no
multiplexing.
Choose a value that is based on the ability of the central processing unit to
handle parallel jobs. Because extra buffers are required, memory is also
important. If the server cannot perform other tasks or runs out of memory or
processes, reduce the Maximum Streams Per Drive setting for the storage unit.
Consider the following to estimate the potential load that multiplexing can place
on the central processing unit:
■ The maximum concurrent jobs that NetBackup can attempt equals the sum
of the concurrent backup jobs that can run on all storage units.
■ The maximum concurrent jobs that can run on a storage unit equals the
Maximum Streams Per Drive value, multiplied by the number of drives.
Media multiplexing for a schedule

In addition to the Maximum Streams Per Drive setting for a storage unit, specify
a Media Multiplexing value for each schedule.
For more information, see “Media multiplexing” on page 141 in the NetBackup
The Media Multiplexing value specifies the maximum number of backups from
the schedule to be multiplexed onto any single drive in the configuration.
The Media Multiplexing setting ranges from 1 through 32, where 1 is the default
and specifies no multiplexing. Regardless of the setting on a schedule, the
maximum jobs that NetBackup starts never exceeds the Maximum Streams Per
Drive value for the storage unit. NetBackup attempts to add multiplexed jobs to
drives that are already use multiplexing. If multiplexed jobs are confined to
specific drives, other drives are available for non-multiplexed jobs.
Multiplexing
When NetBackup multiplexes jobs, it continues to add jobs to a drive until the
number of jobs on the drive matches either of the following:
■ This schedule’s Media Multiplexing setting.
If the limit is reached for a drive, NetBackup sends jobs to other drives. In
the following figure, when the Schedule A limit is reached on Drive 1,
NetBackup adds Schedule A jobs to Drive 2.
■ The storage unit’s Maximum streams per drive setting. NetBackup can add
jobs from more than one schedule to a drive.
In the following figure, unshaded numbers denote a job starting. Shaded
numbers denote job completion. For example, 1 denotes the start of job
A1 on Drive 1.
9 denotes the completion of job A1 on Drive 1.
Multiplexing
Figure 1-1 Multiplexing and schedules

Schedule A Schedule B
Media Multiplexing per drive = 2 Media Multiplexing per drive = 4
Storage Unit
dog Max mpx per drive = 4 fox
1 9 A1 B1 5 12
2 10 A2 Drive 1
B2 6
A5
13
cat otter
3 11 A3 B3 7
Drive 2
4 A4 B4 8
Assume schedule A begins first (note that the schedules can be in the same or in different
policies). Also, assume that Allow Multiple Data Streams is enabled, so a client can have multiple
data streams.
Jobs A1 and A2 from client dog start on drive 1. Schedule A Media Multiplexing limit of 2
1 2 is reached for this drive.
3 4 Jobs A3 and A4 from client cat start on drive 2. Schedule A Media Multiplexing limit of 2 is
reached for this drive.
5 6 Jobs B1 and B2 for client fox start on drive 1. Storage unit max mpx is reached for this
drive.
Jobs B3 and B4 from client otter start on drive 2. All jobs are now running for schedule B.
7 8 Storage Unit Max mpx is reached for drive 2.
Jobs A1 and A2 from client dog finish on drive 1. However, jobs B1 and B2 for client fox
9 10 continue to run. Schedule A Media Multiplexing limit of 2 prevents job A5 from starting on
drive 1.
11 12 Job A3 from client cat finishes on drive 2 and job B1 from client fox finishes on drive 1.
Job B2 is the only job currently running on drive 1.
Job A5 from client cat starts on drive 1. JobA5 is the last job for schedule A. Schedule A
13 Media Multiplexing limit of 2 prevents job A5 from starting on Drive 2. Therefore, job A5
starts on Drive 1. NetBackup attempts to add multiplexed jobs to drives that already use
multiplexing. If multiplexed jobs are confined to specific drives, other drives are available
for non-multiplexed jobs.
Multiplexing
Note: If the backup window closes before NetBackup can start all the jobs in a
multiplexing set, NetBackup completes only the jobs that have started. For
example, Figure 1-1 on page 21 assumes that the Activity Monitor shows A1
through A5 as queued and active. If only A1 and A2 start before the window
closes, NetBackup does not perform the other jobs that are in the set. If the
window closes before any jobs have started, then only the first queued and
active job starts and completes. (A1 in this example.)
Other configuration settings to consider using multiplexing

Limit jobs per policy
Set Limit Jobs Per Policy high enough to support the specified level of
multiplexing.
For more information, see “Limit jobs per policy” on page 97 in the NetBackup
Maximum jobs per client

The Maximum Jobs Per Client property limits the number of backup jobs that
can run concurrently on any NetBackup client.
Usually, the client setting does not affect multiplexing. However, consider a case
where jobs from different schedules on the same client go to the same storage
unit. In this case, the maximum number of jobs that are permitted on the client
would be reached before the multiplexing limit is reached for the storage unit.
When the maximum number of jobs on the client is reached, it prevents
NetBackup from fully using the storage unit’s multiplexing capabilities.
Maximum Jobs Per Client appears on the Global properties dialog box.
Maximum jobs this client

You can also set the maximum number of jobs that are allowed on a specific
client without affecting other clients.
For more information, see “Maximum data streams” on page 387 in the
NetBackup Administrator’s Guide, Volume I.
MPX restore delay

The Delay On Multiplexed Restores property applies to multiplexed restores.
The property specifies how long the server waits for additional restore requests
of files and raw partitions in a set of multiplexed images on the same tape. Delay
On Multiplexed Restores appears on the General Server properties dialog box.
Multiplexing
Demultiplexing
Demultiplexing speeds up future restores and is useful for creating a copy for
off-site storage. Use duplication to demultiplex a backup.
Duplication allows one multiplexed backup at one time to be copied from the
source media to the target media. When duplication is complete, the target
contains a single demultiplexed copy of each duplicated backup. (The target can
also contain other backups.) The duplicate copy can be made into the primary
copy. Do not select Preserve Multiplexing in the Setup Duplication Variables
dialog box when backups are duplicated.
Note: If you use the bpduplicate command instead of the NetBackup

Administration Console, do not include the -mpx option on that command.
Using multiple NetBackup master servers
Using multiple NetBackup master servers
For a large site, you can use multiple NetBackup master servers to optimize the
backup loads. You divide the clients between the servers as necessary. The
following figure shows a multiple-server configuration where the two sets of
networks (A1/A2 and B1/B2) each have enough clients to justify separate
servers. In this environment, the two NetBackup server configurations are
completely independent. You can also create a configuration where one server is
the master and the other is a media server.
Workstations
Network A1
NetBackup Workstations
Mass Master Server A
Storage
Network A2
NetBackup
Mass
Master Server B
Storage
Network B1
Workstations
Router
Workstations
Network B2
Using multiple media servers with one master server
Using multiple media servers with one master

server
You can set up a NetBackup protection domain as follows:
■ One master server, which controls all backup scheduling.
■ Multiple media servers, which write the backup images to disk or removable
media. They may have peripheral devices to provide additional storage.
■ Multiple protected NetBackup clients, which send their data to the media
servers.
A protection domain refers collectively to the NetBackup master server, its
NetBackup media servers, and its NetBackup clients. In a group of NetBackup
servers, a client can have backups directed to any device on any server in the
group.
A common alternative strategy is to install extra peripherals on the clients that
produce large amounts of data. The master server directs the data from the
client to the client’s peripherals, which reduces network traffic because the data
does not traverse the network. This strategy also distributes the backup load
between the master and the media servers.
Two important points to remember about master and media servers:
■ There can be only one master server in a group.
■ A NetBackup master server is a media server for itself but cannot be a media
server for another master server.
Using multiple media servers with one master server
The following figure shows where software is installed and where the
NetBackup catalogs are located (by default). The following topics provide more
details on master and media servers and a procedure to configure them.
Master Server
Administration
Interface*
NetBackup Catalogs User Interface (BAR)
User Interface (BAR) Configuration files
Image database
Information in
NetBackup Storage Administration
relational databases
Client Device Interface*
(about devices,
volumes)
User Interface User Interface (BAR)
NetBackup NetBackup
Storage Storage
Device Media Server Media Server Device
Remote Admin Remote Admin

Console* Console*
* You can also use the Backup, Archive, and Restore user
interface from a Windows client that has the Remote
Administration Console installed.
Software on each server

Applies to NetBackup Enterprise Server only.
Install NetBackup server software on each NetBackup server that has a
peripheral that you want to include in a storage unit. The NetBackup installation
program has choices for master and media server installation.
Adding a media server
NetBackup catalogs
The master server is the default location for the NetBackup catalogs. The
catalogs include the media and the volume database (emm_data.db). The volume
database contains the media usage information and the volume information
that are used during the backups.

The following section applies to NetBackup Enterprise Server only.
Use the following procedure to add a media server to an existing NetBackup
environment.
Note: The NetBackup Enterprise Media Manager service must be active when
you add a media server, configure devices and volumes, and backup or restore
clients.
To add a media server

1 On the new media server host, attach the devices and install any software
that is required to drive the storage devices. For help, see the vendor’s
documentation.
2 Prepare the device drivers on the new media server host’s operating system
as explained in the NetBackup Device Configuration Guide.
3 Add the new media server to the additional servers list of the master server
and of the clients the new media server backs up. If the EMM server resides
on a host other than the master server, add the new media server to the
additional servers list on that host. If the new media server is part of a
server group, add it to the additional servers list on all media servers in the
group.
Note: To avoid problems with NetBackup, ensure that the host name you
use in NetBackup matches the host name in your TCP/IP configuration.
To add the new media server to the additional servers list, do the following:
a Select NetBackup Management > Host Properties > hosttype. For
example, to add the new media server to clients, select Clients.
b Select the host that you want to change in the right pane. To select more
than one host, hold down the Shift key and select all the hosts that you
want to change in the right pane.
c Select Actions > Properties.
d Select the Servers properties.

e Click Add next to the Additional servers window and type the name of
the new server.
f Click Add to add the server to the additional server list for all selected
hosts.
g Click Close.
h Click OK.
For more information, see “Servers properties” on page 465 in the

4 Restart the NetBackup services on the master server, the EMM server, and
the media servers on which you added the new server name.
5 On NetWare target clients, add the new media server name by using a
SERVER entry in the bp.ini file.
6 Install the NetBackup media server software as explained in the NetBackup
Installation Guide.
7 Configure the drives and robots as explained in ”Devices” in the NetBackup
8 Configure the volumes as explained in “Media” in the NetBackup
9 On the master server, do the following to the NetBackup configuration:
a Add storage units to the media server. Always specify the media server
as the media server for the storage unit.
b Enter the catalog paths if necessary:
To use the online, hot catalog backup method:
NetBackup enters the paths automatically.
To use the offline, cold catalog backup method:
Add the catalog paths for the media server to the NetBackup catalog
backup configuration.
For more information, see Chapter 4, “NetBackup Catalog” on page 275
in the Administrator’s Guide, Volume I.
Paths on a Windows media server:
media_server_name:install_path\NetBackup\db
media_server_name:install_path\NetBackup\var
media_server_name:install_path\Volmgr\database
Where install_path is the directory where the NetBackup
software is installed on the media server.
Paths on a UNIX media server:
media_server_name:/usr/openv/netbackup/db
media_server_name:/usr/openv/var
media_server_name:/usr/openv/volmgr/database
c Configure the NetBackup policies and schedules to use the storage units
that are configured on the media server.
10 Test your configuration by performing a user backup or a manual backup
that uses a schedule that specifies a storage unit on the media server.
Registering a media server

If the EMM server is not running when you add a media server, the media server
is not registered. You cannot discover, configure, and manage devices. You must
register the media server with the EMM server.
To register a media server
1 Start the EMM service on the EMM server.
2 On the EMM server host, run the following command (use the host name of
the media server):
nbemmcmd -addhost -machinename hostname -machinetype media
-masterserver server_name -operatingsystem os_type
-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 nbemmcmd command usage, see NetBackup Commands for UNIX and Linux
or NetBackup Commands for Windows.
NetBackup configuration options
NetBackup configuration options allow an administrator to customize

NetBackup to meet specific site preferences and requirements. In most
instances, the defaults provide good results. To change the defaults, do so
according to the one of the following methods:
■ In the NetBackup Administration Console, navigate to the various properties
by selecting NetBackup Management > Host Properties within Master
Servers, Media Servers, or Clients.
Configuration options are described in Chapter 7 of the NetBackup
Note: Stop and restart all NetBackup daemons and utilities after making a
change to the /usr/openv/netbackup/bp.conf file on the master
server. Restart the daemons to ensure that the new bp.conf values are
used all the NetBackup processes that require them. This action is not
required for changes to bp.conf files on a client or to a $HOME/bp.conf
file on the master server.
■ On NetBackup UNIX servers and clients, use one of the following:

■ Use the bpgetconfig command to obtain a list of configuration
entries. Then, use bpsetconfig to change the entries. The commands
are described in the NetBackup Commands for UNIX and Linux.
■ Enter the option in the bp.conf file as explained in this chapter. Most
options can be entered in this way.
■ Enter the option in the vm.conf file as explained in this chapter. The
vm.conf file contains configuration entries for media and device
management.
■ Use the nbemmcmd command to modify some options as noted in this
chapter or as described in NetBackup Commands for UNIX and Linux.
■ On clients, specify configuration options as explained in the Backup,
Archive, and Restore Getting Started Guide for the client.
Syntax rules for bp.conf options

Use the following syntax rules to create entries in bp.conf:
■ Use the # symbol to comment out lines
■ Any number of spaces or tabs are allowed on either side of = signs
■ Blank lines are allowed
■ Any number of blanks or tabs are allowed at the start of a line
bp.conf options for servers

The bp.conf options for NetBackup UNIX servers are located in the following
file:
/usr/openv/netbackup/bp.conf
If a single UNIX system is running as both a client and a server, the

/usr/openv/netbackup/bp.conf file contains both the server the and client
options.
Each nonroot user on a UNIX client can also have a personal bp.conf file in
their home directory:
$HOME/bp.conf
For information about client options, see “bp.conf options for UNIX clients” on
page 66.
Note: The SERVER option must be present in the

/usr/openv/netbackup/bp.conf file on all NetBackup UNIX clients and
servers. It is also the only required entry in these bp.conf files. NetBackup uses
internal software defaults for all options in the bp.conf file, except SERVER.
During installation, NetBackup sets the SERVER option to the name of the
master server where the software is installed.

The SERVER entries must be the same on all servers in a master and a media
server cluster. Symantec recommends (but does not require ) that all other
entries also match on all servers. (The CLIENT_NAME entry is an exception.)
ALLOW_MEDIA_OVERWRITE
The ALLOW_MEDIA_OVERWRITE option overrides NetBackup’s overwrite
protection for various media formats on removable media.
Use this option by adding it to the /usr/openv/netbackup/bp.conf file on a
UNIX master server. Or, set the Allow media overwrite property in the Media
host properties.
For more information, see Chapter 7 of the NetBackup Administrator’s Guide,
Volume I.
For example, to permit overwriting the cpio format, add the following on the
master server (and media servers if applicable):
ALLOW_MEDIA_OVERWRITE = CPIO
ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA
The ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA entry allows NetBackup to
mix retention levels on media. Default: This option is not present and each
volume can contain backups of one retention level.
This option can be set using either of the following methods:
■ Changing the Enable standalone drive extension property in the Media host
properties. (Default: enabled.)
For more information, see Chapter 7 of the NetBackup Administrator’s
Guide, Volume I.
■ By using the nbemmcmd command. (See NetBackup Commands for UNIX and
Linux.)
ALLOW_NON_RESERVED_PORTS
The ALLOW_NON_RESERVED_PORTS entry specifies that the NetBackup Client
daemon (bpcd) can accept remote connections from nonprivileged ports (port
numbers 1024 or greater). If this entry is not present, then bpcd requires
remote connections to come from privileged ports (port numbers 1024 or
smaller). This option can be useful when NetBackup clients and servers are on
opposite sides of a firewall.
ALLOW_NON_RESERVED_PORTS = YES | NO
UNIX master server.
For use on a client, see “ALLOW_NON_RESERVED_PORTS” on page 33.
AUTHENTICATION_DOMAIN
The AUTHENTICATION_DOMAIN entry defines a set of Symantec product
authentication principals. A master server that uses Symantec product
authentication and authorization must have at least one
AUTHENTICATION_DOMAIN entry, and more than one can be specified.
If a media server or client does not define an authentication domain, it uses the
authentication domains of its master server.
UNIX master server. Or, add a domain in the Authentication Domain tab of the
Access Control host properties.
Volume I.
AUTHENTICATION_DOMAIN = domain "comment" mechanism broker [
port ]
Where:
■ domain is an Internet domain name or a Windows domain name.
■ "comment" is a quoted comment that describes the authentication domain.
■ mechanism is the authentication mechanism. The following keywords
indicate the mechanism:
■ NIS (Network Information Service version 1)
■ NIS+ (Network Information Service version 2)
■ PASSWD (Local UNIX password file on the specified broker)
■ VXPD (the Symantec product authentication and authorization private
database)
■ WINDOWS (Windows Active Directory or primary domain controller)
■ broker is the host name or IP address of the authentication broker.
■ port is the port number of the authentication broker. The default is the
standard port number for authentication brokers.
Example
AUTHENTICATION_DOMAIN = mycompany.com "Typical UNIX logins" NIS
broker1.mycompany.com
AUTHENTICATION_DOMAIN = OurEnterprise "Typical Windows logins"
WINDOWS broker2.mycompany.com 5544
AUTHENTICATION_DOMAIN = mycompany.com "VxSS-Only Identities" VXPD
broker1.mycompany.com
AUTHENTICATION_DOMAIN = broker3.mycompany.com "Local UNIX Logins on
host broker3" PASSWD broker3.mycompany.com
In the example, mycompany.com is the Internet domain name and

OurEnterprise is the Windows domain name.
The broker on host name broker1 handles both NIS and private authentication
for Symantec product authentication.
The broker on host name broker2 handles Windows authentication for
Symantec product authentication.
broker2 uses the non-standard port number 5544.
The broker on host name broker3 uses its local /etc/passwd file for
Symantec product authentication.
AUTHORIZATION_SERVICE
The AUTHORIZATION_SERVICE entry defines the Symantec product
authorization service that the local NetBackup server uses. A master server that
uses Symantec product authorization must define an authorization service. If a
media server does not define an authorization service, it uses its master server's
authorization service.
UNIX master server. Or, enter a host name in the Authorization Service tab in
the Access Control host properies.
Volume I.
AUTHORIZATION_SERVICE = host [ port ]
Where:
host is the host name or IP address of the authorization service.
port is the port number of the authorization service. The default is the
standard port number for the authorization service.
BPBRM_VERBOSE
Used for debugging purposes, the BPBRM_VERBOSE option controls the amount
of information NetBackup includes in its bpbrm debug log. Default: The same
value as the bp.conf VERBOSE entry (Global logging level). The
BPBRM_VERBOSE entry overrides the bp.conf VERBOSE entry.
UNIX master server. Or, set the BPBRM logging level property in the Logging
host properties.
Volume I.
To use the same value as the bp.conf VERBOSE entry for bpbrm, enter:
BPBRM_VERBOSE = 0
The entry is the same as setting BPBRM logging level in the Logging host
properties to Same as Global.
To log the minimum amount of information for bpbrm, enter:
BPBRM_VERBOSE = -1
properties to 0.
To log additional information for bpbrm, enter a value of 1 through 5:
BPBRM_VERBOSE = 1
properties to 1.
To log the maximum amount of information for bpbrm, enter:
BPBRM_VERBOSE = 5
properties to 5.
For more information about the bpbrm debug log, see the NetBackup
Troubleshooting Guide for UNIX and Windows.
BPDBJOBS_COLDEFS
Add BPDBJOBS_COLDEFS entries to the bp.conf file to customize the output of
bpdbjobs. Add a BPDBJOBS_COLDEFS entry for every column you want to
include in the output using the following format:
BPDBJOBS_COLDEFS = COLDEFS_ENTRY [minimum_size [true |
false]]
Where:
COLDEFS_ENTRY is the name of the column to include in the output. See the
following table for valid BPDBJOBS_COLDEFS entries.
minimum_size is the minimum column width. If not specified, the default
is a width of 5.
true indicates that the column should expand as needed. If not specified,
true is the default.
false indicates that the column should not expand beyond the
minimum_size.
The order of the entries determines the order that the column headings appear.
Example
BPDBJOBS_COLDEFS = JOBID 5 true
BPDBJOBS_COLDEFS = TYPE 4 true
BPDBJOBS_COLDEFS = STATE 5 true
BPDBJOBS_COLDEFS = STATUS 6 true
BPDBJOBS_COLDEFS = POLICY 6 true
BPDBJOBS_COLDEFS = SCHEDULE 8 true
BPDBJOBS_COLDEFS = CLIENT 6 true
BPDBJOBS_COLDEFS = DSTMEDIA_SERVER 12 true
BPDBJOBS_COLDEFS = ACTPID 10 true
Note: Keep in mind the following ramifications of a BPDBJOBS_COLDEFS entry

in the bp.conf conditions:
– The addition of any BPDBJOBS_COLDEFS entry overrides all default columns.
– All users on the local system see only those columns that are specified in the
bp.conf file.
Table 1-1 BPDBJOBS_COLDEFS Entries and Column Head Names
COLDEFS Entry Column Name COLDEFS Entry Column Name
ACTIVEELAPSED Active Elapsed (elapsed active PATHNAME KB Per Sec

time)
ACTPID Active PID (PID of job) PARENTJOBID Parent JobID
ATTEMPT Attempt POLICY Policy
BACKUPTYPE Backup Type POLICYTYPE Policy Type
CLIENT Client PRIORITY Priority
COMPLETION Completion (percent complete) PROFILE Profile (Vault only)
COMPRESSION Compression RETENTION Retention

(yes or no) (retention period)
DSTMEDIA_SERVER Dest Media Svr RESUMABLE Resumable

(writing media server)
DSTMEDIAID Dest Media ID (writing media ROBOT Robot (Vault only)

ID)
DSTSTORAGE_UNIT Dest StUnit (writing storage RQSTPID Request PID

unit) (PID requesting job, if
applicable)
ELAPSED Elapsed (elapsed time) SCHEDULE Schedule
ENDED Ended SCHEDULETYPE Schedule Type
ESTFILE Est File (estimated number of SESSIONID Session ID (Vault only)

files)
ESTKB Est KB SRCMEDIA_SERVER Src Media Svr

(estimated number of kilobytes)
FILES Files SRCMEDIAID Src Media ID
GROUP Group SRCSTORAGE_UNIT Src StUnit
JOBID JobID STARTED Started
KBPERSEC Pathname STATE State
KILOBYTES Kilobytes STATUS Status
LASTBACKUP Last Backup (date and time) STREAMNUMBER Stream Number

Table 1-1 BPDBJOBS_COLDEFS Entries and Column Head Names (continued)
COLDEFS Entry Column Name COLDEFS Entry Column Name
MAINPID Main PID (PID that spawns job, SUSPENDABLE Suspendable

if applicable)
NUMTAPESEJECT Media to Eject (number of tapes TYPE Type (job type)

to eject; Vault only)
OPERATION Operation (current operation) VAULT Vault (Vault only)
OWNER Owner
BPDBM_VERBOSE
Used for debugging purposes, the BPDBM_VERBOSE option controls the amount
of information NetBackup includes in its bpdbm debug logs.
UNIX master server. Or, set the BPDBM logging level property in the Logging
host properties.
Volume I.
Default: The same value as the bp.conf VERBOSE entry (Global logging level).
The BPDBM_VERBOSE entry overrides the bp.conf VERBOSE entry (Global
logging level).
To use the same value as the bp.conf VERBOSE entry for bpdbm, enter:
BPDBM_VERBOSE = 0
The entry is the same as setting BPDBM logging level in the Logging host
To log the minimum amount of information for bpdbm, enter:
BPDBM_VERBOSE = -1
properties to 0.
To log additional information for bpdbm, enter a value of 1 through 5:
BPDBM_VERBOSE = 1
properties to 1.
To log the maximum amount of information for bpdbm, enter:
BPDBM_VERBOSE = 5
properties to 5.
The following examples show two bp.conf entries that enable logging, while
minimizing the rate of growth of the bpdbm debug file:
VERBOSE = 5
BPDBM_VERBOSE = -1
For more information about the bpdbm debug log, see the NetBackup
BPRD_VERBOSE
Used for debugging purposes, the BPRD_VERBOSE option controls the amount of
information NetBackup includes in its bprd debug logs.
UNIX master server. Or, set the BPRD logging level property in the Logging host
properties.

Volume I.
The BPRD_VERBOSE entry overrides the bp.conf VERBOSE entry (Global
logging level).
To use the same value as the bp.conf VERBOSE entry for bprd, enter:
BPRD_VERBOSE = 0
The entry is the same as setting BPRD logging level in the Logging host
To log the minimum amount of information for bprd, enter:
BPRD_VERBOSE = -1
properties to 0.
To log additional information for bprd, enter a value of 1 through 5:
BPRD_VERBOSE = 1
properties to 1.
To log the maximum amount of information for bprd, enter:
BPRD_VERBOSE = 5
properties to 5.
For more information about the bprd debug log, see the NetBackup
BPTM_VERBOSE
Used for debugging purposes, the BPTM_VERBOSE option controls the amount of
information NetBackup includes in its bptm debug logs.
UNIX master server. Or, set the BPTM logging level property in the Logging host
properties.
Volume I.
The BPTM_VERBOSE entry overrides the bp.conf VERBOSE entry (Global
logging level).
To use the same value as the bp.conf VERBOSE entry for bptm, enter:
BPTM_VERBOSE = 0
The entry is the same as setting BPTM logging level in the Logging host
To log the minimum amount of information for bptm, enter:
BPTM_VERBOSE = -1
properties to 0.
To log additional information for bptm, enter a value of 1 through 5:
BPTM_VERBOSE = 1
properties to 1.
To log the maximum amount of information for bptm, enter:
BPTM_VERBOSE = 5
properties to 5.
For more information about the bptm debug log, see the NetBackup
BPEND_TIMEOUT
Note: If you change this option, verify that the CLIENT_READ_TIMEOUT option
is set to the same or higher value.
Specifies the number of seconds to wait for the bpend_notify script on a client
to complete. Default: Timeout is 300 seconds.
UNIX master server. Or, set the Backup end notify timeout property in the
Timeouts host properties.
Volume I.
BPSTART_TIMEOUT
Note: If you change this option, verify that the CLIENT_READ_TIMEOUT option
is also set to the same or higher value.
Specifies the number of seconds to wait for the bpstart_notify script on a
client to complete. Default: 300 seconds.
UNIX master server. Or, set the Backup start notify timeout property in the
Volume I.
CHECK_RESTORE_CLIENT
The CHECK_RESTORE_CLIENT entry specifies that the client being restored to
is checked before the restore starts. An unresponsive client can slow the
restores of other clients that have data on the same tapes. This option only
applies to master servers.
UNIX master server.
CLIENT_CONNECT_TIMEOUT
The CLIENT_CONNECT_TIMEOUT entry specifies the number of seconds that
the server waits before timing out when it connects to a client. Default: 300
seconds.
UNIX master server. Or, set the Client connect timeout property in the
CLIENT_PORT_WINDOW
The CLIENT_PORT_WINDOW entry specifies the range of nonreserved ports on
this computer that are used for connecting to NetBackup on other computers.
This setting applies when it connects to a client configured to accept
nonreserved ports.
For information on client configuration, see
“ALLOW_NON_RESERVED_PORTS” on page 33.
Use this option by adding it to the /usr/openv/netbackup/bp.conf file on
NetBackup servers or clients.
The following example permits ports from 4800 through 5000:
CLIENT_PORT_WINDOW = 4800 5000
If you specify 0 for the first number (default), the operating system determines
the nonreserved port to use.
Refer to “NBJAVA_CLIENT_PORT_WINDOW” on page 664 in the
Administrator’s Guide, Volume I for connections from the NetBackup-Java
console.
CLIENT_READ_TIMEOUT
Note: Use this option only on a server or a database agent (such as NetBackup
for Oracle). This option has a reasonable default and has to be changed only if
problems are encountered.
The CLIENT_READ_TIMEOUT entry specifies the number of seconds to use for
the client-read timeout.
UNIX master server. Or, set the Client read timeout property in the Timeouts
host properties.
Volume I.
You can also add CLIENT_READ_TIMEOUT on database agents (such as
NetBackup for Oracle).
CLIENT_READ_TIMEOUT on a database agent is a special case because these
types of clients can initially require more time to get ready than other clients.
Database backup utilities frequently start several backup jobs at the same time,
which slows the CPU.
The sequence on a database agent is as follows:
■ NetBackup on the database agent reads the client’s

CLIENT_READ_TIMEOUT to find the value to use initially. If the option is
not set, the standard default of five minutes is used.
■ When the database agent API receives the server’s value, it uses it as the
CLIENT_READ_TIMEOUT.
Default: CLIENT_READ_TIMEOUT is not specified on either a server or a
database agent and the timeout is 300 seconds.
Note: We suggest that you set CLIENT_READ_TIMEOUT on the database agent to

a value greater than 5 minutes. A setting of 15 minutes has been found to be
adequate for many installations.
CLIENT_RESERVED_PORT_WINDOW
The CLIENT_RESERVED_PORT_WINDOW entry specifies the range of reserved
ports on this computer that are used for connecting to NetBackup on other
computers. This setting applies when connecting to a client configured to accept
only reserved ports.
UNIX master server or client.
CLIENT_RESERVED_PORT_WINDOW = 900 1023
Default: Range of 512 through 1023. Note that if you specify 0 for the first
number, a nonreserved port is used instead. The nonreserved port is chosen by
the operating system.
CONNECT_OPTIONS
The CONNECT_OPTIONS entry specifies three options that are designed to
enhance firewall efficiency with NetBackup:
■ Whether the host is connected to using a reserved or a nonreserved port
number.
■ Whether the host is connected to by another server using the traditional
call-back method or using the Veritas Network daemon (vnetd).
■ Whether the host is connected to by using one of the following methods:
■ vnetd or the daemon’s port number,
■ by using vnetd only, or
■ by using the daemon’s port number only.
UNIX master server. Or, set this option in the Firewall host properties.
Volume I.
To use this entry, add it to /usr/openv/netbackup/bp.conf on NetBackup
servers in the following format:
CONNECT_OPTIONS = host [ 0 | 1 | 2 ][ 0 | 1 | 2 | 3 ]
[ 0 | 1 | 2 | 3 ]
Where:
■ host is the host name of the server or client to be connected to. host must be
at NetBackup version 4.5 or greater.
■ The first setting indicates the type of port to use to connect to bpcd on host:
0 = Use a reserved port number.
1 = Use a nonreserved port number. If you select this option, enable Allow
non reserved ports for the selected host. See the Universal Settings dialog
box under Host Properties > Media Servers.
2 = Use the that the DEFAULT_CONNECT_OPTIONS configuration entry
defines (default).
■ The second setting indicates the bpcd call-back method to use to connect to
host:
0 = Use the traditional call-back method (default).
1 = Use the vnetd no call-back method.
defines (default).
See “DEFAULT_CONNECT_OPTIONS” on page 45.
■ The third setting is relevant to NetBackup clients and servers. This setting
indicates the connection method to use to connect to host:
0 = Connect to a daemon on the host using vnetd if possible, otherwise
connect using the traditional port number of the daemon.
1 = Connect to a daemon on the host using vnetd only. This setting turns
on unidirectional bpcd.
2 = Connect to a daemon on the host using the traditional port number of
the daemon only.
defines (default).
See “DEFAULT_CONNECT_OPTIONS” on page 45.
The bp.conf file may contain CONNECT_OPTIONS settings for multiple hosts.
For example:
CONNECT_OPTIONS = shark 0 0 0
bpcd connections to server shark must use a reserved port number and
the traditional call-back method.
Connections to bpdbm, vmd, bprd, and robotic daemons on server
shark can use either vnetd or the daemon’s port number.
CONNECT_OPTIONS = dolphin 1 0 1
bpcd connections to server dolphin must use a nonreserved port
number and the traditional call-back method.
Connections to bpdbm, vmd, bprd, and robotic daemons on server
dolphin must use vnetd.
CONNECT_OPTIONS = perch 0 1 2
bpcd connections to server perch must use a reserved port number and
vnetd.
Connections to bpdbm, vmd, bprd, and robotic daemons on server perch
must use the daemon’s port number.
CONNECT_OPTIONS = trout 1 1 2
bpcd connections to server trout must use a nonreserved port number
and vnetd.
Connections to bpdbm, vmd, bprd, and robotic daemons on server trout
must use the daemon’s port number.
Refer to “NBJAVA_CONNECT_OPTION” on page 665 in the Administrator’s
Guide, Volume I for connections from the NetBackup-Java Console.
DEFAULT_CONNECT_OPTIONS
The DEFAULT_CONNECT_OPTIONS entry specifies the default values for the
CONNECT_OPTIONS configuration entry. If a host name is not specified in any
CONNECT_OPTIONS entry, the value from the DEFAULT_CONNECT_OPTIONS
entry is used.
UNIX master server. Or, set this option in the Firewall host properties.
Volume I.
To use this entry, add it to /usr/openv/netbackup/bp.conf on NetBackup
servers in the following format:
DEFAULT_CONNECT_OPTIONS = [ 0 | 1 ][ 0 | 1 ][ 0 | 1 | 2 ]
Where:
■ The first setting indicates the type of port to use to connect to bpcd on the
remote host:
0 = Use a reserved port number (default).
1 = Use a nonreserved port number. If you select this option, enable Allow
non reserved ports for the selected host. See the Universal Settings dialog
box under Host Properties > Media Servers.
■ The second setting indicates the bpcd call-back method to use to connect to
the remote host:
0 = Use the traditional call-back method.
1 = Use the vnetd no call-back method (default).
■ The third setting indicates the connection method to use to connect to the
remote host:
0 = Connect to a daemon on the host using vnetd if possible, otherwise
connect using the traditional port number of the daemon (default).
1 = Connect to a daemon on the host using vnetd only.
2 = Connect to a daemon on the host using the traditional port number of
the daemon only.
Note: If vnetd only (1) is selected as the daemon connection port, the BPCD
connect-back setting is not applicable. If vnetd only (1) is selected as the
daemon connection port, the non-reserved ports setting (1) is always used
regardless of the value of the ports setting.
DISABLE_JOB_LOGGING
The DISABLE_JOB_LOGGING entry disables the logging of the job information
that the NetBackup Activity Monitor requires. Default: job logging occurs.
UNIX master server.
DISABLE_STANDALONE_DRIVE_EXTENSIONS
The DISABLE_JOB_LOGGING entry can be set using either of the following
methods:
■ Changing the Enable standalone drive extension property in the Media host
properties. (Default: enabled.)
Guide, Volume I.
■ By using the nbemmcmd command. (See NetBackup Commands for UNIX and
Linux.)
Disables the nonrobotic drive operations. During a backup, NetBackup does not
automatically attempt to use whatever labeled or unlabeled media it finds in a
nonrobotic drive.
DISALLOW_BACKUPS_SPANNING_MEDIA
The DISALLOW_BACKUPS_SPANNING_MEDIA entry prevents backups from
spanning media. If the end of media is encountered and
DISALLOW_BACKUPS_SPANNING_MEDIA is present, the media is set to FULL.
The operation terminates abnormally. (The action applies to both robotic and
nonrobotic drives.) Default: Backups can span media.

UNIX master server. Or, set the Allow backups to span media property in the
Media host properties.
Volume I.
DISALLOW_CLIENT_LIST_RESTORE
Note: Override the DISALLOW_CLIENT_LIST_RESTORE option for individual

clients by changing their list_restore setting.
The DISALLOW_CLIENT_LIST_RESTORE entry denies the list and restore

requests for all clients. When this option is present, clients cannot list or restore
any files that they have backed up through this master server. Default: This
option is not present and clients can list and restore their files.
UNIX master server.
DISALLOW_CLIENT_RESTORE
Note: You can override the DISALLOW_CLIENT_RESTORE option for individual

clients by changing their list_restore setting.
The DISALLOW_CLIENT_RESTORE entry denies restore requests for all clients.

When this option is present, clients cannot restore the files that they have
backed up through this master server. Default: This option is not present and
clients can restore their files.
UNIX master server.
EMMSERVER
The EMMSERVER entry indicates the master or the media server that acts as the
Enterprise Media Manager server for one or more master servers. The EMM
server contains the database where media and device configuration information
is stored.
The EMMSERVER entry applies only to 6.0 (and later) servers.
EMMSERVER = server_name
ENABLE_ROBUST_LOGGING
The ENABLE_ROBUST_LOGGING entry helps limit the amount of disk space that
one debug log directory consumes. When a log file grows to the maximum size,
the log file is closed and a new log file is opened. If the new log file causes the
maximum number of log files in the directory to be exceeded, the oldest log file
is deleted.
The maximum size of a log file is set using the NetBackup command vxlogcfg
with parameters NumberOfLogFiles and MaxLogFileSizeKB. See the
NetBackup Troubleshooting Guide for more information on controlling the log
file size.
If a NetBackup environment uses scripts depending on the MMDDYY.log
naming convention, either update the scripts or disable Robust Logging.
UNIX master server. Or, set the Robust logging property in the Logging host
properties.
Volume I.
FAILOVER_RESTORE_MEDIA_SERVERS
Applies to NetBackup Enterprise Server:
The FAILOVER_RESTORE_MEDIA_SERVERS entry specifies automatic failover
to another NetBackup server if a server is temporarily inaccessible for a restore.
This failover does not require administrator intervention. Default: NetBackup
does not perform automatic failover. The format for the entry follows:
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 server, NetBackup searches from left
to right through the associated FAILOVER_RESTORE_MEDIA_SERVERS list. It
stops when it finds one that is eligible to perform the restore.
Note: There can be multiple FAILOVER_RESTORE_MEDIA_SERVERS entries and

each entry can have multiple servers. However, a NetBackup server can be a
failed_host in only one entry.

UNIX master server.
After adding the FAILOVER_RESTORE_MEDIA_SERVERS entry, stop and restart

the NetBackup Request daemon on the master server where you plan to change
the configuration.
For more information, see “Alternate server restores” on page 687 in the
FORCE_RESTORE_MEDIA_SERVER
The FORCE_RESTORE_MEDIA_SERVER entry forces restores to go to a specific
server, regardless of where the files were backed up. The format for the entry
follows:
FORCE_RESTORE_MEDIA_SERVER = from_host to_host
Where from_host is the server that performed the original backup and to_host is
the server to use for the restore.
UNIX master server.
Stop and restart the NetBackup Request daemon on the master server after
adding the FORCE_RESTORE_MEDIA_SERVER entry. Physically move the media
to to_host before attempting a restore. Update the Media Manager volume
database to reflect the move.
This setting applies to all storage units on the original server. Restores for any
storage unit on from_host go to to_host . To revert to the original configuration
for future restores, delete the entry.
For more information, see “Alternate server restores” on page 687 in the
GENERATE_ENGLISH_LOGS
The GENERATE_ENGLISH_LOGS entry enables the generation of an English
error log, and English trace logs for the bparchive, bpbackup, bpduplicate,
bpimport, and bprestore commands. This option is useful to support
personnel to assist in distributed environments where different locales result in
logs that contain various languages.
An English text error log (indicated by the suffix _en) is created in the following
directory:
/usr/openv/netbackup/db/error
Setting the GENERATE_ENGLISH_LOGS option also forces the -en argument on
the execution of the following commands when the progress log is specified (-L):
bparchive, bpbackup, bpduplicate, bpimport, and bprestore.
The suffix _en indicates the English text progress log.

INCOMPLETE_JOB_CLEAN_INTERVAL
The INCOMPLETE_JOB_CLEAN_INTERVAL entry indicates the number of days a
failed restore job can remain in the incomplete state before being moved to the
done state:
INCOMPLETE_JOB_CLEAN_INTERVAL = x
Where x is a value between 0 and 365. A value of 0 indicates that failed,
incomplete jobs are never automatically moved to the done state. (Default: 7
days.)
UNIX master server or client. Or, set the Move restore job from incomplete
state to done state property in the Global Attributes host properties.
Volume I.
INITIAL_BROWSE_SEARCH_LIMIT
The INITIAL_BROWSE_SEARCH_LIMIT entry specifies the number of days
back that NetBackup searches for files to restore. The value is in days. For
example, to limit the browse range to the seven days before the current date,
specify the following:
INITIAL_BROWSE_SEARCH_LIMIT = 7
This option can be specified on the master server and applies to all NetBackup
clients. It can also be specified on a UNIX client. When this option is specified on
a UNIX client, it applies only to that client. The option can reduce the size of the
search window from what is specified on the server (the client setting cannot
make the window larger).
Default: NetBackup includes files from the time of the last full backup through
the latest backup for the client. If the client belongs to more than one policy,
then the browse starts with the earliest of the set of last full backups.
LIMIT_BANDWIDTH
Note: Read “Notes on bandwidth limits” on page 379 before this option is
changed.
The LIMIT_BANDWIDTH entry specifies a limit for the network bandwidth that
one or more NetBackup clients use on a network. The actual limiting occurs on
the client side of the backup connection. This feature limits only backups.
Restores are unaffected. Default: The bandwidth is not limited.
Each LIMIT_BANDWIDTH entry specifies the bandwidth value and the IP address
of the clients and networks to which it applies. The syntax is as follows:
LIMIT_BANDWIDTH = xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy zzz
LIMIT_BANDWIDTH = xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy zzz
Where:
■ xxx.xxx.xxx.xxx is the beginning of the IP address range. (For example,
10.0.0.2.)
■ yyy.yyy.yyy.yyy is the end of the IP address range. (For example, 10.0.0.49.)
■ zzz is the bandwidth limitation in kilobytes per second. (For example, 200.) A
value of 0 disables throttling for the individual client or the range of IP
addresses covered by this entry.
UNIX master server.
Rules for IP address ranges

The IP address ranges can specify individual clients or entire subnets. The
following are some specific rules on addresses:
■ An IP address can have any one of the following forms:
■ a.b.c.d
Where a, b, c, and d are integers in the range 0-255.
■ 128.net.host
Policy B address (16-bit host).
■ net.host
Policy A address (24-bit host).
■ a
A 32-bit integer that represents the full IP address in network byte
order. (The big endian, the most significant byte is first on the wire.)
■ You can enter IP addresses as decimal, octal, or hexadecimal numbers.
Numbers that begin with 0 are assumed to be octal; numbers that begin with
0x are hexadecimal; all others are assumed to be decimal.
■ Neither the net nor the host part of an IP address can be zero.
■ Only ordinary IP addresses are accepted (policy A, B & C, no multicast or
reserved addresses).
■ Do not create multiple entries that specify the same range of IP addresses. If
you do, NetBackup uses the last one it finds. In the following example,
NetBackup uses the second entry.
LIMIT_BANDWIDTH = 111.222.333.1 111.222.333.255 500
LIMIT_BANDWIDTH = 111.222.333.1 111.222.333.255 200
This rule also applies to multiple entries that specify an exact client
address:
LIMIT_BANDWIDTH = 111.222.333.111 111.222.333.111 200
LIMIT_BANDWIDTH = 111.222.333.111 111.222.333.111 100
■ Do not specify IP address ranges that overlap one another. Consider the
following:
LIMIT_BANDWIDTH = 111.222.333.1 111.222.333.255 500
LIMIT_BANDWIDTH = 111.222.333.5 111.222.333.255 500
The ranges overlap, and bandwidth limiting results are unpredictable.
■ You can specify a range of addresses in one entry and an address for a
specific client in other entries.
If a client is covered by an entry that specifies its exact IP address and by
another entry that specifies a range of IP addresses, NetBackup uses the
bandwidth value in the entry with the exact IP address.
The following sets the bandwidth for a range of IP addresses:
LIMIT_BANDWIDTH = 111.222.333.1 111.222.333.255 500
The following sets the bandwidth for a specific address that is within the
range.
LIMIT_BANDWIDTH = 111.222.333.111 111.222.333.111 200
In this case, NetBackup uses the specific entry (bandwidth of 200) for the
client whose address is 111.222.333.111. You can also use this capability to
exclude specific clients from bandwidth limiting. The order of the range and
specific address entries in the bp.conf file is not significant.
Rules for setting bandwidth values

Set bandwidths for individual clients to one of the following values:
■ 0 (no bandwidth limiting), or
■ Less than or equal to any value that is set for the IP address range that
contains the IP address for the client.
For example, the following is valid:
LIMIT_BANDWIDTH = 111.222.333.1 111.222.333.255 500
LIMIT_BANDWIDTH = 111.222.333.111 111.222.333.111 300
If the bandwidth is set higher for a client than is set for the range, NetBackup
ignores the individual setting. NetBackup uses the value for the range instead.
In this case, the client receives a share of the bandwidth that is specified for the
network.
If the bandwidth limit for a client is equal to or lower than the value for the
range, the client uses whichever setting is lower:
■ Its share of the network bandwidth value
■ Its individual bandwidth value
The bandwidth value that NetBackup uses for a client is always at least one
kilobyte per second.
Examples
■ Configure a bandwidth limit of 500 kilobytes per second for all machines on
the subnet 111.222.333 as follows:
LIMIT_BANDWIDTH = 111.222.333.1 111.222.333.255 500
■ Configure a bandwidth limit of 700 kilobytes per second for a particular

client (111.222.333.111) as follows:
LIMIT_BANDWIDTH = 111.222.333.111 111.222.333.111 700
■ To disable bandwidth limiting for a client in a subnet that has a bandwidth

limit, specify 0 for the kilobytes per second:
LIMIT_BANDWIDTH = 111.222.333.1 111.222.333.255 500
LIMIT_BANDWIDTH = 111.222.333.111 111.222.333.111 0
In this case, no limiting occurs for the client with IP address

111.222.333.111
MEDIA_ID_PREFIX
The MEDIA_ID_PREFIX entry can be set using either of the following methods:
■ Change the Media ID prefix (non-robotic) property in the Media host
properties dialog box. (Default: checkbox clear.)
Guide, Volume I.
■ Use the nbemmcmd command.
(See NetBackup Commands for UNIX and Linux.)
The prefix must be one to three alpha-numeric characters. For example:
MEDIA_ID_PREFIX = FEB
NetBackup appends numeric characters as needed, so the assigned media IDs
become FEB000, FEB001, and so on.
The default media ID prefix is A: NetBackup assigns A00000, then A00001, and
so on.
MEDIA_ID_PREFIX = A
MEDIA_UNMOUNT_DELAY
When MEDIA_UNMOUNT_DELAY is specified, the media unload is delayed for the
specified number of seconds after the requested operation has completed.
(Applies only to user operations.)
UNIX master server. Or, set the Media unmount delay property in the Media
host properties.
Volume I.
For example, assume the delay is 120 seconds:
MEDIA_UNMOUNT_DELAY = 120
MEDIA_REQUEST_DELAY
The MEDIA_REQUEST_DELAY entry can be set using either of the following
methods:
■ Changing the Media request delay property in the Media host properties.
(Default: 0 seconds.)
Guide, Volume I.
■ By using the nbemmcmd command.
See NetBackup Commands for UNIX and Linux.
MEDIA_SERVER
The MEDIA_SERVER entry is similar to the SERVER entry.
A host that is specified as a MEDIA_SERVER is able to back up and restore
clients. However, if the host is not specified as a SERVER, the host has limited
administrative capabilities.
UNIX master server. Or, enter a media server name in the Media Servers list in
the Servers host properties.
Volume I.
For example, assume the media server’s name is oak:
MEDIA_SERVER = oak
MPX_RESTORE_DELAY
The MPX_RESTORE_DELAY entry applies to multiplexed restores. It specifies
how long the server waits for restore requests of files and raw partitions that are
in a set of multiplexed images on the same tape. All the restore requests that are
received within the delay period are included in the same restore operation (one
pass of the tape). Default: 30 seconds.
UNIX master server.
For example, assume the delay is 60 seconds:
MPX_RESTORE_DELAY = 60
MUST_USE_LOCAL_DRIVE
The MUST_USE_LOCAL_DRIVE entry can be set using either of the following
methods:
■ Change the Must use local drive property in the General Server host
properties dialog box. (Default: checkbox clear.)
Guide, Volume I.
■ Use the nbemmcmd command.
For more information, see NetBackup Commands for UNIX and Linux.
If the client is also a media server and this entry is present, backups for this
client must occur on a local drive. If the client is not a media server, this entry
has no effect.
NBRB_CLEANUP_OBSOLETE_DBINFO
The NBRB_CLEANUP_OBSOLETE_DBINFO entry serves as a performance tuning
option for the Intelligent Resource Manager. This entry indicates the number of
seconds (default: 60) that can elapse between the cleanup of obsolete
information in the NetBackup Resource Broker (nbrb) database.
No equivalent exists in the NetBackup Administration Console host properties.
NBRB_ENABLE_OPTIMIZATIONS
The NBRB_ENABLE_OPTIMIZATIONS entry serves as a performance tuning
option for the Intelligent Resource Manager. This entry indicates whether the
Resource Broker caches states of resource requests. Default: 1 (true).
NBRB_FORCE_FULL_EVAL
The NBRB_FORCE_FULL_EVAL entry serves as a performance tuning option for
the Intelligent Resource Manager. This entry indicates the number of seconds
that can elapse between full evaluations of all NetBackup Resource Broker
(nbrb) queues, using no cached EMM information. (Default: 1800 seconds/30

minutes.) For example, full evaluations include matching job resource requests
with available resources.
NBRB_REEVAL_PENDING
The NBRB_REEVAL_PENDING entry serves as a performance tuning option for
the Intelligent Resource Manager. This entry indicates the number of seconds
(default: 60) that can elapse between evaluations of the pending request queue.
For example, a pending request queue can include, jobs awaiting resources.
NBRB_REEVAL_PERIOD
The NBRB_REEVAL_PERIOD entry serves as a performance tuning option for the
Intelligent Resource Manager and NetBackup Resource Broker (nbrb).
NBRB_REEVAL_PERIOD indicates the time between evaluations if an
outstanding request is not satisfied, and if no other requests or resources have
been released. Default: 5 minutes passes before the initial request is reevaluated.
NBRB_RETRY_DELAY_AFTER_EMM_ERR
The NBRB_RETRY_DELAY_AFTER_EMM_ERR entry serves as a performance
tuning option for the Intelligent Resource Manager. This entry indicates how
long NetBackup waits after an EMM error before attempting again. (Default: 60
seconds.) The error must be one where a retry is possible. For example, if a
media server is down.
NBRB_MPX_GROUP_UNLOAD_DELAY
The NBRB_MPX_GROUP_UNLOAD_DELAY entry serves as a performance tuning
option for the Intelligent Resource Manager.
This entry indicates the number of seconds that the NetBackup Resource Broker
(nbrb) waits for a new job to appear before a tape is unloaded.
(Default: 10 seconds.) This setting can help avoid unnecessary reloading of tapes
and applies to all backup jobs.
During user backups, nbrb uses the maximum value of
NBRB_MPX_GROUP_UNLOAD_DELAY and the Media mount timeout host
property setting when unmounting the tape.
This host property is found in the NetBackup Administration Console under
NetBackup Management > Host Properties > Select master server > Timeouts >
Media mount timeout. See Chapter 7 in the Administrator’s Guide, Volume I for
more details.
During restores, Media mount timeout is used, not
NBRB_MPX_GROUP_UNLOAD_DELAY.
RANDOM_PORTS
The RANDOM_PORTS entry specifies whether NetBackup chooses port numbers
randomly or sequentially when it requires one for communication with
NetBackup on other computers.
■ If RANDOM_PORTS = YES (default), NetBackup chooses port numbers
randomly from those that are free in the allowed range. For example, if the
range is from 1024 through 5000, it chooses randomly from the numbers in
this range.
■ If RANDOM_PORTS = NO, NetBackup chooses numbers sequentially, starting
with the highest number available in the allowed range. For example, if the
range is from 1024 through 5000, NetBackup chooses 5000 (if the number is
available). If 5000 is not available, port 4999 is chosen.
By default, this option is not present and NetBackup uses the random method
for selecting port numbers.
RE_READ_INTERVAL
The RE_READ_INTERVAL entry determines how often NetBackup checks disk
storage units for available capacity. Default: 300 seconds (5 minutes).
UNIX master server. Or, change the frequency value for the Check the capacity
of disk storage units property in the General Server host properties.
Volume I.
For example, assume the re-read interval is 350 seconds:
RE_READ_INTERVAL = 350
REQUIRED_INTERFACE
The REQUIRED_INTERFACE entry specifies the network interface that
NetBackup uses when it connects to another NetBackup client or server. A
NetBackup client or server can have more than one network interface and, by
default, the operating system determines the one to use. To force NetBackup
connections to be through a specific network interface, use this entry to specify
the network host name of that interface.
In the following example, host1 is the network host name of the interface:
REQUIRED_INTERFACE = host1
You can add this option to the /usr/openv/netbackup/bp.conf file on a
NetBackup client or server. Default: The entry does not exist and the operating
system determines the interface to use.
Example 1 - client with multiple network interfaces

Assume you have a NetBackup client with two network interfaces. One is for the
regular network and one is for the backup network:
■ The host name for the regular interface is fred
■ The host name for the backup interface is fred_nb
The NetBackup client name setting on both the client and server is fred_nb.
When users on fred start a backup, restore, or list operation, the request ideally
always goes out on the fred_nb interface and over the backup network. This
assumes that fred and the network are set up for this. However, if this
configuration is not in place, fred can send the request out on the fred interface
and over the regular network. The server receives the request from client
fred_nb with host name fred and refuses it because the host and client names do
not match.
One way to solve this problem is to set up the master server to allow alternate
client restores for fred. This allows the server to accept the request, but leaves
NetBackup traffic on the regular network. A better solution is to add the
following entry to the bp.conf file on fred:
REQUIRED_INTERFACE = fred_nb
Now, 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.
Example 2 - server with multiple network interfaces.

Assume you have a NetBackup server with two network interfaces. One is for the
regular network and one is for the backup network:
■ The host name for the regular interface is barney
■ The host name for the backup interface is barney_nb
The bp.conf file on all NetBackup servers and clients has a SERVER =
barney_nb entry.
When barney connects to a client for a backup, the request ideally goes out on
the barney_nb interface and over the backup network. This assumes that barney
and the network are set up for this. However, if this configuration is not in place,
barney can send the request out on the barney interface and over the regular
network. The client now receives the request from barney rather than
barney_nb and refuses it as coming from an invalid server.
One way to solve this problem is to add SERVER = barney to the bp.conf file
on the client. The client now accepts requests from barney, but NetBackup
traffic is still on the regular network.
A better solution is to add the following entry to the bp.conf file on barney:
REQUIRED_INTERFACE = barney_nb
Now, when barney connects to a client, the connection is always through the
barney_nb interface and everything works as intended.
REQUIRED_NETWORK
The REQUIRED_NETWORK entry specifies the required route for backup traffic in
an environment where the network traffic is segregated.
For example, an environment may contain a production network at
145.21.14.0 and a backup network at 192.132.28.0. To indicate that
NetBackup should use only the backup network, add the following entry in the
bp.conf file:
REQUIRED_NETWORK = 192.132.28.0
Note: If the variable is set and the network is not available, all connections fail
and no backups are performed.
SERVER
The first SERVER entry in the bp.conf file must point to that master server
itself. During installation, SERVER is automatically set to the name of the
system on which you install the NetBackup master server software.
The SERVER option must be present in the /usr/openv/netbackup/bp.conf
file on all NetBackup UNIX servers and clients. It is the only required entry in
these bp.conf files. This option is not used in $HOME/bp.conf files on a client.
Note: This section discusses the bp.conf entries on the server. However, note
that every SERVER entry in a client bp.conf file must be a NetBackup master or
media server. That is, each system listed as a SERVER must have either
NetBackup master or media server software installed. The client service on
some clients cannot be started if the client name is incorrectly listed as a server.

If you configure NetBackup media servers for a master server, the bp.conf file
on the master server must have a SERVER entry or MEDIA_SERVER entry for
each. As previously mentioned, the first SERVER entry in the list designates the
master server itself. The SERVER or MEDIA_SERVER entries should be added
after the first, self-referencing entry.
A NetBackup master server can be backed up as a NetBackup client by servers
that belong to another cluster. In that case the bp.conf file on the master
server should have SERVER entries for those servers as well.
The following is an example bp.conf file on a master server:
SERVER = Master_server (this master server itself)
SERVER = NBU_server (master server of another cluster)
SERVER = Media_server_#1
MEDIA_SERVER = Media_server_#2
.
The first SERVER entry in the bp.conf files on all the media servers must point
to the master server for those media servers. A media server can have only one
master server. However, a media server can be backed up as a NetBackup client
by servers that belong to another cluster, in which case the bp.conf on the
media server should have SERVER entries for those servers as well.
The following is an example bp.conf file on a media server:
SERVER = Master_server (for this media server)
SERVER = NBU_server (master server of another cluster)
The SERVER entries must be the same on all servers in a master and media
server cluster.
If you modify or add a SERVER entry in the bp.conf file on the master server,
stop and restart both the NetBackup request daemon (bprd) and NetBackup
database manager (bpdbm) so NetBackup recognizes the change.
Note: If you modify the first bp.conf SERVER entry (the master server) on a
media server, the EMM database also needs to be updated. To update the EMM
database, run nbemmcmd -updatehost to change the master server for a
media server.
SERVER_PORT_WINDOW
The SERVER_PORT_WINDOW entry specifies the range of nonreserved ports on
which this computer accepts connections from NetBackup on other computers.
Default range: 1024 through 5000. This option can also be useful on the clients
that run the NetBackup-Java application server.
UNIX master server. Or, change the Server port window range property in the
Port Ranges host properties.
Volume I.
SERVER_PORT_WINDOW = 4900 5000
SERVER_RESERVED_PORT_WINDOW
The SERVER_RESERVED_PORT_WINDOW entry specifies the range of local
reserved ports on which this computer accepts connections from NetBackup on
other computers. Default range: 512 through 1023.
This setting applies when connecting to a client configured to accept only
reserved ports. This entry is generally not useful on clients.
UNIX master server. Or, change the Server reserved port window range
property in the Port Ranges host properties.
Volume I.
SERVER_RESERVED_PORT_WINDOW = 900 1023
SKIP_RESTORE_TO_SYMLINK_DIR
The SKIP_RESTORE_TO_SYMLINK_DIR entry forces NetBackup to check all
directories on a UNIX client into which files are restored. If the file to be
restored is under a symbolically linked directory, NetBackup does not restore
the file.
For example, if the UNIX client requests a restore for /home/user/.cshrc and
/home/user is a symbolic link, NetBackup does not restore .cshrc.
The addition of SKIP_RESTORE_TO_SYMLINK_DIR helps minimize potential
security and data-loss problems if the restore is performed with root
permissions. Without SKIP_RESTORE_TO_SYMLINK_DIR in the bp.conf file,
NetBackup follows any symbolically linked directories and restores files to that
location.
Note: Restore job performance is reduced when using this option.
SKIP_RESTORE_TO_SYMLINK_DIR and UNLINK_ON_OVERWRITE do not affect

each other if both are specified, with one exception:
If Overwrite existing files is selected with SKIP_RESTORE_TO_SYMLINK_DIR
and UNLINK_ON_OVERWRITE, symbolic links that the restore job comes across
are unlinked before checking, and the files and directory are restored.
For example, if /home/user/ was backed up as a directory and, when restored,
it is a symbolic link to a directory:
■ With just SKIP_RESTORE_TO_SYMLINK_DIR set (and Overwrite existing

files indicated), no files are restored into the directory the symbolic link
points to, and the symbolic link remains.
■ With both UNLINK_ON_OVERWRITE and
SKIP_RESTORE_TO_SYMLINK_DIR (and Overwrite existing files
indicated), the symbolic link directory is unlinked, the original directory is
restored, and all files within the directory are also restored.
■ With neither entry set (and Overwrite existing files indicated), NetBackup
follows the symbolic link and restore all files into the directory to which the
symbolic link points.
SERVER_CONNECT_TIMEOUT
SERVER_CONNECT_TIMEOUT specifies the number of seconds that the master
server waits before timing out when it connects to a media server. Default:
Timeout period is 30 seconds.
UNIX master server.
The following example permits a timeout of 60 seconds:
SERVER_CONNECT_TIMEOUT = 60
UNLINK_ON_OVERWRITE
When a UNIX client indicates Overwrite existing files as a restore option,
UNLINK_ON_OVERWRITE forces NetBackup to first check for the existence of a
file to be restored, unlink the file if it exists, then restore the file. The file can be
any normal file, symbolic link, hard link, or empty directory.
The addition of UNLINK_ON_OVERWRITE helps minimize potential security and
data-loss problems from following existing symbolic links. It also guarantees
that files are restored exactly as they were backed up.
Note: Restore job performance is reduced when using this option.
Without UNLINK_ON_OVERWRITE indicated in the bp.conf file (or set to NO),
but overwrite is specified, NetBackup unlinks existing files or empty directories
when restoring symbolic links, hard links, or special files (CHR, BLK, and FIFO).
However, NetBackup does not unlink when it restores normal files or directories.
This can be a problem with symbolic links because NetBackup follows the
symbolic link to create or replace file(s) pointed to by the symbolic link or in a
directory pointed to by a symbolic link.
SKIP_RESTORE_TO_SYMLINK_DIR and UNLINK_ON_OVERWRITE do not
affect each other if both are specified, with one exception:
If Overwrite existing files is selected with SKIP_RESTORE_TO_SYMLINK_DIR
and UNLINK_ON_OVERWRITE, symbolic links that the restore job comes across
are unlinked before checking, and the files and directory are restored.
For example, if /home/user/ was backed up as a directory and, when restored,
it is a symbolic link to a directory:
■ With just SKIP_RESTORE_TO_SYMLINK_DIR set (and Overwrite existing

files indicated), no files are restored into the directory the symbolic link
points to, and the symbolic link remains.
■ With both UNLINK_ON_OVERWRITE and
SKIP_RESTORE_TO_SYMLINK_DIR (and Overwrite existing files
indicated), the symbolically linked directory is unlinked, the original
directory is restored, and all files within the directory are also restored.
■ With neither set (and Overwrite existing files indicated), NetBackup follows
the symbolic link and restore all files into the directory the symbolic link
points to.
USE_VXSS
The USE_VXSS entry specifies whether the local system uses Symantec product
authentication and authorization.
UNIX master server. Or, change the Symantec product authentication and
authorization property in the Access Control host properties to Required,
Prohibit, or Automatic.
Volume I.
USE_VXSS = REQUIRED | PROHIBITED | AUTOMATIC
Where:
REQUIRED indicates that the local system always uses Symantec product
authentication and authorization. Connections from systems not using
Symantec product authentication and authorization are rejected.
PROHIBITED indicates that the local system never uses Symantec product
authentication and authorization. Connections from systems using Symantec
product authentication and authorization are rejected (default).
AUTOMATIC indicates that the local system negotiates with the remote system
whether to use Symantec product authentication and authorization.
If USE_VXSS = AUTOMATIC is specified, VXSS_NETWORK entries can be used
to require or prohibit Symantec product authentication and authorization
connections with specified remote systems. See VXSS_NETWORK for an
example using USE_VXSS = AUTOMATIC.
VERBOSE
Used for debugging purposes, the VERBOSE option controls the amount of
information NetBackup includes in its legacy logs. Default: Disabled.
UNIX master server. Or, change the Global logging level property in the Logging
host properties.
Volume I.
VERBOSE = [ 0 | 1 | 2 | 3 | 4 | 5 ]
VXSS_NETWORK
The VXSS_NETWORK entry identifies whether a specific network or remote
system must or must not use Symantec product authentication and
authorization with the local system.
If a media server or client does not define a Symantec product authentication
and authorization network, it uses the Symantec product authentication and
authorization networks of its master server.
UNIX master server. Or, change the networks list property in the Access Control
host properties.
Volume I.
VXSS_NETWORK is relevant only if USE_VXSS is set to AUTOMATIC
(USE_VXSS = AUTOMATIC). More than one VXSS_NETWORK entry can be
specified.
VXSS_NETWORK = hostname | IP_address | .domain | network.
[AUTOMATIC | REQUIRED | PROHIBITED]
Possible values:
■ hostname
The host name of the remote system.
■ IP_address
The IP address of the remote system.
■ .domain
A dot followed by the Internet domain name of the remote systems.
■ network.
The network of the remote systems followed by a dot.
The optional second value can be one of the following keywords:
■ AUTOMATIC
■ REQUIRED
■ PROHIBITED
Note: If a system is specified by more than one VXSS_NETWORK entry, the first
occurance takes precedence.
Example
USE_VXSS = AUTOMATIC
VXSS_NETWORK = fred.mycompany.com
VXSS_NETWORK = 10.0.0.37 REQUIRED
VXSS_NETWORK = 10.0.0. PROHIBITED
VXSS_NETWORK = .theircompany.com
VXSS_NETWORK = wilma.theircompany.com PROHIBITED
VXSS_NETWORK = barney.mycompany.com PROHIBITED
In the example, Symantec product authentication and authorization is required

for connections between the local system and the system with host
fred.mycompany.com.
Symantec product authentication and authorization is required for connections
between the local system and the system with IP address 10.0.0.37.
Symantec product authentication and authorization is prohibited for
connections between the local system and systems in the 10.0.0 network
except for 10.0.0.37.
between the local system and systems within the theircompany.com Internet
domain.
between the local system and the system with host name
wilma.theircompany.com despite the PROHIBITED entry for
wilma.theircompany.com. The REQUIRED entry for .theircompany.com
takes precedence.
Symantec product authentication and authorization is prohibited for
connections between the local system and the system with host name
barney.mycompany.com
bp.conf options for UNIX clients

On NetBackup UNIX clients, the main bp.conf file is located in the following
pathname:
/usr/openv/netbackup/bp.conf
NetBackup uses internal software defaults for all options in the bp.conf file,
except SERVER. During installation, NetBackup sets the SERVER option to the
name of the master server where the software is installed.
Note: The SERVER option must be in the /usr/openv/netbackup/bp.conf

file on all NetBackup UNIX clients. It is also the only required entry in this file.
If a UNIX system is both a client and a server, both the server and the client
options are in the /usr/openv/netbackup/bp.conf file.
Each nonroot user on a UNIX client can have a personal bp.conf file in their
home directory as follows:
$HOME/bp.conf
The options in personal bp.conf files apply only to user operations. During a
user operation, NetBackup checks the $HOME/bp.conf file before
/usr/openv/netbackup/bp.conf. Root users do not have personal bp.conf
files. NetBackup uses the /usr/openv/netbackup/bp.conf file for root
users.
The following topics describe the options that you can specify in the
/usr/openv/netbackup/bp.conf and $HOME/bp.conf files on a
NetBackup UNIX client.
Note: PC clients provide similar options that you can change either through the
client-user interface or in a configuration file, depending on the client. For
instructions, see the online help in the Backup, Archive, and Restore client
interface.
ALLOW_NON_RESERVED_PORTS
The ALLOW_NON_RESERVED_PORTS entry specifies that the NetBackup client
daemon (bpcd) can accept remote connections from non-privileged ports (port
numbers 1024 or greater). If this entry is not present, then bpcd requires
remote connections to come from privileged ports (port numbers less than
1024). This option can be useful when NetBackup clients and servers are on
opposite sides of a firewall.
UNIX client.
In addition, run the following commands as root on the master server.
cd /usr/openv/netbackup/bin/admincmd
./bpclient -client client_name -add -connect_nr_port 1

Where client_name is the name of the client where you added the
ALLOW_NON_RESERVED_PORTS option. These commands instruct the master
server to use nonprivileged ports.
AUTHENTICATION_DOMAIN
The AUTHENTICATION_DOMAIN entry defines a set of VxSS authentication
principals. A client that uses VxSS must have at least one
AUTHENTICATION_DOMAIN entry, and more than one can be specified.
For more information, see “AUTHENTICATION_DOMAIN” on page 33 for more
information.
If a media server or client does not define an authentication domain, it uses the
authentication domains of its master server.
UNIX client. Or, set the Authentication Domains in the Access Control
properties under client host properties.
For more information, see “Authentication Domain tab within the Access
Control properties” on page 368 in the NetBackup Administrator’s Guide,
Volume I.
BPARCHIVE_POLICY
The BPARCHIVE_POLICY entry specifies the name of the policy to use for user
archives. Default: BPARCHIVE_POLICY is not in any bp.conf file and
NetBackup uses the first policy that it finds that has the client and a user
archive schedule.
For example:
BPARCHIVE_POLICY = arch_1
You can add this option to the /usr/openv/netbackup/bp.conf and
$HOME/bp.conf files on a UNIX client.
The value in the user’s $HOME/bp.conf file takes precedence if it exists.
BPARCHIVE_SCHED
The BPARCHIVE_SCHED entry specifies the name of the schedule for user
archives. Default: BPARCHIVE_SCHED is not in any bp.conf file and NetBackup
uses the first archive schedule in the first policy that it finds that has this client.
For example
BPARCHIVE_SCHED = user_arch1
BPBACKUP_POLICY
The BPBACKUP_POLICY entry specifies the name of the policy name to use for
user backups. Default: BPBACKUP_POLICY, is not in any bp.conf file and
NetBackup uses the first policy it finds that has both the client and a user
backup schedule.
For example:
BPBACKUP_POLICY = userback_1
You can add this option to the /usr/openv/netbackup/bp.conf and (or)
The value in user’s $HOME/bp.conf file takes precedence if it exists.
BPBACKUP_SCHED
The BPBACKUP_SCHED entry specifies the name of the schedule to use for user
backups. Default: BPBACKUP_SCHED is not in any bp.conf file and NetBackup
uses the first policy it finds that has both the client and a user backup schedule.
For example:
BPBACKUP_SCHED = user_back1
BUSY_FILE_ACTION
The BUSY_FILE_ACTION entry directs the action that NetBackup performs on
busy files when busy-file processing is enabled.

There can be multiple entries of the following form:
BUSY_FILE_ACTION = filename_template action_template
Where
■ filename_template is the absolute pathname and file name of the busy
file. The shell language metacharacters *, ?, [], [ - ] can be used for
matching patterns of filenames or parts of filenames.
■ action_template is one of the following:
MAIL | mail
Directs NetBackup to email a busy file notification message to the user
that the BUSY_FILE_NOTIFY_USER option specifies.
REPEAT | repeat [repeat_count]
Directs NetBackup to retry the backup on the specified busy file. A
repeat count can be specified to control the number of backup
attempts. The default repeat count is 1.
IGNORE | ignore
Directs NetBackup to exclude the busy file from busy file being
processed.
BUSY_FILE_DIRECTORY
The BUSY_FILE_DIRECTORY entry specifies the path to the busy-files working
directory when busy-file processing is enabled. Default:
BUSY_FILE_DIRECTORY is not in any bp.conf file and NetBackup creates the
busy_files directory in /usr/openv/netbackup.
The value in the user’s $HOME/bp.conf file takes precedence, if it exists.
BUSY_FILE_NOTIFY_USER
The BUSY_FILE_NOTIFY_USER entry specifies the recipient of the busy file
notification message when BUSY_FILE_ACTION is set to MAIL or mail. Default:
BUSY_FILE_NOTIFY_USER is not in any bp.conf file and the email recipient is
root.
The value in the user’s $HOME/bp.conf file takes precedence, if it exists.
BUSY_FILE_PROCESSING
The BUSY_FILE_PROCESSING entry allows the user to control NetBackup
actions when a file changes while being backed up. Default:
BUSY_FILE_PROCESSING option is not in bp.conf and busy-file processing
does not occur.
For more information, see “Busy file processing (UNIX clients only)” on
page 105 for instructions on setting this option.
UNIX client.
CLIENT_NAME
The CLIENT_NAME entry specifies the name of the client as it is known to
NetBackup. There can be one CLIENT_NAME entry and it must match the name
that is used in any policy that backs up the client. An exception is for an
alternate-client restore, where the name must match that of the client whose
files are to be restored.
For more information, see “Client-redirected restores” on page 673.
The client installation procedures automatically set CLIENT_NAME to the value
that is specified on the ftp_to_client or install_client command in the
installation scripts.
UNIX client.
The option can also be added to a $HOME/bp.conf file on a UNIX client.
However, the option is usually added only for alternate-client restores.
If the value is not in any bp.conf file, NetBackup uses the value that is returned
by the gethostname() library function.
CLIENT_PORT_WINDOW
The CLIENT_PORT_WINDOW entry specifies the range of nonreserved ports on
this computer that are used for connecting to NetBackup on other computers.
For more information, see “CLIENT_PORT_WINDOW” on page 41.
CLIENT_READ_TIMEOUT
Th CLIENT_READ_TIMEOUT entry specifies the number of seconds for the
client-read timeout on a server or a database agent.
For more information, see “CLIENT_READ_TIMEOUT” on page 42.
CLIENT_RESERVED_PORT_WINDOW
The CLIENT_RESERVED_PORT_WINDOW entry specifies the range of reserved
ports on this computer that are used for connecting to NetBackup on other
computers.
For more information, see “CLIENT_RESERVED_PORT_WINDOW” on page 43.
COMPRESS_SUFFIX
Note: The COMPRESS_SUFFIX entry has a reasonable default and has to be

changed only if problems are encountered.
The COMPRESS_SUFFIX entry specifies a list of file extensions. During a

backup, NetBackup does not compress files with these extensions because the
file can already be in a compressed format. Default, COMPRESS_SUFFIX is not in
the bp.conf file.
For more information, see “Compression” on page 105.
You cannot use wildcards to specify these extensions. For example, you can
specify the following:
.A1
You cannot specify either of the following:
.A* or .A[1-9]
UNIX client.
CRYPT_CIPHER
Note: The CRYPT_CIPHER entry applies to clients with the NetBackup

Encryption option installed. For information on NetBackup Encryption, see the
NetBackup Encryption Administrator’s Guide.
The CRYPT_CIPHER entry on the client takes one the following values:
■ AES-128-CFB (used when no method is specified; default)
■ AES-256-CFB
■ BF-CFB
■ DES-EDE-CFB
This client property can also be configured on the Encryption host properties
dialog box for each client.
CRYPT_KIND
Note: The CRYPT_KIND entry applies to 5.1 clients with the NetBackup
The CRYPT_KIND entry on the client determines whether the standard

encryption or legacy encryption is used in the backup. Normally, CRYPT_KIND is
set automatically. The following values that can be entered:
NONE = No encryption is used on the client (default)
LEGACY = Use on NetBackup clients running versions previous to 5.1.
Legacy pertains to 40-bit and 56-bit Data Encryption Standard (DES).
STANDARD = Use on NetBackup 5.1 clients to use the 128-bit and 256-bit
options of NetBackup Encryption.
CRYPT_OPTION
Note: The CRYPT_OPTION entry applies to clients with the NetBackup

The CRYPT_OPTION entry specifies the encryption options on NetBackup

clients. NetBackup creates this entry automatically in the
/usr/openv/netbackup/bp.conf file on a UNIX client when you run the
bpinst_crypt command on the NetBackup master server.
Do not alter the entry or create this file manually unless it has been accidentally
deleted. The allowable values follow:
DENIED|denied
Specifies that the client does not permit encrypted backups. If the server
requests an encrypted backup, it is considered an error. This option is the
default for a client that has not been configured for encryption.
ALLOWED|allowed
Specifies that the client allows either encrypted or unencrypted backups.

REQUIRED|required
Specifies that the client requires encrypted backups. If this value is

specified and the server requests an unencrypted backup, it is considered
an error.
CRYPT_STRENGTH
Note: The CRYPT_STRENGTH entry applies to clients with the NetBackup

Encryption option installed. See the NetBackup Encryption Administrator’s
Guide.
The CRYPT_STRENGTH entry specifies the encryption strength on NetBackup

clients. NetBackup creates this entry automatically in the
Do not alter the entry or create it manually unless it has been accidentally
deleted. The possible values follow:
DES_40|des_40
Specifies 40-bit DES encryption. 40-bit is the default value for a client that
has not been configured for encryption.
DES_56|des_56
Specifies 56-bit DES encryption.

CRYPT_LIBPATH
Note: The CRYPT_LIBPATH entry applies to clients with the NetBackup

Guide.
The CRYPT_KEYFILE entry specifies the directory that contains the encryption
libraries for NetBackup clients. NetBackup creates this entry automatically in
the /usr/openv/netbackup/bp.conf file on a UNIX client when you run
the bpinst_crypt command on the NetBackup master server.
deleted.
■ The following is the default value on UNIX systems:
/usr/openv/lib/
■ The following is the default value on Windows systems:

install_path\bin\
Where install_path is the directory where NetBackup is installed and by
default is C:\Program Files\VERITAS.
CRYPT_KEYFILE
Note: The CRYPT_KEYFILE entry applies to clients with the NetBackup

Guide.
The CRYPT_KEYFILE entry specifies the file that contains the encryption keys
on NetBackup clients. NetBackup creates this entry automatically in the
deleted. The default values follow:
■ On UNIX systems: /usr/openv/netbackup/keyfile
■ On Windows systems: install_path\bin\keyfile.dat
Where install_path is the directory where NetBackup is installed and by
default is C:\Program Files\VERITAS.
DISALLOW_SERVER_FILE_WRITES
The DISALLOW_SERVER_FILE_WRITES entry prevents the NetBackup server
from creating files on the NetBackup client. For example, this entry prevents
server-directed restores or server-directed updates of the bp.conf file on the
client.
UNIX client. By default, server writes are allowed.
DO_NOT_RESET_FILE_ACCESS_TIME
Note: The DO_NOT_RESET_FILE_ACCESS_TIME entry 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. When the atime is updated, it appears as
if the files are frequently used and prevents Storage Migrator from selecting the
files for migration.
The DO_NOT_RESET_FILE_ACCESS_TIME entry specifies that if a file is backed

up, its access time (atime) displays the time of the backup. Default: NetBackup
preserves the access time by resetting it to the value it had before the backup.
UNIX client.
GENERATE_ENGLISH_LOGS
The GENERATE_ENGLISH_LOGS entry enables the generation of an English
error log, and English trace logs for the bparchive, bpbackup, bpduplicate,
bpimport, and bprestore commands. This option is useful to support
personnel to assist in distributed environments where different locales result in
logs that contain various languages.
You can add this option to the /usr/openv/netbackup/bp.conf file on
NetBackup servers and clients.
IGNORE_XATTR
By default, extended attribute files (Solaris 9 or greater) and named data
streams are backed up. To exclude extended attributes and named data streams
from backups, add the IGNORE_XATTR entry to the
/usr/openv/netbackup/bp.conf file on the client. (IGNORE_XATTR was
formerly IGNORE_XATTR_SOLARIS.)
If IGNORE_XATTR is present in the bp.conf file, NetBackup does not check for
extended attributes or named data streams.
For more information, see “Backup and restore of extended attribute files and
named data streams” on page 180.
INFORMIX_HOME
The INFORMIX_HOME entry specifies the path to the Informix home directory
and is required when the client uses NetBackup for Informix.
You must add INFORMIX_HOME to the /usr/openv/netbackup/bp.conf file
on UNIX clients that are running NetBackup for Informix.
INITIAL_BROWSE_SEARCH_LIMIT
The INITIAL_BROWSE_SEARCH_LIMIT entry reduces the default number of
days back that NetBackup searches for files to restore.
You can add INITIAL_BROWSE_SEARCH_LIMIT to the
/usr/openv/netbackup/bp.conf file on NetBackup master servers and
clients.
For more information, see “INITIAL_BROWSE_SEARCH_LIMIT” on page 50.
KEEP_DATABASE_COMM_FILE
The KEEP_DATABASE_COMM_FILE entry causes NetBackup to keep database
agent logs for seven days. Default: NetBackup keeps database agent logs for only
one day.
You can add KEEP_DATABASE_COMM_FILE to the
/usr/openv/netbackup/bp.conf file on a UNIX database agent. For
example, add it to a client that is running NetBackup for Informix.
KEEP_LOGS_DAYS
The KEEP_LOGS_DAYS entry specifies how long to keep job and progress logs of
the NetBackup Java program, Backup, Archive, and Restore. NetBackup writes
these files in the usr/openv/netbackup/logs/user_ops/username/jobs
and /usr/openv/netbackup/logs/user_ops/username/logs directories.
A directory exists for each user that uses the Backup, Archive, and Restore
program. This entry also controls the number of days to keep the
NetBackup-Java GUI log files that are contained in
/usr/openv/netbackup/logs/user_ops/nbjlogs.
Default: Three days.
You can add KEEP_LOGS_DAYS to the /usr/openv/netbackup/bp.conf file
on a UNIX client.
LIST_FILES_TIMEOUT
The LIST_FILES_TIMEOUT entry specifies how long to wait for a response
from the server when it lists files by using the client-user interface or bplist. If
this time is exceeded, the user receives a socket read failed error even if
the server continues to process the user’s request. Default:
LIST_FILES_TIMEOUT is not in any bp.conf file and NetBackup uses a value
of 30 minutes.
LOCKED_FILE_ACTION
The LOCKED_FILE_ACTION entry specifies the behavior of NetBackup when it
backs up a file that has mandatory file locking enabled in its file mode. (See
chmod(1)). If LOCKED_FILE_ACTION is set to SKIP, NetBackup skips the files
that currently have mandatory locking set by another process. NetBackup logs a
message to this effect.
You can add LOCKED_FILE_ACTION to the
/usr/openv/netbackup/bp.conf files on a UNIX client. Default: NetBackup
waits for files to become unlocked.
Note: SKIP is the only legal value for this entry.
MEDIA_SERVER
The MEDIA_SERVER entry specifies that the listed machine is a media server
only. Machines that are listed as media servers can back up and restore clients,
but have limited administrative privileges.
MEGABYTES_OF_MEMORY
Note: The MEGABYTES_OF_MEMORY entry has a reasonable default and should

be changed only if problems are encountered.
The MEGABYTES_OF_MEMORY entry specifies how much memory is available on

the client to use to compress files 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 the compress code,
the greater the compression. The percentage of machine resources that are used
is also greater. If other processes also need memory, use a maximum value of
1/2 the actual physical memory on a machine to avoid excessive swapping.
UNIX client. Default: NetBackup assumes a value of one megabyte.
NFS_ACCESS_TIMEOUT
The NFS_ACCESS_TIMEOUT entry specifies the number of seconds that the
backup process waits to process an NFS mount table. After the time is exceeded,
the process considers an NFS file system to be unavailable.
UNIX client. Default: Timeout period is five seconds.
RANDOM_PORTS
The RANDOM_PORTS entry specifies whether NetBackup chooses port numbers
randomly or sequentially when it requires one for communication with
NetBackup on other computers.
For more information, see “RANDOM_PORTS” on page 57
RESTORE_RETRIES
Note: The RESTORE_RETRIES entry has a reasonable default and should be

changed only if problems are encountered.
The RESTORE_RETRIES entry specifies the number of times to retry a restore
after a failure. Default: 0 (no retries).
You can add RESTORE_RETRIES to the /usr/openv/netbackup/bp.conf
file on a UNIX client.
REQUIRED_INTERFACE
The REQUIRED_INTERFACE entry specifies the network interface that
NetBackup uses to connect to another NetBackup client or server.
For more information, see “REQUIRED_INTERFACE” on page 57.
SERVER_PORT_WINDOW
The SERVER_PORT_WINDOW entry specifies the range of nonreserved ports on
which this computer accepts connections from NetBackup on other computers.
SERVER
The SERVER entry defines the list of NetBackup master servers and media
servers that can access the NetBackup client. During client installation, the
SERVER is set to the name of the primary master server for this client. Other
SERVER entries can be added for any other master servers for this client, and for
media servers for this client. (Media servers for this NetBackup client can also
be added using the MEDIA_SERVER option.)
Note: Every SERVER entry in a client bp.conf file must be a NetBackup master
or media server. That is, each system listed as a SERVER must have either
NetBackup master or media server software installed. The client service on
some clients cannot be started if the client name is incorrectly listed as a server.
If you configure media servers, you must have a SERVER or MEDIA_SERVER

entry for each media server in the NetBackup client’s bp.conf file.
The following is an example bp.conf file on a client:
SERVER = Master_server (default master server)
SERVER = NBU_server (other master server)
.
The first SERVER entry denotes the master server to which the client connects
to by default for any requests. (For example, to back up, to list, or to restore
files). The SERVER entry must be present in the
/usr/openv/netbackup/bp.conf file on all UNIX clients. The SERVER entry
is the only required entry in the bp.conf file for clients. The SERVER entry is
not used in a $HOME/bp.conf file. On NetBackup UNIX servers, the SERVER
entry applies to both client and the server.
SYBASE_HOME
The SYBASE_HOME entry specifies the path to the Sybase home directory and is
required when using NetBackup for Sybase to back up Sybase databases.
Default: SYBASE_HOME is not in the bp.conf file.
You must add SYBASE_HOME to the /usr/openv/netbackup/bp.conf file on
a NetBackup for Sybase client.
Note: This entry is not required to back up the Sybase ASA that NetBackup uses
as part of the NetBackup catalog.
USE_CTIME_FOR_INCREMENTALS
Note: If you specify USE_CTIME_FOR_INCREMENTALS, you must also specify

DO_NOT_RESET_FILE_ACCESS_TIME.
Do not use these options 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. When the atime is updated, it appear as if the files are frequently
used and prevents Storage Migrator from selecting the files for migration.
The USE_CTIME_FOR_INCREMENTALS entry causes the NetBackup client

software to use both modification time (mtime) and inode change time (ctime)
during incremental backups to determine if a file has changed.
UNIX client. Default: NetBackup uses only mtime.
USE_FILE_CHG_LOG
The USE_FILE_CHG_LOG entry specifies whether NetBackup utilitzes the file
change log on VxFS clients. Default: off.
the client. Or, set the Use VxFS File Change Log for Incremental Backups
property in the UNIX Client Settings under client host properties.
Supported platforms are described in “Client Settings (UNIX) properties” on
page 397 in the NetBackup Administrator’s Guide, Volume I.
USE_VXSS
The USE_VXSS entry specifies whether the local system uses VxSS.

the client. Or, by setting the Symantec Product Authentication and
Authorization to Required in the Access Control properties under client host
properties.
For more information, see “Symantec Product Authentication and
Authorization” on page 365 in the NetBackup Administrator’s Guide, Volume I.
USEMAIL
The USEMAIL entry specifies the email address where NetBackup sends status
on the outcome of operations for a UNIX client. Default: USEMAIL is not present
in any bp.conf file and no email is sent.
Note: You can use multiple addresses or an email alias as long as no blanks or
white space appear between them.

■ If the /usr/openv/netbackup/bp.conf file specifies an address,
NetBackup sends automatic backup and manual backup status to that
address.
■ If the $HOME/bp.conf file specifies an address, NetBackup also sends
status on the success or failure of user operations to that address.
VERBOSE
The VERBOSE entry causes NetBackup to include more information in its logs.
Default: Disabled.
UNIX client.
VXSS_NETWORK
The VXSS_NETWORK entry identifies whether a specific network or remote
system must or must not use VxSS with the local system.
If a media server or client does not define a VxSS network, it uses the VxSS
networks of its master server.
For more information, see “VXSS_NETWORK” on page 64.
Use VXSS_NETWORK by adding it to the /usr/openv/netbackup/bp.conf
file on a UNIX client. Or, by adding the network to the Networks list in the
Access Control properties under client host properties.
For more information, see “Networks list” on page 366 in the NetBackup
UNIX client examples
Example /usr/openv/netbackup/bp.conf file

SERVER = hare
CLIENT_NAME = freddie
USEMAIL = abc@bdev.com
COMPRESS_SUFFIX = .Addrs
COMPRESS_SUFFIX = .Counts
VERBOSE = 1
RESTORE_RETRIES = 1
BPBACKUP_POLICY = U1userdir
BPBACKUP_SCHED = userbackups
BPARCHIVE_POLICY = U1userdir
BPARCHIVE_SCHED = userarchives
LOCKED_FILE_ACTION = SKIP
Example $HOME/bp.conf file

Nonroot users on UNIX clients can have a personal bp.conf file in their home
directory. A personal bp.conf file can have any of the following options
Note: A root user cannot have a personal bp.conf file. For root users,
NetBackup uses the /usr/openv/netbackup/bp.conf file.
USEMAIL = mars@bdev.com
BPBACKUP_POLICY = user1
BPBACKUP_SCHED = userback
BPARCHIVE_POLICY = user1
BPARCHIVE_SCHED = userarch
LIST_FILES_TIMEOUT = 10
CLIENT_NAME = alternate_client_name
Specify CLIENT_NAME only when doing restores to an alternate client.

For more information, see “Redirected restore examples” on page 676.
vm.conf options for media servers

The /usr/openv/volmgr/vm.conf file contains configuration entries for
media and device management. NetBackup may create this file, but if it does not
exist, it must be created to add entries.
The NetBackup component reads this configuration file on the host where the
component runs. The NetBackup component is a command, daemon, process, or
utility. The host may be a NetBackup administration client or a server where
administration operations are requested.
See “Example vm.conf file” on page 99 for an example configuration file.
ACS_mediatype
ACS_mediatype = Media_Manager_mediatype
This configuration entry applies only to NetBackup Enterprise Server

If this entry is used in vm.conf, the ACS media type is mapped to the specified
Media Manager media type. You can specify more than one ACS_mediatype
entry.
This entry is read and interpreted on the host on which vmcheckxxx and
vmupdate run during a robot inventory operation. Use this entry on every
NetBackup media server that functions as an ACS robot control host.
For a list of the valid ACS_mediatype entries, see “Media Type Mappings tab”
in the NetBackup Administrator’s Guide for UNIX and Linux, Volume I.
ACS_SEL_SOCKET
ACS_SEL_SOCKET = socket_name

By default, acssel listens on socket name 13740. If this entry is specified in
vm.conf, the default can be changed. This entry is read and interpreted on the
host on which acsd runs.
ACS_CSI_HOSTPORT
ACS_CSI_HOSTPORT = ACS_library_software_hostname socket_name

Valid value for ACS_library_software_hostname is the host name of the
ACS library host. Do not use the IP address of the ACS library host for this
parameter.
Valid values for socket_name are 1024 - 65535 and 0. The value must match
the value on the ACSLS server for the port that the CSI uses for inbound packets.
If 0 (zero), NetBackup uses the previous behavior of CSI and acsssi (no specific
ports).
This entry specifies the port where the acsssi process sends its ACSLS
requests on the ACSLS server. The ACSLS CSI must use this port to accept
inbound ACSLS requests from acsssi processes.
This entry and the ACS_SSI_INET_PORT and ACS_TCP_RPCSERVICE
entries are commonly used with firewall implementations. With these three
entries in the vm.conf file, TCP connections use the designated destination
ports. Note that TCP source ports are not restricted. Also see
“ACS_SSI_INET_PORT” on page 84 and “ACS_TCP_RPCSERVICE /
ACS_UDP_RPCSERVICE” on page 85.
For example, a NetBackup media server has two ACSLS servers (ACSLS_1 and
ACSLS_2) behind firewalls. Both servers listen for queries on port 30031 and the
firewall allows traffic through this port. The vm.conf entries are as follows:
ACS_TCP_RPCSERVICE
ACS_CSI_HOSTPORT = ACSLS_1 30031
ACS_SSI_INET_PORT = ACSLS_1 30032
Each acsssi process sends queries to the respective ACSLS server’s port 30031,
and the ACSLS server is configured to listen for queries on this port.
ACS_SSI_HOSTNAME
ACS_SSI_HOSTNAME = host

Use ACS_SSI_HOSTNAME to specify the host to which RPC return packets from
ACS library software are routed for ACS network communications. By default,
the local host name is used. This entry is read and interpreted on the host on
which acsd and acsssi run. Do not use the IP address of the host for this
parameter.
ACS_SSI_INET_PORT
ACS_SSI_INET_PORT = ACS_library_software_hostname socket_name

parameter.
The socket_name entry specifies the port that acsssi uses for incoming
ACSLS responses. Valid values are 1024 - 65535 and 0. This value must be
unique for each acsssi process.
A value between 1024 - 65535 indicates the number to be used as the TCP port
on which acsssi accepts ACSLS responses.
0 (zero) indicates that the previous behavior (allow the port to be dynamically
allocated) should remain in effect.
This entry and the ACS_CSI_HOSTPORT and ACS_TCP_RPCSERVICE entries
are commonly used with firewall implementations. With these three entries in
the vm.conf file, TCP connections use the designated destination ports. Note
that TCP source ports are not restricted. Also see “ACS_CSI_HOSTPORT” on
page 83 and “ACS_TCP_RPCSERVICE / ACS_UDP_RPCSERVICE” on page 85.
For example, a NetBackup media server has two ACSLS servers (ACSLS_1 and
ACSLS_2) behind firewalls. Ports 30032 and 300033 have been opened in the
firewall for acsssi to ACSLS server communication. The entries would be as
follows:
ACS_TCP_RPCSERVICE
The NetBackup media server starts two acsssi processes. One listens for
ACSLS_1 responses on port 30032, and the other listens on port 30033 for
responses from ACSLS_2.
ACS_SSI_SOCKET
ACS_SSI_SOCKET = ACS_library_software_hostname socket_name

parameter.
By default, acsssi listens on unique, consecutive socket names; the names
begin with 13741. If this entry is specified in vm.conf, specify socket names on
an ACS library software host basis. This entry is read and interpreted on the
host where acsd and acsssi are running.
ACS_TCP_RPCSERVICE / ACS_UDP_RPCSERVICE
ACS_TCP_RPCSERVICE
ACS_UDP_RPCSERVICE

These entries specify the method over which acsssi communicates with
ACSLS servers: TCP or UDP.
Only one entry should be entered into vm.conf. NetBackup uses UDP if both
entries are found or neither entry is found.
For acsssi firewall support, ACS_TCP_RPCSERVICE must be entered in
vm.conf (see “ACS_CSI_HOSTPORT” on page 83 and “ACS_SSI_INET_PORT”
on page 84).
ADJ_LSM
ADJ_LSM = robot_num ACS_ID,LSM_ID ACS_ID,LSM_ID
This configuration entry applies only to NetBackup Enterprise Server.

In an ACS robot with multiple library storage modules (LSMs), pass-through

mechanisms may move ejected media to the media access port (MAP). A
pass-through mechanism passes media from one LSM to another. This travel
time can be excessive when media must pass through several LSMs.
Use this entry to specify the physical orientation of the LSMs in an ACS robot. If
this entry is specified in vm.conf, you do not need to know which MAP (or ACS
CAP) to select for efficient ejects. NetBackup determines the appropriate MAP to
complete the media eject using a nearest-MAP algorithm.
This nearest-MAP algorithm is based on the physical orientation of the LSMs
that defined with this entry. This algorithm is only for the cases where more
than one MAP has been requested to handle the eject. If this algorithm is used,
any MAP_ID entries in vm.conf are ignored.
Note: The nearest-MAP capability is only available using the vmchange

command with the -map option or the Vault administrative interface. It is not
available from the NetBackup Administration Console.
Without this entry present, NetBackup assumes that all LSMs are
interconnected with pass-through ports, except for the first LSM and the last
LSM. The LSMs are interconnected in a line formation.
robot_num is the robot number. ACS_ID and LSM_ID are the coordinates of
the LSM.
For example, the following entries are required to specify the physical layout of
LSM interconnections for robot number 700 (Figure 1-2 on page 87):
ADJ_LSM = 700 0,0 0,1
ADJ_LSM = 700 0,0 0,6
ADJ_LSM = 700 0,1 0,2
ADJ_LSM = 700 0,1 0,6
ADJ_LSM = 700 0,2 0,6
ADJ_LSM = 700 0,2 0,3
ADJ_LSM = 700 0,3 0,4
ADJ_LSM = 700 0,4 0,5
The robot has pass-through mechanisms between 7 LSMs.

Figure 1-2 Pass-through example
Interconnections for
Robot 700 1
0 2
5 3
API_BARCODE_RULES
API_BARCODE_RULES

If this entry is specified in vm.conf, barcode rule support for API robots is
enabled.
NetBackup barcode rules allow default media mappings to be overridden.
Barcode rules are especially useful when multiple generations of the same tape
drive use the same type of media.
For example STK 9940A and STK 9940B drives use STK1R media, but write data
at different densities. The drive must be configured using different drive types
such as hcart or hcart2. You can specify a barcode rule for a series of barcodes to
configure some of the media as hcart2. Other STK1R media not in this barcode
range are configured as hcart (the default for STK1R). Without this entry, a
robot inventory operation configures all media of type STK1R as either hcart or
hcart2, depending on how the drive was configured.
AUTHORIZATION_REQUIRED
AUTHORIZATION_REQUIRED
This entry specifies that NetBackup should use the vm.conf file SERVER entry
to control which hosts can monitor and control devices on this host. This entry
is read and interpreted on the media server on which the NetBackup vmd service
runs.
If this entry is specified in vm.conf, the vm.conf file also must include a
SERVER entry for every media server that controls devices on this host.
If no AUTHORIZATION_REQUIRED entry exists and no SERVER entries exist, any
NetBackup server can monitor and control devices on this host.
For maximum security, Symantec recommends that you use this entry and
SERVER entries.
This entry is read and interpreted on media servers on which the NetBackup
vmd service runs.
AUTO_PATH_CORRECTION
AUTO_PATH_CORRECTION = YES|NO
If this entry is specified in vm.conf, it specifies whether automatic device path
remapping is enabled or disabled.
If the value is NO, the device configuration remains unchanged when the
NetBackup Device Manager service (ltid) is started. Therefore, the saved
device configuration may be different than the actual configuration after you
change devices and restart the server.
If the value is YES, NetBackup tries to discover attached devices and then
automatically update the device configuration for any device paths that are
incorrect. On Windows computers, this entry is read and interpreted on the host
on which the NetBackup Device Manager service runs. On UNIX and Linux
computers, this entry is read and interpreted on the host on which ltid runs.
Device path remapping is enabled by default on Windows and Linux servers. It is
disabled by default on all other servers.
AUTO_UPDATE_ROBOT
AUTO_UPDATE_ROBOT
Use this entry to inject media automatically from the Media Access Port (MAP)
into a TL8 or TLD robot and update the EMM database. Media are injected if the
robot generates a unit attention message.
This entry only operates with the TL8 or TLD robots that post a unit attention
when their MAP has been opened.
Symantec recommends that this entry not be used with partitioned libraries.
Most robotic libraries with multiple partitions do not post a unit attention when
the MAP has been opened.
AVRD_PEND_DELAY
AVRD_PEND_DELAY = number_of_seconds
If this entry is specified in vm.conf, avrd waits number_of_seconds before it

displays a pending status (PEND) in the Device Monitor. This entry is read and
interpreted on the host on which avrd runs.
On some server operating systems (Windows, Tru64, and HP-UX), NetBackup
reports PEND if the drive reports Busy when a volume is unmounted. Use this
entry to minimize the display of this misleading status.
The minimum for number_of_seconds is zero. The maximum is 255. The default
value is 180 seconds.
AVRD_SCAN_DELAY
AVRD_SCAN_DELAY = number_of_seconds
If this entry is specified in vm.conf, avrd waits number_of_seconds between
normal scan cycles. This entry is read and interpreted on the host on which
avrd runs.
Use this entry to minimize tape mount times. Without this entry, NetBackup
delays mount requests by an average of 7.5 seconds.
The minimum for number_of_seconds is 1. The maximum is 180. A value of zero
is converted to 1 second. The default value is 15 seconds. If a value is used that is
greater than the default, NetBackup delays mount requests and drive status
updates in the Device Monitor.
Caution: If number_of_seconds is set to a value that allows media to be changed

within one scan cycle, NetBackup may not detect media changes. Data loss may
occur.
CLEAN_REQUEST_TIMEOUT
CLEAN_REQUEST_TIMEOUT = minutes
Use this entry to specify how long NetBackup waits for a drive to be cleaned
before it removes the cleaning request from the cleaning queue. Unprocessed
requests to clean a drive are removed from the queue after 30 minutes.
minutes can be from 1 to 144000 (100 days). The default value is 30 and a value
of zero is converted to the default value of 30.
CLIENT_PORT_WINDOW
CLIENT_PORT_WINDOW = start end
Use this entry to specify the range of non-reserved ports on this host that are
used to connect to vmd on other hosts. This entry is read and interpreted on the
host on which vmd runs.
For example, the following entry permits ports from 4800 through 5000:
CLIENT_PORT_WINDOW = 4800 5000
The operating system determines the non-reserved port to use in the following
cases:
■ A CLIENT_PORT_WINDOW entry is not specified.
■ A value of zero is specified for start.
CLUSTER_NAME
CLUSTER_NAME = cluster_alias
This entry and the following two entries determine the name other NetBackup
servers and clients should use when they refer to this server:
MM_SERVER_NAME = host_name
REQUIRED_INTERFACE = host_name
The algorithm for determining the server name is as follows:

■ Use the CLUSTER_NAME entry if present in vm.conf.
■ Use the MM_SERVER_NAME entry if present in vm.conf.
■ Use the REQUIRED_INTERFACE entry if present in vm.conf.
■ Use the same name that NetBackup uses. The NetBackup name is configured
in the bp.conf file.
■ Use the gethostname() name.
This entry is read and interpreted on the host on which the required interface is
needed.
CONNECT_OPTIONS
CONNECT_OPTIONS = server_name 0 0 [0|1|2]
Add this entry in vm.conf to specify the options that enhance firewall
efficiency with NetBackup. Server connection options can be any of the
following: use vnetd or the daemon’s port number, use only vnetd, or use only
the daemon’s port number.
CONNECT_OPTIONS entries can be specified for multiple servers.
You can also use a similar entry and add it to the NetBackup configuration file
(/usr/openv/netbackup/bp.conf). For more information, see
“CONNECT_OPTIONS” on page 43.
server_name is the name of the media server to connect to. The server must be
at NetBackup level 4.5 or higher for vnetd to operate correctly.
The first and second options currently are not used. Specify zero for these
options.
The third option specifies the connection method to use to connect to

server_name as follows:
■ A value of 0 specifies to use vnetd to connect to a daemon on the server. If
vnetd is not active, connect by using the traditional port number of the
daemon.
■ A value of 1 specifies to use vnetd only to connect to a daemon on the
server.
■ A value of 2 specifies to use the traditional port number of the daemon to
connect to the daemon on the server. The default value is 2.
Examples
The following entry specifies to use either vnetd or the daemon’s port number
to connect to server shark:
CONNECT_OPTIONS = shark 0 0 0
The following entry specifies to use vnetd only to connect to server dolphin:
CONNECT_OPTIONS = dolphin 0 0 1
The following entry specifies to use the daemons’s port number only to connect
to server perch:
CONNECT_OPTIONS = perch 0 0 2
DAS_CLIENT
DAS_CLIENT = client_name

If this entry is specified in vm.conf, specify the DAS client name that the TLM
robot uses for communications with the DAS/SDLC server. By default this client
name is the host name of the media server. This entry is read and interpreted on
the host where tlmd is running.
DAYS_TO_KEEP_LOGS
DAYS_TO_KEEP_LOGS = days
If this entry is specified in vm.conf, specify the number of days to keep debug
logs before vmd deletes them. This entry is read and interpreted on the hosts
where vmd is running.
A value of zero means that the logs are not deleted. The default is zero. This
entry does not impact debug logs created by Unified Logging.
For more information about Unified Logging, see the NetBackup
Troubleshooting Guide for UNIX, Windows, and Linux.
EMM_RETRY_COUNT
EMM_RETRY_COUNT = number_of_retries
The vmd and the ltid daemons use this entry to determine how many times to
retry requests to the NetBackup Enterprise Media Manager.
Default: one retry.
Only change the value of this vm.conf file entry when directed to do so by your
NetBackup support representative. If you add this entry to the vm.conf file or
change this value, you must restart the vmd and the ltid daemons / services.
EMM_CONNECT_TIMOUT
EMM_CONNECT_TIMOUT = number_of_seconds
This value applies for broken connections between the vmd and the ltid
daemons and the NetBackup Enterprise Media Manager. The vmd and the ltid
daemons use this entry to determine for how long they should try to reconnect
to the NetBackup Enterprise Media Manager.
Default: 20 seconds.
EMM_REQUEST_TIMOUT
EMM_REQUEST_TIMOUT = number_of_seconds
The vmd and the ltid daemons use this entry to determine how many seconds
to allow a request to the NetBackup Enterprise Media Manager to complete.
Default: 300 seconds.
ENABLE_ROBOT_AUTH
NetBackup encourages the use of Symantec Product Authentication and
Authorization for NetBackup Access Control (NBAC) instead of legacy security
implementations.
For information about the ENABLE_ROBOT_AUTH configuration entry, see the
NetBackup 6.0 documentation. For information on Symantec Product
Authentication and Authorization, see the NetBackup Security and Encryption
Guide.
INVENTORY_FILTER
INVENTORY_FILTER = robot_type robot_number mode value1 [value2 ...]

Used to filter robot inventory results in ACS or TLH robot types. This entry must
be added to the configuration file (vm.conf) on the NetBackup server on which
the inventory operation is invoked. This entry is read and interpreted on the
host on which vmcheckxxx and vmupdate run.
Note: This entry may be required for an ACS robot and the ACS library software
host was an STK Library Station. Newer versions of STK Library Station allow
robot inventory commands to function correctly so filters are not required.
robot_type can be ACS or TLH.
robot_number is the number of the robot as was configured in NetBackup.
mode is BY_ACS_POOL for ACS or BY_CATEGORY for TLH.
See the following examples:
INVENTORY_FILTER = ACS 0 BY_ACS_POOL 4 5
INVENTORY_FILTER = TLH 0 BY_CATEGORY FFFA CDB0
MAP_ID
MAP_ID = robot_num map_ID

Use this entry to configure the default Media Access Port (MAP) to use to eject
media from Automated Cartridge System (ACS) robots. This default is
highlighted as a choice in the NetBackup Administration Console but you can
also select other Media Access Ports for ejects.
If the MAP is not available or the vm.comf file does not contain this entry,
NetBackup uses the default MAP selection process. By default, NetBackup uses
the smallest MAP that can hold the number of media to be ejected.
If NetBackup selects multiple MAPs, NetBackup uses the nearest-MAP
algorithm rather than the MAP that is specified in the MAP ID entry. For more
information, see “ADJ_LSM” on page 85.
robot_num is the robot number. map_ID is in the format of an ACS CAP
(Cartridge Access Port) ID and cannot contain any spaces.
The following example specifies the MAP ID for ACS robot number 700. The ACS
CAP ID of 0,1,0 is used.
MAP_ID = 700 0,1,0
MAP_CONTINUE_TIMEOUT
MAP_CONTINUE_TIMEOUT = seconds
This entry applies only when the vmchange command is used and the -w option
is specified. The default timeout value for seconds is 300 (5 minutes).
seconds cannot be zero and values greater than 1200 (20 minutes) may cause
the robotic daemon to cancel the operation.
If this entry is specified in vm.conf, the SCSI robotic daemons wait the
specified number of seconds before they time out. A timeout can occur while
waiting for a reply from the user to continue after removing volumes from the
media access port. A timeout results in the operation being aborted.
This entry is read and interpreted on the host on which the SCSI-controlled
robotic daemon or process runs.
Caution: Non-mount activities such as a robotic inventory can not occur during
this timeout period.
MEDIA_ID_BARCODE_CHARS
MEDIA_ID_BARCODE_CHARS = robot_num barcode_length media_ID_rule
Note: To use this entry, the robot must support barcodes and the robot type
cannot be an API robots.
If this entry is specified in vm.conf, it controls NetBackup media ID generation.

This entry is read and interpreted on the host on which vmcheckxxx and
vmupdate run as part of the robot inventory operation.
Choose how NetBackup creates media IDs by defining the rules that specify
which characters of a barcode on tape NetBackup uses. Alphanumeric
characters can be specified to be inserted in the ID.
Multiple entries can be added to the vm.conf file. For example, specify media ID
generation for each robot or for each barcode format that has different numbers
of characters. The multiple entries allow flexibility for multimedia.
If no MEDIA_ID_BARCODE_CHARS entries exist or the entry is invalid,
NetBackup uses the rightmost six characters of the barcode to create its media
ID.
robot_num is the robot number.
barcode_length is the length of the barcode.
A media_ID_rule consists of a maximum of six fields that colons delimit.
Numbers in the fields define the positions of the characters in the barcode that
NetBackup extracts (from left to right). For example, 2 in a field extracts the
second character from the barcode. The numbers can be specified in any order.
If the pound sign (#) prefixes a character, that character is inserted in that
position in the generated ID. Any alphanumeric characters must be valid for a
media ID. Use rules to create media IDs of many different formats. However, if
the generated media ID is different from the label on the media, media
management may be more difficult.
The following is an example rule and the resulting generated media ID:
Barcode on the tape: 032945L1
Media ID rule: #N:2:3:4:5:6
Generated media ID: N32945
MEDIA_ID_PREFIX
MEDIA_ID_PREFIX = media_id_prefix
If this entry is specified in vm.conf, it defines the media ID prefixes to use for
media without barcodes. This entry is read and interpreted on the host where
vmcheckxxx and vmupdate are running as part of the robot inventory
operation.
The best way to add media to a robot is to use the Robot Inventory Update
Volume Configuration operation.
MM_SERVER_NAME
This entry determines the name other NetBackup servers and clients should use
when they refer to this server:

needed.
PREFERRED_GROUP
NetBackup encourages the use of Symantec Product Authentication and
Authorization for NetBackup Access Control (NBAC) instead of legacy security
implementations.
For information about the PREFERRED_GROUP configuration entry, see the
NetBackup 6.0 documentation. For information on Symantec Product
Authentication and Authorization, see the NetBackup Security and Encryption
Guide.
PREVENT_MEDIA_REMOVAL
Applies to the TL8 robots only.
Specifying this entry changes the default operation for TL8 robots. Without this
entry present, NetBackup allows the removal of media.
If this entry is specified in vm.conf, TL8 robots execute the SCSI command
PREVENT MEDIUM REMOVAL. The robot's main door or the MAP cannot be
opened while the robotic control daemon runs.
This entry is read and interpreted on the host on which the TL8 robot control
daemon or process (tl8cd) runs.
To override PREVENT_MEDIA_REMOVAL
Do one of the following:
◆ Use the test utility and run allow media removal.
◆ Use inject or eject for access, when volumes are added or moved.
RANDOM_PORTS
RANDOM_PORTS = YES|NO
Use this entry to specify whether NetBackup chooses port numbers randomly or
sequentially for communication with other NetBackup servers. This entry is
read and interpreted on hosts on which vmd runs.
If YES or no entry exists (the default), NetBackup chooses port numbers
randomly from those that are available in the allowed range.
If NO, NetBackup chooses numbers sequentially. NetBackup begins with the
highest number in the allowed range, then tries the next highest, and so on until
a port is available.
If random ports are not specified in the NetBackup configuration, specify
RANDOM_PORTS = NO in the vm.conf file.
For more information, see “RANDOM_PORTS” on page 57.
To specify no random ports in the NetBackup configuration file

◆ Do one of the following:
■ Specify RANDOM_PORTS = NO in the bp.conf file on UNIX.
■ Use the NetBackup Host Properties on Windows.
REQUIRED_INTERFACE
This entry and the following two entries determine the name other NetBackup
servers should use when they refer to this server:

needed.
A NetBackup server can have more than one network interface, and by default
the operating system determines the one to use. To force NetBackup to connect
through a specific network interface, use REQUIRED_INTERFACE and specify
the network host name of that interface.
SERVER
SERVER = host_name
SERVER entries in the vm.conf file are used for NetBackup media server
security. The SERVER entries work with the AUTHORIZATION_REQUIRED entry
to control which hosts can monitor and control devices on this host.
If the AUTHORIZATION_REQUIRED entry exists, the vm.conf file must include
a SERVER entry for every media server that controls devices on this host. If the
vm.conf file contains any SERVER entries, it also must include a SERVER entry
for itself or it cannot manage its own devices.
If no AUTHORIZATION_REQUIRED entry exists and no SERVER entries exist, any
NetBackup server can monitor and control devices on this host.
For security, the entries that allow only specific hosts to access the devices must
be added remotely.
This entry is read and interpreted on media servers on which the NetBackup
vmd service runs.
SSO_DA_REREGISTER_INTERVAL
SSO_DA_REREGISTER_INTERVAL = minutes

This vm.conf entry is for the Shared Storage Option (SSO) for Tape feature
only. It is read and interpreted on the host on which ltid runs.
ltid on a scan host periodically registers its shared drives with EMM/DA to
ensure that it is still provides the drive scanning function. Only one of the hosts
that share a drive scan the drive. This reregistration allows conditions such as a
device allocator restart to have minimal impact on use of shared drives.
The default for the reregistration interval is 5 minutes. Use the
SSO_DA_REREGISTER_INTERVAL entry to tune this interval. After the entry is
added, stop and restart ltid for the change to take effect.
SSO_DA_RETRY_TIMEOUT
SSO_DA_RETRY_TIMEOUT = minutes

If ltid encounters problems during communications with EMM/DA or a failure
while trying to reserve a shared drive, ltid delays before trying again.
The default value for the delay is 3 minutes. Use the SSO_DA_RETRY_TIMEOUT
entry to tune this delay period. After the entry is added, stop and restart ltid
for the change to take effect.
SSO_HOST_NAME
SSO_HOST_NAME = host_name

This entry specifies the name that the current host uses to register, reserve, and
release shared drives with EMM/DA. The default is the local host name.
TLH_mediatype
TLH_mediatype = Media_Manager_mediatype

Dynamic host name and IP addressing
If this entry is specified in vm.conf, IBM ATL media types in Tape Library
Half-inch (TLH) robots are mapped to Media Manager media types. This entry is
read and interpreted on the host where vmcheckxxx and vmupdate are
running as part of the robot inventory operation.
TLM_mediatype
TLM_mediatype = Media_Manager_mediatype

If this entry is specified in vm.conf, DAS/SDLC media types in Tape Library
Multimedia (TLM) robots are mapped to Media Manager media types. This entry
is read and interpreted on the host where vmcheckxxx and vmupdate are
running as part of the robot inventory operation.
VERBOSE
If this entry is specified in vm.conf, all Media Manager components on the host
are started with verbose logging enabled.
Use this option only if problems occur or if requested by Symantec support.
After the problem is resolved, remove the debug logs or add a
DAYS_TO_KEEP_LOGS entry.
Example vm.conf file

The following is an example of a vm.conf file, on host server1:
SERVER = server1
SERVER = server2
MEDIA_ID_PREFIX = NV
MEDIA_ID_PREFIX = NETB
ACS_3490E = HCART2

By default, a NetBackup server assumes that a NetBackup client name is the
same as the network host name of the client machine. This assumption makes it
difficult to back up any clients that have network host names that might change.
For example, a portable machine that plugs into a LAN and obtains IP addresses
from a DHCP server. Or, a remote machine that dials into a PPP server.
NetBackup dynamic host name and IP addressing allows you to define
NetBackup clients that do not have fixed IP addresses and host names.
Note: If you use dynamic addressing, remember that the NetBackup servers still
require fixed IP addresses and host names.
Note: All clients configured to use dynamic addressing and host names must
trust each other, similar to the NetBackup altnames feature.
The following steps are required to support the configurations that use dynamic
IP addressing for NetBackup. Before you make changes to a configuration, read
this entire section.
1 Configure your network to use a dynamic IP addressing protocol like DHCP.
NetBackup requires that IP addresses of clients have a network host name.
Be sure to define network host names for the range of dynamic IP addresses
in the hosts file, NIS, and (or) DNS on your network.
2 Determine the NetBackup client names for the machines that have dynamic
IP addresses and network host names.
These NetBackup client names are used in step 3 and step 6. Each
NetBackup client must have a unique NetBackup client name. The
NetBackup client name that is assigned to a client is permanent—do not
change it.
3 Make changes on the master server:
a Create NetBackup policies with client lists that include the names from
step 2.
b Create entries in the NetBackup client database for the client names
from step 2.
Create the entries by using the bpclient command.
4 Make changes on each dynamic NetBackup Windows client:
Start the Backup, Archive, and Restore user interface on the client. Select
File > NetBackup Client Properties. The NetBackup Client Properties dialog
box appears. Select the General tab. Change the Client Name to the correct
NetBackup client name for the machine.
5 On the master server, enable the Announce DHCP Interval option:
Open the NetBackup Administration Console and navigate to the Host
Properties for clients. (Select NetBackup Management > Host Properties >
Clients.) Open the client properties for the Windows client(s). Under the
Windows Client host properties, select Network. Check the Announce DHCP
Interval checkbox.
6 Make changes on each dynamic NetBackup UNIX client:
a Modify the bp.conf file to include a CLIENT_NAME entry with the
correct NetBackup client name for the machine.
b Configure the system to notify the master server of the machine's

NetBackup client name and current network host name during startup.
The bpdynamicclient command is used to notify the master server.
c Configure the system to notify periodically the master server of the
machine's NetBackup client name and current network host name.
Setting up dynamic IP addresses and host names

Configure your network to use a dynamic IP addressing protocol. A protocol like
DHCP has a server and several clients. For example, when a DHCP client starts
up, it requests an IP address from the DHCP server. The server then assigns an
IP address to the client from a range of predefined addresses.
NetBackup requires that the IP addresses of NetBackup clients have
corresponding network host names. Ensure that each IP address that could be
assigned to NetBackup clients has a network host name. The host name should
be defined in the host file, NIS, and DNS on your network.
As an example, suppose that you have 10 dynamic IP addresses and host names
available. The dynamic IP addresses and host names might be:
123.123.123.70 dynamic00
123.123.123.71 dynamic01
123.123.123.72 dynamic02
123.123.123.73 dynamic03
123.123.123.79 dynamic09
Assign a unique NetBackup client name to each NetBackup client that might use
one of these dynamic IP addresses. The NetBackup client name that is assigned
to a client is permanent and should not be changed. The client name that is
assigned to NetBackup clients with dynamic IP addressing must not be the same
as any network host names on your network. If the NetBackup client names are
changed or are not unique, backup and restore results are unpredictable.
For example, suppose you have 20 machines that share the IP addresses as
previously defined. If you want these machines to be NetBackup clients, you
might assign them these NetBackup client names as follows:
nbclient01
nbclient02
nbclient03
nbclient04
nbclient20

Configuring the NetBackup master server

On the master server, create your NetBackup backup policies. For client name
lists, use the NetBackup client names (for example, nbclient01) rather than the
dynamic network host names (for example, dynamic01).
Next, create the client database on the master server. The client database
consists of directories and files in the following directory:
/usr/openv/netbackup/db/client
You can create, update, list, and delete client entries with the bpclient
command. The bpclient command is in the following directory:
/usr/openv/netbackup/bin/admincmd
■ To create a dynamic client entry:
bpclient -add -client client_name -dynamic_address 1
where client_name is the NetBackup client name. The
-dynamic_address 1 argument indicates that the client uses dynamic IP
addressing. You can create entries with -dynamic_address 0 for static IP
addressing, but that is unnecessary and adversely affects performance.
■ To delete a client entry:
bpclient -delete -client client_name
■ To list a client entry:

bpclient -L -client client_name
■ To list all client entries:

bpclient -L -All
In our example, you can enter these commands to create the 20 clients:
cd /usr/openv/netbackup/bin/admincmd
bpclient -add -client nbclient01 -dynamic_address 1
To see what is currently in the client database, run bpclient as follows:

/usr/openv/netbackup/bin/admincmd/bpclient -L -All
The output is similar to the following:
Client Name: nbclient01
Current Host:
Hostname: *NULL*
IP Address: 0.0.0.0
Connect on non-reserved port: no
Dynamic Address: yes

Current Host:
Hostname: *NULL*
IP Address: 0.0.0.0
Current Host:
Hostname: *NULL*
IP Address: 0.0.0.0
The NetBackup client notifies the NetBackup server of its NetBackup client
name and network host name. Then, the Current Host, Hostname, and IP
Address fields display the values for that NetBackup client.
Configuring a dynamic Microsoft Windows client

If it is not already installed, install NetBackup on the Windows client.
Start the Backup, Archive, and Restore user interface on the client and then
select File > NetBackup Client Properties. The NetBackup Client Properties
dialog box appears. Select the General tab. Change the Client Name to specify
the NetBackup client name for the Windows client.
In the NetBackup Administration Console, set Announce DHCP Interval. This
value specifies how many minutes the client waits before it announces that it
will use a different IP address.
For more information, see “Announce DHCP interval” on page 455 in the
The server is not notified if the default value of 0 is used. For a DHCP client, a
good value to use is one-half of the lease period.
On the client, stop and restart the NetBackup Client service to have the changes
take effect.
Configuring a dynamic UNIX NetBackup client

If not already installed, install the NetBackup client software.
Edit the /usr/openv/netbackup/bp.conf file. Use the CLIENT_NAME entry
to specify the NetBackup client name for the machine, as follows:
CLIENT_NAME = nbclient00
You must run the bpdynamicclient command once when the system first
starts up. bpdynamicclient notifies the NetBackup server of the machine's
NetBackup client name and current network host name. The

bpdynamicclient command is in the directory:
/usr/openv/netbackup/bin
The format of the bpdynamicclient command is as follows:
bpdynamicclient -last_successful_hostname file_name
When bpdynamicclient starts up, it checks for the existence of file_name.
If file_name exists, bpdynamicclient determines if the host name that is
written in the file is the same as the current network host name. If the host
names match, bpdynamicclient exits and does not connect to the master
server. If the host names do not match, bpdynamicclient connects to the
master server and informs the server of its NetBackup client name and host
name. If bpdynamicclient successfully informs the server,
bpdynamicclient writes the current network host name into file_name. If
bpdynamicclient cannot inform the server, bpdynamicclient deletes
file_name.
Most UNIX systems provide a facility to define startup scripts. For example, you
can create a script in the /etc/rc2.d directory on a Solaris system:
# cat > /etc/rc2.d/S99nbdynamicclient <<EOF
#! /bin/sh
rm /usr/openv/netbackup/last_successful_hostname
/usr/openv/netbackup/bin/bpdynamicclient
-last_successful_hostname \
/usr/openv/netbackup/last_successful_hostname
EOF
# chmod 544 /etc/rc2.d/S99nbdynamicclient
Ensure that the dynamic client startup script is called after the machine obtains
its IP address.
You must also create a root crontab entry to call periodically the
bpdynamicclient command. For example, the following entry (one line) calls
bpdynamicclient at seven minutes after each hour:
7 * * * * /usr/openv/netbackup/bin/bpdynamicclient
-last_successful_hostname
/usr/openv/netbackup/last_successful_hostname
If you use DHCP, a good interval to use between calls to bpdynamicclient is

one-half of the lease period.
Busy file processing (UNIX clients only)
Note: Busy file processing applies only to UNIX clients. For information
concerning Microsoft Windows clients, see “VSP (Volume Snapshot Provider)
properties,” in the NetBackup Administrator’s Guide, Volume I.
A busy file is a file that was detected as changed during a user or a scheduled
backup. Typically, detection occurs if a process writes to a file while NetBackup
attempts to back it up. The following conditions result in the detection of busy
files:
■ Read error on the file
■ File modification time changed
■ File inode time changed
■ File size changed
The backup usually completes with a status of 1, that indicates that the backup
was partially successful. Busy file processing allows the user control the actions
of NetBackup when busy files are detected.
Busy file processing can be configured in the Busy File Settings host properties
for UNIX clients. For more information, see Chapter 7, “Host properties,” in the
Busy file processing can also be enabled, by adding the
BUSY_FILE_PROCESSING option to the client
/usr/openv/netbackup/bp.conf file. Then, add other busy file options to
control the processing of busy files. The options can exist in both the client
/usr/openv/netbackup/bp.conf file and a user’s $HOME/bp.conf. The
user’s bp.conf file takes precedence when the options are in both places.
NetBackup creates several files and directories when processing busy files.
Initially, a working directory named busy_files is created under
/usr/openv/netbackup. NetBackup then creates the /actions directory
under busy_files and places action files in that directory. An action file
contains the information that NetBackup uses to control the processing of busy
files.
By default, the contents of the action file are derived from the
BUSY_FILE_ACTION options in bp.conf. A user can also create an action file
to control a specific backup policy and schedule. NetBackup creates a logs
directory under busy_files for storing busy file status and diagnostic
information.
For more information, see “Creating action files” on page 108.
Getting started
To use the bp.conf file to configure busy file processing, perform the following
steps:
■ Modify the bp.conf file options as described in the following section,
“Modifying bp.conf to configure busy file processing” on page 106.
Copy the bpend_notify_busy script:
/usr/openv/netbackup/bin/goodies/bpend_notify_busy
to the path:
/usr/openv/netbackup/bin/bpend_notify
Be sure to set the file access permissions to allow group and other to execute
bpend_notify.
(This step is also performed when configuring busy file processing in the
Busy File Settings host properties.)
■ 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 (upper-case characters first) for the first
available policy with a user backup schedule and an open backup window.
For example, a policy name of AAA_busy_files is selected ahead of
B_policy.
(This step is also performed when configuring busy file processing in the
Busy File Settings host properties.)
Modifying bp.conf to configure busy file processing

Configure busy file processing by using the Busy File Settings host properties
for UNIX clients.
For more information, see Chapter 7, “Host properties,” in the NetBackup
Or, configure busy file processing using the following entries in the bp.conf
file on the client. The user may also configure a bp.conf file in a home
directory. The busy file options specified in the user's bp.conf file apply only to
user-directed backups. NetBackup ignores busy file processing for user
backups, if a bp.conf file does not exist in their home directory.
The BUSY_FILE_PROCESSING entry enables the NetBackup busy
file-processing feature. By default, this entry is not present in the client’s
/usr/openv/netbackup/bp.conf file.
BUSY_FILE_DIRECTORY
The BUSY_FILE_DIRECTORY entry specifies an alternate path to the busy files
working directory. This entry is not required. By default, this entry is not
present in the client’s /usr/openv/netbackup/bp.conf or $HOME/bp.conf
file. By default, NetBackup creates the busy_files directory in
/usr/openv/netbackup or the user’s home directory.
BUSY_FILE_ACTION
The BUSY_FILE_ACTION entry directs the action that NetBackup performs on
busy files. By default, this entry is not present in the client’s
/usr/openv/netbackup/bp.conf or $HOME/bp.conf file.
Multiple entries may exist in the following form:
BUSY_FILE_ACTION = filename_template action_template
Where
■ filename_template is the absolute pathname and file name of the busy
file. The shell language metacharacters *, ?, [], [ - ] can be used to
match the patterns of file names or parts of file names.
■ action_template is one of the following:
MAIL | mail
Directs NetBackup to mail a busy file notification message to the user
that the BUSY_FILE_NOTIFY_USER option specifies.
REPEAT | repeat [repeat_count]
Directs NetBackup to retry the backup on the specified busy file. A
repeat count can be specified to control the number of backup
attempts. The default repeat count is 1.
IGNORE | ignore
Directs NetBackup to exclude the busy file from busy file processing.
The file is backed up and a log entry that indicates that the file was
busy appears in the All Log Entries report.
BUSY_FILE_NOTIFY_USER
This option specifies the recipient of the busy file notification message
when BUSY_FILE_ACTION is set to MAIL or mail. By default,
BUSY_FILE_NOTIFY_USER is not in
/usr/openv/netbackup/bp.conf or $HOME/bp.conf file on a
client. By default, the mail recipient is root.
Example 1
BUSY_FILE_DIRECTORY = /tmp
BUSY_FILE_NOTIFY_USER = kwc
BUSY_FILE_ACTION = /usr/* mail
BUSY_FILE_ACTION = /usr/local ignore
This set of options causes NetBackup to take the following actions when it
encounters busy files:
■ Create the busy files working directory in /tmp
■ Send an email notification message to user kwc for all busy files that it finds
under /usr except for those in /usr/local.
Example 2
BUSY_FILE_ACTION = /usr/* repeat 2
BUSY_FILE_ACTION = /usr/openv mail
This set of options causes NetBackup to take the following actions when it
encounters busy files:
■ Send a busy file notification message to root for busy files in /usr/openv.
■ Repeat the backup up to two times for all busy files that it finds under /usr,
except for those in /usr/openv and /usr/local.
■ Exclude the busy files in /usr/local from all actions.
Creating action files

When a backup operation begins, NetBackup creates a default action file named
actions in the busy_files/actions directory. The contents of the
actions file are derived from the BUSY_FILE_ACTION options in the bp.conf
file.
Normally, NetBackup refers to the default action file for all future busy file
processing. To override the default, create an action file to control a specific
backup policy and schedule. The following entries show the naming convention
for the policy and the schedule action files:
actions.policy_name.schedule_name
actions.policy_name
Where policy_name and schedule_name correspond to a predefined backup

policy and schedule.
NetBackup performs the following steps when it searches for an action file:
1 Checks for a file that names a specific policy and schedule, such as:
actions.policy_name.schedule_name
2 If a file for a specific policy and schedule is not found, NetBackup searches
for a less specific name, such as the following:
actions.policy_name
3 If a less specific name does not exist, NetBackup refers to the default action
file.
The contents of user-created action files are similar to the default. Optional
comment lines can be included. The specification is the same as for the
BUSY_FILE_ACTION option:
# comment_line
filename_template action_template
Example 1
The bp.conf file might contain the following:
BUSY_FILE_ACTION = /usr/openv mail
BUSY_FILE_ACTION = /usr/* repeat 2
If yes, the default actions file (named actions) contains the following lines:
/usr/openv mail
/usr/* repeat 2
/usr/local ignore
Example 2
An action file name for a backup policy production_servers with a schedule name
full follows:
actions.production_servers.full
The actions file can contain the following line:
/bin/* repeat
If yes, NetBackup repeats the backup for busy files in the /bin directory.
Logs directory
During busy file processing NetBackup creates a number of files under the
busy_files/logs directory. These files contain status and diagnostic
information. NetBackup derives the names of these files from the policy name,
schedule name, and process id (PID) of the backup.
■ Busy file log
NetBackup records the names of any busy files in the busy file log. The
name of the busy file log has the following form:
policy_name.schedule_name.PID
■ Diagnostic log file

NetBackup generates a log file that contains diagnostic information. The
name of the log file has the following form:
log.policy_name.schedule_name.PID
■ Retry log file
NetBackup also generates a retry file that contains diagnostic information

that is recorded when the repeat option is specified. The name of the retry
file has the following form:
policy_name.schedule_name.PID.retry.retry_count
Where retry_count starts at zero and increases by one every time a
backup is repeated. Processing stops when retry_count is one less than
the number that is specified by the repeat option.
Example
To service busy file backup requests, the administrator defined a policy named
AAA_busy_files that has a user backup schedule named user. A scheduled
backup is initiated with the policy named production_servers, schedule named
full, and PID of 1442.
If busy files are detected, NetBackup generates the following files in the
/usr/openv/netbackup/busy_files/logs directory:
production_servers.full.1442
log.production_servers.full.1442
If the actions file has the repeat count set to 2, NetBackup generates the
following files:
production_servers.full.1442.retry.0
AAA_busy_files.user.10639
log.AAA_busy_files.user.10639
If a repeat backup is attempted, NetBackup generates the following files:

production_servers.full.1442.retry.1
AAA_busy_files.user.15639
log.AAA_busy_files.user.15639
Modifying bpend_notify_busy
The administrator can modify busy file processing by changing the
bpend_notify_busy script. The only recommended changes are as follows:
■ Changing the RETRY_POLICY and RETRY_SCHED variables from NONE to
the busy file backup policy name and schedule name.
■ Remove the files in the logs directory after busy file processing (these logs
are not removed automatically):
a At the end of the busy_files() function, add the following command:
/bin/rm -f $LOG_FILE
b After the call to the busy_files() function in main, add the following
commands:
/bin/rm -f $BUSYFILELOG
/bin/rm -f $RETRY_FILE

Configuring email notifications
Configuring email notifications
You can configure NetBackup to send email notifications to users and

administrators with the results of backup, archive, and restore operations.
The types of notifications you can configure are as follows:
■ Notify server administrators when a scheduled backup,
administrator-directed manual backup, or a backup of the NetBackup
databases occurs.
Configure NetBackup to email these notifications by specifying the server
administrator’s address with the NetBackup master server Global Attribute
property, Administrator’s E-mail Address. For more information, see the
If you customize the dbbackup_notify script to include an email message
and recipient, this script also sends a message after each NetBackup
database backup.
■ Notify users on UNIX clients as to the success or failure of their user
operations.
To configure these notifications, specify the user’s email address with the
USEMAIL option in the user’s personal bp.conf file. This file is located in
the user’s home directory (create one if necessary).
■ Notify system administrators of UNIX clients about the success or failure of
scheduled or manual backups.
To configure these notifications, specify the client administrator’s address
with the USEMAIL option in the /usr/openv/netbackup/bp.conf file
on the client.
You can also set up email notifications with the scripts provided with NetBackup
UNIX server software.
For more information, see “Goodies scripts” on page 687 in the NetBackup

Specifying the locale of the NetBackup installation
Specifying the locale of the NetBackup installation

NetBackup applications can display a wide range of international date and time
formats as determined by the locale of the installation. To help ensure
consistency among the applications, NetBackup uses a single, configurable
source to define the locale conventions.
Table 1-2 To specify the locale of a NetBackup installation
Platform Directions
Windows To access the regional settings, double-click Regional and Language Options in the Windows
Control Panel. The Regional and Language Options dialog box provides access to the predefined
number, date, and time formats.
See the Microsoft Help pages for further assistance.
UNIX The /usr/openv/msg/.conf file contains information on the supported locales. This file
defines the date and the time formats for each supported locale.
The .conf file contains very specific instructions on how to add or modify the list of supported
locales and formats. However, the format of the file is summarized here.
The .conf file is divided into two parts, the TL lines and the TM lines.
TL Lines
The third field of the TL lines defines the case-sensitive locales that the NetBackup applications
support. The fourth and the fifth fields define the date and the time fields and associated
separators for that supported locale is as follows:
You can modify the existing formats to change the default output. For example, the TL line for the
C locale is:
TL 1 C :hh:mn:ss/mm/dd /yyyy
An alternate specification to the order of months, days, and years would be as follows:
TL 1 C :hh:mn:ss -yyyy-mm-dd
or:
TL 1 C :hh:mn:ss/dd /mm/yy
You can add more TL lines; see the comments in the .conf file.
If the .conf file is not accessible, the default locales (TL lines) are:
TL 1 C :hh:mn:ss /mm/dd /yyyy
TL 2 ov :hh:mn:ss/mm/dd /yyyy
Note that C and ov are synonymous.

Adjusting time zones in the NetBackup-Java console
Table 1-2 To specify the locale of a NetBackup installation (continued)
Platform Directions
TM Lines
The TM lines define a mapping from unrecognized locales to those supported by NetBackup, as
defined by the TL lines.
The third field of the TM lines defines the unrecognized locale. The fifth field defines the
supported equivalent that is identified in the TL lines.
For example, use the following TM line to map the unrecognized locale french to the supported
locale fr, the TM line is:
TM 6 french 2 fr
To map french to C
TM 6 french 1 C
To add more TM lines, see the specific instructions in the .conf file.
If the .conf file is not accessible, no default TM lines exist, as the default locale is C (ov).

Sites in a geographically dispersed NetBackup configuration may need to adjust
the time zone in the NetBackup-Java Console for administration of remote
NetBackup hosts. (In this context, a remote NetBackup host may either be the
host that is specified in the console login dialog box or one referenced by the File
> Change Server capability in the console.)
The default time zone for the console is that of the host on which the console is
started, not the host that is specified (if different) in the console login dialog
box.
■ For backup, restore or archive operations from within the NetBackup-Java
Console (jnbSA) or the Backup, Archive, and Restore application when run
on a client (jbpSA): the time zone should be set relative to the NetBackup
server from which the client restores files.
■ The time zone must be set in separate instances of the NetBackup-Java
Console when servers in different time zones are administered.
For example, open a NetBackup-Java Console to set the time zone for your
local server in the Central time zone. To set the time zone for a server in the
Pacific time zone as well, open another NetBackup-Java Console.
Do not open a new window in the first NetBackup-Java Console, change
servers (File > Change Server), then set the time zone for the Pacific time
zone server. Doing so changes the time zone for the Central time zone
server as well.
To set the time zone and daylight savings time

1 In the NetBackup Administration Console, or in the Backup, Archive, and
Restore client interface, select File > Adjust Application Time Zone. The
Adjust Time Zone dialog box appears.
2 To use the Standard tab to configure the time zone:
a Clear the Use custom time zone check box.
b Select the time zone.
c To use daylight savings time, select Use daylight savings time.
d To have administrative capabilities and apply the settings to the current
session and all future sessions, select Save as default time zone.
3 To use the Custom tab to configure the time zone:
a Select the Use custom time zone check box.
b Select the time zone on which to base the Backup, Archive, and Restore
interface time. For a list of time zones, see Time Zone Table.
c Adjust the time to reflect how many hours and minutes the server’s
time zone is offset (either behind or ahead) of Greenwich Mean Time.
d To use daylight savings time, select Use daylight savings time.
e Indicate when Daylight Savings Time (DST) should begin. Use one of
the following methods:
■ To begin DST on a specific date, select Absolute date and indicate
the month and day.
■ To begin DST on the first occurrence of a day in a month, select
First day of week in month. Indicate the day of the week and the
month.
■ To begin DST on the first occurrence of a day in a month and after
a specific date, select First day of week in month after date.
Indicate the day of the week and the month and day.
■ To begin DST on the last occurrence of a day in a month, select
Last day of week in month. Indicate the day of the week and the
month.
■ To begin DST on the last occurrence of a day in a month and before
a specific date, select Last day of week in month after date.
Indicate the day of the week and the month and day.
f Select the appropriate Day of week, Month, Day, and Time.
Select Absolute date to have DST begin on a To have DST begin on April 5:
specific date.
Indicate the month and day.
Select First day of week in month to have To begin DST on the first Monday in April:
DST begin on the first occurrence of a day in
a month.
Indicate the day of the week and the month.
Select First day of week in month after date To begin DST on the first Monday after April 5:
to have DST begin on the first occurrence of a
day in a month and after a specific date.
Indicate the day of the week and the month
and day.
Select Last day of week in month to have DST To begin DST on the last Thursday in April:
begin on the last occurrence of a day in a
month.
Indicate the day of the week and the month.
Select Last day of week in month after date To begin DST before April 30:
to have DST begin on the last occurrence of a
day in a month and before a specific date.
Indicate the day of the week and the month
and day.
g Indicate when DST should end, using one of the methods in step e.
h To have administrative capabilities and apply the settings to the current
session and all future sessions, select Save as default time zone.
4 Click OK.
Chapter 2
Menu user interfaces
The following menu user interfaces are available on UNIX or Linux systems to
manage NetBackup:
■ “Using the bpadm NetBackup management utility” on page 118
■ “Using the vmadm media management utility” on page 132
■ “Using the tpconfig device configuration utility” on page 144
■ “Using the disk configuration utility” on page 153
These utilities are alternatives to using the NetBackup Administration Console.
The terminology, general concepts, and results are the same regardless of the
administration method that is used.
118 Menu user interfaces

Using the bpadm NetBackup management utility

The NetBackup bpadm administrator utility is a character-based, menu-driven
interface. It can be used at any terminal (or terminal emulation window) for
which termcap or terminfo is defined.
Note: Use bpadm only on the master server. Make sure that no other instances of
bpadm or the NetBackup Administration Console are active while the
configuration is modified. To modify the configuration by using multiple
utilities may produce unpredictable results.
Start the bpadm program by running the bpadm command as a root user. bpadm
is located in the following directory:
/usr/openv/netbackup/bin
The main menu appears:

NetBackup Server: server_name
NetBackup Administration
-------------------------
d) Data Classification Management...
s) Storage ...
p) Policy Management...
g) Global Configuration...
f) Fibre Channel Transport Management...
r) Reports...
m) Manual Backups...
x) Special Actions...
u) User Backup/Restore...
e) Media Management...
o) Server Group Management...
h) Help
q) Quit
ENTER CHOICE:
All menus provide online help. For more information, the topics are discussed in
the corresponding chapter of the NetBackup Administrator’s Guide, Volume I.
Press the escape (Esc) key to abort most operations.
Data classification management

Use the Data Classifications menu to view, add, and modify data classifications:
Name: <ALL>
Description: <ALL>
Rank: <ALL>
Classification ID: <ALL>
Output Destination: SCREEN
Menu user interfaces 119

Data Classifications
-------------------------
a) Add Data Classification ...
m) Modify Data Classification ...
k) Modify Data Classification Ranks
b) Browse Data Classifications Forward
r) Browse Data Classifications Reverse
e) Enter
l) List/Display Data Classifications
o) Output Destination (SCREEN or FILE)
h) Help
q) Quit
Defining and managing storage units and storage unit groups

Use the Storage menu to define and manage storage units. To display the
Storage menu, press s (Storage...) on the bpadm main menu:
Storage
-------
u) Storage Unit Management ...
g) Storage Unit Group Management ...
s) Storage Lifecycle Policy Management ...
h) Help
q) Quit Menu
Defining and managing storage unit groups

A storage unit group is a list of storage units, ordered by priority. The Storage
Unit Group Management menu contains options to define and manage
storage unit groups. Create a storage unit group to define sets of storage units
and to assign priorities to one or more storage units.
To display this menu, press g while viewing the Storage main menu:
Storage Unit Group Label: <ALL>
Storage Unit Group Management
-----------------------------
a) Add Storage Unit Group...
m) Modify Storage Unit Group...
d) Delete Storage Unit Group
b) Browse Storage Unit Groups Forward
r) Browse Storage Unit Groups Reverse

e) Enter Storage Unit Group
l) List/Display Storage Unit Groups
o) Output Destination SCREEN or FILE)

h) Help
q) Quit Menu
ENTER CHOICE:
Defining and managing policies

Use the Policy Management menu to create and manage NetBackup policies.
To display the Policy Management menu, press p (Policy Management) on
the bpadm main menu.
Policy: <none>
Clients: <none>
Schedules: <none>
Policy Management
-----------------
a) Add Policy...
m) Modify Policy Attributes...
d) Delete Policy
s) Schedule Management...
c) Client List Management...
f) File List Management...
t) Catalog Backup Disaster Recovery...
b) Browse Policies Forward
r) Browse Policies Reverse
e) Enter Policy
l) List/Display Policies
h) Help
q) Quit Menu
ENTER CHOICE:
Configuring an online catalog backup

An online, hot catalog backup differs from the offline, cold catalog backup in
previous releases. A hot catalog backup is policy-based, which means that it has
all of the scheduling flexibility of a regular backup policy. The online catalog
backup is designed for use in highly active NetBackup environments with
constant backup activity and the catalog size is large.
Catalog backups are crucial to the ability to restore client data. For that reason,
the process for creating an online catalog backup is described here. Create an
online catalog backup as you would create a policy, from the Policy
Management menu.
To create an online catalog backup

1 From the NetBackup Administration menu, press p (Policy
Management).
2 From the Policy Management menu, press a (Add Policy).
3 Provide a name for the policy. The name must be unique to the configuration
and cannot contain any spaces.
4 Specify whether to use an existing policy as a template. The new policy can
be changed later. In this procedure, assume no policy is used as a template.
[1]
5 Select policy attribute 1) Policy Type, then enter policy type selection
21) NBU-Catalog.
6 The NBU-Catalog policy type presents the following policy configuration
options:
Modify Policy Attributes (<ESC> to quit)
-----------------------------------------
1) Policy Type/subtype : NBU-Catalog
2) Active : Yes
--) Collect True Image Recovery Information : Yes with move
detection
--) Cross mount points : Yes
--) Follow NFS mounts : Yes
--) Client Compression : No
--) Client encryption : No
--) Allow multiple data streams : No
--) Collect disaster recovery information : No
--) Collect BMR information : No
--) Maximum number of jobs per policy : 1
12) Required storage unit :
13) Volume pool : CatalogBackup
14) Server group : ANY
--) Granular Restore : No
16) Keyword :
17) Priority as compared to other policies : 0
--) Take checkpoints : No
19) Set Policy Attributes for Snapshot Client.
Note: NBU-Catalog policy types write to the CatalogBackup volume pool

by default.
7 If necessary, make any changes to other policy attributes.

8 When complete, press <ESC>, then press y to add the policy or n to cancel.
9 To create a schedule for the policy, from the Policy Management menu,
press s (Schedule Management).
10 From the Schedule Management menu, press a (Add Schedule).
11 Type a label for the schedule and press Return.
12 NBU-Catalog policy types allow the following schedule types:
Add Schedule (<ESC> to abort)
-----------------------------
Enter Schedule Label: full_sched
Schedule Type
-------------
0) Full Backup
1) Differential Incremental Backup
2) Cumulative Incremental Backup
3) Vault Catalog Backup
Enter Choice [0-3]: (0)
See the NetBackup Administrator’s Guide, Volume I for the details of adding
a schedule to a policy.
13 Disaster recovery information should be configured for NBU-Catalog
policies.
From the Policy Management menu, press t (Catalog Backup
Disaster Recovery). Disaster recovery information can only be
configured for NBU-Catalog policies:
Policy: catalog-backup
Modify Catalog Backup Disaster Recovery (<ESC> to quit)
-------------------------------------------------------
1) Disaster Recovery Email Address :
2) Disaster Recovery File Location :
3) User Name to Access File Location :
4) Password to Access File Location :
5) Critical policy :
Enter Choice (choices marked "--" are unavailable) [1-5]:
The Modify Catalog Backup Disaster Recovery menu contains the following
options:
1) Disaster Recovery Email Address
Prompts the user to:

Enter Email Address:
Symantec recommends that the policy is configured to send the disaster

recovery information to a NetBackup administrator. This backup-specific
information is sent after every online catalog backup.
To send the information to more than one administrator, separate multiple
email addresses using a comma: email1,email2
Make sure that email notification is enabled in the environment.
2) Disaster Recovery File Location

Enter DR Path:
Enter the path to the directory where the disaster recovery information is
to be saved. Specify an NFS share.
Note: Symantec recommends that the image file is saved to a network share
or a removeable device. Do not save the disaster recovery information to the
local machine.
3) User Name to Access File Location

Enter User Name:
If necessary, enter the logon name used to access the NFS share.
4) Password to Access File Location

Enter Password:
If necessary, enter the password information to access the NFS share. As it

is entered, the password is viewable on the screen. Once Return is pressed,
the password appears as eight asterisks.
5) Critical policy
A critical policy is considered crucial to the recovery of a site in the event of

a disaster. The policy must appear on the Critical Policies list. The list
appears in the configuration for a NBU-Catalog policy on the Disaster
Recovery tab.
14 Press <ESC>, then: press y to modify the policy or n to cancel.
Defining NetBackup global attributes

Use the Global Configuration Attributes menu to define aspects of
NetBackup operation that are not defined elsewhere in the configuration. To
display the Global Configuration Attributes menu, press g (Global
Configuration...) on the bpadm main menu:
Keep Logs: 2 days

Admin Mail Address: <none>
Job Retry Delay: 10 minutes
Policy Update Interval: 10 minutes
Preprocess Interval: 4 hours (default)
Backup Tries: 2 times in 12 hours
Maximum Backup Copies: 2
Global Configuration
--------------------
m) Modify Configuration Parameters...
l) List/Display All Configuration Parameters
h) Help
q) Quit Menu
Defining and managing Fibre Channel transport

Use the Fibre Channel Transport Management menu to define and
manage the NetBackup Fibre Channel and SAN clients. To display the Fibre
Channel Transport Management menu, press f (Fibre Channel
Transport Management) on the bpadm main menu:
Fibre Channel Transport Management
-----------------------------
c) SAN Client Management ...
s) FT Server Management ...
d) Defaults Configuration ...
r) FT Connection Report ...
h) Help
q) Quit
ENTER CHOICE:
Alternatively, you can start the Fibre Channel Transport Management utility by
using the /usr/openv/netbackup/bin/nbftadm command.
Displaying reports
Use the Reports menu to view problem or status reports from one or more
NetBackup servers or clients. To use the Reports menu, press r (Reports) on
the bpadm main menu.
Server: ALL
Client: ALL
Start Date: 05/14/2007 13:58:27
End Date: 05/15/2007 23:59:59
Reports
-------
b) Backup Status
l) List Client Backups
p) Problems

a) All Log Entries
m) Media ...
d) Change Dates
c) Change Client
s) Change Server
h) Help
q) Quit Menu
ENTER CHOICE:
Performing manual backups

Use the Manual Backups menu to perform a manual backup of the files that
are associated with any policy, client, or schedule. Press m (Manual Backups)
on the bpadm main menu:
Policy: W2
Client: <ALL>
Schedule: w2_daily_incr (Incremental)
Manual Backups
--------------
i) Initiate Backup
b) Browse Policies Forward
r) Browse Policies Reverse
s) Browse Schedules
c) Browse Client Workstations
e) Enter Policy/Client/Schedule...
h) Help
q) Quit Menu
ENTER CHOICE:
To perform manual backups

Choose the method in step 1 or 2 to select the policy, client, and schedule for a
manual backup; then complete step 3.
1 Press e (Enter Policy/Client/Schedule) and specify your policy,
client, and schedule.
2 Press b (Browse Policies Forward) until the Policy line at the top of
the screen shows the name you want.
a To select either a single client or all clients, press c (Browse Client
Workstations). Stop when the name of a specific client (or ALL for all
clients) appears on the Client line at the top of the screen.
b To select the schedule or schedules, press s (Browse Schedules).

Stop when the name of a specific schedule appears on the Schedule
line at the top of the screen.
3 To start the backup, press i (Initiate Backup).
Performing special actions

Use the Manual Backups menu to perform a manual backup of the files that
are associated with any policy, client, or schedule. Press m (Manual Backups)
on the bpadm main menu:
Use the Special Actions menu to perform a variety of tasks that do not fall
under other categories. Press x (Special Actions) on the bpadm main menu:
Special Actions
---------------
c) Install All Clients...
b) Offline Catalog Backup...
r) View and Change Retention Levels
i) Initiate Request Daemon
t) Terminate Request Daemon
h) Help
q) Quit Menu
Install NetBackup on all trusting clients

To install software on trusting clients, press c (Install All Clients). A
trusting client is one that has an /.rhosts file with an entry for the NetBackup
server.
Perform an offline catalog backup

To perform an immediate offline catalog backup, press b (Offline Catalog
Backup). Also, use this menu choice to modify or delete an existing offline
catalog backup:
Backup When: never - must be manually initiated
Offline Catalog Backup
----------------------
m) Modify Offline Catalog Backup Settings...
d) Delete Offline Catalog Backup Media ID...
b) Perform Offline Catalog Backup Now...
a) Add Offline Catalog Backup File Path...

r) Remove Offline Catalog Backup File Path...
l) List/Display Offline Catalog Backup Settings

h) Help
q) Quit Menu
Note: An offline, cold catalog backup, exists by default and does not need to be
created. However, in order for the offline catalog backup to run, it must be
configured to run (the default is Never). Use option m from the Offline
Catalog Backup menu.
An online, hot catalog backup is created using the Policy Management menu.
For a description of the process, see “Configuring an online catalog backup” on
page 120.
Two information lines appear:

■ Backup When: Displays the current setting for how often the catalog is to
be backed up offline:
■ never - must be manually initiated
■ after each backup schedule
■ after any successful backup/archive
“Modifying offline catalog backup settings” on page 127 explains these
settings.
■ Output Destination: Determines where bpadm sends the output of a
List/Display Offline Catalog Backup Settings selection. If the
word SCREEN appears on this line, the output appears on the terminal
screen. If a file path appears (for example, /tmp/bp_db_backup), the
output goes to the file. Change the output setting by using the o option.
Modifying offline catalog backup settings

To modify an offline catalog backup, press m while viewing the Offline
Catalog Backup menu and follow the prompts.
Caution: If media ID information is modified for a media ID that was previously

used for backups, the Written date and time for the media ID is overwritten in
the NetBackup database. The contents of the media itself is not destroyed unless
it is used again.
For example, assume you change to a different media ID to make an extra copy
of the catalog files. When you change to the new media ID, NetBackup replaces
the old ID with the new ID. It no longer tracks the old ID in its database. This
results in the media being associated with old ID being made available for
reassignment by Media Manager.
To modify offline catalog backup settings

1 From the Offline Catalog Backup menu, select m to specify when the
offline catalog backup should occur:
■ 1) never - must be manually initiated:
With this option selected, NetBackup never automatically backs up the
catalog files. You must initiate the backup using the Perform
Offline Catalog Backup Now option.
■ 2) after each successful backup schedule:
NetBackup performs an offline catalog backup after any scheduled
backup session that results in the creation of at least one successful
backup image. A catalog backup does not occur after a manual or
user-directed backup or archive. Option 2 is the recommended method.
■ 3) after any successful backup/archive:
NetBackup performs an offline catalog backup after any backup session
that results in the creation of at least one backup or archive image.
Backup sessions include scheduled, manual, and user-directed, backups
and archives.
The following example configures a NetBackup offline catalog backup after
any successful backup or archive image.
Enter Selection [1-3]: (1) 2 <Return>
Enter Server name: (server1.xxx.yyy.com) <Return>
Modify ID 1? (y/n): y
Storage Unit Type Selections:
1) Disk
2) Media Manager
Enter Type [1-2]: (1) <Return>
Enter ID (path): (path_other_than_local_drive) <Return>

Modify ID 2? (y/n): y
Storage Unit Type Selections:
1) Disk
2) Media Manager
Enter Type [1-2]: 2 <Return>
Density Selections
1) 4mm - 4mm Cartridge
2) 8mm - 8mm Cartridge
3) 8mm2 - 8mm Cartridge 2
4) 8mm3 - 8mm Cartridge 3
5) dlt - DLT Cartridge
6) dlt2 - DLT Cartridge 2
7) dlt3 - DLT Cartridge 3
8) dtf - DTF Cartridge
9) hcart - 1/2 Inch Cartridge
10) hcart2 - 1/2 Inch Cartridge 2
11) hcart3 - 1/2 Inch Cartridge 3
12) odiskwm - Optical Disk Write-Many
13) odiskwo - Optical Disk Write-Once
14) qscsi - 1/4 Inch Cartridge
Enter Selection [1-14]: 5 <Return>
Enter ID (media ID): RR1005 <Return>
Make change now? (y/n): y
2 Specify the server to which the catalog backups are to be sent.

The default is the current value shown in parentheses after the Enter
Server Name prompt. During initial configuration, the default is always
the master server.
To change the destination to a media server, ensure that the server has been
previously configured. (That is, the server is listed in the bp.conf file on
the master server where bprd and bpdbm was started.)
Also, to back up to a media server, modify the backup paths for the master
server as explained in step 7.
3 Specify whether to modify the first of the two available media IDs (ID 1).
■ Press n to leave the media ID unchanged, then go to step 5.
■ Press y to change the ID, then go to step 4.
Caution: An offline catalog backup does not span tape volumes. All the backup
data must fit on one tape. Therefore, it is extremely important for the
administrator to select a media type that can contain all the data to be backed
up. The size requirement is dependent on the size of the databases. NetBackup
sends a notification if the backup fails.
4 Select the storage unit type (the number in parentheses shows the current
type).
■ Press 1 for Disk type and specify the path where the offline catalog
backup is to be written. This should be to a subdirectory. NetBackup
creates the path if it does not exist and produces an error if the path
exists and is a file rather than a directory.
Note: If the path already exists, the error NetBackup reports occurs when the
backup is performed, not when the path is specified.
■ Press 2 for a Removable or Robotic type storage unit and select the
density.
Specify the media ID (volume serial number) of the media to use.
5 Specify whether to modify the second media ID (ID 2). If y, you are
prompted as shown for media ID 1 in step 3.
6 Specify whether to make the changes. Either choice returns you to the
Offline Catalog Backup menu.
7 To back up the offline catalog to a media server (see step 2), modify the
offline catalog backup paths for the master server:
a Remove each backup path for the master server by using the Remove
Offline Catalog Backup File Path option on the Offline
b To add each backup path for the master server again, press a (Add
Offline Catalog Backup File Path) while viewing the Offline
When the paths are added, specify the paths in the following format:
master_name:database_backup_path
For example, if the platform is named bunny, the paths are as follows:
bunny:/usr/openv/netbackup/db
bunny:/usr/openv/volmgr/database
Performing manual offline catalog backups

To start an immediate offline catalog backup, press b (Perform Offline
Catalog Backup Now) from the Offline Catalog Backup menu.
The following prompt appears:
WARNING: Backing up the catalog may take a while.
Are you sure you want to continue? (y/n):

Note: If the media ID used for the offline catalog backup is not in a robot, a
mount request for that media ID is sent. If the mount request is not honored, a
manual offline catalog backup must wait for the mount before proceeding. A
schedule-driven catalog backup must also wait for the mount and, because the
schedule is waiting, all other backups and archives must also wait until the
catalog backup is complete.
■ Press y to start the offline catalog backup. NetBackup uses the least recently
used of the two media IDs you have assigned for backups. You must wait for
completion of the backup to regain control of the terminal session.
■ Press n to abort the operation.
Redefining retention levels

To change the retention period that is associated with any retention level, press
x (Special Actions) from the main menu. Press r (View and Display
Retention Levels) and follow the prompts:
Level Period level Period
----- ----------- ----- -----------

* 0 1 week * 1 2 weeks
* 2 3 weeks * 3 1 month
4 2 months 5 3 months
6 6 months 7 9 months
* 8 1 year * 9 infinity
10 infinity 11 infinity
24 infinity
Enter 'r' to restore defaults.
'*' indicates the retention is used in a current schedule.
Select the retention level you wish to change. (0-8, 10-24, r,
q=quit, s=save)>
Note: An asterisk in front of a retention level indicates that the retention level is
referenced in a currently defined schedule. To change the retention level may
have adverse effects on the schedules that use it.
Using the vmadm media management utility
Defining and managing server groups

Use the Server Group Management menu to define and manage server
groups. To display the Server Group Management menu, press o (Server
Group Management) on the bpadm main menu:
Server Group Label: <none>
Server Group Management
-----------------------------
a) Add Server Group...
m) Modify Server Group...
d) Delete Server Group
b) Browse Server Groups Forward
r) Browse Server Groups Reverse
e) Enter Server Group
l) List/Display Server Groups

h) Help
q) Quit Menu
ENTER CHOICE:

UNIX systems only.
This section explains how to use the NetBackup vmadm media management
utility to add, delete, or change media in a NetBackup volume configuration.
These utilities are alternatives to using the NetBackup Administration Console.
The terminology, general concepts, and results are the same regardless of which
method you use.
Starting vmadm
You must be the root user to run vmadm.
To start vmadm
◆ Enter /usr/openv/volmgr/bin/vmadm.
Starting and stopping vmd

You can control the Media Manager volume daemon, vmd in the following ways:
To start vmd from the UNIX prompt

◆ Enter /usr/openv/volmgr/bin/vmd.
To start vmd from vmadm

1 On the main menu, choose s for Special Actions.
2 Choose i for Initiate Media Manager Volume Daemon, which starts vmd and
returns you to the Special Actions menu.
To stop vmd from vmadm
1 On the main menu, choose s for Special Actions.
2 Choose t for Terminate Media Manager Volume Daemon. This stops vmd
and returns you to the Special Actions menu.
The vmadm main menu

The main menu is similar to the following:
Database Host: shark
Media Management
-----------------
a) Add Volumes
d) Delete Volumes
m) Move Volumes
p) Print Information about Volumes
c) Configure Volume Pools
s) Special Actions
u) Device Configuration Utility
k) Disk Configuration Utility
h) Help
q) Quit
ENTER CHOICE:
Specify an option by pressing the key that corresponds to the menu option. Each
option displays other menus from which you make choices.
The Database Host is the host on which the EMM database resides and the Media
Manager volume daemon (vmd) is running.
Defining and managing volume pools

To open the Configure Volume Pools menu, press c at the Media Management
menu. The Configure Volume Pools menu appears as follows:
Display Mode: BRIEF
Configure Volume Pools
---------------------
a) Add Pool
c) Change Pool
d) Delete Pool
l) List Pools
s) List Scratch Pools
p) List Catalog Pools
m) Mode (brief or full)
o) Output Destination (screen or file)
h) Help
q) Quit Menu
ENTER CHOICE:
To add, change, or delete volume pools, press the letter key that corresponds to
the menu option and then follow the prompts.
For more information about volume pools, see “Volume pool operations” in the
“Media” chapter of the NetBackup Administrator’s Guide for UNIX and Linux,
Volume I.
Adding volumes
To add volumes, press a at the Media Management menu and then follow the
prompts. You can add:
■ stand-alone volumes (when prompted for the location, specify Not in
robotic device)
■ Volumes to a robot (when prompted for the location, specify the robot in
which the volumes reside)
You can add a single volume, a range of volumes, or let vmadm read the barcodes
on the media and add them automatically (auto-populate).
For more information about volumes, see “Volume operations” in the “Media”
chapter of the NetBackup Administrator’s Guide for UNIX and Linux, Volume I.
Auto-populating a robot
You can use auto-populate for the robots that support barcodes and for the
robots that do not support barcodes, with some operational limitations. For
limitations, see “Robot attributes” in the NetBackup Device Configuration Guide.
The easiest way to add new media to NetBackup is to:
■ Inject the media into the robot.
■ Use auto-populate to update the EMM database to agree with the contents of
the robot. The database update includes automatic creation of media IDs.
If the robot supports barcodes and the volumes have readable barcode labels,
auto-populate generates media IDs for new volumes from one of the following:
■ The last six characters of the barcodes.
■ Media ID generation rules.
When you use barcode rules, the new media that are added through a barcode
rule are assigned: a media type, a pool name, a maximum number of mounts (or
cleaning), and a description.
If the robot does not support barcodes or the media does not have readable
barcodes, the new media IDs are based on a media ID prefix that you specify.
Auto-populate prerequisites
The following are prerequisites for auto-populating a robot:
■ Check the barcode capabilities of the robot and its media by following the
procedures in “Inventory robots” on page 140. Check whether the following
are true:
■ The robot supports barcodes.
■ The new media have readable barcodes.
If the robotic library does not support barcodes or the media do not have
readable barcodes, save the results of the verify. You can use those results if
you assign a media ID prefix.
You can use the physical inventory utility for nonbarcoded media. For
procedures, see “Using the physical inventory utility” in the “Media”
chapter of the NetBackup Administrator’s Guide for UNIX and Linux,
Volume I.
■ Create barcode rules (optional).

For procedures, see “Configuring barcode rules” on page 143. Create any
additional barcode rules that you want to use to auto-populate the database.
■ For the robot types that are not API robots, create media ID generation rules
(optional).
■ For API robots, create media type mappings for the robot as explained in
“Changing update options” on page 141
You can change the default media type mappings as explained in “Managing
Media” in the NetBackup Administrator’s Guide for UNIX and Linux, Volume
I.
■ Ensure that the appropriate control daemons are active on the robot control
host.
Displaying the volume configuration

You can display the volume configuration on the screen or send the output to a
file.
Press p at the Media Management menu to display the Display Options menu.
To show all volumes in the configuration, press s at the Display Options menu.
You can toggle between brief or full display. You can send the output to the
screen (the default) or write it to a file. You can filter the output by the following
criteria:
■ All
■ Media ID
■ Media type
■ Volume group
■ Robot number
■ Robot type
■ Volume pool
■ Vault container ID
Deleting volumes or groups

Press d at the Media Management menu and then following the prompts.
You can delete a single volume, multiple volumes, or a volume group.
If you delete multiple volumes, you enter the media IDs one at a time. When you
have deleted all of the volumes, press Enter without entering a media ID.
Moving volumes or a volume group

Moving volumes in vmadm changes only their logical residence in the EMM
database. They also must be moved physically, unless they are injected or
ejected using the media access port.
You can move:

■ A single volume. If the robot has a media access port, you can inject or eject
the volume.
■ Multiple volumes. To move multiple volumes is similar to a single volume.
However, after you choose where you want the volumes to be moved, you are
prompted to continue entering media IDs of volumes to move. When you
have moved all of the volumes, press Enter without entering a media ID. You
also do not have the option to eject and inject volumes using the media
access port.
■ A volume group.
If the robot supports barcodes and the media have readable barcodes, the easiest
method to move volumes is to inventory the robot and update the volume
configuration.
If the robot does not support barcodes or the barcodes are unreadable, use one of
the following:
■ The move procedures in the following subsection.
■ The physical inventory utility (see “Using the physical inventory utility” in
the “Media” chapter of the NetBackup Administrator’s Guide for UNIX and
Linux, Volume I).
For an overview of how to move volumes, see “Moving volumes” in the
NetBackup Administrator’s Guide for UNIX and Linux, Volume I.
Moving volumes or volume groups

Press m at the Media Management menu and then following the prompts.
Changing a volume description

Press s at the Media Management menu, press d at the Special Actions menu,
and then follow the prompts.
Changing a volume's volume pool

Press s at the Media Management menu, press p at the Special Actions menu,
At the Volume Pool menu, select the new volume pool for the volume, and then
enter the media ID of the volume to change.
To quit changing volumes, press Enter at the Enter Media ID prompt without
entering a media ID. To change another volume, enter another media ID.

Changing the expiration date for volumes

You can change the expiration date for any volume in the EMM database. The
expiration date is the age of the media, not the age of the data on the media. It is
when the media is considered too old to be reliable.
When the expiration date of a volume has passed, NetBackup can still read it.
However, NetBackup does not mount an expired volume for a write access.
NetBackup writes a warning message to the system console log for a read access
request for an expired volume. NetBackup generates an error message for a
write request to an expired volume.
Press s at the Media Management menu, press e at the Special Actions menu,
Enter 0 for no expiration date or enter a date in one of the following formats:
■ mm/dd/yy hh/mm/ss
■ mm/dd/yyyy hh/mm/ss
■ mm/dd/yy
■ mm/dd/yyyy
■ mm/dd
To quit changing volumes, press Enter at the Enter Media ID prompt without
entering a media ID. To change another volume, enter another media ID.
Changing the volume group for volumes

Press s at the Media Management menu, press g at the Special Actions menu,
You can change one or more volumes. To quit changing volumes, press Enter at
the Enter Media ID prompt without entering a media ID. To change another
volume, enter another media ID.
At the Volume Group menu, select the new group for the volumes or generate a
new volume group for the volumes.
Change Vault attributes of volumes

Several volume attributes are used for the NetBackup Vault option. You can
change those Vault attributes.
Press s at the Media Management menu and then press a at the Special Actions
menu to display the Vault Volume Parameters menu:
Vault Volume Parameters
-----------------------
n) Change Vault Name for Volumes

d) Change Date Volumes are sent to Vault
r) Change Date Volumes return from Vault
s) Change Vault Slot for Volumes
i) Change Vault Session ID for Volumes
h) Help
q) Quit Menu
ENTER CHOICE:
Press the letter key that corresponds to the attributed you want to change.
Setting the maximum mounts for volumes

You can set or change the maximum number of times a volume NetBackup
mounts a volume. When this number is reached, any further requests to mount
the volume for a write operation result in an error. If you specify 0, NetBackup
can mount the volume an unlimited number of times.
To help determine the maximum mount count to use, consult your vendor
documentation for information on the expected life of the media.
Note: You cannot set the maximum number of mounts for a cleaning cartridge.
Press s at the Media Management menu, press s at the Special Actions menu,
Modifying the number of cleanings

You can set or change the number of cleanings that are allowed for a cleaning
tape. This number is decremented with each cleaning and when it is zero,
NetBackup stops using the tape. You then must change the cleaning tape or
increase the number of cleanings that remain.
Press s at the Media Management menu, press m at the Special Actions menu,
Updating barcodes for selected volumes in a robot

For the robots that support barcodes and have readable barcoded media, you can
check the barcodes of volumes and update the EMM database if necessary.
Use this menu option only to add the barcodes that are not in the database. For
example, if you add a new volume to NetBackup but do not inject it into the
robot, NetBackup does not update the EMM database. In this case, you can use
the Update/Validate Barcode option to fill in the missing barcode.
Note: You cannot use the Update/Validate Barcodes option for API robots
because NetBackup does not manage media location information for API robots.
Press s at the Media Management menu, press u at the Special Actions menu,
You can update one or more volumes. To quit updating volumes, press Enter at
the Enter Media ID prompt without entering a media ID. To update another
Inventory robots
For the robots that support barcodes and have media with readable barcodes,
you can inventory the media in the robot. You also can use one of the inventory
options to add new media to the NetBackup configuration.
Inventory a robot
Select the inventory type from the Special Actions menu and follow the
prompts. The procedure is similar for each type of inventory.
Special considerations
■ ACS and TLM robots: at the Robot Control Host prompt, enter the host on
which the NetBackup robotic daemon runs (acsd or tlmd).
■ For an inventory and compare operation:
■ For API robots, NetBackup determines whether the media ID and media
type that is stored in the EMM database matches the robot’s database.
■ For non-API robots with barcode readers, NetBackup determines
whether the barcodes in the robot match those in the EMM database.
When the report shows <none>, it means that the media does not have
a barcode.
■ For the robots that cannot read barcodes, vmadm verifies only whether
the EMM database correctly shows whether a slot contains media.
Changing update modes

For an inventory operation and update operation, the update modes are:
■ INTERACTIVE, which displays a list of recommended changes and prompts
you to confirm whether to continue with the update.
■ NOT INTERACTIVE, which makes the recommended changes without
prompting for a confirmation.
The m option of the Inventory and Update menu toggles the update mode.
Changing update options

The o option of the Inventory and Update menu displays the Update Options
menu:
Update Robot: TL8 (10) - whale
OPTION FOR REMOVED MEDIA
-----------------------
Volume Group: DEFAULT
OPTIONS FOR ADDED OR MOVED MEDIA
-------------------------------
Volume Group: DEFAULT
Use Barcode Rules: YES
Media Type: DEFAULT
Media ID Prefix: DEFAULT
Volume Pool: DEFAULT
Update Options
-------------
b) Use Barcode Rules r) Volume Group for REMOVED media
m) Media Type a) Volume Group for ADDED or MOVED media
i) Media ID Prefix p) Volume Pool
h) Help
q) Quit Menu
ENTER CHOICE:
To change an update option, select the letter key that corresponds to the option.
For most configurations, the default update options work well. You should only
change the defaults if your configuration has special hardware or usage
requirements.
Be aware of the following:
■ Use barcode rules. If yes, NetBackup attempts to use barcode rules only for
the volumes that are not already in the EMM database.
■ Media type if you do not use barcode rules. For API robots vmadm uses the
Media Type Mappings that are displayed. For non-API robots that are
configured on this robot host, vmadm uses the media type for the robot as
follows:
■ If all of the drives are the same type and at least one drive is configured
on the robot control host, vmadm uses the media type for the drives.
■ If all of the drives are not the same type, vmadm uses the default media
type for the robotic library.
You must select a media type from the menu if:
■ The robotic library supports multiple media types and you do not want
the default media type.
■ The drives are not configured on the robot control host and the drives
are not the default media type for the robot.
■ Media type if you use barcode rules, choose DEFAULT to let the barcode rule
determine the media type that is assigned. To use a media type other than
the default, choose a specific type from the menu. The update media type
setting always overrides barcode rules.
■ Media ID prefix. Specify a media ID prefix if the robot does not support
barcodes and the media that was inserted does not have readable barcodes.
If neither of the previous conditions are true, a prefix is not required.
NetBackup uses one of the following for a Media ID:
■ The last six characters of the barcode.
■ The characters that you specify if you use Media ID generation rules,
whether or not a barcode rule is used.
If you select default media ID prefix, vmadm uses the last
MEDIA_ID_PREFIX entry in the vm.conf file. If no MEDIA_ID_PREFIX
entries exist, vmadm uses the letter A as the default prefix.
If you select use no media ID prefix, the operation succeeds only if the robot
supports barcodes and the media have readable barcodes. This choice may
be useful if you use media with barcodes and want updates to fail when
unreadable or missing barcodes are encountered.
■ Volume Group for removed media. If Media Type is DEFAULT, you can
choose from the existing volume groups that are valid for the robot’s default
Media Type. If Media Type is other than DEFAULT, you can choose from the
existing volume groups that are valid for the media type.
■ Volume group for added or moved media. If Media Type is DEFAULT, you can
choose from the existing volume groups that are valid for the robot’s default
Media Type. If Media Type is other than DEFAULT, you can choose from the
existing volume groups that are valid for the media type.
■ Use platter side in media ID. For ODL robots, choose yes to include an A/B
designation in the media IDs for the two sides of an optical disk platter. One
side has a media ID of xxxxxA and the other side xxxxxB, where xxxxx is the
media ID prefix and and number. If no, a platter side designation is not
used. The two sides of an optical disk platter are referred to as media ID
partners.
Use platter side in media ID appears only if you inventory and update on an
ODL robot and you use a media ID prefix.
■ Volume pool. If you use barcode rules, by default the volume pool setting of
the barcode rule determines the volume pool that NetBackup assigns. The
Update Options volume pool always overrides a barcode rule. If you do not
using barcode rules, by default NetBackup uses: the NetBackup volume pool
for data volumes and the None volume pool for cleaning tapes.
Configuring barcode rules

To configure barcode rules, choose b) Configure Barcode Rules from the Special
Actions menu. The following menu appears:
Display Mode: BRIEF
Configure Barcode Rules
----------------------
a) Add Rule
c) Change Rule
d) Delete Rule
l) List Rules
m) Mode (brief or full)
o) Output Destination (screen or file)
h) Help
q) Quit Menu
ENTER CHOICE:
For more information about barcode rules, see “Barcode Rules tab” in the
“Media” chapter of the NetBackup Administrator’s Guide, Volume I.
Formatting optical disks

Before NetBackup can use an optical disk platter, you must write a media ID and
a volume label on the platter. The media ID should match the external media ID.
Two methods exist to write this information:
■ Use vmadm to format the platter when you add it. The final step in the
procedure is to format the volume, and vmadm invokes tpformat to do the
formatting.
■ Use the tpformat command.
Using the tpconfig device configuration utility
When you use vmadm, the media ID becomes the recorded media ID. The
following steps use vmadm. See tpformat in NetBackup Commands for UNIX
and Linux for a description of how to use tpformat.
Note: All operating systems do not support 1024 byte-per-sector platters. Most
support only 512 byte-per-sector sizes. Before you purchase optical disk
platters, check your operating system documentation to determine which sector
sizes it supports. Also see the Symantec support web site for information on
what is supported. Symantec recommends that you use preformatted platters.

UNIX systems only.
This section explains how to configure robots and drives using the NetBackup
device management configuration utility, tpconfig. After you configure
devices, you can use the Media Management utility (vmadm) to configure
volumes.
The following subsections describe the attributes of device configuration and
how to use the tpconfig utility to configure those attributes.
Robot number
You assign a robot number when you add a robot to the configuration.
tpconfig prompts you to enter a number or accept the next available robot
number that it displays. This number identifies the robot in displays and
listings, and it follows the robotic type in parentheses, such as TL8(2).
The following point applies only to NetBackup Enterprise Server.
If you configure robots on multiple systems, robot numbers must be unique. If
you connect drives from a robot to multiple systems, you must specify the same
robot number for the robot on all systems.
Robotic control path

For most robots, you or the operating system creates this path in the /dev
directory when you add a robot to the configuration. When tpconfig prompts
you, enter the path to the robotic control as found in the /dev directory. If the
entries do not exist, see the NetBackup Device Configuration Guide .
For API robots, see the appendices in the NetBackup Device Configuration Guide
for information on how to configure robotic control. The control path to a robot
may be on another host. If so, enter the host name of the host instead of a path.
When you define a robot that another host controlls by another host, the robot
number must be the same on both hosts.
Host name
This topic is a NetBackup Enterprise Server topic.
You must specify a host name in the following cases. When you add:
■ An ACS robot, enter the name of the host on which the ACS Library Software
resides instead of a robotic control path.
■ A TLM robot, enter the DAS or Scalar DLC server name instead of a robotic
control path.
■ An TL8, TLD, or TLH robot that has robotic control on another host, you are
prompted for the host name of that host.
No rewind on close device name

You specify a no rewind on close device name when you add a drive. Usually the
device name is preceded or followed by the letter n. If the device name entries do
not exist, you must create them as explained in the NetBackup Device
Configuration Guide.
In tpconfig displays and output, these device names are shown under the
heading DrivePath.
Character device name

Character device name applies only to optical disk devices. A drive that is used
as a character device uses a complete 512-byte block each time it writes data.
(Note that some systems may use 1024-byte blocks.) If less than 512 bytes are
used, the remaining bytes are padded out. A character device is also referred to
as a raw device. NetBackup and Storage Migrator use character mode.
You specify a device name when you add an optical disk to the configuration. For
the device path, enter the path name to the device as found in the /dev
directory. If the entries do not exist, you must create them as explained in the
NetBackup Device Configuration Guide
In tpconfig displays and output, the character device name appears under the
heading DrivePath.
Volume header device name
Note: Volume headers do not apply to all systems.

The volume header device name is used internally but must be specified when
you add an optical drive to a configuration. For the device path, enter the path
name to the device as found in the /dev directory. To display the volume header
device name, choose the Update or Delete option from the Drive Configuration
menu.
On Solaris SPARC systems, the MAKEDEV command may have to be run first to
create these entries. For more information, see the NetBackup Device
Configuration Guide and the MAKEDEV(8) command.
Drive status
Drive status indicates whether NetBackup considers a drive available. You
specify the initial drive status when you add a drive to the configuration. You
can change the status. To do so, use the Update option of the Drive
Configuration menu in tpconfig (ensure that ltid is not active). If ltid is
active, use the Administration Console Device Monitor or the vmoprcmd
command.
Starting the tpconfig device configuration utility

You can start the device configuration utility by pressing u (Device
Configuration Utility) from the vmadm Media Management menu. Alternatively,
you can use the following command in a UNIX shell (you must have root user
privileges):
/usr/openv/volmgr/bin/tpconfig
The following menu appears:

Device Management Configuration Utility
1) Drive Configuration
2) Robot Configuration
3) Credentials Configuration
4) Print Configuration
5) Help
6) Quit
Enter option:
Note: If the Media Manager device daemon is running, you should stop it with
the stopltid command.
The following table describes the main menu choices:
Option Menu choice Description
1 Drive Opens a menu to add, delete, or update drive definitions;

Configuration list definitions of drives and robots; or configure drive
paths.
2 Robot Opens a menu add, delete, or update robot definitions or

Configuration list definitions of drives and robots
3 C
redentials Opens a menu to add, delete, update, or list credentials
Configuration for:
■ NDMP filer
■ Disk array
■ OpenStorage server
■ Virtual machine
4 Print The List Configuration commands on subsequent menus

Configuration allow you to display the current configuration on the
screen or write it to a file.
If you specify the -d option only on the tpconfig
command, tpconfig writes the current configuration to
stdout (the screen) without invoking the menus.
Other command options are available. Run tpconfig -help
or see tpconfig in the NetBackup Commands for UNIX
and Linux.
5 Help Online help is available on the main menu and most

submenus.
6 Quit Terminates the utility and returns you to the UNIX

prompt.
You can return to the main menu from anywhere in the utility by entering Ctrl C
or using the Escape key.
Adding robots
When you configure robots and drives, first add the robots using the Robot
Configuration menu and then add the drives using the Drive Configuration
menu.
To change stand-alone drives to robotic, use the Update option of the Drive
Configuration menu. See “Updating a drive configuration” on page 150.
To add a robot
1 Select the Robot Configuration menu.
2 Select the Add option.
3 From the list of possible robot types, select the one you want to add.
4 Enter a robot number you know is unused or accept the default robot
number.
5 Indicate where the robotic control for the library is by entering the device
file path or library name. The Help option on the Robot Configuration menu
has examples of typical path names.
6 This step applies only to NetBackup Enterprise Server.
a If robotic control is on another host, enter that host name.
For an ACS robot, you must enter the name of the ACS library software
host.
For a TLM robot, you must enter the name of the DAS or Scalar DLC
server.
b If robotic control is on this host, enter the device file path or library
name. The Help option on the Robot Configuration menu has examples
of typical path names.
For an ACS robot, enter the name of the ACS library software host.
For a TLH robot on an AIX system, enter the LMCP Device File;
otherwise, enter the Automated Tape Library Name.
For a TLM robot, enter the name of the DAS or Scalar DLC server.
7 If no conflicts are detected with the new configuration, you see a message
that the robot was added.
Adding drives
Use the following procedure to add a drive.
To add a drive
1 Select the Drive Configuration menu.
2 Select the Add option.
3 From the list of possible drive types that are displayed, select the one you
want to add.
4 Enter the no rewind on close device path as shown in the /dev directory.
If the device is an optical disk, enter the character device and volume
header device file paths. File paths are in the /dev directory (volume
headers do not appy to all systems).
The Help option on the Drive Configuration menu has examples of typical
path names.
5 Enter the drive status (Up or Down).
6 If a robot exists to which the you can add the drive, specify whether to add
the drive to the robot. Alternatively, you can configure the drives as a
stand-alone drive.
If there are no robots to which you can add the drive, tpconfig
automatically adds the drive as a stand-alone drive.
If you add a drive to a robot and more than one possible robot exists, enter
the number of the robot that controls the drive.
Depending on the type of robot, you may also be prompted to add the robot
drive number.
7 This step applies only to NetBackup Enterprise Server.
For a drive in an ACS robot, you are prompted for four drive identifiers. For
more information on ACS robots, see the NetBackup Device Configuration
Guide.
For a drive in a TLH robot, you are prompted for an IBM device number. For
more information, see the appendix NetBackup Device Configuration Guide.
For a drive in a TLM robot, you are prompted for a DAS or Scalar DLC drive
name. For more information see the NetBackup Device Configuration Guide.
8 Type a drive name or press Enter key to use the default drive name.
If you use the shared drives option, all hosts that share the same physical
drive must use the same name for the drive. Descriptive drive names are
recommended.
Updating a robot configuration

Use the following procedure to change the robot number or the robotic control
path.
To change the robot number or the robotic control path

1 On the main menu, choose Robot Configuration.
Note: If only one robot is configured, step 2 and step 3 are skipped.
2 On the Robot Configuration menu, choose Update.

The following prompt is displayed
Enter robot number to update:
3 Enter the number of the robotic library you want to change.

The following prompt is displayed:

Enter new robot number or <RETURN> to use existing (n):
4 Enter a new robot number to replace the existing robot number or press
Enter to retain the current robot number.
You are prompted to enter robotic control information. The actual prompts
depend on the type of robotic library you update.
5 Enter the appropriate robotic control path or name of the server that hosts
the robot.
Updating a drive configuration

You can change information for a drive (for example, you can add it to a robot).
To change information for a drive
1 On the main menu, choose Drive Configuration.
2 On the Drive Configuration menu, choose Update.
3 Enter the name of the drive you want to update.

The current drive information is displayed, followed by prompts to change
each field.
4 Enter a new value or press Enter to retain the existing value.
One of the prompts asks if you want to configure the drive in a robot. If you
do, tpconfig adds the drive immediately or gives you the opportunity to
choose from any existing robot of the appropriate type.
When you have responded to all prompts, a revised Drive Information
display appears, along with the following prompt:
Are you sure you want to UPDATE drive name xxxxx? (y/n) n:
5 Answer yes by pressing y.
Deleting a drive
Use the following procedure to delete a drive.
To delete a drive
1 On the main menu, choose Drive Configuration.
2 In the Drive Configuration menu, choose Delete.
3 Enter the name of the drive you want to delete:

Drive information and a prompt similar to the following are displayed:
Are you sure you want to DELETE drive name xxxxx? (y/n) n:
4 Enter y to delete the drive.

If you respond with y, a message confirms that the drive was deleted.
If you respond with n, press any key to return to the Drive Configuration
menu.
Deleting a robot
Use the following procedure to delete a robot.
To delete a robot
1 On the main menu, choose Robot Configuration.
Note: If only one robot is configured, step 2 and step 3 are skipped.
2 On the Robot Configuration menu, choose Delete.

3 If more than one robot is configured, enter the number of the robot to
delete.
A prompt similar to the following is displayed:
Deleting robotic definition:
TLD(0) robotic path = /dev/sg/c1t0d0s0,
Any drives defined on this robot will be changed to standalone
drives
Do you want to proceed? (y/n) n:
4 Enter y to delete the robot.

If you respond with y, a message confirms that the robot was deleted.
If you respond with n, press any key to return to the Drive Configuration
menu.
Configuring drive paths

Use the following procedures to configure and manage drive paths.
To display the drive path menu

1 From the Drive Configuration menu, select Drive Path Configuration.
The following prompt is displayed:
Enter name of drive to configure path(s) for:
2 Enter a drive name.

The Drive Path Configuration menu is displayed.
To add a drive path

1 Select Add from the Drive Path Configuration menu.
A prompt similar to the following appears:
Enter the new drive path:
2 Enter a valid drive path.

A prompt similar to the following appears:
Enter drive status on this path - (u)p, (d)own or dis(a)bled:
3 Specify the drive status on the path.

The drive can be Up, Down, or Disabled for the path.
To delete a drive path
1 Select Delete from the Drive Path Configuration menu.
2 Enter the drive path to delete.
To update a drive path

1 Select Update from the Drive Path Configuration menu.
A prompt similar to the following is displayed:
Enter the current drive path:
2 Enter the drive path to update.

3 Specify a new drive path or press Enter to update the status of the drive
path.
4 A prompt similar to the following is displayed:
Enter drive status on this path - (u)p, (d)own or dis(a)bled:
5 Enter the path status.
Configuring host credentials

You can add, delete, update, or configure default host credentials:
■ NDMP filer. You also can add a default set of credentials to be used for all
NDMP Filers by all NetBackup servers.
■ Disk array.
■ OpenStorage server.
■ Virtual machine.
To configure host credentials
1 On the main menu, choose Credentials Configuration.
2 On the credentials menu, select the type of credential you want to configure.
The following is an example of the menu:

Please select the type of host you are trying to configure:
1) (N)dmp Filer

Using the disk configuration utility
2) (D)isk Array Management Server
3) (O)penStorage Server
4) (V)irtual Machine
Enter option or <ESC> to quit:
3 Select an option at the specific credentials menu and follow the prompts.
Displaying and printing your device configuration

You can display the current configuration from every menu in tpconfig. To do
so, use the Print Configuration option on the main menu or the List
Configuration option on the submenus.
You can print the configuration by using the Print Configuration option on the
main menu. Specify a file to write the configuration to or press Enter to display
the configuration on the screen.
In addition, you can specify the -d option on the tpconfig command to write
the current configuration to standard output (stdout) without invoking the
menus.

The NetBackup disk configuration utility is a UNIX utility that lets you
configure and manage disk storage entities. Use this utility for optional
NetBackup products such as SharedDisk.
To configure a basic disk storage unit using a UNIX utility, see “Defining and
managing storage units and storage unit groups” on page 119.
The following is the NetBackup disk configuration utility menu. To display this
menu, press k (Disk Configuration Utility) from the vmadm Media Management
menu (the main menu). To start the vmadm utility, see “Starting vmadm” on
page 132.
NetBackup Disk Configuration Utility
------------------------------------
e) Enclosure Management for SharedDisk
o) OpenStorage Disk Management
m) Change Master Server
h) Help
q) Quit Menu
ENTER CHOICE:

Managing SharedDisk
Use the Enclosure Management for SharedDisk menu to configure and manage
disk storage for the NetBackup SharedDisk option.
To display this menu, press e (Enclosure Management for SharedDisk) from the
NetBackup disk configuration utility main menu.
Enclosure Management for SharedDisk
-----------------------------------
a) Add Storage Server
r) Remove Storage Server
v) View Storage Server
p) Preview Enclosure
i) Import Enclosure
t) Take Disk Pool Inventory
m) Merge Two Disk Pools
c) Change Disk Pool
s) Change Disk Pool State
d) Delete Disk Pool
l) List Disk Pools
h) Help
q) Quit Menu
ENTER CHOICE:
To configure and manage AdvancedDisk, select a menu option and follow the
prompts.
Managing OpenStorage
Use the OpenStorage Disk Management menu to configure and manage disk
storage for the OpenStorage Disk Storage Unit Option.
To display this menu, press o (OpenStorage Disk Management) from the
NetBackup disk configuration utility main menu.
OpenStorage Disk Management
---------------------------
a) Add Storage Server
r) Remove Storage Server
v) View Storage Server
p) Preview Disk Volumes
n) Create New Disk Pool
t) Take Disk Pool Inventory

m) Merge Two Disk Pools
c) Change Disk Pool
s) Change Disk Pool State
d) Delete Disk Pool
l) List Disk Pools
h) Help
q) Quit Menu
ENTER CHOICE:
To configure and manage OpenStorage, select a menu option and follow the
prompts.
Chapter 3
Reference topics
The topics in this chapter provide additional information about various aspects
of NetBackup configuration and management:
■ “Rules for using host names in NetBackup” on page 158
■ “Reading backup images with tar” on page 162
■ “Factors that affect backup time” on page 165
■ “Determining NetBackup transfer rate” on page 167
■ “How NetBackup builds a worklist” on page 169
■ “Determining backup media requirements” on page 171
■ “NetBackup notify scripts” on page 172
■ “Media and device management best practices” on page 187
■ “Using TapeAlert” on page 190
■ “Drive cleaning overview” on page 194
■ “Volume pool and volume group overview” on page 197
■ “Barcode overview” on page 202
■ “Changing your hardware configuration” on page 206
■ “How NetBackup selects drives” on page 210
■ “How NetBackup reserves drives” on page 211
■ “How NetBackup selects media” on page 219
■ “Media formats” on page 223
■ “Media Manager commands” on page 226
■ “Device discovery overview” on page 228
■ “Correlating tape drives to device files or addresses” on page 232
158 Reference topics

Rules for using host names in NetBackup
■ “Tape I/O commands” on page 235

NetBackup uses host names to identify, communicate with, and initiate
processes on NetBackup client and server computers. The correct use of host
names during configuration is essential to the proper operation of NetBackup.
For more information, see “Dynamic host name and IP addressing” on page 99.
Qualifying host names

A major consideration is the extent to which you qualify host names. In many
cases, the short host name of a computer is adequate. If the network
environment contains multiple domains, qualify host names to the extent that
servers and clients can identify each other in a multi-domain environment.
For example, use a name such as mercury.bdev.null.com or mercury.bdev
rather than only mercury.
The following two discussions provide more information by explaining:
■ How NetBackup uses host names

■ How to update NetBackup for client host name changes
How NetBackup uses host names

The following topics discuss how NetBackup stores and uses host names. These
topics also address considerations to choose host names.
Server and client name on UNIX servers and clients

On both UNIX servers and clients, the SERVER entries in the bp.conf file define
the NetBackup servers that are allowed access. The first SERVER entry identifies
the master server. The first SERVER entry indicates the server to which client
requests are made. For this reason, the SERVER name must be one by which all
clients can connect to the server.
If more than one SERVER entry exists, the additional entries identify other
NetBackup servers that can initiate scheduled backups on the client. The
bp.conf file must have multiple SERVER entries if any remote media servers
are configured. The NetBackup Request daemon (bprd) and NetBackup
Database Manager daemon (bpdbm) do not run on any server other than a
master.
When a client makes a list or restore request to the server, the NetBackup client
name is used to determine whether to allow the operation. (The client name as
Reference topics 159
specified on the client.) The client name that is used is usually the
CLIENT_NAME from the bp.conf file of the client. Or, the client name may be
the actual host name of the client if not in the bp.conf file. Alternate client
restores may use the name that is specified through the user interface or with a
parameter on the bprestore command.
For a successful request, the client name must match the name that is specified
for the client in the NetBackup configuration on the server. The only exception
to this rule is if the server is configured to allow alternate client restores.
Host names on Windows servers and PC clients

Windows NetBackup servers and clients also have SERVER and CLIENT_NAME
settings. On these systems, specify server and client settings in the NetBackup
Administration Console.
Policy configuration
The configured name for a client is the host name as it is added to a policy. This
name is how the client is identified in the NetBackup configuration. NetBackup
also adds a CLIENT_NAME entry to a UNIX client’s bp.conf file when software
is first installed on the client.
The server uses the client’s configured name to connect to the client and start
the processes that satisfy client requests. Always use qualified host names to
add clients to a policy so that all NetBackup servers can connect to the clients.
When a client makes a user backup, archive, or restore request to the NetBackup
server, the server uses the peer name of the client. The peer name (identified
from its TCP connection) is used to determine the client’s configured name.
If you add a client to more than one policy, always use the same name in all
cases. If the same name is not used, the client cannot view all the files that are
backed up on its behalf. In this case, file restores become complicated because
both user- and administrator-action is required to restore from some of the
backups.
Image catalog
A subdirectory in the image catalog is created for a client when a backup is first
created for that client. The subdirectory’s name is the client’s configured name.
Every backup for a client has a separate file in this subdirectory. Each of these
backup records contains the host name of the server on which the backup was
written.
Error catalog
NetBackup uses entries in the error catalog for generating reports. These entries
contain the host name of the server that generates the entry and the client’s
configured name, if applicable. The server host name is normally the server’s
short host name. (For example, shark instead of shark.null.com.)
Catalog backup information

If you include a media server’s catalog files in the NetBackup catalog, qualify the
host name of the media server in the file path. Qualified names are necessary
because they allow the master server to connect to the media server.
How to update NetBackup after a host name changes
Note: Do not change the host name of a NetBackup server. A name change might
require that all previously used media be imported to the server before the host
can be used under the new name.
Use the following steps to update the NetBackup configuration if a client’s host
name is changed.
1 On the master server:
■ Delete the client’s old name from all policies where it exists and add the
client’s new name to those policies. You do not need to reinstall
NetBackup software on the client. The client continues to have access
to all previous backups.
■ Create a symbolic link from the client’s old image directory to its new
image directory. For example,
cd /usr/openv/netbackup/db/images ln -s
old_client_name new_client_name
2 On the client:
■ On PC clients, change the client name setting either through the user
interface or in a configuration file. (See the online help in the Backup,
Archive, and Restore client interface.)
■ On UNIX clients, change the CLIENT_NAME value in the bp.conf file
to the new name.
Note: If users on UNIX clients have a bp.conf file in the $HOME directory, users
must change CLIENT_NAME in that file to the new name.
Special considerations for Domain Name Service (DNS)

In some requests to the master server, client software sends the name that it
obtains through its gethostname(2) library function. If the name is unknown
to the master server Domain Name Service, the master server may not be able to
reply to client requests.
This possible situation depends on how the client and the server are configured.
If gethostname(2) on the client returns host the names that DNS on the
master server cannot resolve, problems occur.
One possible solution is to reconfigure the client or the master server DNS hosts
file. Another option is to create a special file in the altnames directory on the
master server. The file forces the translation of NetBackup client host names.
/usr/openv/netbackup/db/altnames/host.xlate
Each line in the host.xlate file contains three elements: a numeric key and
two host names. Each line is left-justified, and a space character separates each
element of the line:
key hostname_from_ client client_as_known_by_server
Where
■ key is a numeric value used by NetBackup to specify the cases where
translation is to be done. Currently this value must always be 0, which
indicates a configured name translation.
■ hostname_from_client is the value to translate. The client name must
correspond to the name that is obtained by running the client’s
gethostname(2). The value must be sent to the server in the request.
■ client_as_known_by_server is the name to substitute for
hostname_from_client for request responses. The name must match the
name in the NetBackup configuration on the master server and must also be
known to the master server’s network services.
Consider the following example:
0 xxxx xxxx.eng.aaa.com
The line specifies that when the master server receives a request for a
configured client name (numeric key 0), the name xxxx.eng.aaa.com always
replaces xxxx. The substitution resolves the problem if the following conditions
are true:
■ When gethostname(2) is run on the client, it returns xxxx.
■ The master server’s network services gethostbyname(2) library function
did not recognize the name xxxx.
■ The client was configured and named in the NetBackup configuration as
xxxx.eng.aaa.com. And, this name is also known to network services on
the master server.
Reading backup images with tar

NetBackup for UNIX uses a modified GNU tar for reading backup images. The
modified tar is located in /usr/openv/netbackup/bin/tar. By using the
modified tar, NetBackup can understand compressed files, sparse files, long
pathnames, ACL information. It offers features similar to those in cpio.
Although non-NetBackup versions of tar can be used to restore files, they
provide only limited restore capabilities.
Note: You cannot use the NetBackup modified-GNU tar on UNIX or tar32.exe
on Windows to extract files from a NetBackup for Windows backup image.
Effects of a non-NetBackup tar

Non-NetBackup versions of tar do not supply all of the restore capabilities that
the NetBackup /usr/openv/netbackup/bin/tar provides. Possible
problems result.
The following is a list of some effects that a non-NetBackup tar may encounter
in certain situations:
■ Compressed backups cannot be recovered.
■ Multiplexed backups cannot be recovered.
■ Solaris extended attributes cannot be restored to a client.
■ VxFS named data streams cannot be restored to a client.
■ Backups cannot be recovered that contain raw partitions. (Includes
FlashBackup images.)
■ NDMP client backup images cannot be restored, though NDMP vendors may
have tools or the utilities that may perform a restore directly from the
media.
■ Non-NetBackup versions of tar may have trouble with sparse files and
often skip sparse files.
■ HP CDFs are restored with non-NetBackup versions of tar. The directory is
no longer hidden and the name of the directory has a + appended to it.
■ If the backup spans more than one piece of media, you must read and
combine the fragments from the media to give to tar. To combine the
fragments, the system’s dd command may be useful.
Another possibility is to use tar on the fragments. To use tar on
fragments may allow recovery of any file in the backup other than the one
that spanned the media.
Some versions of the HP9000-800 /bin/tar command are known to give a

directory checksum error for the second fragment of a backup that crossed
media.
■ Some versions of Solaris tar combine the atime, mtime, and ctime
strings with the file name and create the file paths that are not desirable.
To restore files with a non-NetBackup tar

The following process explains how to use a non-NetBackup tar to read a
backup from a NetBackup tape. Most versions of tar can read the tapes that
NetBackup creates after using the mt command to position to the proper tape
location. First, see the notes following the procedure as well as “Effects of a
non-NetBackup tar” on page 162 for possible limitations.
This sequence assumes that the media is known to Media Manager and that the
tape drive is under Media Manager control.
First, obtain the following information:
■ The media id of the tape that contains the required backup.

■ The tape file number of the backup on the tape (see the NetBackup Images
on Media report for this tape).
■ The tape type and density.
■ The tape pool.
To restore files with a non-NetBackup tar

1 tpreq -m media_id -a r -d density -p poolname -f
/tmp/tape
Where:
media_id is the media id of tape that contains the backup.
density is the density of the tape.
poolname is the volume pool to which the tape belongs
2 mt -f /tmp/tape rew
3 mt -f /tmp/tape fsf file_#
Where:
file_# is the tape file number of the backup on tape. Determine the tape file
number by checking the NetBackup Images on Media report for the tape.
4 mt -f /tmp/tape fsr
5 /bin/tar -tvfb /tmp/tape blocksize
Where:
■ blocksize is 64 (assume that the tape is written with 32K blocks)
6 tpunmount /tmp/tape
Notes on the procedure, “To restore files with a non-NetBackup tar” on

page 163:
1 This procedure does not apply to optical platters.
2 This procedure does not apply to encrypted backups using NetBackup
Encryption. Encrypted backups are recoverable, however, the backups
cannot be decrypted.
To determine if a backup is encrypted, run tar -t before the recovery. The
output for an encrypted backup is similar to the following example:
erw-r--r-- root/other Nov 14 15:59 2006 .EnCryYpTiOn.388
-rw-r--r-- root/other Oct 30 11:14 2006 /etc/group.10-30
Where the e at the beginning of line one indicates that the backup is
encrypted. (Additional messages appear during recovery.)
3 This procedure does not work on the Solaris platform. You cannot use
/usr/sbin/tar on Solaris to read NetBackup backups. The Solaris tar
command uses the ctime and the atime fields differently than other tar
commands.
When /usr/sbin/tar is used to restore backups, directories with large
numbers are created at the top level. These directories are from the ctime
and the atime fields being read as pathnames.
You can, however, use /usr/openv/netbackup/bin/tar or GNU tar to
read the backups on Solaris platforms.
4 Steps 1 and 6 are optional in a stand-alone environment. If step 1 is skipped,
DOWN the drive, then substitute the /dev path of the drive in place of
/tmp/tape in the other steps. Remember to UP the drive when you are
done.
Example
The following example was successful on an HP9000-800 with a DOWNed
4mm stand-alone drive and the NetBackup tar.
mt -t /dev/rmt/0hncb rew
mt -t /dev/rmt/0hncb fsf 1
mt -t /dev/rmt/0hncb fsr 1
/usr/openv/netbackup/bin/tar tvfb /dev/rmt/0hncb 64
Some platforms require other options on the tar command. The following
is required on Solaris 2.4:
/usr/openv/netbackup/bin/tar -t -v -f /dev/rmt/0hncb -b 64
Note: For additional limitations see, “Effects of a non-NetBackup tar” on

page 162.
Factors that affect backup time
Files that tar generates

Any version of tar (including NetBackup-modified tar), can generate a number
of files depending on the circumstances of the recovery:
■ @@MaNgLeD.nnnn
For backups containing pathnames longer than 100 characters, tar
generates the files that are named @@MaNgLeD.nnnn that contain the
actual file.
■ @@MaNgLeD.nnnn_Rename
tar generates another file (@@MaNgLeD.nnnn_Rename) that explains how
to rename the @@MaNgLeD.nnnn files to return the files to the correct
location.
■ @@MaNgLeD.nnnn_Symlink
For long names of symbolic links, tar generates the files that are named
@@MaNgLeD.nnnn_Symlink. These files contain descriptions of the
symbolic links that need to be made to return a link to the correct file.
■ For cross-platform ACLs restores, tar creates and stores the ACLs in
.SeCuRiTy.nnnn files in the root directory. Read or delete the files.
Regenerate the ACLs to the corresponding files by hand.
For more information, see “Restoring files and access control lists” on
page 681.
■ For cross-platform VxFS extent attribute restores, tar creates and stores
extent attributes in .ExTeNt.nnnn files in the root directory. The files can
either be deleted or read and the extent attributes regenerated by hand to
the corresponding files.

The time NetBackup requires to complete a backup is an important factor in
setting up schedules. The importance of time is particularly true for the sites
that handle large amounts of data. For example, the total backup time can
exceed the time that is allotted to complete backups and interfere with normal
network operations. Longer backup times also increase the possibility of a
problem that disrupts the backup. The time to back up files can also give an
indication of how long it may take to recover the files.
The following formula shows the major factors that affect backup time:
Backup Total data Compression Device

= x +
time Transfer rate factor (optional) delays
Total data
The total amount of data to back up depends on the size of the files for each
client included the policy. The total amount of data also depends on whether the
backup is a full backup or an incremental backup.
■ Full backups involve all the data. Therefore, a full backup usually takes
longer than an incremental backup.
■ Differential incremental backups include only the data that has changed
since the last full or incremental backup.
■ Cumulative incremental backups include all the data that has changed since
the last full backup.
For incremental backups, the amount of data depends on the frequency with
which files change. If a large number of files change frequently, incremental
backups are larger.
Transfer rate
The transfer rate depends on the following factors:
■ The speed of the backup device. Backups that are sent to tapes with a
transfer rate of 800 kilobytes per second are generally faster than tapes with
a transfer rate of 400 kilobytes. (Assume that other factors allow for the
faster transfer rate.)
■ The available network bandwidth. The available bandwidth is less than the
theoretical network bandwidth and depends on how much other network
traffic is present. For example, multiple backups occurring on the same
network compete for bandwidth.
■ The speed with which the client can process the data. The speed varies with
the hardware platform and depends on the other applications that run on
the platform. File size is also an important factor. Clients can process larger
files faster than smaller ones. A backup for twenty files, 1 megabyte each, is
faster than a backup for 20,000 files that are 1 kilobyte each.
■ The speed with which the server can process the data. Like client speed,
server speed also varies with the hardware platform and depends on the
other applications that run on the platform. The number of concurrent
backups being performed also affects server speed.
■ Network configuration can affect performance. For example, when some
machines run full-duplex and some run half-duplex in an Ethernet
environment, the throughput is significantly reduced.
For more information, see “Determining NetBackup transfer rate” on page 167.
Determining NetBackup transfer rate
Compression
Software compression often multiplies the backup time by a factor of two or
three for a given set of data.
Device delays
Device delays can be due to the following factors: the device may be busy or slow
to load the media. Or, the device may be slow to find the location on the media at
which to start writing the backup. These delays can vary widely and depend on
the devices and the computing environments.

Calculate three variations of the backup transfer rate by using NetBackup report
data. The following are the three rates and calculation methods:
■ “Network transfer rate” on page 167
■ “Network transfer plus end-of-backup-processing rate” on page 167
■ “Network transfer plus end-of-backup-processing rate” on page 167
Network transfer rate

The network transfer rate is the rate provided in the All Log Entries report.
The network transfer rate considers only the time it takes to transfer data over
the network from client to server. This rate ignores the following:
■ The time the device requires to load and position media before a backup.
■ The time that the tape file requires to close and write an additional
NetBackup information record to the tape.
Network transfer plus end-of-backup-processing rate

This rate ignores the time it takes to load and position media before a backup.
However, the rate does include the end-of-backup processing that is ignored in
the network transfer rate. To determine this rate, use the All Log Entries report
and calculate the time from the message:
begin writing backup id xxx
until the message

successfully wrote backup id xxx
To calculate the transfer rate, divide this time (in seconds) into the total bytes
that are transferred. (The total bytes that are transferred is recorded in the All
Log Entries report.)
Total transfer rate

This transfer rate includes the time it takes to load and position the media as
well as the end-of-backup processing. Use the List Client Backups report to
calculate the transfer rate by dividing Kilobytes by Elapsed Time (converted to
seconds).
Examples
Assume that the reports provide the following data.
Sample All Log Entries Report:
TIME SERVER/CLIENT TEXT
04/28/06 23:10:37 windows giskard begin writing backup
id giskard_0767592458, fragment 1 to
media id TL8033 on device 1 . . .
04/29/06 00:35:07 windows giskard successfully wrote
backup id giskard_0767592458,
fragment 1, 1161824 Kbytes at
230.325 Kbytes/sec
Sample List Client Backups Report:

Client: giskard
Backup ID: giskard_0767592458
Policy: production_servers
Client Type: Standard
Sched Label: testing_add_files
Schedule Type: Full
Backup Retention Level: one week (0)
Backup Time: 04/28/06 23:07:38
Elapsed Time: 001:27:32
Expiration Time: 05/05/06 23:07:38
Compressed: no
Kilobytes: 1161824
Number of Files: 78210
The following three rates were compiled with the backup data from the sample
reports:
Network transfer rate:
1161824 Kbytes at 230.325 Kbytes per second
Network transfer plus end-of-backup processing rate:
23:10:30 - 00:35:07 = 01:24:30 = 5070 seconds
1161824 Kbytes/5070 = 229.157 Kbytes per second
Total transfer rate:
Elapsed time = 01:27:32 = 5252 seconds
1161824 Kbytes/5252 = 221.216 Kbytes per second
How NetBackup builds a worklist
The following topics explain how NetBackup determines the order in which
automatic backups occur for each client. This information is useful to evaluate
problems with schedules.
Building the worklist (Queue)

NetBackup builds an internal worklist that contains all scheduled, active jobs.
NetBackup calculates the due time for each job, then sorts all the jobs in the
worklist in the order that the jobs are due:
a NetBackup builds a worklist that consists of jobs for every client in
every policy.
b NetBackup evaluates each job and determines when it is due, based on
the following factors:
■ When the job ran last
■ How often the job is scheduled to run (the frequency of the job)
■ How soon the next scheduled window is open for the job (if the
window is not currently open)
c NetBackup sorts the worklist by the due time of each job.
While a job waits for resources (devices) to become available, the job is
considered Queued, and appears on the Jobs tab of the Activity Monitor.
Once a job receives the resources it needs, the job becomes Active and begins.
When the job completes, NetBackup computes the next due time for the job, thus
the worklist is perpetually calculated and reordered.
The order of the jobs on the worklist is dynamic. The following items are some of
the factors that affect the job order on the worklist:
■ Whether the job finished successfully or whether it failed and is Waiting for
Retry.
(The time that NetBackup waits before it tries the job again is configurable
by setting the Job retry delay Global Attribute master server property.
A retried job retains the original job ID. If the job does not succeed after the
number of attempts that are allowed, the job is considered Done. The status
of the job indicates that the job was not successful. The number of attempts
counts toward the Schedule backup attempts limit. (Found under Host
Properties > Global Attributes > Schedule backup attempts.)
■ Whether attempts to run the job exceed the number of attempts that the
Schedule backup attempts host property indicates.
■ Whether the job is a child job. When a parent job is Active, all of the children
from that parent job have precedence over other jobs. The precedence
includes the children of another parent job.
To prioritize queued jobs

The worklist generally contains jobs from different policies and schedules.
NetBackup checks for the following items when it determines the order in which
to run the backups:
1 NetBackup checks for the jobs that are to be multiplexed. The jobs join an
existing multiplexed group if allowed, even if a job of higher priority is on
the worklist.
2 NetBackup checks the priority of the job, as determined by the policy Job
priority setting. Backup jobs from the policy with the highest priority run
first.
For example, assume that client_1 and client_2 are in different policies and
that client_1 is in the policy with the highest priority. Here, the jobs for
client_1 always run before the client_2 jobs.
3 NetBackup looks for backups with a retention level that is the same as a tape
that is currently mounted.
If policy priorities are equal, NetBackup tries to start a backup job that has
the same retention period as a tape that is currently mounted. To choose a
tape with the same retention level reduces delays to mount tapes.
For example, assume that client_1 and client_2 are in the same policy but
their schedules have different retention periods. Also, assume that the
client_1 job is the most overdue. However, a tape is mounted that has the
same retention level as client_2.
The client_2 job runs first because it can be stored on a tape that is already
mounted to use resources most efficiently. If there is another drive of the
correct type available, a tape is mounted on that drive for the client_1 job.
4 NetBackup looks for the backup jobs that are most overdue.
If the priorities and retention level are equal, NetBackup prioritizes
backups according to how long they are overdue. The clients that are the
most overdue have the highest priority.
To determine how long a backup is overdue, NetBackup subtracts the
frequency from the length of time since the last successful backup for that
client. (The backup frequency is indicated on the schedule in the policy.
For example, assume that client_1 and client_2 have some backup jobs that
are in the same policy and have the same retention level. The schedules for
these backup jobs both have a frequency of 1 day. The last backup for
client_1 ran 25 hours ago and the last backup for client_2 ran 26 hours ago.
Determining backup media requirements
Both clients are overdue for a backup. However, the job of client client_2 is
the most overdue and runs first.
This approach ensures that a backup that was unsuccessful during its
previous backup window has priority over the successful backups. The
priority of the most overdue jobs is important in a busy NetBackup
configuration where the backup window can close before all backups can
begin.
Determining backup media requirements

To determine how much media is available, NetBackup provides the following
tools:
■ The NetBackup Media Summary report, which lists the active and the
inactive media that is available to a server.
■ The available_media script in the
/usr/openv/netbackup/bin/goodies directory, which lists all the
media IDs that are available on the server where you run the script.
To manage a backup environment efficiently, determine the amount of media
that is required for both daily and long-term use. The daily requirement must be
known to ensure that enough media is available for each backup session. The
long-term requirements are necessary to assess costs for acquisition of new
media, storage devices, and off-site storage (if required).
For daily requirements, first determine the approximate amount of data in the
files that you back up to each type of media each day. Then, check the Media
Summary report and the results from running the available_media script to
verify that enough media IDs and disk space are available.
To plan for the future, consider the following points:
■ How long you want to retain the data. All backups on a given tape or optical
disk have the same retention level unless the Allow multiple retentions per
media property is enabled. If not enabled, additional media is required for
each different retention level.
■ Whether duplicates for off-site storage or extra security are needed.
■ Allow for new software releases and other special backups.
■ Allow for the replacement of old, worn media.
■ Consider the changes in disk usage patterns over time. If disk usage and
capacity increase, backup needs may also increase.
■ Consider the number of backups on one tape. Tape marks are created
between backups. A tape with many small backups (possibly incremental
backups) contains less real data when compared to a tape that contains
NetBackup notify scripts
fewer large backups. The sizes of the tape marks vary depending on the
media type. A tape that contains many small files has more backup overhead
because each file requires an extra 512 bytes for catalog information on the
media.
■ Media sharing may be used to help maximize tape usage.
■ If you have many different volume pools, ensure that enough media is
defined to accommodate the data.
Note: Ensure that the notify scripts can be run by other before using. To do so,
run chmod 755 script_name, where script_name is the name of the script.
NetBackup uses the following scripts or batch files for collecting information
and providing notification of events.
The following scripts are active on the master server:
/usr/openv/netbackup/bin/backup_notify
/usr/openv/netbackup/bin/backup_exit_notify
/usr/openv/netbackup/bin/dbbackup_notify
/usr/openv/netbackup/bin/diskfull_notify
/usr/openv/netbackup/bin/mail_dr_info.sh (must be created)
/usr/openv/netbackup/bin/restore_notify
/usr/openv/netbackup/bin/session_notify
/usr/openv/netbackup/bin/session_start_notify
/usr/openv/netbackup/bin/userreq_notify
/usr/openv/netbackup/bin/parent_end_notify
/usr/openv/netbackup/bin/parent_start_notify
Scripts that run on clients:
/usr/openv/netbackup/bin/goodies/bpstart_notify
/usr/openv/netbackup/bin/goodies/bpend_notify
/usr/openv/netbackup/bin/goodies/bpend_notify_busy
To use the client scripts, the scripts must first be created on the client. Use
the procedures as described in “bpstart_notify.bat (Microsoft Windows
clients only)” on page 176 and “bpend_notify.bat (Microsoft Windows
clients only)” on page 180.
For further information, refer to the comments in the scripts.
Caution: Applies to NetBackup Enterprise Server only.

If you use either the bpstart_notify or bpend_notify scripts, do not
include any commands that write to stdout. NetBackup sends the output that is
written to stdout to the server as part of the backup. The resulting backup can
abort with an error message that pertains to block sizes. Also, ensure that all
commands in the scripts are appropriate to the client platform. For example, the
-s parameter is invalid for the UNIX mail command on some UNIX platforms.
Its use can cause data to be written to stdout or stderr.
backup_notify
The backup_notify script runs on the NetBackup server where the storage
unit is located. It is called each time a backup is successfully written to media.
The parameters that NetBackup passes to this script are:
■ The name of the program doing the backup
■ The backup-image name or path
For example:
backup_notify bptm bilbo_0695316589
Note: Applies to NetBackup Enterprise Server only.

If NetBackup backs up files to a UNIX disk storage unit that Storage migratory
manages, the backup_notify script notifies Storage migratory to perform
migration as quickly as possible. The released script does not, however, have
commands to force a backup of the managed file system after NetBackup has
stored its backups. To back up the managed file system, modify the script as
necessary to meet site requirements for backup.
backup_exit_notify
The backup_exit_notify script runs on the master server. It is called to
perform site-specific processing when an individual backup completes.
Table 3-1 backup_exit_notify parameters
Parameter Description
clientname Name of the client from the NetBackup catalog.
policyname Policy name from the NetBackup catalog.
schedname Schedule name from the NetBackup catalog.

schedtype One of the following: FULL, INCR (differential incremental), CINC (cumulative incremental),
UBAK, UARC
exitstatus Exit code for the entire backup job.
For example:
backup_exit_notify freddie production fulls FULL 0
backup_exit_notify danr production incrementals INCR 73
bpstart_notify (UNIX clients only)
Note: Ensure that this script can be run by other on the client before it is used.
To do so, run chmod 755 script_name, where script_name is the name of the
script.
On UNIX clients, NetBackup calls the bpstart_notify script each time the
client starts a backup or an archive.
To use this script, copy the following file from the server:
/usr/openv/netbackup/bin/goodies/bpstart_notify
And place it to the following location on the UNIX client:

/usr/openv/netbackup/bin/
Modify the script and ensure that you have permission to run the script.
The bpstart_notify script runs each time a backup or an archive starts and
initialization is completed. The script runs before the tape is positioned. This
script must exit with a status of 0 for the calling program to continue and for the
backup or archive to proceed. A nonzero status causes the client backup or
archive to exit with a status of bpstart_notify failed.
If the /usr/openv/netbackup/bin/bpstart_notify script exists, it runs
in the foreground and the bpbkar process on the client waits for it to complete
before continuing. Any commands in the script that do not end with an &
character run serially.
The server expects the client to respond with a continue message within the
time that the BPSTART_TIMEOUT option specifies on the server.
The default for BPSTART_TIMEOUT is 300. If the script needs more time than
300 seconds, increase the value to allow more time.

Table 3-2 bpstart_notify parameters
schedtype One of the following: FULL, INCR (differential incremental), CINC (cumulative incremental),
UBAK, UARC
Caution: The bpstart_notify script also runs for NetBackup catalog backups
if a .policyname[.schedule] is not specified.
For example:
bpstart_notify freddie cd4000s fulls FULL
bpstart_notify danr cd4000s incrementals INCR
bpstart_notify hare cd4000s fulls FULL
bpstart_notify freddie cd4000s user_backups UBAK
bpstart_notify DangDang cd4000s user_archive UARC
To create a bpstart_notify script for a specific policy or policy and schedule

combination, create script files with a .policyname or .policyname.schedulename
suffix. The following are two examples of script names for a policy (production)
that has a schedule (fulls):
/usr/openv/netbackup/bin/bpstart_notify.production
/usr/openv/netbackup/bin/bpstart_notify.production.fulls
The first script affects all scheduled backups in the policy that are named
production. The second script affects scheduled backups in the policy that is
named production only when the schedule is named fulls.
Note: For a given backup, NetBackup uses only one bpstart_notify script and
that is the script with the most specific name. For example, if there are both
bpstart_notify.production and bpstart_notify.production.fulls
scripts, NetBackup uses only bpstart_notify.production.fulls.
The bpstart_notify script can use the following environment variables:

BACKUPID
UNIXBACKUPTIME
BACKUPTIME
The NetBackup bpbkar process creates these variables. The following are
examples of the strings that are available to the script to use to record
information about a backup:
BACKUPID=freddie_0857340526
UNIXBACKUPTIME=0857340526
BACKUPTIME=Sun Mar 2 16:08:46 2006
In addition, the following environment variables can be used to support multiple

data streams:
STREAM_NUMBER indicates the stream number. The first stream from a policy,
client, and schedule is 1. A 0 value indicates that multiple data streams is not
enabled.
STREAM_COUNT specifies the total number of streams to be generated from this
policy, client, and schedule.
STREAM_PID is the pid (process ID) number of bpbkar.
RESTARTED can be used for checkpointed restarts or checkpointed backup jobs.
A value of 0 indicates that the job was not resumed. (For example, upon first
initiation.) A value of 1 indicates that the job was resumed.
bpstart_notify.bat (Microsoft Windows clients only)

For all Windows clients, you can create some batch scripts that provide
notification whenever the client starts a backup or archive.
To use this script, copy the following file from the server:
/usr/openv/netbackup/bin/goodies/bpstart_notify.bat
And place it on the client in the same directory as the NetBackup client binaries:
Install_path\NetBackup\bin\
Where Install_path is the directory where NetBackup is installed.
You can create bpstart_notify scripts that provide notification for all
backups or for backups of a specific policy or schedule.
To create a script that applies to all backups, name the script
bpstart_notify.bat
To create a bpstart_notify script that applies only to a specific policy or
policy and schedule combination, add a .policyname or
.policyname.schedulename suffix to the script name.
■ The following script applies only to a policy named days:
install_path\netbackup\bin\bpstart_notify.days.bat
■ The following script applies only to a schedule that is named fulls in a policy
named days:
install_path\netbackup\bin\bpstart_notify.days.fulls.bat

Caution: The bpstart_notify script also runs for NetBackup catalog backups
if a .policyname[.schedule] is not specified.
The first script affects all scheduled backups in the policy named days. The
second script affects scheduled backups in the policy named days only when the
schedule is named fulls.
For a given backup, NetBackup calls only one bpstart_notify script and
checks for them in the following order:
bpstart_notify.policy.schedule.bat
bpstart_notify.policy.bat
bpstart_notify.bat
For example, if there are both bpstart_notify.policy.bat and

bpstart_notify.policy.schedule.bat scripts, NetBackup uses only the
bpstart_notify.policy.schedule.bat script.
Note: bpend_notify scripts can provide a different level of notification than

the bpstart_notify scripts. For example, to use one of each, the script names
might be bpstart_notify.policy.bat and
bpend_notify.policy.schedule.bat.
When the backup starts, NetBackup passes the following parameters to the
script.
Table 3-3 bpstart_notify.bat parameters
%1 Name of the client from the NetBackup catalog.
%2 Policy name from the NetBackup catalog.
%3 Schedule name from the NetBackup catalog.
%4 One of the following: FULL, INCR, CINC, UBAK, UARC
%5 Status of the operation is always 0 for bpstart_notify.

%6 Results file that NetBackup checks for a return code from the script. NetBackup uses %6 to
pass the file name and then expects the script to create the file in the same directory as the
script.
If the script applies to a specific policy and schedule, the results file must be named
install_path\netbackup\bin\BPSTART_RES.policy.schedule
If the script applies to a specific policy, the results file must be named
install_path\netbackup\bin\BPSTART_RES.policy
If the script applies to all backups, the results file must be named
install_path\netbackup\bin\BPSTART_RES
An echo 0> %6 statement is one way for the script to create the file.
NetBackup deletes the existing results file before it calls the script. After the script runs,
NetBackup checks the new results file for the status. The status must be 0 for the script to
be considered successful. If the results file does not exist, NetBackup assumes that the
script was successful.
time that the NetBackup BPSTART_TIMEOUT option specifies. The default for
BPSTART_TIMEOUT is 300. If the script needs more than 300 seconds, increase
the value to allow more time.
For Windows 2000 clients, the bpstart_notify script can use the following
environment variables for the support of multiple data streams:
enabled.
bpend_notify (UNIX clients only)
Caution: The bpend_notify script is run when the client is finished sending
data, but the server has not yet completed writing to media.
To receive a notification whenever a UNIX client completes a backup or an

archive operation, copy the following file from the server:
/usr/openv/netbackup/bin/goodies/bpend_notify
And place it to the following location on the UNIX client:

/usr/openv/netbackup/bin/bpend_notify
Modify the script and ensure that you have permission to run the script.
The bpend_notify script runs each time a backup or archive completes. For
archives, it runs after the backup but before the files are removed.
If bpend_notify exists, it runs in the foreground and bpbkar on the client
waits until it completes. Any commands that do not end with an & character run
serially.
The server expects the client to respond within the time that the
BPEND_TIMEOUT NetBackup configuration option specifies. The default for
BPEND_TIMEOUT is 300.
If the script needs more than 300 seconds, set BPEND_TIMEOUT to a larger
value. Avoid too large a value because it can delay the server from servicing
other clients.
NetBackup passes the following parameters to the bpend_notify script.
Table 3-4 bpend_notify parameters
schedtype One of the following: FULL, INCR (differential incremental), CINC
(cumulative incremental), UBAK, UARC
exitstatus Exit code from bpbkar. The status is the client status and does not
indicate that the backup is complete and successful.
The client can display a status 0 when, due to a failure on the server,
the All Log Entries report displays a status 84.
Caution: The bpend_notify script also runs for NetBackup catalog backups if a
.policyname[.schedule] is not specified.
For example:
bpend_notify freddie pol_1 fulls FULL 0
bpend_notify danr pol_1 incrementals INCR 73

To create a bpend_notify script for a specific policy or policy and schedule
combination, create script files with a .policyname or .policyname.schedulename
suffix. The following are two examples of script names for a policy that is named
production with a schedule that is named fulls:
/usr/openv/netbackup/bin/bpend_notify.production
/usr/openv/netbackup/bin/bpend_notify.production.fulls
The first script affects all scheduled backups in the policy production. The
second script affects scheduled backups in the policy production only when the
Note: For a given backup, NetBackup uses only one bpend_notify script and
that is the one with the most specific name. For example, if there are both
bpend_notify.production and bpend_notify.production.fulls
scripts, NetBackup uses only bpend_notify.production.fulls.
If the UNIX client is running NetBackup 3.0 or later software, the

bpend_notify script can use the following environment variables:
BACKUPID
UNIXBACKUPTIME
BACKUPTIME
The NetBackup bpbkar process creates these variables. The following are
examples of the strings that are available to the script for use to record
information about a backup:
BACKUPID=freddie_0857340526
UNIXBACKUPTIME=0857340526
BACKUPTIME=Sun Mar 2 16:08:46 2005
The following environment variables can be used for the support of multiple
data streams:
enabled.
FINISHED can be used for checkpointed restarts of backup jobs. A value of 0
indicates that the client was not finished sending all of the data. A value of 1
indicates that the client was finished sending all the of data.
bpend_notify.bat (Microsoft Windows clients only)

For Windows clients, you can create some batch scripts that provide notification
whenever the client completes a backup or archive. These scripts must reside on
the client and in the same directory as the NetBackup client binaries:
Install_path\NetBackup\bin\bpend_notify.bat
Where Install_path is the directory where NetBackup is installed.
You can create bpend_notify scripts that provide notification for all backups
or for backups of a specific policy or schedule.
To create a bpend_notify script that applies to all backups, name the script
bpend_notify.bat
To create a script that applies only to a specific policy or policy and schedule
combination, add a .policyname or .policyname.schedulename suffix to the
script name.
■ The following script applies only to a policy named days:
Install_path\netbackup\bin\bpend_notify.days.bat
■ The following script applies only to a schedule that is named fulls in a policy
named days:
Install_path\netbackup\bin\bpend_notify.days.fulls.bat
Caution: The bpend_notify script also runs for NetBackup catalog backups if a
.policyname[.schedule] is not specified.
The first script affects all scheduled backups in the policy named days. The
second script affects scheduled backups in the policy named days only when the
For a given backup, NetBackup calls only one bpend_notify script and checks
for them in the following order:
bpend_notify.policy.schedule.bat
bpend_notify.policy.bat
bpend_notify.bat
For example, if there are both bpend_notify.policy.bat and

bpend_notify.policy.schedule.bat scripts, NetBackup uses only
Note: bpstart_notify scripts can provide a different level of notification than

the bpend_notify scripts. For example, if you had one of each, they could be
bpstart_notify.policy.bat and
When the backup completes, NetBackup passes the following parameters to the
script.
Table 3-5 bpend_notify parameters
%1 Name of the client from the NetBackup catalog.
%2 Policy name from the NetBackup catalog.
%3 Schedule name from the NetBackup catalog.
%4 One of the following: FULL, INCR, CINC, UBAK, UARC
%5 Status of the operation. It is the same as sent to the NetBackup server. The status is 0 for
successful backups and 1 for partially successful backups. If an error occurs, the status is the
value associated with that error.
%6 Results file that NetBackup checks for a return code from the script. NetBackup uses %6 to pass
the file name and then expects the script to create the file in the same directory as the script.
If the script applies to a specific policy and schedule, the results file must be named
Install_path\netbackup\bin\BPEND_RES.policy.schedule
If the script applies to a specific policy, the results file must be named
Install_path\netbackup\bin\BPEND_RES.policy
If the script applies to all backups, the results file must be named
Install_path\netbackup\bin\BPEND_RES
An echo 0> %6 statement is one way for the script to create the file.
NetBackup deletes the existing results file before it calls the script. After the script runs,
NetBackup checks the new results file for the status. The status must be 0 for the script to be
considered successful. If the results file does not exist, NetBackup assumes that the script was
successful.
time that the BPEND_TIMEOUT option specifies. The default for
BPEND_TIMEOUT is 300. If the script needs more than 300 seconds, increase the
value to allow more time.
For Windows 2000 clients, the bpend_notify script can use the following
environment variables for the support of multiple data streams:
enabled.
bpend_notify_busy (UNIX clients only)

The bpend_notify_busy script is used to configure busy file processing when
using the bp.conf file. For more information, see “Busy file processing (UNIX
clients only)” on page 105.
Busy file processing can also be configured in the Busy File Settings host
properties of the NetBackup Administration Console.
dbbackup_notify
NetBackup calls the dbbackup_notify script each time NetBackup completes
an offline, cold catalog backup. The script runs on the server that receives the
data for the offline catalog backup. NetBackup passes the following parameters
to this script.
Table 3-6 dbbackup_notify parameters
device Device type the backup was written to.
vsn_or_path Volume serial number (for tape) or path (for disk) used for the backup.
status Specifies whether the backup was successful and must have a value of
either SUCCESS or FAIL.
For example:
dbbackup_notify DISK /disk1/bpsync1 SUCCESS
dbbackup_notify OPTICAL AA0001 FAIL
dbbackup_notify TAPE XYZ047 SUCCESS
You must be able to identify the most recent catalog backup. Modify this script
to produce a printed copy of the media ID to which the catalog backup was done.

If the NetBackup catalog files are backed up to a UNIX disk storage unit that
Storage Migrator manages, the dbbackup_notify script notifies Storage
Migrator to perform migration as quickly as possible. The script does not,
however, have commands to force Storage Migrator to back up its own catalog
after a backup of the NetBackup catalog. You must modify the script to meet site
requirements for backup of the Storage Migrator catalog.
diskfull_notify
The diskfull_notify script runs on the NetBackup server contains the
storage unit. The disk media manager (bpdm) calls this script if it encounters a
disk full condition while it writes a backup to a disk storage unit. The default
action is to report the condition and immediately try to write the data again.
(The file being written is kept open by the active bpdm).
The script can be modified to send a notification to an email address. Or
modified to perform actions such as removing other files in the affected
directory or file system. NetBackup passes the following parameters to this
script.
Table 3-7 diskfull_notify parameters
programname Name of the program (always bpdm).
pathname Path to the file being written.
For example:
diskfull_notify bpdm
/disk1/images/host_08193531_c1_F1
Note
In previous releases, the diskfull_notify script default condition was to
sleep for five minutes when a disk storage unit became full. To retain this
behavior upon upgrade, either:
■ Copy the netbackup/bin/diskfull_notify.old_revision_number
script to netbackup/bin/diskfull_notify, or
■ Modify the script, to change sleep 0 to:
sleep 300
mail_dr_info.sh
Use mail_dr_info.sh to send NetBackup disaster recovery information to
specified recipients after running an online, hot catalog backup.
To create the script, touchthe following file:
/usr/openv/netbackup/bin/mail_dr_info.sh
Update the script using the following exit parameters.

Table 3-8 mail_dr_info.sh parameters
%1 The recipient's address. For multiple addresses, enter email1,email2
%2 The subject line.
%3 The message file name.
%4 The attached file name.
NetBackup checks to see if mail_dr_info.sh is present in

/usr/openv/netbackup/bin. If mail_dr_info.cmd exists, NetBackup
passes the parameters to the script.
mail_dr_info.sh is not an installed file. Users must create the script.
parent_end_notify
NetBackup calls the parent_end_notify script each time a parent job ends.
Update the script using the following parameters.
Table 3-9 parent_end_notify parameters

status Exit code for the entire backup job.
streamnumber The stream number for a parent job is always -1.
parent_start_notify
NetBackup calls the parent_start_notify script each time a parent job
starts.
Update the script using the following parameters.
Table 3-10 parent_start_notify parameters

status Exit code for the entire backup job.
streamnumber The stream number for a parent job is always -1.
restore_notify

If the files are restored to a UNIX disk storage unit that Storage Migrator
manages, the restore_notify script notifies Storage Migrator to perform
migration as quickly as possible after the restore is complete.
The restore_notify script runs on the server that contains the storage unit.
The NetBackup tape or disk manager (bptm or bpdm) calls the script when it is
finished sending data to the client during a restore. The script is called
regardless of whether data is sent.) NetBackup passes the following parameters
to this script.
Table 3-11 restore_notify parameters
programname Name of the program doing the restore or other read operation.
pathname Path to the backup name or path.
operation One of the following: restore, verify, duplication, import
For example:
restore_notify bptm bilbo_0695316589 duplication
session_notify
The session_notify script runs on the master server. It is called at the end of
a backup session if at least one scheduled backup has succeeded. NetBackup
Media and device management best practices
passes no parameters to this script. Scheduling is suspended until this script

completes, so no other backups can start until that time.
session_start_notify
The session_start_notify script runs on the master server. When a set of
backups is due to run, NetBackup calls this script to do any site-specific
processing before it starts the first backup. NetBackup passes no parameters to
this script.
userreq_notify
The userreq_notify script runs on the master server. NetBackup calls it each
time a request is made to:
■ List files that are in backups or archives
■ Start a backup, archive, or restore
You can alter this script to gather information about user requests to
NetBackup. NetBackup passes the following parameters to this script.
Table 3-12 userreq_notify parameters
action Defines the action and can have the following values: backup,
archive, manual_backup, restore, list
clientname Defines the client name.
userid Defines the user ID.
For example:
userreq_notif backup mercury jdoe
userreq_notify archive mercury jdoe
userreq_notify manual_backup mercury jdoe
userreq_notify restore mercury jdoe
userreq_notify list mercury jdoe

The following are best practices for NetBackup media and device management.
If you follow these recommendations, you can minimize problems. Many of
these practices also reduce the time and effort that are required to administer
your configuration. Following these best practices should save you time.
For a list of supported devices, server platforms, and the latest device mapping
file, see the NetBackup support web site, http://entsupport.symantec.com.
General practices
The following are general best practices for media and device management:
■ Use only Symentec documented and Symentec supported options for
NetBackup commands.
■ Refer to the NetBackup release notes to see if the methods you use are
eliminated in the current release or eliminated in future releases. The
release notes also contain information about all new functionality in each
release.
■ Use the documented methods for terminating the NetBackup Media
Manager daemons and services.
■ Periodically verify your backups using NetBackup Management > Catalog in
the NetBackup Administration Console. Also, periodically restore files to
prove that restores work correctly.
■ Always back up the NetBackup catalogs. You may also want to back up the
vm.conf and bp.conf (UNIX system) files on your media servers. Those
files contain configuration settings.
■ When you restore the NetBackup catalog (for example, master server
databases and the EMM database), use backups from the same point in time.
■ Ensure that all names and numbers for devices and all media IDs and
barcodes are unique across the entire enterprise.
■ To use devices with other applications and NetBackup controls those
devices, you must do one of the following to avoid potential loss of data:
■ Use the NetBackup tpreq command to mount media on a drive and
tpunmount to remove media from the drive. If you use these
commands, another application can control a device when NetBackup
is finished with the device.
■ Down the drive, if the drive is in the UP state.
Media management
The following are media management best practices:
■ Use the robot inventory update operation for media management.
■ Use a scratch pool for unassigned media.
■ Configure cleaning cartridges for your tape drives, and use TapeAlert for
automatic drive cleaning if the drives support automatic cleaning.
■ Replace old media according to the life-span recommendations of the
manufacturer. Replace old cleaning media also.
■ Use robotic libraries that have a barcode reader and use only barcode labels
that the robot vendor recommends.
■ Use barcode rules for media type assignment when you inventory
multimedia libraries. Use barcode naming conventions to differentiate
between data and cleaning tapes and different physical media types. A
common convention is a prefix that identifies the type of media.
■ Before performing inject or eject commands, ensure that the media access
port is empty. Although NetBackup can handle a port that is not empty,
some libraries may have problems.
Device management
The following are device management best practices:
■ Monitor the NetBackup system log for device errors encountered.
■ Monitor devices by using the NetBackup Device Monitor.
■ Investigate the causes of all drives that are down.
■ Do not use the robotic test utilities while running backup or restore jobs.
■ Read the NetBackup Device Configuration Guide before configuring devices
on media servers (or SAN media servers).
■ Use only robots, tape drives and tape drivers, and server platforms and
hardware that are tested and supported by Symatec. For supported devices,
see the NetBackup hardware compatibility list on the NetBackup support
site.
■ Use only fully-serialized devices. A fully-serialized SCSI library should
report a serial number for the robot and also a serial number for each drive
in the robot.
■ Always configure and use pass-through paths for robotic libraries and
drives.
■ When possible, use SCSI reserve.
■ Use persistent bindings for fibre-attached devices.
■ Use the NetBackup Device Configuration wizard to configure your devices.
■ Download and install the latest device mapping file from the NetBackup
support web site before you use the Device Configuration wizard.
Using TapeAlert
■ Use consistent logical drive types for all physical drive types on all servers
in your environment. For example, use dlt as the logical drive type for all
DLT7000 drives.
■ Do not load vendor medium-changer drivers on Microsoft Windows hosts.
The default Microsoft medium-changer driver is acceptable (but is not
required) for use with NetBackup.
Performance and troubleshooting

The following are performance and troubleshooting best practices:
■ Use the performance-tuning documents available on the NetBackup support
Web page.
■ Use only a dedicated server for the NetBackup master server and Enterprise
Media Manager (EMM) server. Do not use a server that hosts other
applications or stores data. Plan periodic maintenance periods for all of your
backup servers.
■ Consult the Troubleshooter in the NetBackup Administration Console or the
NetBackup Troubleshooting Guide for all error conditions.
■ Always install the latest NetBackup release updates that are available from
Symantec.
■ Verify all SCSI-related operating system configuration files (for example, the
Solaris st.conf file), when you install operating system release updates.
■ For problems with devices, consult the vendor for firmware upgrades and
consult the NetBackup hardware compatibility list for supported firmware
levels.
■ Do not use the NetBackup DISABLE_RESOURCES_BUSY touch file.
■ Do not disable the operating system TCP_NODELAY functionality.
■ See the NetBackup Shared Storage Guide before you install and configure
the NetBackup Shared Storage Option, OpenStorage, or SharedDisk.
Using TapeAlert
TapeAlert is a tape drive status monitor and message utility. The TapeAlert
utility can detect tape quality problems, defects in tape drive hardware, and the
need to clean drives. For the tape drives that support TapeAlert, the TapeAlert
firmware monitors the drive hardware and the media. Error, warning, and
informational states are logged on a TapeAlert log page. NetBackup writes
TapeAlert conditions into:
Using TapeAlert
■ The bptm log

■ The error log
■ The job details log
■ The system log on UNIX and Event Viewer on Windows
For more information, also see “Reactive cleaning (TapeAlert)” on page 194.
Requirements for using TapeAlert

To use TapeAlert, all of the following conditions must be true. No additional
configuration is needed.
■ The drive must support the TapeAlert capability, and the TapeAlert must be
enabled on the drive.
To determine if a drive supports TapeAlert, see the Symantec support site.
■ To clean drives using TapeAlert, a cleaning tape is configured and available
in NetBackup for the robotic library.
■ The cleaning tape has not reached its end of life.
■ Passthru device files must be configured on UNIX media servers. For more
information, see the NetBackup Device Configuration Guide.
TapeAlert log codes

TapeAlert codes are derived from the T10 SCSI-3 Stream Commands standard.
Refer to the device’s documentation for the list of codes that are supported by
the device. TapeAlert checks for errors of the following types:
■ Recoverable read and write drive problems
■ Unrecoverable read and write drive problems
■ Hardware defects
■ Wrong or worn-out media
■ Expired cleaning tapes
■ Abnormal errors
Using TapeAlert
A set of TapeAlert conditions are defined that can cause the media in use to be
frozen. An additional set of conditions are defined that can cause a drive to be
downed. Table 3-13 on page 192 describes the TapeAlert codes..
Table 3-13 TapeAlert log codes
TapeAlert code Default action Error type Error message
0x01 None Warning - WRN READ WARNING
0x02 None Warning - WRN WRITE WARNING
0x03 None Warning - WRN HARD ERROR
0x04 Freeze media - FRZ Critical - CRT MEDIA
0x05 Freeze media - FRZ Critical - CRT READ FAILURE
0x06 Freeze media - FRZ Critical - CRT WRITE FAILURE
0x07 Freeze media - FRZ Warning - WRN MEDIA LIFE
0x08 Freeze media - FRZ Warning - WRN NOT DATA GRADE
0x09 None Critical - CRT WRITE PROTECT
0x0a None Informational - NO REMOVAL

INFO
0x0b None Informational - CLEANING MEDIA

INFO
0x0c None Informational - UNSUPPORTED

INFO FORMAT
0x0d Freeze media - FRZ Critical - CRT REC. MECH.

CARTRIDGE FAILURE
0x0e Freeze media - FRZ Critical - CRT UNREC. MECH.

CARTRIDGE FAILURE
0x0f Freeze media - FRZ Warning - WRN MIC FAILURE
0x10 None Critical - CRT FORCED EJECT
0x11 None Warning - WRN READ ONLY
0x12 None Warning - WRN DIRECTORY

CORRUPTED ON LOAD
0x13 Freeze media - FRZ Informational - NEARING MEDIA LIFE

INFO
0x14 Clean drive - CLN Critical - CRT CLEAN NOW

Using TapeAlert
Table 3-13 TapeAlert log codes (continued)
0x15 Clean drive - CLN Warning - WRN CLEAN PERIODIC
0x16 Freeze media - FRZ Critical - CRT EXPIRED CLEANING

MEDIA
0x17 Freeze media - FRZ Critical - CRT INVALID CLEANING

TAPE
0x18 None Warning - WRN RETENSION

REQUESTED
0x19 None Warning - WRN DUAL-PORT ERROR
0x1a None Warning - WRN COOLING FAN

FAILURE
0x1b None Warning - WRN POWER SUPPLY

FAILURE
0x1c None Warning - WRN POWER

CONSUMPTION
0x1d None Warning - WRN DRIVE MAINTENANCE
0x1e Down drive - DOWN Critical - CRT HARDWARE A
0x1f Down drive - DOWN Critical - CRT HARDWARE B
0x20 None Warning - WRN INTERFACE
0x21 None Critical - CRT EJECT MEDIA
0x22 None Warning - WRN DOWNLOAD FAIL
0x23 None Warning - WRN DRIVE HUMIDITY
0x24 None Warning - WRN DRIVE TEMPERATURE
0x25 None Warning - WRN DRIVE VOLTAGE
0x26 None Critical - CRT PREDICTIVE FAILURE
0x27 None Warning - WRN DIAGNOSTICS REQ.
0x28 - 0x31 None Informational UNDEFINED

INFO
0x32 None Warning - WRN LOST STATISTICS
0x33 Freeze media - FRZ Warning - WRN DIRECTORY INVALID

ON UNLOAD
Drive cleaning overview
Table 3-13 TapeAlert log codes (continued)
0x34 Freeze media - FRZ Critical - CRT SYSTEM AREA WRITE

FAILURE
0x35 Freeze media - FRZ Critical - CRT SYSTEM AREA READ

FAILURE
0x36 Freeze media - FRZ Critical - CRT NO START OF DATA
0x37 Freeze media - FRZ Critical - CRT LOADING FAILURE
0x38 Freeze media - FRZ Critical - CRT UNREC. UNLOAD

FAILURE
0x39 None Critical - CRT AUTOMATION

INTERFACE FAILURE
0x3a None Warning - WRN FIRMWARE FAILURE
0x3b Freeze media - FRZ Warning - WRN WORM MEDIUM -

INTEGRITY CHECK
FAILED
0x3c Freeze media - FRZ Warning - WRN WORM MEDIUM -

OVERWRITE
ATTEMPTED
0x3d - 0x40 None Informational - UNDEFINED

INFO

The following types of drive cleaning are available using NetBackup:
■ Reactive cleaning
Symantec recommends that you use reactive cleaning.
■ Library-based cleaning
■ Frequency-based cleaning
■ Operator-initiated cleaning
Reactive cleaning (TapeAlert)

Reactive cleaning (also known as on-demand cleaning or TapeAlert cleaning)
using TapeAlert is a function of the tape drive. The drive determines and
initiates the cleaning when needed. If a drive supports the TapeAlert capability
and it is enabled on the drive, the NetBackup bptm process polls the drive for
status from TapeAlert.
TapeAlert allows reactive cleaning for most drive types. Not all platforms,
robots, drives, or firmware levels support this type of reactive cleaning.
For the drives that do not support TapeAlert, you can configure and use
frequency-based cleaning. For more information, see “Frequency-based
cleaning” on page 196 and “TapeAlert and frequency-based cleaning” on
page 195.
Symantec recommends that you use reactive cleaning.
For more information, see “Requirements for using TapeAlert” on page 191.
TapeAlert cleaning
A drive with TapeAlert capability tracks how many read and write errors it has
encountered within a certain time period. Although a drive can recover from
these errors, the drives sets a CLEAN_NOW or CLEAN_PERIODIC flag when a
threshold is reached.
If bptm detects that either of these flags is set, it performs a cleaning at one of
the following times:
■ At the end of a backup or a restore to the drive.
■ Before the next backup or restore to the drive.
TapeAlert and frequency-based cleaning

Using TapeAlert with frequency-based cleaning ensures that a drive is cleaned
at least every x hours, depending on the setting for the cleaning frequency. In
addition, the drive may be cleaned sooner, if the CLEAN_NOW or
CLEAN_PERIODIC TapeAlert flags are set by the drive.
When you use TapeAlert without frequency-based cleaning, a drive is cleaned
only when the drive sets its CLEAN_NOW or CLEAN_PERIODIC flags.
Library-based cleaning
NetBackup does not support library-based cleaning (also known as robotic
cleaning or auto cleaning) for most robots because robotic library and operating
systems vendors have implemented this cleaning in different ways. These
different methods often interfere with NetBackup robotic control operations.
NetBackup does not define cleaning media that is used for library-based
cleaning, and the robotic library manages the cleaning media.
Because TapeAlert provides the same type of cleaning as library-based cleaning,

Symantec recommends that you disable library-based cleaning when using
TapeAlert.
Frequency-based cleaning
Frequency-based cleaning occurs when the accumulated mount time exceeds
the time you specify for the cleaning frequency. NetBackup updates the mount
time for the drive each time a tape is unmounted.
The cleaning frequency is configured when you add a drive to NetBackup. You
can also change the cleaning frequency by changing the drive properties or by
using the Media and Device Management Device Monitor.
If the following conditions are met, drive cleaning occurs when the accumulated
mount time exceeds the time you specified for cleaning frequency:
■ The drive is in a robotic library that supports drive cleaning.
■ A cleaning tape is configured and available for the robotic library.
■ The cleaning tape has cleanings that remain.
NetBackup cleans the drive immediately after a tape is unmounted. Drive
cleaning never causes an unmount in the middle of an active backup. The mount
time is reset after the drive is cleaned. The cleaning frequency value remains the
same.
A cleaning can occur within a backup if the backup spans tapes. For example, if
cleaning is due after the first tape is full, NetBackup cleans the drive before it
mounts the next tape.
Media can remain in a drive for extended periods. It does not affect cleaning
frequency because NetBackup increments the mount time only when NetBackup
assignes the media to a process.
Frequency-based cleaning limitations

The following applies only to NetBackup Enterprise Server.
Frequency-based cleaning is not supported for drives in ACS or TLH libraries
that are under API robotic control. The robotic library software controls the
drive cleaning. To manage drive cleaning for these robots, use the robot vendor
interfaces.
Operator-initiated cleaning
You can initiate a drive cleaning regardless of the cleaning frequency or
accumulated mount time of the drive. You can clean stand-alone drives or
Volume pool and volume group overview
robotic drives if a cleaning tape of the correct media type and residence for the
drive was added to NetBackup.
NetBackup reports that a drive needs cleaning if either of the following
conditions are true:
■ The value for the mount time is greater than the cleaning frequency.
■ The TapeAlert CLEAN_NOW or CLEAN_PERIODIC flag is set.
and either of the following conditions are true:
■ The drive is a stand-alone drive and a cleaning tape is not defined.
■ The drive is a stand-alone drive and no cleaning tape has any cleanings that
remain.
NetBackup displays NEEDS CLEANING as follows:
■ The Tape Cleaning Comment column of the Drive List in the Devices node of
the NetBackup Administration Console.
■ The comment field of the output from the tpclean -L command.
Using a cleaning tape
Note: NetBackup does not control the cleaning tapes that library-based cleaning
uses.
You can specify the number of cleanings that are allowed for a cleaning tape.
This number is decremented with each cleaning. When the number of cleanings
is zero, NetBackup stops using the cleaning tape. You can use a new cleaning
tape or increase the number of cleanings that are allowed for the tape.
Symantec suggests that you follow the recommendations from cleaning tape
vendors for the amount of tape usage. If you use a cleaning tape past its
recommended life, cleaning delays may occur (due to excessive tape position
operations) and drives may be downed.

A volume pool is used to identify a logical set of volumes by usage.
A volume group is a logical grouping that identifies a set of volumes that reside
at the same physical location. Volume groups are convenient for updating a
configuration when you move volumes (for example, from robotic to
stand-alone).
You specify volume pools and volume groups when you add volumes to
NetBackup.
Volume pools
The volume pool concept is relevant only for NetBackup storage units and does
not apply to disk storage units.
Volume pools protect volumes from access by unauthorized users, groups, or
applications. You can create volume pools for user groups or other reasons, and
as you add volumes, associate them with the appropriate pool. You can also
move unassigned volumes to a different pool.
With the exception of the CatalogBackup, NetBackup, and DataStore volume
pools, you must create a volume pool before you can add volumes to it. By
default, NetBackup creates volume pools named None, NetBackup,
CatalogBackup, and DataStore.
Volume groups
Volume groups show the location of a volume, such as the robot in which it
resides. If you move a volume physically, you also must move it logically (a
logical move means to change the volume attributes to show the new location).
Volume groups are convenient for tracking the location of volumes, such as the
case when a volume is moved off-site.
Volume groups let you perform operations on a set of volumes by specifying the
group name rather than each individual media ID of each volume. Operations
include moves between a robotic library and a stand-alone location or
deletetions from NetBackup.
Rules for assigning volume groups

The following are the rules for assigning volume groups:
■ All volumes in a group must be the same media type.
However, a media type and its corresponding cleaning media type are
allowed in the same volume group (such as DLT and DLT_CLN).
■ All volumes in a robotic library must belong to a volume group. You cannot
add volumes to a robotic library without specifying a group or having Media
Manager generate a name for the group.
■ The only way to clear a volume group name is to move the volume to
stand-alone and not specify a volume group.
■ More than one volume group can share the same location. For example, a
robotic library can contain volumes from more than one volume group and
you can have more than one stand-alone volume group.
■ All volumes in a group must be in the same robotic library or be stand-alone.

That is, you cannot add a group (or part of a group) to a robotic library if it
already exists in another robotic library.
Volume pool and volume group example

Figure 3-1 on page 199 shows an example with one volume pool (named
NB_pool) and several volume groups. In this example, volumes can be moved
between the groups in the robotic library and any groups that are off-site. All
volumes, however, remain in the same pool.
Figure 3-1 Volume pool with multiple volume groups
Standalone
Robotic NB_pool
Off-site 1
Group 1 Group 2
Group 3 Group 4
Off-site 2
In Figure 3-2 on page 200, members of the same volume pools are in different
volume groups. Note that the data is stored on separate volumes by assigning
different volume pools. The volumes in a pool can be in more than one physical
location and in more than one volume group.
In this example, the volumes in the pool NB_pool_dept_1 are spread among the
rob_A, standalone1, and off-site volume groups. These groups also have
volumes from more than one pool (though the volumes in each group must all be
the same type).
Figure 3-2 Volume groups with multiple volume pools
Robot A Standalone
Group Standalone Group
rob_A off-site
Group
standalone1
NB_pool
_dept_1
NB_pool
_dept_2
Robot B
Group
rob_B
NB_pool
_dept_3
You also can configure a scratch pool from which NetBackup can transfer
volumes when a volume pool has no media available. For more information, see
“Scratch volume pools” on page 200.
Scratch volume pools

The scratch pool is an optional volume pool that you can configure. If a scratch
pool is configured, NetBackup moves volumes from that scratch pool to other
pools that have do not have volumes available.
Scratch pool example

In Figure 3-3 on page 201, the scratch pool is named Scratch_pool. The three
robots contain volumes from that pool in addition to those from other pools.
Assume the following sequence of events:
■ NetBackup requires a DLT volume, so Media Manager attempts to assign one
from NB_pool_dept_1 in Robot C.
■ Robot C has no unassigned volumes available in the NB_pool_dept_1 pool.
■ NetBackup searches the scratch pool for an unassigned DLT volume in

Robot C. If a volume is available, NetBackup moves it to NB_pool_dept_1.
Otherwise, NetBackup logs a media unavailable status.
Figure 3-3 Scratch pool example
Robot A - TL8 Robot C - DLT
Group
Group
rob_A rob_C
NB_pool_dept_1
Scratch_pool
Robot B - TL8
Group
rob_B
NB_pool_dept_2
Scratch pool usage

The following list contains important notes about scratch pool usage:
■ If the scratch pool contains assigned volumes, these volumes remain in the
scratch pool. Media Manager does not move assigned volumes to other pools
as it does with unassigned volumes.
■ NetBackup does not assign volumes while they are in a scratch pool. For
example if a NetBackup policy or schedule specifies the scratch pool, all
requests for those volumes are denied.
■ Media Manager returns expired media to the scratch volume pool
automatically (media that is returned must have been originally in the same
scratch pool).
Barcode overview
■ To have Media Manager manage the allocation of your volumes to your

volume pools, do the following:
a Create volume pools as required, but do not add any volumes to the
pools.
b Define a scratch pool and add all of your volumes to it. NetBackup
moves volumes to the other pools as they are needed.
Barcode overview
When a robotic library has a barcode reader, it scans the media for barcodes and
saves the results. The results associate the slot number and the barcode with the
media in that slot. NetBackup obtains barcode and slot information from the
robotic library.
Barcode advantages
NetBackup functions well whether or not barcodes are used. However, Symantec
suggests that you use media with barcodes in the robots that can read barcodes.
Barcodes offer the following advantages:
■ Automatic media ID assignment. When you add new media to a robot,
NetBackup is able to assign media IDs according to the criteria that you
specify.
■ More accurate tracking of volume location. A robot inventory update can
determine which volumes are in a robot.
■ Increased performance. Not using barcodes can adversely affect
performance for some robots. A robot that reads barcodes performs a scan
each time it moves a tape. The robot stores the correct barcode in memory or
verifies a previously saved barcode. However, if a tape does not have a
barcode, the robot retries the scan multiple times, degrading performance.
Barcode best practices

When you select barcodes for your volumes, consider the following:
■ Barcodes usually appear on the labels that you attach to the outside of tape
volumes.
Barcodes are not generally used on optical disks, and NetBackup does not
support barcodes for optical disk libraries (ODL robots).
■ The maximum barcode length that NetBackup supports depends on the type
of robot.
Barcode overview
■ When you purchase barcode labels for use with NetBackup, always follow
the robotic library vendor’s recommendations. Ensure that the barcodes
have the correct number of characters.
■ Barcodes can represent any combination of alpha and numeric characters,
but different robots support different lengths of barcodes. See the robot
vendor’s documentation to determine the requirements for a specific robot
type.
■ Use barcodes without spaces (at the beginning, at the end, or between any
characters). Otherwise, the robot or NetBackup may not read them correctly.
■ Volumes in an API robot have a real or a logical barcode. This volume
identifier is used as the NetBackup media ID. This volume identifier is the
volume serial number in ACS, TLH, and TLM robots.
■ For API robots, the barcode for a volume must be identical to the NetBackup
media ID.
You can match barcodes to media IDs by getting custom labels in the same
series as your media IDs. For example, to match a set of media IDs from
AA0000 to ZZ9999, get barcode labels in that series.
■ When a robotic library can contain more than one media type, you should
assign specific characters in the barcode to different media types using
media ID generation rules. Also, you should use barcodes to differentiate
between data tapes and cleaning tapes or to differentiate between volume
pools.
Barcode rules
A barcode rule specifies criteria for assigning attributes to new robotic volumes.
NetBackup assigns these attributes using the barcode for the volume that the
robotic library provides and your barcode rules.
In NetBackup, you choose whether to use barcode rules when you set up the
robot inventory update operation. The barcode rules are stored on the EMM
server .
NetBackup actions for barcodes

When a robot inventory update operation uses NetBackup barcode rules and a
new barcode is detected in the robot:
■ NetBackup searches the list of rules (from first to last) for a rule that
matches the new barcode.
■ If a rule matches the barcode tag, NetBackup verifies that the media type in
the rule is compatible with the media type you specified for the update.
Barcode overview
■ If the media types match, NetBackup assigns the attributes in the rule to the
volume. The attributes include the media type, volume pool, maximum
number of mounts (or number of cleanings), and description.
Note: NetBackup does not use barcode rules if a volume already uses a barcode.
Checking barcodes
In the robots that have barcode readers, NetBackup verifies the barcode to
ensure that the robot loads the correct volume. If the barcode on the volume
does not match the barcode in the EMM database, NetBackup:
■ May assign the request a pending status (for media-specific jobs such as a
restore)
■ May use another volume (for backup or duplicate jobs)
■ May fail the job (cold catalog backup jobs)
If a requested volume is not in a robot, a pending request message appears in the
NetBackup Administration Console Device Monitor. The operator must then
find the volume and do one of the following:
■ Check the Device Monitor to find a suitable drive and mount the requested
volume in that drive.
■ Move the volume into the robot, update the volume configuration to reflect
the correct location for the media, and resubmit the request.
If the volume is labeled (tape or optical platter), the automatic volume
recognition daemon reads the label and the drive is assigned to the request. If
the volume is unlabeled and not associated with a robot, the operator manually
assigns the drive to the request.
Example barcode rules

The following table shows some example barcode rules. Rules are sorted first
according to the number of characters in the barcode tag and then by the order
you add them. Two exceptions are the <NONE> and <DEFAULT> rules, which
are always located at the end of the list.
Table 3-14 Example barcode rules
Barcode tag Media type Volume pool Max mounts Description

/ cleanings
0080 8MM b_pool 55 new 008 volumes
DLT DLT d_pool 200 dlt backup

Barcode overview
Table 3-14 Example barcode rules (continued)
Barcode tag Media type Volume pool Max mounts Description

/ cleanings
CLD DLT_CLN None 30 dlt cleaning
CLT 8MM_CLN None 20 8-mm cleaning
TL8 8MM t_pool 0 8-mm backup
TL 8MM None 0 8-mm no pool
<NONE> DEFAULT None 0 no barcode
<DEFAULT> DEFAULT NetBackup 0 other barcodes
Refer to the previous table for example barcode rules for the following
examples. Assume that you select the following media settings (update options)
for the update operation for a new 8-mm volume in a TL8 robot:
Media Type = 8MM
Volume Group = 00_000_TL8
Use Barcode Rules = YES
Volume Pool = DEFAULT
If a new volume in this robotic library has a barcode of TL800001, NetBackup
uses the rule with the barcode tag of TL8 and assigns the following attributes for
the volume:
Media ID = 800001 (last six characters of barcode)
Volume Pool = t_pool
Max Mounts = 0 (no maximum)
If a new volume has a barcode of TL000001, NetBackup uses the rule with the
barcode tag of TL and assigns the following attributes for the volume:
Media ID = 000001 (last six characters of barcode)
Volume Pool = None
Max Mounts = 0 (no maximum)

Changing your hardware configuration
Media ID generation rules
Note: To use media ID generation rules, the robot must support barcodes and the
robot cannot be an API robot. Media ID generation rules are saved in the Media
Manager configuration file (vm.conf).
Using media ID generation rules allows you to override the default media ID
naming method NetBackup uses. The default method uses the last six characters
of the barcode the robot provides to generate the media ID.
For example, two eight-character barcodes are S00006L1 and 000006L1. If you
do not specify any media ID generation rules, NetBackup uses the last six
characters of the barcode to generate its media IDs. In this example, the same
media ID for the two barcodes would be created (0006L1) .
In a rule, you can control how NetBackup creates media IDs by specifying which
characters of a barcode are used in the media ID. You also can specify that
alphanumeric characters are to be inserted into the ID.
You can define multipe rules to accommodate your robots and the barcode
lengths. You can define rules to specific robots and for each barcode format that
has different numbers of characters in the barcode. Multiple rules allow
flexibility for the robots that support multiple media types.

The following are advanced topics for changing an existing NetBackup
configuration:
■ “Replacing devices” on page 206.
■ “Decommissioning a media server” on page 208.
Replacing devices
If you replace an existing device in your configuration, the serial number of the
new device is different than the old device. NetBackup recognizes the change
and updates the EMM database without restarting ltid. NetBackup also
recognizes device firmware upgrades. For devices on NetBackup 5.x hosts, you
must restart ltid before NetBackup recognizes the new device.
In upgrades from NetBackup environments earlier than 6.0, devices retain their
serial numbers. In NetBackup 6.0 and later, a change to a serial number
formatting algorithm may affect a small number of tape drives and robotic
libraries. Those devices may be configured as unserialized or configured with a
different serial number. Therefore, NetBackup integrity checks that query the
device serial number and compare it with the serial number in the database may
fail. If so, a device may be unusable (such as the tape drive may be downed).
Integrity checks occur when ltid performs automatic path correction or when
the run-time Plug-n-Play code (Windows only) performs serial number checks.
In such cases:
■ Update the serial number or reconfigure the device so that the new serial
number to be stored in the EMM database. For procedures, see
■ “To swap a serialized drive or to update drive firmware on a single
host” on page 207
■ For a shared drive, “To swap a shared serialized drive or to update drive
firmware on a shared drive” on page 207
■ Disable runtime serial number checks by using the
AUTO_PATH_CORRECTION vm.conf option.
To swap a serialized drive or to update drive firmware on a single host

1 Down the drive. In the Device Monitor, select the drive to swap or update.
From the Actions menu, select Down Drive. Alternatively, down the drive
using the vmoprcmd command with the -downbyname drive_name
option.
2 Replace the drive or physically update the firmware for the drive. If you
replace the drive, specify the same SCSI ID for the new drive as the old drive.
3 Up the drive. In the Device Monitor, select the new drive. From the Actions
menu, select Up Drive.
If you replace a drive with a drive of a different type or replace a serialized
drive with an unserialized drive, configure the new drive by using the
NetBackup Device Configuration wizard. The drive must first be recognized
by the operating system of each server.
Device configuration may require remapping, rediscovery, and possibly a
reboot of the operating system. For more information, see the NetBackup
Device Configuration Guide.
To swap a shared serialized drive or to update drive firmware on a shared

drive
1 Down the drive. In the Device Monitor, select the drive to swap or update.
From the Actions menu, select Down Drive.
2 Replace the drive or physically update the firmware for the drive. If you
replace the drive, specify the same SCSI ID for the new drive as the old drive.
3 To produce a list of new and missing hardware, run tpautoconf
-report_disc on one of the reconfigured servers. This command scans for
new hardware and produce a report that shows the new and the replaced
hardware.
4 Ensure that all servers that share the new hardware are up and that all
NetBackup services are active.
5 Run tpautoconf with the -replace_drive drive_name -path
path_name options or -replace_robot robot_number -path robot_path
options.
The tpautoconf command reads the serial number from the new
hardware device and then updates the EMM database.
6 If the new device is an unserialized drive, run the device configuration
wizard on all servers that share the drive.
If the new device is a robot, run the device configuration wizard on the
server that is the robot control host.
7 Up the drive. In the Device Monitor, select the new drive. From the Actions
menu, select Up Drive.
Decommissioning a media server

You must perform several steps to decommission a media server and remove it
from a NetBackup configuration. If any devices attached to the media server
contain NetBackup media, you must move that media to a new NetBackup media
server. Alternatively, if the media is no longer usable or valid, you must delete it
from the NetBackup configuration.
Note: If you use NetBackup Vault and plan to decomission a media server,
contact Symantec Consulting for help with this task.
Use the following procedure to decommission a server (the old_server) and move
its media to a new media server (the new_server). If you do not do the following
and a subsequent restore requires media that is associated with the old media
server, you must import the media. Importing media consumes more time than
performing the following procedure.
To decommission a media server

1 Run the bpmedialist command to determine which tapes on the
old_server contain NetBackup images that have not expired. The -l option
produces one line of output per tape.
bpmedialist -mlist -l -h old_server

2 Select another server or the master server (new_server) to manage the tapes
from the old_server.
Run the bpmedia command for each tape that has active images as
identified in step 1. The command replaces the old_server with the
new_server in the EMM database and updates the images database on the
master server.
bpmedia -movedb -ev media_ID -oldserver old_server
-newserver new_server
3 Add the following command to the end of the bp.conf file on the master
server. The command allows restores from the media that are associated
with the old_server to occur from a new_server.
FORCE_RESTORE_MEDIA_SERVER = old_server new_server
4 Use the NetBackup Administration Console to move the tapes that are in the
robots that are attached to the old_server to non-robotic status
(stand-alone). Select each robot that is attached to the old_server, highlight
all of the tapes, and move them to stand-alone.
5 Use the NetBackup Administration Console to delete the drives and then the
robots from the old_server.
6 Use the NetBackup Administration Console to delete all storage units that
use the robots that are associated with the old_server.
7 If any robots from the old_server are reused on other media servers, do the
following:
a Power down the affected servers, disconnect the robots from the old
servers, and then connect them to the new media servers. Verify that
the operating systems on the new media servers recognize the robots.
b Use the NetBackup Administration Console to add the robots and drives
to those media servers. You can use the NetBackup Device
Configuration wizard.
c Use the NetBackup Administration Console to create the appropriate
NetBackup storage units.
d Use the NetBackup Administration Console to inventory the robots that
are attached to the new_server. The inventory updates the location of all
tapes in these robots.
8 Modify any policies that explicitly specified any of the storage units on the
old_server. These policies must be changed to point to any other defined
storage units in the NetBackup configuration or to Any Available, as
appropriate.
How NetBackup selects drives
9 Remove all reference to the old_server in the bp.conf files (UNIX only) and
vm.conf files on the NetBackup master server and all NetBackup media
servers.
10 Use the nbemmcmd command to remove the host aliases and host names
that reference the old_server. Run nbemmcmd -listhosts to verify that all
references have been removed.
11 Update the server list on all clients to no longer refer to the old_server.
Restart the NetBackup daemons (or services) on any system that was
updated.
How NetBackup selects drives

NetBackup stores media information and device configuration and status
information in the EMM database. When a robotic mount request is issued, the
NetBackup Resource Broker (nbrb) queries the EMM database for the media ID
of the volume requested. If the volume is in the EMM database, the media
request is matched with a compatible drive in the robot. The mount request is
forwarded to the appropriate robotic daemon (UNIX) or process (Windows)
based on the location of the media. Location is the robotic library and the
storage slot number, if applicable.
A drive must meet the following criteria to be selected for the mount request.
■ The drive is configured.
■ The drive is in the robotic library that contains the media.
■ The drive allows the requested media density.
The EMM server (nbemm) manages the drives and requests for locally-attached
or shared drives in the EMM domain by doing the following:
■ Determines which of the drives are currently available. A drive is available if
it is:
■ Configured as UP
■ Not assigned.
■ Compatible with the media type
■ Not reserved by another host (NetBackup Enterprise Server only).
■ Picks an available drive that was used least recently. NetBackup selects the
robotic-based drives over stand-alone drives unless the corrrect media
already is loaded in a stand-alone drive.
The first drive in the drive configuration is used first, then the second drive, and
so on. You can see the drive order in the configuration by using the tpconfig
-d command.
How NetBackup reserves drives
The following applies only to NetBackup Enterprise Server.

If some of the drives are shared drives, NetBackup chooses a nonshared drive
first (if one is available). NetBackup chooses a shared drive first so the shared
drives can be used on other hosts that share the drives. Shared drives require
the Shared Storage Option.

In multiple-initiator (multiple host bus adapter) environments, device-level
access protection is required to avoid unintended sharing of tape devices and
possible data loss problems. (Shared Storage Option is a multiple-initiator
environment.) Access protection on a tape drive prevents an HBA that is not the
reservation owner from issuing commands to control the drive. SCSI access
protection operates at the SCSI target level and depends on correct operation of
the fibre-to-SCSI bridge or the native fibre device hardware.
The only commonly available technique for this purpose is SPC-2 SCSI reserve
and release functionality. All tape drive vendors support the SPC-2 SCSI reserve
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, a drive reset usually is required
because the reservation owner is inoperative.)
■ 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.
NetBackup lets you configure either SCSI persistent reserve or SPC-2 SCSI
reserve. The following are the protection options:
■ SCSI persistent reserve. This option provides SCSI persistent reserve
protection for SCSI devices. The devices must conform to the SCSI Primary
Commands - 3 (SPC-3) standard.
■ SPC-2 SCSI reserve. (The default option.) This option provides SPC-2 SCSI
reserve protection for SCSI devices. The devices must conform to the reserve
and release management method in the SCSI Primary Commands - 2
standard.
■ No protection. Other HBAs can send the commands that may cause a loss of
data to the tape drives.
You can configure access protection for each NetBackup media server. The
protection setting configures tape drive access protection for all tape drive
paths from the media server on which the setting is configured. You can
override the media server setting for any drive path.
SCSI reservations provide protection for NetBackup Shared Storage Option
environments or any other multiple-initiator environment in which drives are
shared.
SCSI access protection is used on tape drives only.
SCSI persistent reserve process

The NetBackup process that reads from or writes to the media in a drive (bptm)
issues SCSI persistent reserve commands to do the following:
■ Register with the tape drive’s device server (the server is a logical unit
within a drive that processes SCSI tasks)
■ Request an exclusive access reservation
If the tape drive’s device server grants the reservation, the NetBackup process
has exclusive use of the device. The reservation prevents other host bus
adapters (HBAs) from issuing any commands that can cause data loss.
If the reservation fails, NetBackup fails the job.
When the NetBackup process is finished with the drive, NetBackup unloads the
drive and sends a persistent reserve clear command to the drive. The command
removes both the reservation and the registration.
SCSI persistent reserve also provides device status detection, which NetBackup
uses to resolve reservation conflicts within NetBackup.
The reservation does not prevent other applications on the host that has the
reservation from using the same device and from causing data loss. For
example, if a user on the same host issues a UNIX mt command, the mt
command may take control of the drive.
Also, other HBAs can clear or release an SCSI persistent reservation. Therefore,
an application can clear another HBAs reservation (although it should not do
so).
SCSI persistent reserve commands

When a device receives an exclusive access type SCSI persistent reservation
command, it does not process commands from any other HBA until the HBA that
owns the SCSI persistent reservation clears the reservation. If an application
sends a command to a reserved device, the device fails the command by
returning a status of RESERVATION CONFLICT. The only exceptions to this
action are several commands that cannot interfere with the reservation, such as
Inquiry or Request Sense.
A device stays reserved until one of the following occurs on the device:
■ Released by the HBA that reserved it.
■ Power cycled (usually).
■ Preempted by an SCSI persistent reserve command.
SCSI persistent reserve conflicts

NetBackup uses unique reservation keys. Therefore, NetBackup attempts to
resolve conflicts with other NetBackup reservations. If a conflict exists,
NetBackup sends SCSI commands to unload the drive. Based on the drive status,
NetBackup tries to unload the drive again by using additional information to
release or preempt the persistent reservation.
In cluster environments after a failover event, NetBackup on the active cluster
node detects the persistent reservation and clears the reservation. NetBackup
regains use of the drive without power-cycling the drive.
If NetBackup does not own the persistent reservation, NetBackup reports a
pending status in the Device Monitor. The reservation owner must clear the
reservation before NetBackup can use the drive. For example, NetBackup does
not clear a NetApp persistent reservation.
SPC-2 SCSI reserve process

The NetBackup process issues an SPC-2 SCSI reserve command to the tape drive
that contains the media. (The process can be bptm, bprecover, or
bpbackupdb.) If the device is not reserved, NetBackup acquires a reservation.
The drive does not process commands from any other host bus adapters (HBAs)
until NetBackup releases the reservation or the reservation is broken. If the
reservation fails, NetBackup fails the job.
The reservation does not prevent other applications on the host that has the
reservation from using the same device and from causing data loss. For
example, if a user on the same host issues a UNIX mt command, the mt
command may take control of the drive.
After the NetBackup process has finished with the media, it issues an SPC-2
SCSI command to release the reservation during the unmount operation. The
release frees the device for access by another HBA.
SCSI reserve does not provide a method to determine if a device is reserved. Only
the reservation owner (the host bus adapter) can release the reservation.
However, these limitations do not interfere with NetBackup operations in most
environments.
SPC-2 SCSI reserve commands

When a device receives an SCSI reserve command, it does not process
commands from any other HBA until the HBA that owns the reservation issues
the release command. If an application sends a command to a reserved device,
the device fails the command by returning a status of RESERVATION
CONFLICT. The only exceptions to this action are several commands that cannot
interfere with the reservation, such as Inquiry or Request Sense.
A device stays reserved until one of the following occurs on the device:
■ Released by the HBA that reserved it.
■ Released by a TARGET or a LOGICAL UNIT RESET. These resets are protocol
dependent and differ between parallel SCSI and FCP (SCSI on fibre channel).
These resets may be issued from any HBA.
■ Released by fibre channel LOGO, PLOGO, PRLI, PRLO, or TPRLO action or
failed discovery (link actions).
■ Power cycled.
A negative consequence of SPC-2 SCSI reserve occurs if the HBA that owns the
reservation fails. A device that an HBA reserves stays reserved until the
reservation is removed or broken. Only the original HBA can remove the
reservation, which means the system must be available. If the HBA that owns
the reservation fails, it cannot remove the reservation. Therefore, the
reservation must be broken.
To break a reservation, the device must be reset by any of the following:
■ SCSI reset
■ Bus device reset
■ LUN device reset
■ Power cycle
■ Fibre channel link actions may break reservations.
SPC-2 SCSI reserve commands are mandatory for all SCSI-2 and SCSI-3 devices.
See the SCSI 2 standard for a detailed description of SCSI reserve command
operation and behavior.

SCSI reservation conflicts

The NetBackup Automatic Volume Recognition process (avrd) manages access
to tape devices. A properly configured NetBackup environment and properly
configured tape devices should not receive a reservation conflict message from a
tape drive. When avrd starts, it issues an SPC-2 SCSI release to all configured,
nondisabled tape drive paths that are currently in the Up state. The command
releases all devices that were SPC-2 reserved at the time of a system reboot or
crash. The SCSI release command returns tape devices to general availability
after a system crash.
If avrd gets a reservation conflict message, avrd changes the status of the
device to PEND and writes the following message in the system log:
Reservation Conflict status from DRIVENAME (device NUMBER)
Also, the NetBackup Administration Console Device Monitor or the output from
the vmoprcmd command shows PEND in the Control column.
If a conflict occurs, a reservation problem may exist. If the HBA that reserves
the drive is unavailable (for example, due to a system crash or hardware failure),
it cannot release the reservation. NetBackup cannot release or break an SPC-2
SCSI reservation automatically. You must force a release or break the
reservation to make the drive available, even for a failover server in a cluster
environment.
When the conflict is resolved, the following message is written to the log:
Reservation Conflict status cleared from DRIVENAME (device NUMBER)
Forcing a release
To force a release of an unavailable HBA’s SPC-2 reservation, you can use the
following NetBackup vmoprcmd command and option:
vmoprcmd -crawlreleasebyname drive_name
This option requests that all hosts that are registered to use the drive issue
SPC-2 SCSI release commands to the drive.
Issue the vmoprcmd command on the host that is the device allocator (DA host).
Alternatively, use the -h option of the command to specify the DA host. The DA
host is also the EMM server.
Caution: You can use this command after a PEND status has been displayed in
the NetBackup Administration Console Device Monitor. However, do not issue
this command during backups.
For more information about using the vmoprcmd command, see NetBackup
Commands for UNIX and Linux or NetBackup Commands for Windows.
Breaking a reservation
If you cannot release an SPC-2 SCSI reservation, you can try to use an operating
system command that forces a device reset. A device reset breaks a reservation.
The procedure depends on the operating system type.
Caution: The reset operation may reset other devices in your configuration. Loss
of data is also possible. You should first try alternate methods to break the
reservation on a device (using switch and bridge hardware).
Lastly, if the following operating system commands cannot break the

reservation, you can power-cycle the drive. A power cycle breaks SPC-2 SCSI
drive reservations (and usually breaks SCSI persistent drive reservations).
To break an SPC-2 reservation on Solaris

1 Issue mt -f drive_path_name forcereserve.
2 Issue mt -f drive_path_name release.
See the mt(1) man page for more information.
To break an SPC-2 reservation on HP-UX

◆ Issue st -f drive_path_name -r.
See the st(1m) man page for more information.
To break an SPC-2 reservation on AIX

◆ Issue tctl -f drive_path_name reset.
See the tctl man page (in the IBM AIX Commands Reference) for more
information.
SCSI reserve requirements and limitations

The following are the requirements to use SCSI persistent reserve or SPC-2 SCSI
reserve:
■ There must be passthru driver access to all shared drives. The passthru
driver must be installed and all required paths must be created.
For information about how to configure and use the passthru driver for
UNIX operating systems, see the NetBackup Device Configuration Guide .
■ You must configure the operating systems on the NetBackup media servers
so they allow NetBackup to control SCSI persistent reserve or SPC-2 SCSI
reserve.
■ On HP-UX systems, you must disable the operating system's use of SPC-2
SCSI reserve. For instruction, see “Enabling SPC-2 SCSI reserve” in the
“Hewlett-Packard HP-UX” chapter of the NetBackup Device Configuration
Guides.
■ Depending on your tape drives, you may have to disable the operating
system’s use of SPC-2 SCSI reserve. AIX and Solaris may require such a
change. For more information, see the appropriate operating system
chapter of the NetBackup Device Configuration Guide.
The NetBackup implementation of SCSI persistent reserve and SPC-2 reserve
has the following limitations:
■ SCSI persistent reserve and SPC-2 reserve do not apply to NDMP drives. The
NDMP filer is responsible for providing exclusive device access.
■ Third-party copy configurations must be configured correctly. To retain
reservation of a tape device during a third-party copy backup, you must
configure the NetBackup mover.conf file. For procedures, see the
NetBackup Snapshot Client Administrator's Guide. Do not use SCSI
persistent reserve on the drive paths that are used for third-party copy
backups.
■ With SPC-2 SCSI reserve, devices may remain reserved after a failover in
cluster environments or multipath environments with failover capability.
You cannot use SPC-2 SCSI reserve if the following are true: the failover
does not break the device reservations and those devices that were in use
during the failover must be available without manual intervention. You can
use SCSI persistent reserve.
■ If a drive path changes, backups and restores fail. Therefore, jobs fail in
cluster environments or any multipath environments that share paths
dynamically. If you cannot disable dynamic path sharing, you cannot use
SPC-2 SCSI reserve or SCSI persistent reserve in NetBackup. HP Tru64 is a
system that uses dynamic path sharing.
SCSI reservation logging

The bptm process logs SCSI reservation-related commands. You should examine
the bptm log on all NetBackup media servers to ensure that the SCSI operations
are logged. SCSI reservation commands are labelled SCSI PERSISTENT
RESERVE or SCSI RESERVE in the log.
In addition, information about the SCSI persistent reservations that are broken
are also written to the NetBackup Problems report.
Server operating system limitations

This topic applies to Tru64 and Windows servers.
Tru64 and Windows operating systems cannot distinguish between a reserved
device and a busy device. Therefore, PEND appears in the Device Monitor if
another application controls the tape drive. NetBackup cannot share tape
devices with other applications. If you use other applications, you should use the
NetBackup tpreq command or Down the drive before you use the drive.
These operating systems also may report PEND if the drive reports Busy when a
volume is unmounted. You can use the AVRD_PEND_DELAY entry in the
vm.conf configuration file to filter out these extraneous reports.
Checking for data loss

To detect data loss, the bptm process reads the tape position and then verifies
the actual position against the expected position. If the actual position is less
than the expected position at the end of the backup process, the following
occurs:
■ The tape is frozen.
■ The backup fails.
■ The following error message entry is written to the bptm log:
FREEZING media id xxxxxx, External event caused rewind during
write, all data on media is lost
Possible data loss causes

If tape drive access protection is not enabled on your NetBackup media servers,
the following may cause data loss: configuration errors, incorrect paths,
multiple master servers, incorrect Shared Storage Option configurations, and
third-party or operating system utilities.
If access protection is enabled on all NetBackup media servers, the following
may cause data loss: any third-party or operating system utilities that run on
the server that runs the NetBackup backup job.
Unfortunately, data loss cannot be prevented only recognized after the fact.
NetBackup does not remove catalog information about the backup sessions that
were lost. You must use the bpexpdate command to expire the images for the
lost backup sessions.
Checking for tape and driver configuration errors

To detect data loss, the bptm process reads the tape position and then verifies
the actual position against the expected position. If a configuration problem
How NetBackup selects media
causes the actual position to be greater than the expected position at the end of
the backup process, the following occurs:
■ The tape is frozen.
■ The backup fails.
■ The following error message entry is placed in the bptm log:
FREEZING media id xxxxxx, too many data blocks written, check
tape/driver block size configuration
The backup data may be usable. If so, you can import the image using the
NetBackup bpimport command so the data is available for restores.
Common configuration problems

You must identify and fix the source of the configuration problem that causes
data loss. The most common configuration error is a failure to configure the
driver for variable length blocks.
A less common error may be in the tape driver's configuration data, such as in
the /kernel/drv/st.conf file on a Solaris system.
For information about tape driver configuration, see the NetBackup Device
Configuration Guide.
Configuring SCSI reserve

The SCSI reserve protection setting configures tape drive access protection for
all tape drives from the media server on which the setting is configured. You can
configure the protection for each media server, and you can override the global
setting for any drive path.
To configure SCSI reserve protection on a media server: use the NetBackup
Administration Console to set the media server host property Enable SCSI
Reserve on the Media tab.
To override the media server protection setting: use the NetBackup
Administration Console to set the drive path property Override SCSI reserve
settings when you add a drive or change a drive’s properties.

How NetBackup selects media depends on whether the media is in a robot or a
stand-alone drive.
Selecting media in robots

When NetBackup receives a request for a volume, it searches the EMM database
for the media ID. A request for a volume includes the media ID, device density,
and the file name that is used to link to the device that is assigned. The external
media ID should correspond to the NetBackup media ID. NetBackup selects a
volume in a robot in the following order:
■ NetBackup searches the media catalog for a volume that is already mounted
in a drive and meets the following criteria:
■ Configured to contain backups at the retention level that the backup
schedule requires. However, if the NetBackup Media host property
Allow multiple retentions per media is specified for the server,
NetBackup does not search by retention level.
■ In the volume pool that is required by the backup.
■ Not in a FULL, FROZEN, IMPORTED, or SUSPENDED state.
■ Of the same density that is required by the requested backup andin the
robot that is requested by the backup.
■ Not currently in use by another backup or a restore.
■ Not written in a protected format. NetBackup detects tape format after
the volume is mounted. If the volume is in a protected format,
NetBackup unmounts the volume and resumes the search.
If a suitable volume is found, NetBackup uses it.
■ If NetBackup cannot find a mounted volume that satisfies all of the previous
conditions, it checks the media catalog for any volume that is suitable.
■ If a suitable volume is in a robot, NetBackup issues the commands that
move the volume to a drive, position the heads to the beginning of the
volume, and assign it to the request. No manual intervention is
required.
■ If a suitable volume is not in a robot but is in a stand-alone drive,
NetBackup automatically mounts and assigns it. No manual
intervention is required.
■ If a suitable volume is not in a robot or a stand-alone drive, NetBackup
does one of the following:
■ Pends a mount request if the request is media-specific (restore,
import, or tpreq).
■ Attempts to to use another volume (for backup jobs where any
other media can be used).
■ If the media catalog does not have a suitable volume or if a suitable volume
is at end of media (EOM), a new volume is assigned. NetBackup may assign a
new volume even if a volume is not full (because NetBackup received an
EOM message from the drive). The new volume must meet all of the
following criteria:
■ Is the correct media type.
■ Is for the correct robot type (if applicable).
■ Is located in the requested robotic peripheral (if applicable).
■ Resides on the requested host.
■ Is in the correct volume pool.
■ Is not currently assigned (not already allocated to NetBackup).
■ Is not expired (if an expiration date is defined in NetBackup).
■ Has not exceeded the maximum number of mounts allowed.
■ If more than one volume qualifies, NetBackup chooses the volume that was
least recently used. NetBackup then adds it to the media catalog and assigns
it the specified retention level.
■ If there are no unassigned volumes of the requested type, the backup
terminates with an error message that no media was available.
Spanning media
After an end of media (EOM) is reached, automatic media selection depends on
whether NetBackup is configured to allow backups to span media, as follows:
■ NetBackup spans media if the NetBackup Media host property Allow
backups to span media is specified for the server. In this case, NetBackup
uses another volume to start the next fragment and the resulting backup is
composed of fragments on different volumes.
■ NetBackup does not span media if Allow backups to span media is not
specified. In this case, the backup terminates abnormally and the operation
is retried according to the NetBackup Global Attributes host property,
Schedule backup attempts.
Selecting media in stand-alone drives

The following subsections explain media selection and other aspects of
stand-alone drive operations.
Media selection using stand-alone drive extensions

With NetBackup stand-alone drive extensions, NetBackup tries to use any
labeled or any unlabeled media that is in a stand-alone drive. This capability is
enabled by default during installation. The media selection process is as follows:
■ If a backup is requested and an appropriate stand-alone drive does not

contain a volume, NetBackup selects a volume as explained in “How
NetBackup selects media” on page 219.
The Device Monitor shows the mount request, and an operator must
manually insert the volume and assign it to a drive.
■ If an appropriate drive contains a volume, NetBackup tries to select and use
that volume.
A volume that has been used previously for backups must meet the following
criteria:
■ Not be FULL, FROZEN, or SUSPENDED.
■ Contain backups at the retention level and be in the same volume pool as
the backup that requires a volume. However, if the NetBackup Media host
property Allow multiple retentions per media is specified for the server,
NetBackup does not require a specific retention level.
NetBackup uses media that was not used previously. If the media is unlabeled,
the following actions occur:
■ NetBackup labels the media.
■ NetBackup adds a media ID to the volume configuration, if necessary. If a
media ID is added, the NetBackup Media ID prefix (non-robotic) is used as
the first characters of the media ID.
■ If a media ID prefix is not specified, the default prefix is the letter A. For
example, A00000.
■ NetBackup adds the requested volume pool to the volume configuration (if
the backup policy specifies a volume pool).
If the unused media is not labeled, you can label it by using the bplabel
command. You can specify the -u parameter ito force assignment of a specific
drive index, which eliminates the need to assign the drive manually.
Disabling stand-alone drive extensions

You can disable the stand-alone drive extensions by clearing the NetBackup
media server host property, Enable standalone drive extensions. If you clear
this property, NetBackup uses the same method to select media for stand-alone
drives as it uses for robotic drives.
Spanning media
Media selection after an end of media (EOM) condition depends on whether
NetBackup is configured to allow backups to span media, as follows:
■ NetBackup spans media if the media server host property, Allow backups to
span media, is specified for the server. NetBackup selects another volume to
Media formats
begin the next fragment, and the resulting backup has data fragments on
more than one volume.
■ After an EOM condition, NetBackup attempts to use an unassigned
volume rather than one that already has images on it. NetBackup
checks the EMM database for a volume that is the correct media type,
in the correct volume pool, and so on.
■ If a suitable unassigned volume is unavailable, NetBackup selects a
volume.
■ NetBackup does not span media if Allow backups to span media is not
specified. The backup terminates abnormally when the end of media is
reached. The operation is rescheduled according to the master server host
property Schedule backup attempts.
When NetBackup spans media and an EOM is encountered on a stand-alone
drive, you can direct NetBackup to wait until a volume is loaded in a compatible
stand-alone drive. NetBackup then does not search for other media or generate a
pending mount request. The wait period is helpful when a gravity feed tape
stacker takes a long time to load the next media in the drive. (A gravity feed tape
stacker is not controlled by software.)
To direct NetBackup to wait, specify the Media request delay media server host
property. This property specifies the number of seconds NetBackup waits to use
a volume that is loaded in a compatible drive before looking for another drive.
NetBackup also waits to generate a pending mount request during tape span
operations. The Media request delay property is effective only when
stand-alone drive extensions are enabled.
Keeping stand-alone drives in the ready state

To leave stand-alone drives in a ready condition after a backup or restore
completes, use the nbemmcmd command to enable the
-do_not_eject_standalone option. NetBackup does not eject the tape after
an operation completes. The media is still ejected if EOM is reached or an error
is encountered. Also, the media is ejected if the drive needs to be used with
another media or the media needs to be used with another drive.
One standalone drive may be ready and contain suitable media.
See the NetBackup Commands for UNIX and Linux for detailed information on
the nbemmcmd command.
Media formats
NetBackup writes media in a format that allows the position to be verified before
appending new backups. The format for tape and optical media differs slightly
because of characteristics of the media.
Media formats
The following symbols are used in the media format descriptions in the
following subsections.
Symbol Description
MH Media Header (1024 bytes).
* Tape mark.
BH Backup Header (1024 bytes).
BH1 ... BHn Backup Headers (1024 bytes). One for each job that is part of the set
of jobs being multiplexed
Image Data from the backup.
EH Empty Backup Header, which is used for position validation.
Standard tape format

For all tape media except quarter-inch cartridge (QIC) and WORM, the format
for the backups that are not multiplexed is as follows:
MH * BH Image * BH Image * BH Image * EH *
When you add a new backup image, the tape is positioned to the EH and the
position is verified. The EH is overwritten by a BH and the backup proceeds.
When complete, a new EH is written for future positioning validation.
When NetBackup encounters the end of media during a write, it terminates the
tape with two tape marks and does not write an EH.
QIC/WORM tape format

This format is used for quarter-inch cartridge (QIC) and WORM media. Unlike
the standard tape format, NetBackup does not write empty backup headers (EH).
The format is as follows:
MH * BH Image * BH Image * BH Image *
To append backup images to QIC media, NetBackup positions to the end of data
(EOD) and then starts the next backup.
Optical media format

For optical media, the format is as follows:
MH BH Image EH BH Image EH BH Image EH
Optical disk media have no tape marks to delimit backups. The data on an
optical disk is recorded in successive sectors. Because optical disks can seek to a
random position, find operations and verify a position operations are a fast.
Media formats
Fragmented backups
For fragmented backups, the media format is similar to the standard tape
format. The difference is that NetBackup breaks the backup image into
fragments of the size that you specify when you configure the storage unit. The
following is an example:
MH * BH Image (frag 1)* BH Image (frag 2)* BH Image (frag n) * EH *
Fragmentation is intended primarily for storing large backup images on a disk
type storage unit. The following are some benefits of image fragmentation:
■ For multiplexed backups, faster restores because NetBackup can advance to
the specific fragment before starting its search for a file.
■ Faster restores from any backup images that NetBackup Storage Migrator
migrated. For example, if a 500-MB backup is stored in 100-MB fragments,
Storage Migrator has to retrieve only the fragment that has the files. Storage
Migrator does not have to retrieve the entire 500 MBs.
Note: If an error occurs in a backup, the entire backup is discarded and the
backup restarts from the beginning. It does not restart from the fragment where
the error occurred. Exception: checkpoint and restart backups resume from the
last checkpoint fragment.
Multiplexing format
The tape format for multiplexed backups is as follows:
MH * BH1 ... BHn Image...
By default, the data image is in 64-kilobyte blocks. Each block also contains 512
bytes that are reserved for multiplexing control information and to identify the
backup to which the block corresponds.
When a job ends or a new job is added to the multiplexing set, NetBackup writes
a tape mark and starts multiplexing the revised set of jobs. The following is an
example:
MH * BH1 BH2 BH3 Image* BH2 BH3 Image* BH2 BH3 BH4 Image. .
Spanning tapes
By default, NetBackup spans a backup image to another tape if it encounters the
end of media during a backup. The format is the same as described for
fragmented backups. The first fragment on the next tape begins with the buffer
of data where the end of media occurred.
Media Manager commands
The following is the first tape format (NetBackup does not write an EH, and
terminates the tape with two tape marks):
MH * ... *BHn Image (frag 1) * *
The following is the second tape format:
MH * BHn Image (frag2)* ... * EH *

See the NetBackup Commands for UNIX and Linux for detailed information
about most of the commands shown in the following tables.
The jnbSA command is located in the directory
/usr/openv/netbackup/bin. The other commands listed are located in
/usr/openv/volmgr/bin.
Table 3-15 Starting daemons
Command Description Note
acsd The Automated Cartridge System robotic daemon. Applies only to

This daemon is started by ltid. NetBackup
Enterprise
Server.
avrd The Automatic Volume Recognition daemon. This

daemon is started by ltid.
ltid Starts the Media Manager device daemon. Starting

ltid also starts the robotic, robotic control, and
Media Manager volume and avrd daemons.
odld The Optical Disk Library robotic daemon. This daemon

is started by ltid.
tl4d The Tape Library 4MM robotic daemon. This daemon

is started by ltid.
tl8cd Starts the Tape Library 8MM robotic-control daemon.

This daemon is started by ltid.
tl8d The Tape Library 8MM robotic daemon. This daemon

is started by ltid.
tldcd Starts the Tape Library DLT robotic-control daemon.

This daemon is started by ltid.
Table 3-15 Starting daemons (continued)
tldd The Tape Library DLT robotic daemon. This daemon is

started by ltid.
tlhcd Starts the Tape Library Half-inch robotic-control Applies only to

daemon. This daemon is started by ltid. NetBackup
Enterprise
Server.
tlhd The Tape Library Half-inch robotic daemon. This Applies only to
daemon is started by ltid. NetBackup
Enterprise
Server.
tlmd The Tape Library Multimedia daemon. This daemon is Applies only to
started by ltid. NetBackup
Enterprise
Server.
vmd The Media Manager volume daemon. This daemon is

started by ltid.
vmscd The NetBackup Status Collection daemon. vmscd is

started by nbemm on the same host as the EMM server
if one or more NetBackup 5.x servers are present in
the configuration.
Table 3-16 Stopping daemons
kill pid Stops the process for the daemon with the specified pid
(process id).
This is a system command with a path of
/usr/bin/kill or /bin/kill.
stopltid Stops the device, robotic, and robotic-control daemons.
tldcd -t Stops the Tape Library DLT robotic-control daemon.
tl8cd -t Stops the Tape Library 8MM robotic-control daemon.
tlhcd -t Stops the Tape Library Half-inch robotic-control Applies only to

daemon. NetBackup
Enterprise
Server.
Device discovery overview

NetBackup discovers devices and configures them automatically on all
supported operating system server platforms (except NetWare servers) and for
supported peripherals.
Device discovery is an exploratory method used to determine which peripheral
devices a host can detect. Detection depends on physical attachment (SCSI,
Fibre, and so on), device state (on and responding or off and not responding),
and host-based system device-layer configuration.
Discovery sends SCSI commands through operating system device files (on
UNIX) or APIs (on Windows) that support SCSI pass through. A pass-through
path to a device must exist; otherwise, the device is not discovered. For
information about configuring the devices in your operating systems, see the
NetBackup Device Configuration Guide.
The goal of device discovery is to provide information to enable fully or partially
automatic configuration of peripherals for use with NetBackup. Device
discovery provides data that correlates the devices that are interconnected
across multiple hosts or multiple host bus adapters on the same host.
Device serialization
Device serialization is a firmware feature that allows device identification and
configuration. A unique serial number identifies a device.
NetBackup determines device relationships by comparing serial numbers from
multiple sources that refer to the same device. If both a robotic library and a
drive fully support serialization, NetBackup can determine the drive's position
(or address) in the robotic library.
Most robots and drives support device serialization. If a device supports
serialization, the following actions occur when the Device Configuration Wizard
queries the devices.
■ Each robot and each drive returns a unique serial number.
■ For any robots in the configuration, the wizard issues an additional
command. The robot returns the number of drives and the serial number for
each of the drives in the robot. The wizard uses the information to
determine the correct drive number for each drive in the robot.
NetBackup uses the information to construct your configuration.
If a device does not support serialization, ask the vendor for the new firmware
that returns serial numbers. Even with the proper firmware, some devices
require the vendor to perform another action to enable serialization for the
device.
If you know that your devices do not support serialization, make sure that you
follow the maximum configuration limits that they allow.
The greater the number of drives and robots in your configuration that do not
support serialization, the greater the chance of configuration problems using
the Device Configuration Wizard.
Devices that can be discovered

NetBackup can discovery the following types of devices:
■ SCSI-based robotic libraries (such as changers, autoloaders, and stackers).
■ SCSI-based tape drives.
■ Native parallel SCSI, Fibre Channel Protocol (FCP) and FC-AL (loop)
connections.
■ SCSI over IP (reported).
■ ACS, TLM, and TLH robots.
■ NDMP devices that run NDMP version 3 or later.
Device discovery in NetBackup

NetBackup is based on a static configuration of devices. These configurations
are persistent for robotic libraries and tape or optical drives in the NetBackup
Enterprise Media Manager (EMM) database. The EMM database contains the
primary attribute information that the following NetBackup components need
to use devices:
■ The NetBackup Administration Console used on the master server
■ Device configuration wizards that are used on the master server
■ The tpconfig command that is used locally on each media server
■ An internal API
The EMM database also contains the discovered device attributes that are
required for device correlation and for validation of consistency in the
configuration. The EMM database ensures consistency between drives, robotic
libraries, storage units, media, and volume pools across multiple servers. The
EMM server contains information for all media servers that share devices in a
multiple server configuration.
The NetBackup scheduling components use the EMM database information to

select the server, drive path, and media for jobs. When the device manager ltid
starts up, it reads device information from the EMM database into a shared
memory segment. Components on the same host communicate by using shared
memory IPC or socket protocols. Socket protocols are used between components
across multiple hosts. Command line interfaces are available to obtain run-time
(shared memory) information and static device configuration information.
Device discovery in the Device Configuration Wizard

The NetBackup Device Configuration Wizard uses device discovery. For a list of
hosts to be discovered, the wizard issues device discovery queries to all the hosts
and correlates the data returned. You can drag and drop devices between
specific addresses in a robotic library and the group of stand-alone (non-robotic)
drives.
If the devices are fully serialized, the wizard configures it; you do not have to
move devices. The wizard changes the device configuration as needed on all
hosts on which device discovery was requested. ltid is stopped and restarted to
activate the latest device configuration.
You can use the Device Configuration wizard after initial configuration. If the
device configuration changes or if it needs to be verified, you can use the Device
Configuration wizard again. However, ltid cannot be stopped and restarted
while NetBackup activity is in progress. Therefore, ensure that no jobs are active
when you start the Device Configuration wizard.
NetBackup can be configured to run an automated form of device discovery
during ltid startup (which is the default behavior for Windows). Automated
discovery detects differences between the actual device configuration and the
device configuration that is defined in the EMM database. NetBackup then can
reconcile those differences.
Device discovery and shared tape drives

NetBackup polls locally-attached non-shared tape drives on the hosts where
they are configured when they are in the UP state and are not in use. For shared
tape drives, only the scan host polls drives until a mount request is received
from NetBackup. During a mount request, NetBackup uses the host that
requests the mount to poll the shared drive. (A scan host is the host from which
the automatic volume recognition process (avrd) scans unassigned drives.)
This design enables NetBackup to support Dynamic Loop Switching or SAN
zones. Each tape drive needs to be detected only from a single host. Each tape
drive can potentially have its own scan host that switches dynamically to
process errors and continue availability. A central device arbitrating component

manages scan host assignments for shared drives. The arbitrating component
also provides a network drive reservation system so that multiple NetBackup
media servers can share a drive.
Polling a shared tape drive allows dynamic loop switching and reduces the
number of device accesses and reduces CPU time. However, it cannot detect
connectivity breaks (for example, discontinuity in the Fibre Channel fabric) until
I/O occurs.
Viewing and verifying the device configuration

You can view your device configuration by using one of the following device
configuration interfaces available in NetBackup:
■ Media and Device Management in the NetBackup Administration Console
■ Menu-based device configuration interface (tpconfig on UNIX)
■ Command line interface for device configuration (tpconfig -d command)
You can verify your device configuration by running the Device Configuration
wizard. However, some details of a device configuration cannot be validated
without attempting tape mounts. You can use the NetBackup robtest utility to
mount tapes and validate the configuration.
Adding devices without discovery

Symantec recommends that you use device discovery and the Device
Configuration Wizard to add storage devices to NetBackup and to update the
NetBackup device configuration.
However, NetBackup supports some devices that cannot be discovered
automatically. NetBackup also supports some devices that require user
intervention during the discovery process. To add and configure those devices,
you can use Media and Device Management in the NetBackup Administration
Console or the tpconfig command.
For the devices that NetBackup cannot discovered or that do not have serial
numbers, automated device path correction when the ltid device manager
starts is limited.
Device mapping file

NetBackup uses a file to determine which protocols and settings to use to
communicate with storage devices.
Correlating tape drives to device files or addresses
In some cases, you can add support for new or upgraded devices without waiting
for a release updates from Symantec. For information about how to update this
file, see the NetBackup Administrator’s Guide, Volume I.
Related topics

If your tape drives do not support device serialization, you may have to
determine which device file, logical device name, or SCSI address matches the
physical drive.
For shared drives, see the NetBackup Shared Storage Guide for more
information. (NetBackup Enterprise Server only.)
Correlating devices and device files on UNIX hosts

Correlate device files to physical drives when you create the device files for each
drive. The NetBackup Device Configuration Guide provides guidance to help you
create device files. The following is a general procedure:
To correlate device files

1 Determine the physical location of each drive within the robotic library. The
location usually is shown on the connectors to the drives or in the vendor’s
documentation.
2 Physically connect the drives to SCSI adapters in your host.
3 Record the adapter and SCSI addresses to which you connected each drive.
4 Create device files for each drive; use the SCSI addresses of the drives and
adapters. Add the device file using your notes from step 3 to complete the
correlation between device files and physical drive location.
5 Configure the robot in NetBackup and then add the drives.
When you add the drives, verify that you assign the correct drive address
(for example, robot drive number) to each device path.
Optionally, use the appropriate NetBackup robotic test utility to verify the
configuration. For information about the robotic test utilities, see the NetBackup
Troubleshooting Guide.
After you create device files and configure NetBackup, you can verify the
configuration.
To verify the configuration (UNIX)
1 Stop the NetBackup device daemon (ltid).

2 Start ltid, which starts the Automatic Volume Recognition daemon (avrd).
You must stop and restart ltid to ensure that the current device
configuration has been activated.
If robotic control is not local to this host, also start the remote robotic
control daemon.
3 Use the robotic test utility to mount a tape on a drive.
4 Use the NetBackup Administration Console Device Monitor to verify that
the tape was mounted on the correct robot drive.
Verify configuration example
For example, assume a TLD robot includes three drives and the operating
system includes the following device paths:
■ Drive 1: /dev/rmt/0cbn
Also assume that in step 3 in “To verify the configuration (UNIX),” you
requested that the tape be mounted on drive 1. If the device path for the drive is
configured correctly, the Device Monitor shows that the tape is mounted on
drive 1.
If the Device Monitor shows that the tape is mounted on a different drive, the
device path for that drive is not configured correctly. For example, if the Device
Monitor shows that the tape is mounted on Drive 2, the device path for drive 1 is
incorrect. Replace the drive 1 device path (/dev/rmt/0cbn) with the correct
device path (/dev/rmt/1cbn) for drive 2. You may need to use a temporary
device path while making these changes. You also know that the device path for
drive 2 is incorrect. Possibly, the device paths were swapped during
configuration.
Use the robotic test utility to unload and unmount the tape from drive 1. Repeat
the test for each drive.
If the path to the drive where the tape is mounted is not on the host with direct
robotic control, you may have to unload the drive with a command from another
host or from the drive’s front panel.
Correlating devices and names on Windows hosts

Use the following procedure to match the logical device name with the drives:
To correlate SCSI addresses

1 Note the SCSI target of the drive.
2 Correlate the SCSI target to the drive address by using the robot’s interface
panel. Alternatively, examine the indicators on the rear panel of the tape
drive.
3 Determine the physical drive address (for example, number) by checking
labels on the robot.
4 Configure the robot in NetBackup and then add the drives.
When you add the drives, nsure that you assign the correct drive address to
each set of SCSI coordinates.
Optionally, use the appropriate NetBackup robotic test utility to verify the
configuration. For information about the robotic test utilities, see the NetBackup
Troubleshooting Guide.
To verify the configuration (Windows)

1 Stop the NetBackup Device Manager (ltid).
2 Restart ltid, which starts the Automatic Volume Recognition process
(avrd). You must stop and restart ltid to ensure that the current device
configuration has been activated.
If robotic control is not local to this host, also start the remote robotic
control daemon.
3 Use the robotic test utility to mount a tape on a drive.
4 Use the NetBackup Device Monitor to verify that the tape was mounted on
the correct robot drive.
Verify configuration example
For example, assume a TLD robot includes three drives at the following SCSI
addresses:
■ Drive 1: 5,0,0,0
■ Drive 2: 5,0,1,0
■ Drive 3: 5,0,2,0
Also assume that in step 3 in “To verify the configuration (Windows),” you
requested that the tape be mounted on drive 1. If the SCSI coordinates for the
drive are configured correctly, the Device Monitor shows that the tape is
mounted on drive 1.
If the Device Monitor shows that the tape is mounted on a different drive, the
SCSI coordinates for that drive are not correctly configured. For example, if the
Tape I/O commands
Device Monitor shows the tape mounted on drive 2, the SCSI coordinates for
drive 1 are incorrect. Replace the drive 1 SCSI coordinates (5,0,0,0) with the
correct SCSI coordinates (5,0,1,0) for drive 2. You also know that the SCSI
coordinates for drive 2 are incorrect. Possibly, the SCSI coordinates were
swapped during configuration.
Use the robotic test utility to unload and unmount the tape from drive 1. Repeat
the test for each drive.
If the data path to the drive where the tape was mounted is not on the host with
direct robotic control, you may have to unload the drive with a command from
another host or from the drive’s front panel.
Tape I/O commands

If you are not using NetBackup or Storage Migrator, or you want to troubleshoot
or test Media Manager, you can manually request Media Manager to mount and
remove specific volumes by using the commands found in this chapter.
This chapter includes the following topics:
■ Requesting tapes
■ Reading and writing tape files
■ Removing tape files
■ Using an optical disk
■ External access to Media Manager controlled devices
■ User error messages
Requesting tapes
The tpreq command allows you to request a tape of a particular density and
specify various options, such as the access mode. This command reserves a
single drive and creates a file in the current working directory (unless a full path
is specified). The file acts as a symbolic link to the tape and all subsequent access
to the tape is through this file name. Users do not have to be concerned with the
full path to a specific device file.
The information you supply on the tpreq command is required for use by the
Media Manager device daemon and used to validate all access requests to the
tape file.
For all types of tapes, the tape is actually mounted and assigned when you enter
the tpreq command.
Tape I/O commands
By default, the drive assigned is one which supports DLT cartridge tapes, using
the density dlt. You can use the density option on tpreq to request a drive that
supports another density. For a list of supported densities and drive types, see
the tpreq man page or the online help for the Pending Requests pane in the
NetBackup Administration Console..
The density for the physical write is not selected automatically on drives. It is
requested, so an operator can satisfy the correct drive. Density is determined by
the /dev device name that was used when the drive was added to the Media
Manager configuration or by the buttons selected on the drive.
A tpreq command must include a media ID and a file name. If the tape volume
is associated with a volume pool (configured using Media Manager), the name of
the volume pool may also be specified using the -p parameter. If the pool name is
specified, the name will be validated against the pool name associated with the
media in the EMM database.
See tpreq in the NetBackup Commands for UNIX and Linux for more
information.
drive_mount_notify script
When a tpreq command is executed, a call is made to execute the
drive_mount_notify script immediately after the media has been
successfully placed in a pre-selected drive.
This script allows user special-handling to occur at this point. Control is then
returned to NetBackup to resume processing. The script is only called from the
tpreq command for drives that are in robots and is not valid for standalone
drives.
This script is located in the /usr/openv/volmgr/bin/goodies directory. If
you wish to use this feature, this script should be activated and put into the
/usr/openv/volmgr/bin directory.
Usage information is documented within the script.
tpreq example
The following sample tpreq command reserves a tape drive and creates a
symbolic tape file:
/usr/openv/volmgr/bin/tpreq -f tape1 -m jlr01 -a w -d qscsi
This command creates a file named tape1in the current working directory and
links the file to the drive containing the tape volume having the media ID of
JLR01. The access mode for the tape file is set to write and a 1/4-inch cartridge
drive is assigned.
Tape I/O commands
Reading and writing tape files

Reading or writing tape files involves copying the file from tape to disk or from
disk to tape. To perform read or write operations, use one of the UNIX
commands that performs input/output operations, for example tar or mt.
Positioning tape files

The mt command positions tape files by skipping forward or backward
according to tape marks. The following table shows the options available on the
mt command for positioning tapes and how they affect tape files.
mt Option Operation
eof, weof Writes end-of-file tapemarks at the current position on the tape
according to the count option on mt.
fsf, bsf Spaces forward or backward the number of tapemarks on the count
option.
fsr, bsr Spaces forward and backward the number of records according to the
count option on mt. bsr is only supported for the undefined record
type.
The following example uses mt to skip forward three files on a tape:

mt -f tape1 fsf 3
Rewinding tape files

When a file is rewound, it is positioned to the beginning of the data. To rewind a
tape file, you can use the mt command.
The following command causes rewinding of tape file tape1. tape1 is
positioned to the beginning of the tape volume associated with the file:
mt -f tape1 rewind
The count option is not used for the rewind operation. If a count is specified, it is
ignored.
Removing tape files

When you have completed reading or writing tape files, use the
/usr/openv/volmgr/bin/tpunmount command to end the assignment of
the tape file. This command removes from the directory the tape file you created
using tpreq and causes the tape volume to be removed from the tape drive.
Using tpunmount is required for each file created by a tpreq command.
Tape I/O commands
See tpunmount in the NetBackup Commands for UNIX and Linux for more
information.
drive_unmount_notify script
When a tpunmount command is executed, a call is made to execute the
drive_unmount_notify script.
This script allows user special-handling to occur at this point. Control is then
returned to NetBackup to resume processing. The script is only called from the
tpreq command for drives that are in robots and is not valid for standalone
drives.
This script is located in the /usr/openv/volmgr/bin/goodies directory. If
you wish to use this feature, this script should be activated and put into the
/usr/openv/volmgr/bin directory.
Usage information is documented within the script.
Using an optical disk

An optical disk cannot be used in the same ways that a tape can. It does have
many similarities to a tape and takes advantage of the automation provided by
Media Manager: optical disks allow automatic volume recognition, and they can
be mounted and moved by a robot.
Optical disks work well with Symantec storage management applications. These
applications use databases to handle location information (offsets, capacity, and
so forth) that would otherwise have to be done by the user. A user who is willing
to keep track of such information can access an optical disk using the following
tape commands.
In the following example, a user performs two tar operations to an optical disk,
then lists the second tar image.
1 A rewritable optical disk is requested, as follows.
tpreq tape -m XXX01A -d odiskwm -p NetBackup
2 The first tar is performed, starting at the beginning of the disk.

tar -cvf - /home/arh | dd of=tape ibs=10240 obs=10240
0+473 records in
189+0 records out
3 The second tar is performed, starting at the end of the previous data. The
records out information is used for the oseek parameter.
tar -cvf - /home/arh/.cshrc|dd of=tape ibs=10240
obs=10240 oseek=189
4 The disk is unmounted, as follows.
Tape I/O commands
tpunmount tape
5 The optical disk is requested again.

tpreq tape -m XXX01A -d odiskwm
6 The second tar image is listed. To access the data, the user must know
where it is located for the iseek parameter.
dd if=tape ibs=10240 obs=10240 iseek=189 | tar -tvf
rw-r--r--357/110 2386 Jul 9 14:01 1992
/home/arh/.cshrc
7 The disk is unmounted, as follows.

tpunmount tape
External access to Media Manager controlled devices

The device daemon (ltid) restricts access to Media Manager controlled drives
that are in an up state, by changing the permissions of the device files for those
drives. The permissions are changed to 0600 when ltid starts and back to their
original settings when ltid is terminated (or when a drive’s state is changed to
DOWN).
Do not modify the permissions of these device files when ltid is active. To
ensure reliable operation, only users that use the tpreq and tpunmount
commands, or the drive_mount_notify and drive_unmount_notify
callout scripts, explained in this chapter can have access to a drive that is up
under ltid control.
The following example uses tpreq:
tpreq tape -m xxx -d 4mm -f /tmp/tape
/bin/tar -cvf /tmp/tape files
tpunmount /tmp/tape
Users that do not use tpreq and tpunmount or the callout scripts to access
drives that are in the up state may encounter both access and data reliability
problems. These problems occur because the Media Manager avrd daemon
periodically attempts to rewind and read data from media in drives that are up
and are not currently assigned.
A user that is unable to use tpreq and tpunmount must do one of the following
actions before attempting to access the drive:
◆ Down the drive prior to accessing it.
◆ Terminate ltid by executing stopltid and then restart ltid after
accessing the drive.
Tape I/O commands
User error messages

For explanations of the status and error messages, see the NetBackup
Troubleshooting Guide or the NetBackup Administration Console help.
Chapter 4
Using NetBackup with AFS
This chapter explains how to install, configure, and use NetBackup to back up
AFS file servers. (AFS is an acronym for Andrew File System.)
Note: AFS is no longer available from IBM and IBM has ended support for AFS.
AFS is not supported with 6.5 clients. AFS continues to be supported with
NetBackup 5.x clients that run under 5.x or 6.0 servers.
Installation
System requirements
■ The AFS file servers that can be NetBackup AFS clients:
■ Solaris 7 and HP-UX 11.0, or IBM AIX 4.3.3 platforms
■ NetBackup 5.0 or 5.1 clients
■ AFS level 3.6 or later installed
Server and client installation

The NetBackup software that is needed to support AFS is automatically installed
with the server and client.
Configuration
To configure backups for NetBackup AFS clients, add an AFS policy to the
NetBackup configuration on the master server. The requirements are the same
as for other NetBackup policies, except for the differences that are mentioned
here. To back up the files and directories that are not in AFS volumes, create
separate policies.
242 Using NetBackup with AFS
Configuration
General policy attributes

Specify AFS as the policy type in the policy’s general attributes.
Client list
In the client list, specify the names of the AFS file servers to be backed up. These
systems must have the NetBackup client installed.
Backup selections
In the backup selection list for the AFS policy, specify the AFS volumes and vice
partitions to be backed up. The following example shows both volumes and vice
partitions:
user.abc
/vicepb
/vicepc/user.*
In this instance, NetBackup backs up the following:

■ The volume user.abc
■ All volumes in vice partition vicepb
■ All volumes in vicepc that begin with user.
When the list includes a vice partition, all the volumes in the partition are
backed up one at a time.
Note: NetBackup supports the maximum AFS 3.6 volume size of 8 GB.
Backup selection list directives

The following directives can be in the backup selection list in an AFS policy:
■ CREATE_BACKUP_VOLUMES
This directive causes NetBackup to create .backup volumes before it
performs the backup. If a .backup volume already exists, NetBackup
overwrites it to create a more recent copy.
Because NetBackup backs up only the .backup copy of AFS volumes, this
directive is useful if an automated mechanism is not in place to create
.backup copies. Creating .backup copies also ensures that the backups
include the latest changes.
Using NetBackup with AFS 243
Configuration
Caution: If an automated mechanism is not in place to create .backup copies,

include the CREATE_BACKUP_VOLUMES directive in the backup selection list or
AFS volumes are not backed up.
■ REMOVE_BACKUP_VOLUMES
This directive causes NetBackup to remove .backup volumes after
performing the backup. The directive removes .backup volumes that are
created using the CREATE_BACKUP_VOLUMES directive or created by
another mechanism.
■ SKIP_SMALL_VOLUMES
This directive allows small or empty volumes to be skipped during backups.
For example:
SKIP_SMALL_VOLUMES=5
(do not include spaces on either side of the = sign)
In this example, NetBackup skips volumes ≤ 5 KB. Specify any number for
the volume size.
If no number is specified, the size defaults to 2 KB. For example:
SKIP_SMALL_VOLUMES
The following rules also apply to the directives:

■ Directives must be all upper case.
■ Although directives can be located anywhere in the backup selection list, try
to place directives at the top. For example:
CREATE_BACKUP_VOLUMES
SKIP_SMALL_VOLUMES
/user.abc
/vicepb
Regular expressions
NetBackup supports regular expressions in backup selection list entries. These
are useful to perform the following actions:
■ Add or move volumes without having to change the backup selection list.
■ Add vice partitions without having to change the backup selection list.
■ Split volumes and vice partitions on AFS file servers into groups that can be
backed up by separate policies. The different groups allow for concurrent
backups or multiplexing.
The following examples use regular expressions:
user.[a-m]*
/vicep[a-c]
Backups and restores
Exclude and include lists

Exclude lists can be created on the client to exclude certain specific volumes
from automatic backups. An exclude list cannot contain vice partitions but it
can contain individual volumes within a vice partition.
An include list adds volumes to the backup that were specified in the exclude
list. For example, if a range of volumes is excluded, the include list can add back
specific volumes within the range.

Backups
Note: User backups or archives of AFS volumes are not allowed.
Automatic backup
The most convenient way to back up NetBackup for AFS clients is to configure
an AFS policy and set up schedules for automatic, unattended backups.
Manual backup
The administrator on the master server can use the NetBackup Administration
Console to run manually a backup for an AFS policy.
For information about manual backups, see Chapter 3 of the NetBackup
Restores
The administrator performs all restores on either the NetBackup AFS client or
the master server. Restores are performed on the basis of volumes. To restore a
vice partition, the administrator must select all the volumes in that partition.
Caution: If the Overwrite Existing Files option is selected, the volumes are
overwritten. All changes or files that were created since the last backup are lost.
Restore from the NetBackup for AFS client

An administrator on a NetBackup AFS client (AFS file server) can use the
NetBackup Backup, Archive, and Restore interface to restore volumes to that
Using NetBackup with AFS 245
client. An administrator can perform a redirected restore as well. A redirected

restore restores a volume to another volume or another vice partition.
Restore from the NetBackup master server

The administrator can use the NetBackup Backup, Archive, and Restore
interface on the master server to restore volumes to the same NetBackup AFS
client (AFS file server). Or, to perform a redirected (or server-directed) restore.
For instructions, see the online help in the Backup, Archive, and Restore
interface.
Notes about restores

■ The NetBackup Backup, Archive, and Restore client interface (jbpSA),
provides a convenient mechanism for specifying an alternate name for a
volume or a vice partition. Specify an alternate volume name to prevent an
existing volume from being overwritten by the restore.
■ If the administrator does not specify Overwrite Existing Files or an
alternate name for the volume, NetBackup adds an R to the name of the
restored volume. For example:
■ If the volume name is less than 22 characters long, NetBackup adds a
leading R to the name of the restored volume. For example:
If the volume name is:
/AFS/shark/vicepa/user.abc
The restored name is:

/AFS/shark/vicepa/Ruser.abc
■ If the volume name is 22 characters long, the first character of the

original volume name is replaced with an R. (The maximum allowable
length for a volume name is 22 characters.) For example:
If the volume name is:
/AFS/shark/vicepa/engineering.documents1
The restored name is:

/AFS/shark/vicepa/Rngineering.documents1
■ To specify an existing volume to restore to an alternate path, enable the

Overwrite Existing Files option. In this case, the entire volume is
overwritten. If Overwrite Existing Files option is not enabled, the restore
fails.
■ To restore a volume to an alternate vice partition, the vice partition must
exist or the restore fails.
Troubleshooting
Troubleshooting
The following sections provide tips and information for troubleshooting

problems with NetBackup for AFS. See the NetBackup Troubleshooting Guide for
UNIX and Windows for overall troubleshooting information.
Troubleshooting backups
To increase the level of detail in the logs:
■ Add the VERBOSE option to the /usr/openv/netbackup/bp.conf file on
the NetBackup for AFS client.
■ Create the following debug log directory on the NetBackup for AFS client:
/usr/openv/netbackup/logs/bpbkar
If the AFS backup terminates with a status code of 9, the code indicates that
NetBackup AFS client software was not properly installed. (An extension
release update is needed.)
If the AFS backup terminates with a status code of 78, the code indicates an
AFS vos command failure. (afs/dfs command failed) The NetBackup
Problems Report provides additional information as to why the command
failed. The bpbkar debug log shows the command that was run. Run the
vos command manually to attempt to duplicate the problem.
Also, examine the /usr/openv/netbackup/listvol file on the
NetBackup client for irregularities. The vos listvol command can
demand much from system resources so NetBackup caches the output of
the vos listvol command in this file. NetBackup uses the cached
listvol file to obtain the volume list instead of running another vos
listvol command. (If the cached listvol file was created less than four
hours before the backup.)
Troubleshooting restores
If the restore of an AFS volume fails, check the restore process log for additional
information. Create a /usr/openv/netbackup/logs/tar debug log
directory if a vos restore command failure is indicated. Then, retry the
operation and check the resulting log to see that the vos restore command
was run.
Chapter 5
Intelligent Disaster
Recovery
Intelligent Disaster Recovery (IDR) for Windows is an automated disaster
recovery solution. It allows administrators to recover Windows computers
quickly and efficiently after a disaster. The IDR wizards help administrators
prepare for disaster recovery and recover computers to their state before the
disaster.
This chapter contains the following sections:
■ “Changes for NetBackup 6.0 and later” on page 248 explains limited
supported for IDR in NetBackup 6.0 and later.
■ “Supported Windows editions” on page 248 documents the Windows
versions that IDR supports.
■ “Overview of IDR use” on page 250 explains the main steps that are involved
in using the disaster recovery software.
■ “About the DR files” on page 250 introduces the Disaster Recovery files and
explains their importance in disaster recovery.
■ “Configuring NetBackup policies for IDR” on page 251 explains how to
configure the policies that contain the clients that use IDR.
■ “Backing up the protected computer” on page 252 explains that you must
back up the computer before you create the bootable media that is used in
recovery.
■ “Creating IDR media” on page 252 explains how to use the IDR Preparation
Wizard to prepare the bootable media that is used to recover data.
■ “Updating IDR media” on page 258 explains how and when to update the
IDR media so it is always ready when it is needed.
248 Intelligent Disaster Recovery
Changes for NetBackup 6.0 and later
■ “Recovering your computer” on page 261 explains how to perform disaster

recovery.
■ “Notes on recovering specific platforms” on page 267 provides information
on data recovery for specific types of platforms.
■ “IDR frequently asked questions” on page 269 answers questions that are
frequently asked about IDR.
Changes for NetBackup 6.0 and later

Bare Metal Restore replaces Intelligent Disaster Recovery beginning with the
NetBackup 6.0 release. To protect NetBackup 6.0 and later clients, use the Bare
Metal Restore option for NetBackup.
You cannot use IDR to protect or recover NetBackup 6.0 or later client
computers. However, you can use Intelligent Disaster Recovery on NetBackup
6.0 and later servers as follows:
■ To protect NetBackup 5.1 and 5.0 clients.
■ To generate bootable media for supported clients (master server only).
If a backup policy is configured to collect IDR information:
■ Backup jobs for NetBackup clients earlier than 6.0 return a status of 0
(successful).
■ Backup jobs for NetBackup 6.0 or later clients return a status of 1 (partially
successful). The NetBackup server tries to collect IDR information from
those clients and is unable to do so. If no other problems exist, the client
data is backed up.
If you use IDR with NetBackup 6.0 or later to protect NetBackup 5.1 or 5.0
clients, the NetBackup master server must be licensed for IDR.
Supported Windows editions

IDR lets you protect and recover the following Windows computers:
■ Windows Server 2003 (Standard Edition, Enterprise Edition, and Web
Edition).
■ Windows XP 32-bit versions.
■ Windows 2000 Server, Advanced Server, and Professional.
■ Windows NT 4.0 Enterprise Server, Small Business Server, and Workstation
editions with Service Pack 6A or later. Requires a supported NetBackup 5.x
media server to back up the client.
Intelligent Disaster Recovery 249
Requirements for IDR
Requirements for IDR
The following are the requirements for IDR:

■ NetBackup client software must be installed on the Windows computers that
you want to protect. The IDR software is installed automatically when that
client software is installed. IDR is not installed on NetBackup 6.0 and later
client computers. The IDR software is not required (and cannot be installed)
on UNIX computers.
■ The NetBackup master server that collects the disaster recovery
information must be licensed for IDR. The NetBackup master server that
collects the disaster recovery information can reside on either a Windows or
UNIX computer.
■ The IDR Preparation Wizard that runs on the client computer generates
recovery media only for the computers that have the same IDR version
installed.
■ The protected computer must be an Intel computer that runs a supported
Windows operating system.
For more information, see “Supported Windows editions” on page 248.
■ At least 40 MB of hard drive space to hold the minimal recovery computer
on the protected computer.
■ The protected computer must contain sufficient space to accommodate the
restored data.
■ The protected computer must contain sufficient swap space to support the
computer’s RAM. For example, for 128 MB of RAM, the minimum swap that
is used is 128 MB. For a 2-GB partition that stores 1.8 GB of data, the
required hard drive space for that partition is 1.8 GB. In addition, it must
contain 128 MB plus 40 MB, for a total of 1.97 GB.
■ The partition on the first physical drive on the protected computer must be
the boot partition and must be labeled C:\.
■ A protected computer must use a network card that does not require a
Windows service pack to be installed. Refer to the “Network LAN Adapters”
section of the “Hardware Compatibility List” that accompanies the
Microsoft Windows software. This section contains a list of cards that have
passed Microsoft compatibility tests without service packs.
■ Windows must support the required driver of the CD-ROM drive on a
protected computer.
Windows NT computers: The IDR Preparation Wizard may detect that the
driver on the protected computer is different than the driver on the
Windows NT installation CD. In that case, select a driver to use. Symantec
Overview of IDR use
recommends using the SCSI drivers currently installed on the protected

computer because the drivers on the Windows CD may not be up to date. For
IDE hard disks greater than 8 GBs, use the SCSI driver currently installed on
the computer.
Overview of IDR use

Using IDR involves the following steps:
■ NetBackup client software must be installed on the Windows computers that
you want to protect. The IDR software is installed automatically when that
client software is installed. IDR is not installed on NetBackup 6.0 and later
client computers. The IDR software is not required (and cannot be installed)
on UNIX computers.
■ Licensing. To activate IDR for backups, you must enter an IDR license key on
the master server.
■ Configuration. On the NetBackup master server, select the Collect disaster
recovery information general attribute when setting up the policy
configuration for protected clients. You can use a NetBackup master server
on either a Windows or UNIX computer to collect disaster recovery
information.
■ Backup. An initial full backup must be completed of a protected computer
before you create IDR media. Also, you should back up your computer
frequently and update the DR files often.
■ Preparing the IDR media. Use the IDR Preparation Wizard on the client
computer to help prepare the media that is used to recover protected
computers.
■ Recovery. Use the Disaster Recovery Wizard to help rebuild the protected
computer and restore data to that computer. The protected computers
should be backed up regularly by NetBackup.
The installation, configuration, backup, and media preparation steps are
necessary for to recover a Windows computer through a network connection to
a NetBackup server.
About the DR files

The disaster recovery (DR) files are mentioned frequently in this chapter and in
the wizard screens. A DR file contains the following information about the
protected computer:
■ Hard disk partition information.
Configuring NetBackup policies for IDR
■ Network interface card information.

■ NetBackup configuration information necessary to restore data files.
The automatic recovery of an IDR-protected computer requires a copy of the DR
file for that computer. IDR must be installed on the server and client. The server
must be configured to collect disaster recovery information for NetBackup to
create a DR file. NetBackup stores a copy on the client and the master server
after each of the following backups:
■ Full backup
■ Incremental differential or incremental cumulative backup
■ User backup
■ User archive
NetBackup stores the DR file for each client in the
install_path\NetBackup\Idr\data
directory on the client. The DR files that are generated after a backup are named
in the format netbackup_client_name.dr. For example, if the client name is
bison, the DR file is bison.dr.
Note: IDR requires that the DR file name match the computer name of the client.
That is, if the network recognizes the computer name bison, the DR file must be
named bison.dr. If the NetBackup client name is different, rename the DR file
that is created after each backup before using it in a recovery. (Use the format
computer_name.dr.)
On the NetBackup master server, the DR files for all clients are stored in the
NetBackup catalog on the server.
Configuring NetBackup policies for IDR

Set up the policy configuration on the NetBackup master server as follows:
■ Ensure that each protected client is in an MS-Windows-NT type policy.
■ Select the Collect disaster recovery information policy attribute for at least
one of the MS-Windows-NT policies that backup protected clients.
■ The NetBackup master server that collects disaster recovery
information must be licensed for IDR. If not, the Collect disaster
recovery information attribute cannot be selected.
■ Ensure that all the clients in this policy have IDR installed. If a client
does not have IDR installed, the backups for that client by this policy
can never end with a status of 0. A successful backup in this instance
Backing up the protected computer
shows a status of 1 (partially successful). The status is a result of

NetBackup being unable to find a DR file to store in its catalog after
each backup.
■ NetBackup 6.0 and later collects the DR information from the clients
that run versions of NetBackup earlier than 6.0. However, you must use
the IDR software revision on the client to prepare the bootable media
for that client. For example, for a NetBackup 5.1 client, use the same
IDR version to prepare the IDR media.
■ Ensure that the client name that is used in the NetBackup policy
configuration matches the client’s computer name. If the names do not
match, rename the DR file that is created after each backup before
using it in a recovery. (Use the format computer_name.dr.)
Backing up the protected computer

Perform a full backup of the protected computer before you prepare the IDR
media, which includes the DR file used in recovery. The NetBackup master
server that performs the backup must be configured to collect disaster recovery
information. The backup information that is collected is used to create the DR
file.
You can prepare IDR bootable media if differential or incremental backups have
occurred since the full backup.
Ensure that all local drives are backed up. For Windows 2000 computers, ensure
that System State is backed up.
Ensure that any utility partitions are backed up. Utility partitions are small
partitions created on the hard drive, usually by the computer vendor, that may
contain computer configuration and diagnostic utilities.
Creating IDR media

The IDR Preparation Wizard helps you to create the IDR media that is used in
recovery. A set of IDR media includes the following:
■ The bootable media that is used to boot the computer and install and
configure the operating system.
■ System-specific drivers and the Disaster Recovery Wizard.
■ The disaster recovery (DR) file.
■ For Windows XP and Windows Server 2003 computers, Windows Automated
System Recovery files.
To create IDR media, you must have:
Creating IDR media
■ At least one full backup of the computer to be protected.

■ The Windows installation CD for the version and language that is installed
on the protected computer.
■ The license key for the Windows 2000, Windows XP, or Windows Server
2003 operating system.
■ Administrative privileges for the protected computer.
■ A device that can create bootable media:
■ CD-R drive (CD Recordable CD-ROM)
■ CD-RW drive (CD Rewritable CD-ROM)
■ Diskette drive (IDR does not support bootable diskette media for
Windows XP or Windows Server 2003)
More information about media is provided later in this chapter.
You must prepare the media before a disaster. For CD-R or CD-RW, you should
also try booting from the media before a disaster occurs to ensure that your
hardware can boot from it.
For more information, see “Step 1: Boot your computer” on page 262.
Choosing the bootable media

For Windows NT and Windows 2000, the IDR Preparation Wizard can create
both bootable diskettes and bootable CD-Recordable (CR-R) or CD-Rewritable
(CR-RW) media.
Note: IDR does not support bootable diskette media for Windows XP or Windows
Server 2003.
Consider the following factors to decide between diskettes and CD-ROM media:
■ Diskettes work on most computers but require more time for preparation
and recovery than CDs.
■ Diskettes require the Windows installation CD during recovery.
■ Because of space limitations, diskettes hold SCSI driver information for only
one computer. To use one set of diskettes to protect multiple computers,
choose one computer that represents all the other computers and create
bootable media for it. For computers with different SCSI drivers, create a set
of diskettes for each computer with a different driver.
■ CDs require less time for preparation and recovery than diskettes.
■ CD media has enough space to store SCSI driver information for multiple
computers. Use a single CD for multiple computers during disaster recovery.
Creating IDR media
■ CD media requires that the protected computer have a BIOS that supports a
CD boot.
■ CD media requires CD writing hardware. The protected computer does not
require a CD writer. The IDR Preparation Wizard creates a bootable image to
write to a CD on any computer that contains a CD writer.
■ For CD media, third-party CD writing software is required if the protected
computer does not have a CD writer. The software is also required if the IDR
Preparation Wizard cannot detect the CD writer that is attached to the
protected computer. The CD hardware and software must be able to write
ISO 9660 CD images.
■ With both diskettes and CDs, prepare separate media for each operating
system level and language being protected.
Creating bootable diskettes

The IDR Preparation Wizard helps create a full set of diskette media to boot a
computer during recovery and to run the Disaster Recovery Wizard.
A full set of IDR diskette media includes the following:
■ Windows setup diskettes. A Microsoft Windows utility creates the Windows
Setup diskettes. The utility is on the Windows installation CD. The IDR
Preparation Wizard modifies these setup diskettes for use specifically with
NetBackup for Windows.
■ Intelligent Disaster Recovery Diskettes that contain the computer-specific
information that is necessary to perform disaster recovery. The IDR
Preparation Wizard creates these diskettes.
Windows NT requires five and Windows 2000 requires six blank, formatted
1.44-MB diskettes for each set of disaster recovery diskettes.
Note: Windows XP and Windows Server 2003 do not support bootable diskettes.
Note: The Windows installation CD is required both to prepare disaster recovery

diskettes and for disaster recovery using those diskettes. You also need the
Windows 2000 license key, either during bootable diskette preparation or during
recovery.
Creating IDR media
To create bootable diskettes

1 Format the diskettes. Windows NT requires five diskettes and Windows 2000
requires six. Windows XP and Windows Server 2003 do not support bootable
diskettes.
2 To prepare the diskettes, select Start > Programs > Veritas NetBackup >
Intelligent Disaster Recovery PrepWizard. The IDR Preparation Wizard
Welcome screen appears.
3 Click Next to continue.
The Create or Update IDR Boot Media screen appears.
4 Select Create - Full Set of Diskettes to boot the Windows Installation CD

and click Next.
The Starting Bootable Diskettes Creation screen appears.
5 Follow the prompts until the IDR Preparation Wizard is completed.
To modify diskette sets for use with multiple Windows 2000

computers
To use the same diskettes 2 through 5 for all IDR-protected Windows 2000
computers, do not select Let IDR Automatically Partition the Boot and System
Drive. The option appears on the Select Computer for Diskette Preparation
screen of the wizard. You can use the same diskettes 2 through 5 for all of the
Creating IDR media
Windows 2000 computers. However, you have to create a different diskette 1 for
each computer protected with IDR.
Diskette 1 contains a file named winnt.sif. It is the script used to automate
the installation of Windows 2000 for disaster recovery. This scripted
installation of Windows 2000 requires that the name of the computer being
recovered be listed in the winnt.sif file.
Therefore, for each Windows 2000 computer that shares diskettes 2 through 5,
make a copy of diskette 1 (and its files). For each copy of diskette 1, edit the
winnt.sif file and change the computer name to the name of the computer to
be protected. If you do not change the computer name, duplicate computer
names on the network may occur. The duplicate names may prevent the
recovered computer from participating on the network.
Creating a bootable CD image

The IDR Preparation Wizard helps create a bootable CD image. Then write the
image to a CD using the IDR Preparation Wizard or other writing software. The
computer where you run the IDR Preparation Wizard may not have a CD-R or
CD-RW drive. If it does not, write the image onto a CD on a different computer
using third-party CD writing software.
The CD image contains all the necessary IDR files unless you choose to store the
Windows Server 2003 Automated System Recovery files on a diskette. If you
store them on the CD, the ASR files always are read from the CD even if more
recent versions are on a diskette. For example, suppose you create a bootable CD
and then later create IDR diskettes. During recovery, the ASR files are read from
the CD even though the IDR diskettes contain more recent versions.
The Windows installation CD is required only during media preparation.
The license key for your Windows 2000, Windows XP, or Windows Server 2003
operating system is required. If you do not enter the license key while creating
the bootable CD, you must enter it during recovery.
Note: On Windows NT 4.0 computers, the IDR software cannot write to a CD;
therefore, you must use other CD writing software to create the CD.
To create a bootable CD image

1 Select Start > Programs > Veritas NetBackup > Intelligent Disaster
Recovery PrepWizard to prepare the bootable CD image. The IDR
Preparation Wizard Welcome screen appears.
Creating IDR media
3 Select Create - Bootable CD Image for Use with CD Writers (ISO 9660) and
click Next.
The Starting CD Image Creation screen appears.
Caution: Test your bootable CD to ensure that your computer can boot from it.
(See “Step 1: Boot your computer” on page 262.)
Creating IDR diskettes

Two formatted, 1.44 MB floppy diskettes are required to create IDR diskettes.
To create IDR diskettes

Recovery PrepWizard to prepare the IDR diskettes. The Welcome screen for
the IDR preparation wizard appears.
Updating IDR media
2 Click Next to continue. The Create or Update IDR Boot Media screen
appears.
3 Select Create - IDR Diskettes Only (Includes ASR Files for XP/2003) and
click Next. The Creating the IDR Diskettes screen appears.
Updating IDR media

Update the IDR media if the hardware configuration changes, if SCSI drivers
were updated, or if other computer drivers were updated.
Also, Symantec recommends periodic IDR diskette updates so the diskettes
contain the latest DR files.
Updating a bootable CD
You cannot update a bootable CD, you must create a new bootable CD image and
then burn a new CD. If you install new hardware or change components on a
protected computer, create a new bootable CD.
For procedures, see “Creating a bootable CD image” on page 256.
Updating IDR media
Updating bootable diskettes

Use the IDR Preparation Wizard to update the set of bootable diskettes. Update
the diskettes:
■ After hardware changes.
■ After SCSI driver updates.
■ After other computer driver updates.
■ When you already have a full set of bootable diskettes that you want to
update.
To update IDR bootable diskettes

Recovery PrepWizard to prepare the IDR diskettes. The Welcome screen for
the IDR preparation wizard appears.
3 Select Update - Full Set of Diskettes Used to Boot the Windows Installation
CD and click Next.
Updating IDR media
Updating IDR diskettes only

You can update the IDR diskettes with the latest DR file (and ASR files for
Windows XP and Windows Server 2003 computers) by using the IDR
Preparation Wizard.
To update the DR file only, run the drfile.exe file from a command prompt to
create a new DR file. Copy the DR file to the diskette.
For more information, see “Using drfile.exe to create or update a DR file” on
page 260.
To update IDR diskettes using IDR preparation wizard

Recovery PrepWizard. to prepare the IDR diskettes. The Welcome screen for
the IDR Preparation Wizard appears.
3 Select IDR Diskettes Only (Includes ASR Files for XP/2003) and click Next.
Using drfile.exe to create or update a DR file

If IDR diskettes have already been created, run the drfile.exe program on the
client to update only the DR file. Then copy the DR file to the diskette that
Recovering your computer
contains the DR file. The name of the DR file should match the computer name
of the client (the name that IDR requires). The name is required, even if it differs
from the name that is used in the NetBackup policy configuration.
1 Go to install_path\NetBackup\bin and double-click drfile.exe.
The drfile.exe program creates (or updates) the DR file that is located in
the install_path\NetBackup\Idr\Data directory on your computer.
2 If the NetBackup client name is different than the computer name, rename
the DR file.
The DR file name is in the form computer_name.dr. The name of the DR
file must match the computer name of the client. If the NetBackup client
name is different than the computer name, you must rename the DR file so
it can be used in a recovery.
3 Insert the diskette that contains the DR file and copy the DR file to it.
The diskette can be one of the IDR diskettes or a separate diskette. If you
use a separate diskette, insert the separate diskette when prompted for the
DR file during disaster recovery.

To use IDR to restore a computer to its pre-disaster status includes the following
steps:
■ Step 1: Boot your computer. Use the previously prepared IDR bootable
media to boot the computer being recovered.
■ Step 2: Windows setup in IDR recovery. Use the Windows installation
program to partition and format the computer drive on the computer being
recovered. The IDR bootstrap process loads and runs the Windows
installation program from the Windows installation CD.
■ Step 3: Disaster recovery wizard. Use the NetBackup IDR Disaster Recovery
wizard to restore your computer to its pre-disaster state and restore your
data files.
Automating the recovery with the Disaster Recovery wizard requires the
following:
■ A NetBackup server that can restore the latest backups to the computer
being recovered.
■ The latest DR file for the computer being recovered.
If you have not updated the DR file since the last backup, it may contain
out-of-date hard disk partition, network-interface-card driver, or backup
set information.
■ Bootable IDR CD media or the original Windows installation CD.

■ The license key for your Windows operating system (if you did not enter the
license key during preparation of the IDR bootable media).
■ For Windows XP and Windows Server 2003 computers, the ASR files for the
computer being recovered.
■ If your network adapter requires special driver software, use the installation
program that the CD manufacturer provides. Special drivers are the drivers
that are not on the operating system installation program. For example, a
driver for a network interface card (NIC) supplied by the manufacturer.
Note: Windows 2000: if Let IDR Automatically Partition the Boot and System
Drives was not selected during IDR preparation,reinstall any utility partitions
before the recovery process begins. Reinstall the partitions by using the
OEM-supplied installation program. During recovery, select the option to
partition and format the drives manually.
Step 1: Boot your computer

You can recover a Windows computer by using the bootable diskettes or the CD
that was created during disaster preparation. The computer being recovered
must have a device capable of booting from the bootable media.
Caution: Disconnect any storage area network or cluster computers that are
attached to the computer being recovered. If they are not disconnected, the hard
drives on those computers may be partitioned and formatted.
To boot a computer using a bootable diskette
1 Insert the bootable diskette.
2 Start the computer.
3 Follow the on-screen boot process instructions and continue with “Step 2:
Windows setup in IDR recovery” on page 263.
To boot from a bootable CD

1 Insert the bootable CD.
2 Start the computer and perform the tasks necessary to boot from the CD. For
example, you may have to press a function key to boot from the CD drive.
The NetBackup Intelligent Disaster Recovery Bootstrap screen appears.
3 Perform one of the following actions:
■ To test the CD to determine if it can boot the computer, press Esc to

exit. Then remove the CD from the drive.
■ To perform disaster recovery, press Enter to continue with the boot
process.
4 Depending on the computer, perform one of the following actions:
■ For Windows NT and Windows 2000, go to “Step 2: Windows setup in
IDR recovery” on page 263.
■ For Windows XP and Windows Server 2003, press F2 to load the ASR
files when prompted by the boot process. If you have an ASR diskette,
place it in the floppy disk drive so the ASR files can be loaded.
5 Continue by going to “Step 2: Windows setup in IDR recovery” on page 263.
Step 2: Windows setup in IDR recovery

During the recovery process, the DR boot process uses the Windows Setup
program to partition and format the computer drive on the recovery computer.
If you booted from the IDR bootable CD, Windows Setup is started from that CD.
If you booted from diskette, the system prompts you to insert the Windows
installation CD so the Windows Setup can be started.
To use Windows setup in IDR recovery

1 Follow the on-screen instructions to continue the boot process.
If you booted from diskette, the program prompts you to insert the
Windows installation CD.
The Windows Setup program is loaded and performs the tasks necessary to
partition and format drives and install a limited version of the operating
system.
2 During Windows Setup, you may have to make choices about the following:
■ For Windows NT, Express Setup or Custom Setup. Usually, Express
Setup is the best choice. Use Custom Setup if SCSI drivers are not
present on the boot media or if RAID hardware needs to be
reconfigured.
■ For Windows NT, FAT or NTFS file system. If a new hard drive is
detected, you must choose which file system format to use. Select FAT
format for the C drive. IDR cannot partition to the old layout if you
build the partition as NTFS.
3 Ensure that no diskettes or CDs are in the drives when prompted to reboot.
Press Enter to reboot the computer. After the reboot, the Disaster Recovery
Wizard starts automatically.
4 Go to “Step 3: Disaster recovery wizard” on page 264.
Step 3: Disaster recovery wizard

After Windows Setup finishes, the Disaster Recovery Wizard starts as part of
the recovery process. Follow the instructions to recover the computer. These
instructions do not provide a procedure because different conditions affect the
process. However, the process is similar to the following.
To use the Disaster Recovery Wizard

1 When the wizard prompts you, select the DR file for the computer to recover
and click Next.
The name of a DR file matches the computer for which it was created. For
example, if the computer is named carrot look for the carrot.dr file.
Note: If a DR file does not exist, click Next to proceed. When the wizard
notifies you that you did not select a recovery file, click Yes to continue in
manual mode.
2 One or more screens about hard disk layout may appear, as follows:
■ Whether to replace the current hard drive partition with the partition
information contained in the DR file or to keep the current hard drive
partitions.
■ Run the Windows Disk Administrator (or Disk Manager) program. The
program lets you make additional changes to the partition information.
To make partition changes, click Run Disk Administrator or Run Disk
Manager.
For more information, see “Notes on altering hard drive partition
sizes” on page 267.
Otherwise, click Next to continue the recovery process.
For more information about Disk Administrator and fault tolerant
configurations, see the operating system documentation.
3 For Windows 2000, a Completed IDR Phase 1 dialog box appears. Perform
one of the following actions:
■ If your network adapter requires special driver software, click
Pre-install Custom Network Driver. Follow the prompts to find and
install the appropriate driver software. Special drivers are the drivers
that are not on the operating system installation program. For
example, a driver for a network interface card (NIC) supplied by the
manufacturer.
■ To continue, click Next and go to step 5 to continue the recovery.
4 For Windows NT only, you are asked to select either Automatic Restore or
Manual Restore for network installation. Perform one of the following
actions:
■ If your network adapters use the drivers and the software that is
included with the operating system, select Automatic Restore. Click
Finish to complete the network installation. Proceed to step 5 to
continue the recovery.
■ If your network adapters require special drivers and software, select
Manual Restore. Select Wired to the Network and click Next. Proceed
to step a.
a To select the network adapter, perform one of the following actions:
■ Click Select from list if the network adapter requires a
manufacturer-supplied setup diskette. Then click Have Disk.
■ If the network adapter does not require a manufacturer-supplied
setup diskette, click either Select from list or Start search.
A list of network adapters appears.
Note: If your network adapter is not listed, click Select from list. Then click
Have Disk add an adapter to the Network Adapter List. For automatic
network installation to succeed, the Windows NT installation program must
be able to recognize the network interface card being used.
b The next screen lists the default network protocols. Select the
networking protocols that are used on the network. Click Next.
c Windows NT is ready to install the networking components. Insert the
Windows NT installation CD or the IDR bootable CD into the CD-ROM
drive. Click Next to continue. (If you created a bootable CD, it may
include the appropriate network drivers if the drive were found during
the IDR preparation process.)
Note: If additional screens about setting up your network interface card

appear, respond as appropriate.
d If TCP/IP is selected as the network protocol, you are prompted to use

DHCP. If you do not want to use DHCP, enter a TCP/IP number.
The Windows NT Networking Installation dialog box appears.
e Click Next to start the network and complete the installation of the
networking components.
f Enter the name of the workgroup or domain for your computer and
click Next.
Note: Symantec recommends that you enter the name of a temporary

workgroup rather than the name of a domain. When the recovery is
complete, the computer is restored to its original workgroup or domain.
g Click Finish to complete the network installation and continue with

recovery.
5 Select either Automatic or Manual:
■ If you selected Automatic, click Next and proceed to step 6.
■ If you select Manual, click Next and proceed to step 8.
6 The restore process merges hardware information from the current live
version of the registry into the saved version of the registry when recovering
the registry. (The saved version is the registry version that was backed up.)
The registry merger ensures that the computer reboots after the restore if
the hardware changed.
If the hardware changed, select the server from which you want to restore
files. Click Start Restore to submit the restore request to the selected
server. The files are restored and the hardware information from the
current live version of the registry is merged with the saved version of the
registry. Go to step 8.
If the hardware has not changed, you do not have to merge the live version
and the saved version of the registry. The hardware registry settings are
identical to the setting in the saved version of the registry. To prevent
merging the registries, continue with step a:
a Start a command window by pressing F1.
b Navigate to the following directory (the default location;
%SYSTEMROOT% is usually C:\Windows) :
%SYSTEMROOT%\System32\VERITAS\NetBackup\Bin
c Type the following command, then press Enter.

W2KOption -restore -display -same_hardware 1
The following output appears:

NetBackup Restore Options
-----------------------------------------
SYSVOL Restore: Primary
Hard Link Restore: Perform secondary restore
Same Hardware Restore: Assume different hardware
NetBackup Restore Options
-----------------------------------------
SYSVOL Restore: Primary
Hard Link Restore: Perform secondary restore
Same Hardware Restore: Assume same hardware
Notes on recovering specific platforms
d Make sure that Assume Same Hardware is displayed in the Same

Hardware Restore field, then continue with the restore process.
7 After the restore is complete, click Next. Go to step 10.
8 Select Start NetBackup Interface to start the NetBackup Backup, Archive,
and Restore interface.
Using this interface, you can make changes to the NetBackup configuration
and you also have more control over the restore. (See the NetBackup
Backup, Archive, and Restore Getting Started Guide for more information on
using the interface.)
When the restore is complete, close the Backup, Archive, and Restore
interface and any other open NetBackup windows.
9 When the restore is complete, click Next.
10 Remove any diskettes from drive A and click Finish to reboot the computer.
Notes on altering hard drive partition sizes
Note: This section applies only to Windows NT and Windows NT 4.0. Formatting
and partitioning is not supported on Windows 2000, Windows XP, or Windows
Server 2003.
IDR defaults to restore hard drive partitions to their pre-recovery size. The
recovery computer may contain a larger hard drive than before the recovery.
For example, a larger hard drive may have been installed or the DR file may be
from a computer with a smaller hard drive. There may be unused and
unallocated hard drive space. Run the Windows NT Disk Administrator program
to alter the partition sizes to match the larger hard drive size. The Windows NT
Disk Administrator program is accessible during the IDR recovery process
within the Recovery Wizard. For information about fault tolerant
configurations, please refer to the Windows NT Server 4.0 Resource Kit.

For information about specific platforms, see the following.
Recovering the dell PowerEdge 6100/200 with RAID
Note: This section discusses how to restore a Dell computer. The general
procedure is the same for any computer that requires the use of third-party
drivers.
To recover a Dell PowerEdge 6100/200 with RAID configuration is different
from recovering a regular computer with one hard drive.
To load Windows on this type of computer, you must load the PowerRaid II
driver manually, which is not bundled with the Windows operating system.
Load the Adaptec controller driver manually after loading the PowerRaid II
driver. Failure to follow these steps results in Windows being unable to
recognize any hard drive partitions on the computer.
Use the following steps with your IDR recovery diskette set
1 When the Windows blue Setup screen appears after booting with the IDR
boot diskette, press and hold down the F6 key.
2 Windows prompts for IDR diskette 2.
3 Insert IDR diskette 2 and press and hold the F6 key again.
After the additional drivers are loaded, a Setup screen appears that lets you
specify additional devices.
4 Release the F6 key and press the S key.
5 Follow the on-screen instructions to load the PowerEdge RAID II controller
software.
6 After the PowerEdge RAID software is loaded, press S again to specify
loading another device.
7 Follow the on-screen instructions to load the Adaptec controller software
next.
8 After both pieces of third-party software are loaded, press Enter and
proceed as normal to recover the computer.
Recovering IBM computers

If the drive that contains the computer’s configuration information fails,
reconfigure the computer before you recover it. Use the IBM Reference Diskette
to reconfigure the computer.
IDR frequently asked questions
Recovering Compaq computers

If the drive that contains the System Configuration Partition fails, IDR recreates
the partition on the new hard disk. However, use the Compaq SmartStart
utilities to update the computer partition.

Q. Can I restore boot managers such as System Commander or OS/2 Boot
Manager with Intelligent Disaster Recovery for Windows?
A. No, because boot managers usually are installed at a very low level that
NetBackup cannot protect.
For example, the OS/2 boot manager resides in its own hard drive partition that
NetBackup cannot access. Because of the many different boot managers on the
market, an IDR restore may render the computer unbootable. It may be
unbootable even though the operating system has been restored. In this case,
reinstalling the boot manager should fix the problem.
Q. I ran a full backup of my computer but when I run the IDR Preparation
Wizard again, I do not see a disaster recovery file. What happened?
A. For some reason, the DR file was not generated automatically.
Generate it manually as explained in “Using drfile.exe to create or update a DR
file” on page 260.
Q. Why does the recovery wizard warn me that one or more of my hard drives
are smaller than the originals?
A. The minimal version of Windows that runs the recovery wizard may have
detected the hard drives in a different order than originally configured.

Be sure that the hard drive and controller configuration matches the original
configuration before a disaster occurs.
If the original configuration does not match, you may be able to control the
numbering of the hard drive. The following chart lists the order that Windows
uses to assign disk drive numbers. Keep in mind that this chart can change if
third-party drivers are used.
Windows Hard Drive Numbering Scheme
Primary IDE Master Server

Media Server
Secondary IDE Master Server

Media Server
Windows Hard Drive Numbering Scheme (continued)
SCSI Adapter 0 SCSI ID 0

SCSI ID 1
(In order of the lowest I/O port address)
...
SCSI ID 7 (or 15 is wide SCSI)
SCSI Adapter 1 SCSI ID 0

SCSI ID 1
...
SCSI ID 7 (or 15 is Wide SCSI)
SCSI Adapter n SCSI ID 0

SCSI ID 1
...
SCSI ID 7 (or 15 is Wide SCSI)
Other types of mass storage controllers are usually seen as SCSI controllers by Windows.
Note: Windows NT: If the IDR Recovery Wizard does not detect the hard drive
order, set up hard drive partitions manually. To do so, use the Windows NT Disk
Administrator option within the Disaster Recovery Wizard. Then, continue with
the automated restore of the backup media.
If the recovery wizard reports drives greater than 8 GBs as being only 8 GBs,
create bootable diskettes. To do so, enable the Use SCSI drivers currently
installed on this computer option.
Index
Symbols AUTHENTICATION_DOMAIN 33, 67
AUTHORIZATION_REQUIRED, vm.conf entry 87
.ExTeNt.nnnn files 165
AUTHORIZATION_SERVICE 34
.SeCuRiTy.nnnn files 165
auto cleaning 195
@@MaNgLeD.nnnn files 165
AUTO_PATH_CORRECTION, vm.conf entry 88
@@MaNgLeD.nnnn_Rename files 165
AUTO_UPDATE_ROBOT, vm.conf entry 88
@@MaNgLeD.nnnn_Symlink files 165
auto-populate robot 135
available_media script 171
A AVRD_PEND_DELAY, vm.conf entry 89, 218
access control
AVRD_SCAN_DELAY, vm.conf entry 89
lists (ACLs) 165
to a server or client 79
B
ACS_ vm.conf entry 83
backup selection list, AFS 242, 243
ACS_CSI_HOSTPORT, vm.conf entry 83
backup_exit_notify script 173
ACS_SEL_SOCKET, vm.conf entry 83
backup_notify script 173
ACS_SSI_HOSTNAME, vm.conf entry 84
backups
ACS_SSI_INET_PORT, vm.conf entry 84
backup_exit_notify script 173
ACS_SSI_SOCKET, vm.conf entry 85
backup_notify script 173
ACS_TCP_RPCSERVICE, vm.conf entry 85
bpend_notify script
ACS_UDP_RPCSERVICE, vm.conf entry 85
UNIX client 179
ADJ_LSM, vm.conf entry 85
Windows client 180
adjust time zone 113
bpstart_notify script
Administrator’s e-mail address property 111
UNIX client 174
Allow Backups to Span Media 221
Windows client 176
Allow media overwrite property 32
compressed 162
Allow multiple retentions per media property 33
diskfull_notify script 184
ALLOW_MEDIA_OVERWRITE 32, 69
estimating time required 165
ALLOW_MULTIPLE_RETENTIONS_PER_MEDIA 3
media requirements 171
3, 70
multiplexed 162
ALLOW_NON_RESERVED_PORTS 33
session_notify script 186
client 67
session_start_notify script 187
alternate client restores, host.xlate file 161
barcodes 140, 202, 203
Andrew File System (AFS)
boot managers and IDR 269
backup selection list 242
booting a computer
directives 242
with IDR bootable media 262
installing 241
bp.conf file 209
regular expressions 243
options 32
restores 244
personal
troubleshooting 246
for UNIX nonroot user 66, 69, 82
Announce DHCP interval property 100
for UNIX root user 66
API robots 136, 144, 203
personal file
API_BARCODE_RULES, vm.conf entry 87
272
for UNIX nonroot user 32

creating action files 108
UNIX client options 66, 111

logs 109
UNIX server options 32

logs directory 109
bpadm, using
modifying
clients
bp.conf 106
install software 126

bpend_notify_busy 110
critical policy for Disaster Recovery 123
email address to send Disaster Recovery
information 122
C
Global properties, specifying 123
catalog backups
install client software 126

backup notification script 183
location to store Disaster Recovery

offline, cold 183
information 123
changing
manual backups 125, 126

volume expiration date 138
menu overview 118

volume maximum mounts 139
NetBackup-database backup
character device 148
changing backup attributes 127

CHECK_RESTORE_CLIENT 41
manual 130
checkpoint restart
offline catalog backup 126

bp.conf entry for maximum incomplete
password to access location of Disaster
status 50
Recovery information 123

CLEAN_REQUEST_TIMEOUT, vm.conf entry 89
reports, displaying 124

cleaning
starting bpadm 118

frequency-based 196
user name to access location of Disaster

library-based 195
Recovery information 123

reactive 194
utility 118
tape 139
BPARCHIVE_POLICY 68
times allowed 197
BPARCHIVE_SCHED 68
CLIENT_CONNECT_TIMEOUT 41
BPBACKUP_POLICY 68
CLIENT_NAME 70
BPBACKUP_SCHED 69
CLIENT_PORT_WINDOW 41, 71
BPBRM_VERBOSE 35
CLIENT_PORT_WINDOW, vm.conf entry 89
BPDBJOBS_COLDEFS 36
CLIENT_READ_TIMEOUT 41, 42, 71
BPDBM_VERBOSE 38
CLIENT_RESERVED_PORT_WINDOW 43, 71
bpdynamicclient 103
clients
bpend_notify script
bp.conf options 31
UNIX client 179

changing host names 160
Windows client 180

dynamic UNIX client 103
BPEND_TIMEOUT 40
IGNORE_XATTR bp.conf entry 76
BPRD_VERBOSE 39
IGNORE_XATTR_SOLARIS bp.conf entry 76
bpstart_notify script
cluster environments 90, 217
UNIX client 174

CLUSTER_NAME, vm.conf entry 90
Windows client 176

Compaq computers, recovering with IDR 269
BPSTART_TIMEOUT 41
COMPRESS_SUFFIX 71
BPTM logging level property 40

compressed backups 162
BPTM_VERBOSE 39
CONNECT_OPTIONS 43
Busy file settings property 105, 106

CONNECT_OPTIONS, vm.conf entry 90
BUSY_FILE_NOTIFY_USER 70
control path, robotic 144
busy-file processing
crawlreleasebyname, vmoprcmd option 215
configuration overview 105

CREATE_BACKUP_VOLUMES 242
CRYPT_KEYFILE 74
273
CRYPT_LIBPATH 74
name 149
CRYPT_STRENGTH 73
no rewind device 148
robot drive number 149
robot number, controlling drive 149
D stand-alone 149
DAS_CLIENT, vm.conf entry 91

TLH information 149
DataStore volume pool 198

TLM information 149
Daylight savings time 114

type 148
DAYS_TO_KEEP_LOGS, vm.conf entry 91

update configuration 150
dbbackup_notify script 183

volume header device 148
decommission a media server 208

Dynamic host name and IP addressing 99
DEFAULT_CONNECT_OPTIONS 45
Dell PowerEdge 6100/200 with RAID
recovering with IDR 268

E
device
e-mail notifications 111
delays 167
EMM_REQUEST_TIMOUT, vm.conf entry 92
discovery 228
EMM_RETRY_COUNT, vm.conf entry 92
file permission 239

EMMSERVER 47
file, robotic 148

Enable standalone drive extension property 33, 46
DHCP server 99
ENABLE_ROBOT_AUTH, vm.conf entry 92
directives for AFS 242

ENABLE_ROBUST_LOGGING 48
DISABLE_JOB_LOGGING 46
encryption 164
DISABLE_STANDALONE_DRIVE_EXTENSIONS 46
English error log 49, 75
DISALLOW_BACKUPS_SPANNING_MEDIA 46
extended attribute files 162
DISALLOW_CLIENT_LIST_RESTORE 47
to ignore during backup 76
DISALLOW_CLIENT_RESTORE 47
ExTeNt.nnnn files 165
DISALLOW_SERVER_FILE_WRITES 75
disaster recovery
diskettes, updating 260
F
procedure 261
FAILOVER_RESTORE_MEDIA_SERVERS 48
disk administrator 267

files
disk overhead, for catalogs 171

.ExTeNt.nnnn 165
diskfull_notify script 184

.SeCuRiTy.nnnn 165
display device configuration 153

@@MaNgLeD.nnnn 165
DO_NOT_RESET_FILE_ACCESS_TIME 75
@@MaNgLeD.nnnn_Rename 165
Domain Name Service (DNS) hostnames 161

@@MaNgLeD.nnnn_Symlink 165
drfile.exe command 260

files in /usr/openv/netbackup/
drive_mount_notify script 236

bp.conf 32
drive_unmount_notify script 238

name on tpreq 236
drives
positioning on tape 237
access permission 239

FlashBackup 162
ACS information 149

FORCE_RESTORE_MEDIA_SERVER 49
adding 148
format
character device 148

description for optical 224
cleaning
optical media 143
manual 196
fragmented backups 225
operator-initiated 196
frequency-based drive cleaning 196
overview 194
configuring 144
deleting 150
274
G updating bootable media 258
updating IDR media
GENERATE_ENGLISH_LOGS 49, 75
recovery diskettes 259, 260
Global logging level property 40, 64
using drfile.exe 260
GNU tar 162
when to update 258
using boot managers 269
H Windows
host names
disk administrator 264
changing client name 160

editions supported 248
changing server name 160

setup 263
client peername 159

wizards
correct use 158

disaster recovery 261
robotic control selection 145, 148

IDR preparation 252
short 160
INVENTORY_FILTER, vm.conf entry 92, 93
host.xlate file and alternate client restores 161
K
I
KEEP_DATABASE_COMM_FILE 76
IBM
KEEP_LOGS_DAYS 76
computers, recovering with IDR 268
device number 149

L
IGNORE_XATTR 76
library-based cleaning 195
INCOMPLETE_JOB_CLEAN_INTERVAL 50
LIMIT_BANDWIDTH 50
INFORMIX_HOME 76
LIST_FILES_TIMEOUT 77
INITIAL_BROWSE_SEARCH_LIMIT 50
LOCKED_FILE_ACTION 77
set on UNIX client 76
Logging
inode change time 80
host properties
Intelligent Disaster Recovery (IDR)
BPBRM logging level 35
bootable media
BPDBM logging level 38
choosing type 253
BPRD logging level 39
creating CD image 256
BPTM logging level 39
preparing 252
Global logging level 64
configuration 251
logs, retaining database extension logs 76
custom setup, when to use 263
diskettes
preparing 252
M
updating 259
mail notifications, USEMAIL on UNIX clients 81
diskettes, updating 260

mail_dr_info.sh 184
DR files
manual backups, with bpadm 125, 126
obtaining from server 251

MAP_CONTINUE_TIMEOUT, vm.conf entry 94
overview 250
MAP_ID, vm.conf entry 93
update with drfile.exe 260

maximum barcode lengths 202
frequently asked questions 269

maximum mounts
hard disk partition changes 264

change volumes 139
hard drive partition, altering sizes 267

Media
overview 250
host properties
preparation wizard 252

Allow media overwrite 32
recovery wizard 261

Allow multiple retentions per media 33
requirements for using 249

media
supported Windows editions 248
275
configuring 132
NBRB_REEVAL_PERIOD 56
determining requirements 171

NBRB_RETRY_DELAY_AFTER_EMM_ERR 56
formats 223
NDMP 162, 217
ID generation rules 135, 206

NDMP host credentials 152
pool 197
NetBackup Access Control (NBAC)
selection algorithm 220, 221

use of 92, 96
server register 29
NetBackup for Informix 76
spanning 221, 222

NetBackup Vault 138
using tar to read images 162

network transfer rate 167
Media ID prefix property 53

NFS_ACCESS_TIMEOUT 78
Media Manager
notification scripts 172
best practices 187
configuration file 82
security 97
O
Media request delay property 54
online help for tpconfig 147
Media unmount delay property 54

open files (see busy-file processing)
MEDIA_ID_BARCODE_CHARS, vm.conf entry 94

optical disk
MEDIA_ID_PREFIX 53
format 224
MEDIA_ID_PREFIX, vm.conf entry 95

format and label 143
MEDIA_REQUEST_DELAY 54
usage 238
MEDIA_SERVER 54, 77
OS/2, boot manager and IDR 269
MEDIA_UNMOUNT_DELAY 54
Overwrite existing files property 62
MEGABYTES_OF_MEMORY 78
Overwrite existing files restore option 63
MM_SERVER_NAME, vm.conf entry 95
move volumes
P
multiple volumes 137
peername, client 159
single volume 137

permissions, for device access 239
MPX_RESTORE_DELAY 54
positioning tape files 237
multiple servers 24
PREFERRED_GROUP, vm.conf entry 96
multiplexing (MPX)
PREVENT_MEDIA_REMOVAL, vm.conf entry 96
backups 225
printing device configuration 153
demultiplexing 23
Maximum jobs per client property 22
recovering backups 162

R
schedule media multiplexing 19
RANDOM_PORTS 57
storage unit max per drive 19

set use on client 78
tape format 225

RANDOM_PORTS, vm.conf entry 96
Must use local drive property 55

raw partitions 162
MUST_USE_LOCAL_DRIVE 55
RE_READ_INTERVAL 57
reactive cleaning 195
reading tape files 237
N reconfiguring devices in a shared drive
named data streams

configuration 206
to ignore during backups 76

register a media server 29
VxFS 162
regular expressions, AFS file list 243
NBRB_CLEANUP_OBSOLETE_DBINFO 55
remove a server from a configuration 208
NBRB_ENABLE_OPTIMIZATIONS 55
REMOVE_BACKUP_VOLUMES 243
NBRB_FORCE_FULL_EVAL 55
removing tape files 237
NBRB_MPX_GROUP_UNLOAD_DELAY 56
replacing a device in a shared drive
NBRB_REEVAL_PENDING 56
276
configuration 206
restore_notify 172
requests
session_notify 172
user tape 235

session_start_notify 172
REQUIRED_INTERFACE 57, 59
userreq_notify 172
set on client 79
SCSI persistent reserve 211
REQUIRED_INTERFACE, vm.conf entry 97

SCSI reserve/release
RESERVATION CONFLICT status 215

break a reservation 214, 216
restore_notify script 186

error recovery 215
RESTORE_RETRIES 78
limitations 217, 218
restores
overview 212
adjust time zone for 113

PEND status 215
AFS clients 244

requirements 216
notes on AFS 245

RESERVATION CONFLICT 214, 215
restore_notify script 186

SeCuRiTy.nnnn files 165
retrying 78
SERVER 54
rewind
bp.conf option on client 79
devices, none 148

SERVER bp.conf entry 59
tape files 237

Server list
robotic cleaning 195

on UNIX client 79, 80
robots
server, NetBackup
adding 147
controlling access 79
configuring 144
SERVER, vm.conf entry 97
control host 145, 148

SERVER_CONNECT_TIMEOUT 62
deleting 151
SERVER_PORT_WINDOW 61, 79
device file 148

SERVER_RESERVED_PORT_WINDOW 61
drive 149
servers
number 148, 149

changing host names 160
type 148
NetBackup
update configuration 149

configuring bp.conf file 32
Robust logging 48
master 25
media 25
multiple 24
S session_notify script 186
schedules
session_start_notify script 187
default for user backups 69

SKIP_RESTORE_TO_SYMLINK_DIR 62
how processed 169

SKIP_SMALL_VOLUMES 243
scratch pool 200

Solaris
scripts
extended attributes 162
available_media 171
spanning media 221, 222, 225
backup_exit_notify 172
SSO, vm.conf entries 98
backup_notify 172
SSO_DA_REREGISTER_INTERVAL, vm.conf
bpend_notify 172
entry 98
bpstart_notify 172, 174, 176

SSO_DA_RETRY_TIMEOUT, vm.conf entry 98
dbbackup_notify 172
SSO_HOST_NAME, vm.conf entry 98
diskfull_notify 172
stand-alone drive
drive_mount_notify 236
extensions, disabling 222
drive_unmount_notify 238
tpconfig 149
notification 172
subnets, address formats 51
parent_end_notify 172
SYBASE_HOME 80
parent_start_notify 172
277
Symantec Product Authentication and

online help 147
Authorization
overview 144
AUTHENTICATION_DOMAIN 33
printing device configuration 153
AUTHORIZATION_SERVICE 34
starting 146
System Commander and IDR 269

stopping 146
update drive configuration 150
update robot configuration 149
T tpreq, requesting tapes 235
tape
tpunmount, removing tape files 237
overhead, for catalogs 171

transfer rate 166, 167
spanning 221, 223

troubleshooting AFS backups 246
tape configuration utility (see tpconfig)
tape format
fragmented 225
U
multiplexed 225
UNLINK_ON_OVERWRITE 63
non-QIC 224
USE_CTIME_FOR_INCREMENTALS 80
QIC/WORM 224
USE_FILE_CHG_LOG 80
spanned tapes 225

USE_VXSS 64, 80
TapeAlert 190, 194

USEMAIL on UNIX clients 81
log codes 191

user
requirements 191
access to devices 239
tapes and tape files

tape requests 235
density 236
userreq_notify script 187
file name 236
positioning tape file 237
reading tape files 237
removing tape files 237

VERBOSE 81
requesting tapes 235

VERBOSE bp.conf entry 64
rewinding 237
VERBOSE, vm.conf entry 99
using optical disk 238

Veritas Security Subsystem (VxSS)
volume pool assignment 236

AUTHENTICATION_DOMAIN 67
writing tape files 237

USE_VXSS bp.conf entry 80
tar
VXSS_NETWORK bp.conf entry 81
GNU 162
vm.conf file
to read backup images 162

ACS_ entries 83
time zones
ACS_CSI_HOSTPORT entries 83
adjustment for restores 113

ACS_SEL_SOCKET entries 83
setting Daylight savings time 114

ACS_SSI_HOSTNAME entries 84
timeout
ACS_SSI_INET_PORT entries 84
bpend 40
ACS_SSI_SOCKET entries 85
client read 42, 71

ACS_TCP_RPCSERVICE entries 85
TLH_ vm.conf entry 98

ACS_UDP_RPCSERVICE entries 85
TLM_ vm.conf entry 99

ADJ_LSM entries 85
tpconfig
API_BARCODE_RULES entries 87
adding drive 148

AUTHORIZATION_REQUIRED entries 87
adding NDMP host credentials 152

AUTO_PATH_CORRECTION entries 88
adding robot 147

AUTO_UPDATE_ROBOTentries 88
deleting drive 150

AVRD_PEND_DELAY entries 89
deleting robots 151

AVRD_SCAN_DELAY entries 89
menus 146
CLEAN_REQUEST_TIMEOUT entries 89
278
CLIENT_PORT_WINDOW entries 89 in AFS file list 243

CLUSTER_NAME entries 90 wizards
CONNECT_OPTIONS entries 90 disaster recovery 261
DAS_CLIENT entries 91 IDR preparation 252
DAYS_TO_KEEP_LOGS entries 91 worklist, prioritizing 170
ENABLE_ROBOT_AUTH entries 92 writing tape files 237
INVENTORY_FILTER entries 92, 93
MAP_CONTINUE_TIMEOUT entries 94
MAP_ID entries 93
MEDIA_ID_BARCODE_CHARS entries 94
MEDIA_ID_PREFIX entries 95
MM_SERVER_NAMEentries 95
overview 82
PREFERRED_GROUP entries 96
PREVENT_MEDIA_REMOVAL entries 96
RANDOM_PORTS entries 96
REQUIRED_INTERFACE entries 97
SERVER entries 97
SSO_DA_REREGISTER_INTERVAL entries 98
SSO_DA_RETRY_TIMEOUT entries 98
SSO_HOST_NAME entries 98
TLH_ entries 98
TLM_ entries 99
VERBOSE entries 99
vmadm
changing
volume expiration date 138
volume maximum mounts 139
command 132
format optical disk 143
moving volumes (see move volumes)
stopping vmd 133
vmd command 133
volume
group
rules for assigning 198
pool
configuring a scratch pool 200
overview 197
volume header device 148
volumes 137, 139
adding 135
VxFS
extent attributes 165
named data streams 162
VXSS_NETWORK 64, 81
W
wildcard characters

6.5 Admin Guide 2 (Unix)

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

6.5 Admin Guide 2 (Unix)

Caricato da

Copyright:

Formati disponibili

Veritas NetBackup™

Administrator’s Guide, Volume II

for UNIX and Linux

THIS DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED

The Licensed Software and Documentation are deemed to be “commercial computer

Printed in the United States of America.

Third-party software may be recommended, distributed, embedded, or bundled

Licensing and registration

Chapter 1 Additional configuration

When to use multiplexing ...........................................................................18

How to configure multiplexing ..................................................................18

Maximum streams per drive for a storage unit ...............................19

Media multiplexing for a schedule ....................................................19

Other configuration settings to consider using multiplexing ......22

Using multiple NetBackup master servers ......................................................24

Using multiple media servers with one master server ..................................25

Software on each server ..............................................................................26

NetBackup catalogs .....................................................................................27

Adding a media server .........................................................................................27

Registering a media server .........................................................................29

NetBackup configuration options .....................................................................31

Syntax rules for bp.conf options ...............................................................31

bp.conf options for servers .........................................................................32

bp.conf options for UNIX clients ............................................................... 66

UNIX client examples .................................................................................. 82

Example /usr/openv/netbackup/bp.conf file .................................. 82

Example $HOME/bp.conf file ............................................................ 82

vm.conf options for media servers ........................................................... 82

ACS_TCP_RPCSERVICE / ACS_UDP_RPCSERVICE ........................ 85

Example vm.conf file ...........................................................................99

Dynamic host name and IP addressing ............................................................99

Setting up dynamic IP addresses and host names ................................101

Configuring the NetBackup master server ............................................102

Configuring a dynamic Microsoft Windows client ...............................103

Configuring a dynamic UNIX NetBackup client ....................................103

Busy file processing (UNIX clients only) ........................................................105

Getting started ...........................................................................................106

Modifying bp.conf to configure busy file processing ...........................106

Creating action files ...................................................................................108

Logs directory .............................................................................................109

Modifying bpend_notify_busy .................................................................110

Configuring email notifications ......................................................................111

Specifying the locale of the NetBackup installation ....................................112

Adjusting time zones in the NetBackup-Java console ..................................113

Chapter 2 Menu user interfaces

Data classification management .............................................................118

Defining and managing storage unit groups .................................119

Defining and managing policies ..............................................................120

Configuring an online catalog backup ............................................120

Defining NetBackup global attributes ....................................................123

Defining and managing Fibre Channel transport .................................124

Displaying reports .....................................................................................124

Performing manual backups ....................................................................125

Performing special actions .......................................................................126

Install NetBackup on all trusting clients ........................................126

Perform an offline catalog backup ..................................................126

Modifying offline catalog backup settings .....................................127

Performing manual offline catalog backups ..................................130

Redefining retention levels ..............................................................131

Defining and managing server groups ...................................................132

Using the vmadm media management utility ...............................................132

Starting vmadm ..........................................................................................132

Starting and stopping vmd .......................................................................133