Plan and carry out procedures for regularly scheduled backups of the
InterChange Server Express system. The more frequently you perform
backups, the less data you need to recover in the event of data loss.
When planning a backup schedule, keep in mind the information in this
section.
Within the InterChange Server Express system, two types of data should be
backed up: static data and dynamic data.
- Static data rarely changes and should be backed up only when
changed. For example, back up static configuration data stored in the
InterChange Server Express repository only when it has changed or before
planned reinstallations or upgrades to the system. Following is a
partial list of static data in the InterChange Server Express system:
- InterChange Server Express repository (except for relationship tables)
- Custom collaborations components, such as Java class files
(.class), and message files (.msg)
- Custom connectors
- Map components, including map design files and Java class files
(.class).
- Dynamic data constantly changes and should be backed up on a regular
basis. For example, the relationship tables maintain the instance data
for relationship definitions. Because relationship instance data is
maintained continuously, regularly back up this data and application
data.
The relationship tables are stored by default in the repository
database. If you store them in another database, you need to back up
that database. For more information about settings for storage of
relationship tables, see the Map Development Guide.
Following is a partial list of dynamic data in the InterChange Server
Express system:
- InterChange Server Express cross-reference database
- InterChange Server Express relationship tables
- InterChange Server Express WIP (event management) and transaction tables
- WebSphere MQ queue data
- InterChange Server Express connector archive tables (this is part of the
application backup; all events since the last backup should be archived)
- Log files (as desired for historical information)
Plan your backup schedule at times when your systems environment is in a
quiescent state or in a state with a minimal amount of event
processing. InterChange Server Express is in a quiescent state when all
of the following conditions exist:
- All working queues are drained.
- All collaborations are paused so that no new data can be written to the
cross-reference tables.
- All data is consistent between the integrated applications.
