Chapter 14 Installing and Configuring Sun Cluster HA for NetBackup

This chapter describes procedures for setting up and administering the Sun Cluster HA for NetBackup data service on Sun Cluster servers.

This chapter includes the following sections:

• "Sun Cluster HA for NetBackup Overview"

• "Installing VERITAS NetBackup"

• "Installing and Configuring Sun Cluster HA for NetBackup"

Sun Cluster HA for NetBackup Overview

The Sun Cluster HA for NetBackup product consists of a VERITAS NetBackup master server, VERITAS NetBackup slave servers, VERITAS NetBackup clients, and the Sun Cluster HA for NetBackup data service.

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

Typically, in non-clustered systems, the node running the master server is connected to the devices used for making and storing backups. However, in the Sun Cluster environment, the backup devices must be attached to slave servers rather than master servers, and neither backup devices nor slave servers can be included in the cluster. The master server communicates with slave servers through connections to the public network.

The NetBackup slave servers are the machines that actually perform the backups. A cluster can employ zero or more slave servers. Workload can be distributed between multiple slave servers.

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

The product also includes a NetBackup media manager, which consists of daemons that interface with the backup devices. The daemons exist outside the control of Sun Cluster.

Installation Notes

Note the following considerations before installing VERITAS NetBackup and Sun Cluster HA for NetBackup. The configuration limitations are illustrated in Figure 14-1.

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

• NetBackup master servers must be installed in a cluster.

• NetBackup clients can exist inside or outside a cluster.

• NetBackup slave servers and backup devices (tape libraries, optical readers, and so on) cannot be included in any cluster.

• The shared disk 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 required for your configuration.

• Do not add entries for the NetBackup startup and shutdown scripts (S77netbackup and K77netbackup) to any rc script on any cluster node. The NetBackup startup and shutdown scripts must be insulated from cluster node startups and shutdowns.

Supported Configurations

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

The NetBackup master server must be included in a cluster. NetBackup clients can be configured inside or outside a cluster. Backup devices can be attached only to slave servers, and neither can be included in a cluster.

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

Figure 14-1 Sun Cluster HA for NetBackup Supported Configurations

Installing VERITAS NetBackup

After you have installed and configured the Sun Cluster product, install and configure the VERITAS NetBackup product, using the following procedure and your VERITAS documentation.

How to Install VERITAS NetBackup

1. Start Sun Cluster.

2. Install the VERITAS NetBackup packages from the VERITAS product CD-ROM into the /opt/openv directories on all nodes.

   The VERITAS NetBackup product is contained in two packages, SUNWmmgr and SUNWnetbp, available from your VERITAS product CD-ROM.

   ---

   Note -

   On all nodes, install the SUNWmmgr package first and the SUNWnetbp package second. This ordering is necessary because of package dependencies.

   ---

   During package installation, links are created automatically between /usr/openv and /opt/openv.

   # pkgadd -d . SUNWmmgr SUNWnetbp

3. Select a logical host to be the NetBackup master server.

   In the examples throughout this procedure, the name nb-master refers to the logical host mastering NetBackup, and slave-1 refers to the slave server.

4. Run the VERITAS NetBackup post-install script on all cluster nodes.

   1. Switch the NetBackup logical host you selected in Step 3 to its default master, and run the VERITAS NetBackup post-install script from the default master.

      The post-install script is contained in the SUNWnetbp package. When the script prompts you for the name of the master server, you must specify the logical host name rather than the default. No cluster-specific requirements exist for the slave servers--set them up as required for your configuration.

      phys-hahost1# haswitch phys-hahost1 nb-master phys-hahost1# /usr/openv/netbackup/bin/install_bp ... Would you like to use "phys-hahost1.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 ...

   2. Switch the NetBackup logical host to another node, and run the post-install script on that node. Repeat as necessary until you have run the post-install script on all nodes.

      When the script prompts you for the name of the master server, specify the logical host name rather than the defaults, and set up the slave servers as required for your configuration.

      phys-hahost2# haswitch phys-hahost2 nb-master phys-hahost2# /usr/openv/netbackup/bin/install_bp ... Would you like to use "phys-hahost1.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 ...

   3. Switch the NetBackup logical host back to its default master.

      phys-hahost1# haswitch phys-hahost1 nb-master

5. On only the default master, modify the file /usr/openv/netbackup/bp.conf to specify that all requests to the backup server originate from the logical host.

6. Modify the file to specify the logical host as the CLIENT_NAME, and add a new line to specify the logical host as the REQUIRED_INTERFACE. The resulting file should resemble this example, where nb-master is the name of the logical host:

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

7. Move the NetBackup configuration files to the shared disk.

   In this example, diska is the mount point for the shared disk for the logical host nb-master. Run the following commands from the default master of the logical host, nb-master.

   # /usr/openv/netbackup/bin/goodies/K77netbackup # mkdir /diska/netbackup # mv /usr/openv/netbackup/bp.conf /diska/netbackup # mv /usr/openv/netbackup/db /diska/netbackup # mv /usr/openv/volmgr/database /diska/netbackup # ln -s /diska/netbackup/bp.conf /usr/openv/netbackup/bp.conf # ln -s /diska/netbackup/db /usr/openv/netbackup/db # ln -s /diska/netbackup/database /usr/openv/volmgr/database

   Then run the following commands from all other nodes.

   # /usr/openv/netbackup/bin/goodies/K77netbackup # rm -rf /usr/openv/netbackup/bp.conf # rm -rf /usr/openv/netbackup/db # rm -rf /usr/openv/volmgr/database # ln -s /diska/netbackup/bp.conf /usr/openv/netbackup/bp.conf # ln -s /diska/netbackup/db /usr/openv/netbackup/db # ln -s /diska/netbackup/database /usr/openv/volmgr/database

VERITAS NetBackup is now installed. Proceed to "Installing and Configuring Sun Cluster HA for NetBackup".

Installing and Configuring Sun Cluster HA for NetBackup

This section describes the steps to install, configure, register, and start Sun Cluster HA for NetBackup. You must install and set up Sun Cluster and the VERITAS NetBackup product before configuring Sun Cluster HA for NetBackup.

You configure Sun Cluster HA for NetBackup by using the hadsconfig(1M) command. See the hadsconfig(1M) man page for details.

---

Note -

To use NetBackup with this release of Sun Cluster, you must install patches that revise the scinstall(1M) and hadsconfig(1M) commands to recognize Sun Cluster HA for NetBackup. Get the patches from your service provider or from the Sun patch website http://sunsolve.sun.com. Install the patches after you install and configure Sun Cluster but before you install and configure Sun Cluster HA for NetBackup.

---

How to Install and Configure Sun Cluster HA for NetBackup

1. On each Sun Cluster server, install the Sun Cluster HA for NetBackup package, SUNWscnb, if it is not installed already.

   Install the package in the default location on all cluster nodes. See Chapter 3, Installing and Configuring Sun Cluster Software for more information about running scinstall(1M).

2. Register the Sun Cluster HA for NetBackup data service by running the hareg(1M) command.

   Run this command on only one node:

   phys-hahost1# hareg -s -r netbackup

3. Run the hadsconfig(1M) command on one node to configure Sun Cluster HA for NetBackup.

   See "Configuration Parameters for Sun Cluster HA for NetBackup", for information on input to supply to hadsconfig(1M). Run this command on only one node:

   phys-hahost1# hadsconfig

4. Use the hareg(1M) command to start Sun Cluster HA for NetBackup.

   Run this command on only one node:

   phys-hahost1# hareg -y netbackup

   The configuration is complete.

Configuration Parameters for Sun Cluster HA for NetBackup

This section describes the information you supply to the hadsconfig(1M) command to create configuration files for Sun Cluster HA for NetBackup. The hadsconfig(1M) command uses templates to create these configuration files. The templates contain some default, some hard-coded, and some unspecified parameters. You must provide values for those parameters that are unspecified.

Configure Sun Cluster HA for NetBackup by supplying the hadsconfig(1M) command with parameters listed in Table 14-1.

Table 14-1 Configuration Parameters for Sun Cluster HA for NetBackup

Parameter	Description
Name of the instance	Nametag used as an identifier for the instance. The log messages generated by Sun Cluster HA for NetBackup refer to this nametag. The hadsconfig(1M) command prefixes the package name to the value you supply here. For example, if you specify "netbackup," the hadsconfig(1M) command produces "SUNWscnb_netbackup."
Logical host	Name of the logical host that provides service for this instance of Sun Cluster HA for NetBackup, nb-master in the examples in this chapter.
Base install directory	Directory containing the S77netbackup and K77netbackup scripts. Normally this directory is /usr/openv/netbackup/bin/goodies.
Local probe flag	Flag that specifies whether the local probe is started automatically at cluster reconfiguration or when the NetBackup service is activated. The probe runs on the same node as the NetBackup instance. There is no remote probe for this service.Possible values are y or n. The default value is y (automatic restart).
Probe interval	The interval, in seconds, that the probe waits between checks of the service. The default value is 60 seconds.
Number of retries	The number of attempts that will be made to restart a failed NetBackup instance on the local node before resorting to other actions, such as failover or switchover. The default value is 3.
Takeover flag	Flag that specifies whether a failure of this instance will cause a takeover or failover of the logical host associated with the NetBackup instance. Such a takeover or failover occurs only after efforts to revive the service on the local node have failed. Possible values are y or n. The default value is y.