Before you begin the upgrade process, contact Delphix Support to perform some pre-checks.
Scheduling Downtime
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 upgrade. The length of 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 3GB 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.
For example, if we want to upgrade to 5.1.8.0, you would need to download the following files:
“5.1.8.0/media/delphix_5.1.8.0_2017-08-09-16-07.upgrade.tar.gz”
“5.1.8.0/media/delphix_5.1.8.0_2017-08-09-16-07.upgrade.tar.gz.md5sum”
The first file is the actual upgrade file. The contents of the second text file is used to verify the MD5 hash value of the actual upgrade file. For instructions on using the md5sum file, see Verifying the Downloaded Upgrade Image.
Delphix Engines can only perform replication to engines on the same version; it is recommended to upgrade all engines in a replication group at the same time. Upgrading a replication source or target without upgrading its replication peers will cause replication between those peers to fail.