Hi All, I am (as I've posted a few times now) rolling out my combined HT/CAS server and I have a quick question regarding disk/performance and the placement of HT logs, databases, etc. I found this post from a last year: http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/e735abb1-ae4c-488b-949d-d4aabe21ad58 and I found this entry on TechNet in regards to moving the Transport Queue database and logs: http://technet.microsoft.com/en-us/library/bb125177.aspx. Both links talk about the the Queue database and logs, but I see there are a few others that I was wondering if I should consider moving as well. Namely (as specified in the EdgeTransport.exe.config), the IpFilterDatabase and the TemporaryStoragePath, both of which are living in Program Files\Microsoft\Exchange Server\V14\TransportRoles\Data by default. Is there any benefit to moving around? My current server is configured as such: -Boot/System Volume (C:) 30GB -Program Files (D:) 10GB -Data/Databases (E:) 30GB -Logs (Z:) 30GB My guess is that I'm over-complicating this, but I was planning on moving as much of the "working" data to E:\ as possible. Thanks in advance!

you need not move these unless you have found enough evidenced in favour. what you need to do though is exclude from the file level scanner if you have anyDhruv

Hi Dhruv, Thanks for the reply. Any idea about how large these databases get? I mean, after all, it is just a "Queue" and a "Temporary" work space we're talking about here, right? My environment is relatively simple, if not large (from a data standpoint). I have one domain with approximately 200 mailboxes and the average size per mailbox is 1GB (despite sizes ranging from 10MB to 10GB) and average message size is around 80KB. I'm starting to think that I can do away with the E: volume and have the databases in D: (might have to grow D: a bit though, but that's not a problem). What do you think? Oh, and I already found the Exchange 2010 AV consideration/exclusions list. ;) Thanks again!

your databse disk needs to have at least 2.2 TB + 20 percent of volume size for indexing assuming 14 days retention period low maailbox profile (20 recived / 5 sent permailbox ) and log directory depends how frequently you take backup (400 logs will be generated per day ) about IpFilterDatabase The IP filter database stores the IP Allow lists and IP Block lists that are part of connection filtering and will be static. and will not change frequently and TemporaryStoragePath is not expected to grow either , you would need always 4GB of free space where you plan to put the mail.que and transaction logs Dhruv

Oh, I'm not talking about the database & logs of the Database server role, just the databases/data of the Hub and CAS roles (which are installed on one server; Database role will be a separate server). I'm thinking that the space and performance of the IpFilter, TemporaryStoragePath, and Queue would function fine on the same volume as the Exchange install. Maybe I increase the volume to 20GB though. After that I don't even think I'll need the E: volume. What do you think?

yes, you can put the the install files and the transport databse in the same vollume and 20GB will be enough, you will need to moniter the mial.que though you need to have at least 4 gb all the time The database (mail.que) does not store items indefinitely, and the capacity reserved should be the average message size multiplied by the maximum queue, 80kb*200*25 ( assuming low profile mailboxes ) Dhruv

Awesome; thanks for the insight and the help you've provided to me thus far; it is greatly appreciated!