Solved

Veeam Error: Reconnectable socket has beed forcibly closed. Failed to recover connection.

Posted on 2015-01-28
2
740 Views
Last Modified: 2016-02-25
Veeam Replication Problem
I have 1 problem with Big VM when Replication first time with Seeding from Backup VM in DR site
The Replication started but stop after some hours and give me this error –

Error: Reconnectable socket has beed forcibly closed. Failed to recover connection.

it’s stopped after digest 4 VMDK HDDs from 8 VMDK HDDs
VM size : 2.2TB
Using WAN Speed ( 30MB)
0
Comment
Question by:alfanarsupport
2 Comments
 
LVL 16

Accepted Solution

by:
Dirk Mare earned 500 total points
ID: 40575231
1, Veeam has excellent support and I would recommend logging a support ticket with them directly.

2. Replication of that size I would do a Local backup of it and transfer the backup to site and use that backup as a repository for the replication job (once off) This is just to get the bulk of the data at your DR site.

3. The error, the drop in communication between your site and DR is probably the cause of the issue.

DirkMare
0
 
LVL 5

Expert Comment

by:MaximVeeam
ID: 40577135
I agree w/ Dirk Mare.

Veeam Support - https://www.veeam.com/support.html

This thread on Veeam Community Forums might be helpful - http://forums.veeam.com/vmware-vsphere-f24/wan-replication-failing-t3458.html
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Linux VM 6 88
Storage DRS Recommendation Alert 3 37
VMware tools installation after domain controller promotion 4 45
How many VM guests can I expect to host? 5 72
If your vDisk VHD file gets deleted from the image store accidentally or on purpose, you won't be able to remove the vDisk from the PVS console. There is a known workaround that is solid.
Will try to explain how to use the VMware feature TAGs in the VMs and create Veeam Backup Jobs using TAGs. Since this article is too long, I will create second article for the Veeam tasks.
Teach the user how to edit .vmx files to add advanced configuration options Open vSphere Web Client: Edit Settings for a VM: Choose VM Options -> Advanced: Add Configuration Parameters:
Teach the user how to configure vSphere clusters to support the VMware FT feature Open vSphere Web Client: Verify vSphere HA is enabled: Verify netowrking for vMotion and FT Logging is in place or create it: Turn On FT for a virtual machine: Verify …

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question