Migrating Oracle E-Business Suite using AWS Application Migration Service

AWS Application Migration Service (AWS MGN) is a migration and replication tool available from AWS which can be used for migrating the applications as well as for setting up DR environments on AWS. It works by migrating or replicating the blocks of storage devices from source to target. Because it operates at the block level, it can migrate various workloads, including enterprise resource planning (ERP) applications from virtual machines (VMs), cloud, or physical data center. AWS MGN supports migration from any OS to AWS. Following is an architecture showing various components of AWS MGN and how they work together to migrate workloads on AWS.

AWS MGN migration or disaster recovery

The AWS MGN orchestration engine automatically launches a fully operational Oracle E-Business Suite environment in the target AWS Region, enabling a recovery time objective (RTO) of minutes. The AWS MGN automated machine conversion process takes approximately 30 seconds, and ensures that OS machines replicated from physical, virtual, and cloud-based infrastructure will natively boot and run transparently in AWS, by automatically handling all hypervisor and OS configuration changes, boot process changes, and OS activation and installation of target infrastructure guest agents.

Major steps involved in migrating Oracle E-Business Suite environment using AWS MGN are as follows:

1. Identify the list of servers to be migrated by name, and break down the list to migration waves.

2. Install the AWS MGN software agents on the selected servers to initiate replication and confirm replication progress within the AWS MGN console.

3. Assess source Oracle E-Business Suite network to plan the network creation in the target infrastructure.

4. Create the target network within the target infrastructure of choice.

5. Once server replication is complete, create test target machines using the AWS MGN dashboard and confirm that they are functioning and accessible.

6. Upon confirmation of the successful target machines launch, engage with the business/application owners for Oracle E-Business Suite acceptance tests. If corrections are required, modify the target blueprints accordingly and repeat this step. If the acceptance tests are completed successfully, proceed to cutover.

7. Cutover procedure:

   1. Schedule a migration cutover window.

   2. Prevent user connectivity to the source Oracle E-Business Suite environment.

   3. Create a final version of the target machines.

   4. Confirm Oracle E-Business Suite application readiness.

   5. Redirect user traffic to the new target machines.

   6. Stop the AWS MGN replication on the source servers that were cutover, and decommission them.

Notes:

• For the database tier, use of Oracle native tools outlined in this document is recommended rather than AWS MGN.

• If you’re using Oracle ASM or Oracle ASM Filter Driver, refer to Can Application Migration Service replicate Oracle ASM? in the Application Migration Service whitepaper.

• If you are using Oracle ASM, note the EC2 volume limits by EC2 instance family at Linux-specific volume limits.