Backing up and restoring other supported databases

By default, the IBM® Engineering Lifecycle Management products are configured to run with a Derby database. Changing to a database such as IBM Db2®, Oracle, or SQL Server can provide better performance, scalability, and reliability in a production environment. The examples provided are for Db2. For complete instructions, refer to the documentation supplied by your database vendor.

Before you begin

Note: You must backup the JazzInstallDir/server/conf/jts/indices directory in the same place as the database, and it must be restored at the same time when restoring the database.

Procedure

To back up a Db2 database or other supported database:

  1. Stop the Jazz® Team Server.

    The default Jazz Team Server uses WebSphere Liberty.

  2. Follow the instructions in your database documentation for backing up the database. In the case of Db2, complete these steps:
    1. Locate the Jazz Team Server database in Db2.
    2. Right-click the Jazz Team Server database, and select Backup.
    3. For the Media type, select File system, and point to the location for saving the backup.
    4. Click Finish.
    5. Repeat Steps 2a, 2b, and 2c for CCM and any other databases that you need to back up.
    6. Restart the Jazz Team Server.
  3. To restore an existing Db2 database with the version that you backed up:
    1. Stop the Jazz Team Server.
    2. Locate the Jazz Team Server database in Db2.
    3. Right-click the Jazz Team Server database, and select Restore.
    4. Click Restore to new database.
    5. Type a name for the new database, for example, JTS.
    6. Select the directory that contains the backup.
    7. Click Finish.
    8. Open the JazzInstallDir/server/conf/jts/teamserver.properties file and edit the following lines to point to your restored database.
      com.ibm.team.repository.db.vendor = DB2
      com.ibm.team.repository.db.jdbc.location=//localhost:50000/JAZZ:user=db2admin;password={password};
      com.ibm.team.repository.db.jdbc.password=db2admin
      
    9. Save your changes and close the teamserver.properties file.
    10. Repeat Steps 3a to 3j for CCM and any other databases that you need to restore.
    11. Restart the server.