Determining differences between snapshots

• US 7,100,089 B1
• Filed: 09/06/2002
• Issued: 08/29/2006
• Est. Priority Date: 09/06/2002
• Status: Expired due to Term

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: 3pardata Incorporated
• Inventors: Phelps, Adam M.
• Primary Examiner(s): LE, DIEU MINH T
• Application Number:
  US10/237,432
• Time in Patent Office: 1,453 Days
• Field of Search: 714/42, 714 5- 9, 714 11- 13, 714/54, 714/718, 711/154, 711161-162
• US Class Current: 714/42
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 3/0607 by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
• CPC Class Codes: G06F 3/065 Replication mechanisms
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]

Abstract

A method is provided for synchronization of a backup copy of a volume of memory represented by a snapshot tree. The snapshot tree includes a plurality of snapshot volumes, each snapshot volume corresponding to a respective snapshot of the volume of memory. The method comprises the following: determining whether there are any exceptions in any of the snapshot volumes in the snapshot tree between and including the snapshot volumes corresponding to a first and a second snapshot; if there are exceptions, processing for the exceptions to synchronize the backup copy of the memory volume; otherwise, if there are no exceptions, ignoring the snapshot volumes.

Claims

1. A method for determining differences between two snapshots of a base volume in a snapshot tree comprising the base volume and a plurality of snapshot volumes, wherein each of the two snapshots corresponds to a respective snapshot volume of the snapshot tree, wherein the snapshot volumes corresponding to the two snapshots are in a same branch of the snapshot tree, the method beginning with the older and ending with the more recent of the snapshot volumes corresponding to the two snapshots, the method comprising for each snapshot volume:

searching for exceptions in exception tables of the snapshot volume presently being considered, wherein the exceptions tables only point to data that were (1) originally in the base volume at a time the snapshot volume presently being considered was taken and (2) later modified after the snapshot volume presently being considered was taken;

if exceptions are found, processing for the exceptions;

otherwise, if no exceptions are found, determining whether the snapshot volume presently being considered is the more recent of the snapshot volumes corresponding to the two snapshots; and

if the snapshot volume presently being considered is not the more recent of the snapshot volumes corresponding to the two snapshots, moving to the next snapshot volume up the branch from the snapshot volume presently being considered and treating the next snapshot volume as the snapshot presently being considered.

2. The method of claim 1, wherein the snapshot tree is structured as a plurality of branches, each branch including a read-write snapshot volume and possibly one or more read-only snapshot volumes.

3. The method of claim 1, further comprising ignoring the snapshot volume presently being considered if no exceptions are found.

4. A method for determining differences between first and second snapshots of a base volume in a snapshot tree comprising the base volume and a plurality of snapshot volumes, wherein each of the first and the second snapshots corresponds to a respective snapshot volume of the snapshot tree, wherein the first snapshot is in a first branch of the snapshot tree and the second snapshot is in a second branch of the snapshot tree, the method comprising:

searching for exceptions in exception tables of any of the snapshot volumes in the first branch from the first snapshot up to a first common parent snapshot between the first and the second snapshots in the snapshot tree, wherein the exception tables in a snapshot volume only point to data that were (1) originally in the base volume at a time the snapshot volume was taken and (2) later modified after the snapshot volume was taken;

searching for exceptions in exception tables of any of the snapshot volumes in the second branch from the second snapshot up to the first common parent snapshot;

if exceptions are found, determining if the exceptions for the snapshot volumes in the first branch are the same as the exceptions for the snapshot volumes in the second branch; and

if the exceptions are the same, ignoring the snapshot volumes;

otherwise, if the exceptions are not the same, processing for the exceptions.

5. The method of claim 4, further comprising ignoring the snapshot volumes if no exceptions are found.

6. The method of claim 4, wherein the snapshot tree is structured as a plurality of branches, each branch including a read-write snapshot volume and possibly one or more read-only snapshot volumes.

7. A method for synchronization of a backup copy of a base volume in a snapshot tree comprising the base volume and a plurality of snapshot volumes, each snapshot volume corresponding to a respective snapshot of the base volume, the method comprising:

determining whether there are any exceptions in exception tables of any of the snapshot volumes in the snapshot tree between and including the snapshot volumes corresponding to a first snapshot and a second snapshot, wherein the exceptions tables in a snapshot volume only point to data that were (1) originally in the base volume at a time the snapshot volume was taken and (2) later modified after the snapshot volume was taken;

if there are exceptions, processing for the exceptions to synchronize the backup copy of the base volume;

otherwise, if there are no exceptions, ignoring the snapshot volumes.

8. The method of claim 7, wherein said processing for the exceptions comprises generating the backup copy of the base volume with a memory state corresponding to one of the first and second snapshots.

9. The method of claim 7, wherein said processing for the exceptions comprises updating the backup copy of the base volume to a memory state corresponding to one of the first and second snapshots.

10. The method of claim 7, wherein the base volume is a virtual volume.

11. The method of claim 7, wherein said determining, beginning with an older and ending with a more recent of the snapshot volumes corresponding to the first and the second snapshots, comprises:

searching for exceptions in exception tables of the snapshot volume presently being considered;

if no exceptions are found, determining whether the snapshot volume presently being considered is the more recent of the snapshot volumes corresponding to the two snapshots; and

if the snapshot volume presently being considered is not the more recent of the snapshot volumes corresponding to the two snapshots, moving to the next snapshot volume up the tree from the snapshot volume presently being considered and treating the next snapshot volume as the snapshot presently being considered.

12. The method of claim 7, wherein said determining comprises searching for exceptions in exception tables of any of the snapshot volumes in the snapshot tree between and including the snapshot volumes corresponding to each of the first and the second snapshots up to a first common parent in the snapshot tree.

13. A system for synchronization of a backup copy of a base volume in a snapshot tree comprising the base volume and a plurality of snapshot volumes, each snapshot volume corresponding to a respective snapshot of the base volume, the system comprising an executable process for:

determining whether there are any exceptions in exception tables of any of the snapshot volumes in the snapshot tree between and including the snapshot volumes corresponding to a first and a second snapshot, wherein the exception tables in a snapshot volume only point to data that were (1) originally in the base volume at a time the snapshot volume was taken and (2) later modified after the snapshot volume was taken;

if there are exceptions, processing for the exceptions to synchronize the backup copy of the base volume;

otherwise, if there are no exceptions, ignoring the snapshot volumes.