Switchover and Failover Testing

Steps below are for testing the switchover and failover of a SIOS cluster for SAP. Open “SAP Logon” or “SAP GUI for Windows”, which is an SAP supplied Windows client the Windows client. The program can be downloaded from the SAP download site. The virtual IP address may be used as the “Application Server” on the Properties page. This ensures that a connection to the primary machine where the virtual ip resides is active.

1. Using the LifeKeeper GUI, failover from Node1 -> Node2. Right click on the top resource in the cluster underneath node2, and select “In Service…”. This demonstrates that node 2 is able to take over from node1 during a failure

After switchover has completed, check on the SAP GUI or reconnect where necessary and examine that SAP is still running normally.

You may also check if SAP processes are running in the OS.

2. Using the LifeKeeper GUI, failover from Node2 -> Node1. Right click on the top resource in the cluster underneath node2, and select “In Service…”. This demonstrates that node 1 is able to take over from node2 during a failure

After switchover has completed, check on the SAP GUI or reconnect where necessary and examine that SAP is still running normally.

You may also check if SAP processes are running in the OS.

3. On the command line interface on node 1 (active node), execute the following command to perform a “hard crash” of the OS

# halt -fni

After failover has completed, use the LifeKeeper GUI on node 2 to check visually that the services are failed over normally.

Check on the SAP GUI or reconnect where necessary and examine that SAP is still running normally.

You may also check if SAP processes are running in the OS.

Turn on node 1 again and use the LifeKeeper GUI on node 2 to check visually that the services are on node 1 becomes standby, and replication is started.

Note: Before attempting to do any more switchover or failover testing, ensure that the data replication resources have already completed their synchronization and are in sync.

4. Repeat step 2 or step 1 as necessary to switchover back to node 1, or to perform another crash testing on node 2.