Fix redirecting urls

This commit is contained in:
Cyryl Płotnicki 2023-08-12 21:39:19 +01:00
parent 09f2c13630
commit b5cd71ac2d
2 changed files with 2 additions and 2 deletions

View file

@ -44,7 +44,7 @@ Sync is also not a replacement for backup, as file deletions and corruption can
## Backups ## Backups
Here is where I am not that happy with the overall setup. Here is where I am not that happy with the overall setup.
Currently I use [restic](https://restic.net/) to encrypt the backup and then ship it off of individual machines to my central NAS storage. Then from there it is being shipped to Backblaze's [b2](https://www.backblaze.com/b2/cloud-storage.html) for off-site storage. Currently I use [restic](https://restic.net/) to encrypt the backup and then ship it off of individual machines to my central NAS storage. Then from there it is being shipped to Backblaze's [b2](https://www.backblaze.com/cloud-storage) for off-site storage.
In principle, the setup I would like to retain, where the encryption credentials are only on machines creating backups and everything else only sees already encrypted files. In practice, restic itself seems to have a lot of troubles with the source machines being laptops and being constantly opened and closed, caused the running backup process to go through hibernation cycles. This locks/damages the central backup repo quite frequently and I need to run `restic rebuild-index` quite often to keep things working. In principle, the setup I would like to retain, where the encryption credentials are only on machines creating backups and everything else only sees already encrypted files. In practice, restic itself seems to have a lot of troubles with the source machines being laptops and being constantly opened and closed, caused the running backup process to go through hibernation cycles. This locks/damages the central backup repo quite frequently and I need to run `restic rebuild-index` quite often to keep things working.

View file

@ -67,7 +67,7 @@ Sync is also not a replacement for backup, as file deletions and corruption can
- [restic](https://restic.net/) - [restic](https://restic.net/)
Here is where I am not that happy with the overall setup, and not that much has changed from 2019. Here is where I am not that happy with the overall setup, and not that much has changed from 2019.
Currently I use `restic` to package and encrypt the backup and then ship it off of individual machines to my central NAS storage. Then from there it is being copied to Backblaze's [b2](https://www.backblaze.com/b2/cloud-storage.html) for off-site storage. Currently I use `restic` to package and encrypt the backup and then ship it off of individual machines to my central NAS storage. Then from there it is being copied to Backblaze's [b2](https://www.backblaze.com/cloud-storage) for off-site storage.
I made some progress on [bakare](https://github.com/cyplo/bakare), a small backup engine in Rust, but it's not ready for production use yet. [Let me know](mailto:bakare@cyplo.net) if you would be interested in collaborating with me on it. I made some progress on [bakare](https://github.com/cyplo/bakare), a small backup engine in Rust, but it's not ready for production use yet. [Let me know](mailto:bakare@cyplo.net) if you would be interested in collaborating with me on it.