
Managing Disk Array Capacity
247
M
a
na
ging
the
Di
sk
Array
on HP-UX
Assigning LUN Ownership
When a LUN is bound, you must identify which disk array controller (A or B) owns the
LUN. The controller that is assigned ownership serves as the primary I/O path to the LUN.
The other controller serves as the secondary or alternate path to the LUN. If there is a
failure in the primary I/O path and alternate links are configured, ownership of the LUN
automatically switches to the alternate path, maintaining access to all data on the LUN.
When assigning LUN ownership, consider the following:
•
To ensure optimum performance, LUN ownership should be balanced between
controllers. This ensures that one controller is not overloaded with I/O requests, while
the other is idle.
•
Controller ownership can be changed on an existing LUN without impacting its
operation. If you find that there is an imbalance between I/O path loads, you can change
the ownership of one or more LUNs to solve the problem.
Note
Does the primary path selected using LVM impact LUN ownership?
Yes. The primary I/O path established using LVM defines the owning controller
for the LUN. This may override the controller ownership defined when the LUN
was bound. For example, if controller A was identified as the owning controller
when the LUN was bound, and LVM subsequently established the primary path
to the LUN through controller B, controller B becomes the owning controller.
Selecting a RAID Level
C
AUTION
RAID 0 does not provide data redundancy. It should only be used in
situations where high performance is more important than data protection.
The failure of any disk within a RAID 0 LUN will cause the loss of all data on
the LUN.. RAID 0 should only be used for non-critical data that could be lost
in the event of a hardware failure.
The RAID level you select for each LUN determines the method used to store data on the
disks. Once selected, the RAID level cannot be changed dynamically. If you want to change
Summary of Contents for Surestore Disk Array 12h - And FC60
Page 16: ...16 ...
Page 36: ...36 Array Controller Enclosure Components Figure 9 Controller Enclosure Front View ...
Page 41: ...Array Controller Enclosure Components 41 Product Description Figure 13 Controller Fan Module ...
Page 44: ...44 Array Controller Enclosure Components Figure 15 Power Supply Fan Module ...
Page 68: ...68 Capacity Management Features ...
Page 117: ...Topologies for HP UX 117 Topology and Array Planning Figure 39 High Availability Topology ...
Page 122: ...122 Topologies for HP UX Figure 40 High Availability Distance and Capacity Topology ...
Page 126: ...126 Topologies for HP UX Figure 41 Campus Topology ...
Page 130: ...130 Topologies for HP UX Figure 43 Four Hosts Connected to Cascaded Switches ...
Page 142: ...142 Topologies for Windows NT and Windows 2000 ...
Page 158: ...158 Installing the Disk Array FC60 Figure 54 Enclosure EIA Positions for System E Racks ...
Page 161: ...Installing the Disk Enclosures 161 Installation Figure 56 Disk Enclosure Contents ...
Page 172: ...172 Installing the Controller Figure 62 Controller Enclosure Package Contents ...
Page 174: ...174 Installing the Controller Figure 63 Mounting the Controller Enclosure ...
Page 234: ...234 Adding Disk Enclosures to Increase Capacity ...
Page 274: ...274 Managing the Disk Array Using SAM Unassigned disks selected as hot spares ...
Page 345: ...HP UX Diagnostic Tools 345 5 HP UX DIAGNOSTIC TOOLS Overview 346 Support Tools Manager 347 ...
Page 350: ...350 Support Tools Manager Figure 90 mstm Interface Main Window ...
Page 358: ...358 Support Tools Manager ...
Page 440: ...440 FCC Statements USA Only ...
Page 466: ...466 Index ...