The 2026 Unstructured Data Management Report is Here! Access Now.

Tier Across Any NAS, Cloud Transparently Without Lock-In

Patented Komprise TMT tiers with no changes to users or applications. Get native access at every tier without the rehydration expense of proprietary storage tiering.

Core Features of Tiering

Transparent, Continuous Tiering

Flexible Tiering Policies

Tiering Across Multi-Vendor Storage Arrays

Prevent Rehydrating Tiered Data on First Access

Avoid Performance Impact on Hot Data

Fast Access to Tiered Data

Bulk Recall of Tiered Data

Native Cloud Access to Tiered Data

(NO DATA LOCK-IN)

Showback or Chargeback

Decommissioning without Rehydration

(NO VENDOR LOCK-IN)

Storage Array Block Tiering (NetApp FabricPool, Dell CloudPools)

Generally, can only specify an age. But that too can be limited where cold data is specified as anything 6 months or older.

Each storage array only supports tiering from its storage devices, and you must manage each cluster independently. There is no single page of glass to manage tiering across the clusters.

Tiered data that is accessed is immediately rehydrated. Requires that extra storage be kept reserved for such rehydration there by reducing cost advantages.

Since the core tiering engine is used to tier data, high latency to the target can impact performance.

Furthermore, the block tiering approach requires a constant traffic to the cloud to defragment blocks stored in objects. This constant traffic drives up cloud costs and impacts performance. For this reason, storage arrays clearly indicate that if more than 300TB is to be tiered, local object storage should be used.

Blocks are read back instead of the entire file. The blocks are stored back on the array to ensure future requests are fast. However, this approach request that some amount of storage be left unused to house accessed data. This reduces cost savings.

Data is brought back as it is accessed.

The data is in proprietary form and the entire file may not be on the target. The tiered data can only be read from the source.

It is very difficult to switch vendors once you start tiering with a storage array’s tiering solution.

Logo-color

Komprise TMT File Tiering

Komprise provides a range of ages as well as exclusions based on size, file type, directory.

In the next major release, Komprise will allow users to granularly specify what to tier based on custom queries.

Komprise is vendor agnostic. Komprise can be deployed across most common storage arrays, allowing one, consistent, global way to tier data.

Komprise provides a single pane of glass across multi-vendor storage systems.

Komprise allows you to configure just when an access data is rehydrated.

Komprise is involved only when cold data is accessed.

Komprise streams the data and does not wait for the entire file to be read. Komprise caches the data locally to ensure future requests are fast.

Komprise provides a bulk recall feature. In many cases it may be necessary to bring back a large set of data.

Komprise writes tiered data in the format used by the target. For instance, if tiered to S3, it will write the data in S3 format. The data can be accessed from the source or, in this case, the cloud using a standard S3 browser. This enables processing of tiered data without burdening the source storage array.

Today, in the UI Komprise provides percentage of a share’s total storage that is local, and which has been tiered. Customizable showback reporting improves collaboration and alignment across teams.

With Komprise you can migrate from one vendor’s storage array to another without re-hydrating the huge quantity of tiered data. The tiered data will be transparently accessible from the new storage array.