I apologize for not giving full hardare and software specs, but in this case they are not relevant, the below is to describe an example setup to support the question.
Source machine (main server):
However, and this is where my question begins, the rpi does not have ECC ram and is susceptible to bit rot and other issues as well. If a bit rot occurs on the destination machine, will rsync fix this given that the source data is correct?
My understanding is that rsync uses checksum to discover differences, but will it amend a bit rot on the destination server data?
If that is the case I am ok, with this test setup and will use the rpi as offshore backup. If not there is no point and I will repurpose the rpi for something else.
Still only scratching the surface on these topics and apologize in advance for any noob-ish mistkes.
Source machine (main server):
- FreeNAS
- ECC ram
- RaidZ pool with ZFS and 3 drives + extra drive for local snapshot replication
- raspberry pi 3 B+
- open media vault
- SD card for system
- swap disabled (to spare the poor SD card)
- USB HDD for backups (currently only one)
- BTRFS as filesystem for share and rsync server to use
However, and this is where my question begins, the rpi does not have ECC ram and is susceptible to bit rot and other issues as well. If a bit rot occurs on the destination machine, will rsync fix this given that the source data is correct?
My understanding is that rsync uses checksum to discover differences, but will it amend a bit rot on the destination server data?
If that is the case I am ok, with this test setup and will use the rpi as offshore backup. If not there is no point and I will repurpose the rpi for something else.
Still only scratching the surface on these topics and apologize in advance for any noob-ish mistkes.