Systems and methods for a disaster recovery system utilizing virtual machines running on at least two host computers in physically different locations

• US 20060085792A1
• Filed: 10/15/2004
• Published: 04/20/2006
• Est. Priority Date: 10/15/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Traut, Eric P.
• Granted Patent: US 7,840,963 B2
• Time in Patent Office: Days
• US Class Current: 718/100
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06F 11/2025 using centralised failover control functionality
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups

Abstract

The present invention is directed to systems and methods for providing disaster recovery services using virtual machines. The invention provides an inexpensive and minimally intrusive way to provide disaster recovery services including recovery of the state of computer processors and devices. The system includes a production host and a backup host that communicate via a communications link. The state of the processor and devices on the production host are periodically stored onto backup host and can be restored in the event of an emergency. Additionally, the invention includes two business methods for utilizing the system and methods for providing disaster recovery services.

Claims

1. A method for minimizing interruptions to a software service during a disaster event, said method comprising:

executing said software service on a first virtual machine;

storing a set of state information corresponding to said first virtual machine for utilization by a second virtual machine when said first virtual machine becomes unavailable due to said disaster event; and

executing said software service on said second virtual machine when said first virtual machine becomes unavailable due to said disaster event.

2. The method of claim 1, wherein said element of executing said software service on said second virtual machine when said first virtual machine becomes unavailable due to said disaster event occurs, further comprising said second virtual machine detecting that said first virtual machine becomes unavailable.

3. The method of claim 1 wherein said first virtual machine executes on a first hardware and said second virtual machine executes on a second set of hardware.

4. The method of claim 1 further comprising, when said first virtual machine becomes available again after said disaster event:

storing a set of state information corresponding to said second virtual machine for utilization by said first virtual machine; and

executing said software service on said first virtual machine.

5. The method of claim 4, wherein said element of executing said software service on said second virtual machine when said first virtual machine becomes unavailable due to said disaster event occurs, further comprising said second virtual machine detecting that said first virtual machine has become unavailable.

6. A system for minimizing interruptions to a software service during a disaster event, said system comprising at least one subsystem for:

executing said software service on a first virtual machine;

storing a set of state information corresponding to said first virtual machine for utilization by a second virtual machine when said first virtual machine becomes unavailable due to said disaster event; and

executing said software service on said second virtual machine when said first virtual machine becomes unavailable due to said disaster event.

7. The system of claim 6, wherein said element of executing said software service on said second virtual machine when said first virtual machine becomes unavailable due to said disaster event occurs, further comprising at least one subsystem for said second virtual machine detecting that said first virtual machine becomes unavailable.

8. The system of claim 6 further comprising at least one subsystem whereby said first virtual machine executes on a first hardware and said second virtual machine executes on a second set of hardware.

9. The system of claim 6 further comprising at least one subsystem for, when said first virtual machine becomes available again after said disaster event:

storing a set of state information corresponding to said second virtual machine for utilization by said first virtual machine; and

executing said software service on said first virtual machine.

10. The system of claim 9, wherein said element of executing said software service on said second virtual machine when said first virtual machine becomes unavailable due to said disaster event occurs, further comprising at least one subsystem for said second virtual machine detecting that said first virtual machine has become unavailable.

11. A computer-readable medium comprising computer-readable instructions for minimizing interruptions to a software service during a disaster event, said computer-readable instructions comprising instructions for:

executing said software service on a first virtual machine;

storing a set of state information corresponding to said first virtual machine for utilization by a second virtual machine when said first virtual machine becomes unavailable due to said disaster event; and

executing said software service on said second virtual machine when said first virtual machine becomes unavailable due to said disaster event.

12. The computer-readable instructions of claim 11, wherein said element of executing said software service on said second virtual machine when said first virtual machine becomes unavailable due to said disaster event occurs, further comprising computer-readable instructions for said second virtual machine detecting that said first virtual machine becomes unavailable.

13. The computer-readable instructions of claim 11 further comprising instructions whereby said first virtual machine executes on a first hardware and said second virtual machine executes on a second set of hardware.

14. The computer-readable instructions of claim 11 further comprising computer-readable instructions for, when said first virtual machine becomes available again after said disaster event:

storing a set of state information corresponding to said second virtual machine for utilization by said first virtual machine; and

executing said software service on said first virtual machine.

15. The computer-readable instructions of claim 14, wherein said element of executing said software service on said second virtual machine when said first virtual machine becomes unavailable due to said disaster event occurs, further comprising computer-readable instructions for said second virtual machine detecting that said first virtual machine has become unavailable.

16. A hardware control device for minimizing interruptions to a software service during a disaster event, said device comprising means for:

executing said software service on a first virtual machine;

storing a set of state information corresponding to said first virtual machine for utilization by a second virtual machine when said first virtual machine becomes unavailable due to said disaster event; and

executing said software service on said second virtual machine when said first virtual machine becomes unavailable due to said disaster event.

17. The hardware control device of claim 16, wherein said element of executing said software service on said second virtual machine when said first virtual machine becomes unavailable due to said disaster event occurs, further comprising means for said second virtual machine detecting that said first virtual machine becomes unavailable.

18. The hardware control device of claim 16 further comprising means whereby said first virtual machine executes on a first hardware and said second virtual machine executes on a second set of hardware.

19. The hardware control device of claim 16 further comprising means for, when said first virtual machine becomes available again after said disaster event:

storing a set of state information corresponding to said second virtual machine for utilization by said first virtual machine; and

executing said software service on said first virtual machine.

20. The hardware control device of claim 19, wherein said element of executing said software service on said second virtual machine when said first virtual machine becomes unavailable due to said disaster event occurs, further comprising means for said second virtual machine detecting that said first virtual machine has become unavailable.

21. A method for disaster recovery, said method comprising using virtual machines to minimize interruptions to a software service during a disaster event.

22. The method of claim 21 wherein said method is performed by a service provider for the benefit of a client, said client providing a compensation to said service provider for performing said method.

23. The method of claim 22 wherein said compensation is based on at least one compensation basis from among the following plurality of compensation bases:

bandwidth usage across a communications medium;

a number of bits sent across said communications medium;

a number of snapshots submitted from a production host to a backup host; and

a number of restores performed.

24. A system for disaster recovery, said system comprising a subsystem for utilizing at least two virtual machines to minimize interruptions to a software service during a disaster event.

25. The system of claim 24 wherein said system further comprises at least one subsystem for a service provider to receive from a client a compensation for performing said method.

26. The system of claim 25 wherein said system further comprises at least one subsystem whereby said compensation is based on at least one compensation basis from among the following plurality of compensation bases:

bandwidth usage across a communications medium;

a number of bits sent across said communications medium;

a number of snapshots submitted from a production host to a backup host; and

a number of restores performed.

27. A computer-readable medium comprising computer-readable instructions for disaster recovery using virtual machines to minimize interruptions to a software service during a disaster event.

28. The computer-readable medium of claim 27 further comprising instructions whereby said client provides a compensation to said service provider for performing said method.

29. The computer-readable medium of claim 28 further comprising instructions whereby said compensation is based on at least one compensation basis from among the following plurality of compensation bases:

bandwidth usage across a communications medium;

a number of bits sent across said communications medium;

a number of snapshots submitted from a production host to a backup host; and

a number of restores performed.