Skip to content

Commit 2b431c0

Browse files
committed
edit
1 parent 5053fd7 commit 2b431c0

1 file changed

Lines changed: 8 additions & 8 deletions

File tree

articles/reliability/reliability-community-training.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Community Training uses Azure availability zones to provide high availability an
2424

2525
- The [control plane](/azure/azure-resource-manager/management/control-plane-and-data-plane#control-plane) is zone redundant in the primary regions of availability.
2626

27-
- The [data plane](/azure/azure-resource-manager/management/control-plane-and-data-plane#data-plane) can be either zonal or zone-redundant, depending on what you choose for your needs. However, it is highly recommended that you choose a zone-redundant deployment in order to avoid data loss and maintain service availability in the case of a zone outage.
27+
- The [data plane](/azure/azure-resource-manager/management/control-plane-and-data-plane#data-plane) can be either zonal or zone-redundant, depending on what you choose for your needs. However, it's highly recommended that you choose a zone-redundant deployment in order to avoid data loss and maintain service availability during a zone outage.
2828

2929

3030
### Prerequisites
@@ -51,7 +51,7 @@ Community Training uses Azure availability zones to provide high availability an
5151

5252
### Zonal failover support
5353

54-
Community Training uses a number of dependency Azure services, such as App service and Azure SQL. When you choose a zone redundant deployment, Community Training also creates zonal redundant offerings of those underlying Azure service resources. If one zone fails, all resources, including dependency resources, fail over to one of the healthier zones.
54+
Community Training uses many dependency Azure services, such as App service and Azure SQL. When you choose a zone redundant deployment, Community Training also creates zonal redundant offerings of those underlying Azure service resources. If one zone fails, all resources, including dependency resources, fail over to one of the healthier zones.
5555

5656

5757
#### Create a resource with availability zone enabled
@@ -60,24 +60,24 @@ Community Training provides configuration for availability zones only at the tim
6060

6161
### Zone down experience
6262

63-
- **Zonal zone down experience**. During a zone-wide outage, Community Training can have either complete or partial service disruption. The extent to which it is available depends on various factors, such as whether the entire datacenter is down, or whether a specific dependency service isn't no longer available in that zone.
63+
- **Zonal zone down experience**. During a zone-wide outage, Community Training can have either complete or partial service disruption. The extent to which it's available depends on various factors, such as whether the entire datacenter is down, or whether a specific dependency service isn't no longer available in that zone.
6464

65-
- **Zone redundant zone down experience**. During a zone-wide outage, you won't experience any impact on provisioned resources. However, you should be prepared for a brief interruption in communication with those resources. In a zone down situation, Clients typically receive 409 error codes, as well as retry logic attempts to re-establish connections at appropriate intervals. New requests are directed to healthy nodes with zero impact on the user. During zone-wide outages, users are able to create new resources and successfully scale existing ones.
65+
- **Zone redundant zone down experience**. During a zone-wide outage, you shouldn't experience any impact on provisioned resources. However, you should be prepared for a brief interruption in communication with those resources. In a zone down situation, Clients typically receive 409 error codes, as well as retry logic attempts to re-establish connections at appropriate intervals. New requests are directed to healthy nodes with zero impact on the user. During zone-wide outages, users are able to create new resources and successfully scale existing ones.
6666

6767
## Disaster recovery and business continuity
6868

6969
[!INCLUDE [introduction to disaster recovery](includes/reliability-disaster-recovery-description-include.md)]
7070

71-
The entire disaster recovery procedure for Community Training is manually managed by the Community Training team. Disaster recovery is not active-active or active passive, but is instead based on recovery from the most recent available backup of Azure services. The Community Training team manually creates all resources in the paired region from data backup.
71+
The Microsoft Community Training team manages the entire disaster recovery procedure for Community Training. Disaster recovery isn't active-active or active passive, but is instead based on recovery from the most recent available backup of Azure services. The Community Training team manually creates all resources in the paired region from data backup.
7272

7373
>[!NOTE]
7474
>Community Training disaster recovery is only supported in [paired regions](./cross-region-replication-azure.md#azure-paired-regions).
7575
7676
### Disaster recovery in multi-region geography
7777

78-
- In the case of regional disaster, the **control plane** is manually failed over to the paired region. You should expect some service degradation in the time before the failover completes. After the failover, only read-only operations are supported until the disaster region is back online. The service is manually failed back to the original region once it's back online and all operations resume. Recovery Point Objective (RPO) is expected to be ten minutes; Recovery Time Objective (RTO), 24 hours.
78+
- In a regional disaster, the **control plane** is manually failed over to the paired region. You should expect some service degradation in the time before the failover completes. After the failover, only read-only operations are supported until the disaster region is back online. The service is manually failed back to the original region once it's back online and all operations resume. Recovery Point Objective (RPO) is expected to be 10 minutes; Recovery Time Objective (RTO), 24 hours.
7979

80-
- For the **data plane**, Community Training offers microsoft managed disaster recovery. To use managed disaster recovery, you'll need to [enable disaster recovery]() during Community Training instance creation in Azure. Once you enable disaster recovery, Microsoft maintains the backup of storage and database in the paired region. Recovery Point Objective (RPO) is expected to be twelve hours; Recovery Time Objective (RTO), 48 hours.
80+
- For the **data plane**, Community Training offers microsoft managed disaster recovery. To use managed disaster recovery, you need to [enable disaster recovery]() during Community Training instance creation in Azure. Once you enable disaster recovery, Microsoft maintains the backup of storage and database in the paired region. Recovery Point Objective (RPO) is expected to be 12 hours; Recovery Time Objective (RTO), 48 hours.
8181

8282

8383
>[!NOTE]
@@ -86,7 +86,7 @@ The entire disaster recovery procedure for Community Training is manually manage
8686

8787
#### Outage detection, notification, and management
8888

89-
When a Community Training health check detects an outage of any service, and in any region, Microsoft will request your consent for failover to the paired region. Microsoft will let you know which features will be available during the disaster recovery procedure. Once Microsoft receives your consent, the Community Training team can then start the disaster recovery procedure.
89+
When a Community Training health check detects an outage of any service, and in any region, Microsoft requests your consent for failover to the paired region. Microsoft informs you which features are available during the disaster recovery procedure. Once Microsoft receives your consent, the Community Training team can then start the disaster recovery procedure.
9090

9191
>[!IMPORTANT]
9292
> Learners will not be able to consume audio/video features until the primary region is operational. It's recommended that you avoid media upload operations until the primary site is operational.

0 commit comments

Comments
 (0)