- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- MPIO policy settings for Windows cluster
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
08-16-2011 02:24 AM
08-16-2011 02:24 AM
MPIO policy settings for Windows cluster
Hi experts,
What is the correct load balance policy for windows cluster? I currently run with SQST, ALB on but I got many error messages from time to time. It is very slow(300~700ms per read) during backup and it caused disk missing once. Please help. (Please see attachment for full text)
-----------------------------------------------------------------------
In system event log:
HP MPIO DSM for EVA4x00/6x00/8x00 family of Disk Arrays is attempting an operation on \Device\MPIODisk2. The Type is noted in the dump data.
An unrecoverable path failure occurred on SCSI address (3.0.4.3). Disk 6001438005DED1EC0000D00000F80000 is still accessible over redundant path(s).
The DSM has completed remove processing for path (SCSI address (3.0.4.3)) to multipath capable disk 6001438005DED1EC0000D00000F80000.
-----------------------------------------------------------------------
In sql server errorlog:
2011-08-11 17:11:06.97 spid11s SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [j:\TCPDATA2\TCPDATA10.ndf] in database [TCP] (5). The OS file handle is 0x0000000000001FF0. The offset of the latest long I/O is: 0x00003054d6e000
2011-08-11 17:11:34.83 Backup Error: 3203, Severity: 16, State: 1.
2011-08-11 17:11:34.83 Backup Read on "J:\TCPLOG3\TCPLOG3.ldf" failed: 1167(The device is not connected.)
2011-08-11 17:11:34.83 Backup Error: 3203, Severity: 16, State: 1.
2011-08-11 17:11:34.83 Backup Read on "j:\TCPDATA2\TCPDATA7.ndf" failed: 1167(The device is not connected.)
2011-08-11 17:11:34.83 spid1836 Internal I/O request 0x000000B22589CAA0: Op: ReadDatabase, pBuffer: 0x000001027E360000, Size: 458752, PageNumber: 8:1929880, SOS: Internal: 0xC000009D, InternalHigh: 0x0, Offset: 0xAE530000, OffsetHigh: 0x3, m_buf: 0x000001027E360000, m_len: 458752, m_actualBytes: 0, m_errcode: 1167, File: j:\TCPDATA2\TCPDATA7.ndf
-----------------------------------------------------------------------