You are here:Home » Frequently Asked Questions » Backup and Migration (TKLBAM) » Overview » Frequently Asked Questions - Overview
If you're using any TurnKey derived system, you don't need to install it as TKLBAM is a bundled into the TurnKey Core.
If you're using a generic Debian or Ubuntu derived system you can install it with the following shell command:
wget -O - -q \ https://raw.github.com/turnkeylinux/tklbam/master/contrib/ez-apt-install.sh \ | PACKAGE=tklbam /bin/bash
This adds the TurnKey package repository to your APT sources and uses APT to install the tklbam package and its dependencies.
Using TKLBAM on TurnKey Linux provides the best experience but it will also work well with any Debian or Ubuntu derived system and even with other Linux distributions if you install from source and use the --skip-packages option to disable integration with APT, the Debian package manager.
When you use TKLBAM with TurnKey Linux it takes advantage of the known fixed installation state to make the smallest possible backup. For example, it will only backup /etc configuration files that you have changed. This makes migration easier by increasing visibility into what actually changed. By comparison on a generic Debian or Ubuntu system it will backup all /etc configuration files.
Pretty much anything, though storing backups to Amazon S3 is easiest because authentication and key management are automatic. You just need to run:
But you can also backup to any storage target supported by TKLBAM's back-end Duplicity including the local filesystem, NFS, Rsync, SSH, FTP, WebDAV, Rackspace CloudFiles and even IMAP.
The local filesystem is one of the easier storage targets to use because you don't need to mess around with authentication credentials.
So assuming you want to store your backup at /mnt/otherdisk:
tklbam-backup --address file:///mnt/otherdisk/tklbam/backup tklbam-escrow /mnt/otherdisk/tklbam/key
And restore like this:
tklbam-restore --address file:///mnt/otherdisk/tklbam/backup \ --keyfile=/mnt/otherdisk/tklbam/key
Not as easy as the Hub-enabled "automatic" mode, but still vastly easier than your conventional backup process. The disadvantage is that you won't be able to restore/test your backup in the cloud, or from a VM running in another office branch (for example). Also keep in mind that a physical hard disk, even a RAID array, provides much lower data reliability compared with Amazon S3.
For this reason we recommend users use local backups to supplement cloud backups (e.g., providing fast local access).
Currently, only MySQL and PostgreSQL have built-in support but TKLBAM can work with other databases so long as you configure custom serialization/unserialization procedures in a hook script.
- Top downloads
- About TurnKey
- Apps (105)
- TurnKey Hub