US2013138615A1PendingUtilityA1
Synchronizing updates across cluster filesystems
Est. expiryNov 29, 2031(~5.4 yrs left)· nominal 20-yr term from priority
G06F 11/1471G06F 16/2379G06F 16/2365G06F 16/178
50
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
Embodiments of the invention relate to synchronization of data in a shared pool of configurable computer resources. An image of the filesystem changes, including data and metadata, is captured in the form of a consistency point. Sequential consistency points are created, with changes to data and metadata in the filesystem between sequential consistency captured and placed in a queue for communication to a target filesystem at a target site. The changes are communicated as a filesystem operation, with the communication limited to the changes captured and reflected in the consistency point.
Claims
exact text as granted — not AI-modified1 . (canceled)
2 . (canceled)
3 . (canceled)
4 . (canceled)
5 . (canceled)
6 . (canceled)
7 . (canceled)
8 . (canceled)
9 . (canceled)
10 . A system comprising:
a server having memory in communication with a processing unit, and associated with a filesystem; the server in communication with a shared pool of configurable computer resources; a functional unit in communication with the processing unit, the functional unit comprising:
a data manager to process data at a source site in the shared pool, including periodic creation of a consistency point in a source filesystem of the source site at a file set level, each consistency point to represent source filesystem data and metadata at a point-in-time to establish a recovery point, including the data manager to create a first consistency point at a first point-in-time and a second consistency point at a second point-in-time;
a delta manager in communication with the data manager, the delta manager to compare the first consistency point with the second consistency point, including identification of any differences between the first and second consistency points; and
a data mover in communication with the delta manager, the data mover to apply the identified differences between the first and second consistency points, including a replay of the identified differences based upon a mapping of file system objects.
11 . The system of claim 10 , wherein the data mover employs a map of a source filesystem inode to a target filesystem inode to apply the identified differences.
12 . The system of claim 10 , wherein application of the identified differences by the data mover includes identification of filesystem operations on filesystem objects using file names.
13 . The system of claim 10 , wherein the delta manager produces an exact delta from the identified differences, the exact delta including any metadata change and any data change, and the data mover to replay only those changes reflected in the exact delta.
14 . The system of claim 10 , further comprising the data mover to generate an output file for the identified difference and to support a concurrent replay of a series of filesystem operation to a target site.
15 . The system of claim 10 , further comprising the data mover to replay the output file after communication failure between the source site and a target site.
16 . A computer program product comprising a non-transitory computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising:
computer readable program code configured to process data at a source site in a shared pool of configurable resources, including periodic creation of a consistency point in a source filesystem of the source site at a file set level, each consistency point to represent source filesystem data and metadata at a point-in-time to establish a recovery point, the periodic creation of the consistency point including the creation of a first consistency point at a first point-in-time and a second consistency point at a second point-in-time; computer readable program code configured to compare the first consistency point with the second consistency point, including identification of any differences between the first and second consistency points; computer readable program code configured to map filesystem objects; and computer readable program code configured to apply the identified differences between the first and second consistency points, including replaying the identified differences as one or more filesystem operations based upon the mapping of the filesystem objects.
17 . The computer program product of claim 16 , wherein the program code to apply the identified differences employs a mapping of a source filesystem inode to a target filesystem inode.
18 . The computer program product of claim 16 , wherein the program code to apply the identified differences includes program code to identify filesystem operations on filesystem objects using file names.
19 . The computer program product of claim 16 , wherein the code configured to apply the identified differences between the first and second consistency points produces an exact delta of any metadata change and any data change, and replays only those changes reflected in the exact delta.
20 . The computer program produce of claim 16 , further comprising computer program code configured to generate an output file for the identified differences and to concurrently apply the identified differences between the first and second consistency points to support multiple concurrent filesystem operations.
21 . The computer program product of claim 16 , further comprising computer program code configured to replay the output file after communication failure between the source site and a target site.
22 . The computer program product of claim 16 , wherein the first and second consistency points are not limited to successive consistency points.
23 . The computer program product of claim 16 , further comprising computer program code configured to revert changes at the target filesystem by moving to an older consistency point.
24 . (canceled)
25 . (canceled)Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.