Home > Storage > PowerScale (Isilon) > Product Documentation > Data Protection > Dell PowerScale SyncIQ: Architecture, Configuration, and Considerations > Snapshots and SyncIQ policies
As snapshots and SyncIQ policies are configured, consider the scheduled time. As a best practice, stagger the scheduled times for snapshots and SyncIQ policies. Staggering snapshots and SyncIQ policies at different times ensures that the dataset is not interacting with snapshots while SyncIQ jobs are running, or conversely. Also, having snapshots and SyncIQ policies with exclusive scheduled times ensures that the maximum system resources are available, minimizing overall run times. However, system resources are also dependent on any performance rules that are configured, as descriged in SyncIQ performance rules.
Another factor to consider is the impact on system resources if SyncIQ policies are triggered based on snapshots, as discussed in Whenever a snapshot of the source directory is taken. For example, if a snapshot policy is configured to run every 5 minutes, the policy is triggered when the snapshot completes. Depending on the dataset and the rate of updates, SyncIQ could be far behind the newest snapshot. In addition, a constant trigger of data replication affects cluster resources. Consider how the snapshot frequency affects overall system performance. Alternatively, rather than using snapshot triggered replication, consider manually running a SyncIQ policy with a specified snapshot, as explained in Specifying snapshots for replication.
For more information about snapshots and SyncIQ, see Target snapshots and SnapshotIQ and SyncIQ.