Abstract: A request is received from a client for accessing a first backup instance of first backup data associated with the client, wherein the request includes a first filename and a first savetime. A first directory record database is identified from a plurality of directory record databases based on a client identifier (ID) identifying the client. A first node identifier associated with a first directory comprising the first filename from the first directory record is identified. A first node record database is identified based on the first savetime from the node record databases, the first node record database including node records, each corresponding to a file or a directory of files associated with the first backup instance. A first node record is obtained from the first node record database based on the first node identifier. Node record information associated with the first node record is returned to the client.

Abstract: One example method includes sending, from a manager client to a manager server, a recover request that identifies data targeted for recovery and restoration, and receiving, at the manager client, from a server agent at the manager server: a notification that a recover session corresponding to the recover request has been created; and a recover session ID. The method also includes performing, by a backup client, a deviceless recover and restore process after the recover session has been created, and transmitting, after completion of the deviceless recover and restore process, a communication from the manager client to the server agent indicating that the deviceless recover and restore process is complete.

Abstract: A system for building a restore list for a restore includes a processor and a memory. The processor is configured to determine whether a next sibling record of a directory index record of a root directory includes a subdirectory or a file, wherein the content of the directory index is determined from an incremental backup of the root directory. In the event that the next sibling record comprises a subdirectory of the root directory, the processor is configured to push a directory path associated with the next sibling record onto a directory stack. In the event that the next sibling record comprises a file, the processor is configured to add the latest index record associated with the file to a restore list in the event that the file is not already in the restore list. The restore list is provided for a restore of the state of data of the root directory at a desired time.

Abstract: In one example, a method for backing up data is performed in part by a manager server that receives a request for a deviceless backup session. The manager server authenticates the request and authorizes media database and index database operations. Next, the requested deviceless backup session is created and a backup session ID is transmitted that corresponds to the created deviceless backup session. The manager server then spawns an agent to handle communications with other devices. An update is then received concerning a backup performed with respect to a target device, and a confirmation sent that that the backup has been completed. Catalogue information concerning the completed backup is then received and stored, and the deviceless backup session and agent terminated.

Abstract: A method and system for implementing enhanced indexing in a backup system as well as manage file recovery. The method implemented at a backup server receives a filename from a client to be retrieved from a backup system and queries the filename on a directory records database. As a query return, a directory record is received including a savetime identifying a backup instance and an inode of a directory for the filename of the requested file. The process then queries the inode on a node records database and receives at least one node record where the node record has the inode of the directory record as a parent.

Abstract: A method and system for implementing enhanced indexing in a backup system as well as manage file recovery. The method implemented at a backup server receives backup meta data from a client over a network. The backup meta data is checked to determine whether the backup meta data is directory data or node data and the directory data and node data from the received backup meta data is committed to a set of databases as received during the backup process.

Abstract: Children backup applications communicating to parent backup applications via application program interfaces are described. A child backup task is executed by a child backup application. Backup information associated with an execution of the child backup task by the child backup application is communicated from the child backup application via an application program interface to a parent backup application. A parent backup task is executed by the parent backup application based on the backup information. The child backup application inherently lacks a functionality to execute the parent backup task as the parent backup application executes the parent backup task.

Abstract: Various methods and techniques are disclosed to manage resources of virtual backup appliances in a backup and recovery network. In one embodiment, a backup server receives a request to decommission a virtual backup appliance (VBA) of a first primary storage system. The backup server is configured to manage backup operations to back up data from a plurality of primary storage systems to a backup storage system over a network, where each primary storage system has one or more VBA that carry out backup operations. In response to the request, the backup server transmits a first request to the first primary storage system over the network to delete data and metadata related to the data associated with the VBA. The back up server then determines whether the backup storage system contains data associated with the requested VBA. Upon the determination, the backup server transmits a second request to the backup storage system to delete the data associated with the requested VBA from the backup storage system.

Abstract: A system for building a restore list comprises a processor and a memory. The processor is configured to determine whether a next sibling record comprises a directory. The directory is popped from a directory stack. In the event that the next sibling record comprises a subdirectory of the directory, the processor is configured to push a directory path associated with the next sibling record onto the directory stack. In the event that the next sibling record does not comprise a subdirectory, the processor is configured to add the latest index record associated with the latest index record to a restore list. The memory coupled to the processor and configured to provide the processor with instructions.

Abstract: Virtual machine backup is described. A backup copy is created of a data set associated with a virtual machine based on a backup schedule. A clone copy is created of the backup copy based on a clone schedule. The clone copy is stored on an external destination node including a disk and/or a tape. A disaster recovery copy may be created of the backup copy and metadata associated with the backup copy based on a checkpoint at an interval. A request to restore the data set may be received. The data set may be restored based on the backup copy, the clone copy, or the disaster recovery copy.

Abstract: The present invention is directed to a system and method for providing single instance storage of previously backed up data objects in archived backup storage, also known as data deduplication. Current deduplication methods implemented during backup and archiving of data do not work with previously backed up data. Previously backed up images may vary in format depending upon the method of backup and the type of backup system used. As a result, while future backup efforts may prevent multiple instances of backup data, previously backed up data may exist in multiple instances, wasting valuable storage space. The present invention decodes previously stored backup images for deduplication using an image adapter module that works cohesively with a deduplication engine, regardless of the format of the previously backed up images.

Abstract: A system for building a restore list includes a processor and a memory. The processor is configured to determine whether a next sibling record includes a directory. The directory is popped from a directory stack. In the event that the next sibling record includes a subdirectory of the directory, the processor is configured to push a directory path associated with the next sibling record onto the directory stack. In the event that the next sibling record does not include a subdirectory, the processor is configured to add the latest index record associated with the latest index record to a restore list. The memory coupled to the processor and configured to provide the processor with instructions.

Abstract: A system for an efficient data rehydration comprises a server, one or more reader device managers, a writer device manager, and a verifier. The server is for receiving a restore list comprising a plurality of storage locations and lengths for performing a data rehydration. The one or more reader device managers is for reading a data set indicated by the restore list by reading the plurality of storage locations for the lengths from one or more storage nodes. The plurality of storage locations and lengths indicate chunks from a client system stored as part of a full or as an incremental backup session on a storage device attached to a storage node. The writer device manager is for transferring the data set to a save node. A verifier is for verifying transfer of the data set.

Abstract: A method, article of manufacture, and apparatus for efficiently backing up information is disclosed. In an embodiment, this comprises receiving data and analyzing the received data. In an embodiment, the data may be deduped. File headers, corresponding file metadata and corresponding file blocks are then created based on analyzing the data. In an embodiment, the data is discarded. The file headers, corresponding file metadata and corresponding file blocks are then organized into a self contained datastream. The self contained datastream is then stored in a storage device. File headers are used to indicate the start of a new file in the self contained datastream. File blocks contain the information necessary to reconstruct the files in the datastream. File metadata describes how to reconstruct the file, such as which file blocks are required for the file, and the location of each file block in the self contained datastream, among others.

Abstract: According to some embodiments, a technique for storing data comprises receiving data from a data sender; wherein the data sender uses a first protocol; and sending the received data to a storage medium; wherein the received data is sent by a proxy, and wherein the proxy uses a second protocol.

Abstract: A method, article of manufacture, and apparatus for efficiently restoring information is disclosed. In an embodiment, this comprises receiving a self-contained datastream and analyzing the self-contained datastream for file headers, corresponding file metadata and corresponding file blocks. Data is then reconstructed based on analyzing the self-contained datastream into reconstructed data, and the reconstructed data is then stored in a storage device. File headers are used to indicate the start of a new file in the self contained datastream. File blocks contain the information necessary to reconstruct the files in the datastream. File metadata describes how to reconstruct the file, such as which file blocks are required for the file, and the location of each file block in the self contained datastream, among others. In an embodiment, the reconstructed data may contain deduped data.