Dell EMC VxFlex Ready Node User Manual page 64
Hide thumbs
Also See for EMC VxFlex Ready Node:
- Operating system installation manual (74 pages) ,
- Operating system installation manual (86 pages) ,
- Installation manual (92 pages)
Table of Contents
Advertisement
Architecture
Dell EMC VxFlex Ready Node AMS User Guide
64
during migration and the reserved capacity does not guarantee success). The MDM
does not hold onto source capacity once it has been migrated, but releases it
immediately.
You can live migrate volumes (and v-trees) from one pool to another, even between
Fine-Granularity and Medium-Granularity, and across Protection Domains.
Note:
This often requires zero-padding on the pools, especially when moving from
Fine-Granularity to Medium-Granularity for compression benefits.
All new Medium-Granularity pools should have zero-padding enabled.
Use the following Migration Paths table for reference:
V-Tree migration can take a long time, depending on the size of the V-Tree and the
system workload. During migration, the V-Tree is fully available for user I/O. V-Tree
migration is done volume block by volume block. When a single block has completed its
migration, the block's capacity at the source becomes available, and it becomes active
in the destination Storage Pool. During migration, the V-Tree has some of its blocks
active in the source Storage Pool and the remaining blocks active in the destination
Storage Pool.
Note:
You can speed up the migration by using volume migration IO priority (QoS).
The default favors applications with one concurrent IO and 10MB/sec per device.
Increasing the 10MB/sec increases the migration speed in most cases. The max
value can reach 25MB/sec. The faster the migration the higher the impact might
be to the applications. To avoid significant impact, the concurrent IOs should not
be increased.
When migrating from Multi Granularity to Fine Granularity, volumes must be zero
padded. For more information on zero-padding, see "Storage Pools" in the Getting to
Know Guide .
The user can pause a V-Tree migration at any time, in the following ways:
Gracefully: To allow all data blocks currently being migrated to finish before
l
pausing.
Forcefully: To abort the migration of all blocks currently in progress.
l
Once paused, you can choose to resume the V-Tree migration, or to roll back the
migration and have all volume blocks returned to the original Storage Pool.
V-Tree migration can also be paused internally by the system. System pauses happen
when a rebuild operation begins at either the source or destination Storage Pool. If the
- Quick Links:
- Introduction to Vxflex Ready Node
- Hardware
Hide quick links:
Advertisement
Chapters
Table of Contents
