Abstract: Embodiments include a data aware deduplicating object store. The data aware deduplicating data store includes a consistent hashing logic that manages a consistent hashing architecture for the object store. The consistent hashing architecture includes a metadata ring and a bulk ring. The consistent hashing architecture may be a multiple ring architecture comprising a metadata ring and two or more bulk rings. A bulk ring may include a key/value (k/v) data store, where a k/v data store stores a shard of an index and a reference count that facilitates the individual approach to garbage collection or data reclamation. The data aware deduplicating data store also includes a deduplication logic that provides data deduplication for data to be stored in the object store. The deduplication logic performs variable length deduplication and provides a shared nothing approach.

Abstract: Example apparatus and methods identify files that are so small or so large that they compromise the efficient operation of a file system that uses re-assignable one-to-one inodes and inode numbers. Small files are aggregated into collections of files and large files are subdivided into collections of smaller files. Information for locating multiple related files with fewer lookups is generated and stored in a folder. An inode having a new type of inode number is then created. The new type of inode number encodes information for finding the folder. The encoded information may include a folder identifier that acts as a primary key into a database that is configured to locate a member of the aggregated or subdivided files with a single lookup. A filter file system may be updated with the new inode. The new inode number is unique within the filter file system and may not be re-assigned.

Abstract: Example apparatus and methods provide a file system that stores files in multiple different logical units. The logical units are associated with different classes of devices. The file system interacts with the logical units through block-based interfaces. The file system is a single file system that spans the multiple logical units. The multiple different logical units include data storage devices for which the file system manages block storage allocation and an object storage system that manages its own block storage allocation rather than having the file system manage its block storage allocation. The file system may maintain a single namespace, hierarchy, or directory structure for the multiple logical units. The object storage system may protect files using redundant copies, erasure codes, or other approaches. An archive process may selectively move files from other devices to the object storage system and leave a symbolic link behind.

Abstract: Example apparatus and methods access a Linear Tape File System (LTFS) repository that stores data associated with an external entity (e.g., file system, application). Data is copied from the LTFS repository, selectively converted to a form associated with a cloud repository, and provided to the cloud repository. A mapping between corresponding addresses in the LTFS repository and cloud repository is established. Requests by the external entity for data may be satisfied from either the LTFS repository or the cloud repository until a changeover event is detected and are then satisfied from the cloud repository afterwards. The external entity runs on a different computer than the method. The method is transparent to the external entity, is performed independent of the external entity, and continues under its own control until a selected amount of data is moved from the LTFS repository to the cloud repository.

Abstract: Example apparatus and methods provide improved reclamation, garbage collection (GC) and defragmentation (defrag) for data storage devices including solid state drives (SSD) or shingled magnetic recording (SMR) drives. An erasure code (EC) layer that facilitates logically or physically erasing data from the SSD or SMR as a comprehensive GC or defrag is added to the SSD or SMR. Erased data may be selectively recreated from the EC layer as needed. Pre-planned EC write zones may be established to further optimize GC and defrag. Recreated data may be written to selected locations to further optimize SSD and SMR performance. Erasure code data may be distributed to co-operating devices to further improve GC or defrag. Example apparatus and methods may also facilitate writing data to an SMR drive using tape or VTL applications or processes and providing a pseudo virtual tape library on the SMR drive.

Abstract: Embodiments include a data aware deduplicating object store. The data aware deduplicating data store includes a consistent hashing logic that manages a consistent hashing architecture for the object store. The consistent hashing architecture includes a metadata ring and a bulk ring. The consistent hashing architecture may be a multiple ring architecture comprising a metadata ring and two or more bulk rings. A bulk ring may include a key/value (k/v) data store, where a k/v data store stores a shard of an index and a reference count that facilitates the individual approach to garbage collection or data reclamation. The data aware deduplicating data store also includes a deduplication logic that provides data deduplication for data to be stored in the object store. The deduplication logic performs variable length deduplication and provides a shared nothing approach.

Abstract: Example apparatus and methods provide a file system that stores files in multiple different logical units. The logical units are associated with different classes of devices. The file system interacts with the logical units through block-based interfaces. The file system is a single file system that spans the multiple logical units. The multiple different logical units include data storage devices for which the file system manages block storage allocation and an object storage system that manages its own block storage allocation rather than having the file system manage its block storage allocation. The file system may maintain a single namespace, hierarchy, or directory structure for the multiple logical units. The object storage system may protect files using redundant copies, erasure codes, or other approaches. An archive process may selectively move files from other devices to the object storage system and leave a symbolic link behind.

Abstract: Example apparatus and methods access a Linear Tape File System (LTFS) repository that stores data associated with an external entity (e.g., file system, application). Data is copied from the LTFS repository, selectively converted to a form associated with a cloud repository, and provided to the cloud repository. A mapping between corresponding addresses in the LTFS repository and cloud repository is established. Requests by the external entity for data may be satisfied from either the LTFS repository or the cloud repository until a changeover event is detected and are then satisfied from the cloud repository afterwards. The external entity runs on a different computer than the method. The method is transparent to the external entity, is performed independent of the external entity, and continues under its own control until a selected amount of data is moved from the LTFS repository to the cloud repository.

Abstract: Example apparatus and methods provide improved reclamation, garbage collection (GC) and defragmentation (defrag) for data storage devices including solid state drives (SSD) or shingled magnetic recording (SMR) drives. An erasure code (EC) layer that facilitates logically or physically erasing data from the SSD or SMR as a comprehensive GC or defrag is added to the SSD or SMR. Erased data may be selectively recreated from the EC layer as needed. Pre-planned EC write zones may be established to further optimize GC and defrag. Recreated data may be written to selected locations to further optimize SSD and SMR performance. Erasure code data may be distributed to co-operating devices to further improve GC or defrag. Example apparatus and methods may also facilitate writing data to an SMR drive using tape or VTL applications or processes and providing a pseudo virtual tape library on the SMR drive.

Abstract: Example apparatus and methods identify files that are so small or so large that they compromise the efficient operation of a file system that uses re-assignable one-to-one inodes and inode numbers. Small files are aggregated into collections of files and large files are subdivided into collections of smaller files. Information for locating multiple related files with fewer lookups is generated and stored in a folder. An inode having a new type of inode number is then created. The new type of inode number encodes information for finding the folder. The encoded information may include a folder identifier that acts as a primary key into a database that is configured to locate a member of the aggregated or subdivided files with a single lookup. A filter file system may be updated with the new inode. The new inode number is unique within the filter file system and may not be re-assigned.

Abstract: A system and method for use in an automated data storage cartridge library defines cartridges for use with an external host computer (“open” cartridges), and cartridges for use only internal to the library (“closed” cartridges). Cartridges may be “virtualized” by storing data from them on disk or closed cartridges, and then “realized” by writing data to physical cartridges. Virtual cartridges may be logically exported from one library to another. When new cartridges are introduced to the library, they may be designated with one of multiple designations or uses.