What are SnapMirror relationship prerequisites?

What are SnapMirror relationship prerequisites?

• A. Only same ONTAP version
• B. No network requirement
• C. Compatible ONTAP versions on source/target, network connectivity, adequate bandwidth, appropriate permissions, and replication relationship configured
• D. Only license check

Answer: (C)

SnapMirror requires a prepared, reachable pairing between the two clusters and the proper authorization to set up and run replication. First, the ONTAP versions on source and target must be compatible so the replication features and data structures align; mismatched versions can cause unsupported scenarios or failures. Next, there must be network connectivity between the clusters so data can be transferred; without a reliable path, replication cannot occur. Adequate bandwidth is important because the initial seed and ongoing transfers can be substantial, and insufficient capacity can slow replication, cause timeouts, or miss RPO targets. You also need appropriate permissions on both clusters to create and manage the relationship, ensuring you have the rights to configure, monitor, and modify SnapMirror settings. Finally, a replication relationship must actually be configured—defining the source and destination, schedules, and transfer parameters—so the system knows what to replicate and how. If any of these elements are missing, SnapMirror cannot be established or maintained. The other options are incomplete because they cover only a single aspect and ignore the rest.

SnapMirror requires a prepared, reachable pairing between the two clusters and the proper authorization to set up and run replication. First, the ONTAP versions on source and target must be compatible so the replication features and data structures align; mismatched versions can cause unsupported scenarios or failures. Next, there must be network connectivity between the clusters so data can be transferred; without a reliable path, replication cannot occur. Adequate bandwidth is important because the initial seed and ongoing transfers can be substantial, and insufficient capacity can slow replication, cause timeouts, or miss RPO targets. You also need appropriate permissions on both clusters to create and manage the relationship, ensuring you have the rights to configure, monitor, and modify SnapMirror settings. Finally, a replication relationship must actually be configured—defining the source and destination, schedules, and transfer parameters—so the system knows what to replicate and how. If any of these elements are missing, SnapMirror cannot be established or maintained. The other options are incomplete because they cover only a single aspect and ignore the rest.