CN112130770A - Maintenance data storage method, system, equipment and medium - Google Patents
Maintenance data storage method, system, equipment and medium Download PDFInfo
- Publication number
- CN112130770A CN112130770A CN202010988138.2A CN202010988138A CN112130770A CN 112130770 A CN112130770 A CN 112130770A CN 202010988138 A CN202010988138 A CN 202010988138A CN 112130770 A CN112130770 A CN 112130770A
- Authority
- CN
- China
- Prior art keywords
- data
- maintenance
- expansion area
- service
- service data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000012423 maintenance Methods 0.000 title claims abstract description 89
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000013500 data storage Methods 0.000 title claims abstract description 4
- 230000008521 reorganization Effects 0.000 claims abstract description 18
- 230000008569 process Effects 0.000 claims abstract description 13
- 230000004044 response Effects 0.000 claims abstract description 11
- 230000002159 abnormal effect Effects 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 8
- 238000010586 diagram Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000005299 abrasion Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000003139 buffering effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000004321 preservation Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0614—Improving the reliability of storage systems
- G06F3/0619—Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/061—Improving I/O performance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0629—Configuration or reconfiguration of storage systems
- G06F3/0631—Configuration or reconfiguration of storage systems by allocating resources to storage systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/0644—Management of space entities, e.g. partitions, extents, pools
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a maintenance data storage method, which comprises the following steps: reorganizing the service data in response to receiving the service data; acquiring maintenance data generated in the business data reorganization process, and recording the maintenance data in a preset data expansion area; and in response to the completion of the reorganization of the service data, forming a new data block by the service data and the corresponding maintenance data recorded in the data expansion area, and storing the new data block in a data disk. The invention also discloses a system, a computer device and a readable storage medium. The scheme provided by the invention enables the maintenance data and the service data to form a new data block and store the new data block on the back-end data disk, so that the maintenance data is stored adjacently along with the service data, can be directly read, and has high positioning efficiency. Meanwhile, data maintenance does not depend on an external storage space, and no system disk is worn. Meanwhile, the problem that log information cannot ensure whether the log falls after the data falls when the log is recorded asynchronously is avoided.
Description
Technical Field
The present invention relates to the field of data processing, and in particular, to a method, a system, a device, and a storage medium for storing maintenance data.
Background
In the era of dramatic increase of storage devices, storage applications are varied, and as storage systems become more complex, in a development stage, when a problem (particularly a data inconsistency problem) occurs on an IO path, positioning becomes very difficult. For development, the most direct and effective way to locate problems is to analyze logs and clear the context of business logic, thereby finding problem points. The industry typically adds logs by: recording a log on a system disk; dumping the log to other log servers; however, more or less problems exist, for example, the method firstly has a high requirement on the capacity of a system disk, the abrasion of the system disk is also aggravated when the log amount on the IO path is very large, and the method secondly depends on external storage and transmission bandwidth, so that the use cost and the performance often do not reach the standard.
Disclosure of Invention
In view of the above, in order to overcome at least one aspect of the above problem, an embodiment of the present invention provides a method for storing maintenance data, including the following steps:
reorganizing the service data in response to receiving the service data;
acquiring maintenance data generated in the business data reorganization process, and recording the maintenance data in a preset data expansion area;
and in response to the completion of the reorganization of the service data, forming a new data block by the service data and the corresponding maintenance data recorded in the data expansion area, and storing the new data block in a data disk.
In some embodiments, further comprising:
creating a data expansion area interface;
and setting configuration parameters of the data expansion area through the data expansion area interface.
In some embodiments, further comprising:
and responding to the abnormal business data, and acquiring the business data and corresponding maintenance data in the data disc according to the storage address of the business data.
In some embodiments, further comprising:
and analyzing the reason of the abnormal business data according to the maintenance data.
In some embodiments, the obtaining maintenance data generated in the business data reorganization process and recording the maintenance data in a preset data expansion area further includes:
recording maintenance data corresponding to the service data through the context of the IO stack;
and acquiring corresponding maintenance data in the context of the IO stack according to the KEY for maintaining the data.
In some embodiments, recording, by the context of the IO stack, maintenance data corresponding to the service data, further includes:
and recording path information and log information corresponding to the service data through the context of the IO stack.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a maintenance system for maintaining data, including:
a receiving module configured to reorganize service data in response to receiving the service data;
the recording module is configured to acquire maintenance data generated in the business data reorganization process and record the maintenance data to a preset data expansion area;
and the landing module is configured to respond to the completion of reorganization of the service data, and store the service data and the corresponding maintenance data recorded in the data expansion area into a data disk after forming a new data block.
In some embodiments, further comprising a creation module configured to:
creating a data expansion area interface;
and setting configuration parameters of the data expansion area through the data expansion area interface.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer apparatus, including:
at least one processor; and
a memory storing a computer program operable on the processor, wherein the processor executes the program to perform any of the steps of the method for maintaining data as described above.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a computer-readable storage medium, which stores a computer program that, when executed by a processor, performs the steps of any of the maintenance data saving methods described above.
The invention has one of the following beneficial technical effects: the scheme provided by the invention enables the maintenance data and the service data to form a new data block and store the new data block on the back-end data disk, so that the maintenance data is stored adjacently along with the service data, can be directly read, and has high positioning efficiency. Meanwhile, data maintenance does not depend on an external storage space, and no system disk is worn. Meanwhile, the problem that log information cannot ensure whether the log falls after the data falls when the log is recorded asynchronously is avoided.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other embodiments can be obtained by using the drawings without creative efforts.
Fig. 1 is a schematic flow chart of a maintenance data saving method according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a maintenance data saving system according to an embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a computer device provided in an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a computer-readable storage medium according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the following embodiments of the present invention are described in further detail with reference to the accompanying drawings.
It should be noted that all expressions using "first" and "second" in the embodiments of the present invention are used for distinguishing two entities with the same name but different names or different parameters, and it should be noted that "first" and "second" are merely for convenience of description and should not be construed as limitations of the embodiments of the present invention, and they are not described in any more detail in the following embodiments.
According to an aspect of the present invention, an embodiment of the present invention provides a method for saving maintenance data, as shown in fig. 1, which may include the steps of:
s1, responding to the received service data, reorganizing the service data;
s2, obtaining maintenance data generated in the business data reorganization process, and recording the maintenance data in a preset data expansion area;
s3, in response to the completion of the reorganization of the service data, the service data and the corresponding maintenance data recorded in the data extension area are combined into a new data block and then stored in a data disk.
The scheme provided by the invention enables the maintenance data and the service data to form a new data block and store the new data block on the back-end data disk, so that the maintenance data is stored adjacently along with the service data, can be directly read, and has high positioning efficiency. Meanwhile, data maintenance does not depend on an external storage space, and no system disk is worn.
In some embodiments, further comprising:
creating a data expansion area interface;
and setting configuration parameters of the data expansion area through the data expansion area interface.
Specifically, a data expansion area interface may be newly added, and the function of determining whether to open the data expansion area, that is, whether to open the data expansion area and drop the maintenance data and the service data together may be realized through the interface. If the function is started, all maintenance data generated by reorganizing the service data are recorded in the data expansion area before the service data are received and the service data are reorganized, after the service data are reorganized, the maintenance data corresponding to the service data are extracted from the data expansion area to form a new data block, and the service data and the maintenance data are stored in adjacent positions by landing, so that the maintenance data corresponding to the service data can be conveniently and quickly acquired while the service data are acquired in the follow-up process.
In some embodiments, the configuration of the data extension area may also be implemented through the data extension area interface, for example, setting the size of the data extension area, setting the level of maintenance data in the data extension area, and the like.
In some embodiments, further comprising:
and responding to the abnormal business data, and acquiring the business data and corresponding maintenance data in the data disc according to the storage address of the business data.
Specifically, when the service data and the maintenance data form a new database and are stored on the data disk, the size of the data block may be the same, that is, the size of each data block may be specified, so that the storage location of each service data may be determined.
In some embodiments, further comprising:
and analyzing the reason of the abnormal business data according to the maintenance data.
Specifically, when the service data is abnormal, for example, the service data is inconsistent, the position of the corresponding maintenance data may be quickly determined according to the position of the data in the data disk, so as to acquire the corresponding maintenance data from the data disk. Therefore, when the service data is abnormal, the corresponding maintenance data can be quickly found, and then corresponding analysis processing is carried out.
In some embodiments, the obtaining maintenance data generated in the business data reorganization process and recording the maintenance data in a preset data expansion area further includes:
recording maintenance data corresponding to the service data through the context of the IO stack;
and acquiring corresponding maintenance data in the context of the IO stack according to the KEY for maintaining the data.
In some embodiments, recording, by the context of the IO stack, maintenance data corresponding to the service data, further includes:
and recording path information and log information corresponding to the service data through the context of the IO stack.
Specifically, the data extension area may store, in the form of an IO stack, maintenance data generated during the data reorganization process of a plurality of service data. The maintenance data may include all path information from the generation of the service data from the upper layer to the buffering to the disk-dropping, and also include log information generated when data reorganization is performed, such as a change in data structure, and the like. And then, recording the maintenance data corresponding to each service data through the context information of the IO stack, and acquiring the corresponding maintenance data from the IO stack when the disk is dropped, so that the new data block is formed and then the disk is dropped.
The scheme provided by the invention enables the maintenance data and the service data to form a new data block and store the new data block on the back-end data disk, so that the maintenance data is stored adjacently along with the service data, can be directly read, and has high positioning efficiency. Meanwhile, data maintenance does not depend on an external storage space, and no system disk is worn. Meanwhile, the problem that log information cannot ensure whether the log falls after the data falls when the log is recorded asynchronously is avoided.
Based on the same inventive concept, according to another aspect of the present invention, an embodiment of the present invention further provides a preservation system 400 for maintaining data, as shown in fig. 2, including:
a receiving module 401, where the receiving module 401 is configured to reorganize the service data in response to receiving the service data;
a recording module 402, where the recording module 402 is configured to acquire maintenance data generated in the business data reorganization process, and record the maintenance data in a preset data expansion area;
a disk dropping module 403, where the disk dropping module 403 is configured to, in response to that the business data is reorganized, combine the business data and the corresponding maintenance data recorded in the data extension area into a new data block and store the new data block in a data disk.
In some embodiments, further comprising a creation module configured to:
creating a data expansion area interface;
and setting configuration parameters of the data expansion area through the data expansion area interface.
In some embodiments, further comprising an exception handling module configured to:
and responding to the abnormal business data, and acquiring the business data and corresponding maintenance data in the data disc according to the storage address of the business data.
In some embodiments, further comprising an analysis module configured to:
and analyzing the reason of the abnormal business data according to the maintenance data.
In some embodiments, the recording module 402 is further configured to:
recording maintenance data corresponding to the service data through the context of the IO stack;
and acquiring corresponding maintenance data in the context of the IO stack according to the KEY for maintaining the data.
In some embodiments, the recording module 402 is further configured to:
and recording path information and log information corresponding to the service data through the context of the IO stack.
The scheme provided by the invention enables the maintenance data and the service data to form a new data block and store the new data block on the back-end data disk, so that the maintenance data is stored adjacently along with the service data, can be directly read, and has high positioning efficiency. Meanwhile, data maintenance does not depend on an external storage space, and no system disk is worn. Meanwhile, the problem that log information cannot ensure whether the log falls after the data falls when the log is recorded asynchronously is avoided.
Based on the same inventive concept, according to another aspect of the present invention, as shown in fig. 3, an embodiment of the present invention further provides a computer apparatus 501, comprising:
at least one processor 520; and
the memory 510, the memory 510 stores a computer program 511 that is executable on the processor, and the processor 520 executes the program to perform any of the steps of the above-described maintenance data saving method.
Based on the same inventive concept, according to another aspect of the present invention, as shown in fig. 4, an embodiment of the present invention further provides a computer-readable storage medium 601, where the computer-readable storage medium 601 stores computer program instructions 610, and the computer program instructions 610, when executed by a processor, perform the steps of any of the above maintenance data saving methods.
Finally, it should be noted that, as will be understood by those skilled in the art, all or part of the processes of the methods of the above embodiments may be implemented by a computer program to instruct related hardware to implement the methods.
Further, it should be appreciated that the computer-readable storage media (e.g., memory) herein can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as software or hardware depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosed embodiments of the present invention.
The foregoing is an exemplary embodiment of the present disclosure, but it should be noted that various changes and modifications could be made herein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps and/or actions of the method claims in accordance with the disclosed embodiments described herein need not be performed in any particular order. Furthermore, although elements of the disclosed embodiments of the invention may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated.
It should be understood that, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly supports the exception. It should also be understood that "and/or" as used herein is meant to include any and all possible combinations of one or more of the associated listed items.
The numbers of the embodiments disclosed in the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments.
It will be understood by those skilled in the art that all or part of the steps of implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
Those of ordinary skill in the art will understand that: the discussion of any embodiment above is meant to be exemplary only, and is not intended to intimate that the scope of the disclosure, including the claims, of embodiments of the invention is limited to these examples; within the idea of an embodiment of the invention, also technical features in the above embodiment or in different embodiments may be combined and there are many other variations of the different aspects of the embodiments of the invention as described above, which are not provided in detail for the sake of brevity. Therefore, any omissions, modifications, substitutions, improvements, and the like that may be made without departing from the spirit and principles of the embodiments of the present invention are intended to be included within the scope of the embodiments of the present invention.
Claims (10)
1. A maintenance data storage method is characterized by comprising the following steps:
reorganizing the service data in response to receiving the service data;
acquiring maintenance data generated in the business data reorganization process, and recording the maintenance data in a preset data expansion area;
and in response to the completion of the reorganization of the service data, forming a new data block by the service data and the corresponding maintenance data recorded in the data expansion area, and storing the new data block in a data disk.
2. The method of claim 1, further comprising:
creating a data expansion area interface;
and setting configuration parameters of the data expansion area through the data expansion area interface.
3. The method of claim 2, further comprising:
and responding to the abnormal business data, and acquiring the business data and corresponding maintenance data in the data disc according to the storage address of the business data.
4. The method of claim 3, further comprising:
and analyzing the reason of the abnormal business data according to the maintenance data.
5. The method according to claim 1, wherein the obtaining of the maintenance data generated during the business data reorganization process and recording of the maintenance data in a preset data extension area further comprises:
recording maintenance data corresponding to the service data through the context of the IO stack;
and acquiring corresponding maintenance data in the context of the IO stack according to the KEY for maintaining the data.
6. The method of claim 5, wherein the recording of maintenance data corresponding to the business data via a context of an IO stack further comprises:
and recording path information and log information corresponding to the service data through the context of the IO stack.
7. A maintenance system for maintaining data, comprising:
a receiving module configured to reorganize service data in response to receiving the service data;
the recording module is configured to acquire maintenance data generated in the business data reorganization process and record the maintenance data to a preset data expansion area;
and the landing module is configured to respond to the completion of reorganization of the service data, and store the service data and the corresponding maintenance data recorded in the data expansion area into a data disk after forming a new data block.
8. The system of claim 7, further comprising a creation module configured to:
creating a data expansion area interface;
and setting configuration parameters of the data expansion area through the data expansion area interface.
9. A computer device, comprising:
at least one processor; and
memory storing a computer program operable on the processor, characterized in that the processor executes the program to perform the steps of the method according to any of claims 1-6.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, is adapted to carry out the steps of the method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010988138.2A CN112130770B (en) | 2020-09-18 | 2020-09-18 | Maintenance data storage method, system, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010988138.2A CN112130770B (en) | 2020-09-18 | 2020-09-18 | Maintenance data storage method, system, equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112130770A true CN112130770A (en) | 2020-12-25 |
| CN112130770B CN112130770B (en) | 2023-01-06 |
Family
ID=73841390
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010988138.2A Active CN112130770B (en) | 2020-09-18 | 2020-09-18 | Maintenance data storage method, system, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112130770B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110147360A (en) * | 2019-04-03 | 2019-08-20 | 深圳价值在线信息科技股份有限公司 | A kind of data integration method, device, storage medium and server |
| CN111124258A (en) * | 2018-10-31 | 2020-05-08 | 深信服科技股份有限公司 | Data storage method, device and equipment of full flash memory array and readable storage medium |
| CN111208946A (en) * | 2020-01-06 | 2020-05-29 | 北京同有飞骥科技股份有限公司 | Data persistence method and system supporting KB-level small file concurrent IO |
-
2020
- 2020-09-18 CN CN202010988138.2A patent/CN112130770B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111124258A (en) * | 2018-10-31 | 2020-05-08 | 深信服科技股份有限公司 | Data storage method, device and equipment of full flash memory array and readable storage medium |
| CN110147360A (en) * | 2019-04-03 | 2019-08-20 | 深圳价值在线信息科技股份有限公司 | A kind of data integration method, device, storage medium and server |
| CN111208946A (en) * | 2020-01-06 | 2020-05-29 | 北京同有飞骥科技股份有限公司 | Data persistence method and system supporting KB-level small file concurrent IO |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112130770B (en) | 2023-01-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109063027A (en) | A kind of method and device for business processing | |
| CN113111129A (en) | Data synchronization method, device, equipment and storage medium | |
| CN110888837B (en) | Object storage small file merging method and device | |
| CN105574217A (en) | Data synchronization method and device of distributed relational database | |
| CN102325078B (en) | Application identification method and device | |
| CN112130770B (en) | Maintenance data storage method, system, equipment and medium | |
| CN108536822A (en) | Data migration method, device, system and storage medium | |
| US20160253247A1 (en) | Method and device for restoring system file indexes | |
| CN112883124B (en) | Data processing method and device, computer equipment and storage medium | |
| CN110764949A (en) | Hard disk replacement method, hard disk replacement device, and storage medium | |
| CN107154960B (en) | Method and apparatus for determining service availability information for distributed storage systems | |
| CN113553193A (en) | Mirror image data auditing and distributing processing method and system | |
| CN110196785B (en) | Data backup management method and device and electronic equipment | |
| CN111813589A (en) | Distributed cluster fault positioning method, device, equipment and storage medium | |
| CN113806125B (en) | Method, device, equipment and readable medium for processing unloaded volume exception | |
| CN111405216B (en) | Configuration method, device and equipment and storage medium | |
| CN114826884A (en) | Method, device, equipment and readable medium for positioning communication fault of cross-equipment protocol | |
| CN115674275A (en) | Method and apparatus for internal testing of robotic systems | |
| CN113805799A (en) | Method, device and equipment for managing latest write records of RAID (redundant array of independent disk) array and readable medium | |
| CN115840737A (en) | Database-based separate log management method and system | |
| CN116303271A (en) | Synchronous audio/video file processing method, device and medium for business client | |
| CN115268777A (en) | Capacity expansion method and device for storage nodes | |
| CN118316795A (en) | Automatic checking method and device based on network high availability model | |
| CN112988694A (en) | Operation and maintenance method and device for batch management of network file systems by centralized management platform | |
| CN117493332A (en) | Data processing method, device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |