Legato Win Installation

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

EMC® NetWorker™

Release 7.3.2Microsoft Windows Version

INSTALLATION GUIDEP/N 300-003-653

REV A01

EMC NetWorker Release 7.3.2, Microsoft Windows Version, Installation Guideii

Copyright © 1998 - 2006 EMC Corporation. All rights reserved.Published 2006

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.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

Contents

Preface ............................................................................................................................................................... vii

Chapter 1 Introduction About the NetWorker product ........................................................................................ 1-2

NetWorker client......................................................................................................... 1-2NetWorker storage node............................................................................................ 1-2NetWorker server ....................................................................................................... 1-3NetWorker Management Console............................................................................ 1-3NetWorker License Manager .................................................................................... 1-3

Supported devices............................................................................................................. 1-4 Enabler codes ..................................................................................................................... 1-4

Chapter 2 Updating the Software Updating to NetWorker 7.3.2........................................................................................... 2-2

Upgrading NetWorker software (client, server and storage node)..................... 2-2Upgrading NetWorker Modules from a previous release .................................... 2-3Upgrading from a different bit version of NetWorker software (32-bit, 64-bit) 2-3

Maintaining a NetWorker software installation ........................................................... 2-4Changing a NetWorker software (client, storage node, server) installation...... 2-4Repairing a NetWorker software installation......................................................... 2-5Repair a NetWorker Management Console installation ....................................... 2-5Relocating a NetWorker software installation........................................................ 2-6

Chapter 3 Installing the Software Software installation roadmap........................................................................................ 3-2 Software installation requirements................................................................................. 3-2

General requirements ................................................................................................. 3-2TCP/IP requirements ................................................................................................. 3-3NetWorker client requirements ................................................................................ 3-3NetWorker server requirements ............................................................................... 3-4Storage node requirements........................................................................................ 3-4Storage device requirements ..................................................................................... 3-4Console server software requirements .................................................................... 3-5Estimating the space required for the Console database information ................ 3-7

Installing the NetWorker software ................................................................................. 3-7Task 1: Access the NetWorker installation files ..................................................... 3-7Task 2: Install the NetWorker software (client, server, storage node) ................ 3-8Task 3: Install the Console software......................................................................... 3-9

Contents iii

Contents

EMC NetWorker Release 7.3.2, Microsoft Windows Version, Installation Guideiv

Verifying the installation ................................................................................................ 3-11Task 1: Start the Console for the first time ............................................................ 3-11Task 2: Add a NetWorker server to the Console server...................................... 3-12Task 3: Configure a device....................................................................................... 3-12Task 4: Test the NetWorker software installation ................................................ 3-14

Uninstalling the NetWorker software .......................................................................... 3-14

Chapter 4 MSCS Installation Cluster terminology .......................................................................................................... 4-2 Installation requirements ................................................................................................. 4-2 Updating NetWorker software........................................................................................ 4-3 NetWorker server installation ......................................................................................... 4-3

Installing a NetWorker server for noncluster mode .............................................. 4-3Installing a NetWorker server for cluster mode..................................................... 4-4

Configuring a backup device for the NetWorker virtual server ................................ 4-9Defining a cluster node as a storage node............................................................. 4-10

Moving the NetWorker server to another node.......................................................... 4-10 Registering NetWorker licenses for cluster failover................................................... 4-11 Restarting the NetWorker server services ................................................................... 4-11 Installing only the NetWorker client software in a cluster........................................ 4-11 Removing NetWorker software from MSCS............................................................... 4-12

Uninstall NetWorker software from all the nodes in the cluster ....................... 4-12Uninstalling NetWorker software from only one node in the cluster .............. 4-12

Troubleshooting NetWorker software in the MSCS environment ........................... 4-13NetWorker virtual server fails to start nsrmmd................................................... 4-13NetWorker server fails to back up a virtual cluster client .................................. 4-13NetWorker services fail to start in an MSCS environment ................................. 4-14

Chapter 5 EMC AutoStart Installation Software installation roadmap ........................................................................................ 5-2 Installation requirements ................................................................................................. 5-2

Software requirements ............................................................................................... 5-2Hardware requirements............................................................................................. 5-2Configuration options ................................................................................................ 5-3System information requirements ............................................................................ 5-3

Updating NetWorker software in a EMC AutoStart environment ............................ 5-4 Installing a NetWorker virtual server............................................................................. 5-4

Task 1: Ensure that the EMC AutoStart software is installed............................... 5-5Task 2: Install the NetWorker software ................................................................... 5-5Task 3: Promote at least one secondary cluster node to primary ........................ 5-5Task 4: Create the resource that will become the managed shared disk ............ 5-5Task 5: Define the NetWorker server as highly available..................................... 5-6Task 6: Configure the NetWorker virtual server.................................................... 5-7Task 7: Configure clients of the NetWorker cluster server ................................... 5-8Task 8: Register NetWorker licenses for cluster server failover........................... 5-9

Installing only the NetWorker client software in a cluster.......................................... 5-9Task 1: Install the NetWorker cluster client software.......................................... 5-10Task 2: Configure NetWorker client software as a highly available ................. 5-10

Configuring the NetWorker virtual server with a backup device ........................... 5-11 Troubleshooting............................................................................................................... 5-11

Setting the shutdown wait timeout values............................................................ 5-11NetWorker virtual server fails to start nsrmmd................................................... 5-12NetWorker server fails to back up a virtual cluster client .................................. 5-12Rolling back changes to the cluster configuration file......................................... 5-13

Uninstalling the NetWorker software .......................................................................... 5-13

Contents

Chapter 6 Licensing and Enabling the Software How NetWorker software is licensed............................................................................. 6-2 The evaluation process ..................................................................................................... 6-2

Evaluating a new installation.................................................................................... 6-2Evaluating features on an existing installation....................................................... 6-2

The licensing process ........................................................................................................ 6-3Task 1: Enter the license enabler code...................................................................... 6-4Task 2: Obtain an authorization code ...................................................................... 6-4Task 3: Enter the authorization code........................................................................ 6-5

Multiplatform licensing.................................................................................................... 6-6Update enablers .......................................................................................................... 6-7Additional licenses ..................................................................................................... 6-7

Managing NetWorker licenses ........................................................................................ 6-8

Contents v

Contents

EMC NetWorker Release 7.3.2, Microsoft Windows Version, Installation Guidevi

Preface

As part of its effort to continuously improve and enhance the performance and capabilities of the EMC NetWorker product line, EMC periodically releases new versions of its hardware and software. Therefore, some functions described in this guide may not be supported by all revisions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

AudienceThis guide is part of the NetWorker documentation set, and is intended for use by system administrators during the installation of NetWorker software.

Readers of this guide are expected to be familiar with the following software:

◆ EMC NetWorker software

◆ Microsoft Windows software

OrganizationHere is a list of where information is located in this guide.

◆ Chapter 1, “Introduction,” provides a description of NetWorker and supporting software, including features, components, and functions.

◆ Chapter 2, “Updating the Software,”describes how to update the NetWorker software from a previous release.

◆ Chapter 3, “Installing the Software,” describes how to access and install the NetWorker software from the distribution media.

◆ Chapter 4, “MSCS Installation,” describes how to access and install the NetWorker software from the distribution media in an MSCS cluster environment.

◆ Chapter 5, “EMC AutoStart Installation,” describes how to access and install the NetWorker software from the distribution media in an EMC AutoStart cluster environment.

◆ Chapter 6, “Licensing and Enabling the Software,” describes how to license and enable the NetWorker software.

Preface vii

Preface

Related documentationFor more information about EMC NetWorker software, refer to this documentation:

◆ NetWorker, Release 7.3.2, Administration Guide

◆ NetWorker, Release 7.3.2, Release Notes

◆ NetWorker, Release 7.3.2, Installation Guides

◆ EMC Information Protection Software Compatibility Guide

Conventions used in this guideEMC uses the following conventions for notes, cautions, warnings, and danger notices.

Note: A note presents information that is important, but not hazard-related.

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment. The caution may apply to hardware or software.

Typographical conventionsEMC uses the following type style conventions in this guide:

bold • User actions (what the user clicks, presses, or selects)• Interface elements (button names, dialog box names)• Names of keys, commands, programs, scripts, applications, utilities, processes,

notifications, system calls, services, applications, and utilities in text

italic • Book titles• New terms in text• Emphasis in text

Courier • Prompts • System output • Filenames • Pathnames• URLs • Syntax when shown in command line or other examples

Courier, bold • User entry• Options in command-line syntax

Courier italic • Arguments in examples of command-line syntax• Variables in examples of screen or file output• Variables in pathnames

<> Angle brackets for parameter values (variables) supplied by user.

[] Square brackets for optional values.

| Vertical bar symbol for alternate selections. The bar means or.

... Ellipsis for nonessential information omitted from the example.

EMC NetWorker Release 7.3.2, Microsoft Windows Version, Installation Guideviii

Preface

Where to get helpFor information about software patches, technical documentation, support programs, sales, and licensing, go to:

http://softwaresupport.EMC.com

Your commentsComments and suggestions about our product documentation are always welcome.

To provide feedback:

1. Go to:


2. Click the Documentation link.

3. Click the Technical Publications Customer Survey link at the top of the page to comment on a particular guide.

Preface ix

http://softwaresupport.emc.com


Preface

EMC NetWorker Release 7.3.2, Microsoft Windows Version, Installation Guidex

1

This chapter provides background information on EMC NetWorker software and supported devices.

It includes these sections:

◆ About the NetWorker product.................................................................................................1-2 ◆ Supported devices .....................................................................................................................1-4◆ Enabler codes .............................................................................................................................1-4

Introduction

Introduction 1-1

Introduction

About the NetWorker productThe EMC® NetWorker™ product is a suite of storage management software that provides backup, recovery, and other services to computers 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 of CD-ROMs that contains the software and electronic documentation for several related EMC products.

◆ As a downloadable archive file from the EMC website.

The NetWorker product has five major components:

◆ NetWorker client

◆ NetWorker storage node

◆ NetWorker server

◆ NetWorker Management Console

◆ NetWorker License Manager

NetWorker clientThe NetWorker client software communicates with the NetWorker server and provides recover and ad hoc (manual) backup functionality. The NetWorker client software is installed on all computers that are backed up to the NetWorker server.

NetWorker clients do not have to be running the same operating system as the NetWorker server. However, to back up clients running other operating systems, the NetWorker server must have an EMC ClientPak® enabler for that client. For example, in order for the NetWorker server for IRIX to back up NetWorker clients running another operating system, a separate ClientPak enabler must be purchased and entered for that operating system.

NetWorker storage nodeData can be backed up directly to devices attached to a NetWorker server, or to a NetWorker storage node. A storage node controls storage devices such as tape drivers, autochangers, and silos.

Storage nodes depend on the NetWorker server for these functions:

◆ Control over which clients use the storage node’s devices for backups

◆ License management

◆ Management of the client file indexes that track each client’s data

◆ Management of the media database that tracks the data contained on each volume

NetWorker storage nodes and the NetWorker server can use different operating systems. To use a NetWorker storage node on a Linux operating system with a NetWorker server running another operating system, the storage node’s enabler on the server must be of the same edition as the base enabler for the NetWorker server.

EMC NetWorker Release 7.3.2, Microsoft Windows Version, Installation Guide1-2

Introduction

NetWorker server

The NetWorker server software provides control and scheduling for NetWorker operations. It enables you to:

◆ Enter the enabler licenses for the NetWorker server and all the functions the NetWorker server controls, such as autochanger modules, additional client connections, and ClientPak licenses.

◆ Define the clients, devices, and media that the NetWorker server controls.

◆ Define the schedules for backups and other operations.

◆ Monitor the results of backups and other operations.

◆ Manage the client file indexes that track each client’s data.

◆ Manage the media database that tracks the data contained on each volume.

NetWorker Management ConsoleAll NetWorker servers and clients are managed from the NetWorker Management Console. The Console replaces the NetWorker Administration program (nwadmin) which is no longer available.

The Console provides reporting, managing, and monitoring capabilities for all NetWorker servers and clients. The Console must in be installed on an AIX, HP-UX, Linux, Solaris, or Microsoft Windows host in order to administer NetWorker servers.

The Console is accessed through a graphical interface that can be run from from only an AIX, HP-UX, Linux, Solaris, or Windows host that has a web-enabled browser with the specified version of Java Runtime environment configured. Multiple users can access the Console server concurrently from different browser sessions. A computer that hosts the web-enabled browser can also be a NetWorker client, server, or storage node.

You must install the NetWorker Management Console software on one computer in your datazone to manage and monitor the NetWorker server. Only one installation of the Console is required to manage multiple NetWorker servers and to take full advantage of the Console’s consolidated reporting feature.

NetWorker License ManagerThe NetWorker License Manager provides a central location for managing the licenses of all the NetWorker clients and servers. Instead of managing licenses separately, all NetWorker licenses can be maintained from a single computer. Installation of the NetWorker License Manager is an option when installing the NetWorker software.

For more information about the NetWorker License Manager, refer to the NetWorker License Manager Installation and Administration Guide and the NetWorker License Manager Release Notes.

About the NetWorker product 1-3

Introduction

Supported devicesNetWorker software supports a variety of media types and devices, either stand-alone or in an autochanger or silo tape library. Devices can be attached to a NetWorker server or a designated storage node. To obtain the latest list of supported devices, refer to the EMC Information Protection Software Compatibility Guide.

A nonrewinding device must be used for NetWorker backups. The pathnames for these devices must follow the Berkeley Software Distribution (BSD) semantic rules, for example, /dev/rmt/0mbn. The b in the pathname satisfies the semantics requirement. If a file type device is used, enter it as a directory path (the same as for other device types) rather than as just a filename.

The term autochanger refers to a variety of backup devices:

◆ Autoloader

◆ Carousel

◆ Datawheel

◆ Jukebox

◆ Library

◆ Near-line storage

Enabler codesEnabler codes (licenses), which activate the functionality of NetWorker software and other EMC software, are sold separately. For information, see Chapter 6, “Licensing and Enabling the Software.”


2

This chapter explains how to upgrade, maintain, or uninstall NetWorker software.

It includes the following sections:

◆ Updating to NetWorker 7.3.2 ...................................................................................................2-2◆ Maintaining a NetWorker software installation....................................................................2-4

Note: When updating to NetWorker release 7.3.2 or later format, there is no way to revert to a previous release of the NetWorker software. It is a one-way conversion.

Updating the Software

Updating the Software 2-1


Updating to NetWorker 7.3.2When updating to NetWorker release 7.3.2 or later, there is no way to revert to a previous release of the NetWorker software. It is a one-way conversion.

The NetWorker Management Console software does not support direct upgrade, which means the previous installed version must be removed before the new version can be installed. Before upgrading, make notes of the previous database location and port numbers used before removing the previous installation. Also, select the partial remove option to leave the Console database on the machine for database upgrade.

Note: NetWorker release 7.3.2 supports direct upgrades from NetWorker release 6.x and later. If you are currently using NetWorker software earlier than release 6.x, you must first upgrade to release 6.x or later before upgrading to NetWorker release 7.3.2.

When you upgrade from a previous NetWorker release, NetWorker is automatically installed in the existing location. For information about the default installation location, see “Supported devices” on page 1-4. For information about changing the location during an upgrade, see “Relocating a NetWorker software installation” on page 2-6.

The following options are not supported during an upgrade:

◆ Changing the installation type (for example, from client to server)

◆ Editing the list of NetWorker servers that are allowed to access the computer

◆ Installing NetWorker License Manager

You can, however, make any of these changes after the upgrade. For instructions, see “Maintaining a NetWorker software installation” on page 2-4.

Upgrading NetWorker software (client, server and storage node)

Note: A NetWorker release 7.3.2 storage node is not compatible with an earlier NetWorker server earlier than release 7.3. Update the NetWorker servers before updating a storage node.

To upgrade NetWorker software to release 7.3.2:

1. Verify that the target computer satisfies the requirements. For details, see “Software installation requirements” on page 3-2.

2. Log on with administrator privileges to the target computer.

3. Ensure that all NetWorker programs are stopped.

4. Access the installation files. For instructions, see “Task 1: Access the NetWorker installation files” on page 3-7.

5. Double-click the setup.exe file. Skip this step if Autorun started the installation automatically.

The Setup program detects the existing installation and automatically runs in update mode.

6. In the Welcome to NetWorker and NetWorker Management Console Installation page, select Install NetWorker.

7. In the Welcome to NetWorker Update dialog box, click Next.

8. In the Ready to Update dialog box, click Update.



9. In the NetWorker Server Selection page, select the NetWorker servers that can perform backups and directed recoveries for this client:

• To add a NetWorker server that is not listed in the Available Servers list, type the name of the server in the Enter a server name text box and click Add.

• To browse for available NetWorker servers, click Update List. You can select a NetWorker server from the Available Servers list.

• To add or remove NetWorker servers from the Available Servers list to the Selected Servers list, use the arrow buttons.

10. Click Finish when the upgrade is complete.

Note: If you are updating NetWorker software on a computer running Windows XP Professional, Windows 2000 or 2003, at the end of the setup process you are prompted to run the Change Journal Manager. For information about configuring NetWorker software to use the Windows Change Journal, refer to the NetWorker Administration Guide.

Upgrading NetWorker Modules from a previous releaseAfter updating to NetWorker release 7.3.2 from a release 6.x, NetWorker Modules must be reinstalled. Additionally, you may have to make minor changes to the Users attribute of the User Group resource (within the Users group) to ensure successful backups.

Note: If updating to NetWorker release 7.3.2 from release 7.0, NetWorker Modules do not need to be reinstalled.

For information, refer to the appropriate EMC NetWorker Module documentation.

Upgrading from a different bit version of NetWorker software (32-bit, 64-bit)

The following procedure is only required if updating from a 32-bit installation of NetWorker software to a 64-bit version or vice-versa.

To update the NetWorker software:

1. Use the NetWorker software to back up the client file index and the media database. For instructions, refer to the NetWorker Administration Guide.

2. Uninstall NetWorker software. For instructions, see “Uninstalling the NetWorker software” on page 3-14.

3. Delete the existing client file index and the media database.

4. Install the new version NetWorker software. For instructions, see “Installing the NetWorker software” on page 3-7.

5. Perform a bootstrap recovery of the saved NetWorker client file index and the media database. For detailed instructions, refer to the NetWorker Administration Guide.

Updating to NetWorker 7.3.2 2-3


Maintaining a NetWorker software installationAfter NetWorker software is installed, you can run the Setup program to perform the following maintenance tasks:

◆ Change the installation type (for example, from client to server), edit the servers list, add the NetWorker License Manager, add or remove the Console software. For instructions, see “Changing a NetWorker software (client, storage node, server) installation” on page 2-4.

◆ Replace missing or corrupted program files. For instructions, see “Repairing a NetWorker software installation” on page 2-5.

Changing a NetWorker software (client, storage node, server) installationTo change a NetWorker installation:


2. Stop all NetWorker programs.




The Setup program detects the existing NetWorker installation and automatically runs in maintenance mode.

6. In the Welcome to NetWorker Maintenance page, click Next.

7. In the Maintenance Type page, select Change and click Next.

8. In the Installation Type and Location page, make the following selections and click Next:

• Select the Client, Storage Node, or Server and Client option.

• To install the NetWorker software in a location other than the default location, click Change and specify the installation path.

• To install the License Manager software, select the Include EMC License Manager option.

Note: Only one installation of the NetWorker License Manager is required on a network. Do not install the NetWorker License Manager on any computer other than a primary or backup license server.

The NetWorker License Manager is not supported on Windows NT 4.0. For information, refer to the NetWorker License Manager Installation and Administration Guide.

9. In the Ready to Change page, review the setting and click Change to accept the settings.







Note: If the Selected Servers list is left empty, any NetWorker server can perform backups and directed recoveries of this computer’s data. This might affect the security of your data. To change this list after the installation, see “Maintaining a NetWorker software installation” on page 2-4.

11. In the NetWorker Setup Complete page, select Finish.

Note: The Setup program stops the NetWorker services if necessary, makes the requested changes, and then restarts the NetWorker services.

Repairing a NetWorker software installation

To repair an installation in which program files are corrupted or missing:


2. Ensure that all NetWorker programs are stopped.





6. In the Welcome to NetWorker Maintenance page, click Next.

7. In the Maintenance Type dialog box, select Repair and click Next.

8. In the Ready to Repair dialog box, click Repair.


Note: The Setup program stops the NetWorker services if necessary, replaces any corrupted or missing files, and then restarts the NetWorker services.

Repair a NetWorker Management Console installationTo repair an installation in which program files are corrupted or missing:


2. Verify that NetWorker Remote Exec Service is installed and running.

3. Stop all NetWorker programs.


5. Double-click the setup.exe file located. Skip this step if Autorun started the installation automatically.

Maintaining a NetWorker software installation 2-5


6. In the Welcome to NetWorker and NetWorker Management Console Installation page, select Install NetWorker Management Console.


7. In the Welcome to NetWorker Management Console Maintenance page, click Next.

8. In the Maintenance Type dialog box, select Repair and click Next.

9. In the Ready to Repair dialog box, click Repair.

10. In the Configuration Options page, indicate the Database Destination path, the IP port numbers to use for the embedded HTTP server, and the Client Service port:

• To change the default database path, select Change.

• To use the default port numbers, type 9000 for the HTTP server and 9001 for the Client Service port.

• To use different port numbers, type the new port numbers (between 1024 and 49151).

Note: Port 2638 is reserved by the Console software as it uses the TDS protocol to communicate with the database.

11. In the Customer Database Maintenance Options page, select the appropriate option.

12. In the Product Setup page, review the status of the installed software and the configuration summary and click Next.


Note: The Setup program stops the NetWorker services if necessary, replaces any corrupted or missing files, and then restarts the NetWorker services.

Relocating a NetWorker software installation

To change the location of an existing NetWorker software installation:


2. Remove the NetWorker software from its current location, making sure to retain the metadata. For instructions, see “Uninstalling the NetWorker software” on page 3-14.

Note: If you are removing a NetWorker software release earlier than 7.3.2, refer to the NetWorker Installation Guide for that release, and follow the instructions for a partial uninstallation.

3. Create the path to the new NetWorker installation location. For example:

E:\emc

4. Move the nsr directory from the previous location to the new location. For example, from:

C:\Program Files\emc\nsr to E:\emc\nsr.

5. Install the NetWorker software in the new location. For instructions, see “Installing the NetWorker software” on page 3-7.

6. During the installation, when the Installation Type and Location dialog box appears, click Change and specify the new location. For example:

E:\emc\nsr


3

This chapter explains how to install, update, or uninstall NetWorker software.


◆ Software installation roadmap ................................................................................................3-2◆ Software installation requirements .........................................................................................3-2◆ Installing the NetWorker software..........................................................................................3-7◆ Verifying the installation ........................................................................................................3-11◆ Uninstalling the NetWorker software...................................................................................3-14

Installing the Software

Installing the Software 3-1


Software installation roadmapThe following roadmap provides an overview of the installation tasks:

1. Ensure that all installation requirements are satisfied, see “Software installation requirements” on page 3-2.

2. Access the installation files, see “Task 1: Access the NetWorker installation files” on page 3-7.

3. Install the NetWorker software. For details, see:

• “Task 2: Install the NetWorker software (client, server, storage node)” on page 3-8

• “Task 3: Install the Console software” on page 3-9

Note: You must install the Console server software on one computer in your data zone to manage and monitor the NetWorker server. Only one installation of the Console server is required to manage multiple NetWorker servers and to take full advantage of the Console’s consolidated reporting feature.

4. Test the NetWorker software. For details, see “Verifying the installation” on page 3-11.

5. Enable and register the NetWorker software. For details, see Chapter 6, “Licensing and Enabling the Software.”

Software installation requirementsThe system requirements differ for each NetWorker installation type. For details, see:

◆ “General requirements” on page 3-2

◆ “NetWorker client requirements” on page 3-3

◆ “NetWorker server requirements” on page 3-4

◆ “Storage node requirements” on page 3-4

◆ “Storage device requirements” on page 3-4

◆ “Console server software requirements” on page 3-5

General requirements

The following are general NetWorker software installation requirements:

◆ Do not include an underscore character ( _ ) in Windows computer names.

◆ If NetWorker software is installed on a File Allocation Table (FAT) partition, do not disable long name support.

◆ Microsoft Windows Installer 2.0 (msiexec.exe) is included with the NetWorker release 7.3.2 software. If the target computer has an older version of the Windows Installer, it will be updated and a reboot will be required during the NetWorker software installation or update.

◆ InstallShield requires that the entire installation program must be put into memory, even if you only intend to install a single NetWorker software component.



Note: NetWorker software does not support locales (defined by the operating system) or code sets that remap special characters. Depending on the filesystem, special characters may include the slash (/), backslash (\), colon (:), or period(.). For example, De_DE.646 is an unsupported locale. For more information, refer to the NetWorker Administration Guide.

TCP/IP requirementsThe following are requirements for TCP/IP network communication when using NetWorker software:

◆ All NetWorker server, storage node, and client host computers must have TCP/IP installed and configured.

◆ The NetWorker server hostname must be added to the Domain Name System (DNS) database for the network, or to the local hosts file located in %SystemRoot%\system32\drivers\etc.

Note: If DNS is used, reverse lookup must be correctly configured.

◆ If the NetWorker server host is a Dynamic Host Configuration Protocol (DHCP) client, it must have a reserved address.

◆ If DHCP with dynamic addresses is used, DHCP must be synchronized with DNS.

◆ The NetWorker server’s TCP/IP hostname and Windows computer name must be the same.

NetWorker client requirements

NetWorker client software is supported on the following Microsoft Windows operating systems:

◆ Windows NT 4.0 with Service Pack 6 installed (Workstation, Server, and Enterprise Editions)

◆ Windows 2000 with the latest service pack installed (Server, Advanced Server, Enterprise Server, and Datacenter Editions)

◆ Windows 2000 (32-bit version of the Professional Edition)

◆ Windows XP (32-bit and 64-bit versions of the Professional Edition)

◆ Windows Server 2003 (32-bit versions of the Standard, Web, Enterprise, and Datacenter Editions)

◆ Windows Server 2003 (64-bit version of Enterprise and Datacenter Editions)

Note: For NetWorker clients on the same hardware platform as the NetWorker server, use the same installation files to install the clients and server. For NetWorker clients on other hardware platforms, you must purchase and install the NetWorker client software separately. For information, contact EMC or an Authorized EMC Reseller.

Software installation requirements 3-3


NetWorker server requirements

NetWorker server software is supported on the following Microsoft Windows operating systems:


◆ Windows Server 2003 (32-bit and 64-bit versions of Standard, Web, Enterprise, and Datacenter Editions)

The NetWorker server host computer must have enough disk space for the NetWorker client file indexes and the media database. For example, backing up a million files requires approximately 80 MB of disk space for client file indexes and the media database.


Storage node requirementsNetWorker storage node software is supported on the following Microsoft Windows operating systems:


◆ Windows Server 2003 (32-bit and 64-bit versions of the Standard, Web, Enterprise, and Datacenter Editions)

Note: Microsoft renamed the operating system formerly known as Windows .NET to Windows Server 2003. For information about NetWorker storage node support on Windows 2003, refer to the NetWorker Release Notes.

NetWorker software also supports the use of file type and advanced file type devices. For details, refer to the NetWorker Administration Guide.

Storage device requirementsYou must install one or more storage devices prior to installing the NetWorker server software. For a current list of the supported devices, refer to the EMC Information Protection Software Compatibility Guide.

Note: You must use a nonrewinding device for NetWorker backups. NetWorker software writes a filemark on the volume at the end of each backup. When the next backup occurs, NetWorker software appends data to the volume based on the position of the filemark. If a device automatically rewinds the tape, the filemark position is lost and the next backup overwrites existing data. In that case, you would not be able to recover the previous backup data.



Console server software requirements

The general requirements for installing Console software include:

◆ An installed and licensed NetWorker version 7.3.2 client.

◆ A Java Runtime Environment (JRE), which is required in order to do the following:

• Support the command line reporting feature.

• Download the Console client and display the user interface.

The JRE version must be 1.4.2_11 or later, up to–but not including–version 1.5.


System requirements for the Console server and database

Table 3-1 on page 3-5 provides a list of system requirements for installing the Console server and database.

Table 3-1 Console server system requirements

System feature Requirement

Processor and RAM Minimum: 500 MHz with 128 MB of RAM, 512 MB to run reportsAs the number of servers being monitored increases, increase the computer’s capabilities.For 50 servers: Dual 500 MHz with no less than 192 MBFor 100 servers: Dual 800 MHz with no less than 256 MBFor 200 servers: Dual 1.3 GHz with no less than 512 MB

Operating system One of the following Microsoft Windows operating systems:2000, with SP42003, 32-bit

Software The following programs must already be installed and running:NetWorker client, release 7.3.2 or later.NetWorker Remote Exec service must be installed and running. If the service is stopped, the Setup Wizard issues an error message.

Java Runtime Environment JRE starting from version 1.4.2 or later, up to but not including 1.6. This is required to run the command line reporting feature on the Console server host.

Browsers One of the following:Microsoft Internet Explorer 5.5 or 6.x on the supported Microsoft Windows platforms.Netscape Communicator 4.76 (or later 4.7x version) or 7.x on the supported Microsoft Windows platforms.

Available disk space Microsoft Windows Server: 220 MB + x, where: x is a buffer of disk space for the Console database. For more information, see “System requirements for the Console client” on page 3-6.

Software installation requirements 3-5


System requirements for the Console clientAlthough the Console client does not need to be installed separately, the JRE which includes Java Web Start must be installed in order to download and run the program properly. Installing the JRE on the system requires administration privileges. When connecting to the Console server for the first time, there is a prompt to download the Console client application.

Table 3-2 on page 3-6 provides a list of system requirements for installing the Console client.

Estimating the size of the Console databaseThe Console server collects data from the NetWorker servers in the enterprise, and stores the data in its local Console database. By default, the database is installed on the local file system with the most available space. Console integrates and processes this information to produce reports that facilitate trend analysis, capacity planning, and problem detection. For information about reports, refer to the NetWorker Administration Guide.

To store the collected data, allocate sufficient disk space for the Console database. Several factors affect the amount of disk space required:

◆ The number of NetWorker servers monitored for the reports.

◆ The number of savegroups run by each of those servers.

◆ The frequency with which savegroups are run.

◆ The length of time report data is saved (data retention policies).

Note: Since the amount of required disk space is directly related to the amount of historical data stored, the requirements can vary greatly, on average between 0.5 GB and several GB. Allow for this when planning hardware requirements.

Table 3-2 Console client system requirements

System feature Requirement

Operating system One of the following:Microsoft Windows 2000, with SP4Microsoft Windows 2003, 32-bitMicrosoft Windows XP with SP1

Java Runtime Environment JRE starting from version 1.4.2, up to but not including 1.6.

Browsers One of the following:Microsoft Internet Explorer 5.5 or 6.x on the supported Microsoft Windows platformsNetscape Communicator 4.76 (or later 4.7x version) or 7.x on the supported Microsoft Windows platforms

Available disk space Console client: 5 MBJRE with Web Start: 50 MB

RAM A minimum of 512 MB to run reports

Graphics card Must support display of both:At least 16-bit color (at least 65,000 colors)Screen resolution of at least 1024 x 768



Estimating the space required for the Console database information

Use the formula presented in Table 3-3 on page 3-7 to estimate the space needed for different types of data and to estimate the total space required.

Installing the NetWorker softwareThe following sections explain how to access and install the NetWorker software:

◆ “Task 1: Access the NetWorker installation files” on page 3-7

◆ “Task 2: Install the NetWorker software (client, server, storage node)” on page 3-8

◆ “Task 3: Install the Console software” on page 3-9

Task 1: Access the NetWorker installation files

The NetWorker software can be accessed from a local CD-ROM or from the EMC website.

From a local CD-ROM

Note: The 32-bit and 64-bit versions of the NetWorker software are distributed on separate CD-ROMs.

To access NetWorker installation files on a local CD-ROM:

1. Log on with administrator privileges where the NetWorker software is being installed.

2. Insert the NetWorker software CD-ROM into the computer’s CD-ROM drive.

3. If Autorun is enabled, the NetWorker software installation screen appears automatically. Perform the following:

a. Select Install NetWorker Release 7.3.2 software.

b. In the File Download dialog box, select Run this program from its current location. Do not select Save this program to disk.

c. If a Security Warning appears, click Yes to continue.

Table 3-3 Estimating space requirements for Console database information

To estimate the total space required for Multiply

By the number of NetWorker servers

By the number of weeks in the The results indicate

save set media database information

weekly amount of save sets

monitored by the Console server

save set output policy

The length of time that a save set took to run successfully. The results also identify the number of files that were backed up, and how much data was saved during the operation.

save set output weekly amount of output messages


save set output retention policy

The number of save set output describes how many groups and save sets were attempted and their success or failure.

savegroup completion data

weekly amount or savegroups


completion data retention policy

All save output data that could be used to troubleshoot backup problems.

Installing the NetWorker software 3-7


4. If Autorun is disabled, change directories to the appropriate location:

• nw732_win_x86 (to install on a 32-bit computer)

• nw732_win_ia64 (to install on a 64-bit computer)

From the websiteTo access the installation software from the EMC website:

1. Log on with administrator privileges where the NetWorker software is being installed.

2. Create a temporary folder to download and extract the evaluation software.

3. Go to the EMC Software CustomerNet Downloads portal (http://softwaresupport.EMC.com) and navigate to the appropriate content management download site.

4. Download the evaluation software to the temporary folder and change to that folder.

5. Extract the downloaded file.

Task 2: Install the NetWorker software (client, server, storage node)This section provides instructions for installing the following software:

◆ NetWorker client

◆ NetWorker storage node

◆ NetWorker server

◆ NetWorker License Manager

Note: You must install the Console server software on one computer in your data zone to manage and monitor the NetWorker server. Only one installation of the Console server is required to manage multiple NetWorker servers and to take full advantage of the Console’s consolidated reporting feature. For details, see “Task 3: Install the Console software” on page 3-9.

You can install the NetWorker License Manager with any of the NetWorker software components. The NetWorker client must be installed before the NetWorker Management Console software.

To install NetWorker software:

1. Verify that the target computer satisfies the requirements. For details, see “Software installation requirements” on page 3-2.

2. Log on with administrator privileges to the target computer for the NetWorker software installation.



5. In the Customer Information page, fill in the appropriate information and click Next.

6. In the Installation Type and Location page, make the following selections and click Next:

• Select the Client, Storage Node, or Server and Client option.

• To install the NetWorker software in a location other than the default location, click Change and specify the installation path.

• To install the License Manager software, select the Include NetWorker License Manager option.




Note: Only one installation of the NetWorker License Manager is required on a network. Do not install the License Manager on any computer other than a primary or backup license server. The NetWorker License Manager product is not supported on Windows NT 4.0. For information, refer to the NetWorker License Manager Installation and Administrator’s Guide.

7. The installation program is ready to install. Review the settings and click Install.





Note: If the Selected Servers list is left empty, any NetWorker server can perform backups and directed recoveries of this computer’s data. This might affect the security of your data. To change this list after the installation, see “Maintaining a NetWorker software installation” on page 2-4.

If you are installing NetWorker software on a computer running Windows Server 2003, Windows XP Professional, or Windows 2000, at the end of the setup process you are prompted to run the Change Journal Manager. For information about configuring NetWorker software to use the Windows Change Journal, refer to the NetWorker Administration Guide.

Task 3: Install the Console software

You must install the Console server software on one computer in your data zone to manage and monitor the NetWorker server. Only one installation of the Console server is required to manage multiple NetWorker servers and to take full advantage of the Console’s consolidated reporting feature.

Note: The Console installation relies on the existence of several other components. Ensure that all of the installation prerequisites are met. For details, see “Console server software requirements” on page 3-5.

To install the Console:

1. In the Welcome to NetWorker and NetWorker Management Console Installation page, select Install NetWorker Management Console.

2. In the Welcome to NetWorker Management Console Installation page, click Next.

3. In the Customer Information page, fill in the appropriate information and click Next.

4. In the Installation Required JRE page, if you have not installed the JRE version 1.4.2_11 software, install it now and then click Next.

The JRE is required to run the Console reporting function:

• Select Install Java 2 Runtime Environment, SE v1.4.2_11 to install the JRE version 1.4.2_11 software.

• Select Skip JRE Installation to continue the installation without installing the JRE.

You are prompted to install the JRE when you first access the Console interface. This disables the command line reporting feature.

Installing the NetWorker software 3-9


5. In the Product Setup page, select the destination of the Console server (GST) server.

• To install the software in the default directory, click Next.

• To install the software in a different directory, click Change and navigate to or type a new destination.

Note: The estimated disk space required for the Console components is 220 MB. For details, see “System requirements for the Console client” on page 3-6.

If the Setup wizard detects that there is insufficient disk space to install the software, another dialog box appears listing the system’s local drives, and highlighting the drive with insufficient disk space. The list also displays disk size, available space, and required space, which allows the selection of an appropriate drive on which to continue the installation.

6. In the Configuration Options page, indicate the Database Destination path, the IP port numbers to use for the embedded HTTP server, and the Client Service port:

• To change the default database path, select Change.

• To use the default port numbers, type 9000 for the HTTP server and 9001 for the Client Service port.

• To use different port numbers, type the new port numbers (between 1024 and 49151).

Note: Port 2638 is reserved by the Console software as it uses the TDS protocol to communicate with the database.

7. Review the information in the Product Configuration summary window and click Next.

8. In the Ready to Install the Program window, click Install.

9. When the installation is complete, the NetWorker Management Console Setup Completed page appears.

The box shows where the install.log and gst.daemon logs can be viewed. It also gives the browser URL to use to start the Console software from any desktop.

a. Click the check box (the default is selected) to launch the client in the default browser immediately after exiting the InstallShield Wizard.

b. Click Finish to exit the InstallShield Wizard.

10. If the Console server and the NetWorker server are installed on separate hosts, you must add the Console administrator to the administrator lists of the monitored NetWorker server. This enables the the Console administrator to administer and monitor the target NetWorker server.

On the NetWorker server:

a. Specify the process owner of the Console service process.

If the Console server is on a:

– Windows host:nsraddadmin -u "user=SYSTEM, host=console_host"

– Linux, or Solaris only host:nsraddadmin -u "user=root, host=console_host"

b. Specify the Console administrator user:

nsraddadmin -u "user=administrator, host=console_host"

Where console_host is the Console server hostname.



Verifying the installationThis section provides information about testing and verifying the NetWorker software installation. To verify that the NetWorker software was installed properly, first connect to a NetWorker server and then test the software on a device.

This section includes the following procedures:

◆ “Task 1: Start the Console for the first time” on page 3-11

◆ “Task 2: Add a NetWorker server to the Console server” on page 3-12

◆ “Task 3: Configure a device” on page 3-12

◆ “Task 4: Test the NetWorker software installation” on page 3-14

Task 1: Start the Console for the first timeThese steps assume that the NetWorker software is installed and that all of the software and hardware requirements have been met on the computer that will access Console.

To open Console for the first time:

1. Start a web browser session.

2. Type the URL of the Console server:

http://server_name:http_service_port

where:

• server_name is the name of the computer where the Console server component was installed.

• http_service_port is the IP port for the embedded HTTP server. (The HTTP port is specified during installation. The default HTTP port is 9000.)

For example:

http://houston:9000

3. From the Welcome page, click Start.

4. From the Security Warning page, click Start to install and run NetWorker Management Console.

5. If JRE 1.4.2_11 was not already installed on the system, a prompt to install it appears. Follow the on-screen instructions to install JRE.

Once the JRE has been installed, the Java Web Start Desktop Integration dialog box displays.

6. Complete the Java Web Start Desktop Integration dialog box by selecting one of the following options:

• To place a shortcut on the desktop, click Yes.

• To decline having a shortcut placed on the desktop, click No.

• To have the option to decide later, click Ask Later.

7. In the NetWorker Management Console Login dialog box, type the user name and password.

Verifying the installation 3-11


Note: The default user is administrator and the default password for the administrator is “administrator”. For security purposes, this password should be changed during the first login session.

8. Click OK. The Console Window appears.

Starting the Console after the first timeAfter the Console has been started the first time, start it by using any of the following methods:

◆ Point the browser to the same URL as in “Task 1: Start the Console for the first time” on page 3-11.

◆ Double-click the NetWorker Management Console product name in the Java Web Start Application Manager.

◆ Double-click the desktop icon, if one was set up through the Java Web Start Application Manager.

Task 2: Add a NetWorker server to the Console serverTo add and select a NetWorker server:

1. Start the NetWorker Management Console software.

2. From the Console window, click Enterprise.

3. From the File menu, select New>Host.

4. Type a hostname and alias for the NetWorker server.

The NetWorker server appears in the right pane.

5. From the right pane, select the NetWorker server.

6. From the Enterprise menu, select Launch Application.

The Administration window is launched as a separate application.

If the server connection fails, refer to the server connectivity information in the NetWorker Administration Guide to troubleshoot the problem.

Task 3: Configure a deviceIf not already configured, you must configure a device before testing the NetWorker software.

You can configure one of the following devices:

◆ “Stand-alone tape device” on page 3-12

◆ “Stand-alone file or advanced file device” on page 3-13

◆ “Autochanger or silo” on page 3-13

Stand-alone tape deviceTo configure a stand-alone tape device:

1. In the server’s NetWorker Administration interface, click Devices.

2. From the left pane, select Storage Nodes.

3. Right-click the storage node to which the device is to be configured.



4. Select Scan for devices.

The Scan for Devices window appears.

5. From the list, select the storage node to be scanned.

6. Click Start Scan after filling in the requested information.

The newly detected device appears in the right pane.

7. From the right pane, select the new device to be configured.

8. From the Device menu, select Stand-alone Device Configuration>Configure drive.

9. From the Device menu, select Device Operations>Label.

The Label window appears.

10. Verify the information in the Label window and click OK.

Stand-alone file or advanced file deviceTo configure a stand-alone file or advanced files device:


2. From the left pane, select Devices.

3. From the File menu, select New.

The Create Devices window appears.

4. For the Name attribute, type the device path.

5. For the Media type attribute, select file or adv_file.

6. Click OK. The new device appears in the right pane.

7. From the right pane, select the new device.

8. From the Device menu, select Device Operations>Label.

The Label window appears.

9. Verify the information in the Label window and click OK.

Autochanger or siloTo configure a new library resource (autochanger or silo) to a storage node:


2. From the left pane, select Storage Nodes.

3. Right-click the storage node to which the device is to be configured.

4. Select Configure All Libraries.

5. Click Start Configuration after filling in the requested information.

6. Click Finish on the Configuration window, once the configuration has completed.

Verifying the installation 3-13


Task 4: Test the NetWorker software installation

Test a NetWorker installation by performing an adhoc (manual) back up of a file or folder. You can also use the NetWorker Client Configuration Wizard to configure a scheduled backup. For information about the wizard, refer to the NetWorker Administration Guide.

To test the NetWorker software on a stand-alone device:


2. Start the NetWorker nwbackup program.

The NetWorker nwbackup program provides a graphical interface through which ad hoc (manual) backups are performed. For general information about the NetWorker nwbackup program, see the NetWorker Administration Guide.

To start the NetWorker nwbackup program:

a. From the Administration window, select Start>NetWorker Backup.

The NetWorker Backup window appears.

b. From the NetWorker nwbackup program, select Launch Backup.

c. In the left pane of the Backup window, click the appropriate directory folder.

d. Select each directory and/or file you intend for manual backup by performing one of the following:

– Select the directory or file and click Mark. To clear an item, click Unmark.– Click the directory or file. When you mark a directory or file for backup, a check

mark appears next to that item.e. Click Start to begin the ad hoc backup.

The Backup Status dialog box displays the progress of the backup. When the NetWorker server has successfully finished the backup, the nwbackup program displays this (or a similar) message:

Backup completion time: 2-15-06 3:27p

Note: If the backup fails, an error message will appear. Error messages are also written to the NetWorker log file. If the test backup was not successfully completed, refer to the troubleshooting information in the NetWorker Administration Guide to determine the cause.

Uninstalling the NetWorker software

Note: Uninstall the NetWorker Management Console before uninstalling the rest of the NetWorker software.

To uninstall the NetWorker software from a host computer:


2. Stop all NetWorker programs and ensure that no other program, such as Windows Explorer, is accessing directories or files under NetWorker_install_path.

3. In the Windows Control Panel, select Add/Remove Programs.

4. In the Add/Remove Programs window, select NetWorker Management Console and click Remove.



Note: All of the NetWorker Management Console is removed except the JRE Java Web Start programs on which the Console is dependant. You can remove the Java programs through the Add/Remove Programs window separately.

5. In the Add/Remove Programs window, select NetWorker.

• Windows NT 4.0 — Click Add/Remove to launch the Setup program in Maintenance mode, then proceed to step 6.

• Windows Server 2003 and 2000 — Select one of the following options:

– Change — Launches the Setup program in Maintenance mode. If you select this option, proceed to step 6.

– Remove — Performs a partial uninstallation of the NetWorker software, leaving the NetWorker metadata. To perform a complete uninstallation, select the Change option. If you select Remove, you are prompted to confirm. Click Yes to perform the uninstallation.

6. If you select Change in the Add/Remove Programs window or are running Windows NT 4.0, the Welcome to NetWorker Maintenance dialog box appears. Click Next.

7. In the Maintenance Type dialog box, select Remove, and then click Next.

8. In the Ready to Remove dialog box, ensure that the Remove NetWorker Metadata option is set the way you want it, and then click Remove.

Note: For a complete uninstallation of the NetWorker software, select Remove NetWorker Metadata. By default, the Remove NetWorker Metadata check box is cleared to ensure that all of the NetWorker configuration files (such as client file indexes, media database, logs, and resource files) are retained for a future installation of the NetWorker software. This has the same effect as Partial Uninstallation in NetWorker releases prior to 7.3.2.

9. In the Ready to Remove dialog box, click Remove.

10. In the NetWorker Setup Complete dialog box, click Finish.

11. Remove the NetWorker Management Console shortcut icon from your desktop.

Uninstalling the NetWorker software does not remove the NetWorker Management Console shortcut icon from your desktop, it must be removed manually.

Note: If NetWorker License Manager is installed, it will be removed along with the other NetWorker software components. If you want to remove only the NetWorker License Manager and leave the other NetWorker components intact, disregard this procedure and see “Maintaining a NetWorker software installation” on page 2-4.

Uninstalling the NetWorker software 3-15

4

This chapter provides instructions for installing and configuring NetWorker software in a Microsoft Cluster Server (MSCS) environment.


◆ Cluster terminology ..................................................................................................................4-2◆ Installation requirements..........................................................................................................4-2◆ Updating NetWorker software ................................................................................................4-3◆ NetWorker server installation..................................................................................................4-3◆ Configuring a backup device for the NetWorker virtual server.........................................4-9◆ Moving the NetWorker server to another node ..................................................................4-10◆ Registering NetWorker licenses for cluster failover ...........................................................4-11◆ Restarting the NetWorker server services............................................................................4-11◆ Installing only the NetWorker client software in a cluster ................................................4-11◆ Removing NetWorker software from MSCS .......................................................................4-12◆ Troubleshooting NetWorker software in the MSCS environment ...................................4-13

For information on how to use NetWorker software in an MSCS environment, refer to the NetWorker Administration Guide. To perform a disaster recovery in an MSCS environment, refer to the NetWorker Disaster Recovery Guide.

MSCS Installation

MSCS Installation 4-1

MSCS Installation

Cluster terminologyEMC documentation uses the following cluster terminology:

◆ Node — A physical computer that is a member of a cluster.

◆ Private disk — A local disk on a cluster node. A private disk is not available to other nodes within the cluster.

◆ Shared disk — A disk that is shared by the cluster nodes.

◆ Failover — A means of ensuring application availability by relocating resources in the event of a hardware or software failure. Two-node failover capability allows operations to switch from one cluster node to the other. Failover capability can also be used as a resource management tool.

◆ Highly available application — An application installed in a cluster environment and configured for failover capability.

◆ Cluster-aware NetWorker server — A NetWorker server that can recognize cluster clients.

◆ Cluster client — A NetWorker client within a cluster; this can be either a virtual client, or a NetWorker Client resource that backs up the private data belonging to one of the physical nodes.

◆ Virtual client — A NetWorker Client resource that backs up data belonging to a highly available service or application within a cluster. Virtual clients can fail over from one cluster node to another.

◆ Stand-alone server — A NetWorker server running within a cluster, but not configured as a highly available application. A stand-alone server does not have failover capability.

◆ Virtual server — A NetWorker server configured to run as a highly available application. A virtual server can fail over from one cluster node to another.

Installation requirementsThis section specifies the software and hardware required to install and configure the NetWorker server or client software within an MSCS environment.

The MSCS software must be installed in a Microsoft certified hardware configuration. For the supported hardware list, refer to the Microsoft website.

All nodes must have one of the following installed:

◆ Microsoft Windows Server 2003, Standard, Enterprise, and Datacenter Editions, 32-bit version, two-node and four-node support, NetWorker server support

◆ Microsoft Windows Server 2003, Enterprise or Datacenter Edition, 32-bit version, two-node and four-node support, NetWorker client support

◆ Microsoft Windows 2000, Advanced Server or Datacenter with the latest service pack installed, two-node support, NetWorker server and client support

Note: If a Windows 2000 service pack earlier than SP3 is used, the Microsoft Gethostbyaddr( ) hotfix must be applied (available from Microsoft Product Support Services).

◆ Microsoft Windows NT 4.0 Server, Enterprise Edition, with MSCS and the latest service pack installed, NetWorker client support

◆ NetWorker software must always be installed on the private disk of a node.


MSCS Installation

Updating NetWorker software

Note: For more information about MSCS, and detailed procedures for using the Microsoft Management Console (MMC) Cluster Administrator snap-in, refer to the Microsoft documentation.

To update the NetWorker server software in an MSCS environment, on one node in the cluster:

1. In the Cluster Administrator program, take the NetWorker server cluster resource group offline.

2. Rename the <NetWorker_install_path>\bin\NetWorker.clustersvr file to <NetWorker_install_path>\bin\NetWorker.nocluster.

3. Update the NetWorker software. For details, see “Task 2: Install the NetWorker software (client, server, storage node)” on page 3-8.

4. Stop the NetWorker Backup and Recover Server service.

5. Open the NetWorker Backup and Recover Server Properties dialog box and change the startup type from Automatic to Manual.

6. Rename the NetWorker.nocluster file back to NetWorker.clustersvr.

7. On the second node of the cluster:

a. Rename the <NetWorker_install_path>\bin\NetWorker.clustersvr file to <NetWorker_install_path>\bin\NetWorker.nocluster.

b. Update the NetWorker software. For details, see “Task 2: Install the NetWorker software (client, server, storage node)” on page 3-8.

c. Stop the NetWorker Backup and Recover Server service.

d. Open the NetWorker Backup and Recover Server Properties dialog box and change the startup type from Automatic to Manual.

e. Rename the NetWorker.nocluster file back to NetWorker.clustersvr.

8. Bring the NetWorker server cluster resource group back online.

NetWorker server installation

Note: For more information about MSCS, and detailed procedures for using the MMC Cluster Administrator snap-in, refer to the Microsoft documentation.

Installing a NetWorker server for noncluster mode

To run the NetWorker server in noncluster mode within a cluster, the NetWorker server software must be installed as a stand-alone application. For installation instructions, see “Task 2: Install the NetWorker software (client, server, storage node)” on page 3-8.

Note: If you install NetWorker software without rebooting, running the cluster administrator for the first time can result in an error due to the cluster administrator extension DLL not being reloaded. If this error occurs, close the cluster administrator interface and run the following from the command line to reload the DLL: regsvr32 /u nsrdresex.dll

Updating NetWorker software 4-3

MSCS Installation

In this configuration, the NetWorker server software is usually installed on only one of the nodes in the cluster, and the NetWorker client software is installed on each node in the cluster.

The following rules apply:

◆ No failover of the NetWorker server takes place.

◆ The NetWorker server does not have to be configured as a resource managed by the cluster.

◆ The cluster service might or might not be running.

Installing a NetWorker server for cluster mode

The following sections explain how to configure a NetWorker server as a highly available application in MSCS:

◆ “Task 1: Install the NetWorker software” on page 4-4

◆ “Task 2: Create and register the NetWorker server cluster resource type” on page 4-5

◆ “Task 3: Verify the NetWorker server resource type” on page 4-5

◆ “Task 4: Create an MSCS group resource and required components resource” on page 4-5

◆ “Task 5: Bring the NetWorker server resource online” on page 4-7

◆ “Task 6: Configure the NetWorker virtual server” on page 4-8

◆ “Task 7: Configure clients on the NetWorker cluster server” on page 4-8

Task 1: Install the NetWorker softwareOn each node in the cluster, install NetWorker software in the same location on a private disk. Log on as Administrator to the node where you will install NetWorker software.

To install the software:

1. On one node in the cluster:

a. Complete the installation, see Chapter 3, “Installing the Software.”

b. From the NetWorker Administration window, note the host ID number for the appropriate cluster license.

The host ID is needed for the procedure “Registering NetWorker licenses for cluster failover” on page 4-11.

2. On the second node in the cluster:

a. Complete the installation, see Chapter 3, “Installing the Software.”

b. From the NetWorker Administration window, note the host ID number for the appropriate cluster license.

The host ID is needed for the procedure “Registering NetWorker licenses for cluster failover” on page 4-11.

For information about the installation location, see “Supported devices” on page 1-4.


MSCS Installation

Task 2: Create and register the NetWorker server cluster resource typeTo create and register the NetWorker Server cluster resource type:

1. Verify that NetWorker server software is installed in the same location on each node in the cluster.

2. On one of the cluster nodes, run the following command:

regcnsrd -c

This creates the NetWorker Server cluster resource type. It also registers the resource extension module so the NetWorker Server resource type can be managed from this node.

3. On the second cluster node, run the following command:

regcnsrd -r

If you are prompted with the following question, type Y:

Is this machine a member of the cluster on which you want to register Resource Extension for NetWorker Server resource?

This registers the resource extension module so the NetWorker Server resource type can be managed from this node.

Task 3: Verify the NetWorker server resource typeTo verify that a NetWorker Server resource type exists:

1. In the Cluster Administrator program, select the Resource Type folder under the Cluster Configuration folder.

2. Verify that NetWorker Server is listed as a resource type.

The resource type IP Address and Network Name define the NetWorker server’s virtual identity. The resource type Physical Disk is for the shared nsr directory.

Task 4: Create an MSCS group resource and required components resourceTo create the NetWorker virtual server Group resource:

1. In the Cluster Administrator program, select the Disk Group in the Groups folder containing the shared disk you wish to associate with the NetWorker server. You can rename this Disk Group to anything you like. In this procedure, the Disk Group was renamed to NetWorker Group.

Note: The NetWorker server must have its own dedicated Shared Disk resource; the cluster service quorum disk cannot be used for this.

2. Select the NetWorker Group (Disk Group) identified in the previous step and create the following resources for the NetWorker Group:

• “NetWorker IP address resource” on page 4-6

• “NetWorker network name resource” on page 4-6

• “NetWorker server resource” on page 4-7

Note: Do not create multiple instances of the NetWorker Server resources. Creating more than one instance of a NetWorker Server resource interferes with the functionality of existing NetWorker Server resources.

NetWorker server installation 4-5

MSCS Installation

NetWorker IP address resourceTo create a NetWorker IP Address resource:

1. In the Cluster Administrator program, select File > New > Resource.

2. Complete the following attributes:

Name: NSR_IP

Description: NetWorker IP Address

Resource Type: IP Address

Group: NetWorker Group

Note: For the Name attribute, type any descriptive name (without spaces). For the Description attribute, type any descriptive text.

3. Click Next. In the Possible Owners dialog box, type the hostname of each required node in the cluster. For example:

Possible Owners: uranus, pluto

4. Click Next. In the Dependencies dialog box, specify the shared disk you associated with the NetWorker virtual server. For example:

Dependencies: Disk P:

5. Click Next. In the TCP/IP Address Parameters dialog box, type the IP address of the NetWorker virtual server. For example:

IP: 10.0.0.4

NetWorker network name resourceTo create a NetWorker Network Name resource:

1. In the Cluster Administrator program, select File>New>Resource.


Name: NSR_NetworkName

Description: NetWorker Network Name

Resource Type: Network Name


Note: For the Name attribute, type any descriptive name (without spaces). For the Description attribute, type any descriptive text.


Possible Owners: pluto, uranus

4. Click Next. In the Dependencies dialog box, type the name of the NetWorker IP Address resource. For example:

Dependencies: NSR_IP

5. Click Next. In the Network Name Parameters dialog box, type the name of the NetWorker virtual server. For example:

Name: neptune


MSCS Installation

NetWorker server resourceTo create a NetWorker Server resource:

1. In the Cluster Administrator program, select File>New>Resource.


Name: NSR_Server

Description: NetWorker Server Resource

Resource Type: NetWorker Server


Note: For the Name attribute, type any descriptive name (without spaces). For the Description attribute, type any descriptive text. For the Resource Type attribute, type the name of the resource type created in “Task 2: Create and register the NetWorker server cluster resource type” on page 4-5.


Possible Owners: pluto, uranus

4. Click Next. In the Dependencies dialog box, type the name of the NetWorker Network Name resource. For example:

Dependencies: NSR_NetworkName

5. Click Next. In the NetWorker Server Parameters dialog box, complete the following attributes:

Server Name: (leave blank)

NsrDir: P:\nsr

Additional Arguments: (leave blank)

Note: The directory path entered for the NsrDir attribute must reside on the NetWorker server shared disk.

6. After completing these steps, a message appears indicating that the resource was successfully created. Verify that a new NetWorker Server type resource was created in the selected resource group.

Note: The MSCS software provides an option to set up an application of the Generic Application type within a Group resource. Do not create a Generic Application resource for the NetWorker virtual server.

Task 5: Bring the NetWorker server resource onlineTo bring the NetWorker Server resource online:

1. In the Cluster Administrator program, select the resource group where the NetWorker Server resource exists.

2. Select the NetWorker Server resource.

3. Select Bring Online from the File menu to bring the NetWorker server online. The state of the NetWorker Server resource changes to Online Pending.

4. Wait until the state of the NetWorker Server resource changes to Online.

These steps stop the NetWorker Remote Exec service and restart all of the NetWorker services.

NetWorker server installation 4-7

MSCS Installation

Task 6: Configure the NetWorker virtual serverTo configure the NetWorker virtual server:

1. Log on to the cluster node that is running the NetWorker virtual server.

2. 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:

administrator@cluster_phy1

b. Click OK.

Note: To specify which NetWorker servers can back up a particular client, edit the <NetWorker_install_path>\res\servers file and add the NetWorker virtual host and each cluster node.

Task 7: Configure clients on the NetWorker cluster serverTo configure a NetWorker client to back up the quorum data, first perform the following steps:

1. In the Cluster Administrator program, verify that the same physical node owns the cluster group and quorum disk.

2. Select the disk group that contains the quorum disk.

3. Drag the quorum disk to the cluster group.

To configure the NetWorker Client resource:

1. Log on to the cluster node that is running the NetWorker virtual server.

2. Add the NetWorker virtual server to the hosts file on each node (located in %SystemRoot%\system32\drivers\etc).


4. Make each physical node within the cluster a client of the NetWorker virtual server.

For each physical node in the cluster:

a. Create a new NetWorker Client resource.

b. For the Name attribute, type the name of the physical host.

For information about creating a NetWorker Client resource, refer to the NetWorker Administration Guide.

5. Make each virtual server within the cluster a client of the NetWorker virtual server.

For each virtual node in the cluster:

a. Create a new NetWorker Client resource.

b. For the Remote Access attribute, type the user@hostname of each physical node within the cluster.

6. Define one or more NetWorker Group resources to include the NetWorker virtual server and each of the physical nodes in the cluster:

a. Create the necessary groups and define their attributes as appropriate.

b. For each group, select Enabled for the Autorestart attribute.

c. For each group, ensure that Manual Restart is not selected in the Options attribute (under the Preferences tab).


MSCS Installation

Note: The only save sets that restart after a virtual client failover are those that belong to a group in which Autorestart is enabled and Manual Restart is disabled.

7. Run a test probe to verify that the Client and Group resources are properly configured. On the node on which the NetWorker server resides, run the following command:

savegrp -pv -c client_name group_name

If the expected scheduled backups and index do not appear, perform the following workaround:

a. Create an empty file named pathownerignore in the directory where the NetWorker savefs command is installed (the default location is <NetWorker_install_path>\bin). This allows a valid save set to be scheduled for backup for a NetWorker client.

This file must be created on each NetWorker server and NetWorker client host in the cluster.

b. To bypass the default ownership scheduling rules, run the following command:

echo NUL: > NetWorker_install_path\bin\pathownerignore

This command allows any path to be scheduled for backup for a NetWorker client.

Note: A NetWorker scheduled save might use a client index name other than the one you want it to. To override this default, run a manual save with the -c option:save -c desired_client_name To restrict the set of NetWorker servers that can back up a particular client, edit the <NetWorker_install_path>\res\servers file to add the NetWorker virtual host as well as each cluster node to the list of servers.

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 that is to be backed up by the NetWorker virtual host.

Configuring a backup device for the NetWorker virtual serverThe NetWorker virtual server must be configured with storage node backup devices. The storage nodes the NetWorker virtual server uses 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 drive or an autochanger.

For information on configuring storage nodes, refer to the NetWorker Administration Guide.

Note: MSCS does not support shared tapes. You cannot configure the NetWorker virtual server with tape devices connected to a shared bus.

MSCS does support disk devices connected to a shared bus. However, it is strongly recommended that you not use file type devices connected to a shared bus.

Configuring a backup device for the NetWorker virtual server 4-9

MSCS Installation

The NetWorker virtual server requires a local backup device to save the bootstrap and the server indexes. With release 6.0 or later, the NetWorker virtual server bootstrap and indexes can be also saved to a storage node. The storage node device, in such a case, must be attached to the cluster node on which the NetWorker virtual server is currently running.

A NetWorker virtual server running on a two-node cluster requires the following minimum device configuration:

◆ Each cluster node must be configured as a storage node for the NetWorker virtual server. For instructions, see “Defining a cluster node as a storage node” on page 4-10.

◆ The Storage Nodes attribute for the NetWorker virtual server (under the Preferences tab in the Client resource) must list the storage nodes enabled to store data for the client, in the following order:

• One cluster node

• Other cluster node

• nsrserverhost

Note: The nsrserverhost must be listed last in each client's storage node list.

NetWorker software does not allow you to configure a storage node on a cluster node running the NetWorker server software. Consequently, before you configure a storage node, you must move the NetWorker virtual server to another node in the cluster.

Defining a cluster node as a storage node

To define each cluster node as a storage node for the NetWorker virtual server:

1. Log on to a cluster node that does not currently own the NetWorker virtual server.

2. Configure the cluster node as a NetWorker storage node. For instructions, refer to the NetWorker Administration Guide.

3. Using the Cluster Administrator program, move the NetWorker virtual server to another node in the cluster.

4. Once you have moved the NetWorker virtual server to the other node:

a. Log on to a cluster node that does not currently own the NetWorker virtual server.

b. Configure the cluster node as a NetWorker storage node.

Note: The NetWorker Remote Exec service must be running on each storage node within the cluster.

Moving the NetWorker server to another nodeTo move the NetWorker server from one node to another within the cluster, use the Cluster Administrator program to move the resource group that contains the NetWorker Server resource from one node to another:

1. Select the resource group where the NetWorker Server resource exists.

2. Select Move Group from the File menu to change the state of the resources in this group to Offline Pending.

This brings all the resources in the current node offline. It also brings all the resources in the other node in the cluster online.

3. Wait until the state of all the resources in the group becomes Online again.


MSCS Installation

Registering NetWorker licenses for cluster failover

Note: To register NetWorker licenses for cluster failover, first complete all tasks under “Installing a NetWorker server for cluster mode” on page 4-4.

1. Ensure the NetWorker virtual server is online.

2. Log on to the cluster node on which the NetWorker virtual server is running.

3. Create a file named hostids in the <NetWorker_install_path>\res directory. The file name must not have a file extension.

4. Add one line to the hostids file, in the following format:

hostid1:hostid2

where the host ID are the NetWorker server host ID values obtained in: “Task 1: Install the NetWorker software” on page 4-4.

5. Restart the NetWorker virtual server by taking it offline and then bringing it back online.

Note: The host ID now displayed in the NetWorker Administrator program (or by running the lgtolic -i command) is the composite hostid. This composite host ID is required for permanent registration in a clustered environment.

6. Register the NetWorker software for permanent use. For information on registering NetWorker software, see Chapter 6, “Licensing and Enabling the Software.”

Restarting the NetWorker server services

Note: Start the NetWorker server manually in a cluster environment only if it is running as a stand-alone server.

If the NetWorker server is configured as a cluster group resource, then you must start or restart the NetWorker services through the cluster software.

To start the NetWorker server within cluster mode, see “Task 5: Bring the NetWorker server resource online” on page 4-7. Use the Cluster Administrator program to restart the NetWorker server services in the current node by taking the server offline and bringing it back online.

Installing only the NetWorker client software in a clusterTo install the NetWorker client software as a highly available application:

1. Install the NetWorker client software on the private disk of each node in the cluster. For instructions, see “Task 2: Install the NetWorker software (client, server, storage node)” on page 3-8.

2. Configure each node in the cluster as a client of the NetWorker server. These are physical cluster clients.

If the NetWorker server is configured as a Cluster resource, add the hostname and user of this NetWorker virtual server to the following Client resource attributes of the physical cluster clients:

• Remote Access

• Administrator

Registering NetWorker licenses for cluster failover 4-11

MSCS Installation

3. Configure each of the virtual servers in a cluster as a client of the NetWorker virtual server. These are virtual cluster clients.

4. Add the hostname and user of each node to the following Client resource attributes of the virtual clients:

• Remote Access

• Administrator

Removing NetWorker software from MSCSIf the NetWorker server is configured as a cluster resource, perform the following steps before removing the NetWorker software.

If the NetWorker server is installed as a stand-alone application (not cluster managed) or only the client software is installed, follow the standard uninstall procedure for NetWorker software. For instructions, see “Uninstalling the NetWorker software” on page 3-14.

Note: Before uninstalling NetWorker software from a cluster node, close the Cluster Administrator program on the NetWorker server.

Uninstall NetWorker software from all the nodes in the cluster

To uninstall NetWorker software from all the nodes in the cluster:

1. Unregister and remove the NetWorker Server resource:

a. In the Cluster Administrator program, select Take Offline from the File menu to bring the NetWorker Server resource Offline.

b. Select Delete from the File menu to delete the NetWorker Server resource from MSCS.

c. Run the regcnsrd -u command on all but the last member of the cluster.

If you are prompted with the following question, type Y:

Is this machine a member of the cluster on which you want to un-register Resource Extension for NetWorker Server resource?

d. Run the regcnsrd -d command on the last member of the cluster.

2. Close the Cluster Administrator program on all the nodes where you plan to uninstall NetWorker software.

3. Uninstall the NetWorker software from all nodes. For instructions, see “Uninstalling the NetWorker software” on page 3-14.

Uninstalling NetWorker software from only one node in the cluster

Use the following procedure if the NetWorker server software is installed on more than one node and all these nodes are possible owners that can host the NetWorker Server resource.

To uninstall NetWorker software from only one node in the cluster:

1. From one node in the cluster, run the regcnsrd -u command.

If you are prompted with the following message, type Y:

Is this machine a member of the cluster on which you want to un-register Resource Extension for NetWorker Server resource?


MSCS Installation

2. Log on to another node in the cluster that can host the NetWorker server.

3. Remove the node that you are uninstalling from the Possible Owners attribute in the NetWorker Server resource.

Note: To determine the possible owners of the NetWorker Server cluster resource, review the properties of the NetWorker Server resource.

4. Close the Cluster Administrator program on the node where you plan to uninstall the NetWorker software.

5. Uninstall the NetWorker software from the node. For instructions, see “Uninstalling the NetWorker software” on page 3-14.

Troubleshooting NetWorker software in the MSCS environmentThe following sections provide tips for troubleshooting problems with the NetWorker software in an MSCS environment.

NetWorker virtual server fails to start nsrmmdIf the NetWorker virtual server fails to start nsrmmd on a NetWorker storage node, the following error messages are written into the NetWorker server daemon.log file:

06/08/00 10:00:11 nsrmon #217: connect to nsrexec prog 390113 vers 1 on `uranus' failed: RPC error: Remote system error06/08/00 10:00:11 nsrd: media notice: check storage node: uranus (RPC error: Remote system error)06/08/00 10:00:11 nsrd: media info: restarting nsrmmd #1 on uranus in 2 minute(s)06/08/00 10:02:12 nsrd: media info: restarting nsrmmd #1 on uranus now06/08/00 10:02:42 nsrmon #183: connect to nsrexec prog 390113 vers 1 on `

The error might be caused by the NetWorker Remote Exec service not running on the storage node.

If the NetWorker Remote Exec service is not running:

1. On the Storage Node, select Services from the Control Panel.

2. Right-click the NetWorker Remote Exec service name and select Start.

NetWorker server fails to back up a virtual cluster clientThis example uses the following names:

◆ charon — virtual cluster client running on pluto

◆ pluto — physical cluster node

◆ neptune — NetWorker server

Troubleshooting NetWorker software in the MSCS environment 4-13

MSCS Installation

If a NetWorker server fails to back up a virtual cluster client, the following error message might appear:

06/19/03 12:56:57 nsrd: savegroup alert: test completed, 1 client(s) (charon Failed) charon:Q:\: No save sets with this name were found in the media database; performing a full backup

* charon:Q:\ save: RAP error: Unable to extract resource info for client pluto.emc.com.* charon:Q:\ save: Cannot open save session with neptune.emc.com* charon:Q:\ 1 retry attempted* charon:Q:\: No save sets with this name were found in the media database; performing a full backup* charon:Q:\ save: RAP error: Unable to extract resource info for client pluto.emc.com.* charon:Q:\ save: Cannot open save session with neptune.EMC.com

06/19/03 12:56:57 nsrd: runq: NSR group test exited with return code 1.

This error might occur because the NetWorker Client resources for each of the physical nodes in the cluster are missing.

To correct the error:

1. Create a NetWorker Client resource for each physical node that is allowed to own the virtual cluster client.

2. Rerun the backup.

NetWorker services fail to start in an MSCS environment

If the NetWorker services fail to start in an MSCS environment:

1. Check for a file named NetWorker_install_path>\bin\NetWorker.clustersvr.

2. If the NetWorker.clustersvr does not exist, create an empty file with that name.

3. Select Services from the Control Panel.

4. Right-click the NetWorker Remote Exec service name and select Start.


5

This chapter explains how to install NetWorker software in an EMC AutoStart™ environment.


◆ Software installation roadmap ................................................................................................5-2◆ Installation requirements..........................................................................................................5-2◆ Installing a NetWorker virtual server.....................................................................................5-4◆ Installing only the NetWorker client software in a cluster ..................................................5-9◆ Configuring the NetWorker virtual server with a backup device.................................... 5-11◆ Troubleshooting ....................................................................................................................... 5-11◆ Uninstalling the NetWorker software...................................................................................5-13

EMC AutoStartInstallation

EMC AutoStart Installation 5-1

EMC AutoStart Installation

Software installation roadmapThe following tasks are a roadmap to follow when installing the NetWorker software. Read the roadmap and the referenced sections before installing the software.

1. Review the requirements section and note the default directory location. For information, see “Installation requirements” on page 5-2.

2. Install the required NetWorker software. For installation instructions, see one of the following sections:

• “Installing a NetWorker virtual server” on page 5-4

• “Installing only the NetWorker client software in a cluster” on page 5-9

3. Enable and register all of the NetWorker products. For information, see Chapter 6, “Licensing and Enabling the Software.”

Installation requirementsThe following sections discuss the software and hardware required to install and configure the NetWorker server or client software within a EMC AutoStart cluster environment:

For the most up-to-date information regarding software and hardware requirements, refer to the EMC Information Protection Software Compatibility Guide.

Software requirementsTo install NetWorker cluster server and client, ensure that the following software is installed on each node in the cluster.

Cluster server◆ Windows 2000 Server/Advanced Server (latest Service Pack installed) or later

◆ EMC AutoStart release 5.1 or later

◆ 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

Cluster clientThe following must be installed on the private disk of each node in the cluster prior to installing the NetWorker client:

◆ Windows 2000 Server/Advanced Server (latest Service Pack installed) or later

◆ EMC AutoStart release 5.1 or later

Hardware requirements

To install the NetWorker software, make sure that the following hardware requirements are met for server installation only:

◆ Dedicated shared disk used as the NetWorker storage disk (for the /nsr directory) connected to all the nodes within the cluster.

◆ Device with local affinity for the local bootstrap backup connected to all the nodes within the cluster.



Configuration options

Refer to the NetWorker Administration Guide for 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 5-1 on page 5-3 and Table 5-1 on page 5-4 display the system information needed to install NetWorker software within a EMC AutoStart environment.

Different platforms use different terms for the same cluster concepts. EMC AutoStart refers to:

◆ Physical hosts as nodes

◆ Virtual server as a resource group (application service)

Figure 5-1 Sample cluster configuration

Node 1 clus_phys1

Node 2 clus_phys2

Private NetWork

Local Disk Local Diskclus_log1

NetWorker Logical Host

If Node1fails,clus_log1 failsover to Node2

Public NetWork

Volume-managed Shared Disks

Terminal Concentrator

Administrative Workstation

Installation requirements 5-3


Table 5-1 Information Required During NetWorker Virtual Server Installation

Updating NetWorker software in a EMC AutoStart environmentTo update the NetWorker server software in a EMC 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\Legato\nsr\bin.

3. Upgrade the NetWorker software. For details, see “Task 2: Install the NetWorker software (client, server, storage node)” on page 3-8.

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.

Installing a NetWorker virtual serverTo install and configure the NetWorker software as a highly available service in a cluster, read and follow the procedures for these tasks:

◆ “Task 1: Ensure that the EMC AutoStart software is installed” on page 5-5

◆ “Task 2: Install the NetWorker software” on page 5-5

◆ “Task 3: Promote at least one secondary cluster node to primary” on page 5-5

◆ “Task 4: Create the resource that will become the managed shared disk” on page 5-5

◆ “Task 5: Define the NetWorker server as highly available” on page 5-6

◆ “Task 6: Configure the NetWorker virtual server” on page 5-7

◆ “Task 7: Configure clients of the NetWorker cluster server” on page 5-8

◆ “Task 8: Register NetWorker licenses for cluster server failover” on page 5-9

Required information Example

Pathname for the shared nsr directory s:\nsr

Server name of the NetWorker virtual server jupiter

Server netmask 255.255.255.0

Domain name for the EMC AutoStart server (Domain names are case-sensitive)

galaxy

Installation directory pathname C:\Program Files\emc\ AAM\galaxy

Server names of first and second physical hosts in the EMC AutoStart Cluster. Server names must not exceed fifteen characters in length.

marssaturn



Task 1: Ensure that the EMC AutoStart software is installed

Ensure that the EMC AutoStart software is installed. For detailed installation instructions, refer to the EMC AutoStart documentation.

For EMC AutoStart release 5.1.2, you must install the following hotfix: ftp://ftp.legato.com/pub/cluster/patches/5.1/windows

/A_WIN_HF_5.1.2_79520.exe

Task 2: Install the NetWorker software

On each node in the cluster, install NetWorker server software in the same location on a private disk, for example, in %SystemDrive%\Program Files\Legato\nsr.

To install the NetWorker software:

1. Log on as Administrator on one node.

2. Install the following NetWorker software on each node in the cluster:

• NetWorker client

• Storage node

• NetWorker server

For instructions, see Chapter 3, “Installing the Software.”

3. Obtain the NetWorker hostid as follows:

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. You will need this HostID later in the installation.

4. Repeat the preceding steps on the second node.

Task 3: Promote at least one secondary cluster node to primaryYou must always run two primary controllers. Promote at lease one secondary node to the primary, using the EMC AutoStart Console. If one node fails, the other can be brought online automatically with all data.

For detailed instructions, refer to the EMC AutoStart documentation available.

Task 4: Create the resource that will become the managed shared diskOn one of the cluster nodes, create a folder that you can later use as the managed, shared disk. For example, create the \nsr folder.

Note: Do not share the folder at this point. If you do, the installation will fail. If EMC AutoStart software is already installed and a managed shared disk already exists, remove the share property now.

Installing a NetWorker virtual server 5-5


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 on as Administrator.

2. 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 using DNS, use the following command:

nslookup nodename

3. Start the NetWorker Backup and Recover Server services.

Note: If you are upgrading NetWorker software or reinstalling after a partial uninstall of the NetWorker software, the lc_config script prompts you to enter a command to keep, rename or delete each of the old server configuration files. It is safe to simply delete the old files.

To delete a file, when you are prompted, enter d. After you finish entering your choices for each of the old configuration files, continue with step 5.

4. Run the lc_config script. When the lc_config script runs, you are prompted to enter the information listed in Table 5-1 on page 5-4.

lc_configC:\Program Files\Legato\nsr\bin>lc_config Checking for C:\Program Files\Legato\nsr\bin\lcmap.bat Checking for C:\Program Files\Legato\nsr\bin\NetWorker.clustersvrEnter shared nsr dir:s:\nsrEnter the Legato Cluster domain name:galaxyEnter the directory in which your Legato Cluster software is installed (typically something like C:\galaxy):C:\Program Files\Legato AAM\galaxy

5. As the lc_config script continues running, the information you entered is shown on the screen and you are prompted to enter y to confirm that this information is correct. If you need to make corrections, enter n. The lc_config script runs again so that you can re-enter your information.

You entered the following data:Nsr Dir = s:\nsr,Legato Cluster domain = galaxyLegato Cluster software location = C:\Program Files\Legato AAM\galaxyIs this OK [y/n]y

6. Stop the NetWorker Backup and Recover Server services.

7. Edit the nw_nt.aam5.imp file and modify the following fields:

• virtual hostname

• physical cluster node names

• shared drive letter

The #NW customise label tag appears before each field that requires modification.



8. On one node only, go to %SystemDrive%\Program Files\Legato\nsr\bin and run the following command. For example, if your EMC AutoStart domain name is galaxy, enter:

“C:\Program Files\Legato AAM\galaxy\bin\ftcli” -d galaxy -c "import nw_nt.lc.imp"

The screen displays the following:

C:\Program Files\Legato\nsr\bin>"C:\Program Files\Legato AAM\galaxy\bin\ftcli" -domain galaxy -c "import nw_nt.aam5.imp"IP Address "guiro" CreatedProcess Class "nsrd" CreatedProcess "NSRserver" CreatedConfiguration "NSRserver" CreatedProcess Class "nsrexecd" CreatedProcess "NSRexecd" CreatedConfiguration "NSRexecd" CreatedData Source "networker_ds" CreatedResource Group "networker" CreatedOK

9. Use the EMC 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.

10. For each physical node in the cluster, ensure that the EMC AutoStart Console user account, NT AUTHORITY\SYSTEM is included in the valid user list with administrator access.

11. 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 EMC AutoStart Management Console.

The data source for the NetWorker virtual server is defined as networker_ds in the NetWorker resource group.

c. Run the following script from the directory where the NetWorker software was installed:

nwinst.bat

For details about EMC AutoStart Console, refer to the EMC AutoStart documentation.

Task 6: Configure the NetWorker virtual server

To configure the NetWorker server:

1. Log in as root on the cluster node that is running the NetWorker virtual server and start the NetWorker software:

nsradmin -s clus_vir1

2. From the Administration window, select Properties from the File menu.

Installing a NetWorker virtual server 5-7


a. For the Administrator attribute, add entries for any cluster nodes that are not already listed. For example:

root@hostname

b. Click OK.

Note: To restrict the set of NetWorker servers that can backup a particular client, edit the nsr\res\servers file and add the NetWorker virtual host as well as each cluster node to the list of servers.

Task 7: Configure clients of the NetWorker cluster serverTo configure each client under the NetWorker server:

1. (Optional) Define save groups as required:

Note: Save groups must have the Autorestart attribute enabled and the Manual Restart option disabled in order for their save sets to restart after a virtual client or NetWorker server failover.

2. Make each physical Client within the cluster a NetWorker client of the NetWorker server.

For each physical client in the cluster:

a. Create a new NetWorker client.

b. For the Name attribute, enter the name of the physical client.

3. Make each virtual client within the cluster a NetWorker client of the virtual NetWorker server.

For each virtual client in the cluster:


b. For the Name attribute, enter 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. For information, refer to the NetWorker Administration Guide.

4. Verify that the client and group resources have been properly configured by running a test probe. On the node on which the NetWorker server resides, run the following command:

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:

On each node of the cluster, enter the following command from a Windows command prompt:

echo NUL: NetWorker_bin_dir\pathownerignore



Note: A NetWorker scheduled save might use a client index name other than the one you want it to. To override this default, run a manual save with the -c option from the Windows command prompt:save -c client_name

To restrict the set of NetWorker servers that can back up a particular client, edit the %SystemDrive%\Program Files\Legato\nsr\res\servers file and add the NetWorker virtual host as well as each cluster node to the list of servers.

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. Make sure that you defined the NetWorker virtual server as part of a cluster.

2. Make sure that the NetWorker service is running.

3. Log on 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 file named hostids and add one line. For the values of the hostids, use the NetWorker hostids values you obtained in “Task 2: Install the NetWorker software” on page 5-5.

hostid1:hostid2

6. Restart the NetWorker virtual server by taking it offline and then bringing it back on line.

7. Register the NetWorker software for permanent use. For information explaining how to register NetWorker software, see Chapter 6, “Licensing and Enabling the Software.”

Installing only the NetWorker client software in a clusterTo install NetWorker cluster client, read and follow the procedures for these tasks:

◆ “Task 1: Install the NetWorker cluster client software” on page 5-10

◆ “Task 2: Configure NetWorker client software as a highly available” on page 5-10

Note: Ensure the NetWorker client software is installed on every node to be backed up in the cluster.

Installing only the NetWorker client software in a cluster 5-9


Task 1: Install the NetWorker cluster client software

To install the NetWorker client software on each node in the cluster:

1. Ensure that the operating system is updated with the most recent cluster patch.

2. For EMC AutoStart release 5.1.2, you must install the following hotfix: ftp://ftp.legato.com/pub/cluster/patches/5.1/windows

/A_WIN_HF_5.1.2_79520.exe

3. Install the NetWorker client software on the physical disk of each node in the cluster to be backed up. For instructions, see “Task 2: Install the NetWorker software (client, server, storage node)” on page 3-8.

Task 2: Configure NetWorker client software as a highly available

To configure the NetWorker server:

1. Make each physical client within the cluster a NetWorker client of the NetWorker server.

For each physical client in the cluster:

a. Create a NetWorker new client.

b. For the Name attribute, enter the name of the physical client.

Note: 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. Make each virtual client within the cluster a client of the NetWorker server.

For each virtual client in the cluster:


b. For the Name attribute, enter 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.

3. Schedule backups using the NetWorker application.

4. On each node in the cluster, run the cluster configuration program lc_config.

a. Log on as Administrator on each node.

b. Run the lc_config program. When prompted for the shared nsr directory, you can leave the field blank. For example:

lc_config

C:\Program Files\Legato\nsr\bin>lc_configChecking for C:\Program Files\Legato\nsr\bin\lcmap.batChecking for C:\Program Files\Legato\nsr\bin\NetWorker.clustersvrEnter shared nsr dir:Enter the Legato Cluster domain name:galaxyEnter the directory in which your Legato Cluster software is installed (typically something like C:\galaxy): C:\ProgramFiles\Legato AAM\galaxy

c. Confirm the information by typing y when prompted.



5. For each physical node in the cluster, ensure that the EMC AutoStart Console user account, NT AUTHORITY\SYSTEM is included in the valid user list with administrator access.

For instructions on using the EMC AutoStart Console, refer to the EMC AutoStart documentation.

Configuring the NetWorker virtual server with a backup deviceThe NetWorker virtual server must be configured with storage node backup devices. The storage nodes 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. For information explaining how to configure storage nodes, refer to the NetWorker Administration Guide.

The NetWorker server requires a local backup device to save the bootstrap and the server indexes. With release 6.0 or later, the NetWorker virtual server bootstrap and indexes can be also saved to a storage node. The storage node device, in such a case, must be attached to the cluster node on which the NetWorker virtual server is currently running.

The following is the recommended device configuration for a NetWorker virtual server, release 6.0 or later, running in a two-node EMC AutoStart cluster:

◆ Each cluster node must be defined as a storage node for the NetWorker virtual server.

◆ In the EMC AutoStart Console, the Preferences\’Storage Nodes attribute in the NetWorker virtual server client resource lists the storage nodes enabled to store data for the client. The storage nodes must be listed in the following order:

• one cluster node

• the other cluster node

• nsrserverhost

Note: Ensure the nsrserverhost is always listed last in each client's storage node list.

NetWorker software does not allow the configuration of a storage node on a cluster node 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.

TroubleshootingThe following sections contain troubleshooting tips for NetWorker software in a EMC AutoStart environment.

Setting the shutdown wait timeout values

To prevent timing problems during failover, perform the following 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 and then select the 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.

Configuring the NetWorker virtual server with a backup device 5-11


NetWorker virtual server fails to start nsrmmd

If the NetWorker virtual server fails to start nsrmmd on a NetWorker storage node, the following error messages are sent to the NetWorker server daemon log:

06/08/00 10:00:11 nsrmon #217: connect to nsrexec prog 390113 vers 1 on

`uranus' failed: RPC error: Remote system error

06/08/00 10:00:11 nsrd: media notice: check storage node: uranus (RPC

error: Remote system error)

06/08/00 10:00:11 nsrd: media info: restarting nsrmmd #1 on uranus in 2

minute(s)

06/08/00 10:02:12 nsrd: media info: restarting nsrmmd #1 on uranus now

06/08/00 10:02:42 nsrmon #183: connect to nsrexec prog 390113 vers 1 on `

The error might be caused by the NetWorker Remote Exec service not running on the storage node. If the service is not running, complete these steps to restart the service:

1. Select Services from the Control Panel on the storage node.

2. Restart the service.

NetWorker server fails to back up a virtual cluster client

In this example, the following names are used:

◆ charon — Virtual cluster client running on pluto

◆ pluto — Physical cluster node

◆ neptune — NetWorker server

If a NetWorker server fails to backup a virtual cluster client, the following error message might appear:

06/19/00 12:56:57 nsrd: savegroup alert: test completed, 1 client(s)

(charon Failed) charon:Q:\: No save sets with this name were found in the

media database; performing a full backup

* charon:Q:\ save: RAP error: Unable to extract resource info for client

pluto.legato.com.

* charon:Q:\ save: Cannot open save session with neptune.legato.com

* charon:Q:\ 1 retry attempted

* charon:Q:\: No save sets with this name were found in the media

database; performing a full backup

* charon:Q:\ save: RAP error: Unable to extract resource info for client

pluto.legato.com.

* charon:Q:\ save: Cannot open save session with neptune.legato.com

06/19/00 12:56:57 nsrd: runq: NSR group test exited with return code 1.

This error might be occurring because the NetWorker client resources for each of the physical nodes in the cluster are missing.

Complete the following steps to correct the error:

1. Create client resources for each physical node in the cluster that is allowed to own the virtual cluster client.

2. Re-run the backup.



Rolling back changes to the cluster configuration file

To roll back changes to the cluster configuration file (lc_config), perform the following:

1. Take the NetWorker Resource Group Offline.

For instructions on using the EMC AutoStart Console, refer to EMC AutoStart documentation.

2. Stop the NetWorker Remote Exec service.

3. Delete or rename the following files from the NetWorker installation directory:

• NetWorker.clustersvr

• lcmap.bat

• nwinst.bat

An example of the NetWorker installation directory is:

C:\Program Files\Legato\nsr\bin

4. From the EMC AutoStart Console, select and delete the following:

• Networker Resource Group

• NSRserver

• NSRexecd services

• networker_ds data source

• NetWorker virtual server IP address.

Uninstalling the NetWorker softwareTo uninstall the NetWorker software from a EMC AutoStart environment:

1. Take the NetWorker Resource Group Offline.

For instructions on using the EMC AutoStart Console, refer to EMC AutoStart documentation.

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. Uninstall the NetWorker Server software from each node. For information on uninstalling NetWorker software, see “Uninstalling the NetWorker software” on page 3-14.

Note: If the NetWorker software will be reinstalled to the same location, ensure that the following files are deleted from the /bin subdirectory: NetWorker.clustersvr, lcmap.bat and winst.bat.

Uninstalling the NetWorker software 5-13

6

This chapter explains how to enable the NetWorker software and features for permanent use. The chapter also describes the EMC NetWorker licensing model and provides a basic explanation of licensing for the different NetWorker Editions, modules, and features, but it does not provide a comprehensive description of every possible licensing scenario. For specific licensing questions, go to http://softwaresupport.EMC.com.

When the NetWorker software is installed, it is in a temporary evaluation mode with all of the features available.

The chapter includes these sections:

◆ How NetWorker software is licensed .....................................................................................6-2◆ The evaluation process .............................................................................................................6-2◆ The licensing process ................................................................................................................6-3◆ Multiplatform licensing ............................................................................................................6-6◆ Managing NetWorker licenses.................................................................................................6-8

Licensing and Enablingthe Software

Licensing and Enabling the Software 6-1


Licensing and Enabling the Software

How NetWorker software is licensedNetWorker software and added features, such as modules, are installed in evaluation mode. The licensing of NetWorker software means entry of enabler and authorization codes on the server for the NetWorker environment. Without these codes, the software or added features will not run beyond the evaluation period.

Each installation of NetWorker server software must be licensed with a base enabler. This enabler “turns on” the software and allows you to use a particular bundle of features, such as a specified number of clients and devices. All licensing takes place on the server. The licenses are entered and stored on the server. The server enforces the licensing.

Base enablers come in different editions, which enable varying degrees of functionality. Add-on enablers allow a broader scope of features.

The steps in this chapter assume that the NetWorker software is installed and that all of the software and hardware requirements have been met on the computer that will access Console. For information about the Console, see “NetWorker Management Console” on page 3.

The evaluation processEvaluating NetWorker software can take place in two ways:

◆ By evaluating a new installation of the software on a NetWorker server

◆ By evaluating NetWorker features on an existing NetWorker installation

Evaluating a new installationWhen you first install the NetWorker software, you can evaluate it with all the modules and features for 30 days free without entering any codes.

By the end of the evaluation period, you must purchase, enter, and authorize a base enabler to continue to use the NetWorker software to back up data. The base enabler is the license that enables the edition purchased. Go to http://softwaresupport.EMC.com for information.

To continue to use some of the modules and features that were available with the evaluation software, you may need to purchase add-on enablers, depending on the edition of the base enabler.

Evaluating features on an existing installationIf you are evaluating one or more NetWorker Modules or features on an edition of NetWorker software that has already been installed and enabled, enter a temporary enabler for each module or feature. The temporary enabler is valid for 45 days.

◆ To obtain a temporary enabler code, refer to the EMC Information Protection Media Kit or go to http://softwaresupport.EMC.com.

◆ “How to enter a temporary enabler code” on page 3 describes how to install a temporary enabler code.

By the end of the evaluation period, you must purchase, install, and authorize the corresponding license enablers to continue to use modules or features you have evaluated. “The licensing process” on page 3 provides instructions. “Multiplatform licensing” on page 6 provides information on the different NetWorker features.





How to enter a temporary enabler code

CAUTION!The temporary enabler code is valid on only one computer in a network. If you enter the same code on more than one computer in a network, a copy protection violation error occurs and the NetWorker server software is disabled on all NetWorker servers with duplicate enablers.

To enter the temporary enabler code:


2. Launch the Administration window:

a. From the Console window, click Enterprise.

b. From the left pane, select a NetWorker server in the Enterprise list.

c. From the right pane, select the application.

d. From the Enterprise menu, click Launch Application.


3. From the Administration window, click Configuration.

4. In the left pane, select Registration.


6. In the Enabler Code attribute, type the enabler code.

7. In the Name attribute, type the name of the license.

8. (Optional) In the Comment attribute, type a description of the license.

9. Click OK.

The licensing processTo permanently use NetWorker software, you must purchase and enter a license enabler code, and then authorize it. This licensing process is the same for all editions of NetWorker software as well as for individual modules and features.

The license enabler code that you purchase is valid for 45 days, as a registration period. During the registration period, you must obtain and enter a corresponding authorization code.

These sections explain how to enter and authorize the license enabler:

◆ “Task 1: Enter the license enabler code” on page 4

◆ “Task 2: Obtain an authorization code” on page 4

◆ “Task 3: Enter the authorization code” on page 5

The licensing process 6-3


Task 1: Enter the license enabler code

License enabler codes are included in either the letter announcing the updated or upgraded software, or on the Enabler Certificate you receive when you purchase a software license. This depends on whether the software purchased is a first-time purchase or an updated or upgraded version.

Note: To save time when entering multiple licenses, enter the base enabler last. Otherwise, once a base enabler is entered, devices that do not yet have licenses entered may be disabled. Those devices would have to be reenabled manually after their licenses are installed.

To enter the license enabler code:




b. From the left pane, click a NetWorker server in the Enterprise list.

c. From the right pane, click the application.

d. From the Enterprise menu, select Launch Application.


3. In the Administration window, click Configuration.

4. In the left pane, select Registrations.


The Create Registration dialog box appears.

6. In the Enabler Code attribute, type the enabler code.

7. In the Name attribute, type the name of the license.

8. (Optional) In the Comment attribute, type a description of the license.

9. Click OK.

The new license is added and appears in the right pane. Repeat the procedure to add any additional enabler codes.

After you type a license enabler code, you have 45 days as a registration period to authorize the NetWorker software.

Task 2: Obtain an authorization codeRegistration of NetWorker software takes place by obtaining an authorization code. Obtain a unique authorization code through one of these methods:

◆ “By using the EMC website” on page 5

◆ “By using email” on page 5

CAUTION!If the software or feature is not authorized by the end of the 45-day registration period, the NetWorker backup function or feature is disabled. However, data that was backed up during the registration period can still be recovered from local devices.



By using the EMC websiteRegister products and obtain authorization codes online by completing a registration form on the EMC CustomerNet portal at http://softwaresupport.EMC.com.

An authorization code that permanently enables the NetWorker license will be sent by email. “Where to get help” on page ix provides contacts for any questions about software updates.

By using emailTo register the software and obtain an authorization code by email:









4. In the left pane, select the NetWorker server.

5. From the File menu, select Properties.

The Properties dialog box appears.

6. Select the Customer Information tab and complete your contact information.

7. Email your registration information. For contact information, go to the EMC CustomerNet portal at http://softwaresupport.EMC.com.

An authorization code that permanently enables the updated NetWorker software will be sent to you.

Task 3: Enter the authorization code

To complete the licensing process, you must enter the unique authorization code on the NetWorker server within 45 days of entering the license enabler code.

If the authorization process is successful, the expiration date for the license displays “Authorized - No expiration date.” If the authorization is not verified in this way, contact http://softwaresupport.EMC.com.

To avoid an interruption in scheduled backups if you move the NetWorker software from one computer to another, or to change the network address of a computer after the software is installed, perform one of the following:

◆ Obtain a new authorization code. You need the host ID of the original server as well as the new server. The host ID appears in the server’s Registration window. For contact information, go to the EMC CustomerNet portal at http://softwaresupport.EMC.com.

◆ Install and configure the EMC NetWorker License Manager software. “Managing NetWorker licenses” on page 8 provides information on use of the NetWorker License Manager, and the latest EMC NetWorker License Manager Installation and Administration Guide.

The licensing process 6-5






How to enter the authorization codeTo enter the authorization code:









4. In the left pane, select Registration.

5. In the right pane, select a license.

6. From the file menu, select Properties.

7. In the Auth Code attribute, type the authorization code for the product (the authorization code assigned to the specified permanent enabler or update enabler code).

8. Click OK.

The license is now permanently enabled.

Multiplatform licensingThe client connections that come with a NetWorker server can be used for only that server platform. A NetWorker ClientPak license allows the NetWorker server to back up clients of different platforms. For example:

◆ The client connections accompanying a NetWorker server for Microsoft Windows can be used for Windows client computers only.

◆ The client connections accompanying a NetWorker server for Solaris can be used for Solaris clients only.

With a ClientPak for UNIX, other UNIX platforms can be enabled for use with a NetWorker server for Solaris. The ClientPak for UNIX supports all UNIX platforms. The UNIX ClientPak is sufficient for all UNIX clients (backed up by a UNIX or Windows server).

Note: The NetWorker software treats Linux as a separate operating system. A ClientPak for Linux is necessary to back up Linux clients by either UNIX or Windows servers.

Example 6-1 Multiplatform licensing scenarios

A company was using a Linux server to back up Solaris, Linux, and Windows clients. It needed two ClientPak licenses, one for Solaris and one for Windows. The company added HP-UX and AIX clients, which required the addition of a ClientPak license for UNIX.

As the company grew and needed to add a server, it added a Windows 2000 server, which backed up the existing Windows clients and subsequent Windows 2000 clients without requiring a ClientPak. The company assigned the NetWorker server to a Solaris computer to back up the HP-UX, Solaris, and AIX clients by using a single ClientPak for UNIX.



Update enablers

To update existing NetWorker software to a major release, an update enabler is necessary. Update enablers are required for any major NetWorker software upgrade from release 4.0 and later, including the current NetWorker release. To use the NetWorker License Manager, the NetWorker server must be release 5.0 or later.

With a first-time purchase of NetWorker software, a one-year update agreement may be included. After a year, an update enabler may be acquired with a new update agreement purchase.

Table 6-1 on page 6-7 lists the NetWorker releases that require update enablers.

Additional licensesThis section describes a few of the additional licenses required to operate some of the NetWorker features.

Client connection licensesEvery computer to be backed up in a NetWorker datazone requires a client connection license, even the NetWorker server. The client connection license may be one of the licenses that is supplied with the base enabler or purchased separately. A cluster client or NDMP data server requires a special type of client connection license, as described in “Cluster clients” on page 8 or “NDMP licensing” on page 8.

Storage nodesEach storage node requires a storage node license, in addition to its client connection license. A dedicated storage node, which allows the storage node to back up only itself, is licensed separately.

Table 6-1 NetWorker update enablers

Upgrade from to 5.0 to 5.5 to 5.5.x to 5.6 to 5.7 to 6.x to 7.0 to 7.1 to 7.2 to 7.3

Any release prior to 5.0

yes yes yes yes yes yes yes yes yes yes

5.0 yes yes yes yes yes yes yes yes yes

5.5 yes yes (UNIX only)

yes (NT only)

yes yes yes yes yes

5.5.x yes (UNIX only)

yes (NT only)

yes yes yes yes yes

5.6 NA* yes yes yes yes yes

5.7 yes yes yes yes yes

6.0 no yes yes yes yes

7.0 yes yes yes

7.1 yes yes

7.2 yes

Note: * Release 5.6 is UNIX only, and release 5.7 is Microsoft Windows only. NT refers to Windows NT.

Multiplatform licensing 6-7


NetWorker Application Modules NetWorker Application Modules are licensed on the basis of one enabler per database type host. For example, to back up the Oracle database on two hosts, two NetWorker Module for Oracle enablers are required, even if the two hosts are backed up by the same server. However, if multiple database instances are running on a NetWorker client host, only one NetWorker Module enabler is required for that one host.

Cluster clientsFor each physical node in a cluster, you must purchase a Cluster Client Connection, which takes the place of one standard client connection. The NetWorker Administration Guide provides information on how to license computers in a cluster.

NDMP licensingNDMP licensing requires one NDMP Client Connection per NDMP data server. The NDMP Client Connection is valid for any supported NDMP data server. The NDMP data server does not require a standard client connection.

Managing NetWorker licensesThe NetWorker License Manager software provides centralized license management, allowing you to maintain all of an enterprise’s NetWorker licenses from a single computer. With the NetWorker License Manager, you can move NetWorker software from one computer to another, or change the IP address on an existing NetWorker server without having to reauthorize the software. The NetWorker License Manager can be installed as an option during the NetWorker software installation.

To begin to implement the NetWorker License Manager:

1. Contact EMC Licensing to obtain bulk enabler codes. For contact information, go to http://softwaresupport.EMC.com.

2. Install the NetWorker License Manager software.

3. Configure the NetWorker License Manager software.

4. Configure the NetWorker servers to access the NetWorker License Manager for their licenses.

The latest NetWorker License Manager Installation and Administration Guide provides more information on how to install and use the NetWorker License Manager.


Legato Win Installation

Documents

Transcript of Legato Win Installation