linuxig_7.3.2

7/28/2019 linuxig_7.3.2

1/82

EMC Corporation

Corporate Headquarters:

Hopkinton, MA 01748-91031-508-435-1000www.EMC.com

EMCNetWorker

Release 7.3.2Linux Version

INSTALLATION GUIDE

300-003-651

7/28/2019 linuxig_7.3.2

2/82

EMC NetWorker for Linux, Release 7.3.2, Installation Guideii

Copyright September 2006 EMC Corporation. All rights reserved.

Published September 2006

EMC believes the information in this publication is accurate as of its publication date. The information is subject to changwithout 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 THISPUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software licens

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.

7/28/2019 linuxig_7.3.2

3/82

iii

Contents

Chapter 1 Introduction

About the NetWorker product ........................................................................................ 1-2NetWorker client......................................................................................................... 1-2NetWorker storage node............................................................................................ 1-2

NetWorker server ....................................................................................................... 1-3NetWorker Management Console............................................................................ 1-3NetWorker License Manager .................................................................................... 1-3

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

Chapter 2 Updating from a Previous Release

Introduction ....................................................................................................................... 2-2Updating from a previous release .................................................................................. 2-2

Task 1: Prepare to update the NetWorker software on the NetWorker server . 2-2Task 2: Update the NetWorker software................................................................. 2-2

Chapter 3 Linux for Intel x86 Installation

Software installation roadmap........................................................................................ 3-2Installation requirements ................................................................................................. 3-2

General requirements................................................................................................. 3-3TCP/IP requirements................................................................................................. 3-3Client software requirements.................................................................................... 3-3Storage node software requirements ....................................................................... 3-4Server software requirements ................................................................................... 3-4Console server software requirements .................................................................... 3-6Estimating the space required for the Console database information................ 3-8

Installing the NetWorker software ............................................................................... 3-10Task 1: Access the NetWorker software ................................................................ 3-10

Task 2: Install the NetWorker software ................................................................. 3-11Task 3: Change the NetWorker servers with access to a client .......................... 3-15Task 4: Start the NetWorker daemons ................................................................... 3-15

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

Uninstalling the NetWorker software .......................................................................... 3-19

7/28/2019 linuxig_7.3.2

4/82

EMC NetWorker for Linux, Release 7.3.2, Installation Guideiv

Chapter 4 Linux for Itanium Processor Installation

Software installation roadmap ........................................................................................ 4-2Installation requirements ................................................................................................. 4-2

General requirements................................................................................................. 4-2TCP/IP requirements................................................................................................. 4-3Client software requirements.................................................................................... 4-3

Storage node software requirements ....................................................................... 4-4Server software requirements ................................................................................... 4-4

Installing the NetWorker software.................................................................................. 4-6Task 1: Access the NetWorker software .................................................................. 4-6Task 2: Install the NetWorker software ................................................................... 4-7Task 3: Change the NetWorker servers with access to a client ............................ 4-9Task 4: Start the NetWorker daemons ................................................................... 4-10

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

Uninstalling the NetWorker software .......................................................................... 4-14

Chapter 5 EMC AutoStart Installation

Software installation roadmap ........................................................................................ 5-2Installation requirements ................................................................................................. 5-2

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

Installing a NetWorker virtual server............................................................................. 5-4Task 1: Ensure that the EMC AutoStart software is installed............................... 5-4Task 2: Install the NetWorker software in a cluster............................................... 5-4Task 3: Define the NetWorker server as highly available..................................... 5-4Task 4: Grant access to the NetWorker virtual server ........................................... 5-6Task 5: Configure the NetWorker server................................................................. 5-7Task 6: Configure clients under the NetWorker server......................................... 5-7Task 7: Register NetWorker licenses for virtual server failover .......................... 5-8

Installing a virtual Console server.................................................................................. 5-9Task 1: Install the NetWorker Management software in a cluster....................... 5-9Task 2: Define the Console server as highly available........................................... 5-9

Installing only the NetWorker client software in a cluster........................................ 5-10Task 1: Install the NetWorker cluster client software.......................................... 5-10Task 2: Configure NetWorker client software as highly available .................... 5-11Task 3: Define the list of trusted NetWorker servers........................................... 5-11Task 4: Configure clients under the NetWorker server....................................... 5-12

Configuring an external client to a virtual server ...................................................... 5-12Defining ownership of a raw partition for virtual clients ......................................... 5-13Tracking scheduled saves............................................................................................... 5-13Uninstalling the NetWorker software .......................................................................... 5-14

7/28/2019 linuxig_7.3.2

5/82

v

Chapter 6 Licensing and Enabling the Software

How NetWorker software is licensed............................................................................. 6-2The evaluation process..................................................................................................... 6-2

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

The licensing process........................................................................................................ 6-3

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

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

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

Appendix A Sample stinit.def File

Usage .................................................................................................................................. A-2Examples of the stinit file ................................................................................................ A-2

Appendix B stinit(8) Man Page

Synopsis ............................................................................................................................. B-2Description ........................................................................................................................ B-2Options .............................................................................................................................. B-2The devices being initiated ............................................................................................. B-2Return value ...................................................................................................................... B-4Restrictions ........................................................................................................................ B-5

7/28/2019 linuxig_7.3.2

6/82

EMC NetWorker for Linux, Release 7.3.2, Installation Guidevi

7/28/2019 linuxig_7.3.2

7/82

vii

Preface

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

Audience

This guide is part of the NetWorker documentation set, and is intended for use by systemadministrators during the installation of NetWorker software.

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

EMC NetWorker software Linux software

Organization

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

Chapter 1, Introduction, provides a description of NetWorker and supportingsoftware, including features, components, and functions.

Chapter 2, Updating from a Previous Release, describes how to update the NetWorkersoftware from a previous release.

Chapter 3, Linux for Intel x86 Installation, describes how to access and install theNetWorker software from the distribution media in a Linux for Intel x86 environment.

Chapter 4, Linux for Itanium Processor Installation, describes how to access and installthe NetWorker software from the distribution media in a Linux for Itanium processorenvironment.

Chapter 5, EMC AutoStart Installation, describes how to install the NetWorkersoftware in a EMC Autostart cluster environment.

Chapter 6, Licensing and Enabling the Software, describes how to license and enablethe NetWorker software.

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 Software Compatibility Guide

7/28/2019 linuxig_7.3.2

8/82

EMC NetWorker for Linux, Release 7.3.2, Installation Guideviii

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 ordamage to the system orequipment. The caution may apply to hardware or software.

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

Where to get help

For information about software patches, technical documentation, support programs, salesand 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 commeon a particular guide.

bold User actions (what the user clicks, presses, or selects) Interface elements (button names, dialog box names)

Names of keys, commands, programs, scripts, applications, utilities, processes,notifications, system calls, services, applications, and utilities in text

italic Book ti tles New terms in text

Emphasis in textCourier Prompts

System output

Filenames

Pathnames

URLs

Syntax when shown in command line or other examples

Courier, bold User entry

Options in command-line syntax

Courier italic Arguments in examples of command-line syntax

Variables in examples of screen or file output

Variables in pathnames

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

[] Square brackets for optional values.

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

... Ellipsis for nonessential information omitted from the example.
http://softwaresupport.emc.com/http://softwaresupport.emc.com/http://softwaresupport.emc.com/http://softwaresupport.emc.com/

7/28/2019 linuxig_7.3.2

9/82

Introduction 1-1

1

Introduction

This chapter provides background information on EMC NetWorker software andsupported devices.

It includes the following sections:

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

7/28/2019 linuxig_7.3.2

10/82

EMC NetWorker for Linux, Release 7.3.2, Installation Guide1-2

Introduction

About the NetWorker product

The NetWorker product is a suite of storage management software that provides backup,recovery, and other services to computers with a wide variety of operating systems and dattypes. NetWorker products for different operating systems are interoperable. This providesthe flexibility to design a storage management system that works best with the current

computing environment.

The NetWorker software is distributed in these formats:

In a media kit of CD-ROMs that contains the software and electronic documentation forseveral related EMC products.

As a downloadable archive file from the EMC website.

The NetWorker product has five major components:

NetWorker client

NetWorker storage node

NetWorker server

NetWorker Management Console

NetWorker License Manager

NetWorker client

The NetWorker client software communicates with the NetWorker server and providesrecover and ad hoc (manual) backup functionality. The NetWorker client software is installeon all computers that are backed up to the NetWorker server.

NetWorker clients do not have to be running the same operating system as the NetWorkerserver. However, to back up clients running other operating systems, the NetWorker servermust 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,separate ClientPak enabler must be purchased and entered for that operating system.

NetWorker storage node

Data can be backed up directly to devices attached to a NetWorker server, or to a NetWorkestorage node. A storage node controls storage devices such as tape drivers, autochangers, ansilos.

Storage nodes depend on the NetWorker server for these functions:

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. Touse a NetWorker storage node on a Linux operating system with a NetWorker server runninanother operating system, the storage nodes enabler on the server must be of the sameedition as the base enabler for the NetWorker server.

7/28/2019 linuxig_7.3.2

11/82

About the NetWorker product1-

Introducti

NetWorker server

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

Enter the enabler licenses for the NetWorker server and all the functions the NetWorkerserver controls, such as autochanger modules, additional client connections, andClientPak 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.

NetWorker Management Console

All NetWorker servers and clients are managed from the NetWorker Management Console.

The Console replaces the NetWorker Administration program (nwadmin) which is no longeravailable.

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

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

browser can also be a NetWorker client, server, or storage node.

You must install the NetWorker Management Console software on one computer in your

datazone to manage and monitor the NetWorker server. Only one installation of the Consoleis required to manage multiple NetWorker servers and to take full advantage of the Consolesconsolidated reporting feature.

NetWorkerLicense Manager

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

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

7/28/2019 linuxig_7.3.2

12/82


Introduction

Supported devices

NetWorker software supports a variety of media types and devices, either stand-alone or inan autochanger or silo tape library. Devices can be attached to a NetWorker server or adesignated storage node. To obtain the latest list of supported devices, refer to the EMCHardware Compatibility Guides.

A nonrewinding device must be used for NetWorker backups. The pathnames for thesedevices 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 deviis used, enter it as a directory path (the same as for other device types) rather than as just afilename.

The term autochanger refers to a variety of backup devices:

Autoloader

Carousel

Datawheel

Jukebox

Library

Near-line storage

Enabler codes

Enabler codes (licenses), which activate the functionality of NetWorker software and otherEMC software, are sold separately. For information, see Chapter 6, Licensing and Enablingthe Software.

7/28/2019 linuxig_7.3.2

13/82

Updating from a Previous Release 2-1

2

This chapter explains how to update from a previous release of NetWorker software.


Introduction................................................................................................................................2-2 Updating from a previous release...........................................................................................2-2

Updating from aPrevious Release

7/28/2019 linuxig_7.3.2

14/82


Updating from a Previous Release

Introduction

When updating to NetWorker release 7.3.2 from NetWorker release 6.x or earlier, there is noway to revert to a previous release of the NetWorker software. The client file indexes areautomatically reorganized into new directory structures. It is a one-way conversion.

Updating from a previous release

Use the following roadmap to update the NetWorker software:

Task 1: Prepare to update the NetWorker software on the NetWorker server on page 2

Task 2: Update the NetWorker software on page 2-2

Task 1: Prepare to update the NetWorker software on the NetWorker server

To update from a previous release of NetWorker software:

1. Back up all client file indexes and generate a bootstrap for the server.

If a current bootstrap and backup of all client file indexes does not exist, performscheduled backups on all clients before updating to the next NetWorker release.

For example, to save bootstrap information, type the following command:

savegrp -O group

Note: Ensure that all clients are included in the groups being backed up.

2. Record the latest bootstrap save set ID and its associated volume label.

To obtain this information, type the following command:

mminfo -B

3. If the NetWorker software is not currently installed in the default location, record thelocation of the client file indexes.

Task 2: Update the NetWorker software

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

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.3. Uninstall the previous NetWorker release, but do not remove the client file indexes, the

resource files, or the media database.

On Linux for Intel x86 processors, see Uninstalling the NetWorker software onpage 3-19.

On Linux for the Itanium processor, see Uninstalling the NetWorker software onpage 4-14

7/28/2019 linuxig_7.3.2

15/82

7/28/2019 linuxig_7.3.2

16/82

7/28/2019 linuxig_7.3.2

17/82

Linux for Intel x86 Installation 3-1

3

This chapter explains how to install the NetWorker software on Linux for Intel x86 processors.

It contains the following sections:

Software installation roadmap.................................................................................................3-2 Installation requirements..........................................................................................................3-2 Installing the NetWorker software........................................................................................3-10

Verifying the installation ........................................................................................................3-16 Uninstalling the NetWorker software...................................................................................3-19

Linux for Intel x86Installation

7/28/2019 linuxig_7.3.2

18/82

7/28/2019 linuxig_7.3.2

19/82

Installation requirements3-

Linux for Intel x86 Installati

General requirements

The following are general NetWorker installation requirements:

All NetWorker servers, clients, and storage nodes must have TCP/IP installed,configured, and networked.

The designated server name that the NetWorker software requests must be the hostnameof the backup server.

TCP/IP requirements

The following are requirements for TCP/IP network communication when using NetWorkersoftware:

All NetWorker server, storage node, and client host computers must have TCP/IPinstalled 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, itmust have a reserved address.

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

Client software requirements

The following sections describe NetWorker installation requirements and recommendationsfor Linux client software:

System requirements on page 3-3

Client backup and recovery guidelines on page 3-4

System requirements

If the client software is being installed as part of the server installation, use the sameinstallation media and methods. The space requirements remain the same.

If only the NetWorker client software for Linux is being installed, purchase the NetWorkerClientPak for Linux with a separate enabler code. The NetWorker for Linux software islicensed as a separate platform.

Note: If client computers have a previous release of the NetWorker ClientPak for Linux installed, updatethose clients to the latest NetWorker release to fully exercise all the features in the software. When theinstallation identifies an existing NetWorker client package for Linux, it prompts for permission toupdate the client. The update process removes the existing NetWorker client and man pages and itinstalls the new version of the NetWorker client software.

Before installing the client software, review Server software requirements on page 3-4 forother relevant requirements and recommendations, which include supported software,hardware, and directory information.

Guidelines specific to the indexes and storage node do not apply to a client installation.

7/28/2019 linuxig_7.3.2

20/82


Linux for Intel x86 Installation

Client backup and recovery guidelines

A client can be configured to use the NetWorker software to access the NetWorker server inone of two ways:

Install the NetWorker client program directly on the local disk.

Configure the client with a directory on the network file system (NFS) on the remote

system where the NetWorker programs are located.To back up a NetWorker client, the nsrexecd daemon must be active on the client. To start thnsrexecd daemon, type the following command:

/etc/init.d/networker start

Storage node software requirements

At least one supported storage device must be attached and installed. The device can be astand-alone device, autochanger, or silo tape library. For a list of supported devices, refer tothe EMC Compatibility Guides.

Server software requirements

The following sections describe NetWorker installation requirements and recommendationfor a Linux server:


Directories and pathnames on page 3-5

Note: You must install the Console server software on one computer in your data zone to manage andmonitor the NetWorker server. Only one installation of the Console server is required to managemultiple NetWorker servers and to take full advantage of the Consoles consolidated reporting featur

System requirements

Table 3-1 lists the Linux distributions supported in release 7.3.2 of NetWorker server softwaon Linux for Intel x86, along with package requirements for each of the installations.

Note: Ensure that the kernel is supported and that all of the required packages and patches are installebefore beginning the NetWorker software installation. For information, refer to the Linux distributionsoftware documentation or other Linux documentation sources.

Table 3-1 Software requirements by supported Linux distribution

Linux distribution Kernel Additional modules, libraries, or upgrades

Red Hat Advanced Server Edition 2.1 2.4.9-e.3 pdksh-5.2.14-13.i386.rpm

Red Hat Enterprise Server 3 2.4.21-4.EL pdksh-5.2.14-21.i386.rpm

Red Hat Enterprise Server 4 2.6.9-5.ELand higher

pdksh-5.2.14-30.i386.rpm

SuSE Linux Enterprise Server 8 2.4.18-1 pdksh-5.2.14-19

SuSE Linux Enterprise Server 9 2.6.5-7.97 pdksh-5.2.14-780.1

7/28/2019 linuxig_7.3.2

21/82



Table 3-2 lists the minimum memory and storage requirements for the NetWorker server forLinux software. Additionally, because the client file index and media database that aNetWorker server generates can grow large over time, the NetWorker server needs enoughfree storage space to accommodate these indexes.

Install the appropriate storage devices, including SCSI adapter, cabling, and termination,prior to installing the NetWorker server. The NetWorker installation program assumes thatthe storage devices have been properly installed and configured, and that the operatingsystem recognizes the devices.

For a list of the currently supported devices, refer to the EMC Compatibility Guides.

Directories and pathnames

The following pathnames and directories are required for installation:

A directory on the server large enough for the NetWorker client and server indexes andmedia database (usually /nsr).

The system pathname of at least one storage device for use by the NetWorker server toback up and recover files.

A directory for the PDF documentation files and for Adobe Acrobat Reader if it is notalready installed.

Table 3-3 lists the default directories that the NetWorker installation program creates.

Table 3-2 Hardware requirements for NetWorker server

Requirement Value

Recommended RAM 128 MB

Disk storage for software 120 MB

Online indexes 5% of total backup data (allowing for up to three times the index size duringsoftware update conversion)

Table 3-3 Default locations and space requirements

Software and documentation files NetWorker server default location Space needed

NetWorker Management Console program /usr/bin/opt/lgtonmc

17 MB

NetWorker daemon and utility command files /usr/sbin 72 MB

Device drivers /usr/lib/nsr 6 MB

Online client file and server indexes; media database /nsr 4 MB

License Manager files /usr/sbin

/usr/nsr/lic/res

/nsr/lic/res

2 MB

22 KB

21 KB

NetWorker man pages /usr/share/man 2 MB

PDF files optional varies

7/28/2019 linuxig_7.3.2

22/82

7/28/2019 linuxig_7.3.2

23/82



System requirements for the Console client

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

Table 3-5 provides a list of system requirements for installing the Console client.

Estimating the size of the Console database

The Console server collects data from the NetWorker servers in the enterprise, and stores thedata in its local Console database. By default, the database is installed on the local file systemwith the most available space. Console integrates and processes this information to producereports that facilitate trend analysis, capacity planning, and problem detection. Forinformation about reports, refer to the NetWorker Administration Guide.

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

The number of NetWorker servers monitored for the reports.

The number of savegroups run by each of those servers.

The frequency with which savegroups are run. The length of time report data is saved (data retention policies).

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

Table 3-5 Console client system requirements

System feature Requirement

Operating system Red Hat Advanced Server Edition 2.1

Red Hat Enterprise Server 3

Red Hat Enterprise Server 4

SuSE Linux Enterprise Server 8

SuSE Linux Enterprise Server 9

Note: SuSE version 9.2 is supported.

Java Runtime Environment JRE version 1.4.2_11

Browsers One of the following:

Netscape Communicator 7.2 on the supported Linux platforms.

Mozilla 1.7 on the supported Linux platforms.

Available disk space Console client: 5 MB

JRE with Web Start: 50 MB

RAM A minimum of 512 MB to run reports.

Graphics card Must support display of both:

At least 16-bit color (at least 65,000 colors)

Screen resolution of at least 1024 x 768

7/28/2019 linuxig_7.3.2

24/82

7/28/2019 linuxig_7.3.2

25/82



After login to the host system:

a. Type the setenv command to change the locale.

b. Depending on the language, select one of the following:

To match the French NetWorker locale, type:

setenv LANG fr

setenv LC_ALL fr

To match the Japanese NetWorker locale, type:

setenv LANG ja

setenv LC_ALL ja

To match the Simplified Chinese NetWorker locale, type:

setenv LANG zh

setenv LC_ALL zh

Change 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 theoperating system of the Console server and client.

To load a font:

1. To select a language font, go to the Console menu bar and select View>Font.

The Change Font dialog box appears.

2. Select the appropriate font.

3. Select a font size, if a size other than the default is needed and click OK.

How to use 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 hostoperating system. In order to display non-English characters, the host operating systemmust have installed a font (or fonts) that supports those characters.

The Console client, rather than the Console server, must have the appropriate languagecharacter 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 alocalized version of NetWorker software automatically recognizes the font for theassociated localized language.

If the required font is loaded in the operating system, an appropriate language font canthen be selected.

Note: If the required font is not installed on the system, obtain it from the operating system vendor andinstall it on the system.

7/28/2019 linuxig_7.3.2

26/82

7/28/2019 linuxig_7.3.2

27/82

7/28/2019 linuxig_7.3.2

28/82

7/28/2019 linuxig_7.3.2

29/82

7/28/2019 linuxig_7.3.2

30/82

7/28/2019 linuxig_7.3.2

31/82

7/28/2019 linuxig_7.3.2

32/82

7/28/2019 linuxig_7.3.2

33/82

Verifying the installation3-1


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 followingmethods:

Point the browser to the same URL as in Task 1: Start Console for the first time onpage 3-16.

Double-click the NetWorker Management Console product name in theJava Web StartApplication Manager.

Task 2: Add a NetWorker server to the Console server

To add and select a NetWorker server:

1. Start the NetWorker Management Console software.

2. From the Console window, click Enterprise.

3. From the left pane, select the Enterprise icon.

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

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

The NetWorker server appears in the right pane and left pane.

6. From the left pane, select the NetWorker server.

7. From the right pane, select the NetWorker application.

8. From the Enterprise menu, select Launch Application.

The Administration window launches.

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

Task 3: Configure a device

If not already configured, you must configure a device before testing the NetWorker software.

You can configure one of these devices:

Stand-alone tape device on page 3-17

Stand-alone file or advanced file device on page 3-18

Autochanger or silo on page 3-18

Stand-alone tape device

To configure a stand-alone tape device:

1. In the servers NetWorker Administration interface, click Devices.2. From the left pane, select Storage Nodes.

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

4. Select Scan for devices.

The Scan for Devices window appears.

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

7/28/2019 linuxig_7.3.2

34/82



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.




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.


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.

Task 4: Test the NetWorker software installation

Test a NetWorker installation by performing an ad hoc (manual) backup of a file or folder.You can also use the NetWorker Client Configuration Wizard to configure a scheduled

backup. For information about the wizard, refer to the NetWorker Administration Guide.

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


2. Start the NetWorker nwbackup program.

7/28/2019 linuxig_7.3.2

35/82

7/28/2019 linuxig_7.3.2

36/82



3. Type the following commands to uninstall the software.

To uninstall all the packages, type:

rpm -e lgtolicm lgtoserv lgtonode lgtonmc lgtoclnt lgtoman

To uninstall packages individually, typerpm -efollowed by the specified packages

For NetWorker License Manager, follow with lgtolicm-7.3.2

For server software, follow with lgtoserv-7.3.2

For storage node software, follow with lgtonode-7.3.2

For Console server software, follow with lgtonmc-7.3.2

For client software, follow with lgtoclnt-7.3.2

For NetWorker man pages, follow with lgtoman-7.3.2

For example, if NetWorker release 6.1 is installed and an update to NetWorker release 7.3.2 required, type the following command to uninstall all NetWorker packages:

rpm -e lgtolicm-6.1 lgtoserv-6.1 lgtonode-6.1 lgtoclnt-6.1 lgtoman-6.1

7/28/2019 linuxig_7.3.2

37/82

Linux for Itanium Processor Installation 4-1

4

This chapter explains how to install the NetWorker software on Linux for the Itaniumprocessor.

It contains the following sections:

Software installation roadmap.................................................................................................4-2 Installation requirements..........................................................................................................4-2

Installing the NetWorker software..........................................................................................4-6 Verifying the installation ........................................................................................................4-10 Uninstalling the NetWorker software...................................................................................4-14

Linux for ItaniumProcessor Installation

7/28/2019 linuxig_7.3.2

38/82


Linux for Itanium Processor Installation

Software installation roadmap

Use the following roadmap when installing the NetWorker software:

1. Review the requirements section and note the default directory location and spacerequirements for the software installation file. For information, see Installation

requirements on page 4-2.2. If there is an earlier release of NetWorker software installed, update the software. For

information, see Updating from a Previous Release on page 2-1.

3. Install the required NetWorker software. For information, see Installing the NetWorkesoftware on page 4-6.

Note: You must install the Console server software on one computer in your data zone to managethe NetWorker server. Only one installation of the Console server is required to manage multipleNetWorker servers.

4. Test the NetWorker software, see Verifying the installation on page 4-10.

5. Enable and register all NetWorker products. For information, see Chapter 6, Licensingand Enabling the Software.

Installation requirements

The following sections provide information on the system requirements for the differentcomponents being installed:

General requirements on page 4-2

TCP/IP requirements on page 4-3

Client software requirements on page 4-3

Storage node software requirements on page 4-4

Server software requirements on page 4-4

Note: NetWorker software does not support locales (defined by the operating system) or code sets tharemap characters that have special meaning for file systems. Depending on the file system, these specicharacters might 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.

General requirements

The following are general NetWorker installation requirements:

All NetWorker servers, clients, and storage nodes must have TCP/IP installed,configured, and networked.

The designated server name that the NetWorker software requests must be the hostnamof the backup server.

The TCP/IP hostname must be identical to the computer name. Do not include anunderscore character (_) in the computer name.

7/28/2019 linuxig_7.3.2

39/82

7/28/2019 linuxig_7.3.2

40/82



Storage node software requirements

At least one supported storage device must be attached and installed. The device can be astand-alone device, autochanger, or silo tape library. For a list of supported devices, refer tothe EMC Compatibility Guides.

Server software requirements

The following sections describe NetWorker installation requirements and recommendationfor a Linux server:


Directories and pathnames on page 4-5

System requirements

Table 4-8 lists the Linux distributions supported in release 7.3.2 of NetWorker server softwaon Linux for Itanium Processor, along with package requirements for each of the installation

Note: Ensure that the kernel is supported and that all of the required packages and patches are installebefore beginning the NetWorker software installation. For information, refer to the Linux distributionsoftware documentation or other Linux documentation sources

Table 4-9 lists the minimum memory and storage requirements for the NetWorker Server foLinux software. Additionally, because the client file index and media database that aNetWorker server generates can grow large over time, the NetWorker server needs enoughfree storage space to accommodate these indexes.

Table 4-8 Software requirements by supported Linux distribution

Linux distribution Kernel Additional modules, libraries, or upgrades

SuSE Linux Enterpr ise Server 8 2.4.18-1 pdksh-5.2.14-19

SuSE Linux Enterprise Server 9 2.6.5-7.97 pdksh-5.2.14-780.1

RedHat Advanced Server 2.1 2.4.9-e.3 pdksh-5.2.14-13.i386.rpm

Red Hat Enterprise Server 3 2.4.21-4.EL pdksh-5.2.14-21.i386.rpm

Red Hat Enterprise Server 4 2.6.9-5.EL andhigher

pdksh-5.2.14-30.i386.rpm

Table 4-9 Hardware requirements for NetWorker server

Requirement Value

Recommended RAM 64 MB

Disk storage for software 100 MB

Online indexes 5% of total backup data (allowing for up to three times the index size duringsoftware update conversion)

7/28/2019 linuxig_7.3.2

41/82


Linux for Itanium Processor Installati

Installation guidelines

On the NetWorker server, install all of the NetWorker software in the following order:

1. Client

2. Storage Node

3. Server

It is recommended that the NetWorker software packages all be installed on the server duringthe same installation session.

Install the appropriate storage devices, including SCSI adapter, cabling, and termination,prior to installing the NetWorker server. The NetWorker installation program assumes thatthe storage devices have been properly installed and configured, and that the operatingsystem recognizes the devices.

Note: For a list of the currently supported devices, refer to the EMC Compatibility Guides.

Directories and pathnames

The following pathnames and directories are required for installation:

A directory on the server large enough for the NetWorker client and server indexes andmedia database (usually /nsr).

The system pathname of at least one storage device for use by the NetWorker server toback up and recover files.

A directory for the PDF documentation files and for Adobe Acrobat Reader if it is notalready installed.

If the default locations and space requirements are accepted during installation, theinstallation script creates the directories listed in Table 4-10.

Table 4-10 Default locations and space requirements

Software and Documentation Files NetWorker server default location Space needed

NetWorker Administrator program and NetWorkerClient program files

/usr/bin 29 MB

NetWorker daemon and utility command files /usr/sbin 66 MB

Device drivers /usr/lib/nsr 10 MB

Online client file and server indexes; media database /nsr 4 MB

NetWorker License Manager files /usr/sbin/usr/nsr/lic/res/nsr/lic/res

2 MB

22 KB

21 KB

NetWorker man pages /usr/share/man 2 MB

PDF files optional varies

7/28/2019 linuxig_7.3.2

42/82



Installing the NetWorker software

The following sections explain how to install the NetWorker software:

Task 1: Access the NetWorker software on page 4-6

Task 2: Install the NetWorker software on page 4-7

Task 3: Change the NetWorker servers with access to a client on page 4-9

Task 4: Start the NetWorker daemons on page 4-10

Task 1: Access the NetWorker software

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

The evaluation release of NetWorker software contains tarred and compressed versions of thNetWorker software distribution files. Ensure that there is adequate disk space for both thecompressed download file (about 60 MB) and the fully uncompressed files (about 60 MB).

From a local CD-ROM To access the NetWorker software from a local system:

1. Log in as root on the computer where the NetWorker software is being installed.

2. Mount the CD-ROM.

3. Locate the /linux_ia64 directory on the installation CD-ROM.

4. On both the NetWorker server and client, set the PATH environment variable for user roto contain the directory where the NetWorker executables reside. For information on thdirectory, see Table 4-10, Default locations and space requirements, on page 4-5.

From the EMC website

To access the installation software from the EMC website:

1. Log in as root on the computer where the NetWorker software is being installed.

2. Create a temporary directory to download the evaluation software.

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

4. Download the evaluation software to the temporary directory and change to thatdirectory.

5. Uncompress the downloaded software, enter the following command:

gunzip nw732_linux_ia64.tar.gz

6. Extract the uncompressed tarred file, enter the following command:

tar -xvpBf nw732_linux_ia64.tar

The NetWorker distribution software directories and files are listed on the screen as theextraction proceeds.

7. On both the NetWorker server and client, set the PATH environment variable for the usroot, to contain the directory where the NetWorker executables will be installed, that is/usr/sbin. For information on this directory, see Table 4-10 on page 4-5.

7/28/2019 linuxig_7.3.2

43/82

Installing the NetWorker software4-


Task 2: Install the NetWorker software

By default, the NetWorker software is installed in the /usr directory. The software can,however, be installed in a different directory. If there is insufficient disk space on the /usrpartition, choose another location to install the software.

Follow the instructions in one of the following sections to install the software:

Installing to the default location on page 4-7

Installing to a nondefault location on page 4-8

Installing to the default location

To install the client, storage node, and server software to the default location, see thefollowing sections:

Client installation on page 4-7

Storage node installation on page 4-7

Server installation on page 4-8

Client installation

Note: The NetWorker software uses the rpm utility for installation. For information about using rpm,refer to the Linux rpm man page.

To install the NetWorker software on computers designated as NetWorker clients:

1. Log in to the NetWorker Linux client.

2. Change to the directory containing the NetWorker software.

3. Enter the following command:

rpm -ivh lgtoclnt-7.3-2.ia64.rpm

4. (Optional) To install the man pages, enter the following command:

rpm -ivh lgtoman-7.3-2.ia64.rpm

Note: You might need to install the UTF-8 converters available with your operating system.

Storage node installation

Install the NetWorker software on the following systems:

Install the client and storage node software on the computers designated as storage nodesif you purchased an enabler for storage node support.

The storage node package must be installed on the NetWorker server, regardless ofwhether separate systems are designated storage nodes. For instructions, see Serverinstallation on page 4-8.


7/28/2019 linuxig_7.3.2

44/82



To install the NetWorker client and storage node software:


2. Enter the following command to install the client and storage node packages:

rpm -ivh lgtoclnt-7.3-2.ia64.rpm lgtonode-7.3-2.ia64.rpm

3. (Optional) To install the man page package, enter the following command:

rpm -ivh lgtoman-7.3-2.ia64.rpm


Server installation

On the computer designated as the NetWorker server, install all the NetWorker softwarepackages in the following order: client, storage node, server. The NetWorker License Managcan be installed any time after the client package is installed.


To install the software:


2. Enter the following command to install the client, storage node, server, and NetWorkerLicense Manager software:

rpm -ivh lgtoclnt-7.3-2.ia64.rpm lgtonode-7.3-2.ia64.rpmlgtoserv-7.3-2.ia64.rpm lgtolicm-7.3-2.ia64.rpm

Note: Installing the NetWorker License Manager software is optional. It can be installedany time afterthe client software.


rpm -ivhlgtoman-7.3-2.ia64.rpm

The installation process adds the following files:

/etc/init.d/networker

/etc/init.d/rc3.d/S95networker

/etc/init.d/rc5.d/S95networker

/etc/init.d/rc0.d/K05networker


Installing to a nondefault location

By default, the NetWorker software is installed in the /usr directory. If there is insufficientdisk space on the /usr partition, relocate the NetWorker packages to a specified directory oanother partition. For information about directories and space requirements, see Table 4-10on page 4-5.

7/28/2019 linuxig_7.3.2

45/82

Installing the NetWorker software4-


To install the NetWorker software to a nondefault location:


2. Enter the following command to install the NetWorker client, storage node, server, andNetWorker License Manager software:

rpm -ivh --relocate old path=new pathlgtoclnt-7.3-2.ia64.rpm

lgtonode-7.3-2.ia64.rpm lgtoserv-7.3-2.ia64.rpm lgtolicm-7.3-2.ia64.rpm

For example, if you relocated the /usr/bin directory to a new directory called /backup,youwould enter the following command to relocate the /sbin subdirectory:

rpm -ivh --relocate /usr/bin=/backup lgtoclnt-7.3-2.ia64.rpmlgtonode-7.3-2.ia64.rpm lgtoserv-7.3-2.ia64.rpm lgtolicm-7.3-2.ia64.rpm

Note: Installing the NetWorker License Manager software is optional. It can be installed any timeafterthe client software is installed.


rpm -ivh --relocate old path=new path lgtoman-7.3-2.ia64.rpm

4. Modify the root PATH variable to designate the /usr/bin and /usr/lib/nsr subdirectoriesof the directory just created.

For example, if you relocated the /usr/bin directory to a new directory called /backup,you would enter the following command to relocate the /usr/sbin subdirectory:

/backup:/usr/sbin


Task 3: Change the NetWorker servers with access to a client

To limit the servers authorized to access a client, a list of trusted NetWorker servers can bespecified for a client in the /nsr/res/servers file. After installing the client, storage node, andserver software, use the following procedure to change the NetWorker servers that areauthorized to access a client.

To change the NetWorker servers that can access a client:

1. Edit or create the /nsr/res/servers file and add the NetWorker servers, one per line, thatrequire access to the client. The first entry in this file becomes the default NetWorkerserver.

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 recover to the client.

2. If necessary, delete the -s option from the nsrexecd command that is invoked by theboot-time startup file. Running nsrexecd with the -s option supersedes the following file:

/nsr/res/servers

7/28/2019 linuxig_7.3.2

46/82

7/28/2019 linuxig_7.3.2

47/82

7/28/2019 linuxig_7.3.2

48/82



Task 3: Configure a device

If not already configured, you must configure a device before testing the NetWorker softwar

You can configure one of these devices:

Stand-alone tape device on page 4-12

Stand-alone file or advanced file device on page 4-12

Autochanger or silo on page 4-13

Stand-alone tape device

To configure a stand-alone tape device:




4. Select Scan for devices.

The Scan for Devices window appears.

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

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

The newly detected device appears in the right pane.

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

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




Stand-alone file or advanced file device

To configure a stand-alone file or advanced files device:


2. From the left pane, select Devices.

3. From the File menu, select New.

The Create Devices window appears.

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

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

6. Click OK. The new device appears in the right pane.7. From the right pane, select the new device.




7/28/2019 linuxig_7.3.2

49/82

Verifying the installation4-1


Autochanger or silo

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




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.

Task 4: Test the NetWorker software installation

Test a NetWorker installation by performing an ad hoc (manual) backup of a file or folder.You can also use the NetWorker Client Configuration Wizard to configure a scheduled

backup. For information about the wizard, refer to the NetWorker Administration Guide.

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


2. Start the NetWorker nwbackup program.

The NetWorker nwbackup program provides a graphical interface through which ad hoc(manual) backups are performed. The NetWorker Administration Guide provides generalinformation about the NetWorker nwbackup program.

To start the NetWorker nwbackup program:

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

The NetWorker Backup window appears.

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

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

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

Select the directory or file and click Mark. To clear an item, click Unmark.

Click the directory or file. When you mark a directory or file for backup, a checkmark appears next to that item.

e. Click Start to begin the ad hoc backup.

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

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

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

7/28/2019 linuxig_7.3.2

50/82



Uninstalling the NetWorker software

Use this command to uninstall individual NetWorker packages or all of the NetWorkerpackages at the same time:

rpm -epackage_nameFor information about using rpm, refer to the rpm man page.

Note: The following sequence must be used to uninstall all of the NetWorker software packages:lgtolicm, lgtoserv, lgtonode, lgtoclnt. The man pages (lgtoman) and document files have no dependenciesand can be uninstalled any time.

To uninstall the NetWorker software packages:

1. Log in as root on the computer where the software is being uninstalled.

2. Run a query to see which packages are installed:

rpm -qa | grep lgto

The packages are displayed in the following format, 7.3.2 is the release number and -1 i

appended by the RPM utility:

lgtonode-7.3.2-1

lgtoclnt-7.3.2-1

lgtoserv-7.3.2-1

lgtoman-7.3.2-1

lgtolicm-7.3.2-1

3. Enter this command to uninstall the software:

rpm -epackage_name To uninstall all the packages, enter:

rpm -e lgtolicm lgtoserv lgtonode lgtoclnt lgtoman

To uninstall packages individually, enter rpm -e followed by the specified packages:

For NetWorker License Manager, follow with lgtolicm-7.3.2

For server software, follow with lgtoserv-7.3.2

For storage node software, follow with lgtonode-7.3.2

For client software, follow with lgtoclnt-7.3.2

For NetWorker man pages, follow with lgtoman-7.3.2

7/28/2019 linuxig_7.3.2

51/82

EMC AutoStart Installation 5-1

5

This chapter explains how to install NetWorker software in an EMC AutoStart environment(formerly EMC Automated Availability Manager).


Software installation roadmap.................................................................................................5-2 Installation requirements..........................................................................................................5-2

Installing a NetWorker virtual server.....................................................................................5-4 Installing a virtual Console server ..........................................................................................5-9 Installing only the NetWorker client software in a cluster ................................................5-10 Configuring an external client to a virtual server ...............................................................5-12 Defining ownership of a raw partition for virtual clients .................................................5-13 Tracking scheduled saves.......................................................................................................5-13 Uninstalling the NetWorker software...................................................................................5-14

Note: EMC AutoStart is supported on the Linux for the Intel x86 platform. It is not supported on otherNetWorker Linux platforms.

EMC AutoStartInstallation

7/28/2019 linuxig_7.3.2

52/82


EMC AutoStart Installation

Software installation roadmap

Use the following roadmap when installing the NetWorker software. Read the roadmap anthe referenced sections before installing the software.

1. Review the requirements section and note the default directory location. For more

information, see Installation requirements on page 5-2.2. Install the required NetWorker software. For information, see:

Installing a NetWorker virtual server on page 5-4

Installing only the NetWorker client software in a cluster on page 5-10

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

Installation requirements

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

Software requirements on page 5-2

Hardware requirements on page 5-2

Configuration options on page 5-3

System information requirements on page 5-3

For the most up-to-date information regarding software and hardware requirements, refer the EMC Compatibility Guides.

Software requirements

To install a NetWorker cluster server, ensure that the following software is installed on eachnode in the cluster:

Red Hat Enterprise Linux AS2.1 or later

EMC AutoStart release 5.1 or later

NetWorker release 7.3 and later

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 me

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 withthe cluster.

7/28/2019 linuxig_7.3.2

53/82

7/28/2019 linuxig_7.3.2

54/82

7/28/2019 linuxig_7.3.2

55/82

Installing a NetWorker virtual server5-

EMC AutoStart Installati

3. Set and export the FT_DIR, FT_DOMAIN, and the FT_CONSOLE_DIR environmentvariables. For example, from the Bourne shell, type the following commands:

FT_DIR=/opt/LGTOaamxx

FT_CONSOLE_DIR=$FT_DIR/console

FT_DOMAIN=domain_name

export FT_DIR FT_DOMAIN FT_CONSOLE_DIR

where:

xx = 50 for EMC AutoStart version 5.x

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, networker.cluster located in the/usr/sbindirectory.

b. Type the following information:

Location of the local NetWorker database directory provided during theinstallation procedure:

/nsr

Published virtual hostname:

clus_vir1

Shared nsr mount directory:

/nsr_shared_mnt_pt

Note: Any changes to the configuration can be undone by running the networker.cluster -r option.

5. From one node in the cluster:

a. Log in as administrator.

b. Customize the /opt/lgtonmc/bin/nw_ux.lc.aam5.imp file

The nw_ux.lc.aam5.imp file is used to create the NetWorker resource group and itsdependant objects.

Note: In the nw_ux.lc.aam5.imp file, there are multiple instances of the NW Customizecomment, ensure that all entries are replaced with the appropriate cluster configuration values.

Follow the instructions listed in the comments at the beginning of thenw_ux.lc.aam5.imp file to customize the following NetWorker default values based onthe cluster configuration:

Virtual hosts IP address:

192.168.1.10

Physical hostnames:

clus_phys1, clus_phys2

Shared disk file system:

/nsr_shared_mnt_pt

Device name:

/dev/dsk/c1t3d0s0

For a list of the sample values provided, see Table 5-12 on page 5-3.

7/28/2019 linuxig_7.3.2

56/82

7/28/2019 linuxig_7.3.2

57/82

Installing a NetWorker virtual server5-


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 thevirtual NetWorker server. For example:

clus_vir1

clus_phys1

clus_phys2

Task 5: Configure the NetWorker server

To configure the NetWorker server:

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

nsradmin -s clus_vir1

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

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

root@hostname

b. Click OK.

Task 6: Configure clients under the NetWorker server

When the /usr/sbin/networker.cluster script runs, it creates a symbolic link, /nsr, thatpoints to a local disk. It also creates a second link named nsr.NetWorkerBackup.local thatpoints to the local NetWorker directory. For example, if the local NetWorker directory wascreated in /var/nsr, each client member will have the following links:

/nsr->/nsr.NetWorkerBackup.local /nsr.NetWorkerBackup.local->/var/nsr

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 optiondisabled 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 NetWorkerserver.

For each virtual client in the cluster:


b. For the Name attribute, type the name of the virtual client.

7/28/2019 linuxig_7.3.2

58/82



c. In the Remote Access attribute, add entries for each physical client within the clusteFor 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 Trackingscheduled saves on page 5-13.

Task 7: Register NetWorker licenses for virtual server failover

To register a NetWorker server in a cluster environment:

1. Ensure that the NetWorker virtual server is defined as a part of the cluster.

2. Ensure that the NetWorker service is running.

3. For each physical node in the cluster:

a. Relocate, sequentially, the NetWorker server to this node.

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

4. Log on to the system running the NetWorker virtual server and create a file named/nsr/res/hostids that contains the host IDs of all the cluster nodes.

Use the following syntax:

hostid1:hostid2:hostid3:...

For example:12345678:87654321

5. Restart the server by taking the NetWorker virtual server offline and then putting it baconline.

6. From the NetWorker Administration window, note the host ID number for theappropriate cluster license.

7. Register the NetWorker software. Customer Service will send you authorization codesthat use the composite host ID that was created in step 4.

7/28/2019 linuxig_7.3.2

59/82

Installing a virtual Console server5-


Installing a virtual Console server

To install and configure the Console software as a highly available service in a cluster, readand follow the procedures for these tasks:

Task 1: Install the NetWorker Management software in a cluster on page 5-9

Task 2: Define the Console server as highly available on page 5-9

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. Ensure that this environment variable is set to the home directory of the root user:

$HOME

3. Install the Console server (lgtonmc) software on each node in the cluster.

For instructions, see Installing the NetWorker software on page 3-10.

Task 2: Define the Console server as highly available

To define and configure the Console server as a highly available application on each node inthe cluster:

1. Log in as root.

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 Domain Name System (DNS) or NetworkInformation Service (NIS).

3. Set and export the FT_DIR, FT_DOMAIN, and the FT_CONSOLE_DIR environment

variables.For example, from the Bourne shell type the following commands:





where:

xx= 5.0 for EMC AutoStart version 5.0

xx= 5.1 for EMC AutoStart version 5.1


4. From each node in the cluster that will run the NetWorker server process:

a. Run the cluster configuration script:

/opt/lgtonmc/bin/gst_ha.cluster.

b. Type the following information:

Published logical hostname:

clus_vir1

Shared nmc mount directory:

/nmc_shared_mnt_pt

7/28/2019 linuxig_7.3.2

60/82



Note: Any changes to the configuration can be undone by running the gst_ha.cluster -r option.

5. From one node in the cluster, customize the following file:

/opt/lgtonmc/bin/gst_ha_ux.aam5.imp

The gst_ha_ux.aam5.imp file is used to create the NetWorker 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 Customizecomment, ensure that all entries are replaced with the appropriate cluster configuration values.

Follow the instructions listed in the comments at the beginning of thegst_ha_ux.aam5.imfile to customize the following Console default values based on the cluster configuratio

Virtual hosts IP address:

192.168.1.10

Physical hostnames:

clus_phys1, clus_phys2

Shared disk file system:

/nmc_shared_mnt_pt

Device name:

/dev/dsk/c1t3d0s0

For a listing of the sample values provided, see Table 5-12 on page 5-3.

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, by using the EMCAutoStart Console.

Installing only the NetWorker client software in a cluster

To install NetWorker cluster client, follow the procedures for these tasks:

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

Task 2: Configure NetWorker client software as highly available on page 5-11

Task 3: Define the list of trusted NetWorker servers on page 5-11

Task 4: Configure clients under the NetWorker server on page 5-12

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

Task 1: Install the NetWorker cluster client software

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

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

2. Install the NetWorker software on every node in the cluster to be backed up.

7/28/2019 linuxig_7.3.2

61/82

Installing only the NetWorker client software in a cluster5-1


Task 2: Configure NetWorker client software as highly available

To define and configure a NetWorker client as a highly available application:

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. Set and export the FT_DIR, FT_DOMAIN, and the FT_CONSOLE_DIR environment

variables.

For example, from the Bourne shell type the following commands:





where:

xx= 50 for EMC AutoStart version 5.x


4. For each node in the cluster:

a. Run the cluster configuration script:

/usr/sbin/networker.cluster

b. In response to the prompt to configure the NetWorker server, type No.

Note: Any changes to the configuration can be undone by running the networker.cluster -r option.

Task 3: 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 /nsr/res/servers file.

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 recover to the client.

To define the list of trusted NetWorker servers, perform the following steps on each node inthe cluster:

1. Shut down the NetWorker processes and verify that all NetWorker services 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 virtualNetWorker 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 following in the file:

-s servername

7/28/2019 linuxig_7.3.2

62/82



Task 4: Configure clients under the NetWorker server

Note: The NetWorker server might reside outside of the cluster.

To configure each client under the NetWorker server:

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

For each physical client in the cluster:


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

For information, refer to the NetWorker Administration Guide.

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

For each virtual client in the cluster:


a. For the Name attribute, type the name of the virtual client.

b. For the Remote Access attribute, add entries for each physical client within the clusteFor example:

root@clus_phys1

c. For the Group attribute, select a group.

3. Schedule backups by using the NetWorker Administrator program. For detailedinstructions, refer to the NetWorker Administration Guide.

Configuring an external client to a virtual server

Before a NetWorker server can back up a client, the server must be granted access. Granting

access is controlled by editing the /nsr/res/servers file.

Note: If the /nsr/res/servers file is empty or does not exist, any NetWorker server isauthorized to:- Access and back up the client.- Perform a directed recover to the client.

To configure and back up an external NetWorker client to a NetWorker server, perform thefollowing on each NetWorker client that is outside of the cluster:

1. Shut down the NetWorker processes and verify that all NetWorker services have stoppe

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 virtuNetWorker server. For example:

clus_vir1

clus_phys1

clus_phys2

7/28/2019 linuxig_7.3.2

63/82

Defining ownership of a raw partition for virtual clients5-1


Defining ownership of a raw partition for virtual clients

Use the IPOverride option to back up the raw partitions of a NetWorker virtual client, asdescribed in the following steps:

1. Open the EMC AutoStart Management Console and select Resource Group.

The Resource Group Editor window appears.

2. Select the Edit View tab and then select Edit>Attributes.

The Def

Documents

linuxig_7.3.2