Abstract: 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.

Abstract: 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.

Abstract: 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).

Abstract: 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).

Abstract: A method that is performed for backing up data. The method includes obtaining an asset backup request; and in response to the asset backup request: obtaining an asset and an asset entry associated with the asset backup request; dividing the asset into pseudo-assets using the asset entry; storing the pseudo-assets across backup storages to generate pseudo-asset backups; initiating the merging of the pseudo-asset backups to generate an asset backup; and updating asset backup metadata based on the asset backup.

Abstract: 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).

Abstract: 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).

Abstract: Techniques described herein relate to a method for performing data protection services. The method includes identifying a restoration event associated with an network attached storage (NAS) asset stored in a backup storage; obtaining backup information associated with the NAS asset; making a determination that the restoration is associated with cross platform restoration; and in response to the determination; identifying an available cross platform host of a multi-platform host environment (MPHE) using host information; and initiating restoration of the NAS asset using the cross platform host.

Abstract: Embodiments of the invention relate to methods and systems for efficiently backing up a production host. In one or more embodiments, assets are assigned to one or more slices. Depending on the type of assets assigned to a slice such as directory information versus data, the slices are assigned a flag. This flag may then be used to determine which streams a slice should be assigned to and based on the specific flags of the slices assigned to each stream, the order by which the streams are transferred to backup containers located in a backup storage may be determined. This may result in better or more efficient utilization of available connections between the containers and the production host, resulting in better utilization of system and network resources as well as a better backup and recovery performance.

Abstract: Embodiments of the invention relate to methods and systems for efficiently restoring a production host. Selected assets are restored from a plurality of slices stored on a plurality of containers in a backup storage system. In order to restore the selected assets, a hierarchical mapping of the slices is produced by analyzing a backup's metadata, from which the assets are to be restored. The hierarchical mapping is then searched for highest level slice containing the assets and then searching the lower-level slices associated with the highest-level slice to efficiently discover the slices containing the selected assets. This invention reduces and/or eliminates the need to crawl the entire slice list once the highest level is discovered; only its children need to be searched for the asset. Once the slices associated with an asset are found, they can be quickly restored from the corresponding containers which hold the assets.

Abstract: Embodiments of the invention relate to methods and systems for efficiently restoring a production host. Selected assets are restored from a plurality of slices stored on a plurality of containers in a backup storage system. In order to restore the selected assets, a hierarchical mapping of the slices is produced by analyzing a backup's metadata, from which the assets are to be restored. The hierarchical mapping is then searched for highest level slice containing the assets and then searching the lower-level slices associated with the highest-level slice to efficiently discover the slices containing the selected assets. This invention reduces and/or eliminates the need to crawl the entire slice list once the highest level is discovered; only its children need to be searched for the asset. Once the slices associated with an asset are found, they can be quickly restored from the corresponding containers which hold the assets.

Abstract: Embodiments of the invention relate to methods and systems for efficiently backing up a production host. In one or more embodiments, assets are assigned to one or more slices. Depending on the type of assets assigned to a slice such as directory information versus data, the slices are assigned a flag. This flag may then be used to determine which streams a slice should be assigned to and based on the specific flags of the slices assigned to each stream, the order by which the streams are transferred to backup containers located in a backup storage may be determined. This may result in better or more efficient utilization of available connections between the containers and the production host, resulting in better utilization of system and network resources as well as a better backup and recovery performance.

Abstract: Embodiments of the invention relate to methods and systems that improve the operation of one or more computing devices by allowing backups and restorations to be performed on files and folders that are normally unavailable for normal restoration. By utilizing the backup's meta-data, a backup agent can receive an indication that a file or folder is not available and take appropriate actions so that the files and folders that are normally not available can be properly restored. Making it possible to efficiently perform a backup of a file-system that can be restored even when files and/or folders are normally unavailable to be restored normally.

Abstract: A method for performing data backup includes: receiving a backup request specifying a file where the file is stored in a shared storage. Additionally, in response to the backup request: retrieving, by a primary data node, properties of the file; determining, by the primary data node, resource availability for plurality of secondary data nodes where the primary data node and the plurality of secondary data nodes is operatively connected to the shared storage and a backup storage; logically dividing, by the primary data node, the file into a plurality of segments using at least the properties of the file; and coordinating, by the primary data node, the backup of the file using the plurality of segments and the resource availability of the plurality of secondary data nodes.

Abstract: Embodiments of the invention relate to methods and systems for backing up user defined logical assets. In accordance with one or more embodiments, a user may define a logical asset type prior to a backup being performed. The user may define the logical asset type based on any rules, filters, or attributes of files and/or folders stored in a file system. Once the user has defined the asset type, the system may utilize file-system meta-data to quickly ascertain which files and folders meet the definition of the logical asset type, allowing for the backup of the user defined asset to be performed with minimal additional workload by the production hosts, clients, backup agents, and other associated components of the system.

Abstract: Embodiments of the invention relate to methods and systems that improve the operation of one or more computing devices by allowing backups and restorations to be performed on files and folders that are normally unavailable for normal restoration. By utilizing the backup's meta-data, a backup agent can receive an indication that a file or folder is not available and take appropriate actions so that the files and folders that are normally not available can be properly restored. Making it possible to efficiently perform a backup of a file-system that can be restored even when files and/or folders are normally unavailable to be restored normally.

Abstract: A method for performing a data backup process on a cluster includes: obtaining a backup generation request for virtual machines; in response to obtaining the backup generation request: generating a first set of backup groupings based on the backup generation request where each of the first set of backup groupings includes at least one of the virtual machines; issuing a disable migration command to a plurality of production hosts where each of the plurality of production hosts is associated with at least one of the virtual machines; identifying, after the issuing, a virtual machine of the virtual machines that is migrating; removing, based on the identifying, the virtual machine from the first set of backup groupings to obtain a second set of backup groupings where the virtual machine is placed in an excluded group after the removing; and backing up the second set of backup groupings.

Abstract: Techniques described herein relate to a method for performing data protection services for data stored in a shared storage. The method may include identifying, by a primary data node, a protection policy event initiating performance of data protection services for data stored in the shared storage used by the primary data node and secondary data nodes; in response to identifying the protection policy event: obtaining primary data node monitoring information associated with the primary data node; obtaining secondary data node monitoring information associated with the secondary data nodes; assigning at least one resource limit to the primary data node and the secondary data nodes based on the primary data node monitoring information and the secondary data node monitoring information; and initiating performance of the data protection services by the primary data node and the secondary data nodes based on the assigned at least one resource limit.

Abstract: Embodiments for managing metadata in a high density network attached storage system. A change file list is obtained though external or internal crawler processes. A slicer creates multiple slices of the entire fileshare to enable parallel backup of the slices. A backup engine creates a separate backup containers and separate metadata files for each slice. The individual metadata files are combined into a single consolidated metadata file, and the individual metadata files are then deleted. The consolidated metadata file contains all of the elements comprising the entire fileshare, and a corresponding container ID is also added to each entry of the file. Another table contains details of the sub-assets and their backup properties. A backup agent obtains the backup IDs for the individual sub-assets, using a job ID field for a backup query operating on the single consolidated metadata file.

Abstract: 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.