Procedures at Your Site for High Availability

Purpose

This section helps you adapt the information given in the rest of the documentation to the SAP system setup at your site. The first section gives you some clues to how you can adapt the procedures at your site to cope with the special demands of high availability. Then there is a set of questions to help you assess your high availability requirements (this does not claim to be an exhaustive list of questions).

Finally, we provide two checklists. The general checklist covers a wide range of high availability issues while the single point of failure (SPOF) checklist covers how you can improve the overall availability of your system by looking at its particularly vulnerable aspects.

Before you implement high availability solutions, you need to assess the costs caused by systems failure compared to the costs of proposed improvements compared:

·         Estimate the costs caused by failure of your SAP systems for a specific length of time (for example, one hour), including lost revenue and the costs of recovering from the failure.

·         Estimate the costs that your business can afford to provide a reasonable level of protection against such a failure.

Process Flow

...

       1.      You think about high availability as early as possible in the installation of your SAP system. It is cheaper and easier to build in high availability from the start than to add it afterwards. Be sure to ask the questions mentioned above and run through the high availability checklists.

       2.      You regularly review your setup and procedures in the light of changing circumstances, particularly when the system configuration changes.