XenMobile is a great product that ensures that all mobile devices accessing your Network & Data, do so in a secure and manageable way without leaving your company open to data leaks and information accessed in an unmanaged and unsecured way. If you are thinking about implementing it in your organisation you really also have to think how you are going to make it highly available. In this article I have tried to bring together the options you have to provide HA for each XenMobile component.
If you have a virtual environment, you naturally would want to make all the VM’s that make up the XenMobile Solution highly available, but what are your options if the actually VM fails. Naturally you want to ensure that the all the VM’s are fully backed up and restorable in the event of a failure, but there are options for each component in the XenMobile suite it is worth thinking about.
Device Manager (MDM)
Albert Alvarez at Citrix, did a couple of handy videos of how you can cluster XenMobile Device Manager for HA.
Configuring HA Clustering for Citrix Xen Mobile Device Manager Part 1
Configuring HA Clustering for Citrix Xen Mobile Device Manager Part 2
Again Albert has come up with some great videos on how you can provide HA for the Application Controller. The Application Controller is a virtual appliance that has the ability to provide HA built in.
Making your XenMobile Deployment Enterprise Ready – HA Clustering part 1
You need an SQL Database for the Device Manager, and naturally this need to be made highly available, how you actually do this will depend on your environment, but probably the best option is mirroring between 2 SQL Servers.
Taken from Citrix eDocs:
“The recommended best practice is to install at least two StorageZone Controllers. When you install the first controller, you create a StorageZone. When you install the second controller, you join it to the same StorageZone. StorageZone Controllers that belong to the same StorageZone must use the same file share for storage.
In a high availability deployment the secondary servers are independent, fully functioning StorageZones Controllers. The StorageZones control subsystem randomly chooses a StorageZone Controller for operations. If the primary server goes offline, you can easily promote a secondary server to primary. You can also demote a server from primary to secondary.
You can configure multiple external public addresses, each associated with a different StorageZone Controller.”
As you can see configuring HA for Sharefile is a fairly simple process actually handled by Sharefile.