Home > Windows > Exchange
Enquire Search Register Secure Login
close
Login...
Please enter your username and password to gain access to the locked areas of the site:


Edit Your Details
To amend, simple re-edit your details below and click 'Update'.
Search...
Please type a keyword you would like to search for and then click 'Search...'
Search Results...
Need to Contact Us?
Please complete the boxes below and click 'Ok' to submit.

Disaster Recovery and High Availability
for Business Critical Applications

Skip Navigation Links
Home
Vacancies
What We Do
FAQs
Who We Are
Solutions
Our Customers
Contact Us
Events
sitemap
Windows
Linux
Data Replication
Disaster Recovery
Virtualisation
Scroll up
Scroll down
Articles of Interest
Exchange Case Study
OM Cabot casestudy
Read More
More Exchange Info
Related Topics
Exchange
IIS
Oracle
SQL Server
Bespoke Applications
SAP
Data Replication
Windows File Server
Exchange High Availability and Disaster Recovery
Exchange servers present particular challenges when planning disaster recovery and high availability.

For a seamless recovery of your Exchange servers, SteelEye Life Keeper from Open Minds guarantees to provide you with a complete disaster recovery solution ensuring that you maintain business continuity. Our high availability solutions will grant continuous data protection providing data replication as well as the monitoring of all your Exchange servers to ensure failover through the Java GUI.

Complete protection of Exchange Servers

Recovery of Exchange servers needs to be managed in the context of Active Directory servers, Exchange Logs and Exchange Data.
LifeKeeper for Exchange is available for all versions of Exchange without the need for Enterprise edition or shared storage. It can be used with all types of storage incuding SAN, NAS, iSCSI etc.

Real-time replication of Exchange data and logs over a LAN or WAN
Replication is real-time and can be synchronous or asynchronous. Replication can be to multiple targets making a 3-node solution with a local and remote backup possible.

Failover of Exchange servers

LifeKeeper for Exchange monitors Exchange server system resources and services. When a failure occurs, a recovery is initiated. By default a local recovery is attempted before a failover to a backup system is performed. A manual failover can also be performed for system maintenance activities.
A failover does not involve any reconfiguration of clients.

Failback of Exchange servers
Once a failover occurs and the system has been recovered, data is resynchronised backwards to the previously live server. When the data resynchronisation is complete, the system can be returned to service without any further disruption to the users. Bandwidth is used effectively due to data replication features which allow compression of data.

Spam filters/ Blackberry and mobile devices

Spam filters and Blackberry/mobile devices can be incorporated easily into this solution. Many of our customers have both Blackberry and anti-spam filters with their Exchange servers.

Installing the solution
Open Minds will help you to plan, setup and deploy your Exchange recovery solution on your servers or systems. Or, we can provide you with training and consultancy as you require, to help you implement a fully working Exchange recovery for your servers.

2-node Exchange solution
Replication of Exchange data and logs, and monitoring of Exchange services takes place continuously. On failure, all the users are migrated to the backup Exchange server in the Active Directory. Enabling the users to access their mail store from the backup server.




















Local and remote recovery - without shared storage
This is similar to above, except there is a local and remote backup node. When there is break in service due to hardware failure, or inoperability of Exchange services, a local recovery takes place. If, however, there is a site disaster, then a recovery to the remote backup node takes place.



















3-node Exchange solution - with shared storage
Shared storage is used locally while data mirrors to the remote backup server. Again, a local failover occurs on server or service failure, and a remote failover occurs on site disaster.