Microsoft Exchange Replication through PeerSync

Identifying Needs for Microsoft® Exchange Replication

Before beginning the process of testing exchange replication solutions, it is necessary to identify first the goals and requirements of the replication process.

Exchange Store Replication can be used for disaster recovery, high availability, load balancing, local backup, duplication for analysis or testing, as well as many other uses. Identifying which uses your organization requires can help determine how tightly bound the solution must be to your needs. Beginning the process of defining these requirements is critical before asking how PeerSync can provide the right solution for Exchange Store Replication.

Understanding How PeerSync can provide Microsoft® Exchange Replication

PeerSync Professional Series provides the capability of replicating not only file and folder changes, but database changes as well. Utilizing the optional Embedded Open File Manager (EOFM), PeerSync can provide replication of current Exchange Store database files as well as transactions logs.

The guarantees provided by the PeerSync replication are:

• An accurate snapshot of the database files and transaction logs.

• No interruption of service to Exchange will occur.

• A minimum amount of resources will be used in the process.

Requirements for PeerSync Replication of Exchange Stores are:

• PeerSync is installed on the source Exchange Server.

• Replicated Store is not currently mounted and running on Target servers.

How PeerSync can transfer just the changes of Microsoft Exchange Store

PeerSync offers the ability to replicate the entire store during transfer, or just the changes portions. Utilizing the ByteReplicator feature, PeerSync can analyze the database to determine and transfer just the changed portions of the database.

The ByteReplicator functionality guarantees:

 • Every attempt will be made to transfer the minimum amount of data

necessary to make the replicated Exchange Store current.

• A minimum amount of resources will be used in the process.

Requirements for Byte-Level Replication of Exchange Stores are:

• PeerSync is installed on the Source Exchange Server.

• Additional ByteReplicator service is installed on the destination server(s).

The Role of PeerSync in the Replication of a Microsoft® Exchange Store

In order to configure Exchange Store, it is necessary to identify the location of the Exchange Store database files and transactions logs. These are generally located in the MDBData directory. This location will be the Source within a PeerSync Job. The Target location must be a local folder, mapped drive or UNC Path.

Additional configuration necessary can be found in the EOFM configuration (KBA-01045).

Please keep in mind that during the replication process, it is not necessary to shutdown any Microsoft® Exchange services on the source server.

The Role of PeerSync in the Restoration of a Microsoft® Exchange Store

During the replication of the Exchange Store by PeerSync, the destination data will be stored identically to the source data. This allows for restoration through PeerSync, through another tool, or manually. PeerSync can be used to restore a particular Exchange Store by selecting its Job in the Profiler Window and reversing the Source/Target in the Folder Selection Window. Additionally, the Restore Files Option should be enabled in the Alterations Window. Care should be taken to identify other data within that Job that should not be restored.

Once PeerSync is configured, the Source Exchange Server must be prepared by unmounting the Exchange Store. This can be done through the Exchange Management console. The Job can then be saved and launched to restore the data. PeerSync will then proceed to restore the database as well as transaction logs. The Exchange Store can then be mounted. Upon mounting the Store, Exchange will load the database as well as replay any necessary logs to bring itself to a current stable state.

The Role of PeerSync within your Organization

By providing efficient and fast replication of Microsoft® Exchange along with file replication, PeerSync continues to provide a critical line of solutions necessary for small, medium, and Enterprise organizations. PeerSync’s replication capabilities extend beyond Exchange into other packages such as Microsoft® SQL Server. We recommend visiting our site or contacting us directly for information regarding any other database packages.

Product(s): PeerSync

Version(s): All Versions