Yugabyte operations in DCT

This guide is for Delphix administrators and operators who perform YugabyteDB setup and provisioning tasks in DCT.

Perform YugabyteDB data operations using Delphix Data Control Tower (DCT) in conjunction with the Delphix Continuous Data (CD) Engine. The topics in this section walk through DCT-specific workflows to add YugabyteDB environments, upload the YugabyteDB connector toolkit, link YugabyteDB dSources using a supported ingestion method, and provision YugabyteDB virtual databases (VDBs).

Prerequisites

• Access to DCT with appropriate administrative permissions

• A running Delphix Continuous Data Engine

• Network connectivity between DCT, the engine, and YugabyteDB hosts

• Valid YugabyteDB OS and database credentials

• YugabyteDB connector JSON file available for upload

Key components

• Continuous Data Engine

  Executes YugabyteDB discovery, ingestion, and snapshot operations. For more information, read Connect a Continuous Data Engine in DCT.

• YugabyteDB connector

  A JSON-based connector that enables the engine to detect YugabyteDB installations on registered hosts. For more information, read Upload the Connector.json in DCT.

• Infrastructure connections (environments)

  Registered YugabyteDB hosts that DCT communicates with over SSH. For more information, read Add a YugabyteDB environment in DCT.

• Source configurations

  Logical definitions that identify which YugabyteDB instance can be ingested as a dSource. For more information, read Create a source configuration for Connectors in DCT.

• dSources

  Managed representations of YugabyteDB databases used to take snapshots, create bookmarks, link dSources, and provision VDBs.

• VDBs

  Manage a VDB which is provisioned from a dSource or a VDB snapshot.

Supported ingestion methods

The YugabyteDB connector supports two ingestion approaches:

Ingestion type	Description
Staging Pull	Delphix orchestrates data ingestion by working with Yugabyte Anywhere (YBA) to restore a YugabyteDB backup into the staging environment. Supports full backup restore from AWS S3, NFS, or Azure Blob Storage locations. Recommended for most deployments.
Staging Push	You design and execute the ingestion workflow, manually transferring and preparing YugabyteDB data in the staging environment. Use when your backup or infrastructure requirements do not fit the Staging Pull model.

Limitations

• V2P (Virtualize to Physical) is not supported.

• Point-in-time recovery is not supported. Provision, refresh, and rewind operations are snapshot-based only.

• Yugabyte Anywhere (YBA) does not support assigning Masters on dedicated nodes.

• Yugabyte Anywhere will not allow provisioning of a single VDB filesystem into a pre-existing YugabyteDB cluster. DCT must create a new YugabyteDB instance for each VDB, with its own unique HTTP port.

• If the YugabyteDB version on a staging or target host is changed, the staging database and VDB must be recreated.

DCT Workflow

Follow this sequence to complete the DCT workflow for the YugabyteDB connector in DCT: