Hi Guys
I have a HP ProLiant DL585 G2 8222 which may or may not have a hardware fault, and I need a way of testing it under simulated conditions so I know if it is faulty by next Monday.
It was running 2003 x64 but kept falling over each night with no errors in the event log, I tried installing 2008 R2 today and it blue screened part way into extracting the install files. After 45mins with HP support, they suggested update the firmwares and try again. I ran the Update disk, and this appears to have allowed it to install, I left it on the desktop as I went home at 5.
It also passes the HP diag tests with no issues, it also did this before the bios updates, so i'm not convinced the updates did anything useful.
Does anyone have any recommendations how I can stress it out so I can see if its really working correctly by Monday. It will be used as a MS-SQL Sever either 2005 or 2008 (if I have a license for it) but it will be running the backend db for our call logging software, so it needs to be reliable, or else I will get it in the neck.
It has raid + backup and all that jazz so I wont lose "much" data if it crashes, but it needs to be almost 100% reliable so that the helpdesk + others can keep on working.
Does anyone have any ideas,
At least if I know its faulty, I can give up and use the VM Cluster, but it seemed like a good use for a spare (previously broken, then repaired (badly)) server.
Thanks in advance
Jon
I have a HP ProLiant DL585 G2 8222 which may or may not have a hardware fault, and I need a way of testing it under simulated conditions so I know if it is faulty by next Monday.
It was running 2003 x64 but kept falling over each night with no errors in the event log, I tried installing 2008 R2 today and it blue screened part way into extracting the install files. After 45mins with HP support, they suggested update the firmwares and try again. I ran the Update disk, and this appears to have allowed it to install, I left it on the desktop as I went home at 5.
It also passes the HP diag tests with no issues, it also did this before the bios updates, so i'm not convinced the updates did anything useful.
Does anyone have any recommendations how I can stress it out so I can see if its really working correctly by Monday. It will be used as a MS-SQL Sever either 2005 or 2008 (if I have a license for it) but it will be running the backend db for our call logging software, so it needs to be reliable, or else I will get it in the neck.
It has raid + backup and all that jazz so I wont lose "much" data if it crashes, but it needs to be almost 100% reliable so that the helpdesk + others can keep on working.
Does anyone have any ideas,
At least if I know its faulty, I can give up and use the VM Cluster, but it seemed like a good use for a spare (previously broken, then repaired (badly)) server.
Thanks in advance
Jon
