The TM V2 release has changed its database engine from MySQL to SQLite. Before upgrading to this new version from V1R3 or an earlier version, careful planning is necessary.
The processed trace data is stored in the current TM database engine along with additional configuration data. This data will not be automatically migrated by the upgrade process; therefore, before upgrading to the new TM V2R0 version, you have to decide on the strategy you want to follow.
The TM systems will be re-created in the new SQLite database engine.
The trace files collected from the Telephony Control Server, Branch, and RGs will be preserved in the Tracedata folder during the upgrade or moved to a storage folder called TRACES.OLD depending on the upgrade strategy planned by the administrator.
During the upgrade, the TM administrator will be prompted to indicate what upgrade strategy will be followed and based on the answer, either all trace files will be reprocessed again by the DIPAZ service after the upgrade is completed or no data will be re-processed.
The amount of processing time that will take for the data files to be re-processed will depend on the number of trace files in the Tracedata storage directory and the Days in Rear configuration parameter set for each TM system.
After the upgrade is completed, DIPAZ will age the trace data files in the TRACES.OLD folder with the same frequency as it is configured for the regular tracedata folder based on the Clean Days in Rear parameter configured for each TM system.
The Quality of Service data for the phones will be lost during the upgrade since this data is collected directly into the database by the Phone TrapCollector. This data is not critical as it is also captured by the Telephony Control Server can be viewed through the Telephony Control_Voice view -> Performance tab in FADE if the option to re-process trace files is chosen.
User accounts will be migrated.
Personal queries will be migrated; however, due to syntax differences between MySQL and SQLite, they may not function properly and will probably require either fixing the query definition or re-creating the query by the query owner.
Any custom reports or applications written by users that interfaced directly with the MySQL database will no longer work. They will have to be redesigned to work with SQLite.
Parent topic: Administration Tasks for Trace Management
Migration from an Earlier TM Version to V2
Make sure you have enough free disk space in Tracedata
to accommodate the existing trace files and the new files that will be transferred after the upgrade. The DIPAZ monitor will age the preserved files based on how you configure the Clean Days in Rear
parameter, so calculate your disk space depending on what upgrade strategy you will follow.
The MySQL software will not be uninstalled; neither the MySQL old database be removed by the TM upgrade process.
It will be the responsibility of the administrator to uninstall MySQL and delete the old database from the TM server after the upgrade has been successfully verified.
How to Perform an Upgrade Installation
Manual Upgrade of Additional 3rd Party Software
Some 3rd party software isn't needed for Lotus Sametime Unified Telephony or TM anymore. That's why a case sensitive decision is needed for upgrading.