|
2 | 2 | title: Back up a SharePoint farm to Azure with MABS
|
3 | 3 | 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.
|
4 | 4 | ms.topic: how-to
|
5 |
| -ms.date: 07/22/2024 |
| 5 | +ms.date: 07/14/2025 |
6 | 6 | ms.service: azure-backup
|
7 | 7 | ms.custom: engagement-fy24
|
8 |
| -author: jyothisuri |
9 |
| -ms.author: jsuri |
| 8 | +author: AbhishekMallick-MS |
| 9 | +ms.author: v-mallicka |
10 | 10 | # Customer intent: "As a SharePoint administrator, I want to configure Azure Backup Server to back up my SharePoint farm, so that I can ensure data protection and enable quick recovery of my SharePoint data in the event of loss or corruption."
|
11 | 11 | ---
|
12 | 12 |
|
@@ -54,11 +54,9 @@ Additional prerequisites:
|
54 | 54 |
|
55 | 55 | * 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.
|
56 | 56 |
|
57 |
| -## Configure the backup |
| 57 | +## Configure SharePoint Farm backup |
58 | 58 |
|
59 |
| -To back up the SharePoint farm, configure protection for SharePoint by using *ConfigureSharePoint.exe* and then create a protection group in MABS. |
60 |
| - |
61 |
| -Follow these steps: |
| 59 | +To back up the SharePoint farm, configure protection for SharePoint using *ConfigureSharePoint.exe* and create a protection group in MABS by following these steps: |
62 | 60 |
|
63 | 61 | 1. **Run ConfigureSharePoint.exe**: This tool configures the SharePoint VSS Writer service \(WSS\) and provides the protection agent with credentials for the SharePoint farm. After you've deployed the protection agent, the ConfigureSharePoint.exe file can be found in the `<MABS Installation Path\>\bin` folder on the front\-end Web server.
|
64 | 62 |
|
@@ -128,17 +126,17 @@ Follow these steps:
|
128 | 126 |
|
129 | 127 | When it finishes, the protection group status will show as **OK** on the **Status** page. Backup then takes place in line with the protection group settings.
|
130 | 128 |
|
131 |
| -## Monitor the operations |
| 129 | +## Monitor the SharePoint Farm backup operations |
132 | 130 |
|
133 | 131 | After the protection group creation is complete, the initial replication happens and MABS starts backing up and synchronizing the SharePoint data. MABS monitors the initial synchronization and subsequent backups. You can monitor the SharePoint data in a couple of ways:
|
134 | 132 |
|
135 | 133 | * Using default MABS monitoring, you can set up notifications for proactive monitoring by publishing alerts and configuring notifications. You can send notifications by e-mail for critical, warning, or informational alerts, and for the status of instantiated recoveries.
|
136 | 134 |
|
137 | 135 | * If you use Operations Manager, you can centrally publish alerts.
|
138 | 136 |
|
139 |
| -### Set up monitoring notifications |
| 137 | +### Configure monitoring notifications |
140 | 138 |
|
141 |
| -To set up monitoring notifications, follow these steps: |
| 139 | +To configure monitoring notifications, follow these steps: |
142 | 140 |
|
143 | 141 | 1. On the **MABS Administrator Console**, select **Monitoring** > **Action** > **Options**.
|
144 | 142 |
|
@@ -296,7 +294,7 @@ To change the front-end Web server that MABS uses to protect the farm, follow th
|
296 | 294 |
|
297 | 295 | 1. On *Server2*, at a command prompt, change the directory to `_MABS installation location_\bin\` and run **ConfigureSharepoint**.
|
298 | 296 |
|
299 |
| - For more information about ConfigureSharePoint, see [Configure backup](#configure-the-backup). |
| 297 | + For more information about ConfigureSharePoint, see [Configure backup](#configure-sharepoint-farm-backup). |
300 | 298 |
|
301 | 299 | 1. Select the protection group that the server farm belongs to, and then select **Modify protection group**.
|
302 | 300 |
|
|
0 commit comments