Abstract: Disclosed are systems and methods for using a metadata agent to collect metadata from a client computer system and including receiving the metadata associated with files used by applications executing in the client computer system. The metadata belong to objects stored in a volume associated with the client computer system. The metadata is collected in real time by the metadata agent executing in the client computer system as a background task. The metadata is stored in a metadata base associated with a metadata server. A request to search the metadata is received from a backup server associated with the metadata server. The search request includes search criteria. A search engine associated with the metadata server searches the metadata in the metadata database to find a match based on the search criteria. A search result is transmitted from the metadata server to the backup server which uses the search result to search for objects in the backup data.

Abstract: A computer-implemented method for securely storing backup data while facilitating fast failovers may include 1) identifying, at a primary site, a virtual disk file that includes a backup image, 2) modifying a boot sector within the virtual disk file to add a boot loader that supports reading disks encrypted with whole disk encryption, 3) encrypting the backup image within the virtual disk file, except for at least one decryption area, with whole disk encryption, and 4) storing the virtual disk file at a secondary site after encrypting the backup image within the virtual disk file. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: A method and apparatus for performing file-level restoration from a block-based backup file stored on a sequential storage device is described. In one embodiment, a method of processing a backup file to perform file-level restoration from a sequential storage device comprises generating extent information, wherein the extent information pertains to at least one file system object associated with a backup file, wherein the backup file is to be stored on a sequential storage device, wherein the backup file is block-based and processing a backup catalog, wherein the backup catalog indicates locations of various portions of the extent information and is used to restore a file system object.

Abstract: A computer-implemented method for synthetic backups may include identifying a full backup of a volume of files. The computer-implemented method may also include identifying a set of incremental backups that were performed subsequently to the full backup. The computer-implemented method may further include identifying a set of storage devices that store the full backup and the set of incremental backups. The computer-implemented method may additionally include identifying a request to create a synthetic backup incorporating the full backup and the set of incremental backups. The computer-implemented method may moreover include generating a sorted catalog for the synthetic backup by indexing files for the synthetic backup in an order based on at least one characteristic of the files.

Abstract: Various methods and systems for presenting a logical view of a database backup are disclosed. One method involves querying a database recovery manager for logical identifiers that correspond to physical backup pieces generated during a backup. The method uses the logical identifiers to display a backup view to a user. The backup view identifies logical database components that are available to be restored.

Abstract: Restore software executing in a computer system may invoke a snapshot of a target volume before restoring a plurality of files from a backup image to the target volume. If the restore operation fails before all the files are restored to the target volume then the restore software may use the snapshot to return one or more of the files to their original states as they existed before the restore operation was initiated.

Abstract: One or more computer systems, a carrier medium, and a method are provided for creating a catalog for backup data using NDMP file history messages. The messages are received at a first computer system (NDMP client) from a second computer system (NDMP host). Each message comprises information describing a filesystem node (a file or directory). The messages comprise hierarchy information and attribute information for the nodes. For each message comprising hierarchy information, an entry may be created for the respective node in a catalog, and the hierarchy information for the respective node may be stored in the catalog. For each message comprising attribute information, the attribute information for the respective node may be stored in the catalog. The messages may be processed in a single pass without caching them all. A carrier medium may include program instructions which, when executed, cause the above operations on one or more computer systems.