/explore
|
You are here 
|
cullmann.dev | ||
| | | | |
blog.patshead.com
|
|
| | | | | The automated backup strategy that I've been using for the past three or four years was very solid, and it served me very well. I was using ... | |
| | | | |
it-notes.dragas.net
|
|
| | | | | I have already dealt with the problem of performing a correct backup. This time I will give you some insights into how I make backups and how I am able to guarantee a certain level of security. | |
| | | | |
cullmann.io
|
|
| | | | | Backup is always something you under-appreciate until you need it. Therefore, since I lost a lot of my mails due to non-existing backups in the past, I tried to keep proper backups around the last decade. At least this allowed me to keep all my Kate related development mails intact since 2001 or so, not that bad ;=) My old way of doing backups: rsync & duplicity So far, I did my backup on my Unix machines by using rsync to a second host and duplicity to archive stuff on my old Synology NAS. | |
| | | | |
www.agwa.name
|
|
| | | |||
