MABS console crashes when attempting restore with throttling on clustered VMs.īackup fails due to the error: replica couldn’t be mounted or unmounted due to open handle on the replica.Ĭreate online replica now option doesn't work in offline seeding process. MABS Management console might crash when navigating to alerts in Monitoring tab or when the job information is getting updated on Recovery wizard. Modify Protection Group operation might take longer, while protecting large number of client machines in a single protection group.Ĭonsistency check for deduped enabled NTFS volumes fails with error: ID 30134 and a message Cannot create a file when that file already exists (0x800700B7). Restore of Windows Server 2016 NTFS deduped volumes with MABS v3 running on Windows Server 2019 results in corrupted files. Hyper-V VM protection fails when the total size of the VM file name and MABS mount path is more than 256 characters.
ULTIMATE BACKUP V.2.0 FULL
See Issue 2 in More information section for additional details.Įxpress full backup schedule in the UI getting changed to default value, if retention range in Modify Protection group changes. SharePoint backup fails when SQL server is in a different domain than the front-end SharePoint server. MABS crashes when attempting OLR, if the protected server does not have DPMRA (DPM agent) installed. Hyper-V backups fail intermittently due to issues with agent communication on MABS. In SQL Always On configuration with a Failover cluster backup, sometimes the backups might fail because the backup preferences are not honored. In some scenarios, re-protecting an inactive workload re-calculates the required disk space to be excessively large. See Issue 1 in More information section for additional details.ĭisk Utilization report was not reflecting Modern Backup Storage usage. Registry key added to the protected server to extend the timeout.
Issues that are fixedĪ stale file entry in the ActiveOwner folder breaks VMware protection.īare metal backups running longer than 24 hours will time out.
If the latest agent is not installed, online backups may fail, and no Microsoft Azure Backup Server to Microsoft Azure operation will work.
ULTIMATE BACKUP V.2.0 UPDATE
This article describes the issues that are fixed in Update Rollup 2 for Microsoft Azure Backup Server v3. This article also contains the installation instructions for this update.Įxisting Azure Backup Server customers should upgrade to the latest Microsoft Azure Recovery Services (MARS) agent (version or a later version).
0 kommentar(er)
