Windows Server 2003 (32-bit) and Windows 2000
configuration
Requirements
• Switch zoning or controller level SSP must be used to ensure each single path HBA has an exclusive
path to its LUNs.
• Single path HBA server can be in the same fabric as servers with multiple HBAs.
• Single path HBA server cannot share LUNs with any other HBAs.
• In the use of snapshots and snapclones, the source virtual disk and all associated snapshots and
snapclones must be presented to the single path hosts that are zoned with the same controller. In
the case of snapclones, after the cloning process has completed and the clone becomes an ordinary
virtual disk, you may present that virtual disk as you would any other ordinary virtual disk.
HBA configuration
• Host 1 is a single path HBA host.
• Host 2 is a multiple HBA host with multipathing software.
See Figure 29.
Risks
• Single path failure will result in loss of connection with the storage system.
• Single path failure may cause the server to reboot.
• Controller shutdown puts controller in a failed state that results in loss of data accessibility and
loss of host data that has not been written to storage.
NOTE:
For additional risks, see “Windows Server 2003, Windows 2000, and Windows XP Professional
x32” on page 74.
Limitations
• HP Continuous Access EVA is not supported with single path configurations.
• Single path HBA server is not part of a cluster.
• Booting from the SAN is not supported on single path HBA servers.
Single path implementation60
To Next Page
Loading...
Need help?
General