What is data lifecycle management?

Home | Resources | Glossary | Data Lifecycle, Tiering, and Mobility

KEY TAKEAWAYS

The data lifecycle.

Unstructured data moves through its stages without announcing it, so the stage has to be read from the file’s own attributes in a metadata catalog.

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 policy-based data management?

Policy-based data management is managing data through written rules rather than one-off projects. Each rule names a set of files by attributes, such as project, age, owner, or retention class, and states what happens to them, such as a move to an archive tier. The rule runs on a schedule, previews its effect as a dry run, and records what it did. The result is a lifecycle that keeps running after the first cleanup ends.

What is the difference between data lifecycle management and information lifecycle management?

Data lifecycle management decides where data sits and when it moves, is kept, or is removed, based on attributes such as age, last access date, and owner. Information lifecycle management, often shortened to ILM, uses the same stages but asks a business question: how valuable is this information, and to whom. In practice the two meet, because the business value has to be recorded as metadata before any rule can act on it.

Data tiering.

Tiering is placement matched to how often a file is read, and the savings it produces are the subject of storage cost optimization.

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.

Can tiering use business attributes instead of file age?

Yes, when the catalog holds them. A tiering rule can use fields such as project, status, or retention class, so a completed project that has not changed in a year moves to the archive tier even if someone opened one of its files last week. Age and last access still matter, and business attributes make the decision closer to what the data is worth. The storage system moves the files, and the catalog decides which files move.

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 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 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.

Data mobility and migration.

Movement is also when governance risk gets created, because a file can land somewhere its retention class does not allow. Our blog post on what data automation actually means covers how policy keeps that from happening.

Data migration compared with data mobility:

	DATA MIGRATION	DATA MOBILITY
What it is	A one-time move of data between storage systems	Movement of files between systems, tiers, sites, and clouds on policy
How long it runs	It has a start and an end	It runs continuously
What drives it	A hardware refresh or a move to the cloud	Rules written against attributes such as project, owner, or retention class
Typical example	Moving data off a storage system at the end of its life	Moving a completed project to the archive tier

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 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 do you plan an unstructured data migration?

Start with an index of what is on the source system, then decide what moves at all. A typical plan has four steps: index the source, leave behind duplicates and data with no remaining use, preview the move as a dry run, and move the rest in batches with each file recorded in the catalog. Planning from the index usually makes the migration smaller, because part of the source never needed to move.

What is a cloud storage gateway?

A cloud storage gateway is a device or service that presents cloud object storage to local applications as a file share, usually over Network File System (NFS) or Server Message Block (SMB). Applications keep reading and writing files, while the gateway stores the data in the cloud and keeps recently used data in a local cache. It makes the cloud reachable, and it does not describe what the files are, so a catalog is still needed to decide which files belong there.

Dry runs and safe moves.

Every rule previews before it runs. The named list a dry run produces is the same evidence unstructured data governance asks for after the fact.

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.