Dell Products Inc.

Emc IP Holding Company LLC

Emc Corporation

Upanshu Singhal

Shelesh Chopra

Matthew Dickey Buchman

Soumen Acharya

Scott Forrest Bingham

Chandra Prakash

Sunil Kumar Yadav

Manish Sharma

Archit Seth

Ashish Kumar

Patrick M Simonich

Chakraveer Singh

Lalita Dabburi

Akansha Purwar

Rahul Bhardwaj

Kumari Priyanka

Shivakumar Kunnal Onkarappa

Asif Khan

Shilpa Mehta

Pradeep Mittal

John C Rokicki

Poornima Ramu

Venkatesha Murthy

Adam E Brenner

Nitin Kumar

Aaditya Rakesh Bansal

Suman Chandra Tokuri

Sanjeev Kumar Lohchab

Aaditya Rakesh

Sairam Veeraswamy

Ravi Vijayakumar Chitloor

Navneet Upadhyay

Krishnendu Bagchi

Anupam Chakraborty

Elango Chockalingam

Aditya Kapoor

Vedavathi Ht

Rintu Kumar Kanp

LahariCharan Bejjanke

Nancy Jain

Amarendra Behera

Tushar Dethe

Sharath Talkad Srinivasan

Mu Chai

Anurag Bhatnagar

Manjesh Venkatanarayana Chikkanayakanahally

Peter Armorer

Nikhil Ambastha

Pawan Singh

Satyendra Nath Sharma

Srikanth Venkataraman

Sudha Narayanan

Prakash Venkatanarayanan

Yash Karakalli Sannegowda

George Shioyama

Tom Frencel

Sowmya Devarahalli Nanjappa

Rock Brown

Sreeman Sunku

Anju Singisetty

Hema Basavaraju

Syed Razi Rasool

Shivam Chaturvedi

Sanjeev Lochab

Razi Syed

Sekhar Samala

Abhishek Sharma

Pradeep Annappa

Milind Parvatikar

A method for sizing backup infrastructure. The method includes: receiving a sizing request including an asset protection policy covering an asset of the backup infrastructure, the asset protection policy at least specifying the asset; based on receiving the sizing request: creating an asset snapshot of the asset; mounting the asset snapshot to obtain a mounted asset snapshot through which asset snapshot data of the asset snapshot is accessible; partitioning the asset snapshot data into a plurality of asset snapshot data slices; computing, at least based on a cardinality of the plurality of asset snapshot data slices, a number of proxy nodes of the backup infrastructure required to collectively perform a prospective backup operation entailing the asset snapshot data; and providing, in reply to the sizing request, a sizing response at least specifying the number of proxy nodes required to collectively perform the prospective backup operation.

Optimal environment sizing for performing asset backup operations

A method for performing a backup operation, the method comprising receiving a backup request for an asset, partitioning, based on available capacity in a proxy infrastructure, a plurality of slices of the asset into a plurality of backup sessions, wherein each backup session comprises a separate portion of the slices, wherein the plurality of slices are associated with a queue, sending a first reservation request to the proxy infrastructure, wherein the first reservation request specifies the plurality of backup sessions, making a first determination that a first portion of the plurality of backup sessions was successfully reserved and that a second portion of the plurality of backup sessions was unsuccessfully reserved, sending a request to initiate the first portion of the plurality of backup sessions on the proxy infrastructure, and sending the second portion of the plurality of backup sessions to the queue based on the first determination.

Preventing resource starvation in backup session

A method for checking of asset protection infrastructure includes: receiving a request specifying an asset source, an asset, and a target storage; performing a check of the asset source to obtain an asset source configuration state; performing a second check of the target storage to obtain a target storage configuration state; extracting an asset source connection attempt result from the asset source configuration state; extracting a target storage connection attempt result from the target storage configuration state; making a determination that the asset source connection attempt result and target storage connection attempt result both reflect a successful result; performing, based on the determination, an asset backup configuration check of a backup operation involving the asset to obtain an asset backup configuration state; generating a response including the asset source configuration state, asset backup configuration state, and target storage configuration state; and returning the response in response to the request.

Configuration checking of asset protection infrastructure

A method for performing a backup operation, the method comprising receiving a backup operation request for an asset, partitioning a plurality of slices of the asset into a plurality of backup sessions, wherein each backup session comprises a separate portion of the plurality of slices, sending a first backup request to a proxy manager to initiate a backup session of the plurality of backup sessions, wherein initiating the backup session comprises: instantiating a container on the one compute node, wherein the backup session operates within the container, receiving a notification that one of the plurality of slices in the backup session has been processed, and sending, based on the notification, a second backup request to the proxy manager to add a new slice to the backup session, wherein the new slice is associated with a second asset.

Orchestrating backup sessions for efficient resource usage

A method for performing a backup operation, the method comprising receiving a backup operation request for an asset, identifying a queue comprising the plurality of slices, wherein each slice references a separate portion of the asset, sending a first backup request to a proxy manager to instantiate a container for each of a plurality of backup sessions, wherein each backup session corresponds to a slice of the plurality of slices, receiving, from the proxy manager, a notification that one of the number of backup sessions is complete and a corresponding container has been torn down, making a second determination that there is an additional slice on a second queue associated with a second asset, and sending, based on the second determination, a backup request to the proxy manager to instantiate a new container for the additional slice associated with the second asset.

Orchestrating per-slice per-container backup sessions for efficient resource usage

One example method includes, in a network attached storage platform, determining a size of a slice of data that is included in a share of the network attached storage platform, when the size of the slice exceeds a threshold, re-slicing the slice to generate multiple new slices, and each of the new slices has a size that is smaller than the threshold, and when all slices in the share have been evaluated in terms of their respective sizes, generating a slice list that includes the new slices.

Balancing of slices with consolidation and re-slicing

A method, non-transitory computer readable medium, and a system for intra-backup anomalous object management and post-backup exclusion rule creation. Enterprise information technology environments often include any number of assets maintaining vast quantities of data and state. Any asset, in turn, may be riddled with various anomalous objects that tend to cause backup failure. Embodiments described herein address backup failure due to the presence of anomalous objects by, while any number of assets undergo backup, objects across said asset(s) may be assessed against object exclusion lists, populated during a pre-backup stage, to identify any anomalous objects of said objects. Once identified, the anomalous object(s) (or metadata descriptive thereof) may be recorded as backup metadata, which may be used in the post-backup creation of one or many exclusion rule(s). The exclusion rule(s) impact, and thus adjust, the backup policy/policies associated with the asset(s) on which the anomalous object(s) had been identified.

Intra-backup anomalous object management and post-backup exclusion rule creation

Embodiments of the invention relate to methods and systems for efficiently performing one or more backups of assets stored on a shared storage. In one or more embodiments, the assets are sliced into a plurality of slices and the size of the slices is determined based on a maximum recommended number of connections that can be used and either a previous backups number of connections used, or the total number of connections currently used. The recommended number of connections to use is also calculated based on system telemetry. By changing the size of the slices, one or more embodiments of the invention may ensure that the backup is performed as efficiently as possible. This may result in better utilization of system and network resources as well as a better backup and recovery performance.

Storage array aware dynamic slicing of a file system

A method comprises requesting and receiving from a cloud mobility platform metadata for accessing one or more file systems which have been tiered to cloud storage, and writing the metadata to at least one backup storage location. In the method, a plurality of stub files are read, the plurality of stub files corresponding to a plurality of files of the one or more file systems which have been tiered to cloud storage. The plurality of stub files are written to the at least one backup storage location.

Data protection for stub files and cloud metadata

A method, non-transitory computer readable medium, and a system for pre-backup anomalous object detection and exclusion rule creation. Enterprise information technology environments often include any number of assets maintaining vast quantities of data and state. Any asset, in turn, may be riddled with various anomalous objects that tend to cause backup failure. Embodiments described herein address backup failure due to the presence of anomalous objects by, during a pre-backup stage, examining any number of assets to identify any anomalous objects there-within. Once identified, the anomalous object(s) (or metadata descriptive thereof) may be recorded within a backup skip list and, subsequently, excluded from the current and/or any future backup(s). Exclusion of the anomalous object(s), from said backup(s), may be enforced through the automatic creation of one or many exclusion rule(s) that impact, and thus adjust, the backup policy/policies associated with the asset(s).

Pre-backup anomalous object detection and exclusion rule creation

A method for managing network attached storage (NAS) assets obtaining, by a backup manager, a backup request for backing up the NAS assets, in response to the backup request: determining a number of streams available to be performed in parallel by a set of backup agents, obtaining a set of slices associated with the NAS assets, performing a categorization on the set of slices based on metadata associated with the set of slices to obtain a set of batches, initiating a slice distribution of the set of slices to the set of backup agents based on the set of batches and the number of streams, and storing the set of slices in a backup storage system.

System and method for slice distribution of network attached storage assets based on slice metadata

Techniques described herein relate to a method for performing pre-backup tasks. The method includes obtaining, by a proxy host, a snapshot request associated with a full backup of a file system stored in a network attached storage (NAS) from a backup manager; in response to obtaining the snapshot request: instantiating a NAS container to obtain a snapshot of the file system; providing the snapshot to the NAS container; after providing the snapshot to the NAS container: generating, using the snapshot, slices associated with the file system; sorting the slices based on average file sizes associated with each slice; grouping the slices based on the average file sizes and group criteria to generate slice groups; generating a slice list specifying the slices and the slice groups; and providing the slice list to the backup manager.

Method and system for grouping data slices based on average data file size for data slice backup generation

Embodiments of the invention relate to methods and systems for efficiently backing up a production host. In one or more embodiments, the size of slices associated with certain preset asset types are altered. By leveraging metadata of previous backups performed on the assets/hosts, one or more embodiments of the invention are able to determine the types of assets being backed up. Based on these determinations, some asset types may be assigned to slices having a larger size, while other assets may be assigned to slices having smaller sizes as appropriate for type of asset. Thus, various embodiments may improve the utilization of system and network resources.

Dynamic slicing of filesystem data with application awareness

A method for managing data protection includes: obtaining metadata associated with a backup from a backup storage; performing analysis on the metadata using an analysis engine to generate an analysis result; generating a data protection strategy using the analysis result; and providing the data protection strategy to a production agent.

Method and system for generating and implementing a data protection strategy using metadata

Techniques described herein relate to a method for performing pre-backup tasks. The method includes obtaining, by a proxy host, a snapshot request associated with an incremental backup of a file system stored in a network attached storage (NAS) from a backup manager; in response to obtaining the snapshot request: instantiating a NAS container to obtain a snapshot of the file system; providing the snapshot to the NAS container; after providing the snapshot to the NAS container: retrieving a previously generated slice list and backup metadata associated with the file system; identifying, using the backup metadata and the slice list, data types associated with each of the slices; grouping the slices based on the data types and group criteria to generate slice groups; generating an updated slice list specifying the slices and the slice groups; and providing the updated slice list to the backup manager.

Method and system for grouping data slices based on data file types for data slice backup generation

Growing community of inventors

Bengaluru, India

Upanshu Singhal