Install & Configure Legato NetWorker On TruCluster Server

Install & Configure Legato NetWorker on Tru64-ClusterServer
[UNIX] HowTo: Install & Configure NetWorker cluster server v6.x on TruCluster v5.x
COMPONENT : Legato NetWorker
OPERATING SYSTEM OR PRODUCT NAME : Compaq Tru64 UNIX
VERSION :
NetWorker v6.x
Tru64 UNIX v5.x
TruCluster v5.x
1. Hardware Configuration
-------------------------
This is an example to show you how. It is being used for illustration

throughout this article.
Ethernet
--------|---------------------------------------|--------
| |
--------- ---------
| | Memory Channel | |
| |-------------------------------| |
| | Shared Bus | |
| |-------------------------------| |
|Tru64 UNIX Shared Bus |Tru64 UNIX
| v5.0a | | v5.0a |
| |-----|------------------|------| |
| | | | | |
--------- | | ---------
| |
'stan' | | 'kyle'
| StorageWorks |
----- -----
| | | |
|===[disk-/nsr] |===[TZ885–jukebox]
| | | |
----- -----
System Configuration:
- A cluster consists of 2 systems named stan and kyle. Cluster alias

name is called clua0.
Both systems are running Tru64 UNIX v5.0a, TruCLuster software v5.0a.
- A tz855 jukebox connected to the share bus of the cluster.
- A disk (/dev/disk/dsk9c) in a HSZ StorageWorks is used for the
NetWorker server home directory (/nsr).
TZ885 and the shared disk information:
# hwmgr -view devices

HWID: Device Name Mfg Model Location
70: /dev/disk/dsk9c DEC HSZ70 bus-3-targ-3-lun-2
71: /dev/changer/mc0 TZ Media Changer bus-2-targ-5-lun-1
72: /dev/ntape/tape0 DEC TZ885 (C) DEC bus-2-targ-5-lun-0
The NetWorker software, in conjunction with the TZ885 and the

shared disk, form the NetWorker virtual server. The cluster alias
is the NetWorker virtual server name.
2. Creating a filesystem for the NetWorker server home directory

----------------------------------------------------------------
Example:
stan# cd /
stan# mkdir /clua0
stan# mkfdmn /dev/disk/dsk9c nsr_domain
stan# mkfset nsr_domain nsr
stan# mount nsr_domain#nsr /clua0
Then add an entry to the /etc/fstab file, e.g.

nsr_domain#nsr /clua0 advfs rw 0 4
Please note that, you must use the cluster alias name for the
mount point of this filesystem. Also, if you have a fully-qualified
cluster alias name, only use the short name (without the domain name).
3. Installing NetWorker software

--------------------------------
A) Login as root onto one node of the cluster, mount the NetWorker
software media.
B) Issue '/usr/sbin/setld -l /<cdrom-mount-point>;/TRU64' to install

the software if using the Legato media.
Issue '/usr/sbin/setld -l /<cdrom-mount-point>;/NetWorker/kit' if
using the Compaq Associated Product Library media.
Make sure your answers/inputs to the installation are:
Enter the location for this Client's NetWorker home directory

(it must sit on a local disk!) [ /var/nsr ]: /nsr
/nsr/res/servers file does not exist..

Do you wish to create the file? (y/n):n
By now, you should have 2 'nsrexecd' up and running on each node

in the cluster.
Please note that you only need to install NetWorker software on one
node in the cluster. NetWorker software is installed to the
/usr/opt/networker directory of the /usr Cluster FileSystem (CFS).
Sample installation script is in Appendix A.
4. Configuring the NetWorker server environment

-----------------------------------------------
Run the following script one at a time on every node in the cluster:
# /usr/opt/networker/bin/networker.cluster
Please note that this script could take 2-5 minutes to run to
completion, depending on the processor type and system resources.
Sample output of this script is in Appendix B.
5. Creating CAA profile, and registering the NetWorker resource

---------------------------------------------------------------
Create a TruCluster CAA (Cluster Application Availability) profile
for each backup device (tape drives and media changers) on the
cluster shared bus to be used by the NetWorker cluster server.
In this example, 2 profiles are created, one for the tape drive
(/dev/ntape/tape0_d1), and one for the changer (/dev/changer/mc0).
# cd /var/cluster/caa/profile
# more mczero.cap
NAME=mczero
TYPE=changer
DEVICE_NAME=/dev/changer/mc0
# more tapezero.cap
NAME=tapezero
TYPE=tape
DEVICE_NAME=/dev/ntape/tape0_d1
Edit the networker.cap profile (in /var/cluster/caa/profile/), and add

the profiles that you just created to the REQUIRED_RESOURCES entry.
E.g.
REQUIRED_RESOURCES=mczero tapezero
Then register all the profiles you have created, as well as the
networker.cap profile using the caa_register command. E.g. on one
node in the cluster, run:
# /usr/sbin/caa_register mczero
# /usr/sbin/caa_register tapezero
# /usr/sbin/caa_register networker
Note:
If you make any change to one of your resource ".cap" file
after that resource has been registered, that resource must be
un-registered and re-registered for the change to take effect.
6. Startup the NetWorker server

-------------------------------
Run the following command on any node in the cluster:

# /usr/sbin/caa_start -c <node-name>; networker
The '-c <node-name>;' is optional.
Example:
stan# caa_start -c stan networker

Attempting to start `networker` on member `stan`
Start of `networker` on member `stan` succeeded.
stan# caa_stat networker

NAME=networker
TYPE=application
TARGET=ONLINE
STATE=ONLINE on stan
stan# ps -e |grep nsr | grep -v grep

558692 ?? S 0:00.14 /usr/opt/networker/bin/nsrexecd
558712 ?? S 0:01.30 /usr/opt/networker/bin/nsrd -k clua0
558751 ?? I< 0:00.10 /usr/opt/networker/bin/nsrmmd -n 1
558760 ?? IN 0:00.34 /usr/opt/networker/bin/nsrmmdbd
558761 ?? I 0:00.12 /usr/opt/networker/bin/nsrindexd
kyle# ps -e |grep nsr | grep -v grep

1204850 ?? I 0:00.07 /usr/opt/networker/bin/nsrexecd
7. Creating the NetWorker "servers" file

----------------------------------------
Define the list of trusted NetWorker servers.
A) On the node which is running the NetWorker cluster server,

shut it down by using:
# caa_stop networker
B) On each node in the cluster, edit or create the /nsr/res/servers file

and add the set of NetWorker servers, one per line, that you want
grant access to this client.
Make sure that the first entry in this file is the cluster alias
(NetWorker server name).
C) On each node, re-start NetWorker client daemons by:

# /sbin/init.d/NSRstartstop stop
# /sbin/init.d/NSRstartstop start
D) On one node, start NetWorker server by issuing:

# caa_start -c <node-name>; networker
On the node which is running the NetWorker server, edit or create

the /nsr/res/servers file, using the same procedure as described
in step (B). Then re-start NetWorker server by issuing:
# caa_start -c <node-name>; networker
8. Defining NetWorker group for autorestart

-------------------------------------------
On the node that is running the NetWorker server, startup the

nwadmin window. E.g. /usr/opt/networker/bin/nwadmin -s <cluster-alias>;.
Create group(s), or modify the existing group 'Default', and set

the following attributes:
- Select 'Enabled' for the "Autorestart" field
- 'Manual restart' option is unchecked in the "Options" field
Both Autorestart and Options fields are hidden attributes, and

you need to click View pull-down menu and select Detail in the
Groups window.
Note, only save sets that are part of a savegroup with the Autorestart
attribute enabled and have Manual restart option disabled, will be
restarted after a virtual client or a NetWorker server failover.
9. Configuring the NetWorker server resource

--------------------------------------------
/usr/opt/networker/bin/nwadmin ->; Server ->; Setup.

In the Server window, add 'root@<cluster-node>;' to the "Administrator"
field for each physical cluster node in the cluster.
10. Configuring client resource for the NetWorker virtual server

----------------------------------------------------------------
A client resource of the cluster alias is automatically created.

In this example, a client resource named 'clua0' is created.
/usr/opt/networker/bin/nwadmin ->; Clients ->; Setup.

In the Clients window, select the NetWorker virtual server
(cluster alias name):
- Add 'root@<cluster-node-name>;' of each physical node within the
cluster to the "Remote access" field.
- Make sure "Save set" field is set to 'All'.
Please note that, the client resource of the cluster alias takes the
identity of the cluster. It is being used to backup all the cluster
filesystems.
11. Configuring client resource for each cluster node

-----------------------------------------------------
You still need to setup a client resource for each physical cluster node
in the cluster. It is recommended that these client resources belong to
an inactive backup group, that is, a group which "Autostart" field is
set to 'Disabled'. In this case, each cluster node will not get backup.
A) Create an inactive group

/usr/opt/networker/bin/nwadmin ->; Customize ->; Groups ->; Create.
For example, name the group as 'Inactive', and make sure that the
"Autostart" field is set to 'Disabled'.
B) Create client resource for each cluster node

/usr/opt/networker/bin/nwadmin ->; Clients ->; Client Setup ->; Create.
Then select 'Inactive' for the "group" field.
In this example, two client resources will be created, one for

stan, and the other for kyle.
Failure to create client resource for each cluster node will result in
getting following error when you are backing up the cluster alias:
<cluster alias>;:/<filesystem>; save: RAP error: Unable to extract
resource info for client <cluster node name>;
12. Configuring jukebox

-----------------------
On the node that is running the NetWorker server, use 'jbconfig'

to configure jukebox resource for all the stackers or tape
libraries on the cluster shared bus.
'jbconfig' will ask you to input the pathname of the control port:
Pathname of the control port for the jukebox device? [scsidev@b.t.l]
Where b.t.l is the bus, target and LUN of the changer.
Make sure you input the device filename for the control port,
e.g. /dev/changer/mc0.
Sample output of creating a NetWorker jukbebox resource for

the TZ885 is in Appendix C.
13. Shutdown, startup, and relocate NetWorker

---------------------------------------------
A) Shutdown & startup NetWorker server

# caa_start -c <cluster-node-name>; networker
B) Relocate NetWorker server

# caa_relocate -c <cluster-node-name>; networker
C) Shutdown & startup NetWorker client

# /sbin/init.d/NSRstartstop stop
# /sbin/init.d/NSRstartstop start
14. Creating Composite Hostid

-----------------------------
In a NetWorker virtual server environment, a composite host ID is

used to tie to the NetWorker authorization codes.
Refer to the NetWorker technical article

"HowTo: Register NetWorker Licenses for NetWorker Cluster Server"
for more detail information on creating the composite hostid and
registering licensing to Legato.
15. NetWorker virtual server directory structure

------------------------------------------------
A) After installing NetWorker software

/nsr is a directory.
B) After running "networker.cluster"

/nsr ->; /cluster/members/{memb}/nsr
/cluster/members/{memb}/nsr ->; /var/cluster/members/{memb}/nsr
C) On each cluster member that is not running the NetWorker server

/cluster/members/{memb}/nsr ->; /var/cluster/members/{memb}/nsr
D) On the cluster member that is running the NetWorker server

/cluster/members/{memb}/nsr ->; /<cluster-alias-name>;/nsr
Appendix A - Installing NetWorker

=================================
stan# setld -l /cdrom/TRU64
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) Legato Networker Basic Client

2) Legato Networker Driver & Storage Node
3) Legato Networker Manpages
4) Legato Networker Server
--- MORE TO FOLLOW ---

Enter your choices or press RETURN to display the next screen.
Estimated free diskspace(MB) in root:109.2 usr:405.2 var:882.5
Choices (for example, 1 2 4-6):

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:
Legato Networker Basic Client

Legato Networker Driver & Storage Node
Legato Networker Manpages
Legato Networker Server
Is this correct? (y/n): y
Checking file system space required to install selected subsets:
File system space checked OK.
4 subsets will be installed.
Loading subset 1 of 4 ...
This subset may take some time to complete.

Copying from . (disk)
Working....Tue Oct 24 13:20:56 EDT 2000
Verifying

Verifying

Verifying
This subset will take some time to complete.

Verifying
4 of 4 subsets installed successfully.
Configuring "Legato Networker Basic Client" (LGTOCLNT600) on member1
Copyright (c) 1990-2000, Legato Systems, Inc.
************ File Configuration on NetWorker Client ***********
/nsr not found!
Enter the location for this Client's NetWorker home directory

(it must sit on a local disk!) [ /var/nsr ]: /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/NSRstartstop 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/NSRstartstop
Starting nsrexecd...
The nsr/res/servers file will need to be updated with

the list of servers that will back up this system as
as a client.
This is also needed if this machine is to be used
as an HSM client.
Do you wish to create the file? (y/n):n

*********************************************
Please create the /nsr/res/servers file

and manually edit it with the list of
remote backup servers
*********************************************
LGTOCLNT600 software installed successfully

The Legato NetWorker Client version 600 binaries have been installed in
/usr/opt/networker/bin. Please update the PATH environment
variable to include /usr/opt/networker/bin.
*******************************************************************************
Configuring "Legato Networker Driver & Storage Node" (LGTONODE600) on member1

LGTONODE600 software installed successfully
The Legato NetWorker Storage Node version 600 binaries have been installed
in /usr/opt/networker/bin. Please update the PATH environment
*******************************************************************************
Configuring "Legato Networker Manpages" (LGTOMAN600) on member1

LGTOMAN600 software installed successfully
The Manpages are installed in the following locations:
/usr/opt/networker/man/man3
Please update the MANPATH environment variable to include the path

/usr/opt/networker/man.
*******************************************************************************
Configuring "Legato Networker Server" (LGTOSERV600) on member1
************ File Configuration on NetWorker Server ***********
starting nsrd...
NetWorker icon has been successfully installed into CDE.
LGTOSERV600 software installed successfully
The Legato NetWorker Server version 600 binaries have

been installed in /usr/opt/networker/bin.
Please update the PATH environment variable to include
/usr/opt/networker/bin.
*******************************************************************************


mkdir: cannot create /usr/opt/networker/bin/C.
/usr/opt/networker/bin/C: File exists

Do you wish to continue? (y/n) [ y ]: Modifying /etc/rpc

/etc/rpc already modified for NetWorker
/cluster/members/{memb}/etc/syslog.conf already modified for NetWorker
The modified files were saved and
renamed as follows:

---- ----------------------

as a client.
as an HSM client.
Do you wish to create the file?

(y/n):*********************************************

*********************************************
*******************************************************************************


*******************************************************************************


*******************************************************************************
starting nsrd...

*******************************************************************************

mkdir: cannot create /usr/opt/networker/bin/C.
/usr/opt/networker/bin/C: File exists

Do you wish to continue? (y/n) [ y ]: Modifying /etc/rpc

/etc/rpc already modified for NetWorker
* * * Restarting syslog daemon * * *
The modified files were saved and renamed as follows:

---- ----------------------

as a client.
as an HSM client.
Do you wish to create the file?

(y/n):*********************************************

*********************************************
*******************************************************************************

*******************************************************************************


*******************************************************************************
starting nsrd...

*******************************************************************************
Appendix B - "networker.cluster" output

=======================================
stan# /usr/opt/networker/bin/networker.cluster
TruCluster is a high availability product for Tru64 Unix.

It defines failover applications which may move from one node to
another, depending on the availability and health of the machine
it is running upon.
The Networker Client and Networker Server have the default cluster
identity.
Do you wish to continue? [Yes]?

Shutting down NetWorker services...
Restarting syslog daemon...
/cluster/members/{memb}/etc/syslog.conf already modified for NetWorker
Restarting syslog daemon...
NetWorker has been successfully cluster configured.
Appendix C - "jbconfig" output

==============================
stan# /usr/opt/networker/bin/jbconfig
1) Install a SmartMedia Jukebox.
2) Install an Autodetected SCSI Jukebox.
3) Install an Autodetected NDMP SCSI Jukebox.
4) Install an SJI Jukebox.
5) Install an STL Silo.
What kind of Jukebox are you installing? [1] 2

These are the SCSI Jukeboxes currently attached to your system:
1) scsidev@2.5.1: Quantum DLT/Digital DLT
Which one do you want to install? 1
Installing an 'Quantum DLT/Digital DLT' jukebox.
Name you would like to assign to the jukebox device? tz885
A brief description of the jukebox device? [scsidev@2.5.1: Quantum DLT/Digital
DLT]
Pathname of the control port for the jukebox device? [scsidev@2.5.1] /dev/changer/mc0
Do you want automated device cleaning support enabled? (yes/no) no
Enter hostname that owns media drive 1: ? [clua0]
An example of a valid device name for this OS is '/dev/nrmt0h

for Tru64 Unix V4.x or /dev/ntape/tape0_d1 for V5.x'
Enter pathname of media drive 1: ? /dev/ntape/tape0_d1
using '/dev/ntape/tape0_d1' as device name
Should the drive be configured as a NDMP device? (yes/no) no
Jukebox has been added successfully

Would you like to configure another jukebox? (yes/no) no

Install & Configure Legato NetWorker On TruCluster Server

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Install & Configure Legato NetWorker On TruCluster Server

Enviado por

Direitos autorais:

Formatos disponíveis

Install & Configure Legato NetWorker on Tru64-ClusterServer

OPERATING SYSTEM OR PRODUCT NAME : Compaq Tru64 UNIX

This is an example to show you how. It is being used for illustration

- A cluster consists of 2 systems named stan and kyle. Cluster alias

TZ885 and the shared disk information:

# hwmgr -view devices

The NetWorker software, in conjunction with the TZ885 and the

2. Creating a filesystem for the NetWorker server home directory

Then add an entry to the /etc/fstab file, e.g.

3. Installing NetWorker software

B) Issue '/usr/sbin/setld -l /<cdrom-mount-point>;/TRU64' to install

Make sure your answers/inputs to the installation are:

Enter the location for this Client's NetWorker home directory

/nsr/res/servers file does not exist..

By now, you should have 2 'nsrexecd' up and running on each node

Sample installation script is in Appendix A.

4. Configuring the NetWorker server environment

Sample output of this script is in Appendix B.

5. Creating CAA profile, and registering the NetWorker resource

Edit the networker.cap profile (in /var/cluster/caa/profile/), and add

6. Startup the NetWorker server

Run the following command on any node in the cluster:

The '-c <node-name>;' is optional.

stan# caa_start -c stan networker

stan# caa_stat networker

stan# ps -e |grep nsr | grep -v grep

kyle# ps -e |grep nsr | grep -v grep

7. Creating the NetWorker "servers" file

Define the list of trusted NetWorker servers.

A) On the node which is running the NetWorker cluster server,

B) On each node in the cluster, edit or create the /nsr/res/servers file

C) On each node, re-start NetWorker client daemons by:

D) On one node, start NetWorker server by issuing:

On the node which is running the NetWorker server, edit or create

8. Defining NetWorker group for autorestart

On the node that is running the NetWorker server, startup the

Create group(s), or modify the existing group 'Default', and set

Both Autorestart and Options fields are hidden attributes, and

9. Configuring the NetWorker server resource

/usr/opt/networker/bin/nwadmin ->; Server ->; Setup.

10. Configuring client resource for the NetWorker virtual server

A client resource of the cluster alias is automatically created.

/usr/opt/networker/bin/nwadmin ->; Clients ->; Setup.

11. Configuring client resource for each cluster node

A) Create an inactive group

B) Create client resource for each cluster node

In this example, two client resources will be created, one for

12. Configuring jukebox

On the node that is running the NetWorker server, use 'jbconfig'

Sample output of creating a NetWorker jukbebox resource for

13. Shutdown, startup, and relocate NetWorker

A) Shutdown & startup NetWorker server

B) Relocate NetWorker server

C) Shutdown & startup NetWorker client

14. Creating Composite Hostid

In a NetWorker virtual server environment, a composite host ID is

Refer to the NetWorker technical article

15. NetWorker virtual server directory structure

A) After installing NetWorker software

B) After running "networker.cluster"

C) On each cluster member that is not running the NetWorker server

D) On the cluster member that is running the NetWorker server

Appendix A - Installing NetWorker

** File Configuration on NetWorker Client *

** File Configuration on NetWorker Server *

** File Configuration on NetWorker Client *