Author |
Message |
Joshua
Joined: 26 Dec 2019 Posts: 3
|
Posted: Thu Dec 26, 2019 2:35 pm Post subject: Syncing large datasets between 3 locations, long check times |
|
|
Hello. I am currently using ViceVersa 2.5 to sync a very large dataset between 3 sites.
I have ViceVersa installed at Site A, and Site C. Site A has a synchronize job running between Site A and Site B, and Site C has a synchronize job running between Site C and Site B. This effectively allows this dataset to synchronize between all 3 sites. Changes to the dataset are made at all 3 sites.
The problem is this dataset is very large (around 900GB), and continually growing, and is taking an excessive amount of time to perform the target check (around 2 - 4 hours). The actual data transfer does not take very long in comparison to the target check. The internet speed at all 3 locations is good.
I've looked into the no Rescan options, but this does not some appropriate for my setup.
Is there anything I can do to make this setup run better? Does TGMRN offer any other products that would be able to do this type of synchronization any faster? |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8769
|
|
Back to top |
|
|
Joshua
Joined: 26 Dec 2019 Posts: 3
|
Posted: Fri Dec 27, 2019 1:52 pm Post subject: |
|
|
We aren't currently using VVEngine, but after reading through the information on it, it looks promising. I'm currently doing 2-way sync jobs and I'm assuming to do a setup like this, I would need to add a 3rd instance of ViceVersa to Site B and then do 1-way sync jobs between the locations.
So I would then do one way real time syncs between:
Site A > Site B
Site B > Site A
Site C > Site B
Site B > Site C
Does this sound like it will work properly? |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8769
|
|
Back to top |
|
|
Joshua
Joined: 26 Dec 2019 Posts: 3
|
Posted: Fri Jan 10, 2020 2:34 pm Post subject: |
|
|
I just wanted to update this thread that setting up VVEngine (and a third instance of ViceVersa at Site B) seems to be working pretty well.
I have considered setting up another set of jobs running one way real time syncs directly from Site A to Site C (and Site C to Site A), but I'm not sure how much this would rock the boat. |
|
Back to top |
|
|
|