Professional Documents
Culture Documents
2
Microsoft Windows Version
INSTALLATION GUIDE
P/N 300-003-653 REV A01
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.
ii
Contents
Chapter 2
Chapter 3
3-2 3-2 3-2 3-3 3-3 3-4 3-4 3-4 3-5 3-7 3-7 3-7 3-8 3-9
iii
Contents Verifying the installation ................................................................................................ Task 1: Start the Console for the first time ............................................................ Task 2: Add a NetWorker server to the Console server...................................... Task 3: Configure a device....................................................................................... Task 4: Test the NetWorker software installation ................................................ Uninstalling the NetWorker software .......................................................................... 3-11 3-11 3-12 3-12 3-14 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-3 Installing a NetWorker server for cluster mode..................................................... 4-4 Configuring a backup device for the NetWorker virtual server ................................ 4-9 Defining 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-12 Uninstalling NetWorker software from only one node in the cluster .............. 4-12 Troubleshooting NetWorker software in the MSCS environment ........................... 4-13 NetWorker virtual server fails to start nsrmmd................................................... 4-13 NetWorker server fails to back up a virtual cluster client .................................. 4-13 NetWorker services fail to start in an MSCS environment ................................. 4-14
Chapter 5
iv
Contents
Chapter 6
Contents
Contents
vi
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. Audience This 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:
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 documentation For 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 guide EMC 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 conventions EMC 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 Book titles New terms in text Emphasis in text Prompts System output Filenames Pathnames URLs Syntax when shown in command line or other examples
italic
Courier
Courier, bold
Courier italic
User entry Options in command-line syntax 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.
<> [] | ...
viii
Preface
Where to get help For information about software patches, technical documentation, support programs, sales, and licensing, go to:
http://softwaresupport.EMC.com
Your comments Comments and suggestions about our product documentation are always welcome. To provide feedback: 1. Go to:
http://softwaresupport.EMC.com
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
Preface
1
Introduction
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
1-1
Introduction
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.
NetWorker client NetWorker storage node NetWorker server NetWorker Management Console NetWorker License Manager
NetWorker client
The 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.
Control over which clients use the storage nodes devices for backups License management Management of the client file indexes that track each clients 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 nodes enabler on the server must be of the same edition as the base enabler for the NetWorker server.
1-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 clients data. Manage the media database that tracks the data contained on each volume.
1-3
Introduction
Supported devices
NetWorker 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:
Enabler codes
Enabler 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.
1-4
2
Updating the Software
This chapter explains how to upgrade, maintain, or uninstall NetWorker software. It includes the following sections:
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.
2-1
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.
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.
2-2
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.
2-3
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.
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. 10. 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.
2-4
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.
Note: If the Selected Servers list is left empty, any NetWorker server can perform backups and directed recoveries of this computers 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.
2-5
6. In the Welcome to NetWorker and NetWorker Management Console Installation page, select Install NetWorker Management Console. The Setup program detects the existing NetWorker installation and automatically runs in maintenance mode. 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. 13. In the NetWorker Setup Complete page, select Finish.
Note: The Setup program stops the NetWorker services if necessary, replaces any corrupted or missing files, and then restarts the NetWorker services.
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
2-6
3
Installing the Software
This chapter explains how to install, update, or uninstall NetWorker software. It includes the following sections:
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
3-1
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.
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.
3-2
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 requirements
The 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 servers TCP/IP hostname and Windows computer name must be the same.
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.
3-3
Windows 2000 with the latest service pack installed (Server, Advanced Server, Enterprise Server, and Datacenter Editions) 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.
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 Consoles consolidated reporting feature.
Windows 2000 with the latest service pack installed (Server, Advanced Server, Enterprise Server, and Datacenter Editions) 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.
3-4
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 tobut not includingversion 1.5.
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 Consoles consolidated reporting feature.
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 Requirement Minimum: 500 MHz with 128 MB of RAM, 512 MB to run reports As the number of servers being monitored increases, increase the computers capabilities. For 50 servers: Dual 500 MHz with no less than 192 MB For 100 servers: Dual 800 MHz with no less than 256 MB For 200 servers: Dual 1.3 GHz with no less than 512 MB One of the following Microsoft Windows operating systems: 2000, with SP4 2003, 32-bit 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. 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. 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. 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.
Operating system
Software
3-5
System requirements for the Console client Although 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.
Table 3-2
Console client system requirements Requirement One of the following: Microsoft Windows 2000, with SP4 Microsoft Windows 2003, 32-bit Microsoft Windows XP with SP1 JRE starting from version 1.4.2, up to but not including 1.6. 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 Console client: 5 MB JRE with Web Start: 50 MB A minimum of 512 MB to run reports 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 size of the Console database The 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.
3-6
Estimating space requirements for Console database information By the number of NetWorker servers monitored by the Console server By the number of weeks in the save set output policy
To estimate the total space required for save set media database information
The results indicate 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. The number of save set output describes how many groups and save sets were attempted and their success or failure. All save output data that could be used to troubleshoot backup problems.
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
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 computers 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.
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 website To 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.
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 Consoles 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. 3. Double-click the setup.exe file. Skip this step if Autorun started the installation automatically. 4. In the Welcome to NetWorker and NetWorker Management Console Installation page, select Install NetWorker. 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.
3-8
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 Administrators Guide.
7. The installation program is ready to install. Review the settings and click Install. 8. 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.
Note: If the Selected Servers list is left empty, any NetWorker server can perform backups and directed recoveries of this computers 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.
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.
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 systems 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.
3-10
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
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.
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 time After 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.
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 device To configure a stand-alone tape device: 1. In the servers 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.
3-12
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 device To configure a stand-alone file or advanced files device: 1. In the servers NetWorker Administration interface, click Devices. 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 silo To configure a new library resource (autochanger or silo) to a storage node: 1. In the servers 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 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.
3-13
To uninstall the NetWorker software from a host computer: 1. Log on with administrator privileges to the target 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.
3-14
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.
3-15
3-16
4
MSCS Installation
This chapter provides instructions for installing and configuring NetWorker software in a Microsoft Cluster Server (MSCS) environment. It includes the following sections:
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
4-1
MSCS Installation
Cluster terminology
EMC 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 requirements
This 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.
4-2
MSCS Installation
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.
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.
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 software On 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.
4-4
MSCS Installation
Task 2: Create and register the NetWorker server cluster resource type To 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
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 type To 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 servers virtual identity. The resource type Physical Disk is for the shared nsr directory. Task 4: Create an MSCS group resource and required components resource To 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.
4-5
MSCS Installation
NetWorker IP address resource To 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 resource To create a NetWorker Network Name resource: 1. In the Cluster Administrator program, select File>New>Resource. 2. Complete the following attributes:
Name: NSR_NetworkName Description: NetWorker Network Name Resource Type: Network Name 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: 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
4-6
MSCS Installation
NetWorker server resource To create a NetWorker Server resource: 1. In the Cluster Administrator program, select File>New>Resource. 2. Complete the following attributes:
Name: NSR_Server Description: NetWorker Server Resource Resource Type: NetWorker Server Group: NetWorker Group 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.
3. Click Next. In the Possible Owners dialog box, type the hostname of each required node in the cluster. For example:
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 online To 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.
4-7
MSCS Installation
Task 6: Configure the NetWorker virtual server To 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 server To 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). 3. Start the NetWorker Management Console software. 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).
4-8
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.
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 servers 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.
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.
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.
MSCS Installation
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.
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.
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
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.
4-12
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.
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.
charon virtual cluster client running on pluto pluto physical cluster node neptune NetWorker server
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.
4-14
5
EMC AutoStart Installation
This chapter explains how to install NetWorker software in an EMC AutoStart environment. It includes the following sections:
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
5-1
Installation requirements
The 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 requirements
To 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 client The 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.
5-2
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
Node 2 clus_phys2
Local Disk
Local Disk
Public NetWork
Figure 5-1
Installation requirements
5-3
Table 5-1
Information Required During NetWorker Virtual Server Installation Required information Pathname for the shared nsr directory Server name of the NetWorker virtual server Server netmask Domain name for the EMC AutoStart server (Domain names are case-sensitive) Installation directory pathname Server names of first and second physical hosts in the EMC AutoStart Cluster. Server names must not exceed fifteen characters in length. Example s:\nsr jupiter 255.255.255.0 galaxy C:\Program Files\emc\ AAM\galaxy mars saturn
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
5-4
Task 4: Create the resource that will become the managed shared disk
On 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.
5-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_config C:\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.clustersvr Enter shared nsr dir:s:\nsr Enter the Legato Cluster domain name:galaxy Enter 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 = galaxy Legato Cluster software location = C:\Program Files\Legato AAM\galaxy Is 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.
5-6
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" Created Process Class "nsrd" Created Process "NSRserver" Created Configuration "NSRserver" Created Process Class "nsrexecd" Created Process "NSRexecd" Created Configuration "NSRexecd" Created Data Source "networker_ds" Created Resource Group "networker" Created OK
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.
2. From the Administration window, select Properties from the File menu.
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.
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: a. Create a new NetWorker client. 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
5-8
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.
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 servers 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.
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.
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.
5-9
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.
2. Make each virtual client within the cluster a client of the NetWorker server. For each virtual client in the cluster: a. Create a new NetWorker client. 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_config Checking for C:\Program Files\Legato\nsr\bin\lcmap.bat Checking for C:\Program Files\Legato\nsr\bin\NetWorker.clustersvr Enter shared nsr dir: Enter the Legato Cluster domain name:galaxy Enter the directory in which your Legato Cluster software is installed (typically something like C:\galaxy): C:\Program Files\Legato AAM\galaxy
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.
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.
Troubleshooting
The following sections contain troubleshooting tips for NetWorker software in a EMC AutoStart environment.
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.
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.
5-12
5-13
5-14
6
Licensing and Enabling the Software
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
6-1
By evaluating a new installation of the software on a NetWorker server By evaluating NetWorker features on an existing NetWorker installation
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.
6-2
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: 1. Start the NetWorker Management Console software. 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. The Administration window is launched as a separate application. 3. From the Administration window, click Configuration. 4. In the left pane, select Registration. 5. From the File menu, select New. 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.
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
6-3
To enter the license enabler code: 1. Start the NetWorker Management Console software. 2. Launch the Administration window: a. From the Console window, click Enterprise. 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. The Administration window is launched as a separate application. 3. In the Administration window, click Configuration. 4. In the left pane, select Registrations. 5. From the File menu, select New. 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.
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.
6-4
By using the EMC website Register 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 email To register the software and obtain an authorization code by email: 1. Start the NetWorker Management Console software. 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, click the application. d. From the Enterprise menu, select Launch Application. The Administration window is launched as a separate application. 3. In the Administration window, click Configuration. 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.
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 servers 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.
6-5
How to enter the authorization code To enter the authorization code: 1. Start the NetWorker Management Console software. 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, click the application. d. From the Enterprise menu, select Launch Application. The Administration window is launched as a separate application. 3. In the Administration window, click Configuration. 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 licensing
The 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
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.
6-6
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.
Table 6-1
NetWorker update enablers to 5.5 yes yes to 5.5.x yes yes yes to 5.6 yes yes yes (UNIX only) yes (UNIX only) to 5.7 yes yes yes (NT only) yes (NT only) NA* to 6.x yes yes yes to 7.0 yes yes yes to 7.1 yes yes yes to 7.2 to 7.3 yes yes yes yes yes yes
to 5.0 yes
5.5.x
yes
yes
yes
yes
yes
yes yes no
Note: * Release 5.6 is UNIX only, and release 5.7 is Microsoft Windows only. NT refers to Windows NT.
Additional licenses
This section describes a few of the additional licenses required to operate some of the NetWorker features. Client connection licenses Every 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 nodes Each 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.
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 clients For 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 licensing NDMP 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.
6-8