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/healthcare-apis/business-continuity-disaster-recovery.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,10 +20,10 @@ Business continuity and disaster recovery (BCDR) in Azure Health Data Services h
20
20
21
21
Azure Health Data Services is available in multiple regions. When you create an Azure Health Data Services resource, you specify its region. From then on, your resource and all its operations stay associated with that Azure region. Cross-region disaster recovery isn't currently supported in Azure Health Data Services.
22
22
23
-
In most cases, Azure Health Data Services handles disruptive events that may occur in the cloud environment and is able to keep your applications and business processes running. However, Azure Health Data Services can't handle these situations:
23
+
In most cases, Azure Health Data Services handles disruptive events that may occur in the cloud environment and is able to keep your applications and business processes running. However, Azure Health Data Services can't handle situations like:
24
24
25
-
- You accidentally delete or update your service or data, and you don't have a backup.
26
-
- A natural disaster, such as an earthquake, causes a power outage or disables the region or data center where your service and data are located.
25
+
- You have deleted your service
26
+
- A natural disaster, such as an earthquake or power outage disables the region or data center where your service and data are located.
27
27
- Any other catastrophic event that requires cross-region failover.
28
28
29
29
## Database backups for the FHIR service
@@ -33,7 +33,7 @@ Database backups are an essential part of any business continuity strategy becau
33
33
The support team handles the backups and restores of the FHIR database. To restore the data, customers need to submit a support ticket with these details:
34
34
35
35
- Name of the service
36
-
- Restore point date and time within the last seven days. If the date and time is unavailable, ask us to restore from the earliest available point.
36
+
- Restore point date and time within the last seven days. If the requested restore point is not available, we will use the nearest one available, unless you tell us otherwise. Please include this information in your support request.
37
37
38
38
More information: [Create an Azure support request](../azure-portal/supportability/how-to-create-azure-support-request.md)
0 commit comments