instead of creating parity file for it? If yes, which tool do you suggest for managing these copies, repairing corruptions, etc?
If you cannot allow for a single file to get corrupted by a storage defect, use a software RAID solution. On Linux you can use LVM or BtrFS or ZFS for this purpose. If you're concerned with user error or malicious program / user, then you should go for backups. Filesystems like BtrFS allow you to have snapshots that take almost no extra space. In userspace you can also use borgbackup. It can do compression, deduplication and encryption and saves to either local or remote (via ssh) storage. Deduplication means that if you backup multiple files (or do multiple backups) that have similar contents, your repository's total storage usage won't increase much. Regarding copies, if you care about your data, make sure you have the same important data (or its backup) on at least 3 different devices.
You need 3 copies if you actually care about the file.
Обсуждают сегодня