scy on Nostr: What are some best practices for setting up your #backup when working with large ...
What are some best practices for setting up your #backup when working with large files locally on your machine?
For example, I'm working with OpenStreetMap data. The planet is 75 GB in size. I don't need to back that up, I can download it again should the need arise.
However, I'm also creating derived data from it, in files with a similar size, and generating them can take hours. I'd like to have a local backup in case of accidental `rm`, but don't want to clog up my disk with these backups.
For example, I'm working with OpenStreetMap data. The planet is 75 GB in size. I don't need to back that up, I can download it again should the need arise.
However, I'm also creating derived data from it, in files with a similar size, and generating them can take hours. I'd like to have a local backup in case of accidental `rm`, but don't want to clog up my disk with these backups.