You can view and manage information about the Mirage servers, Mirage Management servers, and Mirage Gateway servers in your environment, such as server status, connections, port, and so on.

You can perform various actions for the servers.

Table 1. Managing Mirageservers, Mirage Management servers




Configure the maximum connections, port, transport type, and certificate information.


Remove the selected servers.


Start the selected servers.


Stop the selected servers.

Collect Logs

You select the report level, destination, and UNC path.

You can configure and remove Mirage Gateway servers.

You can view the MongoDB path on the Management Servers tab. If a Mirage Management server has less than 5% of available disk space, uploads are suspended for all Mirage Management servers in the Mirage system. Uploads restart after there is sufficient free disk space on the Mirage Management server or after you move the MongoDB database to a drive with sufficient free disk space.

As an administrator, you can move the MongoDB data of a selected Mirage Management Server to a different location. This feature is enabled only after installing more than one Mirage Management Server. In your Web Management, click Servers > Management Servers > Configure. In the Configure Mirage Management Server dialog, enter the name of the location where you move the MongoDB data and click OK.

The Web Management generates events for MongoDB connectivity issues that enables you to take action in time to protect MongoDB from corruptions.

The events are generated in the following cases:



MongoDB Frequent Crashes

When the system experiences more than a certain number of unexpected MongoDB crashes in the stipulated time period.

MongoDB Connectivity Issues

When the system experiences 20 incidents of disk latency higher than 1 second during a period of 3 days, for the disk storing the MongoDB data.

MongoDB is disabled due to repetitive crashes

When MongoDB is disabled after a certain number of unexpected MongoDB failures in the stipulated time period

MongoDB is disabled due to high latency to the data disk

When the MongoDB is disabled because of high latency on the data disk.

MongoDB is disabled because not enough disk space is available

When the MongoDB is disabled if there is not enough disk space.

MongoDB is replicating or rebuilding index, please wait

When the MongoDB is temporarily disabled when it is replication of rebuilding index.

In these cases, the Mirage Management server stops its MongoDB instance immediately.

A critical event is generated and the status of the Management Server changes to “Mongo service is Down” in the Management Servers tab.

To bring Management Server back to its normal state, use the Start command from the Management Servers tab in the Mirage Web Console.

If your configuration has only one Mirage Management Server, the Web Management displays a red banner with the following message:

Your system has a single active Management Server. Set up multiple Management Servers to prevent data loss in case the Management Server fails. Important: Do not clone the VM.

If your configuration has only one Mirage Management Server, and if any one of the management servers is down or disabled, the Web Management displays a red banner with the following message:

Some of the Mongo nodes on your system are down, if all nodes are down Mirage operations will fail. View the Management Servers tab for details. After resolving the issue start the Management Server via Management Servers tab. For more information refer to KB2144975.