Unsolved
This post is more than 5 years old
76 Posts
0
963
VMAX ThinPool re-claim
If I add a disk to my Celerra Thin Pool I can immediately delete it as long as no data is on it.
Is there a way I can do the same thing when my Celerra Pool utilization shrinks ?
Consider a 10Tb Pool on the Celerra supported by 10 1TB disks. d1,2,3,4,5,...
If I delete 3 filesystems that use 6Tb I'd like to return a portion of the meta's to the original VMAX thin pool.
- NAS, Evacuate the remaining data off Celerra disk. (How)
- NAS, Delete the disk.
- VMAX Unbind etc to return the tdat capacity.
Option 2
Create a new pool and move remaining data to it.
nas_copy ?
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
May 20th, 2015 11:00
i am afraid you are limited to option 2 (nas_copy, server_archive, nas_replicate)
ScotN
76 Posts
0
May 21st, 2015 04:00
Unfortunately I seem to be in a pickle. The storage pool also contains my DART luns. root_vdm's etc...
Is there really no way to evacuate a meta disk from a pool without destroying the entire pool ?
There seem to be options that would support it.
nas_pool...
-shrink { |id= } [-storage ]
-volumes [, ,...][-deep]
Shrinks the storage pool by the specified unused volumes. The
-storage option can be used to differentiate pools when the same pool
name is used in multiple storage systems. When the -deep option is
used to shrink a user-defined storage pool, it removes the specified
member volumes from the pool, and recursively deletes any unused
volumes unless it is a disk volume. If the -deep option is not used to
shrink a user-defined storage pool, the member volumes are left
intact so that they can be reused. The is_dynamic option must be set
to n before shrinking system-defined storage pools.
Note: Shrinking of a system-defined storage pool by default deletes
member volumes automatically. Specifying the -deep option on the
system-defined storage pool shrink does not make any difference.
ScotN
76 Posts
0
May 21st, 2015 05:00
Scratch that comment on DART volumes they are not in this user defined pool. Only VDM_ROOT and user volumes.
dynamox
1 Rookie
1 Rookie
•
20.4K Posts
0
May 21st, 2015 05:00
if you use replicator (loop back replication), root_vdm file systems will be migrated as well (if you replicate VDM that is, in addition to user data file system)