AspireNXT designs Disaster Recovery for SAP/ERP workload in AWS cloud

Task at Hand

One of our IT clients was in the market for a disaster recovery scenario on cloud with high availability and they reached out to us for help. The client had an Oracle ERP infrastructure running on premise with a RTO and RPO of 30 minutes. This with a database that was critical and needed continuous replication.

Our Solution

After an analysis of the situation, AspireNxt proposed the implementation of a DR on AWS Cloud in a pilot light scenario.

Why Pilot Light? Pilot light is often used to describe a DR scenario in which minimal version of an environment is always running on cloud.

We Deployed EC2 instance for the frontend and configured it with their current data and saved the server for future use as a machine image. We then deployed a Database EC2 instance for them that acted as pilot light since the server was running on an Oracle database and with continuous replication between on premise and cloud database server. The Configuration of these servers was minimal, just sufficient to run the workload and had autoscaling in place to ensure that setup is up and running if there is a high load also during a DR.

Once a DR was declared their server was launched using the saved Ami’s and Route 53 DNS record that was configured to point to the current server to distribute traffic. The initialization of the environment took around 20 minutes, which did not cross the RTO. Since there was continuous replication, the database was also updated so an RPO of 20 minutes was achieved.

Once the DR was over, we had to establish reverse mirroring/replication from DR site back to primary site, data changes were frozen and then we repointed to the primary site post which we unfroze the data changes.

Value Delivered

Client’s DR solution was implemented successfully with and RTO and RPO of 20 minutes from declaration of DR.

Technologies Used

Client Logo
Client Logo