The staging and target environments requirements are as below.
Network and Connectivity Requirements
Ensure that the requirements for Delphix Engine network connectivity are met before proceeding further.
This section covers MSSQL Linux connector specific network and connectivity requirements.
SSH Connectivity to staging/target host
-
Staging and target environments are required to have sshd running and configured for Continuous Data to connect over ssh.
-
The Delphix platform expects to maintain long-running, highly performant ssh connections with the host environment.
Whitelisting inbound port for SSH connection to target host
Continuous Data Engine shares its storage space with the target host using NFS mounts.
|
Protocol |
Port Number |
Use |
|
TCP |
22 |
SSH and SFTP connections to the source, staging, and target database environments. Starting with Continuous Data 16.0.0.0, Delphix will use SCP connections only if SFTP is unavailable.
|
|
TCP/UDP |
111 |
Remote Procedure Call (RPC) port mapper used for NFSv3 mounts. |
|
TCP |
1110 |
Network Status Monitor (NSM) client from target hosts to the Continuous Data Engine. |
|
TCP |
2049 |
NFS client from target hosts to the Continuous Data Engine (NFSv3 and NFSv4). |
|
TCP |
54043 |
Client mount daemon (NFSv3 only). |
|
TCP |
54044 |
Lock state notification service (NFSv3 only). |
|
TCP |
54045 |
Network Lock Manager (NLM) client from target hosts to Continuous Data Engine (NFSv3 only). |
|
UDP |
33434 - 33464 |
Traceroute from the target database server to the Continuous Data Engine (optional). |
Connecting to MSSQL Linux Instances [dSource + VDBs]
|
Outgoing [From] |
Incoming [To] |
Protocol |
Port Number |
Use |
|
End-user hosts |
Staging / Target MSSQL DATABASE instance |
TCP |
<target-port> |
Connecting to the created database instance on the target host. |
Host environment requirements
To improve the performance of staging and target environments, refer to the Performance best practices and configuration guidelines for SQL Server on Linux documentation.
|
Staging/Target Host Requirements |
Explanation |
|
Host compatibility check The operating system and architecture of the target host must match the source environment. |
It is required that the source and the target environments should have identical OS and hardware configurations. |
|
The user should be mssql OS user or a member of the mssql group (primary group of the mssql user) |
|
|
MSSQL configuration file (default - /var/opt/mssql/mssql.conf) must be owned by mssql user and group |
If the Delphix user is the primary user, the configuration file (/var/opt/mssql/mssql.conf) must be owned by the Delphix user and the mssql group to ensure proper creation and management of datasets. If the configuration file is not owned by the Delphix user and the mssql group, it may cause issues during dataset discovery and related workflows. |
|
There must be a directory on the staging/target host where the MSSQL Connector support files can be installed (for example, /var/tmp) with the following properties:
|
This path is called the “Toolkit Path” in the Environment creation UI page. |
|
MSSQL Linux installation and compatibility check There must be an installation of MSSQL DATABASE on the staging/target host that is compatible with the installation of MSSQL DATABASE on the source host. |
The MSSQL database binary version on the staging/target must be identical to the source side. |
|
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:
|
|
|
Hostname and IP must be correctly set in /etc/hosts file. |
The output of the hostname -i command should produce the correct result as the IP address of the server. For example: [root@source ~]# hostname -i 10.110.211.225 |
|
Storage |
|
| Path validation | To ensure consistent and safe handling of path inputs, support for certain special characters has been restricted. The MSSQL for Linux connector will reject any path containing the following characters:
< > | * ? " \ ; & $ [space] |
| Instance username validation | Instance user names must not contain the following special characters:
; \ & < > ( ) [space] |