Data task management automation method, system, electronic device, and storage medium

Abstract

The present invention provides a data task management automation method, system, electronic device, and storage medium. The data task management automation method includes: a first server stores data tasks in a message queue according to a set period, wherein the data tasks include first-class tasks and second-class tasks for statistically querying the task status of the first-class tasks; the first server obtains the data tasks from the message queue; if the data task is a first-class task, the first server sends the first-class task to one or more clients; and if the data task is a second-class task, the first server executes the second-class task locally. The method and device provided by the present invention can realize the execution of automated data tasks and realize efficient execution statistics of data tasks.

Description

Background Art

[0002] Enterprises employ a large number of DBAs (Database Administrators), who rely on their database operation and maintenance experience to manually provide database services. Database administrators develop their own operation and maintenance scripts and use script tools to ensure the smooth operation of the database.

[0003] Currently, this manual mode requires a large number of experienced database administrators to provide 7*24 hours database service support. Trouble shooting and performance tuning have always been professional issues in the database field, which require the professional skills of senior database administrators to solve. Due to the large number of R&D projects, the huge database scale and access volume, the existing personnel cannot guarantee to provide comprehensive database service support. There is a serious mismatch between service support and operation and maintenance needs. Some repetitive and process-based work restricts the work efficiency of database administrators, and enterprise costs continue to rise. Summary of the invention

[0004] In order to overcome the defects of the above-mentioned related technologies, the present invention provides a data task management automation method, system, electronic device, and storage medium, thereby overcoming one or more problems caused by the limitations and defects of the related technologies at least to a certain extent.

[0005] According to one aspect of the present invention, there is provided a data task management automation method, comprising:

[0006] The first server stores data tasks into a message queue according to a set period, wherein the data tasks include first-category tasks and second-category tasks for performing statistical inquiries on the task status of the first-category tasks;

[0007] The first server obtains the data task from the message queue;

[0008] If the data task is a first-category task, the first server sends the first-category task to one or more clients; and

[0009] If the data task is a second-type task, the first server executes the second-type task locally.

[0010] Optionally, after the first server sends the first type of task to one or more clients, the step further includes:

[0011] The first server monitors one or more of the clients to store and update the task status of the first type of tasks.

[0012] Optionally, the first server determines whether the data task is a first-category task or a second-category task according to a packet header of a data packet of the data task.

[0013] Optionally, before the first server stores the data task in a message queue according to a set period, the process further includes:

[0014] The first server receives the data task from the second server. The second server maintains a data task table. The data task table stores the data task, the type of the data task, the period set for the data task, and the identifier of the client to execute the data task.

[0015] Optionally, after the first server locally executes the second type of task, the method further includes:

[0016] The first server sends the execution result of the second type of task to the second server, so that the execution result is displayed on a display webpage provided by the second server.

[0017] According to another aspect of the present invention, there is further provided a first server, which is applied to the data task management automation method, and the first server comprises:

[0018] A tracking module, used for storing data tasks into a message queue according to a set period, wherein the data tasks include first-category tasks and second-category tasks for performing statistical inquiries on the task status of the first-category tasks;

[0019] A consumption module, used for obtaining the data task from the message queue; and

[0020] A working module, if the data task is a first-type task, the working module is used to send the first-type task to one or more clients; if the data task is a second-type task, the working module is used to locally execute the second-type task.

[0021] According to another aspect of the present invention, there is also provided a data task management automation system, comprising:

[0022] A first server as described above;

[0023] The client performs the following steps:

[0024] Monitor the first type of tasks issued by the first server;

[0025] performing the tasks of the first category;

[0026] Feedback the task status of the first type of tasks to the first server.

[0027] Optionally, it also includes:

[0028] The second server is used to perform the following steps:

[0029] Maintaining a data task table, wherein the data task table stores data tasks, types of data tasks, periods set for data tasks, and identifiers of clients to execute the data tasks;

[0030] The data task is sent to the first server according to the set period of the data task in the data task table.

[0031] Optionally, the second server is further configured to perform the following steps:

[0032] A display webpage is provided to display the execution results of the second type of tasks.

[0033] According to another aspect of the present invention, there is further provided an electronic device, comprising: a processor; and a storage medium storing a computer program, wherein the computer program executes the above steps when executed by the processor.

[0034] According to yet another aspect of the present invention, a storage medium is provided, wherein a computer program is stored on the storage medium, and when the computer program is executed by a processor, the steps described above are executed.

[0035] Compared with the prior art, the advantages of the present invention are:

[0036] On the one hand, automatic scheduling of data tasks can realize automatic execution of periodic and repetitive tasks, reducing the labor cost of database administrators in writing scripts; on the other hand, by distributing repetitive first-category tasks to the client for execution, and executing second-category tasks that perform statistical queries on the task status of the first-category tasks locally on the first server, since the first server monitors the execution status of the first-category tasks of the client, the second-category tasks can be executed quickly and efficiently on the first server, and it is convenient for database administrators to perform subsequent database operation and maintenance operations based on the task execution results of the second-category tasks. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.

[0038] Figure 1 A flow chart of a data task management automation method according to an embodiment of the present invention is shown.

[0039] Figure 2 A module diagram of a first server according to an embodiment of the present invention is shown.

[0040] Figure 3 A schematic diagram showing a first server scheduling data tasks according to an embodiment of the present invention is shown.

[0041] Figure 4 A schematic diagram of a data task management automation system according to an embodiment of the present invention is shown.

[0042] Figure 5 A flow chart of scheduling data tasks of a client according to an embodiment of the present invention is shown.

[0043] Figure 6 A schematic diagram of a data task management automation system according to another embodiment of the present invention is shown.

[0044] Figure 7 A schematic diagram of a computer-readable storage medium in an exemplary embodiment of the present invention is schematically shown.

[0045] Figure 8 The figure schematically shows a schematic diagram of an electronic device in an exemplary embodiment of the present invention. DETAILED DESCRIPTION

[0046] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the present invention will be more comprehensive and complete and fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0047] In addition, the accompanying drawings are only schematic illustrations of the present invention and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0048] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the steps. For example, some steps may be decomposed, while some steps may be combined or partially combined. Therefore, the actual execution order may be changed according to the actual situation.

[0049] Figure 1 FIG. 1 is a flowchart of a data task management automation method according to an embodiment of the present invention. Figure 1 , the data task management automation method comprises the following steps:

[0050] Step S110: the first server stores the data tasks into a message queue according to a set period, wherein the data tasks include first-category tasks and second-category tasks for performing statistical inquiries on the task status of the first-category tasks;

[0051] Step S120: the first server obtains the data task from the message queue;

[0052] Step S130: The first server determines whether the data task is a first-category task.

[0053] If the step S130 determines that the data task is a first-type task, then executing step S140: the first server sends the first-type task to one or more clients; and

[0054] If the step S130 determines that the data task is a second-type task, step S150 is executed: the first server locally executes the second-type task.

[0055] In the data task management automation method of the exemplary embodiment of the present invention, on the one hand, the automatic execution of periodic and repetitive tasks can be achieved through the automatic scheduling of data tasks, reducing the labor cost of database administrators in writing scripts; on the other hand, by distributing repetitive first-category tasks to the client for execution, and executing second-category tasks of statistical queries on the task status of the first-category tasks locally on the first server, since the first server monitors the execution status of the first-category tasks of the client, the second-category tasks can be executed quickly and efficiently on the first server, and it is convenient for the database administrator to perform subsequent database operation and maintenance operations according to the task execution results of the second-category tasks.

[0056] Specifically, in various embodiments of the present invention, the first type of tasks may be, for example, data tasks such as environment deployment, data backup, and data migration on devices where multiple clients are located. The second type of tasks may be, for example, statistics on the progress of environment deployment of a certain device, statistics on the progress of data backup of a certain device, and statistics on the progress of the first type of tasks of all devices. The above is only a schematic description of the first type of tasks and the second type of tasks of the present invention, and the present invention is not limited thereto.

[0057] The data task management automation method provided by the present invention will be described below in conjunction with various specific embodiments:

[0058] In a specific implementation, the step S140: after the first server sends the first type of task to one or more clients, further includes:

[0059] The first server monitors one or more of the clients to store and update the task status of the first type of tasks.

[0060] Through this step, since the task status of the first type of task is stored in the first server and its task status is updated in real time, the efficiency of executing the second type of task on the first server can be improved.

[0061] In a specific implementation, the step S130: the first server determining whether the data task is a first-category task may include:

[0062] The first server determines whether the data task is a first-category task or a second-category task according to a packet header of a data packet of the data task.

[0063] Specifically, in some specific embodiments, the message task is encapsulated via the TCP socket protocol. If a data task is obtained from the message queue, the data task is firstly subjected to a TCP socket byte security check in step S130, and then the socket header of the data task is parsed after passing the check. The first type of task and the second type of task are distinguished.

[0064] In a specific implementation, the step S140: the first server sending the first type of task to one or more clients may also include:

[0065] The first server may send the first type of tasks to one or more clients in the form of file transfer or command transfer for multi-threaded concurrent execution.

[0066] In a specific implementation, before the first server stores the data task into a message queue according to a set period in step S110, the following may also be included:

[0067] The first server receives the data task from the second server. The second server maintains a data task table. The data task table stores the data task, the type of the data task, the period set for the data task, and the identifier of the client to execute the data task.

[0068] The second server may be, for example, a web server for providing a web page interface, through which a user may enter a data task, or trigger a data task according to a user's operation on the web page interface and store it in a data task table. The second server may send the data task in the data task table that has arrived at a set time to the first server. Alternatively, the first server may obtain the data task that has arrived at a set time from the second server.

[0069] In the above implementation, after the first server locally executes the second type of task in step S150, the following may also be included:

[0070] The first server sends the execution result of the second type of task to the second server, so that the execution result is displayed on a display webpage provided by the second server.

[0071] Specifically, the data task management automation method provided by the present invention uses the producer-consumer model through a message queue. The producer is the process that produces data (storing data tasks in a message queue), and the consumer is the process that consumes data (consuming task data from a message queue). The producer-consumer model solves the problem of strong coupling between producers and consumers through message queues, so there is no need for direct communication between the two.

[0072] Based on the above-mentioned producer and consumer model, the data task management automation method provided by the present invention performs uninterrupted cyclic detection. Once a data task is found to be generated periodically or actively by the user, the first server will obtain the task time (for example, it can be divided into cyclic tasks, daily tasks, weekly tasks and monthly tasks) and queue it according to the specified time message.

[0073] Combine the following Figure 2 The first server provided by the present invention is described. Figure 2 The module diagram of the first server according to the embodiment of the present invention is shown. The first server 210 includes a tracking module 211, a consumption module, and a working module 213. The consumption module can be integrated in the working module 213, for example. The first server can also include a message queue 212.

[0074] The tracking module 211 is used to store data tasks into a message queue according to a set period, wherein the data tasks include first-type tasks and second-type tasks for statistically querying the task status of the first-type tasks;

[0075] The consumption module is used to obtain the data task from the message queue; and

[0076] If the data task is a first-type task, the working module 213 is used to send the first-type task to one or more clients; if the data task is a second-type task, the working module 213 is used to execute the second-type task locally.

[0077] In the first server of the exemplary embodiment of the present invention, on the one hand, the automatic execution of periodic and repetitive tasks can be achieved through the automatic scheduling of data tasks, thereby reducing the labor cost of database administrators in writing scripts; on the other hand, by distributing repetitive first-category tasks to the client for execution, and executing the second-category tasks of statistical queries on the task status of the first-category tasks locally on the first server, since the first server monitors the execution status of the first-category tasks of the client, the second-category tasks can be executed quickly and efficiently on the first server, and it is convenient for the database administrator to perform subsequent database operation and maintenance operations according to the task execution results of the second-category tasks.

[0078] Figure 2 The first server 210 provided by the present invention is merely schematically shown. Without violating the concept of the present invention, the splitting, merging and increasing of modules are all within the protection scope of the present invention.

[0079] In a specific implementation of the present invention, the working module 213 executes Figure 3 The process shown:

[0080] Step S310: the working module 213 consumes messages from the message queue (data task);

[0081] Step S320: the working module 213 determines whether the message is empty, if it is empty, it returns to step S310; if it is not empty, it continues to execute step S330;

[0082] Step S330: The working module 213 analyzes the data header of the message (the type of data task is stored in the data header).

[0083] Step S340: the working module 213 determines whether the data task is a first-category task according to the data header.

[0084] If step S340 determines that the data task is not a first-type task, then the data task is a second-type task, and step S350 is executed to execute the second-type task locally in the working module 213 .

[0085] If step S340 determines that the data task is a first-class task, then step S360 is executed in which the working module 213 determines that the data task is a second-class task;

[0086] Step S370: the working module 213 determines whether the first type of task is a multi-threaded task.

[0087] If the judgment in step S370 is no, step S380 is executed, and the working module 213 directly calls (calls) the first type of task to the client;

[0088] If the judgment in step S370 is yes, step S390 is executed, and the working module 213 calls the execution process to send the first type of task to the client.

[0089] The above is only a specific implementation of the working module 213, and the present invention is not limited thereto.

[0090] In a specific implementation of the present invention, the first server 210 further includes a first monitoring module 214, and the first monitoring module 214 is used to monitor the task status (execution status) of the first type of tasks of the client.

[0091] In the specific implementation of the present invention, the first server 210 integrates the operation and maintenance tools in a plug-in manner, and realizes the automated operation of task scheduling through process control. The first server 210 may also include, for example, a daemon module for realizing process daemon; an interactive module for controlling and communicating with the client, and performing remote commands and file transfers; a plug-in module that supports internal data interfaces and integrates automated operation and maintenance tools; and a process control module that manages task attributes and execution steps. The first server 210 may also integrate other modules, and the present invention is not limited thereto.

[0092] Combine the following Figure 4 The present invention provides a data task management automation system. The data task management automation system includes a first server 410 and a client 420. The first server 410 can communicate with Figure 2 The first server has the same modules.

[0093] The client 420 is used to perform the steps of monitoring the first type of tasks issued by the first server 410 ; executing the first type of tasks; and feeding back the task status of the first type of tasks to the first server 410 .

[0094] In the data task management automation system of the exemplary embodiment of the present invention, on the one hand, the automatic execution of periodic and repetitive tasks can be achieved through the automatic scheduling of data tasks, thereby reducing the labor cost of database administrators in writing scripts; on the other hand, by distributing repetitive first-category tasks to the client for execution, and executing second-category tasks that perform statistical queries on the task status of the first-category tasks locally on the first server, since the first server monitors the execution status of the first-category tasks of the client, the second-category tasks can be executed quickly and efficiently on the first server, and it is convenient for the database administrator to perform subsequent database operation and maintenance operations according to the task execution results of the second-category tasks.

[0095] In this embodiment, the client 420 may include a second monitoring module 423 for monitoring the first type of tasks issued by the first server 410; an execution module 422 for executing the first type of tasks; and an interaction module for feeding back the task status of the first type of tasks to the first server 410. The above is only a schematic description of the module structure of the client 420 of the present invention, and the present invention is not limited thereto, and the combination and splitting of modules are all within the scope of protection of the present invention.

[0096] Specifically, in a specific implementation of the present invention, after the first server 410 issues a task in TCP mode, the processing function of the second monitoring module 423 of the client 420 can be Figure 5 The step S510 shown continuously monitors the arrival of the request. Then, step S520 is executed to determine whether the data task is a first-class task. For example, the task monitored by the second monitoring module 423 can be determined to be a first-class task in the same manner as step S330 and step S340 of the above-mentioned first server (for example, analyzing the socket packet header). If it is not a first-class task, step S530 is executed to return the data task to the first server 410. If step S530 determines that it is a first-class task, step S540 is executed to further determine whether the first-class task is an asynchronous task. If step S540 determines that the first-class task is not an asynchronous task, step S550 is executed to directly execute the first-class task through an interface call. If step S540 determines that the first-class task is not an asynchronous task, step S560 is executed to add the data task to a message queue of the client and execute it in an asynchronous manner. The present invention is not limited to this.

[0097] In a specific embodiment, the client 420 can return the execution result of the first type of task to the first monitoring module in the first server via TCP socket transmission. The first monitoring module can call the application programming interface inside the first server to update and process the first type of task status task.

[0098] In some specific implementations of the client 420, the client 420 may include multiple modules that call each other, and the multiple modules may be loaded into the client 420 in the form of a common library. The multiple modules may include, for example, an interaction module 421 (used to interact with the first server and responsible for all data transmission); a log module (used to store and update the execution log of the first type of task); a setting module (used to provide some global information); and a tool module (used to provide general tools), but the present invention is not limited thereto. The modules in the common library may call each other.

[0099] Combine the following Figure 6The data task management automation system of another embodiment of the present invention is described. The data task management automation system includes a first server 610, a client 620 and a second server 630. The first server 610 can be connected to Figure 2 The first server has the same modules.

[0100] The client 620 is used to perform the steps of monitoring the first type of tasks issued by the first server 610; executing the first type of tasks; and feeding back the task status of the first type of tasks to the first server 610.

[0101] The second server 630 is used to perform the steps of: maintaining a data task table, wherein the data task table stores data tasks, data task types, data task set cycles, and identifiers of clients to be executed with the data tasks; and sending data tasks to the first server according to the set cycles of the data tasks in the data task table. In a specific embodiment, the second server 630 is also used to perform the step of providing a display webpage displaying the execution results of the second type of tasks.

[0102] The second server 630 may trigger or generate a data task according to the user's operation on the web page interface provided by the second server 630.

[0103] In an exemplary embodiment of the present invention, a computer-readable storage medium is also provided, on which a computer program is stored, and when the program is executed by, for example, a processor, the steps of the electronic prescription circulation processing method described in any of the above embodiments can be implemented. In some possible implementations, various aspects of the present invention can also be implemented in the form of a program product, which includes a program code. When the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps of various exemplary embodiments of the present invention described in the above electronic prescription circulation processing method section of this specification.

[0104] refer to Figure 7 As shown, a program product 700 for implementing the above method according to an embodiment of the present invention is described, which can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

[0105] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0106] The computer readable storage medium may include a data signal propagated in a baseband or as part of a carrier wave, wherein a readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The readable storage medium may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by an instruction execution system, an apparatus, or a device or used in combination with it. The program code contained on the readable storage medium may be transmitted with any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the above.

[0107] Program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the tenant computing device, partially on the tenant device, as a separate software package, partially on the tenant computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device may be connected to the tenant computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0108] In an exemplary embodiment of the present invention, an electronic device is further provided, which may include a processor and a memory for storing executable instructions of the processor, wherein the processor is configured to execute the steps of the electronic prescription circulation processing method described in any one of the above embodiments by executing the executable instructions.

[0109] It will be appreciated by those skilled in the art that various aspects of the present invention may be implemented as a system, method or program product. Therefore, various aspects of the present invention may be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as a "circuit", "module" or "system".

[0110] Refer to the following Figure 8 An electronic device 800 according to this embodiment of the present invention will be described. Figure 8 The electronic device 800 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0111] like Figure 8 As shown, the electronic device 800 is in the form of a general computing device. The components of the electronic device 800 may include, but are not limited to: at least one processing unit 810, at least one storage unit 820, a bus 830 connecting different system components (including the storage unit 820 and the processing unit 810), a display unit 840, etc.

[0112] The storage unit stores program codes, which can be executed by the processing unit 810, so that the processing unit 710 executes the steps according to various exemplary embodiments of the present invention described in the electronic prescription circulation processing method section of this specification. For example, the processing unit 810 can execute the following steps: Figure 1 Steps shown.

[0113] The storage unit 820 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 8201 and / or a cache memory unit 8202 , and may further include a read-only memory unit (ROM) 8203 .

[0114] The storage unit 820 may also include a program / utility 8204 having a set (at least one) of program modules 8205, such program modules 8205 including but not limited to: an operating system, one or more application programs, other program modules and program data, each of which or some combination may include the implementation of a network environment.

[0115] Bus 830 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0116] The electronic device 800 may also communicate with one or more external devices 900 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may communicate with one or more devices that enable tenants to interact with the electronic device 800, and / or may communicate with any device that enables the electronic device 800 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed through an input / output (I / O) interface 850. In addition, the electronic device 800 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 860. The network adapter 860 may communicate with other modules of the electronic device 800 through a bus 830. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0117] Through the description of the above implementation methods, it is easy for those skilled in the art to understand that the example implementation methods described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation method of the present invention can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including a number of instructions to enable a computing device (which can be a personal computer, a server, or a network device, etc.) to execute the above-mentioned electronic prescription circulation processing method according to the implementation method of the present invention.

[0118] Compared with the prior art, the advantages of the present invention are:

[0119] On the one hand, automatic scheduling of data tasks can realize automatic execution of periodic and repetitive tasks, reducing the labor cost of database administrators in writing scripts; on the other hand, by distributing repetitive first-category tasks to the client for execution, and executing second-category tasks that perform statistical queries on the task status of the first-category tasks locally on the first server, since the first server monitors the execution status of the first-category tasks of the client, the second-category tasks can be executed quickly and efficiently on the first server, and it is convenient for database administrators to perform subsequent database operation and maintenance operations based on the task execution results of the second-category tasks.

[0120] Those skilled in the art will readily appreciate other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary techniques in the art that are not disclosed by the present invention. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present invention are indicated by the appended claims.

Claims

1. A data task management automation method, characterized in that: include: The first server receives the data task from the second server, the second server maintains a data task table, the data task table stores the data task, the type of the data task, the period set for the data task, and the identifier of the client to execute the data task; The first server stores data tasks in a message queue according to a set period, wherein the data tasks include repetitive first-category tasks and second-category tasks for statistically querying the task status of the first-category tasks, wherein the first-category tasks include environment deployment, data backup, and data migration of the device where the client is located, and the second-category tasks include statistics on the progress of environment deployment of a certain device, statistics on the progress of data backup of a certain device, and statistics on the progress of the first-category tasks of all devices; The first server obtains the data task from the message queue; If the data task is a first-category task, the first server sends the first-category task to one or more clients for execution; as well as If the data task is a second-type task, the first server executes the second-type task locally; The first server sends the execution result of the second type of task to the second server, so that the execution result is displayed on a display webpage provided by the second server.

2. The data task management automation method according to claim 1, characterized in that: After the first server sends the first type of task to one or more clients, the following further includes: The first server monitors one or more of the clients to store and update the task status of the first type of tasks.

3. The data task management automation method according to claim 1, characterized in that: The first server determines whether the data task is a first-category task or a second-category task according to a packet header of a data packet of the data task.

4. A first server, applied to a data task management automation method, characterized in that: The first server comprises: A tracking module is used to store data tasks into a message queue according to a set period, wherein the data tasks include repetitive first-category tasks and second-category tasks for statistical query of the task status of the first-category tasks, wherein the first-category tasks include environment deployment, data backup, and data migration of the device where the client is located, and the second-category tasks include statistics on the progress of environment deployment of a certain device, statistics on the progress of data backup of a certain device, and statistics on the progress of first-category tasks of all devices; A consumption module, used for obtaining the data task from the message queue; and A working module, if the data task is a first-type task, the working module is used to send the first-type task to one or more clients for execution; if the data task is a second-type task, the working module is used to execute the second-type task locally, The first server is also used to: receive the data task from the second server, the second server maintains a data task table, the data task table stores the data task, the type of data task, the period set for the data task and the identifier of the client to execute the data task; send the execution result of the second type of task to the second server, so that the execution result is displayed on a display web page provided by the second server.

5. A data task management automation system, characterized in that: include: The first server as claimed in claim 4; The client performs the following steps: Monitor the first type of tasks issued by the first server; Performing the tasks of the first category; Feedback the task status of the first type of tasks to the first server.

6. The data task management automation system according to claim 5, characterized in that: Also includes: The second server is used to perform the following steps: Maintaining a data task table, wherein the data task table stores data tasks, types of data tasks, cycles set for data tasks, and identifiers of clients to execute the data tasks; The data task is sent to the first server according to the set period of the data task in the data task table.

7. The data task management automation system according to claim 6, characterized in that: The second server is further configured to perform the following steps: A display webpage is provided to display the execution results of the second type of tasks.

8. An electronic device, characterized in that: The electronic device comprises: processor; A memory having a computer program stored thereon, wherein the computer program is executed by the processor to perform the steps according to any one of claims 1 to 3.

9. A storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the steps according to any one of claims 1 to 3 are executed.

Images