Netapp, Inc.

Emc Corporation

Ranjit Kumar

Kaladhar Voruganti

Sisir Shekhar

Parag Deshmukh

Kartheek Muthyala

Chhavi Sharma

Vineet Pandey

Michael Robin Eisler

A method and system for replicating file system entities in a manner that preserves block-level access and file system efficiency mechanisms such as deduplication are disclosed. In an embodiment, a replication engine receives a stream of file system entities that include a file system inodes and file system data blocks. The replication engine generates object-based storage (OBS) objects based on data and reference information specified by the file system entities. As part of generating the OBS objects, the replication engine generates at least one inode file object that associates file block numbers of a file system inode file and the inode numbers. The replication engine uses inode information to generate reference objects that logically associate file block numbers with data block numbers in per inode manner. The replication engine further generates data objects that contains the file system data blocks and that associates the data blocks with corresponding data block numbers.

Object-based storage replication and recovery

A method and system for managing backup storage of file system entities. In an aspect, a file system catalog includes a database populator tool that generates records within a metadata table that may be maintained within a database. In response to detecting a replication cycle, the populator tool reads a stream of replication operations. For each of the replication operations, the populator tool determines the type of operation and in response to determining that a directory inode is an operand of the replication operation, the tool generates one or more catalog records. Each of the generated records includes and logically associates data entries corresponding to an inode number, a parent inode number, an entity type, a point-in-time-image (PTI) ID, an absolute path, and an operation.

Cataloging metadata for replication management and recovery

One or more techniques and/or systems are provided for migrating a dataset from a file storage system to an object storage system. That is, a snapshot of a file system may be received from the file storage system. The snapshot may comprise file data associated with a file of the file system. The file may be converted into an object using the file data. The object may be stored within a data constituent volume of the object storage system. A namespace volume, used to track objects, may be populated with a redirector that maps a front-end data path (e.g., a path used by clients to reference the object) to a back-end data path that specifies a path to the object within the data constituent volume. In this way, a dataset of one or more files may be migrated from the file storage system to the object storage system.

Migrating data from legacy storage systems to object storage systems

Determining efficiently whether it is necessary to re-inventory a storage media library, such as a tape library, is disclosed. It is determined whether a first number computed based at least in part on at least a portion of a new inventory data is the same as a second number computed based at least in part on a corresponding stored inventory data. An update of the stored inventory data is initiated if it is determined that the first number is not the same as the second number.

Inventory of libraries

The present invention is a system and method for extending the functionality of tape device tapemarks. When data is backed up to tape, the tape controller may mark the tape with a tapemark to organize portions of the tape. Present tape storage devices are limited to a single type of tapemark; therefore current recovery requests require knowledge of the tapemark location. The present invention allows for unique types of tapemarks. By allowing the tape device, tape controller and/or backup and recovery software to recognize unique tapemarks, data organized by unique tapemarks can be recovered without referencing tapemark location, thereby optimizing recovery. Unique tapemarks may be encrypted such that data recovery is only completed upon verification of the requester.

Growing community of inventors

Santa Clara, CA, United States of America

Ranjit Kumar