primecluster wizard for networker 4 - fujitsu … wizard for networker. networker becomes possible...

J2S1-7460-01-Z2

PRIMECLUSTER Wizard for NetWorker 4.1

Introduction

Purpose of this manual This manual explains procedure of installation through operation for PRIMECLUSTER Wizard for NetWorker.

Audience of this manual Audience for this manual are system engineer and system administrator who construct or do maintenance for PRIMECLUSTER system. They are required to have knowledge for PRIMECLUSTER and NetWorker.

About this manual This manual is consisted of 5 chapters and appendix A. Each chapter contains the following. · Chapter 1 Overview of Function · Chapter 2 Setup and Installation · Chapter 3 Operation · Chapter 4 Commands · Chapter 5 List of Messages · Appendix A Creating NetWorker Cluster Application (CUI)

Figures on this manual The following figures indicate:

Items that can be referred.

Items explained by using example.

Trademark

Solaris, NFS, and Sun Microsystems are the trademark or registered trademark for Sun Microsystems, Inc. in the US and other countries. The logo mark and Solaris are the registered trademark for Sun Microsystems, Inc. in the US. Legato is the trademark for Legato Systems, Inc.

NetWorker is the registered trademark for Legato Systems, Inc. Company names and product names are product name, trademark, or registered trademark for each company.

Notes

This manual is not allowed to be copied without acknowledgement. This manual may be altered without notification.

All Rights Reserved, Copyright(C) Fujitsu Limited 2003

i

Chapter 1 Overview of Function

1.1 Function

Shared resources which PRIMECLUSTER manages can be backed up consistently with clustering environment on PRIMECLUSTER Wizard for NetWorker.

Cluster system host computer which is constructed on PRIMECLUSTER can be operated with standby operation form.

The form to cooperate NetWorker client with clustering system is called client-cluster form. The form NetWorker Storage Node cooperate with cluster system is called storage cluster form, and the form NetWorker server cooperate with cluster system is called server cluster form.

Data can be backed up consistently in client cluster form. Data can be backed up in cluster without sending data to NetWorker server in storage cluster form.

In server-cluster form, standby operation of NetWorker improves availability of backup operation system.

1.1.1 Standby Operation and High Availability of NetWorker (client-cluster form)

Client cluster form enables backup user resource which is constructed on PRIMECLUSTER consistently in clustering environment.

Using logical host name (virtual NetWorker client and server) enables backup after failover occurs without changing NetWorker definition.

1

[1] Virtual Client Backup

Data on the shared disk which PRIMECLUSTER manages can be backed up by a virtual server name (logical host name).

The logical host name is a virtual name related to virtual IP address defined by takeover IP address of PRIMECLUSTER. Moreover, it is a name managed to support virtual NetWorker client, server, and storage node PRIMECLUSTER Wizard for NetWorker.

NetWorker becomes possible by using the logical host name the treatment of a single similar system of the cluster system. Therefore, it is possible to back up data on a shared disk from the standby node (new operation node) without the definition change of NetWorker even if failover is generated, and the backup data can be recovered from each node.

The logical host name can be specified each user application of the cluster. Therefore, data on a shared each disk can be backed up and recovered by logical host name treating each application as a single system even if in N:1 operation standby form or mutual standby form.

[2] Local Backup of hosts consisting cluster

Data on a local disk of each host which composes the cluster can be backed up by using a physical host name of the host which composes the cluster.

A local disk of the standby host can be backed up because the NetWorker client is operated on all hosts which compose the cluster. Moreover, the backup operation can be continued without the definition change of NetWorker even if failover is occured.

[3] Standby operation making about NetWorker client

The standby operation of the NetWorker client is achieved by starting a necessary NetWorker client in operation/standby system when the cluster does failover in cooperation with PRIMECLUSTER.

Moreover, because NetWorker daemon-specific monitor only for the NetWorker client can use recovery/failover function of PRIMECLUSTER by notifying PRIMECLUSTER when abnormality occurs while observing the process of the NetWorker client, the availability of the backup operation system which uses NetWorker is improved.

2

1.1.2 Standby Operation and High Availability of NetWorker (storage node cluster form)

Sharing tape library by clustering NetWorker Storage Node and SAN Storage Node and NetWorker daemon-specific monitor improves availability of backup system on which NetWorker is used.

Clustering Storage Node and SAN Storage Node improve backup availability on LAN-free with SAN environment.

To make NetWorker Storage Node a standby operation can take over functions that are provided by NetWorker Storage Node using by failover of PRIMECLUSTER without changing of NetWorker configurations.

Data can be backed up on logical host likewise client cluster form. Client daemon can also be monitored. Also, monitoring NetWorker daemon improves availability and reliability of data backup system.

Tape device can be shared between nodes that consist cluster system. NetWorker Dynamic Device Sharing Module is needed to share one tape device between nodes.

NetWorker Storage Node is a NetWorker Client. Therefore NetWorker Storage Node includes function of client cluster.

1.1.3 Standby Operation and High Availability of NetWorker (server cluster form)

Clustering NetWorker and monitoring system by NetWorker daemon-specific monitor improves availability of backup operation system on which NetWorker is used.

3

Clustering NetWorker server, sharing tape device and NetWorker management database (stores information such as when and what data is backed up and NetWorker setting) improves backup availability. Even failure occurs during backup and failover occurs in cluster system, backup can be continued on standby node.

Also, data can be backed up on logical host likewise client cluster form.

NetWorker Server is a NetWorker Client and a NetWorker Storage Node. Therefore NetWorker Server includes function of client cluster and storage node cluster.

1.1.3.1 Taking over Backup Service

NetWorker-specific RMS configuration script and detector which monitors NetWorker server daemon cooperate with PRIMECLUSTER and it enables to takeover backup service.

If backup on ONLINE host can not be continued, backup operation is auto-switched from ONLINE host to STANDBY host. Then, NetWorker server is automatically started on STANDBY host (new ONLINE host) and resumes backup service.

New ONLINE host enables backup operation without changing NetWorker definition. Also, data which is backed up on previous ONLINE host can be recovered on new ONLINE host.

1.1.3.2 Auto Detection and Recovery of NetWorker Failure

RMS configuration script and NetWorker server daemon detector automatically detects and recover failure on NetWorker and this minimizes time to stop backup service.

4

[1] RMS Configuration Script

RMS configuration script is booted by RMS (Reliant Monitor Software) which is provided by PRIMECLUSTER Wizard for NetWorker and boot and stop NetWorker daemon. If failure occurs during operating NetWorker, RMS script is rebooted by AutoRecover function and performs recovery for failure on NetWorker.

RMS configuration script checks NetWorker index when server daemon is booted. Then, if failure occurs on index, failure is automatically recovered.

[2] NetWorker Daemon Monitor Detector

Process for NetWorker server and client daemon is monitored by PRIMECLUSTER NetWorker daemon detector (detector). If detector detects failure on NetWorker server and client daemon, it notifies failure to RMS. Then, RMS reboot server daemon or changes host state from ONLINE to FAULT. Detector continues to monitor server daemon after notifying error to RMS. If server daemon is rebooted by RMS configuration script, detector resume monitoring server daemon.

Detail for each failure and recovery procedure is described below.

[2-1] Recovery for Failure on NetWorker Daemon

Detector notifies RMS abnormality when NetWorker is always observed, and abnormality is detected. If AutoRecover attribute is enabled, RMS boots NetWorker boot script after failure is notified to RMS.

For how to enable or disable AutoRecover attribute, refer to "PRIMECLUSTER Installation guide".

[2-2] Index Failure on NetWorker

RMS configuration script checks index by using NetWorker commands. If RMS determines that index is required to be recovered, RMS recovers index on object client by using NetWorker's commands. RMS configuration script determines that index must be recovered if NetWorker command notifies failure on index.

Failure occurs on NetWorker server process during backup or failover occurs due to shutdown on operation host during backup may cause failure on index.

Recovery on index is optional. For how to setup recover mode, refer to " 4.1 clntwparam - Setting Operating Environment ".

For the procedure of recover index manually, refer to "3.5.3 Treatments for Frequent Trouble".

1.1.4 Temporary Stop of Monitoring NetWorker Daemon

The monitoring of NetWorker can be stopped by using command (hvnwdisable) of PRIMECLUSTRE WIzard for NetWorker. For the detail of commands, refer to "4.3 hvnwdisable - Temporary Stop of Monitoring".

Shutting down NetWorker without stopping other user applications to stop the monitoring of NetWorker becomes possible. The cluster operation is not considered in this and NetWorker can be maintained. In this case, the state of the user application of NetWorker is always ONLINE.

When NetWorker is observed again, command (hvnwenable) of PRIMECLUSTER Wizard for NetWorker is used. For detail of command, refer to "4.4 hvnwenable - Resuming Monitoring".

1.1.5 STANDBY Operation

If server is not operated on hosts which consist of cluster, the status of the host is standby status and operates client on NetWorker with server cluster form.

Client daemon is monitored on STANDBY operation host. If NetWorker daemon is ended abnormally on STANDBY operation host, the status of NetWorker application resource is FAULT. If status of host is normal on host which status is FAULT, clear FAULT status to resume STANDBY operation.

Also, if server daemon is booted by mistake on STANDBY operation host, monitoring detector determines that status of host is in failure; it is notified to RMS and the status becomes FAULT on that host.

5

1.2 Operating Environment

1.2.1 System Configuration

1.2.1.1 Client Cluster Form

1.2.1.2 Storage Node Cluster Form

6

1.2.1.3 Server Cluster Form

1.2.2 Available Operation Form on PRIMECLUSTER

Operation form and name of product Standby Class

Operation standby Mutual standby System configuration

1 : 1 N : 1 Cascade 1:1

NetWorker Client runs runs not

(Note 1) runs

runs not

(Note 1)

NetWorker Storage Node

NetWorker SAN Storage Node runs

runs not

(Note 1) Runs

runs not

(Note 1)

NetWorker Server runs runs not

(Note 1) Runs

runs not

(Note 1)

(Note 1) NetWorker user applications can not be operated simultaneously. However, standby operation between NetWorker user application and other application can be run.

7

Chapter 2 Setting and Installation

2.1 Environment Setup

2.1.1 Environment Setup for Client Cluster Form

2.1.1.1 Procedure for Environment Setup

Follow the procedure below to setup environment for client cluster form. · Setup environment for PRIMECLUSTER · Install NetWorker · Setup environment for PRIMECLUSTER Wizard for NetWorker · Setup NetWorker The detail of each item is explained below.

2.1.1.2 Setup Environment for PRIMECLUSTER

Follow the procedure below to setup environment for PRIMECLUSTER.

[1] Installing PRIMECLUSTER through initial setting of PRIMECLUSTER system configuration

After installing PRIMECLUSTER, boot cluster operation management view, register PRIMECLUSTER system license, and setup hardware and CF (CLUSTER FOUNDATION) on PRIMECLUSTER system.

For how to install PRIMECLUSTER or setting, refer to "PRIMECLUSTER Installation Guide".

Pay attention to the following to setup PRIMECLUSTER environment. · Setting Shared Disk Device

Shared disk which is shared between cluster hosts must be defined to construct NetWorker cluster environment. For how to set up shared disk, refer to "PRIMECLUSTER Installation guide".

· Setting Network To setup cluster environment on NetWorker, use takeover IP address as takeover network. Therefore, IP address application must be created on wizard. For how to setup network, refer to "PRIMECLUSTER Installation guide". To create IP address application, refer to "PRIMECLUSTER Installation guide".

· /etc/vfstab file Define disk mount information which is shared by cluster application.

· /etc/hosts file Define logical hostname which corresponds to takeover IP address.

· /usr/opt/reliant/etc/hvipalias file Define cluster interface which is used by takeover IP address. For detail of setting, refer to "PRIMECLUSTER Installation guide".

· Creating Resource Created on the following resource; After the resource of PRIMECLUSTER Wizard for NetWorker is created, the user application is create. - IP address resource (Ipaddress) IP address resource is required to setup takeover IP address for cluster operation. Hostname which is specified with this resorce is used as virtual hostname. - Mount point resource (Fsystem) Mount point resource specifies mount point of shared disk which is shared among clusters. For how to create application, refer to "PRIMECLUSTER Installation guide".

2.1.1.3 Installing NetWorker

You are going to install NetWorker.

To install NetWorker, pay attention to the following. For the procedure of installing NetWorker, refer to NetWorker manual. · Installation Host

Install LGTOclnt (NetWorker client) package to all the client hosts on which data is backed up. · Installation Disk

Install NetWorker to local disk on each host and create NetWorker management file (client, licensing and

9

server information) on local disk on each host. For the detail of how to install NetWorker, refer to NetWorker Installation Guide.

2.1.1.4 Environment Setting for PRIMECLUSTER Wizard for NetWorker

Follow the procedure below to setup environment for PRIMECLUSTER Wizard for NetWorker. · Install PRIMECLUSTER Wizard for NetWorker · Define logical host name · Creating usr application of NetWorker Client Detail for each item is described below.

[1] Instaling PRIMECLUSTER Wizard for NetWorker

Install FJSVclntw package.

FJSVclntw package must be installed on each host.

For how to install FJSVclntw package, refer to "Installation Guide" of PRIMECLUSTER Wizard for NetWorker.

[2] Defining Logical Host Name

To define logical hostname (virtual client name), edit the following logical hostname management file which PRIMECLUSTER Wizard for NetWorker provides by using vi editor.

/etc/opt/FJSVclntw/etc/clnwc.env

Also, edit /etc/hosts file by using vi editor and add logical hostname which is related to takeover IP address.

Define logical hostname on all the host on which PRIMECLUSTER Wizard for NetWorker is installed.

[2-1] Logical Host Name Management File

Logical host name file is used to define logical host name (virtual client name).

[description style]

ApplicationName, LogicalNodeName, ClusterMntFileName, RawDeviceListFileName

ApplicationName, LogicalNodeName, ClusterMntFileName, RawDeviceListFileName

.

.

.

[Description]

Enter ','between each file name and enter all the file name within one line..ApplicationName,LogicalNodeName,ClusterMntFileName,RawDeviceListFileName

RawDeviceListFileName can be abbreviated.

Define logical hostname for each cluster service. If there are more than one logical hostnames, enter them by multiple lines for each cluster service.

Characters between "#" to enter and space are ignored.

[Parameter]

ApplicationName:

Enter the name of NetWorker client application.

This can not be omitted.

LogicalNodeName:

Specify logical hostname (hostname) which is related to takeover IP address which is created on IP application (defined on /etc/hosts file).

This is not allowed to be omitted.

Specify logical hostname which is defined as client name with NetWorker client definition to backup shared disk.

ClusterMntFileName:

Specify path name for cluster mount information file.

10

This is not allowed to be omitted.

For how to create cluster mount information file, refer to "Cluster Mount Information File".

RawDeviceListFileName:

Specify pathname for raw device path list file.

Write to this file for backup shared disk as raw device.

If shared disk is backed up as file system, pathname is not required to be written.

For detail of raw device path list file, "raw Device Path List File".

[Example]

# Logical Node Name Management File

# All Right Reserved, Copyright Fujitsu 2003

#

# ApplicationName, LogicalNodeName, ClusterMntFileName, RawDeviceListFileName

apl1, virtual_host1, /etc/opt/FJSVclntw/etc/vfstab_apl1

apl2, virtual_host2, /home/vfstab_apl2, /etc/opt/FJSVclntw/etc/rawdevicelist1

[2-2] Cluster Mount Information File

Cluster mount information file is used to define file system on shared disk which is backed up on logical host.

Format of this file must be followed to /etc/vfstab file on Solaris.

For /etc/vfstab file, refer to "Solaris System Administration Guide" or online manual of vfstab(4).

Create cluster mount information file by the following procedure. 1. Copy template file of cluster mount information file (/etc/opt/FJSVclntw/etc/vfstab.draft file) on cp (1). # cp /etc/opt/FJSVclntw/etc/vfstab.draft /home/vfstab_apl1

If there is no file system on shared disk on which data is backed up, procedure for creating a file is complete.

If file system is on shared disk on which data is backed up, execute procedure 2. 1. Edit a file by using vi(1).

#vi /home/vfstab_apl1 [example]

# Cluster mount information file

# All Rights Reserved, Copyright Fujitsu 2003

#

# device device mount FS fsck mount moun

# to mount to fsck point type pass at boot options

# /dev/dsk/c0t0d0s5 /dev/rdsk/c0t0d0s5 /vol1 ufs - yes -

/dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 /mnt_point ufs 2 no quota

[2-3] raw Device Path List File

raw device path list file is used to define raw device to be backed up.

This file is required for backup shared disk as raw device.

This file must be created on each logical host.

To edit this file , copy template of raw device path list

File (/etc/opt/FJSVclntw/etc/raw_list) on cp (1) and use vi (1).

[format]

raw device path

raw device path

.

11

.

.

[explanation]

Write down raw device path in one line.

If there are more than one raw device path, write them in multiple lines.

Characters in between "#" to enter and spaces are ignored.

[parameter]

raw device path:

Specify path name of raw device on which data is backed up if shared disk is backed up as raw device.

[example]

# Raw Device Path List File

# All Right Reserved, Copyright Fujitsu 2003/01/23

# RawDevicePath

# /dev/rdsk/c1t0d0s5

/dev/rdsk/c2t1d0s0

/dev/rdsk/c2t1d0s1

[3] Creating user application of NetWorker Client

Refer to "2.1.4 Creating NetWorker Cluster Application" for creating the user application of the NetWorker client by GUI.

Refer to "Chapter 6 Appendix A" for creating the user application of the NetWorker client by CUI.

Both the GUI and the CUI methods of setting the NetWorker server application have been described as an example. However, the method of setting on the wizard is the same.

NetWorker application must be set upper than applications that will be backed up.

2.1.1.5 Setting NetWorker

The procedure of setting NetWorker is explained below.

Pay attention to the following to setup NetWorker. For the procedure of NetWorker, refer to NetWorker manual. · Setting Client To backup shared disk resource, specify logical hostname which is defined as client name on logical hostname management file with NetWorker client definition. To backup local disk resource on each host, specify physical hostname as client name on NetWorker client definition.

"Remote access" must be defined to setup logical host.

Follow the procedure below to change each logical host in cluster to virtual NetWorker client.

Using nwadmin GUI, select [client] -> [setup client].

Confirmed whether the logical host name has be set in the [name] field. The [create] is clicked, and the logical host name is input to [name] field if not set.

Specify name of administrator (user@hostname) of physical host consisting of cluster on [remote access] field. 1. Example: "root@Fj_host1" "root@Fj_host2"

2. 3. The setting will be needed each physical hosts that consist cluster system which will be backed up.

12

2.1.2 Environment Setting for Storage Node Cluster Form

2.1.2.1 Procedure of Environment Setting

How to setup environment for Storage Node cluster form is the same way as to setup environment for NetWorker client cluster form. Follow the procedure below to setup. · Setting environment for PRIMECLUSTER · Installing NetWorker · Setting environment for PRIMECLUSTER Wizard for NetWorker · Setting NetWorker (Setting Storage Node and SAN Storage Node) Detail for each item is described below.

The following must be setup with Storage Node; · The following packages must be installed when installing NetWorker module.

LGTOclnt : NetWorker Client LGTOdrvr : Tape library control driver LGTOnode : NetWorker Storage Node

· Shared tape library must be defined.

2.1.2.2 Environment Setting for PRIMECLUSTER

Setup environment for PRIMECLUSTER by the procedure below.

[1] Installing PRIMECLUSTER to setting initial configuration of PRIMECLUSTER System

Installation must be performed on client cluster form. · Setting shared disk device

Refer to "2.1.1.2 Setup Environment for PRIMECLUSTER". · Setting network

Refer to "2.1.1.2 Setup Environment for PRIMECLUSTER" to setup takeover IP address. To run storage node, use takeover IP address.

· Creating Resource Refer to "2.1.1.2 Setup Environment for PRIMECLUSTER" to create IP address resource and shared disk resource. After the resource of PRIMECLUSTER Wizard for NetWorker is created, the user application is create.


How to install NetWorker is described below.

For how to install NetWorker, refer to NetWorker manual. · Hosts for Installation

Install the following package to the hosts which is NetWorker Storage Node and NetWorker SAN Storage Node. LGTOclnt : NetWorker Client LGTOdrvr : Library Control Driver LGTOnode : NetWorker Storage Node

Do not install LGTOserv (NetWorker server). Setup /nsr (a directory to hold NetWorker database) to local disk.


Setup environment for PRIMECLUSTER Wizard for NetWorker. · Installing PRIMECLUSTER Wizard for NetWorker · Defining Logical Host Name · Setting Shared Tape Library · Creating an user application of NetWorker Storage Node Detail for each item is explained below.

For procedure of installing PRIMECLUSTER Wizard for NetWorker and defining logical hostname, refer to "2.1.1.4 Environment Setting for PRIMECLUSTER Wizard for NetWorker".

13

[1] Setting Shared Tape Library

Shared tape library which is shared on Storage Node must be setup. Refer to "2.2 Notes for Constructing Tape Device Shared System" for setup.

[2] Creating user application of NetWorker Storage Node

Refer to "2.1.4 Creating NetWorker Cluster Application" for creating the user application of the NetWorker Storage Node by GUI.

Refer to "Chapter 6 Appendix A" for creating the user application of the NetWorker Storage Node by CUI.

Both the GUI and the CUI methods of setting the NetWorker server application have been described as an example. However, the method of setting on the wizard is the same.



Pay attention to the following to setup NetWorker. For the procedure of setting NetWorker Storage Node, refer to NetWorker manual. · Executing jbconfig command Follow the procedure of setting Storage Node/SAN Storage Node to setup and use jbconfig command. To define host name specified for Storage Node and SAN Storage Node, specify host name with takeover IP. · Setting Client

Refer to "Setting Client" of Client Cluster. · About License

The number of shared tape library must be prepared with the module of NetWorker Storage Node and SAN Storage Node Module. The number of NetWorker Cluster Connections license in cluster system must be prepared.

2.1.3 Environment Setting for Server Cluster Form

2.1.3.1 Procedure for Environment Setting

How to setup environment for PRIMECLUSTER Wizard for NetWorker is described below.

Follow the procedure below for environment setting.

[1] Procedure

Operation Host Standby Host

1 Installing PRIMECLUSTER Installing PRIMECLUSTER

2 Setting Initial Configuration of PRIMECLUSTRE System

3 Installing NetWorker Installing NetWorker

4 Stopping NetWorker Stopping NetWorker

5 Installing PRIMECLUSTER Wizard for NetWorker Installing PRIMECLUSTER Wizard for NetWorker

6 Setting PRIMECLUSTER Wizard for NetWorker Setting PRIMECLUSTER Wizard for NetWorker

7 Executing nwclntwadd

8 Setting NetWorker detector by PRIMECLUSTER Wizard for NetWorker

9 Setting Application

10 Setting NetWorker

14

11 Confirming Function

12 Exchanging Application

13 Confirming Function

14 Exchanging Application

15 Registering NetWorker License

· How to register license is different from normal registration to use NetWorker in cluster environment. Refer to

"2.1.3.7 Registering NetWorker License" for detail. · The procedure for setting is different from normal procedure if tape device is shared between operation host

and standby host. Refer to "2.2 Notes for Constructing Tape Device Shared System" for the detail of setting.

2.1.3.2 Environment Setting for PRIMECLUSTER

Setup environment for PRIMECLUSTER by following the procedure below.

[1] Installing PRIMECLUSTER to Setting Initial Configuration of PRIMECLUSTER System

Installation must be performed on client cluster. · Setting Shared Disk Device

Refer to "2.1.1.2 Setup Environment for PRIMECLUSTER". · Setting Network

Refer to "2.1.1.2 Setup Environment for PRIMECLUSTER" to setup takeover IP address. To run NetWorker server, use takeover IP address.

· Set Confirmation of Shared Disk Device Do a shared-disk device in the mount manually. And confirm whether setting to the shared-disk device is correctly done. Select the volume which becomes a shared disk on the screen of "Global Disk Services" when you use GDS (Global Disk Services) . And, select [Operation] of the menu, do [Volume start], and start the volume. Moreover, format with newfs etc. , and put the volume into the state which can be used as a filesystem. Refer to "PRIMECLUSTER Installation guide" for details of setting GDS.

· Creating Resource Refer to "2.1.1.2 Setup Environment for PRIMECLUSTER" to make IP address resource and shared disk resource. After the resource of PRIMECLUSTER Wizard for NetWorker is created, the user application is create.


[1] Installing NetWorker

How to install NetWorker is described below.

Pay attention to the following for installation. For the procedure of installing NetWorker, refer to NetWorker manual. · Installing Host

Install the following packages to the hosts which is part of NetWorker Server. Install other packages (such as online manual) if necessary. - LGTOclnt : NetWorker Client - LGTOdrvr : Tape Library Control Driver - LGTOnode : NetWorker Storage Node - LGTOserv : NetWorker Server

· Installing Disk Install NetWorker to under/usr (default) on local disk on each host. Install NetWorker management file (under/nsr : client, licensing and server information) on local disk on each host.

· NetWorker Access Control When installing NetWorker, do not follow the following instruction and do not specify accessible server. "Enter the first NetWorker server's name [no more]"

[2] Stopping NetWorker

After NetWorker is installed, the NetWorker daemon is stopped. The stop of the NetWorker daemon uses"/usr/sbin/nsr_shutdown" command. Refer to the manual of NetWorker for details of"/usr/sbin/nsr_shutdown" command.

15


Set environment for PRIMECLUSTER Wizard for NetWorker following the procedure below. · Installing PRIMECLUSTER Wizard for NetWorker · Setting PRIMECLUSTER Wizard for NetWorker · Executing nwclntwadd · Setting NetWorker detector by PRIMECLUSTER Wizard for NetWorker · Setting Application Detail of each item is explained below.

[1] Installing PRIMECLUSTER Wizard for NetWorker

Install FJSVclntw package.

FJSVclntw package must be installed on each host.

For how to install FJSVclntw package, refer to "Installation Guide" on PRIMECLUSTER Wizard for NetWorker.

[2] Setting PRIMECLUSTER Wizard for NetWorker

The following two items are set by using the clntwparam command which PRIMECLUSTER Wizard for NetWorker offers. It is necessary to set it respectively on each node.

Refer to "4.1 clntwparam - Setting Operating Environment" for details of the clntwparam command.

[2-1] Setting of management file local path name

The specific place of /usr which is specified on installation is set in Local_Path by the absolute path name.

(example)

/etc/opt/FJSVclntw/bin/clntwparam Local_Path /var/opt/nsr

[2-2] Setting of management file shared path name

The place where data base area (/nsr) is set when NetWorker operates in the server cluster form is arranged is set in Virtual_Path by the absolute path name.

(example)

/etc/opt/FJSVclntw/bin/clntwparam Virtual_Path /networker/nsr

[3] Executing nwclntwadd

The NetWorker data base (under the control of /nsr) made for a local disk is copied onto Virtual_Path of a shared disk (shared pass of the use when NetWorker operates on the cluster) by executing the nwclntwadd command.

When GDS(Global Disk Services) is used, it is necessary to put a shared disk device into the state that can be mounted. Moreover, it is necessary to put the volume which becomes a shared disk into the state of "active". Refer to "PRIMECLUSTER Installation guide" for the use of GDS.

Execute the nwclntwadd command from one node in the cluster node.

Refer to "4.5 nwclntwadd - Setting NetWorker shared Data-Base" for details of the nwclntwadd command.

[4] Setting NetWorker detector by PRIMECLUSTER Wizard for NetWorker

To setup operating environment for detector and RMS configuration script, use the clntwparam command PRIMECLUSTER Wizard for NetWorker provides. Refer to "4.1 clntwparam - Setting Operating Environment" for a set method and a set content.

Edit /etc/hosts file by using vi editor and add logical host name (hostname) which is related to takeover IP address.

Set operating environment for monitor and RMS configuration script on all the hosts on which PRIMECLUSTER Wizard for NetWorker is installed.

[4-1] Defining Logical Host Name

Hosts to be NetWorker server is also host of NetWorker client ; therefore, resources on shared disk which is shared on NetWorker servers are backed up for virtual client (virtual server).

To backup resource on shared disk which is shared on NetWorker server, logical hostname for client cluster form (virtual client) must be defined.

16

Part of NetWorker management file (/nsr)is automatically backed up on NetWorker.

Logical hostname for cluster service (virtual client name) to which resource on shared disk belongs on which NetWorker management file is hold must be defined.

Then, specify Virtual_Host (logical hostname (virtual server name)) which is specified by using clntwparam command for logical hostname of logical hostname management file.

For how to define logical hostname, refer to "[2] Defining Logical Host Name" in client cluster.

[5] Setting Application

Refer to "2.1.4 Creating NetWorker Cluster Application" for creating the user application of the NetWorker server by GUI.

Refer to "Chapter 6 Appendix A" for creating the user application of the NetWorker server by CUI.



[1] Setting NetWorker

Setup NetWorker.

Pay attention to the following to setup NetWorker. For procedure of setting NetWorker, refer to NetWorker manual. · Server Name of NetWorker

Server name of NetWorker is Virtual_Host (logical hostname (virtual server name)) which is setup by using clntwparam command.

· Setting Logical Server The following items must be defined for server which is specified as Virtual_Host.

1. Using nwadmin GUI, select [server] -> [specify server]. 2. Specify name of administrator of physical host which consists of cluster on [administrator]field

(user@hostname). example: "root@clus_phys1", "root@clus_phys2" If environment is on which hostname is taken over, name of administrator is not required to be specified.

· Setting NetWorker Define NetWorker client on operation node and it is not required on standby node. After defining environment, switch cluster service and ensure that setup on operation node is enabled. After it is ensured, switch service again.

· Setting Client Refer to "Setting Client" of Client Cluster.

2.1.3.6 Confirming Function

[1] Confirming Function

The message "INFO:GdCheck:Beginning of process watch"is logged after some trace information. If no error information is output, NetWorker starts to run normally.

Log file is /var/opt/FJSVclntw/logs/FJSVclntw.log.

[2] Confirmation on another host by switch of cluster

Switch the cluster and do the operation confirmation on other cluster nodes. Refer to "PRIMECLUSTER Installation guide" for the switch of the cluster.

2.1.3.7 Registering NetWorker License

[1] Registering NetWorker License

Different type of NetWorker license is required for server cluster form.

Follow the procedure below to enter and apply NetWorker enabler code and authorization code.

17

[1-1] Procedure 1. Ensure that NetWorker server is booted normally on operation host.

When NetWorker server is booted on operation host, enter NetWorker license after PRIMECLUSTER, NetWorker, and PRIMECLUSTER Wizard for NetWorker are installed.

2. Log in to operation host as superuser. 3. Use the following command to boot administration program (nwadmin).

# nwadmin & 4. Open "register" window on "server" on menu bar. 5. Select "create". 6. Enter enabler code on "Enabler code" field. 7. Open "server" window on "setup server" on "server" on menu bar and enter name, address, telephone number,

and email address. 8. Create the following file.

/nsr/res/hostids 9. Write the hostid of operation host and standby host by the following format to /nsr/res/hostids file created in

procedure 8. - - format

hostid of operation host and standby host. To find each hostid, execute hostid command on each host.

- - example 1 If the hostid is as follows: hostid for operation host:12345678 hostid for standby host:87654321 Write down hostid as follows 12345678:87654321

- - example 2 If the hostid is as follows: hostid for operation host:12345678 hostid for standby host:87654321 hostid for standby host:98765432 Write down hostid as follows 12345678:87654321:98765432

10. Switch cluster server and rebooting all the hosts, and reboot NetWorker server. After that, reboot management program (nwadmin).

11. Change displaying style of server window to chart style and output content of server resource. 12. Follow the procedure of applying NetWorker license.

Fill out password application form based on the output result on procedure 11 and send application form to password issuing office. When you receive "authorization code", enter the authorization code on "Auth Code" field on "register" window and apply that code. If authorization code is entered, you are allowed to operate NetWorker permanently.

For the detail of NetWorker enabler code and authorization code, refer to NetWorker manual.

Perform the procedure above only on operation host; not required on standby host.

2.1.4 Creating NetWorker Cluster Application

Here, the method of creating the NetWorker application by using PRIMECLUSTER Wizard is explained.

[1] Environment

The resource of "Fsystem (share file system)" and "Ipaddress (taking over IP address)" is already set up. (Refer to Fig1)

Moreover, NetWorker and PRIMECLUSTER Wizard for NetWorker are installed beforehand. CF (CLUSTER FOUNDATION) is under operation and RMS (Reliant Monitor Services) is in a stopped state.

It is the cluster composition (Refer to Fig2) after "Nwsv (PRIMECLUSTER Wizard for NetWorker)" is added and then "userApp_0" is made into parent at two sets (in the example of a setting, "dahliaRMS" is set to SysNode A and "violetRMS" is set to SysNode B) of nodes.

The above settings are already constructed according to "2.1.1.4 Environment Setting for PRIMECLUSTER Wizard for NetWorker" of "2.1.1 Environment Setup for Client Cluster Form" and "2.1.2.4 Environment Setting for PRIMECLUSTER Wizard for NetWorker" of "2.1.2 Environment Setting for Storage Node Cluster Form", "2.1.3.4 Environment Setting for PRIMECLUSTER Wizard for NetWorker" of "2.1.3 Environment Setting for Server Cluster Form" in this manual.

1.

18

2. Since the report of the help at the time of a setup is common to GUI/CUI, contents peculiar to CUI are also included in part.

[FIG 1. Cluster composition before create]

"Ipaddress (taking over IP address)" is set as SubApplication of "Nwsv (PRIMECLUSTER Wizard for NetWorker)", and "Fsystem (share file system)" is set as SubApplication of "Ipaddress (taking over IP address)".

[FIG 2. Cluster composition after create]

[2] Creation procedure

1. The following screen is displayed after starting userApplication Configuration Wizard. "Create Resource" is chosen after a check.

19

2. In the case of a NetWorker server cluster, a Resource type is set as "Nwsv" from a "Create Resource" screen. In the case of a NetWorker client cluster, the type is set as "Nwcl", and in the case of a NetWorker Storage Node/SAN Storage Node cluster, "Nwst" is set up. ( Henceforth, the setting method of the user application of a server, a Storage Node, and a client is the same).

3. Since a "Set up Resource" screen is displayed, choose "ApplicationName" or "Options" when a setup of a resource name or the each items of Nwsv has change, and move on to the next. It can change into arbitrary names and values. (There is usually no need to change)

20

The following screen is displayed when "Options" is chosen. Choose an item to change and move on to the next. It can change into arbitrary values.

The meaning of each item is as follows.

AutoRecover

Effective when it is set as yes. When abnormalities occur in a resource, RMS tries the reboot of a resource before changing to another node. An initial value is "yes".

ApplicationTimeout

The timeout value of the user application of PRIMECLUSTER Wizard for NetWorker is set up. An initial value is 300 seconds and can be set up in the range for 60 to 86400 seconds (24 hours). And even if it chooses "advanced setup", there are no changes of the displaying and the item which can be set up.

21

The following screen is displayed when "ApplicationName" is chosen. Choose an item to change and set up arbitrary names. (The following screen is an example in the case of changing a resource name into "Nwsv1" from "Nwsv")

4.Choose "SAVE+EXIT" in the "Set up Resource" screen.

5.When creation of a Nwsv resource is completed, make sure that the tree on the left of a "userApplication Configuration menu" screen is displayed as follows. After a checking, "Create userApplication" is chosen.

22

6. A userApplication name is specified in a "Set up userApplication name and operation method" screen.

7. The dahliaRMS and the violetRMS are added to "Selected SysNode" from "Available SysNode" on a "Select SysNode" screen.

23

8. Only setups of AutoSwitchOver and StandbyTransitions are changed from a "Set up Attribute" screen. Change the value if necessary for other items referring to "PRIMECLUSTER Installation guide". The meaning of AutoSwitchOver and StandbyTransitions are as follows. For the details of these attribute, refer to " PRIMECLUSTER Installation guide ".

AutoSwitchOver

When an obstacle occurs in userApplication, it sets up so that it will be changed automatically. Here, choose "HostFailure|ResourceFailure|ShutDown" (when obstacle occurs with a host or a resource, or shutdown RMS).

StandbyTransitions

The execution time of Standby state changes is set up. Here, choose "ClearFaultRequest|StartUp|SwitchRequest" (when the state of Faulted of userApplication is cleared and changes to Offline or when RMS is started, or when changes to another node).

24

It is necessary to set up of "AutoStartUp" and "AutoSwitchOver" in automation of cluster employment.

Usually, "AutoStartUp=Yes" and "AutoSwitchOver= HostFailure|ResourceFailure|ShutDown" are set up. It has not set up in the above example of a setting.

For the details of the contents of a setting, refer to the "PRIMECLUSTER Installation guide".

9. It adds to "Selected Resource" in Nwsv, Ipaddress0, and Fsystem0 on a "Select Resource" screen from "Available Resource".

10. Execute "Registration" after checking that SubApplication of Nwsv is set as Ipaddress0 and SubApplication of Ipaddress0 is set as Fsystem0 on a "Confirm registration" screen.

25

11. Make sure that the tree on the left of a "userApplication Configuration menu" screen is displayed as follows. All works are an end now.

12. Start RMS for "Global Cluster Services" from the "RMS" menu after selection from a top screen of Web-Based Admin View. About starting of RMS, refer to "PRIMECLUSTER Installation guide".

[Creating procedure of NetWorker user application by CUI]

Enter the following command to stop PRIMECLUSTER function on operation host.

# hvshut -a

Enter the following command to specify application.

# hvw -n Configfile

26

For the detail of setting user application, refer to "Chapter 6 Appendix A".

2.2 Notes for Constructing Tape Device Shared System

[1] Setting Operating Environment

If tape device is shared on cluster system on NetWorker Server, NetWorker Storage Node, and NetWorker San Storage Node, device path name of shared tape device must be specified with operating environment setting.

Use clntwparam command to setup operating environment.

For the detail of clntwparam command, refer to " 4.1 clntwparam - Setting Operating Environment ".

[example]

"# /etc/opt/FJSVclntw/bin/clntwparam Devices /dev/rmt/0cbn"

After installing PRIMECLUSTER Wizard for NetWorker, change operating environment before booting cluster service. If service is booted without specifying device pathname of shared tape device, tape may not be able to be mounted to jukebox.

Device and SCSI port which specified device uses must be correspond in cluster system. If specified value is not correspondent in each cluster host, tape library may not be able to use.

[2] Setting /kernel/drv/st.conf

If tape library is shared on cluster system, the below setting is needed.

Edit /kernel/drv/st.conf file using by vi command according to manual that appends in hardware.

After above setting, add "ST_NO_RESERVE_RELEASE 0x20000" in st.conf file.

[example: The case DLT8000 is used]

[Before changing]

tape-config-list="QUANTUM DLT8000","Quantum DLT8000","QDLT8";

QDLT8 = 1,0x36,0,0x9639,4,0x84,0x85,0x88,0x89,3;

[After changing]

tape-config-list="QUANTUM DLT8000","Quantum DLT8000","QDLT8";

QDLT8 = 1,0x36,0,0x29639,4,0x84,0x85,0x88,0x89,3;

Reboot this server.

Do not use the tape library that sets above settings except NetWorker. And the tape library can not be shared between two or more NetWorker Servers. Data may be vanished if the tape library is shared by two or more NetWorker Servers.

27

Chapter 3 Operation

3.1 Changing Environment

3.1.1 Changing Operating Environment for Detector and RMS Configuration Script

To change operating environment for detector and RMS configuration script, use clntwpara command PRIMECLUSTER Wizard for NetWorker provides.

The following parameters are allowed to be changed on each detector.

1. Server Detector · Logical hostname · NetWorker management file shared pathname · NetWorker management file local pathname · Device pathname which issues SCSI reset (must be specified for sharing tape device) · System log achieving mode · Recovery mode · Log size · NetWorker startup language · Monitoring detector cycle 2. Storage Node / SAN Storage Node Detector · Device pathname which issues SCSI reset (must be specified for sharing tape device) · System log achieving mode · Recovery mode · Log size · NetWorker startup language · Monitoring detector cycle 3. Client detector · System log achieving mode · Recovery mode · Log size · NetWorker startup language · Monitoring detector cycle After executing commands, changes are enabled user application is booted for the next time.

Command must be executed on all the hosts consisting of user application.

For the detail of clntwparam command, refer to " 4.1 clntwparam - Setting Operating Environment".

3.1.2 Changing Operating Environment for NetWorker Application

To define application for NetWorker, Server, Storage Node, and Client on Wizard, the following can be changed; · Change name of NetWorker application · Setup AutoStartUp · Change time for application timeout To change, follow the procedure below.

[How to change NetWorker user application by GUI]

Refer to "2.1.4 Creating NetWorker Cluster Application" for the change procedure.

[How to change NetWorker user application by CUI]

Enter the following command to stop PRIMECLUSTER function on operation host.

# hvshut -a

Enter the following command to specify application.

# hvw -n Configfile

After a menu is displayed, chose "Application-Edit".And chose the application of PRIMECLUSTER Wizard for NetWorker to change settings.

"ApplicationName":Changes the name of NetWorker user application.

29

"Options" -> "AutoRecover": In the case that "Yes" was chosen, recovery processing starts when abnormalities occur in NetWorker. In rhe case that "No" was chosen, fail over is carried out without performing recovery processing when abnormalities occur in NetWorker.

"Options" -> "ApplicationTimeout":Changes the timeout value of the user application of RIMECLUSTER Wizard for NetWorker. An initial value is 300 seconds and can be set up in the range for 60 to 86400 seconds (24 hours).

For the detail of setting user application, refer to "Chapter 6 Appendix A".

3.2 Auto re-execution of Backup

If failover occurs during backup, backup is re-executed automatically by retry function of NetWorker in client cluster form. Frequency for retry can be changed. For detail, refer to NetWorker manual.

By using NetWorker Autorestart function, if failure occurs on NetWorker server or operation host and failover occurs during backup, backup is resumed automatically on new operation host in server cluster form.

Detail of backup operation using Autorestart function is explained below.

3.2.1 What is Autorestart Function?

If backup is not ended normally due to host shutdown, backup operation is re-executed when booting NetWorker server next time. When rebooting NetWorker, write EOF to the tape that writing is interrupted and backup data from interrupted save set. For detail of function, refer to NetWorker manual.

Enabling Autorestart function allows re-execute backup automatically on new operation node if failover occurs during backup.

3.2.2 Procedure for Autorestart Setup

Enable Autorestart function by the procedure below.

[1] Procedure 1. Ensure that NetWorker server is booted normally on operation host. 2. Login to operation host as superuser. 3. Using the following command, boot management program (nwadmin):

# nwadmin & 4. Open [group] window on "customize" on menu bar. 5. Select "display" -> "detail" on [group] window. 6. Change "Autorestart" to "Enabled". To enable Autorestart function, "Autostart" must be changed to "Enabled". If "Manual restart" is specified on "Options", "Autorestart" is not enabled. Note that if backup is interrupted, "Manual restart" on "Options" is automatically selected.

3.2.3 Notes to Use Autorestart Function

Depends on timing of failover, data is not backed up automatically because error occurs on NetWorker before Autorestart is enabled. If such a case occurs, cause of error on NetWorker must be resolved before backup manually.

Autorestart is enabled only with server-cluster form on NetWorker.

Data must be re-backed up manually with other form such as client cluster form, Storage Node form, and SUN Storage Node form.

3.3 Stopping NetWorker During Cluster Operation

· If NetWorker is stopped by normal procedure, NetWorker daemon is rebooted and host is failed over to another host because PRIMECLUSTER Wizard for NetWorker monitors NetWorker operation during operating PRIMECLUSTER. To disable monitoring NetWorker temporary, execute the following command;

· Command used to stop monitoring /etc/opt/FJSVclntw/bin/hvnwdisable application_name resource_name

· Command to resume monitoring /etc/opt/FJSVclntw/bin/hvnwenable application_name resource_name

Execute these commands on operating host.

"Application_name" specifies the user application of PRIMECLUSTER. "Resource_name" specifies the stopping

30

resource name. Refer to hvnwdisable and hvnwenable of "Chapter 4 Commands" in this book for details of the command. Execute "hvdisp" of PRIMECLUSTER to makesure the resource name. Refer to "hvdisp" for details of the command " PRIMECLUSTER Installation guide ".

Shutting down NetWorker without stopping the user application to stop the monitoring of the NetWorker server becomes possible . Moreover, the cluster operation is able not to be considered and maintain NetWorker. In this case, the state of the user application of NetWorker is always Online. When NetWorker is observed again, the hvnwenable command is used.

If AutoRecover is enabled when NetWorker application is created, boot NetWorker daemon by using AutoRecover function. If AutoRecover is not enabled, use the following command and resume operation.

# /etc/init.d/networker start

# /usr/sbin/nsrd -k hostname

hostname indicates virtual hostname which is specified on Virtual_Path.

3.4 Notes for Operation

· On the host on which NetWorker server is run During server is run, NetWorker server is run on operation host; therefore, NetWorker server can not be run on standby host and shared disk can not be backed up on standby host.

· file.xxxx File If monitor is not stopped normally due to failure on host, file.xxxx (xxxx is number) may be stored on /var/opt/FJSVclntw/logs. This file may be used for testing when failure occurs.

· Notes for shared operation of tape device If failover occurs during robot is operated on library in transferring tape, backup may not be ended normally. In such a case, execute "nsrjb -H" and "nsrjb -I" command and backup manually.

· About the message on syslog · Although the following messages may be displayed on a console screen at the time of node starting and a

node change, it does not have influence on operation. syslogd: /nsr/logs/messages: Input-and-output error syslogd: /nsr/logs/messages: There are a file and no directory. syslogd: /nsr/logs/summary": There are a file and no directory. The file in this message is a log file of a NetWorker server, and is performing the writing to these log files using syslogd. In case mount processing to a shared disk is performed at the time of node starting or a change and the message output from the application which is using other syslogd(s) in the state where it became impossible to refer to these files temporarily is performed, this message output generates a /nsr directory. The message file of the /var/adm subordinate who is using Syslogd etc. is normally outputted, while this message is displayed. Moreover, since it is in the state where NetWorker is not started, it is not used for these log files of a NetWorker server.

· The index automatic restoration function of this product is realized by performing the following processings at the time of NetWorker starting. - Check an index for no abnormalities using the "nsrck" command which NetWorker offers. - Restore by executing a "nsrck -F" command to the index by which abnormalities were detected. However, the abnormalities in an index may not be notified by the "nsrck" command depending on the kind of abnormalities in an index. When the abnormalities in an index are not notified by the "nsrck" command, in spite of choosing the mode which performs index automatic restoration, since index automatic restoration is not carried out, the abnormalities in an index may fail in it at backup owing to. When such a phenomenon occurs, please back up again after restoring the target index by executing a "nsrck -F" command. The example of the message at the time of this phenomenon generating is shown below.

· Message of nwadmin : (Fri) 13:05:06 cat:/var/tmp saving to pool 'Default' (cat.004) [E0231-E0232] (Fri) 13:05:12 cat:/var/tmp done saving to pool 'Default' (cat.004) 23 MB [E0231-E022R-E0232] (Fri) 13:05:13 cat:/var/tmp saving to pool 'Default' (cat.004) [E0231-E0232] (Fri) 13:05:19 cat:/var/tmp done saving to pool 'Default' (cat.004) 23 MB [E0231-E022R-E0232] (Fri) 13:05:20 cat:bootstrap saving to pool 'Default' (cat.004) [E0231-E0232] (Fri) 13:05:25 cat:bootstrap done saving to pool 'Default' (cat.004) 104 KB [E0231-E022R-E0232] (Fri) 13:05:25 cat:bootstrap saving to pool 'Default' (cat.004) [E0231-E0232] (Fri) 13:05:30 cat:bootstrap done saving to pool 'Default' (cat.004) 104 KB [E0231-E022R-E0232] (Fri) 13:05:31 savegroup alert: test completed, 1 client(s) (cat Failed) [E0281-404E-4043]

3.5 Troubleshooting

3.5.1 Treatment for Trouble

Log information of PRIMECLUSTER Wizard for NetWorker is described on the following file; · Server Cluster

/var/opt/FJSVclntw/logs/clnwcdll.log

31

/var/opt/FJSVclntw/logs/FJSVclntw.log /var/opt/FJSVclntw/logs/FJSVclntw.script.log

· Storage Cluster /var/opt/FJSVclntw/logs/clnwcdll.log /var/opt/FJSVclntw/logs/FJSVclnts.log /var/opt/FJSVclntw/logs/FJSVclnts.script.log

· Client Cluster /var/opt/FJSVclntw/logs/clnwcdll.log /var/opt/FJSVclntw/logs/FJSVclnwc.log /var/opt/FJSVclntw/logs/FJSVclnwc.script.log

To resolve trouble, refer to the file above and log information of PRIMECLUSTER and NetWorker.

For log information of PRIMECLUSTER and NetWorker, refer to their manual.

3.5.2 How to Achieve Trouble Information

Execute clntwlog command and achieve trouble information to notify trouble to our system engineer. Please notify detail of trouble such as logged information, content of trouble, and procedure of trouble to our system engineer.

For the detail of clntwlog command, refer to "4.2 clntwlog - Achieving Confidential".

3.5.3 Treatments for Frequent Trouble

Contents of frequent trouble and treatments are described below.

[1] Failure on Inventory

[1-1] Content for trouble

"Can not open for read. Input/output error". is displayed and mounting and unmounting cannot be executed normally.

Below is an example of NetWorker message.

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

Device:

/dev/rmt/0cbn (J) dlt7000 is not mounted. Can not open for read-only. Input/output error.

Message:

(Mon) 10:00:00 index notice: Checking of 1client has completed. [E0285-U03A]

(Mon) 10:01:34 media warning: /dev/rmt/0cbn is in the process of opening: Input/output error

[E0284-E0263]

(Mon) 10:01:34 /dev/rmt/0cbn Cannot open for read-only. Input/output error.[270GH]

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

[1-2] Treatment

NetWorker may not recognize status of tape device precisely.

This could occur in cases such as tape device is operated manually or failover occurs due to shutdown on host while running Autochanger or standby host is rebooted during Autochanger is running.

Re-inventory by the procedure below. 1. Reset by executing the following command;

# nsrjb -H 2. Re-inventory by executing the following command;

# nsrjb -I For detail of nsrjb command, refer to NetWorker manual.

[2] Failure on Index

[2-1] Content of Trouble

"index notice: Failed checking client cat (incorrect database header)" and can not backup.

Example of NetWorker message is shown below.

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

32

Device:

/dev/rmt/0cbn (J) dlt7000 cat.001 mount completed dlt7000 tape cat.001

message:

(Mon) 10:00:00 index notice: Failed checking client cat (incorrect database header)[E0285-V02B-U036]

(Mon) 10:00:00 index notice: Completed checking 1 client [E0285-U03A]

(Mon) 10:00:39 media info: dlt7000 tape cat.001 was written before crush occurs. [E0286-2702V]

(Mon) 10:01:00 media info: read 354 record and EOF mark is after file 3.

[E0286-27033]

(Mon) 10:01:05 /dev/rmt/0cbn mount completed dlt7000 tape cat.001 [E0WK]

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

[2-2] Treatment

Index file of NetWorker may be destroyed.

This could occur if failover occurs due to host shutdown during backup.

Recover NetWorker index by the following procedure. 1. Check the index.

# nsrck 2. Recover index.

# nsrck -F client name For the detail of nsrck command, refer to NetWorker manual.

[3] Input/Output Error


Input and output error occurs with tape shared environment ; therefore, tape can not be mounted and unmounted.

[3-2] Treatment

Device path may not be specified.

If device path name is not specified with tape shared environment, reboot cluster service after specifying tape device name by using clntwparam command.

[4] The error at the time of NetWorker server starting


The following messages are outputted to /var/adm/messages and a NetWorker server does not start.

nsrd: Can't start nsrd becausee /nsr/res (/nsr) is local, and NetWorker is configured as a cluster server. Use cluster manager to check NetWorker service status.

[4-2] Treatment

It is output when there is no management database (/nsr) of NetWorker in a shared disk, or when the path which the management database of NetWorker exists in a setup of a cluster mount information file is not registered. Please make sure the following two points.

1. Please make sure whether the mount path described by the cluster mount information file specified by /etc/opt/FJSVclntw/etc/clnwc.env (logical node name management file) is set as the shared disk. For details, refer to "[2] Defining Logical Host Name" in this book "2.1.3.4 Environment Setting for PRIMECLUSTER Wizard for NetWorker".

2. Please make sure whether Virtual_Path (management file shared path name) set up by the clntwparam command is set up on the shared disk. For details, refer to this book "4.1 clntwparam - Setting Operating Environment".

[5] Cannot back up (shared disk resources of a logical node)


Although the NetWorker server has started, the shared disk resources of a logical node cannot be backed up. Or the

33

34

shared disk resources of the logical node of a client cluster are not backed up.

[5-2] Treatment

It generates, when the setup of the shared disk resources which a logical node owns is not performed correctly. Please make sure the following setup.

1. Please make sure whether the logical node name which a setup of the logical node for backup is included, or was mistaken by /etc/opt/FJSVclntw/etc/clnwc.env (logical node name management file) is set up. For the detail, refer to this book "2.1.3.4 Environment Setting for PRIMECLUSTER Wizard for NetWorker".

2. Please make sure whether the directory for backup is set up with a cluster mount information file or a RAW device file path. Here, when it is set as a save set by making applicable to backup the path which is not set up, backup processing is skipped without outputting an error about backup of the save set as specification of NetWorker. For the detail, refer to this book "2.1.3.4 Environment Setting for PRIMECLUSTER Wizard for NetWorker".

[6] Cannot back up (local disk resources).


The local disk resources of the node belonging to a cluster cannot be backed up.

[6-2] Treatment

Please make sure whether the mount path of local disks, such as "/", is set as the description in the cluster mount information file specified by /etc/opt/FJSVclntw/etc/clnwc.env (logical node name management file). For the detail, refer to this book "2.1.3.4 Environment Setting for PRIMECLUSTER Wizard for NetWorker".

Chapter 4 Commands

4.1 clntwparam - Setting Operating Environment

[1] Executing User

Superuser

[2] Form

/etc/opt/FJSVclntw/bin/clntwparam [parameter name Specified value]

/etc/opt/FJSVclntw/bin/clntwparam -p [parameter name]

[3] Explanation of Feature

Specify and display operating environment for detector and RMS configuration script.

Value can not be specified to more than one parameters at a time.

[4] Parameter

Define operating environment by specifying "parameter name specifying value". Display operating environment by specifying "-p parameter name". If specifying "parameter name" is omitted, all currently specified parameters are displayed. The following content can be specified for "parameter name specifying value".

* Forms in the parenthesis indicates that it can be specified for form with NetWorker.

* Describe SAN Storage Node and Storage Node as Storage Node. Virtual_Host Logical Hostname (Server)

Specify logical hostname (virtual server name of NetWorker) which is related to virtual IP for "logical hostname", Logical hostname must be specified for operating NetWorker Server. It is not necessary to set it when hostname succession is used. (example) /etc/opt/FJSVclntw/bin/clntwparam Virtual_Host lnode

Virtual_Path management file shared pathname (Server)

Specify destinated directory on shared disk on NetWorker management file which is specified when installing NetWorker for "management file shared pathname". This must be specified for operating NetWorker Server. (example) /etc/opt/FJSVclntw/bin/clntwparam Virtual_Path /rdisk/nsr

Local_Path management file local pathname (Server)

Specify direction for NetWorker management file holding directory on local disk for "management file local pathname". This must be specified for operating NetWorker Server. (example) /etc/opt/FJSVclntw/bin/clntwparam Local_Path /ldisk/nsr

Devices Device Pathname (Server/Storage Node)

Specify device pathname of tape device that is to use for "Device pathname". If this is specified, SCSI reset is issued to specified device immediately before booting NetWorker. This must be specified to share tape device on SCSI multi-initiate connection. If more than one tape device exist, specify "device pathname" by entering space between device pathname. This must be specified for operating NetWorker Server and Storage Node. (example) /etc/opt/FJSVclntw/bin/clntwparam Devices /dev/rmt/0cbn /dev/rmt/1cbn

Syslog Facility and Priority (Server/Storage Node/Client)

Monitor specifies the mode to achieve system log. daemon, local0, local1, local2, local3, local4, local5, local6, local7, and user can be specified for facility. notice, err, warning, info, and debug can be specified for priority. Specify daemon.err for initial value. (example)

35

/etc/opt/FJSVclntw/bin/clntwparam Syslog local1.err Recovery-Mode Mode (Server/Storage Node/Client)

Specify recovery mode with which to boot monitor. 0 indicates no recovery for index. 1 indicates perform only recovery for index. 0 and 1 are the values that can be specified. The initial value is 1. (example) /etc/opt/FJSVclntw/bin/clntwparam Recovery-Mode 0

Log-Size Log-size (KB) (Server/Storage Node/Client)

If size is over the range of specified size, change the name to *.old and create a new file. The range that can be specified is 10 to 4096. Initial value is 512. (example) /etc/opt/FJSVclntw/bin/clntwparam Log-Size 1024

NetWorker-Lang Language used when booting NetWorker (Server/Storage Node/Client)

When NetWorker is booted, NetWorker monitor specifies this value as LANG of environment variable. "C" or "ja" can be specified. "ja" must be specified for initial value. If "C" is specified, NetWorker is booted with English mode; if "ja" is specified, NetWorker is booted with Japanese mode. (example) /etc/opt/FJSVclntw/bin/clntwparam NetWorker-Lang ja

Detector_Interval monitoring interval(s) (Server/Storage Node/Client)

Specify interval for monitoring NetWorker daemon. The range for specifying is 5 to 60. The initial value must be 10.

[5] Status for Completion

0 : normally stopped except for above : stopped abnormally

4.2 clntwlog - Achieving Confidential

[1] Executing User

Superuser

[2] Form

/etc/opt/FJSVclntw/bin/clntwlog [-d output destination directory path]

[3] Features

Achieve resource for trouble

The name of outpur file is clntwtrace.tar.Z .

[4] Parameter

To specify destinated output directory, specify "-d output destination directory path". This directory is used for working directory. The default is /var/tmp.

(example)

# /etc/opt/FJSVclntw/bin/clntwlog -d /tmp

Getting NetWorker log.

*** Internal log collection completion ***

*** NetWorker log collection completion ***

*** System log collection completion ***

Getting system information.

*** Process ***

*** Package ***

*** Network ***

36

*** Resource tree ***

*** tar + compress ***

complete

#

[5] Completion Status

0 : stopped normally except for above : stopped abnormally

[6] Notes

When this command executes in the state which the user application is "Stop", the latest log of NetWorker cannot be gathered. After mounting only a shared disk using by /usr/sbin/mount command, the latest is gathered. Or, detach the user application of NetWorker from the user application once or gather it by stopping the monitoring operation of NetWorker from PRIMECLUSTER temporarily (Refer to "3.3 Stopping NetWorker During Cluster Operation").

Disk space can not be confirmed by executing this command.

4.3 hvnwdisable - Temporary Stop of Monitoring

[1] Executing user

Superuser

[2] Form

/etc/opt/FJSVclntw/bin/hvnwdisable application_name resource_name

[3] Features

Stop monitoring application such as NetWorker on PRIMECLUSTER temporarily. Use this function for NetWorker maintenance.

[4] Parameter

application_name specifies the user application of PRIMECLUSTER, and the resource name which stops resource_name. Please check by performing command "hvdisp" of PRIMECLUSTER about a resource name. Refer to a "PRIMECLUSTER Installation guide" about the details of a "hvdisp" command.

(example)

# hvdisp -a

Local System: dahliaRMS

Configuration: /opt/SMAW/SMAWRrms/build/test001.us

Resource Type HostName State

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

dahliaRMS SysNode Online

violetRMS SysNode Online

generic userApplication Online

Machine001_generic andOp dahliaRMS

Machine000_generic andOp violetRMS Online

ManageProgram001_Nwsv gResource Online

Interface000_Ipaddress gResource Online

MountPoint001_Fsystem gResource Online

# /etc/opt/FJSVclntw/bin/hvnwdisable generic ManageProgram001_Nwsv

hvnwdisable: The detection of ManageProgram001_Nwsv was disabled.

#

37


0 : normally stopped except for above : stopped abnormally

4.4 hvnwenable - Resuming Monitoring

[1] Executing user

Superuser

[2] Form

/etc/opt/FJSVclntw/bin/hvnwenable application_name resource_name

[3] Features

Resume monitoring on application which is stopped by hvdisable command. Use this function for NetWorker maintenance.

[4] Parameter

application_name and resource_name specify the user application name and resource name which were specified to be the "hvdisable" command.

(example)*It is an example of a procedure after execution of hvnwdisable.

# nsr_shutdown <- Shutdown command of NetWorker

nsr_shutdown will kill the following processes

6411 ? S 0:00 /usr/sbin/nsrexecd

6421 ? S 0:00 /usr/sbin/nsrexecd

6444 ? S 0:02 /usr/sbin/nsrd -k v_node <- virtual node name

6484 ? S 0:00 /usr/sbin/nsrmmdbd

6491 ? S 0:00 /usr/sbin/nsrindexd

6513 ? S 0:00 /usr/sbin/nsrmmd -n 1

6523 ? S 0:00 /usr/sbin/nsrmmd -n 2

Do you want to continue? [Yes]?

* * Killing NetWorker daemons

---- Maintenance ----

# /etc/init.d/networker start <- Startup of NetWorker Client

# /usr/sbin/nsrd -k v_node <- Startup of NetWorker Server as a virtual name

# /etc/opt/FJSVclntw/bin/hvnwenable generic ManageProgram001_Nwsv

hvnwenable: The detection of ManageProgram001_Nwsv was enabled.

#



[6] Note

Use this command as a pair of a hvnwdisable command

4.5 nwclntwadd - Setting NetWorker shared Data-Base

[1] Executing user

Superuser

38

[2] Form

/etc/opt/FJSVclntw/bin/nwclntwadd

[3] Features

Set a sharing setting file of NetWorker server on a shared disk in the cluster system. Execute this command from one node in the cluster node.

[4] Parameter

No parameters.

(example)

It is an example when the substance of NetWorker data base (/nsr) is on a shared disk (here, "/networker/nsr" is specified in "Virtual_Path").

# /etc/opt/FJSVclntw/bin/nwclntwadd

PRIMECLUSTER Wizard for NetWorker Setup tool

1 /networker

2 /oracle

3 /data

Select Mount-Point Number (quit:q) : 1

Virtual_Path Mount

NetWorker Database copy

Virtual_Path Unmount

Setup is succeeded.

#



39

Chapter 5 Message List

This chapter describes error messages which are displayed during installation and operation of PRIMECLUSTER Wizard for NetWorker.

5.1 Error Messages During Installation

Content and meaning, and treatment for each error of messages appears during installation is described below.

Cannot install this package under "$OS".

Content

This product can not be installed to "$OS".

Treatment

Install this product to OS on which this product can be run.

Cannot install this package. This package needs Solaris 8 SPARC later.

Content

This product must be installed to Solaris(TM) 8 OE or later.

Treatment


Cannot install this package. This package needs Solaris for SPARC.

Content

This product must be installed to Solaris(TM) 8 OE or later for SPARC platform.

Treatment


5.2 Error Messages of Commands

Content, meaning, and treatment for each error message during execution of commands are described below.

Messages shown except for below may be output. For the messages shown on PRIMECLUSTER, refer to PRIMECLUSTER manual.

Message is displayed by the format: "package name : level of message : message number : message". "FJSVclntw" is displayed as "package name". The description of format below omits package name.

5.2.1 clntwparam-specific Message

Error:4001:Not system administrator's authority

Content

Not root authority.

41

Treatment

Re-execute by root authority.

Error:4201:Specified parameter ($PARAM) is not available.

Content

Specified parameter does not exist.

Treatment

Confirm parameter name and re-execute the parameter.

Error:4202:The range to specify for parameter ($PARAM) is $RANGE .

Content

Specified value is not within the range.

Treatment

Specify the value that is within range and re-execute.

Error:4203:Command ended abnormally. Code for detail:X,X

Content

Failure occurs within command.

Treatment

Contact to our system engineer.

5.2.2 clntwlog-specific Message

ERROR:4001:No system administrator authority.

Content

Not root authority.

Treatment

Re-execute by root authority.

ERROR:4021:The $PATH directory does not exist.

Content

Directory specified with -d option does not exist.

Treatment

Specify the directory within -d option.

42

ERROR:4022:Abnormal end. Detail:X,X

Content

Error occurs within command.

Treatment

Contact to our system engineer.

ERROR:4023:The "$CMD" command terminated abnormally. Processing is ended. Detail:X

Content

"$CMD"ended abnormally. Either /usr/bin/cp or /usr/bin/tar or /usr/bin/compress is in "$CMD". Example of displayed error message for disk shortage is shown below.

(example)

Getting NetWorker log.

*** Internal log collection completion ***

tar: write error: Error is detected on EOF.

ERROR: The /usr/bin/tar command terminated abnormally. Processing is ended. code:2

Treatment

Check disk space of /var/tmp or directory specified with -d option. Change the destinated directory and re-execute.

WARNING:2002:It was judged that the mountpoint of /nsr was /. Confirm the mountpoint of /nsr. Do you continue? (default: n) [y,n,?]

Content

This is alarm message that urges to check mount point of NetWorker management information directory (/nsr) and wait for user response.

This message is displayed if command is executed during cluster service is stopped or executed on instance host.

Treatment

Enter y if you continue after mount point of /nsr directory is confirmed. If you want to stop, enter n.

5.2.3 nwclntwadd-specific Message

ERROR : Shared-disk does not exist.

Content

The shared disk which can be used from PRIMECLUSTER does not exist.

Treatment

Set the shared disk which can be used with PRIMECLUSTER.

ERROR : Device or Mountpoint is not set.

Content

Setting "Device" or "Mountpoint" of the shared disk is illegal.

43

Treatment

Comfirm the shared disk setting.

ERROR : Mount of shared-disk is failed.

Content

The mounting of a shared disk failed.

Treatment

Confirm setting a shared disk or whether a shared disk's being using.

ERROR : Unmount of shared-disk is failed.

Content

The mounting of a shared disk failed.

Treatment

Confirm whether there is the process where a shared disk is used.

ERROR : Virtual_Path or Local_Path is not set.

Content

Neither "Virtual_Path" nor "Local_Path" are set.

Treatment

Confirm "Virtual_Path" and "Local_Path" of PRIMECLUSTER Wizard for NetWorker. (Refer to "4.1 clntwparam - Setting Operating Environment" for details)

ERROR : Copy of NetWorker's database(/nsr) is failed.

Content

The copying of a shared data area of NetWorker failed.

Treatment

Confirm whether there is existing/nsr area in a shared data area.

44

Chapter 6 Creating NetWorker Cluster Application (CUI)

In this part, how to create application for operating NetWorker in clustering environment on PRIMECLUSTER Wizard for NetWorker.

6.1 Creating Cluster Application (CUI)

The procedure of creating NetWorker cluster application is described below.

The procedure below must be performed on NetWorker server, NetWorker Storage Node and SAN Storage Node, NetWorker client. Follow the procedure below to create cluster application.

[1] Environment

In this example, there are two hosts (hostname of HOST A is dahlia; hostname of HOST B is violet) and the procedure of such a case is shown below.

Setup PRIMECLUSTER Wizard for NetWorker with cluster configuration below.

45

Cluster application of "Ipaddress (takeover IP) " and "Fsystem (shared file system) " whose parent is "generic" is specified on two hosts ("dahlia" and "violet").

NetWorker and PRIMECLUSTER Wizard for NetWorker has been installed on two hosts.

CF (Cluster Foundation) is running; RMS (Reliant Monitor Services) is stopped.

The above settings are already constructed according to "2.1.1.4 Environment Setting for PRIMECLUSTER Wizard for NetWorker" of "2.1.1 Environment Setup for Client Cluster Form" and "2.1.2.4 Environment Setting for PRIMECLUSTER Wizard for NetWorker" of "2.1.2 Environment Setting for Storage Node Cluster Form", "2.1.3.4 Environment Setting for PRIMECLUSTER Wizard for NetWorker" of "2.1.3 Environment Setting for Server Cluster Form" in this manual.

[2] Procedure

Enter the following command on operation host and "Creating Cluster Application" is then displayed. (In this case "test" is specified).

# hvw -n test

The following screen is displayed. Select "Application-Create".

46

When the following screen is displayed, select "OPTIONS".

The following screen is displayed; to display all the registered wizard setting, select "ShowAllAvailableWizards". ""ShowTurnKeyWizardsOnly" is specified on default.

The following screen appears. Select "Nwsv".

Select "Nwcl" to specify on NetWorker Client. Select "Nwst" to specify on NetWorker Storage Node and SAN Storage Node (procedure for setting is same).

The following screen will appear.

Application that should be booted before booting PRIMECLUSTER Wizard for NetWorker must be determined.Select "AdditionalSubApplication" and specify "takeover host IP" and "shared disk" which has been defined under the application of PRIMECLUSTER Wizard for NetWorker.

47

List of defined application is displayed; specify shared file system (Fsystem) "Fsystem" for sub application on PRIMECLUSTER Wizard for NetWorker.

The following screen appears. Specify defined takeover host IP for sub application on PRIMECLUSTER Wizard for NetWorker. Select "AdditionalSubApplication".

List of defined application is displayed; specify t sub application for takeover host on PRIMECLUSTER Wizard for NetWorker. Select "Ipaddress".

Select "SAVE+EXIT" and save.

48

Change definition of "generic" as upper application of PRIMECLUSTER for NetWorker.

Select "Application-Edit".

List of defined application is displayed; to change definition, select "generic".

Change "SubApplications" in "generic".

Select "SubApplications[1]=Ipaddress".

49

Clear setting of "SubApplications[1] " in "generic". Select "NONE" to clear setting.

Change the setting "SubApplications" to "PRIMECLUSTER Wizard for NetWorker".

Select "SubApplications[0]=Fsystem" .

50

The following screen appears. Select "Nwsv".

Setting on PRIMECLUSTER for NetWorker completes. However, you must change setting on PRIMECLUSTER. Select "(StandbyTransitions=)".

51

"StandbyTransitions" must be changed to "standby" while NetWorker clustering system is standby.

State of standby default is "offline"; therefore, NetWorker is not booted. Select "ClearFaultRequest|StartUp|SwitchRequest".

Select "SAVE+EXIT" and save.

52

It is necessary to set up of "AutoStartUp" and "AutoSwitchOver" in automation of cluster employment.

Usually,"AutoStartUp=Yes"and "AutoSwitchOver= HostFailure|ResourceFailure|ShutDown" are set up. In this example, it has already been set (Refer to figure of procedure 19). For the details of the contents of a setting, refer to the "PRIMECLUSTER Installation guide".

Select "RETURN".

Go back to "Main RMS management menu" screen. Then, to create application, select "Configuration-Generate".

53

The following screen appears. Press return key.

The following screen appears.

To enable application, select "Configuration-Activate".

The following screen appears. Press return key after RMS runs normally is confirmed.

54

The following screen appears. Select "QUIT" and setting completes.

Boot RMS by using GUI or commands.

Enter the following command to use a command and to boot RMS.

# hvcm -c test

55

primecluster wizard for networker 4 - fujitsu … wizard for networker. networker becomes possible...

Documents