Disaster Recovery & Backup
In any company there is always the possibility of a web downtime. The main priority is to be able to recover the environment as soon as possible. Therefore, Planeta Huerto commissioned us to design a platform that allows us to be quick in restoring the service in case of disaster.
Company: Planeta Huerto
Planeta Huerto of the Carrefour Group is an online store with information and healthy products.
Main factors on which the Disaster Recovery Plan acts to ensure business continuity
Backup and Disaster Recovery projects are one of the entry solutions that many companies use to validate the cloud as a business continuity strategy. The main risks of downtime for the Planeta Huerto website occur when it requires more resources and they cannot be provided because the maximum limit has been reached.
In this case, the two ways to increase the limits were specified for both the application layer (backend, middleware and frontend) and the database layer.
Other crashes could occur due to the following factors:
- Table crash in Database.
- Deployment with a bug in the application.
- DDoS attack.
In reality, there are a multitude of threats that can cause a website to crash. The most common ones have already been specified. But the important thing is to have a defined process in operation to recover data and functionality in the event of a system crash caused by a catastrophe, whether natural or intentional.
Disaster Recovery & Backup to overcome unforeseen events or failures
Backup solutions consist of programmed uploading of corporate data to the cloud so that in the event of loss they can be recovered for service restoration.
- Deployment of contingency platforms in the cloud.
- Automated cloud backup systems.
- Integration of local data centres with the cloud.
This contingency plan includes the action protocol and methodologies to be used when one, several or all of a company’s IT systems are suspended. The main focus of Disaster Recovery is to restart the critical processes of a company in the shortest possible time.
In this way, the impact produced by the disaster is minimised, allowing the organization and its workers to return to operating relatively normally until the problem is definitively solved.
In our approach, we have the key indicators RTO and RPO
- RTO (Recovery Time Objective): the maximum amount of time that business activity can be halted.
- RPO (Recovery Point Objective): the previous point in time to which we are willing to return to recover business data and functionality.
Configuring and managing alerts
In addition, alerts were set up in case of a fall:
- Preventive alert that warns us when a certain percentage of criticality is reached.
- Alert that allows us to know when the service is down before a customer calls us.
- Health check configuration to know when the service has been restored.
The tools we use for this project are DataSync, S3 and AWS Storage Gateway. In this way we can develop customized solutions to upload data to the cloud on a scheduled basis and retrieve it automatically if necessary. We also integrate Veeam Backup services in cloud environments for further storage optimization and agile operations.
A Disaster Recovery System has to provide a stable and robust solution that is capable of recovering a critical system in minutes. For this we use the AWS Elastic Disaster Recovery service which offers us a perfect solution to keep your standby system synchronized and ready to take control of your production loads in the event of a problem.
request proof of concept
Subscribe to receive exclusive content and business news in real time.
Alicante Science Park (UA campus extension) Alicante, 03005, Spain
(34) 671 76 54 11