Skip to content

Commit d3efb25

Browse files
Merge pull request #295519 from anaharris-ms/freshness-reliability-overview
Reliability - Overview freshness
2 parents 579cb3f + 983d066 commit d3efb25

File tree

3 files changed

+30
-9
lines changed

3 files changed

+30
-9
lines changed

articles/reliability/concept-failover-failback.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ author: anaharris-ms
1010
ms.custom: subject-reliability
1111
---
1212

13-
# Failover and failback
13+
# What are failover and failback?
1414

1515
This article provides a general overview of how both *failover* and *failback* operate in a cloud environment. However, to understand failover, you should first understand redundancy and replication. To learn about those concepts before continuing with this article, see [Redundancy, replication, and backup](./concept-redundancy-replication-backup.md).
1616

articles/reliability/concept-redundancy-replication-backup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ author: anaharris-ms
1010
ms.custom: subject-reliability
1111
---
1212

13-
# Redundancy, replication, and backup
13+
# What are redundancy, replication, and backup?
1414

1515
We often think about the cloud as a globally distributed, ubiquitous system. However, in reality the cloud is made up of hardware running in datacenters. Resiliency requires that you account for some of the risks associated with the physical locations in which your cloud-hosted components run.
1616

articles/reliability/overview.md

Lines changed: 28 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
11
---
22
title: Azure reliability documentation
3-
description: Overview of Azure reliability documentation, including platform capabilities, the shared responsibility model, and how each Azure service supports reliability.
3+
description: Overview of Azure reliability documentation, incuding platform capabilities, guides for how each Azure service supports reliability, and reliability fundamentals.
44
author: anaharris-ms
55
ms.topic: overview
6-
ms.date: 01/28/2025
6+
ms.date: 02/28/2025
77
ms.author: anaharris
88
ms.service: azure
99
ms.subservice: azure-reliability
@@ -17,10 +17,14 @@ The Azure reliability documentation provides information on what reliability mea
1717

1818
The documentation is organized into the following sections:
1919

20-
- **Azure reliability guides by service.** Learn how each Azure service supports reliability, including availability zones, multi-region support, and backup support.
21-
- **Reliability fundamentals.** Learn about the concepts of reliability, business continuity, high availability, and disaster recovery. Understand how shared responsibility works between Microsoft and you.
22-
- **Azure regions.** Learn about Azure regions, paired and nonpaired regions, and the list of services that are deployed to Azure regions.
23-
- **Azure availability zones.** Learn about availability zones, including how they support high availability and disaster recovery, and which Azure services and regions support availability zones.
20+
- **Azure reliability guides by service** contains guides on how each Azure service supports reliability, including availability zones, multi-region support, and backup support.
21+
- **Reliability fundamentals** contains fundamental reliability concepts, such as:
22+
- Business continuity, high availability, and disaster recovery.
23+
- Redundancy, replication (Data redundancy), and backup
24+
- Failover and failback.
25+
- Shared responsibility between Microsoft and you.
26+
- **Azure regions** contains information on Azure regions, paired and nonpaired regions, and different region configurations.
27+
- **Azure availability zones** contains information on how availability zones, including how they support high availability and disaster recovery. The section also includes lists of Azure services and regions that support availability zones.
2428

2529
## What is reliability?
2630

@@ -61,7 +65,24 @@ When considering business continuity, it's important to understand the following
6165

6266
- *Disaster recovery* is about planning how to deal with uncommon risks and the catastrophic outages that can result.
6367

64-
For more information on business continuity and business continuity planning through high availability and disaster recovery design, see [What are business continuity, high availability, and disaster recovery?](./concept-business-continuity-high-availability-disaster-recovery.md)
68+
For information on business continuity and business continuity planning through high availability and disaster recovery design, see [What are business continuity, high availability, and disaster recovery?](./concept-business-continuity-high-availability-disaster-recovery.md).
69+
### Redundancy, replication, and backup
70+
71+
We often think about the cloud as a globally distributed, ubiquitous system. However, in reality the cloud is made up of hardware running in datacenters. Resiliency requires that you account for some of the risks associated with the physical locations in which your cloud-hosted components run.
72+
73+
*Redundancy* is the ability to maintain multiple identical copies of a service component, and to use those copies in a way that prevents any one component from becoming a single point of failure.
74+
75+
*Replication* or data redundancy is the ability to maintain multiple copies of data, called replicas.
76+
77+
*Backup* is the ability to maintain a timestamped copy of data that can be used to restore data that has been lost.
78+
79+
For an introduction to redundancy, replication, and backup, see [What is redundancy, replication, and backup?](./concept-redundancy-replication-backup.md).
80+
81+
### Failover and failback
82+
83+
A common reason for maintaining redundant copies of both applications and data replicas is to be able to perform a failover. With failover, you can redirect traffic and requests from unhealthy instances to healthy ones. Then, once the original instances become healthy again, you can perform a failback to return to the original configuration.
84+
85+
For more information on failover and failback, see [What is failover and failback?](./concept-failover-failback.md).
6586

6687
### Shared responsibility
6788

0 commit comments

Comments
 (0)