GLOSSARY
What is data lifecycle management?
What happens to data between creation and retirement: the stages, the tiers, the moves, and how a catalog decides what goes where.
Home | Resources | Glossary | Data Lifecycle, Tiering, and Mobility
DEFINITION
Data lifecycle management is the practice of deciding what happens to data at each stage of its life, from creation through active use, cooling, archive, and retirement. For unstructured data, the stages are not marked by anything the file itself records, so they have to be inferred from attributes: age, last access date, project status, and owner. The lifecycle is a set of rules applied to those attributes.
KEY TAKEAWAYS
up to 50%
of stored data is redundant, obsolete, or trivial
30+
hours a week returned to teams from manual data housekeeping
8 PB
reclaimed by one media customer across a 260 petabyte data estate in four data centers
QUESTIONS THIS PAGE ANSWERS
What is data lifecycle management?
Data lifecycle management is the practice of deciding what happens to data at each stage of its life and applying those decisions as rules rather than as projects. It covers where data sits, when it moves, how long it is kept, and what proves it was treated correctly.
What are the stages of the data lifecycle?
Creation, active use, cooling, archive, and retirement. Unstructured data moves through these stages without announcing it, so you have to derive a file’s stage from its attributes. Last access date is the strongest single signal, followed by project status and owner.
What is data tiering?
Data tiering is placing each file on storage matched to how often it is read. Frequently read data sits on the fastest tier, rarely read data on slower and less costly storage, and data kept for the record on archive storage. The decision is economic, and it depends on knowing access patterns.
What is the difference between file-level and block-level tiering?
Block-level tiering moves blocks within a storage system and is invisible to users and to any catalog. File-level tiering moves whole files between systems and tiers, so each move is visible, attributable, and reversible. Only file-level tiering can be driven by attributes such as project, owner, or retention class.
What is data mobility?
Data mobility is the ability to move files between storage systems, tiers, sites, and clouds on policy rather than as a project. It differs from a migration in that it is continuous and rule-driven. A catalog makes it safe because it decides which files qualify.
What is the difference between data mobility and data migration?
A migration is a one-time move, usually driven by a hardware refresh or a cloud adoption, with a start and an end. Mobility is an ongoing capability where files move whenever a rule says they should. A migration is a project. Mobility is an operating state.
What is archival storage, and when should data be archived?
Archival storage is low-cost storage for data that must be kept and is rarely read. The right moment to archive is when a file has passed its active life and still has a retention obligation or a plausible future use. Deciding that from evidence rather than instinct is the entire difficulty.
What is cloud tiering?
Cloud tiering moves cold data from on-premises storage to cloud storage classes priced for infrequent access. The savings are real, and the risk is read cost, because cloud providers charge more to read data out than to put it in. The decision depends on access history, not on capacity.
What is data repatriation?
Data repatriation is moving data and workloads from public cloud back to on-premises or colocation storage. It usually follows a cost review where read and egress charges turned out to be higher than modeled. The same catalog that justified the move out is what makes the move back measurable.
How does a catalog decide what to move?
It applies rules to attributes it already holds. A typical rule combines age, last access date, path or project, owner, and format, then produces a list of matching files. The rule is written once and keeps running, which is what distinguishes it from an annual clean-up.
What is a dry run, and why does it matter before a move?
A dry run reports exactly which files a rule would affect, without moving anything. It turns a policy from a risk into a reviewable proposal, and it lets someone approve a change covering millions of files with a clear conscience.
What happens to the catalog when a file moves?
The catalog record follows the file. That is what keeps a move from breaking the estate view: the file is still described, still attributable to its project and owner, and still findable, with its new location recorded. A move that loses the description has traded one visibility problem for another.
TERMS IN THIS CATEGORY
Data lifecycle management >
Data lifecycle management is the practice of deciding what happens to data at each stage of its life, and applying those decisions as rules rather than as projects. It covers where data sits, when it moves, how long it is kept, and what proves it was treated correctly.
Archival storage >
Archival storage is low-cost storage for data that must be kept and is rarely read. It trades retrieval speed for price, which is the right trade once a file has passed its active life and still has a retention obligation or a plausible future use.
Data tiering >
Data tiering is the practice of placing each file on storage matched to how often it is read. Frequently read data sits on the fastest tier, rarely read data on slower and less costly storage, and data kept for the record on archive storage. The decision is economic, and it depends on knowing access patterns.
Cloud tiering >
Cloud tiering moves cold data to cloud storage classes priced for infrequent access. The savings are real, and so is the read charge, so the decision depends on access history rather than on how much capacity would be freed.
File-level tiering >
File-level tiering moves whole files between systems and tiers, visibly and reversibly. Because the unit is a file, each move can be driven by attributes such as project, owner, or retention class, and each move can be attributed and undone.
Data repatriation >
Data repatriation is moving data and workloads from the public cloud back on-premises or to colocation. It usually follows a cost review where read and egress charges turned out higher than modeled.
Data mobility >
Data mobility is the movement of files between systems, tiers, sites, and clouds on policy. It differs from a migration in being continuous and rule-driven: a migration is a project with an end date, and mobility is an operating state.
Dry run >
A dry run is a report of what a policy would do, produced without doing it. It turns a rule from a risk into a reviewable proposal, which is what lets someone approve a change covering millions of files.
Data migration >
A data migration is a one-time move of data between storage systems, usually driven by a hardware refresh, a consolidation, or a move to the cloud. It has a start and an end, which is what separates it from mobility.
Retention >
Retention is the period for which data must be kept before it may be removed. The period comes from a regulation, a contract, or an internal rule, and for file data the difficulty is usually working out which period applies to which files.
Diskover for data lifecycle management.
Lifecycle work runs continuously, not once a year. Here is where to start.
Rules that run themselves.
Policies act on metadata like age, last access date, project, owner, and format, so lifecycle stages get applied continuously rather than in an annual push. A rule written once keeps finding the files that match it.
Movement across vendors and clouds.
Policy moves files between network-attached storage, object storage, cloud, and archive, whatever the vendor, and the catalog record follows them. PowerScale, ONTAP, S3, and Azure Blob are among the systems supported.
A named list before any action.
A policy acts on specific files rather than on a percentage, and a person approves that list before any file is touched. The list names the rule each file matched, so the approval is a review rather than a leap.
Hours returned to the team.
Teams running this pattern report 30 or more hours a week saved from manual data housekeeping: the searching, the spreadsheet reconciling, and the chasing of owners that lifecycle work used to mean.
RELATED CATEGORIES
SOURCES
- Cadence Group, 2025: in large enterprises, redundant, obsolete, or trivial data can account for up to 50% of stored data.
- Hours-returned and customer reclamation figures are Diskover’s own, measured across customer deployments and reported by industry rather than by name.
Method note. Lifecycle stage boundaries are set by each organization, so any figure describing what share of an estate is cold depends on where that line was drawn. The hours-returned figure is reported by customers rather than instrumented, and it reflects teams that did this work manually beforehand. The reclamation figure describes one estate rather than a typical result.
Last updated: September 24, 2026.