Introduction to Oracle Exadata Cloud@Customer

Learn how you can leverage the combined capabilities of Oracle Exadata and Oracle Cloud Infrastructure with Oracle Exadata Cloud@Customer

Oracle Autonomous Database on Oracle Exadata Cloud@Customer combines the benefits of a self-driving, self-securing, and self-repairing database management system and the security and control offered by having it deployed securely on premise behind your firewall.

About Oracle Exadata Cloud@Customer

With Oracle Exadata Cloud@Customer, you can maintain absolute control over your data while leveraging the combined capabilities of Oracle Exadata and Oracle Cloud Infrastructure managed by Oracle.

Oracle Exadata Cloud@Customer enables you to apply the combined power of Oracle Exadata and Oracle Cloud Infrastructure inside your own data center. You have full access to the features and capabilities of Oracle Database along with the intelligent performance and scalability of Oracle Exadata, but with Oracle owning and managing the Exadata infrastructure. You can use the Oracle Cloud Infrastructure console and APIs to manage Oracle Exadata Cloud@Customer just as with any other cloud resource, while maintaining absolute sovereignty over your data.

Each Oracle Exadata Cloud@Customer system configuration contains compute nodes (database servers) and Oracle Exadata Storage Servers that are interconnected using a high-speed, low-latency InfiniBand network, and intelligent Oracle Exadata software. Each configuration is equipped with a fixed amount of memory, storage, and network resources.

Oracle Exadata Cloud@Customer uses virtual machine (VM) technology to separate the customer-managed and components managed by Oracle on each compute node. You have root privilege for the Oracle Exadata compute node VMs, so you can manage the Oracle Database, Oracle Grid Infrastructure, and Oracle Exadata system software. However, you do not have administrative access to the physical compute node hardware, which Oracle administers.

Oracle Exadata Cloud@Customer uses Oracle Exadata Storage Servers for database storage. The storage is allocated to disk groups managed by Oracle Automatic Storage Management (Oracle ASM). You have full administrative access to the Oracle ASM disk groups, but Oracle administers the Oracle Exadata Storage Server hardware and software.

In addition to the compute node hardware and Oracle Exadata Storage Servers, Oracle also manages other Oracle Exadata Cloud@Customer infrastructure components, including the network switches, power distribution units (PDUs), and integrated lights-out management (ILOM) interfaces.

Subscription to Oracle Exadata Cloud@Customer can include all of the required Oracle Database software licenses, or you can choose to bring Oracle Database software licenses that you already own to Oracle Exadata Cloud@Customer. If you choose to include Oracle Database software licenses in your Oracle Exadata Cloud@Customer subscription, then the included licenses contain all of the features of Oracle Database Enterprise Edition, plus all of the database enterprise management packs, and all of the Enterprise Edition options, such as Oracle Database In-Memory and Oracle Real Application Clusters (Oracle RAC). Exadata Cloud@Customer also comes with cloud-specific software tools that assist with administration tasks, such as backup, recovery, and patching.

On each Oracle Exadata Cloud@Customer system, you can create one or more databases. Apart from the inherent storage and processing capacity of your Oracle Exadata system, there is no set maximum for the number of databases that you can create.

Per-Second Billing for OCPU Usage

Exadata Cloud@Customer Gen2 uses per-second billing for OCPUs. This means that OCPU usage is billed by the second, with a minimum usage period of 1 minute.

Per-Second Billing for Autonomous Database OCPU Usage

Exadata Cloud@Customer Gen2 uses per-second billing for OCPUs. This means that OCPU usage is billed by the second, with a minimum usage period of 1 minute.

System Configuration Options for Oracle Exadata Cloud@Customer

To meet the needs of your enterprise, you can select from one of four Oracle Exadata X8M-2 systems, Oracle Exadata X8-2 systems, or Oracle Exadata X7-2 systems.

Exadata Cloud@Customer is offered in the following system configurations:

  • Base System: Contains two compute nodes and three Oracle Exadata Storage Servers. A Base System is an entry-level configuration. Compared to other configurations, a Base System contains Oracle Exadata Storage Servers with significantly less storage capacity, and compute nodes with significantly less memory and processing power.
  • Quarter Rack: Contains two compute nodes and three Oracle Exadata Storage Servers.
  • Half Rack: Contains four compute nodes and six Oracle Exadata Storage Servers.
  • Full Rack: Contains eight compute nodes and 12 Oracle Exadata Storage Servers.

Each system configuration is equipped with a fixed amount of memory, storage, and network resources. All system configurations are based on Oracle Exadata X8M-2, X8-2, or X7-2 systems.

Oracle Exadata Cloud@Customer X8M-2 System Specifications

Review the technical specifications for each system configuration option for Oracle Exadata Cloud@Customer.

Tip:

X8M-2 support is available only in the ashburn-1, ap-hyderabad-1, eu-frankfurt-1, ca-toronto-1, sa-saopaulo-1, and ap-tokyo-1 regions.

Table 1-1 Oracle Exadata Cloud@Customer X8M-2 System Specifications

Property Base Rack Quarter Rack Half Rack Full Rack
Number of Compute Nodes 2 2 4 8
Total Maximum Number of Enabled CPU Cores 48 100 200 400
Total RAM Capacity 656 GB 2780 GB 5560 GB 11120 GB
Persistent Memory 0 4.6 TB 9.2 TB 18.4 TB
Number of Exadata Storage Servers 3 3 6 12
Total Raw Flash Storage Capacity 38.4 TB 76.8 TB 153.6 TB 307.2 TB
Total Usable Storage Capacity** 74 TB 149 TB 299 TB 598 TB
Max number of VMs 4 8 8 8

** TB=1024^4

Oracle Exadata Cloud@Customer X8-2 System Specifications

Review the technical specifications for each system configuration option for Oracle Exadata Cloud@Customer.

Table 1-2 Oracle Exadata Cloud@Customer X8-2 System Specifications

Property Base System Quarter Rack Half Rack Full Rack
Number of Compute Nodes 2 2 4 8
Total Maximum Number of Enabled CPU Cores 48 100 200 400
Total RAM Capacity 720 GB 1440 GB 2880 GB 5760 GB
Number of Exadata Storage Servers 3 3 6 12
Total Raw Flash Storage Capacity 38.4 TB 76.8 TB 153.6 TB 307.2 TB
Total Raw Disk Storage Capacity 252 TB 504 TB 1008 TB 2016 TB
Total Usable Storage Capacity 74.8 TB 149.7 TB 299.4 TB 598.7 TB
Maximum Number of VMs 5 5 5 5

Oracle Exadata Cloud@Customer X7-2 System Specifications

Review the technical specifications for each system configuration option for Oracle Exadata Cloud@Customer.

Table 1-3 Oracle Exadata Cloud@Customer X7-2 System Specifications

Property Base System Quarter Rack Half Rack Full Rack
Number of Compute Nodes 2 2 4 8
Total Maximum Number of Enabled CPU Cores 44 92 184 368
Total RAM Capacity 480 GB 1440 GB 2880 GB 5760 GB
Number of Exadata Storage Servers 3 3 6 12
Total Raw Flash Storage Capacity 19.2 TB 76.8 TB 153.6 TB 307.2 TB
Total Raw Disk Storage Capacity 144 TB 360 TB 720 TB 1440 TB
Total Usable Storage Capacity 42.7 TB 106.9 TB 213.8 TB 427.6 TB
Maximum Number of VMs 6 6 6 6

Plan Your Configuration Settings on Storage

The proportions that you select for your DATA, RECO, and SPARSE disk groups profoundly affect your storage space. Review the best options for your enterprise needs.

About Storage Configuration for Oracle Exadata Cloud@Customer

As part of configuring each Exadata Cloud@Customer VM cluster, the storage space inside the Exadata Storage Servers is configured for use by Oracle Automatic Storage Management (ASM).

By default, the following ASM disk groups are created:

  • The DATA disk group is primarily intended for the storage of Oracle Database data files. Also, a small amount of space is allocated from the DATA disk group to support the shared file systems that are used to store software binaries (and patches) and files associated with the cloud-specific tooling. You should not store your own data, including Oracle Database data files, backups, trace files, and so on, inside the system-related ACFS file systems.
  • The RECO disk group is primarily used for storing the Fast Recovery Area (FRA), which can be used to provide a local store for files related to backup and recovery. By default, the FRA is used to store archived redo log files and the backup control file. If you configure your VM cluster with the option to allocate storage for local backups, then you can use the FRA as a database backup destination. Finally, if you enable flashback features on a database, then the FRA is used to store the flashback logs.

In addition, you can choose to create the SPARSE disk group. The SPARSE disk group is required to support Exadata snapshot functionality. Exadata snapshots enable space-efficient clones of Oracle databases that can be created and destroyed very quickly and easily. Snapshot clones are often used for development, testing, or other purposes that require a transient database. For more information about Exadata snapshot functionality, see "Setting Up Oracle Exadata Storage Snapshots" in Oracle Exadata System Software User's Guide.

Allocation of Storage Space Options on Oracle Exadata Storage Servers

Select the storage option that best meets your planned use case on your Oracle Exadata Storage Servers.

As an input to the virtual machine (VM) cluster creation process, you must choose options that determine how storage space in the Oracle Exadata Storage Servers is allocated to the Oracle ASM disk groups. Your choices profoundly affect how storage space in the Exadata Storage Servers is allocated to the ASM disk groups. Consider which option best meets your needs:

  • Allocate Storage for Exadata Snapshots

    If you select this option, then the SPARSE disk group is created, and less space is allocated to the DATA and RECO disk groups. If you do not select this option, then the SPARSE disk group is not created, and you cannot use Exadata snapshot functionality.

  • Allocate Storage for Local Backups

    If you select this option, then more space is allocated to the RECO disk group to accommodate local backups to Oracle Exadata storage. If you do not select this option, then more space is allocated to the DATA disk group, but you cannot use local Oracle Exadata storage as a backup destination for any databases in the VM cluster.

Allocation Proportions for DATA, RECO and SPARSE Disk Groups

Determine the storage allocation between the DATA, RECO, and SPARSE disk groups for Oracle Exadata Storage Servers.

Exadata Storage Server Configuration Allocation With No Exadata Snapshot Storage or Local Backup

When you select Allocate Storage for Exadata Snapshots: No and Enable Backups on Local Exadata Storage: No, then storage allocation is as follows:

  • DATA Disk Group: 80%
  • RECO Disk Group: 20%
  • SPARSE Disk Group 0% (The SPARSE disk group is not created.)

Exadata Storage Server Configuration Allocation With No Exadata Snapshot Storage and Local Backup Enabled

When you select Allocate Storage for Exadata Snapshots: No and Enable Backups on Local Exadata Storage: Yes, so that backups are enabled on local storage, then storage allocation is as follows:

  • DATA Disk Group: 40%
  • RECO Disk Group: 60%
  • SPARSE Disk Group 0% (The SPARSE disk group is not created.)

Exadata Storage Server Configuration Allocation With Exadata Snapshot Storage and No Local Backup

When you select Allocate Storage for Exadata Snapshots: Yes and Enable Backups on Local Exadata Storage: No, so that storage is allocated for Exadata snapshots, then storage allocation is as follows:

  • DATA Disk Group: 60%
  • RECO Disk Group: 20%
  • SPARSE Disk Group 20%

Exadata Storage Server Configuration Allocation With Both Exadata Snapshot Storage and Local Backup Enabled

When you select Allocate Storage for Exadata Snapshots: Yes and Enable Backups on Local Exadata Storage: Yes, so that storage is allocated for Exadata snapshots, and storage is allocated for local backups, then storage allocation is as follows:

  • DATA Disk Group: 35%
  • RECO Disk Group: 50%
  • SPARSE Disk Group 15%

Moving to Oracle Cloud Using Zero Downtime Migration

Oracle now offers the Zero Downtime Migration service, a quick and easy way to move on-premises databases and Oracle Cloud Infrastructure Classic databases to Oracle Cloud Infrastructure. You can migrate databases to the following types of Oracle Cloud Infrastructure systems: Exadata, Exadata Cloud@Customer, bare metal, and virtual machine.

Zero Downtime Migration leverages Oracle Active Data Guard to create a standby instance of your database in an Oracle Cloud Infrastructure system. You switch over only when you are ready, and your source database remains available as a standby. Use the Zero Downtime Migration service to migrate databases individually or at the fleet level. See Move to Oracle Cloud Using Zero Downtime Migration for more information.