HP StoreAll Storage - Manual (Page 272)

3. If the ibrix_cud service is not running, start the ibrix_server services:
service ibrix_server start
4. Start a new replication task:
ibrix_crr -s -f -o -S -P [-e
]
The -S option specifies the directory under the source file system to synchronize with the
target directory. The -P option specifies the target directory.
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 Fusion Manager 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 ibrix_crr_nic command can be used
to change the server assignments (the server/NICs pairs that handle remote replication requests).
Truncating a file during replication
If a file is truncated while it is being replicated, the file is replicated successfully, but a Domain
scan failure message is displayed. Also, an error message is logged in the ibrcfrworker.log
file. The text of the message is similar to the following:
rsync: read errors mapping "/mnt/ibrix/filter/tasks/5/ifs1/test.dat": No data available (61)
rsync: read errors mapping "/ifs1/test.dat": No data available (61)
You can ignore these error messages. The file was replicated successfully.
Consideration for replication tasks when unmounting or deleting a file system
Before you unmount or delete a file system, verify that the file system is not a target for any active
continuous remote replication tasks. If the file system is a target for an active replication task, you
must stop the task before you unmount or delete the file system.
Replicating content between objects of different types on the same path and
with the same name fails
In this scenario, there could be a directory on the source cluster and a file on the target cluster that
use the same name (for example, test1):
•
On the source cluster: //test1(directory)
•
On the target cluster: //test1 (file)
Because they are different objects (directory, file) on the same path, the replication job will stop
because the object types do not match.
In the following scenario, replication will work because the objects are on different paths:
•
On the source cluster: //test1 (directory)
•
On the target cluster: //test_directory/test1 (file within a directory)
Troubleshooting custom metadata replication
Whether you are enabling or disabling custom metadata replication, you must monitor the applicable
log file until the message that the task was either enabled or disabled successfully is displayed.
See
“crr_cmd_replication.sh” (page 261) for more information.
For any other issues with custom metadata replication not documented here, contact HP Support.
272 Using continuous remote replication