Why does the snapshot policy stop working on my FSx for ONTAP file system after I use the "snapmirror resync" command?
2 minute read
I want to preserve my snapshot policy after I reestablish SnapMirror on my Amazon FSx for NetApp ONTAP file system using the "snapmirror resync" command.
The snapmirror resync command reestablishes a mirroring relationship between a source and a destination endpoint. User-created snapshot copies aren't replicated by the snapmirror resync operation. The exported snapshot copy on the destination is removed and the client sees the active file system on the destination volume. The relationship is InSync and the periodic creation of common snapshot copies resumes.
1. To determine if the snapshot policy stopped replication on the destination, run the following commands.
Note: The following commands verify that snapshots are created on the destination.
Destination::> snap list vol_name
Destination::> snap list snappolicy_DR
The following example output includes the name of the most recent snapshot:
The preceding example output shows that the last snapshot was taken on 2022-11-02.
2. To avoid issues with snapshot policy replication, use the optional preserve parameter when you run the snapmirror resync command. The preserve parameter is supported only for extended data protection (XDP) relationships. The parameter isn't supported for relationships with a non-data FSx for ONTAP endpoint or for relationships with strict-sync-mirror or sync-mirror policy types. The preserve parameter allows the snapshot policy to continue snapshot creation on the destination.