In the following sections, these assumptions are being made with respect to making the backup:
/tmp/backupwill be used as the target for backups
By default, the whole Katello instance will be turned off completely for the entire backup.
# katello-backup /tmp/backup
Backing up the repositories can take an extensive amount of time. You can perform a backup while online. In order for this procedure to succeed, you must not change or update the repositories database until the backup procedure is complete. Thus, you must avoid publishing, adding, or deleting content views, promoting content view versions, adding, changing, or deleting sync-plans, and adding, deleting, or syncing repositories during this time. To perform an online-backup of the repositories, run:
# katello-backup --online-backup /tmp/backup
There may be situations in which you want to see a system without its repository information. You can skip backing up the Pulp database with the following option:
# katello-backup --skip-pulp /tmp/backup
Please note you would not be able to restore a Katello instance from a directory where the Pulp database was skipped.
Incremental backups can be used to only store the changes since the last backup:
First take a full backup:
# katello-backup /tmp/backup/full
Take 1st incremental backup
# katello-backup /tmp/backup/incremntal1 --incremental /tmp/backup/full
Take 2nd incremental backup
# katello-backup /tmp/backup/incremntal2 --incremental /tmp/backup/incremntal1
An example with full backup on Sunday and incremental backup for all other weekdays would look like:
#!/bin/bash -e DESTINATION=/var/backup if [[ $(date +%w) == 0 ]]; then katello-backup $DESTINATION else LAST=$(ls -td -- $DESTINATION/*/ | head -n 1) katello-backup $DESTINATION --incremental "$LAST" fi exit 0
After a successful backup, the backup directory should have the following files:
# ls /tmp/backup config_files.tar.gz mongo_data.tar.gz pgsql_data.tar.gz
Additionally, if you ran the backup without skipping the Pulp database, you will see the additional file:
Katello instance should be up and running. Next chapter is dedicated to restoring a backup.
All the following commands are executed under
root system account.
Please note only backups that include the Pulp database can be restored. To verify that your backup directory is usable, make sure it has the following files:
# ls /tmp/backup config_files.tar.gz mongo_data.tar.gz pgsql_data.tar.gz pulp_data.tar
Once verified, simply run:
# katello-restore /tmp/backup
This command will require verification in order to proceed, as the method will destruct all databases before restoring them. Once the procedure is finished, all processes will be online, and all databases and system configuration will be reverted to the state and the time of the backup.
Check log files for errors, such as
Incremental backups need to be restored sequentially starting with the oldest:
# katello-restore /tmp/backup/full # katello-restore /tmp/backup/incremntal1 # katello-restore /tmp/backup/incremntal2
A new bug fix release for Foreman 1.15 is available. See the Foreman 1.15.3 release notes for more details.
Foreman 1.15.0 is now available, featuring a new notifications UI, template changes, and improvements to host owners and SSH keys. Read about all of the changes in the release notes, and follow the quick start to install it.