Oracle Cloud Infrastructure Documentation

Exadata Cloud at Customer

Exadata Cloud at Customer enables you to apply the combined power of 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 Exadata, but with Oracle owning and managing the Exadata infrastructure. You can use the Oracle Cloud Infrastructure console and APIs to manage Exadata Cloud at Customer like any other cloud resource, while maintaining absolute sovereignty over your data.

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

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

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

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

Subscription to Exadata Cloud at 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 Exadata Cloud at Customer. If you choose to include Oracle Database software licenses in your Exadata Cloud at 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 (RAC). Exadata Cloud at Customer also comes with cloud-specific software tools that assist with administration tasks, such as backup, recovery, and patching.

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

System Configuration

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

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

Each system configuration is equipped with a fixed amount of memory, storage, and network resources, and all system configurations are based on Oracle Exadata X8 systems.

The following table outlines the technical specifications for each Exadata Cloud at Customer system configuration.

Exadata Cloud at Customer X8 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

Storage Configuration

 

As part of configuring each Exadata Cloud at 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 optionally 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.

Impact of Configuration Settings on Storage

As an input to the VM cluster creation process, you must choose options that determine how storage space in the Exadata Storage Servers is allocated to the ASM disk groups:

  • Allocate Storage for Exadata Snapshots: If you select this option, 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, more space is allocated to the RECO disk group to accommodate local backups to Exadata storage. If you do not select this option, more space is allocated to the DATA disk group but you cannot use local Exadata storage as a backup destination for any databases in the VM cluster.

Your choices profoundly affect how storage space in the Exadata Storage Servers is allocated to the ASM disk groups. The following table outlines the proportional allocation of storage among the DATA, RECO, and SPARSE disk groups for each possible configuration:

Configuration Settings DATA Disk Group RECO Disk Group SPARSE Disk Group

Allocate Storage for Exadata Snapshots: No

Enable Backups on Local Exadata Storage: No

80% 20%

0%

The SPARSE disk group is not created.

Allocate Storage for Exadata Snapshots: No

Enable Backups on Local Exadata Storage: Yes

40% 60%

0%

The SPARSE disk group is not created.

Allocate Storage for Exadata Snapshots: Yes

Enable Backups on Local Exadata Storage: No

60% 20% 20%

Allocate Storage for Exadata Snapshots: Yes

Enable Backups on Local Exadata Storage: Yes

35% 50% 15%