Resynchronization of a target volume with a source volume

Data processing: database and file management or data structures – Database design – Data structure types

Reexamination Certificate

Rate now

  [ 0.00 ] – not rated yet Voters 0   Comments 0

Details

C707S793000, C707S793000

Reexamination Certificate

active

06668264

ABSTRACT:

BACKGROUND OF THE INVENTION
1. Field of Invention
This invention relates to data storage systems. In particular, the invention relates to synchronization of source and target volumes in a mirrored storage system.
2. Related Art
Snapshots and multiple volumes are frequently used to prevent data loss when a data storage drive fails in a file system. Such snapshots “capture” the contents of the files and directories in a volume at a particular point in time in order to recover earlier versions of a file following an unintended deletion or modification. Such snapshots can also be copied to one or more volumes, which then can be used as a mirror or a collection or mirrors and which can provide a back-up copy of the file system. When used in this way, the mirror can be referred to as a target volume. In general, a target volume is a “read-only” volume that contains a set of data that is equivalent to the set of data on an original source volume. Such target volumes can be written to only by the original source volume.
A target volume may be updated periodically with respect to a source volume by looking to the most recent snapshot that the target and source have in common and using that snapshot as a consistency point (CP). The file blocks in the most recent common snapshot and the file blocks of a new snapshot are compared. The set of differences resulting from this comparison are written to the less up-to-date volume. In this way, both source and target volumes maintain equivalent sets of file blocks.
A source volume may become unavailable due to a failure of the source volume or to a failed connection to the source volume. Under such conditions, it is advantageous to temporarily use the target volume as a source volume by designating it as a “read/write” volume. User I/Os are directed to write to the target volume while the original source volume is unavailable.
One problem with writing to a target volume is that it may cause the target volume to contain data not found in the original source volume. A partial solution to this problem involves transferring data from the target to the source once the source is restored. However this is undesirable because it requires diversion of computational resources and filer overhead.
Accordingly, it would be advantageous to provide an improved technique for quickly and efficiently updating source and target volumes after a target volume has been written to. This is achieved in an embodiment of the invention that addresses the foregoing deficiencies.
SUMMARY OF THE INVENTION
The invention provides an improved method and apparatus for quickly and efficiently updating an original source volume and an original target volume after the original target volume has been used as a source volume in a file system. One or more snapshots are used to compare data included in the source and target volume. Instead of transferring the entire volume, only the data that is missing from a source and a target volume is transferred.
In a first aspect of the invention, a target volume becomes synchronized with a source volume after the target has been written to by an entity other than the source. Synchronization is a two phase process. In the first phase, a target volume provides the source volume with a list of snapshots and associated snapshot numbers used to determine the sequence of the snapshots on the list. The source volume compares its own list of snapshot numbers with the list of the target volume's snapshot numbers and determines the newest common snapshot. This newest common snapshot is a consistency point between the target volume and the source volume. The source volume sends the target volume a set of snapshot numbers describing the newest common snapshot and the target volume reverts back to this snapshot. In the second phase, file system software identifies all the data blocks contained in any one or more of the snapshots of the source volume. This file system software also identifies all the data blocks in any one or more of the snapshots of the target volume using the data sent by the target volume to the source volume as described supra. A set of data blocks that are included in the source volume and not included in the target volume is generated. This can be accomplished by making a comparison based on logical differences, generating a virtual or actual list or other techniques known in the art.
File system software synchronizes the target volume with the source volume. First, the file system software removes snapshots from a target volume if the snapshots are not included in the source volume's snapshot list. Second, the file system software adds the set of data blocks identified above (that is the set of data blocks that are included in the source volume and not included in the target volume) to its memory. Lastly, the file system software adds snapshots to the target volume if the snapshots are included in the source volume's snapshot list and not in the target volume's snapshot list. At this point, the target volume includes the data blocks that are present on the source volume.
In a second aspect of the invention, the roles of the target volume and source volume are reversed and the process described supra is performed again so as to synchronize source volume with the target volume. This is necessary because the target volume may include data blocks not included in the source volume. After both source and target volumes are synchronized, the target volume stops being written to and the source once again is used as the active file. This is accomplished by 1) designating the target as a read-only volume, 2) designating the source as a read/write volume, and 3) redirecting users'I/O's back to the source volume.
In a preferred embodiment, sources and volumes can be synchronized dynamically, using a WAFL (Write Anywhere File Layout) system using RAID (Redundant Arrays of Independent Disks) architecture. However, various other types of file systems involving redundant copies of data can also be used.


REFERENCES:
patent: 4742450 (1988-05-01), Duvall et al.
patent: 4751635 (1988-06-01), Kret
patent: 4875159 (1989-10-01), Cary et al.
patent: 4887204 (1989-12-01), Johnson et al.
patent: 4897781 (1990-01-01), Chang et al.
patent: 5008786 (1991-04-01), Thatte
patent: 5043876 (1991-08-01), Terry
patent: 5208813 (1993-05-01), Stallmo
patent: 5222217 (1993-06-01), Blount et al.
patent: 5276840 (1994-01-01), Yu
patent: 5305326 (1994-04-01), Solomon et al.
patent: 5313626 (1994-05-01), Jones et al.
patent: 5313646 (1994-05-01), Hendricks et al.
patent: 5357509 (1994-10-01), Ohizumi
patent: 5454095 (1995-09-01), Kraemer et al.
patent: 5504883 (1996-04-01), Coverston et al.
patent: 5604862 (1997-02-01), Midgely et al.
patent: 5633999 (1997-05-01), Clowes et al.
patent: 5649152 (1997-07-01), Ohran et al.
patent: 5649196 (1997-07-01), Woodhill et al.
patent: 5668943 (1997-09-01), Attanasio et al.
patent: 5721916 (1998-02-01), Pardikar
patent: 5819292 (1998-10-01), Hitz et al.
patent: 5819310 (1998-10-01), Vishlitzky et al.
patent: 5835953 (1998-11-01), Ohran
patent: 5907672 (1999-05-01), Matze et al.
patent: 5996086 (1999-11-01), Delaney et al.
patent: 6000039 (1999-12-01), Tanaka et al.
patent: 6119244 (2000-09-01), Schoenthal et al.
patent: 6131088 (2000-10-01), Hill
patent: 6377951 (2002-04-01), Campbell
patent: 0 497 067 (1992-08-01), None
patent: WO 00/07104 (2000-02-01), None
Gertrude G. Reusser and Donald C. Loughry, “Hewlett-Packard and the Open Systems Interconnection Reference Model”, Hewlett-Packard Journal, Oct. 1986, vol. 37, No. 10.
Bruce Nelson and Yu-Ping-Cheng, “The Myth of Transfer Rate”, How and Why SCSI Is better than IPI for NFS, Technical Report 6, Second Edition, Jul. 1992, Auspex.

LandOfFree

Say what you really think

Search LandOfFree.com for the USA inventors and patents. Rate them and share your experience with other people.

Rating

Resynchronization of a target volume with a source volume does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Resynchronization of a target volume with a source volume, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Resynchronization of a target volume with a source volume will most certainly appreciate the feedback.

Rate now

     

Profile ID: LFUS-PAI-O-3181549

  Search
All data on this website is collected from public sources. Our data reflects the most accurate information available at the time of publication.