Chapter 1. Installing NetWorker

This chapter describes the procedure for installing, licensing, enabling, and removing IRIX NetWorker 4.2.5-B.  The NetWorker software distribution CD-ROM contains all the software you need for Silicon Graphics servers and clients, including:

Licenses are required to enable the NetWorker server and the optional items.  Each NetWorker server and each autochanger require a license.  NetWorker software is license-protected with FlexLM™ nodelocked licenses.  The NetWorker distribution is shipped with a temporary license that enables full use of the basic NetWorker server for a short period until you obtain permanent licenses from Silicon Graphics.

Versions and Compatibility

The NetWorker 4.2.5-B server runs on IRIX 5.3 and above.  Refer to the IRIX NetWorker Release Notes for a list of IRIX patch requirements.  The server requires tertiary storage (such as a tape drive) and enough disk space to store the installation images and the indexes, which consume about 60 MB of disk space for each GB of backup data.


Caution: Server upgrades from NetWorker 4.1.3 (or 4.2.5) to NetWorker 4.2.5 -B are supported, but upgrades from earlier versions have not been tested.  NetWorker 4.2.5-B replaces NetWorker 4.2.5, and is compatible with NetWorker 4.2.9 Power Edition.

The NetWorker 4.2.5 client software runs on IRIX 5.x or IRIX 6.x.  Earlier versions of the NetWorker client are interoperable with later versions of the NetWorker server.

An IRIX NetWorker server can back up Silicon Graphics clients and client systems from other vendors as well.  NetWorker software for other vendors' clients, and installation information for those clients, is included in the NetWorker ClientPak, which is available either from Legato Systems or from Silicon Graphics.

NetWorker requires a no-rewind tape backup device (except for optical drives) because it writes a file mark on the backup volume at the end of each backup and then appends data based on the position of the file mark.  If a device rewinds, the file mark position is lost and previously written data is overwritten by the next backup.

Overview of Installation Procedures

To deploy NetWorker on Silicon Graphics servers, you must install the NetWorker server software, obtain licenses, and enable the server and its optional components.  To back up the local disks of workstations across the network, you must also install NetWorker client software on each workstation.

  • For instructions on installing the NetWorker server, see the section “Installing and Enabling NetWorker Servers”.

    • Use the inst command to install NetWorker server software.

    • Obtain permanent licenses from Silicon Graphics, and use the LicenseManager command to activate these licenses.

    • Enable the permanent licenses using the nsrcap command.  Permanent licenses replace the temporary license.

  • For instructions on installing the NetWorker clients, see the section “Installing Client Software”.

    • Use the inst command to install NetWorker client software.

    • No license is necessary, but network configuration is advised to that clients can quickly recognize the NetWorker server.


Note: NetWorker ClientPak products may include older versions of client software for Silicon Graphics workstations.  For the most up-to-date NetWorker client software, please install from the IRIX NetWorker CD-ROM instead of from the ClientPak.


Installing and Enabling NetWorker Servers

To install and enable NetWorker, you perform these tasks:

Installing NetWorker Servers

To install NetWorker on an IRIX server, you need a filesystem on the server with enough free disk space to store both NetWorker and its indexes.  For each client (including the server itself), the size of the indexes on the server is approximately 2% of the disk space in use on the client, assuming average-size files and the default backup schedule.


Caution: Upgrading from NetWorker 4.1.3 to 4.2.5-B converts indexes to a new format, and is irreversible (4.2.5-B index format is the same as 4.2.5 and 4.2.9).  Before upgrading, the NetWorker server should have as much free disk space on the /nsr partition as the indexes currently consume, since index size can nearly double during conversion.

Follow this procedure to install Networker server software:

  1. Load the IRIX NetWorker software distribution CD-ROM.

  2. On the NetWorker server, switch user to root.

    % /bin/su - 
    Password:
    

    If you are upgrading from an older version of NetWorker, stop the daemons now, and make a copy of the /nsr partition, for example using xfsdump:

    # /etc/init.d/networker stop 
    # xfsdump -f /dev/tape -J /nsr 
    

  3. Run the inst command, specifying the location of the NetWorker distribution:

    # inst -f /CDROM/dist 
    inst> list 
    

  4. Select subsystems inside inst.  Use Table 1-1 as a guide to selecting product images.  For example, to install the software, reference pages, release notes, and the InSight versions of two NetWorker manuals, enter these commands:

    Inst> keep * 
    Inst> i networker4.sw.server networker4.sw.client 
    Inst> i networker4.man.* *.books.NetWorker_UG *.books.NetWorker_AG 
    

    For more information on the available product images, refer to the IRIX NetWorker Release Notes.  For details about inst, refer to IRIX Admin: Software Installation and Licensing, or see the inst(1M) reference page.

    Table 1-1. Subsystems for NetWorker Servers

    Subsystem

    Description

    Required/Optional

    networker4.sw.server

    NetWorker server software for system performing backups

    Required

    networker4.sw.client

    NetWorker client software for IRIX 5.x and IRIX 6.x

    Required (Default)

    networker4.man.server

    Reference pages for NetWorker server software

    Optional

    networker4.man.client

    Reference pages for NetWorker client software

    Optional (Default)

    networker4.man.relnotes

    Release notes

    Optional (Default)

    networker4.books.NetWorker_UG

    Online version of the IRIX NetWorker User's Guide

    Optional; IRIS InSight is a prerequisite (Default)

    networker4.books.NetWorker_AG

    Online version of the IRIX NetWorker Administrator's Guide

    Optional; InSight needed

    networker4.books.NetWorker_IG

    Online version of this book

    Optional; InSight needed

    networker4.sw.archive

    Archive and retrieve client

    Optional; license required

    networker4.man.archive

    Reference pages for Archive

    Optional

    networker4.sw.DMO

    Database Module for Oracle

    Optional; license required

    networker4.books.NetWorkerDMO

    Online version of the IRIX NetWorker BusinesSuite Module for Oracle Administrator's Guide

    Optional; InSight needed


  5. Perform the installation and exit inst:

    Inst> go 
    ...
    Inst> quit 
    


    Note: If /nsr already existed and you want to evaluate NetWorker using temporary licenses, you must delete all existing files and directories under /nsr now.


  6. Choose a filesystem for the NetWorker index files.  You can use part of an existing filesystem or dedicate a filesystem (typically called /nsr).


    Caution: If you are upgrading from NetWorker 4.1.3 to NetWorker 4.2.5-B, you need as much free space on /nsr as the largest client index, because conversion involves making a copy of the index.  More space is highly recommended, especially to allow index conversion in parallel.  Running out of space results in a hung server.


  7. If you choose a non-root partition instead of a dedicated /nsr filesystem, create a symbolic link so NetWorker knows where to place the index files.  For directory, substitute the relative pathname of a directory on that filesystem, such as ./bigfs/nsr on the /bigfs filesystem.

    # ln -s directory /nsr 
    

    If you are upgrading from an older version of NetWorker, expedite the conversion by running nsrck on each client index; see nsrck(1M) for more information:

    # nsrck -D 10 client 
    nsrck: checking index for client ...
    

  8. Start the NetWorker daemons with this command:

    # /etc/init.d/networker start 
    

At this point, the NetWorker server is ready for a test drive as described in Chapter 2.  Out of the box, NetWorker operates in evaluation mode using temporary licenses.  Because licenses have not yet been installed and enabled, you can ignore the following messages, which eventually appear in /var/adm/SYSLOG and in mail sent to root:

Subject: registration status for client 
NetWorker Registration: (notice) server disabled. Install base enabler.
NetWorker registration: (info) Server is disabled (Base expired).

Within 30 days after you install the NetWorker server, you must license it by following instructions in the sections below.  If your NetWorker server supports networked clients, you must inform some network naming service by following instructions in the section “Configuring Clients to Recognize the Server”.

Licensing NetWorker Servers

All NetWorker products are included on the NetWorker software distribution CD-ROM.  Table 1-2 lists NetWorker products, their features, and licensing information.

Table 1-2. Licensed NetWorker Products

Product

Description

Licensing Information

IRIX NetWorker
Network edition

Supports 10 or fewer networked clients, up to 32 backup or recover sessions, and up to 16 concurrent devices (tape drives).

IRIX NetWorker license is required on each NetWorker server.

IRIX NetWorker
Server edition

No built-in client support.  An upgrade makes this identical to network edition.

No clients—primarily intended for backing up single servers.

IRIX NetWorker
Power edition

Provides support for high-speed backup and high-capacity devices.

This license is required for NetWorker server version 4.2.9.

 

Autochanger Software Module

Enables use of tape libraries and disc jukeboxes.  Available for 1-8 slots, up to 16 slots, up to 32 slots, up to 64 slots, up to 128 slots, up to 256 slots, and more than 256 slots (upgrades possible).

A separate autochanger license (for the appropriate number of slots) is required for each connected tape library or disc jukebox.

Archive Module

Provides file archiving and optional grooming and verification.

Client licenses not required, although archive server must be licensed.

BusinesSuite Module for Oracle

Provides a NetWorker connection from the Oracle Enterprise Backup Utility.

License required for each Oracle database server (per hostname).

Database Module for Informix

Provides a NetWorker connection from Informix Online Backup and Restore.

License required for each Informix database server (per hostname).

Server edition upgrade

Server edition becomes Power edition.

Same as NetWorker Power edition.

Nework edition upgrade

Network edition becomes Power edition.

Same as NetWorker Power edition.

5 Client Connection

Supports 5 additional clients

Additive up to a maximum of 1000.

25 Client Connection

Supports 25 additional clients

Additive up to maximum of 1000.

100 Client Connection

Supports 100 additional clients

Additive up to maximum of 1000.

ClientPak Software Module

Allows client to perform backups to, or administer, the NetWorker server.  Also available from Legato Systems.

Available for many UNIX systems, various PC desktops, Windows NT, NetWare, and Macintosh.

When you purchase IRIX NetWorker server or any of the related optional products, you must enable them by installing and activating FlexLM licenses.

Evaluating NetWorker—Temporary Licenses

The software distribution CD-ROM is shipped with evaluation mode, which provides a temporary NetWorker network edition license, a temporary license for an autochanger with 1-16 slots, and a temporary Archive license.  These licenses allow you to use these products on any Silicon Graphics server for a short period.


Note: If you are evaluating NetWorker, do not run the nsrcap command as shown in the steps below, because it disables the temporary licenses that permit evaluation mode.


Obtaining Permanent Licenses

To continue using NetWorker products, before the temporary licenses expire, you must obtain a permanent, nodelocked license for each NetWorker product you purchase.  To do so, either point your Web browser at http://www.sgi.com/Products/license.html and fill out the forms, or send e-mail to license@sgi.com.  Both the Web page and e-mail form ask you to provide proof of purchase.

If you lack Internet access, you may telephone the 1-800-800-4SGI hotline within the United States, or your local sales office elsewhere.

Inserting Permanent Licenses

If LicenseManager is installed on your server (the default in IRIX 6.2), click the Web site's AUTO_INSTALL button, or double-click the e-mail attachment from license@sgi.com, to have LicenseManager automatically install licenses in the /var/flexlm/license.dat file.

If you received e-mail without an installation script, or encounter a Web site without the AUTO_INSTALL button, use your favorite editor to copy and paste the appropriate license lines into the NetWorker server's /var/flexlm/license.dat file.

The Product Name list in Figure 1-1 shows two NetWorker licenses as they appear after installation, one license for the Archive option, and one for the NetWorker server (network edition with 10 clients).

Figure 1-1. LicenseManager Interface

Figure 1-1 LicenseManager Interface

The next two sections describe how to enable NetWorker server software by activating licenses.  The section “Enabling Server Software Except Autochangers” explains how to enable all server software except for jukeboxes.  The section “Enabling Autochangers” explains how to enable jukebox licenses.

If you plan to run NetWorker in conjunction with an autochanger (also called a jukebox or robotic library), skip to “Enabling Autochangers”.

Enabling Server Software Except Autochangers

Follow the steps below to enable all NetWorker server software except jukebox support.  This procedure can be used when the software is initially installed and when you add new licenses, for example, after purchasing the NetWorker 25 Client Connection for an existing NetWorker server.

To enable NetWorker on regular backup devices, follow these steps:

  1. Make sure you have purchased and installed FlexLM permanent nodelocked licenses as described in the previous section.

  2. Switch user to root on the NetWorker server.

    % /bin/su - 
    Password:
    

  3. If the subsystem license_eoe.sw.flexlm_utils is not already installed, use the inst command to install it from the IRIX system software CD-ROM.

  4. Verify that the NetWorker licenses were installed in /var/flexlm/license.dat.  For example, that file should contain lines like these:

        FEATURE NW_BASE sgifd 4.000 1-jan-0 0 AC215525CE8EFE18215D \
            VENDOR_STRING=NETWORK_EDITION HOSTID=#1762217977 \
            vendor_info="NetWorker Network Edition" \
            ISSUER="Silicon Graphics, Inc." 
    

  5. Start NetWorker:

    # /usr/etc/nwadmin & 
    

  6. Activate the FlexLM licenses by running the nsrcap command (see nsrcap(1M) for more information):

    # /usr/etc/nsrcap -v 
    No license is available for feature
    ...
    Found 1 FlexLM license for feature NW_BASE/NETWORK_EDITION
    ...
    Found a FlexLM license for installation:
            name:    NetWorker, Network Edition
            enabler code: AC215525CE8EFE18215D
            license type: B1
            expires:      14299 days (Feb 06, 2036)
    

    The nsrcap output lists the licenses you installed.  These licenses are now activated.


    Note: If you have the Registration window open from the nwadmin command when you activate NetWorker licenses with nsrcap, close it to refresh the window.

    If you are upgrading from an older version of NetWorker, check the Server window for values of Parallelism and Sessions per device, which might not have been correctly preserved during upgrade.

Enabling Autochangers

The procedure for enabling an Autochanger Software Module differs from the procedure for enabling other NetWorker software in that it uses the jbm_enabler command.  Use the procedure in this section to enable each Autochanger Software Module you purchase, either initially, or later as you add upgrades.

To enable NetWorker on jukebox devices, follow these steps for each autochanger:

  1. Switch user to root and run the jbm_enabler command to tell NetWorker about the autochanger; see jbm_enabler(1M) for details.  This command queries the system for jukebox devices, and returns a list of the ones it found.  For example:

    # /usr/etc/jbm_enabler 
    Enter the number of the type of jukebox you are installing:
     1) /dev/scsi/sc2d3l0    : DLT2700/DLT2700XT/DLT2500XT
    Choice? 1 
    Installing DLT2700/DLT2700XT/DLT2500XT jukebox (/dev/scsi/sc2d3l0).
    Name you would like to assign to the jukebox device? DLT 
    Do you want automated device cleaning support enabled? (yes/no) no 
    Looking for tape devices...
    Following tape devices have been found:
    *   1) /dev/rmt/tps2d3nrnsv : dlt
    Choice for media drive 1? [1] 1 
    Jukebox has been added successfully
    


    Note: Automated device cleaning is recommended for devices that lack an indicator for when they need cleaning.

    The numbers that you enter for the slots represent a range of slots, not the total number of slots available.  Entering a single slot number means that only a single slot would be used for backup and recovery with NetWorker.

    If jbm_enabler fails to find all the autochangers connected to a system, you can disable automatic recognition as follows:

    # /usr/etc/jbm_enabler -noauto 
    Enter the number of the type of jukebox you are installing:
             1) DLT2700/DLT2700XT/DLT2500XT
             2) DLT4700XT/DLT4500XT
             3) ATL/Odetics 2640
             4) Spectra Logic SL-4000
             5) Breece-Hill Q7
             6) Breece-Hill Q47
             7) Qualstar TLS-4210
             8) IBM 3590
             9) STK-9704/Lago 340
            10) STK-9708/STK-9711/Lago 380
            11) STK-9710
            12) EXB-10e/EXB-10h
            13) EXB-10i
            14) EXB-210
            15) EXB-400 Series
            16) HP-C1553A/Surestore 12000e
            17) other
    Choice?
    


    Note: The list of supported jukebox types is subject to change.


  2. Verify that the NetWorker jukebox licenses were installed in /var/flexlm/license.dat.  For example, that file should contains lines like these:

        FEATURE NW_BASE sgifd 4.000 1-jan-0 0 AC215525CE8EFE18215D \
            VENDOR_STRING=NETWORK_EDITION HOSTID=#1762217977 \
            vendor_info="NetWorker Network Edition" \
            ISSUER="Silicon Graphics, Inc." 
        FEATURE NW_AUTO sgifd 4.000 1-jan-97 0 DCE11347B151837A0F44 \
            VENDOR_STRING=SLOTS=8 HOSTID=ANY vendor_info="NW Autochg <=8 slots" \
            ISSUER="Silicon Graphics, Inc." 
    

  3. Start NetWorker:

    # /usr/etc/nwadmin & 
    

  4. Activate the license by running the nsrcap command:

    # /usr/etc/nsrcap -v 
    No license is available for feature
    ...
    Found 1 FlexLM license for feature NW_BASE/NETWORK_EDITION
    Found 1 FlexLM license for feature NW_AUTO/SLOTS=8
    ...
    Found a FlexLM license for installation:
            name:    NetWorker, Network Edition
            enabler code: AC215525CE8EFE18215D
            license type: B1
            expires:      14299 days (Feb 06, 2036)
    Found a FlexLM license for installation:
            name:    NetWorker Autochanger, 8 slots
            enabler code: DF215525CE8EFE18215G
            license type: J8
            expires:      14299 days (Feb 06, 2036)
    


    Note: If you have the Registration window open from the nwadmin command when you activate NetWorker licenses with nsrcap, close it to refresh the window.

    If you are upgrading from an older version of NetWorker, check the Server window for values of Parallelism and Sessions per device, which might not have been correctly preserved during upgrade.

Installing and Enabling NetWorker on Clients

To install and enable NetWorker clients, you must perform these tasks:

NetWorker clients do not require a license.  However, the total number of NetWorker clients may not exceed the maximum number of client connections licensed for the NetWorker server.  Additive client licenses are available in units of 5, 25, and 100, and may be applied in any combination.

Installing Client Software

Follow the steps in this section to install Networker client software.  No enabling of the client software is required.

  1. On the client, become root and invoke the inst command, specifying the location of the NetWorker software distribution:

    % /bin/su - 
    Password:
    # inst -f /CDROM/dist 
    Inst> list 
    

  2. Select subsystems inside inst.  Use Table 1-3 as a guide to selecting product images.  Subsystems not listed below are never needed on NetWorker clients.  For example, to install the required client software, the reference pages, and the IRIS InSight version of the NetWorker user manual, enter these commands:

    Inst> keep * 
    Inst> install networker4.*.client 
    Inst> install networker4.books.NetWorker_UG 
    

    For additional information on the available NetWorker product images, refer to the IRIX NetWorker Release Notes.

    Table 1-3. Subsystems for NetWorker Clients

    Subsystem

    Description

    Required/Optional

    networker4.sw.client

    NetWorker client software

    Required

    networker4.man.client

    Reference pages for client

    Optional

    networker4.books.NetWorker_UG

    Online IRIX NetWorker User's Guide

    Optional; recommended

    networker4.books.NetWorker_AG

    Online copy of the IRIX NetWorker Administrator's Guide

    Optional; useful for system administrators

    networker4.sw.archive

    Archive and retrieve client software

    Optional; license needed to enable server Archive

    networker4.man.archive

    Reference pages for Archive option

    Optional


  3. Perform the installation and exit inst:

    Inst> go
    Inst> quit
    

  4. Check to see if the hostname alias nsrhost has been set to your NetWorker server:

    # /usr/etc/ping -c1 nsrhost 
    PING b2.mktg.corp.com (199.99.172.4): 56 data bytes
    64 bytes from 199.99.172.4: icmp_seq=0 ttl=252 time=4 ms
    ...
    

    In this command, the -c argument is followed by a numeral 1 to indicate only one ping request.  The first line of output should contain the name of the NetWorker server aliased to nsrhost, in this case b2.mktg.corp.com.

    If the output does not contain the name of the NetWorker server, commands such as the nwadmin do not automatically connect to the NetWorker server; users must bring up the Change Server dialog box to specify a server, or run nwadmin with the -s option to specify server name.

    To set the hostname alias nsrhost to your NetWorker server, follow the directions in the section “Configuring Clients to Recognize the Server” below.


Note: In IRIS FailSafe clusters, mounted filesystems are not always listed in /etc/fstab. To have NetWorker back up nonexplicit filesystems, list them in /etc/fstab with the noauto keyword in the options field:


/dev/dsk/dks1d2s7   /spare   xfs   noauto,rw

Configuring Clients to Recognize the Server

The clients on the network can be configured so that when they use the nwbackup or nwrecover commands (and with the Archive programs, nwarchive or nwretrieve), NetWorker automatically points to their server.  If clients are not configured this way, users must use the Change Server dialog box to specify their server, or run NetWorker commands with the -s option to specify server name.  Configure clients by defining a host alias called nsrhost that can be resolved by each client to be the name of their NetWorker server.

Configuring clients to recognize the NetWorker server can be done in these ways:

For more information about how clients bind to NetWorker servers, see the introductory reference page, nsr(1M).

Using NIS to Configure Clients

If you have NIS on the network, follow these steps to configure clients to recognize the NetWorker server:

  1. Identify the NIS master for each client using the ypwhich command on each client; see ypwhich(1) for more information:

    % ypwhich -m hosts
    ypmaster
    

    In this example, ypmaster is the master NIS host for the client.

  2. As superuser on each of the master NIS hosts, edit the /etc/hosts file, adding nsrhost as an alias after the original hostname of the NetWorker server.  For example:

    199.99.172.4    b2 nsrhost
    


    Note: Only one host in /etc/hosts should have the nsrhost alias.  If several NetWorker servers back up files on clients served by a single NIS master host, some users may have to specify their server by choosing Change from the Server menu (or with the Change Server button) of nwbackup and nwrecover.


  3. As superuser on each of the master NIS hosts, change directory to /var/yp and run the ypmake command (see ypmake(1M) for details):

    # cd /var/yp 
    # ./ypmake 
    

  4. To verify that each client can recognize the NetWorker server, enter this command on each client after waiting a suitable period for the NIS databases to propagate:

    # ypmatch nsrhost hosts 
    199.99.172.4    b2 nsrhost
    

    The hostname listed in the output should be the name of the NetWorker server.

Configuring Clients Without NIS or DNS

This section describes the procedure for configuring a client to recognize the NetWorker server when NIS and DNS (BIND) are not used on the network.  This procedure can also be used if NIS or DNS is in use on the network.

Follow these steps to hand-configure clients to recognize the NetWorker server:

  1. As superuser on each NetWorker client, edit the /etc/hosts file, adding nsrhost as an alias next to the NetWorker server name:

    199.99.172.4    b2 nsrhost
    

    In this example, the client will be backed up by the NetWorker server named b2.


    Note: If you have purchased NetWorker for more than one server, only one host should have the nsrhost alias in each client's /etc/hosts file.


  2. If NIS and/or DNS are in use on the network, verify that nsrhost is correctly aliased:

    # /usr/etc/ping -c1 nsrhost 
    PING b2.mktg.corp.com (199.99.172.4): 56 data bytes
    64 bytes from 199.99.172.4: icmp_seq=0 ttl=252 time=4 ms
    ...
    

    In the command, the -c argument is followed by a numeral 1 to indicate only one ping request.  The first line of output should contain the name of the NetWorker server aliased to nsrhost, in this case b2.mktg.corp.com.  If the output does not contain the name of the NetWorker server, modify the client's /etc/resolv.conf file so that the local /etc/hosts file is checked before NIS or BIND.  See the resolver(4) reference page for more information.

Removing NetWorker

If you want to remove the NetWorker software and data files from a server system, follow these steps:

  1. Shut down the NetWorker daemons using the following command:

    # /etc/init.d/networker stop 
    

  2. Use the versions command to remove the NetWorker software; see versions(1M) for more information. For example, to remove all the software, enter this command:

    # versions remove networker4 
    

    If you want to remove just the NetWorker server, leaving the client software, enter this command:

    # versions remove "networker4.*.server" 
    

    Also remove NetWorker software on network clients using the versions command.

  3. Remove the NetWorker configuration files and index files by entering these commands:

    # rm -r /nsr/* 
    # rmdir /nsr 
    

    If /nsr is a symbolic link to another filesystem, remove the symbolic link as well.

    If you want to continue running the NetWorker client, start the nsrexecd daemon using the following command:

    # /etc/init.d/networker start 
    

    The NetWorker client re-creates the /nsr directories as needed.