File repair of file stored across multiple data stores

Patent metadata

Field	Value
Publication number	US-2016299937-A1
Application number	US-201514838590-A
Country	US
Kind code	A1
Filing date	Aug 28, 2015
Priority date	Apr 8, 2015
Publication date	Oct 13, 2016
Grant date	—

Abstract

Non-limiting examples of the present disclosure describe file repair of a file stored across multiple data stores. An inconsistency associated with a file stored across two or more data stores on a client device is identified. A repair action is determined from a plurality of different repair actions based on attributes associated with the inconsistency identified. A repair queue entry is created in a persisted repair queue, the repair queue entry used for execution of the repair action. The repair action is executed as scheduled within the persisted repair queue when pre-requisite checks are satisfied and a persisted repair history for execution of repair actions indicates that no conflicting repair action exists. The persisted repair history and the persisted repair queue are updated based on the execution of the repair action. Other examples are also described.

First claim

1 . A computer-implemented method comprising:
identifying an inconsistency associated with a file stored across two or more data stores on a client device; creating an archived version of the file on the client device when an inconsistency is identified; executing a repair action associated with the file, wherein the executing of the repair action comprises selecting further action based on comparing a content stream of the archived version of the file with a content stream of a version of the file maintained by a server device; and determining whether the file is successfully repaired based on the executing of the repair action.

2 . The computer-implemented method according to claim 1 , further comprising determining the repair action from a plurality of different repair actions based on attributes associated with a synchronization inconsistency identified.

3 . The computer-implemented method according to claim 1 , wherein the determining of whether the file is successfully repaired further comprises updating a repair history based on a result of executing the repair action and rescanning the data stores on the client device after the repair action is executed.

4 . The computer-implemented method according to claim 1 , further comprising creating a queue entry for evaluating the inconsistency identified and maintaining a persisted repair history for execution of repair actions on one or more files, wherein the queue entry is updatable at any point after the queue entry is created.

5 . The computer-implemented method according to claim 4 , wherein when the file is determined to be unsuccessfully repaired for a predetermined number of attempts, the computer-implemented method further comprising updating the persisted repair history to indicate that the repair action is flawed and that another repair action is to be applied.

6 . The computer-implemented method according to claim 4 , further comprising preventing, based on an automated review of the persisted repair history, execution of the repair action on one or more files when another repair application is being applied to the one or more files.

7 . The computer-implemented method according to claim 4 , further comprising delaying execution of the repair action until pre-requisite checks are satisfied, wherein the delaying further comprises re-prioritizing the queue entry until the pre-requisite checks are satisfied, and notifying the client device that the pre-requisite checks are unsatisfied.

8 . The computer-implemented method according to claim 1 , further comprising requesting download, to the client device, of the version of the file maintained by the server and executing the repair action when it is determined that the version of the file maintained by the server is downloaded to the client device.

9 . The computer-implemented method according to claim 8 , further comprising re-prioritizing a queue entry for executing of the repair action when the repair action is scheduled to execute and a requested download of the version of the file maintained by the server is incomplete.

10 . A system comprising:
a memory; and at least one processor operatively connected with the memory, programmed to execute operations comprising:
identifying an inconsistency associated with a file stored across two or more data stores on a client device,
creating an archived version of the file on the client device when an inconsistency is identified,
executing a repair action associated with the file, wherein the executing of the repair action comprises selecting further action based on comparing a content stream of the archived version of the file with a content stream of a version of the file maintained by a server device, and
determining whether the file is successfully repaired based on the executing of the repair action.

11 . The system according to claim 10 , wherein the operations executed by the processor further comprising determining the repair action from a plurality of different repair actions based on attributes associated with the inconsistency identified.

12 . The system according to claim 10 , wherein the determining of whether the file is successfully repaired further comprises updating a repair history based on a result of executing the repair action and rescanning the data stores on the client device after the repair action is executed.

13 . The system according to claim 10 , wherein the operations executed by the processor further comprising creating a queue entry for evaluating the inconsistency identified and maintaining a persisted repair history for execution of repair actions on one or more files, wherein the queue entry is updatable at any point after the queue entry is created.

14 . The system according to claim 13 , wherein when the file is determined to be unsuccessfully repaired for a predetermined number of attempts, the operations executed by the processor further comprising updating the persisted repair history to indicate that the repair action is flawed and that another repair action is to be applied.

15 . The system according to claim 13 , wherein the operations executed by the processor further comprising preventing, based on an automated review of the persisted repair history, execution of the repair action on one or more files when another repair application is being applied to the one or more files.

16 . The system according to claim 13 , wherein the operations executed by the processor further comprising delaying execution of the repair action until pre-requisite checks are satisfied, wherein the delaying further comprises re-prioritizing the queue entry until the pre-requisite checks are satisfied, and the operations executed by the processor further comprising notifying the client device that the pre-requisite checks are unsatisfied.

17 . The system according to claim 10 , wherein the operations executed by the processor further comprising requesting download, to the client device, of the version of the file maintained by the server and executing the repair action when it is determined that the version of the file maintained by the server is downloaded to the client device.

18 . The system according to claim 17 , wherein the operations executed by the processor further comprising re-prioritizing a queue entry for executing of the repair action when the repair action is scheduled to execute and a requested download of the version of the file maintained by the server is incomplete.

19 . A computer-readable storage device including executable instructions, that when executed on at least one processor, causing the processor to perform operations comprising:
identifying an inconsistency associated with a file stored across two or more data stores on a client device; determining a repair action from a plurality of different repair actions based on attributes associated with the inconsistency identified; creating a repair queue entry in a persisted repair queue, the repair queue entry for execution of the repair action; executing the repair action as scheduled within the persisted repair queue when pre-requisite checks are satisfied and a persisted repair history for execution of repair actions indicates that no conflicting repair action exists; and updating the persisted repair history and the persisted repair queue based on the executing of the repair action.

20 . The computer-readable storage device according to claim 19 , wherein the operations executed by the processor further comprising re-evaluating the repair queu

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Crockett Sterling J
• Stix Jeffrey
• Parameswaren Anup S
• Zircher Dana M
• Buzzell Steve

Classifications

• G06F16/1873 Primary

  Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files · CPC title

• G06F17/30082

  Physics · mapped topic

• G06F17/30371 Primary

  Physics · mapped topic