CN117271203A - Application program data backup system and method and electronic equipment - Google Patents
Application program data backup system and method and electronic equipment Download PDFInfo
- Publication number
- CN117271203A CN117271203A CN202210664594.0A CN202210664594A CN117271203A CN 117271203 A CN117271203 A CN 117271203A CN 202210664594 A CN202210664594 A CN 202210664594A CN 117271203 A CN117271203 A CN 117271203A
- Authority
- CN
- China
- Prior art keywords
- backup
- scheduler
- application program
- plug
- application
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 71
- 238000009434 installation Methods 0.000 claims description 29
- 238000004590 computer program Methods 0.000 claims description 7
- 238000010586 diagram Methods 0.000 description 9
- 238000012545 processing Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000013500 data storage Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- 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/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
Abstract
The embodiment of the application provides an application program data backup system, an application program data backup method and electronic equipment, comprising the following steps: the system comprises a scheduler and a target plugin, wherein the scheduler is provided with a universal backup component, the universal backup component is a backup flow which is common to different types of application programs, the different plugins correspond to different types of application programs, the scheduler is used for determining backup tasks containing the types of the application programs to be backed up based on the universal backup component, determining the target plugin from at least one plugin according to the types of the application programs to be backed up, sending the backup tasks to the target plugin, and the target plugin is used for receiving the backup tasks and acquiring and storing application program data corresponding to the types of the application programs to be backed up based on the backup tasks. According to the method and the device, all backup processes do not need to be independently developed, so that the investment of manpower and material resources is reduced, and the efficiency and the flexibility of application program data backup are improved.
Description
Technical Field
The embodiment of the application relates to the technical field of data processing, in particular to an application program data backup system, an application program data backup method and electronic equipment.
Background
With the development of network technology, the types of application programs are increasing, and users can store data, office, etc. through the application programs.
In the prior art, in order to ensure the safety and stability of an application program, application program data can be backed up, and when the application program fails, the data can be restored by the backed up application program data.
However, the types of the application programs may be multiple, and the backup modes of the application programs of different types are different, so that a set of backup program needs to be developed separately for each type of application program to realize the backup of the application program, the investment of manpower and material resources is increased, and the efficiency of the backup of the application program data is reduced.
Disclosure of Invention
The embodiment of the application provides an application program data backup system, an application program data backup method and electronic equipment, so that the efficiency of application program data backup is improved.
In a first aspect, an embodiment of the present application provides an application data backup system, including: a scheduler and a target plug-in, the scheduler is provided with a universal backup component, the universal backup component is a backup flow which is common to different types of application programs, the different plug-ins correspond to the different types of application programs,
The scheduler is used for determining a backup task containing an application program type to be backed up based on the universal backup component, determining a target plug-in from at least one plug-in according to the application program type to be backed up, and sending the backup task to the target plug-in;
and the target plug-in is used for receiving the backup task, and acquiring and storing the application program data corresponding to the application program type to be backed up based on the backup task.
Optionally, the scheduler includes a first scheduler and a second scheduler, where the first scheduler and the second scheduler are disposed in different hardware devices, and the second scheduler is at least one, and the first scheduler is configured to:
broadcasting the backup task to the at least one second scheduler;
for any of the second schedulers, for:
and after receiving the backup task, acquiring the authority of data backup, determining a target plug-in corresponding to the application program type according to the backup task, and sending the backup task to the target plug-in.
Optionally, the second scheduler is further configured to:
splitting the backup task after receiving the backup task to obtain at least two first backup subtasks;
Transmitting the at least two first backup sub-tasks to the first scheduler;
the first scheduler is further configured to:
broadcasting the at least two first backup subtasks to at least one second scheduler after receiving the at least two first backup subtasks, wherein the first backup subtasks comprise a first subtask identifier and an application type to be backed up;
for any of the second schedulers, further for:
after receiving the at least two first backup subtasks, acquiring the authority of data backup corresponding to any one of the first backup subtasks, determining a target plug-in corresponding to the application program type, and sending the first backup subtask with the acquired data backup authority to the target plug-in;
the target plug-in is further configured to receive the first backup subtask, and obtain application data corresponding to the type of the application to be backed up and the first subtask identifier.
Optionally, the first scheduler is further configured to:
splitting the backup task to obtain at least two second backup subtasks, and broadcasting the at least two second backup subtasks to the second scheduler, wherein the second backup subtasks comprise an application program type to be backed up and a second subtask identifier;
For any of the second schedulers, further for:
after receiving the at least two second backup subtasks, acquiring the authority of data backup corresponding to any second backup subtask, determining a target plug-in corresponding to the application program type, and sending the second backup subtask with the acquired data backup authority to the target plug-in
And the target plug-in is further used for acquiring application program data corresponding to the type of the application program to be backed up and the second subtask identifier.
Optionally, the first scheduler is further configured to:
determining a storage space corresponding to the backup task;
the target plugin is further configured to:
and after the application program data corresponding to the application program type to be backed up is acquired, storing the application program data corresponding to the application program type to be backed up into the storage space.
Optionally, the first scheduler is further configured to:
constructing plug-in installation packages corresponding to different types of application programs according to pre-stored program specification data;
sending a plug-in installation request to the second scheduler, wherein the plug-in installation request comprises plug-in installation packages corresponding to different types of application programs;
The second scheduler is further configured to:
and receiving the plug-in installation request, and installing plug-in installation packages corresponding to the different types of application programs according to the plug-in installation request.
In a second aspect, an embodiment of the present application provides an application data backup method, which is applied to a scheduler, where a general backup component is disposed in the scheduler, where the general backup component is a backup flow that is common to different types of applications, and different plug-ins correspond to different types of applications, and the method includes:
determining a backup task containing an application program type to be backed up based on the universal backup component;
and determining a target plug-in from at least one plug-in according to the type of the application program to be backed up, and sending the backup task to the target plug-in so that the target plug-in acquires and stores application program data corresponding to the type of the application program to be backed up.
In a third aspect, an embodiment of the present application provides an application data backup method, applied to a target plugin, where a scheduler is configured with a universal backup component, where the universal backup component is a backup flow that is common to different types of applications, and the different plugins correspond to different types of applications, including:
Receiving a backup task containing an application program type to be backed up, which is sent by a scheduler, wherein the backup task is determined by the scheduler based on the universal backup component, and the target plug-in is determined by the scheduler from at least one plug-in according to the application program type to be backed up;
and acquiring and storing application program data corresponding to the application program type to be backed up.
In a fourth aspect, embodiments of the present application provide an electronic device, including: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored by the memory to implement the application data backup method of any one of the third or fourth aspects.
In a fifth aspect, embodiments of the present application provide a computer-readable storage medium having stored therein computer-executable instructions, which when executed by a processor, implement the application data backup method according to any one of the third or fourth aspects.
In a sixth aspect, embodiments of the present application provide a computer program product comprising a computer program which, when executed by a processor, implements the application data backup method as in any of the third or fourth aspects.
The embodiment of the application provides an application program data backup system, an application program data backup method and electronic equipment. The scheduler is used for determining a backup task containing an application program type to be backed up based on the universal backup component, determining a target plug-in from at least one plug-in according to the application program type to be backed up, sending the backup task to the target plug-in, and the target plug-in is used for receiving the backup task and acquiring and storing application program data corresponding to the application program type to be backed up based on the backup task. For different types of application programs, the universal backup components which are common to the different types of application programs are deployed in the scheduler, and different plug-ins are arranged for the different types of application programs to realize the backup of different types of application program data, namely, when the different types of application programs backup data, a part of backup processes can share a common execution framework, all backup processes are not required to be independently developed, the investment of manpower and material resources is reduced, and the efficiency and the flexibility of the application program data backup are improved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive faculty for a person skilled in the art.
FIG. 1 is a schematic diagram of an application data backup system according to an embodiment of the present disclosure;
FIG. 2 is an application schematic diagram of an application data backup system according to an embodiment of the present application;
FIG. 3 is a timing diagram of an application data backup system according to an embodiment of the present disclosure;
fig. 4 is a flowchart of an application data backup method according to an embodiment of the present application;
FIG. 5 is a flowchart illustrating a method for backing up application data according to another embodiment of the present disclosure;
FIG. 6 is a schematic structural diagram of an application data backup device according to an embodiment of the present disclosure;
FIG. 7 is a schematic structural diagram of an application data backup device according to another embodiment of the present disclosure;
fig. 8 is a schematic hardware structure of an electronic device according to an embodiment of the present application.
Detailed Description
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims of this application and in the above-described figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the present application described herein may be capable of including other sequential examples in addition to those illustrated or described. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In order to ensure the safety and stability of the application program, the application program data can be backed up (for example, the data in the databases of different types can be backed up), and when the application program fails, the data can be restored through the backed-up application program data, so that the safety and stability of the application program are improved. However, the types of the application programs may be multiple, and the backup modes of the application programs of different types are different, so that a set of backup program needs to be developed independently for each type of application program to realize the backup of the application program, namely, a set of complete backup program needs to be developed again for all backup processes when a new application program to be backed up is added, so that the investment of manpower and material resources is increased, and the efficiency of the backup of the application program data is reduced.
According to the application program data backup method and device, the universal backup components which are common to different types of application programs are deployed in the scheduler, and different plug-ins are arranged for different types of application programs to realize the backup of different types of application program data, namely, when different types of application programs are used for backing up data, a part of backup processes can share a common execution framework, all backup processes are not required to be independently developed, the investment of manpower and material resources is reduced, and the efficiency and flexibility of application program data backup are improved.
The technical scheme of the present application is described in detail below with specific examples. The following embodiments may be combined with each other, and some embodiments may not be repeated for the same or similar concepts or processes.
Fig. 1 is a schematic structural diagram of an application data backup system provided in an embodiment of the present application, and as shown in fig. 1, the application data backup system provided in an embodiment of the present application may include: the system comprises a scheduler and a target plug-in, wherein a universal backup component is arranged in the scheduler, the universal backup component is a backup flow which is common to different types of application programs, and the different plug-ins correspond to the different types of application programs.
The scheduler is used for determining a backup task containing an application program type to be backed up based on the universal backup component, determining a target plug-in from at least one plug-in according to the application program type to be backed up, and sending the backup task to the target plug-in.
And the target plug-in is used for receiving the backup task, and acquiring and storing the application program data corresponding to the application program type to be backed up based on the backup task.
In this embodiment, when data backup is performed on different types of applications, some backup processes are not limited to the application types, that is, some backup processes are common to the different types of applications, so that the backup processes that are common in the data backup process can be summarized to obtain a common backup component, and the common backup component is deployed in the scheduler. In addition, some backup processes are corresponding to the application program types, namely, some backup processes are not common to the application programs of different types, so that the processes which are not common to the application programs of different types in the data backup process, namely, the differentiated parts in the data backup process of the application programs of different types, can be realized in the form of plug-ins. If the new type application program needs to backup data, the general execution framework can be reused, only a new plug-in is needed to be developed for the new type application program, a whole new backup program is not needed to be developed again, and the development efficiency is improved.
In addition, the backup task may be determined in various ways. Alternatively, the backup task may be determined according to a preset backup rule. For example, the backup time of each application program to be backed up may be preset, and when the backup time of the application program to be backed up is reached, the backup task may be automatically generated.
Optionally, the backup task may also be determined by a touch operation manner, that is, the application to be backed up may be determined in response to a touch operation (a single click operation, a double click operation, etc.) of the user, and the backup task may be generated according to the application to be backed up. The backup task may include a type of an application to be backed up, a name of the application to be backed up, a size of the application to be backed up, and the like.
In summary, the system includes a scheduler and a target plug-in, where a generic backup component is deployed in the scheduler, where the generic backup component is a generic backup flow for different types of applications, and the different plug-ins correspond to different types of applications. The scheduler is used for determining a backup task containing an application program type to be backed up based on the universal backup component, determining a target plug-in from at least one plug-in according to the application program type to be backed up, and sending the backup task to the target plug-in, wherein the target plug-in is used for receiving the backup task and acquiring and storing application program data corresponding to the application program type to be backed up. For different types of application programs, the universal backup components which are common to the different types of application programs are deployed in the scheduler, and different plug-ins are arranged for the different types of application programs to realize the backup of different types of application program data, namely, when the different types of application programs backup data, a part of backup processes can share a common execution framework, all backup processes are not required to be independently developed, the investment of manpower and material resources is reduced, and the efficiency and the flexibility of the application program data backup are improved.
The present description examples also provide some specific embodiments of the method based on the system of fig. 1, as described below.
In another embodiment, the scheduler may include a first scheduler and a second scheduler, the first scheduler and the second scheduler being disposed in different hardware devices, the second scheduler being at least one, the first scheduler being configured to:
broadcasting the backup task to the at least one second scheduler.
For any of the second schedulers, for:
and after receiving the backup task, acquiring the authority of data backup, determining a target plug-in corresponding to the application program type according to the backup task, and sending the backup task to the target plug-in.
In this embodiment, the schedulers may include a first scheduler and a second scheduler, and one or more second schedulers may be provided, where the first scheduler and the second scheduler may be disposed in the same hardware device, or may be disposed in different hardware devices. In order to reduce the load of the hardware devices, the first scheduler and the second scheduler may be deployed in different hardware devices. In addition, if there are multiple second schedulers, different second schedulers may be deployed in the same hardware device, or may be deployed in different hardware devices. The hardware device may be a server, a server cluster, a personal computer, or the like.
In addition, when the first scheduler and the second schedulers are deployed in different hardware devices, the first scheduler sends the backup task to the second schedulers, and the backup task can be sent in a broadcasting mode, namely the first scheduler broadcasts the backup task to all the second schedulers, the second scheduler can preempt the backup task after receiving the backup task, the second scheduler preempts the backup task can obtain the authority of data backup, and then a target plug-in corresponding to the type of the application program can be determined according to the backup task.
In addition, the second schedulers and the plug-ins may be disposed in the same hardware device, and the number of plug-ins that may be scheduled by each second scheduler may be the same or different, and may be set according to a hardware composition of the hardware device, which is not limited in detail herein.
Fig. 2 is an application schematic diagram of an application data backup system according to an embodiment of the present application, as shown in fig. 2, in this embodiment, a first scheduler is disposed in a first hardware device, a second scheduler is disposed in a first hardware device of a second hardware device, and two second schedulers are disposed, where each second scheduler is also disposed in a different hardware device. In addition, each second scheduler also corresponds to three plug-ins, namely a first plug-in, a second plug-in and a third plug-in. The hardware equipment where the first scheduler is located may further include a display interface, and the control corresponding to the application program to be backed up is displayed in the display interface. In this embodiment, three controls corresponding to the application program to be backed up are displayed in the display interface, which are respectively a first application program control, a second application program control and a third application program control, the application program to be backed up can be determined through touch operation of a user, the first scheduler can respond to the touch operation of the user, generate a backup task and broadcast the backup task to the second scheduler, any second scheduler can determine a target plug-in after preempting the backup task, and start a corresponding target plug-in (exemplary, can be the first plug-in) after determining the target plug-in to realize data backup of the application program to be backed up.
In summary, by disposing the second scheduler and the first scheduler in different hardware devices, the load of a single hardware device is reduced, and the efficiency of application program data backup is improved.
Furthermore, in another embodiment, the second scheduler is further configured to:
after the backup task is received, splitting the backup task to obtain at least two first backup sub-tasks.
And sending the at least two first backup sub-tasks to the first scheduler.
The first scheduler is further configured to:
and broadcasting the at least two first backup subtasks to at least one second scheduler after receiving the at least two first backup subtasks, wherein the first backup subtasks comprise a first subtask identifier and an application type to be backed up.
For any of the second schedulers, further for:
after the at least two first backup subtasks are received, acquiring the authority of data backup corresponding to any one of the first backup subtasks, determining a target plug-in corresponding to the application program type, and sending the first backup subtask with the acquired data backup authority to the target plug-in.
The target plug-in is further configured to receive the first backup subtask, and obtain application data corresponding to the type of the application to be backed up and the first subtask identifier.
In this embodiment, there may be multiple second schedulers, and after preempting the authority of task backup, any second scheduler may determine the data volume of the application program data to be backed up first, and if the data volume of the application program data to be backed up is greater than a preset data volume threshold, split the backup task to obtain at least two first backup subtasks. Alternatively, there may be a plurality of different splitting manners when splitting the backup task. In one possible implementation manner, the backup task is formed by a plurality of subtasks, and each subtask corresponds to a subtask identifier, so that the backup task can be split according to the subtask identifiers contained in the backup task to obtain at least two first backup subtasks. In another possible implementation manner, the number of second schedulers in the idle state and the number of threads that each second scheduler in the idle state can run in parallel may be determined first, then the number of subtasks to be split is determined through the number of second schedulers in the idle state and the number of threads that each second scheduler in the idle state can run in parallel, and the backup tasks are split according to the determined number of subtasks to be split, so as to obtain first backup subtasks corresponding to the number of subtasks to be split, where each first backup subtask includes a first subtask identifier. For example, if the number of subtasks to be split is 6, the first subtask identifiers may be 1,2,3,4,5, and 6, respectively.
Furthermore, the second scheduler is further configured to:
after receiving the backup task, a pre-preparation task can be executed first, and after the pre-preparation task is completed, the target plug-in is called to backup the data of the application program to be backed up, or the backup task is split, so that at least two first backup sub-tasks are obtained.
Alternatively, the pre-preparation task may be to determine that the storage space is insufficient, determine that the application to be backed up is not occupied, i.e., is not in a running state, or the like.
In addition, after splitting the backup task to obtain at least two first backup subtasks, the second scheduler may send the at least two first backup subtasks to the first scheduler. The first scheduler may broadcast the at least two first backup sub-tasks to the at least one second scheduler after receiving the at least two first backup sub-tasks. After broadcasting at least two first backup sub-tasks to at least one second scheduler, each second scheduler (including the second scheduler that previously received the backup task and the new second scheduler) may preempt the data backup authority of the first backup sub-task, and the number of preemptions may be one or more. In order to further improve the efficiency of data backup, the number of the second scheduler preempting the first backup subtasks may default to one, and may be adjusted according to actual applications in the later period.
After the second scheduler obtains the data backup authority of the first backup subtask, the second scheduler can determine the target plug-in through the application program type, then the first backup subtask with the obtained data backup authority can be sent to the target plug-in, and the target plug-in can obtain the application program data corresponding to the application program type to be backed up and the first subtask identifier. And then, the application program data acquired by the target plug-ins corresponding to different second schedulers can be summarized to obtain the application program data corresponding to the application program to be backed up.
In summary, the data backup efficiency is improved by splitting the backup task after the second scheduler receives the backup task.
Furthermore, in another embodiment, the first scheduler is further configured to:
splitting the backup task to obtain at least two second backup subtasks, and broadcasting the at least two second backup subtasks to the second scheduler, wherein the second backup subtasks comprise application types to be backed up and second subtask identifiers.
For any of the second schedulers, further for:
and after receiving the at least two second backup subtasks, acquiring the authority of data backup corresponding to any second backup subtask, determining a target plug-in corresponding to the application program type, and sending the second backup subtask with the acquired data backup authority to the target plug-in.
And the target plug-in is further used for acquiring application program data corresponding to the type of the application program to be backed up and the second subtask identifier.
In this embodiment, when splitting the backup task, the backup task may be split through the second scheduler, and the backup task may be split through the first scheduler. After the backup task is generated, the backup task can be split through the first scheduler without redundant judgment, so that the task splitting process is simplified, the calculated amount of the first scheduler and the second scheduler is reduced, meanwhile, the backup task is scattered to a plurality of different second schedulers for execution through the splitting of the backup task, the concurrency of the backup task execution is improved, and the data backup efficiency is further improved.
Furthermore, in another embodiment, the first scheduler is further configured to:
and determining a storage space corresponding to the backup task.
The target plugin is further configured to:
and after the application program data corresponding to the application program type to be backed up is acquired, storing the application program data corresponding to the application program type to be backed up into the storage space.
In this embodiment, the first scheduler may determine a storage space corresponding to the backup task after the backup task is generated, and then may send the storage space to the second scheduler, and the second scheduler may send the storage space to the target plug-in after determining the target plug-in, and after the target plug-in obtains the application data corresponding to the application type to be backed up, store the application data corresponding to the application type to be backed up in the storage space, so as to implement backup of the application data, and then may perform data restoration through the application data in the storage space, thereby improving security of application data storage, and further improving stability and reliability of application operation corresponding to the application data.
Furthermore, in another embodiment, the first scheduler is further configured to:
and constructing plug-in installation packages corresponding to different types of application programs according to the pre-stored program specification data.
And sending a plug-in installation request to the second dispatcher, wherein the plug-in installation request comprises plug-in installation packages corresponding to different types of application programs.
The second scheduler is further configured to:
And receiving the plug-in installation request, and installing plug-in installation packages corresponding to the different types of application programs according to the plug-in installation request.
In this embodiment, different plug-ins may correspond to different types of application programs, and backup of different types of application program data may be implemented through the plug-ins. Before the plug-in is applied, plug-in installation packages corresponding to different types of application programs can be built according to pre-stored program specification data, the plug-in installation packages corresponding to the different types of application programs are sent to a second scheduler, and the second scheduler can install the plug-in installation packages corresponding to the different types of application programs in hardware equipment according to plug-in installation requests. The program specification data corresponding to different types of application programs are different, and may be specifically obtained through a common management tool corresponding to the type of application programs, which is not limited in detail herein.
Fig. 3 is a timing chart of an application data backup system provided in an embodiment of the present application, as shown in fig. 3, in this embodiment, may include:
s301, the user interface responds to touch operation to determine the type of the application program to be backed up.
S302, the user interface sends the type of the application program to be backed up to the first dispatcher.
S303, the first scheduler generates a backup task.
S304, the first scheduler allocates storage space for the backup task.
S305, the first dispatcher broadcasts the backup task to the second dispatcher through the interface. The interface may be REST interface.
S306, at least one second dispatcher returns a receiving notification to acquire the specific information of the backup task to the first dispatcher.
S307, the first dispatcher returns the specific information of the backup task to the second dispatcher which acquires the data backup authority.
And S308, the second dispatcher which acquires the data backup authority acquires the storage space allocated for the backup task. The storage space allocated for the backup task may be obtained through an NFS (network file system) or CIFS (common internet file system) protocol, that is, the storage space allocated for the backup task is mounted in a hardware device where the second scheduler is located.
S309, the second dispatcher which acquires the data backup authority executes the pre-task. Wherein the pre-tasks may be performed through the universal interface thin.
S310, splitting the backup task by the second dispatcher which acquires the data backup authority to acquire a plurality of backup subtasks.
And S311, reporting the new multiple backup sub-tasks to the first scheduler by the second scheduler which acquires the data backup authority.
S312, the first scheduler broadcasts the new plurality of backup sub-tasks to at least one second scheduler.
S313, the second dispatcher which acquires the data backup authority returns a receiving notification to acquire the specific information of the plurality of backup subtasks. The second schedulers can obtain the data backup permission of one or more backup sub-tasks.
S314, the first dispatcher returns specific information of the plurality of backup subtasks to the corresponding second dispatcher which acquires the data backup authority.
S315, the second dispatcher which acquires the data backup authority determines a target plug-in corresponding to each backup subtask.
S316, the second dispatcher which acquires the data backup authority sends each backup subtask to the corresponding target plug-in.
S317, the target plug-in acquires application program data corresponding to the backup sub-task.
And S318, the application program returns the corresponding application program data to the target plug-in unit.
And S319, the target plug-in writes the returned application program data into the allocated storage space.
In this embodiment, in order to support the capability of supporting the compatibility of backing up different types of application programs, and reduce the influence of adding applications on the existing application framework, a system architecture of the present application is obtained, which mainly includes: the user interface, the first scheduler and the backup agent, and correspondingly, the user can select an application program to be backed up at the interface. The first scheduler mainly can provide the capacity and schedule the backup agent to execute tasks, and the back-end storage and allocation storage space flow is universal, so that the back-end storage and allocation storage space flow can be abstracted into a backup universal component which is deployed in the first scheduler. The backup agent may include a second scheduler that is primarily used to schedule plug-ins corresponding to different applications to perform data backup operations. Each application program of different types can correspond to a plug-in unit and is used for backing up actual data to the allocated storage space, and personalized processing of interfacing with the application program is mainly realized. In addition, one backup agent can flexibly select the number of plug-ins to be deployed, and each backup agent can support the backup of various applications.
In summary, when a new type of application program needs to be backed up, a new plug-in needs to be developed, namely, the data backup of the new type of application program can be realized according to the new plug-in and the universal backup component, in addition, the plug-in for starting development of different languages can be supported through the universal interface based on thread, and the compatibility is strong.
In another embodiment, the target plug-in may further report the data backup progress, and illustratively, the target plug-in may report the data backup progress to the second scheduler through the thread interface, and after the second scheduler receives the data backup progress, the second scheduler may report the data backup progress to the first scheduler through the Rest interface, and the first scheduler may view the data backup progress. If the data backup progress is successful, a prompt of successful data backup can be displayed on the display interface. If the data backup progress is in backup, a prompt in data backup can be displayed on the display interface, and meanwhile, a specific backup progress (for example, 60% of data backup and the like) can also be displayed. In addition, a situation of data backup failure may be stored, and if the data backup fails, the data backup process may be re-executed until the data backup is successful, or the retry number exceeds the preset number threshold. If the retry times exceeds the preset times threshold, other second schedulers can be scheduled to carry out data backup, and the probability of successful data backup is increased.
In conclusion, the data backup progress is displayed on the display interface, so that a user or operation and maintenance personnel can intuitively know the data backup condition, and the use experience of the user is improved.
Fig. 4 is a flow chart of an application data backup method provided in an embodiment of the present application, which is applied to a scheduler, where the scheduler is configured with a general backup component, where the general backup component is a backup flow that is common to different types of applications, and different plug-ins correspond to different types of applications, as shown in fig. 4, where the method may include:
s401: a backup task containing the type of application to be backed up is determined based on the generic backup component.
S402: and determining a target plug-in from at least one plug-in according to the type of the application program to be backed up, and sending a backup task to the target plug-in so that the target plug-in acquires and stores the application program data corresponding to the type of the application program to be backed up.
In this embodiment, by disposing a general backup component common to different types of application programs in the scheduler and setting different plug-ins for different types of application programs, the backup of different types of application program data is realized, that is, when different types of application programs backup data, a part of backup processes can share a general execution framework, without developing all backup processes separately, thereby reducing the investment of manpower and material resources and improving the efficiency and flexibility of application program data backup.
Furthermore, the scheduler is further configured to:
splitting the backup task to obtain at least two first backup subtasks.
And acquiring the authority of data backup corresponding to any first backup subtask, determining a target plug-in corresponding to the application program type, and sending the first backup subtask with the acquired data backup authority to the target plug-in so that the target plug-in receives the first backup subtask and acquires the application program data corresponding to the application program type to be backed up and the first subtask identifier.
Furthermore, the scheduler is further configured to:
determining a storage space corresponding to the backup task;
and sending the storage space to a target plug-in, so that the target plug-in stores the application program data corresponding to the application program type to be backed up into the storage space after acquiring the application program data corresponding to the application program type to be backed up.
Furthermore, the scheduler is further configured to:
and constructing plug-in installation packages corresponding to different types of application programs according to the pre-stored program specification data.
And installing plug-in installation packages corresponding to the different types of application programs.
Fig. 5 is a flow chart of a method for backing up application data, which is provided in another embodiment of the present application, and is applied to a target plug-in, and a general backup component is deployed in a scheduler, where the general backup component is a backup flow that is common to different types of application programs, and the different plug-ins correspond to different types of application programs, as shown in fig. 5, and the method may include:
S501: and receiving a backup task which is sent by a scheduler and contains the type of the application program to be backed up, wherein the backup task is determined by the scheduler based on the universal backup component, and the target plug-in is determined by the scheduler from at least one plug-in according to the type of the application program to be backed up.
S502: and acquiring and storing application program data corresponding to the type of the application program to be backed up.
In this embodiment, by disposing a general backup component common to different types of application programs in the scheduler and setting different plug-ins for different types of application programs, the backup of different types of application program data is realized, that is, when different types of application programs backup data, a part of backup processes can share a general execution framework, without developing all backup processes separately, thereby reducing the investment of manpower and material resources and improving the efficiency and flexibility of application program data backup.
Based on the same idea, the embodiment of the present disclosure further provides a device corresponding to the method, and fig. 6 is a schematic structural diagram of an application data backup device provided in the embodiment of the present disclosure, where the scheduler is configured with a general backup component, where the general backup component is a backup process that is common to different types of application programs, and different plug-ins correspond to different types of application programs, as shown in fig. 6, where the device provided in the embodiment of the present disclosure may include:
A determining module 601, configured to determine, based on the generic backup component, a backup task including a type of an application to be backed up.
And the sending module 602 is configured to determine a target plug-in from at least one plug-in according to the type of the application to be backed up, and send the backup task to the target plug-in, so that the target plug-in obtains and stores application data corresponding to the type of the application to be backed up.
Furthermore, the determining module 601 is further configured to:
splitting the backup task to obtain at least two first backup subtasks.
And acquiring the authority of data backup corresponding to any first backup subtask, determining a target plug-in corresponding to the application program type, and sending the first backup subtask with the acquired data backup authority to the target plug-in so that the target plug-in receives the first backup subtask and acquires the application program data corresponding to the application program type to be backed up and the first subtask identifier.
In addition, the sending module 602 is further configured to:
determining a storage space corresponding to the backup task;
and sending the storage space to a target plug-in, so that the target plug-in stores the application program data corresponding to the application program type to be backed up into the storage space after acquiring the application program data corresponding to the application program type to be backed up.
Furthermore, the determining module 601 is further configured to:
and constructing plug-in installation packages corresponding to different types of application programs according to the pre-stored program specification data.
And installing plug-in installation packages corresponding to the different types of application programs.
Fig. 7 is a schematic structural diagram of an application data backup device provided in another embodiment of the present application, which is applied to a target plug-in, and a general backup component is deployed in a scheduler, where the general backup component is a backup flow that is common to different types of applications, and the different plug-ins correspond to the different types of applications, as shown in fig. 7, the device provided in this embodiment of the present application may include:
the receiving module 701 is configured to receive a backup task including an application type to be backed up sent by a scheduler, where the backup task is determined by the scheduler based on the universal backup component, and the target plugin is determined by the scheduler from at least one plugin according to the application type to be backed up.
The acquiring module 701 is configured to acquire and store application data corresponding to the application type to be backed up.
The device provided in the embodiment of the present application may implement the method of the embodiment shown in fig. 4 or 5, and the implementation principle and technical effects are similar, which are not repeated herein.
Fig. 8 is a schematic hardware structure of an electronic device provided in an embodiment of the present application, as shown in fig. 8, an apparatus 800 provided in the embodiment includes: a processor 801, and a memory communicatively coupled to the processor. The processor 801 and the memory 802 are connected by a bus 803.
In a specific implementation, the processor 801 executes computer-executable instructions stored in the memory 802, so that the processor 801 performs the method in the above-described method embodiment.
The specific implementation process of the processor 801 may refer to the above-mentioned method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein again.
In the embodiment shown in fig. 8, it should be understood that the processor may be a central processing unit (english: central Processing Unit, abbreviated as CPU), or may be other general purpose processors, digital signal processors (english: digital Signal Processor, abbreviated as DSP), application specific integrated circuits (english: application Specific Integrated Circuit, abbreviated as ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution.
The memory may comprise high speed RAM memory or may further comprise non-volatile storage NVM, such as at least one disk memory.
The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component Interconnect, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, the buses in the drawings of the present application are not limited to only one bus or one type of bus.
The embodiment of the application also provides a computer readable storage medium, wherein computer execution instructions are stored in the computer readable storage medium, and when a processor executes the computer execution instructions, the application program data backup method of the method embodiment is realized.
The embodiment of the application also provides a computer program product, which comprises a computer program, wherein the computer program realizes the application program data backup method when being executed by a processor.
The computer readable storage medium described above may be implemented by any type of volatile or non-volatile memory device or combination thereof, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, or optical disk. A readable storage medium can be any available medium that can be accessed by a general purpose or special purpose computer.
An exemplary readable storage medium is coupled to the processor such the processor can read information from, and write information to, the readable storage medium. In the alternative, the readable storage medium may be integral to the processor. The processor and the readable storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC for short). The processor and the readable storage medium may reside as discrete components in a device.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.
Claims (11)
1. An application data backup system, comprising: a scheduler and a target plug-in, the scheduler is provided with a universal backup component, the universal backup component is a backup flow which is common to different types of application programs, the different plug-ins correspond to the different types of application programs,
the scheduler is used for determining a backup task containing an application program type to be backed up based on the universal backup component, determining a target plug-in from at least one plug-in according to the application program type to be backed up, and sending the backup task to the target plug-in;
and the target plug-in is used for receiving the backup task, and acquiring and storing the application program data corresponding to the application program type to be backed up based on the backup task.
2. The system of claim 1, wherein the scheduler comprises a first scheduler and a second scheduler, the first scheduler and the second scheduler being disposed in different hardware devices, the second scheduler being at least one, the first scheduler being configured to:
broadcasting the backup task to the at least one second scheduler;
for any of the second schedulers, for:
And after receiving the backup task, acquiring the authority of data backup, determining a target plug-in corresponding to the application program type according to the backup task, and sending the backup task to the target plug-in.
3. The system of claim 2, wherein the second scheduler is further configured to:
splitting the backup task after receiving the backup task to obtain at least two first backup subtasks;
transmitting the at least two first backup sub-tasks to the first scheduler;
the first scheduler is further configured to:
broadcasting the at least two first backup subtasks to at least one second scheduler after receiving the at least two first backup subtasks, wherein the first backup subtasks comprise a first subtask identifier and an application type to be backed up;
for any of the second schedulers, further for:
after receiving the at least two first backup subtasks, acquiring the authority of data backup corresponding to any one of the first backup subtasks, determining a target plug-in corresponding to the application program type, and sending the first backup subtask with the acquired data backup authority to the target plug-in;
The target plug-in is further configured to receive the first backup subtask, and obtain application data corresponding to the type of the application to be backed up and the first subtask identifier.
4. The system of claim 2, wherein the first scheduler is further configured to:
splitting the backup task to obtain at least two second backup subtasks, and broadcasting the at least two second backup subtasks to the second scheduler, wherein the second backup subtasks comprise an application program type to be backed up and a second subtask identifier;
for any of the second schedulers, further for:
after receiving the at least two second backup subtasks, acquiring the authority of data backup corresponding to any second backup subtask, determining a target plug-in corresponding to the application program type, and sending the second backup subtask with the acquired data backup authority to the target plug-in
And the target plug-in is further used for acquiring application program data corresponding to the type of the application program to be backed up and the second subtask identifier.
5. The system of any of claims 2-4, wherein the first scheduler is further configured to:
Determining a storage space corresponding to the backup task;
the target plugin is further configured to:
and after the application program data corresponding to the application program type to be backed up is acquired, storing the application program data corresponding to the application program type to be backed up into the storage space.
6. The system of any of claims 2-4, wherein the first scheduler is further configured to:
constructing plug-in installation packages corresponding to different types of application programs according to pre-stored program specification data;
sending a plug-in installation request to the second scheduler, wherein the plug-in installation request comprises plug-in installation packages corresponding to different types of application programs;
the second scheduler is further configured to:
and receiving the plug-in installation request, and installing plug-in installation packages corresponding to the different types of application programs according to the plug-in installation request.
7. The utility model provides an application program data backup method which is characterized in that the method is applied to a scheduler, the scheduler is provided with a general backup component, the general backup component is a general backup flow of different types of application programs, and different plug-ins correspond to different types of application programs, and the method comprises the following steps:
Determining a backup task containing an application program type to be backed up based on the universal backup component;
and determining a target plug-in from at least one plug-in according to the type of the application program to be backed up, and sending the backup task to the target plug-in so that the target plug-in acquires and stores application program data corresponding to the type of the application program to be backed up.
8. The utility model provides an application program data backup method which is characterized in that the method is applied to a target plug-in, a general backup component is arranged in a scheduler, the general backup component is a general backup flow of different types of application programs, and the different plug-ins correspond to the different types of application programs, and the method comprises the following steps:
receiving a backup task containing an application program type to be backed up, which is sent by a scheduler, wherein the backup task is determined by the scheduler based on the universal backup component, and the target plug-in is determined by the scheduler from at least one plug-in according to the application program type to be backed up;
and acquiring and storing application program data corresponding to the application program type to be backed up.
9. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
The memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the application data backup method of claim 7 or 8.
10. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor perform the application data backup method of claim 7 or 8.
11. A computer program product comprising a computer program which, when executed by a processor, implements the application data backup method of claim 7 or 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210664594.0A CN117271203A (en) | 2022-06-14 | 2022-06-14 | Application program data backup system and method and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210664594.0A CN117271203A (en) | 2022-06-14 | 2022-06-14 | Application program data backup system and method and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117271203A true CN117271203A (en) | 2023-12-22 |
Family
ID=89216535
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210664594.0A Pending CN117271203A (en) | 2022-06-14 | 2022-06-14 | Application program data backup system and method and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117271203A (en) |
-
2022
- 2022-06-14 CN CN202210664594.0A patent/CN117271203A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109117260B (en) | Task scheduling method, device, equipment and medium | |
| US7779413B2 (en) | Method of assigning available resources for internal and external users at start time of scheduled time period based on program reservations information | |
| CN109936604B (en) | Resource scheduling method, device and system | |
| US10261813B2 (en) | Data processing system for dispatching tasks from a plurality of applications to a shared resource provided by an accelerator | |
| US8286178B2 (en) | Allocation and regulation of CPU entitlement for virtual processors in logical partitioned platform | |
| CN110941481A (en) | Resource scheduling method, device and system | |
| US20170017511A1 (en) | Method for memory management in virtual machines, and corresponding system and computer program product | |
| CN110888743A (en) | GPU resource using method, device and storage medium | |
| CN110427258B (en) | Resource scheduling control method and device based on cloud platform | |
| CN114625533A (en) | Distributed task scheduling method and device, electronic equipment and storage medium | |
| CN110737453A (en) | Security chip upgrading method and device and security chip | |
| WO2011114476A1 (en) | Multicore processor system, notification program, and notification method | |
| CN111694658A (en) | CPU resource allocation method, device, electronic equipment and storage medium | |
| CN115480931A (en) | Inter-core communication processing method and device and computer system | |
| CN111736961B (en) | Virtual machine release method and device, storage medium and electronic equipment | |
| CN117271203A (en) | Application program data backup system and method and electronic equipment | |
| CN112068960A (en) | CPU resource allocation method, device, storage medium and equipment | |
| CN111359205A (en) | Operation method and device of cloud game, computer equipment and storage medium | |
| CN111813541B (en) | Task scheduling method, device, medium and equipment | |
| JP2006031203A (en) | On-vehicle information terminal | |
| CN112181662A (en) | Task scheduling method and device, electronic equipment and storage medium | |
| CN106484536B (en) | IO scheduling method, device and equipment | |
| CN110704181A (en) | Resource allocation method, device and storage medium | |
| CN111382351B (en) | Soft telephone resource sharing method, electronic device and computer readable storage medium | |
| US10013299B2 (en) | Handling crashes of a device's peripheral subsystems |
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 |