NetWorker Save and Restore for DIGITAL UNIX Version 4.4 AA-Q2H4K-TE Installation Guide Digital Equipment Corporation Maynard, Massachusetts 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. [C] Copyright Digital Equipment Corporation 1997 All rights reserved. The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by DIGITAL or its affiliated companies. The following are trademarks of Digital Equipment Corporation: DEC, DEC 4000, DEC C++, DECchip, DECladebug, DECsystem, DECstation, DECsupport, DIGITAL, OpenVMS, POLYCENTER, ULTRIX, UWS, VAX, VAX DOCUMENT, VMS, the DIGITAL logo. MIPS is a trademark of Mips Computer Systems, Incorporated. Microsoft, MS-DOS, Windows, and Windows NT are registered trademarks of Microsoft Corporation. PostScript is a registered trademark of Adobe Systems, Inc. OSF and OSF/1 are registered trademarks of Open Software Foundation, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. All other trademarks and registered trademarks are the property of their respective holders. Revision/Update Information: This revised manual supersedes the NetWorker Save and Restore for DIGITAL UNIX Installation Guide (Order Number AA-Q2H4J-TE). Operating System and Version: DIGITAL UNIX Version 4.0A or higher. Future maintenance releases may require higher versions. Software Version: NetWorker Version 4.4 Date: November 1997 Order Number: AA-Q2H4K-TE Contents Preface vii Intended Audience vii Structure of This Document vii Manuals in the NetWorker Documentation Set viii Related Manuals viii Conventions ix 1 Preparing for NetWorker Installation 1 Release Notes 1 License Registration1 Installation Procedure Requirements 4 Backing Up Your System Disk 5 Time Required for Installation 5 Login Requirements 5 Hardware Requirements 5 Software Requirements 6 Server Requirements 6 Client Requirements 8 Deleting Old Subsets 9 Determining Which Subsets to Load 10 Disk Space Requirements 11 Ensuring Adequate Disk Space for Online Indexes 12 Stopping the Installation 13 Error Recovery 13 2 Installing the NetWorker Server Software 15 Installing from CD-ROM Consolidated Distribution Media 15 Using a RIS Server 16 Responding to Installation Procedure Prompts 16 Selecting Subsets 17 Loading Subsets Process 18 3 Installing a NetWorker Cluster Server 25 Installation Requirements 25 Software Requirements 25 Hardware Requirements 25 System Information Required 26 Installation Procedures 26 Installation Examples 27 Checking for FIS Installation 27 Registering NetWorker Licenses 28 Installing NetWorker in a Cluster 29 Connecting Storage Devices to the Cluster 33 Defining NetWorker as a Highly Available Application 34 Configuring the NetWorker Cluster Server 43 Migrating a NetWorker Server to a Cluster Server 44 Relocating the NetWorker Service 45 Shutting Down/Restarting the Cluster Server 46 Deinstalling the Cluster Server Subset 46 Reinstalling the Cluster Server Subset 47 Making a Cluster Member a Client of the NetWorker Cluster Server 48 4 Completing the Server Installation 49 Running the Installation Verification Procedure 49 Configuring Server Files 49 Configuring Server Files Manually 50 Creating the /sbin/init.d/nsrd File 50 Configuring the /etc/rpc and /etc/syslog.conf Files 52 Customizing the NetWorker Server 53 Deleting NetWorker from Your System 53 Accessing Release Notes and Documentation 54 5 Installing the Client Software 55 DIGITAL UNIX Client Installation 55 Starting the Client Installation Procedure 56 A Sample Listing for NetWorker Installation 61 NetWorker Server Installation Example 61 DIGITAL UNIX Client Installation Example 65 B Files Installed on Your System 69 Files Installed on Server Systems 69 Files Installed on DIGITAL UNIX Client Systems 74 C Client Installation Worksheet 77 Index 79 iv List of Tables Table 1 Prerequisite Server Software 7 Table 2 Optional Server Software 8 Table 3 Prerequisite Client Software 9 Table 4 Subset Sizes (Kilobytes Required) 11 Table 5 Required Information 26 Table 6 NetWorker Subsets 49 Table 7 Installed NetWorker Files -- Server 69 Table 8 Installed NetWorker Files -- DIGITAL UNIX Client 74 v Preface This guide describes how to install the NetWorker Save and Restore server software on DIGITAL[TM] Alpha processors that are running the DIGITAL UNIX[R] operating system. Additionally, this guide describes how to install the NetWorker client software on DIGITAL UNIX clients. Intended Audience This guide is intended for anyone who installs NetWorker. Structure of This Document This manual is organized as follows: o Chapter 1 describes the software and hardware requirements for installation. It also describes related procedures that you complete before installing NetWorker. o Chapter 2 describes the procedure for installing the NetWorker server software and loading the DIGITAL client subset on the NetWorker server. o Chapter 3 describes the procedure for installing NetWorker as a cluster server in an Available Server Environment (ASE) and configuring a shared tape service. o Chapter 4 describes the Installation Verification Procedure (IVP) and any post-installation procedures that you must complete in order to use NetWorker. o Chapter 5 describes the procedure for installing the DIGITAL client software. o Appendix A contains sample listings for NetWorker installation. o Appendix B describes the hierarchy and contents of NetWorker directories. o Appendix C provides a template for the client installation worksheet. Manuals in the NetWorker Documentation Set In addition to this guide, the NetWorker documentation set includes the following manuals: o NetWorker Save and Restore for DIGITAL UNIX Administrator's Guide o NetWorker Save and Restore for DIGITAL UNIX Addendum o NetWorker Save and Restore for DIGITAL UNIX User's Guide Printable PostScript[R] files for each of these books are available in the optional subset, NetWorker Release Notes and Documentation. The subset identifier is BRXRNOTES440. If you would like printed versions of these books, see the Software Product Description (SPD) for individual part numbers, or you can order the complete documentation set by ordering part number QA-2ALAA-GZ.4.4. Related Manuals The following manuals are part of the base operating system documentation set: o Network Configuration o Network Administration and Problem Solving o Installation Guide o Sharing Software on a Local Area Network o System Administration o User's Guide o TruCluster Available Server Software, ASE Administration o TruCluster Available Server Software, ASE User Guide viii Conventions The following conventions are used in this guide: Convention Meaning UPPERCASE and The DIGITAL UNIX system differentiates between lowercase lowercase and uppercase characters. Literal strings that appear in text, examples, syntax descriptions, and function descriptions must be entered exactly as shown. directory This italic typeface indicates the exact name of a path name, directory, or file. It is also used for manual titles. command This bold typeface is used to indicate the exact name of a command. user input In interactive examples, this bold typeface indicates input entered by the user. User variable In interactive examples, this bold italic typeface indicates variable input determined and entered by the user. System output This typeface is used in code examples and other screen displays. % The percent sign is the default user prompt. # A number sign is the default root user prompt. Ctrl/X In procedures, a sequence such as Ctrl/X indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button. ix Chapter 1 Preparing for NetWorker Installation Before starting the installation procedures in Chapter 2, Installing the NetWorker Server Software, complete the preparation requirements outlined in this chapter. Completing these preparation steps will make your installation run smoothly. Release Notes NetWorker provides online release notes, which are located on your DIGITAL layered product CD-ROM optical disc. DIGITAL strongly recommends that you read the release notes before installing the product. The release notes contain important information about installing and using NetWorker that is not included in this guide or other documentation. The release notes are available in both PostScript and text versions, which you can display or print from the CD-ROM distribution disc after it is mounted. Note that you can access the release notes before installing NetWorker. The PostScript file is titled brx440_relnotes.ps and the text file is brx440_relnotes.txt. For instructions on how to locate the release notes online and print them from the CD-ROM distribution disc, see the Software Product Library CD-ROM User's Guide. The copies of the release notes are included in the software kit in their own subset, and are located in the directory /usr/opt/BRX440/usr/doc after you install the release notes subset. The release notes are, therefore, accessible from the product directory after the CD-ROM distribution disc is unmounted. License Registration NetWorker includes support for the DIGITAL UNIX License Management Facility (LMF). A NetWorker License Product Authorization Key (License PAK) must be registered in the License Database (LDB) in order to use NetWorker. The License PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. If you are installing NetWorker as an update on a node already licensed for this software, you have already completed the License PAK registration requirements. If you are installing prerequisite or optional software along with NetWorker, review the PAK status and install the PAKs for any prerequisite or optional software before you install NetWorker. Because NetWorker software consists of both client and server software, you might have more than one license PAK to register. There are several types of license PAKs for NetWorker: o DECNSR-CLUST-SRV o DECNSR-NET-SVR o DECNSR-SRV-ARCH o DECNSR-SRV-HSM o DECNSR-SSC-SVR o DECNSR-NET-CLNT o DECNSR-PC-CLNT o DECNSR-CLUST-CLNT1, DECNSR-CLUST-CLNT2, and DECNSR-CLUST-CLNT3 o JUKEBOX-TIER-1, JUKEBOX-TIER-2, and JUKEBOX-TIER-3 o DECNSR-SVR-SQL o DECNSR-SVR-EXCH The number and type of license PAKs that you must register depends on your backup configuration. Register the appropriate license PAKs in the following ways. Note that for the following license PAKs, registrations must be performed on a NetWorker server and not on the clients: o A DECNSR-NET-SVR PAK for each NetWorker server. In addition, you must register the optional add-on PAKs: - DECNSR-SRV-ARCH PAK to use the archiving feature. - DECNSR-SRV-HSM PAK to use the HSM feature. - DECNSR-SSC-SVR PAK to use the save set consolidation feature. 2 Preparing for NetWorker Installation - DECNSR-SVR-SQL to back up Windows NT@ SQL clients. - DECNSR-SVR-EXCH to enable the server to back up Microsoft Exchange clients. o A DECNSR-CLUST-SVR PAK on each cluster member in an ASE if NetWorker is to run as a cluster server. In addition, the following PAKs must also be installed on each cluster member. Note that the purchase of only one set of server licenses is required in a cluster environment. See the SPD for additional information on cluster licensing. - DECNSR-NET-SRV PAK - DECNSR-CLUST-CLNT1/2/3 PAKs - PAKs for any optional features - Appropriate number and type of client PAKs o A DECNSR-NET-CLNT PAK for each NetWorker non-PC client connection on the network. Archive and HSM clients must be licensed separately from backup clients. For example, if there are 10 backup clients and each of those clients will also function as an archive client, then 20 client licenses are required. o A DECNSR-PC-CLNT PAK for each NetWorker PC on the network. Note that SQL and Exchange clients must be licensed separately. For example, if you have 10 SQL PC backup clients and also want to back up Microsoft Exchange on each PC, 20 PC client licenses are required. o A DECNSR-CLUST-CLNTn PAK, available in three tiers, is required for each cluster host. - DECNSR-CLUST-CLNT1 -- For a workgroup - DECNSR-CLUST-CLNT2 -- For a departmental - DECNSR-CLUST-CLNT3 -- For the enterprise See the Software Product Description (SPD) for detailed information on which license PAKs to purchase. The client resources associated with ASE services do not require an additional license, as they are included in the cluster client license. The cluster client license also contains both a client archive and HSM license. Therefore, if you have a DECNSR-CLUST-CLNTn license, an additional DECNSR-NET-CLNT license is not needed to perform archiving or HSM on a cluster client. (The DECNSR-SRV-ARCH license is still required on the NetWorker server to perform archiving and the DECNSR-SRV-HSM license is required on the NetWorker server to perform HSM.) Preparing for NetWorker Installation 3 o If you have one or more jukeboxes in your NetWorker configuration, you must register the appropriate JUKEBOX-TIER license PAKs. See the Software Product Description (SPD) for information on which jukebox license to register. To register a license under the DIGITAL UNIX system, first log in as root user. Edit an empty PAK template with the lmf register command and include all the information on your License PAK. After you register your license, use the lmf reset command to copy the license details from the License Database (LDB) to the kernel cache. For complete information on using the DIGITAL UNIX License Management Facility, see DIGITAL UNIX Software License Management or the lmf(8) reference page. The following information may aid in understanding NetWorker licensing policies: o Client, jukebox, and cluster client licenses are assigned to the defined resources in the order in which the server reads them from the resource database (/nsr/res/nsr.res) at NetWorker startup. o Defined clients that are unable to obtain a connection license at server startup will be allowed to browse and recover previously saved data, but will be unable to perform any backups. o NetWorker cluster server installations in an ASE require the purchase of only one set of server licenses. These licenses can then be installed on each cluster member in the ASE. o The number of cluster client licenses to purchase should be one less than the number of cluster servers. o Cluster clients do not require an archive license. The ability to perform archive operations is included in the cluster client license. o For tiered licenses (jukebox and cluster client licenses), if no units of the correct tier license are available for use, the next higher tier license will be used, if available. This continues until all available tiers are searched. In addition, a PC client can use a workstation connection license if there are no units of PC licenses available. Installation Procedure Requirements This section discusses various requirements for installing NetWorker. 4 Preparing for NetWorker Installation Backing Up Your System Disk Back up your system disk before installing any software. For details on performing a system disk backup, see your DIGITAL UNIX documentation. Time Required for Installation Installing the NetWorker server software and running the Installation Verification Procedure (IVP) on your DIGITAL UNIX Alpha system requires 10 to 20 minutes. In addition, each optional subset requires approximately 5 minutes. After loading the NetWorker DIGITAL UNIX Client subset on the server, you will need approximately 10 minutes to install the client software on each client system. Login Requirements You must be able to log in as root user on the system where you are installing NetWorker. Only the root user has sufficient privileges to install the NetWorker software. Hardware Requirements To install NetWorker, you need the following hardware: o Software distribution device (if installing from media) Locate the CD-ROM drive for the CD-ROM software distribution media. The CD booklet or the documentation for the CD-ROM drive you are using explains how to load the CD-ROM media. o Terminal You can use either a hardcopy or video terminal to communicate with the operating system and respond to prompts from the installation procedure. o Network connection You need a hardware network connection between the NetWorker server and NetWorker client systems. See the NetWorker Software Product Description (SPD) for additional hardware requirements. Preparing for NetWorker Installation 5 Software Requirements The following sections list and describe the required software for installing NetWorker on server and client systems. Server Requirements NetWorker Version 4.4 requires the following operating system: DIGITAL UNIX Version 4.0A or higher. Table 1 provides information on the minimum software you must have installed on your system before installing NetWorker. Table 2 provides information about optional software that you can use together with NetWorker. The NetWorker SPD contains a complete list of prerequisite and optional software and their required version numbers. 6 Preparing for NetWorker Installation Table 1 Prerequisite Server Software Subset Subset Name Description Identifier OSFBASE405 DIGITAL UNIX Base operating system software. Base System OSFCLINET405 Basic Network server communications. Networking Services OSFNFS405 NFS Utilities Network server communications. OSFPRINT405 Local Printer This software is needed to print Support the bootstrap file and to print (Printing information from NetWorker Environment) windows that display in tabular format. Preparing for NetWorker Installation 7 Table 2 Optional Server Software Subset Subset Name Description Identifier OSFMANOS405 Ref Pages Reference pages for the base (Admin/User operating system. This software is Reference needed in order to view the Pages) NetWorker reference pages. CLCMC312 SCSI CAM Media Device driver required if you have Changer Driver a jukebox with a SCSI interface control port. Check the SCSI CAM Layered Components Product Description for information on which version of the software to install. CLCOP312 SCSI CAM Device driver required if you have Optical Driver an optical jukebox with a SCSI interface control port. Check the SCSI CAM Layered Components Product Description for information on which version of the software to install. Perform the following steps to determine whether the required subsets are loaded: 1. Log in to the system where you will install NetWorker. 2. Enter the following command: # /usr/sbin/seld -i | grep SUBSET_IDENTIFIER Check the displayed rows for the name of the relevant subset and any patches. Note that SUBSET_IDENTIFIER is the subset name listed in Table 1 or Table 2. The word installed appears in a row after the subset identifier when a subset is loaded. If the word installed does not appear (the second column in a row is blank), the subset or patch is not loaded. In this case, you must load the missing DIGITAL UNIX software before installing NetWorker. Client Requirements DIGITAL UNIX Version 4.0A or higher (DIGITAL UNIX client) is required to install the NetWorker client software on DIGITAL clients. Table 3 provides information on the minimum software you must have installed on your system before installing NetWorker DIGITAL client software. 8 Preparing for NetWorker Installation Table 3 Prerequisite Client Software Subset Subset Name Description Identifier OSFBASE405 DIGITAL UNIX Base operating system software. Base System OSFCLINET405 Basic Network server communications. Networking Services OSFNFS405 NFS Utilities Network server communications. Deleting Old Subsets Before you can install any of the NetWorker Version 4.4 subsets, you must first delete any older versions of those subsets. Note If you are upgrading from NetWorker version 3.2A or earlier to NetWorker version 4.4, the NetWorker index will be converted to a new format when NetWorker is restarted. Before deleting the old subsets, issue the nsrck -F command. This command performs an index consistency check and places the index files in a clean and consistent state. To delete outdated subsets from the NetWorker server, do the following: 1. If you have jukeboxes in your configuration, use the nsrjb -u command to unmount all volumes from all jukebox drawers. Failing to unmount volumes before deleting old subsets can cause serious problems when you start the new version of NetWorker. See the Addendum for details. 2. Log in as root user on the NetWorker server. 3. Using the setld -i command, list the subsets installed on the NetWorker server and check for the presence of any subset with a name that starts with BRX, ends with 220, 221, 222, 300, 310, 311, 320, 321, 421, 422, 423, or 430 and includes the word installed. # setld -i | grep BRX 4. Using the setld -d command, delete the old BRX subsets from the NetWorker server. For example: # setld -d BRXSOAKIT422 Preparing for NetWorker Installation 9 Repeat this step for each outdated NetWorker subset. Warning During the deletion of the old subsets, you are asked if you want to delete the /nsr directory and the indexes. Answer "no" to these questions. If the indexes are inadvertently deleted, they can be recovered from your NetWorker media using the mmrecov and recover commands. Determining Which Subsets to Load You must choose the NetWorker subsets you want to load. The NetWorker subsets have the following titles: o NetWorker Release Notes and Documentation This subset contains the NetWorker release notes and PostScript versions of the NetWorker documentation. This is an optional subset. Its identifier is BRXRNOTES440. o NetWorker Server for DIGITAL UNIX This is NetWorker server software and is a required subset for all NetWorker server systems running DIGITAL UNIX Version 4.0A or higher. Its identifier is BRXSOAKIT440 for DIGITAL Alpha systems. o NetWorker DIGITAL UNIX Client This is NetWorker DIGITAL client software and is a required subset for DIGITAL UNIX Alpha client systems. Its identifier is BRXCKIT440. o NetWorker Server Reference Pages The Server Reference Page subset is an optional subset. Its identifier is BRXSMAN440. You can load the NetWorker Server Reference Page subset only if the DIGITAL UNIX Admin Reference Pages subset is already loaded on your NetWorker server. If users on the system where NetWorker is being installed use reference pages that are NFS mounted from another system, load the NetWorker reference pages on the other system rather than the one where you are currently installing NetWorker. In this case, do not request the reference page subset during this installation of NetWorker. After the installation is complete, you can log in to the system where the DIGITAL UNIX reference pages are installed and load only the NetWorker reference page subset on that system. See the setld(8) reference page for information about loading specific subsets. 10 Preparing for NetWorker Installation Disk Space Requirements Table 4 lists the disk space requirements for loading NetWorker software subsets. Table 4 Subset Sizes (Kilobytes Required) Server Subset /usr/opt /usr/bin /tmp /nsr NetWorker Server 43000 5 100 5000 for DIGITAL UNIX BRXSOAKIT440 Client Subset /usr/opt* /usr/bin** /usr/tmp** /usr/man** NetWorker DIGITAL 24120 24120 24120 250 UNIX Client BRXCKIT440 NetWorker Reference Pages /usr/opt* /usr/man NetWorker Reference Pages 704 5 BRXSMAN440 Documentation /usr/opt* Subset NetWorker Release 9316 Notes and Documentation BRXRNOTES440 * Disk space on NetWorker server ** Disk space on client Compare the space required for subsets with the free space currently on the disks where NetWorker files will reside. You can check which filesystems are mounted and where they are by logging in to the system where you plan to install NetWorker and displaying the /etc/fstab file. # more /etc/fstab /dev/rz0a / ufs rw 1 1 /dev/rz0g /usr ufs rw 1 2 /dev/rz1c /var ufs rw a 2 /usr/staff/r1/leslie@bigsys /usr/staff/r1/leslie nfs rw,bg 0 0 /usr/man@bigsys /usr/man nfs ro,bg 0 0 Preparing for NetWorker Installation 11 The previous display indicates that /usr (mounted to /dev/rz0g) is the only mount point that affects where NetWorker files will reside; the system has only one local disk drive and the /usr/opt filesystem resides in the g partition of the disk on that drive. Enter the df -k command to determine total space and free space for the filesystem where NetWorker files will reside. Given the previous display of the /etc/fstab file, the free space in the /usr filesystem is checked as follows: # df -k /usr Filesystem kbytes used avail capacity Mounted on /dev/rz0g 628561 455041 110663 80% /usr This display indicates that there are 110663 kilobytes free on /usr. This free space must accommodate subset requirements listed in Table 4 for the /usr/opt filesystem. On systems where /usr/opt is mounted to a different device, enter the following command: # df -k /usr/opt In this case, you compare space required for NetWorker files in /usr/opt to the free space displayed in the df output list. Ensuring Adequate Disk Space for Online Indexes The NetWorker installation procedure creates the /nsr directory and loads files into subordinate directories. If the /nsr directory does not exist, the installation procedure creates it. If the /nsr directory does exist, the installation procedure uses it. The /nsr directory contains the online volume and file indexes. The online file index stores information about the files backed up by NetWorker. The online volume index maps the backup files to volumes. The size of these online indexes grows as the number of clients and the amount of data to be backed up increases. The size of the indexes is also affected by the daily backup schedule. For example, daily full backups cause the online indexes to consume considerably more disk space than daily incremental backups. To ensure that the /nsr directory provides enough disk space for the online indexes, DIGITAL recommends that /nsr be installed as a symbolic link to a directory where a free disk partition or disk is mounted. By default, /nsr is set as a symbolic link to /var/nsr, which usually contains more free disk space than the root (/) partition. 12 Preparing for NetWorker Installation For information on managing the online indexes, see the NetWorker Save and Restore for DIGITAL UNIX Administrator's Guide. Stopping the Installation You can stop the installation procedure any time by pressing Ctrl/C. Files created up to this point, however, are not deleted automatically. Delete these files interactively, if you wish. Appendix B, Files Installed on Your System, on page 69, lists the files and directories created during the installation procedure. Error Recovery If errors occur during the installation, the system displays messages. Installation errors can occur if any of the following conditions exist: o The operating system version is incorrect o The prerequisite software version is incorrect o The system parameter values for successful installation are insufficient. If the installation fails due to insufficient disk space, the following message appears: There is not enough file system space for subset BRXSOAKIT440 NetWorker Server for DIGITAL UNIX (BRXSOAKIT440) will not be loaded. For descriptions of error messages generated by these conditions, see the DIGITAL UNIX documentation on system messages, recovery procedures, and DIGITAL UNIX software installation. For information on system software requirements, see the Software Requirements section on page 7 in this chapter. If an error occurs while using NetWorker and you believe the error is caused by a problem with the product, take one of the following actions: o If you have a basic or DECsupport[TM] Software Agreement, call your Customer Support Center (CSC). The CSC provides telephone support for high-level advisory and remedial assistance. o If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). Preparing for NetWorker Installation 13 o If you purchased NetWorker within the last 90 days and you think the problem is caused by a software error, you can submit an SPR. When you report an error, be sure to provide ample background information. Concise, complete information helps DIGITAL give accurate and timely service to software problems. If you find an error in the NetWorker documentation, refer to the How Did We Do? page at the back of the document containing the error. 14 Preparing for NetWorker Installation Chapter 2 Installing the NetWorker Server Software This chapter describes the procedure for installing the NetWorker server software and loading the DIGITAL client subset on the NetWorker server. Before starting the installation, read Chapter 1, Preparing for NetWorker Installation, which describes general options and requirements for installing the product. Note If you are installing NetWorker as a cluster server in an ASE, follow the installation instructions provided in Chapter 3, Installing a NetWorker Cluster Server. Installing NetWorker into a network configuration is a two-step procedure: 1. Install NetWorker server software and load NetWorker client software on the server system. 2. Install NetWorker client software on each client system. The installation procedure loads NetWorker files onto the disks that belong to the system where you perform the installation. When NetWorker is run, its executable files are mapped into memory on the same system. If you need to stop the installation, or if an error occurs, see Stopping the Installation, page 13, or Error Recovery, page 13, in Chapter 1. Installing from CD-ROM Consolidated Distribution Media Start the installation procedure as follows: 1. Load the media on the appropriate disk drive. 2. Mount the distribution media by entering the following command. This command example shows how to mount read-only the CD-ROM device /dev/rz4c on the /mnt mount point: # mount -rd /dev/rz4c /mnt 3. If you have not already read the release notes, please read them now, before beginning the setld installation procedure. The release notes are located on the CD-ROM distribution disc and can be accessed once the CD-ROM is mounted. See Release Notes in Chapter 1 for information about accessing the release notes. 4. Enter a setld command that specifies the load function (-l) and identifies the directory in the mounted filesystem where NetWorker subsets are located. For example, if the directory location for these subsets is /mnt/brx440/kit, enter the following command: # setld -l /mnt/brx440/kit See page 16 to continue the installation. Using a RIS Server To install NetWorker from a Remote Installation Services (RIS) server to a RIS client, the NetWorker software must first be installed in your RIS server environment. If you have not already obtained and read the release notes, see your RIS manager for information about obtaining them. Please read the release notes before beginning the installation procedure. Also, see your RIS manager if NetWorker is not already installed on the RIS server. To install the NetWorker subsets from the distribution area of a RIS server system, enter a setld command that specifies the load function (-l) and identifies the directory in the mounted filesystem where NetWorker subsets are located. For example, if you are loading NetWorker subsets from a RIS distribution area on node bigsys, enter the following command: # setld -l bigsys: See the next section to continue the installation. Responding to Installation Procedure Prompts This section explains the installation procedure prompts and displays. 16 Installing the NetWorker Server Software Selecting Subsets After you enter the setld command, the installation procedure displays the names of the NetWorker subsets and asks you to specify the subsets that you want to load: The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) NetWorker DIGITAL UNIX Client 2) NetWorker Release Notes and Documentation 3) NetWorker Server Reference Pages 4) NetWorker Server for DIGITAL UNIX Or you may choose one of the following options: 5) ALL of the Above 6) CANCEL selections and redisplay menus 7) EXIT without installing subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 5 If you specify more than one number at the prompt, separate each number with a space, not a comma. Note that when you install subsets from a particular RIS server area, the menu displays each software subset available in that RIS area. If NetWorker subsets are available in a RIS area that includes other software subsets, then all the subsets are displayed. Consequently, the subset menu item may vary depending on what products are installed in the RIS server area. Next, the script lets you verify your choice. For example, if you enter 5 in response to the previous prompt, you will see the following display: You are installing the following subsets: NetWorker DIGITAL UNIX Client NetWorker Release Notes and Documentation NetWorker Server Reference Pages NetWorker Server for DIGITAL UNIX Is this correct? (y/n): If the displayed subsets are not the ones you intended to choose, enter n. In this case, the subset selection menu is again displayed, and you can correct your choice of optional subsets. Installing the NetWorker Server Software 17 If the displayed subsets are the ones you want to load, enter y. Loading Subsets Process After you have selected the appropriate subsets, the installation procedure does the following: 1. Displays a message that the installation is starting: Checking file system space required to install selected subsets: File system space checked OK. 4 subset(s) will be installed. Loading 1 of 4 subset(s)... This subset will take 5 minutes to complete. NetWorker Server for DIGITAL UNIX Copying from . (disk) Working....Tue Mar 18 10:06:19 PDT 1997 Verifying Loading 2 of 4 subset(s)... This subset will take 5 minutes to complete. NetWorker Server Reference Pages Copying from . (disk) Verifying Loading 3 of 4 subset(s)... This subset will take 5 minutes to complete NetWorker DIGITAL UNIX Client Copying from . (disk) Working....Tue Mar 18 10:06:19 PDT 1997 Verifying Loading 4 of 4 subset(s)... This subset will take 5 minutes to complete NetWorker Release Notes and Documentation Copying from . (disk) Working....Tue Mar 18 10:06:19 PDT 1997 Verifying 4 of 4 subset(s) installed successfully. Configuring "NetWorker Server for DIGITAL UNIX" (BRXSOAKIT440) 18 Installing the NetWorker Server Software NetWorker Save and Restore Version 4.4 Copyright Digital Equipment Corporation 1991, 1997. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use or copying of this software and media is authorized only pursuant to a valid license from Digital or an authorized sublicensor. 2. Warns you that you currently have a loader resource defined. Starting with NetWorker version 4.3, loaders are no longer supported. You will need to redefine the device as a jukebox, if possible. See the SPD for details about the type of license required for your redefined loader. ************************************************************* This NetWorker server has a loader resource currently defined. Starting with NetWorker V4.3, use of a sequential loader/stacker is no longer supported. If you choose to continue with the installation, the installation will remove the loader resources. You will then need to redefine this device as a jukebox. You may need to purchase a corresponding jukebox license. See the SPD for information. Some sequential loaders/stackers cannot be used as jukeboxes. Please consult the device documentation. To continue the installation,type n in response to the following query, or ? for more information. ************************************************************* Do you wish to stop the installation now? [Y]: ? a. If you enter a question mark at the prompt, the following additional information is displayed: ********************************************************** If you upgrade to NetWorker V4.4 without first installing the jukebox license, you will not be able to use your jukebox, except as a standalone device. Once you install NetWorker V4.4, you will not be able to easily revert to your earlier NetWorker version in order to regain loader functionality, because NetWorker V4.4 converts your server and client online indexes to a new format which is incompatible with earlier versions of NetWorker. Installing the NetWorker Server Software 19 See the NetWorker V4.4 Software Product Description (SPD) for part numbers and ordering information. For information on license installation, see the NetWorker Installation Guide. ********************************************************** Do you wish to stop the installation now? [Y]: y b. If you decide to stop the installation, the following information is displayed: ********************************************************** Once you have installed the jukebox license, you may complete the NetWorker server installation by invoking setld as follows: #setld -c BRXSOAKIT440 install Or, you can use the setld -d command to delete this subset, and reinstall your earlier version of NetWorker. ********************************************************** c. If you want to continue with the installation, continue with the next step. 3. Prompts you for the name of the NetWorker home directory, which is the directory to which you want the /nsr directory to be symbolically linked: Enter location for the NetWorker home directory [ /var/nsr ]: By default, NetWorker links the /nsr directory to /var/nsr. For more information on the /nsr directory, see Ensuring Adequate Disk Space for Online Indexes on page 12. 4. Displays a message indicating that specific files will be modified: The installation procedure adds entries to the /etc/rpc and /etc/syslog.conf files on the NetWorker server; the original files are renamed and saved. The installation also creates the /sbin/init.d/nsrd file. Do you wish to continue? (y/n) [ y ] : The /etc/rpc and /etc/syslog.conf files on the NetWorker server must be modified before you can use NetWorker software. The installation script can modify these files for you, or you can perform this task manually. If you do not want the installation to modify NetWorker server files now, enter n. See Configuring Server Files Manually on page 50 for the procedure to manually configure NetWorker server files. 20 Installing the NetWorker Server Software 5. If you enter y, modifies the server files and automatically creates a copy of each original file. In addition, the procedure checks the /etc/hosts file for an nsrhost alias name. If it does not find this alias, it issues a warning message. If you get this warning, see Configuring Server Files on page 49. 6. Asks whether you want to remove the original (saved) files: Do you wish to remove the saved files? (y/n) [ n ] : To remove the original files, enter y. If you enter n, the procedure displays the new location of each original system file. The modified files were saved and renamed as follows: File Location of saved file /etc/rpc /etc/rpc_nsrsave /etc/syslog.conf /etc/syslog.conf_nsrsave Creating /sbin/init.d/nsrd Starting nsrd... 7. Displays a message indicating that if this server will be backed up as a client of a remote server or used as an HSM client, you must run the specified script. *********************************************************** If this system is to be backed up as the client of a remote NetWorker server or is used as an HSM client, you must run the script, /bin/nsrexecd.sh. This script will place the remote server's name in the file /nsr/res/servers, which is the list of NetWorker servers recognized by the local nsrexecd process as legitimate backup servers. ************************************************************ 8. Displays messages indicating that the selected subsets were installed successfully: NetWorker icon has been successfully installed into CDE. /usr/lib/X11/app-defaults/Networker file exists. Do you wish to overwrite this file? (y/n) [n]: BRXSOAKIT440 software installed successfully Configuring "NetWorker Server Reference Pages" (BRXSMAN440) NetWorker Save and Restore Version 4.4 Installing the NetWorker Server Software 21 Copyright Digital Equipment Corporation 1991, 1997. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use or copying of this software and media is authorized only pursuant to a valid license from Digital or an authorized sublicensor. BRXSMAN440 software installed successfully. Configuring "NetWorker DIGITAL UNIX Client" (BRXCKIT440) NetWorker Save and Restore Version 4.4 Copyright Digital Equipment Corporation 1991, 1997. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use or copying of this software and media is authorized only pursuant to a valid license from Digital or an authorized sublicensor. BRXCKIT440 software installed successfully Configuring "NetWorker Release Notes and Documentation" (BRXRNOTES440) NetWorker Save and Restore Version 4.4 Copyright Digital Equipment Corporation 1991, 1997. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use or copying of this software and media is authorized only pursuant to a valid license from Digital or an authorized sublicensor. 22 Installing the NetWorker Server Software BRXRNOTES440 software installed successfully Installing the NetWorker Server Software 23 Chapter 3 Installing a NetWorker Cluster Server NetWorker can be used for backup in a DIGITAL TruCluster Available Server Environment (ASE). By installing NetWorker as a highly available application on each node in an ASE, NetWorker will fail over (relocate) with the cluster server. In an ASE, NetWorker will recognize a cluster environment during installation and allow you to install NetWorker as either a cluster server or as a designated server. If NetWorker is to run as a cluster server, you must install NetWorker as a cluster server on each cluster member in the ASE. Installation Requirements Chapter 1 of this manual describes the software and hardware requirements for installing NetWorker. This section discusses the additional software and hardware requirements for setting up NetWorker as a highly available application in an ASE. Software Requirements In addition to the requirements presented in the Software Requirements section starting on page 7, you must have all of the following software on each cluster member to install NetWorker as a cluster server: o DIGITAL UNIX Version 4.0D o DIGITAL TruCluster Version 1.5 o NetWorker Version 4.4 Hardware Requirements In addition to the requirements presented in the Hardware Requirements section on page 5, you must have the following hardware configuration to install NetWorker on a cluster member server: o Cluster system running DIGITAL UNIX Version 4.0D and TruCluster Version 1.5 on each cluster member. o Dedicated disk to be used as the NetWorker storage disk (for the /nsr directory) connected to a cluster shared bus. o Shared tape device(s). See the SPD for a list of supported shared tape devices. System Information Required The following table identifies the information you will need to set up NetWorker on a cluster server member. Table 5 Required Information Information Required Example Tape service name with IP address goofy, 16.64.96.31t in the same subnet as the cluster members Tape service mount point /goofy Tape service media changer (if /dev/mc131 required)* Tape service one or more devices /dev/nrmt1h, /dev/nrmt2h Tape service storage disk /dev/rz130g Tape service start action script* /bin/NetWorker.start Tape service stop action script* /bin/NetWorker.stop *Note The tape service media changer requires the installation of CLC312. The action scripts are installed on /bin by NetWorker during the installation configuration. Installation Procedures This section identifies the procedures for setting up and installing NetWorker as a highly available application in an ASE. The steps required include the following: o Check for FIS installation o Register server and client licenses 26 Installing a NetWorker Cluster Server o Install NetWorker o Connect the storage devices to the cluster o Define NetWorker as a highly available application o Configure the NetWorker cluster server Installation Examples In the sections that follow, examples of commands and input are provided. To clarify the procedures, the following sample configuration is used throughout the examples: o Two cluster nodes: - pluto: IP address 16.64.96.28 - donald: IP address: 16.64.96.30 o NetWorker tape service: - goofy: IP address 16.64.96.31 o Shared bus: 16 o Shared tape device: - TL810 connected to the shared bus o Media changer: SCSI ID #3 o Four devices on SCSI ID: numbers: 0, 1, 4, 5 o Storage disk on shared bus: SCSI ID #2 Checking for FIS Installation NetWorker may have been installed on your system at the factory. A factory installed system (FIS) would not be configured for a cluster environment. To determine if you have an FIS installation, check for the /usr/opt/BRX440/BRXSOAKIT440/fis.file. If this file exists on any of the cluster members, then NetWorker 4.4 was installed on that system by using the FIS installation process. If the fis.file file exists, issue the setld -d command to delete the NetWorker 4.4 server subset: # setld -d BRXSOAKIT440 Then, reinstall the NetWorker 4.4 server subset from your media distribution. Installing a NetWorker Cluster Server 27 Registering NetWorker Licenses In a cluster environment, you must install the NetWorker Server license, the NetWorker Cluster Server license, and the corresponding cluster client license on each cluster member that will run NetWorker. Refer to the License Registration section on page 1 for additional information on the licenses available. 28 Installing a NetWorker Cluster Server Installing NetWorker in a Cluster Installing NetWorker in a cluster environment is basically the same as installing in a non-cluster environment, except that when you install NetWorker on a cluster server, NetWorker will give you the option to install NetWorker 4.4 as a NetWorker cluster server if it detects that your system is running the proper software. If you choose to install the NetWorker server as a cluster server, you must install the NetWorker 4.4 software on each cluster member in the same ASE_ID number where the NetWorker server is to run. Follow these steps to install NetWorker: 1. Make sure the local /nsr directory is created on a local disk. 2. Refer to the section on page 15 or the Using a RIS Server section on page 16 for information on mounting media and issuing the setld command. 3. Refer to the Selecting Subsets and Loading Subsets Process sections beginning on page 17 for information on choosing and loading the subsets. 4. During the installation, the following additional message is displayed in an ASE: ********** File Configuration on NetWorker Server ********** ************************************************************* This system has the cluster software installed. If this system is to run as a member of a NetWorker cluster server, make sure that ase is running. The installation will create this member local home directory. ************************************************************* Is this system a member of a NetWorker cluster server? [ y ]: /nsr not found! Enter the location for this cluster member NetWorker home directory (it must sit on a local disk!) [ /var/nsr ]: Installing a NetWorker Cluster Server 29 5. If you want NetWorker to run as a cluster server, respond y to the first query and provide a location for the NetWorker home directory. The following is an example of the installation script. Note that, except for the nsrexecd daemon, the NetWorker server daemons will not start at the conclusion of the installation procedure. root@pluto[1]> setld -l /kits/BRX440 The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) NetWorker DIGITAL UNIX Client 2) NetWorker Release Notes and Documentation 3) NetWorker Server Reference Pages 4) NetWorker Server for DIGITAL UNIX Or you may choose one of the following options: 5) ALL of the above 6) CANCEL selections and redisplay menus 7) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 4 You are installing the following optional subsets: NetWorker Server for DIGITAL UNIX Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. 1 subset(s) will be installed. Loading 1 of 1 subset(s).... This subset will take 5 minutes to complete. NetWorker Server for DIGITAL UNIX Copying from /kits/BRX440/output.Jun4 (disk) Working....Thu Jun 5 08:03:03 PDT 1997 Verifying 30 Installing a NetWorker Cluster Server 1 of 1 subset(s) installed successfully. Configuring "NetWorker Server for DIGITAL UNIX" (BRXSOAKIT440) NetWorker Save and Restore Version V4.4 Copyright Digital Equipment Corporation 1991, 1997. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use or copying of this software and media is authorized only pursuant to a valid license from Digital or an authorized sublicensor. *********** File Configuration on NetWorker Server ********** ************************************************************* This system has the cluster software installed. If this system is to run as a member of a NetWorker cluster server, make sure that ase is running. The installation will create this member local home directory. ************************************************************* Is this system a member of a NetWorker cluster server? [ y ]: ? ************************************************************* The NetWorker installation procedure has detected that TruCluster v1.5 is installed on system pluto.zso.dec.com. If this system is to run as a member of a NetWorker cluster server, type y to this query. Follow the instructions at the end of this installation to configure your cluster system with a NetWorker service. ************************************************************* Is this system a member of a NetWorker cluster server? [ y ]: /nsr not found! Enter the location for this cluster member NetWorker home directory (it must sit on a local disk!) [ /var/nsr ]: The installation procedure adds entries to the /etc/rpc and /etc/syslog.conf files on the NetWorker server; the original files are renamed and saved. The installation also creates the /sbin/init.d/nsrd file. Installing a NetWorker Cluster Server 31 Do you wish to continue? (y/n) [ y ]: Modifying /etc/rpc Modifying /etc/syslog.conf * * * Restarting syslog daemon * * * Do you wish to remove the saved files? (y/n) [ n ]: The modified files were saved and renamed as follows: File Location of saved file /etc/rpc /etc/rpc_nsrsave /etc/syslog.conf /etc/syslog.conf_nsrsave Creating /sbin/init.d/nsrd Starting nsrexecd... ************************************************************* If this system is to be backed up as the client of a remote NetWorker server or is used as a HSM client, you must run the script /bin/nsrexecd.sh. This script will place the remote server's name in the file /nsr/res/servers, which is the list of NetWorker servers recognized by the local nsrexecd process as legitimate backup servers ************************************************************* NetWorker icon has been successfully installed into CDE. ************************************************************* Please refer to the TruCluster Production Server Software Documentation Version 1.5 for information on - how to define a highly available application - how to install and setup shared tapes hardware - how to define a cluster tape service Please refer to the 'NetWorker Save and Restore for DIGITAL UNIX Version 4.4 Installation Guide' for instructions on: Setting up NetWorker 4.4 as a NetWorker Cluster Server. ************************************************************* /usr/lib/X11/app-defaults/NetWorker file exists. Do you wish to overwrite this file? (y/n) [ n ]: BRXSOAKIT440 software installed successfully root@pluto[3]> exit script done on Thu Jun 5 08:04:34 1997 6. Run the /bin/nsrexecd.sh command on each node to add each cluster member and the NetWorker tape service name to the /nsr/res/servers server file. 32 Installing a NetWorker Cluster Server Connecting Storage Devices to the Cluster Refer to the TruCluster, DIGITAL UNIX, and device documentation for instructions on installing the NetWorker storage disk and tape device(s) to the cluster shared bus. If you are using a jukebox, you must install the CLC312 kit and create the media changer special device on each cluster member. Also, make sure that the special device files created in the /dev directory for each device have the same name on each cluster member. For example, the scu command reports the shared disk, media changer, and four tape devices in the TL820 hooked up to the example cluster shared bus (16) as follows: root@pluto[1]> scu show edt lun 0 CAM Equipment Device Table (EDT) Information: Device: RZ28 Bus: 0, Target: 0, Lun: 0, Type: Direct Access Device: RZ28 Bus: 0, Target: 1, Lun: 0, Type: Direct Access Device: RZ28 Bus: 0, Target: 2, Lun: 0, Type: Direct Access Device: RZ28 Bus: 0, Target: 4, Lun: 0, Type: Direct Access Device: TLZ6 Bus: 0, Target: 5, Lun: 0, Type: Sequential Access Device: RRD43 Bus: 0, Target: 6, Lun: 0, Type: Read-Only Direct Access Device: TZ88 Bus: 16, Target: 0, Lun: 0, Type: Sequential Access Device: TZ88 Bus: 16, Target: 1, Lun: 0, Type: Sequential Access Device: RZ28 Bus: 16, Target: 2, Lun: 0, Type: Direct Access Device: TL810 Bus: 16, Target: 3, Lun: 0, Type: Medium Changer Device: TZ88 Bus: 16, Target: 4, Lun: 0, Type: Sequential Access Device: TZ88 Bus: 16, Target: 5, Lun: 0, Type: Sequential Access Device: Bus: 16, Target: 7, Lun: 0, Type: Processor The corresponding special file names for each device on the example cluster node, pluto, were created with names as follows: root@pluto[2]> file /dev/nrmt*h /dev/nrmt1h: character special (9/262147) SCSI #16 TZ88 tape #7 (SCSI ID #0) (SCSI LUN #0) errors = 0/81 62500_bpi /dev/nrmt2h: character special (9/263171) SCSI #16 TZ88 tape #8 (SCSI ID #1) (SCSI LUN #0) errors = 0/17 offline Installing a NetWorker Cluster Server 33 /dev/nrmt3h: character special (9/266243) SCSI #16 TZ88 tape #11 (SCSI ID #4) (SCSI LUN #0) errors = 0/10 offline /dev/nrmt4h: character special (9/267267) SCSI #16 TZ88 tape #12 (SCSI ID #5) (SCSI LUN #0) errors = 0/10 offline On the example cluster node, donald, the names are the same, as follows: root@donald[2]> file /dev/nrmt*h /dev/nrmt1h: character special (9/262147) SCSI #16 TZ88 tape #7 (SCSI ID #0) (SCSI LUN #0) errors = 0/81 62500_bpi /dev/nrmt2h: character special (9/263171) SCSI #16 TZ88 tape #8 (SCSI ID #1) (SCSI LUN #0) errors = 0/17 offline /dev/nrmt3h: character special (9/266243) SCSI #16 TZ88 tape #11 (SCSI ID #4) (SCSI LUN #0) errors = 0/10 offline /dev/nrmt4h: character special (9/267267) SCSI #16 TZ88 tape #12 (SCSI ID #5) (SCSI LUN #0) errors = 0/10 offline Note After you have created the NetWorker tape service, the file command will display the above output only on the node currently running the tape service. This is because the devices are then reserved to that node and the file command is not allowed to get information from any other node. Defining NetWorker as a Highly Available Application The TruCluster Available Server administration document includes detailed information on how to define a highly available application and set up a shared tape service for general applications. Refer to that document for general information. This section includes specific instructions for defining NetWorker as a highly available application and setting up a NetWorker shared tape service. The steps presented in this section instruct you on how to: o Create the NetWorker tape service o Verify the shared device and tape services 34 Installing a NetWorker Cluster Server To define NetWorker as a highly available application in an ASE, complete each of the following steps: 1. On each cluster member, add the NetWorker tape service name to the /etc/hosts file by using the nsrhost command. 2. Create the NetWorker tape service by running the ASE asemgr utility and completing the following steps: a. From the ASE Main Menu choose Managing ASE Services (m). Then, select Service Configuration (c) followed by Add a new service (a). b. Choose to add a Tape service (5) from the Adding a Service menu. Assign a name to the tape service and an IP address. The name assigned to the tape service must also be used to identify the mount point in step f below. c. Specify tape information to define the tape storage for the tape service. d. Enter a media changer special file name (if applicable). e. Specify disk information to define the disk storage for the tape service. f. Identify the mount point of the directory on which the NetWorker tape service will be mounted. The mount point name used must be the same as the name assigned to the tape service in step b above. g. Enter read-write and quota management information. h. Define the Start action user-defined script for the tape service. From the menu, choose Add a start action script. Enter the full pathname of the start action script: /bin/NetWorker.start. The start action script argument must have the same name as the tape service specified in step b. i. Define the Stop action user-defined script for the tape service. From the menu, choose Add a stop action script. Enter the full pathname of the stop action script: /bin/NetWorker.stop. The stop action script argument must have the same name as the tape service specified in step b. j. At the Selecting an Automatic Service Placement (ASP) Policy menu, choose the preferred policy. k. Select Quit when all choices are complete. The following script example shows how to create the NetWorker tape service: Installing a NetWorker Cluster Server 35 root@pluto[1]> asemgr TruCluster Production Server (ASE) ASE Main Menu a) Managing the ASE --> m) Managing ASE Services --> s) Obtaining ASE Status --> x) Exit ?) Help Enter your choice: m Managing ASE Services c) Service Configuration --> r) Relocate a service on) Set a service on line off) Set a service off line res) Restart a service s) Display the status of a service a) Advanced Utilities --> q) Quit (back to the Main Menu) x) Exit ?) Help Enter your choice [q]: c Service Configuration a) Add a new service m) Modify a service o) Modify a service online d) Delete a service s) Display the status of a service c) Display the configuration of a service q) Quit (back to Managing ASE Services) x) Exit ?) Help Enter your choice [q]: a Adding a service Select the type of service: 1) NFS service 2) Disk service 3) User-defined service 4) DRD service 5) Tape service 36 Installing a NetWorker Cluster Server q) Quit without adding a service x) Exit ?) Help Enter your choice [1]: 5 You are now adding a new tape service to your ASE. A tape service consists of one or more tape devices, zero or more media changer devices, and an optional disk configuration that are failed over together. The disk configuration can include UFS filesystems, AdvFS filesets, LSM volumes, or raw disk information. Tape Service Name The name of a tape service must be a unique service name within this ASE. Optionally, an IP address may be assigned to a tape service. In this case, the name must be a unique IP host name set up for this service and present in the local hosts database on all ASE members. Enter the tape service name ('q' to quit): goofy Assign an IP address to this service? (y/n): y Checking to see if goofy is a valid host... Specifying Tape Information Enter one or more character device special files to define the tape storage for this service. For example: Rewind on close, high density: /dev/rmt0h No rewind on close, medium density: /dev/nrmt1m To end the list, press the Return key at the prompt. To quit, enter 'q'. Enter a tape special file name (press 'Return' to end): /dev/nrmt1h Enter a tape special file name (press 'Return' to end): /dev/nrmt2h Enter a tape special file name (press 'Return' to end): /dev/nrmt3h Enter a tape special file name (press 'Return' to end): /dev/nrmt4h Enter a tape special file name (press 'Return' to end): Specifying Media Changer Information Enter zero or more character device special files to define the media changers for this service. For example: /dev/mc16 Installing a NetWorker Cluster Server 37 To end the list, press the Return key at the prompt. To quit, enter 'q'. Enter a media changer special file name (press 'Return' to end): /dev/mc131 Enter a media changer special file name (press 'Return' to end): Specifying Disk Information Enter one or more device special files, AdvFS filesets, or LSM volumes to define the disk storage for this service. For example: Device special file: /dev/rz3c AdvFS fileset: domain1#set1 LSM volume: /dev/vol/dg1/vol01 To end the list, press the Return key at the prompt. Enter a device special file, an AdvFS fileset, or an LSM volume as storage for this service (press 'Return' to end): /dev/rz130g Mount Point The mount point is the directory on which to mount '/dev/rz130g'. If you do not want it mounted, enter "NONE". Enter the mount point or NONE: /goofy UFS File System Read-Write Access and Quota Management Mount '/dev/rz130g' file system with read-write or read-only access? 1) Read-write 2) Read-only Enter your choice [1]: 1 You may enable user and group quotas on this file system by specifying full path names for the quota files. If you place the files within the service's file systems, the quota assignments you make with edquota will relocate with the service. Enter "none" to disable quotas. User quota file [/goofy/quota.user]: Group quota file [/goofy/quota.group]: 38 Installing a NetWorker Cluster Server UFS Mount Options Modification Enter a comma-separated list of any mount options you want to use for '/dev/rz130g' (in addition to the UFS-specific defaults listed in the mount.8 reference page). If none are specified, only the default mount options are used. Enter options (Return for none): Specifying Disk Information Enter one or more device special files, AdvFS filesets, or LSM volumes to define the disk storage for this service. For example: Device special file: /dev/rz3c AdvFS fileset: domain1#set1 LSM volume: /dev/vol/dg1/vol01 To end the list, press the Return key at the prompt. Enter a device special file, an AdvFS fileset, or an LSM volume as storage for this service (press 'Return' to end): Modifying user-defined scripts for `goofy`: 1) Start action 2) Stop action 3) Add action 4) Delete action x) Exit - done with changes Enter your choice [x]: 1 Modifying the start action script for 'goofy': a) Add a start action script ) Edit the start action script ) Modify the start action script arguments [] ) Modify the start action script timeout [60] ) Remove the start action script x) Exit - done with changes Enter your choice [x]: a Enter the full pathname of your start action script or "default" for the default script (x to exit): /bin/NetWorker.start Enter the argument list for the start action script (x to exit): goofy Installing a NetWorker Cluster Server 39 Enter the timeout in seconds for the start action script [60]:300 Modifying the start action script for 'goofy': a) Replace the start action script e) Edit the start action script g) Modify the start action script arguments [goofy] t) Modify the start action script timeout [60] r) Remove the start action script x) Exit - done with changes Enter your choice [x]: Modifying user-defined scripts for `goofy`: 1) Start action 2) Stop action 3) Add action 4) Delete action Exit - done with changes Enter your choice [x]: 2 Modifying the stop action script for 'goofy': a) Add a stop action script ) Edit the stop action script ) Modify the stop action script arguments [] ) Modify the stop action script timeout [60] ) Remove the stop action script x) Exit - done with changes Enter your choice [x]: a Enter the full pathname of your stop action script or "default" for the default script (x to exit): /bin/NetWorker.stop Enter the argument list for the stop action script (x to exit): goofy Enter the timeout in seconds for the stop action script [60]:300 Modifying the stop action script for 'goofy': f) Replace the stop action script e) Edit the stop action script g) Modify the stop action script arguments [goofy] t) Modify the stop action script timeout [60] r) Remove the stop action script x) Exit - done with changes 40 Installing a NetWorker Cluster Server Enter your choice [x]: Modifying user-defined scripts for 'goofy': 1) Start action 2) Stop action 3) Add action 4) Delete action x) Exit - done with changes Enter your choice [x]: Selecting an Automatic Service Placement (ASP) Policy Select the policy you want ASE to use when choosing a member to run this service: b) Balanced Service Distribution f) Favor Members r) Restrict to Favored Members ?) Help Enter your choice [b]: Selecting an Automatic Service Placement (ASP) Policy Do you want ASE to consider relocating this service to another member if one becomes available while this service is running (y/n/?): n Enter 'y' to add Service 'goofy' (y/n): y Adding service... Starting service... Service goofy successfully added... Service Configuration Add a new service m) Modify a service o) Modify a service online d) Delete a service s) Display the status of a service c) Display the configuration of a service q) Quit (back to Managing ASE Services) x) Exit ?) Help Enter your choice [q]: x Installing a NetWorker Cluster Server 41 Note To verify that the NetWorker service can relocate from one cluster to another successfully, attempt a manual relocation. Refer to the TruCluster documentation for information on how to do this. 3. To determine the name of the cluster member that is currently running the NetWorker service, use the asemgr -d command. The following example indicates that the tape service, goofy, is running on pluto: root@pluto asemgr -d Level of ASE logging: Informational (log everything) Location of Logger(s) The following member(s) are logging ASE information: mcpluto mcdonald Member Status Member: Host Status: Agent Status: mcpluto UP RUNNING mcdonald UP RUNNING Service Status goofy on mcpluto 4. Run the asemgr -d -v command to verify that the NetWorker tape service definition completed successfully. The following is an example of the verification command output: root@pluto asemgr -d -v Status for TAPE service 'goofy' Status: Relocate: Placement Policy: Favored Member(s): on mcpluto no Balance Services None Storage configuration for TAPE service 'goofy' Tape devices /dev/nrmt1h /dev/nrmt2h /dev/nrmt3h /dev/nrmt4h Media changer devices /dev/mc131 42 Installing a NetWorker Cluster Server Mount Table (device, mount point, type, options) /dev/rz130g /goofy advfs rw,groupquota,userquota 5. To verify the share devices reservations, use the scu command. In the following example, the NetWorker tape service, goofy, is running on the cluster node, pluto. The scu command is used to verify device reservation for /dev/nrmt1h. The scu and tur commands return the following error for cluster node donald because this device is reserved by cluster node pluto: root@pluto[1]> scu scu> set nexus b 16 t 0 l 0 Device: TZ88, Bus: 16, Target: 0, Lun: 0, Type: Sequential Access scu> tur root@donald[14]> scu scu> set nexus b 16 t 0 l 0 Device: TZ88, Bus: 16, Target: 0, Lun: 0, Type: Sequential Access scu> tur scu: 'test unit ready' failed, EIO (5) - I/O error scu> Note: Media changer devices are not reserved Configuring the NetWorker Cluster Server After NetWorker is installed on the cluster servers, you must complete the installation by running the IVP and configuring the servers. Complete the following steps. 1. Log in to the cluster member that is running the NetWorker tape service. 2. Refer to Chapter 4, Completing the Installation. Follow the instruction in the Running the Installation Verification Procedure and the Configuring Server Files sections. 3. Run the /bin/nsrexecd.sh script to add the NetWorker tape service and each cluster member to the list of servers that are allowed to back it up. 4. From the NetWorker GUI Server window, go to Server Setup and add any cluster member not already listed in the server administrator attribute. 5. To define a savegroup, go to the Savegroup window from the GUI Server window. Use the Details mode to set the autorestart attribute to On. Installing a NetWorker Cluster Server 43 Notice the following differences in the NetWorker cluster server setup: a. The NetWorker cluster server will take the identity of the NetWorker tape service regardless of which cluster member is currently running the NetWorker service. b. The first time NetWorker is run, NetWorker will create the client resource for the NetWorker tape service. Client resources need to be created manually for any cluster member to be backed up by the NetWorker tape service. Migrating a NetWorker Server to a Cluster Server When a system already running NetWorker is a member of a cluster and is to be upgraded to NetWorker V4.4 so that it can run as a cluster server, you must install NetWorker 4.4 as a cluster server. To migrate the existing server indexes, media database, and resource file, follow the installation steps presented in this section. Warning You can migrate a non-cluster NetWorker server to a NetWorker cluster server only if the NetWorker storage device used on the existing server is one of the devices supported for cluster server failover. See the NetWorker SPD for the list of supported devices. Follow these steps to migrate the non-cluster NetWorker server to a NetWorker cluster server: 1. Issue the setld -d command to remove the old NetWorker server. Do not remove the old nsr directory. 2. Preserve the link to the old nsr directory (located on the old server local disk) by issuing the following command: # mv /nsr /nsr.old 3. Follow the instructions in the Installing a NetWorker Cluster Server chapter on page 25 to install and configure NetWorker V4.4 as a cluster server. These instructions include directions for connecting the NetWorker shared storage and the shared dedicated disk to a shared bus in the cluster. 4. Make sure NetWorker is running on the cluster node where the old nsr directory is located (you may need to relocate the tape service to accomplish this). 5. On the cluster node running the NetWorker tape service as root, perform the following steps: 44 Installing a NetWorker Cluster Server a. Issue the nsr_shutdown command to stop all NetWorker activity. b. Issue the following command to remove the default resources created when the NetWorker tape service was defined: # rm -rf /nsr/* 6. Refer to the Migrating Your NetWorker Environment section in the NetWorker Addendum to migrate the indexes, media database, and resource files from the old server to the NetWorker cluster server nsr directory (now located on a shared disk). Follow the procedures outlined in Step One - Migrating Indexes with the following changes: a. Skip step 2 and step 3. b. In step 4, issue the following commands in place of the commands presented: # cd /nsr.old # uasm -s -f /tmp/directive . | (cd /nsr; uasm -rv) Then, complete the procedures outlined in Step Two - Migrating Resource Files as presented. 7. Set the NetWorker tape service off line and then set it back on line. NetWorker will take the identity of the NetWorker tape service. 8. Remove any old device and jukebox resources and reconfigure them to reflect their new location on the shared bus. Relocating the NetWorker Service Each time the NetWorker tape service is relocated either manually, due to system crash, or due to ASE placement policy enforcement, the ASE software will: 1. Shut down all the NetWorker daemons on the cluster member running the NetWorker tape service. It will then restart nsrexecd on that system. 2. Relocate the NetWorker service to the assigned cluster member. Note that the /nsr link will be redefined to point to the NetWorker tape service shared disk: /nsr -> /tape_service_name/nsr. Following the defined cluster example, at any time, the link to the /nsr directory will be as follows: Installing a NetWorker Cluster Server 45 a. On the cluster member running the NetWorker service: /nsr -> /goofy/nsr /nsr.NetWorker.local -> /var/nsr b. On each cluster member not running the NetWorker service: /nsr -> /nsr.NetWorker.local /nsr.NetWorker.local -> /var/nsr Note that ASE will not relocate the NetWorker service if: o The storage disk is busy (this could happen if a user has changed to a directory (cd) on that file system). o It cannot access any of the NetWorker tape service devices. Shutting Down/Restarting the Cluster Server To shut down the NetWorker daemon on the cluster server, you must take the NetWorker tape service off line by running the ASE asemgr command. Taking the tape service offline will cleanly stop all NetWorker activity. To manually restart the NetWorker daemons on a cluster server, set the NetWorker tape service online by running the ASE asemgr command. Deinstalling the Cluster Server Subset Before deinstalling the cluster server subset, set the NetWorker tape service off line to stop any NetWorker activity and the NetWorker daemons. If the NetWorker daemons are running, the NetWorker server subset will not be deinstalled. To deinstall the server subset on a cluster member, follow these steps: 1. Issue the asemgr command to set the NetWorker service off line. 2. Issue the setld -d BRXSOAKIT440 command to remove the NetWorker server subset. The following is an example of a successful deinstall: root@donald[16]> setld -d BRXSOAKIT440 The following background processes are still running and will be killed during the BRXSOAKIT440 deletion: ?? I 0:01.02 /usr/bin/nsrexecd 46 Installing a NetWorker Cluster Server Do you wish to continue? (y/n) [ y ]: Killing pids: 660 The nsrd related processes are no longer running. Deleting /sbin/init.d/nsrd Delete the local /nsr directory of this NetWorker cluster member(y/n) [ n ]: Removing NetWorker icon from the CDE environment Do you wish to deinstall /usr/lib/X11/app-defaults/Networker? (y/n) [ n ]: Deleting "NetWorker Server for DIGITAL UNIX" (BRXSOAKIT440). root@donald[17]> If you do not stop the NetWorker daemons before attempting to deinstall, the following error will occur: root@pluto[1]> setld -d BRXSOAKIT440 ************************************************************* NetWorker's server daemons appear to be running on this NetWorker cluster server system. Use the 'asemgr' command to set the NetWorker's service off line before deleting the BRXSOAKIT440 subset. ************************************************************* setld: BRXSOAKIT440, deletion declined by subset control program. root@pluto[2]> Reinstalling the Cluster Server Subset To reinstall the server subset on a cluster member, follow these steps: 1. Issue the asemgr command to set the NetWorker tape service offline. 2. Issue the setld -d BRXSOAKIT440 command to remove the NetWorker server subset. 3. Issue the setld -l command to reinstall the NetWorker server subset before you set the NetWorker service back on line. 4. Issue the asemgr command to set the NetWorker tape service back on line. Installing a NetWorker Cluster Server 47 Making a Cluster Member a Client of the NetWorker Cluster Server When you install the NetWorker 4.4 software on a cluster member, the installation creates the /nsr link to point to a local disk. It also creates a second link to the local NetWorker directory named nsr.NetWorker.local. For example, if the local NetWorker directory was created in /var/nsr, after the installation, each client member will have the following links: o /nsr -> /var/nsr o /nsr.NetWorker/local -> /var/nsr To make a cluster member a NetWorker client of the NetWorker cluster server, follow these steps: 1. Run the /bin/nsrexecd.sh script to add the name of the NetWorker service and the names of each cluster member to the list of servers allowed to back up this client. 2. Use the GUI/Clients/'Client Setup' option to add the cluster member as a client of the NetWorker server. 3. Add the IP name for this cluster member's cluster interconnect to its remote access attribute list. For example, add root@mcdonald.com to donald's client resource. 48 Installing a NetWorker Cluster Server Chapter 4 Completing the Server Installation This chapter explains what you need to do after the installation to get NetWorker ready for use, and it describes how to access the NetWorker documentation. Running the Installation Verification Procedure After installing NetWorker, you should run the Installation Verification Procedure (IVP) independently to verify that the software is available on your NetWorker server system. You might also want to run the IVP after a system failure to be sure that users can access NetWorker. To run the IVP after an installation, enter the following command: # setld -v subsetname In this command, subsetname can be any NetWorker subset. The subset identifiers for NetWorker servers include: Table 6 NetWorker Subsets Subset Name Subset Identifier NetWorker Server for DIGITAL UNIX BRXSOAKIT440 NetWorker DIGITAL UNIX Client BRXCKIT440 NetWorker Server Reference Pages BRXSMAN440 NetWorker Release Notes and Documentation BRXRNOTES440 Configuring Server Files After you have run the NetWorker installation script, you can optionally modify the /etc/hosts file to add the name nsrhost as an alias to the official host name of the NetWorker server. This ensures that NetWorker will only attempt to connect to the designated NetWorker server. Configuring Server Files Manually When you ran the NetWorker installation script, the script asked whether you wanted certain files on the NetWorker server to be created or modified automatically. If you answered no, the script did not create the /sbin/init.d/nsrd file or modify the /etc/rpc and /etc/syslog.conf. In this case, you must create and modify these files manually, after you have run the NetWorker installation script. Creating the /sbin/init.d/nsrd File In order for the server to cleanly shut down and restart NetWorker on system shutdown and restart, create the file /sbin/init.d/nsrd with the following contents: #!/sbin/sh # #ifdef IDENT #ident"@(#)nsrd 1.8 97/08/06 Copyright (C) 1997, Digital Equipment Corp" #endif # # %BRX440_BEGIN% - DO NOT MODIFY OR DELETE (April 1997) PATH=/sbin:/usr/sbin:/bin:/usr/bin export PATH WORKLIST="false" if["$1"="-c"];then WORKLIST="true" shift fi case "$1" in install_clust_svr) # # Start only nsrexecd following installation where cluster # server failover is configured. This case is called by the # server install procedure only. # if[-f /usr/bin/nsrexecd] then 50 Completing the Server Installation if /bin/ps -e | grep nsrexecd | grep -v grep > /dev/null then echo "Stopping and restarting nsrexecd process" >/dev/console 2>&1 ps_output="`ps -eopid,comm |grep nsrexecd`" active_pids="`echo "$ps_output" |awk '/awk/ {next} $0 ~ /'"nsrexecd "'/ { print $1 }'`" kill -9 $active_pids >/dev/console 2>&1 fi ( /usr/bin/nsrexecd; sleep 2 ) >/dev/console 2>&1 fi ;; start) # # Un-comment out (remove the leading #) on the line # below which sets the variable NSR_OLDFWARE_TLZ7L # to "ENABLED" if you wish to enable the NSR software # to work-around the TLZ7L firmware bug (see the bug # description in the NSR v3.2 release notes). #NSR_OLDFWARE_TLZ7L="ENABLED" ; export NSR_OLDFWARE_TLZ7L # Allows portmap to start before the NetWorker server if /bin/ps -e | grep portmap > /dev/null then echo nsrd portmap check passed >/dev/console else [ -f /usr/sbin/portmap ] && /usr/sbin/portmap fi # Start NetWorker server after system reboot if [ -f /usr/bin/nsrd ] then ( /usr/bin/nsrd; sleep 2 ) >/dev/console 2>&1 fi # Start nsrexecd after system reboot if [ -f /usr/bin/nsrexecd ] then if /bin/ps -e|grep nsrexecd|grep -v grep> /dev/null then echo "Stopping and restarting nsrexecd process">/dev/console 2&1 ps_output="'ps -eopid,comm |grep nsrexecd'" active_pids="'echo "$ps_output" lawk '/awk/ {next} $0 ~ /'"nsrexecd""/ {print$1}''" kill -9 $active_pids >/dev/console 2>&1 fi ( /usr/bin/nsrexecd; sleep 2 ) >/dev/console 2>&1 fi Completing the Server Installation 51 ;; stop) # Shutdown NetWorker server if [ -f /usr/bin/nsr_shutdown ] then echo Stopping NetWorker daemons >/dev/console if [ "${WORKLIST}" = "true" ]; then /usr/bin/nsr_shutdown -c -q& >/dev/console 2>&1 echo nsr_shutdown -c -q >/dev/console else /usr/bin/nsr_shutdown -q& >/dev/console 2>&1 echo nsr_shutdown -q >/dev/console fi ;; *) echo init.d/nsrd: $1 ignored >/dev/console ;; esac # %BRX440_END% - DO NOT MODIFY OR DELETE Next, create soft links to the /sbin/init.d/nsrd file by issuing the following commands: # ln -s /sbin/init.d/nsrd /sbin/rc3.d/S94nsrd # ln -s /sbin/init.d/nsrd /sbin/rc0.d/K00nsrd Configuring the /etc/rpc and /etc/syslog.conf Files To manually modify the /etc/rpc and the /etc/syslog.conf files, follow these steps: 1. Log in as root user on the NetWorker server. 2. Edit the /etc/rpc file on the NetWorker server to add the following lines, exactly as shown, at the end of the file: # %BRX440_BEGIN% - DO NOT MODIFY OR DELETE nsrd 390103 nsr nsrmmd 390104 nsrmm nsrindexd 390105 nsrindex nsrmmdbd 390107 nsrmmdb nsrstat 390109 nsrexec 390113 nsrexecd # %BRX440_END% - DO NOT MODIFY OR DELETE 3. Edit the /etc/syslog.conf file on the NetWorker server to add the following lines, exactly as shown, at the end of the file: 52 Completing the Server Installation # %BRX440_BEGIN% - DO NOT MODIFY OR DELETE daemon.notice /dev/console daemon.notice /nsr/logs/messages daemon.notice operator local0.notice /nsr/logs/summary local0.alert root, operator # %BRX440_END% - DO NOT MODIFY OR DELETE 4. If you are not running NetWorker as a cluster server, start the NetWorker daemons by entering the following command at the NetWorker server system prompt: # /sbin/init.d/nsrd start Customizing the NetWorker Server After NetWorker is installed, your next step is to customize the NetWorker server for your environment. Refer to the NetWorker Administrator Guide UNIX Version for general information about NetWorker functionality and resources. Review the Addendum for specific information about configuring NetWorker on the DIGITAL UNIX operating system. Deleting NetWorker from Your System If you must remove a version of NetWorker from your system, delete each subset that you previously installed. To delete subsets: 1. Enter the setld command: # setld -i | grep BRX or, if you know the subset name: # setld -i | subsetnamennn where nnn is the version number. 2. Look for the word installed in the listing produced by the command in Step 1. Delete the installed subsets using the following command: # setld -d subsetnamennn Completing the Server Installation 53 Accessing Release Notes and Documentation After you complete your software installation, you can access the release notes and product documentation from the product directory /usr/opt/BRX440/usr/doc if you selected the release notes subset as one of the subsets to install. The release notes are provided in this product directory as well as on the Software Product Library CD-ROM distribution disc so that you can access them on line at any time before or after product installation. The release notes are available in both PostScript and text versions. The PostScript file is titled brx440_relnotes.ps and the text file is brx440_relnotes.txt. For instructions on how to locate the release notes on the distribution disc, see the Software Product Library CD-ROM User's Guide. 54 Completing the Server Installation Chapter 5 Installing the Client Software This chapter provides procedures for installing the client software. You can install the NetWorker software on the client's disk or mount the binaries from an NFS file server. Once the client subset has been loaded onto the NetWorker server, you can install the DIGITAL UNIX client using the instructions in the DIGITAL UNIX Client Installation section on this page. For other clients, refer to the Installation Guide that came with your Client Kit. DIGITAL UNIX Client Installation Before you begin installing the client software, photocopy the client installation worksheet provided in Appendix C. You may need several copies, depending upon your network backup configuration. Use the worksheet to organize your client installations. The fields in the client installation worksheet include: o Server Hostname Enter the host name of the server. If your backup configuration includes several NetWorker servers, generate a worksheet for each server. o Client Hostname Enter the official host name of a client system on each new line of the worksheet. If possible, list client systems according to platform types. o Directory Enter the directory where NetWorker client executables will reside. This applies to installations to client disks and installations to a server disk that client systems can NFS mount. The default directory for installations to client disks is /usr/bin. o Old Version Removed? If applicable, have you removed the old versions of NetWorker client software from each client system? Depending on how the old version was installed, consult the nsr_ize(8) reference page or the Installation Guide provided with the client software for instructions on how to delete the old client software. o Base Software Installed? Are the required base system, network, and manual page software subsets installed? See Software Requirements on page 7. o Directory on Search Path? Is the directory where NetWorker client executables will reside in the root account of the client system's interactive and non-interactive default search path? o Disk Space Available? Is there enough disk space for the NetWorker client subset? See page 11 for disk space requirements. o Portmap Activated? Is the portmap daemon running on the client system? See the portmap (8) reference page for instructions on starting the portmap daemon. o System File Configured? On each client system, modify the following file: /etc/hosts In the /etc/hosts file of each client system, make nsrhost an alias to the official host name of the NetWorker server, as follows: Internet_address official_hostname nsrhost Starting the Client Installation Procedure Before installing the NetWorker client software onto the DIGITAL clients, review the disk space requirements in Table 4 on page 11. Also, be sure that old versions of the DIGITAL UNIX client archive and backup software are removed. If the archive software is installed, it must be removed before removing the backup software. To remove the software, issue the following commands on the client system: # archive_ize -r # nsr_ize -r 56 Installing the Client Software Caution If you have Networker Version 4.2A or later installed, the nsr_ize -r command will remove both archive and backup software at the same time. In addition, the nsr_ize -i command will install both the archive and backup software. When the NetWorker client subset is installed on the NetWorker server system, the client kit tar file is loaded by default to the NetWorker server system. The file specification is: /usr/opt/BRX440/BRXCKIT440/clientkit.tar. The following steps describe how to extract the tar file and install the software on a DIGITAL UNIX client system. Caution During installation of the DIGITAL clients using the nsr_ize command, a system can hang if it uses automount with a host map with the name export. To avoid this problem, edit the nsr_ize script and replace the two occurrences of /export/exec/ with /exec/. Make sure that /exec/ is not a host map name already in use. The example shows the installation of NetWorker DIGITAL UNIX client software on node cochiti from the NetWorker server, mercury. 1. Log in as root user on the client system. 2. NFS mount the filesystem where the tar file (clientkit.tar) resides on the server system. # mount mercury:/usr/opt/BRX440 /usr/opt/BRX440 3. Use the mkdir command to create the nsr_extract directory. # cd /usr/tmp # mkdir nsr_extract # cd nsr_extract 4. Use the tar command to extract the software. # tar -xvpf /usr/opt/BRX440/BRXCKIT440/clientkit.tar decaxp 5. Use the nsr_ize command to install the software. Note that this command puts the binaries in the /usr/bin directory by default. If you do not have enough available disk space in /usr/bin, when prompted during the installation, specify /var as the directory where the programs should be installed. # cd decaxp # ./nsr_ize -i The procedure displays information similar to the following example: Installing the Client Software 57 NetWorker(TM) - Release V4.4 Copyright (c) 1990-1997, Digital Equipment Corp. All rights reserved. This product includes software developed by the University of California, Berkeley and its contributors. nsr_ize is about to install NetWorker client software on client machine 'cochiti.zso.dec.com'. 6. Indicate if you want to install the reference pages and where. Install the NetWorker man pages [yes]? Directory into which the NetWorker man pages should be installed [/usr/man]? Installing NetWorker man pages into /usr/man Update the man page directory (NOTE - this takes a while) [yes]? 7. Indicate if you want to install the decaxp NetWorker programs and where. Install the decaxp NetWorker programs [yes]? Directory where decaxp NetWorker programs should be installed [/usr/bin]? Installing decaxp NetWorker client programs into /usr/bin Creating /usr/bin/nsr_man Linking /usr/bin/nwadmin to /usr/bin/networker 8. Indicate where you want the nsrexecd log and work files located. To set up a NetWorker client, you need to supply a directory for the nsrexecd log and work files. On NSR servers and clients, this is normally /nsr (which will be softlinked to the directory you now specify) Directory where nsrexecd NetWorker programs should be installed [/nsr]? /var/nsr 9. Identify all of the servers that are to back up this client. This information will be stored in the /nsr/res/servers file. (Additional servers can be added to this file after installation.) The nsrexecd program restricts access to a select set of NetWorker servers. Please enter the names of each computer running a NetWorker server that will back up this computer, one name at a time. If a computer has more than one network interface, please enter each interface's name (one at a time). 58 Installing the Client Software Enter the first NetWorker server's name [no more]: mercury.zso.dec.com Enter the next NetWorker server's name [no more]: 10.Indicate if you want to start NetWorker when the installation is complete. Start NetWorker daemons at end of install [yes]? Installing NetWorker home directory in /var/nsr nsr-izing system files Creating /sbin/init.d/networker Creating /nsr/res/servers Creating /sbin/rc3.d/S94networker Creating /sbin/rc3.d/K00networker Completing Installation Starting NetWorker daemons NetWorker successfully installed on 'cochiti.zso.dec.com'! 11.In order for the NetWorker server to access the client for the network-wide backups, add the directory with the NetWorker software to the path environment variable for the root shell. 12.Delete the nsr_extract directory using the following commands: # cd /usr/tmp # rm -rf nsr_extract Installing the Client Software 59 Appendix A Sample Listing for NetWorker Installation This appendix provides a listing for the installation of NetWorker from a CD-ROM into a network configuration. This installation procedure includes the following two steps: 1. Install NetWorker Server for DIGITAL UNIX software and load the following optional subsets on the NetWorker server: - NetWorker DIGITAL UNIX Client - NetWorker Server Reference Pages - NetWorker Release Notes and Documentation 2. Install NetWorker client software on a DIGITAL UNIX client system. NetWorker Server Installation Example The following listing shows a sample installation of NetWorker on a DIGITAL UNIX server system using CD-ROM media. In addition to installing NetWorker server software, this installation loads NetWorker client software in preparation for step two. All commands in this listing are issued from the NetWorker server system: # setld -l /mnt/brx440/kit The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 1) NetWorker DIGITAL UNIX Client 2) NetWorker Release Notes and Documentation 3) NetWorker Server Reference Pages 4) NetWorker Server for DIGITAL Or you may choose one of the following options: 5) ALL of the above 6) CANCEL selections and redisplay menus 7) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 5 You are installing the following optional subsets: NetWorker DIGITAL UNIX Client NetWorker Release Notes and Documentation NetWorker Server Reference Pages NetWorker Server for DIGITAL UNIX Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. 4 subset(s) will be installed. Loading 1 of 4 subset(s).... This subset will take 5 minutes to complete. NetWorker Server for DIGITAL UNIX Copying from (disk) Working....Tue Mar 18 12:33:12 PST 1997 Verifying Loading 2 of 4 subset(s).... This subset will take 5 minutes to complete. NetWorker Server Reference Pages Copying from (disk) Verifying Loading 3 of 4 subset(s).... This subset will take 5 minutes to complete. NetWorker DIGITAL UNIX Client Copying from (disk) Working....Tue Mar 18 12:34:21 PST 1997 Verifying 62 Sample Listing for NetWorker Installation Loading 4 of 4 subset(s).... This subset will take 5 minutes to complete. NetWorker Release Notes and Documentation Copying from (disk) Working....Tue Mar 18 12:34:52 PST 1997 Verifying 4 of 4 subset(s) installed successfully. Configuring "NetWorker Server for DIGITAL UNIX" (BRXSOAKIT440) NetWorker Save and Restore Version V4.4 Copyright Digital Equipment Corporation 1991, 1997. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use or copying of this software and media is authorized only pursuant to a valid license from Digital or an authorized sublicensor. ************ File Configuration on NetWorker Server *********** The installation procedure adds entries to the /etc/rpc and /etc/syslog.conf files on the NetWorker server; the original files are renamed and saved. The installation also creates the /sbin/init.d/nsrd file. Do you wish to continue? (y/n) [ y ]: Modifying /etc/rpc Modifying /etc/syslog.conf * * * Restarting syslog daemon * * * Do you wish to remove the saved files? (y/n) [ n ]: The modified files were saved and renamed as follows: File Location of saved file /etc/rpc /etc/rpc_nsrsave /etc/syslog.conf /etc/syslog.conf_nsrsave Creating /sbin/init.d/nsrd Sample Listing for NetWorker Installation 63 Starting nsrd... *************************************************************** * If this system is to be backed up as the client of a remote * * NetWorker server or is used as a HSM client, you must run * * the script /bin/nsrexecd.sh * * This script will place the remote server's name in the file * * /nsr/res/servers, which is the list of NetWorker servers * * recognized by the local nsrexecd process as legitimate * * backup servers * *************************************************************** NetWorker icon has been successfully installed into CDE. /usr/lib/X11/app-defaults/Networker file exists. Do you wish to overwrite this file? (y/n) [n]: The app-defaults file for Networker was not installed. Use 'setld -c BRXSOAKIT440 INSTALL' command to install later. BRXSOAKIT440 software installed successfully Configuring "NetWorker Server Reference Pages" (BRXSMAN440) NetWorker Save and Restore Version V4.4 Copyright Digital Equipment Corporation 1991, 1997. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use or copying of this software and media is authorized only pursuant to a valid license from Digital or an authorized sublicensor. BRXSMAN440 software installed successfully Configuring "NetWorker DIGITAL UNIX Client" (BRXCKIT440) NetWorker Save and Restore Version V4.4 Copyright Digital Equipment Corporation 1991, 1997. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use or 64 Sample Listing for NetWorker Installation copying of this software and media is authorized only pursuant to a valid license from Digital or an authorized sublicensor. BRXCKIT440 software installed successfully Configuring "NetWorker Release Notes and Documentation" (BRXRNOTES440) NetWorker Save and Restore Version V4.4 Copyright Digital Equipment Corporation 1991, 1997. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use or copying of this software and media is authorized only pursuant to a valid license from Digital or an authorized sublicensor. BRXRNOTES440 software installed successfully DIGITAL UNIX Client Installation Example The following listing shows a sample installation of the DIGITAL UNIX client software (decaxp) on node cochiti.zso.dec.com. All commands in this listing are issued from the NetWorker client system: # cd /usr/tmp # mkdir nsr_extract # cd nsr_extract # tar -xvpf /usr/opt/BRX440/BRXCKIT440/clientkit.tar decaxp blocksize = 256 x decaxp x decaxp/decaxp x decaxp/decaxp/nsrexecd.sh, 3023 bytes, 6 tape blocks x decaxp/decaxp/mminfo, 376832 bytes, 736 tape blocks x decaxp/decaxp/mmlocate, 532480 bytes, 1040 tape blocks x decaxp/decaxp/mmpool, 532480 bytes, 1040 tape blocks x decaxp/decaxp/nsradmin, 483328 bytes, 944 tape blocks x decaxp/decaxp/nsrclone, 540672 bytes, 1056 tape blocks x decaxp/decaxp/nsrexecd, 901120 bytes, 1760 tape blocks x decaxp/decaxp/nsrinfo, 892928 bytes, 1744 tape blocks x decaxp/decaxp/nsrmm, 598016 bytes, 1168 tape blocks x decaxp/decaxp/nsrwatch, 540672 bytes, 1056 tape blocks x decaxp/decaxp/nwadmin, 1581056 bytes, 3088 tape blocks x decaxp/decaxp/nwbackup, 1204224 bytes, 2352 tape blocks Sample Listing for NetWorker Installation 65 x decaxp/decaxp/nwrecover, 1482752 bytes, 2896 tape blocks x decaxp/decaxp/recover, 1163264 bytes, 2272 tape blocks x decaxp/decaxp/save, 999424 bytes, 1952 tape blocks x decaxp/decaxp/savefs, 811008 bytes, 1584 tape blocks x decaxp/decaxp/nsralist, 565248 bytes, 1104 tape blocks x decaxp/decaxp/nsrarchive, 1081344 bytes, 2112 tape blocks x decaxp/decaxp/nsrretrieve, 1163264 bytes, 2272 tape blocks x decaxp/decaxp/nwarchive, 1204224 bytes, 2352 tape blocks x decaxp/decaxp/nwretrieve, 1163264 bytes, 2272 tape blocks x decaxp/decaxp/hideasm, 6476 bytes, 13 tape blocks x decaxp/decaxp/tarasm, 5095 bytes, 10 tape blocks x decaxp/decaxp/uasm, 679936 bytes, 1328 tape blocks x decaxp/decaxp/nsrhsmck, 638976 bytes, 1248 tape blocks x decaxp/decaxp/nsrib, 638976 bytes, 1248 tape blocks x decaxp/decaxp/nsriba, 1155072 bytes, 2256 tape blocks x decaxp/decaxp/nsrmig, 638976 bytes, 1248 tape blocks x decaxp/decaxp/nsrpmig, 1105920 bytes, 2160 tape blocks x decaxp/nsr_ize, 94419 bytes, 185 tape blocks x decaxp/nsr_shutdown, 12930 bytes, 26 tape blocks x decaxp/nsr_support, 29050 bytes, 57 tape blocks x decaxp/nsr.help, 218546 bytes, 427 tape blocks x decaxp/man x decaxp/man/mminfo.8, 32477 bytes, 64 tape blocks x decaxp/man/mmlocate.8, 3639 bytes, 8 tape blocks x decaxp/man/mmpool.8, 1821 bytes, 4 tape blocks x decaxp/man/nsr_getdate.3, 4095 bytes, 8 tape blocks x decaxp/man/nsradmin.8, 9562 bytes, 19 tape blocks x decaxp/man/nsrclone.8, 11893 bytes, 24 tape blocks x decaxp/man/nsrexecd.8, 3713 bytes, 8 tape blocks x decaxp/man/nsrwatch.8, 4187 bytes, 9 tape blocks x decaxp/man/nsrinfo.8, 8611 bytes, 17 tape blocks x decaxp/man/nsrmm.8, 15201 bytes, 30 tape blocks x decaxp/man/nwadmin.8, 2082 bytes, 5 tape blocks x decaxp/man/recover.8, 15927 bytes, 32 tape blocks x decaxp/man/save.8, 7536 bytes, 15 tape blocks x decaxp/man/savefs.8, 10040 bytes, 20 tape blocks x decaxp/man/uasm.8, 17126 bytes, 34 tape blocks x decaxp/man/nsr_archive_request.5, 7257 bytes, 15 tape blocks x decaxp/man/nsralist.8, 1533 bytes, 3 tape blocks x decaxp/man/nsrarchive.8, 5955 bytes, 12 tape blocks x decaxp/man/nsrretrieve.8, 3324 bytes, 7 tape blocks x decaxp/man/nwarchive.8, 2313 bytes, 5 tape blocks x decaxp/man/nwretrieve.8, 2420 bytes, 5 tape blocks x decaxp/man/nsr_migration.5, 8999 bytes, 18 tape blocks x decaxp/man/nsrhsmck.8, 3645 bytes, 8 tape blocks x decaxp/man/nsrib.8, 9735 bytes, 20 tape blocks x decaxp/man/nsriba.8, 9735 bytes, 20 tape blocks x decaxp/man/nsrmig.8, 2545 bytes, 5 tape blocks x decaxp/man/nsrpmig.8, 6415 bytes, 13 tape blocks # cd decaxp # ./nsr_ize -i 66 Sample Listing for NetWorker Installation NetWorker(TM) - Release V4.4 Copyright (c) 1990-1997, Digital Equipment Corp. All rights reserved. This product includes software developed by the University of California, Berkeley and its contributors. nsr_ize is about to install NetWorker client software on client machine 'cochiti.zso.dec.com'. Install the NetWorker man pages [yes]? Directory into which the NetWorker man pages should be installed [/usr/man]? Installing NetWorker man pages into /usr/man Update the man page directory (NOTE - this takes a while) [yes]? Install the decaxp NetWorker programs [yes]? Directory where decaxp NetWorker programs should be installed [/usr/bin]? Installing decaxp NetWorker client programs into /usr/bin Creating /usr/bin/nsr_man Linking /usr/bin/nwadmin to /usr/bin/networker To set up a NetWorker client, you need to supply a directory for the nsrexecd log and work files. On NSR servers and clients, this is normally /nsr (which will be softlinked to the directory you now specify) Directory where decaxp NetWorker programs should be installed [/nsr]? /var/nsr The nsrexecd program restricts access to a select set of NetWorker servers. Please enter the names of each computer running a NetWorker server that will back up this computer, one name at a time. If a computer has more than one network interface, please enter each interface's name (one at a time). Enter the first NetWorker server's name [no more]: mercury.zso.dec.com Enter the next NetWorker server's name [no more]: Start NetWorker daemons at end of install [yes]? Installing NetWorker home directory in /var/nsr nsr-izing system files Creating /sbin/init.d/networker Creating /nsr/res/servers Creating /sbin/rc3.d/S94networker Creating /sbin/rc3.d/K00networker Completing Installation Starting NetWorker daemons Sample Listing for NetWorker Installation 67 NetWorker successfully installed on 'cochiti.zso.dec.com'! 68 Sample Listing for NetWorker Installation Appendix B Files Installed on Your System The following sections describe the files installed on NetWorker server systems, and the files installed on DIGITAL UNIX. Files Installed on Server Systems To allow the server to cleanly shut down and restart NetWorker on system shutdown and restart, the /sbin/init.d/nsrd file is installed automatically during the installation or manually if you chose not to install the file during installation. See the Creating the /sbin/init.d/nsrd File section on page 50 if this file is not installed. Table 7 Installed NetWorker Files -- Server lists and describes the files associated with a NetWorker server installation. These files reside in the /usr/opt/BRX440/BRXSOAKIT440/bin directory. The installation procedure creates symbolic links in the /bin directory that point to the respective NetWorker server software files. Table 7 Installed NetWorker Files -- Server File Description ansrd Agent NetWorker server daemon used for a save or recover session asavegrp Executable file for starting a group of NetWorker clients saving their filesystems changers Lists all SCSI jukeboxes connected to a system hideasm Module for saving and recovering without creating index entries hpflip Reads vendor-unique mide page from HP optical disk drive and converts the device type (continued) Table 7 Installed NetWorker Files -- Server (cont.) File Description ielem Initializes element status of specified SCSI device inquire Returns INQUIRY data for all or specified SCSI devices attached to system jb_config Executable file to add a jukebox as a NetWorker resource jbexercise Executable file for testing the functions of a jukebox vector mminfo Executable file for reporting media information mmlocate Executable file for accessing and managing the volume location information contained in the media databases mmpool Used to display pool information stored in the media database mmrecov Executable file for recovering the online indexes of the NetWorker server nsr.help A help file used by the executable NetWorker software to provide online Motif-based help nsr_shutdown Executable file for killing NetWorker processes running on the NetWorker server nsr_support Executable file for collecting configuration information from the customer system that can be forwarded to the DIGITAL Customer Support Center nsradmin Executable file for activating a character- based program for system administration nsralist Archive request executor nsrarchive Executable file for archiving files nsrck Executable file for checking and repairing server indexes nsrclone Save set cloning command (continued) 70 Files Installed on Your System Table 7 Installed NetWorker Files -- Server (cont.) File Description nsrd NetWorker server daemon nsrexecd Daemon used for enhanced security of remote logins nsrexecd.sh Setup script to define NetWorker server as a client of another NetWorker server nsrfile Module to aid in writing shell script ASMs nsrhsmck HSM consistency checker nsrib HSM index browser nsriba HSM index browser agent nsrim Executable file for managing NetWorker's online file and media indexes nsrindexasm Executable file for saving and recovering NetWorker indexes nsrindexd NetWorker index daemon nsrinfo Executable file for reporting the contents of a client file index nsrjb Executable file for managing jukeboxes for the NetWorker server nsrls Executable file for listing the statistics of NetWorker index files nsrmig Executable file for migrating files for long- term storage with HSM. nsrmm Executable file for the NetWorker media interface nsrmmd NetWorker media management daemon nsrmmdbasm Executable file for saving and recovering NetWorker media databases (continued) Files Installed on Your System 71 Table 7 Installed NetWorker Files -- Server (cont.) File Description nsrmmdbd NetWorker media index daemon nsrpmig Executable file for premigrating (copy file) files for long-term storage with HSM nsrretrieve Executable file for retrieving archived data nsrtrap Mechanism for sending NetWorker notifications using the SNMP trap mechanism nsrwatch Executable file for displaying NetWorker server status from an ASCII terminal nwadmin Executable file for activating a Motif-based program for system administration nwarchive Executable file for activating a Motif-based program for controlling archiving activities nwbackup Executable file for activating a Motif-based program for backup functions nwrecover Executable file for activating a Motif-based program for recover functions nwretrieve Executable file for activating a Motif-based program for retrieving archived data rawasm Module for saving to and from raw disk devices recover Executable file for browsing the online indexes and recovering files from the NetWorker server relem Sends a READ ELEMENT STATUS command to all or a specified media changer save Executable file for saving files to the NetWorker server savefs Executable file for saving filesystems to the NetWorker server savegrp Executable file for saving the files of a group of NetWorker clients (continued) 72 Files Installed on Your System Table 7 Installed NetWorker Files -- Server (cont.) File Description scanner Executable file for reading the contents of a volume that will be recovered from a NetWorker server crash sjiielm Tests the Initialize Element Status interface for a jukebox sjiinq Returns a string identifying an SJI-compliant jukebox sjirdp Returns the ordinal device positions from an SJI-compliant jukebox sjirdtag Reads and displays media presence and tag data from an SJI-compliant jukebox sjirelem Reads and displays media presence and origin data from an SJI-compliant jukebox sjirjc Reads and displays internal configuration information and options from an SJI-compliant jukebox ssc Executable file for performing save set consolidation tapeexercise Writes sample data to a tape, and tests to see if position and read operations perform as expected. Read the reference page before using this command tarasm Module for saving and recovering using the tar command tarsum Calculates checksum of a tar stream while the tar command is running tur Sends a TEST UNIT READY command to all or a specified SCSI device attached to the system uasm Executable file for saving and recovering generic UNIX files vjb_config Program for customer support vjb_contents Program for customer support Files Installed on Your System 73 Files Installed on DIGITAL UNIX Client Systems Table 8 lists and describes the files associated with the DIGITAL UNIX client installation. When you initially load these files onto the NetWorker server, NetWorker places them in a tar file in the directory /usr/opt/BRX440/BRXCKIT440. Later, when you install the files on the client system, these files reside in a directory that you specify during installation. Table 8 Installed NetWorker Files -- DIGITAL UNIX Client File Description hideasm Module for saving and recovering without creating index entries mminfo Executable file for reporting media information mmlocate Executable file for accessing and managing the volume location information contained in the media databases mmpool Executable file used to display pool information stored in the media database nsr.help A help file used by the executable NetWorker software to provide online Motif-based help nsr_ize Executable file for installing or removing NetWorker software files to or from a machine. nsr_shutdown Executable file for killing NetWorker processes running on the NetWorker server nsr_support Executable file for collecting configuration information from the customer system that can be forwarded to the DIGITAL Customer Support Center nsradmin Executable file for activating a character- based program for system administration nsralist Archive request executor nsrarchive Executable file for archiving files nsrclone Save set cloning command (continued) 74 Files Installed on Your System Table 8 Installed NetWorker Files -- DIGITAL UNIX Client (cont.) File Description nsrexecd Daemon used for enhanced security of remote logins nsrhsmck HSM consistency checker nsrib HSM index browser nsriba HSM index browser agent nsrinfo Executable file for reporting the contents of a client file index nsrmig HSM migration utility nsrmm Executable file for the NetWorker media interface nsrpmig HSM premigration utility nsrretrieve Executable file for retrieving archived data nsrwatch Executable file for displaying NetWorker server status from an ASCII terminal nwadmin Executable file for activating a Motif-based program for system administration nwarchive Executable file for activating a Motif-based program for controlling archiving activities nwbackup Executable file for activating a Motif-based program for backup functions nwrecover Executable file for activating a Motif-based program for recover functions nwretrieve Executable file for activating a Motif-based program for retrieving archived data recover Executable file for browsing the online indexes and recovering files from the NetWorker server save Executable file for saving files to the NetWorker server (continued) Files Installed on Your System 75 Table 8 Installed NetWorker Files -- DIGITAL UNIX Client (cont.) File Description savefs Executable file for saving filesystems to the NetWorker server tarasm Module for saving and recovering using tar uasm Executable file for saving and recovering generic UNIX files 76 Files Installed on Your System Appendix C Client Installation Worksheet This appendix provides a template for the client installation worksheet described in Chapter 3. Use the client installation worksheet to organize the installation of NetWorker client software. Avoid writing on this template worksheet; instead, use this copy as a master from which you can make additional copies. See DIGITAL UNIX Client Installation for more information on using this worksheet. Illustration is not available in this format. Index FIS, 27 B backing up system disk, 5 H hardware requirements, 5 C highly available application, CD-ROM 34 installing from, 15 cluster server I client, 48 installation procedure configuring, 43 cluster server, 26 deinstall, 46 example, 61 example, 27 from a RIS server, 16 installation requirements, from CD-ROM, 15 25 monitoring displays during, license registration, 28 18 member name, 42 selecting subsets, 17 reinstall, 47 stopping, 13 relocate, 45 time required, 5 restart, 46 installation requirements shared tape service, 34 cluster server, 25 shut down, 46 disk space, 11 special device files, 33 hardware, 5 cluster shared bus, 33 login, 5 software, 7 D Installation Verification deinstall cluster server, 46 Procedure. See IVP deleting NSR, 53 IVP deleting old subsets, 9 running, 49 disk space requirements for local L installation, 11 License Management Facility. See LMF E license registration, 4, 28 error recovery, 13 LMF, 1 F R Factory Installed System. See reinstall cluster server, 47 FIS release notes files accessing from product installed on a DIGITAL UNIX directory, 54 client, 74 location on CD-ROM, 1 installed on server, 69 relocate cluster server, 45 software requirements, 7 removing NSR subsets, 53 special device files, 33 requirements. See start action script, 35 installation requirements stop action script, 35 restart cluster server, 46 stopping the installation, 13 RIS installation procedure, subsets 16 deleting old, 9 described, 10 S loading, 18 shared tape service selecting during creating, 35 installation, 17 setup, 34 system disk, backing up, 5 shut down cluster server, 46 80 Index Ordering Additional Information You can order additional user information electronically, by telephone, or by mailing an order. If you need help with your order, call 800-343-4040. Electronic Orders To place an order at the Electronic Store, dial 800-DEC-DEMO (800-332-3366) using a 1200- or 2400-bps modem. If you need assistance using the Electronic Store, call 800-DIGITAL (800- 344-4825). Telephone and Direct Mail Orders Your Location Call Contact Continental 800-DIGITAL Digital Equipment Corporation USA, PO Box CS2008 Alaska, or Nashua, NH 03061 Hawaii Puerto Rico 809-754-7575 Local DIGITAL subsidiary Canada 800-267-6215 Digital Equipment of Canada Attn: DECdirect Operation KAO2/2 PO Box 13000 100 Herzberg Road Kanata, Ontario, Canada K2K 2A6 International Local DIGITAL subsidiary or approved distributor Internal1 SSB Order Processing - NQO/V19 or U.S. Software Supply Business Digital Equipment Corporation 10 Cotton Road Nashua, NH 03063-1260 1For internal orders, you must submit on Internal Software Order Form (EN-01740-07). How Did We Do? Please take a moment to let us know whether the online and paper documentation that we provided with this product is useful to you. We are particularly interested in comments about clarity, organization, figures, examples (or the lack thereof), the index, page layout, and, of course, accuracy. When you send a comment, be sure to provide ample background information to help us locate the right source files. Include the product name and version, the document name, and the page number. Internet address: doc_comments@zso.dec.com Fax numbers: 800-DEC-FAXX (800-332-3299) 206-865-8890 Mailing address: Publications Manager Digital Equipment Corporation 14475 NE 24th Street Bellevue, WA 98007