About this update
When you use Microsoft Azure Backup to back up data, the size of the primary data source is currently not sent to the service. The new Protected Instances pricing model needs this information for accurate billing. If there is no primary data source size information, the billing will be based on the total backup data that is stored in the service. For more information about the new pricing, check out the Azure Backup pricing page.
Resolution
After you install the update, the size information is sent to Azure Backup as a part of each backup. The Protected Instances that you are billed for will be based on the size information that was sent to Azure Backup.
Update information
This update (version 2.0.8704.0) is available for download from the Microsoft Download Center.
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 services Microsoft 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.
Prerequisites
To apply this update, you must have one of the following updates installed:
-
For System Center 2012 Data Protection Manager Service Pack 1: Update Rollup 7
-
For System Center 2012 R2 Data Protection Manager: Update Rollup 3
Restart information
You do not have to restart the computer after you apply this update.
Replacement information
This update replaces the following updates:
-
Offline disk shipment and increases the number of backup copies
-
A backup to Azure Backup fails if the data source is larger than 850 GB
-
Update for Azure Backup for Microsoft Azure Recovery Services Agent
-
Azure Backup Agent cannot be installed on Windows Server 2008
-
Azure Backup now supports 64-bit editions of Windows client operating systems
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
Learn about the terminology that Microsoft uses to describe software updates.
