Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 410
  • Last Modified:

Recommended partition size of Windows 2003 Server Standard Edition

Dear all experts,

 I just bought a Windows 2003 Server which is used for file sharining.  This server has 3 * 72GB HD which is running as Raid 5.  Thefore, it has around 140 GB for data storage.  My question is, how large should be the system parition?  Moreover MSDE is also installed and which is used by Backup Exec for logging.

Regards
0
towo2002
Asked:
towo2002
1 Solution
 
karel_jespersCommented:
for the system partition i take at least 3 gb
put you logs on other partitions
0
 
Lee W, MVPTechnology and Business Process AdvisorCommented:
If you set things up properly (logs on other partitions, data files (Exchange) on other partitions, then I'd probably make the C: drive 5-10 GB.  You don't want to underestimate because future upgrades can become PAINFUL.  But you don't want to over estimate either because the space could be used for file sharing, etc.  Basically, only you can answer this correctly.  What else do you plan on or think you might have the remotest need of installing on the system?  Allow space for those items now (plus at least 1GB extra for upgrades).

By the way, Windows won't install if you don't have 1.5x RAM in free disk space - so if you plan on ever upgrading, RAM, make sure you have 1.5GBxRAM + sufficient space for Windows and whatever apps/server programs you may use (You can always get around the 1.5xRAM thing by removing RAM to do the install and putting it back, but Windows will typically create a page file during the install and use 1.5xRAM.  You can move the page file as soon as Windows is setup, but until then, you're stuck with it on C:
0
 
EricdJCommented:
I would agree with the other colleagues. and will mention in addition:

- you need at least up to 2 GB for the setup files (depending on your server version).
- keep in mind the pagefile size (about twice your RAM)
- keep enough free space for additional tasks, like defragmenting. (40%)
- keep enough free space for future fixes/packs (25%)
- put your logs to a separate volume.
... so my suggestion would be 5 (OS) + 3 (page file) + 2 (fixes) + 3 (other programs) makes 13 GB and round off upwards to 15-20 GB for additional tasks.

- In addition i would mention the 'shadow copy' feature of windows 2003, which is very interesting in your scenario of a file server. As it provides users (and you as a operator) the option of recovering a deleted file(s) from the file server (share) without having to restore a backup!! A very useful and introducing article on this can be found on http://www.petri.co.il/what's_shadow_copy_on_windows_server_2003.htm.

good luck.

0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
mikeleebrlaCommented:
keep in mind that you can move the page file to any local drive... to it doesn't have to be on the system/boot partition at all.
0
 
karel_jespersCommented:
you better never do that ,
place it on another physical drive   !!!
0
 
karel_jespersCommented:
if possible of course
0
 
mikeleebrlaCommented:
its on the boot partition by default
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Tackle projects and never again get stuck behind a technical roadblock.
Join Now