This topic covers the virtual machine requirements, including memory and data storage, for the deployment of the Delphix Engine on Amazon EC2 (Elastic Cloud Compute).
This section covers the following topics:
- Instance Types
- Network Configuration
- EBS Configuration
- General Storage Configuration
- Additional AWS Configuration Notes
Once you understand the requirements listed on this page, you should view the next pages on AWS EC2 deployment:
The following is a list of instance types that are supported to deploy Delphix on AWS EC2. Delphix periodically certifies new instance types, which will be added to the list here.
Large Memory Instances (Preferred):
It is recommended to enable Enhanced Networking to maximize performance, for more information view Enhanced Networking on Linux.
Virtual Private Cloud
You must deploy the Delphix Engine and all of the source and target environments in a VPC network to ensure that private IP addresses are static and do not change when you restart instances.
When adding environments to the Delphix Engine, you must use the host's VPC (static private) IP addresses.
Static Public IP
The EC2 Delphix instance must be launched with a static IP address; however, the default behavior for VPC instances is to launch with a dynamic public IP address – which can change whenever you restart the instance. If you're using a public IP address for your Delphix Engine, static IP addresses can only be achieved by using assigned AWS Elastic IP Addresses.
Security Group Configuration
The default security group will only open port 22 for SSH access. You must modify the security group to allow access to all of the networking ports used by the Delphix Engine and the various source and target engines.
See Network Performance Configuration Options for information about network performance tuning.
See General Network and Connectivity Requirements for information about specific port configurations.
Deploying Delphix on AWS EC2 requires EBS provisioned IOPS volumes. Since EBS volumes are connected to EC2 instances via the network, other network activity on the instance can affect throughput to EBS volumes. EBS optimized instances provide guaranteed throughput to EBS volumes and are required to provide consistent and predictable storage performance.
EBS Provisioned IOPS Volumes
Note: All attached storage devices must be EBS volumes
Delphix does not support the use of instance store volumes.
Use EBS volumes with provisioned IOPs in order to provide consistent and predictable performance. The number of provisioned IOPs depends on the estimated IO workload on the Delphix Engine.
Provisioned IOPs volumes must be configured with a volume size of at least 30 GiB times the number of provisioned IOPs. For example, for a provisioned volume of 3000 IOPs, you would need at least 100 GiB since the volume required is at least thirty times the provisioned IOPs.
General Storage Configuration
Delphix recommends using a total of four 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 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.
|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.
Additional AWS Configuration Notes
- Using storage other than EBS is not supported.
- Limits on the number of volumes are dictated by the EBS instance type, and is generally advised that over 40 can be expected to cause issue on Linux VMs. More information can be found in the AWS Volume Limits and AWS Volume Constraints articles. The maximum device limit imposed by AWS can be handled by the Delphix Engine.
- The use of the local SSDs attached to i2 instance types is not supported.
- Cold HDD (sc1) volumes (not supported due to poor performance)
- Using fast storage for EBS volumes is supported and recommended, including (in order of decreasing speed):
- Provisioned IOPs (io1) volumes (recommended)
- General Purpose SSD (gp2) volumes (supported)
- Throughput Optimized HDD (st1) volumes (supported)
- Magnetic (standard) volumes (supported, but use st1 instead where possible)
- Use of EBS volumes encrypted at creation is supported (during initial deployment from AMI, as well as storage devices added post-deployment), but can have negative performance consequences. Conversion of existing EBS volumes is possible in AWS but is not supported in Delphix at this time.