Transparent Move Technology™
Transparent Move Technology™
Leverage the Full Power of the Cloud Without Disrupting Users.
The patented Komprise Transparent Move Technology™ (TMT) goes beyond storage tiering to analyze, migrate, tier and replicate data across multi-vendor storage and clouds while enabling native use of the data at each layer. This is possible without disrupting users and without vendor lock-in.
Files moved by Komprise TMT appear just as they did before, without users noticing any difference, and open like normal files on the desktop. No stubs. No agents.
Komprise is the only vendor that provides transparent tiering from the source storage array with native access to the cold data on the target, without getting in front of hot data on the source. Core to Komprise Intelligent Data Management, Komprise TMT tiers, archives, migrates, replicates and extracts data to deliver the following benefits:
TRANSPARENT ACCESS TO MOVED FILES FROM THE ORIGINAL NAS
- TMT moves files by policy to a secondary storage of your choice such as the cloud. TMT leaves behind industry-standard symbolic links that are dynamic and resilient, called Komprise Dynamic Links.
- Users and apps can open and access the moved files from their original location exactly as before, without any changes.
PRESERVE FILE-OBJECT DUALITY
- With TMT, moved files can be natively accessed as objects in the cloud.
- When Komprise TMT moves a file to object storage such as Amazon S3, it writes the entire file as an object, unlike storage-based tiering (“cloud pools”). This means you can directly access your moved data and extract more value from your cold data.
NO OBSTRUCTION OF HOT DATA
- Komprise TMT moves data using standard protocol constructs, so it is not in the hot data path, unlike storage tiering, global file storage gateways and data virtualization solutions.
- Komprise is only called when cold files are accessed, which happens rarely. This improves performance of primary storage and allows you to run data analytics in the cloud versus on your file storage.
NO STUBS, AGENTS, OR PROPRIETARY INTERFACES
- Komprise Dynamic Links contain all the file system information a user or application requires in a simple, scalable format.
- No stubs or agents that are brittle and problematic to manage. No central database. Learn more about the fault-tolerance and load balancing of the Komprise Elastic Grid.
MINIMIZE REHYDRATION AND EGRESS FEES
- Komprise TMT moves data at the file level with the file metadata fully preserved at the target so the moved data can be accessed as files from both the source and from the target.
- With Komprise, you can use files in the cloud for any file-based applications without having to bring data back to the original NAS. This has the added benefit that your big data analytics projects don’t tax your primary NAS.
ESTABLISH A LAYERED DEFENSE AGAINST RANSOMWARE
- Komprise customers can use immutable cloud storage via AWS S3 Object Lock to provide another layer of defense against ransomware.
- Komprise enables organizations to protect file data from ransomware at 80% lower cost through a combination of transparent cloud tiering and replication of all data to an object-locked location with file-level isolation. [Learn More]
Read the white paper: Komprise Intelligent Data Management Architecture Overview
Why Transparent File Tiering?
Cloud tiering and archiving can offer significant cost savings, a path to the cloud, and a zero-disruption solution that is never in the hot data path and leverages existing investments. But, not all tiering solutions are the same. You may end up paying more in cloud egress and storage licensing costs by picking the wrong strategy.
Block-Level versus File-Level Data Tiering – What’s the Difference?
 |
||||||
| Core Features of Tiering | Storage Array Block Tiering (NetApp FabricPool, Dell CloudPools) |
Komprise TMT File Tiering | ||||
| Transparent, Continuous Tiering |
|
|
||||
| Flexible Tiering Policies |
Generally, can only specify an age. But that too can be limited where cold data is specified as anything 6 months or older. |
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. |
||||
| Tiering Across Multi-Vendor Storage Arrays |
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. |
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. |
||||
| Prevent Rehydrating Tiered Data on First Access |
Tiered data that is accessed is immediately rehydrated. Requires that extra storage be kept reserved for such rehydration there by reducing cost advantages. |
Komprise allows you to configure just when an access data is rehydrated. |
||||
| Avoid Performance Impact on Hot Data |
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. |
Komprise is involved only when cold data is accessed. |
||||
| Fast Access to Tiered Data |
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. |
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. |
||||
| Bulk Recall of Tiered Data |
Data is brought back as it is accessed. |
Komprise provides a bulk recall feature. In many cases it may be necessary to bring back a large set of data. |
||||
| Native Cloud Access to Tiered Data (NO DATA LOCK-IN) |
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. |
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. |
||||
| Showback or Chargeback |
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 colloboration and alignment across teams. |
|||||
| Decommissioning without Rehydration (NO VENDOR LOCK-IN) |
It is very difficult to switch vendors once you start tiering with a storage array’s tiering solution. |
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. |
||||
Read White Paper: Cloud Tiering: Storage-Based vs. Gateways vs. File-Based
