PRIMECLUSTER Installation and Administration Guide 4.1 (for Solaris(TM) Operating System) |
Contents
Index
![]() ![]() |
Part 6 PRIMECLUSTER Products | > Chapter 13 PRIMECLUSTER Wizard for NetWorker | > 13.1 Functional Overview | > 13.1.3 Server Cluster |
NetWorker errors are automatically detected and corrected by running the RMS (Reliant Monitor Services) configuration script that is exclusive to NetWorker provided by PRIMECLUSTER Wizard for NetWorker and the process monitoring facility that monitors the NetWorker server on PRIMECLUSTER.
This automatic detection and recovery function reduces downtime of backup application.
RMS (Reliant Monitor Services) starts the RMS configuration script to start or stop NetWorker. Also, when an error occurs during NetWorker operation, the RMS configuration script is restarted with the AutoRecover function to recover the NetWorker operation. The RMS configuration script checks the NetWorker management database index during NetWorker startup. If an error occurs in the index, then it is automatically corrected.
The PRIMECLUSTER NetWorker process monitoring facility monitors the process of NetWorker. When the process monitoring facility detects a NetWorker error, it notifies RMS of the error. First, RMS attempts to restart NetWorker once, but if it doesn't work, it brings the Online node Faulted. The process monitoring facility continues monitoring NetWorker even after notifying RMS of the error. When NetWorker is restarted with the RMS configuration script, the process monitoring facility starts monitoring NetWorker again.
Details on each error and its recovery are given below:
The process monitoring facility monitors NetWorker, if an error is detected, it notifies RMS of the error. If the AutoRecover attribute is enabled, the RMS starts up NetWorker startup script after receiving the error notification.
To determine whether the AutoRecover function should be enabled, refer to the PRIMECLUSTER manuals.
The RMS configuration script checks the index by executing the NetWorker commands. If it determines that it is necessary to correct the index of the NetWorker management database, it corrects the index of the target client by executing the NetWorker commands. The RMS configuration script determines if the index needs to be recovered using the NetWorker command.
The index error might be caused by the following cases:
A failure occurs in NetWorker during backup
A running node is powered off during backup, and a failover occurs
You can select Yes or No in the recovery mode parameter provided by PRIMECLUSTER Wizard for NetWorker for index correction.
For details on how to set the recovery mode, see the "PRIMECLUSTER Wizard for NetWorker Configuration and Administration Guide."
For details on how to correct index errors manually, see the "PRIMECLUSTER Wizard for NetWorker Configuration and Administration Guide."
Contents
Index
![]() ![]() |