Abstract: A method of backing up data includes backing up, using a processor, multiple save sets of data to a first backup data storage; obtaining a first save set from the first backup data storage after the backup of the first save set has completed on the first backup data storage; determining that the first backup data storage is capable of concurrent read and write operations; and replicating, based at least in part on the determining, the first save set onto a second backup data storage while backing up of one or more other save sets of the multiple save sets to the first backup data storage is pending.

Abstract: Concurrently backing up data streams based on backup time estimates is described. A system identifies multiple data streams scheduled for backup. The system identifies multiple backup time estimates corresponding to the multiple data streams. The system creates a ranked relational sequence based on the multiple backup time estimates. The system concurrently backs up the multiple data streams based on a concurrency limit and the ranked relational sequence.

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: A discovery is made of an object to be backed up on a storage array of a client. An object mapping is generated that maps the object to a LUN of the storage array where the object is located. The object mapping is stored at a backup server. A snapshot of the storage array is obtained. The object mapping is reviewed to identify on the snapshot the object to be backed up and the object is backed up to a backup storage unit.

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: A data protection policy generator is described. A first set of selections is received to generate a first task. The first set of selections includes selections of a first source, a first data set, a first destination, and a first execution schedule. A second set of selections is received to generate a second task. The tasks may be any of a backup copy task, a clone task, a backup verification task, a snapshot creation task, a snapshot backup task, a snapshot clone task, a backup delete task, a backup query task, or a restore task. The second set of selections includes selections of a second source, a second data set, a second destination, and a second execution schedule. The first data destination includes the second data source. Execution of the first task and the second task is enabled based on at least the first execution schedule and the second execution schedule.

Abstract: A system for auto-determining a backup level comprises an input interface and a processor. The input interface is configured to receive backup information. The processor is configured to determine whether a backup criterion is satisfied, based at least in part on the backup information, and in the event the backup criterion is satisfied, change the backup level.

Abstract: Methods and apparatuses select service tasks according to allocations of an available usage rate of a common processing resource are described. An ordering relationship is updated among the service tasks. E service task can have a rate of usage of the common processing resource. Each service may be associated with one of multiple task types. An allocation of the available rate of usage may be determined among the task types. The allocation can indicate a portion of the available rate of usage for each task type. The service tasks may be selected according to the allocation and the ordering relationship. At least one of the selected service tasks is associated with each task type associated with the service tasks.

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: Concurrently backing up data streams of multiple computers based on backup time estimates is described. A system queries multiple computers to identify multiple data streams scheduled for backup. The system queries the multiple computers to identify multiple backup time estimates corresponding to the multiple data streams. The system creates a ranked relational sequence based on the multiple backup time estimates. The system instructs the multiple computers to provide the multiple data streams based on the ranked relational sequence. The system concurrently backs up the multiple data streams based on a concurrency limit and the ranked relational sequence.

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: Parent backup application driving of children backup applications is described. An instruction for a child backup application to execute a child backup task is communicated from a parent backup application to the child backup application. An instruction for a second child backup application to execute a second child backup task may be communicated from the parent backup application to the second child backup application. An execution of the child backup task by the child backup application is communicated from the child backup application to a parent backup application. An execution of the second child backup task by the second child backup application may be communicated from the second child backup application to the parent backup application. A parent backup task is executed by the parent backup application. At least one child backup application inherently lacks a functionality to execute the parent backup task as the parent backup application executes the parent backup task.

Abstract: A system for auto-determining a backup level comprises an input interface and a processor. The input interface is configured to receive backup information. The processor is configured to determine whether a backup criterion is satisfied, based at least in part on the backup information, and in the event the backup criterion is satisfied, change the backup level.

Abstract: A backup agent issues to a virtual machine management service (VMMS) a request to export a virtual machine (VM). The VMMS generates a configuration file associated with the export that cannot be accessed by the backup agent because the file is encrypted. A full backup of the exported VM is performed. A first backup check point corresponding to the full backup is created. After the full backup, a second backup check point is created. The agent issues to the VMMS a request to export changes to the VM between the first and second backup check points. An incremental backup of the exported changes is performed and a backup components document is created. A synthetic full backup based on the incremental and full backups is created and restoration of the VM from the synthetic full backup is based on the information in the backup components document.

Abstract: Techniques for determining characteristics of data blocks being accessed in a storage system are described herein. According to one embodiment, an input/output (IO) request is received for accessing a first data block of a first file stored in a storage system. The first file is one of the files stored in the storage system and each file contains multiple data blocks. In response to the request, a block-based monitor executed in a memory by a processor accesses a set of monitoring rules to determine whether the first file should be monitored. If so, the block-based monitor captures statistics data associated with the first data block and stores the statistics data of the first data block in a statistics database maintained in a persistent storage device. The statistics database stores statistics data of the data blocks of files monitored and captured based on the set of monitoring rules.

Abstract: Exemplary methods for dynamically performing multiple save streams include in response to receiving a request to perform backup of an aggregate backup data, splitting the backup data into savepoints based on a splitting policy. In one embodiment, the method includes creating a first set of directors, each director responsible for backing up one of the savepoints. The method further includes allocating save streams to each of the directors, wherein each save stream is used by the corresponding director for backing up its savepoint. In one embodiment, in response to receiving an indication from a first director of the first set of directors that its savepoint has been backed up, creating a second set of directors, and allocating one or more save streams from a number of save streams freed by the first director to a second (unfinished) director from the first set of directors.

Abstract: A method of backing up data including backing up, using a processor, a backup data set to a first backup data storage; storing the backup data set in a native file format in a first storage area of the first backup data storage; generating a data stream file of the backup data set in a data stream file format, the data stream file being a logical copy of the backup data set and containing metadata of the backup data set; storing the data stream file in a second storage area of the first backup data storage; and replicating, using the data stream file, the backup data set onto a second backup data storage.

Abstract: Disclosed are systems and methods relating to the deployment of an application. A plurality of nodes in one or more clusters of nodes may be identified. Inventory information for each of the plurality of nodes may be retrieved. The inventory information may provide configuration and state information associated with each node. For example, the inventory information retrieved from the plurality of nodes may include an internet protocol address or a hostname associated with each the plurality of nodes, and a version of software installed on each of the plurality of nodes. An order for deploying the software application may be determined based on the retrieved inventory information. The order may identify a sequence in which the software application is deployed to at least one of the plurality of nodes. The software application may be deployed to at least one of the plurality of nodes based on the determined order.

Abstract: Disclosed are systems and methods relating to profiling software and configuration information associated with one or more entities. In various implementations, software and configuration information associated with one or more entities may be retrieved. The retrieved software and configuration information may provide state information associated with the one or more entities. The retrieved information may be processed to identify one or more changes in the software and configuration information that is associated with the one or more entities. A report may be generated based on the retrieved information. The report may display identified changes in a state for at least one entity based on the changes in the software and configuration information that were identified during the processing.

Abstract: Techniques for reducing and discouraging sending large scale emails are described herein. According to one embodiment, in response to a first email received from a sender to be sent to a list of recipients, a distribution cost of the first email is determined based on content of the first email and the recipients. An email client application is to present a first graphical user interface (GUI) page to the sender prompting a confirmation from the sender, where the first GUI page includes information indicating a size of the first email and a number of recipients, if the distribution cost of the first email is above a first predetermined threshold. In response to a positive confirmation from the sender, the first email is sent to the intended recipient.