Disaster Recovery
In the last two years, about 80% of companies have had an incident that required the use of a disaster recovery plan. Organizations must protect, plan and prepare for any disruption.
EUDC DRaaS is a service for fast backup and recovery of critical data and systems after a disaster. Using cloud computing resources, the EUDC Disaster Recovery service is less expensive, more flexible and more easily scalable than using IT infrastructures in a secondary location.
Disaster Recovery as a Service (DRaaS)
What is Disaster Recovery?
Disaster Recovery (DR) encompasses the procedures, policies, or processes that prepare an organization's vital IT infrastructure to recover effectively from natural, man-made disasters or cyber attacks, and to ensure business continuity. The DR must cover any possible scenario that threatens the availability of the IT infrastructure.
In recent years, DR has taken on an increasingly predominant role in companies' budgets, often accounting for 20-25% of IT spending.
The correct Plan
A DR plan outlines how an organization will respond to any disaster scenario, in order to support time-sensitive business processes and functions and maintain business continuity.
This plan contains both receptive and preventive elements and is a key part of the company. On the receptive side, the plan outlines numerous disaster scenarios and defines the detailed responses to each, in order to reduce the negative impact of the event. In terms of prevention, the plan minimizes the negative effects of specific scenarios, defining what the organization must do to avoid them.
Specifically, a plan must anticipate and delineate an action plan in response to the loss of such critical IT components and services, such as:
To achieve maximum efficiency and keep costs under control, organizations should use a combination of internal resources and solutions provided by vendors in their disaster recovery planning. The optimal internal / provider mix depends on the specific disaster recovery objectives of the organization, which are measured by the Recovery Time Objective (RTO) and the Recovery Point Objective (RPO). The recovery time objective can be defined as the period of time in which a business can operate without system availability, while the recovery point objective expresses how old the data will be once the systems recover.
Disaster Recovery in Data Center
To meet an organization's RTO and RPO goals, data center operators face a key challenge: data synchronization. In other words: How to ensure that data from all alternative locations is up-to-date to ensure service consistency and business continuity, even in the event of a disaster?
To some extent, the answer to this question is the level of replication, which can be defined as the frequency with which the receiving system (backup environment) recognizes the receipt of data from the sending system (production environment). The most common replication methods are:
Synchronous replication
The safest, but resource-intensive replication method. In a synchronous replication scenario, the receiving system recognizes each change received from the sending system. Adopting this method requires maintaining a "hot" backup site and is the most efficient.
Semi-synchronous replication
The receiving system sends the confirmation only after a series of changes have been received. This method of synchronization is parallel to the "hot" approach and may be the right choice for services that, in the event of a disaster, may allow data loss and a period of inactivity.
Asynchronous replication
Replication of this method's data is faster, but less secure, because the sending system simply continues to send data without receiving a response. This method is best suited for static resources or scenarios where data loss is acceptable.
When creating a Disaster Recovery Plan, organizations must ensure that their recovery policy is complementary to the chosen timing method.
For example, the "hot" synchronization / recovery policy ensures that data is always 100% synchronized and that a parallel system is always ready to take over the production system with minimal latency or downtime. However, if a data center has chosen asynchronous replication, the cost of maintaining a "hot" server may not be justified, as the data may not be fully replicated at some point in the failure.
EUDC offers you consulting services for choosing the optimal solution.