EMC NetWorker. Cluster Installation Guide. Release 8.0 P/N REV A02

Transcription

1 EMC NetWorker Release 8.0 Cluster Installation Guide P/N REV A02

2 Copyright EMC Corporation. All rights reserved. Published in the USA. Published July, 2012 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC 2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website. 2 EMC NetWorker Release 8.0 Cluster Installation Guide

3 CONTENTS Revision History Chapter 1 Chapter 2 Chapter 3 Chapter 4 PREFACE Introduction About the NetWorker product NetWorker client NetWorker storage node NetWorker server NetWorker Management Console server NetWorker datazone NetWorker daemons Supported storage devices NetWorker cluster services Enabler codes EMC AutoStart for Microsoft Windows Installation Software installation roadmap Installation requirements Software requirements Hardware requirements Configuration options System information requirements Update the NetWorker software Update to the NetWorker software in an AutoStart 5.4 and later cluster. 22 Install a NetWorker virtual server Task 1: Ensure that the EMC AutoStart software is installed Task 2: Install the NetWorker software in a cluster Task 3: Promote at least one secondary cluster node to primary Task 4: Create the resource that will become the managed shared disk. 24 Task 5: Define the NetWorker server as highly available Task 6: Configure the NetWorker virtual server Task 7: Configure the clients of the NetWorker cluster server Task 8: Register NetWorker licenses for cluster server failover Install only the NetWorker client software in a cluster Task 1: Install the NetWorker cluster client software Task 2: Configure NetWorker client software as cluster aware Uninstall the NetWorker software Configure the NetWorker virtual server with a backup device Troubleshoot the NetWorker software Set the shutdown wait timeout values NetWorker virtual server fails to start nsrmmd NetWorker server fails to back up a virtual cluster client Roll back changes to the cluster configuration file EMC AutoStart for UNIX Installation Software installation roadmap EMC NetWorker Release 8.0 Cluster Installation Guide 3

4 Contents Installation requirements Software requirements Hardware requirements Configuration options System information requirements Update the NetWorker software in an AutoStart 5.4 and later cluster Install a NetWorker virtual server Task 1: Ensure that the AutoStart software is installed Task 2: Install the NetWorker software in a cluster Task 3: Define the NetWorker server as highly available Task 4: Grant access to the NetWorker virtual server Task 5: Configure the NetWorker server Task 6: Configure clients under the NetWorker virtual server Task 7: Register NetWorker licenses for virtual server failover Install a virtual NetWorker Console server Task 1: Install the NetWorker Management software in a cluster Task 2: Define the NetWorker Console server as highly available Install only the NetWorker client software in a cluster Task 1: Install the NetWorker cluster client software Task 2: Configure the NetWorker client software as cluster aware Task 3: Define the list of trusted NetWorker servers Task 4: Configure clients under the NetWorker server Uninstall the NetWorker software AIX Version HP-UX version Linux version Solaris version Configure an external client to back up to a virtual server Define ownership of a raw partition for virtual clients Chapter 5 HACMP or PowerHA SystemMirror for AIX Installation Software installation roadmap Installation requirements Software requirements Hardware requirements Configuration options System information requirements Install a NetWorker virtual server Task 1: Install the NetWorker software in a cluster Task 2: Define the server as highly available Task 3: Define a NetWorker virtual server Task 4: Grant access to the NetWorker virtual server Task 5: Configure the NetWorker cluster server Task 6: Configure clients under the NetWorker cluster server Task 7: Register NetWorker licenses for virtual server failover Install only the NetWorker client software in a cluster Task 1: Install the NetWorker cluster client software Task 2: Configure the NetWorker client software as cluster aware Task 3: Define the list of trusted NetWorker servers Task 4: Configure clients under the NetWorker server Uninstall the NetWorker software Configure an external client to a virtual server Schedule saves for raw volumes Track scheduled saves EMC NetWorker Release 8.0 Cluster Installation Guide

5 Contents Chapter 6 Chapter 7 MC/ServiceGuard and MC/LockManager Installation Software installation roadmap Installation requirements Software requirements for HP-UX Hardware requirements System information requirements Prepare the system for the NetWorker installation Install the NetWorker server as highly available on HP-UX MC/ServiceGuard 74 Task 1: Install the NetWorker server software Task 2: Configure the NetWorker software Task 3: Define the NetWorker software as highly available Task 4: Change the NetWorker servers with access to a client Task 5: Make the cluster nodes a client of the NetWorker virtual server. 80 Task 6: Register NetWorker licenses for cluster server failover VxVM on HP ServiceGuard clusters Install only the NetWorker client software in a cluster Task 1: Install the NetWorker software Task 2: Configure the NetWorker client software in the cluster Task 3: Change the NetWorker servers with access to a client Task 4: Configure cluster clients on the NetWorker server Uninstall the NetWorker software Track scheduled saves Microsoft Cluster Server (MSCS) Installation Cluster terminology Installation requirements Update the NetWorker software Install the NetWorker server Install a NetWorker server for noncluster mode Install a NetWorker server for cluster mode Configure a backup device for the NetWorker virtual server Define a cluster node as a storage node Move the NetWorker server to another node Register NetWorker licenses for cluster failover Restart the NetWorker server services Install only the NetWorker client software in a cluster Uninstall the NetWorker software from MSCS Uninstall the software from all the nodes in the cluster Uninstall the software from only one node in the cluster Troubleshoot the NetWorker software in the MSCS environment NetWorker virtual server fails to start nsrmmd NetWorker server fails to back up a virtual cluster client NetWorker services fail to start in an MSCS environment Chapter 8 Microsoft Failover Cluster on Windows Server 2008 Installation requirements Update the NetWorker software Install the NetWorker software in a Microsoft Failover Cluster Install a NetWorker server as a highly available application Install only the NetWorker client software Uninstall the NetWorker software in a Microsoft Failover Cluster EMC NetWorker Release 8.0 Cluster Installation Guide 5

6 Contents Chapter 9 Chapter 10 Sun Cluster Version 3.2 Installation Software installation roadmap Installation requirements Software requirements Hardware requirements Configuration options System information requirements Update from a previous release of the software Install the NetWorker software in a cluster Install a NetWorker virtual server Install a virtual NetWorker Console server Install only the NetWorker client software in a cluster Install the NetWorker software in a zone cluster Install NetWorker software in a whole root zone cluster Install the NetWorker software in a sparse root zone cluster Uninstall the NetWorker software Configure an external client to a virtual server Define ownership of a raw partition for virtual clients VERITAS Cluster Server Installation Cluster configuration Software requirements Install the NetWorker server in a cluster Task 1: Install the NetWorker software Task 2: Define the NetWorker server as a highly available application. 156 Task 3: Define a NetWorker service group Task 4 (Optional): Create NetWorker Client resource instances Task 5: Grant access to the highly available NetWorker server Task 6: Configure the NetWorker virtual server Task 7: Configure clients under the NetWorker virtual server Task 8: Register licenses for the highly available NetWorker server Task 9: Authorize the software Install only the NetWorker client software in a cluster Task 1: Install the NetWorker cluster client software Task 2: Configure NetWorker client software as cluster aware Task 3 (Optional): Create NetWorker Client resource instances Task 4: Define the list of trusted NetWorker servers Task 5: Configure clients under the NetWorker server Tracking scheduled saves Uninstall the NetWorker software Uninstall the software on Solaris and Linux Uninstall the software on Windows EMC NetWorker Release 8.0 Cluster Installation Guide

7 REVISION HISTORY your clarifications or suggestions for this document to: The following table lists the revision history of this document. Revision Date Description of added or changed sections A02 July 20, 2012 Updated the following: In each chapter, added information to consider when modifying the servers file. Replaced Powerlink references with the EMC Online Support Site. A01 June 21, 2012 First release of this document for Restricted Availability (RA) of EMC NetWorker Release 8.0. EMC NetWorker Release 8.0 Cluster Installation Guide 7

8 Revision History 8 EMC NetWorker Release 8.0 Cluster Installation Guide

9 PREFACE As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. Contact your EMC representative if a product does not function properly or does not function as described in this document. This document was accurate at publication time. New versions of this document might be released on the EMC online support website. Check the EMC online support website to ensure that you are using the latest version of this document. Purpose Audience Related documentation This document describes how to uninstall, update and install the NetWorker software in a cluster environment. This document is part of the NetWorker documentation set and is intended for use by system administrators during the installation and setup of NetWorker software in a cluster environment. The following EMC publications provide additional information: EMC NetWorker Administration Guide Describes how to configure and maintain the NetWorker software. EMC NetWorker Installation Guide Provides information on how to install, uninstall and update the NetWorker software for clients, storage nodes, and servers on all supported operating systems. EMC NetWorker Release Notes Contains information on new features and changes, fixed problems, known limitations, environment and system requirements for the latest NetWorker software release. EMC NetWorker Avamar Devices Integration Guide Provides planning and configuration information on the use of Avamar devices in a NetWorker environment. EMC NetWorker Cloning Integration Guide Contains planning, practices, and configuration information for using the NetWorker, NMM, and NMDA cloning feature. EMC NetWorker Command Reference Guide Provides reference information for NetWorker commands and options. EMC NetWorker Release 8.0 Cluster Installation Guide 9

10 PREFACE EMC NetWorker Data Domain Deduplication Devices Integration Guide Provides planning and configuration information on the use of Data Domain devices for data deduplication backup and storage in a NetWorker environment. EMC NetWorker Disaster Recovery Guide Contains information about preparing for a disaster and recovering NetWorker servers, storage nodes, and clients. EMC NetWorker Error Message Guide Provides information on common NetWorker error messages. EMC NetWorker Licensing Guide Provides information about licensing NetWorker products and features. EMC NetWorker Performance Optimization Planning Guide Contains basic performance sizing, planning, and optimizing information for NetWorker environments. EMC NetWorker Management Console Online Help Describes the day-to-day administration tasks performed in the NetWorker Management Console and the NetWorker Administration window. To view Help, click Help in the main menu. EMC NetWorker User Online Help The NetWorker User program is the Windows client interface. Describes how to use the NetWorker User program which is the Windows client interface connect to a NetWorker server to back up, recover, archive, and retrieve files over a network. NetWorker Procedure Generator The NetWorker Procedure Generator (NPG) is a stand-alone Windows application used to generate precise user driven steps for high demand tasks carried out by customers, support, and the field. With the NPG, each procedure is tailored and generated based on user-selectable prompts. This generated procedure gathers the most critical parts of NetWorker product guides and are combined with the advice of experts in a single document with a standardized format. To access the NetWorker Procedure Generator, log on to: You must have a valid service agreement to use this site. Technical Notes/White Papers Technical Notes and White Papers provide an in-depth technical perspective of a product or products as applied to critical business issues or requirements. Technical Notes and White paper types include technology and business considerations, applied technologies, detailed reviews, and best practices planning. Conventions used in this document EMC uses the following conventions for special notices: NOTICE is used to present information that is important or essential to software or hardware operation. 10 EMC NetWorker Release 8.0 Cluster Installation Guide

11 PREFACE Note: A note presents information that is important, but not hazard-related. Used in tables. Typographical conventions EMC uses the following type style conventions in this document: Normal Used in running (nonprocedural) text for: Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, functions, and utilities URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, and notifications Bold Used in running (nonprocedural) text for names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, and man pages Used in procedures for: Names of interface elements, such as names of windows, dialog boxes, buttons, fields, and menus What the user specifically selects, clicks, presses, or types Italic Used in all text (including procedures) for: Full titles of publications referenced in text Emphasis, for example, a new term Variables Courier Used for: System output, such as an error message or script URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Courier bold Used for specific user input, such as commands Courier italic Used in procedures for: Variables on the command line User input variables < > Angle brackets enclose parameter or variable values supplied by the user [ ] Square brackets enclose optional values Vertical bar indicates alternate selections the bar means or { } Braces enclose content that the user must specify, such as x or y or z... Ellipses indicate nonessential information omitted from the example Where to get help EMC support, product, and licensing information can be obtained as follows: Product information For documentation, release notes, software updates, or information about EMC products, licensing, and service, go to the EMC online support website (registration required) at: EMC NetWorker Release 8.0 Cluster Installation Guide 11

12 PREFACE Technical support For technical support, go to EMC online support and select Support. On the Support page, you will see several options, including one to create a service request. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account. Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to: BSGdocumentation@emc.com 12 EMC NetWorker Release 8.0 Cluster Installation Guide

13 CHAPTER 5 Introduction This chapter includes these sections: About the NetWorker product About the NetWorker product NetWorker client NetWorker storage node NetWorker server NetWorker Management Console server NetWorker datazone NetWorker daemons Supported storage devices NetWorker cluster services Enabler codes The EMC NetWorker product is a storage management software suite that provides backup, recovery, and other services to machines with a wide variety of operating systems and data types. NetWorker products for different operating systems are interoperable. This provides the flexibility to design a storage management system that works best with the current computing environment. The NetWorker software is distributed in these formats: In a media kit that contains the software and electronic documentation for several related NetWorker products. As a downloadable archive file from the EMC Online Support Site web site. The NetWorker product has these components: NetWorker client NetWorker storage node NetWorker server NetWorker management console server NetWorker language packs NetWorker license manager NetWorker client The NetWorker client software communicates with the NetWorker server and provides client initiated backup and recover functionality. The NetWorker client software is installed on all machines that are backed up to the NetWorker server. Introduction 13

14 Introduction NetWorker storage node Data is backed up directly to devices local to a NetWorker server or remotely to a NetWorker storage node. A storage node controls storage devices such as tape drives, disk devices, autochangers, and silos. The NetWorker server is a local storage node. A remote NetWorker storage node: Off-loads most of the data movement involved in a backup or recovery operation from the NetWorker server Improves performance. Requires high I/O bandwidth to manage the transfer of data transfer from local clients, or network clients to target devices. Can be a different operating system from the NetWorker server. NetWorker server The NetWorker server provides services to back up and recover data for the NetWorker client machines in a datazone. The NetWorker server can also act as a storage node and control multiple remote storage nodes. Index and media management operations are some of the primary processes of the NetWorker server: The client file index tracks the files that belong to a save set. There is one client file index for each client. The media database tracks: The volume name. The location of each save set fragment on the physical media (file number/file record). The backup dates of the save sets on the volume. The file systems in each save set. Unlike the client file indexes, there is only one media database per server. The client file indexes and media database can grow to become prohibitively large over time and will negatively impact backup performance. The NetWorker server schedules and queues all backup operations, tracks real-time backup and restore related activities, and all Console server communication. This information is stored for a limited amount of time in the jobsdb database which for real-time operations, has the most critical backup server performance impact. The data stored in the jobsdb database is not required for restore operations. 14 EMC NetWorker Release 8.0 Cluster Installation Guide

15 Introduction NetWorker Management Console server The NetWorker Management Console (NMC) server or Console server, is a Java based web application server that provides centralized: Management of multiple NetWorker servers across multiple datazones. Monitoring of multiple NetWorker servers across multiple datazones. Backup reporting of multiple NetWorker servers across multiple datazones. The Console server: Is installed on an AIX, Linux, Solaris, or Microsoft Windows host. Is accessed through a graphical user interface on a host with a web-enabled browser that has the specified version of Java Runtime configured. Multiple users can access the Console server concurrently from different browser sessions. A machine that hosts the web-enabled browser can also be a NetWorker client, server, or storage node. Embeds the Apache server software. The apache software is used to: Download of the Console jar files. Startup of the Console server daemon or service. Embeds the Sybase SQL Anywhere software. NetWorker datazone NetWorker daemons The Console server database is a Sybase SQL Anywhere database. A NetWorker datazone is a single NetWorker server and its client and storage node machines. The NetWorker software requires processes on Windows or daemons on UNIX to run on the system and facilitate NetWorker operations in the datazone. Table 1 on page 15 lists the NetWorker daemons for each of the software components. Table 1 NetWorker daemons NetWorker packages NetWorker server NetWorker client NetWorker storage node NetWorker Management Console server NetWorker daemons nsrd, nsrexecd, nsrindexd, nsrmmdbd, nsrmmd, nsrjobd, nsrmmgd, nsrlcpd, nsrlogd nsrexecd nsrexecd, nsrmmd, nsrlcpd, nsrsnmd gstd, httpd, dbsrv12 NetWorker Management Console server 15

16 Introduction Consider the following: The nsrmmd process or daemon is present when one or more devices are enabled. The nsrmmgd process or daemon is present on the NetWorker server when a library is enabled. The nsrlcpd process or daemon is present on a NetWorker server and storage nodes with an attached library. The nsrcpd process or daemon is present on the NetWorker server during a client push software upgrade. The Console server daemon, gstd starts these additional processes: dbsrv12 the SQL Anywhere database process. httpd there will be 2 or more httpd processes. gstsnmptrapd an optional process that is present on the Console server when SNMP Trap monitoring is configured for a Data Domain system. Supported storage devices Storage devices are attached to a NetWorker server or to a designated storage node. The NetWorker software supports a variety of media types and devices including: Disk devices Stand-alone tape devices Tape devices in an autochanger or silo tape library The term autochanger refers to a variety of backup devices: Autoloader Carousel Datawheel Jukebox Library Near-line storage NetWorker cluster services The NetWorker 7.3 (and Later) Hardware Compatibility Guide provides the most up-to-date list of supported devices. In cluster setups on all supported cluster platforms, the cluster services must be running before the NetWorker services start. When the cluster services start after Networker, the NetWorker software will exhibit undesirable behavior. 16 EMC NetWorker Release 8.0 Cluster Installation Guide

17 Introduction Enabler codes Enabler codes or licenses activate the functionality of the NetWorker software and are generally sold separately. The NetWorker 8.0 License Guide provides more information. Enabler codes 17

18 Introduction 18 EMC NetWorker Release 8.0 Cluster Installation Guide

19 Chapter 6 EMC AutoStart for Microsoft Windows Installation This chapter includes these sections: Software installation roadmap Installation requirements Update the NetWorker software Install a NetWorker virtual server Install only the NetWorker client software in a cluster Uninstall the NetWorker software Configure the NetWorker virtual server with a backup device Troubleshoot the NetWorker software EMC AutoStart for Microsoft Windows Installation 19

20 EMC AutoStart for Microsoft Windows Installation Software installation roadmap Installation requirements Software requirements Use the following roadmap when installing the NetWorker software: 1. Review Installation requirements on page 19 and note the default directory location. 2. Install the required NetWorker software by following one of these procedures: Install a NetWorker virtual server on page 23 Install only the NetWorker client software in a cluster on page Enable and register all of the NetWorker products. More information is available in the NetWorker Licensing Guide. This section specifies the software and hardware required to install and configure the NetWorker server or client software within an AutoStart TM cluster environment. The EMC Information Protection Software Compatibility Guide provides the most up-to-date software and hardware requirements. The following software must be installed on each node in the cluster: Software requirements on page 20 Hardware requirements on page 20 Configuration options on page 20 System information requirements on page 21 Cluster server This software must be installed on the cluster server: Windows 2003 Server/Advanced Server (latest Service Pack installed) or later EMC AutoStart release 5.3 SP1 or 5.3 SP2 Dedicated shared disk to be used as the NetWorker storage disk (for the nsr folder) connected to all the nodes within the cluster Device with local affinity for the local bootstrap backup Ensure that the most recent cluster patch for the operating system is installed. Cluster client This software must be installed on the private disk of each node in the cluster: Windows 2003 Server/Advanced Server (latest Service Pack installed) or later EMC AutoStart release 5.3 SP1 or 5.3 SP2. 20 EMC NetWorker Release 8.0 Cluster Installation Guide

21 EMC AutoStart for Microsoft Windows Installation Hardware requirements There are no hardware requirements for the cluster client. The following hardware requirements must be met for server installation only: Dedicated shared disk that is used as the NetWorker storage disk (for the /nsr directory) is connected to all the nodes within the cluster. Device with local affinity for the local bootstrap backup is connected to all the nodes within the cluster. Configuration options The NetWorker Administration Guide provides information on how to configure: Tape libraries with a NetWorker virtual server Remote physical storage node with a NetWorker virtual server System information requirements Figure 1 on page 21 and Table 2 on page 21 illustrate the system information needed to install NetWorker software within an AutoStart environment. Different platforms use different terms for the same cluster concepts. AutoStart refers to: Physical hosts as nodes Virtual server as a resource group (application service Installation requirements 21

22 EMC AutoStart for Microsoft Windows Installation ) Node 1 clus_phys1 Node 2 clus_phys2 Private NetWork Local Disk clus_log1 If Node1fails, clus_log1 fails over to Node2 Local Disk NetWorker Logical Host Volume-managed Shared Disks Terminal Concentrator Administrative Workstation Public NetWork Figure 1 Sample cluster configuration Table 2 Information required during NetWorker virtual server installation Required information Pathname for the shared nsr directory Server name of the NetWorker virtual server Example s:\nsr jupiter Server netmask Domain name for the AutoStart server (Domain names are case-sensitive) Installation directory pathname Server names of first and second physical hosts in the AutoStart Cluster. Server names must not exceed fifteen characters in length. galaxy C:\Program Files\EMC\AutoStart\galaxy. mars saturn 22 EMC NetWorker Release 8.0 Cluster Installation Guide

23 EMC AutoStart for Microsoft Windows Installation Update the NetWorker software To update the NetWorker server software in an AutoStart environment: 1. Start the EMC AutoStart Console and take the NetWorker server Cluster resource group offline. 2. Rename the NetWorker.clustersvr file to NetWorker.nocluster. This file is typically located in %SystemDrive%\Program Files\EMC NetWorker\nsr\bin. 3. Upgrade the NetWorker software. The NetWorker Installation Guide provides instructions. 4. Stop the NetWorker Backup and Recover Server service. 5. Open the NetWorker Backup and Recover Server service properties and change the Startup type from Automatic to Manual. 6. Rename the NetWorker.nocluster file back to NetWorker.clustersvr. 7. Repeat step 2 through step 6 on the second node of the cluster. 8. Bring the NetWorker server Cluster resource group back online. Update to the NetWorker software in an AutoStart 5.4 and later cluster Beginning in AutoStart release 5.4, AutoStart no longer provides the nwclust.pl script. The NetWorker software includes the script, and as a result the location of the script has changed, and the lcmap script must be updated to point to the new location. When updating the NetWorker software in an AutoStart 5.4 or later cluster environment, reconfigure the AutoStart cluster to point the generated lcmap script to the correct location of the nwclust.pl script: 1. Run lc_config -r. 2. Run lc_config. The following example shows the generated lcmap script on Windows after the cluster configuration: SET FT_DIR=C:\Program Files\EMC\AutoStart\eas54 SET FT_DOMAIN=eas54 "C:\Program Files\EMC\AutoStart\eas54\bin\ftPerl" "C:\Program Files\EMC NetWorker\nsr\bin\nwclust.pl" For a new installation of the NetWorker software, these steps for upgrading do not apply. Install only the NetWorker client software in a cluster on page 29 provides instructions on installing the NetWorker software in an AutoStart cluster environment. Update the NetWorker software 23

24 EMC AutoStart for Microsoft Windows Installation Install a NetWorker virtual server To install and configure the NetWorker software as a highly available service in a cluster, complete these tasks: Task 1: Ensure that the EMC AutoStart software is installed on page 23 Task 2: Install the NetWorker software in a cluster on page 23 Task 3: Promote at least one secondary cluster node to primary on page 24 Task 4: Create the resource that will become the managed shared disk on page 24 Task 5: Define the NetWorker server as highly available on page 24 Task 6: Configure the NetWorker virtual server on page 26 Task 7: Configure the clients of the NetWorker cluster server on page 27 Task 8: Register NetWorker licenses for cluster server failover on page 28 Task 1: Ensure that the EMC AutoStart software is installed Ensure that the AutoStart software is installed. The AutoStart documentation provides detailed installation instructions. Task 2: Install the NetWorker software in a cluster On each node in the cluster, install NetWorker server software in the same location on a private disk, for example, in %SystemDrive%\Program Files\EMC NetWorker\nsr. To install the NetWorker software: 1. Log in as administrator on one node. 2. Install these NetWorker software packages on each node in the cluster: Client Storage Node Server Man pages The EMC NetWorker 8.0 Installation Guide provides detailed installation instructions. 24 EMC NetWorker Release 8.0 Cluster Installation Guide

25 EMC AutoStart for Microsoft Windows Installation 3. Obtain the NetWorker hostid: a. Launch the NetWorker Management Console software. b. From the Administration windows, select Registration from the Configuration menu. c. Right-click NetWorker/10 Eval and select Properties. The value that is displayed in the HostID field is the hostid for the node on which NetWorker server is running. This HostID is required later in the installation. 4. Repeat step 1 through step 3 on the second node. Task 3: Promote at least one secondary cluster node to primary Always run two primary controllers. Promote at lease one secondary node to the primary by using the AutoStart Console. If one node fails, the other can be online automatically with all data. The AutoStart documentation provides detailed instructions. Task 4: Create the resource that will become the managed shared disk On one of the cluster nodes, create a folder to use later as the managed, shared disk. For example, create the folder s:\nsr. Do not share the folder at this point, or the installation will fail. If the AutoStart software is already installed and a managed shared disk already exists, remove the share property now. Task 5: Define the NetWorker server as highly available To define the NetWorker server as a highly-available application, run the lc_config script on each node. By configuring the NetWorker server as a highly-available application, you create a NetWorker cluster group resource. This allows the NetWorker server to run in cluster mode (that is, with failover capability). To run the lc_config script: 1. Log in as administrator. 2. Add the virtual hostnames to the hosts file on each cluster node (located in %SystemRoot%\system32 # # \drivers\etc). 3. Ensure that all node names to be used in the cluster, both the physical nodes and the virtual nodes, can be resolved using DNS. To verify that the node names can be resolved by using DNS, type: nslookup node_name Install a NetWorker virtual server 25

26 EMC AutoStart for Microsoft Windows Installation 4. Start the NetWorker Backup and Recover Server services. If you are upgrading NetWorker software or reinstalling after a partial uninstall of the NetWorker software, the lc_config script prompts for a command to keep, rename or delete each of the old server configuration files. It is safe to delete the old files. To delete a file, type d when prompted. After you finish typing the choices for each of the old configuration files, continue with step Run the lc_config script. When the lc_config script runs, you are prompted to type the information listed in Table 2 on page 21. lc_config C:\Program Files\EMC NetWorker\nsr\bin>lc_config Checking for C:\Program Files\EMC NetWorker\nsr\bin\lcmap.bat Checking for C:\Program Files\EMC NetWorker\nsr\bin\NetWorker.clustersvr Enter shared nsr dir:s:\nsr Enter the EMC Fulltime Autostart domain name:galaxy Enter the directory in which your EMC Fulltime Autostart software is installed (typically something like C:\galaxy): C:\Program Files\EMC\AutoStart\galaxy 6. Type y to confirm that the information is correct. If required to make corrections, type n. When lc_config script runs again, retype the information: You entered the following data: Nsr Dir = s:\nsr, EMC Fulltime Autostart domain = galaxy EMC Fulltime Autostart software location = C:\Program Files\EMC\AutoStart\galaxy Is this OK [y/n]y 7. Stop the NetWorker Backup and Recover Server services. 8. Edit the nw_nt.aam5.imp file and modify these fields: Virtual hostname Physical cluster node names Shared drive letter The #NW customise label tag appears before each field that requires modification. 26 EMC NetWorker Release 8.0 Cluster Installation Guide

27 EMC AutoStart for Microsoft Windows Installation 9. On one node only, go to %SystemDrive%\Program Files\EMC NetWorker\nsr\bin and run the following command. For example, if the AutoStart domain name is galaxy, type: C:\Program Files\EMC\AutoStart\galaxy\bin\ftcli -d galaxy -c "import nw_nt.lc.imp" This information is displayed: C:\Program Files\EMC NetWorker\nsr\bin>"C:\Program Files\EMC\AutoStart\galaxy\bin\ftcli" -domain galaxy -c "import nw_nt.aam5.imp"ip Address "guiro" Created Process Class "nsrd" Created Process "NSRserver" Created Configuration "NSRserver" Created Process Class "nsrexecd" Created Process "NSRexecd" Created Configuration "NSRexecd" Created Data Source "networker_ds" Created Resource Group "networker" Created OK 10. Use the AutoStart Console to: a. Verify that the NetWorker Server resource was created. b. Share the managed shared disk (for example, s:\nsr). c. Bring the NetWorker virtual server online. d. Select the disk to be used for NetWorker virtual server storage and set the disk to be managed as a shared storage for each physical node in the cluster. 11. For each physical node in the cluster, ensure that the AutoStart Console user account, NT AUTHORITY\SYSTEM is included in the valid user list with administrator access. 12. Ensure that the value of the environment variable for the administrator user FT_DOMAIN is set to the AutoStart domain name. Install a NetWorker virtual server 27

28 EMC AutoStart for Microsoft Windows Installation 13. From one node in the cluster: a. Log in as administrator. b. Ensure that the data source for the NetWorker virtual server is managed by the AutoStart Management Console. The data source for the NetWorker virtual server is defined as networker_ds in the NetWorker resource group. c. Run this script from the directory where the NetWorker software was installed: nwinst.bat The AutoStart documentation provides instructions on using the AutoStart Console. AutoStart warning messages are generated when running the nwinst.bat script. The messages do not indicate that any AutoStart functionality is affected, and should be ignored. This is an example of an Autostart warning message: Connecting to AutoStart domain autostar...backbone warning on primrose (pid 135) Wed Mar 31 01:52: in ISIS_MGT_INTERCL_MODULE.\cl_inter.c/intercl_accept(), line 1927 ID Intercl IO Queue NULL/IO_DEAD calling resurrect. Process from=1/612 nd dest=1/1352. Backbone warning on primrose (pid 1352) Wed Mar 31 01:52: in ISIS_MGT_INTERCL_MODULE.\cl_inter.c/intercl_accept(), line 1927 ID Intercl IO Queue NULL/IO_DEAD calling resurrect. Process from=2/1868 and dest=1/1352. Task 6: Configure the NetWorker virtual server To configure the NetWorker server: 1. Log in as administrator on the cluster node that is currently running the NetWorker server resource group. 2. Start the NetWorker Console software. 3. From the Administration window, select Properties from the File menu. a. For the Administrator attribute, add entries for any cluster nodes that are not already listed. For example: b. Click Ok. 28 EMC NetWorker Release 8.0 Cluster Installation Guide

29 EMC AutoStart for Microsoft Windows Installation 4. Restrict the set of NetWorker servers that can back up a particular client. Edit the %SystemDrive%\Program Files\EMC NetWorker\nsr\res\servers file and add the NetWorker virtual host as well as each cluster node to the list of servers. Consider the following: If no servers are specified, any NetWorker server can backup this client. If no servers are specified, any NetWorker server can perform a directed recovery to the client. When adding NetWorker servers, specify both the short name and FQDN for each NetWorker server. Task 7: Configure the clients of the NetWorker cluster server To configure each client under the NetWorker server: 1. (Optional) Define save groups. In order for their save sets to restart after a virtual client or NetWorker server failover, save groups must have the Autorestart attribute enabled and the Manual Restart option disabled. 2. Make each physical client within the cluster a client of the NetWorker server. For each physical client in the cluster: a. Create a new NetWorker client. b. For the Name attribute, type the name of the physical client. 3. Make each virtual client within the cluster a client of the virtual NetWorker server. For each virtual client in the cluster: a. Create a new NetWorker client. b. For the Name attribute, type the name of the virtual client. c. For the Remote Access attribute, add entries for each physical client within the cluster. For example: root@clus_phys1 d. For the Group attribute, select a group. The first time the NetWorker application runs, it creates the Client resource for the NetWorker virtual server. The NetWorker 8.0 Administration guide provides more information. 4. Verify that the Client and Group resources are properly configured by running a test probe. On the node where the NetWorker server resides, type: savegrp -pv -c client_name group_name If this test does not display the expected scheduled backups and index, create an empty file named pathownerignore in the directory where the NetWorker savefs command is installed. This allows a valid save set on a NetWorker client to be scheduled for backup. For example: Install a NetWorker virtual server 29

30 EMC AutoStart for Microsoft Windows Installation On each node of the cluster, type: echo NUL: networker_bin_dir\pathownerignore A NetWorker scheduled save might use a default rather than a specified client index name. To override this default, run a manual save with the -c option: save -c client_name 5. Restrict the set of NetWorker servers that can back up a particular client. Edit the %SystemDrive%\Program Files\EMC NetWorker\nsr\res\servers file and add the NetWorker virtual host as well as each cluster node to the list of servers. Consider the following: If no servers are specified, any NetWorker server can backup this client. If no servers are specified, any NetWorker server can perform a directed recovery to the client. When adding NetWorker servers, specify both the short name and FQDN for each NetWorker server. After the client configuration is complete: The NetWorker cluster server uses the IP address of the NetWorker virtual host regardless of which cluster node currently masters the NetWorker virtual server. The NetWorker cluster server takes the identity of the NetWorker virtual server s hostname regardless of which cluster node is currently running the NetWorker service. The first time NetWorker software runs, it creates the client resource for the NetWorker virtual host. Client resources must be created manually for any cluster node to be backed up by the NetWorker virtual host. Task 8: Register NetWorker licenses for cluster server failover To register NetWorker licenses for cluster failover: 1. Ensure that the NetWorker virtual server is defined as part of a cluster. 2. Ensure that the NetWorker service is running. 3. Log in to the cluster node on which the NetWorker virtual server is running. 4. Create a file named hostids in the nsr\res directory. 5. Open the hostids file and add one line. For hostid values, use the NetWorker hostids values that were derived in Task 2: Install the NetWorker software in a cluster on page 23. hostid1:hostid2 6. Restart the NetWorker virtual server by taking it offline and then bringing it back online. 7. Register the NetWorker software for permanent use. More information is available in the NetWorker Licensing Guide. 30 EMC NetWorker Release 8.0 Cluster Installation Guide

31 EMC AutoStart for Microsoft Windows Installation Install only the NetWorker client software in a cluster To install NetWorker cluster client, read and follow the procedures for these tasks: Task 1: Install the NetWorker cluster client software on page 29 Task 2: Configure NetWorker client software as cluster aware on page 29 Make sure the NetWorker client software is installed on every node to be backed up in the cluster. Task 1: Install the NetWorker cluster client software To install the NetWorker client software on each node in the cluster: Ensure that the operating system is updated with the most recent cluster patch. Install the NetWorker client software on the physical disk of each node in the cluster to be backed up. More information is available in the NetWorker Licensing Guide. Task 2: Configure NetWorker client software as cluster aware To configure the NetWorker client software as cluster aware: 1. Make each physical client within the cluster a client of the NetWorker server. For each physical client in the cluster: a. Create a new client. b. For the Name attribute, type the name of the physical client. If a physical Client is backed up to a NetWorker server outside the cluster, the name of any virtual service that can run on the physical node must be added to the Remote Access list of the physical Client resource. 2. Add the virtual hostnames to the hosts file on each cluster node (located in %SystemRoot%\system32 # # \drivers\etc). 3. Make each virtual client within the cluster a client of the NetWorker server. For each virtual client in the cluster: a. Create a new client. b. For the Name attribute, type the name of the NetWorker server. c. For the Remote Access attribute, add entries for each physical client within the cluster. For example: root@clus_phys1 d. For the Group attribute, select a group. 4. Schedule backups by using the NetWorker application. Install only the NetWorker client software in a cluster 31

32 EMC AutoStart for Microsoft Windows Installation 5. On each node in the cluster, run the cluster configuration program lc_config. a. Log in as administrator on each node. b. Run the lc_config program: lc_config When prompted for the shared nsr directory, you can leave the field blank. c. Type y to confirm the information. 6. For each physical node in the cluster, ensure that the AutoStart Console user account, NT AUTHORITY\SYSTEM is included in the valid user list with administrator access. Uninstall the NetWorker software To uninstall the NetWorker software from an AutoStart environment: 1. Take the NetWorker Resource Group offline. 2. Select and delete the NetWorker Resource Group from the Current Resource Group list. 3. Select and delete the NSRserver and the NSRexecd services. 4. Select and delete the networker_ds resource. 5. Select and delete the NetWorker virtual server IP Address. 6. On each node in the cluster: a. Log in as administrator on the computer from which the software is being removed. b. Undo all changes to the configuration by running the following: lc_config.exe -r 7. Uninstall the NetWorker Server software from each node. The NetWorker Installation Guide provides instructions. If the NetWorker software will be reinstalled to the same location, ensure that the required files are deleted from the /bin subdirectory: NetWorker.clustersvr, lcmap.bat and winst.bat. Configure the NetWorker virtual server with a backup device The NetWorker virtual server must be configured with storage node backup devices. The storage nodes that are used by the NetWorker virtual server can be devices attached to a remote system (external to the cluster). They can also be devices connected locally to any of the physical nodes in the cluster. A storage node device can be a stand-alone tape device or an autochanger. The NetWorker Administration Guide provides information about how to configure storage nodes. The NetWorker server requires a local backup device to save the bootstrap and the server indexes. 32 EMC NetWorker Release 8.0 Cluster Installation Guide

33 EMC AutoStart for Microsoft Windows Installation This is the recommended device configuration for a NetWorker virtual server, release 6.0 or later, that is running in a two-node AutoStart cluster: Each cluster node must be defined as a storage node for the NetWorker virtual server. In the AutoStart Console, the Preferences\ Storage Nodes attribute in the NetWorker virtual server Client resource lists the storage nodes that are enabled to store data for the client. Each of the storage nodes must be listed before you can list the nsrserverhost: 1. One cluster node 2. The other cluster node 3. The nsrserverhost The nsrserverhost must always be listed last in each client's storage node list. NetWorker software does not allow the configuration of a storage node on a cluster node that is running the NetWorker server binaries. Consequently, before configuring a cluster node as a storage node, you must move the NetWorker virtual server to another node in the cluster. Troubleshoot the NetWorker software Set the shutdown wait timeout values These sections contain troubleshooting tips for NetWorker software in an AutoStart environment. To prevent timing problems during failover, perform this procedure to increase the shutdown wait timeout value for the NSRserver service. 1. Start the EMC AutoStart Console and select the domain. 2. Select Resource Groups>NetWorker Resource group. 3. Select the Settings tab. 4. Select NSRserver from the list box and click Edit. 5. Increase the value for the Wait until service is stopped item. Troubleshoot the NetWorker software 33