Abstract: A set of logical containers are maintained in a cache, each logical container corresponding to a portion of a main snapshot catalog. First metadata of a first snapshot created by a first snapshot appliance is examined. Based on the first metadata examination, the first snapshot is cataloged into a first logical container. Second metadata of a second snapshot created by a second snapshot appliance is examined. Based on the second metadata examination, the second snapshot is cataloged into a second logical container, separate from the first logical container. A request is received to perform an operation involving one of the first or second snapshots. The request is matched to one of the first or second logical containers. The one of the first or second logical containers is searched to retrieve a snapshot responsive to the request without searching another of the first or second logical containers.

Abstract: Rules are stored for dynamically managing virtual machine backups in a computing environment. Each rule includes a triggering condition and an action to be performed when the triggering condition is satisfied. A selection of at least one rule to apply to the environment is received. The environment is polled to detect changes. The selected at least one rule is evaluated against a detected change. Based on the evaluation, a determination is made that a triggering condition has been satisfied. An action specified in the at least one rule is performed where the action includes one of commissioning a new virtual backup proxy or decommissioning an existing virtual backup proxy.

Abstract: Data protection using change-based measurements in block-based backup is disclosed. Block change information indicating an extent of change associated with a volume may be determined. The block change information may be based at least in part on stored information indicating monitored changes to blocks in the volume. A backup operation may be initiated based at least in part on the determined block change information.

Abstract: Retrieving backup parameters for recovery is described. A clone copy is created of a backup file stored on a disk. The clone copy is stored on an external destination node including an external disk and/or a tape. Backup parameters are stored to a backup catalog. The backup parameters identify a location of the clone copy. A request is received to recover the clone copy. The backup parameters are retrieved from the backup catalog. The clone copy is recovered from the external destination node based on the backup parameters. The clone copy is restored to a database associated with the backup file.

Abstract: The system for backing up data comprises an input interface configured to receive an input set of files. The system for backing up data additionally comprises a processor configured to add modified objects to a list of modified objects in the set of files, and, in the event it is determined to provide the list of modified objects to a backup process, provide the list to the backup process.

Abstract: A system for image recovery comprises an input interface and a processor. The input interface is configured to receive a block backup volume that can be mounted. The processor is configured to determine a merged chain map by consolidating one or more incremental chain maps and to store an image using the merged chain map and a volume map.

Abstract: Data protection using change-based measurements in block-based backup is disclosed. Block change information indicating an extent of change associated with a volume may be determined. The block change information may be based at least in part on stored information indicating monitored changes to blocks in the volume. A backup operation may be initiated based at least in part on the determined block change information.

Abstract: Embodiments described herein provide for a system and associated logic to enable browsing of a federated backup having a plurality of portions, each portion separately generated and indexed by a plurality of nodes. In one embodiment, the system performs a federated backup by generating a unique identifier on a primary node and providing the unique identifier to each secondary node tasked with generating the plurality of portions. The secondary nodes associate the unique identifier with each of the plurality of portions. The unique identifier can then be used by a recovery UI to generate and display a consolidated view of the plurality of portions.

Abstract: Systems and methods for disseminating backup data sets to targets. Backup data sets are classified with an attribute. A gateway device between the backup application and potential target destinations for the backup data set determines where to send the backup data set based on the attribute.

Abstract: A system for image recovery comprises an input interface and a processor. The input interface is configured to receive a block backup volume that can be mounted. The processor is configured to determine a merged chain map by consolidating one or more incremental chain maps and to store an image using the merged chain map and a volume map.

Abstract: A system for displaying a performance dashboard comprises an input interface, a processor, and an output interface. The input interface is configured to receive log data. The log data comprises a set of process log entries. The processor is configured to determine one or more daemon response times and to determine dashboard information. The dashboard information is based at least in part on the log data and the one or more daemon response times. The output interface is configured to provide the dashboard information.

Abstract: A system for displaying a performance dashboard comprises an input interface, a processor, and an output interface. The input interface is configured to receive log data. The log data comprises a set of process log entries. The processor is configured to determine one or more daemon response times and to determine dashboard information. The dashboard information is based at least in part on the log data and the one or more daemon response times. The output interface is configured to provide the dashboard information.

Abstract: Backup storage is configured to automatically take one or more snapshots of a protected device. After a plurality of snapshots of the protected device have been automatically taken by the backup storage, the backup storage is communicated with in order to catalog metadata associated with the plurality of snapshots.

Abstract: Backup policies specifying backup frequencies are stored. An identification of a logical unit number (LUN) to which a virtual volume of a virtual machine has been mapped and an input/output (IO) rate of the LUN are gathered from a storage array. A backup policy having a range of IO rates that correspond to the IO rate of the LUN gathered from the storage array is selected. The virtual volume is backed up according to a particular backup frequency as specified in the selected backup policy.

Abstract: A backup is performed by collecting in a report database attributes associated with a filer and backup application. Rules are stored in a rule database specifying one or more backup configuration settings to be applied when a rule is satisfied. A request is received from the backup application to perform a backup of a dataset stored on the filer. Attributes associated with the filer and backup application are fetched from the report database. A rule from the rule database is evaluated against attributes fetched from the report database and associated with the filer and backup application. Based on the rule evaluation, a configuration setting for the backup is generated. The filer is instructed to perform the backup according to the configuration setting.

Abstract: Systems and techniques are provided for managing performance of a backup environment. A set of rules are stored, with each rule specifying a threshold value of a backup configuration parameter. Configurations of the backup environment are periodically obtained. Each obtained configuration includes a current value of the backup configuration parameter. A determination is made for each configuration as to whether the current value exceeds a suggested value, where the suggested value is based on the threshold value. If the current value exceeds the suggested value, an entry including an alert of a first type is written to a log. The log is analyzed, and if the frequency of entries in the log including alerts of the first type exceeds a threshold frequency, an entry including an alert of a second type, different from the first type, is written to the log. The threshold value of the backup configuration parameter may specify a maximum number of backup streams or a maximum number of backup clients, for example.

Abstract: Methods and systems are described for grouping one or more save sets into a consistency group, the save sets being located across one or more client computers in a network, and for performing backup and recovery operations over a consistency group. According to one embodiment, a consistency group operation request is received by a backup system on a main server, the request indicating that a backup or recovery operation is to be performed over the consistency group. In response, the backup system retrieves information regarding the consistency group's save sets, and sends a save set operation request to each client computer instructing the client computer to perform the backup or recovery operation on any save sets within the consistency group.

Abstract: A system for discovering new backup clients is disclosed. The system comprises an input interface and a processor. The input interface is configured to receive a notice from a backup client. The processor is configured to provide an indication of the notice and select a configuration mode from a set of available configuration modes.

Abstract: Offloaded data protection based on virtual machine snapshots is described. A system identifies a virtual machine associated with a backup application. The system identifies a storage identifier associated with a virtual machine storage management tool and the virtual machine. The system creates a snapshot of the virtual machine and an identifier of the snapshot by prompting a storage array, which is associated with the virtual machine storage management tool, with the storage identifier. The system mounts the snapshot to a proxy server. The system creates a backup based on the snapshot by prompting the backup application with the identifier of the snapshot.

Abstract: A backup and recovery architecture for applications compatible with the Microsoft Windows Volume Shadow Copy Service (VSS) includes a backup client module that includes an orchestration engine, an application manager, a common requestor, and a save transports component. The client module interacts with the VSS on the client in the generation of a shadow copy. Data is backed up from the shadow copy to a backup storage server. In various specific embodiments, the application manager includes functions that are application-specific and the orchestration engine includes functions that are not application-specific. A single consolidated log may be generated by the backup client module for a backup or recover operation.