HP StorageWorks SAN Virtualization Services Platform Administrator Guide (5697-0934, May 2011)

• Using the management interface of the new array, create or define DPMs and VSMs as hosts,
and then present the back-end LUs to the DPMs and VSMs. Each pair of quads should have
a unique host definition.
• Refresh the VSM software using the VSM refresh button. Once the new back-end LU is visible,
use it and others to create stripe sets, then create pools. Use the pools to create front-end
virtual disks.
It is also important to understand the best practices for the vendor-specific storage arrays that are
configured behind the SVSP. Since much of I/O directed at the SVSP will pass directly through the
SVSP, optimizing the arrays based upon the I/O characteristics has the most value. It should also
be noted that with the exception of striping, the SVSP does not change the performance of the
back-end array, and with the exception of synchronous mirrors, SVSP does not change the
availability of a back-end array. All physical LUs presented from any array should have the
“preferred path” balanced between controllers (for arrays with such a concept; this may not be
applicable to HP XP arrays).
NOTE:
• Do not expand back-end LUs that are already configured in the SVSP. If a particular storage
pool runs out of free space and you want to expand it, create a new virtual disk on the EVA,
and add it to the pool.
• Do not change back-end LU numbers for LUNs that are already managed by the SVSP.
• Remove back-end LUs from SVSP management only after releasing them from storage pools
and stripe sets.
• Do not use HP Business Copy EVA or HP Continuous Access EVA (or the equivalent with other
arrays) on any back-end LU presented to the SVSP domain.
• Once a back-end LU is presented to the SVSP domain, do not change any characteristics of
the back-end LU.
• Do not rename a back-end LU once it has been included in a storage pool.
Adding EVAs
When using HP Command View EVA to create back-end LUNs on the EVA that will be presented
to the SAN Virtualization Services Platform domain (both DPM and VSM servers), or when presenting
existing EVA virtual disks to the domain (for data import) the following presentation rules apply:
• Each DPM quad and each VSM server must be defined as hosts and include all ports.
• Create a number of LUNs with at least one LUN per path to the controller.
• Display the virtual disk to the DPM quad and VSM server using the same LUN number. The
EVA virtual disk must be presented to both the DPM and VSM servers.
• The LUN must use the appropriate preferred controller setting of “failover/auto failback”
option, and not “no preference.”
Adding MSAs
The following process describes how to create back-end LUs on an MSA2000 and present them
to SVSP. For other MSAs, consult the MSA documentation.
18 Adding devices to the domain