| Both sides previous revision Previous revision | Next revisionBoth sides next revision |
| rethinking_my_backup_strategy [01.01.2021 23:05] – [First POC - Burp + rsync] Pascal Suter | rethinking_my_backup_strategy [01.01.2021 23:23] – [First POC - Burp + rsync] Pascal Suter |
|---|
| * ''server_can_restore = 0'' | * ''server_can_restore = 0'' |
| * ''server_can_override_includes = 0'' | * ''server_can_override_includes = 0'' |
| * a script on the burp server uses ''rsync -aAhHvXxR --numeric-ids --delete /var/spool/burp/./*/current/ rsync:%%//%%user@offsite/current0'' to write backups to the offsite server | * a script on the burp server uses ''rsync -aAhHvXxR --numeric-ids --delete ...'' sync the latest backups stored in ''/var/spool/burp/<client name>/<backup timestamp>'' where ''backup timestamp'' is the target of the ''current'' symlink in the same directory. so a script which uses something along the lines of ''readlink'' should find the ''current'' backup which was just completed and then rsync this to the offsite server's ''current directory'' |
| * on the offsite server, a script is called (somehow, haven't figured out yet how exactly this will be done) after the rsync from the burp server successfully finished. the script will use ''cp -alx /backups/current /backups/`date +%Y.%m.%d-%H%M`'' to create hardlinked copies of the current directory. by using this script, we can avoid to use the ''%%--%%link-dest'' option of rsync which in turn would make it necessary to at least include the latest completed backup also in the writable share. | * on the offsite server, a script is called (somehow, haven't figured out yet how exactly this will be done) after the rsync from the burp server successfully finished. the script will use ''cp -alx /backups/current /backups/`date +%Y.%m.%d-%H%M`'' to create hardlinked copies of the current directory. by using this script, we can avoid to use the ''%%--%%link-dest'' option of rsync which in turn would make it necessary to at least include the latest completed backup also in the writable share. |
| |
| docker run --net burp --name burpsrv -ti ubuntu-test:latest | docker run --net burp --name burpsrv -ti ubuntu-test:latest |
| to create the container for the burp server, and similar commands for the other servers. | to create the container for the burp server, and similar commands for the other servers. |
| | |
| | for testing i ran the burp server with this command line: |
| | burp -v -F -c /home/jdoe/burp/etc/burp-server.conf |
| | |
| | which outputs any logs directly to stdout and keeps the daemon in the foreground. |
| | |
| | ==== offsite backup file encryption ==== |
| | since all files are encrypted on the client side before they are sent to the backup server, we don't have to encrypt them again when uploading them from the backup server to the offsite backup. this basically removes all the challenges mentioned in the "self made" backup |