Perform SAP Tests

Perform the following series of tests. The test steps are different for each configuration. Some steps call for verifying that SAP is running correctly but do not call out specific tests to perform. For a list of possible tests to perform to verify that SAP is configured and running correctly, refer to the appendices of the SAP document, SAP R/3 in Switchover Environments.

Tests for Active/Active Configurations

1. When the SAP hierarchy is created, the SAP and DB will in-service on different servers. From an SAP GUI, log in to SAP. Verify that you can successfully log in and that SAP is running correctly.

2. Log out and re-log in through a redundant AS. Verify that you can successfully log in.

3. If you have set up a login group, verify that you can successfully log in through this group.

4. Using the LifeKeeper GUI, bring the SAP hierarchy in service on the SAP Backup Server. Both the SAP and DB will now be in service on the same server.

5. Again, verify that you can log in to SAP using the SAP virtual server name, a redundant AS and the login group. Verify that SAP is running correctly.

6. Using the LifeKeeper GUI, bring the DB hierarchy in service on the DB Backup Server. Each hierarchy will now be in service on its backup server.

7. Again, verify that you can log in to SAP using all login methods and that SAP is running correctly. If you execute transaction SM21, you should be able to see in the logs where the PAS lost then regained communication with the DB.

8. While logged in to SAP, shut down the SAP Backup server where SAP is currently in service by pushing the power supply switch. Verify that the SAP hierarchy comes in service on the SAP Primary Server, and that after the failover, you can again log in to the PAS, and that it is running correctly.

9. Restore power to the failed server. Using the LifeKeeper GUI, bring the DB hierarchy back in service on the DB Primary Server. Again, while logged in to SAP, shut down the DB Primary server where the DB is currently in service by pushing the power supply switch. Verify that the DB hierarchy comes in-service on the DB Backup Server and that, after the failover, you are still logged in to SAP and can execute transactions successfully.

10. Restore power to the failed server. Using the LifeKeeper GUI, bring the DB hierarchy back in service on the DB Primary Server.

Tests for Active/Standby Configurations

1. When the hierarchy is created, both the SAP and DB will be in service on the Primary Server. The redundant AS will be started on the Backup Server. From an SAP GUI, log in to SAP. Verify that you can successfully log in and that SAP is running correctly. Execute transaction SM51 to see the list of SAP servers. This list should include both the PAS or ASCS and AS.

2. Log out and re-log in through the redundant AS on the Backup Server. Verify that you can successfully log in.

3. If you have set up a login group, verify that you can successfully log in through this group.

4. Using the LifeKeeper GUI, bring the SAP/DB hierarchy in service on the Backup Server.

5. Again, verify that you can log in to SAP using the SAP virtual server name, a redundant AS and the login group. Verify that SAP is running correctly.

6. While logged in to SAP, shut down the SAP/DB Backup server where the hierarchy is currently in service by pushing the power supply switch. Verify that the SAP/DB hierarchy comes in service on the Primary Server, and after the failover, you can again log in to the PAS and that it is running correctly (you will lose your connection when the server goes down and will have to re-log in).

7. Restore power to the failed server. Again, while logged in to SAP, shut down the SAP/DB Primary server where the DB is currently in service by pushing the power supply switch. Verify that the SAP/DB hierarchy comes in service on the Backup Server and that, after the failover, you can again log in to SAP, and that it is running correctly.

8. Again, restore power to the failed server. Using the LifeKeeper GUI, bring the SAP/DB hierarchy in service on the Primary Server.