Chapter 12 Installing and Configuring Sun Cluster HA for NetBackup

This chapter describes the procedures to set up and administer Sun Cluster HA for NetBackup on Sun Cluster servers.

This chapter contains the following procedures.

• "How to Install VERITAS NetBackup"

• "How to Install Sun Cluster HA for NetBackup Packages"

• "How to Register and Configure Sun Cluster HA for NetBackup"

Installing and Configuring Sun Cluster HA for NetBackup

The following table lists the sections that describe the installation and configuration tasks.

Sun Cluster HA for NetBackup Overview

Sun Cluster HA for NetBackup makes the VERITAS NetBackup master server highly available.

The NetBackup master server acts as the centralized administration and scheduling server. Each cluster can have only one NetBackup master server.

The master server communicates with media servers through connections to the public network. Typically, in non-clustered systems, the node that runs the master server is connected to the devices that are used for making and storing backups. However, in the Sun Cluster environment, you must attach backup devices to media servers rather than to master servers. You cannot include backup devices or media servers in the cluster.

NetBackup media servers are the machines that perform backups. Multiple media servers can exist on the local network. You can distribute workload between multiple media servers.

NetBackup clients are processes that run on nodes that are inside or outside of the cluster. The clients transfer data from the machine to be backed up to the master servers and media servers.

NetBackup also includes a NetBackup media manager, which consists of daemons that interact with the backup devices. Sun Cluster does not control the daemons.

Sun Cluster HA for NetBackup only makes the NetBackup master server highly available. VERITAS NetBackup components, agents, add-ons, and the features that use these components are not highly available. For example, online (hot) and warm backups of databases are not highly available because the database backup agents are not under the control of the Sun Cluster framework.

Installation Notes

Note the following considerations before you install VERITAS NetBackup and Sun Cluster HA for NetBackup. Figure 12-1 illustrates the configuration limitations.

• VERITAS NetBackup is a single-instance data service. You cannot run more than one instance of VERITAS NetBackup per cluster.

• You must install NetBackup master servers in a cluster.

• NetBackup clients can exist inside of a cluster or outside of a cluster.

• You cannot include NetBackup media servers and their backup devices (tape libraries, optical readers, and so on) in any cluster.

• The shared disk that is associated with the NetBackup master server should be large enough to accommodate the NetBackup administrative files and logs that accumulate over time. The size of the administrative files and logs depends upon the amount of backup activity that is required for your configuration.

Supported Configurations

The following figure illustrates the supported configuration for Sun Cluster HA for NetBackup.

You must include the NetBackup master server in a cluster. You can attach backup devices only to media servers. You cannot include backup devices and media servers in a cluster.

Communication between NetBackup components occurs only through connections to the public network. If failover or switchover occurs, the components under cluster control fail over or switch over to their backup nodes.

Figure 12-1 Sun Cluster HA for NetBackup Supported Configurations

Installing VERITAS NetBackup

After you install and configure Sun Cluster 3.0, use the following procedure and your VERITAS documentation to install and configure VERITAS NetBackup.

How to Install VERITAS NetBackup

1. Ensure that Sun Cluster is running on all of the nodes.

2. Bring the logical hostname resource online on the node on which you plan to install NetBackup.

   In the examples throughout this procedure, the name nb-master refers to the cluster node that masters NetBackup, and slave-1 refers to the media server.

3. Execute the install script to install the VERITAS NetBackup packages from the VERITAS product CD-ROM into the /usr/openv directories on all of the nodes.

   phys-schost-1# ./install

4. When the menu displays, choose Option 1 (NetBackup).

   This option installs both the Media Manager and the NetBackup software on the server.

5. Follow the prompts in the installation script.

   The installation script adds entries to the /etc/services and /etc/inetd.conf files.

   phys-schost-1# ./install ... Would you like to use "phys-schost-1.somedomain.com" as the configured name of the NetBackup server? (y/n) [y] n ... Enter the name of the NetBackup server: nb-master ... Is nb-master the master server? (y/n) [y] y ... Enter the fully qualified name of a media (slave) server (q to quit)? slave-1

6. Remove the /etc/rc2.d/S77netbackup and /etc/rc0.d/K77netbackup files from each cluster node on which Sun Cluster HA for NetBackup is installed.

   If you remove these files, you prevent NetBackup from starting at boot time.

7. On one node, modify the /usr/openv/netbackup/bp.conf file to specify the following information.

   • SERVER = logical-hostname-resource

     All requests to the backup server originate from the primary node. The server name equals the logical hostname resource.

   • CLIENT_NAME = logical-hostname-resource

     On a cluster that runs Sun Cluster HA for NetBackup, the CLIENT_NAME equals nb-master.

   • REQUIRED_INTERFACE = logical-hostname-resource

     This entry indicates the logical interface that the NetBackup application is to use.

   The resulting file should resemble the following example.

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

8. From one node, put the NetBackup configuration files on a multihost disk.

   Place the files on a disk that is part of a failover disk device group that NetBackup is to use.

   1. Run the following commands from the primary node of the failover disk device group. In this example, the failover disk device group is global.

      # mkdir /global/netbackup # mv /usr/openv/netbackup/bp.conf /global/netbackup # mv /usr/openv/netbackup/db /global/netbackup # mv /usr/openv/volmgr/database /global/netbackup # ln -s /global/netbackup/bp.conf /usr/openv/netbackup/bp.conf # ln -s /global/netbackup/db /usr/openv/netbackup/db # ln -s /global/netbackup/database /usr/openv/volmgr/database

      ---

      Note -

      Run the command scstat -p to identify the primary for a particular disk device group.

      ---

   2. Run the following commands from all of the other nodes.

      # rm -rf /usr/openv/netbackup/bp.conf # rm -rf /usr/openv/netbackup/db # rm -rf /usr/openv/volmgr/database # ln -s /global/netbackup/bp.conf /usr/openv/netbackup/bp.conf # ln -s /global/netbackup/db /usr/openv/netbackup/db # ln -s /global/netbackup/database /usr/openv/volmgr/database

Where to Go From Here

See "Installing Sun Cluster HA for NetBackup Packages" to register Sun Cluster HA for NetBackup and configure the cluster for the data service.

Installing Sun Cluster HA for NetBackup Packages

Use the interactive scinstall(1M) utility to install the Sun Cluster HA for NetBackup package, SUNWscnb, on your cluster.

If you installed the SUNWscnb package as part of your initial Sun Cluster installation, proceed to "Registering and Configuring Sun Cluster HA for NetBackup". Otherwise, use the following procedure to install the SUNWscnb package.

How to Install Sun Cluster HA for NetBackup Packages

You need the Sun Cluster 3.0 Agents 12/01 CD-ROM to complete this procedure. Perform this procedure on all of the cluster nodes that run Sun Cluster HA for NetBackup.

1. Load the Sun Cluster 3.0 Agents 12/01 CD-ROM into the CD-ROM drive.

2. Run the scinstall utility with no options.

   This step starts the scinstall utility in interactive mode.

3. Choose the menu option, Add Support for New Data Service to This Cluster Node.

   The scinstall utility prompts you for additional information.

4. Provide the path to the Sun Cluster 3.0 Agents 12/01 CD-ROM.

   The utility refers to the CD as the "data services cd."

5. Specify the data service to install.

   The scinstall utility lists the data service that you selected and asks you to confirm your choice.

6. Exit the scinstall utility.

7. Unload the CD from the drive.

Where to Go From Here

See "Registering and Configuring Sun Cluster HA for NetBackup" to register Sun Cluster HA for NetBackup and configure the cluster for the data service.

Registering and Configuring Sun Cluster HA for NetBackup

Use the procedures in this section to register and configure Sun Cluster HA for NetBackup as a failover data service.

To configure a data service, you must create resource groups and resources for your application. See Chapter 1 and the Sun Cluster 3.0 12/01 Concepts document for details on resources and resource groups.

How to Register and Configure Sun Cluster HA for NetBackup

This procedure describes how to use the scrgadm(1M) command to register and configure Sun Cluster HA for NetBackup.

Other options also enable you to register and configure the data service. See "Tools for Data-Service Resource Administration" on page 8 for details about these options.

You must have the following information to perform this procedure.

• A list of cluster nodes that can master the data service.

• The network resource that clients use to access the data service. Normally, you set up this IP address when you install the cluster. See the Sun Cluster 3.0 12/01 Concepts document for details on network resources.

Perform this procedure on one cluster member.

1. Become superuser on a cluster member.

2. Run the scrgadm command to register the resource types for the data service.

   Register SUNW.netbackup_master as the resource type.

   # scrgadm -a -t SUNW.netbackup_master

   -a

   Specifies that you are adding a new configuration.

   -t SUNW.netbackup_master

   Specifies the predefined resource type name for your data service.

3. Create a failover resource group to hold the network and application resources.

   You can optionally select the set of nodes that the data service can run on with the -h option, as follows.

   # scrgadm -a -g resource-group [-h nodelist]

   -g resource-group

   Specifies the name of the resource group. Each resource group requires a unique name.

   [-h nodelist]

   Specifies an optional comma-separated list of physical node names or IDs that identify potential masters. The order here determines the order in which the nodes are considered as primary during failover. If all of the nodes in the cluster are potential masters, you do not need to use the -h option.

4. Verify that you have added all of your network resources to the name service database.

   You should have performed this verification during the Sun Cluster installation.

   ---

   Note -

   Ensure that all of the network resources are present in the server's and client's /etc/hosts file to avoid any failures because of name service lookup.

   ---

5. Add a network resource to the resource group.

   # scrgadm -a {-L|-S} -g resource-group -l hostname-list\ [-j resource] [-n netiflist]

   {-L|-S}

   Specifies the type of network resource that the resource group uses. Select either -L, logical hostname resource, or -S, shared address resource.

   -l hostname_list

   Specifies the list of addresses that will be shared.

   [-j resource]

   An optional name for the logical hostname resource. If you do not specify a name, the default resource name is the first name to appear after the -l option.

   [-n netiflist]

   Specifies an optional, comma-separated list that identifies the NAFO groups on each node. All of the nodes in the resource group's nodelist must be represented in netiflist. If you do not specify this option, the scrgadm command attempts to discover a net adapter on the subnet that the hostname-list identifies for each node that is in the nodelist. For example, -n nafo0@nodename, nafo0@nodename2.

6. Create a NetBackup resource in the resource group.

   # scrgadm -a -j resource -g resource-group -t SUNW.netbackup_master

   -j resource

   Specifies the name of the resource to add.

   -g resource-group

   Specifies the name of the resource group into which you are placing the resource.

   -t SUNW.netbackup_master

   Specifies the type of resource to add.

7. Run the scswitch(1M) command to complete the following tasks.

   • Enable the resource and fault monitoring.

   • Move the resource group into a managed state.

   • Bring the resource group online.

   # scswitch -Z -g resource-group

   -Z

   Enables the resource and monitor, moves the resource group to the managed state, and brings the resource group online.

   -g resource-group

   Specifies the name of the resource group.

Example - Registering Sun Cluster HA for NetBackup

The following example shows how to register Sun Cluster HA for NetBackup on a two-node cluster.

Cluster Information
Node names: phys-schost-1, phys-schost-2
Resource Type: SUNW.netbackup_master
Logical hostname resource: nb-master
Resource group: NB-RG (failover resource group)
Netbackup Resources: test-scnb

(Register the NetBackup resource type.)
# scrgadm -a -t SUNW.netbackup_master 

(Add the failover resource group to contain all the resources.)
# scrgadm -a -g NB-RG -h phys-schost-1,phys-schost-2
 
(Add the network resource to the resource group.)
# scrgadm -a -L -g NB-RG -l nb-master 
 
(Add the NetBackup resource to the resource group.)
# scrgadm -a -j test-scnb -g NB-RG -t SUNW.netbackup_master
 
(Bring the resource group online.)
# scswitch -Z -g NB-RG

Configuring Sun Cluster HA for NetBackup Extension Properties

This section describes the Sun Cluster HA for NetBackup extension properties. Typically, you use the command line scrgadm -x parameter=value to configure the extension properties when you create the resource. See Appendix A for details on all of the Sun Cluster properties.

Table 12-2 describes the extension properties that you can set for the NetBackup resource. You can update some extension properties dynamically. You can update others, however, only when you create the resource. In the following table, the Tunable field indicates when you can update each property.

Fault Monitoring Sun Cluster HA for NetBackup

When the application starts, NetBackup starts three daemons-vmd, bprd, and bpdbm. The Sun Cluster HA for NetBackup fault monitor monitors these processes. While the START method runs, the fault monitor waits until the daemons are online before monitoring the application. The Probe_timeout extension property specifies the amount of time that the fault monitor waits.

After the daemons are online, the fault monitor uses kill (pid, 0) to determine whether the daemons are running. If any daemon is not running, the fault monitor initiates the following actions, in order, until all of the probes are running successfully.

1. Restarts the resource on the current node.

2. Restarts the resource group on the current node.

3. Fails over the resource group to the next node on the resource group's nodelist.

All process IDs (PIDs) are stored in a temporary file, /var/run/.netbackup_master.

(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