Microsoft Technology Licensing, LLC

Manoj K Valiyaparambil

Abid Ali

Karandeep Singh Anand

Vijay Sen

Amit Singla

Muralidhar Krishnaprasad

Robert M Fries

Ravisankar V Pudipeddi

Ran Kalach

Lu Xun

Abhishek Agarwal

Dilip Madhusudan Ranade

Sriram Sampath

Anil Kumar Nori

Vivek Sahasranaman

Vinay Badami

Pankaj Khanzode

Anurag Gupta

Abhinav Srivastava

Vanita Prabhu

Charumathy Srinivasan

Sriram Balasubramaniam

Giridharan Kasirala Ramachandraiah

Arasu Shankher

Christian Paul Stackhouse

Narendra Babu T V

Sujoy Gupta

Padma Priya A B

Paramesh Vaidyanathan

A system includes determination of a resource stored in a cloud storage service, identification of a first cloud service associated with the resource, determination of a first pre-backup callback and a first post-backup callback associated with the first cloud service, transmission of the first pre-backup callback to the first cloud service, reception of a return of the first pre-backup callback from the first cloud service, transmission, in response to receipt of the return, of an instruction to the cloud storage service to backup the resource, and transmission of the first post-backup callback to the first cloud service.

Cloud services integrated backup and restore

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

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

Systems and methods that supply a replication layer/agent that is generic to supporting a plurality of storage configuration as part of a distributed store. Such distributed store employs a Common Availability Substrate (CAS) for data transport and consistency, to render the distributed store scalable and available. Such an arrangement enables continuous operation of the store, while the replication subsystem creates new replicas (e.g., for load balancing, failover, and the like).

Replication for common availability substrate

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

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 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.

Retaining shadow copy data during replication

An automatic resource management service implements a policy to automatically control resource usage by processes running on a computer. A policy expresses criteria for identifying process sets, and imposes allocations and sub-allocations or resource amounts to be used by given process sets and subsets. Exclusion lists are used in an embodiment of the invention to exclude processes from management by the management service. In an embodiment of the invention the resources whose use is managed are CPU resources, although in further embodiments the managed resources include memory resources as well.

System and method for CPU bandwidth allocation

Growing community of inventors

Hyderabad Telangana, India

Manoj K Valiyaparambil