DCT appliance

DCT appliance — also referred to as virtual appliance — is a self-contained virtual machine deployment of Data Control Tower, distributed as a closed appliance image. It brings DCT closer to the familiar deployment model of standard Continuous Data and Compliance engines, no Kubernetes cluster or container orchestration required.

The appliance is available in multiple formats to suit your infrastructure: an OVA for VMware ESX and Oracle Cloud Infrastructure, a VHDX for Hyper-V, and marketplace offerings for Microsoft Azure and Amazon Web Services.

Once deployed, the appliance provides two interfaces: a setup UI for infrastructure-level configuration (network, TLS, storage, and engine registration) and the DCT application UI for managing accounts, roles, authentication, and connected Delphix resources. Both are accessible over HTTPS from a supported web browser.

Use the topics in this section to get your appliance up and running:

• Requirements and prerequisites: Minimum CPU, memory, and storage specifications, along with supported platforms and hypervisor versions. Review this before provisioning your VM.

• Installation and setup (OVA): Step-by-step instructions for deploying the OVA on VMware ESX or OCI, completing the first-boot Setup UI wizard, and accessing the DCT application UI.

• Hyper-V deployment: Requirements and recommended configuration for deploying the DCT appliance on Hyper-V, including vCPU, memory, storage, and Hyper-V-specific considerations.

• Backup and restore: How to take point-in-time backups of DCT application metadata and restore them — whether recovering from a failure, correcting a configuration error, or migrating to a new VM.

• Migrating from DCT on Kubernetes: If you're running DCT on Kubernetes today, this page walks you through provisioning a new appliance, backing up your existing instance, and restoring it onto the appliance so you can decommission Kubernetes.