A Linux cross-disk volume group disaster recovery system and disaster recovery method

By using volume filtering driver and volume replication program in Linux cross-disk volume group environment for real-time backup, combined with boot adapter tools to process virtual block devices, the problems of inconsistent volume group metadata and high resource utilization in the existing technology are solved, and the problem of inconsistent volume group metadata and high resource utilization in the existing technology is realized. Efficient cross-disk volume group backup and disaster recovery.

CN114490176BActive Publication Date: 2024-11-01NANJING UNARY INFORMATION TECH
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202111492983.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-12-08
Publication Date
2024-11-01
Estimated Expiration
2041-12-08

AI Technical Summary

Technical Problem

Existing block-level CDP backups cannot guarantee the consistency of volume group metadata for Linux across disk volume groups, resulting in the inability to perform disaster recovery normally. File-level CDP backups will consume a large resource, cost high, and cannot parse valid data.

Method used

A Linux disaster recovery system is designed for cross-disk volume groups, including the proxy and server. It uses volume filtering driver and volume replication program for real-time backup. It monitors disk or logical volume IO changes through volume filtering drivers, volume replication program backup and Recover disk and volume group information, and handle virtual block devices through the boot adapter tool to realize real-time backup and disaster recovery of logical volumes across disk volume groups.

Benefits of technology

Solve the problem of inconsistent metadata of volume groups in block-level CDP backup, reduce the resource usage and cost of file-level CDP backup, realize efficient backup and disaster recovery across disk volume groups, and avoid slow speed caused by full disk backup. and the problem of large storage space.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114490176B_ABST
    Figure CN114490176B_ABST
Patent Text Reader

Abstract

The invention discloses a disaster recovery system and method for a Linux cross-disk volume group, belonging to the technical field of data backup and disaster recovery. The system comprises: an agent installed in a host containing a cross-disk volume group; a management platform and a server installed in a server; and a virtualization platform for disaster recovery. The disaster recovery method comprises the following steps: step 1, backing up and saving the metadata of the volume group; step 2, dividing the disk and the volume group according to the partition type and the execution result of the volume group-related command, monitoring and backing up the basic partition by partition, and monitoring and backing up the logical volume on the cross-disk volume group by volume; the Linux cross-disk volume group disaster recovery system and method solve the problem that the existing block-level CDP backup can only back up the cross-disk volume group in its entirety, resulting in inconsistent volume group metadata, thereby failing to perform disaster recovery. At the same time, it also solves the problem that the block-level CDP backup can only back up the cross-disk volume group in its entirety, and cannot parse valid data, resulting in slow backup and large storage space occupation.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention belongs to the technical field of data backup and disaster recovery, and specifically provides a disaster recovery system and a disaster recovery method supporting Linux cross-disk volume groups. Background Art

[0002] LVM is the Logical Volume Management function provided by the Linux kernel. It is a logical layer built on top of hard disks and partitions and below the file system. When the file system is established, the underlying disk partition layout is shielded, and the disk capacity is dynamically adjusted while keeping the existing data unchanged, thereby improving the flexibility of disk management. As the amount of data grows, the problem of insufficient file system space becomes increasingly apparent. The Linux environment usually solves this problem by expanding the volume group, specifically by adding a new disk or partition to expand the existing volume group. After the volume group is successfully expanded, the logical volume on the volume group is expanded. The schematic diagram of the Linux cross-disk volume group environment after expansion is shown below. Figure 1 As shown;

[0003] Continuous Data Protection (CDP) is a method that can continuously capture or track any changes to target data without affecting the operation of primary data, and can restore to any previous time point. The CDP system can provide block-level, file-level and application-level backup, as well as unlimited and variable recovery points for the recovery target. It is a revolutionary breakthrough in traditional data backup technology. However, the existing block-level CDP backup and the existing file-level CDP backup cannot support the Linux cross-disk volume group environment well. The existing block-level CDP backup backs up data at the block device level and monitors data changes at the block device level in real time. Figure 1 The block-level CDP backup is to back up the / dev / sda and / dev / sdb disks, but the / dev / sda2 partition under / dev / sda and the / dev / sdb1 partition under / dev / sdb are in the same volume group systemvg. In this way, the valid data cannot be backed up, and only a full backup is required. Because the / dev / sda and / dev / sdb disks are backed up in a certain order, the backed-up data cannot guarantee the consistency of the volume group systemvg metadata, and then, it cannot guarantee that the disaster recovery function can normally take over the business.

[0004] The existing file-level CDP backup is to back up the data at the file system level and monitor the data changes at the file system level in real time. Figure 1, file-level CDP backup is to back up / boot, / and / data, and the backed-up data does not contain boot information and LVM metadata information; that is, if disaster recovery is based on file-level CDP backup, a disaster recovery machine needs to be prepared in advance and correspond one-to-one with the production machine, which not only takes up resources but also increases costs. Therefore, it is necessary to develop a new disaster recovery system and disaster recovery method to solve the existing problems. Summary of the invention

[0005] The purpose of the present invention is to provide a disaster recovery system and method supporting Linux cross-disk volume groups, so as to solve the problem that the existing cross-disk volume group backup based on block-level CDP cannot ensure the consistency of volume group metadata and cannot be disaster-tolerant.

[0006] To achieve the above object, the present invention provides the following technical solution: a Linux cross-disk volume group disaster recovery system, comprising:

[0007] Installed on the agent side of the host configured with a cross-disk volume group;

[0008] The agent terminal includes:

[0009] Volume filter driver for monitoring disk or logical volume IO changes;

[0010] Volume copy program for querying, backing up, and restoring disk and volume group information;

[0011] Client management program for client message communication, process control and driver management;

[0012] The server installed in the server;

[0013] The server includes:

[0014] A virtual block device driver used to provide a mirror device to the agent for data backup or to provide a virtual block device to the virtualization platform for disaster recovery;

[0015] CDP driver for receiving IO data from the agent, marking the timestamp and saving it to the storage;

[0016] Server-side agent for server-side message communication, process control, and driver management;

[0017] A management program used to provide a web interface for users;

[0018] A boot adapter tool for processing boot files and automount files in virtual block devices;

[0019] Virtualization platform for disaster recovery.

[0020] The present invention further provides a disaster recovery method for a Linux cross-disk volume group disaster recovery system, comprising the following steps:

[0021] Step 1: Back up the metadata of the volume group and save it;

[0022] Step 2: Divide disks and volume groups according to partition types and volume group-related command execution results, monitor and back up basic partitions by partition, and monitor and back up logical volumes on cross-disk volume groups by volume, and record IO data changes in IO logs;

[0023] Step 3: If there is a hardware or software failure, a virtual block device can be created at a specified time point through the IO log. After being processed by the boot adapter tool, it is provided to the virtualization platform to create a disaster recovery machine to take over the business.

[0024] Step 4: Restore the volume group using the volume group metadata backed up in step 1, and use the migration tool to migrate data from the disaster recovery machine to the Linux cross-disk volume group environment.

[0025] Preferably, in step 2, the initialization backup step includes:

[0026] Step 21: Install the agent in any host across the disk volume group, and register the agent with the management platform;

[0027] Step 22: Select the disks and logical volumes to be protected in the management platform and configure the continuous data protection backup policy;

[0028] Step 23: The agent receives the continuous data protection backup policy, parses the disk and logical volume information to be protected configured in the policy, and uploads it to the server;

[0029] Step 24, the agent executes the continuous data protection backup strategy, notifies the server to create a mirror device, and after connecting to the mirror device, the agent starts to perform initialization backup; wherein, the initialization backup includes the volume filter driver adding a monitoring task to monitor disk or logical volume IO changes and the volume copy program backing up disk or logical volume data.

[0030] Preferably, in step 2, establishing the IO log includes the following steps:

[0031] Step 25, the server receives the IO data sent by the agent, marks the timestamp, and stores it in the storage of the server;

[0032] Step 26: After the backup of the volume copy program on the proxy side is completed, when the volume filter driver monitors the IO changes in real time, it notifies the server side that the initialization backup is completed. The server side marks the initialization completed and records the time point of the initialization completion.

[0033] Preferably, in step 3, the step of creating a disaster recovery machine includes:

[0034] Step 31, creating a disaster recovery strategy on the management platform, wherein the disaster recovery strategy includes a data source of backup data of the production machine, a virtualization platform, and a disaster recovery machine configuration;

[0035] Step 32: Start the disaster recovery strategy on the management platform and specify the time point at which the disaster recovery machine needs to be taken over. The server organizes data and generates a virtual block device according to the specified time point. The virtualization platform creates a disaster recovery machine according to the disaster recovery machine configuration.

[0036] Step 33, after the virtual block device is generated on the server side, the boot adapter tool checks and processes the boot file and the automatic mount file in the virtual block device;

[0037] Step 34, when the boot adapter tool completes the processing, the server provides the virtual block device to the disaster recovery machine of the virtualization platform, and starts the disaster recovery machine to take over.

[0038] Preferably, in step 4, the step of migrating the disaster recovery machine to an environment containing a Linux cross-disk volume group includes:

[0039] Step 41, enter the migration environment through the migration tool, in which the built-in migration agent will automatically connect to the management platform; if the volume group structure of the production environment is damaged, rebuild the volume group through the vgcfg.bak configuration file backed up by the server;

[0040] Step 42, creating a migration strategy on the management platform, the migration strategy including a data source, a migration mode, and a migration target machine;

[0041] Step 43, the migration agent restores data according to the migration strategy, and restarts after the migration is completed.

[0042] Preferably, in step 24, the mirror device includes a virtual block device created by the server according to source device information provided by the agent, and its capacity is the same as that of the source device, and the source device includes a disk or a logical volume.

[0043] Preferably, in step 1, the metadata of the backup volume group includes backing up and saving the metadata of the volume group through vgcfgbackup; wherein the metadata of the volume group backed up by vgcfgbackup can be set to scheduled backup, or automatically backed up after detecting changes in the volume group.

[0044] Preferably, in step 2, the partition type division of disks and volume groups includes parsing partition types such as 8e (LVM partition type) and volume group related commands such as vgscan, pvscan, lvscan, etc. to obtain partitions and logical volumes through a volume copy program.

[0045] Preferably, in step 22, the continuous data protection backup strategy includes: disk configuration, logical volume configuration, snapshot configuration, backup mode configuration and storage configuration.

[0046] The technical effects and advantages of the present invention are as follows: the Linux cross-disk volume group disaster recovery system and disaster recovery method realize real-time backup of logical volumes on the cross-disk volume group through volume filter driver and volume copy program, and solve the problem that the existing block-level CDP backup causes inconsistent volume group metadata in the cross-disk volume group backup, thus making it impossible to perform disaster recovery;

[0047] It solves the problem of large disaster recovery resource usage and high cost based on file-level CDP backup across disk volume groups. It also solves the problem of slow backup and large storage space usage due to the inability to parse valid data and only full disk backup based on existing block-level CDP backup across disk volume groups.

[0048] The boot adapter tool automatically processes the boot files and auto-mount files in the virtual block device, seamlessly connecting the subsequent disaster recovery operations. In addition, this solution does not require the preparation of a disaster recovery machine in advance. Instead, it can be pulled up on demand when disaster recovery is needed, thereby reducing resource usage and disaster recovery costs.

[0049] By parsing the logical volumes on the cross-disk volume group through the volume copy program, the backup of valid data on the volume group is realized, which solves the problems of slow speed and large storage space occupied in the existing block-level CDP backup of the full disk of the cross-disk volume group. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 It is a schematic diagram of the structure of a cross-disk volume group in the prior art of the present invention;

[0051] Figure 2 is a flow chart of the present invention;

[0052] Figure 3 Initialize backup and create IO log flow chart for the present invention;

[0053] Figure 4 A flow chart for creating a disaster recovery machine for the present invention;

[0054] Figure 5 A flow chart of the present invention for migrating a disaster recovery machine to an environment containing a Linux cross-disk volume group;

[0055] Figure 6 A schematic diagram of the backup and disaster recovery system of the present invention;

[0056] Figure 7 This is a backup and disaster recovery timing diagram of the present invention. DETAILED DESCRIPTION

[0057] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0058] The present invention provides Figure 6 In the figure, a Linux cross-disk volume group disaster recovery system is shown, including:

[0059] Installed on the agent side of the host configured with a cross-disk volume group;

[0060] The agent terminal includes:

[0061] Volume filter driver for monitoring disk or logical volume IO changes;

[0062] Volume copy program for querying, backing up, and restoring disk and volume group information;

[0063] Client management program for client message communication, process control and driver management;

[0064] The server installed in the server;

[0065] The server includes:

[0066] A virtual block device driver used to provide a mirror device to the agent for data backup or to provide a virtual block device to the virtualization platform for disaster recovery;

[0067] CDP driver for receiving IO data from the agent, marking the timestamp and saving it to the storage;

[0068] Server-side agent for server-side message communication, process control, and driver management;

[0069] A management program used to provide a web interface for users;

[0070] A boot adapter tool for processing boot files and automount files in virtual block devices;

[0071] A virtualization platform for disaster recovery. In this embodiment, the virtualization platform is a virtualization program developed based on the open source KVM, which can be installed on the same server as the server. There is no need to prepare a disaster recovery machine in advance. Instead, when disaster recovery is needed, a disaster recovery machine is created to take over, which reduces resource usage and disaster recovery costs.

[0072] The present invention further provides a disaster recovery method for a Linux cross-disk volume group disaster recovery system, such as Figure 2 , Figure 7As shown, the following steps are included:

[0073] Step 1, back up the metadata of the volume group and save it; in this embodiment, the metadata of the backed up volume group includes backing up the metadata of the volume group through vgcfgbackup and saving it; wherein the metadata of the volume group backed up by vgcfgbackup can be set to scheduled backup, or automatically backed up after detecting changes in the volume group.

[0074] Step 2: Divide the disk and volume group according to the partition type and the execution result of the volume group related commands, monitor and back up the basic partitions by partition, and monitor and back up the logical volumes on the cross-disk volume group by volume, and record the IO data changes in the IO log; in this embodiment, the volume filter driver is different from the existing disk filter driver based on block-level CDP backup. In this solution, the IO changes of the disk and the logical volume are monitored at the same time;

[0075] When the volume copy program backs up a cross-disk volume group, it backs up the logical volumes on the cross-disk volume group instead of the partitions or disk devices that make up the cross-disk volume group. It also parses and backs up the valid data on the logical volume, thereby improving backup efficiency and shortening backup time. Combined with the volume filter driver to monitor data changes on the logical volume, it effectively solves the problem that the existing block-level CDP backup cannot ensure the consistency of metadata across the disk volume group, and the physical volume is lost during disaster recovery.

[0076] In step 2, if Figure 3 As shown, the initialization backup steps include:

[0077] Step 21: Install an agent in any host across the disk volume group, and register the agent with the management platform; the agent includes a volume-level filter driver, a volume copy program, and a client management program, etc. The management platform is an application running on the server side, and is used to manage backup, recovery, and disaster recovery services;

[0078] Step 22, after the agent goes online on the management platform, the disk and volume group information of the production environment, i.e., the environment containing the Linux cross-disk volume group, can be queried on the management platform, and the disk and logical volume to be protected can be selected on the management platform to configure the continuous data protection backup strategy; in this embodiment, the continuous data protection backup strategy includes: disk configuration, logical volume configuration, snapshot configuration, backup mode configuration, and storage configuration; the disk and volume group information of the production environment is obtained by querying the volume copy program, and the volume copy program obtains the current device file by parsing / proc / partitions, and then obtains the specific disk and partition information by the parted command, and then obtains the specific information of the volume group by the volume group related commands;

[0079] Step 23, the agent receives the continuous data protection backup policy, parses the disk and logical volume information to be protected configured in the policy, and uploads it to the server; the agent receives the CDP backup policy, parses the disk and logical volume information to be protected configured in the policy; the agent calls "vgcfgbackup -f vgcfg.bak" to back up the volume group metadata information, and uploads it to the server;

[0080] Step 24, the agent executes the continuous data protection backup strategy, notifies the server to create a mirror device, and after connecting to the mirror device, the agent starts to do initialization backup; wherein, the initialization backup includes the volume filter driver adding a monitoring task for monitoring disk or logical volume IO changes and the volume copy program backing up disk or logical volume data;

[0081] The mirror device includes a virtual block device created by the server according to the source device information provided by the agent, and its capacity is the same as that of the source device, and the source device includes a disk or a logical volume;

[0082] The mirror device includes a virtual block device created by the server based on the source device information provided by the agent. Its size is the same as the source device and is used to provide CDP backup for the agent. The source device includes a disk or a logical volume.

[0083] The volume filter driver monitors the IO changes during the backup process. If the driver monitors a common partition or disk, the volume filter driver adds a disk monitoring task to monitor the IO changes on the disk. If the driver monitors a logical volume, the volume filter driver adds a logical volume monitoring task to monitor the IO changes on the logical volume on the cross-disk volume group.

[0084] The volume copy program backs up disk and logical volume data, including if the backup object is a common partition or disk, the volume copy program backs up the disk data; if the backup object is a cross-disk volume group, the volume copy program backs up the logical volume data on the cross-disk volume group;

[0085] In step 2, the establishment of the IO log includes the following steps:

[0086] Step 25, the server receives the IO data sent by the agent, marks the timestamp, and stores it in the storage of the server;

[0087] Step 26: After the backup of the volume copy program on the proxy side is completed, when the volume filter driver monitors the IO changes in real time, it notifies the server side that the initialization backup is completed. The server side marks the initialization completed and records the time point of the initialization completion.

[0088] Step 3: After the Linux cross-disk volume group environment is backed up and IO is in real-time monitoring, the logical volume is backed up. During disaster recovery, the device name of the production virtual block device is different from that of the original device, but the UUID of the file system is the same, so the boot adapter tool is needed to update the boot file configuration items and automatic mount file configuration items according to the boot mode and operating system. The boot modes are mainly BIOS and UEFI. In addition to common Linux distributions, the operating system also includes domestically produced Galaxy Kylin, UOS, Euler and other operating systems. The boot file includes the Linux boot loader configuration file, among which the Linux boot loader Including GRUB, GRUB2, LILO; if the hardware or software fails, a virtual block device is created at a specified time point through the IO log, processed by the boot adapter tool, and sent to the virtualization platform to create a disaster recovery machine; in this embodiment, the virtualization platform is KVM; the creation of a disaster recovery machine to take over the business is created on demand, and does not need to occupy resources all the time, which effectively reduces the disaster recovery cost. The virtualization platform is a hyper-converged platform or a cloud platform; the virtualization platform includes KVM, VMWareESXi, Microsoft Hyper-V, and Xen. When a hardware error or logical error occurs in the production environment, causing the production business to be unable to continue running, a disaster recovery machine can be created through the management platform to take over the business, such as Figure 4 As shown in the figure, the steps to create a disaster recovery machine include:

[0089] Step 31, creating a disaster recovery strategy on the management platform, wherein the disaster recovery strategy includes a data source of backup data of the production machine, a virtualization platform, and a disaster recovery machine configuration;

[0090] Step 32: Start the disaster recovery strategy on the management platform and specify the time point at which the disaster recovery machine needs to be taken over. The server organizes data and generates a virtual block device according to the specified time point. The virtualization platform creates a disaster recovery machine according to the disaster recovery machine configuration.

[0091] Step 33, after the virtual block device is generated on the server side, the boot adapter tool checks and processes the boot file and the automatic mount file in the virtual block device;

[0092] Step 34, when the boot adapter tool completes the processing, the server provides the virtual block device to the disaster recovery machine of the virtualization platform and starts the disaster recovery machine to take over;

[0093] Step 4: Restore the volume group using the volume group metadata backed up in step 1, and use the migration tool to migrate data from the disaster recovery machine to the environment containing the Linux cross-disk volume group;

[0094] When the production environment is available, the data taken over by the disaster recovery machine can be migrated back to the production machine through the management platform, such as Figure 5 As shown in the figure, the steps to migrate the disaster recovery machine back to the environment with Linux cross-disk volume group include:

[0095] Step 41, enter the migration environment through the migration tool, in which the built-in migration agent will automatically connect to the management platform; if the volume group structure of the production environment is damaged, rebuild the volume group through the vgcfg.bak configuration file backed up by the server;

[0096] Step 42, creating a migration strategy on the management platform, the migration strategy including a data source, a migration mode, and a migration target machine;

[0097] Step 43, the migration agent restores data according to the migration strategy, and restarts after the migration is completed.

[0098] If the volume group in the Linux cross-disk volume group environment is damaged due to hardware or software reasons, it can be rebuilt using the volume group metadata backed up in step 1;

[0099] The disaster recovery system and method of the present invention realize real-time backup of logical volumes on cross-disk volume groups through volume filter drivers and volume replication programs, solving the problem that the existing block-level CDP backup results in inconsistent volume group metadata for cross-disk volume group backup, thus making disaster recovery impossible.

[0100] It solves the problem of large disaster recovery resource usage and high cost based on file-level CDP backup across disk volume groups. It also solves the problem of slow backup and large storage space usage due to the inability to parse valid data and only full disk backup based on existing block-level CDP backup across disk volume groups.

[0101] The boot adapter tool automatically processes the boot files and auto-mount files in the virtual block device, seamlessly connecting the subsequent disaster recovery operations. In addition, this solution does not require the preparation of a disaster recovery machine in advance. Instead, it can be pulled up on demand when disaster recovery is needed, thereby reducing resource usage and disaster recovery costs.

[0102] By parsing the logical volumes on the cross-disk volume group through the volume copy program, the backup of valid data on the volume group is realized, which solves the problems of slow speed and large storage space occupied in the existing block-level CDP backup of the full disk of the cross-disk volume group.

[0103] Finally, it should be noted that the above is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, it is still possible for those skilled in the art to modify the technical solutions described in the aforementioned embodiments or to make equivalent substitutions for some of the technical features therein. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A Linux cross-disk volume group disaster recovery method, characterized by: The following steps are involved: Step 1: Back up the metadata of the volume group and save it; Step 2: Divide the disk and volume group according to the partition type and volume group command execution result, monitor and back up the basic partition by partition, and monitor and back up the logical volume on the cross-disk volume group by volume, and record the IO data changes in the IO log, wherein the backup step includes: Step 21: Install an agent in any host across the disk volume group, and register the agent with the management platform. The agent includes a volume filter driver, a volume copy program, and a client management program. The management platform is an application running on the server side, and is used to manage backup, recovery, and disaster recovery services. Step 22: Select the disks and logical volumes to be protected in the management platform and configure the continuous data protection backup policy; Step 23: The agent receives the continuous data protection backup policy, parses the disk and logical volume information to be protected configured in the policy, and uploads it to the server; Step 24, the agent executes the continuous data protection backup strategy and notifies the server to create a mirror device, wherein the mirror device includes a virtual block device created by the server according to the source device information provided by the agent, and its size is the same as that of the source device, and is used to provide the agent with CDP backup; the source device includes a disk or a logical volume, and after connecting to the mirror device, the agent starts to perform initialization backup; wherein the initialization backup includes: The volume filter driver monitors the IO changes during the backup process. If the driver monitors a common partition or disk, the volume filter driver adds a disk monitoring task to monitor the IO changes on the disk. If the driver monitors a logical volume, the volume filter driver adds a logical volume monitoring task to monitor the IO changes on the logical volume on the cross-disk volume group. The volume copy program backs up disk and logical volume data, including if the backup object is a common partition or disk, the volume copy program backs up the disk data; if the backup object is a cross-disk volume group, the volume copy program backs up the logical volume data on the cross-disk volume group; Step 3: If there is a hardware or software failure, a virtual block device is created at a specified time point through the IO log. After being processed by the boot adapter tool, it is provided to the virtualization platform to create a disaster recovery machine. Step 4: Restore the volume group using the volume group metadata backed up in step 1, and use the migration tool to migrate data from the disaster recovery machine to the Linux cross-disk volume group environment.

2. A Linux cross-disk volume group disaster recovery method according to claim 1, characterized in that: Step 2 also includes the following steps: Step 25, the server receives the IO data sent by the agent, marks the timestamp, and stores it in the storage of the server; Step 26: After the backup of the volume copy program on the proxy side is completed, when the volume filter driver monitors the IO changes in real time, it notifies the server side that the initialization backup is completed. The server side marks the initialization completed and records the time point of the initialization completion.

3. A Linux cross-disk volume group disaster recovery method according to claim 1, characterized in that: In step 3, the steps of creating a disaster recovery machine include: Step 31, creating a disaster recovery strategy on the management platform, wherein the disaster recovery strategy includes a data source of backup data of the production machine, a virtualization platform, and a disaster recovery machine configuration; Step 32: Start the disaster recovery strategy on the management platform and specify the time point at which the disaster recovery machine needs to be taken over. The server organizes data and generates a virtual block device according to the specified time point. The virtualization platform creates a disaster recovery machine according to the disaster recovery machine configuration. Step 33, after the virtual block device is generated on the server side, the boot adapter tool checks and processes the boot file and the automatic mount file in the virtual block device; Step 34, when the boot adapter tool completes the processing, the server provides the virtual block device to the disaster recovery machine of the virtualization platform, and starts the disaster recovery machine to take over.

4. A Linux cross-disk volume group disaster recovery method according to claim 1, characterized in that: In step 4, the steps of migrating the disaster recovery machine to the environment containing the Linux cross-disk volume group include: Step 41, enter the migration environment through the migration tool, in which the built-in migration agent will automatically connect to the management platform; if the volume group structure of the production environment is damaged, rebuild the volume group through the vgcfg.bak configuration file backed up by the server; Step 42, creating a migration strategy on the management platform, the migration strategy including a data source, a migration mode, and a migration target machine; Step 43, the migration agent restores the data according to the migration strategy, and restarts after the migration is completed.

5. The Linux cross-disk volume group disaster recovery method according to claim 1, characterized in that: In step 1, the metadata of the volume group is backed up by vgcfgbackup and saved; wherein the metadata of the volume group backed up by vgcfgbackup is set to be backed up regularly, or automatically backed up after detecting changes in the volume group.

6. A Linux cross-disk volume group disaster recovery method according to claim 1, characterized in that: In step 2, the partition type division of disks and volume groups includes obtaining basic partitions and logical volumes through a volume copy program and volume group related commands, and the volume group related commands include vgscan or pvscan.

7. A Linux cross-disk volume group disaster recovery method according to claim 1, characterized in that: In step 22, the continuous data protection backup strategy includes: disk configuration, logical volume configuration, snapshot configuration, backup mode configuration and storage configuration.

8. A disaster recovery system supporting Linux cross-disk volume groups, used to implement a Linux cross-disk volume group disaster recovery method according to any one of claims 1 to 7, characterized in that: include: Installed on the agent side of the host configured with a cross-disk volume group; The agent terminal includes: Volume filter driver for monitoring disk or logical volume IO changes; Volume copy program for querying, backing up, and restoring disk and volume group information; Client management program for client message communication, process control and driver management; The server installed in the server; The server includes: A virtual block device driver used to provide a mirror device to the agent for data backup or to provide a virtual block device to the virtualization platform for disaster recovery; CDP driver for receiving IO data from the agent, marking the timestamp and saving it to the storage; Server-side agent for server-side message communication, process control, and driver management; A management program used to provide a web interface for users; A boot adapter tool for processing boot files and automount files in virtual block devices; Virtualization platform for disaster recovery.

Citation Information

Patent Citations

  • CDP (Continual Data Protection) disaster-tolerance method based on cloud platform

    CN108255641A

  • A fast incremental initialization method after a volume mirroring image is interrupted

    CN109542673A

  • Rapid remote recovery method and system for continuous data protection

    CN111045864A

  • High-availability system based on volume copy and multi-server data synchronization method

    CN111158955A

  • Method and system for supporting block-level incremental backups of file system volumes using volume pseudo devices

    US9959278B1