Microsoft Technology Licensing, LLC

Microsoft Corporation

Abid Ali

Karandeep Singh Anand

Vijay Sen

Manoj K Valiyaparambil

Amit Singla

Vinay Badami

Pankaj Khanzode

Sunil Pai

Sushil Baid

Robert M Fries

Brian Thomas Berkowitz

Catharine Van Ingen

Suresh P Duddi

Vanita Prabhu

Charumathy Srinivasan

Ravisankar V Pudipeddi

Dilip Madhusudan Ranade

Vivek Sahasranaman

Asim Mitra

Madhan Sambandam

Sachin Durge

Arasu Shankher

Sriram Balasubramaniam

Embodiments are directed to efficiently backing up portions of data and to performing a scoped data recovery. In an embodiment, a computer system preloads data images with data corresponding to various different software applications or operating systems. The computer system chunks the data images, so that each data image is divided into multiple data chunks, and where each data chunk is represented by a hash value. The computer system then receives, from a user, portions of delta data representing data differences between the received user data and the data in the preloaded data images. The computer system also generates a logical backup representation that includes the data chunk hash values for the preloaded data images as well as the delta data received from the user. This logical representation allows restoration of the user's data using only the hash values and the delta data.

Efficient application-aware disaster recovery

Aspects of the subject matter described herein relate to a storage architecture. In aspects, an address provided by a data source is translated into a logical storage address of virtual storage. This logical storage address is translated into an identifier that may be used to store data on or retrieve data from a storage system. The address space of the virtual storage is divided into chunks that may be streamed to the storage system.

Storage architecture for backup application

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.

Backup using metadata virtual hard drive and differential virtual hard drive

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.

Method, system, and apparatus for creating an archive routine for protecting data in a data protection system

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 yield a minimum peak percentage utilization of the media resource. Alternatively, the backup application schedules the new backup job and previously scheduled backup jobs as function of the calculated current load and the predicted load value such that the resulting load on the media resource will yield a minimum peak percentage utilization of the media resource.

Scheduling of new job within a start time range based on calculated current load and predicted load value of the new job on media resources

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.

Controlled anticipation in creating a shadow copy

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.

Method and system for improving management of media used in archive applications

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.

Creating frequent application-consistent backups efficiently

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.

Driving data backups with data source tagging

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.

Managing backup solutions with light-weight storage nodes

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.

Method and system for monitoring and managing archive operations

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.

Growing community of inventors

Hyderabad Telangana, India

Abid Ali