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 Servers” (page 148).
Limitations
• HP P6000 Continuous Access 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.
Figure 64 Windows Server 2003 (64-bit) and Windows Server 2008 (64–bit) configurations
6. SAN switch 11. Network interconnection
7. Multiple single HBA paths2. Management server
8. SAN switch 23. Host 1
9. Controller A4. Host 2
10. Controller B5. Host 3
Oracle Solaris 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
138 Single path implementation
To Next Page
Loading...
Need help?
General
