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

OR:
Use the ssh-keygen command to create the custom key pair. Then run the
rplkeys -i command to import the key pair into the mxds datastore and
publish it for replication use.
The rplkeys -c and -i commands attempt to publish the key on the destination
cluster. If the command is not successful (for example, because of ssh connection
issues), you can use rplkeys -d to install the key on the destination cluster after
the issues are fixed.
Hard link behavior
Because of the way that replication handles file change events, there is some odd
behavior if multiple hard links to a single file are created in the same directory during
a single interval. Each link will be given the same ID, and therefore only one of the
objects will be included in the master replication log. This means that only that object
will be replicated to the destination. (The hardlink instance that will be replicated is
the last one to be modified on the node with the lexically highest IP address.) All of
the user data will be on the destination, but the file structure will look different (it will
be missing some hard links to the file). Later changes to these links will cause them
to show up on the destination, as will any event that causes a sub-tree containing
the links to be walked.
Troubleshooting
The following information may be useful for resolving replication issues.
Replication files
The following logs and files may be helpful when troubleshooting replication issues.
Replication logs
The replication log files created by rplwatch are located in the /_adminfs
filesystem under the directory /replication/logs. The following types of logs
are created:
Path logs. These log files contain the inodes and absolute paths of the directories
included in the replica set. Replication uses this information internally to find the
absolute paths for modified files in the directories.
Configure and manage replication270