Skip to content

Commit 9b4429e

Browse files
author
AbhishekMallick01
committed
more updates
1 parent 7789350 commit 9b4429e

7 files changed

+80
-51
lines changed

articles/azure-vmware/set-up-backup-server-for-azure-vmware-solution.md

Lines changed: 22 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Set up Azure Backup Server for Azure VMware Solution
33
description: Set up your Azure VMware Solution environment to back up virtual machines using Azure Backup Server.
44
ms.topic: how-to
55
ms.service: azure-vmware
6-
ms.date: 08/23/2022
6+
ms.date: 03/01/2023
77
---
88

99
# Set up Azure Backup Server for Azure VMware Solution
@@ -27,18 +27,18 @@ This article helps you prepare your Azure VMware Solution environment to back up
2727
2828
## Supported VMware features
2929

30-
- **Agentless backup:** Azure Backup Server doesn't require an agent to be installed on the vCenter Server or ESXi server to back up the VM. Instead, provide the IP address or fully qualified domain name (FQDN) and the sign in credentials used to authenticate the VMware vCenter Server with Azure Backup Server.
30+
- **Agentless backup:** Azure Backup Server doesn't require an agent to be installed on the vCenter Server or ESXi server to back up the VM. Instead, provide the IP address or fully qualified domain name (FQDN) and the sign-in credentials used to authenticate the VMware vCenter Server with Azure Backup Server.
3131
- **Cloud-integrated backup:** Azure Backup Server protects workloads to disk and the cloud. The backup and recovery workflow of Azure Backup Server helps you manage long-term retention and offsite backup.
3232
- **Detect and protect VMs managed by vCenter Server:** Azure Backup Server detects and protects VMs deployed on a vCenter Server or ESXi hosts. Azure Backup Server also detects VMs managed by vCenter Server so that you can protect large deployments.
33-
- **Folder-level auto protection:** vCenter Server lets you organize your VMs into Virtual Machine folders. Azure Backup Server detects these folders. You can use it to protect VMs at the folder level, including all subfolders. When protecting folders, Azure Backup Server protects the VMs in that folder and protects VMs added later. Azure Backup Server detects new VMs daily, protecting them automatically. As you organize your VMs in recursive folders, Azure Backup Server automatically detects and protects the new VMs deployed in the recursive folders.
33+
- **Folder-level auto protection:** vCenter Server lets you organize your VMs into Virtual Machine folders. Azure Backup Server detects these folders. You can use it to protect VMs at the folder level, including all subfolders. During the protection of folders, Azure Backup Server protects the VMs in that folder and protects VMs added later. Azure Backup Server detects new VMs daily, protecting them automatically. As you organize your VMs in recursive folders, Azure Backup Server automatically detects and protects the new VMs deployed in the recursive folders.
3434
- **Azure Backup Server continues to protect vMotioned VMs within the cluster:** As VMs are vMotioned for dynamic resource load balancing within the cluster, Azure Backup Server automatically detects and continues VM protection.
3535
- **Recover necessary files faster:** Azure Backup Server can recover files or folders from a Windows VM without recovering the entire VM.
36-
- **Application Consistent Backups:** If VMware Tools is not installed, a crash consistent backup will be executed. When VMware Tools is installed with Microsoft Windows virtual machines, all applications that support VSS freeze and thaw operations will support application consistent backups. When VMware Tools is installed with Linux virtual machines, application consistent snapshots are supported by calling the pre and post scripts.
36+
- **Application Consistent Backups:** If the *VMware Tools* isn't installed, a crash consistent backup will be executed. When the *VMware Tools* is installed with Microsoft Windows virtual machines, all applications that support VSS freeze and thaw operations will support application consistent backups. When the *VMware Tools* is installed with Linux virtual machines, application consistent snapshots are supported by calling the pre and post scripts.
3737

3838
## Limitations
3939

40-
- Update Rollup 1 for Azure Backup Server v3 must be installed.
41-
- You can't backup user snapshots before the first Azure Backup Server backup. After Azure Backup Server finishes the first backup, then you can back up user snapshots.
40+
- • If you're using *Azure Backup Server V3*, then you must install [Update Rollup 2](https://support.microsoft.com/topic/update-rollup-2-for-microsoft-azure-backup-server-v3-350de164-0ae4-459a-8acf-7777dbb7fd73). New installations from the Azure portal now use *Azure Backup Server V4* that supports vSphere, version *6.5* to *8.0*.
41+
- You can't back up user snapshots before the first Azure Backup Server backup. After Azure Backup Server finishes the first backup, then you can back up user snapshots.
4242
- Azure Backup Server can't protect VMware vSphere VMs with pass-through disks and physical raw device mappings (pRDMs).
4343
- Azure Backup Server can't detect or protect VMware vSphere vApps.
4444

@@ -53,7 +53,7 @@ To set up Azure Backup Server for Azure VMware Solution, you must finish the fol
5353

5454
Azure Backup Server is deployed as an Azure infrastructure as a service (IaaS) VM to protect Azure VMware Solution VMs.
5555

56-
:::image type="content" source="media/azure-vmware-solution-backup/deploy-backup-server-azure-vmware-solution-diagram.png" alt-text="Diagram showing Azure Backup Server deployed as an Azure infrastructure as a service (IaaS) VM to protect Azure VMware Solution VMs." border="false":::
56+
:::image type="content" source="media/azure-vmware-solution-backup/deploy-backup-server-azure-vmware-solution-diagram.png" alt-text="Diagram showing the Azure Backup Server deployed as an Azure infrastructure as a service (IaaS) VM to protect Azure VMware Solution VMs." border="false":::
5757

5858
## Prerequisites for the Azure Backup Server environment
5959

@@ -73,9 +73,9 @@ Follow the instructions in the [Create your first Windows VM in the Azure portal
7373
> Azure Backup Server is designed to run on a dedicated, single-purpose server. You can't install Azure Backup Server on a computer that:
7474
> * Runs as a domain controller.
7575
> * Has the Application Server role installed.
76-
> * Is a System Center Operations Manager management server.
76+
> * Is a System Center Operations Manager management server?
7777
> * Runs Exchange Server.
78-
> * Is a node of a cluster.
78+
> * Is a node of a cluster?
7979
8080
### Disks and storage
8181

@@ -113,7 +113,7 @@ If you want to scale your deployment, you have the following options:
113113

114114
### .NET Framework
115115

116-
The VM must have .NET Framework 3.5 SP1 or higher installed.
116+
The VM must have .NET Framework 4.5 or higher installed.
117117

118118
### Join a domain
119119

@@ -208,7 +208,7 @@ Follow the steps in this section to download, extract, and install the software
208208
> [!NOTE]
209209
> You must download all the files to the same folder. Because the download size of the files together is greater than 3 GB, it might take up to 60 minutes for the download to complete.
210210
211-
:::image type="content" source="../backup/media/backup-azure-microsoft-azure-backup/downloadcenter.png" alt-text="Screenshot showing Microsoft Azure Backup files to download.":::
211+
:::image type="content" source="../backup/media/backup-azure-microsoft-azure-backup/downloadcenter.png" alt-text="Screenshot showing the Microsoft Azure Backup files to download.":::
212212

213213
### Extract the software package
214214

@@ -223,7 +223,7 @@ If you downloaded the software package to a different server, copy the files to
223223

224224
1. Select **Extract** to begin the extraction process.
225225

226-
:::image type="content" source="../backup/media/backup-azure-microsoft-azure-backup/extract/03.png" alt-text="Screenshot showing Microsoft Azure Backup files ready to extract.":::
226+
:::image type="content" source="../backup/media/backup-azure-microsoft-azure-backup/extract/03.png" alt-text="Screenshot showing the Microsoft Azure Backup files ready to extract.":::
227227

228228
1. Once extracted, select the option to **Execute setup.exe** and then select **Finish**.
229229

@@ -232,7 +232,7 @@ If you downloaded the software package to a different server, copy the files to
232232
233233
### Install the software package
234234

235-
1. On the setup window under **Install**, select **Microsoft Azure Backup** to open the setup wizard.
235+
1. On the setup window under **Install**, select **Microsoft Azure Backup** to open the setup wizard and accept any licensing terms from the list that appears.
236236

237237
1. On the **Welcome** screen, select **Next** to continue to the **Prerequisite Checks** page.
238238

@@ -251,9 +251,9 @@ If you downloaded the software package to a different server, copy the files to
251251

252252
When you use your own SQL Server instance, make sure you add builtin\Administrators to the sysadmin role to the main database sysadmin role.
253253

254-
**Configure reporting services with SQL Server 2017**
254+
**Configure reporting services with SQL Server 2019 or 2022**
255255

256-
If you use your instance of SQL Server 2017, you must configure SQL Server 2017 Reporting Services (SSRS) manually. After configuring SSRS, make sure to set the **IsInitialized** property of SSRS to **True**. When set to **True**, Azure Backup Server assumes that SSRS is already configured and skips the SSRS configuration.
256+
If you use your instance of SQL Server, you must configure SQL Server Reporting Services (SSRS) manually. After configuring SSRS, make sure to set the **IsInitialized** property of SSRS to **True**. When set to **True**, Azure Backup Server assumes that SSRS is already configured and skips the SSRS configuration.
257257

258258
To check the SSRS configuration status, run:
259259

@@ -316,10 +316,6 @@ If you downloaded the software package to a different server, copy the files to
316316

317317
1. After the installation step finishes, select **Close**.
318318

319-
### Install Update Rollup 1
320-
321-
Installing the Update Rollup 1 for Azure Backup Server v3 is mandatory before you can protect the workloads. You can find the bug fixes and installation instructions in the [knowledge base article](https://support.microsoft.com/en-us/help/4534062/).
322-
323319
## Add storage to Azure Backup Server
324320

325321
Azure Backup Server v3 supports Modern Backup Storage that offers:
@@ -333,7 +329,7 @@ Azure Backup Server v3 supports Modern Backup Storage that offers:
333329

334330
Add the data disks with the Azure Backup Server VM's required storage capacity if not already added.
335331

336-
Azure Backup Server v3 only accepts storage volumes. When you add a volume, Azure Backup Server formats the volume to Resilient File System (ReFS), which Modern Backup Storage requires.
332+
Azure Backup Server only accepts storage volumes. When you add a volume, Azure Backup Server formats the volume to Resilient File System (ReFS), which Modern Backup Storage requires.
337333

338334
### Add volumes to Azure Backup Server disk storage
339335

@@ -345,6 +341,12 @@ Azure Backup Server v3 only accepts storage volumes. When you add a volume, Azur
345341

346342
1. Select **OK** to format these volumes to ReFS so that Azure Backup Server can use Modern Backup Storage benefits.
347343

344+
## Upgrade to Azure Backup Server V4 from Azure Backup Server V3
345+
346+
If you're already using Azure Backup Server V3 to back up AVS VMs, you can [upgrade to Azure Backup Server V4](../backup/backup-azure-microsoft-azure-backup.md#upgrade-mabs) to get access to the latest features and bug fixes.
347+
348+
349+
348350
## Next steps
349351

350352
Now that you've covered how to set up Azure Backup Server for Azure VMware Solution, you can use the following resources to learn more.

articles/backup/backup-azure-backup-faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ sections:
134134
135135
For Azure VM Linux backups, Azure Backup supports [the list of distributions endorsed by Azure](../virtual-machines/linux/endorsed-distros.md), except Core OS Linux and 32-bit operating system. Other bring-your-own Linux distributions might work as long as the VM agent is available on the VM, and support for Python exists.
136136
137-
Learn more about the [latest workloads supported by DPM and MABS Server](backup-mabs-protection-matrix.md).
137+
Learn more about the latest workloads supported by [DPM](/system-center/dpm/dpm-protection-matrix?view=sc-dpm-2022) and [MABS Server](backup-mabs-protection-matrix.md).
138138
139139
- question: |
140140
Are there size limits for data backup?

articles/backup/backup-mabs-release-notes-v3.md

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Release notes for Microsoft Azure Backup Server v3
33
description: This article provides the information about the known issues and workarounds for Microsoft Azure Backup Server (MABS) v3.
44
ms.topic: conceptual
5-
ms.date: 07/27/2021
5+
ms.date: 03/01/2023
66
ms.asset: 0c4127f2-d936-48ef-b430-a9198e425d81
77
author: jyothisuri
88
ms.author: jsuri
@@ -12,7 +12,13 @@ ms.author: jsuri
1212

1313
This article provides the known issues and workarounds for Microsoft Azure Backup Server (MABS) V3.
1414

15-
## Backup and recovery fails for clustered workloads
15+
## MABS V4 known issues and workarounds
16+
17+
Currently, there are no known issues with MABS V4.
18+
19+
## MABS V3 known issues and workarounds
20+
21+
### Backup and recovery fails for clustered workloads
1622

1723
**Description:** Backup/restore fails for clustered data sources such as Hyper-V cluster or SQL cluster (SQL Always On) or Exchange in database availability group (DAG) after upgrading MABS V2 to MABS V3.
1824

@@ -45,7 +51,7 @@ This article provides the known issues and workarounds for Microsoft Azure Backu
4551
GO
4652
```
4753

48-
## Upgrade to MABS V3 fails in Russian locale
54+
### Upgrade to MABS V3 fails in Russian locale
4955

5056
**Description:** Upgrade from MABS V2 to MABS V3 in Russian locale fails with an error code **4387**.
5157

@@ -68,7 +74,7 @@ This article provides the known issues and workarounds for Microsoft Azure Backu
6874

6975
9. Start MSDPM service.
7076

71-
## After installing UR1 the MABS reports aren't updated with new RDL files
77+
### After installing UR1, the MABS reports aren't updated with new RDL files
7278

7379
**Description**: With UR1, the MABS report formatting issue is fixed with updated RDL files. The new RDL files aren't automatically replaced with existing files.
7480

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

Lines changed: 4 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Back up a SharePoint farm on Azure Stack
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: 10/20/2022
5+
ms.date: 03/02/2023
66
ms.service: backup
77
ms.custom: engagement-fy23
88
author: jyothisuri
@@ -15,28 +15,18 @@ This article describes how to back up and restore SharePoint data using Microsof
1515

1616
Microsoft Azure Backup Server (MABS) enables you to back up a SharePoint farm (on Azure Stack) 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.
1717

18-
In this article, you'll learn about:
19-
20-
> [!div class="checklist"]
21-
> - SharePoint supported scenarios
22-
> - Prerequisites
23-
> - Configure backup
24-
> - Monitor operations
25-
> - Restore a SharePoint item from disk by using MABS
26-
> - Restore a SharePoint database from Azure by using MABS
27-
> - Switch the Front-End Web Server
2818

2919
## SharePoint supported scenarios
3020

31-
You need to confirm the following supported scenarios before you back up a SharePoint farm to Azure.
21+
You need to confirm the supported scenarios before you back up a SharePoint farm to Azure from the [support matrix](backup-mabs-protection-matrix.md).
3222

3323
### Supported scenarios
3424

3525
Azure Backup for MABS supports the following scenarios:
3626

3727
| Workload | Version | SharePoint deployment | Protection and recovery |
3828
| --- | --- | --- | --- |
39-
| SharePoint |SharePoint 2016, SharePoint 2013, SharePoint 2010 |SharePoint deployed as an Azure Stack virtual machine <br> -------------- <br> SQL Always On | Protect SharePoint Farm recovery options: Recovery farm, database, and file or list item from disk recovery points. Farm and database recovery from Azure recovery points. |
29+
| SharePoint |SharePoint 2019, SharePoint 2016 with latest SPs |SharePoint deployed as an Azure Stack virtual machine <br> -------------- <br> SQL Always On | Protect SharePoint Farm recovery options: Recovery farm, database, and file or list item from disk recovery points. Farm and database recovery from Azure recovery points. |
4030

4131
### Unsupported scenarios
4232

@@ -106,7 +96,7 @@ Follow these steps:
10696

10797
1. In **Select Group Members**, expand the server that holds the WFE role.
10898

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

111101
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.
112102

0 commit comments

Comments
 (0)