Академический Документы
Профессиональный Документы
Культура Документы
2
Solaris Version
INSTALLATION GUIDE
P/N 300-003-655 REV A01
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.
ii
Contents
Chapter 2
Chapter 3
NetWorker Installation
Software installation roadmap........................................................................................ 3-2 Software installation requirements................................................................................. 3-2 General requirements ................................................................................................. 3-2 TCP/IP requirements ................................................................................................. 3-3 Client software requirements.................................................................................... 3-3 Storage node requirements........................................................................................ 3-3 Storage device requirements ..................................................................................... 3-3 Server software requirements ................................................................................... 3-4 Console server software requirements .................................................................... 3-5 Estimating the space required for the Console database information ................ 3-7 Installing the NetWorker software ................................................................................. 3-9 Task 1: Access the NetWorker software .................................................................. 3-9 Task 2: Install the NetWorker software ................................................................. 3-10 Task 3: Change the NetWorker servers with access to a client .......................... 3-13 Task 4: Start the NetWorker daemons ................................................................... 3-14
Contents
iii
Contents
Verifying the installation ................................................................................................ 3-15 Task 1: Start Console for the first time................................................................... 3-15 Task 2: Add a NetWorker server to the Console server...................................... 3-16 Task 3: Configure a device....................................................................................... 3-16 Task 4: Test the NetWorker software installation ................................................ 3-18 Uninstalling the NetWorker software .......................................................................... 3-18 Software dependencies............................................................................................. 3-19 Uninstalling the software......................................................................................... 3-19
Chapter 4
Chapter 5
iv
Contents
Chapter 6
Chapter 7
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 from a Previous Release, describes how to update the NetWorker software from a previous release. Chapter 3, NetWorker Installation, describes how to access and install the NetWorker software from the distribution media in a Solaris environment. Chapter 4, EMC AutoStart Installation, describes how to access and install the NetWorker software in a EMC AutoStart environment. Chapter 5, Sun Cluster Version 3.0 or 3.1 Installation, describes how to install the NetWorker software in a Sun Cluster environment. Chapter 6, VERITAS Cluster Server Installation, describes how to install the NetWorker software in a VERITAS Cluster Server environment. Chapter 7, 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
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.
Courier italic
<> [] | ...
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.
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 7, Licensing and Enabling the Software.
1-4
2
Updating from a Previous Release
This chapter explains how to update from a previous release of NetWorker software. It includes the following sections:
2-1
Introduction
When updating to NetWorker release 7.3.2 from NetWorker release 6.x or earlier, there is no way to revert to a previous release of the NetWorker software. The client file indexes are automatically reorganized into new directory structures. It is a one-way conversion.
Task 1: Prepare to update the NetWorker software on the server on page 2-2 Task 2: Update the NetWorker software on page 2-3 Task 3: Enable and register the software on page 2-3
Note: Converting the NetWorker indexes from NetWorker 5.x to NetWorker 7.3.2 requires enough free disk space to match the largest client file index being converted. This space is used during the conversion process and will be released when completed. Following conversion, the media database should be approximately twice its original size. The client file indexes will be 20% to 40% smaller. These storage requirement changes are permanent.
3. Record the latest bootstrap save set ID and its associated volume label. To obtain this information, type the following command:
mminfo -B
4. If the NetWorker software is not currently installed in the default location, record the location of the client file indexes.
2-2
To update the NetWorker software on the NetWorker client, storage node, and server: 1. Keep a copy of the current configuration. 2. Shut down the NetWorker software using the following command:
nsr_shutdown
3. Remove the earlier NetWorker release, but do not remove the client file indexes, the resource files, and the media database. For information, see Uninstalling the NetWorker software on page 3-18. 4. Install the new release of the NetWorker software. For more information, see Installing the NetWorker software on page 3-9.
Note: Do not start the NetWorker daemons.
5. Apply any required NetWorker software patches. 6. Restart the NetWorker software by running the NetWorker startup script:
/etc/init.d/networker start
The media database and the client file index are converted automatically.
2-3
2-4
3
NetWorker Installation
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-9 Verifying the installation ........................................................................................................3-15 Uninstalling the NetWorker software...................................................................................3-18
NetWorker Installation
3-1
NetWorker Installation
4. Test the NetWorker software, see Verifying the installation on page 3-15. 5. Enable and register the NetWorker software, see Chapter 7, Licensing and Enabling the Software.
General requirements on page 3-2 TCP/IP requirements on page 3-3 Client software requirements on page 3-3 Storage node requirements on page 3-3 Storage device requirements on page 3-3 Server software requirements on page 3-4 Console server software requirements on page 3-5
Note: Before installing NetWorker software, ensure that the operating system is up-to-date with the most recent patches.
General requirements
NetWorker software does not support locales (defined by the operating system) or code sets that remap characters having special meaning for file systems. Depending on the file system, these special characters may include the slash (/), the backslash (\), the colon (:), or the period(.). For example, De_DE.646 is an unsupported locale. For information, refer to the NetWorker Administration Guide.
3-2
NetWorker Installation
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 /etc/hosts.
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.
At least one supported storage device must be attached and installed. The device can either be a stand-alone device, autochanger, or silo tape library. For a list of supported devices, refer to the EMC Information Protection Software Compatibility Guide. NetWorker software also supports the use of file type and advanced file type devices. For details, refer to the NetWorker Administration Guide.
3-3
NetWorker Installation
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.
The system meets the space requirements listed in Table 3-1 on page 3-5. There is a directory on the server large enough for the NetWorker client and server indexes and the media database (usually /nsr). The installation script checks for space and suggests one or more locations for the indexes and media database. The system pathname of at least one storage device is used by the NetWorker server to back up and recover files. If a tape device is being used to back up data, use a valid pathname for that device. For example: /dev/rmt/0cbn
Note: The tape device must be nonrewinding.
Acrobat Reader software has been installed. This software is required to read the documentation PDF files. Acrobat Reader requires a directory with enough space to install the software.
Installation guidelines On the NetWorker server, install all of the NetWorker software in the following order: 1. Client 2. Storage Node 3. Server 4. Console Server It is recommended that the NetWorker software packages all be installed on the server during the same installation session.
Note: If installing additional NetWorker software packages (storage node, server) to a NetWorker client that has processes running (for example, the nsrexecd process) an RPC error is reported. Before each software package is installed, the NetWorker software requires all NetWorker processes be shutdown. The RPC error is generated because the nsr_shutdown process attempts to stop NetWorker server processes when in fact no NetWorker server is running. This error message can be ignored and the installation process completes successfully.
During the pkgadd process, ensure that no NetWorker processes are running and do not start the NetWorker daemons until the final package is installed.
3-4
NetWorker Installation
Table 3-1 on page 3-5 lists the default locations on the server that the installation script uses, and the disk space required.
Table 3-1
Default locations and space requirements Software and documentation files NetWorker program files NetWorker daemon and utility command files (if you install LGTOlicm, add 1 MB) Online client file indexes; media database NetWorker device drivers (note that 39 MB of drivers are now installed in /usr/sbin) NetWorker server default location /usr/bin /usr/sbin /nsr /usr/kernel/drv /usr/sbin /usr/lib/nsr /usr/man /opt/Acrobat3/bin optional Space needed 13 MB 90 MB varies 40 MB
1 MB 8 MB varies
An installed and licensed network of NetWorker servers, clients, and storage nodes. 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.6.
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-2 provides a list of system requirements for installing the Console server and database.
Table 3-2
Console server system requirements (sheet 1 of 2) System feature Processor and RAM Requirement Minimum: 500 MHz with 128 MB of RAM; 512 MB to run reports. As the number of NetWorker 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 Solaris 7, 8, 9, 10 The following programs must already be installed and running: NetWorker client, release 7.3.2 NetWorker License Manager, release 7.3 .2
3-5
NetWorker Installation
Table 3-2
Console server system requirements (sheet 2 of 2) System feature Java Runtime Environment Browsers Requirement 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: Netscape Communicator 6.2.3 on the supported Solaris platforms Mozilla 1.4, 1.5, 1.7 on the supported Solaris platforms Solaris Server: 350 MB + x, where: x is a buffer of disk space for the Console database. For more information, see System requirements for the NetWorker Console client on page 3-6. JRE with Web Start: 55 MB
System requirements for the NetWorker 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. When connecting to the Console server for the first time, there is a prompt to download the JRE and the Console client application. Table 3-3 provides a list of system requirements for installing the Console client.
Table 3-3
Console client system requirements System feature Operating system Java Runtime Environment Browsers Requirement Solaris 7, 8, 9, 10 JRE starting from version 1.4.2, up to but not including 1.6. One of the following: Netscape Communicator 6.2.3 on the Solaris version 7, 8, and 9. Mozilla 1.4, 1.5, 1.7 on the supported Solaris version 7, 8, 9, and 10. Console client: 10 MB JRE with Web Start: 55 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).
3-6
NetWorker Installation
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.
Estimating space requirements for Console database information To estimate the total space required for save set media database information By the number of NetWorker servers monitored by the Console server By the number of weeks in the save set output policy
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.
Displaying international fonts in UNIX non-US locale environments Console software can run (in English mode) on localized operating systems; it supports retrieving double-byte characters from NetWorker data. If the appropriate non-English font is not available on the Console client, the retrieved data appears as gibberish. To use or view data from a localized, non-English NetWorker server: 1. Ensure that the appropriate font is available to the Console client. 2. Perform one of the following tasks: Change the language locale to match that of the localized NetWorker language locale. Choose a language font that is already loaded in the operating system and which matches the localized NetWorker language locale.
Note: You can select the Font from the View menu on the Console menu.
Changing the language locale to match that of the localized NetWorker data To change the language locale to match that of the localized NetWorker language locale. Choose one of the following:
Before login: a. Select Options on the Login dialog box. b. Select Options>Language. c. Select a locale from one of three alphabetical lists.
3-7
NetWorker Installation
After login: a. Type the setenv command to change the locale. b. Depending on the language, choose one of the following: To match the French NetWorker locale, type:
setenv LANG fr setenv LC_ALL fr
Changing the language font to view localized NetWorker data Instead of changing the language locale, you can change the Console font, so that localized NetWorker data can be viewed from the Console software. The font must be loaded in the operating system of the Console server and client. To load a font: 1. To select a language font, go to the Console menu and select View>Font. 2. In the Change Font dialog box, select the appropriate font. 3. Select a font size, if a size other than the default is needed and click OK. Using a non-US locale When using Console software in a non-US locale environment:
Support for the language locale and various language character sets comes from the host operating system. In order to display non-English characters, the host operating system must have installed a font (or fonts) that supports those characters. The Console client, rather than the Console server, must have the appropriate language character sets supported in the client operating system. By default, Console software uses a non-UNICODE font that supports US English. If the font is loaded in the operating system, a language locale that is supported by a localized version of NetWorker software automatically recognizes the font for the associated localized language. If the required font is loaded in the operating system, an appropriate language font can then be selected.
Note: If the required font is not installed on the system, obtain it from the operating system vendor and install it on the system.
3-8
NetWorker Installation
Task 1: Access the NetWorker software on page 3-9 Task 2: Install the NetWorker software on page 3-10 Task 3: Change the NetWorker servers with access to a client on page 3-13 Task 4: Start the NetWorker daemons on page 3-14
The NetWorker distribution software directories and files are listed on the screen as the extraction proceeds. The PATH environment variable for the user root on the NetWorker server and the user on each NetWorker client must contain the directory where the NetWorker executables reside. For information on this directory, see Table 3-1 on page 3-5.
3-9
NetWorker Installation
Client on page 3-10 Storage node on page 3-10 Server on page 3-10 Console server on page 3-11
Client To install the NetWorker software on the computer that is designated as the NetWorker client: 1. Type this command:
pkgadd -d /cdrom/cdrom1/solaris Note: Do not press the Enter key for the default response All. Accepting the default installs the server.
2. Type the appropriate option number to install the client package (LGTOclnt). The client package temporarily requires 35 MB of free space on the client computer. 3. (Optional) Type the appropriate option number to install the man pages (LGTOman). Storage node To install the NetWorker software on the computer that is designated as the NetWorker storage node and for which you have purchased an enabler code: 1. Type the following command:
pkgadd -d /cdrom/cdrom1/solaris
2. Type the appropriate options to install the following packages. Software packages on the storage node must be installed in the following order: LGTOclnt (client software package) LGTOnode (storage node software package) LGTOman (optional man pages) Server To install the NetWorker software on the computer that is designated as the NetWorker server: 1. Keep a copy of the current configuration. The NetWorker software installation script modifies the /etc/rpc and /etc/syslog.conf files during the installation process. Type the following commands:
cp /etc/rpc /etc/rpc.old cp /etc/syslog.conf /etc/syslog.conf.old
3-10
NetWorker Installation
3. Type the appropriate options to install the following packages. Software packages on the server must be installed in the following order: a. LGTOclnt (client software package) b. LGTOnode (storage node software package) c. LGTOserv (server software package) d. LGTOman (optional man pages) e. LGTOlicm (optional NetWorker License Manager software package) For information on the NetWorker License Manager software, refer to the NetWorker License Manager Installation and Administration Guide. Console server 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. To manage the NetWorker server, install the Console and NetWorker client software on one machine in the data zone. The Console server installation relies on the existence of several other components. Ensure that all installation prerequisites are met. For details, see Console server software requirements on page 3-5. To install NetWorker software on the computer that is designated as the Console server: 1. Ensure that JRE version 1.4.2_11 software is installed. This enables the command line reporting feature. a. If the NetWorker software had been downloaded from the web, type the following command to verify that execute permissions are applied to the JRE file. For example:
chmod +x /tmpdir/j2re-1_4_2_11-solaris-sparc.sh
The j2re-1_4_2_11-solaris-sparc.sh creates an install directory in the working directory where it is run. b. Change to the directory where the JRE is to be installed. c. Run the following script:
/tmpdir/j2re-1_4_2_11-solaris-sparc.sh
d. Accept the Java licensing agreement. 2. Start the NetWorker software installation:
pkgadd -d /cdrom/cdrom1/solaris Note: Do not press the Enter key for the default response All. Accepting the default installs the server.
3. Type the appropriate option number to install the client package (LGTOclnt), if not already installed. The client package temporarily requires 35 MB of free space on the client computer. 4. Type the appropriate option number to install the Console server package (LGTOnmc). 5. (Optional) Type the appropriate option number to install the man pages (LGTOman).
3-11
NetWorker Installation
6. Follow the prompts to install the software. For example: For the web server port number, use the default port number (9000) or use a custom port number. Valid port numbers are between 1024 and 49151. For the Console server, use the default port number (9001) or use a custom port number. Valid port numbers are between 1024 and 49151.
Note: Do not use port numbers that are already in use. Port 2638 is reserved by the Console server, using Tabular Data Stream (TDS) protocol to communicate with the database.
The Console daemon includes these processes: gstd dbsrv9 gsttclsh 8. 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 daemon process. If the Console server is on a: Windows host:
nsraddadmin -u "user=SYSTEM, host=console_host"
Where console_host is the Console server hostname. Installing to a nondefault location By default, the following NetWorker software is installed in the /usr directory. If there is insufficient disk space on the /usr partition, the following NetWorker packages can be relocated to a specified directory on another partition:
LGTOclnt (client software package) LGTOnode (storage node software package) LGTOserv (server software package)
By default, the Console server software is installed in the /opt directory. If there is insufficient disk space on the /opt partition, the Console server package, LGTOnmc can be relocated to a specified directory on another partition. The NetWorker man pages package (LGTOman) must always be installed in the default location. For a listing of the default locations and size requirements, see Table 3-1 on page 3-5.
Note: Do not relocate any of the packages if NetWorker Module software is already installed on the computer.
3-12
NetWorker Installation
To install the NetWorker packages to a nondefault location: 1. Copy the /var/sadm/install/admin/default file, as shown:
cp /var/sadm/install/admin/default /tmp/default.tmp
2. Edit the /var/sadm/install/admin/default file and change the value assigned to the basedir variable from default to ask, as shown:
basedir=ask
3. Create a directory and the bin and sbin subdirectories to install the NetWorker packages, for example:
mkdir -p /my_path/sbin mkdir -p /my_path/bin
4. Modify the root PATH variable to include the bin and sbin subdirectories of the directory just created, for example:
/my_path/bin:/my_path/sbin
When the following prompt appears in the script, type the same base directory for all the relocated packages:
Enter path to package base directory (default: /usr) [?,q] /my_path Using /my_path as the package base directory.
6. When all the applicable packages are added and the prompt appears, press [q] to exit. 7. Copy the /tmp/default.tmp file to the following location. For example:
cp /tmp/default.tmp /var/sadm/install/admin/default
If pkgrm is used to remove the packages at a later date, specify the base directory.
2. Edit or create the /nsr/res/servers file and add the set of NetWorker servers, one per line, that require access to the client. The first entry in this file becomes the default NetWorker server.
Note: If the /nsr/res/servers file is empty or does not exist, any NetWorker server is authorized to: - Access and back up the client. - Perform a directed recovery to the client.
3-13
NetWorker Installation
3. If necessary, remove the -s option from the nsrexecd command that is invoked by the boot-time startup file. Running nsrexecd with the -s option supersedes the following file:
/nsr/res/servers
a. Check the NetWorker boot-time startup file to see whether nsrexecd is being run with the -s option. The boot-time startup file for the Solaris environment is /etc/init.d/networker. b. If the -s option exists in the boot-time startup file, remove all occurrences of the following in the startup file:
-s server_name
Table 3-5 on page 3-14 lists the NetWorker daemons that should be running.
Note: The NetWorker daemon nsrmmd is only present if one or more devices are enabled.
Table 3-5
NetWorker daemons NetWorker installation packages NetWorker server NetWorker client NetWorker storage node NetWorker License Manager NetWorker daemons nsrd, nsrexecd, nsrindexd, nsrmmdbd, nsrmmd, nsrjobd, nsrmmgd, nsrlcpd nsrexecd nsrexecd, nsrmmd, nsrlcpd lgtolmd
3. If the output does not list nsrd and nsrexecd as current processes, run the following command to start the NetWorker daemons on the NetWorker server:
/etc/init.d/networker start Note: You might need to install the UTF-8 converters available with your operating system. For example: 0.
3-14
NetWorker Installation
Task 1: Start Console for the first time on page 3-15 Task 2: Add a NetWorker server to the Console server on page 3-16 Task 3: Configure a device on page 3-16 Task 4: Test the NetWorker software installation on page 3-18
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 screen, click Start. 5. If JRE 1.4.2 was not already installed on the system, a prompt to install it appears. Follow the instructions to install JRE. 6. In the NetWorker Management Console Login dialog box, type the username and password.
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.
3-15
NetWorker Installation
How to start 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 Console for the first time on page 3-15. Double-click the NetWorker Management Console product name in the Java Web Start Application Manager.
3-16
NetWorker Installation
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-17
NetWorker Installation
Software dependencies on page 3-19 Uninstalling the NetWorker software on page 3-18
3-18
NetWorker Installation
Software dependencies
The NetWorker software packages depend on each other. Uninstall them in the following order:
LGTOserv LGTOnode LGTOnmc If the Console server software is installed (LGTOnmc), there is a dependency on the NetWorker client software and the Console server software must be uninstalled first.
LGTOlicm If the NetWorker License Manager software is installed, there is a dependency on the NetWorker client software and the NetWorker License Manager software must be uninstalled first.
LGTOclnt LGTOman
Note: The man pages (LGTOman) and document files have no dependencies and can be uninstalled at any time.
4. Type the pkgrm command to remove the software. For example: To remove all the packages, type the following command:
pkgrm LGTOserv LGTOnode LGTOnmc LGTOlicm LGTOclnt LGTOman Note: Do not choose the default option All to remove the NetWorker software packages. Choosing this option removes all the software packages (not just NetWorker software) that were installed on the computer using the pkgadd utility.
3-19
NetWorker Installation
The LGTOnmc package must be uninstalled before the LGTOclnt package. Client software, type the following command:
pkgrm LGTOclnt
This removes the LGTOman package from the server, storage node, or client where the man pages are installed.
3-20
4
EMC AutoStart Installation
An EMC AutoStart cluster consists of multiple nodes in a networked configuration and provides additional security with the failover capability. Failover allows another node in the cluster to take over operations from the first node. For information, refer to the EMC AutoStart documentation. This chapter explains how to install NetWorker software in an EMC AutoStart environment. It includes the following sections:
Software installation roadmap ................................................................................................4-2 Installation requirements..........................................................................................................4-2 Installing a NetWorker virtual server.....................................................................................4-4 Installing a virtual Console server ..........................................................................................4-9 Installing only the NetWorker client software in a cluster ................................................ 4-11 Configuring an external client to a virtual server...............................................................4-13 Defining ownership of a raw partition for virtual clients .................................................4-13 Tracking scheduled saves .......................................................................................................4-14 Uninstalling the NetWorker software...................................................................................4-14
4-1
Installation requirements
The following sections discuss the software and hardware required to install and configure the NetWorker server or client software within an EMC AutoStart cluster environment:
Software requirements on page 4-2 Hardware requirements on page 4-2 Configuration options on page 4-3 System information requirements on page 4-3
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, ensure that the following software is installed on each node in the cluster:
Solaris version 2.7 or later EMC AutoStart release 5.1 or later NetWorker release 7.3
Note: Ensure that the most recent cluster patch for the operating system is installed.
Hardware requirements
To install the NetWorker software, ensure 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.
4-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
Figure 4-1
Installation requirements
4-3
Table 4-1
Required information Required information NetWorker virtual hostname with an IP address NetWorker package mount point for virtual volume Shared storage disk virtual volume NetWorker control script File containing the hostids of all the cluster members NetWorker monitor script Console hostname Console database mount point Example clus_vir1 192.168.1.10 /nsr_shared_mnt_pt /dev/dsk/c1t3d0s0 /usr/sbin/nw_ux.lc /nsr/res/hostids /usr/sbin/nw_ux.lc clus_vir2 192.168.1.11 nmc_shared_mnt_pt
Task 1: Ensure that the EMC AutoStart software is installed on page 4-4 Task 2: Install the NetWorker software in a cluster on page 4-4 Task 3: Define the NetWorker server as highly available on page 4-5 Task 4: Grant access to the NetWorker virtual server on page 4-6 Task 5: Configure the NetWorker server on page 4-7 Task 6: Configure clients under the NetWorker server on page 4-7 Task 7: Register NetWorker licenses for virtual server failover on page 4-8
4-4
Where: xx = 50 for EMC AutoStart version 5.0 xx = 51 for EMC AutoStart version 5.1 domain_name = EMC AutoStart domain 4. From each node in the cluster that will run the NetWorker server process: a. Run the cluster configuration script:
/usr/sbin/networker.cluster
b. Type the following information: Location of the local NetWorker database directory provided during the installation procedure:
/nsr
5. From one node in the cluster: a. Log in as administrator. b. Customize the following file:
/opt/LGTOnmc/bin/nw_ux.lc.aam5.imp
The nw_ux.lc.aam5.imp file is used to create the NetWorker resource group and its dependant objects in one step.
Note: In the nw_ux.lc.aam5.imp file, there are multiple instances of the NW Customize comment, ensure that all entries are replaced with the appropriate cluster configuration values.
4-5
Follow the instructions in the comments at the beginning of the nw_ux.lc.aam5.imp file to customize these default values based on the cluster configuration: Virtual hosts IP address:
192.168.1.10
Physical hostnames:
clus_phys1, clus_phys2
Device name:
/dev/dsk/c1t3d0s0
For a listing of the sample values provided, see Table 4-1 on page 4-4. c. Type the following command.
$FT_DIR/bin/ftcli -c import /opt/LGTOnmc/bin/nw_ux.lc.aam5.imp
d. Verify that the NetWorker resource group was imported correctly, using the EMC AutoStart Console. e. Run the following script located in the /usr/sbin directory:
nwinst.sh
To grant access to the NetWorker virtual server: 1. On each node in the cluster: a. Shut down the NetWorker processes and verify that all NetWorker daemons have stopped. b. Edit or create the /nsr.NetWorker.local/res/servers file: Add the set of NetWorker servers, one per line, that require access to this client. For each virtual NetWorker server, add an entry for each physical host and the virtual NetWorker server. For example:
clus_vir1 clus_phys1 clus_phys2
c. Check the NetWorker boot-time startup file to see whether nsrexecd is being run with the -s option. If the -s option exists, remove all occurrences of the following in the file:
-s servername
4-6
2. On one node in the cluster, start the NetWorker service using the cluster management software. a. Start the NetWorker Resource Group using the ftconsole. b. Edit or create the /nsr/res/servers file: Add the set of NetWorker servers, one per line, that require access to this client. For each virtual NetWorker server, add an entry for each physical host and the virtual NetWorker server. For example:
clus_vir1 clus_phys1 clus_phys2
3. If required, grant access to each NetWorker client that is outside of the cluster: a. Shut down the NetWorker processes and verify that all NetWorker daemons have stopped. b. Edit or create the /nsr/res/servers file: Add the set of NetWorker servers, one per line, that require access to this client. For each virtual NetWorker server, add an entry for each physical host and the virtual NetWorker server. For example:
clus_vir1 clus_phys1 clus_phys2
b. Click OK.
/nsr->/nsr.NetWorker.local /nsr.NetWorker.local->/var/nsr
4-7
To 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, type the name of the physical client. For information, refer to the NetWorker Administration Guide. 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, type the name of the virtual client. c. For the Remote Access attribute, add entries for each physical client within the cluster. For example:
root@clus_phys1
d. For the Group attribute, select a group. The first time the NetWorker application runs, it creates the Client resource for the NetWorker virtual server. For information, refer to the NetWorker Administration Guide. 4. Run a test probe to verify that the Client and Group resources have been properly configured. On the node on which the NetWorker server resides, run the following command:
savegrp -pv -c client_name group_name
If the test probe does not display the scheduled back ups and index, see Tracking scheduled saves on page 4-14.
4-8
For example:
12345678:87654321
5. Restart the server by taking the NetWorker virtual server offline and then putting it back online. 6. From the NetWorker Administration window, note the host ID number for the appropriate cluster license. 7. Register the NetWorker software. Customer Service will send you authorization codes using the composite host ID that was created in step 4.
Task 1: Install the Console server software in a cluster on page 4-9 Task 2: Define the Console server as highly available on page 4-9
3. Install the Console server (LGTOnmc) software on each node in the cluster. For instructions, see Installing the NetWorker software on page 3-9.
4-9
Where: xx = 5.0 for EMC AutoStart version 5.0 xx = 5.1 for EMC AutoStart version 5.1 domain_name = EMC AutoStart domain 4. From each node in the cluster that will run the Console server process: a. Run the cluster configuration script:
/opt/LGTOnmc/bin/gst_ha.cluster
The gst_ha_ux.aam5.imp file is used to create the Console resource group and its dependant objects in one step.
Note: In the gst_ha_ux.aam5.imp file, there are multiple instances of the NW Customize comment, ensure that all entries are replaced with the appropriate cluster configuration values.
Follow the instructions in the comments at the beginning of the gst_ha_ux.aam5.imp file to customize these NetWorker default values based on the cluster configuration: Virtual hosts IP address:
192.168.1.10
Physical hostnames:
clus_phys1, clus_phys2
Device name:
/dev/dsk/c1t3d0s0
For a listing of the sample values provided, see Table 4-1 on page 4-4. 6. Type the following command:
$FT_DIR/bin/ftcli -c import /opt/LGTOnmc/bin/gst_ha_ux.aam5.imp
The Console resource group is automatically created. 7. Verify that the Console resource group was imported correctly, using the EMC AutoStart Console.
4-10
Task 1: Install the NetWorker cluster client software on page 4-11 Task 2: Configure NetWorker client software as highly available on page 4-11 Task 3: Define the list of trusted NetWorker servers on page 4-12 Task 4: Configure clients under the NetWorker server on page 4-12
Note: Ensure that the NetWorker client software is installed on every node to be backed up in the cluster.
where: xx = 5.0 for EMC AutoStart version 5.0 xx = 5.1 for EMC AutoStart version 5.1 domain_name = Cluster domain 4. For each node in the cluster: a. Run the cluster configuration script:
/usr/sbin/networker.cluster
4-11
To define the list of trusted NetWorker servers, perform the following steps on each node in the cluster: 1. Shut down the NetWorker processes and verify that all NetWorker daemons have stopped. 2. Edit or create the /nsr/res/servers file: a. Add the set of NetWorker servers, one per line, that require access to this client. b. For each virtual NetWorker server, add an entry for each physical host and the virtual NetWorker server. For example:
clus_vir1 clus_phys1 clus_phys2
3. Check the NetWorker boot-time startup file to see whether nsrexecd is being run with the -s option. If the -s option exists, remove all occurrences of the following in the file:
-s servername
c. 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-12
3. Schedule backups using the NetWorker application. For instructions, refer to the NetWorker Administration Guide.
Note: The NetWorker server might reside outside of the cluster.
On each NetWorker client that is outside of the cluster: 1. Shut down the NetWorker processes and verify that all NetWorker daemons have stopped. 2. Edit or create the /nsr/res/servers file: a. Add the set of NetWorker servers, one per line, that require access to this client. b. For each virtual NetWorker server, add an entry for each physical host and the virtual NetWorker server. For example:
clus_vir1 clus_phys1 clus_phys2
For example:
IPOverride=135.69.103.149=/dev/rdsk/c1t3d0s1
Note: The IPOverride attribute does not add to the normal list of virtual client owned paths, but completely overrides them. In the previous example, if the virtual client also owns the filesystem /share/web, set the following path: IPOverrride=135.69.103.149=/dev/rdsk/c1t3d0s1, /share/web
4-13
If the test probe does not display all the scheduled save sets, do one of the following and run a second test probe to verify the configuration:
Check the cluster configuration. If necessary, reconfigure the cluster. Ensure that the save sets defined for the client are owned by that client. If necessary, redistribute the client save sets to the appropriate Client resources.
Note: Misconfiguration of the cluster resources might cause scheduled save sets to be dropped from the backup. For information, refer to the NetWorker Administration Guide.
To override scheduled save rules (not path ownership rules), run the following command on each node in the cluster:
touch networker_bin_dir/pathownerignore
This command allows any path to be backed up for a client, whether it is owned by the virtual client or physical node. For information, refer to the NetWorker Administration Guide. If pathownerignore was used, check that the NetWorker scheduled save uses the correct client index. If it uses the wrong index, save sets can be forced to go to a specific index: 1. From the NetWorker Administration window, select a client and edit its properties. 2. For the Backup Command attribute, type the name of a backup script that contains the following:
save -c client_name
For information about the Backup Command attribute, refer to the NetWorker Administration Guide.
3. Ensure that the following environment variables have been set: $FT_DIR $FT_DOMAIN 4. Run the following command:
/usr/sbin/networker.cluster -r
5. Remove the subsets for the following packages with the pkgrm command in the following order. For example:
pkgrm LGTOman LGTOserv LGTOnode LGTOnmc LGTOlicm LGTOclnt
4-14
5
Sun Cluster Version 3.0 or 3.1 Installation
This chapter explains how to install NetWorker software in a Sun Cluster version 3.0 or 3.1, environment. It includes the following sections:
Installation requirements..........................................................................................................5-2 Updating from a previous release of NetWorker software .................................................5-4 Installing NetWorker software in a cluster ............................................................................5-4 Installing a virtual Console server ........................................................................................5-14 Configuring an external client to a virtual server...............................................................5-19 Defining ownership of a raw partition for virtual clients .................................................5-20 Tracking scheduled saves .......................................................................................................5-20 Uninstalling the NetWorker software...................................................................................5-21 NetWorker Cluster script........................................................................................................5-21
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 Sun Cluster environment:
Software requirements on page 5-2 Hardware requirements on page 5-2 Configuration options on page 5-2 System information requirements for a highly available NetWorker server on page 5-2
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 a NetWorker virtual server, ensure that the following software is installed on each node in the cluster:
Solaris 8 or Solaris 9 operating environment is installed Sun Cluster version 3.0 or 3.1 is installed Volume Manager software (Solstice DiskSuite/Solaris Volume Manager)
Hardware requirements
To install the NetWorker software, ensure that the following hardware requirements are met for server installation only:
Multihosted disks that are used as a mount point for global file systems to contain the shared /nsr area. A device with local affinity for the local bootstrap backup that is connected to all the nodes within the cluster.
Configuration options
For information on how to configure the following, refer to the NetWorker Administration Guide:
Tape libraries with a NetWorker virtual server Remote physical storage node with a NetWorker virtual server
Node 1 is a computer with its own Local Disk. Node 2 is a computer with its own Local Disk. Highly available NetWorker Server on the Virtual Server owns Shared Disks.
5-2
In this example, the NetWorker server can fail over between Node 1 and Node 2; however, the NetWorker server only runs on one node at a time. The NetWorker server inherits the virtual servers IP address. Although NetWorker software is installed on all the physical nodes within the cluster, the server software is active on only one node at a time. If a hardware or software breakdown occurs on the node on which the NetWorker server is running, the NetWorker server moves to another node in the cluster. The NetWorker client software runs on all the physical nodes within the cluster, regardless of whether or not the NetWorker server resource group is running. This allows the backup of the physical client to proceed, as long as the node is running. Only one instance of the client software (nsrexecd) runs on each physical node within the cluster. The NetWorker client software is designed to recognize more than one client (physical client plus virtual client) that might be associated with a single physical node.
Node 2 clus_phys2
Local Disk
If Node1fails, clus_log1 fails over to Node2 NetWorker Logical Host (Virtual Server)
Local Disk
Public NetWork Sample Cluster Configuration. System Information Required information NetWorker virtual hostname with an IP address in the same subnet as the cluster nodes NetWorker globally mounted configuration area NetWorker cluster configuration script File containing the host ID of all the cluster members Example clus_vir1 192.168.1.10 /global/nw /usr/sbin/networker.cluster /nsr/res/hostids
Installation requirements
5-3
3. Use NetWorker software to back up the cluster. Ensure that you have a recent backup of the indexes and bootstrap using the savegrp -O command. 4. Remove the NetWorker software cluster configuration files and uninstall the NetWorker software. Do not remove the global and local /nsr directories. For instructions on uninstalling the NetWorker software, see Uninstalling the NetWorker software on page 5-21. 5. If required, upgrade the Sun Cluster software. For instructions, refer to the Sun Cluster documentation. 6. Install and configure the NetWorker 7.3 software.
Note: Do not relocate the NetWorker software. By default, the NetWorker is installed in the /usr directory.
Ensure that: You specify the same local /nsr and global /nsr directories. The NetWorker client type resource properties for Owned_paths and Clientname are the same as before the upgrade. The NetWorker Config_dir resource contains the same values as before the upgrade. The Network_resources_used property contains the same value that the Resource_dependencies property had before the upgrade. For instructions on installing NetWorker software in a Sun Cluster environment, see Installing NetWorker software in a cluster on page 5-4.
Installing a NetWorker virtual server on page 5-5 Installing a virtual Console server on page 5-14 Installing only the NetWorker client software in a cluster on page 5-16
Note: Do not relocate the NetWorker software. By default, the NetWorker is installed in the /usr directory.
5-4
Task 1: Install the NetWorker software on page 5-5 Task 2: Define the NetWorker server as highly available on page 5-6 Task 3: Create an instance of the NetWorker server resource group on page 5-7 Task 4: (Optional) add a HAStoragePlus resource to an existing NetWorker server resource group on page 5-8 Task 5: Grant access to the highly available NetWorker server on page 5-9 Task 6: Configure the NetWorker server on page 5-10 Task 7: Configure clients under the NetWorker server on page 5-10 Task 8: Create instances of the NetWorker client resource type on page 5-11 Task 9: Register licenses for the highly available NetWorker server on page 5-13 Task 10: Authorize the software on page 5-14
Task 1: Install the NetWorker software The NetWorker software must be installed on all nodes in the cluster that are required to run the NetWorker resource group. Ensure that the:
Solaris 8 operating environment and Sun Cluster 3.0 or 3.1 software are already installed on all nodes in the cluster and that those nodes boot in cluster mode. PATH environment variable includes /usr/sbin and /usr/cluster/bin.
To install the NetWorker software on nodes that will be running the NetWorker resource group: 1. Access the NetWorker software from the distribution media. For installation instructions, see Installing the NetWorker software on page 3-9. 2. Keep a copy of the current configuration. The NetWorker software installation script modifies the /etc/rpc and /etc/syslog.conf files during the installation process. Type the following commands:
cp /etc/rpc /etc/rpc.old cp /etc/syslog.conf /etc/syslog.conf.old
4. Press [Enter] to install all of the packages on the server. EMC recommends installing all the software on the server at the same time.
Note: Start the NetWorker daemons only after the last NetWorker package is installed.
Install selected software packages in the following order: a. LGTOclnt (client software package) b. LGTOnode (storage node software package) c. LGTOserv (server software package) d. LGTOman (optional man pages)
Installing NetWorker software in a cluster
5-5
6. Press [q] to exit. Do not relocate the NetWorker software. By default, the NetWorker is installed in the /usr directory. Task 2: Define the NetWorker server as highly available To define and configure the NetWorker server as highly available: 1. Log in as root. 2. Ensure that the /etc/hosts file on each cluster node contains the name of the logical host. The logical hostname can be published in the Domain Name System (DNS) or Network Information Services (NIS). 3. From each node in the cluster that will run the NetWorker server process: a. Run the cluster configuration script networker.cluster located in /usr/sbin. For an example of the script, see NetWorker Cluster script on page 5-21. This script defines the LGTOserv and the LGTOclnt resource types that the NetWorker software requires. b. In response to the following prompts, type the following information:
Enter directory where local NetWorker database is installed [/nsr]?
Type the location of the local NetWorker database directory provided during the installation procedure. For example: /space/nsr
Do you wish to configure for both NetWorker server and client? Yes or No [Yes]?
Type Yes to configure the server software. This also installs the client software by default. Type No to configure only the client software.
Do you wish to add now the site-specific values for: NSR_SHARED_DISK_DIR and NSR_SERVICE_ID Yes or No [Yes]?
Type the published logical hostname to be used by the highly available NetWorker server. For example: clus_vir1
In what path will this nsr directory be created/located?
Type the pathname of the globally mounted /nsr directory that will contain the configuration information for the highly available NetWorker server. For example:
/global/nw Note: To undo any changes to the configuration, run the networker.cluster -r script and then run the networker.cluster script again.
For information, see System information requirements for a highly available NetWorker server on page 5-2.
5-6
Task 3: Create an instance of the NetWorker server resource group A resource group must be created for the highly available NetWorker server. It must contain the following resources:
Logical hostname Globally mounted file system for the /nsr area LGTO.serv resource LGTO.clnt resource HAStoragePlus (optional)
To create an instance of the NetWorker server resource group, perform these steps on one node in the cluster: 1. Create a resource group:
scrgadm -a -g networker
3. (Optional), create an instance of the SUNW.HAStoragePlus resource type: a. Determine if the HAStoragePlus resource type is registered within the cluster:
scrgadm -p | egrep Type
If the logical host resource name is different than the hostname it specifies, use the following command to: a. Set the client name to the virtual hostname. b. Set the optional network_resource property to the logical host resource name. For example:
scrgadm -a -j client -t LGTO.clnt -g networker \ -x clientname=virtual_hostname -x network_resource=clus_vir1 \ -x owned_paths=/global/clus_vir1/nw,/global/clus_vir1/space
5-7
If the logical host resource name is different than the hostname it specifies, set the optional servername property to the virtual hostname:
scrgadm -a -j server -t LGTO.serv -g networker \ -y network_resources_used=clus_vir1 \ -x servername=virtual_hostname \ -x config_dir=/global/clus_vir1/nw Note: If you are using a HAStoragePlus resource, set resource_dependencies property to the HAStoragePlus resource name.
In the following example, a highly available NetWorker server uses the logical hostname backup_server. The highly available NetWorker server uses /global/networker (globally mounted file system) as its configuration directory. 1. Create a resource group with the name backups:
scrgadm -a -g backups
2. Add the logical hostname resource type to the resource group created in the previous step:
scrgadm -a -L -g backups -l backup_server
3. Create an instance of the LGTO.serv resource type with the name networker_server. This resource belongs to the resource group backups and has a dependency on the logical host created in the previous step. Specify the configuration directory on the globally mounted file system /global/networker:
scrgadm -a -j networker_server -t LGTO.serv -g backups \ -y network_resources_used=backup_server \ -x config_dir=/global/networker
4. The NetWorker logical host is also a client of the highly available NetWorker server. Create an instance of the LGTO.clnt resource type for the logical host backup_server within the resource group backups. The name of this resource is networker_client:
scrgadm -a -j networker_client -t LGTO.clnt -g backups \ -x clientname=backup_server -x owned_paths=/global/networker
5. Start the highly available service associated with the resource group backups.
scswitch -Z -g backups
Task 4: (Optional) add a HAStoragePlus resource to an existing NetWorker server resource group To add a SUNW.HAStoragePlus resource to an existing NetWorker server resource group: 1. Determine whether the HAStoragePlus resource type is registered within the cluster:
scrgadm -p | egrep Type
5-8
5. Set up a dependency for the NetWorker Server resource on the HAStoragePlus resource:
scrgadm -c -j server -y Resource_Dependencies=hastorageplus
Task 5: Grant access to the highly available NetWorker server Before a NetWorker server can back up a client, the client must grant the server access. Granting access is controlled by the servers file. For the node that is running the NetWorker Server resource group, this file is located in the globally mounted file system. Otherwise, this file is located on a local disk.
Note: If the /nsr/res/servers file is empty or does not exist, any NetWorker server is authorized to: - Access and back up the client. - Perform a directed recovery to the client.
To grant access to the highly available NetWorker server: 1. On one node in the cluster: a. Stop the NetWorker daemon using the cluster management software, as follows:
scswitch -F -g NetWorker
b. Edit or create the servers file in the globally mounted /nsr area. For example, /global/nw/res/servers: Add the set of NetWorker servers, one per line, to be granted access to this client. Add an entry for the NetWorker logical hostname first. Then add entries for each physical host that can run the NetWorker resource group. For example:
clus_vir1 clus_phys1 clus_phys2
2. On each node in the cluster: a. Shut down the NetWorker processes and verify that all NetWorker daemons have stopped:
nsr_shutdown ps -ef | grep nsr
b. Check the NetWorker boot-time startup file to see whether nsrexecd is being run with the -s option. If the -s option exists, remove all occurrences of the following in the file:
-s servername
c. Edit or create the /nsr.NetWorker.local/res/servers file: Add the set of NetWorker servers, one per line, that require access to this client. Add an entry for the NetWorker logical hostname first. Then add entries for each physical host that can run the NetWorker resource group. For example:
clus_vir1 clus_phys1 clus_phys2
5-9
3. On one node in the cluster, start the NetWorker daemon using the cluster management software, as follows:
scswitch -Z -g NetWorker
4. If required, grant access to the NetWorker virtual server on clients outside of the cluster: On each client that is outside of the cluster: a. Shut down the NetWorker processes:
nsr_shutdown
c. Edit or create the /nsr/res/servers file: Add the set of NetWorker servers, one per line, that require access to this client. Add an entry for the NetWorker logical hostname first. Then add entries for each physical host that can run the NetWorker resource group. For example:
clus_vir1 clus_phys1 clus_phys2
Task 6: Configure the NetWorker server To configure the NetWorker server: 1. Log in as root on the cluster node that is currently running the NetWorker server resource group. 2. Start the NetWorker Console software. 3. From the Administration window, select Properties from the File menu. a. For the Administrator attribute, add entries for any cluster nodes that are not already listed. For example:
root@hostname
b. Click OK. Task 7: Configure clients under the NetWorker server When the networker.cluster script runs, it creates a symbolic link named /nsr that points to a local disk. It also creates a second link named nsr.NetWorker.local that points to the local NetWorker directory. For example, if the local NetWorker directory was created in /var/nsr, each client member has the following links:
/nsr->/nsr.NetWorker.local /nsr.NetWorker.local->/var/nsr
5-10
To configure each client under the NetWorker server: 1. (Optional) Define save groups as required. 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. Type the name of the physical client for the Name attribute. For information, refer to the NetWorker Administration Guide 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, type the name of the virtual client. c. In the Remote Access attribute, add entries for each physical client within the cluster. For example:
root@clus_phys1
d. For the Group attribute, select a group. 4. Run a test probe to verify that the Client resource and the Group resource have been properly configured. On the node on which the NetWorker server resides, run the following command:
savegrp -pv -c client_name group_name
If the test probe does not display the correct scheduled backups and index, see Tracking scheduled saves on page 5-20. Task 8: Create instances of the NetWorker client resource type An instance of the NetWorker Client resource type must be created for each virtual client that accesses data on globally mounted file systems. Virtual clients in Sun Cluster 3.0 and 3.1 are either logical hostnames or shared addresses.
Note: All globally mounted file systems (except the /global/.devices/... file systems) must be owned by a resource group and defined in a NetWorker Client resource type. If the file systems are not properly configured, multiple copies will be backed up for each cluster node.
To back up the data for a virtual client: 1. Create an instance of the NetWorker Client resource as part of an existing resource group that contains a logical host or shared addresses. For example:
scrgadm -a -j resource_name -g resource_group_name -t LGTO.clnt \ -x clientname=virtual_hostname -x owned_paths=pathname_1, pathname_2[,...]
The virtual_hostname variable is a hostname specified by a logical hostname or shared address resource. By default, the logical hostname or shared address resource name is the same as the first hostname in the list of hostnames the resource controls.
5-11
If the logical hostname or shared address resource was explicitly named, set the optional network_resource property to the resource name:
scrgadm -a -j resource_name -g resource_group_name -t LGTO.clnt \ -x clientname=virtual_hostname -x network_resource=logicalhostname_ or_SharedAddress_resource_name \ -x owned_paths=pathname_1, pathname_2[,...]
For information, see the following examples: Example 5-2, A highly available Informix database server, on page 5-12 Example 5-3, A scalable Apache web server, on page 5-12 2. 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 savegroup_name
If the test probe does not display the scheduled backups and index, refer to the section on "Tracking Scheduled Saves" in the NetWorker Administration Guide.
Example 5-2
In the following example, the Informix database server is configured to use the DNS registered hostname informix_lhrs. An existing failover resource group named informix_rg contains:
This SUNW.informix database server can access data on a global file system under /global/informix/config and /global/informix/db. To add a NetWorker virtual client to the existing resource group informix_rg, type the following command:
scrgadm -a -j informix_clntrs -g informix_rg -t LGTO.clnt \ -x clientname=informix_lhrs \ -x owned_paths=/global/informix/config,/global/informix/db
Example 5-3
In the following example, an Apache web server is configured to use the DNS registered hostname apache_sars. An existing scalable resource group named apache_rg contains:
This Apache web server accesses data on a global file system under /global/web/config and /global/web/data. To add a NetWorker virtual client to the existing resource group apache_rg, type the following command:
scrgadm -a -j apache_clntrs -g apache_rg -t LGTO.clnt \ -x clientname=apache_sars \ -x owned_paths=/global/web/config,/global/web/data
5-12
Task 9: Register licenses for the highly available NetWorker server To register and license the highly available NetWorker server: 1. Order licenses from EMC for the type of NetWorker server and client configuration you are using. 2. Log on to the system that is currently running the NetWorker resource group. 3. Perform the following operations to type the purchased enabler codes: a. If you have been evaluating the NetWorker highly available software and have now purchased the software: Upgrade from the base evaluation enabler to the purchased enabler. Type the following command:
nsrcap -v -u base_enabler_code
This eliminates warning messages due to expiring evaluation enablers. b. For each enabler code, type the following command:
nsrcap -v -c enabler_code
4. Ensure that the highly available NetWorker server is defined as a part of the cluster. 5. On each node that is currently running the NetWorker server resource group, run the following command and capture the output:
hostid
This prints the numeric identifier of the current host. 6. Log on to the computer that is currently running the NetWorker server resource group. a. Create a file named /nsr/res/hostids that contains the host IDs of all the cluster nodes that were captured in the previous steps. Use the following syntax:
hostid1:hostid2:hostid3:...
For example:
12345678:87654321:13572468
b. Restart the server by taking the highly available NetWorker server offline and then putting it back online, as follows:
scswitch -F -g NetWorker scswitch -Z -g NetWorker
7. On one node in the cluster: a. Start the NetWorker Console. Use the logical hostname for the highly available NetWorker server. b. From the NetWorker Administration window, note the host ID number for the appropriate cluster license. c. Register the NetWorker software. Do not change the logical hostname for the highly available NetWorker server. If you change the logical host configuration for the highly available NetWorker server after you update the software, you must permanently license and authorize the highly available NetWorker server.
5-13
Task 10: Authorize the software To enter the permanent authorization code for NetWorker servers and clients: 1. On one node in the cluster, start the Console. Use the logical hostname for the highly available NetWorker server. 2. Complete the customer information and contact information fields: a. Start the Console software. b. From the Administration window, click Configuration. c. In the left pane, select the NetWorker server. d. From the File menu, select Properties. The Properties dialog box appears. e. Select the Customer Information tab and complete your contact information. f. Click Ok. 3. Review the registration information: a. From the Administration window, click Configuration. b. In the left pane, click Registration. c. In the right pane, right-click the license to be authorized, then select Properties. The Properties dialog box appears. d. Review the Auth Code attribute.
Task 1: Install the NetWorker Management software in a cluster on page 5-14 Task 2: Define the NetWorker Management server as highly available on page 5-14
Task 1: Install the NetWorker Management software in a cluster To install the NetWorker software on each node in the cluster: 1. Ensure that the most recent cluster patch for the operating system is installed. 2. Install the Console server software (LGTOnmc) on each node in the cluster. For instructions, see Installing the NetWorker software on page 3-9. Task 2: Define the NetWorker Management server as highly available To define and configure NetWorker server as a highly available application: 1. From each node in the cluster: a. Log in as root. b. Ensure that the /etc/hosts file on each cluster node contains the name of the logical host. The logical hostname can be published in the Domain Name System (DNS) or Network Information Services (NIS). 2. From each node in the cluster that will run the NetWorker server process: a. Run the cluster configuration script gst_ha.cluster located in /opt/LGTOnmc/bin/nsr. This script defines the GST_HA.serv resource type that the Console server requires.
5-14
Note: When running the gst_ha.cluster script, ensure that you use the same values for logical hostname and for the global mounted path for all node in the cluster. # ./gst_ha.cluster NMC Console Server is in the process of being made a Highly Available application within Sun Cluster 3.1.0,REV=2003.03.24.14.50.
To complete this task, the following are required. A Logical host or virtual IP for the Console server A globally mounted dir for the LGTOnmc database. A GST_HA.serv resource type will be created via this process and will be needed to configure NMC as a Highly Available Application within Sun Cluster 3.1.0,REV=2003.03.24.14.50.
Do you wish to continue? [Yes]? Restarting syslog daemon... Please enter Logical Hostname to be used by NMC server? hunt Is the Logical Hostname entered correct (y/n)? y The lgto_gstdb database should be on a globally mounted filesystem which can be accessible by the cluster nodes which will host the Highly Available NMC server. Please enter the globally mounted shared directory for the lgto_gstdb database (/global/logicalhost)? /global/hunt/data1 Is the shared directory path entered for the lgto_gstdb database correct (y/n)? y Moving /bigspace/lgto_gstdb local gstdb directory to globally mounted /global/hunt/data1/lgto_gstdb Resource type GST_HA.serv is not registered Defining GST_HA.serv resource type with RGM. NMC has been successfully cluster-configured.
5-15
3. From one node in the cluster: a. Create a resource group named "nmc":
# scrgadm -a -g nmc
Task 1: Install the NetWorker cluster client software on page 5-16 Task 2: Configure NetWorker client software as highly available on page 5-17 Task 3: Create instances of the client resource type on page 5-17 Task 4: Define the list of trusted NetWorker servers on page 5-18 Task 5: Configure clients under the NetWorker server on page 5-19
Note: Ensure that the NetWorker client software is installed on each node in the cluster. Do not relocate the NetWorker software. By default, the NetWorker is installed in the /usr directory.
To install the NetWorker software on the computer that is designated as the NetWorker client: 1. Access the NetWorker software from the distribution media. For details, see Installing the NetWorker software on page 3-9. 2. Type the pkgadd command:
pkgadd -d . Note: Do not press the [Enter] key for the default response All. Accepting the default installs the server package.
3. Type the appropriate option number to install the client package (LGTOclnt). The package temporarily requires 70 MB of free space on the client computer. 4. (Optional) Type the appropriate option number to install the man pages (LGTOman). 5. Start the NetWorker daemons:
/etc/init.d/networker start
6. When all the applicable packages have been added, and the prompt appears, press [q] to exit.
5-16
Task 2: Configure NetWorker client software as highly available To define and configure a NetWorker client as highly available: 1. Log in as root on each node where the NetWorker software is being installed. 2. Ensure that the /etc/hosts file on each cluster node contains the name of the virtual host. The virtual hostname can be published in the DNS or NIS. 3. For each node in the cluster: a. Run the cluster configuration script, /usr/sbin/networker.cluster. This script defines the LGTO.clnt resource types that the NetWorker software requires. b. In response to the prompts, type the following information:
Enter directory where local NetWorker database is installed [/nsr]?
Type the location of the local NetWorker database directory provided during the installation procedure. For example: /space/nsr
Do you wish to configure for both NetWorker server and client? Yes or No [Yes]?
For information, see System information requirements for a highly available NetWorker server
on page 5-2.
Task 3: Create instances of the client resource type An instance of the NetWorker Client resource type must be created for each virtual client that accesses data on globally mounted file systems. Virtual clients in Sun Cluster 3.0 and 3.1 are either logical hostnames or shared addresses.
Note: All globally mounted file systems (except the /global/.devices/... file systems) must be owned by a logical host and defined in a NetWorker Client resource type. If the file systems are not properly configured, multiple copies will be backed up for each cluster node.
To back up the data for a virtual client, from any node in the cluster, create an instance of the NetWorker Client resource as part of an existing resource group that contains a logical host or shared address. For example:
scrgadm -a -j resource_name -g resource_group_name -t LGTO.clnt \ -x clientname=virtual_hostname \ -x owned_paths=pathname_1, pathname_2[,...]
5-17
Example 5-4
In the following example, the Informix database server is configured to use the DNS registered hostname informix_lhrs. An existing failover resource group named informix_rg contains a:
This SUNW.informix database server can access data on a global file system under /global/informix/config and /global/informix/db. To add a NetWorker virtual client to the existing resource group informix_rg, type the following command:
scrgadm -a -j informix_clntrs -g informix_rg -t LGTO.clnt \ -x clientname=informix_lhrs \ -x owned_paths=/global/informix/config,/global/informix/db
Example 5-5
In the following example, an Apache web server is configured to use the DNS registered hostname apache_sars. An existing scalable resource group named apache_rg contains:
This Apache web server accesses data on a global file system under /global/web/config and /global/web/data. To add a NetWorker virtual client to the existing resource group apache_rg:
scrgadm -a -j apache_clntrs -g apache_rg -t LGTO.clnt \ -x clientname=apache_sars \ -x owned_paths=/global/web/config,/global/web/data
Task 4: Define the list of trusted NetWorker servers Before a NetWorker server can back up a client, the client must grant the server access. Granting access is controlled by the servers file. For the node that is currently running the NetWorker server resource group, this file is located in the globally mounted file system. Otherwise, this file is located on a local disk. Note: If the /nsr/res/servers file is empty or does not exist, any NetWorker server is authorized to: - Access and back up the client. - Perform a directed recovery to the client. To define the list of trusted NetWorker servers, perform the following steps on each node in the cluster: 1. Shut down the NetWorker processes and verify that all NetWorker daemons have stopped:
nsr_shutdown ps -ef |grep nsr
2. Edit or create the /nsr/res/servers file and add the set of NetWorker servers, one per line, that require access to this client.
5-18
3. Check the NetWorker boot-time startup file to see whether nsrexecd is being run with the -s option. If the -s option exists, remove all occurrences of the following in the file:
-s servername
Task 5: Configure clients under the NetWorker server 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 new NetWorker client. b. For the Name attribute, type 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: a. Create a new NetWorker client. b. For the Name attribute, type the name of the NetWorker server. c. For the Remote Access attribute, add entries for each physical client within the cluster. For example:
root@clus_phys1
d. For the Group attribute, select a group. 3. Schedule backups using the NetWorker application.
Note: The NetWorker server might reside outside of the cluster.
5-19
3. Edit or create the /nsr/res/servers file: a. Add the set of NetWorker servers, one per line, that require access to this client. b. Add an entry for the NetWorker logical hostname first. Then add entries for each physical host that can run the NetWorker resource group. For example:
clus_vir1 clus_phys1 clus_phys2
In the following example, a highly available web server uses the shared address web_server. The web server services are placed under the control of the resource group apache_rg. The services access files that are kept in two separate globally mounted file systems: /global/web/config and /global/web/data. The web server also accesses the raw partition /dev/md/hunt/rdsk/d30. To create the NetWorker Client resource named apache_nw, type the following:
scrgadm -a -j apache_nw -g apache_rg -t LGTO.clnt -x clientname=web_server \ -x owned_paths=/global/web/config,/global/web/data, /dev/md/hunt/rdsk/d30
For information on backing up raw partitions, refer to the rawasm command as described in the uasm(1m) man page.
If the test probe does not display all the scheduled save sets, do one of the following and run a second test probe to verify the configuration:
Check the cluster configuration. If necessary, reconfigure the cluster. Ensure that the save sets defined for the client are owned by that client. If necessary, redistribute the client save sets to the appropriate Client resources. Misconfiguration of the cluster resources might cause scheduled save sets to be dropped from the backup. For information, refer to the NetWorker Administration Guide.
To override scheduled save rules (not path ownership rules), run the following command on each node in the cluster:
touch networker_bin_dir/pathownerignore
This command allows any path to be backed up for a client, whether it is owned by the virtual client or physical node. For information, refer to the NetWorker Administration Guide.
5-20
If pathownerignore was used, check that the NetWorker scheduled save uses the correct client index. If it uses the wrong index, save sets can be forced to go to a specific index: 1. From the NetWorker Administration window, select a client and edit its properties. 2. For the Backup Command attribute, type the name of a backup script that contains the following:
save -c client_name
For details about the Backup Command, refer to the NetWorker Administration Guide.
networker.cluster -----------------------------------------------------------Sun Cluster 3.0 extends the Solaris operating environment into a cluster operating system. A cluster is a collection of loosely coupled computing nodes that provide a single client view of network services or applications. To complete this procedure, one must have a logical host defined on which the NetWorker server can be entered -----------------------------------------------------------Do you wish to continue? [Yes]? Yes Shutting down NetWorker services... Enter directory where local NetWorker database is installed [/nsr]? /space/nsr Restarting syslog daemon...
NetWorker Cluster script
5-21
Do you wish to configure for both NetWorker server and client? Yes or No [Yes]? Yes Do you wish to add now the site-specific values for: NSR_SHARED_DISK_DIR and NSR_SERVICE_ID Yes or No [Yes]? Yes Enter the Logical Hostname to be used for NetWorker? clus_vir1 The shared directory of the NetWorker server (the nsr directory) must be on a globally mounted file system. In what path will this nsr directory be created/located? /global/nw Creating /usr/sbin/nsr/lcmap file ... -rwxrwxr-x 1 root 1707 Aug 20 12:44 /usr/sbin/nsr/lcmap Finished creating /usr/sbin/nsr/lcmap file. resource type is not registered Defining LGTO.clnt resource type with RGM. resource type is not registered Defining LGTO.serv resource type with RGM. NetWorker has been successfully cluster-configured.
5-22
6
VERITAS Cluster Server Installation
This chapter explains how to install NetWorker software in a VERITAS Cluster Server 3.5, 4.0 environment. It includes the following sections:
Cluster concepts and terminology ..........................................................................................6-2 Software requirements..............................................................................................................6-4 Installing only the NetWorker client software in a cluster ..................................................6-4 Uninstalling the NetWorker software...................................................................................6-10 NetWorker Cluster script........................................................................................................6-10
Note: A stand-alone or highly available (virtual) NetWorker server is not supported in the cluster. The NetWorker server must be outside the cluster. Highly available storage nodes, physical storage nodes and the Console server are also not supported in the cluster.
6-1
Cluster terminology on page 6-2 About clustering on page 6-2 Cluster-aware and cluster-unaware NetWorker servers and clients on page 6-3
Cluster terminology
For consistency and clarity, this section defines the following terms: Node A physical machine that is a member in the cluster. Failover node A cluster node to which a highly available application can fail over. Virtual client A NetWorker client that is associated with a highly available or scalable service in a cluster. Cluster client A NetWorker cluster client is either a physical client or a virtual client. A physical client resource backs up data belonging to a physical node within a cluster. A virtual client resource backs up data belonging to a highly available or scalable service within a cluster. Virtual server A server that is configured as a highly available application within a cluster. Stand-alone NetWorker server A NetWorker server that is not highly available. Cluster-aware NetWorker server A NetWorker server that can recognize cluster clients.
About clustering
Clustering means that two or more nodes are connected and appear to network users as a single, highly available system. A highly available system allows the application services to continue despite most hardware or software failures. Each cluster node has its own IP address. Each cluster node might also have private (local) resources or disks that are available only to that computer. In addition to the nodes, a cluster can have one or more virtual services, each with its own IP address. A virtual service can have zero or more shared disks. Figure 6-1 on page 6-3 displays a general cluster configuration consisting of two or more nodes and at least one virtual server. In this illustration:
Node 1 is a computer with its own Local Disk. Node 2 is a computer with its own Local Disk. Virtual Server owns Shared Disks.
6-2
Node 1 clus_phys1 Private NetWork clus_log1 If Node1fails, clus_log1 fails over to Node2 Virtual Server
Node 2 clus_phys2
Local Disk
Local Disk
Public NetWork
Figure 6-1
In this example, the virtual server, clus_log1, can fail over between Node 1 and Node 2; however, the server only runs on one node at a time. The NetWorker client software runs on all the physical nodes within the cluster. This allows the backup of the physical client to proceed, as long as the node is running. Only one instance of the client software (nsrexecd) runs on each physical node within the cluster. The NetWorker client software is designed to recognize more than one client (physical client plus virtual client) that might be associated with a single physical node.
If a NetWorker server does not have cluster-client support, it cannot recognize cluster clients. When a scheduled backup is performed, the NetWorker server backs up only the private data of the physical node. The data is backed up to the same index representing the physical node. If a NetWorker client does not have cluster-client support, it backs up all data that belongs to the virtual servers and physical nodes into the same index representing the physical node. It does not recognize the difference between virtual and physical clients.
For information, refer to the EMC Information Protection Software Compatibility Guide.
6-3
Software requirements
Ensure that the following software is installed on each node in the cluster:
Solaris 7, 8 or 9 operating environment with Veritas Cluster Server (VCS) required patches VERITAS Cluster Server 3.5, 4.0 NetWorker release 7.3 VERITAS Volume Manager VxVM 3.5, 4.0 (optional) VERITAS File System VxFS 3.5 (optional)
For the most up-to-date information regarding software requirements, refer to the EMC Information Protection Software Compatibility Guide.
Task 1: Install the NetWorker cluster client software on page 6-4 Task 2: Configure NetWorker client software as highly available on page 6-5 Task 3: Register the NWClient resource type on page 6-5 Task 4: Define the list of trusted NetWorker servers on page 6-8 Task 5: Configure clients under the NetWorker server on page 6-8
Note: Ensure that the NetWorker client software is installed on each node in the cluster.
To install NetWorker software on the computer designated as the NetWorker client: 1. Access the NetWorker software from the distribution media. For installation instructions, see Installing the NetWorker software on page 3-9. 2. Type the pkgadd command:
pkgadd -d . Note: Do not press the [Enter] key for the default response All. Accepting the All response installs the server package.
6-4
3. Type the appropriate option number to install the client package (LGTOclnt). The package temporarily requires 70 MB of free space on the client computer. 4. (Optional) Type the appropriate option number to install the man pages, (LGTOman). 5. Start the NetWorker daemons: /etc/init.d/networker start 6. When all the applicable packages have been added, and the prompt appears, press [q] to exit.
This script creates NWClient resource types that may need to be added later to the VERITAS Cluster Server configuration. b. Type the following information in response to the prompts: Enter directory where local NetWorker database is installed [/nsr]? Type the location of the local NetWorker database directory provided during the installation procedure. For example: /space/nsr Do you wish to configure for both NetWorker server and client? Yes or No [Yes]? Type No. This configures only the client software.
Note: Any changes to the configuration can be undone by running the networker.cluster -r option and then running the networker.cluster script again.
Contain raw devices or logical volumes to back up. Contain more than one IP type resource. Are parallel with one or more IP type resources.
6-5
Creating an instance of NWClient resource type is optional if the following conditions exist:
The failover VERITAS Cluster service group has only one IP type resource. The owned filesystems on the shared devices are instances of the mount type resource contained in the same service group.
Check the VERITAS Cluster Server configuration to determine which, if any, service groups require one or more NWClient resources. If no such groups require NWClient resources, proceed to Task 4: Define the list of trusted NetWorker servers on page 6-8. About NWClient resources Before starting the steps in this task, review the information in this section to become familiar with the structure of an NWClient resource. The NWClient resource type definition is:
type NWClient ( static str ArgList[] = { IPAddress, Owned_paths } NameRule = NWClient_ + resource.IPAddress static str Operations = None str IPAddress str Owned_paths[] )
NWClient resource required attributes Required attributes IPAddress Type and dimension string, scalar Definition IP address of the virtual NetWorker client. An IP type resource with a matching Address attribute must exist in the service group. A list of filesystems or raw devices on a shared storage device. These filesystems or raw devices are owned by the virtual NetWorker client specified by the IPAddress attribute.
Owned_paths
string, vector
Example 6-1
6-6
Register resource type and create resource instances This section describes how to register the NWClient resource and create NWClient resource instances. To register the resource type and create resource instances: 1. Save the existing VERITAS Cluster Server configuration and prevent further changes while main.cf is modified:
haconf -dump -makero
2. Stop the VERITAS Cluster Server software on all nodes and leave the resources available:
hastop -all -force
4. Copy the NWClient resource definition file that is in the VERITAS Cluster Server configuration directory:
cp /etc/VRTSvcs/conf/NWClient.cf /etc/VRTSvcs/conf /config/NWClient.cf
5. Add the NWClient resource type and add NWClient resource type instances by editing the main.cf file: a. Add the NWClient resource type definition by adding an include statement to the main.cf file:
include "NWClient.cf"
b. Add an NWClient resource instance to every service group that contains an IP type resource and has associated filesystems or raw devices on shared storage. For information about a sample NWClient resource type instance, see "Example 6-1 NWClient resource sample configuration" on page 6. 6. Save and close the file. 7. Verify the syntax of the file, /etc/VRTSvcs/conf/config/main.cf:
hacf -verify config
9. Log in on the remaining nodes in the cluster and start the VERITAS Cluster Server engine:
hastart
6-7
To define the list of trusted NetWorker servers, perform the following steps on each node in the cluster: 1. Shut down the NetWorker processes and verify that all NetWorker daemons have stopped:
nsr_shutdown ps -ef |grep nsr
2. Edit or create the /nsr/res/servers file and add the set of NetWorker servers, one per line, that require access to this client. 3. Check the NetWorker boot-time startup file to see whether nsrexecd is being run with the -s option. If the -s option exists, remove all occurrences of the following in the file:
-s servername
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, type 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, type the name of the virtual client. c. For the Remote Access attribute, add entries for each physical client within the cluster. For example:
root@clus_phys1
6-8
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. Run a test probe to verify that the Client and Group resources have been properly configured. On the node on which the NetWorker server resides, run the following command:
savegrp -pv -c client_name group_name
If the test probe does not display the scheduled back ups and index, see Tracking scheduled saves on page 6-9.
If the test probe does not display all the scheduled save sets:
Check the cluster configuration using the cluster software. If necessary, reconfigure the cluster. Ensure that the save sets defined for the client are owned by that client. If necessary, redistribute the client save sets to the appropriate Client resources. Run the following command to override scheduled save rules (not path ownership rules), on each node in the cluster:
touch networker_bin_dir/pathownerignore
This command allows any path to be backed up for a client, whether it is owned by the virtual client or physical node. For information, refer to the NetWorker Administration Guide. If pathownerignore was used, check that the scheduled save uses the correct client index. If the wrong index is used, force save sets to go to a specific index: 1. From the NetWorker Administration window, select a client and edit its properties. 2. For the Backup Command attribute, type the name of a backup script that contains the following:
save -c client_name
For information about the Backup Command attribute, refer to the NetWorker Administration Guide.
6-9
A list of NetWorker daemons to be shut down appears, and you are prompted whether to continue. d. Type the following command to remove: All the packages:
pkgrm LGTOclnt LGTOman
networker.cluster --------------------------------------------------------------Veritas Cluster Server is a high availability product. Only cluster-aware NetWorker Client is supported in the cluster. --------------------------------------------------------------Do you wish to continue? [Yes]? Shutting down NetWorker services... Enter directory where local NetWorker database is installed [/nsr]? /space2/nsr Restarting syslog daemon... Creating /usr/sbin/lcmap file ... -rwxrwxr-x 1 root 5860 Jul 29 11:56 /usr/sbin/lcmap Finished creating /usr/sbin/lcmap file. NetWorker has been successfully cluster-configured.
6-10
7
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 Legato 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 .....................................................................................7-2 The evaluation process .............................................................................................................7-2 The licensing process ................................................................................................................7-3 Multiplatform licensing ............................................................................................................7-6 Managing NetWorker licenses.................................................................................................7-8
7-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 73 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 73 provides instructions. Multiplatform licensing on page 76 provides information on the different NetWorker features.
7-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 74 Task 2: Obtain an authorization code on page 74 Task 3: Enter the authorization code on page 75
7-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.
7-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 78 provides information on use of the NetWorker License Manager, and the latest EMC NetWorker License Manager Installation and Administration Guide.
7-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 7-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.
7-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 7-1 on page 7-7 lists the NetWorker releases that require update enablers.
Table 7-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 78 or NDMP licensing on page 78. 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
7-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.
7-8