HP Integrity rx2800 Boot from SAN Guide - Page 14

Restrictions, Operating system restrictions, Clustered server restrictions

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 14 highlights

Restrictions The following sections describe restrictions for booting from a SAN. Operating system restrictions The following operating system restrictions apply: Microsoft Windows operating systems require a unique, dedicated disk for booting. Therefore, each server connected to a RAID array must have its own disk, or logical unit number (LUN), dedicated for booting and operating system files. Data can be allocated across both the boot disk and the remaining disks. Booting from array-based disk partitions is possible. NOTE: For Windows Server 2003, a crash dump file will not be generated if the path to the system drive is different from the active path established if the system was booted at the time of a system crash. To ensure that a crash dump is created, move the system disk back to the active boot time path as soon as possible, after any failure. For detailed information a file creation, see the website http://download.microsoft.com/download/f/9/7/f9775acc-baa6-45cc-9dec-b82983705620/ Boot%20from%20SAN%20in%20Windows.doc Clustered server restrictions This section describes clustered server restrictions for Storport miniport drivers. Storport miniport driver restrictions • For Storport miniport driver restrictions, see the following Microsoft articles: • To set up MSCS properly, see Cluster is formed by using a local quorum resource after a cluster setup failure in Windows Server 2003, available at the website http://support.microsoft.com/?kbid=888160 • For boot from SAN and MSCS configurations on Windows Server 2003 systems, see the updated Storport storage driver, version 5.2.3790.2494 that is available for Windows Server 2003 available at the website http://support.microsoft.com/kb/912944/en-us Also see How to add a registry value to a Windows Server 2003-based computer that you start from a SAN so that the startup disk, the page file disks, and the cluster disks are all on the same SAN fabric, available on the website http://support.microsoft.com/kb/886569/en-us • To avoid improper modification of the registry, use the Boot from SAN Cluster Registry Update utility to add the Manage Disks On System Buses key. Download the utility (BFSCLRegUp.exe) from the website http://h18006.www1.hp.com/storage/saninfrastructure.html • A minimum of two HBA ports per host is required for a High Availability (HA) configuration. For detailed information, see the ProLiant High Availability website http://h18004.www1.hp.com/solutions/enterprise/highavailability/index.html 14 Boot from SAN

  • 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
Restrictions
The following sections describe restrictions for booting from a SAN.
Operating system restrictions
The following operating system restrictions apply:
Microsoft Windows operating systems require a unique, dedicated disk for booting. Therefore, each
server connected to a RAID array must have its own disk, or logical unit number (LUN), dedicated for
booting and operating system files. Data can be allocated across both the boot disk and the remaining
disks. Booting from array-based disk partitions is possible.
NOTE:
For Windows Server 2003, a crash dump file will not be generated if the path to the system drive is
different from the active path established if the system was booted at the time of a system crash. To
ensure that a crash dump is created, move the system disk back to the active boot time path as soon
as possible, after any failure. For detailed information a file creation, see the website
Boot%20from%20SAN%20in%20Windows.doc
Clustered server restrictions
This section describes clustered server restrictions for Storport miniport drivers.
Storport miniport driver restrictions
•
For Storport miniport driver restrictions, see the following Microsoft articles:
•
To set up MSCS properly, see
Cluster is formed by using a local quorum resource after a cluster
setup failure in Windows Server 2003
, available at the website
h
t
tp://su
ppo
r
t
.mi
c
r
o
s
o
f
t
.co
m/?kb
i
d=8
8
816
0
•
For boot from SAN and MSCS configurations on Windows Server 2003 systems, see
the up-
dated Storport storage driver, version 5.2.3790.2494 that is available for Windows Server
2003
available at the website
h
t
tp://su
ppo
r
t
.mi
c
r
o
s
o
f
t
.co
m/kb/912
9
44/e
n
-u
s
Also see
How to add a registry value to a Windows Server 2003-based computer that you
start from a SAN so that the startup disk, the page file disks, and the cluster disks are all on
the same SAN fabric
, available on the website
h
t
tp://su
ppo
r
t
.mi
c
r
o
s
o
f
t
.co
m/kb/8
8
6
5
6
9/e
n
-u
s
•
To avoid improper modification of the registry, use the Boot from SAN Cluster Registry Update
utility to add the Manage Disks On System Buses key. Download the utility (
BFSCLRegUp.exe
)
from the website
h
t
tp://h18
006
.w
w
w1.hp
.co
m/s
t
o
r
age/s
aninf
r
a
s
tr
u
c
tur
e
.h
tml
•
A minimum of two HBA ports per host is required for a High Availability (HA) configuration.
For detailed information, see the ProLiant High Availability website
h
t
tp://h18
00
4.w
w
w1.hp
.co
m/s
o
lu
ti
o
ns/e
n
t
e
r
pr
is
e/hi
gha
v
aila
b
ilit
y/inde
x
.h
tml
Boot from SAN
14