Link a YugabyteDB using Seed ingestion in DCT

With Seed, Delphix creates an empty YugabyteDB universe on the staging host and mounts Delphix storage. You load your data into that universe.

Prerequisites

• The staging and target environments must meet the requirements described in the Yugabyte network and connectivity requirements.

• You are responsible for loading data into the empty YugabyteDB universe on the Delphix-mounted staging path.

Procedure

Perform the following steps to create a source config on the staging environment:

1. Log in to DCT.

2. Add a source config against the discovered staging or target YugabyteDB environment . For more information, read Create a source configuration for Connectors in DCT.

3. Go to Data>dSources tab and click +dSource.

4. On the Select Data Source page, select the YugabyteDB dSource.

5. Once the YugabyteDB dSource is selected, the following configuration settings will appear. Do the following:

• Enter the Database Name.

• Ingestion Type: Seed

• Mount Path on Staging Host: Absolute path where Delphix filesystem will be mounted on the staging host

• IP Address / Hostname of the Staging Cluster: Enter the IP address or fully qualified domain name (FQDN) of the node or load-balanced interface that will be used by Delphix to communicate with the YugabyteDB staging cluster.

• Yugabyte Anywhere URL: Enter the base URL (e.g., https://yba.example.com or https://10.43.52.215) of the Yugabyte Anywhere instance that manages the target Universe. This will be used by the connector for REST API operations.

• Yugabyte Anywhere API Key: Enter a valid API key with sufficient privileges to authenticate REST API requests to Yugabyte Anywhere for Universe creation, backup retrieval, and other operations.

• SSH Private Key Path: Enter the absolute path, on the staging host, to the PEM-formatted SSH private key that Yugabyte Anywhere uses for passwordless login to the universe nodes. The file must be readable by the staging OS user (recommended permissions: 0400).

• Universe Identifier: Enter the unique identifier (configured name) of the YugabyteDB Universe that will be used during the staging and provisioning process. This links the backup/restore process to the correct Universe within Yugabyte Anywhere.

• Database Names: Enter the names of the YugabyteDB Databases to be restored. If multiple keyspaces are required, separate them using commas (e.g., Database1,Database2).

• Enable Cluster Authentication: Select this check box to enable secure authentication for accessing the YugabyteDB cluster.

• Cluster Authentication Details -> Database Password: Enter the password that will be used to authenticate against the YugabyteDB database. Required only if cluster authentication is enabled.

• Additional Nodes: Use this section to define additional nodes (e.g., other hosts in the YugabyteDB cluster) that are part of the configuration. Click on Add to add a Node.

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

  • Environment User: Specify the OS-level user (e.g., yugabyte) that Delphix should use to connect to this additional node.

  • IP Address / Hostname of Additional Node: Enter the IP address or fully qualified domain name (FQDN) of the additional cluster 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)

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

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

• TLS Management Mode: Select Disabled, YBA Self-Signed (Auto), Customer Self-Signed, or CA-Signed.

• Certificate Label: Enter the name under which the certificate is registered in YBA. Leave blank to use delphix-tls-<universe name>.

• Root CA Cert Path: Enter the path to the PEM root CA certificate on the staging node for Customer Self-Signed mode, or a path that exists on every universe node for CA-Signed mode.

• Root CA Key Path: For Customer Self-Signed mode, enter the path to the root CA private key on the staging node.

• Node Cert Path / Node Key Path: For CA-Signed mode, enter the paths to the per-node certificate and key. Use the same paths on every node.

• Client Cert Path / Client Key Path: For CA-Signed mode, enter the paths to the per-node client certificate and key.

6. Click Next.

7. On the dSource Configuration page, enter a dSource name and select a group for your dSource. Adding a dSource to a dataset group allows you to manage user permissions for that database and its objects, including snapshots.

8. On the Data Management tab, specify your staging environment, user, and snapshot parameters. Select the Resynchronize dSource check box if you want to resynchronize the dSource. This operation will force a non-incremental load of data from the source. This operation is similar to creating a new dSource, but prevents duplication of the storage requirements and maintains timeflow history. Click Next to proceed.

9. On the Policies page, apply policy details to the dSource if needed, then click Next to continue.

10. On the Hooks tab, select a Hook Point and then click +add to add a script that you want to run at that hook point. You have the flexibility to define scripts to run at multiple hook points in the process.

11. On the Summary page, review the configuration profile for your dSource.

12. Click Submit. The Delphix Continuous Data Engine will initiate two jobs, namely DB_Link and DB_Sync to create the dSource.