CN112579360A - System backup and restoration method based on kylin operating system embedded platform - Google Patents
System backup and restoration method based on kylin operating system embedded platform Download PDFInfo
- Publication number
- CN112579360A CN112579360A CN202011567349.5A CN202011567349A CN112579360A CN 112579360 A CN112579360 A CN 112579360A CN 202011567349 A CN202011567349 A CN 202011567349A CN 112579360 A CN112579360 A CN 112579360A
- Authority
- CN
- China
- Prior art keywords
- backup
- data
- command
- boot
- setting
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000012545 processing Methods 0.000 claims abstract description 28
- 238000000638 solvent extraction Methods 0.000 claims abstract description 24
- 230000009467 reduction Effects 0.000 claims abstract description 18
- 238000005192 partition Methods 0.000 claims description 62
- 238000011084 recovery Methods 0.000 claims description 30
- 238000011112 process operation Methods 0.000 claims description 3
- 238000012795 verification Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 abstract description 23
- 230000009191 jumping Effects 0.000 description 10
- 230000006870 function Effects 0.000 description 8
- 230000000694 effects Effects 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 2
- 230000006399 behavior Effects 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 239000011449 brick Substances 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
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/1456—Hardware arrangements for backup
-
- 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
Abstract
A system backup and restoration method based on an kylin operating system embedded platform comprises the following steps: setting a backup and reduction information data block; partitioning the system; processing the system crash; restoring the system and processing; and processing the system backup. The system backup and restoration method based on the embedded platform of the kylin operating system has the following advantages that: the kylin embedded system can automatically start the backup system under the condition that the system cannot be started. Ensuring the basic use condition of the equipment; the kylin embedded system can also support the basic function of backup restoration under the condition that the self-supporting storage capacity of the equipment is not large; therefore, the kylin embedded system does not need to manually restart the system to enter a backup reduction environment for backup operation in the system backup process, and the direct system backup function of the equipment is supported.
Description
Technical Field
The invention belongs to the technical field of kylin operating systems, and particularly relates to a system backup and restoration method based on an embedded platform of an kylin operating system.
Background
In the embedded field, the embedded hardware does not have a storage hard disk such as a solid state disk, a mechanical hard disk and the like, and correspondingly replaces a storage device such as emmc/nand/ufs and the like fixed on a mainboard, so that if the system cannot be normally started due to system damage, a client cannot restore the partition of the storage device and reinstall the partition on a machine like taking out the mechanical hard disk. Because the storage of the embedded device is often fixed on the mainboard, once the system is damaged, the device cannot be started, and the device is changed into a brick, the kylin embedded system needs to avoid the condition, and when the system is halted, the backup system can be automatically restarted.
On the desktop system, if a client performs restore/backup operation on the kylin system, the client needs to restart the system first and enter a system restore/backup environment, then copy the system partition to be restored onto the partition to be restored (restore operation), or copy the system partition to be backed up onto the backup partition (backup), and then restart the system into the restored partition (restore) or normal restart (backup). This series of processes often requires three parts to complete: 1. normal system partitioning, 2. system environment to execute restore/backup command, 3. restore/backup partition. Satisfying these three conditions, it must ensure that the capacity of the storage disk is large enough to put down the above 3 partitions. Embedded devices tend to have a small memory capacity, and it is preferable to be able to eliminate unnecessary memory capacity. That is to say, when the kylin embedded version performs backup and restore operations, the system environment support for executing restore/backup commands is not needed, only a simple partition is needed to store corresponding data information, and the partition can be very small and does not exceed 4M at most. While the system environment of the desktop environment that executes the restore/backup commands is typically 500M-2G in size.
On a desktop system, the environment size of a basic system is usually 2G-4G file capacity, while the environment size of an kylin embedded system is usually very small and is within 100M of file capacity. Therefore, if a client performs a backup restore operation on the desktop, the actual time for the client to wait, i.e. the time for copying 2G-4G files, is generally 30-60 minutes, and the time for copying 100M is also 1-2 minutes. Therefore, on the kylin embedded platform, the backup operation can be performed in the background, without affecting the normal system use operation of the user at all, while if the desktop system of 2-4G is backed up in the background, it is not good enough, because the copy of the large file will make the user feel that the system is stuck and stuck for 30-60 minutes.
Based on the three points, it is completely necessary to improve the original backup and restore method under the system in the embedded field, so as to make the user of the kylin embedded system more comfortable to use.
Disclosure of Invention
In order to solve the above problems, the present invention provides a system backup and restore method based on an embedded platform of an kylin operating system, which comprises the following steps:
setting a backup and reduction information data block;
partitioning the system;
processing the system crash;
restoring the system and processing;
and processing the system backup.
Preferably, the setting of the backup and restore information data block includes the steps of:
backing up and restoring the data information block;
executing a backup restoration command on the data information block;
recording the state information of the data information block;
recording a check value of a current backup system partition;
and reserving the check value in a preset format.
Preferably, the partitioning the system comprises the steps of:
partitioning a bootloader of the system;
partitioning the Linux kernel of the system;
partitioning the normal system of the system;
partitioning a recovery _ system of the system;
partitioning the flags _ data of the system.
Preferably, the processing of the system crash comprises the steps of:
collecting the crash starting condition of the system;
setting a next boot status;
checking command in the flags _ data;
determining a boot status state;
judging whether the command is dev _ normal _ boot or not;
if yes, the system is started normally;
if not, the system is started to enter a backup system partition and a reduction operation is executed; and executing the system recovery processing flow operation.
Preferably, the processing of the system restoration comprises the steps of:
setting a system restoration operation;
setting a next boot status;
setting command as dev _ recovery;
restarting the system and checking whether the command is dev _ recovery;
if yes, the system is started normally;
if not, starting the system to enter the backup system partition and preparing to execute the reduction operation;
writing command dev _ normal _ boot into the flags _ data area;
writing current restoration information into the data and flags area;
judging whether to continue using the system;
and if so, restarting the system.
Preferably, the processing the system backup comprises the steps of:
setting system backup operation;
setting command as dev _ backup;
performing backup service process operation;
setting command to dev _ normal _ boot;
writing current backup information into the data and flags area;
and executing the verification operation of the backup file.
The system backup and restoration method based on the embedded platform of the kylin operating system has the following advantages that:
(1) the kylin embedded system can automatically start the backup system under the condition that the system cannot be started. Ensuring the basic use condition of the equipment;
(2) the kylin embedded system can also support the basic function of backup restoration under the condition that the self-supporting storage capacity of the equipment is not large;
(3) in the system backup process, the kylin embedded system does not need to manually restart the system to enter a backup reduction environment for backup operation, and the direct system backup function of the equipment is supported;
(4) the kylin embedded system can normally use the system without waiting for the completion of the backup operation in the system backup process, namely, the background automatic backup function is supported;
(5) in the recovery process of the system, the backup partition of the system which enters the kylin embedded system is still a normal operating system environment, and the use effect of a user is consistent with the normal effect.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic flow diagram of a system backup and restore method based on an embedded platform of an kylin operating system according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings in conjunction with the following detailed description. It should be understood that the description is intended to be exemplary only, and is not intended to limit the scope of the present invention. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present invention.
Referring to fig. 1, in the embodiment of the present application, the present invention provides a system backup and restore method based on an embedded platform of an kylin operating system, where the method includes the steps of:
s1: setting a backup and reduction information data block;
s2: partitioning the system;
s3: processing the system crash;
s4: restoring the system and processing;
s5: and processing the system backup.
In the embodiment of the application, when a system is backed up and restored based on an embedded platform of an kylin operating system, a backup and restoration information data block is firstly set, then the system is partitioned, then the system is halted and processed, then the system is restored and processed, and then the system backup is processed.
In the embodiment of the application, the principle of implementing the system backup restoration method based on the embedded platform of the kylin operating system is to establish two consistent original systems and implement the system backup restoration method through setting of a Linux kernel driver, setting of a partition zone bit and copying of a system backup partition. It implements several scenarios as follows:
when the system is halted, the Linux kernel driver detects the flag bit and detects that the normal system cannot be normally started after detecting that the system is halted, so that the system environment of the backup partition is started, and after the system is successfully started from the backup system partition, a service exists in the background of the backup system to copy the partition file of the backup system on the original system mirror image, so that the operation of restoring the halted system is achieved. When the system recovery operation is finished, the kernel driver is informed to clear the zone bit, so that the system can detect that the normal system is recovered in the next starting/restarting process, and the function of automatic recovery of crash is finished;
when the system is actively restored, a user actively sets restoration operation, when a Linux kernel driver receives a message of a user layer as the system restoration, a mark position of data on a corresponding partition address is started, the system is waited for restarting, the mark position is checked to be already set in the system restarting process, so that normal partition starting is called, the system is started by a backup partition, after the backup partition is started, a service exists in a background of the backup system to copy a partition file of the backup system on an original system mirror image, after the copying is finished, the mark position is cleared, the system is restarted, the next starting process detects that the system mark position is cleared, and the system is started from the normal partition position;
when the system is actively backed up, a user actively sets a reduction operation, when the Linux kernel driver receives a message of a user layer as the system backup, the Linux kernel driver records the backup time to a backup reduction data block, starts a backup service, and a background backs up the local system to a backup partition position. After the backup is completed, the system notifies the user that the backup is completed. Thus, when the user is at the next restore time, the restored system will be the system file backed up this time.
In this embodiment of the present application, the setting of the backup and restore information data block in step S1 includes the steps of:
backing up and restoring the data information block;
executing a backup restoration command on the data information block;
recording the state information of the data information block;
recording a check value of a current backup system partition;
and reserving the check value in a preset format.
In the embodiment of the present application, the specific steps of setting the backup and restore information data block are as follows:
and a-1, backing up and restoring a data information block, namely allocating a Linux data block with the size of 4M for storing the backed-up and restored data, wherein the content of the Linux data block comprises a-2, a-3 and a-4.
Step a-2 command: the command with the size of 32 bytes records the backup and restore state set by the system, and comprises dev _ recovery, dev _ backup, dev _ normal _ boot and the like, wherein dev _ recovery is a command for restoring the device, dev _ backup is a command for backing up the device, and dev _ normal _ boot is a command for normally starting the device. When the system is started, the bootloader firstly checks the information of the bootloader, if the information is dev _ recovery, the system is started from a backup system, and after the system is started, a restoring service process is started to restore the files of the backup system to a normal system partition, if the information is dev _ backup, the system is started on the normal system, and after the system is started, the restoring service process is started to restore the files of the backup system to the backup partition of the system needing to be backed up. If it is dev normal boot, the system will start normally.
Step a-3boot status, a status information flag with a size of 32 bytes, wherein the starting status of the current system is recorded, and the status information flag includes normal _ boot, charge _ boot, protected _ boot, hwerr _ boot, swerr _ boot, unburnt _ boot, etc., the normal _ boot is the normal starting status of the system, the charge _ boot is the starting status of the system in the charging status, the protected _ boot is the starting status of the system which is manually set in the protection status, the hwerr _ boot is the starting status of the system under the premise that the system perceives hardware errors, the swerr _ boot is the starting status of the system which perceives software errors, and the unburnt _ boot is the unknown starting status of the system. When the state is normal _ boot, charge _ boot, protected _ boot and unbow _ boot, the system starts on the normal partition, and when the state is hwerror _ boot, swerror _ boot, the system starts on the backup system partition. And the system starting state has the function of automatic transmission switching, for example, when the system needs to be backed up, the system should ensure to switch from the normal _ boot state to the charge _ boot state, or start under the charge _ boot (namely, a charger or a power supply insertion state), so as to prevent the system of the backup partition from being damaged due to power failure in the system backup process. If the system is in a crash state, the system is in a hwerr _ boot/swerr _ boot state at the moment, the system directly enters a backup system partition, and is restarted after the system is completely backed up, at the moment, the boot status is switched to normal _ boot/charge _ boot, and the system is recovered to be normal. The situation is not exhaustive.
Step a-3data and flags: the data information with the size of 2 Mbytes records the check value of the current backup system partition, the check value of the current starting system partition, the time point of system backup, the reason of system backup (manual description of a client), the logic address information of the whole storage block, the GPT partition table information and the like, and aims to provide information data of related backup reduction inquired and verified by a user client;
step a-4reserved data, fill data with 0xff in hexadecimal.
In the embodiment of the present application, partitioning the system in step S2 includes the steps of:
partitioning a bootloader of the system;
partitioning the Linux kernel of the system;
partitioning the normal system of the system;
partitioning a recovery _ system of the system;
partitioning the flags _ data of the system.
In the embodiment of the present application, the partitioning step of the system is specifically as follows:
a-6, a bootloader partition, which comprises a most basic bootstrap program of the system and collects hardware information to preliminarily determine the current starting state of the system, namely a-3boot status;
and a-7, a Linux kernel partition which comprises a kernel program for starting the hardware by the system, on one hand, the kernel program can verify whether the starting state set by the a-6 is correct, on the other hand, the kernel program can also determine and set the a-3boot status by using the starting information of the hardware of the system. For example: in a-6, the system determines that the starting state is a normal boot, and in the process of starting a-7, the system cannot be started normally by perceiving that the system is caused by video card driving problems, so that the system starting state is set to be a swerror boot. The reason for this is that the system cannot be started normally due to incorrect installation of the video card driver.
a-8, normal _ system partition, when the system is normally started, the partition is used for starting by default, and the operating system environment used by the user is also the partition environment;
a-9, recovering _ system partition, when the system fails to start or the user selects the system to restore, the command of a-2 will be set, so as to start the system environment of the partition by default, and when the restoring operation is completed, the command of a-2 sets the normal _ system of a-8 as the default start of the system.
a-10, a-1 backup recovery data information block, which is the storage position of the minimum 4M data information block.
In this embodiment of the present application, the processing of the system crash in step S3 includes the steps of:
collecting the crash starting condition of the system;
setting a next boot status;
checking command in the flags _ data;
determining a boot status state;
judging whether the command is dev _ normal _ boot or not;
if yes, the system is started normally;
if not, the system is started to enter a backup system partition and a reduction operation is executed;
and executing the system recovery processing flow operation.
In the embodiment of the application, the system crash processing flow comprises the following steps:
b-2, generating a crash problem in the starting process of the system, collecting the crash starting condition of the system, and jumping to b-3;
b-3, setting the next boot status, setting the command as dev _ recovery, and jumping to b-4;
in the process of the b-4 system, checking a command in the flags _ data, determining the boot status state, if the system is normally started and the command is dev _ normal _ boot, jumping to b-5, and if the command is dev _ recovery, jumping to b-6;
b-5, starting the system normally;
b-6, starting the system, entering a backup system partition, and executing a reduction operation;
and b-7, completing the restoration of the system, writing command dev _ normal _ boot into the flags _ data area, writing current restoration information into the data and flags area, and determining whether to continue to use or not by the user at a time point, and jumping to b-6 if continuing to use, or entering normal _ system if restarting the system.
b-8, in the next restarting process, checking the command as dev _ normal _ boot, and finally jumping to b-5 in the starting process, which represents that one-time crash recovery operation is completed.
In this embodiment of the present application, the processing of the system restoration in step S4 includes the steps of:
setting a system restoration operation;
setting a next boot status;
setting command as dev _ recovery;
restarting the system and checking whether the command is dev _ recovery;
if yes, the system is started normally;
if not, starting the system to enter the backup system partition and preparing to execute the reduction operation;
writing command dev _ normal _ boot into the flags _ data area;
writing current restoration information into the data and flags area;
judging whether to continue using the system;
and if so, restarting the system.
In the embodiment of the present application, the system recovery processing flow specifically includes the following steps:
c-2, the user actively sets system recovery operation through any interactive behaviors such as keys, network, touch, mouse, keyboard and the like;
c-3, setting the next boot status, setting the command as dev _ recovery, and jumping to c-4;
c-3 restarting the system and checking that the mark is dev _ recovery, then jumping to c-6, and if the command is dev _ normal _ boot, jumping to c-5;
c-5, starting the system normally;
c-6, starting the system to enter a backup system partition and preparing to execute a reduction operation;
and c-7, completing the restoration of the system, writing command dev _ normal _ boot into the flags _ data area, writing current restoration information into the data and flags area, and determining whether to continue to use by the user, wherein if the system continues to use, the system jumps to c-6, and if the system is restarted, the system enters normal _ system.
c-8, in the next restart process, checking the command as dev _ normal _ boot, and finally jumping to c-5 in the starting process, which represents that one system recovery operation is completed.
In this embodiment of the present application, the processing of the system backup in step S5 includes the steps of:
setting system backup operation;
setting command as dev _ backup;
performing backup service process operation;
setting command to dev _ normal _ boot;
writing current backup information into the data and flags area;
and executing the verification operation of the backup file.
In the embodiment of the present application, the system backup processing flow specifically includes the following steps:
c-2, the user actively sets system backup operation through any interactive behaviors such as keys, network, touch, mouse, keyboard and the like;
and c-3, starting the backup service by the system, actively setting the command to dev _ backup, checking the current state of the system, and if the system boot status is only a normal boot, prompting a user to use a power supply for access so as to ensure that the backup partition is not damaged due to abnormal power failure in the system backup process.
c-4 when the backup service process is finished, setting the command dev _ normal _ boot actively. And if the backup process is abnormal, re-backing up until the backup is successful, writing current backup information into the data and flags area, checking the backup file and the like.
c-5, and the next restoration operation is carried out, if the user sets the restoration operation, the active jump is carried out to the system restoration processing flow. But the system restored at this time is the system backed up this time.
The flow of the backup restore operation is described above, as well as the partition status of the device. How the backup restore is handled needs to be described below.
The operating system will divide a block of storage space into several partitions, as described in the a-5 system partition state, and when the system is performing backup and restore operations, it will also use the partition information to perform operations such as copying data. The backup and restore operations mainly include implementations such as blk _ read, blk _ write, blk _ clear, and as is often the case, it implements a read-write clear operation for data of a certain segment size at the address of a partition. At this time, the reading and writing and the clearing of the partition can be carried out according to the partition address defined by the a-5.
For example, assume that the partition addresses of normal _ system are on 0x1a000000-0x5a000000 and the partition addresses of recovery are on 0x5a000000-0x9a 000000. In the system backup process, actually, the data with the size of 0x40000000 is written by blk _ read 0x1a000000-0x5a000000 and 0x5a000000-0x9a000000 by blk _ write, and if necessary, the data with the size of 0x5a000000-0x9a000000 needs to be cleared once first.
For example, assume that the user manually sets the restore operation, and the address data of a-2command is stored in 0x9a000000-0x9a000020, i.e. the command set to dev _ recovery is performed by the data of 32 bytes whose ble _ write starts at 0x9a 000000. If necessary, after the ble _ write is finished, the data of the first 32 bytes is read by the ble _ read to make a confirmation, which guarantees that the command has been successfully set.
The system backup and restoration method based on the embedded platform of the kylin operating system has the following advantages that:
(1) the kylin embedded system can automatically start the backup system under the condition that the system cannot be started. Ensuring the basic use condition of the equipment;
(2) the kylin embedded system can also support the basic function of backup restoration under the condition that the self-supporting storage capacity of the equipment is not large;
(3) in the system backup process, the kylin embedded system does not need to manually restart the system to enter a backup reduction environment for backup operation, and the direct system backup function of the equipment is supported;
(4) the kylin embedded system can normally use the system without waiting for the completion of the backup operation in the system backup process, namely, the background automatic backup function is supported;
(5) in the recovery process of the system, the backup partition of the system which enters the kylin embedded system is still a normal operating system environment, and the use effect of a user is consistent with the normal effect.
It is to be understood that the above-described embodiments of the present invention are merely illustrative of or explaining the principles of the invention and are not to be construed as limiting the invention. Therefore, any modification, equivalent replacement, improvement and the like made without departing from the spirit and scope of the present invention should be included in the protection scope of the present invention. Further, it is intended that the appended claims cover all such variations and modifications as fall within the scope and boundaries of the appended claims or the equivalents of such scope and boundaries.
Claims (6)
1. A system backup and restoration method based on an kylin operating system embedded platform is characterized by comprising the following steps:
setting a backup and reduction information data block;
partitioning the system;
processing the system crash;
restoring the system and processing;
and processing the system backup.
2. The method for system backup and restore based on the embedded platform of kylin operating system as claimed in claim 1, wherein said setting the backup and restore information data block comprises the steps of:
backing up and restoring the data information block;
executing a backup restoration command on the data information block;
recording the state information of the data information block;
recording a check value of a current backup system partition;
and reserving the check value in a preset format.
3. The method for restoring system backup based on embedded platform of kylin operating system as claimed in claim 1, wherein said partitioning the system comprises the steps of:
partitioning a bootloader of the system;
partitioning the Linux kernel of the system;
partitioning the normal system of the system;
partitioning a recovery _ system of the system;
partitioning the flags _ data of the system.
4. The method for restoring system backup based on embedded platform of kylin operating system as claimed in claim 1, wherein said processing of system crash comprises the steps of:
collecting the crash starting condition of the system;
setting a next boot status;
checking command in the flags _ data;
determining a boot status state;
judging whether the command is dev _ normal _ boot or not;
if yes, the system is started normally;
if not, the system is started to enter a backup system partition and a reduction operation is executed;
and executing the system recovery processing flow operation.
5. The method for restoring system backup based on embedded platform of kylin operating system as claimed in claim 1, wherein said processing said system restore comprises the steps of:
setting a system restoration operation;
setting a next boot status;
setting command as dev _ recovery;
restarting the system and checking whether the command is dev _ recovery;
if yes, the system is started normally;
if not, starting the system to enter the backup system partition and preparing to execute the reduction operation;
writing command dev _ normal _ boot into the flags _ data area;
writing current restoration information into the data and flags area;
judging whether to continue using the system;
and if so, restarting the system.
6. The method for restoring system backup based on embedded platform of kylin operating system as claimed in claim 1, wherein said processing said system backup comprises the steps of:
setting system backup operation;
setting command as dev _ backup;
performing backup service process operation;
setting command to dev _ normal _ boot;
writing current backup information into the data and flags area;
and executing the verification operation of the backup file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011567349.5A CN112579360A (en) | 2020-12-25 | 2020-12-25 | System backup and restoration method based on kylin operating system embedded platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011567349.5A CN112579360A (en) | 2020-12-25 | 2020-12-25 | System backup and restoration method based on kylin operating system embedded platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112579360A true CN112579360A (en) | 2021-03-30 |
Family
ID=75139811
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011567349.5A Pending CN112579360A (en) | 2020-12-25 | 2020-12-25 | System backup and restoration method based on kylin operating system embedded platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112579360A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20050021736A (en) * | 2003-08-25 | 2005-03-07 | 남승리 | Method for backup and restorating computer system, and the recording medium wihich records the program for the backup and restoratin |
| CN102541685A (en) * | 2011-11-16 | 2012-07-04 | 中标软件有限公司 | Linux system backup method and Linux system repair method |
| CN103473067A (en) * | 2013-09-23 | 2013-12-25 | 福建三元达软件有限公司 | Embedded Linux partitioning and data recovery method, embedded Linux partitioning and data recovery system and system development method |
| CN104182301A (en) * | 2014-08-26 | 2014-12-03 | 山东超越数控电子有限公司 | Backup method and restore method for Kylin operating system |
| CN107193506A (en) * | 2017-06-22 | 2017-09-22 | 山东超越数控电子有限公司 | A kind of implementation method for kylin system root partition dilatation of getting the bid |
| CN108491292A (en) * | 2018-03-07 | 2018-09-04 | 天津麒麟信息技术有限公司 | A kind of backup and reduction method based on platform of soaring |
| CN109101366A (en) * | 2018-08-10 | 2018-12-28 | 郑州云海信息技术有限公司 | A kind of method and system of operating system backup and reduction based on Linux |
| CN109189485A (en) * | 2018-08-08 | 2019-01-11 | 烽火通信科技股份有限公司 | A kind of system starting management of embedded device, operating system configuration method |
| CN110968457A (en) * | 2019-10-28 | 2020-04-07 | 湖南麒麟信安科技有限公司 | Backup restoration method, system and medium for Linux operating system |
-
2020
- 2020-12-25 CN CN202011567349.5A patent/CN112579360A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20050021736A (en) * | 2003-08-25 | 2005-03-07 | 남승리 | Method for backup and restorating computer system, and the recording medium wihich records the program for the backup and restoratin |
| CN102541685A (en) * | 2011-11-16 | 2012-07-04 | 中标软件有限公司 | Linux system backup method and Linux system repair method |
| CN103473067A (en) * | 2013-09-23 | 2013-12-25 | 福建三元达软件有限公司 | Embedded Linux partitioning and data recovery method, embedded Linux partitioning and data recovery system and system development method |
| CN104182301A (en) * | 2014-08-26 | 2014-12-03 | 山东超越数控电子有限公司 | Backup method and restore method for Kylin operating system |
| CN107193506A (en) * | 2017-06-22 | 2017-09-22 | 山东超越数控电子有限公司 | A kind of implementation method for kylin system root partition dilatation of getting the bid |
| CN108491292A (en) * | 2018-03-07 | 2018-09-04 | 天津麒麟信息技术有限公司 | A kind of backup and reduction method based on platform of soaring |
| CN109189485A (en) * | 2018-08-08 | 2019-01-11 | 烽火通信科技股份有限公司 | A kind of system starting management of embedded device, operating system configuration method |
| CN109101366A (en) * | 2018-08-10 | 2018-12-28 | 郑州云海信息技术有限公司 | A kind of method and system of operating system backup and reduction based on Linux |
| CN110968457A (en) * | 2019-10-28 | 2020-04-07 | 湖南麒麟信安科技有限公司 | Backup restoration method, system and medium for Linux operating system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6807630B2 (en) | Method for fast reinitialization wherein a saved system image of an operating system is transferred into a primary memory from a secondary memory | |
| JP4371771B2 (en) | Power management block used in non-volatile memory system | |
| US6205558B1 (en) | Recovery of file systems after modification failure | |
| KR100843543B1 (en) | System comprising flash memory device and data recovery method thereof | |
| US8341386B2 (en) | Method for updating basic input/output system and method for repairing thereof | |
| US7724643B2 (en) | Recovery of duplex data system after power failure | |
| US7558904B2 (en) | Controller, data memory system, data rewriting method, and computer program product | |
| CN107918568B (en) | Method for preventing Linux system from failing to restart | |
| EP2353081A2 (en) | Managing cache data and metadata | |
| CN101667128B (en) | Method for updating and repairing basic input and output system | |
| CN102298545A (en) | System startup boot processing method and device | |
| US11960748B2 (en) | SSD supporting read-only mode after PLP backup failure | |
| US11294779B2 (en) | Memory device providing fast data recovery | |
| CN111124760B (en) | Uboot-based embedded equipment starting method and apparatus | |
| CN113190256A (en) | Upgrading method, device and equipment | |
| CN114756355B (en) | Method and device for automatically and quickly recovering process of computer operating system | |
| CN111240903A (en) | Data recovery method and related equipment | |
| CN115562593A (en) | Abnormal RAID member disk processing method, device and medium | |
| CN112579360A (en) | System backup and restoration method based on kylin operating system embedded platform | |
| CN108804033B (en) | Full-disk scanning method and device based on power-off continuation, computer equipment and medium | |
| JP2016200861A (en) | Semiconductor device and storage medium control method | |
| CN116204353B (en) | Recovery and restoration method, device and equipment of vehicle-mounted system and storage medium | |
| US20030237021A1 (en) | Automatic restoration of software applications in a mobile computing device | |
| JPH07201190A (en) | Nonvolatile memory file system | |
| CN117931091A (en) | Abnormal power failure processing method, device, equipment, medium and product |
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 |