The Komprise scale-out architecture works across storage systems using standard protocols—with no interference to hot data, metadata, or network paths. Access data with full fidelity from anywhere with no lock-in, keeping you in control of your data. Some of the benefits of direct data access include:
Access data from any tier without going to the source
When you move your data with Komprise, it can be directly accessed from the target device using its native protocol. Let’s say you move data to the cloud using Komprise. You can access that data transparently from the source and directly from the target using standard S3/object cloud native tools. You can view and access that data as files by mounting the Komprise Cloud File System. This ensures your data doesn’t get locked into any one storage or backup solution—or to Komprise for that matter.
Access data in native format. At Komprise, we believe you should own your data and not be locked into a proprietary solution. When we archive or copy your data, we put it in a form that’s native to that storage system. This ensures that archived data is not locked away and can be continually used to extract value. You can use third-party applications, cloud native tools, or Komprise applications to extract that value— Komprise never locks you in. We preserve all the standard metadata and the extended metadata, such as tags with the data wherever it moves, so your files retain their full context and remain usable wherever they go.
No rehydration necessary.  Block-level tiering, used by many storage-based data management solutions, requires rehydrating archived data before it can be used, migrated, or backed up. This approach negates much of the benefit of data archiving in the first place. For instance, if you archive 75% of your data but must rehydrate it when backing up, you’ve saved nothing. Or, if you want to end-of-life your 1PB storage system from which you’ve archived 3PB of data over its lifetime, you’ll need to rehydrate all 3PB before you can migrate off that system. Komprise file-based tiering eliminates these rehydration issues.
Read the Komprise architecture white paper.