From 158b5d275ed56836fb6f40667741c23a57136fd2 Mon Sep 17 00:00:00 2001 From: Muhammad Zaeem Khaliq <57555591+ZaeemKhaliq@users.noreply.github.com> Date: Sun, 5 Jul 2026 15:23:45 +0500 Subject: [PATCH] Update backup storage redundancy information Clarified backup storage redundancy behavior for geo-secondary databases in General Purpose and Business Critical service tiers. --- azure-sql/database/active-geo-replication-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/azure-sql/database/active-geo-replication-overview.md b/azure-sql/database/active-geo-replication-overview.md index 95c5e844dcb..31be7e1433c 100644 --- a/azure-sql/database/active-geo-replication-overview.md +++ b/azure-sql/database/active-geo-replication-overview.md @@ -116,7 +116,7 @@ If you decide to create the geo-secondary with a different configuration, you sh > - If the geo-secondary is at a lower compute size than the primary. Look for the `HADR_THROTTLE_LOG_RATE_MISMATCHED_SLO` wait type in [sys.dm_exec_requests](/sql/relational-databases/system-dynamic-management-views/sys-dm-exec-requests-transact-sql) and [sys.dm_os_wait_stats](/sql/relational-databases/system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql) database views. > - Throttling can also occur for reasons unrelated to compute size, for example in heavy workloads for bulk insert, `SELECT INTO`, and index builds. For more information on wait types for different kinds of log I/O throttling, see [Transaction log rate governance](resource-limits-logical-server.md#transaction-log-rate-governance). -By default, backup storage redundancy of the geo-secondary is same as for the primary database. You can choose to configure a geo-secondary with a different backup storage redundancy. Backups are always taken on the primary database. If the secondary is configured with a different backup storage redundancy, then after a geo-failover, when the geo-secondary is promoted to the primary, new backups will be stored and billed according to the type of storage (RA-GRS, ZRS, LRS) selected on the new primary (previous secondary). +By default, backup storage redundancy of the geo-secondary is same as for the primary database. You can choose to configure a geo-secondary with a different backup storage redundancy. Backups are always taken on the primary database in **General Purpose** service tier (In **Business Critical** tier, they are now taken on [secondary replicas](https://learn.microsoft.com/en-us/azure/azure-sql/database/automated-backups-overview?view=azuresql#automatic-backups-on-secondary-replicas)). If the secondary is configured with a different backup storage redundancy, then after a geo-failover, when the geo-secondary is promoted to the primary, new backups will be stored and billed according to the type of storage (RA-GRS, ZRS, LRS) selected on the new primary (previous secondary). ## Save on costs with the standby replica