CN106844094B - File repair method and device - Google Patents
File repair method and device Download PDFInfo
- Publication number
- CN106844094B CN106844094B CN201611209586.8A CN201611209586A CN106844094B CN 106844094 B CN106844094 B CN 106844094B CN 201611209586 A CN201611209586 A CN 201611209586A CN 106844094 B CN106844094 B CN 106844094B
- Authority
- CN
- China
- Prior art keywords
- production system
- data block
- file
- repair
- bad block
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1435—Saving, restoring, recovering or retrying at system level using file system or storage system metadata
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
Abstract
A file repair method and device are used for solving the problem that file system service is interrupted when files in a file system are repaired in the prior art. The method comprises the following steps: the production system receives a first reading request sent by the terminal equipment, wherein the first reading request is used for requesting to read a specified file stored by the production system; the production system determines that at least one bad block exists in a specified file stored by the production system; the production system sends a second reading request to the backup system, wherein the backup system and the production system store the same files, and the second reading request is used for requesting to read at least one data block corresponding to the at least one bad block in the specified files stored by the backup system; and the production system repairs the specified file stored in the production system according to the at least one data block.
Description
Technical Field
The present invention relates to the field of storage technologies, and in particular, to a file repair method and apparatus.
Background
With the continuous development of the internet and information technology, more and more files are stored in file systems such as a local file system and a distributed file system. To fully utilize the files stored in the file system, the reliability of the files is guaranteed first. In addition to performing redundant backup on files, improving file reliability requires repairing damaged files.
In the prior art, manual operation is required by a user when files are repaired. For example, when the file system is redundantly backed up in a disaster recovery manner, the process of repairing the file may be as shown in fig. 1. The method comprises the steps that a terminal device sends a request for reading a specified file to a production system, and when the specified file cannot be read due to a bad block, the production system reports an error to the terminal device and the reading service is interrupted; after the terminal equipment receives the error report of the production system, a user manually switches to a disaster recovery backup system which stores the same file as the production system, the disaster recovery backup system returns a data block corresponding to a bad block to the terminal equipment, the terminal equipment sends the data block to the production system, and the production system can repair the specified file stored by the production system by using the data block. Therefore, the file repair process needs a user to manually switch the file system, and the repair process can cause service interruption of the file system.
In summary, there is a problem of file system service interruption when repairing a file in a file system in the prior art.
Disclosure of Invention
The embodiment of the invention provides a file repair method and device, which are used for solving the problem of file system service interruption when files in a file system are repaired in the prior art.
In a first aspect, an embodiment of the present invention provides a file repair method, where the method includes: the production system receives a first reading request sent by the terminal equipment, wherein the first reading request is used for requesting to read an appointed file stored by the production system; the production system sends a second reading request to a backup system after determining that at least one bad block exists in the specified file stored in the production system, wherein the backup system and the production system store the same file, and the second reading request is used for requesting to read at least one data block corresponding to the at least one bad block in the specified file stored in the backup system; after the production system receives the at least one data block sent by the backup system, the specified file stored by the production system can be repaired according to the at least one data block.
By adopting the scheme, after the production system determines that at least one bad block exists in the designated file stored in the production system, the designated file stored in the production system is repaired according to at least one data block which is sent by the backup system and corresponds to the at least one bad block, so that when the designated file stored in the production system needs to be repaired, the production system does not need to report an error to the terminal equipment and interrupt reading service as in the prior art, and then the designated file stored in the production system is repaired by manually switching to the disaster recovery system by a user. By adopting the file repair method provided by the first aspect, the production system can repair the designated file stored by the production system according to at least one data block sent by the backup system, and the repair process is realized by interaction of the production system and the backup system, and the terminal device does not participate in the repair process, so that the execution of the repair process cannot be sensed, and therefore, the read service interruption of the terminal device cannot be caused by the repair process, the efficiency of providing the file read-write service for the terminal device by the system is improved, and the service interruption of the system is avoided; in addition, the production system does not need manual participation of a user in the repair process of the specified file, the repair process is simplified, and user experience is improved.
In the first aspect, the backup system and the production system can store the same files by three ways, namely synchronous replication, asynchronous replication and backup. The specific process of repairing a specified file stored by a production system may vary with different implementations.
When a synchronous copying mode is adopted, the backup system is completely consistent with the files stored in the production system; when the asynchronous replication or backup mode is adopted, the backup system periodically synchronizes the files stored in the production system, and the data blocks contained in the backup system and the files stored in the production system are not necessarily completely consistent.
When the backup system synchronously copies the files stored by the production system, the production system repairs the specified files stored by the production system according to at least one data block, and the method can be realized through the following processes: after the production system receives the at least one data block, the at least one data block is written in the storage address of the at least one bad block, and then the repair process of the specified file stored in the production system can be completed.
Since the backup system synchronously copies the files stored in the production system, the backup system is completely consistent with the files stored in the production system. When the production system repairs the designated file stored in the production system, at least one data block sent by the backup system can be directly written in the storage address of at least one bad block. By adopting the scheme, when the backup system synchronously copies the files stored by the production system, a method for repairing the specified files stored by the production system is provided.
When the backup system asynchronously copies or backs up the files stored by the production system, the production system repairs the specified files stored by the production system according to at least one data block, and the method can be realized by the following processes: the production system can repair at least one bad block by using at least one data block based on whether the situation of the at least one bad block is recorded in the difference bitmap stored by the production system after receiving the at least one data block.
The production system repairs at least one bad block by using at least one data block based on whether the difference bitmap records the at least one bad block, and the method can be specifically realized in the following way: when at least one bad block is not recorded in the difference bitmap, the production system writes at least one data block under the storage address of the at least one bad block; or when at least one bad block is recorded in the difference bitmap, the production system modifies at least one data block according to the modification mode of at least one bad block stored in the production system; the production system writes the modified at least one data block under the memory address of the at least one bad block.
Since the backup system asynchronously copies or backs up files stored by the production system, the data blocks contained in the files stored by the backup system and the production system are not necessarily completely consistent. When the production system repairs the designated file stored in the production system, the repair is performed based on whether at least one bad block is recorded in the difference bitmap. By adopting the scheme, when the backup system asynchronously copies or backs up the files stored in the production system, the method for repairing the specified files stored in the production system is provided.
In addition, after the production system repairs the specified file stored by the production system according to the at least one data block, the production system can send the specified file stored by the production system to the terminal equipment; or before the production system receives the at least one data block sent by the backup system, the production system can also send other data blocks except the at least one bad block in the designated file to the terminal device; after the production system receives the at least one data block sent by the backup system, the production system sends the at least one data block to the terminal device.
By adopting the scheme, the production system not only can repair the designated file stored by the production system, but also can provide the service of reading the designated file for the terminal equipment through the process.
In a second aspect, an embodiment of the present invention provides a file repair method, where the method includes: the backup system receives a second reading request sent by the production system, the backup system and the production system store the same files, at least one bad block exists in the specified file stored by the production system, the second reading request is used for requesting to read at least one data block corresponding to the at least one bad block in the specified file stored by the backup system, and the at least one data block can be used for the production system to repair the specified file stored by the production system according to the at least one data block; the backup system sends the at least one data block to the production system.
By adopting the scheme, after the production system determines that at least one bad block exists in the designated file stored in the production system, the production system can repair the designated file stored in the production system according to at least one data block which is sent by the backup system and corresponds to the at least one bad block, so that when the designated file stored in the production system needs to be repaired, the production system does not need to report an error to the terminal equipment and interrupt reading service as in the prior art, and then the user manually switches to the disaster recovery system to repair the designated file stored in the production system. By adopting the file repair method provided by the second aspect, the production system can repair the designated file stored by the production system according to at least one data block sent by the backup system, and the repair process is realized by interaction of the production system and the backup system, and the terminal device does not participate in the repair process, so that the execution of the repair process cannot be sensed, and therefore, the read service interruption of the terminal device cannot be caused by the repair process, the efficiency of providing the file read-write service for the terminal device by the system is improved, and the service interruption of the system is avoided; in addition, the production system does not need manual participation of a user in the repair process of the specified file, the repair process is simplified, and user experience is improved.
In a third aspect, an embodiment of the present invention provides a file repair apparatus, where the apparatus includes a transceiver module, a storage module, and a repair module. The receiving and sending module is used for receiving a first reading request sent by the terminal equipment, and the first reading request is used for requesting to read the specified file; the storage module is used for storing the specified file; the repair module is used for determining that at least one bad block exists in the specified file stored by the storage module; the receiving and sending module is further used for sending a second reading request to the backup system and receiving at least one data block sent by the backup system, the backup system and the production system store the same file, and the second reading request is used for requesting to read at least one data block corresponding to at least one bad block in the specified file stored by the backup system; and the repair module is also used for repairing the specified file stored in the storage module according to the at least one data block sent by the backup system.
The file repair device provided in the third aspect may be regarded as a device in the production system in the embodiment of the present invention, and the device may be used to repair a specified file stored in the production system.
By adopting the scheme, after the repair module determines that at least one bad block exists in the designated file stored in the storage module, the designated file stored in the storage module is repaired according to at least one data block sent by the backup system, so that when the designated file stored in the storage module needs to be repaired, the error reporting to the terminal equipment and the reading service interruption are not needed as in the prior art, and then the user manually switches to the disaster recovery system to repair the designated file stored in the storage module. In the file repair apparatus provided in the third aspect, the repair module may repair the specified file stored in the storage module according to at least one data block sent by the backup system, and since the repair process is implemented by interaction between the file repair apparatus and the backup system provided in the third aspect, the terminal device does not participate in the repair process, and thus the execution of the repair process is not sensed, the repair process will not cause interruption of the reading service of the terminal device, thereby improving the efficiency of the file repair apparatus for providing the file reading and writing service for the terminal device, and avoiding interruption of the service of the system; in addition, the repairing module does not need manual participation of a user in the repairing process of the specified file, the repairing process is simplified, and user experience is improved.
In the third aspect, the backup system and the storage module can store the same files by three ways, namely synchronous replication, asynchronous replication and backup. The specific process of repairing the designated file stored by the storage module may vary with different implementations.
When a synchronous copying mode is adopted, the backup system is completely consistent with the files stored in the storage module; when an asynchronous copying or backup mode is adopted, the backup system periodically synchronizes the files stored in the storage module, and the data blocks contained in the backup system and the files stored in the storage module are not necessarily completely consistent.
When the backup system synchronously copies the file stored by the storage module, the repair module can write at least one data block received by the transceiver module under the storage address of at least one bad block when repairing the specified file stored by the storage module according to at least one data block.
Because the backup system synchronously copies the files stored in the storage module, the backup system is completely consistent with the files stored in the storage module. When the repair module repairs the specified file stored in the storage module, at least one data block sent by the backup system can be directly written in the storage address of at least one bad block. By adopting the scheme, when the backup system synchronously copies the files stored in the storage module, a method for repairing the specified files stored in the storage module is provided.
When the backup system asynchronously copies or backs up a file stored in the storage module, and the repair module repairs the specified file stored in the storage module according to at least one data block, the repair module may repair the at least one bad block using the at least one data block based on whether the at least one bad block is recorded in the difference bitmap stored in the storage module. The difference bitmap is used for recording the data blocks which are modified in the storage module and are not modified correspondingly by the backup system.
The repair module is specifically implemented by the following processes when repairing at least one bad block by using at least one data block based on whether at least one bad block is recorded in the difference bitmap: when at least one bad block is not recorded in the difference bitmap, writing at least one data block under the storage address of the at least one bad block; or when at least one bad block is recorded in the difference bitmap, modifying at least one data block according to the modification mode of the at least one bad block; and writing the modified at least one data block under the storage address of the at least one bad block. Wherein the modification mode of at least one bad block is stored in the storage module.
Since the backup system asynchronously copies or backs up the files stored in the storage module, the data blocks contained in the files stored in the backup system and the storage module are not necessarily completely consistent. When the repair module repairs the specified file stored in the storage module, the repair module needs to repair the specified file based on whether at least one bad block is recorded in the difference bitmap. By adopting the scheme, when the backup system asynchronously copies or backs up the file stored in the storage module, the method for repairing the specified file stored in the storage module is provided.
In addition, the transceiver module can also send the specified file stored by the storage module to the terminal device after the repair module repairs the specified file stored by the storage module according to the at least one data block; or the transceiver module may further send other data blocks except the at least one bad block in the designated file to the terminal device before receiving the at least one data block sent by the backup system, and then send the at least one data block to the terminal device after receiving the at least one data block sent by the backup system.
By adopting the scheme, the file repairing device can repair the specified file stored in the storage module through the repairing module, and the transceiver module of the file repairing device can also provide a service for reading the specified file for the terminal equipment.
In a fourth aspect, an embodiment of the present invention provides a file repair apparatus, where the apparatus includes a storage module and a transceiver module.
The storage module is used for storing the specified file; the transceiver module is used for receiving a second read request sent by the production system and sending at least one data block to the production system. The storage module and the production system store the same file, at least one bad block exists in the specified file stored by the production system, the second reading request is used for requesting to read at least one data block corresponding to the at least one bad block in the specified file stored by the storage module, and the at least one data block is used for repairing the specified file stored by the production system according to the at least one data block.
After the production system determines that at least one bad block exists in the designated file stored in the production system, the production system can repair the designated file stored in the production system according to at least one data block which is sent by the transceiver module and corresponds to the at least one bad block, so that when the designated file stored in the production system needs to be repaired, the production system does not need to report an error to the terminal equipment and interrupt reading service as in the prior art, and then the user manually switches to the disaster recovery system to repair the designated file stored in the production system. By adopting the file repair device provided by the fourth aspect, the production system can repair the designated file stored by the production system according to at least one data block sent by the transceiver module, and the repair process is realized by interaction of the production system and the file repair device provided by the fourth aspect, and the terminal device does not participate in the repair process, so that the execution of the repair process cannot be sensed, and therefore, the read service of the terminal device cannot be interrupted in the repair process, the efficiency of providing the file read-write service for the terminal device by the system is improved, and the service interruption of the system is avoided; in addition, the production system does not need manual participation of a user in the repair process of the specified file, the repair process is simplified, and user experience is improved.
In a fifth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer-executable instruction is stored, and when at least one processor of a computing node executes the computer-executable instruction, the computing node executes a method provided by the first aspect or various possible designs of the first aspect, or executes a method provided by the second aspect or various possible designs of the second aspect.
In a sixth aspect, an embodiment of the present invention provides a computer program product, where the computer program product includes computer executable instructions, and the computer executable instructions are stored in a computer readable storage medium. The computer executable instructions may be read by at least one processor of the computing node from a computer readable storage medium, the computer executable instructions being executable by the at least one processor to cause the computing node to implement the method provided by the first aspect or the various possible designs of the first aspect described above, or to implement the method provided by the second aspect or the various possible designs of the second aspect described above.
Drawings
FIG. 1 is a schematic flow diagram of a process for file repair provided by the prior art;
FIG. 2 is a flowchart illustrating a first file writing process according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating a second file writing process according to an embodiment of the present invention;
FIG. 4 is a flowchart illustrating a third file writing process according to an embodiment of the present invention;
fig. 5 is a schematic flowchart of a file repair method according to an embodiment of the present invention;
FIG. 6 is a schematic structural diagram of a first file recovery apparatus according to an embodiment of the present invention;
FIG. 7 is a schematic structural diagram of a second file recovery apparatus according to an embodiment of the present invention;
FIG. 8 is a schematic structural diagram of a third file recovery apparatus according to an embodiment of the present invention;
FIG. 9 is a schematic structural diagram of a fourth file recovery apparatus according to an embodiment of the present invention;
fig. 10 is a schematic structural diagram of a file system according to an embodiment of the present invention.
Detailed Description
For a better understanding of the above-described objects, aspects and advantages of embodiments of the present invention, detailed descriptions are provided below. The detailed description sets forth various embodiments of the devices and/or methods via the use of diagrams and/or examples of block diagrams, flowcharts, and the like. In these block diagrams, flowcharts, and/or examples, one or more functions and/or operations are included. Those skilled in the art will understand that: the various functions and/or operations within these block diagrams, flowcharts or examples can be implemented, individually and collectively, by a wide variety of hardware, software, firmware, or any combination of hardware, software and firmware.
The embodiment of the invention relates to repairing a specified file, wherein the specified file is a file repaired by using the file repairing method provided by the embodiment of the invention, the file type of the specified file is not limited in the embodiment of the invention, and as long as a certain file in a production system can be repaired by using the file repairing method provided by the embodiment of the invention, the file can be regarded as the specified file. Two file systems, a production system and a backup system, are involved in repairing a specified file.
The production system is used for providing file read-write service for the terminal equipment, and the backup system and the production system store the same files. That is, when the specified file stored in the production system is not damaged, the production system can provide a file read-write service for the terminal device; when part of data blocks in the specified file stored in the production system are damaged, the production system can repair the specified file stored in the production system according to the specified file stored in the backup system, and after the repair is finished, the production system can continue to provide file read-write service for the terminal equipment; when the files stored in the production system cannot be repaired, the user can switch the backup system into a file system providing file read-write service through the terminal equipment.
The backup system and the production system store the same files and can be realized by the following three ways:
the first mode is as follows: synchronous replication
The backup system synchronously replicating files stored by the production system may be implemented by a file writing process as shown in fig. 2. In fig. 2, it is assumed that file 1 to be written into the production system by the terminal device contains five data blocks, A, B, C, D and E, and when the terminal device writes file 1 into the production system, it needs to write A, B, C, D and E five data blocks into the production system, respectively. Taking the example of writing the data block a, the terminal device writes the data block a in the production system first, then the production system sends an instruction for writing the data block a to the backup system, after the backup system successfully writes the data block a, the backup system sends an indication message of successful writing to the production system, and after the production system confirms that the backup system has successfully written the data block a, the production system sends an indication message of successful writing to the terminal device. The writing process of data blocks B, C, D and E is the same as the writing process of data block A and will not be described again. When both data blocks A, B, C, D and E complete the write process, the write process for File 1 is complete.
In addition, when the backup system synchronously copies the files stored in the production system, if the terminal device needs to modify the data blocks stored in the production system, it also needs to modify the corresponding data blocks stored in the backup system at the same time.
The second mode is as follows: asynchronous replication
The asynchronous copying of files stored by the production system by the backup system may be accomplished by a file write process as shown in fig. 3. In fig. 3, a synchronization period needs to be configured between the backup system and the production system, and when the synchronization period does not arrive, for a data block written to the production system by the terminal device, the production system only needs to record the data block in a difference bitmap stored by the production system, and does not need to write the data block into the backup system; when the synchronization period comes, the production system writes the data blocks recorded in the difference bitmap into the backup system. For example, file 1 to be written by the terminal device into the production system contains A, B, C, D and E, and it is assumed that at the end of the last synchronization period, A, B, C three data blocks have been written in both the production system and the backup system. When the synchronous period does not arrive, the terminal equipment writes a data block D into the production system, the production system records the data block D in the difference bitmap, then the terminal equipment writes a data block E into the production system, and the production system records the data block E in the difference bitmap; when the synchronization period comes, the production system writes the data blocks D and E recorded in the difference bitmap into the backup system.
In addition, when the backup system asynchronously copies the file stored in the production system, if the terminal device wants to modify the data block stored in the production system, the production system needs to record the modified data block in the difference bitmap when the synchronization period does not come. When the synchronization period comes, the production system writes the data blocks recorded in the difference bitmap into the backup system.
In particular, when a backup system synchronously copies or asynchronously copies files stored by a production system, the backup system may also be referred to as a disaster backup system. The production system can repair the files stored in the disaster recovery backup system according to the files stored in the disaster recovery backup system, and when the production system stops working due to accidents (such as fire, earthquake and the like), a user can switch the disaster recovery backup system into a file system providing file read-write service through the terminal device, and the disaster recovery backup system can replace the production system to continue to provide the file read-write service for the terminal device.
The third mode is as follows: backup of
Backup system backup of files stored by the production system may be accomplished by a file writing process as shown in fig. 4. Similar to the process in which the backup system asynchronously replicates files in the production system, the process in which files stored in the production system are backed up in the backup system may be implemented by periodically writing data blocks recorded in the difference bitmap to the backup system. Unlike asynchronous replication processes, multiple copies may be backed up in a backup system for a file. For example, file 1 to be written by the terminal device into the production system contains five data blocks A, B, C, D and E, and assuming that three data blocks A, B, C have been written in both the production system and the backup system at the end of the last synchronization period, copy 1 of file 1 in the backup system consists of data block A, B, C. When the synchronous period does not arrive, the terminal equipment writes a data block D into the production system, the production system records the data block D in the difference bitmap, then the terminal equipment writes a data block E into the production system, and the production system records the data block E in the difference bitmap; when the synchronization cycle arrives, the production system backs up the data block D and the data block E recorded in the difference bitmap to the backup system, and the copy 2 of the file 1 in the backup system is composed of the data block A, B, C, D, E. Wherein copy 2 is the latest version of the copy.
In addition, when the backup system backs up a file stored in the production system, if the terminal device wants to modify a data block in the production system, the production system needs to record the modified data block in the difference bitmap when the synchronization period does not come. When the synchronization period comes, the production system writes the data blocks recorded in the difference bitmap into the backup system to form another copy.
In the three modes, when a synchronous copying mode is adopted, the backup system is completely consistent with the files stored in the production system; when the asynchronous replication or backup mode is adopted, the backup system periodically synchronizes the files stored in the production system, and the data blocks contained in the backup system and the files stored in the production system are not necessarily completely consistent. The specific meaning that the data blocks contained in the files stored in the backup system and the production system are not necessarily completely consistent is that: the backup system is the same as the file stored in the production system, but for the same file, when the synchronization period does not come, the production system may modify some data blocks in the file and record the modified data blocks in the difference bitmap, but since the modification occurs before the synchronization period comes, the data blocks in the file in the backup system are not modified correspondingly.
In the prior art, when files stored in a production system are repaired, manual operation needs to be performed by a user. When the production system determines that some data blocks in the file stored by the production system are damaged, the production system reports an error to the terminal equipment and the reading service is interrupted; after the terminal equipment receives the error report of the production system, a user manually switches to the backup system, the backup system returns the data block corresponding to the bad block to the terminal equipment, the terminal equipment sends the data block to the production system, and the production system can repair the damaged data block in the corresponding file by using the data block. The file repair process requires a user to manually switch the file system, and the repair process can cause the production system to stop providing the file read-write service for the terminal device, i.e., cause the service interruption of the file system.
In order to solve the problem of file system service interruption when a file in a file system is repaired in the prior art, an embodiment of the present invention provides a file repair method. As shown in fig. 5, the method includes the steps of:
s501: the production system receives a first reading request sent by the terminal equipment.
The first read request is used for requesting to read a specified file stored by the production system.
In the embodiment of the present invention, the terminal device includes, but is not limited to, a smart phone, a smart watch, a tablet computer, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a personal computer, a handheld computer, and a personal digital assistant.
S502: the production system determines that at least one bad block exists in a specified file stored by the production system.
S503: the production system sends a second read request to the backup system.
The backup system and the production system store the same files, and the second read request is used for requesting to read at least one data block corresponding to at least one bad block in the specified file stored in the backup system.
Wherein, at least one data block is a data block corresponding to at least one bad block. Assuming that file 1 stored in the production system contains A, B, C, D, E five data blocks, where data block C and data block D are two bad blocks, file 1 stored in the backup system also contains A, B, C, D, E five data blocks, and the two data blocks that are in one-to-one correspondence with at least the two bad blocks are data block C and data block D stored in the backup system.
S504: the backup system sends the at least one data block to the production system.
S505: and the production system repairs the specified file stored in the production system according to the at least one data block.
In the embodiment of the present invention, the storage of the same file in the backup system and the production system can be realized by the above three ways, i.e., synchronous copy, asynchronous copy, and backup, which are not described herein again.
Optionally, after the production system performs S505 to repair the specific file stored in the production system, the repaired specific file may be sent to the terminal device, so that after the repair of the specific file is completed, the production system provides a service for reading the specific file for the terminal device.
Optionally, before executing S504 to receive at least one data block, the production system may further send other data blocks in the specified file except for the at least one bad block to the terminal device; after the step S504 is executed to receive the at least one data block, the at least one data block may also be sent to the terminal device, so that the production system may repair the specified file and provide a file read-write service for the terminal device.
When the backup system and the production system store the same files, the three modes are realized in different ways, and the specific implementation modes for repairing the specified files stored in the production system are different.
When the backup system synchronously copies the file stored by the production system, in S505, the production system repairs the specified file stored by the production system according to at least one data block, and the method may be implemented as follows: after the production system receives the at least one data block, the at least one data block is written in the storage address of the at least one bad block, and then the repair process of the specified file stored in the production system can be completed.
Since the backup system synchronously copies the files stored in the production system, the backup system is completely consistent with the files stored in the production system. When the production system repairs the designated file stored in the production system, at least one data block sent by the backup system can be directly written in the storage address of at least one bad block. By adopting the scheme, when the backup system synchronously copies the files stored by the production system, a method for repairing the specified files stored by the production system is provided.
When the backup system asynchronously copies or backs up the file stored in the production system, in S505, the production system repairs the specified file stored in the production system according to at least one data block sent by the backup system, which may be implemented as follows: the production system can repair at least one bad block by using at least one data block based on whether the situation of the at least one bad block is recorded in the difference bitmap stored by the production system after receiving the at least one data block. The difference bitmap is used for recording data blocks which are modified in the production system and are not modified correspondingly by the backup system.
Since the backup system asynchronously copies or backs up files stored by the production system, the data blocks contained in the files stored by the backup system and the production system are not necessarily completely consistent. When the production system repairs the designated file stored in the production system, the repair is performed based on whether at least one bad block is recorded in the difference bitmap. By adopting the scheme, when the backup system asynchronously copies or backs up the files stored in the production system, the method for repairing the specified files stored in the production system is provided.
Specifically, when the production system repairs the designated file based on the fact whether at least one bad block is recorded in the difference bitmap, there are two cases:
first case
When at least one bad block is not recorded in the difference bitmap, the production system writes at least one data block under the storage address of the at least one bad block, and then the repair process of the specified file stored in the production system can be completed;
second case
When at least one bad block is recorded in the difference bitmap, the production system correspondingly modifies at least one data block according to a modification mode of modifying the at least one bad block stored in the production system, and writes the modified at least one data block under the storage address of the at least one bad block after modification is completed.
When the backup system asynchronously copies or backs up a designated file stored in the production system, the backup system synchronizes data blocks with the production system only when a synchronization period comes, so that a difference bitmap needs to be stored in the production system to record which data blocks are data blocks which are modified in the production system and data blocks which are not modified in the backup system. In addition, the production system can also store the modification mode of the data blocks recorded in the difference bitmap, so that when the production system repairs the designated file stored in the production system, the production system can correspondingly modify at least one data block according to the modification mode of at least one bad block.
It should be noted that, when a partial data block in at least one bad block is recorded in the differential bitmap, after receiving the at least one data block, the production system may modify the partial data block according to a modification manner of the partial data block stored in the production system, use the at least one data block of the modified partial data block as the modified at least one data block, and write the modified at least one data block in a storage address of the at least one bad block, that is, complete a repair process for the specified file stored in the production system.
For example, if the specified file stored by the production system includes four bad blocks A, B, C, D, the four data blocks corresponding to the four bad blocks are A, B, C, D four data blocks in the specified file stored by the backup system, that is, after the production system sends the second read request, the backup system sends A, B, C, D four data blocks to the production system. If two data blocks, namely a and B, are recorded in the difference bitmap, that is, a and B are modified in the production system and are not modified correspondingly in the backup system, after the production system receives A, B, C, D data blocks sent by the backup system, the production system can modify a data block a and a data block B of A, B, C, D four data blocks sent by the backup system according to the modification mode of a and B stored by the production system, and use the four data blocks with the modified a and B as the modified four data blocks, and then write the modified four data blocks in the storage addresses of the four bad blocks.
With the file repair method shown in fig. 5, after the production system determines that at least one bad block exists in the designated file stored in the production system, the designated file stored in the production system is repaired according to at least one data block corresponding to the at least one bad block, which is sent by the backup system, so that when the designated file stored in the production system needs to be repaired, it is not necessary to report an error to the terminal device by the production system and interrupt the reading service, and then the designated file stored in the production system is repaired by manually switching to the disaster recovery system by the user, as in the prior art. By adopting the file repair method provided by the embodiment of the invention, the production system can repair the designated file stored by the production system according to at least one data block sent by the backup system, and the repair process is realized by the interaction of the production system and the backup system, and the terminal equipment does not participate in the repair process, so that the execution of the repair process cannot be sensed, and therefore, the read service interruption of the terminal equipment cannot be caused by the repair process, the efficiency of providing the file read-write service for the terminal equipment by the system is improved, and the service interruption of the system is avoided; in addition, the production system does not need manual participation of a user in the repair process of the specified file, the repair process is simplified, and user experience is improved.
An embodiment of the present invention provides a file repair apparatus, which may be used to execute operations executed by a production system in the file repair method shown in fig. 5. As shown in fig. 6, the apparatus 600 includes a transceiver module 601, a storage module 602, and a repair module 603.
The transceiver module 601 is configured to receive a first read request sent by a terminal device, where the first read request is used to request to read an appointed file; a storage module 602, configured to store a specified file; a repairing module 603, configured to determine that at least one bad block exists in the specified file stored in the storage module 602; the transceiver module 601 is further configured to send a second read request to the backup system, and receive at least one data block sent by the backup system, where the backup system and the production system store the same file, and the second read request is used to request to read at least one data block corresponding to at least one bad block in the specified file stored by the backup system; the repairing module 603 is further configured to repair the specified file stored in the storage module 602 according to the at least one data block sent by the backup system.
Optionally, the backup system and the storage module 602 store the same file, specifically: the backup system synchronously copies files stored by the storage module 602.
Optionally, when repairing the specified file stored in the storage module 602 according to at least one data block sent by the backup system, the repairing module 603 is specifically configured to: and writing at least one data block under the storage address of at least one bad block.
Optionally, the backup system and the storage module 602 store the same file, specifically: the backup system asynchronously copies or backs up files stored by the storage module 602.
Optionally, the storage module 602 is further configured to: storing a difference bitmap, wherein the difference bitmap is used for recording data blocks which are modified in the storage module 602 and are not modified correspondingly by the backup system; when repairing the specified file stored in the storage module 602 according to at least one data block sent by the backup system, the repairing module 603 is specifically configured to: and repairing the at least one bad block by using the at least one data block based on whether the at least one bad block is recorded in the difference bitmap.
Optionally, the storage module 602 is further configured to store a modification manner of the at least one bad block; the repairing module 603 is specifically configured to, when repairing at least one bad block by using at least one data block based on whether the difference bitmap records the at least one bad block: when at least one bad block is not recorded in the difference bitmap, writing at least one data block under the storage address of the at least one bad block; or when at least one bad block is recorded in the difference bitmap, modifying at least one data block according to the modification mode of the at least one bad block; and writing the modified at least one data block under the storage address of the at least one bad block.
Optionally, the transceiver module 601 is further configured to send the specified file stored in the storage module 602 to the terminal device after the repair module 603 repairs the specified file stored in the storage module 602 according to the at least one data block sent by the backup system; alternatively, the transceiver module 601 sends other data blocks except for the at least one bad block in the designated file to the terminal device before receiving the at least one data block sent by the backup system, and sends the at least one data block to the terminal device after receiving the at least one data block sent by the backup system.
In the file repair apparatus 600, after determining that at least one bad block exists in the designated file stored in the storage module 602, the repair module 603 repairs the designated file stored in the storage module 602 according to at least one data block sent by the backup system, so when the designated file stored in the storage module 602 needs to be repaired, it is not necessary to report an error to a terminal device and interrupt a reading service as in the prior art, and then manually switch to the disaster recovery system by a user to repair the designated file stored in the storage module 602. In the file repair apparatus 600, the repair module 603 may repair the specified file stored in the storage module 602 according to at least one data block sent by the backup system, and since the repair process is implemented by interaction between the file repair apparatus 600 and the backup system, and the terminal device does not participate in the repair process, the execution of the repair process is not sensed, and therefore, the repair process does not cause interruption of the reading service of the terminal device, thereby improving the efficiency of the file repair apparatus for providing the file reading and writing service for the terminal device, and avoiding service interruption of the system; in addition, the repair module 603 does not need manual participation of a user in the repair process of the specified file, so that the repair process is simplified, and the user experience is improved.
It should be noted that the file repair apparatus 600 provided by the embodiment of the present invention may be used to execute operations executed by the production system in the file repair method shown in fig. 5, and the implementation manner that is not explained and described in detail by the file repair apparatus 600 may refer to the relevant description in the file repair method shown in fig. 5.
It should be noted that, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.
Based on the above embodiments, an embodiment of the present invention further provides a file repair apparatus, which may execute the method provided in the embodiment corresponding to fig. 5, and may be the same as the file repair apparatus 600 shown in fig. 6.
Referring to fig. 7, the file repair apparatus 700 includes at least one processor 701, a memory 702, and a communication interface 703; the at least one processor 701, the memory 702, and the communication interface 703 are all connected by a bus 704;
the memory 702 for storing computer-executable instructions;
the at least one processor 701 is configured to execute the computer-executable instructions stored in the memory 702, so that the file repair apparatus 700 performs the file repair method provided in the foregoing embodiment by performing data interaction with other devices (e.g., a terminal device and a backup system) through the communication interface 703.
At least one processor 701, which may include processors 701 of different types, or processors 701 of the same type; the processor 701 may be any of the following: a Central Processing Unit (CPU), an ARM processor, a Field Programmable Gate Array (FPGA), a special processor, and other devices with computing and Processing capabilities. In an alternative embodiment, the at least one processor 701 may also be integrated as a many-core processor.
The memory 702 may be any one or any combination of the following: random Access Memory (RAM), Read Only Memory (ROM), non-volatile Memory (NVM), Solid State Drive (SSD), mechanical hard disk, magnetic disk, and magnetic disk array.
The communication interface 703 is used for data interaction between the file repair apparatus 700 and other devices (e.g., a terminal device and a backup system). Communication interface 703 may be any one or any combination of the following: a network interface (e.g., an ethernet interface), a wireless network card, etc. having a network access function.
The bus 704 may include an address bus, a data bus, a control bus, etc., which is represented by a thick line in FIG. 7 for ease of illustration. Bus 704 may be any one or any combination of the following: an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended EISA (EISA) bus, and other wired data transmission devices.
An embodiment of the present invention provides a file repair apparatus, which may be used to execute operations executed by a backup system in the file repair method shown in fig. 5. As shown in fig. 8, the apparatus 800 includes a storage module 801 and a transceiver module 802.
A storage module 801, configured to store a specified file;
the transceiver module 802 is configured to receive a second read request sent by the production system, and send at least one data block to the production system. The storage module 801 and the production system store the same file, at least one bad block exists in the specified file stored by the production system, the second read request is used for requesting to read at least one data block corresponding to the at least one bad block in the specified file stored by the storage module 801, and the at least one data block is used for the production system to repair the specified file stored by the production system according to the at least one data block.
After the production system determines that at least one bad block exists in the designated file stored in the production system, the production system can repair the designated file stored in the production system according to at least one data block which is sent by the transceiver module 802 and corresponds to the at least one bad block, so that when the designated file stored in the production system needs to be repaired, the production system does not need to report an error to the terminal device and interrupt reading service as in the prior art, and then the user manually switches to the disaster recovery system to repair the designated file stored in the production system. By adopting the file repair device provided in the fourth aspect, the production system can repair the designated file stored in the production system according to at least one data block sent by the transceiver module 802, and since the repair process is realized by interaction between the production system and the file repair device 800, the terminal device does not participate in the repair process, and the execution of the repair process cannot be sensed, the repair process cannot cause interruption of reading service, so that the efficiency of providing file reading and writing service for the terminal device by the system is improved, and the service interruption of the system is avoided; in addition, the production system does not need manual participation of a user in the repair process of the specified file, the repair process is simplified, and user experience is improved.
It should be noted that the file repair apparatus 800 provided by the embodiment of the present invention may be used to perform operations performed by the backup system in the file repair method shown in fig. 5, and the implementation manner that is not explained and described in detail by the file repair apparatus 800 may refer to the relevant description in the file repair method shown in fig. 5.
Based on the above embodiments, an embodiment of the present invention further provides a file repair apparatus, and the file repair apparatus may execute the method provided in the embodiment corresponding to fig. 5, and may be the same as the file repair apparatus 800 shown in fig. 8.
Referring to fig. 9, the file repair apparatus 900 includes at least one processor 901, a memory 902, and a communication interface 903; the at least one processor 901, the memory 902 and the communication interface 903 are all connected by a bus 904;
the memory 902 is used for storing computer execution instructions;
the at least one processor 901 is configured to execute the computer-executable instructions stored in the memory 902, so that the file repair apparatus 900 performs the file repair method provided by the foregoing embodiments by performing data interaction with other devices (e.g., a terminal device and a production system) through the communication interface 903.
At least one processor 901, which may include processors 901 of different types, or which may include processors 901 of the same type; the processor 901 may be any one of a CPU, an ARM processor, an FPGA, a dedicated processor, and the like having a computing processing capability. In an alternative embodiment, the at least one processor 901 may also be integrated as a many-core processor.
The memory 902 may be any one or any combination of the following: storage media such as RAM, ROM, NVM, SSD, mechanical hard disk, magnetic disk array, and the like.
The communication interface 903 is used for data interaction between the file repair apparatus 900 and other devices (e.g., a terminal device and a production system). The communication interface 903 may be any one or any combination of the following: a network interface (e.g., an ethernet interface), a wireless network card, etc. having a network access function.
The bus 904 may include an address bus, a data bus, a control bus, etc., which is represented by a thick line in fig. 9 for ease of illustration. Bus 904 may be any one or any combination of the following: ISA bus, PCI bus, EISA bus and other wired data transmission devices.
The embodiment of the invention also provides a file system. As shown in fig. 10, the file system 1000 includes the file repair apparatus 600 shown in fig. 6 and the file repair apparatus 800 shown in fig. 8, and the file repair apparatus 600 and the file repair apparatus 800 in the file system 1000 may interact with each other to complete the file repair method shown in fig. 5.
In summary, with the file repair method and apparatus provided in the embodiments of the present invention, the production system can repair the designated file stored in the production system according to at least one data block sent by the backup system, and since the repair process is implemented by interaction between the production system and the backup system, the terminal device does not participate in the repair process, and thus cannot sense execution of the repair process, the repair process does not cause interruption of a reading service of the terminal device, thereby improving efficiency of providing a file reading and writing service for the terminal device by the system, and avoiding service interruption of the system; in addition, the production system does not need manual participation of a user in the repair process of the specified file, the repair process is simplified, and user experience is improved.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present invention without departing from the spirit or scope of the embodiments of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.
Claims (6)
1. A method for file repair, comprising:
a production system receives a first reading request sent by terminal equipment, wherein the first reading request is used for requesting to read an appointed file stored by the production system;
the production system determines that at least one bad block exists in a specified file stored by the production system;
the production system sends a second read request to a backup system, the backup system asynchronously copies or backs up the files stored by the production system, and the second read request is used for requesting to read at least one data block corresponding to the at least one bad block in the designated files stored by the backup system;
the production system receives the at least one data block sent by the backup system;
the production system repairs the specified file stored in the production system according to the at least one data block;
before the production system receives the at least one data block sent by the backup system, the method further includes: the production system sends other data blocks except the at least one bad block in the specified file to the terminal equipment; after the production system receives the at least one data block sent by the backup system, the method further comprises: and the production system sends the at least one data block to the terminal equipment.
2. The method of claim 1, wherein the repair of the specified file stored by the production system from the at least one data block by the production system comprises:
the production system repairs the at least one bad block by using the at least one data block based on whether the at least one bad block is recorded in a difference bitmap stored in the production system, wherein the difference bitmap is used for recording the data blocks which are modified in the production system and are not modified correspondingly in the backup system.
3. The method of claim 2, wherein the producing system repairs the at least one bad block using the at least one data block based on whether the at least one bad block is recorded in the difference bitmap, comprising:
when the at least one bad block is not recorded in the difference bitmap, the production system writes the at least one data block under the storage address of the at least one bad block; or
When the difference bitmap records the at least one bad block, the production system modifies the at least one data block according to a modification mode of the at least one bad block stored in the production system; and the production system writes the modified at least one data block under the storage address of the at least one bad block.
4. A file repair device, comprising:
the terminal equipment comprises a transceiving module, a receiving module and a sending module, wherein the transceiving module is used for receiving a first reading request sent by the terminal equipment, and the first reading request is used for requesting to read an appointed file;
the storage module is used for storing the specified file;
the repair module is used for determining that at least one bad block exists in the specified file stored by the storage module;
the transceiver module is further configured to send a second read request to a backup system, where the backup system asynchronously copies or backs up files stored in the production system, and the second read request is used to request to read at least one data block corresponding to the at least one bad block in a specified file stored in the backup system; receiving the at least one data block sent by the backup system;
the restoration module is further configured to restore the specified file stored in the storage module according to the at least one data block, and the backup system and the storage module store the same file;
the transceiver module is further configured to: before receiving the at least one data block sent by the backup system, sending other data blocks except the at least one bad block in the designated file to the terminal equipment; and after receiving the at least one data block sent by the backup system, sending the at least one data block to the terminal equipment.
5. The apparatus of claim 4, wherein the storage module is further to: storing a difference bitmap, wherein the difference bitmap is used for recording data blocks which are modified in the storage module and are not modified correspondingly in the backup system;
when the repair module repairs the specified file stored in the storage module according to the at least one data block, the repair module is specifically configured to: and repairing the at least one bad block by using the at least one data block based on whether the at least one bad block is recorded in the difference bitmap.
6. The apparatus of claim 5, wherein the storage module is further to: storing the modification mode of the at least one bad block;
when the repair module uses the at least one data block to repair the at least one bad block based on whether the at least one bad block is recorded in the difference bitmap, the repair module is specifically configured to: when the at least one bad block is not recorded in the difference bitmap, writing the at least one data block under the storage address of the at least one bad block; or
When the at least one bad block is recorded in the difference bitmap, modifying the at least one data block according to the modification mode of the at least one bad block; and writing the modified at least one data block under the storage address of the at least one bad block.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611209586.8A CN106844094B (en) | 2016-12-23 | 2016-12-23 | File repair method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611209586.8A CN106844094B (en) | 2016-12-23 | 2016-12-23 | File repair method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106844094A CN106844094A (en) | 2017-06-13 |
| CN106844094B true CN106844094B (en) | 2021-01-29 |
Family
ID=59136685
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611209586.8A Active CN106844094B (en) | 2016-12-23 | 2016-12-23 | File repair method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106844094B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113316770B (en) * | 2019-01-25 | 2023-08-22 | 华为技术有限公司 | Data restoration method and device |
| CN117667468A (en) * | 2022-08-24 | 2024-03-08 | 成都华为技术有限公司 | Data restoration method and storage device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1801107A (en) * | 2006-01-12 | 2006-07-12 | 上海洲信信息技术有限公司 | Data recovery method |
| CN101777013A (en) * | 2009-01-12 | 2010-07-14 | 成都市华为赛门铁克科技有限公司 | Solid state disk and data read-write method |
| CN102880530A (en) * | 2012-09-25 | 2013-01-16 | 东莞宇龙通信科技有限公司 | Terminal and terminal backup and recovery method |
| CN103617097A (en) * | 2013-11-19 | 2014-03-05 | 华为技术有限公司 | File recovery method and file recovery device |
| CN103873503A (en) * | 2012-12-12 | 2014-06-18 | 鸿富锦精密工业（深圳）有限公司 | Data block backup system and method |
-
2016
- 2016-12-23 CN CN201611209586.8A patent/CN106844094B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1801107A (en) * | 2006-01-12 | 2006-07-12 | 上海洲信信息技术有限公司 | Data recovery method |
| CN101777013A (en) * | 2009-01-12 | 2010-07-14 | 成都市华为赛门铁克科技有限公司 | Solid state disk and data read-write method |
| CN102880530A (en) * | 2012-09-25 | 2013-01-16 | 东莞宇龙通信科技有限公司 | Terminal and terminal backup and recovery method |
| CN103873503A (en) * | 2012-12-12 | 2014-06-18 | 鸿富锦精密工业（深圳）有限公司 | Data block backup system and method |
| CN103617097A (en) * | 2013-11-19 | 2014-03-05 | 华为技术有限公司 | File recovery method and file recovery device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106844094A (en) | 2017-06-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106201338B (en) | Date storage method and device | |
| CN102306115B (en) | Asynchronous remote copying method, system and equipment | |
| CN103548011A (en) | Asynchronous replication in a distributed storage environment | |
| US10365978B1 (en) | Synchronization of snapshots in a distributed consistency group | |
| CN102929750A (en) | Nonvolatile media dirty region tracking | |
| CN103164523A (en) | Inspection method, device and system of data consistency inspection | |
| CN110058791B (en) | Storage system and corresponding method and computer readable medium | |
| US20170168756A1 (en) | Storage transactions | |
| CN102929748A (en) | Method and device for data backup | |
| CN110825562B (en) | Data backup method, device, system and storage medium | |
| CN106844094B (en) | File repair method and device | |
| US8015375B1 (en) | Methods, systems, and computer program products for parallel processing and saving tracking information for multiple write requests in a data replication environment including multiple storage devices | |
| WO2018113322A1 (en) | Method and device for reading data | |
| CN104461784A (en) | Single progress bitmap based clone copying method and system | |
| CN104298609B (en) | Data copying method and device | |
| CN102629223A (en) | Method and device for data recovery | |
| CN109165117B (en) | Data processing method and system | |
| CN104484354A (en) | Snapshot method for guaranteeing data consistency and storage equipment | |
| TW201022930A (en) | Method to improve recovery time of mirrored disks when read stability is in doubt | |
| US20160077743A1 (en) | Shared-bandwidth multiple target remote copy | |
| GB2581947A (en) | Management of data written via a bus interface to a storage controller during remote copy operations | |
| CN101814042B (en) | Data asynchronous replication method and device thereof | |
| CN115509806A (en) | Real-time protection asynchronous remote copying method, device and equipment based on ROW | |
| CN110704239B (en) | Data copying method and device and electronic equipment | |
| CN104090729B (en) | The method and device of mirror image synchronization is repaired by business write operation |
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 |