Advanced configuration

This topic details customizing plugin timeouts and retry parameters for the Yugabyte plugin. You can modify these parameters in the plugin_timeouts_and_retries section of the yugabyte_plugin_config.conf file. If any key is missing or invalid, the fallback default from the plugin code will be applied and the file rewritten.

Parameter value Usage
liveTsSearchingLoopMaxRetries Maximum number of retries when searching for a live timestamp during backup operations.
sleepInLiveTsSearchingRoundSec Seconds to wait between each live‑timestamp‑search retry round.
createSnapshotTimeoutSec Time (in seconds) to wait for a snapshot creation operation to complete before timing out.
restoreDownloadLoopMaxRetries Maximum number of retry attempts for downloading backup data during a restore.
restoreSnapshotTimeoutSec Time (in seconds) to wait for the restore snapshot process to finish before timing out.
replicasSearchingLoopMaxRetries Maximum number of retries when locating replica tablet servers in the cluster.
sleepInReplicasSearchingRoundSec Seconds to pause between each replica‑search retry cycle.
disableSplittingMs Duration (in milliseconds) to temporarily disable tablet splitting after certain operations.
disableSplittingFreqSec Interval (in seconds) between successive attempts to disable tablet splitting.
isSplittingDisabledMaxRetries Maximum number of retries to verify that splitting has been successfully disabled.
createMetafilesMaxRetries Maximum number of retry attempts when generating backup metadata files.
leadersSearchingLoopMaxRetries Maximum number of retries when searching for leader nodes in the cluster.
sleepInLeadersSearchingRoundSec Seconds to wait between each leader‑search retry round.
testSleepAfterFindSnapshotDirsSec Seconds to pause after locating snapshot directories before proceeding to the next step.
baseDelay Initial backoff delay (in milliseconds) for Yugabyte Anywhere API call retries.
maxDelay Maximum backoff delay (in milliseconds) for Yugabyte Anywhere API call retries.
timeout Overall timeout (in seconds) for Yugabyte Anywhere API requests.

Backup, cloud CLI, and TLS issues

  • No valid backup found: Check that Backup Location points to the universe folder (univ-<id>), that every database listed in Database Names is included, and that the backups completed successfully in YBA. In-progress and failed backups are ignored.

  • The dSource contains older data than expected: The connector restores the most recent completed full backup and the most recent completed incremental backup. Check that recent backups completed successfully and incremental backups are enabled in the backup policy. Resynchronize the dSource to pick up newer backups.

  • Cloud CLI not found: Install the AWS CLI for S3 or the Azure CLI for Azure Blob Storage on the staging host.

  • Node certificate not found: Check that the certificate file name matches the IP address or hostname entered for the node. The certificate Subject Alternative Name must include both the DNS name and the IP address. See Yugabyte TLS prerequisites.

  • Permission denied on the mount path: Ensure that the staging mount path is writable by the Delphix OS user. Delphix updates permissions during resynchronization.

Plugin config file

After installation—or on the first operation—the plugin will generate the file:

<toolkit path>/Delphix_COMMON_<long id>/plugin/sc\:yugabyte_fc862709-a6e7-473f-8eed-70eae7af04eb/.delphix/yugabyte_plugin_config.conf

This yugabyte_plugin_config.conf lives in the reserved directory and includes a [plugin_timeouts_and_retries] section with all of the parameters detailed above. You can edit this file directly, or allow the YugabyteConfigManager to detect and correct any missing or invalid entries automatically.

Logging

There are the following sets of logs for the Yugabyte connector.

  1. The connector logs are part of the Delphix Continuous Data Engine. Refer to How to Retrieve Logs to find out how to get the Delphix connector Logs.

  2. Yugabyte Instance logs:

    1. YugabyteDB Instance logs are located at:

      1. <mount_path>/<node_name>/yb-data/master/logs for master

      2. <mount_path>/<node_name>/yb-data/tserver/logs for server

    Consult the Yugabyte documentation to determine instance log locations, as there are different log paths for YB-Anywhere, and for various cluster or single-node Yugabyte deployments.
Last updated
Oct 19, 2026