Backing up the Tivoli Enterprise Portal Server Container automatically

Edit online

Explains the process of automatically backing up the Tivoli® Enterprise Portal Server Container.

About this task

Back up the IBM Tivoli Monitoring - Tivoli Enterprise Portal Server Container files and database from the underlying host system, ensuring it can be restored later if needed. Regular backups are essential because they allow you to migrate the IBM Tivoli Monitoring - Tivoli Enterprise Portal Server Container to a new system, recover the server in case of a failure, and restore functionality if an upgrade fails for any reason.

Note: Automatic backups are available starting with IBM Tivoli Monitoring - Tivoli Enterprise Portal Server Container version 1.1.0.1. To perform a manual backup, see Backing up the Tivoli Enterprise Portal Server Container manually for instructions.
Note: IBM Tivoli Monitoring - Tivoli Enterprise Portal Server Container supports both Docker and Podman runtime environments. The commands in this topic demonstrate installation using Podman. To use Docker instead, replace podman with docker in the commands.

Procedure

  1. Access the IBM Tivoli Monitoring - Tivoli Enterprise Portal Server Containerusing the following command: 
    podman exec -it <CONTAINER_NAME> bash
  2. From the host system, run the following command: 
    ./tepscontainer.sh container_backup
    This script first verifies whether the Tivoli Enterprise Portal Server Container is running. It then executes the database export (migrate-export.sh) inside the container and collects the resulting saveexport.sql file along with all necessary configuration files. These files are packaged into a compressed archive named TEPS.tar.gz, which is finally copied to the current directory on the host system.

    Once the process completes, you will see messages indicating that Backup completed successfully. and that the Backup available at: /full/path/to/TEPS.tar.gz.

  3. Confirm that TEPS.tar.gz exists in your current directory.