Storage checkpointing in a mirrored virtual machine system

• US 9,983,935 B2
• Filed: 09/25/2013
• Issued: 05/29/2018
• Est. Priority Date: 05/23/2011
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Fuente, Carlos F., Mulcahy, James, Scales, William J.
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): Lu, Kevin X
• Application Number:
  US14/036,771
• Publication Number:
  US 20140025913A1
• Time in Patent Office: 1,707 Days
• CPC Class Codes: G06F 11/1435 using file system or storage system metadata
• CPC Class Codes: G06F 11/1484 involving virtual machines
• CPC Class Codes: G06F 11/2023 Failover techniques
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency ensuring consistency in mirrored systems G06F11/2064
• CPC Class Codes: G06F 9/3863 using multiple copies of the architectural state, e.g. shadow registers
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors

Abstract

A method and system are provided for storage checkpointing in a mirrored virtual machine system. The method includes a storage controller receiving a modifying operation to storage from a virtual machine and carrying out the modifying operation in a non-destructive manner by saving the modifying operation data to a checkpointing region of storage and preserving the stored previous data state. The method also includes receiving a checkpoint notification and committing modifying operation data from the checkpointing region and releasing the stored previous data state. If a failover notification is received, the storage controller rolls back the physical storage to match a checkpoint state.

Claims

1. A method for storage checkpointing in a mirrored virtual machine system, comprising a storage controller:

receiving, by the storage controller in a storage system, a modifying operation to modify data stored at a physical storage location within the storage system from a first virtual machine;

carrying out, by the storage controller, the modifying operation in a non-destructive manner by saving modifying operation data of the modifying operation to a new checkpointing region of the physical storage location that is appended to the data stored at a previous checkpointing region in the physical storage location thereby preserving a stored previous data state of the data;

receiving, by the storage controller, a start new checkpoint notification;

responsive to receiving the start new checkpoint notification, saving, by the storage controller, subsequent modifying operation data in the previous checkpointing region, wherein the start new checkpoint notification is received and completed before new modifying operations are submitted by the first virtual machine;

receiving, by the storage controller, a retire previous checkpoint notification;

copying, by the storage controller, an associated state of the new checkpointing region from the first virtual machine to the second virtual machine;

responsive to receiving the retire previous checkpoint notification, committing, by the storage controller, the modifying operation data from the new checkpointing region to the appended physical storage location and releasing the data associated with the previous checkpointing region and modified by the modifying operation data as the new checkpointing region, wherein the retire previous checkpoint notification is received only when the associated state of the new checkpointing region has been completely transferred from the first virtual machine to a second virtual machine; and

resuming, by the storage controller, the implementation of the other modify operations from the first virtual machine.

2. The method as claimed in claim 1, including:

supporting, by the storage controller, multiple checkpoints, wherein the new checkpoint notification and the retire previous checkpoint notification each include a checkpoint identifier for distinguishing from other checkpoints.

3. The method as claimed in claim 1, including:

receiving at the storage controller a query to determine which checkpoints exist at a given time.

4. The method as claimed in claim 1, including:

presenting, by the storage controller, a logical drive of the storage addressable by a client;

saving, by the storage controller, the modifying operation data of the modifying operation on the logical drive; and

maintaining, by the storage controller, a mapping of the logical drive to the physical storage in the new checkpointing region.

5. The method as claimed in claim 4, including:

receiving, by the storage controller, a failover notification; and

rolling, by the storage controller, back the physical storage to match a checkpoint state.

6. The method as claimed in claim 4, including:

receiving, by the storage controller, a failover notification with a checkpoint identifier;

rolling, by the storage controller, back the physical storage to match an identified checkpoint state;

reverting, by the storage controller, the mapping of the logical drive to the physical storage following the identified checkpoint; and

discarding, by the storage controller, the modifying operation data in the new checkpointing region.

7. The method as claimed in claim 6, wherein the checkpoint identifier associates the checkpoint identifier with a point-in-time view of the logical drive.

8. The method as claimed in claim 1, wherein carrying out the modifying operation in the non-destructive manner includes one of:

performing a copy-on-write operation or performing a redirect-on-write operation.

9. The method of claim 1, wherein, responsive to receiving the retire previous checkpoint notification and prior to committing the modifying operation data from the new checkpointing region to the appended physical storage location and releasing the data associated with the previous checkpointing region and modified by the modifying operation data as the new checkpointing region, the method further comprises:

pausing, by the storage controller, implementation of other modify operations from the first virtual machine; and

responsive to the associated state of the new checkpointing region being completely transferred from the first virtual machine to the second virtual machine, committing, by the storage controller, the modifying operation data from the new checkpointing region to the appended physical storage location and releasing the data associated with the previous checkpointing region and modified by the modifying operation data as the new checkpointing region.

10. A method for storage checkpointing in a mirrored virtual machine system, comprising a storage controller:

receiving, by the storage controller in a storage system, a modifying operation to modify data stored at a physical storage location within the storage system from a first virtual machine;

carrying out, by the storage controller, the modifying operation in a non-destructive manner by saving modifying operation data of the modifying operation to a new checkpointing region of the physical storage location that is appended to the data stored at a previous checkpointing region in the physical storage location thereby preserving a stored previous data state of the data;

receiving, by the storage controller, a start new checkpoint notification; and

responsive to receiving the start new checkpoint notification, saving, by the storage controller, subsequent modifying operation data in the previous checkpointing region, wherein the start new checkpoint notification is received and completed before new modifying operations are submitted by the first virtual machine;

receiving, by the storage controller, a retire previous checkpoint notification; and

responsive to receiving the retire previous checkpoint notification, pausing, by the storage controller, implementation of other modify operations from the first virtual machine;

copying, by the storage controller, the associated state of the new checkpointing region from the first virtual machine to a second virtual machine;

responsive to the associated state of the new checkpointing region being completely transferred from the first virtual machine to the second virtual machine, committing, by the storage controller, the modifying operation data from the new checkpointing region to the appended physical storage location and releasing the data associated with the previous checkpointing region and modified by the modifying operation data as the new checkpointing region; and

resuming, by the storage controller, the implementation of the other modify operations from the first virtual machine.