Azure Synapse Dedicated SQL Pool - DR Query

Question

Hi,

We have Azure Synapse that uses a Dedicated SQL Pool and does not use a Synapse workspace.

Is there any documentation on how to implement and test Disaster Recovery for Azure Synapse that uses a Dedicated SQL Pool.

Kind Regards

Ramdas

Answer 1

@Ramdas Panicher - Thanks for the question and using MS Q&A platform.

For the Dedicated Pools, we create a DW snapshot that you can use to recover or copy your data warehouse to a previous state. These snapshots help you recover or copy your data warehouse to a previous state. If you want to customize the snapshot window, you can create user-defined restore points by taking a user-created snapshot.

 

Per SLA requirements, Dedicated SQL Pools have an automatic system snapshot or restore point that following some rules:

• A geo-backup is created once per day to a paired data center (we have a backup/Snapshot job that in fact runs several times a day) to guarantee the RPO of 24 hours.
• A geo-restore is always a data movement operation and the RTO will depend on the data size.
• Only the latest geo-backup is retained. You can restore the geo-backup to a server in any other region where dedicated SQL pool is supported.
• A geo-backup ensures you can restore data warehouse in case you cannot access the restore points in your primary region.

 

For more details, I suggest you check out the following documentation Backup and restore - snapshots, geo-redundant and Creating a custom disaster recovery plan for your Synapse workspace Part 1.

Hope this helps. Do let us know if you any further queries.

---

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

Azure Synapse Analytics, including dedicated SQL Pools, inherently provide data protection features such as automatic backups, geo-redundant backups, and Point-in-Time restore, which can be used as part of a DR strategy. However, the specifics of testing these features, or implementing additional DR measures, such as active geo-replication or failover groups, may depend on the specifics of your application and data usage.

I would recommend considering the following aspects when designing a DR strategy:

• Understanding the Recovery Point Objective (RPO) and Recovery Time Objective (RTO) for your application.
• Implementing regular backups and understanding how to restore from them.
• Considering geo-redundant backups if your business continuity plan requires it.
• Implementing measures to ensure data consistency in the event of a failover.
• Regular testing of your DR strategy.