Merge pull request #29377 from WilliamDAssafMSFT/20231220-ltr-table-dates

20231220 ltr table dates

Author: v-dirichards

azure-sql/database/long-term-retention-overview.md

@@ -5,14 +5,14 @@ description: Learn how Azure SQL Database & Azure SQL Managed Instance support s
 author: grrlgeek
 ms.author: jeschult
 ms.reviewer: wiassaf, mathoma, randolphwest
-ms.date: 12/13/2023
+ms.date: 12/20/2023
 ms.service: sql-db-mi
 ms.subservice: backup-restore
 ms.topic: conceptual
-monikerRange: "=azuresql || =azuresql-db || =azuresql-mi"
+monikerRange: "=azuresql||=azuresql-db||=azuresql-mi"
 ---
 # Long-term retention - Azure SQL Database and Azure SQL Managed Instance
-[!INCLUDE[appliesto-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
+[!INCLUDE [appliesto-sqlmi](../includes/appliesto-sqldb-sqlmi.md)]
 
 This article provides a conceptual overview of long-term retention of backups for Azure SQL Database and Azure SQL Managed Instance. Long-term retention can be configured for up to 10 years on backups for Azure SQL Database (including in the Hyperscale service tier), and Azure SQL Managed Instance.
 
@@ -26,7 +26,7 @@ By using the LTR feature, you can store specified full SQL Database and SQL Mana
 
 > [!NOTE]  
 > - It's not currently possible to configure backups of Azure SQL Database and Azure SQL Managed Instance as [immutable](/azure/storage/blobs/immutable-storage-overview). 
-> - In Azure SQL Managed Instance, use SQL Agent jobs to schedule [copy-only database backups](/sql/relational-databases/backup-restore/copy-only-backups-sql-server) as an alternative to LTR beyond 35 days.
+> - In Azure SQL Managed Instance, use SQL Agent jobs to schedule [copy-only database backups](/sql/relational-databases/backup-restore/copy-only-backups-sql-server?view=azuresqldb-mi-current&preserve-view=true) as an alternative to LTR beyond 35 days.
 
 To enable LTR, you can define a policy using a combination of four parameters: weekly backup retention (W), monthly backup retention (M), yearly backup retention (Y), and week of the year (WeekOfYear). If you specify W, one backup every week is copied to long-term storage. If you specify M, the first backup of each month is copied to the long-term storage. If you specify Y, one backup during the week specified by WeekOfYear is copied to the long-term storage. If the specified WeekOfYear is in the past when the policy is configured, the first LTR backup is created the following year. Each backup is kept in long-term storage according to the policy parameters that are configured when the LTR backup is created.
 
@@ -54,12 +54,41 @@ The following table illustrates the cadence and expiration of the long-term back
 
 `W=12 weeks` (84 days), `M=12 months` (365 days), `Y=10 years` (3650 days), `WeekOfYear=20` (the week after May 13)
 
-   :::image type="content" source="media/long-term-retention-overview/ltr-example.png" alt-text="Diagram showing an example of Long-term retention.":::
+The following dates are in ISO 8601 (`YYYY-MM-DD`).
+
+|**PITR backup to LTR**|**Expiration W**|**Expiration M**|**Expiration Y**|
+|:--|:--|:--|:--|
+|**2018-03-07** | | 2019-07-03     | |
+|2018-03-14     | 2018-06-06     | | |
+|2018-03-21     | 2018-06-13     | | |
+|2018-03-28     | 2018-06-20     | | |
+|**2018-04-04** | | 2019-04-25     | |
+|2018-04-11     | 2018-07-04     | | |
+|2018-04-18     | 2018-07-11     | | |
+|2018-04-25     | 2018-07-18     | | |
+|**2018-05-02** | | 2019-05-23     | |
+|2018-05-09     | 2018-08-01     | | |
+|**2018-05-16** | | | 2028-05-13     |
+|2018-05-23     | 2018-08-15     | | |
+|2018-05-30     | 2018-08-22     | | |
+|**2018-06-06** | | 2019-06-20     | |
+|2018-06-13     | 2018-09-05     | | |
+|2018-06-20     | 2018-09-12     | | |
+|2018-06-27     | 2018-09-19     | | |
+|**2018-07-04** | | 2019-07-25     | |
+|2018-07-11     | 2018-10-03     | | |
+|2018-07-18     | 2018-10-10     | | |
+|2018-07-25     | 2018-10-17     | | |
+|**2018-08-01** | | 2019-08-22     | |
+|2018-08-08     | 2018-10-31     | | |
+|2018-08-15     | 2018-11-07     | | |
+|2018-08-22     | 2018-11-14     | | |
+|2018-08-29     | 2018-11-21     | | |
 
 If you modify the above policy and set `W=0` (no weekly backups), the service only retains the monthly and yearly backups. No weekly backups are stored under the LTR policy. The storage amount needed to keep these backups reduces accordingly.
 
 > [!IMPORTANT]  
-> The timing of individual LTR backups is controlled by Azure SQL Database. You cannot manually create an LTR backup or control the timing of the backup creation. After configuring an LTR policy, it  may take up to 7 days before the first LTR backup will show up on the list of available backups.  
+> The timing of individual LTR backups is controlled by Azure SQL Database. You cannot manually create an LTR backup or control the timing of the backup creation. After configuring an LTR policy, it might take up to 7 days before the first LTR backup will show up on the list of available backups.  
 >  
 > If you delete a logical server or a managed instance, all databases on that server or managed instance are also deleted and can't be recovered. You can't restore a deleted server or managed instance. However, if you had configured LTR for a database or managed instance, LTR backups are not deleted, and they can be used to restore databases on a different server or managed instance in the same subscription, to a point in time when an LTR backup was taken.
 >  
@@ -76,9 +105,9 @@ If you're using active geo-replication or failover groups as your business conti
 
 You can configure long-term backup retention using the Azure portal and PowerShell for Azure SQL Database and Azure SQL Managed Instance. To restore a database from the LTR storage, you can select a specific backup based on its timestamp. The database can be restored to any existing server or managed instance under the same subscription as the original database.
 
-To learn how to configure long-term retention or restore a database from backup for SQL Database using the Azure portal or PowerShell, see [Manage Azure SQL Database long-term backup retention](long-term-backup-retention-configure.md).
+To learn how to configure long-term retention or restore a database from backup for SQL Database using the Azure portal or PowerShell, see [Manage Azure SQL Database long-term backup retention](long-term-backup-retention-configure.md?view=azuresql-db&preserve-view=true).
 
-To learn how to configure long-term retention or restore a database from backup for SQL Managed Instance using the Azure portal or PowerShell, see [Manage Azure SQL Managed Instance long-term backup retention](../managed-instance/long-term-backup-retention-configure.md).
+To learn how to configure long-term retention or restore a database from backup for SQL Managed Instance using the Azure portal or PowerShell, see [Manage Azure SQL Managed Instance long-term backup retention](../managed-instance/long-term-backup-retention-configure.md?view=azuresql-mi&preserve-view=true).
 
 When a restore request is initiated in the final 7 days of the LTR retention period, Azure will automatically extend the expiration date of all backups +7 days, to prevent an LTR backup from expiring during the restore.
 
@@ -96,5 +125,5 @@ Because database backups protect data from accidental corruption or deletion, th
 
 For a tutorial on configuring and managing LTR backups, visit:
 
-- [Manage Azure SQL Database long-term backup retention](long-term-backup-retention-configure.md)
-- [Manage Azure SQL Managed Instance long-term backup retention](../managed-instance/long-term-backup-retention-configure.md)
+- [Manage Azure SQL Database long-term backup retention](long-term-backup-retention-configure.md?view=azuresql-db&preserve-view=true)
+- [Manage Azure SQL Managed Instance long-term backup retention](../managed-instance/long-term-backup-retention-configure.md?view=azuresql-mi&preserve-view=true)