# US 2013/0297966 A1 · Svc cluster configuration node failover

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0297966 A1
- Document ID: US20130297966A1
- Status: Published application
- Kind: A1
- Application number: 13/925,087
- Filed: 2013-06-24
- Published: 2013-11-07
- Earliest claimed: 2009-09-30
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Hao HE; Ling SUN; Jun Wei ZHANG
- Web page: https://patentgrep.com/patent/US20130297966A1

## CPC

- G06F 11/2007: {using redundant communication media}
- G06F 11/2017: {where memory access, memory control or I/O control functionality is redundant (redundant communication control functionality G06F11/2005; redundant storage control functionality G06F11/2089)}
- G06F 11/2028: {eliminating a faulty processor or activating a spare}
- G06F 11/2089: {Redundant storage control functionality}
- G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)}
- H04L 41/0668: by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 67/1001: for accessing one among a plurality of replicated servers
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- G06F 11/2038: {with a single idle spare processing component}
- G06F 11/2046: {where the redundant components share persistent storage (G06F11/2043 takes precedence)}
- G06F 2201/85: Active fault masking without idle spares
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods, systems, and computer programs are provided for failover responses to configuration node failures in SVC clusters. An SVC cluster manages a plurality of storage devices and includes a plurality of SVCs interconnected via a network, each SVC acting as a separate node. A storage device event log is saved, with an original configuration node. An entry is made in the storage device event log each time the original configuration node receives storage device events and setting the entry to a negative value indicating a storage device event has not been handled. The entry is set to a positive value indicating the storage device event has been handled after the original configuration node notifies respective subscribed clients about those of the storage device events the original configuration node receives. A new configuration node is activated in response to configuration node failures.

## Claims

### Claim 1

A failover method for responding to configuration node failures in a SAN Volume Controller (SVC) cluster, wherein the SVC cluster manages a plurality of storage devices and comprises a plurality of SVCs interconnected via the internet, each SVC acting as a separate node, and at any given time, only one node within the SVC cluster functions as a configuration node to operate external services, the method comprising:
setting an entry to a positive value indicating a storage device event has been handled after an original configuration node notifies respective subscribed clients about storage device events the original configuration node receives.

### Claim 2 (depends on 1)

The method according to claim 1, further including performing one of:
making the entry in the storage device event log each time the original configuration node receives storage device events and setting the entry to a negative value indicating a storage device event has not been handled,
saving, with the original configuration node, the storage device event log,
activating a new configuration node in response to failures of the original configuration node, wherein any entries in the storage device event log contains at least the following information: an event code; an event description; and an indication as to whether the event has been handled.

### Claim 3 (depends on 1)

The method according to claim 1, performing the following:
obtaining client subscription information related to the storage device events managed by the SVC cluster from the plurality of storage devices with the new configuration node, wherein the plurality of storage devices are not in the original configuration node,
retrieving the storage device events from a storage device event monitoring unit with the new configuration node in response to the storage device events occurring in the plurality of storage devices managed by the SVC cluster, and
sending storage device events to subscribed clients with the new configuration node based on the obtained client subscription information.

### Claim 4 (depends on 3)

The method according to claim 3, wherein the storage device event monitoring unit is in a node other than the original configuration node of the SVC cluster.

### Claim 5 (depends on 1)

The method according to claim 1, further comprising:
with the new configuration node, searching for entries that are set to a negative value indicating the storage device event has not been handled in the storage device event log after activation,
searching for subscribed clients who have subscribed to events corresponding to all the records based on the obtained client subscription information, and
sending the corresponding events to clients who have subscribed to these events.

### Claim 6 (depends on 4)

The method according to claim 4, wherein any of the entries in the storage device event log further includes a time of event occurrence.

### Claim 7 (depends on 6)

The method according to claim 6, further comprising:
with the original configuration node, making an entry in the storage device event log each time the original configuration node receives a storage device event and recording the time at which the storage device event occurs for the time of event occurrence.

### Claim 8 (depends on 7)

The method according to claim 7, further comprising:
recording the time at which a failure of the original configuration node occurs in response to the failure of the original configuration node,
recording successful activation of the new configuration node in response to a successful activation of the new configuration node,
determining which events in the storage device event log occurred between the failure time of the original configuration node and the successful activation time of the new configuration node based on the failure time of the original configuration node and the successful activation time of the new configuration node,
searching for subscribed clients for the events that occurred between the failure time of the original configuration node and the successful activation time of the new configuration node based on the obtained client subscription information stored in one of the plurality of storage devices, and
sending the corresponding events to the subscribed clients for the events that occurred between the failure time of the original configuration node and the successful activation time of the new configuration node.

### Claim 9

A failover system for responding to configuration node failures in a SAN Volume Controller (SVC) cluster, the SVC cluster managing a plurality of storage devices and comprising a plurality of SVCs interconnected via the internet, each SVC acting as a separate node, and at any given time, only one node within the SVC cluster functioning as a configuration node to operate external services, the system comprising:
a storage device sets an entry to a positive value indicating a storage device event has been handled after an original configuration node notifies respective subscribed clients about storage device events the original configuration node receives.

### Claim 10 (depends on 9)

The failover system according to claim 9, further including at least one of:
the storage device makes the entry in the storage device event log each time the original configuration node receives storage device events and setting the entry to a negative value indicating a storage device event has not been handled,
the storage device to save, with the original configuration node, the storage device event log, and
an activation unit to activate a new configuration node in response to node failures of the original configuration node, wherein any entries in the storage device event log contains at least the following information: an event code; an event description; and an indication as to whether the event has been handled.

### Claim 11 (depends on 9)

The failover system according to claim 9, further including:
a storage device to store client subscription information regarding the storage device events managed by the SVC cluster, and the storage device is not in the original configuration node,
a storage device event monitoring unit to monitor the plurality of storage devices managed by the SVC cluster,
a first retrieval unit to enable the new configuration node to retrieve the client subscription information from the plurality of storage devices,
a second retrieval unit to enable the new configuration node to retrieve a storage device event from the storage device event monitoring unit, and
a submission device to enable the new configuration node to send the storage device event to subscribed clients based on the client subscription information.

### Claim 12 (depends on 11)

The failover system according to claim 11, wherein the storage device event monitoring unit is in a node other than the original configuration node of the SVC cluster.

### Claim 13 (depends on 9)

The failover system according to claim 9, wherein following the activation of the new configuration node, the new configuration node searches for all the entries that are set to a negative value indicating the storage device event has not been handled, searches for the subscribed clients who have subscribed to events corresponding to the entries that are set to a negative value indicating the storage device event has not been handled based on the client subscription information, and sends the corresponding events to the respective subscribed clients.

### Claim 14 (depends on 9)

The failover system according to claim 9, wherein any of the entries in the storage device event log contains a time of event occurrence.

### Claim 15 (depends on 14)

The failover system according to claim 14, wherein the storage device event monitoring unit of the original configuration node makes an entry in the event log every time the storage device event monitoring unit receives a storage device event and records the time at which the event occurred for the time of event occurrence.

### Claim 16 (depends on 15)

The failover system according to claim 15, wherein:
when the activation unit monitors a failure of the original configuration node, the activation unit records the time at which the failure of the original configuration node occurs,
the new configuration node records the successful activation time of the new configuration node following successful activation of the new configuration node, and
the new configuration node determines which events in the storage device event log occurred between the failure time of the original configuration node and the successful activation time of the new configuration node based on the failure time of the original configuration node and the successful activation time of the new configuration node and searches for subscribed clients for the events that occurred between the failure time of the original configuration node and the successful activation time of the new configuration node based on the subscription information stored in the storage device and the corresponding events to the subscribed clients for the events that occurred between the failure time of the original configuration node and the successful activation time of the new configuration node.

### Claim 17

A computer program product for responding to configuration node failures in a SAN Volume Controller (SVC) cluster, the computer program product comprising a non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:
a first executable portion that sets an entry to a positive value indicating a storage device event has been handled after an original configuration node notifies respective subscribed clients about storage device events the original configuration node receives.

### Claim 18 (depends on 17)

The computer program product according to claim 17, further including a second executable portion that performs one of:
makes the entry in the storage device event log each time the original configuration node receives storage device events and setting the entry to a negative value indicating a storage device event has not been handled,
saves, with the original configuration node, the storage device event log, and
activates a new configuration node in response to failures of the original configuration node, wherein any entries in the storage device event log contains at least the following information: an event code; an event description; and an indication as to whether the event has been handled.

### Claim 19 (depends on 17)

The computer program product according to claim 17, further comprising a second executable portion that performs the following:
obtaining client subscription information related to the storage device events managed by the SVC cluster from the plurality of storage devices with the new configuration node, wherein the plurality of storage devices are not in the original configuration node,
retrieving the storage device events from a storage device event monitoring unit with the new configuration node in response to the storage device events occurring in the plurality of storage devices managed by the SVC cluster, and
sending storage device events to subscribed clients with the new configuration node based on the obtained client subscription information.

### Claim 20 (depends on 19)

The computer program product according to claim 19, wherein the storage device event monitoring unit is in a node other than the original configuration node of the SVC cluster.

### Claim 21 (depends on 17)

The computer program product according to claim 17, further comprising a second executable portion that performs the following:
with the new configuration node, searching for entries that are set to a negative value indicating the storage device event has not been handled in the storage device event log after activation,
searching for subscribed clients who have subscribed to events corresponding to all the records based on the obtained client subscription information, and
sending the corresponding events to clients who have subscribed to these events.

### Claim 22 (depends on 20)

The computer program product according to claim 20, wherein any of the entries in the storage device event log further includes a time of event occurrence.

### Claim 23 (depends on 22)

The computer program product according to claim 22, further comprising a second executable portion that, with the original configuration node, makes an entry in the storage device event log each time the original configuration node receives a storage device event and recording the time at which the storage device event occurs for the time of event occurrence.

### Claim 24 (depends on 23)

The computer program product according to claim 23, further comprising a third executable portion that performs the following:
recording the time at which a failure of the original configuration node occurs in response to the failure of the original configuration node,
recording successful activation of the new configuration node in response to a successful activation of the new configuration node,
determining which events in the storage device event log occurred between the failure time of the original configuration node and the successful activation time of the new configuration node based on the failure time of the original configuration node and the successful activation time of the new configuration node,
searching for subscribed clients for the events that occurred between the failure time of the original configuration node and the successful activation time of the new configuration node based on the obtained client subscription information stored in one of the plurality of storage devices, and
sending the corresponding events to the subscribed clients for the events that occurred between the failure time of the original configuration node and the successful activation time of the new configuration node.
