Hi everyone, recently I have started having problems with replication runs. It happens once or twice per week, that some of our 3 VMs fail to replicate, while some finish just fine. Please check the error code below:
07/10/2014 07:45:25 :: Processing 'Y3SMSG' Error: Client error: Failed to open VDDK disk [[esxi00_storage1] Y3SMSG_replica/EBS08-MAIL_1-000002.vmdk] ( is read-only mode - [false] )
Failed to open VMDK.
Logon attempt with parameters [VC/ESX: [10.3.0.72];Port: 902;Login: [****];VMX Spec: [moref=5];Snapshot mor: [5-snapshot-621];Transports: [nbd];Read Only: [false]] failed because of the following errors:
Failed to process [srcReplicateVddkDiskContent] command.
An existing connection was forcibly closed by the remote host
I would suggest you to contact Veeam Support Team for the problem investigation.
The reason might be that the target proxy server didn't unmount disks failed server, which in its turn resulted in failed job. Once the were manually unmounted, everything started to work as expected. The solution is described here. But, it`s better to work on that with the support team.
Hi, the support case isn't closed yet but until proven otherwise the suggested solution is to increase the number of concurrent tasks for each proxy to maximum possible while still having the green tick. Also to make sure that the Parallel processing option is enabled in Options > Advanced.
I will come back with the conclusion after a week's worth of monitoring.
Hi, it's a "Case # 00649058" but your colleague from the business support and I have agreed to monitor the issue for a week after doing the above. This is to make sure that the issue is really solved because of its intermittent nature. No need to chase it!
Morgenstern wrote:Hi, the support case isn't closed yet but until proven otherwise the suggested solution is to increase the number of concurrent tasks for each proxy to maximum possible while still having the green tick. Also to make sure that the Parallel processing option is enabled in Options > Advanced.
I will come back with the conclusion after a week's worth of monitoring.
Now that the case has been successfully closed I can confirm that the above is the confirmed solution to this issue.