I am planning some data migrations with snapmirror.
Both source and destination aggregates (different clusters) are attached to FabricPool and both source and destination have "auto" tiering policy. I am assuming the the "temperature" of the XDP destinations is measured independently from the source and as long as it's still in preparations - all data will be considered "cold" and will get tiered to the cloud-tier.
After the "cutover" the users will start working on the "destinations" that are now RW and could suffer from performance issues since all the "hot" data is in the cloud tier.
Is my assumption about the "temperature" being different between source and DP ? is there a way to prevent this situation (if i'm short in space and do want to save on the AFF tier in the destination, and not wait until migration is done and only then enable the tiering)
