Peersync Standard Server Exchange-High-Availability

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 Solutions provide 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.

• PeerSync is installed on the source Exchange Server.
• Replicated Store is not currently mounted and running on target servers.

• 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.

• PeerSync is installed on the source Exchange Server.
• Additional ByteReplicator service is installed on the destination server(s).