WO2017075375A1 - Method, device and medium for performing switchover operations between computing nodes - Google Patents

Method, device and medium for performing switchover operations between computing nodes Download PDF

Info

Publication number
WO2017075375A1
WO2017075375A1 PCT/US2016/059358 US2016059358W WO2017075375A1 WO 2017075375 A1 WO2017075375 A1 WO 2017075375A1 US 2016059358 W US2016059358 W US 2016059358W WO 2017075375 A1 WO2017075375 A1 WO 2017075375A1
Authority
WO
WIPO (PCT)
Prior art keywords
computing node
cloud
computing
node
operational state
Prior art date
Application number
PCT/US2016/059358
Other languages
English (en)
French (fr)
Inventor
Sriram Gudalore VANGHEEPURAM
Vijay Kumar Chakravarthy EKKALADEVI
Original Assignee
Netapp, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Netapp, Inc. filed Critical Netapp, Inc.
Priority to CN201680062470.8A priority Critical patent/CN108351824B/zh
Priority to EP16791273.2A priority patent/EP3368985B1/en
Priority to JP2018521645A priority patent/JP6476350B2/ja
Publication of WO2017075375A1 publication Critical patent/WO2017075375A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0727—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a storage system, e.g. in a DASD or network based storage system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0751—Error or fault detection not based on redundancy
    • G06F11/0754—Error or fault detection not based on redundancy by exceeding limits
    • G06F11/0757—Error or fault detection not based on redundancy by exceeding limits by exceeding a time limit, i.e. time-out, e.g. watchdogs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/2053—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where persistent mass storage functionality or persistent mass storage control functionality is redundant
    • G06F11/2089—Redundant storage control functionality
    • G06F11/2092—Techniques of failing over between control units
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/815—Virtual

Definitions

  • a network storage provider may utilize a cloud computing environment (e.g., a third party cloud provider) to host computing nodes that provide such services.
  • a network storage provider may deploy a first computing node, into the cloud computing environment, for providing storage services to a finance department of a company.
  • the storage provider may deploy a second computing node, into the cloud computing environment, for providing storage services to an engineer department of the company.
  • the storage provider may configure the first computing node and the second computing node as disaster recovery partners, such that a surviving computing node may takeover resources of a failed computing node in order to provide clients with failover access to services previously provided by the failed computing node (e.g., upon detecting that the first computing node has failed, the second computing node may take over storage of the first computing node in order to provide failover storage services to the finance department such as access to data previously accessible through the first computing node).
  • the first computing node and the second computing node may establish an internode communication link, such as internet protocol (IP) communication, for sharing operational state information (e.g., a heartbeat and/or a notification that a computing node is operational, rebooting, failed, is in a kernel panic mode, etc.).
  • IP internet protocol
  • a computing node may be unable to determine whether a partner computing node has failed or whether the internode communication link is down such as due to an IP network failure within the cloud computing environment. Thus, if the computing node incorrectly assumes that the partner computing node has failed, then the computing node may erroneously attempt to takeover for the partner computing node that is still operational.
  • a failure of the partner computing node is the cause of the communication loss (e.g., the failed partner computing node is unable to transmit heartbeat information due to the failure)
  • the computing node incorrectly assumes that the communication loss is due to the internode communication link being down, then clients may loss access to the storage service provided by the failed partner computing node because the computing node may not takeover for the failed partner computing node.
  • the first computing node and the second computing node are configured to share operational state information through storage managed by respective computing nodes, then a computing node may be unable to detect whether a partner computing node has failed in the event the computing node losses access to the storage of the partner computing node, such as due to a cloud computing environment infrastructure failure.
  • Fig. 1 is a component block diagram illustrating an example clustered network in accordance with one or more of the provisions set forth herein.
  • FIG. 2 is a component block diagram illustrating an example data storage system in accordance with one or more of the provisions set forth herein.
  • Fig. 3A is a component block diagram illustrating a cloud computing environment.
  • Fig. 3B is a component block diagram illustrating a cloud computing environment, where a first computing node erroneously performs a switchover operation.
  • FIG. 4A is a component block diagram illustrating an exemplary computing device for determining whether to perform a switchover operation between computing nodes utilizing a cloud environment node state provider.
  • Fig. 4B is a component block diagram illustrating an exemplary computing device for determining whether to perform a switchover operation between computing nodes utilizing a cloud environment node state provider, where a switchover operation is not performed.
  • Fig. 4C is a component block diagram illustrating an exemplary computing device for determining whether to perform a switchover operation between computing nodes utilizing a cloud environment node state provider, where a switchover operation is performed.
  • FIG. 5A is a component block diagram illustrating an exemplary computing device for determining whether to perform a switchover operation between computing nodes utilizing a cloud storage service.
  • Fig. 5B is a component block diagram illustrating an exemplary computing device for determining whether to perform a switchover operation between computing nodes utilizing a cloud storage service, where a switchover operation is not performed.
  • Fig. 5C is a component block diagram illustrating an exemplary computing device for determining whether to perform a switchover operation between computing nodes utilizing a cloud storage service, where a switchover operation is performed.
  • Fig. 6 is a flow chart illustrating an exemplary method of determining whether to perform a switchover operation between computing nodes utilizing a cloud environment node state provider.
  • Fig. 7 is a flow chart illustrating an exemplary method of determining whether to perform a switchover operation between computing nodes utilizing a cloud storage service.
  • FIG. 8 is an example of a computer readable medium in accordance with one or more of the provisions set forth herein.
  • One or more techniques and/or computing devices for determining whether to perform a switchover operation between computing nodes are provided. For example, a first computing node and a second computing node may be deployed into a computing environment (e.g., a cluster network storage computing
  • the first computing node and the second computing node may share operational state information over an internode communication link (e.g., an IP network) and/or through storage managed by partner computing nodes (e.g., the first computing node may store operational health information within storage owned by the first computing node and accessible for reading by the second computing node).
  • an internode communication link e.g., an IP network
  • partner computing nodes e.g., the first computing node may store operational health information within storage owned by the first computing node and accessible for reading by the second computing node.
  • the operational state information indicates that a computing node has failed (e.g., a loss of a heartbeat)
  • the surviving computing node may perform a switchover operation to provide clients with failover access to resources previously accessible to the clients through the failed computing node. Because the internode communication link may go down and/or a cloud computing environment infrastructure failure may result in computing nodes being unable to access operational state information within storage owned by partner computing nodes, a computing node may erroneously perform a switchover operation for a partner computing node that has not actually failed.
  • the first computing node and the second computing node may be configured to share operational state information through a cloud environment node state provider (e.g., the cloud environment node state provider may monitor operational states of computing nodes within the cloud computing environment) and/or cloud persistent storage that is accessible through a cloud storage service (e.g., a computing node may store operational state information through cloud persistent storage that is highly available to the partner computing node).
  • a cloud environment node state provider e.g., the cloud environment node state provider may monitor operational states of computing nodes within the cloud computing environment
  • cloud persistent storage e.g., a computing node may store operational state information through cloud persistent storage that is highly available to the partner computing node.
  • a computing node may reliably determine whether a partner computing node has failed (e.g., a loss of a heartbeat due to a failure of the partner computing node) or not (e.g., a loss of a heartbeat due to the internode communication link being down and/or an infrastructure failure such as a cloud computing environment infrastructure failure), which may mitigate erroneous switchover.
  • a partner computing node e.g., a loss of a heartbeat due to a failure of the partner computing node
  • an infrastructure failure such as a cloud computing environment infrastructure failure
  • FIG. 1 illustrates an embodiment of a clustered network environment 100 or a network storage environment. It may be appreciated, however, that the techniques, etc. described herein may be implemented within the clustered network environment 100, a non-cluster network environment, and/or a variety of other computing environments, such as a desktop computing environment. That is, the instant disclosure, including the scope of the appended claims, is not meant to be limited to the examples provided herein. It will be appreciated that where the same or similar components, elements, features, items, modules, etc. are illustrated in later figures but were previously discussed with regard to prior figures, that a similar (e.g., redundant) discussion of the same may be omitted when describing the subsequent figures (e.g., for purposes of simplicity and ease of understanding).
  • Fig. 1 is a block diagram illustrating an example clustered network environment 100 that may implement at least some embodiments of the techniques and/or systems described herein.
  • the example environment 100 comprises data storage systems or storage sites 102 and 104 that are coupled over a cluster fabric 106, such as a computing network embodied as a private Infiniband, Fibre Channel (FC), or Ethernet network facilitating communication between the storage systems 102 and 104 (and one or more modules, component, etc. therein, such as, nodes 116 and 118, for example).
  • a cluster fabric 106 such as a computing network embodied as a private Infiniband, Fibre Channel (FC), or Ethernet network facilitating communication between the storage systems 102 and 104 (and one or more modules, component, etc. therein, such as, nodes 116 and 118, for example).
  • FC Fibre Channel
  • Ethernet network facilitating communication between the storage systems 102 and 104 (and one or more modules, component, etc. therein, such as, nodes 116 and 118,
  • nodes 116, 118 comprise storage controllers (e.g., node 116 may comprise a primary or local storage controller and node 118 may comprise a secondary or remote storage controller) that provide client devices, such as host devices 108, 110, with access to data stored within data storage devices 128, 130.
  • client devices such as host devices 108, 110
  • clustered networks are not limited to any particular geographic areas and can be clustered locally and/or remotely.
  • a clustered network can be distributed over a plurality of storage systems and/or nodes located in a plurality of geographic locations; while in another embodiment a clustered network can include data storage systems (e.g., 102, 104) residing in a same geographic location (e.g., in a single onsite rack of data storage devices).
  • one or more host devices 108, 110 which may comprise, for example, client devices, personal computers (PCs), computing devices used for storage (e.g., storage servers), and other computers or peripheral devices (e.g., printers), are coupled to the respective data storage systems 102, 104 by storage network connections 112, 114.
  • Network connection may comprise a local area network (LAN) or wide area network (WAN), for example, that utilizes Network Attached Storage (NAS) protocols, such as a Common Internet File System (CIFS) protocol or a Network File System (NFS) protocol to exchange data packets.
  • CIFS Common Internet File System
  • NFS Network File System
  • the host devices 108, 110 may be general-purpose computers running applications, and may interact with the data storage systems 102, 104 using a client/server model for exchange of information. That is, the host device may request data from the data storage system (e.g., data on a storage device managed by a network storage control configured to process I/O commands issued by the host device for the storage device), and the data storage system may return results of the request to the host device via one or more network connections 112, 114.
  • the data storage system e.g., data on a storage device managed by a network storage control configured to process I/O commands issued by the host device for the storage device
  • the data storage system may return results of the request to the host device via one or more network connections 112, 114.
  • the nodes 116, 118 on clustered data storage systems 102, 104 can comprise network or host nodes that are interconnected as a cluster to provide data storage and management services, such as to an enterprise having remote locations, cloud storage (e.g., a storage endpoint may be stored within a data cloud), etc., for example.
  • a node in a data storage and management network cluster environment 100 can be a device attached to the network as a connection point, redistribution point or communication endpoint, for example.
  • a node may be capable of sending, receiving, and/or forwarding information over a network communications channel, and could comprise any device that meets any or all of these criteria.
  • One example of a node may be a data storage and management server attached to a network, where the server can comprise a general purpose computer or a computing device particularly configured to operate as a server in a data storage and management system.
  • a first cluster of nodes such as the nodes 116, 118 (e.g., a first set of storage controllers configured to provide access to a first storage aggregate comprising a first logical grouping of one or more storage devices) may be located on a first storage site.
  • a second cluster of nodes may be located at a second storage site (e.g., a second set of storage controllers configured to provide access to a second storage aggregate comprising a second logical grouping of one or more storage devices).
  • the first cluster of nodes and the second cluster of nodes may be configured according to a disaster recovery configuration where a surviving cluster of nodes provides switchover access to storage devices of a disaster cluster of nodes in the event a disaster occurs at a disaster storage site comprising the disaster cluster of nodes (e.g., the first cluster of nodes provides client devices with switchover data access to storage devices of the second storage aggregate in the event a disaster occurs at the second storage site).
  • nodes 116, 118 can comprise various functional components that coordinate to provide distributed storage architecture for the cluster.
  • the nodes can comprise a network module 120, 122 and a data module 124, 126.
  • Network modules 120, 122 can be configured to allow the nodes 116, 118 (e.g., network storage controllers) to connect with host devices 108, 110 over the network connections 112, 114, for example, allowing the host devices 108, 110 to access data stored in the distributed storage system.
  • the network modules 120, 122 can provide connections with one or more other components through the cluster fabric 106. For example, in Fig. 1, a first network module 120 of first node 116 can access a second data storage device 130 by sending a request through a second data module 126 of a second node 118.
  • Data modules 124, 126 can be configured to connect one or more data storage devices 128, 130, such as disks or arrays of disks, flash memory, or some other form of data storage, to the nodes 116, 118.
  • the nodes 116, 118 can be interconnected by the cluster fabric 106, for example, allowing respective nodes in the cluster to access data on data storage devices 128, 130 connected to different nodes in the cluster.
  • data modules 124, 126 communicate with the data storage devices 128, 130 according to a storage area network (SAN) protocol, such as Small
  • SCSI Computer System Interface
  • FCP Fiber Channel Protocol
  • example embodiment 100 illustrates an equal number of network and data modules
  • other embodiments may comprise a differing number of these modules.
  • there may be a plurality of network and data modules interconnected in a cluster that does not have a one-to- one correspondence between the network and data modules. That is, different nodes can have a different number of network and data modules, and the same node can have a different number of network modules than data modules.
  • a host device 108, 110 can be networked with the nodes 116, 118 in the cluster, over the networking connections 112, 114.
  • respective host devices 108, 110 that are networked to a cluster may request services (e.g., exchanging of information in the form of data packets) of a node 116, 118 in the cluster, and the node 116, 118 can return results of the requested services to the host devices 108, 110.
  • the host devices 108, 110 can exchange information with the network modules 120, 122 residing in the nodes (e.g., network hosts) 116, 118 in the data storage systems 102, 104.
  • the data storage devices 128, 130 comprise volumes 132, which is an implementation of storage of information onto disk drives or disk arrays or other storage (e.g., flash) as a file-system for data, for example.
  • Volumes can span a portion of a disk, a collection of disks, or portions of disks, for example, and typically define an overall logical arrangement of file storage on disk space in the storage system.
  • a volume can comprise stored data as one or more files that reside in a hierarchical directory structure within the volume.
  • Volumes are typically configured in formats that may be associated with particular storage systems, and respective volume formats typically comprise features that provide functionality to the volumes, such as providing an ability for volumes to form clusters. For example, where a first storage system may utilize a first format for their volumes, a second storage system may utilize a second format for their volumes.
  • the host devices 108, 110 can utilize the data storage systems 102, 104 to store and retrieve data from the volumes 132.
  • the host device 108 can send data packets to the network module 120 in the node 116 within data storage system 102.
  • the node 116 can forward the data to the data storage device 128 using the data module 124, where the data storage device 128 comprises volume 132A.
  • the host device can access the storage volume 132A, to store and/or retrieve data, using the data storage system 102 connected by the network connection 112.
  • the host device 110 can exchange data with the network module 122 in the host 118 within the data storage system 104 (e.g., which may be remote from the data storage system 102).
  • the host 118 can forward the data to the data storage device 130 using the data module 126, thereby accessing volume 132B associated with the data storage device 130.
  • determining whether to perform a switchover operation between computing nodes may be implemented within the clustered network environment 100 (e.g., nodes within a cloud computing environment and/or nodes outside the cloud computing environment but with communicative access to the cloud computing environment).
  • the node 116 e.g., a first computing node
  • the node 118 e.g., a second computing node
  • the node 116 may be hosted within the cloud computing environment and the node 118 may be hosted outside the cloud computing environment, where the node 118 has communicative access to the cloud computing environment (e.g., access to cloud persistent storage accessible through a cloud storage service).
  • the node 116 and the node 118 may be hosted outside the cloud computing environment but may have communicative access to the cloud computing environment (e.g., access to the cloud persistent storage accessible through the cloud storage service).
  • a cloud environment node state provider and/or the cloud persistent storage accessible through the cloud storage service may be used by the node 116 and the node 118 to reliably share operational state information.
  • a computing node may reliably determine whether a partner computing node has failed, and thus a switchover operation should be performed (e.g., as opposed to erroneously performing a switchover in response to a communication link failure or an infrastructure issue otherwise hindering
  • determining whether to perform a switchover operation between computing nodes may be implemented for and/or between any type of computing environment, and may be transferrable between physical devices (e.g., node 116, node 118, etc.) and/or the cloud computing environment (e.g., associated with or remote to the clustered network environment 100).
  • physical devices e.g., node 116, node 118, etc.
  • the cloud computing environment e.g., associated with or remote to the clustered network environment 100.
  • Fig. 2 is an illustrative example of a data storage system 200 (e.g., 102, 104 in Fig. 1), providing further detail of an embodiment of components that may implement one or more of the techniques and/or systems described herein.
  • the example data storage system 200 comprises a node 202 (e.g., host nodes 116, 118 in Fig. 1), and a data storage device 234 (e.g., data storage devices 128, 130 in Fig. 1).
  • the node 202 may be a general purpose computer, for example, or some other computing device particularly configured to operate as a storage server.
  • a host device 205 e.g., 108, 110 in Fig.
  • the node 202 can be connected to the node 202 over a network 216, for example, to provides access to files and/or other data stored on the data storage device 234.
  • the node 202 comprises a storage controller that provides client devices, such as the host device 205, with access to data stored within data storage device 234.
  • the data storage device 234 can comprise mass storage devices, such as disks 224, 226, 228 of a disk array 218, 220, 222. It will be appreciated that the techniques and systems, described herein, are not limited by the example
  • disks 224, 226, 228 may comprise any type of mass storage devices, including but not limited to magnetic disk drives, flash memory, and any other similar media adapted to store information, including, for example, data (D) and/or parity (P) information.
  • D data
  • P parity
  • the node 202 comprises one or more processors 204, a memory 206, a network adapter 210, a cluster access adapter 212, and a storage adapter 214 interconnected by a system bus 242.
  • the storage system 200 also includes an operating system 208 installed in the memory 206 of the node 202 that can, for example, implement a Redundant Array of Independent (or Inexpensive) Disks (RAID) optimization technique to optimize a reconstruction process of data of a failed disk in an array.
  • RAID Redundant Array of Independent
  • the operating system 208 can also manage communications for the data storage system, and communications between other data storage systems that may be in a clustered network, such as attached to a cluster fabric 215 (e.g., 106 in Fig. 1).
  • the node 202 such as a network storage controller, can respond to host device requests to manage data on the data storage device 234 (e.g., or additional clustered devices) in accordance with these host device requests.
  • the operating system 208 can often establish one or more file systems on the data storage system 200, where a file system can include software code and data structures that implement a persistent hierarchical namespace of files and directories, for example.
  • the operating system 208 is informed where, in an existing directory tree, new files associated with the new data storage device are to be stored. This is often referred to as "mounting" a file system.
  • memory 206 can include storage locations that are addressable by the processors 204 and adapters 210, 212, 214 for storing related software application code and data structures.
  • the processors 204 and adapters 210, 212, 214 may, for example, include processing elements and/or logic circuitry configured to execute the software code and manipulate the data structures.
  • the operating system 208 portions of which are typically resident in the memory 206 and executed by the processing elements, functionally organizes the storage system by, among other things, invoking storage operations in support of a file service implemented by the storage system.
  • the network adapter 210 includes the mechanical, electrical and signaling circuitry needed to connect the data storage system 200 to a host device 205 over a computer network 216, which may comprise, among other things, a point-to-point connection or a shared medium, such as a local area network.
  • the host device 205 e.g., 108, 110 of Fig. 1
  • the host device 205 may be a general-purpose computer configured to execute applications. As described above, the host device 205 may interact with the data storage system 200 in accordance with a client/host model of information delivery.
  • the storage adapter 214 cooperates with the operating system 208 executing on the node 202 to access information requested by the host device 205 (e.g., access data on a storage device managed by a network storage controller).
  • the information may be stored on any type of attached array of writeable media such as magnetic disk drives, flash memory, and/or any other similar media adapted to store information.
  • the information can be stored in data blocks on the disks 224, 226, 228.
  • the storage adapter 214 can include input/output (I/O) interface circuitry that couples to the disks over an I/O interconnect arrangement, such as a storage area network (SAN) protocol (e.g., Small Computer System Interface (SCSI), iSCSI, hyperSCSI, Fiber Channel Protocol (FCP)).
  • SAN storage area network
  • SCSI Small Computer System Interface
  • iSCSI iSCSI
  • hyperSCSI HyperSCSI
  • FCP Fiber Channel Protocol
  • the information is retrieved by the storage adapter 214 and, if necessary, processed by the one or more processors 204 (or the storage adapter 214 itself) prior to being forwarded over the system bus 242 to the network adapter 210 (and/or the cluster access adapter 212 if sending to another node in the cluster) where the information is formatted into a data packet and returned to the host device 205 over the network connection 216 (and/or returned to another node attached to the cluster over the cluster fabric 215).
  • storage of information on arrays 218, 220, 222 can be implemented as one or more storage "volumes" 230, 232 that are comprised of a cluster of disks 224, 226, 228 defining an overall logical arrangement of disk space.
  • the disks 224, 226, 228 that comprise one or more volumes are typically organized as one or more groups of RAIDs.
  • volume 230 comprises an aggregate of disk arrays 218 and 220, which comprise the cluster of disks 224 and 226.
  • the operating system 208 may implement a file system (e.g., write anywhere file system) that logically organizes the information as a hierarchical structure of directories and files on the disks.
  • file system e.g., write anywhere file system
  • respective files may be implemented as a set of disk blocks configured to store information
  • directories may be implemented as specially formatted files in which information about other files and directories are stored.
  • data can be stored as files within physical and/or virtual volumes, which can be associated with respective volume identifiers, such as file system identifiers (FSIDs), which can be 32-bits in length in one example.
  • FSIDs file system identifiers
  • a physical volume corresponds to at least a portion of physical storage devices whose address, addressable space, location, etc. doesn't change, such as at least some of one or more data storage devices 234 (e.g., a Redundant Array of Independent (or Inexpensive) Disks (RAID system)).
  • data storage devices 234 e.g., a Redundant Array of Independent (or Inexpensive) Disks (RAID system)
  • RAID system Redundant Array of Independent (or Inexpensive) Disks
  • the location of the physical volume doesn't change in that the (range of) address(es) used to access it generally remains constant.
  • a virtual volume in contrast, is stored over an aggregate of disparate portions of different physical storage devices.
  • the virtual volume may be a collection of different available portions of different physical storage device locations, such as some available space from each of the disks 224, 226, and/or 228. It will be appreciated that since a virtual volume is not "tied" to any one particular storage device, a virtual volume can be said to include a layer of abstraction or virtualization, which allows it to be resized and/or flexible in some regards.
  • a virtual volume can include one or more logical unit numbers (LUNs) 238, directories 236, Qtrees 235, and files 240.
  • LUNs logical unit numbers
  • directories 236, Qtrees 235, and files 240 allow the disparate memory locations within which data is stored to be identified, for example, and grouped as data storage unit.
  • the LUNs 238 may be characterized as constituting a virtual disk or drive upon which data within the virtual volume is stored within the aggregate.
  • LUNs are often referred to as virtual drives, such that they emulate a hard drive from a general purpose computer, while they actually comprise data blocks stored in various parts of a volume.
  • one or more data storage devices 234 can have one or more physical ports, wherein each physical port can be assigned a target address (e.g., SCSI target address).
  • a target address on the data storage device can be used to identify one or more LUNs 238.
  • respective target addresses can identify multiple LUNs, such that a target address can represent multiple volumes.
  • the I/O interface which can be implemented as circuitry and/or software in the storage adapter 214 or as executable code residing in memory 206 and executed by the processors 204, for example, can connect to volume 230 by using one or more addresses that identify the LUNs 238.
  • determining whether to perform a switchover operation between computing nodes may be implemented for the data storage system 200.
  • the node 202 e.g., a first computing nodes
  • a second node e.g., a second computing node
  • the node 202 and a second node may be hosted within a cloud computing
  • the node 202 may be hosted within the cloud computing environment and the second node may be hosted outside the cloud computing environment, where the second node has communicative access to the cloud computing environment (e.g., access to the cloud persistent storage accessible through the cloud storage service).
  • the node 202 and the second node may be hosted outside the cloud computing environment but may have communicative access to the cloud computing environment (e.g., access to cloud persistent storage accessible through a cloud storage service).
  • a cloud environment node state provider and/or the cloud persistent storage accessible through the cloud storage service may be used by the node 202 and the second node to reliably share operational state information.
  • a computing node may reliably determine whether a partner computing node has failed, and thus a switchover operation should be performed (e.g., as opposed to erroneously performing a switchover in response to a communication link failure or an infrastructure issue otherwise hindering communication of operational state information). It may be appreciated that determining whether to perform a switchover operation between computing nodes may be implemented for and/or between any type of computing environment, and may be transferrable between physical devices (e.g., node 202, host 205, etc.) and/or the cloud computing environment (e.g., comprising the node 202 and/or the host 205).
  • physical devices e.g., node 202, host 205, etc.
  • the cloud computing environment e.g., comprising the node 202 and/or the host 205.
  • Figs. 3A-3B illustrate a cloud computing environment 300.
  • Fig. 3A illustrates a plurality of computing nodes, such as a first computing node 304 and a second computing node 306, being hosted within the cloud computing environment 300.
  • the first computing node 304 and/or the second computing node 306 may be hosted within a non-cloud computing environment, but may have communicative access to the cloud computing environment 300 (e.g., access to cloud persistent storage accessible through a cloud storage service).
  • the computing nodes may provide resources and/or storage to clients over a network 302.
  • a shopping business provider may deploy computing nodes within the cloud computing environment 300 for hosting a shopping service
  • a videogame business provider may deploy computing nodes within the cloud computing environment 300 for hosting videogame services
  • a network storage provider may deploy the first computing node 304 to host storage services for a marketing department of a company client using a first set of resources 312 and a first storage device 310
  • the network storage provider may deploy the second computing node 306 to host storage services for an engineering department of the company client using a second set of resources 316 and a second storage device 314.
  • various service providers may utilize the cloud computing environment 300, hosted by a third party cloud provider, to provide services to clients over the network 302.
  • the network storage provider may configure the first computing node 304 and the second computing node 306 as disaster recovery partners, such that if a computing node fails, then the surviving computing node will perform a switchover operation to obtain ownership of resources and/or storage devices, previously owned by the failed computing node, in order to provide clients with failover access to services previously provided by the failed computing node using the switched over resources and storage devices.
  • the first computing node 304 and the second computing node 306 may be configured to share operational state information (e.g., a heartbeat and/or an indication as to whether a computing node is operational, failed, rebooting, is in a kernel panic mode, has a relatively high latency and is unable to keep up with client demands, etc.) over an intemode communication link 308.
  • operational state information e.g., a heartbeat and/or an indication as to whether a computing node is operational, failed, rebooting, is in a kernel panic mode, has a relatively high latency and is unable to keep up with client demands, etc.
  • the intemode communication link 308 may comprise an IP network where the first computing node 304 may send first operational state information to the second computing node 306 using an IP address assigned to the second computing node 306.
  • the first computing node 304 may be configured to store the first operational state information within the first storage device 310 owned by the first computing node 304.
  • the second computing node 306 may utilize a first cloud infrastructure connection 320 to read the first operational state information from the first storage device 310.
  • the second computing node 306 may be configured to store second operational state information within the second storage device 314 owned by the second computing node 306.
  • the first computing node 306 may utilize a second cloud infrastructure connection 318 to read the second operational state information from the second storage device 314.
  • the first computing node 304 and the second computing node 306 may utilize the intemode communication link 308 and/or cloud infrastructure connections for sharing operational state information used to determine whether a switchover operation should be performed.
  • Fig. 3B illustrates the first computing node 304 detecting a heartbeat loss 330 of operational state information from the second computing node 306.
  • a heartbeat loss 330 of operational state information from the second computing node 306.
  • an IP network failure may result in the internode communication link 308 being down, and thus the first computing node 304 may incorrectly determine that the heartbeat loss 330 is a result of the second computing node 306 failing as opposed to the internode communication link 308 being down.
  • a cloud infrastructure failure may result in the second cloud infrastructure connection 318 being down, and thus the first computing node 304 may incorrectly determine that the heartbeat loss 330 is a result of the second computing node 306 failing as opposed to an inability to access operational state information, of the second computing node 306, within the second storage device 314 due to the cloud infrastructure failure.
  • the first computing node 304 may erroneously implement a switchover operation 332 to take over ownership of the second storage device 314 and/or the second set of resources 316 for providing clients with failover access to storage services previously provided by the second computing node 306 utilizing the second storage device 314 and/or the second set of resources 316.
  • the first computing node 304 and the second computing node 306 may undesirably contend for ownership of the second storage device 314 and/or the second set of resources 316 because the second computing node 306 is operational and the first computing node 304 is erroneously attempting to perform the switchover operation 332.
  • FIGs. 4A-4C illustrate examples of determining whether to perform a switchover operation between computing nodes.
  • a first computing node 404 and a second computing node 406 may be hosted within a cloud computing environment 400. It may be appreciated that in an example, the first computing node 404 and/or the second computing node 406 may be hosted within a non-cloud computing environment, but may have communicative access to the cloud computing
  • the first computing node 404 may be hosted within a first cloud level zone and the second computing node 406 may be hosted within a second cloud level zone (e.g., hosted within different zones or locations of a data center, within different data centers, etc.).
  • the first computing node 404 may provide clients, over a network 402, with access to a first set of storage resources 412 within the cloud computing environment 400 (e.g., storage resources associated with a first storage device 410 owned by the first computing node 404).
  • the second computing node 406 may provide clients, over the network 402, with access to a second set of storage resources 416 within the cloud computing environment 400 (e.g., storage resources associated with a second storage device 414 owned by the second computing node 406).
  • An internode communication link 408 may be established between the first computing node 404 and the second computing node 406.
  • the internode communication link 408 may comprise IP based communication, such as an IP network (e.g., as opposed to a direct link, such as a physical link, between the computing nodes, which may be impractical because the computing nodes may be within different cloud level zones, such as within different data centers or locations within a data center).
  • the first computing node 404 and the second computing node 406 may be configured to transmit operational state information (e.g., a heartbeat, an indication of a failure, an indication of normal operation, etc.) over the internode communication link 408.
  • operational state information e.g., a heartbeat, an indication of a failure, an indication of normal operation, etc.
  • the first computing node 404 may be configured to store first operational state information within the first storage device 410 so that the second computing node 406 may read the first operational state information from the first storage device 410 over a first cloud infrastructure connection 420.
  • the second computing node 406 may be configured to store second operational state information within the second storage device 414 so that the first computing node 404 may read the second operational state information from the second storage device 414 over a second cloud infrastructure connection 418.
  • a cloud environment node state provider 430 may be utilized to verify operational states of computing node.
  • the first computing node 404 and the second computing node 406 may be configured to provide operational state information to the cloud environment node state provider 430 of the cloud computing environment 40.
  • the cloud environment node state provider 430 may be a service provided by a cloud provider/owner of the cloud computing environment 400, and thus may provide highly available and reliable information regarding whether computing nodes are operational or not.
  • FIG. 4B illustrates the first computing node 404 detecting a loss 440 of communication over the internode communication link 408 (e.g., a timeout since a last receipt of operation state information from the second computing node 406 over the internode communication link 408) and/or of access to the second storage device 414 (e.g., an inability to access the second storage device 414 over the second cloud infrastructure connection 418) while the second computing node 406 is operational. Responsive to identifying the loss 440, the first computing node 404 may query the cloud environment node state provider 430 for operational state information of the second computing node 406.
  • a loss 440 of communication over the internode communication link 408 e.g., a timeout since a last receipt of operation state information from the second computing node 406 over the internode communication link 408
  • the second storage device 414 e.g., an inability to access the second storage device 414 over the second cloud infrastructure connection 41
  • the cloud environment state provider 430 may respond with an operational state message 442 regarding the second computing node 406 being in the operational state. Accordingly, the first computing node 404 may refrain from erroneously performing a switchover operation because the second computing node 406 is operational for providing clients with access to the second set of resources 416. Thus, the first computing node 404 may determine that the loss 440 corresponds to a cloud computing environment infrastructure failure and/or inoperability of the internode communication link 408.
  • Fig. 4C illustrates the first computing node 404 detecting a loss 451 of communication over the internode communication link 408 (e.g., a timeout since a last receipt of operation state information from the second computing node 406 over the internode communication link 408) and/or of access to the second storage device 414 (e.g., an inability to access the second storage device 414 over the second cloud infrastructure connection 418) while the second computing node 406 is in a failed state 450. Responsive to detecting the loss 451, the first computing node 404 may query the cloud environment node state provider 430 for operational state information of the second computing node 406.
  • a loss 451 of communication over the internode communication link 408 e.g., a timeout since a last receipt of operation state information from the second computing node 406 over the internode communication link 408
  • the second storage device 414 e.g., an inability to access the second storage device 414 over the second cloud infrastructure connection 41
  • the cloud environment state provider 430 may respond with a failed state message 452 regarding the second computing node 406. Accordingly, the first computing node 404 may perform a switchover operation 454 to take over ownership of the second storage device 414 and/or the second set of resources 416 for providing clients with failover access to storage services previously provided by the second computing node 406 utilizing the second storage device 414 and/or the second set of resources 416.
  • the first computing node 404 may also query a cloud storage service, hosting cloud persistent storage into which computing nodes may store operational information, to determine the operational state of the second computing node 406 (e.g., Figs. 5A-5C).
  • a cloud storage service hosting cloud persistent storage into which computing nodes may store operational information, to determine the operational state of the second computing node 406 (e.g., Figs. 5A-5C).
  • FIGs. 5A-5C illustrate examples of determining whether to perform a switchover operation between computing nodes.
  • a first computing node 504 and a second computing node 506 may be hosted within a cloud computing environment 500. It may be appreciated that in an example, the first computing node 504 and/or the second computing node 506 may be hosted within a non-cloud computing environment, but may have communicative access to the cloud computing
  • the first computing node 504 may be hosted within a first cloud level zone and the second computing node 506 may be hosted within a second cloud level zone.
  • the first computing node 504 may provide clients, over a network 502, with access to a first set of storage resources 512 within the cloud computing environment 500 (e.g., storage resources associated with a first storage device 510 owned by the first computing node 504).
  • the second computing node 506 may provide clients, over the network 502, with access to a second set of storage resources 516 within the cloud computing environment 500 (e.g., storage resources associated with a second storage device 514 owned by the second computing node 506).
  • An internode communication link 508 may be established between the first computing node 504 and the second computing node 506.
  • the internode communication link 508 may comprise IP based communication, such as an IP network.
  • the first computing node 504 and the second computing node 506 may be configured to transmit operational state information (e.g., a heartbeat corresponding to a sequence of numbers indicative of progress of a computing node, an indication of a failure, an indication of normal operation, etc.) over the internode communication link 508.
  • operational state information e.g., a heartbeat corresponding to a sequence of numbers indicative of progress of a computing node, an indication of a failure, an indication of normal operation, etc.
  • the first computing node 504 may be configured to store first operational state information within the first storage device 510 so that the second computing node 506 may read the first operational state information from the first storage device 510 over a first cloud infrastructure connection 520.
  • the second computing node 506 may be configured to store second operational state information within the second storage device 514 so that the first computing node 504 may read the second operational state information from the second storage device 514 over a second cloud infrastructure connection 518.
  • a cloud storage service 530 may be utilized to verify operational states of computing devices. Accordingly, the first computing node 504 and the second computing node 506 may be configured to store operational state information into cloud persistent storage accessible through the cloud storage service 530 of the cloud computing environment 500.
  • the cloud storage service 530 and the cloud persistent storage are provided by a cloud provider/owner of the cloud computing environment 500, and thus may provide highly available and reliable information regarding whether computing nodes are operational or not.
  • Fig. 5B illustrates the first computing node 504 detecting a loss 540 of communication over the internode communication link 508 (e.g., a timeout since a last receipt of operation state information from the second computing node 506 over the internode communication link 508) and/or of access to the second storage device 514 (e.g., an inability to access the second storage device 514 over the second cloud infrastructure connection 518) while the second computing node 506 is operational.
  • a loss 540 of communication over the internode communication link 508 e.g., a timeout since a last receipt of operation state information from the second computing node 506 over the internode communication link 508
  • the second storage device 514 e.g., an inability to access the second storage device 514 over the second cloud infrastructure connection 51
  • the first computing node 504 may query the cloud storage service 530 for operational state information 542 stored by the second computing node 506 within the cloud persistent storage (e.g., a heartbeat comprising sequences numbers indicating progress of the second computing node 506; an indication of a failure, kernel panic, or normal operating state; etc.). Because the operational state information 542 may indicate that the second computing node 506 is operational, the first computing node 504 may refrain from erroneously performing a switchover operation because the second computing node 506 is operational for providing clients with access to the second set of resources 516.
  • operational state information 542 may indicate that the second computing node 506 is operational
  • the first computing node 504 may refrain from erroneously performing a switchover operation because the second computing node 506 is operational for providing clients with access to the second set of resources 516.
  • the first computing node 504 may determine that the loss 540 corresponds to a cloud computing environment infrastructure failure and/or inoperability of the internode communication link 508.
  • Fig. 5C illustrates the first computing node 504 detecting a loss 551 of communication over the internode communication link 508 (e.g., a timeout since a last receipt of operation state information from the second computing node 506 over the internode communication link 508) and/or of access to the second storage device 514 (e.g., an inability to access the second storage device 514 over the second cloud infrastructure connection 518) while the second computing node 506 is in a failed state 550.
  • a loss 551 of communication over the internode communication link 508 e.g., a timeout since a last receipt of operation state information from the second computing node 506 over the internode communication link 508
  • the second storage device 514 e.g., an inability to access the second storage device 514 over the second cloud infrastructure connection 51
  • the first computing node 504 may query the cloud storage service 530 for operational state information 552 stored by the second computing node 506 within the cloud persistent storage (e.g., a heartbeat comprising sequences numbers indicating progress of the second computing node 506; an indication of a failure, kernel panic, or normal operating state; etc.).
  • operational state information 552 stored by the second computing node 506 within the cloud persistent storage (e.g., a heartbeat comprising sequences numbers indicating progress of the second computing node 506; an indication of a failure, kernel panic, or normal operating state; etc.).
  • the first computing node 504 may perform a switchover operation 554 to take over ownership of the second storage device 514 and/or the second set of resources 516 for providing clients with failover access to storage services previously provided by the second computing node 506 utilizing the second storage device 514 and/or the second set of resources 516. It may be appreciated that in another example, the first computing node 504 may also query a cloud environment node state provider to determine the operational state of the second computing node 506 (e.g., Figs. 4A- 4C).
  • FIG. 6 One embodiment of determining whether to perform a switchover operation between computing nodes is illustrated by an exemplary method 600 of Fig. 6.
  • the method 600 starts.
  • an internode communication link is established between a first computing node and a second computing node hosted within a cloud computing environment.
  • the first computing node is configured to provide clients with access to a first set of resources within the cloud computing environment.
  • the second computing node is configured to provide clients with access to a second set of resources within the cloud computing environment.
  • the first computing node and the second computing node are configured to provide operational state information to a cloud environment node state provider of the cloud computing environment.
  • the cloud environment node state provider may be queried for first operational state information of the first computing node, at 608.
  • a switchover operation may be performed from the first computing node to the second computing node for providing clients with failover access to the first set of resources, previously accessible to clients through the first computing node, based upon the second computing node being a failure recovery partner for the first computing node.
  • the method 600 ends.
  • FIG. 7 One embodiment of determining whether to perform a switchover operation between computing nodes is illustrated by an exemplary method 700 of Fig. 7.
  • the method 700 starts.
  • an internode communication link is established between a first computing node and a second computing node.
  • the first computing node and the second computing node may be hosted within a cloud computing environment.
  • the first computing node and the second computing node may be hosted within a non-cloud computing environment (e.g., a cluster network storage environment), but may have
  • the first computing node may be hosted within the cloud computing environment and the second computing node may be hosted within the non-cloud computing environment, where the second computing node has communicative access to the cloud computing environment.
  • the first computing node is configured to provide clients with access to a first set of resources.
  • the second computing node is configured to provide clients with access to a second set of resources.
  • the first computing node and the second computing node are configured to store operational state information into cloud persistent storage accessible through a cloud storage service of the cloud computing environment.
  • the cloud storage service may be queried for first operational state information of the first computing node, at 708.
  • a switchover operation may be performed from the first computing node to the second computing node for providing clients with failover access to the first set of resources, previously accessible to clients through the first computing node, based upon the second computing node being a failure recovery partner for the first computing node.
  • the method 700 ends.
  • Still another embodiment involves a computer-readable medium comprising processor-executable instructions configured to implement one or more of the techniques presented herein.
  • FIG. 8 An example embodiment of a computer-readable medium or a computer-readable device that is devised in these ways is illustrated in Fig. 8, wherein the implementation 800 comprises a computer-readable medium 808, such as a CD-R, DVD-R, flash drive, a platter of a hard disk drive, etc., on which is encoded computer-readable data 806.
  • This computer-readable data 806, such as binary data comprising at least one of a zero or a one in turn comprises a set of computer instructions 804 configured to operate according to one or more of the principles set forth herein.
  • the processor-executable computer instructions 804 are configured to perform a method 802, such as at least some of the exemplary method 600 of Fig.
  • the processor-executable instructions 804 are configured to implement a system, such as at least some of the exemplary system 400 of Figs. 4A-4C and/or at least some of the exemplary system 500 of Figs. 5A-5C, for example. Many such computer-readable media are contemplated to operate in accordance with the techniques presented herein.
  • Computer readable media can include processor-executable instructions configured to implement one or more of the methods presented herein, and may include any mechanism for storing this data that can be thereafter read by a computer system.
  • Examples of computer readable media include (hard) drives (e.g., accessible via network attached storage (NAS)), Storage Area Networks (SAN), volatile and nonvolatile memory, such as read-only memory (ROM), random-access memory (RAM), EEPROM and/or flash memory, CD-ROMs, CD-Rs, CD-RWs, DVDs, cassettes, magnetic tape, magnetic disk storage, optical or non-optical data storage devices and/or any other medium which can be used to store data.
  • NAS network attached storage
  • SAN Storage Area Networks
  • volatile and nonvolatile memory such as read-only memory (ROM), random-access memory (RAM), EEPROM and/or flash memory
  • CD-ROMs, CD-Rs, CD-RWs, DVDs cassettes, magnetic tape, magnetic disk storage, optical or non-optical data storage devices and/or any other medium which can be used to store data.
  • the claimed subject matter is implemented as a method, apparatus, or article of manufacture using standard application or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter.
  • article of manufacture as used herein is intended to encompass a computer application accessible from any computer-readable device, carrier, or media.
  • a component includes a process running on a processor, a processor, an object, an executable, a thread of execution, an application, or a computer.
  • an application running on a controller and the controller can be a component.
  • One or more components residing within a process or thread of execution and a component may be localized on one computer or distributed between two or more computers.
  • exemplary is used herein to mean serving as an example, instance, illustration, etc., and not necessarily as advantageous.
  • “or” is intended to mean an inclusive “or” rather than an exclusive “or”.
  • “a” and “an” as used in this application are generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.
  • at least one of A and B and/or the like generally means A or B and/or both A and B.
  • such terms are intended to be inclusive in a manner similar to the term “comprising”.
  • first,” “second,” or the like are not intended to imply a temporal aspect, a spatial aspect, an ordering, etc. Rather, such terms are merely used as identifiers, names, etc. for features, elements, items, etc.
  • a first set of information and a second set of information generally correspond to set of information A and set of information B or two different or two identical sets of information or the same set of information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Hardware Redundancy (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
PCT/US2016/059358 2015-10-30 2016-10-28 Method, device and medium for performing switchover operations between computing nodes WO2017075375A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201680062470.8A CN108351824B (zh) 2015-10-30 2016-10-28 用于在计算节点之间执行切换操作的方法、设备和介质
EP16791273.2A EP3368985B1 (en) 2015-10-30 2016-10-28 Method,device and medium for performing switchover operations between computing nodes
JP2018521645A JP6476350B2 (ja) 2015-10-30 2016-10-28 コンピューティングノード間の切り替え動作を実行する方法、装置、及び媒体

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14/928,137 2015-10-30
US14/928,137 US10855515B2 (en) 2015-10-30 2015-10-30 Implementing switchover operations between computing nodes

Publications (1)

Publication Number Publication Date
WO2017075375A1 true WO2017075375A1 (en) 2017-05-04

Family

ID=57233961

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/059358 WO2017075375A1 (en) 2015-10-30 2016-10-28 Method, device and medium for performing switchover operations between computing nodes

Country Status (5)

Country Link
US (2) US10855515B2 (zh)
EP (1) EP3368985B1 (zh)
JP (1) JP6476350B2 (zh)
CN (1) CN108351824B (zh)
WO (1) WO2017075375A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10521306B2 (en) * 2017-07-27 2019-12-31 Western Digital Technologies, Inc. Methods, systems and devices for restarting data processing units
US11157300B2 (en) * 2018-02-13 2021-10-26 Sophos Limited Managing virtual machine security resources
KR102494744B1 (ko) * 2018-03-22 2023-02-02 국방과학연구소 서비스의 연속성을 지원하는 클라우드 서버, 이를 포함하는 시스템 및 방법
US10860368B2 (en) * 2018-09-28 2020-12-08 Juniper Networks, Inc. Migrating workloads in multicloud computing environments
US10909009B2 (en) * 2018-11-01 2021-02-02 Dell Products L.P. System and method to create a highly available quorum for clustered solutions
CN111176888B (zh) * 2018-11-13 2023-09-15 浙江宇视科技有限公司 云存储的容灾方法、装置及系统
CN110333974B (zh) * 2019-06-03 2022-04-15 腾讯科技（深圳）有限公司 一种云存储服务的切换方法和设备
CN112199240B (zh) * 2019-07-08 2024-01-30 华为云计算技术有限公司 一种节点故障时进行节点切换的方法及相关设备
CN113746763B (zh) * 2020-05-29 2022-11-11 华为技术有限公司 一种数据处理的方法、装置和设备
US11625338B1 (en) * 2021-10-29 2023-04-11 Hewlett Packard Enterprise Development Lp Extending supervisory services into trusted cloud operator domains

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050204183A1 (en) * 2004-03-12 2005-09-15 Hitachi, Ltd. System and method for failover
EP2800303A1 (en) * 2012-08-17 2014-11-05 Huawei Technologies Co., Ltd Switch method, device and system for virtual application dual machine in cloud environment
US20150019900A1 (en) * 2013-07-11 2015-01-15 International Business Machines Corporation Tolerating failures using concurrency in a cluster
US20150269043A1 (en) * 2014-03-20 2015-09-24 Netapp Inc. Storage device health status synchronization

Family Cites Families (69)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH01195544A (ja) * 1988-01-29 1989-08-07 Nec Corp デュプレックス構成システムのダウン監視方式
DE19613519B4 (de) 1996-04-03 2014-06-05 Robert Bosch Gmbh Telefonanlage für schnurlose Telefone
GB2353113B (en) * 1999-08-11 2001-10-10 Sun Microsystems Inc Software fault tolerant computer system
US6954435B2 (en) * 2002-04-29 2005-10-11 Harris Corporation Determining quality of service (QoS) routing for mobile ad hoc networks
JP2004021556A (ja) * 2002-06-14 2004-01-22 Hitachi Ltd 記憶制御装置およびその制御方法
US20040250030A1 (en) * 2003-06-06 2004-12-09 Minwen Ji Data redundancy using portal and host computer
US7380081B2 (en) * 2003-06-06 2008-05-27 Hewlett-Packard Development Company, L.P. Asynchronous data redundancy technique
US7178055B2 (en) * 2003-06-06 2007-02-13 Hewlett-Packard Development Company, L.P. Method and system for ensuring data consistency after a failover event in a redundant data storage system
US7120825B2 (en) * 2003-06-06 2006-10-10 Hewlett-Packard Development Company, L.P. Adaptive batch sizing for asynchronous data redundancy
US7089383B2 (en) * 2003-06-06 2006-08-08 Hewlett-Packard Development Company, L.P. State machine and system for data redundancy
US7711820B2 (en) * 2004-11-08 2010-05-04 Cisco Technology, Inc. High availability for intelligent applications in storage networks
US7426653B2 (en) * 2005-04-13 2008-09-16 Progress Software Corporation Fault tolerant distributed lock management
US7804769B1 (en) * 2005-12-01 2010-09-28 Juniper Networks, Inc. Non-stop forwarding in a multi-chassis router
US8266472B2 (en) * 2006-05-03 2012-09-11 Cisco Technology, Inc. Method and system to provide high availability of shared data
US7711683B1 (en) * 2006-11-30 2010-05-04 Netapp, Inc. Method and system for maintaining disk location via homeness
US7685461B2 (en) * 2006-12-20 2010-03-23 International Business Machines Corporation Method, apparatus and program storage device for performing fault tolerant code upgrade on a fault tolerant system by determining when functional code reaches a desired state before resuming an upgrade
US20080162984A1 (en) * 2006-12-28 2008-07-03 Network Appliance, Inc. Method and apparatus for hardware assisted takeover
US7899895B2 (en) * 2007-08-29 2011-03-01 International Business Machines Corporation Transfer of ownership of a storage object in response to an original owner node becoming available after a period of unavailability
US7778986B2 (en) * 2007-08-29 2010-08-17 International Business Machines Corporation Securing transfer of ownership of a storage object from an unavailable owner node to another node
US8064360B2 (en) * 2009-01-23 2011-11-22 Empire Technology Development Llc Wireless home network routing protocol
US8943498B2 (en) * 2009-05-31 2015-01-27 Red Hat Israel, Ltd. Method and apparatus for swapping virtual machine memory
US8417938B1 (en) * 2009-10-16 2013-04-09 Verizon Patent And Licensing Inc. Environment preserving cloud migration and management
US8078902B2 (en) * 2009-10-30 2011-12-13 Verizon Patent And Licensing, Inc. Fault surveillance and automatic fail-over processing in broker-based messaging systems and methods
US8452932B2 (en) * 2010-01-06 2013-05-28 Storsimple, Inc. System and method for efficiently creating off-site data volume back-ups
US9098456B2 (en) * 2010-01-13 2015-08-04 International Business Machines Corporation System and method for reducing latency time with cloud services
US8515726B2 (en) * 2010-01-20 2013-08-20 Xyratex Technology Limited Method, apparatus and computer program product for modeling data storage resources in a cloud computing environment
CN101860492A (zh) * 2010-06-28 2010-10-13 中兴通讯股份有限公司 快速切换的方法、装置和系统
US8799422B1 (en) * 2010-08-16 2014-08-05 Juniper Networks, Inc. In-service configuration upgrade using virtual machine instances
US8413145B2 (en) * 2010-09-30 2013-04-02 Avaya Inc. Method and apparatus for efficient memory replication for high availability (HA) protection of a virtual machine (VM)
US8676763B2 (en) * 2011-02-08 2014-03-18 International Business Machines Corporation Remote data protection in a networked storage computing environment
US8984330B2 (en) * 2011-03-28 2015-03-17 Siemens Corporation Fault-tolerant replication architecture
US8751863B2 (en) * 2011-05-23 2014-06-10 Microsoft Corporation Implementing failover processes between storage stamps
US8930320B2 (en) * 2011-09-30 2015-01-06 Accenture Global Services Limited Distributed computing backup and recovery system
CN102546256B (zh) * 2012-01-12 2015-05-06 易云捷讯科技（北京）有限公司 用于对云计算服务进行监控的系统及方法
US9213580B2 (en) * 2012-01-27 2015-12-15 MicroTechnologies LLC Transportable private cloud computing platform and associated method of use
US9304879B2 (en) * 2012-03-12 2016-04-05 Os Nexus, Inc. High availability failover utilizing dynamic switch configuration
US8839031B2 (en) * 2012-04-24 2014-09-16 Microsoft Corporation Data consistency between virtual machines
US8966491B2 (en) * 2012-04-27 2015-02-24 Oracle International Corporation System and method for implementing NUMA-aware reader-writer locks
US8935563B1 (en) * 2012-06-15 2015-01-13 Symantec Corporation Systems and methods for facilitating substantially continuous availability of multi-tier applications within computer clusters
US9367412B2 (en) * 2012-06-25 2016-06-14 Netapp, Inc. Non-disruptive controller replacement in network storage systems
US10152398B2 (en) * 2012-08-02 2018-12-11 At&T Intellectual Property I, L.P. Pipelined data replication for disaster recovery
US20140095925A1 (en) * 2012-10-01 2014-04-03 Jason Wilson Client for controlling automatic failover from a primary to a standby server
US9378145B2 (en) * 2013-03-05 2016-06-28 Dot Hill Systems Corporation Storage controller cache synchronization method and apparatus
US20160057214A1 (en) * 2013-04-15 2016-02-25 P. Ashok Anand Load Balancer System and Method for Server/Nodes in Cloud Environment
CN103209099B (zh) * 2013-05-03 2016-06-29 广州市成格信息技术有限公司 一种节点间的网络通信线路的自动切换保护方法
US9483558B2 (en) * 2013-05-29 2016-11-01 Commvault Systems, Inc. Assessing user performance in a community of users of data storage resources
US11042309B1 (en) * 2013-08-23 2021-06-22 Acronis International Gmbh Recovery of virtual machine files using disk attachment
US9946843B2 (en) * 2013-11-13 2018-04-17 Koninklijke Philips N.V. Clinical decision support system based triage decision making
US9582373B2 (en) * 2014-03-31 2017-02-28 Vmware, Inc. Methods and systems to hot-swap a virtual machine
US9317380B2 (en) * 2014-05-02 2016-04-19 International Business Machines Corporation Preserving management services with self-contained metadata through the disaster recovery life cycle
WO2015197564A1 (en) * 2014-06-23 2015-12-30 Getclouder Ltd. Cloud hosting systems featuring scaling and load balancing with containers
US9940073B1 (en) * 2014-06-30 2018-04-10 EMC IP Holding Company LLC Method and apparatus for automated selection of a storage group for storage tiering
US9641388B2 (en) * 2014-07-29 2017-05-02 Commvault Systems, Inc. Customized deployment in information management systems
US9489270B2 (en) * 2014-07-31 2016-11-08 International Business Machines Corporation Managing backup operations from a client system to a primary server and secondary server
US20160048408A1 (en) * 2014-08-13 2016-02-18 OneCloud Labs, Inc. Replication of virtualized infrastructure within distributed computing environments
US20160085606A1 (en) * 2014-09-19 2016-03-24 Netapp Inc. Cluster-wide outage detection
US9436555B2 (en) * 2014-09-22 2016-09-06 Commvault Systems, Inc. Efficient live-mount of a backed up virtual machine in a storage management system
US9417968B2 (en) * 2014-09-22 2016-08-16 Commvault Systems, Inc. Efficiently restoring execution of a backed up virtual machine based on coordination with virtual-machine-file-relocation operations
WO2016071736A1 (en) * 2014-11-04 2016-05-12 Telefonaktiebolaget L M Ericsson (Publ) Network function virtualization service chaining
US9912625B2 (en) * 2014-11-18 2018-03-06 Commvault Systems, Inc. Storage and management of mail attachments
US20160142485A1 (en) * 2014-11-19 2016-05-19 Commvault Systems, Inc. Migration to cloud storage from backup
US10061664B2 (en) * 2015-01-15 2018-08-28 Cisco Technology, Inc. High availability and failover
JP6540072B2 (ja) * 2015-02-16 2019-07-10 富士通株式会社 管理装置、情報処理システム及び管理プログラム
US9747180B1 (en) * 2015-03-31 2017-08-29 EMC IP Holding Company LLC Controlling virtual endpoint failover during administrative SCSI target port disable/enable
US9800459B1 (en) * 2015-04-01 2017-10-24 EMC IP Holding Company LLC Dynamic creation, deletion, and management of SCSI target virtual endpoints
US10275328B2 (en) * 2015-04-02 2019-04-30 Vmware, Inc. Fault tolerance for hybrid cloud deployments
US10303453B2 (en) * 2015-05-08 2019-05-28 Desktop 365, LLC Method and system for managing the end to end lifecycle of the virtualization environment for an appliance
US9921764B2 (en) * 2015-06-30 2018-03-20 International Business Machines Corporation Using inactive copy relationships to resynchronize data between storages
US10423588B2 (en) * 2015-08-25 2019-09-24 International Business Machines Corporation Orchestrated disaster recovery

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050204183A1 (en) * 2004-03-12 2005-09-15 Hitachi, Ltd. System and method for failover
EP2800303A1 (en) * 2012-08-17 2014-11-05 Huawei Technologies Co., Ltd Switch method, device and system for virtual application dual machine in cloud environment
US20150019900A1 (en) * 2013-07-11 2015-01-15 International Business Machines Corporation Tolerating failures using concurrency in a cluster
US20150269043A1 (en) * 2014-03-20 2015-09-24 Netapp Inc. Storage device health status synchronization

Also Published As

Publication number Publication date
US10855515B2 (en) 2020-12-01
EP3368985B1 (en) 2019-06-19
CN108351824B (zh) 2021-07-30
US20170126479A1 (en) 2017-05-04
CN108351824A (zh) 2018-07-31
US20210075665A1 (en) 2021-03-11
JP2018536229A (ja) 2018-12-06
EP3368985A1 (en) 2018-09-05
JP6476350B2 (ja) 2019-02-27

Similar Documents

Publication Publication Date Title
US11232004B2 (en) Implementing automatic switchover
US20210075665A1 (en) Implementing switchover operations between computing nodes
US20220276941A1 (en) Trust relationship migration for data mirroring
US9990262B2 (en) Dynamic mirroring
US9715435B2 (en) Interconnect path failover
US10719419B2 (en) Service processor traps for communicating storage controller failure
US9836345B2 (en) Forensics collection for failed storage controllers
US10853210B2 (en) Storage device health status synchronization
US9348714B2 (en) Survival site load balancing
US9952951B2 (en) Preserving coredump data during switchover operation
US10855522B2 (en) Dual port storage device emulation
WO2016195841A1 (en) Dynamic mirroring

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16791273

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2018521645

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016791273

Country of ref document: EP