Generic hierarchical file system software

In concluding this post, it should be highlighted that we have built the filesystem to enable a variety of data management use cases, across a customerвЂ™s storage environment, without creating any lock-in. They are also provisioned for dynamic load balancing across the Komprise Observer Virtual Appliance Grid, using a co-operative distribution algorithm.

The filesystem instances running on various nodes of the Komprise grid serve up both migration and access traffic. Policy based at folder granularity to have a level of control over egress costs from public clouds.Off-grid cloud hosted read-only gateways for file based access in and from public clouds.Typically for browsing the directory hierarchies for a global view.Direct access over Komprise exported mounts.Redirections from source share links or stubs.Cold and archival data transfer from the source shares to Komprise targets.Although not particularly having affinity to any particular workload, the following are what are typically expected over the lifetime of the Komprise management of data: The filesystem instances on the Komprise Observer Virtual Appliance are operationally transparent to users of the Komprise solution and entirely managed autonomously. To learn more about the Komprise architecture, read the Komprise Architecture Whitepaper. By leveraging open standards and creating a distributed design, Komprise is able to provide unified visibility and management without creating lock-in. Instead, Komprise leverages the sources and targets themselves to create a redundant, overarching namespace. Komprise addresses these with a patent-pending redundant, transparent, hierarchical filesystem that is not creating any new storage or metadata repositories. Enable access to data from primary and secondary storage without lock-in.Transparent file gateway that bridges NAS, object and cloud storage.Provide a single namespace to all moved data without fronting all the metadata or data paths.Seamless, transparent translation between files andВ objects (key, value pairs) when object stores are the at rest targets.Secure and bandwidth optimized for transport over WANs to public clouds (but not limited to just public clouds).Fidelity in preservation and representation of file metadata and namespace hierarchy.The Komprise Filesystem has been designed to address the following: To understand how Komprise works and provides transparent access, watch our five-minute demo. Data moved to any of these targets looks to users and applications as if it were still on the original source and remains fully accessible, exactly as before.

Komprise Targets can be public/private clouds, LTO/archival devices or other NAS filers. The Komprise solution includes a filesystem interface which is not merely self-serving vis-Г -vis data ingestion, but also forms a vital cog that provides seamless and transparent access as the data temperature varies over its lifetime. LetвЂ™s examine how cold data, identified by Komprise, is stored and managed on your cloud or on-prem targets. Instead, Komprise delivers transparent file access to cold data from any of your sources. Walking Through the Komprise Architecture and How it Works Under the Hood.ДЇirst, letвЂ™s look at how Komprise provides a redundant, transparent, hierarchical filesystem that bridges file and object data without superimposing a single namespace or metadata layer.

Generic hierarchical file system software