Show TOC

Background documentationHigh Availability Locate this document in the navigation structure

 

The tasks for the system administrator depend on the high availability features that you have implemented. In general, you need to minimize both planned downtime and unplanned downtime for your SAP system. The tasks listed below are important to minimizing downtime in your system.

Getting Started

Note Note

High availability is a technically complex area, and implementation considerations vary according to your system setup.

For technical guidance when developing a high availability strategy or when implementing a specific product or feature, contact the appropriate source, such as your SAP consultant or your hardware partner.

For more information about business continuity in general in SAP environments, see the SAP Business Continuity Guide at http://scn.sap.com/community/business-continuity and SAP Business Continuity.

End of the note.
Technical System Landscape

For more information on a system landscape for high availability, see the Technical Infrastructure Guide at:

  http://service.sap.com/instguides   SAP NetWeaver   SAP NetWeaver <Product> 7.1   Installation  

Tasks on Demand

Reason

Task

More Information

System failure

Restore database

Database Administration

SAP system upgrade required

Upgrade SAP system

http://service.sap.com/upgrade

Database upgrade required

Upgrade database

  http://service.sap.com/instguides   Other Documentation   Database Upgrades  

Operating system upgrade required

Upgrade operating system

Operating system documentation

Periodic Tasks

Frequency

Task

More Information

Regularly

Test switchover functionality

http://scn.sap.com/community/business-continuity

Regularly

Database backup, online or offline, possibly with split-mirror

Database Administration

Note Note

How often you perform the periodic tasks depends on the requirements and nature of your installation.

For example, the frequency with which you expect a switchover to occur determines how often you test switchover functionality – if you expect frequent switchovers you need to frequently test switchover functionality.

End of the note.