Installation Instructions

 Multiple Windows servers running the mobilEcho File Access Server service, with one of

those Windows servers also running the mobilEcho Client Management service

4. Multiple mobilEcho Servers front-ended by a load balancer

 One standalone Windows server running the mobilEcho Client Management service, and two

or more Windows servers running the mobilEcho File Access Server service only, front-ended

by a load-balancer.

5. Windows Failover Cluster

 Supported in version 5.0.3 or newer.

 A multi-node Windows Failover Cluster running mobilEcho on 1 or more active/active or

active/passive virtual servers.

Important notes on Scenario 4 – Load Balanced mobilEcho File Access Servers

If you are running multiple mobilEcho File Access Servers front-ended by a load balancer, each of these

mobilEcho servers must be kept configured with identical mobilEcho Volumes, so that users can connect to any

node to access their files. The most common way to maintain identical Volumes on these sets of load balanced

servers is to replicate the mobilEcho Volumes settings, which are stored in the registry in mobilEcho 4.5 or

earlier.

In Acronis Access, the Volumes settings have been moved into a SQL database. If you upgrade to Acronis Access,

your existing scripted registry updates used when adding new volumes to your mobilEcho servers will cease to

work. A new feature has been introduced in 5.1 that allows groups of load balanced Gateway servers to be

automatically administered from within the Acronis Access Server console. This feature eliminates the need to

replicate registry settings and script updates to your servers. Adding a new data source (volume) to your servers

is a one step process that is handled automatically by the management console. For more information, visit the

Cluster Groups article.

Important notes on Scenario 5 – Windows Failover Cluster

Installing and upgrading mobilEcho on a Windows Failover Cluster is a complicated process. The architecture

changes introduced in mobilEcho 5.0 require change to the way mobilEcho works on Windows Failover Clusters.

For instructions on installing Acronis Access on a cluster, visit the Installing Acronis Access on a cluster (p. 16)

article.

For instructions on upgrading a mobilEcho cluster to a Acronis Access cluster, visit the Upgrading Acronis Access

on a cluster (p. 133) article.

In this section

Upgrading a single mobilEcho server without Client Management configured 69

Upgrading a single mobilEcho server with Client Management enabled 82

Upgrading multiple mobilEcho servers with Client Management ........... 98

Upgrading a single mobilEcho server with Client Management enabled and an activEcho server 103