Scalable File Replication and Web-based Access

• US 20070185932A1
• Filed: 02/01/2006
• Published: 08/09/2007
• Est. Priority Date: 02/01/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Teodosiu, Dan, Liu, Huisheng, Annamalai, Muthukaruppan, Bjorner, Nikolaj, Bozeman, Patrick, Steere, David, Bohlander, Michael
• Granted Patent: US 7,743,023 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/184 implemented as replicated file system

Abstract

Various embodiments introduce the notion of a replication entity which implements a highly scalable file replication system. In one embodiment, the replication entity resides in the form of a scalable replication service. In at least some embodiments, the replication service provides a “drive in the sky” facility that can be used by individuals, such as subscribers, to synchronize their individual machines, such that their files are automatically replicated to a safe and always-on location. Alternatively or additionally, individuals such as subscribers can also access their files via a web-based interface when they are away from their machines.

Claims

1. A system comprising:

a replication entity configured to;

replicate files;

store file data in a scalable binary large object (blob) store; and

store file metadata in a scalable metadata store.

2. The system of claim 1, wherein the replication entity is configured to merge replication metadata with file metadata in the scalable metadata store.

3. The system of claim 2, wherein the replication entity is configured to, responsive to updates to the blob store, transact both file metadata and replication metadata together.

4. The system of claim 3, wherein the replication entity is configured to receive at least some updates via a web interface.

5. The system of claim 1, wherein the replication entity comprises a service.

6. The system of claim 1, wherein the replication entity comprises one or more hubs.

7. The system of claim 1, wherein the replication entity is configured as a state-based replication entity.

8. The system of claim 1, wherein the blob store does not require full file system semantics.

9. A system comprising:

one or more replication front ends individual ones of which being associated with a file replication engine that is configured to provide state-based file replication;

at least one scalable file store for storing file data in a manner that does not require full file system semantics; and

at least one scalable metadata store for storing associated file metadata.

10. The system of claim 9, wherein said at least one scalable metadata store stores replication metadata that is associated with said file metadata.

11. The system of claim 10 further comprising one or more access nodes individual ones of which being configured to transact both the replication metadata and associated file metadata together.

12. The system of claim 9, wherein said system is embodied as a service.

13. The system of claim 12, wherein a replication client can participate in bidirectional replication with the replication service using the same replication protocols that would be utilized when replicating with another replication client running on a file system.

14. The system of claim 9 further comprising one or more replication group redirection services to direct replication clients to a particular instance of a replication front end.

15. The system of claim 9 further comprising one or more servers individual ones of which hosting a presentation layer configured to communicate with one or more web clients and to present HTML file system views for the one or more web clients.

16. The system of claim 9 further comprising one or more scalable file service access nodes at least some of which being configured to marshal files into a staged file format and unmarshal staged files.

17. A computer-implemented method comprising:

receiving, with a replication entity, a staged file;

sending, to a storage access node, a write request for the staged file;

sending the staged file to a scalable binary large object (blob) store;

receiving, from the blob store, a locator token for the staged file;

sending, to the storage access node, a metadata write request to write replication metadata, file system metadata for the staged file, and the locator token;

forwarding the metadata write request to a scalable metadata store; and

committing said metadata write request on said scalable metadata store.

18. The method of claim 17 further comprising, prior to said act of receiving a staged file, receiving from a replication client, a communication and responsive to said communication, directing said replication client to a particular instance of a replication front end comprising a replication engine for replicating files.

19. The method of claim 17 further comprising uploading a file from one or more web clients to the replication entity.

20. The method of claim 17 further comprising downloading a file from the replication entity to one or more web clients.