Data Replication In Bi-directional, One-to-many, Many-to-one and
Many-to-many Schemes
Real-time replication copies only the modified portion of a file. So no matter
how many databases you have or how large the size of them, after the initial
file sync, all real-time data replication should take only the minimal system
resources and network bandwidth.
Four types of
clustering structures for real time data replication can be set using
ClusterReplica Enterprise 2.0.
| 1. Bi-directional data replication
In this setting, the two "master" servers are both also
function as a Replica Member to receiving data from the other.
Typically, the two servers are a MS SQL server and an IIS web
server. Creating a clustering for data protection and High Availability
purposes without additional computers.
|
 |
| 2. One-to-many data replication with Failover
In this setting, the two Replica Member stations are used for local and
remote data backup.
The Primary master can be an IIS web server and a File server that
needs to be alive 24x7. At the same time web programmers updates files on
it daily.
|
 |
| 3. Many-to-one data replication only
This setting can involve a combination of
- A MS SQL server and an IIS web server
- A MS QL server and a File server
- A File server and an IIS web server
Both servers need to backup data for data protection. The Data Version
Management function allows File server end-users to self manage their
working files.
|
 |
| 4. Many-to-many data replication
This is a more comprehensive setting. While the Primary Master manages
the entire clustering structure, a Repli-Master server has its own
sub-structure to replicate data to a local and a remote server for data
protection.
Typically in this setting, an IIS web server is installed as the
Primary Master so that it can utilize Failover for High Availability.
The Repli-Master is the MS SQL server that contains all kinds of
databases and requires extra measure on data protection.
|
 |
Back to ClusterReplica
Enterprise page
|
