Lsi Corporation

Emc IP Holding Company LLC

Dell Products Inc.

Avago Technologies General IP (singapore) Pte. Ltd.

Agere Systems Inc.

Symantec Corporation

Avago Technologies International Sales Pte. Limited

Dell USA L.p.

Symantec Operating Corporation

George Mathew

Yuan Xing Lee

Hongwei Song

Jongseung Park

Shaohua Yang

Abhinav Duggal

Philip N Shilane

Murthy V Mamidi

Erich Franz Haratsch

Pengju Shang

Abhishek Rajimwale

Eui Seok Hwang

Ming Jin

Pranay Singh

Bruce Alexander Wilson

Haitao Xia

Xiufeng Song

Chegu Vinod

Weijun Tan

Jeffrey Paul Grundvig

Craig Harmer

Richard Rauschmayer

Charles J Hickey

Jefferson E Singleton

Suharli Tedja

Dhawal Bhagwat

Englin Koay

Hao Zhong

Donna Barry Lewis

Senthil Ponnuswamy

Timothy B Lund

Prajakta Balkrishna Ayachit

Anand Rudrabhatla

Ajith Krishnamurthy

Fan Zhang

Jehuda Shemer

Mukund Purshottam Khatri

Adolfo Sandor Montero

Bing Liu

Zongwang Li

Yang Han

Kalyan Chakravarthy Gunda

Jingfeng Liu

Viswanath Annampedu

Jun Xiao

Kelly K Fitzpatrick

Keyur B Desai

Carl E Forhan

Scott M Dziak

Haotian Zhang

Timothy W Swatosh

Murthy Mamidi

Mahadev Karadigudda

Kurt J Worrell

Mukesh Sharma

Louis M Davis

Robert Alan Greene

Xiaohong W Wang

Krithika Subramanian

Shefali Gautam

Ronald S Karr

Shu Li

Oleg Kiselev

Travis Roger Oenning

Ramprasad N Chinthekindi

Mahesh Kamat

Xun Zhang

Nitin Madan

Nayak Ratnakar Aravind

Dheer Moghe

Basant Rajan

Angelo Rocco Mastrocola

Wai-Ming Richard Chan

Poornima Gupte

Srikant Viswanathan

Srisailendra Yallapragada

Shobhan Chinnam

Terry Gene Hahn

Naveen Rastogi

Frank L Wu

Li Du

Viral Kirtikumar Mehta

Andrew R Huber

Nagaraj Shyam

Omkar Anand Ekbote

Shaojie Li

Albert John Bolian

Han Fang

Harley Burger

Tariq Saeed

Pradeep Padukone

Rahul Goyal

Chetan Risbud

Sai Chivukula

Liu Jingfeng

Du Li

Foad Askari

Sirisha Kapoor

Geetha Shendge

Sampath Jayaram

Page keys are formed in a key-value store (KVS) storing metadata of a filesystem. Page keys identify pages of trees within which namespaces of logical partitions are held. Leaf pages include first and second full keys for each file. First full keys index inodes. Second full keys index filenames. Inode keys are formed in the KVS. Inode keys identify inodes of the files. Metadata is embedded into the page and inode keys such that each page key includes an identifier of a logical partition, an identifier of a snapshot taken of a namespace of the logical partition, and a page number to a page tree holding the namespace. Each inode key includes the logical partition identifier, the snapshot identifier, and an inode number of an inode to a file. Upon damage to the namespace, queries are conducted of the KVS and the namespace is recovered based on the query results.

Namespace recovery for key-value store (KVS)-persisted metadata

Metadata of a file system is maintained in a key value store. The metadata includes a namespace represented as a B+ tree having pages written to the key value store. Identifiers to the pages include a snapshot identifier and a page number. The identifiers are stored as keys in the key value store. The snapshot identifiers are used to track pages that are shared between first and second snapshots. Upon a request to write to an existing page, a determination is made from the snapshot identifiers as to whether the existing page belongs to the first or second snapshot. If the existing page belongs to the second snapshot, the write to the existing page is allowed. If the existing page belongs to the first snapshot, a copy on write (COW) is performed to generate a new page for the write.

Storing namespace metadata in a key value store to facilitate space efficient point in time snapshots

A cluster service receives a cluster message based on a removal of a first service from membership in a first node in a cluster, and requests a shared storage to generate and then provide a new access key, thereby enabling the shared storage to use the new access key to validate requests to access resources stored by the shared storage. The cluster service receives the new access key from the shared storage, and sends the new access key in at least some cluster messages to at least a second service in a second node in the cluster of nodes. The second service creates a key based on the new access key. The second service uses the key to create a request to access a resource stored by the shared storage, sends the request to the shared storage, and then accesses the resource, which was previously accessed by the first service.

Fencing off cluster services based on shared storage access keys

A distributed and deduplicating file system that stores backup data to object storage is described. A node, in a cluster of nodes, receives a write operation to back up a data file, and identifies backup data associated with the write operation. The node identifies deduplicated data by deduplicating the backup data. The cluster stores the deduplicated data to each of the buffers which corresponds to a node in the cluster. If the node determines that the size of information, which includes the deduplicated data, stored to each of the buffers has accumulated to become greater than or equal to an object threshold, then the node writes the information, which includes the deduplicated data, stored in each of the buffers to an object storage which stores data for the nodes in the cluster.

Distributed and deduplicating file system for storing backup data to object storage

One or more embodiments of the invention relates to a method of managing data in a cluster. The method includes receiving, by a global event manager of the cluster, a notification that an event has occurred on the cluster, wherein the cluster comprises a plurality of file system redirector proxy (FSRP) nodes. In response to the notification, the global event manager performs a load balancing analysis on the cluster to assign an export location of a file system export to a FSRP node of the plurality of FSRP nodes, and notifying each of the plurality of FSRP nodes in the cluster of the event, wherein the notifying results in an update of a global export table of each of the plurality of FSRP nodes of the assigning of the export location to the FSRP node.

Scaling and distributing namespaces and clients across multiple file system redirector proxies

Embodiments for performing load balancing in a filesystem of a distributed network comprising worker nodes accessing shared resources that are controlled by distributed locks to grant and prevent access from clients, by assigning a range of directory entries to each worker node, and providing feedback from each worker node to a load balancer to expose an internal state of acquired resources and other parameters of each worker node. In response to periodic updates of the directory ranges to be collocated, the system maintains directory ranges in each worker so that complete subtrees of the directory tree fit in a single range assigned to a worker. Upon receipt of a client request to access a data asset, the load balancer selects the most optimum worker to satisfy the request based on the worker internal states and other parameters.

Intelligent load balancing in a distributed system

System creates mapping of storage intent, defined for digital asset, to primary storage tier, of primary storage tiers in primary protection storage system, that matches storage intent. System receives request to store copy of digital asset, and stores the copy with storage intent in primary storage tier, based on mapping of storage intent to primary storage tier. System identifies expanded group of storage tiers comprising primary storage tiers combined with additional storage tier. If additional storage tier matches storage intent more than primary storage tier matches storage intent, which is mapped to primary storage tier, system changes mapping of storage intent to primary storage tier into mapping of storage intent, defined for digital asset, to additional storage tier. System relocates each copy of digital asset, based on mapping of storage intent to primary storage tier, to additional storage tier, based on mapping of storage intent to additional storage tier.

Intent-driven storage tiers that protect and relocate assets

Embodiments are described for providing backup resources in a multi-tier network, by providing a plurality of different storage devices, each with different operating characteristics and costs for storage of data assets, and organizing the storage devices into a plurality of tiers based on respective operating characteristics, such as based on performance versus cost parameters. Certain Service Level Agreements (SLAs) dictating storage requirements for each of the data assets to a backup program are provided to the backup system, and a mapper maps each SLA to one or more tiers of the plurality of tiers based on the storage requirements of a respective SLA to the operating characteristics of each tier.

Mapping service level agreements for backup systems to multiple storage tiers in a clustered network

Described is a system (and method) that maintains deduplication efficiency when storing data within a clustered data storage environment that implements a global namespace. To provide such a capability, the system may obtain granular data source identifying information from a client system that provides data to be backed-up by a backup component. The data source identifying information may take the form of a placement tag that is associated with the received data. The backup component may then provide such placement tags when providing the backup data to the clustered storage system. The placement tags may then be used to intelligently distribute backup files to particular storage nodes of the clustered storage system to improve deduplication efficiency.

Granular data source identification for obtaining deduplication storage efficiency within a clustered environment

A fencing service receives a cluster message based on a first service's removal from membership in a first node in a cluster, and generates an access key based on a generation identifier in the cluster message. The fencing service sends the access key to a shared storage, thereby enabling the shared storage to create signing keys based on the access key, and which are used to validate signed requests to access resources stored by the shared storage. A second service in a second node in the cluster receives the cluster message, and generates the access key based on the generation identifier. The second service accesses a resource previously accessed by the first service, by generating a signing key based on the access key and a request to access the resource stored by the shared storage, and then sending the request signed by the signing key to the shared storage.

Fencing off cluster services based on access keys for shared storage

A system creates a mapping of a storage intent, defined for a digital asset, to one of the primary storage tiers, in a primary protection storage system, which matches the storage intent. The system receives a request to store a copy of the digital asset and stores the copy with the storage intent in the primary storage tier, based on the mapping of the storage intent to the primary storage tier. Upon receiving a request to replicate the copy of the digital asset, the system creates a mapping of the storage intent to one of the secondary storage tiers, in a secondary protection storage system, which matches the storage intent. The system replicates each copy of the digital asset, which is stored in the primary storage tier, and the storage intent to the secondary storage tier, based on the mapping of the storage intent to the secondary storage tier.

Intent-driven storage tiers that protect and replicate assets

Embodiments are described for migrating data and load balancing in a multi-domain network having a clustered network partitioned into a number of separate domains. Each domain contains resources like processors and memory, as well as deduplication and compression services. A single global namespace for the network is presented by combining all of the namespaces in the domains. A multi-domain manager component with an analytics engine facilitates analytics-driven migration of data among nodes in different domains, and a load balancer component monitors environmental operating conditions of each node in the clustered network, detects nodes having operating conditions exceeding defined tolerances, and migrates data and processes from nodes exceeding the defined tolerances to other nodes not exceeding the defined tolerances.

Data migration and namespace management across domains in multi-domain clustered file systems

A distributed and deduplicating file system that stores backup metadata to object storage is described. A node, in a cluster of nodes, receives backup data associated with a write operation to back up a data file, and identifies metadata associated with deduplicated data by deduplicating the backup data. If the access frequency associated with the metadata is greater than or equal to an access threshold, and the size of the metadata is less than or equal to a storage threshold, the cluster writes the metadata to each of the memory devices corresponding to the nodes in the cluster. If the access frequency associated with the metadata is less than the access threshold, or the size of the metadata is more than the storage threshold, the node writes information which includes the metadata to an object storage that stores data objects for the nodes in the cluster.

Distributed and deduplicating file system for storing backup metadata to object storage

Mapping information identifies ranges of files, a set of front-end microservices, and assignments of the ranges to the front-end microservices. Each front-end microservice is thereby responsible for a range of files. The files are represented by segment trees and the front-end microservices handle operations involving an upper-level of the segment trees. A file system request on a file is directed to a particular front-end microservice that is responsible for handling a particular range of files within which the file falls according to the mapping information. An indication is received from a container orchestration service that a number of front-end microservices has changed. The mapping information is updated based on the change in the number of front-end microservices.

Scale out deduplicated file system as microservices

A security level tagging process to enable a user to associate a security level descriptor with a file, or a namespace directory where files and subdirectories inherit the security level descriptor from a parent directory. A parser can be used to automatically set a security level descriptor based on the contents of the file and/or attributes of files, or an administrator can associate a security level to a storage tier in the file system so that files are placed on the storage tiers with the matching security level as the file security level descriptor. The placement of the file on a storage tier depends on the data security level descriptor of the file and the security level of the storage so that files are placed on tiers where security level associated with the tier is greater than or equal to data security level of the file. Files can be migrated among storage tiers as their security levels may change.

Data security classification for storage systems using security level descriptors

Growing community of inventors

San Jose, CA, United States of America

George Mathew