This chapter describes the procedure for installing and licensing NetWorker 4.1.1 for IRIX on NetWorker servers and clients. The NetWorker software distribution CD-ROM contains all the software you need for Silicon Graphics servers and clients, including
IRIX NetWorker, which supports 10 or fewer clients and one or two tape drives
options for additional client connections in additive units of 5, 25, or 100
the NetWorker TurboPak option, which supports archive services, save set cloning, concurrent device support, autochanger support, and parallel backup and recovery
ClientPak Software option
Autochanger Software Module options
Licenses are required to enable each of these items except the ClientPak Software option.
NetWorker server software is license-protected with NetLS™ node-locked licenses, so the NetWorker software distribution is shipped with a temporary license that enables you to use all NetWorker features to back up a maximum of 10 clients for a short period until you obtain permanent licenses from Silicon Graphics. Additional client connections are separate licenses; each server and each autochanger require a license.
This chapter explains how to install NetWorker software on Silicon Graphics servers and clients, and how to install and activate the licenses that enable the server software. The basic steps are as follows:
For the server:
Use inst(1M) to install NetWorker software on servers. This procedure is described in the section “Installing Server Software.”
Enable NetWorker server software by following the directions in the section “Enabling Server Software.”
Follow the directions included with the NetWorker package to obtain permanent licenses from Silicon Graphics, if you did not install permanent licenses earlier.
Install permanent licenses to replace temporary licenses on the appropriate servers by again using the procedure in the section “Enabling Server Software.”
For the client:
Use inst(1M) to install NetWorker software on clients. This procedure is described in the section “Installing NetWorker Software on Clients.”
Configure each client to recognize its NetWorker server by following the directions in the section “Configuring Clients to Recognize the Server.” No licenses are required on clients.
A Silicon Graphics NetWorker server can back up other vendors' systems as well as Silicon Graphics clients. NetWorker software for those clients and installation information for those clients is included in NetWorker ClientPak products, which are available from Silicon Graphics.
To install and enable NetWorker software on servers, you must perform these three tasks:
Install NetWorker software on servers, as described in the section “Installing Server Software.”
Install and activate licenses and perform other tasks to enable the NetWorker products, as described in the section “Enabling Server Software.”
Configure network information service (NIS) master hosts or other systems so that clients can recognize the NetWorker servers, as described in the section “Configuring Clients to Recognize the Server.”
If you have purchased the optional Archive product (in TurboPak) and you are using an autochanger (jukebox or tape library), it is a good idea to premount an archive volume in one of the slots.
To install NetWorker on a server, you need:
IRIX Release 5.3 or 6.0.x running on the server
A filesystem on the server with enough free disk space to store the NetWorker 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, presuming average-size files and the default backup schedule.
![]() | Caution: If you are upgrading from NetWorker 4.0.x, you cannot go back to the earlier version once you have upgraded to 4.1.1, because upgrading changes the index files. |
Follow this procedure to install Networker server software:
On the server, become root and enter the inst(1M) command:
% /bin/su - Password: # inst |
Specify the location of the NetWorker software distribution and get a list of the subsystems, for example:
Inst> from /CDROM/dist Inst> list |
For additional information on Inst, see the Software Installation Administrator's Guide.
Make subsystem selections in Inst. Use Table 2-1 to guide you in selecting subsystems. Subsystems not listed in Table 2-1 should not be installed on servers. For example, to install the required software, the reference pages, the release notes, and the InSight versions of the NetWorker manuals, enter these commands:
Inst> keep * Inst> install networker4.*.server networker4.*.client_5 Inst> install networker4.man.relnotes |
For additional information on these subsystems, see the IRIX NetWorker Release Notes.
Table 2-1. Subsystems for NetWorker Servers
Subsystem | Description | Required/Optional |
---|---|---|
networker4.sw.server | NetWorker server software | Required |
networker4.sw.client_5 | NetWorker client software for IRIX 5.3 and 6.x | Required for IRIX 5.3 and 6.x systems |
networker4.sw.client_4 | NetWorker client software for IRIX 4.x | Required for IRIX 4.x systems |
networker4.man.server | Reference pages for NetWorker server software | Optional |
networker4.man.client_5 | Optional | |
networker4.man.relnotes | Release notes | Optional |
networker4.books.NetWorker_UG | InSight version of the IRIX NetWorker User's Guide | Optional; requires IRIX 5.0 or later |
networker4.books.NetWorker_AG | InSight version of this guide | Optional; requires IRIX 5.0 or later |
networker4.sw.archive.server_5 | Optional archive and retrieve software for server | Requires purchase of TurboPak option |
Perform the installation and exit inst:
Inst> go Inst> quit |
Choose a filesystem for the NetWorker index files. As a rule of thumb, the amount of disk space used by the index files is about 2% of the amount of disk space used by the backed up files, presuming average-size files and the default backup schedule. You can use part of a filesystem, or dedicate a filesystem. Dedicated filesystems are typically called /nsr.
If you've chosen a filesystem other than a dedicated filesystem named /nsr, use this command to tell NetWorker where to put the index files:
mars# ln -s directory /nsr |
directory is the name of a directory in the filesystem you've chosen for the index files, for example, /bigfs/nsr.
Start NetWorker daemons with this command:
mars# /etc/init.d/networker start |
Because the licenses haven't been enabled yet with the nsrcap command (see the next section, “Enabling Server Software”), these messages, which can be ignored, appear in /var/adm/SYSLOG and in mail sent to root:
NetWorker Registration: (notice) server disabled; No valid Base or Advanced licenses found, nsrd: either install new licenses or recover a valid resource file. (15017) NetWorker registration: (info) Server is disabled (Install base enabler). |
If this is the first time that NetWorker has been installed on this system, you may also see this message, which you can also ignore:
Verification could not mount '/nsr/mm/mmvolume' |
After you install software on the server, you must enable it by following the instructions in the next section, and you must ensure that clients can recognize the hostname alias nsrhost by following the instructions in “Configuring Clients to Recognize the Server,” later in this chapter.
When you purchase any of the NetWorker products, you must enable them on servers by installing NetLS licenses and activating the licenses with the nsrcap(1M) command.
All NetWorker products are included on the NetWorker software distribution CD. Table 2-2 lists the NetWorker products, their features, and licensing information.
Table 2-2. Licensed NetWorker Products
The software distribution CD-ROM is usually shipped with a temporary NetWorker IRIX NetLS license, a temporary NetLS license for an autochanger with 1-16 slots, and a temporary license for the NetWorker TurboPak option. These licenses allow you to use these products on any Silicon Graphics system for a short period.
To continue to use NetWorker products after the temporary licenses expire, you must obtain a permanent, node-locked license for each NetWorker product you purchase. If you do not already have the appropriate licenses for your NetWorker product(s), see Network License System Administration Guide and the IRIX NetWorker Release Notes for information on obtaining licenses. Additional information on installing NetLS licenses is available in the Network License System Administration Guide.
The next two sections describe how to enable NetWorker server software by installing and activating NetLS licenses. The section “Enabling Server Software Except Autochangers” explains how to enable all server software except the NetWorker Autochanger Software Module. The section “Enabling Autochangers” explains how to enable IRIX NetWorker Jukebox options.
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 upgrades are added, for example when a license for the Networker 25 Client Connection is added to the system.
Find the NetWorker NetLS license information stickers or sheets in your package. (Purchase the licenses from the Silicon Graphics licensing organization.)
Become root on the NetWorker server.
mars% /bin/su - Password: |
If the subsystem netls_eoe.sw.netls_eoe is not already installed, use inst to install it from the IRIX CD that you used when installing the system software on the server.
To begin entering license information, edit /var/netls/nodelock. For example:
#:# “Silicon Graphics” “NetWorker TurboPak” “A” “1995/05/29” 546fb4684914.02.c0.1a.3d.52.00.00.00 svav6qttzsd78c5ja75ukmia #:# “Silicon Graphics” “NetWorker Autochanger/16” “A” “1995/05/29” 546fb4684914.02.c0.1a.3d.52.00.00.00 zi3xheugrikecc5ja75ukmia #:# “Silicon Graphics” “Networker 4.1.1 Archive Option” “4.1.1” “1995/04/06” 546fb4684914.02.c0.1a.3d.52.00.00.00 xjzihimf6varac5ja75ukx2a 546fb4684914.02.c0.1a.3d.52.00.00.00 925gbqbqmxkgqc9999998mia # Desks A 1995/05/15 |
Using the information from the license information sheet, fill in the Product Name, Version, Expiration Date, and License Password fields.
Start NetWorker:
# /usr/etc/nwadmin &
|
Activate the licenses by running the nsrcap command as root:
mars# /usr/etc/nsrcap -v Found a NetLS license for installation: name: NetWorker /10 enabler code: 2b2d6b-a3b02d-6a9c80 license type: B10 expires: 990 days (Nov 18, 1996) |
The output of nsrcap lists each license you installed. These licenses are now activated.
![]() | Note: If you have the Registration window open at the time you activate NetWorker licenses with nsrcap, close it to refresh the window. |
The procedure for enabling a NetWorker Autochanger Software Module differs from the procedure for enabling other NetWorker software. Use the procedure in this section to enable each Autochanger Software Module you purchase. You can use this procedure to enable when you install NetWorker initially and to enable autochangers that you add later as upgrades.
Follow this procedure for each autochanger:
Run the jbm_enabler(1M) command as root to tell NetWorker about the autochanger (jukebox or tape library). For example:
![]() | Note: The list of supported jukebox types is subject to change. |
The numbers that you enter for the slots represent a range of slots, not the total number of slots available. Usually, for a jukebox, you do not enter a single slot number. Entering a single slot number means that only a single slot would be used for backup and recovery with NetWorker.
To begin entering license information, edit /var/netls/nodelock, as explained in“Enabling Server Software Except Autochangers,” earlier in this chapter.
Start NetWorker:
# /usr/etc/nwadmin &
|
Activate the license by running the nsrcap command as root:
mars# /usr/etc/nsrcap -v Found a NetLS license for installation: name: JSM-10 enabler code: 2b2d6b-a3b02d-6a9c80 license type: J10 expires: 990 days (Nov 18, 1996) |
![]() | Note: If you have the Registration window open in the NetWorker Administration program (nwadmin) when you enable a NetWorker license with nsrcap, close it to refresh the window. |
The clients on the network can be configured so that when they use the nwbackup and nwrecover commands (and, if TurboPak and an archive license have been purchased, the nwarchive and nwretrieve commands), it automatically points to their server. (If clients are not configured this way, users must use the “Change Server” command or speed button to specify their server.) Configure the clients by defining a hostname 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:
If your network uses the network information service NIS, use the section “Using NIS to Configure Clients.”
If your network uses the Domain Network Service (DNS), refer to the documentation on the BIND Name Server in the IRIS Advanced Site and Server Administration Guide.
If your network uses neither NIS nor DNS, use the section “Configuring Clients Without NIS or DNS.”
For more information about how clients bind to NetWorker servers, see the nsr(1M) reference page.
If you have NIS on the network, follow these steps to configure clients to recognize the NetWorker server:
Identify the NIS master for each client by using the ypwhich(1) command on each client:
jupiter% ypwhich -m hosts venus |
In this example, venus is the master NIS host for the client jupiter.
As root on each of the master NIS hosts, edit the /etc/hosts file, adding nsrhost as an alias next to the name of the NetWorker server. For example:
137.69.1.3 mars 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 using the “Change Server” command on the Server pulldown menu (or the Change Server button) of nwadmin. |
On each of the master NIS hosts, change directory to /usr/etc/yp and use the ypmake(1) command:
jupiter# cd /usr/etc/yp jupiter# /usr/etc/yp/ypmake |
To verify that each client can recognize the NetWorker server, you can enter this command on each client after waiting a suitable period for NIS databases to propagate:
jupiter# ypmatch nsrhost hosts 137.69.1.3 mars nsrhost |
The hostname listed in the output should be the name of the NetWorker server.
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.
Log on to the client as root:
jupiter# |
Edit the file /etc/hosts, adding nsrhost as an alias next to the NetWorker server name:
137.69.1.3 mars nsrhost |
In this example, the client named jupiter will be backed up by the NetWorker server named mars.
![]() | 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. |
If NIS and/or DNS are in use on the network, verify that nsrhost is correctly aliased:
jupiter% /usr/etc/ping -c1 nsrhost PING mars.engr.xyz.com (192.48.155.20): 56 data bytes ... |
In the command, the -c is followed by a numeral 1. The first line of output should contain the name of the NetWorker server. If the output doesn't contain the name of the NetWorker server, modify the client's /usr/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.
Follow the procedure in this section to install Networker client software. Because licenses for NetWorker clients are not installed on the clients, no enabling of the client software is required.
On the client, become root and enter the inst(1M) command:
% /bin/su - Password: # inst |
Specify the location of the NetWorker software distribution and get a list of the subsystems, for example:
Inst> from /CDROM/dist Inst> list |
For additional information on inst, see the Software Installation Administrator's Guide.
Make subsystem selections in Inst. Use Table 2-3 to guide you in selecting subsystems. Subsystems not listed in Table 2-3 should not be installed on clients. For example, to install the required software, the references pages, the release notes, and the InSight versions of the NetWorker manuals on an IRIX 5.2 client, enter these commands:
Inst> keep * Inst> install networker4.*.client_5 Inst> install networker4.man.relnotes Inst> install networker4.books.* |
For additional information on these subsystems, see the IRIX NetWorker Release Notes.
Table 2-3. Subsystems for NetWorker Clients
Perform the installation and exit inst:
Inst> go Inst> quit |
Check to see if the hostname alias nsrhost has been set to your NetWorker server:
jupiter% /usr/etc/ping -c1 nsrhost PING mars.engr.xyz.com (192.48.155.20): 56 data bytes ... |
In the command, the -c is followed by a numeral 1. The first line of output should contain the name of the NetWorker server.
If the output doesn't contain the name of the NetWorker server, NetWorker commands such as the nwadmin won't automatically connect you to your server; you'll have to use the “Change Server” command on the File pulldown menu to specify your server.
To set the hostname alias nsrhost to your NetWorker server, follow the directions in the section “Configuring Clients to Recognize the Server” in this chapter.
If you need to remove the NetWorker software and data files on a server for any reason, follow these steps:
Shut down the NetWorker server using the nsr_shutdown(1M) command:
mars# /usr/etc/nsr_shutdown |
Use the versions(1M) command to remove any or all of the NetWorker software. For example, to remove all of the software, enter this command:
mars# versions remove networker4 |
Remove the data files by entering these commands:
mars# cd /nsr mars# rm -rf . mars# cd / mars# rm -f /nsr |
You can remove NetWorker software on a client with the versions or inst commands.