CN112882871A - Host conflict detection method, device, equipment and storage medium - Google Patents
Host conflict detection method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112882871A CN112882871A CN202110471323.9A CN202110471323A CN112882871A CN 112882871 A CN112882871 A CN 112882871A CN 202110471323 A CN202110471323 A CN 202110471323A CN 112882871 A CN112882871 A CN 112882871A
- Authority
- CN
- China
- Prior art keywords
- host
- identification information
- instruction
- data
- recovered
- 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.)
- Granted
Links
Images
Classifications
-
- 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/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention belongs to the technical field of data recovery, and discloses a host conflict detection method, device, equipment and storage medium. The method comprises the following steps: when a data recovery instruction is received, determining corresponding backup data and a host to be recovered according to the data recovery instruction, wherein the backup data comprises a backup file of a source host and identification information of the source host; sending the backup data to a host to be restored so that the host to be restored performs data restoration according to the backup file and feeds back identification information; detecting whether other hosts associated with the service system have the same identification information; and when the same identification information exists in other hosts related to the service system, judging that the service system has host conflict. By the above mode, after the host to be recovered performs data recovery according to the backup data, the host to be recovered feeds back the identification information of the host to acquire the host with the identification information, and judges whether the host with the identification information conflicts with the source host, so as to achieve the purpose of detecting whether the host conflicts exist.
Description
Technical Field
The present invention relates to the field of data recovery technologies, and in particular, to a method, an apparatus, a device, and a storage medium for detecting a host conflict.
Background
At present, many business systems are backed up, and in order to verify the validity of backup data and the continuity of business, disaster recovery drilling needs to be performed on the backup data regularly. It is common practice to shut down the original business system host, restore the backed up data and system to another host, and then verify whether the restored business system is the same as expected. After the drill is finished, the recovered host needs to be closed, and the original service system host is restarted, otherwise, host conflict occurs. Because many service systems are composed of a plurality of hosts, different hosts (some physical machines of a machine room, some cloud hosts of a public cloud, and some virtual machines … … on super fusion) may be recovered during drilling, and after the drilling is finished, a specific host is forgotten to be closed, so that the original service system host is abnormally operated after being started (such as ip collision or incapability of normally registering on a domain control server and a cluster), the service is interrupted, and the troubleshooting process may be time-consuming and labor-consuming.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a host conflict detection method, device, equipment and storage medium, and aims to solve the technical problem that in the prior art, after disaster recovery drilling is performed on backup data of a source host, whether a drilling host exists or not is detected, so that host conflict is caused.
In order to achieve the above object, the present invention provides a host collision detection method, including the following steps:
when a data recovery instruction is received, determining corresponding backup data and a host to be recovered according to the data recovery instruction, wherein the backup data comprises a backup file of a source host and identification information of the source host;
sending the backup data to the host to be restored so that the host to be restored performs data restoration according to the backup file and feeds back the identification information;
detecting whether other hosts related to the service system have the identification information or not;
and when the identification information exists in other hosts associated with the service system, judging that the service system has host conflict.
Optionally, the step of sending the backup data to the host to be restored to enable the host to be restored to perform data restoration according to the backup file, and feeding back the identification information includes:
sending the backup data to the host to be restored so that the host to be restored can restore the data according to the backup file;
and sending the service type instruction to the host to be recovered so that the host to be recovered feeds back the identification information according to the service type instruction.
Optionally, after the step of determining, when the data recovery instruction is received and when the data recovery instruction is received, the corresponding backup data and the host to be recovered according to the data recovery instruction, the method further includes:
determining the type of data recovery service according to the data recovery instruction;
generating a service type instruction according to the data recovery service type;
and sending the service type instruction to the host to be recovered.
Optionally, the step of sending the service type instruction to the host to be recovered to enable the host to be recovered to feed back the identification information according to the service type instruction includes:
when the service type instruction is a data recovery instruction, sending the data recovery instruction to the host to be recovered, so that the host to be recovered feeds back the identification information according to the data recovery instruction;
and when the service type instruction is a drilling recovery instruction, sending the drilling recovery instruction to the host to be recovered, so that the host to be recovered generates drilling identification information according to the drilling recovery instruction, and feeds back the identification information and the drilling identification information.
Optionally, when the identification information exists in another host associated with the service system, the step of determining that a host conflict exists in the service system includes:
when the identification information exists in other hosts associated with the business system, judging whether the target host with the identification information exists the drilling identification information or not;
when the target host has the drilling identification information, acquiring the running state of the target host;
and when the running state is a preset state, determining that the service system has host conflict.
Optionally, the step of obtaining the operating state of the target host when the drill identification information exists in the host includes:
sending an operating state query instruction to the target host to enable the target host to feed back a query result;
and determining the running state of the target host according to the query result.
Optionally, after the step of determining that the service system has a host conflict when the operating state is the preset state, the method further includes:
when the running state of the target host is a preset state, judging that the target host is a target conflict host;
and sending a shutdown instruction to the target conflict host to enable the target conflict host to execute shutdown operation.
In addition, to achieve the above object, the present invention further provides a host collision detection apparatus, including:
the device comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining corresponding backup data and a host to be recovered according to a data recovery instruction when the data recovery instruction is received, and the backup data comprises a backup file of a source host and identification information of the source host;
the sending module is used for sending the backup data to the host to be restored so as to enable the host to be restored to carry out data restoration according to the backup file and feed back the identification information;
the detection module is used for detecting whether the identification information exists in other hosts related to the service system;
and the judging module is used for judging that the business system has host conflict when the identification information exists in other hosts related to the business system.
In addition, to achieve the above object, the present invention further provides a host collision detection device, including: a memory, a processor and a host conflict detection program stored on the memory and executable on the processor, the host conflict detection program configured to implement the steps of the host conflict detection method as described above.
Furthermore, to achieve the above object, the present invention further provides a storage medium having a host collision detection program stored thereon, which when executed by a processor implements the steps of the host collision detection method as described above.
When a data recovery instruction is received, corresponding backup data and a host to be recovered are determined according to the data recovery instruction, wherein the backup data comprises a backup file of a source host and identification information of the source host; sending the backup data to a host to be restored so that the host to be restored performs data restoration according to the backup file and feeds back identification information; detecting whether other hosts associated with the service system have the same identification information; and when the same identification information exists in other hosts related to the service system, judging that the service system has host conflict. By the mode, after the host to be recovered recovers data according to the backup data, the identification information of the host is fed back, so that the host with the identification information is obtained, whether the host with the identification information conflicts with the source host is judged, and the purpose of detecting whether the host conflicts exist is achieved.
Drawings
Fig. 1 is a schematic structural diagram of a host conflict detection device of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a host collision detection method according to a first embodiment of the present invention;
FIG. 3 is a flowchart illustrating a host collision detection method according to a second embodiment of the present invention;
fig. 4 is a block diagram of a first embodiment of a host collision detection apparatus according to the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic structural diagram of a host conflict detection device in a hardware operating environment according to an embodiment of the present invention.
As shown in fig. 1, the host collision detection device may include: a processor 1001, such as a Central Processing Unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a WIreless interface (e.g., a WIreless-FIdelity (WI-FI) interface). The Memory 1005 may be a Random Access Memory (RAM) Memory, or may be a Non-Volatile Memory (NVM), such as a disk Memory. The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the configuration shown in fig. 1 does not constitute a limitation of the host collision detection device and may include more or fewer components than shown, or some components in combination, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a storage medium, may include therein an operating system, a network communication module, a user interface module, and a host collision detection program.
In the host collision detection apparatus shown in fig. 1, the network interface 1004 is mainly used for data communication with a network server; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 of the host collision detection device of the present invention may be disposed in the host collision detection device, and the host collision detection device calls the host collision detection program stored in the memory 1005 through the processor 1001 and executes the host collision detection method provided by the embodiment of the present invention.
An embodiment of the present invention provides a host collision detection method, and referring to fig. 2, fig. 2 is a flowchart illustrating a first embodiment of a host collision detection method according to the present invention.
In this embodiment, the host collision detection method includes the following steps:
step S10: when a data recovery instruction is received, corresponding backup data and a host to be recovered are determined according to the data recovery instruction, wherein the backup data comprises a backup file of a source host and identification information of the source host.
It should be noted that the main execution body of this embodiment is a backup server, the backup server establishes communication connections with all hosts associated in the service system, and the backup server is further configured to store backup files that need to be backed up in the source host, and may send the backup files to the corresponding hosts for data recovery.
It is understood that each host in the business system has a unique identifier, the unique identifier may be generated by a client installed on the host, the host sends the identifier to the backup server after connecting with the backup server, the backup server distinguishes and identifies different hosts through the identifier, the identifier may be in the form of a random permutation and combination of numbers, letters and symbols, for example, the identifier may be F3EA6B9E-C17D-45F1-AC6D-355C5C5080C4, and this embodiment is not limited. According to the operating systems of different hosts, the identifier may be stored in a corresponding location, for example, when the operating system of the host is Windows, the identifier may be stored in a C:/hot file, and when the operating system of the host is linux, the identifier may be stored in an/etc/hot file, which is not limited in this embodiment.
It is easy to understand that, when receiving a data recovery instruction, the backup server needs to send backup data to the host to be recovered for data recovery, where the backup data includes a backup file that needs to be backed up by the source host and identification information of the source host, and the identification information includes the unique identifier.
Further, after step S10, the method further includes: determining the type of data recovery service according to the data recovery instruction;
generating a service type instruction according to the data recovery service type;
and sending the service type instruction to the host to be recovered.
It should be noted that, the data recovery of the service system host (i.e. source host) includes multiple service types, and firstly, when the service system host fails, the backup file backed up by the service system host in advance needs to be recovered to other hosts; secondly, the service system host is in a normal state, but it needs to detect whether the backup data of the service system host can be normally recovered, i.e. performing the drill recovery, so that the subsequent operation steps need to be performed according to different data recovery service types.
It can be understood that the data recovery instruction includes a service type set by a network administrator, and the backup server generates a corresponding service type instruction according to the service type in the data recovery instruction, and then sends the service type instruction to the host to be recovered.
Step S20: and sending the backup data to the host to be restored so that the host to be restored performs data restoration according to the backup file and feeds back the identification information.
It can be understood that, after the backup data is sent to the host to be restored, the host to be restored performs data restoration according to the backup data, where the backup data includes the identification information of the source host, and the identification information of the source host also exists on the host to be restored.
In a specific implementation, after the host to be restored completes data restoration according to the backup data, the host to be restored sends the identification information of the source host to the backup server, and the backup server can know that the data restoration of the host to be restored is completed after receiving the identification information sent by the host to be restored.
Further, step S20 includes: sending the backup data to the host to be restored so that the host to be restored can restore the data according to the backup file;
and sending the service type instruction to the host to be recovered so that the host to be recovered feeds back the identification information according to the service type instruction.
It can be understood that the backup server sends the backup file to the host to be restored and sends the service type instruction to the host to be restored, and the host to be restored performs data restoration according to the backup file in the backup data and feeds back the corresponding identification information according to the service type instruction.
Further, the step of sending a service type instruction to the host to be recovered so that the host to be recovered feeds back the identification information according to the service type instruction includes:
when the service type instruction is a data recovery instruction, sending the data recovery instruction to the host to be recovered, so that the host to be recovered feeds back the identification information according to the data recovery instruction;
and when the service type instruction is a drilling recovery instruction, sending the drilling recovery instruction to the host to be recovered, so that the host to be recovered generates drilling identification information according to the drilling recovery instruction, and feeds back the identification information and the drilling identification information.
It should be noted that, when the host of the service system cannot operate normally and needs to perform a normal data recovery service, the backup server generates backup data from the backup file and the identification information backed up by the source host in advance and sends the backup data to the host to be recovered, and after the host to be recovered performs data recovery according to the backup data, the identification information of the source host may exist on the host to be recovered.
It can be understood that, when the service system host can operate normally, but data recovery drilling needs to be performed to detect feasibility of data recovery of the service system under the abnormal condition of the service system host, at this time, the backup server generates a recovery drilling instruction and sends the recovery drilling instruction to the host to be recovered, after the host to be recovered performs data recovery according to the backup data, the host to be recovered has identification information of the service system host, and after the host to be recovered receives the recovery drilling instruction, the client on the host to be recovered generates drilling identification information.
Step S30: and detecting whether other hosts associated with the service system have the identification information.
It should be understood that the host having the identification information in the service system may be determined according to the identification information fed back by the host to be restored, or the backup system may send an identification obtaining instruction to other hosts before the source host is ready to start, and after the other hosts receive the identification obtaining instruction, all the identification information existing on the host may be fed back, so that the backup server may know which hosts perform data restoration according to the backup data of the source host.
Step S40: and when the identification information exists in other hosts associated with the service system, judging that the service system has host conflict.
It should be noted that the source host is generally in a shutdown state when the host to be recovered performs data recovery, and when identification information of the source host exists in other associated hosts in the service system, if the hosts are in an on state, host conflicts, such as IP conflicts, may occur after the source host is powered on. For example: the IP address of the source host is 10.35.92.11, the backup data includes network configurations such as the IP address, the network configuration of the host to be backed up is the same as that of the source host according to the backup data, the IP address of the host to be restored is 10.35.92.11 at this time, and if the host to be restored is not powered off, the source host collides with the host to be restored after being powered on, thereby affecting normal service of the source host.
In a specific implementation, when the host operates normally, the client on the host may send state information of the host to the backup server to inform the backup server whether the host is in the power-on state, and after the host to be restored sends the identification information to the backup server, the backup server may know whether the host to be restored is in the power-on state according to the client on the host to be restored that sent the identification information. When the host to be recovered is in the boot state, it indicates that the host to be recovered and the source host will generate a host conflict.
In this embodiment, when a data recovery instruction is received, corresponding backup data and a host to be recovered are determined according to the data recovery instruction, where the backup data includes a backup file of a source host and identification information of the source host; sending the backup data to a host to be restored so that the host to be restored performs data restoration according to the backup file and feeds back identification information; detecting whether other hosts associated with the service system have identification information or not; and when the identification information exists in other hosts associated with the service system, judging that the service system has host conflict. By the mode, after the host to be recovered performs data recovery according to the backup data, the host with the identification information is fed back to obtain the identification information of the host, when in disaster tolerance drilling, whether the drilling identification information exists on the host to be recovered is judged, and whether the host conflicts with the source host or not is judged according to the identification information and the drilling identification information, so that the purpose of detecting whether the host conflicts exist in the service system or not is achieved.
Referring to fig. 3, fig. 3 is a flowchart illustrating a host collision detection method according to a second embodiment of the present invention.
Based on the first embodiment, in step S40, the host collision detection method in this embodiment includes:
step S41: and when the identification information exists in other hosts associated with the service system, judging whether the target host with the identification information exists the drilling identification information or not.
It should be noted that, when the host having the identification information in the service system is in a power-on state, the host is a target host, and it needs to detect whether the target host has the drilling identification, and the target host is provided with a client, and the client can autonomously detect whether the host has the drilling identification information and then feed back the drilling identification information to the backup server, or feed back the drilling identification information when receiving a drilling identification query instruction from the backup server.
Step S42: and when the target host has the drilling identification information, acquiring the running state of the target host.
It can be understood that, when the drilling identification information exists on the target host, it indicates that this data recovery is for the drilling test, and the source host can operate normally, so if the target host with the drilling identification information continues to keep the on state, after the source host is turned on, the target host may generate host conflict with the source host, and interrupt the service of the source host. At this time, the operating state of the target host needs to be acquired, so that whether a host conflict exists in the service system is judged.
Further, step S42 includes: sending an operating state query instruction to the target host to enable the target host to feed back a query result;
and determining the running state of the target host according to the query result.
It should be noted that the backup server needs to send an operation status query instruction to the target host, the target host feeds back a query result according to the instruction after receiving the operation status query instruction, the query result is a successful query when the target host is in the on state, the host cannot feed back according to the instruction when the host is in the off state, and the query result is a failed query after a preset time, for example, after 5 seconds and 10 seconds. The backup server may determine the operational status of the host according to the query result.
Step S43: and when the running state is a preset state, determining that the service system has host conflict.
It can be understood that, when the operation status of the target host is a preset status, that is, when the target host is in a normal on status, it indicates that the target host and the source host may generate a host conflict, thereby affecting the service progress of the source host.
Further, after step S43, the method further includes: when the running state of the target host is a preset state, judging that the target host is a target conflict host;
and sending a shutdown instruction to the target conflict host to enable the target conflict host to execute shutdown operation.
It can be understood that, when the operation status of the target host is a preset status, i.e. when the target host is in a normal on status, then the target host is a target conflicting host and needs to be further processed so as not to affect the service of the source host.
It should be appreciated that the backup server needs to send a shutdown command to the target conflicting host to avoid the target conflicting host from generating a host conflict with the source host.
It should be noted that, in general, when performing the drilling recovery, the original service system host is first turned off, and then the drilling recovery is performed, if the source host is forgotten to be turned off before the drilling to cause host conflict, the backup server will notify the drilling host (i.e. the target conflicting host) to turn off after detecting the host conflict, so that service interruption is not caused. If the individual drilling host is forgotten to be closed after drilling is finished and host conflict occurs after the original service system host is started, the backup server informs the client which is not closed to execute shutdown operation, so that the original service system is prevented from being influenced.
In this embodiment, when the identification information exists in other hosts associated with the service system, it is determined whether the target host having the identification information exists the drilling identification information; when the target host has the drilling identification information, acquiring the running state of the target host; and when the running state is a preset state, determining that the service system has host conflict. By the method, after the drilling data of the service system is recovered, the host with the identification information and the drilling identification information is used as the target host, the target host in the running state is used as the target conflict host, and the shutdown instruction is sent to the target conflict host, so that the host conflict generated after the source host is started is avoided.
In addition, an embodiment of the present invention further provides a storage medium, where a host conflict detection program is stored on the storage medium, and when executed by a processor, the host conflict detection program implements the steps of the host conflict detection method described above.
Referring to fig. 4, fig. 4 is a block diagram illustrating a first embodiment of a host collision detection apparatus according to the present invention.
As shown in fig. 4, the apparatus for detecting a host collision according to an embodiment of the present invention includes:
the determining module 10 is configured to determine, when a data recovery instruction is received, corresponding backup data and a host to be recovered according to the data recovery instruction, where the backup data includes a backup file of a source host and identification information of the source host;
a sending module 20, configured to send the backup data to the host to be restored, so that the host to be restored performs data restoration according to the backup file, and feeds back the identification information;
a detection module 30, configured to detect whether the identification information exists in other hosts associated with the service system;
a determining module 40, configured to determine that a host conflict exists in the service system when the identification information exists in other hosts associated with the service system.
In an embodiment, the sending module 20 is further configured to send the backup data to the host to be restored, so that the host to be restored performs data restoration according to the backup file;
and sending the service type instruction to the host to be recovered so that the host to be recovered feeds back the identification information according to the service type instruction.
In an embodiment, the determining module 10 is further configured to determine a data recovery service type according to the data recovery instruction;
generating a service type instruction according to the data recovery service type;
and sending the service type instruction to the host to be recovered.
In an embodiment, the sending module 20 is further configured to send the data recovery instruction to the host to be recovered when the service type instruction is a data recovery instruction, so that the host to be recovered feeds back the identification information according to the data recovery instruction;
and when the service type instruction is a drilling recovery instruction, sending the drilling recovery instruction to the host to be recovered, so that the host to be recovered generates drilling identification information according to the drilling recovery instruction, and feeds back the identification information and the drilling identification information.
In an embodiment, the determining module 40 is further configured to determine whether the target host having the identification information has the drilling identification information when the identification information exists in other hosts associated with the service system;
when the target host has the drilling identification information, acquiring the running state of the target host;
and when the running state is a preset state, determining that the service system has host conflict.
In an embodiment, the determining module 40 is further configured to send an operation status query instruction to the target host, so that the target host feeds back a query result;
and determining the running state of the target host according to the query result.
In an embodiment, the determining module 40 is further configured to determine that the target host is a target conflicting host when the operating state of the target host is a preset state;
and sending a shutdown instruction to the target conflict host to enable the target conflict host to execute shutdown operation.
It should be understood that the above is only an example, and the technical solution of the present invention is not limited in any way, and in a specific application, a person skilled in the art may set the technical solution as needed, and the present invention is not limited thereto.
In this embodiment, when a data recovery instruction is received, corresponding backup data and a host to be recovered are determined according to the data recovery instruction, where the backup data includes a backup file of a source host and identification information of the source host; sending the backup data to a host to be restored so that the host to be restored performs data restoration according to the backup file and feeds back identification information; detecting whether other hosts associated with the service system have the same identification information; and when the same identification information exists in other hosts associated with the service system, judging that the service system has host conflict. By the mode, after the host to be recovered recovers data according to the backup data, the identification information of the host is fed back, so that the host with the identification information is obtained, whether the host with the identification information conflicts with the source host is judged, and the purpose of detecting whether the host conflicts exist is achieved.
It should be noted that the above-described work flows are only exemplary, and do not limit the scope of the present invention, and in practical applications, a person skilled in the art may select some or all of them to achieve the purpose of the solution of the embodiment according to actual needs, and the present invention is not limited herein.
In addition, the technical details that are not described in detail in this embodiment may refer to the host conflict detection method provided in any embodiment of the present invention, and are not described herein again.
Further, it is to be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (e.g. Read Only Memory (ROM)/RAM, magnetic disk, optical disk), and includes several instructions for enabling a terminal device (e.g. a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A host collision detection method, characterized in that the host collision detection method comprises:
when a data recovery instruction is received, determining corresponding backup data and a host to be recovered according to the data recovery instruction, wherein the backup data comprises a backup file of a source host and identification information of the source host;
sending the backup data to the host to be restored so that the host to be restored performs data restoration according to the backup file and feeds back the identification information;
detecting whether other hosts related to the service system have the identification information or not;
and when the identification information exists in other hosts associated with the service system, judging that the service system has host conflict.
2. The method according to claim 1, wherein the step of sending the backup data to the host to be restored to enable the host to be restored to perform data restoration according to the backup file and feed back the identification information includes:
sending the backup data to the host to be restored so that the host to be restored can restore the data according to the backup file;
and sending the service type instruction to the host to be recovered so that the host to be recovered feeds back the identification information according to the service type instruction.
3. The method according to claim 2, wherein after the step of determining the corresponding backup data and the host to be restored according to the data restoration instruction when receiving the data restoration instruction, the method further comprises:
determining the type of data recovery service according to the data recovery instruction;
generating a service type instruction according to the data recovery service type;
and sending the service type instruction to the host to be recovered.
4. The method according to claim 2, wherein the step of sending the service type instruction to the host to be recovered so that the host to be recovered feeds back the identification information according to the service type instruction comprises:
when the service type instruction is a data recovery instruction, sending the data recovery instruction to the host to be recovered, so that the host to be recovered feeds back the identification information according to the data recovery instruction;
and when the service type instruction is a drilling recovery instruction, sending the drilling recovery instruction to the host to be recovered, so that the host to be recovered generates drilling identification information according to the drilling recovery instruction, and feeds back the identification information and the drilling identification information.
5. The method of claim 4, wherein said step of determining that a host conflict exists with the business system when the identification information exists in other hosts associated with the business system comprises:
when the identification information exists in other hosts associated with the business system, judging whether the target host with the identification information exists the drilling identification information or not;
when the target host has the drilling identification information, acquiring the running state of the target host;
and when the running state is a preset state, determining that the service system has host conflict.
6. The method of claim 5, wherein the step of obtaining the operating status of the target host when the drill identification information exists in the host comprises:
sending an operating state query instruction to the target host to enable the target host to feed back a query result;
and determining the running state of the target host according to the query result.
7. The method of claim 5, wherein after the step of determining that there is a host conflict in the service system when the operation status is a preset status, the method further comprises:
when the running state of the target host is a preset state, judging that the target host is a target conflict host;
and sending a shutdown instruction to the target conflict host to enable the target conflict host to execute shutdown operation.
8. A host collision detection apparatus, characterized in that the host collision detection apparatus comprises:
the device comprises a determining module, a judging module and a judging module, wherein the determining module is used for determining corresponding backup data and a host to be recovered according to a data recovery instruction when the data recovery instruction is received, and the backup data comprises a backup file of a source host and identification information of the source host;
the sending module is used for sending the backup data to the host to be restored so as to enable the host to be restored to carry out data restoration according to the backup file and feed back the identification information;
the detection module is used for detecting whether the identification information exists in other hosts related to the service system;
and the judging module is used for judging that the business system has host conflict when the identification information exists in other hosts related to the business system.
9. A host collision detection device, characterized in that the device comprises: memory, a processor and a host collision detection program stored on the memory and executable on the processor, the host collision detection program being configured to implement the steps of the host collision detection method according to any of claims 1 to 7.
10. A storage medium having stored thereon a host collision detection program which, when executed by a processor, implements the steps of the host collision detection method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110471323.9A CN112882871B (en) | 2021-04-29 | 2021-04-29 | Host conflict detection method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110471323.9A CN112882871B (en) | 2021-04-29 | 2021-04-29 | Host conflict detection method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112882871A true CN112882871A (en) | 2021-06-01 |
| CN112882871B CN112882871B (en) | 2021-08-24 |
Family
ID=76040197
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110471323.9A Active CN112882871B (en) | 2021-04-29 | 2021-04-29 | Host conflict detection method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112882871B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116560908A (en) * | 2023-05-09 | 2023-08-08 | 中工数保(北京)科技有限公司 | Data recovery method of industrial control system and related equipment thereof |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101977245A (en) * | 2010-01-07 | 2011-02-16 | 中兴通讯股份有限公司 | Method, network equipment and system for detecting IP (Internet Protocol) address conflict |
| CN102761428A (en) * | 2011-04-27 | 2012-10-31 | 鸿富锦精密工业（深圳）有限公司 | Server system and server switching method |
| US20150095691A1 (en) * | 2010-09-30 | 2015-04-02 | Axcient, Inc. | Cloud-Based Virtual Machines and Offices |
| CN104780068A (en) * | 2015-04-15 | 2015-07-15 | 中国工商银行股份有限公司 | Network switching method, device and system for machine room migration |
| CN107992381A (en) * | 2017-12-11 | 2018-05-04 | 深圳市科力锐科技有限公司 | System reducing method, device, system, backup and reduction server and storage medium |
| CN108039969A (en) * | 2017-12-13 | 2018-05-15 | 深圳市科力锐科技有限公司 | Network method of automatic configuration, device, system, storage medium and object-computer |
| CN110377400A (en) * | 2019-07-22 | 2019-10-25 | 深信服科技股份有限公司 | A kind of virtual machine restoration methods, equipment, system and medium |
| CN111143114A (en) * | 2018-11-02 | 2020-05-12 | 深信服科技股份有限公司 | Virtualization platform disaster tolerance method, system, server and storage medium |
| CN111385377A (en) * | 2020-03-03 | 2020-07-07 | 深信服科技股份有限公司 | IP address conflict processing method, equipment and storage medium |
| CN111581019A (en) * | 2020-04-21 | 2020-08-25 | 苏州浪潮智能科技有限公司 | Test method and device for storage fault recovery |
-
2021
- 2021-04-29 CN CN202110471323.9A patent/CN112882871B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101977245A (en) * | 2010-01-07 | 2011-02-16 | 中兴通讯股份有限公司 | Method, network equipment and system for detecting IP (Internet Protocol) address conflict |
| US20150095691A1 (en) * | 2010-09-30 | 2015-04-02 | Axcient, Inc. | Cloud-Based Virtual Machines and Offices |
| CN102761428A (en) * | 2011-04-27 | 2012-10-31 | 鸿富锦精密工业（深圳）有限公司 | Server system and server switching method |
| CN104780068A (en) * | 2015-04-15 | 2015-07-15 | 中国工商银行股份有限公司 | Network switching method, device and system for machine room migration |
| CN107992381A (en) * | 2017-12-11 | 2018-05-04 | 深圳市科力锐科技有限公司 | System reducing method, device, system, backup and reduction server and storage medium |
| CN108039969A (en) * | 2017-12-13 | 2018-05-15 | 深圳市科力锐科技有限公司 | Network method of automatic configuration, device, system, storage medium and object-computer |
| CN111143114A (en) * | 2018-11-02 | 2020-05-12 | 深信服科技股份有限公司 | Virtualization platform disaster tolerance method, system, server and storage medium |
| CN110377400A (en) * | 2019-07-22 | 2019-10-25 | 深信服科技股份有限公司 | A kind of virtual machine restoration methods, equipment, system and medium |
| CN111385377A (en) * | 2020-03-03 | 2020-07-07 | 深信服科技股份有限公司 | IP address conflict processing method, equipment and storage medium |
| CN111581019A (en) * | 2020-04-21 | 2020-08-25 | 苏州浪潮智能科技有限公司 | Test method and device for storage fault recovery |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116560908A (en) * | 2023-05-09 | 2023-08-08 | 中工数保(北京)科技有限公司 | Data recovery method of industrial control system and related equipment thereof |
| CN116560908B (en) * | 2023-05-09 | 2024-01-26 | 中工数保(北京)科技有限公司 | Data recovery method of industrial control system and related equipment thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112882871B (en) | 2021-08-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9146839B2 (en) | Method for pre-testing software compatibility and system thereof | |
| US20160132420A1 (en) | Backup method, pre-testing method for environment updating and system thereof | |
| US20040117414A1 (en) | Method and system for automatically updating operating systems | |
| CN110838953B (en) | Test method, test system, electronic equipment and storage medium | |
| CN109144776B (en) | Virtual machine image file processing method and device | |
| CN110825399A (en) | Deployment method and device of application program | |
| KR20040047209A (en) | Method for automatically recovering computer system in network and recovering system for realizing the same | |
| CN111352779A (en) | On-off test method of AC power supply of MOC card and related assembly | |
| CN112882871B (en) | Host conflict detection method, device, equipment and storage medium | |
| CN110597662B (en) | Backup data automatic verification method and device, user equipment and storage medium | |
| CN114238255A (en) | Method and device for synchronizing files, electronic equipment and computer readable storage medium | |
| CN111698558A (en) | Television software upgrading method, television terminal and computer readable storage medium | |
| CN113438292A (en) | Agent deployment method and device based on automatic operation and maintenance tool | |
| CN113485755B (en) | Device driver verification method, device and storage medium | |
| CN112579359B (en) | Service system reconstruction method, device, equipment and storage medium | |
| CN105550071A (en) | System file upgrading and detecting method and communication device | |
| CN106911508B (en) | DNS configuration recovery method and device | |
| CN112579361A (en) | Backup data reconstruction method, device, equipment and storage medium | |
| CN109257235B (en) | Network anomaly recovery method, device, equipment and computer readable storage medium | |
| CN110597520A (en) | Server, deployment method thereof and computer-readable storage medium | |
| KR102221593B1 (en) | System for maintaining the installation envoronment of computer terminals | |
| CN112711430B (en) | ADB-based non-network equipment upgrading method, system and readable storage medium | |
| CN110737546B (en) | Consistency snapshot checking method, device, equipment and storage medium | |
| CN112883349B (en) | Data recovery method, device, equipment and storage medium | |
| CN112579358B (en) | Backup point detection method, device, equipment and storage medium |
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 |