Requirements for MySQL staging and target environments

Host compatibility check

The Operating System and architecture of the staging/target host must be compatible with the source environment. 

The source and target environments must have identical Operating Systems and hardware configurations.

MySQL installation and compatibility check

MySQL must be installed on the staging/target host in a way that is compatible with MySQL installation on the source host.

Two MySQL installations can only be compatible if and only if the staging/target's version number is equal to the source's version number.

Network Connectivity Requirements

Delphix Continuous Data Engine, staging and target host must follow the network requirements mentioned in the Network and connectivity requirements topic.

The source database must be accessible from the staging host whenever Replication Ingestion Mechanism is used. 

Staging/Target Operating System Environment OS User

An environment user with elevated permissions can execute ps, mount, umount, mkdir, and rmdir commands without entering a password.

The Delphix Continuous Data Engine connects to the target host (via SSH) to perform the following operations: 

1. Mount and unmount directories for linking and provisioning operations. This privilege is required because mount and unmount are typically reserved for the superuser.

2. Create and remove directories for linking and provisioning operations.

3. Run all commands requested by the MySQL connector.

You need to provide the below permissions in the sudoers file for the staging/target or Delphix Continuous Data Engine user for the plugin to work correctly:

1. Open the sudoers file using the below:
 
vi /etc/sudoers
# Or
visudo


2. Below entries need to be created in the sudoers file:

Defaults:delphix_os !requiretty
delphix_os ALL=NOPASSWD: \
/bin/mount, /bin/umount, /bin/mkdir, /bin/rmdir, /bin/ps

Delphix Continuous Data Engine requires that the requiretty setting be disabled for all Delphix Continuous Data Engine users with sudo privileges.

It is required to specify the NOPASSWD qualifier within the "sudo" configuration file, as shown here, This ensures that the "sudo" command does not demand the entry of a password, even for the “display permissions” (i.e. sudo -l) command.

Toolkit Pathfield

On the staging/target host, a directory with the following properties must exist:

1. The directory must be writable by the previously mentioned staging/target operating system user.

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

The directory on the staging/target host where the MySQL connector support files are installed (for example, /opt/toolkit) is specified in the "Toolkit Path" field on the Environment creation UI page.

Required utilities and tools

Make sure the netstat or ss utilities are installed on the staging/target host.

MySQL connector checks the status of the running MySQL instance and the availability of ports on the staging/target host using the netstat or ss utilities.

Checking to see if the netstat and ss utilities are installed.

which netstat
which ss

Set Hostname and IP in host file (Optional)

Hostname and IP can be defined in the /etc/hosts file.

The hostname -i command should return the correct server IP address.

For example:

[root@source ~]# hostname -i
10.110.252.214

MySQL Configuration File (Optional) 

Define a my.cnf file for further configuration.

• The my.cnf file is a MySQL database configuration file. It holds a list of parameters to configure the MySQL database server.

• You can place a starter my.cnf file into the Delphix Toolkit Directory, and Delphix Continuous Data Engine will use this my.cnf file for creating a staging database. 

• Having a my.cnf in the toolkit directory is not mandatory. If this file is not provided, Delphix Continuous Data Engine will create a my.cnf file from scratch. 

• The following my.cnf parameters are considered restricted and will be ignored if specified: server-id, socket, port, basedir, data-dir, tmpdir, log-error, and pid-file.

• An invalid my.cnf file will cause errors during dSource linking and/or VDB provisioning.

• The contents of a my.cnf file will be attached to snapshots and inherited during VDB provisioning.

• The default or inherited my.cnf file can be modified further through additions during the dSource and/or VDB configuration steps.

• From high to low, the hierarchy of my.cnf parameters are as follows:

  • VDB or dSource configuration settings.

  • Inheritance of the my.cnf from Staging/dSource to child VDBs.

  • The staging database’s starter my.cnf file provided by the user.

  • Default my.cnf values.

To ensure consistent and secure path handling, the MySQL connector now applies path validation on UI fields.

Paths must start with / and may include only letters, digits, periods (.), underscores (_), hyphens (-), and slashes (/).

To ensure consistent and secure username handling, validation has been added to UI fields.

Usernames must start with a letter or underscore (_), can include letters, digits, periods ., space , $, or -, and may be up to 32 characters long.