5.6 HP StorageWorks X9000 File Serving Software User Guide (TA768-96035, June 2011)

Querying remote replication tasks
Use the following command to list all running and stopped continuous replication jobs in the cluster,
optionally restricted by the specified file system and host name.
ibrix_cfrjob -l [-f SRC_FSNAME] [-h HOSTNAME] [-C SRC_CLUSTERNAME]
To see more detailed information about continuous and run-once replication tasks, run
ibrix_cfrjob with the -i option. The command can optionally be restricted to a specified file
system and host name. The display shows the status of jobs on each node, as well as job summary
statistics (number of files in the queue, number of files processed). The query also indicates whether
scanning is in progress on a given file serving node and lists any error conditions.
ibrix_cfrjob -i [-f SRC_FSNAME] [-h HOSTNAME] [-C SRC_CLUSTERNAME]
The following command prints detailed information about continuous replication tasks matching
the specified task IDs. Use the -h option to limit the output to the specified host.
ibrix_cfrjob -i –n TASKIDS [ [-h HOSTNAME] [-C SRC_CLUSTERNAME]
Viewing replication status and activity
To view replication status and statistics, execute the ibrix_cfrjob -i command. If the command
is executed from the source side, that management console answers the query with information
gathered from the ibrcfrd daemons on the source-side file serving nodes.
Configuring remote failover/failback
When remote replication is configured from a local cluster to a remote cluster, you can fail over
the local cluster to the remote cluster:
1. Stop write traffic to the local site.
2. Wait for all remote replication queues to drain.
3. Stop remote replication on the local site.
4. Reconfigure shares as necessary on the remote site. The cluster name and IP addresses (or
VIFs) are different on the remote site, and changes are needed to allow clients to continue to
access shares.
5. Redirect write traffic to the remote site.
When the local cluster is healthy again, take the following steps to perform a failback from the
remote site:
1. Stop write traffic to the remote site.
2. Set up Run-Once remote replication, with the remote site acting as the source and the local
site acting as the destination.
3. When the Run-Once replication is complete, restore shares to their original configuration on
the local site, and verify that clients can access the shares.
4. Redirect write traffic to the local site.
Troubleshooting remote replication
Continuous remote replication fails when a private network is used
Continuous remote replication will fail if the configured cluster interface and the corresponding
cluster Virtual Interface (VIF) for the management console are in a private network on either the
source or target cluster. By default continuous remote replication uses the cluster interface and the
Cluster VIF (the ibrixinit –C and –v options, respectively) for communication between the
source cluster and the target cluster. To work around potential continuous remote replication
communication errors, it is important that the ibrixinit -C and -v arguments correspond to
a public interface and a public cluster VIF, respectively. If necessary, the
94 Using remote replication