Backing up and restoring databases

Backing up the design databases consists of backing up the master database and each resource database. Similarly, restoring the design databases, whether to a previously used, or to a new MongoDB server instance, consists of restoring the master database and each backed up resource database.

For Linux Docker installations: For IBM Sterling Transformation Extender installations on a Linux system using Docker, the MongoDB container configuration must be known to perform MongoDB database backups. For default Docker installations, the container name is hip-server-mongo. For example, a backup could be performed by starting an interactive terminal session in the running container and dumping the master and resource databases to a directory within the container. The dumped data could then be copied out of the container.

If MongoDB databases are being migrated to a new MongoDB server instance, you must remember to update the MongoDB connection properties in the appropriate IBM Sterling Transformation Extender configuration file.

In general, it must be considered if IBM Sterling Transformation Extender downtime is necessary when migrating between MongoDB server instances. In the simplest case, IBM Sterling Transformation Extender would be stopped, the design databases would be backed up, and the restore operation in the new MongoDB server instance would be performed. The IBM Sterling Transformation Extender installation configuration update operation would then be updated, and IBM Sterling Transformation Extender could be started with the new configuration.