Synchronization of mutually shared data stored on network devices

• US 8,291,101 B1
• Filed: 12/08/2005
• Issued: 10/16/2012
• Est. Priority Date: 12/08/2005
• Status: Active Grant

• Current Assignee: Pulse Secure, LLC (Ivanti Software, Inc.)
• Original Assignee: Juniper Networks Incorporated
• Inventors: Tock, Theron, Yan, Xudong, Kougiouris, Panagiotis
• Primary Examiner(s): Lazaro, David
• Assistant Examiner(s): KIM, EDWARD J
• Application Number:
  US11/297,595
• Time in Patent Office: 2,504 Days
• Field of Search: 709201-203, 709212-216, 709217-219, 709/248, 709230-236, 707/10, 707/100, 707/104, 707/200, 707203-206, 707610-615, 707/685
• US Class Current: 709/231
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Techniques are described for resynchronizing mutually shared data stored on network devices of a computer network. Upon receiving change instruction and globally unique identifier (GUID) messages, each of the network devices records the change instructions and GUIDs in a journal of the network device. When communication is lost for a period of time between a first network device and a second network device, the mutually shared data of the first network device may need to be resynchronized with the mutually shared data of the second network device. The techniques described herein allow resynchronization of the mutually shared data of the first network device based on a common GUID recorded in the journals of both first and second network devices, the journal of the first network device, and the journal of the second network device.

Claims

1. A method of resynchronizing copies of mutually shared data stored by a network device and a second network device, the method comprising:

receiving a plurality of messages from the second network device coupled to the network device via a network using an agreed-order protocol that requires the network device and the second network device to exchange and process the messages in a defined order in accordance with a sequence number within each of the messages,

wherein the plurality of messages includes one or more messages containing change instructions to modify the mutually shared data and at least one message containing a unique identifier,

wherein each of the network device and the second network device maintain a respective journal, and

wherein the unique identifier received from the second device is a bookmark recorded in an entry in the journal of the second device and indicates that the second device has processed all change instructions that preceded the unique identifier in the journal of the second device to modify a copy of the mutually shared data stored on the second device;

recording the change instructions and the unique identifier in respective entries of the journal of the network device in chronological order in which the change instructions and the unique identifier were sent by the second network device;

storing the exchanged unique identifiers and change instructions in an inbound message queues of the network device;

receiving a token from the second network device;

determining, based at least in part on the token, whether an interruption has occurred in a connection between the network device and the network; and

responsive to determining that the interruption occurred, resynchronizing the mutually shared data of the network device by at least sending a resynchronization request to the second network device that includes a sequence of unique identifiers recorded in the journal of the network device.

2. The method of claim 1, further comprising:

applying the change instructions to the mutually shared data stored by the network device.

3. The method of claim 1, wherein resynchronizing the mutually shared data of the network device comprises:

sending a resynchronization request to the second network device that includes a sequence of unique identifiers recorded in the journal of the network device;

comparing the sequence of unique identifiers in the resynchronization request with unique identifiers recorded in the journal of the second network device to determine a common unique identifier; and

receiving a resynchronization reply from the second network device that includes a sequence of change instructions and unique identifiers recorded in the journal of the second network device starting with the common unique identifier.

4. The method of claim 3, further comprising:

storing the mutually shared data in a database within the network device;

periodically storing a backup of the mutually shared data in a backup database within the network device; and

deleting from the journal of the network device any of the change instructions and unique identifiers that were received prior to storing the backup.

5. The method of claim 4, wherein resynchronizing the mutually shared data of the network device comprises:

finding the common unique identifier within the change instructions and unique identifiers recorded in the journal of the network device after storing the backup;

replacing the mutually shared data stored in the database of the network device with the mutually shared data stored in the backup database;

applying the change instructions recorded in the journal from the beginning of the journal to the common unique identifier; and

applying the change instructions included in the resynchronization reply.

6. The method of claim 3, wherein sending a resynchronization request to the second network device comprises collecting a chronologically-ordered sequence of unique identifiers from the journal of the network device.

7. The method of claim 3, wherein receiving a resynchronization reply from the second network device comprises receiving a chronologically-ordered sequence of change instructions and unique identifiers recorded in the journal of the second network device starting with the common unique identifier.

8. The method of claim 3, wherein determining a common unique identifier comprises determining the latest recorded unique identifier in the resynchronization request from the network device that is also recorded in the journal of the second network device.

9. The method of claim 3, wherein resynchronizing the mutually shared data of the network device comprises performing a textual comparison and resynchronization routine when a common unique identifier cannot be found in the journal of the network device and the journal of the second network device.

10. The method of claim 9, wherein performing the textual comparison and resynchronization routine comprises comparing canonical representations of the mutually shared data stored in a database within the network device and a database within the second network device.

11. The method of claim 9, wherein performing the resynchronization routine comprises:

receiving an alert from the second network device that a common unique identifier cannot be found;

creating a serialized version of the mutually shared data stored in a database within the network device;

dividing the serialized version of the mutually shared data stored in the database within the network device into a series of segments of fixed size;

calculating checksums for each of the segments;

sending the checksums to the second network device;

comparing the checksums to checksums calculated from the mutually shared data stored in a database within the second network device; and

receiving instructions from the second network device to correct the mutually shared data stored in the database of the network device.

12. The method of claim 1, further comprising:

sending a unique identifier to the second network device when a size of the journal of the network device surpasses a predetermined threshold;

storing a backup of the mutually shared data of the network device upon receiving a unique identifier;

deleting the change instructions and unique identifier entries in the journal of the network device; and

adding the received unique identifier to the journal of the network device.

13. The method of claim 1, wherein determining, based at least on the token, whether an interruption has occurred comprises receiving the token after a token timeout has expired.

14. The method of claim 1, wherein determining, based at least on the token, whether an interruption has occurred comprises receiving the token wherein the token contains an unexpected identifier.

15. The method of claim 1, wherein the network device and second network device comprise instant virtual extranet (IVE) devices.

16. The method of claim 1, wherein the unique identifier is a globally unique identifier.

17. A network device comprising:

a programmable processor;

a database to store data mutually shared between the network device and a second network device;

an inbound message queue to store messages received from the second network device using an agreed-order protocol that requires the network device and the second network device to exchange and process the messages in a defined order in accordance with a sequence number within each of the messages, wherein the messages include one or more messages of a first type containing change instructions to modify the mutually shared data and one or more messages of a second type each containing a unique identifier, and wherein each of the unique identifiers received from the second device is a bookmark recorded in an entry of a journal of the second device and indicates that the second device has processed all change instructions that preceded the unique identifier in the journal of the second device;

a non-transitory computer-readable medium to store a journal having a plurality of entries to record the change instructions and the unique identifiers in a chronological order in which the second network device sent the change instructions and the unique identifiers to the network device; and

a synchronization service module operable by the programmable processor to receive a token from the second network device, determine, based at least in part on the token, whether an interruption has occurred in a connection between the network device and the network, and responsive to determining that the interruption occurred, and resynchronize the mutually shared data of the network device by sending a resynchronization request to the second network device that includes a sequence of the unique identifiers recorded in the journal of the network device.

18. The network device of claim 17, wherein the synchronization service module is further operable by the programmable processor to detect restored communication with the second network device.

19. The network device of claim 17, wherein the synchronization service module is further operable by the programmable processor to receive change instructions that describe a change in the mutually shared data, and apply the change instructions to the mutually shared data.

20. The network device of claim 17, wherein the synchronization service module is further operable by the programmable processor to receive a resynchronization request from the second network device that specifies a sequence of unique identifiers recorded in the journal of the second network device, compare the sequence of unique identifiers with unique identifiers recorded in the journal of the network device to determine a common unique identifier, and send a sequence of change instructions and unique identifiers in the journal following the common unique identifier to the second network device.

21. The network device of claim 17, wherein the synchronization service module is further operable by the programmable processor to send a resynchronization request to the second network device that includes a sequence of unique identifiers recorded in the journal, and receive a resynchronization reply from the second network device that includes a sequence of change instructions and unique identifiers that follow a last common unique identifier present in the journal and a journal of the second network device.

22. The network device of claim 20, further comprising:

a backup database to store a backup of the mutually shared data,

wherein the journal records unique identifiers and change instructions received by the network device after storing a backup of the mutually shared data in the backup database.

23. The network device of claim 22, wherein the synchronization service module is further operable by the programmable processor to record the resynchronization reply in the journal following the common unique identifier recorded in the journal, replace the mutually shared data stored in the database of the network device with the mutually shared data stored in the backup database, and apply the change instructions recorded in the journal to the mutually shared data stored in the database within the network device.

24. The network device of claim 23, wherein the synchronization service module is further operable by the programmable processor to delete entries in the journal following the common unique identifier prior to recording the resynchronization reply in the journal of the network device following the common unique identifier.

25. The network device of claim 21, wherein the resynchronization request comprises a chronologically-ordered sequence of unique identifiers from the journal.

26. The network device of claim 21, wherein the resynchronization reply comprises chronologically-ordered sequence of change instructions and unique identifiers recorded in the journal of the second network device starting with the common unique identifier.

27. The network device of claim 21, wherein the common unique identifier comprises the latest recorded unique identifier in the resynchronization request from the network device that is also recorded in the journal of the second network device.

28. The network device of claim 21, wherein the synchronization service module is further operable by the programmable processor to perform a textual comparison and resynchronization routine to resynchronize the mutually shared data of the network device when a common unique identifier cannot be found in the journal and the journal of the second network device.

29. The network device of claim 28, wherein the textual comparison and resynchronization routine comprises a comparison of canonical representations of the mutually shared data stored in the database and a database within the second network device.

30. The network device of claim 28, wherein the synchronization service module is further operable by the programmable processor to receive an alert from the second network device that a common unique identifier cannot be found, create a serialized version of the mutually shared data stored in the database, divide the serialized version of the mutually shared data stored in the database into a series of segments of fixed size, calculate checksums for each of the segments, send the checksums to the second network device, and receive instructions from the second network device to correct the mutually shared data stored in the database.

31. The network device of claim 28, wherein the synchronization service module is further operable by the programmable processor to send an alert to the second network device when a common unique identifier cannot be found, receive checksums from the second network device, compare the checksums to checksums calculated from the mutually shared data stored in the database, and send instructions to the second network device to correct the mutually shared data stored in a database of the second network device.

32. The network device of claim 17, wherein the synchronization service module is further operable by the programmable processor to send a unique identifier to the second network device when a number of entries in the journal surpasses a predetermined threshold, delete the change instructions and the unique identifiers recorded in the journal, and store a backup of the mutually shared data upon receiving a response unique identifier;

and record the response unique identifier as a first entry in the journal.

33. The network device of claim 17, wherein the network device and the second network devices comprise instant virtual extranet (IVE) devices.

34. The network device of claim 17, wherein the unique identifier is a globally unique identifier.

35. A non-transitory computer-readable storage medium storing instructions for resynchronizing mutually shared data stored by a network device and a second network device, the instructions comprising instructions that cause a programmable processor to:

receive a plurality of messages from a second network device coupled to the network device via a network using an agreed-order protocol that requires the network device and the second network device to exchange and process the messages in a defined order in accordance with a sequence number within each of the messages,

wherein the plurality of messages includes one or more messages containing change instructions to modify the mutually shared data and at least one message of containing a unique identifier,

wherein each of the network device and the second network device maintain a respective journal, and

wherein the unique identifier received from the second device is a bookmark recorded in an entry in the journal of the second device and indicates that the second device has processed all change instructions that preceded the unique identifier in the journal of the second device to modify the shared data stored on the second device;

record the change instructions and the unique identifier in respective entries of the journal of the network device in chronological order in which the change instructions and unique identifiers were sent by the second network device;

store the exchanged unique identifiers and change instructions in an inbound message queue of the network device;

receive a token from the second network device;

determine, based at least in part on the token, whether an interruption has occurred in a connection between the network device and the network; and

responsive to determining that the interruption occurred, resynchronize the mutually shared data of the network device by sending a resynchronization request to the second network device that includes a sequence of unique identifiers recorded in the network device.

36. The computer-readable medium of claim 35, further comprising instructions that cause the programmable processor to:

apply the change instructions to the mutually shared data.

37. The computer-readable medium of claim 35, wherein the instructions that cause the programmable processor to resynchronize the mutually shared data of the network device further cause the programmable process to:

send a resynchronization request to the second network device that includes a sequence of unique identifiers recorded in the journal of the network device;

compare the sequence of unique identifiers in the resynchronization request with unique identifiers recorded in a journal of the second network device to determine a common unique identifier; and

receive a resynchronization reply from the second network device that includes a sequence of change instructions and unique identifiers recorded in the journal of the second network device starting with the common unique identifier.

38. The computer-readable medium of claim 37, further comprising instructions that cause the programmable processor to:

store the mutually shared data in a database within the network device;

periodically store a backup of the mutually shared data in a backup database within the network device;

deleting from the journal of the network device the change instructions and unique identifiers that were received prior to storing the backup; and

record unique identifiers and change instructions received by the network device in the journal after storing the backup of the mutually shared data.

39. The computer-readable medium of claim 38, wherein the instructions that cause the programmable processor to resynchronize the mutually shared data of the network device further cause the programmable processor to:

record the resynchronization reply in the journal following the common unique identifier recorded in the journal;

replace the mutually shared data stored in the database of the network device with the mutually shared data stored in the backup database; and

apply the change instructions recorded in the journal to the mutually shared data stored in the database within the network device.

40. The computer-readable medium of claim 37, wherein the instructions that cause the programmable processor to resynchronize the mutually shared data of the network device further cause the programmable processor to perform a textual comparison and resynchronization routine when a common unique identifier cannot be found in the journal and the journal of the second network device.

41. The computer-readable medium of claim 37, wherein the instructions that cause the programmable processor to perform a resynchronization routine cause the programmable processor to:

receive an alert from the second network device that a common unique identifier cannot be found;

create a serialized version of the mutually shared data stored in a database within the network device;

divide the serialized version of the mutually shared data stored in the database into a series of segments of fixed size;

calculate checksums for each of the segments;

send the checksums to the second network device;

compare the checksums to checksums calculated from the mutually shared data stored in a database within the second network device; and

receive instructions from the second network device to correct the mutually shared data stored in the database of the network device.

42. The computer-readable medium of claim 35, further comprising instructions that cause the programmable processor to:

send a unique identifier to the second network device when a number of entries in the journal of the network device surpasses a predetermined threshold;

delete the change instructions and the unique identifiers recorded in the journal;

store a backup of the mutually shared data of the network device upon receiving a response unique identifier; and

record the response unique identifier as a first entry in the journal.