Updated Backup to rsync.net via ZFS (markdown)
@ -84,3 +84,23 @@ Select the filesystems that your want to backup:
|
|||||||
>>> Transfer 6% 16MB/s (total 2022MB, 1 minutes left)
|
>>> Transfer 6% 16MB/s (total 2022MB, 1 minutes left)
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## Security considerations
|
||||||
|
|
||||||
|
### Cloud provider
|
||||||
|
|
||||||
|
Although rsync.net is a very professional and trustworthy company, i still will layout the security implications and how you can mitigate some of them with ZFS encryption:
|
||||||
|
|
||||||
|
* The rsync staff can login to your VM to support your machine, so this means they can easily access your data. Even if you use encryption, as long as the key is loaded on the target they could access your data.
|
||||||
|
* You're allowed to deny them access by removing they ssh key. (but this can have some other implications, like updates and support)
|
||||||
|
* To make absolutely sure your data is safe, you should encrypt your data on the source side. (on your server) This will be send over in encrypted form to rsync.net
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
### Crypto ware
|
||||||
|
|
||||||
|
* If you use a push-backup, you are not secured against hackers: If they hack your server, they will have access to your rsync.net server as well.
|
||||||
|
|
||||||
|
### Pull backup
|
||||||
|
|
||||||
|
* You can actually let the rsync.net server login to your server and pull the backup. Keep in mind that
|
||||||
|
|||||||
Reference in New Issue
Block a user