How it works
How WAN optimization works
Physical or virtual Wanos appliances are placed on each end of the link. Traffic crosses the WAN optimized between them, and the solution is 100% transparent to end stations.
The solution
One appliance on each side of the WAN
- Stream compression and deduplication through byte-caching, in real time.
- Less data over the WAN means bandwidth cost savings, faster applications and a better user experience.
- Quality of service, packet loss recovery and forward error correction improve link performance.
- TCP acceleration significantly improves performance over sub-optimal network conditions.
- SD-WAN path selection moves bandwidth-intensive traffic to a secondary broadband link.
AIVA: replication approaches 40 Mbps while the WAN remains at 11 Mbps, saving 1.2 TB in a week.
Quick demo
A file copied over a 6.5 Mbps WAN link
Optimization is disabled on the first transfer, with a copy speed of 800 KBytes/s (the WAN link rate). With WAN optimization enabled, the warm byte-cached data delivers 80+ Mbps, or more than 10x WAN acceleration.
The results
Wanos has helped us to improve replication throughput more than twofold. Although we also trialed the leading WAN optimization products, we selected Wanos since it provided one of the best ROIs.
Jorge Redondo, Head of Business Technology, AIVA
Replication approaches 40 Mbps while the WAN remains at 11 Mbps, resulting in 1.2 TB saved for the week.
40 Mbps replication on the LAN
11 Mbps on the WAN
1.2 TB saved in the week
Use cases
Where Wanos is used
- Accelerate backup and replication
- Accelerate WAN and cloud applications
- Accelerate branch broadband VPN
- TCP acceleration for high-latency links
- Load balance between MPLS and broadband fibre
- Improve network visibility
Deployment
Deployment options
- Bridge mode by default: quick and simple to deploy, non-intrusive, and it preserves the natural traffic flow
- Tunnel mode as a flexible way to route traffic through the optimizer
- Physical or virtual: ESXi, Hyper-V, KVM, XenServer, Proxmox, LXD, AWS, Azure, bare metal or a Wanos appliance
- Deployment guides in the docs