Recommended scheduled maintenance
Introduction
To ensure optimum system performance, we suggest that you follow the recommended scheduled maintenance.
| Maintenance | Schedule |
|---|---|
|
Back up message files. Perform the following two levels of backups:
|
Ongoing backups�as needed. |
| Archive the message database | How often you archive your message
database depends on the size of your database and the size of your messages.
When you receive a �database is full� alarm, you should consider archiving your
database especially if the alarm is a 90% full alarm. Run the archive when
your system load is low.
Below are some figures to help you determine when to archive your MCMessages database:
Based on the above information, the MCMessages and MCArchive databases should grow no larger than 30,000 records. |
| Manage and update the dictionary | As needed. |
| Managing the overflow queue | When overflow queue exceeds 5,000 messages. |
| Clean up temp directory | Remove files that are over a week old. |
| Clean up winnt\system32\Logfiles | Either disable logging or clean up files on a daily basis. |
| Check performance characteristics of your system | At least once a month or more frequently as needed. For example, if you are experiencing an increase in mail volume then you may want to check system performance more than once a month. |
| Backup log files | As needed. |
|
Copyright © 2001 Avaya Inc. All rights reserved. Modified: March 19, 2001 |
|