Migrating and upgrading ITM from Windows 2003 to 2012
yewhoongng 120000JSN6 Visits (9452)
A customer is planning to move from their existing out of support Windows 2003 OS to Windows 2012 R2 64bit. As part of this change, their existing ITM server components (HUB, TEPS, TDW, RTEMS) will need to be migrated/upgraded too.
Their current ITM version is 6.23FP2 running a physical Windows 2003 server and they intend to move to ITM 6.3FP4 running on virtual Windows 2012 R2 64 bit. Their TDW will also need to be migrated from DB2 9.5 to 10.1.4
1. Windows 2012 R2 64bit OS does not support ITM 6.23FP2 server components
2. Window 2003 does not support ITM 6.3FP4 server components
3. In place upgrade of the 6.23FP2 TEMS, TEPS and TDW to 6,3 FP4 on existing Windows 2003 is not officially supported.
4. In place upgrade of Windows 2003 to Windows 2012 while retaining ITM 6.23FP2 is not officially supported.
All the TEMAs are connected to the Remote TEMS via a DNS alias. ie using hostname.
No configuration changes will be made to TEMAs.
I came up with the following procedure to get this done. I plan to use a intermediary Windows 2008 OS which supports both 6.23FP2 and 6.3FP4. I have divided the work into pre-migration and migration steps. Ensure all steps are tested in pre production first and ensure there is a back out plan
Remove all application support from the 6.23 FP2 HUB TEMS for all TEMAs which will not be used in the final 6.3FP4 environment.
Start by doing a Database Health Checker on the current 6.23FP2 HUB TEMS. There are rare cases where objects are in a state where they cannot be FTO synchronised.
Install a new 6.23 FP2 HUB TEMS onto a Windows 2008 server. Ensure all the application support are the same as the existing 6.23 FP2 HUB TEMS.
Configure the Windows 2003 HUB TEMS as the acting hub and the windows 2008 HUB TEMS as the standby HUB. That will start synchronising the EIB files between the 2 HUB TEMS. Let it run for at least one hour to complete all the syncing. There will be a long services of messages in the TEMS operations log.
Next install a new 6.3.FP4 HUB TEMS on the Windows 2012 server. Install the same application support for the TEMAs as the ones on the windows 2003 HUB TEMS. Also install the 6.3FP4 64bit WPA/SPA application support files.
Next install the new 6.3FP4 Remote TEMS on Windows 2012, with the same application support for the TEMAs on the Windows 2003 Remote TEMS. Configure them but don't start them. The new RTEMS will use the same DNS alias as the old windows 2003 RTEMS later on but for now no TEMAs are connected to any of the new Remote TEMS
Create new DB2 10.1.4 TDW, install and configure the 6.3 FP4 64bit WPA/SPA but don't start these agents yet.
Install new 6.3 FP4 64bit TEPS on the Windows 2012 server and install the same TEMA support files too. Configure to use the Windows 2012 6.3 FP3 HUB TEMS. Also install 6.3FP4 64bit WPA/SPA application support files.
At this stage you should have the foollowing:
a. Windows 2003 6.23 FP2 HUB TEMS running in sync with an existing Windows 2008 6.23 FP2 HUB TEMS as the standby HUB TEMS
b. Windows 2012 6.3 FP4 64 bit HUB TEMS, TEPS running
c. Windows 2012 6.3 FP4 64 bit WPA/SPA configured but not running
d. Windows 2012 6.4 FP4 64bit Remote TEMS configured but not running.
Stop the WPA/SPA on the Windows 2003 TDW to stop all activity on the TDW.
Stop and unconfigure the Hot Standby option on the windows 2008 HUB TEMS.
Stop and unconfigure the Hot Standby option on the windows 2003 HUB TEMS.
Upgrade the Windows 2008 6.2.3PF2 32bit HUB TMES to a 64bit 6.3FP4. The HUB TEMS can be upgraded in place from a 32bit to a 64bit version. Also install the 64bit WPA/SPA application support files on the Windows 2008 HUB TEMS.
Configure the windows 2012 HUB TEMS to use FTO pointing to the Windows 2008 HUB TEMS. Ensure this setting is added first into KBBENV of the Windows 2012 HUB TEMS
This is a one way FTO usage known as Hot Standby. As above this is a one way sync so no changes is required to the Windows 2008 HUB TEMS. The windows 2012 HUB TEMS is started for backup purposes only. This is not an actual FTO configuration but it uses FTO logic to get the job done.
Start the Windows 2012 HUB TEMS and wait until the sync is complete. It will run at a fairly high utilization and then drop low, should take around 1 to 2 hours maximum.
Now stop the Windows 2012 HUB TEMS and unconfigure the FTO option. Now the windows 2012 HUB TEMS should have all the latest EIB files from the windows 2008 HUB TEMS.
Reconfigure the Windows 2003 TEPS to point at the windows 2012 HUB TEMS. This is to ensure that the TEPS database has information relevant to the windows 2012 HUB TEMS. When reconfiguring the portal server on windows system for a different monitoring server, a window is displayed asking if a snapshot of the portal server data should be taken. NO is the correct response when reconfiguring the portal server for a hot standby monitoring server because the same portal server data is relevant to both the primary and hot standby monitoring server.
Log into windows 2003 TEPS using a TEP client and double check that all situations, workflow policies, historical configuration are still the same as before. MSL should also look the same. There should also be outstanding events. This information is now coming from the new Windows 2012 6.3FP4 HUB TEMS.
To populate the new 6.3 FP4 TEPS database, use migrate-export.bat on the older 6.23 FP2 TEPS and then use migrate-import.bat to import the saveexport.sql on the new 6.3FP4 TEPS. Run buil
Log into the 6.3FP4 TEPS and double check that the historical configuration. They should be the same as the older Windows 2003 ITM environment.
As for TDW data, run the ITM Schema Publication tool from the 64bit SPA to create SQL scripts for the detailed and summarised tables that needs to be migrated. This task should be performed after SPA is installed and configured but before the WPA/SPA is started for the first time
The command line is tdwschema -rspfile response_file
It will generate the following SQL files for the products specified in the response file.
These SQL files need to be executed in sequence on the new 10.1.4 DB2 TDW using the db2 client tool. Once executed, you can now migrate over the existing detailed and summarised tables from the old 9.5 DB2 TDW.
Once all the tables are migrated, you can now configure and start the new 6.3FP4 Remote TEMS, WPA and SPA.
At this stage, you should have the following
a. Windows 2012 6.3FP4 HUB TEMS with all the EIB information form the older Windows 2003 HUB TEMS (via the temporary windows 2008 HUB TEMS). The EIB should include all the situations and managed systems list. The 6.3FP4 WPA/SPA TEMA is now connected to the HUB TEMS
b. Windows 2012 6.3FP4 TEPS with the same TEPS DB content as the older 6.23FP2 TEPS, which includes all previous workspaces, users and historical configuration.
c. Windows 2012 6.3FP4 TDW populated with the same detailed and summarised data as the older 6.23FP2 TDW.
d. Windows 2012 6.3FP4 Remote TEMS connected to the 6.3FP4 HUB TEMS with no agents connected.
Open up a TEP Client to a Windows 2012 TEPS and double check that all situations, workflow policies, historical configuration are the same as before. MSL should also be the same. Any outstanding events should also be transferred to the new environment. The newer 64bit SPA/WPA should appear online along with the 2 new Remote TEMS.
Change (with the assistance of the network team) the existing Remote TEMS DNS alias from the older 6.23FP2 Remote TEMS to the newer 6.3FP4 Remote TEMS so that all the TEMAS will now communicate to the newer 6.3FP4 Remote TEMS. The TEMAs won't know that their Remote TEMS have actually changed since they're still communicating using the same DNS alias.
Open up a TEP Client in the new 6.3FP4 environment and check that all the TEMAs are now appearing online. Also check that historical data are now going into the new 6.3FP4 TDW.