I am running Veeam Backup and Replication in two different data centers. In Data Center A all of the servers are on a Brocade 10 Gig switch and the switch and servers are behind a Sonicwall 2400 running Firmware version SonicOS Enhanced 126.96.36.199-36o. I can replicate from server to server without issue.
In Data Center B all of the servers are also on a Brocade 10 Gig switch and the switch and servers are behind a Sonicwall 3500 running Firmware version SonicOS Enhanced 188.8.131.52-17o which admittedly is quite old. In this environment I am having issues.
Everything is running on Windows Hyper-V running 2012 R2.
In data center A I can replicate from any server to any server without issue. I can also replicate from data center A to servers in data center B without issue. Not bad considering the distance is over 2600 miles.
In data center B however things are much different. Whether I am trying to replicate from data center B to data center A or am trying to replicate between servers in data center B I always get the same error as shown below.
3/31/2017 2:34:36 PM :: VM processing started at 3/31/2017 2:34:36 PM
3/31/2017 2:34:36 PM :: VM size: 225.0 GB
3/31/2017 2:34:53 PM :: Preparing to create snapshot
3/31/2017 2:34:54 PM :: Hyper-V Integration Services are not up to date
3/31/2017 2:34:56 PM :: Creating snapshot Microsoft Software Shadow Copy provider 1.0 (mode: Crash consistent)
3/31/2017 2:35:08 PM :: Using source proxy Servername (onhost)
3/31/2017 2:35:12 PM :: Network traffic will be encrypted
3/31/2017 2:35:31 PM :: Processing configuration
3/31/2017 2:36:08 PM :: Closing snapshot
3/31/2017 2:36:16 PM :: Failed to process replication task Error: Failed to connect to the port [Servername:2500].
3/31/2017 2:36:16 PM :: Network traffic verification detected no corrupted blocks
3/31/2017 2:36:16 PM :: Processing finished with errors at 3/31/2017 2:36:16 PM
So far I have confirmed all ports on both sonicwalls are configured correctly and open. The same is true for the Windows Hyper-V nodes. I have also tried to shut off the Windows firewalls but get the same results. I have also checked my Sonicwalls to be sure the settings are correct. At this point I am leaning that the firmware on the Sonicwall 3500 is to old and causing the problem but I am not sure.
Other than doing the firmware upgrade, which I am reticent to do as I am remote. Can anyone think of another reason why this will not work. Veeam support has looked at the logs and they are not sure why this is happening.
Any input here would be greatly appreciated