What is rehydration?

Rehydration is the process to fully reconstitute files so the transferred data can be accessed and used. Block-level tiering requires rehydrating tiered archived data before it can be used, migrated or backed up. No rehydration is needed with Komprise, which uses file-based tiering.

Rehydration and the Cloud

In this post, Komprise CEO Kumar Goswami answers the question: “Will I lose storage efficiencies such as de-dupe by not using a storage tiering solution in the cloud?” He notes:

Komprise_CloudTieringPool_blogsocial2Block-tiering-vs-file-tiering-Oct-2019-FINALv21024_1The overhead of keeping blocks in the cloud due to high egress costs, high data rehydration costs and high defragmentation costs significantly overshadows any potential de-dupe savings. When data is moved at the block level to the cloud, you are really not saving on any third-party backups and other applications because block tiering is a proprietary solution – read this white paper for more background on block-level vs file-based data tiering and cloud tiering. So if you consider all the additional backup licensing costs, cloud egress costs, cloud retrieval costs plus the fact that you are now locked-in and have to pay file system costs forever in the cloud to access your data (learn more about the benefits of cloud native unstructured data access), then the small savings you may get from dedupe are significantly overshadowed by overall costs and the loss of flexibility.

Komprise provides a custom data rehydration policy that the user can configure to meet their needs. Data need not be re-hydrated on the first access. Komprise also provides a bulk recall feature if needed. Learn more about file-based cloud tiering with Komprise.

Want To Learn More?

Related Terms

Getting Started with Komprise:

Contact | Data Assessment