Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
| mobi_2.0 [31.12.2020 08:51] – [self-made collection of other tools] Pascal Suter | mobi_2.0 [31.12.2020 09:00] – [Burp] Pascal Suter | ||
|---|---|---|---|
| Line 48: | Line 48: | ||
| ===== possible solutions ===== | ===== possible solutions ===== | ||
| ==== Burp ==== | ==== Burp ==== | ||
| - | as stated above, use burp, maybe in hardlink mode or with a BTRFS storage underneath and then create a custom off-site backup | + | Since burp has all the features we want, it seems like it might be worth to just dig into the remote-backup |
| + | possible solutions to consider are: | ||
| + | * use burp in hardlink mode and try if using rsync is simpler now | ||
| + | * use burp with a BTRFS or ZFS storage underneath and then create a custom off-site backup (by using BTRFS Snapshots). | ||
| + | * BTRFS seems to be a good choice as it is designed to provide easily transferrable snapshots.. by backing up each snapshot to the offsite server, we could make sure, that even if the entire btrfs filesystem is messed up on the main backup server, we would still have intact old snapshots on the secondary backup server. | ||
| + | * ZFS on the other hand provides erasure coding through the various radz2 and so on levels, which means we will loose less harddisk space and can work without expensive and error prone raid controllers in our backup systems, that would be a nice side-effect | ||
| + | * the advantage of any of these snapshot method is, that they will work no matter what the burp developers decide to change in the future about how they store backups.. so we don't need to mess with internals of burp to get a remote backup running, where with rsync we need to know what burp does exactly and how we can back up the right data to preserve this functionality. | ||
| + | |||
| + | the main advantages of using burp over a selve made variant are | ||
| + | * burp is tested and trusted by many | ||
| + | * burp already solves the permission issues | ||
| + | * burp provides a way to browse client-side encrypted backups already | ||
| + | * we only have to implement a secondary backup solution. so this is probably a lot less work over all | ||
| + | * we get additional features such as windows backups for free which might be appreciated in the future. | ||
| ==== self-made collection of other tools ==== | ==== self-made collection of other tools ==== | ||
| so "self made" is a bit flexible here.. what i mean is a larger script that will use a combination of several tools together: | so "self made" is a bit flexible here.. what i mean is a larger script that will use a combination of several tools together: | ||