Lead Image © crazymedia, 123RF.com
QoS Systems for Disaster Recovery Support
Lifeline
After a catastrophic failure of the IT infrastructure – whether from damage to undersea cables, weather, or pilfering by copper thieves – restoring full bandwidth between the individual nodes of a network can take days or even weeks. The quality of the user experience during these emergency operations depends on how quickly applications and core services respond to requests. Efficient bandwidth and latency management is crucial for a company's disaster recovery (DR) strategy, and tools such as LibreQoS can help you allocate scarce resources and prioritize latency-critical services.
QoS Data Stream Priorities
From a user experience perspective, some packets are not as important as others. Whereas higher latency during a Windows update or when uploading an object store BLOB is not particularly critical, a 100ms delay in voice or video connections is disruptive.
As shown in Figure 1, quality-of-service (QoS) systems sit between local and global networks. Packets passing through are classified and then prioritized or throttled by applying various algorithms. Note that QoS systems do not interact with intranet packets: Prioritizing the connection between two stations located on the same network is not supported.
...
Buy this article as PDF
(incl. VAT)
Buy ADMIN Magazine
Subscribe to our ADMIN Newsletters
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Most Popular
Focus On Self-Hosting
• Wiring the Modern Stack with Node-RED
• Self-Hosted Collaboration with Forgejo
• Self-Hosted PaaS with Coolify
• Build and Host Docker Images
• Self-Hosted Pritunl VPN Server with MFA
• Self-Hosted Chat Servers
Support Our Work
ADMIN content is made possible with support from readers like you. Please consider contributing when you've found an article to be beneficial.
