Backup data processing method and apparatus, computer device, and readable storage medium

Abstract

The application relates to a backup data processing method and device, computer equipment and a readable storage medium, and relates to the technical field of backup. The method comprises the following steps: determining a first reference information list based on reference information of each backup data in an active storage area; determining reference reference information of each backup data in the active storage area based on multiple historical backup records, and then determining a second reference information list; each historical backup record is used for recording backup data referenced by a terminal in one backup; comparing the first reference information list and the second reference information list to determine difference backup data with differences between the reference information and the reference reference information; and correcting the reference information of the difference backup data based on the reference reference information of the difference backup data. The method can avoid the misdeletion of backup data caused by the damage of the reference relationship of the backup data.

Description

Technical Field

[0001] This application relates to the field of backup technology, and in particular to a backup data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0002] In related technologies, in private cloud architectures, the reference relationships of backup data are typically recorded based on reference information, and then the lifecycle of backup data is managed based on the reference information. For example, backup data is deleted when the reference count is zero.

[0003] However, the reference relationships of backup data may be corrupted due to server abnormalities, concurrent update conflicts, or network interruptions, such as the reference count being abnormally cleared to zero, which may lead to the accidental deletion of backup data that is still being referenced. Summary of the Invention

[0004] Therefore, it is necessary to provide a backup data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product to address the technical problem of accidental deletion of backup data due to the damage of the reference relationship of backup data in the above-mentioned private cloud architecture.

[0005] Firstly, this application provides a method for processing backup data, including:

[0006] In the event of a self-healing event for reference information, a first list of reference information is determined based on the reference information of each backup data in the active storage area; the reference information of each backup data includes at least a reference count and a list of referencing terminals for the backup data, wherein the reference count is used to record the number of files that reference the backup data, and the list of referencing terminals is used to record the terminal identifiers of the terminals that reference the backup data;

[0007] Based on multiple historical backup records, reference information for each backup data in the active storage area is determined, and a second reference information list is determined based on the reference information for each backup data in the active storage area; each historical backup record is used to record the backup data referenced by a terminal in a backup; the reference information for each backup data includes at least the reference count of the backup data and a list of reference terminals;

[0008] By comparing the first reference information list and the second reference information list, among the backup data in the active storage area, the differential backup data whose reference information differs from the reference reference information is determined;

[0009] Based on the reference information of the differential backup data, the reference information of the differential backup data is corrected.

[0010] In one embodiment, the method further includes:

[0011] Receive the target file uploaded by the target terminal;

[0012] If target backup data corresponding to the target file already exists in the active storage area, update the reference information of the target backup data;

[0013] If the target backup data does not exist in the active storage area, the target backup data is created and stored in the active storage area based on the target file, and the reference information of the target backup data is determined.

[0014] The method further includes:

[0015] Upon detecting a local deletion event of the target file by the target terminal, the reference information of the target backup data is updated; the local deletion event of the target file by the target terminal is an event that deletes the target file stored locally on the target terminal.

[0016] In one embodiment, the method further includes:

[0017] Upon detecting a first deletion event for backup data in the active storage area, the backup data is moved from the active storage area to the recycle bin storage area;

[0018] The time when the backup data is moved to the recycle bin storage area is recorded to obtain the initial deletion time of the backup data. Based on the data type of the backup data, the retention period of the backup data is determined; different data types correspond to different retention periods.

[0019] If a data recovery event is detected for the backup data, the backup data is moved from the recycle bin storage area to the active storage area;

[0020] Upon detecting a second deletion event for backup data in the recycle bin storage area, the backup data is deleted from the recycle bin storage area; the second deletion event for the backup data is triggered when the target deletion time of the backup data is reached, the target deletion time of the backup data being determined based on the initial deletion time and retention period of the backup data.

[0021] In one embodiment, the method further includes:

[0022] For any backup data in the active storage area, if the reference count of the backup data is less than or equal to a first preset value, a first deletion event for the backup data is determined to have been detected.

[0023] In one embodiment, the step of detecting a data recovery event for the backup data further includes:

[0024] For any backup data in the recycle bin storage area, if a data recovery event for the backup data is detected, the reference count of the backup data is configured to a second preset value.

[0025] In one embodiment, determining the retention period of the backup data based on the data type of the backup data includes:

[0026] Determine the data format and / or data importance labels of the backup data;

[0027] Based on the data format and / or data importance tags of the backup data, the data type of the backup data is determined from multiple candidate data types; each candidate data type has a corresponding preset retention period;

[0028] The retention period of the backup data is determined based on the preset retention period corresponding to the data type of the backup data.

[0029] In one embodiment, the method further includes:

[0030] Upon detecting a recycle bin cleanup event, iterate through each backup data in the recycle bin storage area;

[0031] For the current backup data that has been traversed, the target deletion time of the current backup data is determined based on the initial deletion time and retention period of the current backup data;

[0032] If the current time of the current backup data is later than or equal to the target deletion time of the current backup data, it is determined that a second deletion event for the current backup data has been detected.

[0033] Secondly, this application also provides a backup data processing apparatus, comprising:

[0034] The first reference information determination module is used to determine a first reference information list based on the reference information of each backup data in the active storage area when a reference information self-healing event is detected; the reference information of each backup data includes at least the reference count of the backup data and the reference terminal list, wherein the reference count is used to record the number of files that reference the backup data, and the reference terminal list is used to record the terminal identifier of the terminal that references the backup data;

[0035] The second reference information determination module is used to determine the reference information of each backup data in the active storage area based on multiple historical backup records, and to determine a second reference information list based on the reference information of each backup data in the active storage area; each historical backup record is used to record the backup data referenced by a terminal in a backup; the reference information of each backup data includes at least the reference count of the backup data and the list of reference terminals;

[0036] The differential backup data determination module is used to compare the first reference information list and the second reference information list, and determine the differential backup data in the active storage area where the reference information differs from the reference reference information.

[0037] The automatic reference information correction module is used to correct the reference information of the differential backup data based on the reference information of the differential backup data.

[0038] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0039] In the event of a self-healing event for reference information, a first list of reference information is determined based on the reference information of each backup data in the active storage area; the reference information of each backup data includes at least a reference count and a list of referencing terminals for the backup data, wherein the reference count is used to record the number of files that reference the backup data, and the list of referencing terminals is used to record the terminal identifiers of the terminals that reference the backup data;

[0040] Based on multiple historical backup records, reference information for each backup data in the active storage area is determined, and a second reference information list is determined based on the reference information for each backup data in the active storage area; each historical backup record is used to record the backup data referenced by a terminal in a backup; the reference information for each backup data includes at least the reference count of the backup data and a list of reference terminals;

[0041] By comparing the first reference information list and the second reference information list, among the backup data in the active storage area, the differential backup data whose reference information differs from the reference reference information is determined;

[0042] Based on the reference information of the differential backup data, the reference information of the differential backup data is corrected.

[0043] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0044] In the event of a self-healing event for reference information, a first list of reference information is determined based on the reference information of each backup data in the active storage area; the reference information of each backup data includes at least a reference count and a list of referencing terminals for the backup data, wherein the reference count is used to record the number of files that reference the backup data, and the list of referencing terminals is used to record the terminal identifiers of the terminals that reference the backup data;

[0045] Based on multiple historical backup records, reference information for each backup data in the active storage area is determined, and a second reference information list is determined based on the reference information for each backup data in the active storage area; each historical backup record is used to record the backup data referenced by a terminal in a backup; the reference information for each backup data includes at least the reference count of the backup data and a list of reference terminals;

[0046] By comparing the first reference information list and the second reference information list, among the backup data in the active storage area, the differential backup data whose reference information differs from the reference reference information is determined;

[0047] Based on the reference information of the differential backup data, the reference information of the differential backup data is corrected.

[0048] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0049] In the event of a self-healing event for reference information, a first list of reference information is determined based on the reference information of each backup data in the active storage area; the reference information of each backup data includes at least a reference count and a list of referencing terminals for the backup data, wherein the reference count is used to record the number of files that reference the backup data, and the list of referencing terminals is used to record the terminal identifiers of the terminals that reference the backup data;

[0050] Based on multiple historical backup records, reference information for each backup data in the active storage area is determined, and a second reference information list is determined based on the reference information for each backup data in the active storage area; each historical backup record is used to record the backup data referenced by a terminal in a backup; the reference information for each backup data includes at least the reference count of the backup data and a list of reference terminals;

[0051] By comparing the first reference information list and the second reference information list, among the backup data in the active storage area, the differential backup data whose reference information differs from the reference reference information is determined;

[0052] Based on the reference information of the differential backup data, the reference information of the differential backup data is corrected.

[0053] The aforementioned backup data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product firstly, upon detecting a self-healing event of reference information, determine a first reference information list based on the reference information of each backup data in the active storage area; the reference information of each backup data includes at least a reference count of the backup data and a list of referencing terminals, the reference count being used to record the number of files referencing the backup data, and the list of referencing terminals being used to record the terminal identifiers of the terminals referencing the backup data; then, based on multiple historical backup records, determine reference reference information for each backup data in the active storage area, and determine a second reference information list based on the reference reference information of each backup data in the active storage area; each historical backup record is used to record the backup data referenced by a terminal in a backup; the reference reference information of each backup data includes at least a reference reference count of the backup data and a list of referencing terminals; next, by comparing the first reference information list and the second reference information list, identify the differential backup data in the active storage area whose reference information differs from the reference reference information; then, based on the reference reference information of the differential backup data, correct the reference information of the differential backup data. In this way, upon detecting a self-healing event for reference information, for each backup data in the active storage area, a first reference information list is determined based on the reference information of each backup data, and a second reference information list is determined based on the reference information of each backup data based on historical backup records. This allows us to obtain the reference information currently recorded for each backup data (the first reference information list) and the actual reference information that should have been recorded (the second reference information list). By comparing the first and second reference information lists, we can identify the backup data with discrepancies between the reference information and the reference reference information, i.e., the backup data with corrupted reference information. Based on the reference reference information of the discrepancy backup data, i.e., the actual reference information that should have been recorded for the discrepancy backup data, we can correct the reference information of the discrepancy backup data. This enables self-healing of the corrupted reference information of the discrepancy backup data, thereby ensuring the correctness of the reference information recorded by the discrepancy backup data and avoiding accidental deletion of backup data due to corrupted reference information. Attached Figure Description

[0054] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only one embodiment of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0055] Figure 1 This is an application environment diagram of a backup data processing method in one embodiment;

[0056] Figure 2 This is a flowchart illustrating a backup data processing method in one embodiment;

[0057] Figure 3 This is a schematic diagram of the soft deletion process for backup data in one embodiment;

[0058] Figure 4 This is a schematic diagram of an object storage-based soft deletion and data self-healing system for a home private cloud in one embodiment;

[0059] Figure 5 This is a schematic diagram of a hierarchical soft deletion mechanism in one embodiment;

[0060] Figure 6 This is a schematic diagram illustrating a self-healing mechanism in one embodiment;

[0061] Figure 7 This is a schematic diagram illustrating accidental deletion recovery in a home setting, as shown in one embodiment.

[0062] Figure 8 This is a schematic diagram of a cascading deletion protection mechanism in one embodiment;

[0063] Figure 9 This is a structural block diagram of a backup data processing device in one embodiment;

[0064] Figure 10 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0065] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit the scope of this application.

[0066] It is understood that terms such as "first" and "second" in this application are used only to distinguish similar objects and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. The term "connection" in the embodiments of this application refers to various connection methods, such as direct or indirect connections, to achieve communication between devices; this application does not impose any limitations on this.

[0067] It is understandable that "at least one" refers to one or more, while "multiple" refers to two or more.

[0068] When used herein, the singular forms of “a,” “an,” and “the” may also include the plural forms unless the context clearly indicates otherwise. It should also be understood that the terms “comprising / including” or “having,” etc., specify the presence of the stated features, wholes, steps, operations, components, parts, or combinations thereof, but do not preclude the possibility of the presence or addition of one or more other features, wholes, steps, operations, components, parts, or combinations thereof. Meanwhile, the term “and / or” as used in this specification includes any and all combinations of the associated listed items.

[0069] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0070] The backup method provided in this application embodiment can be applied to, for example, Figure 1 The application environment shown is a private cloud application environment, including server 102 and at least one terminal 104. Server 102 communicates with terminal 104 via a network. Server 102 is a server providing a private cloud storage system; it can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a NAS (Network Attached Storage) server. Terminal 104 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, drones, low-altitude aircraft, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, projection devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc. Head-mounted devices can be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. In practical applications, the server is the storage server for the private cloud application; the terminal is the device running the private cloud application, such as the personal device of a user of the private cloud application. Furthermore, the server 102 and the terminal 104 can be connected directly or indirectly via wired or wireless communication, and this application does not impose any restrictions on this.

[0071] For example, firstly, upon detecting a self-healing event for reference information, server 102 determines a first list of reference information based on the reference information of each backup data in the active storage area. The reference information for each backup data includes at least a reference count and a list of referencing terminals. The reference count records the number of files referencing the backup data, and the list of referencing terminals records the terminal identifiers of the terminals referencing the backup data. Then, server 102 determines reference information for each backup data in the active storage area based on multiple historical backup records, and determines a second list of reference information based on the reference information of each backup data in the active storage area. Each historical backup record records the backup data referenced by a terminal in a backup. The reference information for each backup data includes at least a reference reference count and a list of referencing terminals. Next, server 102 compares the first list of reference information and the second list of reference information to identify the differential backup data in the active storage area whose reference information differs from the reference information. Then, server 102 corrects the reference information of the differential backup data based on the reference information of the differential backup data.

[0072] In one embodiment, such as Figure 2 As shown, a backup data processing method is provided, which can be applied to... Figure 1 Taking the server in the example, the method includes the following steps:

[0073] Step S202: In the event of a self-healing event for reference information detected, a first list of reference information is determined based on the reference information of each backup data in the active storage area.

[0074] The server is used to receive files uploaded by terminals that communicate with the server and to store the files in order to back them up. For example, data storage and management are implemented through the S3 (Simple Storage Service) object storage protocol. Furthermore, backup data corresponding to files uploaded by different terminals is managed through an S3 object storage pool. The S3 object storage pool includes file buckets and a content addressing pool. File buckets store file metadata, and the content addressing pool stores backup data corresponding to the files. Further, the content addressing pool stores backup data in the form of data blocks. Moreover, the content addressing pool is divided into an active storage area and a recycle bin storage area. There is a reference relationship between file metadata and backup data. The file metadata of each file includes at least the file's hash value, which is calculated based on the file's content. For example, the server uses S3 object Metadata to store file metadata. Each backup data is stored using the hash value of the file referencing it as a data identifier. Each backup data has corresponding reference information, which includes at least a reference count and a list of referencing terminals. The reference count records the number of files referencing the backup data, and the list of referencing terminals records the terminal identifiers of the terminals referencing the backup data. For example, the server uses S3 object TagSet to store the reference information of the backup data.

[0075] The reference information self-healing event can be either a user-instructed self-healing of the reference information of each backup data in the active storage area, or the time interval between the current moment and the historical self-healing moment reaching a second time interval. The historical self-healing moment refers to the moment when the reference information of each backup data in the active storage area was last self-healed. The second time interval can be set by the user or by the private cloud application.

[0076] The first reference information list is used to record reference information for each backup data in the active storage area; for example, the first reference information list includes reference information for each backup data in the active storage area.

[0077] In this step, when the server detects a self-healing event for reference information, it traverses each backup data in the active storage area and obtains a first list of reference information based on the reference information of each backup data.

[0078] For example, in the first list of reference information, each backup data is indexed by its data identifier (i.e., the hash value of its corresponding file).

[0079] Step S204: Based on multiple historical backup records, determine the reference information of each backup data in the active storage area, and based on the reference information of each backup data in the active storage area, determine the second reference information list.

[0080] Each historical backup record is used to record the backup data referenced by a terminal in a backup.

[0081] The reference information for each backup data set includes at least the reference count and the list of reference terminals.

[0082] The second reference information list is used to record reference information for each backup data in the active storage area; for example, the second reference information list includes reference information for each backup data in the active storage area.

[0083] In this step, the server obtains multiple historical backup records. Then, the server iterates through each historical backup record, and during the iteration, it counts the reference information of each backup data in the active storage area. For example, for each backup data, each time the backup data appears during the iteration, the reference count of the backup data is incremented by 1, and the terminal identifier of the terminal to which the currently iterated historical backup record belongs is added to the reference terminal list of the backup data. After the iteration is completed, the server obtains a second reference information list based on the reference information of each backup data.

[0084] For example, in the historical backup record and the second reference information list, each backup data is indexed by its data identifier (i.e., the hash value of its corresponding file).

[0085] Step S206: Compare the first reference information list and the second reference information list, and identify the differential backup data in the active storage area where the reference information differs from the referenced reference information.

[0086] In this step, the server compares the first reference information list and the second reference information list. Through this comparison, it identifies the backup data in the active storage area whose reference information differs from the corresponding reference information. For example, if the reference information of the backup data differs from the reference information, it indicates that the reference information of the backup data has been abnormally corrupted.

[0087] Step S208: Based on the reference information of the differential backup data, correct the reference information of the differential backup data.

[0088] In this step, for each differential backup data, the server corrects the reference information of the differential backup data based on the reference information of the differential backup data. For example, the reference information of the differential backup data is replaced with the reference information of the differential backup data, thereby obtaining the corrected reference information of the differential backup data.

[0089] Furthermore, if the reference count in the reference information of the differential backup data, after correction, is less than or equal to a first preset value, the server determines that it has detected a first deletion event for the differential backup data, moves the differential backup data to the recycle bin storage area, and records an audit log. The first preset value can be set by the user or by the private cloud application. In practice, the private cloud application sets the first preset value to 0.

[0090] For example, when the server traverses each backup data in the active storage area, it can first determine whether the reference information of each backup data is abnormal. If there is backup data with abnormal reference information, it can then obtain multiple historical backup records to perform reference information self-healing.

[0091] In the above backup data processing method, firstly, upon detecting a self-healing event of reference information, the server determines a first reference information list based on the reference information of each backup data in the active storage area. The reference information of each backup data includes at least a reference count and a list of referencing terminals. The reference count records the number of files referencing the backup data, and the list of referencing terminals records the terminal identifiers of the terminals referencing the backup data. Then, based on multiple historical backup records, the server determines reference information for each backup data in the active storage area, and determines a second reference information list based on the reference information of each backup data in the active storage area. Each historical backup record records the backup data referenced by a terminal in a backup. The reference information of each backup data includes at least a reference reference count and a list of referencing terminals. Next, the server compares the first reference information list and the second reference information list, and identifies the differential backup data in the active storage area whose reference information differs from the reference information. Then, based on the reference information of the differential backup data, the server corrects the reference information of the differential backup data. In this way, upon detecting a self-healing event for reference information, for each backup data in the active storage area, a first reference information list is determined based on the reference information of each backup data, and a second reference information list is determined based on the reference information of each backup data based on historical backup records. This allows us to obtain the reference information currently recorded for each backup data (the first reference information list) and the actual reference information that should have been recorded (the second reference information list). By comparing the first and second reference information lists, we can identify the backup data with discrepancies between the reference information and the reference reference information, i.e., the backup data with corrupted reference information. Based on the reference reference information of the discrepancy backup data, i.e., the actual reference information that should have been recorded for the discrepancy backup data, we can correct the reference information of the discrepancy backup data. This enables self-healing of the corrupted reference information of the discrepancy backup data, thereby ensuring the correctness of the reference information recorded by the discrepancy backup data and avoiding accidental deletion of backup data due to corrupted reference information.

[0092] In one embodiment, the backup data processing method provided by this application further includes the following steps for backing up files uploaded by a terminal: receiving a target file uploaded by a target terminal; updating the reference information of the target backup data if target backup data corresponding to the target file already exists in the active storage area; and creating and storing target backup data in the active storage area based on the target file, and determining the reference information of the target backup data if target backup data does not exist in the active storage area.

[0093] The target terminal is any one of the terminals that communicates with the server; the terminal that communicates with the server runs a private cloud application.

[0094] In this embodiment, the server receives a target file uploaded by the target terminal. First, the server calculates the hash value of the target file based on its content, and determines the file metadata of the target file based on the hash value. The file metadata includes the hash value of the target file. Then, the server stores the file metadata of the target file in a file storage bucket. Next, based on the hash value of the target file, the server searches for target backup data identified by the hash value of the target file in the backup data of the active storage area. If the target backup data is found, it means that the target file is already stored in the active storage area. Therefore, the server updates the reference to the target backup data. For example, the server increments the reference count of the target backup data, for instance, by incrementing the reference count by 1, and adds the terminal identifier of the terminal that uploaded the target file to the reference terminal list of the target backup data. If the target backup data is not found, it means that the target file is not stored in the active storage area. Therefore, the server creates target backup data in the active storage area to store the file content of the target file, using the hash value of the target file as the data identifier, initializes the reference count of the target backup data to a third preset value, and adds the terminal identifier of the target terminal that uploaded the target file to the reference terminal list of the target backup data.

[0095] The third preset value can be set by the user or by the private cloud application. In practice, the private cloud application sets the third preset value to 1.

[0096] In this embodiment, the server stores the target file using hash addressing, which enables duplicate file storage at minimal cost and reduces the memory occupied by backups.

[0097] In one embodiment, the backup data processing method provided in this application further includes the following steps for cascading protection among multiple terminals: when a local deletion event of a target file by a target terminal is detected, the reference information of the target backup data is updated; the local deletion event of the target file by the target terminal is an event that deletes the target file stored locally on the target terminal.

[0098] In this embodiment, if the server detects that a target file stored locally on the target terminal has been deleted, it determines that a local deletion event for the target file has been detected by the target terminal, and then updates the reference information of the target backup data. For example, the server reduces the reference count of the target backup data corresponding to the target file, for example, by decrementing the reference count of the target backup data by 1. Also, the server deletes the terminal identifier of the target terminal from the reference terminal list of the target backup data corresponding to the target file. If the reference terminal list of the target backup data records multiple terminal identifiers of the target terminal, only one of them is deleted.

[0099] In this embodiment, the server updates the reference information of the target backup data corresponding to the target file when it detects a local deletion event of the target file by the target terminal, instead of directly deleting the target backup data corresponding to the target file. This avoids the impact of a local deletion by one terminal on other terminals and the private cloud, thereby achieving cascading protection among multiple terminals.

[0100] In the practical application of private clouds, accidental deletion of backup data by users is a frequent occurrence. For example, in a home private cloud scenario, users may accidentally delete important photos or documents. In related technologies, private cloud architectures typically use the S3 object storage protocol for data storage and management. However, the delete operation corresponding to the DeleteObject interface in the S3 object storage protocol is permanent. After accidental deletion by a user, the S3 storage architecture in related technologies cannot recover the deleted backup data, directly resulting in the permanent loss of the backup data. In one embodiment, such as... Figure 3 As shown, the backup data processing method provided in this application further includes the following steps to perform soft deletion of backup data in order to recover backup data accidentally deleted by the user:

[0101] In step S302, if a first deletion event is detected for backup data in the active storage area, the backup data is moved from the active storage area to the recycle bin storage area.

[0102] Specifically, the first deletion event for backup data refers to a scenario where the reference count of the backup data is less than or equal to a first preset value. This first preset value can be set by the user or by the private cloud application. In practice, the private cloud application sets the first preset value to 0.

[0103] In this step, for each backup data in the active storage area, if the server detects that the reference count of the backup data is less than or equal to a first preset value, it determines that a first deletion event has been detected for the backup data. The server then moves the backup data from the active storage area to the recycle bin storage area to achieve soft deletion of the backup data.

[0104] Step S304: Record the moment when the backup data is moved to the recycle bin storage area to obtain the initial deletion moment of the backup data. Based on the data type of the backup data, determine the retention period of the backup data.

[0105] The data type of the backup data can be any one of multiple candidate data types. Each candidate data type has a corresponding preset retention period. The retention period of the backup data is determined based on the preset retention period corresponding to its data type. For example, the server determines the preset retention period corresponding to the data type of the backup data as the retention period of the backup data.

[0106] The candidate data types include at least image and video data, document data, cached and temporary data, and backup data marked as important by the user. The preset retention period for each candidate data type can be set by the user or by the private cloud application. In practice, the private cloud application sets the preset retention period for image and video data to 90 days, for document data to 30 days, for cached and temporary data to 3-7 days, and for backup data marked as important by the user to 180 days.

[0107] The data type of the backup data is determined based on the data format and / or data importance label of the backup data; the data format of the backup data is used to characterize whether the backup data is image and video data, document data, cache and temporary data, and the data importance label of the backup data is used to characterize whether the backup data has been marked as important data by the user.

[0108] In this step, for any backup data in the active storage area, the server will record the moment when the backup data is moved to the recycle bin storage area as the initial deletion moment of the backup data, and determine the data type to which the backup data belongs from multiple candidate data types based on the data format and / or data importance label of the backup data, and then determine the preset retention period corresponding to the data type to which the backup data belongs as the retention period of the backup data.

[0109] In practical applications, the server uses the S3 object TagSet to record the data importance tag, data format, initial deletion time, and retention period of the backup data. Furthermore, the server can also use the S3 object TagSet to record the original storage path of the backup data and the reason for its deletion.

[0110] Step S306: If a data recovery event for backup data is detected, move the backup data from the recycle bin storage area to the active storage area.

[0111] Among them, the data recovery event for backup data refers to the backup data being selected by the user for recovery in the recycle bin interface; for example, the private cloud application supports users to select backup data in the recycle bin storage area for recovery in the recycle bin interface. When the user selects the backup data to be recovered in the recycle bin interface, the server determines that a data recovery event for the selected backup data has been detected.

[0112] In this step, for any backup data in the recycle bin storage area, if the server detects a data recovery event for the backup data when the backup data is selected by the user for recovery in the recycle bin interface, the server moves the backup data from the recycle bin storage area to the active storage area to realize the recovery of the backup data.

[0113] In practical applications, the server moves the backup data from the recycle bin storage area to the active storage area through the original storage path recorded in the S3 object TagSet, and records the recovery time of the backup data from the recycle bin storage area to the active storage area through the S3 object TagSet.

[0114] Step S308: If a second deletion event for backup data is detected, delete the backup data in the recycle bin storage area; the second deletion event for backup data is triggered when the target deletion time of the backup data is reached, and the target deletion time of the backup data is determined based on the initial deletion time and retention period of the backup data.

[0115] The second deletion event for backup data refers to the time when the backup data is deleted. The target deletion time is determined based on the initial deletion time and the retention period of the backup data. For example, the target deletion time is obtained by adding the retention period to the initial deletion time.

[0116] The time interval between the target deletion time and the initial deletion time is the retention period.

[0117] In this step, for any backup data in the recycle bin storage area, when the target deletion time of the backup data arrives, the server determines that a second deletion event for the backup data has been detected, and deletes the backup data in the recycle bin storage area to achieve the true deletion of the backup data.

[0118] In this embodiment, firstly, upon detecting a first deletion event for backup data in the active storage area, the server moves the backup data from the active storage area to the recycle bin storage area. Then, the server records the time the backup data is moved to the recycle bin storage area to obtain the initial deletion time of the backup data. Based on the data type of the backup data, the retention period of the backup data is determined; different data types correspond to different retention periods. Next, upon detecting a data recovery event for the backup data, the server moves the backup data from the recycle bin storage area to the active storage area. Then, upon detecting a second deletion event for the backup data, the server deletes the backup data in the recycle bin storage area. The second deletion event for the backup data is triggered when the target deletion time of the backup data is reached; the target deletion time of the backup data is determined based on the initial deletion time and the retention period of the backup data. In this way, by moving the backup data from the active storage area to the recycle bin instead of deleting it directly when a first deletion event targeting the backup data is detected, and deleting the backup data in the recycle bin when a second deletion event is detected that triggers a target deletion event based on the initial deletion time and retention period of the backup data, the backup data that is instructed to be deleted can be retained for a period of time before being actually deleted, thus achieving soft deletion of the backup data. By moving the backup data from the recycle bin to the active storage area when a data recovery event targeting the backup data is detected, the backup data can be recovered. Based on the above process, the backup data processing method can recover accidentally deleted backup data through the soft deletion mechanism and recovery mechanism.

[0119] In one embodiment, the backup data processing method provided by this application further includes the following steps for sensing the triggering of a first deletion event: for any backup data in the active storage area, if the reference count of the backup data is detected to be less than or equal to a first preset value, a first deletion event for the backup data is determined to be detected.

[0120] The first preset value can be set by the user or by the private cloud application. In practice, the private cloud application sets the first preset value to 0.

[0121] In this embodiment, for any backup data in the active storage area, if the server detects that the reference count of the backup data is less than or equal to a first preset value, for example, if the reference count of the backup data is less than or equal to 0, the server determines that a first deletion event has been detected for the backup data.

[0122] In this embodiment, the server can perform soft deletion of the backup data by determining that a first deletion event for the backup data has been detected when the reference count of the backup data is low.

[0123] In one embodiment, step S306 above, when a data recovery event for backup data is detected, further includes the following step: for any backup data in the recycle bin storage area, when a data recovery event for backup data is detected, the reference count of the backup data is configured to a second preset value.

[0124] The second preset value can be set by the user or by the private cloud application; for example, the second preset value must be set to a value greater than the first preset value. In practical applications, the private cloud application sets the second preset value to 1.

[0125] In this embodiment, for any backup data in the recycle bin storage area, when the server detects a data recovery event for the backup data, it configures the reference count of the backup data to a second preset value, such as 1, and then moves the backup data from the recycle bin storage area to the active storage area to realize the recovery of the backup data.

[0126] In this embodiment, the server can restore the backup data by configuring the reference count of the backup data to a second preset value and moving the backup data from the recycle bin storage area to the active storage area when a data recovery event for the backup data is detected.

[0127] In one embodiment, step S304 above, which determines the retention period of the backup data based on the data type of the backup data, includes the following steps: determining the data format and / or data importance label of the backup data; determining the data type of the backup data from multiple candidate data types based on the data format and / or data importance label of the backup data; and determining the retention period of the backup data based on the preset retention period corresponding to the data type of the backup data.

[0128] The data type of the backup data can be any one of multiple candidate data types. Each candidate data type has a corresponding preset retention period. The retention period of the backup data is determined based on the preset retention period corresponding to its data type. For example, the server determines the preset retention period corresponding to the data type of the backup data as the retention period of the backup data.

[0129] The candidate data types include at least image and video data, document data, cached and temporary data, and backup data marked as important by the user. The preset retention period for each candidate data type can be set by the user or by the private cloud application. In practice, the private cloud application sets the preset retention period for image and video data to 90 days, for document data to 30 days, for cached and temporary data to 3-7 days, and for backup data marked as important by the user to 180 days.

[0130] In this embodiment, the server determines the data type of the backup data from multiple candidate data types based on the data format and / or data importance label of the backup data, and then determines the preset retention period corresponding to the data type of the backup data as the retention period of the backup data.

[0131] For example, backup data marked as important by the user is greater than other candidate data types. The server first determines whether the data importance label of the backup data is the target value. If it is the target value, it means that the backup data is marked as important by the user, and the server determines that the data type of the backup data is the backup data marked as important by the user. If the data importance label of the backup data is not the target value, the server determines the data type of the backup data according to the data format of the backup data. For example, if the suffix of the backup data is .image or .video, the data type of the backup data is determined to be image and video data; if the suffix of the backup data is .application or .text, the data type of the backup data is determined to be document data; if the suffix of the backup data is .tmp or .cache, the data type of the backup data is determined to be cache and temporary data.

[0132] In this embodiment, the server can adopt differentiated retention strategies for different types of backup data, thereby enabling fine-grained differentiated management of different types of backup data.

[0133] In one embodiment, the backup data processing method provided by this application further includes the following steps for sensing the triggering of a second deletion event: when a recycle bin cleanup event is detected, traversing each backup data in the recycle bin storage area; for the current backup data that has been traversed, determining the target deletion time of the current backup data based on the initial deletion time and retention period of the current backup data; when the current time of the current backup data that has been traversed is later than or equal to the target deletion time of the current backup data, determining that a second deletion event for the current backup data has been detected.

[0134] The recycle bin cleanup event can be either a user-instructed cleanup of the recycle bin storage area, or the time interval between the current moment and a previous cleanup moment reaching a first time interval. The previous cleanup moment refers to the moment when the recycle bin storage area was last cleaned. The first time interval can be set by the user or by the private cloud application.

[0135] In this embodiment, when the server detects a recycle bin cleanup event, it iterates through each backup data in the recycle bin storage area. For each backup data encountered, the server determines the current backup data and calculates the target deletion time of the current backup data based on the initial deletion time and retention period. For example, the retention period is added to the initial deletion time to obtain the target deletion time. Then, the server determines whether the current time of encountering the current backup data is later than or equal to the target deletion time of the current backup data. If it is later than or equal to the target deletion time, it determines that a second deletion event for the current backup data has been detected.

[0136] In this embodiment, the server can determine that a second deletion event for the backup data has been detected when it iterates through the target deletion time of the backup data, which is later than or equal to the backup time, thereby enabling the actual deletion of the backup data.

[0137] In one specific embodiment, this application also provides a method and system for soft deletion and data self-healing based on object storage for home private clouds. Figure 4 As shown, the system includes a private cloud client running on the user terminal and a private cloud NAS deployed in the user's home LAN. The private cloud client includes at least a self-healing report viewing module, a retention period configuration module, a recycle bin interface, and a backup service. The private cloud NAS includes an active storage area, a recycle bin storage area, a backup record area, a soft delete management module, a self-healing management module, a tiered cleanup module, and a recovery management module.

[0138] like Figure 5 The diagram illustrates a tiered soft deletion mechanism: When the private cloud NAS detects that the reference count of backup data in the active storage area has reached zero, it determines the retention period based on the data type and moves the backup data to the recycle bin storage area. Users can restore the backup data through the recycle bin interface on the private cloud client. If the user chooses to restore, the private cloud NAS moves the backup data back to the active storage area and resets its reference count to 1. If the retention period expires, the private cloud NAS permanently deletes the backup data.

[0139] like Figure 6The self-healing mechanism is shown below: Scan all backup data in the active area to determine the first reference information list; traverse all backup records to determine the second reference information list; compare the first reference information list and the second reference information list to reconstruct the reference information of backup data where the comparison results differ.

[0140] like Figure 7 The diagram shows the timing of accidental deletion recovery in a home scenario. When a user accidentally deletes a photo, causing the photo's reference count to become 0, the private cloud client will request the private cloud NAS to delete it. The private cloud NAS will then place the photo in the recycle bin storage area. If the user discovers that the photo has been accidentally deleted 3 days later, they can query it through the recycle bin interface of the private cloud client, and the private cloud NAS will return the recycle bin list.

[0141] like Figure 8 The diagram illustrates the cascading deletion protection mechanism: Assuming devices A, B, and C have all uploaded photo D to the private cloud, then each device holds a reference to photo D, sharing the corresponding data block of photo D in the active storage area. The reference count for this data block is 3, and the list of referencing devices is [Device A, Device B, Device C]. If a user deletes photo D locally on device A, then after deletion, the data block of photo D remains in the active storage area, the reference count for the data block of photo D becomes 2, and the list of referencing devices becomes [Device B, Device C]. Access to photo D by devices B and C is unaffected.

[0142] In this embodiment, firstly, accidental deletion is recoverable: Home users can recover accidentally deleted data with one click within the retention period, significantly reducing the risk of permanent data loss and solving the problem of unrecoverable accidental deletion in existing solutions. Secondly, reference relationships are self-healing: When reference information is damaged, it is automatically reconstructed from backup records without manual intervention, suitable for non-professional users, solving the problem of existing solutions' inability to self-heal after reference information is damaged. Thirdly, differentiated retention: Different retention periods are set for different data types, balancing storage space and data security, avoiding a "one-size-fits-all" approach, and solving the problem of traditional solutions' inability to finely configure according to content type. Fourthly, cascading protection: In multi-device scenarios, deletion on a single device only reduces the reference count; if the reference count remains greater than 0 after the reduction, other devices are completely unaffected, avoiding synchronous accidental deletion and solving the risk of cascading deletion in existing multi-device sharing scenarios. Fifthly, zero additional cost: It does not rely on paid features such as S3 version control, and is entirely based on the standard S3 interface, solving the problems of high cost and complex configuration in enterprise-level solutions. Sixthly, complete metadata inheritance: Metadata is fully retained during recovery, or it can be optionally not retained, solving the problem of metadata loss after recovery.

[0143] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0144] Based on the same inventive concept, this application also provides a backup data processing apparatus for implementing the backup data processing method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more backup data processing apparatus embodiments provided below can be found in the limitations of the backup data processing method described above, and will not be repeated here.

[0145] In one embodiment, such as Figure 9 As shown, a backup data processing device is provided, including: a first reference information determination module 902, a second reference information determination module 904, a differential backup data determination module 906, and a reference information automatic correction module 908, wherein:

[0146] The first reference information determination module 902 is used to determine a first reference information list based on the reference information of each backup data in the active storage area when a reference information self-healing event is detected. The reference information of each backup data includes at least a reference count and a list of referencing terminals. The reference count is used to record the number of files that reference the backup data, and the list of referencing terminals is used to record the terminal identifiers of the terminals that reference the backup data.

[0147] The second reference information determination module 904 is used to determine the reference information of each backup data in the active storage area based on multiple historical backup records, and to determine the second reference information list based on the reference information of each backup data in the active storage area; each historical backup record is used to record the backup data referenced by a terminal in a backup; the reference information of each backup data includes at least the reference count of the backup data and the list of reference terminals.

[0148] The differential backup data determination module 906 is used to compare the first reference information list and the second reference information list to determine the differential backup data in the active storage area where the reference information differs from the referenced reference information.

[0149] The automatic reference information correction module 908 is used to correct the reference information of the differential backup data based on the reference information of the differential backup data.

[0150] In one embodiment, the backup data processing device further includes a file backup processing module, which is used to receive a target file uploaded by a target terminal; if target backup data corresponding to the target file already exists in the active storage area, update the reference information of the target backup data; if target backup data does not exist in the active storage area, create and store the target backup data in the active storage area based on the target file, and determine the reference information of the target backup data.

[0151] In one embodiment, the backup data processing apparatus further includes a reference count update module, used to update the reference information of the target backup data when a local deletion event of the target terminal for the target file is detected; the local deletion event of the target terminal for the target file is an event that deletes the target file stored locally on the target terminal.

[0152] In one embodiment, the backup data processing apparatus further includes a backup data deletion module, configured to: move backup data from the active storage area to the recycle bin storage area upon detecting a first deletion event for backup data in the active storage area; record the time when the backup data is moved to the recycle bin storage area to obtain the initial deletion time of the backup data; determine the retention period of the backup data based on the data type of the backup data; different data types correspond to different retention periods; move backup data from the recycle bin storage area to the active storage area upon detecting a data recovery event for the backup data; delete the backup data in the recycle bin storage area upon detecting a second deletion event for the backup data; and trigger the second deletion event for the backup data upon reaching the target deletion time of the backup data, the target deletion time of the backup data being determined based on the initial deletion time and the retention period of the backup data.

[0153] In one embodiment, the backup data deletion module is further configured to determine, for any backup data in the active storage area, that a first deletion event for the backup data has been detected if the reference count of the backup data is less than or equal to a first preset value.

[0154] In one embodiment, the backup data deletion module is further configured to, for any backup data in the recycle bin storage area, configure the reference count of the backup data to a second preset value when a data recovery event for the backup data is detected.

[0155] In one embodiment, the backup data deletion module is further configured to determine the data format and / or data importance label of the backup data; based on the data format and / or data importance label of the backup data, determine the data type of the backup data from multiple candidate data types; each candidate data type has a corresponding preset retention period; and determine the retention period of the backup data based on the preset retention period corresponding to the data type of the backup data.

[0156] In one embodiment, the backup data deletion module is further configured to, upon detecting a recycle bin cleanup event, traverse each backup data in the recycle bin storage area; for the current backup data being traversed, determine the target deletion time of the current backup data based on the initial deletion time and retention period of the current backup data; and if the current time of the current backup data being traversed is later than or equal to the target deletion time of the current backup data, determine that a second deletion event for the current backup data has been detected.

[0157] Each module in the aforementioned backup data processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0158] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows. Figure 10 As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and databases. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media to run. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a backup data processing method.

[0159] Those skilled in the art will understand that Figure 10 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0160] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0161] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above-described method embodiments.

[0162] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0163] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0164] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0165] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for processing backup data, characterized in that, The method includes: In the event of a self-healing event for reference information, a first list of reference information is determined based on the reference information of each backup data in the active storage area; the reference information of each backup data includes at least a reference count and a list of referencing terminals for the backup data, wherein the reference count is used to record the number of files that reference the backup data, and the list of referencing terminals is used to record the terminal identifiers of the terminals that reference the backup data; Based on multiple historical backup records, reference information for each backup data in the active storage area is determined, and a second reference information list is determined based on the reference information for each backup data in the active storage area; each historical backup record is used to record the backup data referenced by a terminal in a backup; the reference information for each backup data includes at least the reference count of the backup data and a list of reference terminals; By comparing the first reference information list and the second reference information list, among the backup data in the active storage area, the differential backup data whose reference information differs from the reference reference information is determined; Based on the reference information of the differential backup data, the reference information of the differential backup data is corrected.

2. The method according to claim 1, characterized in that, The method further includes: Receive the target file uploaded by the target terminal; If target backup data corresponding to the target file already exists in the active storage area, update the reference information of the target backup data; If the target backup data does not exist in the active storage area, the target backup data is created and stored in the active storage area based on the target file, and the reference information of the target backup data is determined. The method further includes: Upon detecting a local deletion event of the target file by the target terminal, the reference information of the target backup data is updated; the local deletion event of the target file by the target terminal is an event that deletes the target file stored locally on the target terminal.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Upon detecting a first deletion event for backup data in the active storage area, the backup data is moved from the active storage area to the recycle bin storage area; The time when the backup data is moved to the recycle bin storage area is recorded to obtain the initial deletion time of the backup data. Based on the data type of the backup data, the retention period of the backup data is determined; different data types correspond to different retention periods. If a data recovery event is detected for the backup data, the backup data is moved from the recycle bin storage area to the active storage area; Upon detecting a second deletion event for backup data in the recycle bin storage area, the backup data is deleted from the recycle bin storage area; the second deletion event for the backup data is triggered when the target deletion time of the backup data is reached, the target deletion time of the backup data being determined based on the initial deletion time and retention period of the backup data.

4. The method according to claim 3, characterized in that, The method further includes: For any backup data in the active storage area, if the reference count of the backup data is less than or equal to a first preset value, a first deletion event for the backup data is determined to have been detected.

5. The method according to claim 3, characterized in that, The method further includes, upon detecting a data recovery event for the backup data: For any backup data in the recycle bin storage area, if a data recovery event for the backup data is detected, the reference count of the backup data is configured to a second preset value.

6. The method according to claim 3, characterized in that, Determining the retention period of the backup data based on its data type includes: Determine the data format and / or data importance labels of the backup data; Based on the data format and / or data importance tags of the backup data, the data type of the backup data is determined from multiple candidate data types; each candidate data type has a corresponding preset retention period; The retention period of the backup data is determined based on the preset retention period corresponding to the data type of the backup data.

7. The method according to claim 3, characterized in that, The method further includes: Upon detecting a recycle bin cleanup event, iterate through each backup data in the recycle bin storage area; For the current backup data that has been traversed, the target deletion time of the current backup data is determined based on the initial deletion time and retention period of the current backup data; If the current time of the current backup data is later than or equal to the target deletion time of the current backup data, it is determined that a second deletion event for the current backup data has been detected.

8. A backup data processing device, characterized in that, The device includes: The first reference information determination module is used to determine a first reference information list based on the reference information of each backup data in the active storage area when a reference information self-healing event is detected; the reference information of each backup data includes at least the reference count of the backup data and the reference terminal list, wherein the reference count is used to record the number of files that reference the backup data, and the reference terminal list is used to record the terminal identifier of the terminal that references the backup data; The second reference information determination module is used to determine the reference information of each backup data in the active storage area based on multiple historical backup records, and to determine a second reference information list based on the reference information of each backup data in the active storage area; each historical backup record is used to record the backup data referenced by a terminal in a backup; the reference information of each backup data includes at least the reference count of the backup data and the list of reference terminals; The differential backup data determination module is used to compare the first reference information list and the second reference information list, and determine the differential backup data in the active storage area where the reference information differs from the reference reference information. The automatic reference information correction module is used to correct the reference information of the differential backup data based on the reference information of the differential backup data.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

11. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images