Network Deployment (Distributed operating systems), v8.0 > Applications > Service integration
Service integration backup
You should back up your service integration setup on a regular basis so that it can be restored in the event of an unrecoverable failure.
For service integration, these are the main components that you can back up:
- Configuration files
- The configuration of a service integration setup is stored as XML files.
To back up or restore these configuration files, use the relevant command as detailed in Back up and restore administrative configuration files. Any backup or restore of a service integration setup must include a backup or restore of the configuration files.
- Data stores that are accessed by the messaging engines
- Back up and restore your data stores is optional. As messages are transient in nature, you might not want to back up or restore the data stores.
- If you do not back up the data stores, and you modified your current configuration since it was last backed up, when you restore the configuration backup be aware that you might lose messages. For example, if you back up the configuration and then create a bus destination, when you restore the configuration backup the bus destination will no longer exist. Any messages for this destination will be deleted when the server that hosted that messaging engine is restarted.
- If you do back up your data stores, also back up the configuration files. We must back up or restore the configuration files at the same time as the data store is backed up or restored. Backing up and restoring at the same time maintains the consistency of the system and reduces the possibility of losing or duplicating messages from the time of the backup.
To back up a data store, see Back up a data store.
- File stores that are accessed by the messaging engines
- Back up and restore your file stores is optional. As messages are transient in nature, you might not want to back up or restore the files.
To back up a file store, see Back up a file store.
If we have multiple servers, you should ideally back up all the servers at the same time, otherwise messages from the time of the backup might be lost or duplicated. You should also minimize message traffic to reduce the possibility of losing or duplicating messages.
When you restart a messaging engine after restoring a backup, you should take steps to minimize loss of messages. See Restore a data store and recovering its messaging engine.
Service integration technologies
Message reliability levels - JMS delivery mode and service integration quality of service
Back up a data store
Back up a file store
Restore a file store
Restore a data store and recovering its messaging engine