The network path that is chosen for data replication between each pair of servers must also already be configured as a LifeKeeper communication path between those servers. To change the network path, see Changing the Data Replication Path.
When configuring DataKeeper resources, avoid using an interface/address already in use by a LifeKeeper IP resource that has local recovery enabled. For example, if a LifeKeeper IP resource is configured on interface eth1 having local recovery enabled with interface eth2, DataKeeper resources should avoid using either eth1 or eth2. Enabling local recovery will disable the interface during switchover to the backup interface which can cause SteelEye DataKeeper failure.
This release of SteelEye DataKeeper does not support Automatic Switchback for DataKeeper resources. Additionally, the Automatic Switchback restriction is applicable for any other LifeKeeper resource sitting on top of a DataKeeper resource.
© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.