Detecting out-of-band (OOB) changes when replicating a source file system using an in-line system

US9311331B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9311331-B2
Application numberUS-201314011718-A
CountryUS
Kind codeB2
Filing dateAug 27, 2013
Priority dateAug 27, 2013
Publication dateApr 12, 2016
Grant dateApr 12, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Examples described herein include a computer system, positioned in-line with respect to a plurality of clients that actively use a source file system, to replicate a source file system on a target memory in presence of out-of-band events which alter the source file system.

First claim

Opening claim text (preview).

What is claimed is: 1. A method for replicating changes, the method being implemented by one or more processors that are external to a source file system, the method comprising: replicating at least a portion of the source file system on a target memory while a plurality of clients utilize the source file system; generating an object identifier for each file system object that is replicated in the target memory, the object identifiers being based at least in part on metadata provided with each file system object in the source file system; storing the object identifier, for each file system object that is replicated, in association with a corresponding file handle; and handling requests from individual clients in the plurality of clients for file system objects of the source file system; wherein handling requests includes: receiving a given request that specifies a file handle; retrieving, from the source file system, a set of metadata associated with the specified file handle; determining, from the set of metadata, that the file handle identifies a first file system object on the source file system and a second file system object on the target memory by (i) generating an object identifier from the retrieved set of metadata, and (ii) determining that the generated object identifier does not match one of the stored object identifiers; and updating the target memory so that the specified file handle identifies the first file system object. 2. The method of claim 1 , wherein determining includes comparing a time stamp in the set of metadata with a corresponding time stamp associated with the file handle in the target memory. 3. The method of claim 1 , wherein the target memory corresponds to a cache. 4. The method of claim 1 , wherein the target memory corresponds to a destination file system, and wherein replicating at least the portion of the source file system includes replicating the source file system on the destination file system while the source file system is in use by the plurality of clients. 5. A system positioned in-line between a plurality of clients and a source file system, the system comprising: a memory resource to store instructions; one or more processors using the instructions stored in the memory resource to: replicate at least a portion of the source file system on a target memory while the plurality of clients utilize the source file system; generate an object identifier for each file system object that is replicated in the target memory, the object identifiers being based at least in part on metadata provided with each file system object in the source file system; store the object identifier, for each file system object that is replicated, in association with a corresponding file handle; and handle requests from individual clients in the plurality of clients for file system objects of the source file system; wherein handling requests includes: receiving a given request that specifies a file handle; retrieving, from the source file system, a set of metadata associated with the specified file handle; determining, from the set of metadata, that the file handle identifies a first file system object on the source file system and a second file system object on the target memory by (i) generating an object identifier from the retrieved set of metadata, and (ii) determining that the generated object identifier does not match one of the stored object identifiers; and updating the target memory so that the specified file handle identifies the first file system object. 6. The system of claim 5 , wherein determining includes comparing a time stamp in the set of metadata with a corresponding time stamp associated with the file handle in the target memory. 7. The system of claim 5 , wherein the target memory corresponds to a cache. 8. The system of claim 5 , wherein the target memory corresponds to a destination file system, and wherein replicating at least the portion of the source file system includes replicating the source file system on the destination file system while the source file system is in use by the plurality of clients. 9. A non-transitory computer-readable medium that stores instructions, executable by one or more processors, to cause the one or more processors to perform operations that comprise: replicating at least a portion of a source file system on a target memory while a plurality of clients utilize the source file system; generating an object identifier for each file system object that is replicated in the target memory, the object identifiers being based at least in part on metadata provided with each file system object in the source file system; storing the object identifier, for each file system object that is replicated, in association with a corresponding file handle; and handling requests from individual clients in the plurality of clients for file system objects of the source file system; wherein handling requests includes: receiving a given request that specifies a file handle; retrieving, from the source file system, a set of metadata associated with the specified file handle; determining, from the set of metadata, that the file handle identifies a first file system object on the source file system and a second file system object on the target memory by (i) generating an object identifier from the retrieved set of metadata, and (ii) determining that the generated object identifier does not match one of the stored object identifiers; and updating the target memory so that the specified file handle identifies the first file system object. 10. The non-transitory computer-readable medium of claim 9 , wherein determining includes comparing a time stamp in the set of metadata with a corresponding time stamp associated with the file handle in the target memory. 11. The non-transitory computer-readable medium of claim 9 , wherein the target memory corresponds to a cache. 12. The non-transitory computer-readable medium of claim 9 , wherein the target memory corresponds to a destination file system, and wherein replicating at least the portion of the source file system includes replicating the source file system on the destination file system while the source file system is in use by the plurality of clients.

Assignees

Inventors

Classifications

  • Physics · mapped topic

  • Physics · mapped topic

  • G06F16/119Primary

    Details of migration of file systems (migration mechanisms in storage systems G06F3/0647) · CPC title

  • File system administration, e.g. details of archiving or snapshots (error detection or correction of the data by redundancy in operations G06F11/14) · CPC title

  • G06F16/178Primary

    Techniques for file synchronisation in file systems · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9311331B2 cover?
Examples described herein include a computer system, positioned in-line with respect to a plurality of clients that actively use a source file system, to replicate a source file system on a target memory in presence of out-of-band events which alter the source file system.
Who is the assignee on this patent?
Netapp Inc
What technology area does this patent fall under?
Primary CPC classification G06F17/30212. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Apr 12 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).