Data backup method and device

Abstract

An embodiment of the present invention provides a data backup method and device, comprising: when a platform receives a target node completion message for a target order, obtaining the to-be-backed-up data corresponding to the target order and the storage time of the to-be-backed-up data from a target business system; when the storage time is less than a preset time threshold, determining a target data identifier corresponding to the data type and / or data source of the to-be-backed-up data; determining a target backup strategy that matches the target data identifier; and backing up the to-be-backed-up data according to the target backup strategy. Through the embodiment of the present invention, targeted data backup is achieved, resource waste during the data backup process is reduced, and important data is ensured to be backed up in a timely manner.

Description

Technical Field

[0001] The present invention relates to the technical field of data backup, and in particular to a data backup method and device. Background Art

[0002] With the continuous development of Internet technology, the Internet can provide more and more services. The same e-commerce business can be provided by different business systems. When the business system provides related services, it will generate corresponding data. In order to avoid the loss of this data, it is necessary to back up this data in real time.

[0003] However, if all data are backed up in real time and completely, the data backup process may consume a lot of resources. Summary of the Invention

[0004] In view of the above problems, a data backup method and apparatus are proposed to overcome or at least partially solve the above problems, including:

[0005] A data backup method, comprising:

[0006] When the platform receives a target node completion message for a target order, it obtains the data to be backed up corresponding to the target order and the storage time of the data to be backed up from the target business system;

[0007] When the storage time is less than a preset time threshold, determining a target data identifier corresponding to the data type and / or data source of the data to be backed up;

[0008] Determine a target backup strategy that matches the target data identifier;

[0009] Back up the data to be backed up according to the target backup strategy.

[0010] Optionally, determining a target data identifier corresponding to a data type and / or a data source of the data to be backed up includes:

[0011] Obtain the data update frequency of the target business system; determine the target data identifier based on the data update frequency;

[0012] and / or, determining a target system identifier of a target business system; determining a target data identifier corresponding to the target system identifier;

[0013] And / or, determining a target service corresponding to the data to be backed up; determining a target service level of the target service, and determining a target data identifier corresponding to the target service level.

[0014] Optionally, the target backup strategy includes a system change backup strategy, and backing up the backup data according to the target backup strategy includes:

[0015] Determine the initiation time of the target order and determine the target time interval based on the initiation time and the time when the target node completion message is received;

[0016] Determine whether the target business system has changed within the target time interval;

[0017] When it is determined that a change has occurred, the data to be backed up is backed up.

[0018] Optionally, determining whether a target business system has changed within a target time interval includes:

[0019] Determine whether the system software package of the target business system has changed within the target time interval; if a change occurs, determine that the target business system has changed;

[0020] And / or, determining whether a system configuration of the target business system changes within a target time interval; and determining that the target business system changes when a change occurs.

[0021] Optionally, the target backup strategy includes an incremental backup strategy. Backing up the backup data according to the target backup strategy includes:

[0022] Identify new data in the data to be backed up that has changed since the last backup of the target business system;

[0023] Back up the newly added data.

[0024] Optionally, the target backup strategy includes a time-sharing backup strategy. Backing up the backup data according to the target backup strategy includes:

[0025] performing incremental backup of the data to be backed up according to a first time interval, and performing full backup of the data to be backed up according to a second time interval;

[0026] The first time interval is smaller than the second time interval.

[0027] Optionally, back up the backup data according to the target backup strategy, including:

[0028] Determine the amount of data to be backed up;

[0029] Adjust the backup time included in the target backup strategy based on the amount of data;

[0030] Back up the data to be backed up according to the adjusted backup time.

[0031] A data backup device, comprising:

[0032] The storage time acquisition module is used to obtain the to-be-backed-up data and the storage time of the to-be-backed-up data corresponding to the target order from the target business system when the platform receives the target node completion message for the target order;

[0033] an identification determination module, configured to determine a target data identification corresponding to a data type and / or a data source of the data to be backed up when the storage time is less than a preset time threshold;

[0034] A backup strategy determination module, configured to determine a target backup strategy that matches a target data identifier;

[0035] The backup module is used to back up the backup data according to the target backup strategy.

[0036] A server includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor. When the computer program is executed by the processor, the above data backup method is implemented.

[0037] A computer-readable storage medium stores a computer program, which implements the above data backup method when executed by a processor.

[0038] The embodiments of the present invention have the following advantages:

[0039] In an embodiment of the present invention, when the platform receives a target node completion message for a target order, it obtains the to-be-backed-up data corresponding to the target order and the storage time of the to-be-backed-up data from the target business system; when the storage time is less than a preset time threshold, it determines a target data identifier corresponding to the data type and / or data source of the to-be-backed-up data; determines a target backup strategy that matches the target data identifier; and backs up the to-be-backed-up data according to the target backup strategy. Through the embodiment of the present invention, targeted data backup is achieved, resource waste in the data backup process is reduced, and important data is ensured to be backed up in a timely manner. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solution of the present invention, the following briefly introduces the drawings required for use in the description of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0041] Figure 1 This is a flowchart of the steps of a data backup method according to an embodiment of the present invention;

[0042] Figure 2 is a flowchart of another data backup method according to an embodiment of the present invention;

[0043] Figure 3 is a flowchart of the steps of another data backup method according to an embodiment of the present invention;

[0044] Figure 4 is a flowchart of the steps of another data backup method according to an embodiment of the present invention;

[0045] Figure 5 It is a structural block diagram of a data backup device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0046] To make the above-mentioned objects, features, and advantages of the present invention more clearly understood, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments described are only a portion of the embodiments of the present invention, not all of them. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of the present invention without inventive effort are also within the scope of protection of the present invention.

[0047] Reference Figure 1 , shows a flowchart of a data backup method according to an embodiment of the present invention, which may specifically include the following steps:

[0048] Step 101: When the platform receives a target node completion message for a target order, it obtains the to-be-backed-up data corresponding to the target order and the storage time of the to-be-backed-up data from the target business system;

[0049] Among them, the target order can refer to an order placed by a user on a platform (such as an e-commerce platform), and the target completion message can refer to a message used to indicate that a certain node in the process of placing the target order has been completed.

[0050] When it is detected that the target order has completed the target node, a target node completion message for the target order can be generated based on this and sent to the platform.

[0051] When the platform receives the target node completion message, it can indicate that the target order has completed the target node; at this time, the business system that provides the business corresponding to the target node can be determined first and used as the target business system.

[0052] The data to be backed up corresponding to the target order can then be retrieved from the target business system. Furthermore, the data to be backed up may have been previously stored. If the data to be backed up has not been backed up for a long time, the risk of complete loss of the data to be backed up may increase. Therefore, the storage time of the data to be backed up can be retrieved from the business system. The storage time may refer to the length of time the data to be backed up has been stored, which is not a limitation in the present embodiment.

[0053] Step 102: When the storage time is less than a preset time threshold, determine a target data identifier corresponding to the data type and / or data source of the data to be backed up;

[0054] As an example, a data type may refer to the type of data to be backed up, which may be determined based on the target business that generates the data to be backed up; a data source may refer to the source of the data to be backed up. In practical applications, different data identifiers may be set for different data types and / or different data sources to distinguish between different data types and / or different data sources.

[0055] After obtaining the storage time, it is possible to first determine whether the data to be backed up has been stored for a long time and has not been backed up based on the storage time. Specifically, a preset time threshold can be set in advance, and the preset time threshold can be set according to actual conditions; thus, when determining whether the data to be backed up has been stored for a long time and has not been backed up, the storage time can be compared with the preset time threshold. If the storage time is less than the preset time threshold, it can be indicated that the data to be backed up has not been stored for a long time.

[0056] In this case, in order to perform different backups for different data, thereby avoiding the situation where important data is not backed up as quickly as possible or unimportant data is frequently backed up, the data type of the data to be backed up can be determined first; of course, the data source of the data to be backed up can also be determined. The data type and data source can be determined simultaneously or alternatively, and this is not limited in this embodiment of the present invention.

[0057] After determining the data type and / or data source, a data identifier corresponding to the data type and / or data source of the data to be backed up can be determined from the data identifiers pre-set for the data type and data source, and used as the target data identifier.

[0058] Step 103: Determine a target backup policy that matches the target data identifier;

[0059] Different data requires different backup strategies. For example, some data only changes when the system changes. In this case, a system change backup strategy can be set for the data type and / or data source corresponding to such data to back up data only when the system changes. The embodiments of the present invention do not limit this.

[0060] In order to facilitate the determination of the backup strategy for the data to be backed up, the correspondence between the data identifier and the backup strategy can be preset; then, when the backup strategy needs to be determined, the target backup strategy corresponding to the target data identifier can be determined from the preset correspondence.

[0061] Step 104: Back up the data to be backed up according to the target backup strategy.

[0062] Then, the determined target backup strategy can be used to back up the data to be backed up, so as to ensure that when the data to be backed up is lost, the data to be backed up can be obtained from the backup, thereby avoiding complete loss of data.

[0063] As an example, you can perform a backup by following these steps:

[0064] Determine the amount of data to be backed up; adjust the backup time included in the target backup strategy based on the amount of data; and back up the data to be backed up according to the adjusted backup time.

[0065] A backup strategy can include a backup time, which is the interval between backups. In practice, larger amounts of data require longer backup times. Setting a longer backup time may result in a longer backup time for all the data to be backed up. Therefore, you can first determine the amount of data to be backed up and then adjust the backup time accordingly. For example, if the data volume is large, you can shorten the backup time to quickly complete the backup.

[0066] After adjusting the backup time, you can use the adjusted backup time to back up the data.

[0067] In an embodiment of the present invention, upon receiving a target node completion message for a target order, the target business system retrieves the data to be backed up corresponding to the target order and the storage time of the data to be backed up. When the storage time is less than a preset time threshold, the target data identifier corresponding to the data type and / or data source of the data to be backed up is determined. A target backup strategy matching the target data identifier is determined. The data to be backed up is backed up according to the target backup strategy. Through the embodiment of the present invention, targeted data backup is achieved, resource waste during the data backup process is reduced, and important data is ensured to be backed up in a timely manner.

[0068] Reference Figure 2 , shows a flowchart of another data backup method according to an embodiment of the present invention, including the following steps:

[0069] Step 201: When the platform receives a target node completion message for a target order, it obtains the to-be-backed-up data corresponding to the target order and the storage time of the to-be-backed-up data from the target business system;

[0070] When it is detected that the target order has completed the target node, a target node completion message for the target order can be generated based on this and sent to the platform.

[0071] When the platform receives the target node completion message, it can indicate that the target order has completed the target node; at this time, the business system that provides the business corresponding to the target node can be determined first and used as the target business system.

[0072] Then, the data to be backed up corresponding to the target order can be obtained from the target business system. In addition, the data to be backed up may have been stored previously. If the data to be backed up has not been backed up for a long time, there is a greater risk of complete loss of the data to be backed up. Therefore, the storage time of the data to be backed up can be obtained from the business system.

[0073] Step 202: When the storage time is less than a preset time threshold, determine a target data identifier corresponding to the data type and / or data source of the data to be backed up;

[0074] After obtaining the storage time, it is possible to first determine whether the data to be backed up has been stored for a long time and has not been backed up based on the storage time. Specifically, a preset time threshold can be set in advance, and the preset time threshold can be set according to actual conditions; thus, when determining whether the data to be backed up has been stored for a long time and has not been backed up, the storage time can be compared with the preset time threshold. If the storage time is less than the preset time threshold, it can be indicated that the data to be backed up has not been stored for a long time.

[0075] In this case, in order to perform different backups for different data, thereby avoiding the situation where important data is not backed up as quickly as possible or unimportant data is frequently backed up, the data type of the data to be backed up can be determined first; of course, the data source of the data to be backed up can also be determined. The data type and data source can be determined simultaneously or alternatively, and this is not limited in this embodiment of the present invention.

[0076] After determining the data type and / or data source, a data identifier corresponding to the data type and / or data source of the data to be backed up can be determined from the data identifiers pre-set for the data type and data source, and used as the target data identifier.

[0077] In one embodiment of the present invention, the target data identifier may be determined through any one or more of the following sub-steps.

[0078] Sub-step 11: Obtain the data update frequency of the target business system; determine the target data identifier based on the data update frequency;

[0079] Different business systems may have different data update frequencies, and different data update frequencies may require different backup strategies. For example, data in a business system with a high data update frequency requires frequent backups, while data in a business system with a slow data update frequency may not require as frequent backups. Therefore, you can pre-set different data identifiers for different data update frequencies and associate the data update frequency with the backup strategy.

[0080] As an example, different data identifiers can be set for data update frequencies in different intervals, so that after obtaining the data update frequency from the target business system, the data update frequency can be matched with the pre-set interval, and the target data identifier corresponding to the data update frequency of the target business system can be determined based on the matching result.

[0081] Sub-step 12: determining the target system identifier of the target business system; determining the target data identifier corresponding to the target system identifier;

[0082] As an example, system identifiers for distinguishing business systems can be set in advance for multiple business systems connected to the platform, and the system identifiers can be associated with data identifiers so that when it is necessary to determine the data identifier corresponding to the data source of the data to be backed up, it can be determined directly based on the system identifier.

[0083] Specifically, the target system identifier set for the target business system may be determined first; and then, based on the association relationship between the system identifier and the data identifier, the target data identifier corresponding to the target system identifier may be determined.

[0084] Sub-step 13: determining the target service corresponding to the data to be backed up; determining the target service level of the target service, and determining the target data identifier corresponding to the target service level.

[0085] As an example, a business system may provide at least one e-commerce business. Different businesses have different levels of importance. For example, data related to finance-related businesses is more important, while data related to computing-related businesses is less important. Therefore, service levels can be pre-set based on the importance of the business, and a relationship between service levels and data identifiers can be established to quickly determine the target data identifier for the service level corresponding to the data type to be backed up.

[0086] Specifically, the target service corresponding to the data to be backed up may be determined first, and then a target service level pre-set for the target service may be obtained; and then based on the relationship between the service level and the data identifier, a target data identifier corresponding to the target service level may be determined.

[0087] Step 203: Determine a target backup policy that matches the target data identifier; the target backup policy includes a system change backup policy;

[0088] As an example, the target backup policy may include a system change backup policy. The system change backup policy may refer to a backup method in which a backup is performed only when a system change occurs.

[0089] In order to facilitate the determination of the backup strategy for the data to be backed up, the correspondence between the data identifier and the backup strategy can be preset; then, when the backup strategy needs to be determined, the target backup strategy corresponding to the target data identifier can be determined from the preset correspondence.

[0090] Step 204: Determine the initiation time of the target order and determine the target time interval based on the initiation time and the time when the target node completion message is received;

[0091] When the target backup strategy is determined to be a system change backup strategy, you can first determine whether the target business system has changed within a certain period of time. Specifically, you can first determine the initiation time of the target order, for example, the time when the target order was generated.

[0092] Then, the time when the target node completion message is received can be determined, and a target time interval can be determined in combination with the initiation time of the target order.

[0093] Step 205: Determine whether the target business system has changed within the target time interval;

[0094] After determining the target time interval, it is possible to determine whether the target business system has undergone any system changes within the target event interval.

[0095] In one embodiment of the present invention, step 205 may include the following sub-steps:

[0096] Determine whether a system software package of a target business system has changed within a target time interval; if so, determine that the target business system has changed; and / or determine whether a system configuration of the target business system has changed within a target time interval; if so, determine that the target business system has changed.

[0097] As an example, the update status of the system software package of the target business system can be determined first, and it can be judged whether the system software package of the target business system has been updated within the target time interval; if a change has occurred within the target time interval, it can be indicated that the target business system has been changed within the target time interval.

[0098] As another example, you can first determine the update status of the system configuration of the target business system, and judge whether the system configuration of the target business system has changed within the target time interval; if it has changed within the target time interval, it can be said that the target business system has changed within the target time interval.

[0099] Step 206: When it is determined that a change occurs, the data to be backed up is backed up.

[0100] After determining that the target business system has changed within the target time interval, it can be indicated that the data to be backed up needs to meet the requirements of the system change backup policy. At this time, the data to be backed up can be backed up.

[0101] In an embodiment of the present invention, when a target node completion message for a target order is received, the data to be backed up corresponding to the target order and the storage time of the data to be backed up are obtained from the target business system; when the storage time is less than a preset time threshold, a target data identifier corresponding to the data type and / or data source of the data to be backed up is determined; a target backup strategy that matches the target data identifier is determined; the target backup strategy includes a system change backup strategy; the initiation time of the target order is determined, and a target time interval is determined based on the initiation time and the time when the target node completion message is received; it is determined whether the target business system has changed within the target time interval; when it is determined that a change has occurred, the data to be backed up is backed up. Through the embodiment of the present invention, targeted data backup is achieved, so that only data that needs to be backed up when a system change occurs can be backed up according to the corresponding system change backup strategy, avoiding waste of resources during the backup process.

[0102] Reference Figure 3 , shows a flowchart of another data backup method according to an embodiment of the present invention, including the following steps:

[0103] Step 301: When the platform receives a target node completion message for a target order, it obtains the to-be-backed-up data corresponding to the target order and the storage time of the to-be-backed-up data from the target business system;

[0104] When it is detected that the target order has completed the target node, a target node completion message for the target order can be generated based on this and sent to the platform.

[0105] When the platform receives the target node completion message, it can indicate that the target order has completed the target node; at this time, the business system that provides the business corresponding to the target node can be determined first and used as the target business system.

[0106] Then, the data to be backed up corresponding to the target order can be obtained from the target business system. In addition, the data to be backed up may have been stored previously. If the data to be backed up has not been backed up for a long time, there is a greater risk of complete loss of the data to be backed up. Therefore, the storage time of the data to be backed up can be obtained from the business system.

[0107] Step 302: When the storage time is less than a preset time threshold, determine a target data identifier corresponding to the data type and / or data source of the data to be backed up;

[0108] After obtaining the storage time, it is possible to first determine whether the data to be backed up has been stored for a long time and has not been backed up based on the storage time. Specifically, a preset time threshold can be set in advance, and the preset time threshold can be set according to actual conditions; thus, when determining whether the data to be backed up has been stored for a long time and has not been backed up, the storage time can be compared with the preset time threshold. If the storage time is less than the preset time threshold, it can be indicated that the data to be backed up has not been stored for a long time.

[0109] In this case, in order to perform different backups for different data, thereby avoiding the situation where important data is not backed up as quickly as possible or unimportant data is frequently backed up, the data type of the data to be backed up can be determined first; of course, the data source of the data to be backed up can also be determined. The data type and data source can be determined simultaneously or alternatively, and this is not limited in this embodiment of the present invention.

[0110] After determining the data type and / or data source, a data identifier corresponding to the data type and / or data source of the data to be backed up can be determined from the data identifiers pre-set for the data type and data source, and used as the target data identifier.

[0111] Step 303: Determine a target backup strategy that matches the target data identifier; the target backup strategy includes an incremental backup strategy;

[0112] As an example, the target backup policy may include an incremental backup policy, which may refer to a backup method of backing up only increased or decreased data.

[0113] Step 304: Determine the newly added data in the data to be backed up that has changed compared to the last time the target business system backed up data.

[0114] Since the incremental backup strategy only backs up added or reduced data, the data to be backed up can be compared with the data of the last backup of the target business system, and the new data that has changed compared to the last backup data can be determined; the new data can include both added data and reduced data.

[0115] Step 305: Back up the newly added data.

[0116] After the newly added data is determined, the backup can be performed according to the newly added data. For example, the added data can be added to the backup database, and the reduced data can be deleted from the backup database.

[0117] In an embodiment of the present invention, when a target node completion message for a target order is received, the data to be backed up corresponding to the target order and the storage time of the data to be backed up are obtained from the target business system; when the storage time is less than a preset time threshold, the target data identifier corresponding to the data type and / or data source of the data to be backed up is determined; a target backup strategy that matches the target data identifier is determined; the target backup strategy includes an incremental backup strategy; new data in the data to be backed up that has changed compared to the last time the target business system backed up data is determined; and the new data is backed up. Through the embodiment of the present invention, targeted data backup is achieved, so that data that only needs to be backed up when data increases or decreases can be backed up according to the corresponding incremental backup strategy, avoiding waste of resources during the backup process and ensuring that important data can be backed up in a timely manner.

[0118] Reference Figure 4 , shows a flowchart of another data backup method according to an embodiment of the present invention, including the following steps:

[0119] Step 401: When the platform receives a target node completion message for a target order, it obtains the to-be-backed-up data corresponding to the target order and the storage time of the to-be-backed-up data from the target business system;

[0120] When it is detected that the target order has completed the target node, a target node completion message for the target order can be generated based on this and sent to the platform.

[0121] When the platform receives the target node completion message, it can indicate that the target order has completed the target node; at this time, the business system that provides the business corresponding to the target node can be determined first and used as the target business system.

[0122] Then, the data to be backed up corresponding to the target order can be obtained from the target business system. In addition, the data to be backed up may have been stored previously. If the data to be backed up has not been backed up for a long time, there is a greater risk of complete loss of the data to be backed up. Therefore, the storage time of the data to be backed up can be obtained from the business system.

[0123] Step 402: When the storage time is less than a preset time threshold, determine a target data identifier corresponding to the data type and / or data source of the data to be backed up;

[0124] After obtaining the storage time, it is possible to first determine whether the data to be backed up has been stored for a long time and has not been backed up based on the storage time. Specifically, a preset time threshold can be set in advance, and the preset time threshold can be set according to actual conditions; thus, when determining whether the data to be backed up has been stored for a long time and has not been backed up, the storage time can be compared with the preset time threshold. If the storage time is less than the preset time threshold, it can be indicated that the data to be backed up has not been stored for a long time.

[0125] In this case, in order to perform different backups for different data, thereby avoiding the situation where important data is not backed up as quickly as possible or unimportant data is frequently backed up, the data type of the data to be backed up can be determined first; of course, the data source of the data to be backed up can also be determined. The data type and data source can be determined simultaneously or alternatively, and this is not limited in this embodiment of the present invention.

[0126] After determining the data type and / or data source, a data identifier corresponding to the data type and / or data source of the data to be backed up can be determined from the data identifiers pre-set for the data type and data source, and used as the target data identifier.

[0127] Step 403: Determine a target backup strategy that matches the target data identifier; the target backup strategy includes a time-sharing backup strategy;

[0128] As an example, the target backup strategy may include a time-sharing backup strategy, which may refer to performing incremental backup according to a first time interval and performing full backup according to a second time interval; wherein the first time interval and the second time interval can be set according to actual conditions, and the first time interval is smaller than the second time interval.

[0129] Step 404: perform incremental backup of the data to be backed up according to a first time interval, and perform full backup of the data to be backed up according to a second time interval; wherein the first time interval is smaller than the second time interval.

[0130] When it is determined that the target backup strategy is a time-sharing backup strategy, incremental backup of the data to be backed up can be performed according to a pre-set first time interval. Specifically, the data to be backed up can be compared with the data of the last backup of the target business system, and the new data that has changed in the data to be backed up compared with the last backup data can be determined; then the new data can be backed up, for example: the added data can be filled in the backup database, and the reduced data can be deleted from the backup database.

[0131] In addition, all the data to be backed up may be backed up according to a preset second time interval. For example, all the data to be backed up may be backed up.

[0132] In an embodiment of the present invention, when the platform receives a target node completion message for a target order, it obtains the data to be backed up corresponding to the target order and the storage time of the data to be backed up from the target business system; when the storage time is less than a preset time threshold, it determines the target data identifier corresponding to the data type and / or data source of the data to be backed up; determines the target backup strategy that matches the target data identifier; the target backup strategy includes a time-sharing backup strategy; incremental backup of the data to be backed up is performed at a first time interval, and full backup of the data to be backed up is performed at a second time interval; wherein the first time interval is less than the second time interval. Through the embodiment of the present invention, targeted data backup is achieved, and different backups are performed at different time intervals, which ensures that the data that needs to be backed up in time is backed up in time, and that other data can be backed up within a certain period of time, and that the resources used in the backup process are reasonably allocated.

[0133] It should be noted that for the sake of simplicity, the method embodiments are described as a series of actions. However, those skilled in the art should be aware that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0134] Reference Figure 5 , shows a schematic structural diagram of a data backup device according to an embodiment of the present invention, which may specifically include the following modules:

[0135] The storage time acquisition module 501 is used to acquire the to-be-backed-up data and the storage time of the to-be-backed-up data corresponding to the target order from the target business system when the platform receives the target node completion message for the target order;

[0136] An identifier determination module 502 is configured to determine a target data identifier corresponding to a data type and / or data source of the data to be backed up when the storage time is less than a preset time threshold;

[0137] A backup strategy determination module 503 is configured to determine a target backup strategy that matches the target data identifier;

[0138] The backup module 504 is configured to back up the data to be backed up according to the target backup strategy.

[0139] In one embodiment of the present invention, the identification determination module 502 includes:

[0140] The frequency determination identification submodule is used to obtain the data update frequency of the target business system; and determine the target data identification according to the data update frequency;

[0141] The system identification submodule is used to determine the target system identification of the target business system; determine the target data identification corresponding to the target system identification;

[0142] The service level identification submodule is used to determine the target service corresponding to the data to be backed up; determine the target service level of the target service, and determine the target data identification corresponding to the target service level.

[0143] In one embodiment of the present invention, the target backup strategy includes a system change backup strategy, and the backup module 504 includes:

[0144] The first backup submodule is used to determine the initiation time of the target order and determine the target time interval based on the initiation time and the time when the target node completion message is received; judge whether the target business system has changed within the target time interval; when it is determined that a change has occurred, back up the backup data.

[0145] In one embodiment of the present invention, the first backup submodule is used to determine whether the system software package of the target business system has changed within a target time interval; when a change has occurred, determine that the target business system has changed; and / or, determine whether the system configuration of the target business system has changed within the target time interval; when a change has occurred, determine that the target business system has changed.

[0146] In one embodiment of the present invention, the target backup strategy includes an incremental backup strategy, and the backup module 504 includes:

[0147] The second backup submodule is used to determine the newly added data in the data to be backed up that has changed compared to the last time the target business system backed up data; and back up the newly added data.

[0148] In one embodiment of the present invention, the target backup strategy includes a time-sharing backup strategy, and the backup module 504 includes:

[0149] A third backup submodule is configured to perform incremental backup of the backup data according to the first time interval and perform full backup of the backup data according to the second time interval;

[0150] The first time interval is smaller than the second time interval.

[0151] In one embodiment of the present invention, the backup module 504 includes:

[0152] The fourth backup submodule is used to determine the amount of data to be backed up;

[0153] Adjust the backup time included in the target backup strategy based on the amount of data;

[0154] Back up the data to be backed up according to the adjusted backup time.

[0155] In an embodiment of the present invention, when the platform receives a target node completion message for a target order, it obtains the to-be-backed-up data corresponding to the target order and the storage time of the to-be-backed-up data from the target business system; when the storage time is less than a preset time threshold, it determines a target data identifier corresponding to the data type and / or data source of the to-be-backed-up data; determines a target backup strategy that matches the target data identifier; and backs up the to-be-backed-up data according to the target backup strategy. Through the embodiment of the present invention, targeted data backup is achieved, resource waste in the data backup process is reduced, and important data is ensured to be backed up in a timely manner.

[0156] An embodiment of the present invention further provides a server, comprising a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the above data backup method when executed by the processor.

[0157] An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the above data backup method is implemented.

[0158] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0159] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0160] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, apparatus, or computer program products. Thus, embodiments of the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0161] The embodiments of the present invention are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the process in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0162] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0163] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0164] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they become aware of the basic creative concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0165] Finally, it should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or terminal device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or terminal device that includes the element.

[0166] The above is a detailed introduction to the data backup method and device provided. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core ideas. At the same time, for those skilled in the art, according to the ideas of the present invention, there may be changes in the specific implementation methods and application scopes. In summary, the contents of this specification should not be understood as limiting the present invention.

Claims

1. A data backup method, characterized in that: The method comprises: When the platform receives a target node completion message for a target order, it obtains the to-be-backed-up data corresponding to the target order and the storage time of the to-be-backed-up data from the target business system; When the storage time is less than a preset time threshold, determining a target data identifier corresponding to the data type and / or data source of the data to be backed up; Determining a target backup strategy that matches the target data identifier; Backing up the data to be backed up according to the target backup strategy; The target backup strategy includes a system change backup strategy, and backing up the data to be backed up according to the target backup strategy includes: Determine the initiation time of the target order, and determine the target time interval based on the initiation time and the time when the completion message of the target node is received; Determining whether the target business system has changed within the target time interval; wherein the target business system having changed within the target time interval includes: a system software package of the target business system having changed within the target time interval, and / or a system configuration of the target business system having changed within the target time interval; When it is determined that a change occurs, the data to be backed up is backed up.

2. The method according to claim 1, characterized in that The determining of the target data identifier corresponding to the data type and / or data source of the data to be backed up includes: Obtaining the data update frequency of the target business system; determining the target data identifier based on the data update frequency; and / or, determining a target system identifier of the target business system; determining a target data identifier corresponding to the target system identifier; And / or, determining a target service corresponding to the data to be backed up; determining a target service level of the target service, and determining a target data identifier corresponding to the target service level.

3. The method according to claim 1, characterized in that The target backup strategy includes an incremental backup strategy, and backing up the data to be backed up according to the target backup strategy includes: Determining new data in the data to be backed up that has changed compared to the last time the target business system backed up data; Back up the newly added data.

4. The method according to claim 1, wherein The target backup strategy includes a time-sharing backup strategy, and backing up the data to be backed up according to the target backup strategy includes: Performing incremental backup of the data to be backed up at a first time interval, and performing full backup of the data to be backed up at a second time interval; The first time interval is smaller than the second time interval.

5. The method according to claim 1, wherein Backing up the data to be backed up according to the target backup strategy includes: Determine the amount of data to be backed up; Adjusting the backup time included in the target backup strategy according to the amount of data; Back up the data to be backed up according to the adjusted backup time.

6. A data backup device, characterized in that: The device comprises: A storage time acquisition module is used to acquire the to-be-backed-up data corresponding to the target order and the storage time of the to-be-backed-up data from the target business system when the platform receives a target node completion message for the target order; an identification determination module, configured to determine a target data identification corresponding to a data type and / or a data source of the data to be backed up when the storage time is less than a preset time threshold; A backup strategy determination module, configured to determine a target backup strategy that matches the target data identifier; A backup module, configured to back up the data to be backed up according to the target backup strategy; The target backup strategy includes a system change backup strategy, and the backup module includes: The first backup submodule is used to determine the initiation time of the target order and determine the target time interval based on the initiation time and the time when the completion message of the target node is received; judge whether the target business system has changed within the target time interval; when it is determined that a change has occurred, back up the data to be backed up; wherein, the target business system has changed within the target time interval, including: the system software package of the target business system has changed within the target time interval, and / or the system configuration of the target business system has changed within the target time interval.

7. A server, characterized in that: The method comprises a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein the computer program implements the data backup method according to any one of claims 1 to 5 when executed by the processor.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the data backup method according to any one of claims 1 to 5 is implemented.

Images