CN111949214B - Disk misoperation method, system, equipment and medium for preventing HANA cluster - Google Patents
Disk misoperation method, system, equipment and medium for preventing HANA cluster Download PDFInfo
- Publication number
- CN111949214B CN111949214B CN202010788660.6A CN202010788660A CN111949214B CN 111949214 B CN111949214 B CN 111949214B CN 202010788660 A CN202010788660 A CN 202010788660A CN 111949214 B CN111949214 B CN 111949214B
- Authority
- CN
- China
- Prior art keywords
- key
- volume
- working node
- node
- lun
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- WVCHIGAIXREVNS-UHFFFAOYSA-N 2-hydroxy-1,4-naphthoquinone Chemical compound C1=CC=C2C(O)=CC(=O)C(=O)C2=C1 WVCHIGAIXREVNS-UHFFFAOYSA-N 0.000 title claims abstract description 35
- 230000004044 response Effects 0.000 claims abstract description 13
- 238000013507 mapping Methods 0.000 claims description 17
- 238000004590 computer program Methods 0.000 claims description 8
- 230000008569 process Effects 0.000 claims description 8
- 238000001514 detection method Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 6
- 230000007257 malfunction Effects 0.000 description 3
- 230000002265 prevention Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0614—Improving the reliability of storage systems
- G06F3/0619—Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/0643—Management of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0662—Virtualisation aspects
- G06F3/0665—Virtualisation aspects at area level, e.g. provisioning of virtual or logical volumes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/0671—In-line storage system
- G06F3/0683—Plurality of storage devices
- G06F3/0689—Disk arrays, e.g. RAID, JBOD
-
- 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
- H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- 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
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
Abstract
The invention discloses a disk misoperation method for preventing an HANA cluster, which comprises the following steps: generating a key corresponding to each working node, and respectively writing the key into an LUN header file corresponding to the volume under each working node; responding to the operation request of the working node to the volume, converting the operation request into an operation command and adding a key corresponding to the working node into the operation command; sending the operation command added with the key to a bottom storage and comparing the key; and in response to that the key in the operation command is different from the key in the LUN header file corresponding to the volume to be operated, not operating the volume to be operated and reporting an error. The invention also discloses a system, a computer device and a readable storage medium. The scheme provided by the invention can not only realize the method for preventing the data disks under other nodes from being operated by mistake, effectively solve the problem of artificial misoperation of the disks, but also ensure the disaster tolerance of the HANA cluster.
Description
Technical Field
The invention relates to the field of an HANA cluster, in particular to a method, a system, equipment and a storage medium for preventing disk misoperation of the HANA cluster.
Background
The multiple servers are used for constructing the HANA cluster, so that the requirement for a larger memory can be met, and the disaster tolerance of the nodes of the HANA cluster can be realized. However, in order to implement disaster recovery of HANA cluster nodes, all nodes need to have access to all shared disk volume groups. As shown in fig. 1, the HANA cluster shown in the figure includes 3+1 nodes (3 working nodes and one standby node), each working node has a respective data and log volume, and when any one of the working nodes (here, host2) generates an abnormal state, host4 (standby node) can manage the corresponding data and log volumes of any failed node. After the failed node is repaired, the shared disk volume of all other nodes also needs to be accessed. For the HANA cluster, all cluster nodes need to be able to access all shared volumes, but in normal operation of the HANA cluster, each cluster node only performs data operations on its respective data and log volumes, and does not need to perform operations on the data volumes and log volumes of other clusters. All nodes of the HANA cluster can operate data and log volumes of other nodes, and with the increase of the number of nodes of the HANA cluster, the difficulty of technicians in the actual operation and maintenance process is higher, so that the data of a data disk can be lost due to misoperation.
Disclosure of Invention
In view of the above, in order to overcome at least one aspect of the above problems, an embodiment of the present invention provides a method for preventing a disk misoperation in a HANA cluster, including the following steps:
generating a key corresponding to each working node, and respectively writing the key into an LUN (logical unit number) header file corresponding to a volume under each working node;
responding to the working node receiving an operation request for the volume, converting the operation request into an operation command and adding a key corresponding to the working node into the operation command;
sending the operation command added with the key to a bottom storage and comparing the key;
and in response to that the key in the operation command is different from the key in the LUN header file corresponding to the volume to be operated, not operating the volume to be operated and reporting an error.
In some embodiments, further comprising:
and responding to the fact that the key in the operation command is the same as the key in the LUN head file corresponding to the volume to be operated, and carrying out corresponding operation on the volume to be operated according to the operation command.
In some embodiments, further comprising:
and respectively sending the key corresponding to each working node and the identification code of the volume to all other nodes to obtain the mapping relation of the identification codes of each working node, the key and the volume.
In some embodiments, further comprising:
generating a key corresponding to the standby node in response to the detection that the working node fails;
and determining a key corresponding to the failed working node and an identification code of the volume according to the mapping relation, and replacing the key in the LUN header file corresponding to the volume under the failed working node with the key corresponding to the spare node by using the key corresponding to the spare node and the key corresponding to the failed working node.
In some embodiments, replacing a key in the LUN header file corresponding to the volume in the failed working node with a key corresponding to the spare node and a key corresponding to the failed working node, further includes:
deleting the key in the LUN header file corresponding to the volume under the working node with the fault by using the key corresponding to the working node with the fault;
and writing the key corresponding to the standby node into the LUN header file corresponding to the volume under the working node with the fault.
In some embodiments, further comprising:
and sending the key corresponding to the standby node and the identification code of the volume to other non-failed working nodes so as to update the mapping relation.
In some embodiments, in response to detecting that the working node fails, generating a key corresponding to a standby node, further includes:
and switching the process service on the failed working node to the standby node.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a disk misoperation prevention system for HANA clustering, comprising:
the generating module is configured to generate a key corresponding to each working node and write the key into an LUN header file corresponding to a volume under each working node;
the adding module is configured to respond to the fact that the working node receives an operation request for the volume, convert the operation request into an operation command and add a key corresponding to the working node into the operation command;
the sending module is configured to send the operation command added with the key to a bottom storage and compare the key;
and the comparison module is configured to respond that the key in the operation command is different from the key in the LUN header file corresponding to the volume to be operated, and does not operate the volume to be operated and reports an error.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer apparatus, including:
at least one processor; and
a memory storing a computer program operable on the processor, wherein the processor executes any of the above-described methods for preventing a disk malfunction in a HANA cluster when executing the program.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer-readable storage medium storing a computer program which, when executed by a processor, performs the steps of any of the above-described methods for preventing a disk malfunction of a HANA cluster.
The invention has one of the following beneficial technical effects: the scheme provided by the invention can not only realize the method for preventing the data disks under other nodes from being operated by mistake, effectively solve the problem of artificial misoperation of the disks, but also ensure the disaster tolerance of the HANA cluster.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other embodiments can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic diagram of a structure of a HANA cluster;
FIG. 2 is a flowchart illustrating a method for preventing disk misoperation in a HANA cluster according to an embodiment of the present invention;
fig. 3 is a mapping relationship diagram before a node fails according to an embodiment of the present invention;
fig. 4 is a mapping relationship diagram after a node fails according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a mailbox-based remote control system according to an embodiment of the present invention;
FIG. 6 is a schematic structural diagram of a computer device provided in an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.
It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are used for distinguishing two entities with the same name but different names or different parameters, and it should be noted that "first" and "second" are only used for convenience of expression and should not be construed as a limitation to the embodiments of the present invention, and no description is given in the following embodiments.
According to an aspect of the present invention, an embodiment of the present invention provides a disk misoperation prevention method for HANA cluster, as shown in fig. 2, which may include the steps of:
s1, generating a key corresponding to each working node, and writing the key into the LUN header file corresponding to the volume under each working node;
s2, responding to the operation request of the working node to the volume, converting the operation request into an operation command and adding the key corresponding to the working node into the operation command;
s3, sending the operation command added with the key to a bottom storage and comparing the key;
s4, in response to the fact that the key in the operation command is different from the key in the LUN header file corresponding to the volume to be operated, the volume to be operated is not operated and an error is reported.
The scheme provided by the invention can not only realize the method for preventing the data disks under other nodes from being operated by mistake, effectively solve the problem of artificial misoperation of the disks, but also ensure the disaster tolerance of the HANA cluster.
In some embodiments, in step S1, a Key corresponding to each working node is generated, and the Key is written into the LUN header file corresponding to the volume under each working node, specifically, an SCSI command may be initiated by the SCSI controller on each node to generate a random Key using a random function, the SCSI controller records and retains the Key and sends the Key to the storage controller in the bottom layer storage, and the storage controller writes the Key into the LUN header file corresponding to the volume under each working node.
For example, taking 3+1 HANA cluster nodes as an example, as shown in fig. 3, the HANA cluster nodes host1 to host3 are working nodes, and the nodes host1 to host3 of the HANA cluster generate keys 1, 2, and 3, respectively, and use the generated keys to lock the volumes used by the keys, respectively.
In some embodiments, the method further comprises:
and respectively sending the key corresponding to each working node and the identification code of the volume to all other nodes to obtain the mapping relation of the identification codes of each working node, the key and the volume.
Specifically, the generated keys (key1, key2, key3) are distributed to all HANA cluster nodes (host 1-4, wherein host4 is a standby node), and the node names, the identification codes of the volumes and the mapping relations between the keys are recorded.
In some embodiments, the method further comprises:
and responding to the fact that the key in the operation command is the same as the key in the LUN head file corresponding to the volume to be operated, and carrying out corresponding operation on the volume to be operated according to the operation command.
Specifically, when the operating system of the node receives an I/O request for operating a volume, the request may be converted into an SCSI operating command through the SCSI controller, and a key is attached to the SCSI command and then issued to the storage controller in the underlying storage, and then the storage controller is used to verify whether the key carried in the SCSI command is consistent with the key in the LUN header file corresponding to the volume to be operated. If the two volumes are consistent, the volume can be operated, if the two volumes are inconsistent, the volume can not be operated and an error is reported,
it should be noted that all volumes of the cluster node are in a locked state, and although each node has a key of another node, when a volume is to be operated, only the key of the node is used, so that when a user needs to operate the volume, such as mkvg, mkfs, dd, and the like, if the volume to be operated selected by the user is not the volume corresponding to the node, the user cannot operate the volume, and misoperation of the volumes of other nodes is prevented.
In some embodiments, the method further comprises:
generating a key corresponding to the standby node in response to the detection that the working node fails;
and determining a key corresponding to the failed working node and an identification code of the volume according to the mapping relation, and replacing the key in the LUN header file corresponding to the volume under the failed working node with the key corresponding to the spare node by using the key corresponding to the spare node and the key corresponding to the failed working node.
In some embodiments, replacing a key in the LUN header file corresponding to the volume in the failed working node with a key corresponding to the spare node and a key corresponding to the failed working node, further includes:
deleting a key in an LUN header file corresponding to a volume under the working node with the fault by using the key corresponding to the working node with the fault;
and writing the key corresponding to the standby node into the LUN header file corresponding to the volume under the working node with the fault.
In some embodiments, further comprising:
and sending the key corresponding to the standby node and the identification code of the volume to other working nodes which do not have faults so as to update the mapping relation.
In some embodiments, in response to detecting that the working node fails, generating a key corresponding to a standby node, further includes:
and switching the process service on the failed working node to the standby node.
Specifically, as shown in fig. 4, when a working node of the cluster fails, for example, host2 fails and cannot be accessed, host4 unlocks disk2 locked by host2 using key2 corresponding to host2 according to the mapping table shown in fig. 3. After the Host4 is unlocked, a new key (key4) is generated again, the disk2 is locked by using the key4 according to the same locking flow, and the key4 is redistributed to all HANA cluster nodes to generate a new mapping relation. And the HANA cluster related process service can be switched to host4, so that the HANA cluster disaster tolerance switching is realized.
According to the scheme provided by the invention, the volume is locked, so that when a user needs to operate the volume, if the volumes under other nodes are operated by mistake, the volumes can be directly reported by mistake without being operated by corresponding keys. And the key generated by each node can be shared by all other nodes, so that after the working node fails, the standby node can unlock the volume under the failed working node according to the shared key and ensure cluster disaster tolerance.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a disk misoperation prevention system 400 for HANA clustering, as shown in fig. 5, comprising:
a generating module 401, where the generating module 401 is configured to generate a key corresponding to each working node, and write the key into an LUN header file corresponding to a volume under each working node;
an adding module 402, wherein the adding module 402 is configured to respond to the working node receiving an operation request for a volume, convert the operation request into an operation command, and add a key corresponding to the working node into the operation command;
a sending module 403, where the sending module 403 is configured to send the operation command with the key added to a bottom storage and compare the key;
a comparison module 404, where the comparison module 404 is configured to not operate the to-be-operated volume and report an error in response to that a key in the operation command is different from a key in the LUN header corresponding to the to-be-operated volume.
In some embodiments, the system 400 further comprises a first response module configured to:
and responding to the fact that the key in the operation command is the same as the key in the LUN head file corresponding to the volume to be operated, and performing corresponding operation on the volume to be operated according to the operation command.
In some embodiments, system 400 further comprises a sharing module configured to:
and respectively sending the key corresponding to each working node and the identification code of the volume to all other nodes to obtain the mapping relation of the identification codes of each working node, the key and the volume.
In some embodiments, the sharing module is further configured to:
generating a key corresponding to the standby node in response to the detection that the working node fails;
and determining a key corresponding to the failed working node and an identification code of the volume according to the mapping relation, and replacing the key in the LUN header file corresponding to the volume under the failed working node with the key corresponding to the spare node by using the key corresponding to the spare node and the key corresponding to the failed working node.
In some embodiments, the sharing module is further configured to:
deleting the key in the LUN header file corresponding to the volume under the working node with the fault by using the key corresponding to the working node with the fault;
and writing the key corresponding to the standby node into the LUN header file corresponding to the volume under the working node with the fault.
In some embodiments, the sharing module is further configured to:
and sending the key corresponding to the standby node and the identification code of the volume to other non-failed working nodes so as to update the mapping relation.
In some embodiments, the sharing module is further configured to: and switching the process service on the failed working node to the standby node.
Based on the same inventive concept, according to another aspect of the present invention, as shown in fig. 6, an embodiment of the present invention further provides a computer apparatus 501, comprising:
at least one processor 520; and
the memory 510 and the memory 510 store a computer program 511 that can be executed on the processor, and the processor 520 executes the program to perform any of the above-described steps of the method for preventing a disk malfunction in a HANA cluster.
Based on the same inventive concept, according to another aspect of the present invention, as shown in fig. 7, an embodiment of the present invention further provides a computer-readable storage medium 601, where the computer-readable storage medium 601 stores computer program instructions 610, and the computer program instructions 610, when executed by a processor, perform the steps of any of the above methods for preventing disk misoperation of a HANA cluster.
Finally, it should be noted that, as those skilled in the art can understand, all or part of the processes in the methods of the embodiments described above can be implemented by instructing relevant hardware through a computer program, and the program may be stored in a computer readable storage medium, and when executed, may include the processes of the embodiments of the methods described above.
Further, it should be understood that the computer-readable storage medium herein (e.g., memory) can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.
The foregoing are exemplary embodiments of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, where the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant only to be exemplary, and is not intended to intimate that the scope of the disclosure, including the claims, is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of the embodiments of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.
Claims (10)
1. A disk misoperation preventing method for an HANA cluster is characterized by comprising the following steps:
generating a key corresponding to each working node, and respectively writing the key into an LUN header file corresponding to the volume under each working node;
responding to the operation request of the working node to the volume, converting the operation request into an operation command and adding a key corresponding to the working node into the operation command;
sending the operation command added with the key to a bottom storage and comparing the key;
and in response to that the key in the operation command is different from the key in the LUN header file corresponding to the volume to be operated, not operating the volume to be operated and reporting an error.
2. The method of claim 1, further comprising:
and responding to the fact that the key in the operation command is the same as the key in the LUN head file corresponding to the volume to be operated, and carrying out corresponding operation on the volume to be operated according to the operation command.
3. The method of claim 1, further comprising:
and respectively sending the key corresponding to each working node and the identification code of the volume to all other nodes to obtain the mapping relation of the identification codes of each working node, the key and the volume.
4. The method of claim 3, further comprising:
generating a key corresponding to the standby node in response to the detection that the working node fails;
and determining a key corresponding to the failed working node and an identification code of the volume according to the mapping relation, and replacing the key in the LUN header file corresponding to the volume under the failed working node with the key corresponding to the spare node by using the key corresponding to the spare node and the key corresponding to the failed working node.
5. The method of claim 4, wherein replacing a key in the LUN header file corresponding to the volume under the failed working node with a key corresponding to the backup node and a key corresponding to the failed working node, further comprises:
deleting the key in the LUN header file corresponding to the volume under the working node with the fault by using the key corresponding to the working node with the fault;
and writing the key corresponding to the standby node into the LUN header file corresponding to the volume under the working node with the fault.
6. The method of claim 4, further comprising:
and sending the key corresponding to the standby node and the identification code of the volume to other working nodes which do not have faults so as to update the mapping relation.
7. The method of claim 4, wherein generating a key corresponding to a backup node in response to detecting the working node fails further comprises:
and switching the process service on the failed working node to the standby node.
8. A disk misoperation system for preventing HANA clustering, comprising:
the generating module is configured to generate a key corresponding to each working node and write the key into an LUN header file corresponding to a volume under each working node;
the adding module is configured to respond to the fact that the working node receives an operation request for the volume, convert the operation request into an operation command and add a key corresponding to the working node into the operation command;
the sending module is configured to send the operation command added with the key to a bottom storage and compare the key;
and the comparison module is configured to respond that the key in the operation command is different from the key in the LUN header file corresponding to the volume to be operated, and not operate the volume to be operated and report an error.
9. A computer device, comprising:
at least one processor; and
memory storing a computer program operable on the processor, characterized in that the processor, when executing the program, performs the steps of the method according to any of claims 1-7.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, is adapted to carry out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010788660.6A CN111949214B (en) | 2020-08-07 | 2020-08-07 | Disk misoperation method, system, equipment and medium for preventing HANA cluster |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010788660.6A CN111949214B (en) | 2020-08-07 | 2020-08-07 | Disk misoperation method, system, equipment and medium for preventing HANA cluster |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111949214A CN111949214A (en) | 2020-11-17 |
| CN111949214B true CN111949214B (en) | 2022-07-26 |
Family
ID=73331762
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010788660.6A Active CN111949214B (en) | 2020-08-07 | 2020-08-07 | Disk misoperation method, system, equipment and medium for preventing HANA cluster |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111949214B (en) |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7613947B1 (en) * | 2006-11-30 | 2009-11-03 | Netapp, Inc. | System and method for storage takeover |
| CN109639794B (en) * | 2018-12-10 | 2021-07-13 | 杭州数梦工场科技有限公司 | State cluster recovery method, device, equipment and readable storage medium |
| CN110213230B (en) * | 2019-04-26 | 2020-01-31 | 特斯联（北京）科技有限公司 | network security verification method and device for distributed communication |
-
2020
- 2020-08-07 CN CN202010788660.6A patent/CN111949214B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN111949214A (en) | 2020-11-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8433947B2 (en) | Computer program, method, and apparatus for controlling data allocation | |
| US9541978B2 (en) | Redundancies for reconstruction in mass data storage systems | |
| US6266785B1 (en) | File system filter driver apparatus and method | |
| US7133964B2 (en) | Raid assimilation method and apparatus | |
| US8572431B2 (en) | Disaster recovery framework | |
| JP4371724B2 (en) | Storage system and storage device system | |
| CN113515499B (en) | Database service method and system | |
| US8707098B2 (en) | Recovery procedure for a data storage system | |
| US7702757B2 (en) | Method, apparatus and program storage device for providing control to a networked storage architecture | |
| CN110569149B (en) | Method for triggering Oracle disaster recovery automatic emergency switching based on fault detection | |
| KR100825720B1 (en) | File management method in file system and metadata server for the same | |
| US6366965B1 (en) | System for updating an identity of a device in response to determining that a neighbor device has an identity different from one stored therein | |
| JPH05307445A (en) | Method and device for deciding states of a pair of mirrored data storage units in data processing system | |
| KR20060052773A (en) | System and method of relational configuration mirroring | |
| US5996087A (en) | Program product for serializating actions of independent process groups | |
| US8423776B2 (en) | Storage systems and data storage method | |
| CN111949214B (en) | Disk misoperation method, system, equipment and medium for preventing HANA cluster | |
| US6754753B2 (en) | Atomic ownership change operation for input/output (I/O) bridge device in clustered computer system | |
| CN112732492A (en) | Extraction backup method and system based on cloud database | |
| US20060155718A1 (en) | Multiple copy track stage recovery in a data storage system | |
| US20190354433A1 (en) | Parity log with by-pass | |
| US10809940B1 (en) | Multilevel resiliency | |
| Pâris et al. | Self-adaptive disk arrays | |
| CN117667526A (en) | Data distributed storage fault database switching method and system | |
| CN117851132B (en) | Data recovery optimization method for distributed object storage |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |