Abstract: Methods and systems are disclosed for backup using a metadata virtual hard drive (VHD) and a differential VHD. A particular system includes a memory device that stores files and a backup agent configured to detect changes to the files. The system includes a translation module configured to translate the detected changes into VHD formatted changes and a VHD module configured to write the VHD formatted changes to a metadata VHD stored at the memory device. The VHD module is also configured to generate a differential VHD based on the metadata VHD. A network interface at the system is configured to transmit the metadata VHD and the differential VHD to a remote storage device.

Abstract: In accordance with one embodiment of the present invention, a method for efficiently inventorying a plurality of items of media contained in a library is provided. The method includes reading a barcode located on an item of media that contains contents and determining whether the barcode is known. Optionally, the method may also determine if the know item of media was previously offline. If it is determined that the barcode is known, the media is identified as known. However, if it is determined that the barcode is not known, a detailed inventory of the contents of the item of media is performed. In one embodiment, if it is determined that the barcode is not known, a user is notified that a new item of media has been identified.

Abstract: A method for creating an archive protection plan for archiving a backup of data is provided. An indication of an archive data protection kind and an archive data protection duration are received. In response to receiving the archive data protection kind and the archive data protection duration, an archive scheme is determined and an archive protection plan representative of the archive scheme is generated.

Abstract: A method for creating an archive protection plan for archiving a backup of data is provided. An indication of an archive data protection kind and an archive data protection duration are received. In response to receiving the archive data protection kind and the archive data protection duration, an archive scheme is determined and an archive protection plan representative of the archive scheme is generated.

Abstract: One embodiment of the present invention provides a system that handles instruction fetch requests that return out-of-order at an IFU of a processor. During operation, the system sends a request to obtain a cache line to an instruction cache, wherein the request can be serviced and the cache line can be sent to a fetch buffer before a preceding cache line for a preceding request has returned from the instruction cache. In response to the request, the system receives the cache line from the instruction cache. Next, the system determines whether the cache line was returned out-of-order with respect to the preceding cache line. If so, the system performs an action to handle the out-of-order return.

Abstract: Data can be protected at a production server in a virtually continuous fashion, without necessarily imposing severe constraints on the source application(s). For example, a production server can create an application-consistent backup of one or more volumes, the backups corresponding to a first instance in time. A volume filter driver can monitor data changes in each volume using an in-memory bitmap, while a log file and/or update sequence number journal can keep track of which files have been added to or updated. The volume updates are also consistent for an instance (later) in time. At the next replication cycle, such as every few minutes (however configured), the volume filter driver passes each in-memory bitmap to the physical disk on the production server. The production server then sends the updates to the backup server, which thus stores application-consistent backups for the volume for multiple instances of time.

Abstract: Implementations of the present invention allow clients (e.g., end-users, administrators, etc.) to associate data with one or more protection intents at the data/data source level. A backup server can then associate the data with a specific protection mechanism regardless of where the data/data source(s) are located, or regardless of how other like-data are being backed up. The backup server can then backup data that are associated with similar protection intents in a similar manner based on client specifications. The backup server can also monitor the various protection intents and associations to ensure that the protection intents are being met. For example, if the backup server identifies that data are not being backed up in accordance with their associated protection intent, the backup server can send one or more communications indicating the same, such that the protection mechanisms can be adjusted appropriately.

Abstract: A backup system in accordance with an implementation of the present invention includes one or more light-weight (i.e., stateless) storage nodes that are positioned close enough to one or more assigned production servers to enable as rapid and efficient a data recovery as possible. The one or more light-weight storage nodes are driven by, and implement backup policies in accordance with, control settings determined by and received from a centralized backup server. Changes to the control settings are simply produced at the centralized backup server and propagated to each storage node in the system. In addition to efficient backup times, general backup administration can be greatly simplified at least in part since a large number of production serves can be serviced through a small or large number of light-weight storage nodes, which in turn can be managed by a single centralized backup server.

Abstract: In accordance with an aspect of the present invention, in a data protection system having a production location, a storage location, and a communication path for transmitting data between the production location and the storage location, a method for creating a makeup archive job is provided. The method includes determining if a task of an archive job was successful and, if it is determined that the task was not successful, including the task in an archive makeup job. Additionally, the method determines if there are any tasks of the archive job that are dependent upon the failed task. If there are dependent tasks, those dependent tasks are also included in the archive makeup job.

Abstract: A system that suppresses duplicative prefetches for branch target cache lines. During operation, the system fetches a first cache line into in a fetch buffer. The system then prefetches a second cache line, which immediately follows the first cache line, into the fetch buffer. If a control transfer instruction in the first cache line has a target instruction which is located in the second cache line, the system determines if the control transfer instruction is also located at the end of the first cache line so that a corresponding delay slot for the control transfer instruction is located at the beginning of the second cache line. If so, the system suppresses a subsequent prefetch for a target cache line containing the target instruction because the target instruction is located in the second cache line which has already been prefetched.

Abstract: Implementations of the present invention provide systems, methods, and components configured to preserve valid shadow copies during replication cycles, before those valid shadow copies have expired. In particular, one or more components can identify the size and rate of changes in production server data that will be applied to a new volume shadow copy. The components can then determine the storage area that would be needed to store the new volume shadow copy in the backup volume and apply changes onto the backup volume if there is appropriate space. If there is not an appropriate amount of space, the components can alert the system that new action should be taken to preserve both prior, valid shadow copies as well as new shadow copies. For example, a backup administrator may need to increase the shadow copy storage space, or assign a new storage medium for handling new shadow copies.

Abstract: In one embodiment, a processor comprises a branch prediction array, an index generator coupled to the branch prediction array, and a control unit coupled to the index generator. The branch prediction array is configured to store a plurality of branch predictions for conditional branches. The index generator is configured to generate an index to the branch prediction array responsive to at least a portion of a fetch address corresponding to a fetch request that is at a first pipeline stage of the processor and further responsive to a branch history. The control unit is configured to update the branch history responsive to a first fetch request at the first pipeline stage and to defer the update for a second fetch request to a second pipeline stage subsequent to the first pipeline stage.

Abstract: Method for scheduling a new backup job within a backup application to optimize a utilization of a media resource of said backup application. The backup application includes one or more previously scheduled backup jobs. The backup application calculates a current load of the media resource as a function of the previously scheduled backup jobs and the media resource and predicts a load value for the new backup job as a function of job parameters associated with the new backup job. Then, the backup application schedules the new backup job as a function of the calculated current load and the predicted load value such that the resulting load on the media resource will yeild a minimum peak percentage utilization of the media resource.

Abstract: Controlling data retention of a collection of data in a data store. An instruction is received to store a shadow collection of data to the data store. The data store has a previous version of the shadow collection of data. An available amount of data storage space on the data store is identified. An amount of data storage space needed is estimated for storing the shadow collection of data to the data store based on the received instruction. It is determined whether the identified available amount of data storage space is sufficient for storing the estimated amount of data storage space. The shadow collection of data is stored to the data store when said determine indicates that the identified available amount of data storage space is sufficient and the previous version is permitted to be deleted or to be overwritten.

Abstract: A processor includes a fetch pipeline, out-of-order (OOO) logic and a strand selector. The fetch pipeline is configured to provide instructions from an instruction store to a fetch buffer responsive to receiving a plurality of fetch requests for a first strand, selected from a plurality of active strands. The OOO logic is coupled to the fetch pipeline and is configured to detect an OOO packet in the fetch pipeline in response to the fetch requests for the first strand. The strand selector is coupled to the OOO logic and the fetch pipeline and selects a second strand for processing in the fetch pipeline, from the active strands, when the OOO logic detects the OOO packet associated with the first strand.

Abstract: One embodiment of the present invention provides a system that handles instruction fetch requests that return out-of-order at an IFU of a processor. During operation, the system sends a request to obtain a cache line to an instruction cache, wherein the request can be serviced and the cache line can be sent to a fetch buffer before a preceding cache line for a preceding request has returned from the instruction cache. In response to the request, the system receives the cache line from the instruction cache. Next, the system determines whether the cache line was returned out-of-order with respect to the preceding cache line. If so, the system performs an action to handle the out-of-order return.

Abstract: One embodiment of the present invention provides a system that performs a fast-scanning operation to generate fetch bundles within an instruction fetch unit (IFU) of a processor. During operation, the system obtains a cache line containing instructions at the IFU. Next, the system performs a complete-scanning operation on the cache line to identify control transfer instructions (CTIs) in the cache line. At the same time, the system performs a fast-scanning operation to identify CTIs in a group of initial instructions in the cache line, wherein the initial instructions are executed before other instructions in the cache line. Next, the system obtains results from the fast-scanning operation before results of the complete-scanning operation are available. The system then uses results from the fast-scanning operation to form an initial fetch bundle containing initial instructions, and sends the initial fetch bundle to the instruction-issue unit.

Abstract: Implementations of the present invention allow clients (e.g., end-users, administrators, etc.) to associate data with one or more protection intents at the data/data source level. A backup server can then associate the data with a specific protection mechanism regardless of where the data/data source(s) are located, or regardless of how other like-data are being backed up. The backup server can then backup data that are associated with similar protection intents in a similar manner based on client specifications. The backup server can also monitor the various protection intents and associations to ensure that the protection intents are being met. For example, if the backup server identifies that data are not being backed up in accordance with their associated protection intent, the backup server can send one or more communications indicating the same, such that the protection mechanisms can be adjusted appropriately.

Abstract: Implementations of the present invention provide systems, methods, and components configured to preserve valid shadow copies during replication cycles, before those valid shadow copies have expired. In particular, one or more components can identify the size and rate of changes in production server data that will be applied to a new volume shadow copy. The components can then determine the storage area that would be needed to store the new volume shadow copy in the backup volume and apply changes onto the backup volume if there is appropriate space. If there is not an appropriate amount of space, the components can alert the system that new action should be taken to preserve both prior, valid shadow copies as well as new shadow copies. For example, a backup administrator may need to increase the shadow copy storage space, or assign a new storage medium for handling new shadow copies.

Abstract: Data can be protected at a production server in a virtually continuous fashion, without necessarily imposing severe constraints on the source application(s). For example, a production server can create an application-consistent backup of one or more volumes, the backups corresponding to a first instance in time. A volume filter driver can monitor data changes in each volume using an in-memory bitmap, while a log file and/or update sequence number journal can keep track of which files have been added to or updated. The volume updates are also consistent for an instance (later) in time. At the next replication cycle, such as every few minutes (however configured), the volume filter driver passes each in-memory bitmap to the physical disk on the production server. The production server then sends the updates to the backup server, which thus stores application-consistent backups for the volume for multiple instances of time.