Central-level remote backup disaster recovery system and method

Abstract

The embodiment of the invention discloses a center-level remote backup disaster recovery system and method. The system comprises a production data center, a city-wide disaster recovery data center and a remote disaster recovery data center. For any data center, the data center comprises a service monitoring subsystem, a core service logic subsystem and a data backup subsystem; the core business logic subsystem is used for processing the core business logic of the data center and sending the state of the core business logic subsystem to the business monitoring subsystem; the service monitoring subsystem is used for monitoring the state of the target core service logic subsystem and switching the data center for executing the target core service logic according to the state monitoring result; and the data backup subsystem is used for backing up the data of the data center, realizing centralized management of remote disaster recovery of each data center and automatic fault detection, and ensuring high availability and stability of a multi-center level.

Description

Technical Field

[0001] The disclosed embodiments relate to the technical field of disaster recovery and backup, and in particular to a center-level off-site backup and disaster recovery system and method. Background Art

[0002] Offsite backup disaster recovery technology refers to building two or more sets of identical databases in different geographical locations, and backing up local data to offsite servers in real time to ensure that when a disaster occurs, the original business system can be quickly taken over and operate normally, thereby ensuring data integrity and business continuity.

[0003] In the digital age, off-site disaster recovery strategies are essential for maintaining business continuity and ensuring data security, but existing implementations face increased management complexity and technical challenges brought about by multi-location, multi-component environments. Specifically, the real-time problem of data synchronization is particularly prominent. Due to the delay in data transmission between different geographical locations, how to achieve near-instant data synchronization has become a technical barrier. In addition, the lack of efficient disaster recovery processes and simplified system switching mechanisms has unnecessarily extended the time to recover business operations from disaster events, which further exacerbates the risk of service interruption during recovery and management complexity.

[0004] Existing off-site backup and disaster recovery solutions mainly rely on center-level architecture. Snapshot-based backup solutions are limited by the time delay and non-real-time nature of snapshot creation and recovery, and face certain recovery window challenges. Asynchronous replication solutions asynchronously transmit data to off-site backup centers without interrupting the operation of the primary data center. However, data consistency and transmission efficiency are easily affected by network conditions, and there is a potential risk of data loss. The high construction and operation and maintenance costs of multi-active architectures limit their widespread application in small and medium-sized enterprises. Summary of the invention

[0005] The disclosed embodiments provide a center-level off-site backup disaster recovery system and method, which implements centralized management and automated fault detection of off-site disaster recovery of data centers, and ensures high availability and stability at the multi-center level.

[0006] In a first aspect, a central-level off-site backup disaster recovery system is provided, the system comprising a production data center, a disaster recovery data center in the same city, and a disaster recovery data center in a different location; wherein the disaster recovery data center in the same city and the production data center are located in the same target area; and the disaster recovery data center in a different location and the production data center are located in different target areas;

[0007] For any data center, the data center includes a business monitoring subsystem, a core business logic subsystem and a data backup subsystem;

[0008] The core business logic subsystem is used to process the core business logic of the data center and send the status of the core business logic subsystem to the business monitoring subsystem;

[0009] The business monitoring subsystem is used to monitor the status of the target core business logic subsystem and switch the data center used to execute the target core business logic according to the status monitoring result; the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the data center; the target core business logic is the core business logic corresponding to the core business logic subsystem with abnormal status monitoring result in the target core business logic subsystem;

[0010] The data backup subsystem is used to back up the data of the data center.

[0011] In a second aspect, a center-level off-site backup disaster recovery method is provided, which is applied to any data center in the center-level off-site backup disaster recovery system described in the first aspect, wherein the system includes: a production data center, a disaster recovery data center in the same city, and a disaster recovery data center in a different location; wherein the disaster recovery data center in the same city and the production data center are located in the same target area; and the disaster recovery data center in a different location and the production data center are located in different target areas.

[0012] For any data center, the data center includes a business monitoring subsystem, a core business logic subsystem and a data backup subsystem; the method includes:

[0013] The core business logic subsystem processes the core business logic of the data center and sends the status of the core business logic subsystem to the business monitoring subsystem;

[0014] The business monitoring subsystem performs status monitoring on the target core business logic subsystem, and switches the data center used to execute the target core business logic according to the status monitoring result; the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the data center; the target core business logic is the core business logic corresponding to the core business logic subsystem with abnormal status monitoring result in the target core business logic subsystem;

[0015] The data backup subsystem backs up the data of the data center.

[0016] The disclosed embodiment discloses a center-level off-site backup disaster recovery system and method, the system includes a production data center, a same-city disaster recovery data center and a off-site disaster recovery data center; wherein the same-city disaster recovery data center and the production data center are located in the same target area; the off-site disaster recovery data center and the production data center are located in different target areas; for any data center, the data center includes a business monitoring subsystem, a core business logic subsystem and a data backup subsystem; the core business logic subsystem is used to process the core business logic of the data center and send the status of the core business logic subsystem to the business monitoring subsystem; the business monitoring subsystem is used to monitor the status of the target core business logic subsystem and switch the data center for executing the target core business logic according to the status monitoring result; the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the data center; the target core business logic is the core business logic corresponding to the core business logic subsystem with abnormal status monitoring result in the target core business logic subsystem; the data backup subsystem is used to back up the data of the data center. This technical solution includes a business monitoring subsystem, a core business logic subsystem and a data backup subsystem in each data center. The business monitoring subsystem of each data center monitors the status of the target core business logic subsystem, and switches the data center used to execute the target core business logic according to the status monitoring result, thereby realizing centralized management and automated fault detection of disaster recovery in different locations of each data center, reducing manual intervention and improving recovery efficiency; and real-time monitoring of the load conditions of each node in the data center ensures high availability and stability at the multi-center level.

[0017] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the embodiments of the present disclosure. Other features of the embodiments of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0019] Figure 1 A structural block diagram of a central-level off-site backup disaster recovery system provided in the first embodiment of the present disclosure;

[0020] Figure 2 This is a schematic diagram of a data backup process provided by Embodiment 1 of the present disclosure;

[0021] Figure 3 It is a flowchart of a central-level off-site backup and disaster recovery method provided in the second embodiment of the present disclosure. Specific implementation manners

[0022] In order to enable those skilled in the art of the present technology to better understand the solutions of the embodiments of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all of the embodiments. Based on the embodiments in the embodiments of the present disclosure, all other embodiments obtained by those of ordinary skill in the art without making creative efforts shall fall within the protection scope of the embodiments of the present disclosure.

[0023] It should be noted that the terms "first", "second", etc. in the description and claims of the embodiments of the present disclosure and the above accompanying drawings are used to distinguish similar objects, and do not necessarily need to be used to describe a specific order or sequence. It should be understood that such used data can be interchanged under appropriate circumstances so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device including a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0024] Embodiment 1

[0025] Figure 1 It is a structural block diagram of a central-level off-site backup and disaster recovery system provided in the first embodiment of the present disclosure. As Figure 1 shown, the central-level off-site backup and disaster recovery system 10 includes: a production data center 101, a local disaster recovery data center 102, and an off-site disaster recovery data center 103; wherein, the local disaster recovery data center 102 and the production data center 101 are located in the same target area; the off-site disaster recovery data center 103 and the production data center 101 are located in different target areas.

[0026] For any data center, the data center includes a business monitoring subsystem, a core business logic subsystem and a data backup subsystem. The core business logic subsystem is used to process the core business logic of the data center and send the status of the core business logic subsystem to the business monitoring subsystem; the business monitoring subsystem is used to perform status monitoring on the target core business logic subsystem and switch the data center used to execute the target core business logic according to the status monitoring result; the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the data center; the target core business logic is the core business logic corresponding to the core business logic subsystem with abnormal status monitoring results in the target core business logic subsystem; the data backup subsystem is used to back up the data of the data center. The data center can be Figure 1 The production data center 101, the disaster recovery data center 102 in the same city and the disaster recovery data center 103 in a different location.

[0027] Specifically, in this embodiment, the production data center, the same-city disaster recovery data center, and the remote disaster recovery data center included in the center-level remote backup disaster recovery system can all include a business monitoring subsystem, a core business logic subsystem, and a data backup subsystem. The business monitoring subsystem, the core business logic subsystem, and the data backup subsystem included in each data center can all have the same functions.

[0028] For any data center, the core business logic subsystem is used to process the core business logic of the data center and send the status of the core business logic subsystem to the business monitoring subsystem;

[0029] Specifically, the core business logic can be the most critical and core logic processing part of the data center in the process of providing services and completing tasks. The core business logic can determine the business process of the data center, the data processing method, and the service implementation method. For example, the core business logic can include business logic such as data storage, data processing, data protection, and data distribution. The core business logic subsystem can process the core business logic of the corresponding data center and send the status of the core business logic subsystem to the business monitoring subsystem. The core business logic subsystem can be Figure 1 The core business logic subsystem 1012, the core business logic subsystem 1022 or the core business logic subsystem 1032, that is, Figure 1 The core business logic subsystem 1012, the core business logic subsystem 1022 or the core business logic subsystem 1032 can all implement the functions of the above core business logic subsystems.

[0030] It should be noted that while each component within the core business logic subsystem implements its main function, it also has a status reporting function, so that the business monitoring subsystem can obtain the health status of each component in real time.

[0031] The business monitoring subsystem is used to monitor the status of the target core business logic subsystem and switch the data center used to execute the target core business logic according to the status monitoring results; the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the data center; the target core business logic is the core business logic corresponding to the core business logic subsystem with abnormal status monitoring results in the target core business logic subsystem;

[0032] Specifically, the business monitoring subsystem can monitor the status of the target core business logic subsystem and switch the data center used to execute the target core business logic according to the status monitoring results. Specifically, when the business monitoring subsystem detects that the status of the target core business logic subsystem is abnormal or the performance has declined, it can automatically switch to another data center to execute the target core business logic according to the preset rules and strategies to ensure the continuity and reliability of the business. The business monitoring subsystem can be Figure 1 the business monitoring subsystem 1011, the business monitoring subsystem 1021, or the business monitoring subsystem 1031 in

[0033] Among them, the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the data center corresponding to the business monitoring subsystem; the target core business logic is the core business logic corresponding to the core business logic subsystem with abnormal status monitoring results in the target core business logic subsystem. The business monitoring subsystem

[0034] The data backup subsystem is used to back up the data in the data center.

[0035] Specifically, the data backup subsystem can back up the data in the data center corresponding to the data backup subsystem. The data backup subsystem can be Figure 1 the data backup subsystem 1013, the data backup subsystem 1023, or the data backup subsystem 1033 in

[0036] Such as Figure 1As shown, the production data center 101 may include a business monitoring subsystem 1011, a core business logic subsystem 1012 and a data backup subsystem 1013; the same-city disaster recovery data center 102 may include a business monitoring subsystem 1021, a core business logic subsystem 1022 and a data backup subsystem 1023; and the off-site disaster recovery data center 103 may include a business monitoring subsystem 1031, a core business logic subsystem 1032 and a data backup subsystem 1033.

[0037] Taking the production data center 101 as an example, the core business logic subsystem 1012 is used to process the core business logic of the production data center 101 and send the status of the core business logic subsystem 1012 to the business monitoring subsystem 1011;

[0038] In this embodiment, the production data center 101 is taken as an example, therefore, the core business logic subsystem 1012 can be used to process the core business logic of the production data center 101, and send the status of the core business logic subsystem 1012 to the business monitoring subsystem 1011. The production data center can be a data center that actually runs and provides services, as opposed to a data center in a test or development environment.

[0039] The business monitoring subsystem 1011 is used to monitor the status of the target core business logic subsystem and switch the data center used to execute the target core business logic according to the status monitoring result; the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the production data center 101; the target core business logic is the core business logic corresponding to the core business logic subsystem with abnormal status monitoring result in the target core business logic subsystem;

[0040] Specifically, the target core business logic subsystem may include the core business logic subsystem 1022 corresponding to the local disaster recovery data center 102 and the core business logic subsystem 1032 corresponding to the remote disaster recovery data center 103. The target core business logic may be the core business logic corresponding to the core business logic subsystem with abnormal status monitoring result in the target core business logic subsystem. Exemplarily, if the status monitoring result of the core business logic subsystem 1022 corresponding to the local disaster recovery data center 102 is abnormal, the target core business logic is the core business logic corresponding to the core business logic subsystem 1022.

[0041] Continuing with the above description, by performing status monitoring on the target core business logic subsystem, a status monitoring result can be obtained. Exemplarily, the status monitoring result can include normal or abnormal. And the data center used to execute the target core business logic is switched according to the status monitoring result. Exemplarily, taking the production data center 101 as an example, if the production data center 101 obtains that the status monitoring results of the core business logic subsystem 1022 of the same-city disaster recovery data center 102 and the core business logic subsystem 1032 of the remote disaster recovery data center 103 are both abnormal, then the various components in the core business logic subsystem 1012 of the production data center 101 are started to execute, so that the core business logic subsystem 1012 executes the target core business logic.

[0042] The data backup subsystem 1013 is used to back up the data of the production data center 101 .

[0043] Specifically, the data backup subsystem 1013 can be used to back up data in the production data center 101 .

[0044] It should be noted that the data backup subsystem 1013 can also utilize the cluster composed of internal nodes of the core business logic subsystem 1012 to report the health status of each node in the cluster.

[0045] Taking the local disaster recovery data center 102 as an example, the core business logic subsystem 1022 is used to process the core business logic of the local disaster recovery data center 102 and send the status of the core business logic subsystem 1022 to the business monitoring subsystem 1021;

[0046] In this embodiment, the core business logic subsystem 1022 can be used to process the core business logic of the local disaster recovery data center 102 and send the status of the core business logic subsystem 1022 to the business monitoring subsystem 1021 .

[0047] The business monitoring subsystem 1021 is used to monitor the status of the target core business logic subsystem and switch the data center used to execute the target core business logic according to the status monitoring result; the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the local disaster recovery data center 102; the target core business logic is the core business logic corresponding to the core business logic subsystem with abnormal status monitoring result in the target core business logic subsystem;

[0048] Specifically, the target core business logic subsystem may include the core business logic subsystem 1012 corresponding to the production data center 101 and the core business logic subsystem 1032 corresponding to the remote disaster recovery data center 103. The target core business logic may be the core business logic corresponding to the core business logic subsystem with abnormal status monitoring results in the target core business logic subsystem. Exemplarily, if the status monitoring result of the core business logic subsystem 1012 corresponding to the production data center 101 is abnormal, the target core business logic is the core business logic corresponding to the core business logic subsystem 1012.

[0049] Continuing with the above description, by monitoring the status of the target core business logic subsystem, the status monitoring result can be obtained, and the data center used to execute the target core business logic can be switched according to the status monitoring result. Exemplarily, taking the local disaster recovery data center 102 as an example, if the local disaster recovery data center 102 obtains that the status monitoring results of the core business logic subsystem 1012 of the production data center 101 and the core business logic subsystem 1032 of the remote disaster recovery data center 103 are both abnormal, then the various components in the core business logic subsystem 1022 of the local disaster recovery data center 102 are started to execute, so that the core business logic subsystem 1022 executes the target core business logic.

[0050] The data backup subsystem 1023 is used to back up the data of the local disaster recovery data center 102.

[0051] Specifically, the data backup subsystem 1023 can be used to back up data in the local disaster recovery data center 102. It should be noted that the data backup subsystem 1023 can also use the cluster composed of internal nodes of the core business logic subsystem 1022 to report the health status of each node in the cluster.

[0052] Taking the remote disaster recovery data center 103 as an example, the core business logic subsystem 1032 is used to process the core business logic of the remote disaster recovery data center 103 and send the status of the core business logic subsystem 1032 to the business monitoring subsystem 1031;

[0053] In this embodiment, the core business logic subsystem 1032 can be used to process the core business logic of the remote disaster recovery data center 103 and send the status of the core business logic subsystem 1032 to the business monitoring subsystem 1031 .

[0054] The business monitoring subsystem 1031 is used to monitor the status of the target core business logic subsystem and switch the data center used to execute the target core business logic according to the status monitoring result; the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the remote disaster recovery data center 103; the target core business logic is the core business logic corresponding to the core business logic subsystem with abnormal status monitoring result in the target core business logic subsystem;

[0055] Specifically, the target core business logic subsystem includes the core business logic subsystem 1012 corresponding to the production data center 101 and the core business logic subsystem 1022 corresponding to the local disaster recovery data center 102. The target core business logic may be the core business logic corresponding to the core business logic subsystem with abnormal status monitoring result in the target core business logic subsystem. Exemplarily, if the status monitoring result of the core business logic subsystem 1022 corresponding to the local disaster recovery data center 102 is abnormal, the target core business logic is the core business logic corresponding to the core business logic subsystem 1022.

[0056] Continuing with the above description, by monitoring the status of the target core business logic subsystem, the status monitoring result can be obtained, and the data center used to execute the target core business logic can be switched according to the status monitoring result. Exemplarily, taking the off-site disaster recovery data center 103 as an example, if the off-site disaster recovery data center 103 obtains that the status monitoring results of the core business logic subsystem 1012 of the production data center 101 and the core business logic subsystem 1022 of the same-city disaster recovery data center 102 are both abnormal, then the various components in the core business logic subsystem 1032 of the off-site disaster recovery data center 103 are started to execute, so that the core business logic subsystem 1032 executes the target core business logic.

[0057] The data backup subsystem 1033 is used to back up the data of the remote disaster recovery data center 103 .

[0058] Specifically, the data backup subsystem 1033 can be used to back up data of the remote disaster recovery data center 103. It should be noted that the data backup subsystem 1033 can also use the cluster composed of internal nodes of the core business logic subsystem 1032 to report the health status of each node in the cluster.

[0059] The present embodiment provides a center-level off-site backup disaster recovery system, the system includes a production data center, a disaster recovery data center in the same city and a disaster recovery data center in a different location; wherein the disaster recovery data center in the same city and the production data center are located in the same target area; the disaster recovery data center in a different location and the production data center are located in different target areas; for any data center, the data center includes a business monitoring subsystem, a core business logic subsystem and a data backup subsystem; the core business logic subsystem is used to process the core business logic of the data center and send the status of the core business logic subsystem to the business monitoring subsystem; the business monitoring subsystem is used to perform status monitoring on the target core business logic subsystem and switch the data center used to execute the target core business logic according to the status monitoring result; the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the data center; the target core business logic is the core business logic corresponding to the core business logic subsystem with abnormal status monitoring result in the target core business logic subsystem; the data backup subsystem is used to back up the data of the data center. It realizes centralized management of disaster recovery in different data centers and automated fault detection, reduces manual intervention, and improves recovery efficiency. It also monitors the load of each node in the data center in real time, ensuring high availability and stability at the multi-center level.

[0060] As an optional implementation of this embodiment, the central-level off-site backup and disaster recovery system provided in this embodiment further includes: a rights management subsystem;

[0061] The permission management subsystem is used to manage the access rights of each data center.

[0062] Specifically, the authority management subsystem can manage the access rights of the production data center, the same-city disaster recovery data center, and the remote disaster recovery data center in the center-level remote backup disaster recovery system provided in this embodiment, ensuring the integrity and confidentiality of data transmitted across centers.

[0063] It should be noted that a local load balancer and data caching strategy can be used in each data center in the center-level off-site backup and disaster recovery system provided in this embodiment to achieve fast response, load balancing, and ensure data consistency and continuous operation of core business logic.

[0064] As an optional implementation of this embodiment, the service monitoring subsystem is further used for:

[0065] 1) when the status monitoring results of the target core business logic subsystem are abnormal at the same time, starting the components in the core business logic subsystem to use the core business logic subsystem to process the core business logic of the target core business logic subsystem;

[0066] Specifically, the business monitoring subsystem of each data center can monitor the target core business logic subsystem. If the business monitoring subsystem of each data center detects that the status monitoring results of the target core business logic subsystem are abnormal at the same time, the components within the core business logic subsystem of the data center itself can be started to use the core business logic subsystem to process the core business logic of the target core business logic subsystem.

[0067] It should be noted that the business monitoring subsystem of each data center not only monitors the status of the core business logic subsystems of other data centers except itself, but also monitors the network status and health status of the core business logic subsystems of other data centers except itself, and sets intelligent alarms, intelligently switches to backup data centers, and quickly restores business.

[0068] Exemplarily, taking the production data center 101 as an example, the production data center 101 can monitor the status of the core business logic subsystem 1022 corresponding to the same-city disaster recovery data center 102 and the core business logic subsystem 1032 corresponding to the remote disaster recovery data center 103. If the core business logic subsystem 1022 and the core business logic subsystem 1032 simultaneously produce abnormalities, the components within the core business logic subsystem 1012 of the production data center 101 can be started to use the core business logic subsystem 1012 to process the core business logic of the target core business logic subsystem.

[0069] Exemplarily, taking the same-city disaster recovery data center 102 as an example, the same-city disaster recovery data center 102 can monitor the status of the core business logic subsystem 1012 corresponding to the production data center 101 and the core business logic subsystem 1032 corresponding to the remote disaster recovery data center 103. If the core business logic subsystem 1012 and the core business logic subsystem 1032 have abnormalities at the same time, the components within the core business logic subsystem 1022 of the same-city disaster recovery data center 102 can be started to use the core business logic subsystem 1022 to process the core business logic of the target core business logic subsystem.

[0070] Exemplarily, taking the off-site disaster recovery data center 103 as an example, the off-site disaster recovery data center 103 can monitor the status of the core business logic subsystem 1012 corresponding to the production data center 101 and the core business logic subsystem 1022 corresponding to the same-city disaster recovery data center 102. If the core business logic subsystem 1012 and the core business logic subsystem 1022 simultaneously produce abnormalities, the components within the core business logic subsystem 1032 of the off-site disaster recovery data center 103 can be started to use the core business logic subsystem 1032 to process the core business logic of the target core business logic subsystem.

[0071] 2) When the status monitoring results of the target core business logic subsystem are not abnormal at the same time, asynchronous replication between the first data center and the second data center is achieved through the data backup subsystem of the first data center and the data backup subsystem of the second data center;

[0072] The first data center is a data center corresponding to a core business logic subsystem whose status monitoring result is abnormal in the target core business logic subsystem;

[0073] The second data center is a data center corresponding to a core business logic subsystem whose status monitoring result is normal in the target core business logic subsystem.

[0074] Specifically, if the business monitoring subsystem of each data center detects that the status monitoring results of the target core business logic subsystem are abnormal at different times, asynchronous replication of the first data center and the second data center can be achieved through the data backup subsystem of the first data center and the data backup subsystem of the second data center; wherein the first data center is the data center corresponding to the core business logic subsystem in the target core business logic subsystem whose status monitoring result is abnormal; the second data center is the data center corresponding to the core business logic subsystem in the target core business logic subsystem whose status monitoring result is normal.

[0075] Exemplarily, the production data center 101 can monitor the status of the core business logic subsystem 1022 corresponding to the same-city disaster recovery data center 102 and the core business logic subsystem 1032 corresponding to the remote disaster recovery data center 103. If the core business logic subsystem 1022 is abnormal and the core business logic subsystem 1032 is normal, the same-city disaster recovery data center 102 can be used as the first data center and the remote disaster recovery data center 103 can be used as the second data center. Asynchronous replication can be performed through the data backup subsystem 1023 of the same-city disaster recovery data center 102 and the data backup subsystem 1033 of the remote disaster recovery data center 103 to synchronize the data of the same-city disaster recovery data center 102 and the remote disaster recovery data center 103.

[0076] Exemplarily, the local disaster recovery data center 102 may monitor the status of the core business logic subsystem 1012 corresponding to the production data center 101 and the core business logic subsystem 1032 corresponding to the remote disaster recovery data center 103. If the core business logic subsystem 1012 is abnormal and the core business logic subsystem 1032 is normal, the production data center 101 may be used as the first data center, and the remote disaster recovery data center 103 may be used as the second data center. Asynchronous replication may be performed through the data backup subsystem 1013 of the production data center 101 and the data backup subsystem 1033 of the remote disaster recovery data center 103 to synchronize the data of the production data center 101 and the remote disaster recovery data center 103.

[0077] Exemplarily, the remote disaster recovery data center 103 may monitor the status of the core business logic subsystem 1012 corresponding to the production data center 101 and the core business logic subsystem 1022 corresponding to the local disaster recovery data center 102. If the core business logic subsystem 1012 is abnormal and the core business logic subsystem 1022 is normal, the production data center 101 may be used as the first data center, and the local disaster recovery data center 102 may be used as the second data center. Synchronous replication may be performed through the data backup subsystem 1013 of the production data center 101 and the data backup subsystem 1023 of the local disaster recovery data center 102; if the core business logic subsystem 1012 is normal and the core business logic subsystem 1022 is abnormal, the local disaster recovery data center 102 may be used as the first data center, and the production data center 101 may be used as the second data center. Synchronous replication may be performed through the data backup subsystem 1023 of the local disaster recovery data center 102 and the data backup subsystem 1013 of the production data center 101 to synchronize the data of the production data center 101 and the local disaster recovery data center 102.

[0078] As an optional implementation manner of this embodiment, the data backup subsystem is further configured to:

[0079] 1) Send the first data to be backed up of the data center to the first target data center based on the components in the data backup subsystem to implement synchronous replication of the first data to be backed up by each node in the first target data center; the first target data center and the data center are located in the same target area;

[0080] In this embodiment, the data that needs to be backed up in each data center may be understood as the first data to be backed up, that is, each data center has corresponding first data to be backed up. The first data to be backed up corresponding to the data center may be sent to the first target data center based on the components in the data backup subsystem in each data center to implement synchronous replication of the first data to be backed up by each node in the first target data center.

[0081] The first target center may be used to store the first data to be backed up, and the first target data center and the data center corresponding to the first data to be backed up are located in the same target area. Exemplarily, the same target area may belong to the same city.

[0082] Exemplarily, the production data center 101 and the disaster recovery data center 102 in the same city belong to the same target area (city), so the first data to be backed up of the production data center 101 can be sent to the disaster recovery data center 102 in the same city.

[0083] 2) Based on the components in the data backup subsystem, the second data to be backed up of the data center is backed up to a second target data center to realize the off-site backup incremental synchronous replication of the second data to be backed up by each node in the second target data center; the second data to be backed up is the data that has changed in the data center; the second target data center and the data center are located in different target areas.

[0084] In this embodiment, among the data that needs to be backed up in each data center, the data that has changed can be understood as the second data to be backed up, and the second data to be backed up corresponding to each data center can be sent to the second target data center based on the components in the data backup subsystem in each data center, so as to realize the off-site backup incremental synchronous replication of the second data to be backed up by each node in the second target data center. The second target data center and the data center corresponding to the second data to be backed up are located in different target areas.

[0085] Among them, the remote backup incremental synchronous replication can only copy the data that has changed since the last backup, rather than copying all the data, that is, between data centers in different target areas, only the changed data will be copied, which can save bandwidth resources and speed up data synchronization. At the same time, this method also ensures that the remote data center can quickly restore data in the event of a disaster, reducing the amount of data transmission and the risk of data loss, and improving the efficiency of data transmission between data centers.

[0086] Exemplarily, the production data center 101 and the off-site disaster recovery data center 103 belong to different target areas (cities), so the second to-be-backed-up data of the production data center 101 can be sent to the disaster recovery data center 103 in the same city.

[0087] Figure 2 A schematic diagram of a data backup process provided in this embodiment, such as Figure 2As shown in the figure, the production data center and the local disaster recovery data center can belong to the same target area. Therefore, when the production data center and the local disaster recovery data center transfer the first data to be backed up, synchronous replication can be used to achieve data synchronization between the production data center and the local disaster recovery data center; the production data center and the remote disaster recovery data center belong to different target areas. Therefore, when the production data center and the remote disaster recovery data center transfer the second data to be backed up, asynchronous replication (incremental synchronous replication for remote backup) can be used to complete data backup.

[0088] As an optional implementation manner of this embodiment, the center-level remote backup and disaster recovery system provided in this embodiment further includes: an encryption subsystem;

[0089] The encryption subsystem is used to perform encryption processing on the first data to be backed up and / or the second data to be backed up based on an encryption algorithm when the data backup subsystem performs data backup;

[0090] Specifically, the encryption subsystem can perform encryption processing on the first data to be backed up and / or the second data to be backed up corresponding to each data center based on an encryption algorithm when the data backup subsystem performs data backup. Exemplarily, the encryption algorithm can be a Secure Sockets Layer / Transport Layer Security (SSL / TLS) encryption algorithm.

[0091] It should be noted that the encryption subsystem can also be used to encrypt data when data is transmitted between each data center in the center-level remote backup and disaster recovery system to ensure the confidentiality of the transmitted data during cross-center transmission.

[0092] As an optional implementation manner of this embodiment, the service monitoring subsystem is further used for:

[0093] 1) Caching the hot data information of the data center to a target storage location; the hot data information includes at least configuration data and stability data;

[0094] In this embodiment, the hot data information includes at least configuration data and stability data. Among them, the configuration data can be the configuration data of the data center, and the stability data can be the data that will not change within a preset time period.

[0095] Specifically, each data center can correspond to different hot data, and the hot data corresponding to each data center can be cached to the target storage location corresponding to each data center respectively. Exemplarily, the target storage location can be Redis. Redis can be an open-source high-performance key-value storage database, and Redis can support various types of data structures, such as strings, lists, sets, ordered sets, hash tables, etc.

[0096] 2) The core business logic subsystem is also used to dynamically allocate the core business logic to be processed based on load balancing rules.

[0097] In this embodiment, the load balancing rules may be rules that define how to distribute the load based on the current system status and request characteristics. Exemplarily, the load balancing rules may include rules such as polling, least connections, and source address hashing. Specifically, the core business logic subsystem of each data center can dynamically allocate the core business logic to be processed based on the load balancing rules. That is, it can be understood that the core business logic subsystem of each data center can flexibly adjust the resource allocation strategy according to the real-time load situation and request characteristics, rather than being fixed. Through the load balancing rules, the core business logic subsystem of each data center can reasonably allocate the core business logic to be processed to different servers or processing units. In this way, the system resources can be fully utilized to avoid the situation where some servers are overloaded while other servers are idle, thereby improving the overall processing power and efficiency.

[0098] As an optional implementation of this embodiment, the business monitoring subsystem further includes an intelligent alarm unit; the intelligent alarm unit is used to issue an alarm according to the status detection result.

[0099] Specifically, the business monitoring subsystem of each data center also includes an intelligent alarm unit; the intelligent alarm unit is used to issue an alarm based on the status detection result.

[0100] This technical solution introduces a business monitoring subsystem to unify the management and scheduling of the core business logic subsystem and the data backup subsystem, and through flexible replication control strategies and automated fault recovery, it achieves a stronger disaster tolerance capability, higher availability, and a more real-time data backup and recovery mechanism.

[0101] Embodiment 2

[0102] Figure 3 A flowchart of a center-level off-site backup disaster recovery method provided in Embodiment 2 of the present disclosure is applied to any data center in a center-level off-site backup disaster recovery system, the system comprising: a production data center, a disaster recovery data center in the same city, and a disaster recovery data center in a different location; wherein the disaster recovery data center in the same city and the production data center are located in the same target area; and the disaster recovery data center in a different location and the production data center are located in different target areas;

[0103] For any data center, the data center includes a business monitoring subsystem, a core business logic subsystem and a data backup subsystem; the method includes:

[0104] S210. The core business logic subsystem processes the core business logic of the data center and sends the status of the core business logic subsystem to the service monitoring subsystem;

[0105] Specifically, the core business logic may be the most critical and core logic processing part in the process of the data center providing services and completing tasks. The core business logic can determine the business processes, data processing methods, and service implementation methods of the data center, etc. Exemplarily, the core business logic may include business logics such as data storage, data processing, data protection, and data distribution. The core business logic subsystem can process the core business logic of the corresponding data center and send the status of the core business logic subsystem to the service monitoring subsystem. It should be noted that while each component within the core business logic subsystem implements its main function, it also has a status reporting function, so that the service monitoring subsystem can obtain the health status of each component in real time.

[0106] S220. The service monitoring subsystem monitors the status of the target core business logic subsystem and switches the data center used to execute the target core business logic according to the status monitoring result; the target core business logic subsystem includes the core business logic subsystems in other data centers except the data center in the system; the target core business logic is the core business logic corresponding to the core business logic subsystem with an abnormal status monitoring result in the target core business logic subsystem.

[0107] Specifically, the service monitoring subsystem can monitor the status of the target core business logic subsystem and switch the data center used to execute the target core business logic according to the status monitoring result. The target core business logic subsystem includes the core business logic subsystems in other data centers except the data center corresponding to the service monitoring subsystem in the system; the target core business logic is the core business logic corresponding to the core business logic subsystem with an abnormal status monitoring result in the target core business logic subsystem.

[0108] S230. The data backup subsystem backs up the data of the data center.

[0109] Specifically, the data backup subsystem can back up the data of the data center corresponding to the data backup subsystem.

[0110] The present embodiment provides a center-level off-site backup disaster recovery method, including: being applied to any data center in a center-level off-site backup disaster recovery system, the system including: a production data center, a disaster recovery data center in the same city, and a disaster recovery data center in a different location; wherein the disaster recovery data center in the same city and the production data center are located in the same target area; the disaster recovery data center in a different location and the production data center are located in different target areas; for any data center, the data center includes a business monitoring subsystem, a core business logic subsystem, and a data backup subsystem; the method includes: the core business logic subsystem processes the core business logic of the data center, and sends the status of the core business logic subsystem to the business monitoring subsystem; the business monitoring subsystem performs status monitoring on the target core business logic subsystem, and switches the data center for executing the target core business logic according to the status monitoring result; the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the data center; the target core business logic is the core business logic corresponding to the core business logic subsystem with an abnormal status monitoring result in the target core business logic subsystem; the data backup subsystem backs up the data of the data center. It realizes centralized management of disaster recovery in different data centers and automated fault detection, reduces manual intervention, and improves recovery efficiency. It also monitors the load of each node in the data center in real time, ensuring high availability and stability at the multi-center level.

[0111] As an optional implementation of this embodiment, the center-level off-site backup disaster recovery method provided by this embodiment further includes:

[0112] 1) When the status monitoring results of the target core business logic subsystem are abnormal at the same time, the business monitoring subsystem starts the components in the core business logic subsystem to use the core business logic subsystem to process the core business logic of the target core business logic subsystem.

[0113] Specifically, the business monitoring subsystem of each data center can monitor the target core business logic subsystem. If the business monitoring subsystem of each data center detects that the status monitoring results of the target core business logic subsystem are abnormal at the same time, the components within the core business logic subsystem of the data center itself can be started to use the core business logic subsystem to process the core business logic of the target core business logic subsystem.

[0114] 2) When the status monitoring results of the target core business logic subsystem are not abnormal at the same time, the business monitoring subsystem implements asynchronous replication between the first data center and the second data center through the data backup subsystem of the first data center and the data backup subsystem of the second data center;

[0115] Among them, the first data center is the data center corresponding to the core business logic subsystem with an abnormal status monitoring result in the target core business logic subsystem;

[0116] The second data center is the data center corresponding to the core business logic subsystem with a normal status monitoring result in the target core business logic subsystem.

[0117] Specifically, if the status monitoring results of the target core business logic subsystem are not simultaneously abnormal as monitored by the business monitoring subsystems of each data center, asynchronous replication between the first data center and the second data center can be achieved through the data backup subsystem of the first data center and the data backup subsystem of the second data center; among them, the first data center is the data center corresponding to the core business logic subsystem with an abnormal status monitoring result in the target core business logic subsystem; the second data center is the data center corresponding to the core business logic subsystem with a normal status monitoring result in the target core business logic subsystem.

[0118] As an optional implementation manner of this embodiment, the center-level off-site backup and disaster recovery method provided in this embodiment further includes:

[0119] 1) Sending the first data to be backed up of the data center to the first target data center based on the components in the data backup subsystem to achieve synchronous replication of the first data to be backed up by each node in the first target data center; the first target data center and the data center are located in the same target area.

[0120] In this embodiment, the data that needs to be backed up in each data center can be understood as the first data to be backed up. Each data center can send the first data to be backed up of the data center to the first target data center based on the components in the data backup subsystem of each data center to achieve synchronous replication of the first data to be backed up by each node in the first target data center.

[0121] Among them, the first target center can be used to store the first data to be backed up. The first target data center and the data center corresponding to the first data to be backed up are located in the same target area. Exemplarily, the same target area can be within the same city.

[0122] 2) Backing up the second data to be backed up of the data center to the second target data center based on the components in the data backup subsystem to achieve off-site backup incremental synchronous replication of the second data to be backed up by each node in the second target data center; the second data to be backed up is the data that has changed in the data center; the second target data center and the data center are located in different target areas.

[0123] In this embodiment, among the data to be backed up in each data center, the changed data can be understood as the second data to be backed up. Each data center can send the second data to be backed up in the data center to the second target data center based on the components in the data backup subsystem within each data center, so as to realize the off-site backup incremental synchronous replication of the second data to be backed up by each node in the second target data center. Among them, the second target data center and the data center corresponding to the second data to be backed up are located in different target regions.

[0124] As an optional implementation manner of this embodiment, the center-level off-site backup and disaster recovery method provided in this embodiment further includes:

[0125] The service monitoring subsystem caches the hot data information of the data center to the target storage location; the hot data information includes at least configuration data and stability data.

[0126] Specifically, the hot data of each data center can be cached to the target storage location.

[0127] The core service logic subsystem dynamically allocates the core service logic to be processed based on the load balancing rule.

[0128] Specifically, the core service logic subsystem of each data center can dynamically allocate the core service logic to be processed based on the load balancing rule.

[0129] The center-level off-site backup and disaster recovery system further includes: an encryption subsystem; the center-level off-site backup and disaster recovery method provided in this embodiment further includes:

[0130] When the data backup subsystem performs data backup, the encryption subsystem encrypts each of the first data to be backed up and / or the second data to be backed up based on the encryption algorithm.

[0131] Specifically, when the data backup subsystem performs data backup, the encryption subsystem can encrypt the first data to be backed up and / or the second data to be backed up corresponding to each data center based on the encryption algorithm.

[0132] It should be noted that the encryption subsystem can also be used to encrypt the data when data is transmitted between each data center in the center-level off-site backup and disaster recovery system, so as to ensure the confidentiality of the data during cross-center transmission.

[0133] The system further includes: a permission management subsystem; the method further includes:

[0134] The permission management subsystem manages the access permissions of each data center;

[0135] The service monitoring subsystem further includes an intelligent alarm unit; the method further includes:

[0136] The intelligent alarm unit issues an alarm according to the status detection result.

[0137] This technical solution proposes a center-level off-site backup disaster recovery method, including production data center, disaster recovery data center in the same city and off-site disaster recovery data center; each center includes business monitoring subsystem, core business logic subsystem and data backup system. Data encryption and permission control are introduced under the multi-center strategy to ensure the integrity and confidentiality of data transmitted across centers. At the same time, local load balancers and data caching strategies are used inside each data center to achieve rapid response, load balancing, and ensure data consistency and continuous operation of the business.

[0138] While the business monitoring subsystem monitors the health status of the core business logic system, it also monitors the network status and health status of the central data center, sets intelligent alarms, intelligently switches to backup data centers, and quickly restores business.

[0139] While implementing their main functions, each component in the core business logic subsystem also has the function of reporting status so that the business monitoring subsystem can obtain the health status of each component in real time.

[0140] While achieving synchronous replication of each node in the same-city data center and incremental synchronous replication of off-site backup, each component in the data backup system also utilizes the cluster composed of nodes within the central-level data center to report the health status of each node in the cluster.

[0141] When the monitoring system of each data center is started, the hot spot data is first cached in Redis, and the business logic to be executed is dynamically allocated using load balancing. At the same time, SSL / TLS encryption is used when transmitting data between data centers to ensure that only authorized users can access the data center. The following is the specific working process of each data center:

[0142] For the production data center, if the health status of the core business logic subsystem of the local disaster recovery data center or the remote disaster recovery data center is found to be an error, then the various components in the business logic system of the production data center will be started. Otherwise, if only the health status of the core business logic subsystem of the local disaster recovery data center is an error and the health status of the core business logic subsystem of the remote disaster recovery data center is correct, then the asynchronous replication of the data backup system of the local disaster recovery data center will be started.

[0143] For the local disaster recovery data center, if the health status of the core business logic subsystems of the production data center and the off-site disaster recovery data center is obtained as incorrect, start executing each component within the business logic system of the local disaster recovery data center; otherwise, if only the health status of the core business logic subsystem of the production center is incorrect and the health status of the core business logic subsystem of the off-site disaster recovery data center is correct, start executing the asynchronous replication of the data backup system of the local disaster recovery data center.

[0144] For the off-site disaster recovery data center, if the health status of the core business logic subsystems of the production data center and the local disaster recovery data center is obtained as incorrect, start executing each component within the business logic system of the off-site disaster recovery data center; otherwise, if the health status of the core business logic subsystem of the production data center is correct, start executing the asynchronous replication of the data backup systems between the production data center and the off-site disaster recovery data center; if the health status of the core business logic subsystem of the local disaster recovery data center is correct, start executing the asynchronous replication of the data backup systems between the local disaster recovery data center and the off-site disaster recovery data center.

[0145] The above technical solution introduces a business monitoring subsystem. Through real-time health checks and status reports on the business components of the data center, the nodes within the database cluster, and the network between the nodes, it realizes the automatic switching of the core business logic of the component data center and the data backup system components between the primary and standby centers. Under the multi-center-level data center strategy, the business monitoring subsystem collects the load conditions of each node within the data center in real time, such as CPU usage rate, memory, response time, etc., and uses load balancing, data caching, and replication control strategies to ensure high availability and stability at the multi-center level.

Claims

1. A central-level off-site backup disaster recovery system, characterized in that: The system includes a production data center, a local disaster recovery data center, and a remote disaster recovery data center; wherein the local disaster recovery data center and the production data center are located in the same target area; the remote disaster recovery data center and the production data center are located in different target areas; For any data center, the data center includes a business monitoring subsystem, a core business logic subsystem and a data backup subsystem; The core business logic subsystem is used to process the core business logic of the data center and send the status of the core business logic subsystem to the business monitoring subsystem; The business monitoring subsystem is used to monitor the status of the target core business logic subsystem and switch the data center used to execute the target core business logic according to the status monitoring result; the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the data center; the target core business logic is the core business logic corresponding to the core business logic subsystem with abnormal status monitoring result in the target core business logic subsystem; The data backup subsystem is used to back up the data of the data center.

2. The system according to claim 1, characterized in that The business monitoring subsystem is also used for: When the status monitoring results of the target core business logic subsystem are abnormal at the same time, starting the components in the core business logic subsystem to use the core business logic subsystem to process the core business logic of the target core business logic subsystem; In the case where the status monitoring results of the target core business logic subsystem are not abnormal at the same time, asynchronous replication between the first data center and the second data center is achieved through the data backup subsystem of the first data center and the data backup subsystem of the second data center; The first data center is a data center corresponding to a core business logic subsystem whose status monitoring result is abnormal in the target core business logic subsystem; The second data center is a data center corresponding to a core business logic subsystem whose status monitoring result is normal in the target core business logic subsystem.

3. The system according to claim 1, characterized in that The data backup subsystem is also used for: Based on the components in the data backup subsystem, the first data to be backed up in the data center is sent to a first target data center to achieve synchronous replication of the first data to be backed up by each node in the first target data center; the first target data center and the data center are located in the same target area; Backing up the second data to be backed up in the data center to a second target data center based on the components in the data backup subsystem, so as to realize the off-site backup incremental synchronous replication of the second data to be backed up by each node in the second target data center; The second data to be backed up is data that has changed in the data center; The second target data center and the data center are located in a different target area.

4. The system according to claim 1, characterized in that The business monitoring subsystem is also used for: Cache the hot data information of the data center to a target storage location; the hot data information includes at least configuration data and stability data; The core business logic subsystem is also used to dynamically allocate the core business logic to be processed based on load balancing rules.

5. The system according to claim 3, characterized in that The system further comprises: an encryption subsystem; The encryption subsystem is used to encrypt each of the first to-be-backed-up data and / or the first to-be-backed-up data based on an encryption algorithm when the data backup subsystem performs data backup; The system also includes: a rights management subsystem; The authority management subsystem is used to manage the access rights of each data center.

6. The system according to claim 1, characterized in that The business monitoring subsystem also includes an intelligent alarm unit; the intelligent alarm unit is used to issue an alarm according to the status detection result.

7. A center-level off-site backup disaster recovery method, characterized in that: Applied to any data center in a center-level off-site backup disaster recovery system, the system includes: a production data center, a local disaster recovery data center and a remote disaster recovery data center; wherein the local disaster recovery data center and the production data center are located in the same target area; the remote disaster recovery data center and the production data center are located in different target areas; For any data center, the data center includes a business monitoring subsystem, a core business logic subsystem and a data backup subsystem; the method includes: The core business logic subsystem processes the core business logic of the data center and sends the status of the core business logic subsystem to the business monitoring subsystem; The business monitoring subsystem performs status monitoring on the target core business logic subsystem, and switches the data center used to execute the target core business logic according to the status monitoring result; the target core business logic subsystem includes the core business logic subsystems in other data centers in the system except the data center; the target core business logic is the core business logic corresponding to the core business logic subsystem with abnormal status monitoring result in the target core business logic subsystem; The data backup subsystem backs up the data of the data center.

8. The method according to claim 7, characterized in that The method further comprises: When the status monitoring results of the target core business logic subsystem are abnormal at the same time, the business monitoring subsystem starts the components in the core business logic subsystem to use the core business logic subsystem to process the core business logic of the target core business logic subsystem; In the case where the status monitoring results of the target core business logic subsystem are not abnormal at the same time, the business monitoring subsystem realizes asynchronous replication between the first data center and the second data center through the data backup subsystem of the first data center and the data backup subsystem of the second data center; The first data center is a data center corresponding to a core business logic subsystem whose status monitoring result is abnormal in the target core business logic subsystem; The second data center is a data center corresponding to a core business logic subsystem whose status monitoring result is normal in the target core business logic subsystem.

9. The method according to claim 7, characterized in that: The method further comprises: Based on the components in the data backup subsystem, the first data to be backed up in the data center is sent to a first target data center to achieve synchronous replication of the first data to be backed up by each node in the first target data center; the first target data center and the data center are located in the same target area; Based on the components in the data backup subsystem, the second data to be backed up of the data center is backed up to a second target data center to realize off-site incremental synchronous replication of the second data to be backed up by each node in the second target data center; the second data to be backed up is the data that has changed in the data center; the second target data center and the data center are located in different target areas.

10. The method according to claim 7, characterized in that The method further comprises: The business monitoring subsystem caches the hot data information of the data center to a target storage location; the hot data information includes at least configuration data and stability data; The core business logic subsystem dynamically allocates the core business logic to be processed based on the load balancing rules; The system further includes: an encryption subsystem; the method further includes: When the data backup subsystem performs data backup, the encryption subsystem encrypts each of the to-be-backed-up data and / or the target backup data based on an encryption algorithm; The system further includes: a rights management subsystem; the method further includes: The authority management subsystem manages the access rights of each data center; The service monitoring subsystem further includes an intelligent alarm unit; the method further includes: The intelligent alarm unit issues an alarm according to the status detection result.

Images