HP StorageWorks SAN Virtualization Services Platform Best Practices Guide (5697-0935, May 2011)

15 SVSP management
Removing a failed back-end drive from the configuration
See the HP StorageWorks SAN Virtualization Services Platform Administrator Guide for the
procedure. It is critical that the steps be followed exactly.
IMPORTANT: If a remove is not performed correctly, data availability may be at risk.
Importing and exporting arrays and LUs into an SVSP configuration
When you import a back-end LU into a pool, it receives 1 MB from the pool at the beginning of
the disk and 2 MB at the end of the disk. In Figure 21 (page 65), a 310 GB LUN is imported into
ImportPool_5GB. When this completes (it is a very fast process), you must select one of the import
options described in this chapter. Once a unit has been imported-in-place, it may make use of all
of the SVSP services. However any service virtual disks created cannot be exported without an
application (backup or mirrorUX).
Import and migrate
If the goal is to permanently migrate the virtual disk, you must migrate the imported disk into a
normal pool. After migrating data, the import pool is 315 GB. Next, remove the 310 GB LUN
from importPool_5GB. Otherwise, after the next import in this pool, the segments in the pool are
mixed up and you cannot remove the 310 GB LUN.
Figure 21 Imported back-end LU
TIP: HP recommends that following an import-in-place, a virtual disk is migrated to storage behind
the SVSP, and the array be repartitioned and its LU presented to a storage pool. Note that this
operation maybe done logical unit by logical unit. It is not necessary to do the entire array at one
time.
Import then export
If it is likely that an export will be necessary, do not migrate imported virtual disk to a new storage
pool, as export will only move the first and last megabytes that were migrated on the import back
Removing a failed back-end drive from the configuration 65