Revision as of 21:16, 7 May 2007 by Preycor
GroupWise Maintenance Best Practises
Use this list of steps for scheduled maintenance:
- Check and fix the structure of the information store nightly. Create an event (and enable it on each POA) that checks the structure of User, Message, and Document databases each evening during the week. Schedule this operation to run before the nightly backup.
- Check and fix the contents of the information store weekly. Create an event (and enable it on each POA) that checks the structure and contents of User, Message, and Document databases over the weekend. Schedule this operation to run following the Friday night backup. Review the log files Monday morning to determine the health of your message stores.
- Run Expire and Reduce to enforce the retention policy. Run Expire/Reduce on the message store at least weekly to enforce mailbox retention policies.
- Run Reduce Only to manage database sizes. Run Reduce Only on the information store at least weekly to manage the sizes of the GroupWise information store databases. Note: It is unnecessary to perform a Reduce Only if expire/reduce is run. After expiring, the reduce is automatically run.
- Leave "Nightly User Upkeep" enabled and set to occur early morning, after midnight. Leave the Nightly User Upkeep option on the POA enabled so uncompleted tasks are pushed forward to the next date on the calendar, deleted items are purged from the Trash folder according to the "Empty Trash / Automatic after" setting, and Personal Address Book entries are synchronized with the corresponding System Address Book entries (in case users are moved).
- Leave Quickfinder Indexing enabled. Leave Quickfinder Indexing enabled so Find activities are returned more quickly and less demand is made on the POA for each Find.
- Lock Cleanup Options to "Manual Delete and Archive." This will force users to choose which items they wish to store in their GroupWise Archives, preventing unnecessary expansion of archive directories. Cleanup should be performed via scheduled maintenance and should be done in accordance with your e-mail policy.
- Lock the archive path to the network "USERS" volume. Lock the path to a drive letter that is map-rooted to the user's home directory so that the setting will correctly apply to all users. You may also choose to place space restrictions on users to discourage abuse of the archive. With archives on the network, the administrator has the ability to back up user archives and can run maintenance on them without visiting user workstations. Do not store GroupWise archives on the mail volume.
- Set mailbox size limits. Locking the size of user's mailboxes allows you to control the size of the information store; users can see the space utilization of their mailbox from the GroupWise 6 client under Tools | Check Mailbox Size.
- Set message size limits. GroupWise 6 and above allows you to set a limit for the size for both internal (within the GroupWise system) and external (i.e., Internet mail) messages. Again, establishing this policy allows for greater control of the size of the information store as well as messaging traffic.