Backup method for key data in hybrid SSD

A key data, hybrid technology, applied in the redundant operation of data error detection, data processing input/output process, electrical digital data processing and other directions, can solve the problem of reducing data backup overhead, delay and increase in write amplification and other problems, to achieve the effect of improving reliability, low write amplification, and good performance

Pending Publication Date: 2021-09-28
6 Cites 0 Cited by

AI-Extracted Technical Summary

Problems solved by technology

b class="d_n">[0005] The purpose of the present invention is to provide a method for backing up key data in a hybrid SSD. By accumulating and then migrating the data that needs to be backed up, i...
View more


The invention relates to a backup method for key data in a hybrid SSD, which mainly comprises the following steps: judging whether the data need to be backed up, and for the read operation of the backup data, defaulting that the data of a fast medium is read and a slow medium is used for recovery; and for the write operation of the backup data, selecting a backup mode according to the request size; for a relatively small write request, using accumulative backup, firstly writing two parts of data to a fast medium, and migrating to a slow medium after a certain amount of data is accumulated; for a large write request, writing data into a fast medium and a slow medium at the same time in a traditional backup mode. The invention has the following advantages that by means of the method that the fast medium is written firstly to be accumulated and then migrated to the slow medium, the problems that delay and write amplification are greatly increased due to the fact that the fast medium and the slow medium are written at the same time are solved, and data backup performance and write amplification expenditure can be reduced.

Application Domain

Input/output to record carriersRedundant operation error correction

Technology Topic

Data needsBackup +2


  • Backup method for key data in hybrid SSD
  • Backup method for key data in hybrid SSD
  • Backup method for key data in hybrid SSD


  • Experimental program(1)

Example Embodiment

[0024] Example
[0025] Mixed SSD with SLC-TLC as an example, see figure 1 , Is a read operation flow chart of the present embodiment, starting from step 101, then:
[0026] At step 102, after the read request arrives, the SSD will split a large read request into a plurality of small read sub-requests separately.
[0027] At step 103, the SSD controller is confirmed to determine if the requested data has a backup as the backup tag issued by the request. If the requested data is not backed up, step 104 is performed, and the read sub-request is processed according to the hybrid SSD, and then proceeds to step 109; if the requested data has a backup, step 105 is executed, from the SLC read data, Then go to step 106.
[0028] At step 106, it is judged whether or not read error occurs when the SLC read data. If a read error occurs, step 107 is performed from the TLC, and then perform step 108, perform data recovery with the backup data saved on the TLC, and finally proceeds to step 109; if no read error occurs, directly go to step 109.
[0029] Mixed SSD with SLC-TLC as an example, see figure 2 It is a write operation flowchart in the present invention, starting from step 201, then:
[0030] At step 202, after the request arrives, the SSD is split by a large write request into a plurality of small write sub-requests separately.
[0031] At step 203, the SSD controller checks if the data issued by the write request is determined whether the requested data requires a backup. If the requested data does not require a backup, step 204 is performed, and the write sub-request is processed according to the hybrid SSD, and then proceeds to step 210; if the requested data requires a backup, step 205 is performed.
[0032] At step 205, it is judge whether or not the size of the request belonging the current sub-request is greater than the threshold. If it is greater than the threshold, then the request does not need to be accumulated, performing step 206, directly writing each of the data to the SLC and TLC; if less than or equal to the threshold, the request needs to be cumulative backup, proceed to step 207.
[0033] At step 207, the data of the sub-request is written on the SLC and adds the cumulative page number ACC_COUNT 1, and then performs the next step 208.
[0034] At step 208, it is judged whether the accumulated page number ACC_CONT reaches the number of TLC strips. If so, step 209 is performed, one of the cumulative data is migrated to the TLC, and the ACC_CONT is set to 0, and the proceeds to step 210 end; if it is not yet reached, the direct proceeds to step 210.
[0035] image 3 It is a schematic diagram of a TLC strip in the present invention.
[0036] Here you need further explanation of the TLC strip. Since there is a channel, a chip, a wafer, a group 4 parallel in the SSD, the different sub requests of the same request will be assigned to different parallel units on parallel. For TLC, since the physical page size is 16KB, each 4 logical pages correspond to a physical page, when the request is assigned to a different channel, chip, wafer, and group, if the request size is requested Do not align, it is very likely that some physical pages are not brought to 4 logical pages, resulting in large writing among TLCs. like image 3As shown, when a request containing 16 logical pages is written to TLC, these logical pages correspond to two channels, 2 chips, 4 wafers, 8 packets of 8 physical pages, and each physics The pages will only have two logical pages, so there is a double write amplifier. In the present invention, the TLC strip size is the minimum amount of data across all parallel units of the TLC, and the number of TLC strips can be written to a 4kb page number of a TLC strip, which is set to the threshold of the migration during the accumulation process. Migration with TLC strip size can completely avoid the writing of TLCs caused by small request backups, achieving ideals to reduce the effect of write an enlargement. The TLC strip size is determined by the parallel architecture and allocation strategy of SSD. exist image 3 In the architecture shown, the TLC is distributed on 2 channels. Each channel has a TLC chip, each chip has 2 wafers, each wafer has two 2 packets, two red dashed lines The content is combined for a TLC strip, a total of 2 * 1 * 2 * 2 = 8 16KB pages, that is, 32 4KB pages, the TLC strip page number is 32, the TLC strip size is 128KB. That is, when the number of pages accumulated in the SLC reaches 32, the accumulated data is migrated to the TLC, and the TLC is not written in this process.


no PUM

Description & Claims & Application Information

We can also present the details of the Description, Claims and Application information to help users get a comprehensive understanding of the technical details of the patent, such as background art, summary of invention, brief description of drawings, description of embodiments, and other original content. On the other hand, users can also determine the specific scope of protection of the technology through the list of claims; as well as understand the changes in the life cycle of the technology with the presentation of the patent timeline. Login to view more.

Similar technology patents

Control system and method for motor vehicles

InactiveUS20040084002A1improve reliabilityspeed and stability

Installation management method, server and terminal for application program

InactiveCN102446106Aprevent crackingImprove reliability

Forest fireproof monitoring and patrolling system


Unmanned aerial vehicle flight control system having multisensor redundant backup

ActiveCN105867414AIncrease flight control weight and costImprove reliability

Classification and recommendation of technical efficacy words

  • Improve reliability
  • good performance

Multiple branch predictions

ActiveUS20050268075A1improve reliabilityfacilitate availability

Implantable lead

ActiveUS20100137928A1good flexibility , fatigue resistance and flex lifeimprove reliability

Macrocyclic picolinamides as fungicides

ActiveUS20140187588A1good performanceeasy to use

System and Method for Socially Aware Recommendations Based on Implicit User Feedback

InactiveUS20150187024A1good performanceintroduce noise
Who we serve
  • R&D Engineer
  • R&D Manager
  • IP Professional
Why Eureka
  • Industry Leading Data Capabilities
  • Powerful AI technology
  • Patent DNA Extraction
Social media
Try Eureka
PatSnap group products