HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: Windows 2003 Server boot from SAN
HPE EVA Storage
1826775
Members
1382
Online
109702
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2006 07:55 PM
05-30-2006 07:55 PM
Hi All,
We plan to implement boot Windows 2003 Server from EVA. In the document WINDOWS 2003 Server BOOT FROM SAN we find a note:
"The memory paging system requires fast access to the pagefile.sys file. In SAN
environments with heavy I/O loads, the access request for moving information to or from the
paging file may be delayed. This can cause the operating system to halt, requiring a reboot to
recover. Microsoft recommends that if paging errors occur, page files should be relocated to disks
that are built into the server using its internal data paths. See the Microsoft article for additional
recommendations related to booting from a SAN on the Microsoft web site
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q305547."
We need exactly know, is it problem for all arrays or for particular array?
Regards, Max
We plan to implement boot Windows 2003 Server from EVA. In the document WINDOWS 2003 Server BOOT FROM SAN we find a note:
"The memory paging system requires fast access to the pagefile.sys file. In SAN
environments with heavy I/O loads, the access request for moving information to or from the
paging file may be delayed. This can cause the operating system to halt, requiring a reboot to
recover. Microsoft recommends that if paging errors occur, page files should be relocated to disks
that are built into the server using its internal data paths. See the Microsoft article for additional
recommendations related to booting from a SAN on the Microsoft web site
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q305547."
We need exactly know, is it problem for all arrays or for particular array?
Regards, Max
/Maxim
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2006 10:44 PM
05-30-2006 10:44 PM
Solution
Hi,
it is not easy to provide you exact answer. The main reason for that is that some HW providers tell you about this problem and some of them do not. It does not mean that they do not have problem, they just did not tell you about it.
I think that this problem is more general then specific to any particular storage and more related to OS itself.
I am almost sure there is no such storage on this world which will have standby resources just for OS paging operations in the case of heavy I/O load on it.
My 2 cents.
Regards,
Mario.
it is not easy to provide you exact answer. The main reason for that is that some HW providers tell you about this problem and some of them do not. It does not mean that they do not have problem, they just did not tell you about it.
I think that this problem is more general then specific to any particular storage and more related to OS itself.
I am almost sure there is no such storage on this world which will have standby resources just for OS paging operations in the case of heavy I/O load on it.
My 2 cents.
Regards,
Mario.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2006 02:18 AM
05-31-2006 02:18 AM
Re: Windows 2003 Server boot from SAN
Max:
I agree with Mario. Any storage Array can have heavy I/O. Windows will ALWAYS work the same (mostly). Delayed access to the pagefile can/will cause a BSOD.
For best performance (if you need a reason), it is best to keep the pagefile separate from anything else. One really good location is on a single disk array on the built-in Array controller (if you have a Proliant DL type server).
Another option is to put in more memory and reduce or remove the page file.
Another problem with Boot from SAN is IF your Wndows Server DOES go belly up (BSOD), and you have the server set up to do a dump... with no local drives, it might not recover properly. I usually just turn off the memory dump since it is not likely that you will send it to MS anyway.
Steven
I agree with Mario. Any storage Array can have heavy I/O. Windows will ALWAYS work the same (mostly). Delayed access to the pagefile can/will cause a BSOD.
For best performance (if you need a reason), it is best to keep the pagefile separate from anything else. One really good location is on a single disk array on the built-in Array controller (if you have a Proliant DL type server).
Another option is to put in more memory and reduce or remove the page file.
Another problem with Boot from SAN is IF your Wndows Server DOES go belly up (BSOD), and you have the server set up to do a dump... with no local drives, it might not recover properly. I usually just turn off the memory dump since it is not likely that you will send it to MS anyway.
Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP