VERITAS Cluster Server Enterprise Agent 1.3 for NetBackup

Transcription

1 VERITAS Cluster Server Enterprise Agent 1.3 for NetBackup Installation and Configuration Guide Solaris July 2003 N10951F

2 Disclaimer The information contained in this publication is subject to change without notice. VERITAS Software Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual. Copyright Copyright VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogans are trademarks of VERITAS Software Corporation in the USA and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks or their respective companies. VERITAS Software Corporation 350 Ellis St. Mountain View, CA Phone Fax

3 Contents Preface v Technical Support v Conventions vi Chapter 1. Introduction Supported Version and Operating System Setting Up NetBackup in a VCS Cluster Environment About the NetBackup Enterprise Agent Detecting an Application Failure Chapter 2. Installing and Configuring the Agent Prerequisites Additional Requirements Shared Tape Drives Mount Point /usr/openv on Shared Disks Transparent IP Address Failover Server-Independent Restores Shared Robotic Control Setting Up the NetBackup Software in the Cluster Installing NetBackup Client Software on Local Disks Editing the bp.conf File on Local Nodes Mounting Shared Storage Device to /usr/openv Setting Up NetBackup DataCenter Server on Shared Disk Editing the bp.conf File for Shared Disk iii

4 Editing the vm.conf File on Shared Disk Removing NetBackup Startup and Shutdown Scripts Installing the Agent Software A Sample NetBackup Configuration Configuring the Agent NetBackup Resource Type Type Definition Sample Configuration Configuring the NetBackup Agent with Cluster Manager Importing the NetBackupTypes.cf File Adding the NetBackup Group Using the Wizard Configuring the NetBackup Agent by Editing Configuration Files Modifying the Agent Configuration Additional Monitoring Disabling the Agent Removing the Agent iv VCS Enterprise Agent for NetBackup Installation and Configuration Guide

5 Preface This document provides instructions on how to install and configure the VERITAS Cluster Server Agent for Netbackup. For information about VCS, refer to the VERITAS Cluster Server User s Guide. Technical Support U.S. and Canada: Call You may also contact Technical Support via at vsupport-us@veritas.com. Europe, the Middle East, or Asia: Visit the Technical Support web site at for a list of each country s contact information. Software updates, TechNotes, product alerts, and hardware compatibility lists, are also available from To learn more about VERITAS and its products, visit v

6 Conventions Conventions Typeface courier courier (bold) italic italic Symbol Usage Computer output, files, attribute names, device names, and directories User input and commands, keywords in grammar syntax New terms, titles, emphasis Variables Usage # Superuser prompt (for all shells) vi VCS Enterprise Agent for NetBackup Installation and Configuration Guide

7 Introduction 1 The NetBackup enterprise agent monitors specific NetBackup resources within an enterprise application, determines the status of these resources, and starts or stops them according to external events. The agent includes VCS type declarations and agent executables, and is represented by the NetBackup resource type. When the agent detects an application failure, the NetBackup service group is failed over to another system in the cluster. Supported Version and Operating System The VCS enterprise agent, version 1.3, for NetBackup supports NetBackup 3.4, 4.5 MP3, and 4.5 FP3. The agent runs with VCS versions 1.3, 2.0, and 3.5 on Solaris 2.5.1, 2.6, 7, 8. Setting Up NetBackup in a VCS Cluster Environment Setting up NetBackup in a VCS Cluster environment involves the following major steps: Configuring the disks, tape drives, and storage libraries to be accessible from each node using the same device path (see Chapter 2) Installing and configuring NetBackup (see Chapter 2 and the NetBackup for HP-UX documentation) Installing the VCS enterprise agent for NetBackup (see Chapter 3) or upgrading the VCS enterprise agent (see Chapter 6) Configuring the VCS enterprise agent for NetBackup (see Chapter 4) Verifying NetBackup configuration and failover (see Chapter 5) 1

8 About the NetBackup Enterprise Agent About the NetBackup Enterprise Agent The NetBackup agent monitors the NetBackup processes. Agent operations include: Online Executes the commands netbackup start or S77netbackup on the NetBackup server. Offline Executes the command bp.kill_all FORCEKILL on each system. Monitor Scans the process table for ltid, vmd, bprd, and bpdbm. The specific processes to be monitored can be configured by the ServerType attribute. Note that the bpdbm and bprd processes run only on the NetBackup Master server. Clean Stops all NetBackup or Media Manager daemons using the command bp.kill_all FORCEKILL. Detecting an Application Failure By default, the agent reports Netbackup is not running if the monitor cannot locate ltid, vmd, bprd, or bpdbm in the process table. 2 VCS Enterprise Agent for NetBackup Installation and Configuration Guide

9 Installing and Configuring the Agent 2 Prerequisites Install and configure VCS. (If necessary, review the VERITAS Cluster Server Installation Guide.) Install and configure NetBackup and the Media Manager software according to the additional requirements listed in the following section. (If necessary, review the NetBackup documentation and release notes.) Additional Requirements Shared Tape Drives If accessing the tape drive through a shared bus (dual-hosted SCSI or fibre-attached), the drive entries in /dev/rmt/ must match on both systems. For a SCSI configuration, ongoing backup jobs on the Master server may be disrupted if the standby system is booted. This disruption is caused by a bus reset signal. We recommend you use multiplexer or fibre switches for shared tape drives. If you use a multibackup server setup (one master fails over to a slave), you must separate the Media Manager configuration from the NetBackup setup. For more information, contact VERITAS Consulting Services. Mount Point /usr/openv on Shared Disks For the NetBackup server, all NetBackup and Media Manager executables, configurations, and database files must reside on a shared disk. Because the path is hardcoded into the application, the shared disk mount point is /usr/openv. Alternatively, you can create a symbolic link from /usr/openv to the installation directory on the shared disk. Note The shared disk must not be in the /etc/vfstab file. VCS must control the mounting and un-mounting of the device. 3

10 Additional Requirements Transparent IP Address Failover Include an IP resource for continuous access to the NetBackup server after the service group is switched. Include the first hostname (or multiple lines with aliases and DNS variations) of this IP address in /usr/openv/netbackup/bp.conf as the line SERVER = NBUMaster_hostname on each server and client. NetBackup uses a hostname lookup for server authentication to establish and maintain client/server communication. To avoid authentication failures, create SERVER entries in bp.conf for each local (private) VCS cluster hostname member defined in the Netbackup service group s SystemList attribute. Include all hostnames in bp.conf if using multiple IP addresses on the NetBackup server under VCS control. Server-Independent Restores If accessing the tape drive through a shared bus (dual-hosted SCSI or fibre-attached), the file /usr/openv/netbackup/bp.conf must contain the line FAILOVER_RESTORE_MEDIA_SERVERS = sysa, sysb. Otherwise, you must modify the NetBackup Media database when the service group is switched. (See the NetBackup documentation.) This feature is available for NetBackup 3.1 and later. The storage unit definition inside NetBackup uses the VCS-controlled IP resource as NetBackup Host. Shared Robotic Control For VCS setups in which robotic control is switched with shared disks as part of server failover, the robotic control host must contain the NetBackup service group s hostname of the IP resource. The name of the robotic control host is automatically chosen by the NetBackup vmconf/tpconfig installation utility. It is the system name of the host on which the installation takes place. To check the current definition of the robotic host definition, type: # strings /usr/openv/volmgr/database/robotic_def If the definition contains the local hostname of one VCS cluster member, save the file by renaming it, then switch the hostname to the NetBackup IP resource: # uname -S vcs_host # hostname vcs_host Verify that hostname has been switched to NetBackup IP resource. Restart vmconf. After reinitializing, revert to the original hostname of the server. 4 VCS Enterprise Agent for NetBackup Installation and Configuration Guide

11 Setting Up the NetBackup Software in the Cluster Verify that the NetBackup generic SCSI drivers in /dev/sg are installed on all hosts accessing the shared tape library. If necessary, use /usr/openv/volmgr/bin/install/sg.install to initialize the sg devices on each system in the NetBackup service group. To verify that the device names are the same on all systems, type: # /usr/openv/volmgr/bin/sgscan Contact VERITAS Technical Support for assistance with StorageTek tape libraries using Automated Cartridge System Library Software (ACSLS). Setting Up the NetBackup Software in the Cluster When you install the NetBackup Server software, use /usr/openv as the mount point to access the shared disks. It is recommended you install the client software on each node in /usr/openv so that cluster nodes not running the NetBackup resource can be backed up. When a cluster node does not have the NetBackup service group running, the client binaries are available locally in the /usr/openv directory. When the cluster node is running the NetBackup service group, /usr/openv is the mount point for the shared disk, where the binaries used are available. Installing NetBackup Client Software on Local Disks Use the following procedure when: You are installing NetBackup client software for the first time to a local disk on the nodes in a cluster You are migrating NetBackup from a single node and need to install NetBackup client software on the disks of the existing node and of the new nodes in the new cluster To install NetBackup client software, do the following: 1. Insert the NetBackup DataCenter Installation CD into the CD-ROM drive of one cluster node and start the installation. Refer to the NetBackup on HP-UX documentation for mounting instructions. 2. From the main menu of the installation script, choose: 2) NetBackup Client Software 3. Choose Yes when asked whether to install the client software on the local node: Do you want to install the NetBackup client software for this client? (y/n) [y] Chapter 2, Installing and Configuring the Agent 5

12 Setting Up the NetBackup Software in the Cluster 4. When presented with the Platform Client Options menu, choose the HP system that applies. 5. Choose the appropriate HP-UX operating system when presented with the choice of operating system options. 6. When you prompted to enter the name of the NetBackup server, Enter the name of the NetBackup server : enter the hostname associated with the virtual IP address to be used for the NetBackup resource in the cluster. 7. When prompted, enter the name of the local client node: Enter the name of this NetBackup client : 8. After the installation script copies client files to the local system and completes the installation, repeat step 1 through step 7 on the next cluster node. Editing the bp.conf File on Local Nodes Edit the file /usr/openv/netbackup/bp.conf on each node. The bp.conf file should contain: A SERVER entry for the virtual hostname of the NetBackup resource A SERVER entry for each cluster node A FAILOVER_RESTORE_MEDIA_SERVERS entry if the tape drive is accessed through a shared bus (dual-hosted SCSI or fibre-attached). For example, if vcs-roam is the hostname for the NetBackup resource, vcs-node1 and vcs-node2 are the hostnames of the first and second nodes of the cluster, the file /usr/openv/netbackup/bp.conf on each node should resemble: On vcs-node1: SERVER = vcs-roam SERVER = vcs-node1 SERVER = vcs-node2 FAILOVER_RESTORE_MEDIA_SERVERS = vcs-node1, vcs-node2 REQUIRED_INTERFACE = vcs-roam CLIENT_NAME = vcs-node1 On vcs-node2: SERVER = vcs-roam SERVER = vcs-node1 SERVER = vcs-node2 6 VCS Enterprise Agent for NetBackup Installation and Configuration Guide

13 Setting Up the NetBackup Software in the Cluster FAILOVER_RESTORE_MEDIA_SERVERS = vcs-node1, vcs-node2 REQUIRED_INTERFACE = vcs-roam CLIENT_NAME = vcs-node2 Mounting Shared Storage Device to /usr/openv From one system in the cluster, mount the shared storage device to /usr/openv. For example: # mount /dev/vg01/lvol01 /usr/openv Use the -o option for any other parameters needed when mounting the disk. Setting Up NetBackup DataCenter Server on Shared Disk If you are installing NetBackup in a new cluster, install the NetBackup DataCenter server software on the shared disk. The shared disk must be mounted on one system only at the mount point /usr/openv. 1. With the shared disk mounted at /usr/openv, insert the NetBackup DataCenter Installation CD into the CD-ROM drive of one cluster node and start the installation. Refer to the documentation for NetBackup on HP-UX for mounting and installation instructions. 2. As you proceed with the installation, be sure to do the following: a. When prompted for the host that is to store the global device configuration, enter the hostname assigned to the virtual IP address for the NetBackup resource if this is a clustered master server. If this is a clustered media server (NBUSlave), enter the hostname of the existing NBU master server. b. Answer Y when prompted to start the NetBackup processes, which are required for the installation and configuration of tape and robot devices. 3. Configure the NetBackup software to use the shared robotic tape drive configured with a shared path. Refer to the NetBackup on HP-UX documentation. Proceed to the next section, Editing the bp.conf File for Shared Disk. Chapter 2, Installing and Configuring the Agent 7

14 Setting Up the NetBackup Software in the Cluster Editing the bp.conf File for Shared Disk Edit the file /usr/openv/netbackup/bp.conf on the shared disk. The bp.conf file should contain: A SERVER entry for the virtual hostname of the NetBackup resource A SERVER entry for each cluster node A FAILOVER_RESTORE_MEDIA_SERVERS entry if the tape drive is accessed through a shared bus (dual-hosted SCSI or fibre-attached). For example, if vcs-roam is the hostname for the NetBackup resource, vcs-node1 and vcs-node2 are the hostnames of the first and second nodes of the cluster, the file /usr/openv/netbackup/bp.conf on the shared disk resemble: SERVER = vcs-roam SERVER = vcs-node1 SERVER = vcs-node2 FAILOVER_RESTORE_MEDIA_SERVERS = vcs-node1, vcs-node2 REQUIRED_INTERFACE = vcs-roam Note The VCS enterprise agent for NetBackup changes the SERVER entries in the bp.conf file so that the actual hostname of the node on which NetBackup is being brought online is the first SERVER entry. Editing the vm.conf File on Shared Disk If Media server (NBUMaster or NBUSlave) processes run on the systems, you must edit the file /usr/openv/volmgr/vm.conf on the shared disk. The vm.conf file contains the following entries: REQUIRED_INTERFACE for the virtual hostname of the NetBackup resource. MH_HOST_NAME for the virtual hostname of the NetBackup resource. DEVICE_HOST for the virtual hostname of the NetBackup resource. For example, if vcs-roam is the hostname for the NetBackup resource, and vcs-node1 and vcs-node2 are the hostnames of the first and second nodes of the cluster, the file /usr/openv/volmgr/vm.conf on the shared disk resembles: REQUIRED_INTERFACE = vcs-roam MH_HOST_NAME = vcs-roam DEVICE_HOST = vcs-roam 8 VCS Enterprise Agent for NetBackup Installation and Configuration Guide

15 Installing the Agent Software Removing NetBackup Startup and Shutdown Scripts Remove the startup and shutdown scripts for NetBackup that were installed with the NetBackup server software. VCS must control startup and shutdown of the NetBackup processes. On the node where the NetBackup server installation was performed, issue the following commands: Installing the Agent Software 1. Log in as root. 2. Insert the CD into a drive connected to your system. If you are running Solaris volume-management software, the software automatically mounts the CD as /cdrom/cdrom0. Type the following command to install the agent: # cd /cdrom/cdrom0 # pkgadd -d. If you are not running Solaris volume-management software, you must mount the CD manually. For example: # mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /mnt Where, in this example, /dev/dsk/c0t6d0s2 is the default for the CD drive. # cd /mnt # pkgadd -d. 3. Repeat steps 1 and 2 on each system to become part of the NetBackup service group. Chapter 2, Installing and Configuring the Agent 9

16 A Sample NetBackup Configuration A Sample NetBackup Configuration In the following example, VCS is configured on a two-system cluster (sysa and sysb), and NetBackup is installed on shared disks. VCS Private Network System A (sysa) System B (sysb) Tape Library Shared Disks Public Network Sample Configuration on a Two-System Cluster 10 VCS Enterprise Agent for NetBackup Installation and Configuration Guide

17 Configuring the Agent Configuring the Agent You can configure the NetBackup agent using two methods: By using VCS Cluster Manager (the VCS graphical user interface) to edit a resource group template for the NetBackup agent. See Configuring the NetBackup Agent with Cluster Manager on page 14), or, By using the types configuration file and directly editing the main.cf file based on the sample main.cf supplied with the NetBackup agent (see Configuring the NetBackup Agent by Editing Configuration Files on page 16). This method requires that VCS be stopped and restarted before the configuration takes effect. Before you configure the agent, review the following tables that describe the NetBackup resource types and their attributes. The resource type definition files and the sample main.cf configurations are also shown for reference. Chapter 2, Installing and Configuring the Agent 11

18 Configuring the Agent NetBackup Resource Type. Attributes Type and Dimension Definition ServerType string-scalar The agent monitors processes as specified by the value of ServerType. The values for ServerType and processes monitored for each are: NBUSlave:vmd,Itid,avrd NBUMaster: bprd, pbdbm, vmd,ltid,avrd NBUMasterwoMM: bprd, bpdbm (this is the equivalent of NBUMaster without Media Manager) The value for ServerType may be a list of process names enclosed by quotes the names separated by white space. For example: "bprd avrd ltid" RobotDaemon (optional) MonScript (optional) string-scalar string-scalar Executable file name of the robotic device control daemon as defined in /usr/openv/volmgr/bin. Pathname of secondary monitor script. (See page 18 for details on secondary monitoring.) By default, the RestartLimit is set to 2. This default setting activates two restart attempts if the resource offlines unexpectedly. The OnLineRetryLimit and OnLineWaitLimit are set to 1. If an online is ineffective (for example, if a daemon does not completely start), this default setting activates a clean action. Type Definition type NetBackup ( str ServerType str RobotDaemon str MonScript static int OnLineRetryLimit = 1 static int OnLineWaitLimit = 1 static int RestartLimit = 2 NameRule = group.name + "_" + resource.servertype static str ArgList[] = { ServerType, RobotDaemon, MonScript } ) 12 VCS Enterprise Agent for NetBackup Installation and Configuration Guide

19 Configuring the Agent Sample Configuration NetBackup nbugrp_nbumaster ( ServerType = NBUMaster RobotDaemon = ts8d MonScript = "" ) The figure below illustrates the configuration s dependency graph. nbugrp_nbumaster NetBackup nbucons IP opt_nbu Mount nbugrp_hme0 NIC shdg_nbu Volume shdg DiskGroup Dependency Graph This configuration has one disk group on which a single volume is created. The mount point /opt/nbu requires the DiskGroup and Volume resources. The service group IP address of the Master server is configured using the IP and NIC resource types. The Master server can be started after each of these resources is brought online. Note In this example, the shared disks are not mounted at /usr/openv/. Use the command ln -s /opt/nbu /usr/openv to create symbolic links on each cluster system. Chapter 2, Installing and Configuring the Agent 13

20 Configuring the NetBackup Agent with Cluster Manager Configuring the NetBackup Agent with Cluster Manager A template for the NetBackup resource groups has been automatically installed when you installed the NetBackup enterprise agent. Using the VCS GUI, you can view the template, which displays the NetBackup service group, its resources and their attributes. You can dynamically modify the attributes values as necessary for your configuration. Importing the NetBackupTypes.cf File To use the NetBackup Group template, import the NetBackupTypes.cf file to the VCS engine by using Cluster Manager: 1. Start Cluster Manager. 2. Click on the File menu and select Import Types. 3. In the Import Types dialog box, select the file: /etc/vrtsvcs/conf/sample_nbu/netbackuptypes.cf 4. Import the types file for NetBackup. 5. Save the configuration. At this point, the NetBackup types have been imported to the VCS engine. The NetBackup agent can be configured without interrupting or stopping VCS. For detailed information about using the VCS Cluster Manager, refer to the chapter About the VCS GUI in the VERITAS Cluster Server User s Guide. Adding the NetBackup Group Using the Wizard If you have imported the NetBackupTypes.cf file, you can download the NetBackup Group template by starting the Service Group Configuration Wizard in Cluster Manager. 1. In Cluster Manager, click the service group configuration wizard icon on the toolbar. 2. Click Next on the wizard Welcome window. a. Enter the service group name. In this instance, enter NetBackup. b. Select the systems on which the service group will run. 3. Confirm that you are basing the service group on a predefined template: click Next. 14 VCS Enterprise Agent for NetBackup Installation and Configuration Guide

21 Configuring the NetBackup Agent with Cluster Manager 4. Select the NetBackup template (NetBackupGroup) from the list of templates; click Next. 5. The wizard prompts you with alternate names in case the names in the template clash with existing names; make corrections as necessary and click Next. 6. When the wizard indicates that it is ready to create the service group, click Next; the service group is dynamically created based on the NetBackup template. 7. Review the service group s resource attributes, and modify the default values, if necessary, in accord with your specific configuration. Chapter 2, Installing and Configuring the Agent 15

22 Configuring the NetBackup Agent by Editing Configuration Files Configuring the NetBackup Agent by Editing Configuration Files Follow the instructions below to configure the agent according to the sample configuration of the Master server: 1. Log in to sysa as root. If VCS is configured and running on your machine, use the following command to stop it: # hastop -all [-force] 2. Copy the NetBackupTypes configuration file: # cp /etc/vrtsvcs/conf/sample_nbu/netbackuptypes.cf /etc/vrtsvcs/conf/config/netbackuptypes.cf 3. If you want to add a NetBackup resource to an existing VCS configuration, go to step 4. If you have a new VCS configuration, perform the following steps: a. Copy the sample NetBackup configuration file: # cp /etc/vrtsvcs/conf/sample_nbu/main.cf /etc/vrtsvcs/conf/config/main.cf b. Edit the default attributes in the file /etc/vrtsvcs/conf/config/main.cf to match the parameters in your configuration. 4. If you have created a resource tree with your own configuration and want to configure the NetBackup resource only, edit the main.cf file to contain the line: include "NetBackupTypes.cf" a. Create the NetBackup resource in the main.cf file, using the sample configuration on page 13. The resource block must be after the group definition, and requires one Mount and one IP resource. b. Assign dependencies to the newly created resource. 16 VCS Enterprise Agent for NetBackup Installation and Configuration Guide

23 Configuring the NetBackup Agent by Editing Configuration Files 5. Verify the syntax of the file /etc/vrtsvcs/conf/config/main.cf: # hacf -verify config 6. Start the VCS engine: # hastart 7. Verify that all NetBackup service group resources are brought online: # hagrp -state service_group -sys sysa 8. Take the service group offline and verify that all resources are stopped: # hagrp -offline service_group -sys sysa # hagrp -state service_group -sys sysa 9. Bring the service group online again and verify that all resources are available: # hagrp -online service_group -sys sysa # hagrp -state service_group -sys sysa 10. Start the VCS engine on sysb: # hastart # hagrp -state service_group -sys sysb 11. Switch the NetBackup service group to sysb: # hagrp -switch service_group -sys sysb 12. Verify that all NetBackup service group resources are brought online on sysb: # hagrp -state service_group -sys sysb # hagrp -state service_group -sys sysa Chapter 2, Installing and Configuring the Agent 17

24 Modifying the Agent Configuration Modifying the Agent Configuration To dynamically configure the VCS enterprise agent for NetBackup, see the chapter on reconfiguring VCS from the command line in the VERITAS Cluster Server User s Guide. Additional Monitoring The VCS enterprise agent for NetBackup provides two levels of application monitoring: primary and secondary. The primary level monitors the NetBackup daemon processes to verify that they are continuously active. The secondary level runs a script for further testing. The pathname to the script, with execute permissions for root, is defined by the MonScript attribute of the NetBackup agent. A return value of 100 indicates that the test failed and that the resource is offline. A return value of indicates that the test was successful and that the resource is online. Other values of the resource state are undefined. (For more information, see the chapter on implementing entry points using scripts in the VERITAS Cluster Server Agent Developer s Guide.) 18 VCS Enterprise Agent for NetBackup Installation and Configuration Guide

25 Disabling the Agent Disabling the Agent To disable the agent on a system, you must first switch the NetBackup service group to an OFFLINE state. You can stop the application completely, or switch the agent to another system. 1. You can determine if the service group is online by entering: # hagrp -state service_group -sys system_name 2. If the service group is online, take it offline by entering: # hagrp -switch service_group -to system_name or: # hagrp -offline service_group -sys system_name 3. Stop the NetBackup agent on the system: # haagent -stop agent When you get the message Please look for messages in the log file, check the file /var/vrtsvcs/log/engine_a.log A for a message confirming the agent has stopped. You can also use the ps command to confirm the agent is stopped. You can now remove the system, service group, or resource type from the VCS configuration. See the chapter on reconfiguring VCS from the command line in the VERITAS Cluster Server User s Guide. Removing the Agent Type the following command on each system to remove the agent. Answer prompts accordingly: # pkgrm VRTSvcsnb Chapter 2, Installing and Configuring the Agent 19

26 Removing the Agent 20 VCS Enterprise Agent for NetBackup Installation and Configuration Guide