Abstract: In one example, a method can be performed that involves receiving a backup request specifying: one or more files to be backed up; a group of one or more categories, each of which corresponds to a respective range of file sizes; and, one or more storage destinations, categorizing each of the files by assigning a respective category to each file, initiating a respective backup datastream corresponding to each category that has been assigned, and requesting that each backup datastream be backed up at the respective storage destination that corresponds to the assigned category associated with that backup datastream.

Abstract: A summary change log indexed by inode number is disclosed. An indication is received that a file system object associated with a corresponding file system index node (inode) has been modified. A summary change record is stored for the corresponding inode, including by: locating or creating an entry for the inode in an inode translation file; storing data associated with the modification in a summary change record located within a summary change file at an offset indicated in the entry; and using the summary change record to perform a backup.

Abstract: Techniques to restore data from backup are disclosed. In various embodiments, an indication of a subcomponent to be restored from backup is received. View information associated with the backup is used to determine a set of physical components required to be retrieved from the backup to restore the requested subcomponent. The determined set of physical components is retrieved from the backup. The retrieved physical components are used to restore the subcomponent. In various embodiments, the view information includes data that identifies each of a plurality of separately-recoverable subcomponents of the backup and for each one or more physical components comprising the backup which would be required to restore that subcomponent.

Abstract: Techniques to restore data from backup are disclosed. In various embodiments, an indication of a subcomponent to be restored from backup is received. View information associated with the backup is used to determine a set of physical components required to be retrieved from the backup to restore the requested subcomponent. The determined set of physical components is retrieved from the backup. The retrieved physical components are used to restore the subcomponent. In various embodiments, the view information includes data that identifies each of a plurality of separately-recoverable subcomponents of the backup and for each one or more physical components comprising the backup which would be required to restore that subcomponent.

Abstract: Techniques to restore data from backup are disclosed. In various embodiments, an indication of a subcomponent to be restored from backup is received. View information associated with the backup is used to determine a set of physical components required to be retrieved from the backup to restore the requested subcomponent. The determined set of physical components is retrieved from the backup. The retrieved physical components are used to restore the subcomponent. In various embodiments, the view information includes data that identifies each of a plurality of separately-recoverable subcomponents of the backup and for each one or more physical components comprising the backup which would be required to restore that subcomponent.

Abstract: Backup failures are categorized by storing a keywords file including a set of entries, where each entry includes at least one of a keyword or string pattern corresponding to a problem that may occur during a backup provided by a backup provider for a customer, and an indication of the problem as being one of chargeable or non-chargeable to the backup provider. A log file including messages logged during the backup is read. The messages in the log file are compared against the set of entries in the keywords file to identify any problems that may have occurred during the backup. Upon a particular problem being identified, a determination is made from the keywords file whether the particular problem is chargeable or non-chargeable to the backup provider. A results file is created listing the particular problem, and whether the particular problem is chargeable or non-chargeable to the backup provider.

Abstract: Techniques to restore data from backup are disclosed. In various embodiments, an indication of a subcomponent to be restored from backup is received. View information associated with the backup is used to determine a set of physical components required to be retrieved from the backup to restore the requested subcomponent. The determined set of physical components is retrieved from the backup. The retrieved physical components are used to restore the subcomponent. In various embodiments, the view information includes data that identifies each of a plurality of separately-recoverable subcomponents of the backup and for each one or more physical components comprising the backup which would be required to restore that subcomponent.

Abstract: Techniques to restore data from backup are disclosed. In various embodiments, an indication of a subcomponent to be restored from backup is received. View information associated with the backup is used to determine a set of physical components required to be retrieved from the backup to restore the requested subcomponent. The determined set of physical components is retrieved from the backup. The retrieved physical components are used to restore the subcomponent. In various embodiments, the view information includes data that identifies each of a plurality of separately-recoverable subcomponents of the backup and for each one or more physical components comprising the backup which would be required to restore that subcomponent.