Deployment for OCI
Deployment / Deployment for OCI

This topic covers the virtual machine requirements, including memory and data storage, for deploying the Delphix DataOps Platform, colloquially known as a Delphix Engine, on Oracle Cloud Infrastructure (OCI).

This section covers the following topics:

  • Image Types
  • Shapes
  • Network Configuration
  • Storage Configuration
  • Additional OCI Configuration Notes

Once you understand the requirements listed on this page, you should view the next pages on OCI deployment:

Compute Image Types 

Delphix distributes product images, for OCI, using the QCOW2 image type. Compute Images must be imported into OCI using the Paravirtualized launch mode; currently, images using the Emulated launch mode are not supported.

Supported Shapes

The following is a list of shapes that are supported to deploy Delphix on OCI.

RequirementsNotes

Large Memory Instances (preferred)

  • VM.Standard2
  • VM.Standard.E4.Flex  
  • The Delphix Engine most closely resembles a storage appliance and performs best when provisioned using a storage-optimized shape.
  • Larger shapes provide more CPU, which can prevent resource shortfalls under high I/O throughput conditions.
  • Larger shapes also provide more memory, which the Delphix Engine uses to cache database blocks. More memory will provide better read performance.
  • Recommended minimum size of 8 vCPU and 64G memory.

Network Configuration

RequirementsNotes
Virtual Cloud Network (VCN)
  • You must deploy the Delphix Engine and all of the source and target environments in a VCN to ensure that private IP addresses are static and do not change when you restart instances.
  • By default, OCI subnets are considered public. When defining a subnet, we encourage configuring it as private. Unless required by your environment, your VCN should not include a Public Subnet.
  • When adding environments to the Delphix Engine, you must use the host's VCN (static private) IP addresses.
Static Private IP
  • The Delphix instance should be launched with a static private IP address. For security reasons, it is encouraged to avoid configuring your engine with a Public IP address; but, in some cases, it may be ok to use a dynamic Public IP address in addition to a static Private IP address if your environment requires such access. 
Security Rules Configuration

General Storage Configuration

We recommend using a minimum of four (4) disks to run your Delphix Engine. One disk is used for the Delphix File System (DxFS) to ensure that its file systems are always consistent on disk without additional serialization. The other three, or more, equally sized disks will be used for data storage. This also enables the Delphix Engine to achieve higher I/O rates by queueing more I/O operations to its storage.

RequirementsNotes

General Storage Configuration

  • Allocate initial storage equal to the size of the physical source database storage. For high redo rates and/or high DB change rates, allocate an additional 10-20 %.
  • Add storage when storage capacity approaches 30% free.
  • Attach a minimum of three (3), equally sized, storage devices to the Delphix Engine. This enables the Delphix File System (DxFS) to make sure that its file systems are always consistent on disk without additional serialization. This also enables the Delphix Engine to achieve higher I/O rates by queueing more I/O operations to its storage.
  • Must use Block Volume for data storage.
  • Block Volumes must be attached using Paravirtualized mode.
OCI Storage Configuration
  • Currently supported Shapes only support Block Volumes; File Storage is not supported.
  • Paravirtualized block devices are required; currently, iSCSI devices are not supported.
  • Elastic Performance Configuration Options (aka Volume Performance Policy): use Higher Performance.

Additional OCI Configuration Notes

  • When running low on storage space, Delphix recommends adding additional equivalently sized block storage volumes, or devices, instead of resizing existing volumes.
  •  If you must expand existing storage volumes, then this must be done using the “online” resizing strategy specified in OCI documentation; “offline” storage resizing is not supported and may lead to unexpected downtime. If an existing storage volume is expanded, then use the Setup, or sysadmin, interface to expand each storage “device,” or volume. The additional storage, as a result of a resize, will not be available for use until the storage devices are explicitly instructed to make use of the additional space.
  •  If expanding storage volumes, it is recommended that all volumes are expanded to the same size. When storage volumes, or devices, are the same size the Delphix product is able to balance I/O distribution among the disks for optimal performance.
  • Hot removal of storage volumes is not supported.

Related Topics