Follow

Replication systems connectivity overview

To replicate data from one InfiniBox system to another, the user must define Replication Network Spaces on each of the InfiniBox systems to connect the two systems. Then the user creates a bi-directional Replication Link that defines the connection between the two Network Spaces.

The same link can be used for all replication types.

Access control for connecting between systems

The replication provisioning commands are only accessible from the InfiniBox systems that participate in the replication.

All of the user operations relevant for Replication Network Spaces and Replication Links require the Admin user role.

Admin permissions are required on both local and remote systems. When running replication operations, the local system tries to log into the remote system with the same credentials. If access is denied, the system asks the user to provide credentials to the remote system.

Replicating data from the local system to the remote system can be carried out by both Admin and Pool Admin user roles.

  • The Admin user can replicate any of the system's datasets that are available for replication.
  • The Pool Admin can replicate only datasets from the relevant pool.

Defining a replication network space

For more information, refer to InfiniBox Best Practices Guide for Setting Up the Replication Service.

The Network Space groups' ethernet interfaces with all three InfiniBox nodes to assure a reliable and redundant replication service between InfiniBox systems.

The Network Space definition requires the user to define minimum of 4 or 7 IPs depending on the replication type.

  • All replication types' network space
    Requires a minimum of 7 IPs

    • The first IP is used as the control IP.
    • 3 IP addresses are used as data IPs for Sync/Active-Active replication.
    • 3 to 6 IP addresses are used as data IPs for Async replication. (3 IP addresses are enough, but 6 IP addresses allow for a smooth failover in the event of a node unavailability.)
  • Async Only network space
    Requires a minimum of 4 IPs

    • Choosing Async Only when defining a network space assigns all the IP's to the async replicas. You cannot define Sync/Active-Active replicas on links using this network space.
    • The first IP is used as the control IP.
    • 3 to 6 IP addresses are used as data IPs for Async replication.

The control IP transfers the replica configuration and management commands between the local and remote systems.

Firewall ports that need to be open:

  • Control - TCP 80, TCP 443
  • Data - TCP 8067

The link is the entity that connects the local InfiniBox system to the remote system using predefined Network Spaces on both systems.

For link creation, the user must have Admin user role permission on both local and remote systems.

The link is bi-directional. It can be created on either of the systems by identifying the second system via the control IP address.

Link states 

The replica link can be in one of the following states:

  • Connected - All of the IP addresses are reachable
  • Degraded - Not all of the IP addresses are unreachable 
  • Disconnected - None of the data IP addresses are available
  • Unknown - The remote management could not be reached or local async service is not available

To change IPs on a linked replication network space, detach the link from the network space, and then either re-attach it after the network space is updated or attach it to a new network space.

  • Detaching a link - When the link is detached, the relationship between the link and the network space is disconnected. All of the replicas that use the link are automatically suspended.
  • Attaching the link - When the link is attached, all of the replicas that were suspended as a result of the detach operation will be automatically resumed.
    Replicas that were suspended prior to the detach will not be automatically resumed.
Was this article helpful?
0 out of 0 found this helpful

0 out of 0 found this helpful

Last edited: 2022-08-06 08:12:43 UTC

Comments