Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revisionBoth sides next revision | ||
rethinking_my_backup_strategy [01.01.2021 23:23] – [First POC - Burp + rsync] Pascal Suter | rethinking_my_backup_strategy [01.01.2021 23:32] – [offsite backup file encryption] Pascal Suter | ||
---|---|---|---|
Line 100: | Line 100: | ||
==== offsite backup file encryption ==== | ==== 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 | + | 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 |
+ | |||
+ | ==== restore from an offsite backup ==== | ||
+ | here is how i have tested the restore-ability of an offsite backup in case we have completely lost the backup server in between. | ||
+ | - set up a new burp backup server with the same client config | ||
+ | - setup a new client or delete the certificates if the client is still there and should be re-used | ||
+ | - using '' | ||
+ | - using '' | ||
+ | - now use '' | ||
+ | - restore using '' | ||
+ | |||
+ | this worked flawlessyl in my test, of coures as long as I still had the **encryption password** available from somewhere! .. needless to say, if you don't store your encryption password your backup is completely useless, so make sure your encryption password is saved somewhere where you will still have it, even if you loose the client, and of course, don't store it together with the backup on the backup servers :) |