Techniques for proactive synchronization of backups on replication targets

• US 8,438,347 B1
• Filed: 03/27/2008
• Issued: 05/07/2013
• Est. Priority Date: 03/27/2008
• Status: Active Grant

• Current Assignee: Veritas Technologies, LLC (Whitehouse Group Ltd.)
• Original Assignee: Symantec Corporation (NortonLifeLock Inc.)
• Inventors: Tawri, Deepak, Krishnan, Sasidharan, Josyula, Subrahmanyam
• Primary Examiner(s): BATAILLE, PIERRE MICHE
• Application Number:
  US12/056,871
• Time in Patent Office: 1,867 Days
• Field of Search: 711/162, 711/165, 711/161, 711/E12.001, 711/112, 711/114
• US Class Current: 711/162
• CPC Class Codes: G06F 11/1456 Hardware arrangements for backup
• CPC Class Codes: G06F 11/2071 using a plurality of controllers
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency ensuring consistency in mirrored systems G06F11/2064
• CPC Class Codes: G06F 2201/855 Details of asynchronous mirroring using a journal to transfer not-yet-mirrored changes

Abstract

Techniques for proactive synchronization of backups on replication targets are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for proactive synchronization of a backup on a replication target comprising reading a stored replication request to obtain replication data address information, sending the replication data address information to a replication target, receiving the replication data address information at the replication target, and copying data associated with the received replication data address information to a backup.

Claims

1. A system for proactive synchronization of a backup on a replication target comprising:

one or more processors communicatively coupled to a server;

wherein the server is configured to;

read a stored replication request associated with a primary node to obtain replication data address information;

send the replication data address information to a secondary node utilizing a control message, wherein the control message signals that the primary node is sending the replication data address information to the secondary node, the secondary node freezes data storage based at least in part upon the control message, and wherein the primary node continues sending replication data address information until the secondary node sends a control message to the primary node;

receive the replication data address information at the secondary node; and

copy data associated with the received replication data address information from the secondary node to a backup storage.

2. The system of claim 1, wherein the replication data address information comprises a length and an offset of the data.

3. The system of claim 1, wherein the backup is one of a full snapshot, a space optimized snapshot, a backup from a copy on write process, and a storage mirror.

4. The system of claim 1, where the processor is further configured to utilize a data message to send replication data address information from a primary node to the secondary node.

5. The system of claim 1, wherein the control message is an in band control message.

6. The system of claim 1, wherein the stored replication request is read from at least one of a replication log and a replication cache.

7. An article of manufacture for proactive synchronization of a backup on a replication target, the article of manufacture comprising:

at least one non-transitory processor readable storage medium; and

instructions carried on the at least one medium;

wherein the instructions are configured to be readable from the at least one medium by at least one processor and thereby cause the at least one processor to operate so as to;

read a stored replication request associated with a primary node to obtain replication data address information;

send the replication data address information to a secondary node utilizing a control message, wherein the control message signals that the primary node is sending the replication data address information to the secondary node, the secondary node freezes data storage based at least in part upon the control message, and wherein the primary node continues sending replication data address information until the secondary node sends a control message to the primary node;

receive the replication data address information at the secondary node; and

copy data associated with the received replication data address information from the secondary node to a backup storage.

8. A method for proactive synchronization of a backup on a replication target comprising:

reading, using at least one computer processor, a stored replication request associated with a primary node to obtain replication data address information;

sending the replication data address information to a secondary node utilizing a control message, wherein the control message signals that the primary node is sending the replication data address information to the secondary node, the secondary node freezes data storage based at least in part upon the control message, and wherein the primary node continues sending replication data address information until the secondary node sends a control message to the primary node;

receiving the replication data address information at the secondary node; and

copying data associated with the received replication data address information from the secondary node to backup storage.

9. The method of claim 8 wherein the replication data address information comprises a length and an offset of the replication data.

10. The method of claim 8, wherein the backup is one of a full snapshot, a space optimized snapshot, a backup from a copy on write process, and a storage mirror.

11. The method of claim 8, further comprising utilizing a data message to send the replication data address information from a primary node to the secondary node.

12. The method of claim 8, wherein the control message is an in band control message.

13. The method of claim 8, wherein the stored replication request is read from at least one of a replication log and a replication cache.

14. The method of claim 8, wherein the stored replication request is read from a primary node.

15. The method of claim 8, wherein the stored replication request is read from a secondary node.

16. At least one non-transitory processor readable storage medium storing a computer program of instructions configured to be readable by at least one processor for instructing the at least one processor to execute a computer process for performing the method as recited in claim 8.