The migration of an existing TM Server to a new freshly installed TM sever will be carried out with the following strategy. The new TM server will be installed according to specific instructions. Configuration files and user queries will be manually migrated from a source TM server to a target TM server. The configuration files are located under the main TM directory labeled MTC/ and contain user's credentials and personalized settings. These configuration files will replace the new TM system configuration files.
The personalized user queries will also be transferred from source TM server to target TM server. The queries are located as individual records in the SQLite database, therefore, various SQL commands will be performed to dump the source TM server query table and populate the new TM server query table.
Finally, the installer will have the option of manually migrating the old source TM system data (individual system traces) to the new TM server corresponding system folders.
Existing Phone QoS data will not be displayed through FADE after the migration. QoS information is included in the raw trace files which can be opened with external tools. The Telephony Control Server and RG QoS data will be displayed under the Performance tab after the raw files are reprocessed by DIPAZ.
Requirements for Migration to new Hardware
For the migration of an existing TM Server to a new freshly installed TM sever must be fulfilled some requirements.
Pre-Installation for Target Lotus Sametime Unified Telephony-TM
Some pre-installation steps are required for target TM installation during migration.
How to Extract TM System Names / RG Names
Extraction of the TM System Names and Corresponding RG Names from the Source TM Server is the first step to migration. This information is required for target TM installation. The system names and their corresponding RGs will have to be manually added through the installation, so that the new database schema matches the source TM database schema.
Installation of Lotus Sametime Unified Telephony-TM on Target Server
You need to have administrator rights to install TM. Login as the local Administrator or with a user account that has administrator's permission. Before you run the installation, the target system should be running Windows 2003 with SP2 and FTP enabled as indicated in the Pre-Install section.
Migration of Configuration between Source and Target TM
Migration comprises the steps: Exporting from the database and packing your queries, point the Telephony Control Server node to the new target TM server and migrating data between source and target TM (optional).
How to Export Query Table
The queries are located as individual records in the MySQL database, therefore, various SQL commands will be performed to dump the source TM server query table and populate the new TM server query table. The following procedure will dump the cannedqueries tables for each system in the source TM and store it in its corresponding source TM system folder.
How to Replace Configuration Files
The configuration files are located under the main TM directory labeled "MTC" and contain user's credentials, personalized settings, and system-specific configuration. These configuration files on the source server will replace the new TM system configuration files.
How to Stop DIPAZ Monitor
How to Import Personal Queries
Import the queries stored in the target TM "MTC" folder into its database.
How to Migrate Data Between Source and Target TM
This task describes how to manually migrate the old source TM system trace files to the corresponding target TM system folders; this folder contains the user FTP data as well.
Initial Configuration of TM Systems
This configuration part of the installation allows you to create TM systems/nodes. To activate tracing integration, at least one system needs to be configured in the server.