Release Information

Introduction

Getting Started

Delphix Engine System Administration

Virtual Database Management with the Delphix Engine

Delphix Modernization Engine

Delphix Compliance Engine

Virtualizing Unstructured Files

Virtualizing Oracle E-Business Suite

Jet Stream

Mission Control Admin User Guide

Delphix Express User Guide

Reference


Documentation for Previous Versions of the Delphix Engine

Delphix Server 3.0 Documentation
Delphix Server 3.1 Documentation
Delphix Engine 3.2 Documentation
Delphix Engine 4.0 Documentation
Delphix Engine 4.1 Documentation

Skip to end of metadata
Go to start of metadata

This topic describes how to upgrade to a new version of the Delphix Engine.

Prerequisites

Upgrades of the Delphix Engine are performed with the assistance of Delphix support. A support engineer will be responsible for performing the steps described below. In preparation for any upgrade, a support case must be opened and the upgrade planned with the assistance of your support engineer.

Because the Delphix Engine may experience brief downtime while it is being upgraded to the new version, you should schedule appropriate downtime for your VDB applications. The VDBs themselves will be automatically disabled during upgrade by the Delphix Engine. The amount of downtime will be proportional to the number of VDBs.

Aside from VDBs being inaccessible during the upgrade, only system administrator users will be able to login to the Delphix Engine. The upgrade will automatically logout any logged in users, and will prevent new users from logging in.

Procedure

  1. Upload an upgrade image through the Delphix Setup GUI.
    1. Log in to the Server Setup application.
    2. In the System Upgrade Management panel, click View.
    3. Click the up arrow to upload a new version
  2. Using the command line interface, login as system administrator.
  3. Navigate to system version and list existing versions by entering list.
    The version you uploaded in step 1 will be listed there. Select it by name as follows.

    delphix> system version
    delphix system version> list
    NAME     STATUS             OSRUNNING  BUILDDATE               
    4.0.6.0  UPLOADED           false      2014-06-17T03:12:48.000Z
    4.0.5.0  CURRENTLY_RUNNING  true       2014-06-10T14:41:28.000Z
    delphix system version> select 4.0.6.0
    delphix system version "4.0.6.0"> 
  4. Start the upgrade by entering apply, then commit.
    Following commit, progress will be displayed as the upgrade executes.  When the Delphix Engine is rebooted to the new version, your CLI session will automatically be terminated. You will be able to log in again when the Delphix Engine has successfully started running the new version.

    delphix system version "4.0.6.0"> apply
    delphix system version "4.0.6.0" apply *> commit
        Dispatched job JOB-12
        UPGRADE_APPLY job started for "sysadmin".
        Starting upgrade to version "4.0.6.0".
        Applying upgrade image.
        Logging out users.
        Stopping policy execution.
        Suspending replication activity.
        Quiescing jobs.
        Disabling VDBs.
        Rebooting to the new version.
    Your CLI session is terminating because the system is being restarted to the new version.  The upgrade process will complete when the system comes back up, after which point you will be able to login again.  If you are still unable to login after a few minutes, contact Delphix support.

Deferred OS Upgrade

Each Delphix Engine upgrade image contains software for DelphixOS (the operating system that runs Delphix) in addition to Delphix management software. DelphixOS is versioned, and the OS version that is delivered with any given Delphix Engine version is displayed as "osVersion" in the version properties. By default, when applying a new version, if that version delivers a new OS (newer than what is currently running), the system will reboot to the new OS as part of the upgrade process. This requires scheduling downtime for VDBs, as VDBs are disabled during upgrade.

In some cases, it may be possible to defer upgrading DelphixOS even when a new version is included in the upgrade image. You can determine if this is a possibility by comparing the "minOsVersion" property of the new version with the "osVersion" that is currently running. For example:

delphix system version> list
NAME     STATUS             OSRUNNING  BUILDDATE               
4.0.6.0  UPLOADED           false      2014-06-17T03:12:48.000Z
4.0.5.0  CURRENTLY_RUNNING  true       2014-06-10T14:41:28.000Z

Here, the running OS comes from version 4.0.5.0, and we'd like to see if the OS version in 4.0.5.0 meets the minimum requirements for 4.0.6.0, the version we're upgrading to:

delphix system version> select 4.0.5.0 get osVersion
    4.0.2014.06.07
delphix system version> select 4.0.6.0 get osVersion
    4.0.2014.07.01
delphix system version> select 4.0.6.0 get minOsVersion
    4.0.2014.04.24

Here, although 4.0.6.0 includes a newer version of DelphixOS than what is currently running, its minimum OS version requirement is met by the currently running OS. We may then choose to defer upgrading DelphixOS when upgrading from 4.0.5.0 to 4.0.6.0 by setting the "defer" property in the "apply" context. In general, one can defer upgrading DelphixOS when the currently running OS version is greater than or equal to the minimum OS version requirements of the version being upgraded to. When you do such a deferred OS upgrade, the OS version will still be installed, but the system will simply not reboot to that new version. The Delphix Engine will still restart to the new version, but this restart will not result in downtime for VDBs. After that point, the "STATUS" column of the running version will show "DEFERRED" instead of "CURRENTLY_RUNNING" indicating that while this version is running, the OS upgrade was deferred.

The OS can later be updated to the current version by applying the running version again and not setting the defer property. When you do this, the system will simply reboot to the current version of DelphixOS (this will result in downtime for your VDBs).