sync.db and how to synchronise properly 3x6TB disk

[michalb]

Hi Guys,

I'm looking for a solution/good way to synchronize 3 disks. In detail, I've 3x6TB which one of them is the source and the rest of them are copies. How the flow of backups should look?

Is the flow under is correct?
Source disk --(Mirror with detecting moved files)-> Disk copy 1 --(Mirror with detecting moved files)-> Disk copy 2.

What with sync.db files existing on these disks? Should I care about these files or the FFS will handle and detect that there are different disk and save the changes to sync.db without the problem?

Thanks in advance for responses.

[xCSxXenon]

Honestly, if you are using these as locally connected disks, you are better off setting them up in RAID 1 using the hardware RAID in BIOS, if available, or creating a software RAID in Windows Disk Management if not. This will write the same data to all of them at the same time instead of waiting to run a sync. This would only apply if your goal is to have all three drives to be identical.

[xCSxXenon]

If you plan on disconnecting them, then you would probably be best off creating a job with two folder pairs:
Source Drive <-> Disk copy 1
Source Drive <-> Disk copy 2
If you do "source -> copy 1 -> copy 2" you will have to run the sync twice

[michalb]

Thanks for responses. :)

Raid is impossible to do, because all of those disks are external and indepented.
So the flow looks:
Source Disk is located in one localization also with Disk copy 1 and in the second localization I have 3rd disk.

Should I travel with source disk and makes mirror copy to Copy 1 and 2 disks?

Does the sync.db on source disk can contain information for two disk?

[xCSxXenon]

Gotcha. Yes, you will want to travel with and work off of the main source disk, then run the sync to create mirror backups on disk copy 1/2. The 'sync.db' file basically holds information about the files on the source drive. If you move or rename a file, you want to save time by doing that same thing on the backups. Let's say I have a file named "Company Jack Bx LLC" that is synced/mirrored to the two disk copies. But oh no, I misspelled the company name! I will rename it "Company Jack Box LLC" and run the sync again, but crap, the file is 50GB and will take hours to backup! The sync.db file will hopefully recognize the simple name change and instead of deleting "Company Jack Bx LLC" and copying the 'new' file "Company Jack Box LLC", it will just rename it in the backups as well. That will take less than 5 seconds instead of the long transfer time