Upgrading LH3000 disk subsystem

[Paulo Mira]

Hello all. I have an LH3000 with 4 18GB drives, set up as a RAID5 array with a single logical drive (i was under the misconception that a RAID array doesn't suffer from fragmentation. i know better now). This server is doing a lot of diferent things, namely file serving, email and MSSQL. Recently, some heavy-usage databases were installed on the SQL Server, which are bringing the disk subsystem to it's knees. I now want to add some HDs and rebuild the RAID arrays. I want to set up a 4 drive RAID 1+0 array for the database data files, a RAID 1 array for the log files, files being served, mail and OS.
So my questions are:
Does this configuration sound adequate, or should i add another RAID 1 array and try to separate things further?
What is the Disk Duplexing Kit for, and would it help me in this situation?
Can i use the newest U320 drives with the NetRAID controller?
Can i use Compaq brand HDs, or should i stick with the HP ones mentioned on the product's accesories page?

Thanks for your time,

Paulo

[Terri Harris]

First, there is not an option with the NetRAID controllers to do a RAID 1+0.
Is this the Ultra2 or Ultra3 version of the LH3000? If the product number (P1234X) ends in a "A", it is the Ultra2. If it ends in a "B", it is the Ultra3 version.
Ultra3 drives are supported, but if the integrated NetRAID is Ultra2 then it will only be Ultra2. You can add a Ultra3 NetRAID controller such as the NetRAID-1M or NetRAID-2M.
With the existing hardware I would configure a RAID 1 for the OS and log files, and a RAID 5 as the data array.
You will need to use the HP drives.
The duplex kit allows the hot swap drive cage to be "split", resulting in 3 hot swap drive bays going to one controller, and 3 hot swap drive bays going to a different controller. Without the duplex kit (as it is now) you can connect the hot swap drive cage (up to 6 drives) to one controller only.
I hope this helps!

[Paulo Mira]

Hi,

The server's Prod. N. ends with an A, so it's an Ultra2 controller. Also, i meant to say RAID 10, not 1+0.

Today was the second time in three weeks that the server hung: after some 5 minutes of heavy HD trashing, Windows 2000 BSOD'ed.

I think i will take a step-by-step aproach: first i will add 2x 36GB HD 10 or 15K, upgrade the memory on the NetRAID to 128MB and get a battery for the controller. This will leave me with 6 drives total, and will allow me to set the cache to write-back (i have the server hooked up to an UPS, but since there's no redundancy should the UPS fail, i have left the cache on write-through)

If the problems persists, i'll have to get a 2nd drive cage, possibly a 2nd RAID controller and either get addicional HDs or move each RAID array to it's own ontroller.
The second option will, of course, be much more expensive than the first, and (assuming the problem gets solved in step 1) the savings will allow me to get a new server and offload some of the work to it.

In your opinion, would this be the right move? Will i experience any problems if i fill a drive cage with 4 10K HDs and 2 15K HDs, heat-wise or power-wise? Would RAID 10 be overkill for MSSQL data files?

[Terri Harris]

Before making any changes, what actually indicates that the problem is the disk subsystem?
I would recommend the following steps first.
1. Install HP Instant TopTools, under the REPORT tab save the file and email this to Netserver support:
NetSrvTech_Support@hp.com
2. Check the STATUS tab under Instant TopTools to view the HP event log. Are there any hardware errors?

To install Instant TopTools, go to the following web site:

http://www.hp.com/toptools/download/server_agents.html

Under other hp management tools, select: Instant TopTools 5.x (Eng.)

The downloaded exe file will launch an install wizard. Install and run the program.

Let's troubleshoot your existing system & configuration, then recommendations can be better made.

Note: The L3000 includes a dual-channel integrated RAID controller. So you should have a 2nd RAID channel available if you do add the 2nd drive cage.

[Carsten Reinhard]

Hi Paulo,

Did you solve your Problem? What have you done? We have a similar problem with MS SQL Server and solved it (after changing all the hardware through HP) just by uninstalling a particular part of the HP Top Tools. Do you have them installed too?

Regards,

Carsten

[Paulo Mira]

what a trip down memory lane.
thread closed, points assigned.