5.6.1 HP X9000 Series Release Notes (TA768-96053, September 2011)

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.
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
If the recovery is not successful, contact HP Support.
• If your cluster uses a dedicated management console, and you want to apply quotas to users and
groups from your Active Directory domain, take the following steps before assigning the quotas:
1. Install the likewise-cifs.x86_64.rpm. (This RPM is provided in the X9000 Software
distribution in the directory /usr/local/ibrix/installation/ibrix/distrib/
engine/RHEL5/x86-64.)
rpm –i likewise-cifs.x86_64-X9000_v5.5.rpm
2. Join the management console to the AD domain manually:
/opt/likewise/bin/domainjoin-cli join <domain name> <domain account
to join domain>
3. Stop Likewise:
/opt/likewise/bin/lwsm stop lwreg && /etc/init.d/lwsmd stop
Workarounds 11