Particular attention must be given to the operation of PRIMECLUSTER Wizard for NetWorker.
Features and functions
Below are guidelines and precautions to be taken in using the features and functions provided by PRIMECLUSTER Wizard for NetWorker.
For the node where NetWorker server is running
During server is running, NetWorker server is running on the OPERATING node. Therefore, the NetWorker server cannot be run and shared disk cannot be backed up on the STANDBY node.
About the storage node cluster operation
NetWorker 7.4/7.5/7.6 does not support the high available storage node in any cluster systems. Therefore, the storage node cluster operation is not supported for NetWorker 7.4/7.5/7.6.
Configuration
Below are guidelines and precautions to be taken in configuring an environment that allows for PRIMECLUSTER Wizard for NetWorker.
There is no problem in operation, though the default setting such as the label templates and managers becomes a physical node name when the server cluster operation is constructed. Change to an appropriate setting.
Operations
Below are guidelines and precautions to be taken in operating PRIMECLUSTER Wizard for NetWorker:
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 access to the tape device
It keeps waiting for the response from hardware when the cluster application is switched with NetWorker accessed the tape device. Therefore, the NetWorker process cannot stop and PRIMECLUSTER might have the node in the panic. Execute the switch of the cluster application with their no access to the tape device.
file.xxxx File
If monitor is not stopped normally due to node failure, file.xxxx (xxxx is number) may be stored on /var/opt/FJSVclntw/logs.
This file may be used for testing when failure occurs.
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.
About the Warning state when the NetWorker resource starts
There is no problem that a NetWorker resource may become the Warning state and the following message is output before it becomes the Online state, when the resource starts.
[ID 748625 daemon.warning] LOG3.011892417591080023 11 4 0 4.2 RMS (DET, 29): WARNING: Resource <ManageProgram001_Nwsv> received detector report DetReportsOnlineWarn" the WarningScript "/etc/opt/FJSVclntw/sys/clntwwarning" will be run."
If the NetWorker resource keeps the Warning state and it does not become the Online state, see "3.3.3 Bringing Warning NetWorker Resource to Online State" to solve the problem.
About the NetWorker Console server
In case you start the NetWorker Console server of NetWorker 7.4/7.5/7.6 on a node of the cluster, make the NetWorker cluster application the Online or Standby state because the NetWorker client daemon needs to be running in that node.
