Discussion Locked

OS RAID Config

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello,

I need your help. I have a boss who does not come from a network admin background. We are spec'ing out a new terminal server from Dell. This will be the third terminal server. I am spec'ing the server with RAID 0 for the OS (2 36 GB drives). He is questioning why we need RAID on the OS since the server will have no data and there are already 2 terminal servers. I am trying to make him understand about uptime, the cost of downtime, and performance. This does not seem to be making him feel that this should be a "standard." Any ideas of sites/docs that you know of to help me convince him of this?

Thank you for any input on this matter

David
dmahler@isidc.com

5 replies

by stress junkie

I'm inclined to agree with your boss. A terminal server doesn't need fast disks, which RAID 0 would enhance. Your I/O bottleneck is going to be your network.

RAID 0 configuration, which is striping, doubles your risk of disk failure. You might want to consider RAID 1 which is mirroring.

SCSI disks are expensive. Here again we run up against the issue of disk performance and how it is not an issue in your terminal server. I'd use ATAPI disks. I'd use Seagate or Maxtor, and not the expensive server disks either. Desktop disks will perform fine. I'd avoid Western Digital disks.

SCSI costs more money in its required support hardware. Either you have a motherboard with a SCSI controller, which is more expensive than a motherboard without a SCSI controller, or you need to purchase a SCSI bus card. So you can save money both on the disks and on the controller if you purchase ATAPI disks and use software based RAID 1.

Think about this. The slowest, cheapest CPUs that you can purchase these days are overkill for this application. This machine will not be busy. The network cards may be saturated but the CPUs may still be 50% idle unless you are going to have six or eight network cards. The workload on this machine will be very bursty rather than evenly spread out over time.

I think that you can use good, solid, but inexpensive hardware to implement this machine. You can get reliable performance requirements from your other terminal servers so that could alter almost anything that I said about CPU requirements, but the disks still probably don't have to be high performance server disks.

by david_mahler

Great reply! I did mean RAID 1 for fault tolerance. I agree with your comments about the CPU and network. The reason I am pitching this, and not a glorified desktop with a gigabit card, is fault tolerance. With a server, there can be redundant NIC's, power supply, and hard drives. My focus is uptime. If we can spend a couple hundred dollars more and avoid the downtime of rebuilding a server, then it is worth it in my book.

David

by rkuhn040172

Without more info such as # of users, costs of downtime/loss of productivity, etc, I'd go the cheap route.

The hardware requirements for the "typical" terminal server just aren't that great.

Although, if the money is available it certaintly wouldn't hurt.

Another thing to consider as a potential bottleneck is the connection speed at which the end user is connecting.

At my work (construction) they are typically connecting in on a ISN with a measley 128k connection.

The server is far from the bottleneck.

by stress junkie

I recommend the following approach in these kinds of situations. Find out the performance requirements for the new machine. Then find out if the oldest desktop machine would be sufficient to do this work. Then you can use that older machine and purchase a new desktop machine for the person who had been using the old equipment on their desk. Everybody wins. The new desktop machine would have to be purchased at some point in the future anyway so purchasing the desktop computer is something that had to be done. The old equipment is being used so you don't have to purchase new equipment for a function that doesn't really need it. It keeps the old equipment in service longer so it saves a trip to the computer recycler, or worse, the landfill. So you may need to purchase a second disk for the old equipment to implement RAID 1. Overall it saves money and it benefits more people than purchasing new equipment for the terminal server.

by dbucyk

Look into the servers you already have. Have they reached their limit in terms of workload. Are the CPUs burdened, can you expand those systems any more?

If you are having issues with these problems you'll have to scale out meaning to offload the other computers.

You can also ask yourself about the cost of implementing these systems.

You got to remember that Terminal Services requires licensing to each server either remotely or just on the LAN.

When you go through the advantages, in terms of cost (bosses like to hear about saving money), and the disadvantages of losing money, he'll listen.

Just make sure to have a detailed plan when you are implementing the server.

Once you do this, it should change his mind.

This discussion is closed to new replies.