Merge pull request #281434 from AbhishekMallick-MS/Jul-22-2024-Freshness

Freshness - SPT farm backup

Author: AnnaMHuff

articles/backup/backup-azure-backup-sharepoint-mabs.md

@@ -2,9 +2,9 @@
 title: Back up a SharePoint farm to Azure with MABS
 description: Use Azure Backup Server to back up and restore your SharePoint data. This article provides the information to configure your SharePoint farm so that desired data can be stored in Azure. You can restore protected SharePoint data from disk or from Azure.
 ms.topic: how-to
-ms.date: 11/29/2022
+ms.date: 07/22/2024
 ms.service: backup
-ms.custom: engagement-fy23
+ms.custom: engagement-fy24
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
 ---
@@ -15,18 +15,6 @@ This article describes how to back up SharePoint farm using Microsoft Azure Back
 
 Microsoft Azure Backup Server (MABS) enables you to back up a SharePoint farm to Microsoft Azure, which gives an experience similar to back up of other data sources. Azure Backup provides flexibility in the backup schedule to create daily, weekly, monthly, or yearly backup points, and gives you retention policy options for various backup points. It also provides the capability to store local disk copies for quick recovery-time objectives (RTO) and to store copies to Azure for economical, long-term retention.
 
-In this article, you'll learn about:
-
-> [!div class="checklist"]
-> - SharePoint supported scenarios
-> - Prerequisites
-> - Configure the backup
-> - Monitor the operations
-> - Restore a SharePoint item from disk using MABS
-> - Restore a SharePoint database from Azure using MABS
-> - Switch the front-end Web server
-> - Remove a database from a SharePoint farm
-
 >[!Note]
 >The backup process for SharePoint to Azure using MABS is similar to back up of SharePoint to Data Protection Manager (DPM) locally. Particular considerations for Azure are noted in this article.
 
@@ -43,6 +31,14 @@ For information on the supported SharePoint versions and the MABS versions requi
 * MABS that protects a SharePoint farm doesn't protect search indexes or application service databases. You need to configure the protection of these databases separately.
 * MABS doesn't provide backup of SharePoint SQL Server databases that are hosted on scale-out file server (SOFS) shares.
 
+### Limitations
+
+* You can't protect SharePoint databases as a SQL Server data source. You can recover individual databases from a farm backup.
+
+* Protecting application store items isn't supported with SharePoint 2013.
+
+* MABS doesn't support protecting remote FILESTREAM. The FILESTREAM should be part of the database.
+
 ## Prerequisites
 
 Before you continue, ensure that you've met all the [prerequisites for using Microsoft Azure Backup](backup-azure-dpm-introduction.md#prerequisites-and-limitations) to protect workloads. The tasks for prerequisites also include: create a backup vault, download vault credentials, install Azure Backup Agent, and register the Azure Backup Server with the vault.
@@ -53,18 +49,10 @@ Additional prerequisites:
 
 * Remember that MABS runs as **Local System**, and it needs *sysadmin* privileges on that account for the SQL server to back up SQL Server databases. On the SQL Server you want to back up, set *NT AUTHORITY\SYSTEM* to **sysadmin**.
 
-* For every 10 million items in the farm, there must be at least 2 GB of space on the volume where the MABS folder is located. This space is required for catalog generation. To enable you to use MABS to perform a specific recovery of items (site collections, sites, lists, document libraries, folders, individual documents, and list items), catalog generation creates a list of the URLs contained within each content database. You can view the list of URLs in the recoverable item pane in the Recovery task area of the MABS Administrator Console.
+* For every 10 million items in the farm, there must be at least 2 GB of space on the volume where the MABS folder is located. This space is required for catalog generation. To enable you to use MABS to perform a specific recovery of items (site collections, sites, lists, document libraries, folders, individual documents, and list items), catalog generation creates a list of the URLs contained within each content database. You can view the list of URLs in the recoverable item blade in the Recovery task area of the MABS Administrator Console.
 
 * In the SharePoint farm, if you've SQL Server databases that are configured with SQL Server aliases, install the SQL Server client components on the front-end Web server that MABS will protect.
 
-### Limitations
-
-* You can't protect SharePoint databases as a SQL Server data source. You can recover individual databases from a farm backup.
-
-* Protecting application store items isn't supported with SharePoint 2013.
-
-* MABS doesn't support protecting remote FILESTREAM. The FILESTREAM should be part of the database.
-
 ## Configure the backup
 
 To back up the SharePoint farm, configure protection for SharePoint by using *ConfigureSharePoint.exe* and then create a protection group in MABS.
@@ -105,15 +93,15 @@ Follow these steps:
 
    When you expand the computer running SharePoint, MABS queries VSS to see what data MABS can protect. If the SharePoint database is remote, MABS connects to it. If SharePoint data sources don't appear, check that the VSS writer is running on the computer that's running SharePoint and on any remote instance of SQL Server. Then, ensure that the MABS agent is installed both on the computer running SharePoint and on the remote instance of SQL Server. Also, ensure that SharePoint databases aren't being protected elsewhere as SQL Server databases.
 
-1. On **Select data protection method**,  specify how you want to handle short and long\-term backup. Short\-term back up is always to disk first, with the option of backing up from the disk to the Azure cloud with Azure Backup \(for short or long\-term\).
+1. On **Select data protection method**,  specify how you want to handle short and long\-term backup. Short\-term backup is always to disk first, with the option of backing up from the disk to the Azure cloud with Azure Backup \(for short or long\-term\).
 
 1. On **Select short\-term goals**, specify how you want to back up to short\-term storage on disk.   In **Retention range** you specify how long you want to keep the data on disk. In **Synchronization frequency**, you specify how often you want to run an incremental backup to disk. 
 
    If you don't want to set a backup interval, you can check just before  a recovery point so that MABS will run an express full backup just before each recovery point is scheduled.
 
 1. On the **Review disk allocation** page, review the storage pool disk space allocated for the protection group.
 
-   **Total Data size** is the size of the data you want to back up, and **Disk space to be provisioned on MABS** is the space that MABS recommends for the protection group. MABS chooses the ideal backup volume, based on the settings. However, you can edit the backup volume choices in the **Disk allocation details**. For the workloads, select the preferred storage in the dropdown menu. Your edits change the values for **Total Storage** and **Free Storage** in the **Available Disk Storage** pane. Underprovisioned space is the amount of storage MABS suggests you add to the volume, to continue with backups smoothly in the future.
+   **Total Data size** is the size of the data you want to back up, and **Disk space to be provisioned on MABS** is the space that MABS recommends for the protection group. MABS chooses the ideal backup volume, based on the settings. However, you can edit the backup volume choices in the **Disk allocation details**. For the workloads, select the preferred storage in the dropdown menu. Your edits change the values for **Total Storage** and **Free Storage** in the **Available Disk Storage** blade. Underprovisioned space is the amount of storage MABS suggests you add to the volume, to continue with backups smoothly in the future.
 
 1. On **Choose replica creation method**, select how you want to handle the initial full data replication.
 
@@ -323,20 +311,20 @@ When a database is removed from a SharePoint farm, MABS will skip the backup of
 
 ### MABS Alert - Farm Configuration Changed
 
-This is a warning alert that is generated in Microsoft Azure Backup Server (MABS) when automatic protection of a SharePoint database fails. See the alert **Details** pane for more information about the cause of this alert.
+This is a warning alert that is generated in Microsoft Azure Backup Server (MABS) when automatic protection of a SharePoint database fails. See the alert **Details** blade for more information about the cause of this alert.
 
 To resolve this alert, follow these steps:
 
 1. Verify with the SharePoint administrator if the database has actually been removed from the farm. If the database has been removed from the farm, then it must be removed from active protection in MABS.
 1. To remove the database from active protection:
    1. In **MABS Administrator Console**, click **Protection** on the navigation bar.
-   1. In the **Display** pane, right-click the protection group for the SharePoint farm, and then click **Stop Protection of member**.
+   1. In the **Display** blade, right-click the protection group for the SharePoint farm, and then click **Stop Protection of member**.
    1. In the **Stop Protection** dialog box, click **Retain Protected Data**.
    1. Select **Stop Protection**.
 
 You can add the SharePoint farm back for protection by using the **Modify Protection Group** wizard. During re-protection, select the SharePoint front-end server and click **Refresh** to update the SharePoint database cache, then select the SharePoint farm and proceed.
 
-## Next steps
+## Next step
 
 - [Back up Exchange server](backup-azure-exchange-mabs.md)
 - [Back up SQL Server](backup-azure-sql-mabs.md)

articles/backup/backup-sql-server-vm-from-vm-pane.md

@@ -1,37 +1,42 @@
 ---
 title: Back up a SQL Server VM from the VM pane
 description: In this article, learn how to back up SQL Server databases on Azure virtual machines from the VM pane.
-ms.topic: conceptual
-ms.date: 08/11/2022
+ms.topic: how-to
+ms.date: 07/22/2024
 author: AbhishekMallick-MS
 ms.author: v-abhmallick
+ms.custom: engagement-fy24
 ---
-# Back up a SQL Server from the VM pane
+# Back up a SQL Server from the VM blade
 
 This article explains how to back up SQL Server running in Azure VMs with the [Azure Backup](backup-overview.md) service. You can back up SQL Server VMs using two methods:
 
 - Single SQL Server Azure VM: The instructions in this article describe how to back up a SQL Server VM directly from the VM view.
 - Multiple SQL Server Azure VMs: You can set up a Recovery Services vault and configure backup for multiple VMs. Follow the instructions in [this article](backup-sql-server-database-azure-vms.md) for that scenario.
 
+## Prerequisites
+
+Before you start the SQL Server backup operation, see the [backup prerequisites](backup-sql-server-database-azure-vms.md#prerequisites).
+
 ## Before you start
 
-1. Verify your environment with the [support matrix](sql-support-matrix.md).
-2. Get an [overview](backup-azure-sql-database.md) of Azure Backup for SQL Server VM.
-3. Verify that the VM has [network connectivity](backup-sql-server-database-azure-vms.md#establish-network-connectivity).
+- Verify your environment with the [support matrix](sql-support-matrix.md).
+- Get an [overview](backup-azure-sql-database.md) of Azure Backup for SQL Server VM.
+- Verify that the VM has [network connectivity](backup-sql-server-database-azure-vms.md#establish-network-connectivity).
 
 >[!Note]
 >See the [SQL backup support matrix](sql-support-matrix.md) to know more about the supported configurations and scenarios.
 
 ## Configure backup on the SQL Server
 
-You can enable backup on your SQL Server VM from the **Backup** pane in the VM. This method does two things:
+You can enable backup on your SQL Server VM from the **Backup** blade in the VM. This method does two things:
 
 - Registers the SQL VM with the Azure Backup service to give it access.
 - Autoprotects all the SQL Server instances running inside the VM. This means that the backup policy is applied to all the existing databases, as well as the databases that will be added to these instances in the future.
 
 1. Select the banner on the top of the page to open the SQL Server backup view.
 
-    ![SQL Server backup view](./media/backup-sql-server-vm-from-vm-pane/sql-server-backup-view.png)
+    ![Screenshot shows the SQL Server backup view.](./media/backup-sql-server-vm-from-vm-pane/sql-server-backup-view.png)
 
     >[!NOTE]
     >Don't see the banner? The banner is only displayed for those SQL Server VMs that are created using Azure Marketplace images. It's additionally displayed for the VMs that are protected with Azure VM Backup. For other images, you can configure backup as explained [here](backup-sql-server-database-azure-vms.md).
@@ -43,32 +48,32 @@ You can enable backup on your SQL Server VM from the **Backup** pane in the VM.
 
 3. Choose a **Backup Policy**. You can choose from the default policy, or any other existing policies that you created in the vault. If you want to create a new policy, you can refer to [this article](backup-sql-server-database-azure-vms.md#create-a-backup-policy) for a step-by-step guide.
 
-    ![Choose a backup policy](./media/backup-sql-server-vm-from-vm-pane/backup-policy.png)
+    ![Screenshot shows how to choose a backup policy.](./media/backup-sql-server-vm-from-vm-pane/backup-policy.png)
 
 4. Select **Enable Backup**. The operation may take a few minutes to complete.
 
-    ![Select enable backup](./media/backup-sql-server-vm-from-vm-pane/enable-backup.png)
+    ![Screenshot shows how to select enable backup.](./media/backup-sql-server-vm-from-vm-pane/enable-backup.png)
 
 5. Once the operation is completed, you'll see the **vault name** in the banner.
 
-    ![Vault name appears in banner](./media/backup-sql-server-vm-from-vm-pane/vault-name.png)
+    ![Screenshot shows the Vault name in banner.](./media/backup-sql-server-vm-from-vm-pane/vault-name.png)
 
 6. Select the banner to go the vault view, where you can see all the registered VMs and their protection status.
 
-    ![Vault view with registered VMs](./media/backup-sql-server-vm-from-vm-pane/vault-view.png)
+    ![Screenshot shows the Vault view with registered VMs.](./media/backup-sql-server-vm-from-vm-pane/vault-view.png)
 
 7. For non-marketplace images, the registration may be successful, but **configure backup** may not be triggered until the Azure Backup extension is given permission on the SQL Server. In such cases, the **Backup Readiness** column reads **Not Ready**. You need to [assign the appropriate permissions](backup-azure-sql-database.md#set-vm-permissions) manually for non-marketplace images so configure backup can get triggered.
 
-    ![Backup readiness isn't ready](./media/backup-sql-server-vm-from-vm-pane/backup-readiness-not-ready.png)
+    ![Screenshot shows that the backup readiness isn't ready.](./media/backup-sql-server-vm-from-vm-pane/backup-readiness-not-ready.png)
 
 8. For further operations or monitoring that you need to do on the backed-up SQL Server VM, go to the corresponding Recovery Services vault. Go to **Backup Items** to see all the databases backed up in this vault, and trigger operations such as on-demand backup and restore. Similarly, go to **Backup Jobs** to [monitor](manage-monitor-sql-database-backup.md) jobs corresponding to operations such as configure protection, backup, and restore.
 
-    ![See backed-up databases in Backup Items](./media/backup-sql-server-vm-from-vm-pane/backup-items.png)
+    ![Screenshot shows how to view backed-up databases in Backup Items.](./media/backup-sql-server-vm-from-vm-pane/backup-items.png)
 
 >[!NOTE]
 >The backup isn't automatically configured on any of the new SQL Server instances that may be added later to the protected VM. To configure backup on the newly added instances, you need to go the vault that the VM is registered to and follow the steps listed [here](backup-sql-server-database-azure-vms.md).
 
-## Next steps
+## Next step
 
 Learn how to: