• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 271
  • Last Modified:

Exchange 2010 questions

I should probably be able to find the following on the net but ain't having much joy.

So, what's the best disk design for Ex2010?  Its going to be running on ESX 4 on a FC attached SAN so was thinking.  

C: = 50 GB (System)
D: = 350GB (DB and Logs)

This is the curent setup in EX2003.  We're 200 users, some with very large mailboxes.
Or is is best to have DBs and logs on seperate disks??
Also, did i read that you shouldn't use vSphere thin provisioning for Ex2010 and disks should be fat.

Finally, we 're going to be running the PrepareAD on the Schema master which is an 2003 SP2 box does it require an pre-requisites installed as i know it did for 2007.

Cheers
0
kswan_expert
Asked:
kswan_expert
2 Solutions
 
oneitnzCommented:
In my personal opinion you are just causing yourself headaches by worrying about partitioning your server.

You say your using a FC attached SAN, what Raid are you running on it Raid 10, Raid 5?

This is what I would setup.
Raid 10 Array on the FC SAN
Deploy 1 Fixed Size Virtual HDD (ie Not Expanding)
Install everything in one partition.

You don't get any performance boost by having separate partitions so don't even bother.

Here is the info on Exchange Prerequisites:
http://technet.microsoft.com/en-us/library/bb125224.aspx 

But according to this I think you should be right
By default, the schema master runs on the first Windows Server 2003 or Windows Server 2008 or Windows Server 2008 R2 domain controller installed in a forest. The schema master must be running any of the following:
Windows Server 2003 Standard Edition with Service Pack 1 (SP1) or later (32-bit or 64-bit)
Windows Server 2003 Enterprise Edition with SP1 or later (32-bit or 64-bit)
Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)
Windows Server 2008 R2 Standard or Enterprise
0
 
kswan_expertAuthor Commented:
So you reckon create a giant C: no thin provisionng and install all in here?  i've not heard of this setup before.

For exchange 2007 i had some notes that you needed the following installed on the DC you were going to Prep AD from

Install correct version of MMC  - KB907265
Install Microsoft .Net Framework 2.0 – Dotnetfx.exe
Install Windows Powershell – KB926139
Install MS .Net Framewok 2.0 Hotfix – KB926776

but not sure for Ex2010
0
 
oneitnzCommented:
Sorry I'm not aware of any such requirements however I have never installed 2010 on a 2003 Server.

Microsoft recommends having your System Partition on Different Spindles to your Exchange Store however this would mean that you would have to provision your storage with Separate Raid Arrays for each Virtual Disk. In reality a Raid 10 Array of 4 disk will always out perform 2 Raid 1 Arrays.

If however your storage appliance is configured in Raid 5 you will probably notice a huge impact as Raid 5 is horrible when it comes to Write performance.

Regards
Brett
One IT
www.oneit.co.nz
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
ashok_523Commented:
Iam not sure about the array part but it is always advisable to have logs and database in different drives.
this is becasue in worst case , even if we lost one(Database or Logs) we can retrive the data using the other options
0
 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
Use Microsoft Storage Calculator to find out the space u need for DB and logs,you just cant guess it as too many things have changed in Exchange 2010 (eg, no SIS).

http://gallery.technet.microsoft.com/v144-of-the-Exchange-2010-1912958d

You can run schema prep on 2003 SP2 Schema master, no issues.
Exchange should be in native mode and AD forest and domain functional level should be Windows 2003 or higher.
0
 
oneitnzCommented:
I agree with ashok about having the redundancy by putting your Database and Logs on separate physical disks. However this is very 1999 as nowadays everyone in their right mind should be running Raid anyways so this makes it worthless. The chances of loosing your entire Raid array at the same time are very minimal, so, so long as your monitoring your Raid for any drive failures and more importantly have a Backup Solution in place (Raid does not remove the need for Backups) then your not going to get any speed benefit from putting logs and databases and OS on different partitions.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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