NetApp
Vserver : Storage > Volumes : Understanding volumes : Considerations for working with Snapshot copies of Infinite Volumes
Considerations for working with Snapshot copies of Infinite Volumes
You can create, manage, and restore Snapshot copies of Infinite Volumes. However, you should be aware of the factors affecting how the copies are created and the requirements for managing and restoring the copies.
When creating Snapshot copies of Infinite Volumes, consider the following factors:
•
The volume must be online.
•
The Snapshot copy schedule should be more than hourly.
It takes longer to create a Snapshot copy of an Infinite Volume than of a FlexVol volume.
•
The operation can run in the background.
The creation of a Snapshot copy of an Infinite Volume is handled as a cluster-scoped job (unlike the same operation on a FlexVol volume). The long-running operation spans multiple nodes in the cluster.
After you create Snapshot copies of an Infinite Volume, you cannot rename or modify the copies.
When you are managing Snapshot copy disk consumption, consider the following limitations:
•
You cannot calculate the amount of disk space that can be reclaimed if the Snapshot copies of an Infinite Volume are deleted.
•
To reclaim disk space used by Snapshot copies of Infinite Volumes, you must manually delete the copies.
You cannot use a Snapshot policy to automatically delete Snapshot copies of Infinite Volumes. However, you can manually delete Snapshot copies of Infinite Volumes, and you can run the delete operation in the background.
When you are restoring Snapshot copies of Infinite Volumes, consider the following requirements:
•
You must restore the entire copy.
You cannot restore single files or parts of files.
•
The copy must be in a valid state.

Was this topic helpful? Send comments to NetApp.