VERITAS NetBackup 6.0 High Availability

(1)

VERITAS NetBackup

™

_{6.0 High}

Availability

System Administrator’s Guide

for UNIX, Windows, and Linux

(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.

VERITAS Legal Notice

Copyright © 2002-2005 VERITAS Software Corporation. All rights reserved. VERITAS, the VERITAS Logo, and NetBackup are trademarks or registered trademarks of VERITAS Software Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners.

Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved. VERITAS Software Corporation

350 Ellis Street Mountain View, CA 94043 USA Phone 650-527-8000 Fax 650-527-2908 www.veritas.com Third-Party Copyrights

(3)

Preface

This guide provides information on how to install and configure NetBackup to work with different clustering solutions.

NetBackup provides high-performance backups and restores for a variety of computer types. Administrators can set up schedules for automatic, unattended backups for clients anywhere in the network. These backups can be full or incremental and are managed entirely by the NetBackup server (also referred to as the NetBackup master server). This guide is intended for the NetBackup system administrator responsible for

configuring NetBackup in a cluster environment. A system administrator is a person with system administrator privileges and responsibilities. This guide assumes:

◆ A basic understanding of Windows or UNIX/Linux system administration. ◆ A working understanding of the NetBackup client software.

◆ A working understanding of the NetBackup server software.

◆ A familiarity with the information covered in the following NetBackup manuals: ◆ NetBackup System Administrator’s Guide, Volume I

◆ NetBackup Troubleshooting Guide

(10)

Getting Help

You can find answers to questions and get help from the NetBackup documentation and from the VERITAS technical support web site.

Finding NetBackup Documentation

A list of the entire NetBackup documentation set appears as an appendix in the NetBackup Release Notes. All NetBackup documents are included in PDF format on the NetBackup Documentation CD.

For definitions of NetBackup terms, consult the online glossary.

▼ To access the NetBackup online glossary

1. In the NetBackup Administration Console, click Help > Help Topics.

2. Click the Contents tab.

3. Click Glossary of NetBackup Terms.

Use the scroll function to navigate through the glossary.

Accessing the VERITAS Technical Support Web Site

The address for the VERITAS Technical Support Web site is http://support.veritas.com. The VERITAS Support Web site lets you do any of the following:

◆ Obtain updated information about NetBackup, including system requirements, supported platforms, and supported peripherals

◆ Contact the VERITAS Technical Support staff and post questions to them ◆ Get the latest patches, upgrades, and utilities

◆ View the NetBackup Frequently Asked Questions (FAQ) page

◆ Search the knowledge base for answers to technical support questions ◆ Receive automatic notice of product updates

◆ Find out about NetBackup training

(11)

Getting Help

From http://support.veritas.com, you can complete various tasks to obtain specific types of support for NetBackup:

1. Subscribe to the VERITAS Email notification service to be informed of software alerts, newly published documentation, Beta programs, and other services.

a. From the main http://support.veritas.com page, select a product family and a product.

b. Under Support Resources, click Email Notifications.

Your customer profile ensures you receive the latest VERITAS technical information pertaining to your specific interests.

2. Locate the telephone support directory at http://support.veritas.com by clicking the

Phone Support icon. A page appears that contains VERITAS support numbers from around the world.

Note Telephone support for NetBackup is only available with a valid support contract. To contact VERITAS for technical support, dial the appropriate phone number listed on the Technical Support Guide included in the product box and have your product license information ready for quick navigation to the proper support group.

3. Contact technical support using e-mail.

a. From the main http://support.veritas.com page, click the E-mail Support icon. A wizard guides you to do the following:

◆ Select a language of your preference ◆ Select a product and a platform

◆ Provide additional contact and product information, and your message ◆ Associate your message with an existing technical support case

(12)

Accessibility Features

Contacting VERITAS Licensing

For license information, you can contact us as follows: ◆ Call 1-800-634-4747 and select option 3

◆ Fax questions to 1-650-527-0952

◆ In the Americas, send e-mail to [email protected].

In the Asia and Pacific areas, send email to [email protected]. In all other areas, send email to [email protected].

Accessibility Features

NetBackup contains features that make the user interface easier to use by people who are visually impaired and by people who have limited dexterity. Accessibility features include:

◆ Support for assistive technologies such as screen readers and voice input (Windows servers only)

◆ Support for keyboard (mouseless) navigation using accelerator keys and mnemonic keys

(13)

Comment on the Documentation

Let us know what you like and dislike about the documentation. Were you able to find the information you needed quickly? Was the information clearly presented? You can report errors and omissions or tell us what you would find useful in future versions of our manuals and online help.

Please include the following information with your comment:

◆ The title and product version of the manual on which you are commenting ◆ The topic (if relevant) on which you are commenting

◆ Your comment ◆ Your name

Email your comment to [email protected].

Please only use this address to comment on product documentation. See “Getting Help” in this preface for information on how to contact Technical Support about our software. We appreciate your feedback.

(14)

(15)

1

Introduction to NetBackup High Availability

Clusters provide high availability of applications and data to users. In a cluster, two or more servers (called nodes) are linked in a network, and run cluster software that allows each node access to the shared disks. If a node becomes unavailable, cluster resources migrate to an available node (this is called failover). The shared disks and the virtual server are kept available. During failover, users experience only a short interruption in service. NetBackup can protect data on shared disks, as well as data on the node’s local disks. NetBackup can also protect databases in a cluster, such as Microsoft Exchange and Oracle, and make use of NetBackup options such as NetBackup Vault.

In this document, Microsoft Cluster Server is also referred to as MSCS, VERITAS Volume Manager as Volume Manager, VERITAS Cluster Server as VCS, HP Tru64 UNIX

(16)

How a NetBackup Failover Server Protects Data in a Cluster

There are several ways to use NetBackup for protecting the data in a cluster environment. The purpose of this document is provide instruction for installing and configuring a highly available (or failover) NetBackup server. Use of standalone media servers and NetBackup clients in a cluster is briefly described in “Non-Failover Cluster

Configurations” on page 103.

When installed as a failover server, a NetBackup server is installed on the cluster as a virtual server application, allowing the server to failover from one of the nodes to the other. The server is assigned a network name resource (the virtual server name), an IP address resource, and a disk resource. The duties of the server fail over from one of the nodes to the other if a failure occurs on the active node. This provides high availability of the NetBackup server itself.

For failover master servers, the virtual server name is used as the name of the master server for all media servers and clients using this master server. For failover media servers, the virtual server name is used in the NetBackup storage unit and added to the server list of any NetBackup clients to be backed up to this media server.

When a failover occurs, backup jobs that were running are rescheduled by using the normal NetBackup retry logic for a failed backup. The NetBackup services are started on another node and the backup processing resumes.

Both types of NetBackup failover servers, master and media, operate in an active/passive failover configuration. The active node and the passive (or failover node) must be the same type of server, master or media. NetBackup does not support mixing the two server types in the same failover server configuration. For example, a master server on one node cannot failover to a media server on another node.

(17)

Supported Cluster Solutions

NetBackup supports the following cluster environments. For more information on installing and configuring NetBackup in that type of cluster, refer to the chapter or document listed in the Table “Supported Cluster Solutions.”

Supported Cluster Solutions

Cluster Solution Refer to...

Microsoft Cluster Server “NetBackup in a Microsoft Cluster Server” on page 7

HP Tru64 UNIX TruCluster “NetBackup in an HP Tru64 UNIX TruCluster” on page 21

VERITAS Cluster Server 4.1 or later on “NetBackup in a VERITAS Cluster Server on Windows

Windows 2000 and Windows 2003 2000 and Windows 2003” on page 47

VERITAS Cluster Server on “NetBackup in a VERITAS Cluster Server on

UNIX/Linux UNIX/Linux” on page 31

Sun Cluster “NetBackup in a Sun Cluster” on page 59

HP MC/Service Guard “NetBackup in a HP MC/Service Guard Cluster” on page 69

Supported NetBackup Database Agents and Options in a

Cluster

To see the list of database agents and NetBackup options that are supported in a clustered environment, refer to the following section “Accessing Compatibility Lists.” For

information on installing and configuring database agents and options in a cluster, refer to the system administrator’s guide for that agent or option.

(18)

Limitations of Using NetBackup with Clustering Solutions

Accessing Compatibility Lists

The VERITAS support web site now contains the most current platform support

information for NetBackup. To locate the latest information on the VERITAS support web site, perform the following procedure.

▼ To access the compatibility lists on the VERITAS support website 1. Go to the VERITAS support web site: http://support.veritas.com.

2. In the Select Product Family list, click NetBackup Products.

3. From the Product list, choose NetBackup Enterprise Server. For Microsoft Cluster Server and VERITAS Cluster Server for Windows, you can also choose NetBackup

Server.

4. Under Support Resources, click Compatibility and Reference.

5. For information on supported cluster environments, see NetBackup (tm) x.x Cluster

Compatibility (updated date).

6. Click on the link for the PDF document.

Limitations of Using NetBackup with Clustering Solutions

The following general limitations exist for NetBackup in a cluster:

◆ NetBackup does not support converting an existing non-failover NetBackup server to a highly available failover NetBackup server. You must uninstall NetBackup, then install again.

◆ All NetBackup nodes within a cluster must be of the same server type. Do not mix master and media servers in a cluster.

◆ NetBackup is not supported as an active/active application in a cluster.

◆ NetBackup Server is only supported with Microsoft Cluster Server and VERITAS Cluster Server for Windows. NetBackup Enterprise Server is supported with all cluster solutions (see “Supported Cluster Solutions” on page 3).

◆ Refer to the NetBackup Release Notes for limitations specific to Media Manager and NetBackup database agents and options.

(19)

Limitations of Using NetBackup with Clustering Solutions

Media Manager Cluster Support Limitations

The following limitations have been identified to affect clustering support in a Media Manager.

◆ Breaking SCSI Reservations

When fail over occurs in an environment where SCSI Reserve/Release is being used (explicitly in NetBackup, or implicitly in lower-level drivers or hardware), a SCSI Reservation remains on the drive. The drive remains unusable by other nodes and other hosts until the SCSI reservation is cleared.

(20)

(21)

2

NetBackup in a Microsoft Cluster Server

This chapter provides information on how to install and configure NetBackup as a highly available application in a Microsoft Cluster Server environment. Refer to the NetBackup Installation Guide and the NetBackup System Administrator's Guide, Volume I, for a detailed understanding of how NetBackup is installed and administered. Refer to the

documentation for MSCS for a detailed understanding of how MSCS works and how it is installed and administered.

For information on other configurations of NetBackup in a cluster, including installing NetBackup as a non-failover server, see “Non-Failover Cluster Configurations” on page 103 and “NetBackup Media Server in a Cluster” on page 111.

(22)

Installation Prerequisites

This section contains information about the requirements that must be met prior to installing and configuring a NetBackup failover server in an MSCS environment. ❏ Verify that your hardware is supported by MSCS and NetBackup 6.0. For a list of

supported storage devices, visit http://support.veritas.com and also consult the MSCS documentation.

❏ Verify that storage devices have been properly installed and configured to work in a Windows environment. Refer to “Configuring Storage Devices for Windows” in the NetBackup Installation Guide.

❏ Verify that Microsoft Cluster Server is correctly installed and configured (all versions are supported with NetBackup 6.0). NetBackup can be installed on as many nodes as MSCS supports. MSCS supports up to 4 or 8 nodes in a cluster, depending on the level of Windows that is installed.

❏ If you want the NetBackup media server to be highly available, the robotic and tape devices must be physically connected to all the nodes that would be part of the NetBackup High Availability setup. This can be done via SCSI or fibre channel.Verify, using operating system commands, that all the devices are connected properly. Refer to the Media Manager Device Configuration Guide.

❏ Verify that you have an IP address and host name (virtual name) to be assigned to the NetBackup cluster group.

❏ Using Cluster Administrator, verify that the Possible Owners list for each disk resource that NetBackup uses includes each node to which NetBackup can failover. ❏ Verify you have the NetBackup Enterprise Server 6.0 or NetBackup Server 6.0

(23)

Installing and Configuring a NetBackup Failover Server on a MSCS Cluster

Installing and Configuring a NetBackup Failover Server on

a MSCS Cluster

The Microsoft Cluster Administrator must be installed on all NetBackup servers (including NetBackup administration clients) that you use to remotely administer the NetBackup failover server (master or media). You must also have administrator rights to the server cluster.

Installation Notes

◆ These instructions assume that this is a new installation of a NetBackup failover server.

◆ The same type of NetBackup server must be installed on each node to which NetBackup may failover. You cannot install both a master server and a media server in the same overlapping failover configuration.

◆ If you install a NetBackup failover media server, ensure that all media server nodes reference the same NetBackup master server name during the install.

Caution After configuring NetBackup as a cluster group in MSCS, do not change the group name.

Installation and Configuration Instructions

▼ To install a NetBackup failover server on a MSCS cluster

1. On each desired node in the cluster, install the NetBackup master or media server.

a. Follow the instructions for installing NetBackup in a clustered environment as described in the NetBackup Installation Guide.

b. When prompted to provide the list of servers, enter all servers that need to have access to the NetBackup failover server.

(24)

Installing and Configuring a NetBackup Failover Server on a MSCS Cluster

2. If you added license keys at the end of the installation, these keys must be added to each node in the cluster by failing over to and adding the keys to each node in the cluster. Refer to “Adding License Keys” on page 94.

3. Install any agents or options that require separate installations.

Most Windows agents and options only require a special license key and do not require a separate installation. See the appropriate NetBackup documentation for the specific database agent or option for more information.

4. After the installation is complete, continue with the configuration of NetBackup. ◆ Refer to “NetBackup Configuration Guidelines” on page 79 for guidelines on

configuring NetBackup.

◆ Refer to “Device Configuration Guidelines” on page 80 and “Configuring Devices for MSCS, VCS, Sun Cluster, or Service Guard” on page 81 for guidelines and instructions on configuring devices in a cluster. Note that devices must be configured on each node in the cluster.

◆ See “Configuring NetBackup Catalog Backups in a Cluster” on page 83 for instructions on verifying that the entries for the NetBackup Catalog backups are correct. Catalog backup information is stored on the shared disk and do not need to be configured for each node.

◆ See “Configuring Backup Polices” on page 86 for instructions on verifying that the entries for the NetBackup Catalog backups are correct. Backup policies are stored on the shared disk and do not need to be configured for each node. ◆ By default, NetBackup options (such as NetBackup Vault) will not cause

NetBackup to failover if they fail. You can configure NetBackup options to failover NetBackup if a service or the option fails. For more information, see “Configuring Add-Ons for Monitoring (MSCS)” on page 91.

5. When you have completed the configuration of NetBackup, verify that NetBackup can fail over properly in the cluster. Refer to “Verifying NetBackup Configuration” on page 89.

6. If the cluster configuration does not complete successfully, refer to the next section “Running bpclusterutil” for instructions on running bpclusterutil manually.

(25)

Running bpclusterutil

Under normal circumstances, cluster configuration is one of the final steps in installing NetBackup in a cluster. If this step is not done or does not complete successfully, you can use the bpclusterutil command to perform this step.

See the Appendix “bpclusterutil” on page 119 for more details on this command.

▼ To reconfigure NetBackup for the cluster

1. From the active node, run the following command. bpclusterutil -ci

2. Recreate the database.

3. Run the following commands: tpext

(26)

Upgrading a NetBackup Failover Server

This section describes how to upgrade a failover server from NetBackup 5.0 or 5.1 to 6.0.

Note NetBackup does not support converting an existing non-failover NetBackup server to a highly available failover NetBackup server.

▼ To upgrade a NetBackup failover server

1. Ensure a good backup of your cluster environment exists that includes the NetBackup databases and catalogs.

Note If in a Windows 2000 environment, perform the upgrade installation directly from the system console. Do not use Remote Terminal Services.

2. Ensure the server list for each NetBackup server running outside of the cluster contains the name of each node on which NetBackup can run and the name of the virtual server.

3. Take the all NetBackup resources offline except for the disk resource before beginning the upgrade install.

4. Follow the instructions for upgrading NetBackup in a clustered environment as described in the NetBackup Installation Guide. The installation program will: ◆ Upgrade NetBackup on the active node.

◆ Push the install to each inactive node. ◆ Bring NetBackup resources online.

(27)

Performing Backups and Restores in a MSCS Cluster

5. Review and complete the process for creating and populating the EMM database (or running nbpushdata) in the NetBackup Installation Guide. Run this command from the active node.

Caution It is imperative that you follow the sequence below when running the nbpushdatacommand in your NetBackup environment.

1. 5.0 MP4 (or later) or 5.1 Global Device Database Host

2. Master servers

3. Volume Database Hosts

4. Any remaining media servers that have been upgraded the Netbackup 6.0

6. Upgrade and configure any database agents or options.

Most agents and options require only a license key and do not need to be upgraded separately. For information on installing and configuring a specific agent or option, see the appropriate NetBackup documentation for that agent or option.

Performing Backups and Restores in a MSCS Cluster

For complete instructions on recovering MSCS cluster nodes, refer to the following Microsoft Document. VERITAS only provides instructions for restoring objects that you have backed up using NetBackup. Server Clusters: Backup and Recovery Best Practices for Windows Server 2003 which can be found on the Microsoft web site:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/ clustering/sercbrbp.mspx

The following topics describe how to restore the cluster quorum. Additional guidelines and instructions for backups and restores are covered in the chapter “Using NetBackup to Perform Backups and Restores in a Cluster” on page 95.

(28)

Restoring the Cluster Quorum

The cluster quorum is backed up as part of System State or Shadow Copy Components for each node. To restore the cluster quorum, other nodes in the cluster must be offline. If you cannot take the other nodes in the cluster offline before restoring the cluster quorum, follow the instructions in the next procedure.

▼ To force the restore of the cluster quorum when other nodes are online 1. Create the following registry entry:

HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\ Config\Cluster_Database_Force_Restore

Note The actual registry entry above must be on a single line.

If required, create this registry value as data type REG_SZ with a value of YES. When this value is set, the cluster service is stopped for any nodes that are online.

2. If Active Directory is running on the target server or the target server is currently a domain controller, see “Restoring Cluster Quorum to a Node With Directory Services” on page 15.

▼ To restore the cluster quorum

1. If the other nodes in the cluster are online, create the registry entry described in the previous procedure.

2. In the NetBackup Backup, Archive, and Restore interface, open a Restore window.

3. Select the backup image (or range of images) that contains the the backup of the System State or Shadow Copy Components for this node of the cluster.

4. In the All Folders pane, select System_State or Shadow Copy Components.

5. If the disk where the cluster quorum previously resided has been changed, you may have to set the registry entry described above to force the restore to continue. The disk could have been replaced with a new one, or the disk configuration could have been changed so that the cluster quorum now resides on a different disk. This enables the drive letter of the disk that the cluster quorum was on to remain the same, even if the configuration has changed and the disk signatures contained in the restore media do not match the disk signatures contained in the cluster quorum.

(29)

6. Continue the restore.

7. When the restore operation is complete, either reboot the cluster node or use the Microsoft Cluster Administrator to restart the cluster service on any nodes where it was stopped.

Restoring Cluster Quorum to a Node With Directory Services

To restore the quorum to a node that is running Active Directory or to a node that is currently a domain controller, the node must be in Directory Services Restore Mode. The cluster services cannot run in this mode, so the cluster quorum must be restored

separately, after System State or Shadow Copy Components is restored and the node has been rebooted.

▼ To restore the cluster quorum to a node running Active Directory or that is currently a domain controller

1. In the NetBackup Backup, Archive, and Restore interface, open a Restore window.

2. Select the backup image (or range of images) that contains the backup you wish to restore.

3. Select System_State or Shadow Copy Components.

4. Exclude the cluster quorum from this restore by expanding System_State or Shadow

Copy Components and deselecting Cluster_Database .

5. Continue the restore.

6. When the restore operation is complete, reboot the cluster node in safe (repair) mode (restart the computer and press F8 when prompted to select an operating system) and then select Directory Services Restore Mode.

7. Start the NetBackup service(s).

(30)

9. If the disk where the cluster quorum previously resided has been changed, you may have to set the registry entry described above to force the restore to continue. The disk could have been replaced with a new one, or the disk configuration could have been changed so that the cluster quorum now resides on a different disk. This enables the drive letter of the disk that the cluster quorum was on to remain the same, even if the configuration has changed and the disk signatures contained in the restore media do not match the disk signatures contained in the cluster quorum.

10. Continue the restore.

11. When the restore is complete, reboot the target node.

12. Use Microsoft Cluster Administrator to restart the cluster service on any nodes on which it was stopped.

(31)

_____________________________________________

_____________________________________________ Preparing for Disaster Recovery of A Cluster

Preparing for Disaster Recovery of A Cluster

For complete instructions on recovery of MSCS, refer to the following Microsoft

Document. VERITAS only provide instructions for restoring objects that you have backed up using NetBackup. Server Clusters: Backup and Recovery Best Practices for Windows Server 2003 which can be found on the Microsoft web site:

http://ww.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/ clustering/sercbrbp.mspx

If a disaster occurs, the following information is required to successfully recover the cluster.

General Cluster Information

Cluster name _____________________________________________

Cluster IP address and subnet mask _____________________________________________

Cluster node names _____________________________________________

Node IP addresses _____________________________________________

Local and shared drive letters and partition _____________________________________________ scheme Cluster Groups Group name _____________________________________________ Preferred nodes _____________________________________________ Failover/failback policies _____________________________________________ Cluster Resources Resource name _____________________________________________

(32)

Disaster Recovery of A MSCS Cluster

Restart and Looks Alive/Is Alive properties _____________________________________________

Resource-related parameters _____________________________________________

Disaster Recovery of A MSCS Cluster

Several scenarios are discussed in this section:

◆ To recover the entire cluster, see the next topic, “Recovering the Entire Cluster”. ◆ To recover all shared disks, see “Recovering All Shared Disks” on page 19.

◆ To recover the shared disk that the NetBackup application resides on, see “Recovering NetBackup Data on a Shared Disk” on page 20.

Recovering the Entire Cluster

▼ To recover the nodes to their pre-disaster state

1. On the first node you want to recover, reinstall the Windows operating system, including the last service pack applied before the failure.

2. Install any other drivers or applications to make the node operational.

Note After booting the nodes in a cluster, ensure that the drive letters match the original cluster configuration. If the original configuration does not match, you can use the Disk Administrator, to some extent, to control the hard drive numbering scheme that Windows devises.

3. On all remaining nodes you need to recover, reinstall Windows, including the last service pack applied before the failure. Also, see the previous note.

4. Reinstall the cluster services and bring the cluster online.

5. Reinstall the same NetBackup software on the cluster that was installed before the failure.

6. Use the appropriate NetBackup catalog recovery procedure to restore the NetBackup catalog information before continuing.

See the NetBackup Troubleshooting Guide for more information on recovering the NetBackup catalog database.

(33)

7. Restore the data files through the virtual server.

8. If you must restore a database to the shared drives, see the system administrator’s guide for your database agent to continue the restore.

Recovering All Shared Disks

▼ To recover all shared disks

1. Uninstall the cluster software from both nodes.

2. Replace and repartition the shared disks.

3. Reinstall the cluster software.

4. Ensure all NetBackup shared disks are assigned the same drive letters used when NetBackup was originally installed and configured.

5. To reconfigure NetBackup for the cluster, do the following on the active node:

a. Run the following command. bpclusterutil -ci

b. Recreate the database.

c. Run the following commands: tpext

bpclusterutil -online

6. Use the appropriate NetBackup catalog recovery procedure to restore the NetBackup catalog information on the shared disk before continuing. See the NetBackup

Troubleshooting Guide for more information on recovering the NetBackup catalog database.

(34)

Recovering NetBackup Data on a Shared Disk

If you must recover the shared disk that was used for the NetBackup failover server, use the appropriate NetBackup catalog recovery procedure to restore the NetBackup catalog information on the shared disk. See the NetBackup Troubleshooting Guide for more

(35)

3

NetBackup in an HP Tru64 UNIX TruCluster

This chapter provides information on how to install, configure and use NetBackup Enterprise Server as a highly available application in a TruCluster environment. For information about NetBackup, refer to the NetBackup System Administrator's Guide, Volume I. For information about TruCluster, refer to the TruCluster User's Guide.

(36)

The CAA Facility

Since all nodes in a TruCluster have access to all installed software within the cluster, there must to be a way to differentiate the single node that is to run the server software. In a typical NetBackup installation, a script starts and stops the server software. In a TruCluster, this script would be executed on all machines in the cluster. As a result, a number of processes are started on each machine. Where these machines are configured as servers this is problematic. HP’s CAA (Cluster Application Availability) facility can control the node on which NetBackup will run.

The CAA facility provides monitoring and resource control and the ability to switch applications between nodes in a cluster. Once NetBackup is registered with CAA, this facility can be used to control upon which node an application can be active. When configuring a failover server, you will run the cluster_config script, which will register NetBackup with CAA and create the scripts used to start, stop, and monitor NetBackup.

CAA provides two controls:

caa_start <netbackup_group> brings the NetBackup daemons online caa_stop <netbackup_group> takes the NetBackup daemons offline

If you experience caa_stop failures for NetBackup, you may want to consider increasing the script timeout value. The default is 180 seconds but sometimes this is not enough for a heavily loaded machine to shut down all of the robotic daemons. The same is true of machines with several tape drives attached in a SAN configuration. To see if this solution is correct for you, use bpps -a to check which daemons are running immediately after the error. If it is a robotic daemon, increasing the timeout will most likely fix your problem. The script timeout value is part of TruCluster profile property; use the caa_profile TruCluster command to change this value.

(37)

Installation Prerequisites

❏ Verify all hardware (used for nodes) is supported by your version of TruCluster and by NetBackup Enterprise Server 6.0. For a list of supported storage devices, visit http://support.veritas.com and consult the TruCluster documentation.

❏ Verify that TruCluster 5.1b is correctly installed and configured.

❏ Verify that you have an IP address and host name (virtual name) to be assigned to the NetBackup resource in VCS.

❏ Make sure that each node in the cluster, on which you wish to install NetBackup, is rsh equivalent. As the root user you need to be able to perform a remote login to each node without entering a password. This is only necessary for installation, upgrades, and configuration of the NetBackup server and any NetBackup database agents and options. Once installation and configuration is complete this is no longer required. ❏ If you want the NetBackup media server to be highly available, the robotic and tape

devices must be physically connected to all the nodes that would be part of the NetBackup High Availability setup. This can be done via SCSI or fibre channel.Verify, using operating system commands, that all the devices are connected properly. Refer to the Media Manager Device Configuration Guide.

❏ Verify you have the NetBackup Enterprise Server 6.0 installation media and a valid license key.

Installing a NetBackup Server on a TruCluster

This section describes how to install NetBackup Enterprise Server as a failover application on a TruCluster.

Installation Notes

◆ These instructions assume that this is a new installation of a NetBackup server. ◆ Converting an existing non-failover NetBackup server to a highly available failover

(38)

Installing a NetBackup Server on a TruCluster

Installing and Configuring NetBackup as a Failover Server

▼ To install and configure NetBackup as a failover server in a TruCluster

1. Follow the instructions for installing a non-failover NetBackup server as described in the NetBackup Installation Guide.

The NetBackup server software (master or media) can be installed on any node in the cluster. During installation, specify the cluster alias as the server name.

2. Run the following command:

/usr/openv/netbackup/bin/cluster/cluster_config

3. For the TruCluster NetBackup service/profile name, indicate a new name for this configuration.

4. Specify the cluster alias to be used by NetBackup.

Caution You must provide the same cluster alias that you provided during the installation. This name is also case-sensitive. If applicable, provide the fully qualified name. For example, if you indicate the name

“clusternbu.domain.com” during installation, but “clusternbu” or “CLUSTERNBU.DOMAIN.COM” for the cluster_config script, the configuration process will fail.

If this is a new cluster alias, indicate the cluster alias IP address to be used by

NetBackup. This should already be configured in the /etc/hosts file, or in DNS, or NIS. Also provide the cluster alias IP subnet to be used by CAA. This is the network subnet for the cluster alias IP address. For instance, an IP address of 10.80.136.119 on a network with a netmask of 255.255.248.0 would have a subnet of 10.80.136.0.

5. Provide a list of the cluster members on which NetBackup may run. Separate member names with a space and list them in the preferred order.

6. On the summary screen, review the information you provided.

Note If you chose to use a pre-existing cluster alias, the IP and subnet fields will be blank.

The script will:

◆ Create and register a CAA profile for the NetBackup application. ◆ Create and register a cluster alias (if a new alias was specified).

◆ Remove the S77NetBackup and K77NetBackup scripts from /sbin/rc0.d and /sbin/rc2.d directories.

(39)

◆ Update the bp.conf and vm.conf files. ◆ Set up the EMM database, if required. ◆ Start the NetBackup server.

7. You are now able to start and stop NetBackup with the following commands: caa_start profile_name

caa_stop profile_name

For example, with a caa registered profile named “netbackup” for NetBackup server, you can start and stop the application with the following commands:

caa_start netbackup caa_stop netbackup

You must use the caa commands in place of the standard NetBackup start and stop script. The standard script does not track which node the software is running on and allows multiple instances of NetBackup within the cluster.

8. Install any NetBackup database agents or options.

Note You must freeze NetBackup before installing any agents or options. Refer to the next section, “Installing and Upgrading Database Agents and Options” on page 27.

9. Continue with the configuration of NetBackup.

◆ All servers outside of the cluster that need to access the NetBackup failover server must be added to the servers list in the host properties or in the bp.conf. ◆ Refer to “NetBackup Configuration Guidelines” on page 79 for guidelines on

configuring NetBackup.

◆ Refer to “Device Configuration Guidelines” on page 80 and “Configuring Devices for a TruCluster” on page 82 for guidelines and instructions on configuring devices in a cluster. Note that devices must be configured on each node in the cluster.

(40)

◆ See “Configuring Backup Polices” on page 86 for instructions on verifying that the entries for the NetBackup Catalog backups are correct. Backup policies are stored on the shared disk and do not need to be configured for each node.

10. When you have completed configuration of NetBackup, verify that NetBackup can failover properly in the cluster. Refer to “Verifying NetBackup Configuration” on page 89.

(41)

Installing and Upgrading Database Agents and Options

In a TruCluster, NetBackup database agents and options are installed or upgraded as in anon-cluster environment. Before beginning the installation or upgrade, the NetBackup must be frozen.

▼ To install or upgrade a NetBackup agent or option 1. Freeze NetBackup by running the following command:

caa_stop profile_name

2. Install the database agents and options as you would in a non-clustered environment. Refer to the system administrator’s guides for those agents or options.

3. Unfreeze NetBackup by running the following command: caa_start profile_name

4. (Optional) Configure robot daemons and NetBackup options to failover NetBackup if a daemon or the option fails.

By default, robotic daemons and NetBackup options (such as NetBackup Vault) will not cause NetBackup to failover if they fail. For more information, see “Configuring Robotic Daemons for Monitoring (UNIX/Linux Clusters)” on page 90 and

(42)

Applying a Patch to a NetBackup Failover Server

Follow these instructions when applying patches to a NetBackup failover server. See the NetBackup Release Notes for the latest information on applying a specific patch.

▼ To apply a patch to a NetBackup failover server

2. Login to the node NetBackup is running on.

3. Stop the NetBackup server using the command caa_stop profile name.

4. Complete the patch install.

5. Start NetBackup using the command caa_start profile name.

6. Verify that NetBackup can failover properly in the cluster. Refer to “Verifying NetBackup Configuration” on page 89.

Upgrading a Failover Server

This section describes how to upgrade a failover server from NetBackup 5.0 or 5.1 to 6.0.

▼ To upgrade a failover server

2. Stop the NetBackup server using the following command. caa_stop profile_name

3. In the bp.conf, verify that any CLUSTER_NAME entries are defined as the virtual server name.

4. In the vm.conf:

◆ Verify that any CLUSTER_NAME entries are defined as the virtual server name. ◆ If it exists, change the REQUIRED_INTERFACE entry to CLUSTER_NAME and

(43)

Upgrading a Failover Server

5. Follow the instructions for upgrading a non-failover NetBackup server as described in the NetBackup Installation Guide.

6. Review and complete the process for creating and populating the EMM database (or running nbpushdata) in the NetBackup Installation Guide.

Caution It is imperative that you follow the sequence below when running the nbpushdatacommand in your NetBackup environment.

1. 5.0 MP4 (or later) or 5.1 Global Device Database Host

2. Master servers

3. Volume Database Hosts

4. Any remaining media servers that have been upgraded the Netbackup 6.0

7. Upgrade any NetBackup database agents or options.

Note You must freeze NetBackup before upgrading any agents or options. Refer to “Installing and Upgrading Database Agents and Options” on page 27.

8. Verify that NetBackup can failover properly in the cluster. Refer to “Verifying NetBackup Configuration” on page 89.

(44)

Performing Backups and Restores in a TruCluster

The process of configuring and performing backups and performing restores in any supported cluster is similar no matter which clustering solution you are using. Guidelines and instructions for backups and restores are covered in the chapter “Using NetBackup to Perform Backups and Restores in a Cluster” on page 95.

(45)

4

NetBackup in a VERITAS Cluster Server on

UNIX/Linux

This chapter describes the steps to install and configure a NetBackup Enterprise Server in as a highly available application in a VCS environment on UNIX or Linux. VCS is a high-availability solution for cluster configurations. VCS enables you to monitor systems and application services, and to restart services on a different system when hardware or software fails.

For information about VCS, refer to the VERITAS Cluster Server User's Guide. For more detailed information about this agent, refer to “NetBackup Agent for VERITAS Cluster Server for UNIX/Linux” on page 127. For information on other configurations of NetBackup in a cluster, including installing NetBackup as a non-failover server, see “Non-Failover Cluster Configurations” on page 103 and “NetBackup Media Server in a Cluster” on page 111.

(46)

Installation Prerequisites

This section contains information about the requirements that must be met prior to installing and configuring a NetBackup failover server in a VCS 3.5 or later environment. ❏ PBX has a known issue that prevents it from being installed in the cluster using the

push installation method you can usually employ with installics. To install PBX in a cluster, you must run the installics command on every node.

❏ Verify that your hardware is supported by VCS and by NetBackup Enterprise Server 6.0. For a list of supported storage devices, visit http://support.veritas.com.

❏ Verify that VCS is correctly installed and configured on Solaris, HP-UX, AIX, or Linux. Follow the steps in the VERITAS Cluster Server Installation Guide.

❏ The shared disk must be configured and accessible to all cluster nodes on which NetBackup will be installed.

❏ Verify that you have an IP address and host name (virtual name) to be assigned to the NetBackup resource in VCS.

❏ Make sure that each node in the cluster, on which you wish to install NetBackup, is rshequivalent (On HP the command is remsh). As the root user you need to be able to perform a remote login to each node in the cluster without entering a password. This is only necessary for installation, upgrades, and configuration of the NetBackup server and any NetBackup database agents and options. Once installation and configuration is complete this is no longer required.

❏ If you want the NetBackup media server to be highly available, the robotic and tape devices must be physically connected to all the nodes that would be part of the NetBackup High Availability setup. This can be done using SCSI or fibre

channel.Verify that all the devices are connected properly. Refer to the Media Manager Device Configuration Guide.

❏ Verify you have the NetBackup Enterprise Server 6.0 installation media and a valid license key.

(47)

__________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________ __________________________________

Pre-Installation Checklist for a NetBackup Failover Server Installation

Pre-Installation Checklist for a NetBackup Failover Server

Installation

Note The configuration utility will treat all attribute values globally.

Virtual Name for NetBackup: __________________________________

IP Address: __________________________________

Subnet mask __________________________________

Network Device Name (NIC) __________________________________

Nodes on which NetBackup server is installed

(48)

For VCS Solaris and Linux

Scenario 1 - Using VxVM

Resource Example

Disk Group Resource:

DiskGroup:__________________________ nbudg StartVolumes: _______________________ 0 or 1 StopVolumes: _______________________ 0 or 1 Volume Resource: (optional)

Volume: _____________________________ nbuvol Mount Resource

MountPoint: _________________________ /opt/VRTSnbu

BlockDevice:_________________________ /dev/vx/dsk/nbuvol FS Type:_____________________________ vxfs

Mount Option: _______________________ (this is optional)

Fsck Option: _________________________ (if you add other options, -y is also required)

(49)

Scenario 2- Disk Only, No Volume Manager

Mount Resource

MountPoint: ____________________________ /opt/VRTSnbu BlockDevice: ____________________________ /dev/dsk/c1t1dos3 FS Type: ________________________________ vxfs

Mount Option: __________________________ (this is optional)

Fsck Option: ____________________________ (if you add other options, -y is also required)

(50)

For VCS AIX

Scenario 1 - Using VxVM

DiskGroup: __________________________ nbudg StartVolumes: _______________________ 0 or 1 StopVolumes: ________________________ 0 or 1 Volume Resource: Volume: ____________________________ nbuvol Mount Resource MountPoint: _________________________ /opt/VRTSnbu BlockDevice: ________________________ /dev/vx/dsk/nbuvol FS Type: _____________________________ vxfs is required

Mount Option: ______________________ (optional)

(51)

Scenario 2 - Using AIX LVMVG

LVMVG Resource:

VolumeGroup: ___________________________ nbuvg MajorNumber: __________________________ 58

Disks: __________________________________ hdisk1 or hdisk2 ImportvgOpt: ____________________________ (optional) VaryonvgOpt: ___________________________ (optional) SyncODM: ______________________________ (optional) Mount Resource: MountPoint: _____________________________ /opt/VRTSnbu BlockDevice:_____________________________ /dev/nbudev FS Type:_________________________________ jfs2

Mount Option: ___________________________ (optional)

Fsck Option: _____________________________ (if you add other options, -y is also required)

(52)

Scenario 3 - Disk Only, No Volume Manager

Mount Resource:

MountPoint:_____________________________ /opt/VRTSnbu BlockDevice: ____________________________ /dev/dsk/c1t1dos3 FS Type: ________________________________ jfs2

Mount Option: __________________________ (optional)

Fsck Option:_____________________________ (if you add other options, -y is also required)

(53)

For VCS HP-UX

Scenario 1 - Using VxVM

DiskGroup: __________________________ nbudg StartVolumes: _______________________ 0 or 1 StopVolumes: _______________________ 0 or 1 Volume Resource: Volume: _____________________________ nbuvol Mount Resource: MountPoint: _________________________ /opt/VRTSnbu BlockDevice:_________________________ /dev/vx/dsk/nbuvol FS Type:_____________________________ vxfs is required

Mount Option: _______________________ (optional)

Scenario 2 - Using Logical Volume Manager

LVMVolume Group Resource:

(54)

Scenario 3 - Disk Only, No Volume Manager

Mount Resource:

MountPoint: _____________________________ /opt/VRTSnbu BlockDevice:_____________________________ /dev/dsk/c1t1dos3 FS Type:_________________________________ hfs

Mount Option: ___________________________ (optional)

Fsck Option: _____________________________ (if you add other options, -y is also required)

(55)

Installing and Configuring a Failover NetBackup Server

This section describes how to install and configure a new NetBackup failover server. If you are upgrading from NetBackup 5.0 or 5.1 to 6.0, refer to “Upgrading a NetBackup Failover Server” on page 45.

Installation Notes

◆ These instructions assume that this is a new installation of a NetBackup failover server.

◆ You must install the same type of NetBackup server on each node to which

NetBackup may failover. You cannot install a master server and a media server in a failover configuration.

◆ If you are installing a NetBackup failover media server, ensure that all media server nodes reference the same NetBackup master server name during the install.

◆ Do not install older versions of the VCS agent. Use the version of the agent provided with NetBackup 6.0. This agent is installed along with the NetBackup 6.0 Server software. The cluster_config script is only supported with versions of the VCS agent included with NetBackup 5.0 or later.

Installation and Configuration Instructions

▼ To install and configure a NetBackup failover server

1. Fill out the appropriate sections, based on your environment, of the checklist in the section “Pre-Installation Checklist for a NetBackup Failover Server Installation” on page 33.

2. Make sure the shared disk is not mounted on any node in the cluster.

If applicable, unmount the NetBackup shared mount point. Stop the volume the mount point is on and stop the disk group for that volume on all nodes of the cluster.

(56)

Installing and Configuring a Failover NetBackup Server

Be sure that you:

◆ Install NetBackup on each node to which it can failover. ◆ Use the virtual name for the NetBackup server name.

4. After installing NetBackup on each node, run the following command on the primary node:

/usr/openv/netbackup/bin/cluster/cluster_config

5. Answer questions based on the information gathered in step 1.

Caution When prompted, you must provide the same virtual cluster name that you provided during the installation. This name is also case-sensitive. If applicable, provide the fully qualified name. For example, if you indicate the name “clusternbu.domain.com” during installation, but “clusternbu” or “CLUSTERNBU.DOMAIN.COM” for the cluster_config script, the configuration process will fail.

The script will:

◆ Create and register a cluster alias (if a new alias was specified). ◆ Remove NetBackup start and stop scripts from the rc directories. ◆ Update the bp.conf and vm.conf files.

◆ Set up the EMM database, if required. ◆ Start the NetBackup server.

6. Install any NetBackup database agents or options.

Note You must freeze the NetBackup group before installing any agents or options. Refer to the next section, “Installing and Upgrading NetBackup Database Agents and Options.”

7. Continue with the configuration of NetBackup.

◆ All servers outside of the cluster that need to access the NetBackup failover server must be added to the servers list in the host properties or in the bp.conf on each node.

◆ Refer to “NetBackup Configuration Guidelines” on page 79 for guidelines on configuring NetBackup.

(57)

Installing and Upgrading NetBackup Database Agents and Options

◆ Refer to “Device Configuration Guidelines” on page 80 and “Configuring Devices for MSCS, VCS, Sun Cluster, or Service Guard” on page 81 for guidelines and instructions on configuring devices in a cluster. Note that devices must be configured on each node in the cluster.

◆ See “Configuring Backup Polices” on page 86 for instructions on verifying that the entries for the NetBackup Catalog backups are correct. Backup policies are stored on the shared disk and do not need to be configured for each node.

8. When you have completed configuration of NetBackup, verify that NetBackup can failover properly in the cluster. Refer to “Verifying NetBackup Configuration” on page 89.

Installing and Upgrading NetBackup Database Agents and

Options

Install or upgrade NetBackup database agents and options on all cluster nodes where the NetBackup server is installed. In addition, the NetBackup group must be frozen before you install any agents or options.

Note Before upgrading an database agents or options, ensure NetBackup is up and running (the NetBackup resource is online in the cluster, server processes are running onthe active node).

▼ To install or upgrade a NetBackup agent or option

1. Freeze the NetBackup group using hagrp -freeze nbu group name .

2. On each inactive node in the cluster on which NetBackup is installed, install any agents or options. See the appropriate NetBackup documentation for the agent or option for installation and configuration instructions.

(58)

Installing and Upgrading NetBackup Database Agents and Options

4. Unfreeze the NetBackup group using hagrp -unfreeze nbu group name.

5. (Optional) Configure robot daemons and NetBackup options to failover NetBackup if a daemon or the option fails.

By default, robotic daemons and NetBackup options (such as NetBackup Vault) will not cause NetBackup to failover if they fail. For more information, see “Configuring Robotic Daemons for Monitoring (UNIX/Linux Clusters)” on page 90 and

(59)

Upgrading a NetBackup Failover Server

Follow these instructions when upgrading a NetBackup failover server from version 5.0 or 5.1 to 6.0.

Note VERITAS requires that you use the latest VCS agent that is installed with NetBackup 6.0. Older versions of the agent are not supported.

▼ To upgrade a NetBackup failover server 1. Make sure the NetBackup group is online.

3. Ensure the server list for each NetBackup server running outside of the cluster contains the name of each node on which NetBackup can run and the name of the virtual server.

4. Freeze the NetBackup group using hagrp -freeze nbu_group_name .

Note If the NetBackup resource faults during the upgrade, clear the fault.

5. On each inactive node to which NetBackup may failover, install the NetBackup server software.

◆ Follow the instructions for upgrading NetBackup servers and clients as described in the NetBackup Installation Guide.

◆ If required to specify the server name, provide the virtual name of the server. ◆ If necessary, refer to the VERITAS Infrastructure Core Services Installation Guide for

details on installing PBX.

6. On the active node, install the NetBackup server software.

Follow the instructions for upgrading NetBackup servers and clients as described in the NetBackup Installation Guide.