netbackup_administrator guide 2
TRANSCRIPT
-
8/14/2019 NetBackup_Administrator Guide 2
1/176
Veritas NetBackup Administrators Guide, Volume II
for Windows
Release 6.5
12308282
-
8/14/2019 NetBackup_Administrator Guide 2
2/176
VeritasNetBackup Administrators Guide, Volume IICopyright 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 betrademarks 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 documentmay 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 IMPLIEDCONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIEDWARRANTY 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 SHALLNOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTIONWITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THEINFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGEWITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computersoftware and commercial computer software documentation as defined in FARSections 12.212 and DFARS Section 227.7202.
Symantec Corporation20330 Stevens Creek Blvd.Cupertino, CA 95014www.symantec.com
Printed in the United States of America.
http://www.symantec.com/http://www.symantec.com/ -
8/14/2019 NetBackup_Administrator Guide 2
3/176
Third-party legal notices
Third-party software may be recommended, distributed, embedded, or bundledwith this Veritas product. Such third-party software is licensed separately by itscopyright holder. All third-party copyrights associated with this product arelisted in the accompanying release notes.Windows is a registered trademark of Microsoft Corporation.
Licensing and registrationVeritas NetBackup is a licensed product. See the NetBackup Installation Guide for license installation instructions.
Technical supportFor technical assistance, visit http://entsupport.symantec.com and select phoneor email support. Use the Knowledge Base search feature to access resourcessuch as TechNotes, product alerts, software downloads, hardware compatibilitylists, and our customer email notification service.
http://entsupport.symantec.com/http://entsupport.symantec.com/ -
8/14/2019 NetBackup_Administrator Guide 2
4/176
-
8/14/2019 NetBackup_Administrator Guide 2
5/176
Contents
Chapter 1 Additional configurationMultiplexing .........................................................................................................13
When to use multiplexing ...........................................................................14How to configure multiplexing ..................................................................14
Maximum streams per drive for a storage unit ...............................15Media multiplexing for a schedule ....................................................15Other configuration settings to consider using multiplexing ......18
Demultiplexing .............................................................................................19Using multiple NetBackup master servers ......................................................20Using multiple media servers with one master server ..................................21
Software on each server ..............................................................................22NetBackup catalogs .....................................................................................23
Adding a media server .........................................................................................23Registering a media server ......................................................................... 25
NetBackup configuration options .....................................................................27NetBackup administration options ...........................................................27
NBRB_CLEANUP_OBSOLETE_DBINFO ............................................28
NBRB_ENABLE_OPTIMIZATIONS ....................................................28NBRB_FORCE_FULL_EVAL ................................................................28NBRB_REEVAL_PENDING ..................................................................28NBRB_REEVAL_PERIOD .....................................................................28NBRB_RETRY_DELAY_AFTER_EMM_ERR ...................................... 29NBRB_MPX_GROUP_UNLOAD_DELAY ...........................................29REQUIRED_NETWORK .......................................................................29
vm.conf options for media servers ............................................................ 30
ACS_mediatype ......................................................................................30 ADJ_LSM ................................................................................................30API_BARCODE_RULES ........................................................................31AUTHORIZATION_REQUIRED ..........................................................32AUTO_PATH_CORRECTION ..............................................................32AUTO_UPDATE_ROBOT .....................................................................33AVRD_PEND_DELAY ...........................................................................33AVRD_SCAN_DELAY ...........................................................................33
CLEAN_REQUEST_TIMEOUT ............................................................34CLIENT_PORT_WINDOW ...................................................................34CLUSTER_NAME ..................................................................................34
-
8/14/2019 NetBackup_Administrator Guide 2
6/176
6
CONNECT_OPTIONS ........................................................................... 35
DAS_CLIENT ......................................................................................... 35DAYS_TO_KEEP_LOGS ....................................................................... 36EMM_RETRY_COUNT ......................................................................... 36EMM_CONNECT_TIMOUT ................................................................. 36EMM_REQUEST_TIMOUT ................................................................. 36ENABLE_ROBOT_AUTH ..................................................................... 37INVENTORY_FILTER .......................................................................... 37MAP_ID .................................................................................................. 37
MAP_CONTINUE_TIMEOUT ............................................................. 38MEDIA_ID_BARCODE_CHARS .......................................................... 38MEDIA_ID_PREFIX .............................................................................. 39MM_SERVER_NAME ........................................................................... 39PREFERRED_GROUP .......................................................................... 40PREVENT_MEDIA_REMOVAL ........................................................... 40RANDOM_PORTS ................................................................................ 40REQUIRED_INTERFACE ..................................................................... 41SERVER ................................................................................................. 41SSO_DA_REREGISTER_INTERVAL .................................................. 42SSO_DA_RETRY_TIMEOUT ............................................................... 42SSO_HOST_NAME ............................................................................... 43TLH_mediatype .................................................................................... 43TLM_mediatype ................................................................................... 43VERBOSE ............................................................................................... 43Example vm.conf file ........................................................................... 43
Direct I/O for backups ......................................................................................... 44Disabling direct I/O ..................................................................................... 45
Dynamic host name and IP addressing ............................................................ 45Setting up dynamic IP addresses and host names .................................. 46Configuring the NetBackup master server .............................................. 47Configuring a dynamic Microsoft Windows client ................................. 49Configuring a dynamic UNIX NetBackup client ..................................... 49
Configuring email notifications ........................................................................ 50Specifying the locale of the NetBackup installation ...................................... 51
Chapter 2 Reference topicsRules for using host names in NetBackup ....................................................... 54
Qualifying host names ................................................................................ 54How NetBackup uses host names .............................................................. 54
Policy configuration ............................................................................ 55
Image catalog ....................................................................................... 55Error catalog ......................................................................................... 55Catalog backup information ............................................................... 55
-
8/14/2019 NetBackup_Administrator Guide 2
7/176
7
How to update NetBackup after a host name changes ...........................56
Special considerations for Domain Name Service (DNS) .......................56Reading backup images with tar .......................................................................58
Effects of a non-NetBackup tar .......................................................... 58Factors that affect backup time ......................................................................... 59
Total data ......................................................................................................59Transfer rate .................................................................................................59Device delays ................................................................................................60
Determining NetBackup transfer rate .............................................................. 60
Network transfer rate ..................................................................................60Network transfer plus end-of-backup-processing rate ......... .................61Total transfer rate .......................................................................................61Examples .......................................................................................................61Using the system monitor ..........................................................................62
How NetBackup builds a worklist ......................................................................65Building the worklist (Queue) ....................................................................65To prioritize queued jobs ............................................................................66
Determining backup media requirements .......................................................67NetBackup notify scripts ....................................................................................68
backup_notify.cmd ..............................................................................69backup_exit_notify.cmd ......................................................................69bpstart_notify (UNIX clients only) ....................................................70bpstart_notify.bat (Microsoft Windows clients only) ....................72bpend_notify (UNIX clients only) ......................................................74bpend_notify.bat (Microsoft Windows clients only) ......................76dbbackup_notify.cmd ..........................................................................78diskfull_notify.cmd ..............................................................................79mail_dr_info.cmd .................................................................................80nbmail.cmd ............................................................................................81parent_end_notify.cmd .......................................................................81parent_start_notify.cmd .....................................................................82restore_notify.cmd ...............................................................................82session_notify.cmd ..............................................................................83session_start_notify.cmd ....................................................................83userreq_notify.cmd ..............................................................................83
Media and device management best practices ................................................84General practices .........................................................................................84Media management .....................................................................................85Device management ....................................................................................85Performance and troubleshooting ............................................................86
Using TapeAlert ...................................................................................................87Requirements for using TapeAlert ............................................................87TapeAlert log codes .....................................................................................87
-
8/14/2019 NetBackup_Administrator Guide 2
8/176
8
Drive cleaning overview ..................................................................................... 90
Reactive cleaning (TapeAlert) .................................................................... 91TapeAlert cleaning .............................................................................. 91TapeAlert and frequency-based cleaning ........................................ 91
Library-based cleaning ............................................................................... 91Frequency-based cleaning .......................................................................... 92
Frequency-based cleaning limitations ............................................. 92Operator-initiated cleaning ....................................................................... 93Using a cleaning tape .................................................................................. 93
Volume pool and volume group overview ....................................................... 93Volume pools ................................................................................................ 94Volume groups ............................................................................................. 94
Rules for assigning volume groups ................................................... 94Volume pool and volume group example ................................................. 95Scratch volume pools .................................................................................. 96
Scratch pool example .......................................................................... 96Scratch pool usage ............................................................................... 97
Barcode overview ................................................................................................. 98Barcode advantages ..................................................................................... 98Barcode best practices ................................................................................ 98Barcode rules ................................................................................................ 99
NetBackup actions for barcodes ........................................................ 99Checking barcodes .............................................................................100Example barcode rules ......................................................................100
Media ID generation rules ........................................................................102Controlling hardware compression ................................................................102Changing your hardware configuration .........................................................102
Replacing devices .......................................................................................102Decommissioning a media server ...........................................................104
How NetBackup selects drives .........................................................................106How NetBackup reserves drives ......................................................................107
SCSI persistent reserve process ..............................................................108SCSI persistent reserve commands ................................................. 109SCSI persistent reserve conflicts ..................................................... 109
SPC-2 SCSI reserve process ......................................................................109SPC-2 SCSI reserve commands ........................................................ 110SCSI reservation conflicts ................................................................111Forcing a release ................................................................................111Breaking a reservation ......................................................................112
SCSI reserve requirements and limitations ...........................................112SCSI reservation logging ..........................................................................114Server operating system limitations ...................................................... 114Checking for data loss ...............................................................................114
-
8/14/2019 NetBackup_Administrator Guide 2
9/176
9
Possible data loss causes ...................................................................114
Checking for tape and driver configuration errors ..............................115Common configuration problems ....................................................115
Configuring SCSI reserve ..........................................................................115How NetBackup selects media .........................................................................116
Selecting media in robots .........................................................................116Spanning media ..................................................................................117
Selecting media in stand-alone drives ....................................................117Media selection using stand-alone drive extensions ....................118
Media formats ....................................................................................................120Standard tape format ................................................................................120QIC/WORM tape format ............................................................................120Optical media format .................................................................................121Fragmented backups .................................................................................121Multiplexing format ..................................................................................121Spanning tapes ...........................................................................................122
Media Manager commands ..............................................................................122Device discovery overview ...............................................................................124
Device serialization ...................................................................................124Devices that can be discovered ................................................................125Device discovery in NetBackup .................. ..............................................125Device discovery in the Device Configuration Wizard .........................126Device discovery and shared tape drives ...............................................126Viewing and verifying the device configuration ...................................127Adding devices without discovery ...........................................................127Device mapping file ...................................................................................128
Correlating tape drives to device files or addresses .....................................128Correlating devices and device files on UNIX hosts .............................128Correlating devices and names on Windows hosts ..............................130
Chapter 3 UNIX reference topicsCross mount points ............................................................................................134
Exclude and include lists on UNIX clients .....................................................136Creating an exclude list on a UNIX client ......................................136Creating an include list on a UNIX client .......................................139
Schedules for user backups or archives .........................................................140
Chapter 4 Using NetBackup with AFSInstallation ..........................................................................................................141
System requirements ................................................................................141Server and client installation ...................................................................141
Configuration .....................................................................................................141
-
8/14/2019 NetBackup_Administrator Guide 2
10/176
10
General policy attributes ..........................................................................142
Client list .....................................................................................................142Backup selections ......................................................................................142Backup selection list directives ...............................................................142Regular expressions ..................................................................................143Exclude and include lists ..........................................................................144
Backups and restores ........................................................................................144Backups .......................................................................................................144
Automatic backup ..............................................................................144
Manual backup ...................................................................................144Restores .......................................................................................................144
Restore from the NetBackup for AFS client .................................. 144Restore from the NetBackup master server ..................................145Notes about restores ..........................................................................145
Troubleshooting .................................................................................................145Troubleshooting backups .........................................................................146Troubleshooting restores .........................................................................146
Chapter 5 Intelligent Disaster RecoveryChanges for NetBackup 6.0 and later .............................................................148Supported Windows editions ........................................................................... 148Requirements for IDR .......................................................................................149Overview of IDR use ..........................................................................................150About the DR files ..............................................................................................150
Configuring NetBackup policies for IDR ........................................................ 151Backing up the protected computer ................................................................ 152Creating IDR media ...........................................................................................152
Choosing the bootable media ...................................................................153Creating bootable diskettes ......................................................................154
To modify diskette sets for use with multiple Windows 2000 computers155
Creating a bootable CD image ..................................................................156
Creating IDR diskettes ..............................................................................157Updating IDR media .......................................................................................... 158
Updating a bootable CD ............................................................................158Updating bootable diskettes ....................................................................159Updating IDR diskettes only ....................................................................160Using drfile.exe to create or update a DR file .......................................160
Recovering your computer ...............................................................................161Step 1: Boot your computer ......................................................................162
Step 2: Windows setup in IDR recovery .................................................163Step 3: Disaster recovery wizard .............................................................164Notes on altering hard drive partition sizes ..........................................167
-
8/14/2019 NetBackup_Administrator Guide 2
11/176
11
Notes on recovering specific platforms ..........................................................167
Recovering the dell PowerEdge 6100/200 with RAID ..........................168Recovering IBM computers ......................................................................168Recovering Compaq computers ...............................................................169
IDR frequently asked questions ......................................................................169
-
8/14/2019 NetBackup_Administrator Guide 2
12/176
12
-
8/14/2019 NetBackup_Administrator Guide 2
13/176
Chapter 1
Additional configuration
This chapter explains settings that, in most instances, are optional. The sectionsin this chapter include the following:
Multiplexing on page 13
Using multiple NetBackup master servers on page 20
Using multiple media servers with one master server on page 21
Adding a media server on page 23
NetBackup configuration options on page 27
Direct I/O for backups on page 44
Dynamic host name and IP addressing on page 45
Configuring email notifications on page 50
Specifying the locale of the NetBackup installation on page 51
MultiplexingNetBackup multiplexing sends concurrent backups from one or several clients
to a single storage device. NetBackup multiplexes the backups sequentially ontothe media. Multiplexed and unmultiplexed backups can reside on the samevolume. Separate volume pools or media IDs are not necessary.
-
8/14/2019 NetBackup_Administrator Guide 2
14/176
14 Additional configurationMultiplexing
No special action is required to restore a multiplexed backup. NetBackup finds
the media and restores the requested backup.
Clients
Disk Server
Removable media ormagnetic disk
Disk
Disk
When to use multiplexingMultiplexing is generally used to reduce the amount of time that is required tocomplete backups. The performance in the following situations would beimproved 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 toproviding parallel data streams, multiplexing reduces the time each jobwaits for a device to become available. Therefore, the storage device transferrate is maximized.
Multiplexing reduces performance on restores because it uses extra time to readthe images.
Note: To reduce the impact of multiplexing on restore times, set the storage unitmaximum fragment size to a value smaller than the largest allowed value.
How to configure multiplexingMultiplexing must be set in two places in the NetBackup configuration:
-
8/14/2019 NetBackup_Administrator Guide 2
15/176
-
8/14/2019 NetBackup_Administrator Guide 2
16/176
16 Additional configurationMultiplexing
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 schedules Media Multiplexing setting.
If the limit is reached for a drive, NetBackup sends jobs to other drives. Inthe following figure, when the Schedule A limit is reached on Drive 1,NetBackup adds Schedule A jobs to Drive 2.
The storage units 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. Shadednumbers denote job completion. For example, 1 denotes the start of jobA1 on Drive 1.
9 denotes the completion of job A1 on Drive 1.
-
8/14/2019 NetBackup_Administrator Guide 2
17/176
17Additional configurationMultiplexing
Figure 1-1 Multiplexing and schedules
Schedule A Schedule BMedia Multiplexing per drive = 2 Media Multiplexing per drive = 4
Storage Unitdog Max mpx per drive = 4 fox
cat
1
2 10
3
4
11
13
9 5
6
12A1 B1
A2
A5
Drive 1B2
A3 B3
Drive 2
A4 B4
7
8
otter
Assume schedule A begins first (note that the schedules can be in the same or in differentpolicies). Also, assume that Allow Multiple Data Streams is enabled, so a client can have multipledata streams.
Jobs A1 and A2 from client dog start on drive 1. Schedule A Media Multiplexing limit of 2is reached for this drive.
Jobs A3 and A4 from client cat start on drive 2. Schedule A Media Multiplexing limit of 2 isreached for this drive.
1 2
3 4
5 6
7 8
9 10
1211
13
Jobs B1 and B2 for client fox start on drive 1. Storage unit max mpx is reached for thisdrive.
Jobs B3 and B4 from client otter start on drive 2. All jobs are now running for schedule B.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 continue to run. Schedule A Media Multiplexing limit of 2 prevents job A5 from starting on
drive 1.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 AMedia Multiplexing limit of 2 prevents job A5 from starting on Drive 2. Therefore, job A5starts on Drive 1. NetBackup attempts to add multiplexed jobs to drives that already usemultiplexing. If multiplexed jobs are confined to specific drives, other drives are availablefor non-multiplexed jobs.
-
8/14/2019 NetBackup_Administrator Guide 2
18/176
18 Additional configurationMultiplexing
Note: If the backup window closes before NetBackup can start all the jobs in amultiplexing set, NetBackup completes only the jobs that have started. Forexample, Figure 1-1 on page 17 assumes that the Activity Monitor shows A1through A5 as queued and active. If only A1 and A2 start before the windowcloses, NetBackup does not perform the other jobs that are in the set. If thewindow closes before any jobs have started, then only the first queued andactive job starts and completes. (A1 in this example.)
Other configuration settings to consider using multiplexing
Limit jobs per policySet Limit Jobs Per Policy high enough to support the specified level of multiplexing.
For more information, see Limit jobs per policy on page 104 in the NetBackup Administrators Guide, Volume I .
Maximum jobs per clientThe Maximum Jobs Per Client property limits the number of backup jobs thatcan run concurrently on any NetBackup client.
Usually, the client setting does not affect multiplexing. However, consider a casewhere jobs from different schedules on the same client go to the same storageunit. In this case, the maximum number of jobs that are permitted on the clientwould be reached before the multiplexing limit is reached for the storage unit.When the maximum number of jobs on the client is reached, it preventsNetBackup from fully using the storage units multiplexing capabilities.
Maximum Jobs Per Client appears on the Global properties dialog box.
Maximum jobs this clientYou can also set the maximum number of jobs that are allowed on a specificclient without affecting other clients.
For more information, see Maximum data streams on page 386 in theNetBackup Administrators Guide, Volume I .
MPX restore delayThe Delay On Multiplexed Restores property applies to multiplexed restores.The property specifies how long the server waits for additional restore requestsof files and raw partitions in a set of multiplexed images on the same tape. DelayOn Multiplexed Restores appears on the General Server properties dialog box.
http://../nbu_sa_win_print_I/wn_pol_print.pdfhttp://../nbu_sa_win_print_I/wn_pol_print.pdfhttp://../nbu_sa_win_print_I/wn_pol_print.pdfhttp://../nbu_sa_win_print_I/wn_host_print.pdfhttp://../nbu_sa_win_print_I/wn_host_print.pdfhttp://../nbu_sa_win_print_I/wn_host_print.pdfhttp://../nbu_sa_win_print_I/wn_host_print.pdfhttp://../nbu_sa_win_print_I/wn_pol_print.pdf -
8/14/2019 NetBackup_Administrator Guide 2
19/176
19Additional configurationMultiplexing
DemultiplexingDemultiplexing speeds up future restores and is useful for creating a copy foroff-site storage. Use duplication to demultiplex a backup.
Duplication allows one multiplexed backup at one time to be copied from thesource media to the target media. When duplication is complete, the targetcontains a single demultiplexed copy of each duplicated backup. (The target canalso contain other backups.) The duplicate copy can be made into the primarycopy. 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 NetBackupAdministration Console, do not include the -mpx option on that command.
-
8/14/2019 NetBackup_Administrator Guide 2
20/176
20 Additional configurationUsing multiple NetBackup master servers
Using multiple NetBackup master serversFor a large site, you can use multiple NetBackup master servers to optimize thebackup loads. You divide the clients between the servers as necessary. Thefollowing figure shows a multiple-server configuration where the two sets of networks (A1/A2 and B1/B2) each have enough clients to justify separateservers. In this environment, the two NetBackup server configurations arecompletely independent. You can also create a configuration where one server isthe master and the other is a media server.
Workstations
Workstations
Workstations
Workstations
Network A1
Network A2
Network B1
Network B2
MassStorage
MassStorage
Router
NetBackupMaster Server A
NetBackupMaster Server B
-
8/14/2019 NetBackup_Administrator Guide 2
21/176
21Additional configurationUsing multiple media servers with one master server
Using multiple media servers with one masterserver
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 removablemedia. They may have peripheral devices to provide additional storage.
Multiple protected NetBackup clients, which send their data to the mediaservers.
A protection domain refers collectively to the NetBackup master server, itsNetBackup media servers, and its NetBackup clients. In a group of NetBackupservers, a client can have backups directed to any device on any server in thegroup.
A common alternative strategy is to install extra peripherals on the clients thatproduce large amounts of data. The master server directs the data from theclient to the clients peripherals, which reduces network traffic because the datadoes not traverse the network. This strategy also distributes the backup loadbetween 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.
-
8/14/2019 NetBackup_Administrator Guide 2
22/176
22 Additional configurationUsing 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 moredetails on master and media servers and a procedure to configure them.
StorageDevice
Storage
Device
NetBackup Catalogs
Master Server
Remote AdminConsole*
User Interface (BAR)
Storage
Device
Remote AdminConsole*
User Interface
NetBackup
Media Server
NetBackup
Media Server
NetBackupClient
User Interface (BAR)
AdministrationInterface*
AdministrationInterface*
User Interface (BAR)
Image database
Configuration files
Information inrelational databases
(about devices,volumes)
* You can also use the Backup, Archive, and Restore userinterface from a Windows client that has the RemoteAdministration Console installed.
Software on each server Applies to NetBackup Enterprise Server only.
Install NetBackup server software on each NetBackup server that has aperipheral that you want to include in a storage unit. The NetBackup installationprogram has choices for master and media server installation.
-
8/14/2019 NetBackup_Administrator Guide 2
23/176
23Additional configurationAdding a media server
NetBackup catalogs Applies to NetBackup Enterprise Server only.
The master server is the default location for the NetBackup catalogs. Thecatalogs include the media and the volume database (emm_data.db). The volumedatabase contains the media usage information and the volume informationthat are used during the backups.
Adding a media serverThe following section applies to NetBackup Enterprise Server only.
Use the following procedure to add a media server to an existing NetBackupenvironment.
Note: The NetBackup Enterprise Media Manager service must be active whenyou add a media server, configure devices and volumes, and backup or restoreclients.
To add a media server
1 On the new media server host, attach the devices and install any softwarethat is required to drive the storage devices. For help, see the vendorsdocumentation.
2 Prepare the device drivers on the new media server hosts operating systemas explained in the NetBackup Device Configuration Guide .
3 Add the new media server to the additional servers list of the master serverand of the clients the new media server backs up. If the EMM server resideson a host other than the master server, add the new media server to theadditional servers list on that host. If the new media server is part of aserver group, add it to the additional servers list on all media servers in thegroup.
Note: To avoid problems with NetBackup, ensure that the host name youuse 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 . Forexample, to add the new media server to clients, select Clients .
-
8/14/2019 NetBackup_Administrator Guide 2
24/176
25Additi l fi ti
-
8/14/2019 NetBackup_Administrator Guide 2
25/176
25Additional configurationAdding a media server
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 catalogbackup configuration.For more information, see Chapter 4, NetBackup Catalog on page 273 in the Administrators 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 NetBackupsoftware 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 unitsthat 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 serverIf the EMM server is not running when you add a media server, the media serveris not registered. You cannot discover, configure, and manage devices. You mustregister the media server with the EMM server.
To register a media server1 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
26 Additional configuration
http://../nbu_sa_win_print_I/wn_cat_print.pdfhttp://../nbu_sa_win_print_I/wn_cat_print.pdfhttp://../nbu_sa_win_print_I/wn_cat_print.pdfhttp://../nbu_sa_win_print_I/wn_cat_print.pdf -
8/14/2019 NetBackup_Administrator Guide 2
26/176
26 Additional configurationAdding a media server
Note: To avoid problems with NetBackup, ensure that the host name youuse 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 .
27Additional configuration
-
8/14/2019 NetBackup_Administrator Guide 2
27/176
27Additional configurationNetBackup configuration options
NetBackup configuration optionsNetBackup configuration options allow an administrator to customizeNetBackup to meet specific site preferences and requirements. Generally, theseoptions are configured in the NetBackup Administration Console, under HostProperties .
Options for configuring media and device management in the vm.conf file asexplained in this chapter. The vm.conf file contains configuration entries formedia and device management.
However, some options cannot be configured by using the NetBackupAdministration Console.
NetBackup administration options
Media and device configuration options ( vm.conf file)
NetBackup administration optionsThe following NetBackup configuration options cannot be configured by usingthe NetBackup Administration Console.
To change a default value, use the bpgetconfig command to obtain a list of configuration entries, then use bpsetconfig to change the entries as needed.The commands are described in NetBackup Commands for Windows .
28 Additional configuration
-
8/14/2019 NetBackup_Administrator Guide 2
28/176
gNetBackup configuration options
NBRB_CLEANUP_OBSOLETE_DBINFO
The NBRB_CLEANUP_OBSOLETE_DBINFOentry serves as a performance tuningoption for the Intelligent Resource Manager. This entry indicates the number of seconds (default: 60) that can elapse between the cleanup of obsoleteinformation in the NetBackup Resource Broker ( nbrb ) database.
No equivalent exists in the NetBackup Administration Console host properties.
NBRB_ENABLE_OPTIMIZATIONS
The NBRB_ENABLE_OPTIMIZATIONSentry serves as a performance tuningoption for the Intelligent Resource Manager. This entry indicates whether theResource Broker caches states of resource requests. Default: 1 (true).
No equivalent exists in the NetBackup Administration Console host properties.
NBRB_FORCE_FULL_EVALThe NBRB_FORCE_FULL_EVALentry serves as a performance tuning option for
the Intelligent Resource Manager. This entry indicates the number of secondsthat can elapse between full evaluations of all NetBackup Resource Broker(nbrb.exe ) queues, using no cached EMM information. (Default: 1800seconds/30 minutes.) For example, full evaluations include matching jobresource requests with available resources.
No equivalent exists in the NetBackup Administration Console host properties.
NBRB_REEVAL_PENDINGThe NBRB_REEVAL_PENDINGentry serves as a performance tuning option forthe 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.
No equivalent exists in the NetBackup Administration Console host properties.
NBRB_REEVAL_PERIODThe NBRB_REEVAL_PERIODentry serves as a performance tuning option for theIntelligent Resource Manager and NetBackup Resource Broker ( nbrb.exe ).NBRB_REEVAL_PERIODindicates the time between evaluations if anoutstanding request is not satisfied, and if no other requests or resources havebeen released. Default: 5 minutes passes before the initial request is reevaluated.
No equivalent exists in the NetBackup Administration Console host properties.
29Additional configuration
-
8/14/2019 NetBackup_Administrator Guide 2
29/176
NetBackup configuration options
NBRB_RETRY_DELAY_AFTER_EMM_ERR
The NBRB_RETRY_DELAY_AFTER_EMM_ERRentry serves as a performancetuning option for the Intelligent Resource Manager. This entry indicates howlong NetBackup waits after an EMM error before attempting again. (Default: 60seconds.) The error must be one where a retry is possible. For example, if amedia server is down.
NBRB_MPX_GROUP_UNLOAD_DELAY
The NBRB_MPX_GROUP_UNLOAD_DELAYentry serves as a performance tuningoption for the Intelligent Resource Manager.
This entry indicates the number of seconds that the NetBackup Resource Broker(nbrb.exe ) waits for a new job to appear before a tape is unloaded.
(Default: 10 seconds.) This setting can help avoid unnecessary reloading of tapesand applies to all backup jobs.
During user backups, nbrb.exe uses the maximum value of
NBRB_MPX_GROUP_UNLOAD_DELAYand theMedia mount timeout
hostproperty setting when unmounting the tape.
This host property is found in the NetBackup Administration Console underNetBackup Management > Host Properties > Select master server > Timeouts >Media mount timeout . See Chapter 7 in the Administrators Guide, Volume I formore details.
During restores, Media mount timeout is used, notNBRB_MPX_GROUP_UNLOAD_DELAY.
No equivalent exists in the NetBackup Administration Console host properties.
The RE_READ_INTERVALentry determines how often NetBackup checks diskstorage units for available capacity. Default: 300 seconds (5 minutes).
REQUIRED_NETWORKThe REQUIRED_NETWORKentry specifies the required route for backup traffic inan environment where the network traffic is segregated.
For example, an environment may contain a production network at145.21.14.0 and a backup network at 192.132.28.0 . To indicate thatNetBackup should use only the backup network, add the following entry in thebp.conf file:
REQUIRED_NETWORK = 192.132.28.0
Note: If the variable is set and the network is not available, all connections failand no backups are performed.
30 Additional configuration
-
8/14/2019 NetBackup_Administrator Guide 2
30/176
NetBackup configuration options
vm.conf options for media serversThe install_path \volmgr\vm.conf file contains configuration entries formedia and device management. NetBackup may create this file, but if it does notexist, it must be created to add entries.
The NetBackup component reads this configuration file on the host where thecomponent runs. The NetBackup component is a command, daemon, process, orutility. The host may be a NetBackup administration client or a server where
administration operations are requested.See Example vm.conf file on page 43 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 specifiedMedia Manager media type. You can specify more than one ACS_ mediatypeentry.
This entry is read and interpreted on the host on which vmcheckxxx andvmupdate run during a robot inventory operation. Use this entry on everyNetBackup media server that functions as an ACS robot control host.
For a list of the valid ACS_ mediatype entries, see Media Type Mappings tabin the NetBackup Administrators Guide for Windows, Volume I .
ADJ_LSMADJ_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-throughmechanisms may move ejected media to the media access port (MAP). Apass-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 ACSCAP) to select for efficient ejects. NetBackup determines the appropriate MAP tocomplete the media eject using a nearest-MAP algorithm.
This nearest-MAP algorithm is based on the physical orientation of the LSMsthat defined with this entry. This algorithm is only for the cases where morethan one MAP has been requested to handle the eject. If this algorithm is used,any MAP_IDentries in vm.conf are ignored.
31Additional configurationN tB k fi ti ti
-
8/14/2019 NetBackup_Administrator Guide 2
31/176
NetBackup configuration options
Note: The nearest-MAP capability is only available using the vmchangecommand with the -map option or the Vault administrative interface. It is notavailable from the NetBackup Administration Console.
Without this entry present, NetBackup assumes that all LSMs areinterconnected with pass-through ports, except for the first LSM and the lastLSM. 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 31):ADJ_LSM = 700 0,0 0,1ADJ_LSM = 700 0,0 0,6ADJ_LSM = 700 0,1 0,2ADJ_LSM = 700 0,1 0,6ADJ_LSM = 700 0,2 0,6ADJ_LSM = 700 0,2 0,3
ADJ_LSM = 700 0,3 0,4ADJ_LSM = 700 0,4 0,5
The robot has pass-through mechanisms between 7 LSMs.
Figure 1-2 Pass-through example
1
4
0 2
6
35
Interconnections forRobot 700
API_BARCODE_RULESAPI_BARCODE_RULES
This configuration entry applies only to NetBackup Enterprise Server.
32 Additional configurationNetBackup configuration options
-
8/14/2019 NetBackup_Administrator Guide 2
32/176
NetBackup configuration options
If this entry is specified in vm.conf , barcode rule support for API robots isenabled.
NetBackup barcode rules allow default media mappings to be overridden.Barcode rules are especially useful when multiple generations of the same tapedrive use the same type of media.
For example STK 9940A and STK 9940B drives use STK1R media, but write dataat different densities. The drive must be configured using different drive typessuch as hcart or hcart2. You can specify a barcode rule for a series of barcodes toconfigure 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, arobot inventory operation configures all media of type STK1R as either hcart orhcart2, depending on how the drive was configured.
AUTHORIZATION_REQUIREDAUTHORIZATION_REQUIRED
This entry specifies that NetBackup should use the vm.conf file SERVERentry
to control which hosts can monitor and control devices on this host. This entryis read and interpreted on the media server on which the NetBackup vmd serviceruns.
If this entry is specified in vm.conf , the vm.conf file also must include aSERVERentry for every media server that controls devices on this host.
If no AUTHORIZATION_REQUIREDentry exists and no SERVERentries exist, anyNetBackup server can monitor and control devices on this host.
For maximum security, Symantec recommends that you use this entry andSERVERentries.
This entry is read and interpreted on media servers on which the NetBackupvmd service runs.
AUTO_PATH_CORRECTIONAUTO_PATH_CORRECTION = YES|NO
If this entry is specified in vm.conf , it specifies whether automatic device pathremapping is enabled or disabled.
If the value is NO, the device configuration remains unchanged when theNetBackup Device Manager service ( ltid ) is started. Therefore, the saveddevice configuration may be different than the actual configuration after youchange devices and restart the server.
If the value is YES, NetBackup tries to discover attached devices and thenautomatically update the device configuration for any device paths that areincorrect. On Windows computers, this entry is read and interpreted on the host
33Additional configurationNetBackup configuration options
-
8/14/2019 NetBackup_Administrator Guide 2
33/176
NetBackup configuration options
on which the NetBackup Device Manager service runs. On UNIX and Linuxcomputers, 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 isdisabled by default on all other servers.
AUTO_UPDATE_ROBOTAUTO_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 therobot generates a unit attention message.
This entry only operates with the TL8 or TLD robots that post a unit attentionwhen 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 whenthe MAP has been opened.
AVRD_PEND_DELAYAVRD_PEND_DELAY = number_of_seconds
If this entry is specified in vm.conf , avrd waits number_of_seconds before itdisplays a pending status (PEND) in the Device Monitor. This entry is read andinterpreted on the host on which avrd runs.
On some server operating systems (Windows, Tru64, and HP-UX), NetBackupreports PEND if the drive reports Busy when a volume is unmounted. Use thisentry to minimize the display of this misleading status.The minimum for number_of_seconds is zero. The maximum is 255. The defaultvalue is 180 seconds.
AVRD_SCAN_DELAYAVRD_SCAN_DELAY = number_of_seconds
If this entry is specified in vm.conf , avrd waits number_of_seconds betweennormal scan cycles. This entry is read and interpreted on the host on whichavrd runs.
Use this entry to minimize tape mount times. Without this entry, NetBackupdelays mount requests by an average of 7.5 seconds.
The minimum for number_of_seconds is 1. The maximum is 180. A value of zerois converted to 1 second. The default value is 15 seconds. If a value is used that isgreater than the default, NetBackup delays mount requests and drive status
updates in the Device Monitor.
34 Additional configurationNetBackup configuration options
-
8/14/2019 NetBackup_Administrator Guide 2
34/176
p g p
Caution: If number_of_seconds is set to a value that allows media to be changedwithin one scan cycle, NetBackup may not detect media changes. Data loss mayoccur.
CLEAN_REQUEST_TIMEOUTCLEAN_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. Unprocessedrequests 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 valueof zero is converted to the default value of 30.
CLIENT_PORT_WINDOWCLIENT_PORT_WINDOW = start end
Use this entry to specify the range of non-reserved ports on this host that areused to connect to vmd on other hosts. This entry is read and interpreted on thehost 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 followingcases:
A CLIENT_PORT_WINDOWentry is not specified. A value of zero is specified for start .
CLUSTER_NAMECLUSTER_NAME = cluster_alias
This entry and the following two entries determine the name other NetBackupservers and clients should use when they refer to this server:
MM_SERVER_NAME =host_nameREQUIRED_INTERFACE = host_name
The algorithm for determining the server name is as follows:
Use the CLUSTER_NAMEentry if present in vm.conf .
Use the MM_SERVER_NAMEentry if present in vm.conf .
Use the REQUIRED_INTERFACE entry if present in vm.conf .
Use the same name that NetBackup uses.
Use the gethostname() name.
35Additional configurationNetBackup configuration options
-
8/14/2019 NetBackup_Administrator Guide 2
35/176
This entry is read and interpreted on the host on which the required interface isneeded.
CONNECT_OPTIONSCONNECT_OPTIONS = server_name 0 0 [0|1|2]
Add this entry in vm.conf to specify the options that enhance firewallefficiency with NetBackup. Server connection options can be any of thefollowing: use vnetd or the daemons port number, use only vnetd , or use onlythe daemons port number.
CONNECT_OPTIONSentries can be specified for multiple servers.
server_name is the name of the media server to connect to. The server must beat NetBackup level 4.5 or higher for vnetd to operate correctly.
The first and second options currently are not used. Specify zero for theseoptions.
The third option specifies the connection method to use to connect toserver_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 thedaemon.
A value of 1 specifies to use vnetd only to connect to a daemon on theserver.
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.
ExamplesThe following entry specifies to use either vnetd or the daemons port numberto 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 daemonss port number only to connectto server perch:CONNECT_OPTIONS = perch 0 0 2
DAS_CLIENTDAS_CLIENT = client_name
This configuration entry applies only to NetBackup Enterprise Server
If this entry is specified in vm.conf , specify the DAS client name that the TLMrobot uses for communications with the DAS/SDLC server. By default this client
36 Additional configurationNetBackup configuration options
-
8/14/2019 NetBackup_Administrator Guide 2
36/176
name is the host name of the media server. This entry is read and interpreted onthe host where tlmd is running.
DAYS_TO_KEEP_LOGSDAYS_TO_KEEP_LOGS = days
If this entry is specified in vm.conf , specify the number of days to keep debuglogs before vmd deletes them. This entry is read and interpreted on the hostswhere vmd is running.
A value of zero means that the logs are not deleted. The default is zero. Thisentry does not impact debug logs created by Unified Logging.
For more information about Unified Logging, see the NetBackupTroubleshooting Guide for UNIX, Windows, and Linux .
EMM_RETRY_COUNTEMM_RETRY_COUNT =number_of_retries
The vmd and the ltid daemons use this entry to determine how many times toretry 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 yourNetBackup support representative. If you add this entry to the vm.conf file orchange this value, you must restart the vmd and the ltid daemons / services.
EMM_CONNECT_TIMOUTEMM_CONNECT_TIMOUT =number_of_secondsThis value applies for broken connections between the vmd and the ltiddaemons and the NetBackup Enterprise Media Manager. The vmd and the ltiddaemons use this entry to determine for how long they should try to reconnectto the NetBackup Enterprise Media Manager.
Default: 20 seconds.
Only change the value of thisvm.conf
file entry when directed to do so by yourNetBackup support representative. If you add this entry to the vm.conf file orchange this value, you must restart the vmd and the ltid daemons / services.
EMM_REQUEST_TIMOUTEMM_REQUEST_TIMOUT =number_of_seconds
The vmd and the ltid daemons use this entry to determine how many secondsto allow a request to the NetBackup Enterprise Media Manager to complete.
Default: 300 seconds.
37Additional configurationNetBackup configuration options
-
8/14/2019 NetBackup_Administrator Guide 2
37/176
Only change the value of this vm.conf file entry when directed to do so by yourNetBackup support representative. If you add this entry to the vm.conf file orchange this value, you must restart the vmd and the ltid daemons / services.
ENABLE_ROBOT_AUTHNetBackup encourages the use of Symantec Product Authentication andAuthorization for NetBackup Access Control (NBAC) instead of legacy securityimplementations.
For information about the ENABLE_ROBOT_AUTHconfiguration entry, see theNetBackup 6.0 documentation. For information on Symantec ProductAuthentication and Authorization, see the NetBackup Security and EncryptionGuide .
INVENTORY_FILTERINVENTORY_FILTER = robot_type robot_number mode value1 [ value2 ...]
This configuration entry applies only to NetBackup Enterprise Server.
Used to filter robot inventory results in ACS or TLH robot types. This entry mustbe added to the configuration file ( vm.conf ) on the NetBackup server on whichthe inventory operation is invoked. This entry is read and interpreted on thehost on which vmcheckxxx and vmupdate run.
Note: This entry may be required for an ACS robot and the ACS library softwarehost 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_POOLfor ACS or BY_CATEGORYfor TLH.
See the following examples:INVENTORY_FILTER = ACS 0 BY_ACS_POOL 4 5
INVENTORY_FILTER = TLH 0 BY_CATEGORY FFFA CDB0
MAP_IDMAP_ID = robot_num map_ID
This configuration entry applies only to NetBackup Enterprise Server.
Use this entry to configure the default Media Access Port (MAP) to use to ejectmedia from Automated Cartridge System (ACS) robots. This default is
highlighted as a choice in the NetBackup Administration Console but you canalso select other Media Access Ports for ejects.
38 Additional configurationNetBackup configuration options
-
8/14/2019 NetBackup_Administrator Guide 2
38/176
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 usesthe smallest MAP that can hold the number of media to be ejected.
If NetBackup selects multiple MAPs, NetBackup uses the nearest-MAPalgorithm rather than the MAP that is specified in the MAP ID entry. For moreinformation, see ADJ_LSM on page 30 .
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 ACSCAP ID of 0,1,0 is used.MAP_ID = 700 0,1,0
MAP_CONTINUE_TIMEOUTMAP_CONTINUE_TIMEOUT = seconds
This entry applies only when the vmchange command is used and the -w optionis specified. The default timeout value for seconds is 300 (5 minutes).
seconds cannot be zero and values greater than 1200 (20 minutes) may causethe robotic daemon to cancel the operation.
If this entry is specified in vm.conf , the SCSI robotic daemons wait thespecified number of seconds before they time out. A timeout can occur whilewaiting for a reply from the user to continue after removing volumes from themedia access port. A timeout results in the operation being aborted.
This entry is read and interpreted on the host on which the SCSI-controlledrobotic daemon or process runs.
Caution: Non-mount activities such as a robotic inventory can not occur duringthis timeout period.
MEDIA_ID_BARCODE_CHARSMEDIA_ID_BARCODE_CHARS = robot_num barcode_length media_ID_rule
Note: To use this entry, the robot must support barcodes and the robot typecannot 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 andvmupdate run as part of the robot inventory operation.
39Additional configurationNetBackup configuration options
-
8/14/2019 NetBackup_Administrator Guide 2
39/176
Choose how NetBackup creates media IDs by defining the rules that specifywhich characters of a barcode on tape NetBackup uses. Alphanumericcharacters can be specified to be inserted in the ID.
Multiple entries can be added to the vm.conf file. For example, specify media IDgeneration for each robot or for each barcode format that has different numbersof characters. The multiple entries allow flexibility for multimedia.
If no MEDIA_ID_BARCODE_CHARSentries exist or the entry is invalid,NetBackup uses the rightmost six characters of the barcode to create its mediaID.
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 thatNetBackup extracts (from left to right). For example, 2 in a field extracts thesecond 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 amedia 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, mediamanagement may be more difficult.
The following is an example rule and the resulting generated media ID:Barcode on the tape: 032945L1Media ID rule: #N:2:3:4:5:6Generated media ID: N32945
Also see Media ID generation rules on page 102 .
MEDIA_ID_PREFIXMEDIA_ID_PREFIX = media_id_prefix
If this entry is specified in vm.conf , it defines the media ID prefixes to use formedia without barcodes. This entry is read and interpreted on the host wherevmcheckxxx 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 UpdateVolume Configuration operation.
MM_SERVER_NAMEMM_SERVER_NAME =host_name
This entry determines the name other NetBackup servers and clients should use
when they refer to this server:CLUSTER_NAME = cluster_alias
40 Additional configurationNetBackup configuration options
-
8/14/2019 NetBackup_Administrator Guide 2
40/176
REQUIRED_INTERFACE = host_name
The algorithm for determining the server name is as follows:
Use the CLUSTER_NAMEentry if present in vm.conf .
Use the MM_SERVER_NAMEentry if present in vm.conf .
Use the REQUIRED_INTERFACE entry if present in vm.conf .
Use the same name that NetBackup uses.
Use the gethostname() name.
This entry is read and interpreted on the host on which the required interface isneeded.
PREFERRED_GROUPNetBackup encourages the use of Symantec Product Authentication andAuthorization for NetBackup Access Control (NBAC) instead of legacy securityimplementations.
For information about the PREFERRED_GROUPconfiguration entry, see theNetBackup 6.0 documentation. For information on Symantec ProductAuthentication and Authorization, see the NetBackup Security and EncryptionGuide .
PREVENT_MEDIA_REMOVALApplies to the TL8 robots only.
Specifying this entry changes the default operation for TL8 robots. Without thisentry present, NetBackup allows the removal of media.
If this entry is specified in vm.conf , TL8 robots execute the SCSI commandPREVENT MEDIUM REMOVAL. The robot's main door or the MAP cannot beopened while the robotic control daemon runs.
This entry is read and interpreted on the host on which the TL8 robot controldaemon 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_PORTSRANDOM_PORTS = YES|NO
-
8/14/2019 NetBackup_Administrator Guide 2
41/176
42 Additional configurationNetBackup configuration options
-
8/14/2019 NetBackup_Administrator Guide 2
42/176
SERVERentries in the vm.conf file are used for NetBackup media serversecurity. The SERVERentries work with the AUTHORIZATION_REQUIREDentryto control which hosts can monitor and control devices on this host.
If the AUTHORIZATION_REQUIREDentry exists, the vm.conf file must includea SERVERentry for every media server that controls devices on this host. If thevm.conf file contains any SERVERentries, it also must include a SERVERentryfor itself or it cannot manage its own devices.
If no AUTHORIZATION_REQUIREDentry exists and no SERVERentries exist, anyNetBackup server can monitor and control devices on this host.
For security, the entries that allow only specific hosts to access the devices mustbe added remotely.
This entry is read and interpreted on media servers on which the NetBackupvmd service runs.
SSO_DA_REREGISTER_INTERVALSSO_DA_REREGISTER_INTERVAL = minutes
This configuration entry applies only to NetBackup Enterprise Server.
This vm.conf entry is for the Shared Storage Option (SSO) for Tape featureonly. It is read and interpreted on the host on which ltid runs.
ltid on a scan host periodically registers its shared drives with EMM/DAtoensure that it is still provides the drive scanning function. Only one of the hoststhat share a drive scan the drive. This reregistration allows conditions such as adevice allocator restart to have minimal impact on use of shared drives.
The default for the reregistration interval is 5 minutes. Use theSSO_DA_REREGISTER_INTERVAL entry to tune this interval. After the entry isadded, stop and restart ltid for the change to take effect.
SSO_DA_RETRY_TIMEOUTSSO_DA_RETRY_TIMEOUT = minutes
This configuration entry applies only to NetBackup Enterprise Server.
This vm.conf entry is for the Shared Storage Option (SSO) for Tape featureonly. It is read and interpreted on the host on which ltid runs.
If ltid encounters problems during communications with EMM/DAor a failurewhile 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_TIMEOUTentry to tune this delay period. After the entry is added, stop and restart ltidfor the change to take effect.
43Additional configurationNetBackup configuration options
-
8/14/2019 NetBackup_Administrator Guide 2
43/176
SSO_HOST_NAME
SSO_HOST_NAME =host_name
This configuration entry applies only to NetBackup Enterprise Server.
This vm.conf entry is for the Shared Storage Option (SSO) for Tape featureonly. It is read and interpreted on the host on which ltid runs.
This entry specifies the name that the current host uses to register, reserve, andrelease shared drives with EMM/DA. The default is the local host name.
TLH_mediatypeTLH_ mediatype = Media_Manager_mediatype
This configuration entry applies only to NetBackup Enterprise Server.
If this entry is specified in vm.conf , IBM ATL media types in Tape LibraryHalf-inch (TLH) robots are mapped to Media Manager media types. This entry isread and interpreted on the host where vmcheckxxx and vmupdate arerunning as part of the robot inventory operation.
TLM_mediatypeTLM_ mediatype = Media_Manager_mediatype
This configuration entry applies only to NetBackup Enterprise Server.
If this entry is specified in vm.conf , DAS/SDLC media types in Tape LibraryMultimedia (TLM) robots are mapped to Media Manager media types. This entryis read and interpreted on the host where vmcheckxxx and vmupdate arerunning as part of the robot inventory operation.
VERBOSEIf this entry is specified in vm.conf , all Media Manager components on the hostare 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_LOGSentry.
Example vm.conf fileThe following is an example of a vm.conf file, on host server1:SERVER = server1SERVER = server2MEDIA_ID_PREFIX = NVMEDIA_ID_PREFIX = NETB
ACS_3490E = HCART2
44 Additional configurationDirect I/O for backups
-
8/14/2019 NetBackup_Administrator Guide 2
44/176
Direct I/O for backupsBy default, the buffer size for disk storage units is 256K. If the buffer size is setto a value greater than 256K, backups written to that storage unit automaticallyuse direct I/O. An increased buffer size can improve backup speed.
To increase the buffer size, the following conditions must be met:
The storage unit must be owned by a Windows media server.
The storage unit must be either a Basic Disk or an Array Disk storage unit.
The backup to be stored cannot be multiplexed. The touch file that disables direct I/O must not be present
(install_path \ VERITAS\NetBackup\bin\DISABLE_DIRECT_IO ).
To increase the buffer size, create one of the following touch files on the mediaserver that owns the storage unit:
For backups to disk:install_path \VERITAS\NetBackup\db\config\SIZE_DATA_BUFFERS_DISK
For backups to disk or tape:install_path \VERITAS\NetBackup\db\config\SIZE_DATA_BUFFERS
If both touch files are present, SIZE_DATA_BUFFERS_DISK overrides the valuein SIZE_DATA_BUFFERS . At this time, Symantec recommends usingSIZE_DATA_BUFFERS_DISK .
Possible values to include in SIZE_DATA_BUFFERS_DISK orSIZE_DATA_BUFFERS include the following:
Table 1-1 Absolute byte values for SIZE_DATA_BUFFERS_DISK,SIZE_DATA_BUFFERS
For a data buffer of this size (kilobytes), enter this touch file value
32 32768
64 65536
96 98304
128 131072
160 163840
192 196608
224 229376
45Additional configurationDynamic host name and IP addressing
-
8/14/2019 NetBackup_Administrator Guide 2
45/176
Table 1-1 Absolute byte values for SIZE_DATA_BUFFERS_DISK,SIZE_DATA_BUFFERS
256 262144
For a data buffer of this size (kilobytes), enter this touch file value
Data buffer sizes continue in multiples of 32. Multiply the buffer size by 1024 forthe touch file value.
A direct I/O backup triggers the following message: Enabling direct I/O. Buffer
size: < buffer size >.
Disabling direct I/OTo disable direct I/O, create the following touch file on the media server thatowns the storage unit:
install_path \ VERITAS\NetBackup\bin\DISABLE_DIRECT_IO
Dynamic host name and IP addressingBy default, a NetBackup server assumes that a NetBackup client name is thesame as the network host name of the client machine. This assumption makes itdifficult 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 addressesfrom a DHCP server. Or, a remote machine that dials into a PPP server.
NetBackup dynamic host name and IP addressing allows you to defineNetBackup clients that do not have fixed IP addresses and host names.
Note: If you use dynamic addressing, remember that the NetBackup servers stillrequire fixed IP addresses and host names.
Note: All clients configured to use dynamic addressing and host names musttrust each other, similar to the NetBackup altnames feature.
The following steps are required to support the configurations that use dynamicIP addressing for NetBackup. Before you make changes to a configuration, readthis 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 addressesin the hosts file and (or) DNS on your network.
-
8/14/2019 NetBackup_Administrator Guide 2
46/176
47Additional configurationDynamic host name and IP addressing
-
8/14/2019 NetBackup_Administrator Guide 2
47/176
NetBackup requires that the IP addresses of NetBackup clients havecorresponding network host names. Ensure that each IP address that could beassigned to NetBackup clients has a network host name. The host name shouldbe defined in the host file, NIS, and DNS on your network.
As an example, suppose that you have 10 dynamic IP addresses and host namesavailable. The dynamic IP addresses and host names might be:
123.123.123.70 dynamic00123.123.123.71 dynamic01123.123.123.72 dynamic02123.123.123.73 dynamic03
..
.123.123.123.79 dynamic09
Assign a unique NetBackup client name to each NetBackup client that might useone of these dynamic IP addresses. The NetBackup client name that is assignedto a client is permanent and should not be changed. The client name that isassigned to NetBackup clients with dynamic IP addressing must not be the sameas any network host names on your network. If the NetBackup client names arechanged or are not unique, backup and restore results are unpredictable.
For example, suppose you have 20 machines that share the IP addresses aspreviously defined. If you want these machines to be NetBackup clients, youmight assign them these NetBackup client names as follows:
nbclient01nbclient02nbclient03nbclient04...nbclient20
Configuring the NetBackup master serverOn the master server, create your NetBackup backup policies. For client name
lists, use the NetBackup client names (for example, nbclient01) rather than thedynamic network host names (for example, dynamic01 ).
Next, create the client database on the master server. The client databaseconsists of directories and files in the following directory:
install_path \NetBackup\db\clientYou can create, update, list, and delete client entries with the bpclientcommand. The bpclient command is in the following directory:install_path \NetBackup\bin\admincmd
To create a dynamic client entry:
48 Additional configurationDynamic host name and IP addressing
-
8/14/2019 NetBackup_Administrator Guide 2
48/176
bpclient.exe -add -client client_name -dynamic_address 1where client_name is the NetBackup client name. The
-dynamic_address 1 argument indicates that the client uses dynamic IPaddressing. You can create entries with -dynamic_address 0 for static IPaddressing, but that is unnecessary and adversely affects performance.
To delete a client entry:bpclient.exe -delete -client client_name
To list a client entry:bpclient.exe -L -client client_name
To list all client entries:bpclient.exe -L -All
In our example, you can enter these commands to create the 20 clients:cd install_path \NetBackup\bin\admincmdbpclient -add -client nbclient01 -dynamic_address 1bpclient -add -client nbclient02 -dynamic_address 1bpclient -add -client nbclient03 -dynamic_address 1bpclient -add -client nbclient04 -dynamic_address 1
..
.bpclient -add -client nbclient20 -dynamic_address 1
To see what is currently in the client database, run bpclient as follows:install_path \NetBackup\bin\admincmd\bpclient -L -All
The output is similar to the following:Client Name: nbclient01Current Host:Hostname: *NULL*IP Address: 0.0.0.0Connect on non-reserved port: noDynamic Address: yes
Client Name: nbclient02Current Host:Hostname: *NULL*IP Address: 0.0.0.0
Connect on non-reserved port: noDynamic Address: yes...Client Name: nbclient20Current Host:Hostname: *NULL*IP Address: 0.0.0.0Connect on non-reserved port: noDynamic Address: yes
49Additional configurationDynamic host name and IP addressing
-
8/14/2019 NetBackup_Administrator Guide 2
49/176
The NetBackup client notifies the NetBackup server of its NetBackup clientname and network host name. Then, the Current Host, Hostname, and IPAddress fields display the values for that NetBackup client.
Configuring a dynamic Microsoft Windows clientIf it is not already installed, install NetBackup on the Windows client.
Start the Backup, Archive, and Restore user interface on the client and thenselect File > NetBackup Client Properties . The NetBackup Client Propertiesdialog box appears. Select the General tab. Change the Client Name to specifythe NetBackup client name for the Windows client.
In the NetBackup Administration Console, set Announce DHCP Interval . Thisvalue specifies how many minutes the client waits before it announces that itwill use a different IP address.
For more information, see Announce DHCP interval on page 457 in the Administrators Guide, Volume I .
The server is not notified if the default value of 0 is used. For a DHCP client, agood value to use is one-half of the lease period.On the client, stop and restart the NetBackup Client service to have the changestake effect.
Configuring a dynamic UNIX NetBackup clientIf not already installed, install the NetBackup client software.
Edit the /usr/openv/netbackup/bp.conf file. Use the CLIENT_NAMEentryto specify the NetBackup client name for the machine, as follows:CLIENT_NAME = nbclient00
You must run the bpdynamicclient command once when the system firststarts up. bpdynamicclient notifies the NetBackup server of the machine'sNetBackup client name and current network host name. Thebpdynamicclient 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 iswritten in the file is the same as the current network host name. If the hostnames match, bpdynamicclient exits and does not connect to the masterserver. If the host names do not match, bpdynamicclient connects to themaster server and informs the server of its NetBackup client name and hostname. If bpdynamicclient successfully informs the server,bpdynamicclient writes the current network host name into file_name . If
50 Additional configurationConfiguring email notifications
http://../nbu_sa_win_print_I/wn_host_print.pdfhttp://../nbu_sa_win_print_I/wn_host_print.pdfhttp://../nbu_sa_win_print_I/wn_host_print.pdfhttp://../nbu_sa_win_print_I/wn_host_print.pdf -
8/14/2019 NetBackup_Administrator Guide 2
50/176
bpdynamicclient cannot inform the server, bpdynamicclient deletesfile_name .
Most UNIX systems provide a facility to define startup scripts. For example, youcan create a script in the /etc/rc2.d directory on a Solaris system:
# cat > /etc/rc2.d/S99nbdynamicclient
-
8/14/2019 NetBackup_Administrator Guide 2
51/176
Specifying the locale of the NetBackup installationNetBackup applications can display a wide range of international date and timeformats as determined by the locale of the installation. To help ensureconsistency among the applications, NetBackup uses a single, configurablesource to define the locale conventions.
Table 1-2 To specify the locale of a NetBackup installation
Platform DirectionsWindows 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 predefinednumber, 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 filedefines the date and the t ime formats for each supported locale.
The .conf file contains very specific instructions on how to add or modify the list of supportedlocales and formats. However, the format of the file is summarized here.
The .conf file is divided into two parts, the TL lines and the TMlines.
TL Lines
The third field of the TL lines defines the case-sensitive locales that the NetBackup applicationssupport. The fourth and the fifth fields define the date and the time fields and associatedseparators for that supported locale is as follows:
You can modify the existing formats to change the default output. For example, the TL line for t