specific volume can only be the source volume of a single policy. Only one volume per
VTree may be used as a source volume of a policy (any policy). For more information
on V-Trees, see "Snapshots" in the
Getting to Know Guide
.
When you remove the source volume from the policy, you must choose how to handle
auto-snapshots. Snapshots created by the policy are referred to as auto-snapshots.
Your selection depends on if there are locked auto snapshots.
l
If the source volume has no auto snapshots, it doesn’t matter if you select Detach
auto snapshots or Remove auto snapshots.
l
If the source volume has auto snapshots but none of them are locked, you can
choose to detach all snapshots. They become regular snapshots as if the user
created them manually. If you select Remove auto snapshots, they are deleted.
l
If the source volume has locked auto snapshots, you can choose to detach all
snapshots. They become regular snapshots, as if the user created them manually.
If you remove them, those that are not locked are removed, while the auto
snapshots which are locked are detached.
Migrate volume trees (V-Trees)
Migrate a volume and all of its snapshots to a different Storage Pool.
About this task
Volumes undergoing migration remain available for I/O.
Note:
l
V-Tree migration is a long process and can take days or weeks, depending on
the V-Tree's size.
l
You can't migrate volumes that are source volumes of a Snapshot Policy.
Procedure
1. In the Frontend > Volumes view, select the V-Trees display.
2. Expand the list of Protection Domains and Storage Pools and select the V-Tree
that you want to migrate.
3. Right-click the volume and select Migrate V-Tree.
Configuring the System using the VxFlex OS GUI
Dell EMC VxFlex Ready Node AMS User Guide 247
To Next Page
Loading...
