Novell Home

Cool Tip: Building a Better Disk Check Event

Novell Cool Solutions: Tip
By Jonathan Laudicina

Digg This - Slashdot This

Posted: 20 Jan 2005
 

Its been my experience that Disk Check Events are an under utilized feature amongst GroupWise administrators. Here's an example of how they can be leveraged and in many cases save an administrator's butt. Here's the documentation link for starters Preventing the Post Office from Running Out of Disk Space, but read on here for more.

If internal policy and politics prevents you as an administrator from restricting mailbox size or attachment size, consider setting up staggered Disk Check events to notify you of an impending low disk space situation on your mail volume. By default, the POA is enabled to check disk space every 5 minutes. It's up to the administrator to define the actions that are taken after those checks...

I've defined 3 staggered Disk Check Events...the 3rd event will tell the POA to stop processing mail, and in my example here, also delete attachments larger than 30MB. The other 2 events are for notification purposes only, so I don't want them to do the Stop Mail Processing activity. This is all defined on the POA object, under Scheduled Events.

My Events:

Disk Check Event 1, named: Poor Performance Notify:

This event will be triggered when the POA detects that the server has 19% free space on the volume. (anything below 20% is almost guaranteed to have negative impact on performance so...) At 19% free the POA will perform a MailboxStats configured to report on all attachments larger than 30MBs. It will email the mailadmins@mycompany.com distribution list and provide the report and a customized message about the event. The mail administrators can then examine the report and pursue action with the offending users. This gives administrators the opportunity to prevent low disk space problems before they get too severe.

The Stop Mail Processing value is set to ZERO % because I define Stop Mail Processing in Event 3.

Click the Notification Tab at the bottom of the MailboxStats, Scheduled Event Action configuration window in ConsoleOne and be certain to enable the "Notify administrator if action fails".

Disk Check Event 2, named: Low Disk Space Notify:

This event will trigger an action at 5% of free space. it will email the mailadmins@mycompany.com of the CRITICAL situation and include another large attachment report. This again allows the administrators to take action but stress more critical terms in the customized message. The Stop Mail Processing value is set to ZERO % because I define Stop Mail Processing in Event 3. Click the Notification Tab at the bottom of the MailboxStats, Scheduled Event Action configuration window in ConsoleOne and be certain to enable the "Notify administrator if action fails".

Disk Check Event 3, named: Low Disk Space Actions:

This event will trigger an action at XX MB of free space. XX should be defined in your system at minimum of >= your largest GroupWise DB file; usually this will be your largest OFMSG\MSG##.DB file, or 150MB whichever is larger.

I've configured this event to perform an Expire/Reduce Messages (instead of a MailboxStats like the first 2). My Expire/Reduce Messages will automatically strip out all attachments larger than 40MB. It will also Empty all Trash older than 1 day. This is last resort, stop-gap prevention of running the server out of space.

For me its far easier and much better to restore a few large attachments for a few users than to risk and recover from the corruption of a ZERO space mail volume. For most shops, its better to delete these attachments than take hours of downtime to recover from the potential corruption...

Lastly, this 3rd job is enabled to Stop Mail Processing at 100MB free space.

The Expire/Reduce Messages job results are emailed to the mailadmins@mycompany.com distribution list when the job completes.

This is just an example of how you can leverage the existing features of your POA. There are lots of events that can be triggered. Apply your knowledge of your environment and configure your events as needed.

It might save you a lot of headache.

Good Luck,
-JL


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell