Search the VMware Knowledge Base (KB)
View by Article ID

Best practices for upgrading VMware Mirage (2031711)

  • 34 Ratings

Purpose

This article provides information on the best practices when upgrading VMware Horizon Mirage.

Resolution

Upgrading a Mirage system:

  1. Make a note of these items to use during installation (either in the server config file or locate using other methods):

    • Database server name
    • Credentials for the database server
    • Mirage server cache directory location

      Note: The default location of the Mirage Server Cache is C:\ProgramData\Wanova Mirage\LocalCache.

    • Cache size

      Note: To identify the cache size, select the directory and view properties.

  2. Prepare Mongo deployment.

    Mirage 5.4 and later added a new component, the Mongo database which dramatically improves the IO consumption of Mirage.

    This component requires some prerequisites to function correctly and reliably:

    If upgrading from Mirage versions 5.3 and earlier:

    1. Prepare a server to install a second management server.

      Note: A second management server is recommended to eliminate Mongo as a single point of failure and prevent corruption. This server will keep a replicated copy of the Mongo database.
    2. Prepare a local, dedicated, 250GB disk drive for Mongo on each management server (including the original management server and the new secondary management server).

      Note: If the environment contains more than 3000 CVDs, prepare a disk of at least 5% of your total Mirage volume size.
    3. The management server installation wizard prompts you to input the location of the disks you have prepared for the upgrade.

    If upgrading from Mirage version 5.4 and later:

    Note: In Mirage 5.4, Mongo was located on a Mirage volume on the same disk with CVDs. For Mirage 5.5 and later, it is highly recommended to locate Mongo on a local disk.

    1. Check if Mongo is located on a volume or a local disk (the current Mongo path in the web manager is under Servers > Management Servers).

      If it is not located on a local, dedicated disk, prepare a local, dedicated, 250GB disk drive for Mongo on each management server (including the original management server and the new secondary management server).
    2. If the environment contains more than 3000 CVDs, prepare a disk of at least 5% of your total Mirage volume size. Ensure that there are two managements server instances.
      If not, prepare a second server to eliminate Mongo as a single point of failure and prevent corruption. The second management server will keep a replicated copy of the Mongo database.
    3. Stop Mirage Services.

  3. Backup the Mirage database using one of the two methods:

    • Run a full sysreport in Mirage by double-clicking this file:

      C:\Program Files\Wanova\Mirage Management Server\sysreport_full.cmd
    • Use SQL Server Management Studio.

      Notes:
  4. Take snapshots of all Mirage volumes. Ensure that you use image based block backup, and not file based.

    Note: If snapshot functionality is not available, create and run a backup job for each volume's directory using any available backup program. This takes a significant amount of time to complete. The backup software must support Alternate Data Streams (ADS). VMware recommends using block based backup programs rather than file level backup using ADS.
  5. If upgrading from version 5.4 and later, backup the Mongo database:
    1. Log in to the Mirage Web Manager, and navigate to Servers > Management Servers.
    2. Note the MongoDB path of one of the nodes marked as “Up”.
    3. Stop all Mirage services.
    4. Backup the folder containing all the Mongo collection.

      Note: Backup only one of the instances of Mongo as they are replicated.
To upgrade Mirage:
  1. Go to Control Panel > Add or Remove Programs and uninstall the Mirage system in this order:

    1. Uninstall all Mirage Servers.
    2. Uninstall Mirage Web Manager.
    3. Uninstall all instances of Mirage Management Server.
    4. Uninstall Mirage WebAccess.
  2. Install the latest version of Mirage using the new MSIs in this order:

    1. Install Mirage Management Server.
    2. Install Mirage Web Manager.
    3. Install Mirage Server.
    4. Install Mirage WebAccess.
  3. After the installation is complete, if Mongo was not located on a local disk, move it to the local disk which was prepared in advance.
  4. When both Management servers are up and replicated (marked as Up in the Web Manager console under Servers > Management Servers):
    If upgrading to Mirage 5.6 and later:

    1. In the web management, go to Servers > Management Servers.
    2. Choose the correct Mongo instance and click Configure.
    3. Change the path to the target local dedicated disk and click OK.

      If you want to move to version 5.5, or without a second replicated Mongo node, see Changing the location of MongoDB when in use by Mirage(2131044).

Note: Mirage 5.x and later versions do not require the uninstallation and reinstallation as Mirage installers perform these actions. VMware recommends keeping the same order of the installation. However, it is not a requirement as the console notifies if there is any version mismatch.

Impact/Risks

If you have enabled the experimental App Layering feature in Mirage 3.6, review Upgrading Mirage 3.6 with experimental App Layers enabled is not supported (2046226) before proceeding.

See Also

Update History

8/14/2014 - Added Note under Resolution section.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 34 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 34 Ratings
Actions
KB: