Clonezilla-based openEuler system rapid backup and restoration method, system, equipment and device

Abstract

The invention discloses a quick backup and restoration method, system, equipment and device for an openEuler system based on Clonezilla, and relates to the technical field of operating system backup. The method comprises the following steps: manufacturing a Clonezilla startup disk and an ext4 format storage device; the method comprises the following steps: starting target equipment through a boot disk, selecting a local storage mode and a backup strategy, and performing partition-level or full-disk compression backup on an openEuler system under an enterprise-level server which is developed as the dominant of China and is provided with a Peng processor, all software in the system and an environment required for installing the software; generating a bootable system mirror image ISO file; according to the method, the problems of poor compatibility, low efficiency and incomplete environment restoration of a traditional Linux backup method under a domestic platform are solved through a customized mirror image processing flow, hardware instruction set adaptation and a system environment deep capture technology, and the response speed of system deployment and disaster recovery is improved.

Description

TECHNICAL FIELD

[0001] The application relates to the technical field of system backup, in particular to an openEuler system fast backup and restoration method, system, device and apparatus based on Clonezilla. BACKGROUND

[0002] With the popularity of domestic servers, operating systems and databases, servers based on Kunpeng processors (ARM64 architecture) and openEuler systems are widely used in various industries. In the process of server operation and maintenance, system backup, fault restoration and batch deployment are core requirements.

[0003] The traditional backup method has the following problems: Poor adaptability: general backup tools are not optimized for Kunpeng architecture and openEuler system, and compatibility problems are prone to occur; Low efficiency: manual backup needs to be operated one by one, and server deployment takes a long time; Complex operation: manual configuration of partitions, compression parameters, etc. is required, and high skills are required for operation and maintenance personnel; Single deployment method: lack of flexible deployment means combining local and remote.

[0004] In view of the above problems, an efficient and automated backup method is needed to adapt to Kunpeng processors, openEuler systems, all software in the system, and the installation environment and drivers required by the software. SUMMARY

[0005] In order to solve the problems of poor adaptability, low efficiency and complex operation of the traditional backup method on Kunpeng architecture and openEuler system, the application provides an openEuler system fast backup and restoration method, system, device and apparatus based on Clonezilla.

[0006] The technical scheme adopted by the application is: an openEuler system fast backup and restoration method based on Clonezilla, comprising the following steps: Step S1: complete the preparation work of backup: including hardware environment, software tools and adapted startup disk and storage disk; Step S2: start the target device with openEuler system through the startup disk, enter the customized Clonezilla operation environment, select the storage device and image storage path, and generate the compressed image file of the openEuler system on the target device through the selection of backup strategy; The customized Clonezilla operating environment includes: a partition table analysis tool optimized for the openEuler kernel, supporting mixed backup of LVM logical volumes and physical volumes; a parallel computing library based on the NEON instruction set of the Kunpeng processor, used to accelerate image compression. Step S3: Convert the compressed image file to a bootable ISO image file. Step S4: Boot through the startup disk or mount the ISO image file remotely through BMC to complete system restoration.

[0007] Further, the hardware environment in step S1 includes a Kunpeng processor, and the software tools include Clonezilla live-arm64 image, Rufus software or dd instruction.

[0008] Further, the steps of making a startup disk are as follows: S11, modify the kernel parameters of Clonezilla live-arm64 image, add openEuler_compat=1 identifier, and enable the compatibility mode for openEuler system call interface; S12, format the specified parameters of the storage disk through the mkfs.ext4 command to adapt to the user mode application compatibility requirements of the Kunpeng processor.

[0009] Further, the storage device in step S2 is a formatted storage disk, and the image storage path is bound to the volume label identifier through the blkid tool of the openEuler system to ensure the unique identification of the storage device.

[0010] Further, in step S2, the backup strategy is selected to perform compressed backup of the entire disk or specified partition of the openEuler system of the target device; If it is a full-disk backup: call the modified ocs-sr script, first capture the LVM logical volume structure through the pvdisplay and lvdisplay commands, and then perform sector-level compressed backup on the physical disk; If it is a partition backup: after mounting the target partition through the mount command, run the openEuler exclusive environment capture tool env-capture to scan and record the dependency library paths / usr / lib, / usr / local / lib and kernel module configuration / lib / modules of the system software, and generate the environment dependency list env-deps.json.

[0011] Further, the ISO image file generated in step S3 includes: Adapt the UEFI boot program of openEuler and the environment-dependent automatic installation script env-restore.sh to rebuild the software running environment during restoration.

[0012] Further, the system restoration of step S4 includes: S41, booting through the startup disk or remotely mounting the ISO image file through BMC; S42, automatically matching the LVM logical volume structure of the target disk, and if the capacity of the target disk is different from that of the source disk, dynamically adjusting the logical volume size through the lvresize tool; S43, executing env-restore.sh, installing missing dependent libraries based on env-deps.json, and repairing system services of openEuler through the dnf tool; S44, automatically restarting or shutting down after completion.

[0013] An openEuler system fast backup and restoration system based on Clonezilla, comprising: A device preparation module for making a Clonezilla startup disk and formatting a storage device; A startup module for booting the target device into a customized Clonezilla operating environment; An image generation module for performing system backup and generating an ISO format startable image file; A recovery module for loading the image file through the startup disk or BMC and completing system restoration.

[0014] A computer device comprising a memory, a processor, and a computer program stored on the memory, wherein the processor executes the computer program to implement the steps of the method.

[0015] A storage device having a computer program / instruction stored thereon, which is executed by a processor to implement the steps of the method.

[0016] The present application has the following beneficial effects over the prior art: 1) Strong adaptability: optimized for Kunpeng processors and openEuler systems, solving compatibility problems; 2) High efficiency and automation: simplified operation process through Clonezilla interactive interface, supporting batch image making and deployment, saving maintenance time; 3) Flexible deployment: supporting local U disk startup and remote BMC mounting, adapting to different maintenance scenarios; 4) High reliability: ensuring consistency of backup and restoration through image verification mechanism, reducing data loss risk. BRIEF DESCRIPTION OF DRAWINGS

[0017] The following description, in conjunction with the accompanying drawings, further illustrates this application: Figure 1 A flowchart illustrating the creation of a system compressed file provided in this application embodiment; Figure 2 A flowchart illustrating the creation process of an ISO image file provided in this application embodiment; Figure 3 A flowchart of ISO restoration using USB flash drive boot method provided for embodiments of this application; Figure 4 This application provides an ISO restoration flowchart using the BMC remote mounting method as an example. Figure 5 This is a structural block diagram of a computer device provided in an embodiment of this application. Detailed Implementation

[0018] like Figures 1 to 5 As shown, this application provides a fast backup and restore method for the openEuler system based on Clonezilla, including the following steps: Step S1: Complete the backup preparation work, create a Clonezilla boot disk adapted to the ARM64 architecture, integrate the openEuler system-specific driver module (including the power management driver and PCIe device driver for the Kunpeng processor), and format the storage device to ext4 format to store the backup image. Step S2: Boot the target device running the openEuler system via the boot disk and enter the customized Clonezilla operating environment. The operating environment includes: a partition table parsing tool optimized for the openEuler kernel, which supports hybrid backup of LVM logical volumes and physical volumes; and a parallel computing library based on the Kunpeng processor NEON instruction set to accelerate image compression. Select the local storage mode and specify the ext4 formatted storage device as the mirror storage path. The mirror storage path is bound to the volume label identifier through the blkid tool of the openEuler system to ensure the unique identification of the storage device. Select a backup strategy to perform a full disk or specified partition compressed backup of the openEuler system on the target device, generating a compressed image file; Step S3: Convert the backed-up compressed image file into a bootable ISO image file; Step S4: Load the ISO image file by booting from the boot disk or mounting it via BMC to complete the system restore.

[0019] The hardware environment in step S1 includes a Kunpeng processor server, at least two U disks (for starting and storing images respectively); the software tools include a Clonezilla live-arm64 image, Rufus software or a dd instruction; and the storage medium processing needs to format the starting U disk as FAT32 and the storage U disk as ext4.

[0020] The preparation of the starting disk in step S1 includes: S11, modifying the kernel parameters of the Clonezilla live-arm64 image (Clonezilla starting disk adapted to ARM64 architecture), adding an openEuler_compat=1 identifier, and enabling the compatibility mode for openEuler system call interface; S12, formatting the specified parameters of the storage device through the mkfs.ext4 command, adapting to the user mode application compatibility requirements of the Kunpeng processor; The specified parameters of the storage device formatted through the mkfs.ext4 command include: (1) -L volume label: set a custom volume label (bound with blkid to achieve unique identification); (2) -b block size: set to a block size compatible with ARM64 architecture (such as 4096 bytes) to ensure the read-write efficiency of the Kunpeng processor user mode application to the storage device; (3) -i inode size: inode allocation strategy optimized for ARM64 architecture to avoid file system compatibility problems caused by architecture differences (4) -o data=writeback data mode: enable asynchronous write-back mode to reduce log synchronization delay and improve Kunpeng multi-core concurrent write performance.

[0021] The partition table analysis tool in step S2 is a partition table analysis tool optimized for the openEuler kernel, based on the original Clonezilla tool modification, specially adapted to the partition structure of the openEuler kernel (especially the LVM logical volume management feature), solving the problem of incomplete recognition of domestic system partitions by general tools.

[0022] The principle of implementing hybrid backup using the partition table analysis tool is as follows: ① First, capture the hierarchical structure of the LVM logical volume (such as volume group, logical volume size, mount point, etc.) through the pvdisplay (physical volume information query) and lvdisplay (logical volume information query) commands; ② Then, combine the sector-level data of the physical disk to associate the logical volume structure information with the original data of the physical volume for backup, ensuring that the physical disk data can be restored and the logical structure of the LVM logical volume can be rebuilt during restoration.

[0023] The volume label identifier in step S2 is a custom label for the storage device, used to uniquely identify the storage device, and can be customized. The phrase "binding the volume label identifier using the blkid tool of the openEuler system" in step S2 means: ①The blkid tool is used to obtain a device's unique identifier (such as a UUID); ② The volume label is a custom label that is defined when formatting the storage device (e.g., mkfs.ext4 -L volume label name). Together with the UUID, it ensures that the storage device is uniquely identified during backup / restore, avoiding path errors caused by changes in the device name (e.g., / dev / sdb).

[0024] The compressed backup in step S3 includes the following operations: S31, If ​​it is a full disk backup: call the modified ocs-sr script (the core script of Clonezilla for disk cloning and backup), first capture the LVM logical volume structure through the pvdisplay and lvdisplay commands, and then perform sector-level compression backup of the physical disk. Among them, ocs-sr is the core backup script of Clonezilla. The modifications are mainly aimed at the LVM features of openEuler and the adaptation to the Kunpeng architecture, specifically including: (1) Add LVM structure capture logic: Before backup, automatically call the pvdisplay and lvdisplay commands to parse and record the structure information of LVM logical volumes (such as volume groups, logical volume layouts, and mount relationships), solving the problem that the original script could not recognize LVM logical volumes; (2) Adapting to openEuler system calls: Combine the openEuler_compat=1 flag added when creating the boot disk, modify the logic related to the system call interface in the script to ensure compatibility with the openEuler kernel; (3) Integration of NEON instruction set acceleration: During the sector-level compression backup stage, the parallel computing library based on the Kunpeng NEON instruction set is called to improve compression efficiency.

[0025] S32, if it is a partition backup: after mounting the target partition using the mount command, run the openEuler-specific environment capture tool (env-capture) to scan and record the dependency library paths ( / usr / lib, / usr / local / lib) and kernel module configurations ( / lib / modules) of the software in the system, and generate an environment dependency list (env-deps.json). S33, the compression algorithm adopts parallel GZIP (1st level compression) accelerated by NEON instruction set, data stream is split by multi-threading, and the compression efficiency is improved by more than 30% by using the SIMD instruction of the Kunpeng processor.

[0026] The ISO image file generated in step S3 includes: The UEFI boot program adapted to openEuler (used to replace the default GRUB configuration of Clonezilla: grub2-efi-arm64); The environment-dependent automatic installation script (env-restore.sh) is used to restore the software running environment.

[0027] The system restoration of step S4 includes: S41, booting through a U disk or mounting an ISO image file remotely through BMC; S42, automatically matching the LVM logical volume structure of the target disk, and if the capacity of the target disk is different from that of the source disk, dynamically adjusting the size of the logical volume through the lvresize tool; S43, executing env-restore.sh, installing missing dependent libraries based on env-deps.json, and repairing system services specific to openEuler through the dnf tool; S44, automatically restarting or shutting down after completion.

[0028] The system services specific to openEuler in step S43 mainly include hardware adaptation services based on the Kunpeng architecture, such as: ① Kunpeng processor power management service (kunpeng-power.service); ② PCIe device driver service (driver management for domestic server hardware); ③ openEuler exclusive package management service (dnf related background service); ④ Kernel module loading service (related to the Kunpeng optimized modules under the / lib / modules path).

[0029] The traditional method only backs up the static files of the file system, ignoring the dependency relationship of the service, the startup configuration and the binding information with the hardware (such as the adaptation parameters of the driver with the Kunpeng processor), resulting in the failure of the service to start after restoration. The present application calls the dnf tool through env-restore.sh and repairs the service dependency and configuration based on env-deps.json, solving the above problems.

[0030] The present application develops a logical volume structure recognition and dynamic adjustment technology for the LVM logical volume characteristics of openEuler, breaking through the limitation that the capacity of the target disk must be greater than or equal to that of the source disk. Wherein the logical volume structure identification and dynamic adjustment technology is not only embodied in step S31 (capturing LVM structure through pvdisplay / lvdisplay during full disk backup), but also more core in step S42 (automatically matching the LVM logical volume structure of the target disk, and dynamically adjusting the size through the lvresize tool during restoration) The logical volume structure identification principle is: by analyzing the LVM metadata (such as volume group descriptor, logical volume mapping table), the "logical topology" of the source disk LVM structure is established, compared with the prior art which relies on static partition table, the present application is optimized for the LVM dynamic management characteristics of openEuler, and can identify complex structures such as nested logical volumes and snapshot volumes.

[0031] The logical volume structure dynamic adjustment principle is: combined with the target disk capacity, the adjustment ratio is automatically calculated, and the lvresize tool is used to realize lossless adjustment of the logical volume size (including file system expansion / shrink), which breaks through the limitation that the target disk capacity must be greater than or equal to the source disk, which is an improvement over traditional static cloning.

[0032] And the environment-dependent capture and restoration mechanism is added, not only the file system is backed up, but also the software package version, repository configuration and kernel module are associated, solving the problem of "system can start but software is not available" after general method restoration.

[0033] Based on the hardware characteristics (NEON instruction set, multi-core architecture) of Kunpeng processor, the compression algorithm is optimized, and higher parallel efficiency than tar is realized (the actual test backup speed is improved by 40%); The principle of the above-mentioned optimized compression algorithm can refer to step S33, specifically: (1) NEON instruction set acceleration: using the NEON SIMD (Single Instruction Multiple Data) instruction set of Kunpeng processor, the compressed data stream is split into multiple sub-streams, and the compression operation is performed through multi-thread parallel processing (each thread corresponds to a NEON processing unit); (2) Parallel GZIP optimization: using level 1 compression level (balancing speed and compression rate), combined with the multi-core architecture of Kunpeng, the compression task is distributed to multiple cores to avoid single-core bottleneck; (3) Compared with the single-thread compression or inefficient parallel of tar, this optimization combines hardware instruction-level parallelism and multi-core scheduling, and the actual test improves the backup speed by more than 40%.

[0034] For the UEFI boot process of openEuler (different from the GRUB configuration of traditional Linux), the boot image generation logic is customized to ensure that the remote management (BMC) of domestic servers is supported after restoration, and this generation logic is mainly embodied in step S3 (generating an ISO image), which specifically includes: (1) Replace the UEFI bootloader: Replace the default GRUB configuration of Clonezilla with grub2-efi-arm64 (adapted to the UEFI boot process of openEuler) to ensure compatibility with the UEFI firmware of domestic servers; (2) Integrated BMC boot support: Pre-configure the boot parameters required for remote BMC management (such as remote console adaptation) in the ISO image to ensure that the server can be recognized by BMC and remotely started after restoration; (3) Bind boot environment dependencies: Associate env-restore.sh with the bootloader to ensure that system services are repaired before startup during restoration, thus avoiding boot failure due to missing services.

[0035] This application has the following two major innovations: 1) Hardware-software integrated adaptation: By modifying Clonezilla kernel parameters, the backup tool can directly recognize the openEuler system call interface, avoiding backup interruptions caused by API differences between domestic systems and general Linux; 2) Dynamic environment reconstruction: The env-capture tool was created and combined with openEuler's DNF package manager database to achieve automatic completion of software dependencies, which solves the shortcomings of traditional methods that only back up files and ignore dependencies.

[0036] This application also proposes a fast backup and restore system for the openEuler system based on Clonezilla, including: Device preparation module: used to create Clonezilla boot disks and format ext4 storage devices; Startup module: Guides the target device into the Clonezilla operating environment; Image generation module: Performs system backup and generates a bootable ISO image; Recovery module: Loads the image via boot disk or BMC and completes system restoration.

[0037] Backup configuration module: Select storage mode, backup range, and compression parameters; Backup configuration module supports: Full disk backup (including / boot and / partitions) or backup of specified partitions; Selection of parallel GZIP compression levels; Mirror encryption and integrity verification switch.

[0038] The recovery module is compatible with ARM64 architecture and UEFI boot mode, and supports media-free restoration by remotely mounting image files via BMC.

[0039] The application will be further described in detail below in conjunction with the drawings and specific embodiments.

[0040] The hardware environment of the embodiment is an ARM64 architecture server with Kunpeng processor, installed with openEuler-20.03-LTS-SP3-everything-aarch64 system; the software environment includes Clonezilla-live-2.6.6-11-arm64.iso, Rufus3.18 (USB startup disk making tool), and Ubuntu20.04 (used for formatting U disk).

[0041] Step S1: Preparation Hardware preparation: the server is equipped with Kunpeng processor, 128 GB memory, and 2 TB SSD system disk; two U disks (8 GB for starting and 64 GB for storing image files).

[0042] Software preparation: download Clonezilla image: http: / / free.nchc.org.tw / clonezilla-live / experimental / arm / 2.6.6-11 / ; Install Rufus tool (Windows environment).

[0043] Storage medium processing: open Rufus, select 8 GB U disk, load Clonezilla image, set partition type as GPT, file system as Large FAT32, and click “start” to make a startup disk; Format storage U disk: insert 64 GB U disk into Ubuntu system and execute: sudo fdisk –l #identify U disk device (such as / dev / sdb); sudo umount / dev / sdb #unmount; sudo mkfs.ext4 / dev / sdb #format as ext4.

[0044] Step S2: Make system compression file ①Insert the startup U disk into the server, power on and enter BIOS, and set the U disk as the first startup item; ②Select “Clonezilla live (Default settings, VGA 800x600)” to enter the interactive interface; ③Select in turn: start_Clonezilla→device-image→local_dev; ④ Insert the storage U disk and press Enter to detect the device. Select / dev / sdb as the storage path, and then use the Tab key to select Done. Select the mode: Beginne mode (additional configuration options are configured by default); Select the target hard disk ( / dev / sda) → compression level 1 (parallel GZIP) → skip file system check (sfsck) → enable image verification → no encryption (senc) → select automatic shutdown after backup is complete; Start the automated backup and wait for the backup to complete. After completion, a folder with the name you just named will appear in the external U disk, and the relevant content of the backup will be in it.

[0045] Step S3: Create an ISO image file: Restart the server and re-enter the Clonezilla interactive interface. Repeat steps ①-④ in step S2. Select "recovery-iso-zip" → automatically identify the image file generated in step S2; Select the "recovery-iso-zip" option because there are many options in this step, including savedisk in step S2. The reason for selecting this option is that this option is "to make a compressed file into an iso file". After selecting, select the image to be integrated backup. Clonezilla will generally automatically identify the compressed file completed in the first step (such as "2025-7-25-01-img"); Specify the target device name as / dev / sda (consistent with the source hard disk) → select the output format as ISO; Confirm the parameters to generate an ISO image file (stored in a 64GB U disk, named "openEuler-deploy.iso").

[0046] Step S4: System deployment: U disk startup mode: Use Rufus to write "openEuler-deploy.iso" to the third U disk (32GB), set the partition type to MBR, and the target system type to UEFI; insert the third U disk into the server to be deployed; Enter BIOS and select U disk startup; Confirm the restore path ( / dev / sda) and image file in the Clonezilla interface, and input "y" to start restoration; BMC mounting mode: Log in to the server BMC management interface, enter "Remote Control" → "Virtual Media", and mount "openEuler-deploy.iso"; Set the BMC boot priority to "Virtual CD / DVD", and restart the server; The subsequent steps are consistent with the restoration method of the U disk starting mode, and the remote deployment is completed.

[0047] Figure 5 A structural block diagram of a computer device according to an embodiment of the present application is shown. As shown in FIG. 5, the computer device includes a memory and a processor, and the memory stores instructions executable on the processor. The processor implements the method in the above embodiment when executing the instructions. The number of the memory and the processor can be one or more. The computer device is intended to represent various forms of digital computers, such as a laptop computer, a desktop computer, a workstation, a personal digital assistant, a server, a blade server, a mainframe computer, and other suitable computers. The computer device can also represent various forms of mobile devices, such as a personal digital processing, a cellular phone, a smart phone, a wearable device, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not intended to limit the implementations of the present application described and / or claimed herein.

[0048] The computer device can also include a communication interface for communicating with external devices, transmitting and receiving data. Various devices are connected to each other by different buses, and can be installed on a common mainboard or in other ways as needed. The processor can process instructions executed in the computer device, including instructions stored in the memory or memory to display GUI on external input / output devices (such as a display device coupled to the interface) to display graphical information. In other embodiments, multiple processors and / or multiple buses can be used with multiple memories and multiple storage devices, if necessary. Similarly, multiple electronic devices can be connected, each providing part of the necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 In the figure, only one thick line is used, but it does not mean that there is only one bus or one type of bus.

[0049] Optionally, in a specific implementation, if the memory, the processor and the communication interface are integrated on a chip, the memory, the processor and the communication interface can communicate with each other through an internal interface.

[0050] It should be appreciated that the above processor can be a central processing unit (CPU), and can also be other general-purpose processors, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc. It should be noted that the processor can be a processor supporting an advanced RISC machine (ARM) architecture.

[0051] The embodiments of the present application provide a storage device or a computer readable storage medium (such as the memory described above), which stores computer instructions, and the program is executed by a processor to implement the method provided in the embodiments of the present application.

[0052] Optionally, the memory can include a program storage area and a data storage area, wherein the program storage area can store an operating system and at least one application required by a function; and the data storage area can store data created according to the use of the mapping computer device, etc. In addition, the memory can include a high-speed random access memory, and can also include a non-transient memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transient solid-state memory device. In some embodiments, the memory can optionally include a memory remotely arranged relative to the processor, and these remote memories can be connected to the mapping computer device through a network. Examples of the above network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0053] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the above embodiments, or make equivalent replacement for part or all of the technical features thereof; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for rapid backup and restore of the openEuler system based on Clonezilla, characterized in that: Includes the following steps: Step S1: Complete the backup preparation work: including hardware environment, software tools, and compatible boot disk and storage disk; Step S2: Boot the target device running the openEuler system from the boot disk, enter the customized Clonezilla operating environment, select the storage device and image storage path, and generate a compressed image file of the openEuler system on the target device by selecting a backup strategy; The customized Clonezilla operating environment includes: a partition table parsing tool optimized for the openEuler kernel, supporting hybrid backup of LVM logical volumes and physical volumes; and a parallel computing library based on the Kunpeng processor NEON instruction set for accelerating image compression. Step S3: Convert the compressed image file into a bootable ISO image file; Step S4: Boot from the boot disk or remotely mount the ISO image file using BMC to complete the system restore.

2. The method for rapid backup and restore of the openEuler system based on Clonezilla according to claim 1, characterized in that: The hardware environment in step S1 includes the Kunpeng processor, and the software tools include the Clonezilla live-arm64 image, Rufus software, or dd instructions.

3. The method for rapid backup and restore of the openEuler system based on Clonezilla according to claim 2, characterized in that: The steps to create a bootable disk are as follows: S11 modifies the kernel parameters of the Clonezilla live-arm64 image by adding the openEuler_compat=1 flag to enable compatibility mode for the openEuler system call interface; S12 uses the mkfs.ext4 command to format the storage disk with specified parameters, adapting to the user-space application compatibility requirements of the Kunpeng processor.

4. The method for rapid backup and restore of the openEuler system based on Clonezilla according to claim 3, characterized in that: The storage device in step S2 is a formatted storage disk. The mirror storage path is bound to the volume label identifier through the blkid tool of the openEuler system to ensure the unique identification of the storage device.

5. The method for rapid backup and restore of the openEuler system based on Clonezilla according to claim 1, characterized in that: In step S2, select a backup strategy to perform a full disk or specified partition compressed backup of the openEuler system on the target device; For full disk backup: call the modified ocs-sr script, first capture the LVM logical volume structure using the pvdisplay and lvdisplay commands, and then perform sector-level compression backup of the physical disk; For partition backup: After mounting the target partition using the mount command, run the openEuler-specific environment capture tool env-capture to scan and record the dependency library paths of software in the system, such as / usr / lib, / usr / local / lib, and kernel module configuration / lib / modules, and generate the environment dependency list env-deps.json.

6. The method for rapid backup and restore of the openEuler system based on Clonezilla according to claim 5, characterized in that: The ISO image file generated in step S3 includes: The UEFI bootloader and environment dependency auto-installation script env-restore.sh, adapted for openEuler, are used to rebuild the software runtime environment during restoration.

7. The method for rapid backup and restore of the openEuler system based on Clonezilla according to claim 6, characterized in that: The system restore in step S4 includes: S41, boot from a boot disk or remotely mount an ISO image file via BMC; S42 automatically matches the LVM logical volume structure of the target disk. If the capacity of the target disk is different from that of the source disk, the logical volume size is dynamically adjusted using the lvresize tool. S43, execute env-restore.sh, install the missing dependency libraries based on env-deps.json, and repair the openEuler system service using the dnf tool; S44 will automatically restart or shut down upon completion.

8. A fast backup and restore system for the openEuler system based on Clonezilla, characterized in that: include: Device preparation module: used to create Clonezilla boot disks and format storage devices; Startup module: Guides the target device into the customized Clonezilla operating environment; Image generation module: Performs system backup and generates a bootable ISO image file; Recovery module: Loads the image file via boot disk or BMC and completes system restore.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the method according to any one of claims 1-7.

10. A storage device storing computer programs / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method according to any one of claims 1-7.

Images