Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

Comparing backup quotes: protected data, stored data and the retention included

Technical article
Backup & Recovery

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

To compare backup quotes, convert each one into the same unit: the monthly cost per GB of protected data, for the same retention, with every extra charge counted. Quotes differ because they charge on different things. Some charge per machine, some on the size of the data protected, and some on the space the backups occupy. A rate that looks lower can cost more once you apply it to the right size.

Protected size means the used data on the servers you back up. Stored size means the space the backups occupy at the provider. Stored size is larger than protected size whenever more than one point is kept, so the two cannot be compared directly. Every quote should say which one it charges on. If it does not, ask.

What can a backup quote charge on?

The published pricing of two large providers shows the common patterns. The wording is each provider's own, and no prices are quoted.

Charged on How a provider describes it What happens as you grow
Machine or instance, in size bands Azure Backup: a protected-instance charge in bands "plus storage consumed"; for instances over 500 GB, "for each 500 GB increment" Steps up as each band is crossed
Protected size Azure Backup: "The size of the backed-up data determines the pricing for Azure Backup in each protected instance before compression and encryption" Rises with the data on the server, not with retention
Stored size AWS Backup: storage billed "is based on the average storage space used throughout the month (billed as GB-Month)" Rises with protected size, change rate and retention
Separate storage charge Azure Backup: "Charges for storage are separate from the cost of Azure Backup Protected Instances" Both parts move

One quote can use more than one row. Azure's structure charges an instance part and a storage part, and its storage part has choices of redundancy: locally redundant, zone redundant or geo-redundant storage. A quote with one flat figure per terabyte does not show that split. Ask which of the four rows the figure follows.

Size is also defined differently from one provider to the next. For virtual machines Microsoft says the size "is the sum of all data in the VM, excluding temporary storage", and that pricing is "based on the actual data that's stored on the data disks, not on the maximum supported size for each data disk". A quote on provisioned disk size and a quote on used data size are not the same unit, even when both say "per TB".

What retention and copies does each quote include?

Retention changes stored size, and a quote can include it, price it by tier, or leave it open. Settle the following in writing for every quote before you compare a single rate.

Item What to ask Why it changes the comparison
Retention How many daily, weekly, monthly and yearly points are included? More points mean more stored data on stored-size quotes
How points are stored Is each point a full copy or only new data after the first? AWS says resources without incremental support store "a full copy" for each backup
Number of copies One copy, or copies in another site or region? Each copy is stored and may be charged separately
Restore charge Is restoring free, or charged per GB restored? AWS bills "the amount of data restored for the month"; Microsoft says restoring from its Standard tier "is free of charge"
Copying or moving data out Is transfer between regions or out of the provider charged? AWS lists "backup data transferred between AWS Regions"
Minimum terms Is there a minimum storage period on cold or archive data? AWS cold storage has a 90-day minimum; Azure Archive has an early deletion period of 180 days
Small objects Is there a minimum billable size per object? AWS prices S3 backups of objects under 128 KB "as a 128-KB backup"
Stopping Is data billed after protection stops? Microsoft says billing "continues as long as any backup data for the VM is stored in a vault"

The second line is the one buyers skip. Two quotes may state the same retention of 30 days and still store very different amounts. A quote that stores full copies carries 30 times the protected size at 30 days. A quote that stores only new data carries the protected size plus 29 days of change, because the oldest point holds the full copy.

How do I put two quotes on one unit?

Work out one figure per quote: the monthly cost for 1 GB of protected data, with the retention you need.

For a quote on protected size, that is the rate itself, plus any per-machine or restore charge divided across the protected GB.

For a quote on stored size, multiply the rate by the ratio of stored to protected size. The ratio comes from this estimate, which assumes that each day's new data is unique and kept for the full retention:

stored size = protected size + (daily new data x (daily points kept − 1))

Example (illustrative): you need 30 daily points for a server fs01 holding 2,000 GB. Quote A charges A per GB-month on protected size, with 30 points included. Quote B charges B per GB-month on stored size. Both rates are placeholders.

  • With about 1% new data a day (20 GB), B's stored size is 2,000 + (20 x 29) = 2,580 GB. That is 1.29 times protected size, so B's cost per protected GB is 1.29 x B.
  • B is cheaper only if 1.29 x B is below A, which means B must be below about 78% of A.
  • With 2% new data a day (40 GB), stored size is 2,000 + (40 x 29) = 3,160 GB, which is 1.58 times protected. B must then be below about 63% of A.
  • If retention rises to 60 daily points at 1%, stored size is 2,000 + (20 x 59) = 3,180 GB, about 1.59 times, and A's cost is unchanged if the retention is included.

A stored-size rate that looks well below a protected-size rate can still cost the same or more. The break-even moves with the change rate and retention, so ask IT for the measured daily new data before you decide. The budgeting guide in the related list shows how to get it.

The same method works when a quote includes full copies: stored size is then protected size multiplied by the number of points, and the ratio is 30 at 30 days.

How do I check a quote?

Send every provider the same sheet:

  1. Server list with used data (GB) and expected growth over the term.
  2. Measured daily new data per server, or a percentage from IT.
  3. Retention required: daily, weekly, monthly and yearly counts.
  4. The number of copies and locations required.
  5. A restore test per quarter of a named size, and a full recovery of one server.

Ask each provider to return:

  • The unit each charge is based on, and whether it is before or after compression.
  • The monthly price at your sizes, with the arithmetic.
  • Whether storage is billed on a monthly average or on the month-end figure.
  • Every charge for restores, copies, transfers and early deletion, with the rate.
  • What is billed, and for how long, if you stop protecting a server.
  • How long the quote holds and how rates can change during the term.

Put the replies side by side in one table with a row per charge. A blank cell is a question to ask, not a zero. The guide to comparing managed hosting quotes gives a wider worksheet covering servers, licences and support beyond backup. For transfer-out charges, the guide on measuring egress shows how to count the volume.

Risks and limits

  • Risk: choosing on the lowest rate can quietly reduce retention, copies or restore rights, and shortening retention later removes older restore points for good. Compare at the same retention and the same copies.
  • The break-even formula is an estimate. It ignores compression, metadata and rounding, and assumes new data is unique each day. Overlap in the data makes stored size smaller.
  • Azure and AWS pages show two ways of structuring a charge. Other providers use other units, and those pages do not describe how any other provider bills. No provider is ranked here.
  • Pricing pages and terms change. Re-read the page behind a quote at signing, and put the units and terms into the contract.

NetLeverage includes a daily full disaster-recovery backup of each hosted server at no extra charge. Talk to an engineer.

Sources