WO2018059565A1 - Procédé et système de copie de sauvegarde de données de mémoire flash - Google Patents

Procédé et système de copie de sauvegarde de données de mémoire flash Download PDF

Info

Publication number
WO2018059565A1
WO2018059565A1 PCT/CN2017/104623 CN2017104623W WO2018059565A1 WO 2018059565 A1 WO2018059565 A1 WO 2018059565A1 CN 2017104623 W CN2017104623 W CN 2017104623W WO 2018059565 A1 WO2018059565 A1 WO 2018059565A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
data area
flash memory
backup
partition
Prior art date
Application number
PCT/CN2017/104623
Other languages
English (en)
Chinese (zh)
Inventor
何美玲
Original Assignee
深圳创维数字技术有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 深圳创维数字技术有限公司 filed Critical 深圳创维数字技术有限公司
Publication of WO2018059565A1 publication Critical patent/WO2018059565A1/fr

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/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

Definitions

  • the present disclosure relates to the field of flash technology, for example, to a method and system for backing up flash data.
  • the flash backup method in the related art includes: a primary backup mechanism and a secondary backup mechanism.
  • the flash memory includes or is added by the user to have a backup data area, the data in the original data area is damaged, the data in the backup data area can be used, and the data in the backup data area can be used to use the data in the original data area.
  • the flash memory includes a raw data area, a backup data area, and a swap area, and recovers the corrupted data using important data (files) in at least one of the original data area, the backup data area, and the swap area.
  • the storage capacity that the user can allocate is small in the case where the total storage capacity of the flash memory is constant.
  • a backup data area is added correspondingly and even a swap area is added, and the user cannot use the backup data area and the swap area. Since data is written to the flash memory through spi, the data is written at a slow rate.
  • the flash memory takes twice or even three times longer than the flash memory without the backup data area. Users using flash memory with a one-level backup mechanism, potential defects in the flash itself or flash drive may cause write or data check exceptions, as well as corrupted raw and backup data.
  • a backup method and system for flash data is provided.
  • the system is started by using the default data stored in the planned partition to start the system when the data in the original data area and the backup data area are abnormal.
  • a method for backing up flash data including:
  • the system is started using the default data in the planned partition of the flash memory, wherein the default data includes one or more partitions in the flash memory.
  • Divide data or partitions of important partitions to plan partitioning data, and necessary boot data required for system startup, and the planned partitions are flash partitions that will not be altered or modified.
  • the method further includes:
  • the original data area, the backup data area, and the sector of the flash memory occupied by the planned partition are preset.
  • the method further includes:
  • the method further includes:
  • the data in the backup data area is copied to the original data area, and the system is started using the data in the backup data area.
  • the planning partition also stores data required for flash booting.
  • the method further includes:
  • the divided data of each partition in the flash memory or the partitioned data of important partitions in the flash memory, and default data are written into the planned partition.
  • the method before determining whether the data in the original data area is damaged, the method further includes: pre-dividing a plurality of partitions in the flash memory to determine that the original data area, the backup data area, and the planning partition respectively occupy Sector.
  • the method further includes: driving the flash memory.
  • a backup system for flash data comprising:
  • a first booting module configured to boot a system using default data in a planned partition of the flash memory when data in both the original data area and the backup data area in the flash memory is damaged, wherein the default data includes the flash memory Divided data of one or more partitions or partitioned plan data of important partitions, and necessary boot data required for system startup, and the planned partition is a flash partition that is not altered or modified.
  • system further includes:
  • a first determining module configured to determine whether data in the original data area of the flash memory is damaged
  • a second determining module configured to determine whether the data in the backup data area of the flash memory is damaged if the first determining module determines that the data in the original data area is damaged
  • the first startup module is configured to: if the second determining module determines that the data in the backup data area is damaged, copy the default data saved in the planned partition of the flash memory to the original data area and the In the backup data area;
  • the original data area, the backup data area, and the sector of the flash memory occupied by the planned partition are preset.
  • system further includes:
  • the third determining module is configured to determine whether the data in the backup data area is damaged if the first determining module determines that the data in the original data area is not damaged;
  • a second startup module configured to: if the third determining module determines that the data in the backup data area is not damaged, use the data in the original data area to start the system; if the third determining module determines the The data in the backup data area is corrupted, the data in the original data area is copied to the backup data area, and the system is started using the data in the original data area.
  • the first startup module is further configured to: if the second determining module determines that the data in the backup data area is not damaged, copy the data in the backup data area to the original data area, The system is booted using the data in the backup data area.
  • the planning partition further stores data required for device startup.
  • system further includes
  • Writing to the module configured to: before the determining whether the original data area is damaged, writing the partition data of each partition in the flash memory and the data related to system startup into the original data area;
  • the divided data of each partition in the flash memory or the partitioned data of important partitions in the flash memory, and default data are written into the planned partition.
  • system further includes:
  • the design module is configured to pre-divide a plurality of partitions in the flash memory to determine sectors occupied by the original data area, the backup data area, and the planned partition.
  • system further includes:
  • Drive module set to drive flash.
  • a computer readable storage medium storing computer executable instructions arranged to perform the above method.
  • An electronic device comprising:
  • At least one processor At least one processor
  • the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the method described above.
  • FIG. 1 is a flowchart of a method for backing up flash data provided by the first embodiment.
  • FIG. 2 is a flow chart of a method for backing up flash data provided by the second embodiment.
  • FIG. 3 is a structural block diagram of a backup system for flash data provided by the third embodiment.
  • FIG. 4 is a block diagram showing the structure of a backup system for flash data provided by the fourth embodiment.
  • FIG. 5 is a schematic structural diagram of hardware of an electronic device according to an embodiment.
  • FIG. 1 is a flow chart of a method for backing up flash data provided in a specific embodiment. As shown in Figure 1, the method includes the following steps.
  • step 101 it is determined whether the data in the original data area of the flash memory is damaged; if the data in the original data area is not damaged, step 102 is performed; if the data in the original data area is damaged, step 105 is performed.
  • the embodiment can be applied to a flash memory without a self-backup mechanism.
  • the user can preset a sector occupied by the original data area, and the data in the original data area includes planning information of each partition in the flash memory and an important relationship related to system startup. data.
  • the important data may be the boot parameters bootcmd and bootargs in the Linux operating system or the Android (Adroid) operating system, or mtdparts (the divided data storing the flash memory).
  • the data in the raw data area may also include some environment related data.
  • the environment related data may be at least one of ethaddr, bootdelay, and baudrate.
  • step 102 it is determined whether the data in the backup data area of the flash memory is damaged. If the data in the backup data area is not damaged, step 103 is performed; if the data in the backup data area is damaged, step 104 is performed.
  • the data in the original data area is not damaged, it is judged whether the data in the backup data area is damaged, and the data in the original data area and the data in the backup data area are mutually backed up, and the backup can be judged regardless of whether the data in the original data area is damaged or not. Whether the data in the data area is damaged. If the data in the backup data area is corrupted, the data in the original data area can be copied to the backup data area.
  • the user can set the sector occupied by the backup data area, the data in the backup data area includes the partition data of each partition of the flash memory, and important data related to system startup.
  • the data in the backup data area can be the same as the data in the original data area, and the data in the backup data area can be backed up with the data in the original data area.
  • data integrity algorithms eg, Cyclic Redundancy Check (CRC)
  • CRC Cyclic Redundancy Check
  • step 103 the system is started using the data in the original data area.
  • the data in the backup data area is not damaged, and the system can be started using the data in the original data area.
  • step 104 the data in the original data area is copied to the backup data area, and the system is started using the data in the original data area.
  • the data in the original data area is not corrupted, the data in the backup data area is corrupted, the data in the original data area can be copied to the backup data area, and the system is started using the data in the original data area.
  • data in the backup data area and one of the original data areas may be corrupted. Since the data in the backup data area and the data in the original data area are mutually backed up, when the data in one of the backup data area and the original data area is damaged, the data of the booting system can still be obtained.
  • step 105 it is determined whether the data in the backup data area is damaged. If the data in the backup data area is not damaged, step 106 is performed; if the data in the backup data area is damaged, step 107 is performed.
  • step 106 the data in the backup data area is copied to the original data area, and the system is started using the data in the backup data area.
  • the data in the backup data area is copied to the original data area, and the system is started using the data in the backup data area. If a sudden power failure occurs during the process of writing data to the flash memory, the data in one of the backup data area and the original data area is damaged. Since the data in the backup data area and the data in the original data area are backed up to each other, the system can still be started.
  • step 107 the default data stored in the planned partition of the flash memory is copied into the original data area and the backup data area, and the system is started using the default data.
  • the system can be booted by default data stored in the planned partition of the flash memory.
  • the default data stored in the planned partition of the flash memory may be copied into the original data area and the backup data area.
  • the default data startup system includes partition partition data for each partition in the flash memory or partition partition data of important partitions in the flash memory, and data required for system startup.
  • the default data includes the necessary data to start the system.
  • the default data is the necessary data for system startup. It takes up less storage space and saves the default data in the planned partition of the flash memory to ensure system startup.
  • the planned partition of the flash memory can be other partitions than the original data area and the backup data area.
  • Important partitions include the partition where the boot data resides. It can also include system kernel (kernel) data, root file system (rootfs) data in Linux systems, and partitions where user data (userdata) resides.
  • kernel kernel
  • rootfs root file system
  • user data userdata
  • the default data can also occupy a single partition.
  • the default data is stored in a boot data area that also holds data required for flash boot, such as boot data and the like. In the process of producing flash memory or using flash memory, the data in the boot data area is not changed or rarely changed, and the default data is stored in the boot data area to protect the default data.
  • the default data can also be stored in a partition (eg, the first sector of the flash) that will not be altered or altered during the production or use of the flash.
  • the boot data area may also store data required for booting of an external device (for example, at least one of a network port or a Universal Serial Bus (USB) device).
  • USB Universal Serial Bus
  • the original data area, the backup data area, and the planned partition are occupied by The sectors are preset by the user. Each partition can occupy one sector, and each partition can also occupy multiple sectors.
  • the data in the original data area and the backup data area can be written by the user according to his needs, and the default data can also be written into the planning partition by the user according to his needs.
  • the user sets the partition to ensure system startup by using the original data area, the backup data area, and the default data stored in the planned partition.
  • the default data not only occupies a large number of sectors, but also ensures that the data in the original data area and the backup data area are damaged when the system starts data, which can solve the problem in the related art that the important data of the flash memory is damaged and the system cannot be started. The problem of inconvenience caused by the production and use of flash memory.
  • FIG. 2 is a flow chart of a method for backing up data in a flash memory provided in a specific embodiment.
  • the method includes the following steps.
  • step 201 the flash memory is driven.
  • step 202 it is determined whether the data in the original data area is damaged. If the data in the original data area is not damaged, step 203 is performed; if the data in the original data area is damaged, step 206 is performed.
  • step 203 it is determined whether the data in the backup data area is damaged. If the data in the backup data area is not damaged, step 204 is performed; if the data in the backup data area is damaged, step 205 is performed.
  • step 204 the system is launched using the data in the original data area.
  • step 205 the data in the original data area is copied to the backup data area, and the system is started using the data in the original data area.
  • step 206 it is determined whether the data in the backup data area is damaged. If the data in the backup data area is not damaged, step 207 is performed; if the data in the backup data area is damaged, step 208 is performed.
  • step 207 the data in the backup data area is copied to the original data area, and the location is used.
  • the data in the backup data area starts the system.
  • step 208 the default data stored in the planned partition of the flash memory is copied into the original data area and the backup data area, and the system is started using the default data.
  • the method before the determining whether the data in the original data area is damaged, the method further includes: pre-dividing a plurality of partitions in the flash memory to determine the original data area, the backup data area, and the Plan the sectors occupied by the partition.
  • pre-dividing a plurality of partitions in the flash memory to determine the original data area, the backup data area, and the Plan the sectors occupied by the partition.
  • multiple partitions in the flash memory can also be divided in the production process, and multiple partitions in the flash memory can be divided by the user during use.
  • the planning partition is a boot data area
  • the boot data area also stores data required for the flash boot itself, such as boot data.
  • the method further includes:
  • the divided data of each partition in the flash memory or the divided data of important partitions in the flash memory, and default data are written in the boot data area.
  • steps 201 to 208 are processes of using the original data area, the backup data area, and the three data areas of the start data area.
  • the user divides multiple partitions, and the system is started by using the original data area, the backup data area, and the default data stored in the planned partition.
  • the default data does not occupy more sectors and can guarantee the original data area and
  • the system can be started, which solves the problem that the system cannot be started due to the damage of the important data of the flash memory, which causes inconvenience to the production and use of the flash memory.
  • the data in the method in the above embodiment can occupy less flash space and shorten the read and write operation time of the flash memory.
  • the system can start up while occupying less flash space.
  • the method in the above embodiment can start the system by default data, facilitate online upgrade of data in the flash memory, and reduce maintenance cost of the electronic device including the flash memory.
  • the following is an embodiment of a backup system for flash data provided in a specific embodiment.
  • the embodiment of the backup system for flash data is based on the above-described embodiment of the backup method of flash data, and is not described in the backup system of the flash data. Reference is made to an embodiment of the backup method of the aforementioned flash data.
  • FIG. 3 is a structural block diagram of a backup system for flash data provided in a specific embodiment. This embodiment is implemented on the basis of the first embodiment of the backup method of the flash data. For the details not in the embodiment, please refer to the first embodiment of the backup method of the flash data. As shown in FIG. 3, the system includes: a first judging module 31, a second judging module 32, and a first starting module 33.
  • the first determining module 31 is configured to determine whether the data in the original data area of the flash memory is damaged.
  • the data in the original data area includes partition data for each partition of the flash memory, and important data related to system startup.
  • the second determining module 32 is configured to determine whether the data in the backup data area of the flash memory is damaged if the first determining module determines that the data in the original data area is damaged.
  • the data in the backup data area includes the planning of each partition in the flash memory and important data related to system startup.
  • the first startup module 33 is configured to: if the second determination module determines that the data in the backup data area is damaged, copy the default data saved in the planned partition of the flash memory to the original data area and the backup data. In the zone, the system is started using the default data.
  • system further includes: a third determining module 34 and a second starting module 35.
  • the third determining module 34 is configured to determine whether the data in the backup data area is damaged if the first determining module determines that the data in the original data area is not damaged.
  • the second startup module 35 is configured to: if the third determining module determines that the data in the backup data area is not damaged, use the data in the original data area to start the system; if the third determining module determines the The data in the backup data area is corrupted, the data in the original data area is copied to the backup data area, and the system is started using the data in the original data area.
  • the first startup module 33 may be further configured to: if the second determining module determines that the data in the backup data area is not damaged, copy the data in the backup data area to the original data area, The system is booted using the data in the backup data area.
  • the default data includes partitioned data for each partition in the flash memory or partitioned data of important partitions, and data required for system startup.
  • the sectors occupied by the original data area, the backup data area, and the planned partition of the flash memory may be preset by a user.
  • the user divides the partition, and uses the original data area, the backup data area, and the default data stored in the planned partition to ensure normal startup of the system.
  • the default data does not occupy more sectors but also ensures the original data area and
  • the system can be started, which solves the problem that the system cannot be started due to the damage of the important data of the flash memory, which causes inconvenience to the production and use of the flash memory.
  • the system includes a driving module 41, a first determining module 42, a second determining module 43, and a first starting module 44.
  • the drive module 41 is arranged to drive the flash memory.
  • the first decision module 42 is arranged to determine if the data in the original data area is corrupt.
  • the data in the original data area includes partition data for each partition in the flash memory and important data related to system startup.
  • the second determining module 43 is configured to determine whether the data in the backup data area is damaged if the first determining module determines that the data in the original data area is damaged.
  • the data in the backup data area includes partition data for each partition in the flash memory and important data related to system startup.
  • the first startup module 44 is configured to: if the second determination module determines that the data in the backup data area is damaged, copy the default data saved in the planned partition of the flash memory to the original data area and the backup data. In the zone, the system is started using the default data.
  • system further includes: a third determining module 45 and a second starting module 46.
  • the third determining module 45 is configured to determine whether the data in the backup data area is damaged if the first determining module determines that the data in the original data area is not damaged.
  • the second startup module 46 is configured to: if the third determining module determines that the data in the backup data area is not damaged, use the data in the original data area to start the system; if the third determining module determines the The data in the backup data area is corrupted, the data in the original data area is copied to the backup data area, and the system is started using the data in the original data area.
  • the first startup module 44 may be further configured to: if the second determining module determines that the data in the backup data area is not damaged, copy the data in the backup data area to the original data area, and use the The data in the backup data area starts the system.
  • the default data includes partition planning for the entire or important partition of the flash memory, and data required for system startup.
  • the original data area, the backup data area, and a sector occupied by the flash memory plan are preset by a user.
  • the planning partition is a boot data area, and the boot data area also holds data required for flash booting.
  • the system can also include a write module 47.
  • the write module is set to:
  • the planning data of each partition in the flash memory or the partition planning information of the important partition, and the default data are written in the startup data area.
  • the system further includes: a design module 48 configured to pre-divide a plurality of partitions in the flash memory to determine the original data area, the backup data area, and the planning partition Occupied sector.
  • a design module 48 configured to pre-divide a plurality of partitions in the flash memory to determine the original data area, the backup data area, and the planning partition Occupied sector.
  • the embodiment provides a system for using flash data backup. The user can divide the partition in the flash memory, and ensure the system startup by using the original data area, the backup data area, and the default data stored in the planned partition. The default data is The system can be started when the data in the original data area and the backup data area are abnormal, and the problem that the system cannot be started due to the damage of the important data of the flash memory is solved.
  • the electronic device includes:
  • At least one processor 50 is exemplified by a processor 50 in FIG. 5; a memory 51; and a communication interface 52 and a bus 53.
  • the processor 50, the memory 51, and the communication interface 52 can complete communication with each other through the bus 53.
  • Communication interface 52 can transmit data and signals.
  • Processor 50 can invoke logic instructions in memory 51 to perform the methods of the above-described embodiments.
  • logic instructions in the memory 51 described above may be implemented in the form of software functional units and sold or used as separate products, and may be stored in a computer readable storage medium.
  • the memory 51 is a computer readable storage medium and can be used to store software programs, computer executable programs, such as program instructions or modules corresponding to the methods in the above embodiments.
  • the processor 50 executes the functional application and data processing by executing software programs, instructions or modules stored in the memory 51, i.e., implements the methods in the above embodiments.
  • the memory 51 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function; the storage data area may store data created according to usage of the device, and the like. Further, the memory 51 may include a high speed random access memory, and may also include a nonvolatile memory.
  • the above technical solution may be embodied in the form of a software product stored in a storage medium, including one or more instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to execute All or part of the steps of the method described in the above embodiments.
  • a computer device which may be a personal computer, a server, a network device, etc.
  • the system is started by the default data stored in the planned partition, and the system can be started when the data in the original data area and the backup data area are damaged.

Abstract

Selon l'invention, un procédé de copie de sauvegarde de données de mémoire flash comprend les étapes suivantes : lorsque des données sont corrompues à la fois dans une zone de données d'origine et dans une zone de données de copie de sauvegarde d'une mémoire flash, utiliser des données par défaut dans une partition planifiée de la mémoire flash pour le démarrage de système, les données par défaut comprenant des données de division d'une ou de plusieurs partitions de la mémoire flash ou des données de division de partition d'une partition principale et des données de démarrage essentielles nécessaires au démarrage de système, et la partition planifiée est une partition de mémoire flash qui soit ne peut pas être modifiée, soit peut être modifiée de manière minimale. L'invention concerne également un système de copie de sauvegarde de données de mémoire flash.
PCT/CN2017/104623 2016-09-29 2017-09-29 Procédé et système de copie de sauvegarde de données de mémoire flash WO2018059565A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610864885.9A CN106484567A (zh) 2016-09-29 2016-09-29 一种flash数据备份的使用方法及系统
CN201610864885.9 2016-09-29

Publications (1)

Publication Number Publication Date
WO2018059565A1 true WO2018059565A1 (fr) 2018-04-05

Family

ID=58268274

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/104623 WO2018059565A1 (fr) 2016-09-29 2017-09-29 Procédé et système de copie de sauvegarde de données de mémoire flash

Country Status (2)

Country Link
CN (1) CN106484567A (fr)
WO (1) WO2018059565A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110287059A (zh) * 2019-05-21 2019-09-27 广东九联科技股份有限公司 一种spi flash的多备份方法

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106484567A (zh) * 2016-09-29 2017-03-08 深圳创维数字技术有限公司 一种flash数据备份的使用方法及系统
CN113296850B (zh) * 2021-07-26 2021-12-03 湖南博匠信息科技有限公司 嵌入式板卡操作系统备份启动方法及嵌入式系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6459624B1 (en) * 2000-09-01 2002-10-01 Megawin Technology Co., Ltd. Memory structure capable of preventing data loss therein and method for protecting the same
US20120054540A1 (en) * 2010-08-25 2012-03-01 Smartsynch, Inc. System and method for automated unattended recovery for remotely deployed intelligent communication devices
CN103514013A (zh) * 2013-09-11 2014-01-15 深圳市共进电子股份有限公司 一种网关产品flash配置丢失处理方法
CN103530138A (zh) * 2012-07-02 2014-01-22 京信通信技术(广州)有限公司 基于嵌入式linux的文件系统数据保护方法及装置
CN106484567A (zh) * 2016-09-29 2017-03-08 深圳创维数字技术有限公司 一种flash数据备份的使用方法及系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101515259B (zh) * 2009-03-26 2011-05-25 浙江大华技术股份有限公司 一种嵌入式设备配置数据保护方法
CN101546284B (zh) * 2009-04-28 2010-11-03 冠捷科技(武汉)有限公司 一种液晶显示设备数据资料的恢复方法
CN103176859A (zh) * 2011-12-21 2013-06-26 北京普源精电科技有限公司 一种flash数据备份/恢复方法、设备及信号源

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6459624B1 (en) * 2000-09-01 2002-10-01 Megawin Technology Co., Ltd. Memory structure capable of preventing data loss therein and method for protecting the same
US20120054540A1 (en) * 2010-08-25 2012-03-01 Smartsynch, Inc. System and method for automated unattended recovery for remotely deployed intelligent communication devices
CN103530138A (zh) * 2012-07-02 2014-01-22 京信通信技术(广州)有限公司 基于嵌入式linux的文件系统数据保护方法及装置
CN103514013A (zh) * 2013-09-11 2014-01-15 深圳市共进电子股份有限公司 一种网关产品flash配置丢失处理方法
CN106484567A (zh) * 2016-09-29 2017-03-08 深圳创维数字技术有限公司 一种flash数据备份的使用方法及系统

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110287059A (zh) * 2019-05-21 2019-09-27 广东九联科技股份有限公司 一种spi flash的多备份方法
CN110287059B (zh) * 2019-05-21 2023-12-15 广东九联科技股份有限公司 一种spi flash的多备份方法

Also Published As

Publication number Publication date
CN106484567A (zh) 2017-03-08

Similar Documents

Publication Publication Date Title
US9489274B2 (en) System and method for performing efficient failover and virtual machine (VM) migration in virtual desktop infrastructure (VDI)
US8918778B2 (en) Method of fail safe flashing management device and application of the same
TWI471726B (zh) 快取資料與元資料之管理
TWI386846B (zh) 利用共享式非揮發性記憶體初始化多個處理元件之方法、系統及快閃記憶體元件
EP3764237A1 (fr) Procédé et appareil de démarrage de système, dispositif électronique et support d'informations
US9766992B2 (en) Storage device failover
JP6297715B2 (ja) コンピューティングデバイスの初期化トレース
US9239725B2 (en) System and method for installing an OS via a network card supporting PXE
US20120117555A1 (en) Method and system for firmware rollback of a storage device in a storage virtualization environment
US9448889B2 (en) BIOS failover update with service processor
US9448808B2 (en) BIOS update with service processor without serial peripheral interface (SPI) access
US20060036832A1 (en) Virtual computer system and firmware updating method in virtual computer system
JP6201049B2 (ja) 読み出し専用のシステムイメージ内のシステムレベルサービスを更新するためのシステム及び方法
US20160085445A1 (en) Method operating raid system and data storage systems using write command log
JP4712102B2 (ja) 記憶装置、データ処理方法およびデータ処理プログラム
WO2018059565A1 (fr) Procédé et système de copie de sauvegarde de données de mémoire flash
CN114222975A (zh) 使用存储器孔径冲刷顺序的数据保存
TW201301016A (zh) 資料備份與恢復系統及方法
EP3989052B1 (fr) Procédé de fonctionnement de dispositif de stockage et procédé de fonctionnement de système de stockage l'utilisant
US8788800B2 (en) OS processing method, system and non-transitory computer readable storage medium thereof
CN109582332B (zh) 互联网摄像机的系统升级方法及装置
US9619340B1 (en) Disaster recovery on dissimilar hardware
CN115562593A (zh) 一种异常raid成员盘处理方法、装置及介质
JP6070115B2 (ja) 情報処理装置、ｂｍｃおよびｂｉｏｓアップデート方法
CN113950673A (zh) 非易失性存储分区标识符

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17855015

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17855015

Country of ref document: EP

Kind code of ref document: A1