CN116149802B - Data pushing method, device, storage medium and apparatus - Google Patents
Data pushing method, device, storage medium and apparatus Download PDFInfo
- Publication number
- CN116149802B CN116149802B CN202310425180.7A CN202310425180A CN116149802B CN 116149802 B CN116149802 B CN 116149802B CN 202310425180 A CN202310425180 A CN 202310425180A CN 116149802 B CN116149802 B CN 116149802B
- Authority
- CN
- China
- Prior art keywords
- hardware configuration
- virtual machine
- target virtual
- target
- preset
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a data pushing method, equipment, a storage medium and a device, wherein when a data pushing instruction is received, whether second hardware configuration information corresponding to a target virtual machine meets preset configuration conditions or not is detected; when the second hardware configuration information does not meet the preset configuration conditions, modifying the second hardware configuration information according to the target hardware configuration parameters corresponding to the target virtual machine; and pushing the data to be pushed to the target virtual machine when the second hardware configuration information meets the preset configuration conditions. Because the hardware configuration information of the target virtual machine in the data pushing stage is dynamically adjusted, the hardware configuration of the target virtual machine meets the preset configuration conditions required by data pushing, compared with the prior art, which has low disaster recovery efficiency due to unnecessary occupation of resources of the target virtual platform, the method and the device can reduce unnecessary occupation of resources of the target virtual platform in the data pushing stage of disaster recovery, and improve disaster recovery efficiency.
Description
Technical Field
The present invention relates to the field of data disaster recovery technologies, and in particular, to a data pushing method, device, storage medium, and apparatus.
Background
When disaster recovery is performed on the computer system (data), since the resources of the target virtualization platform are limited, and the target virtual machine is started to occupy the memory resources and the CPU resources of the target virtualization platform, once the resources of the target virtualization platform reach the bottleneck, the target virtual machine cannot be started, and disaster recovery cannot be performed.
In the prior art, hardware configuration parameters consistent with the source machine are generally used when the virtual machine is created, the data is not changed in the subsequent data pushing stage and the switching stage, and then the target virtual machine is started to push the data. Such as: if the available memory of the target virtualization platform is 64GB, the total number of available CPU cores is 64 cores, and the source machines are 8-core 8GB service systems, only 8 source machines can be simultaneously involved in the data pushing stage according to the scheme, so that unnecessary resources of the target virtualization platform are occupied, and the disaster recovery efficiency is low.
The foregoing is provided merely for the purpose of facilitating understanding of the technical solutions of the present invention and is not intended to represent an admission that the foregoing is prior art.
Disclosure of Invention
The invention mainly aims to provide a data pushing method, equipment, a storage medium and a device, and aims to solve the technical problem of low disaster recovery efficiency in the prior art due to unnecessary occupation of resources of a target virtualization platform.
In order to achieve the above object, the present invention provides a data pushing method, which includes the following steps:
constructing a target virtual machine according to first hardware configuration information corresponding to the disaster recovery source machine;
when a data pushing instruction is received, detecting whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions or not;
when the second hardware configuration information does not meet the preset configuration conditions, modifying the second hardware configuration information according to the target hardware configuration parameters of the target virtual machine so that the second hardware configuration information meets the preset configuration conditions;
and pushing the data to be pushed to the target virtual machine when the second hardware configuration information meets the preset configuration conditions.
Optionally, the step of constructing the target virtual machine according to the first hardware configuration information corresponding to the disaster recovery source machine includes:
acquiring first hardware configuration information corresponding to a disaster recovery source machine;
determining target hardware configuration parameters required by a target virtual machine in a data pushing stage according to the first hardware configuration information of the disaster recovery source machine;
and calling an API interface of the target virtualization platform according to the target hardware configuration parameters of the target virtual machine to construct the target virtual machine.
Optionally, the step of determining, according to the first hardware configuration information, a target hardware configuration parameter required by a target virtual machine in the data push stage includes:
determining preset hardware configuration parameters required by a target virtual machine in a data pushing stage according to disk information in the first hardware configuration information;
and if the preset hardware configuration parameter is larger than the actual hardware configuration parameter corresponding to the disaster recovery source machine, taking the actual hardware configuration parameter as a target hardware configuration parameter.
Optionally, when receiving the data pushing instruction, the step of detecting whether the second hardware configuration information corresponding to the target virtual machine meets a preset configuration condition includes:
when a data pushing instruction is received, acquiring a second hardware configuration parameter of the target virtual machine;
comparing the second hardware configuration parameters with the target hardware configuration parameters of the target virtual machine, and judging whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions or not according to comparison results;
after the step of detecting whether the second hardware configuration information corresponding to the target virtual machine meets the preset configuration condition when the data pushing instruction is received, the method further comprises the following steps:
And when the second hardware configuration information does not meet the preset configuration conditions, modifying the second hardware configuration parameters into preset hardware configuration parameters.
Optionally, the step of determining whether the second hardware configuration information corresponding to the target virtual machine meets the preset configuration condition according to the comparison result includes:
and when the second hardware configuration parameters are different from the target hardware configuration parameters, judging that the second hardware configuration information does not meet the preset configuration conditions.
Optionally, after the step of pushing the data to be pushed to the target virtual machine when the second hardware configuration information meets the preset configuration condition, the method includes:
when a service system switching instruction is received, operating system deployment is carried out on the target virtual machine according to hardware equipment information corresponding to the disaster recovery source machine, and the target virtual machine is configured according to first hardware configuration information of the disaster recovery source machine.
Optionally, when receiving a service system switching instruction, performing operating system deployment on the target virtual machine according to hardware device information corresponding to the disaster recovery source machine, and configuring the target virtual machine according to first hardware configuration information of the disaster recovery source machine, where the method includes:
When a service system switching instruction is received, acquiring hardware equipment information corresponding to the disaster recovery source machine;
searching a driver corresponding to a target operating system from a preset driver library according to the hardware equipment information;
and deploying the driver to an operating system of the target virtual machine, and configuring the target virtual machine according to the first hardware configuration information of the disaster recovery source machine.
In addition, in order to achieve the above object, the present invention also proposes a data pushing device comprising a memory, a processor and a data pushing program stored on the memory and executable on the processor, the data pushing program being configured to implement the steps of data pushing as described above.
In addition, in order to achieve the above object, the present invention also proposes a storage medium having stored thereon a data push program which, when executed by a processor, implements the steps of the data push method as described above.
In addition, to achieve the above object, the present invention also proposes a data pushing apparatus, including:
the virtual machine construction module is used for constructing a target virtual machine according to the first hardware configuration information corresponding to the disaster recovery source machine;
The configuration adjustment module is used for detecting whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions or not when a data pushing instruction is received;
the configuration adjustment module is further configured to modify the second hardware configuration information according to a target hardware configuration parameter of the target virtual machine when the second hardware configuration information does not meet the preset configuration condition, so that the second hardware configuration information meets the preset configuration condition;
and the data pushing module is used for pushing the data to be pushed to the target virtual machine when the second hardware configuration information meets the preset configuration condition.
According to the method, a target virtual machine is constructed according to first hardware configuration information corresponding to a disaster recovery source machine, and when a data pushing instruction is received, whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions is detected; when the second hardware configuration information does not meet the preset configuration conditions, modifying the second hardware configuration information according to the target hardware configuration parameters so as to enable the second hardware configuration information to meet the preset configuration conditions; and pushing the data to be pushed to the target virtual machine when the second hardware configuration information meets the preset configuration conditions. Compared with the prior art, which has low disaster recovery efficiency due to unnecessary occupation of resources of the target virtualization platform, the method can reduce unnecessary occupation of resources of the target virtualization platform in the data pushing stage of disaster recovery by dynamically adjusting the hardware configuration information of the target virtual machine, allow more disaster recovery tasks to be performed simultaneously and improve the disaster recovery efficiency.
Drawings
FIG. 1 is a schematic diagram of a data pushing device of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart of a data pushing method according to a first embodiment of the present invention;
FIG. 3 is a flowchart illustrating a data pushing method according to a second embodiment of the present invention;
FIG. 4 is a flowchart illustrating a third embodiment of a data pushing method according to the present invention;
FIG. 5 is a flowchart illustrating a third embodiment of a data pushing method according to the present invention;
fig. 6 is a block diagram of a first embodiment of a data pushing device according to the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
Referring to fig. 1, fig. 1 is a schematic diagram of a data pushing device of a hardware running environment according to an embodiment of the present invention.
As shown in fig. 1, the data pushing device may include: a processor 1001, such as a central processing unit (Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, a memory 1005. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display (Display), and the optional user interface 1003 may also include a standard wired interface, a wireless interface, and the wired interface for the user interface 1003 may be a USB interface in the present invention. 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 high-speed random access Memory (Random Access Memory, RAM) or a stable Memory (NVM), such as a disk Memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.
Those skilled in the art will appreciate that the structure shown in fig. 1 does not constitute a limitation of the data pushing device and may include more or fewer components than shown, or may combine certain components, or may be arranged in a different arrangement of components.
As shown in fig. 1, an operating system, a network communication module, a user interface module, and a data push program may be included in a memory 1005, which is considered to be a type of computer storage medium.
In the data pushing device shown in fig. 1, the network interface 1004 is mainly used for connecting to a background server, and performing data communication with the background server; the user interface 1003 is mainly used for connecting user equipment; the data pushing device invokes a data pushing program stored in the memory 1005 through the processor 1001, and executes the data pushing method provided by the embodiment of the present invention.
Based on the above hardware structure, an embodiment of the data pushing method of the present invention is provided.
Referring to fig. 2, fig. 2 is a flowchart of a first embodiment of a data pushing method according to the present invention, and the first embodiment of the data pushing method according to the present invention is provided.
In this embodiment, the data pushing method includes the following steps:
step S10: and constructing a target virtual machine according to the first hardware configuration information corresponding to the disaster recovery source machine.
It should be noted that, in this embodiment, the execution body may be a disaster recovery integrated machine connected to the source machine and the target virtualization platform, where the disaster recovery integrated machine may be a device with a data pushing function, and the disaster recovery source machine may refer to a protected computer device (data transmission end), where the device is as follows: the virtual platform may be a computer and its matched equipment used in the information and system science related engineering and technology field, where the target virtual machine may be used as a data receiving end to receive data sent by the source machine, so as to implement data synchronization operation, and the target virtual machine may refer to a host running on the virtual platform, which is not limited in this embodiment. This embodiment and the following embodiments will be described by taking the disaster recovery integrated machine as an example.
It can be understood that the first hardware configuration information may refer to hardware configuration parameters corresponding to the disaster recovery source machine, where the hardware configuration parameters include a total number of cores of the CPU, a memory size, disk information, network card information, and the like.
It should be understood that, in order to ensure that the problem of occupation of unnecessary resources of the virtualized platform is reduced when the virtual machine is constructed, the hardware configuration parameters required for constructing the target virtual machine are determined by analyzing the first hardware configuration information of the disaster recovery source machine, the virtual machine is created on the target virtualized platform according to the hardware configuration parameters, and then a startup instruction is executed on the target machine, so that normal use of the constructed virtual machine is ensured.
Step S20: and when a data pushing instruction is received, detecting whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions or not.
It should be noted that, the data pushing instruction may be an instruction generated by a source machine, or may be an instruction fed back by a virtualization platform, for example: the instruction may be a preset data pushing instruction generated according to a pushing time period, or may be a data pushing instruction generated according to a pushing data flow, or may be an instruction fed back when the virtualization platform receives that the pushed data amount reaches a preset threshold, which is not limited in the present application.
It can be understood that the second hardware configuration information may refer to real-time hardware configuration information of the target virtual machine before the data synchronization operation is performed, that is, the second hardware configuration information is hardware configuration information corresponding to the target virtual machine after the virtual machine is built based on the disaster recovery source machine first hardware configuration information. The second hardware configuration information comprises the memory size and the total number of cores of the CPU, namely, the lowest hardware configuration required by the target virtual machine in the push data module is calculated according to the hardware configuration parameters of the source machine, and then an interface of the target virtual platform is called to create the target virtual machine according to the lowest configuration. In order to avoid the change of the second hardware configuration information corresponding to the target virtual machine caused by human factors, so that unnecessary resources are occupied due to the fact that the second hardware configuration information corresponding to the target virtual machine is not operated according to preset configuration conditions, whether the second hardware configuration information corresponding to the target virtual machine meets the preset configuration conditions or not needs to be detected before data synchronization.
It should be understood that the preset configuration condition may be a preset minimum hardware configuration condition required by the target virtual machine in the data pushing stage, where the minimum hardware configuration condition refers to a configuration condition that the virtual machine satisfies data pushing when performing data synchronization, so that the problem of invalid resource occupation in the data pushing stage can be avoided.
In a specific implementation, before pushing data, detecting whether the hardware configuration of the target virtual machine is the lowest configuration, if so, starting to push the data to the target virtual machine.
Step S30: and when the second hardware configuration information does not meet the preset configuration conditions, modifying the second hardware configuration information according to the target hardware configuration parameters of the target virtual machine so that the second hardware configuration information meets the preset configuration conditions.
It should be noted that, before pushing data, it is detected whether the hardware configuration of the target virtual machine is the lowest configuration, if not, the target hardware configuration parameters required by the target virtual machine in the data pushing stage are determined according to the first hardware configuration information, and the current second hardware configuration information corresponding to the target virtual machine is modified according to the configuration parameters required by the virtual machine in the data pushing stage, so that the second hardware configuration information meets the lowest configuration conditions required in the data pushing stage.
In a specific implementation, pushing data means pushing disk data of a source machine to a target machine, so that the target machine data is consistent with the source machine data, thereby achieving the purpose of disaster recovery, one disaster recovery task can push the data for many times, and the target virtual machine can use the lowest hardware configuration parameters in the data pushing stage, thereby reducing the occupation of resources of a virtualization platform, improving the disaster recovery efficiency, and before each data pushing, detecting whether second hardware configuration information of the target virtual machine meets preset configuration conditions or not, and if the current configuration of the target virtual machine is the lowest hardware configuration, starting to push the data; otherwise, the target virtual machine is required to be powered off, then the hardware configuration parameters of the target virtual machine are modified to be the lowest configuration by calling the API interface of the target virtualization platform, then the target virtual machine is powered on, and then the source machine data are pushed to the target machine.
Step S40: and pushing the data to be pushed to the target virtual machine when the second hardware configuration information meets the preset configuration conditions.
In the specific implementation, first hardware configuration information of a disaster recovery source machine is analyzed, and the minimum configuration required by a data pushing stage is calculated; creating a virtual machine on a target virtualization platform by using the lowest configuration, and then executing a starting instruction on the target virtual machine; before pushing data, detecting whether the hardware configuration of the target virtual machine is the lowest configuration, if yes, starting to push the data to the target virtual machine, otherwise, powering off the target virtual machine, modifying the current hardware configuration of the target virtual machine to be the lowest configuration according to the lowest configuration determined by the first hardware configuration information, and then starting up to push the data to the target virtual machine.
According to the method, a target virtual machine is constructed according to first hardware configuration information corresponding to a disaster recovery source machine, and whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions is detected when a data pushing instruction is received; when the second hardware configuration information does not meet the preset configuration conditions, modifying the second hardware configuration information according to the target hardware configuration parameters so as to enable the second hardware configuration information to meet the preset configuration conditions; and pushing the data to be pushed to the target virtual machine when the second hardware configuration information meets the preset configuration conditions. Because the hardware configuration information of the target virtual machine in the data pushing stage is dynamically adjusted, so that the hardware configuration of the target virtual machine meets the preset configuration conditions required by data pushing, compared with the prior art, which is low in disaster recovery efficiency due to unnecessary occupation of resources of the target virtual platform, the hardware configuration information of the target virtual machine is dynamically adjusted, unnecessary occupation of resources of the target virtual platform can be reduced in the data pushing stage of disaster recovery, more disaster recovery tasks are allowed to be performed simultaneously, and disaster recovery efficiency is improved.
Referring to fig. 3, fig. 3 is a flowchart illustrating a second embodiment of the data pushing method according to the present invention, and the second embodiment of the data pushing method according to the present invention is proposed based on the first embodiment shown in fig. 2.
In this embodiment, the step S10 includes:
step S101: and acquiring first hardware configuration information corresponding to the disaster recovery source machine.
It should be noted that, the first hardware configuration information may be searched from the preset configuration database by the device identifier corresponding to the disaster recovery source machine. The preset configuration database may be a preset database, where the database includes a correspondence between a disaster recovery source device identifier and a hardware configuration parameter of a source device.
In a specific implementation, in order to ensure the hardware configuration identification efficiency of the disaster recovery source machine, a database is constructed according to the corresponding relation between the equipment identifier of the disaster recovery source machine and the hardware configuration parameters of the disaster recovery source machine.
Step S102: and determining target hardware configuration parameters required by the target virtual machine in the data pushing stage according to the first hardware configuration information of the disaster recovery source machine.
It should be noted that the target hardware configuration parameter may refer to a minimum hardware configuration parameter required by the target virtual machine in the data push stage, where the target hardware configuration parameter may be configured according to an actual situation, and in this embodiment, parameter values are not specifically set.
Further, in order to accurately determine the target hardware configuration parameter, the step S102 further includes: determining preset hardware configuration parameters required by a target virtual machine in a data pushing stage according to disk information in the first hardware configuration information; and if the preset hardware configuration parameter is larger than the actual hardware configuration parameter corresponding to the disaster recovery source machine, taking the actual hardware configuration parameter as a target hardware configuration parameter.
It should be noted that, the first hardware configuration information includes disk information, where the disk information includes the number of disks and information of a memory size required by each disk, and in determining the minimum hardware configuration information required by the target virtual machine in the data pushing stage, the preset hardware configuration parameters required by the target virtual machine in the data pushing stage are determined by using the disk information of the disaster recovery source machine and a preset calculation mode. The preset hardware configuration parameters refer to hardware configuration parameters that satisfy preset configuration conditions.
It can be understood that the preset calculation modes include: calculating the lowest CPU configuration according to the number of the disks of the disaster recovery source machine; and calculating the lowest memory configuration according to the number of the disks of the disaster recovery source machine and the memory size required by each disk, and determining hardware configuration parameters required by the target virtual machine meeting the preset configuration conditions in the data pushing stage according to the lowest CPU configuration and the lowest memory configuration.
It should be understood that if the calculated preset hardware configuration parameters are larger than the actual CPU and the memory of the source machine, the actual CPU core number and the memory size of the disaster recovery source machine are used as the hardware configuration parameters of the target virtual machine in the data push stage.
In the specific implementation, determining preset hardware configuration parameters required by a target virtual machine in a data pushing stage according to information such as the number of disks included in disk information in the first hardware configuration information; if the preset hardware configuration parameter is larger than the actual hardware configuration parameter corresponding to the disaster recovery source machine, taking the actual hardware configuration parameter as the target hardware configuration parameter.
Step S103: and calling an API interface of the target virtualization platform according to the target hardware configuration parameters of the target virtual machine to construct the target virtual machine.
It should be noted that, the target hardware configuration parameter may refer to a preset hardware configuration parameter required by determining the target virtual machine in the data pushing stage through the disk information of the disaster recovery source machine and a preset computing manner, or may refer to the actual CPU core number and the memory size of the disaster recovery source machine as the hardware configuration parameter of the target virtual machine in the data pushing stage, so that the target hardware configuration parameter may be configured according to the actual situation.
In the specific implementation, if the calculated preset hardware configuration parameters are larger than the actual CPU and the memory of the source machine, the actual CPU core number and the memory size of the disaster recovery source machine are used as the hardware configuration parameters of the target virtual machine in the data pushing stage, and an API interface of the target virtualization platform is called to construct the target virtual machine. And if the calculated preset hardware configuration parameters are not greater than the actual CPU and the memory of the source machine, calling an API interface of the target virtualization platform according to the calculated hardware configuration parameters to construct the target virtual machine.
In this embodiment, the step S20 includes:
Step S201: and when a data push instruction is received, acquiring a second hardware configuration parameter of the target virtual machine.
It should be noted that, the second hardware configuration parameter may be a hardware configuration parameter corresponding to the built target virtual machine, for example: determining target hardware configuration parameters required by constructing a virtual machine in a data pushing stage by analyzing target hardware configuration parameter information of the disaster recovery source machine A, constructing a target virtual machine a according to the target hardware configuration parameters, and detecting current hardware configuration parameters corresponding to the constructed target virtual machine a before data pushing, wherein the current hardware configuration parameters are second hardware configuration parameters.
It should be understood that, detecting the second hardware configuration parameter of the target virtual machine before data pushing may avoid that the second hardware configuration does not meet the preset configuration condition due to other factors, thereby affecting disaster recovery efficiency.
Step S202: comparing the second hardware configuration parameters of the target virtual machine with the target hardware configuration parameters, and judging whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions or not according to comparison results.
It should be noted that, comparing the detected second hardware configuration parameter with the target hardware configuration parameter, determining whether the memory size and the total number of cores of the CPU in the second hardware configuration parameter are consistent with those in the target hardware configuration parameter, and determining whether the second hardware configuration information corresponding to the target virtual machine meets the preset configuration condition according to the determination result.
Further, the step S202 further includes: and when the second hardware configuration parameters are different from the target hardware configuration parameters, judging that the second hardware configuration information does not meet the preset configuration conditions.
It should be understood that, when the second hardware configuration parameter is different from the target hardware configuration parameter, it is determined that the second hardware configuration information does not satisfy the preset configuration condition; and when the second hardware configuration parameters are the same as the target hardware configuration parameters, judging that the second hardware configuration information meets the preset configuration conditions.
Further, after the step S20, the method further includes: and when the second hardware configuration information does not meet the preset configuration conditions, modifying the second hardware configuration parameters into preset hardware configuration parameters.
In a specific implementation, when the second hardware configuration information corresponding to the target virtual machine does not meet the preset configuration condition, the second hardware configuration parameter is modified into a preset hardware configuration parameter in a data pushing stage.
The embodiment obtains first hardware configuration information corresponding to the disaster recovery source machine; determining target hardware configuration parameters required by a target virtual machine in a data pushing stage according to the first hardware configuration information; calling an API interface of a target virtualization platform to construct a target virtual machine according to target hardware configuration parameters of the target virtual machine, and acquiring second hardware configuration parameters of the target virtual machine when a data pushing instruction is received; comparing the second hardware configuration parameters with the target hardware configuration parameters of the target virtual machine, and judging whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions or not according to comparison results; when the second hardware configuration information does not meet the preset configuration conditions, modifying the second hardware configuration information according to the target hardware configuration parameters of the target virtual machine so that the second hardware configuration information meets the preset configuration conditions; and pushing the data to be pushed to the target virtual machine when the second hardware configuration information meets the preset configuration conditions. Because the hardware configuration information of the target virtual machine in the data pushing stage is dynamically adjusted, so that the hardware configuration of the target virtual machine meets the preset configuration conditions required by data pushing, compared with the prior art, which is low in disaster recovery efficiency due to unnecessary occupation of resources of the target virtual platform, the hardware configuration information of the target virtual machine is dynamically adjusted, unnecessary occupation of resources of the target virtual platform can be reduced in the data pushing stage of disaster recovery, more disaster recovery tasks are allowed to be performed simultaneously, and disaster recovery efficiency is improved.
Referring to fig. 4, fig. 4 is a flowchart illustrating a third embodiment of the data pushing method according to the present invention, and the third embodiment of the data pushing method according to the present invention is proposed based on the first embodiment shown in fig. 2.
In this embodiment, after the step S40, the method further includes:
step S50: when a service system switching instruction is received, operating system deployment is carried out on the target virtual machine according to hardware equipment information corresponding to the disaster recovery source machine, and the target virtual machine is configured according to first hardware configuration information of the disaster recovery source machine.
It should be noted that, after the data pushing is completed, when the operating system and the service system of the target virtual machine need to be started, the source service needs to be switched to the target data center, so that the continuity of the service is ensured, and the configuration of the switched target virtual machine may not be consistent with the lowest hardware configuration used in the data pushing stage. Thus requiring reconfiguration of the operating system and hardware configuration of the target virtual machine.
It should be understood that, the hardware device information corresponding to the disaster recovery source machine includes information such as a disk controller, a network card controller, a mouse controller, a keyboard controller, a graphics card adapter, and the like, and when the service system is switched, the operating system in the target virtual machine should be kept consistent with the system in the source machine, so that the service system switching operation of the source machine can be completed on the target virtual machine, therefore, the operating system deployment needs to be performed on the target virtual machine according to the hardware device information corresponding to the disaster recovery source machine, and the target virtual machine is configured according to the first hardware configuration information corresponding to the source machine, that is, the target virtual machine is configured according to the hardware configuration information of the source machine.
Further, in order to ensure service continuity, the target virtual machine is configured when the system is switched, and the step S50 further includes: when a service system switching instruction is received, acquiring hardware equipment information corresponding to the disaster recovery source machine; searching a driver corresponding to a target operating system from a preset driver library according to the hardware equipment information; and deploying the driver to an operating system of the target virtual machine, and configuring the target virtual machine according to the first hardware configuration information of the disaster recovery source machine.
When it is identified that service system switching needs to be performed, hardware device information of a disaster recovery source machine is obtained, a driver corresponding to a target operating system is searched from a preset driver library according to the hardware device information, all the obtained drivers are added to the operating system of a new virtual machine disk, so that the target virtual machine can complete configuration of the operating system according to the driver, after the service system of the target virtual machine and a corresponding operating system are configured, as the data pushing stage adopts the lowest configuration, if the target machine is switched to the service system, generally, higher configuration is needed to ensure that sufficient resources are available for the service system, and therefore, the CPU core number and the memory size of the target virtual machine are modified into the CPU core number and the memory size of the source machine contained in first hardware configuration information corresponding to the disaster recovery source machine by calling an API interface of the target virtual platform.
In a specific implementation, after the hardware configuration and the system of the target virtual machine are configured, the target virtual machine is powered off or restarted according to the requirement, so that the target virtual machine can operate according to the requirement when the service system is switched. To further illustrate the method for reducing the occupation of the target virtualized platform resource in the disaster recovery process, reference may be made to a workflow diagram shown in fig. 5, in which, by determining a source machine, analyzing hardware configuration information of the source machine, preset hardware configuration parameters required by the target virtual machine are calculated; creating a virtual machine on a target virtualization platform by using preset hardware configuration parameters, and then executing a starting instruction on the target virtual machine; before pushing data, checking whether a second hardware configuration parameter of the target virtual machine meets a preset configuration condition, if yes, starting to push the data to the target machine, if not, powering off the target virtual machine, modifying the hardware configuration of the target virtual machine according to the preset hardware configuration parameter, and then powering on to push the data to the target machine; when the target machine is required to be switched into a service system, after the target virtual machine is configured, the hardware configuration of the target virtual machine is modified according to the hardware configuration parameters of the source machine, and then the target virtual machine is restarted or powered off as required.
According to the method, a target virtual machine is constructed according to first hardware configuration information corresponding to a disaster recovery source machine, and whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions is detected when a data pushing instruction is received; when the second hardware configuration information does not meet the preset configuration conditions, modifying the second hardware configuration information according to the target hardware configuration parameters so as to enable the second hardware configuration information to meet the preset configuration conditions; and pushing the data to be pushed to the target virtual machine when the second hardware configuration information meets the preset configuration conditions. When a service system switching instruction is received, operating system deployment is carried out on the target virtual machine according to hardware equipment information corresponding to the disaster recovery source machine, and the target virtual machine is configured according to the first hardware configuration information. Because the hardware configuration information of the target virtual machine in the data pushing stage is dynamically adjusted, so that the hardware configuration of the target virtual machine meets the preset configuration conditions required by data pushing, when the target virtual machine needs to be switched to a service system, after the target virtual machine is configured, the hardware configuration of the target virtual machine is modified to be consistent with the source machine, namely high configuration, and then the target virtual machine is restarted or shut down as required.
In addition, in order to achieve the above object, the present invention also proposes a storage medium having stored thereon a data push program which, when executed by a processor, implements the steps of the data push method as described above.
Referring to fig. 6, fig. 6 is a block diagram of a first embodiment of a data pushing device according to the present invention.
As shown in fig. 6, the data pushing device provided in the embodiment of the present invention includes:
the virtual machine construction module 10 is configured to construct a target virtual machine according to first hardware configuration information corresponding to the disaster recovery source machine;
the configuration adjustment module 20 is configured to detect, when receiving a data push instruction, whether second hardware configuration information corresponding to the target virtual machine meets a preset configuration condition;
the configuration adjustment module 20 is further configured to modify the second hardware configuration information according to the target hardware configuration parameter when the second hardware configuration information does not meet the preset configuration condition, so that the second hardware configuration information meets the preset configuration condition;
and the data pushing module 30 is configured to push data to be pushed to the target virtual machine when the second hardware configuration information meets the preset configuration condition.
According to the method, a target virtual machine is constructed according to first hardware configuration information corresponding to a disaster recovery source machine, and whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions is detected when a data pushing instruction is received; when the second hardware configuration information does not meet the preset configuration conditions, modifying the second hardware configuration information according to the target hardware configuration parameters so as to enable the second hardware configuration information to meet the preset configuration conditions; and pushing the data to be pushed to the target virtual machine when the second hardware configuration information meets the preset configuration conditions. Because the hardware configuration information of the target virtual machine in the data pushing stage is dynamically adjusted, so that the hardware configuration of the target virtual machine meets the preset configuration conditions required by data pushing, compared with the prior art, which is low in disaster recovery efficiency due to unnecessary occupation of resources of the target virtual platform, the hardware configuration information of the target virtual machine is dynamically adjusted, unnecessary occupation of resources of the target virtual platform can be reduced in the data pushing stage of disaster recovery, more disaster recovery tasks are allowed to be performed simultaneously, and disaster recovery efficiency is improved.
Optionally, the virtual machine construction module 10 is further configured to obtain first hardware configuration information corresponding to the disaster recovery source machine; determining target hardware configuration parameters required by a target virtual machine in a data pushing stage according to the first hardware configuration information; and calling an API interface of the target virtualization platform according to the target hardware configuration parameters to construct a target virtual machine.
Optionally, the virtual machine construction module 10 is further configured to determine preset hardware configuration parameters required by the target virtual machine in the data pushing stage according to information such as the number of disks in the first hardware configuration information; and if the preset hardware configuration parameter is larger than the actual hardware configuration parameter corresponding to the disaster recovery source machine, taking the actual hardware configuration parameter as a target hardware configuration parameter.
Optionally, the configuration adjustment module 20 is further configured to obtain a second hardware configuration parameter of the target virtual machine when receiving a data push instruction; and comparing the second hardware configuration parameters with the target hardware configuration parameters, and judging whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions or not according to comparison results.
Optionally, the configuration adjustment module 20 is further configured to determine that the second hardware configuration information does not meet the preset configuration condition when the second hardware configuration parameter is different from the target hardware configuration parameter.
Optionally, the configuration adjustment module 20 is further configured to perform operating system deployment on the target virtual machine according to hardware device information corresponding to the disaster recovery source machine when receiving a service system switching instruction, and configure the target virtual machine according to the first hardware configuration information.
Optionally, the configuration adjustment module 20 is further configured to obtain hardware device information corresponding to the disaster recovery source machine when receiving a service system switching instruction; searching a driver corresponding to a target operating system from a preset driver library according to the hardware equipment information; and deploying the driver to an operating system of the target virtual machine, and configuring the target virtual machine according to the first hardware configuration information of the source machine.
Other embodiments or specific implementation manners of the data pushing device of the present invention may refer to the above method embodiments, and are not described herein again.
It should 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 one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the terms first, second, third, etc. do not denote any order, but rather the terms first, second, third, etc. are used to interpret the terms as names.
From the above description of embodiments, it will be clear to a person skilled in the art that the above embodiment method may be implemented by means of software plus a necessary general hardware platform, but may of course also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. read only memory mirror (Read Only Memory image, ROM)/random access memory (Random Access Memory, RAM), magnetic disk, optical disk), comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (9)
1. The data pushing method is characterized by comprising the following steps of:
determining target hardware configuration parameters required by a target virtual machine in a data pushing stage according to first hardware configuration information corresponding to a disaster recovery source machine, and constructing the target virtual machine according to the target hardware configuration parameters;
when a data pushing instruction is received, detecting whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions or not;
when the second hardware configuration information does not meet the preset configuration conditions, modifying the second hardware configuration information according to the target hardware configuration parameters of the target virtual machine so that the second hardware configuration information meets the preset configuration conditions;
when the second hardware configuration information meets the preset configuration conditions, pushing the data to be pushed to the target virtual machine;
When a service system switching instruction is received, performing operating system deployment on the target virtual machine according to hardware equipment information corresponding to the disaster recovery source machine, and configuring the target virtual machine according to first hardware configuration information of the disaster recovery source machine;
the step of determining the target hardware configuration parameters required by the target virtual machine in the data pushing stage according to the first hardware configuration information corresponding to the disaster recovery source machine comprises the following steps:
determining preset hardware configuration parameters required by the target virtual machine in the data pushing stage according to the disk information in the first hardware configuration information corresponding to the disaster recovery source machine and a preset calculation mode;
and determining target hardware configuration parameters required by the target virtual machine in the data pushing stage according to the preset hardware configuration parameters.
2. The data pushing method as claimed in claim 1, wherein the step of determining a target hardware configuration parameter required by a target virtual machine in the data pushing stage according to the first hardware configuration information corresponding to the disaster recovery source machine, and constructing the target virtual machine according to the target hardware configuration parameter includes:
acquiring first hardware configuration information corresponding to a disaster recovery source machine;
determining target hardware configuration parameters required by a target virtual machine in a data pushing stage according to the first hardware configuration information;
And calling an API interface of the target virtualization platform according to the target hardware configuration parameters of the target virtual machine to construct the target virtual machine.
3. The data pushing method as claimed in claim 2, wherein the step of determining target hardware configuration parameters required for the target virtual machine in the data pushing stage according to the preset hardware configuration parameters includes:
and if the preset hardware configuration parameter is larger than the actual hardware configuration parameter corresponding to the disaster recovery source machine, taking the actual hardware configuration parameter as a target hardware configuration parameter.
4. The method for pushing data according to claim 1, wherein the step of detecting whether the second hardware configuration information corresponding to the target virtual machine satisfies a preset configuration condition when the data pushing instruction is received includes:
when a data pushing instruction is received, acquiring a second hardware configuration parameter of the target virtual machine;
comparing the second hardware configuration parameters of the target virtual machine with the target hardware configuration parameters of the target virtual machine, and judging whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions or not according to comparison results;
after the step of detecting whether the second hardware configuration information corresponding to the target virtual machine meets the preset configuration condition when the data pushing instruction is received, the method further comprises the following steps:
And when the second hardware configuration information does not meet the preset configuration conditions, modifying the second hardware configuration parameters into preset hardware configuration parameters.
5. The data pushing method as claimed in claim 4, wherein the step of determining whether the second hardware configuration information corresponding to the target virtual machine meets the preset configuration condition according to the comparison result includes:
and when the second hardware configuration parameters are different from the target hardware configuration parameters, judging that the second hardware configuration information does not meet the preset configuration conditions.
6. The data pushing method as claimed in claim 1, wherein the step of deploying the operating system of the target virtual machine according to the hardware device information corresponding to the disaster recovery source machine and configuring the target virtual machine according to the first hardware configuration information of the disaster recovery source machine when the service system switching instruction is received includes:
when a service system switching instruction is received, acquiring hardware equipment information corresponding to the disaster recovery source machine;
searching a driver corresponding to a target operating system from a preset driver library according to the hardware equipment information;
and deploying the driver to an operating system of the target virtual machine, and configuring the target virtual machine according to the first hardware configuration information of the disaster recovery source machine.
7. A data pushing device, characterized in that the data pushing device comprises: memory, a processor and a data push program stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the data push method according to any of claims 1 to 6.
8. A storage medium having stored thereon a data push program which, when executed by a processor, implements the steps of the data push method according to any of claims 1 to 6.
9. A data pushing device, characterized in that the data pushing device comprises:
the virtual machine construction module is used for determining target hardware configuration parameters required by a target virtual machine in a data pushing stage according to first hardware configuration information corresponding to the disaster recovery source machine, and constructing the target virtual machine according to the target hardware configuration parameters;
the configuration adjustment module is used for detecting whether second hardware configuration information corresponding to the target virtual machine meets preset configuration conditions or not when a data pushing instruction is received;
the configuration adjustment module is further configured to modify the second hardware configuration information according to a target hardware configuration parameter of the target virtual machine when the second hardware configuration information does not meet the preset configuration condition, so that the second hardware configuration information meets the preset configuration condition;
The data pushing module is used for pushing the data to be pushed to the target virtual machine when the second hardware configuration information meets the preset configuration conditions;
the configuration adjustment module is further configured to, when receiving a service system switching instruction, perform operating system deployment on the target virtual machine according to hardware equipment information corresponding to the disaster recovery source machine, and configure the target virtual machine according to first hardware configuration information of the disaster recovery source machine;
the virtual machine construction module is further used for determining preset hardware configuration parameters required by the target virtual machine in the data pushing stage according to the disk information in the first hardware configuration information corresponding to the disaster recovery source machine and a preset calculation mode; and determining target hardware configuration parameters required by the target virtual machine in the data pushing stage according to the preset hardware configuration parameters.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310425180.7A CN116149802B (en) | 2023-04-20 | 2023-04-20 | Data pushing method, device, storage medium and apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310425180.7A CN116149802B (en) | 2023-04-20 | 2023-04-20 | Data pushing method, device, storage medium and apparatus |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116149802A CN116149802A (en) | 2023-05-23 |
| CN116149802B true CN116149802B (en) | 2023-09-12 |
Family
ID=86339245
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310425180.7A Active CN116149802B (en) | 2023-04-20 | 2023-04-20 | Data pushing method, device, storage medium and apparatus |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116149802B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104142861A (en) * | 2013-05-10 | 2014-11-12 | 中国电信股份有限公司 | Processing method and processing device for configuration of server resources |
| CN106919450A (en) * | 2015-12-24 | 2017-07-04 | 华为技术有限公司 | resource adjusting method and device |
| CN109992350A (en) * | 2017-12-29 | 2019-07-09 | 北京华胜天成科技股份有限公司 | The moving method and device of virtual machine in the resource pool of cloud computing system |
| CN113127133A (en) * | 2019-12-30 | 2021-07-16 | 中国移动通信集团山西有限公司 | Cross-platform virtual machine live migration method, device, equipment and medium |
| CN113835644A (en) * | 2021-11-26 | 2021-12-24 | 深圳市科力锐科技有限公司 | Complete machine migration method, device, equipment and storage medium |
| CN115357355A (en) * | 2022-08-11 | 2022-11-18 | 中国铁路信息科技集团有限公司 | Method, device and equipment for software cross-system migration and readable storage medium |
-
2023
- 2023-04-20 CN CN202310425180.7A patent/CN116149802B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104142861A (en) * | 2013-05-10 | 2014-11-12 | 中国电信股份有限公司 | Processing method and processing device for configuration of server resources |
| CN106919450A (en) * | 2015-12-24 | 2017-07-04 | 华为技术有限公司 | resource adjusting method and device |
| CN109992350A (en) * | 2017-12-29 | 2019-07-09 | 北京华胜天成科技股份有限公司 | The moving method and device of virtual machine in the resource pool of cloud computing system |
| CN113127133A (en) * | 2019-12-30 | 2021-07-16 | 中国移动通信集团山西有限公司 | Cross-platform virtual machine live migration method, device, equipment and medium |
| CN113835644A (en) * | 2021-11-26 | 2021-12-24 | 深圳市科力锐科技有限公司 | Complete machine migration method, device, equipment and storage medium |
| CN115357355A (en) * | 2022-08-11 | 2022-11-18 | 中国铁路信息科技集团有限公司 | Method, device and equipment for software cross-system migration and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116149802A (en) | 2023-05-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7269723B2 (en) | Reducing the boot time of a client device in a client device/data center environment | |
| CN110134446B (en) | Method for starting PCIE equipment scanning | |
| US10055273B2 (en) | Method for checking whether hardware of intelligent terminal runs abnormally and intelligent terminal | |
| CN112861057A (en) | Page rendering method, device and equipment based on small program and storage medium | |
| CN111026493B (en) | Interface rendering processing method and device | |
| CN112612417B (en) | Data migration method, device, equipment and storage medium | |
| CN116185571B (en) | Data migration method, device, storage medium and apparatus | |
| CN114968567A (en) | Method, apparatus and medium for allocating computing resources of a compute node | |
| CN111045789B (en) | Virtual machine starting method and device, electronic equipment and storage medium | |
| CN116149802B (en) | Data pushing method, device, storage medium and apparatus | |
| CN107688479B (en) | Android system network cluster, construction method thereof, and Android system network cluster data processing method and system | |
| CN115357355A (en) | Method, device and equipment for software cross-system migration and readable storage medium | |
| CN111030874B (en) | Service arranging method, equipment, storage medium and device | |
| CN114237631A (en) | Service deployment method and device | |
| CN114237743A (en) | Interface loading method and device, electronic equipment and storage medium | |
| CN112306373A (en) | Cluster capacity expansion method and system, electronic equipment and storage medium | |
| CN115658185B (en) | Method and device for quickly starting cloud application, storage medium and electronic equipment | |
| CN113535187B (en) | Service online method, service updating method and service providing method | |
| CN110287017B (en) | Task scheduling method and task scheduling device | |
| CN115390992A (en) | Virtual machine creating method, device, equipment and storage medium | |
| CN116245121A (en) | Information input method, information input device, computer equipment and storage medium | |
| CN113821444A (en) | Drive log control method, device, equipment and storage medium | |
| CN106775917B (en) | Method and system for starting virtual machine | |
| CN117519907A (en) | Cloud host cluster self-adaptive vGPU segmentation method, device and equipment | |
| CN116932019A (en) | Function updating method, device 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 |