(Optional) Configuring Non-HA VERITAS Netbackup Clients on a Cluster

Optionally, you can configure NetBackup clients on a cluster that will not run Sun Cluster HA for NetBackup. To do so, use one of the following methods.

• Configure each node as a separate NetBackup client – You can use any of the nodes to backup files on the cluster file system. You can use a particular node's NetBackup client name to backup files that are local to that node.

• Configure one logical hostname resource as the NetBackup client – You cannot configure multiple logical hostname resources on a cluster as NetBackup clients. Furthermore, if you have configured a logical hostname resource as the NetBackup client, you cannot configure any nodes that are potential primaries for that logical hostname as NetBackup clients.

  To configure one logical hostname resource as a NetBackup client, perform the following steps.

  1. On all of the potential primary nodes for the logical hostname resource, modify the file /usr/openv/netbackup/bp.conf so that CLIENT_NAME equals logical-hostname-resource, as follows.

     CLIENT_NAME = logical-hostname-resource

  2. On all of the potential primary nodes for the logical hostname resource, add the following entry to the /usr/openv/netbackup/bp.conf file.

     REQUIRED_INTERFACE = logical-hostname-resource

     ---

     Note –

     If REQUIRED_INTERFACE already exists, modify the entry to equal logical-hostname-resource.

     ---

     If the name of the logical hostname resource is schost-1, for example, the modified file should contain the following entries.

     SERVER = nb-master SERVER = slave-1 CLIENT_NAME = schost-1 REQUIRED_INTERFACE = schost-1