Cold storage backup moves rarely accessed data into low-cost archive tiers so you can hold it for years without paying hot-storage rates. The same tiers that make long-term retention cheap also make recovery slower and sometimes more expensive than teams expect.
What is cold storage backup?
Cold storage backup keeps backup copies in archive-grade storage built for data you access rarely but cannot delete. Cold tiers offer far lower storage rates than hot tiers, in exchange for slower access and retrieval fees.
Retention drives the decision. Operational backups stay in faster tiers for quick recovery. Older copies and compliance records you keep only because a regulator or contract requires them move to cold storage, where holding them stays cheap over years.
How cold storage backup works for long-term retention
Cold storage backup works by moving aged data into archive tiers through lifecycle rules, then requiring a retrieval step before you can read it again.
Tiering and lifecycle transitions
Lifecycle policies move objects from hot to cold automatically once they reach a set age or stop being accessed. On AWS, a lifecycle rule shifts backups into S3 Glacier classes after a set number of days.
Azure and Google Cloud use the same model. The transition runs on a schedule, so plan for it to apply within about a day rather than instantly.
The retrieval step teams underestimate
Archived objects in offline tiers cannot be read directly. You first submit a restore request, wait for a temporary copy, then read it. That wait runs from a few hours on Glacier Flexible Retrieval to 12 hours or more on Deep Archive or Azure Archive, the gap that catches teams mid-incident.
Google Cloud's Archive class is the exception, keeping data online with millisecond access, though retrieval fees still apply.
Cold storage tiers across AWS, Azure, and Google Cloud
Archive tiers differ most in retrieval speed and minimum storage duration. The table maps the main options across the three major clouds.
Tier figures come from AWS, Azure, and Google Cloud documentation. The two columns that decide the call are retrieval speed and minimum storage duration, so read the table by how fast you would actually need the data back.
What cold storage backup actually costs over a retention window
Cold storage backup costs less to hold but more to recover, so the real number comes from your full retention window, including retrieval and minimum-duration fees.
Storage is the cheap part. AWS S3 Glacier Deep Archive lists at about $1 per TB per month. The charges that surprise teams sit elsewhere. Every archive tier bills a minimum storage period, from 90 days on Glacier Flexible Retrieval to 365 on Google Cloud Archive, and deleting an object early still costs the remaining days.
Retrieval adds its own line. Pulling large volumes back carries per-GB fees, and a full restore can become a real bill in the one month you need the data.
The bigger lever is to archive less in the first place. Eon's backup-optimized storage tier deduplicates and compresses backup data before it ever reaches a tier, cutting the stored footprint 30–50%. That is how NETGEAR cut its backup storage costs 35% on Eon.
What belongs in cold storage, and what gets stranded
Data belongs in cold storage when you must keep it for years and can tolerate a slow recovery, and it gets stranded when nobody decided either of those things.
Three inputs settle the call. One, a retention obligation, whether a regulation or contract forces you to keep it. Two, recovery-time tolerance, how long the business can wait. Three, access pattern, how often anyone reads it.
Cost pressure pushes teams to skip that triage, and disposable data drifts into the archive. In Eon's 2026 report, 87% of cost-pressured teams hold data they do not need. One Director of Data Infrastructure in the report described keeping "daily backups for the past three or four years sitting in a data lake."
Cloud Backup Posture Management (CBPM) is built to catch this. Eon classifies resources as they are created and sets retention by data type, so compliance data gets a long hold and disposable data does not age into an archive you keep paying for.
Why do cold backups fail when you finally need them?
Cold backups fail at recovery time when the retrieval delay runs longer than the business can wait, or when the only path back is a full-object restore that rehydrates an entire archive to reach one file.
A 12 to 48 hour retrieval is fine for a tax archive and unworkable for a system that has to be back in an hour.
The second trap is granularity. Recovering one record from an archive often means rehydrating the whole object or snapshot, then searching it. Granular recovery avoids that by pulling back only the file, object, or table you need.
Innago cut common restores to 10 to 15 minutes after moving to granular recovery on Eon.
Long retention also raises an integrity question: whether a years-old copy is still clean. Immutable, logically air-gapped backups hold a copy that production credentials can’t change or delete, the copy you rely on for ransomware recovery and audit defense.
Keeping long-retained backup data usable
Long-retained backup data stays useful when you can search or query it in place, instead of restoring an entire archive to answer one question.
A compliance lookup or an audit usually needs a few records rather than a full environment. Eon's 2026 report found 77% of teams see strategic value in retained data, while only 16% are actively using it that way.
Global Search finds records across it without a full restore. This is an emerging capability, strongest for supported database and object workloads.
Cold storage backup best practices
Cold storage backup pays off when retention, recovery, and access are decided up front. The table contrasts what works with the mistake that usually follows.
See where your retention plan stands
How fast could you get a single record back from data you archived three years ago? If the honest answer is hours or days, your cold storage plan is worth pressure-testing before the next audit or incident.
Eon is built for this end of the data lifecycle: it sets retention by data type, so disposable data never strands in an archive, and cloud-native deduplication keeps what you do retain 30–50% smaller.
When you need something back, an immutable, logically air-gapped copy stands behind audit and ransomware recovery, and granular recovery pulls a single record or queries the archive in place instead of rehydrating the whole thing.
Not sure how your own archives would hold up under a real restore? Book a demo and see how Eon handles long-term retention and granular recovery.
Frequently asked questions
What is the cheapest cold storage tier for backups?
Amazon S3 Glacier Deep Archive is AWS's lowest-cost tier at about $1 per TB per month, with Google Cloud Archive and Azure Archive in a similar range. The tradeoff is slower retrieval and a longer minimum storage duration, so the cheapest tier is rarely the cheapest choice once retrieval is included.
How long does it take to recover data from cold storage?
Recovery from cold storage ranges from milliseconds to roughly 48 hours, depending on the tier. Google Cloud Archive returns data in milliseconds, AWS Glacier Flexible Retrieval in minutes to hours, and AWS Deep Archive or Azure Archive in 12 hours or more.
Is cold storage the same as a backup?
No, cold storage is a storage tier, while a backup is a protected, recoverable copy of your data. Putting a backup in a cold tier sets its cost and access speed, but the backup still needs policy, isolation, and a tested restore path to be reliable.
Can you recover a single file from cold storage?
Recovering a single file from cold storage depends on the tool, not only the tier. Native archive restores often bring back the whole object or snapshot first, while granular recovery lets you pull back one file, object, or record without rehydrating the surrounding environment.
