* [Topics](/en/topics "Topics") * [Linux](/en/topics/linux "Linux") * What is high availability? What is high availability? ========================== Updated March 28, 2025•*5*-minute read Copy URL Jump to section --------------- OverviewWhy is high availability important?How does high availability work?High availability and disaster recoveryWhat are high-availability clusters?How Red Hat helps achieve high availability What is high availability? -------------------------- *High availability* is the ability of an IT system to be accessible and reliable nearly 100% of the time, eliminating or minimizing downtime. It combines two concepts to determine if an IT system is meeting its operational performance level: that a given service or server is accessible–or available–almost 100% of the time without downtime, and that the service or server performs to reasonable expectations for an established time period. High availability is more than hitting an uptime service level agreement (SLA), or the expectations set between a service provider and client. It is about truly resilient, reliable, and well-functioning systems. This video can't play due to privacy settings To change your settings, select the "Cookie Preferences" link in the footer and opt in to "Advertising Cookies or try disabling adblockers." Why is high availability important? ----------------------------------- With the adoption of online services and hybrid workloads, there is greater demand for infrastructures to handle increased system loads while still maintaining operational standards. To achieve high availability, these infrastructures, often referred to as high availability systems, must hit defined, quantifiable outcomes beyond just "running better." One of the targets of high-availability solutions, or high availability services, is called *five-nines availability*, meaning that a system is running and performing well 99.999% of the time. Usually only mission critical systems like [healthcare](/en/solutions/healthcare), [government](/en/solutions/public-sector/us), and financial services require this level of availability for compliance or competitive reasons. However, many organizations and industries still require their high availability systems to maintain 99.9% or even 99.99% uptime to provide constant digital access for their customers or allow their employees to work from home. How to achieve high availability for Apache Kafka ------------------------------------------------- [Get the resource](/en/resources/high-availability-for-apache-kafka-detail "Get the resource") How does high availability work? -------------------------------- High-availability infrastructure is dependent on detecting and eliminating single points of failure that could contribute to increased system downtime and prevent organizations from reaching their performance goals. A single point of failure is an aspect of the infrastructure that could take the entire system offline, and in complex systems, multiple single points of failure can exist. Organizations also have to take into account the different types of failures that can occur in a modern, complex [IT infrastructure](/en/topics/cloud-computing/what-is-it-infrastructure). These include hardware failures, software failures (both for the operating system and for the running applications), service failures (such as inaccessible networking and latency or cloud services or performance degradation), and external failures, such as power outages. The first step each organization can take toward high availability is determining the specific, most important outcomes it wants to see based on its core services, workload and regulatory or compliance requirements, performance benchmarks, critical applications, and operational priorities: * What are the uptime requirements either for regulatory compliance or for user experience? * How distributed is the environment? What are the key points of failure? * What is the required performance for the application? What are the risks to that app's performance (e.g., high user traffic or heavy write loads)? * What kind of [storage](/en/topics/data-storage/why-choose-red-hat-storage) is in use? * What requirements are there around data loss or data access? * Given current IT resources, what are achievable SLAs in case of an outage? What are the current planned maintenance schedules, and what is the impact on uptime? * Are there plans around different disaster recovery scenarios or changes in business operations? With high-availability environments, there are also several common metrics that IT teams use to determine whether the high availability architecture is meeting its objectives. Some may be more relevant to your [architecture](/en/topics/cloud-native-apps/what-is-an-application-architecture) than others, but it is worthwhile to evaluate all of them to set baseline performance expectations: * **Mean time between failures (MTBF)**: How long the environment operates between a system failure. * **Mean downtime**: How long the system is down (minutes of downtime) before it is recovered or replaced in the topology. * **Recovery time objective (RTO)**: The total time it takes to complete a repair and bring a system back online. * **Recovery point objective (RPO)**: The period of time in which you need to be able to recover data. This is the window of lost data. For example, if a system is relying on bringing in another system from backups and the backups are taken daily, then there could be up to 24 hours of lost data in the recovered system. However, if there is replicated or shared storage, then the data loss may only be minutes or even less. High availability and disaster recovery --------------------------------------- A high-availability architecture incorporates principles from each layer of continuity planning, such as monitoring and [automation](/en/topics/automation). This allows the overall system to be resilient to all types of failures, from specific local failures to an overall outage. It even allows the overall system to remain operational even with planned maintenance windows and other service interruptions. A disaster recovery or continuity plan would incorporate approaches for each potential failure: * **Anticipate specific failures**: For each of those areas, IT architects first make sure that systems are redundant, and that backup systems are available in case of a failure. The next step is to automate failover and failure-detection processes so that down systems are automatically detected and services are switched to the backup system. * **Manage performance proactively**: Fault tolerance will address an outage, but it won’t necessarily deal with performance degradation. This is where load balancing and scalability become useful tools. In this case, IT architects monitor system performance and use multiple systems to manage user requests and operations. Load balancers and traffic management can intelligently route traffic in real time based on bandwidth, system performance, user, or request type. * **Deal with catastrophe**: Widespread infrastructure failures–like a cloud provider going down, a natural disaster at a data center site–are rare, but they require a more comprehensive approach than hardware/software failures alone. Along with bringing the infrastructure back online, it is necessary to have up-to-date data available. This can be done synchronously through replication (though there are performance risks) or asynchronously through data backups (with some risk of data loss). [Maximize your business continuity](/en/resources/maximize-business-continuity-datasheet "resources | Maximize business continuity - HTML") What are high-availability clusters? ------------------------------------ High-availability architectures run active failover clusters, so there is built-in redundancy and failover and—hopefully—zero downtime. Within the cluster, nodes are monitored not just for availability, but for overall performance of applications, services, and network. Because there is shared storage, there is no data loss if a node goes down, because all cluster nodes work from the same data source. Load balancing can be used to manage traffic for best performance. Outside those broad characteristics, high-availability clusters can be designed for more specialized activities, depending on the priorities and activities within the IT infrastructure. The [Red Hat Enterprise Linux High Availability Add-on](/en/store/high-availability-add), for example, has four default configurations: * **High availability**: focuses on uptime and availability * **High performance**: for high speed, concurrent operations * **Load balancing**: for cost-effective scalability * **Storage**: for resilient data management In real-life environments, the high-availability systems  would incorporate aspects of those focus elements. > I enjoy the patching processes and the way Red Hat Enterprise Linux has elements set up. I have never had a patch session fail, even when installing a thousand packages at a time. > > Bruce Lundberg > > Linux HPC Systems Administrator Read more reviews How Red Hat helps achieve high availability ------------------------------------------- High availability spans the entire infrastructure, accounting for [data and storage management](/en/topics/data-services/what-is-data-management) in separate environments–both [cloud](/en/topics/cloud-native-apps) and physical–and different locations for services and applications. This is why a common platform and [standard operating environment](/en/topics/management/what-is-an-soe) can be so powerful: it creates consistency regardless of the deployment environment. [Red Hat Enterprise Linux](/en/technologies/linux-platforms/enterprise-linux) has additional capabilities and services that can be included through add-on packages. The [Red Hat Enterprise Linux High Availability Add-on](/en/store/high-availability-add) addresses the networking, clustering, and storage aspects of the topology. Because high availability is so entwined with [data management](/en/topics/data-services/what-is-data-management), Red Hat Enterprise Linux deployments for [Microsoft SQL Server](/en/technologies/linux-platforms/enterprise-linux/sql-server) and [SAP](/en/technologies/linux-platforms/enterprise-linux/sap) also include the Red Hat Enterprise Linux High Availability Add-on. According to IDC, standardizing on Red Hat Enterprise Linux could result in [313% increase](/en/engage/idc-business-value-of-standardizing-analyst-material) in your return on investment (ROI) over three years. [See how Red Hat Enterprise Linux provides value to your organization](/en/resources/seven-ways-gain-business-value-enterprise-linux-checklist "resources | 7 ways to gain business value with Red Hat Enterprise Linux - HTML") Resource Red Hat Enterprise Linux Resilient Storage Add-On ------------------------------------------------- Read how Resilient Storage Add-On protects critical business data from software or system failures with cluster management and automated app recovery. [Get the resource](/en/resources/enterprise-linux-resilient-storage-add-on-datasheet "Red Hat Enterprise Linux Resilient Storage Add-On") All Red Hat product trials -------------------------- Our no-cost product trials help you gain hands-on experience, prepare for a certification, or assess if a product is right for your organization. [Keep reading](/en/products/trials "All Red Hat product trials") Keep reading ------------ ### What is an image builder? An image builder is a tool used to create a copy of a virtual system or configuration that can then be used as a base from which developers can build and deploy these systems on other machines or platforms. [Read the article](/en/topics/linux/what-is-an-image-builder "article | What is an image builder?") ### Why choose Red Hat for Linux? Workloads need to be portable and scalable across environments. Red Hat Enterprise Linux is your consistent, stable foundation across hybrid cloud deployments. [Read the article](/en/topics/linux/why-choose-red-hat-enterprise-linux "article | why choose red hat for linux?") ### What is Linux? Linux is an open source operating system made up of the kernel, the base component of the OS, and the tools, applications, and services bundled with it. [Read the article](/en/topics/linux/what-is-linux "article | what is linux?") Linux resources --------------- ### Related content * Datasheet [[node:rh-smart-meta-title]](/en/resources/linux-extended-life-cycle-premium-datasheet) * Blog post [Enabling long-term stability: Introducing Red Hat Enterprise Linux Extended Life Cycle, Premium](/en/blog/ensuring-long-term-stability-introducing-red-hat-enterprise-linux-extended-life-cycle-premium-rhel-extended-life-cycle) * Blog post [(Re)Introducing the Red Hat Universal Base Image](/en/blog/introducing-red-hat-universal-base-image) * Blog post [Red Hat Enterprise Linux now supported for Microsoft SQL Server on Azure VMs with SQL IaaS Agent extension](/en/blog/red-hat-enterprise-linux-now-supported-microsoft-sql-server-azure-vms-sql-iaas-agent-extension) ### Related articles * [What is an image builder?](/en/topics/linux/what-is-an-image-builder) * [Why choose Red Hat for Linux?](/en/topics/linux/why-choose-red-hat-enterprise-linux) * [Linux for cloud computing](/en/topics/linux/linux-for-cloud-computing) * [How to move to Red Hat Enterprise Linux from other Linux distros](/en/technologies/linux-platforms/enterprise-linux/migration-process/convert2rhel) * [Why run Microsoft SQL Server on Linux?](/en/topics/linux/why-run-sql-server-on-linux) * [What is Linux?](/en/topics/linux/what-is-linux) * [What is post-quantum cryptography?](/en/topics/security/post-quantum-cryptography) * [What is the SAP HANA migration?](/en/topics/linux/what-is-sap-hana-migration) * [What is lightweight directory access protocol (LDAP) authentication?](/en/topics/security/what-is-ldap-authentication) * [Red Hat Enterprise Linux security](/en/technologies/linux-platforms/enterprise-linux/security) * [Why run Linux on AWS?](/en/topics/linux/linux-on-aws) * [What is ERP?](/en/topics/linux/what-is-erp) * [Functional safety and continuous certification on Linux](/en/topics/open-source/functional-safety-and-continuous-certification-on-linux) * [What is SAP HANA (and why does it run on Linux)?](/en/topics/linux/sap-hana-and-linux) * [Why run Linux on IBM Cloud](/en/topics/linux/linux-on-ibm-cloud) * [What is CentOS Stream?](/en/topics/linux/what-is-centos-stream) * [Why choose Red Hat Enterprise Linux on Azure?](/en/technologies/linux-platforms/enterprise-linux/why-choose-red-hat-enterprise-linux-on-azure) * [Why choose Red Hat Enterprise Linux on AWS?](/en/technologies/linux-platforms/enterprise-linux/why-choose-red-hat-enterprise-linux-on-aws) * [Linux on Azure](/en/topics/linux/linux-on-azure) * [Red Hat Enterprise Linux migration process](/en/technologies/linux-platforms/enterprise-linux/migration-process) * [What to know about CentOS Linux EOL](/en/topics/linux/centos-linux-eol) * [What to know for Red Hat Enterprise Linux 7 End of Maintenance](/en/technologies/linux-platforms/enterprise-linux/rhel-7-end-of-maintenance) * [What is CentOS?](/en/topics/linux/what-is-centos) * [Why run Linux on Google Cloud?](/en/topics/linux/linux-on-google-cloud) * [Red Hat Satellite on Red Hat Enterprise Linux](/en/technologies/management/satellite/satellite-for-rhel) * [Why choose Red Hat Enterprise Linux on Google Cloud?](/en/technologies/linux-platforms/enterprise-linux/why-choose-red-hat-enterprise-linux-google-cloud) * [What is Linux kernel live patching?](/en/topics/linux/what-is-linux-kernel-live-patching) * [What's the difference between Fedora and Red Hat Enterprise Linux](/en/topics/linux/fedora-vs-red-hat-enterprise-linux) * [What's the best Linux distro for you?](/en/topics/linux/whats-the-best-linux-distro-for-you) * [What is a Linux server?](/en/topics/linux/linux-server) * [What is a configuration file?](/en/topics/linux/what-configuration-file) * [What is high performance computing (HPC)?](/en/topics/high-performance-computing/what-is-high-performance-computing) * [What is a golden image?](/en/topics/linux/what-is-a-golden-image) * [What is an ARM processor?](/en/topics/linux/what-is-arm-processor) * [ARM vs x86: What's the difference?](/en/topics/linux/ARM-vs-x86) * [What is MPLS?](/en/topics/edge-computing/what-is-mpls) * [What is a Linux certification?](/en/topics/linux/linux-certification) * [What was CoreOS and CoreOS container Linux](/en/technologies/cloud-computing/openshift/what-was-coreos) * [What is SELinux?](/en/topics/linux/what-is-selinux) * [What is the Linux kernel?](/en/topics/linux/what-is-the-linux-kernel) [More about this topic](/en/topics/linux "More about this topic")