- Mar 20, 2001
- 1,065
- 0
- 76
I'm heavily leaning towards the HP servers at this point. Like I mentioned above, I thought they were prohibitively expensive and that they forced you to use their hard drives. 3 to 6k for a new server (minus storage) is very doable. Our botched move to the cloud host still has us officially owing them more than $20k! I say officially, because there is quite a bit of room to explore what went wrong and where the blame lies. They will most certainly be willing to negotiate with us on amounts owed as we pull out of that contract.
I fully concede that without a sys admin on staff, this whole course of action that I'm pursuing would be folly. I am, at the moment, typing up a job description for a sys admin (because our CTO told me yesterday I'm the only one that has a firm handle on what this person would be responsible for... /sigh). Getting a sys admin on staff is actually more important to me than the whole own-our-own-servers question. They're currently paying us developers to do IT stuff. We didn't sign on for this, and it's more expensive to have us doing it than to hire a real sys admin.
EDIT: forgot to mention, I don't know too much about our SAN. I'm pretty sure it's FC, but our CTO seemed to think it was iSCSI. We have our two big databases separated out (logs as well) onto separate LUNs, but I don't know how the underlying spindles are apportioned or what RAID is in use.
I fully concede that without a sys admin on staff, this whole course of action that I'm pursuing would be folly. I am, at the moment, typing up a job description for a sys admin (because our CTO told me yesterday I'm the only one that has a firm handle on what this person would be responsible for... /sigh). Getting a sys admin on staff is actually more important to me than the whole own-our-own-servers question. They're currently paying us developers to do IT stuff. We didn't sign on for this, and it's more expensive to have us doing it than to hire a real sys admin.
EDIT: forgot to mention, I don't know too much about our SAN. I'm pretty sure it's FC, but our CTO seemed to think it was iSCSI. We have our two big databases separated out (logs as well) onto separate LUNs, but I don't know how the underlying spindles are apportioned or what RAID is in use.
Facebook
Twitter