Storage Tiering, Data Archiving, and Transparent Archiving – What’s the Difference?

A few months ago, we published a white paper that summarizes the differences between Tiering, Data Archiving and Transparent Data Archiving. The paper also outlines the differences between data migration and data archiving, which are terms often used interchangeably, but are quite different.

With cloud data migration a top priority in the era of digital transformation, it’s never been more important to move “cold data” to a cheaper capacity storage to reduce costs. This can be done via data archiving—a process of taking cold files and tiering them to a cheaper location. But, data tiering solutions often move data off the original location so users have to change behavior and look for data in the new place. Such disruption to your end users and applications does not have to be inevitable. Transparent archiving solutions enable cold data to be tiered to cloud storage without any change to user and application access, which is key to gaining user adoption. When your users are worried about not being able to access tiered data as before, they’re less likely to allow data archiving, which reduces savings.

Archive data without disruption

Transparent data archiving is key to maximizing adoption and savings

I think it’s important to emphasize this point: the ability for both your users and your enterprise applications to still access files exactly where they were before being archived—without having to rehydrate the file—is possible. That is the power of what we call Transparent Move Technology™ (TMT). With Komprise, files get archived and they still appear in the original location, so users and applications continue to access the files exactly as before. Additionally, file-level tiering ensures that the entire file is archived as an object, so it can be accessed natively in the cloud by any standard S3 tools, without having to go back to the original file system or to the data management software itself. Komprise TMT enables fully transparent archiving using file-level tiering, so users see no disruption and data is accessed without lock-in.

So how do you ask the right questions to make an educated choice, avoid surprises, and save your organization costs?

Data archiving takes many forms, many of which can cause different types of disruption. Some solutions claim the ability to transparently archive, but are unable to reduce the backup footprint and make it nearly impossible to switch primary vendors, thus eroding savings and imposing vendor lock-in. Our data archiving white paper includes a table that categorizes tiering and archiving into three categories:

  1. cloud tieringTraditional archiving, which creates significant disruption to user access, requires manual approvals and archives only in batches, eliminating a substantial amount of cold data to be archived and cost savings to be realized.
  2. Proprietary transparent archiving via storage tiering, which is the is the method behind Hierarchical Storage Management, which is cumbersome and includes brittle and unreliable stubs and agents. Storage vendors provide archiving with tiering software, which eliminates stubs but can impact performance and imposes vendor lock-in. It also drastically reduces the cost savings afforded by transparent archiving because it fails to reduce the backup and DR footprint.
  3. Standards-based transparent archiving is the only true transparent archiving method that eliminates all disruption and delivers maximum archiving savings. Komprise Intelligent Data Management uses a patented Transparent Move Technology that offers standards-based transparent data tiering and archiving and provides maximum savings. It archives data without disruption to users or getting in front of hot data—all without using stubs or agents or creating vendor lock-in. You can learn more here.

Here is the table:

 

Key Archiving Feature Traditional Archiving Proprietary Transparent Archiving via Storage Tiering Standards-based Transparent Archiving
Maximizes storage & backup savings No

Manual process results in archiving.

No

Only 20% of savings since backup and DR footprint and license costs aren’t reduced.

YES

Provides 100% savings since primary storage footprint is reduced as is backup and DR.

Non disruptive to users and apps No

Users must search for data in two places.

No

It’s transparent to users but not applications, such as backup and virus scanners.

YES

Users and apps are not disrupted. Backup footprint is reduced; virus scanners are not impacted.

Vendor agnostic Yes

Data is lifted and shifted to any secondary storage with no connection to the primary storage. As a result, migrating to another primary storage vendor has no implications.

No

Migrating to primary storage of another vendor is not simple. All archived data must be rehydrated and then migrated to the new primary storage.

YES

You can readily migrate from one primary vendor to another without rehydrating all the archived data.

Outside hot data path

 

Yes

The file is fully moved.

 

No

Tiering cold blocks to slow secondary storage (e.g. cloud storage) can adversely impact performance of these arrays.

YES

Sits behind hot data and metadata paths.

 

Native access on secondary storage Yes

So long as the file was stored in a format native to the secondary storage.

No

The blocks and files moved are in proprietary format and can only be accessed from the primary storage device.

YES

The full file is written in a format native to the secondary storage device.

Example solutions Project-based archiving, ad-hoc archiving or backup-based archiving. Ideal for tiering snapshots that are not usually backed up and tiering warm data. Not designed for wholesale data archiving. Komprise Intelligent Data Management

Provides both project-based and policy-based data archiving.

We often hear, “why didn’t I know about Komprise sooner?” I hope this storage tiering, data archiving, and transparent archiving overview, table, and white paper are useful resources that help you identify the right solution for your use case.

Getting Started with Komprise:

Contact | Demo