3.6. Updating Oracle VDI to Release 3.3.2

3.6.1. Before You Update
3.6.2. How to Update an Oracle VDI Center (Single Host)
3.6.3. How to Update an Oracle VDI Center (High Availability With Bundled MySQL Database)
3.6.4. How to Update an Oracle VDI Center (High Availability With Remote MySQL Database)

3.6.1. Before You Update

Updates to Oracle VDI release 3.3.2 are supported only from the following releases of Oracle VDI:

Operating System

Update Supported From

Oracle Linux (64-bit) on x86 platforms

Release 3.3.1

Oracle Solaris (64-bit) on x86 platforms

Release 3.3.1

Release 3.2.2

To update from any other release of Oracle VDI, contact Oracle Support.

To update Oracle VDI, follow the instructions for your specific Oracle VDI configuration:

Updating Sun Ray Client Firmware

When you update Oracle VDI, you also update the included Sun Ray Software component. You must update the firmware on your Sun Ray Clients for the new Sun Ray Software version. Instructions for how to update Sun Ray Client firmware can be found in Sun Ray Client Firmware in the Sun Ray Software 5.2 Administration Guide.

Updating from Oracle VDI Release 3.2.2

By default, Oracle VDI release 3.3.2 uses an embedded MySQL Server database instead of the bundled MySQL Cluster database used in Oracle VDI release 3.2.2. The following table summarizes the configuration changes that happen when you update from release 3.2.2.

Supported Configuration

Configuration Changes

Single Oracle VDI Host

  • The existing MySQL database is extended to support the new features for release 3.3.2.

  • Before the update, the database is treated as a remote database even though it is located on the Oracle VDI host. After the update, the database is still treated as a remote database.

  • The Single Oracle VDI Host Configuration model is different in release 3.3.2. You must perform a fresh installation, and not an update, to configure an Oracle VDI Center for this model.

High Availability with bundled MySQL Cluster

  • On the primary host, the existing data in the MySQL Cluster database is exported and imported in to a new embedded MySQL Server database. This database is the master database.

  • On the first secondary host, the existing MySQL Cluster database is removed and a new embedded MySQL Server database is created. This database is the slave database that receives asynchronous replications from the master.

  • On the other secondary hosts, the MySQL Cluster database is removed. MySQL Server is installed on these hosts but it is not used. These hosts have no database role.

  • Before the update, the primary host might be configured to not host any Oracle VDI sessions. After the update, the primary is configured to host Oracle VDI sessions.

  • After the update, the configuration model for the Oracle VDI Center is High Availability Configuration Using Embedded MySQL Database.

High Availability with Remote MySQL

  • The existing MySQL database is extended to support the new features for release 3.3.2.

  • Before the update, the primary host might be configured to not host any Oracle VDI sessions. After the update, the primary is configured to host Oracle VDI sessions.

  • After the update, the configuration model for the Oracle VDI Center is High Availability Configuration Using Remote MySQL Database.

Updating Virtualization Platforms

In addition to updating Oracle VDI, you might also have to update your virtualization platform. See the following for details of what is supported in this release:

3.6.2. How to Update an Oracle VDI Center (Single Host)

Before you begin:

  • Ensure that no users are logged in to Oracle VDI on the host. The update stops all Oracle VDI services.

  • If you are updating from Oracle VDI release 3.2.2, ensure that you have the user name and password of the privileged administrator of the remote database.

  • Check that the host meets the requirements for installing Oracle VDI, see Section 3.2, “Oracle VDI System Requirements”.

  • Check that the host meets the requirements for updating Oracle VDI, see Section 3.6.1, “Before You Update”.

  1. Download the Oracle VDI software archive to a temporary location on the host.

  2. Log in as root on the host.

  3. Make a backup of the Oracle VDI database.

    While the backup job is running, all other jobs are stopped or held in the queue.

    • From the CLI, run the vda-backup command.

      # /opt/SUNWvda/sbin/vda-backup -p <path-to-directory> -o <output-file-name>

      Use the vda-backup -h to see all the options for this command.

    • In Oracle VDI Manager:

      1. Go to SettingsVDI Center.

      2. Select the Database tab.

      3. In the VDI Database Backup section, click Backup.

  4. (Updates from Oracle VDI release 3.2.2 only) Make a note of your current Sun Ray Authentication Manager policy.

    Run the utpolicy command to check the policy. For example:

    # /opt/SUNWut/sbin/utpolicy 
    # Current Policy:
    -a -g -z both -m -k both -u both
    

    Make a note of the policy.

  5. Unzip the Oracle VDI software archive and change working directory to the extracted directory.

    # unzip vda_3.3.2_solaris_amd64.zip
    # cd vda_3.3.2_solaris_amd64
  6. Preserve the Oracle VDI configuration on the host.

    # ./vda-preserve

    This step preserves the Oracle VDI configuration settings and stops Oracle VDI services on the host.

  7. Install the software.

    # ./vda-install

    An existing installation is detected and you are prompted to update the installation.

    Oracle Virtual Desktop Infrastructure 3.3.2 Installation
            
    Oracle VDI 3.3.1 is already installed on this host.
    Do you want to update to Oracle VDI 3.3.2 now? ([y]/n)
  8. To update, press the Return key.

    The Software License Agreement is displayed and you are prompted to accept its terms and conditions.

    After accepting the license agreement, the update begins.

    If you are updating from Oracle VDI release 3.2.2, you are prompted for the administrator password for the remote database.

    Oracle VDI 3.3.2 Installation
    Updating from Oracle VDI 3.2.2 to Oracle VDI 3.3.2
    
    MySQL VDA Database Update.
    Enter remote database administrator privileged user name: mydbadmin
    Enter remote database administrator privileged password:

    Type the administrator password and press the Return key.

    The Oracle VDI components are updated.

  9. At the end of the update, you are prompted to configure Oracle VDI.

    Do you want to configure Oracle VDI 3.3.2 now? ([y]/n)

    To configure the host, press the Return key.

    To configure the host later, type n and press the Return key. Use the vda-config command to configure the host.

    The host is configured using the details from the preserved configuration.

  10. (Updates from Oracle VDI release 3.2.2 only) Check that the current Sun Ray Authentication Manager policy is the same as before the update.

    Run the utpolicy command to see the policy in effect after the update. For example:

    # /opt/SUNWut/sbin/utpolicy
    # Current Policy:
    -a -g -z both
    

    If the policy is not the same as the policy before the update, run the following command to configure the policy:

    # /opt/SUNWut/sbin/utpolicy <policy>

    For example:

    # /opt/SUNWut/sbin/utpolicy -a -g -z both -m -k both -u both

3.6.3. How to Update an Oracle VDI Center (High Availability With Bundled MySQL Database)

Before you begin:

  1. Make a backup of the Oracle VDI database.

    The backup can be made on any host in the Oracle VDI Center.

    While the backup job is running, all other jobs in the Oracle VDI Center are stopped or held in the queue.

    • From the CLI, run the vda-backup command.

      # /opt/SUNWvda/sbin/vda-backup -p <path-to-directory> -o <output-file-name>

      Use the vda-backup -h to see all the options for this command.

    • In Oracle VDI Manager:

      1. Go to SettingsVDI Center.

      2. Select the Database tab.

      3. In the VDI Database Backup section, click Backup.

  2. (Updates from Oracle VDI release 3.2.2 only) Make a note of your current Sun Ray Authentication Manager policy.

    Run the utpolicy command to check the policy. For example:

    # /opt/SUNWut/sbin/utpolicy 
    # Current Policy:
    -a -g -z both -m -k both -u both
    

    Make a note of the policy.

  3. Preserve the Oracle VDI configuration on all hosts in the Oracle VDI Center.

    Start with the primary, then the first secondary, followed by the second secondary, and finally the additional secondaries.

    Repeat the following steps on each Oracle VDI host.

    1. Download the Oracle VDI software archive to a temporary location on the host.

    2. Log in as root on the host.

    3. Unzip the Oracle VDI software archive and change working directory to the extracted directory.

      # unzip vda_3.3.2_solaris_amd64.zip
      # cd vda_3.3.2_solaris_amd64
    4. Run the preservation script.

      # ./vda-preserve

      This step preserves the Oracle VDI configuration settings and stops Oracle VDI services on the host.

  4. Install and configure the software on the primary host.

    1. Install the software.

      # ./vda-install

      An existing installation is detected and you are prompted to update the installation.

      Oracle Virtual Desktop Infrastructure 3.3.2 Installation
              
      Oracle VDI 3.3.1 is already installed on this host.
      Do you want to update to Oracle VDI 3.3.2 now? ([y]/n)
    2. To update, press the Return key.

      The Software License Agreement is displayed and you are prompted to accept its terms and conditions.

      After accepting the license agreement, the update begins.

      At the end of the update, you are prompted to configure Oracle VDI.

      Do you want to configure Oracle VDI 3.3.2 now? ([y]/n)
    3. To configure the host, press the Return key.

      To configure the primary host later, type n and press the Return key. Use the vda-config command to configure the host. If you do this, you must configure the primary before you configure any secondary hosts.

      The primary host is configured using the details from the preserved configuration.

  5. Install and configure the software on all the secondary hosts.

    Start with the first secondary, then the second secondary, followed by the additional secondaries.

    Only configure one secondary host at a time. Wait for the configuration to complete before adding additional secondary hosts.

    The steps for updating a secondary host depend on whether you are updating from Oracle VDI release 3.3.1 or release 3.2.2

    Updating a Secondary Host From Oracle VDI Release 3.3.1

    If you are updating from Oracle VDI release 3.3.1, repeat the following steps on each Oracle VDI secondary host.

    1. Install the software.

      # ./vda-install

      An existing installation is detected and you are prompted to update the installation.

      Oracle Virtual Desktop Infrastructure 3.3.2 Installation
              
      Oracle VDI 3.3.1 is already installed on this host.
      Do you want to update to Oracle VDI 3.3.2 now? ([y]/n)
    2. To update, press the Return key.

      The Software License Agreement is displayed and you are prompted to accept its terms and conditions.

      After accepting the license agreement, the update begins.

      At the end of the update, you are prompted to configure Oracle VDI.

      Do you want to configure Oracle VDI 3.3.2 now? ([y]/n)
    3. To configure the secondary host, press the Return key.

      To configure the secondary host later, type n and press the Return key. Use the vda-config command to configure the host. If you do this, you must configure the primary before you configure any secondary hosts.

      The host is configured using the details from the preserved configuration.

    Updating a Secondary Host From Oracle VDI Release 3.2.2

    If you are updating from Oracle VDI release 3.2.2, repeat the following steps on each Oracle VDI secondary host.

    1. Install the software.

      # ./vda-install

      An existing installation is detected and you are prompted to update the installation.

      Oracle Virtual Desktop Infrastructure 3.3.2 Installation
              
      Oracle VDI 3.2.2 is already installed on this host.
      Do you want to update to Oracle VDI 3.3.2 now? ([y]/n)
    2. To update, press the Return key.

      The Software License Agreement is displayed and you are prompted to accept its terms and conditions.

      After accepting the license agreement, the update begins.

      At the end of the update, you are prompted to configure Oracle VDI.

      Do you want to configure Oracle VDI 3.3.2 now? ([y]/n)
    3. To configure the secondary host, press the Return key.

      You are prompted to enter the DNS name of the primary host in the Oracle VDI Center.

      Oracle Virtual Desktop Infrastructure 3.3.2 Configuration
      
      Enter the primary Oracle VDI Host [primary.example.com]:

      To configure the secondary host later, type n and press the Return key. Use the vda-config command to configure the host. If you do this, you must configure the primary before you configure any secondary hosts.

    4. To accept the original primary host, press the Return key.

      The MD5 fingerprint of the primary's SSL certificate is displayed and you are prompted to enter the password of the root user on the primary host.

      Retrieving certificate from primary.example.com...
      MD5 fingerprint is 7F:59:0C:92:42:FD:13:34:B5:6A:B2:6A:BA:06:C4:E7.
      
      Enter the root password for primary.example.com:
    5. Check that the MD5 fingerprint matches the fingerprint of the primary host.

      This is an important security step that ensures you are adding the secondary to a genuine Oracle VDI Center. To check the fingerprint:

      1. Log in as root on the primary host.

      2. Use the vda-center agent-status command to display the MD5 fingerprint of the primary host.

        # /opt/SUNWvda/sbin/vda-center agent-status
        Agent is up for 0 day(s), 0:6.
        MD5 fingerprint is 7F:59:0C:92:42:FD:13:34:B5:6A:B2:6A:BA:06:C4:E7.
    6. On the secondary host, enter root's password and press the Return key.

      The host is configured using the supplied settings.

  6. (Updates from Oracle VDI release 3.2.2 only) Check that the current Sun Ray Authentication Manager policy is the same as before the update.

    Run the utpolicy command to see the policy in effect after the update. For example:

    # /opt/SUNWut/sbin/utpolicy
    # Current Policy:
    -a -g -z both
    

    If the policy is not the same as the policy before the update, run the following command to configure the policy:

    # /opt/SUNWut/sbin/utpolicy <policy>

    For example:

    # /opt/SUNWut/sbin/utpolicy -a -g -z both -m -k both -u both

3.6.4. How to Update an Oracle VDI Center (High Availability With Remote MySQL Database)

Before you begin:

  • Ensure that no users are logged in to the Oracle VDI Center. The update stops all Oracle VDI services in the Center.

  • Ensure that you have the user name and password of the privileged administrator of the remote database.

  • Check that the hosts meet the requirements for installing Oracle VDI, see Section 3.2, “Oracle VDI System Requirements”.

  • Check that the hosts meet the requirements for updating Oracle VDI, see Section 3.6.1, “Before You Update”.

  1. Make a backup of the Oracle VDI database.

    While the backup job is running, all other jobs in the Oracle VDI Center are stopped or held in the queue.

    • From the CLI, run the vda-backup command.

      # /opt/SUNWvda/sbin/vda-backup -p <path-to-directory> -o <output-file-name>

      Use the vda-backup -h to see all the options for this command.

    • In Oracle VDI Manager:

      1. Go to SettingsVDI Center.

      2. Select the Database tab.

      3. In the VDI Database Backup section, click Backup.

  2. (Updates from Oracle VDI release 3.2.2 only) Make a note of your current Sun Ray Authentication Manager policy.

    Run the utpolicy command to check the policy. For example:

    # /opt/SUNWut/sbin/utpolicy 
    # Current Policy:
    -a -g -z both -m -k both -u both
    

    Make a note of the policy.

  3. Preserve the Oracle VDI configuration on all hosts in the Oracle VDI Center.

    Start with the primary, then the first secondary, followed by the additional secondaries.

    Repeat the following steps on each Oracle VDI host.

    1. Download the Oracle VDI software archive to a temporary location on the host.

    2. Log in as root on the host.

    3. Unzip the Oracle VDI software archive and change working directory to the extracted directory.

      # unzip vda_3.3.2_solaris_amd64.zip
      # cd vda_3.3.2_solaris_amd64
    4. Run the preservation script.

      # ./vda-preserve

      This step preserves the Oracle VDI configuration settings and stops Oracle VDI services on the host.

  4. Install and configure the software on the primary host.

    1. Install the software.

      # ./vda-install

      An existing installation is detected and you are prompted to update the installation.

      Oracle Virtual Desktop Infrastructure 3.3.2 Installation
              
      Oracle VDI 3.3.1 is already installed on this host.
      Do you want to update to Oracle VDI now? ([y]/n)
    2. To update, press the Return key.

      The Software License Agreement is displayed and you are prompted to accept its terms and conditions.

      After accepting the license agreement, the update begins and you are prompted for the administrator password for the remote database.

      Oracle VDI 3.3.2 Installation
      Updating from Oracle VDI 3.3.1 to Oracle VDI 3.3.2
      
      MySQL VDA Database Update.
      Enter remote database administrator privileged user name: mydbadmin
      Enter remote database administrator privileged password:
    3. Enter the administrator password and press the Return key.

      The Oracle VDI components are updated.

      At the end of the update, you are prompted to configure Oracle VDI.

      Do you want to configure Oracle VDI 3.3.2 now? ([y]/n)
    4. To configure the host, press the Return key.

      The primary host is configured using the details from the preserved configuration.

      To configure the primary host later, type n and press the Return key. Use the vda-config command to configure the host. If you do this, you must configure the primary before you configure any secondary hosts.

  5. Install and configure the software on all the secondary hosts.

    Start with the first secondary, followed by the additional secondaries.

    Only configure one secondary host at a time. Wait for the configuration to complete before configuring additional secondary hosts.

    The steps for updating a secondary host depend on whether you are updating from Oracle VDI release 3.3.1 or release 3.2.2

    Updating a Secondary Host From Oracle VDI Release 3.3.1

    If you are updating from Oracle VDI release 3.3.1, repeat the following steps on each Oracle VDI secondary host.

    1. Install the software.

      # ./vda-install

      An existing installation is detected and you are prompted to update the installation.

      Oracle Virtual Desktop Infrastructure 3.3.2 Installation
              
      Oracle VDI 3.3.1 is already installed on this host.
      Do you want to update to Oracle VDI 3.3.2 now? ([y]/n)
    2. To update, press the Return key.

      The Software License Agreement is displayed and you are prompted to accept its terms and conditions.

      After accepting the license agreement, the update begins.

      At the end of the update, you are prompted to configure Oracle VDI.

      Do you want to configure Oracle VDI 3.3.2 now? ([y]/n)
    3. To configure the secondary host, press the Return key.

      To configure the secondary host later, type n and press the Return key. Use the vda-config command to configure the host. If you do this, you must configure the primary before you configure any secondary hosts.

      The host is configured using the details from the preserved configuration.

    Updating a Secondary Host From Oracle VDI Release 3.2.2

    If you are updating from Oracle VDI release 3.2.2, repeat the following steps on each Oracle VDI secondary host.

    1. Install the software.

      # ./vda-install

      An existing installation is detected and you are prompted to update the installation.

      Oracle Virtual Desktop Infrastructure 3.3.2 Installation
              
      Oracle VDI 3.2.2 is already installed on this host.
      Do you want to update to Oracle VDI 3.3.2 now? ([y]/n)
    2. To update, press the Return key.

      The Software License Agreement is displayed and you are prompted to accept its terms and conditions.

      After accepting the license agreement, the update begins.

      At the end of the update, you are prompted to configure Oracle VDI.

      Do you want to configure Oracle VDI 3.3.2 now? ([y]/n)
    3. To configure the secondary host, press the Return key.

      You are prompted to enter the DNS name of the primary host in the Oracle VDI Center.

      Oracle Virtual Desktop Infrastructure 3.3.2 Configuration
      
      Enter the primary Oracle VDI Host [primary.example.com]:

      To configure the secondary host later, type n and press the Return key. Use the vda-config command to configure the host. If you do this, you must configure the primary before you configure any secondary hosts.

    4. To accept the original primary host, press the Return key.

      The MD5 fingerprint of the primary's SSL certificate is displayed and you are prompted to enter the password of the root user on the primary host.

      Retrieving certificate from primary.example.com...
      MD5 fingerprint is 7F:59:0C:92:42:FD:13:34:B5:6A:B2:6A:BA:06:C4:E7.
      
      Enter the root password for primary.example.com:
    5. Check that the MD5 fingerprint matches the fingerprint of the primary host.

      This is an important security step that ensures you are adding the secondary to a genuine Oracle VDI Center. To check the fingerprint:

      1. Log in as root on the primary host.

      2. Use the vda-center agent-status command to display the MD5 fingerprint of the primary host.

        # /opt/SUNWvda/sbin/vda-center agent-status
        Agent is up for 0 day(s), 0:6.
        MD5 fingerprint is 7F:59:0C:92:42:FD:13:34:B5:6A:B2:6A:BA:06:C4:E7.
    6. On the secondary host, enter root's password and press the Return key.

      The host is configured using the supplied settings.

  6. (Updates from Oracle VDI release 3.2.2 only) Check that the current Sun Ray Authentication Manager policy is the same as before the update.

    Run the utpolicy command to see the policy in effect after the update, for example:

    # /opt/SUNWut/sbin/utpolicy
    # Current Policy:
    -a -g -z both

    If the policy is not the same as the policy before the update, run the following command to configure the policy:

    # /opt/SUNWut/sbin/utpolicy <policy>

    For example:

    # /opt/SUNWut/sbin/utpolicy -a -g -z both -m -k both -u both