You can test your DataKeeper resource hierarchy by initiating a manual switchover. This will simulate a failover of the resource instance from the primary server to the backup server.
Performing a Manual Switchover from the LifeKeeper GUI
You can initiate a manual switchover from the LifeKeeper GUI by selecting Edit, Resource, and InService. For example, an in-service request executed on a backup server causes the DataKeeper resource hierarchy to be taken out-of-service on the primary server and placed in-service on the backup server. At this point, the original backup server is now the primary server and original primary server has now become the backup server.
The state of the DataKeeper resource on the new primary server is set to “Source” in the LifeKeeper GUI. During the switchover, the state of the DataKeeper resource on each target is initially set to “Out of Sync” to show that data is not replicating to that target yet. For a multi-target configuration the previous source will show “Out of Sync’ and other targets will show “Out of Sync (Wait for Previous Source)”. Resynchronization will automatically begin (the state will transition to “Resyncing”) on each target starting with the previous source. Once resynchronization is complete, the state will change to “Target”, which is the normal Standby condition. These state transitions will often occur quickly, so they may not be seen in the GUI.
If you execute the Out of Service request, the resource hierarchy is taken out of service without bringing it in service on the other server. The resource can only be brought in service on the same server if it was taken out of service during resynchronization.
Post your comment on this topic.