You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/backup/backup-mabs-release-notes-v3.md
+21-2Lines changed: 21 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Release notes for Microsoft Azure Backup Server v3
3
3
description: This article provides the information about the known issues and workarounds for Microsoft Azure Backup Server (MABS) v3.
4
4
ms.topic: conceptual
5
-
ms.date: 11/07/2023
5
+
ms.date: 12/04/2023
6
6
ms.asset: 0c4127f2-d936-48ef-b430-a9198e425d81
7
7
author: AbhishekMallick-MS
8
8
ms.author: v-abhmallick
@@ -12,10 +12,29 @@ ms.author: v-abhmallick
12
12
13
13
This article provides the known issues and workarounds for Microsoft Azure Backup Server (MABS) V3.
14
14
15
-
## MABS V4 UR1 known issues and workarounds
15
+
## MABS V4 UR1 Refresh known issues and workarounds
16
16
17
17
No known issues.
18
18
19
+
20
+
21
+
## MABS V4 UR1 known issues and workarounds
22
+
23
+
Microsoft is recalling the release of Update Rollup 1 for Microsoft Azure Backup Server V4 due to the following known issues:
24
+
25
+
- Hyper-V scheduled backups take a long time to complete because each backup job triggers a consistency check.
26
+
27
+
**Error Message**: The replica of Microsoft Hyper-V RCT on `<Machine Name>` is not consistent with the protected data source. MABS has detected changes in file locations or volume configurations of protected objects since the data source was configured for protection. (ID 30135)
28
+
29
+
- MABS console occasionally crashes when SMTP alerts or reports are configured.
30
+
31
+
The updated build **Update Rollup 1 Refresh for MABS V4** is released that fixes these known issues.
32
+
33
+
>[!Important]
34
+
>If you had installed Update Rollup 1 for MABS V4 (14.0.42.0), we recommend that you install **Update Rollup1 Refresh (14.0.46.0)** on your MABS server and update the protection agents from *KB 5033756*.
35
+
>
36
+
>For any queries or additional information, contact **Microsoft Support**.
37
+
19
38
## MABS V4 known issues and workarounds
20
39
21
40
If you're protecting Windows Server 2012 and 2012 R2, you need to install Visual C++ redistributable 2015 manually on the protected server. You can download [Visual C++ Redistributable for Visual Studio 2015 from Official Microsoft Download Center](https://www.microsoft.com/en-in/download/details.aspx?id=48145).
Copy file name to clipboardExpand all lines: articles/backup/backup-mabs-whats-new-mabs.md
+19-3Lines changed: 19 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: What's new in Microsoft Azure Backup Server
3
3
description: Microsoft Azure Backup Server gives you enhanced backup capabilities for protecting VMs, files and folders, workloads, and more.
4
4
ms.service: backup
5
5
ms.topic: conceptual
6
-
ms.date: 11/23/2023
6
+
ms.date: 12/04/2023
7
7
author: AbhishekMallick-MS
8
8
ms.author: v-abhmallick
9
9
---
@@ -12,7 +12,23 @@ ms.author: v-abhmallick
12
12
13
13
Microsoft Azure Backup Server gives you enhanced backup capabilities to protect VMs, files and folders, workloads, and more.
14
14
15
+
## What's new in MABS V4 Update Rollup 1 Refresh (UR1 Refresh)?
15
16
17
+
Microsoft Azure Backup Server version 4 (MABS V4) Update *Rollup 1 Refresh* includes critical bug fixes and feature enhancements. For information about the bugs fixed and the installation instructions of MABS V4 UR1 Refresh, see [KB article 5033756](https://support.microsoft.com/home/contact?SourceApp=smcivr2).
18
+
19
+
>[!Important]
20
+
>MABS V4 UR1 Refresh supersedes MABS V4 UR1 that has the same feature enhancements, but fixes the known issues in MABS V4 UR1. [Learn more](backup-mabs-release-notes-v3.md).
21
+
22
+
The following table lists the new features added in MABS V4 UR1:
23
+
24
+
| Feature | Supportability |
25
+
| --- | --- |
26
+
| Item-level recovery for VMware VMs running Windows directly from online recovery points. | Use MARS version *2.0.9251.0* or above for this feature. |
27
+
| Windows and Basic SMTP Authentication for MABS email reports and alerts. | This enables MABS to send reports and alerts using any vendor supporting SMTP Basic Authentication. [Learn more](/system-center/dpm/monitor-dpm?view=sc-dpm-2022&preserve-view=true#configure-email-for-dpm). <br><br> Note that if you're using Microsoft 365 SMTP with a MABS V4 private fix, re-enter the credential using Basic Authentication. |
28
+
| Fall back to crash-consistent backups for VMware VMs. | Use a registry key for VMware VMs when backups fail with ApplicationQuiesceFault. [Learn more](backup-azure-backup-server-vmware.md#applicationquiescefault). |
29
+
| Experience improvements for MABS backups to Azure. ||
30
+
| List online recovery points for a data source along with the expiry time and soft-delete status. | To view the list of recovery points along with their expiration dates, right-click a data source and select **List recovery points**. |
31
+
| Stop protection and retaining data using the policy duration for immutable vaults directly from the console. | This helps you save the backup costs when stopping protection for a data source backed up to an immutable vault. [Learn more](backup-azure-security-feature.md#immutability-support).
16
32
17
33
## What's new in MABS V4 Update Rollup 1 (UR1)?
18
34
@@ -35,7 +51,7 @@ The following table lists the new features added in MABS V4 UR1:
35
51
| Feature | Supportability |
36
52
| --- | --- |
37
53
| Item-level recovery for VMware VMs running Windows directly from online recovery points. | Note that you need *MARS version 2.0.9251.0 or above* to use this feature. |
38
-
| Windows and Basic SMTP Authentication for MABS email reports and alerts. | This enables MABS to send reports and alerts using any vendor supporting SMTP Basic Authentication. [Learn more](/system-center/dpm/monitor-dpm?view=sc-dpm-2022&preserve-view=true#configure-email-for-dpm). <br><br> Note that if you are using Microsoft 365 SMTP with a MABS V4 private fix, reenter the credential using Basic Authentication. |
54
+
| Windows and Basic SMTP Authentication for MABS email reports and alerts. | This enables MABS to send reports and alerts using any vendor supporting SMTP Basic Authentication. [Learn more](/system-center/dpm/monitor-dpm?view=sc-dpm-2022&preserve-view=true#configure-email-for-dpm). <br><br> Note that if you are using Microsoft 365 SMTP with a MABS V4 private fix, re-enter the credential using Basic Authentication. |
39
55
| Fall back to crash consistent backups for VMware VMs. | Use a registry key for VMware VMs when backups fail with ApplicationQuiesceFault. [Learn more](backup-azure-backup-server-vmware.md#applicationquiescefault). |
40
56
|**Experience improvements for MABS backups to Azure.**||
41
57
| List online recovery points for a data source along with the expiry time and soft-delete status. | To view the list of recovery points along with their expiration dates, right-click a data source and select **List recovery points**. |
@@ -143,7 +159,7 @@ MABS V3 UR1 includes a new parameter **[-CheckReplicaFragmentation]**. The new p
143
159
144
160
### 32-Bit protection agent deprecation
145
161
146
-
With MABS v3 UR1, support for 32-bit protection agent is no longer supported. You won't be able to protect 32-bit workloads after upgrading the MABS v3 server to UR1. Any existing 32-bit protection agents will be in a disabled state and scheduled backups will fail with the **agent is disabled** error. If you want to retain backup data for these agents, you can stop the protection with the retain data option. Otherwise, the protection agent can be removed.
162
+
With MABS v3 UR1, support for 32-bit protection agent is no longer supported. You won't be able to protect 32-bit workloads after upgrading the MABS v3 server to UR1. Any existing 32-bit protection agents will be in a disabled state and scheduled backups will fail with the **agent is disabled** error. If you want to retain the backup data for these agents, you can stop the protection with the retained data option. Otherwise, the protection agent can be removed.
147
163
148
164
>[!NOTE]
149
165
>Review the [updated protection matrix](./backup-mabs-protection-matrix.md) to learn the supported workloads for protection with MABS UR 1.
0 commit comments