Volume management for the xp128/xp1024, Volume management (lu size expansion), Figure 28 luse configuration – HP StorageWorks XP Remote Web Console Software User Manual

Page 59: Drawbacks, Luse rules, 2 volume management for the xp128/xp1024, 28 luse configuration

Advertising
background image

LUN Configuration and Security Manager XP user guide for the XP128/XP1024

59

2

Volume Management for the XP128/XP1024

Use Volume Management to perform the following tasks:

Volume Management (LU Size Expansion)

” on page 59)

Volume Size Configuration (VSC)

” on page 60)

Volume Management (LU Size Expansion)

Volume Management (LU Size Expansion or LUSE) combines two or more LDEVs to function as a larger

LDEV. As a result, a host can access a greater amount of storage with a smaller number of LDEVs.

Figure 28

shows the effect of a LUSE configuration.

Figure 28

LUSE configuration

LUSE can combine up to 36 LDEVs into a LUSE volume. The LDEV number of the LUSE volume is the first or

lowest number of the LDEVs making up the LUSE volume. This is the top LDEV, and is the number the host

will recognize.

Drawbacks

Some operating systems may experience slow disk access times with large logical units, if they contain

a large number of high-use files.

The size of a LUSE volume can increase the amount of time required to perform backups.

LUSE rules

Open volume emulation types OPEN-3, OPEN-8, OPEN-9, OPEN-E, OPEN-L, or OPEN-V are

supported.

The maximum number of LDEVs that can be used to create a LUSE is 36.

LDEVs must be of the same emulation type.

LDEVs must be at the same RAID level. Combining RAID 1 and RAID 5 volumes into the same LUSE

volume is supported, but not recommended.

LDEVs or LUSE volumes to be combined must have no assigned path definitions. These are known as

free (or available) LDEVs. For this reason, Business Copy XP, Continuous Access XP, TrueCopy (TC390),

ShadowImage (SI390), and Continuous Access XP Journal pair volumes cannot be targets of LUSE

operations. For more information, see

LUSE operations that handle a path-defined LDEV

” on page 60.

LDEVs that are to be combined into LUSE volumes must not be reserved for Auto LUN.

When you combine a LUSE volume with another LUSE volume, the range of LDEVs should not be

overlapped.

Advertising