Skip to content

Commit c697c56

Browse files
Merge pull request #255427 from outinyman/patch-9
Update business-continuity-disaster-recovery.md
2 parents df1eeb9 + dc5a30b commit c697c56

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/healthcare-apis/business-continuity-disaster-recovery.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,10 +20,10 @@ Business continuity and disaster recovery (BCDR) in Azure Health Data Services h
2020

2121
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.
2222

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:
2424

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.
2727
- Any other catastrophic event that requires cross-region failover.
2828

2929
## Database backups for the FHIR service
@@ -33,7 +33,7 @@ Database backups are an essential part of any business continuity strategy becau
3333
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:
3434

3535
- 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.
3737

3838
More information: [Create an Azure support request](../azure-portal/supportability/how-to-create-azure-support-request.md)
3939

0 commit comments

Comments
 (0)