Database recovery

Use the best available database backup technologies

Depending on the database vendor chosen, various different database backup utilities are available. If you use IBM DB2, on-line backups are available and provide a way to keep quality backups with minimal interruption. See the DB2 documentation for details on enabling on-line backups. Some specific settings are required in the area of log file management. Even with a solid backup story, scheduling occasional downtime for a full backup is wise. On Jazz.net, on-line database backups are taken nightly and in conjunction with transaction logs. Up to the last committed transaction can be restored. Off-line backups occur only when migrations or host system configuration changes are completed.

When you use an Oracle database, configure for ARCHIVE LOG mode. You can use the Oracle RMAN utility or Enterprise manager to take backups and schedule them on a periodic basis in conjunction with archive logs. The same tools can provide functionality to restore the database in case of failure. There might be other components that need to be backed up, like instance configuration settings, to exactly restore the database to original configuration.

In addition to backing up your Jazz repository databases, back up data that defines your application server configuration or configurations. The key items to backup from the Jazz application servers include: the jazz.war file, the workitemindex directory, the teamserver properties, the profile.ini file, the update-site directory, and the conf directory.

Also back up the following files from your web server: server.xml, web.xml, tomcat-users.xml (Tomcat), or the WebSphere profiles when using WebSphere Application Server. WebSphere Application Server provides a backup utility for doing this.

Tip: Deploy the Jazz repositories on an enterprise-ready database technology. Use the functionality and features available with that technology to best minimize downtime for backup and restore operations. Use standard enterprise backup procedures and policies with respect to backup media and offsite storage. Test these technologies and procedures, and document the specific approaches and procedures in place in your environment. For details on database backup technologies and concerns, see the Deployment Guide for Jazz Team Server and the Getting Started with Rational Team Concert 3.x: A Deployment Guide.

Database tier clustering

A common strategy for high availability in the database tier is the use of DB2 HADR or Oracle RAC capabilities.

IBM DB2

• See Configuring IBM DB2 9.7 HADR for RTC.

Oracle

• Demonstrated with Oracle RAC technology in Task 189875.

Related topics: Approaches to implementing high availability and disaster recovery for Rational Jazz environments

External links:

• None

Additional contributors: None