VV Pro VPN probem with Win Server 2012 R2

[JerryEF]

Problem: VVPro jobs frequently do not copy all files. Skipped files are because of: “An unexpected network error occurred”, “The network is busy” and/or “The specified network name is no longer available” errors. Many other files do copy across before and after the error files. Large (>20M) files are most commonly hit. (Large files == longer time copying == greater exposure to errors and error counters)

Problem cropped up this past spring and seems to be getting worse(???). Prior to this, VVPro worked perfectly for several years. Other than this issue, this is the best product out there.

Environment:
Source Server: HP Prolient running Win Server 2012 R2 Essentials-All updates applied.
Target: QNAP TS-251 – current OS and updates applied.
Connection: Broadband Source:Comcast Blast, Target TCW, VPN: Sonicwall TZ-205s – updates applied.
Software: VVPro 64-bit Build 2515

Other info.
Problem has persisted over various hardware and software updates including VVPro.

Problem seems to be isolated to when running on server. I installed VVPro on a Win 7 PC and tested problem jobs – no errors. Problem on server is consistent and repeatable over a period of time on any given day- I can rerun the same job 5-6 times and it will have issues each time - normally on same larger files.

I tried running VVPro job while a windows copy was copying a very large file from the same source, over the same VPN to the same target – the copy would be successful, the VVPro would have network problems. Does the fact that widows copy works and VVPro has issues point to VVPro not dealing with transmission errors with the same ‘grace’ as copy?

Other copy program – CloudBerry and CrashPlan do run successfully every day on same server (although not over VPN and not to same target).

Other copy programs running on other sources machines run successfully to the same target over the VPN with no problems.

Vice Versa support has been looking at this for several months with no resolution yet. Any thoughts out there?

[TGRMN Software]

Hi,

did you already try activating the option "Use Windows native file copy"? This option instructs ViceVersa to use the Windows native file copy to copy files, instead of its own algorithm. So it would be the same as a copy with Windows Explorer. In certain situations, this option can improve performance / resolve issues. The option is in ViceVersa profile settings -> performance.

Other options to look at : Buffer size (bytes) and Flush buffer every write. They are on the same settings page. Try using a small buffer size and activate the option Flush buffer every write

Let us know how it goes.
thanks!
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[JerryEF]

Tried all the above - no joy. More details in email with Matt.

When we get a solution I will try to remember to post here for the benefit of others.

In my research I note that Microsoft has had issues with SMB. While this is a bit (way) over my head, does this sound like a direction to travel?

[JerryEF]

I problem has been somewhat helped along by a visit from the cable guy. There were apparently some questionable connections and components on the street side of my cable connection. This appears to have been responsible for much of the data errors I was experiencing.

Changing the VVPro execution performance to use Windows Copy had a positive impact too. Some of the improvement may have been because of using more 'native' windows copy code. Also, because the windows copy seems to provide a faster copy, each file copy took less time and (I suspect) was less exposed to network hiccups ???

While Things are much better than before, we are not there yet. I am still looking forward to getting a fix that handles errors better.