Skip to content

Commit 0641c6a

Browse files
author
AbhishekMallick-MS
committed
Freshness - Azure Stack backup
1 parent 47fb0dc commit 0641c6a

File tree

1 file changed

+20
-20
lines changed

1 file changed

+20
-20
lines changed

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

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Back up a SharePoint farm on Azure Stack
2+
title: Back up a SharePoint farm on Azure Stack by using Azure Backup
33
description: Use Azure Backup Server to back up and restore your SharePoint data on Azure Stack. 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.
44
ms.topic: how-to
5-
ms.date: 03/02/2023
5+
ms.date: 03/15/2024
66
ms.service: backup
7-
ms.custom: engagement-fy23
7+
ms.custom: engagement-fy24
88
author: AbhishekMallick-MS
99
ms.author: v-abhmallick
1010
---
@@ -34,11 +34,19 @@ Azure Backup for MABS supports the following scenarios:
3434

3535
* MABS doesn't provide backup of SharePoint SQL Server databases that are hosted on scale-out file server (SOFS) shares.
3636

37+
### Limitations
38+
39+
* You can't protect SharePoint databases as a SQL Server data source. You can recover individual databases from a farm backup.
40+
41+
* Protecting application store items isn't supported with SharePoint 2013.
42+
43+
* MABS doesn't support protecting remote FILESTREAM. The FILESTREAM should be part of the database.
44+
3745
## Prerequisites
3846

3947
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 in prerequisites also include: create a backup vault, download vault credentials, install Azure Backup Agent, and register the Azure Backup Server with the vault.
4048

41-
Additional prerequisites and limitations:
49+
### Additional prerequisites
4250

4351
* By default when you protect SharePoint, all content databases (and the SharePoint_Config and SharePoint_AdminContent* databases) are protected.
4452

@@ -52,14 +60,6 @@ Additional prerequisites and limitations:
5260

5361
* In the SharePoint farm, if you have 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.
5462

55-
### Limitations
56-
57-
* You can't protect SharePoint databases as a SQL Server data source. You can recover individual databases from a farm backup.
58-
59-
* Protecting application store items isn't supported with SharePoint 2013.
60-
61-
* MABS doesn't support protecting remote FILESTREAM. The FILESTREAM should be part of the database.
62-
6363
## Configure backup
6464

6565
To back up the SharePoint farm, configure protection for SharePoint by using ConfigureSharePoint.exe, and then create a protection group in MABS.
@@ -96,11 +96,11 @@ Follow these steps:
9696

9797
1. In **Select Group Members**, expand the server that holds the WFE role.
9898

99-
If there's more than one WFE server, select the one on which you installed *ConfigureSharePoint.exe*.
99+
If there are more than one WFE servers, select the one on which you installed *ConfigureSharePoint.exe*.
100100

101101
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.
102102

103-
1. In **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\).
103+
1. In **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\).
104104

105105
1. In **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.
106106

@@ -252,35 +252,35 @@ To recover a SharePoint content database, follow these steps:
252252

253253
If you have more than one front-end web server, and want to switch the server that MABS uses to protect the farm, follow the instructions:
254254

255-
The following procedure uses the example of a server farm with two front-end Web servers, *Server1* and *Server2*. MABS uses *Server1* to protect the farm. Change the front-end Web server that MABS uses to *Server2* so that you can remove *Server1* from the farm.
255+
The following procedure uses the example of a server farm with two front-end Web servers, `Server1` and `Server2`. MABS uses `Server1` to protect the farm. Change the front-end Web server that MABS uses to `Server2` so that you can remove `Server1` from the farm.
256256

257257
> [!NOTE]
258258
> If the front-end Web server that MABS uses to protect the farm is unavailable, use the following procedure to change the front-end Web server by starting at step 4.
259259
260260
### Change the front-end Web server that MABS uses to protect the farm
261261

262-
1. Stop the SharePoint VSS Writer service on *Server1* by running the following command at a command prompt:
262+
1. Stop the SharePoint VSS Writer service on `Server1` by running the following command at a command prompt:
263263

264264
```CMD
265265
stsadm -o unregisterwsswriter
266266
```
267267
268-
1. On *Server1*, open the Registry Editor and navigate to the following key:
268+
1. On `Server1`, open the Registry Editor and navigate to the following key:
269269
270270
**HKLM\System\CCS\Services\VSS\VssAccessControl**
271271
272272
1. Check all values listed in the VssAccessControl subkey. If any entry has a value data of 0 and another VSS writer is running under the associated account credentials, change the value data to 1.
273273
274-
1. Install a protection agent on *Server2*.
274+
1. Install a protection agent on `Server2`.
275275
276276
> [!WARNING]
277277
> You can only switch Web front-end servers if both the servers are on the same domain.
278278
279-
1. On *Server2*, at a command prompt, change the directory to `_MABS installation location_\bin\` and run **ConfigureSharepoint**. For more information about ConfigureSharePoint, see [Configure backup](#configure-backup).
279+
1. On `Server2`, at a command prompt, change the directory to `_MABS installation location_\bin\` and run **ConfigureSharepoint**. For more information about ConfigureSharePoint, see [Configure backup](#configure-backup).
280280
281281
1. Select the protection group that the server farm belongs to, and then select **Modify protection group**.
282282
283-
1. On the Modify Group Wizard, on the **Select Group Members** page, expand *Server2* and select the server farm, and then complete the wizard.
283+
1. On the Modify Group Wizard, on the **Select Group Members** page, expand `Server`* and select the server farm, and then complete the wizard.
284284
285285
A consistency check will start.
286286

0 commit comments

Comments
 (0)