You're reading from Limitless Analytics with Azure Synapse

Product type Book

Published in Jun 2021

Publisher Packt

ISBN-13 9781800205659

Pages 392 pages

Edition 1st Edition

Languages

Python

Concepts

Data Science

Author (1):

Prashant Kumar Mishra

Table of Contents (20) Chapters

Preface

1. Section 1: The Basics and Key Concepts

2. Chapter 1: Introduction to Azure Synapse

3. Chapter 2: Considerations for Your Compute Environment

4. Section 2: Data Ingestion and Orchestration

5. Chapter 3: Bringing Your Data to Azure Synapse

6. Chapter 4: Using Synapse Pipelines to Orchestrate Your Data

7. Chapter 5: Using Synapse Link with Azure Cosmos DB

8. Section 3: Azure Synapse for Data Scientists and Business Analysts

9. Chapter 6: Working with T-SQL in Azure Synapse

10. Chapter 7: Working with R, Python, Scala, .NET, and Spark SQL in Azure Synapse

11. Chapter 8: Integrating a Power BI Workspace with Azure Synapse

12. Chapter 9: Perform Real-Time Analytics on Streaming Data

13. Chapter 10: Generate Powerful Insights on Azure Synapse Using Azure ML

14. Section 4: Best Practices

15. Chapter 11: Performing Backup and Restore in Azure Synapse Analytics

16. Chapter 12: Securing Data on Azure Synapse

17. Chapter 13: Managing and Monitoring Synapse Workloads

18. Chapter 14: Coding Best Practices

19. Other Books You May Enjoy

Geo-backups and disaster recovery

Synapse performs a geo-backup once per day to a paired data center automatically, and that's why the option to enable a geo-backup policy for your dedicated SQL pool is disabled. The Recovery Point Objective (RPO) for a geo-backup is 24 hours. This geo-backup can be used to restore your SQL pool if the restore points in the primary region are not available.

In this section, we are going to create geo-redundant restore points using the Azure portal and PowerShell script as well. This PowerShell script can be used for any dedicated SQL pool just by providing correct values for the parameters in the script.

As shown in the following screenshot, we cannot create a geo-backup policy for a dedicated SQL pool because the SQL pool is automatically backed up to the region pair. You can read about region pairs at the following link—https://docs.microsoft.com/en-us/azure/best-practices-availability-paired-regions: