Electrical computers and digital processing systems: memory – Storage accessing and control – Control technique
Reexamination Certificate
1998-09-03
2001-10-09
Yoo, Do Hyun (Department: 2185)
Electrical computers and digital processing systems: memory
Storage accessing and control
Control technique
C711S154000, C711S111000, C711S112000, C714S013000, C714S006130, C714S020000
Reexamination Certificate
active
06301643
ABSTRACT:
BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to a method and system for insuring that data is stored in a consistent and sequential manner.
2. Description of the Related Art
Disaster recovery systems typically address two types of failures, a sudden catastrophic failure at a single point in time or data loss over a period of time. In the second type of gradual disaster, updates to volumes may be lost. To assist in recovery of data updates, a copy of data may be provided at a remote location. Such dual or shadow copies are typically made as the application system is writing new data to a primary storage device. International Business Machines Corporation (IBM), the assignee of the subject patent application, provides two systems for maintaining remote copies of data at a secondary site, extended remote copy (XRC) and peer-to-peer remote copy (PPRC). These systems provide a method for recovering data updates between a last, safe backup and a system failure. Such data shadowing systems can also provide an additional remote copy for non-recovery purposes, such as local access at a remote site. These IBM of XRC and PPRC systems are described in IBM publication “Remote Copy: Administrator's Guide and Reference,” IBM document no. SC35-0169-02 (IBM Copyright 1994, 1996), which publication is incorporated herein by reference in its entirety.
In such backup systems, data is maintained in volume pairs. A volume pair is comprised of a volume in a primary storage device and a corresponding volume in a secondary storage device that includes an identical copy of the data maintained in the primary volume. Typically, the primary volume of the pair will be maintained in a primary direct access storage device (DASD) and the secondary volume of the pair is maintained in a secondary DASD shadowing the data on the primary DASD. A primary storage controller may be provided to control access to the primary DASD and a secondary storage controller may be provided to control access to the secondary DASD.
In the XRC environment, the application system writing data to the primary volumes includes a sysplex timer which provides a time-of-day (TOD) value as a time stamp to data writes. The application system time stamps data sets when writing such data sets to volumes in the primary DASD. The integrity of data updates is related to insuring that updates are done at the secondary volumes in the volume pair in the same order as they were done on the primary volume. In the XRC and other prior art systems, the time stamp provided by the application program determines the logical sequence of data updates. In many application programs, such as database systems, certain writes cannot occur unless a previous write occurred; otherwise the data integrity would be jeopardized. Such a data write whose integrity is dependent on the occurrence of a previous data writes is known as a dependent write. For instance, if a customer opens an account, deposits $400, and then withdraws $300, the withdrawal update to the system is dependent on the occurrence of the other writes, the opening of the account and the deposit. When such dependent transactions are copied from the primary volumes to secondary volumes, the transaction order must be maintained to maintain the integrity of the dependent write operation.
Volumes in the primary and secondary DASDs are consistent when all writes have been transferred in their logical order, i.e., all dependent writes transferred first before the writes dependent thereon. In the banking example, this means that the deposit is written to the secondary volume before the withdrawal. A consistency group is a collection of updates to the primary volumes such that dependent writes are secured in a consistent manner. For instance, in the banking example, this means that the withdrawal transaction is in the same consistency group as the deposit or in a later group; the withdrawal cannot be in an earlier consistency group. Consistency groups maintain data consistency across volumes. For instance, if a failure occurs, the deposit will be written to the secondary volume before the withdrawal. Thus, when data is recovered from the secondary volumes, the recovered data will be consistent.
A consistency time is a time the system derives from the application system's time stamp to the data set. A consistency group has a consistency time for all data writes in a consistency group having a time stamp equal or earlier than the consistency time stamp. In the IBM XRC environment, the consistency time is the latest time to which the system guarantees that updates to the secondary volumes are consistent. As long as the application program is writing data to the primary volume, the consistency time increases. However, if update activity ceases, then the consistency time does not change as there are no data sets with time stamps to provide a time reference for further consistency groups. If all the records in the consistency group are written to secondary volumes, then the reported consistency time reflects the latest time stamp of all records in the consistency group. Methods for maintaining the sequential consistency of data writes and forming consistency groups to maintain sequential consistency in the transfer of data between a primary DASD and secondary DASD are described in U.S. Pat. Nos. 5,615,329 and 5,504,861, which are, assigned to IBM, the assignee of the subject patent application, and which are incorporated herein by reference in their entirety.
Consistency groups are formed under the following assumptions:
(A) application writes that are independent can be performed in any order;
(B) application writes that are dependent must be performed in time stamp order;
(C) a second write of a first and second dependent write pair will always be either in the same record set consistency group as a first write with a later time stamp or in a subsequent record consistency group.
In prior art systems, to generate reports for the current data, the user would have to take the application system off-line and stop updating data to the primary volumes. The user could then run reports on the current volumes in the secondary DASD. To insure the consistency of the report at a specific time, the user would break the volume pair and not allow any updates or writes to the primary or secondary volume of those volumes pairs being tested. This allows the user to insure that all writes are consistent as of a specified time. However, with such a system, the primary volume cannot receive updates from the application program until the reports on the secondary volumes are completed and the secondary volumes are brought back on-line to shadow writes to the primary volumes.
SUMMARY OF THE PREFERRED EMBODIMENTS
To overcome the limitations in the prior art described above, the present invention discloses a system for maintaining consistency of data across storage devices. A cut-off time value is provided to the system. The system then obtains information on data writes to a first storage device, including information on time stamp values associated with the data writes indicating an order of the data writes to the first storage device. At least one group of data writes having time stamp values earlier in time than the cut-off time value is then formed. The system then transfers the data writes in the groups to a second storage device for storage therein.
In further embodiments, the system includes information on at least one volume pair to which the cut-off time applies. A volume pair comprises a volume in the second storage device and a corresponding volume in the first storage device. The volume in the second storage device includes a copy of data in the corresponding volume in the first storage device, wherein the groups only include data writes to the provided volume pairs.
In yet further embodiments, information is obtained and data groups are formed multiple times until the time stamp value of the data writes is determined to be at or later in time than the cut-off time value. If the
Crockett Robert Nelson
Kern Ronald Maynard
McBride Gregory Edward
International Business Machines - Corporation
Konrad Raynes & Victor LLP
McLean Kimberly
Victor David W.
Yoo Do Hyun
LandOfFree
Multi-environment data consistency does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Multi-environment data consistency, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Multi-environment data consistency will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2558991