MOM threshold settings for warning when Exchange 2003 Mail Stores get too large

Hi,
there is no recommendation in this topic because it vary from customer to customer, it depends how you d backup, your backup technology/speed and storage size

we usually monitor the space of the database harddisk and logs harddisk and create alerts when 20% space is only available, this is a riugh estimation for some customer 20% can be consumed so fast so they monitor 40 or 50%

Thanks,  can you provide a link to an article(s) that talks about this? I would need to use this to back up my information. Thanks.

the only one that exists is for scom here:
http://ops-mgr.spaces.live.com/Blog/cns!3D3B8489FCAA9B51!220.entry

Great information, thank you.

Just have a few more questions related to Exchange, MOM, servers running SQL 2005 and servers that are used for shared Company data, would the same common monitoring/alert threshold of 40 or 50% apply across the board? Or would it vary from one type of server to the next? What thresholds are recommended for an Enterprise environment of about 130 servers? What is generally recommended?

When monitoring the size of Exchange Stores and Transaction Logs, what should be considered? How quickly do Exchange transaction logs in 2003 grow?

If MOM is running in a production environment and I want to install the exact same version MOM on a VM in a test environment which is on a different domain but need to import the same rules and configuration from the current production setup in order to test changes to the rules, how can I do this successfully? What is the recommendation or best way to go about doing this? Can you provide step by step documentation on how to do this without breaking the MOM system running in production?

Still looking for an answer to the following only:

If MOM is running in a production environment and I want to install the exact same version of MOM on a VM in a test environment which is on a different domain but need to import the same rules and configuration from the current production setup in order to test changes to the rules, how can I do this successfully? What is the recommendation or best way to go about doing this? Can you provide step by step documentation on how to do this without breaking the MOM system running in production?

Can I get any help on this please?

Sorry, I forgot replying on you.
as you said it will vary so much from organization to another, generally we monitor 90 percent processor utlization, 80% memory consumbtion and 85 % free memory, thos are general it will vary due to server roles and organization's requirements.

for Exchange monitoring, Yes it is about how fast your disks will be filled, and how fast you can provision new storage or backup the storage to free the space.

you can create all of the configuration in custom management pack, export it and then import it in the new environment.

I would highly recommend using SCOM not MOM

Thank you for your reply, I have another question with regards to the Exchange Rules, with multiple threshold settings applied, if all components (OS, DB, Transaction Logs, SMTP Queues, Pagefile) are on the same drive or volume, which of the following attached rules will apply? Will the warnings/alerts work properly if everything is on the same volume? Or will it only work if they are broken up on different volumes/drives? (Please view attachment for list of Rules)


Exchange-Rules.doc

Hi,
Sorry to say that but no, it will detect that the the drive is full but you will have to investigate what causes the drive to be filled.
so it will monitor thedrive but not specific content within the drive.

hope that my answer helped

The “check free disk space” rule creates the following event IDs based on the following criteria:

'   9971 - error for all disks

'   9972 - warning for all disks

'   9973 - error for disks with SMTP queues

'   9974 - warning for disks with SMTP queues

'   9975 - error for disks with Exchange log files

'   9976 - warning for disks with Exchange log files

'   9977 - error for disks with log files and a queue directory

'   9978 - warning for disks with log files and a queue directory

 

The parameters (thresholds) that are used for notification is as follows:

All Disks: %free space for error alert
 
All Disks: %free space for warning alert
 
Log Disks: %free space for error alert
 
Queue Disks: %free space for error alert
 
Log Disks: %free space for warning alert
 
Queue Disks: %free space for warning alert
 

 

There is no parameter for smtp queue and log volume. So if all my eggs are in one basket and I set a 20% warning threshold for the TL and 15% warning threshold for the smtp queue, the question is when the check free disk space runs will it create event id 9977 and/or 9976 and/or 9974? Thank you.

 

Not at this moment, thank you.