Granted Patent B2

US 7,734,826 · App. 10/099,522 · Granted Jun 8, 2010

Abstract

Claims (75)

1. A computer-readable non-transitory medium storing a client synchronization application suitable for running on a client, the client synchronization application comprising:

a client sync index (CSI) identifying a state of files stored on the client;

a client synchronization file system (CSFS) storing client metadata corresponding to the files stored on the client;

client sync data (CSD) comprising first server IDs (SIDs), each first SID corresponding to one of the files stored on the client;

means for receiving a server sync index (SSI) from a server, the SSI identifying a state of files stored on the server;

means for comparing the CSI with the SSI;

means for determining if the files stored on the client are in sync with the files stored on the server based on the compared CSI and SSI;

means for receiving server sync data (SSD) from the server if the means for determining determines that the files stored on the client are not in sync with the files stored on the server, the SSD comprising second SIDs, each second SID corresponding to one of the files stored on the server;

means for determining CSD/SSD SIDs comprising a union of the first SIDs and the second SIDs;

means for determining whether each CSD/SSD SID is in at least one of the CSD and the SSD;

responsive to determining that a CSD/SSD SID is in the SSD and not in the CSD, means for downloading from the server a file corresponding to the CSD/SSD SID;

responsive to determining that a CSD/SSD SID is in the CSD and not in the SSD, means for deleting on the client a file corresponding to the CSD/SSD SID and removing the CSD/SSD SID from the CSD; and

a filter driver to monitor activity on the client, wherein the filter driver interrupts the client synchronization application if a second application accesses at least one of the files stored on the client.

2. A computer-readable non-transitory medium according to claim 1 , wherein the filter driver monitors activity corresponding to the files stored on the client.

3. A computer-readable non-transitory medium according to claim 1 , wherein the metadata comprises a client ID (CID), a server ID, and a file sync index (FSI).

4. A computer-readable non-transitory medium according to claim 1 , wherein the client synchronization application further comprises means for partially uploading or downloading the file.

5. A computer-readable non-transitory medium according to claim 4 , wherein:

the client synchronization application further comprises:

a message digest array (MDA) for the file;

means for receiving a second MDA from the server; and

the means for partially uploading or downloading includes means for comparing the MDA and the second MDA.

6. A computer-readable non-transitory medium according to claim 5 , wherein the MDA is stored with a metadata item for the file.

7. A computer-readable non-transitory medium according to claim 5 , wherein the client synchronization application further comprises means for generating the MDA for the file.

8. A computer-readable non-transitory medium according to claim 5 , wherein the client synchronization application further comprises means for storing a change time to the file.

9. A computer-readable non-transitory medium according to claim 1 , wherein the client synchronization application further comprises means for decrypting the SSI received from the server if the SSI is encrypted.

10. A computer-readable non-transitory medium according to claim 1 , wherein the client synchronization application further comprises means for decrypting the SSD received from the server if the SSD is encrypted.

11. A system, comprising:

a server having installed thereon a synchronization file system including:

a directory entry;

a metadata item for the directory entry;

server sync data (SSD) comprising first server IDs (SIDs) corresponding to files on the server; and

a server sync index (SSI), the SSI representing a state of all files on the server; and

a client, remote from the server, having installed thereon a client synchronization application including:

client sync data (CSD) comprising second SIDs corresponding to files on the client;

means for retrieving the SSI from the server;

means for decrypting the SSI;

means for comparing a client sync index (CSI) with the SSI, the CSI representing a state of all files on the client; and

means for determining if the client is in sync with the server based on the compared CSI and SSI;

means for retrieving the server sync data (SSD) from the server;

means for decrypting the SSD; and

means for determining CSD/SSD SIDs comprising a union of the first SIDs and the second SIDs;

means for determining which, if any, of the files on the client are not in sync with the files on the server by determining whether each CSD/SSD SID is in only one of the CSD and the SSD;

responsive to determining that a CSD/SSD SID is in the SSD and not in the CSD, means for downloading from the server a file corresponding to the CSD/SSD SID;

responsive to determining that a CSD/SSD SID is in the CSD and not in the SSD, means for deleting on the client a file corresponding to the CSD/SSD SID and removing the CSD/SSD SID from the CSD; and

a filter driver for interrupting the client synchronization application if a second application accesses at least one of the files on the client; and

a network connecting the client to the server.

12. A method for a client to synchronize a first directory on the client with a second directory on a synchronization file system of a server, comprising:

the client transmitting a client sync index (CSI) to the synchronization file system of the server, the CSI identifying a state of files on the client;

the client receiving a server sync index (SSI) from the synchronization file system of the server, the SSI identifying a state of files on the server;

comparing the CSI to the SSI to determine whether the account on the server and the account on the client are synchronized;

if the server and client are not synchronized:

receiving server sync data (SSD) from the synchronization file system responsive to a determination that the account on the server and the account on the client are not synchronized, the SSD comprising first server IDs (SIDs);

comparing client sync data (CSD) to the SSD to determine what updates to make to the client, wherein the CSD comprises second SIDs, and wherein comparing the CSD to the SSD comprises determining CSD/SSD SIDs comprising a union of the first SIDs and the second SIDs and determining whether each of the CSD/SSD SIDs is in at least one of the CSD and the SSD; and

updating a directory entry on the client and a metadata item for the directory entry on the client;

responsive to determining that a CSD/SSD SID is in the SSD and not in the CSD, means for downloading from the server a file corresponding to the CSD/SSD SID;

responsive to determining that a CSD/SSD SID is in the CSD and not in the SSD, means for deleting on the client a file corresponding to the CSD/SSD SID and removing the CSD/SSD SID from the CSD;

monitoring file activity on the client; and

responsive to detecting an access of a file on the client by an application on the client during a driver read call of the file, temporarily suspending operation of the application while cancelling the driver read call.

13. A method according to claim 12 , wherein comparing a client sync data (CSD) and the SSD includes:

identifying a server ID (SID) in the SSD but not in the CSD; and

determining that a file exists on the server and is missing on the client.

14. A method according to claim 12 , further comprising updating the CSD based on the comparison of the CSD and the SSD.

15. A method according to claim 12 , further comprising updating a metadata item based on the SSD.

16. A method according to claim 12 , wherein updating the file on the client includes:

requesting the file from the synchronization file system by a server ID;

the client receiving the file from the synchronization file system of the server; and

storing the file on the client.

17. A method according to claim 16 , wherein:

requesting the file includes requesting a block of the file from the synchronization file system; and

receiving the file includes the client receiving the block of the file from the synchronization file system of the server.

18. A method according to claim 16 , wherein:

requesting the file includes requesting a first message digest array (MDA) for the file from the synchronization file system, the first MDA including an array of hashes of blocks of the file;

receiving the file includes receiving the first MDA of the file from the synchronization file system;

identifying a second MDA for a file on the client; and

comparing the first MDA and the second MDA.

Assignments (13)