Managed Database Backup Retention: Days Kept and Whether It Bills Separately
Short answer: The number of days a provider prints for backups is not the same thing as what those backups cost, and four official pages checked on 2026-11-18 do not line up on either question. Azure SQL Database says backups are "included at no extra cost beyond the price of the service tier" and, on the same page, that it "computes your total used backup storage as a cumulative value" reported hourly to the billing pipeline — free and metered in one document. OVHcloud says "backups ... included" and then prints three different retention periods on three node tiers (48 hours, 14 days, 30 days). DigitalOcean prints "free daily backups" with a seven-day restore window but no number of days you are billed for. Google Cloud SQL says retention runs "from 1 day to 10 years" depending on the backup option and that final backups "are charged similar to other backups for the number of days retained." Read the billing paragraph next to the retention number: included days and billed days are two different meters.
Comparison table: what each official page printed about backup days and billing (checked 2026-11-18)
Every cell was read from the named first-party page on 2026-11-18. Where a page printed no figure, the cell says so. Azure and OVHcloud were each opened twice with byte-identical text; the two figures that disagree are on the same page of each provider, not a difference between two visits. Units, wording and day-counts are kept as printed.
| Provider | Retention as printed | Included or billed, as printed | The same page's conflicting line | Official source (opened 2026-11-18) |
| Azure SQL Database | PITR "7 days by default, configurable between 1 and 35 days (except Basic databases, which are configurable between 1 and 7 days)"; LTR "up to 10 years" | "Are included at no extra cost beyond the price of the service tier"; separately, "You aren't charged for backup storage consumption up to the maximum data size for a database" | "Azure SQL Database computes your total used backup storage as a cumulative value. Every hour, Azure reports this value to the billing pipeline"; "deleting and recreating a database might increase backup storage costs" | learn.microsoft.com, automated-backups-overview [S1] |
| OVHcloud Managed MySQL | Discovery "Backup: 48-hour retention"; Production "Backup: 14-day retention"; Advanced "Backup: 30-day retention" | "with IOPS, backups, and traffic included"; feature list "Point in time recovery / Included" | the word "included" sits above a range that runs from 48 hours to 30 days by node tier; FAQ says "default retention policies differ depending on the pack you choose" | ovhcloud.com/en/public-cloud/mysql/ [S2] |
| DigitalOcean Managed Databases | "Restore data to any point within the previous seven days"; docs add daily PITR backups, single-node plans included | "Free daily backups"; no per-day or per-GB backup price printed on the product or pricing page opened | billing page printed a plan price and a "Storage Optimized" tier but no backup-retention charge line (Read not available on the pages opened) | digitalocean.com/products/managed-databases, /pricing/managed-databases, docs.digitalocean.com/products/databases/ [S3] |
| Google Cloud SQL (MySQL) | automated retention "from 1 day to 10 years, depending on your instance's backup option"; final backup "30 days" default, 1–365 days standard or 1–10 years enhanced; deleted instances' backups retained "four days" | on-demand standard backups "stored indefinitely until manually deleted"; "Final backups are charged similar to other backups for the number of days retained" | one page lists on-demand backups as kept indefinitely at no stated charge and final backups as charged per day retained, under the same "Backup retention" heading | cloud.google.com/sql/docs/mysql/backup-recovery/backups [S4] |
Two of these pages place "included" and "metered" in the same document. One prints three retention periods under a single "included" label. One states no retention charge at all. One charges final backups by the day while keeping other backups indefinitely. The day-count is not a price, and the word "free" is not a billing statement.
The finding a retention column cannot carry
- "Azure SQL Database's automatic-backup page says backups 'Are included at no extra cost beyond the price of the service tier' and, in the same document, says it 'computes your total used backup storage as a cumulative value' reported 'every hour' to 'the billing pipeline'; it also states that deleting and recreating a database 'might increase backup storage costs' — a page that calls backups free also describes a meter that bills them." — Angle: official page contradicts itself. Both reloads of this page returned byte-identical text, so the two statements are one document, not a stale cache. The reader's takeaway is to read the metering paragraph, not the "included" label.
- "OVHcloud's Managed MySQL page prints 'with IOPS, backups, and traffic included' and lists 'Point in time recovery / Included', then prints Backup: 48-hour retention on Discovery, 14-day retention on Production and 30-day retention on Advanced; its FAQ confirms 'default retention policies differ depending on the pack you choose' — 'included' covers three different day-counts." — Angle: one word, three quantities. This page was opened twice with byte-identical text. A buyer comparing the single word "included" across tiers is comparing 48 hours to 30 days.
- "Azure writes backup retention in days (7 default, 1–35 configurable, up to 10 years for LTR), OVHcloud writes it per node tier (48 hours, 14 days, 30 days), DigitalOcean writes it as a restore window (seven days), and Google Cloud SQL writes it as a range tied to a backup option (1 day to 10 years); four 'retention' figures attach to four different objects." — Angle: price and quantity hang on different objects. A day-count next to a monthly price does not tell you what the day-count costs until you know which object it measures.
- "Google Cloud SQL's backup page keeps on-demand standard backups 'indefinitely until manually deleted' while stating that final backups 'are charged similar to other backups for the number of days retained', and retains deleted instances' backups for 'four days'; three different retention rules sit under one 'Backup retention' heading on one page." — Angle: the same item printed with a different nature. Indefinite storage, a 30-day default and a four-day post-deletion window are not one policy, so a single "does it bill separately" answer cannot cover them.
Where the first ten result slots stop (Google US, udm=14, gl=us, checked 2026-11-18)
R12 counts on this SERP: nine natural results, zero sponsored results, zero People Also Ask or video cards counted by the card selector, and an AI overview present. The AI overview printed its own definition of managed database backup retention. The tenth natural slot was absent — after nine natural results the remaining space was taken by the AI overview, not by another natural entry.
- Microsoft Learn — "Long-Term Retention Backups, Azure SQL Database": the first result is the official LTR configuration page; this page reads the sibling automatic-backup page in full and quotes both billing lines from it.
- Microsoft Learn — "Long-Term Backup Retention, Azure SQL Managed Instance": the managed-instance variant of the same topic; this page keeps SQL Database and SQL Managed Instance figures from being mixed.
- Severalnines — "Managing Database Backup Retention Schedules": an operator-facing editorial guide, not a provider price list; this page uses first-party pages for all four providers.
- azure.cn — "Manage Azure SQL Database long-term backup retention": the China-region documentation mirror; this page cites learn.microsoft.com, not the mirror, for the figures it prints.
- Eon.io — "Backup Retention Policy: What to Keep, How Long": a vendor blog on retention policy, not published provider meters; this page prints what each provider actually charges.
- Oracle Help Center — "Backup Retention": Oracle's own recovery-service docs; not read as a fourth provider here because the four-provider table is already filled from pages with billing text.
- Tencent Cloud — "Backup Retention Settings": a provider doc page for a region this page did not open; no figure from it is quoted here.
- Tencent Cloud — "Backing up Databases": another provider doc; this page does not quote community or third-party text for its figures.
- Stack Overflow — "Increase Azure SQL Managed Instance backup retention": a community Q&A titled in the results; body not read, and no community text is quoted here.
- Tenth natural slot absent: after nine natural results the SERP showed the AI overview and no further natural entry; there was no tenth result to record.
Cross-check against pages already in this cluster
Three published pages in this cluster — [managed database hosting](/managed-database-hosting), [database as a service](/database-as-a-service) and [managed database pricing](/managed-database-pricing) — record the day-counts (DigitalOcean seven days, OVHcloud 48 hours at entry, Vultr 14 days at 3 nodes) but treat retention as a specification. None of them sets the day-count next to the billing paragraph. This page takes the meter that those pages leave out: what "included" costs once a provider writes a billing pipeline, a per-day final-backup charge or three tier-dependent day-counts under one label.
Sources
- [S1] https://learn.microsoft.com/en-us/azure/azure-sql/database/automated-backups-overview — opened twice 2026-11-18 (byte-identical): PITR "7 days by default, configurable between 1 and 35 days (except Basic databases ... 1 and 7 days)", LTR "up to 10 years", "included at no extra cost beyond the price of the service tier", "You aren't charged for backup storage consumption up to the maximum data size for a database", "computes your total used backup storage as a cumulative value ... reports this value to the billing pipeline", "deleting and recreating a database might increase backup storage costs".
- [S2] https://www.ovhcloud.com/en/public-cloud/mysql/ — opened twice 2026-11-18 (byte-identical): "with IOPS, backups, and traffic included", "Point in time recovery / Included", Discovery $64.24/month/node 48-hour retention, Production $81.76 14-day, Advanced $83.074 30-day, FAQ "default retention policies differ depending on the pack you choose".
- [S3] https://www.digitalocean.com/products/managed-databases + https://www.digitalocean.com/pricing/managed-databases + https://docs.digitalocean.com/products/databases/ — opened 2026-11-18: "Free daily backups", "Restore data to any point within the previous seven days", docs "Daily point-in-time backups"; no backup-retention charge line on the pages opened.
- [S4] https://cloud.google.com/sql/docs/mysql/backup-recovery/backups?hl=en — opened 2026-11-18: automated retention "1 day to 10 years" by backup option, final backup 30-day default / 1–365 days standard / 1–10 years enhanced, "Final backups are charged similar to other backups for the number of days retained", on-demand standard backups "stored indefinitely until manually deleted", deleted-instance backups "four days".
Marcus Reid
Systems Architect & VPS Infrastructure Analyst
Marcus has been working with virtualized server infrastructure since 2015, deploying and benchmarking VPS and cloud instances across DigitalOcean, Vultr, Hetzner, OVHcloud, Contabo, RackNerd, Hostinger, and the major hyperscalers. His work focuses on the gap between what providers advertise and what actually happens when you deploy a real workload. He verifies every price and specification against official provider pages before publication.