AWS, Big Data, Cloud Computing

5 Mins Read

Disaster Recovery (DR) using AWS Database Migration Services

Why DR?

Disaster Recovery (DR) is the process an organization uses to recover access to their software, data, and/or hardware that are needed to resume the performance of normal, critical business functions after the event of either a natural disaster or a disaster caused by humans. In the event of a disaster, the continued operations of your company depend on the ability to replicate your IT systems and data.  The disaster recovery plan stipulates how a company will prepare for a disaster, what the company’s response will be and what steps it will take to ensure that operations can be restored.


When an unforeseen event takes place and causes day-to-day operations to come to a halt, a company will need to recover as quickly as possible to ensure you will continue providing services to clients and customers. A disaster recovery plan would place your production servers in a top tier data centre with no single point of failure on the power and network connections.

Why Cloud For DR?

Having DR sites in the Cloud reduces the need for data center space, IT infrastructure and IT resources, which leads to significant cost reductions, enabling smaller companies to deploy disaster recovery options that were previously only found in larger enterprises. There’s no need to invest in more hardware or allocate additional IT personnel to bother with extra maintenance tasks. Instead, you have convenient access to a supremely elastic infrastructure that scales seamlessly based on your resource demands.

When connected to the Cloud, you are not hinged to a single location, data center or network. So even if one building loses power after a vicious storm, your operation can stay online and continue to roll.

RTOs and RPOs can be realistically achieved in hours rather than days.

Since in Cloud the virtual server is hardware independent, the operating system, applications, patches and data can be safely and accurately transferred from one data centre to a second data centre without the burden of reloading each component of the server. This can dramatically reduce recovery times compared to conventional (non-virtualized) disaster recovery approaches where servers need to be loaded with the OS and application software and patched to the last configuration used in production before the data can be restored.

What is DMS?

AWS Database Migration Service is a service provided by AWS which helps you to migrate your databases to AWS quickly and securely. The source database remains fully operational during the migration, minimizing downtime to applications that rely on the database. The AWS Database Migration Service can migrate your data to and from most widely used commercial and open-source databases. The service aims to reduce the duration of database transfers, which can take months otherwise. AWS DMS can handle homogenous migrations, such as Oracle to Oracle, as well as heterogeneous migrations, such as Oracle to MySQL. One of the endpoints must always be in AWS; the other can be on-premises, running on an EC2 instance, or running on an RDS database instance.

The AWS Database Migration Service works by setting up and then managing a replication instance on AWS. This instance unloads data from the source database and loads it into the destination database and can be used for a one-time migration followed by on-going replication to support a migration that entails minimal downtime.

AWS Database Migration Service is simple to use. There is no need to install any drivers or applications, and it does not require changes to the source database. Once the migration has started, DMS manages all the complexities of the migration process including automatically replicating data changes that occur in the source database during the migration process.

Prerequisites for using DMS:

For more information see, Using an Oracle Database as a Source for AWS Database Migration Service & Using a PostgreSQL Database as a Target for AWS Database Migration Service.

Steps for implementation of DMS:


call mysql.rds_set_configuration (‘binlog retention hours’, 24);

For more information see,

Creating Replication Instance:

Creating Endpoints:

(Test endpoint connection helps to know if AWS DMS can communicate with your database or not.)

Creating Task:

When the task gets started the database from on-premises will start migrating to AWS Cloud (i.e on RDS).

If you want to know mare about AWS courses kindly visit our website

Voiced by Amazon Polly


CloudThat is a leading provider of cloud training and consulting services, empowering individuals and organizations to leverage the full potential of cloud computing. With a commitment to delivering cutting-edge expertise, CloudThat equips professionals with the skills needed to thrive in the digital era.



  1. Olivia Ava

    Apr 19, 2021


    It helps in migrating our databases quickly. In this case, we don’t need to know about coding. You would say it’s a CMS of transferring databases from one place to other securely.

  2. it support

    Feb 17, 2021


    very nice and informative article.

  3. aws training

    May 2, 2019


    Seems to be a crucial blog on Data Recovery.
    I would like to thank the members for sharing such useful blog.

    • Pritam Agrawal

      May 13, 2019


      Thank you!!!

    Click to Comment

Get The Most Out Of Us

Our support doesn't end here. We have monthly newsletters, study guides, practice questions, and more to assist you in upgrading your cloud career. Subscribe to get them all!