GCP requirements
Overview
This topic outlines the requirements for deploying the DCT appliance on Google Cloud Platform (GCP). The DCT appliance on GCP is deployed as a Compute Engine instance created from a public GCE Custom Image published by Delphix. For air-gapped environments, a manual image import path using a tar.gz file is also available. See GCP deployment for step-by-step instructions.
Machine types
Any general-purpose GCP machine type that meets the minimum requirements is acceptable. DCT is a lightweight control-plane application and does not require high-memory or storage-optimized instances.
|
Specification |
Minimum |
Recommended |
|---|---|---|
|
vCPU |
8 |
8 or more |
|
Memory |
16 GB |
32 GB (required with Delphix AI Services) |
|
Processor |
Intel or AMD (x86_64) |
Intel or AMD (x86_64) |
Recommended machine type families: N2-standard (for example, n2-standard-8 provides 8 vCPU and 32 GB) or N4-standard. Arm-based machine types (T2A) are not supported.
Network
DCT communicates with registered Continuous Data and Continuous Compliance engines exclusively over HTTPS. It does not use NFS, iSCSI, or DSP, and does not move bulk data between the appliance and the engines. This means DCT has significantly lower network bandwidth requirements than a Continuous Data engine.
-
VPC and subnet: Deploy the DCT instance in a VPC with connectivity to your registered Delphix engines. A static internal IP address is recommended for consistent access. Reserve a static external IP only if the DCT UI or API must be reachable from outside the VPC.
-
Firewall rules: Create or update firewall rules to allow:
-
Inbound TCP 443 from admin browsers and API clients to the DCT instance.
-
Outbound TCP 443 from the DCT instance to registered Delphix engines.
No additional database-specific ports are required for DCT itself.
-
-
gVNIC: Supported but not required. A standard VirtIO NIC is sufficient for DCT's control-plane traffic.
Storage
DCT requires two disks: a system disk and a metadata volume. Unlike Continuous Data, DCT does not require a DxFS storage pool or multiple data disks.
|
Disk |
Size |
Type |
Notes |
|---|---|---|---|
|
System disk |
128 GB |
SSD Persistent Disk |
Ships at 128 GB in the custom image. |
|
Metadata volume |
50 GB minimum |
SSD Persistent Disk |
Stores DCT application metadata. Standard Persistent Disk is acceptable but SSD is recommended for consistent I/O performance. |
No object storage (Cloud Storage bucket) is required for DCT operation. The GCS bucket used during image import (see GCP deployment) is only needed temporarily and can be deleted after the custom image is created.