Before You Start to Upgrade Mirage

<

Before you begin the upgrade process, you must perform certain pre-upgrade steps.

About this task

Mirage uses a MongoDB database to store system data and small files, which improves performance. The MongoDB files are created and stored on a dedicated path. Unlike previous Mirage versions, 5.3 and earlier, loss of system data stored in the MongoDB database can impact the entire system, including CVDs. VMware recommends that after you upgrade Mirage, you install an additional Mirage Management server.

If you are upgrading from Mirage 5.3 or earlier, when you install the Mirage Management server, you are prompted to specify a path for the MongoDB database files.

If you are upgrading from Mirage 5.4, when you install the Mirage Management server, you are not prompted to specify a path for the MongoDB database files. After you upgrade from Mirage 5.4, VMware recommends that you install an additional Mirage Management server to ensure data availability.

Prerequisites

Verify that you have the following information available from the server config file.

Database server name

Credentials for the database server

Mirage server cache directory location

Cache size

Procedure

Stop Mirage services.

Back up the Mirage database.

Double-click the C:\Program Files\Wanova\Mirage Management Server\sysreport_full.cmd file to run a full sysreport in Mirage

Use SQL Server Management Studio.

Take snapshots of all Mirage storage volumes.

Use image-based block backup, not file-based backup.

If you cannot make a snapshot, create and run a backup job for each volume's directory using any available backup program.

This process can take a significant amount of time to complete. The backup software must support Alternate Data Streams (ADS). For best results, use block-based backup programs rather than file-level backup using ADS.