Selecting a Landscape Design Based on High Availability and Disaster Recovery Requirements

Based on your assessment of high availability and disaster recovery objectives, as well as factoring in other considerations that affect your implementation of SAP Mobile Platform, you can select one of several common landscape designs to use as a guideline.

The landscape designs detailed in this section are common designs that provide some guidelines for typical SAP Mobile Platform implementations. There are many possible landscape designs, and you should rely on solution architects who are familiar with all the requirements and specific circumstances to recommend a satisfactory approach for your enterprise.

Determine your parameters for recovery time objective (RTO) for downtime and recovery point objective (RPO) for data loss.
See Assessing High Availability and Disaster Recovery Objectives in Stage 1: Assess in this document.

Select the landscape design that best matches your objectives for downtime and data loss.

You may need to evaluate several of these landscapes to make your final selection.

Downtime/Data Loss Objectives*	Landscape Design
Downtime: user's best effort determines downtime Data Loss: complete data loss is tolerable	Individual Development and Test
Downtime: 4 – 24 hours Data Loss: 15 minutes – 24 hours	Shared Development and Test
Downtime: less than 4 hours Data Loss: no data loss	Fault-Tolerant Production

Downtime/Data Loss Objectives*

Landscape Design

Downtime: user's best effort determines downtime

Data Loss: complete data loss is tolerable

Individual Development and Test

Downtime: 4 – 24 hours

Data Loss: 15 minutes – 24 hours

Shared Development and Test

Downtime: less than 4 hours

Data Loss: no data loss

Fault-Tolerant Production

* The values for downtime and data loss are guidelines, based on sample installations that are operating in relatively isolated environments. In more complex environments, actual values for these parameters, especially for downtime, are typically adversely affected by the need to simultaneously restore other systems.

Individual Development and Test
For an individual working autonomously to develop or test applications, a single-server installation is generally sufficient. This landscape design does not include high availability or a disaster recovery infrastructure.
Shared Development and Test
A basic cluster installation supports a team working together to develop or test applications. To minimize work disruption, this landscape design includes a minimal high availability and disaster recovery infrastructure.
Fault-Tolerant Production
A cluster design in which a production system is mirrored by a complete disaster recovery system supports production applications that require no data loss and minimal downtime.

Parent topic: Stage 2: Design