Exchange db/logs reads and writes query

On an Exchange 2007 Server, we have 5 SG's. Each SG has one Store only.

I would like to measure the amount of disk activity and get a baseline in case we need to reference this during times of trouble.

Questions -

1. Am I correct in thinking that

- The logs would be very write intensive but not read intensive-. The DB would be very read intensive but not write intensive

2. Does it mean anything if the logs are read intensive and the DB is write intensive too?

3. Should the activity be constant or spiking all the time?

4. What should I be looking for if there is a problem?

On a Windows 2008 Server, SCC cluster.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You should read this article on "Configuring, validating and monitoring your Exchange 2007 storage" and the associated links within since it provides you with all that you need and more.
kam_ukAuthor Commented:
Thanks guys, but doesn't answer the below three questions:

2. Does it mean anything if the logs are read intensive and the DB is write intensive too?

3. Should the activity be constant or spiking all the time?

4. What should I be looking for if there is a problem?
One of the reasons I sent you the article is because this is a fairly broad subject and really you should be measuring the server based upon the criteria in the article so that you have a better idea of whats expected, the ramifications etc.   That said

1. Strange that the logs are read intensive, are you perhaps running an Anti-Virus product that is scanning the log folder?

2. As far as the DB is concerned it will depend upon the type of activity thats taking place, i.e. there will be both reads and writes.

3. As far as the load remaining constant or spiking, again thats difficult to say since I don't know enough about your organization, but overall I would think you would see spikes in DB usage first thing in morning as people log on an then again post lunch breaks.  

5. Other things that could cause a spike would be Exchange Database Backups as we as AV scanning

5. As far as where to look for a problem, I would read the article I forwarded you to get an understanding of;

A. how your system is setup vs the recommended settings/configurations  in the article
your system by measuring the baseline results and then looking at the latency

B. Measure your systems performance

C.  How are your users doing, i.e. any complaints about slowness etc? Now just because you  receive complaints doesn't mean its the server configuration, i.e. it could be the local machine, the network or other issues.  What this gives you though is another set of data points to analyze, i.e. are there other users experiencing the same issue?  What are the similarities between users, time of impact etc

6. Download and run

A. Microsoft Exchange Best Practices Analyzer

B. Microsoft Exchange Troubleshooting Assistant

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Thanks for the points
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.