|
| ▲ | LeoPanthera an hour ago | parent | next [-] |
| This is bordering on paranoia. If the bad sector contains a critical part of the filesystem, you're going to lose everything anyway. Do modern disks even have physical "sectors" anymore? Isn't it all virtual? Without dedup you're just going to backup less stuff, which is far worse. |
| |
| ▲ | locknitpicker an hour ago | parent [-] | | > This is bordering on paranoia. What? You actually think that the mere idea of a backup getting corrupted is something that is "bordering on paranoia"? Have you ever heard of redundancy or even RAID? > If the bad sector contains a critical part of the filesystem, you're going to lose everything anyway. Do you honestly failed to understand that the problem is actually the "lose everything" part? |
|
|
| ▲ | stuxnet79 3 hours ago | parent | prev | next [-] |
| If you are storing your data in a filesystem like ZFS then the risk is lower since you'll know you have a bad sector long before you attempt to deduplicate. But I otherwise share your same concerns and I'm eager to hear from others how to mitigate this. I've lost a volume due to poor practice while encrypting so I'm understandably reluctant to overcomplicate my backup strategies in the name of space compression or privacy. |
|
| ▲ | haradion 3 hours ago | parent | prev | next [-] |
| It doesn't really hurt in practice because it's only one part of the full backup procedure. Deduplicate to save space; re-duplicate the (smaller) backups to separate media for redundancy; scrub regularly for bit rot and rotate your media. A proper backup system requires all but the first of those anyway. |
|
| ▲ | NSUserDefaults 3 hours ago | parent | prev [-] |
| In that case you are supposed to use your /other/ backup. Which you have. |
| |