Replication on demand helps in the scenario where each node works with different pieces of data and will be combined at logical steps.
对于每个节点处理不同部分数据并在逻辑步骤中整合这些数据的情况，随需复制是很有帮助的。
AS with the other hardware replication technologies, although the IASP is not accessible on the backup node while its actively replicating, the node itself is available to do other work.
与其他的硬件复制技术一样，在主动复制时，尽管备份节点上的IASP是不可访问的，但是节点本身对于完成其他工作是可访问的。
Replication can proceed in a peer-based approach where registry updates from all other nodes can be obtained from any one node.
复制可以以一种基于对等的方式进行，在任何一个节点上都可以获得在其它所有节点上发生的注册中心更新。
With asynchronous replication, order is preserved, but the write is allowed to complete without waiting for an acknowledgement from the target node that the write has been received there.
对于异步复制，顺序是一样的，但是无需等待目标节点确认已经收到写入操作，就可以完成生产节点上的写入操作。
During failover, one of the children becomes the master node and all replication starts flowing from that node.
在故障恢复过程中，其中一个子节点会成为主节点，而所有复制将从该节点开始。
With synchronous replication, the write on the production node does not complete until it has been received on the target node, so you are guaranteed identical copies on each side.
对于同步复制，目标节点不接收到此写入操作，生产节点上的写入操作就无法完成，这样可以保证两边的复制一致。
This is a variation of replication strategy where the regular commits are for the current node and the code can trigger replication at a logical point.
这是复制策略的一种变化，其中常规提交是针对当前节点的，而这个节点可以逻辑点触发复制。
The advantage of replication is that reads are always local, as everybody has the data, and there is no re-balancing going on when a new node joins or an existing node leaves the cluster.
这种复制的优点在于它通常只在本地节点读取数据，因为每个节点都拥有这些数据；另外，当群集中有新节点加入或者需要移除现存节点的时候，它也不需要重新进行负载均衡。
A DB2 redundant node can be set up with data replication.
可以设置DB 2冗余节点来进行数据复制。
The master node must have connectivity with all the servers in the Enterprise Replication topology.
主节点必须和EnterpriseReplication拓扑中的所有服务器相连接。
The apply TAB provides information on replication apply activity for the selected node.
Apply选项卡提供关于选中节点的复制应用活动的信息。
Automatic replication with automatic fail-over upon node crash.
自动复制，并且在节点崩溃的时候能够自动恢复。
UDDI Version 1 only supported a file-based replication scheme whose complexity grew as n-squared with the number of registry node implementations participating within a UDDI registry.
UDDI版本1仅支持基于文件的复制模式，随参与到uddi注册中心中的注册中心节点实现数目的增长，其复杂程度以n的平方增长。
JBossCache framework only supports the "replication" mode (where every node in a cluster replicates everything to every other node).
JBossCache框架只支持“复制”模式(就是在群集里面的每一个节点都向其它节点复制所有的数据)。
In asynchronous mode, the write transaction is acknowledged after the write data is stored on the local node's storage; the replication of the data to the peer node occurs in the background.
在异步模式下，写数据被存储到本地节点存储中之后，写事务被认可；对等节点中的数据的副本出现在后台中。
As the complement of early replication, the instant replication is used to balance load between nodes with the source node reserves more resource to server the local user.
即时复制是早期复制的补充，可进一步地平衡服务器节点之间的负载，同时使得节点保留更多的资源服务本地用户。
As the complement of early replication, the instant replication is used to balance load between nodes with the source node reserves more resource to server the local user.
即时复制是早期复制的补充，可进一步地平衡服务器节点之间的负载，同时使得节点保留更多的资源服务本地用户。
应用推荐