IP Library Granted Patent US 10,503,616
Granted Patent B2
US 10,503,616 · App. 15/439,513 · Granted Dec 10, 2019

Periodic data replication

Inventors: Xiaopin Wang (Beijing, CN); Haiyang Zhang (Beijing, CN); Shaorong Li (Beijing, CN)
Assignee: CA, Inc.
G06F11/2038G06F11/1464G06F11/1662G06F11/2097G06F16/27H04L67/1095G06F2201/84
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,503,616
App. No.
15/439,513
Granted
Dec 10, 2019
Kind
B2
Abstract

Systems and methods for replicating data from a production server to a backup server include recording at least one operation on one or more data items stored in a volume of a production server. The operation may be recorded as at least one journal event in a memory. A determination may then be made regarding whether a system malfunction incident has occurred in the production server and if so, a first set of journal events may be transferred from the memory to an auxiliary storage at a first time instant. At a second time instant, a second set of journal events recorded in the memory between the first and second time instants may be transferred to the auxiliary storage. At one journal event stored in the auxiliary storage unit may then be sent for replication to a backup server.

Claims (73)

1. A method, comprising:

determining whether a system malfunction incident has occurred in a production server that has recorded an operation performed on a data item stored in a volume of the production server as a journal event in a memory, wherein:

the system malfunction incident comprises:

a storage capacity of the memory reaching a threshold;

failure of a connection between the production and backup servers; and/or

failure to capture the snapshot of the volume of the production server; and

the system malfunction prevents or halts replication from the operational production server to a backup server, prevents or halts recording of the operation performed on the data item, and/or prevents or halts capturing in the operational production server of a snapshot of data for replication;

transferring the journal event from the memory to an auxiliary storage unit at a first time instant, responsive to a determination that the system malfunction incident has occurred;

transferring, at a second time instant, an additional journal event recorded in the memory between the first and second time instants to the auxiliary storage unit; and

sending the journal event stored in the auxiliary storage unit for replication to a backup server.

2. The method of claim 1 , further comprising consolidating the journal event with a previously recorded journal event as the journal event is recorded in the memory.

3. The method of claim 1 , further comprising:

consolidating the journal event and the additional journal event in the auxiliary storage as an event sequence; and

sending at least part of the event sequence for replication to a backup server.

4. The method of claim 1 , wherein the operation is recorded as the journal event without recording data content associated with the operation.

5. The method of claim 1 , further comprising:

capturing a snapshot of the volume of the production server; and

sending a point in time of the capturing of the snapshot to the backup server.

6. The method of claim 5 , wherein the capturing the snapshot invokes the transferring step at the second time instant.

7. The method of claim 5 , further comprising:

retrieving data associated with the journal event stored in the auxiliary storage unit from the captured snapshot; and.

sending the retrieved data along with the journal event stored in the auxiliary storage unit to the backup server.

8. The method of claim 1 , comprising:

steps for data replication from a primary server to replica server.

9. The method of claim 1 , the auxiliary storage unit comprises means for acting as a backup server.

10. The method of claim 1 , comprising steps for copying data items in a consistent state.

11. The method of claim 1 , comprising steps for performing an initial synchronization.

12. A system comprising:

a hardware processor system configured to:

determine whether a system malfunction incident has occurred in a production server that has recorded an operation performed on a data item stored in a volume of the production server as a journal event in a memory, wherein:

the system malfunction incident comprises:

a storage capacity of the memory reaching a threshold;

failure of a connection between the production and backup servers; and/or

failure to capture the snapshot of the volume of the production server; and

the system malfunction prevents or halts replication from the operational production server to a backup server, prevents or halts recording of the operation performed on the data item, and/or prevents or halts capturing in the operational production server of a snapshot of data for replication;

transfer the journal event from the memory to an auxiliary storage unit at a first time instant, responsive to a determination that the system malfunction incident has occurred;

transfer, at a second time instant, an additional journal event recorded in the memory between the first and second time instants to the auxiliary storage unit; and

send the journal event stored in the auxiliary storage unit for replication to a backup server.

13. The system of claim 12 , wherein the processor system is further configured to consolidate the journal event with a previously recorded journal event as the journal event is recorded in the memory.

14. The system of claim 12 , wherein the processor system is further configured to:

consolidate the journal event and the additional journal event in the auxiliary storage as an event sequence; and

send at least part of the event sequence for replication to a backup server.

15. The system of claim 14 , wherein the operation is recorded as the journal event without recording data content associated with the operation.

16. The system of claim 12 , wherein the processor system is further configured to:

capture a snapshot of the volume of the production server; and

send a point in time of the capturing of the snapshot to the backup server.

17. The system of claim 16 , wherein the processor system is further configured to transfer the additional journal event at the second time instant after capturing a snapshot of the volume of the production server.

18. The system of claim 16 , wherein the processor system is further configured to:

retrieve data associated with the journal event stored in the auxiliary storage unit from the captured snapshot; and

send the retrieved data along with the journal event stored in the auxiliary storage unit to the backup server.

19. The system of claim 12 , wherein:

the hardware processor system is configured to execute steps for data replication from a primary server to replica server.

20. The system of claim 12 , the auxiliary storage unit comprises means for acting as a backup server.

21. The system of claim 12 , wherein the hardware processor system is configured to execute steps for copying data items in a consistent state.

22. The system of claim 12 , wherein the hardware processor system is configured to execute steps for performing an initial synchronization.

23. A computer program product comprising:

a non-transitory computer readable storage medium storing information, the stored information comprising:

instructions configured to cause a processor to:

determine whether a system malfunction incident has occurred in a production server that has recorded an operation performed on a data item stored in a volume of the production server as a journal event in a memory, wherein:

the system malfunction incident comprises:

a storage capacity of the memory reaching a threshold;

failure of a connection between the production and backup servers; and/or

failure to capture the snapshot of the volume of the production server; and

the system malfunction prevents or halts replication from the operational production server to a backup server, prevents or halts recording of the operation performed on the data item, and/or prevents or halts capturing in the operational production server of a snapshot of data for replication;

transfer the journal event from the memory to an auxiliary storage unit at a first time instant, responsive to a determination that the system malfunction incident has occurred;

transfer, at a second time instant, an additional journal event recorded in the memory between the first and second time instants to the auxiliary storage unit; and

send the journal event stored in the auxiliary storage unit for replication to a backup server.

24. The computer program product of claim 23 , further comprising instructions configured to cause the processor to:

consolidate the journal event and the additional journal event in the auxiliary storage as an event sequence; and

send at least part of the event sequence for replication to a backup server.

25. The computer program product of, claim 23 , further comprising instructions configured to cause the processors to:

retrieve data associated with the journal event stored in the auxiliary storage unit from the captured snapshot; and

send the retrieved data along with the journal event stored in the auxiliary storage unit to the backup server.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 22, 2017
From: WANG, XIAOPIN; ZHANG, HAIYANG; LI, SHAORONG
To: COMPUTER ASSOCIATES THINK, INC.
Reel/Frame 041344/0301 →
MERGER Recorded Feb 22, 2017
From: COMPUTER ASSOCIATES THINK, INC.
To: CA, INC.
Reel/Frame 041344/0476 →
Continuity (2)
Continuation 12955299 · Nov 29, 2010
Related Publication 20170161161A1 · Jun 8, 2017