NetBackup AdminGuide HighAvailability

NetBackup_AdminGuide_HighAvailability.
book Page i Friday, October 24, 2003 12:04 PM
VERITAS NetBackup™ 5.0 High

Availability
System Administrator’s Guide
N102678
NetBackup_AdminGuide_HighAvailability.book Page ii Friday, October 24, 2003 12:04 PM
Disclaimer
The information contained in this publication is subject to change without notice. VERITAS Software
Corporation makes no warranty of any kind with regard to this manual, including, but not limited to,
the implied warranties of merchantability and fitness for a particular purpose. VERITAS Software
Corporation shall not be liable for errors contained herein or for incidental or consequential damages
in connection with the furnishing, performance, or use of this manual.
VERITAS Legal Notice

Copyright © 2002-2003 VERITAS Software Corporation. All rights reserved. VERITAS, VERITAS
Software, the VERITAS logo, VERITAS NetBackup, VERITAS Backup Exec, and all other VERITAS
product names and slogans are trademarks or registered trademarks of VERITAS Software
Corporation.VERITAS, the VERITAS Logo, VERITAS NetBackup Reg. U.S. Pat. & Tm. Off. Other
product names and/or slogans mentioned herein may be trademarks or registered trademarks of their
respective companies.
Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-Digest
Algorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved.
VERITAS Software Corporation
350 Ellis Street
Mountain View, CA 94043
USA
Phone 650–527–8000 Fax 650–527–2901
www.veritas.com
Third-Party Copyrights
ACE 5.2A: ACE(TM) is copyrighted by Douglas C.Schmidt and his research group at Washington University and University of California, Irvine,
Copyright (c) 1993-2002, all rights reserved.
IBM XML for C++ (XML4C) 3.5.1: Copyright (c) 1999,2000,2001 Compaq Computer Corporation; Copyright (c) 1999,2000,2001 Hewlett-Packard
Company; Copyright (c) 1999,2000,2001 IBM Corporation; Copyright (c) 1999,2000,2001 Hummingbird Communications Ltd.; Copyright (c)
1999,2000,2001 Silicon Graphics, Inc.; Copyright (c) 1999,2000,2001 Sun Microsystems, Inc.; Copyright (c) 1999,2000,2001 The Open Group; All
rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"),
to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell
copies of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this
permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting
documentation.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
JacORB 1.4.1: The licensed software is covered by the GNU Library General Public License, Version 2, June 1991.
Open SSL 0.9.6: This product includes software developed by the OpenSSL Project * for use in the OpenSSL Toolkit. (http://www.openssl.org/)
TAO (ACE ORB) 1.2a: TAO(TM) is copyrighted by Douglas C. Schmidt and his research group at Washington University and University of
California, Irvine, Copyright (c) 1993-2002, all rights reserved.
NetBackup_AdminGuide_HighAvailability.book Page iii Friday, October 24, 2003 12:04 PM
NetBackup Release 5.0 Revision History

The following table summarizes revisions made to this document for all 5.0 release
versions. See the NetBackup Release Notes for UNIX and Windows for more detailed
information.
Release Date Description
NetBackup 5.0 December 2003 Original version for this release.
NetBackup Release 5.0 Revision History iii

NetBackup_AdminGuide_HighAvailability.book Page iv Friday, October 24, 2003 12:04 PM
iv NetBackup High Availability System Administrator’s Guide

NetBackup_AdminGuide_HighAvailability.book Page v Friday, October 24, 2003 12:04 PM
Contents
NetBackup Release 5.0 Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
What Is In This Manual? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xii
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
NetBackup Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Accessibility Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
Chapter 1. Introduction to NetBackup High Availability . . . . . . . . . . . . . . . . . . . . . . . 1

How NetBackup Protects Data in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Supported Cluster Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Supported NetBackup Database Agents and Options in a Cluster . . . . . . . . . . . . . . 3
Accessing Compatibility Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Limitations of Using NetBackup with Clustering Solutions . . . . . . . . . . . . . . . . . . . . . . . 4
Media Manager Cluster Support Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Sample NetBackup Configuration in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 2. NetBackup in Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installing and Configuring a NetBackup Failover Server on a MSCS Cluster . . . . . . . . 8
Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Installation and Configuration Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
v
NetBackup_AdminGuide_HighAvailability.book Page vi Friday, October 24, 2003 12:04 PM
Upgrading a NetBackup Failover Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Installing Non-Failover Media Servers on a MSCS Cluster . . . . . . . . . . . . . . . . . . . . . . 10
Installing the NetBackup Client on a MSCS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Performing Backups and Restores in a MSCS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Restoring the Cluster Quorum for Windows 2000 Systems . . . . . . . . . . . . . . . . . . . 11
Restoring Cluster Quorum to Windows 2000 Node With Directory Services . . . . 12
Preparing for Disaster Recovery of A Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Disaster Recovery of A MSCS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Recovering the Entire Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Recovering NetBackup Data on a Shared Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chapter 3. NetBackup in HP Tru64 UNIX TruCluster . . . . . . . . . . . . . . . . . . . . . . . . 17

The CAA Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installing a NetBackup Server on a TruCluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Installation Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuring TruCluster to Use a Failover NetBackup Server . . . . . . . . . . . . . . . . . . . . 20
Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Upgrading a NetBackup Failover Server on a TruCluster . . . . . . . . . . . . . . . . . . . . . . . 22
Upgrading an Existing 4.5FPx or 4.5MP3 (or later) Failover Media Server to 5.0 . 23
Configuring TruCluster to Use a Non-Failover NetBackup Server . . . . . . . . . . . . . . . . 25
Upgrading a NetBackup Non-Failover Server on a TruCluster . . . . . . . . . . . . . . . . . . . 27
Upgrading an Existing Non-Failover Server to 5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Installing Only the NetBackup Client on a TruCluster . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Performing Backups and Restores in a TruCluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 4. NetBackup in VERITAS Cluster Server on Windows NT . . . . . . . . . . . . 29

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Installing the VCS Enterprise Agent for NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
vi NetBackup High Availability System Administrator’s Guide

NetBackup_AdminGuide_HighAvailability.book Page vii Friday, October 24, 2003 12:04 PM
Installing NetBackup Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Configuring the VCS Enterprise Agent 1.2.1 for NetBackup . . . . . . . . . . . . . . . . . . . . . 34
Configuring NetBackup for the VCS Enterprise Agent 1.2.1 . . . . . . . . . . . . . . . . . . . . . 38
Configuring Devices in a VCS for NT Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Upgrading NetBackup Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Performing Backups and Restores in a VCS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Chapter 5. NetBackup in VERITAS Cluster Server on Windows 2000 . . . . . . . . . . . 43

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Post-Installation Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Chapter 6. NetBackup in VERITAS Cluster Server on UNIX . . . . . . . . . . . . . . . . . . . 47

About the VCS Enterprise Agent for NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Detecting an Application Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Additional Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Pre-Installation Checklist for a NetBackup Failover Server Installation . . . . . . . . . . . . 50
For VCS Solaris and Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Scenario 1 - Using VxVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Scenario 2- Disk Only, No Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
For VCS AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Scenario 2 - Using AIX LVMVG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Scenario 3 - Disk Only, No Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
For VCS HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Scenario 2 - Using Logical Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Contents vii
NetBackup_AdminGuide_HighAvailability.book Page viii Friday, October 24, 2003 12:04 PM
Scenario 3 - Disk Only, No Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Installing and Configuring a Failover NetBackup Server . . . . . . . . . . . . . . . . . . . . . . . . 57
Installation and Configuration Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Installing or Upgrading NetBackup Agents and Options . . . . . . . . . . . . . . . . . . . . . . . 58
Upgrading a NetBackup Failover Server from 4.5FPx or 4.5 MPx to 5.0 . . . . . . . . . . . 60
Installing a Non-Failover NetBackup Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Upgrading a NetBackup Non-Failover Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Installing the NetBackup Client Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Performing Backups and Restores in a VCS Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Chapter 7. NetBackup in Sun Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Installation Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Installation and Configuration Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Installing or Upgrading NetBackup Agents and Options . . . . . . . . . . . . . . . . . . . . . . . 69
Upgrading from NetBackup 4.5FP3 or later (With Sun Microsystem’s NetBackup
Agent) to 5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Performing Backups and Restores in a Sun Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Chapter 8. Configuring NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

NetBackup Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Device Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Configuring Devices in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Configuring Devices for MSCS, VCS, or Sun Cluster . . . . . . . . . . . . . . . . . . . . . 76
Configuring Devices for a TruCluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Verifying NetBackup Catalog Backup Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Windows Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
UNIX Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Verifying NetBackup Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
viii NetBackup High Availability System Administrator’s Guide

NetBackup_AdminGuide_HighAvailability.book Page ix Friday, October 24, 2003 12:04 PM
Configuring Robotic Daemons for Monitoring (VCS for UNIX, TruCluster, or

Sun Cluster) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Configuring Add-ons for Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Configuring Add-ons for Monitoring in a VCS for UNIX, TruCluster, or Sun Cluster
Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Configuring Add-ons for Monitoring in a MSCS Environment . . . . . . . . . . . . . . . . 81
Chapter 9. Using NetBackup to Perform Backups and Restores in a Cluster . . . . . 83

What to Back Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Backing Up Local Disks in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Backing the Shared Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Backing Up Database Files in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Restoring Data in a Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Chapter 10. Operational Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Delay in Detecting of Loss of Connection (MSCS and VCS on Windows) . . . . . . . . . . 90
MSCS Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Appendix A. Additional Configurations for NetBackup and Clusters . . . . . . . . . . . 93

Cluster with Tape Devices on a Shared SCSI Bus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Configuring a Shared SCSI Bus for Tape Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Cluster with Locally-attached Storage Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Clusters Sharing Devices on a Fibre Channel SAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Appendix B. bpclusterutil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
Contents ix
NetBackup_AdminGuide_HighAvailability.book Page x Friday, October 24, 2003 12:04 PM
x NetBackup High Availability System Administrator’s Guide

NetBackup_AdminGuide_HighAvailability.book Page xi Friday, October 24, 2003 12:04 PM
Preface
This guide provides information on how to install and configure NetBackup to work with
different clustering solutions.
NetBackup provides high-performance backups and restores for a variety of computer
types. Administrators can set up schedules for automatic, unattended backups for clients
anywhere in the network. These backups can be full or incremental and are managed
entirely by the NetBackup server (also referred to as the NetBackup master server). For
information about NetBackup, refer to the NetBackup System Administrator's Guide for
Windows, Volume I, and NetBackup System Administrator's Guide for UNIX, Volume I.
This guide is intended for the NetBackup system administrator responsible for
configuring NetBackup. A system administrator is a person with system administrator
privileges and responsibilities. This guide assumes:
◆ A basic understanding of Windows and UNIX system administration.
◆ A working understanding of the NetBackup for Windows and UNIX client software.
◆ A working understanding of the NetBackup for Windows and UNIX server software.
◆ A familiarity with the information covered in the following NetBackup manuals:
◆ NetBackup System Administrator’s Guide for UNIX or NetBackup System
Administrator’s Guide for Windows.
◆ NetBackup Troubleshooting Guide for UNIX and Windows.
◆ A working understanding of your cluster software.
xi
NetBackup_AdminGuide_HighAvailability.book Page xii Friday, October 24, 2003 12:04 PM
What Is In This Manual?
What Is In This Manual?

This guide is organized as follows:
◆ “Introduction to NetBackup High Availability” contains information how NetBackup
works in a cluster and sample configurations.
◆ “NetBackup in Microsoft Cluster Server” describes how to install and configure
NetBackup in a Microsoft Cluster Server environment.
◆ “NetBackup in HP Tru64 UNIX TruCluster” describes how to install and configure
NetBackup in a HP Tru64 UNIX TruCluster environment.
◆ “NetBackup in VERITAS Cluster Server on Windows NT” describes how to install
and configure NetBackup in a VERITAS Cluster Server 1.21 for Windows NT
environment.
◆ “NetBackup in VERITAS Cluster Server on Windows 2000” describes installation
prerequisites and post-installation instructions for configuring NetBackup in a
VERITAS Cluster Server 2.0 for Windows 2000 environment.
◆ “NetBackup in VERITAS Cluster Server on UNIX” describes how to install and
configure NetBackup in a VERITAS Cluster Server in a UNIX environment.
◆ “NetBackup in Sun Cluster” describes how to install and configure NetBackup in a
Sun Cluster environment.
◆ “Configuring NetBackup” includes guidelines for configuring the NetBackup Server,
including device configuration.
◆ “Using NetBackup to Perform Backups and Restores in a Cluster” describes what
data should be backed up in a cluster and guidelines for how to back up and restore
data in a cluster.
◆ “Operational Notes” covers general information about using NetBackup in a cluster
environment.
◆ “Additional Configurations for NetBackup and Clusters” provides further examples
of NetBackup can be configured in a cluster.
◆ “bpclusterutil” describes this command and how to use it to modify and configure
NetBackup in a Windows cluster.
xii NetBackup High Availability System Administrator’s Guide

NetBackup_AdminGuide_HighAvailability.book Page xiii Friday, October 24, 2003 12:04 PM
Getting Help
Getting Help
Use the VERITAS Technical support web site to get help for NetBackup if you have
questions.
Accessing the VERITAS Technical Support Web Site

The VERITAS Technical Support Web site allows you to do any of the following:
◆ obtain updated information about NetBackup, including system requirements,
supported platforms, and supported peripherals
◆ contact the VERITAS Technical Support staff and post questions to them
◆ get the latest patches, upgrades, and utilities
◆ view the NetBackup Frequently Asked Questions (FAQ) page
◆ search the knowledge base for answers to technical support questions
◆ receive automatic notice of product updates
◆ find out about NetBackup training
◆ read current white papers related to NetBackup
The address for the VERITAS Technical Support Web site follows:
http://support.veritas.com
Using VERITAS Telephone and E-mail Support

Telephone support for NetBackup is only available with a valid support contract. To
contact VERITAS for technical support, dial the appropriate phone number listed on the
Technical Support Guide included in the product box and have your product license
information ready for quick navigation to the proper support group.
▼ To locate the telephone support directory on the VERITAS web site
1. Open http://support.veritas.com in your web browser.
2. Click the Phone Support icon. A page that contains VERITAS support numbers from
around the world appears.
Preface xiii
NetBackup_AdminGuide_HighAvailability.book Page xiv Friday, October 24, 2003 12:04 PM
NetBackup Manuals
▼ To contact support using E-mail on the VERITAS web site
1. Open http://support.veritas.com in your web browser.
2. Click the E-mail Support icon. A brief electronic form will appear and prompt you to:
◆ Select a language of your preference
◆ Select a product and a platform
◆ Associate your message to an existing technical support case
◆ Provide additional contact and product information, and your message
3. Click Send Message.
NetBackup Manuals
The following manuals, along with the online help, comprise the NetBackup
documentation set. For a more detailed listing of NetBackup documents, refer to
NetBackup Release Notes for UNIX and Windows.
If you have a UNIX server, refer to these documents:
◆ VERITAS NetBackup System Administrator's Guide for UNIX, Volume I
NetBackup_AdminGuideI_UNIXServer.pdf
Explains how to configure and manage NetBackup on a UNIX server, including
managing storage units, backup policies, catalogs and host properties.
◆ VERITAS NetBackup System Administrator's Guide for UNIX, Volume II
NetBackup_AdminGuideII_UNIXServer.pdf
Explains additional NetBackup features such as notify scripts, enhanced
authorization and authentication, and role-based security. The guide also discusses
using NetBackup with AFS, Intelligent Disaster Recovery (IDR), and the BE Tape
Reader.
◆ NetBackup Media Manager System Administrator’s Guide for UNIX
Explains how to configure and manage the storage devices and media on UNIX
NetBackup servers. Media Manager is part of NetBackup.
◆ VERITAS NetBackup Commands for UNIX
NetBackup_Commands_UNIX.pdf
Describes NetBackup and Media Manager commands and processes that can be run
from a UNIX command line.
xiv NetBackup High Availability System Administrator’s Guide

NetBackup_AdminGuide_HighAvailability.book Page xv Friday, October 24, 2003 12:04 PM
NetBackup Manuals
If you have a Windows server, refer to these documents:

◆ VERITAS NetBackup System Administrator’s Guide for Windows, Volume I
NetBackup_AdminGuideI_WinServer.pdf
Explains how to configure and manage NetBackup on a Windows server, including
managing storage units, backup policies, catalogs and host properties.
◆ VERITAS NetBackup System Administrator’s Guide for Windows, Volume II
NetBackup_AdminGuideII_WinServer.pdf
Explains additional NetBackup features such as notify scripts, enhanced
authorization and authentication, and role-based security. The guide also discusses
using NetBackup with AFS, Intelligent Disaster Recovery (IDR), and the BE Tape
Reader.
◆ NetBackup Media Manager System Administrator’s Guide for Windows
Explains how to configure and manage the storage devices and media on Windows
NetBackup servers. Media Manager is part of NetBackup.
◆ VERITAS NetBackup Commands for Windows
NetBackup_Commands_Windows.pdf
Describes NetBackup and Media Manager commands and processes that can be run
from a Windows command prompt.
Also refer to the following documents:
◆ VERITAS NetBackup Troubleshooting Guide for UNIX and Windows
Provides troubleshooting information for UNIX- and Windows-based NetBackup
products, including Media Manager.
◆ VERITAS NetBackup Media Manager Device Configuration Guide for UNIX and Windows
MediaMgr_DeviceConfig_Guide.pdf
Explains how to add device drivers and perform other system-level configurations for
storage devices and media servers (or SAN media servers) that are supported by
NetBackup Media Manager.
◆ VERITAS NetBackup SAN Shared Storage Option System Administrator’s Guide for UNIX
and Windows
MediaMgr_AdminGuide_SSO.pdf
Provides information on installing and configuring the NetBackup Shared Storage
Option (SSO) on UNIX and Windows-based servers. SSO is an extension to tape drive
allocation and configuration for NetBackup Media Manager.
Preface xv
NetBackup_AdminGuide_HighAvailability.book Page xvi Friday, October 24, 2003 12:04 PM
Accessibility Features
Glossary
If you encounter unfamiliar terminology, consult the NetBackup online glossary. The
glossary contains terms and definitions for NetBackup and all additional NetBackup
options and agents.
The NetBackup online glossary is included in the NetBackup help file.
▼ To access the NetBackup online glossary
1. In the NetBackup Administration Console (or from the Backup, Archive, and Restore
client interface), click Help > Help Topics.
2. Click the Contents tab.
3. Double-click Glossary.
4. Click NetBackup Glossary of Terms.

The glossary displays in a help window. Use the scroll function to navigate through the
glossary.
Accessibility Features
NetBackup contains features that make the user interface easier to use by people who are
visually impaired and by people who have limited dexterity. Accessibility features
include:
◆ Support for assistive technologies such as screen readers and voice input (Windows
servers only)
◆ Support for keyboard (mouseless) navigation using accelerator keys and mnemonic
keys
For more information, see the NetBackup System Administrator’s Guide, Volume I.
Conventions
The following section explains typographical and other conventions used in this guide.
Product-Specific Conventions
The following term is used in the NetBackup documentation to increase readability while
maintaining technical accuracy.
xvi NetBackup High Availability System Administrator’s Guide

NetBackup_AdminGuide_HighAvailability.book Page xvii Friday, October 24, 2003 12:04 PM
Conventions
◆ Microsoft Windows, Windows

Terms used to describe a specific product or operating system developed by
Microsoft, Inc. Some examples you may encounter in NetBackup documentation are,
Windows servers, Windows 2000, Windows Server 2003, Windows clients, Windows
platforms, or Windows GUI.
When Windows or Windows servers is used in the documentation, it refers to all of
the currently supported Windows operating systems. When a specific Windows
product is identified in the documentation, only that particular product is valid in that
instance.
For a complete list of Windows operating systems and platforms that NetBackup
supports, refer to the NetBackup Release Notes for UNIX and Windows or go to the
VERITAS support web site at http://www.support.veritas.com.
Typographical Conventions
Here are the typographical conventions used throughout the manuals:
Conventions
Convention Description
GUI Font Used to depict graphical user interface (GUI) objects, such as fields,
listboxes, menu commands, and so on. For example: Enter your
password in the Password field.
Italics Used for placeholder text, book titles, new terms, or emphasis. Replace
placeholder text with your specific text. For example: Replace filename
with the name of your file. Do not use file names that contain spaces.
This font is also used to highlight NetBackup server-specific or operating
system-specific differences. For example: This step is only applicable for
NetBackup Enterprise Server.
Code Used to show what commands you need to type, to identify pathnames
where files are located, and to distinguish system or application text that
is displayed to you or that is part of a code example.
Key+Key Used to show that you must hold down the first key while pressing the
second key. For example: Ctrl+S means hold down the Ctrl key while
you press S.
You should use the appropriate conventions for your platform. For example, when
specifying a path, use backslashes on Microsoft Windows and slashes on UNIX.
Significant differences between the platforms are noted in the text.
Preface xvii
NetBackup_AdminGuide_HighAvailability.book Page xviii Friday, October 24, 2003 12:04 PM
Conventions
Tips, notes, and cautions are used to emphasize information. The following samples
describe when each is used.
Tip Used for nice-to-know information, like a shortcut.
Note Used for important information that you should know, but that shouldn’t cause any
damage to your data or your system if you choose to ignore it.
Caution Used for information that will prevent a problem. Ignore a caution at your own
risk.
Command Usage
The following conventions are frequently used in the synopsis of command usage.
brackets [ ]
The enclosed command line component is optional.
Vertical bar or pipe (|)
Separates optional arguments from which the user can choose. For example, when a
command has the following format:
command arg1|arg2
In this example, the user can use either the arg1 or arg2 variable.
Navigating Multiple Menu Levels

When navigating multiple menu levels, a greater-than sign (>) is used to indicate a
continued action.
The following example shows how the > is used to condense a series of menu selections
into one step:
❖ Select Start > Programs > VERITAS NetBackup > NetBackup Administration
Console.
The corresponding actions could be described in more steps as follows:
1. Click Start in the task bar.
2. Move your cursor to Programs.
3. Move your cursor to the right and highlight VERITAS NetBackup.
xviii NetBackup High Availability System Administrator’s Guide

NetBackup_AdminGuide_HighAvailability.book Page xix Friday, October 24, 2003 12:04 PM
Conventions
4. Move your cursor to the right. First highlight and then click NetBackup
Administration Console.
Terms Used in this Document

◆ Microsoft Cluster Server
Microsoft Cluster Server will also be referred to as MSCS in this document.
◆ VERITAS Volume Manager
VERITAS Volume Manager will also be referred to as Volume Manager in this
document.
◆ VERITAS Cluster Server
VERITAS Cluster Server will also be referred to as VCS in this document.
◆ HP Tru64 UNIX TruCluster
HP Tru64 UNIX TruCluster will also be referred to as TruCluster.
Preface xix
NetBackup_AdminGuide_HighAvailability.book Page xx Friday, October 24, 2003 12:04 PM
Conventions
xx NetBackup High Availability System Administrator’s Guide

NetBackup_AdminGuide_HighAvailability.book Page 1 Friday, October 24, 2003 12:04 PM
Introduction to NetBackup High Availability 1

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

There are several ways to use NetBackup for protecting the data in a cluster environment.
One way is to back up the data from a cluster across the network to a separate NetBackup
server by installing a NetBackup client. This is the easiest method to set up and maintain
since the NetBackup-specific configuration tasks for tape devices, media, and so on, are
kept separate from the set up and maintenance of the cluster itself.
Another approach is to install a NetBackup media server. This allows you to back up the
data to tape devices that attach directly to one or more of the nodes without going across
the network.
A NetBackup media server can be installed on the cluster either as a single media server
running as a virtual server application, or it can be installed as separate media servers,
each running on a node of the cluster independently of the other. Of course, installing
separate media servers on each node of the cluster does not provide failover protection of
the NetBackup media server itself, but there can be other advantages to this approach.
Installing a single NetBackup media server on the cluster as a virtual server application
allows the media server to failover from one of the nodes to the other as described
previously. This is called a NetBackup failover media server.
1
How NetBackup Protects Data in a Cluster
When you install a NetBackup failover media server, you assign NetBackup a virtual
server name/IP address resource and a shared disk resource. Note that the network name
and IP address must be unique and set up in your name resolution configuration prior to
setting up a NetBackup failover server.
The virtual server name is used in the NetBackup storage unit and added to the server list
of any NetBackup clients to be backed up to this media server. When a failover occurs,
backup jobs that were running are rescheduled by using the normal NetBackup retry logic
for a failed backup. The NetBackup services are restarted on another node and backup
processing resumes.
Yet another approach is to install a NetBackup master server on the cluster as a virtual
server application. This is called a NetBackup failover master server and as the name
implies, allows the duties of the master server to failover from one of the nodes to the
other if a failure occurs on the active node. This provides high availability of the
NetBackup master server itself.
As with a NetBackup failover media server, when you install a NetBackup failover master
server, you assign it a network name resource (the virtual server name), an IP address
resource, and a disk resource. Note that the network name and IP address must be unique
and set up in your name resolution configuration prior to setting up a NetBackup failover
server.
The virtual server name is used as the name of the master server for all media servers and
clients using this master server. As above, when a failover occurs, backup jobs that were
running are rescheduled using the normal NetBackup retry logic for a failed backup. The
NetBackup services are restarted for the failover node and processing resumes.
Both types of NetBackup failover servers, master and media, operate in an active/passive
failover configuration. The active node and the passive (or failover node) must be the
same type of server, master or media. Mixing the two server types in the same failover
server configuration is not supported. For example, a master server on one node cannot
failover to a media server on another node.
Specific details of how NetBackup runs in a cluster vary depending on the configuration
you use in the cluster. (For information about the supported configurations and their
specific requirements, see “Additional Configurations for NetBackup and Clusters” on
page 93.)
2 NetBackup High Availability System Administrator’s Guide

Supported Cluster Solutions

NetBackup supports the following cluster environments. For more information on
installing and configuring NetBackup in that type of cluster, refer to the chapter or
document listed in the Table “Supported Cluster Solutions.”
Cluster Solution Refer to ...
Microsoft Cluster Server “NetBackup in Microsoft Cluster Server” on page 7
HP Tru64 UNIX TruCluster “NetBackup in HP Tru64 UNIX TruCluster” on page 17
VERITAS Cluster Server on Windows “NetBackup in VERITAS Cluster Server on Windows NT”
NT on page 29
VERITAS Cluster Server 2.0 on “NetBackup in VERITAS Cluster Server on Windows 2000”
Windows 2000 on page 43 and the VERITAS Cluster Server Enterprise
Agent 2.2 for NetBackup Installation and Configuration
Guide
VERITAS Cluster Server on UNIX “NetBackup in VERITAS Cluster Server on UNIX” on

page 47
Sun Cluster “NetBackup in Sun Cluster” on page 65
Supported NetBackup Database Agents and Options in a

Cluster
To see the list of database agents and NetBackup options that are supported in a clustered
environment, refer to the following section “Accessing Compatibility Lists.” For
information on installing and configuring agents and options in a cluster, refer to the
system administrator’s guide for that agent or option.
Chapter 1, Introduction to NetBackup High Availability 3

Limitations of Using NetBackup with Clustering Solutions
Accessing Compatibility Lists

The VERITAS support web site now contains the most current platform support
information for NetBackup. To locate the latest information on the VERITAS support web
site, perform the following procedure.
▼ To access the compatibility lists on the VERITAS support website
1. Go to the VERITAS support web page: www.support.veritas.com.
2. In the left margin of the VERITAS Support page, choose Compatibility Lists. The
Online Compatibility Lists page appears.
3. From the Product List, choose +NetBackup Products. The list refreshes showing a list
of NetBackup products.
4. Choose a NetBackup product. This page contains various links to supported platform
lists.
Limitations of Using NetBackup with Clustering Solutions

The following limitations exist for NetBackup:
◆ Converting an existing non-failover NetBackup server to a highly available failover
NetBackup server is not supported. NetBackup must be uninstalled, then installed
again.
◆ All NetBackup nodes within a cluster must be of the same server type. Master and
Media servers cannot be mixed in a cluster.
◆ NetBackup is not supported as an active/active application in a cluster.
Media Manager Cluster Support Limitations

The following limitations have been identified to affect clustering support in Media
Manager.
1. Retries on All Failover Events

When failover occurs, any task that is in process needs to be able to recover and
continue. Communication needs to be re-established using the new node, and all
operations that were in progress need to be retried on the new node.

Sample NetBackup Configuration in a Cluster
2. Breaking SCSI Reservations

When fail over occurs in an environment where SCSI Reserve/Release is being used
(explicitly in NetBackup, or implicitly in lower-level drivers or hardware), a SCSI
Reservation will be left on the drive. The drive will remain unusable by other nodes
and other hosts until the SCSI reservation is cleared.
3. Failover for Assigned Drives and In-progress Mount/dismount Activity

State information (drive status, mount status, cleaning status, robotic library status,
eject/inject status, etc.) is not in a database, as these states are in process memory,
which is lost at failover time. On the new node, none of this information will be
reestablished by bringing up the daemons/services. The “SSO drive allocation
resiliency” feature in NetBackup 5.0 addresses this only for the device allocator
(vmd/DA) component for SSO. This alone does not make SSO failover-safe, plus
virtually all other Media Manager tasks also remain non-failover friendly.
4. No Transaction Support in All Database Operations

Current tasks include making multiple database operations to reflect one event. For
example, scenarios where changes are made by deletion and re-addition, or changes
where multiple records are related (such as, optical partner relationships), or where
robots are deleted and drives in the robot need also to be deleted.

Example of a cluster with NetBackup and tape devices that are shared.
NetBackup Virtual Server
Controlling node Failover node
Shared Disks
Shared Tape
Private Network
LAN
Chapter 1, Introduction to NetBackup High Availability 5


NetBackup in Microsoft Cluster Server 2

This chapter provides information on how to install and configure NetBackup in a
Microsoft Cluster Server environment. Refer to the NetBackup System Administrator's Guide
for Windows, Volume I for a detailed understanding of how NetBackup is installed and
administered. Refer to the documentation for MSCS for a detailed understanding of how
MSCS works and how it is installed and administered.
7
Installation Prerequisites
❏ Verify all hardware (used for nodes) is supported by MSCS and NetBackup. For a list
of supported storage devices, see the NetBackup Release Notes for UNIX and Windows
and the MSCS documentation.
❏ Verify that storage devices have been properly installed and configured to work in a
Windows environment. Refer to “Configuring Storage Devices for Windows” in the
NetBackup Installation Guide for Windows.
❏ Verify that Microsoft Cluster Server is correctly installed and configured (all versions
are supported with NetBackup 5.0). NetBackup can be installed on as many nodes as
MSCS supports. MSCS supports up to 4 or 8 nodes in a cluster, depending on the level
of Windows that is installed.
❏ If you want the NetBackup Media Server to be highly available, the robotic and tape
devices must be physically connected to all the nodes that would be part of the
NetBackup High Availability setup. This can be done via SCSI or fibre channel.Verify,
using OS commands, that all the devices are connected properly. Refer to the Media
Manager Device Configuration Guide for UNIX and Windows.
❏ Using Cluster Administrator, verify that the Possible Owners list for each disk
resource used by NetBackup includes each node to which NetBackup can failover.
❏ Verify you have the NetBackup Enterprise Server 5.0 installation media and a valid
license key.
Installing and Configuring a NetBackup Failover Server on

a MSCS Cluster
The Microsoft Cluster Administrator must be installed on all NetBackup servers
(including NetBackup Administration Clients) that you will use to remotely administer
the NetBackup failover server (master or media). You must also have administrator rights
to the server cluster.
Installation Notes
◆ These instructions assume that this is a new installation of a NetBackup failover
server.
◆ The same type of NetBackup server must be installed on each node to which
NetBackup may failover. You cannot install a master server and a media server in a
failover configuration.

Installing and Configuring a NetBackup Failover Server on a MSCS Cluster
◆ If you are installing a NetBackup failover media server, ensure that all media server
nodes reference the same NetBackup master server name during the install.
◆ Once NetBackup has been configured as a cluster group in MSCS, do not change the
group name.
Installation and Configuration Instructions

▼ To install a NetBackup failover server on a MSCS cluster
1. On each desired node in the cluster, install the NetBackup master or media server.
Follow the instructions for installing NetBackup in a clustered environment as
described in the NetBackup Installation Guide for Windows.
2. Add licenses for any NetBackup agents or options (note that some agents and options
require a separate installation). See the appropriate NetBackup documentation for the
agent or option for installation and configuration instructions.
3. After the installation is complete, continue with the configuration of NetBackup.

◆ Refer to “NetBackup Configuration Guidelines” on page 74 for guidelines on
configuring NetBackup.
◆ Refer to “Device Configuration Guidelines” on page 74 and “Configuring Devices
in a Cluster” on page 75 for guidelines and instructions on configuring devices in
a cluster. Note that devices must be configured on each node in the cluster.
◆ See “Verifying NetBackup Catalog Backup Entries” on page 77 for instructions on
verifying that the entries for the NetBackup Catalog backups are correct.
◆ By default, NetBackup options (such as NetBackup Advanced Reporter) will not
cause NetBackup to failover if they fail. NetBackup options can be configured to
failover NetBackup if a daemon or the option fails. For more information, see
“Configuring Add-ons for Monitoring in a MSCS Environment” on page 81.
Chapter 2, NetBackup in Microsoft Cluster Server 9

Upgrading a NetBackup Failover Server
4. When you have completed configuration of NetBackup, verify that NetBackup can
fail over properly in the cluster. Refer to “Verifying NetBackup Configuration” on
page 79.
Note Under normal circumstances, cluster configuration is one of the final steps in
installing NetBackup in a cluster. If this step is not done or does not complete
successfully, the bpclusterutil command may be used perform this step. The
“bpclusterutil -c” command runs the cluster configuration step performed by
installation. Using the -a option with the appropriate option name configures the
NetBackup option in a cluster. This command can be run multiple times. Only run
this command from the active node. See the Appendix “bpclusterutil” on page 99
for more information.
Upgrading a NetBackup Failover Server

Follow the instructions for upgrading NetBackup in a clustered environment as described
in the NetBackup Installation Guide for Windows.
Note By default, NetBackup options (such as NetBackup Advanced Reporter) will not
cause NetBackup to failover if they fail. NetBackup options can be configured to
failover NetBackup if a daemon or the option fails. For more information, see
“Configuring Add-ons for Monitoring in a MSCS Environment” on page 81.
Note Converting an existing non-failover NetBackup server to a highly available failover

NetBackup server is not supported.
Installing Non-Failover Media Servers on a MSCS Cluster

Instead of installing a NetBackup failover media server on a MSCS cluster, you can install
a non-failover NetBackup media server on each desired node of the cluster. There is no
cluster failover protection of the NetBackup media server when it is installed this way. A
media server is installed on a cluster just as it is in a non-clustered environment.
▼ To install a NetBackup non-failover Media server on a MSCS cluster
1. Review “Installation Prerequisites” on page 8.
2. Install the NetBackup Media Server software on each desired node in the cluster.
Refer to the NetBackup Installation Guide for Windows for instructions.

Installing the NetBackup Client on a MSCS Cluster
3. Configure each NetBackup media server. Refer to the following manuals for
information on configuring media servers:
◆ NetBackup Installation Guide for Windows
◆ NetBackup Media Manager System Administrator's Guide for Windows
◆ NetBackup System Administrator's Guide for Windows, Volume I
Installing the NetBackup Client on a MSCS Cluster

If you are backing up the data across the network to a separate NetBackup server, you can
install the NetBackup client on the cluster. In this case, you must install the NetBackup
client on each desired node of the cluster. You set up this configuration in nearly the same
way as standalone clients. However, if you have problems with name resolution when
trying to back up data on the cluster (either local data or shared data), consider setting the
Required Network Interface parameter, for each client, to the fully qualified name of the
node where the NetBackup client is installed.
The NetBackup client is installed on a cluster just as it is in a non-clustered environment.
Refer to the NetBackup Installation Guide for Windows for information on installing the
NetBackup client.
Performing Backups and Restores in a MSCS Cluster

The process of configuring and performing backups and performing restores in a cluster
is similar no matter which clustering solution you are using. Guidelines and instructions
for backups and restores are covered in the chapter “Using NetBackup to Perform
Backups and Restores in a Cluster” on page 83.
This following section covers information on restoring the cluster quorum, which is
specific to a MSCS environment.
Restoring the Cluster Quorum for Windows 2000 Systems

The cluster quorum is backed up as part of System State for each node. To restore the
cluster quorum, other nodes in the cluster must be offline. If you cannot take the other
nodes in the cluster offline before restoring the cluster quorum, you can create the
following registry entry to force the restore of the cluster quorum:
HKEY_LOCAL_MACHINE\Software\VERITAS\NetBackup\CurrentVersion\Config\
Cluster_Database_Force_Restore
Note The actual registry entry above must be on a single line.

If required, create this registry value as data type REG_SZ with a value of YES. When this
value is set, the cluster service is stopped for any nodes that are online.
Restoring the quorum to a node that is running Active Directory or to a node that is
currently a domain controller, requires additional steps not listed here. If Active Directory
is running on the target server or the target server is currently a domain controller, see
“Restoring Cluster Quorum to Windows 2000 Node With Directory Services” on page 12.
▼ To restore the cluster quorum
1. From the NetBackup Backup, Archive, and Restore interface, select the backup image
(or range of images) that contains the backup of the System State for this node of the
cluster. Then, select the node of the tree labeled System_State as the directory to be
restored. For details, see the section on performing restores in the NetBackup User’s
Guide for Windows.
2. If the disk where cluster quorum previously resided has been changed (The disk
could have been replaced with a new one, or the disk configuration could have been
changed so that the cluster quorum now resides on a different disk.), you may have to
set the registry entry described above to force the restore to continue. This allows the
drive letter of the disk that the cluster quorum was on to remain the same, even if the
configuration has changed and the disk signatures contained in the restore media do
not match the disk signatures contained in the cluster quorum.
3. Continue the restore operation as explained in the section on performing restores in

the NetBackup User’s Guide for Windows.
4. When the restore operation is complete, either reboot the cluster node or use the
Microsoft Cluster Administrator to restart the cluster service on any nodes where it
was stopped, whichever is appropriate.
Restoring Cluster Quorum to Windows 2000 Node With

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

▼ To restore the cluster quorum to a node running Active Directory or that is currently
a domain controller
1. From the NetBackup Backup, Archive, and Restore interface, select the backup image
(or range of images) that contains the backup of the System State for this node of the
cluster. Then, select the node of the tree labeled System_State as the directory to be
restored. For details, see the section on performing restores in the NetBackup User’s
Guide for Windows.
2. Exclude the cluster quorum from being restored with System State at this time by
expanding the System_State node and deselecting the Cluster_Database node of the
tree.
3. Continue the restore operation by following the steps on performing restores in the
NetBackup User’s Guide for Windows.
4. When the restore operation is complete, reboot the cluster node in safe (repair) mode
(restart the computer and press F8 when prompted to select an operating system) and
then select Directory Services Restore Mode.
5. Start the NetBackup service(s).
6. In the NetBackup Backup, Archive, and Restore interface, expand the System_State
node and select only the Cluster_Database node.
7. If the disk where the cluster quorum previously resided has been changed, you may
have to set the registry entry described above to force the restore to continue. The disk
could have been replaced with a new one, or the disk configuration could have been
changed so that the cluster quorum now resides on a different disk. This allows the
drive letter of the disk that the cluster quorum was on to remain the same, even if the
configuration has changed and the disk signatures contained in the restore media do
not match the disk signatures contained in the cluster quorum.
8. Continue the restore operation by following the steps in the section on performing
restores in the NetBackup User’s Guide for Windows.
9. When the restore has completed, reboot the target node.
10. When the restore operation is complete, use the Microsoft Cluster Administrator to
restart the cluster service on any nodes on which it was stopped.

Preparing for Disaster Recovery of A Cluster
Preparing for Disaster Recovery of A Cluster

If a disaster occurs, the following information is required to successfully recover the
cluster.
General Cluster Information
Cluster name _____________________________________________
Cluster IP address and subnet mask _____________________________________________
Cluster node names _____________________________________________
Node IP addresses _____________________________________________
Local and shared drive letters and partition _____________________________________________

scheme
_____________________________________________
Cluster Groups
Group name _____________________________________________
Preferred nodes _____________________________________________
Failover/failback policies _____________________________________________
_____________________________________________
Cluster Resources
Resource name _____________________________________________
Resource type _____________________________________________
Group membership _____________________________________________
Possible owners _____________________________________________
Resource dependencies _____________________________________________
Restart and Looks Alive/Is Alive properties _____________________________________________
Resource-related parameters _____________________________________________

Disaster Recovery of A MSCS Cluster

Several scenarios are discussed in this section:
◆ To recover the entire cluster, see the next topic, “Recovering the Entire Cluster”.
◆ To recover the shared disk that the NetBackup application resides on, see “Recovering
NetBackup Data on a Shared Disk” on page 16.
Recovering the Entire Cluster

▼ To recover the nodes to their pre-disaster state
1. On the first node you want to recover, reinstall Windows, including the last service
pack applied before the failure.
2. Install any other drivers or applications in order to get the node operational.
Note After booting the nodes in a cluster, ensure that the drive letters match the original
cluster configuration. If the original configuration does not match, you can use the
Disk Administrator, to some extent, to control the hard drive numbering scheme
that Windows devises.
3. On all remaining nodes you need to recover, reinstall Windows, including the last
service pack applied before the failure. Also, see the previous caution.
4. Reinstall the cluster services and bring the cluster online.
5. Reinstall the same NetBackup software on the cluster that was installed before the
failure. For details, see the earlier sections that describe installing a NetBackup client
or media server on a cluster, whichever applies.
6. If a NetBackup failover server was installed on the cluster or separate NetBackup

media servers were installed on the nodes of the cluster as described earlier, use the
NetBackup bprecover command to restore the NetBackup catalog information
before continuing. See the NetBackup Troubleshooting Guide for UNIX and Windows for
more information on recovering the NetBackup catalog database.
7. Restore the data files through the virtual server.
8. If you must restore a database to the shared drives, see the system administrator’s
guide for your database agent to continue the restore.

Recovering NetBackup Data on a Shared Disk

If a NetBackup failover server was installed on the cluster as described earlier in this
appendix and you must recover the shared disk that was used for the NetBackup failover
server, use the NetBackup bprecover command to restore the NetBackup catalog
information on the shared disk. See the NetBackup Troubleshooting Guide for UNIX and
Windows for more information on recovering the NetBackup catalog database.

NetBackup in HP Tru64 UNIX TruCluster 3

This chapter provides information on how to install, configure and use NetBackup Server
in a TruCluster environment. For information about NetBackup, refer to the NetBackup
System Administrator's Guide for UNIX, Volume I. For information about TruCluster, refer to
the TruCluster User's Guide.
17
The CAA Facility
The CAA Facility

Since all nodes in a TruCluster have access to all installed software within the cluster, there
needs to be a way to differentiate the single node that is to run the server software. In a
typical NetBackup installation, server software is started and stopped by a script. In a
TruCluster, this would be executed on all machines in the cluster. This results in a number
of processes running on each machine. Where these machines are configured as servers
this is problematic. The node on which NetBackup will run can be controlled with HP’s
CAA (Cluster Application Availability) facility.
The CAA facility provides for monitoring and switching applications and resource control
between nodes within a cluster. Applications are assigned names and registered with
CAA, which controls upon which nodes the application can be active. A script needs to be
provided which handles starting, stopping, and monitoring applications. A pointer to
start and stop scripts needs to be added, as well as the daemon to be monitored to
determine if the application is active. NetBackup is then started by CAA, which keeps
track of which node it is active on.
CAA provides two controls:
caa_start brings the NetBackup daemons online
caa_stop takes the NetBackup daemons offline
Installing a NetBackup Server on a TruCluster

This section describes how to install NetBackup as a non-failover or failover server on a
TruCluster.
Installation Notes
◆ These instructions assume that this is a new installation of a NetBackup server.
◆ Converting an existing non-failover NetBackup server to a highly available failover

Installing a NetBackup Server on a TruCluster
Prerequisites
❏ Verify all hardware (used for nodes) is supported by TruCluster and NetBackup. For
a list of supported storage devices, see the NetBackup Release Notes for UNIX and
Windows and the TruCluster documentation.
❏ Verify that TruCluster 5.1a or 5.1b is correctly installed and configured.
❏ (Failover server only) Set up a virtual name for NetBackup in NIS, DNS or
/etc/hosts. This hostname will be used as a logical hostname during the
NetBackup installation and configuration of the cluster. It will not be assigned to any
physical node, but will be attached to the NetBackup application resource, allowing
NetBackup to failover to the appropriate node during the failover process.
❏ (Failover server only) Make sure that each node in the cluster, on which you wish to
install NetBackup, is rsh equivalent. As the root user you need to be able to perform
a remote login to each node without entering a password. This is only necessary for
installation and configuration of the NetBackup server and any NetBackup agents
and options. Once installation and configuration is complete this is no longer
required.
license key.
Installation Instructions
The NetBackup server software (master or media) can be installed on any node in the
cluster. Follow the instructions for installing NetBackup Server software as described in
the NetBackup Installation Guide for UNIX.
For a non-failover NetBackup server, specify the specific node name as the server name
during installation. For a failover NetBackup server, specify the cluster alias as the server
name during installation.
Note When the NetBackup is installed in a cluster as a failover server, the NetBackup
client will only run on the node that is also running the NetBackup server.
Chapter 3, NetBackup in HP Tru64 UNIX TruCluster 19

Configuring TruCluster to Use a Failover NetBackup Server

▼ To configure for a failover server
1. From the /usr/openv/netbackup/bin/cluster/ directory, run the

cluster_config configuration utility.
2. For the TruCluster NetBackup service/profile name, indicate a new name for this
configuration.
3. Specify the cluster alias to be used by NetBackup.

If this is a new cluster alias, indicate the cluster alias IP address to be used by
NetBackup. This should already be configured in the /etc/hosts file, or in DNS, or
NIS. Also provide the cluster alias IP subnet to be used by CAA. This is the network
subnet for the cluster alias IP address. For instance, an IP address of 10.80.136.119 on a
network with a netmask of 255.255.248.0 would have a subnet of 10.80.136.0.
4. Provide a list of the cluster members on which NetBackup may run. Separate member
names with a space and list them in the preferred order.
5. On the summary screen, review the information you provided.
Note If you chose to use a pre-existing cluster alias the IP and subnet fields will be blank.
◆ If the information is incorrect, choose No, and the configuration script will start
back at the beginning.
◆ If the information is correct, choose Yes.
The script will:
◆ Create and register a CAA profile for the Netbackup application.
◆ Create and register a cluster alias (if a new alias was specified).
◆ Remove the S77NetBackup and K77NetBackup scripts from
/sbin/rc0.d and /sbin/rc2.d directories.
◆ Update the bp.conf and vm.conf files.
◆ Start the NetBackup server.
6. At this point the application can be started and stopped with the following
commands:
caa_start profile_name
caa_stop profile_name

Note If you have installed a NetBackup failover media server then you must manually
start Media Manager daemons. Start the daemons with the caa_start command.
The caa commands must be used in place of the standard NetBackup start and stop
script which does not track which node the software is running on and will allow
multiple instances of NetBackup within the cluster.
For example, with caa registered profile named “netbackup” for NetBackup server,
the application can be started and stopped with the following commands:
caa_start netbackup
caa_stop netbackup
7. Continue with the configuration of NetBackup.

8. Install any NetBackup agents and options.
a. Freeze NetBackup by running the following command:

b. Install the agents and options as you would in a non-clustered environment.

Refer to the system administrator’s guides for those agents or options.
a. Unfreeze NetBackup by running the following command:

By default, robotic daemons and NetBackup options (such as NetBackup Advanced
Reporter) will not cause NetBackup to failover if they fail. Robot daemons and
NetBackup options can be configured to failover NetBackup if a daemon or the option
fails. For more information, see “Configuring Robotic Daemons for Monitoring (VCS
for UNIX, TruCluster, or Sun Cluster)” on page 79 and “Configuring Add-ons for
Monitoring in a VCS for UNIX, TruCluster, or Sun Cluster Environment” on page 80.
failover properly in the cluster. Refer to “Verifying NetBackup Configuration” on
page 79.

Upgrading a NetBackup Failover Server on a TruCluster
Tips
◆ By default, NetBackup will attempt to complete a backup job 2 times (within 12
hours) before allowing the job to fail. It is possible that scheduler attempts may be
exhausted before the failover of the NetBackup Media Server can be completed. If this
happens, increase the Scheduled Backup Attempts setting to 5 or 6. This problem can
also be avoided by setting the Wakeup Interval setting to a lower value.
◆ The Wakeup Interval setting should be set lower to increase the likelihood that
NetBackup will be able to initiate all scheduled backups.
◆ If you experience caa_stop failures for NetBackup, you may want to consider
increasing the script timeout value. The default is 180 seconds but sometimes this is
not enough for a heavily loaded machine to shut down all of the robotic daemons. The
same is true of machines with several tape drives attached in a SAN configuration. To
see if this solution is correct for you, use “vmps” to check which daemons are running
immediately after the error. If it is a robotic daemon, increasing the timeout will most
likely fix your problem. The script timeout value is part of TruCluster profile
property; use the caa_profile TruCluster command to change this value.

Follow these instructions when applying patches to a NetBackup 5.0 failover server. See
the NetBackup Release Notes for UNIX and Windows for the latest information on applying a
specific patch.
▼ To apply a patch to a NetBackup 5.0 failover server
1. Login to the node NetBackup is running on.
2. Stop NetBackup server using the command caa_stop profile name.
3. Complete the patch install.
4. Start NetBackup using the command caa_start profile name.
5. Verify that NetBackup can failover properly in the cluster. Refer to “Verifying
NetBackup Configuration” on page 79.

Upgrading an Existing 4.5FPx or 4.5MP3 (or later) Failover

Media Server to 5.0
This section describes how to upgrade from a 4.5FPx or 4.5MP3 (or later) failover media
server to a 5.0 media server.
Caution A NetBackup failover server must be upgraded according to the instructions

below. If these steps are not followed, NetBackup may not function properly in
the cluster.
▼ To upgrade a failover media server to 5.0
1. Stop the NetBackup media server using the following command.

2. In the bp.conf file, change the REQUIRED_INTERFACE entry to CLUSTER_NAME

entry. This should be defined as the virtual server name.
3. In the vm.conf:
◆ Verify that any MM_SERVER_NAME or CLUSTER_NAME entries are defined as the
virtual server name.
◆ If it exists, change the REQUIRED_INTERFACE entry to CLUSTER_NAME and
define it as the virtual name.
4. Install NetBackup 5.0. Follow the instructions for “Upgrading NetBackup on UNIX
Servers and Clients” as described in the NetBackup Installation Guide for UNIX.
5. When installation is complete run the following command.

6. Upgrade any NetBackup agents and options you have purchased.
a. Freeze NetBackup by running the following command:


b. Upgrade agents and options as you would in a non-clustered environment.

Refer to the system administrator’s guides for those agents or options.
By default, robotic daemons and NetBackup options (such as NetBackup
Advanced Reporter) will not cause NetBackup to failover if they fail. Robot
daemons and NetBackup options can be configured to failover NetBackup if a
daemon or the option fails. For more information, see “Configuring Robotic
Daemons for Monitoring (VCS for UNIX, TruCluster, or Sun Cluster)” on page 79
and “Configuring Add-ons for Monitoring in a VCS for UNIX, TruCluster, or Sun
Cluster Environment” on page 80.
c. Unfreeze NetBackup by running the following command:


Configuring TruCluster to Use a Non-Failover NetBackup Server
Configuring TruCluster to Use a Non-Failover NetBackup

Server
The following procedure describes how to use the CAA facility to start NetBackup and
keep track of the node on which it is active. For more information on this, see “The CAA
Facility” on page 18.
▼ To configure for a non-failover server
1. Move the following:

/usr/openv/netbackup/bin/cluster/trucluster/caa_netbackup
to
/usr/openv/netbackup/bin/cluster/trucluster/caa_netbackup.orig
2. Copy the following:

/var/cluster/caa/template/template.scr
to
/usr/openv/netbackup/bin/cluster/trucluster/caa_netbackup
3. Remove the S77NetBackup and K77NetBackup scripts from rc0.d and rc2.d
directories, since the CAA facility will be used to start and stop NetBackup.
4. In the script, add pointers to the start and stop scripts and to the daemon(s) to be
monitored (to determine if the application is active). The daemon to be monitored for
the media server is vmd. For the master server the daemons to monitor are vmd, bprd
and bpdbm. “netbackup” is the name used for the NetBackup application.
To start NetBackup services the script should call:
/usr/openv/netbackup/bin/goodies/netbackup start
To stop the NetBackup services the script should call:

/usr/openv/netbackup/bin/goodies/bp.kill_all FORCEKILL
5. Once the script is complete, a CAA profile must be made. Run the following
command:
caa_profile -create netbackup -t application -a
/usr/openv/netbackup/bin/cluster/trucluster/caa_netbackup -p restricted -h <name of the host
the software is to run on>
This creates a profile that uses the completed script, names the application
“netbackup,” and restricts the operation of that application to the named node.

Configuring TruCluster to Use a Non-Failover NetBackup Server
6. Assuming NetBackup has been installed, the application needs to be registered. Use
the following command.
caa_register profile_name
7. In the /etc/inetd.conf file, comment out the lines that define the NetBackup
listeners (bpcd, vnetd, vopied, bpjava).
8. Login to the node NetBackup will be running on (the restricted hostname specified in
step 5) and add the following NetBackup listener lines to the
/etc/inetd.conf.local file.
bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd
vnetd stream tcp nowait root /usr/openv/bin/vnetd vnetd
vopied stream tcp nowait root /usr/openv/bin/vopied vopied
bpjava-msvc stream tcp nowait root /usr/openv/netbackup/bin/bpjava-msvc bpjava-msvc -transient
9. At this point the application can be started and stopped with the following
commands:
The caa commands should be used in place of the standard NetBackup start and stop
script which does not track which node the software is running on and will allow
multiple instances of NetBackup within the cluster.
For example, with caa registered profile named “netbackup” for NetBackup server,
the application can be started and stopped with the following commands:
caa_start netbackup
caa_stop netbackup
10. Continue with the configuration of NetBackup. Refer to the NetBackup Installation
Guide for UNIX for information on configuring the NetBackup server software.
11. Install any NetBackup agents and options you have purchased. Install agents and
options as you would in a non-clustered environment. Refer to the NetBackup guides
for those agents or options.

Upgrading a NetBackup Non-Failover Server on a TruCluster
Upgrading a NetBackup Non-Failover Server on a

TruCluster
Follow these instructions when applying patches to a non-failover server.
▼ To apply a patch to a NetBackup non-failover server
1. Login to the node NetBackup is running on (restricted hostname specified when

creating the profile).
2. Stop NetBackup server using the command caa_stop profile name.
3. Install NetBackup 5.0.
4. In the /etc/inetd.conf file, make sure the NetBackup listeners (bpcd, vnetd,
vopied, bpjava) are commented out.
5. To turn off the NetBackup listeners, refresh the inetd daemon on all cluster nodes.
6. For each node on which NetBackup is installed, verify that the NetBackup listeners
(bpcd, vnetd, vopied, bpjava) are included in the /etc/inetd.conf.local
file.
7. Start NetBackup using the command caa_start profile name.
Upgrading an Existing Non-Failover Server to 5.0

Refer the instructions for upgrading NetBackup on UNIX servers and clients as described
in the NetBackup Installation Guide for UNIX.

Installing Only the NetBackup Client on a TruCluster
Installing Only the NetBackup Client on a TruCluster

The client software can be installed on any node in the cluster (since the software is run
from the shared /usr file system). Specify the name of one of the nodes in the cluster as
the client name. This will limit the execution of the client to that node.
Performing Backups and Restores in a TruCluster


NetBackup in VERITAS Cluster Server on

Windows NT 4
This chapter provides information on how to install and configure NetBackup as a
clustered application in a VERITAS Cluster Server, version 1.2.1, for Windows NT 4.0
environment. For information on using NetBackup with VCS 2.0 on Windows 2000, refer
to the “NetBackup in VERITAS Cluster Server on Windows 2000” on page 43 and the
VERITAS Cluster Server Enterprise Agent 2.2 for NetBackup Installation and Configuration
Guide.
VCS is a high-availability solution for cluster configurations. VCS enables you to monitor
systems and application services, and to restart services on a different system when
hardware or software fails. For information about VCS, refer to the VERITAS Cluster Server
User's Guide.
29
This section contains information to the requirements that must be met prior to installing
and configuring the VCS Enterprise Agent for NetBackup and the NetBackup server in a
VCS environment.
❏ Verify that your hardware is supported by VCS 1.2.1 and NetBackup 5.0. For a list of
supported storage devices, see the VERITAS Cluster Server System Administrator’s
Guide and the NetBackup Release Notes for UNIX and Windows.
❏ Verify that you have correctly installed and configured VCS 1.2.1. NetBackup can be
installed on as many nodes as VCS 1.2.1 supports. Follow the steps in the VERITAS
Cluster Server Installation Guide.
❏ Verify that VCS Cluster Manager is installed. Refer to the VERITAS Cluster Server
Installation Guide for more information.
❏ Verify that you have an IP address and host name to be assigned to the NetBackup
resource in VCS.
❏ Verify that you have the installation media for the VCS Enterprise Agent for
NetBackup, version 1.2.1.
license key.
Limitations
NetBackup add-on options and database agents are not supported in a VCS for Windows
NT environment.

Installing the VCS Enterprise Agent for NetBackup
Installing the VCS Enterprise Agent for NetBackup

This section contains instructions for installing the VCS Enterprise Agent for NetBackup
version 1.2.1.
▼ To install the VCS Enterprise Agent for NetBackup
1. Insert the VCS Enterprise Agent for NetBackup CD.
2. Click Install NetBackup Agent.
3. Click Next.
4. From the Available Nodes text box, select the systems on which to install the agent.
5. Click Add. (Click Add All to install the agent on each system in the cluster.)
6. Click Next.
7. Review the current settings and click Next to proceed or Back to correct an entry.
8. Click Finish to complete the installation.
9. Click Exit to close the CD Browser.
10. After the installation is complete, continue with the next section, “Installing
NetBackup Server.”
Chapter 4, NetBackup in VERITAS Cluster Server on Windows NT 31

Installing NetBackup Server
Installation Notes
server.
◆ After installing NetBackup 5.0, the CLUSTER_NAME and MM_SHARED_MISC registry
entries must be added as described in “Configuring NetBackup for the VCS
Enterprise Agent 1.2.1” on page 38
Installation Instructions
To install a NetBackup Server in on a VERITAS Cluster Server, follow these steps for each
of the nodes in the NetBackup service group.
▼ To install a NetBackup Server in a VCS Cluster
Note When prompted for the name of the server, use the server node name.
1. Log in as Administrator on the server where you will be installing NetBackup.
2. Insert the NetBackup CD in the drive.

◆ On Windows systems with AutoPlay enabled for CD-ROM drives, the VERITAS
NetBackup installation browser starts automatically.
◆ On Windows systems that have AutoPlay disabled, run Launch.exe in the
top-level directory on the CD.
3. Click NetBackup Installation.
4. Click Install Server Software.
5. When prompted to choose the Installation Type, choose Install to this computer only.
6. When prompted to choose the Setup Type, choose Custom.

7. In the NetBackup Services screen, clear the Start NetBackup Server Services After
Install box.
Note Do not launch the NetBackup Administration Console, start the NetBackup
services, configure any devices or storage units, or run the Getting Started wizard at
this time.
8. Once the NetBackup installation is complete for the node, add the path of the
NetBackup executables to the Path variable of the “system” environment variables.
For example, if NetBackup is installed on C:\Program
Files\VERITAS\NetBackup\bin, add this path to the Path variable.
9. Continue installing NetBackup on each node in the NetBackup service group.
10. After the installation is complete, continue with the next section, “Configuring the
VCS Enterprise Agent 1.2.1 for NetBackup.”

Configuring the VCS Enterprise Agent 1.2.1 for NetBackup

The VCS Enterprise Agent 1.2.1 for NetBackup needs to be configured as follows in order
to achieve a highly available NetBackup application. You must be logged in as an
administrator in order to perform the following tasks.
▼ To configure the VCS Enterprise Agent for NetBackup
1. Obtain the necessary Shared Disk information (used for step 17).
a. A shared disk used for NetBackup must use NTFS format.
b. Make sure the disk is not assigned a drive letter on any of the nodes on which
NetBackup was installed (use Disk Administrator, on each node).
c. Retrieve drive information by using the GetDrive utility.

The utility is located in the path VCS_HOME\bin. By default, VCS_HOME is
C:\Program Files\VERITAS\Cluster Server\.
From the command prompt, enter:
GetDrive
or
GetDrive -details
The system retrieves (disk number, signature) information about the disks and
stores it in a file called DriveInfo.txt.
2. Obtain the necessary Network information (used for step 17).

From the command prompt, enter:
ipconfig /all
Note the adapter names used for the public resource.
3. Start the Cluster Manager and login.
4. Start the Cluster Configuration Wizard.
5. Click Yes when prompted to begin the Cluster Configuration wizard.

If you choose not to begin the wizard, you can open it from the Cluster Explorer, by
choosing to Tools > ConfigurationWizard.
6. Click Next.

7. Enter the service group name (e.g., NetBackupSG).
8. From the Available Systems list, select the systems to which the NetBackup service
can failover.
9. Click the right arrow to include the selected systems in the service group.
The systems added to the service group are listed in Systems for Service Group list.
Note Do not make a system a part of the AutoStartList. Make sure the Start-up box in the
Systems for Service Group list is not selected.
10. Assign priorities to the cluster systems.
11. Click Next.
12. In the “Would you like the service group to be based on a template?” window, click
Next.
13. Select the NetBackupGroup template from the list of available templates, then click
Next.
14. If any service group or resource names conflict with existing names, the wizard
prompts you with alternate names. You can use the suggested alternates, or enter
different ones. Click Next.
15. The wizard informs you that it is ready to create the service group based on the
selected template. Click Next.
The wizard shows a progress bar indicating service group creation.
16. In the Service Group successfully created window, click Next.
17. Configure the following resources.
Resource Attribute Example Setting
DiskRes Disks 0
Signatures 2822641176
IP AdapterName N1001
Address 10.80.101.61

Resource Attribute Example Setting
SubNetMask 255.255.248.0
Lanman VirtualName herovcs
Mount DriveLetter F
Note The drive letter assigned must not be in-use by any
disk on any node in the cluster
PartitionNo 1 - default
Signature 2822641176
NIC AdapterName N1001
NetBackup ServerName herovcs
ServerType For a NetBackup Master server: “master, volmgr”

For a NetBackup Media server: “media, volmgr”
For a NetBackup server that is both Master and Media
server: “master, media, volmgr”
18. When you have completed configuring the resources, click Finish.
19. From the left pane of the window, select the newly created service group.
20. Right-click the service group and select Enable Resources.

This enables all resources in the service group.
21. Right-click on the service group and select Enable, and then the system where you
want to enable the service group.
22. Save your configuration. (Choose File > Close Configuration.)
23. On the primary node, bring the NetBkup_LanMan and NetBkup_Mount resources
online. This is where you will begin your NetBackup configuration.
Note This will bring all resources online, except NetBackup.

24. Freeze the service group. (Right-click on the service group and select Freeze >
Temporary.)
25. After the installation is complete, continue with the next section, “Configuring
NetBackup for the VCS Enterprise Agent 1.2.1.”

Configuring NetBackup for the VCS Enterprise Agent 1.2.1

This section provides instructions for configuring NetBackup to use the VCS Enterprise
Agent once you have installed and configured the agent.
▼ To configure NetBackup for the VCS Enterprise Agent 1.2.1
1. Make sure that the NetBackup service group is in Temporary Freeze state (step 24,
previous procedure).
2. From the primary node, run the Setup wizard by executing the nbuvcs.exe
program located in the VCS_HOME\bin\NetBackup directory. By default,
VCS_HOME is C:\Program Files\VERITAS\Cluster Server\
This wizard guides you through the rest of the installation.
3. From the Introduction screen, click Next.
4. Select the available nodes containing NetBackup and add them to the Selected Nodes
list. Click Next.
5. Enter the virtual server name and the full path to a directory on the shared disk and
click Next.
Note This server name should match the name entered for the VirtualName of the
LanMan resource and the ServerName attribute of the NetBackup resource.
Note This path name should match the drive letter specified in the Mount resource.
6. Review the attributes for the NetBackup failover server on the NetBackup VCS Setup
Summary screen. Click Next.
7. After the wizard is complete, click Finish.

◆ When configuring devices, begin with configuration on the active node. Then
unfreeze the NetBackup service group, switch the group to another node, freeze
the group again and configure devices on that next node. Refer to the next section,
“Configuring Devices in a VCS for NT Cluster” for instructions on using the VCS
interface to switch the NetBackup resource group to other nodes.
◆ See the chapter, “Configuring NetBackup” on page 73 for guidelines on
configuring NetBackup in a cluster.

9. When configuration is complete, unfreeze the service group by right-clicking on the

service group and selecting Unfreeze > Temporary.
10. Change the AutoStartList attribute to allow the service group to start automatically.
a. Select a group from the left pane window and then select the Attributes tab in the
right pane to display the attributes.
b. Select the AutoStartList attribute.
c. Click the browse button (...) in the Edit column.
d. From the Edit Attribute window, add an entry for the primary node.
e. Click OK.
11. When performing an upgrade of NetBackup 4.5 to NetBackup 5.0, edit the Windows
registry as follows:
a. Add the Cluster_Name value:

HKLM\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config\
Cluster_Name
with the string set to the NetBackup virtual server name (this value is the same as
the value of REQUIRED_INTERFACE).
b. Add the MM_SHARED_MISC value:

HKLM\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Paths\
MM_SHARED_MISC
with the string set to the shared drive letter:shared install
path\Volmgr\misc
c. Add the ROBOTIC_DB_PATH value:

ROBOTIC_DB_PATH
path\Volmgr\misc\robotic_db.

d. Remove the REQUIRED_INTERFACE value:

REQUIRED_INTERFACE
12. Verify that NetBackup can fail over properly in the cluster. Refer to “Verifying
Configuring Devices in a VCS for NT Cluster

The same basic procedure is used to add new devices to the cluster. First, configure them
on one node, then move the NetBackup service group to the other node and configure the
devices for that node.
Note Devices must be configured on each node in the cluster.
▼ To configure devices in a VCS for NT cluster
1. Configure the devices on the active node.
2. Unfreeze the service group. (Right-click on the service group and select Unfreeze >
Temporary.)
3. Using the Switch command in the VERITAS Cluster Manager, move control of the
NetBackup group to the another node in the group.
4. Freeze the service group. (Right-click on the service group and select Freeze >
Temporary.)
5. Repeat step 1 through step 4 for each node on which NetBackup was installed.
Note The Media and Device Management utility shows the devices that are configured
for the node that controls the NetBackup group. By using the Switch command in
the VERITAS Cluster Manager to move control of the NetBackup group from one
node to the other, you can examine the device configuration for each node.

Upgrading NetBackup Server
Upgrading NetBackup Server

◆ When applying patches, be sure to first apply the patch on the inactive nodes in the
cluster. Then failover (switch) the NetBackup group to the newly patched inactive
node (thereby making it active) and apply patches to the remaining nodes.
◆ To upgrade a NetBackup failover server to 5.0, first freeze the NetBackup service
group. Then follow the installation instructions as described in “Installing NetBackup
Server” on page 32. When the installation is complete, unfreeze the NetBackup service
group.
Performing Backups and Restores in a VCS Cluster




Windows 2000 5
This chapter provides information on how to install and configure NetBackup as a
clustered application in a VERITAS Cluster Server, version 2.0, for Windows 2000
environment. For additional information on using NetBackup with VCS 2.0 on Windows
2000, please refer to the VERITAS Cluster Server Enterprise Agent 2.2 for NetBackup
Installation and Configuration Guide.
VCS is a high-availability solution for cluster configurations. VCS enables you to monitor
systems and application services, and to restart services on a different system when
hardware or software fails. For information about VCS, refer to the VERITAS Cluster Server
User's Guide.
43
This section contains information to the requirements that must be met prior to installing
and configuring the VCS Enterprise Agent for NetBackup and the NetBackup server in a
VCS environment.
❏ Verify that your hardware is supported by VCS 2.0 and NetBackup 5.0. For a list of
supported storage devices, see the VERITAS Cluster Server System Administrator’s
Guide and the NetBackup Release Notes for UNIX and Windows.
❏ Verify that you have correctly installed and configured VCS 2.0. NetBackup can be
installed on as many nodes as VCS 2.0 supports. Follow the steps in the VERITAS
Cluster Server Installation Guide.
❏ Verify that VCS Cluster Manager is installed. Refer to the VERITAS Cluster Server
Installation Guide for more information.
❏ Verify that you have an IP address and host name to be assigned to the NetBackup
resource in VCS.
❏ Verify that you have the installation media for the VCS Enterprise Agent for
NetBackup, version 2.0 or later.
license key.
Limitations
NetBackup options and database agents are not supported in a VCS 2.0 environment.

Installation and Configuration

Refer to the VERITAS Cluster Server Enterprise Agent 2.2 for NetBackup Installation and
Configuration Guide for details on installing and configuring NetBackup to work with the
VCS Enterprise Agent.
If you chose not to install the latest VCS Enterprise Agent for NetBackup (version 2.2),
continue with the instructions in the next section, “Post-Installation Configuration.”
Perform these steps before configuring the NetBackup server.
Post-Installation Configuration
If you did not install the VCS Enterprise Agent 2.2 for NetBackup when performing an
upgrade of NetBackup 4.5 to NetBackup 5.0, you must edit the registry as follows.
▼ To configure NetBackup in the Windows registry
1. Open the Windows registry.
2. Add the Cluster_Name value:

HKLM\SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config\Cluster_Name
with the string set to the NetBackup virtual server name (this value is the same as the
value of REQUIRED_INTERFACE).
3. Add the MM_SHARED_MISC value:

MM_SHARED_MISC
path\Volmgr\misc
4. Add the ROBOTIC_DB_PATH value:

ROBOTIC_DB_PATH
path\Volmgr\misc\robotic_db.
5. Remove the REQUIRED_INTERFACE value:

REQUIRED_INTERFACE
Chapter 5, NetBackup in VERITAS Cluster Server on Windows 2000 45

Post-Installation Configuration
6. Close the Windows registry.


UNIX 6
This chapter describes the steps to install and configure a NetBackup Server in a VCS for
UNIX environment. VCS is a high-availability solution for cluster configurations. VCS
enables you to monitor systems and application services, and to restart services on a
different system when hardware or software fails. For information about VCS, refer to the
VERITAS Cluster Server User's Guide.
47
About the VCS Enterprise Agent for NetBackup
About the VCS Enterprise Agent for NetBackup

The VCS Enterprise Agent for NetBackup monitors specific NetBackup resources,
determines the status of these resources, and starts or stops NetBackup according to
external events. The agent includes VCS type declarations and agent executables, and is
represented by the NetBackup resource type. When the agent detects an application
failure, the NetBackup service group is failed over to another system in the cluster.
Specific agent operations include:
Online Executes the following command:

/usr/openv/netbackup/bin/goodies/netbackup start
Offline Executes the following command:

Monitor Scans the process table for vmd, bprd, and bpdbm, etc. The specific
processes to be monitored can be configured using the cluster
configuration utility. The agent provides two levels of application
monitoring: basic and detailed (in-depth). See “Additional Monitoring” on
page 48 for more information.
Clean Stops all NetBackup daemons after detecting an unexpected offline

operation, or an ineffective online operation.
Detecting an Application Failure

The agent detects an application failure if the monitor process cannot locate the specific
monitored processes (such as vmd, bprd, bpdbm.) in the process table.
Additional Monitoring
Additional monitoring capabilities are available for robots and add-on products. Refer to
the “Configuring Robotic Daemons for Monitoring (VCS for UNIX, TruCluster, or Sun
Cluster)” on page 79 and “Configuring Add-ons for Monitoring” on page 80.

❏ Verify that your hardware is supported by both VCS and NetBackup. For a list of
supported storage devices, see the NetBackup Release Notes for UNIX and Windows and
the VCS documentation.
❏ Verify that VCS 2.1 or later is correctly installed and configured on Solaris, HP-UX,
AIX, or Linux. Follow the steps in the VERITAS Cluster Server Installation Guide.
❏ The shared disk must be configured and accessible to all cluster nodes on which
NetBackup will be installed.
❏ Set up a virtual name for NetBackup in NIS, DNS or /etc/hosts. This hostname
will be used as a logical hostname during the NetBackup installation and
configuration of the cluster. It will not be assigned to any physical node, but will be
attached to the NetBackup application resource, allowing NetBackup to failover to the
appropriate node during the failover process.
❏ Make sure that each node in the cluster, on which you wish to install NetBackup, is
rsh equivalent (On HP the command is remsh). As the root user you need to be able
to perform a remote login to each node in the cluster without entering a password.
This is only necessary for installation and configuration of the NetBackup server and
any NetBackup agents and options. Once installation and configuration is complete
this is no longer required.
license key.
Chapter 6, NetBackup in VERITAS Cluster Server on UNIX 49

Pre-Installation Checklist for a NetBackup Failover Server Installation
Pre-Installation Checklist for a NetBackup Failover Server

Installation
Note The configuration utility will treat all attribute values globally.
Virtual Name for NetBackup: __________________________________
IP Address: __________________________________
Subnet mask __________________________________
Network Device Name (NIC) __________________________________
Nodes on which NetBackup Server is installed
Node Name IP addresses
__________________________________ __________________________________
__________________________________ __________________________________
__________________________________ __________________________________
__________________________________ __________________________________

For VCS Solaris and Linux
Scenario 1 - Using VxVM
Disk Group Resource:
DiskGroup: __________________________ (e.g. nbudg)
StartVolumes: ________________________ (0 or 1)
StopVolumes: ________________________ (0 or 1)
Volume Resource: (optional)
Volume: _____________________________ (e.g. nbuvol)
Mount Resource
MountPoint: _________________________ (e.g. /opt/VRTSnbu)
BlockDevice: _________________________ (e.g. /dev/vx/dsk/nbuvol)
FS Type: _____________________________ (vxfs is required)
Mount Option: _______________________ (optional)
Fsck Option: _________________________ (if you add other options, -y is also

required)

Scenario 2- Disk Only, No Volume Manager
Mount Resource
MountPoint: _____________________________ (e.g. /opt/VRTSnbu)
BlockDevice:_____________________________ (e.g. /dev/dsk/c1t1dos3)
FS Type:_________________________________ (vxfs is required)
Mount Option: ___________________________ (optional)
Fsck Option: _____________________________ (if you add other options, -y is

also required)

For VCS AIX
StartVolumes: ________________________ (0 or 1)
StopVolumes: ________________________ (0 or 1)
Volume Resource:
Volume: _____________________________ (e.g. nbuvol)
Mount Resource
BlockDevice: _________________________ (e.g. /dev/vx/dsk/nbuvol)
FS Type: _____________________________ (vxfs is required)
Fsck Option: _________________________ (if you add other options, -y is

also required)

Scenario 2 - Using AIX LVMVG
LVMVG Resource:
VolumeGroup:___________________________ (e.g. nbuvg)
MajorNumber: __________________________ (e.g. 58)
Disks: __________________________________ (e.g. hdisk1, hdisk2)
ImportvgOpt: ___________________________ (optional)
VaryonvgOpt: ___________________________ (optional)
SyncODM: ______________________________ (optional)
Mount Resource:
MountPoint:_____________________________ (e.g. /opt/VRTSnbu)
BlockDevice: ____________________________ (e.g. /dev/nbudev)
FS Type: ________________________________ (e.g. jfs2)
Mount Option: __________________________ (optional)
Fsck Option:_____________________________ (if you add other options, -y is

also required)
Scenario 3 - Disk Only, No Volume Manager
Mount Resource:
MountPoint:_____________________________ (e.g. /opt/VRTSnbu)
BlockDevice: ____________________________ (e.g. /dev/dsk/c1t1dos3)
FS Type: ________________________________ (e.g. jfs2)
Mount Option: __________________________ (optional)
Fsck Option:_____________________________ (if you add other options, -y is

also required)

For VCS HP-UX
StartVolumes: _______________________ (0 or 1)
StopVolumes: _______________________ (0 or 1)
Volume Resource:
Volume: _____________________________ (e.g. nbuvol)
Mount Resource:
BlockDevice:_________________________ (e.g. /dev/vx/dsk/nbuvol)
FS Type:_____________________________ (vxfs is required)
Fsck Option: _________________________ (if you add other options, -y is

also required)
Scenario 2 - Using Logical Volume Manager
LVMVolume Group Resource:
Volume Group:_______________________ (e.g. vg0a)
LVMLogical Volume Resource:
Volume Group:_______________________ (e.g. vg0a)
Logical Group: _______________________ (e.g. lvol1)

Scenario 3 - Disk Only, No Volume Manager
Mount Resource:
MountPoint: _____________________________ (e.g. /opt/VRTSnbu)
BlockDevice:_____________________________ (e.g. /dev/dsk/c1t1dos3)
FS Type:_________________________________ hfs
Mount Option: ___________________________ (optional)
Fsck Option: _____________________________ (if you add other options, -y is

also required)

Installing and Configuring a Failover NetBackup Server
Installing and Configuring a Failover NetBackup Server

This section describes how to install and configure a new NetBackup failover server. If
you are upgrading from 4.5 FPx or 4.5MPx to 5.0, refer to “Upgrading a NetBackup
Failover Server from 4.5FPx or 4.5 MPx to 5.0” on page 60.
Installation Notes
server.
◆ Do not install older versions of the VCS for UNIX agent. Use the version of the agent
provided with NetBackup 5.0. This agent is installed along with the NetBackup 5.0
Server software.

▼ To install and configure a NetBackup failover server
1. Fill out the appropriate sections, based on your environment, of the checklist in the
section “Pre-Installation Checklist for a NetBackup Failover Server Installation” on
page 50.
2. Make sure the shared disk is not mounted on any node in the cluster.
3. Follow the instructions for installation and initial configuration in the NetBackup
Installation Guide for UNIX. You must install on each node that you want NetBackup to
run on.
The virtual name should be used for the server name during the install procedure.
4. From the primary node, run the cluster_config utility located in

/usr/openv/netbackup/bin/cluster directory.
5. Answer questions based on the information gathered in step 1.

Installing or Upgrading NetBackup Agents and Options
start Media Manager daemons. Start the daemons with the hagrp -online
command.

7. Install any NetBackup agents or options you have purchased. Refer to the next
section, “Installing or Upgrading NetBackup Agents and Options.”
failover properly in the cluster. Refer to “Verifying NetBackup Configuration” on
page 79.

NetBackup agents and options need to be installed on all cluster nodes where the
NetBackup Server is installed. The NetBackup group must be frozen before any agents or
options can be installed.
Reporter) will not cause NetBackup to failover if they fail. Robot daemons and NetBackup
options can be configured to failover NetBackup if a daemon or the option fails. For more
information, see “Configuring Robotic Daemons for Monitoring (VCS for UNIX,
TruCluster, or Sun Cluster)” on page 79 and “Configuring Add-ons for Monitoring in a
VCS for UNIX, TruCluster, or Sun Cluster Environment” on page 80.
▼ To install or upgrade a NetBackup agent or option in a cluster
1. Freeze the NetBackup group.
2. On each inactive node in the cluster on which NetBackup is installed, install the agent
or option. See the appropriate NetBackup documentation for the agent or option for
installation and configuration instructions.

3. On the active node, install the agent or option.
4. Unfreeze the NetBackup group.

Upgrading a NetBackup Failover Server from 4.5FPx or 4.5 MPx to 5.0
Upgrading a NetBackup Failover Server from 4.5FPx or 4.5

MPx to 5.0
The process of upgrading a NetBackup failover server from 4.5FPx or 4.5MPx to 5.0
includes upgrading the active node, removing NetBackup from the cluster, removing
NetBackup from the inactive nodes, and, finally, installing NetBackup on the inactive
nodes.
Note It is highly recommended that you use the latest VCS for UNIX agent that is
installed with NetBackup 5.0. Older versions of the agent are not supported. The
cluster_config script is also not supported with earlier versions of the VCS for
UNIX agent.

the cluster.
▼ To upgrade a NetBackup failover server
1. Edit the bp.conf and vm.conf files.
a. If a REQUIRED_INTERFACE entry exists, replace it with a CLUSTER_NAME entry.

Otherwise add a new CLUSTER_NAME entry. This entry should be defined as the
virtual server name.
b. For a master server, ensure that the first SERVER entry matches the
CLUSTER_NAME entry.
2. Freeze the NetBackup group.
3. On the active node, install the NetBackup Server software. Follow the instructions for
“Upgrading NetBackup on UNIX Servers and Clients” as described in the NetBackup
Installation Guide for UNIX.
4. Unfreeze the NetBackup group.
5. Bring the NetBackup group offline. This will unmount the shared disk.
6. Put the cluster configuration into writable mode:

haconf -makerw

7. Remove the old NetBackup group, agent, and type from the cluster.
a. Remove each resource in the NetBackup group. Use the following command:
hares -delete <name of resource>
b. Remove the NetBackup group. Use the following command:

hagrp -delete <name of NetBackup group>
c. On each node in the cluster, stop the NetBackup agent:

haagent -stop NetBackup -sys hostname
d. Remove the NetBackup resource type.

hatype -delete NetBackup
e. Remove the agent:

◆ On Solaris, run pkgrm VRTSvcsnb
◆ On AIX, run installp -U VRTSvcsnb.rte
◆ On HP, run swremove VRTSvcsnb
◆ On Linux, run rpm -ev VRTSvcsnb
Then, run the following command:

rm -rf /opt/VRTSvcs/bin/NetBackup
8. Dump the cluster configuration and return to read-only mode:

haconf -dump -makero
Note It is only necessary to remove NetBackup from the inactive nodes on which it is
installed.
9. On each inactive node to which NetBackup may failover:
a. Remove the NetBackup software.

◆ On Solaris, run pkgrm to remove the server software and any options or
agents.
◆ On all other platforms, remove everything in the /usr/openv directory.

b. Install the NetBackup Server software. Follow the instructions for “Installing
NetBackup Server Software” as described in the NetBackup Installation Guide for
UNIX.
The virtual name should be used for the server name during the install procedure.
Note Do not perform an upgrade installation on the nodes. NetBackup Server 5.0 is
installed differently in a cluster than NetBackup 4.5FPx and 4.5MPx. An upgrade
installation is only performed on the shared disk (as in step 3).
10. To configure the cluster, run the following command:

/usr/openv/netbackup/bin/cluster/cluster_config -vcs_agent_upgrade
When prompted for the block device, use the same block device for the shared disk
that you used when installing NetBackup 4.5_FPx or 4.5_MPx.
11. If you have devices attached to your failover server, run the Device Discovery wizard
from each node in the cluster. Refer to “Device Configuration Guidelines” on page 74
and “Configuring Devices in a Cluster” on page 75 for guidelines and instructions on
configuring devices in a cluster.
12. On each node on which NetBackup Server is installed, upgrade any NetBackup
agents or options. Refer to the section, “Installing or Upgrading NetBackup Agents
and Options” on page 58. For detailed instructions refer to the system administrator’s
guides for those agents and options.
14. Start the daemons with the hagrp -online command.

Installing a Non-Failover NetBackup Server
Installing a Non-Failover NetBackup Server

▼ To install a NetBackup non-failover server on a VCS for Solaris cluster
1. Review “Installation Prerequisites” on page 49.
2. Install the NetBackup Server software on the local disk of each desired node in the
cluster. Follow the instructions for installing NetBackup Server software as described
in the NetBackup Installation Guide for UNIX.
3. Configure each NetBackup server. Refer to the NetBackup Installation Guide for UNIX,
and the NetBackup System Administrator's Guide for UNIX, Volume I, for information on
configuring NetBackup server software.
Upgrading a NetBackup Non-Failover Server

The process of upgrading a NetBackup non-failover server is the same as for a new
installation. On each node on which NetBackup is installed, install the NetBackup Server
software on the local disk. Follow the instructions for upgrading NetBackup on UNIX
servers and clients as described in the NetBackup Installation Guide for UNIX.
Installing the NetBackup Client Only

Install NetBackup client software on a local disk on all desired nodes in the cluster. Follow
the instructions for a standard client install as described in the NetBackup Installation Guide
for UNIX.



NetBackup in Sun Cluster 7

This chapter provides information on how to install and configure NetBackup in a Sun
Cluster. Refer to the NetBackup System Administrator's Guide for UNIX, Volume I, for a
detailed understanding of how NetBackup is installed and administered. Refer to the
documentation for Sun Cluster for a detailed understanding of how Sun Cluster works,
how it is installed and administered, and for information on the SunPlex cluster system.
65
Complete the following tasks before installing and configuring NetBackup in a Sun
Cluster.
❏ Verify that your hardware is supported by both Sun Cluster and NetBackup. For a list
of supported storage devices, see the NetBackup Release Notes for UNIX and Windows
and the Sun Cluster documentation.
❏ Verify that Sun Cluster 3.0 is correctly installed and configured.
❏ Setup a virtual name for NetBackup in NIS, DNS or /etc/hosts. This hostname will
be used as a logical hostname during the NetBackup installation and configuration of
the cluster. It will not be assigned to any physical node, but will be attached to the
NetBackup application resource, allowing NetBackup to failover to the appropriate
node during the failover process.
❏ The shared disk must be configured and accessible to all cluster nodes on which
NetBackup will be installed. See the Sun Cluster documentation for more information
on how to create and configure a shared disk. Make sure the shared disk has enough
space for the NetBackup database files and directories.
❏ Make sure that each node in the cluster, on which you wish to install NetBackup, is
rsh equivalent. As the root user you need to be able to perform a remote login to each
node in the cluster without entering a password. This is only necessary for installation
and configuration of the NetBackup server and any NetBackup agents and options.
Once installation and configuration is complete this is no longer required.
❏ You must be able to mount the disk on all nodes at the same time (i.e., a global file
system).
license key.


This section describes procedures for setting up and administering NetBackup server as a
failover application in a Sun Cluster.
Installation Notes
server.
◆ The NetBackup resource group name in a Sun Cluster is always scnb-harg. This cannot
be configured by the user.
◆ Two Sun Cluster resource files are installed with NetBackup and should not be edited:
scnb.VRTS and scnb.conf.

▼ To install and configure NetBackup in a Sun Cluster
1. Install the NetBackup on each node to which NetBackup may failover. Follow the
instructions for installing NetBackup Server software as described in the NetBackup
2. Execute /usr/openv/netbackup/bin/cluster/cluster_config on the

primary node. You will be prompted for a hostname that will be used as a logical
hostname, and the directory path for the shared NetBackup space. Enter the same
hostname and shared path for all the nodes. The NetBackup resource group will be
called sncb-harg. The NetBackup resource will be called scnb-hars. Follow the
onscreen directions to configure the type of NetBackup Server you will be using.
Chapter 7, NetBackup in Sun Cluster 67

3. After running cluster_config, NetBackup will be configured to work as a HA

Application. To bring the NetBackup resource group online or offline, special Sun
Cluster commands must be used.
◆ To bring the NetBackup resource group online, /usr/cluster/bin/scswitch
-z -g scnb-harg -h <hostname>.
◆ To take the NetBackup resource group offline, use
/usr/cluster/bin/scswitch -F -g scnb-harg.
See the Sun Cluster documentation for more information on this and other
commands.
Note Use the /usr/cluster/bin/scstat -g command to verify that the NetBackup

resource is online.
start Media Manager daemons. Start the daemons with the scswitch -z -g
scnb-harg -h <hostname> command.
4. Freeze the NetBackup group by executing the following command:

/usr/cluster/bin/scswitch -M -n -j scnb-hars
5. On each node on which NetBackup Server is installed, install any NetBackup agents
or options. Refer to the next section, “Installing or Upgrading NetBackup Agents and
Options.”

fail over properly in the cluster. Refer to “Verifying NetBackup Configuration” on
page 79.


In order to install or upgrade agents and options, NetBackup daemons must be brought
offline without causing a failover. In order to accomplish this, Sun Cluster must be told to
stop monitoring NetBackup, but keep NetBackup resources online.
Reporter) will not cause NetBackup to failover if they fail. Robot daemons and NetBackup
options can be configured to failover NetBackup if a daemon or the option fails. For more
information, see “Configuring Robotic Daemons for Monitoring (VCS for UNIX,
TruCluster, or Sun Cluster)” on page 79 and “Configuring Add-ons for Monitoring in a
VCS for UNIX, TruCluster, or Sun Cluster Environment” on page 80.
▼ To put NetBackup in the unmanaged state
1. Execute the following command:

/usr/cluster/bin/scswitch -M -n -j scnb-hars
2. On each inactive node on which NetBackup Server is installed, install or upgrade any
agents or options. See the appropriate NetBackup documentation for the agent or
option for installation and configuration instructions.
3. Perform the same installation or upgrade on the active node.
4. After completing the installs for the agents or options, execute the following
command:
/usr/cluster/bin/scswitch -M -e -j scnb-hars
This will bring the NetBackup resources online and instruct Sun Cluster to resume
monitoring the NetBackup resource.

Upgrading from NetBackup 4.5FP3 or later (With Sun Microsystem’s NetBackup Agent) to 5.0
Upgrading from NetBackup 4.5FP3 or later (With Sun

Microsystem’s NetBackup Agent) to 5.0
Follow these instructions if you have installed NetBackup failover server on a Sun Cluster
and are using Sun Microsystem’s agent for NetBackup 4.5FP3 or later.

the cluster.
Note These upgrade instructions only support upgrading if you are using a globally
shared disk. NetBackup 5.0 does not support upgrading an HASP configuration. If
you are using an HASP configuration convert your disk to be a global disk (each
machine can access the disk simultaneously).
▼ To upgrade NetBackup with Sun Microsystem’s agent
1. Bring NetBackup offline with the following command:

/usr/cluster/bin/scswitch -F -g netbackup resource group
2. Create a temporary resource group while for upgrading NetBackup:

scrgadm -a -g scnb-harg
Note You must use scnb-harg as the name of the resource group. This is a temporary
group that will be removed after the upgrade.
3. Register the virtual name in the above group:

scrgadm -a -L -g scnb-harg -l virtual-name
4. Bring the NetBackup group online:

scswitch -Z -g scnb-harg
5. In the bp.conf and vm.conf files, change all REQUIRED_INTERFACE entries to

CLUSTER_NAME.
6. Copy all NetBackup databases and files on the shared disk back to their default
locations. This includes but is not limited to the following:
/usr/openv/db/var
/usr/openv/netbackup/db

Upgrading from NetBackup 4.5FP3 or later (With Sun Microsystem’s NetBackup Agent) to 5.0
/usr/openv/netbackup/bp.conf
/usr/openv/volmgr/database
/usr/openv/volmgr/vm.conf
7. On all the other nodes, remove all the links to files and databases on the shared disk.
8. On each of the nodes, edit the bp.conf so the CLIENT_NAME entry is set to the
hostname of the node.
9. On the shared disk, copy the netbackup directory to netbackup.orig.
10. On the active node, perform an upgrade installation. Follow the instructions for
“Upgrading NetBackup on UNIX Servers and Clients” as described in the NetBackup
11. During the install, choose to start up all the daemons.
12. Perform the same upgrade on the inactive nodes.
13. On the inactive nodes, bring the daemons down:

14. Remove the temporary scnb-harg group that was created for the upgrade by running
the following commands:
scswitch -F -g scnb-harg
scswitch -n -j virtual-name
scrgadm -r -j virtual-name
scrgadm -r -g scnb-harg
15. On the active node, run the cluster_config utility.
16. Bring the cluster online with using the following command:
/usr/cluster/bin/scswitch -Z scnb-harg
From now on start and stop netbackup with scswitch. The resource group is named
scnb-harg. The name of the resource group is not configurable.

Performing Backups and Restores in a Sun Cluster
Performing Backups and Restores in a Sun Cluster


Configuring NetBackup 8
Configuration of NetBackup includes configuring storage devices, volumes, the catalog
backup, and creating backup policies. This configuration can be completed most easily by
using the NetBackup Configuration Wizards in the NetBackup Administration Console.
Refer to the NetBackup System Administrator's Guide for Windows, Volume I, or NetBackup
System Administrator's Guide for UNIX, Volume I, for more details for instructions on
performing these steps manually (See the section, “Configuring NetBackup Without
Wizards.”).
Before configuring NetBackup, refer to the following sections in this chapter.
Section Description
“NetBackup Configuration Guidelines” on Guidelines to follow when configuring the

page 74 NetBackup server in a cluster.
“Device Configuration Guidelines” on Guidelines to follow when configuring devices in a

page 74 cluster.
“Configuring Devices in a Cluster” on Instructions for configuring devices in a cluster.

page 75
“Verifying NetBackup Catalog Backup Applicable only to NetBackup installed in a MSCS

Entries” on page 77 or VCS for NT cluster. Instructions for verifying the
NetBackup Catalog entries.
73
NetBackup Configuration Guidelines

◆ The NetBackup server list must be set up correctly on each node where NetBackup is
configured as a failover server. If NetBackup is installed as a master server in the
cluster, the virtual server name must appear first, followed by the node names within
the NetBackup group. If NetBackup is installed as a media server in the cluster, then
the name of the master must appear first in the server list and the virtual server name
must be included elsewhere in the server list.
◆ NetBackup depends on names to route information between participants in the
backup and restore process. Therefore, it is very important that all name usage be
consistent within a NetBackup configuration. Specific node names and cluster aliases
should not be used interchangeably.
◆ CLIENT_NAME should be set to the name of the node.
◆ CLUSTER_NAME should be set to the virtual server name.
◆ With the exception of NetBackup in a TruCluster, when making changes to the
NetBackup configuration on the active node, be sure to apply the same changes to
each node in the cluster.
◆ Any configuration changes should be verified by moving the NetBackup server to
each node to check for the correct setting.
◆ Configuration information for backup policies, storage units, and the NetBackup
catalog backup is stored on the shared disk and cannot be configured separately for
each node.
◆ Use the NetBackup Administration Console as much as possible to configure and
administer NetBackup.
Device Configuration Guidelines

The following are guidelines for avoiding problems as you configure the devices for a
clustered NetBackup server:
◆ If there are devices attached to one node but not to the other node, they are available
only when the node where they are attached is online. For a NetBackup failover
server, it is usually best to attach all of the devices to each node on which NetBackup
is installed using shared SCSI or fibre channel connections as necessary to share the
devices.
◆ For NetBackup Media Server failover, configure devices from the NetBackup Master
Server using the cluster alias or virtual server name as the NetBackup Media Server
name.
In a TruCluster, device paths should be the same on each node in the cluster.

◆ To keep the configuration as straightforward as possible, specify the NetBackup

master server as the volume database host for robots in the cluster and as the
standalone volume database host for standalone tape devices in the cluster.
◆ For tape devices that are in a robotic library, ensure the robot drive number field is set
correctly according to the drive numbering scheme implemented by the manufacturer
of the robotic library. Note that the first drive in the robot is always considered robot
drive number 1 for NetBackup; if the manufacturer’s drive numbering scheme starts
with a different number such as 0, adjust it accordingly.
◆ Ensure that the robot numbers you define for robots used by the failover server are
consistent on all servers that use that robot. If the robot number defined for the robot
on one node does not match the number defined on another node for the same robot,
problems will occur when attempting backups.
◆ When adding devices or including a new device host, specify the virtual server name
of the NetBackup failover server in the Device host field in the Media and Device
Management utility.
◆ For automatic discovery of devices, specify the virtual server name as the device host
to scan.
◆ Always use the virtual server name of the NetBackup failover server in the
NetBackup media server field (Windows interface) or Media server field (Java
interface) when creating storage units that reside on the cluster.
Configuring Devices in a Cluster

This section describes briefly how to configure devices in a clustered environment. For
complete details on this topic, refer to the NetBackup Media Manager System Administrator's
Guide for Windows or NetBackup Media Manager System Administrator's Guide for UNIX.
Note To accommodate disparate SCSI connections on each node of the cluster, devices
must be configured on each node in a MSCS, VCS, Sun Cluster environment. First,
configure the devices on the active node. Then move the NetBackup group to
another node and configure the devices on that node, move NetBackup to another
node and configure the devices on that node, etc.
In a TruCluster, devices need only be configured once.
Chapter 8, Configuring NetBackup 75

Configuring Devices for MSCS, VCS, or Sun Cluster
▼ To configure devices for MSCS, VCS, or Sun Cluster
1. Review the guidelines in the section, “Device Configuration Guidelines.”
2. On the active node, run the Device Configuration wizard. This wizard will
automatically discover and configure the devices and create storage units for those
devices.
Using the Device Configuration wizard is the recommended method of configuring
devices. To add robots and drives manually, refer to the “Configuring and Managing
Devices section in the NetBackup System Administrator's Guide for Windows, Volume I, or
NetBackup System Administrator's Guide for UNIX, Volume I.
Note Be sure to use the virtual server name as the device host to scan.
Note If you are using one or more standalone tape drives, the Standalone Volume
Database Host setting must be changed to the appropriate NetBackup server setting
(usually the NetBackup master server). NetBackup does not change this setting
automatically, so you must verify the setting is correct.
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. Again, use the virtual server name when
specifying the device host.
Note You may observe some transient errors while the cluster is partially configured. For
example, the GUI may indicate the Global Database needs to be synced up. This
error will be resolved once the devices are configured on all nodes in the cluster.
6. Continue configuring the devices on each node in the cluster by repeating step 3
through step 5.
Note If device paths are not displayed after refreshing the Devices node or running
tpconfig, the active node of the cluster is not configured properly.
Note If you wish to configure NetBackup to failover if a robotic device fails, refer to the
section, “Configuring Robotic Daemons for Monitoring (VCS for UNIX, TruCluster,
or Sun Cluster).”

▼ To add new devices

Follow the same procedure as when initially configuring devices in a cluster. First,
configure the devices on the active node. Then move the NetBackup group to another
node and configure the devices on that node, move NetBackup to another node and
configure the devices on that node, etc.
Configuring Devices for a TruCluster
▼ To configure devices in a TruCluster
1. Review the guidelines in the section, “Device Configuration Guidelines.”
2. On the active node, run the Device Configuration wizard. This wizard will
automatically discover and configure the devices and create storage units for those
devices.
Using the Device Configuration wizard is the recommended method of configuring
devices. To add robots and drives manually, refer to the “Configuring and Managing
Devices section in the NetBackup System Administrator's Guide for Windows, Volume I, or
NetBackup System Administrator's Guide for UNIX, Volume I.
Note Be sure to use the virtual server name as the device host to scan.
Note If you are using one or more standalone tape drives, the Standalone Volume
Database Host setting must be changed to the appropriate NetBackup server setting
(usually the NetBackup master server). NetBackup does not change this setting
automatically, so you must verify the setting is correct.
Note If you wish to configure NetBackup to failover if a robotic device fails, refer to the
section, “Configuring Robotic Daemons for Monitoring (VCS for UNIX, TruCluster,
or Sun Cluster).”
Verifying NetBackup Catalog Backup Entries

After you have configured the NetBackup Server, the Files list entries for the NetBackup
Catalog need to be verified and changed, if necessary. The Files list for the Catalog Backup
can be accessed as follows:

Windows Servers
▼ To configure the Catalog Backup file list
1. Open the NetBackup Administration Console,
2. Right-click on Catalog and choose Configure NetBackup Catalog Backup.
3. Click on the Files tab.

Verify that there are entries in the files list for the Catalog Backup for each of the nodes to
which NetBackup can failover. The list must contain three entries for each node:
nodename:install_path\NetBackup\db
nodename:install_path\Volmgr\database
nodename:install_path\NetBackup\var
Where nodename is the physical node name of that node and install_path is the
path where NetBackup is installed on the local drive.
The list must also contain the following two entries for the virtual server:
virtual_server_name:shared_disk_path\NetBackup\db
virtual_server_name:shared_disk_path\Volmgr\database
virtual_server_name:shared_disk_path\Volmgr\misc
Where virtual_server_name is the virtual server name of the NetBackup failover
server and shared_disk_path is the path to the NetBackup files on the shared disk.
UNIX Servers
▼ To configure the Catalog Backup file list
1. Open the NetBackup Administration Console,
2. Right-click on Catalog and choose Configure NetBackup Catalog Backup.
3. Click on the Files tab.
4. Verify that there are entries in the files list for the Catalog Backup for each of the nodes
to which NetBackup can failover.
virtual_name:/usr/openv/var
virtual_name:/path/to/shared/netbackup/db

Configuring Robotic Daemons for Monitoring (VCS for UNIX, TruCluster, or Sun Cluster)
virtual_name:/path/to/shared/volmgr/database/*DB
virtual_name:/path/to/shared/volmgr/datbbase/robotic_def
virtual_name:/path/to/shared/volmgr/database/ltidevs
If there is anything present in the volmgr/database directory besides what is listed
above (e.g., NDMP devices) add entries for these to the Files list.
Verifying NetBackup Configuration

After completing configuration of storage devices, volumes, the catalog backup, and
backup policies, verify that NetBackup fails over properly in the cluster.
1. Confirm that the NetBackup is online on the primary node, then determine if the
following can be completed successfully:
◆ scheduled backups
◆ user-directed backups
◆ NetBackup database backups
◆ server- and user-directed restores
2. Switch the NetBackup resource group to another node and perform the same tests as
above. Repeat for each node in the cluster on which NetBackup is installed.
Configuring Robotic Daemons for Monitoring (VCS for UNIX,

TruCluster, or Sun Cluster)
By default, robotic daemons will not cause NetBackup to failover if they fail. Robot
daemons can be configured to failover NetBackup if a daemon fails.
Note Robots must be configured before performing the following instructions. Refer to
the NetBackup Installation Guide for Windows or NetBackup Installation Guide for UNIX
for instructions on configuring storage 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_config -r

Configuring Add-ons for Monitoring
3. Choose a (Add).
4. Select your robot from the list.

Multiple robots can be selected.
▼ To remove a robotic daemon from monitoring

/usr/openv/netbackup/bin/cluster_config -r
2. Choose d (Delete).
3. Select the robot type you would like to remove.

By default, add-on products (such as NetBackup Advanced Reporter) will not cause
NetBackup to failover if they fail. These products can be configured to failover NetBackup
if an add-on product fails.
Configuring Add-ons for Monitoring in a VCS for UNIX,

TruCluster, or Sun Cluster Environment
▼ To monitor an add-on and failover NBU when the add-on fails

/usr/openv/netbackup/bin/cluster_config -a
2. Choose a (Add).
3. Select your add-on from the list.

Multiple add-ons can be selected.

▼ To remove an add-on from monitoring

/usr/openv/netbackup/bin/cluster_config -a
2. Choose d (Delete).
3. Select the add-on you wish to delete from the list.
Configuring Add-ons for Monitoring in a MSCS Environment

▼ To monitor an add-on service and failover NetBackup when the add-on service fails
1. Open the Cluster Administrator.
2. Select the NetBackup group.
3. In the right-hand pane, double-click on the resource you want to monitor.

The properties for the resource are displayed.
4. Click on the Advanced tab.
5. In the Restart group, select Affects the group.
6. Click Apply.
7. Click OK.
▼ To remove an add-on service from monitoring
1. Open the Cluster Administrator.
2. Select the NetBackup group.
3. In the right-hand pane, double-click on the resource you want to remove from
monitoring.
The properties for the resource are displayed.
4. Click on the Advanced tab.
5. In the Restart group, deselect Affects the group.

6. Click Apply.
7. Click OK.

Using NetBackup to Perform Backups and

Restores in a Cluster 9
This chapter provides information on what data should be backed up in a cluster and
guidelines on how to back up and restore data in a cluster. Specific instructions for
performing backups and restores can be found in the NetBackup User's Guide for Windows
or NetBackup User's Guide for UNIX and in the system administrator guides for NetBackup
options and agents.
83
What to Back Up
What to Back Up
Back up the following to protect all data in the cluster, including file systems and
databases:
◆ Local disks on each node. (See “Backing Up Local Disks in a Cluster” on page 84.)
◆ All disks that attach to the shared SCSI bus. (See “Backing the Shared Disks” on
page 85.)
◆ Virtual servers, which may contain data or contain database applications. Use
NetBackup database agents to back up databases. (See “Backing Up Database Files in
a Cluster” on page 86.)
User backups that are run on individual nodes of the cluster generally run as a backup
of the node, not the NetBackup virtual server. Because of this, it is usually easier and
less confusing to use scheduled backups rather than user backups to protect the data
in the cluster.
MSCS and VCS for Windows Clusters

In addition to the items above, be sure to back up the System State on each node. For
MSCS clusters, the cluster quorum, which contains recovery information for the cluster
and information about changes to the cluster configuration, is included in the System
State backup (Windows 2000 or later only). (See “Backing Up Local Disks in a Cluster” on
page 84.)
Backing Up Local Disks in a Cluster

To protect the data on the node’s local disks, configure a policy that includes the cluster
node names in the client list. In addition to this policy, you must also configure a separate
policy to back up the shared disks (see “Backing the Shared Disks” on page 85).
The following are guidelines for configuring the policy to back up local disks:
◆ If NetBackup is installed on the cluster as a NetBackup failover media server, for the
policy storage unit, select the storage unit 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 node name as
a client. For each policy, select the storage unit created for the NetBackup media
server that is installed on that cluster node.

Backing the Shared Disks
◆ In the Backup Selections list, add the ALL_LOCAL_DRIVES directive. Then add the
shared disks to the Exclude List for each client (or, for UNIX clients, create an exclude
list for the policy that performs backups of those clients). Adding the shared disks to
the Exclude List prevents the shared disks from being backed up with each client’s
local disks.
◆ For Windows 2000 or later, always include System_State:\ in the file list to back
up the System State for each cluster node. In a policy for an MSCS cluster,
System_State:\ will also back up the cluster quorum information.
Backing the Shared Disks

To protect the data on the disks that attach to the shared SCSI bus, configure a policy that
includes the virtual server name associated with the shared disk in the Clients list. In
addition to this policy, you must also configure a separate policy to back up the local disks
(see “Backing Up Local Disks in a Cluster” on page 84).
The following are guidelines for configuring the policy to back up the shared disks:
◆ If NetBackup is installed on the cluster as a NetBackup failover media server, for the
policy storage unit, select the storage unit created for the failover media server.
◆ If NetBackup is installed on the cluster as separate NetBackup media servers, you can
select either a storage unit that was created for one of the media servers or select Any
Available.
◆ If a storage unit that does not have local, direct access to the shared disk drives is used
for the backup, the data is backed up across the network. This occurs even if the
storage unit refers to a NetBackup media server running on a node of the cluster that
does not currently have control of the shared disk drives.
◆ In the Backup Selections list, specify the drive letters or mounted directories of the
shared disks.
Note At the time the backup is initiated, if the cluster resource that defines the virtual
server name of the cluster is controlled by one node of the cluster, while the cluster
resource that defines the shared disks is controlled by another node of the cluster,
the backup will fail. To prevent this condition, ensure that the virtual server name
and the shared disks are configured to failover together so that the same node
always controls them.
◆ For Windows 2000 clusters, the System State information is included in the backup of
the node’s local disks, so it is not necessary to include System_State:\ in the file
list for this policy.
Chapter 9, Using NetBackup to Perform Backups and Restores in a Cluster 85

Backing Up Database Files in a Cluster
Backing Up Database Files in a Cluster

Database applications are installed on a cluster as virtual servers. To protect the data for
these virtual servers, install the appropriate NetBackup database agent on each node of
the cluster (With NetBackup for Windows, database agents are installed along with
NetBackup server and the NetBackup client.) and a policy needs to be created for that
database agent. When configuring a policy for the application/database in the cluster,
always use the virtual server name of the application/database as the client name in the
policy. For complete installation and configuration instructions for a particular database
agent, see the NetBackup documentation for that agent.
Restoring Data in a Cluster

For all file restore operations, use the procedures on performing restores in the NetBackup
User's Guide for Windows or NetBackup User's Guide for UNIX. When restoring files to the
shared disk drives, restore those files to the virtual server name.
When restoring individual database files restore those files to the virtual server name that
corresponds to the client where the database application is installed.
Note Because of the multiple virtual names that refer to the same computer in a cluster
environment, it is possible for files to be backed up in the context of more than one
client name. Careful planning of policies should avoid this problem. However, still
remember that when restoring to a cluster, it may be necessary to browse more than
one client name and perform more than one restore to restore all of the files that you
need.
If you are using the Backup, Archive, and Restore interface on a NetBackup client that is
installed on a cluster, additional configuration steps may be necessary to restore files that
were backed up using the virtual server name. Since the Backup, Archive, and Restore
interface operates in the context of that client’s name, you must perform an redirected
restore to restore the files on the shared disk that were backed up using the virtual server
name. NetBackup allows this redirected restore operation only if the necessary
configuration is performed on the NetBackup master server. This configuration consists of
creating the install_path\NetBackup\db\altnames or
/usr/openv/netbackup/db/altnames directory on the master server and adding
files. See the “Managing Client Restores” section of the NetBackup System Administrator's
Guide for Windows, Volume I, or NetBackup System Administrator's Guide for UNIX, Volume I.
There may be other situations that require the appropriate altnames directory entries to
be created on the master server. If while attempting to restore files from the client, the
operation fails with the error 131 client is not validated to use this server
message, you must set up the altnames directory to allow the operation to succeed. One
example is when the required interface parameter is set to a valid network name for the

client but it does not match the NetBackup client name parameter for that client. Note that
this may often be true for NetBackup clients in a cluster. Of course, using a server-directed
restore is always an option and avoids the need to set up the altnames directory.
Example
Assume the cluster virtual server name is TOE and the cluster node names are TIC and
TAC. Files on the shared disk must be backed up by a NetBackup policy that 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-directed restore
does not have to know which node is in control of the shared disk at the time 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 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.
4. Start the Backup, Archive, and Restore interface on that node and select the virtual
server name (TOE) as the source client and the server (On Windows machines, choose
File > Specify NetBackup Machines. On UNIX machines, choose Actions > Specify
NetBackup Machines).
5. Browse the backed-up files by using the virtual server name (TOE) from the shared
disk and restore them as needed.
Chapter 9, Using NetBackup to Perform Backups and Restores in a Cluster 87


Operational Notes 10
Please note the following when using NetBackup in a clustered environment:
◆ If a NetBackup server fails over and there are backup jobs running, one of two things
will happen. If Checkpoint Restart is enabled for backup jobs for the policy, any
backups were running will be resumed at the last checkpoint, assuming that the
schedule window permits resuming the job.
If Checkpoint Restart is not enabled for backup jobs, any backup jobs that were
running will fail and show up as failed jobs in the Activity Monitor or NetBackup
reports. Regularly scheduled backup jobs are retried according to the normal retry
logic, assuming that the schedule window and so on permit the retry of the job. After
a failover occurs, the user must restart user-directed backups and manual backups.
Refer to the NetBackup System Administrator's Guide for Windows, Volume I, or
NetBackup System Administrator's Guide for UNIX, Volume I, for more information on
Checkpoint Restart.
◆ If a NetBackup server fails over and there are restore jobs running, the user must
manually resume the restores.
◆ After a failover occurs on a NetBackup failover server (master or media), it can take a
while for the tape devices and media servers to be reset to a point where they can be
used again by NetBackup. For example, a tape may have to be rewound before being
available. Until the device is again ready for use by NetBackup, you may see errors
such as 213 (no storage units available for use) or 219 (the required storage unit is
unavailable).
◆ If you have one of the NetBackup administration interfaces currently connected to a
NetBackup failover server, it may be necessary to refresh the interface after a failover
occurs.
89
Delay in Detecting of Loss of Connection (MSCS and VCS on Windows)
Delay in Detecting of Loss of Connection (MSCS and VCS

on Windows)
There may be a delay in detecting the loss of a connection from a NetBackup Windows
master server to a media server.
In certain situations, there can be a delay on a NetBackup Windows master server before it
detects that the connection to a media server has been aborted. For example, if a media
server goes down while running a backup, there may be a delay on the master server
before it detects that the media server is no longer available. While at first it may appear
that there is a problem with the NetBackup Windows master server, this delay is actually a
result of a certain TCP/IP configuration parameter on Windows called KeepAliveTime
that is set to 7,200,000 (two hours, in milliseconds) by default. More information about the
KeepAliveTime and other associated TCP/IP configuration parameters on Windows may
be found in the following Microsoft Knowledge Base articles: Q140325 and Q120642.
The effect of this delay is that NetBackup jobs running on that media server appear to be
active for a period of time after the connection to the media server has gone down. In
some cases this can result in an undesirable delay before the current backup job fails and
is subjected to the normal NetBackup retry logic for execution on a different media server,
if one is available.
This delay is especially noticeable when the media server in question is a NetBackup
failover media server running in a Microsoft Cluster Server (MSCS) environment.
NetBackup relies upon the retry logic of the NetBackup master server to restart
NetBackup jobs that were running on the NetBackup failover media server when a
failover occurs.
It may be advantageous to modify the KeepAliveTime configuration parameter on the
NetBackup Windows master server for the reasons described above. However, this must
be done using extreme caution because the parameter is a system wide parameter that
affects all TCP/IP communications for that system.
Also, it may be advantageous to modify this parameter on Windows media servers that
use the failover master server.

MSCS Clusters
MSCS Clusters
This section describes items that should be noted before using NetBackup as a failover
server in a MSCS environment. In addition to what is covered here, refer to the
information above for further notes that are relevant to all cluster environments.
◆ If there are no tape devices configured on the controlling node of the NetBackup
failover server, the NetBackup Device Manager service resource takes itself offline
since it is not needed. If you do not intend to configure tape devices for the
NetBackup failover server, you may want to delete the NetBackup Device Manager
service resource from the NetBackup group. This way you can avoid seeing the group
in a warning or failed state.
◆ For three- or four-node MSCS clusters, the MSCS Move Group command lists all of
the nodes in the cluster, not just the ones used for the NetBackup failover server. You
must pick a node that is valid for the NetBackup failover server to use. (MSCS will
display all nodes in the cluster, even those nodes on which NetBackup has not been
installed.)
Chapter 10, Operational Notes 91

MSCS Clusters

Additional Configurations for NetBackup

and Clusters A
Several cluster configurations are supported by NetBackup; including the following:
◆ Cluster with Tape Devices on a Shared SCSI Bus
◆ Cluster with Locally-attached Storage Devices
◆ Clusters Sharing Devices on a Fibre Channel SAN
Combinations of these configurations can also be used.
93
Cluster with Tape Devices on a Shared SCSI Bus

In this configuration, a NetBackup failover server (master or media) is installed on the
cluster. Only one of the NetBackup servers installed in the cluster is active at any point in
time. Each node in the cluster has access to the tape devices. Access to the tape devices is
controlled by the fact that only one node of the NetBackup failover server can be active at
any point in time.
Example of a cluster with NetBackup and tape devices on a shared SCSI bus
Shared SCSI
Bus for Disks
Shared SCSI Bus Tape

Private Network
LAN
The devices are configured on each of the failover server nodes independently from the
other node. This allows different SCSI bus numbers, and so on, on each of the nodes to
refer to the same device. Remember, however, that any NetBackup storage units you
create for the failover server must be configured with the actual number of devices. For
example, do not increase the number of drives since there are multiple connections to the
same tape device.
In certain situations, it is possible for a SCSI bus reset to be issued for the SCSI bus where
the shared tape devices attach. Therefore, do not connect tape devices and shared disk
drives to the same SCSI bus; connect each to separate SCSI buses.
Configuring a Shared SCSI Bus for Tape Devices

Before configuring a shared SCSI bus for tape devices, read the following carefully.
To configure tape devices on a shared SCSI bus, you must have the following.
◆ SCSI cables
◆ SCSI terminators

◆ A SCSI adapter in each cluster server to provide a shared external bus between the
nodes
◆ At least one tape device on the shared bus
The tape devices must connect to a bus that uses the same method of transmission as the
device (single-ended, differential, or low-voltage differential). Only one transmission
method can be used on a single SCSI bus.
Terminate the SCSI bus at both ends so commands and data can be transmitted to and
from all devices on the bus. Each SCSI bus must have two terminators and they must be at
each end of the segment.
If a tape device is in the middle of the bus as shown in the preceding figure (“Example of a
cluster with NetBackup and tape devices on a shared SCSI bus”) remove any internal
termination in that device.
If the tape device is at the end of the bus as shown in the following figure (“Example of a
shared bus with tape devices at the end of the bus”) and the tape device has internal
termination, you can use the device’s internal termination to terminate the bus.
Example of a shared bus with tape devices at the end of the bus

Shared SCSI
Bus for Disks
Shared SCSI Bus for Tape
Private Network
LAN
◆ SCSI adapters. This method is not recommended because if the server is disconnected
from the shared bus, or if there is a power supply failure, the bus may not be properly
terminated and be inoperable.
◆ Pass-through (or feed-through) SCSI terminators. These can be used with SCSI
adapters and with some tape devices. If the tape device is at the end of the bus, you
can attach a pass-through SCSI terminator to terminate the bus. The internal
terminators in the tape device must be disabled.
Appendix A, Additional Configurations for NetBackup and Clusters 95

Tip To ensure termination if a power supply failure occurs, turn off the on-board
terminators on the SCSI controller (using the method that the host adapter
manufacturer recommends) and physically terminate the controller with a
terminator.
◆ Y cables. These can be used with some tape

devices. If the tape device is at the end of the
bus, you can attach a terminator to one branch
of the Y cable to terminate the bus. The internal
terminators in the tape device must be
disabled.
Example of a Y cable
◆ Trilink connectors. These can be used with

some tape devices. If the tape device is at the end of the
bus, you can attach a terminator to one of the trilink
connectors to terminate the bus. The internal terminators
in the tape device must be disabled.
Besides terminating the bus, Y-cables and trilink connectors
also let you isolate the devices from the shared bus without
affecting the bus termination. You can maintain or remove that Trilink connector
device without affecting the other devices on the shared SCSI
bus.
▼ To configure a shared SCSI bus for tape devices
1. Install the SCSI controllers for the shared SCSI bus.

Ensure that the SCSI controllers for the shared SCSI bus are using different SCSI IDs.
For example, on the controlling node, set the SCSI controller ID to 6 and on the
failover node set the SCSI controller ID to 7.
2. Prepare the SCSI controllers for the shared SCSI bus. For details, see the
documentation provided by your SCSI host adapter manufacturer.
Note Do not have power on both nodes while configuring the systems. Or, if both nodes
have power on, do not connect the shared SCSI buses to both nodes.
3. Connect the shared SCSI tape devices to the cable, connect the cable to both nodes,
then terminate the bus segment using one of the methods discussed in the previous
section.

Cluster with Locally-attached Storage Devices
Cluster with Locally-attached Storage Devices

In this configuration, a separate NetBackup media server is installed on each desired
node, storage devices are locally attached to those nodes, and no failover protection is
available for the NetBackup media servers.
Cluster with NetBackup and Locally-attached Storage Devices
Locally-attached Shared SCSI Locally-attached

storage devices Bus for Disks storage devices
Heartbeat
LAN
Appendix A, Additional Configurations for NetBackup and Clusters 97

Clusters Sharing Devices on a Fibre Channel SAN
Clusters Sharing Devices on a Fibre Channel SAN

In this configuration, one or more clusters attach to a fibre channel storage area network
(SAN), with a NetBackup failover server (master or media) installed on the cluster. Tape
devices are shared through the SAN. This configuration offers the normal advantages of a
SAN backup environment such as performing backups locally to tape devices through the
fibre connections, instead of across the network to a separate NetBackup server.
This configuration insures that backups and restores will never use the network for data
communications. The prioritized storage unit group makes this possible by using the local
storage unit if it is available, but in the case of a machine failover, the other storage unit
will be used. In the case of the machine failover, the virtual print server will have moved
to the other node as well, so this keeps the backups/restores local.
For complete details on configuring devices in a cluster with a fibre channel SAN, refer to
the NetBackup Media Manager System Administrator's Guide for Windows or NetBackup Media
Manager System Administrator's Guide for UNIX.

bpclusterutil B
Under normal circumstances, cluster configuration is one of the final steps in installing
NetBackup in a cluster. If this step is not done or does not complete successfully, the
bpclusterutil command may be used perform this step.
The “bpclusterutil -c” command runs the cluster configuration step performed by
installation. Using the -a option with the appropriate option name configures the
NetBackup option in a cluster. This command can be run multiple times. Only run this
command from the active node.
NAME
bpclusterutil - Modify and configure NetBackup in a Windows cluster.
SYNOPSIS
install_path\NetBackup\bin\bpclusterutil -c [-np]
install_path\NetBackup\bin\bpclusterutil -a [GDM|NBAR|NDMP]
install_path\NetBackup\bin\bpclusterutil -addnode NodeName
install_path\NetBackup\bin\bpclusterutil -delete
install_path\NetBackup\bin\bpclusterutil -display
install_path\NetBackup\bin\bpclusterutil -depend ServiceName
DependServiceName
install_path\NetBackup\bin\bpclusterutil
[-r NETBACKUPTYPE MASTER|MEDIA
-r CLUSTERTYPE MSCS|VCS
-r CLUSTERGROUPNAME
-r CLUSTERNAME <clustername>
-r NETWORKSELECTION <public|private>
-r VIRTUALSERVERNAME <virtual name>
-r NETBACKUPINSTALLPATH <path>
99
-r NETBACKUPSHAREDDRIVE <drive:>
-r VIRTUALIPADDRESS <ip address>
-r VIRTUALSUBNETMASK <subnet mask>
-r NODENAMES <nodename>
-r GLOBDBHOST <nodename>
-r CLUSTEREDSERVICES <servicename>
-r MONITOREDSERVICES <servicename>]
DESCRIPTION
This command is available on NetBackup master and media servers and is only applicable
to clusters in a Windows environment. This command will allow the user to set up the
registry entries used for cluster configuration and then to configure the cluster as well as
configuring NetBackup add on options.
OPTIONS
-a [GDM|NBAR|NDMP]
Configures the specified NetBackup add-on in a cluster.
-addnode
Adds a node name to the possible owners list of all the resources in the
NetBackup Group.
-c
Configures NetBackup in a cluster based on the values specified in the
registry
-delete
Deletes the registry entries used to configure NetBackup in a cluster.
-depend ServiceName DependServiceName
Sets the cluster resource for ServiceName to have a dependency on
DependServiceName.
-display
Displays the registry entries used for clustering configuration.
-r NETBACKUPTYPE MASTER|MEDIA
CLUSTERTYPE MSCS|VCS
CLUSTERGROUPNAME
CLUSTERNAME <clustername>
NETWORKSELECTION <public|private>

VIRTUALSERVERNAME <virtual name>

NETBACKUPINSTALLPATH <path>
NETBACKUPSHAREDDRIVE <drive:>
VIRTUALIPADDRESS <ip address>
VIRTUALSUBNETMASK <subnet mask>
NODENAMES <nodename>
GLOBDBHOST <nodename>
CLUSTEREDSERVICES <servicename>
MONITOREDSERVICES <servicename>
Sets the corresponding NetBackup cluster configuration registry entry to
the specified value.
If NODENAMES is specified, only one node name can be entered. Execute
the command multiple times to add node names.
If CLUSTEREDSERVICES is specified, only one service name can be
entered. Execute the command multiple times to add service names.
If MONITOREDSERVICES is specified, only one service name can be
entered. Execute the command multiple timesto add service names.
Appendix B, bpclusterutil 101


Index
A VERITAS Cluster Server 2.0 on
accessibility features xvi Windows 2000 3
Advanced Reporter, supported in a cluster 3 VERITAS Cluster Server on UNIX 3
altnames directory 86, 87 VERITAS Cluster Server on Windows
assigned drives 5 NT 3
cluster_config
B
in a TruCluster 20
backups
CLUSTER_NAME 23, 60, 70, 74
and failovers 89
Cluster_Name 39, 45
in a Microsoft Cluster Server (MSCS) 11,
clustering with NetBackup, overview 1
84
compatibility lists 4
in a TruCluster 28
configuration, of NetBackup 74
of local disks in a cluster 84
examples 93
of shared disks 85
NetBackup catalog backups 74
what to back up in a cluster 84
policies 74
bpclusterutil 10, 99–101
server list 74
C storage units 74
caa_profile 22 usage of cluster aliases 74
caa_start 18 usage of node names 74
caa_stop 18 verifying 79
failures 22
D
Checkpoint Restart 89
database agents, supported in a cluster 3
CLIENT_NAME 71, 74
databases
Cluster Application Availability (CAA),
protected in a cluster 1
using with NetBackup 18
transaction support in 5
cluster configurations
device configuration
example 5
adding new devices 77
mixed server types not supported 2
attaching devices to all nodes 74
NetBackup client 1
automatic discovery 75
NetBackup master server 2
Device host 75
NetBackup media server 1
guidelines 74–75
cluster quorum, restoring 11–13
instructions 75
cluster solutions
instructions for MSCS 76
HP Tru64 UNIX TruCluster 3
instructions for Sun Cluster 76
limitations 4
instructions for TruCluster 77
Microsoft Cluster Server 3
instructions for VCS 76
Sun Cluster 3
specifying cluster alias or virtual server
supported environments 3
name 74
103
standalone volume database host 75 installing the NetBackup client 11

virtual server name 75 loss of connection to NetBackup
volume database host 75 server 90
device host 75, 76 monitoring NetBackup options 81
disaster recovery, Microsoft Cluster Server Move Group command 91
(MSCS) 14–16 NetBackup agents, installing on a
drives, assigned 5 failover server 9
NetBackup cluster group name 9
F
NetBackup Device Manager 91
failover
NetBackup options, installing on a
and manually refreshing Administration
failover server 9
Console 89
Possible Owners list 8
and storage unit errors 89
restores in a 11, 86
definition 1
upgrading a NetBackup failover
when backup jobs running 89
server 10
when restore jobs running 89
MM_SERVER_NAME 23
failover master servers 2
MM_SHARED_MISC 39, 45
failover media servers 1, 2
mount/dismount activity 5
G
N
GDM, supported in a cluster 3
NDMP, supported in a cluster 3
Glossary. See NetBackup Help.
NetBackup
K as an active/active application in a
K77NetBackup 20, 25 cluster 4
KeepAliveTime 90 NetBackup Catalog Backup entries,
L verifying
limitations UNIX servers 78–79
media manager in a cluster 4 Windows servers 78
NetBackup in a cluster 4 NetBackup configuration 74
local disks examples 93
backups of 84 verifying 79
protected in a cluster 1 NetBackup Device Manager 91
loss of connection, to NetBackup Windows NetBackup failover server
server 90 installing in a MSCS 8, 9
uninstalling from a UNIX cluster See
M NetBackup Installation Guide for UNIX
Microsoft Cluster Administrator, installing uninstalling from a Windows cluster See
on all NetBackup servers 8 NetBackup Installation Guide for Windows
Microsoft Cluster Server (MSCS) upgrading in a MSCS 10
backup in a 11, 84 NetBackup options
bpclusterutil 99–101 installing on a non-failover server
device configuration 76 TruCluster 26
disaster recovery 14–16 supported in a cluster 3
hardware requirements 8 NetBackup options, monitoring
installation notes 8 on a MSCS cluster 81
installation prerequisites 8 on UNIX clusters 80
installing a NetBackup failover server 9 non-failover servers, converting to failover
installing non-failover media servers 10 servers 4

P installation and configuration 67–68

patches, applying to a TruCluster installation rerequisites 66
non-failover server 27 Media Manager daemons, manually
platforms supported for NetBackup in a starting 68
cluster 4 monitoring NetBackup options 69, 80
monitoring robotic daemons 69, 79
R
NetBackup agents, installing or
Required Network Interface, for a client
upgrading 69
in a Microsoft Cluster Server (MSCS) 11
NetBackup options, installing or
REQUIRED_INTERFACE See
upgrading 69
CLUSTER_NAME
NetBackup resource group
restores
bringing offline 68
and failovers 89
bringing online 68
data in a cluster 86
restores 72, 86
in a Microsoft Cluster Server (MSCS) 11,
rsh equivalency 66
86
shared disk configuration 66
in a TruCluster 86
upgrading a NetBackup 4.5FP3 failover
performing in a TruCluster 28
server 70–71
robotic daemons, monitoring on UNIX
clusters 79 T
robotic libraries 75 tpconfig 76
ROBOTIC_DB_PATH 39, 45 transaction support in database operations 5
TruCluster 28
S
backups in a 28, 84
S77NetBackup 20, 25
caa_profile 22
Scheduled Backup Attempts, in a
caa_stop failures 22
TruCluster 22
device configuration 77
SCSI Reservations 5
device paths 74
scstat 68
failover server configuration 20–22
scswitch 68, 69, 70, 71
hardware requirements 19
server types, mixing 4
installation notes 18
shared disks
installation prerequisites 19
and storage units 85
installing a NetBackup failover
protected in a cluster 1
server 18–19
SSO
installing a NetBackup non-failover
drive allocation resiliency 5
server 18–19
supported in a cluster 3
installing the NetBackup client 28
Standalone Volume Database Host 75, 76, 77
monitoring daemons
storage units
for a non-failover server 25
and NetBackup failover media
monitoring NetBackup options 24, 80
servers 85
monitoring robotic daemons 24, 79
and NetBackup non-failover media
NetBackup agents
servers 85
installing on a failover server 24
virtual server as NetBackup media
installing on a non-failover server 26
server 75
NetBackup options
Sun Cluster
installing on a failover server 24
backups in a 72, 84
installing on a non-failover server 26
cluster_config 68
non-failover server configuration 25–26
device configuration 76
registering NetBackup 26
hardware requirements 66
Index 105
restores in a 28, 86 shared disk configuration 49

Scheduled Backup Attempts 22 supported NetBackup agent for 60
setting up a virtual name 19 upgrading a failover server 60–62
upgrading a failover media server 23–24 upgrading a non-failover server 63
upgrading a failover server 22 virtual name for NetBackup 49
Wakeup Interval setting 22 See also the VERITAS Cluster Server
User’s Guide
U
VERITAS Cluster Server (VCS) for
uninstalling NetBackup Server
Windows 2000
from a UNIX cluster See NetBackup
configuration of NetBackup See the
Installation Guide for UNIX
VERITAS Cluster Server Enterprise Agent
from a Windows cluster See NetBackup
2.2 for NetBackup Installation and
Installation Guide for Windows
Configuration Guide
V installation of NetBackup See the
Vault, supported in a cluster 3 VERITAS Cluster Server Enterprise Agent
VCS Cluster Manager 30 2.2 for NetBackup Installation and
VCS Enterprise Agent for NetBackup 30 Configuration Guide
installing 31 installation, configurations steps after 45
vcs_agent_upgrade 62 limitations 44
VERITAS Cluster Server (VCS) for UNIX NetBackup agents support 44
backups in a 63, 84 NetBackup options supported 44
Clean 48 requirements 44
cluster_config 60 See also the VERITAS Cluster Server
detecting an application failure 48 Installation Guide
hardware requirements 49 See also the VERITAS Cluster Server
installation notes 57 System Administrator’s Guide
installing a non-failover server 63 VERITAS Cluster Server (VCS) for
installing and configuring a NetBackup Windows NT
failover server 57–58 AutoStartList 35, 39
installing the NetBackup client only 63 backups in a 84
Monitor 48 configuring devices 40
monitoring NetBackup options 48, 80 configuring NetBackup 38–40
monitoring robotic daemons 79 configuring VCS Enterprise Agent for
monitoring robots 48 NetBackup 34–37
NetBackup agents, installing 58–59 device configuration 76
NetBackup options, installing 58–59 hardware requirements 30
NetBackup options, monitoring 58 installation prerequisites 30
non-failover server, converting to a installing NetBackup server 32–33
failover server 63 installing VCS Enterprise Agent for
Offline 48 NetBackup 31
Online 48 limitations 30
pre-installation checklist 50 loss of connection, to NetBackup
AIX 53–54 Windows server 90
HP-UX 55–56 NetBackup failover media server 9, 32,
Solaris and Linux 51–52 57, 67
restores 86 restores 86
restores in a 63 upgrading NetBackup server 41
robotic daemons, monitoring 58 virtual server name 2, 75
rsh equivalency 49 and backups 85

as the device host 76, 77 W

in a VERITAS Cluster Server for Wakeup Interval setting
Windows NT 38 in a TruCluster 22
in storage units 75 Wakeup Interval setting, in a TruCluster 22
in the Clients list 85
volume database host 75
Index 107

NetBackup AdminGuide HighAvailability

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetBackup AdminGuide HighAvailability

Uploaded by

Copyright:

Available Formats

NetBackup_AdminGuide_HighAvailability.

book Page i Friday, October 24, 2003 12:04 PM

VERITAS NetBackup™ 5.0 High

System Administrator’s Guide

VERITAS Legal Notice

NetBackup Release 5.0 Revision History

Release Date Description

NetBackup 5.0 December 2003 Original version for this release.

NetBackup Release 5.0 Revision History iii

iv NetBackup High Availability System Administrator’s Guide

Chapter 1. Introduction to NetBackup High Availability . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2. NetBackup in Microsoft Cluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Upgrading a NetBackup Failover Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3. NetBackup in HP Tru64 UNIX TruCluster . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 4. NetBackup in VERITAS Cluster Server on Windows NT . . . . . . . . . . . . 29

vi NetBackup High Availability System Administrator’s Guide

Installing NetBackup Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 5. NetBackup in VERITAS Cluster Server on Windows 2000 . . . . . . . . . . . 43

Chapter 6. NetBackup in VERITAS Cluster Server on UNIX . . . . . . . . . . . . . . . . . . . 47

Scenario 3 - Disk Only, No Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 7. NetBackup in Sun Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 8. Configuring NetBackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

viii NetBackup High Availability System Administrator’s Guide

Configuring Robotic Daemons for Monitoring (VCS for UNIX, TruCluster, or

Chapter 9. Using NetBackup to Perform Backups and Restores in a Cluster . . . . . 83

Chapter 10. Operational Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Appendix A. Additional Configurations for NetBackup and Clusters . . . . . . . . . . . 93

x NetBackup High Availability System Administrator’s Guide

What Is In This Manual?

What Is In This Manual?

xii NetBackup High Availability System Administrator’s Guide

Accessing the VERITAS Technical Support Web Site

Using VERITAS Telephone and E-mail Support

▼ To locate the telephone support directory on the VERITAS web site

1. Open http://support.veritas.com in your web browser.

▼ To contact support using E-mail on the VERITAS web site

1. Open http://support.veritas.com in your web browser.

3. Click Send Message.

xiv NetBackup High Availability System Administrator’s Guide

If you have a Windows server, refer to these documents:

▼ To access the NetBackup online glossary

2. Click the Contents tab.

4. Click NetBackup Glossary of Terms.

xvi NetBackup High Availability System Administrator’s Guide

◆ Microsoft Windows, Windows

Tip Used for nice-to-know information, like a shortcut.

Navigating Multiple Menu Levels

1. Click Start in the task bar.

2. Move your cursor to Programs.

3. Move your cursor to the right and highlight VERITAS NetBackup.

xviii NetBackup High Availability System Administrator’s Guide

Terms Used in this Document

xx NetBackup High Availability System Administrator’s Guide

Introduction to NetBackup High Availability 1

How NetBackup Protects Data in a Cluster

How NetBackup Protects Data in a Cluster

2 NetBackup High Availability System Administrator’s Guide

Supported Cluster Solutions

Supported Cluster Solutions

Supported Cluster Solutions

Cluster Solution Refer to ...

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