Hi,
I've started using Drive ShareSync to keep a few shared folders on two NAS's in sync, as offsite replicas of each other.
Essentially I'm looking to do something like this:
DS213j DS115j
Folder A -> Folder A
Folder B <- Folder B
Folder C <- Folder C
My question is:
Is there any functional difference between which NAS in this setup acts as the ShareSync client vs. the server?
ie. Scenario A: DS213j (client) uploads Folder A to DS115j (server)
vs. Scenario B: DS115j (client) downloads Folder A from DS213j (server)
Two of the directories being synced contain a small number of large files (8 x ~80GB files) that rotate once a week. As a result, there seems to be quite a lot of CPU work involved on the client side when a new file needs to be synced.
Given that neither of the NAS's in question is very powerful it could save a lot of time to have this configured the 'correct' way around.
Thanks.
I've started using Drive ShareSync to keep a few shared folders on two NAS's in sync, as offsite replicas of each other.
Essentially I'm looking to do something like this:
DS213j DS115j
Folder A -> Folder A
Folder B <- Folder B
Folder C <- Folder C
My question is:
Is there any functional difference between which NAS in this setup acts as the ShareSync client vs. the server?
ie. Scenario A: DS213j (client) uploads Folder A to DS115j (server)
vs. Scenario B: DS115j (client) downloads Folder A from DS213j (server)
Two of the directories being synced contain a small number of large files (8 x ~80GB files) that rotate once a week. As a result, there seems to be quite a lot of CPU work involved on the client side when a new file needs to be synced.
Given that neither of the NAS's in question is very powerful it could save a lot of time to have this configured the 'correct' way around.
Thanks.