Amazon makes moving an on-premise database to the cloud as easy as possible. The infrastructure provider can thus also generate new users.
Amazon Web Services (AWS) makes a database migration service widely available. The fully managed service will allow users to migrate productive databases from on-premise data centers to the AWS cloud. Last autumn, AWS showed the service as a preview.
The migration service can move data to and from all major commercial and open database platforms, including Oracle, SQL Server, MySQL, MariaDB, and PostgreSQL. It supports both homogeneous migrations (eg from Oracle to Oracle) as well as heterogeneous between different database platforms, for example from Oracle to Amazon Aurora or Microsoft SQL Server to MySQL.
In the past, AWS believed that migrating a database to the cloud always ran the risk of losing revenue because of downtime or costly migration tools needed during the copy process.
The new migration service, on the other hand, is designed to ensure that all source database data changes made during the migration are constantly replicated to the target database so that the source database remains fully operational during the move. After the initial database migration is complete, the target database remains synchronized with the source database as desired. This allows customers to switch their applications from the source to the target database at the most convenient time.
“Hundreds of customers migrated more than a thousand of their on-premise databases to Amazon Aurora, other Amazon RDS engines, or Amazon EC2 databases during the preview phase of the AWS Database Migration Service, ” said Hal Berenson, Vice President of Relational Database Services at AWS , In less than eleven weeks, many customers have already used the AWS Schema Conversion Tool to switch database engines.
The cost side should also be lowered by the services. Migration tasks are set up in the AWS management console in minutes. For example, customers can define the connections between source and target databases and select the type of replication instance in which the migration is performed.
Once setup is complete, the migration task can be run in a development or test environment to review each step. Optimally, the migrated application can then be used in the production environment with just a few clicks. In general, when using the migration service, customers only pay for the data processing resources used during the move. A database with a size of 1 TB can be migrated already for 3 dollars, as AWS promises. Full pricing information is available on the AWS website.
During migration, the service constantly monitors the source and target databases, network connection, and replication instance. If the replication flow is interrupted, the service automatically restarts the process and continues the migration from where it left off. If errors occur that can not be resolved automatically, customers will receive detailed diagnostic reports to make the necessary corrections themselves. An illustrated guide to migrating a database with the AWS service is provided by a blob from Chief Evangelist Jeff Barr.
“Customers have repeatedly told us that they would like help moving their on-premise databases to AWS or switching to more open database engine options, but the response to the AWS Database Migration Service was even stronger than expected.” says Berenson. “During the preview, a third used the migration service not only to migrate databases to the AWS cloud, but also moved to other database engines.”