Workflow for provisioning V-VOLs with direct data mapping enabled

Provisioning Guide for Open Systems for VSP One Block 85

Version
10.5.x
File Size
3643 KB
Audience
anonymous
Part Number
MK-26VSP1B033-03
ft:lastEdition
2026-06-23
  1. Create a pool-VOL and format the LDEVs.
  2. Create a pool and add the pool-VOL.
  3. Create a V-VOL.
  4. Add a path to the V-VOL.
  5. If data migration is required, copy data to the V-VOL.
  6. Reclaim a zero data page.
  7. Monitor free space in the pool.
  8. If pool expansion is required, expand the pool capacity (add the pool-VOL) and expand the V-VOL capacity.
  9. Delete the path from the V-VOL.
  10. Delete the V-VOL.
  11. Delete the pool.

If the data on a volume (V-VOL) is migrated through the host, the unallocated space of the volume is also copied. At this time, the unallocated space before data migration becomes allocated space by the write processing during migration, and the pool used capacity increases after data migration. Therefore, performing data migration on many V-VOLs at a time might fill the pool. The following procedure describes the steps for migrating data on V-VOLs. Perform the following steps for each V-VOL and repeat the steps for all V-VOLs:

  1. Copy all data on the V-VOL from the migration source to the destination.
  2. Reclaim the zero data page.

    To migrate the data per file, reclaim zero data pages as necessary.

If a pool is deleted, the volume (LDEV) that was the pool-VOL becomes blocked. To reuse the volume, format it.