Go Premium for a chance to win a PS4. Enter to Win

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

Exchange 2000 Server Installation

I am about to install Exchange Server 2000 on a Windows 2000 Server box.  I would like to know what you guys out there think the best way for setup -

1. What RAID level - I was going to setup RAID 5.
2. How should I partition the drives - I was going to have one large partition. (only 25 users at most)
3. f.y.i this box is also going to be a DC.

If you guys believe the best way is to have multiple partitions, how should I do it?

1. OS Partition - 20GB, DATA Partition - 200GB or od I need three partitions???
2. f.y.i. I know some of you out there believe in seperating databases by channels on the raid card.  Not needed for this envoirnment.  

But if I have a DATA partition for the Exchange database, will I be able to point Exchange to where the database will reside? Or do I do that later after the installation is done.  Unmount the store move the files and then remount it???

Your help is greatly appreciated.

Also f.y.i this installation of Exchange 2000 will be done using the /diasaterrecovery switch.  I am moving it away from another server, and I have always found this to be the best and fastests way.  I am actually going to remove that server off the network as if it died.  I can afford to have the services down.  Don't know if that switch gives me options of where to store the DB. Don't know if this changes everything.
0
BygRob
Asked:
BygRob
  • 4
  • 2
1 Solution
 
redseatechnologiesCommented:
Hi BygRob,

If you are going to have exchange running on 1 disk (which you are, as the RAID will act like 1 disk) then it doesn't really matter how you configure it with partitions.

For only 20 users, it shouldn't be too much of a performance problem, and you could always add another disk later for the transaction logs,

I would do 3 partitions on RAID5 (you didn't give us the total size of the disks or the databases (or even exchange version) so I will assume it is 200GB,

C: 20GB - Windows/Pagefile/Exchange PROGRAM files
D: 80GB - Exchange Databases (assuming this is exchange 2000 standard)
E: Rest - Transaction logs / static storage (copies of exmerged mailboxes, or the exchange 2000 cd, etc)

-red
0
 
redseatechnologiesCommented:
Whoa, did you change that question after posting it?  There looks like more information there :)

Yes, you can change the location of the exchange databases once the server is live -> http://support.microsoft.com/kb/257184

0
 
BygRobAuthor Commented:
Red -

Do you live by your computer?  :)

Transaction logs? I never knew Exchange uses tranactions logs.  What are the files?  How do I move those to that third partition?  The drive size is 200GB.
0
Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

 
redseatechnologiesCommented:
Lol, I am about to go home from work, just checking mail and looking at new questions :)

Transaction logs are just that, logs of transactions committed to the database.

The reason you want them to be on their own disk is because they are written to whenever the database is - and having 2 things trying to do the same thing at the same time on the same disk is a resource nightmare.

They can be moved quite simply, the above guide will work for that as well (if it doesn't mention it, it is the next box down beneath the databases)

Don't move any files manually, do it the MS way :)

-red
0
 
BygRobAuthor Commented:
Oh so when switching the database and the transaction via Exchange Manager it will move the files for you? I don't have to use explorer to move them myself?
0
 
redseatechnologiesCommented:
Correct :)
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

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