Abstract: One example method includes gathering information regarding filesystem resources, based on the system resource information, identifying a thread pool size, starting a thread pool having the thread pool size, where the thread pool size is dynamically adjustable based on changes in the system resources, crawling a filesystem and identifying crawl jobs to be performed, adding the crawl jobs to the thread pool, and performing the crawl jobs. The method may further include slicing data in one or more directories that have been crawled.

Abstract: One example method includes, in response to completion of a portion of a crawling process performed in a filesystem, instantiating a slice creation process, receiving slicing criteria concerning the slice creation process, slicing filesystem data to create slices according to the slicing criteria, and servicing a query by returning a list that lists one or more of the slices. The slicing criteria may include a specified number of slices and/or a specified size for the slices.

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

Abstract: 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 associated with the file system; identifying, using the slice list, changed data include in the file system; generating change rates associated with each slice; grouping the slices based on the change rates 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.

Abstract: A method and system for maintaining live database data across hybrid storage. Specifically, the disclosed method and system entail accessing live backup database data in part residing on local storage and in part residing on remote storage. That is, on occasion, available local storage capacity may fall short of the required free storage space to accommodate the full restoration or recovery of a given database. Accordingly, to overcome this shortfall, the disclosed method and system detect and cycle the recovery of frequently accessed asset (or database) data files, of the given database, from remote storage onto local storage.

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: In one example, a method includes receiving, at a physical proxy node, a backup request from a client outside the cluster environment, the backup request identifies a VM that is to be backed up, and including data that resides on a virtual federated database that is an element of the cluster environment and to which respective databases of each node of the cluster environment are mapped, and the backup request is received at the physical proxy node due to the position of the physical proxy node in a PSOL. Next, initiating, with an agent at the physical proxy node, a save program on the physical proxy node, and initiating, with the save program, a secondary save process on the physical proxy node that is a federated backup process and includes reading the VM identification from the backup request, and backing up the VM identified in the backup request.

Abstract: In one example, a method includes obtaining cluster and machine configuration information, sending a restore request for one or more machines, and loading a backup of a virtual machine, the backup having been created by a federated backup process involving the physical proxy node, and the virtual machine includes data that resides on a virtual federated database that is an element of a cluster environment and to which respective databases of each of a plurality of nodes of the cluster environment are mapped. Next, the virtual machine is taken offline after the backup of the virtual machine has been loaded, and after the virtual machine has been taken offline, the virtual machine is removed from the node where it resides. The backup of the virtual machine is then restored, and the restored virtual machine brought online, after which the restored virtual machine is enabled as a cluster-wide virtual machine.

Abstract: A backup manager for managing backup services includes persistent storage and a backup analyzer. The persistent storage includes a backup data repository and protection policies. The backup analyzer identifies a new backup stored in backup storage; performs a backup compatibility analysis on the new backup to determine inter-backup compatibility of the identified new backup; updates the backup data repository based on the inter-backup compatibility to obtain an updated backup data repository; and modifies a backup schedule using the updated backup data repository to meet a requirement of a protection policy of the protection policies.

Abstract: In general, embodiments of the invention relate to a method and system for backing up data. More specifically, embodiments of the invention are directed to using a scalable backup infrastructure that enables portions of the backup process to be performed in parallel. The amount of parallelism that may be implemented in the backup process may be dynamically adjusted based on customer requirements and/or limitations on the computing devices, backup storage, and/or production storage that are used to perform the backup process.

Abstract: A manager for providing services to clients includes persistent storage and an orchestration manager. The persistent storage includes protection policies. The orchestration manager obtains a backup from a client of the clients based on a protection policy of the protection policies; makes a determination that an application catalog associated with the client is not stored in backup storages; in response to making the determination: obtains the application catalog from the client; stores the application catalog in the backup storages; and stores the obtained backup in the backup storages.

Abstract: A method for processing backup generation requests includes receiving a backup generation request; in response to receiving the backup generation request: identifying a backup to transfer to a backup storage, the backup includes data blocks; performing a data allocation analysis on the backup to generate an offset table; dividing, based on at least the offset table, the backup into sub-portions, each of the sub-portions includes at least one of the data blocks; and transferring, using at least two data streams, at least two of the sub-portions to a backup storage.

Abstract: A backup storage for managing backups of clients includes persistent storage and a backup analyzer. The persistent storage includes the backups, protection policies, and an early deletion schedule. The backup analyzer obtains a request to analyze a protection policy of the protection policies; in response to obtaining the request: obtains backup data information associated with the protection policy; makes a determination, based on the backup data information and the protection policy, that a portion of the backups associated with the protection policies overprotect a client of the clients associated with the protection policy; and modifies the early deletion schedule based on the determination to obtain a modified early deletion schedule.

Abstract: Embodiments for a method of backing up virtual hard disks by: parsing a list of base parent and differencing disks to identify disk parameters and child disks of immediate parent disks; creating a differencing disk chain in reverse time order of modification of the base parent disk starting from the base parent disk to a latest child differencing disk; identifying changed sectors in each child disk starting from the latest child differencing disk; creating a list detailing a respective differencing disk, sector offsets and logical data sector index for each changed sector; iteratively adding updated sectors to the list for latest changed sectors that were not previously added to the list by a later child disk by reading the changed sectors from their respective child disk; and merging, in a single step, the changed sectors read from their respective child disks into the base parent disk.

Abstract: A backup storage for managing backups of clients includes persistent storage and a backup analyzer. The persistent storage includes the backups, protection policies, and an early deletion schedule. The backup analyzer obtains a request to analyze a protection policy of the protection policies; in response to obtaining the request: obtains backup data information associated with the protection policy; makes a determination, based on the backup data information and the protection policy, that a portion of the backups associated with the protection policies overprotect a client of the clients associated with the protection policy; and modifies the early deletion schedule based on the determination to obtain a modified early deletion schedule.

Abstract: A backup manager for managing backup services includes persistent storage and a backup analyzer. The persistent storage includes a backup data repository and protection policies. The backup analyzer identifies a new backup stored in backup storage; performs a backup compatibility analysis on the new backup to determine inter-backup compatibility of the identified new backup; updates the backup data repository based on the inter-backup compatibility to obtain an updated backup data repository; and modifies a backup schedule using the updated backup data repository to meet a requirement of a protection policy of the protection policies.

Abstract: A manager for managing generation of backups for clients includes persistent storage and a backup manager. The persistent storage stored protection policies associated with the clients and native backup functionality information associated with the clients. The backup manager programmed obtains a portion of the native backup functionality information from a client of the clients; obtains at least one protection policy of the protection policies that is associated with the client; makes a determination that the at least one protection policy and the portion of the native backup functionality information are unique; in response to the determination: generates modifier data based on: the portion of the native backup functionality information and the at least one protection policy; and generates a backup for the client using a modifier associated with the modifier data.

Abstract: A manager for providing services to clients includes persistent storage and an orchestration manager. The persistent storage includes protection policies. The orchestration manager obtains a backup from a client of the clients based on a protection policy of the protection policies; makes a determination that an application catalog associated with the client is not stored in backup storages; in response to making the determination: obtains the application catalog from the client; stores the application catalog in the backup storages; and stores the obtained backup in the backup storages.

Abstract: An optimized solution for accessing virtual machine state while restoration of a respective virtual machine is underway. Specifically, the optimized solution disclosed herein implements a fetching mechanism for retrieving granular virtual machine state over a network and/or from a remote storage system. The fetching mechanism leverages block allocation information in parallel with disk caching to provide instant (or near instant) access to a virtual machine state while also, concurrently, restoring the respective virtual machine.

Abstract: Techniques for virtual proxy based backup of virtual machines in a cluster environment are disclosed. In some embodiments, each of a subset of virtual machines hosted by physical nodes in a cluster environment is configured as a virtual proxy dedicated to backup operations. During backup, data rollover of each virtual machine in the cluster environment that is subjected to backup is performed using a virtual proxy.