Backup and Restore

NOTE! The backup and restore scripts are in the toolkit/ folder. On Ubuntu they must be run with sudo; on RHEL they must be run without sudo. Running them the wrong way produces an error and does nothing. See Script Naming and Usage.

Link-Live Private must be running to create or restore a backup.

  • To create a backup, run the following command:

Ubuntu: sudo ./toolkit/backup.sh -y -o /home/myuser/ll-backups

RHEL: ./toolkit/backup.sh -y -o /home/myuser/ll-backups

  • The backup is saved in the specified directory.

  • The -y / --yes option will make the script non-interactive (if you're planning on automating backups).

Restoring Data

CAUTION! Restoring a backup will overwrite all persistent data for a project.

To restore a backup, run the following:

Ubuntu: sudo ./toolkit/restore.sh -i /home/myuser/ll-backups/backup_<date>

RHEL: ./toolkit/restore.sh -i /home/myuser/ll-backups/backup_<date>

Replace <date> with the actual backup date.

Tip: Regularly test backups to ensure they work.

Data Persistence

Docker

Docker-compose runs with a project name of "linklive". Your persistent data is tied to this linklive project, and data is stored within the system docker data directory.

Refer to docker-compose online user documentation if needed: https://docs.docker.com/compose/.

RHEL

Link-Live Private container services on RHEL run using Podman with a project name of "linklive". Persistent application data is associated with this project and stored within the system’s Podman-managed container storage.

All persistent data is maintained in Podman volumes and remains available across service restarts and system reboots.

For additional information about container projects and volume management on RHEL, refer to the Podman and Podman Compose documentation:

https://docs.podman.io/en/latest/

https://github.com/containers/podman-compose

For Advanced Users

Docker

If you're proficient with Docker, we recommend creating your own backup strategy that can be tailored to your specific environment and processes.

RHEL

If you're proficient with Podman and Linux container management on RHEL systems, you may choose to create your own backup strategy tailored to your specific environment and operational requirements.

  • Persistent application data is stored in the following container volumes: ll-mongo, redis, bedrock-redis, and minio.

  • You can review volume usage and definitions in docker-compose.yml, at the root of the installation directory. RHEL uses that same file, because podman-compose reads it directly.

Reference documentation for container volume backup concepts: https://docs.podman.io/en/latest/markdown/podman-volume.1.html