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

Abstract

The application discloses a Clonezilla-based openEuler system rapid backup and restoration method, system, device and apparatus, and relates to the technical field of operating system backup; the method comprises the following steps: making a Clonezilla startup disk and an ext4 format storage device; starting a target device through a boot disk, selecting a local storage mode and a backup strategy, and performing partition-level or full-disk compressed backup on an openEuler system under an enterprise-level server with a Kunpeng processor developed by Huawei, all software in the system and an environment required for installing the software; and generating a startable system image ISO file; through a customized image processing flow, hardware instruction set adaptation and system environment deep capture technology, the application solves the problems of poor compatibility, low efficiency and incomplete environment restoration of a traditional Linux backup method on a domestic platform, and improves the response speed of system deployment and disaster recovery.

Description

Technical Field

[0001] This application relates to the field of system backup technology, and in particular to a method, system, device and apparatus for fast backup and restore of the openEuler system based on Clonezilla. Background Technology

[0002] With the increasing popularity of domestically produced servers, operating systems, and databases, servers based on the Kunpeng processor (ARM64 architecture) and openEuler system are widely used in various industries. System backup, fault recovery, and batch deployment are core requirements during server operation and maintenance.

[0003] Traditional backup methods have the following problems:

[0004] Poor compatibility: General backup tools are not optimized for the Kunpeng architecture and openEuler system, which can easily lead to compatibility issues;

[0005] Inefficient: Manual backups require operation on a machine-by-machine basis, and server deployment takes a long time;

[0006] Complex operation: It requires manual configuration of partitioning, compression parameters, etc., and demands high skills from operation and maintenance personnel;

[0007] Limited deployment options: lacking flexible deployment methods that combine local and remote deployment.

[0008] To address the aforementioned issues, there is an urgent need for an efficient and automated backup method that is compatible with the Kunpeng processor, the openEuler system, all software within the system, the installation environment required by the software, and its drivers. Summary of the Invention

[0009] To address the issues of poor compatibility, low efficiency, and complex operation of traditional backup methods on the Kunpeng architecture and openEuler system, this application proposes a fast backup and restore method, system, device, and apparatus for the openEuler system based on Clonezilla.

[0010] The technical solution adopted in this application is: a fast backup and restore method for the openEuler system based on Clonezilla, including the following steps:

[0011] Step S1: Complete the backup preparation work: including hardware environment, software tools, and compatible boot disk and storage disk;

[0012] 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;

[0013] 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.

[0014] Step S3: Convert the compressed image file into a bootable ISO image file;

[0015] Step S4: Boot from the boot disk or remotely mount the ISO image file via BMC to complete the system restore.

[0016] Furthermore, the hardware environment in step S1 includes the Kunpeng processor, and the software tools include the Clonezillalive-arm64 image, Rufus software, or dd instructions.

[0017] Furthermore, the steps for creating a bootable disk are as follows:

[0018] 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;

[0019] 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.

[0020] Furthermore, in step S2, the storage device is a formatted storage disk, and the mirrored 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.

[0021] Further, in step S2, a backup strategy is selected to perform a full disk or a compressed backup of a specified partition on the openEuler system of the target device;

[0022] 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;

[0023] 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.

[0024] Furthermore, the ISO image file generated in step S3 includes:

[0025] 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.

[0026] Furthermore, the system restore in step S4 includes:

[0027] S41, boot from a boot disk or remotely mount an ISO image file via BMC;

[0028] 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.

[0029] 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;

[0030] S44 will automatically restart or shut down upon completion.

[0031] A fast backup and restore system for the openEuler system based on Clonezilla, comprising:

[0032] Device preparation module: used to create Clonezilla boot disks and format storage devices;

[0033] Startup module: Guides the target device into the customized Clonezilla operating environment;

[0034] Image generation module: Performs system backup and generates a bootable ISO image file;

[0035] Recovery module: Loads the image file via boot disk or BMC and completes system restore.

[0036] A computer device includes a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the method.

[0037] A storage device having a computer program / instructions stored thereon, which, when executed by a processor, implement the steps of the method.

[0038] The advantages of this application over the prior art are as follows:

[0039] 1) Strong adaptability: Optimized for Kunpeng processors and openEuler system, resolving compatibility issues;

[0040] 2) High efficiency and automation: The Clonzilla interface simplifies the operation process, supports batch image creation and deployment, and saves operation and maintenance time;

[0041] 3) Flexible deployment: Supports local USB flash drive booting and remote BMC mounting, adapting to different operation and maintenance scenarios;

[0042] 4) High reliability: The mirror verification mechanism ensures the consistency between backup and restoration, reducing the risk of data loss. Attached Figure Description

[0043] The following description, in conjunction with the accompanying drawings, further illustrates this application:

[0044] Figure 1 A flowchart illustrating the creation of a system compressed file provided in this application embodiment;

[0045] Figure 2 A flowchart illustrating the creation process of an ISO image file provided in this application embodiment;

[0046] Figure 3 A flowchart of ISO restoration using USB flash drive boot method provided for embodiments of this application;

[0047] Figure 4 This application provides an ISO restoration flowchart using the BMC remote mounting method as an example.

[0048] Figure 5 This is a structural block diagram of a computer device provided in an embodiment of this application. Detailed Implementation

[0049] 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:

[0050] 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.

[0051] 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.

[0052] 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.

[0053] 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;

[0054] Step S3: Convert the backed-up compressed image file into a bootable ISO image file;

[0055] Step S4: Load the ISO image file by booting from the boot disk or mounting it via BMC to complete the system restore.

[0056] The hardware environment in step S1 includes a Kunpeng processor server and at least two USB flash drives (one for booting and one for storing the image); the software tools include the Clonezilla live-arm64 image, Rufus software, or dd commands; the storage media processing requires formatting the boot USB flash drive to FAT32 and the storage USB flash drive to ext4.

[0057] Step S1, creating the boot disk, includes:

[0058] S11 modifies the kernel parameters of the Clonezilla live-arm64 image (a Clonezilla boot disk adapted for the ARM64 architecture) by adding the openEuler_compat=1 flag to enable compatibility mode for the openEuler system call interface.

[0059] S12 uses the mkfs.ext4 command to format specified parameters of the storage device to adapt to the user-space application compatibility requirements of the Kunpeng processor.

[0060] Specified parameters for formatting a storage device using the mkfs.ext4 command include:

[0061] (1) -L label name: Set a custom label (bound to blkid for unique identification);

[0062] (2) -b block size: Set to a block size compatible with the ARM64 architecture (e.g., 4096 bytes) to ensure the read and write efficiency of Kunpeng processor user-mode applications on storage devices;

[0063] (3) -i inode size: An inode allocation strategy optimized for ARM64 architecture to avoid file system compatibility issues caused by architecture differences.

[0064] (4) -o data=writeback data mode: Enable asynchronous writeback mode to reduce log synchronization delay and improve the concurrent write performance of Kunpeng multi-core.

[0065] The partition table parsing tool in step S2 is a partition table parsing tool optimized for the openEuler kernel. It is based on the original Clonezilla tool and is specially adapted to the partition structure of the openEuler kernel (especially the LVM logical volume management feature), solving the problem of general tools not being able to fully recognize partitions of domestic systems.

[0066] The principle behind using partition table parsing tools to achieve hybrid backup is as follows:

[0067] ① First, use the pvdisplay (physical volume information query) and lvdisplay (logical volume information query) commands to capture the hierarchical structure of LVM logical volumes (such as volume groups, logical volume sizes, mount points, etc.);

[0068] ② In addition, by combining the sector-level data of the physical disk, the structure information of the logical volume is backed up with the original data of the physical volume to ensure that the physical disk data can be restored and the logical structure of the LVM logical volume can be reconstructed during restoration.

[0069] 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:

[0070] ①The blkid tool is used to obtain a device's unique identifier (such as a UUID);

[0071] ② 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).

[0072] The compressed backup in step S3 includes the following operations:

[0073] 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.

[0074] 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:

[0075] (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;

[0076] (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;

[0077] (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.

[0078] 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).

[0079] The S33 compression algorithm uses parallel GZIP (level 1 compression) accelerated by the NEON instruction set. It splits the data stream through multiple threads and uses the SIMD instructions of the Kunpeng processor to improve compression efficiency by more than 30%.

[0080] The ISO image file generated in step S3 includes:

[0081] A UEFI bootloader adapted for openEuler (used to replace the default GRUB configuration of Clonezilla: grub2-efi-arm64).

[0082] The environment dependency auto-install script (env-restore.sh) is used to rebuild the software runtime environment during restoration.

[0083] The system restore in step S4 includes:

[0084] S41, boot from USB flash drive or remotely mount ISO image file via BMC;

[0085] 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.

[0086] S43, execute env-restore.sh, install the missing dependency libraries based on env-deps.json, and repair the openEuler-specific system services using the dnf tool;

[0087] S44 will automatically restart or shut down upon completion.

[0088] In step S43, the system services specific to openEuler mainly include hardware adaptation services based on the Kunpeng architecture, such as:

[0089] ① Kunpeng processor power management service (kunpeng-power.service);

[0090] ②PCIe device driver service (driver management for domestic server hardware);

[0091] ③ openEuler dedicated package management service (DNF related backend service);

[0092] ④ Kernel module loading service (related to the Kunpeng optimization module under the / lib / modules path).

[0093] Traditional methods only back up static files in the file system, ignoring service dependencies, startup configurations, and hardware binding information (such as driver compatibility parameters with the Kunpeng processor), resulting in services failing to start after restoration. This application solves the above problem by calling the dnf tool through env-restore.sh, which repairs service dependencies and configurations based on env-deps.json.

[0094] This application develops a logical volume structure identification and dynamic adjustment technology for the LVM logical volume feature of openEuler, breaking through the limitation that "the target disk capacity must be greater than or equal to the source disk".

[0095] The logical volume structure identification and dynamic adjustment technology is not only reflected in step S31 (capturing the LVM structure through pvdisplay / lvdisplay during full disk backup), but more importantly in step S42 (automatically matching the LVM logical volume structure of the target disk and dynamically adjusting its size using the lvresize tool during restoration).

[0096] The principle of logical volume structure identification is as follows: by parsing LVM metadata (such as volume group descriptors and logical volume mapping tables), the "logical topology" of the source disk LVM structure is established. Compared with existing technologies, which mostly rely on static partition tables, this application is specifically optimized for the dynamic LVM management features of openEuler and can identify complex structures such as nested logical volumes and snapshot volumes.

[0097] The principle of dynamic adjustment of logical volume structure is as follows: the adjustment ratio is automatically calculated based on the target disk capacity, and the logical volume size is adjusted without loss (including file system expansion / shrinkage) through the lvresize tool, breaking the limitation that "the target disk capacity must be greater than or equal to the source disk". This is an improvement over traditional static cloning.

[0098] Furthermore, an environment dependency capture and restoration mechanism has been added, which not only backs up the file system, but also associates the package version, repository configuration and kernel module, solving the problem of "the system can start but the software is unusable" after the general method is restored.

[0099] This application optimizes the compression algorithm based on the hardware characteristics of the Kunpeng processor (NEON instruction set, multi-core architecture), achieving higher parallel efficiency than tar (actual backup speed improved by 40%).

[0100] The principle of the above-mentioned optimized compression algorithm can be referred to in step S33, which is as follows:

[0101] (1) NEON instruction set acceleration: Using the NEON SIMD (Single Instruction Multiple Data) instruction set of the Kunpeng processor, the compressed data stream is split into multiple sub-streams and processed in parallel by multiple threads (each thread corresponds to a NEON processing unit) to perform compression operations simultaneously.

[0102] (2) Parallel GZIP optimization: adopting level 1 compression (balancing speed and compression ratio), combined with the Kunpeng multi-core architecture, the compression task is distributed to multiple cores to avoid single-core bottleneck;

[0103] (3) Compared with tar's single-threaded compression or inefficient parallelism, this optimization combines hardware instruction-level parallelism with multi-core scheduling, and in actual tests, it improves backup speed by more than 40%.

[0104] For openEuler's UEFI boot process (which differs from traditional Linux GRUB configuration), a customized boot image generation logic was developed to ensure that the restored image directly supports remote management (BMC) booting on domestic servers. This generation logic is mainly reflected in step S3 (generating the ISO image), specifically including:

[0105] (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;

[0106] (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;

[0107] (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.

[0108] This application has the following two major innovations:

[0109] 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;

[0110] 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.

[0111] This application also proposes a fast backup and restore system for the openEuler system based on Clonezilla, including:

[0112] Device preparation module: used to create Clonezilla boot disks and format ext4 storage devices;

[0113] Startup module: Guides the target device into the Clonezilla operating environment;

[0114] Image generation module: Performs system backup and generates a bootable ISO image;

[0115] Recovery module: Loads the image via boot disk or BMC and completes system restoration.

[0116] Backup configuration module: Select storage mode, backup range, and compression parameters;

[0117] Backup configuration module supports:

[0118] Full disk backup (including / boot and / partitions) or backup of specified partitions;

[0119] Selection of parallel GZIP compression levels;

[0120] Mirror encryption and integrity verification switch.

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

[0122] The application will now be described in further detail with reference to the accompanying drawings and specific embodiments.

[0123] The hardware environment in this embodiment is: an ARM64 architecture server equipped with a Kunpeng processor, with the openEuler-20.03-LTS-SP3-everything-aarch64 system installed; the software environment includes Clonezilla-live-2.6.6-11-arm64.iso, Rufus 3.18 (USB boot disk creation tool), and Ubuntu 20.04 (used for formatting USB flash drives).

[0124] Step S1: Preparation:

[0125] Hardware preparation: The server is equipped with a Kunpeng processor, 128GB of memory, and a 2TB SSD system disk; 2 USB flash drives (8GB for booting and 64GB for storing image files).

[0126] Software preparation: Download the Clonezilla image;

[0127] Install the Rufus tool (Windows environment).

[0128] Storage media processing: Open Rufus, select the 8GB USB flash drive, load the Clonezilla image, set the partition type to GPT, the file system to Large FAT32, and click "Start" to create a bootable disk;

[0129] Format the USB drive: Insert the 64GB USB drive into the Ubuntu system and execute:

[0130] sudo fdisk -l # Identify USB flash drive devices (e.g., / dev / sdb);

[0131] sudo umount / dev / sdb #Unmount;

[0132] sudo mkfs.ext4 / dev / sdb #Format as ext4.

[0133] Step S2: Create a system compressed file:

[0134] ① Insert the bootable USB drive into the server, power on and enter the BIOS, then set the USB drive as the first boot option;

[0135] ② Select "Clonezilla live (Default settings, VGA 800x600)" to enter the interactive interface;

[0136] ③ Select in sequence: start_Clonezilla→device-image→local_dev;

[0137] ④ Insert the USB flash drive, 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: Beginner mode (additional configuration options are already configured by default).

[0138] Select the target hard drive ( / 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;

[0139] Start the automated backup and wait for it to complete. Once complete, a folder named as you just created will appear on the external USB drive, containing the backed-up content.

[0140] Step S3: Create an ISO image file:

[0141] Restart the server, re-enter the Clonzilla interactive interface, and repeat steps ①-④ in S2; select "recovery-iso-zip" → automatically recognize the image file generated in step S2;

[0142] The reason for choosing the "recovery-iso-zip" option is that there are many options in this step, including savedisk in step S2. The reason for choosing this option is that it "creates an ISO file from a compressed file". After selecting it, select the image to be integrated and backed up. Clonezilla will usually automatically recognize the compressed file completed in the first step (such as "2025-7-25-01-img").

[0143] Specify the target device name as / dev / sda (same as the source hard drive) → Select ISO as the output format;

[0144] After confirming the parameters, an ISO image file will be generated (stored on a 64GB USB flash drive and named "openEuler-deploy.iso").

[0145] Step S4: System Deployment

[0146] USB boot method:

[0147] Use Rufus to write "openEuler-deploy.iso" to a third USB drive (32GB), set the partition type to MBR, and the target system type to UEFI; insert the third USB drive into the server to be deployed.

[0148] Enter BIOS and select USB drive as the boot device;

[0149] In the Clonzilla interface, confirm the restore path ( / dev / sda) and image file, then enter "y" to start the restore;

[0150] BMC mounting method:

[0151] Log in to the server's BMC management interface, go to "Remote Control" → "Virtual Media", and mount "openEuler-deploy.iso";

[0152] Set the BMC boot priority to "Virtual CD / DVD" and restart the server;

[0153] The subsequent steps are the same as the restoration method for USB boot mode, to complete the remote deployment.

[0154] Figure 5 A structural block diagram of a computer device according to an embodiment of this application is shown. As shown in Figure 5, the computer device includes a memory and a processor, wherein the memory stores instructions executable on the processor. When the processor executes the instructions, it implements the methods described in the above embodiments. The number of memories and processors can be one or more. This computer device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The computer device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or claimed herein.

[0155] The computer device may also include a communication interface for communicating with external devices and exchanging data. The devices are interconnected using different buses and can be mounted on a common motherboard or otherwise as needed. The processor can process instructions executed within the computer device, including instructions stored in or on memory to display graphical information of a GUI on external input / output devices (such as a display device coupled to the interface). In other embodiments, multiple processors and / or multiple buses can be used with multiple memories and multiple memory modules, if desired. Similarly, multiple electronic devices can be connected, each providing some of the necessary operations (e.g., as a server array, a group of blade servers, or a multiprocessor system). The bus can be divided into address buses, data buses, control buses, etc. For ease of illustration, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

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

[0157] It should be understood that the aforementioned processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. General-purpose processors can be microprocessors or any conventional processor. It is worth noting that the processor can be a processor supporting advanced RISC machines (ARM) architecture.

[0158] This application provides a storage device or computer-readable storage medium (such as the memory described above) that stores computer instructions, which, when executed by a processor, implement the method provided in this application.

[0159] Optionally, the memory may include a stored program area and a stored data area, wherein the stored program area may store the operating system and application programs required for at least one function; the stored data area may store data created based on the use of the computer device for mapping. Furthermore, the memory may include high-speed random access memory and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory may optionally include memory remotely located relative to the processor, which can be connected to the computer device for mapping via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0160] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this 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; 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 to adapt to the user-space application compatibility requirements of the Kunpeng processor. 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 1, 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.

4. 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.

5. The method for rapid backup and restore of the openEuler system based on Clonezilla according to claim 4, 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.

6. The method for rapid backup and restore of the openEuler system based on Clonezilla according to claim 5, 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.

7. A fast backup and restore system for the openEuler system based on Clonezilla, characterized in that: A method for rapidly backing up and restoring a Clonezilla-based openEuler system as described in any one of claims 1-6, the system comprising: 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.

8. 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-6.

9. 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-6.

Images