Legatoinstall 7.2

January 11, 2005
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.
5.2 Limited Software Warranty. Subject to the conditions and limitations of

liability stated herein, LEGATO warrants for a period of thirty (30) days from
the delivery of the first copy of the Software to Licensee that the Software, as
delivered, will materially conform to LEGATOs then current published
Documentation for the Software. This warranty covers only problems
reported to LEGATO during the warranty period. For customers outside of
the United States, this Limited Software Warranty shall be construed to limit
the warranty to the minimum warranty required by law.
5.3 Remedies. The remedies available to Licensee hereunder for any such
Software which does not perform as set out herein shall be either repair or
replacement, or, if such remedy is not practicable in LEGATOs opinion,
refund of the license fees paid by Licensee upon a return of all copies of the
Software to LEGATO. In the event of a refund this EULA shall terminate
immediately without notice with respect to such Software.
6. WARRANTY DISCLAIMER
6.1 Warranty Disclaimer. EXCEPT FOR THE LIMITED WARRANTY
PROVIDED IN SECTION 5 ABOVE, ALL SOFTWARE IS PROVIDED "AS IS".
LEGATO AND ITS LICENSORS MAKE NO WARRANTIES WITH RESPECT
TO ANY SOFTWARE AND DISCLAIMS ALL STATUTORY OR IMPLIED
WARRANTIES, INCLUDING WITHOUT LIMITATION WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
ARISING FROM A COURSE OF DEALING OR USAGE OF TRADE AND
ANY WARRANTIES OF NONINFRINGEMENT. LEGATO DOES NOT
WARRANT THAT THE SOFTWARE WILL MEET ANY REQUIREMENTS
OR THAT THE OPERATION OF SOFTWARE WILL BE UNINTERRUPTED
OR ERROR FREE. ANY LIABILITY OF LEGATO WITH RESPECT TO THE
SOFTWARE OR THE PERFORMANCE THEREOF UNDER ANY
WARRANTY, NEGLIGENCE, STRICT LIABILITY OR OTHER THEORY
WILL BE LIMITED EXCLUSIVELY TO THE REMEDIES SPECIFIED IN
SECTION 5.3 ABOVE. Some jurisdictions do not allow the exclusion of
implied warranties or limitations on how long an implied warranty may last,
so the above limitations may not be applicable.
7. LIMITATION OF LIABILITY
7.1 Limitation of Liability. EXCEPT FOR BODILY INJURY, LEGATO (AND
ITS LICENSORS) WILL NOT BE LIABLE OR RESPONSIBLE WITH
RESPECT TO THE SUBJECT MATTER OF THIS EULA UNDER ANY
CONTRACT, NEGLIGENCE, STRICT LIABILITY, OR OTHER LEGAL OR
EQUITABLE THEORY FOR: (I) ANY INDIRECT, SPECIAL, INCIDENTAL
OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND
WHETHER OR NOT ADVISED IN ADVANCE OF THE POSSIBILITY OF
SUCH DAMAGES; OR (II) DAMAGES FOR LOST PROFITS OR LOST
DATA; OR (III) COST OF PROCUREMENT OF SUBSTITUTE GOODS,
TECHNOLOGY, SERVICES, OR RIGHTS; OR (IV) FOR AMOUNTS IN
EXCESS OF THOSE RECEIVED BY LEGATO FOR THE PARTICULAR
LEGATO SOFTWARE THAT CAUSED THE LIABILITY . Because some
jurisdictions do not allow the exclusion or limitation of incidental or
consequential damages, LEGATO's liability in such jurisdictions shall be
limited to the extent permitted by law.
8. TERM AND TERMINATION
8.1 Term. The term of this EULA is perpetual unless terminated in
accordance with its provisions.
8.2 Termination. LEGATO may terminate this EULA, without notice, upon
Licensee's breach of any of the provisions hereof.
8.3 Effect of Termination. Upon termination of this EULA, Licensee agrees
to cease all use of the Software and to return to LEGATO or destroy the
Software and all Documentation and related materials in Licensee's
possession, and so certify to LEGATO. Except for the License granted herein
and as expressly provided herein, the terms of this EULA shall survive
termination.
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.
Chapter 1: Introduction.......................................................................................... 14.

About the LEGATO NetWorker Product ....................................................................................... 14.
NetWorker Client.................................................................................................................... 15.
NetWorker Storage Node....................................................................................................... 15.
NetWorker Server .................................................................................................................. 15.
LEGATO License Manager .................................................................................................... 16.
Supported Devices ....................................................................................................................... 16.
Enabler Codes.............................................................................................................................. 16.
Related Documentation ................................................................................................................ 16.
Chapter 2: Updating from a Previous NetWorker Release ................................. 17.

Introduction................................................................................................................................... 17.
Updating from a Previous Release ............................................................................................... 17.
Task 1: Prepare to Update the NetWorker Software on the NetWorker Server..................... 18.
Task 2: Update the NetWorker Software ............................................................................... 18.
New Resource Database Replaces nsr.res and nsrjb.res Files ...................................... 19.
Task 3: Enable and Register the Software............................................................................. 19.
Chapter 3: Installing the NetWorker Software .................................................... 20.

Software Installation Roadmap..................................................................................................... 20.
Installation Requirements ............................................................................................................. 21.
Client Software....................................................................................................................... 21.
Storage Node ......................................................................................................................... 21.
LEGATO NetWorker, Release 7.2, Solaris Version

Installation Guide
Contents
Server Software ..................................................................................................................... 21.

System Requirements ..................................................................................................... 22.
Installation Guidelines...................................................................................................... 22.
Installing the NetWorker Software ................................................................................................ 23.
Task 1: Access the NetWorker Software ............................................................................... 23.
Local CD Drive................................................................................................................. 24.
Remote CD Drive............................................................................................................. 24.
LEGATO Web Site........................................................................................................... 24.
Task 2: Install the NetWorker Software.................................................................................. 25.
Installing to a Default Location......................................................................................... 25.
Client ......................................................................................................................... 25.
Storage Node ............................................................................................................ 26.
Server........................................................................................................................ 27.
Installing to a Nondefault Location................................................................................... 29.
Task 3: Change the NetWorker Servers with Access to a Client ........................................... 30.
Task 4: Start the NetWorker Daemons .................................................................................. 31.
Verifying the Installation ............................................................................................................... 31.
Ensuring the NetWorker Software Starts ............................................................................... 31.
How to Start the NetWorker Administrator Program........................................................ 32.
Performing a Test Backup...................................................................................................... 32.
Uninstalling the NetWorker Software............................................................................................ 33.
Software Dependencies ......................................................................................................... 33.
Uninstalling the Software ....................................................................................................... 34.
Chapter 4: Installing NetWorker Software in a

Sun Cluster Version 3.0 or 3.1 Environment........................................................ 36.
Cluster Concepts and Terminology .............................................................................................. 36.
Cluster Terminology ............................................................................................................... 37.
About Clustering..................................................................................................................... 37.
Cluster-Aware and Cluster-Unaware NetWorker Servers...................................................... 38.
Software Requirements.......................................................................................................... 39.
Hardware Requirements ........................................................................................................ 39.
Configuration Options ............................................................................................................ 39.
System Information Requirements for a Highly Available NetWorker Server ........................ 40.
Updating from a Previous Release of NetWorker Software ......................................................... 40.
Installing NetWorker Software in a Cluster ................................................................................... 41.

Installation Guide
Contents
Installing a NetWorker Virtual Server ..................................................................................... 41.

Task 1: Install the NetWorker Software ........................................................................... 42.
Task 2: Define the NetWorker Server as Highly Available .............................................. 43.
Task 3: Create an Instance of the NetWorker Server Resource Group .......................... 44.
Example: A Highly Available NetWorker Server .............................................................. 45.
Task 4: (Optional) Add a HAStoragePlus Resource to an Existing NetWorker Server
Resource Group .............................................................................................................. 46.
Task 5: Grant Access to the Highly Available NetWorker Server .................................... 46.
Task 6: Configure the NetWorker Server......................................................................... 48.
Task 7: Configure Clients under the NetWorker Server .................................................. 48.
Task 8: Create Instances of the NetWorker Client Resource Type ................................. 50.
Example: A Highly Available Informix Database Server .................................................. 51.
Example: A Scalable Apache Web Server ...................................................................... 51.
Task 9: Register Licenses for the Highly Available NetWorker Server............................ 51.
Task 10: Authorize the Software...................................................................................... 53.
Installing Only the NetWorker Client Software in a Cluster.................................................... 53.
Task 1: Install the NetWorker Cluster Client Software..................................................... 53.
Task 2: Configure NetWorker Client Software as Highly Available ................................. 54.
Task 3: Create Instances of the Client Resource Type ................................................... 54.
Example: A Highly Available Informix Database Server .................................................. 55.
Example: A Scalable Apache Web Server ...................................................................... 55.
Task 4: Define the List of Trusted NetWorker Servers .................................................... 56.
Task 5: Configure Clients under the NetWorker Server .................................................. 56.
Configuring an External Client to a Virtual Server ........................................................................ 57.
Defining Ownership of a Raw Partition for Virtual Clients ............................................................ 58.
Example: A Highly Available Web Server........................................................................ 58.
NetWorker Cluster Script .............................................................................................................. 59.
Chapter 5: Installing NetWorker Software in a LEGATO Automated

Availability Manager Environment........................................................................ 60.
Software Installation Roadmap..................................................................................................... 60.
Software Requirements.......................................................................................................... 61.
Hardware Requirements ........................................................................................................ 61.
Configuration Options ............................................................................................................ 61.
System Information Requirements......................................................................................... 62.
Installing a NetWorker Virtual Server ........................................................................................... 63.

Installation Guide
Contents
Task 1: Install the NetWorker Software in a Cluster .............................................................. 63.

Task 2: Define the NetWorker Server as a Highly Available Application ............................... 63.
Task 3: Grant Access to the NetWorker Virtual Server.......................................................... 65.
Task 4: Configure the NetWorker Server ............................................................................... 66.
Task 5: Configure Clients under the NetWorker Server......................................................... 66.
Task 6: Register NetWorker Licenses for Virtual Server Failover.......................................... 68.
Installing Only the NetWorker Client Software in a Cluster .......................................................... 68.
Task 1: Install the NetWorker Cluster Client Software ........................................................... 68.
Task 2: Configure NetWorker Client Software as a Highly Available Application .................. 69.
Task 3: Define the List of Trusted NetWorker Servers........................................................... 69.
Configuring an External Client to a Virtual Server ........................................................................ 71.
Defining Ownership of a Raw Partition for Virtual Clients ............................................................ 71.
Tracking Scheduled Saves ........................................................................................................... 72.
Chapter 6: Installing NetWorker Software in a VERITAS Cluster Server 3.5

Environment............................................................................................................ 75.
Cluster Concepts and Terminology .............................................................................................. 75.
Cluster Terminology ............................................................................................................... 76.
About Clustering..................................................................................................................... 76.
Cluster-Aware and Cluster-Unaware NetWorker Servers and Clients................................... 77.
Software Requirements ................................................................................................................ 78.
Installing Only the NetWorker Client Software in a Cluster .......................................................... 78.
Task 1: Install the NetWorker Cluster Client Software ........................................................... 78.
Task 2: Configure NetWorker Client Software as Highly Available........................................ 79.
Task 3: Register the NWClient Resource Type and Create Resource Type Instances......... 80.
About NWClient Resources ............................................................................................. 80.
Example: NWClient Resource Sample Configuration ............................................... 81.
Register Resource Type and Create Resource Instances .............................................. 81.
Task 4: Define the List of Trusted NetWorker Servers........................................................... 82.

Installation Guide
Contents
Chapter 7: Autochanger Installation and Configuration..................................... 86.

About Autochangers ..................................................................................................................... 86.
Supported Vendor-Specific ASC and ASCQ Codes..................................................................... 87.
Autochanger Configuration and Testing ....................................................................................... 87.
Task 1: Configure the Autochanger ....................................................................................... 88.
Task 2: Test the Autochanger ................................................................................................ 91.
The jbconfig Command Output..................................................................................................... 91.
Using the op Driver with Optical Devices ..................................................................................... 93.
How to Reset HP Optical Drives ............................................................................................ 93.
Chapter 8: Evaluating and Licensing NetWorker Software ................................ 94.

How NetWorker Software Is Licensed .......................................................................................... 94.
The Evaluation Process................................................................................................................ 95.
Evaluating a New Installation ................................................................................................. 95.
Evaluating Features on an Existing Installation ..................................................................... 95.
How to Enter a Temporary Enabler Code........................................................................ 96.
The Licensing Process ................................................................................................................. 96.
Task 1: Enter the License Enabler Code ............................................................................... 97.
Task 2: Obtain an Authorization Code ................................................................................... 97.
Using the LEGATO Web Site .......................................................................................... 98.
By Fax or E-mail .............................................................................................................. 98.
Task 3: Enter the Authorization Code .................................................................................... 98.
NetWorker Licenses ..................................................................................................................... 99.
Multiplatform Licensing ........................................................................................................ 100.
Example: Multiplatform Licensing Schemes .................................................................. 100.
Update Enablers .................................................................................................................. 100.
Required Update Enablers ............................................................................................ 101.
Additional Licenses..................................................................................................................... 101.
Client Connection Licenses ........................................................................................... 101.
Storage Nodes............................................................................................................... 101.
LEGATO NetWorker Application Modules..................................................................... 102.
Cluster Clients ............................................................................................................... 102.
NDMP Licensing ............................................................................................................ 102.
Index ...................................................................................................................... 103.

Installation Guide
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.

Installation Guide
10
Preface
Conventions
This document uses the following typographic conventions and symbols to make
information easier to access and understand.
Convention
Indicates
Example
boldface
Names of line commands,

daemons, options, programs,
or scripts
The nsradmin command starts the command

line version of the NetWorker Administrator
program.
italic in text
Pathnames, filenames,
computer names, new terms
defined in the Glossary or
within the chapter, or
emphasized words
Displayed messages are also written to

/nsr/logs/daemon.log.
italic in command
line
A variable that must be

provided in the command line
nwadmin -s server_name
fixed-width
Examples and information

displayed on the screen
media waiting: recover waiting for 8mm

5GB tape volume name
fixed-width,
boldface
Commands and options that

must be entered exactly as
shown
nsr_shutdown -a
Menu_Name>
Command
A path or an order to follow for Volume>Change Mode>Appendable

making selections in the user
interface
Important:
Information that must be read

and followed to ensure
successful backup and
recovery of data

Installation Guide
The specifications are created, one for each swap

file, in c:\pagefile.sys.
Important: Use the no_verify option with

extreme caution.
11
Preface
Information and Services

LEGATO offers a variety of methods (including e-mail, telephone, and fax support) to
obtain company, product, and technical information.
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.
Customers with an active support agreement have access to the LEGATO

integrated product knowledge base. Help with software issues is also available
through Technical Support.
Customers without an active support agreement can contact Support Sales and
Renewal to purchase annual software update subscriptions, or technical support
services for per-update/per-incident assistance.
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.

Installation Guide
12
Preface
Licensing and Registration

To license and register products, go to the licensing web site at www.LEGATO.com. To
change contact information, transfer licenses, or ask questions about licensing, contact
LEGATO by using one of the following methods.
Licensing and Registration
Contact
Telephone number
(650) 812 6000 (option 3, option 2)a

+31 23 554 8881b
Fax number
(650) 745-1477a
+31 23 554 8808b
E-mail
licensing@LEGATO.coma
licensingemea@LEGATO.comb
a. Contact information for the Americas, Asia, and the Pacific.

b. Contact information for Europe, the Middle East, and Africa.
Customer Feedback
LEGATO welcomes comments and suggestions about software features, the
installation procedure, and its documentation.
To comment on a particular guide, complete the Comments form at

www.LEGATO.com. Navigate to the documentation page and click the Comments
link beside the name of the guide. All comments are reviewed and acted upon,
usually within one business day.
To help improve our documentation in general, complete a brief survey at
www.LEGATO.com. Navigate to the documentation page and click the link to the
survey.
To provide other suggestions and comments, send e-mail to
feedback@LEGATO.com. Although LEGATO cannot respond personally to every
request, all comments and suggestions are considered during product design.

Installation Guide
13
Chapter 1: Introduction
This chapter provides background information on LEGATO NetWorker software and

supported devices. It includes the following sections:
"About the LEGATO NetWorker Product" on page 14

"Supported Devices" on page 16
"Enabler Codes" on page 16
"Related Documentation" on page 16
About the LEGATO NetWorker Product

The LEGATO 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 allow the backup in a
heterogeneous environment while giving the flexibility to design an efficient
manageable setup.
The NetWorker software is distributed in the following formats:
In a media kit of CD-ROMs that contain the software and electronic

documentation for several related LEGATO products
As a downloadable archive file from the LEGATO web site
The NetWorker product has these major components:
NetWorker client
NetWorker storage node
NetWorker server
LEGATO License Manager

Installation Guide
14
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.
NetWorker Storage Node

Data can be backed up directly to devices attached to either a NetWorker server or to
a NetWorker storage node. A storage node controls storage devices such as tape drives,
autochangers, and silos.
Storage nodes depend on the NetWorker server for the following functions:
Control over which clients use the storage nodes devices for backups
License management
Management of the client file indexes that track each clients data
Management of the media database that tracks the data contained on each
volume
NetWorker storage nodes and the NetWorker server can use different operating
systems. 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.

Installation Guide
15
LEGATO License Manager

The LEGATO License Manager provides a central place 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
License Manager is an option when installing the NetWorker software.
For more information about the LEGATO License Manager, refer to the LEGATO
License Manager Installation and Administrators Guide and the LEGATO License Manager
Release Supplement on the LEGATO web site at www.legato.com.
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:
NetWorker Release 7.2, UNIX and Linux Version, Administrators Guide

NetWorker Release 7.2, UNIX and Linux Version, Release Supplement
NetWorker Release 7.2, Multiplatform Version, Disaster Recovery Guide
NetWorker Command Reference Guide
NetWorker Software Compatibility Guide
UNIX man pages

Installation Guide
16
Chapter 2: Updating from a Previous NetWorker

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

The following sections explain how to complete the update process and convert the
indexes:
"Task 1: Prepare to Update the NetWorker Software on the NetWorker Server" on

page 18
"Task 2: Update the NetWorker Software" on page 18
"Task 3: Enable and Register the Software" on page 19
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.

Installation Guide
17
Chapter 2: Updating from a Previous NetWorker Release
Task 1: Prepare to Update the NetWorker Software on the NetWorker Server

To prepare to update the NetWorker software:
1. Determine whether all criteria to complete the index conversion is met. See
"Updating from a Previous Release" on page 17.
2. Back up all client file indexes and generate a bootstrap for the server.
If no current bootstrap and backup of all client file indexes exists, perform
scheduled backups on all clients before updating to the next NetWorker release.
For example, to save the bootstrap information, enter the following command:
savegrp -O group
Note: Make sure that all clients are included in the groups to be backed up.
3. Record the latest bootstrap save set ID and its associated volume label. To obtain
this information, use the following command:
mminfo -B
4. If the NetWorker software is not currently installed in the default location, record
the location of the client file indexes.
Task 2: Update the NetWorker Software

To update the NetWorker software on the NetWorker client, storage node and server:
1. Keep a copy of the current configuration.
2. Shut down the NetWorker software using the following command:
nsr_shutdown
3. Remove the earlier NetWorker release, but do not remove the client file indexes, the
resource files, and media database.
For more information, see "Uninstalling the NetWorker Software" on page 33.
4. Install the new release of the NetWorker software. For more information, see
"Installing the NetWorker Software" on page 23.
Important: 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.

Installation Guide
18
Chapter 2: Updating from a Previous NetWorker Release
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.
New Resource Database Replaces nsr.res and nsrjb.res Files

In NetWorker releases earlier than 7.0, all resource information was stored in *.res files.
To provide better performance and improved scalability, NetWorker release 7.2
replaces the following files with a new NetWorker resource database:
/nsr/res/nsr.res
/nsr/res/nsrjb.res
The configuration information these files contained now resides in the following
directory structure:
/nsr/res/nsrdb/00
.
.
.
/nsr/res/nsrdb/09
Within this directory structure, each resource is stored in a separate numbered file. As
new resources are created (for example, Client, Group, or Pool resources), new files are
added in these directories.
Because client resources are generally very small, the NetWorker client (nsrexecd)
continues to use the /nsr/res/nsrla.res file.
Task 3: Enable and Register the Software

To enable and register the NetWorker software, see "Chapter 8: Evaluating and
Licensing NetWorker Software" on page 94.

Installation Guide
19
Chapter 3: Installing the NetWorker Software
This chapter explains how to install NetWorker software on Solaris. It includes the
following sections:
"Software Installation Roadmap" on page 20

"Installation Requirements" on page 21
"Installing the NetWorker Software" on page 23
"Verifying the Installation" on page 31
"Uninstalling the NetWorker Software" on page 33
Software Installation Roadmap

Use the following roadmap when installing NetWorker software. Read the roadmap
and the referenced sections before installing the software:
1. Review the requirements section and note the default directory location and the
installation file space requirements. For more information, see "Installation
Requirements" on page 21.
2. Install the required NetWorker software. For more information, see ""Installing the
NetWorker Software" on page 23.
To update from an earlier release of NetWorker software, see "Chapter 2: Updating
from a Previous NetWorker Release" on page 17.
3. Install the device drivers for the NetWorker server and any storage nodes. For
more information, refer to the following sources:
"Chapter 7: Autochanger Installation and Configuration" on page 86

The autochanger and silo chapters in the NetWorker Administrators Guide,
UNIX and Linux Version
4. Enable and register all NetWorker products. For more information, see

Installation Guide
20
Installation Requirements
The system requirements differ for each of the installation types:
"Client Software" on page 21

"Storage Node" on page 21
"Server Software" on page 21
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:
Device driver (LGTOdrvr) and client software (LGTOclnt) must be installed.

At least one supported storage device must be attached and installed. The device
can either be a stand-alone device, autochanger, or silo tape library. For a list of
supported devices, refer to the LEGATO Compatibility Guides on the LEGATO
web site.
Server Software
This section describes NetWorker server installation requirements:
"System Requirements" on page 22

"Installation Guidelines" on page 22

Installation Guide
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.

Installation Guide
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
NetWorker Administrator program /usr/bin

files
13 MB
NetWorker daemon and utility

command files (if you install
LGTOlicm, add 1 MB)
/usr/sbin
90 MB
Online client file indexes; media

database
/nsr
varies
NetWorker device drivers (note

that 39 MB of drivers are now
installed in /usr/sbin)
/usr/kernel/drv
/usr/sbin
/usr/lib/nsr
40 MB
NetWorker man pages
/usr/man
1 MB
Adobe Acrobat Reader
/opt/Acrobat3/bin
8 MB
Documentation PDFs
optional
varies
Installing the NetWorker Software

The following sections explain how to access and install the NetWorker software:
"Task 1: Access the NetWorker Software" on page 23

"Task 2: Install the NetWorker Software" on page 25
"Task 3: Change the NetWorker Servers with Access to a Client" on page 30
"Task 4: Start the NetWorker Daemons" on page 31
Task 1: Access the NetWorker Software

Access the LEGATO NetWorker software:
"Local CD Drive" on page 24

"Remote CD Drive" on page 24
"LEGATO Web Site" on page 24
Important: The evaluation release of NetWorker software contains tarred and

compressed versions of the NetWorker software distribution files. Ensure that there is
adequate disk space to contain both the compressed download file (about 13 MB) and
the fully uncompressed files (about 50 MB).

Installation Guide
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.
LEGATO Web Site

To access NetWorker software from the LEGATO web site:
1. To request the NetWorker software:
a. Go to the LEGATO web site at www.legato.com.
b. Click the link for downloading software.
2. Complete and submit the Evaluation Download Request page located at
http://www.legato.com/resources/downloads/index.cfm.
When you have completed and submitted the Evaluation Download Request page,
you will receive an e-mail with the URL to download the NetWorker software.
3. Access the NetWorker software:
a. Log in as root on the computer where the NetWorker software is being
installed.
b. Create a temporary directory to download the file and change to that
directory.
4. Go to the LEGATO Software Evaluation Download page at www.legato.com/eval.
5. Download the NetWorker evaluation software to the /tmpdir directory.

Installation Guide
24
6. Uncompress the downloaded NetWorker software by using one of the following

platform-specific gunzip commands:
gunzip nw72_ncw10_solaris_32.tar.gz
gunzip nw72_ncw10_solaris_64.tar.gz
7. Extract the uncompressed, tarred file by using one of the following
platform-specific tar -xvpBf commands:
tar -xvpBf nw72_ncw10_solaris_32.tar
tar -xvpBf nw72_ncw10_solaris_64.tar
The NetWorker distribution software directories and files are listed on the screen
as the extraction proceeds.
The PATH environment variable for the user root on the NetWorker server and the
user on each NetWorker client must contain the directory where the NetWorker
executables reside. For information on this directory, see Table 1 on page 23.
Task 2: Install the NetWorker Software

By default, the NetWorker software is installed in the /usr directory. The software can
be installed in a default or nondefault location. For instructions, see:
"Installing to a Default Location" on page 25

"Installing to a Nondefault Location" on page 29
Installing to a Default Location

This section explains how to install the server, client, and storage node software:
"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
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.

Installation Guide
25
3. (Optional) Enter the appropriate option numbers to install the NetWorker

configuration wizards:
Client configuration wizard package (LGTOwiz).
Device configuration wizard package (LGTOwizd).
For more information on the NetWorker configuration wizard, refer to the
NetWorker Release Supplement, UNIX and Linux Version.
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
storage node and for which you have purchased an enabler code:
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:
LGTOclnt (client software package)

LGTOdrvr (device driver software package)
LGTOnode (storage node software package)
LGTOman (optional man pages)
LGTOwiz (optional client configuration wizard package)
LGTOwizd (optional device configuration wizard package)

Installation Guide
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.

For more information on how to start the NetWorker daemons, see "Task 4: Start
the NetWorker Daemons" on page 31.
4. Configure the driver software to provide support for NetWorker software to back
up data to the SCSI storage devices attached to the system. For more information,
see "Autochanger Installation and Configuration" on page 86.
For the latest information about supported devices, refer to the LEGATO
Compatibility Guides on the LEGATO web site.
Server
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
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.
installed.

Installation Guide
27
To install only selected software packages on the server, install them in the
following order:
LGTOdrvr (device drivers package)
LGTOserv (server software package)
LGTOlicm (optional LEGATO License Manager software 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.
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:
Table 2 on page 28 lists the NetWorker daemons for each installation package.
Table 2. NetWorker Daemons
NetWorker Installation Packages
NetWorker Daemons
NetWorker server
nsrd, nsrexecd, nsrindexd,

nsrmmdbd, nsrmmd
NetWorker client
nsrexecd
nsrexecd, nsrmmd

Installation Guide
28
Installing to a Nondefault Location

By default, NetWorker software is installed in the /usr directory. If there is insufficient
disk space on the /usr partition, the following NetWorker packages can be relocated to
a specified directory on another partition:

The following NetWorker packages must always be installed in the default location:
LGTOman (optional NetWorker man pages)

LGTOdrvr (optional NetWorker device driver commands, libraries, and utilities)
For a listing of the default locations and size requirements, see Table 1 on page 23.
Important: Do not relocate any of the packages if LEGATO NetWorker Module

software is already installed on the computer.
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.
To install the NetWorker packages to a nondefault location:

1. Copy the /var/sadm/install/admin/default file, as shown:
cp /var/sadm/install/admin/default /tmp/default.tmp
2. Edit the /var/sadm/install/admin/default file and change the value assigned to the
basedir variable from default to ask, as shown:
basedir=ask
3. Create a directory and the bin and sbin subdirectories to install the NetWorker
packages, for example:
mkdir -p /my_path/sbin
mkdir -p /my_path/bin
4. Modify the root PATH variable to include the bin and sbin subdirectories of the
directory just created, for example:
/my_path/bin:/my_path/sbin

Installation Guide
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.
Task 3: Change the NetWorker Servers with Access to a Client

To limit the servers authorized to access a client, specify a list of trusted NetWorker
servers 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 which NetWorker servers can access a client:
1. Enter the following command to shut down the NetWorker daemons:
nsr_shutdown
2. Edit or create the /nsr/res/servers file and add the set of NetWorker servers, one per
line, that require access to the client. The first entry in this file becomes the default
NetWorker server.
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.

Installation Guide
30
Task 4: Start the NetWorker Daemons

The NetWorker daemons must be started after the installation procedure.
1. Start the NetWorker daemons:
2. Enter the following command at the system prompt:
ps -ef | grep nsr
Table 3 on page 31 lists the NetWorker daemons that should be running.
Table 3. NetWorker Daemons
NetWorker Installation Packages
NetWorker Daemons
NetWorker server
nsrd, nsrexecd, nsrindexd, nsrmmdbd,

nsrmmd
NetWorker client
nsrexecd
nsrexecd, nsrmmd
Note: The NetWorker daemon nsrmmd is only present if one or more devices are
enabled.
Verifying the Installation

The following sections provide information about verifying the installation:
"Ensuring the NetWorker Software Starts" on page 31

"Performing a Test Backup" on page 32
Ensuring the NetWorker Software Starts

The NetWorker software provides the NetWorker Administrator program (nwadmin)
and a command line interface. Use the NetWorker Administrator program for the
following procedures. To learn more about the command line interface, refer to the
nsradmin(8) man page.
The toolbar buttons in the main window of the NetWorker Administrator program
provide quick access to the most frequently performed NetWorker administration
tasks.
The programs Online Help is available through the Help menu.

Installation Guide
31
How to Start the NetWorker Administrator Program

To start the NetWorker Administrator program, enter the following command:
nwadmin -s server_name &
If the NetWorker Administrator program does not appear, try one of the following:
Check that the DISPLAY environment variable is set correctly.

Check that the PATH environment variable contains the correct path to the
NetWorker programs. The default installation directories for the Solaris platform
are:
/usr/bin
/usr/sbin
If the NetWorker Administrator program cannot connect to the specified server:

1. Run the ps command to check that the required NetWorker daemons, nsrd and
nsrexecd, are present on the NetWorker server:
ps -ef | grep nsr
2. 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:
Performing a Test Backup

To perform a test backup using stand-alone devices:
1. Configure a device on the NetWorker server. For more information, refer to the
NetWorker Administrators Guide, UNIX and Linux Version.
2. Insert a volume into the configured device.
3. Label the volume with the Default label template:
a. Select the device.
b. Select Label from the main window. The NetWorker Administrator program
displays the preconfigured label templates.
c. Select the Default pool.
d. Click OK.
4. Mount the volume in the drive by selecting Mount from the main window.
5. Configure the NetWorker client:
a. From the Clients menu, select Client Setup.
b. In the Clients attribute, select the NetWorker server host.
c. In the Save Set attribute, click Add, overwrite the text in the Save Set text box
with the path of a single file to be backed up, such as /usr/etc/hosts, and then
click Change.
d. Click Apply to apply changes.

Installation Guide
32
6. Test the group backup:

a. Click the Group Control button on the toolbar of the main window. The
Group Control window appears with the Default group highlighted.
b. Click Start.
7. To view the progress of the test backup, select Details from the Group Control
window. Messages appear in the panels of the main window as the backup
progresses.
8. To view the client file index entries, click the Indexes button on the toolbar of the
main window. These entries were created during the test backup. Entries that
indicate what data was backed up should appear under Save Sets.
If the test backup was not successful, refer to the troubleshooting information in the
NetWorker Administrators Guide, UNIX and Linux Version to determine the cause.
Uninstalling the NetWorker Software

Use the pkgrm command to uninstall individual NetWorker packages or all of the
NetWorker packages at the same time.
Software Dependencies
The NetWorker software packages depend on each other. Uninstall them in the
following order:
LGTOwizd
LGTOwiz
LGTOserv
LGTOnode
LGTOdrvr
LGTOlicm
LGTOclnt
If the LEGATO License Manager (LLM) software is installed, there is a dependency on

the NetWorker client software and the LLM software must be uninstalled first.
If the device configuration wizard software (LGTOwizd) is installed, there is a
dependency on the NetWorker client configuration wizard software (LGTOwiz) and
the device configuration wizard software must be uninstalled first.
If the client configuration wizard software (LGTOwiz) is installed, there is a
dependency on the NetWorker client software and the client configuration wizard
software must be uninstalled first.
The man pages (LGTOman) and document files have no dependencies and can be
uninstalled at any time.

Installation Guide
33
Uninstalling the Software

To remove the NetWorker software packages:
1. Log in as root on the system where the software is being removed.
2. Enter the nsr_shutdown command to shut down the NetWorker daemons. A list
of NetWorker daemons that will be shut down appears, along with a prompt that
asks whether to continue with the nsr_shutdown command.
3. Enter the pkgrm command to remove the software. For example:
To remove all the packages, enter the following command:

pkgrm LGTOwizd LGTOwiz LGTOserv LGTOnode LGTOdrvr LGTOlicm
LGTOclnt LGTOman
Note: In the pkgrm command, LGTOwizd must appear before the LGTOwiz
package. The LGTOwiz package must appear before the LGTOclnt package.
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.
To remove only the:

Device configuration wizard software, enter the following command:
pkgrm LGTOwizd
The LGTOwizd package must be uninstalled before the LGTOwiz package

that must be uninstalled before the LGTOclnt package. For more
information on the NetWorker configuration wizard, refer to the
NetWorker Release Supplement, UNIX and Linux Version.
Client configuration wizard software, enter the following command:
pkgrm LGTOwiz
The LGTOwiz package must be uninstalled before the LGTOclnt package.
For more information on the NetWorker configuration wizard, refer to
the NetWorker Release Supplement, UNIX and Linux Version.
Server software, enter the following command:
pkgrm LGTOserv
Storage node software, enter the following command:

pkgrm LGTOnode
Device driver software, enter the following command:

pkgrm LGTOdrvr
This removes the LGTOdrvr package from the server or storage node
where the device driver software is installed.

Installation Guide
34
LEGATO License Manager software, enter the following command:

pkgrm LGTOlicm
Client software, enter the following command:
pkgrm LGTOclnt
NetWorker man pages, enter the following command:
pkgrm LGTOman
This removes the LGTOman package from the server, storage node, or
client where the man pages are installed.

Installation Guide
35

Sun Cluster Version 3.0 or 3.1 Environment
This chapter explains how to install NetWorker software in a Sun Cluster version 3.0
or 3.1, environment. It includes the following sections:
"Cluster Concepts and Terminology" on page 36

"Updating from a Previous Release of NetWorker Software" on page 40
"Installing NetWorker Software in a Cluster" on page 41
"Configuring an External Client to a Virtual Server" on page 57
"Defining Ownership of a Raw Partition for Virtual Clients" on page 58
"NetWorker Cluster Script" on page 59
A Sun Cluster system enables applications to be run and administered as highly

available resources (data services). For detailed information about Sun Cluster 3.0 or
3.1, refer to the appropriate Sun documentation.
Important: Highly available storage nodes are not supported.
Cluster Concepts and Terminology

This section discusses the following:
"Cluster Terminology" on page 37

"About Clustering" on page 37
"Cluster-Aware and Cluster-Unaware NetWorker Servers" on page 38

Installation Guide
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:
Node 1 is a computer with its own Local Disk.

Highly available NetWorker Server on the Virtual Server owns Shared Disks.

Installation Guide
37
Figure 1. General Cluster Configuration

Node 1
clus_phys1
Node 2
clus_phys2
Private NetWork
clus_log1
Local Disk
If Node1fails,
clus_log1 fails
over to Node2
Local Disk
NetWorker Logical Host

(Virtual Server)
Volume-managed Shared Disks

Administrative
Workstation
Terminal Concentrator
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.
Cluster-Aware and Cluster-Unaware NetWorker Servers

To perform scheduled backups within a cluster, a cluster-aware NetWorker server and
NetWorker client must be installed.
Note: Not all NetWorker servers and clients are cluster-aware. For example:
If a NetWorker server does not have cluster-client support, it cannot recognize

cluster clients. When a scheduled backup is performed, the NetWorker server
backs up only the private data of the physical node. The data is backed up to the
same index representing the physical node.

Installation Guide
38
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.
The following sections discuss the software and hardware required to install and
configure the NetWorker server or client software within a Sun Cluster environment:
"Software Requirements" on page 39

"Hardware Requirements" on page 39
"Configuration Options" on page 39
"System Information Requirements for a Highly Available NetWorker Server" on
page 40
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:
Solaris 8 or Solaris 9 operating environment

Sun Cluster version 3.0 or 3.1
Volume Manager software (Solstice DiskSuite/Solaris Volume Manager)
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:
Tape libraries with a NetWorker virtual server

Remote physical storage node with a NetWorker virtual server

Installation Guide
39
System Information Requirements for a Highly Available NetWorker Server

Figure 2 on page 40 and Table 4 on page 40 display the system information needed to
install a highly available NetWorker software within a Sun Cluster environment.
Figure 2. Sample Cluster Configuration
Node 1
clus_phys1
Node 2
clus_phys2
Private NetWork
clus_log1
Local Disk
If Node1fails,
clus_log1 fails
over to Node2
Local Disk
NetWorker Logical Host

(Virtual Server)

Administrative
Workstation
Public NetWork
Table 4. Required Information: Highly Available NetWorker Server

Information Required
Example
NetWorker virtual hostname with an IP address in the same subnet as clus_vir1

the cluster nodes
192.168.1.10
NetWorker globally mounted configuration area
/global/nw
NetWorker cluster configuration script
/usr/sbin/networker.cluster
File containing the host ID of all the cluster members
/nsr/res/hostids
Updating from a Previous Release of NetWorker Software

To update from NetWorker releases 6.1.x and 7.0 to NetWorker release 7.2 in a Sun
Cluster 3.0 or 3.1 environment:
1. Collect the following NetWorker software system information:
The location of the NetWorker server global /nsr directory on the shared
storage.
The location of the NetWorker client local /nsr directories.

Installation Guide
40
2. List and save the cluster resource group configuration:

scrgadm -pvv > scrgadm_pvv.out
scconf -pvv > scconf_pvv.out
3. Use NetWorker software to back up the cluster. Make sure that you have a recent
backup of the indexes and bootstrap using the savegrp -O command.
4. Remove the NetWorker software cluster configuration files and uninstall the
NetWorker software. Do not remove the global and local /nsr directories.
For instructions on uninstalling the NetWorker software, see "Uninstalling the
NetWorker Software" on page 58.
5. If required, upgrade the Sun Cluster software. For instructions, refer to the Sun
Cluster documentation.
6. Install and configure the NetWorker 7.2 software.
Make sure that:
You specify the same local /nsr and global /nsr directories.
The NetWorker client type resource properties for Owned_paths and
Clientname are the same as before the upgrade.
The NetWorker Config_dir resource contains the same values as before the
upgrade.
The Network_resources_used property contains the same value that the
Resource_dependencies property had before the upgrade.
For detailed instructions on installing NetWorker software in a Sun Cluster
environment, see "Installing NetWorker Software in a Cluster" on page 41.
Installing NetWorker Software in a Cluster

To install the NetWorker software in a Sun Cluster environment, see the following:
"Installing a NetWorker Virtual Server" on page 41

"Installing Only the NetWorker Client Software in a Cluster" on page 53
Installing a NetWorker Virtual Server

To install and configure the NetWorker software as a highly available service in a
cluster, perform the following tasks:
"Task 1: Install the NetWorker Software" on page 42

"Task 2: Define the NetWorker Server as Highly Available" on page 43
"Task 3: Create an Instance of the NetWorker Server Resource Group" on page 44
"Task 4: (Optional) Add a HAStoragePlus Resource to an Existing NetWorker
Server Resource Group" on page 46
"Task 5: Grant Access to the Highly Available NetWorker Server" on page 46
"Task 6: Configure the NetWorker Server" on page 48
"Task 7: Configure Clients under the NetWorker Server" on page 48
"Task 8: Create Instances of the NetWorker Client Resource Type" on page 50

Installation Guide
41
"Task 9: Register Licenses for the Highly Available NetWorker Server" on page 51
"Task 10: Authorize the Software" on page 53
Task 1: Install the NetWorker Software

The NetWorker software must be installed on all nodes in the cluster that are required
to run the NetWorker resource group.
Important: Make sure that the:

Solaris 8 operating environment and Sun Cluster 3.0 or 3.1 software are already
installed on all nodes in the cluster and that those nodes boot in cluster mode.
PATH environment variable includes /usr/sbin and /usr/cluster/bin.
To install the NetWorker software on nodes that will be running the NetWorker
resource group:
1. Access the NetWorker software from the distribution media. For 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.
installed.
Install selected software packages in the following order:

LGTOdrvr (device drivers package)
6. Press [q] to exit.

Installation Guide
42
Task 2: Define the NetWorker Server as Highly Available

To define and configure the NetWorker server as highly available:
1. Log in as root.
2. Make sure that the /etc/hosts file on each cluster node contains the name of the
logical host. The logical hostname can be published in the Domain Name System
(DNS) or Network Information Services (NIS).
3. From each node in the cluster that will run the NetWorker server process:
a. Run the cluster configuration script networker.cluster located in /usr/sbin. For
an example of the script, see "NetWorker Cluster Script" on page 59.
This script defines the LGTO.serv and the LGTO.clnt resource types that the
NetWorker software requires.
b. In response to the following prompts, enter the following information:
Enter directory where local NetWorker database is installed
[/nsr]?
Enter the location of the local NetWorker database directory provided

during the installation procedure. For example: /space/nsr
Do you wish to configure for both NetWorker server and
client?
Yes or No [Yes]?
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]?
Enter Yes to ensure compatibility with other cluster environments.

Enter the Logical Hostname to be used for NetWorker?
Enter the published logical hostname to be used by the highly available

NetWorker server. For example: clus_vir1
In what path will this nsr directory be created/located?
Enter the pathname of the globally mounted /nsr directory that will
contain the configuration information for the highly available NetWorker
server. For example: /global/nw.
Notes:
For more information, see "System Information Requirements for a Highly

Available NetWorker Server" on page 40.
To undo any changes to the configuration, run the networker.cluster -r script and
then run the networker.cluster script again.

Installation Guide
43
Task 3: Create an Instance of the NetWorker Server Resource Group

A resource group must be created for the highly available NetWorker server. It must
contain the following resources:
Logical hostname
Globally mounted 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

Installation Guide
44
5. Create an instance of the LGTO.serv resource type:

scrgadm -a -j server -t LGTO.serv -g networker \
-y network_resources_used=clus_vir1 \
-y Resource_dependencies=hastorageplus \
-x config_dir=/global/clus_vir1/nw
If the logical host resource name is different than the hostname it specifies, set the
optional servername property to the virtual hostname:
scrgadm -a -j server -t LGTO.serv -g networker \
-y network_resources_used=clus_vir1 \
-x servername=virtual_hostname \
-x config_dir=/global/clus_vir1/nw
Note: If you are using a HAStoragePlus resource, set resource_dependencies
property to the HAStoragePlus resource name.
6. Start the NetWorker resource group:
scswitch -Z -g networker
Example: A Highly Available NetWorker Server

In the following example, a highly available NetWorker server uses the logical
hostname backup_server. The highly available NetWorker server uses /global/networker
(globally mounted filesystem) as its configuration directory.
1. Create a resource group with the name backups:
scrgadm -a -g backups
2. Add the logical hostname resource type to the resource group created in the
previous step:
scrgadm -a -L -g backups -l backup_server
3. Create an instance of the LGTO.serv resource type with the name networker_server.
This resource belongs to the resource group backups and has a dependency on the
logical host created in the previous step. Specify the configuration directory on the
globally mounted filesystem /global/networker:
scrgadm -a -j networker_server -t LGTO.serv -g backups \
-y network_resources_used=backup_server \
-x config_dir=/global/networker
4. The NetWorker logical host is also a client of the highly available NetWorker
server. Create an instance of the LGTO.clnt resource type for the logical host
backup_server within the resource group backups. The name of this resource is
networker_client:
scrgadm -a -j networker_client -t LGTO.clnt -g backups \
-x clientname=backup_server -x owned_paths=/global/networker
5. Start the highly available service associated with the resource group backups.
scswitch -Z -g backups

Installation Guide
45
Task 4: (Optional) Add a HAStoragePlus Resource to an Existing NetWorker

Server Resource Group
To add a SUNW.HAStoragePlus resource to an existing NetWorker server resource
group:
1. Determine whether the HAStoragePlus resource type is registered within the
cluster:
scrgadm -p | egrep Type
2. If required, register the HAStoragePlus resource type within the cluster:
scrgadm -a -t SUNW.HAStoragePlus
3. 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
4. Enable the HAStoragePlus resource:
scswitch -e -j hastorageplus
5. Set up a dependency for the NetWorker Server resource on the HAStoragePlus
resource:
scrgadm -c -j server -y Resource_Dependencies=hastorageplus
6. Verify that the resource dependencies are correctly set:
scrgadm -pvv -j server | egrep strong
Task 5: Grant Access to the Highly Available NetWorker Server

Before a NetWorker server can back up a client, the client must grant the server access.
Granting access is controlled by the servers file. For the node that is running the
NetWorker Server resource group, this file is located in the globally mounted
filesystem. Otherwise, this file is located on a local disk.
is authorized to:
To grant access to the highly available NetWorker server:

1. On one node in the cluster:
a. Stop the NetWorker service using the cluster management software, as
follows:
scswitch -F -g networker

Installation Guide
46
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.
For example:
clus_vir1
clus_phys1
clus_phys2
d. Restart the NetWorker processes:
3. On one node in the cluster, start the NetWorker service using the cluster
management software, as follows:
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

Installation Guide
47
c. Edit or create the /nsr/res/servers file:

client.
For example:
clus_vir1
clus_phys1
clus_phys2
d. Restart the NetWorker processes:
Task 6: Configure the NetWorker Server

To configure the NetWorker server:
1. Log in as root on the cluster node that is currently running the NetWorker server
resource group.
2. Start the NetWorker Administrator program:
nwadmin -s clus_vir1
3. From the Server menu, select Server Setup.
4. In the Server dialog box, add entries in the Administrator attribute for any cluster
nodes that are not listed. For example:
root@hostname
5. Click Add and then click Apply.
Task 7: Configure Clients under the NetWorker Server

When the networker.cluster script runs, it creates a symbolic link named /nsr that
points to a local disk. It also creates a second link named nsr.NetWorker.local that points
to the local NetWorker directory. For example, if the local NetWorker directory was
created in /var/nsr, each client member has the following links:
/nsr->/nsr.NetWorker.local
/nsr.NetWorker.local->/var/nsr
To configure each client under the NetWorker server:

1. From one node in the cluster, start the NetWorker Administrator program:
2. (Optional) Define save groups as required:
a. From the Customize menu, select Groups.
b. In the Groups window, select Details from the View menu.
c. Click Create to create a new save group.

Installation Guide
48
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.
d. For each save group, click Enabled in the Autorestart attribute.

e. For each save group, make sure that the Manual Restart option is unchecked
in the Options check box.
f. Define the remaining attributes and click Apply.
3. Make each physical client within the cluster a NetWorker client of the virtual
NetWorker server.
For each physical client in the cluster:
a. In the NetWorker Administrator program, select Client Setup from the Clients
menu.
b. If these steps are being performed after updating the NetWorker server, click
on the client name. Otherwise, click Create and enter the name of the physical
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 Client dialog box, click Add, and click
Apply.
4. Make each virtual client within the cluster a NetWorker client of the virtual
NetWorker server.
For each virtual client in the cluster:
menu.
b. In the Clients dialog box, if these steps are being performed after updating the
NetWorker server, click the client name in the client list. Otherwise, click
Create and enter the name of the virtual client for the Name attribute.
root@clus_phys1
e. Define the remaining attributes in the Clients dialog box, click Add, and click
Apply.
The first time the NetWorker application runs, it creates the Client resource for the
highly available NetWorker server.

Installation Guide
49
Task 8: Create Instances of the NetWorker Client Resource Type

An instance of the NetWorker Client resource type must be created for each virtual
client that accesses data on globally mounted filesystems. Virtual clients in Sun Cluster
3.0 and 3.1 are either logical hostnames or shared addresses.
Important: All globally mounted filesystems (except the /global/.devices/... filesystems)

must be owned by a resource group and defined in a NetWorker Client resource type.
If the filesystems are not properly configured, multiple copies will be backed up for
each cluster node.
To back up the data for a virtual client:

1. Create an instance of the NetWorker Client resource as part of an existing resource
group that contains a logical host or shared addresses. For example:
scrgadm -a -j resource_name -g resource_group_name -t LGTO.clnt \
-x clientname=virtual_hostname -x owned_paths=pathname_1, pathname_2[,...]
The virtual_hostname variable is a hostname specified by a logical hostname or
shared address resource. By default, the logical hostname or shared address
resource name is the same as the first hostname in the list of hostnames the
resource controls.
If the logical hostname or shared address resource was explicitly named, set the
optional network_resource property to the resource name:
-x clientname=virtual_hostname
-x network_resource=logicalhostname_ or_SharedAddress_resource_name \
-x owned_paths=pathname_1, pathname_2[,...]
For more information, see the following examples:
"Example: A Highly Available Informix Database Server" on page 51
"Example: A Scalable Apache Web Server" on page 51
2. Run a test probe to verify that the Client and Group resources are properly
configured.
On the node on which the NetWorker server resides, run the following command:
savegrp -pv -c client_name savegroup_name
If the test probe does not display the scheduled backups and index, refer to the
section on "Tracking Scheduled Saves" in the NetWorker Administrators Guide.

Installation Guide
50
Example: A Highly Available Informix Database Server

In the following example, the Informix database server is configured to use the DNS
registered hostname informix_lhrs. An existing failover resource group named
informix_rg contains a:
SUNW.informix resource named informix_res

SUNW.LogicalHostname resource named informix_lhrs
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
Example: A Scalable Apache Web Server

In the following example, an Apache web server is configured to use the DNS
registered hostname apache_sars. An existing scalable resource group named apache_rg
contains a:
SUNW.apache resource named apache_res

SUNW.SharedAddress resource named apache_sars
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
Task 9: Register Licenses for the Highly Available NetWorker Server

Important: Only NetWorker Power Edition supports backup and recovery for a highly
available NetWorker server; therefore a Power Edition license is required. Power
Edition includes two Cluster Client licenses of the same platform type; adding any
additional cluster clients requires additional Cluster Client Connection licenses.

Installation Guide
51
To register and license the highly available NetWorker server:

1. Order licenses from LEGATO for the type of NetWorker server and client
configuration you are using.
2. Log on to the system that is currently running the NetWorker resource group.
3. Perform the following operations to enter the purchased enabler codes:
a. If you have been evaluating the NetWorker highly available software and
have now purchased the software:
Upgrade from the base evaluation enabler to the purchased Power
Edition base enabler by entering the following command:
nsrcap -v -u base_enabler_code
Delete any remaining evaluation enablers using the NetWorker

Administrator program:
This eliminates warning messages due to expiring evaluation enablers.

b. For each enabler code, enter the following command:
nsrcap -v -c enabler_code
4. Make sure that the highly available NetWorker server is defined as a part of the
cluster.
5. On each node that is currently running the NetWorker server resource group, run
the following command and capture the output:
hostid
This prints the numeric identifier of the current host.
6. Log on to the computer that is currently running the NetWorker server resource
group.
a. Create a file named /nsr/res/hostids that contains the host IDs of all the cluster
nodes that were captured in the previous steps. Use the following syntax:
hostid1:hostid2:hostid3:...
For example: 12345678:87654321:13572468
b. Restart the server by taking the highly available NetWorker server offline and
then putting it back online, as follows:
scswitch -F -g networker
7. On one node in the cluster:
a. Start the NetWorker Administrator program using the logical hostname for
the highly available NetWorker server:
b. From the Server menu, select Registration.
c. Note the new host ID that appears in the Registration window. This is the
composite host ID.
d. Click Ok to close the Registration window.

Installation Guide
52
Task 10: Authorize the Software

For information on how to authorize LEGATO software, see "Chapter 8: Evaluating
and Licensing NetWorker Software" on page 94.
Installing Only the NetWorker Client Software in a Cluster

In this configuration, the NetWorker server is running on a node that is not a member
of the cluster.
To install a NetWorker cluster client, perform the following tasks:
"Task 1: Install the NetWorker Cluster Client Software" on page 53

"Task 2: Configure NetWorker Client Software as Highly Available" on page 54
"Task 3: Create Instances of the Client Resource Type" on page 54
"Task 4: Define the List of Trusted NetWorker Servers" on page 56
Important: Make sure that the NetWorker client software is installed on each node in
the cluster.
Task 1: Install the NetWorker Cluster Client Software

Important: Make sure that the Solaris 8 operating environment and Sun Cluster 3.0 or
3.1 software are already installed on all cluster nodes and that those nodes boot in
cluster mode.
Also, make sure that the PATH environment variable includes /usr/sbin and
/usr/cluster/bin.
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.
package temporarily requires 70 MB of free space on the client computer.

Installation Guide
53
4. (Optional) Enter the appropriate option number to install the man pages,
(LGTOman).
6. When all the applicable packages have been added, and the prompt appears, press
[q] to exit.
Task 2: Configure NetWorker Client Software as Highly Available

To define and configure a NetWorker client as highly available:
1. Log in as root on each node where the NetWorker software is being installed.
virtual host. The virtual hostname can be published in the DNS or NIS.
3. For each node in the cluster:
a. Run the cluster configuration script, /usr/sbin/networker.cluster.
This script defines the LGTO.clnt resource types that the NetWorker software
requires.
b. In response to the prompts, enter the following information:
[/nsr]?
client? Yes or No [Yes]?
Enter No. This configures only the client software.
Notes:
For more information, see "System Information Requirements for a Highly
Available NetWorker Server" on page 40.
Any changes to the configuration can be undone by running the

networker.cluster -r option and then running the networker.cluster script
again.
Task 3: Create Instances of the Client Resource Type

An instance of the NetWorker Client resource type must be created for each virtual
client that accesses data on globally mounted filesystems. Virtual clients in Sun Cluster
3.0 and 3.1 are either logical hostnames or shared addresses.
Important: All globally mounted filesystems (except the /global/.devices/... filesystems)

must be owned by a logical host and defined in a NetWorker Client resource type. If
the filesystems are not properly configured, multiple copies will be backed up for each
cluster node.

Installation Guide
54
To back up the data for a virtual client:

From any node in the cluster, create an instance of the NetWorker Client resource as
part of an existing resource group that contains a logical host or shared address. For
example:
-x clientname=virtual_hostname -x owned_paths=pathname_1, pathname_2[,...]
Example: A Highly Available Informix Database Server

In the following example, the Informix database server is configured to use the DNS
registered hostname informix_lhrs. An existing failover resource group named
informix_rg contains a:
SUNW.informix resource named informix_res

SUNW.LogicalHostname resource named informix_lhrs
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
Example: A Scalable Apache Web Server

In the following example, an Apache web server is configured to use the DNS
registered hostname apache_sars. An existing scalable resource group named apache_rg
contains a:
SUNW.apache resource named apache_res

SUNW.SharedAddress resource named apache_sars
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

Installation Guide
55
Task 4: Define the List of Trusted NetWorker Servers

Granting access is controlled by the servers file. For the node that is currently running
the NetWorker server resource group, this file is located in the globally mounted
is authorized to:
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
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:

1. From any node in the cluster, start the NetWorker Administrator program:
2. Make each physical client within the cluster a NetWorker client of the NetWorker
server.
menu.
NetWorker server, click on the client name in the Client list. Otherwise, click
Create and enter the name of the physical client for the Name attribute.

Installation Guide
56
root@clus_phys1
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.
menu.
NetWorker server, click on the client name in the Clients list. Otherwise, click
root@clus_phys1
4. Schedule backups using the NetWorker application. For detailed instructions, refer
to the NetWorker Administrators Guide.
Configuring an External Client to a Virtual Server

Use this procedure to configure and back up an external NetWorker client to a highly
available NetWorker server. Before a NetWorker server can back up a client, the client
must grant the server access. Granting access is controlled by the servers file. If the
servers file does not exist, any NetWorker server can back up this client. If the servers file
does exist, only the specific servers listed in the file can back up the client.
On each NetWorker client that is outside of the cluster:
1. Shut down the NetWorker processes:
nsr_shutdown
2. Verify that all NetWorker daemons have stopped:
ps -ef |grep nsr
3. Edit or create the /nsr/res/servers file:
a. Add the set of NetWorker servers, one per line, that require access to this
client.
b. Add an entry for the NetWorker logical hostname first. Then add entries for
each physical host that can run the NetWorker resource group. For example:
clus_vir1
clus_phys1
clus_phys2

Installation Guide
57
Defining Ownership of a Raw Partition for Virtual Clients

To back up the raw partitions of a NetWorker virtual client, make sure that the raw
device path appears in the owned paths field of the LGTO.clnt resource.
Example: A Highly Available Web Server

In the following example, a highly available web server uses the shared address
web_server. The web server daemons are placed under the control of the resource group
apache_rg. The daemons access files that are kept in two separate globally mounted
filesystems: /global/web/config and /global/web/data. The web server also accesses the raw
partition /dev/md/hunt/rdsk/d30.
To create the NetWorker Client resource named apache_nw, enter the following:
scrgadm -a -j apache_nw -g apache_rg -t LGTO.clnt -x
clientname=web_server \
-x owned_paths=/global/web/config,/global/web/data,/dev/md/hunt/rdsk/d30
For more information on backing up raw partitions, refer to the rawasm command as
described in the uasm(1m) man page.

To uninstall the NetWorker software from a cluster environment:
1. On one node in the cluster, disable and remove all instances of the LGTO.serv and
LGTO.clnt resource types in the cluster.
For more information, refer to the scswitch(1m) and scrgadm(1m) man pages.
a. Log in as root on the computer that the software is being removed.
b. Undo all changes to the configuration by running the networker.cluster -r
option.
c. Enter the following command to shut down the NetWorker daemons:
nsr_shutdown
A list of NetWorker daemons to be shut down appears, and you are prompted
whether to continue.
Note: Remove the NetWorker software packages in the following order:
LGTOserv
LGTOnode
LGTOdrvr
LGTOclnt
The man pages (LGTOman) and document files have no dependencies
remove them at any time.
d. Enter the following command to remove all the packages:
pkgrm LGTOserv LGTOnode LGTOdrvr LGTOclnt LGTOlic LGTOman
Installation Guide
58
NetWorker Cluster Script

This section demonstrates the typical responses you would give to the prompts of the
networker.cluster script, assuming the following configuration:
Virtual server: clus_vir1

Mount point: /global/nw
networker.cluster
--------------------------------------------------------------Sun Cluster 3.0 extends the Solaris operating environment into a
cluster operating system. A cluster is a collection of loosely
coupled computing nodes that provide a single client view of
network services or applications.
To complete this procedure, one must have a logical host defined
on which the NetWorker server can be entered
------------------------------------------------------------Do you wish to continue? [Yes]? Yes
Shutting down NetWorker services...
[/nsr]? /space/nsr
Restarting syslog daemon...
Do you wish to configure for both NetWorker server and client?
Yes or No [Yes]? Yes
Do you wish to add now the site-specific values for:
NSR_SHARED_DISK_DIR and NSR_SERVICE_ID
Enter the Logical Hostname to be used for NetWorker? clus_vir1
The shared directory of the NetWorker server (the nsr directory)
must be on a globally mounted file system.
In what path will this nsr directory be created/located?
/global/nw
Creating /usr/sbin/nsr/lcmap file ...
-rwxrwxr-x
1 root
1707 Aug 20 12:44 /usr/sbin/nsr/lcmap
Finished creating /usr/sbin/nsr/lcmap file.

resource type is not registered
Defining LGTO.clnt resource type with RGM.
resource type is not registered
Defining LGTO.serv resource type with RGM.
NetWorker has been successfully cluster-configured.

Installation Guide
59

LEGATO Automated Availability Manager
Environment
This chapter explains how to install NetWorker software in a LEGATO Automated

Availability Manager (LAAM) environment (formerly LEGATO Cluster). It
includes the following sections:
"Software Installation Roadmap" on page 60

"Configuring an External Client to a Virtual Server" on page 71
"Defining Ownership of a Raw Partition for Virtual Clients" on page 71
"Tracking Scheduled Saves" on page 72
An Automated Availability Manager cluster consists of multiple nodes in a networked

configuration and provides additional security with the failover capability. Failover
allows another node in the cluster to take over operations from the first node. For
information, refer to the LEGATO Automated Availability Manager User Guide and the
LEGATO Automated Availability Manager Enterprise Programming Guide.
Software Installation Roadmap

The following tasks are a roadmap to follow 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 61.
2. Install the required NetWorker software. For more detailed information, see one of
the following sections:

3. Enable and register all of the NetWorker products. For more information, see

Installation Guide
60
Chapter 5: Installing NetWorker Software in a LEGATO Automated Availability Manager Environment
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:

"Hardware Requirements" on page 61
"Configuration Options" on page 61
"System Information Requirements" on page 62
For the most up-to-date information regarding software and hardware requirements,
refer to the LEGATO Compatibility Guides on the LEGATO web site.
To install NetWorker cluster server, make sure that the following software is installed
on each node in the cluster:
Solaris version 2.6, 2.7 or later

LAAM release 4.8.1, 5.0
LEGATO NetWorker release 7.2
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:
Tape libraries with a NetWorker virtual server

Remote physical storage node with a NetWorker virtual server

Installation Guide
61
System Information Requirements

Figure 3 on page 62 and Table 5 on page 62 display the system information needed to
install NetWorker software within a LEGATO Automated Availability Manager
environment.
Different platforms use different terms for the same cluster concepts. LEGATO
Automated Availability Manager refers to:
Physical hosts as nodes

Virtual server as a resource group (application service)
Figure 3. Sample Cluster Configuration
Node 1
clus_phys1
Node 2
clus_phys2
Private NetWork
clus_log1
Local Disk
If Node1fails,
clus_log1 fails
over to Node2
Local Disk
NetWorker
Logical Host

Administrative
Workstation
Public NetWork
Table 5. Required Information (Part 1 of 2)

Example
NetWorker virtual hostname with an clus_vir1

IP address
192.168.1.10
NetWorker package mount point for /nsr_shared_mnt_pt
virtual volume
Shared storage disk virtual volume

Installation Guide
/dev/dsk/c1t3d0s0
62
Table 5. Required Information (Part 2 of 2)

Example
NetWorker control script
/usr/sbin/nw_ux.lc
File containing the hostids of all the

cluster members
/nsr/res/hostids
NetWorker monitor script
/usr/sbin/nw_ux.lc
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: Install the NetWorker Software in a Cluster" on page 63

"Task 2: Define the NetWorker Server as a Highly Available Application" on
page 63
"Task 3: Grant Access to the NetWorker Virtual Server" on page 65
"Task 4: Configure the NetWorker Server" on page 66
"Task 6: Register NetWorker Licenses for Virtual Server Failover" on page 68
Task 1: Install the NetWorker Software in a Cluster

To install the NetWorker software:
1. Make sure that the most recent cluster patch for the operating system is installed.
2. Install the following NetWorker software on each node in the cluster:
Client
Driver
Storage node
Server
For detailed instructions, see "Installing the NetWorker Software" on page 23.
Task 2: Define the NetWorker Server as a Highly Available Application

To define and configure NetWorker server as a highly available application:
1. Log in as root.
virtual host. The virtual hostname can be published in the Domain Name System
(DNS) or Network Information Service (NIS).

Installation Guide
63
3. Set and export the FT_DIR, FT_DOMAIN, and the FT_CONSOLE_DIR

environment variables. For example, from the Bourne shell enter 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
Notes:
xx = 45 for LEGATO Cluster version 4.5.1
xx = 47 for LEGATO Cluster version 4.7
domain_name = LEGATO Cluster domain
4. From each node in the cluster that will run the NetWorker server process:
a. Run the cluster configuration script, /usr/sbin/networker.cluster. For an
example, see "NetWorker Cluster Script" on page 73.
b. Enter 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, customize the /usr/sbin/nw_ux.lc.imp file. Use the
nw_ux.lc.imp file to create the NetWorker resource group and its dependant objects
in one step.
Important: In the /usr/sbin/nw_ux.lc.imp file, there are multiple instances of the NW

Customize comment, make sure 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.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.

Installation Guide
64
6. At the command line, enter the following command:

$FT_DIR/bin/ftcli -c import /usr/sbin/nw_ux.lc.imp
7. Verify that the NetWorker resource group was imported correctly, using the
Automated Availability Manager Management console.
Task 3: 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.
is authorized to:
access and backup the client
perform a directed recover to the client
To grant access to the NetWorker virtual server:

have stopped.
b. Edit or create the /nsr.NetWorker.local/res/servers file:
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
-s servername in the file.
2. On one node in the cluster, start the NetWorker service using the cluster
management software.
a. Bring the NetWorker Resource Group online using ftconsole.
b. Edit or create the /nsr/res/servers file:
client.
clus_vir1
clus_phys1
clus_phys2

Installation Guide
65
3. If required, grant access to each NetWorker client that is outside of the cluster:
have stopped.
b. Edit or create the /nsr/res/servers file:
client.
clus_vir1
clus_phys1
clus_phys2
Task 4: 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 Administrator program:
2. From the NetWorker Administrator program, select Server Setup.
a. In the Administrator attribute, add entries for any cluster nodes that are not
already listed. For example:
root@hostname
b. Click Add and select Apply.

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.NetWorker.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.NetWorker.local
/nsr.NetWorker.local->/var/nsr

1. (Optional) Define save groups as required:
a.
b.
c.
d.
e.
Open the NetWorker Administrator program.

Select Customize>Groups from the main menu.
Select View>Details from the main menu.
Click Create to create a new save group.
Define the remaining attributes and click Apply.

Installation Guide
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.
f. For each save group, click Enabled in the Autorestart field.

g. For each save group, make sure that the Manual Restart option is unchecked
in the Options checkbox.
2. Make each physical client within the cluster a NetWorker client of the virtual
NetWorker server.
a. Using the NetWorker Administrator program, select Client>Clients Setup.
b. Click Create and enter the name of the physical client for the Name attribute.
c. Define the remaining attributes in the Client window and click Add and
select Apply.
3. Make each virtual client within the cluster a NetWorker client of the virtual
NetWorker server.
a. Using the NetWorker Administrator program, select Client>Clients Setup.
b. Click Create and enter the name of the virtual client for the Name attribute.
c. In the Remote Access field, add entries for each physical client within the
root@clus_phys1
d. For the group attribute, select a group.
e. Define the remaining attributes in the Client window and click Add and
select Apply.
The first time the NetWorker application runs, it creates the client resource for the
NetWorker virtual server.
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 72.

Installation Guide
67
Task 6: Register NetWorker Licenses for Virtual Server Failover

To register a NetWorker server in a cluster environment:
1. Make sure that the NetWorker virtual server is defined as a part of the cluster.
2. Make sure that the NetWorker service is running.
3. On each physical node in the cluster:
a. Relocate sequentially the NetWorker server to this node.
b. In the NetWorker Administrator program, select Server>Registration.
c. Note the hostid that is displayed on the Registration window.
4. Log on to the system running the NetWorker virtual server and create a file named
/nsr/res/hostids that contains the hostids 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. In the NetWorker Administrator program, select Server>Registration. Note the
hostid that is displayed in the Registration window.
7. Register the NetWorker software. For details, see "Chapter 8: Evaluating and
Licensing NetWorker Software" on page 94.
Customer Service will then send the authorization codes using the composite hostid.
The composite hostid was created after step 4.

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

"Task 2: Configure NetWorker Client Software as a Highly Available Application"
on page 69
Important: Make sure the NetWorker client software is installed on every node to be
backed up in the cluster.

To install the NetWorker client software on each node in the cluster:
1. Make sure 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. For
detailed instructions, see "Installing the NetWorker Software" on page 23.

Installation Guide
68
Task 2: Configure NetWorker Client Software as a Highly Available Application

To define and configure a NetWorker client as a highly available application:
(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 enter 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
Note:
xx = 45 for LEGATO Cluster version 4.5.1
domain_name = LEGATO Cluster domain
b. In response to the prompt to configure the NetWorker server, enter No.
networker.cluster -r option.
For an example of the script, see "NetWorker Cluster Script" on page 73.

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.
is authorized to:

Installation Guide
69
stopped.
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
the file.

Note: The NetWorker server might reside outside of the cluster.
server.
a. In the NetWorker Administrator program, select Client>Clients Setup.
b. Click Create and enter the name of the physical client for the Name attribute.
c. Define the remaining attributes in the Client window and click Apply.
a. In the NetWorker Administrator program, select Client>Clients Setup.
b. Click Create and enter the name of the NetWorker server for the Name
attribute.
c. For the Remote Access attribute, add entries for each physical client within
the cluster. For example:
root@clus_phys1
d. For the group attribute, select a group.
e. Define the remaining attributes in the Client window and click Apply.
to the LEGATO NetWorker Administrators Guide.

Installation Guide
70
Configuring an External Client to a Virtual Server

Use the following procedure to configure and back up an external NetWorker client to
a NetWorker highly available 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.
is authorized to:
On each NetWorker client that is outside of the cluster:

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

To back up the raw partitions of a NetWorker virtual client, use the IPOverride option.
1. Open the LEGATO Automated Availability Manager 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 appears.
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 filesystem /share/web, set the following path:
IPOverrride=135.69.103.149=/dev/rdsk/c1t3d0s1, /share/web

Installation Guide
71
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.

Make sure 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.
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

1. If necessary, use the cluster management software to stop the NetWorker server
daemons.
2. Shut down the client daemons on the node on which the NetWorker software is
being removed:
nsr_shutdown

Installation 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

This example, generated when the networker.cluster script runs, it uses the following
configuration:

Virtual server IP address: 192.168.1.10
Mount point: /nsr_shared_mnt_pt
-----------------------------------------------------------LEGATO Cluster x.y installations have a hierarchy of cluster
objects which define high available applications. Each
application service is associated with a resource group that
encapsulates services, IPs and data sources, which may fail over
from one physical host to the next, depending on the availability
and health of the machine it is running upon. When a failover
occurs, this logical host--aka resource group--moves, carrying
its IP addresses and data sources.
One must define a NetWorker resource group with an IP and shared
data source, which contains the shared /nsr directory, before
using NetWorker. This can be done before or after running this
script. The optional ftcli-import template file
/usr/sbin/nw_ux.imp can be used for this purpose.
--------------------------------------------------------------Do you wish to continue? [Yes]? Yes
[/nsr]?
Do you wish to automatically add site-specific values for:
NSR_SHARED_DISK_DIR and NSR_SERVICE_ID in /usr/sbin/nw_ux.lc
Enter the published virtual hostname used for NetWorker?
clus_vir1
Enter the shared mount point directory in which nsr.res resides?
/nsr_shared_mnt_pt
/usr/sbin/nw_ux.lc has been modified

Installation Guide
73
Now please ensure NetWorker is configured as a resource group in

LEGATO Cluster. Refer to the LEGATO Cluster & NetWorker manuals.
Creating /usr/sbin/lcmap file...
!/bin/sh
FT_DIR=/opt/LGTOlc45
FT_DOMAIN=nwmerge
export FT_DIR FT_DOMAIN
$FT_DIR/bin/ftPerl $FT_DIR/bin/nwclust.pl
Finished creating /usr/sbin/lcmap file.
You can now use ftconsole to add a resource group for NetWorker
using the template specifications given in
/usr/sbin/nw_ux.lc.imp.
Alternatively, you can modify /usr/sbin/nw_ux.lc.imp and then
run ftcli with '-c "import /usr/sbin/nw_ux.lc.imp"'.
Note that the user accounts that run NetWorker on the cluster
nodes must be added as secure users of LEGATO Cluster.

Installation Guide
74

VERITAS Cluster Server 3.5 Environment
This chapter explains how to install NetWorker software in a VERITAS Cluster Server
3.5 environment. It includes the following sections
"Cluster Concepts and Terminology" on page 75

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.
Important: A stand-alone or highly available (virtual) NetWorker server is not

supported in the cluster. The NetWorker server must be outside the cluster. Highly
available storage nodes are also not supported in the cluster. However, physical
storage nodes can either be in the cluster or outside the cluster.
Cluster Concepts and Terminology

This section discusses the following:
"Cluster Terminology" on page 76

"About Clustering" on page 76
"Cluster-Aware and Cluster-Unaware NetWorker Servers and Clients" on page 77

Installation Guide
75
Chapter 6: Installing NetWorker Software in a VERITAS Cluster Server 3.5 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 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:

Virtual Server owns Shared Disks.

Installation Guide
76
Figure 4. General Cluster Configuration

Node 1
clus_phys1
Node 2
clus_phys2
Private NetWork
clus_log1
Local Disk
If Node1fails,
clus_log1 fails
over to Node2
Local Disk
Virtual Server

Administrative
Workstation
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.
Cluster-Aware and Cluster-Unaware NetWorker Servers and Clients

To perform scheduled backups of cluster data, a cluster-aware NetWorker server and
cluster-aware NetWorker client on the cluster nodes must be installed.
Note: Not all NetWorker servers and clients are cluster-aware. For example:
If a NetWorker server does not have cluster-client support, it cannot recognize

cluster clients. When a scheduled backup is performed, the NetWorker server
backs up only the private data of the physical node. The data is backed up to the
same index representing the physical node.
If a NetWorker client does not have cluster-client support, it backs up all data that
belongs to the virtual servers and physical nodes into the same index
representing the physical node. It does not recognize the difference between
virtual and physical clients.
For more information, refer to the LEGATO Compatibility Guides on the LEGATO web
site at www.legato.com.

Installation Guide
77
Make sure that the following software is installed on each node in the cluster:
Solaris 7, 8 or 9 operating environment with Veritas Custer Server (VCS) required

patches
VERITAS Cluster Server 3.5
NetWorker release 7.2
VERITAS Volume Manager VxVM 3.5 (optional)
VERITAS File System VxFS 3.5 (optional)
For the most up-to-date information regarding software requirements, refer to the
LEGATO Compatibility Guides on the LEGATO web site.

In this configuration, the NetWorker server is running on a node that is not a member
of the cluster.
To install a NetWorker cluster client, perform the following tasks:

"Task 2: Configure NetWorker Client Software as Highly Available" on page 79
"Task 3: Register the NWClient Resource Type and Create Resource Type
Instances" on page 80
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.

Installation Guide
78
To install NetWorker software on the computer 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 All
response installs the server and the device driver packages.
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).
6. When all the applicable packages have been added, and the prompt appears, press
[q] to exit.
Task 2: Configure NetWorker Client Software as Highly Available

To define and configure a NetWorker client as highly available:
(DNS) or Network Information Services (NIS).
This script creates NWClient resource types that may need to be added later to
the VERITAS Cluster Server configuration.
b. Enter the following information in response to the prompts:
[/nsr]?
client? Yes or No [Yes]?
Enter No. This configures only the client software.
networker.cluster -r option and then running the networker.cluster script
again.

Installation Guide
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.
About NWClient Resources

Before starting the steps in this task, review the information in this section to become
familiar with the structure of an NWClient resource.
The NWClient resource type definition is:
type NWClient (
static str ArgList[] = { IPAddress, Owned_paths }
NameRule = NWClient_ + resource.IPAddress
static str Operations = None
str IPAddress
str Owned_paths[]
)

Installation Guide
80
Table 6 on page 81 describes the required NWClient resource attributes.

Table 6. NWClient Resource Required Attributes
Required Attributes
Type and Dimension
Definition
IPAddress
string, scalar
IP address of the virtual

NetWorker client.
An IP type resource with a
matching Address
attribute must exist in the
service group.
Owned_paths
string, vector
A list of filesystems or raw

devices on a shared
storage device. These
filesystems or raw devices
are owned by the virtual
NetWorker client specified
by the IPAddress attribute.
Example: NWClient Resource Sample Configuration

The following is a sample of a configured NWClient resource:
NWClient nw_helene (
IPAddress="137.69.104.251"
Owned_paths={ "/shared1", "/shared2", "/dev/rdsk/c1t4d0s4" }
)
Register Resource Type and Create Resource Instances

This section describes how to register the NWClient resource and create NWClient
resource instances.
To register the resource type and create resource instances:
1. Save the existing VERITAS Cluster Server configuration and prevent further
changes while main.cf is modified.
haconf -dump -makero
2. Stop VERITAS Cluster Server on all nodes and leave the resources available.
hastop -all -force

Installation Guide
81
3. Make a backup copy of the main.cf file.

cd /etc/VRTSvcs/conf/config
cp main.cf main.cf.orig
4. Copy the NWClient resource definition file that is in the VERITAS Cluster Server
configuration directory.
cp /etc/VRTSvcs/conf/NWClient.cf /etc/VRTSvcs/conf
/config/NWClient.cf
5. Add the NWClient resource type and add NWClient resource type instances by
editing the main.cf file:
a. Add the NWClient resource type definition by adding an include statement to
the main.cf file:
include "NWClient.cf"
b. Add an NWClient resource instance to every service group that contains an IP
type resource and has associated filesystems or raw devices on shared
storage. For more information about a sample NWClient resource type
instance, see "Example: NWClient Resource Sample Configuration" on
page 81.
6. Save and close the file.
7. Verify the syntax of the file, /etc/VRTSvcs/conf/config/main.cf:
hacf -verify config
8. Start the VERITAS Cluster Server engine:
hastart
9. Log in on the remaining nodes in the cluster and start the VERITAS Cluster Server
engine:
hastart
10. Verify the status of all service groups:
hagrp -display

Granting access is controlled by the servers file. For the node that is currently running
the NetWorker server resource group, this file is located in the globally mounted
is authorized to:

Installation Guide
82
stopped:
nsr_shutdown
ps -ef |grep nsr
line, that require access to this client.
the file.
4. Restart the NetWorker daemons:

1. From any node in the cluster, start the NetWorker Administrator program:
server.
menu.
NetWorker server, click on the client name in the Client list. Otherwise, click
Create and enter the name of the physical client for the Name attribute.
root@clus_phys1
menu.
NetWorker server, click on the client name in the Clients list. Otherwise, click

Installation Guide
83
root@clus_phys1
to the NetWorker Administrators Guide.

1. On one node in the cluster, remove all the instances of NWClient resource types and
remove the NWClient type definition from the configuration.
For more information, refer to the hares (1m) and hatype(1m) man pages.
a. Log in as root on the computer from which the software is being removed.
b. Undo all changes to the configuration by running the networker.cluster -r
option.
c. Enter the following command to shut down the NetWorker daemons:
nsr_shutdown
A list of NetWorker daemons to be shut down appears, and you are prompted
whether to continue.
d. Enter the following command to remove:
All the packages:
pkgrm LGTOclnt LGTOman
Only the client package:

pkgrm LGTOclnt
Only the man pages:

pkgrm LGTOman

Installation Guide
84

This section demonstrates the typical responses you would give to the prompts of the
networker.cluster script, assuming the following configuration:

Mount point: /global/nw
networker.cluster
--------------------------------------------------------------Veritas Cluster Server is a high availability product.
Only cluster-aware NetWorker Client is supported in the

cluster.
--------------------------------------------------------------Do you wish to continue? [Yes]?
Shutting down NetWorker services...

[/nsr]? /space2/nsr
Restarting syslog daemon...
Creating /usr/sbin/lcmap file ...

-rwxrwxr-x
1 root
5860 Jul 29 11:56 /usr/sbin/lcmap
Finished creating /usr/sbin/lcmap file.
NetWorker has been successfully cluster-configured.

Installation Guide
85
Chapter 7: Autochanger Installation and

Configuration
This chapter provides information on installing and configuring autochangers. It

includes the following:
"About Autochangers" on page 86

"Supported Vendor-Specific ASC and ASCQ Codes" on page 87
"Autochanger Configuration and Testing" on page 87
"The jbconfig Command Output" on page 91
"Using the op Driver with Optical Devices"
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.

Installation Guide
86
Chapter 7: Autochanger Installation and Configuration
Supported Vendor-Specific ASC and ASCQ Codes

In NetWorker software, the Additional Sense Code (ASC) utility, including its
associated ascdcode and library, translates vendor specific ASC and Additional Sense
Code Qualifier (ASCQ) error messages.
The ASC utility is located in the NetWorker driver package, which is a software
requirement for the storage node and the server package. Requisite software is
installed automatically by default, so if you elect to install the storage node, then the
driver package, and thus the ASC utility, is installed automatically.
Notes:
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
Autochanger Configuration and Testing

This section provides instructions on how to configure and test the device driver
software on a NetWorker server or storage node with an attached autochanger. For
more information on configuring an autochanger, refer to the NetWorker Administrators
Guide.
To use an autochanger for NetWorker storage management, follow the procedures for
these tasks:
"Task 1: Configure the Autochanger" on page 88

"Task 2: Test the Autochanger" on page 91

Installation Guide
87
Task 1: Configure the Autochanger

To configure the autochanger:
1. Make sure the autochanger is connected.
2. Log in as root on the NetWorker server.
3. Enter the inquire command. The inquire command for the Solaris platform is:
/usr/sbin/inquire
The inquire command allows you to verify that the autochanger is attached, and
to determine the following information about the robotics and tape drives:
SCSI address
Vendor and model
Firmware
Device type and pathname
Serial number
Note: If inquire does not display the device pathname, there are several possible
causes:
The computer might need to be rebooted.
The cabling or hardware configuration might be incorrect.
The device driver might not be installed. Contact the vendor to obtain the
driver.
For more information about the inquire command, refer to the inquire(1m) man
page.
4. Run the sjisn command with the SCSI address of the autochanger you want to
configure:
sjisn scsi_address
For supported autochangers, the sjisn command lists the drives, identified by
serial number, in the order that they occur in the autochanger. For example, for the
Exabyte 221L shown previously, enter:
sjisn 4.2.0
The output from sjisn displays the serial number identification of the drives one
by one, as in the following example:
aurora{root}8: sjisn 4.2.0
Serial Number data for 4.2.0 (EXABYTE Exabyte 221L ):
Library:
Serial Number: 99999999
SCSI-3 Device Identifiers:
WWNN:1234567812345678
Drive at element address 82:
ATNN:IBM ULTRIUM-TD1 6811004028
WWNN:502342877745328A

Installation Guide
88
ATNN:IBM ULTRIUM-TD1 6811003960

WWNN:502342877745333C
If the sjisn output does not provide the serial number information, the
autochanger does not support the sjisn command, but you can continue to use
jbconfig to configure the autochanger.
For more information about the sjisn command, refer to the sjisn(1m) man page.
5. Verify that the NetWorker daemons are running by entering one of the following
commands:
ps -ef | grep nsr
ps -aux | grep nsr
If the NetWorker daemons are not running, start them in the following order:
nsrexecd
nsrd
(Optional) nwadmin &
This command launches the NetWorker Administrator program, which should
display the drives if the configuration is completed correctly.
6. Run the jbconfig command:
jbconfig
The program lists the autochanger types that are supported on the platform used.
7. At the prompt, select one of the available options to indicate which type of
autochanger to install. From this point on, the response from jbconfig varies
depending on the number and type of autochangers that are attached, and the
number of drives in the autochanger being configured.
If only one autochanger is attached that matches your choice, jbconfig
automatically displays the autochanger SCSI address and pathname in response to
your selection. If more than one autochanger is attached that matches your choice,
the matching autochangers are listed and you are prompted to select one of them.
As soon as you select an autochanger, jbconfig automatically displays the
autochanger pathname, as shown in the following example:
Installing 'Exabyte' jukebox - scsidev@4.2.0.
8. Enter a name to assign to the autochanger at the jbconfig command prompt. For
example:
What name do you want to assign to this jukebox device? Exabyte
9. Answer whether you want to enable autocleaning.
10. If all drive and pathname information is available, each drive is listed with its SCSI
address and driver pathname. If there are difficulties locating the drives in the
autochanger, a message explains at this point that you will have to supply the
missing information later on.
11. Answer whether you want to configure any of the drives as shared or NDMP
devices.
12. Answer whether any drive is going to have more than one path defined. If all
drives were listed in step 10, jbconfig goes to step 14.

Installation Guide
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:
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:
New Jukebox resource, use the NetWorker Administrator program.

a. If the NetWorker Administrator program is not already running, enter the
command:
nwadmin &
b. From the Media menu, select Jukeboxes.
Attributes of the Jukeboxes resource, refer to the Online Help or the
nsr_jukebox(5) man page.
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
Installation Guide
90
Task 2: Test the Autochanger

To test the autochanger connection:
1. Log in as root on the NetWorker server or storage node.
2. Insert two volumes, one each into the first and last slots of the autochanger. Make
sure that the drives are empty and that any drive doors are open.
3. Enter the jbexercise command at the prompt and specify the control port and the
jukebox model. Make sure to use the same control port pathname that was used in
"Task 1: Configure the Autochanger" on page 88.
For example, the following command runs the jbexercise program on the Exabyte
autochanger detected by the jbconfig script:
jbexercise -c scsidev@4.2.0 -m "EXB-220"
To find the text string for the -m model parameter, run the jbexercise command
without any options to obtain a list of supported models. For additional
information on the command options available for the jbexercise command, refer
to the jbexercise(1m) man page.
Notes:
To list the SCSI devices that are available, use the inquire command. The
control port for SCSI autochangers is typically expressed in the format
scsidev@n.n.n.
To obtain information about a standard SCSI jukebox, run the jbexercise
command with the following options:
jbexercise -m scsidev@n.n.n -c bus.target.lun
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.
The jbconfig Command Output

The following is an example of what would be displayed when installing an
autodetected SCSI jukebox on a Solaris computer. In this case, only one autochanger,
with a single drive, is attached. Output would vary in cases where:
Two or more autochangers are attached

The autochanger has more than one drive
The driver filepath is not detected for one or more drives in an autochanger
Prompts are answered differently than in this example
# jbconfig
1) Configure an AlphaStor/SmartMedia Jukebox.
2) Configure an Autodetected SCSI Jukebox.
3) Configure an Autodetected NDMP SCSI Jukebox.

Installation Guide
91
4) Configure an SJI Jukebox.

5) Configure an STL Silo.
What kind of Jukebox are you configuring? [1] 2

Installing 'HP-C1557A/Surestore 12000e' jukebox - scsidev@1.3.1.
What name do you want to assign to this jukebox device? test

Turn NetWorker auto-cleaning on (yes / no) [yes]? y
The following drive(s) can be auto-configured in this jukebox:

1> 4mm 12GB @ 1.3.0 ==> /dev/rmt/0cbn
These are all the drives that this jukebox has reported.
To change the drive model(s) or configure them as shared or

NDMP drives, you need to bypass auto-configure.
Bypass auto-configure? (yes / no) [no] n
Jukebox has been added successfully
The following configuration options have been set:
> Jukebox description to the control port and model.

> Autochanger control port to the port at which we found it.
> Networker managed tape autocleaning on.
> Barcode reading to off because it does not appear that
this jukebox has a barcode reader.
> Slot intended to hold cleaning cartridge to 6.
Please
ensure that a cleaning cartridge is in that slot.

> Number of times we will use a new cleaning cartridge to 5.
> Cleaning interval for the tape drives to 6 months.
You can review and change the characteristics of the autochanger

and its associated devices using nwadmin.
Would you like to configure another jukebox? (yes/no) [no]n

Installation Guide
92
Using the op Driver with Optical Devices

Solaris support for optical drives is enhanced by the NetWorker optical device driver
op, which enables the use of optical disks with sectors larger than 512 bytes (1,024,
2,048, and 4,096). After NetWorker software is installed, the op driver is used with any
device, attached to the Solaris system, whether a stand-alone device or autochanger,
that claims to be an optical device. On system reboot with the -r option, the op driver
is configured for each optical device, resulting in a device file of the form /dev/opticalN
for each optical drive.
Because HP optical drives can run in either "disk drive" or "optical" mode, any optical
drives running in disk drive mode must be reset to optical mode using the hpflip
utility. Once the HP optical drive is set to optical mode, reboot the system so that the
settings for attached devices are reread.
How to Reset HP Optical Drives

To reset HP optical drives to optical mode:
1. Run the inquire command to obtain the SCSI address of the optical device, which
will be is returned in the form scsidev@b.t.l, where:
b is the bus ID
t is the target ID
l is the logical unit number (LUN) ID
2. Run hpflip as follows:

hpflip -a b.t.l -o
where b.t.l is the SCSI address of the optical device, as returned by the inquire
command, and -o sets the specified drive to optical.
3. Reboot the computer with the -r option as follows, to make the changes performed
by hpflip visible to the operating system:
reboot -dl -- -rv
4. Define all optical devices within NetWorker software as optical devices.

Installation Guide
93
Chapter 8: Evaluating and Licensing NetWorker

Software
When the NetWorker software is installed, it is in a temporary evaluation mode with

all of the features available. This chapter explains how to enable the NetWorker
software and features for permanent use. The chapter also describes the LEGATO
NetWorker licensing model and provides a basic explanation of licensing for the
different NetWorker editions, modules, and features, but it does not provide a
comprehensive description of every possible licensing scenario. For specific licensing
questions, contact a LEGATO sales representative.
The chapter includes the following sections:
"How NetWorker Software Is Licensed" on page 94

"The Evaluation Process" on page 95
"The Licensing Process" on page 96
"NetWorker Licenses" on page 99
"Additional Licenses" on page 101
How NetWorker Software Is Licensed

Licensing NetWorker software means entering 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
which 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, and the server enforces the
licensing.
Base enablers come in four editions:
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.

Installation Guide
94
Chapter 8: Evaluating and Licensing NetWorker Software
The Evaluation Process

Evaluating NetWorker software can take place in two ways:
Evaluating a new installation of the software on a NetWorker server

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 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 using the NetWorker software to back up data. The base enabler is
the license that enables the edition purchased. To obtain a base enabler, contact either
LEGATO Sales or a LEGATO Reseller. For contact information, see "Information and
Services" on page 12. For more information about entering and authorizing the enabler,
see "The Licensing Process" on page 96.
To continue using some of the features that were available with the evaluation
software, you may need to purchase add-on enablers, depending on the edition of base
enabler you purchase. For more information about the different NetWorker editions
and features, see "NetWorker Licenses" on page 99.
Evaluating Features on an Existing Installation

If you are evaluating one or more NetWorker features on an edition of NetWorker
software that has already been installed and enabled, you must enter a temporary
enabler for each feature. The temporary enabler is valid for 45 days.
To obtain a temporary enabler code, refer to the Contents documentation in the

LEGATO media kit, or contact LEGATO Sales or a LEGATO Reseller.
To enter the temporary enabler code, see "How to Enter a Temporary Enabler
Code" on page 96.
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.

Installation Guide
95
How to Enter a Temporary Enabler Code

To enter the temporary enabler code:
1. Log in as root or as NetWorker administrator on the NetWorker server.
nwadmin &
3. From the Server menu, select Registration.
The Registration window opens.
4. Click the Create button.
5. Enter the enabler code in the Enabler Code attribute.
Filling in the Comment attribute is optional.
6. Click Apply.
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.
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 features. To purchase the license
enabler, contact a LEGATO sales representative.
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.
The following sections explain how to enter and authorize the license enabler:
"Task 1: Enter the License Enabler Code" on page 97

"Task 2: Obtain an Authorization Code" on page 97
"Task 3: Enter the Authorization Code" on page 98

Installation Guide
96
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 a number of 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 re-enabled manually after their
licenses were installed.
To enter the license enabler code:
nwadmin &
The Registration window opens.
4. If the Registration list displays a temporary enabler for the product or feature
being licensed, highlight the enabler and click the Delete button.
5. In the Registration window, click the Create button.
6. Enter the enabler code in the Enabler Code attribute.
Filling in the Comment attribute is optional.
7. Click Apply.
After you enter the 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 the following methods:
"Using the LEGATO Web Site"

"By Fax or E-mail"
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.

Installation Guide
97
Using the LEGATO Web Site

Register LEGATO products and obtain authorization codes online by completing a
registration form on the LEGATO web site at www.legato.com. Web registration takes
just a few minutes and is available 24 hours a day, 7 days a week.
An authorization code that permanently enables the NetWorker license will be sent by
e-mail.
If you have any questions regarding software updates, contact LEGATO Licensing. For
contact information, see "Licensing and Registration" on page 13.
By Fax or E-mail
To register the software and obtain an authorization code by fax or e-mail:
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.
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.
To enter the authorization code:
nwadmin &

Installation Guide
98
4. In the Registration window, highlight the appropriate license.

5. In the Auth Code text box, enter the authorization code, and then click Apply.
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 LEGATO Support.
Important: 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, you must either:
Contact LEGATO Licensing to obtain a new authorization code. LEGATO
requires the host ID of the original server as well as the new server. The host ID is
displayed in the servers Registration window.
For contact information, see "Licensing and Registration" on page 13.
Install and configure the LEGATO License Manager software. For more
information on using the License Manager, see "Additional Licenses" on page 101;
also refer to the LEGATO License Manager Installation and Administrator's Guide,
2nd Edition.
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

Installation 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.
Example: Multiplatform Licensing Schemes

A company was using a Solaris server to back up Solaris, Linux, and Windows NT
clients. It needed two ClientPak licenses, one for Linux 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 Windows NT and subsequent Windows
2000 clients without requiring a ClientPak. The company also made the Solaris
computer a NetWorker server to back up the HP-UX, Solaris, and AIX clients, using the
single ClientPak for UNIX.
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.

Installation Guide
100
Required Update Enablers

Table 7 on page 101 lists the NetWorker releases that require update enablers.
Table 7. NetWorker Releases Requiring Update Enablers
Upgrade
from
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
* Release 5.6 is UNIX only, and Release 5.7 is Windows only.
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.
Client Connection Licenses

Every computer to be backed up in a NetWorker data zone requires a client connection
license, even the NetWorker server. The client connection license may be one of the
licenses 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 102 or "NDMP Licensing" on page 102.
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.

Installation Guide
101
LEGATO 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 NetWorker 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. 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.

Installation Guide
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, external
client 71
Legato Automated Availability Manager, options
61
virtual server
Legato Automated Availability Manager
client software 69

Installation Guide
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
61
I
information requirements
inquire command 88
installing
guidelines, server 22
cluster client software 68
virtual server 63
NetWorker 20
requirements
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
Legato License Manager 16

server 15
storage node 15
uninstalling 72
nsr_shutdown command 30, 34
nsr_shutdown daemon 18
nsrck daemon 19
nsrd daemon 28
nsrexecd daemon 28, 30
nsrindexd daemon 28
nsrmmd daemon 28
nsrmmdbd daemon 28
nwadmin command 32
J
jbexercise command
91
L
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

Installation Guide
O
ownership, Legato Automated Availability Manager
virtual client 71
R
requirements
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
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
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
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
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

Installation Guide
105

Legatoinstall 7.2

Загружено:

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

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

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

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

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

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

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

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

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

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

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

Legatoinstall 7.2

Загружено:

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

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

January 11, 2005

5.2 Limited Software Warranty. Subject to the conditions and limitations of

Chapter 1: Introduction.......................................................................................... 14.

Chapter 2: Updating from a Previous NetWorker Release ................................. 17.

Chapter 3: Installing the NetWorker Software .................................................... 20.

LEGATO NetWorker, Release 7.2, Solaris Version

Server Software ..................................................................................................................... 21.

Chapter 4: Installing NetWorker Software in a

LEGATO NetWorker, Release 7.2, Solaris Version

Installing a NetWorker Virtual Server ..................................................................................... 41.

Chapter 5: Installing NetWorker Software in a LEGATO Automated

LEGATO NetWorker, Release 7.2, Solaris Version

Task 1: Install the NetWorker Software in a Cluster .............................................................. 63.

Chapter 6: Installing NetWorker Software in a VERITAS Cluster Server 3.5

LEGATO NetWorker, Release 7.2, Solaris Version

Chapter 7: Autochanger Installation and Configuration..................................... 86.

Chapter 8: Evaluating and Licensing NetWorker Software ................................ 94.

Index ...................................................................................................................... 103.

LEGATO NetWorker, Release 7.2, Solaris Version

LEGATO NetWorker, Release 7.2, Solaris Version

Names of line commands,

The nsradmin command starts the command

Displayed messages are also written to

A variable that must be

Examples and information

media waiting: recover waiting for 8mm

Commands and options that

A path or an order to follow for Volume>Change Mode>Appendable

Information that must be read

LEGATO NetWorker, Release 7.2, Solaris Version

The specifications are created, one for each swap

Important: Use the no_verify option with

Information and Services

Customers with an active support agreement have access to the LEGATO

LEGATO NetWorker, Release 7.2, Solaris Version

Licensing and Registration

(650) 812 6000 (option 3, option 2)a

a. Contact information for the Americas, Asia, and the Pacific.

To comment on a particular guide, complete the Comments form at

LEGATO NetWorker, Release 7.2, Solaris Version

This chapter provides background information on LEGATO NetWorker software and

"About the LEGATO NetWorker Product" on page 14

About the LEGATO NetWorker Product

In a media kit of CD-ROMs that contain the software and electronic

The NetWorker product has these major components:

LEGATO NetWorker, Release 7.2, Solaris Version

NetWorker Storage Node

LEGATO NetWorker, Release 7.2, Solaris Version

LEGATO License Manager

NetWorker Release 7.2, UNIX and Linux Version, Administrators Guide

LEGATO NetWorker, Release 7.2, Solaris Version

Chapter 2: Updating from a Previous NetWorker

Updating from a Previous Release

"Task 1: Prepare to Update the NetWorker Software on the NetWorker Server" on

LEGATO NetWorker, Release 7.2, Solaris Version

Chapter 2: Updating from a Previous NetWorker Release

Task 1: Prepare to Update the NetWorker Software on the NetWorker Server

Task 2: Update the NetWorker Software

Important: Do not start the NetWorker daemons.

5. Apply any required NetWorker software patches.

LEGATO NetWorker, Release 7.2, Solaris Version

Chapter 2: Updating from a Previous NetWorker Release

New Resource Database Replaces nsr.res and nsrjb.res Files