TWI738451B - Data backup method and storage device - Google Patents

Abstract

The present application relates to a data backup method comprising steps of providing a storage device, which includes a storage module having a first mapping table, a second mapping table and a storage block, writing data to a first logical block address of the first mapping table, writing data to a physical block address of the storage block through the first mapping table, writing data to another physical block address of the storage block through a second logical block address of the second mapping table, executing a backup command, and utilizing the second mapping table and the data stored in the another physical block address as backup data. Therefore, after executing the backup command, the backup operation is instantly completed, thereby implementing the function of rapid backup.

Description

Data backup method and storage device

This case is about a backup method, especially a data backup method and storage device that can realize fast backup and incremental backup.

In recent years, Solid-State Drive (SSD) has become the mainstream of storage devices. Since most of the data stored in the storage device is important, various forms of backup are generally performed on the data stored in the storage device. Among them, the software layer backup through backup and restoration software is the simplest implementation method.

Generally speaking, this kind of backup method is based on the operating system, using backup and restoration software built into the system or provided by a third party to perform software-level backup. This kind of backup method includes the entire disk data backup or partial data backup, but because its structure is at the software layer, various operating systems and software licenses need to be considered, and the backup data is exposed in the readable and writable data hidden area.

In other words, traditional backup methods need to rely on specific software or operating systems, and write a large amount of data in response to the entire operating system and software environment, and cannot effectively separate the data in use from the backup data. There are many limitations, but there are also problems such as time-consuming and poor efficiency.

Therefore, how to develop a data backup method and storage device that can effectively solve the aforementioned problems and shortcomings of the prior art is actually a problem to be solved at present.

The main purpose of this case is to provide a data backup method and storage device to solve and improve the aforementioned problems and shortcomings of the prior art.

Another purpose of this case is to provide a data backup method and storage device, when writing data to the first logical block address of the first mapping table, write the data to the physical area of the storage block through the first mapping table Block address, and write data to another physical block address of the storage block through the second mapping table at the same time. After the backup command is executed, the second mapping table can be stored in another physical block location. The data in the address is used as the backup data, so that the backup operation is completed instantly, and then the function of fast backup is realized.

Another purpose of this case is to provide a data backup method and storage device. After executing the backup command, immediately stop writing data to the physical block address and another physical block address at the same time, and instead write to The newly added data of the first logical block address of the first mapping table is only written to the physical block address, which can effectively separate the in-use data from the backup data.

Another object of this case is to provide a data backup method and storage device, by dividing the first logical block address and the second logical block address into a plurality of first logical block areas and a plurality of second logical areas The block area records the first logical block area to which the storage address of each new data belongs, and writes all the data in each first logical block area that is recorded to the corresponding second logical block area Another physical block address of, provides a data backup method for incremental backup of partitions. Only the data in the first logical block area that has been recorded is backed up, which can greatly reduce the amount of data access and effectively reduce the backup time.

To achieve the above objective, a preferred implementation aspect of the present case is to provide a data backup method including the steps of: (a) providing a storage device, wherein the storage device includes a storage module, and the storage module has a first Mapping table, a second mapping table and a storage block; (b) writing a data to a first logical block address of the first mapping table, and writing the data to the first mapping table through the first mapping table A physical block address of the storage block, and the data is simultaneously written into another physical block address of the storage block through a second logical block address of the second mapping table; c) execute a backup command; and (d) use the second mapping table and the data stored in the address of the other physical block as a backup data.

In order to achieve the above objective, a preferred implementation aspect of the present invention is to provide a storage device, including: a controller; and a storage module connected to the controller, and the storage module has a first mapping table, A second mapping table and a storage block; wherein, before a backup command is executed, when a data is written to a first logical block address of the first mapping table, the data is passed through the first logical block at the same time A mapping table and a second logical block address of the second mapping table are written to a physical block address and another physical block address of the storage block; after the backup command is executed , The second mapping table and the data stored in the address of the other physical block become a backup data, and when a new data is written to the first logical block address, the new data is It is written into the physical block address through the first mapping table.

Some typical embodiments embodying the features and advantages of this case will be described in detail in the following description. It should be understood that this case can have various changes in different aspects, which do not depart from the scope of this case, and the descriptions and illustrations therein are essentially for illustrative purposes, rather than being constructed to limit the case.

Please refer to Figure 1, Figure 2, and Figure 3, where Figure 1 is a flowchart showing the data backup method of an embodiment of this case, and Figure 2 is a block diagram showing the architecture of the storage device of an embodiment of this case, and Figure 3 is a schematic diagram showing the relationship among data, logical block addresses, first mapping table, second mapping table, and storage block of the data backup method in this case. As shown in Figure 1, Figure 2, and Figure 3, according to an embodiment of this case, the data backup method of this case can be applied to the host running the operating system (Operation System, OS), but not To be limited, and the data backup method in this case includes the following steps. First, as shown in step S100, the storage device 1 is provided. The storage device 1 includes a storage module 11, and the storage module 11 has a first mapping table 111, a second mapping table 112 and a storage block 113. Next, as shown in step S200, write data to the first logical block address (Logical Block Address, LBA) of the first mapping table 111, and write the data to the storage block 113 through the first mapping table 111 Physical block address, and write data into another physical block address of the storage block 113 through the second logical block address of the second mapping table 112 at the same time. It should be noted that the address of the first logical block of the first mapping table 111 and the address of the second logical block of the second mapping table 112 are shown in Figures 3, 5, 7, and 7 of the drawings in this case. Figures 8, 9, and 11 are shown in the left half of the first mapping table 111 and the second mapping table 112, and the first logical block address is related to the second logical block address , That is, any specific logical block address in the second logical block address can be found and located through another specific logical block address in the first logical block address. In addition, the data written to the first logical block address is synchronously and completely written to the physical block address and another physical block address. In other words, in the physical block address of the storage block 113 and another physical block address, there is a whole piece of complete data, instead of storing different parts of the data separately. In addition, preferably, the logical block address referred to in this case refers to all address ranges in the logical block, rather than a single fixed address, but it is not limited to this. Then, as shown in step S300, the backup instruction is executed. Then, as shown in step S400, the second mapping table 112 and the data stored in another physical block address are used as backup data. Specifically, when the user wants to use the data backup method in this case to back up, after executing the backup command in the operating system, the backup action will be completed in an instant, that is, the second mapping table 112 is stored in another physical block address The data is used as backup data to realize the function of fast backup.

In some embodiments, the storage device 1 further includes a controller 10, and the storage module 11 is connected to the controller 10. Further, the storage module 10 of the storage device 1 may include a firmware code execution area 114 for the firmware code to execute and cooperate with the controller 10 to perform operations on the first mapping table 111, the second mapping table 112, and the storage block 113. Control, but not limited to this. In addition, the storage device 1 may be, for example, a solid state drive, the storage module 11 may be, for example, a flash memory, and the first mapping table 111 and the second mapping table 112 may each be, for example, a flash translation layer (Flash Translation Layer). , FTL) mapping table, but not limited to this, and the first mapping table 111 and the second mapping table 112 are associated with each other. The first mapping table 111 and the second mapping table 112 can be used to record the first logical block address and the second logical block address and the physical block address of the storage block 113 of the storage module 11 of the storage device 1 and The mapping relationship of another physical block address. For example, in Figure 3, addresses 0000 to 4999 in the first logical block address are mapped to addresses 5001 to 10000 in the storage block 113, and the second logical block address is The addresses 5000 to 9999 are mapped to addresses 0001 to 5000 in the storage block 113. Since the first mapping table 111 corresponds to the addresses 0000 to 4999 in the first logical block address to the addresses 5001 to 10000 in the storage block 113, and the second mapping table 112 corresponds to the second logical block bit The addresses 5000 to 9999 in the address correspond to the addresses 0001 to 5000 in the storage block 113, so the addresses 5001 to 10000 in the storage block 113 are physical block addresses, and the addresses in the storage block 113 0001 to 5000 are the addresses of another physical block. Alternatively, the physical block address and the address of another physical block do not have to be a single continuous address range, and can be designed as multiple separate address ranges according to the requirements of the manufacturer or the client. For example, addresses 0001 to 0200 in storage block 113 are physical block addresses, and addresses 0201 to 0250, addresses 0381 to 0500, and addresses 0801 to 0830 in storage block 113 are other physical block locations Address, but not limited to this.

Please refer to Figures 4 and 5 in conjunction with Figure 2. Figure 4 shows the flow chart of the data backup method of an embodiment of this case, and Figure 5 shows the data backup method of an embodiment of this case in the backup command The schematic diagram of the relationship among the data after execution, the new data, the logical block address, the first mapping table, the second mapping table and the storage block. As shown in Figures 2, 4, and 5, after step S400 of the data backup method in this case, the system may further include step S500, writing the newly added data to the first logical block address, and adding The data is written into the physical block address through the first mapping table 111. In other words, after the second mapping table 112 and the data stored in the address of another physical block are used as backup data, the data backup method in this case immediately stops writing data to the physical block address and another physical block at the same time. In the block address operation, the newly written data subsequently written will only be written to the physical block address through the first mapping table 111. In this way, the data backup method in this case can effectively separate the data in use from the backup data.

Simply put, before the backup command is executed, when data is written to the first logical block address, the data is simultaneously written to the physical block address through the first mapping table 111 and the second mapping table 112. And another physical block address. After the backup command is executed, the second mapping table 112 and the data stored in the address of another physical block become the backup data, and when the new data is written to the address of the first logical block, the new data is through The first mapping table 111 is written into the physical block address.

Please refer to Figure 6, Figure 7, Figure 8, and Figure 9 in conjunction with Figure 2. Figure 6 shows a flowchart of an embodiment of the data backup method in this case, and Figure 7 shows an embodiment of this case The data backup method after the execution of the backup command is a schematic diagram of the relationship between the data, the new data, the logical block address and its logical block area, the first mapping table, the second mapping table and the storage block after the backup command is executed. Figure 8 shows The data backup method of one embodiment of the present case shows the relationship between the data, new data, logical block address and its logical block area, the first mapping table, the second mapping table, and the storage block after the backup command is executed, and Figure 9 shows the data, newly added data, logical block address and its logical block area, the first mapping table, the second mapping table, and the storage block after the backup command is executed in the data backup method of an embodiment of this case The relationship diagram. As shown in Fig. 2 and Fig. 6 to Fig. 9, after step S400 of the data backup method of this case, the system may further include step S600, dividing the first logical block address and the second logical block address into A plurality of first logic block regions and a plurality of second logic block regions, wherein the size of the plurality of first logic block regions corresponds to the size of the plurality of second logic block regions. In some embodiments, the size of each first logical block area may be the same or different. For example, in Figure 7, the first logical block area G1, the first logical block area G2, and the first logical area The block area G3, the first logical block area G4, and the first logical block area G5 have the same size; in Figure 8, the first logical block area G11, the first logical block area G12, and the first logical area The size of the block area G13 is different from each other. In some embodiments, the sizes of a part of the first logical block areas are the same, and the sizes of the remaining first logical block areas are the same as each other and are the same as those of the first logical block areas of the aforementioned part. The sizes are different. For example, in Figure 9, the sizes of the first logical block area G21, the first logical block area G22, and the first logical block area 23 are the same, and the first logical block area G24, the first logical block area G24 and the first logical block area 23 have the same size. The block area G25, the first logical block area G26, and the first logical block area 27 have the same size as each other but are the same as the aforementioned first logical block area G21, first logical block area G22, and first logical block area The size of 23 is different. On the other hand, in the second mapping table 112, the second logical block address is divided into a plurality of second logical block areas, and the size of the plurality of first logical block areas corresponds to the same size as the first logical block areas. 2. The size of the logical block area. For example, if the first logical block address is divided into equal-sized first logical block area G1, first logical block area G2, first logical block area G3, and first logical block area G4 And the first logical block area G5 (as shown in Fig. 7), the second logical block address will be divided into five second logical block areas of equal size correspondingly.

Then, after step S600, the data backup method of the present case may further include step S700, writing at least one new data to the first logical block address, and recording the first logic to which the storage address of each new data belongs Block area, and write each new data to the physical block address of the storage block 113 through the first mapping table 111. In some embodiments, the first logical block address is divided into a plurality of first logical block areas, and the first logical block area to which the storage address of the newly added data belongs can be determined by the firmware of the storage device 1. However, it is not limited to this, and the firmware is preferably run in the firmware code execution area 114 of the storage module 11, but it is not limited to this.

Please refer to Figures 10 and 11 in conjunction with Figures 2 and 9, where Figure 10 shows a flowchart of an embodiment of the data backup method in this case, and Figure 11 shows an embodiment of the data backup in this case The method is a schematic diagram of the relationship between the data, the new data, the logical block address and its logical block area, the first mapping table, the second mapping table and the storage block after the incremental backup command is executed. As shown in FIG. 2, FIG. 9, FIG. 10, and FIG. 11, the data backup method of this case, after step S700, may further include step S800, step S900, and step S1000. Among them, step S800 is to execute an incremental backup command, step S900 is to find the second logical block area corresponding to each first logical block area to be recorded, and step S1000 is to record each first logical block area. All the data in the block area is written to the address of another physical block corresponding to the second logical block area. For example, the storage address of the newly added data in Figure 9 is located in the first logical block area G23, so the first logical block area G23 is recorded. After the incremental backup command is executed in step S800, in step S900 In this case, the data backup method of this case is to search for the second logical block area corresponding to the recorded first logical block area G23, and in step S1000, write all the data in the first logical block area G23 to The address of another physical block corresponding to the second logical block area corresponding to the first logical block area G23. On the other hand, if taking Fig. 7 and Fig. 8 as examples, the storage addresses of the newly added data are located in the first logical block area G3 and the first logical block area G12. In the steps S900 and S900 of the data backup method in this case, In step S1000, all the recorded data in the first logical block area G3 and the first logical block area G12 are written to another physical block address through the second mapping table 112. It can be seen that the data backup method in this case provides a data backup method for partition incremental backup, only backing up the data in the first logical block area that has been recorded, which can greatly reduce the amount of data access and effectively reduce the backup time.

Please refer to Figure 12 in conjunction with Figures 2 and 10, where Figure 12 shows a partial flowchart of the data backup method of an embodiment of the present case. As shown in Fig. 2, Fig. 10 and Fig. 12, the data backup method of this case can include step S710, step S720, step S730, step S800, step S900, and step S1000 after step S600. After step S600, as shown in step S710, a plurality of first logical block areas are numbered, so that each first logical block area corresponds to an area number. Then, as shown in step S720, write at least one newly added data to the first logical block address, and record the area number corresponding to the first logical block area to which the storage address of each newly added data belongs. Then, as shown in step S730, each new data is written to the physical block address of the storage block 113 through the first mapping table 111. After step S710 to step S730 are completed, the data backup method of this case executes step S800, step S900, and step S1000. Step S800 is to execute an incremental backup command. In step S900, the second logical block area corresponding to each first logical block area to be recorded is searched, and in step S1000, each first logical block area to be recorded is searched. All data in a logical block area is written to another physical block address of the storage block 113 corresponding to the second logical block areas. Taking Figure 11 as an example, in step S710, the first logical block area G21 to the first logical block area G27 are numbered, for example, the first logical block area G21 to the first logical block area G27 are numbered. Correspond to area numbers 1 to 7. Next, in step S720, when the newly added data is written to the first logical block area G23, the area number 3 corresponding to the first logical block area G23 is recorded. Then, in step S730, the newly added data is written to the physical block address through the first mapping table 111. Further, after the incremental backup command in step S800 is executed, in step S900, search for the second logical block areas corresponding to each of the recorded first logical block areas, and in step S1000, All the recorded data in each first logical block area is written into the address of another physical block corresponding to the second logical block area. Since only the corresponding area number is recorded, the amount of data access can be effectively reduced.

In summary, this project provides a data backup method and storage device. When data is written to the address of the first logical block of the first mapping table, the data is written to the physical area of the storage block through the first mapping table. Block address, and write data to another physical block address of the storage block through the second mapping table at the same time. After the backup command is executed, the second mapping table can be stored in another physical block location. The data in the address is used as the backup data, so that the backup operation is completed instantly, and then the function of fast backup is realized. At the same time, after executing the backup command, immediately stop writing data to the physical block address and another physical block address at the same time, and instead write to the first logical block address of the first mapping table. The newly added data is only written to the physical block address, which can effectively separate the in-use data from the backup data. In addition, by dividing the first logical block address and the second logical block address into a plurality of first logical block areas and a plurality of second logical block areas, the storage address of each new data is recorded It belongs to the first logical block area, and writes all the recorded data in each first logical block area to the address of another physical block corresponding to the second logical block area, providing a partition increment The data backup method of backup only backs up the data in the first logical block area that has been recorded, which can greatly reduce the amount of data access and effectively reduce the backup time.

Even though the present invention has been described in detail by the above-mentioned embodiments, it can be modified in many ways by those skilled in the art, but it does not deviate from the scope of the attached patent application.

1: storage device 10: Controller 11: Storage module 111: first mapping table 112: second mapping table 113: storage block 114: Firmware code execution area S100, S200, S300, S400, S500, S600, S700, S800, S900, S1000: steps S710, S720, S730: steps G1, G2, G3, G4, G5: the first logical block area G11, G12, G13: the first logical block area G21, G22, G23, G24, G25, G26, G27: the first logical block area

Figure 1 is a flow chart showing the data backup method of an embodiment of the present case. FIG. 2 is a block diagram showing the structure of the storage device according to an embodiment of the present invention. Figure 3 is a schematic diagram showing the relationship among data, logical block addresses, first mapping table, second mapping table, and storage block before the execution of the backup command in the data backup method of an embodiment of the present case. Figure 4 is a flow chart showing the data backup method of an embodiment of this case. Figure 5 is a schematic diagram showing the relationship among data, new data, logical block addresses, first mapping table, second mapping table, and storage block after the backup command is executed in the data backup method of an embodiment of the present case. Figure 6 is a flowchart showing the data backup method of an embodiment of the present case. Figure 7 shows the data, newly added data, logical block address and its logical block area, the first mapping table, the second mapping table, and the storage block after the backup command is executed in the data backup method of an embodiment of this case The relationship diagram. Figure 8 shows the data, newly added data, logical block address and its logical block area, the first mapping table, the second mapping table, and the storage block after the backup command is executed in the data backup method of an embodiment of this case The relationship diagram. Figure 9 shows the data, newly added data, logical block address and its logical block area, the first mapping table, the second mapping table, and the storage block after the backup command is executed in the data backup method of an embodiment of this case The relationship diagram. Figure 10 is a flow chart showing the data backup method of an embodiment of this case. Figure 11 shows the data, newly added data, logical block address and its logical block area, the first mapping table, the second mapping table, and storage after the incremental backup command is executed in the data backup method of an embodiment of this case Schematic diagram of the relationship between blocks. Figure 12 shows a partial flow chart of the data backup method in an embodiment of this case.

S100, S200, S300, S400: steps

Claims (10)

A data backup method, including the steps: (a) Provide a storage device, wherein the storage device includes a storage module, and the storage module has a first mapping table, a second mapping table, and a storage block; (b) Write a piece of data to a first logical block address of the first mapping table, and write the data to a physical block address of the storage block through the first mapping table, and The data is simultaneously written into another physical block address of the storage block through a second logical block address of the second mapping table; (c) Execute a backup instruction; and (d) Use the second mapping table and the data stored in the address of the other physical block as a backup data. The data backup method according to claim 1, wherein the first logical block address in the first mapping table is related to the second logical block address in the second mapping table. For the data backup method described in claim 1, after the step (d), it further includes the steps: (e) write a new data to the first logical block address, and pass the new data through the first logical block address. A mapping table is written to the physical block address. According to the data backup method of claim 1, after the step (d), it further includes the step: (f) dividing the first logical block address and the second logical block address into a plurality of first A logical block area and a plurality of second logical block areas, wherein the size of the plurality of first logical block areas corresponds to the size of the plurality of second logical block areas. The data backup method according to claim 4, wherein the size of each of the first logical block regions is the same or different. The data backup method according to claim 4, wherein the sizes of the plurality of first logical block areas of a part are the same as each other, and the sizes of the remaining plurality of first logical block areas are the same as each other and are the same as those of the part The sizes of the plural logical block areas are different. According to the data backup method of claim 4, after the step (f), the method further includes the step of: (g) writing at least one new data to the first logical block address, and recording each new data The first logical block area to which the storage address belongs, and each of the newly added data is written to the physical block address through the first mapping table. According to the data backup method of claim 7, after step (g), it further includes the following steps: (h) Execute an incremental backup instruction; and (i) searching for the second logical block areas corresponding to each of the first logical block areas recorded; (j) Write all the recorded data in each of the first logical block areas to the addresses of the other physical block corresponding to the second logical block areas. The data backup method described in claim 4 further includes the following steps after step (f): (g1) Numbering the plurality of first logical block areas, so that each of the first logical block areas corresponds to an area number; (g2) Write at least one newly added data to the first logical block address, and record the area number corresponding to the first logical block area to which the storage address of each newly added data belongs; (g3) Write each of the newly added data to the physical block address through the first mapping table; (h) Execute an incremental backup instruction; and (i) searching for the second logical block areas corresponding to each of the first logical block areas recorded; (j) Write all the recorded data in each of the first logical block areas to the addresses of the other physical block corresponding to the second logical block areas. A storage device, including: A controller; and A storage module connected to the controller, and the storage module has a first mapping table, a second mapping table and a storage block; Wherein, before a backup command is executed, when a data is written to a first logical block address of the first mapping table, the data is passed through one of the first mapping table and the second mapping table at the same time The second logical block address is written to a physical block address and another physical block address of the storage block; after the backup command is executed, the second mapping table and the other physical block address are stored The data of a physical block address becomes a backup data, and when a new data is written to the first logical block address, the new data is written to the first mapping table Physical block address.

Images