What if I start protecting a machine to Azure in the middle of the month – will I still have to pay the full protected instance price?
No, usage is prorated based on the number of days in a month that an instance has been protected.
Related questions and answers
The total amount of backup data held in Azure Backup (the “backend size”) for a specific Protected Instance can change due to the following factors:
- Retention period of the backed-up data
- Net new churn stored in each recovery point
- Level of compression achieved on the backup data
- Frequency of the scheduled backup jobs
- Any associated backup metadata
A protected instance refers to the computer, physical or virtual server you use to configure the backup to Azure. An instance is protected once you configure a backup policy for the computer, server, or database, and create a backup copy of the data. Subsequent copies of the backup data change the amount of storage consumed, but additional backup copies don’t add to the number of protected instances. Some common examples of protected instances are virtual machines, application servers, and personal computers running the Windows operating system. For example:
- A virtual machine running the Hyper-V or Azure IaaS hypervisor fabric. The guest operating systems for these virtual machines can be Windows Server or Linux.
- An application server with physical or a virtual machine running Windows Server and workloads with data to backup. Common workloads are Microsoft SQL Server, Microsoft Exchange server, Microsoft SharePoint server, Microsoft Dynamics, and the File Server role on Windows Server. To back-up or protect these workloads, you’ll need Azure Backup Server or System Center Data Protection Manager, DPM.
- A personal computer running the Windows operating system.
- SQL Server which includes all databases on the server. If you choose to backup a virtual machine hypervisor fabric and its guest workload, the hypervisor fabric and the guest workload are treated as separate protected instances and are charged independently.
All data stored with Azure Backup is billed per the backup storage rates listed above.
No, from a billing perspective, instances are classified into three categories based on the size of the instance. The price per protected instance depends on the categorization of the instance in the pricing table above. Note that the prices in the above table do not include Storage which is a separate charge.
This depends on the storage choice selected for the backup vault. The choice of storage for the backup vault are: Locally Redundant Storage (LRS) or Geo-Redundant Storage (GRS).
Yes. The backup data in each vault will be billed at the appropriate LRS or GRS Block Blob rates for the region where the vault is located. The customer has complete control of the Azure storage bill with the vault choices that are picked.