A data backup method, device, electronic equipment and storage medium

Abstract

The application discloses a data backup method and device, electronic equipment and storage medium. The method comprises the following steps: obtaining backup account application information for applying for a backup account, and at least one storage platform selected by a user from candidate storage platforms; registering the backup account according to the backup account application information and a super account corresponding to the storage platform, and calling an account management interface of each storage platform respectively; controlling the backup account registered successfully to log in to the target storage platform; storing backup data of the source data in the target storage platform in response to a backup operation of the source data; obtaining monitoring data of the backup data in the target storage platform, and generating a backup monitoring result of the source data in the target storage platform based on the monitoring data. By using the method, the problem that the same source data is difficult to be uniformly managed and monitored when being backed up to multiple different storage platforms is solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer processing, and in particular to a data backup method and device, an electronic device and a storage medium. BACKGROUND

[0002] With the increasing importance of data, data backup is particularly important. In order to prevent data loss caused by system operation errors or system failures, important data may need to be backed up to multiple different storage platforms or storage media, thereby saving multiple backup data. For example, game data of a game server often involves terminal player data or game code data, so multiple backup data is often an important disaster recovery strategy for game data, so as to recover data when the game server fails.

[0003] In the prior art, in the scenario of saving multiple backup data for a source data, an operation and maintenance personnel often applies for a storage account as a backup account for backup data to different public clouds and / or private cloud storage platforms according to backup needs, and then backs up data using the backup account. After backup, a tool is used to record each backup account and the corresponding backup data information. The problem is that there is a lack of unified backup management and monitoring for backing up the same source data to multiple different storage platforms, resulting in the need for the operation and maintenance personnel to learn different storage platforms, which is costly and difficult to monitor the use link and data life cycle of each backup data corresponding to the same source data. The file recording the backup data information also has a risk of loss.

[0004] Therefore, it is very important to provide a reasonable data backup method to solve at least part of the above problems. SUMMARY

[0005] The data backup method provided by the embodiments of the present application solves the problem of the prior art that it is difficult to perform unified backup management and monitoring for backing up the same source data to multiple different storage platforms.

[0006] The data backup method provided by the embodiments of the present application includes: obtaining backup account application information for applying for a backup account, and at least one storage platform selected by a user from candidate storage platforms; calling an account management interface corresponding to each storage platform respectively according to the backup account application information and a super account corresponding to each storage platform, and applying for registration of a backup account to the corresponding storage platform; in response to a login request of a backup account registered successfully logging into a target storage platform, controlling the backup account to log into the target storage platform; in response to a backup operation for a source data, storing backup data of the source data in the target storage platform; obtaining monitoring data for the backup data in the target storage platform, and generating a backup monitoring result of the source data in the target storage platform based on the monitoring data.

[0007] Optionally, the method further comprises: in response to a backup display operation, generating and displaying a backup statistics interface for the backup data.

[0008] Optionally, the method further comprises: in response to a monitoring display operation, generating and displaying a backup monitoring interface for the backup monitoring result.

[0009] Optionally, the method further comprises: in response to a backup account application information and a super account corresponding to each storage platform, respectively calling an account management interface corresponding to each storage platform, and applying for registration of a backup account to the corresponding storage platform, including: using the super account corresponding to each storage platform to send a login request to the storage platform corresponding to the super account; after login, using the backup account application information to call the account management interface corresponding to each storage platform to apply for registration of a backup account; and associating a role with specific data operation permissions set based on the super account in the storage platform corresponding to the super account with the backup account.

[0010] Optionally, the method further comprises: obtaining a first MD5 value generated for the source data; comparing the first MD5 value with a second MD5 value to determine whether they are consistent, and if not, generating a warning information that the backup is incomplete; wherein the second MD5 value is an MD5 value generated for the backup data.

[0011] Optionally, the method further comprises: obtaining monitoring data for the backup data in the target storage platform, and generating a backup monitoring result of the source data in the target storage platform based on the monitoring data, including: obtaining backup parameters corresponding to the backup data stored in the target storage platform, wherein the monitoring data includes the backup parameters; obtaining a backup rule corresponding to the source data; and determining whether the backup parameters of the backup data stored in the target storage platform meet the backup rule to obtain the backup monitoring result.

[0012] Optionally, the method further comprises: if the backup monitoring result is that the backup parameters of the backup data stored in the target storage platform do not meet the backup rule, generating a warning information.

[0013] Optionally, the backup parameters include at least one of the following: backup time, data upload rate, upload data volume, storage duration of the backup data in the target storage platform, data change information of a storage bucket in the target storage platform for storing backup data, and data change frequency of the storage bucket.

[0014] Optionally, the monitoring data includes operation data generated by a user in response to an operation on the backup data.

[0015] Optionally, the source data is at least one of the following data: game log, game database file, game development code.

[0016] Optionally, when the source data is the game log, the monitoring data comprises a data change amount of the game log; and the backup monitoring result of the source data in the target storage platform is generated based on the monitoring data, comprising: determining a game activity level of the corresponding game according to the data change amount; and generating the backup monitoring result according to the game activity level.

[0017] Embodiments of the present application provide a data backup device, comprising: a backup account application unit configured to obtain backup account application information for applying for a backup account, and at least one storage platform selected by a user from candidate storage platforms; a registration unit configured to apply for registration of a backup account to a corresponding storage platform by calling a respective account management interface of each storage platform according to the backup account application information and a super account corresponding to each storage platform; a login unit configured to respond to a login request of a backup account registered successfully to login a target storage platform, and control the backup account to login to the target storage platform; a backup unit configured to store backup data of source data in the target storage platform in response to a backup operation of the source data; and a monitoring unit configured to obtain monitoring data of the backup data in the target storage platform, and generate a backup monitoring result of the source data in the target storage platform based on the monitoring data.

[0018] Embodiments of the present application also provide an electronic device, comprising: a memory and a processor; the memory is configured to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method provided by the embodiments of the present application.

[0019] Embodiments of the present application also provide a computer readable storage medium storing one or more computer instructions, wherein the one or more computer instructions are executed by a processor to implement the method provided by the embodiments of the present application.

[0020] Compared with the prior art, the present application has the following advantages:

[0021] This application provides a data backup method, apparatus, electronic device, and storage medium. The method involves obtaining backup account application information and at least one storage platform selected by the user from candidate storage platforms. Based on the backup account application information and the super account corresponding to each storage platform, the method calls the corresponding account management interface of each storage platform to apply for backup account registration. In response to a login request from a successfully registered backup account to the target storage platform, the method controls the backup account to log in to the target storage platform. In response to a backup operation on the source data, the method stores the backup data of the source data on the target storage platform. The method obtains monitoring data for the backup data on the target storage platform and generates a backup monitoring result of the source data on the target storage platform based on the monitoring data. Since the same backup account can be registered on multiple storage platforms, the maintenance cost of backup accounts can be reduced. Furthermore, using this backup account to back up the same source data on each storage platform ensures the security of data backup. Obtaining monitoring data for the backup data facilitates unified monitoring of multiple backups of the same source data. Furthermore, the entire lifecycle of backup data created by users across various storage platforms is monitored, facilitating the querying of data usage at different times and reducing the risk of unauthorized data use without traceability. Additionally, monitoring backup parameters prevents missed backups. Moreover, statistical analysis of backup data monitoring data helps users uncover the potential value of their data. Attached Figure Description

[0022] Figure 1 This is a schematic diagram of the system environment provided in the embodiments of this application;

[0023] Figure 2 This is a flowchart illustrating the data backup method provided in the first embodiment of this application;

[0024] Figure 3 This is a block diagram of the backup monitoring system provided in the second embodiment of this application;

[0025] Figure 4 This is a schematic diagram of a data backup device provided in the third embodiment of this application;

[0026] Figure 5 This is a schematic diagram of the electronic device provided in this application. Detailed Implementation

[0027] Many specific details are set forth in the following description to provide a full understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of this application; therefore, this application is not limited to the specific embodiments disclosed below.

[0028] Embodiments of the present application provide a data backup method and device, electronic equipment and storage medium. Embodiments of the present application also provide a backup monitoring system. The embodiments are described one by one below.

[0029] For ease of understanding, first, the system environment provided by the embodiments of the present application is given.

[0030] Please refer to Figure 1, the system environment of the method is shown in the figure, including: a data backup platform 101, a backup source end 102, a storage platform 103. Among them, the data backup platform 101 is used for unified management and monitoring of the backup of the same source data to different storage platforms (such as storage platform 1, storage platform 2, …, storage platform N in the figure); the backup source end 102 stores source data that needs to backup at least one backup data; the storage platform 103 can include a plurality of different storage platforms for storing backup data corresponding to the source data, which can be heterogeneous storage platforms, and can include private cloud storage platforms and / or heterogeneous public cloud platforms. The backup source end, the data backup platform and the storage platform form a first link for managing the backup account and monitoring the backup; the backup source end and the data backup platform form a second link for data backup. The data backup platform can be used for, but not limited to: receiving application account information corresponding to the source data, and using the application account information to apply for backup accounts to a plurality of different storage platforms; after the backup account is registered successfully, using the backup account to backup the source data of the backup source end 102 that needs to be backed up to the storage platform selected by the user from the storage platform 103, and performing backup integrity verification on the backup data during backup, such as verifying the consistency of the data file of the source data and the corresponding data file in the backup data based on MD5, so as to ensure the integrity of the backup data; receiving the backup rule set by the user in advance, monitoring the backup state according to the backup rule, which can be the backup frequency corresponding to the source data obtained from the backup rule, for each storage platform, determining whether the backup operation is consistent with the backup frequency according to the difference between the latest backup time of the backup data corresponding to the source data in the storage platform and the current time, if not, the backup state is abnormal, in order to prevent missing backup; obtaining the backup configuration information corresponding to the source data from the backup rule, generating a backup task according to the backup configuration information and the backup frequency, sending the backup task to the backup source end, and the backup source end executing the backup task according to the backup frequency, and backing up the source data to the storage platform specified in the backup configuration information or the storage platform selected by the user; receiving the data life cycle set by the user for the source data, obtaining the operation information and monitoring data of the backup data in each storage platform within the data life cycle, to form monitoring of the use link of the backup data, the operation information can be used to generate operation registration information, and the operation registration information can include but not limited to the visitor corresponding to the operation information, access time, access reason, operation content, purpose of using the backup data, so as to reduce the risk of illegal use of data that cannot be traced. Further, the data backup platform can also alarm for abnormal backup state, abnormal backup integrity verification and other abnormalities in the backup process, and send email or notification message to the user. It can be understood that the above system environment is exemplary and does not limit the method provided by the embodiments of the application.

[0031] The following is combined withFigure 2 The data backup method provided in the first embodiment of this application will be described. Figure 2 The data backup method shown includes steps S201 to S205.

[0032] Step S201: Obtain backup account application information for applying for a backup account, and at least one storage platform selected by the user from the candidate storage platforms.

[0033] Each of the at least one storage platform is a backup destination, used to store backup data generated corresponding to the backup operation performed on the source data that needs to be backed up in the backup source.

[0034] The backup monitoring method provided in this application can be used for unified management and monitoring of data backups from the same source data to different storage platforms. By uniformly managing the backup accounts used to back up the source data to different storage platforms and monitoring the backup data of each storage platform, the cost of backup data maintenance can be reduced.

[0035] In practical applications, the application process for storage accounts on public cloud storage platforms is quite cumbersome, resulting in a high learning curve for operations and maintenance personnel when data needs to be backed up to multiple heterogeneous public cloud storage platforms. Furthermore, the need to back up sensitive data to specific private cloud storage platforms also increases the learning curve. A storage account refers to a backup account used to back up source data. In this embodiment, the account management interfaces and monitoring component open interfaces of each storage platform (public cloud storage platform and private cloud storage platform) are encapsulated into a user interface for easy operation and improved backup maintenance efficiency. Specifically, the backup account application process is encapsulated as a one-click account application function. Users can select one or more storage platforms, such as various public cloud platforms, to apply for an account as needed, and then use that account as the backup account to back up data.

[0036] The step is to obtain backup account application information and a storage platform selected by a user to store backup data, i.e., a backup destination. The backup account application information at least includes an account identifier of the backup account, such as a name of the backup account. There are various implementation manners to obtain the backup account application information. In one implementation manner, the backup account application information for applying for the backup account is obtained, including: detecting that the user triggers a backup monitoring item for creating a backup of the source data, displaying a backup monitoring item editing interface; obtaining item information of the backup monitoring item input by the user, and automatically generating an account identifier of the backup monitoring item backup account according to the item information, the account identifier being the backup account application information. In one implementation manner, the item information of the backup monitoring item input by the user is obtained, and the account identifier of the backup monitoring item backup account is automatically generated according to the item information, and the account identifier is taken as the backup account application information.

[0037] In the embodiment, the candidate storage platforms can be displayed on the backup monitoring item editing interface, and in response to detecting a selection operation of the user on at least one of the storage platforms, the storage platform selected by the user is obtained, and information of the storage platform selected by the user is associated with the backup monitoring item; it is detected that the user confirms to generate the backup monitoring item, and in a subsequent step, an account management interface corresponding to the storage platform selected by the user is called for registration, so as to realize a one-key account application function. Of course, for the same source data, the same backup account application information can be used, and different backup account information can be used to apply for and register backup accounts in multiple storage platforms. If the application information required to register accounts in different storage platforms is different, when the user selects multiple different storage platforms, an interface for inputting backup account application information is displayed for each storage platform, and the interfaces include at least partially different input items. Further, the different backup account information can include the same account identifier. The same account identifier used for the same source data facilitates account management.

[0038] In step S202, according to the backup account application information and the super account corresponding to each storage platform, an account management interface corresponding to each storage platform is respectively called, and a backup account is applied for and registered in the corresponding storage platform.

[0039] The backup account is used to backup the source data to each storage platform, so as to generate backup data corresponding to the source data in each storage platform.

[0040] The step is to register a storage account selected by a user to a storage platform, which is used as a backup account for data backup of the source data. Wherein, according to the backup account application information and the super account corresponding to each storage platform, the account management interface corresponding to each storage platform is respectively called to apply for and register a backup account to the corresponding storage platform, including: sending a login request to the storage platform corresponding to the super account using the super account corresponding to each storage platform; after login, the backup account application information is used to call the account management interface corresponding to each storage platform to apply for and register a backup account; and the role with specific data operation permission set in the corresponding storage platform based on the super account is associated with the backup account. For example: the super account can be used to log in to the corresponding storage platform for authentication, and after authentication, a role with bucket operation permission is set, and a trusted sub-account is created using the account identifier contained in the backup account application information, and the role is assigned to the trusted sub-account, so that the trusted sub-account has the bucket operation permission and can be used to upload and store the backup data to form the backup data. Preferably, after the backup account of each storage platform is successfully registered, the backup account applied for is downloaded from the storage platform, and the backup account is distributed to the actual user who needs to perform backup operation on the source data. Thus, the user can obtain the account content of the backup account of one or more storage platforms through one-time registration, avoiding complex learning cost.

[0041] Step S203, in response to the login request of the backup account registered successfully to the target storage platform, the backup account is controlled to log in to the target storage platform.

[0042] In this step, the backup account is controlled to log in to the target storage platform. When implemented, the interface encapsulating the account management interface of each storage platform (public cloud storage platform and private cloud storage platform) is used to display the information of the candidate storage platform. The target storage platform is selected from the candidate storage platform by the backup account registered successfully, the password information corresponding to the backup account input by the backup account is received, the account management interface of the target storage platform is called according to the backup account and the password information, and the backup account is controlled to log in to the target storage platform. Of course, the backup account registered successfully can be used to log in to the storage platform where the backup account is successfully registered on other devices outside the data backup platform.

[0043] Step S204, in response to the backup operation of the source data, the backup data of the source data is stored in the target storage platform.

[0044] In this embodiment, after the backup account is successfully registered, a storage resource for storing the backup data is created for the user on a target storage platform selected by the user. The storage resource is preferably a storage bucket. The process includes the following steps: obtaining storage bucket configuration information input by the user for the backup project; calling a storage bucket calling interface of the corresponding target storage platform according to the storage bucket configuration information, and sending a storage bucket creation request to the target storage platform; and the target storage platform creates a storage bucket in response to the storage bucket creation request, and the created storage bucket is used to store the backup data. Further, the embodiment also supports deleting, editing and other operations on the storage bucket, for example: detecting a deletion operation of the user on the storage bucket of the target storage platform, calling a storage bucket calling interface of the corresponding target storage platform, and sending a storage bucket deletion request to the target storage platform to make the target storage platform delete the storage bucket.

[0045] This step is a backup operation on the source data. Preferably, the response to the backup operation on the source data stores backup data of the source data on the target storage platform, including: obtaining backup configuration information of the source data from a backup rule, generating a backup task based on the backup configuration information and the backup frequency; after the backup account is successfully registered, sending the backup task to a backup source end that stores the source data, and the backup task is executed to trigger backup of the source data to the target storage platform according to the backup frequency. Of course, the backup configuration information can also include one or more storage platforms as a backup destination, and the backup account is controlled to log in to the one or more storage platforms, and after the backup task is executed by the backup source end, the source data is backed up to the one or more storage platforms according to the backup frequency. The backup task can also be a backup instruction. The backup frequency can also be a backup period. Automatically generating a backup task for different storage platforms can reduce the learning cost of data backup.

[0046] In step S205, monitoring data for the backup data in the target storage platform is obtained, and a backup monitoring result of the source data in the target storage platform is generated based on the monitoring data.

[0047] This step is to monitor the backup data. In actual implementation, the monitoring of the backup data includes but is not limited to backup integrity verification, monitoring whether the backup conforms to the backup rule, and statistics and monitoring of the backup data.

[0048] In the embodiment, the backup data is subjected to backup integrity check, and the integrity check is performed based on MD5 algorithm, specifically including: obtaining a first MD5 value generated for the source data; comparing the first MD5 value with a second MD5 value to determine whether they are consistent, and if not, generating a warning information of incomplete backup; wherein the second MD5 value is an MD5 value generated for the backup data. In actual implementation, the first MD5 value is obtained for at least part of source-end files in the source data; for each storage platform, if the storage platform is a first type of storage platform that can trigger a callback check script for a synchronization command used for backup operation, the callback check script is triggered after the synchronization command is executed, and the second MD5 value is calculated by the callback check script for the destination-end files corresponding to the at least part of source-end files; if the storage platform is a second type of storage platform that is heterogeneous with the first type of storage platform, the second MD5 value is extracted from the object attribute of the destination-end files corresponding to the at least part of source-end files; for each storage platform, it is determined whether the second MD5 value of the destination-end files in the storage platform is consistent with the first MD5 value, and if not, a backup integrity warning is generated for the backup data of the storage platform or information is sent to the user to indicate that the backup integrity check of the backup data fails. Wherein the second MD5 value can be understood as an example of the monitoring data of the backup data, and correspondingly, the check result of the backup integrity check failure or success can be understood as an example of the backup monitoring result. Preferably, the first MD5 value can be stored in a preset path. For example, a private cloud storage platform A using Ceph (a kind of distributed file system) file storage is a first type of storage platform, and the rsync remote synchronization command can be used to synchronize the source data to be backed up to the private cloud storage platform, and the callback script is triggered after the data is synchronized to perform the integrity check of the backup data, and if the value of the second MD5 value is different from the value of the first MD5 value, the backup integrity check fails, a warning information of incomplete backup is generated, and an email is further sent to the user to alarm and prompt.

[0049] In this embodiment, whether the backup meets the backup rule is monitored. The obtaining of the monitoring data of the backup data in the target storage platform, the generating of the backup monitoring result of the source data in the target storage platform based on the monitoring data comprises: obtaining backup parameters corresponding to the backup data stored in the target storage platform, wherein the monitoring data comprises the backup parameters; obtaining a backup rule corresponding to the source data; determining whether the backup parameters of the backup data stored in the target storage platform meet the backup rule to obtain a backup monitoring result. Further, if the backup monitoring result is that the backup parameters of the backup data stored in the target storage platform do not meet the backup rule, an alert information is generated. The backup parameters comprise at least one of the following: backup time, data upload rate, upload data volume, storage duration of the backup data in the target storage platform, data change information of a storage bucket in the target storage platform for storing backup data, and data change frequency of the storage bucket. Taking the backup time as an example, whether the backup time meets the backup rule is monitored, which comprises: obtaining a backup rule corresponding to the source data, obtaining a backup frequency according to the backup rule; for each storage platform, obtaining the latest backup time of the backup data corresponding to the source data in the storage platform according to a preset period, determining the difference between the latest backup time and the current time; if the difference exceeds a backup interval threshold corresponding to the backup frequency, it is determined that the backup operation of the source data to the storage platform is inconsistent with the backup frequency, i.e., it is determined that the backup parameters do not meet the backup rule, and the generated alert information represents a backup exception of not backing up according to the backup plan, and the backup exception is taken as one of the backup monitoring results. The latest backup time is an embodiment of the backup time in the backup parameters, which can represent backup operation information of the backup data. Taking the example of the private cloud storage platform A, before the source data is backed up to A, the user sets the backup frequency to 1 time / day, and then accesses A to detect the backup information of C at a fixed time every day, if the difference between the latest backup time and the current time exceeds 1 day, it is considered that the backup has not been performed for more than 1 day, which is inconsistent with the set backup frequency, and an email alert is sent to the user. Taking the example of the public cloud platform B, a monitoring component of B is regularly called to obtain the latest file backup time of a storage bucket D for storing the backup data corresponding to C, if the difference between the latest file backup time and the current time exceeds 1 day, it is considered that the backup has not been performed for more than 1 day, which is inconsistent with the set backup frequency, and an email alert is sent to the user. Thus, the backup situation of the data backed up regularly can be monitored at all times, the user is reminded to back up the data according to the preset backup rule, and the omission of backup is prevented. During implementation, whether the upload rate, the upload data volume, and the storage duration of the backup data in the target storage platform meet the backup rule can also be monitored, if not, different alert information is generated, so that the user can take appropriate measures.

[0050] In this embodiment, the backup data is counted and monitored by a monitoring component of the target storage platform. The monitoring data of the backup data in the target storage platform is obtained, and the backup monitoring result of the source data in the target storage platform is generated based on the monitoring data. The method comprises the following steps: based on the super account corresponding to the target storage platform accessing the target storage platform, an open interface of the monitoring component of the target storage platform is called, and at least one of the following monitoring data of the backup data corresponding to the source data in the target storage platform is obtained: backup time, data upload rate, upload data volume, data download rate, download data volume, data change information of a storage bucket for storing backup data, and data change frequency of the storage bucket; the monitoring data is counted, and a visual backup monitoring result is formed based on the statistical result. The data upload rate is the upload rate when the source data is uploaded to the target storage platform. The data download rate is the download rate when the backup data is downloaded from the target storage platform. Further, at least one of the following monitoring data can be obtained by calling the open interface of the monitoring component: modification request quantity, access request quantity, request error rate, request response time, etc.

[0051] In this embodiment, in order to visually count and monitor the backup data, a backup statistical interface for the backup data is generated and displayed in response to a backup display operation. For example, the backup statistical interface displays the storage distribution information of the backup project, the statistical information of the backup state health or abnormal project, the information of the storage space occupied by the backup data, etc. The backup monitoring interface for the backup monitoring result is generated and displayed in response to a monitoring display operation. The monitoring data is displayed in the backup monitoring interface, for example, the backup time, data upload rate, upload data volume, data download rate, download data volume, data change frequency, modification request quantity, access request quantity, request error rate, request response time, etc. of the backup project; warning information and / or other backup state abnormal information generated due to the fact that the backup parameters do not meet the backup rules, etc. can also be displayed in the backup monitoring interface.

[0052] In the embodiment, the data lifecycle of the backup data is also set, and the data lifecycle includes the following processing: obtaining the data lifecycle input by the user for the source data; and calling a lifecycle open interface corresponding to the target storage platform based on the data lifecycle to control the storage duration of the backup data in the target storage platform. For example, the monitoring component is an AWS monitoring component, and the lifecycle component is an AWS lifecycle component. Further, the monitoring data includes operation data generated by the user for the backup data operation. The operation data includes at least one of the following data: operation time, user information, operation action information, and operation purpose information. Preferably, the operation information in the data lifecycle of the backup data is recorded, so that the entire lifecycle is monitored, the use of the backup data in each time period is easily queried, the risk of illegal use of the data and failure to trace back is reduced, and the following processing is included: obtaining operation information of the backup data corresponding to the source data in the target storage platform in the data lifecycle; sending an operation registration instruction to a subscription user who subscribes to data operation management information of the backup data according to the operation information; obtaining at least one of the following access information provided by the subscription user for the operation registration instruction: operation time, user information, operation action information, and operation purpose information, wherein the user information is information of an access to the backup data, and the operation purpose information includes a reason for accessing the backup data by the access and a use purpose of the backup data; and generating operation registration information of the backup data according to the operation information and the at least one access information. For example, the reason for accessing the backup data can be to download the backup data or to delete the backup data, and the use purpose of the backup data can be understood as a use of the backup data after the backup data is downloaded. Of course, the corresponding access information input by the user for each piece of operation information can also be received on an interface corresponding to the backup monitoring project, so that the operation registration of the backup data is completed.

[0053] In fact, the data of the game server is a kind of data that needs to be backed up in multiple heterogeneous storage platforms so as to have multiple backup data of the same source data, so as to reduce the risk of data loss. Further, based on the statistics and monitoring information of the backup data of the game data, the potential value of the data can be mined, especially the value data of the backup game log. In the embodiment, the backup source end is a game server, and the source data is at least one of the following data: game log, game database file, and game development code. When the source data is a game log, the monitoring data includes the data change amount of the game log. Correspondingly, the backup monitoring result of the source data in the target storage platform based on the monitoring data includes: determining the game activity degree of the corresponding game according to the data change amount; and generating the backup monitoring result according to the game activity degree. In the implementation, it also includes: counting the data change amount of the game log in the backup data. Further, determining the game activity degree of the corresponding game according to the data change amount; selecting the game log that meets the activity degree threshold, extracting the game service behavior features from the selected game log; and giving game operation disposal suggestions according to the game service behavior features. For example, the size (i.e. data amount) change of the game log in the backup data of a certain game is counted every day, the activity degree of the game can be preliminarily judged, so that the game log with the largest size on a certain day can be selected for targeted data mining.

[0054] It should be noted that the features given in the present embodiment and other embodiments of the present application can be combined with each other without conflict, and steps S201 and S202 or similar terms do not limit the execution of the steps in sequence.

[0055] So far, the method provided by the embodiment is described, the method applies for registering a backup account to each storage platform by using backup account application information and a super account corresponding to each storage platform selected by a user from candidate storage platforms, respectively calls an account management interface corresponding to each storage platform, and realizes registration of the same backup account on multiple storage platforms, thereby reducing the maintenance cost of the backup account. Further, the backup account is controlled to log in to the target storage platform, store backup data of the source data in the target storage platform, obtain monitoring data of the backup data in the target storage platform, generate a backup monitoring result of the source data in the target storage platform based on the monitoring data, and facilitate unified monitoring of multiple backup data of the same source data in different target storage platforms. Further, the entire life cycle of the backup data backed up by the user in each target storage platform is monitored, the use of the data in each time period is facilitated, and the risk of illegal use of the data that cannot be traced is reduced. In addition, the backup parameters are further monitored, which can prevent missing backup. Further, the monitoring data of the backup data is further counted, which is beneficial to the user to mine the potential value of the data.

[0056] Based on the above embodiment, the second embodiment of the present application provides a backup monitoring system, which is described below in combination with Figure 3 the same parts can be referred to the above description of the corresponding embodiment. Figure 3 The backup monitoring system shown in the figure comprises an account application module 301, a backup integrity detection module 302, a backup plan monitoring module 303, and a backup data usage link monitoring module 304.

[0057] The account application module 301 is configured to obtain backup account application information for applying for a backup account, receive selection of at least one storage platform from candidate storage platforms by a user, each storage platform in the at least one storage platform being a backup destination for storing backup data generated by performing a backup operation on source data that needs to be backed up in a backup source, and apply for registration of a backup account with a corresponding storage platform by calling an account management interface of each storage platform respectively according to the backup account application information and a super account corresponding to each storage platform. The system provided in this embodiment can manage and monitor data backups of the same source data to different storage platforms uniformly, and the module manages the backup accounts of the source data to different storage platforms uniformly and monitors the backup data of each storage platform, thereby reducing the maintenance cost of the backup data. In this embodiment, the account management interfaces of each storage platform (public cloud storage platform and private cloud storage platform) and the open interfaces of the monitoring components are encapsulated as an interface for easy operation by the user. In this embodiment, the module encapsulates the application process of the backup account as a one-key account application function, the user selects one or more storage platforms from candidate storage platforms such as various public cloud platforms to apply for an account, and uses the account as a backup account to backup data. Preferably, the backup account application information at least includes an account identifier of the backup account, such as a name of the backup account. In one embodiment, the backup account application information is obtained by detecting that the user triggers creation of a backup monitoring item for the source data, displaying a backup monitoring item editing interface, obtaining a project identifier of the backup monitoring item input by the user, generating an account identifier of the backup account according to the project identifier, and using the account identifier as the backup account application information. In one embodiment, the project information of the backup monitoring item input by the user is obtained, and an account identifier of the backup monitoring item backup account is automatically generated according to the project information, and the account identifier is used as the backup account application information. In this embodiment, the candidate storage platforms can be displayed on the backup monitoring item editing interface for easy selection by the user. When it is detected that the user confirms generation of the backup monitoring item, the account management interface of the storage platform selected by the user is called to register, thereby realizing the one-key account application function. Of course, the same backup account application information or different backup account information can be used to apply for registration of a backup account with multiple storage platforms for the same source data. If the application information required when registering an account with different storage platforms is different, when the user selects multiple different storage platforms, an interface for inputting backup account application information is displayed for each storage platform, and these interfaces include at least some different input items. Further, different backup account information can include the same account identifier.Specifically comprising: sending a login request to the storage platform corresponding to the super account using the super account corresponding to each storage platform respectively; after login success, respectively applying for a backup account by calling the account management interface of each storage platform corresponding to the backup account application information; associating the role with specific data operation permission set based on the super account on the storage platform corresponding to the super account with the backup account. Preferably, after the backup account of each storage platform is successfully registered, the backup account is downloaded from the storage platform, and the backup account is distributed to the actual user who needs to perform backup operation on the source data. Thus, the user can obtain the account content of the backup account of one or more storage platforms through one-time registration, avoiding complex learning cost.

[0058] The backup integrity detection module 302 is configured to obtain a first MD5 value generated by the backup source end for at least part of the source end files in the source data; for each storage platform, if the storage platform is a first type of storage platform that can trigger a callback check script for a synchronization command for backup operation, the callback check script calculates a second MD5 value for the destination file corresponding to the at least part of the source end files; if the storage platform is a second type of storage platform different from the first type of storage platform, the second MD5 value is extracted from the object attribute of the destination file corresponding to the at least part of the source end files; it is judged whether the second MD5 value is consistent with the first MD5 value, if not, a backup exception for indicating that the backup integrity check fails is generated. If the value of the second MD5 value is different from the value of the first MD5 value, the backup integrity check fails, and an email is sent to the user for alarm prompt.

[0059] The backup plan monitoring module 303 is configured to obtain a backup frequency corresponding to the source data; for each storage platform, the latest backup time of the backup data corresponding to the source data in the storage platform is obtained according to a preset period, and the difference between the latest backup time and the current time is determined; if the difference exceeds the backup interval threshold corresponding to the backup frequency, it is determined that the backup operation of the source data to the storage platform is inconsistent with the backup frequency, and a backup exception for indicating that the backup is not according to the backup plan is generated. Further, the backup exception is sent to the user. Wherein, the preset period corresponds to the backup frequency; the backup frequency is extracted from the backup rule corresponding to the source data. Wherein, the latest backup time can represent the backup operation information of the backup data. Thus, for the data to be backed up regularly, the backup situation can be monitored at any time, the user is reminded to backup the data according to the preset backup rule, and the missed backup is prevented.

[0060] The backup data uses the link monitoring module 304 to acquire operation information and monitoring data of the backup data corresponding to the source data in each storage platform within the data life cycle of the backup data. The operation information is used to generate operation registration information. The operation registration information at least includes the following information: visitor, access time, access reason, operation content, and use purpose of the backup data. This module is specifically used for: based on the super account corresponding to each storage platform accessing the storage platform, calling the open interface of the monitoring component of the storage platform, acquiring at least one of the following monitoring data of the backup data corresponding to the source data in the storage platform: backup time, data upload rate, data download rate, uploaded data volume, downloaded data volume, data change information of the storage bucket for storing the backup data, and data change frequency of the storage bucket; statistics are performed on the monitoring data, and a visual backup monitoring result is formed based on the statistical result. Further, it is also used for: acquiring the data life cycle input by the user for the source data; calling the life cycle open interface corresponding to each storage platform based on the data life cycle to control the storage duration of the backup data in the storage platform. For example, the monitoring component is the monitoring component of AWS, and the life cycle component is the life cycle component of AWS. The entire life cycle of the backup data is monitored based on the operation information and the monitoring data, which facilitates the query of the use of the backup data in each time period and reduces the risk that the data is illegally used and cannot be traced.

[0061] Preferably, the backup monitoring system further comprises a warning module. The warning module is used to receive a backup exception sent by at least one of the backup integrity detection module, the backup plan monitoring module, and the backup data use link monitoring module, generate an alarm or send a backup exception notification message to the user according to the backup exception.

[0062] The system provided in this embodiment further comprises a module for providing a configuration management function, such as creating a storage bucket and performing operations such as deleting and modifying the storage bucket. Specifically, as shown in FIG. 1, the system further comprises a configuration management module 306. Figure 3The backup configuration module 305 shown in the figure is configured to create storage resources for storing the backup data on each storage platform selected by the user after the backup account is successfully registered. The storage resources are preferably storage buckets. The backup configuration module is specifically configured to: obtain storage bucket configuration information input by the user for the backup project; call a storage bucket calling interface of a corresponding storage platform according to the storage bucket configuration information, and send a storage bucket creation request to the storage platform; and create a storage bucket on the storage platform, which is used to store the backup data. The backup configuration module is further configured to: detect a deletion operation of the user for the storage bucket, call a storage bucket calling interface of a corresponding storage platform, and send a storage bucket deletion request to the storage platform. Further, the backup configuration module is further configured to configure a backup rule for the source data, the backup rule including backup configuration information and a backup frequency. The backup configuration information includes, for example, file information (i.e., information of the source data) and path information that need to be backed up, path information of the backup data, and the like.

[0063] So far, the system provided by the embodiment has been described. The system can register backup accounts for a plurality of different storage platforms through the account application module; the backup integrity detection module is configured to generate a first MD5 value according to source files of a backup source end and a second MD5 value according to destination files of a backup destination end, and perform backup integrity checking to ensure the integrity of the backup data; the backup plan monitoring module is configured to obtain a backup frequency corresponding to the source data, and determine, for each storage platform, whether the backup operation is consistent with the backup frequency according to a difference between a latest backup time of backup data corresponding to the source data in the storage platform and a current time, to prevent missing backups; and the backup data usage link monitoring module is configured to obtain operation information and monitoring data of the backup data in each storage platform within a data life cycle set by the user, to generate operation registration information, such as recording an access visitor, an access destination, an access time, an access reason, and operation content corresponding to each operation information, thereby reducing the risk of illegal use of data that cannot be traced.

[0064] Corresponding to the first embodiment, the third embodiment of the present application provides a data backup device, which is described below in combination with Figure 4 the same parts can be referred to the above description of the embodiments. Figure 4 The data backup device shown in the figure includes:

[0065] The backup account application unit 401 is configured to obtain backup account application information for applying for a backup account, and at least one storage platform selected by the user from candidate storage platforms;

[0066] The registration unit 402 is configured to, according to the backup account application information and the super account corresponding to each storage platform, respectively call an account management interface corresponding to each storage platform, and apply for registration of a backup account to the corresponding storage platform.

[0067] The login unit 403 is configured to, in response to a login request of a backup account registered successfully, control the backup account to log in to a target storage platform.

[0068] The backup unit 404 is configured to, in response to a backup operation on source data, store backup data of the source data in the target storage platform.

[0069] The monitoring unit 405 is configured to acquire monitoring data of the backup data in the target storage platform, and generate a backup monitoring result of the source data in the target storage platform based on the monitoring data.

[0070] Optionally, the monitoring unit 405 is further configured to, in response to a backup display operation, generate and display a backup statistical interface for the backup data.

[0071] Optionally, the monitoring unit 405 is further configured to, in response to a monitoring display operation, generate and display a backup monitoring interface for the backup monitoring result.

[0072] Optionally, the registration unit 402 is specifically configured to: send a login request to the storage platform corresponding to the super account by using the super account corresponding to each storage platform; after login, call an account management interface corresponding to each storage platform by using the backup account application information to apply for registration of a backup account; and associate a role with specific data operation permissions set in the storage platform corresponding to the super account with the backup account.

[0073] Optionally, the monitoring unit 405 is specifically configured to: acquire a first MD5 value generated for the source data; compare the first MD5 value with a second MD5 value, and if the first MD5 value is inconsistent with the second MD5 value, generate a warning information that the backup is incomplete; wherein the second MD5 value is an MD5 value generated for the backup data.

[0074] Optionally, the monitoring unit 405 is specifically configured to: acquire a backup parameter corresponding to the backup data stored in the target storage platform, wherein the monitoring data comprises the backup parameter; acquire a backup rule corresponding to the source data; and determine whether the backup parameter of the backup data stored in the target storage platform conforms to the backup rule, to obtain a backup monitoring result.

[0075] Optionally, the monitoring unit 405 is specifically configured to: if the backup monitoring result is that the backup parameter of the backup data stored in the target storage platform does not conform to the backup rule, generate a warning message.

[0076] Optionally, the backup parameter comprises at least one of: backup time, data upload rate, upload data volume, storage duration of the backup data in the target storage platform, data change information of a storage bucket in the target storage platform for storing backup data, and data change frequency of the storage bucket.

[0077] Optionally, the monitoring data comprises operation data generated by a user for operations on the backup data.

[0078] Optionally, the source data is at least one of: game logs, game database files, and game development code.

[0079] Optionally, when the source data is game logs, the monitoring data comprises a data change amount of the game logs; and the monitoring unit 405 is specifically configured to: determine a game activity level of a corresponding game according to the data change amount; and generate the backup monitoring result according to the game activity level.

[0080] Based on the above embodiments, a fourth embodiment of the present application provides an electronic device, and related parts can refer to the corresponding description of the above embodiments. Please refer to Figure 5 , the electronic device shown in the figure comprises: a memory 501 and a processor 502; the memory is configured to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method provided by the embodiments of the present application.

[0081] Based on the above embodiments, a fifth embodiment of the present application provides a computer readable storage medium, and related parts can refer to the corresponding description of the above embodiments. The schematic diagram of the computer readable storage medium is similar to Figure 5 . The computer readable storage medium stores one or more computer instructions, and the one or more computer instructions are executed by the processor to implement the method provided by the embodiments of the present application.

[0082] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system or a computer program product. Therefore, the present application can be in the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware aspects. Moreover, the present application can be in the form of a computer program product implemented on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code.

[0083] Although the present application is disclosed with reference to the preferred embodiments above, it is not intended to limit the present application, and any person skilled in the art who learns the present application can make possible changes and modifications without departing from the spirit and scope of the present application, and the protection scope of the present application should be defined by the scope of the claims of the present application.

Claims

1. A method of data backup, characterized by, The method comprises the following steps: obtaining backup account application information for applying for a backup account, and at least one storage platform selected by a user from candidate storage platforms; applying for registration of the backup account on each storage platform according to the backup account application information and a super account corresponding to each storage platform, respectively calling an account management interface corresponding to each storage platform, and applying for registration of the backup account on the corresponding storage platform; after the backup account is successfully registered on each storage platform, downloading the backup account from the storage platform, and distributing the backup account to an actual user who needs to perform a backup operation on source data; in response to a login request of the backup account successfully registered on a target storage platform, controlling the backup account to log in to the target storage platform; in response to a backup operation on the source data, storing backup data of the source data on the target storage platform; obtaining monitoring data of the backup data in the target storage platform, and generating a backup monitoring result of the source data in the target storage platform based on the monitoring data; wherein the backup account application information for applying for a backup account comprises automatically generating an account identifier of a backup account according to a project identifier of a backup monitoring project, and taking the account identifier as the backup account application information; wherein the method further comprises: respectively backing up the same source data on different storage platforms; and obtaining monitoring data of multiple backup data of the same source data to perform unified monitoring.

2. The method of claim 1, wherein, The method further comprises: in response to a backup display operation, generating and displaying a backup statistical interface for the backup data.

3. The method of claim 1, wherein, The method further comprises: in response to a monitoring display operation, generating and displaying a backup monitoring interface for the backup monitoring result.

4. The method of claim 1, wherein, The method further comprises: using the super account corresponding to each storage platform to respectively send a login request to the storage platform corresponding to the super account; after login, using the backup account application information to respectively call an account management interface corresponding to each storage platform to apply for registration of the backup account; associating a role with specific data operation permissions set in the corresponding storage platform based on the super account with the backup account.

5. The method of claim 1, wherein, The method further comprises: obtaining a first MD5 value generated for the source data; comparing whether the first MD5 value and a second MD5 value are consistent, and if not, generating a warning information that the backup is incomplete; wherein the second MD5 value is an MD5 value generated for the backup data.

6. The method of claim 1, wherein, obtaining monitoring data of the backup data in the target storage platform, and generating a backup monitoring result of the source data in the target storage platform based on the monitoring data, comprising: obtaining backup parameters corresponding to the backup data stored in the target storage platform, wherein the monitoring data comprises the backup parameters; obtaining a backup rule corresponding to the source data; judging whether the backup parameters of the backup data stored in the target storage platform meet the backup rule to obtain a backup monitoring result.

7. The method of claim 6, wherein, The method further comprises: If the backup monitoring result is that the backup parameters of the backup data stored in the target storage platform do not comply with the backup rule, a warning information is generated.

8. The method of claim 6, wherein, The backup parameters include at least one of the following: Backup time, data upload rate, upload data volume, backup data storage duration in the target storage platform, data change information of a storage bucket in the target storage platform for storing backup data, and data change frequency of the storage bucket.

9. The method of claim 1, wherein, The monitoring data includes operation data generated by a user for the backup data operation.

10. The method of claim 1, wherein, The source data is at least one of the following data: game log, game database file, and game development code.

11. The method of claim 10, wherein, When the source data is a game log, the monitoring data includes a data change amount of the game log. The backup monitoring result of the source data in the target storage platform is generated based on the monitoring data, including: Determining a game activity level of a corresponding game according to the data change amount; Generating the backup monitoring result according to the game activity level.

12. An apparatus for data backup, characterized by Comprise: A backup account application unit configured to obtain backup account application information for applying for a backup account, and at least one storage platform selected by a user from candidate storage platforms; A registration unit configured to apply for registration of a backup account to a corresponding storage platform by respectively calling an account management interface of each storage platform corresponding to the backup account application information and a super account corresponding to each storage platform; after the backup account of each storage platform is successfully registered, downloading the applied backup account from the storage platform, and distributing the backup account to an actual user who needs to perform a backup operation on source data; A login unit configured to respond to a login request of a backup account registered successfully to a target storage platform, and control the backup account to log in to the target storage platform; A backup unit configured to store backup data of the source data in the target storage platform in response to a backup operation on the source data; A monitoring unit configured to obtain monitoring data for the backup data in the target storage platform, and generate a backup monitoring result of the source data in the target storage platform based on the monitoring data; The backup account application information for applying for a backup account includes: automatically generating an account identifier of a backup account according to a project identifier of a backup monitoring project, and taking the account identifier as the backup account application information. The same source data is respectively backed up in different storage platforms, and monitoring data of multiple backup data of the same source data is obtained to perform unified monitoring.

13. An electronic device, comprising: Comprise a processor and a memory; wherein The memory is configured to store one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement the method of claims 1-11.

14. A computer-readable storage medium having stored thereon one or more computer instructions, wherein, The one or more computer instructions are executed by the processor to implement the method of claims 1-11.

Images