The objectives you set for downtime and data loss largely determine the landscape
design for your SAP Mobile Platform implementation.
The main determinants of your SAP Mobile Platform landscape design are the reliability requirements that the
system must meet. Two measures of system reliability are typically used:
- Recovery time objective (RTO) – acceptable downtime; the maximum
duration of time within which a system must be restored after a failure.
- Recovery point objective (RPO) – acceptable data loss; the
maximum tolerable period from which data might be lost due to a major incident.
To help determine how much downtime and data loss is acceptable for your
SAP Mobile Platform implementation, consider these items:
- How important are the applications that will be supported?
- What is the cost to your organization when these applications
are unavailable?
- What is the cost to your organization of losing data that cannot
be restored, and must be reentered?
- Is your organization likely to lose customers if these
applications are unavailable, or if customers sometimes have to reenter
transactions?
Although it may be difficult to get quantitative answers to such
questions, you must determine objectives for downtime and data loss to design your
SAP Mobile Platform landscape. Keep these objectives
in mind as you review the rest of the assessment topics.