Support for New Microsoft Exchange Server Features

Arcserve Continuous Availability supports the following for Microsoft Exchange Server:

Microsoft introduces changes to the database hierarchy from Exchange 2010. The concept of a storage group was removed, and public folder databases and database management were moved to the organization level. With Exchange Server 2010 and 2013, database protection is provided by Database Availability Groups (DAG). Database Availability Groups are not supported in Replication or HA scenarios. When a Master or Replica is part of a DAG, the software displays a warning.

Note: CDP Repository is no longer supported.

Important! Due to this hierarchy change, you cannot create a database with the same name on the Master and Replica servers, even if the database is dismounted. To overcome this limitation, functionality has been built into the software that allows it to temporarily rename the database for switchover purposes.

With Arcserve Continuous Availability, replication and high availability protection was moved from the storage group level to the mailbox store level.

You can now connect to their mailbox through a server that fills the Client Access Server (CAS) role, while Exchange Server 2007 allowed users to connect directly to their mailbox server. In Arcserve Continuous Availability scenarios, the CAS server must be available in order to fulfill a client access request. The method you used to deploy CAS determines how the software protects the environment.

When the Master server also fulfills the CAS role, the Replica must do the same. You can decide at scenario creation time whether to confirm CAS on the Replica. If the Master server holds only the Mailbox role, CAS must be confirmed on the Replica at scenario creation time. When the master and replica are Exchange 2013 with CAS, you should configure NLB for the master and replica.