Row-based real-time protection asynchronous remote replication method, device and equipment

By adopting the ROW snapshot mechanism in the production center, real-time data synchronization between the source volume and the changed volume is achieved, which solves the problems of write latency and data loss in periodic asynchronous remote replication, and improves data write performance and local disaster recovery capabilities.

CN115509806BActive Publication Date: 2026-04-24INSPUR SUZHOU INTELLIGENT TECH CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
INSPUR SUZHOU INTELLIGENT TECH CO LTD
Filing Date
2022-08-26
Publication Date
2026-04-24

AI Technical Summary

Technical Problem

In existing periodic asynchronous remote replication, users need to wait for the data copy to complete before writing data, which prolongs the write time and may result in the loss of a period of data in the event of a failure.

Method used

The ROW snapshot mechanism is adopted to create source volumes, change volumes, and copy volumes in the production center. ROW snapshots are used to achieve real-time data synchronization between source volumes and change volumes, bypassing the write wait of COW snapshots, directly reporting write success, and synchronizing data to the backup center in real time through change volumes.

Benefits of technology

It improved data write performance, prevented data loss, increased local disaster recovery capabilities, reduced business conflicts, and achieved real-time data protection.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115509806B_ABST
    Figure CN115509806B_ABST
Patent Text Reader

Abstract

The application belongs to the technical field of storage system remote replication, and specifically provides a ROW-based real-time protection asynchronous remote replication method, device and equipment, the method comprising the following steps: creating a pool in a production center, and sequentially creating a RAID, a source volume, a changed volume of the source volume and a copy volume after the creation; creating a pool in a backup center, and sequentially creating a RAID, a target volume and a changed volume of the target volume after the creation; setting a ROW snapshot relationship between the source volume and the changed volume of the source volume, a copy relationship between the changed volume of the source volume and the copy volume, and a snapshot relationship between the target volume and the changed volume of the target volume; establishing an intercommunication connection between the production center and the backup center; creating an asynchronous remote replication relationship from the copy volume to the changed volume of the target volume; starting the remote replication, and starting data synchronization of the source volume and the target volume when the data of the source volume and the target volume are inconsistent; and displaying a remote replication state change in real time after the remote replication is successfully started.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of remote replication technology for storage systems, and specifically to a real-time protected asynchronous remote replication method, apparatus, and device based on ROW. Background Technology

[0002] Remote replication of storage systems is used for data center-level data protection or disaster recovery. Its main operation involves creating copies of the same data in different systems. Typically, considering the balance between system reliability and performance, two copies are used in practical applications. In periodic asynchronous remote replication, four volumes reside in different systems (between I / O Groups of different clusters). The production center contains the source volume and its modified version, while the backup center contains the target volume and its modified version. The production center contains production data written to the host and handles normal business application data; the backup center contains backup data for the source volume and maintains synchronization with the source volume data for data recovery after a disaster.

[0003] In current periodic asynchronous remote replication, a copy-on-write (COW) snapshot is used between the source volume and the changed volume of the source volume. Data is not written to the source volume until the source volume has copied the data to be modified to the changed volume. Users writing data must wait for the data copy to complete, thus extending the write time for them. Periodic asynchronous remote replication typically has periodic data time differences; a failure will result in the loss of one period's worth of data. Summary of the Invention

[0004] In current periodic asynchronous remote replication, a copy-on-write (COW) snapshot is used between the source volume and its modified volume. Data is only written to the source volume after the source volume has copied the data to be modified to its modified volume. Users writing data must wait for the data copy to complete, thus extending the write time for them. Periodic asynchronous remote replication typically has periodic data time differences, and a failure can result in the loss of a full period's worth of data. This invention provides a real-time protection asynchronous remote replication method, apparatus, and device based on copy-on-write (ROW).

[0005] In a first aspect, the present invention provides a real-time protected asynchronous remote replication method based on ROW, comprising the following steps:

[0006] Create a pool in the production center, and after creation, create RAID, source volume, modified volume of the source volume, and copy volume in sequence;

[0007] Create a pool in the backup center, and then create the RAID, target volume, and target volume change volume in sequence after creation;

[0008] Configure the ROW snapshot relationship between the source volume and the source volume's changed volume, the copy relationship between the source volume's changed volume and the copy volume, and the snapshot relationship between the target volume and the target volume's changed volume;

[0009] Establish interconnection between the production center and the backup center;

[0010] Creates an asynchronous remote replication relationship between the modified volume and the target volume;

[0011] Initiate remote replication; if the source and target volumes are inconsistent, initiate data synchronization between the source and target volumes.

[0012] After successful remote replication, the status changes of remote replication will be displayed in real time.

[0013] In the production center, source volumes, modified volumes of source volumes, and copy volumes of modified volumes are created. Source volumes and modified volumes of source volumes use ROW snapshots, while modified volumes and copy volumes of source volumes use real-time data synchronization.

[0014] Furthermore, to initiate remote replication, when the source and target volumes are inconsistent, the steps to synchronize the source and target volumes include:

[0015] When remote replication starts, it checks whether the source volume and the target volume are consistent;

[0016] If the data is inconsistent, initiate data synchronization between the source and target volumes.

[0017] After the data synchronization is completed, check again whether the source volume and the target volume are consistent;

[0018] Data is consistent; remote replication started successfully.

[0019] Furthermore, the steps for displaying real-time changes in the remote replication status include:

[0020] After starting remote replication, if the source volume and target volume have inconsistent data, set the display status to "Inconsistent Copy"; if the source volume and target volume have consistent data, set the display status to "Copying in progress"; after the target volume has finished copying the source volume, set the display status to "Consistent Copy".

[0021] Furthermore, the steps for displaying real-time changes in remote replication status also include:

[0022] After stopping remote copying, if inconsistent copying stops, the display status will be set to "Inconsistent copying stopped"; if copying stops during the process, the display status will be set to "Consistent copying stopped"; if consistent copying stops, the display status will be set to "Consistent copying stopped".

[0023] Furthermore, the method also includes:

[0024] When writing data, the data is written to the production center source volume;

[0025] Triggering the ROW snapshot mechanism redirects the metadata to be written to the changed volume of the source volume;

[0026] After the source volume's modified volume data is successfully written, a notification will be sent to the user indicating that the data writing is complete.

[0027] After the write operation is complete, the changed volume data from the source volume is copied to the copy volume.

[0028] Furthermore, the method also includes:

[0029] During data reading, the corresponding data block is pointed to through the metadata, and the data of the corresponding data block is read from the source volume and the changed volume of the source volume respectively, and the read data is combined.

[0030] The combined data is returned to the user with a successful read notification.

[0031] When user data is written, a ROW snapshot process is used, redirecting the metadata to be written to the source volume's modified volume, and the data is directly written to the source volume's modified volume. Once the source volume's modified volume writes data, a write success message is immediately displayed, bypassing the COW write wait and improving data write performance. Because the source volume's modified volume is updated in real-time when data is written to the production center, data can be synchronized from the production center to the backup center at any time, eliminating periodic delays and resolving scenarios where a period of data is lost. Simultaneously, a copy volume of the source volume's modified volume is added, enhancing the local disaster recovery capabilities of the production center and providing a means for local data recovery. Furthermore, the source volume and its modified volume replicate the user's data stream, while the copy volume and backup center replicate the data backup stream, isolating the data stream and backup stream to ensure that data does not interfere with each other and reducing business conflicts.

[0032] Secondly, the technical solution of the present invention also provides a real-time protection asynchronous remote replication device based on ROW, including a first creation module, a second creation module, a setting addition module, an interoperability setting module, a remote replication creation module, an execution control module, and a status display module;

[0033] The first creation module is used to create a pool in the production center. After creation, it sequentially creates RAID, source volume, modified volume of the source volume, and copy volume.

[0034] The second creation module is used to create a pool in the backup center. After creation, the RAID, target volume, and target volume change volume are created in sequence.

[0035] The Add module is used to set the ROW snapshot relationship between the source volume and the source volume's changed volume, the copy relationship between the source volume's changed volume and the copy volume, and the snapshot relationship between the target volume and the target volume's changed volume.

[0036] The interoperability configuration module is used to establish interoperability between the production center and the backup center;

[0037] The remote replication creation module is used to create asynchronous remote replication relationships between a copy volume and a target volume.

[0038] The execution control module is used to initiate remote replication and to synchronize the source and target volumes when the data is inconsistent.

[0039] The status display module is used to display the changes in the remote replication status in real time after the remote replication is successfully started.

[0040] Furthermore, the execution control module includes a judgment unit and a synchronous execution unit;

[0041] The judgment unit is used to determine whether the source volume and the target volume are consistent when remote replication is initiated;

[0042] The synchronization execution unit is used to determine if the data is inconsistent and initiate data synchronization between the source volume and the target volume; after the data synchronization is completed, the determination unit is triggered again.

[0043] Furthermore, the steps for displaying real-time changes in the remote replication status include:

[0044] The status display module is used to set the display status to "Inconsistent Copy" when the source and target volumes are inconsistent after remote replication is started; "Copying in progress" when the source and target volumes are consistent; "Consistent Copy" when the target volume has finished copying the source volume; "Inconsistent Copy Stopped" when remote replication is stopped; "Consistent Copy Stopped" when copying in progress stops; and "Consistent Copy Stopped" when consistent copying stops.

[0045] Furthermore, the device also includes a data write execution module, which, during data writing, writes data to the production center source volume; triggers the ROW snapshot mechanism to redirect the metadata of the data to be written to the changed volume of the source volume; after the changed volume data of the source volume is successfully written, it sends a feedback to the user that the data writing is complete; after the writing is completed, it copies the changed volume data of the source volume to the copy volume.

[0046] Furthermore, the device also includes a data reading execution module, which, during data reading, uses metadata to point to the corresponding data block, reads the data of the corresponding data block from the source volume and the modified volume of the source volume respectively, combines the read data, returns the combined data to the user, and provides feedback that the reading was successful.

[0047] Thirdly, the present invention also provides an electronic device, the electronic device comprising:

[0048] At least one processor; and,

[0049] A memory communicatively connected to the at least one processor; wherein,

[0050] The memory stores computer program instructions executable by at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the ROW-based real-time protected asynchronous remote replication method as described in the first aspect.

[0051] The ROW snapshot mode replaces the previous COW snapshot mode, aiming to improve write performance for data users in the production center. It also adds a copy volume to the changed volume, enhancing the local disaster recovery capabilities of the production center. Based on the characteristics of ROW snapshots, the snapshot volume is updated in real time, meaning that changes to the source volume are updated in real time, enabling real-time data synchronization to the backup center.

[0052] As can be seen from the above technical solution, this invention has the following advantages: The production center creates a source volume, a modified volume of the source volume, and a copy volume of the modified volume. The source volume and its modified volume use ROW snapshots, while the modified volume and its copy volume synchronize data in real time. When user data is written, the ROW snapshot process is followed, redirecting the metadata to be written to the source volume's modified volume, and the data directly falls into the modified volume. Once data is written to the source volume's modified volume, a write success message is immediately displayed, bypassing the COW write wait and improving data write performance. Because the source volume's modified volume is updated in real time when data is written to the production center, data from the production center can be synchronized to the backup center at any time, eliminating periodic delays and resolving scenarios where a period of data is lost. Simultaneously, the addition of a copy volume of the source volume's modified volume enhances the local disaster recovery capabilities of the production center, providing a means for local data recovery. Furthermore, the source volume and its modified volume replicate the user's data stream, while the copy volume and the backup center replicate the data backup stream, isolating the data stream and backup stream, ensuring that their data do not interfere with each other and reducing business conflicts.

[0053] Furthermore, the design principle of this invention is reliable, the structure is simple, and it has a very wide range of application prospects.

[0054] Therefore, it is evident that the present invention has outstanding substantive features and significant progress compared with the prior art, and the beneficial effects of its implementation are also obvious. Attached Figure Description

[0055] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0056] Figure 1This is a schematic flowchart of a method according to an embodiment of the present invention.

[0057] Figure 2 This is a schematic flowchart illustrating the remote replication initiation of a method according to an embodiment of the present invention.

[0058] Figure 3 This is a schematic flowchart illustrating the data writing method of one embodiment of the present invention.

[0059] Figure 4 This is a schematic flowchart illustrating the data reading method according to an embodiment of the present invention. Detailed Implementation

[0060] Currently, asynchronous remote replication uses a Copy-on-Write (COW) snapshot between the source volume and its modified volume. This means that data to be modified is copied from the source volume to the modified volume before being written to the source volume. Users writing data must wait for the data copy to complete, thus extending the write time. Asynchronous remote replication typically has periodic data time differences, and failures can result in the loss of a full cycle of data. This invention addresses this by creating a source volume, a modified volume, and a copy volume in the production center. The source volume and its modified volume use a ROW snapshot, while the modified volume and its copy volume synchronize data in real time. When user data is written, the ROW snapshot process redirects the metadata to the source volume's modified volume, and the data is directly written to the modified volume. Once the modified volume writes data, it immediately reports a successful write, bypassing the COW write wait and improving write performance. Because the modified volume updates in real time during data writing in the production center, data can be synchronized from the production center to the backup center at any time, eliminating periodic delays and resolving the scenario of losing a full cycle of data. At the same time, a copy volume of the source volume's changed volume was added to enhance the local disaster recovery capabilities of the production center and provide a means for the production center's data to be recovered locally; in addition, the source volume and the source volume's changed volume replicate the user's data stream, and the copy volume of the changed volume and the backup center replicate the data backup stream, isolating the data stream and the backup stream so that the data do not affect each other and reducing business conflicts.

[0061] To enable those skilled in the art to better understand the technical solutions of this invention, the technical solutions of the embodiments of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this invention, and not all embodiments. Based on the embodiments of this invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of this invention.

[0062] like Figure 1As shown, this embodiment of the invention provides a real-time protected asynchronous remote replication method based on ROW, including the following steps:

[0063] Step 1: Create a pool in the production center. After creation, create RAID, source volume, source volume change volume, and copy volume in sequence.

[0064] Step 2: Create a pool in the backup center, and after creation, create the RAID, target volume, and target volume change volume in sequence;

[0065] Step 3: Set up the ROW snapshot relationship between the source volume and the source volume's changed volume, the copy relationship between the source volume's changed volume and the copy volume, and the snapshot relationship between the target volume and the target volume's changed volume;

[0066] Step 4: Establish interconnection between the production center and the backup center;

[0067] Step 5: Create an asynchronous remote replication relationship between the copied volume and the target volume;

[0068] Step 6: Start remote replication. If the source volume and target volume data are inconsistent, start data synchronization between the source volume and target volume.

[0069] Step 7: After successful remote replication, the status changes of remote replication will be displayed in real time.

[0070] In the production center, source volumes, modified volumes of source volumes, and copy volumes of modified volumes are created. Source volumes and modified volumes of source volumes use ROW snapshots, while modified volumes and copy volumes of source volumes use real-time data synchronization.

[0071] The ROW snapshot mode replaces the previous COW snapshot mode, aiming to improve write performance for data users in the production center. It also adds a copy volume to the changed volume, enhancing the local disaster recovery capabilities of the production center. Based on the characteristics of ROW snapshots, the snapshot volume is updated in real time, meaning that changes to the source volume are updated in real time, enabling real-time data synchronization to the backup center.

[0072] In some embodiments, such as Figure 2 As shown, in step 6, when remote replication is initiated and the source and target volumes are inconsistent, the steps to synchronize the source and target volumes include:

[0073] Step 61: When remote replication starts, determine whether the source volume and the target volume are consistent;

[0074] If the data is inconsistent, proceed to step 62; if the data is consistent, proceed to step 64.

[0075] Step 62: Initiate data synchronization between the source and target volumes;

[0076] Step 63: After the data synchronization is completed, check again whether the source volume and the target volume are consistent;

[0077] If the data is inconsistent, proceed to step 62; if the data is consistent, proceed to step 64.

[0078] Step 64: Remote copying started successfully.

[0079] In some embodiments, the step of displaying changes in the remote replication status in real time includes:

[0080] After starting remote replication, if the source volume and target volume have inconsistent data, set the display status to "Inconsistent Copy"; if the source volume and target volume have consistent data, set the display status to "Copying in progress"; after the target volume has finished copying the source volume, set the display status to "Consistent Copy".

[0081] After stopping remote copying, if inconsistent copying stops, the display status will be set to "Inconsistent copying stopped"; if copying stops during the process, the display status will be set to "Consistent copying stopped"; if consistent copying stops, the display status will be set to "Consistent copying stopped".

[0082] like Figure 3 As shown, in some embodiments, the method further includes:

[0083] S11: When writing data, write the data to the production center source volume;

[0084] S12: Trigger the ROW snapshot mechanism to redirect the metadata to be written to the changed volume of the source volume;

[0085] S13: After the source volume's modified volume data is successfully written, feedback is sent to the user indicating that the data writing is complete;

[0086] S14: After writing is complete, copy the changed volume data from the source volume to the copy volume.

[0087] When user data is written, the ROW snapshot process is followed, redirecting the metadata to be written to the source volume's modified volume, and the data is directly written to the source volume's modified volume. Once the source volume's modified volume has written data, a write success message is immediately displayed, bypassing the COW write wait and improving data write performance. Because the source volume's modified volume is updated in real-time when data is written to the production center, data can be synchronized from the production center to the backup center at any time, eliminating periodic delays and resolving scenarios where a period of data is lost.

[0088] like Figure 4 As shown, in some embodiments, the method further includes:

[0089] S21: When reading data, the corresponding data block is pointed to through the metadata, and the data of the corresponding data block is read from the source volume and the changed volume of the source volume respectively, and the read data is combined;

[0090] S22: Return the combined data to the user and report a successful read.

[0091] When user data is written, a ROW snapshot process is used, redirecting the metadata to be written to the source volume's modified volume, and the data is directly written to the source volume's modified volume. Once the source volume's modified volume writes data, a write success message is immediately displayed, bypassing the COW write wait and improving data write performance. Because the source volume's modified volume is updated in real-time when data is written to the production center, data can be synchronized from the production center to the backup center at any time, eliminating periodic delays and resolving scenarios where a period of data is lost. Simultaneously, a copy volume of the source volume's modified volume is added, enhancing the local disaster recovery capabilities of the production center and providing a means for local data recovery. Furthermore, the source volume and its modified volume replicate the user's data stream, while the copy volume and backup center replicate the data backup stream, isolating the data stream and backup stream to ensure that data does not interfere with each other and reducing business conflicts.

[0092] This invention also provides a real-time protection asynchronous remote replication device based on ROW, including a first creation module, a second creation module, a setting addition module, an interoperability setting module, a remote replication creation module, an execution control module, and a status display module;

[0093] The first creation module is used to create a pool in the production center. After creation, it sequentially creates RAID, source volume, modified volume of the source volume, and copy volume.

[0094] The second creation module is used to create a pool in the backup center. After creation, the RAID, target volume, and target volume change volume are created in sequence.

[0095] The Add module is used to set the ROW snapshot relationship between the source volume and the source volume's changed volume, the copy relationship between the source volume's changed volume and the copy volume, and the snapshot relationship between the target volume and the target volume's changed volume.

[0096] The interoperability configuration module is used to establish interoperability between the production center and the backup center;

[0097] The remote replication creation module is used to create asynchronous remote replication relationships between a copy volume and a target volume.

[0098] The execution control module is used to initiate remote replication and to synchronize the source and target volumes when the data is inconsistent.

[0099] The status display module is used to display the changes in the remote replication status in real time after the remote replication is successfully started.

[0100] In some embodiments, the execution control module includes a judgment unit and a synchronous execution unit;

[0101] The judgment unit is used to determine whether the source volume and the target volume are consistent when remote replication is initiated;

[0102] The synchronization execution unit is used to determine if the data is inconsistent and initiate data synchronization between the source volume and the target volume; after the data synchronization is completed, the determination unit is triggered again.

[0103] In some embodiments, the step of displaying changes in the remote replication status in real time includes:

[0104] The status display module is used to set the display status to "Inconsistent Copy" when the source and target volumes are inconsistent after remote replication is started; "Copying in progress" when the source and target volumes are consistent; "Consistent Copy" when the target volume has finished copying the source volume; "Inconsistent Copy Stopped" when remote replication is stopped; "Consistent Copy Stopped" when copying in progress stops; and "Consistent Copy Stopped" when consistent copying stops.

[0105] In some embodiments, the device further includes a data write execution module, which, when writing data, writes data to the production center source volume; triggers the ROW snapshot mechanism to redirect the metadata of the data to be written to the changed volume of the source volume; after the changed volume data of the source volume is successfully written, it sends a feedback to the user that the data writing is complete; after the writing is completed, it copies the changed volume data of the source volume to the copy volume.

[0106] In some embodiments, the device further includes a data reading execution module, which, when reading data, reads the corresponding data block from the source volume and the modified volume of the source volume respectively by pointing to the corresponding data block through metadata, combines the read data, returns the combined data to the user, and provides feedback that the reading was successful.

[0107] When user data is written, a ROW snapshot process is used, redirecting the metadata to be written to the source volume's modified volume, and the data is directly written to the source volume's modified volume. Once the source volume's modified volume writes data, a write success message is immediately displayed, bypassing the COW write wait and improving data write performance. Because the source volume's modified volume is updated in real-time when data is written to the production center, data can be synchronized from the production center to the backup center at any time, eliminating periodic delays and resolving scenarios where a period of data is lost. Simultaneously, a copy volume of the source volume's modified volume is added, enhancing the local disaster recovery capabilities of the production center and providing a means for local data recovery. Furthermore, the source volume and its modified volume replicate the user's data stream, while the copy volume and backup center replicate the data backup stream, isolating the data stream and backup stream to ensure that data does not interfere with each other and reducing business conflicts.

[0108] This invention also provides an electronic device, comprising: a processor, a communication interface, a memory, and a bus, wherein the processor, communication interface, and memory communicate with each other via the bus. The bus can be used for information transmission between the electronic device and sensors. The processor can call logical instructions in the memory to execute the following method: Step 1: Create a pool in the production center, and after creation, sequentially create RAID, source volume, source volume change volume, and copy volume; Step 2: Create a pool in the backup center, and after creation, sequentially create RAID, target volume, and target volume change volume; Step 3: Set and add ROW snapshot relationships between the source volume and the source volume change volume, add copy relationships between the source volume change volume and the copy volume, and add snapshot relationships between the target volume and the target volume change volume; Step 4: Establish an interconnection between the production center and the backup center; Step 5: Create an asynchronous remote replication relationship from the copy volume to the target volume change volume; Step 6: Start remote replication, and when the source volume and target volume data are inconsistent, start data synchronization between the source volume and the target volume; Step 7: After successful remote replication startup, display the changes in remote replication status in real time.

[0109] In some embodiments, the processor may invoke logical instructions in memory to execute the following method: Step 61: When remote copying starts, determine whether the source volume and the target volume are consistent; if the data are inconsistent, execute step 62; if the data are consistent, execute step 64; Step 62: Start data synchronization between the source volume and the target volume; Step 63: After the data synchronization is completed, determine whether the source volume and the target volume are consistent again; if the data are inconsistent, execute step 62; if the data are consistent, execute step 64; Step 64: Remote copying starts successfully.

[0110] In some embodiments, the processor may invoke logical instructions in memory to execute the following method: S11: When writing data, write the data to the production center source volume; S12: Trigger the ROW snapshot mechanism to redirect the metadata of the data to be written to the changed volume of the source volume; S13: After the changed volume data of the source volume is successfully written, feedback is given that the user data writing is complete; S14: After the writing is completed, copy the changed volume data of the source volume to the copy volume.

[0111] In some embodiments, the processor may invoke logical instructions in memory to execute the following method: S21: When reading data, the corresponding data block is pointed to by the metadata, and the data of the corresponding data block is read from the source volume and the modified volume of the source volume respectively, and the read data is combined; S22: The combined data is returned to the user and feedback is given that the reading was successful.

[0112] Furthermore, the logical instructions in the aforementioned memory can be implemented as software functional units and sold or used as independent products, and can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0113] Although the present invention has been described in detail with reference to the accompanying drawings and preferred embodiments, the invention is not limited thereto. Various equivalent modifications or substitutions can be made to the embodiments of the invention by those skilled in the art without departing from the spirit and essence of the invention, and such modifications or substitutions should all be within the scope of the invention. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the invention should also be covered within the protection scope of the invention. Therefore, the protection scope of the invention should be determined by the scope of the claims.

Claims

1. A real-time protected asynchronous remote replication method based on ROW, characterized in that, Includes the following steps: Create a pool in the production center, and after creation, create RAID, source volume, modified volume of the source volume, and copy volume in sequence; Create a pool in the backup center, and then create the RAID, target volume, and target volume change volume in sequence after creation; Configure the ROW snapshot relationship between the source volume and the source volume's changed volume, the copy relationship between the source volume's changed volume and the copy volume, and the snapshot relationship between the target volume and the target volume's changed volume; Establish interconnection between the production center and the backup center; Creates an asynchronous remote replication relationship between the modified volume and the target volume; Initiate remote replication; if the source and target volumes are inconsistent, initiate data synchronization between the source and target volumes. After successful remote replication, the status changes of remote replication will be displayed in real time.

2. The real-time protected asynchronous remote replication method based on ROW according to claim 1, characterized in that, To initiate remote replication, when the source and target volumes are inconsistent, the steps to synchronize the source and target volumes include: When initiating remote replication, it checks whether the source volume and the target volume are identical; If the data is inconsistent, initiate data synchronization between the source and target volumes. After the data synchronization is completed, check again whether the source volume and the target volume are consistent; Data is consistent; remote replication started successfully.

3. The real-time protected asynchronous remote replication method based on ROW according to claim 2, characterized in that, The steps for displaying real-time changes in remote replication status include: After starting remote replication, if the source volume and target volume have inconsistent data, set the display status to "Inconsistent Copy"; if the source volume and target volume have consistent data, set the display status to "Copying in progress"; after the target volume has finished copying the source volume, set the display status to "Consistent Copy".

4. The real-time protected asynchronous remote replication method based on ROW according to claim 3, characterized in that, The steps for displaying real-time changes in remote replication status also include: After stopping remote copying, if inconsistent copying stops, the display status will be set to "Inconsistent copying stopped"; if copying stops during the process, the display status will be set to "Consistent copying stopped"; if consistent copying stops, the display status will be set to "Consistent copying stopped".

5. The real-time protection asynchronous remote replication method based on ROW according to claim 1, characterized in that, The method also includes: When writing data, the data is written to the production center source volume; Triggering the ROW snapshot mechanism redirects the metadata to be written to the changed volume of the source volume; After the source volume's modified volume data is successfully written, a notification will be sent to the user indicating that the data writing is complete. After the write operation is complete, the changed volume data from the source volume is copied to the copy volume.

6. The real-time protected asynchronous remote replication method based on ROW according to claim 1, characterized in that, The method also includes: During data reading, the corresponding data block is pointed to through the metadata, and the data of the corresponding data block is read from the source volume and the changed volume of the source volume respectively, and the read data is combined. The combined data is returned to the user with a successful read notification.

7. A real-time protected asynchronous remote replication device based on ROW, characterized in that, It includes a first creation module, a second creation module, a settings addition module, an interoperability settings module, a remote copy creation module, an execution control module, and a status display module; The first creation module is used to create a pool in the production center. After creation, it sequentially creates RAID, source volume, modified volume of the source volume, and copy volume. The second creation module is used to create a pool in the backup center. After creation, the RAID, target volume, and target volume change volume are created in sequence. The Add module is used to set the ROW snapshot relationship between the source volume and the source volume's changed volume, the copy relationship between the source volume's changed volume and the copy volume, and the snapshot relationship between the target volume and the target volume's changed volume. The interoperability configuration module is used to establish interoperability between the production center and the backup center; The remote replication creation module is used to create asynchronous remote replication relationships between a copy volume and a target volume. The execution control module is used to initiate remote replication and to synchronize the source and target volumes when the data is inconsistent. The status display module is used to display the changes in the remote replication status in real time after the remote replication is successfully started.

8. The ROW-based real-time protected asynchronous remote replication device according to claim 7, characterized in that, The device also includes a data write execution module, which writes data to the production center source volume during data writing; triggers the ROW snapshot mechanism to redirect the metadata of the data to be written to the changed volume of the source volume; and after the changed volume data of the source volume is successfully written, it sends a feedback to the user that the data writing is complete. After the write operation is complete, the changed volume data from the source volume is copied to the copy volume.

9. The ROW-based real-time protected asynchronous remote replication device according to claim 7, characterized in that, The device also includes a data reading execution module, which, when reading data, points to the corresponding data block through metadata, reads the data of the corresponding data block from the source volume and the modified volume of the source volume respectively, combines the read data, returns the combined data to the user, and provides feedback that the reading was successful.

10. An electronic device, characterized in that, The electronic device includes: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores computer program instructions executable by at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the ROW-based real-time protected asynchronous remote replication method as described in any one of claims 1 to 6.

Citation Information

Patent Citations

  • Data filtering method, and device and data reading system

    CN105938457A

  • System and method for creating an application-consistent remote copy of data using remote mirroring

    CN1900914A