# US 2012/0254118 A1 · Recovery of tenant data across tenant moves

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254118 A1
- Document ID: US20120254118A1
- Status: Published application
- Kind: A1
- Application number: 13/077,620
- Filed: 2011-03-31
- Published: 2012-10-04
- Earliest claimed: 2011-03-31
- Assignees: Microsoft Corporation
- Inventors: Siddharth Rajendra Shah; Antonio Marco Da Silva, JR.; Nikita Voronkov; Viktoriya Taranov; Daniel Blood
- Web page: https://patentgrep.com/patent/US20120254118A1

## CPC

- G06F 11/1469: {Backup restoration techniques}
- G06F 11/1448: {Management of the data involved in backup or backup restore}
- G06F 11/1464: {for networked environments}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A history of locations of tenant data is maintained. The tenant data comprises data that is currently being used by the tenant and the corresponding backup data. When a tenant's data is changed from one location to another, a location and a time is stored within the history that may be accessed to determine a location of the tenant's data at a specified time. Different operations trigger a storing of a location/time within the history. Generally, an operation that changes a location of the tenant's data triggers the storing of the location within the history (e.g. upgrade of farm, move of tenant, adding a tenant, load balancing of the data, and the like). When tenant data is needed for an operation (e.g. restore), the history may be accessed to determine the location of the data.

## Claims

### Claim 1

A method for recovering tenant data across tenant moves, comprising:
determining an operation that changes a location of a tenant's data;
in response to the operation that changes the location of the tenant's data, updating a history of the tenant's data by adding a current location of the tenant's data; and
when requested, accessing the history to determine a previous location of the tenant's data.

### Claim 2 (depends on 1)

The method of claim 1, wherein the history is updated in response to a load balancing of at least one of: tenant data and backup data.

### Claim 3 (depends on 1)

The method of claim 1, wherein the history is updated in response to a tenant move.

### Claim 4 (depends on 1)

The method of claim 1, wherein the history is updated in response to a farm upgrade.

### Claim 5 (depends on 1)

The method of claim 1, wherein updating the history comprises storing a location of backup data that corresponds to the tenant's data.

### Claim 6 (depends on 5)

The method of claim 5, wherein the backup data comprises a full backup of the tenant's data and incremental backups of the tenant's data and transaction log backups of the tenant's data.

### Claim 7 (depends on 1)

The method of claim 1, wherein updating the history comprises including a time indicating when the tenant's data is moved from the previous location the current location.

### Claim 8 (depends on 7)

The method of claim 7, further comprising determining the previous location of the tenant's data by accessing the location based upon a comparison of a specified time with the time within the history.

### Claim 9 (depends on 1)

The method of claim 1, further comprising restoring the data to a temporary location and extracting requested data from the temporary location and placing the extracted data into the current location of the tenant's data.

### Claim 10

A computer-readable storage medium storing computer-executable instructions for recovering tenant data across tenant moves, comprising:
determining an operation that changes a location of a tenant's data;
updating a history of the tenant's data to include a current location of the tenant's data, wherein the history includes a record for each location at which the tenant's data has been stored and the current location, wherein each record comprises a tenant data location, a backup location for the tenant data, and time information indicating when the data was at each of the locations; and
when requested, accessing the history to determine a previous location of the tenant's data.

### Claim 11 (depends on 10)

The computer-readable storage medium of claim 10, wherein the history is updated in response to at least one of: a load balancing on at least one of:
tenant data and backup data; a tenant move; and a farm upgrade.

### Claim 12 (depends on 10)

The computer-readable storage medium of claim 10, further comprising providing each location of the backup of tenant's data in response to the request.

### Claim 13 (depends on 12)

The computer-readable storage medium of claim 12, wherein the backup data comprises a full backup of the tenant's data, incremental backups of the tenant's data, and transaction log data.

### Claim 14 (depends on 10)

The computer-readable storage medium of claim 10, wherein updating the history comprises including a time indicating when the tenant's data is moved from the previous location to the current location.

### Claim 15 (depends on 14)

The computer-readable storage medium of claim 14, further comprising determining the previous location of the tenant's data by accessing the location based upon a comparison of a specified time with the time within the history.

### Claim 16 (depends on 10)

The computer-readable storage medium of claim 10, further comprising restoring the data to a temporary location and extracting requested data from the temporary location and placing the extracted data into the current location of the tenant's data.

### Claim 17

A system for recovering tenant data across tenant moves, comprising:
a network connection that is configured to connect to a network;
a processor, memory, and a computer-readable storage medium;
an operating environment stored on the computer-readable storage medium and executing on the processor;
a data store storing tenant data that is associated with different tenants; and
a backup manager operating that is configured to perform actions comprising:
receiving a request for a tenant's data;
accessing a history of tenant data locations to determine a location of the requested tenant data, wherein the history includes a record for each location at which the tenant's data has been stored and the current location, wherein the record comprises a tenant data location, a backup location for the tenant data, and time information indicating when the data was at each of the locations.

### Claim 18 (depends on 17)

The system of claim 17, further comprising comparing a time specified within the request to determine the location of the requested tenant data.

### Claim 19 (depends on 17)

The system of claim 17, further comprising examining each location within the history to determine the location of the requested tenant data.

### Claim 20 (depends on 17)

The system of claim 17, further comprising restoring the tenant's data to a temporary location and extracting the requested data from the temporary location and placing the extracted data into the current location of the tenant's data.
