Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

swap to Dell...

Status
Not open for further replies.

1dannyd

IS-IT--Management
Aug 24, 2001
100
US
I've got six "no name" servers running in my offcies and I'm coming up on a swap out. one I just use as a web/proxy server and one I use as a backup server so those won't enter into the picture. The others i would like some advice on 1)what in your combined experiences on the most reliable dell rack mounted and 2) what is the easiest way to swap over all the infomration from an older server to a new one (I plan on configuring the new dells with additional processor and larger, more disk, RAID5 ARRAYS).
Keep it simple though is relatively my motto. Thanks for the input.
 
I don't think we've ever had an unreliable Dell server, a couple have had hard-to-diagnose faults which has caused more downtime than I'd like but those are the exception.

Specifying a model comes down more to your requirements for the role it will be performing. Current;y we buy a mix of PowerEdge 1750's (1U), PowerEdge 2650's (2U), PowerEdge 2600's (5U in rack orientation) and PowerEdge 4600's (5U in rack orientation).

The 1750 and 2650 are pretty similar, we just use the 2650 when we need more PCI slots (usually for NIC's in firewalls).

The 2600/4600 we use when we want an internal DLT/LTO tape drive as these don't fit in the rack versions. Both perform very well, I can't say I've noticed the 4600 being faster than a similar spec 2600 either.

For real cheap stuff where we don't want RAID etc we get the PowerEdge 650 SCSI (you can RAID these but if the server is important enough to warrant RAID we get a 1750 instead).

As for transferring data, again a lot depends on what the server is doing. For a file server I'd build the new server alongside the old one then do a backup of the old data areas one friday night and restore them to the new server over the weekend, using something like Hyena to recreat shares. It's a hassle though if you use local groups for permissions.

For other servers we build them alongside the current ones also and transfer data if needed or if no data needs to be transferred (say a Proxy server that's not logging locally) we just swap them over.

I've never tried to do a full server restore (including configs) to a different server, you risk taking too much baggage and causing instability on the new server IMO.
 
You need to setup a raid1 / raid 5 config on the new box
put the OS on the raid 1 & use the raid 5 as data storage. This will greatly increase performance
 
A RAID1/RAID5 mixed config is only needed where IO performance is critical. We run pure RAID5 on Exchange, Proxy, file & print etc servers just fine...
 
I typically have a raid one for the os and say, exchange and then use the raid 5 on the same machine for data. In the case of my file server same deal, raid1 for the os and raid 5 for the data, I'm a one man shop so was hoping, especially in terms of the exchange server, to not have to build side by side but Nick makes a good point about bringing over baggage from the other servers. I guess it's time to roll up those sleeves. I see a long weekend coming up...unless you all have a suggestion like running a concurrent exchange server for a while and then pulling the older one off line...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top