Overview
This article outlines the virtual machine requirements, including memory and data storage, for deploying the Delphix Engine on Oracle Cloud Infrastructure (OCI). Once the requirements listed on this page are reviewed, refer to the next articles on OCI deployment:
Delphix disk storage capabilities remain seamlessly operable. There are no additional limitations to your storage, unless otherwise imposed by the [respective] Hypervisor or Cloud environment.
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.
Requirements | Notes |
|---|
Compute shapes The minimum requirements are listed below: Recommended compute shapes: | 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. For more information on OCI shapes, refer to OCI shapes.
|
Network configuration
Requirements | Notes |
|---|
Virtual cloud network (VCN) | The Delphix Engine and all of the source and target environments must be deployed in a VCN to ensure that private IP addresses are static and do not change when restarting instances. By default, OCI subnets are considered public. When defining a subnet, it is recommended to set it as private. Unless required by the environment, the VCN should not include a Public Subnet. When adding environments to the Delphix Engine, 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 the engine with a Public IP address; however, it could be passable to use a dynamic Public IP address in addition to a static Private IP address if the environment requires such access.
|
Security rules configuration | OCI allows two firewall features: Network Security Groups (NSGs) and Security Lists. Oracle recommends the use of NSGs over Security Lists because NSGs let the VCN subnet architecture be separate from the application security requirements. More information can be found in this Oracle documentation A VCN will use a Security List to define default rules. By default, the security list will only open port 22 for SSH access. The Security List must be modified, or new NSGs created, to allow access to all of the networking ports used by the Delphix Engine and the various source and target engines. This dual implementation of firewall or security rules may be different from other clouds, please see OCI documentation for best practices. See Network performance configuration options for information about network performance tuning. See General network and connectivity requirements for information about specific port configurations.
|
General storage configuration
Requirements | Notes |
|---|
General storage configuration | Delphix recommends using storage disks that in sum, have enough storage and IOPS/throughput for your data and performance requirements. Planning ahead for the use of multiple storage disks for the Delphix File System (DxFS) is recommended as it will facilitate growing and shrinking DxFS more easily in the future should your storage needs change. If using multiple storage disks for DxFS, Delphix recommends using equally sized storage disks. Please consult your cloud provider’s storage best practices for additional recommendations. 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. Must use Block Volume for data storage. Block Volumes must be attached using Paravirtualized mode. When adding additional disks to the block storage pool, storage device initialization will not occur since it is not required on this cloud.
|
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. For Delphix Continuous Cloud Engines backed by object storage, read the section Delphix Elastic Data Engines (Engines backed by object storage) in Initial Setup.
|
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 existing storage volumes must be expanded, 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, 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.
