Migrate Oracle to AWS RDS or EC2

We use our in-house DBMSys platform developed around data collection and analysis to capture the metrics from on-premise database servers such as IOPS, memory usage, and CPU utilization for specific period of time. Basing on this information we recommend our customers the most appropriate EC2 instance type for their system in AWS.

Some business situations require zero-downtime during the database migrations. The best way to accomplish this is to conduct a detailed planning and utilize the necessary data replication tools for proper execution.

These migration methodologies typically involve two components: an initial bulk extract/load and tracking the changes that occurred during the execution of the bulk step. Once these changes have been applied, you should validate the migrated data and conduct any necessary testing.

The replication process synchronizes the source and target databases and then replicates all data changes between them.

You can switch over to the database in AWS at any time because the source and target databases will always be in sync.

We consider Oracle Data Guard tool to be the most appropriate for zero-downtime migration tasks.

Please click out our white paper Best Practices for Migrating Oracle Databases to AWS EC2 instances for more information.

There are many approaches to database technology in AWS from infrastructure EC2 to managed RDS and the many flavors of database server that can be supported here.

Key here are understanding these points

• What is your current database and infrastructure technology and what is the appropriate match in AWS?
• What resources do you have to support your database technology in AWS? Is RDS or EC2 the correct approach?
• What is your HA/DR approach and can it be mapped to AWS
• What is your data Egress and Ingress and how will that affect your charges

DB Best can help you evaluate your current workload and direct you to the best technology in the AWS.

Imagine you have a 80 TB database that needs to be extracted and imported into AWS Redshift or Aurora database. Normally, It would take up to several weeks for extracting and migrating such databases over internet.

DB Best has worked with Amazon in exposing a Snowball Edge configuration option in the Schema Conversion Tool. With this feature, you can hookup a Snowball Edge device to your on-premises database, extract data and upload data to the Snowball Edge and send it to AWS for completing the import process.

DB Best Architects are trained to help you in configuring the Snowball Edge, in extracting and help you in completing the data transfer much faster.

DB Best’s architects can help you in automating the entire stack creation process leveraging AWS’s CloudFormation templates using command line scripts. These scripts take few command line parameters and setup your VPC, subnets, ELB, EC2 instances, databases, Auto-scaling groups, creating S3 buckets and uploading data, database restores and health checks.