If you only have two LUNs, what is the point in splitting it up so much? I also see no value at all in installing Exchange on its own drive, never done that myself. I would have a larger C drive, and install all binaries there, then have another partition for the message tracking, protocol logs etc. 20gb log drives is very small, particularly for the migration phase - if you are bringing in 200gb of data then you are going to generate 200gb of logs, unless you are going to run with circular logging enabled for the migration. Have you run the parameters through the Storage configuration tool from the MS Exchange team blog? Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

On Wed, 29 Feb 2012 11:32:01 +0000, Sembee wrote: > > >If you only have two LUNs, what is the point in splitting it up so much? > >I also see no value at all in installing Exchange on its own drive, never done that myself. I would have a larger C drive, and install all binaries there, then have another partition for the message tracking, protocol logs etc. A 50GB C: drive will seem pretty crowded after a while. Patches, differnt .NET versions, etc. will eat up space pretty quickly. >20gb log drives is very small, particularly for the migration phase - if you are bringing in 200gb of data then you are going to generate 200gb of logs, unless you are going to run with circular logging enabled for the migration. Yep. He wouldn't be able to move more than, say 15 mailboxes into each storage group at one time. I suppose if the move to the new server can take several days (or frequent backups during the moves) the log drives would be sufficient. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Wed, 29 Feb 2012 11:32:01 +0000, Sembee wrote: > > >If you only have two LUNs, what is the point in splitting it up so much? > >I also see no value at all in installing Exchange on its own drive, never done that myself. I would have a larger C drive, and install all binaries there, then have another partition for the message tracking, protocol logs etc. A 50GB C: drive will seem pretty crowded after a while. Patches, differnt .NET versions, etc. will eat up space pretty quickly. >20gb log drives is very small, particularly for the migration phase - if you are bringing in 200gb of data then you are going to generate 200gb of logs, unless you are going to run with circular logging enabled for the migration. Yep. He wouldn't be able to move more than, say 15 mailboxes into each storage group at one time. I suppose if the move to the new server can take several days (or frequent backups during the moves) the log drives would be sufficient. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I have been struggling in designing the best approach for my Exchange 2007 Mailbox Role server, this server will serve 800 users with avg of 1GB per mailbox. What are the risks or possible performance degrade with the below setup? New Exchange 2007 SP3 mailbox role server on vmware vsphere 5, Win03 SP2 64-bit, 4 virtual cores, 16 GB Ram, on SAN storage device: VNX5300. - LUN A (Raid 10), 120GB - LUN B (Raid 5), 1100GB C: system (Basic disk, Lun B, 50GB) D: Exchange server (Basic disk, Lun B, 50GB) H: SG1/DB1 (Dynamic Disk, Lun B, 250GB) I: SG1/LOG (Dynamic Disk, Lun A, 20GB) J: SG2/DB1 (Dynamic Disk, Lun B, 250GB) K: SG2/LOG (Dynamic Disk, Lun A, 20GB) M: SG3/DB1 (Dynamic Disk, Lun B, 250GB) N: SG3/LOG (Dynamic Disk, Lun A, 20GB) O: SG4/DB1 (Dynamic Disk, Lun B, 250GB) P: SG4/LOG (Dynamic Disk, Lun A, 20GB) Q: Public Folder/LOG (Dynamic Disk, Lun A, 20GB)

If you only have two LUNs, what is the point in splitting it up so much? I also see no value at all in installing Exchange on its own drive, never done that myself. I would have a larger C drive, and install all binaries there, then have another partition for the message tracking, protocol logs etc. 20gb log drives is very small, particularly for the migration phase - if you are bringing in 200gb of data then you are going to generate 200gb of logs, unless you are going to run with circular logging enabled for the migration. Have you run the parameters through the Storage configuration tool from the MS Exchange team blog? Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.