System and method for providing assured recovery and replication

• US 8,495,019 B2
• Filed: 03/08/2011
• Issued: 07/23/2013
• Est. Priority Date: 03/08/2011
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Shisheng, Liu, Harless, Eric, Ignatius, Paul Puthur
• Primary Examiner(s): LE, THU NGUYET T
• Application Number:
  US13/043,201
• Publication Number:
  US 20120233123A1
• Time in Patent Office: 868 Days
• Field of Search: 707/639, 707674-677
• US Class Current: 707/639
• CPC Class Codes: G06F 11/004 Error avoidance G06F11/07 and subgroups take precedence
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency ensuring consistency in mirrored systems G06F11/2064

Abstract

The system and method for providing assured recovery and replication described herein may recover a master data source from a replica data source without impacting the master data source or the replica data source, and without having to install a standby version of an application associated with the master data source. In particular, a master snapshot may be created to copy application data stored in the master data source, wherein a replication server confirms that the replica data source can recover the master data source if the master snapshot and the replica data source are consistent. The replication server may create a replica snapshot to copy the replica data source and assign an identity associated with the master data source to the replica data source to recover the master data source. As such, replication may be resumed on a virtual machine disk file associated with the replica snapshot.

Claims

1. A system to provide assured recovery and replication, the system comprising:

a replication server in communication with a master data source configured to store application data and a replica data source configured to replicate the application data stored in the master data source, wherein the replication server comprises a processor comprising hardware, the processor configured to;

confirm that the master data source can be recovered from the replica data source in response to validating that the application data copied in a master snapshot associated with the master data source and the application data replicated in the replica data source have a consistent state, wherein the master snapshot copies the application data stored in the master data source;

create a replica snapshot associated with the replica data source in response to a request to recover the master data source from the replica data source, wherein the replica snapshot copies the application data replicated in the replica data source;

assign an identity associated with the master data source to the replica data source to transfer control over storing the application data from the master data source to the replica data source; and

replicate the application data on a virtual machine disk file associated with the replica snapshot.

2. The system of claim 1, further comprising a volume snapshot service configured to create the master snapshot, wherein the volume snapshot service is further configured to record a bookmark associated with the master snapshot to distinguish the master snapshot from an additional master snapshot created with the volume snapshot service.

3. The system of claim 1, wherein the processor associated with the replication server is further configured to:

compare metadata that describes the master snapshot to metadata that describes the replica data source;

validate the consistent state between the master snapshot and the replica data source in response to confirming that no difference exists between the metadata that describes the master snapshot and the metadata that describes the replica data source; and

establish the consistent state between the master snapshot and the replica data source at a nearest previous point in time in response to determining that a difference exists between the metadata that describes the master snapshot and the metadata that describes the replica data source.

4. The system of claim 1, wherein the processor associated with the replication server is further configured to:

perform a binary difference comparison between the master snapshot and the replica data source;

validate the consistent state between the master snapshot and the replica data source in response to the binary difference comparison confirming that no difference exists between the master snapshot and the replica data source; and

establish the consistent state between the master snapshot and the replica data source at a nearest previous point in time in response to the binary difference comparison identifying a difference between the master snapshot and the replica data source.

5. The system of claim 4, wherein the processor associated with the replication server is further configured to limit the binary difference comparison to a file that has changed in the master snapshot or the replica data source.

6. The system of claim 1, wherein the processor associated with the replication server is further configured to:

suspend replication of the application data stored in the master data source to the replica data source while validating the consistent state between the master snapshot and the replica data source; and

resume replication of the application data stored in the master data source to the replica data source in response to validating the consistent state between the master snapshot and the replica data source.

7. The system of claim 1, wherein the processor associated with the replication server is further configured to:

compare the master snapshot to the replica snapshot associated with the replica data source to validate the consistent state between the master snapshot and the replica data source; and

permit replication of the application data stared in the master data source to the replica data source while comparing the master snapshot to the replica snapshot to validate the consistent state between the master snapshot and the replica data source.

8. The system of claim 1, wherein the processor associated with the replication server is further configured to:

replicate information associated with an application and an operating system that interacts with the master data source to the virtual machine disk file;

create the replica snapshot associated with the replica data source from the virtual machine disk file;

boot a virtual machine created from the virtual machine disk file; and

assign the identity associated with the master data source to the replica data source in response to verifying that the application and the operating system have a healthy state in the virtual machine created from the virtual machine disk file.

9. The system of claim 1, wherein the processor is further configured to generate a report that describes any delay associated with replication of the application data to the replica data source or the virtual machine disk file based on a timestamp in a message associated with replication of the application data.

10. The system of claim 1, wherein the processor is further configured to:

execute an operation that applies a change to the application data stored in the master data source; and

generate a report that describes whether the master data source and the replica data source are correctly replicating based on whether the change applied to the master data source has been applied to the replica data source.

11. A method to provide assured recovery and replication, the method comprising:

confirming that a master data source can be recovered from a replica data source, the replica data source replicating application data stored in the master data source, in response to a replication server validating that the application data copied in a master snapshot associated with the master data source and the application data replicated in the replica data source have a consistent state, wherein the master snapshot copies the application data stored in the master data source;

creating a replica snapshot associated with the replica data source in response to a request to recover the master data source from the replica data source, wherein the replica snapshot copies the application data replicated in the replica data source;

assigning an identity associated with the master data source to the replica data source, wherein the replication server assigns the identity associated with the master data source to the replica data source to cause the replica data source to assume control over storing the application data from the master data source; and

replicating the application data on a virtual machine disk file associated with the replica snapshot in response to the replica data source assuming control over storing the application data from the master data source.

12. The method of claim 11, further comprising invoking a volume snapshot service to create the master snapshot, wherein the volume snapshot service records a bookmark associated with the master snapshot to distinguish the master snapshot from an additional master snapshot created with the volume snapshot service.

13. The method of claim 11, further comprising:

comparing metadata that describes the master snapshot to metadata that describes the replica data source;

validating the consistent state between the master snapshot and the replica data source in response to confirming that no difference exists between the metadata that describes the master snapshot and the metadata that describes the replica data source; and

establishing the consistent state between the master snapshot and the replica data source at a nearest previous point in time in response to determining that a difference exists between the metadata that describes the master snapshot and the metadata that describes the replica data source.

14. The method of claim 11, further comprising:

performing a binary difference comparison between the master snapshot and the replica data source;

validating the consistent state between the master snapshot and the replica data source in response to the binary difference comparison confirming that no difference exists between the master snapshot and the replica data source; and

establishing the consistent state between the master snapshot and the replica data source at a nearest previous point in time in response to the binary difference comparison identifying a difference between the master snapshot and the replica data source.

15. The method of claim 14, further comprising limiting the binary difference comparison to a file that has changed in the master snapshot or the replica data source.

16. The method of claim 11, further comprising:

suspending replication between the application data stored in the master data source and the replicated application data stored in the replica data source while validating the consistent state between the master snapshot and the replica data source; and

resuming replication between the application data stored in the master data source and the replicated application data stored in the replica data source in response to validating the consistent state between the master snapshot and the replica data source.

17. The method of claim 11, further comprising:

comparing the master snapshot to the replica snapshot associated with the replica data source to validate the consistent state between the master snapshot and the replica data source; and

permit replication between the application data stored in the master data source and the replicated application data stored in the replica data source while validating the consistent state between the master snapshot and the replica data source.

18. The method of claim 11, further comprising:

replicating information associated with an application and an operating system that interacts with the master data source to the virtual machine disk;

creating the replica snapshot associated with the replica data source from the virtual machine disk file;

booting a virtual machine created from the virtual machine disk file; and

assigning the identity associated with the master data source to the replica data source in response to verifying that the application and the operating system have a healthy state in the virtual machine created from the virtual machine disk file.

19. The method of claim 11, further comprising generating a report that describes any delay associated with replicating the application data to the replica data source or the virtual machine disk file based on a timestamp in a message associated with replicating the application data.

20. The method of claim 11, further comprising:

executing an operation that applies a change to the application data stored in the master data source; and

generating a report that describes whether the master data source and the replica data source are correctly replicating based on whether the change applied to the master data source has been applied to the replica data source.

21. A computer program product comprising:

a non-transitory computer readable storage medium comprising computer-readable program code embodied therewith to provide assured recovery and replication, the computer readable program code comprising;

computer readable program code configured to confirm that a master data source can be recovered from a replica data source, the replica data source replicating application data stored in the master data source, in response to a replication server validating that the application data copied in a master snapshot associated with the master data source and the application data replicated in the replica data source have a consistent state, wherein the master snapshot copies the application data stored in the master data source;

computer readable program code configured to create a replica snapshot associated with the replica data source in response to a request to recover the master data source from the replica data source, wherein the replica snapshot copies the application data replicated in the replica data source;

computer readable program code configured to assign an identity associated with the master data source to the replica data source, wherein the replication server assigns the identity associated with the master data source to the replica data source to cause the replica data source to assume control over storing the application data from the master data source; and

computer readable program code configured to replicate the application data on a virtual machine disk file associated with the replica snapshot in response to the replica data source assuming control over storing the application data from the master data source.

22. The computer program product of claim 21, further comprising:

computer readable program code configured to compare metadata that describes the master snapshot to metadata that describes the replica data source;

computer readable program code configured to validate the consistent state between the master snapshot and the replica data source in response to confirming that no difference exists between the metadata that describes the master snapshot and the metadata that describes the replica data source; and

computer readable program code configured to establish the consistent state between the master snapshot and the replica data source at a nearest previous point in time in response to determining that a difference exists between the metadata that describes the master snapshot and the metadata that describes the replica data source.

23. The computer program product of claim 21, further comprising:

computer readable program code configured to perform a binary difference comparison between the master snapshot and the replica data source;

computer readable program code configured to validate the consistent state between the master snapshot and the replica data source in response to the binary difference comparison confirming that no difference exists between the master snapshot and the replica data source; and

computer readable program code configured to establish the consistent state between the master snapshot and the replica data source at a nearest previous point in time in response to the binary difference comparison identifying a difference between the master snapshot and the replica data source.

24. The computer program product of claim 21, further comprising:

computer readable program code configured to suspend replication between the application data stored in the master data source and the replicated application data stored in the replica data source while validating the consistent state between the master snapshot and the replica data source; and

computer readable program code configured to resume replication between the application data stored in the master data source and the replicated application data stored in the replica data source in response to validating the consistent state between the master snapshot and the replica data source.

25. The computer program product of claim 21, further comprising:

computer readable program code configured to compare the master snapshot to the replica snapshot associated with the replica data source to validate the consistent state between the master snapshot and the replica data source; and

computer readable program code configured to permit replication between the application data stored in the master data source and the replicated application data stored in the replica data source while validating the consistent state between the master snapshot and the replica data source.

26. The computer program product of claim 21, further comprising:

computer readable program code configured to replicating information associated with an application and an operating system that interacts with the master data source to the virtual machine disk file;

computer readable program code configured to create the replica snapshot associated with the replica data source from the virtual machine disk file;

computer readable program code configured to boot a virtual machine created from the virtual machine disk file; and

computer readable program code configured to assign the identity associated with the master data source to the replica data source in response to verifying that the application and the operating system have a healthy state in the virtual machine created from the virtual machine disk file.

27. The computer program product of claim 21, further comprising computer readable program code configured to generate a report that describes any delay associated with replicating the application data to the replica data source or the virtual machine disk file based on a timestamp in a message associated with replicating the application data.

28. The computer program product of claim 21, further comprising:

computer readable program code configured to execute an operation that applies a change to the application data stored in the master data source; and

computer readable program code configured to generate a report that describes whether the master data source and the replica data source are correctly replicating based on whether the change applied to the master data source has been applied to the replica data source.