--- title: "Managed Backup for VMware - Understanding your billing" description: "Find out how the price of a protected virtual machine is calculated with Managed Backup for VMware and how to read the Billing tab of your dashboard" url: https://docs.ovhcloud.com/de/guides/storage-and-backup/managed-backup-for-vmware/billing lang: en lastUpdated: 2026-11-03 --- > For AI agents: the complete documentation index is available at https://docs.ovhcloud.com/de/llms.txt, the full documentation bundle is available at https://docs.ovhcloud.com/de/llms-full.txt. # Managed Backup for VMware - Understanding your billing ## Objective Managed Backup for VMware is billed per protected virtual machine and per billing period, storage included. The price depends on only two things: the Backup plan of the machine and the size of its backup. **This guide explains how the price of a machine is calculated, and how to read your Billing tab.** ## Requirements - Have a Managed Backup for VMware service. *** ### OVHcloud Console Access - **Direct link:** "Managed Backup for VMware" - **Navigation path:** "Private Cloud" > "Backup" > "Managed Backup for VMware" *** ## Instructions ### The principle: one price per machine and per billing period - **Only protected machines are billed:** a machine without a tag is never billed. - **Storage is included:** there is no per-gigabyte line, either for retention or for the copy on the secondary site. - **Each infrastructure is billed separately**, with no grouping or volume discount across your infrastructures. ### The price grid Price per protected virtual machine and per billing period, storage included, in euros excl. VAT: | Size band | Standard | Advanced | Premium | | ------------- | -------: | -------: | ------: | | Up to 250 GB | €9.99 | €14.99 | €20.99 | | 250 GB - 1 TB | €15.99 | €36.99 | €60.99 | | 1 - 2 TB | €24.99 | €64.99 | €112.99 | | 2 - 4 TB | €39.99 | €120.99 | €215.99 | | 4 - 6 TB | €55.99 | €176.99 | €318.99 | | 6 - 8 TB | €70.99 | €232.99 | €422.99 | - **A machine exactly on a limit goes into the higher band:** a machine of exactly 250 GB is in the 250 GB - 1 TB band. - **Machines of 8 TB or more** are not supported: they have no price band. A machine of this size can delay the backups of your other machines. Do not tag it (see [Machines of 8 TB or more](https://docs.ovhcloud.com/de/guides/storage-and-backup/managed-backup-for-vmware/tag-vm.md#virtual-machines-of-8-tb-or-more)). ### Which size is taken into account The band is calculated on the **size of the backup of the machine**, never on the space allocated to its disks. **Tip:** **Key point** A machine whose allocated disks are very large, but whose backup stays small, is billed on the size of its backup, not on the allocated space. The size is measured every day a backup produces a restore point. If the backup of the machine grows, its band can change. ### What is billed over a period Consumption is measured every day and billed once per billing period. A billing period runs from the 28th of the previous month to the 27th of the current month. - **A machine is billed for the period** if at least one backup produced a restore point during that period. A machine whose backups all failed during the period is not billed. - **There is no proration:** a machine that is billed is billed for the whole period. - **The highest plan reached is used:** if a machine was Premium for even one day, the period is billed as Premium. - **The largest band reached is used,** whatever the plan: a machine that grew one day, then shrank, is billed at the largest band. | Situation during the period | What is billed | | --------------------------------------------------------------- | --------------------------------------------------------------- | | Machine on Standard, moved to Premium on the 15th | The whole period as Premium | | Machine on Premium, moved back to Standard on the 10th | The whole period as Premium, then Standard the following period | | Machine of 900 GB that grew to 1.2 TB, then went back to 900 GB | The whole period in the 1 - 2 TB band | | Machine tagged on the 20th | Billed for the period, from its first restore point | | Tag removed on the 5th | Billed for the current period, nothing afterwards | | Machine tagged, but no successful backup | Nothing | | Machine without a tag | Nothing | ### The Billing tab The `Billing ` tab of your dashboard lists the machines billed during the current period, with their price. _The "Billing" tab lists the machines billed during the period, with their infrastructure, their Backup plan and their price._ - **One row per billed machine,** with the **Name**, **Infrastructure**, **Backup plan** and **Price** (excluding VAT) columns. The price takes into account the highest plan and the largest size band reached since the start of the period. To see the band of a machine, open its details in the "Dashboard" tab (**Size band**). - **A machine that had no Backup plan during the period is not listed.** A machine whose tag was removed during the period is still listed, since the period is billed for it. - **The Search field** looks up a machine by name. The tab does not show a total. - **The** "Refresh" **button** reloads the list. It does not speed up the consumption measurement, which is daily. - **An empty list** means that no machine is billed during the period: it is not an error. ### The estimate shown at order time At order time, the summary shows an estimate per Backup plan and a total per billing period. This is a **maximum amount** for a full period, calculated on the machines you selected. The actual amount then depends on the machines you tag or untag. ### In case of termination Terminating does not reduce the current period: each machine backed up during this period, before the termination, is billed for the whole period, as there is no proration. Nothing is added afterwards, since no backup runs during the 35-day window. If the service is reactivated, each machine backed up after the reactivation is billed for the whole period, even if the reactivation happens partway through it. A machine is never billed twice for the same period (see [Terminating and reactivating a service](https://docs.ovhcloud.com/de/guides/storage-and-backup/managed-backup-for-vmware/terminate.md)). ### Disputing a line A line that has already been billed is never reduced automatically. If you think a machine was billed in error, contact support, who will consider a commercial correction. ## Go further [Protecting your virtual machines](https://docs.ovhcloud.com/de/guides/storage-and-backup/managed-backup-for-vmware/tag-vm.md): what makes a machine billable. [Terminating and reactivating a service](https://docs.ovhcloud.com/de/guides/storage-and-backup/managed-backup-for-vmware/terminate.md): what happens to your invoice. [FAQ and troubleshooting](https://docs.ovhcloud.com/de/guides/storage-and-backup/managed-backup-for-vmware/faq.md): frequent billing questions. Join our [community of users](https://community.ovhcloud.com/).