Unless you are planning to run on hardware that has been around for a
while, I would say it makes no difference in performance using SCSI or
IDE with 70 users. Or 300 for that matter. For security reasons you
might want to set up som kind of disk mirroring. There are a few
hardware options both for SCSI and IDE mirroring, and S-ATA of course.
You can choose whichever you find most attractive. Keep in mind that IDE
disks rarely can be hotswapped.
And last, make a fictional disk failure.. Do you know what to do if a
disk fails? How would you even know it has failed if the system is still
running just fine? Some questions to keep in mind.. :)
/Andreas
Jason Williams wrote:
Greetings everyone.
After a long hard fought battle, I finally have received permission to
run squid on our network. I've always run squid on my home network
(with great success) and now im looking to do it in the corporate
world. With that, I was hoping to get some type of idea on hardware
needs and possible some suggestions on where to buy/get my hardware.
Ok. Company is around 70 people currently. Growth is very real
possibility.
Coupled with using squid, I will also be using:
http://dansguardian.org/ For web content filtering. (And won't I
come out smelling like roses when I show them we don't have to pay
$15k for a web content system!)
That's it for now. Squid + web content filtering.
I know squid uses more memory than CPU power. what about disks? SCSI?
IDE? does it matter? Obviously, I would like good performance, but
prefer security over performance.
Thanks everyone.
Cheers,
Jaso
