For archiving and backup, I created the following strategy:
- Server 1 (Local Network in Office) running 24/7, Linux Ubuntu NAS on DIY Odroid XU4 with Cloudshell 2 and Raid-1 (2x 8TB)
- this is my primary backup and archive, important directories on my computers/smartphone etc. get directly synced once they're connected to the local network or if I select files manually for archive
- because this is not a true backup (imagine my house burns, server gets stolen), I have another server (2), which is physically (far) separated from Server 1
- this server is online only once a week, when it rsyncs all data from Server 1 or when I need to perform other more intensive tasks
- it has 32 GB ECC RAM
I know this setup should be the other way around, but the XU4 is pretty silent and I don't want that monster server running 24/7 in my house. I was wondering how bad this setup is in terms of data corruption:
- I assume server 2 will sync files, no matter if they are corrupted or not from server 1 (e.g. due to non-ECC RAM in Server 1)
- is there a feasible approach to tell Server 1: only sync files that changed on purpose, do not sync files corrupted by RAM errors
- maybe Server 1 could even check with server 1, e.g.: "I do not have any live connections currently, File xx still changed - lets check with Server 2 if this was due to a RAM error"
Any help appreciated!