5.5.265 HP StorageWorks X9000 Series Release Notes

Remote replication
• 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_exportcfr -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.
• Continuous remote replication will fail if the configured cluster interface and the corresponding
cluster Virtual Interface (VIF) for the management console 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
nl
ibrix_exportcfrpreference command can be used to change the network interface
preference.
• 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.
Management console
• If the management console service is stopped on the active management console and, within a
minute, the passive management console experiences a shutdown or reboot, the passive
management console will become active when the node is restarted. When the fusionmanager
is started on the formerly active management console (or that node is rebooted), that management
console will also be in active mode. Although both management consoles are active, only one of
these consoles will control the cluster virtual interface.
To recover from this scenario, take the following steps:
1. Determine which management console is running the cluster virtual interface:
ifconfig -a
In the output, check for a configured bond0:1 virtual interface.
2. Place the management console that is not running the cluster interface into maintenance
mode, and then place it into passive mode:
ibrix_fm -m maintenance
ibrix_fm -m passive
8 Fixes