3.7.0 HP StorageWorks HP Scalable NAS File Serving Software administration guide - HP Scalable NAS 3.7 for Linux (AG513-96002, October 2009)

The replication state
Check the replication state
Replication is always in one of the states listed below. The state information is stored
in the mxds datastore. The replication state can be different for the cluster and
individual nodes. For example, replication can be running on the cluster but not be
running on a particular node.
DescriptionState
Configured. A replication configuration file has been imported and replication can
be started.
1
Running. The replication program rplmonitor is running.2
Waiting. An internal state indicating that rplmonitor is in transition to the running
state and is waiting for the administrative filesystem to become available.
3
Stopped. The replication program is running but the worker threads that perform
the replication are not running. To restart replication, see Start replication, page 267.
4
Exited. The replication program either exited because of a fatal error or was termin-
ated from the command line. To restart replication, see Restart replication when it
is not running on the cluster, page 267.
5
The rplstatus command reports the state information for the cluster and for each
individual node. The command also reports the preferred sentinel node, and, if
replication is running, the current sentinel node. In the following example, replication
is in state 2 (running), which is the normal state.
/opt/hpcfs/bin/rplstatus
Cluster replication status
2 (running)
Node replication status
10.30.31.3: 2 (running)
10.30.31.4: 2 (running)
10.30.31.5: 2 (running)
10.30.31.6: 2 (running)
Replication sentinel
preferred sentinel=10.30.31.6
current sentinel=10.30.31.3
Configure and manage replication262