Documente Academic
Documente Profesional
Documente Cultură
NetWorker
Release 7.2
Solaris Version
Installation Guide
Copyright 1990-2005 by EMC Corporation. All rights reserved. This software (including documentation) is subject to the terms and
conditions set forth in the end user license agreement or other applicable agreement, and you may use this software only if you accept all
the terms and conditions of the license agreement. This software comprises proprietary and confidential information of EMC.
Unauthorized use, disclosure, and distribution are strictly prohibited. Use, duplication, or disclosure of the software and documentation
by the U.S. Government are subject to restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software
clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software - Restricted Rights at 48 CFR 52.227-19,
as applicable. Manufacturer is LEGATO Software, a division of EMC, 2350 West El Camino Real, Mountain View, CA 94040.
LEGATO NetWorker, Release 7.2, Solaris Version, Installation Guide
January 11, 2005
e6-1751-01
LEGATO and the LEGATO logo are registered trademarks, and LEGATO NetWorker, NetWorker, AAM, Co-StandbyServer, RepliStor,
SnapShotServer, QuikStartz, AlphaStor, ClientPak, Xtender, XtenderSolutions, DiskXtender, ApplicationXtender, ArchiveXtender,
EmailXtender, and EmailXaminer are trademarks or registered trademarks of LEGATO Software, a division of EMC. This is a
nonexhaustive list of LEGATO trademarks, and other trademarks may be the property of their respective owners.
The following may be trademarks or registered trademarks of the companies identified next to them, and may be used in this document
for identification purposes only.
Acrobat, Adobe / Adobe Systems, Inc.
Apple, Macintosh / Apple Computer, Inc.
Caldera Systems, SCO, SCO OpenServer, UnixWare / Caldera, Inc.
TELEform / Cardiff
Check Point, FireWall-1 / Check Point Software Technologies, Ltd.
Unicenter / Computer Associates International, Inc.
Access Logix, Celerra, Centera, CLARiiON, EMC, EMC2, MirrorView, Navisphere, SnapView, SRDF, Symmetrix, Symmetrix DMX,
TimeFinder / EMC Corporation
Fujitsu / Fujitsu, Ltd.
Hewlett-Packard, HP, HP-UX, HP Tru64, HP TruCluster, OpenVMS, ProLiant / Hewlett-Packard Company
AIX, DB2, DB2 Universal Database, Domino, DYNIX, DYNIXptx, IBM, Informix, Lotus, Lotus Notes, OS/2, PTX, ptx/ADMIN, Raid Plus,
ServeRAID, Sequent, Symmetry, Tivoli, / IBM Corporation
InstallShield / InstallShield Software Corporation
Intel, Itanium / Intel Corporation
Linux / Linus Torvalds
Active Directory, Microsoft, MS-DOS, Outlook, SQL Server, Windows, Windows NT / Microsoft Corporation
Netscape, Netscape Navigator / Netscape Communications Corporation
Data ONTAP, NetApp, NetCache, Network Appliance, SnapMirror, SnapRestore / Network Appliance, Inc.
IntraNetWare, NetWare, Novell / Novell, Inc.
Oracle, Oracle8i, Oracle9i / Oracle Corporation
NetFORCE / Procom Technology, Inc.
DLTtape / Quantum Corporation
Red Hat / Red Hat, Inc.
R/3, SAP / SAP AG
IRIX, OpenVault, SGI / Silicon Graphics, Inc.
SPARC / SPARC International, Inc.a
ACSLS, REELbackup, StorageTek / Storage Technology Corporation
Solaris, Solstice Backup, Sun, SunOS, Sun StorEdge, Ultra / Sun Microsystems, Inc.
SuSE / SuSE, Inc.
Sybase / Sybase, Inc.
Turbolinux / Turbolinux, Inc.
Unicode / Unicode, Inc.
VERITAS, VERITAS File System/ VERITAS Software Corporation
WumpusWare / WumpusWare, LLC
UNIX / X/Open Company Ltdb
Notes:
a. Products bearing SPARC trademarks are based on an architecture developed by Sun Microsystems, Inc.
b. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd.
All other brand or product names may be trademarks or registered trademarks of their respective owners.
LEGATO Software
A Division of EMC Corporation
End-User License Agreement
THIS PRODUCT CONTAINS CERTAIN COMPUTER PROGRAMS AND OTHER PROPRIETARY MATERIAL, THE USE OF WHICH IS SUBJECT TO THIS
END-USER LICENSE AGREEMENT (THE "EULA"). DO NOT PROCEED WITH THE INSTALLATION OF THIS PRODUCT UNTIL YOU (LATER DEFINED
AS LICENSEE) HAVE READ THIS EULA AND AGREE TO BE BOUND BY AND BECOME A PARTY TO THIS EULA. BY PROCEEDING WITH THE
INSTALLATION OF THIS PRODUCT (OR AUTHORIZING ANY OTHER PERSON TO DO SO), YOU AND YOUR COMPANY ACCEPT THIS EULA AND
YOU REPRESENT THAT YOU ARE AUTHORIZED TO DO SO. IF YOU ARE ACCESSING THE PRODUCT ELECTRONICALLY INDICATE YOUR
ACCEPTANCE OF THESE TERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THE EULA. IF YOU DO NOT AGREE TO THE TERMS OF
THIS EULA, YOU MAY RETURN THIS PRODUCT, ALL MEDIA AND DOCUMENTATION, AND PROOF OF PAYMENT, TO THE PLACE YOU OBTAINED
THEM FOR A FULL REFUND WITHIN THIRTY (30) DAYS OF FIRST ACQUIRING THIS PRODUCT OR, IF THE PRODUCT IS ACCESSED
ELECTRONICALLY, SELECT THE "DECLINE" BUTTON AT THE END OF THIS EULA AND RETURN PROOF OF PAYMENT IN ACCORDANCE WITH
THE ABOVE REFERENCED RETURN/REFUND PROCESS. WRITTEN APPROVAL IS NOT A PREREQUISITE TO THE VALIDITY OR ENFORCEABILITY
OF THIS EULA AND NO SOLICITATION OF ANY SUCH WRITTEN APPROVAL BY OR ON BEHALF OF LEGATO SHALL BE CONSTRUED AS AN
INFERENCE TO THE CONTRARY. IF YOU HAVE ORDERED THIS PRODUCT, LEGATO'S ACCEPTANCE IS EXPRESSLY CONDITIONAL ON YOUR
ASSENT TO THESE TERMS TO THE EXCLUSION OF ALL OTHER TERMS; IF THESE TERMS ARE CONSIDERED AN OFFER BY LEGATO, ACCEPTANCE
IS EXPRESSLY LIMITED TO THESE TERMS.
1. DEFINITIONS
1.1 Authorization Code: means the unique code provided to Licensee by
LEGATO for permanent activation of the Software. The Authorization Code
is provided to Licensee once the Enabler Code is registered with LEGATO.
The Authorization Code may be tied to a unique machine ID code supplied
by Licensee.
1.2 Documentation: Documentation: means the user reference materials on
any media, provided by LEGATO for use with the Software.
1.3 Enabler Code: means the code provided by LEGATO for activation of the
Software.
1.4 Licensee: means the person or entity acquiring this License or for whom
this License was acquired.
1.5 Software: means the object code copy of the software program provided
to You in association with this EULA, together with the associated original
media and all accompanying Documentation, and together with all Updates
that may be provided by LEGATO to You from time to time.
2. OWNERSHIP AND ADMINISTRATION OF SOFTWARE
2.1 Ownership and Title. As between the parties, LEGATO, and its licensors,
own and shall retain all right, title, and interest in and to: (i) the Software
including all intellectual property rights embodied therein; (ii) all of the
service marks, trademarks, trade names, or any other designations associated
with the Software; and (iii) all copyrights, patent rights, trade secret rights,
and other proprietary rights relating to the Software.
2.2 Software Activation. LEGATO employs Enabler Codes and
Authorization Codes that enable the use of the Software. The Software is
shipped in a Media Kit which consists of object code software on CD-ROM
and an Enabler Code for initial activation of the Software or the Software and
Enabler Code may be delivered electronically. Once LEGATO receives
confirmation from Licensee that the Software is installed with the correct
Enabler Code, and is provided with the host ID information, LEGATO will
provide the Authorization Code to Licensee. LEGATO administers the
generation and distribution of Enabler and Authorization Codes, which
administration may be modified by LEGATO from time to time.
2.3 Administration of Software. LEGATO may include on the media with
the Software additional computer programs which are not currently licensed
for use by Licensee and to which the Enabler Code or Authorization code will
not permit access. Inclusion of such additional computer programs in no way
implies a license from LEGATO and access or use of such programs is strictly
prohibited unless Licensee procures the right to use any such program and
the applicable Enabler Code is provided thereto.
3. LICENSE GRANT
3.1 Grant. LEGATO grants to Licensee a non-exclusive, nontransferable,
non-sublicensable, perpetual (unless terminated in accordance with the
provisions of this EULA), license (the License) to (i) use the Software
installed in accordance with the Documentation and only on the licensed
computer(s) solely for its own internal operations; and (ii) move the Software
temporarily in case of computer system malfunction. The Software may be
licensed: (a) on a per copy or per seat basis, on a physical or virtual machine,
(b) based upon the number of mailboxes or the number of non-concurrent
users for which it may be used, or (c) based upon data volumes it supports.
The License granted under this EULA does not constitute a sale of the
Software or any portion or copy of it. Licensee may not use the Software on
more than one computer system unless otherwise specifically authorized by
an explicit Software product, or additional licenses for additional computers
are purchased. Rights not expressly granted are reserved by LEGATO.
3.2 Copies. Licensee may make copies of the Software provided that any such
copy is: (i) created as an essential step in utilization of the Software as
licensed and is used in no other manner; or (ii) used for archival purposes.
All trademark and copyright notices must be reproduced and included on
such copies. Licensee may not make any other copies of the Software.
3.3 Restrictions on use. Licensee shall not, and shall not aid, abet, or permit
any third party to: (i) decompile, disassemble, or otherwise reverse engineer
or attempt to reconstruct or discover any source code or underlying ideas or
algorithms of the Software by any means whatsoever; (ii) remove any
identification, copyright, or other notices from the Software; (iii) provide,
lease, lend, use for timesharing or service bureau purposes; (iv) create a
derivative work of any part of the Software; or (v) develop methods to enable
unauthorized parties to use the Software. If EC law is applicable, the
restrictions in Section 3.3 (i) are limited so that they prohibit such activity only
to the maximum extent such activity may be prohibited without violating the
EC Directive on the legal protection of computer programs. Notwithstanding
the foregoing, prior to decompiling, disassembling, or otherwise reverse
engineering any of the Software, Licensee shall request LEGATO in writing,
to provide Licensee with such information or assistance and Licensee shall
refrain from decompiling, disassembling, or otherwise reverse engineering
any of the Software unless LEGATO cannot or has not complied with such
request in a commercially reasonable amount of time.
3.4 Purchase Orders. Nothing contained in any purchase order,
acknowledgment, or invoice shall in any way modify the terms or add any
additional terms or conditions to this EULA.
3.5 Updates. This section applies if the Software acquired is an update to the
original Software (the Update). An Update does not constitute a legally
licensed copy of the Software unless purchased as an Update to a previously
licensed version of the same Software. The Update may only be used in
accordance with the provisions of this EULA. The Update, together with the
original Software, constitutes one (1) legally licensed copy of the Software.
3.6 Evaluation License. This Section applies if the Software is being used for
an initial thirty (30) day evaluation period. The license is valid only for a
period of thirty (30) days from the delivery of the Software, and is designed
to allow Licensee the right to evaluate the Software during such period. In
the event that Licensee desires to continue to license the Software, Licensee
must purchase a license to the Software. Upon such purchase, Licensee will
be provided with an Enabler Code in accordance with Section 2.2 above. In
the event Licensee determines not to purchase a license for the Software at the
end of such thirty (30) day evaluation period, then Licensees rights under
this EULA shall terminate automatically and Licensee shall promptly return
to LEGATO or destroy all copies of the Software and so certify to LEGATO.
3.7 General Public License ("GPL"). The Software may include one or more
components which are derived from software subject to a General Public
License. Any such components are licensed exclusively under the applicable
GPL and not under this EULA.
4. MAINTENANCE AND SUPPORT
4.1 LEGATO has no obligation to provide support, maintenance, upgrades,
modifications, or new releases under this EULA. LEGATO may provide such
services under separate EULA.
5. LIMITED WARRANTY
5.1 Media and Documentation. LEGATO warrants that if the media or
documentation are damaged or physically defective at the time of delivery of
the first copy of the Software to Licensee and if defective or damaged product
is returned to LEGATO (postage prepaid) within thirty (30) days thereafter,
then LEGATO will provide Licensee with replacements at no cost.
9. MISCELLANEOUS
9.1 Governing Law. This EULA shall be governed by the laws of the
Commonwealth of Massachusetts, without regard to the principles of conflict
of laws or the United Nations Convention on Contracts for the International
Sale of Goods.
9.2 Government Restricted Rights. Any Software which is acquired directly
or indirectly for or on behalf of the United States of America, its agencies
and/or instrumentalities ("U.S. Government"), is provided with Restricted
Rights. Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical
Data and Computer Software clause at DFARS 252.227-7013 or
subparagraphs (c)(1) and (2) of the Commercial Computer Software Restricted Rights at 48 CFR 52.227-19, as applicable. Manufacturer is
LEGATO Software, a division of EMC Corporation, 2350 W. El Camino Real,
Mountain View, CA 94040. The Software is a commercial software product,
licensed on the open market at market prices, and was developed entirely at
private expense and without the use of any government funds.
9.3 Export and Import Controls. Regardless of any disclosure made by
Licensee to LEGATO of an ultimate destination of the Products, Licensee may
not directly or indirectly export or transfer any portion of the Software, or any
system containing a portion of the Software, to anyone outside the United
States (including further export if Licensee took delivery outside the U.S.)
without first complying with any export or import controls that may be
imposed on the Software by the U.S. Government or any country or
organization of nations within whose jurisdiction Licensee operates or does
business. Licensee shall at all times strictly comply with all such laws,
regulations, and orders, and agrees to commit no act which, directly or
indirectly, would violate any such law, regulation or order.
9.4 Assignment. This EULA may not be assigned or transferred by Licensee
without the prior written consent of LEGATO, which shall not be
unreasonably withheld. LEGATO may assign or otherwise transfer any or all
of its rights and obligations under this EULA upon notice to Licensee.
9.5 Sole Remedy and Allocation of Risk. Licensee's sole and exclusive
remedies are set forth in this EULA. This EULA defines a mutually
agreed-upon allocation of risk, and the License price reflects such allocation
of risk.
9.6 Equitable Relief. The parties agree that a breach of this EULA adversely
affecting LEGATO's intellectual property rights in the Software may cause
irreparable injury to LEGATO for which monetary damages may not be an
adequate remedy and LEGATO shall be entitled to equitable relief in addition
to any remedies it may have hereunder or at law.
9.7 No Waiver. Failure by either party to enforce any provision of this EULA
will not be deemed a waiver of future enforcement of that or any other
provision, nor will any single or partial exercise of any right or power
hereunder preclude further exercise of any other right hereunder.
9.8 Severability. If for any reason a court of competent jurisdiction finds any
provision of this EULA, or portion thereof, to be unenforceable, that
provision of the EULA will be enforced to the maximum extent permissible
so as to effect the intent of the parties, and the remainder of this EULA will
continue in full force and effect.
10. ENTIRE EULA
10.1 This EULA sets forth the entire understanding and EULA between the
parties and may be amended only in a writing signed by authorized
representatives of both parties. No vendor, distributor, reseller, dealer,
retailer, sales person, or other person is authorized by LEGATO to modify
this EULA or to make any warranty, representation, or promise which is
different than, or in addition to, the warranties, representations, or promises
made in this EULA. No pre-printed purchase order terms shall in any way
modify, replace or supersede the terms of this EULA.
Contents
Preface..................................................................................................................... 10.
Audience....................................................................................................................................... 10.
Product Documentation ................................................................................................................ 10.
Conventions.................................................................................................................................. 11.
Information and Services .............................................................................................................. 12.
General Information ............................................................................................................... 12.
Technical Support .................................................................................................................. 12.
Licensing and Registration..................................................................................................... 13.
Customer Feedback ..................................................................................................................... 13.
Contents
Contents
Contents
Contents
Preface
This guide provides instructions on how to install the LEGATO NetWorker software.
After installing the NetWorker software, refer to the LEGATO NetWorker, Release 7.2,
UNIX and Linux Version, Administrators Guide and the programs Online Help for
detailed instructions on how to configure, administer, and use the NetWorker
software.
Post-release information is contained in the Release Supplement for this product. This
document is available on the LEGATO web site at www.legato.com. Refer to the web site
periodically to view the latest Release Supplement.
Audience
The information in this guide is intended for system administrators who are
responsible for installing software and maintaining the servers and clients on a
network. Operators who monitor the daily backups may also find this manual useful.
Product Documentation
For a complete list of documentation related to this product, see "Related
Documentation" on page 16. Most of the documents are Adobe Acrobat PDFs, and can
be viewed by downloading and installing the Adobe Acrobat Reader. The Reader is
available in the /viewers/acroread directory on the LEGATO Documentation Suite
CD-ROM, or directly from Adobe. To install and use the Reader on the preferred
platform, refer to the instructions in the CD-ROMs /viewers/acroread/readme.txt file or
at the Adobe web site.
10
Preface
Conventions
This document uses the following typographic conventions and symbols to make
information easier to access and understand.
Convention
Indicates
Example
boldface
italic in text
Pathnames, filenames,
computer names, new terms
defined in the Glossary or
within the chapter, or
emphasized words
italic in command
line
nwadmin -s server_name
fixed-width
fixed-width,
boldface
nsr_shutdown -a
Menu_Name>
Command
Important:
11
Preface
General Information
The LEGATO web site provides most of the information that customers might need,
including technical bulletins and binary patches from its FTP site. For specific sales or
training needs, e-mail or call LEGATO.
Service or Resource
Technical
Bulletins
Binary
Patches
Company
and Product
Information
Training
www.legato.com
Yes
Yes
Yes
Yes
ftp.legato.com
(log in as anonymous)
Yes
Yes
LEGATO Sales
(650) 210-7000 (option 1)
sales@LEGATO.com
LEGATO Education Services
(650) 842-9357
training@LEGATO.com
Yes
Yes
Technical Support
The LEGATO web site provides contact information, software patches, technical
documentation, and information about available support programs.
Note: LEGATO Software technical support and update subscription services apply
only to (i) LEGATO price-listed software that LEGATO supplies to its customers; and
(ii) customers that have entered into an authorized LEGATO technical support
agreement.
12
Preface
Contact
Telephone number
Fax number
(650) 745-1477a
+31 23 554 8808b
licensing@LEGATO.coma
licensingemea@LEGATO.comb
Customer Feedback
LEGATO welcomes comments and suggestions about software features, the
installation procedure, and its documentation.
13
Chapter 1: Introduction
NetWorker client
NetWorker storage node
NetWorker server
LEGATO License Manager
14
Chapter 1: Introduction
NetWorker Client
The NetWorker client software provides recover and on-demand backup functionality,
and it communicates with the NetWorker server. The NetWorker client software is
installed on all computers that are required to be backed up to the NetWorker server.
NetWorker clients may not have to be of the same operating system as the NetWorker
server. However, to back up clients of other operating systems, the NetWorker server
must have a ClientPak enabler for that type of client. For example, in order for the
NetWorker server for Solaris to back up NetWorker clients on another operating
system, a separate ClientPak enabler must be purchased and entered for that operating
system.
Control over which clients use the storage nodes devices for backups
License management
Management of the client file indexes that track each clients data
Management of the media database that tracks the data contained on each
volume
NetWorker storage nodes and the NetWorker server can use different operating
systems. For example, a NetWorker storage node can be used on another operating
system with a NetWorker server in a Solaris operating environment. However, the
storage nodes enabler on the server must be of the same edition (either Network
Edition or Power Edition) as the base enabler for the NetWorker server.
NetWorker Server
The NetWorker server software provides control and scheduling for NetWorker
operations. On the NetWorker server:
Enter the enabler licenses for the NetWorker server and all the functions the
NetWorker server controls, such as autochanger modules, additional client
connections, and LEGATO NetWorker ClientPak licenses.
Define the clients, devices, and media that the NetWorker server controls.
Define the schedules for backups and other operations.
Monitor the results of backups and other operations.
Manage the client file indexes that track each clients data.
Manage the media database that tracks the data contained on each volume.
15
Chapter 1: 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
LEGATO Compatibility Guides on the LEGATOweb site at www.legato.com.
Note: The term autochanger refers to a variety of backup devices: autoloader, carousel,
datawheel, jukebox, library, and near-line storage.
Use a nonrewinding device 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 BSD semantics requirement. If a
file device is used, enter it as a directory path (the same as for other device types) rather
than as just a filename.
Enabler Codes
Enabler codes (licenses), which activate the functionality of NetWorker software and
other LEGATO software, are sold separately. For more information, see
"Chapter 8: Evaluating and Licensing NetWorker Software" on page 94.
Related Documentation
For further information about LEGATO NetWorker software for UNIX, refer to the
following related documentation:
16
This chapter explains how to update from a previous release of LEGATO NetWorker
software. It includes the following sections:
"Introduction" on page 17
"Updating from a Previous Release" on page 17
Introduction
When updating to the NetWorker release 7.2 from a release earlier than NetWorker 6.0,
the client file indexes and media database must be converted to a new format.
Important: This is a one-way conversion. Once the client file indexes and the media
database are updated to the current NetWorker release, these objects cannot be
reverted for use by a previous release of the NetWorker software.
Note: Converting the NetWorker indexes from NetWorker 5.x to NetWorker 7.2
requires enough free disk space to match the largest client file index being converted.
This space is used during the conversion process and will be released when completed.
Following conversion, the media database should be approximately twice its original
size. The client file indexes will be 20% to 40% smaller. These storage requirement
changes are permanent.
17
18
The client file index conversion can be enhanced by running multiple instances of
the nsrck program concurrently. This process converts multiple client file indexes
in parallel. To convert multiple client file indexes in parallel, perform one of the
following:
Specify the client file index to convert, as follows:
nsrck client_name
Enter the nsrck command without a client name. This initiates the conversion
of the next client in the list.
Each instance of nsrck occupies a portion of the servers processing, memory,
and space-swapping capability. Balance the speed of index conversion against
other NetWorker server needs. Monitor system performance using a
diagnostic tool to determine the optimum number of nsrck instances to
launch.
7. Once the media database is converted, run scheduled backups. These backups,
however, are not browsable until the associated client is converted.
19
This chapter explains how to install NetWorker software on Solaris. It includes the
following sections:
4. Enable and register all NetWorker products. For more information, see
"Chapter 8: Evaluating and Licensing NetWorker Software" on page 94.
20
Installation Requirements
The system requirements differ for each of the installation types:
Important: Before installing NetWorker software, make sure that the operating system
is up-to-date with the most recent patches.
Note: NetWorker software does not support locales (defined by the operating system)
or code sets that remap characters having special meaning for filesystems. Depending
on the filesystem, these special characters may include the slash (/), the backslash (\),
the colon (:), or the period(.). De_DE.646 is an example of one unsupported locale. For
detailed information, refer to the NetWorker Administrators Guide, UNIX and Linux
Version.
Client Software
The NetWorker client software package temporarily requires 35 MB of free space on
the client computer.
The client software can be installed either on a remote network file system-mounted
directory or a local drive.
Storage Node
To install the NetWorker storage node software, the following requirements must be
met:
Server Software
This section describes NetWorker server installation requirements:
21
System Requirements
To install NetWorker software on a Solaris server, make sure that:
The system meets the space requirements listed in Table 1 on page 23.
There is a directory on the server large enough for the NetWorker client and
server indexes and the media database (usually /nsr). The installation script
checks for space and suggests one or more locations for the indexes and media
database.
The system pathname of at least one storage device is used by the NetWorker
server to back up and recover files.
If a tape device is being used to back up data, use a valid pathname for that device.
For example:
/dev/rmt/0cbn
Note: The tape device must be nonrewinding.
Install Acrobat Reader software is installed to read the documentation PDFs.
Acrobat Reader requires a directory with enough space to install the software.
Installation Guidelines
On the NetWorker server, install all of the NetWorker software in the following order:
1. Client
2. Device drivers
3. Storage node
4. Server
It is recommended that the NetWorker software packages all be installed on the server
during the same installation session.
Note: If installing additional NetWorker software packages (storage node, server) to a
NetWorker client that has processes running (for example, the nsrexecd process) an
RPC error is reported. Before each software package is installed, the NetWorker
software requires all NetWorker processes be shutdown. The RPC error is generated
because the nsr_shutdown process attempts to stop NetWorker server processes when
in fact no NetWorker server is running. This error message can be ignored and the
installation process completes successfully.
During the pkgadd process, ensure no NetWorker processes are currently running and
do not start the NetWorker daemons until the final package is being installed.
22
Table 1 on page 23 lists the default locations on the server that the installation script
uses, and the disk space required.
Table 1. Default Locations and Space Requirements
Software/Documentation Files
NetWorker Server
Default Location
Space Needed
13 MB
/usr/sbin
90 MB
/nsr
varies
/usr/kernel/drv
/usr/sbin
/usr/lib/nsr
40 MB
/usr/man
1 MB
/opt/Acrobat3/bin
8 MB
Documentation PDFs
optional
varies
23
Local CD Drive
To access the LEGATO NetWorker software from a local CD-ROM:
1. Log in as root to the system where the NetWorker software is being installed.
2. Mount the CD-ROM drive.
3. Locate the appropriate directory on the CD-ROM.
4. Set the PATH environment variable for user root to contain the directory where the
NetWorker executables reside. For information, see Table 1 on page 23.
Remote CD Drive
To access the LEGATO NetWorker software from a remote CD-ROM:
1. On the remote system:
a. Insert the CD-ROM into the remote systems drive.
b. Mount the CD-ROM drive on the remote system.
c. Make the CD-ROM drive exportable through the network filesystem (NFS).
2. On the local system:
a. Log in as root on the system where the NetWorker software is being installed.
b. Create a mount point.
c. Mount the remote CD-ROM filesystem. For example:
mount remote_host:/cdrom/mount_dir
Set the PATH environment variable for user root to contain the directory where the
NetWorker executables reside. For information, see Table 1 on page 23.
24
"Client" on page 25
"Storage Node" on page 26
"Server" on page 27
Client
To install NetWorker software on the computer that is designated as the NetWorker
client:
1. Enter one of the following pkgadd commands:
pkgadd -d /cdrom/cdrom1/solaris_32
pkgadd -d /cdrom/cdrom1/solaris_64
Important: Do not press the [Enter] key for the default response All. Accepting the
default installs the server, the device driver packages, and the Fibre Channel devices.
2. Enter the appropriate option number to install the client package (LGTOclnt). The
client package temporarily requires 35 MB of free space on the client computer.
25
Important: If installing the device configuration wizard package (LGTOwizd) you must
first install the client configuration wizard package (LGTOwiz). However, the client
configuration wizard installation is not dependant on the device configuration
package and can be installed separately.
4. (Optional) Enter the appropriate option number to install the man pages
(LGTOman).
5. Start the NetWorker daemons.
For more information on how to start the NetWorker daemons, see "Task 4: Start the
NetWorker Daemons" on page 31.
Storage Node
To install NetWorker software on the computer that is designated as the NetWorker
storage node and for which you have purchased an enabler code:
1. Enter one of the following pkgadd commands:
pkgadd -d /cdrom/cdrom1/solaris_32
pkgadd -d /cdrom/cdrom1/solaris_64
Important: Start the NetWorker daemons only after the last NetWorker package is
installed.
2. Enter the appropriate options to install the following packages. Software packages
on the storage node must be installed in the following order:
26
Important: The LGTOwiz package can be installed at any point after the LGTOclnt
package. If installing the device configuration wizard package (LGTOwizd) you must
first install the Client configuration wizard package (LGTOwiz). However, the client
configuration wizard installation is not dependant on the device configuration
package and can be installed separately. For more information on the NetWorker
configuration wizard, refer to the NetWorker Release Supplement, UNIX and Linux
Version.
Server
To install NetWorker software on the computer that is designated as the NetWorker
server:
1. Keep a copy of the current configuration. The NetWorker software installation
script modifies the /etc/rpc and /etc/syslog.conf files during the installation process.
Enter the following commands:
cp /etc/rpc /etc/rpc.old
cp /etc/syslog.conf /etc/syslog.conf.old
2. Enter one of the following pkgadd commands:
pkgadd -d /cdrom/cdrom1/solaris_32
pkgadd -d /cdrom/cdrom1/solaris_64
3. Press [Enter] to install all of the packages on the server. LEGATO recommends that
all of the NetWorker software be installed on the server at the same time.
Important: Start the NetWorker daemons only after the last NetWorker package is
installed.
27
To install only selected software packages on the server, install them in the
following order:
LGTOclnt (client software package)
LGTOdrvr (device drivers package)
LGTOnode (storage node software package)
LGTOserv (server software package)
LGTOman (optional man pages)
LGTOlicm (optional LEGATO License Manager software package)
LGTOwiz (optional client configuration wizard package)
LGTOwizd (optional device configuration wizard package)
Important: The LGTOwiz package can be installed at any point after the LGTOclnt
package. If installing the device configuration wizard package (LGTOwizd) you must
first install the client configuration wizard package (LGTOwiz). However, the Client
configuration wizard installation is not dependant on the device configuration wizard
package and can be installed separately. For more information on the NetWorker
configuration wizard, refer to the NetWorker Release Supplement, UNIX and Linux
Version.
For more information on the LEGATO License Manager software, refer to the
LEGATO License Manager Installation and Administrator's Guide, 2nd Edition.
4. Start the NetWorker daemons.
For more information on how to start the NetWorker daemons, see "Task 4: Start
the NetWorker Daemons" on page 31.
5. Verify that the NetWorker daemons shown in Table 2 on page 28 are running. Enter
the following command:
ps -ef | grep ns
6. If the output does not list nsrd and nsrexecd as current processes, run the
following command to start the NetWorker daemons on the NetWorker server:
/etc/init.d/networker start
Table 2 on page 28 lists the NetWorker daemons for each installation package.
Table 2. NetWorker Daemons
NetWorker Installation Packages
NetWorker Daemons
NetWorker server
NetWorker client
nsrexecd
nsrexecd, nsrmmd
28
The following NetWorker packages must always be installed in the default location:
For a listing of the default locations and size requirements, see Table 1 on page 23.
29
6. When the following prompt appears in the script, enter the same base directory for
all the relocated packages:
Enter path to package base directory (default: /usr) [?,q]
/my_path
Using /my_path as the package base directory.
Important: To successfully install the LGTOdrvr and LGTOman packages, provide the
root directory (/) when prompted for a directory in which to install the packages.
7. When all the applicable packages are added and the prompt appears, press [q] to
exit.
8. Copy the /tmp/default.tmp file to the following location. For example:
cp /tmp/default.tmp /var/sadm/install/admin/default
If pkgrm is used to remove the packages at a later date, specify the base directory.
Important: If the /nsr/res/servers file is empty or does not exist, any NetWorker server
is authorized to:
Access and back up the client
Perform a directed recovery to the client
3. If necessary, remove the -s option from the nsrexecd command that is invoked by
the boot-time startup file. Running nsrexecd with the -s option supersedes the
/nsr/res/servers file:
a. Check the NetWorker boot-time startup file to see whether nsrexecd is being
run with the -s option. The boot-time startup file for the Solaris environment
is /etc/init.d/networker.
b. If the -s option exists in the boot-time startup file, remove all occurrences of
-s server_name in the startup file.
30
NetWorker Daemons
NetWorker server
NetWorker client
nsrexecd
nsrexecd, nsrmmd
Note: The NetWorker daemon nsrmmd is only present if one or more devices are
enabled.
31
32
Software Dependencies
The NetWorker software packages depend on each other. Uninstall them in the
following order:
LGTOwizd
LGTOwiz
LGTOserv
LGTOnode
LGTOdrvr
LGTOlicm
LGTOclnt
33
Important: Do not choose the default option All to remove the NetWorker software
packages. Choosing this option removes all the software packages (not just NetWorker
software) that were installed on the computer using the pkgadd utility.
34
35
This chapter explains how to install NetWorker software in a Sun Cluster version 3.0
or 3.1, environment. It includes the following sections:
36
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
Cluster Terminology
For consistency and clarity, this section defines the following terms:
Node A physical machine that is a member in the cluster.
Failover node A cluster node to which the NetWorker virtual server can fail over.
Virtual client A NetWorker client that is associated with a highly available or scalable
service in a cluster.
Cluster client A NetWorker cluster client is either a physical client or a virtual client.
A physical client resource backs up data belonging to a physical node within a cluster.
A virtual client resource backs up data belonging to a highly available or scalable
service within a cluster.
Virtual server A NetWorker server that is configured as a highly available application
within a cluster.
Stand-alone NetWorker server A NetWorker server that is not highly available.
Cluster-aware NetWorker server A NetWorker server that can recognize cluster clients.
About Clustering
Clustering means that two or more nodes are connected and appear to network users
as a single, highly available system. A highly available system allows the application
services to continue despite most hardware or software failures. Each cluster node has
its own IP address. Each cluster node might also have private (local) resources or disks
that are available only to that computer. In addition to the nodes, a cluster can have one
or more virtual services, each with its own IP address. A virtual service can have zero or
more shared disks.
Figure 1 on page 38 displays a general cluster configuration consisting of two or more
nodes and at least one NetWorker server. In this illustration:
37
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
Node 2
clus_phys2
Private NetWork
clus_log1
Local Disk
If Node1fails,
clus_log1 fails
over to Node2
Local Disk
Public NetWork
In this example, the NetWorker server can fail over between Node 1 and
Node 2; however, the NetWorker server only runs on one node at a time.
The NetWorker server inherits the virtual servers IP address. Although NetWorker
software is installed on all the physical nodes within the cluster, the server software is
active on only one node at a time. If a hardware or software breakdown occurs on the
node on which the NetWorker server is running, the NetWorker server moves to
another node in the cluster.
The NetWorker client software runs on all the physical nodes within the cluster,
regardless of whether or not the NetWorker server resource group is running. This
allows the backup of the physical client to proceed, as long as the node is running. Only
one instance of the client software (nsrexecd) runs on each physical node within the
cluster. The NetWorker client software is designed to recognize more than one client
(physical client plus virtual client) that might be associated with a single physical node.
38
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
If a NetWorker client does not have cluster-client support, it backs up all data that
belongs to the virtual servers and physical nodes into the same index representing
the physical node. It does not recognize the difference between virtual and
physical clients.
For more information, refer to the LEGATO Compatibility Guides on the LEGATO web
site.
Installation Requirements
The following sections discuss the software and hardware required to install and
configure the NetWorker server or client software within a Sun Cluster environment:
For the most up-to-date information regarding software and hardware requirements,
refer to the LEGATO Compatibility Guides on the LEGATO web site at www.legato.com.
Software Requirements
To install a NetWorker virtual server, make sure that the following software is installed
on each node in the cluster:
Hardware Requirements
To install the NetWorker software, make sure that the following hardware
requirements are met for server installation only:
Multihosted disks that are used as a mount point for global filesystems to contain
the shared /nsr area.
A device with local affinity for the local bootstrap backup that is connected to all
the nodes within the cluster.
Configuration Options
For information on how to configure the following, refer to the NetWorker
Adminstrators Guide:
39
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
Node 2
clus_phys2
Private NetWork
clus_log1
Local Disk
If Node1fails,
clus_log1 fails
over to Node2
Local Disk
Public NetWork
Example
/global/nw
/usr/sbin/networker.cluster
/nsr/res/hostids
The location of the NetWorker server global /nsr directory on the shared
storage.
The location of the NetWorker client local /nsr directories.
40
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
41
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
"Task 9: Register Licenses for the Highly Available NetWorker Server" on page 51
"Task 10: Authorize the Software" on page 53
To install the NetWorker software on nodes that will be running the NetWorker
resource group:
1. Access the NetWorker software from the distribution media. For detailed
installation instructions, see "Chapter 3: Installing the NetWorker Software" on
page 20.
2. Keep a copy of the current configuration. The NetWorker software installation
script modifies the /etc/rpc and /etc/syslog.conf files during the installation process.
Enter the following commands:
cp /etc/rpc /etc/rpc.old
cp /etc/syslog.conf /etc/syslog.conf.old
3. Enter the pkgadd command as follows:
pkgadd -d .
4. Press [Enter] to install all of the packages on the server. LEGATO recommends
installing all the software on the server at the same time.
Important: Start the NetWorker daemons only after the last NetWorker package is
installed.
42
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
Enter Yes to configure the server software. This also installs the client
software by default.
Enter No to configure only the client software.
Do you wish to add now the site-specific values for:
NSR_SHARED_DISK_DIR and NSR_SERVICE_ID
Yes or No [Yes]?
43
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
Logical hostname
Globally mounted filesystem for the /nsr area
LGTO.serv resource
LGTO.clnt resource
HAStoragePlus (optional)
To create an instance of the NetWorker server resource group, perform the following
steps on one node in the cluster:
1. Create a resource group:
scrgadm -a -g networker
2. Add the logical host resource:
scrgadm -a -L -g networker -l clus_vir1
3. (Optional), create an instance of the SUNW.HAStoragePlus resource type:
a. Determine if the HAStoragePlus resource type is registered within the cluster:
scrgadm -p | egrep Type
b. If required, register the HAStoragePlus resource type within the cluster:
scrgadm -a -t SUNW.HAStoragePlus
c. Create the SUNW.HAStoragePlus resource:
scrgadm -a -g networker -j hastorageplus -t SUNW.HAStoragePlus \
-x FilesystemMountPoints=/global/clus_vir1/nw,/global/clus_vir1/space \
-x AffinityOn=True
Note: For more information on the SUNW.HAStoragePlus resource and how to set
up locally mounted global systems, refer to the Sun Cluster 3.0 or 3.1
documentation.
4. Create an instance of the LGTO.clnt resource type:
scrgadm -a -j client -t LGTO.clnt -g networker \
-x clientname=clus_vir1 \
-x owned_paths=/global/clus_vir1/nw,/global/clus_vir1/space
If the logical host resource name is different than the hostname it specifies, use the
following command to:
a. Set the client name to the virtual hostname.
b. Set the optional network_resource property to the logical host resource name.
For example:
scrgadm -a -j client -t LGTO.clnt -g networker \
-x clientname=virtual_hostname -x network_resource=clus_vir1 \
-x owned_paths=/global/clus_vir1/nw,/global/clus_vir1/space
44
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
45
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
Important: If the /nsr/res/servers file is empty or does not exist, any NetWorker server
is authorized to:
Access and back up the client
Perform a directed recovery to the client
46
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
b. Edit or create the servers file in the globally mounted /nsr area. For example,
/global/nw/res/servers:
Add the set of NetWorker servers, one per line, to be granted access to
this client.
Add an entry for the NetWorker logical hostname first. Then add entries
for each physical host that can run the NetWorker resource group.
For example:
clus_vir1
clus_phys1
clus_phys2
2. On each node in the cluster:
a. Shut down the NetWorker processes and verify that all NetWorker daemons
have stopped:
nsr_shutdown
ps -ef | grep nsr
b. Check the NetWorker boot-time startup file to see whether nsrexecd is being
run with the -s option. If the -s option exists, remove all occurrences of
-s servername in the file.
c. Edit or create the /nsr.NetWorker.local/res/servers file:
Add the set of NetWorker servers, one per line, that require access to this
client.
Add an entry for the NetWorker logical hostname first. Then add entries
for each physical host that can run the NetWorker resource group.
For example:
clus_vir1
clus_phys1
clus_phys2
d. Restart the NetWorker processes:
/etc/init.d/networker start
3. On one node in the cluster, start the NetWorker service using the cluster
management software, as follows:
scswitch -Z -g networker
4. If required, grant access to the NetWorker virtual server on clients outside of the
cluster:
On each client that is outside of the cluster:
a. Shut down the NetWorker processes:
nsr_shutdown
b. Verify that all NetWorker daemons have stopped:
ps -ef |grep nsr
47
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
/nsr->/nsr.NetWorker.local
/nsr.NetWorker.local->/var/nsr
48
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
Important: 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.
49
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
50
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
This SUNW.informix database server can access data on a global filesystem under
/global/informix/config and /global/informix/db.
To add a NetWorker virtual client to the existing resource group informix_rg, enter the
following command:
scrgadm -a -j informix_clntrs -g informix_rg -t LGTO.clnt \
-x clientname=informix_lhrs \
-x owned_paths=/global/informix/config,/global/informix/db
This Apache web server accesses data on a global filesystem under /global/web/config
and /global/web/data.
To add a NetWorker virtual client to the existing resource group apache_rg, enter the
following command:
scrgadm -a -j apache_clntrs -g apache_rg -t LGTO.clnt \
-x clientname=apache_sars \
-x owned_paths=/global/web/config,/global/web/data
51
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
52
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
Important: Make sure that the NetWorker client software is installed on each node in
the cluster.
To install the NetWorker software on the computer that is designated as the NetWorker
client:
1. Access the NetWorker software from the distribution media.
For detailed installation instructions, see "Chapter 3: Installing the NetWorker
Software" on page 20.
2. Enter the pkgadd command:
pkgadd -d .
Important: Do not press the [Enter] key for the default response All. Accepting the
default installs the server and the device driver packages.
3. Enter the appropriate option number to install the client package (LGTOclnt). The
package temporarily requires 70 MB of free space on the client computer.
53
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
4. (Optional) Enter the appropriate option number to install the man pages,
(LGTOman).
5. Start the NetWorker daemons:
/etc/init.d/networker start
6. When all the applicable packages have been added, and the prompt appears, press
[q] to exit.
54
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
This SUNW.informix database server can access data on a global filesystem under
/global/informix/config and /global/informix/db.
To add a NetWorker virtual client to the existing resource group informix_rg, enter the
following command:
scrgadm -a -j informix_clntrs -g informix_rg -t LGTO.clnt \
-x clientname=informix_lhrs \
-x owned_paths=/global/informix/config,/global/informix/db
This Apache web server accesses data on a global filesystem under /global/web/config
and /global/web/data.
To add a NetWorker virtual client to the existing resource group apache_rg:
scrgadm -a -j apache_clntrs -g apache_rg -t LGTO.clnt \
-x clientname=apache_sars \
-x owned_paths=/global/web/config,/global/web/data
55
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
Important: If the /nsr/res/servers file is empty or does not exist, any NetWorker server
is authorized to:
Access and back up the client
Perform a directed recovery to the client
To define the list of trusted NetWorker servers, perform the following steps on each
node in the cluster:
1. Shut down the NetWorker processes and verify that all NetWorker daemons have
stopped:
nsr_shutdown
ps -ef |grep nsr
2. Edit or create the /nsr/res/servers file and add the set of NetWorker servers, one per
line, that require access to this client.
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 -s servername in
the file.
4. Restart the NetWorker daemons:
/etc/init.d/networker start
56
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
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.
e. Define the remaining attributes in the Clients dialog box and click Apply.
3. Make each virtual client within the cluster a client of the NetWorker server.
For each virtual client in the cluster:
a. In the NetWorker Administrator program, select Client Setup from the Clients
menu.
b. In the Clients dialog box, if these steps are being performed after updating the
NetWorker server, click on the client name in the Clients list. Otherwise, click
Create and enter the name of the virtual client for the Name attribute.
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.
e. Define the remaining attributes in the Clients dialog box and click Apply.
4. Schedule backups using the NetWorker application. For detailed instructions, refer
to the NetWorker Administrators Guide.
57
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
For more information on backing up raw partitions, refer to the rawasm command as
described in the uasm(1m) man page.
58
Chapter 4: Installing NetWorker Software in a Sun Cluster Version 3.0 or 3.1 Environment
1 root
59
3. Enable and register all of the NetWorker products. For more information, see
"Chapter 8: Evaluating and Licensing NetWorker Software" on page 94.
60
Installation Requirements
The following sections discuss the software and hardware required to install and
configure the NetWorker server or client software within a LEGATO Automated
Availability Manager cluster environment:
For the most up-to-date information regarding software and hardware requirements,
refer to the LEGATO Compatibility Guides on the LEGATO web site.
Software Requirements
To install NetWorker cluster server, make sure that the following software is installed
on each node in the cluster:
Note: Make sure that to the most recent cluster patch for the operating system is
installed.
Hardware Requirements
To install the NetWorker software, make sure that the following hardware
requirements are met for server installation only:
Dedicated shared disk used as the NetWorker storage disk (for the /nsr directory)
connected to all the nodes within the cluster.
Device with local affinity for the local bootstrap backup connected to all the nodes
within the cluster.
Configuration Options
Refer to the LEGATO NetWorker Administrators Guide for information on how to
configure:
61
Node 2
clus_phys2
Private NetWork
clus_log1
Local Disk
If Node1fails,
clus_log1 fails
over to Node2
Local Disk
NetWorker
Logical Host
Public NetWork
Example
/dev/dsk/c1t3d0s0
62
Example
/usr/sbin/nw_ux.lc
/nsr/res/hostids
/usr/sbin/nw_ux.lc
Client
Driver
Storage node
Server
For detailed instructions, see "Installing the NetWorker Software" on page 23.
63
Follow the instructions listed in the comments at the beginning of the nw_ux.lc.imp
file to customize the following NetWorker default values based on the cluster
configuration:
Virtual hosts IP address: 192.168.1.10
Physical hostnames: clus_phys1, clus_phys2
Shared disk file system: /nsr_shared_mnt_pt
Device name: /dev/dsk/c1t3d0s0
For a listing of the sample values provided, see Table 5 on page 62.
64
Important: If the /nsr/res/servers file is empty or does not exist, any NetWorker server
is authorized to:
access and backup the client
perform a directed recover to the client
65
3. If required, grant access to each NetWorker client that is outside of the cluster:
a. Shut down the NetWorker processes and verify that all NetWorker daemons
have stopped.
b. Edit or create the /nsr/res/servers file:
Add the set of NetWorker servers, one per line, that require access to this
client.
For each virtual NetWorker server, add an entry for each physical host
and the virtual NetWorker server. For example:
clus_vir1
clus_phys1
clus_phys2
/nsr->/nsr.NetWorker.local
/nsr.NetWorker.local->/var/nsr
66
Important: 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.
67
Important: Make sure the NetWorker client software is installed on every node to be
backed up in the cluster.
68
Important: If the /nsr/res/servers file is empty or does not exist, any NetWorker server
is authorized to:
access and backup the client
perform a directed recover to the client
69
To define the list of trusted NetWorker servers, perform the following steps on each
node in the cluster:
1. Shut down the NetWorker processes and verify that all NetWorker daemons have
stopped.
2. Edit or create the /nsr/res/servers file:
a. Add the set of NetWorker servers, one per line, that require access to this
client.
b. For each virtual NetWorker server, add an entry for each physical host and
the virtual NetWorker server. For example:
clus_vir1
clus_phys1
clus_phys2
3. Check the NetWorker boot-time startup file to see whether nsrexecd is being run
with the -s option. If the -s option exists, remove all occurrences of -s servername in
the file.
70
Important: If the /nsr/res/servers file is empty or does not exist, any NetWorker server
is authorized to:
access and backup the client
perform a directed recover to the client
71
Important: Misconfiguration of the cluster resources might cause scheduled save sets
to be dropped from the backup. For more information, see LEGATO NetWorker
Administrators Guide.
To override scheduled save rules (not path ownership rules), run the following
command on each node in the cluster:
touch networker_bin_dir/pathownerignore
This command allows any path to be backed up for a client, whether it is owned
by the virtual client or physical node. For detailed information, see LEGATO
NetWorker Administrators Guide.
If pathownerignore was used, check that the NetWorker scheduled save uses the
correct client index. If it uses the wrong index, save sets can be forced to go to a specific
index:
1. In the NetWorker Administrator program, select Clients>Clients Setup.
2. For the Backup command attribute, enter the name of a backup script that contains
save -c client_name.
For detailed information about the Backup command attribute, see LEGATO NetWorker
Administrators Guide.
72
3. Make sure that the $FT_DIR and the $FT_DOMAIN environment variables have
been set.
4. Run the /usr/sbin/networker.cluster -r command. For example:
/usr/sbin/networker.cluster -r
5. Remove the subsets for the following packages with the pkgrm command in the
following order. For example:
pkgrm LGTOman LGTOserv LGTOnode LGTOdrvr LGTOlicm LGTOclnt
73
74
This chapter explains how to install NetWorker software in a VERITAS Cluster Server
3.5 environment. It includes the following sections
VERITAS Cluster Server 3.5 enables you to run and administer applications as highly
available service groups. For detailed information about VERITAS Cluster Server 3.5,
refer to the Solaris version of the VERITAS Cluster Server Installation Guide and the
VERITAS Cluster Server User's Guide.
75
Cluster Terminology
For consistency and clarity, this section defines the following terms:
Node A physical machine that is a member in the cluster.
Failover node A cluster node to which a highly available application can fail over.
Virtual client A NetWorker client that is associated with a highly available or scalable
service in a cluster.
Cluster client A NetWorker cluster client is either a physical client or a virtual client.
A physical client resource backs up data belonging to a physical node within a cluster.
A virtual client resource backs up data belonging to a highly available or scalable
service within a cluster.
Virtual server A server that is configured as a highly available application within a
cluster.
Stand-alone NetWorker server A NetWorker server that is not highly available.
Cluster-aware NetWorker server A NetWorker server that can recognize cluster clients.
About Clustering
Clustering means that two or more nodes are connected and appear to network users
as a single, highly available system. A highly available system allows the application
services to continue despite most hardware or software failures. Each cluster node has
its own IP address. Each cluster node might also have private (local) resources or disks
that are available only to that computer. In addition to the nodes, a cluster can have one
or more virtual services, each with its own IP address. A virtual service can have zero or
more shared disks.
Figure 4 on page 77 displays a general cluster configuration consisting of two or more
nodes and at least one virtual server. In this illustration:
76
Node 2
clus_phys2
Private NetWork
clus_log1
Local Disk
If Node1fails,
clus_log1 fails
over to Node2
Local Disk
Virtual Server
Public NetWork
In this example, the virtual server, clus_log1, can fail over between Node 1 and Node 2;
however, the server only runs on one node at a time.
The NetWorker client software runs on all the physical nodes within the cluster. This
allows the backup of the physical client to proceed, as long as the node is running. Only
one instance of the client software (nsrexecd) runs on each physical node within the
cluster. The NetWorker client software is designed to recognize more than one client
(physical client plus virtual client) that might be associated with a single physical node.
For more information, refer to the LEGATO Compatibility Guides on the LEGATO web
site at www.legato.com.
77
Software Requirements
Make sure that the following software is installed on each node in the cluster:
For the most up-to-date information regarding software requirements, refer to the
LEGATO Compatibility Guides on the LEGATO web site.
Important: Make sure that the NetWorker client software is installed on each node in
the cluster.
Important: Ensure that the Solaris operating environment and the VERITAS Cluster
Server 3.5 software are already installed and configured on all cluster nodes. If the
VERITAS Cluster Server installation and configuration directories are different from
the default directories, set the environment variables VCS_HOME (the default
directory is /opt/VRTSvcs) and VCS_CONF (the default directory is /etc/VRTSvcs) prior
to installing the NetWorker client.
Also, ensure that the PATH environment variable includes /usr/sbin and
$VCS_HOME/bin (the default directory is /opt/VRTSvcs/bin) directories.
78
Important: Do not press the [Enter] key for the default response All. Accepting the All
response installs the server and the device driver packages.
3. Enter the appropriate option number to install the client package (LGTOclnt). The
package temporarily requires 70 MB of free space on the client computer.
4. (Optional) Enter the appropriate option number to install the man pages,
(LGTOman).
5. Start the NetWorker daemons:
/etc/init.d/networker start
6. When all the applicable packages have been added, and the prompt appears, press
[q] to exit.
79
Task 3: Register the NWClient Resource Type and Create Resource Type
Instances
You might need to configure an instance of the NetWorker Client resource type
(NWClient) for virtual clients that own data on shared devices. Virtual clients in the
VERITAS Cluster Server are IP type resources.
Important: Depending on the VERITAS Cluster service group configuration, this task
might not be required. Create an instance of NWClient resource type in VERITAS
Cluster service groups that:
Contain raw devices or logical volumes to back up.
Contain more than one IP type resource.
Are parallel with one or more IP type resources.
Creating an instance of NWClient resource type is optional if the following conditions
exist:
The failover VERITAS Cluster service group has only one IP type resource.
The owned filesystems on the shared devices are instances of the mount type
resource contained in the same service group.
Check the VERITAS Cluster Server configuration to determine which, if any, service
groups require one or more NWClient resources. If no such groups require NWClient
resources, proceed to "Task 4: Define the List of Trusted NetWorker Servers" on
page 82.
80
Definition
IPAddress
string, scalar
Owned_paths
string, vector
81
Important: If the /nsr/res/servers file is empty or does not exist, any NetWorker server
is authorized to:
access and backup the client
perform a directed recover to the client
82
To define the list of trusted NetWorker servers, perform the following steps on each
node in the cluster:
1. Shut down the NetWorker processes and verify that all NetWorker daemons have
stopped:
nsr_shutdown
ps -ef |grep nsr
2. Edit or create the /nsr/res/servers file and add the set of NetWorker servers, one per
line, that require access to this client.
3. Check the NetWorker boot-time startup file to see whether nsrexecd is being run
with the -s option. If the -s option exists, remove all occurrences of -s servername in
the file.
4. Restart the NetWorker daemons:
/etc/init.d/networker start
83
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.
e. Define the remaining attributes in the Clients dialog box and click Apply.
4. Schedule backups using the NetWorker application. For detailed instructions, refer
to the NetWorker Administrators Guide.
84
1 root
85
About Autochangers
Note: The term autochanger refers to a variety of backup devices: library, autoloader,
carousel, datawheel, jukebox, and near-line storage.
For more information about autochanger support by the NetWorker software, refer to
the LEGATO Compatibility Guides on the LEGATO web site.
Notes:
Release 7.0 or later of the NetWorker software includes the ability to recognize
shared drives, known as dynamic drive sharing (DDS). For more information
about DDS, refer to the NetWorker Administrator's Guide.
To install and configure NetWorker support for Network Data Management
Protocol (NDMP), refer to the NetWorker Administrator's Guide.
Important: For all tape devices used with NetWorker software, ensure that the block
size mode specified in the operating system is set to variable. Otherwise, data recovery
may fail. For information about setting the tape device block size mode through the
operating system, refer to the operating system documentation.
86
If you elect not to install the requisite software automatically, and you do not
manually select drivers to install with the storage node, the storage node
installation will fail.
If you install only the client package, then the storage node package, and thus the
ASC utility, is not installed.
The ASC utility translates vendor-specific error messages for the following vendors:
ADIC
ATL
BHTi
Benchmark
Exabyte
Fujitsu
HP
IBM
Overland
Plasmon
Qualstar
Quantum
Seagate
STK
Tandberg
87
88
89
13. If drive pathname information was missing at step 10, you are prompted to enter
it for each drive in question in one of the following forms:
/dev/rmt/1cbn --for local path or
host:device-path --for remote node or
host:drive-letter:directory path --for Windows disk file
Drive x, element y
Drive path ? somepath
where:
x and y are supplied by jbconfig.
somepath is supplied by you.
You can use the output from the sjisn command, if the autochanger supports it, to
verify the serial number of the first drive in the autochanger, or to identify it if the
pathname is not automatically supplied. The first drive in the autochanger is the
first drive listed under the library in the sjisn output.
For example, the first drive listed in the sample output from sjisn in step 4 has the
serial number 6811004028:
Drive at element address 82:
Serial Number: 6811004028
Use the output from the inquire command to identify the drive pathname of the
serial number obtained from sjisn.
For example, the drive with serial number 6811004028 in the sample output from
inquire is /dev/rmt/1cbn.
After you have filled in the pathname as prompted, you may be asked to select a
drive type number from a list of about 50 types.
The process in step 13 repeats until all unaccounted drives receive pathname
information.
14. Configuration is complete.
When the configuration is complete, the following message appears:
Jukebox has been added successfully.
When you use the jbconfig program to configure an autochanger, a new resource is
created with the name you specified.
To view the:
For more information on the available jbconfig command options, refer to the
jbconfig(1m) man page. For an example, see "The jbconfig Command Output" on
page 91.
For more information on configuring an autochanger, refer to the NetWorker
Administrators Guide.
LEGATO NetWorker, Release 7.2, Solaris Version
Installation Guide
90
To obtain the exact SCSI address for the -c parameter, use output from the
inquire command, or the response displayed by the jbconfig command script
when the autochanger was configured:
Installing 'Exabyte' jukebox - scsidev@4.2.0.
For additional information on the command options available for the
jbexercise command, refer to the jbexercise(1m) man page.
91
These are all the drives that this jukebox has reported.
Please
92
b is the bus ID
t is the target ID
l is the logical unit number (LUN) ID
93
Power Edition
Network Edition
Workgroup Edition
Business Edition
These four editions enable varying degrees of functionality. Add-on enablers allow a
broader scope of features. For more information about the editions and different
functionality, see "NetWorker Licenses" on page 99.
94
Note: If the Business, Network, or Workgroup edition is already installed and enabled
on a computer, and you want to evaluate Power Edition, LEGATO recommends using
a different computer as a temporary NetWorker server for evaluation purposes.
By the end of the evaluation period, you must purchase, enter, and authorize the
corresponding license enablers to continue using features you have evaluated. For
instructions, see "The Licensing Process" on page 96. For more information about the
different NetWorker editions and features, see "NetWorker Licenses" on page 99.
95
Important: 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.
96
Important: 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.
97
By Fax or E-mail
To register the software and obtain an authorization code by fax or e-mail:
1. Log in as root or as NetWorker administrator on the NetWorker server.
2. Start the NetWorker Administrator program:
nwadmin &
3. Complete your contact information:
a. From the Server menu, select Server Setup.
b. Complete the contact name, company, address, phone, and e-mail
information requested, and click Apply.
4. Print the registration information sheet.
a. From the Server menu, select Registration.
b. From the View menu, select Tabular.
c. From the File menu, select Print.
5. Send your contact information to LEGATO Licensing. You can either:
Fax the printed registration information sheet.
E-mail the registration information.
For contact information, see "Licensing and Registration" on page 13.
An authorization code that permanently enables the updated NetWorker software will
be sent to you.
98
NetWorker Licenses
There are four different levels, or editions of base enablers:
NetWorker Workgroup Edition enables you to back up the server and up to seven
clients. NetWorker Workgroup Edition does not include support for additional
clients or optional software features, such as NetWorker Archive. If you decide at
a later date to purchase a higher level of NetWorker software, all of the data
backed up by NetWorker Workgroup Edition is recoverable by any level of
NetWorker software you purchase.
NetWorker Business Edition is the same as the Workgroup Edition, except that it
includes a license to use an autochanger (1-26 slots) as part of its base enabler,
allows backing up a two-node cluster client, and allows NDMP connections.
NetWorker Network Edition enables you to back up the server and as many client
workstations as the number of client connections purchased. You can upgrade
this edition to include support for additional clients and autochangers, as well as
optional software features.
NetWorker Power Edition is a server software product that has been specially
tuned to protect and provide backup for environments that support Very Large
Database (VLDB) or large filesystem applications (in the terabyte range). You can
also upgrade NetWorker Power Edition to include support for cluster servers and
clients.
Each of these editions permits you to use the software for a specified number of clients
and devices. These four editions also enable different degrees of parallelism and
support for different add-on modules, including extra client connections, devices, or
features. For more information on NetWorker licenses, refer to the NetWorker
Administrators Guide.
99
Multiplatform Licensing
The client connections that come with a NetWorker server can be used for only that
server platform; a ClientPak license allows the NetWorker server to back up clients of
different platforms. For example, the client connections accompanying a NetWorker
server for Windows can be used only for Windows client computers; similarly, the
client connections that come with 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 the NetWorker Server for Solaris. The ClientPak for UNIX supports all UNIX
platforms; therefore, 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, so a
ClientPak for Linux is necessary to back up Linux clients by either UNIX or Windows
servers.
Update Enablers
To update existing NetWorker software to a major release (one that introduces
important new features), an update enabler is necessary. Update enablers are required
for any major NetWorker software upgrade from release 4.0 and later, including
NetWorker release 7.2. To use the LEGATO 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.
100
to 5.0 to 5.5
to 5.5.x to 5.6
to
to 5.7 to 6.x to 7.0 to 7.1 7.2
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
yes
(UNIX (NT
only) only)
yes
yes
yes
yes
yes
yes
(UNIX (NT
only) only)
yes
yes
yes
yes
yes
yes
yes
yes
5.7
yes
yes
yes
yes
6.0
no
yes
yes
yes
yes
yes
yes
Any release
prior to 5.0
5.0
5.5
5.5.x
5.6
NA*
6.x
Additional Licenses
This section describes a few of the additional licenses required to operate some of the
NetWorker features. For a complete list, contact a LEGATO sales representative.
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.
101
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. To place a NetWorker server
in a cluster, you must have Power Edition. For more information on licensing
computers in a cluster, refer to the NetWorker Administrators Guide.
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.
102
Index
A
autochanger
configuring
testing 91
clients
server
66
66
88
B
backups
clusters
requirements
38, 77
C
client
about 15
daemon 28
file indexes 19
installing 25
requirements
system 21
uninstalling 35
clients
cluster 37, 76
cluster script
Legato Automated Availability Manager 73
clusters
clients 37, 76
configuration 37, 76
defined 37, 76
nodes 37, 76
requirements 38, 77
server 37, 76
commands
gunzip 25
inquire 88
jbexercise 91
mminfo 18
nsr_shutdown 30, 34
nwadmin 32
configuring
autochanger 88
cluster
Legato Automated Availability Manager 62
Legato Automated Availability Manager, external
client 71
Legato Automated Availability Manager, options
61
virtual server
Legato Automated Availability Manager
client software 69
daemons
client 28
list of 28
nsindexd 28
nsr_shutdown 18
nsrck 19
nsrd 28
nsrexecd 28, 30
nsrmmd 28
nsrmmdbd 28
server 28
shut down 34
starting 31
storage node 28
verifying 31
directory default locations
23
E
enabler codes
16
G
gunzip command
25
H
hardware requirements
Legato Automated Availability Manager
61
I
information requirements
Legato Automated Availability Manager 62
inquire command 88
installing
guidelines, server 22
Legato Automated Availability Manager 60
cluster client software 68
virtual server 63
NetWorker 20
requirements
Legato Automated Availability Manager 61
software 23
client 25
103
Index
J-S
server 27
storage node 26
Sun Cluster 36, 75
to default locations 25
to nondefault locations 29
verifying 31
J
jbexercise command
91
L
Legato Automated Availability Manager
configuration 62
configuration options 61
installing 60
requirements
hardware 61
installing 61
software 6061
system information 62
tracking scheduled saves 72
virtual client, ownership 71
virtual server
cluster script 73
configuring 66
client software 69
clients 66
external client 71
defining as highly available 63
granting access 65
installing 63
installing client software 68
registering 68
servers
configuring clients 70
trusted servers 69
Legato License Manager
about 16
uninstalling software 35
licensing
levels 99
69
M
man pages
uninstalling 35
mminfo command 18
N
NetWorker
about 14
client 15
O
ownership, Legato Automated Availability Manager
virtual client 71
R
requirements
Legato Automated Availability Manager
hardware 61
installing 61
software 60
system information 62
S
scripts
restart script 18
server
about 15
daemons 28
installing 27
installing guidelines 22
system requirements 22
uninstalling software 34
servers
clusters 37, 76
software
accessing from
Legato web site 24
local CD 24
remote CD 24
ensuring startup 31
uninstalling 33
client 35
device driver 34
Legato License Manager
NetWorker 72
server 34
storage node 34
storage node
about 15
35
104
Index
T-V
daemons 28
installing software 26
uninstalling software 34
Sun Cluster
installing 36, 75
system requirements
client 21
server 22
T
test backup 32
testing
autochanger 91
installation 32
tracking scheduled saves 72
trusted servers
Legato Automated Availability Manager
69
U
uninstalling
man pages 35
software 33
all packages 33
client 35
Legato License Manager 35
NetWorker 72
server 34
storage node 34
updating from a previous release 17
automatic conversion 17
V
verifying installation 3132
virtual client ownership 71
virtual server
Legato Automated Availability Manager
cluster script 73
configuring 66
client software 69
clients 66
external client 71
configuring clients 70
defining as highly available 63
defining trusted servers 69
granting access 65
installing 63
installing client software 68
registering 68
virtual servers. See clusters
105