6.3.3 HP StoreAll OS Release Notes (AW549-96082, January 2014)

Stop continuous remote replication.1.
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.
Segment evacuation
• The segment evacuator cannot evacuate segments in a READONLY, BROKEN or UNIVAILABLE
state.
SMB
• If you plan to use Microsoft Robocopy to migrate files to a StoreAll HP-SMB share that has data
retention enabled, you must:
◦ Disable the HP-SMB AllowPVFSFilemodeChange registry setting on every StoreAll cluster
nodes and restart HP-SMB. Disabling this registry setting prevents a file from transitioning to
a WORM or retained state through HP-SMB. However, it does not inhibit autocommit or the
ability to transition files to a WORM or retained state using other protocols.
◦ Disable autocommit if it is enabled.
If you do not perform these steps, some Robocopy operations will fail. Specifically, copies of all
read-only files and, in some cases, zero size files, will transition prematurely to a WORM state
during the copy process and Robocopy will be unable to apply all of the source file's attributes
to complete the copies.
Detailed steps are:
Workarounds 29