As explained here: Cross-region disaster recovery isn't currently supported in Azure Health Data Services.
https://learn.microsoft.com/en-us/azure/healthcare-apis/business-continuity-disaster-recovery
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We are planning to use Azure Health Data Service in the East US region, however, there is no built-in solution for Disaster Recovery in the West US (Microsoft recommended pair regions) it seems. What is the workaround for this? Does Microsoft already have a plan to support a DR solution for this service in the West US region?
Also, what are the pros and cons of decisions we make or approaches we take while planning the DR environment?
As explained here: Cross-region disaster recovery isn't currently supported in Azure Health Data Services.
https://learn.microsoft.com/en-us/azure/healthcare-apis/business-continuity-disaster-recovery
@Suwarna S Kale Thanks for reaching out. As Vahid mentioned we don't offer cross-region disaster recovery as a feature for Azure Health Data services offering. A manual option would be to use the $export and $import operations to backup and restore your data in a newly provisioned service. Note: this option would not restore history of the resource, but it would restore the most current version of the resource. behind the scenes we are using Azure SQL, and we store back-ups for last 7 days. Both cross-region disaster recovery and PITR support are features that are on our roadmap, but we don't have ETA to share.
Reference: https://learn.microsoft.com/en-us/azure/healthcare-apis/business-continuity-disaster-recovery
Please let me know if you have any further queries.
Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.