Hello Veeam,
considering you have TCP connection problems and resume errors during BackupCopy-Jobs using WAN Accelerators ...
How is this done on VIA-based WAN Accelerators or is this no longer necessary to configure in Veeam machines?
Quote:
How to Fix It1. Increase Firewall TCP Timeout (Recommended). The most reliable fix is to configure your edge firewalls or VPN appliances to have an extended TCP idle timeout (e.g., 240 minutes or 1440 minutes) specifically for traffic traveling between your WAN accelerator IPs. Open the Registry Editor (regedit) on both WAN accelerator machines. Navigate to: HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\ParametersCreate or modify the following DWORD (32-bit) values:KeepAliveTime: Set to 300000 (Decimal, which equals 5 minutes). This controls how frequently a keep-alive packet is sent when a connection is idle.KeepAliveInterval: Set to 1000 (Decimal, 1 second). This controls the interval between retries if a keep-alive response isn't received. Restart the servers for these OS-level TCP changes to take effect.
-
Didi7
- Veteran
- Posts: 655
- Liked: 113 times
- Joined: Oct 17, 2014 8:09 am
- Location: Hypervisor
- Contact:
TCP Keep Alive on WAN Accelerators (VIA-based)
Using the most recent Veeam B&R in many different environments now and counting!
*** Nominated for being the earliest early adopter of VSA ***
*** Nominated for being the earliest early adopter of VSA ***
-
Mildur
- Product Manager
- Posts: 12262
- Liked: 3521 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: TCP Keep Alive on WAN Accelerators (VIA-based)
Hi Didi7,
Such custom configuration must not be done by a customer themselves on the appliances.
If you notice issues with the TCP connections, first you should troubleshot it with our Support Team which will reach out to our R&D team if necessary. Any specific custom configuration parameters for VIA will then be tested and approved by our R&D team.
May I ask where you got this "quote"?
Best,
Fabian
Such custom configuration must not be done by a customer themselves on the appliances.
If you notice issues with the TCP connections, first you should troubleshot it with our Support Team which will reach out to our R&D team if necessary. Any specific custom configuration parameters for VIA will then be tested and approved by our R&D team.
May I ask where you got this "quote"?
Best,
Fabian
Product Management Analyst @ Veeam Software
-
Didi7
- Veteran
- Posts: 655
- Liked: 113 times
- Joined: Oct 17, 2014 8:09 am
- Location: Hypervisor
- Contact:
Re: TCP Keep Alive on WAN Accelerators (VIA-based)
Hi Fabian,
allright. Let's hope that TCP Keep Alive settings on Firewall or Cisco Gateways might fix the problems.
The output is from Google AI and the question was ...
"veeam wan accelerator resume connection tcp keep alive"
allright. Let's hope that TCP Keep Alive settings on Firewall or Cisco Gateways might fix the problems.
The output is from Google AI and the question was ...
"veeam wan accelerator resume connection tcp keep alive"
Using the most recent Veeam B&R in many different environments now and counting!
*** Nominated for being the earliest early adopter of VSA ***
*** Nominated for being the earliest early adopter of VSA ***
Who is online
Users browsing this forum: d.artzen, DuckDuckGo [Bot], Google [Bot] and 70 guests