aboutsummaryrefslogtreecommitdiffstats
path: root/arch-system/borgbackup
Commit message (Collapse)AuthorAgeFilesLines
* arch-system: backup system updatesTharre2023-04-251-23/+14
|
* arch-system: borgbackup: ignore archive already exists errorTharre2019-06-301-1/+1
|
* arch-system: borgbackup: use proper ssh timeoutTharre2019-04-211-1/+1
| | | | | | ConnectTimeout merely specifies the TCP timeout, what we really want is ServerAliceInterval, which makes the client send a null packet every X seconds.
* arch-system: borgbackup: use snapshot timestampsTharre2019-02-091-0/+1
| | | | | | | | | Previously, a archive would get the timestamp of the time it was uploaded, instead of the time when the snapshot was created. This is problematic, since archives are pruned by this timestamp, meaning if multiple archives are uploaded together most of them would be pruned immediately after.
* arch-system: borgbackup: change repo to rsync.netTharre2018-08-071-2/+2
|
* arch-system: borgbackup: better connectivity checkTharre2018-08-071-5/+6
| | | | | | | | | | Instead of trying to execute borg, which would give us a false positive if borg itself isn't working on the remote, just connect to the server without executing a command. We check for 255 because `man 1 ssh` states the following: ssh exits with the exit status of the remote command or with 255 if an error occured.
* arch-system: borgbackup: treat rc 1 as a warningTharre2018-07-311-6/+14
|
* arch-system: borgbackup: --keep-hourly 24 -> 72Tharre2018-07-161-1/+1
| | | | | | | | Since borg-prune only keeps the last snapshot of each day with --keep-daily, it's possible that a file that was accidentally deleted is only kept for 24h (if the machine is running) before it's purged from backups. Increase to 72h to give the user a better chance of noticing this in time.
* arch-system: borgbackup: notify about upload skipTharre2018-07-161-0/+3
|
* arch-system: borgbackup: use correct key with sshTharre2018-06-151-2/+3
|
* arch-system: borgbackup: check connection with sshTharre2018-06-141-12/+8
| | | | | | Networkmanager isn't really all that reliable, and we actually don't want to depend on it anyway. So trying to connect via ssh is the better thing to do.
* arch-system: borgbackup: only notify when scriptedTharre2018-05-301-1/+4
|
* arch-system: borgbackup: add -p when interactiveTharre2018-05-291-1/+5
|
* arch-system: borgbackup: break locks before backupTharre2018-05-051-1/+3
|
* arch-system: borgbackup: check network statusTharre2018-05-051-4/+15
|
* arch-system: add backup-system packageTharre2018-03-271-0/+65
This implements fully automated, hourly backups of my /home via borgbackup, btrfs and systemd timers. Note that `setup_borgbackup`, a related function that is part of my dotfiles, is needed to setup backups for the first time, as well as a call to `borg init` with the proper environment variables.