Enterprise disaster backup system, method and related device

Abstract

The application discloses an enterprise disaster backup system, method and related equipment, and through disaster backup operation scheduling management of three centers by a disaster backup operation scheduling management platform, visual management, disaster backup switching and exercise control and disaster backup closed-loop management of a double backup center architecture composed of the three centers can be realized; the visual management can realize real-time visual tracking of the disaster backup switching and recovery process, is favorable for automatic fault positioning and progress control, improves response efficiency of the double backup center architecture, the disaster backup switching and exercise control can carry out normal recovery test and actual combat exercise, is favorable for guaranteeing availability of the double backup center architecture, the disaster backup closed-loop management can form a standardized review mechanism of the results of daily disaster backup exercise and effectiveness verification, reversely drive preplan optimization, strategy iteration and resource complement, and guarantee that disaster backup capability can meet business requirements. The application is widely applied in the field of computer technology.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to an enterprise disaster recovery system, method and related equipment. Background Technology

[0002] Disaster recovery, or disaster backup for short, refers to a comprehensive mechanism that ensures the rapid restoration of data integrity and business continuity after a disaster, through pre-deployed backup resources, technical systems, and emergency plans, in response to sudden catastrophic events such as natural disasters, hardware failures, cyberattacks, and human error. To mitigate diverse disaster risks, ensure business continuity, reduce downtime losses, and meet compliance and regulatory requirements, it is essential to build data center disaster recovery systems.

[0003] Power grid data centers are critical national information infrastructure, supporting core operations such as power grid dispatch and control, power trading, marketing services, distribution automation, and renewable energy grid connection management. Beyond the general disaster recovery needs of data centers, power grid security is directly related to people's livelihoods and social stability. Furthermore, with the large-scale integration of intermittent renewable energy sources such as wind and solar power, the reliance of power grid control systems on real-time computing and data synchronization has significantly increased. This places far greater demands on disaster recovery response speed and data consistency than on traditional power grids, placing even higher demands on the disaster recovery work of power grid data centers.

[0004] Current power grid data centers generally suffer from problems such as prioritizing deployment over verification, insufficient backup effectiveness, inadequate visualization, and a lack of closed-loop management. Specifically, after completing the construction of disaster recovery systems, most institutions lack routine recovery testing and practical drills, and do not conduct regular disaster recovery tests. Most invalid backups are only discovered after a failure occurs, resulting in disaster recovery systems that "appear usable but are actually ineffective." The disaster recovery switchover and recovery process lacks real-time visualization and tracking capabilities, and fault location and progress control rely heavily on manual investigation, resulting in low response efficiency. The results of daily disaster recovery drills and effectiveness verifications have not formed a standardized review mechanism, failing to drive contingency plan optimization, strategy iteration, and resource replenishment. After business system upgrades and architecture adjustments, the synchronous update of disaster recovery strategies lacks a systematic closed loop, leading to a continuous disconnect between disaster recovery capabilities and business needs. Summary of the Invention

[0005] In view of at least one of the above-mentioned technical problems, the purpose of this invention is to provide an enterprise disaster recovery system, method and related equipment.

[0006] On one hand, embodiments of the present invention include an enterprise disaster recovery system, the enterprise disaster recovery system comprising: Main production center; Local disaster recovery center; the local disaster recovery center is located in the same geographical area as the primary production center, and the local disaster recovery center is used as a disaster backup center for the primary production center; Off-site disaster recovery center; the off-site disaster recovery center is located in a different geographical area from the primary production center, and the off-site disaster recovery center is used as a disaster backup center for the primary production center; A disaster recovery operation scheduling and management platform; the disaster recovery operation scheduling and management platform is used to perform disaster recovery operation scheduling and management for three centers; the three centers include the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center.

[0007] Furthermore, the disaster recovery operation scheduling and management of the three centers includes: The three centers are managed visually. Disaster recovery switching and drill control were performed on the three centers. The three centers are subject to closed-loop disaster recovery management.

[0008] Furthermore, the visualization management of the three centers includes: The command visualization for simultaneously conducting drills and switching command scenarios at the three centers; The resources of each of the three centers and the interconnection links between the three centers are visualized respectively. Visualize the disaster recovery effectiveness based on the full data of the disaster recovery operation of the three centers.

[0009] Furthermore, the disaster recovery switchover and drill control of the three centers includes: Basic resource management is performed on the three centers through contingency plan management, scenario management, process management, and script management. The exercise management of the three centers is carried out through the implementation of exercise planning, exercise mode configuration, exercise execution control, and exercise reporting and evaluation. Disaster recovery switchover management is performed on the three centers by executing pre-switchover environment checks, disaster recovery switchover execution, disaster recovery rollback execution, and switchover cleanup and analysis.

[0010] Furthermore, the closed-loop disaster recovery management of the three centers includes: A comprehensive capability assessment of the disaster recovery systems of the three centers was conducted. Implement full lifecycle management of the disaster recovery system for the three centers: The disaster recovery effectiveness of the three centers was verified. When an emergency is detected, the three centers will work together to create a closed-loop emergency response. The three centers perform knowledge and organization management by implementing knowledge base management, organization and permission management, workflow management and message push.

[0011] Furthermore, the disaster recovery operation scheduling and management platform is also used to perform partial heterogeneous redundancy configuration of the operating parameters of the three centers.

[0012] Furthermore, the partial heterogeneous redundancy configuration of the operating parameters of the three centers includes: The configurable operating parameters of each of the three centers are detected respectively; The configurable operating parameters shared by the three centers are combined into an operating parameter combination; The combination of operating parameters is divided into a first part, a second part, and a third part; the first part, the second part, and the third part each include a plurality of configurable operating parameters; The configurable operating parameters corresponding to the primary production center and the same-city disaster recovery center and the first part are all configured as first baseline values, and the configurable operating parameters corresponding to the off-site disaster recovery center and the first part are configured as first differentiated values. The configurable operating parameters corresponding to the primary production center and the off-site disaster recovery center and the second part are all configured as the second baseline values, and the configurable operating parameters corresponding to the same-city disaster recovery center and the second part are configured as the second differentiated values. The configurable operating parameters corresponding to the same-city disaster recovery center, the off-site disaster recovery center, and the third part are all configured to the third baseline value, and the configurable operating parameters corresponding to the primary production center and the third part are configured to the third differentiated value.

[0013] On the other hand, embodiments of the present invention also include an enterprise disaster recovery method, the enterprise disaster recovery method comprising: The system includes a disaster recovery operation scheduling and management platform, a primary production center, a local disaster recovery center, and a remote disaster recovery center. The local disaster recovery center is located in the same geographical area as the primary production center and serves as a disaster backup center for the primary production center. The remote disaster recovery center is located in a different geographical area from the primary production center and serves as a disaster backup center for the primary production center. The disaster recovery operation scheduling and management platform is used to manage the disaster recovery operation of the three centers, including the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center.

[0014] On the other hand, embodiments of the present invention also include a computer device, including a memory and a processor, the memory for storing at least one program, and the processor for loading at least one program to execute the enterprise disaster recovery method of the embodiments.

[0015] On the other hand, embodiments of the present invention also include a computer-readable storage medium storing a processor-executable program, which, when executed by a processor, is used to perform the enterprise disaster recovery method in the embodiments.

[0016] The beneficial effects of this invention are as follows: The enterprise disaster recovery system in the embodiments, through the disaster recovery operation scheduling and management platform, manages the disaster recovery operation of three centers, enabling visualized management, disaster recovery switchover and drill control, and disaster recovery closed-loop management of the dual backup center architecture consisting of the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center. Among these, visualized management enables real-time visualized tracking of the disaster recovery switchover and recovery process, which is conducive to automatic fault location and progress control, improving the response efficiency of the dual backup center architecture. Disaster recovery switchover and drill control enables routine recovery testing and practical drills, which is conducive to ensuring the availability of the dual backup center architecture. Disaster recovery closed-loop management can form a standardized review mechanism for the results of daily disaster recovery drills and effectiveness verification, thereby driving contingency plan optimization, strategy iteration, and resource replenishment, ensuring that disaster recovery capabilities can meet business needs. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of the enterprise disaster recovery system in the embodiment; Figure 2 This is a schematic diagram illustrating the steps executed by the disaster recovery operation scheduling and management platform in this embodiment; Figure 3 This is a schematic diagram illustrating the combination of operating parameters in the embodiment; Figure 4 This is a schematic diagram illustrating the principle of steps S404-S406 in the embodiment. Detailed Implementation

[0018] This embodiment provides an enterprise disaster recovery system. (Refer to...) Figure 1 The enterprise disaster recovery system includes a primary production center, a local disaster recovery center, an off-site disaster recovery center, and a disaster recovery operation scheduling and management platform.

[0019] The three centers—the main production center, the same-city disaster recovery center, and the off-site disaster recovery center—each include multiple servers and storage devices that serve as computing power equipment, support equipment that provides power supply, lighting, ventilation, temperature control, and humidity control for the computing power equipment and storage devices, and buildings used to house these devices.

[0020] Specifically, the primary production center is located in a specific geographical area, such as a district within a city. The same-city disaster recovery center is located in the same geographical area as the primary production center, while the off-site disaster recovery center is located in a different geographical area from the primary production center. The same geographical area can refer to being in the same prefecture-level city or the same municipal district, while different geographical areas can refer to being in different prefecture-level cities or different provinces.

[0021] In this embodiment, the same-city disaster recovery center and the off-site disaster recovery center serve as disaster backup centers for the primary production center, thus forming a dual backup center architecture.

[0022] In this embodiment, the disaster recovery operation scheduling and management platform can be operated by one of the three centers, or by devices outside the three centers. The disaster recovery operation scheduling and management platform performs disaster recovery operation scheduling and management for the three centers.

[0023] In this embodiment, refer to Figure 2 When the disaster recovery operation scheduling and management platform performs disaster recovery operation scheduling and management for the three centers, it can specifically perform the following steps: S1. Implement visual management of the three centers; S2. Conduct disaster recovery switchover and drill control for the three centers; S3. Implement closed-loop disaster recovery management for the three centers.

[0024] In this embodiment, by using a disaster recovery operation scheduling and management platform to manage the disaster recovery operation of the three centers, it is possible to achieve visualized management, disaster recovery switchover and drill control, and disaster recovery closed-loop management of the dual backup center architecture consisting of the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center. Among them, visualized management can realize real-time visualized tracking of the disaster recovery switchover and recovery process, which is conducive to automatic fault location and progress control, and improves the response efficiency of the dual backup center architecture. Disaster recovery switchover and drill control can conduct routine recovery tests and practical drills, which is conducive to ensuring the availability of the dual backup center architecture. Disaster recovery closed-loop management can form a standardized review mechanism for the results of daily disaster recovery drills and effectiveness verification, thereby driving contingency plan optimization, strategy iteration and resource replenishment, ensuring that disaster recovery capabilities can meet business needs.

[0025] In this embodiment, when the disaster recovery operation scheduling and management platform performs step S1, which is the step of visual management of the three centers, it can specifically perform the following steps: S101. Command visualization for simultaneous drills and switching of command scenarios across three centers; S102. Visualize the resources of each of the three centers and the interconnection links between the three centers; S103. Visualize disaster recovery effectiveness based on full disaster recovery operation data from three centers.

[0026] In this embodiment, when the disaster recovery operation scheduling and management platform executes steps S101-S103, it can specifically perform the following process: 1. Command visualization (1) Command scenario of the exercise The disaster recovery operation scheduling and management platform simultaneously executes the following steps for the three centers: the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center: Connect with the disaster recovery drill-related systems of the three centers to collect all basic data and real-time status data of the drill tasks.

[0027] The system aggregates and displays an overview of the drills across the three centers, including drill statistics for each disaster recovery operation scheduling and management platform / digital application, historical drill frequency and duration trends, RPO / RTO targets and their achievement status.

[0028] The organizational structure, personnel sign-in information, and division of responsibilities of the three centers covered in this exercise were displayed in a unified manner.

[0029] The system tracks and displays the overall progress of the three center exercises in real time: marking the current execution stage, current execution task, and pending task, and calculating the percentage of completed stages / steps.

[0030] The data on the time taken for each stage of the drills at the three centers are statistically analyzed and displayed: drill start time, time taken for a single stage switch, cumulative time taken, and estimated completion time.

[0031] The steps for each stage of the three-center drills are displayed in a list format, including the step name, person in charge, execution progress, execution status, and corresponding time.

[0032] Collect and display abnormal information during the three-center exercise process, such as phase switching timeout, switching execution failure, and abnormal personnel check-in.

[0033] (2) Switching command scenarios The disaster recovery operation scheduling and management platform simultaneously executes the following steps for the three centers: the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center: Extract key information from the current handover plan and display it intuitively in the command view, covering the handover resource scope of the three centers.

[0034] Collect and display the triggering reasons for disaster recovery switchover (such as failure events and control operations on the primary production center side).

[0035] The system aggregates and displays an overview of the switchover information for the three centers, including the disaster recovery operation scheduling and management platform / applications involved in the switchover, historical switchover counts and time trends, RPO / RTO targets and actual achieved values.

[0036] The organizational structure, personnel check-in information, and division of responsibilities across the three centers covered by this switchover will be displayed in a unified manner.

[0037] Track and display the overall progress of the three center switching in real time: mark the current execution stage, the current execution task, and the task to be executed, and count the percentage of completed stages / steps.

[0038] The system compiles and displays the time taken for each stage of the three-center switchover: switchover start time, single-stage switchover time, cumulative time taken, and estimated completion time.

[0039] The steps for switching between the three centers are displayed in a list format, including the step name, person in charge, execution progress, execution status, and corresponding time.

[0040] Collect and display abnormal information during the three-center switchover process, such as phase switchover timeout, switchover execution failure, and abnormal personnel check-in.

[0041] 2. Resource visualization The disaster recovery operation scheduling and management platform performs the following steps for the resources of the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center, as well as the interconnection links between the three centers: Storage replication status monitoring: Collect operational status data of the storage layers in the three centers respectively, and display the replication and operational status of the overall storage layer and the storage layer of each system in the three centers in a unified manner, based on the business disaster recovery operation scheduling management platform and the basic disaster recovery operation scheduling management platform.

[0042] Database replication status monitoring: Collect operational status data of the database layers in the three centers respectively, and display the replication and operational status of the overall database layer and the database layers of each system in the three centers in a unified manner, based on the business disaster recovery operation scheduling management platform and the basic disaster recovery operation scheduling management platform.

[0043] Interconnection Channel Status Monitoring: Collect operational status data of interconnection channels (fiber optic cables, etc.) between the primary production center and the same-city disaster recovery center, the primary production center and the off-site disaster recovery center, and the same-city disaster recovery center and the off-site disaster recovery center, and perform unified monitoring and display.

[0044] Network traffic status monitoring: Collect network traffic operation data from three centers, as well as cross-center traffic data between the three centers, and perform unified monitoring and display.

[0045] 3. Disaster recovery effectiveness is visible The disaster recovery operation scheduling and management platform performs the following statistical analysis steps based on the full disaster recovery operation data from the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center: Based on the disaster recovery plan: rank the execution efficiency of all switching and drill tasks between the three centers, break down the time consumption of each key link, compare the actual RTO / RPO values ​​with the target values, and verify the rationality of the process.

[0046] Based on resource type: Rank the switching and execution efficiency of similar resources in the three centers, extract detailed data of high-time-consuming links, and identify directions for efficiency optimization.

[0047] By year / month: Statistics cover the completion status of exercise plans across three centers, display a list of systems that have not completed exercises, and associate them with corresponding contingency plans to be executed.

[0048] From the perspective of information systems: statistically analyze the actual RTO and RPO values ​​of various disaster recovery systems deployed in the three centers, and compare them with the business requirements.

[0049] By yearly / monthly cycle: Statistics on the completion status of disaster recovery switchover between the three centers, displaying a list of switched systems, and linking corresponding contingency plans and scenario information.

[0050] Based on disaster recovery levels, statistical analysis was conducted on disaster recovery data at each level: primary production center - same-city disaster recovery center (same city) and primary production center - off-site disaster recovery center (off-site), and trend comparison and recovery time comparison analysis were performed.

[0051] In this embodiment, when the disaster recovery operation scheduling and management platform executes step S2, which is the step of disaster recovery switchover and drill control for the three centers, it can specifically perform the following steps: S201. Basic resource management is carried out for the three centers through contingency plan management, scenario management, process management, and script management. S202. Conduct exercise management for the three centers by implementing exercise plan development, exercise mode configuration, exercise execution control, and exercise reporting and evaluation. S203. Disaster recovery switchover management is carried out for the three centers by performing pre-switchover environment checks, disaster recovery switchover execution, disaster recovery rollback execution, and switchover closure and analysis.

[0052] In this embodiment, when the disaster recovery operation scheduling and management platform executes steps S201-S203, it can specifically perform the following process: 1. Basic resource management (contingency plans, scenarios, processes, scripts) The disaster recovery operation scheduling and management platform revolves around a disaster recovery system consisting of three centers: the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center, and performs full lifecycle basic configuration management. (1) Contingency Plan Management For the main production center's infrastructure, Southern Power Grid Cloud, cloud-based data center, enterprise middleware, digital applications, and other full resources, as well as the disaster recovery resources corresponding to the same-city disaster recovery center and the off-site disaster recovery center, disaster recovery plans are created, edited, queried, and archived in a categorized manner, forming a unified electronic plan library covering the three centers.

[0053] Specialized contingency plans are defined for switching between the primary production center and the same-city disaster recovery center within the same city, and for switching between the primary production center and the off-site disaster recovery center in different locations. These plans cover all resource levels, including communication channels, data networks, centralized storage, technical disaster recovery operation scheduling and management platforms, enterprise middleware, and digital applications.

[0054] All contingency plans involving the three centers will undergo an approval process and will be officially released after approval. Only the released contingency plans can be used for drills and switchover operations at the three centers.

[0055] It provides the ability to visualize and orchestrate contingency plans, referencing published scenarios and processes, and configuring responsible personnel, target resources (corresponding to the primary production center / same-city disaster recovery center / off-site disaster recovery center), and execution operations for each node of the contingency plan, supporting the reuse of sub-processes.

[0056] (2) Scene Management For different business characteristics of primary production center - same-city disaster recovery center and primary production center - off-site disaster recovery center, create, configure, modify, delete switching scenarios and drill scenarios.

[0057] Built-in general scenario templates: including same-city cluster-level, system-level, and data center-level switching scenarios adapted to the primary production center-same-city disaster recovery center, as well as off-site data center-level switching scenarios adapted to the primary production center-off-site disaster recovery center, supporting the association of corresponding contingency plans, scripts, and processes.

[0058] Establish scenario relationships: link upwards to the contingency plan library and exercise plans, and downwards to executable processes, providing scenario selection for the exercise and switching of the three centers.

[0059] Records all scenario releases and reference data involving the three centers, and supports historical version tracing and querying.

[0060] (3) Process Management The process and steps for creating and configuring disaster recovery involve resources in three centers. Each step can be associated with scripts / interfaces in the three centers, supporting automated execution or manual operation marking.

[0061] Configure the corresponding organizational structure and personnel permissions for processes and steps involving the three centers.

[0062] The three centers' switchover / drill process, once configured, must be approved and released before it can be used in contingency plans and scenarios.

[0063] (4) Script Management A public script library covering all levels of the three centers will be built according to resource categories. This library includes operation scripts for resources such as communication channels, data networks, digital applications, Southern Power Grid Cloud, databases, centralized storage, and enterprise middleware. It supports script creation, deletion, modification, querying, and multi-version management.

[0064] It supports executing single scripts / interfaces or batch scripts / interfaces on target resources in three centers, and returns and parses the execution results.

[0065] It supports transferring and distributing files to target resources in three centers and verifies file consistency.

[0066] The orchestrated disaster recovery operations for the three centers are encapsulated into an external API; job scheduling and task management are supported, and the corresponding jobs are automatically executed in the three centers according to the plan.

[0067] 2. Drill Management The disaster recovery operation scheduling and management platform conducts full-process drills and controls for three centers: the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center. Exercise planning: Develop an exercise plan covering the resources of the three centers, select corresponding contingency plans and scenarios, set the exercise time, objectives, participants, associated hardware and software resources of the three centers, execution scripts and guidance documents, and synchronize the plan to the command visualization view after release.

[0068] Exercise mode configuration: Configure and adapt to three execution modes: desktop exercise, simulation exercise, and live exercise for the three centers.

[0069] Exercise execution control: Based on the selected contingency plan, generate a handover drill instance covering three centers; Before the exercise began, an environmental inspection and confirmation was conducted on the disaster recovery resources and production resources of the three centers. The corresponding switching steps are executed sequentially in the three centers according to the exercise process, supporting both manual and automatic execution, and the script execution log is displayed in real time. Supports start and stop control of the exercise process and real-time tracking of the overall progress; If it is a live-action exercise, after the switchover verification is completed, the three central systems will be switched back, the data environment will be imported back, and business verification will be performed to form a closed loop for the exercise.

[0070] Exercise Report and Evaluation: Based on the full-process data of the exercise from the three centers, an exercise report is automatically generated (including exercise scenario, environmental conditions, personnel involved, step duration, execution results, and RTO / RPO achievement status), and PDF export is supported; the exercise effect is evaluated according to predetermined goals, and an evaluation report is generated and archived.

[0071] 3. Disaster recovery switchover management The disaster recovery operation scheduling and management platform performs full-process switchover control for both intra-city switchover from the primary production center to a local disaster recovery center and inter-city switchover from the primary production center to a remote disaster recovery center. (1) Environmental check before switching It connects to systems such as Cloud Shield to collect real-time operational status data of resources that are switched between the primary production center and the same-city disaster recovery center (or the primary production center and the off-site disaster recovery center).

[0072] Compare the disaster recovery resource configurations of the primary production center and the same-city disaster recovery center (or the primary production center and the off-site disaster recovery center) to quickly identify configuration differences and errors.

[0073] Assess whether the current status of the three centers meets the switching conditions. If there are no abnormalities, allow the switching to begin. If there are abnormalities, alert the risk and send a handling reminder.

[0074] (2) Disaster recovery switchover execution Receive disaster recovery switchover applications and process them through the approval process; the switchover can only be initiated after approval.

[0075] Based on the selected contingency plan, scenario, and process, a one-click switch (automatically calling preset scripts) is performed on the corresponding resources of the three centers, and the status of manual operation steps is marked.

[0076] The system records execution logs and issue events at each stage of the switchover process across the three centers in real time, and tracks the entire switchover progress.

[0077] After the switchover is completed, the resource status and business operation status of the target disaster recovery center in the same city (same-city switchover) or the disaster recovery center in another location (another-location switchover) are automatically verified to confirm that the business has returned to normal.

[0078] (3) Disaster recovery switchover execution Once the primary production center resumes service, the resource service status of the primary production center is checked to verify the data consistency between the primary production center and the disaster recovery center in the same city (or between the primary production center and the disaster recovery center in a different location).

[0079] After verification, a one-click switchback operation is performed to switch the business back from the same-city disaster recovery center or the off-site disaster recovery center to the primary production center.

[0080] After the rollback is completed, the business operation status of the primary production center is automatically verified to confirm the successful rollback.

[0081] (4) Switching between closing and analysis Based on the full-process data of the three-center switchover, a formal switchover report is generated (including the cause of the incident, related contingency plans, environmental conditions, personnel involved, step duration, and execution results), and PDF export is supported.

[0082] Analyze the data throughout the switchover process to assess the achievement of RTO / RPO targets, the impact of anomalies, and the effectiveness of business recovery, and identify areas and processes that can be optimized.

[0083] In this embodiment, when the disaster recovery operation scheduling and management platform executes step S3, which is the step of performing closed-loop disaster recovery management for the three centers, it can specifically perform the following steps: S301. Conduct a comprehensive capability assessment of the disaster recovery system of the three centers; S302. Conduct full lifecycle management of the disaster recovery system for the three centers: S303. Verify the disaster recovery effectiveness of the three centers; S304. When an emergency is detected, the three centers will work together to create a closed-loop emergency response. S305. Knowledge and organization management is carried out through three centers: knowledge base management, organization and access control, workflow management, and message push.

[0084] In this embodiment, when the disaster recovery operation scheduling and management platform executes steps S301-S305, it can specifically perform the following process: 1. Disaster recovery capability assessment The disaster recovery operation scheduling and management platform performs a comprehensive capability assessment of the disaster recovery system across three centers: the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center. Maintain the factors and indicator system for disaster recovery capability assessment, establish the correlation between factors and indicators, and cover the entire level of the disaster recovery operation scheduling and management platform of the three centers' infrastructure, applications, and technology.

[0085] By combining automatic data collection with manual data entry, disaster recovery indicator data at each level of the three centers were obtained.

[0086] The evaluation model is used to assess the disaster recovery capabilities of the primary production center-same-city disaster recovery center and the primary production center-off-site disaster recovery center based on indicator data, and to identify the capability gaps.

[0087] Generates a disaster recovery capability assessment report covering the three centers, supports report querying, modification, and PDF export, and provides decision support for disaster recovery planning, construction, and operation and maintenance of the three centers.

[0088] 2. Disaster recovery plan management The disaster recovery operation scheduling and management platform provides full lifecycle management of the disaster recovery system implementation plan for three centers: the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center. A general template for disaster recovery management is provided, while customized solutions are developed based on the specific circumstances of the three centers, including disaster recovery technology strategies, resource deployment planning, data backup / replication strategies, and system / network switching strategies.

[0089] An approval process is implemented for disaster recovery plans involving three centers. Once approved, the plans are officially released and cannot be modified arbitrarily after release.

[0090] Track the implementation progress and feedback of the plan in the three centers.

[0091] After the solution is implemented, the consistency between the implementation results of the three centers and the design solution will be verified by combining the disaster recovery verification function, thus completing the solution loop.

[0092] 3. Disaster Recovery Verification Management The disaster recovery operation scheduling and management platform verifies the disaster recovery effectiveness of three centers: the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center. The configuration covers verification templates for the three centers, including specific verification items such as network system switching and rollback verification, application system switching and rollback verification, technical disaster recovery operation scheduling and management platform switching and rollback verification, and data backup and recovery verification.

[0093] The corresponding functional modules are invoked to perform verification operations between the three centers.

[0094] The verification results from the three centers were collected, displayed, and exported in a unified manner to confirm the effectiveness of disaster recovery capabilities.

[0095] 4. Disaster recovery and emergency management In the event of an emergency, the disaster recovery operation and scheduling management platform coordinates the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center to execute a closed-loop emergency response: Establish an emergency event database covering various failure scenarios across the three centers, classify and manage event information, and establish automatic matching rules between events and disaster recovery plans.

[0096] When a failure occurs at the primary production center, the disaster recovery operation scheduling and management platform automatically collects event information, matches it with emergency database rules, and automatically reports it to the contingency plan center, supporting automatic or manual matching of the corresponding disaster recovery plan.

[0097] Activate the corresponding emergency response procedures in the contingency plan and dispatch disaster recovery resources from the local disaster recovery center or the off-site disaster recovery center to carry out emergency response.

[0098] After the emergency response is completed, mark the emergency event as closed-loop and retain the entire process record; manage all disaster recovery emergency event records and details involving the three centers in a unified manner.

[0099] 5. Knowledge and Organizational Management Knowledge base management: Build a categorized knowledge base covering the disaster recovery system of the three centers, including content such as risk analysis, business impact, laws and regulations, scenario solutions, and best practices; regularly update and maintain the knowledge base to support knowledge sharing and reuse among the three centers.

[0100] Organization and Access Control: Connect to the company's unified identity system to uniformly manage the organizational structure and personnel permissions of the disaster recovery decision-making, management, and execution agencies covering the three centers.

[0101] Workflow management: Configure workflows for contingency plan approval, drill approval, and switchover approval that are compatible with the three centers, simplifying the approval process.

[0102] Push notifications: For approval notices and emergencies from the three centers, push messages to the relevant personnel via SMS, ELINK and other channels, and retain the full message history.

[0103] In this embodiment, the disaster recovery operation scheduling and management platform also performs the following steps: S4. Configure partial heterogeneous redundancy for the operating parameters of the three centers.

[0104] In this embodiment, when the disaster recovery operation scheduling and management platform performs step S4, which is to configure partial heterogeneous redundancy of the operating parameters of the three centers, it can specifically perform the following steps: S401. Detect the configurable operating parameters of each of the three centers respectively; S402. Combine the configurable operating parameters shared by the three centers into an operating parameter combination; S403. Divide the combination of operating parameters into three parts: Part 1, Part 2, and Part 3. S404. Configure the configurable operating parameters of the primary production center and the same-city disaster recovery center corresponding to the first part to the first baseline value, and configure the configurable operating parameters of the off-site disaster recovery center corresponding to the first part to the first differentiated value. S405. Configure the configurable operating parameters corresponding to the primary production center and the off-site disaster recovery center in the second part to the second baseline value, and configure the configurable operating parameters corresponding to the same-city disaster recovery center in the second part to the second differentiated value. S406. Configure the configurable operating parameters corresponding to the same-city disaster recovery center and the off-site disaster recovery center in the third part to the third baseline value, and configure the configurable operating parameters corresponding to the primary production center in the third part to the third differentiated value.

[0105] In steps S401-S402, the combination of running parameters is as follows: Figure 3 As shown. (Refer to...) Figure 3The combination of operating parameters includes multiple configurable operating parameters such as configurable operating parameter 1 (amount of data to be processed), configurable operating parameter 2 (total computing power scale), configurable operating parameter 3 (total power consumption of electrical equipment), configurable operating parameter 4 (proportion of computing power equipment in operation), configurable operating parameter 5 (proportion of computing power equipment in full load), configurable operating parameter 6 (number of storage devices in operation), configurable operating parameter 7 (number of power supply equipment in operation), configurable operating parameter 8 (average temperature of the data center), and configurable operating parameter 9 (average humidity of the data center).

[0106] In this embodiment, the configurable operating parameters in the operating parameter combination are common to the three centers: the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center. For example, when the primary production center is running, it generates a detectable parameter called configurable operating parameter 3 (total power consumption of electrical equipment), which can have a value of 10MW; the same-city disaster recovery center also generates this detectable parameter, which can have a value of 12MW; and the off-site disaster recovery center also generates this detectable parameter, which can have a value of 15MW. Similarly, each of the three centers generates specific detectable values ​​for other configurable operating parameters. For example, the configurable operating parameter 8 (average temperature of the data center) for the primary production center is 22.3℃, for the same-city disaster recovery center it is 20.7℃, and for the off-site disaster recovery center it is 21.4℃.

[0107] In this embodiment, the configurable operating parameters of each of the three centers can be adjusted. For example, for the primary production center, the configurable operating parameter 3 (total power consumption of electrical equipment) of the primary production center can be adjusted by changing the power supply power of the power supply equipment therein, thereby changing the configurable operating parameter 3 (total power consumption of electrical equipment) of the primary production center from 10MW to other values, such as 12MW, which is the same as the configurable operating parameter 3 (total power consumption of electrical equipment) of the disaster recovery center in the same city.

[0108] In step S403, refer to Figure 3 The operating parameter combination is divided into a first part, a second part, and a third part. Each part includes one or more configurable operating parameters, and the configurable operating parameters in different parts are different. In this embodiment, when dividing the operating parameter combination, the number of configurable operating parameters contained in the first part, the second part, and the third part can be kept the same or roughly balanced. For example, refer to... Figure 3The first part includes three configurable operating parameters: configurable operating parameter 1 (amount of data to be processed), configurable operating parameter 2 (total computing power scale), and configurable operating parameter 3 (total power consumption of electrical equipment). The second part includes three configurable operating parameters: configurable operating parameter 4 (proportion of computing power devices in operation), configurable operating parameter 5 (proportion of computing power devices in full load), and configurable operating parameter 6 (number of storage devices in operation). The third part includes three configurable operating parameters: configurable operating parameter 7 (number of power supply devices in operation), configurable operating parameter 8 (average temperature of the data center), and configurable operating parameter 9 (average humidity of the data center).

[0109] The principle of steps S404-S406 is as follows: Figure 4 As shown.

[0110] Reference Figure 4 In step S404, the configurable operating parameters corresponding to the primary production center and the same-city disaster recovery center and the first part are all configured to the first baseline value, and the configurable operating parameters corresponding to the off-site disaster recovery center and the first part are configured to the first differentiated value.

[0111] In this embodiment, the first reference value is a specific set of numerical values, while the first differentiation value is a set of numerical values ​​that are partially or completely different from the first reference value. For example, in this embodiment, the first reference value is 300GB, 8ETOPS, and 12MW, and the first differentiation value is 500GB, 6ETOPS, and 10MW. Thus, by executing step S404, the configurable operating parameter 1 (data volume to be processed) of the primary production center and the same-city disaster recovery center are both set to the same 300GB, while the configurable operating parameter 1 (data volume to be processed) of the off-site disaster recovery center is set to a different 500GB; the configurable operating parameter 2 (total computing power) of the primary production center and the same-city disaster recovery center are both set to the same 8ETOPS, while the configurable operating parameter 2 (total computing power) of the off-site disaster recovery center is set to a different 6ETOPS; the configurable operating parameter 3 (total power consumption of electrical equipment) of the primary production center and the same-city disaster recovery center are both set to the same 12MW, while the configurable operating parameter 3 (total power consumption of electrical equipment) of the off-site disaster recovery center is set to a different 10MW.

[0112] Reference Figure 4 By executing step S404, the specific values ​​of each configurable operating parameter of the first part of the primary production center are the same as the specific values ​​of each configurable operating parameter of the first part of the same-city disaster recovery center, but they are different from the specific values ​​of each configurable operating parameter of the first part of the off-site disaster recovery center.

[0113] The principle of steps S405-S406 is the same as that of step S404.

[0114] Reference Figure 4 By executing step S405, the specific values ​​of each configurable operating parameter of the second part of the primary production center are the same as the specific values ​​of each configurable operating parameter of the first part of the off-site disaster recovery center. That is, their configurable operating parameter 4 (the proportion of computing power devices in operation), configurable operating parameter 5 (the proportion of computing power devices in full load), and configurable operating parameter 6 (the number of storage devices in operation) correspond to the same value and are equal to the combination of values ​​represented by the second benchmark value. However, the configurable operating parameters of the second part of the same-city disaster recovery center have other values, which are equal to the combination of values ​​represented by the second differentiated value.

[0115] Reference Figure 4 By executing step S406, the specific values ​​of each configurable operating parameter of the third part of the same-city disaster recovery center are the same as the specific values ​​of each configurable operating parameter of the third part of the off-site disaster recovery center. That is, their configurable operating parameter 7 (number of operating power supply equipment), configurable operating parameter 8 (average temperature of the computer room), and configurable operating parameter 9 (average humidity of the computer room) correspond to the same value and are equal to the numerical combination represented by the third benchmark value. However, the configurable operating parameters of the third part of the main production center have other values, which are equal to the numerical combination represented by the third differentiated value.

[0116] In this embodiment, by executing steps S401-S406, the operating parameter combinations of the three centers—the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center—can have their own values, exhibiting a hybrid structure of isomorphism and heterogeneity; for example, referring to... Figure 4The primary production center and the same-city disaster recovery center share the same first part of their operating parameter combinations, while the off-site disaster recovery center has different first part of its operating parameter combinations. Therefore, in terms of the first part of the operating parameter combinations, the primary production center and the same-city disaster recovery center are isomorphic, but heterogeneous with the off-site disaster recovery center. Similarly, in terms of the second part of the operating parameter combinations, the primary production center and the off-site disaster recovery center are isomorphic, but heterogeneous with the same-city disaster recovery center. In the first part of the operating parameter combinations, the same-city disaster recovery center and the off-site disaster recovery center are isomorphic, but heterogeneous with the primary production center. Thus, for any configurable operating parameter in the operating parameter combinations, two isomorphic centers and one heterogeneous center can be determined from the three centers: the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center. The two isomorphic centers are distinguished by... The presence of partially identical configurable operating parameters allows for partial heterogeneous redundancy of these parameters, thereby improving the overall disaster recovery capability of the two centers. Conversely, the presence of a heterogeneous center with different configurable operating parameters helps prevent the heterogeneous center from being affected by a specific configurable operating parameter that causes a failure in either of the two homogeneous centers. In summary, at any given configurable operating parameter, two data centers using identical baseline configurations are homogeneous nodes and the default entities of the system, capable of handling the primary service and maintenance consistency requirements. At the same configurable operating parameter, another data center using a different configuration than the baseline is a heterogeneous node and a proactively introduced risk isolation unit, which can mitigate common-cause failures caused by that configurable operating parameter. Therefore, executing steps S401-S406 helps improve the overall disaster recovery capability of the three centers.

[0117] A computer program that executes the enterprise disaster recovery method in this embodiment can be written into a computer device or storage medium. When the computer program is read out and run, the enterprise disaster recovery method in this embodiment is executed, thereby achieving the same technical effect as the enterprise disaster recovery method in the embodiment.

[0118] It should be noted that, unless otherwise specified, when a feature is referred to as "fixed" or "connected" to another feature, it can be directly fixed or connected to the other feature, or indirectly fixed or connected to the other feature. Furthermore, the descriptions of "upper," "lower," "left," and "right" used in this disclosure are only relative to the relative positional relationships of the components of this disclosure in the accompanying drawings. The singular forms "a" and "the" used in this disclosure are also intended to include the plural forms, unless the context clearly indicates otherwise. Moreover, unless otherwise defined, all technical and scientific terms used in this embodiment have the same meaning as commonly understood by one of ordinary skill in the art. The terminology used in this embodiment specification is only for describing particular embodiments and is not intended to limit the invention. The term "and / or" as used in this embodiment includes any combination of one or more of the associated listed items.

[0119] It should be understood that although various elements may be described in this disclosure using terms such as "second," "third," etc., these elements should not be limited to these terms. These terms are used only to distinguish elements of the same type from one another. For example, an element may also be referred to as a second element without departing from the scope of this disclosure, and similarly, a second element may also be referred to as an element. The use of any and all instances or exemplary language ("e.g.," "such as," etc.) provided in this embodiment is intended only to better illustrate embodiments of the invention and, unless otherwise required, does not impose a limitation on the scope of the invention.

[0120] It should be recognized that embodiments of the present invention can be implemented or carried out by computer hardware, a combination of hardware and software, or by computer instructions stored in a non-transitory computer-readable storage medium. The method can be implemented using standard programming techniques—including a non-transitory computer-readable storage medium configured with a computer program, wherein such a storage medium causes the computer to operate in a specific and predefined manner—according to the methods and drawings described in the specific embodiments. Each program can be implemented in a high-level procedural or object-oriented programming language to communicate with the computer system. However, if desired, the program can be implemented in assembly or machine language. In any case, the language can be a compiled or interpreted language. Furthermore, for this purpose, the program can run on a programmed application-specific integrated circuit (ASIC).

[0121] Furthermore, the procedures described in this embodiment can be performed in any suitable order unless otherwise indicated by this embodiment or otherwise obviously contradict the context. The procedures (or variations and / or combinations thereof) described in this embodiment can be executed under the control of one or more computer systems configured with executable instructions, and can be implemented by hardware or a combination thereof as code (e.g., executable instructions, one or more computer programs, or one or more applications) that commonly executes on one or more processors. A computer program includes a plurality of instructions executable by one or more processors.

[0122] Furthermore, the method can be implemented in a suitable computational disaster recovery operation scheduling and management platform of any type, including but not limited to personal computers, minicomputers, mainframes, workstations, networked or distributed computing environments, standalone or integrated computational disaster recovery operation scheduling and management platforms, or communicating with charged particle tools or other imaging devices, etc. Aspects of the invention can be implemented as machine-readable code stored on a non-transitory storage medium or device, whether removable or integrated into a computational disaster recovery operation scheduling and management platform, such as hard disks, optical read and / or write storage media, RAM, ROM, etc., such that it is readable by a programmable computer, and when the storage medium or device is read by the computer, it can be used to configure and operate the computer to perform the processes described herein. Furthermore, the machine-readable code, or portions thereof, can be transmitted via wired or wireless networks. The invention of this embodiment includes these and other different types of non-transitory computer-readable storage media when such media comprises instructions or programs that implement the steps above in conjunction with a microprocessor or other data processor. When programmed according to the method and techniques of the invention, the invention also includes the computer itself.

[0123] A computer program can be applied to input data to perform the functions of this embodiment, thereby transforming the input data to generate output data stored in non-volatile memory. The output information can also be applied to one or more output devices, such as a display. In a preferred embodiment of the invention, the transformed data represents physical and tangible objects, including specific visual depictions of physical and tangible objects generated on the display.

[0124] The above are merely preferred embodiments of the present invention. The present invention is not limited to the above-described embodiments. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention, as long as they achieve the technical effects of the present invention by the same means, should be included within the scope of protection of the present invention. Within the scope of protection of the present invention, the technical solutions and / or implementation methods can have various modifications and variations.

Claims

1. An enterprise disaster recovery system, characterized in that, The enterprise disaster recovery system includes: Main production center; Local disaster recovery center; the local disaster recovery center is located in the same geographical area as the primary production center, and the local disaster recovery center is used as a disaster backup center for the primary production center; Off-site disaster recovery center; the off-site disaster recovery center is located in a different geographical area from the primary production center, and the off-site disaster recovery center is used as a disaster backup center for the primary production center; A disaster recovery operation scheduling and management platform; the disaster recovery operation scheduling and management platform is used to perform disaster recovery operation scheduling and management for three centers; the three centers include the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center.

2. The enterprise disaster recovery system according to claim 1, characterized in that, The disaster recovery operation scheduling and management of the three centers includes: The three centers are managed visually. Disaster recovery switching and drill control were performed on the three centers. The three centers are subject to closed-loop disaster recovery management.

3. The enterprise disaster recovery system according to claim 2, characterized in that, The visualization management of the three centers includes: The command visualization for simultaneously conducting drills and switching command scenarios at the three centers; The resources of each of the three centers and the interconnection links between the three centers are visualized respectively. Visualize the disaster recovery effectiveness based on the full data of the disaster recovery operation of the three centers.

4. The enterprise disaster recovery system according to claim 2, characterized in that, The disaster recovery switchover and drill control of the three centers includes: Basic resource management is performed on the three centers through contingency plan management, scenario management, process management, and script management. The exercise management of the three centers is carried out through the implementation of exercise planning, exercise mode configuration, exercise execution control, and exercise reporting and evaluation. Disaster recovery switchover management is performed on the three centers by executing pre-switchover environment checks, disaster recovery switchover execution, disaster recovery rollback execution, and switchover cleanup and analysis.

5. The enterprise disaster recovery system according to claim 2, characterized in that, The closed-loop disaster recovery management of the three centers includes: A comprehensive capability assessment of the disaster recovery systems of the three centers was conducted. Implement full lifecycle management of the disaster recovery system for the three centers: The effectiveness of disaster recovery at the three centers was verified. When an emergency is detected, the three centers will work together to create a closed-loop emergency response. The three centers perform knowledge and organization management by implementing knowledge base management, organization and permission management, workflow management and message push.

6. The enterprise disaster recovery system according to any one of claims 1-5, characterized in that: The disaster recovery operation scheduling and management platform is also used to configure partial heterogeneous redundancy of the operating parameters of the three centers.

7. The enterprise disaster recovery system according to claim 6, characterized in that, The partial heterogeneous redundancy configuration of the operating parameters of the three centers includes: The configurable operating parameters of each of the three centers are detected respectively; The configurable operating parameters shared by the three centers are combined into an operating parameter combination; The combination of operating parameters is divided into a first part, a second part, and a third part; the first part, the second part, and the third part each include a plurality of configurable operating parameters; The configurable operating parameters corresponding to the primary production center and the same-city disaster recovery center and the first part are all configured as first baseline values, and the configurable operating parameters corresponding to the off-site disaster recovery center and the first part are configured as first differentiated values. The configurable operating parameters corresponding to the primary production center and the off-site disaster recovery center and the second part are all configured as the second baseline values, and the configurable operating parameters corresponding to the same-city disaster recovery center and the second part are configured as the second differentiated values. The configurable operating parameters corresponding to the same-city disaster recovery center, the off-site disaster recovery center, and the third part are all configured to the third baseline value, and the configurable operating parameters corresponding to the primary production center and the third part are configured to the third differentiated value.

8. An enterprise disaster recovery method, characterized in that, The enterprise disaster recovery method includes: The system includes a disaster recovery operation scheduling and management platform, a primary production center, a local disaster recovery center, and a remote disaster recovery center. The local disaster recovery center is located in the same geographical area as the primary production center and serves as a disaster backup center for the primary production center. The remote disaster recovery center is located in a different geographical area from the primary production center and serves as a disaster backup center for the primary production center. The disaster recovery operation scheduling and management platform is used to manage the disaster recovery operation of the three centers, including the primary production center, the same-city disaster recovery center, and the off-site disaster recovery center.

9. A computer device, characterized in that, It includes a memory and a processor, the memory being used to store at least one program, and the processor being used to load at least one program to execute the enterprise disaster recovery method of claim 8.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the enterprise disaster recovery method of claim 8.

Images