Upgrading the Delphix Engine is a multi-step process that requires preparation. The upgrade affects the availability of the Delphix Engine, Masking services, DCT services, the administrative interface, and virtual datasets. The impact depends on the engine type and upgrade type. For large Continuous Data configurations, Upgrade and Reboot can take one to two hours. Upgrade Only typically takes 15 to 30 minutes. You do not need to reboot unless you're instructed to by Delphix to receive specific fixes.
Refer to the Upgrade matrix before upgrading. Review the release notes and version-specific documentation for your source version, target version, and every intermediate version you upgrade through for prerequisites and conditions.
For upgrades from version 6.0.0.0 or later to a compatible version, contacting Delphix Support is not required.
Upgrade images for target versions 6.0.2.0 and later include upgrade pre-checks. Use the latest target-version image because checks may be updated between releases.
Upgrades from version 2025.3.0.* or older to version 2025.4.0.* or newer require an Upgrade and Reboot and VDB downtime.
The following sections explain the steps involved in the upgrade process with links to detailed instructions for each step.
Types of upgrade
There are two types of upgrades, characterized by the impact they have on VDBs during the operation:
|
Upgrade type |
Description |
|---|---|
|
Upgrade Only |
The user interface, API, and CLI (Command Line Interface) are available only to the user performing the upgrade. They restart after the new software is installed. For Continuous Data engines, dSources stop refreshing from production, and policy execution is delayed until the upgrade completes. Continuous Data jobs are canceled. A resumable job can continue from its previous progress when restarted, but it does not necessarily restart automatically. After the upgrade, restart jobs that do not restart automatically, following the associated product documentation. Jobs not documented as resumable start over from the beginning. Continuous Compliance jobs are canceled and do not resume after the upgrade; Continuous Compliance services are unavailable during the upgrade. DCT jobs are canceled, and DCT services are unavailable during the upgrade. Access to VDB data is not affected and remains available. |
|
Upgrade and Reboot |
In addition to the Upgrade Only impact, the machine reboots as part of the process. After the software updates have been applied and the management services have restarted, the Delphix Engine automatically disables all VDBs and dSources to safely reboot to the updated version. Schedule downtime for your VDB applications. When SQL Server VDBs are disabled and enabled during upgrades, both the DB_CHAINING and TRUSTWORTHY database parameters are also disabled. If you use these parameters, Delphix recommends a Post Start Hook to set them as desired. For more information, read the Inheritance of Database Properties During SQL Server VDB Operations KB article. |
Upgrade process outline
Outline of the steps for upgrading your Delphix Engine:
-
Upload the upgrade image to the Delphix Engine.
-
Verify the target version and hotfixes. Resolve critical check results, and resolve or ignore warning results before you start the upgrade. For more information, see Resolve upgrade checks.
-
Schedule time for jobs and management interfaces to be unavailable during Upgrade Only. For Upgrade and Reboot, schedule VDB application downtime as well.
-
Start the upgrade and choose the upgrade type. When the Upgrade matrix lists reboot as optional, Upgrade Only is recommended.
-
For an Upgrade and Reboot only, address any issues that prevent VDBs from being quiesced.
-
Verify that the upgrade completed successfully. If a reboot is required and you selected Upgrade Only, complete it by using Finalize Upgrade. For more information, see Finalize upgrade.
-
Verify that post-upgrade activities completed successfully, including environment and host refreshes and, if applicable, unquiescing datasets.