I'm doing (or trying to do) an offsite replica task though VPN
Before moving offsite I've been doing in-site replicas without any problem.
For this offsite task I've used as the replica mapping VM the same replica VM that was generated through the in-site replication. In fact, on this task either the destination proxy and the destination host are the same used in the in-site replica, with the only exception that both have new IPs because both are now in a remote VPN.
The off-iste job is configured exactly the same as the in-site job, with the exception of the destination ESXi an the destination veeam proxy's IPs
The error appears on every task allways after two hours (always after two hours since the job started). The event that is running at that point is "Calculating digests hard disk", which never reaches 100%. The error string is:
- Code: Select all
Error: Client error: VDDK error: 1.Unknown error Failed to process [calcDiskDigestsCli].
A deeper look at the replica task logfile reveals this error event:
- Code: Select all
[27.02.2013 14:41:36] <09> Info [AP] (fb87) error: VDDK error: 1.Unknown error\n--tr:Disk read operation has failed. Disk path: [[XxxxXxxx_Datastore] XXXXX.domain.name/XXXXX.domain.name-000002.vmdk]. Read offset: [317,005,496,320]. Requested data size: . Disk size: [1,782,688,251,904]\n--tr:Failed to pre-read data ( first start block '1209280', blocks num '16'. Block size: '262144').\n--tr:Next asynchronous read request cannot be processed.\n--tr:Asynchronous data reader has failed.\n--tr:Failed to recalculate digests.\nFailed to process [calcDiskDigestsCli].\n--tr:Client failed to process the command. Command: [calcDiskDigestsCli].\n
So it seems that there is a problem with that snapshot on the replica mapping VM.
The VPN connection is stable and I haven't noticed any problem with it.
As per veeam's documentation «...under Replicas node you will see a VM replica with two restore points. One point will contain the latest state of the mapped VM (the VM located on the target host); the other point will contain the latest state of the original VM on the source host.»
Since the conflicting snapshot is numbered 000002, I understand that it's the one that contains the latest state of the original VM. However I'm pretty sure that no data is transfered yet between the Source ESXi and the Destination ESXi when the error happens.
Can you give any hints or thoughts about this problem?
Thank you in advance.