Test Case Overview
Test Case Steps
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Test Case Summary

A standalone VM, Oracle122-OEL74, was also created and migrated from on premises to VMware Cloud on AWS and back.

This VM was not part of the solution setup but was used merely to demonstrate the migration capability between on-premises data centers and VMware Cloud on AWS for non-RAC Oracle workloads.

For VMware Cloud on AWS, the VDS vmc-dvs has 2 distributed switch port groups that were created for Oracle VM traffic between on-premises data centers and VMware Cloud on AWS:

  • Port group BCA-L2VPN for L2VPN for VM user traffic
    • Enables VMs to keep the same subnet when migrating from on-premises data centers to the cloud and back
  • Port group BCA-VPN-Network for VPN for VM traffic
    • Enables VMs to communicate—or ping each other—without being on the same subnet

L2VPN was used to extend the on-premises data center on site A running VMware SDDC to VMware Cloud on AWS to rapidly and easily migrate application workloads from on-premises data centers to the VMware Cloud on AWS and back.

It thereby requires

  • No VM conversions
  • No application refactoring and therefore no application downtime
  • No networking changes with L2VPN capability between an on-premises SDDC and VMware Cloud on AWS
     

Test Case Overview

A standalone VM, Oracle122-OEL74, was created with the following:

  • 8  vCPUs and 32GB memory
  • Oracle Enterprise Linux 7.4 OS
  • Oracle 12.2.0.1.0 Grid Infrastructure and RDBMS binaries installed on the VM
  • Oracle SGA set to 16GB and PGA set to 4GB for the database instance
  • Oracle ASM and Oracle ASMLib
  • All ASM disk groups disks presented on different PVSCSI controllers for performance and queue depth purposes
  • All database-related VMDKs partitioned using Linux utilities with proper alignment offset and labeled with Oracle ASMLib
  • Oracle ASM disk groups DATA_DG, FRA_DG, and REDO_DG created with external redundancy

 

All best practices for Oracle workloads on VMware SDDC were followed in accordance with the Oracle Databases on VMware Best Practices Guide here.

 

Standalone Oracle VM Oracle122-OEL74 details:

 

 

 

Test Case Steps

1. Log in to the Web Client to the VMware Cloud on AWS virtual center.

 

2. Right-clickVM Oracle122-OEL74.Click Migrate.

 

3.Select the Compute and Storage migration method.

 

4. Select the Oracle-RP compute resource pool.

 

5. Select the WorkloadDatastore datastore for storage.

 

6. Select the appropriate Destination Folder for the VM.

 

7. Select the BCA-L2VPN as the DestinationNetwork port group.

 

8. Select the appropriate vSphere vMotion priority.

 

9. Review the migration. Click Finish when ready.


10. The migration from on-premises data center to VMware Cloud on AWS has started.

 

 

11. The VM is now in the VMware Cloud on AWS.

 

12. Follow the same steps when migrating back to an on-premises data center from VMware Cloud on AWS.

 

Test Case Summary

A single-instance VM, Oracle122-OEL74, was successfully migrated from on-premises data centerto VMware Cloud on AWS.

L2VPN was used to extend the on-premises data center on site A running a VMware SDDC to VMware Cloud on AWS, to rapidly and easily migrate application workloads from on-premises data centerto the VMware Cloud on AWS and back.

This requires

  • No VM conversions
  • No application refactoring and therefore no application downtime
  • No networking changes with L2VPN capability between on-premises SDDC and VMware Cloud on AWS

The demo of the Migrating Oracle standalone database from on-premises data centerto VMware Cloud to AWS and back can be found here.

 

 

check-circle-line exclamation-circle-line close-line
Scroll to top icon