
PeriView Reference Manual
Page 194 # P0602566 Ver: 2.7
Supporting Data Replication in MMDP
MMDP has a built-in capability to replicate the configuration of all data providers
amongst other PeriView Data Providers, provided that they are not configured as
Service MMDPs. Data replication occurs only amongst consolidator MMDPs.
Data Replication occurs in the following scenarios:
• A user changes the MMDP configuration data on one MMDP which is
connected to at least one more MMDP, acting as a consolidator.
or,
• A user requests to import a Consolidator MMDP's configuration and the
operation completes successfully (the imported MMDP receives the merged
configuration which includes not only itself, but also the configuration data of
all the other MMDP that the user was connected to).
In order for data replication to occur, the following conditions must be satisfied:
• The MMDPs must be able to establish a network connection between them.
• The MMDP that sends the update (called the replicator) has newer
information than the MMDP that receives the update (called the replicant).
If updates are done on a replicator, and it is not connected to a replicant, the updates
are cached until such time when the replicator is able to connect. Under most
circumstances, both machines will be up and running, and replication will occur
within one second.
Data replication in MMDP implies that the data stored and displayed through the
clients (PeriView) is consistent and correct at all times. To better understand
replication, consider the following scenario:
The user is using PeriView to connect to the MMDP, UNITEDSTATES.
Additionally, the user has a second instance of the PeriView client connected
to the MMDP, ISRAEL.
Komentarze do niniejszej Instrukcji