AUTOMATIC FAILOVER AND FAILBACK BETWEEN PRIMARY AND SECONDARY STORAGE SYSTEMS

• US 20160179637A1
• Filed: 12/18/2014
• Published: 06/23/2016
• Est. Priority Date: 12/18/2014
• Status: Active Grant

• Current Assignee: Infinidat Ltd.
• Original Assignee: Infinidat Ltd.
• Inventors: Winokur, Alex
• Granted Patent: US 9,703,649 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/2005 using redundant communication controllers
• CPC Class Codes: G06F 11/2064 while ensuring consistency
• CPC Class Codes: G06F 11/2069 Management of state, configuration or failover
• CPC Class Codes: G06F 11/2071 using a plurality of controllers
• CPC Class Codes: G06F 13/4221 being an input/output bus, e.g. ISA bus, EISA bus, PCI bus, SCSI bus
• CPC Class Codes: G06F 2201/85 Active fault masking without idle spares

Abstract

A method for managing a secondary storage system, the method may include performing a failover update, by the secondary storage system, of a status of at least one secondary path that couples a host computer to the secondary storage system thereby causing the host computer to prioritize sending IO requests to the secondary storage system over sending the IO requests to a primary storage system; wherein the failover update is triggered by a determination made by the secondary storage system that (a) the secondary storage system is, when making the determination, at an acceptable synchronization level with the primary storage system, and (b) the primary storage system is disconnected from the host computer; receiving, from the host computer, IO requests; and responding, by the secondary storage system, to the IO requests.

Claims

1. A method for managing a secondary storage system, the method comprises:

performing a failover update, by the secondary storage system, of a status of at least one secondary path that couples a host computer to the secondary storage system thereby causing the host computer to prioritize sending input output (IO) requests to the secondary storage system over sending the IO requests to a primary storage system;

wherein the failover update is triggered by a determination made by the secondary storage system that (a) the secondary storage system is, when making the determination, at an acceptable synchronization level with the primary storage system, and (b) the primary storage system is disconnected from the host computer;

receiving, from the host computer, IO requests; and

responding, by the secondary storage system, to the IO requests.

2. The method according to claim 1 wherein the failover update is performed autonomously and without human intervention.

3. The method according to claim 1 further comprising performing the determination that (a) the secondary storage system is, when making the determination, at the acceptable synchronization level with the primary storage system, and (b) the primary storage system is disconnected from the host computer.

4. The method according to claim 3 wherein the determining that the primary storage system is disconnected from the host computer is based upon a reception, before performing of the failover update, of an initial IO request from the host computer, wherein the initial IO request is expected to reach the secondary storage system when the primary storage system is disconnected from the host computer.

5. The method according to claim 1 wherein the updating of the status of the at least one secondary path comprises indicating that the at least one secondary path is active and of a higher priority than a priority of at least one primary path that couples the host computer to the primary storage system.

6. The method according to claim 1 further comprising preventing, from the host computer, to send the IO requests to the secondary storage system when determining that the secondary storage system did not maintain the acceptable synchronization level with the primary storage system when the primary storage system disconnected from the secondary storage system.

7. The method according to claim 6 wherein the preventing comprising flagging the at least one secondary path as being inactive.

8. The method according to claim 1 further comprising performing a failback update, by the secondary storage system, of the status of the at least one secondary path thereby causing the host computer to prioritize sending new IO requests to the primary storage system over sending the new IO requests to the secondary storage system;

wherein the performing of the failback update is triggered by a determination made by the secondary storage system that the primary storage system is connected to the secondary storage system and that the primary storage system is capable of responding to the new IO requests.

9. The method according to claim 8 wherein the performing of the failback update comprises informing the host computer about a prioritization of the at least one primary path over the at least one secondary path after the primary storage system completed a failback change in the status of the at least one primary path.

18. The non-transitory computer readable medium according to claim 7 that stores instructions for performing of the failback update by informing the host computer about a prioritization of the at least one primary path over the at least one secondary path after the primary storage system completed a failback change in the status of the at least one primary path.

10. A non-transitory computer readable medium that stores instructions that once executed by a secondary storage system causes the secondary storage system to:

perform a failover update of a status of at least one secondary path that couples a host computer to the secondary storage system thereby causing the host computer to prioritize sending IO requests to the secondary storage system over sending the TO requests to a primary storage system;

wherein the failover update is triggered by a determination made by the secondary storage system that (a) the secondary storage system is, when making the determination, at an acceptable synchronization level with the primary storage system, and (b) the primary storage system is disconnected from the host computer;

receive, from the host computer, IO requests; and

respond, by the secondary storage system, to the IO requests.

11. The non-transitory computer readable medium according to claim 10 wherein the failover update is performed autonomously and without human intervention.

12. The non-transitory computer readable medium according to claim 10 that stores instructions for performing the determination that (a) the secondary storage system is, when making the determination, at an acceptable synchronization level with the primary storage system, and (b) the primary storage system is disconnected from the host computer.

13. The non-transitory computer readable medium according to claim 12 that stores instructions for determining that the primary storage system is disconnected from the host computer based upon a reception, before performing of the failover update, of an initial TO request from the host computer, wherein the initial IO request is expected to reach the secondary storage system when the primary storage system is disconnected from the host computer.

14. The non-transitory computer readable medium according to claim 10 that stores instructions for updating of the status of the at least one secondary path by indicating that the at least one secondary path is active and of a higher priority than a priority of at least one primary path that couples the host computer to the primary storage system.

15. The non-transitory computer readable medium according to claim 10 that stores instructions for preventing from the host computer to send the IO requests to the secondary storage system when determining that the secondary storage system did not maintain the acceptable synchronization level with the primary storage system when the primary storage system disconnected from the secondary storage system.

16. The non-transitory computer readable medium according to claim 15 that stores instructions for preventing from the host computer to send the IO requests to the secondary storage system by flagging the at least one secondary path as being inactive.

17. The non-transitory computer readable medium according to claim 10 that stores instructions for performing a failback update of the status of the at least one secondary path thereby causing the host computer to prioritize sending new IO requests to the primary storage system over sending the new IO requests to the secondary storage system;

wherein the performing of the failback update is triggered by a determination made by the secondary storage system that the primary storage system is connected to the secondary storage system and that the primary storage system is capable of responding to the new IO requests.

19. A storage system that comprises a controller and an interface;

wherein the controller is configured to perform a failover update of a status of at least one secondary path that couples a host computer to the secondary storage system thereby causing the host computer to prioritize sending IO requests to the secondary storage system over sending the IO requests to a primary storage system;

wherein the failover update is triggered by a determination made by the secondary storage system that (a) the secondary storage system is, when making the determination, at an acceptable synchronization level with the primary storage system, and (b) the primary storage system is disconnected from the host computer;

wherein the interface is arranged to receive, from the host computer, IO requests; and

wherein the storage system is configured to respond to the IO requests.