What is a high availability VPN?
What is a high availability VPN?

    Requires Free Membership to View

    Login

    When you register for SearchStorage.com, you’ll also receive targeted emails from my team of award-winning editorial writers. Our goal is to keep you informed on the hottest topics, the latest news and the biggest challenges you face as a storage professional today.

    Rich Castagna, Editorial Director

    By submitting your registration information to SearchStorage.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchStorage.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Essentially, a highly available VPN is one where the VPN can quickly and easily recover from component failure, and continue to provide service. Of course, high availability is almost never a black or white sort of thing; there are always degrees of availability. How long does the VPN take to recover after a component has failed? What performance impact does the insertion of high availability intelligence introduce? What is the visible impact upon a connected user after a failover has taken place?

Since performance is also a factor in availability, load balancing may also be a requirement in building a highly available VPN.

As with all highly available solutions, a balance must be made between the level of availability required and the cost of implementing the solution. The cost could be monetary, but it could also take the form of slower performance, user inconvenience, implementation downtime, or in some other way. Each of these forms can also be expressed in terms of money, of course.

This was first published in June 2004

Back to top