Mirroring data between primary and secondary sites

• US 7,877,628 B2
• Filed: 06/08/2006
• Issued: 01/25/2011
• Est. Priority Date: 06/08/2006
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Dewey, Douglas William, Day, Kenneth Fairclough III, Boyd, Kenneth Wayne
• Primary Examiner(s): Baderman; Scott T
• Assistant Examiner(s): Leibovich; Yair
• Application Number:
  US11/423,103
• Publication Number:
  US 20070288710A1
• Time in Patent Office: 1,692 Days
• Field of Search: 714/13
• US Class Current: 714/13
• CPC Class Codes: G06F 11/2069 Management of state, configuration or failover
• CPC Class Codes: G06F 11/2071 using a plurality of controllers
• CPC Class Codes: G06F 11/2082 Data synchronisation

Abstract

Provided are a method, system, and article of manufacture for mirroring data between a first site and a second site. Updates to segments of storage at the first site are copied to corresponding segments of storage at the second site. Codes are generated from the segments at the second site and a valid flag is provided for at least one code indicating whether the code for the segment of data is valid. One code is generated from each segment of storage at the first site. An operation is initiated to copy segments from the second site to the first site. A determination is made for segments at the second site as to whether the valid flag for the code for the segment at the second site indicates that the code is valid in response to initiating the copy operation. The valid code for at least one segment in the second site is compared with the code for the corresponding segment at the first site to determine whether to copy the data from the segment at the second site to the first site as part of the copy operation.

Claims

1. A method for synchronizing data between a primary storage managed by a primary server at a first site and a secondary storage managed by a secondary server at a second site, comprising:

copying updates to segments of the primary storage at the first site to corresponding segments of the secondary storage at the second site as part of a first copy operation;

providing codes generated from the segments in the secondary storage at the second site and a valid flag for at least one code indicating whether the code for the segment of data is valid;

setting the valid flag to indicate one of the segments of data as invalid in response to receiving an update to the segment of data that results in the current code for the segment not reflecting the updated state of that segment;

generating a new code for segments in the secondary storage whose valid flag indicates that the segment is invalid;

setting the valid flag for the segment for which the new code is calculated to indicate that the code for the segment is valid;

providing codes generated from segments of the primary storage at the first site;

initiating a second copy operation to copy segments from the secondary storage at the second site to the primary storage at the first site;

determining, for segments in the secondary storage at the second site, whether the valid flag for the code for the segment in the secondary storage at the second site indicates that the code is valid in response to initiating the second copy operation; and

comparing the code for at least one of the segments in the secondary storage at the second site determined to be valid with the code for the corresponding segment in the primary storage at the first site to determine whether to copy the data from the segment in the secondary storage at the second site to the primary storage at the first site as part of the second copy operation.

2. The method of claim 1, further comprising:

providing valid flags for codes generated from segments at the primary storage at the first site, wherein the code for at least one segment in the secondary storage at the second site is compared with the code for the corresponding segment in the primary storage at the first site if the valid flags for the corresponding segments in the primary and secondary storages at the first and second sites, respectively, indicate valid.

3. The method of claim 1, further comprising:

generating a new code for each segment in the secondary storage whose valid flag indicates that the segment is invalid from current data for the segment; and

comparing the new code for the segment in the secondary storage at the second site with the code for the corresponding segment in the primary storage at the first site to determine whether to copy the data from the segment in the primary storage at the second site to the primary storage at the first site in response to generating the new code.

4. The method of claim 1, further comprising:

copying data from the secondary storage at the second site to the primary storage at the first site if the codes do not match.

5. The method of claim 4, further comprising

copying data from the primary storage at the first site to the secondary storage at the second site while the first site is receiving updates;

receiving updates at the secondary storage at the second site in response to detecting a failure at the first site, wherein updates are not received at the first site while updates are being received at the second site; and

detecting an availability of the first site after the failure at the first site, wherein the copy operation is initiated in response to detecting the availability of the first site.

6. The method of claim 1, wherein the received update is stored in a cache, further comprising:

destaging updates for one segment from the cache to the secondary storage at the second site, wherein the new code is calculated for one segment in response to destaging the updates for the segment.

7. The method of claim 6, further comprising:

determining whether the cache includes a previous update for the block to which the received update applies; and

writing the received update to the block in cache to overwrite any previous update to the block in the cache, wherein the valid flag for the segment is only set to indicate that the code is invalid in response to determining that there is no previous update for the block in the cache.

8. The method of claim 6, further comprising:

staging one segment in the secondary storage at the second site into the cache in response to receiving an update to a block in the segment, wherein updated and unchanged portions of the segment are in the cache, and wherein the new code is calculated from the entire segment stored in the cache in response to destaging the segment.

9. The method of claim 1, wherein the received update is stored in a cache, further comprising:

destaging updates for one segment from the cache to the primary storage at the first site storage; and

initiating a background operation to calculate a new code for each segment whose valid flag indicates that the code is invalid.

10. A method for synchronizing data between a primary storage managed by a primary server at a first site and a secondary storage managed by a secondary server at a second site, comprising:

copying data from segments of the primary storage at the first site to corresponding segments of the secondary storage at the second site;

receiving updates at the secondary storage at the second site in response to detecting a failure at the first site, wherein updates are not received at the primary storage at the first site while updates are being received at the secondary storage at the second site;

detecting an availability of the first site before the first site is ready to begin receiving updates and mirroring updates to the secondary storage at the second site;

initiating operations to calculate codes for the segments at the primary and secondary storages at the first and second sites, respectively, in response to detecting the availability of the first site;

setting a valid flag to indicate one of the segments of data as invalid in response to receiving an update to the segment of data that results in the current code for the segment not reflecting the updated state of that segment;

generating a new code for segments in the secondary storage whose valid flag indicates that the segment is invalid;

setting the valid flag for the segment for which the new code is calculated to indicate that the code for the segment is valid;

initiating a synchronize operation to copy segments from the secondary storage at the second site to the primary storage at the first site in response to determining that the first site is ready to begin receiving updates and mirror updates to the secondary storage at the second site; and

comparing the codes for segments in the secondary storage at the second site with the codes for the corresponding segments in the primary storage at the first site to determine whether to copy the data from the segments in the secondary storage at the second site to the primary storage at the first site as part of the synchronize operation.

11. The method of claim 10, further comprising:

restoring at least one of the segments to the primary storage first site from a backup device in response to detecting the availability of the first site, wherein the operations to calculate the code are initiated while segments are being restored from the backup device.

12. A system for synchronizing data between a primary storage at a first site and a secondary storage at a second site, comprising:

a first system managing access to the primary storage at the first site;

a first copy manager program executed by the first system to perform operations comprising;

copying updates to segments of storage in the primary storage at the first site to corresponding segments of storage in the secondary storage at the second site as part of a first copy operation; and

providing codes generated from the segments of storage of the primary storage at the first site;

a second system managing access to the secondary storage at the second site; and

a second copy manager program executed by the second system to perform operations comprising;

providing codes generated from the segments in the secondary storage at the second site and a valid flag for at least one code indicating whether the code for the segment of data is valid;

setting the valid flag to indicate one of the segments of data as invalid in response to receiving an update to the segment of data that results in the current code for the segment not reflecting the updated state of that segment;

generating a new code for segments in the secondary storage whose valid flag indicates that the segment is invalid;

setting the valid flag for the segment for which the new code is calculated to indicate that the code for the segment is valid;

initiating a second copy operation to copy segments from the secondary storage at the second site to the primary storage at the first site;

determining, for segments in the secondary storage at the second site, whether the valid flag for the code for the segment in the secondary storage at the second site indicates that the code is valid in response to initiating the second copy operation; and

comparing the valid code for at least one of the segments in the secondary storage at the second site with the code for the corresponding segment in the primary storage at the first site to determine whether to copy the data from the segment in the secondary storage at the second site to the primary storage at the first site as part of the second copy operation.

13. The system of claim 12, wherein the first copy manager is executed to further provide valid flags for codes generated from segments in the primary storage at the first site, wherein the code for at least one segment in the secondary storage at the second site is compared with the code for the corresponding segment in the primary storage at the first site if the valid flags for the corresponding segments in the primary and secondary storages at the first and second sites, respectively, are valid.

14. The system of claim 12, wherein the first and second copy managers further generate a new code for each segment whose valid flag indicates that the segment is invalid from current data for the segment, and wherein the second copy manager further compares the new code for the segment in the secondary storage at the second site with the code for the corresponding segment in the primary storage at the first site to determine whether to copy the data from the segment in the secondary storage at the second site to the primary storage at the first site.

15. The system of claim 12, wherein the second copy manager further copies data from the secondary storage at the second site to the primary storage at the first site if the codes do not match.

16. The system of claim 12, further comprising:

a cache in the second system, wherein the received updates at the second system are stored in the cache, wherein the second copy manager further destages updates for one segment from the cache to the secondary storage at the second site storage, wherein the second copy manager calculates the new code for one segment in response to destaging the updates for the segment.

17. A system for synchronizing data between a primary storage at a first site and a secondary storage at a second site, comprising:

a first system managing access to the primary storage at the first site;

a second system managing access to the secondary storage at the second site;

a first copy manager executed by the first system and a second copy manager executed by the second system, wherein at least one of the first and second copy managers are executed to perform operations, the operations comprising;

copying data from segments of the primary storage at the first site to corresponding segments of the secondary storage at the second site;

receiving updates at the secondary storage at the second site in response to detecting a failure at the first site, wherein updates are not received at the primary storage at the first site while updates are being received at the secondary storage at the second site;

detecting an availability of the first site before the first site is ready to begin receiving updates and mirroring updates to the secondary storage at the second site;

initiating operations to calculate codes for the segments in the primary and secondary storages at the first and second sites, respectively, in response to detecting the availability of the first site;

setting a valid flag to indicate one of the segments of data as invalid in response to receiving an update to the segment of data that results in the current code for the segment not reflecting the updated state of that segment;

generating a new code for segments in the secondary storage whose valid flag indicates that the segment is invalid;

setting the valid flag for the segment for which the new code is calculated to indicate that the code for the segment is valid;

initiating a synchronize operation to copy segments from the secondary storage at the second site to the primary storage at the first site in response to determining that the first site is ready to begin receiving updates and mirror updates to the secondary storage at the second site; and

comparing the codes for segments in the secondary storage at the second site with the codes for the corresponding segments in the primary storage at the first site to determine whether to copy the data from the segments in the secondary storage at the second site to the primary storage at the first site as part of the synchronize operation.

18. The system of claim 17, wherein the operations further comprise:

restoring at least one of the segments to the primary storage at the first site from a backup device in response to detecting the availability of the first site, wherein the operations to calculate the code are initiated while segments are being restored from the backup device.

19. An article of manufacture comprising a computer readable storage medium including program instructions implemented in a first and second copy managers for synchronizing data between a primary storage at a first site and a secondary storage at a second site, wherein at least one of the first and second copy managers are executed to perform operations, the operations comprising:

copying updates to segments of storage in the primary storage at the first site to corresponding segments of the secondary storage at the second site;

providing codes generated from the segments in the secondary storage at the second site and a valid flag for at least one code indicating whether the code for the segment of data is valid;

providing codes generated from segments of the primary storage at the first site;

setting a valid flag to indicate one of the segments of data as invalid in response to receiving an update to the segment of data that results in the current code for the segment not reflecting the updated state of that segment;

generating a new code for segments in the secondary storage whose valid flag indicates that the segment is invalid;

setting the valid flag for the segment for which the new code is calculated to indicate that the code for the segment is valid;

initiating an operation to copy segments from the secondary storage at the second site to the primary storage at the first site;

determining, for segments in the secondary storage at the second site, whether the valid flag for the code for the segment in the secondary storage at the second site indicates that the code is valid in response to initiating the copy operation; and

comparing the valid code for at least one of the segments in the secondary storage at the second site with the code for the corresponding segment in the primary storage at the first site to determine whether to copy the data from the segment in the secondary storage at the second site to the primary storage at the first site as part of the copy operation.

20. The article of manufacture of claim 19, wherein the operations further comprise:

providing valid flags for codes generated from segments in the primary storage at the first site, wherein the code for at least one of the segments in the secondary storage at the second site is compared with the code for the corresponding segment in the primary storage at the first site if the valid flags for the corresponding segments in the primary and secondary storages at the first and second sites, respectively, indicate valid.

21. The article of manufacture of claim 19, wherein the operations further comprise:

generating a new code for each segment whose valid flag indicates that the segment is invalid from current data for the segment; and

comparing the new code for the segment in the secondary storage at the second site with the code for the corresponding segment in the primary storage at the first site to determine whether to copy the data from the segment in the secondary storage at the second site to the primary storage at the first site.

22. The article of manufacture of claim 19, wherein the operations further comprise:

copying data from the secondary storage at the second site to the primary storage at the first site if the codes do not match.

23. The article of manufacture of claim 22, wherein the operations further comprise

copying data from the primary storage at the first site to the secondary storage at the second site while the primary storage at the first site is receiving updates;

receiving updates at the secondary storage at the second site in response to detecting a failure at the first site, wherein updates are not received at the primary storage at the first site while updates are being received at the secondary storage at the second site; and

detecting an availability of the first site after the failure at the first site, wherein the copy operation is initiated in response to detecting the availability of the first site.

24. The article of manufacture of claim 19, wherein the received update is stored in a cache, wherein the operations further comprise:

destaging updates for one segment from the cache to the secondary storage at the second site storage, wherein the new code is calculated for one segment in response to destaging the updates for the segment.

25. The article of manufacture of claim 24, wherein the operations further comprise:

determining whether the cache includes a previous update for the block to which the received update applies; and

writing the received update to the block in cache to overwrite any previous update to the block in the cache, wherein the valid flag for the segment is only set to indicate that the code is invalid in response to determining that there is no previous update for the block in the cache.

26. The article of manufacture of claim 24, wherein the operations further comprise:

staging one segment in the secondary storage at the second site into the cache in response to receiving an update to a block in the segment, wherein updated and unchanged portions of the segment are in the cache, and wherein the new code is calculated from the entire segment stored in the cache in response to destaging the segment.

27. The article of manufacture of claim 19, wherein the received update is stored in a cache, wherein the operations further comprise:

destaging updates for one segment from the cache to the primary storage at the first site storage; and

initiating a background operation to calculate a new code for each segment whose valid flag indicates that the code is invalid.

28. An article of manufacture comprising a computer readable storage medium including program instructions implemented in a first and second copy managers for synchronizing data between a primary storage at a first site and a secondary storage at a second site, wherein at least one of the first and second copy managers are executed to perform operations, the operations comprising:

copying data segments of storage in the primary storage at the first site to corresponding segments of storage in the secondary storage at the second site;

receiving updates to the secondary storage at the second site in response to detecting a failure at the first site, wherein updates are not received at the first site while updates are being received at the in the secondary storage at the second site;

detecting an availability of the first site before the first site is ready to begin receiving updates and mirroring updates to the secondary storage at the second site;

initiating operations to calculate codes for the segments in the primary and secondary storages at the first and second sites, respectively, in response to detecting the availability of the first site;

setting a valid flag to indicate one of the segments of data as invalid in response to receiving an update to the segment of data that results in the current code for the segment not reflecting the updated state of that segment;

generating a new code for segments in the secondary storage whose valid flag indicates that the segment is invalid;

setting the valid flag for the segment for which the new code is calculated to indicate that the code for the segment is valid;

initiating a synchronize operation to copy segments from the secondary storage at the second site to the primary storage at the first site in response to determining that the first site is ready to begin receiving updates and mirror updates to the secondary storage at the second site; and

comparing the codes for segments in the secondary storage at the second site with the codes for the corresponding segments in the primary storage at the first site to determine whether to copy the data from the segments in the secondary storage at the second site to the primary storage at the first site as part of the synchronize operation.

29. The article of manufacture of claim 28, wherein the operations further comprise:

restoring at least one of the segments to the primary storage at the first site from a backup device in response to detecting the availability of the first site, wherein the operations to calculate the code are initiated while segments are being restored from the backup device.