You can upgrade to the latest version of Mirage if you have an existing installation of Mirage.
- Make a note of these items to use during installation (either in the server config file or locate via other methods):
Database server name
Credentials for the database server
Mirage Server cache directory locationNote:
The default location of the Mirage Server Cache is C:\ProgramData\Wanova Mirage\LocalCache.
You can identify the cache size by selecting this directory and viewing the properties to see the size.
- Prepare MongoDB deployment.
MongoDB, introduced in Mirage 5.4 and later, dramatically improves the IO consumption of Mirage Image Service. MongoDB requires some prerequisites to function correctly and reliably.
If you are upgrading from Mirage 5.3 or earlier, perform the following steps:
Prepare the server to install a second management server. The second management server is recommended to eliminate MongoDB as a single point of failure and prevent corruption. The second management server keeps a replicated copy of the MongoDB database.
Prepare a local, dedicated, 250GB disk drive for MongoDB on each management server (both the original management server and the new secondary one). If the environment contains more than 3000 CVDs, prepare a disk of at least 5% of your total Mirage volume size.
The management server installation wizard prompts you enter the location of the disks you have prepared for the upgrade.
If you are upgrading from Mirage version 5.4 or later, perform the following steps:
In Mirage 5.4, MongoDB was located on a Mirage volume on the same disk with CVDs. This is not a good practice for Mirage 5.5 and above; it is highly recommended to install MongoDB on a local disk.
Check if MongoDB is located on a volume or a local disk (The current MongoDB path can be seen in the web management under Servers > Management Servers). If it is not located on a local, dedicated disk, prepare a local, dedicated, 250GB disk drive for MongoDB on each management server (both the original management server and the new secondary management server).
If the environment contains more than 3000 CVDs, prepare a disk of at least 5% of your total Mirage volume size. Make sure there are two managements server instances. If not, prepare a second server to eliminate MongoDB as a single point of failure and prevent corruption. The second management server keeps a replicated copy of the MongoDB database.
- Stop Mirage Service.
- Back up the Mirage database using one of these 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.Note:
For more information on backing up the MS SQL database, see Using SQL Server Management Studio in the MSDN article https://msdn.microsoft.com/en-us/library/ms174173.aspx
Ensure you select the database named MirageDB, and that you use the Full backup type.
Make a note of the location of the backup file.
If the MirageDB is a remote Database, the backup of the database may not be able to capture the backup file. Confirm the backup file has been created in the sysreport zip file under the ServerDB folder. If it has been created successfully a MirageDB.bak exists. If this file does not exist, see Collecting the database backup (MirageDB.bak) when the database is remote to the Mirage Management Server (2086220) for remote database configuration settings.
- Take snapshots of all Mirage volumes. Ensure that you use image based block backup, and not file based.
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.