Data disaster recovery method, device and architecture, electronic equipment and readable storage medium

By adopting a data disaster recovery architecture with a two-way bucket replication relationship in a cloud computing scenario, and synchronizing data with asynchronous or synchronous mode between the first storage system and the second storage system, the high cost of data disaster recovery in the prior art is solved by using the high and practical data disaster recovery cost in the prior art. The problem of poor performance has achieved low-cost and high-practical data disaster recovery and data security.

CN118945176AActive Publication Date: 2024-11-12JINAN INSPUR DATA TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202411123873.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-15
Publication Date
2024-11-12
Estimated Expiration
2044-08-15

AI Technical Summary

Technical Problem

The existing data disaster recovery implementation methods are costly and poorly practical, making it difficult to achieve low-cost and highly practical data disaster recovery in cloud computing scenarios to ensure the security of storage data.

Method used

Data disaster recovery architecture adopts a two-way bucket replication relationship, synchronizes data through asynchronous or synchronous modes between the first storage system and the second storage system to avoid the problem of double writing of data, and without the need to purchase an additional third-party storage system. Implement data disaster recovery backup.

Benefits of technology

It realizes low-cost and high-practical data disaster recovery, ensures the security of stored data, and provides the selectivity of asynchronous and synchronization modes, improving the flexibility and accuracy of data synchronization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945176A_ABST
    Figure CN118945176A_ABST
Patent Text Reader

Abstract

The invention discloses a data disaster recovery method, device and architecture, electronic equipment, a computer readable storage medium and a computer program product, a first storage system and a second storage system are deployed in the data disaster recovery architecture, the first storage system and the second storage system are disaster recovery storage systems, and a bidirectional bucket copy relationship is preset between the first storage system and the second storage system. The data disaster recovery method is applied to a first storage system and comprises the steps of receiving a target storage object and storing the target storage object in a local disk; determining a current working mode of the data disaster recovery architecture; if the mode is the asynchronous mode, feeding back storage success information to the sending end of the target storage object, and executing the operation of synchronizing the target storage object to the second storage system; and if the mode is the synchronization mode, executing an operation of synchronizing the target storage object to the second storage system until a synchronization success message fed back by the second storage system is received, and then feeding back a storage success message to the sending end. According to the technical scheme, low-cost and high-practicability data disaster tolerance can be realized, and the security of the stored data is effectively ensured.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of storage technology, and in particular to a data disaster recovery method, and also to a data disaster recovery device, architecture, electronic device, computer-readable storage medium, and computer program product. Background Art

[0002] Disaster recovery is an important requirement in cloud computing scenarios, especially in large data center cloud scenarios and cloud scenarios that carry core businesses. Disaster recovery refers to the process of business recovery after a disaster occurs. By establishing one or more identical IT systems in remote locations that are far apart, they can switch between each other or provide services at the same time, in order to ensure business continuity to the greatest extent. When a business system fails due to an accident, the entire business system can be restored in a remote location, so that the business can continue to provide services externally. In the current data disaster recovery implementation process, most of them adopt a single-site deployment method, which does not have disaster recovery capabilities, and then purchase a third-party storage system to implement the disaster recovery function. Obviously, this implementation method is costly and less practical.

[0003] Therefore, how to achieve low-cost and highly practical data disaster recovery to effectively ensure the security of stored data is an urgent problem to be solved by those skilled in the art. Summary of the invention

[0004] The purpose of the present application is to provide a data disaster recovery method, which can achieve low-cost, highly practical data disaster recovery and effectively ensure the security of stored data; another purpose of the present application is to provide a data disaster recovery device, architecture, electronic device, computer-readable storage medium and computer program product, all of which have the above-mentioned beneficial effects.

[0005] In a first aspect, the present application provides a data disaster recovery method, which is applied to a first storage system deployed in a data disaster recovery architecture, wherein the data disaster recovery architecture is further deployed with a second storage system, wherein the first storage system and the second storage system are disaster recovery storage systems for each other, and a bidirectional bucket replication relationship is preset between the first storage system and the second storage system, and the method includes:

[0006] When receiving the target storage object, saving the target storage object to the local disk;

[0007] Determining a current working mode of the data disaster recovery architecture, where the working modes of the data disaster recovery architecture include an asynchronous mode and a synchronous mode;

[0008] If the current working mode is the asynchronous mode, the storage success information is fed back to the sending end of the target storage object, and the operation of synchronizing the target storage object to the second storage system is performed;

[0009] If the current working mode is the synchronization mode, the operation of synchronizing the target storage object to the second storage system is performed until a synchronization success message fed back from the second storage system is received, and the storage success message is fed back to the sending end of the target storage object.

[0010] Optionally, when receiving the target storage object, saving the target storage object to a local disk includes:

[0011] When the target storage object is received, performing data verification on the target storage object to determine whether there is any data block loss in the target storage object;

[0012] When data blocks of the target storage object are lost, determining remaining data blocks and parity blocks in the target storage object, and using the remaining data blocks and the parity blocks to restore data of the target storage object to obtain an original storage object, and saving the original storage object to the local disk;

[0013] When no data block of the target storage object is lost, the target storage object is saved to the local disk.

[0014] Optionally, when receiving the target storage object, saving the target storage object to a local disk includes:

[0015] When the target storage object is received, the target storage object is encrypted using a preset encryption algorithm to obtain an encrypted storage object;

[0016] Using a preset compression algorithm to compress the encrypted storage object to obtain a compressed storage object;

[0017] The compressed storage object is saved to the local disk.

[0018] Optionally, performing an operation of synchronizing the target storage object to the second storage system includes:

[0019] Sending the target storage object to a bucket replication queue;

[0020] According to the arrangement order of the target storage objects in the bucket replication queue, each of the target storage objects is synchronized to the second storage system.

[0021] Optionally, before synchronizing each of the target storage objects to the second storage system according to the arrangement order of each of the target storage objects in the bucket replication queue, the method further includes:

[0022] For each target storage object in the bucket replication queue, record the data state of the target storage object as a waiting state;

[0023] Accordingly, after synchronizing each of the target storage objects to the second storage system according to the arrangement order of each of the target storage objects in the bucket replication queue, the method further includes:

[0024] For each target storage object synchronized to the second storage system, determining whether a synchronization success message corresponding to the target storage object fed back by the second storage system is received;

[0025] When a synchronization success message corresponding to the target storage object is received, the data state of the target storage object is recorded as a completion state;

[0026] When no synchronization success message corresponding to the target storage object is received, recording the data state of the target storage object as a failure state;

[0027] The second storage system is further configured to, after saving the synchronously received target storage object to the local disk, record the data status of the target storage object as a backup completion status and notify the first storage system.

[0028] Optionally, the data disaster recovery method further includes:

[0029] polling all failed storage objects in the first storage system whose data status is the failed status at a preset time interval;

[0030] Each of the failed storage objects is resent to the bucket replication queue so as to resynchronize each of the failed storage objects.

[0031] In a second aspect, the present application further provides a data disaster recovery architecture, in which a first storage system and a second storage system are deployed, the first storage system and the second storage system are disaster recovery storage systems for each other, and a bidirectional bucket replication relationship is preset between the first storage system and the second storage system;

[0032] Among them, the first storage system is used to save the target storage object to the local disk when receiving the target storage object; determine the current working mode of the data disaster recovery architecture, and the working modes of the data disaster recovery architecture include asynchronous mode and synchronous mode; if the current working mode is the asynchronous mode, the storage success information is fed back to the sending end of the target storage object, and the operation of synchronizing the target storage object to the second storage system is performed; if the current working mode is the synchronous mode, the operation of synchronizing the target storage object to the second storage system is performed until a synchronization success message fed back by the second storage system is received, and the storage success message is fed back to the sending end of the target storage object.

[0033] In a third aspect, the present application further provides a data disaster recovery device, which is applied to a first storage system deployed in a data disaster recovery architecture, wherein the data disaster recovery architecture is further deployed with a second storage system, wherein the first storage system and the second storage system are disaster recovery storage systems for each other, and a bidirectional bucket replication relationship is preset between the first storage system and the second storage system, wherein the device comprises:

[0034] A saving module, configured to save the target storage object to a local disk when receiving the target storage object;

[0035] A determination module, used to determine the current working mode of the data disaster recovery architecture, where the working modes of the data disaster recovery architecture include an asynchronous mode and a synchronous mode;

[0036] A first synchronization module, configured to feed back storage success information to a sending end of the target storage object and execute an operation of synchronizing the target storage object to the second storage system if the current working mode is the asynchronous mode;

[0037] The second synchronization module is used to execute the operation of synchronizing the target storage object to the second storage system if the current working mode is the synchronization mode, until receiving the synchronization success message fed back by the second storage system, and feeding back the storage success message to the sending end of the target storage object.

[0038] In a fourth aspect, the present application further discloses an electronic device, comprising:

[0039] Memory for storing computer programs;

[0040] A processor is used to implement the steps of any one of the data disaster recovery methods described above when executing the computer program.

[0041] In a fifth aspect, the present application further discloses a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of any one of the data disaster recovery methods described above are implemented.

[0042] In a sixth aspect, the present invention further discloses a computer program product, including a computer program / instruction, which implements the steps of any one of the data disaster recovery methods described above when executed by a processor.

[0043] The present application provides a data disaster recovery method, which is applied to a first storage system deployed in a data disaster recovery architecture, wherein the data disaster recovery architecture is also deployed with a second storage system, wherein the first storage system and the second storage system are disaster recovery storage systems for each other, and a bidirectional bucket replication relationship is preset between the first storage system and the second storage system, wherein the method comprises: when a target storage object is received, saving the target storage object to a local disk; determining a current working mode of the data disaster recovery architecture, wherein the working modes of the data disaster recovery architecture include an asynchronous mode and a synchronous mode; if the current working mode is the asynchronous mode, feeding back storage success information to a sending end of the target storage object, and executing an operation of synchronizing the target storage object to the second storage system; if the current working mode is the synchronous mode, executing an operation of synchronizing the target storage object to the second storage system, until receiving a synchronization success message fed back by the second storage system, and feeding back the storage success message to the sending end of the target storage object.

[0044] Apply the technical solution provided in this application to construct a data disaster recovery architecture, which includes a first storage system and a second storage system, which are backup disaster recovery systems for each other and have a preset two-way bucket replication relationship, which can be used to achieve real-time data synchronization and ensure that only one storage system (the first storage system or the second storage system) provides storage services to the outside at the same time, avoiding the problem of double writing of data. In this data disaster recovery architecture, after the first storage system receives the target storage object and saves it to its own disk, it can further synchronize the target storage object to the second storage system to achieve data disaster recovery backup. It can be seen that this implementation method does not require the additional purchase of a third-party storage system, has a low implementation cost, is simple and easy to implement, has high practicality, and effectively ensures the security of stored data. In addition, the data disaster recovery architecture in this technical solution provides two different data synchronization modes, which is convenient for users to customize their working modes according to their actual needs, further improving its practicality.

[0045] In one embodiment of the present application, by establishing a bucket replication queue between the first storage system and the second storage system, synchronization operations are performed on each target storage object in the order in which it is received, which can effectively ensure the accuracy of data storage and effectively avoid data conflict problems.

[0046] The data disaster recovery device, architecture, electronic device, computer-readable storage medium and computer program product provided in this application also have the above-mentioned technical effects, and this application will not repeat them here. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] In order to more clearly illustrate the technical solutions in the prior art and the embodiments of the present application, the drawings required for use in the description of the prior art and the embodiments of the present application are briefly introduced below. Of course, the drawings described below in relation to the embodiments of the present application are only part of the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without creative work, and the obtained other drawings also belong to the protection scope of the present application.

[0048] Figure 1 A schematic diagram of the structure of a data disaster recovery architecture provided by this application;

[0049] Figure 2 A flowchart of a data disaster recovery method provided by this application;

[0050] Figure 3 A schematic diagram of another data disaster recovery architecture provided by this application;

[0051] Figure 4 A flowchart of a method for pre-configuring a data disaster recovery architecture provided by this application;

[0052] Figure 5 A schematic diagram of the principle of a data disaster recovery method provided in this application;

[0053] Figure 6 A schematic diagram of the structure of a data disaster recovery device provided by the present application;

[0054] Figure 7 A schematic diagram of the structure of an electronic device provided in this application. DETAILED DESCRIPTION

[0055] The core of the present application is to provide a data disaster recovery method, which can achieve low-cost, highly practical data disaster recovery and effectively ensure the security of stored data; another core of the present application is to provide a data disaster recovery device, architecture, electronic device, computer-readable storage medium and computer program product, all of which have the above-mentioned beneficial effects.

[0056] In order to describe the technical solutions in the embodiments of the present application more clearly and completely, the technical solutions in the embodiments of the present application will be introduced below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0057] An embodiment of the present application provides a data disaster recovery method.

[0058] First, please refer to Figure 1 , Figure 1 This is a structural diagram of a data disaster recovery architecture provided by the present application. A first storage system and a second storage system are deployed in the data disaster recovery architecture. The two storage systems are disaster recovery storage systems for each other, that is, when the first storage system is used as the primary storage system, the second storage system is used as the disaster recovery backup storage system. When the second storage system is used as the primary storage system, the first storage system is used as the disaster recovery backup storage system. In addition, a bidirectional bucket replication relationship is preset between the two systems, which can be used to achieve real-time data synchronization and ensure that only one storage system (the first storage system or the second storage system) provides storage services to the outside at the same time. The data disaster recovery method provided in the embodiment of the present application is based on Figure 1 The data disaster recovery architecture shown is implemented.

[0059] It should be noted that the specific types of the first storage system and the second storage system do not affect the implementation of this technical solution, and can be deployed by technical personnel according to actual needs. For example, in one possible implementation, in order to achieve disaster recovery backup of container metadata, both the first storage system and the second storage system can be object storage systems, that is, the data to be stored in both is container metadata. Furthermore, the object storage system can be specifically minio, which is a high-performance, distributed object storage system designed for cloud-native applications. It uses a simple and easy-to-use method to implement all the functions required for object storage and has excellent performance.

[0060] For further information, please refer to Figure 2 , Figure 2 A schematic diagram of a data disaster recovery method provided in this application, which is applied to Figure 1 The implementation process of the first storage system in the container management application architecture shown (of course, it can also be applied to the second storage system, because the first storage system and the second storage system are disaster recovery backup systems for each other) may include the following S101-S104:

[0061] S101: When a target storage object is received, the target storage object is saved to a local disk.

[0062] This step is intended to achieve the reception and preservation of the target storage object. Specifically, local disks are deployed in both the first storage system and the second storage system to achieve the storage of the data to be stored in the corresponding storage system, and the above-mentioned target storage object is the data to be stored received by the first storage system. For the first storage system, after receiving the target storage object, it can first save the target storage object to the local disk, and then continue to execute subsequent S102~S104 to synchronize the target storage object to the second storage system, so as to achieve disaster recovery backup of the target storage object. Of course, after obtaining the target storage object, the second storage system will also save it to the local disk.

[0063] In one embodiment of the present application, when receiving the target storage object, saving the target storage object to the local disk may include:

[0064] When receiving the target storage object, performing data verification on the target storage object to determine whether there is any data block loss in the target storage object;

[0065] When a data block is lost in the target storage object, the remaining data blocks and parity blocks in the target storage object are determined, and the target storage object is restored using the remaining data blocks and parity blocks to obtain the original storage object, and the original storage object is saved to the local disk;

[0066] When no data block loss exists in the target storage object, the target storage object is saved to the local disk.

[0067] The data disaster recovery method provided in the embodiment of the present application can further realize more accurate data storage. Specifically, after receiving the target storage object, before saving it to the local disk, the target storage object can be firstly checked for integrity to determine whether the target storage object is complete, that is, to determine whether it has a data block loss problem; further, when it is determined that the target storage object has a data block loss, the remaining data blocks and parity blocks therein can be used to perform a data block restoration operation, and the complete original storage object can be obtained and then saved to the local disk; when it is determined that the target storage object has no data block loss, it can be directly saved to the local disk. In the implementation process, the integrity check and data recovery operations on the target storage object can be implemented based on the Velero tool (an open source tool that can safely back up and restore, perform disaster recovery and migration).

[0068] It can be seen that the embodiment of the present application performs integrity verification and data recovery before saving the target storage object, thereby ensuring the integrity of the stored data and achieving more accurate data storage.

[0069] In one embodiment of the present application, when receiving the target storage object, saving the target storage object to the local disk may include:

[0070] When the target storage object is received, the target storage object is encrypted using a preset encryption algorithm to obtain an encrypted storage object;

[0071] Using a preset compression algorithm to compress the encrypted storage object to obtain a compressed storage object;

[0072] Save the compressed storage object to the local disk.

[0073] The data disaster recovery method provided in the embodiment of the present application can further realize more secure and effective data storage. Specifically, the encryption algorithm and the compression algorithm can be pre-set for calling. Then, after receiving the target storage object, before saving it to the local disk, the preset encryption algorithm and the preset compression algorithm can be called in sequence to encrypt and compress the target storage object respectively, to obtain the final compressed storage object, and then save it to the local disk. It can be understood that encryption processing can effectively ensure the security of stored data, and compression processing can effectively save the storage resources occupied by stored data.

[0074] S102: Determine the current working mode of the data disaster recovery architecture. The working modes of the data disaster recovery architecture include an asynchronous mode and a synchronous mode.

[0075] This step is intended to determine the current working mode of the data disaster recovery architecture, so as to perform different types of synchronization operations on the target storage object according to different working modes. Specifically, the working mode of the data disaster recovery architecture can include an asynchronous mode and a synchronous mode, wherein the asynchronous mode refers to a storage response directly to the sender of the target storage data after the storage of the target storage object on the local disk is completed, that is, the storage success information is fed back to the sender of the target storage data as described later, without waiting for the synchronization of the target storage object to be completed; the synchronous mode refers to a storage response to the sender of the target storage data after the storage of the target storage object on the local disk is completed, and the storage success information is fed back to the sender of the target storage data after the synchronization of the target storage object is completed, that is, the storage success information is fed back to the sender of the target storage data. In addition, the setting of the working mode of the data disaster recovery architecture can be customized by the technical personnel in combination with the actual scenario requirements.

[0076] S103: If the current working mode is the asynchronous mode, the storage success information is fed back to the sending end of the target storage object, and the operation of synchronizing the target storage object to the second storage system is performed.

[0077] This step is intended to complete the target storage object synchronization operation in asynchronous mode. Specifically, when it is determined that the current working mode of the data disaster recovery architecture is asynchronous mode, the storage success information can be directly fed back to the sending end of the target storage object, and at the same time, the operation of synchronizing the target storage object to the second storage system is performed, that is, the storage success message is fed back to the sending end of the target storage object and the target storage object is synchronized to the second storage system. The two can be performed at the same time, or the storage success message is fed back to the sending end of the target storage object first, and the target storage object is synchronized to the second storage system later.

[0078] S104: If the current working mode is the synchronization mode, the target storage object is synchronized to the second storage system until a synchronization success message fed back by the second storage system is received, and the storage success message is fed back to the sending end of the target storage object.

[0079] This step is intended to complete the target storage object synchronization operation in the synchronization mode. Specifically, when it is determined that the current working mode of the data disaster recovery architecture is the synchronization mode, the operation of synchronizing the target storage object to the second storage system can be directly executed, and the waiting state can be entered until the synchronization operation is completed, wherein the method of determining that the target storage object synchronization operation is completed is that the first storage system receives the synchronization success message fed back by the second storage system, and then feeds back the storage success message to the sending end of the target storage object.

[0080] It can be seen that the data disaster recovery method provided in the embodiment of the present application constructs a data disaster recovery architecture, which includes a first storage system and a second storage system, which are backup disaster recovery systems for each other and are preset with a two-way bucket replication relationship, which can be used to achieve real-time data synchronization and ensure that only one storage system (the first storage system or the second storage system) provides storage services to the outside at the same time, avoiding the problem of double writing of data. In this data disaster recovery architecture, after the first storage system receives the target storage object and saves it to its own disk, it can further synchronize the target storage object to the second storage system to achieve data disaster recovery backup. It can be seen that this implementation method does not require the additional purchase of a third-party storage system, has a low implementation cost, is simple and easy to implement, has high practicality, and effectively ensures the security of stored data. In addition, the data disaster recovery architecture in the present technical solution provides two different data synchronization modes, which is convenient for users to customize their working modes according to their actual needs, further improving its practicality.

[0081] Based on the above embodiments:

[0082] In one embodiment of the present application, the operation of synchronizing the target storage object to the second storage system may include:

[0083] Send the target storage object to the bucket replication queue;

[0084] According to the arrangement order of the target storage objects in the bucket replication queue, each target storage object is synchronized to the second storage system.

[0085] The embodiment of the present application provides an implementation method for synchronizing the target storage object to the second storage system. It is understandable that in an actual business scenario, the amount of data generated that needs to be stored is generally huge, that is, the number of target storage objects that need to be synchronized in an actual business scenario is not unique. In order to ensure that the data synchronization operation can be carried out in an orderly manner and avoid data synchronization conflicts, a bucket replication queue can be established between the first storage system and the second storage system to store each target storage object that needs to be synchronized between the two. It is understandable that the bucket replication queue follows the first-in-first-out principle. After the target storage object is sent to the bucket replication queue in the order of receipt, each target storage object can be synchronized to the second storage system in sequence according to the arrangement order of each target storage object in the bucket replication queue. Obviously, the reception order of the target storage objects is the arrangement order of each target storage object in the bucket replication queue, that is, the synchronization order of each target storage object.

[0086] It can be seen that the data disaster recovery method provided in the embodiment of the present application, by establishing a bucket replication queue between the first storage system and the second storage system, realizes the synchronization operation of each target storage object in the order of receipt, which can effectively ensure the accuracy of data storage while effectively avoiding data conflict problems.

[0087] In one embodiment of the present application, before synchronizing each target storage object to the second storage system according to the arrangement order of each target storage object in the bucket replication queue, the method may further include:

[0088] For each target storage object in the bucket replication queue, record the data state of the target storage object as a waiting state;

[0089] Accordingly, after synchronizing each target storage object to the second storage system according to the arrangement order of each target storage object in the bucket replication queue, the method may further include:

[0090] For each target storage object synchronized to the second storage system, determining whether a synchronization success message corresponding to the target storage object fed back by the second storage system is received;

[0091] When a synchronization success message corresponding to the target storage object is received, the data state of the target storage object is recorded as a completion state;

[0092] When no synchronization success message corresponding to the target storage object is received, the data state of the target storage object is recorded as a failure state;

[0093] The second storage system is further configured to, after saving the synchronously received target storage object to the local disk, record the data status of the target storage object as a backup completion status and notify the first storage system.

[0094] The data disaster recovery method provided by the embodiment of the present application further realizes the real-time recording of the data status of the target storage object, which helps the technician to determine the real-time status of each target storage object by querying the data status record. Specifically, for each target storage object, after sending the target storage object to the bucket replication queue, its data status can be recorded as a waiting state; after synchronizing the target storage object to the second storage system, its data status can be recorded according to its synchronization result, that is: when it is determined that the synchronization of the target storage object is successful, its data status is recorded as a completed state; when it is determined that the synchronization of the target storage object fails, its data status is recorded as a failed state; and when the synchronization of the target storage object is successful, the second storage system will also record its data status as a backup completed state after saving it to the local disk, and notify the first storage system. In this way, the real-time recording of the data status of each target storage object is realized.

[0095] In one embodiment of the present application, the data disaster recovery method may further include:

[0096] Polling all failed storage objects in the first storage system whose data status is a failed state at a preset time interval;

[0097] Each failed storage object is resent to the bucket replication queue to resynchronize each failed storage object.

[0098] The data disaster recovery method provided in the embodiment of the present application further realizes the post-processing of the disaster recovery failure data, avoiding the problem of inaccurate synchronization caused by the loss of synchronization data. Specifically, the first storage system can perform data polling at a certain time interval to determine all target storage objects whose data status is a failed state, that is, the above-mentioned failed storage objects, that is, poll all target storage objects that have failed synchronization, and resend them to the bucket replication queue to re-execute the data synchronization operation. It can be seen that the embodiment of the present application can repeatedly perform data synchronization operations on target storage objects that have failed synchronization, which can effectively ensure the success rate of data synchronization, thereby avoiding the problem of inaccurate data synchronization caused by the loss of synchronization data.

[0099] In one embodiment of the present application, the data disaster recovery method may further include:

[0100] For each failed storage object whose data status is a failed state, the number of synchronization failures of the failed storage object is recorded;

[0101] Determine whether the number of synchronization failures of the failed storage object reaches a preset number;

[0102] If the number of synchronization failures of the failed storage object reaches the preset number, an alarm event is generated.

[0103] The data disaster recovery method provided in the embodiment of the present application can further realize the alarm function of synchronization failure data. It is understandable that in addition to occasional reasons (such as abnormal communication between the first storage system and the second storage system), data synchronization failure may also have inevitable reasons (such as damage to the storage of the synchronized data itself). Obviously, the former can synchronize the failed storage object to the second storage system by re-executing the synchronization operation, but the latter will still have the problem of data synchronization failure no matter how many times the synchronization operation is repeated. Based on this, the maximum number of times the synchronization operation can be repeatedly executed can be set, that is, the above-mentioned preset number of times, and the number of synchronization failures for each failed storage object can be counted. If the number of synchronization failures reaches the preset number of times, a corresponding alarm event is generated. It should be noted that the specific value of the above-mentioned preset number of times and the specific alarm method of the alarm event do not affect the implementation of the present technical solution. It can be set by technical personnel according to the actual scenario requirements, and this application is not limited here.

[0104] Based on the above embodiments, the embodiment of the present application takes container metadata as an example to provide another data disaster recovery method. The implementation process of the data disaster recovery method is as follows:

[0105] First, please refer to Figure 3 and Figure 4 , Figure 3 This is a schematic diagram of another data disaster recovery architecture provided by this application. Figure 4 A flowchart of a method for pre-configuring a data disaster recovery architecture provided in this application.

[0106] like Figure 3As shown in the figure, a set of minio is deployed at the production site and the disaster recovery site respectively, and a bidirectional bucket replication relationship is set between the two minio. At the same time, only one minio provides external services, and the problem of double data writing will not occur. When the production site is normal, the velero at both sites connects to and accesses the minio at the production site, and the data is synchronized between the two minio; when the production site fails, the velero at both sites connects to and accesses the minio at the disaster recovery site, and the data is reversely synchronized between the two minio. That is: when protection is turned on, the velero at the production site generates backup data → uploads it to the minio at the production site → pulls it to the minio at the disaster recovery site; when the fault is switched, the velero at the disaster recovery site generates backup data → uploads it to the minio at the disaster recovery site → pulls it to the minio at the production site.

[0107] like Figure 4 As shown in the figure, after completing the construction of the data disaster recovery architecture, you can configure it as follows:

[0108] 1. Deploy minio clusters at the primary and backup sites;

[0109] 2. Create a default disaster recovery bucket and set the name to disasterrecovery;

[0110] 3. Establish a bidirectional bucket replication relationship between the primary and backup sites;

[0111] 4. Set up object storage at http: / / cr.ncloudos.com:26000 and select the bucket named disasterrecovery;

[0112] 5. Create a protection group and select the object storage and bucket set in step 4;

[0113] 6. The protection group enables protection, fault switching, and back-cutting, etc.

[0114] For further information, please refer to Figure 5 , Figure 5 The following is a schematic diagram of the principle of a data disaster recovery method provided by this application, and its implementation process is as follows:

[0115] 1. The client uploads object A and object B (target storage objects) to site 1;

[0116] 2. Perform erasure, encryption, compression and other processing on objects A and B respectively. This process can be implemented by calling corresponding algorithms;

[0117] 3. Site 1 stores Object A and Object B on the disk of Site 1 and determines the current working mode: if it is asynchronous mode, it directly returns a success message to the client; if it is synchronous mode, it needs to wait for the object synchronization to complete;

[0118] 4. Pass objects A and B to the bucket replication queue in the order they are received, and set the object status to pending.

[0119] 5. Object A is synchronized to site 2 and the replication is successful. The object status is changed to completed.

[0120] 6. Site 2 changes the object status of the synchronized object A to replica (successful replication status) and writes it to the disk of Site 2;

[0121] 7. Object B fails to be synchronized to site 2, and the object status is changed to failed.

[0122] 8. The failure scanning task scans object B in the replication failure state at a frequency of 1 minute, and re-transfers object B to the bucket replication queue;

[0123] 9. An alarm event may be generated after bucket replication fails. The alarm information can be notified to relevant personnel via email, SMS, etc. so that the problem can be handled in a timely manner.

[0124] It can be seen that the technical solution provided by the embodiment of the present application has the following advantages:

[0125] 1. High availability: Through minio's distributed storage and site replication functions, high availability of container metadata is achieved;

[0126] 2. Data redundancy: The container metadata is corrected and deleted to achieve data redundancy and fault tolerance;

[0127] 3. High flexibility: Supports multi-node and multi-data center disaster recovery architecture, facilitating expansion and upgrade;

[0128] 4. High ease of use: minio adopts a simple and easy-to-use design, which reduces the complexity of implementation and maintenance;

[0129] 5. High security: through real-time synchronization and automatic fault detection, the risk of data loss is greatly reduced;

[0130] 6. Quick response: The disaster recovery module can respond quickly and minimize service interruption time.

[0131] An embodiment of the present application provides a data disaster recovery architecture.

[0132] like Figure 1 As shown, a first storage system and a second storage system are deployed in the data disaster recovery architecture, the first storage system and the second storage system are disaster recovery storage systems for each other, and a bidirectional bucket replication relationship is preset between the first storage system and the second storage system;

[0133] Among them, the first storage system is used to save the target storage object to the local disk when the target storage object is received; determine the current working mode of the data disaster recovery architecture, and the working modes of the data disaster recovery architecture include asynchronous mode and synchronous mode; if the current working mode is asynchronous mode, the storage success information is fed back to the sending end of the target storage object, and the operation of synchronizing the target storage object to the second storage system is executed; if the current working mode is synchronous mode, the operation of synchronizing the target storage object to the second storage system is executed until a synchronization success message fed back by the second storage system is received, and the storage success message is fed back to the sending end of the target storage object.

[0134] It can be seen that the data disaster recovery architecture provided in the embodiment of the present application constructs a data disaster recovery architecture, which includes a first storage system and a second storage system, which are backup disaster recovery systems for each other, and a two-way bucket replication relationship is preset, which can be used to achieve real-time data synchronization, and ensure that only one storage system (the first storage system or the second storage system) provides storage services to the outside at the same time, avoiding the problem of double writing of data. In this data disaster recovery architecture, after the first storage system receives the target storage object and saves it to its own disk, it can further synchronize the target storage object to the second storage system to achieve data disaster recovery backup. It can be seen that this implementation method does not require the additional purchase of a third-party storage system, has a low implementation cost, is simple and easy to implement, has high practicality, and effectively ensures the security of stored data. In addition, the data disaster recovery architecture in the present technical solution provides two different data synchronization modes, which is convenient for users to customize their working modes according to their actual needs, further improving its practicality.

[0135] For an introduction to the architecture provided in the embodiments of the present application, please refer to the above method embodiments, and this application will not go into details here.

[0136] An embodiment of the present application provides a data disaster recovery device.

[0137] Please refer to Figure 6 , Figure 6 This is a structural schematic diagram of a data disaster recovery device provided by the present application. The data disaster recovery device is applied to a first storage system deployed in a data disaster recovery architecture. The data disaster recovery architecture is also deployed with a second storage system. The first storage system and the second storage system are disaster recovery storage systems for each other, and a bidirectional bucket replication relationship is preset between the first storage system and the second storage system. The device may include:

[0138] Saving module 1, used for saving the target storage object to a local disk when receiving the target storage object;

[0139] Determine module 2, used to determine the current working mode of the data disaster recovery architecture, the working mode of the data disaster recovery architecture includes asynchronous mode and synchronous mode;

[0140] The first synchronization module 3 is used for feeding back storage success information to the sending end of the target storage object and performing an operation of synchronizing the target storage object to the second storage system if the current working mode is the asynchronous mode;

[0141] The second synchronization module 4 is used to execute the operation of synchronizing the target storage object to the second storage system if the current working mode is the synchronization mode, until receiving the synchronization success message fed back by the second storage system, and feeding back the storage success message to the sending end of the target storage object.

[0142] It can be seen that the data disaster recovery device provided in the embodiment of the present application constructs a data disaster recovery architecture, which includes a first storage system and a second storage system, which are backup disaster recovery systems for each other and are preset with a two-way bucket replication relationship, which can be used to achieve real-time data synchronization and ensure that only one storage system (the first storage system or the second storage system) provides storage services to the outside at the same time, avoiding the problem of double writing of data. In this data disaster recovery architecture, after the first storage system receives the target storage object and saves it to its own disk, it can further synchronize the target storage object to the second storage system to achieve data disaster recovery backup. It can be seen that this implementation method does not require the additional purchase of a third-party storage system, has a low implementation cost, is simple and easy to implement, has high practicality, and effectively ensures the security of stored data. In addition, the data disaster recovery architecture in the present technical solution provides two different data synchronization modes, which is convenient for users to customize their working modes according to their actual needs, further improving its practicality.

[0143] In one embodiment of the present application, the above-mentioned saving module 1 can be specifically used to perform data verification on the target storage object when the target storage object is received to determine whether there is any data block loss in the target storage object; when the target storage object has data block loss, determine the remaining data blocks and parity blocks in the target storage object, and use the remaining data blocks and parity blocks to restore the data of the target storage object to obtain the original storage object, and save the original storage object to the local disk; when the target storage object does not have any data block loss, save the target storage object to the local disk.

[0144] In one embodiment of the present application, the above-mentioned saving module 1 can be specifically used to encrypt the target storage object using a preset encryption algorithm to obtain an encrypted storage object when a target storage object is received; compress the encrypted storage object using a preset compression algorithm to obtain a compressed storage object; and save the compressed storage object to a local disk.

[0145] In one embodiment of the present application, the first synchronization module 3 may include:

[0146] A sending unit, used to send the target storage object to the bucket replication queue;

[0147] The synchronization unit is used to synchronize each target storage object to the second storage system according to the arrangement order of each target storage object in the bucket replication queue.

[0148] In one embodiment of the present application, the first synchronization module 3 may further include a recording unit for recording, for each target storage object in the bucket replication queue, a data status of the target storage object as a waiting state before synchronizing each target storage object to the second storage system according to the arrangement order of each target storage object in the bucket replication queue; after synchronizing each target storage object to the second storage system according to the arrangement order of each target storage object in the bucket replication queue, for each target storage object synchronized to the second storage system, determining whether a synchronization success message corresponding to the target storage object fed back by the second storage system is received; when a synchronization success message corresponding to the target storage object is received, recording the data status of the target storage object as a completion state; when a synchronization success message corresponding to the target storage object is not received, recording the data status of the target storage object as a failure state; wherein the second storage system is also used to record the data status of the target storage object as a backup completion state after saving the synchronized target storage object to the local disk, and notifying the first storage system.

[0149] In one embodiment of the present application, the above-mentioned first synchronization module 3 may also include a resynchronization unit, which is used to poll all failed storage objects whose data status is a failed state in the first storage system at a preset time interval; and resend each failed storage object to the bucket replication queue to resynchronize each failed storage object.

[0150] For an introduction to the device provided in the embodiments of the present application, please refer to the above method embodiments, and the present application will not elaborate on them here.

[0151] An embodiment of the present application provides an electronic device.

[0152] Please refer to Figure 7 , Figure 7 This is a schematic diagram of the structure of an electronic device provided in this application, and the electronic device may include:

[0153] A memory 11, used for storing computer programs;

[0154] The processor 10 can implement the steps of any one of the above data disaster recovery methods when executing a computer program.

[0155] like Figure 7 , which is a schematic diagram of the composition structure of an electronic device, the electronic device may include: a processor 10, a memory 11, a communication interface 12 and a communication bus 13. The processor 10, the memory 11 and the communication interface 12 all communicate with each other through the communication bus 13.

[0156] In the embodiment of the present application, the processor 10 may be a central processing unit (CPU), an application specific integrated circuit, a digital signal processor, a field programmable gate array or other programmable logic devices, etc.

[0157] The processor 10 may call a program stored in the memory 11. Specifically, the processor 10 may execute operations in the embodiment of the data disaster recovery method.

[0158] The memory 11 is used to store one or more programs, which may include program codes, and the program codes include computer operation instructions. In the embodiment of the present application, the memory 11 at least stores programs for implementing the following functions:

[0159] When receiving the target storage object, saving the target storage object to the local disk;

[0160] Determine the current working mode of the data disaster recovery architecture. The working modes of the data disaster recovery architecture include asynchronous mode and synchronous mode.

[0161] If the current working mode is the asynchronous mode, the storage success information is fed back to the sending end of the target storage object, and the operation of synchronizing the target storage object to the second storage system is performed;

[0162] If the current working mode is the synchronization mode, the operation of synchronizing the target storage object to the second storage system is performed until a synchronization success message fed back by the second storage system is received, and the storage success message is fed back to the sending end of the target storage object.

[0163] In a possible implementation, the memory 11 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required for at least one function, etc.; the data storage area may store data created during use.

[0164] In addition, the memory 11 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device or other volatile solid-state storage device.

[0165] The communication interface 12 may be an interface of a communication module, and is used to connect to other devices or systems.

[0166] Of course, it should be noted that Figure 7 The structure shown does not constitute a limitation on the electronic device in the embodiment of the present application. In actual applications, the electronic device may include Figure 7 More or fewer components than shown, or combinations of certain components.

[0167] An embodiment of the present application provides a computer-readable storage medium.

[0168] The computer-readable storage medium provided in the embodiment of the present application stores a computer program, and when the computer program is executed by a processor, the steps of any one of the above-mentioned data disaster recovery methods can be implemented.

[0169] Among them, the computer-readable storage medium can be any available medium that can be stored in a computer or a data storage device such as a server or data center that includes one or more available media integrated. For example, it can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape, etc.), an optical medium (such as a DVD) or a semiconductor medium (such as a solid-state hard disk) and other media that can store computer program codes.

[0170] For an introduction to the computer-readable storage medium provided in the embodiments of the present application, please refer to the above method embodiments, and the present application will not elaborate on them here.

[0171] An embodiment of the present application provides a computer program product.

[0172] The computer program product provided in the embodiments of the present application includes a computer program / instruction, and when the computer program / instruction is executed by a processor, the steps of any one of the above-mentioned data disaster recovery methods can be implemented.

[0173] Specifically, in the above embodiments, all or part of them can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of them can be implemented in the form of a computer program product.

[0174] Among them, the computer program product may include one or more computer programs / instructions, and when the computer program / instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application may be generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. Computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line, etc.) or wireless (e.g., infrared, wireless, microwave, etc.) means.

[0175] For an introduction to the computer program product provided in the embodiments of the present application, please refer to the above method embodiments, and the present application will not elaborate on them here.

[0176] The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0177] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0178] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0179] The technical solution provided by the present application is described in detail above. The principle and implementation method of the present application are described in detail using specific examples herein, and the description of the above embodiments is only used to help understand the method and core idea of ​​the present application. It should be pointed out that for ordinary technicians in this technical field, without departing from the principle of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the present application.

Claims

1. A data disaster recovery method, characterized in that: Applied to a first storage system deployed in a data disaster recovery architecture, the data disaster recovery architecture further deploys a second storage system, the first storage system and the second storage system are disaster recovery storage systems for each other, and a bidirectional bucket replication relationship is preset between the first storage system and the second storage system, the method includes: When receiving the target storage object, saving the target storage object to the local disk; Determining a current working mode of the data disaster recovery architecture, where the working modes of the data disaster recovery architecture include an asynchronous mode and a synchronous mode; If the current working mode is the asynchronous mode, the storage success information is fed back to the sending end of the target storage object, and the operation of synchronizing the target storage object to the second storage system is performed; If the current working mode is the synchronization mode, the operation of synchronizing the target storage object to the second storage system is performed until a synchronization success message fed back from the second storage system is received, and the storage success message is fed back to the sending end of the target storage object.

2. The data disaster recovery method according to claim 1, characterized in that: When receiving the target storage object, saving the target storage object to the local disk includes: When the target storage object is received, performing data verification on the target storage object to determine whether there is any data block loss in the target storage object; When data blocks of the target storage object are lost, determining remaining data blocks and parity blocks in the target storage object, and using the remaining data blocks and the parity blocks to restore data of the target storage object to obtain an original storage object, and saving the original storage object to the local disk; When no data block of the target storage object is lost, the target storage object is saved to the local disk.

3. The data disaster recovery method according to claim 1, characterized in that: When receiving the target storage object, saving the target storage object to the local disk includes: When the target storage object is received, the target storage object is encrypted using a preset encryption algorithm to obtain an encrypted storage object; Using a preset compression algorithm to compress the encrypted storage object to obtain a compressed storage object; The compressed storage object is saved to the local disk.

4. The data disaster recovery method according to any one of claims 1 to 3, characterized in that: The step of performing an operation of synchronizing the target storage object to the second storage system includes: Sending the target storage object to a bucket replication queue; According to the arrangement order of the target storage objects in the bucket replication queue, each of the target storage objects is synchronized to the second storage system.

5. The data disaster recovery method according to claim 4, characterized in that: Before synchronizing each of the target storage objects to the second storage system according to the arrangement order of each of the target storage objects in the bucket replication queue, the method further includes: For each target storage object in the bucket replication queue, record the data state of the target storage object as a waiting state; Accordingly, after synchronizing each of the target storage objects to the second storage system according to the arrangement order of each of the target storage objects in the bucket replication queue, the method further includes: For each target storage object synchronized to the second storage system, determining whether a synchronization success message corresponding to the target storage object fed back by the second storage system is received; When a synchronization success message corresponding to the target storage object is received, the data state of the target storage object is recorded as a completion state; When no synchronization success message corresponding to the target storage object is received, recording the data state of the target storage object as a failure state; The second storage system is further configured to, after saving the synchronously received target storage object to the local disk, record the data status of the target storage object as a backup completion status and notify the first storage system.

6. The data disaster recovery method according to claim 5, characterized in that: Also includes: polling all failed storage objects in the first storage system whose data status is the failed status at a preset time interval; Each of the failed storage objects is resent to the bucket replication queue so as to resynchronize each of the failed storage objects.

7. A data disaster recovery architecture, characterized in that: A first storage system and a second storage system are deployed in the data disaster recovery architecture, the first storage system and the second storage system are disaster recovery storage systems for each other, and a bidirectional bucket replication relationship is preset between the first storage system and the second storage system; Among them, the first storage system is used to save the target storage object to the local disk when receiving the target storage object; determine the current working mode of the data disaster recovery architecture, and the working modes of the data disaster recovery architecture include asynchronous mode and synchronous mode; if the current working mode is the asynchronous mode, the storage success information is fed back to the sending end of the target storage object, and the operation of synchronizing the target storage object to the second storage system is performed; if the current working mode is the synchronous mode, the operation of synchronizing the target storage object to the second storage system is performed until a synchronization success message fed back by the second storage system is received, and the storage success message is fed back to the sending end of the target storage object.

8. A data disaster recovery device, characterized in that: The device is applied to a first storage system deployed in a data disaster recovery architecture, wherein the data disaster recovery architecture is further deployed with a second storage system, the first storage system and the second storage system are disaster recovery storage systems for each other, and a bidirectional bucket replication relationship is preset between the first storage system and the second storage system, and the device includes: A saving module, configured to save the target storage object to a local disk when receiving the target storage object; A determination module, used to determine the current working mode of the data disaster recovery architecture, where the working modes of the data disaster recovery architecture include an asynchronous mode and a synchronous mode; A first synchronization module, configured to feed back storage success information to a sending end of the target storage object and execute an operation of synchronizing the target storage object to the second storage system if the current working mode is the asynchronous mode; The second synchronization module is used to execute the operation of synchronizing the target storage object to the second storage system if the current working mode is the synchronization mode, until receiving the synchronization success message fed back by the second storage system, and feeding back the storage success message to the sending end of the target storage object.

9. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the data disaster recovery method according to any one of claims 1 to 6 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the data disaster recovery method according to any one of claims 1 to 6 are implemented.

Citation Information

Patent Citations

  • Disaster recovery storage system

    CN102710752A

  • Establishing method and device of IPSAN disaster tolerant system

    CN107391294A

  • A data backup method and a related device

    CN109376037A

  • Container disaster recovery method, system, device and equipment and computer readable storage medium

    CN115658390A

  • Platform-agnostic containerized application data protection

    US20210271564A1