Snapshot maintenance apparatus and method

• US 20070067585A1
• Filed: 11/21/2005
• Published: 03/22/2007
• Est. Priority Date: 09/21/2005
• Status: Abandoned Application

• Current Assignee: Hitachi, Ltd.
• Original Assignee: Hitachi, Ltd.
• Inventors: Honami, Koji, Ueda, Naoto, Fujii, Naohiro
• Application Number:
  US11/282,707
• Publication Number:
  US 20070067585A1
• Time in Patent Office: Days
• US Class Current: 711/162
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data

Abstract

Provided is a snapshot maintenance apparatus and method capable of maintaining a snapshot in a highly reliability manner. In a snapshot maintenance apparatus and method for maintaining an image at the time of creating a snapshot of an operation volume for reading and writing data from and to a host system, a difference volume and a failure-situation volume are set in a connected physical device; and difference data, which is the difference formed from the operation volume at the time of creating the snapshot and the current operation volume, is sequentially saved in the difference volume according to the writing of the data from the host system in the operation volume, and the difference data is saved in the failure-situation volume when a failure occurs in the difference volume.

Claims

1. A snapshot maintenance apparatus for maintaining an image at the time of creating a snapshot of an operation volume for reading and writing data from and to a host system, comprising:

a volume setting unit for setting a difference volume and a failure-situation volume in a connected physical device; and

a snapshot management unit for sequentially saving difference data, which is the difference formed from said operation volume at the time of creating said snapshot and the current operation volume, in said difference volume according to the writing of said data from said host system in said operation volume, and saving said difference data in said failure-situation volume when a failure occurs in said difference volume.

2. The snapshot maintenance apparatus according to claim 1, wherein said snapshot management unit creates first difference data management information formed from management information of said difference data in said difference volume and second difference data management information formed from management information of said difference data in said failure-situation volume, and migrates said difference data saved in said failure-situation volume to said difference volume while maintaining the consistency of said first and second difference data management information.

3. The snapshot maintenance apparatus according to claim 2, wherein said snapshot management unit determines whether the failure of said difference volume is recoverable or irrecoverable based on the mean time to repair relating to the failure of said difference volume, and sets a new difference volume and migrates said difference data saved in said failure-situation volume to said new difference volume when it is determined that the failure of the difference volume is irrecoverable.

4. The snapshot maintenance apparatus according to claim 2, wherein said snapshot management unit manages a plurality of generations of said snapshots based on said first and second difference data management information.

5. The snapshot maintenance apparatus according to claim 2, wherein first and second difference data management information includes bit information for managing the saving status of said difference data per prescribed block configuring said operation volume, and

wherein said snapshot management unit copies the corresponding region of said second difference data management information to the corresponding position of said first difference data management information before migrating said difference data saved in said failure-situation volume to said original difference volume or said new difference volume.

6. The snapshot maintenance apparatus according to claim 2, wherein said snapshot management unit stores said bit information of said snapshot at the time a failure occurs in said difference volume, and determines whether the failure of said original difference volume has recovered or said new difference volume has been created based on said first difference data management information of said original difference volume or said new difference volume upon migrating said difference data saved in said failure-situation volume to said original difference volume or said new difference volume.

7. The snapshot maintenance apparatus according to claim 1, wherein said snapshot management unit stores the status of said difference volume relating to the failure status, and saves said difference data in one of the corresponding said difference volume or said failure-situation volume based on the status of said stored difference volume.

8. The snapshot maintenance apparatus according to claim 1, wherein said failure-situation volume is set in a storage area provided by a physical device having higher reliability than said difference volume.

10. The snapshot maintenance method according to claim 2, wherein at said second step, first difference data management information formed from management information of said difference data in said difference volume and second difference data management information formed from management information of said difference data in said failure-situation volume is created, and said difference data saved in said failure-situation volume is migrated to said original difference volume or said new difference volume while maintaining the consistency of said first and second difference data management information after the failure of said original difference volume has recovered or said new difference volume is set.

11. The snapshot maintenance method according to claim 10, wherein at said second step, whether the failure of said difference volume is recoverable or irrecoverable is determined based on the mean time to repair relating to the failure of said difference volume, said new difference volume when it is determined that the failure of the difference volume is irrecoverable, and said difference data saved in said failure-situation volume is migrated to said new difference volume.

12. The snapshot maintenance method according to claim 10, wherein at said second step, a plurality of generations of said snapshots are managed based on said first and second difference data management information.

13. The snapshot maintenance method according to claim 10, wherein said first and second difference data management information includes bit information for managing the saving status of said difference data per prescribed block configuring said operation volume, and, at said second step, the corresponding region of said second difference data management information is copied to the corresponding position of said first difference data management information before migrating said difference data saved in said failure-situation volume to said original difference volume or said new difference volume.

14. The snapshot maintenance method according to claim 10, wherein at said second step, said bit information of said snapshot is stored at the time a failure occurs in said difference volume, and whether the failure of said original difference volume has recovered or said new difference volume has been created is determined based on said first difference data management information of said original difference volume or said new difference volume upon migrating said difference data saved in said failure-situation volume to said original difference volume or said new difference volume.

9. A snapshot maintenance method for maintaining an image at the time of creating a snapshot of an operation volume for reading and writing data from and to a host system, comprising:

a first step of setting a difference volume and a failure-situation volume in a connected physical device; and

a second step of sequentially saving difference data, which is the difference formed from said operation volume at the time of creating said snapshot and the current operation volume, in said difference volume according to the writing of said data from said host system in said operation volume, and saving said difference data in said failure-situation volume when a failure occurs in said difference volume.

15. The snapshot maintenance method according to claim 9, wherein at said second step, the status of said difference volume relating to the failure status is stored, and said difference data is saved in one of the corresponding said difference volume or said failure-situation volume based on the status of said stored difference volume.

16. The snapshot maintenance method according to claim 9, wherein said failure-situation volume is set in a storage area provided by a physical device having higher reliability than said difference volume.