IP Library Granted Patent US 9,588,858
Granted Patent B2
US 9,588,858 · App. 12/955,299 · Granted Mar 7, 2017

Periodic data replication

Inventors: Xiaopin Wang (Beijing, CN); Haiyang Zhang (Beijing, CN); Shaorong Li (Beijing, CN)
Assignee: CA, Inc.
G06F11/2097G06F11/1662G06F11/2038
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 9,588,858
App. No.
12/955,299
Granted
Mar 7, 2017
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 (51)

1. A method for data replication from a production server to a backup server, comprising:

recording an operation performed on a data item stored in a volume of a production server, wherein the operation is recorded as a journal event in a memory;

determining whether a system malfunction incident has occurred in the production server;

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,

wherein the system malfunction incident comprises a storage capacity of the memory reaching a threshold.

2. A method for data replication from a production server to a backup server, comprising:

recording an operation performed on a data item stored in a volume of a production server, wherein the operation is recorded as a journal event in a memory;

determining whether a system malfunction incident has occurred in the production server;

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,

wherein the system malfunction incident comprises failure of a connection between the production and backup servers.

3. The method of claim 2 , further comprising evaluating if the connection between the production and backup servers is re-established before sending the journal event stored in the auxiliary storage unit to the backup server.

4. A method for data replication from a production server to a backup server, comprising:

recording an operation performed on a data item stored in a volume of a production server, wherein the operation is recorded as a journal event in a memory;

determining whether a system malfunction incident has occurred in the production server;

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;

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

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,

wherein the system malfunction incident comprises failure to capture the snapshot of the volume of the production server.

5. A method for data replication from a production server to a backup server, comprising:

recording an operation performed on a data item stored in a volume of a production server, wherein the operation is recorded as a journal event in a memory;

determining whether a system malfunction incident has occurred in the production server;

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;

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

capturing a snapshot of the volume of the production server;

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

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.

6. A system for data replication from a production server to a backup server, comprising:

a processor, comprising hardware, configured to:

record an operation on a data item stored in a volume of a production server, wherein the operation is recorded as a journal event in a memory;

determine whether a system malfunction incident has occurred in the production server;

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,

wherein the system malfunction incident comprises a storage capacity of the memory reaching a threshold.

7. 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:

record an operation on a data item stored in a volume of a production server, wherein the operation is recorded as a journal event in a memory;

determine whether a system malfunction incident has occurred in the production server;

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,

wherein the system malfunction incident comprises failure of a connection between the production and backup servers.

Assignments (3)
MERGER Recorded Oct 24, 2013
From: COMPUTER ASSOCIATES THINK, INC.
To: CA, INC.
Reel/Frame 031473/0763 →
CORRECTIVE ASSIGNMENT TO CORRECT THE THIRD ASSIGNOR'S NAME PREVIOUSLY RECORDED ON REEL 025427 FRAME 0242. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jan 10, 2011
From: WANG, XIAOPIN; ZHANG, HAIYANG; LI, SHAORONG
To: COMPUTER ASSOCIATES THINK, INC.
Reel/Frame 025606/0692 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 29, 2010
From: WANG, XIAOPIN; ZHANG, HAIYANG; LI, SHOARONG
To: COMPUTER ASSOCIATES THINK, INC.
Reel/Frame 025427/0242 →
Continuity (1)
Related Publication 20120136827A1 · May 31, 2012