Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Dell PowerScale SyncIQ: Architecture, Configuration, and Considerations
Executive summary Introduction Deployment topologies Use cases Architecture and processes Data replication Configuring a SyncIQ policy Impacts of modifying SyncIQ policies SyncIQ performance rules SnapshotIQ and SyncIQ SyncIQ design considerations Failover and failback Superna Eyeglass DR Edition SyncIQ and CloudPools SyncIQ security SyncIQ bandwidth reservations Monitoring, alerting, reporting, and optimizing performance Administration SyncIQ replication and data reduction 16 TiB large file support and SyncIQ implications OneFS version compatibility SmartLock compatibility Conclusion Appendix A: Failover and failback steps Appendix B: SyncIQ encryption with self-signed certificates Appendix C: Configuring cascaded replication Appendix D: Configuring custom replication
Overview
Appendix E: Technical support and resources

Overview

Overview

  • The steps provided in this appendix provide an example of configuring a custom replication, combining the cascaded and one-to-many topologies. For this example, the steps configure the implementation in the following figure.

    Figure 45.    Cascaded and one-to-many replication

    The configuration described in this appendix triggers replication from ‘Cluster A’ only when a snapshot of the specified source directory on ‘Cluster A’ is taken. For more information about this option, see Whenever a snapshot of the source directory is taken and SnapshotIQ and SyncIQ. To implement the cascaded replication in Figure 45, log in to CLI of each cluster, and perform the following:

    1. On ‘Cluster A’, configure replication from ‘Cluster A’ to ‘Cluster B’ based on when a snapshot of the source directory is taken:

    IsilonClusterA# isi sync policies create --name=pol_a_b sync --source-root-path=/ifs/data/pol_a_b --target-host=[Cluster B IP Address] --target-path=/ifs/data/pol_a_b --schedule=when-snapshot-taken

    Modify policy ‘pol_a_b’ to specify a snapshot naming pattern and archive snapshots:

    IsilonClusterA# isi sync policies modify pol_a_b --target-snapshot-pattern=SIQ_%{SrcCluster}-%{PolicyName}-%Y-%m-%d_%H-%M-%S --target-snapshot-archive=true

    Confirm policy ‘pol_a_b’ is configured for when a snapshot is taken, the snapshot is archived, and the naming pattern is specified:

    IsilonClusterA# isi sync policies view pol_a_b

    <Output truncated – Confirm the fields listed below>

    .

    .

    .

    Target Snapshot Archive: Yes

    Target Snapshot Pattern: SIQ_%{SrcCluster}-%{PolicyName}-%Y-%m-%d_%H-%M-%S

    Target Snapshot Expiration: Never

    Schedule: when-snapshot-taken

    1. On ‘Cluster B’, configure replication from ‘Cluster B’ to ‘Cluster C’ based on when a snapshot of the source directory is taken:

    IsilonClusterB# isi sync policies create --name=pol_b_c sync --source-root-path=/ifs/data/pol_a_b --target-host=[Cluster C IP Address] --target-path=/ifs/data/pol_a_b --schedule=when-snapshot-taken

    Modify policy ‘pol_b_c’ to specify a snapshot naming pattern and archive snapshots:

    IsilonClusterB# isi sync policies modify pol_b_c --target-snapshot-pattern=SIQ_%{SrcCluster}-%{PolicyName}-%Y-%m-%d_%H-%M-%S --target-snapshot-archive=true

    Confirm policy ‘pol_b_c’ is configured for when a snapshot is taken, the snapshot is archived, and the naming pattern is specified:

    IsilonClusterB# isi sync policies view pol_b_c

    <Output truncated – Confirm the fields listed below>

    .

    .

    .

    Target Snapshot Archive: Yes

    Target Snapshot Pattern: SIQ_%{SrcCluster}-%{PolicyName}-%Y-%m-%d_%H-%M-%S

    Target Snapshot Expiration: Never

    Schedule: when-snapshot-taken

    1. On ‘Cluster B’, configure replication from ‘Cluster B’ to ‘Cluster D’ based on when a snapshot of the source directory is taken:

    IsilonClusterB# isi sync policies create --name=pol_b_d sync --source-root-path=/ifs/data/pol_a_b --target-host=[Cluster D IP Address] --target-path=/ifs/data/pol_a_b --schedule=when-snapshot-taken

    Modify policy ‘pol_b_d’ to specify a snapshot naming pattern and archive snapshots:

    IsilonClusterB# isi sync policies modify pol_b_d --target-snapshot-pattern=SIQ_%{SrcCluster}-%{PolicyName}-%Y-%m-%d_%H-%M-%S --target-snapshot-archive=true

    Confirm policy ‘pol_b_d’ is configured for when a snapshot is taken, the snapshot is archived, and the naming pattern is specified:

    IsilonClusterB# isi sync policies view pol_b_d

    <Output truncated – Confirm the fields listed below>

    .

    .

    .

    Target Snapshot Archive: Yes

    Target Snapshot Pattern: SIQ_%{SrcCluster}-%{PolicyName}-%Y-%m-%d_%H-%M-%S

    Target Snapshot Expiration: Never

    Schedule: when-snapshot-taken

    1. On ‘Cluster B’, configure replication from ‘Cluster B’ to ‘Cluster E’ based on when a snapshot of the source directory is taken:

    IsilonClusterB# isi sync policies create --name=pol_b_e sync --source-root-path=/ifs/data/pol_a_b --target-host=[Cluster E IP Address] --target-path=/ifs/data/pol_a_b --schedule=when-snapshot-taken

    Modify policy ‘pol_b_e’ to specify a snapshot naming pattern and archive snapshots:

    IsilonClusterB# isi sync policies modify pol_b_e --target-snapshot-pattern=SIQ_%{SrcCluster}-%{PolicyName}-%Y-%m-%d_%H-%M-%S --target-snapshot-archive=true

    Confirm policy ‘pol_b_e’ is configured for when a snapshot is taken, the snapshot is archived, and the naming pattern is specified:

    IsilonClusterB# isi sync policies view pol_b_e

    <Output truncated – Confirm the fields listed below>

    .

    .

    .

    Target Snapshot Archive: Yes

    Target Snapshot Pattern: SIQ_%{SrcCluster}-%{PolicyName}-%Y-%m-%d_%H-%M-%S

    Target Snapshot Expiration: Never

    Schedule: when-snapshot-taken