Data is growing rapidly nowadays because of which maintenance and monitoring of database servers have become complicated. In the case of on-premises database servers, configuring Read Replica, Multi Availability zone deployment, Automatic backup, Multiple region replication setup etc., takes a lot of time, resources, and cost. By moving the database workloads to cloud reduces the time and cost spent to a large extent. AWS provides Database Migration as a service(DMS) to migrate your database fast and securely with minimal downtime.

blog_insert

Need for Database Migration

There are many factors that can influence the decision to migrate databases in an organization. These are few of the reasons:

  • Legacy system does not have enough storage capacity
  • Need to upgrade hardware/software in a routine manner
  • Increasing business demands
  • Need for High Availability and Disaster Recovery systems
  • Non-availability of resources to manage on-premise Database servers

Method of Migration

AWS DMS 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 ongoing replication to support a migration that entails minimal downtime.  Along the way, DMS handles many of the complex details associated with migration, including data type transformation and conversion from one database platform to another. The service also monitors the replication and the health of the instance, notifies you if something goes wrong, and automatically provisions a replacement instance if necessary.

Migration made simple with just a few clicks-

Create the target database, migrate the database schema, set up the data replication process, and initiate the migration. After the target database has caught up with the source, you simply switch to using it in your production environment.

Types of migration

Homogeneous Migration. Migrating between the same database engine types. For example, migrating from Oracle to Oracle.

Heterogeneous Migration. Migration between different database engine types. For example, migrating from Oracle to MySQL. AWS Schema Conversion Tool helps to transform from one schema to another.

If the size of the database is in petabyte-scale then data is moved using data-transport solution AWS Snowball. And if the database size is even more massive, then it is done with AWS Snowmobile.

Benefits of AWS DMS

DB-Migration

Best practices from live implementations

  1. Improve database performance. Setup Read Replica to enhance the performance of read-heavy database workloads. A separate database is recommended for reads and another database which serves for both read and write operations.
  2. Improve data durability. Leverage Multi-AZ with Read Replica. It synchronously replicates live database into a standby database in a different Availability Zone(AZ).
  3. Seamless implementation. During the backup process, there could be some performance issues in the live database. By enabling  Multi-AZ, the entire backup is taken from a standby database and this does not affect the performance of the live database.
  4. Establish security. The DMS connection can be encrypted with the use of SSL certificates. A Hybrid connection can be used to transfer the file in a secure tunnel.

Right candidate for migration

Industries having large amounts of data and with rapid data growth, maintain and manage a fleet of database servers. All those database servers need hardware/software management, upgrades, and regular backup. By moving to AWS cloud, all these tasks are simplified with a few button clicks.