Oracle Workloads and VMware Cloud on AWS: Deployment, Migration, and Configuration

posted in: AWS, Oracle | 0
Customers deploying Oracle Real Application Clusters (RAC) have requirements such as stringent SLAs, continued high performance, and application availability. It is a major challenge for business organizations to manage data storage in these environments due to these rigorous business requirement.

Common issues presented when using traditional storage solutions for business-critical application (BCA) include inadequate performance, scale-in/scale-out, storage inefficiency, complex management, and high deployment and operating costs.

With more and more production servers being virtualized, the demand for highly converged server-based storage is surging. VMware Virtual SAN aims at providing a highly scalable, available, reliable, and high-performance storage using cost-effective hardware, specifically direct-attached disks in VMware ESXi hosts. Virtual SAN adheres to a new policy-based storage management paradigm, which simplifies and automates complex management workflows that exist in traditional enterprise storage systems with respect to configuration and clustering.

Virtual SAN Stretched Cluster enables active/active data centers that are separated by metro distance. Extended Oracle RAC with Virtual SAN enables transparent workload sharing between two sites accessing a single database while providing the flexibility of migrating or balancing workloads between sites in anticipation of planned events such as hardware maintenance.

VMware Cloud on AWS is an on-demand service that enables customers to run applications across vSphere-based cloud environments with access to a broad range of AWS services. Powered by VMware Cloud Foundation, this service integrates vSphere, vSAN and NSX along with VMware vCenter management, and is optimized to run on dedicated, elastic, bare-metal AWS infrastructure. ESXi hosts in VMware Cloud on AWS reside in an AWS availability Zone (AZ) and are protected by vSphere HA.

The use case for deploying VMware Cloud on AWS are multi-fold namely

  • Data Center Extension & DR
  • Cloud Migration
  • Application modernization & Next-Generation Apps build out



A new feature called Stretched Clusters for VMware Cloud on AWS is designed to protect against an AWS availability zone failure. Now applications can span multiple AWS Availability Zones (AZ) within a VMware Cloud on AWS cluster.



One of the use cases is running Extended Oracle RAC on Stretched Clusters for VMware Cloud on AWS to provide greater availability and protect against AZ failures.

With the release of Virtual SAN Stretched Cluster followed by VMware Cloud for AWS and recently ,Stretched Clusters for VMware Cloud on AWS, applications e.g Oracle RAC which have stringent requirements such as very high SLA’s, continued high performance, and application availability can now take dual advantage of being deployed on the cloud along with having high availability across multiple AZ’s in the Stretched Clusters for VMware Cloud on AWS deployment model.

The paper Oracle Workloads and VMware Cloud on AWS: Deployment, Migration, and Configuration describes the deployment, migration options along with best practices when migrating Oracle Standalone and Oracle RAC on VMware on-premises (vSphere with traditional Storage or VMware HCI vSAN ) to Stretched Clusters for VMware Cloud on AWS using the approach below

  • Validate functionality of current on-premise RAC setup
  • Migrate DR RAC ‘prddg’ from on-premise Site B to Stretched Cluster for VMware Cloud on AWS
  • Take advantage of the Stretched Cluster for VMware Cloud on AWS using the multi-AZ functionality by
    • Adding new nodes to the migrated DR RAC ‘prddg’
    • Create new Oracle RAC ‘vmcrac’

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.