Earned run average: Difference between revisions
en>ZéroBot m r2.7.1) (Robot: Adding pl:Earned run average |
en>KylieTastic Reverted good faith edits by 207.183.230.126 (talk). (TW) |
||
| Line 1: | Line 1: | ||
The term '''recovery consistency objective''' (RCO) is used in [[business continuity planning]] in addition to [[recovery point objective]] (RPO) and [[recovery time objective]] (RTO). It applies [[data consistency]] objectives to [[continuous data protection]] services. Following the definitions for RPO and RTO, RCO defines a measurement for the consistency of distributed business data within interlinked systems after a disaster incident. Similar terms used in this context are "Recovery Consistency Characteristics" (RCC) and "recovery object granularity" (ROG). | |||
<ref>"How to evaluate a recovery management solution." West World Productions, 2006 [http://www.thefreelibrary.com/How+to+evaluate+a+recovery+management+solution-a0147748661]</ref> | |||
The term RCO focuses on business data consistency across multiple systems in [[Service-oriented architecture|SOA]]-driven business applications such as [[SAP ERP]]. It can be defined per business processes and reflects the individual requirements of corresponding business data and cross-system consistency. While RTO and RPO are absolute per-system values, RCO is expressed as percentage measuring the deviation between actual and targeted state of business data across systems for individual business processes or process groups. | |||
The following formula calculates RCO with "n" representing the number of business processes and "entities" representing an abstract value for business data: | |||
<math>\text{RCO} = 1 - \frac{(\text{number of inconsistent entities})_n}{(\text{number of entities})_n}</math> | |||
Targeting 100% RCO for a business process (distributed across several systems) would mean that no business data deviation is allowed after a disaster incident whereas any target below 100% allows deviation. Target values for RCO increase with the criticality of the underlying business data: logistics and banking-related business processes are often characterized by higher RCO requirements than those of CRM or HR systems. | |||
Including RCO considerations in addition to RTO and RPO in the [[business impact analysis]] helps to focus on the integrity of business data and processes in complex application environments.<ref>Josh Krischer, Donna Scott, Roberta J. Witty: "Six Myths About Business Continuity Management and | |||
Disaster Recovery", Gartner Research [http://www.gartner.com/it/content/868800/868812/six_myths_about_bcm.pdf]</ref> RCO considerations should be included in the [[Disaster Recovery]] Architecture by manually defining multiple consistency points across the landscape or by special Disaster Recovery mirroring tools. | |||
== References == | |||
{{reflist}} | |||
{{DEFAULTSORT:Recovery Consistency Objective}} | |||
[[Category:Business continuity and disaster recovery]] | |||
Revision as of 22:41, 11 December 2013
The term recovery consistency objective (RCO) is used in business continuity planning in addition to recovery point objective (RPO) and recovery time objective (RTO). It applies data consistency objectives to continuous data protection services. Following the definitions for RPO and RTO, RCO defines a measurement for the consistency of distributed business data within interlinked systems after a disaster incident. Similar terms used in this context are "Recovery Consistency Characteristics" (RCC) and "recovery object granularity" (ROG). [1]
The term RCO focuses on business data consistency across multiple systems in SOA-driven business applications such as SAP ERP. It can be defined per business processes and reflects the individual requirements of corresponding business data and cross-system consistency. While RTO and RPO are absolute per-system values, RCO is expressed as percentage measuring the deviation between actual and targeted state of business data across systems for individual business processes or process groups.
The following formula calculates RCO with "n" representing the number of business processes and "entities" representing an abstract value for business data:
Targeting 100% RCO for a business process (distributed across several systems) would mean that no business data deviation is allowed after a disaster incident whereas any target below 100% allows deviation. Target values for RCO increase with the criticality of the underlying business data: logistics and banking-related business processes are often characterized by higher RCO requirements than those of CRM or HR systems.
Including RCO considerations in addition to RTO and RPO in the business impact analysis helps to focus on the integrity of business data and processes in complex application environments.[2] RCO considerations should be included in the Disaster Recovery Architecture by manually defining multiple consistency points across the landscape or by special Disaster Recovery mirroring tools.
References
43 year old Petroleum Engineer Harry from Deep River, usually spends time with hobbies and interests like renting movies, property developers in singapore new condominium and vehicle racing. Constantly enjoys going to destinations like Camino Real de Tierra Adentro.