##master-page:HomepageReadWritePageTemplate
##master-date:Unknown-Date
#format wiki
#language en
= High Availability IT systems =

== RPO and RTO's ==
 * '''Recovery Time Objective (RTO)'''
   * RTO is defined as the maximum amount of time that an IT-based business process can be down before the organization starts suffering unacceptable consequences (financial losses, impact to customer satisfaction, reputation, and so on). RTO indicates the downtime tolerance of a business process or an organization in general.
   * The RTO requirements are driven by the mission-critical nature of the business. Thus, for a system running a stock exchange, the RTO is zero or very near to zero.
   * An organization is likely to have varying RTO requirements across its various business processes. Thus, for a high volume e-commerce Web site, for which there is an expectation of rapid response times and for which customer switching costs are very low, the Web-based customer interaction system that drives e-commerce sales is likely to have an RTO close to zero. However, the RTO of the systems that support back-end operations, such as shipping and billing, can be higher. If these back-end systems are down, then the business may resort to manual operations temporarily without a significantly visible impact.
    || System Name   || RTO in 00h00  || Financial Loss || Description of Financial loss and impact ||
    || 1. || || || ||
    || 2. || || || ||
    || 3. || || || ||

 * '''Recovery Point Objective (RPO)'''
   * RPO is the maximum amount of data an IT-based business process may lose before causing detrimental harm to the organization. RPO indicates the data-loss tolerance of a business process or an organization in general. This data loss is often measured in terms of time, for example, 5 hours or 2 days worth of data loss.
   * A stock exchange where millions of dollars worth of transactions occur every minute cannot afford to lose any data. Thus, its RPO must be zero. Referring to the e-commerce example, the Web-based sales system does not strictly require an RPO of zero, although a low RPO is essential for customer satisfaction. However, its back-end merchandising and inventory update system may have a higher RPO; lost data in this case can be reentered.
    || System Data   || RPO in 00h00 of data loss  || Financial Loss || Description of Financial loss and impact ||
    || 1. || || || ||
    || 2. || || || ||
    || 3. || || || ||

== Links ==
 * [[http://docs.oracle.com/cd/B28359_01/server.111/b28281/hadesign.htm|High Availability Design @ Oracle]]

...
----
CategoryArchitecture