RAID is not a backup. Sync is not a backup. But what if I use both of them together

 

Question is. Does this approach qualify as a 3-2-1 backup?

 

Proposed Solution

 

• Unraid Array, single parity
  • Share 1 (Critical Primary)
    • Disk1
    • Disk2
    • etc
  • Share 2 (Critical Backup)
    • Disk3
    • Disk4
    • etc
  • Share 3 (Non-Critical)
    • All disks

 

Implementation

 

• All data, applications, etc would write to Share 1.
• Duplicacy would then be utilized to creation versioned backups of the data between Primary --> Backup.
• Syncthing would be used to mirror Share 2 to an offsite location.
• Shares 1 & 2 would be protected by Dynamix File Integrity plug-in

 

I think this would give me 3-2-1

• 3 copies
  • Share 1, Share 2, offsite
• 2 physical disks
  • disk 1/2 + disk 3/4
• 1 geo-redundant 
  • Offsite

 

Its close though the use of Syncthing for your offsite is not ideal. Ideally your onsite and offsite backups would be independently versioned. Syncthing will propagate your backup but in the general configuration it will propagate deletes as soon as they happen, meaning if a backup is accidentally deleted from your onsite it will also be deleted from your offsite. Syncthing does have its own basic versioning and deletion protection schemes, but since you indicate you will be backing up a Duplicacy storage there may be some weird overlap in their versioning. Its been a while since i looked at a Duplicacy, but cant it be configured to backup to multiple locations to handle both your onsite and offsite? 

1 hour ago, primeval_god said:

cant it be configured to backup to multiple locations to handle both your onsite and offsite? 

 

It can, but using Syncthing saves me from wiregaurd, DDNS, port forwarding, etc on the remote client. It's also very simple to add multiple remote clients. I think the compromise here is to enable the trash can feature for Syncthing, I really only want to manage versioning in 1 place and, from what I can tell Duplicacy is far superior to syncthing in this regard. Enabling the "trash" will at least protect me from accidental deletion.

 

Its not in my previous post but I also have nextcloud running inside the share, so I will have many layers of versioning

• Nextcloud version/ trash can
• Duplicacy replicates of above
• Syncthing "trash can"

 

On 6/5/2023 at 7:43 AM, whitephoenix117 said:

RAID is not a backup. Sync is not a backup. But what if I use both of them together

 

Question is. Does this approach qualify as a 3-2-1 backup?

 

Proposed Solution

 

• Unraid Array, single parity
  • Share 1 (Critical Primary)
    • Disk1
    • Disk2
    • etc
  • Share 2 (Critical Backup)
    • Disk3
    • Disk4
    • etc
  • Share 3 (Non-Critical)
    • All disks

 

Implementation

 

• All data, applications, etc would write to Share 1.
• Duplicacy would then be utilized to creation versioned backups of the data between Primary --> Backup.
• Syncthing would be used to mirror Share 2 to an offsite location.
• Shares 1 & 2 would be protected by Dynamix File Integrity plug-in

 

I think this would give me 3-2-1

• 3 copies
  • Share 1, Share 2, offsite
• 2 physical disks
  • disk 1/2 + disk 3/4
• 1 geo-redundant 
  • Offsite

 

Hey can you explain the method you used for Duplicacy? What was your storage configuration option? 

Looking to set this up myself, cant find any guides yet