Upgrading the Delphix Engine: Overview

Upgrading the Delphix Engine is a multi-step process that requires some preparation. The engine upgrade process affects the availability of the Delphix Engine administrative interface and virtual datasets during the operation based on the type of upgrade you choose. Large configurations and Full/Apply Now upgrades can take one to two hours. Delay the Reboot upgrades typically complete within 15 to 30 minutes. You do not need to reboot unless you're instructed to by Delphix to receive specific fixes. Refer to Upgrade Matrix and the Version compatibility and support pre-checks section below before you begin the upgrade process.

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
Delay the reboot	The user interface, API, and CLI (Command Line Interface) are only available to the user performing the upgrade. dSources stop refreshing from production. Policies execution is delayed until after the upgrade completes. Continuous Data Jobs are canceled (and resume after the upgrade if supported). Continuous Compliance jobs are canceled (and do not resume after the upgrade). Access to VDB data is not affected by this upgrade, and can be used normally.
Apply now	In addition to performing an application upgrade, DelphixOS, the operating system that runs Delphix, also upgrades and the machine reboots to the new OS as part of the upgrade process. The Delphix Engine automatically disables all VDBs and dSources during the upgrade process in order to safely reboot to the new version, so you should 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 type

Description

Delay the reboot

The user interface, API, and CLI (Command Line Interface) are only available to the user performing the upgrade. dSources stop refreshing from production. Policies execution is delayed until after the upgrade completes. Continuous Data Jobs are canceled (and resume after the upgrade if supported). Continuous Compliance jobs are canceled (and do not resume after the upgrade). Access to VDB data is not affected by this upgrade, and can be used normally.

Apply now

In addition to performing an application upgrade, DelphixOS, the operating system that runs Delphix, also upgrades and the machine reboots to the new OS as part of the upgrade process. The Delphix Engine automatically disables all VDBs and dSources during the upgrade process in order to safely reboot to the new version, so you should 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.

Version compatibility and support pre-checks

Refer to Upgrade Matrix before you upgrade to a newer version.

If you run version 5.3.9 or older and want to upgrade to 6.0.0.0 or newer, contact Delphix Support to help coordinate your upgrade.

Upgrading from 6.0.x to 6.0.x includes pre-checks packaged in the upgrade image. You do not need to contact Delphix Support for these upgrades (For exmaple, 6.0.0.0 → 6.0.9.0).

Outline of the upgrade process

Outline of the steps for upgrading your Delphix Engine:

Upload the upgrade image to the Delphix Engine.
Verify and resolve the system requirements and known defects before you start the upgrade.
Schedule the appropriate downtime.
Start the upgrade and choose the upgrade type.
Address any runtime failures that occur as part of the upgrade.
Verify the upgrade was successful.