mubs
Storage? I am Storage!
Does W2k Server suffer from the "poor write perf." issue? If it does, is there a "system is on UPS, don't bypass write-cache" setting somewhere?
Thanks!
Thanks!
About 160 W2K servers in the Americas the last time I checked. Probably 300+ globally. Hopefully, 2004 will see some consolidation. I know we're planning to reduce the Exchange server count by about 2/3 through consolidation (90 to 30).mubs said:I know Fushigi's is an AS/400 shop, but maybe they have some W2k boxes? Anybody else have any comments about how businesses are handling this?
System max for an AS/400 used to be 1000 drives, but I think they've upped that in the latest release. Something like 2000 73GB drives. Connection would be 18 drives/RAID adapter, U320 SCSI, controllers on PCI-X bus, 90 drives/frame, High Speed Loop (HSL) attach between frames (HSL=2GB fiber with 2nd connection for redundancy & path optimization). That'd more than likely be a box with 16 to 32 Power4 CPUs & 128+GB RAM. My little 4-way box with 14GB RAM and 65 drives pales by comparison.mubs said:Thanks for the reply, Fushigi! 65 raided drives on one host! 160 servers just for Exchange! I cower before your might! You're a giant compared to poor midget ole me...
Thanks for the link. I don't know, is it safe to use for W2k Server? I tried that a long time ago on my W2k Prof. box running Promise Ultra 100, and it craps out immediately sayingLunarMist said:Did you try to use these?
Error getting Write Cache value.
(1117) The request could not be performed because of an I/O device error.
This error message indicates that the disk device does not return information about its write caching status in response to the appropriate SCSI or ATAPI command. This error message is simply an indication of the capabilities (or lack thereof) of the device or its driver, and it typically implies that either the device does not support write caching or that the device driver does not support the commands that are required to query and set the device's write cache setting.
To resolve this issue, contact the vendor of the disk device.