Table of Contents | ||
---|---|---|
|
...
The following table describes the data entry fields in the dialog box.
ID (existing feeds) | Read-only; system-assigned identifier | ||
---|---|---|---|
Status (existing feeds) | Read-only; the current feed processing state. | ||
Name | The name attached to a feed. | ||
Scope | The feed filters that were selected for the replication feed. The object is replicated to the domain(s) indicated in this field.
The field value allows pattern matching with the Python regular expression (RE) syntax, so multiple domain names can be matched. The exception to the RE matching is that the "{m,n}" repetition qualifier may not be used. An example domain list value using RE is:
| ||
Target Remote Cluster Name | The configuration setting for the target cluster (the configure the Gateway setting | ||
Proxy or Host(s) | The IP address(es) or host name(s) of either:
Enter each address with a comma or space between them to enter two or more node IP addresses. | ||
Port | Defaults to 80. Allows specifying a custom port for the remote cluster. | ||
Replication Mode | Defaults to Direct POST. Choose replication via direct POST (recommended) or bidirectional GET. Switching modes does not require a feed restart. (v9.6) For best performance, choose direct POST replication, which can go through Gateway. GET replication is the legacy method, which may be needed for application compatibility or networking requirements. | ||
Threads | Replication via direct POST. The default replication speed (20 simultaneous threads) is best for same-sized clusters with minimal replication backlog. When processing backlog, the new default push thread count is 20 per node (in releases prior to v15.0, it was 6 per volume) Reduce the threads to avoid overwhelming a smaller target cluster. For faster replication against a backlog, increase the threads temporarily and monitor bandwidth and cluster performance, as boosting the speed stresses both clusters. | ||
SSL Server | Replication via direct POST. Defaults to none. Enable Require trusted SSL if replicating over an untrusted network; Allow untrusted SSL is available but not intended for production systems. (v10.0) | ||
Remote Admin Name/Password | Inherit from source cluster: Uncheck the enabled box, if the remote cluster user name is different from the source cluster name in the same realm. Then enter: User/Password credentials
|
Propagate Deletes
Info |
---|
The legacy option Propagate Deletes is deprecated; it existed to allow setting a target cluster to preserve all deleted objects. This need is now covered by Object Versioning; historical versions of deleted objects can be accessed to recover mistakenly deleted content. Versioning to the target cluster serving as the archive can be limited, to minimize space usage. (v11.1) Note these restrictions and behaviors if an existing feed has this option specified:
|
...