Administrator Guide

Change the Local or Remote Networks for a Replication Partnership
Change the local or remote replication network or IP address for a replication partnership. NAS volumes can be replicated only
between tenants that are mapped on the local and remote FluidFS clusters.
1. In the Storage view, select a FluidFS cluster.
2. Click the File System tab.
3. In the File System view, click Replications.
4. Click the Remote Clusters tab, select a remote cluster, and then click Edit Settings.
The Edit Remote NAS Cluster Settings dialog box opens.
5. Click Add.
The Add Tenants Mapping for Replication dialog box opens.
6. Select a tenant from the Local FluidFS Cluster drop-down list.
7. Select a tenant from the Remote FluidFS Cluster drop-down list.
8. Click OK.
Delete a Replication Partnership
When you delete a replication partnership, the replication relationship between the source and target FluidFS clusters is discontinued.
When deleting a replication partnership, ensure that both systems are up and running. If both systems are up, the replication
partnership is deleted on both systems. If one of the systems is down or unreachable, the partnership is deleted only on the system
that is up. After the other system comes back up, the partnership must be deleted on that system as well.
Prerequisite
Replications between the replication partners must be deleted.
Steps
1. In the Storage view, select a FluidFS cluster.
2. Click the File System tab.
3. In the File System view, click Replications.
4. Click the Remote Clusters tab.
5. Select a remote FluidFS cluster and click Delete.
The Delete dialog box opens.
6. Click OK.
Replication Throttling
Replication throttling can ne-tune network bandwidth usage for replication of a pair of NAS volumes between two clusters.
Users can limit FluidFS replication bandwidth usage by:
• Lowering bandwidth usage during work hours and increasing bandwidth consumption during nighttime
• Increasing bandwidth usage during weekends
How Replication Throttling Works
Replication throttling:
• Creates a new system entity named QoS node and denes bandwidth allocation in KBps
• Denes usage percentage per hour of the week
• Binds a QoS (Quality of Service) node (network level) of outgoing trac to a replication. The average network usage should not
exceed the bandwidth allocation in a minute timeframe. The default is not to limit the bandwidth for replication.
Limitations
The following limitations apply to replication throttling:
• The maximum number of active outgoing replications is 10. If more than 10 replications are active, they are queued.
450
FluidFS Data Protection