Multiple issues in replication over network

[PabloK]

Hi,

I wonder if anyone has meet issues like we do have.

We are using Vice Versa 2.0 Pro to replicate files stored on a server to several servers in another domains.

The replication task are set up using scheduled time and are restarting by default after 72h. We are using the method “backup and mirror” to ensure that all servers in the network are exactly same as the main server.

The task are using an general dedicated domain account with necessary privileges and accesses across domains.

The backup mirror tasks do look as following:

From:
\\source\sharedfolder\data
To target:
\\target\sharedfolder\data

The Vice Versa does have access to the shared folders with full rights.

At some points the replication works fine, but we meet following errors:

1. [Can not open “\\source\sharedfolder\data” The specified network name is no longer available.] [ERROR]

Where when checked manually all the servers and folders are available all the time, 24/7 and accessible by users. Issue occur multiple times.

2. Copying folder “\\source\sharedfolder\data” [Can not create “\\target\sharedfolder\data” Containing folder could not be created.] [ERROR].

3. [Can not open "\\source\sharedfolder\data\file.xxx". The specified network name is no longer available.] [ERROR].
While both servers and shares are available and accessible, Vice Versa account does have access too.

4. Unable to delete temporary file \\target\sharedfolder\data\folder\fvv1.tmp left from a previous run. [OK].

All 4 errors occur while replicating from “source” server to another servers in different domain.

The problems are strange, cause most of the data (about 60%) does replicate fine, but the rest – not, errors described as above.

I would be grateful if you could advise and assist.

Thanks & regards
PabloK
_________________
It's not a bug, it's an undocumented feature...

[TGRMN Software]

Hello

[Guest]

I have these items included in my profile, and have the drives mapped over the network, (and use the UNC path) AND the auto-disconnect feature turned off on my servers. I think that there may just be a timeout issue, when the VV isn't running for a few hours.

I can go to the mapped drive and click on it, to ensure that it's available, and then start the run with VV and it no longer has a connection issue. Is there a way to extend the VV timeout?

[TGRMN Software]

It's strange because ViceVersa just uses the Windows Networking to access the data, it does not implement any timeout internally....
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com