VERITAS Cluster Server Enterprise Agent 1.3 for NetBackup · If accessing the tape drive through a...

VERITAS Cluster Server™

Enterprise Agent 1.3 for NetBackup

Installation and Configuration Guide

Solaris

July 2003N10951F

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 thismanual, including, but not limited to, the implied warranties of merchantability andfitness for a particular purpose. VERITAS Software Corporation shall not be liable forerrors contained herein or for incidental or consequential damages in connection with thefurnishing, performance, or use of this manual.

Copyright

Copyright © 1998-2003 VERITAS Software Corporation. All rights reserved. VERITAS,VERITAS Software, the VERITAS logo, and all other VERITAS product names and slogansare trademarks of VERITAS Software Corporation in the USA and/or other countries.Other product names and/or slogans mentioned herein may be trademarks or registeredtrademarks or their respective companies.

VERITAS Software Corporation350 Ellis St.Mountain View, CA 94043Phone 650–527–8000Fax 650–527–2908www.veritas.com

www.veritas.com

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Supported Version and Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Setting Up NetBackup in a VCS Cluster Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

About the NetBackup Enterprise Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Detecting an Application Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2. Installing and Configuring the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Additional Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Shared Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Mount Point /usr/openv on Shared Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Transparent IP Address Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Server-Independent Restores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Shared Robotic Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Setting Up the NetBackup Software in the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installing NetBackup Client Software on Local Disks . . . . . . . . . . . . . . . . . . . . . . . . . 5

Editing the bp.conf File on Local Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Mounting Shared Storage Device to /usr/openv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Setting Up NetBackup DataCenter Server on Shared Disk . . . . . . . . . . . . . . . . . . . . . 7

Editing the bp.conf File for Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

iii

Editing the vm.conf File on Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Removing NetBackup Startup and Shutdown Scripts . . . . . . . . . . . . . . . . . . . . . . . . . 9

Installing the Agent Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

A Sample NetBackup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Configuring the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

NetBackup Resource Type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Type Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Sample Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Configuring the NetBackup Agent with Cluster Manager . . . . . . . . . . . . . . . . . . . . . . . 14

Importing the NetBackupTypes.cf File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Adding the NetBackup Group Using the Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Configuring the NetBackup Agent by Editing Configuration Files . . . . . . . . . . . . . . . 16

Modifying the Agent Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Additional Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Disabling the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Removing the Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

iv VCS Enterprise Agent for NetBackup Installation and Configuration Guide

Preface

This document provides instructions on how to install and configure the VERITAS ClusterServer Agent for Netbackup. For information about VCS, refer to the VERITAS ClusterServer User’s Guide.

Technical SupportU.S. and Canada: Call 1-800-342-0652. You may also contact Technical Support via emailat [email protected].

Europe, the Middle East, or Asia: Visit the Technical Support web site athttp://support.veritas.com for a list of each country’s contact information.

Software updates, TechNotes, product alerts, and hardware compatibility lists, are alsoavailable from http://support.veritas.com.

To learn more about VERITAS and its products, visit http://www.veritas.com.

v

Conventions

Conventions

Typeface Usage

courier Computer output, files, attribute names, device names, and directories

courier(bold)

User input and commands, keywords in grammar syntax

italic New terms, titles, emphasis

italic Variables

Symbol Usage

# Superuser prompt (for all shells)

vi VCS Enterprise Agent for NetBackup Installation and Configuration Guide

Introduction
1 The NetBackup enterprise agent monitors specific NetBackup resources within anenterprise application, determines the status of these resources, and starts or stops themaccording to external events. The agent includes VCS type declarations and agentexecutables, and is represented by the NetBackup resource type. When the agent detectsan application failure, the NetBackup service group is failed over to another system in thecluster.
Supported Version and Operating SystemThe 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 EnvironmentSetting up NetBackup in a VCS Cluster environment involves the following major steps:

✔ Configuring the disks, tape drives, and storage libraries to be accessible from eachnode using the same device path (see Chapter 2)

✔ Installing and configuring NetBackup (see Chapter 2 and the NetBackup for HP-UXdocumentation)

✔ Installing the VCS enterprise agent for NetBackup (see Chapter 3) or upgrading theVCS enterprise agent (see Chapter 6)

✔ Configuring the VCS enterprise agent for NetBackup (see Chapter 4)

✔ Verifying NetBackup configuration and failover (see Chapter 5)

1

About the NetBackup Enterprise Agent

About the NetBackup Enterprise AgentThe NetBackup agent monitors the NetBackup processes. Agent operations include:

◆ Online—Executes the commands netbackup start or S77netbackup on theNetBackup server.

◆ Offline—Executes the command bp.kill_all FORCEKILL on each system.

◆ Monitor—Scans the process table for ltid, vmd, bprd, and bpdbm. The specificprocesses to be monitored can be configured by the ServerType attribute. Note thatthe bpdbm and bprd processes run only on the NetBackup Master server.

◆ Clean—Stops all NetBackup or Media Manager daemons using the commandbp.kill_all FORCEKILL.

Detecting an Application FailureBy 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

Installing and Configuring the Agent
2 Prerequisites
✔ Install and configure VCS. (If necessary, review the VERITAS Cluster ServerInstallation Guide.)

✔ Install and configure NetBackup and the Media Manager software according to theadditional requirements listed in the following section. (If necessary, review theNetBackup documentation and release notes.)

Additional Requirements

Shared Tape Drives

If accessing the tape drive through a shared bus (dual-hosted SCSI or fibre-attached), thedrive 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 isbooted. This disruption is caused by a bus reset signal. We recommend you usemultiplexer 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 configurationfrom 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 theapplication, the shared disk mount point is /usr/openv. Alternatively, you can create asymbolic 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 themounting and un-mounting of the device.

3

Additional Requirements

Transparent IP Address Failover

◆ Include an IP resource for continuous access to the NetBackup server after the servicegroup is switched. Include the first hostname (or multiple lines with aliases and DNSvariations) of this IP address in /usr/openv/netbackup/bp.conf as the lineSERVER = NBUMaster_hostname on each server and client. NetBackup uses ahostname lookup for server authentication to establish and maintain client/servercommunication.

◆ To avoid authentication failures, create SERVER entries in bp.conf for each local(private) VCS cluster hostname member defined in the Netbackup service group’sSystemList attribute.

◆ Include all hostnames in bp.conf if using multiple IP addresses on the NetBackupserver 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 lineFAILOVER_RESTORE_MEDIA_SERVERS = sysa, sysb. Otherwise, you must modifythe NetBackup Media database when the service group is switched. (See theNetBackup documentation.) This feature is available for NetBackup 3.1 and later.

◆ The storage unit definition inside NetBackup uses the VCS-controlled IP resource asNetBackup Host.

Shared Robotic Control

◆ For VCS setups in which robotic control is switched with shared disks as part ofserver failover, the robotic control host must contain the NetBackup service group’shostname of the IP resource. The name of the robotic control host is automaticallychosen by the NetBackup vmconf/tpconfig installation utility. It is the systemname 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 fileby 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.


Setting Up the NetBackup Software in the Cluster

◆ Verify that the NetBackup generic SCSI drivers in /dev/sg are installed on all hostsaccessing the shared tape library. If necessary, use/usr/openv/volmgr/bin/install/sg.install to initialize the sg devices oneach system in the NetBackup service group. To verify that the device names are thesame on all systems, type:

# /usr/openv/volmgr/bin/sgscan

◆ Contact VERITAS Technical Support for assistance with StorageTek tape librariesusing Automated Cartridge System Library Software (ACSLS).

Setting Up the NetBackup Software in the ClusterWhen you install the NetBackup Server software, use /usr/openv as the mount point toaccess 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 clientbinaries are available locally in the /usr/openv directory. When the cluster node isrunning the NetBackup service group, /usr/openv is the mount point for the shareddisk, 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 thenodes in a cluster

◆ You are migrating NetBackup from a single node and need to install NetBackup clientsoftware 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 onecluster node and start the installation. Refer to the NetBackup on HP-UXdocumentation 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 thisclient? (y/n) [y]

Chapter 2, Installing and Configuring the Agent 5


4. When presented with the Platform Client Options menu, choose the HP system thatapplies.

5. Choose the appropriate HP-UX operating system when presented with the choice ofoperating 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 theNetBackup 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 theinstallation, 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 shouldcontain:

◆ 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 througha shared bus (dual-hosted SCSI or fibre-attached).

For example, if vcs-roam is the hostname for the NetBackup resource, vcs-node1 andvcs-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-roamSERVER = vcs-node1SERVER = vcs-node2FAILOVER_RESTORE_MEDIA_SERVERS = vcs-node1, vcs-node2REQUIRED_INTERFACE = vcs-roamCLIENT_NAME = vcs-node1

On vcs-node2:

SERVER = vcs-roamSERVER = vcs-node1SERVER = vcs-node2



FAILOVER_RESTORE_MEDIA_SERVERS = vcs-node1, vcs-node2REQUIRED_INTERFACE = vcs-roamCLIENT_NAME = vcs-node2

Mounting Shared Storage Device to /usr/openv

From one system in the cluster, mount the shared storage device to /usr/openv. Forexample:

# 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 serversoftware on the shared disk. The shared disk must be mounted on one system only at themount point /usr/openv.

1. With the shared disk mounted at /usr/openv, insert the NetBackup DataCenterInstallation 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 installationinstructions.

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, enterthe hostname assigned to the virtual IP address for the NetBackup resource if thisis a clustered master server. If this is a clustered media server (NBUSlave), enterthe hostname of the existing NBU master server.

b. Answer “Y” when prompted to start the NetBackup processes, which arerequired for the installation and configuration of tape and robot devices.

3. Configure the NetBackup software to use the shared robotic tape drive configuredwith a shared path. Refer to the NetBackup on HP-UX documentation.

Proceed to the next section, “Editing the bp.conf File for Shared Disk.”



Editing the bp.conf File for Shared Disk

Edit the file /usr/openv/netbackup/bp.conf on the shared disk. The bp.conf fileshould 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 througha shared bus (dual-hosted SCSI or fibre-attached).

For example, if vcs-roam is the hostname for the NetBackup resource, vcs-node1 andvcs-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-roamSERVER = vcs-node1SERVER = vcs-node2FAILOVER_RESTORE_MEDIA_SERVERS = vcs-node1, vcs-node2REQUIRED_INTERFACE = vcs-roam

Note The VCS enterprise agent for NetBackup changes the SERVER entries in thebp.conf file so that the actual hostname of the node on which NetBackup is beingbrought 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 editthe file /usr/openv/volmgr/vm.conf on the shared disk. The vm.conf file containsthe 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-node1and 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-roamMH_HOST_NAME = vcs-roamDEVICE_HOST = vcs-roam


Installing the Agent Software

Removing NetBackup Startup and Shutdown Scripts

Remove the startup and shutdown scripts for NetBackup that were installed with theNetBackup server software. VCS must control startup and shutdown of the NetBackupprocesses. On the node where the NetBackup server installation was performed, issue thefollowing 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 softwareautomatically mounts the CD as /cdrom/cdrom0. Type the following commandto install the agent:

# cd /cdrom/cdrom0# pkgadd -d .

◆ If you are not running Solaris volume-management software, you must mountthe 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.


A Sample NetBackup Configuration

A Sample NetBackup ConfigurationIn the following example, VCS is configured on a two-system cluster (sysa and sysb), andNetBackup is installed on shared disks.

Sample Configuration on a Two-System Cluster

Shared Disks

Public Network

VCS Private Network

System A System B(sysa) (sysb)

Tape Library


Configuring the Agent

Configuring the AgentYou can configure the NetBackup agent using two methods:

◆ By using VCS Cluster Manager (the VCS graphical user interface) to edit a resourcegroup template for the NetBackup agent. See “Configuring the NetBackup Agentwith Cluster Manager” on page 14), or,

◆ By using the types configuration file and directly editing the main.cf file based onthe sample main.cf supplied with the NetBackup agent (see “Configuring theNetBackup Agent by Editing Configuration Files” on page 16). This method requiresthat VCS be stopped and restarted before the configuration takes effect.

Before you configure the agent, review the following tables that describe the NetBackupresource types and their attributes. The resource type definition files and the samplemain.cf configurations are also shown for reference.



NetBackup Resource Type.

By default, the RestartLimit is set to 2. This default setting activates two restartattempts if the resource offlines unexpectedly. The OnLineRetryLimit andOnLineWaitLimit are set to 1. If an online is ineffective (for example, if a daemon doesnot completely start), this default setting activates a clean action.

Type Definition

type NetBackup (str ServerTypestr RobotDaemonstr MonScriptstatic int OnLineRetryLimit = 1static int OnLineWaitLimit = 1static int RestartLimit = 2NameRule = group.Name + "_" + resource.ServerTypestatic str ArgList[] = { ServerType, RobotDaemon, MonScript }

)

Attributes Type andDimension

Definition

ServerType string-scalar The agent monitors processes as specified by the value ofServerType. The values for ServerType and processesmonitored for each are:

◆ NBUSlave:vmd,Itid,avrd

◆ NBUMaster: bprd, pbdbm, vmd,ltid,avrd

◆ NBUMasterwoMM: bprd, bpdbm (this is the equivalent ofNBUMaster without Media Manager)

The value for ServerType may be a list of process namesenclosed by quotes the names separated by white space. Forexample:

"bprd avrd ltid"

RobotDaemon(optional)

string-scalar Executable file name of the robotic device control daemon asdefined in /usr/openv/volmgr/bin.

MonScript

(optional)

string-scalar Pathname of secondary monitor script. (See page 18 for detailson secondary monitoring.)



Sample Configuration

NetBackup nbugrp_NBUMaster (ServerType = NBUMasterRobotDaemon = ts8dMonScript = ""

)

The figure below illustrates the configuration’s dependency graph.

Dependency Graph

This configuration has one disk group on which a single volume is created. The mountpoint /opt/nbu requires the DiskGroup and Volume resources. The service group IPaddress of the Master server is configured using the IP and NIC resource types. TheMaster 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 thecommand ln -s /opt/nbu /usr/openv to create symbolic links on each clustersystem.

nbucons

nbugrp_hme0

NIC

Mount

Volume

DiskGroup

nbugrp_NBUMaster

opt_nbu

shdg_nbu

shdg

IP

NetBackup


Configuring the NetBackup Agent with Cluster Manager

Configuring the NetBackup Agent with Cluster ManagerA template for the NetBackup resource groups has been automatically installed when youinstalled 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 candynamically 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 VCSengine 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 NetBackupagent 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 NetBackupGroup 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.


Configuring the NetBackup Agent with Cluster Manager

4. Select the NetBackup template (NetBackupGroup) from the list of templates; clickNext.

5. The wizard prompts you with alternate names in case the names in the template clashwith 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; theservice group is dynamically created based on the NetBackup template.

7. Review the service group’s resource attributes, and modify the default values, ifnecessary, in accord with your specific configuration.


Configuring the NetBackup Agent by Editing Configuration Files

Configuring the NetBackup Agent by Editing Configuration FilesFollow the instructions below to configure the agent according to the sampleconfiguration of the Master server:

1. Log in to sysa as root.

If VCS is configured and running on your machine, use the following command tostop 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 step4. 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.cfto match the parameters in your configuration.

4. If you have created a resource tree with your own configuration and want toconfigure 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 sampleconfiguration 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.


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


Modifying the Agent Configuration

Modifying the Agent ConfigurationTo dynamically configure the VCS enterprise agent for NetBackup, see the chapter onreconfiguring VCS from the command line in the VERITAS Cluster Server User’s Guide.

Additional MonitoringThe VCS enterprise agent for NetBackup provides two levels of application monitoring:primary and secondary. The primary level monitors the NetBackup daemon processes toverify that they are continuously active.

The secondary level runs a script for further testing. The pathname to the script, withexecute permissions for root, is defined by the MonScript attribute of the NetBackupagent. A return value of 100 indicates that the test failed and that the resource is offline. Areturn value of 101–110 indicates that the test was successful and that the resource isonline. Other values of the resource state are undefined. (For more information, see thechapter on implementing entry points using scripts in the VERITAS Cluster Server AgentDeveloper’s Guide.)


Disabling the Agent

Disabling the AgentTo disable the agent on a system, you must first switch the NetBackup service group to anOFFLINE state. You can stop the application completely, or switch the agent to anothersystem.

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,” checkthe file /var/VRTSvcs/log/engine_A.log A for a message confirming the agenthas 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 VCSconfiguration. See the chapter on reconfiguring VCS from the command line in theVERITAS Cluster Server User’s Guide.

Removing the AgentType the following command on each system to remove the agent. Answer promptsaccordingly:

# pkgrm VRTSvcsnb


Removing the Agent


Date post:	02-Apr-2018
Category:	Documents
Upload:	ngodang
View:	214 times
Download:	1 times

VERITAS Cluster Server Enterprise Agent 1.3 for NetBackup · If accessing the tape drive through a...

Documents