Published on

November 16, 2020

Understanding Azure SQL Database Business Continuity and Disaster Recovery

Azure SQL Database is a cloud-based service model that provides a platform to back up data and ensure business continuity even after a disaster. In this article, we will explore the concepts of business continuity and disaster recovery in Azure SQL Database.

Definitions of RPO and RTO

Recovery Point Objective (RPO) and Recovery Time Objective (RTO) are two important metrics in business continuity and disaster recovery planning. RPO defines the maximum acceptable amount of data loss measured in time, while RTO defines the maximum acceptable downtime measured in time. Understanding these metrics is crucial in designing an effective backup and recovery strategy.

Azure SQL Database Automatic Database Backup

Azure SQL Database offers automatic database backups as part of its high-availability and fault-tolerance solution. By default, Azure stores seven days of database backups using the RA-GRS technique, which ensures geo-redundancy. The retention period can be customized for up to 35 days. Short-term backups allow for point-in-time restore or geo-restore based on backup availability.

Geo-Restore with Examples

Azure SQL Database provides a feature called Geo-restore, which is the most basic disaster recovery solution available. It offers a recovery point objective of up to 1 hour and a recovery time objective of up to 12 hours. However, Geo-restore may not be suitable for critical applications that require shorter recovery times and higher availability.

For critical applications and large databases, using active geo-replication is a viable option. Active geo-replication setup uses auto-failover groups and provides lower RPO and RTO with no limitation on the target region.

Azure SQL Database Backup

Database backups are a vital part of any organization’s business continuity and disaster recovery strategy. Azure SQL Database offers two types of automatic backups based on performance models: short-term backups and long-term backups.

Short-term backups are stored for seven days using the RA-GRS technique, with the option to customize the retention period for up to 35 days. Long-term backups allow for backup retention for up to 10 years, which is useful for meeting security compliance and regulatory requirements.

Performing Geo-Restore

To perform a geo-restore in Azure SQL Database, you can use PowerShell or the Azure portal. Geo-restore is a zero-cost feature that allows you to restore a database from a geo-redundant backup. It is important to note that geo-restore may take longer compared to other database cloning operations.

Measuring Geo-Restore Progress

While detailed restore progress is not available on the Azure portal, you can query the sys.dm_operation_status DMV to measure the progress of the restore. This allows you to track the percent complete and last modify time of the restore operation.

Performing Failover Tasks

After a failover or recovery, there are several tasks that need to be performed to ensure the applications are up and running. These tasks include changing the connection string or settings to point to the new server, adding IP addresses to firewall rules, creating logins and applying permissions, enabling auditing and alerts, and more.

Conclusion

Business continuity and disaster recovery planning are crucial for organizations to ensure the availability and protection of their data. Azure SQL Database offers various features and options for backup, restore, and failover to meet different business requirements. Understanding the concepts and implementing the right strategies can help organizations minimize downtime and data loss in the event of a disaster.

Click to rate this post!
[Total: 0 Average: 0]

Let's work together

Send us a message or book free introductory meeting with us using button below.