Discussion Locked

Creating Partitions For Installation

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

I will be installing a W2K Server.

Server details:
- will be a domain controller with AD installed
- will be a DNS server
- installing IIS (hosting a few web pages)
- installing Exchange 2000
- installing SQL Server 2000
- may be installing small server applications

The server has a 40 GB hard drive.

How many partitions, and of what size, should I create?

7 replies

by cactus pete

It really rather depends, of course. At the very least, I'd suggest putting your Exchange IS on it's own partition, and SQL on its own. So, three at least.

But I hope I'm not the only one who will warn you, Exchange and SQL on the same box is just asking for overwhelming the 40 GB you have in total. Unless you're only a 5 person office with one simple database consisting of pretty much one table...

You will also have a lot of performance issues, as each of your major apps will beg for more RAM and really keep the disk-writing busy.

Most admins like to have SQL databases and logs on different disks, not just partitions. Now you throw in Exchange and IIS and you're easily in too deep.

It's doable, if you're a very small shop, but even then you have a single point of failure causing major data lose in the event of a crash [or worse].

by cactus pete

How big are all of your mailboxes now? How big is the database you currently have, and how do you plan to use it in the future?

Completely as a rough guess, I'd configure 10 gigs for the OS/AD/DNS/IIS [if you really need to keep IIS there - at least be careful of permissioning] and the future small apps you mentioned, and then pretty much split the other 30 in half between Exchange and SQL. BUT, if your SQL is expected to be very small, and not a growth issue, then give a little more to Exchange.

Be careful, also, that you have a partition with three times the expected needed space for SQL... This way you can easily get to and make backups.

by esherwood

Thanks for the advice. The server is for a small office with about 10 users. I'm going to give it a try.

Should the three partitions be of equal size? Or is there an ideal ratio? Or does the partition size depend on the size of the databases and Exchange mail?

by cg it

you CAN install all that AND also have ISA server, all on one box using MS Small Business Server 2000.

I agree though that having SQL on a seperate box is a good idea. Databases have a tendency to grow rather large over time.

I'm running SBS 2000 DC AD with Exchange and ISA server all on one box WITH ALL patches, hotfixes and updates for W2K SBS server, Exchange 2000 server and ISA server using a Promise IDE RAID mirrored 20 GB drives setup. Everything takes up about 10.5 GB. If you have a LOT of workstations [over 50] and a LOT of users then I suggest more room. Users mailboxes can accumulate ALOT of save mail which chews up space [like SQL database]. Also, I suggest your DONT host your web site on the same box as your DC, Exchange, SQL server[s]. High security risk. Seperate server. You can make that a member server with ISA server controlling traffic or set it off your local network.

Also, I would use dynamic disks and not partitions.Though you CAN increase a partitions size using something like partition commander, it's risky therefore if you flub the amount you need your somewhat stuck with it.

by cg it

here's our 3 server, 25 workstation 100 user setup [we run 2 shifts ] [SBS uses per workstation and not per user client licenses. Unlimited user accounts, but limited to 50 workstations. SBS 2003 is increasing that to 75 workstations].

W2K SBS DC AD with Exchange&ISA on a mirrored RAID 20 GB drives. takes about 10.5 GB with all updates.
W2003 Web Server with a 30 GB IDE [only use about 10 but...]
MS SQL 2000 Server with 160 GB drive [and we are running out of space ] we will probably go with the ultra wide 320 SCSI drives on SQL and triple the amount of space.

by marty

If you haven't already licensed your software, you may want to consider Microsoft's Small Business Server product:

http://www.microsoft.com/windowsserver2003/sbs/default.mspx

It has all the functionality you outlined, configures all the server applications and services more or less automatically (use caution here and do your homework on best practices), and costs a lot less than all the products licensed separately.

I hope this helps.
--Marty

by curacao_dejavu

Definitely don't put the sql and exchange on the same box.
And even the applications I would consider on a seperate box.
This will become a typical issue between a small company (10 persons and maybe low budget) vs a technical sound approach on what to do.
You will 2 (real, with raid etc) servers for sure (exchange and sql are no things to think slight over
and then maybe a lower budget server for that apps, but that will depends of the apps again.

sucess

Leopold

This discussion is closed to new replies.