IT/Software/Backup Programs/Borg Backup: Difference between revisions
Access restrictions were established for this page. If you see this message, you have no access to this page.
(Created page with "https://www.borgbackup.org/") |
(finished up to Creating a backup) |
||
| Line 1: | Line 1: | ||
=== About === | |||
Borg Backup is a backup program that features compression deduplication, data compression and runs nicely over [[IT/Software/Command Line Applications/ssh|SSH]]. | |||
https://www.borgbackup.org/ | https://www.borgbackup.org/ | ||
<br /> | |||
=== Usage === | |||
==== Repos ==== | |||
A Borg repo is where backup data is stored. | |||
A repo can be created by running the following in an empty directory. | |||
borg init -e none ''repoLocation'' | |||
[[File:Borg Init.jpg|frameless|482x482px]] | |||
"-e none" is a required flag to tell bog that we don't want any encryption. | |||
<br /> | |||
==== Creating a backup ==== | |||
When creating a backup we need to specify what kind of compression we want to use, where the repo we want to backup to is, and where the source files we want to backup are located. | |||
borg create -C auto,lzma --progress ''repo/location''/::''name-of-backup'' ''location/to/be/backed/up'' | |||
LZMA compression uses more CPU and less storage space. | |||
Name of backup must be unique so using the date command instead of a static name is desirable when automating backups. | |||
... ''repo/location''/::`date '+%Y-%m-%d-%H.%M.%S'` ''location/to/be/backed/up'' | |||
Revision as of 19:19, 4 December 2020
About
Borg Backup is a backup program that features compression deduplication, data compression and runs nicely over SSH.
Usage
Repos
A Borg repo is where backup data is stored.
A repo can be created by running the following in an empty directory.
borg init -e none repoLocation
"-e none" is a required flag to tell bog that we don't want any encryption.
Creating a backup
When creating a backup we need to specify what kind of compression we want to use, where the repo we want to backup to is, and where the source files we want to backup are located.
borg create -C auto,lzma --progress repo/location/::name-of-backup location/to/be/backed/up
LZMA compression uses more CPU and less storage space.
Name of backup must be unique so using the date command instead of a static name is desirable when automating backups.
... repo/location/::`date '+%Y-%m-%d-%H.%M.%S'` location/to/be/backed/up