You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/operational-excellence/relocation-static-web-apps.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ Review the following prerequisites before you prepare for the relocation.
53
53
54
54
## Downtime
55
55
56
-
The relocation of an Azure Static Web site introduces downtime to your application. The downtime is affected by which high availability pattern you have implemented for your Azure Static Web site. General patterns are
56
+
The relocation of an Azure Static Web site introduces downtime to your application. The downtime is affected by which high availability pattern you have implemented for your Azure Static Web site. General patterns are:
57
57
- Cold Standby - the workload data is backed up regularly based on the requirements of the workload. In case of a disaster, the workload is redeployed in a new Azure region and the data is restored.
58
58
- Warm Standby - the workload is deployed in the BCDR region and the data is replicated asynchronously or synchronously. In the event of a disaster, the deployment in the DR region is scaled up and out.
59
59
-[Multi-region](https://learn.microsoft.com/en-us/azure/architecture/web-apps/app-service/architectures/multi-region) - the workload is deployed in both regions and the data is replicated synchronously. Both regions have a writable copy of the data. The implementation can be Active/Passive or Active/Active.
0 commit comments