You are here
TurnKey Linux Backup and Migration (TKLBAM)
New to TKLBAM? Take the tour first for a quick overview and screenshots.
Smart automated backup and restore
TKLBAM is GPL3 licensed free software built on top of Duplicity which provides an efficient system-level backup of changed files, users, databases and package management state. This system-level backup can be restored automatically on any installation of the same type of virtual appliance, regardless of the underlying hardware or location. The intended result is a functionally equivalent copy of the original system.
It is also designed to assist in migration of data and system configurations between different versions of the same type of virtual appliance though for some applications, additional manual steps, such as a database schema update, may be required to complete migration between versions.
Assuming the exact same server type (e.g. LAMP backup restored to LAMP server) and a pre-tested backup (to ensure that it includes all the required files):
A backup should always restore cleanly on the same server.
A backup should usually restore cleanly on a server of the exact same version (e.g. v16.1 -> v16.1).
A backup should most likely restore cleanly on a server of the same major version (e.g. v16.0 -> v16.1).
A backup might restore ok on a server of a single newer major version (e.g. v15.2 -> v16.1) although it may require some tweaking.
A backup will almost certainly need some manual intervention if you restore to a server of a (much) newer version (e.g. v14.2 -> v16.1).
It is generally recommended that when restoring to anything other than the same major version that the restore is staged. I.e. first download the backup, then restore the DB (where relevant) and specific files and directories from the download. E.g. (where BACKUP_ID is the actual ID of the backup to restore and only restoring the directories /root & /var/www):
mkdir -p /tklbam-dump tklbam-restore BACKUP_ID --raw-download=/tklbam-dump tklbam-restore /tklbam-dump --limits="/root /var/www"
Note that other backed up files can be found in /tklbam-dump, relative to root (/). E.g. The backup of /etc/my.conf will be found in /tklbam-dump/etc/my.conf. Note too, that manually moving files out of the backup directory won't restore permissions. If you wish to restore files from the download with the original permissions, add them to the --limits="" (contains a space separated list of paths; sub-paths to exclude can be prefixed with '-''). For more info, please see the tklbam-restore man page.
Comments
You should be able to remove the current association with
Then just tklbam-init to link your new key.
tklbam init --force
Worked for me.
[edit] looked at my history. Didn't actually try --force.
Anyone looked at duplicacy?
It also supports snapshots and lock-free concurrent access.
Here's the github page: https://github.com/gilbertchen/duplicacy-beta
This is where they compare duplicacy to other backup tools such as duplicity: https://github.com/gilbertchen/duplicacy-beta#comparison-with-other-backup-tools
Not sure if TKLBAM can be setup with this or not, but I thought that it was something worth noting.