AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Veeam backup proxy best practice8/5/2023 While, in most cases, day-to-day replication will not consume much bandwidth, operations such as seeding, reprotection and full backup will be rendered impossible with lower bandwidth connections Maintaining Replication and Remote Backup becomes impractical with site-to-site connections less than 20 Mbps and almost impossible with connections less than 10 Mbps. You can get much closer to “stated bandwidth” on slower connections.Note: IP address is example onlyįor throughput VMN or MPLS traffic, we have come to expect sustained rates about 75%-85% of our WAN connectivity on 100+ Mbps connections. Higher-bandwidth connections are more difficult to test accurately. We use iperf to test and baseline available bandwidth from point-to-point. Software VPN (and there are many enterprise options available plus grow-your-own based on BSD, RHEL, CentOS) seems to be limited only by how much horsepower (vCPU) you wish to devote to it. We have found that even relatively hi-end hardware firewall/VPN does not have the horsepower to maintain VPN throughput over about 40-60 Mbps (regardless of proximity or WAN speed). IPsec VPN can not only be configured to automatically fail-over between ISP’s, but can also follow the Sites from one location to another in the event of relocation. Our preferences for establishing the Site-to-Site connection: I know this topic comes round from time-to-time, but I thought I would share some conclusions ( hopefully get others conclusions too) about Network and Technical Best Practices for Replication and Remote Backup.
0 Comments
Read More
Leave a Reply. |