IBM Support

Making your life easier: Backuping up our TEPS Database

Technical Blog Post


Abstract

Making your life easier: Backuping up our TEPS Database

Body

 

Newly I have come across with someone who didnt have a TEPS backup collected from ITMs tool and having to recover by TSM the full system (TEPS/DB) because someone accidentally deleted custom navigators. So, eventually I have decided to write this blog to show how quick, how easyis to keep up a right TEPS DB backup in case some problem occurs to our TEPS and avoiding to miss our work and waste our time.

 

It is true that our companies can have a policy backup with some tool like TSM, DB2 backupor by copying the full filesystem/directory where ITM DB2 is located but in these cases when we have to recover a TEPS we depends on another teams, we have to open request to another departments, etc and normally we have to wait not giving service and hearing the phone ring and ring and ring.

Nothing to say, if the hard disk of our TEPS crash or the machines where TEPS is located has some serious problem, we will have to wait until hard disk is changed, is up and restored puff .. for that moment our phone rang so many times that we are crazy and our head is twisting.

 

Having a right ITM TEPS/db backup we could have restored our system easily even on a machine with different ITM and OS version (yes, you are hearing correctly) we can recover our TEPS/DB from production environment to our pre-production/test TEPS even although both TEPS are not at the same level and the operation system are different. Being able to give service until our production TEPS is up and running again.

 

This blog is going to cover:

  1. Taking a backup of our TEPS DB

  2. Restoring our TEPS DB

 

 

A.  Taking a backup of our TEPS DB:

 

Windows system:

  • Change to the directory Install_dir\CNPS

  • Run migrate-export.bat script

image

  • The saveexport.sql file with the TEPS database is generated in install_dir\CNPS\sqllib .

 

Linux/Unix system:

  • Change to the directory /opt/IBM/ITM/bin

  • Run: ./itmcmd execute cq runscript.sh migrate-export.sh

  • The file saveexport.sql is generated in install_dir\$platform\cq\sqllib

 

NOTE: the migrate-export script can be performed with the TEPS running or stopped , it starts it temporarily in a limitated mode. Dont start TEPS manually     until the script has been completed. (It is really quick). The saveexport.sql file is the one with the TEPS DB.

 

 

B. Restoring our TEPS DB

 

When the destination system is a windows:

  • Stop the TEPS

  • Copy file saveexport.sqlto \install_dir\CNPS\sqllib

 

image

 

  • Run \install_dir\CNPS>migrate-import.bat

  • If we are moving the TEPS DB from one release to another, we will have to perform these steps to add application support:

  1. Edit the install_dir\CNPS\kfwalone file

  2. Set KFW_MIGRATE_FORCE=Y , save and close

  3. Run install_dir\CNPS>buildpresentation.bat to apply the current portal server application support to the newly migrated TEPS DB

image

  • Restart the portal server.

 

NOTE: When the target is a windows system I always prefer to rebuild TEPS database before importing the saveexport.sql file, for example:

  1. Stop TEPS

  2. Create an empty TEPS DB by MTEMS

image

 

image

 

image

 

NOTE:Sometimes it is needed to remove the odbc datasource previously, which will be created automatically rebuilding the TEPS Dd or we can recreate it using the c:\IBM\ITM\InstallITM>DB2DataSource.exe (DB2) or c:\IBM\ITM\InstallITM>CNPSDataSource.exe (MS sql server)

 

The message will be similar to:

image

 

And the TEPS DB start to be rebuilt:

image

 

 

Once it has finished the TEPS DB has been created and the TEP logon is possible with sysadmin. Nothing has been recovered so far.

III. we apply the above steps:

  • copy the saveexport.sql file

  • run migrate-export.bat script

  • if needed, modify the kfwalone file and run buildpresentation.bat

  • Start the TEPS

 

 

 

When the destination system is a Linux/Unix:

  • Stop the TEPS: itmcmd agent stop cq

  • Copy the savexport.sql file to <install_dir>/<platform>/cq/sqllib

  • Run /opt/IBM/ITM/bin> ./itmcmd execute cq runscript.sh migrate-import.sh

image

 

  • If we are moving the TEPS DB from one release to another, we will have to perform these steps to add application support:

  1. Edit the file /opt/IBM/ITM/cq/bin/lnxnocmsenv

  2. Set KFW_MIGRATE_FORCE=Y , save and close the file.

  3. Run /opt/IBM/ITM/bin/./itmcmd execute cq InstallPresentation.sh to apply the current portal server application support to the newly migrated TEPS DB.

image

 

4. Start the TEPS : itmcmd agent start cq

 

The last thing we have to do is reconfigure the TEPS to be connected to the HUB and we will have a TEPS up and running with the production TEPS DB (workspace, navigator, users, etc) connected to our production HUB and giving service at least until TEPS production is up again. Of course, if we have TEPS integrated with Ldap then we will have to configure the integration in this newTEPS.

 

Thanks for Reading, Fran.

 

 

image

 

 

Check out all our other posts and updates:

Academy Blogs:                   
http://ibm.co/1sPj9E8  
Academy Videos:                  http://bit.ly/1wFKveY
Academy Google+:              http://bit.ly/1sR5QTV
Academy Twitter Handle:   http://bit.ly/1CknfoF    

 
 

[{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":""}]

UID

ibm11083729