13.07.2015 Views

EMC Avamar 6.0 for Exchange Guide - EMC Community Network

EMC Avamar 6.0 for Exchange Guide - EMC Community Network

EMC Avamar 6.0 for Exchange Guide - EMC Community Network

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

System requirementsINTRODUCTIONCCR is designed to provide high availability <strong>for</strong> <strong>Exchange</strong> Server 2007 Mailboxservers by providing a solution that:• Has no single point of failure• Has no special hardware requirements• Has minimal shared storage requirements• Can be deployed in one or two datacenter configurationsCCR uses the database failure recovery functionality in <strong>Exchange</strong> Server 2007to enable the continuous and asynchronous updating of a second copy of adatabase with the changes that have been made to the active copy of thedatabase. During installation of the passive node in a CCR environment, eachstorage group and its database is copied from the active node to the passivenode. This operation is called seeding, and it provides a baseline of thedatabase <strong>for</strong> replication. After the initial seeding is per<strong>for</strong>med, log copying andreplay are per<strong>for</strong>med continuously.In a CCR environment, the replication capabilities are integrated with theCluster service to deliver a high availability solution. In addition to providingdata and service availability, CCR also provides <strong>for</strong> scheduled outages. Whenupdates need to be installed or when maintenance needs to be per<strong>for</strong>med, anadministrator can move a clustered mailbox server (called an <strong>Exchange</strong> VirtualServer in previous versions of <strong>Exchange</strong> Server) manually to a passive node.After the move operation is complete, the administrator can then per<strong>for</strong>m theneeded maintenance.CCR can be combined with standby continuous replication (SCR) to replicatestorage groups locally in a primary data center (using CCR <strong>for</strong> high availability)and remotely in a secondary or backup datacenter (using SCR <strong>for</strong> siteresilience). The secondary datacenter could contain a passive node in afailover cluster that hosts the SCR targets. This type of cluster is called astandby cluster because it does not contain any clustered mailbox servers, butit can be quickly provisioned with a replacement clustered mailbox server in arecovery scenario. If the primary datacenter fails or is otherwise lost, the SCRtargets hosted in this standby cluster can be quickly activated on the standbycluster.System requirementsThis topic lists the supported configurations and hardware requirements that mustbe satisfied in order to successfully install and deploy the <strong>Avamar</strong> <strong>Exchange</strong> Clientbackup and recovery solution at your site. The supported configurationsinstallation package column also lists the correct <strong>Avamar</strong> <strong>Exchange</strong> Client softwareinstallation package required <strong>for</strong> that specific <strong>Exchange</strong> version, host plat<strong>for</strong>m andoperating system.<strong>EMC</strong> AVAMAR <strong>6.0</strong> FOR EXCHANGE GUIDE 11

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!