Merge pull request #30419 from rwestMSFT/rw-0418-rename-include

[SCOPED] INCLUDE file maintenance - rename managed-backup file

Author: JamesJBarnett

docs/includes/ss-smartbackup-md.md docs/includes/ss-managed-backup-md.mddocs/includes/ss-smartbackup-md.md renamed to docs/includes/ss-managed-backup-md.md

@@ -1,8 +1,8 @@
 ---
 author: rwestMSFT
 ms.author: randolphwest
-ms.date: 01/29/2024
+ms.date: 04/18/2024
 ms.service: sql
 ms.topic: include
 ---
- SQL Server Managed Backup to Microsoft Azure 
+ SQL Server managed backup to Microsoft Azure 

docs/relational-databases/backup-restore/backup-encryption.md

@@ -17,7 +17,7 @@ This article provides an overview of the encryption options for [!INCLUDE [ssNoV
 
 ## Overview
 
-Starting in [!INCLUDE [ssSQL14](../../includes/sssql14-md.md)], SQL Server has the ability to encrypt the data while creating a backup. By specifying the encryption algorithm and the encryptor (a Certificate or Asymmetric Key) when creating a backup, you can create an encrypted backup file. All storage destinations: on-premises and Azure storage are supported. In addition, encryption options can be configured for [!INCLUDE [ss_smartbackup](../../includes/ss-smartbackup-md.md)] operations, a new feature introduced in [!INCLUDE [ssSQL14](../../includes/sssql14-md.md)].
+Starting in [!INCLUDE [ssSQL14](../../includes/sssql14-md.md)], SQL Server has the ability to encrypt the data while creating a backup. By specifying the encryption algorithm and the encryptor (a Certificate or Asymmetric Key) when creating a backup, you can create an encrypted backup file. All storage destinations: on-premises and Azure storage are supported. In addition, encryption options can be configured for [!INCLUDE [ss-managed-backup](../../includes/ss-managed-backup-md.md)] operations, a new feature introduced in [!INCLUDE [ssSQL14](../../includes/sssql14-md.md)].
 
 To encrypt during backup, you must specify an encryption algorithm, and an encryptor to secure the encryption key. The following are the supported encryption options:
 
@@ -44,7 +44,7 @@ If you're restoring a backup from a TDE encrypted database, the TDE certificate
 
 1. Encryption can also be used for databases that are encrypted using TDE.
 
-1. Encryption is supported for backups done by [!INCLUDE [ss_smartbackup](../../includes/ss-smartbackup-md.md)], which provides additional security for off-site backups.
+1. Encryption is supported for backups done by [!INCLUDE [ss-managed-backup](../../includes/ss-managed-backup-md.md)], which provides additional security for off-site backups.
 
 1. This feature supports multiple encryption algorithms up to AES 256 bit. This gives you the option to select an algorithm that aligns with your requirements.
 

docs/relational-databases/backup-restore/configure-advanced-options-for-sql-server-managed-backup-to-microsoft-azure.md

@@ -13,14 +13,14 @@ f1_keywords:
 ---
 # Configure advanced options for SQL Server managed backup to Microsoft Azure
  [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
-  The following tutorial describes how to set advanced options for [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)]. These procedures are only necessary if you require the features they offer. Otherwise, you can enable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] and depend on the default behavior.  
+  The following tutorial describes how to set advanced options for [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)]. These procedures are only necessary if you require the features they offer. Otherwise, you can enable [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] and depend on the default behavior.  
 
  In each scenario, the backup is specified using the `database_name` parameter. When `database_name` is NULL or *, then the changes affect the default settings at an Instance level. Instance level settings also affect new databases created after the change.  
 
  Once you have specified these settings, you can then enable managed backup for the database or instance using the system stored procedure [managed_backup.sp_backup_config_basic (Transact-SQL)](../../relational-databases/system-stored-procedures/managed-backup-sp-backup-config-basic-transact-sql.md). For more information, see [Enable SQL Server managed backup to Microsoft Azure](../../relational-databases/backup-restore/enable-sql-server-managed-backup-to-microsoft-azure.md).  
 
 > [!WARNING]  
->  You should always configure the advanced options and custom scheduling options before enabling [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] with [managed_backup.sp_backup_config_basic (Transact-SQL)](../../relational-databases/system-stored-procedures/managed-backup-sp-backup-config-basic-transact-sql.md). Otherwise, it is possible that unwanted backup operations will occur during the window of time between enabling [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] and configuring these settings.  
+>  You should always configure the advanced options and custom scheduling options before enabling [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] with [managed_backup.sp_backup_config_basic (Transact-SQL)](../../relational-databases/system-stored-procedures/managed-backup-sp-backup-config-basic-transact-sql.md). Otherwise, it is possible that unwanted backup operations will occur during the window of time between enabling [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] and configuring these settings.  
   
 ## Configure Encryption  
  The following steps describe how to specify encryption settings using the stored procedure  [managed_backup.sp_backup_config_advanced (Transact-SQL)](../../relational-databases/system-stored-procedures/managed-backup-sp-backup-config-advanced-transact-sql.md).  
@@ -105,7 +105,7 @@ f1_keywords:
     ```  
   
 ## Next Steps  
- After configuring advanced options and custom schedules, you must enable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] on the target database or SQL Server instance. For more information, see [Enable SQL Server Managed Backup to Microsoft Azure](../../relational-databases/backup-restore/enable-sql-server-managed-backup-to-microsoft-azure.md).  
+ After configuring advanced options and custom schedules, you must enable [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] on the target database or SQL Server instance. For more information, see [Enable SQL Server Managed Backup to Microsoft Azure](../../relational-databases/backup-restore/enable-sql-server-managed-backup-to-microsoft-azure.md).  
   
 ## See Also  
  [SQL Server Managed Backup to Microsoft Azure](../../relational-databases/backup-restore/sql-server-managed-backup-to-microsoft-azure.md)  

docs/relational-databases/backup-restore/create-an-encrypted-backup.md

@@ -63,7 +63,7 @@ ms.topic: conceptual
  For an example of encrypting a backup protected by an EKM, see [Extensible Key Management Using Azure Key Vault (SQL Server)](../../relational-databases/security/encryption/extensible-key-management-using-azure-key-vault-sql-server.md).  
   
 ### Backup to Azure Storage with Encryption  
- If you are creating a backup to Azure storage using the **SQL Server Backup to URL** option, the encryption steps are the same, but you must use URL as the destination and a SQL Credential to authenticate to the Azure storage. If you want to configure [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] with encryption options, see [Enable SQL Server Managed Backup to Microsoft Azure](../../relational-databases/backup-restore/enable-sql-server-managed-backup-to-microsoft-azure.md).  
+ If you are creating a backup to Azure storage using the **SQL Server Backup to URL** option, the encryption steps are the same, but you must use URL as the destination and a SQL Credential to authenticate to the Azure storage. If you want to configure [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] with encryption options, see [Enable SQL Server Managed Backup to Microsoft Azure](../../relational-databases/backup-restore/enable-sql-server-managed-backup-to-microsoft-azure.md).  
   
  **Prerequisites:**  
   

docs/relational-databases/backup-restore/disable-sql-server-managed-backup-to-microsoft-azure.md

@@ -10,12 +10,12 @@ ms.topic: conceptual
 ---
 # Disable SQL Server Managed Backup to Microsoft Azure
  [!INCLUDE [SQL Server](../../includes/applies-to-version/sqlserver.md)]
-  This topic describes how to disable or pause [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] at both the database and instance levels.  
+  This topic describes how to disable or pause [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] at both the database and instance levels.  
 
-##  <a name="DatabaseDisable"></a> Disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] for a database  
- You can disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] settings by using the system stored procedure, [managed_backup.sp_backup_config_basic (Transact-SQL)](../../relational-databases/system-stored-procedures/managed-backup-sp-backup-config-basic-transact-sql.md). The *\@enable_backup* parameter is used to enable and disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] configurations for a specific database, where 1 enables and 0 disables the configuration settings.  
+##  <a name="DatabaseDisable"></a> Disable [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] for a database  
+ You can disable [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] settings by using the system stored procedure, [managed_backup.sp_backup_config_basic (Transact-SQL)](../../relational-databases/system-stored-procedures/managed-backup-sp-backup-config-basic-transact-sql.md). The *\@enable_backup* parameter is used to enable and disable [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] configurations for a specific database, where 1 enables and 0 disables the configuration settings.  
 
-#### To Disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] for a specific database:  
+#### To Disable [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] for a specific database:  
 
 1.  Connect to the [!INCLUDE[ssDE](../../includes/ssde-md.md)].  
 
@@ -33,16 +33,16 @@ GO
 > [!NOTE]
 > You might also need to set the `@container_url` parameter depending on your configuration.
   
-##  <a name="DatabaseAllDisable"></a> Disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] for all the databases on the Instance  
- The following procedure is for when you want to disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] configuration settings from all the databases that currently have [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] enabled on the instance.  The configuration settings like the storage URL, retention, and the SQL Credential will remain in the metadata and can be used if [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] is enabled for the database at a later time. If you want to just pause [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] services temporarily, you can use the master switch explained in the later sections of this topic.  
+##  <a name="DatabaseAllDisable"></a> Disable [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] for all the databases on the Instance  
+ The following procedure is for when you want to disable [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] configuration settings from all the databases that currently have [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] enabled on the instance.  The configuration settings like the storage URL, retention, and the SQL Credential will remain in the metadata and can be used if [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] is enabled for the database at a later time. If you want to just pause [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] services temporarily, you can use the master switch explained in the later sections of this topic.  
 
-#### To disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] for all the databases:  
+#### To disable [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] for all the databases:  
 
 1.  Connect to the [!INCLUDE[ssDE](../../includes/ssde-md.md)].  
 
 2.  From the Standard bar, click **New Query**.  
 
-3.  Copy and paste the following example into the query window and click **Execute**. The following example identifies if [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] is configured at the instance level and all the [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] enabled databases on the instance, and executes the system stored procedure **sp_backup_config_basic** to disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)].  
+3.  Copy and paste the following example into the query window and click **Execute**. The following example identifies if [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] is configured at the instance level and all the [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] enabled databases on the instance, and executes the system stored procedure **sp_backup_config_basic** to disable [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)].  
 
 ```sql
 -- Create a working table to store the database names  
@@ -100,10 +100,10 @@ SELECT * FROM managed_backup.fn_backup_db_config (NULL);
 GO  
 ```  
 
-##  <a name="InstanceDisable"></a> Disable Default [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] settings for the Instance  
- Default settings at the instance level apply to all new databases created on that instance.  If you no longer need or require default settings, you can disable this configuration by using the **managed_backup.sp_backup_config_basic** system stored procedure with the *\@database_name* parameter set to NULL. Disabling does not remove the other configuration settings like the storage URL, retention setting, or the SQL Credential name. These settings will be used if [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] is enabled for the instance at a later time.  
+##  <a name="InstanceDisable"></a> Disable Default [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] settings for the Instance  
+ Default settings at the instance level apply to all new databases created on that instance.  If you no longer need or require default settings, you can disable this configuration by using the **managed_backup.sp_backup_config_basic** system stored procedure with the *\@database_name* parameter set to NULL. Disabling does not remove the other configuration settings like the storage URL, retention setting, or the SQL Credential name. These settings will be used if [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] is enabled for the instance at a later time.  
 
-#### To disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] default configuration settings:  
+#### To disable [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] default configuration settings:  
 
 1.  Connect to the [!INCLUDE[ssDE](../../includes/ssde-md.md)].  
 
@@ -117,10 +117,10 @@ GO
     GO
     ```  
 
-##  <a name="InstancePause"></a> Pause [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] at the Instance Level  
- There might be times when you need to temporarily pause the [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] services for a short period time.  The **managed_backup.sp_backup_master_switch** system stored procedure allows you to disable [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] service at the instance level.  The same stored procedure is used to resume [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)]. The \@state parameter is used to define whether [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] should be turned off or on.  
+##  <a name="InstancePause"></a> Pause [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] at the Instance Level  
+ There might be times when you need to temporarily pause the [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] services for a short period time.  The **managed_backup.sp_backup_master_switch** system stored procedure allows you to disable [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] service at the instance level.  The same stored procedure is used to resume [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)]. The \@state parameter is used to define whether [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] should be turned off or on.  
 
-#### To Pause [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] Services Using Transact-SQL:  
+#### To Pause [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] Services Using Transact-SQL:  
 
 1.  Connect to the [!INCLUDE[ssDE](../../includes/ssde-md.md)].  
 
@@ -135,7 +135,7 @@ EXEC managed_backup.sp_backup_master_switch @new_state=0;
 Go
 ```  
 
-#### To resume [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] Using Transact-SQL  
+#### To resume [!INCLUDE[ss-managed-backup](../../includes/ss-managed-backup-md.md)] Using Transact-SQL  
 
 1.  Connect to the [!INCLUDE[ssDE](../../includes/ssde-md.md)].