What is RCO?
RCO is the abbreviation in English for the term
Recovery Consistency Objective and refers, as its name suggests, to consistency within recovery data. This is essential for business planning, especially in the case of decentralized or multi-site SMEs.
In turn, this term
It is nourished by two other fundamental concepts. First of all
RPO, which refers to the amount of data at risk of loss that the company can tolerate as "normal." While
RTO RTO refers to the maximum time that the business can do without the correct operation of its system without compromising the core processes of the business. With these two concepts, RTO and RPO, it would be enough to carry out a successful recovery in individual systems, but not with interconnected systems. To establish consistency between disaster recovery data, RCO is established. This is
Core importance for disaster recovery in distributed systems, such is the case of ERP. Unlike RPO and RTO, which are given by concrete figures, RCO
establishes an indicator of correspondence between real data and objective data for some processes or the business in general.
https://mkt.apser.es/ebook-amazon-web-services-aws-como-impulsor-de-la-transformacion-digital
Does my business really need disaster recovery measures?
As trivial as the question may seem, there are still people who are not aware of the role played by both IT security and policies and
disaster recovery strategies within a business. Currently,
In practically all companies, computer systems have an impact on their processes., which is why it is essential to use basic tools such as backups or security copies and complex ones, such as a disaster recovery strategy itself.
How to meet data recovery consistency objectives?
However, the magnitude of IT security measures is also in line with the type of technology available. When a business has several servers or handles information distributed across different computing equipment, it is essential to apply the concept of consistency within disaster recovery data. Why does this happen? Well, in non-distributed systems, with all the information centralized and a general backup, it is very easy, in the event of any eventuality, to restore the data without running the risk of having inconsistent information later. However, with distributed systems this is not the case.
Disaster Recovery in Distributed Systems
In distributed systems, which are commonly implemented in multi-site SMEs, there is a risk that after performing a restore on one of the nodes or servers, the data may present a significant level of inconsistency within the system. From this we can deduce that, as computer systems become more complex and core business processes overlap, the need to manage the concept of consistency between backup recovery data becomes imperative. Thus, financial processes, for example, demand a very high recovery consistency (100% or close to it), while other businesses may be more flexible in this regard.
If you found this post interesting, you might also be interested in this one free PDF guide:
https://mkt.apser.es/ebook-amazon-web-services-aws-como-impulsor-de-la-transformacion-digital
