Considerations for creating a SnapVault backup relationship and a unified data protection relationship for FlexGroup volumes
-
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
-
-
-
Security and data encryption
-
Data protection and disaster recovery
-

Collection of separate PDF docs
Creating your file...
You must be aware of the considerations for creating a SnapVault backup relationship and unified data protection relationship for FlexGroup volumes.
-
You can resynchronize a SnapVault backup relationship and a unified data protection relationship by using the
-preserve
option that enables you to preserve snapshots on the destination volume that are newer than the latest common snapshot. -
Long-term retention is not supported with FlexGroup volumes.
Long-term retention enables creating snapshots directly on the destination volume without requiring to store the snapshots on the source volume.
-
The
snapshot
commandexpiry-time
option is not supported for FlexGroup volumes. -
Storage efficiency cannot be configured on the destination FlexGroup volume of a SnapVault backup relationship and unified data protection relationship.
-
You cannot rename snapshots of a SnapVault backup relationship and unified data protection relationship for FlexGroup volumes.
-
A FlexGroup volume can be the source volume of only one backup relationship or restore relationship.
A FlexGroup volume cannot be the source of two SnapVault relationships, two restore relationships, or a SnapVault backup relationship and a restore relationship.
-
If you delete a snapshot on the source FlexGroup volume and re-create a snapshot with the same name, the next update transfer to the destination FlexGroup volume fails if the destination volume has a snapshot of the same name.
This is because snapshots cannot be renamed for FlexGroup volumes.