4 ms·

A few things that I find don't get considered when contemplating backup procedures are: 1. How long should you keep backups for - is the content of your backup

A few things that I find don't get considered when contemplating backup procedures are: 1. How long should you keep backups for - is the content of your backup covered by privacy laws that require you to not have copies of it after a certain period of time? is there a point where the content of your back up is so old that it's the logical equivalent of not having made a back up in the first place? 2. How much does your backup process cost - if it costs more to back up a system than it would cost you if you lost it, then you've got the backup process wrong (interestingly this can be affected by economies of scale) 3. What do you need to restore a backup - does your system requires bespoke hardware that might have been lost in whatever disaster you're trying to recover from?

t_believ-er873 2y ago
Yes, it's worth paying attention to these questions as they are very important. If renetion is mostly related to compliance requirements of the industry. Some data should be kept for 5 years and some for 20, so it's good if a backup solution provides long-term or unlimited retention. Regarding the cost, I think that a backup solution is always much cheaper than the cost of data loss. So it's better to have a backup than not. And, of course, restore and recovery checks are also important. Moreover, a backup solution should foresee different disaster scenarios. for example, disaster scenarios like those described here in the article: https://gitprotect.io/blog/github-restore-and-github-disaster-recovery-scenarios-and-use-cases/ https://gitprotect.io/blog/github-restore-and-github-disaste...
Xen9 2y ago
Assuming we want to store most-typically-incrementally mutating data in perpetuity, then TOH or a derivation probably provides optimal scheduling scheme. The question is which frequencies you give each "layer", what parameters define these, et cetera.

t_believ-er873 2y ago

Yes, it's worth paying attention to these questions as they are very important. If renetion is mostly related to compliance requirements of the industry. Some data should be kept for 5 years and some for 20, so it's good if a backup solution provides long-term or unlimited retention. Regarding the cost, I think that a backup solution is always much cheaper than the cost of data loss. So it's better to have a backup than not. And, of course, restore and recovery checks are also important. Moreover, a backup solution should foresee different disaster scenarios. for example, disaster scenarios like those described here in the article: https://gitprotect.io/blog/github-restore-and-github-disaster-recovery-scenarios-and-use-cases/ https://gitprotect.io/blog/github-restore-and-github-disaste...

Xen9 2y ago

Assuming we want to store most-typically-incrementally mutating data in perpetuity, then TOH or a derivation probably provides optimal scheduling scheme. The question is which frequencies you give each "layer", what parameters define these, et cetera.