Netapp, Inc.

Kartheek Muthyala

Gaurav Makkar

Srinivasan Narayanamurthy

Sisir Shekhar

Ranjit Kumar

Arun Suresh

Michael Robin Eisler

Ajay Bakre

Rukma Ameet Talwadker

Stephen William Daniel

Chhavi Sharma

Dhruva Krishnamurthy

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 system and computer-based method for performing a data transaction in a network storage system is provided. In an embodiment, the method includes receiving, from a client, a first data transaction request including a first data identifier associated with a first namespace protocol; determining a storage system associated with the first data identifier and associated with a second namespace protocol; determining a second data identifier associated with the first data identifier, wherein the second data identifier conforms to the second namespace protocol; and forwarding a second data transaction request including the second data identifier to the storage system based on determining an association between the second data identifier and the first data identifier, wherein the first namespace protocol and the second namespace protocol are different.

Federated namespace of heterogeneous storage system namespaces

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

Technology is disclosed for managing data in a distributed file system ('the technology'). The technology can gather metadata information associated with the data stored within the distributed file system, create a secondary namespace within a local file system of a local host using the gathered metadata information and store the gathered metadata information as files within the secondary namespace. Further, when a request to create a PPI of the distributed file system is received, the technology can create a PPI of the secondary namespace using a PPI creation feature of the local file system.

Distributed file system snapshot

Embodiments described herein provide an object store that efficiently manages and services objects for use by clients of a distributed data processing system. Illustratively, the object store may be embodied as a quasi-shared storage system that interacts with nodes of the distributed data processing system to service the objects as blocks of data stored on a plurality of storage devices, such as disks, of the storage system. To that end, an architecture of the object store may include an on-disk layout, e.g., of the storage system, and an incore layout, e.g., of the nodes, that cooperate to illustratively convert the blocks to objects for access by the clients.

Object store architecture for distributed data processing system

Technology is disclosed for managing data in a distributed file system ('the technology'). The technology can gather metadata information associated with the data stored within a first file system, store the metadata information in association with a data identifier within a second file system, retrieve the stored metadata information using the data identifier from within the second file system and locate and retrieve the data associated with the metadata information from within first file system.

Distributed file system gateway

Technology is disclosed for managing data in a distributed processing system ('the technology'). In various embodiments, the technology pushes 'cold' data from a primary storage of the distributed processing system to a backup storage thereby maximizing the usage of the space on the primary storage to store &#x201c;hot&#x201d; data on which most data processing activities are performed in the distributed processing system. The cold data is retrieved from the backup storage into the primary storage on demand, for example, upon receiving an access request from a client. While the primary storage stores the data in a format specific to the distributed processing system, the backup storage stores the data in a different format, for example, format corresponding to the type of backup storage.

Growing community of inventors

Bengaluru, India

Kartheek Muthyala