Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
maxLevel2

...

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.

Info

Gateway adminDomain

Do not create the same domain in two clusters; always create it in the source cluster and then replicate it to the target. A Gateway must use an independent adminDomain, at least temporarily, if the Gateway is in front of the target cluster. (CLOUD-2785)
Verify the source cluster’s adminDomain is included in the list of replicated domains if choosing to replicate specific domains.

  • Entire source cluster (global) — To replicate all objects in the source cluster, leave the default selection of Entire source cluster (global)

  • Only objects in select domain(s) — To replicate the objects in one or more domains, select the 'Only objects in select domain(s) option. In the text box that appears, enter one or more domains:

    • Enter the domain to replicate the objects within a specific domain.

    • Enter multiple domains separated by commas, and/or use pattern matching to replicate objects within multiple domains.

    • Enter domains to exclude them from replication. (v10.0)

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: .*\.example\.com
This matches both of these domains: accounting.example.com, engineering.example.com.

Image Modified
  • Include objects without a domain — To replicate any unnamed objects that are not tenanted in any domain, enable the option.

Target Remote Cluster Name

The configuration setting for the target cluster (the cluster.name parameter in the.cfg file of the target cluster).

configure the Gateway setting allowSwarmAdminIP when using Gateway as a target. See Gateway Configuration

Proxy or Host(s)

The IP address(es) or host name(s) of either:

  • One or more nodes in the target cluster. It is best to list all nodes in the target cluster, while Swarm follows redirects, it does not use those redirect targets for subsequent requests.

  • A reverse proxy host that routes to the target cluster.

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 networkAllow 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

  • The administrative user name of the target cluster.

  • The administrative password of the target cluster.

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:

  • With VersioningAlways propagate deletes when using Object Versioning in the cluster.

  • Without Versioning — The target cluster maintains deleted content carrying no verifiable indication of the deleted status if this option is disabled.

...