Skip to main content
Skip table of contents

Network and connectivity requirements for CockroachDB

SSH connectivity to target host

  1. Staging and target environments are required to have sshd running and configured such that the Continuous Data Engine can connect over ssh.

  2. The Delphix platform expects to maintain long-running, highly performant ssh connections with the host environment.

  3. Depending on the Ingestion type, once connected to a target environment through SSH, the Continuous Data Engine initiates a CockroachDB client connection(cockroach) from the staging environment to the source environment.

Whitelisting inbound port for SSH connection to target host


Port Number




SSH connections to the target database environment



Remote Procedure Call (RPC) port mapper used for NFSv3 mounts



Network Status Monitor (NSM) client from target hosts to the Continuous Data Engine



NFS client from target hosts to the Continuous Data Engine (NFSv3 and NFSv4)



Client mount daemon (NFSv3 only)



Lock state notification service (NFSv3 only)



Network Lock Manager (NLM) client from target hosts to Continuous Data Engine (NFSv3 only)


33434 - 33464

Traceroute from the target database server to the Continuous Data Engine (optional)

Connecting to CockroachDB Instances [Source + dSource + VDBs]

Outgoing [From]

Incoming [To]


Port Number


Staging host

Source CockroachDB Instance



CockroachDB Source database instance port to connect to setting up replication pipeline. The default port for a CockroachDB instance is 26257.

End-user hosts

Staging / Target CockroachDB instance



Connecting to the created database instance on the target host.

Host environment requirements for CockroachDB

Staging/Target Host Requirements

Additional Details

Host Compatibility Check

The operating system and architecture of the target environment must match the source environment.

It is required that the source and the target environments must have identical Operating system and hardware architecture configurations.

CockroachDB Installation and Compatibility Check

There must be an installation of CockroachDB on the staging/target host that is compatible with the installation of CockroachDB on the source host.

The CockroachDB binary version on the staging/target must be identical to the source host.

There must be a directory on the staging/target host where the CockroachDB Connector support files can be installed (for example, /var/tmp) with the following properties:

  1. The directory must be writable by the operating system user mentioned above.

  2. The directory must have at least 1.5 GB of available storage.

This path is called the “Toolkit Path” on the Environment creation UI page.

During VDB provisioning, there must be a mount point directory (for example, /mnt) that will be used as the base for mount points that are created when provisioning a VDB with the following properties:

  1. The mount point directory must be writable by the operating system user mentioned above.

  2. The mount point directory should be empty.

Hostname and IP must be correctly set in /etc/hosts file.

The output of “hostname -i” command should produce the correct result as the IP address of the server.

For example:

[root@source ~]# hostname -i

Required Utilities and Tools

Ensure that either the netstat or ss utility is installed on the Staging/Target Host.

CockroachDB Connector checks the status of the running CockroachDB instance and validates if ports are available on the staging/target host using the netstat or ss utility.

Checking if netstat or ss utility is installed

which netstat

which ss

Storage Requirement

  1. Staging Host must have enough storage space to hold the source backup file.

  2. Empty folder on staging host to hold delphix toolkit [ approximate 2GB free space ]

Sizing Requirement

For comprehensive details and configuration guidelines on setting up staging/target CockroachDB clusters, refer to the official documentation: CockroachDB Sizing Recommendations

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.