CN106569920B - Database backup method and device - Google Patents
Database backup method and device Download PDFInfo
- Publication number
- CN106569920B CN106569920B CN201610988896.8A CN201610988896A CN106569920B CN 106569920 B CN106569920 B CN 106569920B CN 201610988896 A CN201610988896 A CN 201610988896A CN 106569920 B CN106569920 B CN 106569920B
- Authority
- CN
- China
- Prior art keywords
- backup
- database
- configuration information
- time
- command
- 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
- 238000000034 method Methods 0.000 title claims abstract description 53
- 230000014759 maintenance of location Effects 0.000 claims description 31
- 230000015654 memory Effects 0.000 claims description 17
- 238000001514 detection method Methods 0.000 claims description 12
- 238000012545 processing Methods 0.000 claims description 7
- 238000012790 confirmation Methods 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims 2
- 238000005516 engineering process Methods 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 10
- 230000005540 biological transmission Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000005034 decoration Methods 0.000 description 2
- 230000003203 everyday effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000000737 periodic effect Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/80—Database-specific techniques
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a database backup method and a database backup device. Wherein, the method comprises the following steps: receiving configuration information uploaded by a client, wherein the configuration information is used for indicating backup operation on a database on a server; adding a backup command for indicating a backup operation on the database into a target file according to the received configuration information, wherein the target file is used for setting a periodically executed command; detecting whether a predetermined execution time for executing the backup command added to the target file is reached; and after detecting that the preset execution time is reached, executing a backup command in the target file to perform backup operation on the database. The invention solves the technical problems of high labor cost, inflexible use and inconvenient operation caused by adopting a manual database backup mode in the related technology.
Description
Technical Field
The invention relates to the field of databases, in particular to a database backup method and a database backup device.
Background
In the related technology, the Database backup mainly depends on a DBA (Database Administrator, which is a general name of related staff engaged in managing and maintaining a Database management system (DBMS)) to directly operate Database management software, and manually configure and complete the backup of the Database at the server end.
In view of the above problems, no effective solution has been proposed.
Disclosure of Invention
The embodiment of the invention provides a database backup method and device, which at least solve the technical problems of high labor cost, inflexible use and inconvenient operation caused by a manual database backup mode in the related art.
According to an aspect of an embodiment of the present invention, there is provided a database backup method, including: receiving configuration information uploaded by a client, wherein the configuration information is used for indicating backup operation on a database on a server; adding a backup command for indicating a backup operation on the database into a target file according to the received configuration information, wherein the target file is used for setting a periodically executed command; detecting whether a predetermined execution time for executing the backup command added to the target file is reached; and after detecting that the preset execution time is reached, executing a backup command in the target file to perform backup operation on the database.
According to another aspect of the embodiments of the present invention, there is also provided a database backup apparatus, including: the system comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving configuration information uploaded by a client, and the configuration information is used for indicating the backup operation of a database on a server; the adding unit is used for adding a backup command for indicating the backup operation of the database into a target file according to the received configuration information, wherein the target file is used for setting a periodically executed command; a first detection unit configured to detect whether a predetermined execution time to execute the backup command added to the target file is reached; and the backup unit is used for executing the backup command in the target file after detecting that the preset execution time is reached so as to perform backup operation on the database.
In the embodiment of the invention, a mode of automatically backing up a database is adopted, and configuration information uploaded by a client is received on a server, wherein the configuration information is used for indicating the backup operation of the database on the server; adding a backup command for indicating a backup operation on the database into a target file according to the received configuration information, wherein the target file is used for setting a periodically executed command; detecting whether a predetermined execution time for executing the backup command added to the target file is reached; after the preset execution time is detected, the backup command in the target file is executed to perform backup operation on the database, and the target file is used for setting the periodically executed command, so that the server can automatically execute the backup command in the target file after the preset execution time is reached, and the aim of automatically backing up the database is fulfilled, thereby achieving the technical effects of reducing the labor cost and improving the flexibility and convenience of use, and further solving the technical problems of high labor cost, insufficient flexibility in use and insufficient convenience in operation caused by the adoption of a manual database backup mode in the related art.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a schematic diagram of a hardware environment for a database backup method according to an embodiment of the present invention;
FIG. 2 is a flow diagram of an alternative database backup method according to an embodiment of the present invention;
FIG. 3(a) is a diagram illustrating an alternative warning of database backup failure according to an embodiment of the invention;
FIG. 3(b) is a diagram illustrating an alternative warning of database backup failure according to an embodiment of the invention;
FIG. 4 is an architecture diagram of an alternative database backup system according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of an alternative implementation of database backup according to an embodiment of the invention;
FIG. 6 is a schematic diagram of an alternative database backup appliance, according to an embodiment of the present invention;
FIG. 7 is a schematic diagram of an alternative database backup appliance, according to an embodiment of the present invention;
FIG. 8 is a schematic diagram of an alternative database backup appliance, according to an embodiment of the present invention;
FIG. 9 is a schematic diagram of an alternative database backup appliance, according to an embodiment of the present invention;
FIG. 10 is a schematic diagram of an alternative database backup appliance, according to an embodiment of the present invention;
FIG. 11 is a schematic diagram of an alternative database backup appliance, according to an embodiment of the present invention; and
fig. 12 is a block diagram of a terminal according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. 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.
First, partial terms or terms appearing in the description of the embodiments of the present invention are applied to the following explanations:
DBA: namely, Database Administrator, is a general term for the staff involved in managing and maintaining a Database management system (DBMS).
RTX: the software is an enterprise-level real-time communication platform and aims to improve the working efficiency and reduce the communication cost.
Example 1
According to an embodiment of the present invention, an embodiment of a method for database backup is provided.
Alternatively, in the present embodiment, the database backup method may be applied to a hardware environment formed by the server 102 and the terminal 104 as shown in fig. 1. As shown in fig. 1, a server 102 is connected to a terminal 104 via a network including, but not limited to: the terminal 104 is not limited to a PC, a mobile phone, a tablet computer, etc. in a wide area network, a metropolitan area network, or a local area network. The database backup method according to the embodiment of the present invention may be executed by the server 102, or executed by the terminal 104, or executed by both the server 102 and the terminal 104. The database backup method of the embodiment of the present invention executed by the terminal 104 may also be executed by a client installed thereon.
Fig. 2 is a flow chart of an alternative database backup method according to an embodiment of the present invention, which may include the following steps, as shown in fig. 2:
step S202, receiving configuration information uploaded by a client, wherein the configuration information is used for indicating the backup operation of a database on a server;
step S204, adding a backup command for indicating the backup operation of the database into a target file according to the received configuration information, wherein the target file is used for setting a periodically executed command;
step S206, detecting whether the preset execution time for executing the backup command added into the target file is reached;
and step S208, after the preset execution time is detected to be reached, executing a backup command in the target file to perform backup operation on the database.
Through the steps S202 to S208, after the client configures the configuration information through the page, receiving the configuration information uploaded by the client on the server, where the configuration information is used to instruct to perform a backup operation on the database on the server; adding a backup command for indicating a backup operation on the database into a target file according to the received configuration information, wherein the target file is used for setting a periodically executed command; detecting whether a predetermined execution time for executing the backup command added to the target file is reached; after the preset execution time is detected, the backup command in the target file is executed to perform backup operation on the database, so that the technical problems of high labor cost, insufficient flexibility in use and insufficient convenience in operation caused by the adoption of a manual database backup mode in the related technology can be solved, and the technical effects of saving the labor cost and improving the flexibility in use and the convenience in operation are achieved.
In the technical solution provided in step S202, in implementation, a user configures configuration information for instructing a backup operation on a certain database on a server through a configuration page at a client, and then the client uploads the configuration information to the server, and the server executes a related database backup operation after receiving the configuration information uploaded by the client.
It should be noted that, in the present invention, the backup management of the database can be performed by the database development and management personnel, and when the backup management is implemented, only simple configuration needs to be performed on the backup center (such as the client), and the relevant backup parameters are specified, so that the server can automatically backup the corresponding database at the specified time.
In the technical solution provided in step S204, in implementation, a time file (e.g., a crontab file) may be designed at the server side and is used as a target file, and taking the crontab file as an example, because the crontab file is used to set a command that is periodically executed, after receiving configuration information, the server adds a script file (i.e., a backup command) for instructing a backup operation on the database to the crontab file based on the configuration information, and specifies a backup period and a backup time, and the like, so that the server automatically backs up the database each time the specified backup time is reached, thereby overcoming a defect that data needs to be manually backed up in the related art.
In the technical solution provided in step S206, when implemented, the system can detect whether the predetermined execution time for executing the backup command added to the target file (i.e. the backup time in the designated backup period) is reached in real time
In the technical solution provided in step S208, in implementation, if the detection result is yes, the backup command in the crontab file is executed to perform a backup operation on the database; and in the case that the detection result is negative, not performing any backup operation, namely not performing the backup command in the crontab file, and not performing any backup operation on the database.
As an alternative embodiment, after step S202, that is, after the configuration information uploaded by the client is received on the server, the method may further include:
step S210, setting a predetermined execution time for executing the backup command in the target file according to the received configuration information.
It should be noted that the predetermined execution time may be periodic, and specifically, may be a specified time in each period. For example, when database a is backed up, the database backup operation may be performed once a day, that is, the backup period is set to 24 hours, and an arbitrary time may be specified as the backup time in each backup period, for example, the backup time is set to 4AM every day.
The embodiment of the invention can meet the requirement of user-defined database backup time.
As an alternative embodiment, the target file may include: a crontab time file. The crontab time file is a crontab file, which is a time file and can be used for setting a command to be executed periodically. In this way, after the script file for executing the database backup operation is added to the file, the server may periodically backup the corresponding database according to the predetermined execution time established in advance.
As an optional embodiment, the configuration information at least includes library configuration information of a database, where before receiving, on the server, configuration information uploaded by the client, the method may further include: step S212, the client configures the configuration information through a page, and the step may include:
step S214, the client receives configuration parameters input by the user, where the configuration parameters include library configuration parameters of at least one of the following: a backup period, a backup time, a backup retention time;
step S216, the client configures the ex-warehouse configuration information on the page according to the warehouse configuration parameters.
Because the data structure of database mainly has 2, respectively: since the database itself and the data tables in the database are used, at least the library configuration is required when the data is configured for backup, and in addition, the table configuration can be performed. When only library configuration is carried out, the data tables in the database need to be backed up by default; when the library configuration and the table configuration are performed simultaneously, only the data table to be configured (i.e. the data table with the table configuration already performed) in the database is backed up.
It should be noted that the backup cycle refers to how often the database is backed up; the backup time refers to the time point at which the database is backed up in each backup period; the backup retention time refers to a retention time of the backup command added to the target file in the target file. For example, for a certain database, the following may be set: the backup period is one day, the backup time is 4AM, and the backup retention time is 3 months, so that the server can execute the backup operation on the database at the time of 4AM every day within the validity period of 3 months, and the corresponding database backup operation cannot be executed at other times.
Specifically, when configuring the database backup information, the database manager operates in units of databases to configure information such as the account host of each database. The library configuration is the definition of the backup information of the database, and mainly comprises 3 attributes, which are respectively: a backup period, i.e. a period of intervals between backups; the backup time, namely the specific time of backup; the backup retention time means that the backup is automatically deleted when the retention time is exceeded.
As an optional embodiment, the configuration information further includes table configuration information of a data table to be backed up in the database, where after step S216, that is, after the client configures the ex-warehouse configuration information on the page according to the configuration parameters, the method may further include:
step S218, the client configures table configuration information of the data table to be backed up on the page according to the table configuration parameters in the configuration parameters, where the table configuration parameters include at least one of the following: the database to which the backup request belongs, the name of the data table and the confirmation parameter of the backup requirement.
In this case, when the backup of the database is configured relatively, the user is allowed to configure the data tables which the user wants to configure according to the needs of the user, so that the flexibility of database backup is increased.
In the embodiment of the present invention, a manner of configuring both two main parts (i.e., the database itself and the data tables in the database) in the data structure of the database is adopted, that is, both the library configuration and the table configuration are performed, where the library configuration process is similar to the library configuration in the above embodiment and is not described herein again, and the table configuration is specifically as follows: after the database information is configured (i.e., the database configuration is completed), the manager of the database can configure the data table of the database, and can configure the data table to be backed up in the corresponding database. The table configuration is used for controlling data tables needing to be backed up in the database, and the data table or the data tables mainly comprise 3 attributes which are respectively as follows: the database to which the database belongs is configured with a numerical identifier of the corresponding database; the name of the data table, namely the name of the data table in the database; whether a backup is needed, i.e. to mark whether the table needs to be backed up.
The embodiment of the invention can meet the requirement of customizing the data table to be backed up in the database by a user.
As an alternative embodiment, after step S204, that is, after adding a backup command for instructing a backup operation on the database to the target file according to the received configuration information, the method may further include:
step S220, detecting whether the backup retention time of the backup command added into the target file is up to delete;
in step S222, after detecting that the backup retention time is reached, the backup command is deleted from the target file to prohibit continuing the backup operation on the database.
That is, in implementation, after adding a backup command for backing up a certain database into a target file according to configuration information uploaded by a client, the server may delete the backup command from the target file after the backup retention time is reached, so that the database can perform corresponding database backup operation within an effective time (i.e., the backup retention time). For example, for the database a, the user actually wants to backup within three months of 10-12 months of a year, and after 12 months of the year, the database is not backed up, so that with the above technical solution, the relevant backup script of the database can be deleted from the target file after the time reaches 12 months of the year.
The embodiment of the invention can meet the requirement of backup retention time of the user-defined database.
As an alternative embodiment, after step S208, that is, after executing the backup command in the target file to perform the backup operation on the database, the method may further include:
step S224, detecting the state of the backup script file and/or the return value of the execution backup command;
step S226, judging whether the database fails to be backed up according to the detection result;
in step S228, after the database backup failure is determined, an alarm interface is called to alarm to notify the user that the database backup failure occurs.
That is, in implementation, whether the database is failed to be backed up may be determined by only detecting the state of the backup script file (i.e., the script corresponding to the backup command), or by only detecting the return value of the backup command, or by detecting both the state of the backup script file (i.e., the script corresponding to the backup command) and the return value of the backup command. Wherein, if the backup is successful, no processing is carried out; and if the backup fails, alarming. Specifically, when the backup fails, a corresponding alarm interface may be called to notify the user that the database backup fails. The alarm notification may include various forms, which are not described in detail herein, wherein fig. 3(a) and fig. 3(b) respectively show two alarm manners for reference, that is, the relevant person is notified by RTX and mail after the backup failure.
The invention is illustrated in detail below in a specific example:
since database backup requires support for both specific data structures and specific procedures. The data structure is used for defining relevant configuration information indicating the backup operation, and the process is used for defining a control process and an interactive process of the whole backup process. The following describes the implementation of data structure and flow and backup respectively:
a data structure
The data structure mainly includes 2, library configuration and table configuration, which are introduced as follows:
(1) library configuration
When configuring the database backup, the database management personnel operates in the unit of the database and configures information such as an account host of each database. The library configuration is the definition of the backup information of the database, and mainly comprises 3 attributes, which are respectively: a backup period, i.e. a period of intervals between backups; the backup time, namely the specific time of backup; the backup retention time means that the backup is automatically deleted when the retention time is exceeded.
(2) Table configuration
After the configuration information of the database is configured, the manager of the database can perform the related configuration of the data table on the database, that is, configure the data table to be backed up in the corresponding database. The table configuration is used for controlling a data table which needs to be backed up in a database, and mainly comprises 3 attributes which are respectively as follows: the database to which the database belongs is a database configuration corresponding to the numerical identification of the database; the name of the data table, namely the name of the data table in the database; whether a backup is needed, i.e. to mark whether the table needs to be backed up.
Two control flow
The configuration process of the whole database backup is based on the two data structures (namely library configuration and table configuration) defined above, and involves two modules, namely a background server (namely a server) and a TV client, and the interaction between the modules is shown in FIG. 4. The whole process consists of the following steps: 1) a manager of the database configures configuration information when the database is backed up through a webpage; 2) a background backup server (server for short) receives relevant configuration information, operates a crontab file (target file) according to the received configuration information, and adds a statement (backup command) of an automatic backup database in the crontab file according to the configuration information; 3) executing a related backup command in the crontab file when a preset backup time is reached so as to backup the corresponding database; 4) if the backup fails, RTX and/or mail inform the manager of the relevant database; 5) in this process the TV client can interact normally with the database through the CGI.
Triple backup implementation
When the server performs backup operation on the database on the server, the backup purpose is realized by combining a backup command provided by the database according to the library configuration information and the table configuration information configured by the user. In order to ensure the safety of the system, the invention adopts the shell script (namely the backup command) which is automatically added with the backup in the crontab task and the shell script which is automatically deleted with the backup, and automatically executes the backup command added into the crontab file at the appointed time to realize the backup. The specific implementation mode is as follows:
1) after a manager of the database configures configuration information for backing up data tables in the database through a configuration page, the server can create a shell script file according to the configuration information, wherein the shell script file corresponds to the database one by one and is used for backing up a specified data table of a specified database, the shell script file is written into a crontab file of the server after being created, and parameters such as execution time, execution period and the like are carried.
2) The basic principle of overtime backup deletion is to create a shell script, which is used for traversing each crottab file in a backup folder, acquiring the creation time of the crottab file, calculating the difference between the creation time and the current time, and deleting the file if the difference exceeds the retention time (namely the backup retention time) of the configured backup file. The shell script needs to provide two parameters, namely a backup folder path and backup file retention time. After the library configuration is completed, the system automatically creates a shell according to the configuration and adds the shell into the crontab file for periodic execution.
3) After executing the backup command, the backup script will check the return value of the backup command and the status of the backup file, if the backup failure is found, call the related alarm interface, notify the creator and manager of the database of the backup failure that the database of the backup failure is failed, and alarm as shown in fig. 3(a) and fig. 3 (b).
By the embodiment of the invention, a self-managed database backup center solution is provided based on table configuration and library configuration; according to the configuration information, the solution of automatic backup and backup file management is realized by using the crontab + shell file, as shown in fig. 5; when the backup fails, an alarm is automatically given through RTX and/or mail.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
Example 2
According to the embodiment of the invention, the database backup device for implementing the database backup method is also provided. Fig. 6 is a schematic diagram of an alternative database backup apparatus according to an embodiment of the present invention, as shown in fig. 6, the apparatus may include: a receiving unit 602, configured to receive configuration information uploaded by a client, where the configuration information is used to indicate that a backup operation is performed on a database on a server; an adding unit 604, configured to add a backup command for instructing a backup operation on a database to a target file according to the received configuration information, where the target file is used to set a command that is executed periodically; a first detecting unit 606 for detecting whether a predetermined execution time for executing the backup command added to the target file is reached; and the backup unit 608 is used for executing the backup command in the target file to perform a backup operation on the database after detecting that the predetermined execution time is reached.
It should be noted that the receiving unit 602 in this embodiment may be configured to execute step S202 in embodiment 1 of this application, the adding unit 604 in this embodiment may be configured to execute step S204 in embodiment 1 of this application, the detecting unit 606 in this embodiment may be configured to execute step S206 in embodiment 1 of this application, and the backup unit 608 in this embodiment may be configured to execute step S208 in embodiment 1 of this application.
It should be noted here that the above units are the same as the examples and application scenarios realized by the corresponding steps, but are not limited to the disclosure of the above embodiment 1. It should be noted that the above units may operate in a hardware environment as shown in fig. 1 as a part of the apparatus, and may be implemented by software or hardware.
As an alternative embodiment, as shown in fig. 7, the apparatus may further include: the setting unit 702 is configured to, after receiving the configuration information uploaded by the client, set a predetermined execution time for executing the backup command in the target file according to the received configuration information.
It should be noted that the setting unit 702 in this embodiment may be used to execute step S210 in embodiment 1 of the present application.
It should be noted here that the above units are the same as the examples and application scenarios realized by the corresponding steps, but are not limited to the disclosure of the above embodiment 1. It should be noted that the above units may operate in a hardware environment as shown in fig. 1 as a part of the apparatus, and may be implemented by software or hardware.
As an alternative embodiment, the object file includes: a crontab time file.
As an alternative embodiment, as shown in fig. 8, the configuration information at least may include library configuration information of a database, where the apparatus may further include: the configuration unit 802 is configured to, before receiving the configuration information uploaded by the client on the server, enable the client to configure the configuration information through a page, and further, the configuration unit 802 may include: a receiving module 8022, configured to receive, by the client, configuration parameters input by a user, where the configuration parameters include library configuration parameters of at least one of: a backup period, a backup time, a backup retention time; the first configuration module 8024 is configured to configure, by the client, the ex-warehouse configuration information on the page according to the library configuration parameter.
It should be noted that the configuration unit 802 in this embodiment may be configured to execute step S212 in embodiment 1 of this application, the receiving module 8022 in this embodiment may be configured to execute step S214 in embodiment 1 of this application, and the first configuration module 8024 in this embodiment may be configured to execute step S216 in embodiment 1 of this application.
It should be noted here that the modules/units described above are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of embodiment 1 described above. It should be noted that the modules/units described above as a part of the apparatus may operate in a hardware environment as shown in fig. 1, and may be implemented by software or hardware.
As an alternative embodiment, as shown in fig. 9, the configuration information may further include table configuration information of a data table to be backed up in a database, where the configuration unit 802 may further include: a second configuration module 902, configured to, after the client configures the ex-warehouse configuration information on the page according to the configuration parameters, configure, by the client, table configuration information of the data table to be backed up on the page according to the table configuration parameters in the configuration parameters, where the table configuration parameters include at least one of: the database to which the backup request belongs, the name of the data table and the confirmation parameter of the backup requirement.
It should be noted that the second configuration module 902 in this embodiment may be configured to execute step S218 in embodiment 1 of this application.
It should be noted here that the modules described above are the same as the examples and application scenarios implemented by the corresponding steps, but are not limited to the disclosure of embodiment 1 described above. It should be noted that the modules described above as a part of the apparatus may operate in a hardware environment as shown in fig. 1, and may be implemented by software or hardware.
As an alternative embodiment, as shown in fig. 10, the apparatus may further include: a second detecting unit 1002, configured to detect whether a backup retention time for deleting a backup command added to a target file is reached after adding the backup command for instructing a backup operation on a database to the target file according to the received configuration information; a deleting unit 1004, configured to delete the backup command from the target file to prohibit continuation of the backup operation on the database after detecting that the backup retention time is reached.
It should be noted that the second detecting unit 1002 in this embodiment may be configured to execute step S220 in embodiment 1 of this application, and the deleting unit 1004 in this embodiment may be configured to execute step S222 in embodiment 1 of this application.
It should be noted here that the above units are the same as the examples and application scenarios realized by the corresponding steps, but are not limited to the disclosure of the above embodiment 1. It should be noted that the above units may operate in a hardware environment as shown in fig. 1 as a part of the apparatus, and may be implemented by software or hardware.
As an alternative embodiment, as shown in fig. 11, the apparatus may further include: a third detecting unit 1102, configured to detect a state of the backup script file and/or a return value of the backup command after the backup command in the target file is executed to perform a backup operation on the database; a judging unit 1104, configured to judge whether the database fails to be backed up according to the detection result; an alarm unit 1106, configured to call an alarm interface to alarm after determining that the database backup fails, so as to notify a user that the database backup fails.
It should be noted that the third detecting unit 1102 in this embodiment may be configured to execute step S224 in embodiment 1 of this application, the determining unit 1104 in this embodiment may be configured to execute step S226 in embodiment 1 of this application, and the warning unit 1106 in this embodiment may be configured to execute step S228 in embodiment 1 of this application.
It should be noted here that the above units are the same as the examples and application scenarios realized by the corresponding steps, but are not limited to the disclosure of the above embodiment 1. It should be noted that the above units may operate in a hardware environment as shown in fig. 1 as a part of the apparatus, and may be implemented by software or hardware.
Through the module, the technical problems of high labor cost, insufficient flexibility in use and insufficient convenience in operation caused by the adoption of a manual database backup mode in the related technology can be solved, and the technical effects of saving the labor cost and improving the flexibility in use and the convenience in operation are achieved.
Example 3
According to the embodiment of the invention, the invention also provides a server or a terminal for implementing the database backup method.
Fig. 12 is a block diagram of a terminal according to an embodiment of the present invention, and as shown in fig. 12, the terminal may include: one or more processors 201 (only one is shown), a memory 203, and a transmission device 205 (such as the transmission device in the above embodiment), as shown in fig. 12, the terminal may further include an input/output device 207.
The memory 203 may be used to store software programs and modules, such as program instructions/modules corresponding to the database backup method and apparatus in the embodiments of the present invention, and the processor 201 executes various functional applications and data processing by running the software programs and modules stored in the memory 203, that is, implementing the above-described database backup method. The memory 203 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 203 may further include memory located remotely from the processor 201, which may be connected to the terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device 205 is used for receiving or sending data via a network, and can also be used for data transmission between a processor and a memory. Examples of the network may include a wired network and a wireless network. In one example, the transmission device 205 includes a Network adapter (NIC) that can be connected to a router via a Network cable and other Network devices to communicate with the internet or a local area Network. In one example, the transmission device 205 is a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
Wherein the memory 203 is specifically used for storing application programs.
The processor 201 may call the application stored in the memory 203 via the transmission means 205 to perform the following steps: receiving configuration information uploaded by a client, wherein the configuration information is used for indicating backup operation on a database on a server; adding a backup command for indicating a backup operation on the database into a target file according to the received configuration information, wherein the target file is used for setting a periodically executed command; detecting whether a predetermined execution time for executing the backup command added to the target file is reached; and after detecting that the preset execution time is reached, executing a backup command in the target file to perform backup operation on the database.
The processor 201 is further configured to perform the following steps: after receiving the configuration information uploaded by the client, setting a preset execution time for executing the backup command in the target file according to the received configuration information.
The processor 201 is further configured to perform the following steps: the configuration information at least includes library configuration information of a database, wherein before receiving configuration information uploaded by a client, the client configures the configuration information through a page, and the configuring of the configuration information by the client through the page may include: the client receives configuration parameters input by a user, wherein the configuration parameters comprise library configuration parameters of at least one of the following: a backup period, a backup time, a backup retention time; and the client configures the ex-warehouse configuration information on the page according to the warehouse configuration parameters.
The processor 201 is further configured to perform the following steps: the configuration information further includes table configuration information of a data table to be backed up in the database, wherein after the client configures the library configuration information on the page according to the configuration parameters, the client configures the table configuration information of the data table to be backed up on the page according to the table configuration parameters in the configuration parameters, wherein the table configuration parameters include at least one of the following: the database to which the backup request belongs, the name of the data table and the confirmation parameter of the backup requirement.
The processor 201 is further configured to perform the following steps: after adding a backup command for indicating the backup operation of the database into the target file according to the received configuration information, detecting whether the backup retention time for deleting the backup command added into the target file is reached; and after detecting that the backup retention time is reached, deleting the backup command from the target file to prohibit the database from continuing to be subjected to backup operation.
The processor 201 is further configured to perform the following steps: after executing the backup command in the target file to perform backup operation on the database, detecting the state of the backup script file and/or executing a return value of the backup command; judging whether the database fails to be backed up or not according to the detection result; and after judging that the database backup fails, calling an alarm interface to alarm so as to inform a user of the database backup failure.
The embodiment of the invention provides a database backup scheme. Receiving configuration information uploaded by a client, wherein the configuration information is used for indicating backup operation on a database on a server; adding a backup command for indicating a backup operation on the database into a target file according to the received configuration information, wherein the target file is used for setting a periodically executed command; detecting whether a predetermined execution time for executing the backup command added to the target file is reached; after the preset execution time is detected, the backup command in the target file is executed to perform backup operation on the database, so that the aim of automatically backing up the database is fulfilled, the technical effects of saving labor cost and improving the use flexibility and the operation convenience are achieved, and the technical problems of high labor cost, insufficient flexibility in use and insufficient convenience in operation caused by the adoption of a manual database backup mode in the related art are solved.
Optionally, the specific examples in this embodiment may refer to the examples described in embodiment 1 and embodiment 2, and this embodiment is not described herein again.
It can be understood by those skilled in the art that the structure shown in fig. 12 is only an illustration, and the terminal may be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, and a Mobile Internet Device (MID), a PAD, etc. Fig. 12 is a diagram illustrating a structure of the electronic device. For example, the terminal may also include more or fewer components (e.g., network interfaces, display devices, etc.) than shown in FIG. 12, or have a different configuration than shown in FIG. 12.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.
Example 4
The embodiment of the invention also provides a storage medium. Alternatively, in this embodiment, the storage medium may be a program code for executing the database backup method.
Optionally, in this embodiment, the storage medium may be located on at least one of a plurality of network devices in a network shown in the above embodiment.
Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps:
s1, receiving configuration information uploaded by the client, wherein the configuration information is used for indicating the backup operation of the database on the server;
s2, adding a backup command for indicating the backup operation of the database into the target file according to the received configuration information, wherein the target file is used for setting a command which is executed periodically;
s3, detecting whether the preset execution time for executing the backup command added into the target file is reached;
and S4, executing the backup command in the target file to perform backup operation on the database after detecting that the preset execution time is reached.
Optionally, the storage medium is further arranged to store program code for performing the steps of: after receiving the configuration information uploaded by the client, setting a preset execution time for executing the backup command in the target file according to the received configuration information.
Optionally, the storage medium is further arranged to store program code for performing the steps of: the configuration information at least includes library configuration information of a database, wherein before receiving configuration information uploaded by a client, the client configures the configuration information through a page, and the configuring of the configuration information by the client through the page may include: the client receives configuration parameters input by a user, wherein the configuration parameters comprise library configuration parameters of at least one of the following: a backup period, a backup time, a backup retention time; and the client configures the ex-warehouse configuration information on the page according to the warehouse configuration parameters.
Optionally, the storage medium is further arranged to store program code for performing the steps of: the configuration information further includes table configuration information of a data table to be backed up in the database, wherein after the client configures the library configuration information on the page according to the configuration parameters, the client configures the table configuration information of the data table to be backed up on the page according to the table configuration parameters in the configuration parameters, wherein the table configuration parameters include at least one of the following: the database to which the backup request belongs, the name of the data table and the confirmation parameter of the backup requirement.
Optionally, the storage medium is further arranged to store program code for performing the steps of: after adding a backup command for indicating the backup operation of the database into the target file according to the received configuration information, detecting whether the backup retention time for deleting the backup command added into the target file is reached; and after detecting that the backup retention time is reached, deleting the backup command from the target file to prohibit the database from continuing to be subjected to backup operation.
Optionally, the storage medium is further arranged to store program code for performing the steps of: after executing the backup command in the target file to perform backup operation on the database, detecting the state of the backup script file and/or executing a return value of the backup command; judging whether the database fails to be backed up or not according to the detection result; and after judging that the database backup fails, calling an alarm interface to alarm so as to inform a user of the database backup failure.
Optionally, the specific examples in this embodiment may refer to the examples described in embodiment 1 and embodiment 2, and this embodiment is not described herein again.
Optionally, in this embodiment, the storage medium may include, but is not limited to: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing one or more computer devices (which may be personal computers, servers, network devices, etc.) to execute all or part of the steps of the method according to the embodiments of the present invention.
In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (12)
1. A method for database backup, comprising:
receiving configuration information uploaded by a client, wherein the configuration information is used for indicating backup operation of a database on a server, the configuration information at least comprises library configuration information of the database, and the receiving of the configuration information uploaded by the client comprises: receiving the library configuration information configured on a page by the client according to library configuration parameters in configuration parameters, wherein the configuration parameters comprise the following library configuration parameters: backup retention time;
adding a backup command for indicating a backup operation of the database into a target file according to the received configuration information, wherein the target file is used for setting a periodically executed command, and the target file comprises: a crontab time file;
detecting whether a predetermined execution time for executing the backup command added to the target file is reached;
after detecting that the preset execution time is reached, executing the backup command in the target file to perform backup operation on the database;
after adding a backup command for indicating a backup operation on the database to a target file according to the received configuration information, the method further comprises:
under the condition that a backup folder path and the backup retention time are provided for an automatically deleted backup shell script automatically added into a crottab task, traversing each crottab time file in a backup folder corresponding to the backup folder path through the automatically deleted backup shell script, and acquiring the creation time of each crottab time file;
calculating the difference value between the creation time of each crontab time file and the current time;
and deleting the crontab time file of the backup command to prohibit the database from being continuously backed up under the condition that the difference value between the creation time of the crontab time file of the backup command and the current time exceeds the backup retention time.
2. The method of claim 1, wherein after receiving the configuration information uploaded by the client, the method further comprises:
and setting the preset execution time for executing the backup command in the target file according to the received configuration information.
3. The method of claim 1, wherein the library configuration parameters further comprise: backup cycle, backup time.
4. The method of claim 3, wherein the configuration information further comprises table configuration information of data tables in the database that need to be backed up, and wherein after the client configures the library configuration information on the page according to the configuration parameters, the method further comprises:
the client configures the table configuration information of the data table to be backed up on the page according to the table configuration parameters in the configuration parameters, wherein the table configuration parameters include at least one of the following parameters: the database to which the backup request belongs, the name of the data table and the confirmation parameter of the backup requirement.
5. The method of claim 1, wherein after executing the backup command in the target file to perform a backup operation on the database, the method further comprises:
detecting the state of a backup script file and/or a return value for executing the backup command;
judging whether the database fails to be backed up or not according to the detection result;
and after judging that the database backup fails, calling an alarm interface to alarm so as to inform a user that the database backup fails.
6. A database backup apparatus, comprising:
the system comprises a receiving unit, a processing unit and a processing unit, wherein the receiving unit is used for receiving configuration information uploaded by a client, and the configuration information is used for indicating the backup operation of a database on a server;
an adding unit, configured to add, according to the received configuration information, a backup command for instructing a backup operation on the database to a target file, where the target file is used to set a command that is executed periodically, and the target file includes: a crontab time file;
a first detection unit configured to detect whether a predetermined execution time to execute the backup command added to the target file is reached;
the backup unit is used for executing the backup command in the target file after detecting that the preset execution time is reached so as to perform backup operation on the database;
wherein the configuration information comprises at least library configuration information of the database;
wherein the apparatus further comprises: the configuration unit is used for enabling the client to configure the configuration information through a page before the configuration information uploaded by the client is received;
the configuration unit includes: a receiving module, configured to receive, by the client, configuration parameters input by a user, where the configuration parameters include the following library configuration parameters: backup retention time; the first configuration module is used for the client to configure the library configuration information on the page according to the library configuration parameters;
wherein the apparatus further comprises: a second detection unit, configured to add a backup command for instructing a backup operation on the database to a target file according to the received configuration information, in the case where the backup folder path and the backup retention time are provided to the shell script that automatically deletes the backup that is automatically added to the crontab task, traversing each crottab time file in the backup folder corresponding to the backup folder path through the shell script for automatically deleting the backup, and acquiring the creation time of each crontab time file, calculating the difference value between the creation time of each crontab time file and the current time, in case that the difference between the creation time of the crontab time file where the backup command is located and the current time exceeds the backup retention time, and deleting the crontab time file where the backup command is positioned so as to prohibit the database from being continuously backed up.
7. The apparatus of claim 6, further comprising:
and the setting unit is used for setting the preset execution time for executing the backup command in the target file according to the received configuration information after receiving the configuration information uploaded by the client.
8. The apparatus of claim 6, wherein the configuration parameters further comprise library configuration parameters: backup cycle, backup time.
9. The apparatus of claim 8, wherein the configuration information further comprises table configuration information of data tables in the database that need to be backed up, and wherein the configuration unit further comprises:
a second configuration module, configured to, after the client configures the library configuration information on the page according to the configuration parameter, configure, by the client, the table configuration information of the data table to be backed up on the page according to a table configuration parameter in the configuration parameter, where the table configuration parameter includes at least one of: the database to which the backup request belongs, the name of the data table and the confirmation parameter of the backup requirement.
10. The apparatus of claim 6, further comprising:
the third detection unit is used for detecting the state of a backup script file and/or executing a return value of the backup command after the backup command in the target file is executed to perform backup operation on the database;
the judging unit is used for judging whether the database fails to be backed up according to the detection result;
and the alarm unit is used for calling an alarm interface to alarm after judging that the database backup fails so as to inform a user that the database backup fails.
11. A computer-readable storage medium comprising a stored program, wherein the program when executed performs the method of any of claims 1 to 5.
12. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method of any of claims 1 to 5 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610988896.8A CN106569920B (en) | 2016-11-09 | 2016-11-09 | Database backup method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610988896.8A CN106569920B (en) | 2016-11-09 | 2016-11-09 | Database backup method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106569920A CN106569920A (en) | 2017-04-19 |
| CN106569920B true CN106569920B (en) | 2020-12-11 |
Family
ID=58540998
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610988896.8A Active CN106569920B (en) | 2016-11-09 | 2016-11-09 | Database backup method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106569920B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107230148A (en) * | 2017-05-03 | 2017-10-03 | 上海动联信息技术股份有限公司 | A kind of date determination methods for transaction funds settlement process |
| CN107479859A (en) * | 2017-08-02 | 2017-12-15 | 深圳市易材科技有限公司 | A kind of method using php program execution system orders |
| CN110019229B (en) * | 2017-12-25 | 2022-04-15 | 航天信息股份有限公司 | Database configuration system |
| CN109117305B (en) * | 2018-07-24 | 2022-01-28 | 郑州市景安网络科技股份有限公司 | Data backup method, device and equipment and computer readable storage medium |
| CN109885431B (en) * | 2019-03-06 | 2022-02-25 | 北京百度网讯科技有限公司 | Method and apparatus for backing up data |
| CN112579531A (en) * | 2020-12-15 | 2021-03-30 | 东方电气风电有限公司 | Method for downloading and storing wind power plant data |
| CN113032406B (en) * | 2021-05-26 | 2022-04-15 | 四川新网银行股份有限公司 | Data archiving method for centralized management of sub-tables through metadata database |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102541694A (en) * | 2012-01-18 | 2012-07-04 | 浪潮(北京)电子信息产业有限公司 | Method and device for database backup |
| CN104679612A (en) * | 2015-03-09 | 2015-06-03 | 陈健强 | Automatic backup and restoration method and automatic backup and restoration system for files |
| CN104731827A (en) * | 2013-12-24 | 2015-06-24 | 重庆新媒农信科技有限公司 | Generating method and generating device for file metadata of fast distributed file system |
| CN105550073A (en) * | 2016-03-10 | 2016-05-04 | 世纪龙信息网络有限责任公司 | Database backup method and system thereof |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6745212B2 (en) * | 2001-06-27 | 2004-06-01 | International Business Machines Corporation | Preferential caching of uncopied logical volumes in an IBM peer-to-peer virtual tape server |
| US7769716B2 (en) * | 2007-03-27 | 2010-08-03 | Yahoo! Inc. | Divided backup of data warehouse |
| CN101873457B (en) * | 2009-09-02 | 2013-05-15 | 杭州海康威视数字技术股份有限公司 | DVR (Digital Video Recorder) as well as data backup method and system thereof |
| CN104252485B (en) * | 2013-06-29 | 2017-08-04 | 北京新媒传信科技有限公司 | A kind of database management platform |
| CN105468476B (en) * | 2015-11-18 | 2019-03-08 | 盛趣信息技术（上海）有限公司 | Data disaster recovery and backup systems based on HDFS |
-
2016
- 2016-11-09 CN CN201610988896.8A patent/CN106569920B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102541694A (en) * | 2012-01-18 | 2012-07-04 | 浪潮(北京)电子信息产业有限公司 | Method and device for database backup |
| CN104731827A (en) * | 2013-12-24 | 2015-06-24 | 重庆新媒农信科技有限公司 | Generating method and generating device for file metadata of fast distributed file system |
| CN104679612A (en) * | 2015-03-09 | 2015-06-03 | 陈健强 | Automatic backup and restoration method and automatic backup and restoration system for files |
| CN105550073A (en) * | 2016-03-10 | 2016-05-04 | 世纪龙信息网络有限责任公司 | Database backup method and system thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106569920A (en) | 2017-04-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106569920B (en) | Database backup method and device | |
| CN106713487B (en) | Data synchronization method and device | |
| CN109032824B (en) | Database verification method, database verification device, computer equipment and storage medium | |
| CN106878363B (en) | Information processing method, device and system | |
| CN105373428A (en) | Task scheduling method and system | |
| CN105224441B (en) | Virtual machine information acquisition device, method and virtual machine information maintaining method and system | |
| CN111371645B (en) | Method, system, computer equipment and storage medium for testing service connectivity | |
| CN111008026A (en) | Cluster management method, device and system | |
| CN112596951A (en) | NAS data disaster tolerance method, device, equipment and storage medium | |
| CN111342992A (en) | Method and system for processing equipment information change record | |
| CN105843871B (en) | Control and management system of distributed application files | |
| CN111813282A (en) | Data form display method and device | |
| CN114356654A (en) | Backup system, backup method, backup device, computer device, and storage medium | |
| CN110708177B (en) | Exception handling method, system and device in distributed system | |
| CN105843675B (en) | Thread exit method and device | |
| CN114461445A (en) | Data recovery method and device, electronic equipment and computer readable storage medium | |
| CN110784358A (en) | Method and device for constructing network call relation topological graph | |
| CN112583912A (en) | VPN automatic connection method, device, equipment and storage medium | |
| CN111324504B (en) | Method and device for monitoring running state of power communication network | |
| CN105022663A (en) | Power system monitoring and control system | |
| CN110958287B (en) | Operation object data synchronization method, device and system | |
| CN111008209A (en) | Data account checking method, device and system, storage medium and electronic device | |
| CN110784353A (en) | Network element equipment configuration data migration method and device | |
| CN111327487A (en) | Power communication network running state monitoring method and device based on deep learning | |
| CN113656378A (en) | Server management method, device and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20231013 Address after: 518000 Tencent Building, No. 1 High-tech Zone, Nanshan District, Shenzhen City, Guangdong Province, 35 Floors Patentee after: TENCENT TECHNOLOGY (SHENZHEN) Co.,Ltd. Patentee after: TENCENT CLOUD COMPUTING (BEIJING) Co.,Ltd. Address before: 2, 518000, East 403 room, SEG science and Technology Park, Zhenxing Road, Shenzhen, Guangdong, Futian District Patentee before: TENCENT TECHNOLOGY (SHENZHEN) Co.,Ltd. |
|
| TR01 | Transfer of patent right |