![]() If you prefer not to deal with keyfiles, you can use the repokey option the key will be stored on the backup server instead. In my example the keyfile is saved at /mnt/nvme/borgdata/.config/borg/keys Losing this will render your backups inaccessible. Securely store the keyfile or the contents of the keyfile in your password manager. mnt/nvme/jellyfin/logs # exclude logsīorgmatic_source_directory: /mnt/nvme/borgdata/.borgmaticīorg_base_directory: /mnt/nvme/borgdata # will contain keyfileĮncryption_passphrase: vsmYPCOqxX6VpgrBPRTi77Q1AMRsEapS # use long passĪrchive_name_format: "homelab-" # use preferred format mnt/backups/borg # attached ext drive, redundant, optional Mine for example looks like this: location: All options are optional except where indicated, so feel free to ignore anything you don't need. You should edit the configuration file to suit your needs, as the generated values are only representative. This generates a sample configuration file at /etc/borgmatic/config.yaml. We'll generate a sample configuration file generate-borgmatic-config Upgrade manually with pip3 occasionally to keep it up-to-date. # login as rootĪdd-apt-repository ppa:costamagnagianfranco/borgbackupīorgmatic will not be upgraded to newer versions automatically. To correctly restore file permissions and set ownership, borg needs to be run as root. This is to allow borg to access system directories such as /etc, /var. We'll also assume you're logged in as root, which is highly recommended. For other distros, refer to the official installation instructions here. We'll assume you're running Ubuntu 20.04+. It will also prune your backups which borg does not perform automatically. borgmatic will read your configuration file and run borg accordingly so you don't have to remember borg commands. While Borg can be used by itself, I like to use a nifty little helper called borgmatic to make configuration easier.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |