|
| 1 | +--- |
| 2 | +title: Reliability in Azure Lab Services |
| 3 | +description: Learn about reliability in Azure Lab Services |
| 4 | +ms.topic: overview |
| 5 | +ms.custom: 'subject-resiliency, references_regions' |
| 6 | +ms.date: 08/18/2022 |
| 7 | +--- |
| 8 | + |
| 9 | +# What is reliability in Azure Lab Services? |
| 10 | + |
| 11 | +This article describes reliability support in Azure Lab Services, and covers regional resiliency with availability zones. For a more detailed overview of reliability in Azure, see [Azure resiliency](/azure/availability-zones/overview.md). |
| 12 | + |
| 13 | +## Availability zone support |
| 14 | + |
| 15 | +Azure availability zones are at least three physically separate groups of datacenters within each Azure region. Datacenters within each zone are equipped with independent power, cooling, and networking infrastructure. In the case of a local zone failure, availability zones allow the services to fail over to the other availability zones to provide continuity in service with minimal interruption. Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Tolerance to failures is achieved with redundancy and logical isolation of Azure services. For more detailed information on availability zones in Azure, see [Regions and availability zones](/azure/availability-zones/az-overview.md). |
| 16 | + |
| 17 | +Azure availability zones-enabled services are designed to provide the right level of resiliency and flexibility. They can be configured in two ways. They can be either zone redundant, with automatic replication across zones, or zonal, with instances pinned to a specific zone. You can also combine these approaches. For more information on zonal vs. zone-redundant architecture, see [Build solutions with availability zones](/azure/architecture/high-availability/building-solutions-for-high-availability). |
| 18 | + |
| 19 | +Azure Lab Services provide availability zone redundancy automatically in all regions listed in this article. While the service infrastructure is zone redundant, customer labs and VMs are not zone redundant. |
| 20 | + |
| 21 | +Currently, the service is not zonal. That is, you can’t configure a lab or the VMs in the lab to align to a specific zone. A lab and VMs may be distributed across zones in a region. |
| 22 | + |
| 23 | +### SLA improvements |
| 24 | + |
| 25 | +There are no increased SLAs available for availability in Azure Lab Services. For the monthly uptime SLAs for Azure Lab Services, see [SLA for Azure Lab Services](https://azure.microsoft.com/support/legal/sla/lab-services/v1_0/). |
| 26 | + |
| 27 | +The Azure Lab Services infrastructure uses Cosmos DB storage. The Cosmos DB storage region is the same as the region where the lab plan is located. All the regional Cosmos DB accounts are single region. In the zone-redundant regions listed in this article, the Cosmos DB accounts are single region with Availability Zones. In the other regions, the accounts are single region without Availability Zones. For high availability capabilities for these account types, see [SLAs for Cosmos DB](/azure/cosmos-db/high-availability#slas). |
| 28 | + |
| 29 | +### Zone down experience |
| 30 | + |
| 31 | +#### Azure Lab Services infrastructure |
| 32 | + |
| 33 | +Azure Lab Services infrastructure is zone-redundant in the following regions: |
| 34 | + |
| 35 | +- Australia East |
| 36 | +- Canada Central |
| 37 | +- France Central |
| 38 | +- Korea Central |
| 39 | +- East Asia |
| 40 | + |
| 41 | +Resources apart from the Lab resources and virtual machines are zone redundant in these regions. |
| 42 | + |
| 43 | +In the event of a zone outage in these regions, you can still perform the following tasks: |
| 44 | + |
| 45 | +- Access the Azure Lab Services website |
| 46 | +- Create/manage lab plans |
| 47 | +- Create Users |
| 48 | +- Configure lab schedules |
| 49 | +- Create/manage labs and VMs in regions unaffected by the zone outage. |
| 50 | + |
| 51 | +Data loss may occur only with an unrecoverable disaster in the Cosmos DB region. For more information, see [Region Outages](/azure/cosmos-db/high-availability#region-outages). |
| 52 | + |
| 53 | +For regions not listed, access to the Azure Lab Services infrastructure is not guaranteed when there is a zone outage in the region containing the lab plan. You will only be able to perform the following tasks: |
| 54 | + |
| 55 | +- Access the Azure Lab Services website |
| 56 | +- Create/manage lab plans, labs, and VMs in regions unaffected by the zone outage |
| 57 | + |
| 58 | +> [!NOTE] |
| 59 | +> Existing labs and VMs in regions unaffected by the zone outage aren't affected by a loss of infrastructure in the lab plan region. Existing labs and VMs in unaffected regions can still run and operate as normal. |
| 60 | +
|
| 61 | +#### Labs and VMs |
| 62 | + |
| 63 | +Azure Lab Services is not currently zone aligned. So, VMs in a region may be distributed across zones in the region. Therefore, when a zone in a region experiences an outage, there are no guarantees that a lab or any VMs in the associated region will be available. |
| 64 | + |
| 65 | +As a result, the following operations are not guaranteed in the event of a zone outage: |
| 66 | + |
| 67 | +- Manage or access labs/VMs |
| 68 | +- Start/stop/reset VMs |
| 69 | +- Create/publish/delete labs |
| 70 | +- Scale up/down labs |
| 71 | +- Connect to VMs |
| 72 | + |
| 73 | +If there's a zone outage in the region, there's no expectation that you can use any labs or VMs in the region. |
| 74 | +Labs and VMs in other regions will be unaffected by the outage. |
| 75 | + |
| 76 | +#### Zone outage preparation and recovery |
| 77 | + |
| 78 | +Lab and VM services will be restored as soon as the zone availability is restored (the outage is resolved). |
| 79 | + |
| 80 | +If infrastructure is impacted, it will be restored when the zone availability is resolved. |
| 81 | + |
| 82 | +### Region down experience |
| 83 | + |
| 84 | +#### Azure Lab Services infrastructure |
| 85 | + |
| 86 | +In a regional outage, in most scenarios you will only be able to perform the following tasks related to Azure Lab Services infrastructure: |
| 87 | + |
| 88 | +- Access the Azure Lab Services website |
| 89 | +- Create/manage lab plans, labs, and VMs in regions unaffected by the zone outage |
| 90 | + |
| 91 | +Typically, labs are in the same region as the lab plan. However, if the outage is in the lab plan region and an existing lab is in an unaffected region, you can still perform the following tasks for the existing lab in the unaffected region: |
| 92 | + |
| 93 | +- Create Users |
| 94 | +- Configure lab schedules |
| 95 | + |
| 96 | +#### Labs and VMs |
| 97 | + |
| 98 | +In a regional outage, labs and VMs in the region are unavailable, so you will not be able to use or manage them. |
| 99 | + |
| 100 | +Existing labs and VMs in regions unaffected by the outage aren't affected by a loss of infrastructure in the lab plan region. Existing labs and VMs in unaffected regions can still run and operate as normal. |
| 101 | + |
| 102 | +#### Regional outage preparation and recovery |
| 103 | + |
| 104 | +Lab and VM services will be restored as soon as the regional outage is restored (the outage is resolved). |
| 105 | + |
| 106 | +If infrastructure is impacted, it will be restored when the regional outage is resolved. |
| 107 | + |
| 108 | +### Fault tolerance |
| 109 | + |
| 110 | +If you want to preserve maximum access to Azure Lab Services infrastructure during a zone outage, create the lab plan in one of the zone-redundant regions listed. |
| 111 | + |
| 112 | +- Australia East |
| 113 | +- Canada Central |
| 114 | +- France Central |
| 115 | +- Korea Central |
| 116 | +- East Asia |
| 117 | + |
| 118 | +## Disaster recovery |
| 119 | + |
| 120 | +Azure Lab Services does not provide regional failover support. If you want to preserve maximum access to the Azure Lab Services infrastructure during a zone outage, create the lab plan in one of the [zone-redundant regions](#fault-tolerance). |
| 121 | + |
| 122 | +### Outage detection, notification, and management |
| 123 | + |
| 124 | +Azure Lab Services does not provide any service-specific signals about an outage, but is dependent on Azure communications that inform customers about outages. For more information on service health, see [Resource health overview](/azure/service-health/resource-health-overview). |
| 125 | + |
| 126 | +## Next steps |
| 127 | + |
| 128 | +> [!div class="nextstepaction"] |
| 129 | +> [Resiliency in Azure](/azure/availability-zones/overview.md) |
0 commit comments