If your current Mirage system deployment exceeds the maximum number of clients, you can plan to deploy an additional Mirage system.

About this task

Deploying a replica environment when your deployment exceeds the maximum number of managed endpoints helps you to restore system or synchronize between several individual deployments. You can migrate all the system settings and layers from your existing deployment to your new deployment. You can import the Mirage system configuration and layers from the self-contained archive that was previously exported from your existing Mirage system. Use the command-line tool to make necessary changes to the destination Mirage system by either overriding current configuration or adding new items to the Mirage system. You can also use this tool to either restore your Mirage system to an earlier state or synchronize multiple Mirage systems. For the synchronization, create an automated task to export settings from one Mirage cluster once a day and import them to the other clusters. If there is no change, this daily task does not impact the Mirage system. The import process also restores items that existed on both source and destination Mirage systems and were deleted from the source.

You can import the following information and settings from the ZIP file that is exported from an existing Mirage deployment:

  • Common server configuration values

  • Bandwidth limiting settings

  • Driver libraries and profiles

  • Factory and CVD policies

  • USMT files

  • Base layers

  • App layers

Prerequisites

  • Ensure that the exported settings are valid before they can be imported.

  • Ensure that the destination location has enough free disk space (8 GB per base layer and 1 GB per app layer).

  • The administrator must be aware of the risks of importing the settings (for example, Overwriting current configuration, changing bandwidth limiting, and overwriting current USMT package) and provide in-process inputs if necessary.

  • The version of the source Mirage system and the destination Mirage systems must be the same.

Procedure

To import the system configuration and layers from a self-contained archive, run the following command.
C:\Program Files\Wanova\Mirage Management Server\Wanova.Server.Tools.exe ImportSystemSettings - miragemgmtIp IP address - tempFolder c:\export\tmp - iniFile c :\config.ini - archiveFile c:\export\MirageSettingsExport.zip

Example

Where:

  • -miragemgmtIp is followed by the IP address of the Mirage system to which you want to import the settings .

  • -tempFolder is followed by the path to the folder with the file to be imported is extracted.

  • -iniFile is followed by the path to the .ini answer file.

    Note:

    Create a .ini file using your text editor and add the following entries and toggle the values between true or false based on your requirements. Set the value of the parameters to true if you want to import the settings. Set the value of the parameters to false if you do not want to import the settings. If MergeContent is set to true, the imported settings are merged with the existing settings. If the MergeContent is set to false, the existing settings are overridden by the imported settings.

    Note:

    You must be aware of the settings in the .ini file because they might severely impact your system configuration.

    [BandwidthLimiting]
    Import=true
    MergeContent=true
    
    [USMT]
    Import=true
    
    [Policy]
    Import=true
    
    [Driver]
    Import=true
    
    [CommonConfig]
    Import=true
    
    [Layers]
    Import=true
  • archivePath is followed by the path to the settings ZIP file exported from your existing Mirage deployment.