Once a dSource snapshot is available, you can provision a YugabyteDB virtual database (VDB) from that snapshot. The connector provisions and manages each VDB directly on the target host without Yugabyte Anywhere.

Each VDB runs as its own YugabyteDB cluster. Ensure that its ports do not conflict with other YugabyteDB instances on the target host. VDB provisioning is snapshot-based; point-in-time recovery is not supported.

Procedure

  1. Log in to DCT.

  2. Go to Data> Data Management >VDBs.

  3. Click the Actions button in the top-right corner and select Provision VDB from the drop down menu.

  4. On the Source page, select the dSource from which you want to provision the VDB (for example, yugabyte-dsource). The right panel displays the source details, including Name, AppData Connector Version, Engine, Group, Timezone, Repository, and Environment.

  5. Click Next.

  6. On the Provision Point page, select the snapshot from which to provision the VDB. The timeline displays available snapshots grouped by date. Select the desired snapshot and click Next.

  7. On the Target Environment page, enter the following details:

    • VDB Name: A name for the VDB (for example, VDB-YugabyteDB).

    • NFS Mount Location: The mount location on the target host. No spaces allowed (for example, /mnt/VDBPG).

    • (Optional) Click + Add to configure VDB with Snapshots only.

    • (Optional) Click + Add to add custom database-level config settings.

    • Enter a tag key and value and click + Tag to add tags.

  8. Click Next.

  9. On the Target Configuration page, select the environment where the VDB will be provisioned (for example, YugabyteDB Target Env). Then configure the following:

    • User: Select the OS user (for example, yugabyte_admin).

    • Instance: Select the YugabyteDB instance (for example, yugabytedb_vFiles (2025.1.0)).

    • NFS Mount Path: Enter the mount path on the target host.

    • (Optional) Enable Authentication on Cluster: Check this box if the VDB cluster requires authentication.

      • Database Password: When authentication is enabled, enter the VDB cluster password. The field is prefilled with a default value; change it for your environment.

    • IP Address / Hostname of the Primary Node: Enter the IP address or fully qualified hostname of the primary node. If TLS is enabled, the node certificate file name and certificate must match this value.

    • Additional Nodes: Use this section to define additional nodes for the VDB cluster.

      • Environment: Select the environment where the additional node is hosted.

      • Environment User: Specify the OS-level user that Delphix should use to connect to the additional node.

      • IP Address / Hostname of Additional Node: Enter the IP address or fully qualified domain name of the additional node.

    • Server Tuning Parameters: Apply advanced configuration settings to optimize performance and resource usage for specific node types.

      • Parameter Name: Define advanced configuration parameters that should be written into the YugabyteDB configuration file.

      • Parameter Value: Define advanced configuration parameters that should be written into the YugabyteDB configuration file.

      • Server Type: Select the server type to which the tuning parameter applies. Example values: Master, TServer. Use the Add button to define multiple server tuning entries for various parameters and server types.

    • Port List: This section configures the bind ports for communication between YugabyteDB services.

      • RPC Bind Port for TServer: 9100 (By default)

      • RPC Bind Port for Master: 7100 (By default)

      • Web UI Port for Master: 7000 (default)

      • PGSQL Proxy Bind Port for TServer: 5433 (By default)

      • CSQL Proxy Bind Port for TServer: 9042 (By default)

    • TLS Management Mode: Select Disabled, Customer Self-Signed, or CA-Signed. YBA Self-Signed (Auto) is not available for VDBs.

    • Node Certificates Directory: Enter the absolute path on each VDB host to the directory containing ca.crt, node.<address>.crt, and node.<address>.key for node-to-node encryption.

    • Client Certificates Directory: Enter the absolute path on each VDB host to the directory containing the same files for client-to-node encryption. You can use the same directory for node and client certificates. See Yugabyte TLS prerequisites.

  10. Click Next.

  11. (Optional) On the Policies page, select a previously defined VDB Snapshot Policy or the Use group policy check box:

    • Snapshot Policy: Defaults to DCT Default Snapshot (daily at 03:30 AM GMT).

    • Retention Policy: Defaults to DCT Default Retention (snapshots and logs removed after 1 week).

    • Click Change Policy to modify.

    • Click Next.

  12. (Optional) On the Masking page, enable Mask this VDB to apply data masking during provisioning. Leave unchecked if masking is not required.

  13. Click Next.

  14. (Optional) On the Hooks page, add hook scripts at available hook points for the following hook points:

    • Configure Clone

    • Pre Refresh / Post Refresh

    • Pre Self-Refresh (Rollback) / Post Self-Refresh (Rollback)

    • Pre Snapshot / Post Snapshot

    • Pre Start / Post Start

  15. Click + Hook to add a script. If no hooks are needed, click Next.

  16. On the Summary page, review all configuration details including Source, Target, Policies, Masking, and Settings and click Submit.

  17. After completion, the VDBs page displays the newly provisioned VDB (for example, VDB-Yugabyte) with a status of Running, platform yugabyte-vsdk, and engine YugabyteDB Engine.

  18. Click View to confirm that the status is RUNNING.

Last updated
Oct 19, 2026