Archive message records
Why archive message records?
The size of the active message database is eventually limited by the available storage capacity of the system, and excessively large databases can have a harmful impact on system performance. Because of these factors, you should monitor the size of your database and periodically create an archive of message records.
Planning
Planning the timing of your archive is important because the messaging software's archiving process can slow performance of the system. You must also keep in mind the capacity constraints of the message database. As the capacity of the database is reaching its maximum, the messaging software will generate alarms. Tthe messaging software generates alarms at 80%, 90%, and then 95% of the database's capacity. When the maximum capacity of the database is reached, the messaging software will stop polling for messages. More information about capacity constraints can be found in CentreVu Internet Solutions capacities.
Before performing an archive, verify that there is sufficient free disk space for the archive database in the location you select for storage. The exact amount of space required depends on the number and size of messages that will be archived. The maximum required archive database space will not exceed the size of the active message database.
Archiving options
The messaging software provides you with two archiving methods:
Archive from the graphical user interface (GUI). See Perform an archive from the Archive Utility window for procedures on running an archive through the GUI.
Archive from the command line interface. You can use this method to schedule an archive. (See Run an archive using the command line file for procedures on running archives from the command line interface.)
Archive procedures
Important!
If you have a non US-English installation of the messaging software, see Non US-English installations before running the archive.
Tests have shown that using the MCArchive tool to archive a MCMessages database containing 30,000 messages takes about 47 minutes (archiving conducted while the messaging system is stopped). The procedure to run the new archive tool is as follows:
Ensure that the target database for archiving (MCArchive) exists, and there is adequate disk space to contain the archive. (From SQL Server Enterprise Manager, right click on MCArchive under Databases to find the disk locations for MCArchive's data and transaction log files).
From SQL Server Query Analyzer, open and then execute the MessagecareIndexes.sql script in the SQL Tools->Install folder in the Message Care installed directory.
From SQL Server Query Analyzer, open and then execute the MessagecareIndexesForArchiveIndexes.sql script in the SQL Tools->Install folder in the Message Care installed directory.
From SQL Server Query Analyzer, open and then change the default database from master to MCMessages . Execute the spMCArchive.sql script in the SQL Tools->Install->Stored Procedures folder in the Message Care installed directory.
Run the Archive utility either from the command line interface (see Run an archive using the command line) or from the Archive Utility Window (see Perform an archive from the Archive Utility window).
Perform an archive from the Archive Utility window
You can perform an archive operation at any time by using the simple graphical user interface provided by the messaging software for this purpose.
From theWindows NT desktop, click on the Start button and select Start->Avaya Message Care->MCArchive.
Result:
The Message Care � Archive Utility window appears.
Enter your archiving criteria (number of days messages have been closed, blocked, and failed), and then click on the Archive button to start the archiving process.
The archive utility will display the number of messages that have been successfully archived while the archive is in progress.
Run an archive using the command line
To perform an archive using the command line, do the following:
Open the MS-DOS Command Prompt window.
Navigate to the \bin directory under Program Files\MessageCare.
Type the following command: mcarchive /i <# of days>
If you do not enter the /i variable, then the Archive Utility window appears.
# of days = the number of days for which you are archiving closed, blocked, and failed messages.
For example, c:\>Program Files\MessageCare\bin>mcarchive /i 7
Post archive tasks
After an archive is completed, perform the following post-archive tasks:
Examine the Windows NT Event Log to ensure that no errors have occured due to the MCArchive application.
Examine the warchive.txt file under the logs folder of the messaging software's installation directory and also examine the Windows NT Event Log to ensure that no errors have occured due to the MCArchive application.
The archiving process generates many database activities which are logged in the transaction log.
Reclaim disk space on the SQL Server's transaction log for the MCMessages database by doing the following:
Double-click MCMessages under Databases in SQL Server Enterprise Manager.
Select the General tab.
From the General tab, click on truncate transaction log located in the shaded Backup frame.
Canceling the archiving process when using the Archive Uitility window
You can cancel an archive procedure at any time after it has been initiated by clicking on the Cancel button. However, if you decide to terminate the process before all of the messages have been archived, be aware that the sequence in which messages are archived depends only on their storage location on the disk drive used for the active messages database. Therefore, cancelling an archive procedure after only a portion of the messages have been stored in the archive database does not mean that those messages archived before cancelling comprise the oldest records.
Important!
If you are using the command line interface and end the archive process through the Task Manager, then successful archive completion is not guaranteed.
Copyright © 2001
Avaya Inc.
All rights reserved.
Modified: March 19, 2001![]()