CN107797887B - Data backup and recovery method and device, storage medium and electronic equipment - Google Patents
Data backup and recovery method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN107797887B CN107797887B CN201711015595.8A CN201711015595A CN107797887B CN 107797887 B CN107797887 B CN 107797887B CN 201711015595 A CN201711015595 A CN 201711015595A CN 107797887 B CN107797887 B CN 107797887B
- Authority
- CN
- China
- Prior art keywords
- data
- backup
- recovery
- information
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a data backup and recovery method, a data backup and recovery device, a storage medium and electronic equipment, and relates to the technical field of data processing. The data backup method comprises the following steps: sending the information to be configured to a server of a user to which the data to be backed up belongs so that the user can configure the information to be configured; acquiring information configured by a user; wherein the user configured information comprises a target directory for storing backup data; and controlling a backup tool to capture data to be backed up at regular time according to a preset requirement and storing the data to be backed up in the target directory. The method and the system can realize unified management of different types of databases, are not limited by the types of the databases, and can perform personalized expansion.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a data backup method, a data recovery method, a data backup apparatus, a data recovery apparatus, a storage medium, and an electronic device.
Background
In the process of database backup and recovery, different types of databases may correspond to different backup and recovery modes, and timeliness may also be different. In this case, different solutions need to be implemented for different types of databases, which consumes a lot of enterprise production costs.
In addition, after the system accesses a large number of different types of databases, when backup and recovery operations are performed on the databases and the operation conditions are checked, processes of encrypting and decrypting each database may be required, and these processes may also increase the management cost of an enterprise.
At present, on one hand, unified deployment and management cannot be performed on different types of accessed databases; on the other hand, database backup and recovery schemes of some technologies aim at a certain type or individual mainstream database, personalized requirements cannot be expanded, and the situation that some databases cannot be backed up and recovered still exists.
In view of this, there is a need for a data backup method, a data recovery method, a data backup apparatus, a data recovery apparatus, a storage medium, and an electronic device.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
An object of the present disclosure is to provide a data backup method, a data restoring method, a data backup apparatus, a data restoring apparatus, a storage medium, and an electronic device, thereby overcoming, at least to some extent, one or more problems due to limitations and disadvantages of the related art.
According to an aspect of the present disclosure, there is provided a data backup method, including:
sending the information to be configured to a server of a user to which the data to be backed up belongs so that the user can configure the information to be configured;
acquiring information configured by a user; wherein the user configured information comprises a target directory for storing backup data;
and controlling a backup tool to capture data to be backed up at regular time according to a preset requirement and storing the data to be backed up in the target directory.
In an exemplary embodiment of the present disclosure, the data backup method further includes:
and deploying the backup tool in a front-end processor.
In an exemplary embodiment of the present disclosure, the data backup method further includes:
controlling the front-end processor to receive a backup log;
and responding to the backup log viewing request to acquire the backup log from the front-end processor.
According to an aspect of the present disclosure, there is provided a data recovery method including:
determining data to be recovered in response to data recovery operation of a user;
acquiring a recovery path of the data to be recovered, which is configured by a user;
and controlling the recovery tool to send the data to be recovered to the target database through the recovery path.
In an exemplary embodiment of the present disclosure, the data recovery method further includes:
deploying the recovery tool in a front-end processor.
In an exemplary embodiment of the present disclosure, the data recovery method further includes:
controlling the front-end processor to receive a recovery log;
responding to a recovery log viewing request to acquire a recovery log from the front-end processor;
and sending alarm information to carry out a manual recovery process if the data recovery fails and/or the recovery log is abnormal.
According to an aspect of the present disclosure, there is provided a data backup apparatus including:
the device comprises a to-be-configured information sending module, a to-be-configured information sending module and a to-be-configured information backup module, wherein the to-be-configured information is sent to a server of a user to which the to-be-configured data belongs, so that the user can configure the to-be-configured information;
the information acquisition module is used for acquiring information configured by a user; wherein the user configured information comprises a target directory for storing backup data;
and the data backup module is used for controlling a backup tool to capture data to be backed up at regular time according to preset requirements and storing the data to be backed up in the target directory.
In an exemplary embodiment of the present disclosure, the data backup apparatus further includes:
and the backup tool deployment module is used for deploying the backup tool in the front-end processor.
In an exemplary embodiment of the present disclosure, the data backup apparatus further includes:
the control backup log receiving module is used for controlling the front-end processor to receive the backup logs;
and the backup log obtaining module is used for responding to the backup log viewing request to obtain the backup log from the front-end computer.
According to an aspect of the present disclosure, there is provided a data recovery apparatus including:
the data to be recovered determining module is used for responding to the data recovery operation of the user to determine the data to be recovered;
a recovery path obtaining module, configured to obtain a recovery path of the data to be recovered, where the recovery path is configured by a user;
and the data recovery module is used for controlling the recovery tool to send the data to be recovered to the target database through the recovery path.
In an exemplary embodiment of the present disclosure, the data restoring apparatus further includes:
and the recovery tool deployment module is used for deploying the recovery tool in the front-end processor.
In an exemplary embodiment of the present disclosure, the data restoring apparatus further includes:
the control recovery log receiving module is used for controlling the front-end processor to receive the recovery log;
the recovery log obtaining module is used for responding to a recovery log viewing request to obtain a recovery log from the front-end processor;
and sending alarm information to carry out a manual recovery process if the data recovery fails and/or the recovery log is abnormal.
According to an aspect of the present disclosure, there is provided a storage medium having stored thereon a computer program which, when executed by a processor, implements the data backup method of any one of the above or the data recovery method of any one of the above.
According to an aspect of the present disclosure, there is provided an electronic device including:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform any one of the data backup methods or any one of the data recovery methods via execution of the executable instructions.
In the technical solutions provided in some embodiments of the present disclosure, first, information to be configured is sent to a user for the user to configure related parameters for backup and recovery, then, a backup tool and a recovery tool are deployed, and then, a data backup and/or recovery process is performed according to the requirements or operations of the user, on one hand, by providing information to be configured for data backup and recovery to the user and acquiring the information configured by the user, unified management on backup and recovery of different types of databases can be achieved; on the other hand, the scheme is not limited by the type of the database and can be subjected to personalized expansion.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty. In the drawings:
FIG. 1 schematically illustrates a flow chart of a data backup method according to an exemplary embodiment of the present disclosure;
FIG. 2 illustrates an effect diagram of an interface of a first portion of information to be configured according to an example embodiment of the present disclosure;
FIG. 3 illustrates an effect diagram of an interface of a second portion of information to be configured according to an example embodiment of the present disclosure;
FIG. 4 illustrates an effect diagram of an interface of a third portion of information to be configured, according to an example embodiment of the present disclosure;
FIG. 5 shows an effect diagram of an interface of a tool deployment according to an example embodiment of the present disclosure;
FIG. 6 shows an effect diagram of an interface for data backup according to an example embodiment of the present disclosure;
FIG. 7 schematically illustrates a flow chart of a method of data recovery according to an exemplary embodiment of the present disclosure;
FIG. 8 illustrates an effect diagram of an interface for data recovery according to an exemplary embodiment of the present disclosure;
FIG. 9 schematically illustrates a block diagram of a data backup apparatus according to an exemplary embodiment of the present disclosure;
FIG. 10 schematically illustrates another block diagram of a data backup apparatus according to an exemplary embodiment of the present disclosure;
FIG. 11 schematically illustrates yet another block diagram of a data backup apparatus according to an exemplary embodiment of the present disclosure;
FIG. 12 schematically illustrates a block diagram of a data recovery apparatus according to an exemplary embodiment of the present disclosure;
FIG. 13 schematically illustrates another block diagram of a data recovery apparatus according to an exemplary embodiment of the present disclosure;
FIG. 14 schematically illustrates yet another block diagram of a data recovery apparatus according to an exemplary embodiment of the present disclosure;
FIG. 15 shows a schematic diagram of a storage medium according to an example embodiment of the present disclosure; and
fig. 16 schematically shows a block diagram of an electronic device according to an exemplary embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of 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. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the steps. For example, some steps may be decomposed, and some steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.
Fig. 1 schematically shows a flowchart of a data backup method of an exemplary embodiment of the present disclosure. Referring to fig. 1, the data backup method may include the steps of:
s10, sending the information to be configured to a server of a user to which the data to be backed up belongs so that the user can configure the information to be configured;
s12, obtaining information configured by a user; wherein the user configured information comprises a target directory for storing backup data;
s14, controlling a backup tool to capture data to be backed up at regular time according to preset requirements and storing the data to be backed up in the target directory.
In the data backup method according to the exemplary embodiment of the present disclosure, on one hand, by sending information to be configured to a user, the user configures the information to be configured and obtains the information configured by the user, unified management of different types of databases can be achieved; on the other hand, the scheme is not limited by the type of the database and can be personalized and expanded.
Each step of the data backup method of the exemplary embodiment of the present disclosure will be described in detail below.
In step S10, the information to be configured is sent to the server of the user to which the data to be backed up belongs, so that the user can configure the information to be configured.
In an exemplary embodiment of the present disclosure, first, a developer may collate information to be configured involved in data backup and recovery by means of a data platform. The data platform can be deployed on a server and can be developed autonomously by developers.
The item to be configured with information according to the present disclosure may include a target directory for storing backup data, that is, may include a storage path of a database backup file. In addition, because database backups are persistent, the items of information to be configured may also include the number of retained backups. Fig. 2 schematically shows an effect diagram of a first part of an interface to be configured with information. As shown in fig. 2, the items to be configured with information may further include a data backup receiving directory, an alarm mail target and an alarm short message target, where the alarm is intended to quickly notify relevant personnel to process if the backup data fails to be recovered.
In addition, the items of information to be configured may also include database sources and database base information. The database source may include a database type, a database version, a system version in which the database is located, and the like. In particular, fig. 3 schematically shows an effect diagram of a second part of the interface of the information to be configured.
In addition, the item to be configured with information may also contain content related to data recovery. In particular, fig. 4 schematically shows an effect diagram of a third part of the interface of the information to be configured. Referring to fig. 4, the information to be configured may further include a target database url, a target database name, a user name, a password, and a remark. Wherein multiple target databases may exist for the data recovery process, and thus, a user may configure one or more target database paths. The method can provide the password service in the data recovery process, and through the encryption and decryption processes, on one hand, a non-data owner cannot recover the data, so that the safety of the data is ensured; on the other hand, the method is beneficial to realizing personalized services. It is easy to understand that the configuration information of the data backup may also be provided with items related to the password to further enhance the security of data processing, which is not further described in this exemplary embodiment.
It should be understood that the content that the user has to fill in may be identified distinctively, for example, the star-shaped identification in fig. 2 to 4 before the item name. And for some default content and content that does not affect data backup and/or recovery, the user is not required to have to configure. In addition, the information to be configured described in the present disclosure may also include other items, which are not particularly limited in the present exemplary embodiment.
After the user configures the information to be configured, the configured information can be sent to the data platform through the server of the user side.
In step S12, information configured by the user is acquired; wherein the user configured information comprises a target directory for storing backup data.
In step S14, the backup tool is controlled according to a preset requirement to capture data to be backed up and store the data to the target directory.
In an exemplary embodiment of the present disclosure, the preset requirement may be set by a user, for example, the preset requirement may include automatic backup every 2 days, backup of specified data in a database at the user end, and the like. In addition, when the user does not provide own requirements, the developer can define the backup requirements as preset requirements according to the processing capacity of the data platform, and the backup requirements are used as default backup rules, for example, data backup is performed at 2 pm every saturday.
According to some embodiments of the present disclosure, a front-end processor may be configured between a data platform and a user server based on security considerations. In addition, it should be understood that the front-end processor is not necessarily a separate device or module, and may be integrated on the user server or on the server of the data platform to implement the functionality of the front-end processor.
In addition, the data backup method of the present disclosure may further include deploying the backup tool in the front-end processor. Specifically, first, the data platform may obtain a backup tool, which may be developed by a developer, or may be an existing backup tool, which is not particularly limited in this exemplary embodiment; next, the data platform may send the backup tool to the front-end processor, thereby implementing deployment of the backup tool on the front-end processor. FIG. 5 schematically illustrates an effect diagram of a tool deployment interface.
The data platform may control the backup tool to capture the data to be backed up from the user database at regular time according to a preset requirement, and store the data to be backed up to the target directory configured by the user in step S10. In the solution of the presence of the front-end processor, the target directory may be present in the front-end processor, and may also be present in a data platform or other units with a storage function, and the specific location of the target directory is not particularly limited in this exemplary embodiment.
In addition, the front-end processor may be configured with, for example, a MySQL database for storing backup logs. In addition, the MySQL database may also store the database basic information described in step S10.
According to some embodiments of the present disclosure, first, a data platform may control a front-end processor to receive a backup log in a data backup process; next, when the developer needs to check the backup log, a backup log checking request may be generated, the data platform may obtain the backup log from the front-end computer in response to the backup log checking request, and generate a data backup interface on the data platform based on the backup log for the developer to check, where fig. 6 schematically illustrates an effect diagram of the data backup interface. In addition, when a developer finds that data backup has problems, the reason can be determined through logs so as to perform corresponding processing.
Further, the present disclosure also provides a data recovery method.
Fig. 7 schematically shows a flowchart of a data recovery method of an exemplary embodiment of the present disclosure. Referring to fig. 7, the data recovery method may include the steps of:
s70, responding to data recovery operation of a user to determine data to be recovered;
s72, acquiring a recovery path of the data to be recovered, configured by a user;
and S74, controlling the recovery tool to send the data to be recovered to the target database through the recovery path.
The data recovery method disclosed by the invention corresponds to the data backup method, and different databases can be uniformly managed in the data backup process, so that the data recovery process can also be uniformly managed on a data platform, and the data recovery method is not limited by the types of the databases and can be personalized and expanded.
In step S70, the user may select the data to be restored according to his own requirements, for example, the user may restore the backup data on a certain date by selecting the date. The data platform may determine, in response to a data recovery operation by a user, backup data stored in the target directory as data to be recovered.
In step S72, since the user has configured the content related to data recovery during the data backup process, the data platform may determine the recovery path of the data to be recovered from the information configured by the user, that is, the data platform may determine the path of the target database to which the data to be recovered should be recovered. It is to be readily understood that the number of target databases may be one or more.
In step S74, according to some embodiments of the present disclosure, a front-end processor may be configured between the data platform and the user server, and the recovery tool may be deployed in the front-end processor, similar to the process of deploying the backup tool, and will not be described herein again.
The front-end processor may be configured with, for example, a MySQL database that may store a recovery log in addition to a backup log, as described above.
According to some embodiments of the present disclosure, first, a data platform may control a front-end processor to receive a recovery log in a data recovery process; next, when the developer needs to view the recovery log, a recovery log viewing request may be generated, the data platform may obtain the recovery log from the front-end processor in response to the recovery log viewing request, and generate a data recovery interface on the data platform based on the recovery log for the developer to view, where fig. 8 schematically illustrates an effect diagram of the data recovery interface. In addition, if the data recovery fails and/or the developer finds that the recovery log is abnormal, the data platform can send out warning information in the form of mails or short messages to inform the developer, so that the developer can timely perform a manual recovery process, and the waiting time of the user in recovering the data error can be reduced.
It should be noted that although the various steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that these steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Further, the present exemplary embodiment also provides a data backup apparatus.
Fig. 9 schematically illustrates a block diagram of a data backup apparatus according to an exemplary embodiment of the present disclosure. Referring to fig. 9, the data backup apparatus 9 according to an exemplary embodiment of the present disclosure may include an information-to-be-configured transmitting module 91, an information acquiring module 93, and a data backup module 95: wherein:
the to-be-configured information sending module 91 may be configured to send the to-be-configured information to a server of a user to which the to-be-backed up data belongs, so that the user configures the to-be-configured information;
an information obtaining module 93, which may be used to obtain information configured by a user; wherein the user configured information comprises a target directory for storing backup data;
the data backup module 95 may be configured to control a backup tool to capture data to be backed up at regular time according to a preset requirement and store the data to the target directory.
In the data backup device according to the exemplary embodiment of the present disclosure, on one hand, by sending information to be configured to a user, the user configures the backup information and obtains the information configured by the user, unified management of different types of databases can be achieved; on the other hand, the scheme is not limited by the type of the database and can be personalized and expanded.
According to an exemplary embodiment of the present disclosure, referring to fig. 10, the data backup apparatus 10 may further include a backup tool deployment module 101, in addition to the to-be-configured information sending module 91, the information obtaining module 93, and the data backup module 95, compared to the data backup apparatus 9, where:
the backup tool deployment module 101 may be configured to deploy the backup tool in a front-end processor.
The safety of data backup is improved by configuring the front-end processor.
According to an exemplary embodiment of the present disclosure, referring to fig. 11, compared to the data backup apparatus 10, the data backup apparatus 11 may further include a control backup log receiving module 111 and a backup log obtaining module 113, in addition to the to-be-configured information sending module 91, the information obtaining module 93, the data backup module 95, and the backup tool deployment module 101, where:
a control backup log receiving module 111, configured to control the front-end processor to receive a backup log;
the backup log obtaining module 113 may be configured to obtain a backup log from the front-end computer in response to the backup log viewing request.
By monitoring the backup log, real-time control over the backup process is facilitated, and when a backup error occurs, the backup error can be corrected in time.
Further, the present exemplary embodiment also provides a data recovery apparatus.
Fig. 12 schematically shows a block diagram of a data recovery apparatus according to an exemplary embodiment of the present disclosure. Referring to fig. 12, the data restoring apparatus 12 according to an exemplary embodiment of the present disclosure may include a to-be-restored data determining module 121, a restoration path acquiring module 123, and a data restoring module 125, wherein:
a to-be-recovered data determining module 121, configured to determine to-be-recovered data in response to a data recovery operation of a user;
a recovery path obtaining module 123, configured to obtain a recovery path of the data to be recovered, where the recovery path is configured by a user;
the data recovery module 125 may be configured to control the recovery tool to send the data to be recovered to the target database via the recovery path.
The data recovery device corresponds to the data backup device, and different databases can be uniformly managed in the data backup process, so that the data recovery process can also be uniformly managed on a data platform, and the data recovery device is not limited by the types of the databases and can be personalized and expanded.
According to an exemplary embodiment of the present disclosure, referring to fig. 13, the data recovery apparatus 13 may further include a recovery tool deployment module 131, in addition to the to-be-recovered data determining module 121, the recovery path obtaining module 123, and the data recovery module 125, compared to the data recovery apparatus 12, wherein:
a recovery tool deployment module 131, which may be used to deploy the recovery tool in a front-end processor.
The safety of data recovery is improved by configuring the front-end processor.
According to an exemplary embodiment of the present disclosure, referring to fig. 14, the data recovery apparatus 14 may further include a control recovery log receiving module 141 and a recovery log obtaining module 143, in addition to the to-be-recovered data determining module 121, the recovery path obtaining module 123, the data recovery module 125, and the recovery tool deploying module 131, compared to the data recovery apparatus 13, where:
a control recovery log receiving module 141, configured to control the front-end processor to receive a recovery log;
a recovery log obtaining module 143, configured to obtain a recovery log from the front-end processor in response to a recovery log viewing request;
and sending alarm information to carry out a manual recovery process if the data recovery fails and/or the recovery log is abnormal.
If the data recovery fails and/or the developer finds that the recovery log is abnormal, the data platform can send out warning information in the form of mails or short messages to inform the developer, so that the developer can conveniently and timely carry out the manual recovery process, and the waiting time of the user in the data recovery error can be reduced.
Since each functional module of the program operation performance analysis apparatus according to the embodiment of the present invention is the same as that in the embodiment of the present invention, it is not described herein again.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.
Referring to fig. 15, a program product 1500 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind 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., through the internet using an internet service provider).
In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 1600 according to this embodiment of the invention is described below with reference to fig. 16. The electronic device 1600 shown in fig. 16 is only an example and should not bring any limitations to the function and scope of use of the embodiments of the present invention.
As shown in fig. 16, electronic device 1600 is in the form of a general purpose computing device. Components of electronic device 1600 may include, but are not limited to: the at least one processing unit 1610, the at least one memory unit 1620, the bus 1630 connecting different system components (including the memory unit 1620 and the processing unit 1610), and the display unit 1640.
Wherein the memory unit stores program code that may be executed by the processing unit 1610 to cause the processing unit 1610 to perform steps according to various exemplary embodiments of the present invention as described in the above section "exemplary method" of the present specification. For example, the processing unit 1610 may perform step S10 as shown in fig. 1: sending the information to be configured to a server of a user to which the data to be backed up belongs so that the user can configure the information to be configured; step S12: acquiring information configured by a user; wherein the user configured information comprises a target directory for storing backup data; step S14: and controlling a backup tool to capture data to be backed up at regular time according to a preset requirement and storing the data to be backed up in the target directory. Alternatively, the processing unit 1610 may execute step S70 shown in fig. 7: determining data to be recovered in response to data recovery operation of a user; step S72: acquiring a recovery path of the data to be recovered, which is configured by a user; step S74: and controlling the recovery tool to send the data to be recovered to the target database through the recovery path.
The memory unit 1620 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)16201 and/or a cache memory unit 16202, and may further include a read only memory unit (ROM) 16203.
The storage unit 1620 may also include a program/utility 16204 having a set (at least one) of program modules 16205, such program modules 16205 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 thereof, may comprise an implementation of a network environment.
The electronic device 1600 can also communicate with one or more external devices 1700 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 1600, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 1600 to communicate with one or more other computing devices. Such communication may occur through input/output (I/O) interface 1650. Also, the electronic device 1600 can 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) via the network adapter 1660. As shown, the network adapter 1660 communicates with the other modules of the electronic device 1600 via the bus 1630. It should be appreciated that although not shown, other hardware and/or software modules may be used in conjunction with electronic device 1600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is to be limited only by the terms of the appended claims.
Claims (6)
1. A data backup method is applied to a data platform, wherein the data platform is deployed on a server, and comprises the following steps:
sending the information to be configured to a server of a user to which the data to be backed up belongs so that the user can configure the information to be configured;
acquiring information configured by a user; wherein the user configured information comprises a target directory for storing backup data;
controlling a backup tool to capture data to be backed up at regular time according to a preset requirement and store the data to be backed up to the target directory, wherein the backup tool is deployed in a front-end processor, and the front-end processor is configured between the data platform and a server of the user;
wherein, the information to be configured further comprises any one or more of the following: keeping the backup times; a data backup receiving directory; a database source; database base information; data recovery related content;
the data backup method further comprises the following steps:
controlling the front-end processor to receive a backup log in a data backup process;
acquiring a backup log from the front-end processor in response to receiving a backup log viewing request;
and generating a display interface of the data backup process on the data platform based on the backup log.
2. A data recovery method is applied to a data platform, wherein the data platform is deployed on a server, and the method comprises the following steps:
determining data to be recovered in response to data recovery operation of a user;
determining a recovery path of the data to be recovered according to the related content of data recovery in the information configured by the user;
controlling a recovery tool to send data to be recovered to a target database via the recovery path, the recovery tool being deployed in a front-end processor, the front-end processor being configured between the data platform and a server of the user;
wherein the user configured information is determined according to the information to be configured in claim 1;
the data recovery method further comprises:
controlling the front-end processor to receive a recovery log in the data recovery process;
responding to the received request for checking the recovery log, and acquiring the recovery log from the front-end processor;
generating a display interface of the data recovery process on the data platform based on the recovery log;
and sending alarm information to carry out a manual recovery process if the data recovery fails and/or the recovery log is abnormal.
3. A data backup device is applied to a data platform, wherein the data platform is deployed on a server, and the data backup device comprises:
the device comprises a to-be-configured information sending module, a to-be-configured information sending module and a to-be-configured information backup module, wherein the to-be-configured information is sent to a server of a user to which the to-be-configured data belongs, so that the user can configure the to-be-configured information;
the information acquisition module is used for acquiring information configured by a user; wherein the user configured information comprises a target directory for storing backup data;
the data backup module is used for controlling a backup tool to capture data to be backed up at regular time according to preset requirements and storing the data to the target directory, wherein the backup tool is deployed in a front-end processor, and the front-end processor is configured between the data platform and a server of the user;
wherein, the information to be configured further comprises any one or more of the following: keeping the backup times; a data backup receiving directory; a database source; database base information; data recovery related content;
the data backup apparatus further includes:
controlling the front-end processor to receive a backup log in a data backup process;
acquiring a backup log from the front-end processor in response to receiving a backup log viewing request;
and generating a display interface of the data backup process on the data platform based on the backup log.
4. A data recovery device is applied to a data platform, wherein the data platform is deployed on a server, and the data recovery device comprises:
the data to be recovered determining module is used for responding to the data recovery operation of the user to determine the data to be recovered;
a restoration path obtaining module, configured to determine a restoration path of the data to be restored according to data restoration related content in the information configured by the user;
the data recovery module is used for controlling a recovery tool to send data to be recovered to a target database through the recovery path, the recovery tool is deployed in a front-end processor, and the front-end processor is configured between the data platform and a server of the user;
wherein the user configured information is determined according to the information to be configured in claim 3;
the data recovery apparatus further includes:
controlling the front-end processor to receive a recovery log in the data recovery process;
responding to the received request for checking the recovery log, and acquiring the recovery log from the front-end processor;
generating a display interface of the data recovery process on the data platform based on the recovery log;
and sending alarm information to carry out a manual recovery process if the data recovery fails and/or the recovery log is abnormal.
5. A storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the data backup method of claim 1 or the data recovery method of claim 2.
6. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the data backup method of claim 1 or the data recovery method of claim 2 via execution of the executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711015595.8A CN107797887B (en) | 2017-10-26 | 2017-10-26 | Data backup and recovery method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711015595.8A CN107797887B (en) | 2017-10-26 | 2017-10-26 | Data backup and recovery method and device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107797887A CN107797887A (en) | 2018-03-13 |
| CN107797887B true CN107797887B (en) | 2021-03-23 |
Family
ID=61547823
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711015595.8A Active CN107797887B (en) | 2017-10-26 | 2017-10-26 | Data backup and recovery method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107797887B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111045857B (en) * | 2018-10-12 | 2023-11-28 | 伊姆西Ip控股有限责任公司 | Method for data backup and recovery, electronic device and computer readable storage medium |
| CN111045862B (en) * | 2019-10-25 | 2022-12-16 | 苏州浪潮智能科技有限公司 | User data management method and device |
| CN113127259B (en) * | 2019-12-30 | 2024-03-12 | 北京懿医云科技有限公司 | Data deployment method, device, equipment and storage medium |
| CN112579363B (en) * | 2020-12-30 | 2023-02-03 | 上海爱数信息技术股份有限公司 | MySQL data protection system and backup and recovery method thereof |
| CN113535478B (en) * | 2021-07-15 | 2024-01-02 | 天翼云科技有限公司 | Data backup method and device, storage medium and electronic equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103092718A (en) * | 2011-10-27 | 2013-05-08 | 鸿富锦精密工业（深圳）有限公司 | Test data backup system and method |
| US9098432B1 (en) * | 2008-04-08 | 2015-08-04 | Emc Corporation | System and method for data deduplication of backup images |
| CN105159943A (en) * | 2015-08-07 | 2015-12-16 | 北京思特奇信息技术股份有限公司 | Automatic backup method and system for distributed database |
| CN106909475A (en) * | 2015-12-23 | 2017-06-30 | 中国移动通信集团重庆有限公司 | Row data backup, the method and apparatus recovered are stored in based on object |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8676763B2 (en) * | 2011-02-08 | 2014-03-18 | International Business Machines Corporation | Remote data protection in a networked storage computing environment |
-
2017
- 2017-10-26 CN CN201711015595.8A patent/CN107797887B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9098432B1 (en) * | 2008-04-08 | 2015-08-04 | Emc Corporation | System and method for data deduplication of backup images |
| CN103092718A (en) * | 2011-10-27 | 2013-05-08 | 鸿富锦精密工业（深圳）有限公司 | Test data backup system and method |
| CN105159943A (en) * | 2015-08-07 | 2015-12-16 | 北京思特奇信息技术股份有限公司 | Automatic backup method and system for distributed database |
| CN106909475A (en) * | 2015-12-23 | 2017-06-30 | 中国移动通信集团重庆有限公司 | Row data backup, the method and apparatus recovered are stored in based on object |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107797887A (en) | 2018-03-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107797887B (en) | Data backup and recovery method and device, storage medium and electronic equipment | |
| US11221939B2 (en) | Managing data from internet of things devices in a vehicle | |
| US8510720B2 (en) | System landscape trace | |
| US8661291B2 (en) | Diagnosing a fault incident in a data center | |
| US8640096B2 (en) | Configuration of componentized software applications | |
| US20100306486A1 (en) | Policy-based application aware storage array snapshot backup and restore technique | |
| US20190138375A1 (en) | Optimization of message oriented middleware monitoring in heterogenenous computing environments | |
| CN108984544B (en) | Method and device for modifying configuration information of distributed system | |
| US20130111018A1 (en) | Passive monitoring of virtual systems using agent-less, offline indexing | |
| US20190347245A1 (en) | Determining when a change set was delivered to a workspace or stream and by whom | |
| CN111026572A (en) | Fault processing method and device of distributed system and electronic equipment | |
| US11640547B2 (en) | Configuration assessment based on inventory | |
| CN110062926A (en) | Device driver telemetering | |
| CN107918564B (en) | Data transmission exception handling method and device, electronic equipment and storage medium | |
| CN110765090B (en) | Log data management method and device, storage medium and electronic equipment | |
| CN109885431B (en) | Method and apparatus for backing up data | |
| CN109299124B (en) | Method and apparatus for updating a model | |
| US11418573B1 (en) | File transfer abstraction on a computer network | |
| US11334446B2 (en) | Backup system for an overlay network | |
| CN109062599A (en) | The management method and device of code update under micro services framework | |
| CN113467941A (en) | Method and device for sharing information | |
| CN114398061A (en) | Publishing method, device, equipment and storage medium | |
| US11061725B2 (en) | Managing a set of computing resources | |
| CN113094211B (en) | Backup data processing method and device | |
| US10977210B2 (en) | Methods for implementing an administration and testing tool |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |