The following tables list the tasks that you complete on a regular
basis to keep the Avaya Modular Messaging system operating properly. The
first table lists the maintenance tasks for the messaging application server (MAS). The second table lists the
maintenance tasks for the Avaya Message Storage
Server (MSS).
Task |
Frequency |
Check the Windows 2003 Event Viewer for errors.
For Modular Messaging—MSS and Modular Messaging—Microsoft Exchange offers, click Start > Programs > Administrative Tools > Services. Double-click the monitor.msc icon on the MAS desktop.
For more information, see:
|
Daily |
Check the Modular Messaging Dialogic Port monitors for errors. For example, check the ports to identify if they are in a disabled state.
For more information, see:
|
Daily |
Check the Port Statistics report to verify that they take calls consistent with the hunt group.
From the MAS desktop, click Start > Programs > Avaya Modular Messaging > Reporting Tool.
For more information, see RT - Port Statistics Report. |
Daily |
Check the Alarm log. The log displays active alarms and resolved alarms. Use the log to review problems that the system detected on an MAS.
For more information, see:
|
Daily |
Check the Operation History Events log. Use the log to diagnose an event in the voice mail message.
For more information, see Overview of system logs. |
Daily |
Check the Key Performance Indicator (KPI) for Event ID 1531 on each MAS.
Each MAS sends the Event ID 1531 daily at midnight. Check the Event ID 1531 to review the user experience for that day.
For more information, see your administrator. |
Daily |
Verify that the unattended backup completed successfully.
For more information, see Check the backup log in the MSS maintenance checklist. |
Daily |
Follow IT processes for:
- Security procedures for virus scans
- Critical updates
- Windows backups
- Defragmentation (defrag)
- Check disk (chkdsk)
- Scan disk (scandisk)
Obtain the recommended schedule for these tasks from the customer IT representative.
Analyze the disk before running the Defragment command.
Note: The Microsoft guideline is to perform the tasks once a week.
For more information, see Messaging Application Server Administration Guide (pdf). |
As required by internal IT standards
Perform the Disk Defragmenter:
- During off-peak times
- After a major change to the application software
- After the addition of many files
- When a maintenance alarm in the software instructs you to run it
|
Perform an attended backup of the MAS followed by an attended backup of the MSS.
For more information, see:
|
Perform the backup task:
- After making major system changes
- After entering new subscribers
- When experiencing system problems to avoid losing information entered since the last unattended backup
- When a partial unattended backup occurs to avoid losing the data types that were not backed up
|
Restore MAS data.
For more information, see:
|
Perform the restore task:
- If MAS data are lost or corrupted
- If the system fails because of data loss
- If the hard disk fails
|
Check the Spool folder for unsent messages.
The Spool folder is located on the MAS at C:\Program Files\Avaya Modular Messaging\VServer\Spool
Note: The presence of undelivered messages can be normal if the MSS was unavailable. |
Once a week
As necessary, when subscribers complain that they have not received messages |
Check for available service packs to download from the Avaya Support Web site at http://www.avaya.com/support. |
Monthly |
Reboot the MAS on a regular basis.
Note: Microsoft does not support the MAS when the time period between system reboots is greater than 90 days. |
Once every 90 days for each MAS that experiences normal traffic volumes
Once every 30 days for each MAS that experiences high traffic volumes |
Task |
Frequency |
Check the MSS events to identify routine conditions and conditions that can lead to an MSS alarm.
For more information, see MSS events. |
Daily |
Administer and check the Subscriber Activity log. Use the log to investigate subscriber activity and to resolve reported problems.
For more information, see:
|
Daily |
Check the Alarm log. The log displays active or resolved MSS alarms. Use the log to complete the following tasks:
- Verify that the system cleared the alarms after the service procedures are complete.
- Troubleshoot intermittent problems that resolve themselves and then reoccur.
For more information, see:
|
Daily |
Check the Administration log. Use the log to review and investigate administrative entries that you can solve.
For more information, see:
|
Daily |
Check the Backup log. Use the log to identify errors that occurred during the backup.
Verify that the unattended backup was successful.
The unattended backup contains all the information necessary to restore the system to an operational state after a service-affecting event. However, the unattended backup might not restore the system to its previous state. Unattended backups occur each morning at 3:05 a.m.
For more information, see:
|
Daily |
Reassign local subscriber default passwords.
Reassign a subscriber default password if the subscriber forgets the subscriber password.
For more information, see:
|
As necessary |
Unlock a subscriber mailbox in the Voice Mail System Configuration (VMSC) program.
The system monitors the number of unsuccessful consecutive log-in attempts to a specific mailbox. The attempts can occur across multiple calls to the system. The maximum number of unsuccessful attempts is set in the Login Failures before Mailbox Lockout field. The system locks out the subscriber ID when the subscriber exceeds the maximum number of unsuccessful consecutive log-in attempts. The subscriber cannot access the system until an administrator unlocks the subscriber mailbox.
Before you unlock a subscriber mailbox, investigate why the mailbox became locked.
The Login Failures before Mailbox Lockout field is on the Subscriber tab of the Telephone User Interface dialog box.
For more information about log-in failures, unlocking a subscriber mailbox, and the VMSC program, see:
|
As necessary |
Check the reboot schedule. If required, reboot the system.
A system reboot refreshes the operating system resources and keeps applications running reliably.
For instructions about how to check the reboot schedule and
reboot the system, see:
|
Every 120 days |
Check the Linux system clock.
Note: To synchronize the time on the MASs with the time on the MSS, run the synctime.bat command on all MASs.
For more information, see:
|
Monthly and when a daylight saving time change occurs |
Add, delete, or modify local subscribers to maintain subscriber profiles that reflect current needs and staffing.
For more information about how to manage local subscribers, see:
For more advanced subscriber management, use the Mailbox Manager application.
For more information, see the Mailbox Manager documentation that accompanies the application. |
As necessary |
Administer remote subscribers.
A remote update can use one of your networking ports for quite some time.
Administer a subscriber manually when you want to administer a remote subscriber immediately but do not want to run a remote update.
For more information, see Administering
remote subscribers manually. |
As necessary |
Check the Internet Postmaster Mailbox for unsent messages.
The Internet Postmaster Mailbox Number is defined on the Configure Subscriber Management page.
For more information, see Defining MSS subscriber management parameters. |
As necessary or once a week |
Run traffic reports.
Use the traffic information to troubleshoot the system and to improve system efficiency.
For more information, see Overview of traffic reports. |
As necessary |
Run audits. An audit synchronizes the system software and the disk after you complete administrative changes. Also, run audits to allow the system to readjust itself after an alarm.
For more information, see Performing database audits on the MSS. |
As necessary |
Perform an attended backup.
For more information, see:
|
Perform the backup task:
- After performing an attended backup on an MAS
- After making major system changes
- After entering new subscribers
- When experiencing system problems to avoid losing information entered since the last unattended backup
- When a partial unattended backup occurs to avoid losing the data types that were not backed up
|
Restore MSS data.
Check the Restore log. Use the log to review information about any errors that occurred during the restore.
If the hard disk fails, install the new hard drive before you restore the data.
For more information, see:
|
Perform the restore task:
- If MSS data are lost or corrupted
- If the hard disk fails
|
Alternate the backup media.
At a minimum, alternate between two backup media. Avaya recommends that you alternate among seven backup media, each labeled with a day of the week.
For more information, see Managing the backup media. |
Daily |
For Modular Messaging—Microsoft Exchange offers, check the contents of the following for notices of non-delivery reports (NDRs):
- External caller mailbox
- NDR performance counter
|
As necessary |
Remove unused enhanced lists.
For more information, see Deleting an enhanced list. |
As necessary |
Check the Software Installation and Removal log. Use the log to review information about the installation, update, or removal of MSS software packages.
For more information, see:
|
As necessary |