Merge pull request #34292 from rwestMSFT/rw-0603-fix-copy-only

Remove ambiguity in copy-only backup article

Author: JamesJBarnett

docs/relational-databases/backup-restore/copy-only-backups-sql-server.md

@@ -1,10 +1,10 @@
 ---
-title: Copy-only backups
+title: Copy-Only Backups
 description: A copy-only backup is a SQL Server backup that is independent of the sequence of SQL Server backups. It doesn't affect how later backups are restored.
 author: MashaMSFT
 ms.author: mathoma
 ms.reviewer: randolphwest
-ms.date: 12/28/2023
+ms.date: 06/03/2025
 ms.service: sql
 ms.subservice: backup-restore
 ms.topic: conceptual
@@ -20,30 +20,37 @@ monikerRange: "=azuresqldb-mi-current || >=sql-server-2016 || >=sql-server-linux
 
 A *copy-only backup* is a [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] backup that is independent of the sequence of conventional [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] backups. Usually, taking a backup changes the database and affects how later backups are restored. However, occasionally, it's useful to take a backup for a special purpose without affecting the overall backup and restore procedures for the database. Copy-only backups serve this purpose.
 
+## Types of copy-only backups
+
 The types of copy-only backups are as follows:
 
-- **Copy-only full backups (all recovery models)**
+### Copy-only full backups (all recovery models)
+
+- A copy-only *full* backup can't serve as a differential base or differential backup and doesn't affect the differential base.
 
-  - A copy-only backup can't serve as a differential base or differential backup and doesn't affect the differential base.
+- Restoring a copy-only full backup is the same as restoring any other full backup.
 
-  - Restoring a copy-only full backup is the same as restoring any other full backup.
+### Copy-only log backups (full recovery model and bulk-logged recovery model only)
 
-- **Copy-only log backups (full recovery model and bulk-logged recovery model only)**
+- A copy-only *log* backup preserves the existing log archive point and, therefore, doesn't affect the sequencing of regular log backups. Copy-only log backups are typically unnecessary. Instead, you can create a new routine log backup, and restore that backup (using the `WITH NORECOVERY` option) together with any previous log backups that are required for the restore sequence.
 
-  - A copy-only log backup preserves the existing log archive point and, therefore, doesn't affect the sequencing of regular log backups. Copy-only log backups are typically unnecessary. Instead, you can create a new routine log backup (using `WITH NORECOVERY`) and use that backup together with any previous log backups that are required for the restore sequence. However, a copy-only log backup can sometimes be useful for performing an online restore. For more information, follow the instructions in the article [Example: Online restore of a read-write file (full recovery model)](example-online-restore-of-a-read-write-file-full-recovery-model.md), using the copy-only backup files instead.
+  A copy-only log backup can sometimes be useful for performing an online restore. For more information, follow the instructions in the article [Example: Online restore of a read-write file (full recovery model)](example-online-restore-of-a-read-write-file-full-recovery-model.md), using the copy-only backup files instead.
 
-  - The transaction log is never truncated after a copy-only backup.
+- The transaction log is never truncated after a copy-only backup.
 
-Copy-only backups are recorded in the `is_copy_only` column of the [backupset](../../relational-databases/system-tables/backupset-transact-sql.md) table.
+## Remarks
 
-> [!IMPORTANT]  
-> In [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)], copy-only backups can't be created for a database encrypted with [service-managed Transparent Data Encryption (TDE)](/azure/sql-database/transparent-data-encryption-azure-sql?tabs=azure-portal#service-managed-transparent-data-encryption). Service-managed TDE uses internal key for encryption of data, and that key can't be exported, so you couldn't restore the backup anywhere else. Consider using [customer-managed TDE](/azure/sql-database/transparent-data-encryption-byok-azure-sql) instead to be able to create copy-only backups of encrypted databases, but make sure to have encryption key available for later restore.
+Copy-only backups are recorded in the `is_copy_only` column of the [backupset](../system-tables/backupset-transact-sql.md) table.
+
+In [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)], copy-only backups can't be created for a database encrypted with [service-managed Transparent Data Encryption (TDE)](/azure/sql-database/transparent-data-encryption-azure-sql?tabs=azure-portal#service-managed-transparent-data-encryption). Service-managed TDE uses internal key for encryption of data, and that key can't be exported, so you couldn't restore the backup anywhere else. Consider using [customer-managed TDE](/azure/sql-database/transparent-data-encryption-byok-azure-sql) instead to be able to create copy-only backups of encrypted databases, but make sure to have encryption key available for later restore.
 
 ## Create a copy-only backup
 
 You can create a copy-only backup with [!INCLUDE [ssManStudioFull](../../includes/ssmanstudiofull-md.md)], [!INCLUDE [azure-data-studio](../../includes/azure-data-studio-short.md)], [!INCLUDE [tsql](../../includes/tsql-md.md)], or PowerShell.
 
-### <a id="SSMSProcedure"></a> A. Use SQL Server Management Studio
+<a id="SSMSProcedure"></a>
+
+### A. Use SQL Server Management Studio
 
 In this example, a copy-only backup of the `Sales` database is backed up to disk at the default backup location.
 
@@ -55,7 +62,9 @@ In this example, a copy-only backup of the `Sales` database is backed up to disk
 
 1. Select **OK**.
 
-### <a id="TsqlProcedure"></a> B. Use Transact-SQL
+<a id="TsqlProcedure"></a>
+
+### B. Use Transact-SQL
 
 This example creates a copy-only backup for the `Sales` database utilizing the `COPY_ONLY` parameter. A copy-only backup of the transaction log is taken as well.
 
@@ -72,15 +81,17 @@ WITH COPY_ONLY;
 > [!NOTE]  
 > `COPY_ONLY` has no effect when specified with the `DIFFERENTIAL` option.
 
-### <a id="TsqlProcedureManagedInstance"></a> C. Use Transact-SQL and Azure SQL Managed Instance
+<a id="TsqlProcedureManagedInstance"></a>
+
+### C. Use Transact-SQL and Azure SQL Managed Instance
 
-Azure SQL Managed Instance supports taking COPY_ONLY full backups. The example performs a COPY_ONLY backup of `MyDatabase` to the Microsoft Azure Blob Storage. The storage Account name is `mystorageaccount`. The container is called `myfirstcontainer`. A storage access policy has been created with read, write, delete, and list rights. The [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] credential, `https://mystorageaccount.blob.core.windows.net/myfirstcontainer`, was created using a Shared Access Signature that is associated with the Storage Access Policy secret. For information on [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] backup to the Microsoft Azure Blob Storage, see [SQL Server Backup and Restore with Microsoft Azure Blob Storage](../../relational-databases/backup-restore/sql-server-backup-and-restore-with-microsoft-azure-blob-storage-service.md) and [SQL Server Backup to URL](../../relational-databases/backup-restore/sql-server-backup-to-url.md).
+Azure SQL Managed Instance supports taking `COPY_ONLY` full backups. The example performs a `COPY_ONLY` backup of `MyDatabase` to the Microsoft Azure Blob Storage. The storage Account name is `mystorageaccount`. The container is called `myfirstcontainer`. A storage access policy is created with read, write, delete, and list rights. The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] credential, `https://mystorageaccount.blob.core.windows.net/myfirstcontainer`, was created using a Shared Access Signature that is associated with the Storage Access Policy secret. For information on [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] backup to the Microsoft Azure Blob Storage, see [SQL Server backup and restore with Azure Blob Storage](sql-server-backup-and-restore-with-microsoft-azure-blob-storage-service.md) and [SQL Server backup to URL for Microsoft Azure Blob Storage](sql-server-backup-to-url.md).
 
 ```sql
 -- Prerequisite to have write permissions
 CREATE CREDENTIAL [https://mystorageaccount.blob.core.windows.net/myfirstcontainer]
 WITH IDENTITY = 'SHARED ACCESS SIGNATURE',
-SECRET = 'sp=...' -- Enter your secret SAS token here.
+SECRET = 'sp=...'; -- Enter your secret SAS token here.
 
 BACKUP DATABASE MyDatabase
 TO URL = 'https://mystorageaccount.blob.core.windows.net/myfirstcontainer/MyDatabaseBackup.bak'
@@ -96,10 +107,11 @@ URL = 'https://mystorageaccount.blob.core.windows.net/myfirstcontainer/MyDatabas
 URL = 'https://mystorageaccount.blob.core.windows.net/myfirstcontainer/MyDatabase-03.bak',
 URL = 'https://mystorageaccount.blob.core.windows.net/myfirstcontainer/MyDatabase-04.bak'
 WITH COPY_ONLY;
-
 ```
 
-### <a id="PowerShellProcedure"></a> D. Use PowerShell
+<a id="PowerShellProcedure"></a>
+
+### D. Use PowerShell
 
 This example creates a copy-only backup for the `Sales` database utilizing the `-CopyOnly` parameter.
 
@@ -111,22 +123,22 @@ Backup-SqlDatabase -ServerInstance 'SalesServer' -Database 'Sales' -BackupFile '
 
 ### Create a full or log backup
 
-- [Create a Full Database Backup (SQL Server)](create-a-full-database-backup-sql-server.md)
-- [Back Up a Transaction Log (SQL Server)](back-up-a-transaction-log-sql-server.md)
+- [Create a Full Database Backup](create-a-full-database-backup-sql-server.md)
+- [Back up a transaction log](back-up-a-transaction-log-sql-server.md)
 
 ### View copy-only backups
 
-- [backupset (Transact-SQL)](../../relational-databases/system-tables/backupset-transact-sql.md)
+- [backupset (Transact-SQL)](../system-tables/backupset-transact-sql.md)
 
 ### Set up and use the SQL Server PowerShell provider
 
 - [SQL Server PowerShell Provider](/powershell/sql-server/sql-server-powershell-provider)
 
 ## Related content
 
-- [Backup Overview (SQL Server)](backup-overview-sql-server.md)
-- [Recovery Models (SQL Server)](recovery-models-sql-server.md)
-- [Copy Databases with Backup and Restore](../../relational-databases/databases/copy-databases-with-backup-and-restore.md)
-- [Restore and Recovery Overview (SQL Server)](restore-and-recovery-overview-sql-server.md)
+- [Backup overview (SQL Server)](backup-overview-sql-server.md)
+- [Recovery models (SQL Server)](recovery-models-sql-server.md)
+- [Copy Databases with Backup and Restore](../databases/copy-databases-with-backup-and-restore.md)
+- [Restore and recovery overview (SQL Server)](restore-and-recovery-overview-sql-server.md)
 - [BACKUP (Transact-SQL)](../../t-sql/statements/backup-transact-sql.md)
 - [Backup-SqlDatabase](/powershell/module/sqlserver/backup-sqldatabase)