Patent Grant
7668810
Commonly assigned U.S. Patent Application Publication No. US 2004/0260896 is incorporated for its showing of copying data from source storage to target storage, wherein the copy operations create a consistent copy of source storage data in the target storage, restricting a write operation on source storage during a copy operation.
This invention relates to copying of data from source data storage volumes to target data storage volumes, and, more particularly, the creation of consistent copies.
Copying of data is useful for backup purposes to avoid the loss of data. As discussed in the incorporated '896 USPAP, in data storage systems, such as enterprise storage servers (ESS), for example, the IBM® TotalStorage Enterprise Storage Server™, there may be copy functions, one of which, such as FlashCopy™, that provides point-in-time copy functions. As discussed in the incorporated '896 USPAP, point-in-time copying techniques provide an instantaneous copy or view of what the original data looked like at a specific point in time.
The data may be interdependent such that data of one volume is dependent on data of another volume. However, source data may be subject to updating while the point-in-time data is being copied, and an update to some data that has not yet been copied may thus conflict with interdependent data that has already been copied, and, if the data not yet copied is then copied, the data is inconsistent, and essentially corrupted. In the incorporated '896 USPAP, while performing a copy operation to copy from a source to a target, a write operation is restricted from being performed on the one source, until the copy operations have been performed on the data that is interdependent.
The group of interdependent data that is being copied may be called a consistency group. The write restriction may be called a “FREEZE”, and subsequent writes to the frozen source volume receive a “long busy” condition. When all of the consistency group relationships are established and the interdependent data is copied, a “consistency group created” command is issued to each logical subsystem, causing the “frozen” volumes to be “THAWED”.
In order to keep from an unexpected problem, or a user forgetting to issue a thaw, a timer is started by ESS when the freeze is initiated. If a volume is not thawed within a specified amount of time, it will be automatically thawed, which may lead to an uncertainty whether the group is in fact consistent.
Data storage systems, data storage controls, and computer program products control the consistency of data storage copies.
In one embodiment, a data storage system comprises data storage configured to store a plurality of source data storage volumes; data storage configured to store a plurality of target data storage volumes; and program logic configured to respond to a restriction of a write operation to at least one source data storage volume (FREEZE), to select, as a verification volume, a source data storage volume to which the restriction applies, the restriction based on a copy operation to establish a consistency group, the copy operation conducted between at least one source data storage volume and at least one target data storage volume; the program logic configured to respond to a verification request to first employ the verification volume to verify that the restriction remains in place with respect to the verification volume, and to allow a reset of the restriction (THAW).
In a further embodiment, the restriction is verified by a query to detect a “long busy” condition with respect to the verification volume.
In another embodiment, the program logic is additionally configured to allow a user to specify criteria for selection of a source data storage volume as the verification volume.
In still another embodiment, the verification volume is the initial source data storage volume of the restriction.
For a fuller understanding of the present invention, reference should be made to the following detailed description taken in conjunction with the accompanying drawings.
This invention is described in preferred embodiments in the following description with reference to the Figures, in which like numbers represent the same or similar elements. While this invention is described in terms of the best mode for achieving this invention's objectives, it will be appreciated by those skilled in the art that variations may be accomplished in view of these teachings without deviating from the spirit or scope of the invention.
Referring to
The illustrated source and target volumes may be physical volumes or may be logical volumes of data, with any desired headers, etc., arranged on various physical data storage devices, such as RAID (Redundant Array of Independent Disks) systems of logic and disk drives, as are known to those of skill in the art.
As discussed in the incorporated '896 USPAP, point-in-time copying techniques provide an instantaneous copy or view of what the original data looked like at a specific point in time. Typically, both the source and the target volumes reside on the same ESS system, although implementations may be possible where the source and target volumes reside on different ESS systems.
A point-in-time copy initially comprises dual pointers to the data on the source volumes, so that a host system write operation may be satisfied with a write complete, in that there are primary and backup means to access the physical data, creating the impression that the data is backed up. Additionally, a RAID system typically provides enough redundancy to the data that its continued availability is assured. With the satisfaction of the write operation of the host system, the physical copying of the data to the target volumes can then be accomplished on an asynchronous basis. Once the write operation is complete, the host system may then update some or all of the data of the source volumes.
The data may be interdependent such that data of one volume is dependent on data of another volume. However, source data may be subject to updating while the point-in-time data is being copied, and an update to some data that has not yet been copied may thus conflict with interdependent data that has already been copied, and, if the data not yet copied is then copied, the data is inconsistent, and essentially corrupted. In the incorporated '896 USPAP, while performing a copy operation to copy from a source to a target, a write operation is restricted from being performed on the one source, until the copy operations have been performed on the data that is interdependent. This may be called a FlashCopy “establish”.
The group of interdependent data that is being copied may be called a consistency group. The write restriction may be called a “FREEZE”, and subsequent writes to the frozen source volume(s) receive a “long busy” condition. When all of the consistency group relationships are established, a “consistency group created” command is issued to each logical subsystem. The data is copied to the target volumes, the pointers are changed, and the “frozen” volumes are “THAWED”.
In order to keep from having an unexpected problem, or in the case of a user forgetting to issue a thaw, a timer may be started by the ESS when the freeze is initiated. If a volume is not thawed in a specified amount of time, it will be automatically thawed by the microcode. It is thus difficult to know positively that the last FlashCopy establish was done prior to the time expiring for the first volume that was frozen.
Referring to
In step 25, the selection criteria may be to select the initial source data storage volume of the write restriction. The selection may comprise saving the device number of volume serial number of the selected source volume.
In step 30, the control 14 continues to establish the relationships between the source data volumes, and issues write restrictions for the consistency group. In the example, the initial source data storage volume to which a write restriction 33 (FREEZE) applies is VOL001, with its corresponding target volume TGT001. VOL002 does not comprise a part of the consistency group and may be copied to TGT002 without a write restriction. VOL003 is interdependent with respect to VOL001 and therefore may have a write restriction 34 applied, and, when the relationships are established, will be part of the consistency group of VOL001, TGT001, VOL003, and corresponding target volume TGT003. The process of step 30 will continue, to include all of the interdependent volumes, such as source volume VOL188 with a write restriction 40, and target volume TGT188 in the consistency group. The write restrictions or FREEZE, for example, comprise invoking instructions such that subsequent writes to the source receive a “long busy” condition. The long busy condition from the control 14 causes the host system to queue an intended write to the volume. At substantially the same time, data will begin to be transferred to the target volumes TGT001-TGT189, as illustrated by the arrows 45.
Once all relationships have been established for the consistency group, the host software issues a command indicating that the consistency group has been created, and that verification is required. Referring to
If the restriction is not in place, “NO” in step 53, in step 58, the control 14 will not verify the consistency group. This may comprise an error condition in which the consistency group data may have been corrupted, for example, by expiration of a timer that prematurely reset the write restriction. The write restrictions of other volumes may also have been reset. The data of the verification volume, and possibly other volumes, may or may not have been overwritten or updated. The control may then undertake measures to limit any potential corruption of the data. Control 14 then proceeds to step 56 and allows a reset of the restriction (THAW).
The described operations may be implemented as systems, apparatus, processors, program logic and/or computer program products using known programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. The control 14 comprises computer processor, logic and/or one or more microprocessors with computer readable medium 15 for storing information and program instructions for operating the microprocessor(s). Herein “processor” or “program logic” and “computer readable medium” may comprise any suitable computer processor, logic, microprocessor, and associated memory for responding to program instructions, and the associated computer readable medium may comprise fixed and/or rewritable memory or data storage devices or apparatus. The program instructions comprise computer readable program code and may be supplied to the controller or computer readable medium from a host or via a data storage drive, or by an input from a floppy or optical disk, or by being read from a cartridge, or by a web user interface or other network connection, or by any other suitable means, themselves also comprising herein “computer readable medium”.
Those of skill in the art will understand that changes may be made with respect to the flow charts of
While the preferred embodiments of the present invention have been illustrated in detail, it should be apparent that modifications and adaptations to those embodiments may occur to one skilled in the art without departing from the scope of the present invention as set forth in the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5341479 | Dean et al. | Aug 1994 | A |
| 5355477 | Strickland et al. | Oct 1994 | A |
| 5546579 | Josten et al. | Aug 1996 | A |
| 5566319 | Lenz | Oct 1996 | A |
| 5734818 | Kern et al. | Mar 1998 | A |
| 5787247 | Norin et al. | Jul 1998 | A |
| 6145006 | Vishlitsky et al. | Nov 2000 | A |
| 6247099 | Skazinski et al. | Jun 2001 | B1 |
| 6493796 | Arnon et al. | Dec 2002 | B1 |
| 6542974 | Gagne et al. | Apr 2003 | B2 |
| 6611901 | Micka et al. | Aug 2003 | B1 |
| 6622259 | Schmuck | Sep 2003 | B1 |
| 6754682 | LeCrone et al. | Jun 2004 | B1 |
| 6772309 | Ohr et al. | Aug 2004 | B1 |
| 6795850 | Wu et al. | Sep 2004 | B2 |
| 6925515 | Burns et al. | Aug 2005 | B2 |
| 7133982 | Werner et al. | Nov 2006 | B2 |
| 7188187 | Hirabayashi et al. | Mar 2007 | B2 |
| 20030028695 | Burns et al. | Feb 2003 | A1 |
| 20030236899 | Otake | Dec 2003 | A1 |
| 20040193944 | LeCrone et al. | Sep 2004 | A1 |
| 20040260726 | Hrle et al. | Dec 2004 | A1 |
| 20040260736 | Kern et al. | Dec 2004 | A1 |
| 20040260896 | Werner et al. | Dec 2004 | A1 |
| 20050071372 | Bartfai et al. | Mar 2005 | A1 |
| 20050149683 | Chong et al. | Jul 2005 | A1 |
| 20050160248 | Yamagami | Jul 2005 | A1 |
| 20050198455 | Yagawa et al. | Sep 2005 | A1 |
| 20060129556 | Reuter | Jun 2006 | A1 |
| 20060136685 | Griv et al. | Jun 2006 | A1 |
| 20070022267 | Werner et al. | Jan 2007 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 20070185928 A1 | Aug 2007 | US |
