Archive (Move to vs. Copy to)

naiad · Joined: 04 Jan 2013 Posts: 17

Hi,

I'm using VV with VV Engine to sync server A and server B. But the VV is installed on server C.

I set the source archive file location in server A, and target archive file location in server B.

However, it looks to me that during a archive siutation on server B, the file was actually copied to server C first where VV is installed, and then copied back to server B.

Is that the case?

Please advise

Thanks

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8759

The file should stay on server B only if target is B and target archive is B too. What led you to wonder if file is copied to C first? thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

naiad · Joined: 04 Jan 2013 Posts: 17

thx for your reply.
from my observation, the creation of archive file on server B was quite slow (speaking of creating archive even for small files no more than few MB). that's why i suspected that it's being copied to server C where VV is installed then copied back to server B. (our server B is in US, while server C is in Asia, which i thought that might explain the slow creation time of archive file)

naiad · Joined: 04 Jan 2013 Posts: 17

this is from the log where archives being copied on target server B

2013-01-08 09:02:34 : -- Done: 2 (4.64MB) Err: 0 (0) Skipped: 0 (0) Tot: 2 (4.64MB) --
2013-01-08 09:02:34 : -- Average Transfer Rate: 63.52KB/Sec -- Elapsed Time: 1 min 14 sec

for 4.64MB, 1 min 14 sec looks too long to me if the action is all taken locally.

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8759

On second thought about this, I think you might be right: the file is firstly read and then written to target from where ViceVersa is installed, which means that the data travels over the network twice (the file does not get copied to where VV is installed, but it does go over the network)

There's an archive option to avoid this issue, which is called Move Files to Archive Folders (instead of copying): this option will improve archiving performance significantly by moving files to the archive folders instead of copying them. It can only be used when source and target and their corresponding archive folders are on the same drive, or an error is reported. When this option is not selected, ViceVersa copies files from source/target to the archive folders. Please note that this option cannot be used with the synchronization method.
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

naiad · Joined: 04 Jan 2013 Posts: 17

hmm... that probably doesn't solve my problem since a real time bi-directional synchronization is exactly what i need in our environment.

could there be other workaround?

if really nothing can be done to remedy this situation, i will change the archive location of Server B to Server C where VV is installed. then at least, it's a single trip across the pacific instead making a round trip every time when an archive is created....

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8759

Unfortunately the option is not supported with the sync method. Reason is that when moving, the file gets removed from the target and put to the archive, and if an error occurs, it may confuse the sync algorithm...
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com