This topic describes how to customize the initial system setup requirements for memory, number of CPUs, storage disks, and network configuration.

The OVA file that you use to install the Delphix Engine is configured for the minimum system requirements. You can customize these to match the capabilities of your specific system.

Prerequisites

  • Follow the initial installation instructions for Installing the Delphix Engine.

Procedure

  1. Shut down the guest operating system and power off the Delphix Engine.
  2. Under Getting Started, select Edit Virtual Machine Settings.
  3. You can now customize the system settings.
SettingOptions
Memory Size  Set to 64GB or larger based on sizing analysis. In the Resource Allocation panel, ensure that Reserve all guest memory is checked.
To adjust the resource allocation of a VM without rebooting it  Delphix supports hotplugging CPUs and memory to ZFS. NoteThis is only available on ESX. For more information, refer to Enabling Hot-adding.
Number of CPUs  Allocate 8 vCPUs or more based on your Delphix licensing. vCPUs should be fully reserved to ensure that the Delphix Engine does not compete for CPU cycles on an overcommitted host.
Supported Controllers

Delphix supports Paravirtual SCSI (PVSCSI) controllers or LSI Parallel controllers. A mix of different types of SCSI controllers is not supported within the engine.

It is recommended to use PVSCSI controllers by default. Although PVSCSI supports high throughput with minimal processing cost, the performance improvements on Delphix Engine may vary from case to case. 

Disks for Data Storage  Add virtual disks to provide storage for user data such as dSources and VDBs. The underlying storage must be redundant. Add a minimum of 150GB per storage disk. All virtual disks should be the same size and have the same performance characteristics. If using VMFS, use thick provisioned, lazy zeroed disks. To alleviate IO bottlenecks at the virtual controller layer, spread the virtual disks across all 4 virtual SCSI controllers.
Data Storage Multipathing Policy

For EMC storage, the multipathing policy should always be set to round-robin (default for 5.X). Additionally, change the IO Operation Limit from the default of 1000 to 1. This should be strongly considered for other storage platforms as well.

See VMware KB article EMC VMAX and DMX Symmetrix Storage Array Recommendations for Optimal Performance on VMware ESXi/ESX.

NetworkThe network configuration is set to have a VMXNET3 network adapter. VMXNET3 is a tuned network interface that is included with the VMtools provided in the OVA file.
It will be assigned to 
VM Network.

JUMBO Frames
VMXNET3 supports Ethernet jumbo frames, and you can use this to maximize throughput and minimize CPU utilization. 

Adding Link Aggregation via VMware NIC Teaming   
To increase throughput or for failover, add multiple physical NICs to the vSwitch that is connected to the Delphix Engine. To increase throughput, NIC Teaming must use the Route Based on IP Hash protocol for load balancing. 

Dedicate Physical NICs to the Delphix Engine
For best performance, assign the Delphix Engine to network adapters that are used exclusively by Delphix. 

Enabling Hot-adding

To manually enable hot-adding, in the VCenter console, do the following steps.

  1. Select the Delphix Engine.
  2. Right-click on the engine and select Edit Settings.
  3. Edit settings:
    1. To enable CPU hotadd, under the CPU section, tick the CPU Hot Plug checkbox.
    2. To enable memory hotadd, under the Memory section, tick the Memory Hot Plug checkbox.
  4. Modify the appropriate setting to the new value; note that only expansion of CPU and memory is supported, and attempts to reduce the values available to the Delphix Engine will fail.
  5. Click Ok to confirm your changes.

Currently, the UI does not update with the new memory and CPU information; verifying that the new resources are in use requires connecting to the OS shell.

For customers migrating from versions before 6.0, an extra step is required to enable CPU/memory hotplug.

  1. After migrating, turn off the VM.
  2. Open VM Settings.
  3. Select VM Options.
  4. Under General, update the guest OS to Ubuntu (64-bit).
  5. Under Advanced, select Edit Configuration.
  6. Set disk.EnableUUID to TRUE.
  7. Follow normal hotplug enable steps.

For customers that are upgrading their existing engines from versions below 6.0.6.0, two vSphere properties need to be enabled manually after the upgrade from vSphere in order to use this feature. The properties are cputHotAddEnabled and memoryHotAddEnabled.

For migrations from Illumos to Linux, the guest OS and version in vSphere also needs to be updated to Ubuntu, in addition to the above two properties. Without this, it has been noticed that hot-adding memory is not allowed from vSphere, even if memoryHotAddEnabled is enabled.

Post-Requisites

Related Topics