Storage Configuration Requirements for Oracle Exadata Database Service on Cloud@Customer
Review the storage requirements for the ASM disk groups and VM file systems to plan the best options for your enterprise needs.
If you are looking for information to plan the local VM storage available on your VM Clusters refer to Estimating How Much Local Storage You Can Provision to Your VMs
- About Storage Configuration for Oracle Exadata Database Service on Cloud@Customer
As part of configuring each Oracle Exadata Database Service on Cloud@Customer VM cluster, the storage space inside the Exadata Storage Servers is configured for use by Oracle Automatic Storage Management (ASM). - 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. - Allocation Proportions for DATA, RECO and SPARSE Disk Groups
Determine the storage allocation between theDATA
,RECO
, andSPARSE
disk groups for Oracle Exadata Storage Servers. - Virtual Machine File System Structure for Oracle Exadata Database Service on Cloud@Customer
About Storage Configuration for Oracle Exadata Database Service on Cloud@Customer
As part of configuring each Oracle Exadata Database Service on 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 theDATA
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 the 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 theDATA
andRECO
disk groups. If you do not select this option, then theSPARSE
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 theDATA
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% (TheSPARSE
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% (TheSPARSE
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%
Virtual Machine File System Structure for Oracle Exadata Database Service on Cloud@Customer
Exadata Cloud@Customer X8M systems use the following file system organization on the virtual machines. To plan for local storage allocation on the virtual machines please refer to Estimating How Much Local Storage You Can Provision to Your VMs.
Filesystem | Mounted On |
---|---|
devtmpfs |
/dev |
tmpfs |
/dev/shm |
tmpfs |
/run |
tmpfs |
/sys/fs/cgroup |
tmpfs
|
/run/user/0 |
/dev/mapper/VGExaDb-LVDbSys1 |
/ |
/dev/mapper/VGExaDb-LVDbOra1 |
/u01 |
/dev/mapper/VGExaDb-LVDbTmp |
/tmp |
/dev/mapper/VGExaDb-LVDbVar1 |
/var |
/dev/mapper/VGExaDb-LVDbVarLog |
/var/log |
/dev/mapper/VGExaDb-LVDbHome |
/home |
/dev/mapper/VGExaDbDisk.u02_extra.img-LVDBDisk |
/u02 |
/dev/mapper/VGExaDb-LVDbVarLogAudit
|
/var/log/audit |
/dev/sda1 |
/boot |
/dev/mapper/VGExaDbDisk.grid19.0.0.0.200414.img-LVDBDisk |
/u01/app/19.0.0.0/grid |
/dev/asm/acfsvol01-142 |
/acfs01 |