← Insights

ACTIVE ARCHIVE

Performance and preservation should work together.

Active Archive separates performance requirements from preservation requirements so information can remain active without delaying long-term protection.

Organizations are often forced to choose between two goals that should not be mutually exclusive.

Keep information on fast storage so users and applications can access it, or move it to a preservation tier so it can be retained economically and durably.

Active Archive changes that decision by separating performance from preservation.

Preservation does not need to wait

The traditional model often leaves information only on performance infrastructure during its active period.

Preservation happens later, after usage declines or an age threshold is reached.

That creates a period in which important information may be highly active but does not yet have an independent preservation copy.

Create the preserved state at ingest

In an Active Archive architecture, information can be written to a performance tier and to durable optical preservation as part of the same ingest process.

The performance copy supports active workloads. The optical copy establishes the preserved state.

The organization no longer has to wait for information to become inactive before preserving it.

Performance capacity can then follow usage

The active copy does not need to exist forever.

As usage falls, policy can reduce or remove the performance copy while the preserved optical version remains available.

If requirements change later, the preserved object can be restored back to performance storage.

Information state and storage state remain separate

This architecture reinforces an important lifecycle principle: the information's governed state does not have to be defined by its current storage tier.

A preserved object can be active, archived, protected, or otherwise governed according to business requirements while its physical placement changes independently.

Storage becomes an execution choice rather than the definition of the lifecycle.

The result is a different storage model

Performance storage is used because performance is required—not simply because the information has nowhere else to live.

Preservation begins immediately rather than eventually.

And when information activity changes, the infrastructure can change with it without sacrificing the preserved copy.

Manage. Store. Preserve.

SAVARTUS PERSPECTIVE

Information should move
when its requirements change.