NetWorker 7.3.2 For Linux Installation Guide - Linuxig - 7.3.2

EMC® NetWorker™
Release 7.3.2
Linux Version
INSTALLATION GUIDE
P/N 300-003-651
REV A01
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
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 EMC NetWorker for Linux, Release 7.3.2, Installation Guide

Contents
Preface ............................................................................................................................................................... vii
Chapter 1 Introduction
About the NetWorker product ........................................................................................ 1-2
NetWorker client......................................................................................................... 1-2
NetWorker storage node............................................................................................ 1-2
NetWorker server ....................................................................................................... 1-3
NetWorker Management Console............................................................................ 1-3
NetWorker License Manager .................................................................................... 1-3
Supported devices............................................................................................................. 1-4
Enabler codes ..................................................................................................................... 1-4
Chapter 2 Updating from a Previous Release

Introduction ....................................................................................................................... 2-2
Updating from a previous release .................................................................................. 2-2
Task 1: Prepare to update the NetWorker software on the NetWorker server . 2-2
Task 2: Update the NetWorker software ................................................................. 2-2
Chapter 3 Linux for Intel x86 Installation

Software installation roadmap........................................................................................ 3-2
Installation requirements ................................................................................................. 3-2
General requirements ................................................................................................. 3-3
TCP/IP requirements ................................................................................................. 3-3
Client software requirements.................................................................................... 3-3
Storage node software requirements ....................................................................... 3-4
Server software requirements ................................................................................... 3-4
Console server software requirements .................................................................... 3-6
Installing the NetWorker software ................................................................................. 3-9
Task 1: Access the NetWorker software ................................................................ 3-10
Task 2: Install the NetWorker software ................................................................. 3-10
Task 3: Change the NetWorker servers with access to a client .......................... 3-15
Task 4: Start the NetWorker daemons ................................................................... 3-15
Verifying the installation ................................................................................................ 3-16
Task 1: Start Console for the first time................................................................... 3-16
Task 2: Add a NetWorker server to the Console server...................................... 3-17
Task 3: Configure a device....................................................................................... 3-17
Task 4: Test the NetWorker software installation ................................................ 3-18
Uninstalling the NetWorker software .......................................................................... 3-19
Contents iii
Contents
Chapter 4 Linux for Itanium Processor Installation

Software installation roadmap ........................................................................................ 4-2
General requirements ................................................................................................. 4-2
TCP/IP requirements ................................................................................................. 4-3
Client software requirements.................................................................................... 4-3
Storage node software requirements ....................................................................... 4-4
Server software requirements ................................................................................... 4-4
Installing the NetWorker software ................................................................................. 4-6
Task 1: Access the NetWorker software .................................................................. 4-6
Task 2: Install the NetWorker software ................................................................... 4-7
Task 3: Change the NetWorker servers with access to a client ............................ 4-9
Task 4: Start the NetWorker daemons ................................................................... 4-10
Verifying the installation ................................................................................................ 4-10
Task 1: Start Console for the first time................................................................... 4-10
Task 2: Add a NetWorker server to the Console server...................................... 4-11
Task 3: Configure a device....................................................................................... 4-12
Task 4: Test the NetWorker software installation ................................................ 4-13
Chapter 5 EMC AutoStart Installation

Software installation roadmap ........................................................................................ 5-2
Software requirements ............................................................................................... 5-2
Hardware requirements............................................................................................. 5-2
Configuration options ................................................................................................ 5-3
System information requirements ............................................................................ 5-3
Installing a NetWorker virtual server............................................................................. 5-4
Task 1: Ensure that the EMC AutoStart software is installed............................... 5-4
Task 2: Install the NetWorker software in a cluster............................................... 5-4
Task 3: Define the NetWorker server as highly available..................................... 5-4
Task 4: Grant access to the NetWorker virtual server ........................................... 5-6
Task 5: Configure the NetWorker server................................................................. 5-7
Task 6: Configure clients under the NetWorker server......................................... 5-7
Task 7: Register NetWorker licenses for virtual server failover .......................... 5-8
Installing a virtual Console server.................................................................................. 5-9
Task 1: Install the NetWorker Management software in a cluster....................... 5-9
Task 2: Define the Console server as highly available........................................... 5-9
Installing only the NetWorker client software in a cluster........................................ 5-10
Task 1: Install the NetWorker cluster client software.......................................... 5-10
Task 2: Configure NetWorker client software as highly available .................... 5-11
Task 3: Define the list of trusted NetWorker servers........................................... 5-11
Task 4: Configure clients under the NetWorker server....................................... 5-12
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
iv EMC NetWorker for Linux, Release 7.3.2, Installation Guide

Contents
Chapter 6 Licensing and Enabling the Software

How NetWorker software is licensed............................................................................. 6-2
The evaluation process ..................................................................................................... 6-2
Evaluating a new installation.................................................................................... 6-2
Evaluating features on an existing installation....................................................... 6-2
The licensing process ........................................................................................................ 6-3
Task 1: Enter the license enabler code...................................................................... 6-4
Task 2: Obtain an authorization code ...................................................................... 6-4
Task 3: Enter the authorization code........................................................................ 6-5
Multiplatform licensing.................................................................................................... 6-6
Update enablers .......................................................................................................... 6-7
Additional licenses ..................................................................................................... 6-7
Managing NetWorker licenses ........................................................................................ 6-8
Appendix A Sample stinit.def File

Usage .................................................................................................................................. A-2
Examples of the stinit file ................................................................................................ A-2
Appendix B stinit(8) Man Page

Synopsis ............................................................................................................................. B-2
Description ........................................................................................................................ B-2
Options .............................................................................................................................. B-2
The devices being initiated ............................................................................................. B-2
Return Value ..................................................................................................................... B-3
Restrictions ........................................................................................................................ B-4
Contents v
Contents
vi EMC NetWorker for Linux, Release 7.3.2, Installation Guide

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:
◆ 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 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, “Linux for Intel x86 Installation,” describes how to access and install the
NetWorker software from the distribution media in a Linux for Intel x86 environment.
◆ Chapter 4, “Linux for Itanium Processor Installation,” describes how to access and install
the NetWorker software from the distribution media in a Linux for Itanium processor
environment.
◆ Chapter 5, “EMC AutoStart Installation,” describes how to install the NetWorker
software in a EMC Autostart cluster environment.
◆ Chapter 6, “Licensing and Enabling the Software,” describes how to license and enable
the NetWorker software.
◆ Appendix A, “Sample stinit.def File,” provides information about the stinit.def file.
◆ Appendix B, “stinit(8) Man Page,” provides informaiton on the stinit(8) man page.
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
italic • Book titles
• New terms in text
• Emphasis in text
Courier • Prompts
• System output
• Filenames
• Pathnames
• URLs
• Syntax when shown in command line or other examples
Courier, bold • User entry
• Options in command-line syntax
Courier italic • Arguments in examples of command-line syntax
• Variables in examples of screen or file output
• Variables in pathnames
<> Angle brackets for parameter values (variables) supplied by user.
[] Square brackets for optional values.
| Vertical bar symbol for alternate selections. The bar means or.
... Ellipsis for nonessential information omitted from the example.
viii EMC NetWorker for Linux, Release 7.3.2, Installation Guide

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
x EMC NetWorker for Linux, Release 7.3.2, Installation Guide

1
Introduction
This chapter provides background information on EMC NetWorker software and supported
devices.
It includes the following sections:
◆ About the NetWorker product.................................................................................................1-2
◆ Supported devices .....................................................................................................................1-4
◆ Enabler codes .............................................................................................................................1-4
Introduction 1-1
Introduction
About the NetWorker product

The EMC® NetWorker™ product is a suite of storage management software that provides
backup, recovery, and other services to computers with a wide variety of operating systems
and data types. NetWorker products for different operating systems are interoperable. This
provides the flexibility to design a storage management system that works best with the
current computing environment.
The NetWorker software is distributed in these formats:
◆ In a media kit of CD-ROMs that contains the software and electronic documentation for
several related EMC products.
◆ As a downloadable archive file from the EMC website.
The NetWorker product has five major components:
◆ NetWorker client
◆ NetWorker storage node
◆ NetWorker server
◆ NetWorker Management Console
◆ NetWorker License Manager
NetWorker 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.
NetWorker storage node

Data can be backed up directly to devices attached to a NetWorker server, or to a NetWorker
storage node. A storage node controls storage devices such as tape drivers, autochangers, and
silos.
Storage nodes depend on the NetWorker server for these functions:
◆ Control over which clients use the storage node’s devices for backups
◆ License management
◆ Management of the client file indexes that track each client’s data
◆ Management of the media database that tracks the data contained on each volume
NetWorker storage nodes and the NetWorker server can use different operating systems. To
use a NetWorker storage node on a Linux operating system with a NetWorker server running
another operating system, the storage node’s enabler on the server must be of the same
edition as the base enabler for the NetWorker server.
1-2 EMC NetWorker for Linux, Release 7.3.2, Installation Guide

Introduction
NetWorker server
The NetWorker server software provides control and scheduling for NetWorker operations. It
enables you to:
◆ Enter the enabler licenses for the NetWorker server and all the functions the NetWorker
server controls, such as autochanger modules, additional client connections, and
ClientPak licenses.
◆ Define the clients, devices, and media that the NetWorker server controls.
◆ Define the schedules for backups and other operations.
◆ Monitor the results of backups and other operations.
◆ Manage the client file indexes that track each client’s data.
◆ Manage the media database that tracks the data contained on each volume.
NetWorker Management Console

All NetWorker servers and clients are managed from the NetWorker Management Console.
The Console replaces the NetWorker Administration program (nwadmin) which is no longer
available.
The Console provides reporting, managing, and monitoring capabilities for all NetWorker
servers and clients. The Console must in be installed on an AIX, HP-UX, Linux, Solaris, or
Microsoft Windows host in order to administer NetWorker servers.
The Console is accessed through a graphical interface that can be run from from only an AIX,
HP-UX, Linux, Solaris, or Windows host that has a web-enabled browser with the specified
version of Java Runtime environment configured. Multiple users can access the Console
server concurrently from different browser sessions. A computer that hosts the web-enabled
browser can also be a NetWorker client, server, or storage node.
You must install the NetWorker Management Console software on one computer in your
datazone to manage and monitor the NetWorker server. Only one installation of the Console
is required to manage multiple NetWorker servers and to take full advantage of the Console’s
consolidated reporting feature.
NetWorker License Manager

The NetWorker License Manager provides a central location for managing the licenses of all
the NetWorker clients and servers. Instead of managing licenses separately, all NetWorker
licenses can be maintained from a single computer. Installation of the NetWorker License
Manager is an option when installing the NetWorker software.
For more information about the NetWorker License Manager, refer to the NetWorker License
Manager Installation and Administration Guide and the NetWorker License Manager Release Notes.
About the NetWorker product 1-3

Introduction
Supported 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:
◆ Autoloader
◆ Carousel
◆ Datawheel
◆ Jukebox
◆ Library
◆ Near-line storage
Enabler codes
Enabler codes (licenses), which activate the functionality of NetWorker software and other
EMC software, are sold separately. For information, see Chapter 6, “Licensing and Enabling
the Software.”

2
Updating from a
Previous Release
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 a Previous Release 2-1

Updating from a Previous Release
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.
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-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, perform
scheduled 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 the
location 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 earlier
than 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” on
page 3-19.
• On Linux for the Itanium processor, see “Uninstalling the NetWorker software” on
page 4-14

4. Install the new release of the NetWorker software.

• For Linux for Intel x86 processors, see “Installing the NetWorker software” on
page 3-9.
• On Linux for the Itanium processor, see “Installing the NetWorker software” on
page 4-6
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.
Updating from a previous release 2-3


3
Linux for Intel x86
Installation
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-9
◆ Verifying the installation ........................................................................................................3-16
◆ Uninstalling the NetWorker software...................................................................................3-19
Linux for Intel x86 Installation 3-1

Linux for Intel x86 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 space
requirements for the software installation file. For information, see “Installation
requirements” on page 3-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. Access the installation files, see “Task 1: Access the NetWorker software” on page 3-10.
4. Install the NetWorker software. For details, see:
• “Task 2: Install the NetWorker software” on page 3-10
• “Task 3: Change the NetWorker servers with access to a client” on page 3-15
• “Task 4: Start the NetWorker daemons” on page 3-15
Note: You must install the Console server software on one computer in your data zone to manage
and monitor the NetWorker server. Only one installation of the Console server is required to
manage multiple NetWorker servers and to take full advantage of the Console’s consolidated
reporting feature.
5. Test the NetWorker software, see “Verifying the installation” on page 3-16.
6. Enable and register all NetWorker products. For information, see Chapter 6, “Licensing
and Enabling the Software.”
Installation requirements
The following sections provide information on the system requirements for the different
components being installed:
• “General requirements” on page 3-3
• “TCP/IP requirements” on page 3-3
• “Client software requirements” on page 3-3
• “Storage node software requirements” on page 3-4
• “Server software requirements” on page 3-4
• “NetWorker Management Console” on page 1-3
Note: NetWorker software does not support locales (defined by the operating system) or code sets that
remap characters that have special meaning for file systems. Depending on the file system, these special
characters might include the forward 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 hostname
of the backup server.
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.
Client software requirements

The following sections describe NetWorker installation requirements and recommendations
for 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 same
installation media and methods. The space requirements remain the same.
If only the NetWorker client software for Linux is being installed, purchase the NetWorker
ClientPak for Linux with a separate enabler code. The NetWorker for Linux software is
licensed as a separate platform.
Note: If client computers have a previous release of the NetWorker ClientPak for Linux installed, update
those clients to the latest NetWorker release to fully exercise all the features in the software. When the
installation identifies an existing NetWorker client package for Linux, it prompts for permission to
update the client. The update process removes the existing NetWorker client and man pages and it
installs the new version of the NetWorker client software.
Before installing the client software, review “Server software requirements” on page 3-4 for
other 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.
Installation requirements 3-3

Client backup and recovery guidelines

A client can be configured to use the NetWorker software to access the NetWorker server in
one 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 the
nsrexecd daemon, type the following command:
Storage node software requirements

At least one supported storage device must be attached and installed. The device can 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.
Server software requirements

for 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 and
monitor the NetWorker server. Only one installation of the Console server is required to manage
multiple NetWorker servers and to take full advantage of the Console’s consolidated reporting feature.
System requirements
Table 3-1 on page 3-4 lists the Linux distributions supported in release 7.3.2 of NetWorker
server software on 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 installed
before beginning the NetWorker software installation. For information, refer to the Linux distribution
software 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

and higher
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

Table 3-2 on page 3-5 lists the minimum memory and storage requirements for the NetWorker
server for Linux software. Additionally, because the client file index and media database that
a NetWorker server generates can grow large over time, the NetWorker server needs enough
free storage space to accommodate these indexes.
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 during
software update conversion)
Install the appropriate storage devices, including SCSI adapter, cabling, and termination,
prior to installing the NetWorker server. The NetWorker installation program assumes that
the storage devices have been properly installed and configured, and that the operating
system recognizes the devices.
For a list of the currently supported devices, refer to the EMC Information Protection Software
Compatibility Guide.
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 and
media database (usually /nsr).
• The system pathname of at least one storage device for use by the NetWorker server to
back up and recover files.
• A directory for the PDF documentation files and for Adobe Acrobat Reader if it is not
already installed.
Table 3-3 on page 3-5 lists the default directories that the NetWorker installation program
creates.
Table 3-3 Default locations and space requirements
Software and documentation files NetWorker server default location Space needed
NetWorker Management Console program /usr/bin 17 MB

/opt/lgtonmc
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 2 MB

/usr/nsr/lic/res 22 KB
/nsr/lic/res 21 KB
NetWorker man pages /usr/share/man 2 MB
PDF files optional varies

Console server software requirements
The general requirements for installing Console software include:

• An installed version 7.3.2 NetWorker client.
• A Java Runtime Environment (JRE), which is required in order to do the following:
• Support the command line reporting feature.
• Run the Console client and display the user interface.
The JRE version must be 1.4.2_11 for all supported Linux versions.
Table 3-4 provides a list of system requirements for installing the Console server and
database.
Table 3-4 Console server system requirements
System feature Requirement
Processor and RAM Minimum: 500 MHz with 128 MB of RAM, 512 MB to run reports. As the number of
servers being monitored increases, increase the computer’s 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
Operating system • Red Hat Advanced Server Edition 2.1

• Red Hat Enterprise Server 3
• SuSE Linux Enterprise Server 8
Note: SuSE version 9.2 is not supported.
NetWorker software NetWorker client, release 7.3.2 software must already be installed and running.
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 • Linux Server: 60 MB + x, where: x is a buffer of disk space for the Console
database. For more information, see “System requirements for the Console client”
on page 3-7.
• JRE with Web Start: 50 MB

System requirements for the Console client

Although the Console client does not need to be installed separately, the JRE which includes
Java Web Start must be installed in order to download and run the program properly.
Installing the JRE on the system requires administration privileges. When connecting to the
Console server for the first time, there is a prompt to download the Console client application.
Table 3-5 provides a list of system requirements for installing the Console client.
Table 3-5 Console client system requirements
System feature Requirement
Operating system • Red Hat Advanced Server Edition 2.1

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
Estimating the size of the Console database

The Console server collects data from the NetWorker servers in the enterprise, and stores the
data in its local Console database. By default, the database is installed on the local file system
with the most available space. Console integrates and processes this information to produce
reports that facilitate trend analysis, capacity planning, and problem detection. For
information about reports, refer to the NetWorker Administration Guide.
To store the collected data, allocate sufficient disk space for the Console database. Several
factors affect the amount of disk space required:
• The number of NetWorker servers monitored for the reports.
• The number of savegroups run by each of those servers.
• The frequency with which savegroups are run.
• The length of time report data is saved (data retention policies).
Note: Since the amount of required disk space is directly related to the amount of historical data stored,
the requirements can vary greatly, on average between 0.5 GB and several GB. Allow for this when
planning hardware requirements.

Estimating the space required for the Console database information

Use the formula presented in Table 3-6 on page 3-8 to estimate the space needed for different
types of data and to estimate the total space required.
Table 3-6 Estimating space requirements for Console database information
To estimate the total By the number of By the number

space required for Multiply NetWorker servers of weeks in the The results indicate
save set media weekly amount of monitored by the save set output The length of time that a save set
database information save sets Console server policy took to run successfully. The
results also identify the number of
files that were backed up, and how
much data was saved during the
operation.
save set output weekly amount of monitored by the save set output The number of save set output
output messages Console server retention policy describes how many groups and
save sets were attempted and their
success or failure.
savegroup completion weekly amount or monitored by the completion data All save output data that could be
data savegroups Console server retention policy 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 bar.
Changing the language locale to match that of localized NetWorker data

There are two ways to change the system language locale to match that of the localized
NetWorker language locale. Choose one of the following:
◆ Before login to the host system:
a. Select Options on the Login dialog box.
b. Select Options>Language.
c. Select a locale from one of three alphabetical lists.
◆ 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
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 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.
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.
Installing the NetWorker software

The following sections explain how to install the NetWorker software:
• “Task 1: Access the NetWorker software” on page 3-10
Installing the NetWorker software 3-9

Task 1: Access the NetWorker software

You can access NetWorker software from a local CD-ROM or the EMC website.
Note: The evaluation version of NetWorker software contains tarred and compressed versions of the
NetWorker software distribution files. Ensure that there is adequate disk space for both the compressed
download file (about 60 MB) and the fully uncompressed files (about 60 MB).
From a local CD-ROM

To access NetWorker software from a local CD-ROM:
1. Log in as root on the computer where the NetWorker software is being installed.
2. Mount the CD-ROM.
3. Locate the /linux_x86 directory on the installation CD-ROM.
4. On both the NetWorker server and client, set the PATH environment variable for user root
to contain the directory where the NetWorker executables reside. For information on this
directory, see Table 3-3, ”Default locations and space requirements,” on page 3-5 .
From the website

To access the installation software from the EMC website:
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 management
download site.
4. Download the evaluation software to the temporary directory and change to that
directory.
5. Uncompress the downloaded software by using the following command:
gunzip nw732_linux_x86.tar.gz
6. Extract the uncompressed, tarred file by using the following command:
tar -xvpBf nw732_linux_x86.tar
The NetWorker distribution software directories and files are listed on the screen as the
extraction proceeds.
7. On both the NetWorker server and client, set the PATH environment variable for the user
root, to contain the directory where the NetWorker executables will be installed, that is
/usr/sbin. For information on this directory, see Table 3-3 on page 3-5.
Task 2: Install the NetWorker software

By default, the NetWorker software is installed in the /usr directory; however, the software
can be installed in a different directory. If you have insufficient disk space on the /usr
partition, 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 3-11
• “Installing to a nondefault location” on page 3-14

Installing to the default location

To install the client, storage node, and server software to the default location, see the
following sections:
• “Client installation” on page 3-11
• “Storage node installation” on page 3-11
• “Server installation” on page 3-12
• “Console server installation” on page 3-12
Client installation
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 the computer designated as the NetWorker client:
1. Log in to the NetWorker Linux client.
2. Change to the directory containing the NetWorker software.
3. Type the following command:
rpm -ivh lgtoclnt-7.3-2.i686.rpm
4. (Optional) To install the man pages, type the following command:
rpm -ivh lgtoman-7.3-2.i686.rpm
You might need to install the UTF-8 converters available with your operating system.
Storage node installation
To install the NetWorker storage node software:
• Install the NetWorker client and storage node software on the computers designated as
storage nodes if you purchased an enabler for storage node support.
• The storage node package must be installed on the NetWorker server, regardless of
whether separate systems are used as designated storage nodes. For instructions, see
“Server software requirements” on page 3-4.
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 required software:

2. Type the following command to install the client and storage node packages:
rpm -ivh lgtoclnt-7.3-2.i686.rpm lgtonode-7.3-1.i686.rpm

Server installation
You must install the Console server software on one computer in your data zone to manage
and monitor the NetWorker server. Only one installation of the Console server is required to
manage multiple NetWorker servers and to take full advantage of the Console’s consolidated
reporting feature.
On the computer designated as the NetWorker server, install all the NetWorker software
packages in the following order: client, storage node, server. The NetWorker License Manager
software can be installed at any point in this sequence after the client package is installed.
To install the software:

2. Type the following commands to install the client, storage node, server, and NetWorker
License Manager software:
rpm -ivh lgtoclnt-7.3-2.i686.rpm lgtonode-7.3-2.i686.rpm
lgtoserv-7.3-2.i686.rpm lgtolicm-7.3-2.i686.rpm
Note: Installing the NetWorker License Manager software is optional. It can be installed any time
after the client software.

The NetWorker software installation modifies these system files during installation. To keep a
copy of the current configuration, save the following original files:
• /etc/rpc
• /etc/syslog.conf
• /etc/ld.so.conf
The following files are added during the installation process:
• /etc/init.d/networker
• /etc/init.d/rc3.d/S95networker
• /etc/init.d/rc0.d/K05networker
Note: You might need to install the UTF-8 converters available with your operating system.
Console server installation
The Console installation relies on the existence of several other components. Ensure that all
installation prerequisites are met. For details, see “System requirements for the Console
client” on page 3-7.

To install NetWorker software on the computer that is designated as the Console server:
1. Install JRE version 1.4.2_11. This enables the command line reporting feature.
a. If the NetWorker software has been downloaded from the web, type the following
command to verify that execute permissions are applied to the JRE file. For example:
chmod +x j2re-1_4_2_11-linux-i586.bin
b. Change to the directory where the JRE is to be installed.
c. Run the following executable:
j2re-1_4_2_11-linux-i586.bin
d. Accept the Java licensing agreement.
3. Type this command to install the NetWorker client software, if not already installed:
rpm -ivh lgtoclnt-7.3-2.i686.rpm
4. Start the NetWorker daemons, if not already started. For information on how to start the
NetWorker daemons, see “Task 4: Start the NetWorker daemons” on page 3-15.
5. Type this command to install the Console software:
rpm -ivh lgtonmc-7.3-2.i686.rpm
By default, the software is installed in /opt.
6. Run this configuration script:
/opt/lgtonmc/bin/nmc_config.sh
7. Follow the prompts to install the software. For example:
• For the web server port number, use the default IP port number (9000) or use a custom
IP port number. Valid IP port numbers are between 1024 and 49151.
• For the Console server, use the default IP port number (9001) or use a custom IP port
number. Valid IP port numbers are between 1024 and 49151.
Note: Do not use IP port numbers that are already in use. Port 2638 is reserved by the Console
software, using Tabular Data Stream (TDS) protocol to communicate with the database.
8. Start the Console daemon if not already started:

/etc/init.d/gst start
The Console daemon includes these processes:
• gstd
• dbsrv9
• gsttclsh
9. If the Console 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"
– Linux or Solaris only host:
nsraddadmin -u "user=root,host=console_host"
b. Specify the Console administrator user:
nsraddadmin -u "user=administrator,host=console_host"
Where console_host is the Console server hostname.
Installing to a nondefault location

By default, the NetWorker software is installed in the /usr directory. If there is insufficient
disk space on the /usr partition, relocate the NetWorker packages to a specified directory on
another partition. For information about directories and space requirements, see “Default
locations and space requirements” on page 3-5.
To install the NetWorker software to a nondefault location:

2. Type the following command to install the NetWorker client, storage node, server, and
NetWorker License Manager software:
rpm -ivh --relocate old path=new path lgtoclnt-7.3-2.i686.rpm
lgtonode-7.3-2.i686.rpm lgtoserv-7.3-2.i686.rpm
Note: The storage node software can be installed any time after the client software is installed.
Installing the NetWorker License Manager software is optional. It can be installed any time after the
client software is installed.
3. Modify the root PATH variable to designate the /usr/bin, /usr/sbin, and /usr/lib/nsr
subdirectories of the directory just created.
For example, if you relocated the /usr/bin directory to a new directory called /backup,
you would type the following command to relocate the /usr/sbin subdirectory:
/backup:/usr/sbin
Note: Installation to a nondefault location is not supported on Red Hat Linux 8.

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

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 be
specified for a client in the /nsr/res/servers file. After installing the client, storage node, and
server software, use the following procedure to change the NetWorker servers that are
authorized 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, 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 recover to the client.
2. If necessary, delete the -s option from the nsrexecd command that is invoked by the
boot-time startup file. Running nsrexecd with the -s option supersedes the
/nsr/res/servers file.
Task 4: Start the NetWorker daemons

Upon startup, the NetWorker software creates the /nsr directory on the root partition. To
change the default location of the nsr directory, do so before starting the NetWorker daemons.
The NetWorker daemons must be started after the installation procedure:
1. Start the NetWorker daemons:
2. Type the following command to determine if the NetWorker daemons are started:
ps -ef | grep nsr
Table 3-7 on page 3-15 lists the NetWorker daemons for each of the software components.
Table 3-7 NetWorker daemons
NetWorker installation packages NetWorker daemons
NetWorker server nsrd, nsrexecd, nsrindexd, nsrmmdbd, nsrmmd, nsrjobd, nsrmmgd, nsrlcpd
NetWorker client nsrexecd
NetWorker storage node nsrexecd, nsrmmd, nsrlcpd
Note: The NetWorker daemon nsrmmd is only present if one or more devices are enabled.

Verifying the installation

This section provides information about testing and verifying the NetWorker software
installation. To verify that the NetWorker software was installed properly, first connect to a
NetWorker server, configure a device, and then test the software on the device.
This section includes these procedures:
◆ “Task 1: Start Console for the first time” on page 3-16
◆ “Task 2: Add a NetWorker server to the Console server” on page 3-17
◆ “Task 3: Configure a device” on page 3-17
◆ “Task 4: Test the NetWorker software installation” on page 3-18
Task 1: Start Console for the first time

These steps assume that the NetWorker software is installed and that all of the software and
hardware requirements have been met on the computer that will access the Console software.
For information about the Console, see “NetWorker Management Console” on page 1-3.
To open Console for the first time:
1. Start a web browser session.
2. Type the URL of the Console server:
http://server_name:http_service_port
where:
• server_name is the name of the computer where the Console server component was
installed.
• http_service_port is the IP port for the embedded HTTP server. (The HTTP port is
specified during installation. The default HTTP port is 9000.)
For example:
http://houston:9000
3. From the Welcome page, click Start.

4. From the Security Warning 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.
7. Click OK.
The Console window appears.

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-16.
• Double-click the NetWorker Management Console product name in the Java Web Start
Application 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 NetWorker
Administration 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 server’s NetWorker Administration interface, click Devices.
2. From the left pane, select Storage Nodes.
3. Right-click the storage node to which the device is to be configured.
4. Select Scan for devices.
The Scan for Devices window appears.
5. From the list, select the storage node to be scanned.
Verifying the installation 3-17

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:
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:
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 general
information 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 of
the following:
– Select the directory or file and click Mark. To clear an item, click Unmark.
– Click the directory or file. When you mark a directory or file for backup, a check
mark appears next to that item.
e. Click Start to begin the ad hoc backup.
The Backup Status dialog box displays the progress of the backup. When the
NetWorker server has successfully finished the backup, the nwbackup program
displays this (or a similar) message:
Backup completion time: 2-15-06 3:27p
Note: If the backup fails, an error message will appear. Error messages are also written to the
NetWorker log file. If the test backup was not successfully completed, refer to the troubleshooting
information in the NetWorker Administration Guide to determine the cause.
Uninstalling the NetWorker software

Use the rpm -e package_name command to uninstall individual NetWorker packages or all of
the NetWorker packages simultaneously. For details about rpm, refer to the rpm man page.
Note: The NetWorker software packages have dependencies on each other and must be uninstalled in
the following order: lgtolicm, lgtoserv, lgtonode, lgtoclnt. The man pages (lgtoman) and document files
have no dependencies and can be uninstalled any time.
The lgtonmc package must be uninstalled before the lgtoclnt package. For information on the
Console server, refer to the NetWorker Administration Guide.
To uninstall the NetWorker software packages:
1. Log in as root to the computer from which the software is being uninstalled.
2. Run a query to see which packages are installed:
rpm -qa | grep lgto
The packages appear in the following format, where 7.x is the release number and -1 is
appended by the RPM utility:
lgtonode-7.3.2
lgtonmc-7.3.2
lgtoclnt-7.3.2
lgtoserv-7.3.2
lgtoman-7.3.2
lgtolicm-7.3.2
Uninstalling the NetWorker software 3-19

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, type 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 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 is
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

4
Linux for Itanium
Processor Installation
This chapter explains how to install the NetWorker software on Linux for the Itanium
processor.
It contains the following sections:
◆ Installing the NetWorker software..........................................................................................4-6
◆ Verifying the installation ........................................................................................................4-10
Linux for Itanium Processor Installation 4-1

Linux for Itanium Processor Installation

Use the following roadmap when installing the NetWorker software:
1. Review the requirements section and note the default directory location and space
requirements 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 NetWorker
software” on page 4-6.
Note: You must install the Console server software on one computer in your data zone to manage
the NetWorker server. Only one installation of the Console server is required to manage multiple
NetWorker 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, “Licensing
and Enabling the Software.”
The following sections provide information on the system requirements for the different
components 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 that
remap characters that have special meaning for file systems. Depending on the file system, these special
characters 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 hostname
of the backup server.
• The TCP/IP hostname must be identical to the computer name. Do not include an
underscore character (_) in the computer name.

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.
• The NetWorker server’s TCP/IP hostname and computer name must be the same.
Client software requirements

for Linux client software:
• “Client backup and recovery guidelines” on page 4-3
System requirements
If the client software is being installed as part of the server installation, use the same
installation media and methods. The space requirements remain the same.
If only the NetWorker client software for Linux is being installed, purchase the NetWorker
ClientPak for Linux with a separate enabler code. The NetWorker for Linux software is
licensed as a separate NetWorker platform.
Before installing the client software, review “Server software requirements” on page 4-4 for
other 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.
Client backup and recovery guidelines

A client can be configured to use the NetWorker software to access the NetWorker server in
one of two ways:
• Install the NetWorker client program directly on the local disk.
• Configure the client with a directory on the NFS on the remote computer where the
NetWorker programs are located.
To back up a NetWorker client, the nsrexecd daemon must be active on the client. To start the
nsrexecd daemon, enter the following command:

Storage node software requirements

At least one supported storage device must be attached and installed. The device can be a
stand-alone device, autochanger, or silo tape library. For a list of supported devices, refer to
Server software requirements

for a Linux server:
• “Directories and pathnames” on page 4-5
System requirements
Table 4-1 on page 4-4 lists the Linux distributions supported in release 7.3.2 of NetWorker
server software on Linux for Itanium Processor, 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 installed
before beginning the NetWorker software installation. For information, refer to the Linux distribution
software documentation or other Linux documentation sources
Table 4-1 Software requirements by supported Linux distribution
Linux distribution Kernel Additional modules, libraries, or upgrades
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
RedHat Advanced Server 2.1 2.4.9-e.3 pdksh-5.2.14-13.i386.rpm
Red Hat Enterprise Server 4 2.6.9-5.EL and pdksh-5.2.14-30.i386.rpm

higher
Table 4-2 on page 4-4 lists the minimum memory and storage requirements for the NetWorker
Server for Linux software. Additionally, because the client file index and media database that
a NetWorker server generates can grow large over time, the NetWorker server needs enough
free storage space to accommodate these indexes.
Table 4-2 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 during
software update conversion)

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 during
the 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 that
the storage devices have been properly installed and configured, and that the operating
system recognizes the devices.
Note: For a list of the currently supported devices, refer to the EMC Information Protection Software
Compatibility Guide.
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 and
media database (usually /nsr).
• The system pathname of at least one storage device for use by the NetWorker server to
back up and recover files.
• A directory for the PDF documentation files and for Adobe Acrobat Reader if it is not
already installed.
If the default locations and space requirements are accepted during installation, the
installation script creates the directories listed in Table 4-3 on page 4-5.
Table 4-3 Default locations and space requirements
Software and documentation files NetWorker server default location Space needed
NetWorker Administrator program and NetWorker /usr/bin 29 MB

Client program files
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/sbi 2 MB

/usr/nsr/lic/res 22 KB
/nsr/lic/res 21 KB
NetWorker man pages /usr/share/man 2 MB
PDF files optional varies

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 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 the
NetWorker software distribution files. Ensure that there is adequate disk space for both the
compressed 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:
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 root
to contain the directory where the NetWorker executables reside. For information on this
directory, see Table 4-3, ”Default locations and space requirements,” on page 4-5 .
From the EMC website

To access the installation software from the EMC website:
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 management
download site.
4. Download the evaluation software to the temporary directory and change to that
directory.
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 the
extraction proceeds.
7. On both the NetWorker server and client, set the PATH environment variable for the user
root, to contain the directory where the NetWorker executables will be installed, that is
/usr/sbin. For information on this directory, see Table 4-3 on page 4-5.

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 /usr
partition, 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 the
following sections:
• “Client installation” on page 4-7
• “Storage node installation” on page 4-7
• “Server installation” on page 4-8
Client installation
To install the NetWorker software on computers designated as NetWorker clients:

1. Log in to the NetWorker Linux client.
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
Storage node installation

Install the NetWorker software on the following systems:
• Install the client and storage node software on the computers designated as storage nodes
if you purchased an enabler for storage node support.
• The storage node package must be installed on the NetWorker server, regardless of
whether separate systems are designated storage nodes. For instructions, see “Server
installation” on page 4-8.

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:
Server installation
On the computer designated as the NetWorker server, install all the NetWorker software
packages in the following order: client, storage node, server. The NetWorker License Manager
can 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 NetWorker
License Manager software:
rpm -ivh lgtoclnt-7.3-2.ia64.rpm lgtonode-7.3-2.ia64.rpm
lgtoserv-7.3-2.ia64.rpm lgtolicm-7.3-2.ia64.rpm
after the client software.

The installation process adds the following files:
• /etc/init.d/networker
• /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 insufficient
disk space on the /usr partition, relocate the NetWorker packages to a specified directory on
another partition. For information about directories and space requirements, see Table 4-3 on
page 4-5.

To install the NetWorker software to a nondefault location:

2. Enter the following command to install the NetWorker client, storage node, server, and
NetWorker License Manager software:
rpm -ivh --relocate old path=new path lgtoclnt-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, you
would enter the following command to relocate the /sbin subdirectory:
rpm -ivh --relocate /usr/bin=/backup lgtoclnt-7.3-2.ia64.rpm
lgtonode-7.3-2.ia64.rpm lgtoserv-7.3-2.ia64.rpm lgtolicm-7.3-2.ia64.rpm
after the 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 subdirectories
of 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 be
specified for a client in the /nsr/res/servers file. After installing the client, storage node, and
server software, use the following procedure to change the NetWorker servers that are
authorized 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, 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:
2. If necessary, delete 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

Task 4: Start the NetWorker daemons

Upon startup, the NetWorker software creates the /nsr directory on the root partition. To
change the default location of the nsr directory, do so before starting the NetWorker daemons.
The NetWorker daemons must be started after the installation procedure:
1. Start the NetWorker daemons:
2. Enter the following command to determine if the NetWorker daemons are started:
ps -ef | grep nsr
Note: The NetWorker daemon nsrmmd is present only if one or more devices are enabled.
Table 4-4 on page 4-10 lists the NetWorker daemons for each of the software components.
Table 4-4 NetWorker daemons
NetWorker installation packages NetWorker daemons
NetWorker server nsrd, nsrexecd, nsrindexd, nsrmmdbd, nsrmmd, nsrjobd, nsrmmgd, nsrlcpd
NetWorker client nsrexecd
NetWorker storage node nsrexecd, nsrmmd, nsrlcpd
Verifying the installation

This section provides information about testing and verifying the NetWorker software
installation. To verify that the NetWorker software was installed properly, first connect to a
NetWorker server, configure a device, and then test the software on the device.
This section includes these procedures:
◆ “Task 1: Start Console for the first time” on page 4-10
◆ “Task 2: Add a NetWorker server to the Console server” on page 4-11
◆ “Task 3: Configure a device” on page 4-12
◆ “Task 4: Test the NetWorker software installation” on page 4-13
Task 1: Start Console for the first time

These steps assume that the NetWorker software is installed and that all of the software and
hardware requirements have been met on the computer that will access the Console software.
For information about the Console, see “NetWorker Management Console” on page 1-3.
To open Console for the first time:
1. Start a web browser session.
2. Type the URL of the Console server:
http://server_name:http_service_port

where:
• server_name is the name of the computer where the Console server component was
installed.
• http_service_port is the IP port for the embedded HTTP server. (The HTTP port is
specified during installation. The default HTTP port is 9000.)
For example: http://houston:9000
3. From the Welcome page, click Start.
4. From the Security Warning 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.
7. Click OK.
The Console window appears.
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 4-10.
• Double-click the NetWorker Management Console product name in the Java Web Start
Application Manager.
Task 2: Add a NetWorker server to the Console server

To add and select a NetWorker server:
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 NetWorker
Administration 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 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.
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:
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 general
information 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 of
the following:
– Select the directory or file and click Mark. To clear an item, click Unmark.
– Click the directory or file. When you mark a directory or file for backup, a check
mark appears next to that item.
e. Click Start to begin the ad hoc backup.
The Backup Status dialog box displays the progress of the backup. When the
NetWorker server has successfully finished the backup, the nwbackup program
displays this (or a similar) message:
Backup completion time: 2-15-06 3:27p
Note: If the backup fails, an error message will appear. Error messages are also written to the
NetWorker log file. If the test backup was not successfully completed, refer to the troubleshooting
information in the NetWorker Administration Guide to determine the cause.


Use this command to uninstall individual NetWorker packages or all of the NetWorker
packages at the same time:
rpm -e package_name
For 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 dependencies
and 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 is
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 -e package_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

5
EMC AutoStart
Installation
This chapter explains how to install NetWorker software in an EMC AutoStart™ environment
(formerly EMC Automated Availability Manager™).
◆ 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
Note: EMC AutoStart is supported on the Linux for the Intel x86 platform. It is not supported on other
NetWorker Linux platforms.
EMC AutoStart Installation 5-1

EMC AutoStart Installation

Use the following roadmap when installing the NetWorker software. Read the roadmap and
the referenced sections before installing the software.
1. Review the requirements section and note the default directory location. For 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.”
The following sections discuss the software and hardware required to install and configure
the NetWorker server or client software within a EMC AutoStart cluster environment:
• “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 to
Software requirements
To install a NetWorker cluster server, ensure that the following software is installed on each
node 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 met
for server installation only:
• Dedicated shared disk used as the NetWorker storage disk (for the /nsr directory)
connected to all the nodes within the cluster.
• Device with local affinity for the local bootstrap backup connected to all the nodes within
the cluster.

Configuration options
Refer to the NetWorker Administrators Guide for information on how to configure:
• Tape libraries with a NetWorker virtual server.
• Remote physical storage node with a NetWorker virtual server.
System information requirements

Figure 5-1 on page 5-3 and Table 5-1 on page 5-3 display the system information needed to
install NetWorker software within a EMC AutoStart environment.
Different platforms use different terms for the same cluster concepts. EMC AutoStart refers
to:
• Physical hosts as nodes
• Virtual server as a Resource Group (application service)
Node A Node B
clus_phys1 clus_phys2
(If Node A fails,

Local clus_vir1 fails
Disk 1 over to Node B) Local
Disk 2
NetWorker Virtual Server
Shared Disks 3
Public Network
Figure 5-1 Sample cluster configuration
Table 5-1 Required information (Sheet 1 of 2)
Required information Example
NetWorker virtual name with an IP address clus_vir1; 192.168.1.10
NetWorker package mount point for virtual volume /nsr_shared_mnt_pt
Shared storage disk virtual volume /dev/sdc1
NetWorker control script /usr/sbin/nsr/nw_ux.lc
File containing the host IDs of all the cluster members /nsr/res/hostids

Table 5-1 Required information (Sheet 2 of 2)
Required information Example
NetWorker monitor script /usr/sbin/nsr/nw_ux.lc
Console virtual hostname clus_vir2 192.168.1.11
Console database mount point nmc_shared_mnt_pt
Installing a NetWorker virtual server

To install and configure the NetWorker software as a highly available service in a cluster, read
and follow the procedures for these tasks:
• “Task 1: Ensure that the EMC AutoStart software is installed” on page 5-4
• “Task 2: Install the NetWorker software in a cluster” on page 5-4
• “Task 3: Define the NetWorker server as highly available” on page 5-4
• “Task 4: Grant access to the NetWorker virtual server” on page 5-6
• “Task 5: Configure the NetWorker server” on page 5-7
• “Task 6: Configure clients under the NetWorker server” on page 5-7
• “Task 7: Register NetWorker licenses for virtual server failover” on page 5-8
Task 1: Ensure that the EMC AutoStart software is installed

Ensure that the EMC AutoStart software is installed. For installation instructions, refer to the
EMC AutoStart documentation.
For EMC AutoStart Release 5.1.2, you must install the following hotfix:
ftp.legato.com/pub/cluster/patches/5.1/unix
Task 2: Install the NetWorker software in a cluster

To install the NetWorker software:
1. Ensure that the most recent cluster patch for the operating system is installed.
2. Install the following NetWorker software on each node in the cluster:
• NetWorker client
• Storage node
• NetWorker server
• NetWorker man pages
For instructions, see “Installing the NetWorker software” on page 3-9.
Task 3: Define the NetWorker server as highly available

To define and configure NetWorker server as a highly available application:
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 Network
Information 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:
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/sbin
directory.
b. Type the following information:
– Location of the local NetWorker database directory provided during the
installation 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 its
dependant objects.
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.
Follow the instructions listed in the comments at the beginning of the

nw_ux.lc.aam5.imp file to customize the following NetWorker default values based on
the cluster configuration:
– Virtual host’s 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-1 on page 5-3.
Installing a NetWorker virtual server 5-5

6. Type this command.

$FT_DIR/bin/ftcli -c “import /opt/lgtonmc/bin/nw_ux.lc.aam5.imp”
7. Verify that the NetWorker resource group was imported correctly, by using the EMC
AutoStart Console.
8. Run the following script located in the /usr/sbin directory:
nwinst.sh
Task 4: Grant access to the NetWorker virtual server

Before a NetWorker server can backup a client, the client must grant the server access.
Granting access is controlled by the /nsr/res/servers file.
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 services 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
2. On one node in the cluster, start the NetWorker service by using the cluster management
software.
a. Bring the NetWorker Resource Group online by using ftconsole.
b. Edit or create the /nsr/res/servers file:
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 services have
stopped.

b. Edit or create the /nsr/res/servers file:

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 start
the 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 already
listed. 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, that
points to a local disk. It also creates a second link named nsr.NetWorkerBackup.local that
points to the local NetWorker directory. For example, if the local NetWorker directory was
created 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 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:
b. For the Name attribute, type the name of the virtual client.
Installing a NetWorker virtual server 5-7

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.
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 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 the
appropriate 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 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
that use the composite host ID that was created in step 4.

Installing a virtual Console server

To install and configure the Console software as a highly available service in a cluster, read
and 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-9.
Task 2: Define the Console server as highly available

To define and configure the Console server as a highly available application on each node in
the cluster:
1. Log in as root.
The virtual hostname can be published in the Domain Name System (DNS) or Network
Information Service (NIS).
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
Installing a virtual Console server 5-9

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 Customize”
comment, ensure that all entries are replaced with the appropriate cluster configuration values.
Follow the instructions listed in the comments at the beginning of the gst_ha_ux.aam5.imp
file to customize the following Console default values based on the cluster configuration:
• Virtual host’s 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-1 on page 5-3.
$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 EMC
AutoStart 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 the
cluster.
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.

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.
The virtual hostname can be published in the DNS or NIS.
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.
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 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 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 following in the file:
-s servername
Installing only the NetWorker client software in a cluster 5-11
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 server.
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 cluster.
For example:
root@clus_phys1
c. For the Group attribute, select a group.
3. Schedule backups by using the NetWorker Administrator program. For detailed
instructions, 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 is
authorized to:
To configure and back up an external NetWorker client to a NetWorker server, perform the
following on each NetWorker client that is outside of the 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 virtual
NetWorker server. For example:
clus_vir1
clus_phys1
clus_phys2

Defining ownership of a raw partition for virtual clients

Use the IPOverride option to back up the raw partitions of a NetWorker virtual client, as
described 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 Define Resource Group Attributes window opens.
3. Add the following line in the Define Resource Group Attributes window:
IPOverride=IP_address=raw_partition_path
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 file system
/share/web, set the following path:
IPOverrride=135.69.103.149=/dev/rdsk/c1t3d0s1, /share/web
Tracking scheduled saves

To verify that the Client and Group resources have been properly configured, run a test probe
for each client from the node where the NetWorker is running:
savegrp -pv -c client_name group_name
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 more information, see NetWorker Administration Guide.
To override scheduled save rules (not path ownership rules), type the following command on
each node in the cluster. This command allows any path to be backed up for a client, whether
it is owned by the virtual client or physical node:
touch networker_bin_dir/pathownerignore
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 Cmmand attribute, type the name of a backup script that contains:
save -c client_name
For details about the Backup Command attribute, refer to the NetWorker Administration Guide.
Defining ownership of a raw partition for virtual clients 5-13


To uninstall the NetWorker software from a cluster environment:
1. If necessary, use the cluster management software to stop the NetWorker server services.
2. Shut down the client services on the node on which the NetWorker software is being
removed:
nsr_shutdown
3. Ensure that the $FT_DIR and the $FT_DOMAIN environment variables have been set.
/usr/sbin/networker.cluster -r
5. Remove the subsets for the following packages with the rpm command in the following
order, as follows:
rpm -e lgtoman-7.3-1 lgtolicm-7.3-1 lgtoserv-7.3-1 lgtonode-7.3-1
lgtoclnt-7.3-1

6
Licensing and Enabling
the Software
This chapter explains how to enable the NetWorker software and features for permanent use.
The chapter also describes the EMC NetWorker licensing model and provides a basic
explanation of licensing for the different NetWorker Editions, modules, and features, but it
does not provide a comprehensive description of every possible licensing scenario. For
specific licensing questions, go to http://softwaresupport.EMC.com.
When the NetWorker software is installed, it is in a temporary evaluation mode with all of the
features available.
The chapter includes these sections:
◆ How NetWorker software is licensed .....................................................................................6-2
◆ The evaluation process .............................................................................................................6-2
◆ The licensing process ................................................................................................................6-3
◆ Multiplatform licensing ............................................................................................................6-6
◆ Managing NetWorker licenses.................................................................................................6-8
Licensing and Enabling the Software 6-1

Licensing and Enabling the Software
How NetWorker software is licensed

NetWorker software and added features, such as modules, are installed in evaluation mode.
The licensing of NetWorker software means entry of enabler and authorization codes on the
server for the NetWorker environment. Without these codes, the software or added features
will not run beyond the evaluation period.
Each installation of NetWorker server software must be licensed with a base enabler. This
enabler “turns on” the software and allows you to use a particular bundle of features, such as
a specified number of clients and devices. All licensing takes place on the server. The licenses
are entered and stored on the server. The server enforces the licensing.
Base enablers come in different editions, which enable varying degrees of functionality.
Add-on enablers allow a broader scope of features.
The steps in this chapter assume that the NetWorker software is installed and that all of the
software and hardware requirements have been met on the computer that will access
Console. For information about the Console, see “NetWorker Management Console” on
page 13.
The evaluation process

Evaluating NetWorker software can take place in two ways:
◆ By evaluating a new installation of the software on a NetWorker server
◆ By evaluating NetWorker features on an existing NetWorker installation
Evaluating a new installation

When you first install the NetWorker software, you can evaluate it with all the modules and
features for 30 days free without entering any codes.
By the end of the evaluation period, you must purchase, enter, and authorize a base enabler to
continue to use the NetWorker software to back up data. The base enabler is the license that
enables the edition purchased. Go to http://softwaresupport.EMC.com for information.
To continue to use some of the modules and features that were available with the evaluation
software, you may need to purchase add-on enablers, depending on the edition of the base
enabler.
Evaluating features on an existing installation

If you are evaluating one or more NetWorker Modules or features on an edition of NetWorker
software that has already been installed and enabled, enter a temporary enabler for each
module or feature. The temporary enabler is valid for 45 days.
◆ To obtain a temporary enabler code, refer to the EMC Information Protection Media Kit or
go to http://softwaresupport.EMC.com.
◆ “How to enter a temporary enabler code” on page 63 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 63 provides instructions. “Multiplatform licensing” on
page 66 provides information on the different NetWorker features.

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

2. Launch the Administration window:
a. From the Console window, click Enterprise.
b. From the left pane, select a NetWorker server in the Enterprise list.
c. From the right pane, select the application.
d. From the Enterprise menu, click Launch Application. The Administration window is
launched as a separate application.
3. From the Administration window, click Configuration.
4. In the left pane, select Registration.
6. In the Enabler Code attribute, type the enabler code.
7. In the Name attribute, type the name of the license.
8. (Optional) In the Comment attribute, type a description of the license.
9. Click OK.
The licensing process

To permanently use NetWorker software, you must purchase and enter a license enabler code,
and then authorize it. This licensing process is the same for all editions of NetWorker software
as well as for individual modules and features.
The license enabler code that you purchase is valid for 45 days, as a registration period.
During the registration period, you must obtain and enter a corresponding authorization
code.
These sections explain how to enter and authorize the license enabler:
◆ “Task 1: Enter the license enabler code” on page 64
◆ “Task 2: Obtain an authorization code” on page 64
◆ “Task 3: Enter the authorization code” on page 65
The licensing process 6-3

Task 1: Enter the license enabler code

License enabler codes are included in either the letter announcing the updated or upgraded
software, or on the Enabler Certificate you receive when you purchase a software license. This
depends on whether the software purchased is a first-time purchase or an updated or
upgraded version.
Note: To save time when entering multiple licenses, enter the base enabler last. Otherwise, once a base
enabler is entered, devices that do not yet have licenses entered may be disabled. Those devices would
have to be reenabled manually after their licenses are installed.
To enter the license enabler code:

b. From the left pane, click a NetWorker server in the Enterprise list.
c. From the right pane, click the application.
d. From the Enterprise menu, select Launch Application. The Administration window
is launched as a separate application.
3. In the Administration window, click Configuration.
4. In the left pane, select Registrations.
The Create Registration dialog box appears.
6. In the Enabler Code attribute, type the enabler code.
7. In the Name attribute, type the name of the license.
8. (Optional) In the Comment attribute, type a description of the license.
9. Click OK.
The new license is added and appears in the right pane. Repeat the procedure to add any
additional enabler codes.
After you type a license enabler code, you have 45 days as a registration period to authorize
the NetWorker software.
Task 2: Obtain an authorization code

Registration of NetWorker software takes place by obtaining an authorization code. Obtain a
unique authorization code through one of these methods:
◆ “By using the EMC website” on page 65
◆ “By using email” on page 65
! CAUTION
If the software or feature is not authorized by the end of the 45-day registration period, the
NetWorker backup function or feature is disabled. However, data that was backed up
during the registration period can still be recovered from local devices.

By using the EMC 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:
4. In the left pane, select the NetWorker server.
5. From the File menu, select Properties.
The Properties dialog box appears.
6. Select the Customer Information tab and complete your contact information.
7. Email your registration information. For contact information, go to the EMC
CustomerNet portal at http://softwaresupport.EMC.com.
An authorization code that permanently enables the updated NetWorker software will be
sent to you.
Task 3: Enter the authorization code

To complete the licensing process, you must enter the unique authorization code on the
NetWorker server within 45 days of entering the license enabler code.
If the authorization process is successful, the expiration date for the license displays
“Authorized - No expiration date.” If the authorization is not verified in this way, contact
To avoid an interruption in scheduled backups if you move the NetWorker software from one
computer to another, or to change the network address of a computer after the software is
installed, perform one of the following:
◆ Obtain a new authorization code. You need the host ID of the original server as well as the
new server. The host ID appears in the server’s Registration window. For contact
information, go to the EMC CustomerNet portal at http://softwaresupport.EMC.com.
◆ Install and configure the EMC NetWorker License Manager software. “Managing
NetWorker licenses” on page 68 provides information on use of the NetWorker License
Manager, and the latest EMC NetWorker License Manager Installation and Administration
Guide.
The licensing process 6-5

How to enter the authorization code

To enter the authorization code:
4. In the left pane, select Registration.
5. In the right pane, select a license.
6. From the file menu, select Properties.
7. In the Auth Code attribute, type the authorization code for the product (the authorization
code assigned to the specified permanent enabler or update enabler code).
8. Click OK.
The license is now permanently enabled.
Multiplatform licensing
The client connections that come with a NetWorker server can be used for only that server
platform. A NetWorker ClientPak license allows the NetWorker server to back up clients of
different platforms. For example:
◆ The client connections accompanying a NetWorker server for Microsoft Windows can be
used for Windows client computers only.
◆ The client connections accompanying a NetWorker server for Solaris can be used for
Solaris clients only.
With a ClientPak for UNIX, other UNIX platforms can be enabled for use with a NetWorker
server for Solaris. The ClientPak for UNIX supports all UNIX platforms. The UNIX ClientPak
is sufficient for all UNIX clients (backed up by a UNIX or Windows server).
Note: The NetWorker software treats Linux as a separate operating system. A ClientPak for Linux is
necessary to back up Linux clients by either UNIX or Windows servers.
Example 6-1 Multiplatform licensing scenarios
A company was using a Linux server to back up Solaris, Linux, and Windows clients. It
needed two ClientPak licenses, one for Solaris and one for Windows. The company added
HP-UX and AIX clients, which required the addition of a ClientPak license for UNIX.
As the company grew and needed to add a server, it added a Windows 2000 server, which
backed up the existing Windows clients and subsequent Windows 2000 clients without
requiring a ClientPak. The company assigned the NetWorker server to a Solaris computer to
back up the HP-UX, Solaris, and AIX clients by using a single ClientPak for UNIX.

Update enablers
To update existing NetWorker software to a major release, an update enabler is necessary.
Update enablers are required for any major NetWorker software upgrade from release 4.0
and later, including the current NetWorker release. To use the NetWorker License Manager,
the NetWorker server must be release 5.0 or later.
With a first-time purchase of NetWorker software, a one-year update agreement may be
included. After a year, an update enabler may be acquired with a new update agreement
purchase.
Table 6-1 on page 6-7 lists the NetWorker releases that require update enablers.
Table 6-1 NetWorker update enablers
Upgrade from to 5.0 to 5.5 to 5.5.x to 5.6 to 5.7 to 6.x to 7.0 to 7.1 to 7.2 to 7.3
Any release prior to yes yes yes yes yes yes yes yes yes yes
5.0
5.0 yes yes yes yes yes yes yes yes yes
5.5 yes yes yes yes yes yes yes yes

(UNIX (NT only)
only)
5.5.x yes yes yes yes yes yes yes

(UNIX (NT only)
only)
5.6 NA* yes yes yes yes yes
5.7 yes yes yes yes yes
6.0 no yes yes yes yes
7.0 yes yes yes
7.1 yes yes
7.2 yes
Note: * Release 5.6 is UNIX only, and release 5.7 is Microsoft Windows only. NT refers to Windows NT.
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 68 or “NDMP licensing” on page 68.
Storage nodes
Each storage node requires a storage node license, in addition to its client connection license.
A dedicated storage node, which allows the storage node to back up only itself, is licensed
separately.
Multiplatform licensing 6-7

NetWorker Application Modules

NetWorker Application Modules are licensed on the basis of one enabler per database type
host. For example, to back up the Oracle database on two hosts, two NetWorker Module for
Oracle enablers are required, even if the two hosts are backed up by the same server.
However, if multiple database instances are running on a NetWorker client host, only one
NetWorker Module enabler is required for that one host.
Cluster clients
For each physical node in a cluster, you must purchase a Cluster Client Connection, which
takes the place of one standard client connection. The NetWorker Administration Guide
provides information on how to license computers in a cluster.
NDMP licensing
NDMP licensing requires one NDMP Client Connection per NDMP data server. The NDMP
Client Connection is valid for any supported NDMP data server. The NDMP data server does
not require a standard client connection.
Managing NetWorker licenses

The NetWorker License Manager software provides centralized license management,
allowing you to maintain all of an enterprise’s NetWorker licenses from a single computer.
With the NetWorker License Manager, you can move NetWorker software from one computer
to another, or change the IP address on an existing NetWorker server without having to
reauthorize the software. The NetWorker License Manager can be installed as an option
during the NetWorker software installation.
To begin to implement the NetWorker License Manager:
1. Contact EMC Licensing to obtain bulk enabler codes. For contact information, go to
2. Install the NetWorker License Manager software.
3. Configure the NetWorker License Manager software.
4. Configure the NetWorker servers to access the NetWorker License Manager for their
licenses.
The latest NetWorker License Manager Installation and Administration Guide provides more
information on how to install and use the NetWorker License Manager.

A
Sample stinit.def File
For optimal tape device performance, and to ensure that all NetWorker tape operations
function properly, EMC recommends that you modify the stinit.def file in the /etc directory,
as appropriate for your device.
Note: The package that provides the stinit binary is mt-st.
Each stinit.def file definition is specific to the manufacturer and model of the tape device
being configured for NetWorker operations, and is based on the requirements defined in the
stinit(8) Linux man page. For further information about stinit(8), see Appendix B, “stinit(8)
Man Page,” and stinit(8), st(4), mt(1) in the Linux kernel source tree.
Sample stinit.def File A-1

Usage
The examples in this appendix are intended only to be used as guidelines and should be
installed as /etc/stinit.def after necessary modifications have been made for the tape device
model and manufacturer. Once installed, reboot the system to ensure that the settings in this
file will be used.
To ensure you have accurate and current stinit.def file information, refer to the tape device
manufacturer’s requirements for the specific device and model being used. In addition, the
EMC Information Protection Software Compatibility Guide provide stinit file definition
information to which you can refer.
Examples of the stinit file

The following definitions are a few examples for devices supported by the NetWorker
software, and are based on the instructions in the stinit(8) manual page released with Linux
7.0 and later.
Device requirements might be different than the parameters specified in these examples.
Users can change these sample definitions to specify the manufacturer and model fields in the
/etc/stinit.def file to correspond to the actual tape device being defined, and modify the
suboptions as necessary.
Note: The manufacturer, model, and revision strings can be obtained from the file /proc/scsi/scsi by
using the cat /proc/scsi/scsi command. Replace the XYZ and UVWx strings that are displayed in the
following examples with the manufacturer and model of your drive.
Common definitions to all devices in the examples:

{buffer-writes read-ahead async-writes }
SONY AIT-3
manufacturer=SONY model = "SDX-700C" {
can-bsr scsi2logical drive-buffering
timeout=800
long-timeout=14400
mode1 blocksize=0 density=0x00 # as close as possible to st.conf entry }
Noncompressing DAT (DDS-1)

manufacturer=XYZ model = “UVW1” {
scsi2logical=1 can-bsr can-partitions auto-lock
mode1 blocksize=0
mode2 blocksize=1024 }
Compressing DAT (DDS-1-DC or DDS-[234])

scsi2logical=1 can-bsr can-partitions auto-lock
mode1 blocksize=0 compression=1
mode4 blocksize = 1024 compression=0 }
A-2 EMC NetWorker for Linux, Release 7.3.2, Installation Guide

QIC-150 drive
manufacturer=XYZ model=”UVW3” {
mode1 # blocksize=512 defined by drive }
QIC-320/525 drive
manufacturer=XYZ model=”UVW4” {
defs-for-writes
mode1 blocksize=0 density=0x11 # QIC-320
mode2 blocksize=1024 density=0x11 # QIC-320
mode3 blocksize=512 density=0x10 # QIC-150 }
Exabyte 8505 and other similar 8 mm helical scan drivers

scsi2logical=1 can-bsr auto-lock
mode1 blocksize=0 density=0x8c # 8500 density, compressing
mode2 blocksize=0 density=0x15 # 8500 density, no compression
mode3 blocksize=0 density=0x90 # 8200 density, compressing
mode4 blocksize=0 density=0x14 # 8200 density, no compression }
Reel-to-Reel tape with 6250/1600/800 bpi densities

can-bsr two-fms
mode1 blocksize=0 density=3 # 6250 bpi
mode2 blocksize=0 density=11 # 1600 bpi
mode3 blocksize=0 density=1 # 800 bpi }
Examples of the stinit file A-3

A-4 EMC NetWorker for Linux, Release 7.3.2, Installation Guide

B
stinit(8) Man Page
This appendix provides the stinit(8) man page contents. The program and the manual page
are copyrighted by Kai Makisara, 1998-2001. They can be distributed according to the GNU
Copyleft. EMC expressly disclaims any rights in or responsibility for the contents of this
appendix. This man page may be obtained from www.fifi.org/cgi-bin/man2html?stinit+8.
stinit(8) Man Page B-1

stinit(8) Man Page
Synopsis
stinit [-f conf_file] [-h] [-p] [-r] [-v] [devices...]
Description
This manual page documents the tape control program stinit that can be used to initialize
SCSI tape drive modes at system startup, after loading the tape driver as module, or after
introducing a new device to the SCSI subsystem at runtime. The initialization is performed by
sending ioctl commands to the drive. The commands are defined in a text file that is indexed
using the inquiry data the drive returns (manufacturer, device, revision). Values for all of the
general and mode-specific SCSI tape parameters up to Linux version 2.4.15 can be initialized.
Options
Table B-1 lists the options for the stinit(8) man page.
Table B-1 stinit(8) Man Page Options
Option Description
-f Specifies the name of the text file containing the definitions for different tape drive types.
By default stinit tries to find the definition file stinit.def or /etc/stinit.def (in this order).
-h Print the usage information.
-p The definition file is parsed but no tape drive initialization is attempted. This option can be
used for testing the integrity of a definition file after changes have been made.
-r Rewind every device being initialized.
-v The more -v options (currently up to two), the more verbose output.
--version Print the program version.
The devices being initiated

If the program is started without arguments, it tries to find all accessible SCSI tape devices
and the device files for the different modes of the devices. The tape drives are searched in the
scanning order of the kernel, and searching stops at the first nonexisting tape. All of the found
devices are initialized if a matching description is found from the parameter file. Note that a
mode for a device is not initialized if the corresponding device file is not found, even if a
matching description for the mode exists. The nonrewind device is preferred over the
auto-rewind device for each mode. If the directory /dev/tapes is found, the devfs file system
is assumed. The configuration file is a simple text file that contains descriptions of tape drives
and the corresponding initialization parameters. The parameter definition blocks are
delimited by braces [ { } ]. Specification of the drive description is restarted after each
parameter definition block.
The drive descriptions and the parameter definitions consist of name = value pairs. The value
is either a numeric parameter, a string with no blanks, or a quoted string. If =value is omitted,
the value "1" is used. If the number sign [#] is found in an input line, the rest of the line is
discarded. This allows use of comments in the definition file.
B-2 EMC NetWorker for Linux, Release 7.3.2, Installation Guide

stinit(8) Man Page
The following example contains definitions for one type of tape drives:
# The XY dat
manufacturer=XY-COMPANY model = "UVW DRIVE" {
scsi2logical=1 # Common definitions for all modes
can-bsr can-partitions auto-lock
# Definition of modes
mode4 blocksize = 1024 compression=0 }
The devices are identified using zero or more of the following keywords corresponding to the
data the tape device returns in response to the SCSI inquiry command. The matches are
case-sensitive and performed up to the length defined in the configuration file (permitting
use of partial matches).
Table B-2 on page B-3 lists device identification.
Table B-2 Device identification
Keyword Description
manufacturer= This keyword specifies the string that must match the vendor identification returned by the device.
model= This keyword defines the string that must match the product identification returned by the device.
revision= This keyword matched the string that must match the product revision level returned by the device.
All of the matching initializations are collected in the order they are defined in the file. This
means that common parameters can be defined for all devices using zero keywords for a
definition block. Another consequence is that, for instance, some parameters can be easily
given different values for a specific firmware revision without repeating the parameters
common to all revisions.
The tape parameters are defined using the following keywords. More thorough descriptions
of the parameters can be found in the st(4) man page or in the drivers/scsi/README.st file in
the Linux kernel source tree. The keywords are matched using only the first characters. The
part of the keywords not used in matching is enclosed in brackets. The numeric values may
be specified either in decimal notation or hexadecimal notation (using the prefix 0x).
Return Value
The program exits with value of one if the command line is incorrect, the definition file is not
found, or the -p option is given and parsing the definition file fails. In all other cases the
return value is zero (that is, failing of initialization is not currently signaled by the return
value).
Table B-3 on page B-3 lists tape parameter information.
Table B-3 Tape parameter information (Sheet 1 of 2)
Value Description
no-w[ait] The immediate mode is used with commands like rewind if value is non-zero (that is, the
driver does not wait for the command to finish).
mode=value This keyword starts the definition of the tape mode value. The value of this mode must be
between 1 and 4.
Return Value B-3

stinit(8) Man Page
Table B-3 Tape parameter information (Sheet 2 of 2)
Value Description
disab[led]=value This mode is disabled for this device if value is non-zero. Can be used if some mode
defined in a more general definition should be disabled by a more specific definition for
some device (for example, for a device with buggy firmware level).
block[size]=value The default tape block size is set to value bytes. The block size zero means variable block
mode.
dens[ity]=value The tape density code is set to value.
buff[ering]=value The buffered writes by the driver in fixed block mode are enabled if value is non-zero.
async[-writes]=value Asynchronous writes by the driver are enabled if value is non-zero.
read[-ahead]=value Read-ahead by the driver in fixed block mode is allowed if value is non-zero.
two[-fms]=value Two filemarks are written when a file being written to is closed if value is non-zero. By
default, one filemark is written.
comp[ression]=value Compression of the data by the drive is enabled if value is non-zero. Note that the tape
driver can't enable compression for all drives that can compress data. Note also that some
drives define compression using density codes.
auto[-lock]=value The tape drive door is locked automatically when the device file is opened and if the value
is non-zero.
noblk[limits]=value The tape driver does not use the READ BLOCK LIMITS SCSI command when the device
is being opened if value is non-zero. This is for the drives that do not support this SCSI
command.
can-p[artitions]=value The support for tape partitions is enabled if value is non-zero.
scsi2[logical]=value Logical block addresses are used in the MTSEEK and MTIOCPOS commands if value is
non-zero. The default is to use the device-specific addresses.
defs-for-w[rites]=value The parameters defining the tape format (density, block size) are forced when writing
starts at the beginning of a tape if value is non-zero. The default is to change these
parameters each time the device is opened at the beginning of a tape (or the mode is
changed in the middle of a tape).
timeout The normal timeout for the device is set to value seconds.
long-time[out] The long timeout for the device is set to value seconds.
Restrictions
With the exception of the -p option, only the superuser can use the stinit program. This is
because the program uses ioctls allowed only for the superuser.
B-4 EMC NetWorker for Linux, Release 7.3.2, Installation Guide

NetWorker 7.3.2 For Linux Installation Guide - Linuxig - 7.3.2

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

NetWorker 7.3.2 For Linux Installation Guide - Linuxig - 7.3.2

Загружено:

Авторское право:

Доступные форматы

EMC® NetWorker™

ii EMC NetWorker for Linux, Release 7.3.2, Installation Guide

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

Chapter 2 Updating from a Previous Release

Chapter 3 Linux for Intel x86 Installation

Chapter 4 Linux for Itanium Processor Installation

Chapter 5 EMC AutoStart Installation

iv EMC NetWorker for Linux, Release 7.3.2, Installation Guide

Chapter 6 Licensing and Enabling the Software

Appendix A Sample stinit.def File

Appendix B stinit(8) Man Page

vi EMC NetWorker for Linux, Release 7.3.2, Installation Guide

◆ NetWorker, Release 7.3.2, Administration Guide

Conventions used in this guide

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

viii EMC NetWorker for Linux, Release 7.3.2, Installation Guide

Where to get help

2. Click the Documentation link.

x EMC NetWorker for Linux, Release 7.3.2, Installation Guide

About the NetWorker product

NetWorker storage node

1-2 EMC NetWorker for Linux, Release 7.3.2, Installation Guide

NetWorker Management Console

NetWorker License Manager

About the NetWorker product 1-3

1-4 EMC NetWorker for Linux, Release 7.3.2, Installation Guide

Updating from a Previous Release 2-1

Updating from a previous release

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

Task 2: Update the NetWorker software

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

4. Install the new release of the NetWorker software.

Note: Do not start the NetWorker daemons.

5. Apply any required NetWorker software patches.

Updating from a previous release 2-3

2-4 EMC NetWorker for Linux, Release 7.3.2, Installation Guide

Linux for Intel x86 Installation 3-1

Software installation roadmap

3-2 EMC NetWorker for Linux, Release 7.3.2, Installation Guide

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

Client software requirements

Installation requirements 3-3

Client backup and recovery guidelines

Storage node software requirements

Server software requirements

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.EL 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

3-4 EMC NetWorker for Linux, Release 7.3.2, Installation Guide

Table 3-2 Hardware requirements for NetWorker server

Recommended RAM 128 MB

Disk storage for software 120 MB

Directories and pathnames

Table 3-3 Default locations and space requirements

NetWorker Management Console program /usr/bin 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 2 MB