Replication Strategy
Several options for replication strategy are available. Each has advantages and disadvantages. You need to decide on the best strategy for your environment. For example, you might use different configuration options that are based on available space, application, criticality of data, and legal requirements. Consider your environment, applications, availability needs, storage growth patterns, and recovery windows to create a replication strategy that best serves your needs.
The Nimble array relationships are based on the direction of replication. The source of the volume collection that is being replicated is the upstream replication partner. The destination is the downstream replication partner. A volume source that is upstream to one partner can be downstream to another. Downstream partners can become upstream partners by sending data to other replication partners and by replicating replicas.
One-to-One Replication
Basic replication involves replicating volumes from one array to another based on the protection schedules configured for their associated volume collections. Each volume collection always replicates to the same replication partner. In this scenario, the second Nimble array could be used strictly for disaster recovery.
- Network
- Single volume assigned to the Hourly volume collection
- Multiple volumes assigned to the Daily volume collection
- Replica of volume in the Hourly volume collection
- Replicas of volumes in the Daily volume collection
Reciprocal Replication
Reciprocal replication involves replicating volumes that originate on two separate arrays to each other. Volumes on one Nimble array are replicated to a second Nimble array, and volumes on the second Nimble array are replicated to the first array. Each array acts as a disaster recovery option for the other. Reciprocal replication is sometimes called mutual replication.
- Network
- Multiple volumes assigned to the SQL volume collection
- Replicas of volumes in the Outlook volume collection
- Replicas of volumes in the SQL volume collection
- Multiple volumes assigned to the Outlook volume collection
Many-to-One (Centralized) Replication
You can use one Nimble array as a centralized replica for volumes that originate on several other Nimble arrays.
- Network
- Single volume assigned to the Daily volume collection
- Multiple volumes assigned to the SQL volume collection
- Multiple volumes assigned to the Hourly volume collection
- Replicas of volumes in the SQL volume collection
- Replicas of volumes in the Hourly volume collection
- Replicas of volumes in the Outlook volume collection
- Replicas of volumes in the Datastore1 volume collection
- Replica of volume in the Daily volume collection
- Multiple volumes assigned to the Outlook volume collection
- Multiple volumes assigned to the Datastore1 volume collection
Many-to-Many Replication
Many-to-many replication involves replicating volumes on the same array to multiple replication partners.
- Network
- Multiple volumes that are assigned to the SQL volume collection
- Single volume that is assigned to the Daily volume collection
- Replicas of the volumes in the Hourly volume collection
- Replicas of the volumes in the Datastore1 volume collection
- Replicas of the volumes in the SQL volume collection
- Multiple volumes assigned to the Datastore1 volume collection
- Multiple volumes assigned to the Outlook volume collection
- Multiple volumes assigned to the Temporary volume collection
- Replicas of volumes in the Outlook volume collection
- Multiple volumes that are assigned to the Hourly volume collection
- Replica of volume in the Daily volume collection
- Replicas of the volumes in the Temporary volume collection