Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Di 28.05.2024 00:00:05 12.103 +3 6.432.508 531,5 chaos.social 4.2.8 500 Mo 27.05.2024 00:00:00 12.100 +2 6.426.194 531,1 chaos.social 4.2.8 500 So 26.05.2024 00:00:00 12.098 0 6.420.138 530,7 chaos.social 4.2.8 500 Sa 25.05.2024 00:00:03 12.098 0 6.414.368 530,2 chaos.social 4.2.8 500 Fr 24.05.2024 00:00:04 12.098 +1 6.408.201 529,7 chaos.social 4.2.8 500 Do 23.05.2024 00:00:04 12.097 +2 6.402.500 529,3 chaos.social 4.2.8 500 Mi 22.05.2024 00:00:03 12.095 +1 6.396.190 528,8 chaos.social 4.2.8 500 Di 21.05.2024 00:00:02 12.094 +1 6.389.970 528,4 chaos.social 4.2.8 500 Mo 20.05.2024 00:00:00 12.093 +2 6.384.133 527,9 chaos.social 4.2.8 500 So 19.05.2024 00:00:03 12.091 0 6.378.152 527,5 chaos.social 4.2.8 500
scy #GPN22 7299 (@scy) · 04/2022 · Tröts: 11.815 · Folger: 2.048
Di 28.05.2024 01:26
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.
[Öffentlich] Antw.: 0 Wtrl.: 1 Fav.: 0 · via Web