Pre-check information

Before you begin the upgrade process, contact Delphix Support to perform some pre-checks.

Scheduling Downtime

To determine if an upgrade will require a reboot and VDB downtime refer to Upgrade Matrix

If the OS will not be updated as part of the upgrade, then the upgrade process will have no impact on the availability of VDBs, and you do not need to schedule any downtime for your VDB applications.

If the OS will be updated as part of the upgrade, then you should schedule appropriate downtime for your VDB applications. The Delphix Engine will automatically disable VDBs and dSources during the upgrade. The length of the downtime will be proportional to the number of VDBs.

Longrunning jobs including replication and SnapSync will fail during any upgrade.


The upgrade file for the version to which you want to upgrade should be downloaded from the 
Delphix download site.

Delphix Upgrade images are approximately 5GB in size; it is recommended to have both a fast internet connection to the Delphix download site as well as to the Delphix Engine.

The upgrade image should be downloaded or moved to a location accessible to the computer used for navigating the Delphix Management application.

The first file is the actual upgrade file. The contents of the second text file are used to verify the MD5 hash value of the actual upgrade file. For instructions on using the md5sum file, see Upgrade Verification.

Upgrading Replication Source

Delphix Engines can only perform replication to engines on the same or higher version. Upgrading a replication source without upgrading its replication targets could cause replication between those peers to fail.

Verifying the Integrity of the Downloaded Upgrade Image

Md5 checksum is used to verify the integrity of files, as virtually any change to a file will cause its MD5 hash to change. Most commonly, md5 checksum is used to verify that a file has not changed as a result of a faulty file transfer, a disk error or non-malicious meddling.

The “md5sum” program is included in most Unix-like operating systems, or compatibility layers such as Cygwin.

Please note that the following step is optional.

On Linux based systems, the command is md5sum <upgrade.tar.gz>, on mac, the command is md5 <upgrade.tar.gz> and on windows, the command is “CertUtil -hashfile <upgrade.tar.gz> MD5>. Verify that the output of the command’s md5 checksum is the same as the one in the md5sum file.

Verifying Connectivity to Datasets and Environments

If a new version of the operating system is included in the new Delphix version, then your Delphix Engine will automatically quiesce all VDBs and dSources during the upgrade process in order to safely reboot to the new version.

At the end of the upgrade process, the Delphix Engine will also update the Delphix platform toolkit on each connected environment.

To perform these tasks, the Delphix Engine must be able to connect to the environments in which datasets exist and must have credentials to connect to datasets or applications. Environments involved must be properly configured to enable script execution.

When an environment, dataset, or application is unreachable or misconfigured, the upgrade may encounter access errors, and may not be able to re-start it after the upgrade has been applied.

If you know that a dataset is unavailable for some reason (e.g. host not reachable on the network, or the hosting server is down), it is recommended that you disable it (if necessary utilize Force Disable). 

The Impact of Upgrade section in the Details tab contains the list of datasets that have been identified as unreachable, misconfigured or not behaving correctly and are at risk of not functioning after the upgrade.

Review the warnings in this section (if any) and take appropriate actions before applying the upgrade.

Related Topics