Merge pull request #31495 from MashaMSFT/202408_sqldbckup

Adding info about automated backups

Author: v-shils

azure-sql/database/automated-backups-overview.md

@@ -5,7 +5,7 @@ description: Learn how Azure SQL Database automatically backs up all databases a
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: mathoma, danil, dinethi
-ms.date: 07/24/2024
+ms.date: 09/03/2024
 ms.service: azure-sql-database
 ms.subservice: backup-restore
 ms.topic: conceptual
@@ -103,6 +103,18 @@ You can use automatically created backups in the following scenarios:
    > Geo-restore is available only for databases that are configured with geo-redundant backup storage. If you're not currently using geo-replicated backups for a database, you can change this by [configuring backup storage redundancy](automated-backups-change-settings.md#configure-backup-storage-redundancy).
 - [Restore a database from a specific long-term backup](long-term-retention-overview.md) of a single or pooled database, if the database has been configured with an LTR policy. LTR allows you to [restore an older version of the database](long-term-backup-retention-configure.md) by using the Azure portal, the Azure CLI, or Azure PowerShell to satisfy a compliance request or to run an older version of the application. For more information, see [Long-term retention](long-term-retention-overview.md).
 
+## Automatic backups on secondary replicas
+
+Automatic backups are now taken from a secondary replica in the [Business Critical](service-tiers-sql-database-vcore.md#business-critical) service tier. Since data is replicated between SQL Server processes on each node, the backup service takes the backup from the non-readable secondary replicas. This design ensures the primary replica remains dedicated to your main workload, and the readable secondary replica is dedicated to read-only workloads. Automatic backups in the Business Critical service tier are taken from a secondary replica most of the time. If an automatic backup fails on a secondary replica, then the backup service takes the backup from the primary replica. 
+
+Automatic backups on secondary replicas: 
+
+- Are enabled by default. 
+- Are included at no additional cost beyond the price of the service tier.
+- Bring improved performance and predictability to the Business Critical service tier.
+
+> [!NOTE]
+> - Create a Microsoft support ticket to disable the feature for your instance. 
 
 ## <a id="restore-capabilities"></a> Restore capabilities and features
 
@@ -139,6 +151,8 @@ To perform a restore, see [Restore a database from backups](recovery-using-backu
 | **Restore a database from a point in time** | [SQL Database](recovery-using-backups.md#point-in-time-restore)<br>[SQL Managed Instance](../managed-instance/point-in-time-restore.md) | [SQL Database](/cli/azure/sql/db#az-sql-db-restore) <br/> [SQL Managed Instance](/cli/azure/sql/midb#az-sql-midb-restore) | [SQL Database](/powershell/module/az.sql/restore-azsqldatabase) <br/> [SQL Managed Instance](/powershell/module/az.sql/restore-azsqlinstancedatabase) |
 | **Restore a deleted database** | [SQL Database](recovery-using-backups.md)<br>[SQL Managed Instance](../managed-instance/point-in-time-restore.md#restore-a-deleted-database) | [SQL Database](long-term-backup-retention-configure.md#restore-from-ltr-backups) <br/> [SQL Managed Instance](../managed-instance/long-term-backup-retention-configure.md#restore-from-ltr-backups) | [SQL Database](/powershell/module/az.sql/get-azsqldeleteddatabasebackup) <br/> [SQL Managed Instance](/powershell/module/az.sql/get-azsqldeletedinstancedatabasebackup)|
 
+
+
 ## Export a database
 
 Automatic backups taken by the Azure service are not available to download or access directly. They can only be used for restore operations through Azure.
@@ -147,6 +161,7 @@ There are alternatives to export an Azure SQL Database. When you need to export
 
 You can also [Import or export an Azure SQL Database using private link](database-import-export-private-link.md) or [Import or export an Azure SQL Database without allowing Azure services to access the server](database-import-export-azure-services-off.md).
 
+
 ## Backup scheduling
 
 The first full backup is scheduled immediately after a new database is created or restored. This backup usually finishes within 30 minutes, but it can take longer when the database is large. For example, the initial backup can take longer on a restored database or a database copy, which would typically be larger than a new database. 

azure-sql/database/doc-changes-updates-release-notes-whats-new.md

@@ -72,6 +72,7 @@ The following table lists features of Azure SQL Database that have been made gen
 | [CURRENT_DATE Transact-SQL](/sql/t-sql/functions/current-date-transact-sql) | August 2024 |  A Transact-SQL (T-SQL) function that returns the current database system date as a date value, without the database time and time zone offset. |
 | [Maintenance window support for named replicas](https://aka.ms/MWsupportforNR)|August 2024|[Maintenance window](maintenance-window.md) support for named replicas is now generally available.|
 | [Maintenance window](maintenance-window.md) support for Hyperscale | August 2024| [Maintenance window](maintenance-window.md) support for Hyperscale databases is now generally available. |
+| [Automatic backups on secondary replicas](automated-backups-overview.md#automatic-backups-on-secondary-replicas) | August 2024 | Mitigate the performance impact on your workload by taking automated backups from the non-readable secondary replica in the Business Critical service tier. |
 | [Database compatibility level 160 is now default](/sql/t-sql/statements/alter-database-transact-sql-compatibility-level?view=azuresqldb-current&preserve-view=true) | June 2024 | Database compatibility level 160 is now the default for new databases created in Azure SQL Database. For more information on this announcement, see [General availability: Database compatibility level 160 in Azure SQL Database](https://techcommunity.microsoft.com/t5/azure-sql-blog/general-availability-database-compatibility-level-160-in-azure/ba-p/4172039). |
 | [Hyperscale named replica zone redundant support](service-tier-hyperscale-replicas.md) | June 2024 | [Zone redundancy support for Hyperscale named replicas](https://aka.ms/ZRSupportForNRPreview) is now generally available. |
 | [License-free standby replica](standby-replica-how-to-configure.md) | May 2024 | Save on licensing costs by configuring your secondary database replica for disaster recovery standby. | 
@@ -91,12 +92,14 @@ Learn about significant changes to the Azure SQL Database documentation. For pre
 
 | Changes | Details |
 | --- | --- |
+|**Automatic backups on secondary replica GA** | Mitigate the performance impact on your workload by taking automated backups from a non-readable secondary replica in the Business Critical service tier. This feature is generally available. Review [Automated backups on secondary replicas](automated-backups-overview.md#automatic-backups-on-secondary-replicas) to learn more.  |
 | **CURRENT_DATE Transact-SQL GA** | The `CURRENT_DATE` Transact-SQL (T-SQL) function returns the current database system date as a date value, without the database time and time zone offset. This function is now generally available. For more information, see [CURRENT_DATE (Transact-SQL)](/sql/t-sql/functions/current-date-transact-sql). |
 | **Maintenance window support for named replicas GA**|[Maintenance window](maintenance-window.md) support for named replicas is now generally available. For more information, read [Maintenance window support for named replicas](https://aka.ms/MWsupportforNR).|
 | **Maintenance window support for Hyperscale GA** | [Maintenance window](maintenance-window.md) support for Hyperscale databases is now generally available. |
 | **Local development experience for Azure SQL Database using Dev Container Templates** | We've provided details and quickstarts to get started with the new [local dev experience for Azure SQL Database](local-dev-experience-dev-containers.md). Dev Container Templates replace the previous local emulator experience. To get started, see [Quickstart: Set up a development environment with Dev Container Templates for Azure SQL Database](local-dev-experience-dev-containers-quickstart.md). |
 | **Resource limits changes** | There are [new default vCore limits](resource-limits-logical-server.md#subscription-vcore-limits-per-region) per region per subscription. Additionally, requests for increasing default DTU limits are now done with [vCores](quota-increase-request.md#vcores-per-subscription).
 
+
 ### July 2024
 
 | Changes | Details |