当按住鼠标右键拖动节点时复制节点。
这个特性仅在复制节点和在随需存储策略的复制中支持。
This feature is needed only for replicated nodes and replication on demand storage strategies.
所有缓存和内存数据都可以重新设计为基于存储的复制节点。
All caching and in-memory data can be redesigned as replicated nodes based storage.
LockManager保证在所有复制节点上具有相同的状态视图。
The LockManager ensures the same view of status across all replicated nodes.
复制节点：数据存在于不同的节点上，能够快速地复制到其他节点。
Replicated nodes: Data is available at different nodes and is replicated immediately to other nodes.
Replicator保证数据会作为一个分布式事务持久化到所有复制节点中。
The Replicator ensures that the data is persisted in all the replicated nodes as a single distributed transaction.
Replicator只有在使用了复制节点和随需存储复制的策略时才会被使用。
The Replicator is used only if replicated nodes and replication on demand storage strategies are used.
复制节点策略指的是，相同的数据存在于不同的节点上，并且能够快速地复制其他节点。
The replicated nodes strategy implies that the same data is available at different nodes and is replicated immediately to other nodes.
如果两台服务器都发生了故障，就使用到第三个灾难恢复服务器集的副本将应用程序引导至复制节点。
If both servers fail, the applications are directed to the replica nodes using replication to a third disaster recovery server set.
查询定义了输出文件内容(如果它们有实际值的话)，或者在输出文件中复制节点，就像它们在输入文件中发生的一样。
The queries either define the output document content (if they have a textual value), or replicate nodes in the output document as often as they occur in the input document.
另外，您可以复制和粘贴节点来快速构建您的示意图。
Moreover, you can just copy and paste nodes to quickly build your map.
主复制为模板提供了完全数据库复制，包括在目标节点上自动创建表的能力。
Master replicates provide the template the capability to do complete database replication including automatic creation of tables on target nodes.
主复制要求所有节点通过访问主节点来获得关于表、列和主键的字典信息。
Master replicates require all nodes to access the master node to obtain the dictionary information about tables, columns, and primary keys.
如果那些表不存在，那么可以通过另一个选项使用主复制在目标节点上创建这些表。
You also have the option to create tables on target nodes using master replicates if those tables are not already present.
将目录与文件从主节点复制到克隆节点。
Copy directories and files from main node to the clone node.
如果原始集群节点出现问题(故障转移情况)，则会话数据还必须复制到其他的集群节点。
The session data also needs to be replicated to other cluster nodes, in case the original cluster node goes down (failover scenario).
可以设置DB 2冗余节点来进行数据复制。
如果成功，将把配置复制到集群中的其他节点。
When successful the configuration will be copied to the rest of the nodes in the cluster.
该命令不会将这些节点添加到主复制。
This command does not add these nodes to the master replicates.
在故障恢复过程中，其中一个子节点会成为主节点，而所有复制将从该节点开始。
During failover, one of the children becomes the master node and all replication starts flowing from that node.
模板可以使用主节点上的主复制字典在其他节点上创建表，以确保大量节点之间模式的一致性。
Templates can use the master replicate dictionary from the master node to create tables on other nodes to ensure consistent schemas among large Numbers of nodes.
对于同步复制，目标节点不接收到此写入操作，生产节点上的写入操作就无法完成，这样可以保证两边的复制一致。
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 function takes the source node and copies it over as a child under the destination node.
大多数IBMi高可用性产品都是监视对象的变更，将这些变更复制到备份节点，然后应用于备份节点上的对象。
Most IBM I high availability products monitor for changes to an object, replicate those changes to the backup node, and then apply the changes to the object on the backup node.
版本2能满足数目更多的参与节点，它们相互复制。
Version 2 addresses the needs of a larger number of participating nodes that replicate with each other.
保存更改时以及配置更改复制到节点时，配置映像将发生更改。
A configuration image changes when configuration changes are saved and when the configuration changes are replicated to a node.
在克隆节点上复制这些文件。
接下来，调用CAS 内置函数，把新的节点复制到top位置。
Next, you invoke CAS and copy the new node to the top location.
Apply选项卡提供关于选中节点的复制应用活动的信息。
The apply TAB provides information on replication apply activity for the selected node.
Apply选项卡提供关于选中节点的复制应用活动的信息。
The apply TAB provides information on replication apply activity for the selected node.
应用推荐