Prior to configuring data replication policies with SyncIQ, it is recommended to map out how policies align with IT administration requirements. Data replication between clusters is configured based on either entire cluster replication or directory-based replication. Designing the policy to align with departmental requirements ensures that policies satisfy requirements at the onset, minimizing policy reconfiguration. When creating policies, Disaster Recovery (DR) plans must be considered, in the event of an actual DR event. DR readiness is a key factor to success during a DR event.
Failover and failback are specific to a policy. In the event of an actual DR event, failing over several policies requires additional time. On the contrary, if entire cluster replication is configured, only a single policy is failed over minimizing downtime. Additionally, consider that clients must be re-directed to the target cluster manually, through either a DNS update or by manual advisement. If entire cluster replication is configured, a single DNS name change will minimize impacts. However, DR steps may not be a concern if Superna Eyeglass is utilized, as explained in Superna Eyeglass DR Edition.
As policies are created for new departments, it is important to consider policy overlap. Although the overlap does not impact the policy running, the concerns include managing many cumbersome policies and resource consumption. If the directory structure in policies overlaps, data is being replicated multiple times impacting cluster and network resources. During a failover, time is a critical asset. Minimizing the number of policies allows administrators to focus on other failover activities during an actual DR event. Additionally, RPO times may be impacted by overlapping policies.
During the policy configuration stage, select options that have been tested in a lab environment. For example, for a synchronize policy configured to run anytime the source is modified, consider the time delay for the policy to run. If this is set to zero, every time a client modifies the dataset, a replication job is triggered. Although this may be required to meet RPO and RTO requirements, administrators must consider if the cluster resources and network bandwidth can meet the aggressive replication policy. Therefore, it is recommended to test in a lab environment, ensuring the replication policy requirements are satisfied. Superna Eyeglass, explained in Superna Eyeglass DR Edition, additional insight into expected RPO and RTO times, based on a policy.