6.1 HP IBRIX X9000 Network Storage System CLI Reference (TA768-96057, June 2012)

ibrix_crr
Starts and stops the replication process and monitors the state of replication activity.
Description
The Continuous Remote Replication service (CRR) provides a transparent method to replicate
changes in a source file system on one cluster to a target file system on either the same cluster or
a second cluster. The remote replication service has two modes: continuous and run-once. For
detailed information about these modes, see the HP IBRIX X9000 Network Storage System File
System User Guide.
Replication tasks are started from the source cluster with ibrix_crr -s. When a replication task
is started for a file system, ibrix_crr dynamically generates a new task with a unique task id
for the replication instance.
Use ibrix_crr -s without the -o option to start a continuous replication task. A continuous
replication task does an initial full synchronization and then continues to replicate any new changes
made on the source. Continuous replication tasks continue to run until manually stopped by the
user.
Use the ibrix_crr -o option for the run-once mode to synchronize single directories or entire
file systems on the source and target in a single pass. The run-once tasks terminate on their own
when the synchronization is completed. Any task can be stopped manually if necessary.
Multiple replication tasks (run-once and/or continuous) can be started simultaneously.
Command options to get the status of replication can be executed from either the source cluster or
the remote target cluster.
NOTE: Remote replication must be configured (clusters registered with each other, and remote
replication exports configured) before replication tasks to remote clusters can be started. For detailed
information about configuring remote replication, see the HP IBRIX X9000 Network Storage System
File System User Guide.
NOTE: While continuous replication tasks ensure that file systems remain synchronized, run-once
tasks replicate a single-pass state of the source, and therefore can experience variations if there
is I/O activity while the task is running. For example, if the source file foo.txt has already been
replicated by the active task and is then edited or deleted while the run-once task is still active, the
changes to foo.txt are not made on the target. The foo.txt file on the target remains as written
by the run-once task.
NOTE: If a source or target file system is unmounted and ibrix_fsck is run to check it, a full
resynchronization is recommended.
Synopsis
Start a continuous or run-once remote replication task to a remote cluster:
ibrix_crr -s -f SRC_FSNAME [-o [-S SRC_DIR] ] –C TGT_CLUSTERNAME –F
TGT_FSNAME [-X TGTEXPORT] [-P TGTDIR] [-R]
The -f option specifies the source file system to be replicated, the -C option specifies the remote
target cluster, and the -F option specifies the remote file system. The -X option specifies the target
exported directory (the default is the root of the file system). The file system specified with the -F
option and the directory specified with the -X option must be exported from the target with
ibrix_crr_export. Optionally, you can also use -P to specify a directory under the replication
target export. The -R option bypasses retention compatibility checking.
Use the -o option for run-once replications. This option can be used to synchronize single directories
or entire file systems on the source and target in a single pass. If you do not specify a source
directory with the -S option, the replication starts at the root of the file system. The run-once task
terminates after the replication is complete; however, the task can be stopped manually, if necessary.
ibrix_crr 31