6.3.2 HP StoreAll OS Release Notes

Before starting the replication, ensure that cross-protocol ACL synchronization is enabled on all
source and target cluster nodes.
• When remote replication is running, if the target file system is unexported, the replication of data
will stop. To ensure that replication takes place, do not unexport a file system that is the target
for a replication (for example, with ibrix_crr_export -U).
• Remote replication will fail if the target file system is unmounted. To ensure that replication takes
place, do not unmount the target file system.
• When continuous remote replication is used and file serving nodes are configured for High
Availability, you will need to take the following steps following failure of a node:
1. Stop continuous remote replication.
2. After the migration to the surviving node is complete, restart continuous remote replication
to heal the replica.
If these steps are not taken, any changes that had not yet been replicated from the failed node
will be lost.
• No alert is generated if the continuous remote replication target becomes unavailable. Confirm
the connection to the target system by issuing a ping command and by inspecting
ibrcfrworker.log.
• Sparse files on the source file system are replicated unsparse on the target. That is, all blocks
corresponding to the file size are allocated on the target cluster. Consequently, if the target file
system is the same size as the source file system, remote replication can fail because there is no
space left on the target file system. To work around this situation, if the source system contains
large sparse files, be sure that the target file system is larger than the source file system, and large
enough to fit all files in an unsparsed manner.
• The mountpoint /mnt/ibrix is reserved for remote replication. Hiding or blocking this mountpoint
by mounting anything over the parent /mnt will prevent Run Once replication from working at
all, and the initial domain scan of Continuous replication will fail.
• When a replication task encounters a file on the target system that was added or changed outside
of a previous replication, the replication task stops and does not replicate the remaining files from
the source to the target.
• If the target file system is unmounted while an inter-cluster or intra-cluster CRR task is running, the
CRR task will not work properly. Before unmounting a file system, it is a best practice to verify
that the file system is not the target for a CRR task. If the file system is the target for a CRR task,
stop the task before unmounting the file system.
Data retention and validation
• In a retention-enabled file system, if the absolute pathname (/FSNAME/<filename>) of the file
is greater than 1023 characters, the checksum is not generated and the validation scan fails.
• When using the ibrix_datavalidation –s –f FSNAME [-d PATH] command, be aware
that if the PATH is a StoreAll Archiving Infrastructure directory, the files within the path will not
be validated.
• The ibrix_vs_snap command cannot delete a block snapshot file system that is enabled for
data retention. Instead, use the ibrix_fs command with the -R option. For example:
ibrix_fs -d -f block_snap_ifs2_1 -R
• Directories are not supported in the path list for the ibrix_reten_adm command. However,
the command does not display the correct error message when the path list includes a directory.
• PDF reports do not display on Internet Explorer with Adobe Reader 10.1.2 installed. Reports
display properly with earlier versions of Adobe Reader or with other supported browsers.
22 Workarounds