netbackup ha

NetBackup High AvailabilityAdministrator's Guide

for Windows, UNIX, and Linux

Release 7.0

NetBackup High Availability Administrator's GuideThe software described in this book is furnished under a license agreement and may be usedonly in accordance with the terms of the agreement.

Documentation version: 7.0

Legal NoticeCopyright © 2009 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo are trademarks or registered trademarks of SymantecCorporation or its affiliates in the U.S. and other countries. Other names may be trademarksof their respective owners.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The License Agreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see the Third Party Legal Notice Appendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer softwareas defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software and Documentation by the U.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. The Technical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, the Technical Support group works with Product Engineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s maintenance offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers automatic software upgrade protection

■ Global support that is available 24 hours a day, 7 days a week

■ Advanced features, including Account Management Services

For information about Symantec’s Maintenance Programs, you can visit our Website at the following URL:

www.symantec.com/techsupp/

Contacting Technical SupportCustomers with a current maintenance agreement may access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer on which the problem occurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system



■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf your Symantec product requires registration or a license key, access our technicalsupport Web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with the following types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and maintenance contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



Maintenance agreement resourcesIf you want to contact Symantec regarding an existing maintenance agreement,please contact the maintenance agreement administration team for your regionas follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you to maximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

These solutions provide early warning of cyber attacks, comprehensive threatanalysis, and countermeasures to prevent attacks before they occur.

Symantec Early Warning Solutions

These services remove the burden of managing and monitoring security devicesand events, ensuring rapid response to real threats.

Managed Security Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trusted partners. Symantec Consulting Services offer a varietyof prepackaged and customizable options that include assessment, design,implementation, monitoring, and management capabilities. Each is focused onestablishing and maintaining the integrity and availability of your IT resources.

Consulting Services

Educational Services provide a full array of technical training, securityeducation, security certification, and awareness communication programs.

Educational Services

To access more information about Enterprise services, please visit our Web siteat the following URL:

www.symantec.com

Select your country or language from the site index.

mailto:[email protected]



www.symantec.com

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 Introduction to NetBackup high availability . . . . . . . . . . . . . . . . . . 13

About this guide .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Other relevant guides ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

About NetBackup high availability ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14About NetBackup failover server data protection in a cluster ... . . . . . . . . . . . . 14About NetBackup failover server support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15About NetBackup supported cluster solutions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15About supported NetBackup database agents and options in a

cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Accessing NetBackup cluster compatibility lists ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16LiveUpdate ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17About NetBackup with clustering solutions limitations .... . . . . . . . . . . . . . . . . . . . 17

Chapter 2 NetBackup in a Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . 19

About NetBackup in a Microsoft Cluster Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20About limitations of NetBackup in an MSCS cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . 20About the installation prerequisites for NetBackup in an MSCS

cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Installation notes for a NetBackup failover server on an MSCS

cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Installing a NetBackup failover server in an MSCS cluster ... . . . . . . . . . . . . . . . . 22Configuring a NetBackup server in the cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Reconfiguring NetBackup for the cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Upgrading a NetBackup failover server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Performing backups and restores in an MSCS cluster ... . . . . . . . . . . . . . . . . . . . . . . . 25Restoring the cluster quorum .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Restoring cluster quorum to a node with directory services ... . . . . . . . . . . . . . . 27Preparing for disaster recovery of a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Disaster recovery of a Microsoft Cluster Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Recovering the entire cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Recovering all shared disks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Recovering NetBackup data on a shared disk .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Contents

Chapter 3 NetBackup in a Veritas Cluster Server onUNIX/Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

About NetBackup in a Veritas Cluster Server on UNIX/Linux .... . . . . . . . . . . . . 33Supported VCS options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Installation prerequisites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Preinstallation checklist for a NetBackup failover server

installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35About installation of NetBackup with all VCS

configurations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35About installation of NetBackup with VCS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Installing and configuring a failover NetBackup server ... . . . . . . . . . . . . . . . . . . . . 38Installation notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Installation and configuration instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Installing or upgrading NetBackup database agents and options .... . . . . . . . 40Upgrading a NetBackup failover server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Performing backups and restores in a VCS cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 4 NetBackup in a Veritas Cluster Server on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

About NetBackup in a Veritas Cluster Server on Windows .... . . . . . . . . . . . . . . . 46About the NetBackup agent for VCS .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46About NetBackup agent for VCS agent functions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Additional monitoring for NetBackup agent for VCS .... . . . . . . . . . . . . . . . . . . . . . . . 47Supported VCS options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Installation prerequisites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Installing and configuring a NetBackup failover server on a VCS

cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Installation notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Installation and configuration instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Reconfiguring NetBackup for the cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Upgrading a NetBackup failover server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Performing backups and restores in a VCS cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 52About detailed monitoring for the NetBackup server ... . . . . . . . . . . . . . . . . . . . . . . . 53Setting up a detailed monitoring script for the NetBackup server in

a VCS for Windows environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Enabling detailed monitoring in VCS Cluster Manager for the

NetBackup server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Disabling detailed monitoring in VCS Cluster Manager for the

NetBackup server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Contents8

Chapter 5 NetBackup in a SunCluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

About NetBackup in a SunCluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Installation prerequisites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58General prerequisites for installing NetBackup in a SunCluster

environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58HA Storage Plus prerequisites when installing NetBackup in a

SunCluster environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Global File System prerequisites when installing NetBackup in a

SunCluster environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Preinstallation checklist for a NetBackup failover server

installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Installing and configuring NetBackup in a SunCluster ... . . . . . . . . . . . . . . . . . . . . . 59

Installation notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Installation and configuration instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Installing or upgrading NetBackup database agents and options .... . . . . . . . 62Upgrading a NetBackup failover server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Bringing the NetBackup resource group online or offline ... . . . . . . . . . . . . . . . . . . 64Performing backups and restores in a SunCluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 6 NetBackup in an HP MC/Service Guard cluster . . . . . . . . . . . . 67

About NetBackup in an HP MC/Service Guard cluster ... . . . . . . . . . . . . . . . . . . . . . . 67Limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Installation prerequisites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Preinstallation checklist for a NetBackup failover server

installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69About installation of NetBackup with all HP MC/Service Guard

cluster configurations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69About installation of NetBackup with HP MC/Service Guard

.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Installation and configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Installation notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Installation and configuration instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Installing or upgrading NetBackup database agents and options .... . . . . . . . 73Upgrading a NetBackup failover server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Bringing the NetBackup resource group online or offline ... . . . . . . . . . . . . . . . . . . 76Performing backups and restores in an HP MC/Service Guard

Cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 7 NetBackup in an HACMP cluster for AIX . . . . . . . . . . . . . . . . . . . . . . . . 77

About NetBackup in an HACMP cluster for AIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Installation prerequisites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

9Contents

Preinstallation checklist for a NetBackup failover serverinstallation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79About installation of NetBackup with all HACMP cluster

configurations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79About installation of NetBackup with HACMP cluster ... . . . . . . . . . . . . . . . 79

Installation and configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Installation and configuration instructions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Installing NetBackup database agents and options .... . . . . . . . . . . . . . . . . . . . . . . . . . 82Upgrading a NetBackup failover server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Bringing the NetBackup resource group online or offline ... . . . . . . . . . . . . . . . . . . 86Performing backups and restores in an HACMP Cluster ... . . . . . . . . . . . . . . . . . . . . 86

Chapter 8 Configuring NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90NetBackup configuration guidelines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Device configuration guidelines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Configuring devices ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Configuring NetBackup catalog backups in a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . 94Configuring backup policies for a NetBackup clustered server ... . . . . . . . . . . . 95What to back up .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Backing up local disks in a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Backing up the shared disks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Backing up database files in a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97User backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Verifying NetBackup configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Configuring robotic daemons for monitoring (UNIX/Linux

clusters) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Configuring additional services (UNIX/Linux clusters) ... . . . . . . . . . . . . . . . . . . . . 99Configuring add-ons for monitoring (UNIX/Linux clusters) ... . . . . . . . . . . . . . . . 99Configuring additional services (Windows) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Configuring add-ons for monitoring (Windows) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Adding license keys ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Chapter 9 Using NetBackup to perform backups and restoresin a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

About performing backups and restores with NetBackup in acluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Performing user-directed backups with NetBackup in a cluster ... . . . . . . . . 104Restoring data in a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Example - Restoring data in a NetBackup cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Contents10

Chapter 10 Operational notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

General notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Delay in detecting of loss of connection (MSCS and VCS on

Windows) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108MSCS clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Managing the NetBackup cluster application .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

About UNIX and Linux logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110About Windows logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Appendix A Non-failover cluster configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Overview of non-failover cluster configurations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Non-failover media servers in a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Installing NetBackup non-failover media servers in a cluster ... . . . . . . . . . . . 112Configuring NetBackup non-failover media servers in a cluster ... . . . . . . . . 112Upgrading an existing NetBackup non-failover server in a

cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112NetBackup client in a cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Appendix B NetBackup master server in a cluster using multipleinterfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Example scenario ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Appendix C Moving NBDB database files in a UNIX/Linuxcluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Moving the database to additional shared disks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Appendix D Virtual storage units with a standalone mediaserver in a NetBackup cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

About virtual storage units with a standalone media server in aNetBackup cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Installation prerequisites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122About configuration of virtual storage units with a standalone media

server in a NetBackup cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Tape storage devices ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

11Contents

Disk storage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Upgrading a NetBackup media server in a cluster with virtual storage

units ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Contents12

Introduction to NetBackuphigh availability

This chapter includes the following topics:

■ About this guide

■ About NetBackup high availability

■ About NetBackup failover server data protection in a cluster

■ About NetBackup failover server support

■ About NetBackup supported cluster solutions

■ About supported NetBackup database agents and options in a cluster

■ Accessing NetBackup cluster compatibility lists

■ LiveUpdate

■ About NetBackup with clustering solutions limitations

About this guideThe NetBackup High Availability Administrator's Guide provides informationabout making NetBackup highly available. Use theNetBackup High AvailabilityAdministrator's Guide to configure a highly available master server .

Other relevant guidesYou may need to refer to the following documents for information aboutconfiguring NetBackup Access Control (NBAC) and making it highly available.

1Chapter

NetBackup Security and Encryption GuideRefer to the NetBackup Security and Encryption Guide for information aboutconfiguring NBAC in clustered and non-clustered modes. TheNetBackupSecurityand Encryption Guide also provides information about securing NetBackup ingeneral, including encrypting the data.

For latest updates and additional information, please refer to:

http://entsupport.symantec.com/docs/336967

Symantec Infrastructure Core Services Installation GuideYou need to install AT and AZ components to enable NBAC on the master server.Please refer to the Symantec Infrastructure Core Services Installation Guide foradditional information about installing AT and AZ. Symantec Infrastructure CoreServices Installation Guide also provides information about making AT and AZhighly available.

About NetBackup high availabilityClusters provide high availability of applications and data to users. In a cluster,two or more servers (called nodes) are linked in a network. These servers run thecluster software that allows each node access to the shared disks. If a node becomesunavailable, cluster resources migrate to an available node (this process is calledfailover). The shared disks and the virtual server are kept available. During failover,users experience only a short interruption in service.

In this topic, the various cluster solutions are abbreviated as follows:

■ Microsoft Cluster Server as MSCS

■ Veritas Volume Manager as Volume Manager

■ Veritas Cluster Server as VCS

■ HP MC/Service Guard as Service Guard

■ IBM’s High Availability Cluster Multiprocessing as HACMP

About NetBackup failover server data protection ina cluster

NetBackup protects the data in a cluster environment in several ways.

When NetBackup is installed as a failover server, a NetBackup server is installedon the cluster as a virtual server application. Then the server can fail over from

Introduction to NetBackup high availabilityAbout NetBackup high availability

14


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. TheNetBackup server fails over from one node to another if a failure occurs on theactive node. This failover provides high availability of the NetBackup server itself.

For failover master servers, the virtual server name is used as the name of themaster server. This virtual name is used for all media servers and clients that usethis master server.

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

The NetBackup failover master servers and media servers operate in an active ora passive failover configuration. The active node and the passive (or failover node)must be the same version of the master server.

The use of stand-alone media servers and NetBackup clients in a cluster is alsobriefly described later in this document.

See “Overview of non-failover cluster configurations” on page 111.

About NetBackup failover server supportFor the NetBackup 7.0 release, the master server supports both configuration andupgrade. Whereas, only upgrade is supported for the media servers. For moreinformation about supported NetBackup versions for upgrade, refer to theNetBackup Installation Guide.

The upgrade procedure for master and media server is the same. Follow theinstructions that are described in the Upgarding a NetBackup failover serversection for each clustering technology in this guide.

About NetBackup supported cluster solutionsNetBackup supports several cluster environments. More information is availableon how to install and configure NetBackup in particular type of cluster.

Table 1-1 includes the topics that describe how to install and configure NetBackupin each supported cluster environment.

Table 1-1 Supported cluster solutions

SeeCluster solution

About NetBackup in a Microsoft Cluster ServerMicrosoft Cluster Server

15Introduction to NetBackup high availabilityAbout NetBackup failover server support

Table 1-1 Supported cluster solutions (continued)

SeeCluster solution

About NetBackup in a Veritas Cluster Server on WindowsVeritas Cluster ServerWindows 2003, 2008, 2008R2

About NetBackup in a Veritas Cluster Server on UNIX/LinuxVeritas Cluster Server onUNIX/Linux

About NetBackup in a SunClusterSunCluster

About NetBackup in an HP MC/Service Guard clusterHP MC/Service Guard

About NetBackup in an HACMP cluster for AIXHACMP for AIX

About supported NetBackup database agents andoptions in a cluster

Only certain database agents and NetBackup options are supported in a clusteredenvironment.

See “Accessing NetBackup cluster compatibility lists” on page 16.

For information on how to install and configure database agents and options ina cluster, refer to the administrator’s guide for that agent or option.

Accessing NetBackup cluster compatibility listsThe Symantec Support Web site now contains the most current platform supportinformation for NetBackup. To locate the latest information on the Web site,perform the following procedure.

To access NetBackup cluster compatibility lists

1 Go to the following Web site:

http://entsupport.symantec.com

2 In the FindYourProduct box, type NetBackup Enterprise Server and clickthe > option.

For Microsoft Cluster Server and Veritas Cluster Server for Windows, youalso can indicate NetBackup Server.

3 From the list on the right, click Compatibility List.

Introduction to NetBackup high availabilityAbout supported NetBackup database agents and options in a cluster

16


4 For information on supported cluster environments, see the following list:

Symantec NetBackup (tm) Enterprise Serverx.x / NetBackup Serverx.xClusterCompatibility (updated date).

For x.x, look for the current release. For date, look for the most recent date.

5 Click the link for the PDF document.

LiveUpdateInformation is available on how to configure LiveUpdate to work with a clusteredNetBackup server.

See the NetBackup Installation Guide.

AboutNetBackupwith clustering solutions limitationsThe following general limitations exist for NetBackup in a cluster:

■ NetBackup does not support the conversion of an existing non-failoverNetBackup server to a failover NetBackup server. Contact Symantec Enterprisetechnical support .

■ All NetBackup nodes within a cluster must be of the same server type andversion.

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

■ NetBackup Server is only supported with Microsoft Cluster Server and VeritasCluster Server for Windows.

■ NetBackup Enterprise Server is supported with all cluster solutionsSee “About NetBackup supported cluster solutions” on page 15.

■ Refer to the NetBackup Release Notes for limitations specific to NetBackupdatabase agents and options. Refer to the NetBackup Administrator’s Guidefor limitations specific to Media Manager.

17Introduction to NetBackup high availabilityLiveUpdate

Introduction to NetBackup high availabilityAbout NetBackup with clustering solutions limitations

18

NetBackup in a MicrosoftCluster Server


■ About NetBackup in a Microsoft Cluster Server

■ About limitations of NetBackup in an MSCS cluster

■ About the installation prerequisites for NetBackup in an MSCS cluster

■ Installation notes for a NetBackup failover server on an MSCS cluster

■ Installing a NetBackup failover server in an MSCS cluster

■ Configuring a NetBackup server in the cluster

■ Reconfiguring NetBackup for the cluster

■ Upgrading a NetBackup failover server

■ Performing backups and restores in an MSCS cluster

■ Restoring the cluster quorum

■ Restoring cluster quorum to a node with directory services

■ Preparing for disaster recovery of a cluster

■ Disaster recovery of a Microsoft Cluster Server

■ Recovering the entire cluster

■ Recovering all shared disks

■ Recovering NetBackup data on a shared disk

2Chapter

About NetBackup in a Microsoft Cluster ServerThis topic provides information on how to install and configure NetBackup as ahighly available application in a Microsoft Cluster Server environment. For detailedinformation of how NetBackup is installed and administered, See the NetBackupInstallation Guide and NetBackup Administrator's Guide, Volume I

Refer to the documentation for MSCS for a detailed understanding of how MSCSworks and how it is installed and administered.

NetBackup can be configured in a cluster as a non-failover server and as astandalone media server with virtual storage units.


See “About virtual storage units with a standalone media server in a NetBackupcluster” on page 121.

About limitations of NetBackup in an MSCS clusterFlashBackup is not supported for shared disks in an MSCS environment.

About the installation prerequisites for NetBackupin an MSCS cluster

The following requirements must be met before you install and configure aNetBackup failover server in an MSCS environment:

■ Verify that MSCS and NetBackup 7.0 support your hardware. For a list ofsupported storage devices, visit the following Web site. Also consult the MSCSdocumentation.http://entsupport.symantec.com

■ Verify that storage devices are properly installed and configured to work in aWindows environment. Refer to the information on configuring storage devicesin the NetBackup Installation Guide.

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

■ Physically connect the robotic devices and tape devices to each node whereyou want to install NetBackup). Connect devices by SCSI or fibre channel. UseOS commands to verify that all the devices are connected properly.See the NetBackup Device Configuration Guide.

NetBackup in a Microsoft Cluster ServerAbout NetBackup in a Microsoft Cluster Server

20


■ Verify that you have an IP address and host name (virtual name) to be assignedto the NetBackup cluster group. Only use these for the NetBackup clustergroup.Also, verify that the disk resource is online on the node from which theNetBackup installation will be performed for the first time on the cluster.

■ Use Cluster Administrator to verify that the Possible Owners list for each diskresource that NetBackup uses includes each node to which NetBackup canfailover.

■ Verify that you have the NetBackup Enterprise Server 7.0 or NetBackup Server7.0 installation program and a valid license key.

■ The Microsoft Cluster Administrator must be installed on all NetBackup serversthat you use to administer the NetBackup failover master server remotely.Microsoft Cluster Administrator must also be installed on any NetBackupadministration clients.

■ You must have administrator rights or domain administrator credentials ofthe server cluster.

■ On Windows 2003, the public network names must be same on both nodes ofthe cluster for push-installs.

Installation notes for a NetBackup failover server onan MSCS cluster

Before you begin installation, review the following notes:

■ These instructions assume that this installation is a new installation of aNetBackup failover server.To upgrade NetBackup rather than complete an initial installation, you followa different procedure.See “Upgrading a NetBackup failover server” on page 25.

■ You must install the same type of NetBackup server on each node to whichNetBackup may failover.

■ The virtual name cannot be more than 15 characters because of a Microsoftlimitation.

Note: After you configure NetBackup as a cluster group in MSCS, do not changethe group name.

21NetBackup in a Microsoft Cluster ServerInstallation notes for a NetBackup failover server on an MSCS cluster

Installing a NetBackup failover server in an MSCScluster

This topic describes how to install a new NetBackup Enterprise Server orNetBackup Server as a failover application in an MSCS cluster.

The installation program does the following:

■ Installs NetBackup on the node with shared disk resource online

■ Pushes the install to each inactive node, including the single license key youprovided for a master server installation.

■ Brings NetBackup resources online.

To upgrade NetBackup rather than complete an initial installation, you follow adifferent procedure.

See “Upgrading a NetBackup failover server” on page 25.

Review the following topic before you install NetBackup in an MSCS cluster.

See “Installation notes for a NetBackup failover server on an MSCS cluster”on page 21.

To install a NetBackup failover server in an MSCS cluster

1 Install NetBackup on all nodes of the cluster. This can be done in the followingways:

■ Install on the cluster node (with shared disk online) and push install toall other nodes in the cluster.

■ Install on the cluster node (with shared disk online). After the first nodeinstallation manually install on all other nodes in the cluster.

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

2 When you are prompted to provide the list of servers, enter all servers thatneed to have access to the NetBackup failover server.

3 If you added license keys at the end of the installation, failover and add thesekeys to each node in the cluster.

See “Adding license keys” on page 101.

NetBackup in a Microsoft Cluster ServerInstalling a NetBackup failover server in an MSCS cluster

22

4 Install any agents or options that require separate installations.

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

See “Configuring a NetBackup server in the cluster” on page 23.

5 After the installation is complete, continue with the configuration ofNetBackup.

Configuring a NetBackup server in the clusterTo configure NetBackup server in a cluster, do the following:

■ Review the guidelines for how to configure NetBackup.See “NetBackup configuration guidelines” on page 91.

■ Configure the devices in the cluster.See “Device configuration guidelines” on page 92.See “Configuring devices” on page 93.Note that devices must be configured on each node in the cluster.

■ Verify that the entries for the NetBackup Catalog backups are correct.See “Configuring NetBackup catalog backups in a cluster” on page 94.Catalog backup information is stored on the shared disk and does not need tobe configured for each node.

■ Configure backup policies. Backup policies are stored on the shared disk anddo not need to be configured for each node.See “Configuring backup policies for a NetBackup clustered server” on page 95.

■ By default, NetBackup options (such as NetBackup Vault) do not causeNetBackup to failover if they fail. You can configure NetBackup options tofailover NetBackup if a service or the option fails.See “Configuring add-ons for monitoring (Windows)” on page 100.

■ When you have completed the configuration of NetBackup, verify thatNetBackup can fail over properly in the cluster.See “Verifying NetBackup configuration” on page 98.

■ If the cluster configuration does not complete successfully, an error messageis displayed. Run bpclusterutil manually.

See “Reconfiguring NetBackup for the cluster” on page 24.

23NetBackup in a Microsoft Cluster ServerConfiguring a NetBackup server in the cluster

Reconfiguring NetBackup for the clusterUnder normal circumstances, cluster configuration is one of the final steps in theinstallation of NetBackup in a cluster. If you receive an error message duringinstallation, you can use the bpclusterutil command to perform this step. Moredetails on this command are available.

To reconfigure NetBackup for the cluster

1 From the active node, run the following command.

bpclusterutil -ci

2 If the NetBackup database was not created, create the database. Run thefollowing command:

install_path\NetBackup\bin\create_nbdb.exe -db_server server_name

-data data_directory -index index_directory

-tlog log_directory -staging staging_directory

The server name and directory names are as follows:

The server name in

install_path\NetBackupDB\conf\server.conf

The server name is NB_server_name. For example,NB_ROULETTE.

server_name

install_path\NetBackupDB\datadata_directory

install_path\NetBackupDB\dataindex_directory

install_path\NetBackupDB\datalog_directory

install_path\NetBackupDB\stagingstaging_directory

Refer to theNetBackup Commands Guide forWindows for more informationabout this command.

3 Run the following commands:

tpext

bpclusterutil -online

NetBackup in a Microsoft Cluster ServerReconfiguring NetBackup for the cluster

24

Upgrading a NetBackup failover serverFollow these instructions if you want to upgrade from 6.0 or 6.5.

Note: NetBackup does not support conversion of an existing non-failoverNetBackup server to a failover NetBackup server. Contact Symantec EnterpriseTechnical Support.

To upgrade a NetBackup failover server

1 Ensure a good backup of your cluster environment exists that includes acatalog backup.

See “Configuring NetBackup catalog backups in a cluster” on page 94.

2 For each NetBackup server that runs outside of the cluster, ensure that theserver list is accurate. This list should contain the name of each node whereNetBackup can run and the name of the virtual server.

3 Take the all NetBackup resources offline except for the disk resource beforeyou begin the upgrade install.

4 Follow the instructions for how to upgrade NetBackup in a clusteredenvironment as described in the NetBackup Installation Guide.


■ Upgrade NetBackup on the active node.

■ Push the install to each inactive node.

■ Bring NetBackup resources online.

5 Upgrade and configure any database agents or options.

Most agents and options require only a license key and do not need to beupgraded separately. For information on how to install and configure a specificagent or option, see the appropriate NetBackup documentation for that agentor option.

Performing backups and restores in anMSCS clusterSymantec only provides instructions for how to restore the objects that you havebacked up with NetBackup. For complete instructions on recovering MSCS clusternodes, refer to the Microsoft Document ServerClusters: BackupandRecoveryBestPractices forWindows Server 2003. You can find this document on the MicrosoftWeb site:

25NetBackup in a Microsoft Cluster ServerUpgrading a NetBackup failover server

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

The process to configure and perform backups or to perform restores in a clusteris similar no matter which cluster solution you have. Additional guidelines andinstructions for how to perform backup and restores with NetBackup are coveredin later in this document.

See “About performing backups and restores with NetBackup in a cluster”on page 103.

Restoring the cluster quorumThe cluster quorum is backed up as part of System State or Shadow CopyComponents for each node. To restore the cluster quorum, other nodes in thecluster must be offline. If you cannot take the other nodes in the cluster offlinebefore you restore the cluster quorum, follow the instructions in the nextprocedure.

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

The actual registry entry must be on a single line. If required, create thisregistry value as data type REG_SZ with a value of YES. When this value isset, 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 iscurrently a domain controller the restore procedure is different.

See “Restoring cluster quorum to a node with directory services” on page 27.

To restore the cluster quorum

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

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

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

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

NetBackup in a Microsoft Cluster ServerRestoring the cluster quorum

26



5 If the disk where the cluster quorum previously resided has been changed,you may have to set the registry entry. This action forces the restore tocontinue.

See “To force the restore of the cluster quorum when other nodes are online”on page 26.

The disk may have been replaced with a new one. Or the disk configurationmay have been changed so that the cluster quorum now resides on a differentdisk. In the latter case, the drive letter can remain the same for the disk thatcontained the cluster quorum. The drive letter can remain the same even ifthe configuration has changed. It can also remain the same if the disksignatures in the restore media do not match the signatures in the clusterquorum.

6 Continue the restore.

7 When the restore operation is complete, restart the cluster node. Or use theMicrosoft Cluster Administrator to restart the cluster service on any nodeswhere it was stopped.

Restoring cluster quorum to a node with directoryservices

To restore the quorum to a node that is running Active Directory or to a node thatis currently a domain controller, the node must be in Directory Services RestoreMode. The cluster services cannot run in this mode. So the cluster quorum mustbe restored separately, after the System State or the Shadow Copy Componentsis restored and after the node is restarted.

To restore the cluster quorum to a node running active directory or that is currentlya domain controller

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

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

3 Exclude the cluster quorum from the restore, as follows:

■ For Windows 2000, expand System_State and then deselectCluster_Database.

■ For Windows 2003, expand Shadow Copy Components > System Stateand then deselect Cluster_Quorum.


27NetBackup in a Microsoft Cluster ServerRestoring cluster quorum to a node with directory services

5 When the restore operation is complete, restart the cluster node in Safe(repair) mode. Then select Directory Services Restore Mode.

6 Start the NetBackup service(s).

7 Open the NetBackup Backup, Archive, and Restore interface.

8 Select only the cluster quorum, as follows:

■ For Windows 2000, expand System_State and select onlyCluster_Database.

■ For Windows 2003, expand Shadow Copy Components > System Stateand select only Cluster_Quorum.

9 If the disk where the cluster quorum previously resided has been changed,you may have to set the registry entry. This action forces the restore tocontinue.

See “To force the restore of the cluster quorum when other nodes are online”on page 26.

The disk may have been replaced with a new one. Or the disk configurationmay have been changed so that the cluster quorum now resides on a differentdisk. In the latter case, the drive letter can remain the same for the disk thatcontained the cluster quorum. The drive letter can remain the same even ifthe configuration has changed. It can also remain the same if the disksignatures in the restore media do not match the signatures in the clusterquorum.


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

12 Use Microsoft Cluster Administrator to restart the cluster service on anynodes where it was stopped.

Preparing for disaster recovery of a clusterFor complete instructions on recovery of MSCS, refer to the following MicrosoftDocument. Symantec only provides instructions for how to restore the objectsthat you have backed up with NetBackup. Refer to Server Clusters: Backup andRecovery Best Practices for Windows Server 2003, which can be found on theMicrosoft Web site:


INSERT TABLE HERE: Comment pending

NetBackup in a Microsoft Cluster ServerPreparing for disaster recovery of a cluster

28



Disaster recovery of a Microsoft Cluster ServerSeveral scenarios are discussed in the following topics:

■ Recovering the entire cluster

■ Recovering all shared disks

■ Recovering NetBackup data on a shared diskDescribes how to recover the shared disk where the NetBackup applicationresides.

Recovering the entire clusterThe following procedure describes how to recover the nodes in a cluster to theirpre-disaster state.

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 that was applied before the failure.

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

3 After you start the nodes in a cluster, ensure that the drive letters match theoriginal cluster configuration. If the original configuration does not match,you can use the Disk Administrator to control the hard drive numberingscheme that Windows devises.

4 On all remaining nodes you need to recover, reinstall Windows, including thelast service pack that was applied before the failure. Also, see the previousnote.

5 Reinstall the cluster services and bring the cluster online.

6 Reinstall the same NetBackup software on the cluster that was installed beforethe failure.

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

See theNetBackupTroubleshootingGuide for more information on recoveringthe NetBackup catalog database.

8 If the clustered NetBackup server is a media server, verify that the restoredvm.conf file contains the correct host-specific MM_SERVER_NAMEconfiguration entry for the active node. If MM_SERVER_NAME is differentfrom the local host name, server name to the local host name:

MM_SERVER_NAME=local host name

29NetBackup in a Microsoft Cluster ServerDisaster recovery of a Microsoft Cluster Server

9 Restore the data files through the virtual server.

10 If you must restore a database to the shared drives, see the Administrator’sGuide for your database agent to continue the restore.

Recovering all shared disksThe following procedure describes how to recover the shared disks in a cluster.

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 that all NetBackup shared disks are assigned the same drive lettersthat were used when NetBackup was originally installed and configured.

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

■ Run the following command.

bpclusterutil -ci

■ Recreate the database.

■ Run the following commands:

tpext


6 Use the appropriate NetBackup catalog recovery procedure to restore theNetBackup catalog information on the shared disk before continuing. See theNetBackup Troubleshooting Guide for more information on recovering theNetBackup catalog database.

7 If the clustered NetBackup server is a media server, verify that the restoredvm.conf file contains the correct host-specific MM_SERVER_NAMEconfiguration entry for the active node. If MM_SERVER_NAME is differentfrom the local host name, server name to the local host name:


8 Use NetBackup to restore any data on the shared disks. For details on how toperform a restore, see the NetBackup Backup, Archive, and Restore GettingStarted Guide.

NetBackup in a Microsoft Cluster ServerRecovering all shared disks

30

Recovering NetBackup data on a shared diskTo recover the shared disk that the NetBackup failover server used, follow theappropriate NetBackup catalog recovery procedure to restore the cataloginformation on the shared disk.

If the clustered NetBackup server is a media server, verify that the restored vm.conffile contains the correct host-specific MM_SERVER_NAME configuration entryfor the active node. If MM_SERVER_NAME is different from the local host name,server name to the local host name:


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

31NetBackup in a Microsoft Cluster ServerRecovering NetBackup data on a shared disk

NetBackup in a Microsoft Cluster ServerRecovering NetBackup data on a shared disk

32

NetBackup in a VeritasCluster Server onUNIX/Linux


■ About NetBackup in a Veritas Cluster Server on UNIX/Linux

■ Supported VCS options

■ Installation prerequisites

■ Preinstallation checklist for a NetBackup failover server installation

■ Installing and configuring a failover NetBackup server

■ Installing or upgrading NetBackup database agents and options


■ Performing backups and restores in a VCS cluster

About NetBackup in a Veritas Cluster Server onUNIX/Linux

This topic describes the steps to install and configure a NetBackup EnterpriseServer as a highly available application in a VCS environment on UNIX. VCS is ahigh-availability solution for cluster configurations. VCS enables you to monitorsystems and application services, and to restart services on a different systemwhen hardware or software fails.

3Chapter




Supported VCS optionsNetBackup supports the use of the Global Cluster Option (GCO) with VCS. Forinformation on how to configure and use GCO with NetBackup, contact ConsultingServices.

Installation prerequisitesThe following requirements must be met before you install and configure aNetBackup failover server:

■ Verify VCS and NetBackup Enterprise Server 7.0 support your hardware. Fora list of supported storage devices, visit the following Web site:http://entsupport.symantec.com

■ Verify that the supported version of VCS is correctly installed and configuredon Solaris, HP-UX, AIX, or Linux. Follow the steps in theVeritas Cluster ServerInstallation Guide.

■ Verify that no VCS resource group and resource exist with the same name asthat which you intend to use for NetBackup.

■ The shared disk must be configured and accessible to all cluster nodes whereyou want to install NetBackup.

■ Verify that you have an IP address and host name (virtual name) to be assignedto the NetBackup resource in VCS. Only use these for the NetBackup resource.Also, ping the IP address and verify that the IP address is not plumbed.

■ Verify that you can mount the disk.

■ Make sure that each node in the cluster, where you want to install NetBackup,is RSH equivalent (On HP the command is remsh). As the root user you mustbe able to perform a remote logon to each node in the cluster without enteringa password. This configuration is only necessary for installation, upgrades,and configuration of the NetBackup server and any NetBackup database agentsand options. After installation and configuration are complete thisconfiguration is no longer required.

NetBackup in a Veritas Cluster Server on UNIX/LinuxSupported VCS options

34


■ For a clustered NetBackup media server, physically connect the robotic devicesand tape devices to each node where you want to install NetBackup). Connectdevices by SCSI or Fibre Channel . Use OS commands to verify that all thedevices are connected properly. Refer to the NetBackup Device ConfigurationGuide.

■ Verify that you have the NetBackup Enterprise Server 7.0 installation programand a valid license key.

Preinstallation checklist for a NetBackup failoverserver installation

The NetBackup Enterprise Server requests certain cluster related informationduring installation. Fill out the checklist for all configurations and the checklistfor your specific configuration before you begin installation.

Note:The configuration utility unless specified, treats all attribute values globally.

About installation of NetBackup with all VCS configurationsThe following information is required for all VCS cluster configurations.

----------------------------------------Virtual Name for NetBackup:

----------------------------------------IP Address:

----------------------------------------Subnet Mask

Network Device Name(NIC)

IP AddressNode Name

------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------

About installation of NetBackup with VCSThe following information is required if you use VCS. Review the scenario thatfits your configuration.

See “Scenario 1 - with VxVM” on page 36.

See “Scenario 2- with no Volume Manager” on page 36.

35NetBackup in a Veritas Cluster Server on UNIX/LinuxPreinstallation checklist for a NetBackup failover server installation

See “Scenario 3 - with AIX LVMVG” on page 37.

See “Scenario 4 - in HP-UX with logical Volume Manager” on page 37.

Scenario 1 - with VxVMThe following information is required if you use VCS with VxVM.

ExampleResource

Disk Group Resource:

nbudgDisk Group: --------------------------------------

0 or 1Start Volumes: -----------------------------------

0 or 1Stop Volumes: -----------------------------------

Volume Resource: (optional)

nbuvolVolume: -------------------------------------------

Mount Resource:

/opt/VRTSnbuMount Point: ------------------------------------

/dev/vx/dsk/nbudg/nbuvolBlock Device: -----------------------------------

vxfsFS Type: ------------------------------------------

(optional)Mount Option: ----------------------------------

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

Scenario 2- with no Volume ManagerThe following information is required if you use VCS with a disk only and noVolume Manager.

ExampleResource


/dev/dsk/clt1dos3Block Device: -----------------------------------

vxfsFS Type: ------------------------------------------



NetBackup in a Veritas Cluster Server on UNIX/LinuxPreinstallation checklist for a NetBackup failover server installation

36

Scenario 3 - with AIX LVMVGThe following information is required if you use VCS in an AIX environment withLVMVG.

ExampleResource

LVMG Resource:

nbuvgVolume Group: ----------------------------------

58Major Number: ----------------------------------

hdisk1 or hdisk2Disks: ----------------------------------------------

(optional)ImportvgOpt: ------------------------------------

(optional)VaryonvgOpt: -----------------------------------

(optional)SyncODM: ---------------------------------------

Mount Resource: -------------------------------


/dev/nbudevBlock Device: -----------------------------------

jfs2FS Type: ------------------------------------------



Scenario 4 - in HP-UX with logical Volume ManagerThe following information is required if you use VCS in an HP-UX environmentwith logical Volume Manager.

ExampleResource

LVM Volume Group Resource:

vg0aVolume Group: ----------------------------------

LVM Logical Volume Resource:

vg0aVolume Group: ----------------------------------

lvol1Logical Group: ----------------------------------

37NetBackup in a Veritas Cluster Server on UNIX/LinuxPreinstallation checklist for a NetBackup failover server installation

Installing and configuring a failoverNetBackup serverThis section describes how to install and configure a new NetBackup EnterpriseServer as a failover application in a VCS for Solaris cluster. If you want to upgradeNetBackup, rather than complete an initial installation, you must follow a differentprocedure.


Installation notesThese instructions assume that this installation is a new installation of aNetBackup failover server.

You must install the NetBackup master server on each node to which NetBackupmay failover. You cannot have a separate failover master server in your NetBackupconfiguration.

Installation and configuration instructionsThe following procedure describes how to install and configure a NetBackupfailover server in a VCS cluster.

Note: NetBackup automatically detects supported clustering technology andprompt question based on it. If you are not prompted for these questions on aclustered setup, please exit from the script and verify that cluster is configuredcorrectly. Refer to cluster guide for details on how to verify the cluster setup.

To install and configure a NetBackup failover server

1 Fill out the checklist for all configurations and the checklist for your specificenvironment.

See “About installation of NetBackup with all VCS configurations” on page 35.

See “Preinstallation checklist for a NetBackup failover server installation”on page 35.

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

If applicable, unmount the NetBackup shared mount point. Stop the volumethe mount point is on and deport the disk group for that volume on all nodesof the cluster.

3 Follow the instructions for how to install NetBackup in the NetBackupInstallation Guide.

Be sure that you:

NetBackup in a Veritas Cluster Server on UNIX/LinuxInstalling and configuring a failover NetBackup server

38

■ Install NetBackup on each node to which it can failover.

■ Use the virtual name for the NetBackup server name.

Caution: When you are prompted, you must provide the same virtual clustername that you provided during the installation. This name is case sensitiveand must be in same format (FQDN/short) on all the nodes.

4 When NetBackup is installed on the clustered setup a confirmation promptis displayed.

■ When installing NetBackup on the first node, you are prompted to confirmcreation of a NetBackup cluster. Type Yes to set up NetBackup in HA mode.

■ When installing NetBackup on the subsequent nodes, information ofalready created NetBackup cluster group is displayed. You are promptedto join the group.

5 When you are prompted for cluster specific configuration details, refer tothe checklist and provide details accordingly.

6 Allow NetBackup to be installed in a cluster. When a NetBackup failoverserver is installed:

■ On the first node, a single node cluster resource group for NetBackup iscreated and brought online.

■ On the other nodes, the installed node is added to the cluster resourcegroup.

7 Install any NetBackup database agents or options.

See “Installing or upgrading NetBackup database agents and options”on page 40.

8 Continue with the configuration of NetBackup, as follows:

■ All servers outside of the cluster that need to access the NetBackup failoverserver must be added to the servers list. You can add servers in the hostproperties or in the bp.conf.



39NetBackup in a Veritas Cluster Server on UNIX/LinuxInstalling and configuring a failover NetBackup server

■ Verify that the entries for the NetBackup Catalog backups are correct.See “Configuring NetBackup catalog backups in a cluster” on page 94.Catalog backup information is stored on the shared disk and do not needto be configured for each node.

■ Configure backup policies. Backup policies are stored on the shared diskand do not need to be configured for each node.See “Configuring backup policies for a NetBackup clustered server”on page 95.

9 When you have completed configuration of NetBackup, verify that NetBackupcan failover properly in the cluster.

See “Verifying NetBackup configuration” on page 98.

Installing or upgrading NetBackup database agentsand options

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

Note: Before you upgrade any database agents or options, ensure that theNetBackup resource is online in the cluster. Also ensure that server processes arerunning on the active node.

To install or upgrade a NetBackup agent or option

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

2 Run the following command on the active node to disable the NetBackupagent monitor:

touch /usr/openv/netbackup/bin/cluster/frozen

3 On each inactive node in the cluster where NetBackup is installed, install anyagents or options. See the appropriate NetBackup documentation for theagent or option for installation and configuration instructions.

4 On the active node, perform the same installation.

5 Unfreeze the NetBackup group with hagrp -unfreeze nbu group name.

NetBackup in a Veritas Cluster Server on UNIX/LinuxInstalling or upgrading NetBackup database agents and options

40

6 Run the following command on the active node to enable the NetBackup agentmonitor:

rm -f /usr/openv/netbackup/bin/cluster/frozen

7 (Optional) Configure robot daemons and NetBackup options to failoverNetBackup if a daemon or the option fails. By default, robotic daemons andNetBackup options (such as NetBackup Vault) do not cause NetBackup tofailover if they fail.

See “Configuring robotic daemons for monitoring (UNIX/Linux clusters)”on page 98.

See “Configuring add-ons for monitoring (UNIX/Linux clusters)” on page 99.

Upgrading a NetBackup failover serverFollow these instructions if you want to upgrade from 6.0 or 6.5.

Note: NetBackup does not support conversion of an existing non-failoverNetBackup server to a failover NetBackup server. Contact Symantec Enterprisetechnical support .

Note: Symantec requires that you use the latest VCS agent that is installed withNetBackup 7.0. Older versions of the agent are not supported.


1 Ensure that a good backup of your cluster environment exists that includesa catalog backup.



3 Take the VCS NetBackup cluster resource offline before you begin the upgrade.

4 Freeze the NetBackup group using the following command:

hagrp -freeze <nbu_group_name> -persistent

41NetBackup in a Veritas Cluster Server on UNIX/LinuxUpgrading a NetBackup failover server

5 Stop the NetBackup cluster agent on all nodes of the NetBackup Group usingthe following command:

haagent -stop NetBackup -force -sys <node>

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

Note the following:

■ Follow the instructions for how to upgrade NetBackup as described in theNetBackup Installation Guide.

■ If required to specify the server name, provide the virtual name of theserver.

7 On each inactive node to which NetBackup may failover, install the NetBackupserver software.

Note the following:

■ Follow the instructions for how to upgrade NetBackup as described in theNetBackup Installation Guide.


8 Start the VCS NetBackup cluster agent on all nodes of the NetBackupGroup.Use the following command:

haagent -start NetBackup -force -sys <node>

9 Unfreeze the NetBackup group using the following command:

hagrp -unfreeze <nbu_group_name> -persistent

10 Take the NetBackup group offline and then bring online.

11 On each node where NetBackup server is installed, upgrade any NetBackupdatabase agents or options.

You must freeze the NetBackup group before you install any agents or options.


12 Verify that NetBackup can failover properly in the cluster.


NetBackup in a Veritas Cluster Server on UNIX/LinuxUpgrading a NetBackup failover server

42

Performing backups and restores in a VCS clusterThe process to configure and perform backups or to perform restores in a clusteris similar no matter which cluster solution you have. Additional guidelines andinstructions for how to perform backup and restores with NetBackup are coveredin later in this document.


43NetBackup in a Veritas Cluster Server on UNIX/LinuxPerforming backups and restores in a VCS cluster

NetBackup in a Veritas Cluster Server on UNIX/LinuxPerforming backups and restores in a VCS cluster

44

NetBackup in a VeritasCluster Server on Windows


■ About NetBackup in a Veritas Cluster Server on Windows

■ About the NetBackup agent for VCS

■ About NetBackup agent for VCS agent functions

■ Additional monitoring for NetBackup agent for VCS

■ Supported VCS options


■ Installing and configuring a NetBackup failover server on a VCS cluster

■ Reconfiguring NetBackup for the cluster


■ Performing backups and restores in a VCS cluster

■ About detailed monitoring for the NetBackup server

■ Setting up a detailed monitoring script for the NetBackup server in a VCS forWindows environment

■ Enabling detailed monitoring in VCS Cluster Manager for the NetBackup server

■ Disabling detailed monitoring in VCS Cluster Manager for the NetBackupserver

4Chapter

About NetBackup in a Veritas Cluster Server onWindows

This topic provides information on the prerequisites for using NetBackupEnterprise Server or NetBackup server as a highly available application with aVeritas Cluster Server (VCS). NetBackup can be used with VCS in a Windowsenvironment.

VCS is a high-availability solution for cluster configurations. With VCS you canmonitor systems and application services, and restart services on a differentsystem when hardware or software fails. For information about VCS, refer to theVeritas Cluster Server Administrator's Guide.




About the NetBackup agent for VCSThe NetBackup agent for VCS monitors specific NetBackup resources, determinesthe status of these resources, and starts or stops NetBackup according to externalevents. The agent includes VCS type declarations and agent executables. TheNetBackup resource type represents the agent. When the agent detects anapplication failure, the NetBackup service group is failed over to another systemin the cluster. NetBackup is installed and configured on this stem.

About NetBackup agent for VCS agent functionsThe following table describes the specific agent operations.

Brings the NetBackup services online.Online

Takes the NetBackup services offline.Offline

Verifies the status of NetBackup services. Detailed monitoring is alsoavailable.

See “Setting up a detailed monitoring script for the NetBackup serverin a VCS for Windows environment” on page 53.

Monitor

NetBackup in a Veritas Cluster Server on WindowsAbout NetBackup in a Veritas Cluster Server on Windows

46

Stops all NetBackup daemons after detecting an unexpected offlineoperation or an ineffective online operation.

Clean

Additional monitoring for NetBackup agent for VCSAdditional monitoring capabilities are available for add-on products.

See “Configuring add-ons for monitoring (Windows)” on page 100.

Supported VCS optionsNetBackup supports the use of the Global Cluster Option (GCO) with VCS. Forinformation on how to configure and use GCO with NetBackup, contact ConsultingServices.

Installation prerequisitesThe following requirements that must be met before you install and configure aNetBackup failover server:

■ Verify that VCS and NetBackup 7.0 support your hardware. For a list ofsupported storage devices, visit the following Web site:http://entsupport.symantec.com

■ Verify that storage devices have been properly installed and configured towork in a Windows environment. Refer to the section on how to configurestorage devices in the NetBackup Installation Guide.

■ Verify that you have installed Veritas Storage Foundation HA and correctlyconfigured VCS. NetBackup can be installed on as many nodes as VCS supports.The NetBackup service group is created during the installation.

■ For VCS Windows (SFW-HA 4.1, SFW-HA 4.2) make sure the patch availablethrough Technote 278307 is installed before you install or upgrade toNetBackup 7.0. The patch is available at the following Web site:http://entsupport.symantec.com/docs/278307

■ Verify the cluster disk group(s) and dynamic volume(s) for NetBackup havebeen created on the shared storage. Refer to the Veritas Storage FoundationAdministrator’s Guide for details on how to create these.

■ All disk resources that you want NetBackup to use must be configured in VeritasEnterprise Administrator (VEA) before you install NetBackup.

47NetBackup in a Veritas Cluster Server on WindowsAdditional monitoring for NetBackup agent for VCS



■ Verify that you have an IP address and host name (virtual name) to be assignedto the NetBackup resource in VCS. Only use these for the NetBackup clustergroup.Also, verify that the disk resource is online on the node from which theNetBackup installation will be performed for the first time on the cluster.

■ For a clustered NetBackup media server, physically connect the robotic devicesand tape devices to each node where you want to install NetBackup). Connectdevices by SCSI or Fibre Channel . Use OS commands to verify that all thedevices are connected properly. Refer to the NetBackup Device ConfigurationGuide.

■ Verify that you have the NetBackup Enterprise Server 7.0 or NetBackup server7.0 installation program and a valid license key.

■ On Windows 2003 and 2008, the public network names must be same on bothnodes of the cluster for push-installs.

Installing and configuring aNetBackup failover serveron a VCS cluster

This section describes how to install and configure a new NetBackup EnterpriseServer as a failover application in a VCS for Windows cluster. If you want toupgrade NetBackup, rather than complete an initial installation, you must followa different procedure.


Installation notesReview the following notes before you begin installation:

■ These instructions assume that this installation is a new installation of aNetBackup failover server.

■ You must install the same type of NetBackup server on each node to whichNetBackup may failover. You cannot have a separate failover master serverand a separate failover media server in your NetBackup configuration.

■ After you configure NetBackup as a cluster group in VCS, do not change thegroup name.

Installation and configuration instructionsThe following procedure describes how to install and configure a NetBackupfailover server in a VCS cluster.

NetBackup in a Veritas Cluster Server on WindowsInstalling and configuring a NetBackup failover server on a VCS cluster

48

To install a NetBackup failover server on a VCS cluster

1 Install NetBackup on all nodes of the cluster. This can be done in the followingways:

■ Install on the cluster node (with shared disk online) and push install toall other nodes in the cluster.

■ Install on the cluster node (with shared disk online). After the first nodeinstallation manually install on all other nodes in the cluster.

Follow the instructions for how to install NetBackup NetBackup in a clusteredenvironment as described in the NetBackup Installation Guide.


■ Installs NetBackup on the active node.

■ Push the install to each inactive node, including the single license key youprovided for the master server.


2 When you are prompted to provide the list of servers, enter all servers thatmust have access to the NetBackup failover server.

3 If you added license keys at the end of the installation, these keys must beadded to each node in the cluster. Fail over and add the keys to each node inthe cluster.

See “Adding license keys” on page 101.

4 If the cluster configuration does not complete successfully, you must runbpclusterutil manually.

See “Reconfiguring NetBackup for the cluster” on page 50.

5 Install any agents or options that require separate installations.

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

6 After the installation is complete, continue with the configuration ofNetBackup.



49NetBackup in a Veritas Cluster Server on WindowsInstalling and configuring a NetBackup failover server on a VCS cluster

■ Verify that the entries for the NetBackup Catalog backups are correct.See “Configuring NetBackup catalog backups in a cluster” on page 94.Catalog backup information is stored on the shared disk and does not needto be configured for each node.


■ By default, NetBackup options (such as NetBackup Vault) do not causeNetBackup to failover if they fail. You can configure NetBackup optionsto failover NetBackup if a service or the option fails.See “Configuring add-ons for monitoring (Windows)” on page 100.

7 When you have completed the installation and configuration of NetBackup,verify that NetBackup can fail over properly in the cluster.


Reconfiguring NetBackup for the clusterUnder normal circumstances, cluster configuration is one of the final steps toinstall NetBackup in a cluster. If you receive an error message during installation,, you can use the bpclusterutil command to perform this step. More details onthis command are available.

NetBackup in a Veritas Cluster Server on WindowsReconfiguring NetBackup for the cluster

50

To reconfigure NetBackup for the cluster

1 From the active node, run the following command.

bpclusterutil -ci

2 If the NetBackup database was no created, create the database. Run thefollowing command:

install_path\NetBackup\bin\create_nbdp.exe -db_server server_name

-data data_directory -index index_directory -tlog

log_directory -staging staging_directory

The server name and directory names are as follows:

The server name in

install_path\NetBackupDB\conf\server.conf

The server name is NB_server_name. For example,NB_ROULETTE.

server_name

install_path\NetBackupDB\datadata_directory

install_path\NetBackupDB\dataindex_directory

install_path\NetBackupDB\datalog_directory

install_path\NetBackupDB\stagingstaging_directory

Refer to theNetBackup Commands Guide forWindows for more informationabout this command


tpext


Upgrading a NetBackup failover serverFollow these instructions if you want to upgrade from NetBackup 6.0 or 6.5.

51NetBackup in a Veritas Cluster Server on WindowsUpgrading a NetBackup failover server






3 Take the VCS NetBackup resource offline before you begin the upgrade.

4 Follow the instructions for how to upgrade NetBackup as described in theNetBackup Installation Guide.


■ Upgrade NetBackup on the active node.

■ Push the install to each inactive node.


5 Upgrade and configure any database agents or options.

Most agents and options require only a license key and do not need to beupgraded separately. For information on how to install and configure a specificagent or option, see the appropriate NetBackup documentation for that agentor option.

Performing backups and restores in a VCS clusterThe process to configure and perform backups or to perform restores in a clusteris similar no matter which cluster solution you have. Additional guidelines andinstructions for how to perform backup and restores with NetBackup are coveredin later in this document.


NetBackup in a Veritas Cluster Server on WindowsPerforming backups and restores in a VCS cluster

52

About detailed monitoring for the NetBackup serverIn the detail monitoring mode, the NetBackup agent runs a script to verify thatNetBackup is available. A sample script, DetailedMonitor.bat, is provided withthe agent for this purpose. You can customize the script to meet your configurationrequirements.

Note: Before setting up detailed monitoring, you must have the NetBackup agentrun at the basic level of monitoring.

Setting up a detailed monitoring script for theNetBackup server in a VCS forWindows environment

This topic describes how to set up detailed monitoring for a NetBackup serverthat is installed in a VCS for Windows environment. The script file must exist onall nodes in the service group’s system list.

To set up a detailed monitoring script

1 Configure and run the NetBackup agent with the basic monitoring.

2 For each node in the NetBackup service group, create a backup policy thatperforms a user backup of the fileinstall_path\bin\cluster\VCS\DetailedMonitor.txt.

install_path is the home directory of NetBackup.

For example, C:\Program Files\VERITAS\NetBackup.

For example, if your NetBackup service group contains five nodes, you mustcreate five different policies, each referencing a different node.

3 Make a copy of following file and edit it to fit your configuration.

install_path\bin\cluster\DetailedMonitor.bat

■ Replace VIRTSRVR with the virtual server name for the NetBackup masteror media server.

■ Make any other edits necessary.

4 From the command line, type the following command to verify the scriptruns without errors:

DetailedMonitorProd

5 Continue with the next section to enable detailed monitoring.

53NetBackup in a Veritas Cluster Server on WindowsAbout detailed monitoring for the NetBackup server

Enabling detailedmonitoring in VCSClusterManagerfor the NetBackup server

This topic describes how to set the detail monitoring option for the NetBackupserver from the VCS Cluster Manager.

To enable detailed monitoring from the Java Console

1 In Cluster Explorer, right-click on the NetBackup service group, chooseOffline, and select the node where you want to bring the service group offline.

2 Click Yes.

3 In the left pane, click the NetBackup resource.

4 On the Properties tab, select the Monscript attribute from the list, and clickthe Edit button.

5 Provide the full path to the NetBackup monitor script that you created.

See “About detailed monitoring for the NetBackup server” on page 53.

6 Click OK.

7 Save your configuration.

8 In the left pane, right-click on the NetBackup service group, select Online,and select the node where you want to bring the service group online.

9 Click Yes.

Disabling detailedmonitoring inVCSClusterManagerfor the NetBackup server

This section describes how to disable the detail monitoring option for theNetBackup server from the VCS Cluster Manager.

To disable detailed monitoring from the Java Console

1 In Cluster Explorer, right-click on the NetBackup service group, chooseOffline,and select the node where you want to bring the service group offline.

2 Click Yes.

3 In the left pane, click the NetBackup resource.

4 On the Properties tab, select the Monscript attribute from the list, and clickthe Edit button.

5 Remove the path information.

6 Click OK.

NetBackup in a Veritas Cluster Server on WindowsEnabling detailed monitoring in VCS Cluster Manager for the NetBackup server

54

7 Save your configuration.

8 In the left pane, right-click on the NetBackup service group, select Online,and select the node where you want to bring the service group online.

9 Click Yes.

55NetBackup in a Veritas Cluster Server on WindowsDisabling detailed monitoring in VCS Cluster Manager for the NetBackup server

NetBackup in a Veritas Cluster Server on WindowsDisabling detailed monitoring in VCS Cluster Manager for the NetBackup server

56

NetBackup in a SunCluster


■ About NetBackup in a SunCluster


■ General prerequisites for installing NetBackup in a SunCluster environment

■ HA Storage Plus prerequisites when installing NetBackup in a SunClusterenvironment

■ Global File System prerequisites when installing NetBackup in a SunClusterenvironment


■ Installing and configuring NetBackup in a SunCluster



■ Bringing the NetBackup resource group online or offline

■ Performing backups and restores in a SunCluster

About NetBackup in a SunClusterThis topic provides information on how to install and configure NetBackupEnterprise Server as a highly available application in a SunCluster . NetBackupsupports the HA Storage Plus option for Sun Clusters. Refer to the NetBackupAdministrator's Guide, Volume I, for a detailed understanding of how NetBackupis installed and administered. Refer to the documentation for SunCluster for adetailed understanding of how SunCluster works and how it is installed andadministered. This guide also includes information on the SunPlex cluster system.

5Chapter




Installation prerequisitesThis section contains information about the requirements that must be met beforeyou install and configure a NetBackup failover server in a SunCluster environment.

General prerequisites for installing NetBackup in aSunCluster environment

The following prerequisites apply to both types of SunCluster installations, HAStorage Plus, and Global File System.

■ Verify SunCluster and NetBackup Enterprise Server 7.0 support your hardware.For a list of supported storage devices, visit the following Web site. Also consultthe SunCluster documentation.http://entsupport.symantec.com

■ Verify that you have an IP address and host name (virtual name) to be assignedto the NetBackup resource group. Only use these for the NetBackup resourcegroup.

■ Physically connect the robotic devices and tape devices to each node whereyou want to install NetBackup). Connect devices by SCSI or Fibre Channel .Use OS commands to verify that all the devices are connected properly. Referto the NetBackup Device Configuration Guide.

■ Make sure that each node in the cluster, where you want to install NetBackup,is RSH equivalent. As the root user you must be able to perform a remote logonto each node in the cluster without entering a password. This configurationis only necessary for installation, upgrades, and configuration of the NetBackupserver and any NetBackup database agents and options. After installation andconfiguration is complete, this configuration is no longer required.


NetBackup in a SunClusterInstallation prerequisites

58


HA Storage Plus prerequisites when installingNetBackup in a SunCluster environment

The following prerequisites must be met for HA Storage Plus:

■ Make sure that the disk has enough space for the NetBackup database filesand directories.

■ Mount the disk on the machine that you want to configure NetBackup on.

Global File System prerequisites when installingNetBackup in a SunCluster environment

The following prerequisites must be met for Global File System:

■ The shared disk must be configured and accessible to all cluster nodes whereyou want to install NetBackup. See the SunCluster documentation for moreinformation on how to create and configure a shared disk.

■ Make sure that the shared disk has enough space for the NetBackup databasefiles and directories.

■ You must be able to mount the disk on all nodes at the same time.


The following information is required for SunCluster cluster configurations.

ExampleResource

vnameVirtual name for NetBackup:

/opt/VRTSnbuMount Point (Shared Directory Path):

y or nHAStoragePlus Resource for NetBackup Data

Installing and configuringNetBackup in a SunClusterThis section describes how to install a new NetBackup Enterprise Server as afailover application in a SunCluster . If you want to upgrade NetBackup, ratherthan complete an initial installation, you must follow a different procedure.

59NetBackup in a SunClusterHA Storage Plus prerequisites when installing NetBackup in a SunCluster environment




■ The NetBackup resource group name in a SunCluster is always scnb-harg.The user cannot configure this name.

■ Two SunCluster resource files are installed with NetBackup and should not beedited: scnb.VRTS and scnb.conf.

Note: Cluster configuration is performed along with the installation process. Donot run the cluster_config script to perform cluster conflagration.

Installation and configuration instructionsThe following procedure describes how to install and configure a NetBackupfailover server in a SunCluster .

Note: Additional commands are required to properly freeze and unfreezeNetBackup in a SunCluster , due to Sun bug #5017826. When NetBackup is startedunder pmf with automatic restarts enabled, pmf intervenes if the tag dies. Thisintervention happens whether the monitor is enabled or not.

Note: If the shared disk is a raw disk with Global File System (GFS) and the primary(active) node is powered off, the shared disk is not accessible from any of theremaining nodes. As a result, the NetBackup server fails to come online on anyother node.

To install and configure NetBackup in a SunCluster




Be sure that you:

NetBackup in a SunClusterInstalling and configuring NetBackup in a SunCluster

60





■ When you install NetBackup on the first node, you are prompted to confirmcreation of a NetBackup cluster. Type Yes to set up NetBackup in HA mode.

■ When you install NetBackup on the subsequent nodes, information ofalready created NetBackup cluster group is displayed. You are promptedto join the group.

4 When you are prompted for cluster-specific configuration details, refer tothe checklist and provide details accordingly.











61NetBackup in a SunClusterInstalling and configuring NetBackup in a SunCluster

■ Verify that the entries for the NetBackup Catalog backups are correct.See “Configuring NetBackup catalog backups in a cluster” on page 94.Catalog backup information is stored on the shared disk and does not needto be configured for each node.


8 When you have completed configuration of NetBackup, verify that NetBackupcan fail over properly in the cluster.



To install or upgrade database agents and options, NetBackup daemons must bebrought offline without causing a failover. SunCluster must be configured to stopmonitoring NetBackup, but keep NetBackup resources online.

By default, robotic daemons and NetBackup options (such as NetBackup Vault)do not cause NetBackup to failover if they fail. You can configure robot daemonsand NetBackup options to failover NetBackup if a daemon or the option fails.



To install or upgrade NetBackup database agents and options

1 Freeze the NetBackup group by executing the following:

/usr/cluster/bin/scswitch -n -j scnb-hars



3 On active node, install or upgrade any database agents or options. See theappropriate NetBackup documentation for the agent or option for installationand configuration instructions.

4 On the inactive node, perform the same installation.

NetBackup in a SunClusterInstalling or upgrading NetBackup database agents and options

62

5 After you complete the installations of any agents or options, run the followingcommands:

/usr/cluster/bin/scswitch -e -j scnb-hars



The NetBackup resources are brought online and SunCluster resumesmonitoring the NetBackup resource.

Upgrading a NetBackup failover serverFollow these instructions if you want to upgrade from 6.0 or 6.5. You must alsohave the SunCluster agent that was installed with your previous version ofNetBackup.






3 Put NetBackup in the unmanaged state by executing the following commands:

/usr/cluster/bin/scswitch -n -j scnb-hars

4 On active node, install the NetBackup server.

Note the following:

■ Follow the instructions for how to install NetBackup server as describedin the NetBackup Installation Guide.


63NetBackup in a SunClusterUpgrading a NetBackup failover server

5 On each inactive node to which NetBackup may failover, install theNetBackupserver.

Note the following:




/usr/cluster/bin/scswitch -e -j scnb-hars

The NetBackup resources are brought online and SunCluster resumesmonitoring the NetBackup resource.

7 Bring the NetBackup resource group offline and online.






Bringing the NetBackup resource group online oroffline

To bring the NetBackup resource group online or offline, special SunClustercommands must be used. See the SunCluster documentation for more informationon these and other commands.

Table 5-1 describes the commands you use to bring the NetBackup resource grouponline or offline.

Table 5-1 SunCluster commands

Enter this command:To:

/usr/cluster/bin/scswitch -z -g scnb-harg -h

hostname

bring the NetBackupresource group online

NetBackup in a SunClusterBringing the NetBackup resource group online or offline

64

Table 5-1 SunCluster commands (continued)


/usr/cluster/bin/scswitch -F -g scnb-hargbring the NetBackupresource group offline

/usr/cluster/bin/scstat -gverify that theNetBackup resource isonline

Performing backups and restores in a SunClusterThe process to configure and perform backups or to perform restores in a clusteris similar no matter which cluster solution you have. Additional guidelines andinstructions for how to perform backup and restores with NetBackup are coveredin later in this document.


65NetBackup in a SunClusterPerforming backups and restores in a SunCluster

NetBackup in a SunClusterPerforming backups and restores in a SunCluster

66

NetBackup in an HPMC/Service Guard cluster


■ About NetBackup in an HP MC/Service Guard cluster

■ Limitations



■ Installation and configuration




■ Performing backups and restores in an HP MC/Service Guard Cluster

About NetBackup in an HPMC/Service Guard clusterThis topic provides information on how to install and configure NetBackupEnterprise Server as a highly available application in an HP MC/Service Guardcluster. Refer to the NetBackup Administrator's Guide, Volume I, for a detailedunderstanding of how NetBackup is installed and administered. Refer to thedocumentation for Service Guard for a detailed understanding of how ServiceGuard works and how it is installed and administered.


6Chapter



LimitationsOnly a new installation of NetBackup 7.0 can be installed in a Service Guard cluster.If you have a previous version of NetBackup installed in the cluster, it cannot beupgraded to version 7.0.

Installation prerequisitesThe following requirements must be met before you install and configure aNetBackup failover server in a Service Guard environment:

■ Verify Service Guard and NetBackup Enterprise Server 7.0 support yourhardware. For a list of supported storage devices, visit the following Web site.Also and consult the Service Guard documentation.http://entsupport.symantec.com

■ Verify that the supported version of Service Guard is correctly installed andconfigured.

■ Verify that you have an IP address and host name (virtual name) to be assignedto the NetBackup resource. Only use these for the NetBackup resource.

■ The shared disk must be configured and accessible to all cluster nodes whereyou want to install NetBackup. See the Service Guard and the appropriateVolume Manager (Veritas or HP) documentation for more information on howto create and configure a shared disk. Make sure that the shared disk hasenough space for the NetBackup database files and directories. Make sure thatthe disk is not mounted on any system and that all volume groups are offlineand volumes are stopped before installing NetBackup.

■ You can have the database spread across multiple shared disks for performancereasons. This configuration can be performed after the initial clusterconfiguration.


■ Make sure that each node in the cluster, where you want to install NetBackup,is remsh equivalent. As the root user you need to be able to perform a remote

NetBackup in an HP MC/Service Guard clusterLimitations

68


logon to each node in the cluster without entering a password. Thisconfiguration is only necessary for installation, upgrades, and configurationof the NetBackup server and any NetBackup database agents and options. Afterinstallation and configuration are complete, this configuration is no longerrequired.




About installation of NetBackup with all HP MC/Service Guard clusterconfigurations

The following information is required for all HP MC/Service Guard clusterconfigurations.

ExampleResource

vnameVirtual name for NetBackup:

10.209.14.54IP address:

10.209.14.0Subnet for the virtual name:

See “Scenario 1 - with VxVM Volume Group ” on page 69.

See “Scenario 2 - with Veritas Cluster Volume Manager” on page 70.

See “Scenario 3 - with LVM Volume Group” on page 70.

About installation of NetBackup with HP MC/Service GuardThe following information is required if you use HP MC/Service Guard. Reviewthe scenario that fits your configuration.

Scenario 1 - with VxVM Volume GroupThe following information is required if you use HP MC/Service Guard with VxVMVolume Group.

69NetBackup in an HP MC/Service Guard clusterPreinstallation checklist for a NetBackup failover server installation

ExampleResource

nbudgDisk Group Name:

dev/dsk/nbudg/nbuvolLogical Volume Path:

/opt/VRTSnbuMount Point:

vxfsFile System:

Mount Options:

Unmount Options:

fsk Options:

Scenario 2 - with Veritas Cluster Volume ManagerThe following information is required if you use HP MC/Service Guard with VeritasCluster Volume Manager.

ExampleResource

nbuggDisk Group Name:

/dev/dsk/nbudg/nbuvolLogical Volume Path:

/opt/VTRSnbuMount Point:

vxfsFile System:

Mount Options:

Unmount Options:

fsk Options:

Scenario 3 - with LVM Volume GroupThe following information is required if you use HP MC/Service Guard with LVMVolume Group.

ExampleResource

nbuvgDisk Group Name:

dev/nbuvg/lvo1Logical Volume Path:

opt/VRTSnbuMount Point:

NetBackup in an HP MC/Service Guard clusterPreinstallation checklist for a NetBackup failover server installation

70

vxfsFile System:

Mount Options:

Unmount Options:

fsk Options:

Installation and configurationThis section describes how to install NetBackup Enterprise Server as a failoverapplication in a Service Guard cluster. If you want to upgrade NetBackup, ratherthan complete an initial installation, you need to follow a different procedure.




■ The NetBackup package name in a Service Guard cluster is always "NetBackup."The user cannot configure this name.

■ The following package ASCII file is installed with NetBackup. You can changethe values for any of the "timeout" settings in this file. Do not make changesto any settings that are not related to timeouts./etc/cmcluster/netbackup/netbackup.config

Note: Cluster configuration is performed along with the installation process. Donot run the cluster_config script to perform cluster conflagration.

Installation and configuration instructionsThe following procedure describes how to install and configure a NetBackupfailover server on a Service Guard cluster.

71NetBackup in an HP MC/Service Guard clusterInstallation and configuration

To install and configure NetBackup in a Service Guard cluster



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

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


Be sure that you:











NetBackup in an HP MC/Service Guard clusterInstallation and configuration

72



Installing or upgrading NetBackup database agents and options










To install or upgrade database agents and options, NetBackup daemons must bebrought offline without causing a failover. Service Guard must be configured tostop monitoring NetBackup, but keep NetBackup resources online (or frozen).



73NetBackup in an HP MC/Service Guard clusterInstalling or upgrading NetBackup database agents and options


To install or upgrade NetBackup database agents and options

1 Place NetBackup in a frozen state by executing the following:

cmmodpkg -d netbackup



3 On the active node where NetBackup server is installed, install any databaseagents or options. See the appropriate NetBackup documentation for theagent or option for installation and configuration instructions.

4 Perform the same installation on each inactive node.

5 After you complete the installations of the agents or options, run thefollowing:

cmmodpkg -e netbackup



The NetBackup resources are brought online and Service Guard resumesmonitoring the NetBackup resource.

Upgrading a NetBackup failover serverFollow these instructions to upgrade NetBackup failover server from 6.0 or 6.5.


1 Ensure a good backup of your cluster environment exists that includes acatalog backup.


2 For each NetBackup server that runs outside of the cluster, ensure that theserver list is accurate. This list must contain the name of each node on whichNetBackup can run and the name of the virtual server.

3 Place NetBackup in a frozen state by executing the following:

cmmodpkg -d netbackup

NetBackup in an HP MC/Service Guard clusterUpgrading a NetBackup failover server

74



5 On active node, install the NetBackup server.

Note the following:



6 On each inactive node to which NetBackup may failover, install the NetBackupserver.

Note the following:



7 Run the following command:

cmmodpkg -e netbackup





10 On each node on which NetBackup server is installed, upgrade any NetBackupdatabase agents or options. You must freeze the NetBackup group before youinstall any agents or options.




75NetBackup in an HP MC/Service Guard clusterUpgrading a NetBackup failover server


To bring the NetBackup resource group online or offline, special Service Guardcommands must be used. See the Service Guard documentation for moreinformation on these and other commands.

Table 6-1 describes the commands you use to bring the NetBackup resource grouponline or offline.

Table 6-1 HP MC/Service Guard commands


/usr/sbin/cmrunpkg netbackupbring the NetBackupresource group online

/usr/sbin/cmhaltpkg netbackupbring the NetBackupresource group offline

/usr/sbin/cmviewclverify that the NetBackupresource is online

Performingbackups and restores in anHPMC/ServiceGuard Cluster

The process to configure and perform backups or to perform restores in a clusteris similar no matter which cluster solution you have. Additional guidelines andinstructions for how to perform backup and restores with NetBackup are coveredin later in this document.


NetBackup in an HP MC/Service Guard clusterBringing the NetBackup resource group online or offline

76

NetBackup in an HACMPcluster for AIX


■ About NetBackup in an HACMP cluster for AIX



■ Installation and configuration

■ Installing NetBackup database agents and options



■ Performing backups and restores in an HACMP Cluster

About NetBackup in an HACMP cluster for AIXThis topic provides information on how to install and configure NetBackupEnterprise Server as a highly available application with High Availability ClusterMultiprocessing (HACMP). Refer to theNetBackupAdministrator'sGuide,VolumeI, for a detailed understanding of how NetBackup is installed and administered.Refer to the documentation for HACMP for a detailed understanding of howHACMP works and how it is installed and administered.



7Chapter


Installation prerequisitesThis section contains information about the requirements that must be met beforeinstall and configure a NetBackup failover server in a HACMP environment.

■ Verify that HACMP and NetBackup Enterprise Server 7.0 support yourhardware. For a list of supported storage devices, visit the following Web site.Also consult the HACMP documentation.http://entsupport.symantec.com

■ Verify that supported version of AIX is installed.

■ Verify that supported version of HACMP is correctly installed and configured.It also must pass cluster verification and synchronization.


■ Make sure that each node in the cluster, where you want to install NetBackup,is RSH equivalent. As the root user you need to be able to perform a remotelogon to each node in the cluster without entering a password. This ability isonly necessary for installation, upgrades, and configuration of the NetBackupserver and any NetBackup database agents and options. When installation andconfiguration are complete this configuration is no longer required.

■ There must be a pre-existing file system available for use by the NetBackupresource group that is configured on all nodes. This file system must be residenton a volume group that is accessible to all nodes where you want to configureNetBackup. It must not be configured as a resource for an existing HACMPresource group. It must not be configured to mount at boot time on any node.

■ Verify that you have a service IP address and an associated name (virtual name)to configure for NetBackup. This name and address must be present in the/etc/hosts file on all nodes before you install NetBackup.

■ If you use IPAT by IP Replacement for your service address, then it must beconfigured in HACMP. The service address must be configured before you startinstalling NetBackup. The service address must not already be assigned to aresource group. This configuration must be done before you install NetBackup.

■ If you use IPAT by IP aliasing, you do not need to configure the service addressin HACMP before you install NetBackup. The service address must conform

NetBackup in an HACMP cluster for AIXInstallation prerequisites

78


to the restrictions that are described in topic entitled "Planning Cluster NetworkConnectivity" of the HACMP Planning and Installation Guide. If you havealready configured the service, it must not be assigned to a resource groupalready.

■ Before you configure NetBackup, the cluster must be stable and able to completea successful verification and synchronization.




About installation of NetBackup with all HACMP cluster configurationsThe following information is required for all HACMP cluster configurations.

ExampleResource

netbackupNetBackup Resource Group Name:

nbu_serverNetBackup Server Resource Name:

/nbha1Mount Point for the Shared Storage:

/nbha1/dir1Top-level Directory on Shared Storage:

About installation of NetBackup with HACMP clusterThe following information is required if you use HACMP. Review the scenariothat fits your configuration.

Scenario 1 - with IPAT by IP AliasingThe following information is required if you use HACMP with IPAT by IP aliasing.

ExampleResource

vnameNetBackup Virtual Name:

79NetBackup in an HACMP cluster for AIXPreinstallation checklist for a NetBackup failover server installation

net_ether_01HACMP Network Name:

Scenario 2 - with IPAT by IP ReplacementThe following information is required if you use HACMP with IPAT by IP aliasing.

ExampleResource

vnameNetBackup Virtual Name:

Installation and configurationThis section describes how to install NetBackup Enterprise Server as a failoverapplication in an HACMP cluster.

Installation and configuration instructionsThe following procedure describes how to install and configure a NetBackupfailover server in an HACMP cluster.

Note: You can ignore the following type of warning message from the clusterconfiguration script. These messages are generated during the verification andsynchronization whenever there are multiple addresses on a network interface.

WARNING:There may be an insufficient number of communication

interfaces definedon node: blazer, network: net_ether_01. Multiple

communication interfaces are recommended for networks that will use

IP aliasing.

To install and configure NetBackup in a HACMP cluster



2 Volume group of the pre-existing file system, that NetBackup is going to usemust be varied-on on the node from which you want to start clusteredinstallation of Netbackup. If the volume group is not varied-on the installermay not detect it as a shareable file system.


NetBackup in an HACMP cluster for AIXInstallation and configuration

80

Be sure that you:



Caution: When you are prompted, you must provide the same virtual clustername that you provided during the installation. This name is case sensitiveand must be in same format (FQDN/short) on all the nodes..





Allow NetBackup to be installed in a cluster. When a NetBackup failoverserver is installed:




You must stop the NetBackup group before you install any agents or options.

Installing NetBackup database agents and options

7 Continue with the configuration of NetBackup.



■ Configure the devices in the cluster.See “Device configuration guidelines” on page 92.See “Configuring devices” on page 93.

81NetBackup in an HACMP cluster for AIXInstallation and configuration

Note that devices must be configured on each node in the cluster.





Installing NetBackup database agents and optionsTo install database agents and options, NetBackup daemons must be broughtoffline without causing a failover. HACMP must be configured to stop monitoringNetBackup, but keep NetBackup resources online.




To install NetBackup database agents and options

1 Enter the following command to disable application monitoring for theNetBackup resource group.

smitty hacmp

2 Choose System Management (C-SPOC).

3 Choose HACMP Resource Group and Application Management.

4 Choose Suspend/Resume Application Monitoring.

5 Choose Suspend Application Monitoring.

6 Select the NetBackup server and press .

NetBackup in an HACMP cluster for AIXInstalling NetBackup database agents and options

82



8 On the active node where NetBackup server is installed, install or upgradeany database agents or options. See the appropriate NetBackup documentationfor the agent or option for installation and configuration instructions.

9 On the inactive node, perform the same installation.



11 Enter the following command to enable application monitoring for theNetBackup resource group.

smitty hacmp




15 Choose Resume Application Monitoring.

16 Select the NetBackup server and press Enter.

Upgrading a NetBackup failover serverFollow these instructions if you want to upgrade from NetBackup 6.0 and 6.5.


83NetBackup in an HACMP cluster for AIXUpgrading a NetBackup failover server





3 Enter the following command to disable application monitoring for theNetBackup resource group.

smitty hacmp




7 Choose Suspend Application Monitoring.


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

Note the following:



10 On each inactive node to which NetBackup may failover, install the NetBackupserver software.

Note the following:



NetBackup in an HACMP cluster for AIXUpgrading a NetBackup failover server

84

11 On the active node, perform the same upgrade installation.

During an upgrade of a NetBackup in a Service Guard cluster you see themessages that indicate that the database is created twice. These messagesappear because the database is created in the default location(/usr/openv/db/) during install_bp. Later, it is moved or recreated on theshared disk.

12 On each inactive node where NetBackup server is installed, install or upgradeany database agents or options. See the appropriate NetBackup documentationfor the agent or option for installation and configuration instructions.

13 On the active node, perform the same installation.



15 Enter the following command to enable application monitoring for theNetBackup resource group.

smitty hacmp




19 Choose Resume Application Monitoring.






See “Installing NetBackup database agents and options” on page 82.



85NetBackup in an HACMP cluster for AIXUpgrading a NetBackup failover server


The SMIT tool manages any resource group operations. Use this tool to bring theNetBackup resource group online or offline and to move the location of theresource group.

To bring the NetBackup resource group online

1 Enter the following command.

smitty

2 Choose Communications Applications and Services.

3 Choose HACMP for AIX.



6 Choose Online Group.

7 Choose the group that you want to bring online.

To bring the NetBackup resource group offline

1 Enter the following command.

smitty

2 Choose Communications Applications and Services.

3 Choose HACMP for AIX.



6 Choose Offline Group.

7 Choose the group that you want to bring offline.

Performingbackupsand restores inanHACMPClusterThe process to configure and perform backups or to perform restores in a clusteris similar no matter which cluster solution you have. Additional guidelines andinstructions for how to perform backup and restores with NetBackup are coveredin later in this document.

NetBackup in an HACMP cluster for AIXBringing the NetBackup resource group online or offline

86


87NetBackup in an HACMP cluster for AIXPerforming backups and restores in an HACMP Cluster

NetBackup in an HACMP cluster for AIXPerforming backups and restores in an HACMP Cluster

88

Configuring NetBackup


■ Overview

■ NetBackup configuration guidelines

■ Device configuration guidelines

■ Configuring devices

■ Configuring NetBackup catalog backups in a cluster

■ Configuring backup policies for a NetBackup clustered server

■ What to back up

■ Backing up local disks in a cluster

■ Backing up the shared disks

■ Backing up database files in a cluster

■ User backups

■ Verifying NetBackup configuration

■ Configuring robotic daemons for monitoring (UNIX/Linux clusters)

■ Configuring additional services (UNIX/Linux clusters)

■ Configuring add-ons for monitoring (UNIX/Linux clusters)

■ Configuring additional services (Windows)

■ Configuring add-ons for monitoring (Windows)

■ Adding license keys

8Chapter

OverviewConfiguration of NetBackup includes the creation of storage devices, volumes,the catalog backup, and backup policies. This configuration can be completedmost easily with the NetBackup Configuration Wizards in the NetBackupAdministration Console. Refer to the NetBackup Administrator's Guide, VolumeI, for more details for instructions on how to perform these steps manually. (Seeinformation for configuring NetBackup without wizards.) Refer to Table 8-1 beforeyou configure NetBackup.

Table 8-1 summarizes the information that applies to each cluster environment.

Table 8-1 Configuring NetBackup

DescriptionSectionCluster Type

General guidelines to follow whenyou configure the NetBackupserver in a cluster.

NetBackup configurationguidelines

All

General guidelines to follow whenyou configure devices for aNetBackup server in a cluster.

Device configuration guidelinesAll

Device configuration guidelines.Configuring devicesAll

Instructions for verifyingNetBackup Catalog Backup entriesare correct.

Configuring NetBackup catalogbackups in a cluster

All

Configuring automatic backuppolicies.

Configuring backup policies for aNetBackup clustered server

All

Instructions to verify thatNetBackup is configured correctly.

Verifying NetBackupconfiguration

All

How to configure robotic daemonsto fail over NetBackup

Configuring robotic daemons formonitoring (UNIX/Linux clusters)

UNIX/Linux

How to configure NetBackupadd-on products to fail overNetBackup in a UNIX/Linuxcluster.

Configuring add-ons formonitoring (UNIX/Linux clusters)

UNIX/Linux

How to configure NetBackupadd-on products to fail overNetBackup in Windows.

Configuring add-ons formonitoring (Windows)

Windows

Configuring NetBackupOverview

90

Table 8-1 Configuring NetBackup (continued)

DescriptionSectionCluster Type

Additional license keys in a clusterenvironment.

Adding license keysAll

NetBackup configuration guidelinesReview the following guidelines before you configure NetBackup.

■ To ensure that all nodes in the NetBackup failover group are properly registeredin the EMM database, you must failover the NetBackup Group to all nodes inthe NetBackup cluster group.

■ The NetBackup server list must be set up correctly on each node whereNetBackup is configured as a failover server. For NetBackup in a clusteredenvironment, the virtual server name must appear first. After that name,include the node names within the NetBackup group.

■ For each NetBackup server that runs outside of the cluster, the server list mustcontain the name of each node where NetBackup can run. The list must alsocontain the name of the virtual server.

■ NetBackup depends on names to route information between participants inthe backup and restore process. Therefore, the use of names must be consistentwithin a NetBackup configuration. Specific node names and virtual namesshould not be used interchangeably.

■ CLIENT_NAME should be set to the name of the node.

■ CLUSTER_NAME should be the virtual server name that is dedicated to theNetBackup Application that runs on the cluster.

■ When you make changes to the NetBackup configuration on the active node,be sure to apply the same changes to each node in the cluster.

■ NetBackup Server Host Properties in a cluster

■ The NetBackup Administration Console obtains node information from theEMM database. Therefore, changes to the Host Properties only affect thenodes that are already registered in the EMM database. (You change theHost Properties only when you fail over to the NetBackup Group to eachnode.)

■ All hostnames that are listed in the Properties panel can have their hostproperties updated with the Host Properties user interface. The exceptionto this is the Authorization host property, which is only updated on theactive node.

91Configuring NetBackupNetBackup configuration guidelines

■ The "Add to All" hosts functionality is applicable only for a clustered masterserver and not for clustered media servers. To update Host Properties onclustered media servers, the user needs to update each node individuallyor select multiple nodes of the clustered media server.

■ Configuration information is stored on the shared disk and cannot beconfigured separately for each node. (This information includes backup policies,storage units, and the NetBackup catalog backup.) All other configurationchanges must be applied by moving the NetBackup server to each node.

■ By default, NetBackup tries to complete a backup job two times (within a12-hour window) before it allows the job to fail. Backup attempts may beexhausted before the failover of the NetBackup media server completes. If thissituation happens, increase the Scheduledbackupattempts setting to 6. Youcan also avoid this problem; set the Job retry delay setting to a lower value.

■ The Job retrydelay setting should be set lower to increase the likelihood thatNetBackup is able to initiate all scheduled backups.

■ The server list for each client you want to back up should contain the name ofeach node where NetBackup can run. This list should also contain the nameof the virtual server.

Device configuration guidelinesThe following are guidelines for configuring the devices for a clustered NetBackupserver:

■ Choose the SCSI Persistent reserve protection option, if possible. The use ofpersistent reserve is recommended, but take care to ensure that your hardwaresupports it correctly. See theNetBackup Administrator’s Guide, Volume II formore information.With this option, NetBackup can recover and use a reserved drive after afailover (if NetBackup owns the reservation). If you use SPC-2 SCSI reserve, adrive reset usually is required because the reservation owner is inoperative.Consult the NetBackup Administrator’s Guide for more information on howto reset a drive and on the Enable SCSI Reserve setting.

■ Devices that are attached to one node but not to the other node are availableonly when the node where they are attached is online. For a NetBackup failovermaster server, attach all of the devices to each node where NetBackup isinstalled. Use shared SCSI or Fibre Channel connections as necessary to sharethe devices.

Configuring NetBackupDevice configuration guidelines

92

■ For a NetBackup media server failover configuration, configure devices fromthe NetBackup master server with the active node name as the NetBackupmedia server name.

■ For any tape devices that are in a robotic library, ensure that the robot drivenumber field is set correctly. Use the drive numbering scheme that themanufacturer of the robotic library has implemented. NetBackup considersthe first drive in the robot as robot drive number 1. If the manufacturer’s drivenumbering scheme starts with a different number such as 0, adjust itaccordingly.

■ Ensure that the robot numbers you define for the robots the failover serveruses are consistent on all servers that use that robot. If the robot number thatis defined on one node does not match the number that is defined on anothernode, backups may fail.

■ When you create the storage units that reside on the cluster, select the virtualname of the failover NetBackup server for the Media server setting.

■ If you choose Anyserver for the media server when you create a storage unit,NetBackup selects the virtual NetBackup server when it performs any backupand restore operations.

Configuring devicesThis section describes how to configure devices in NetBackup.

Note: To accommodate disparate SCSI connections on each node of the cluster,you must configure devices on each node. First, configure the devices on the activenode. Move the NetBackup group to another node and configure the devices onthat node. Then move NetBackup to another node and configure the devices onthat node, etc.

You can configure NetBackup to failover if a robotic device fails.

Configuring robotic daemons for monitoring (UNIX/Linux clusters)

93Configuring NetBackupConfiguring devices

To configure devices

1 Review the device configuration guidelines.

Device configuration guidelines

2 On the active node, run the Device Configuration Wizard . This wizardautomatically discovers and configures the devices and it creates storageunits for those devices.

Symantec recommends that you use the Device Configuration Wizard toconfigure devices.

3 Move the NetBackup group to another node.

4 Refresh the view in the Media and Device Management utility.

5 Run the Device Configuration Wizard .

6 Continue to configure the devices on each node in the cluster. Repeat step 3through step 5.

If device paths are not displayed after you refresh the Devices node or runtpconfig, the active node of the cluster is not configured properly.

To add new devices

Follow the same procedure as when you initially configured devices in thecluster. First, configure the devices on the active node. Move the NetBackupgroup to another node and configure the devices on that node. Then moveNetBackup to another node and configure the devices on that node, and soon.

Configuring NetBackup catalog backups in a clusterFor complete information on how to configure and run online catalog backups,refer to theNetBackupAdministrator’sGuide. For information on recovery of theNetBackup catalog, see the NetBackup Troubleshooting Guide.

Note: An online catalog backup does not back up information on the inactivenodes. You must create a separate policy as described in the following step.

Configuring NetBackupConfiguring NetBackup catalog backups in a cluster

94

To configure an online, hot catalog backup in a cluster

1 Follow the instructions for creating online catalog backups as described inthe NetBackup Administrator’s Guide.

2 Create a policy to back up the following directory on each node in the cluster.

install_path\netbackup\varWindows

/usr/openv/varUNIX/Linux

Configuringbackuppolicies for aNetBackupclusteredserver

To back up all data in a cluster, create the backup policies that back up the localdisks, shared disks, and database files in the cluster.

Review the following topics:

See “What to back up” on page 95.

See “Backing up local disks in a cluster” on page 96.

See “Backing up the shared disks” on page 96.

See “Backing up database files in a cluster” on page 97.

See “User backups” on page 97.

What to back upBack up the following to protect all data in the cluster, including file systems anddatabases:

■ Local disks on each node.See “Backing up local disks in a cluster” on page 96.

■ All disks that attach to the shared SCSI bus.See “Backing up the shared disks” on page 96.

■ Virtual servers, which may contain data or contain database applications. UseNetBackup database agents to back up databases.See “Backing up database files in a cluster” on page 97.See “User backups” on page 97.

■ In MSCS and VCS for Windows clusters, also be sure to back up the SystemState and Shadow Copy Components on each node. For MSCS clusters, you

95Configuring NetBackupConfiguring backup policies for a NetBackup clustered server

must also back up the cluster quorum. The cluster quorum contains recoveryinformation for the cluster and information about changes to the clusterconfiguration. The cluster quorum is included in the System State or ShadowCopy Components backup.See “Backing up local disks in a cluster” on page 96.

Backing up local disks in a clusterTo protect the data on the node’s local disks, configure a policy that includes thecluster node names in the client list. In addition to this policy, you must alsoconfigure a separate policy to back up the shared disks.

See “Backing up the shared disks” on page 96.

The following are guidelines for configuring the policy to back up local disks:

■ If you have a failover media server, when you create a backup policy, selectthe storage unit that you created for the failover media server.

■ If NetBackup is installed on the cluster as separate NetBackup media servers,configure a policy for each node. Each policy should include the cluster nodename as a client. For each policy, select the storage unit that you created forthe NetBackup media server that is installed on that cluster node.

■ In the Backup Selections list, add the ALL_LOCAL_DRIVES directive. Then addthe shared disks to the Exclude List for each client. For UNIX or Linux clients,create an exclude list for the policy that performs backups of those clients).When you add the shared disks to the Exclude List, it prevents the shared disksfrom being backed up with each client’s local disks.

■ Always include System_State:\ or Shadow Copy Components:\ in the file listto back up the System State for each cluster node. In a policy for an MSCScluster, System_State:\ or Shadow Copy Components:\ also backs up the clusterquorum information.

Backing up the shared disksTo protect the data on the shared disks, configure a policy that includes the virtualserver name in the Clients list. This server name must be associated with theshared disk. In addition to this policy, you must also configure a separate policyto back up the local disks.

See “Backing up local disks in a cluster” on page 96.

The following are guidelines for configuring the policy to back up the shared disks:

Configuring NetBackupBacking up local disks in a cluster

96

■ If you have a failover media server, when you create a backup policy, selectthe storage unit that you created for the failover media server.

■ If NetBackup is installed on the cluster as separate NetBackup media servers,select a storage unit that was created for one of the media servers. Or, selectAny Available.

■ If a storage unit does not have local, direct access to the shared disk drives,the data is backed up across the network. This action occurs even if the storageunit refers to a media server which runs on a node of the cluster that does notcurrently have control of the shared disk drives. In the Backup Selections list,specify the drive letters or mounted directories of the shared disks.Note that A backup fails if two separate cluster nodes control the clusterresource that defines the virtual server name and the resource that definesthe shared disks. Ensure that the virtual server name and the shared disks areconfigured to failover together so that the same node always controls them.

■ System State information is included in the backup of the node’s local disks.You do not need to include System_State:\ or Shadow Copy Components:\ inthe file list for this policy.

Backing up database files in a clusterDatabase applications are installed on a cluster as virtual servers. To protect thedata for these virtual servers, install the appropriate NetBackup database agenton each node of the cluster. (With NetBackup for Windows, database agents areinstalled along with NetBackup server and the NetBackup client.) Also create abackup policy for that database agent. When you configure a policy for theapplication or database in the cluster, always use the virtual server name of theapplication or database as the client name in the policy. For complete installationand configuration instructions for a particular database agent, see the NetBackupdocumentation for that agent.

User backupsUser backups that are run on individual nodes of the cluster generally run as abackup of the node, not the NetBackup virtual server. You may find easier to usescheduled backups rather than user backups to protect the data in the cluster.

97Configuring NetBackupBacking up database files in a cluster

Verifying NetBackup configurationAfter you complete the configuration of storage devices, volumes, the catalogbackup, and the backup policies, verify that NetBackup fails over properly in thecluster.

To verify NetBackup configuration

1 Confirm that the NetBackup is online on the primary node, then determineif the following can be completed successfully:

■ Scheduled backups

■ User-directed backups

■ NetBackup catalog backups

■ Server-and user-directed restores

2 Switch the NetBackup resource group to another node and perform the sametests in the previous step. Repeat for each node in the cluster where NetBackupis installed.

Configuring robotic daemons for monitoring(UNIX/Linux clusters)

By default, robotic daemons do not cause NetBackup to failover if they fail. Youcan configure robot daemons to failover NetBackup if a daemon fails.

Note: You must configure robots before you perform the following instructions.Refer to the NetBackup Installation Guide for instructions on how to configurestorage devices.

To configure NetBackup to failover if a robotic daemon fails

1 Configure your robots on each node in the cluster.

2 Run the following script:

/usr/openv/netbackup/bin/cluster/cluster_config -r

3 Choose a (Add).

4 Select your robot from the list.

Multiple robots can be selected.

Configuring NetBackupVerifying NetBackup configuration

98

To remove a robotic daemon from monitoring

1 Run the following script:

/usr/openv/netbackup/bin/cluster/cluster_config -r

2 Choose d (Delete).

3 Select the robot type you want to remove.

Configuring additional services (UNIX/Linux clusters)By default , all the necessary NetBackup services are added to the NetBackupCluster Group.

■ To add a service, run the following command.

/usr/openv/netbackup/bin/bpclusterutil

-addSvc "ServiceName"

This brings up the service when the group comes online, but the service is notmonitored. If the serviceServiceName fails, it does not cause the group tofailover.

■ To delete a service from the NetBackup Cluster Group, run the followingcommand


-deleteSvc "ServiceName"

Configuring add-ons for monitoring (UNIX/Linuxclusters)

By default, add-on products (such as NetBackup Vault) do not cause NetBackupto failover if they fail. These products can be configured to failover NetBackup ifan add-on product fails.

■ To enable monitoring for the optional services, run the following command:


-enableSvc"ServiceName"

■ To disable monitoring for the optional services, run the following command:

99Configuring NetBackupConfiguring additional services (UNIX/Linux clusters)


-disbleSvc"ServiceName"

Monitoring can be turned on or off for only NetBackup Vault Service andNetBackup Key Management Service. The ServiceName parameters for theseservices are nbvault, nbkms

Configuring additional services (Windows)By default , all the necessary NetBackup services are added to the NetBackupCluster Group.

■ To add a service, run the following command:

<NetBackup_install_path>\NetBackup\bin\bpclusterutil.exe

-addSvc "ServiceName"

This brings up the service when the group comes online, but the service is notmonitored. If the service ServiceName fails, it does not cause the group tofailover.

■ To delete a service from a NetBackup Cluster Group, run the followingcommand:


-deleteSvc "ServiceName"

Configuring add-ons for monitoring (Windows)By default, add-on products (such as NetBackup Vault) do not cause NetBackupto failover if they fail. These products can be configured to failover NetBackup ifan add-on product fails.

■ To enable monitoring for the optional services, run the following command:


-enableSvc "ServiceName"

■ To disable monitoring for the optional services, run the following command :


-disbleSvc "ServiceName"

Configuring NetBackupConfiguring additional services (Windows)

100

Monitoring can be turned on or off only for NetBackup Vault Service andNetBackup Key Management Service. The ServiceName parameters for theseservices are "NetBackup Vault Service", "NetBackup Key Management Service"

Adding license keysIf you add other licenses at the end of a Windows master server installation, thenyou must failover and add these licenses to each node in the cluster. If you addnew licenses later, you also need to failover to add these licenses to each node inthe cluster. On Windows, you can also use the bpminlicense command. OnUNIX/Linux servers, you can alternatively use the get_license command to addlicense keys without having to failover to each node.

Some features and products (such as NetBackup Shared Storage Option) requirethe keys to also be installed on the media server. If you have a NetBackup failovermedia server, any of these licenses must also be added to each node in the cluster.

101Configuring NetBackupAdding license keys

Configuring NetBackupAdding license keys

102

Using NetBackup toperform backups andrestores in a cluster


■ About performing backups and restores with NetBackup in a cluster

■ Performing user-directed backups with NetBackup in a cluster

■ Restoring data in a cluster

■ Example - Restoring data in a NetBackup cluster

About performing backups and restores withNetBackup in a cluster

This topic provides instructions on how to perform user-directed backups andrestore data in a cluster. Specific instructions for performing backups and restorescan be found in other NetBackup guides. See theNetBackup Backup, Archive, andRestore Getting Started Guide and the administrator guides for NetBackup’sdatabase agents and options.

The backup and restore process is the same whether you are in a cluster or anon-cluster environment. See the NetBackup Troubleshooting Guide for furtherinformation on backup and archive processes and on restore processes.

9Chapter

Performing user-directed backups with NetBackupin a cluster

When you perform user-directed backups in a cluster, you can use the node nameor the virtual name of the client to perform the backup. If you choose the virtualname, the backup can be restored from any of the cluster nodes. You can alsoconfigure automatic backups.

See “Configuring backup policies for a NetBackup clustered server” on page 95.

To perform a user-directed backup on a Windows client

1 Open the Backup, Archive, and Restore interface.

2 On the File menu, click Specify NetBackup Machines.

3 From the Source client list, select (or add) the wanted node or virtual name.

To perform a user-directed backup on a UNIX/Linux client

1 Start the Backup, Archive, and Restore interface.

2 In the Login dialog, enter the name of the client, either the node or the virtualclient name.

You must log on to the wanted node or virtual client. You cannot specify aclient other than the local client in the Java interface.

Restoring data in a clusterFor all file restore operations, use the procedures on how to perform restores inthe NetBackup Backup, Archive, and Restore Getting Started Guide. When yourestore files to the shared disk drives, restore those files to the virtual servername.

When you restore individual database files, restore those files to the virtual servername that corresponds to the client where the database application is installed.

Note:Since a computer can have multiple virtual names in a cluster environment,files can be backed up in the context of more than one client name. If you carefullyplan your backup policies, you can avoid this problem. However, it may benecessary to browse more than one client name to locate a backup image. Andyou may need to perform more than one restore to restore all of the files that youneed.

The Backup, Archive, and Restore interface operates in the context of that client’sname. You must perform a redirected restore to restore the files on the shared

Using NetBackup to perform backups and restores in a clusterPerforming user-directed backups with NetBackup in a cluster

104

disk that were backed up with the virtual server name. NetBackup allows aredirected restore operation only if the necessary configuration is performed onthe NetBackup master server. See the information on how to allow redirectedrestores in the NetBackup Administrator's Guide, Volume I.

There may be other situations that require the appropriate alt names directoryentries to be created on the master server. While NetBackup tries to restore filesfrom the client, the operation may fail with this error message:

131 client is not validated to use this server

If you see this message, you must set up the altnames directory to allow theoperation to succeed. For example, the required network interface parameter maybe set to a valid network name for the client. But this name may not match theNetBackup Client name parameter for that client. This situation often happensfor NetBackup clients in a cluster. Alternatively, you can perform a server-directedrestore and avoid the need to set up the alt names directory.

Example - Restoring data in a NetBackup clusterAssume the cluster virtual server name is TOE and the cluster node names areTIC and TAC. Files on the shared disk must be backed up by a NetBackup policythat includes TOE in the client list.

To perform a server-directed restore of files on the shared disk

Set both the source client and the destination client to TOE. The server-directedrestore does not have to know which node is in control of the shared disk at thetime of the restore.

To perform a user-directed restore of files on the shared disk

1 Create the following files on the master server.

For a UNIX/Linux server:

/usr/openv/netbackup/db/altnames/tic

/usr/openv/netbackup/db/altnames/tac

For a Windows server:

shared_drive_install_path\NetBackup\db\altnames\tic

shared_drive_install_path\NetBackup\db\altnames\tac

2 In both files, add the virtual server name TOE on one line in the file.

3 Determine which node (TIC or TAC) has control of the shared disk.

105Using NetBackup to perform backups and restores in a clusterExample - Restoring data in a NetBackup cluster

4 Start the Backup, Archive, and Restore interface on that node and select thevirtual server name (TOE) as the source client and the server.

(On Windows machines, in the File menu, click SpecifyNetBackupMachines.On UNIX/Linux machines, in the Actions menu, click NetBackupMachines.)

5 Browse the backed-up files by using the virtual server name (TOE) from theshared disk and restore them as needed.

Using NetBackup to perform backups and restores in a clusterExample - Restoring data in a NetBackup cluster

106

Operational notes


■ General notes

■ Delay in detecting of loss of connection (MSCS and VCS on Windows)

■ MSCS clusters

■ Managing the NetBackup cluster application

■ Logging

General notesConsider the following operational issues to consider when you use NetBackupas a failover server:

■ If a NetBackup server fails over and backup jobs are running, one of thefollowing things happen:

■ If Checkpoint Restart is enabled for backup jobs for the policy, any backupsthat were running are resumed at the last checkpoint. Note that the schedulewindow must permit the job to be resumed.

■ If Checkpoint Restart is not enabled for backup jobs, any backup jobs thatwere running fail. These jobs show up as failed jobs in the Activity Monitoror NetBackup reports. Scheduled backup jobs are retried according to thenormal retry logic. (See the Job retry delay and the Schedule backupattempts attributes). The schedule window and so on must permit the retryof the job. After a failover occurs, the user must restart user-directedbackups and manual backups.

Refer to theNetBackupAdministrator'sGuide,Volume I, for more informationon Checkpoint Restart, Job retry delay, and Scheduled backup attempts.

10Chapter

■ After a failover occurs on a NetBackup failover server (master or media), ittakes time for the tape devices and media servers to be reset. For example, atape may have to be rewound before it is made available. Until the device isagain ready for use, you may see errors. For example, you may see error 213(no storage units available for use) or error 219 (the required storage unit isunavailable).

■ After a failover, NetBackup may change the status of a drive that is requiredfor a backup or restore to PEND. More information is available about how touse the NetBackup Administration Console Device Monitor to resolve a pendingrequest or action.See the NetBackup Administrator’s Guide, Volume I.

■ If you have the NetBackup Administration Console open when a failover occurs,you need to refresh the display. This refresh ensures that the services on theactive node are displayed correctly. In the NetBackup Administration Console(from the View menu) click Refresh All.

■ The backup and restore process is the same whether you are in a cluster or anon-cluster environment. See theNetBackupTroubleshootingGuide for furtherinformation on backup and archive processes and on restore processes.

Delay in detecting of loss of connection (MSCS andVCS on Windows)

There may be a delay in the detection of the loss of a connection from a NetBackupWindows master server to a media server. For example, consider that a mediaserver goes down while running a backup. There may be a delay on the masterserver before it detects that the media server is no longer available. It may firstappear that a problem exists with the NetBackup Windows master server. Thisdelay is a result of a certain TCP/IP configuration parameter on Windows calledKeepAliveTime. By default, this parameter is set to 7,200,000 (two hours, inmilliseconds). More information about the KeepAliveTime and other associatedTCP/IP configuration parameters on Windows may be found in the followingMicrosoft knowledge base articles : Q140325 and Q120642.

Because of the delay jobs appear to be active on that media server even after theconnection to the media server has gone down. In some cases an undesirable delaycan occur before the current backup job fails. NetBackup tries to retry the job ona different media server, if one is available.

This delay is especially noticeable when the media server in question is aNetBackup failover media server that runs in a Microsoft Cluster Server (MSCS)environment. NetBackup relies upon the NetBackup master server to restart the

Operational notesDelay in detecting of loss of connection (MSCS and VCS on Windows)

108

NetBackup jobs that were running on the NetBackup failover media server whena failover occurs.

You may want to modify the KeepAliveTime configuration parameter on theNetBackup Windows master server. However, extreme caution because theparameter is a system wide parameter that affects all TCP/IP communicationsfor that system. Also, it may be advantageous to modify this parameter on Windowsmedia servers that use the failover master server.

MSCS clustersNote the following points before you use NetBackup as a failover server in anMSCS environment:

■ If there are no tape devices configured on the controlling node of the NetBackupfailover server, the NetBackup Device Manager service resource takes itselfoffline. If you do not intend to configure tape devices for the NetBackup failoverserver, you may want to delete the NetBackup Device Manager service resourcefrom the NetBackup group. This way you can avoid seeing the group in awarning state or failed state.

■ For MSCS clusters with three or more nodes, the MSCS Move Group commandlists all of the nodes in the cluster. You must pick a node that is valid for theNetBackup failover server to use. (MSCS displays all nodes in the cluster, eventhose nodes where NetBackup has not been installed.)

■ Also refer to the information in the previous sections for further notes thatare relevant to all cluster environments.

Managing the NetBackup cluster applicationOnly use the cluster application’s management tools to start and to stop NetBackupin the cluster. In a UNIX or Linux environment, do not use bp.start_all or bp.kill_allto start or stop NetBackup.

LoggingNetBackup records information on the processes. You can use this informationto determine why a server has failed over. Logging information is highly usefulfor troubleshooting.

109Operational notesMSCS clusters

About UNIX and Linux loggingLogging information for UNIX and Linux platforms can be found at the followinglocations:

■ Cluster configuration related information is recorded in log.cc.<date> file,which is located at /usr/openv/netbackup/logs/cluster. The configurationscripts creates the log directory, if it is not present.

■ Cluster upgrade related information is recorded intrace.cluster_upgrade.<process_ID> file, which is located at

/usr/openv/netbackup/logs/cluster.

■ Agent (Online/Offline/Monitor) related information is recorded inlog.<date>file, which is located at /usr/openv/netbackup/logs/cluster

■ Add the following configuration parameter “DEBUG_LEVEL=1” to the/usr/openv/netbackup/bin/cluster/NBU_RSP file to generated detailedlogging.

Note: This configuration is node specific and affects the logging level on thatenabled node. Enable this option only when required and turn it off when notrequired for storage considerations.

About Windows loggingLogging information for Windows platform can be found at the following locations:

■ Cluster configuration and upgrade related information is recorded in log.<date>file, which is located at <install_location>\netbackup\logs\cluster. If logdirectory is not present, it will be created by the Installer.

■ For Agent (MSCS) use Event Viewer .

■ For Agent (VCS) use NetBackupVCS agent log file, which is located in the logdirectory of VCS.

Operational notesLogging

110

Non-failover clusterconfigurations

This appendix includes the following topics:

■ Overview of non-failover cluster configurations

■ Non-failover media servers in a cluster

■ Installing NetBackup non-failover media servers in a cluster

■ Configuring NetBackup non-failover media servers in a cluster

■ Upgrading an existing NetBackup non-failover server in a cluster

■ NetBackup client in a cluster

Overview of non-failover cluster configurationsNetBackup can be installed as a non-failover application in a cluster, either as oneor more stand-alone media servers or as the NetBackup client.

Non-failover media servers in a clusterWith stand-alone media servers in a cluster, each server runs on a node of thecluster independently of the other. This installation does not provide failoverprotection of the NetBackup media server itself, but there can be other advantagesto this approach. Another way to use stand-alone media servers is to configurethe virtual storage units that fail over with an application. Refer to the followingtopic for more information on this type of configuration.


AAppendix

Installing NetBackup non-failover media servers in acluster

The following procedure describes how to install NetBackup as a non-failoverserver.

To install NetBackup as a non-failover server

1 Install the NetBackup server as you would in a non-clustered environment,according to the instructions in the NetBackup Installation Guide.

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

2 Continue with the configuration of NetBackup.

See “Configuring NetBackup non-failover media servers in a cluster”on page 112.

Configuring NetBackup non-failover media serversin a cluster

Configure each media server as you would in a non-clustered environment.

Upgrading an existingNetBackup non-failover serverin a cluster

The following procedure describes how to upgrade an existing non-failover server.

To upgrade a non-failover server


For complete information on how to configure and run online catalog backups,refer to the NetBackup Administrator’s Guide.

2 On each node where NetBackup is installed, install the NetBackup serversoftware on the local disk as you would in a non-cluster environment.

Follow the instructions for how to upgrade NetBackup servers as describedin the NetBackup Installation Guide.

Non-failover cluster configurationsInstalling NetBackup non-failover media servers in a cluster

112

NetBackup client in a clusterYou may choose to install only the NetBackup client in a cluster. In thisconfiguration, you can back up the data from the cluster across the network to aseparate NetBackup server. In this situation the NetBackup-specific configurationtasks for tape devices, media, and so on, are separate from the setup andmaintenance of the cluster itself. However, the NetBackup client itself cannot failover.

To install the NetBackup client on an MSCS, VCS, SunCluster , Service Guardcluster, or HACMP cluster

The NetBackup client is installed on a cluster as it is in a non-clusteredenvironment. Refer to the NetBackup Installation Guide for information on howto install the NetBackup client. On Windows systems, you may have problemswith name resolution when you try to back up data on the cluster. (This data canbe either local data or shared data.) Consider setting the Required NetworkInterface parameter for each client to the fully qualified name of the node wherethe NetBackup client is installed.

113Non-failover cluster configurationsNetBackup client in a cluster

Non-failover cluster configurationsNetBackup client in a cluster

114

NetBackup master server ina cluster using multipleinterfaces


■ Overview

■ Example scenario

■ Requirements

■ Configuration

OverviewIn a cluster environment, all NetBackup master server traffic and communicationflow through the network interface that is associated with the virtual name of themaster server. With the ANY_CLUSTER_INTERFACE configuration parameter,you can allow communication through any of the interfaces available to theNetBackup master server.

Example scenarioThe following figure depicts a scenario where a clustered NetBackup master serverhas access to two separate networks (168.1 and 192.1). Client machines are attachedto both networks and must be backed up. The virtual name for the master server(for example, NBUV168) can only be associated with one of the networks. So allNetBackup communication only occurs over that specific interface. Clients onother interfaces cannot be contacted.

BAppendix

Figure B-1 shows NetBackup in an environment with multiple network interfaces.

Figure B-1 NetBackup in an environment with multiple network interfaces

Client 1 Client 2

168.01 network

192.1 network

Client 3 Client 4

Media server

Media168

Media192

PrivateNetwork

NBUV168

NBUV192 NetBackup clusteredmaster server

Node 2Node 1

NA168 NB168

NA192 NB192

NetBackup master server in a cluster using multiple interfacesExample scenario

116

RequirementsThe following requirements exist when you use a NetBackup master server in acluster with multiple interfaces:

■ A cluster environment that is properly installed and configured.

■ Verify that you have a clustered NetBackup master server that is functional.

■ Enterprise Media Manager (EMM) must reside on the master server.

■ A unique virtual name (IP address and host name) associated with eachinterface.

■ NetBackup 6.0 MP1 or higher.

ConfigurationPerform the following steps to allow communication over an additional networkinterface.

To configure the NetBackup master server in a cluster using multiple interfaces

1 For each additional interface, add a virtual name and IP address resource inthe NetBackup cluster group.

This virtual name is the master server name the clients is referenced on theirparticular network.

2 Configure the ANY_CLUSTER_INTERFACE parameter.

3 On Windows, perform the following steps.

■ In regedit, go to the following.

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion

\Config

■ Create a new DWORD value that is called ANY_CLUSTER_INTERFACE.

■ Change the Value Data to 1.

4 On UNIX/Linux, add the following entry to the bp.conf.

ANY_CLUSTER_INTERFACE = 1

5 Add the following to the server list of the master server.

■ The node names of the master server, for each network interface.

■ The virtual name of the master server, for each network interface.

117NetBackup master server in a cluster using multiple interfacesRequirements

For example, to configure the master server in Figure B-1, add the following:NBUV168, NBUV192, NA168, NA192, NB168, NB192.

6 Add the node name of each media server to the media server list on the masterserver.

For example, add Media168 and Media192.

7 Repeat step 2 through step 6 for all nodes where the NetBackup master serveris installed.

8 Update the server list for all NetBackup clients.

The list must include all the possible names for the master server on theirnetwork. For example, for clients on the 168.1 network, include the servernames NBUV168, NA_168, and NB_168. For clients on the 192.1 network,include the server names NBUV192, NA_192, and NB_192.

NetBackup master server in a cluster using multiple interfacesConfiguration

118

Moving NBDB database filesin a UNIX/Linux cluster


■ Overview

■ Moving the database to additional shared disks

OverviewSybase ASA is supported for VCS for UNIX, SunCluster , Service Guard, andHACMP. Sybase ASA failover is included with NetBackup server failover solution.The software is installed on all machines in the cluster. The configuration filesare stored in /usr/openv/var/global and the database files are stored in directoryshared_drive.

Moving the database to additional shared disksYou can spread the NetBackup relational database over multiple shared disks toimprove performance. The database includes three components: the NetBackupsystem database file, NBDB.db; the EMM database file, EMM_DATA.db; and theNetBackup transaction log, NBDB.log. You can also create a mirrored log(NBDB.m.log). If the Bare Metal Restore (BMR) option is also installed, theseadditional database files are created: BMRDB.db, BMR_DATA.db, BMR_INDEX.db,and BMR.log. These files must be collocated with the NBDB database files.

You can distribute the database components as wanted. Though, if NBDB.db isrelocated, EMM_DATA.db (and BMRDB.db and BMR_DATA.db, if applicable) mustbe moved to the same location. For instance, you can put the mirrored transactionlog and the index on one disk. Then you can put the data log and transaction log

CAppendix

on another. Or you can move each of these components to their own disks. Allother shared NetBackup information (the netbackup/db and var or globaldirectories) can continue to reside on the original disk you chose when you runcluster_config.

For more information on the NetBackup relational database, refer to theNetBackupAdministrator’s Guide.

To move the database to additional shared disks

1 On SunCluster , make sure all of the additional disks are mounted.

2 Run the following command.

/usr/openv/netbackup/bin/cluster/util/cluster_mvnbdb

3 Follow the on-screen instructions.

If the BMR option is installed, its database files are moved automatically withthe NBDB files.

Moving NBDB database files in a UNIX/Linux clusterMoving the database to additional shared disks

120

Virtual storage units with astandalone media server ina NetBackup cluster


■ About virtual storage units with a standalone media server in a NetBackupcluster


■ Installation

■ About configuration of virtual storage units with a standalone media serverin a NetBackup cluster

■ Tape storage devices

■ Disk storage

■ Upgrading a NetBackup media server in a cluster with virtual storage units

About virtual storage units with a standalone mediaserver in a NetBackup cluster

In a typical NetBackup environment, the storage unit is associated with aNetBackup entity, such as the master server or media server. In the configurationthat is described in this topic, however, a storage unit is associated with the virtualname of the application in the cluster environment. The storage unit for thatapplication is not associated with any specific node in the cluster and can failoverto any node in the cluster. This guarantees that the storage unit follows along

DAppendix

with the application, wherever the application is running in the cluster. TheNetBackup master server uses the virtual name of the application as the mediaserver name when it backs up the clustered application.

This configuration is supported for Veritas Cluster Server (VCS), Microsoft ClusterServer (MSCS), SunCluster , Service Guard, and HACMP.

Installation prerequisitesThe following requirements exist when you configure a standalone NetBackupmedia server in a cluster with virtual storage units:

■ The clustering technology and NetBackup must be support your hardware.For a list of NetBackup supported storage devices, visit the following Web site.Also, refer to the documentation that is included with your clustering software.http://entsupport.symantec.com

■ Verify that storage devices have been properly installed and configured towork in the cluster environment. Refer to the information on how to configurestorage devices in the NetBackup Installation Guide.

■ An IP address and host name (virtual name) associated with each clusteredapplication.

■ Verify that your cluster (VCS, MSCS, SunCluster , Service Guard, or HACMP)is correctly installed and configured.

■ Make the NetBackup master server the EMM Server and the robotic controlhost. (You may not be able to change the robotic control host in allconfigurations since not all robot types have a robot control option.)

■ Verify that you have the NetBackup Enterprise Server 7.0 installation programand a valid license key. You must also have a valid license key for the NetBackupOpenStorage option, if you perform backups to tape.

InstallationInstall the NetBackup media server software on each node in the cluster. See theNetBackup Installation Guide for details.

Note: When you configure NetBackup as described in this topic, do not configurethe NetBackup media server as a failover application. The media server must betreated as a stand-alone application on each node in the cluster.

Virtual storage units with a standalone media server in a NetBackup clusterInstallation prerequisites

122


About configuration of virtual storage units with astandalone media server in a NetBackup cluster

Storage units are configured differently depending on whether the storage is disk-or tape-based.

Figure D-1 shows NetBackup as installed on local media servers.

Figure D-1 NetBackup as installed on local media servers

Application 2

Virtual Name = VA2

Application 3

Virtual Name = VA3

Application 1

Virtual Name = VA1

Application 1

shared disk

Application 2

shared disk

Application 3

shared disk

Fibre Channel SwitchHub

SCSI

123Virtual storage units with a standalone media server in a NetBackup clusterAbout configuration of virtual storage units with a standalone media server in a NetBackup cluster

Tape storage devicesThe following procedure describes how to configure a storage unit for a roboticdevice.

To configure a storage unit for a robotic device

1 Ensure NetBackup media server and the Shared Storage Option are installedand configured on all nodes in the cluster.

2 On the master server, make the following changes to the Servers list.

■ Add the hostname for each node of the cluster.

■ Add the virtual name for each highly available application.

For a UNIX/Linux environment, update the bp.conf file. For Windows, editthe Servers list in the host properties for the server.

3 On the master server, run the following command to add a host with thevirtual name of the application:

nbemmcmd -addhost -machinename virtual_name -machinetype app_cluster

where virtual_name is the virtual name of the application.

4 On the master server, run the following command to associate the host witheach node where the application runs in the cluster:

nbemmcmd -updatehost -add_server_to_app_cluster -machinename node_name

-machinetype media -clustername virtual_name

-netbackupversion 7.0 -masterserver master_name

where the node_name is a node where the application can run. virtual_nameis the virtual name of the application. master_name is the name of theNetBackup master server.

5 Repeat step 4 for each node where the application can run.

6 On each node where the media server is installed, make the following changesto the Servers list.



7 Use the Administration Console to create a storage unit for each application.Specify the virtual name of the application as media server name for thestorage unit.

Virtual storage units with a standalone media server in a NetBackup clusterTape storage devices

124

8 To back up each application, create a policy that specifies the storage unityou created in step 7 for that application.

Allocate specific tape devices for this configuration so storage units are notover-committed. You want to create storage units for each application withinthe cluster. Or, you may want to create storage unit groups that manyapplications can use.

Disk storageSymantec recommends that you use the NetBackup Administration Console toadd disk storage units. (You can also perform this task from the command line.)

To configure a storage unit for a disk

1 On the master server, make the following changes to the Servers list.



For a UNIX/Linux environment, update the bp.conf file. For Windows, editthe Servers list in the host properties for the server.

2 On the master server, run the following command to add a host with thevirtual name of the application:

nbemmcmd -addhost -machinename virtual_name -machinetype app_cluster


3 On the master server, run the following command to associate the host witheach node where the application runs in the cluster:

nbemmcmd -updatehost -add_server_to_app_cluster -machinename node_name

-machinetype media -clustername virtual_name

-netbackupversion 7.0 -masterserver master_name

where node_name is a node where the application can run. virtual_name isthe virtual name of the application.master_name is the name of the NetBackupmaster server.

4 Repeat step 3 for each node where the application can run.

5 On each node where the media server is installed, make the following changesto the Servers list.



125Virtual storage units with a standalone media server in a NetBackup clusterDisk storage

6 Use the Administration Console to create a disk storage unit for eachapplication. Specify the virtual name of the application as media server namefor the storage unit.

7 To back up each application, create a policy that specifies the storage unityou created in step 6 for that application.

Upgrading aNetBackupmedia server in a clusterwithvirtual storage units

The following procedure describes how to upgrade a standalone NetBackup 6.0or 6.5 media server in a cluster with virtual storage units.

To upgrade a NetBackup media server in a cluster with virtual storage units



2 On each node where NetBackup media server is installed, install the softwareon the local disk as you would in a non-cluster environment.

Follow the instructions on how to upgrade as described in the NetBackupInstallation Guide.

3 On the master server, enter the following command:

nbemmcmd -updatehost -machinename virtual_name -machinetype app_cluster

-netbackupversion 7.0


4 Repeat step 3 for each virtual application that you have in your clusterenvironment.

Virtual storage units with a standalone media server in a NetBackup clusterUpgrading a NetBackup media server in a cluster with virtual storage units

126

Aactive/active application

NetBackup as a 17Advanced Reporter

supported in a cluster 16altnames directory 105

Bbackup policies 95backups

and failovers 107of local disks in a cluster 96of shared disks 96user-directed 104what to back up in a cluster 95

bpclusterutil 24

Ccatalog backups

hot backups 95Checkpoint Restart 107CLIENT_NAME 91cluster configurations

mixed server types not supported 15NetBackup client 113NetBackup failover server 15NetBackup standalone media server 111

cluster quorumrestoring 26, 28

cluster solutionssupported 15

cluster_mvnbdb 120CLUSTER_NAME 91cmhaltpkg 76cmmodpkg 74cmrunpkg 76cmviewcl 76compatibility lists 16

configurationof NetBackup 91–92

information stored on shared disk 92server list 91usage of cluster aliases 91usage of node names 91verifying 98

Ddatabases

agents supported in a cluster 16device configuration

adding new devices 94attaching devices to all nodes 92guidelines 92–93instructions for HP MC/Service Guard 94instructions for MSCS 94instructions for Sun Cluster 94instructions for VCS 94specifying active node name 93

EEnable SCSI reserve 92

Ffailover

and manually refreshing NetBackupAdministration Console 108

and storage unit errors 108definition 14when backup jobs running 107

failover master servers 15failover media servers 15

GGlobal Data Manager (GDM)

NetBackup Operations Manager (NOM) 16

Index

HHACMP

backups in a 95, 104hardware requirements 78installation and configuration 80, 82installation prerequisites 78monitoring NetBackup options 82, 99monitoring robotic daemons 82, 98NetBackup database agents

installing or upgrading 82NetBackup options

installing or upgrading 82restores in a 104rsh equivalency 78upgrading a NetBackup failover server 83, 85

HP MC/Service Guardbackups in a 95, 104device configuration 94hardware requirements 68installation and configuration 71, 73installation prerequisites 68monitoring NetBackup options 73monitoring robotic daemons 73NetBackup database agents


installing or upgrading 73NetBackup resource group

bringing offline 76bringing online 76verifying it is online 76

remshequivalency 69restores in a 104shared disk configuration 68virtual name for NetBackup 68

HP MC/ServiceGuardmonitoring NetBackup options 99monitoring robotic daemons 98

JJob retry delay 92, 107

KKeepAliveTime 109

Llicense keys

adding to master server 101

license keys (continued)adding to media server 101

limitations 17LiveUpdate 17local disks

backups of 96loss of connection, to NetBackup Windows server 108

Mmedia servers

enhanced configuration 122non-failover 111, 122

Microsoft Cluster Administratorinstalling on all NetBackup servers 21

Microsoft Cluster Server (MSCS)backups in a 95, 104bpclusterutil 24device configuration 94disaster recovery 31hardware requirements 20installation notes 21installation prerequisites 20installing a NetBackup failover server 22–23loss of connection to NetBackup server 108monitoring NetBackup options 100Move Group 109NetBackup cluster group name 21NetBackup Device Manager 109Possible Owners list 21restores in a 25, 104restoring the cluster quorum 26upgrading a failover server 25virtual name for NetBackup 21

NNDMP

supported in a cluster 16NetBackup Administration Console

refreshing after failover 108NetBackup client

installing in a cluster 113NetBackup Device Manager 109NetBackup failover server

installing in a MSCS 21–22, 49installing in a VCS 48

NetBackup Operations Manager (NOM)supported in a cluster 16

Index128

NetBackup optionsmonitoring on a MSCS cluster 100monitoring on UNIX/Linux clusters 99supported in a cluster 16

NetBackup Serversupported in a cluster 17

non-failover serversconverting to failover servers 17

Ppending requests 108platforms supported for NetBackup in a cluster 16

RReconfigure NetBackup 50Required Network Interface parameter

for a Windows client 113restores 104

performing 104robotic daemons

monitoring on UNIX/Linux clusters 98robotic libraries 93

SSchedule backup attempts 107Scheduled backup attempts 92SCSI persistent reserve 92scstat 65scswitch 62–65server list 91

for clients 92server types

mixing 17shared disks

and storage units 97Shared Storage Option (SS0)

supported in a cluster 16storage units

active node name as NetBackup media server 93and NetBackup failover media servers 97and NetBackup non-failover media servers 97

Sun Clusterbackups in a 95, 104device configuration 94hardware requirements 58installation and configuration 59, 62installation notes 60installation prerequisites 58

Sun Cluster (continued)monitoring NetBackup options 62, 99monitoring robotic daemons 62, 98NetBackup database agents


installing or upgrading 62NetBackup resource group

bringing offline 65bringing online 64verifying it is online 65

restores in a 104RSH equivalency 58shared disk configuration 59upgrading a NetBackup failover server 63–64

supported cluster solutions 15

Ttpconfig 94

Uuser-directed backups

performing 104

VVault

supported in a cluster 16Veritas Cluster Server (VCS) for UNIX/Linux

backups in a 95, 104hardware requirements 34installation notes 38installing and configuring a NetBackup failover

server 38monitoring NetBackup options 41, 99monitoring robotic daemons 98NetBackup database agents

installing 40–41NetBackup options

installing 40–41monitoring 41

pre-installation checklist 35reconfiiguring NetBackup 50restores in a 104robotic daemons

monitoring 41rsh equivalency 34shared disk configuration 34supported NetBackup agent for 41

129Index

Veritas Cluster Server (VCS) for UNIX/Linux(continued)

upgrading a failover server 41virtual name for NetBackup 34

Veritas Cluster Server (VCS) for Windowsvirtual name for NetBackup 48

Veritas Cluster Server (VCS) for Windows 2000/2003backups in a 95, 104Clean 47detailed monitoring 53, 55device configuration 94installation notes 48installing a NetBackup failover server 49loss of connection

to NetBackup Windows server 108Monitor 46NetBackup cluster group name 48NetBackup service group 48Offline 46Online 46requirements 47restores in a 104upgrading a failover server 51

virtual server name 15and backups 97in the Clients list 96

virtual storage units 122

Index130

netbackup ha

Documents

symantec product

party software

licensed software

symantec logo

free software licenses

documentation version

technical support group

party programs