Data management method, apparatus, and device, and storage medium
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-12-31
- Publication Date
- 2026-08-13
Smart Images
Figure CN2025148007_13082026_PF_FP_ABST
Abstract
Description
Data management methods, apparatus, equipment and storage media
[0001] This application claims priority to Chinese Patent Application No. 202510134178.3, filed on February 6, 2025, entitled “Data Management Method, Apparatus, Device and Storage Medium”, the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of computer technology, and more specifically to a data management method, apparatus, device, and storage medium. Background Technology
[0003] Currently, with the rapid development of internet and cloud storage technologies, more and more users are using cloud storage for model training or other business operations. For example, users can utilize distributed caching tools for machine learning training and other data provisioning. However, existing distributed caching tools and other cloud storage tools have drawbacks such as complex usage processes, inability to detect corrupted or corrupted files, and excessive storage space consumption, which can easily lead to data loss or anomalies and fail to meet users' cloud storage needs. Technical solutions
[0004] This application provides a data management method, apparatus, device, and storage medium, aiming to solve the technical problem in the prior art that data loss or anomalies are easily caused when performing business tasks in cloud storage scenarios.
[0005] On the one hand, embodiments of this application provide a data management method, which includes the following steps:
[0006] In response to a data management request for a target cloud storage module, obtain the target data cache volume in the target cloud storage module corresponding to the data management request;
[0007] Anomaly detection is performed on the target data cache volume based on the target detection parameters and the preset detection database to obtain the cache volume detection result;
[0008] Based on the cache volume detection results, data management is performed on the target data cache volume to obtain the data management results.
[0009] In one possible implementation of this application, before obtaining the target data cache volume in the target cloud storage module corresponding to the data management request, the method further includes:
[0010] Obtain the initial data volume to be configured, and the data volume mount parameters of the initial data volume;
[0011] Configure the initial data volume according to the data volume mount parameters and the preset initial configuration file to obtain the mounted data cache volume;
[0012] The step of obtaining the target data cache volume in the target cloud storage module corresponding to the data management request includes:
[0013] The target data cache volume in the mounted data cache volume is read based on the cache volume identifier in the data management request.
[0014] In one possible implementation of this application, before performing data management on the target data cache volume based on the cache volume detection result and obtaining the data management result, the method further includes:
[0015] Obtain the cache volume backup policy corresponding to the target data cache volume;
[0016] The target data cache volume is backed up using the cache volume backup strategy to obtain cache volume backup data;
[0017] The step of performing data management on the target data cache volume based on the cache volume detection result to obtain the data management result includes:
[0018] If the cache volume detection result is determined to be an abnormal cache volume detection result, the target data cache volume is restored using the cache volume backup data to obtain the data management result.
[0019] In one possible implementation of this application, configuring the initial data volume according to the data volume mount parameters and a preset initial configuration file to obtain a mounted data cache volume includes:
[0020] Obtain the data volume mount identifier and data volume mount point from the data volume mount parameters, and generate a data volume mount string based on the data volume mount identifier and data volume mount point;
[0021] The initial data volume variable of the initial configuration file is updated according to the data volume mount string to obtain the target configuration file;
[0022] The initial data volume is mounted according to the target configuration file to obtain the mounted data cache volume.
[0023] In one possible implementation of this application, the step of performing anomaly detection on the target data cache volume based on the target detection parameters of the target data cache volume and a preset detection database to obtain the cache volume detection result includes:
[0024] In response to an anomaly detection request for the target data cache volume, generate anomaly detection parameters corresponding to the anomaly detection request;
[0025] The target detection file in the target data cache volume is determined based on the anomaly detection parameters and the preset detection database;
[0026] Perform a hash operation on the target detection file to obtain the target detection parameters of the target detection file;
[0027] Anomaly detection is performed on the target data cache volume based on the target detection parameters and the anomaly detection parameters to obtain the cache volume detection result.
[0028] In one possible implementation of this application, before determining the target detection file in the target data cache volume based on the anomaly detection parameters and a preset detection database, the method further includes:
[0029] Obtain cached file data from the target data cache volume, perform calculations on the cached file data, and obtain the cached file operation value corresponding to the cached file data;
[0030] The cached file operation value and the cached file data are associated and stored in a preset database to obtain the initial detection database;
[0031] The initial detection database is added to the local cache module according to the data addition instruction in the preset cache version management module, thereby obtaining the detection database corresponding to the target data cache volume.
[0032] In one possible implementation of this application, the step of performing anomaly detection on the target data cache volume based on the target detection parameters and the anomaly detection parameters to obtain a cache volume detection result includes:
[0033] If the target detection parameters and the anomaly detection parameters are the same, then the target detection file is determined to be a normal detection file;
[0034] If the target detection parameters and the anomaly detection parameters are different, then the target detection file is determined to be an anomaly detection file;
[0035] If the anomaly detection file exists in the target data cache volume, then the cache volume detection result of the target data cache volume is determined to be the anomaly cache volume detection result.
[0036] In one possible implementation of this application, the step of performing data management on the target data cache volume based on the cache volume detection result to obtain a data management result includes:
[0037] Read the cache volume detection result and determine that the cache volume detection result is an abnormal cache volume detection result;
[0038] Obtain the cache volume backup data of the target data cache volume, as well as the data upload command from the cache version management module;
[0039] The data upload command is used to write the cache volume backup data to the target data cache volume, thereby obtaining the data management result.
[0040] On the other hand, this application provides a data management device, the data management device comprising:
[0041] The cache volume acquisition module is configured to respond to a data management request for a target cloud storage module and acquire the target data cache volume in the target cloud storage module that corresponds to the data management request.
[0042] The cache volume detection module is configured to perform anomaly detection on the target data cache volume based on the target detection parameters of the target data cache volume and a preset detection database, and obtain the cache volume detection result.
[0043] The data management module is configured to perform data management on the target data cache volume based on the cache volume detection results, and obtain data management results.
[0044] On the other hand, this application also provides a data management device, the data management device comprising:
[0045] One or more processors;
[0046] Memory; and
[0047] One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor to implement the steps of the data management method.
[0048] On the other hand, this application also provides a computer-readable storage medium having a computer program stored thereon, the computer program being loaded by a processor to execute the steps in the data management method described above.
[0049] This application, in response to a data management request for a target cloud storage module, obtains the target data cache volume corresponding to the data management request within the target cloud storage module; performs anomaly detection on the target data cache volume based on target detection parameters and a preset detection database to obtain a cache volume detection result; and performs data management on the target data cache volume based on the cache volume detection result to obtain a data management result. This achieves the following: upon receiving a data management request corresponding to a target data cache volume mounted in a target cloud storage module of distributed storage, it obtains the target detection parameters corresponding to the specified storage file data in the target data cache volume and a preset detection database to perform anomaly detection on the target data cache volume, thereby assessing whether the storage files in the target data cache volume are corrupted or otherwise abnormal, obtaining a cache volume detection result, and performing data management on the target data cache volume based on the cache volume detection result to perform fault recovery operations such as fault recovery on abnormal storage files in the target data cache volume, obtaining a data management result. This aims to improve data security in distributed cloud storage, reduce the probability of cloud storage data volume loss, and improve the operational stability of cloud storage. Attached Figure Description
[0050] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0051] Figure 1 is a schematic diagram of a scenario of the data management method according to an embodiment of this application;
[0052] Figure 2 is a flowchart illustrating one embodiment of the data management method in this application.
[0053] Figure 3 is a flowchart illustrating an embodiment of the data management method for creating a target data cache volume provided in this application.
[0054] Figure 4 is a flowchart illustrating an embodiment of the data management method provided in this application for performing anomaly detection on a target data cache volume and obtaining cache volume detection results.
[0055] Figure 5 is a schematic diagram of the structure of an embodiment of the data management device provided in this application;
[0056] Figure 6 is a structural schematic diagram of an embodiment of the data management device provided in this application.
[0057] Implementation methods of this application
[0058] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0059] In the description of this application, it should be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," and "outer," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are used only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this application. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more of the stated features. In the description of this application, "a plurality of" means two or more, unless otherwise explicitly specified.
[0060] In this application, the term "exemplary" is used to mean "used as an example, illustration, or description." Any embodiment described as "exemplary" in this application is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use this application. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that this application can be made without using these specific details. In other instances, well-known structures and processes are not described in detail to avoid obscuring the description of this application with unnecessary detail. Therefore, this application is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in this application.
[0061] Currently, with the rapid development of internet and cloud storage technologies, more and more users are using cloud storage for model training or other business operations. For example, users can utilize distributed caching tools for machine learning training and other data provisioning. However, existing distributed caching tools and other cloud storage tools have drawbacks such as complex usage processes, inability to detect corrupted or corrupted files, and excessive storage space consumption, which can easily lead to data loss or anomalies and fail to meet users' cloud storage needs.
[0062] Based on this, this application proposes a data management method, apparatus, device, and computer-readable storage medium to solve the technical problem in the prior art that data loss or anomalies are easily caused when performing business tasks in cloud storage scenarios.
[0063] The data management method in this embodiment is applied to a data management device, which is provided in a data management equipment. The data management equipment includes one or more processors, a memory, and one or more applications. The one or more applications are stored in the memory and configured to be executed by the processor to implement the data management method. The data management equipment can be a smart terminal, such as a mobile phone, tablet computer, network device, and smart computer. Optionally, the data management equipment can also be a server or a service cluster composed of multiple servers.
[0064] As shown in Figure 1, which is a schematic diagram of a data management method according to an embodiment of this application, the data management scenario in this embodiment includes a data management device 100 (which integrates a data management unit) and a target cloud storage module 200. The data management device 100 runs a computer-readable storage medium corresponding to the data management method to execute the steps of the data management method. The target cloud storage module 200 is a distributed cloud storage terminal that interacts with the data management device 100 for data cloud storage. Optionally, in a specific embodiment, the target cloud storage module can be a JuiceFS distributed storage server.
[0065] It is understood that the data management device in the data management method scenario shown in Figure 1, or the device included in the data management device, does not constitute a limitation on the embodiments of this application. That is, the number or type of data management device included in the data management method scenario, or the number or type of device included in each device, does not affect the overall implementation of the technical solution in the embodiments of this application, and can all be considered as equivalent substitutions or derivatives of the technical solutions claimed in the embodiments of this application.
[0066] In this embodiment, the data management device 100 is mainly used for: responding to a data management request for a target cloud storage module, obtaining a target data cache volume in the target cloud storage module corresponding to the data management request; performing anomaly detection on the target data cache volume according to the target detection parameters of the target data cache volume and a preset detection database, and obtaining a cache volume detection result; and performing data management on the target data cache volume according to the cache volume detection result, and obtaining a data management result.
[0067] The data management device 100 in this application embodiment can be an independent data management device, such as a mobile phone, tablet computer, network device, server and smart computer, or a data management network or data management cluster composed of multiple data management devices.
[0068] This application provides a data management method, apparatus, device, and computer-readable storage medium, which will be described in detail below.
[0069] Those skilled in the art will understand that the application environment shown in Figure 1 is only one application scenario related to the solution of this application, and does not constitute a limitation on the application scenario of the solution of this application. Other application environments may include more or fewer data management devices or data management network connections than those shown in Figure 1. For example, only one data management device is shown in Figure 1. It is understood that the scenario of this data management method may also include one or more data management devices, which are not specifically limited here. The data management device 100 may also include a memory for storing detection data and other data.
[0070] It should be noted that the scenario diagram of the data management method shown in Figure 1 is merely an example. The scenario of the data management method described in the embodiments of this application is intended to more clearly illustrate the technical solution of the embodiments of this application and does not constitute a limitation on the technical solution provided in the embodiments of this application.
[0071] Based on the scenarios described above, various embodiments of the data management method disclosed in this application are proposed.
[0072] As shown in Figure 2, Figure 2 is a flowchart of an embodiment of the data management method in this application. The data management method includes the following steps 201 to 203:
[0073] 201. Respond to the data management request for the target cloud storage module and obtain the target data cache volume in the target cloud storage module corresponding to the data management request;
[0074] The data management method in this embodiment is applied to a data management device. The type and number of data management devices are not specifically limited. That is, the data management device can be one or more smart terminals or servers. In a specific embodiment, the data management device is a smart computer.
[0075] The target cloud storage module is communicatively connected to the data management device, capable of mounting the corresponding data cache volume locally on the data management device, receiving cached files accessed and uploaded by the data management device, and transmitting the cached files to the distributed cloud storage system of the cloud storage server via the cloud storage client. The target cloud storage module may include a cloud storage client and a cloud storage server. Optionally, in one specific embodiment, the target cloud storage module may be a distributed cloud storage system such as JuiceFS.
[0076] The target data cache volume is a cloud storage data cache volume that has been mounted and accessed locally in the target cloud storage module and is awaiting data management.
[0077] Specifically, during operation, the data management device can respond to data management requests associated with the target data cache volume mounted in the target cloud storage module. This data management request is an operation event performed during data operation and maintenance to analyze storage faults in the target data cache volume within the target cloud storage module and determine whether the cached data in the target data cache volume is abnormally faulty. Optionally, the triggering method for this data management request is not specifically limited; that is, the data management request can be actively triggered by the user. For example, the user can actively trigger the data management request for the target data cache volume by clicking the data management button corresponding to the target data cache volume in the target cloud storage module on the data management device. Furthermore, the data management request can also be automatically triggered by the data management device. For example, the data management device may have a pre-set data management process that automatically triggers the data management request for the target data cache volume when specific management conditions are met.
[0078] Specifically, after receiving a data management request associated with a target data cache volume, the data management device obtains the target data cache volume corresponding to the data management request. In subsequent steps, it performs a data volume health check and a data volume health status assessment on the target data cache volume to determine whether the cached data in the target data cache volume is faulty. That is, after receiving the data management request, the data management device parses the request to obtain the cache volume identifier carried in the request, and locates the target data cache volume corresponding to that identifier among the various mounted data cache volumes attached to the data management device.
[0079] Optionally, in one specific embodiment, before receiving a data management request associated with the target data cache volume, the data management device also configures the cloud storage client in the target cloud storage module, and then quickly creates a cache volume and mounts it to the data management device through the configured cloud storage client. That is, the data management device calls the cache volume creation interface and passes the data volume mounting parameters corresponding to the initial data volume to be generated to the preset orchestration application to generate the corresponding configuration file, and configures the initial data volume based on the configuration file to obtain the mounted data cache volume, and creates the data volume access interface and service exposure port corresponding to the mounted data cache volume, and checks whether the service exposure port is available. If the service port is available, it is determined that the mounting configuration of the mounted data cache volume is complete.
[0080] 202. Perform anomaly detection on the target data cache volume according to the target detection parameters and the preset detection database to obtain the cache volume detection result;
[0081] Specifically, after determining the target data cache volume corresponding to the data management request, the data management device also performs anomaly detection on the target data cache volume based on the target detection parameters of the target data cache volume and the preset detection database to obtain the cache volume detection result.
[0082] The target detection parameter is a detection parameter characterizing the data integrity of a specified cache file in the target data cache volume. Optionally, the target detection parameter can be a detection parameter obtained by performing specified data calculations on the specified cache data when synchronizing the specified cache data to the target data cache volume or when modifying the specified cache data in the target data cache volume.
[0083] Optionally, in one specific embodiment, the data management device can calculate target detection parameters when writing data to the target data cache volume. That is, after generating and mounting the target data cache volume, the data management device also pre-synchronizes the specified cache file data to the target data cache volume, and before synchronizing the specified cache file data to the target data cache volume, performs a hash operation on each specified cache file data to obtain the file data hash value corresponding to each specified cache file data, and determines the file data hash value as the target detection parameter of the specified cache file data. Optionally, in other embodiments, the target detection parameter can also be other detection parameters that can characterize the integrity of the cache file data besides the file data hash value. This embodiment does not impose specific limitations.
[0084] Specifically, the data management device also pre-creates a detection database associated with the target data cache volume, and stores the target detection parameters corresponding to each cached file in the target data cache volume into this detection database. That is, the data management device uses the file path corresponding to the cached file data as the data key and the target detection parameter as the data value in the detection database. Optionally, this detection database can be a Redis database or a local cache database.
[0085] Optionally, in another specific embodiment, the data management device can synchronously modify the target detection parameters of the cached data when modifying the cached data in the target data cache volume, thereby obtaining the modified target detection parameters. That is, when the data management device modifies the cached file data in the target cache data volume, it first obtains the target detection parameters associated with the cached file data in the detection database, locks the target detection parameters using a distributed lock, modifies the cached file data after locking the target detection parameters, obtains the modified file data, calculates the modification detection parameters corresponding to the modified file data, uses the modification detection parameters as the target detection parameters of the modified file data, and releases the distributed lock.
[0086] Optionally, in other embodiments, the target detection parameter may also be a folder detection parameter obtained by the data management device from data calculation of the cache folder in the target data cache volume.
[0087] Specifically, after determining the target detection parameters in each target data cache volume, the data management device can also respond to anomaly detection requests for that target data cache volume. Based on the anomaly detection request and the detection database, it locates the target detection file to be detected and its corresponding target detection parameters. Then, based on these target detection parameters and the anomaly detection parameters corresponding to the anomaly detection request, it performs a health check on the target data cache volume to determine its data health status. Based on this data health status, it outputs the corresponding cache volume detection result. This data health status represents the detection status indicating whether the target detection files in the target data cache volume exhibit abnormal faults such as data corruption.
[0088] Optionally, the data management device can also perform connectivity status detection on the target data cache volume. That is, the data management device periodically calls the cache volume interface of the target data cache volume according to a preset detection frequency to detect whether the cache volume interface of the target data cache volume can be accessed correctly, thereby determining whether the cache node of the target data cache volume is connected. The target data cache volume corresponding to the unconnected cache node is identified as an abnormal data cache volume, and the corresponding alarm information and cache volume detection results are output.
[0089] 203. Perform data management on the target data cache volume based on the cache volume detection results to obtain data management results.
[0090] Specifically, the data management device can also perform data management on the target data cache volume based on the cache volume detection results, and obtain data management results. That is, the data management device can back up and restore the anomaly detection files in the target data cache volume based on the cache volume detection results, thereby ensuring the validity of the cached file data in the target data cache volume, so as to ensure the stability of business execution based on the target data cache volume.
[0091] Specifically, the data management device also pre-configures a scheduled backup process. Based on this process, it reads the cached file data in the target data cache volume and the corresponding cache volume backup policy. This cache volume backup policy is a backup strategy that characterizes the corresponding data backup operation performed on the target data cache volume. Optionally, the cache volume backup policy includes a first backup policy and a second backup policy. The data management device can perform cache version backups of the cached file data according to the first backup policy and / or the second backup policy to obtain cache volume backup data. This cache volume backup data includes both first and second cache volume backup data, and is uploaded to a backup file database. The first backup policy is a backup strategy that performs metadata backup of the target data cache volume. The second backup policy is a backup strategy that uses the cache version management module to back up the target data cache volume. Optionally, the backup file database can be a NAS (Network Attached Storage) database.
[0092] Optionally, in one specific embodiment, the data management device can use the first backup strategy to read cache metadata containing basic data information from cached file data in the target data cache volume, generate first cache volume backup data based on the full cache metadata, and store the first cache volume backup data in the backup file database. The first cache volume backup data is the cache version metadata corresponding to the target data cache volume.
[0093] Optionally, in another specific embodiment, the data management device can use the second backup strategy to read cached file data in the target data cache volume, calculate the difference detection parameter between each cached file data and the historical cached file data, thereby determining incremental difference data where the difference detection parameter is not equal to a preset difference threshold, backing up the incremental difference data to obtain second cache volume backup data, and uploading the second cache volume backup data to the backup file database. Here, the second cache volume backup data represents the incremental backup data corresponding to the target data cache volume.
[0094] Specifically, the data management device reads the cache volume detection result corresponding to the target data cache volume. After determining that the cache volume detection result is an abnormal cache volume detection result, it also uses the cache volume backup data to perform metadata backup and recovery operations or version backup and recovery operations on the target data cache volume to obtain the data management result.
[0095] Optionally, in one specific embodiment, after determining that the cache volume detection result is an abnormal cache volume detection result, the data management device reads the latest version of cache version metadata associated with the target data cache volume from the backup file database as cache volume backup data, and uses the cache version metadata to perform metadata backup and restoration of the target data cache volume to obtain the data management result.
[0096] Optionally, in another specific embodiment, after determining that the cache volume detection result is an abnormal cache volume detection result, the data management device also uses the cache version management module to access the backup file database, obtain the cache volume backup data corresponding to the target data cache volume in the backup file database, and obtain the data upload instruction corresponding to the cache version management module. The data upload instruction is then used to back up and write the cache volume backup data to the target data volume to obtain the data management result.
[0097] In this embodiment, the data management device, in response to a data management request for a target cloud storage module, obtains the target data cache volume corresponding to the data management request within the target cloud storage module; performs anomaly detection on the target data cache volume based on the target detection parameters of the target data cache volume and a preset detection database, obtaining a cache volume detection result; and performs data management on the target data cache volume based on the cache volume detection result, obtaining a data management result. This achieves the following: upon receiving a data management request corresponding to a target data cache volume mounted in a target cloud storage module of distributed storage, the device obtains the target detection parameters corresponding to the specified storage file data in the target data cache volume and a preset detection database to perform anomaly detection on the target data cache volume, thereby assessing whether the storage files in the target data cache volume are corrupted or otherwise abnormal, obtaining a cache volume detection result, and performing data management on the target data cache volume based on the cache volume detection result to perform fault recovery operations such as fault recovery on abnormal storage files in the target data cache volume, obtaining a data management result. This improves data security in distributed cloud storage, reduces the probability of cloud storage data volume loss, and improves the operational stability of cloud storage.
[0098] As shown in Figure 3, Figure 3 is a flowchart illustrating an embodiment of the data management method for creating a target data cache volume provided in this application. Specifically, in this embodiment, the data management method further includes steps 301 to 302:
[0099] 301. Obtain the initial data volume to be configured, and the data volume mount parameters of the initial data volume;
[0100] 302. Configure the initial data volume according to the data volume mounting parameters and the preset initial configuration file to obtain the mounted data cache volume.
[0101] Based on the above embodiments, in this embodiment, before receiving a data management request associated with the target data cache volume, the data management device also configures the cloud storage client in the target cloud storage module, and then quickly creates a cache volume and mounts it to the data management device through the configured cloud storage client, thereby improving the cache volume generation efficiency and simplifying the cache volume generation complexity.
[0102] Specifically, during operation, the data management device can acquire the initial data volume to be configured and receive the corresponding data volume mount parameters. These mount parameters include a data volume mount identifier and a data volume mount point. The mount identifier is the name identifier of the cache volume after the initial data volume is mounted. The mount point is the mount path corresponding to the initial data volume.
[0103] Specifically, the data management device also obtains the initial configuration file corresponding to the cache volume mount request, and the initial data variables in the initial configuration file. The initial configuration file is a configuration template file for mounting the initial data volume. The initial data variables are configuration template variables in the initial data volume to be mounted. Optionally, in one specific embodiment, the initial configuration file can be a YAML concatenation file. Optionally, in one specific embodiment, the file code of an example of the initial configuration file is shown below:
[0104] In this specific embodiment, the initial data variables of the initial configuration file are #{juicefs.volume.spec|4} and #{juicefs.volume.spec|10}. Here, (|4) and (|10) represent the number of spaces that need to be added before each line when replacing variables.
[0105] Specifically, after obtaining the data volume mount parameters, initial configuration file, and initial data variables, the data management device also updates the initial data volume using these parameters and variables to obtain a mounted data cache volume. That is, the data management device obtains the data mount identifier and mount point from the cached mounted data volume, and generates a data volume mount string based on these identifiers. In other words, the data management device concatenates the data volume mount identifier and mount point into a data volume mount string.
[0106] Optionally, before generating the data volume mount string, the data management device also determines whether there are duplicate data volume mount identifiers or duplicate data volume mount points. If there are no duplicate data volume mount identifiers or duplicate data volume mount points, the data volume mount string is generated based on the data volume mount identifier and data volume mount point.
[0107] Specifically, after obtaining the data volume mount string, the data management device updates the initial data volume variables in the initial configuration file according to the data volume mount string to obtain the target configuration file. That is, the data management device uses the data volume mount string to replace the initial data volume variables in the initial configuration file to obtain a target configuration file containing the target data volume variables.
[0108] Optionally, in one specific embodiment, the data mount identifier is date_dvc, and the data volume mount point is / date / dvc. The file code for one embodiment of the target configuration file is shown below:
[0109] Specifically, after generating the target configuration file, the data management device also performs mounting configuration on the initial data volume according to the target configuration file to obtain the mounted data cache volume.
[0110] Specifically, after generating the mounted data cache volume, the data management device also responds to the data management request, obtains the cache volume identifier in the data management request, and reads the target data cache volume in the mounted data cache volume whose data volume identifier is the same as the cache volume identifier.
[0111] In this embodiment, the data management device, in response to a cache volume mount request, obtains the initial data volume corresponding to the cache volume mount request, as well as the data volume mount parameters of the initial data volume; obtains the initial configuration file corresponding to the cache volume mount request, as well as the initial data volume variables of the initial configuration file; updates the initial data volume according to the data volume mount parameters and the initial data volume variables to obtain the mounted data cache volume; and reads the target data cache volume in the mounted data cache volume according to the cache volume identifier in the data management request. This achieves data cache volume creation through the orchestration of the cache creation process, improving the efficiency of cache volume creation in distributed cloud storage and simplifying the complexity of cache volume creation.
[0112] As shown in Figure 4, Figure 4 is a flowchart illustrating an embodiment of the data management method provided in this application for performing anomaly detection on a target data cache volume and obtaining the cache volume detection result. Specifically, in this embodiment, the data management method further includes steps 401 to 404:
[0113] 401. Respond to the anomaly detection request for the target data cache volume and generate anomaly detection parameters corresponding to the anomaly detection request;
[0114] 402. Determine the target detection file in the target data cache volume based on the anomaly detection parameters and the preset detection database;
[0115] 403. Perform a hash operation on the target detection file to obtain the target detection parameters of the target detection file;
[0116] 404: Anomaly detection is performed on the target data cache volume based on the target detection parameters and the anomaly detection parameters to obtain the cache volume detection result.
[0117] Based on the above embodiments, in this embodiment, the data management device can respond to anomaly detection requests for the target data cache volume, locate the target detection file to be detected and the corresponding target detection parameters based on the anomaly detection request and the detection database, and then perform a health check on the target data cache volume based on the target detection parameters and the anomaly detection parameters corresponding to the anomaly detection request, thereby determining the data health status of the target data cache volume, and outputting the corresponding cache volume detection result based on the data health status. Here, the data health status is a detection status characterizing whether there are any abnormal faults such as data corruption in the target detection file of the target data cache volume.
[0118] Specifically, during operation, the data management device can receive anomaly detection requests for the target data cache volume. These anomaly detection requests are operation events that drive the data management device to perform health checks on the specified target data cache volume.
[0119] Specifically, after receiving an anomaly detection request, the data management device uses a random sampling module to generate several anomaly detection parameters corresponding to the anomaly detection request, and performs parallel detection on the target data cache volume based on these anomaly detection parameters to determine the data health status of the target data cache volume. The anomaly detection parameters are sampling detection parameters randomly generated by the random sampling module and associated with the target data cache volume. Optionally, in one specific embodiment, the anomaly detection parameter can be a hash value.
[0120] Specifically, after acquiring the anomaly detection parameters, the data management device determines the target detection file for the target data cache volume based on these parameters and a preset detection database. That is, the data management device accesses the detection database, inputs the anomaly detection parameters, and uses these parameters to locate the target detection file to be detected in the target data cache volume of the detection database. The target detection file is cached file data with a file hash value identical to the anomaly detection parameters.
[0121] Specifically, after identifying the target detection file to be detected, the data management device performs a hash operation on the target detection file stored in the target data cache volume to obtain the target detection hash value of the target detection file. The target detection hash value is used as the target detection parameter of the target detection file, and the target detection parameter is compared with the anomaly detection parameter to determine whether the target detection file in the target data cache volume is abnormal, thereby obtaining the cache volume detection result.
[0122] Optionally, in one specific embodiment, before the data management device uses the detection database to determine the target detection file of the target data cache volume, it also generates a detection database corresponding to the target data cache volume. That is, the data management device obtains cached file data in the target data cache volume, performs calculations on the cached file data, and obtains the cached file calculation value corresponding to the cached file data. The cached file calculation value and the cached file data are associated and stored in a preset database to obtain an initial detection database. According to the data addition instruction in the preset cache version management module, the initial detection database is added to the local cache module to obtain the detection database corresponding to the target data cache volume. Here, the preset cache version management module is a DVC (Data Version Control) module, and the data addition instruction is a dvc add instruction.
[0123] Specifically, after acquiring the target detection file, the data management device performs a hash operation on the file to obtain its current target detection parameters. Based on these newly acquired parameters and anomaly detection parameters, it then performs anomaly detection on the target cache volume to obtain the cache volume detection result. In other words, the data management device calculates the current target detection parameters and compares them with the anomaly detection parameters to determine whether the data integrity of the target detection file has changed, thereby outputting the corresponding cache volume detection result.
[0124] Optionally, if the target detection parameter and the anomaly detection parameter are the same, the data management device determines that the current data of the target detection file is the same as the data when it was written to or modified to the target data cache volume, and determines that the target detection file is a normal detection file.
[0125] Optionally, if the target detection parameters and the anomaly detection parameters are different, the data management device determines that the data of the target detection file has changed and determines that the target detection file is an anomaly detection file with corrupted data.
[0126] Optionally, if the data management device detects each target detection file and determines that the abnormal detection file exists in the target data cache volume, then the cache volume detection result of the target data cache volume is determined as the abnormal cache volume detection result.
[0127] Specifically, after determining that an abnormal cache volume has been detected due to data corruption in the target data cache volume, the data management device can accurately back up and restore the abnormal detection files in the target data cache volume, thereby ensuring the validity of the cached file data in the target data cache volume and ensuring the stability of business operations based on the target data cache volume.
[0128] In this embodiment, the data management device generates anomaly detection parameters corresponding to the anomaly detection request in response to the anomaly detection request for the target data cache volume; determines the target detection file in the target data cache volume based on the anomaly detection parameters and a preset detection database; performs a hash operation on the target detection file to obtain the target detection parameters of the target detection file; and performs anomaly detection on the target data cache volume based on the target detection parameters and the anomaly detection parameters to obtain the cache volume detection result. This enables accurate identification of whether cached file data in the target data cache volume has data corruption or other anomalies, thereby improving the accuracy and timeliness of data detection and data repair, ensuring the validity of cached file data in the target data cache volume, and guaranteeing the stability of business execution based on the target data cache volume.
[0129] To better implement the data management method in the embodiments of this application, a data management device is also provided in the embodiments of this application, as shown in FIG5. FIG5 is a structural schematic diagram of an embodiment of the data management device provided in the embodiments of this application. Specifically, the data management device 500 includes:
[0130] The cache volume acquisition module 501 is configured to respond to a data management request for a target cloud storage module and acquire the target data cache volume in the target cloud storage module corresponding to the data management request.
[0131] The cache volume detection module 502 is configured to perform anomaly detection on the target data cache volume according to the target detection parameters of the target data cache volume and a preset detection database, and obtain the cache volume detection result.
[0132] The data management module 503 is configured to perform data management on the target data cache volume based on the cache volume detection result, and obtain the data management result.
[0133] In one possible implementation of this embodiment, before the data management device obtains the target data cache volume in the target cloud storage module corresponding to the data management request, it further includes:
[0134] Obtain the initial data volume to be configured, and the data volume mount parameters of the initial data volume;
[0135] Configure the initial data volume according to the data volume mount parameters and the preset initial configuration file to obtain the mounted data cache volume;
[0136] The step of obtaining the target data cache volume in the target cloud storage module corresponding to the data management request includes:
[0137] The target data cache volume in the mounted data cache volume is read based on the cache volume identifier in the data management request.
[0138] In one possible implementation of this embodiment, before obtaining the data management result, the data management device performs data management on the target data cache volume based on the cache volume detection result, and further includes:
[0139] Obtain the cache volume backup policy corresponding to the target data cache volume;
[0140] The target data cache volume is backed up using the cache volume backup strategy to obtain cache volume backup data;
[0141] The step of performing data management on the target data cache volume based on the cache volume detection result to obtain the data management result includes:
[0142] If the cache volume detection result is determined to be an abnormal cache volume detection result, the target data cache volume is restored using the cache volume backup data to obtain the data management result.
[0143] In one possible implementation of this embodiment, the data management device configures the initial data volume according to the data volume mounting parameters and a preset initial configuration file to obtain a mounted data cache volume, including:
[0144] Obtain the data volume mount identifier and data volume mount point from the data volume mount parameters, and generate a data volume mount string based on the data volume mount identifier and data volume mount point;
[0145] The initial data volume variable of the initial configuration file is updated according to the data volume mount string to obtain the target configuration file;
[0146] The initial data volume is mounted according to the target configuration file to obtain the mounted data cache volume.
[0147] In one possible implementation of this embodiment, the data management device performs anomaly detection on the target data cache volume based on the target detection parameters and a preset detection database to obtain cache volume detection results, including:
[0148] In response to an anomaly detection request for the target data cache volume, generate anomaly detection parameters corresponding to the anomaly detection request;
[0149] The target detection file in the target data cache volume is determined based on the anomaly detection parameters and the preset detection database;
[0150] Perform a hash operation on the target detection file to obtain the target detection parameters of the target detection file;
[0151] Anomaly detection is performed on the target data cache volume based on the target detection parameters and the anomaly detection parameters to obtain the cache volume detection result.
[0152] In one possible implementation of this embodiment, before the data management device determines the target detection file in the target data cache volume based on the anomaly detection parameters and the preset detection database, it further includes:
[0153] Obtain cached file data from the target data cache volume, perform calculations on the cached file data, and obtain the cached file operation value corresponding to the cached file data;
[0154] The cached file operation value and the cached file data are associated and stored in a preset database to obtain the initial detection database;
[0155] The initial detection database is added to the local cache module according to the data addition instruction in the preset cache version management module, thereby obtaining the detection database corresponding to the target data cache volume.
[0156] In one possible implementation of this embodiment, the data management device performs anomaly detection on the target data cache volume based on the target detection parameters and the anomaly detection parameters to obtain a cache volume detection result, including:
[0157] If the target detection parameters and the anomaly detection parameters are the same, then the target detection file is determined to be a normal detection file;
[0158] If the target detection parameters and the anomaly detection parameters are different, then the target detection file is determined to be an anomaly detection file;
[0159] If the anomaly detection file exists in the target data cache volume, then the cache volume detection result of the target data cache volume is determined to be the anomaly cache volume detection result.
[0160] In one possible implementation of this embodiment, the data management device performs data management on the target data cache volume based on the cache volume detection result, and obtains a data management result, including:
[0161] Read the cache volume detection result and determine that the cache volume detection result is an abnormal cache volume detection result;
[0162] Obtain the cache volume backup data of the target data cache volume, as well as the data upload command from the cache version management module;
[0163] The data upload command is used to write the cache volume backup data to the target data cache volume, thereby obtaining the data management result.
[0164] In this embodiment, the data management device, in response to a data management request for a target cloud storage module, obtains the target data cache volume corresponding to the data management request within the target cloud storage module; performs anomaly detection on the target data cache volume based on the target detection parameters of the target data cache volume and a preset detection database, obtaining a cache volume detection result; and performs data management on the target data cache volume based on the cache volume detection result, obtaining a data management result. This achieves the following: upon receiving a data management request corresponding to a target data cache volume mounted in the target cloud storage module of the distributed storage, the device obtains the target detection parameters corresponding to the specified storage file data in the target data cache volume and a preset detection database to perform anomaly detection on the target data cache volume, thereby assessing whether the storage files in the target data cache volume are corrupted or otherwise abnormal, obtaining a cache volume detection result, and performing data management on the target data cache volume based on the cache volume detection result, including fault recovery operations for abnormal storage files in the target data cache volume, obtaining a data management result. This improves data security in distributed cloud storage, reduces the probability of cloud storage data volume loss, and enhances the operational stability of cloud storage.
[0165] This application also provides a data management device, as shown in FIG6, which is a schematic diagram of an embodiment of the data management device provided in this application.
[0166] The data management device integrates any of the data management apparatuses provided in the embodiments of this application, and the data management device includes:
[0167] One or more processors;
[0168] Memory; and
[0169] One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor of the steps in the data management method described in any of the above embodiments of the data management method.
[0170] Specifically, the data management device may include components such as a processor 601 with one or more processing cores, a memory 602 with one or more computer-readable storage media, a power supply 603, and an input unit 604. Those skilled in the art will understand that the data management device structure shown in Figure 6 does not constitute a limitation on the data management device, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0171] The processor 601 is the control center of the data management device. It connects various parts of the data management device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 602, and by calling data stored in the memory 602, it performs various functions and processes data, thereby providing overall monitoring of the data management device. Optionally, the processor 601 may include one or more processing cores; preferably, the processor 601 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 601.
[0172] The memory 602 can be used to store software programs and modules. The processor 601 executes various functional applications and data processing by running the software programs and modules stored in the memory 602. The memory 602 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the data management device, etc. In addition, the memory 602 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 602 may also include a memory controller to provide the processor 601 with access to the memory 602.
[0173] The data management device also includes a power supply 603 that supplies power to the various components. Preferably, the power supply 603 can be logically connected to the processor 601 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 603 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.
[0174] The data management device may also include an input unit 604, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
[0175] Although not shown, the data management device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 601 in the data management device loads the executable files corresponding to the processes of one or more applications into the memory 602 according to the following instructions, and the processor 601 runs the applications stored in the memory 602 to realize various functions, as follows:
[0176] In response to a data management request for a target cloud storage module, obtain the target data cache volume in the target cloud storage module corresponding to the data management request;
[0177] Anomaly detection is performed on the target data cache volume based on the target detection parameters and the preset detection database to obtain the cache volume detection result;
[0178] Based on the cache volume detection results, data management is performed on the target data cache volume to obtain the data management results.
[0179] Therefore, embodiments of this application provide a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk, etc. A computer program is stored thereon, which is loaded by a processor to execute the steps in any of the data management methods provided in embodiments of this application. For example, the computer program loaded by the processor can execute the following steps:
[0180] In response to a data management request for a target cloud storage module, obtain the target data cache volume in the target cloud storage module corresponding to the data management request;
[0181] Anomaly detection is performed on the target data cache volume based on the target detection parameters and the preset detection database to obtain the cache volume detection result;
[0182] Based on the cache volume detection results, data management is performed on the target data cache volume to obtain the data management results.
[0183] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the detailed descriptions of other embodiments above, which will not be repeated here.
[0184] In practice, each of the above units or structures can be implemented as an independent entity or can be arbitrarily combined to be implemented as the same or several entities. For the specific implementation of each of the above units or structures, please refer to the previous method embodiments, which will not be repeated here.
[0185] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.
[0186] The data management method provided by the embodiments of this application has been described in detail above. Specific embodiments have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A data management method, wherein, The data management method includes: In response to a data management request for a target cloud storage module, obtain the target data cache volume in the target cloud storage module corresponding to the data management request; Anomaly detection is performed on the target data cache volume based on the target detection parameters and the preset detection database to obtain the cache volume detection result; Based on the cache volume detection results, data management is performed on the target data cache volume to obtain the data management results.
2. The data management method according to claim 1, wherein, Before obtaining the target data cache volume in the target cloud storage module corresponding to the data management request, the method further includes: Obtain the initial data volume to be configured, and the data volume mount parameters of the initial data volume; The initial data volume is configured according to the data volume mount parameters and the preset initial configuration file to obtain the mounted data cache volume.
3. The data management method according to claim 2, wherein, The step of obtaining the target data cache volume in the target cloud storage module corresponding to the data management request includes: The target data cache volume in the mounted data cache volume is read based on the cache volume identifier in the data management request.
4. The data management method according to claim 1, wherein, Before performing data management on the target data cache volume based on the cache volume detection result and obtaining the data management result, the method further includes: Obtain the cache volume backup policy corresponding to the target data cache volume; The target data cache volume is backed up using the cache volume backup strategy to obtain cache volume backup data; The step of performing data management on the target data cache volume based on the cache volume detection result to obtain the data management result includes: If the cache volume detection result is determined to be an abnormal cache volume detection result, the target data cache volume is restored using the cache volume backup data to obtain the data management result.
5. The data management method according to claim 2, wherein, The step of configuring the initial data volume according to the data volume mount parameters and the preset initial configuration file to obtain the mounted data cache volume includes: Obtain the data volume mount identifier and data volume mount point from the data volume mount parameters, and generate a data volume mount string based on the data volume mount identifier and data volume mount point; The initial data volume variable of the initial configuration file is updated according to the data volume mount string to obtain the target configuration file; The initial data volume is mounted according to the target configuration file to obtain the mounted data cache volume.
6. The data management method according to claim 1, wherein, The step of performing anomaly detection on the target data cache volume based on the target detection parameters and a preset detection database to obtain cache volume detection results includes: In response to an anomaly detection request for the target data cache volume, generate anomaly detection parameters corresponding to the anomaly detection request; The target detection file in the target data cache volume is determined based on the anomaly detection parameters and the preset detection database; Perform a hash operation on the target detection file to obtain the target detection parameters of the target detection file; Anomaly detection is performed on the target data cache volume based on the target detection parameters and the anomaly detection parameters to obtain the cache volume detection result.
7. The data management method according to claim 6, wherein, Before determining the target detection file in the target data cache volume based on the anomaly detection parameters and the preset detection database, the method further includes: Obtain cached file data from the target data cache volume, perform calculations on the cached file data, and obtain the cached file operation value corresponding to the cached file data; The cached file operation value and the cached file data are associated and stored in a preset database to obtain the initial detection database; The initial detection database is added to the local cache module according to the data addition instruction in the preset cache version management module, thereby obtaining the detection database corresponding to the target data cache volume.
8. The data management method according to claim 6, wherein, The step of performing anomaly detection on the target data cache volume based on the target detection parameters and the anomaly detection parameters to obtain the cache volume detection result includes: If the target detection parameters and the anomaly detection parameters are the same, then the target detection file is determined to be a normal detection file; If the target detection parameters and the anomaly detection parameters are different, then the target detection file is determined to be an anomaly detection file; If the anomaly detection file exists in the target data cache volume, then the cache volume detection result of the target data cache volume is determined to be the anomaly cache volume detection result.
9. The data management method according to claim 1, wherein, The step of performing data management on the target data cache volume based on the cache volume detection result to obtain the data management result includes: Read the cache volume detection result and determine that the cache volume detection result is an abnormal cache volume detection result; Obtain the cache volume backup data of the target data cache volume, as well as the data upload command from the cache version management module; The data upload command is used to write the cache volume backup data to the target data cache volume, thereby obtaining the data management result.
10. A data management device, wherein, The data management device includes: The cache volume acquisition module is configured to respond to a data management request for a target cloud storage module and acquire the target data cache volume in the target cloud storage module that corresponds to the data management request. The cache volume detection module is configured to perform anomaly detection on the target data cache volume based on the target detection parameters of the target data cache volume and a preset detection database, and obtain the cache volume detection result. The data management module is configured to perform data management on the target data cache volume based on the cache volume detection results, and obtain data management results.
11. The data management device according to claim 10, wherein, Before the cache volume acquisition module acquires the target data cache volume in the target cloud storage module corresponding to the data management request, it is further configured to: Obtain the initial data volume to be configured, and the data volume mount parameters of the initial data volume; The initial data volume is configured according to the data volume mount parameters and the preset initial configuration file to obtain the mounted data cache volume.
12. The data management device according to claim 11, wherein, The cache volume acquisition module acquires the target data cache volume in the target cloud storage module corresponding to the data management request, including: The target data cache volume in the mounted data cache volume is read based on the cache volume identifier in the data management request.
13. The data management device according to claim 10, wherein, The data management module performs data management on the target data cache volume based on the cache volume detection result. Before obtaining the data management result, it is also used for: Obtain the cache volume backup policy corresponding to the target data cache volume; The target data cache volume is backed up using the cache volume backup strategy to obtain cache volume backup data; The data management module performs data management on the target data cache volume based on the cache volume detection results, and obtains data management results, including: If the cache volume detection result is determined to be an abnormal cache volume detection result, the target data cache volume is restored using the cache volume backup data to obtain the data management result.
14. The data management device according to claim 11, wherein, The cache volume acquisition module configures the initial data volume according to the data volume mount parameters and the preset initial configuration file to obtain the mounted data cache volume, including: Obtain the data volume mount identifier and data volume mount point from the data volume mount parameters, and generate a data volume mount string based on the data volume mount identifier and data volume mount point; The initial data volume variable of the initial configuration file is updated according to the data volume mount string to obtain the target configuration file; The initial data volume is mounted according to the target configuration file to obtain the mounted data cache volume.
15. The data management device according to claim 10, wherein, The cache volume detection module performs anomaly detection on the target data cache volume based on the target detection parameters and a preset detection database, and obtains cache volume detection results, including: In response to an anomaly detection request for the target data cache volume, generate anomaly detection parameters corresponding to the anomaly detection request; The target detection file in the target data cache volume is determined based on the anomaly detection parameters and the preset detection database; Perform a hash operation on the target detection file to obtain the target detection parameters of the target detection file; Anomaly detection is performed on the target data cache volume based on the target detection parameters and the anomaly detection parameters to obtain the cache volume detection result.
16. The data management device according to claim 15, wherein, Before the cache volume detection module determines the target detection file in the target data cache volume based on the anomaly detection parameters and the preset detection database, it is further configured to: Obtain cached file data from the target data cache volume, perform calculations on the cached file data, and obtain the cached file operation value corresponding to the cached file data; The cached file operation value and the cached file data are associated and stored in a preset database to obtain the initial detection database; The initial detection database is added to the local cache module according to the data addition instruction in the preset cache version management module, thereby obtaining the detection database corresponding to the target data cache volume.
17. The data management device according to claim 15, wherein, The cache volume detection module performs anomaly detection on the target data cache volume based on the target detection parameters and the anomaly detection parameters, and obtains cache volume detection results, including: If the target detection parameters and the anomaly detection parameters are the same, then the target detection file is determined to be a normal detection file; If the target detection parameters and the anomaly detection parameters are different, then the target detection file is determined to be an anomaly detection file; If the anomaly detection file exists in the target data cache volume, then the cache volume detection result of the target data cache volume is determined to be the anomaly cache volume detection result.
18. The data management device according to claim 10, wherein, The data management module performs data management on the target data cache volume based on the cache volume detection results, and obtains data management results, including: Read the cache volume detection result and determine that the cache volume detection result is an abnormal cache volume detection result; Obtain the cache volume backup data of the target data cache volume, as well as the data upload command from the cache version management module; The data upload command is used to write the cache volume backup data to the target data cache volume, thereby obtaining the data management result.
19. A data management device, wherein, The data management device includes: One or more processors; Memory; and One or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the processor to implement the steps of the data management method according to any one of claims 1 to 9.
20. A computer-readable storage medium, wherein, It stores a computer program, which is loaded by a processor to execute the steps of the data management method according to any one of claims 1 to 9.