To work around the limit of 251 Snapshot copies per volume, you can create a new destination volume clone, then establish a SnapVault relationship with the new clone.
Before you begin
You must have cluster administrator privileges to perform this task for a cluster. You must have Storage Virtual Machine (SVM)
administrator privileges to perform this task for an SVM
About this task
Creating a new SnapVault relationship to a new volume clone
enables you to continue SnapVault protection
with minimum disruption on the clone
volume and without starting a new baseline transfer. Because the source clone and the volume clone share the latest common Snapshot copy, subsequent updates are performed as usual, according to the policy assigned to the SnapVault relationship.
- Quiesce the SnapVault relationship between the primary volume and the secondary volume by using the snapmirror quiesce command.
This step prevents updates from starting until after the task is complete.
- Verify that there are no active transfers on the relationship by using the snapmirror show command.
The Relationships field should be Idle.
- Create a volume clone based on the most recent common Snapshot
copy between the SnapVault primary volume and the SnapVault secondary volume by using the volume clone create command with the -type DP parameter.
- Establish the SnapVault relationship between the primary volume and the newly created secondary volume clone by using the snapmirror resync command and the -type XDP parameter.
- Delete the SnapVault relationship between the primary volume and the original SnapVault secondary volume by using the snapmirror delete command.