Storage server

Number	Tasks	Links	Frequency
1	Check the events to identify routine conditions and conditions that can lead to a storage server alarm.	For more information, see the Avaya Aura^® Messaging Alarms and Events document.	Daily.
2	Administer and check the user activity log. Use the log to investigate user activity and to resolve reported problems.	For more information, see: Storage server logs overview User activity logs Configuring a user activity log Running an activity log report	Daily.
3	Check the alarm log. The log displays active alarms and resolved alarms.	For more information, see: Storage server logs overview Viewing the alarm logs	Daily.
4	Check the administration log. Use the log to review and investigate administrative entries that you can solve.	For more information, see: Storage server logs overview Viewing the administration history log Viewing the administrators log	Daily.
5	Check the backup log. Use the log to identify errors that occurred during the backup.	For more information, see: Viewing backup history Viewing backup logs	Daily.
6	Reset the local user password if the user forgets the user password.	For more information, see Resetting the voice mailbox password.	As necessary.
7	Unlock a voice mailbox account. Messaging automatically locks the system when the user fails to enter proper login credentials after a certain number of consecutive failed attempts. The Lock out users after field on the System Policies Web page determines the number of allowable consecutive failed attempts. The user cannot access the system until an administrator unlocks the user mailbox. Before you unlock a user mailbox, investigate why the system locked the mailbox.	For more information, see: Unlocking the voice mailbox account Viewing the locked out users report	As necessary.
8	Reboot the storage server.	For more information see, Shutting down the server.	As necessary or once a year.
9	Check the Linux system clock.	For more information, see Verifying the system clock.	Monthly and when a daylight saving time change occurs.
10	Add, delete, or modify local users to maintain user profiles that reflect current needs and staffing.	For more information on how to manage local users, see: Adding users Adding users from Active Directory Changing user properties Deleting users Viewing the local users report	As necessary.
11	Administer remote users. A remote update can use one of your networking ports for quite some time. Administer a user manually when you want to administer a remote user immediately, but do not want to run a remote update.	For more information, see: Remote updates Running a remote update manually Viewing the remote users report	As necessary.
12	Check the Internet Postmaster Mailbox for unsent messages. You define the Internet Postmaster Mailbox Number on the User Management > Properties for New User Web page.	For more information, see: Adding the postmaster mailbox Configuring the postmaster mailbox number	As necessary or once a week.
13	Check the uninitialized mailboxes report to identify mailboxes that were never initialized. This report is useful when you migrate from older Messaging releases. You can remove unused mailboxes and free-up unused licenses.	For more information, see Viewing the uninitialized mailboxes report.	Monthly.
14	Check the dormant mailbox report to identify inactive mailboxes.	For more information, see Running the system evaluation report.	Monthly.
15	Run traffic reports. Use the traffic information to troubleshoot the system and to improve system efficiency.	For more information, see: Viewing the Internet messaging traffic Running the traffic measurement report	As necessary.
16	Run audits. Audits can reconcile conflicts among databases by checking for inconsistencies and when possible, updating the information in databases to correct the Messaging problems.	For more information, see: Messaging database audit Performing the voice messaging database audit Running Audit	As necessary.
17	Back up the data.	For more information, see: Back up and restore overview Backing up system files	Nightly according to the routine automatic schedule. Perform the backup task as necessary: After making major system changes. After creating new users. When experiencing system problems to avoid losing information entered since the last backup. When a partial backup occurs to avoid losing the data sets that the system did not back up.
18	Verify that the backup completed successfully.	For more information, see Viewing backup logs.	Daily.
19	Restore the data.	For more information, see: Back up and restore overview Performing a restore	Perform the restore task as necessary: If the storage server data is lost or corrupted. If the system fails because of data loss. If the hard disk fails.
20	Remove unused enhanced lists.	For more information, see Administering an ELA List.	As necessary.
21	Check the software management logs. Use the log to review information about the installation, update, or removal of software packages.	For more information, see: Storage server logs overview Viewing the software management logs	As necessary.