So I have been reading pretty much daily on site now and having made a quite an investment (time/money) on having 2 unraid servers, it has got me thinking "well but if the worst was to happen" I would be screwed!

 

So what would be considered best practice to create an off-site backup.

 

I have 2 machines at the moment, 1 purely for data, 1 purely for processing and dockers.

 

If RIG1 (see sig.) was destroyed that would be years and years of data lost.

 

So should I look to build an identical machine, with similar amount of storage if not more. Do one time sync within LAN than do multiple syncs of WAN daily?

 

Any thoughts or suggestions would be hugely appriciated.

So I have been reading pretty much daily on site now and having made a quite an investment (time/money) on having 2 unraid servers, it has got me thinking "well but if the worst was to happen" I would be screwed!

 

So what would be considered best practice to create an off-site backup.

 

I have 2 machines at the moment, 1 purely for data, 1 purely for processing and dockers.

 

If RIG1 (see sig.) was destroyed that would be years and years of data lost.

 

So should I look to build an identical machine, with similar amount of storage if not more. Do one time sync within LAN than do multiple syncs over WAN daily? Or is it more complicated than that? I know alot of people use crashplan and rsync but I have no experience with them and not sure how many people are doing this over WAN?

 

Any thoughts or suggestions would be hugely appriciated.

Guess that everybody more or less have unique needs?

 

Personally I have a daily local backup of all my data on a separate disk set on my main server as well as a daily backup (using rsync) on my backup server. In addition, I use CrashPlan and have a full backup there as well but I prefer to see that as a disaster recovery option since it would take ages to restore a complete backup.

• My main (critical) data is on the workstation.
  
• It is automatically backed up to the unRAID server through Syncthing with Staggered File Versioning (every 30s for 1st hour, every hour for first day then every day afterward).
  
• The Syncthing folder is then backed up to Crashplan for off-site.
  

 

So if I'm under ransomware attack, I would always have a readily-available "last good" version to restore immediately. And in a disaster situation, Crashplan is my "crash plan".

 

What I like about the above arrangement is that it's "set it and forget it". And since management is done via various GUIs, it does require some tech-savviness but it doesn't require a Linux / Windows expert to check the commandline parameters etc.