Ensure a common Snapshot copy in a mirror-vault deployment
-
PDF of this doc site
- Cluster administration
-
Volume administration
- Logical storage management with the CLI
-
NAS storage management
- Configure NFS with the CLI
- Manage NFS with the CLI
-
Manage SMB with the CLI
- Manage file access using SMB
- SAN storage management
- Security and data encryption
-
Data protection and disaster recovery
- Data protection with the CLI
Collection of separate PDF docs
Creating your file...
You can use the snapmirror snapshot-owner create
command to preserve a labeled Snapshot copy on the secondary in a mirror-vault deployment. Doing so ensures that a common Snapshot copy exists for the update of the vault relationship.
If you use a combination mirror-vault fan-out or cascade deployment, you should keep in mind that updates will fail if a common Snapshot copy does not exist on the source and destination volumes.
This is never an issue for the mirror relationship in a mirror-vault fan-out or cascade deployment, since SnapMirror always creates a Snapshot copy of the source volume before it performs the update.
It might be an issue for the vault relationship, however, since SnapMirror does not create a Snapshot copy of the source volume when it updates a vault relationship. You need to use the snapmirror snapshot-owner create
to ensure that there is at least one common Snapshot copy on both the source and destination of the vault relationship.
-
On the source volume, assign an owner to the labeled Snapshot copy you want to preserve:
snapmirror snapshot-owner create -vserver SVM -volume volume -snapshot snapshot -owner owner
The following example assigns
ApplicationA
as the owner of thesnap1
Snapshot copy:clust1::> snapmirror snapshot-owner create -vserver vs1 -volume vol1 -snapshot snap1 -owner ApplicationA
-
Update the mirror relationship, as described in Updating a replication relationship manually.
Alternatively, you can wait for the scheduled update of the mirror relationship.
-
Transfer the labeled Snapshot copy to the vault destination:
snapmirror update -source-path SVM:volume|cluster://SVM/volume, … -destination-path SVM:volume|cluster://SVM/volume, … -source-snapshot snapshot
For complete command syntax, see the man page.
- The following example transfers the
snap1
Snapshot copy -
clust1::> snapmirror update -vserver vs1 -volume vol1 -source-snapshot snap1
The labeled Snapshot copy will be preserved when the vault relationship is updated.
- The following example transfers the
-
On the source volume, remove the owner from the labeled Snapshot copy:
snapmirror snapshot-owner delete -vserver SVM -volume volume -snapshot snapshot -owner owner
The following examples removes
ApplicationA
as the owner of thesnap1
Snapshot copy:clust1::> snapmirror snapshot-owner delete -vserver vs1 -volume vol1 -snapshot snap1 -owner ApplicationA