HP Integrity rx2800 Boot from SAN Guide - Page 11

Boot from SAN, BFS Rules and Assumptions

Get HP Integrity rx2800 - i2 PDF manuals and user guides View all HP Integrity rx2800 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 11 highlights

1 Boot from SAN This chapter describes boot setup procedures from a storage area network (SAN) with the required software and hardware using HP Emulex HBAs or HP QLogic HBAs running on Itanium or Proliant Windows systems. For the latest version of this document, see the HP storage website: http://h18006.www1.hp.com/storage/networking/index.html Traditionally, HP servers boot operating systems from internal SCSI or IDE storage devices. With the support of external booting from HP StorageWorks HBAs and RAID arrays, you have the option to eliminate server-based internal boot devices. Booting from an external device decreases downtime through faster server replacement in the event of a server or HBA failure. IMPORTANT: For important troubleshooting information, see 3 Troubleshooting. BFS Rules and Assumptions Make sure that the following rules and assumptions are met before you begin. • All rules and assumptions in the About this guide chapter, as well as this chapter, have been sat- isfied. • One available path from HBA to storage LUN. • In addition to this guide, see the following documentation: • Release notes for HP StorageWorks Emulex host bus adapters for Windows. • Release notes for HP StorageWorks QLogic host bus adapters for Windows. • Whitepapers and best-practices documents. To install Windows on a Boot from SAN LUN with driver versions that are not supported by the initial operating system release, the new driver must be integrated as part of the installation process using a BFS kit. Why boot from SAN? Booting from SAN provides: • Improved disaster recovery • Reduced backup time when the boot path is through a SAN • Additional SAN-managed features Fibre Channel host bus adapters software guide for Windows 11

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
1 Boot from SAN
This chapter describes boot setup procedures from a storage area network (SAN) with the required
software and hardware using HP Emulex HBAs or HP QLogic HBAs running on Itanium or Proliant
Windows systems. For the latest version of this document, see the HP storage website:
h
t
tp://h18
006
.w
w
w1.hp
.co
m/s
t
o
r
age/ne
t
w
o
r
king/inde
x
.h
tml
Traditionally, HP servers boot operating systems from internal SCSI or IDE storage devices. With the
support of external booting from HP StorageWorks HBAs and RAID arrays, you have the option to
eliminate server-based internal boot devices. Booting from an external device decreases downtime
through faster server replacement in the event of a server or HBA failure.
IMPORTANT:
For important troubleshooting information, see
3 Troubleshooting
.
BFS Rules and Assumptions
Make sure that the following rules and assumptions are met before you begin.
•
All rules and assumptions in the
About this guide
chapter, as well as this chapter, have been sat-
isfied.
•
One available path from HBA to storage LUN.
•
In addition to this guide, see the following documentation:
•
Release notes for HP StorageWorks Emulex host bus adapters for Windows.
•
Release notes for HP StorageWorks QLogic host bus adapters for Windows.
•
Whitepapers and best-practices documents.
To install Windows on a Boot from SAN LUN with driver versions that are not supported by the initial
operating system release, the new driver must be integrated as part of the installation process using
a BFS kit.
Why boot from SAN?
Booting from SAN provides:
•
Improved disaster recovery
•
Reduced backup time when the boot path is through a SAN
•
Additional SAN-managed features
Fibre Channel host bus adapters software guide for Windows
11