This section describes how to configure Feeds in your Netmail Store cluster network.
Content Router is an object-routing engine in the Netmail Store storage cluster that uses the Publisher Service API to distribute data to one or more targeted Netmail Store clusters subscriber running the Replicator Service API. Content Router can replicate specific content using complex filters based on object metadata and integrate objects using complex rules.
On the source cluster, Publisher processes all UUIDs or names stored in a cluster, filters them based on object metadata, and publishes the results to the remote subscribers. On the targeted cluster, Replicator retrieves the UUIDs or names from the remote Publisher service and coordinates object replication to the cluster.
Content Router provides a backup solution for environments that do not have a reliable connection with the targeted Netmail Store cluster. In these environments, you can run Content Router at night after normal business hours when you have available network bandwidth.
Content Router is a separate product that can be installed separately or as part of the Cluster Services Node (CSN). Content Router requires separate hardware and configuration. See the CSN Installation and Configuration Guide for more information about managing your storage cluster.
Selecting a Replication Plan
Use Content Router in your replication plan when:
- You need a basic replication solution that replicates objects over time.
- You need to replicate specific objects in your source cluster.
- Your remote DR cluster is not available during peak business hours.
- You normally run your replication tasks at night.
- You need to replicate subsets of your objects using complex rules to identify groups of objects that match a particular metadata pattern.
Use Replication Feeds in your replication plan in these situations:
- You need a deterministic replication solution that verifies object replication to the targeted cluster as soon as possible.
- You need to replicate all objects in your source cluster or domain.
- Your remote DR cluster is available during peak business hours.
- You want continuous replication to keep up with source cluster intake.
- You do not need to replicate a subset of objects based on metadata.
These are the implementation differences between Content Router and Feeds:
|Content Router||Replication Feeds|
Provides a basic solution that replicates objects to the targeted cluster over time.
Provides a deterministic solution that verifies object replication to the targeted cluster as soon as possible.
Replicates specific objects in your source cluster.
Replicates all objects in your source cluster or domain.
Replicates objects when your target cluster is not always available.
Replicates objects when your target cluster is always available.
Can replicate objects during off-peak hours (with the appropriate configuration).
|Can replicate objects using available bandwidth.|
Uses Publisher and Replicator APIs to move content from the source to the target cluster.
Uses an intermittent connection (such as HTTP) to move content from the source to the target cluster.
Provides a general API for enumerating objects in the source cluster.
|Provides no externally supported API.|
Implementing a Replication Feed
You implement Feeds through the Cluster Settings page. When you click Settings in the Netmail Store Admin Console, the Cluster Settings page appears, enabling you to make runtime changes to several configuration parameters in your cluster.
When you save your settings for the first time, the Cluster Settings UUID field displays the universal unique identifier (UUID) of the aliased object that contains the cluster settings. All changes will persist in the cluster across reboots.
The Add Replication Feed dialog box allows you to enter the configuration settings for a replication feed to a target cluster.
The following table describes the data entry fields in the dialog box.
The name you attach to this feed.
This name will appear in the Feeds row in the Settings page.
|Feed Domain List|
The feed filters that you select for your replication feed. The object will only be replicated to the domain(s) you indicate in this field.
You can also enter a Python regular expression (regex) in the field to match specific domains.
All domain names or patterns must be separated by commas.
|Propagate deletes||Select this checkbox if deletes should be propagated to the remote cluster.|
Remote Cluster Proxy or Cluster Host(s)
The IP address of either:
To enter two or more node IP addresses, enter each address separated by a comma with no spaces.
Note: If the target cluster is much smaller than the source cluster, lower the
Remote Cluster Name
The configuration setting for your target cluster (for example, the
Remote Cluster Administrative User Name
The administrative user name of the target cluster.
Enter a value in this field only if the remote cluster user name is different from the source cluster name in the same realm.
Remote Cluster Administrative Password
The administrative password of the target cluster.
Enter a value in these fields only if the remote cluster password is different from the password on the source cluster in the same realm.
To add a replication feed:
1. Open the Netmail Store Admin Console and click Settings.
2. In the Feed Name row, click Add Replication.
3. When prompted for authentication, enter your administrator name and password.
4. In the Add Replication Feed window, complete the fields as described above.
5. Click Add.
Your new feed appears in the Feed Name row in the Cluster Settings page and propagates to the targeted nodes in your cluster within 60 seconds.
6. Click Update.
A Success dialog box appears.
7. Click Close.
Deleting a Replication Feed
When you delete a feed, it frees source cluster resources. This process does not affect the objects
previously pushed to the target cluster.
To delete a feed:
1. In the Netmail Store Admin Console click Settings.
2. In the Cluster Settings window, locate the Feed Name section.
3. Identify the feed you want to delete and select the corresponding Delete checkbox.
4. Click Update.
A Success dialog box appears.
5. Click Close.
The deleted feed is removed from the remaining cluster nodes within 60 seconds.