This article describes the improvements that are included and the issues that are fixed in the January 2016 update for Microsoft Azure Backup.
Improvements that are includedAzure Backup currently terminates backup after a single file failure. With this update, Azure Backup continues to back up even after some file or folder backups fail. After Azure Backup is completed successfully, it provides a warning message that lists the files that were not backed up during the backup process.
Issues that are fixed
- After every cloud modification in a DPM to Azure (DPM-A) backup installation, the first cloud recovery point is not retained.
- In some scenarios, Azure Backup fails with one of the following error messages:The following file that is essential for backup is missing: NO_PARAM. (0x7F26)An unexpected error occurred during the operation. Retry the operation (0x07EF9)
Update informationTo apply this update, install the latest version of the Microsoft Azure Recovery Services agent.
The following file is available for download from the Microsoft Download Center:
Note The latest version of the Microsoft Azure Recovery Services agent is 2.0.9028.0.
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online servicesMicrosoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Restart informationYou may have to restart the computer after you apply this update.
Replacement informationThis update replaces the previously released update 3109750 .
PrerequisitesIf you use System Center 2012 R2 Data Protection Manager (DPM), apply Update Rollup 6 for System Center 2012 R2 Data Protection Manager or a later version after you install this update for the Azure Backup agent.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 3139300 - Last Review: 10 Feb 2016 - Revision: 1