nbu ag volume2

Veritas NetBackup Administrators Guide, Volume IIfor Windows

Release 6.5

12308282

Veritas NetBackup 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 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 NONINFRINGEMENT, 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 noticesThird-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.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 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 configurationMultiplexing .........................................................................................................13 When to use multiplexing ...........................................................................14 How to configure multiplexing ..................................................................14 Maximum streams per drive for a storage unit ...............................15 Media multiplexing for a schedule ....................................................15 Other configuration settings to consider using multiplexing ......18 Demultiplexing .............................................................................................19 Using multiple NetBackup master servers ......................................................20 Using multiple media servers with one master server ..................................21 Software on each server ..............................................................................22 NetBackup catalogs .....................................................................................23 Adding a media server .........................................................................................23 Registering a media server .........................................................................25 NetBackup configuration options .....................................................................27 NetBackup administration options ...........................................................27 NBRB_CLEANUP_OBSOLETE_DBINFO ............................................28 NBRB_ENABLE_OPTIMIZATIONS ....................................................28 NBRB_FORCE_FULL_EVAL ................................................................28 NBRB_REEVAL_PENDING ..................................................................28 NBRB_REEVAL_PERIOD .....................................................................28 NBRB_RETRY_DELAY_AFTER_EMM_ERR ......................................29 NBRB_MPX_GROUP_UNLOAD_DELAY ...........................................29 REQUIRED_NETWORK .......................................................................29 vm.conf options for media servers ............................................................30 ACS_mediatype ......................................................................................30 ADJ_LSM ................................................................................................30 API_BARCODE_RULES ........................................................................31 AUTHORIZATION_REQUIRED ..........................................................32 AUTO_PATH_CORRECTION ..............................................................32 AUTO_UPDATE_ROBOT .....................................................................33 AVRD_PEND_DELAY ...........................................................................33 AVRD_SCAN_DELAY ...........................................................................33 CLEAN_REQUEST_TIMEOUT ............................................................34 CLIENT_PORT_WINDOW ...................................................................34 CLUSTER_NAME ..................................................................................34

6

CONNECT_OPTIONS ........................................................................... 35 DAS_CLIENT ......................................................................................... 35 DAYS_TO_KEEP_LOGS ....................................................................... 36 EMM_RETRY_COUNT ......................................................................... 36 EMM_CONNECT_TIMOUT ................................................................. 36 EMM_REQUEST_TIMOUT ................................................................. 36 ENABLE_ROBOT_AUTH ..................................................................... 37 INVENTORY_FILTER .......................................................................... 37 MAP_ID .................................................................................................. 37 MAP_CONTINUE_TIMEOUT ............................................................. 38 MEDIA_ID_BARCODE_CHARS .......................................................... 38 MEDIA_ID_PREFIX .............................................................................. 39 MM_SERVER_NAME ........................................................................... 39 PREFERRED_GROUP .......................................................................... 40 PREVENT_MEDIA_REMOVAL ........................................................... 40 RANDOM_PORTS ................................................................................ 40 REQUIRED_INTERFACE ..................................................................... 41 SERVER ................................................................................................. 41 SSO_DA_REREGISTER_INTERVAL .................................................. 42 SSO_DA_RETRY_TIMEOUT ............................................................... 42 SSO_HOST_NAME ............................................................................... 43 TLH_mediatype .................................................................................... 43 TLM_mediatype ................................................................................... 43 VERBOSE ............................................................................................... 43 Example vm.conf file ........................................................................... 43 Direct I/O for backups ......................................................................................... 44 Disabling direct I/O ..................................................................................... 45 Dynamic host name and IP addressing ............................................................ 45 Setting up dynamic IP addresses and host names .................................. 46 Configuring the NetBackup master server .............................................. 47 Configuring a dynamic Microsoft Windows client ................................. 49 Configuring a dynamic UNIX NetBackup client ..................................... 49 Configuring email notifications ........................................................................ 50 Specifying the locale of the NetBackup installation ...................................... 51

Chapter 2

Reference topicsRules for using host names in NetBackup ....................................................... 54 Qualifying host names ................................................................................ 54 How NetBackup uses host names .............................................................. 54 Policy configuration ............................................................................ 55 Image catalog ....................................................................................... 55 Error catalog ......................................................................................... 55 Catalog backup information ............................................................... 55

7

How to update NetBackup after a host name changes ...........................56 Special considerations for Domain Name Service (DNS) .......................56 Reading backup images with tar .......................................................................58 Effects of a non-NetBackup tar ..........................................................58 Factors that affect backup time .........................................................................59 Total data ......................................................................................................59 Transfer rate .................................................................................................59 Device delays ................................................................................................60 Determining NetBackup transfer rate ..............................................................60 Network transfer rate ..................................................................................60 Network transfer plus end-of-backup-processing rate ..........................61 Total transfer rate .......................................................................................61 Examples .......................................................................................................61 Using the system monitor ..........................................................................62 How NetBackup builds a worklist ......................................................................65 Building the worklist (Queue) ....................................................................65 To prioritize queued jobs ............................................................................66 Determining backup media requirements .......................................................67 NetBackup notify scripts ....................................................................................68 backup_notify.cmd ..............................................................................69 backup_exit_notify.cmd ......................................................................69 bpstart_notify (UNIX clients only) ....................................................70 bpstart_notify.bat (Microsoft Windows clients only) ....................72 bpend_notify (UNIX clients only) ......................................................74 bpend_notify.bat (Microsoft Windows clients only) ......................76 dbbackup_notify.cmd ..........................................................................78 diskfull_notify.cmd ..............................................................................79 mail_dr_info.cmd .................................................................................80 nbmail.cmd ............................................................................................81 parent_end_notify.cmd .......................................................................81 parent_start_notify.cmd .....................................................................82 restore_notify.cmd ...............................................................................82 session_notify.cmd ..............................................................................83 session_start_notify.cmd ....................................................................83 userreq_notify.cmd ..............................................................................83 Media and device management best practices ................................................84 General practices .........................................................................................84 Media management .....................................................................................85 Device management ....................................................................................85 Performance and troubleshooting ............................................................86 Using TapeAlert ...................................................................................................87 Requirements for using TapeAlert ............................................................87 TapeAlert log codes .....................................................................................87

8

Drive cleaning overview ..................................................................................... 90 Reactive cleaning (TapeAlert) .................................................................... 91 TapeAlert cleaning .............................................................................. 91 TapeAlert and frequency-based cleaning ........................................ 91 Library-based cleaning ............................................................................... 91 Frequency-based cleaning .......................................................................... 92 Frequency-based cleaning limitations ............................................. 92 Operator-initiated cleaning ....................................................................... 93 Using a cleaning tape .................................................................................. 93 Volume pool and volume group overview ....................................................... 93 Volume pools ................................................................................................ 94 Volume groups ............................................................................................. 94 Rules for assigning volume groups ................................................... 94 Volume pool and volume group example ................................................. 95 Scratch volume pools .................................................................................. 96 Scratch pool example .......................................................................... 96 Scratch pool usage ............................................................................... 97 Barcode overview ................................................................................................. 98 Barcode advantages ..................................................................................... 98 Barcode best practices ................................................................................ 98 Barcode rules ................................................................................................ 99 NetBackup actions for barcodes ........................................................ 99 Checking barcodes .............................................................................100 Example barcode rules ...................................................................... 100 Media ID generation rules ........................................................................ 102 Controlling hardware compression ................................................................ 102 Changing your hardware configuration .........................................................102 Replacing devices ....................................................................................... 102 Decommissioning a media server ...........................................................104 How NetBackup selects drives ......................................................................... 106 How NetBackup reserves drives ...................................................................... 107 SCSI persistent reserve process .............................................................. 108 SCSI persistent reserve commands ................................................. 109 SCSI persistent reserve conflicts ..................................................... 109 SPC-2 SCSI reserve process ...................................................................... 109 SPC-2 SCSI reserve commands ........................................................ 110 SCSI reservation conflicts ................................................................ 111 Forcing a release ................................................................................ 111 Breaking a reservation ...................................................................... 112 SCSI reserve requirements and limitations ........................................... 112 SCSI reservation logging .......................................................................... 114 Server operating system limitations ...................................................... 114 Checking for data loss ...............................................................................114

9

Possible data loss causes ...................................................................114 Checking for tape and driver configuration errors ..............................115 Common configuration problems ....................................................115 Configuring SCSI reserve ..........................................................................115 How NetBackup selects media .........................................................................116 Selecting media in robots .........................................................................116 Spanning media ..................................................................................117 Selecting media in stand-alone drives ....................................................117 Media selection using stand-alone drive extensions ....................118 Media formats ....................................................................................................120 Standard tape format ................................................................................120 QIC/WORM tape format ............................................................................120 Optical media format .................................................................................121 Fragmented backups .................................................................................121 Multiplexing format ..................................................................................121 Spanning tapes ...........................................................................................122 Media Manager commands ..............................................................................122 Device discovery overview ...............................................................................124 Device serialization ...................................................................................124 Devices that can be discovered ................................................................125 Device discovery in NetBackup ................................................................125 Device discovery in the Device Configuration Wizard .........................126 Device discovery and shared tape drives ...............................................126 Viewing and verifying the device configuration ...................................127 Adding devices without discovery ...........................................................127 Device mapping file ...................................................................................128 Correlating tape drives to device files or addresses .....................................128 Correlating devices and device files on UNIX hosts .............................128 Correlating devices and names on Windows hosts ..............................130

Chapter 3

UNIX reference topicsCross mount points ............................................................................................134 Exclude and include lists on UNIX clients .....................................................136 Creating an exclude list on a UNIX client ......................................136 Creating an include list on a UNIX client .......................................139 Schedules for user backups or archives .........................................................140

Chapter 4

Using NetBackup with AFSInstallation ..........................................................................................................141 System requirements ................................................................................141 Server and client installation ...................................................................141 Configuration .....................................................................................................141

10

General policy attributes .......................................................................... 142 Client list ..................................................................................................... 142 Backup selections ...................................................................................... 142 Backup selection list directives ............................................................... 142 Regular expressions .................................................................................. 143 Exclude and include lists .......................................................................... 144 Backups and restores ........................................................................................ 144 Backups ....................................................................................................... 144 Automatic backup ..............................................................................144 Manual backup ................................................................................... 144 Restores ....................................................................................................... 144 Restore from the NetBackup for AFS client .................................. 144 Restore from the NetBackup master server .................................. 145 Notes about restores .......................................................................... 145 Troubleshooting .................................................................................................145 Troubleshooting backups ......................................................................... 146 Troubleshooting restores ......................................................................... 146

Chapter 5

Intelligent Disaster RecoveryChanges for NetBackup 6.0 and later ............................................................. 148 Supported Windows editions ........................................................................... 148 Requirements for IDR ....................................................................................... 149 Overview of IDR use .......................................................................................... 150 About the DR files .............................................................................................. 150 Configuring NetBackup policies for IDR ........................................................ 151 Backing up the protected computer ................................................................ 152 Creating IDR media ........................................................................................... 152 Choosing the bootable media ................................................................... 153 Creating bootable diskettes ...................................................................... 154 To modify diskette sets for use with multiple Windows 2000 computers 155 Creating a bootable CD image .................................................................. 156 Creating IDR diskettes ..............................................................................157 Updating IDR media .......................................................................................... 158 Updating a bootable CD ............................................................................ 158 Updating bootable diskettes .................................................................... 159 Updating IDR diskettes only .................................................................... 160 Using drfile.exe to create or update a DR file .......................................160 Recovering your computer ...............................................................................161 Step 1: Boot your computer ...................................................................... 162 Step 2: Windows setup in IDR recovery ................................................. 163 Step 3: Disaster recovery wizard ............................................................. 164 Notes on altering hard drive partition sizes .......................................... 167

11

Notes on recovering specific platforms ..........................................................167 Recovering the dell PowerEdge 6100/200 with RAID ..........................168 Recovering IBM computers ......................................................................168 Recovering Compaq computers ...............................................................169 IDR frequently asked questions ......................................................................169

12

Chapter

1

Additional configurationThis chapter explains settings that, in most instances, are optional. The sections in 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 onto the media. Multiplexed and unmultiplexed backups can reside on the same volume. Separate volume pools or media IDs are not necessary.

14 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 multiplexingMultiplexing 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.

How to configure multiplexingMultiplexing must be set in two places in the NetBackup configuration:

Additional configuration Multiplexing

15

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 unitThe 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 228 in the NetBackup Administrators 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 scheduleIn 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 148 in the NetBackup Administrators Guide, Volume I. 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.


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. In the 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. 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.


17

Figure 1-1Schedule A Media Multiplexing per drive = 2 dog 1 2 9 10

Multiplexing and schedulesStorage Unit Max mpx per drive = 4 A1 A2 A5 13 Drive 1 B2 6 B1 Schedule B Media Multiplexing per drive = 4 fox 5 12

cat 3 11 A3 Drive 2 4 A4 B4 8 B3 7

otter

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. 1 3 5 7 2 4 6 8 Jobs A1 and A2 from client dog start on drive 1. Schedule A Media Multiplexing limit of 2 is reached for this drive. Jobs A3 and A4 from client cat start on drive 2. Schedule A Media Multiplexing limit of 2 is reached for this drive. 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. 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 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.

13


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 17 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 multiplexingLimit 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 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 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 specific client without affecting other clients. For more information, see Maximum data streams on page 386 in the NetBackup 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 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.


19

DemultiplexingDemultiplexing 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.

20 Additional configuration 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 Mass Storage NetBackup Master Server A Workstations

Network A2

Mass Storage Network B1 Workstations Router Workstations Network B2

NetBackup Master Server B

Additional configuration Using multiple media servers with one master server

21

Using multiple media servers with one master serverYou 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 clients 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.

22 Additional configuration 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.

Administration Interface* User Interface (BAR)

Master Server NetBackup Catalogs Configuration files Image database User Interface (BAR)

NetBackup Client

Storage Device

Information in relational databases (about devices, volumes)

Administration Interface*

User Interface

User Interface (BAR)

Storage Device

NetBackup Media Server

NetBackup Media Server

Storage Device

Remote Admin Console*

Remote Admin 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 serverApplies 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.

Additional configuration Adding a media server

23

NetBackup catalogsApplies to NetBackup Enterprise Server only. 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.

Adding a media serverThe 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 vendors documentation. Prepare the device drivers on the new media server hosts operating system as explained in the NetBackup Device Configuration Guide. 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.

2 3

24 Additional configuration Adding a media server

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. Select Actions > Properties.

c

d e f g

Select the Servers properties. Click Add next to the Additional servers window and type the name of the new server. Click Add to add the server to the additional server list for all selected hosts. Click Close.

h Click OK. For more information, see Servers properties on page 467 in the NetBackup Administrators Guide, Volume I. 4 5 6 7 8 9 Restart the NetBackup services on the master server, the EMM server, and the media servers on which you added the new server name. On NetWare target clients, add the new media server name by using a SERVER entry in the bp.ini file. Install the NetBackup media server software as explained in the NetBackup Installation Guide. Configure the drives and robots as explained in Devices in the NetBackup Administrators Guide, Volume I. Configure the volumes as explained in Media in the NetBackup Administrators Guide, Volume I. On the master server, do the following to the NetBackup configuration:

Additional configuration Adding a media server

25

a b

Add storage units to the media server. Always specify the media server as the media server for the storage unit. 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 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 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 Configure the NetBackup policies and schedules to use the storage units that are configured on the media server.

c

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 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 2 Start the EMM service on the EMM server. 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 Adding a media server

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.

Additional configuration NetBackup configuration options

27

NetBackup configuration options

NetBackup configuration options allow an administrator to customize NetBackup to meet specific site preferences and requirements. Generally, these options are configured in the NetBackup Administration Console, under Host Properties. Options for configuring media and device management in the vm.conf file as explained in this chapter. The vm.conf file contains configuration entries for media and device management. However, some options cannot be configured by using the NetBackup Administration Console.

NetBackup administration options Media and device configuration options (vm.conf file)

NetBackup administration optionsThe following NetBackup configuration options cannot be configured by using the 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 NetBackup configuration options

NBRB_CLEANUP_OBSOLETE_DBINFOThe 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_OPTIMIZATIONSThe 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). No equivalent exists in the NetBackup Administration Console host properties.

NBRB_FORCE_FULL_EVALThe 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.exe) queues, using no cached EMM information. (Default: 1800 seconds/30 minutes.) For example, full evaluations include matching job resource requests with available resources. No equivalent exists in the NetBackup Administration Console host properties.

NBRB_REEVAL_PENDINGThe 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. No equivalent exists in the NetBackup Administration Console host properties.

NBRB_REEVAL_PERIODThe NBRB_REEVAL_PERIOD entry serves as a performance tuning option for the Intelligent Resource Manager and NetBackup Resource Broker (nbrb.exe). 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. No equivalent exists in the NetBackup Administration Console host properties.


29

NBRB_RETRY_DELAY_AFTER_EMM_ERRThe 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_DELAYThe 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.exe) 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.exe 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 Administrators Guide, Volume I for more details. During restores, Media mount timeout is used, not NBRB_MPX_GROUP_UNLOAD_DELAY. No equivalent exists in the NetBackup Administration Console host properties. The RE_READ_INTERVAL entry determines how often NetBackup checks disk storage units for available capacity. Default: 300 seconds (5 minutes).

REQUIRED_NETWORKThe 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.


vm.conf options for media serversThe install_path\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 43 for an example configuration file.

ACS_mediatypeACS_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 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-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.


31

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 31):

ADJ_LSM ADJ_LSM ADJ_LSM ADJ_LSM ADJ_LSM ADJ_LSM ADJ_LSM ADJ_LSM = = = = = = = = 700 700 700 700 700 700 700 700 0,0 0,0 0,1 0,1 0,2 0,2 0,3 0,4 0,1 0,6 0,2 0,6 0,6 0,3 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 6 5 4

2

3

API_BARCODE_RULESAPI_BARCODE_RULES

This configuration entry applies only to NetBackup Enterprise Server.


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_REQUIREDAUTHORIZATION_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_CORRECTIONAUTO_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


33

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_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 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_DELAYAVRD_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_DELAYAVRD_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_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. 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_WINDOWCLIENT_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_NAMECLUSTER_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. Use the gethostname() name.


35

This entry is read and interpreted on the host on which the required interface is needed.

CONNECT_OPTIONSCONNECT_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 daemons port number, use only vnetd, or use only the daemons port number. CONNECT_OPTIONS entries can be specified for multiple servers. 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.

ExamplesThe following entry specifies to use either vnetd or the daemons 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 daemonss port number only to connect to 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 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_LOGSDAYS_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_COUNTEMM_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_TIMOUTEMM_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. 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_REQUEST_TIMOUTEMM_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.


37

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.

ENABLE_ROBOT_AUTHNetBackup 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_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 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_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 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 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 ACS CAP 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 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_CHARSMEDIA_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.


39

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

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 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_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


REQUIRED_INTERFACE = host_name



This entry is read and interpreted on the host on which the required interface is needed.

PREFERRED_GROUPNetBackup 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_REMOVALApplies 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_PORTSRANDOM_PORTS = YES|NO


41

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. 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_INTERFACEREQUIRED_INTERFACE = host_name

This entry and the following two entries determine the name other NetBackup servers should use when they refer to this server:CLUSTER_NAME = cluster_alias MM_SERVER_NAME = host_name



This entry is read and interpreted on the host on which the required interface is 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.

SERVERSERVER = 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_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 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_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 feature only. It is read and interpreted on the host on which ltid runs. 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.


43

SSO_HOST_NAMESSO_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 feature only. 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, and release 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 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_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 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.

VERBOSEIf 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 fileThe 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

44 Additional configuration Direct I/O for backups

Direct I/O for backups

By default, the buffer size for disk storage units is 256K. If the buffer size is set to a value greater than 256K, backups written to that storage unit automatically use 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 media server 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 value in SIZE_DATA_BUFFERS. At this time, Symantec recommends using SIZE_DATA_BUFFERS_DISK. Possible values to include in SIZE_DATA_BUFFERS_DISK or SIZE_DATA_BUFFERS include the following: Table 1-1 Absolute byte values for SIZE_DATA_BUFFERS_DISK, SIZE_DATA_BUFFERS enter this touch file value32768 65536 98304 131072 163840 196608 229376

For a data buffer of this size (kilobytes),32 64 96 128 160 192 224

Additional configuration Dynamic host name and IP addressing

45

Table 1-1

Absolute byte values for SIZE_DATA_BUFFERS_DISK, SIZE_DATA_BUFFERS enter this touch file value262144

For a data buffer of this size (kilobytes),256

Data buffer sizes continue in multiples of 32. Multiply the buffer size by 1024 for the touch file value.

A direct I/O backup triggers the following message: Enabling direct I/O. Buffer size: .

Disabling direct I/OTo disable direct I/O, create the following touch file on the media server that owns 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 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 and (or) DNS on your network.

46 Additional configuration Dynamic host name and IP addressing

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 permanentdo not change it. Make changes on the master server: a b Create NetBackup policies with client lists that include the names from step 2. Create entries in the NetBackup client database for the client names from step 2. Create the entries by using the bpclient command.

3

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. 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. Make changes on each dynamic NetBackup UNIX client: a b Modify the bp.conf file to include a CLIENT_NAME entry with the correct NetBackup client name for the machine. 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. Configure the system to notify periodically the master server of the machine's NetBackup client name and current network host name.

5

6

c

Setting up dynamic IP addresses and host namesConfigure 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.


47

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 123.123.123.71 123.123.123.72 123.123.123.73 . . . 123.123.123.79 dynamic00 dynamic01 dynamic02 dynamic03

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 serverOn 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:

install_path\NetBackup\db\clientYou can create, update, list, and delete client entries with the bpclient command. The bpclient command is in the following directory:install_path\NetBackup\bin\admincmd

To create a dynamic client entry:

48 Additional configuration Dynamic host name and IP addressing

bpclient.exe -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.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\admincmd bpclient -add -client nbclient01 -dynamic_address bpclient -add -client nbclient02 -dynamic_address bpclient -add -client nbclient03 -dynamic_address bpclient -add -client nbclient04 -dynamic_address . . . bpclient -add -client nbclient20 -dynamic_address 1 1 1 1

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: nbclient01 Current Host: Hostname: *NULL* IP Address: 0.0.0.0 Connect on non-reserved port: no Dynamic Address: yes Client Name: nbclient02 Current Host: Hostname: *NULL* IP Address: 0.0.0.0 Connect on non-reserved port: no Dynamic Address: yes . . . Client Name: nbclient20 Current Host: Hostname: *NULL* IP Address: 0.0.0.0 Connect on non-reserved port: no Dynamic Address: yes


49

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 clientIf 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 457 in the Administrators Guide, Volume I. 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 clientIf 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

50 Additional configuration Configuring email notifications

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/rc

nbu ag volume2

Documents

install path veritas netbackup bin goodies bpstart notif

install path veritas netbackup bin disable direct io

named install path netbackup bin bpend res

install path netbackup bin bpstart res

install path netbackup bin bpend notify

install path netbackup bin bpstart notify

install path netbackup idr data directory

install path netbackup bin