CN116185723B - Database disaster recovery switching exercise method, device, computer equipment and storage medium - Google Patents
Database disaster recovery switching exercise method, device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN116185723B CN116185723B CN202310474940.3A CN202310474940A CN116185723B CN 116185723 B CN116185723 B CN 116185723B CN 202310474940 A CN202310474940 A CN 202310474940A CN 116185723 B CN116185723 B CN 116185723B
- Authority
- CN
- China
- Prior art keywords
- disaster recovery
- plan
- database
- exercise
- switching
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
- Y02A10/00—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE at coastal zones; at river basins
- Y02A10/40—Controlling or monitoring, e.g. of flood or hurricane; Forecasting, e.g. risk assessment or mapping
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The embodiment of the invention discloses a database disaster recovery switching exercise method, a database disaster recovery switching exercise device, computer equipment and a storage medium. The method comprises the following steps: adding asset information of DB2 database production and disaster recovery sides; identifying disaster tolerance pairs according to the characteristic information of the DB2 main and standby ends; selecting a plan type, and arranging the drill plan by combining disaster tolerance pairs to obtain an arranging result; carrying out plan evaluation on the arrangement result; and when the plan evaluation passes, disaster recovery switching exercise is performed on the arrangement result. By implementing the method of the embodiment of the invention, the production and disaster recovery databases can be switched normally during the disaster recovery switching exercise, various error problems caused by misoperation and other factors in the manual mode switching process are avoided, RTO is reduced, service interruption time is shortened, RPO is ensured to meet design requirements, and data is ensured not to be lost.
Description
Technical Field
The invention relates to a database, in particular to a database disaster recovery switching exercise method, a database disaster recovery switching exercise device, computer equipment and a storage medium.
Background
Disaster recovery exercise refers to the process of simulating various emergency situations by adopting certain specific methods and organizing IT personnel to handle various system service recovery. After the database disaster recovery system is built, in order to test and verify the effectiveness of the disaster recovery system, there are three general disaster recovery switching exercise requirements in different scenes, one of which is disaster recovery switching exercise, wherein the disaster recovery switching exercise refers to that when an actual disaster event such as hardware failure and natural disaster occurs in the database, a service is quickly switched to a backup database, the service downtime is shortened, and the continuity and reliability of the service are ensured; the method also comprises planning exercise switching, namely verifying the feasibility and the effectiveness of a database disaster recovery switching scheme through exercise when no actual disaster event occurs. The main steps include: and (3) preparing a disaster recovery switching plan, preparing before disaster recovery switching, performing exercise, and summarizing and evaluating after the exercise. The reliability and efficiency of database disaster recovery switching can be effectively improved through database planning exercise switching. The emergency system also comprises a desktop exercise, wherein the desktop exercise is taken part by a representative or key post personnel of an emergency organization, and according to an emergency plan and a standard workflow thereof, the emergency system is used for carrying out exercise activities which should take actions when an emergency situation is discussed, and the atmosphere is college-type and exploratory. The desktop drilling of the database refers to performing disaster backup availability verification on the disaster recovery database under the condition that the normal operation of the database business of the production end is not affected, and is a high-frequency unreal switching drilling. After the desktop drilling introduction, the newly generated business test data in the drilling process needs to be deleted, and the business test data is recovered to be consistent with the data of the production end.
The existing general treatment method comprises the following steps: manual disaster recovery switching, semi-automatic disaster recovery switching and automatic disaster recovery switching; the manual disaster recovery switching means that the standby database is manually switched into the main database, before the manual disaster recovery switching is performed, the service of the main database is required to be stopped, the service of the standby database is started, and meanwhile, the connection of the application program is directed to the standby database; the semi-automatic disaster recovery switching means that when a main database fails, the disaster recovery switching is performed through manual intervention, and in actual application, an operator can be prompted through a monitoring program to perform the disaster recovery switching; the automatic disaster recovery switching means that when the main database fails, the standby database is automatically switched into the main database; the database service function and the disaster recovery function share a network port; before the exercise, the business department is required to cooperate to stop the application connection. The method is generally suitable for the conditions of low busyness and relatively single business types. However, in a complex business scenario where large data volume, high business pressure, and simultaneous processing of on-line transactions and data analysis business type mix, relying on the above method alone may result in an abnormally complex switching process between production and disaster recovery databases during disaster recovery exercise, and may even severely interfere with original normal business processing.
Manual disaster recovery switching particularly depends on professional DBA (database manager, database Administrator) personnel, is easy to miss or misoperation under the condition of a large number of databases, is particularly stressed when a disaster occurs, is easy to make misoperation to cause larger loss, and can not effectively perform disaster recovery switching under the condition that no professional DBA personnel are on site if a fault occurs late at night; in the semi-automatic disaster recovery switching, specific switching operation is also performed by depending on professional DBA personnel. There are thus also the same drawbacks of manual disaster recovery switching. The automatic disaster recovery switching can only adapt to the scene of disaster recovery switching, the disaster recovery switching exercise requirements of three different scenes for testing and verifying the effectiveness of a disaster recovery system cannot be met, the scenes of planning exercise switching and desktop exercise cannot be met, coordination with a business department is needed before exercise, business can be stopped in advance of exercise so as to stop and switch database services, and due to the fact that application modules are numerous, application servers are distributed and distributed, all application connections are difficult to terminate completely, and it is difficult to predict which part of business is not stopped, and the operation purpose of the mode is only to realize smooth switching of roles of a database, but does not necessarily meet the situation that the roles need to be switched in a real scene. Therefore, this method may not actually perform the role of handover exercise, nor may it cover the complexity of the service entirely.
Therefore, it is necessary to design a new method to ensure that during the disaster recovery switching exercise, the production and disaster recovery databases can be switched normally, so as to avoid various error problems caused by misoperation and other factors during the manual switching process, reduce RTO (recovery time target, recovery Time Objective), reduce service interruption time, and ensure that RPO (recovery point target, recovery Point Object) meets the design requirements, and ensure that data is not lost.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provide a database disaster recovery switching exercise method, a device, computer equipment and a storage medium.
In order to achieve the above purpose, the present invention adopts the following technical scheme: the database disaster recovery switching exercise method comprises the following steps:
adding asset information of DB2 database production and disaster recovery sides;
identifying disaster tolerance pairs according to the characteristic information of the DB2 main and standby ends;
selecting a plan type, and arranging the drill plan by combining the disaster tolerance pair to obtain an arranging result;
carrying out plan evaluation on the arrangement result;
and when the plan evaluation passes, performing disaster recovery switching exercise on the arrangement result.
The further technical scheme is as follows: the asset information includes database information and host information; the database information comprises a port, a database name and an instance name; the host information includes host IP, access IP, host port, and host connection accounting information.
The further technical scheme is as follows: the identifying disaster recovery pairs according to the characteristic information of the DB2 main and standby ends comprises the following steps:
dividing the platform, version and database name of the DB2 database according to the same information to form a plurality of groups of databases;
querying the HADR information of each database in each group of databases;
and identifying disaster recovery pairs according to the HADR information.
The further technical scheme is as follows: the selecting the plan type and combining the disaster recovery pair to conduct drilling plan arrangement to obtain arrangement results, wherein the method comprises the following steps:
selecting a plan type according to disaster tolerance switching exercise requirements of a user in different scenes, wherein the plan type comprises a planning exercise plan, a disaster plan and a desktop exercise plan;
filling in a plan name, a plan description, an RPO index and an RTO index;
selecting disaster tolerance pairs added with demand switching, and selecting strategies in the drilling process according to the demands;
and according to the built-in initial starting node, the built-in initial ending node and the built-in intermediate node of the original arrangement step, adding disaster tolerance pairs switched according to the sequence of switching actual service requirements, and storing the arrangement topological graph to obtain an arrangement result.
The further technical scheme is as follows: the performing the plan evaluation on the arrangement result comprises the following steps:
And carrying out switching evaluation and environment evaluation on the arrangement result.
The further technical scheme is as follows: the switching evaluation is to evaluate whether the exercise switching can be performed or not according to the type of the plan and the actual running condition of the main and standby environments of the database, account authority and main and standby data synchronous delay conditions required by disaster recovery switching, if the conditions are not met, specific reasons for the non-compliance are given, and a solution is prompted; the environment evaluation is to compare the host environment and host resources of the production and disaster recovery databases and judge whether the performance problem of the operation of the disaster recovery database is possibly caused after the switching.
The further technical scheme is as follows: when the plan evaluation passes, performing disaster recovery switching exercise on the arrangement result, including:
selecting a disaster recovery switching operation step of a corresponding type according to the disaster recovery switching plan type corresponding to the arrangement result;
and carrying out disaster recovery switching operation according to the execution sequence of the arrangement result, wherein the disaster recovery switching operation steps are divided into pre-exercise inspection, exercise process and post-exercise inspection.
The invention also provides a database disaster recovery switching exercise device, which comprises:
the adding unit is used for adding asset information of the DB2 database production and disaster recovery side;
The identification unit is used for identifying disaster recovery pairs according to the characteristic information of the DB2 main and standby ends;
the arrangement unit is used for selecting the type of the plan and arranging the drill plan in combination with the disaster tolerance pair so as to obtain an arrangement result;
the evaluation unit is used for carrying out plan evaluation on the arrangement result;
and the drilling unit is used for performing disaster recovery switching drilling on the arrangement result when the plan evaluation passes.
The invention also provides a computer device which comprises a memory and a processor, wherein the memory stores a computer program, and the processor realizes the method when executing the computer program.
The present invention also provides a storage medium storing a computer program which, when executed by a processor, implements the above method.
Compared with the prior art, the invention has the beneficial effects that: according to the method, the disaster recovery pair is arranged and evaluated by selecting the type of the plan, when the plan is evaluated and passed, disaster recovery switching exercise is carried out on an arrangement result, the safety of disaster recovery exercise is fully considered, the data safety of a production system is ensured to the greatest extent, the influence on the data consistency due to the stopping, switching and other operations of a database in the disaster recovery exercise is avoided, various errors easily occurring in the conventional exercise process are solved, risks are avoided, and the disaster recovery exercise work is safer, more reliable and more efficient; the method and the device ensure that the production and disaster recovery databases can be switched normally during the disaster recovery switching exercise, avoid various error problems caused by misoperation and other factors in the manual switching process, reduce RTO, reduce service interruption time, ensure that RPO meets design requirements and ensure that data is not lost.
The invention is further described below with reference to the drawings and specific embodiments.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic flow chart of a database disaster recovery switching exercise method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a sub-flow of a database disaster recovery switching exercise method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a sub-flow of a database disaster recovery switching exercise method according to an embodiment of the present invention;
fig. 4 is a schematic sub-flowchart of a database disaster recovery switching exercise method according to an embodiment of the present invention;
FIG. 5 is a schematic block diagram of a database disaster recovery switching exercise device according to an embodiment of the present invention;
fig. 6 is a schematic block diagram of an identification unit of the database disaster recovery switching exercise device according to the embodiment of the present invention;
fig. 7 is a schematic block diagram of an arrangement unit of the database disaster recovery switching exercise device according to the embodiment of the present invention;
Fig. 8 is a schematic block diagram of an exercise unit of the database disaster recovery switching exercise device provided by the embodiment of the present invention;
fig. 9 is a schematic block diagram of a computer device according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be understood that the terms "comprises" and "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
Referring to fig. 1, fig. 1 is a schematic flowchart of a database disaster recovery switching exercise method according to an embodiment of the present invention. The database disaster recovery switching exercise method is applied to the server. The database is arranged in the server, the safety of disaster recovery exercise is fully considered, the data safety of a production system is ensured to the greatest extent, and the influence on the data consistency due to the stopping, switching and other operations of the database in the disaster recovery exercise is avoided, so that various errors easily occurring in the existing exercise process are solved, risks are avoided, and the disaster recovery exercise work is safer, more reliable and more efficient.
Fig. 1 is a schematic flow chart of a database disaster recovery switching exercise method according to an embodiment of the present invention. As shown in fig. 1, the method includes the following steps S110 to S150.
S110, adding asset information of the DB2 database production and disaster recovery side.
In this embodiment, the asset information includes database information and host information; the database information comprises a port, a database name and an instance name; the host information includes host IP, access IP, host port, and host connection accounting information.
S120, identifying disaster recovery pairs according to the characteristic information of the DB2 main and standby ends.
In this embodiment, the disaster recovery pair is a basic operation object for the disaster recovery switching exercise of the subsequent database.
In one embodiment, referring to fig. 2, the step S120 may include steps S121 to S123.
S121, dividing the platform, version and database name of the DB2 database according to the same information to form a plurality of groups of databases;
s122, inquiring HADR information of each database in each group of databases.
In this embodiment, the DB2 database disaster recovery pair automatic detection module automatically identifies and matches disaster recovery pair information of the DB2 database according to the feature information of the DB2 primary and secondary ends. The DB2 HADR master-slave association method comprises the following steps: inquiring a platform, a version and a database name of the DB2 database; databases with identical information are grouped together. And inquiring HADR information of each database of each group, wherein the HADR information comprises a hadr_role role, a relay_type copy type, a hadr_state state and a hadr_sync data synchronization type, primary_member_host represents a main library, and standby_member_host represents a standby library. And automatically detecting and forming a database disaster recovery pair according to the information and the conditions for judging and forming the DB2 HADR disaster recovery pair.
S123, identifying disaster recovery pairs according to HADR information.
Specifically, the DB2 HADR disaster recovery pair is formed under the conditions that a library hadr_role=primary and relay_type=PHYSICAL and primary_member_host points to itself; b-bank_role=standby and relay_type=physical and standby_membrane_host points to itself; the a-library standby_member_host points to the b-library and the b-library primary_member_host points to the a-library.
S130, selecting a plan type, and arranging the drill plan by combining the disaster recovery pair to obtain an arranging result.
In this embodiment, the arrangement result refers to arranging a group of disaster tolerance pairs or a plurality of groups of disaster tolerance pairs into an exercise plan in a sequential or parallel manner according to the needs of users for disaster tolerance switching exercises in different scenes, where the plans in different scenes are subdivided into three types of planning exercise plans, disaster plans and desktop exercise plans.
In one embodiment, referring to fig. 3, the step S130 may include steps S131 to S134.
S131, selecting a plan type according to disaster tolerance switching exercise requirements of a user in different scenes, wherein the plan type comprises a planning exercise plan, a disaster plan and a desktop exercise plan;
s132, filling in a plan name, a plan description, an RPO index and an RTO index;
S133, selecting a disaster tolerance pair with added demand switching, and selecting a strategy in the drilling process according to the demand.
In this embodiment, the policy includes a preferred policy for the security authorization verification step, where the database log is displayed back in real time.
S134, according to the built-in initial starting node, the built-in final node and the built-in intermediate node of the original arrangement step, adding disaster tolerance pairs switched according to the sequence of switching actual service requirements, and storing the arrangement topological graph to obtain an arrangement result.
And S140, carrying out plan evaluation on the arrangement result.
In this embodiment, the arrangement result is subjected to switching evaluation and environment evaluation.
Specifically, the switching evaluation is to evaluate whether the exercise switching can be performed or not according to the type of the plan and the actual running condition of the main and standby environments of the database, account authority and main and standby data synchronous delay conditions required by disaster recovery switching, if the conditions are not met, specific reasons for the non-compliance are given, and a solution is prompted; the environment evaluation is to compare the host environment and host resources of the production and disaster recovery databases and judge whether the performance problem of the operation of the disaster recovery database is possibly caused after the switching.
In the present embodiment, the evaluation items of the switching evaluation include:
Disaster recovery switching scheme: the connection state of the main and standby databases, the connection state of the main and standby hosts, the read-only parameters of the main database and the HADR state inspection. Evaluation content of connection state of the primary and secondary databases: the database account is required to be connected, and the evaluation content of the connection state of the master host and the slave host is as follows: the host is required to be connectable, and the evaluation content of the read-only parameters of the host library is as follows: the main library is required to enable read-only configuration, and the evaluation content of the HADR state inspection is as follows: the request state is PEER when the synchronization mode is SUPEPSYNC and the request state is REMOTE_CATCHUP and when the synchronization mode is one of SYNC, NEARSYNC, ASYNC. After all conditions are met, the switching evaluation of the plan can be passed.
Disaster-switching scheme: the connection state of the backup database (requiring the database account to be connectable), the connection state of the backup host (requiring the host to be connectable), and the backup HADR state check. After all conditions are met, the switching evaluation of the plan can be passed.
Desktop exercise protocol: a backup database connection STATE (requiring that a database account can be connected), a backup host connection STATE (requiring that a host be connected), a HADR STATE check (HADR_STATE STATE is HADR_STATE is PEER, DISCONNECTED PEER, REMOTE_CATCHUP_PENDING, REMOTE_CATCHUP, a database DB_DIR path is acquired, a log path, a tablespace container path), a database DB_DIR path, a log path, a tablespace container path, a file system check (checking file system information), associating a mount point path (DIR field) with the database path acquired above, and recording and storing the correspondence of a device path (fs field),. If the mount point path (DIR field) is in the root file system/, if the storage device path is not a logical volume LV (cannot be matched with the result in the LVM inspection), the pre-switch inspection fails), the snapshot volume size and the threshold check (according to the corresponding relationship of the mounting point path, the storage device path, the logical volume path and the volume group residual space obtained by the LVM inspection, and shown in the system, each snapshot volume size and the snapshot volume use threshold are set by the user by himself, the system provides an interactive interface, and judges and alarms are made for the content set by the user, if a plurality of logical volumes LV related to the database exist, the client is required to set up separately).
The evaluation items of the environment evaluation include: a host environment and host resources; host environment: the main and standby time and time zone deviation are within a certain range. Host resources: listing the CPU and memory resources of the master and slave. If the two are different, performance problems after switching may be caused.
And S150, performing disaster recovery switching exercise on the arrangement result when the plan evaluation passes.
In one embodiment, referring to fig. 4, the step S150 may include steps S151 to S152.
S151, selecting a disaster recovery switching operation step of a corresponding type according to a disaster recovery switching plan type corresponding to the arrangement result;
and S152, performing disaster recovery switching operation according to the execution sequence of the arrangement result, wherein the disaster recovery switching operation step is divided into pre-exercise inspection, an exercise process and post-exercise inspection.
Specifically, the content of the check before the disaster recovery switching plan exercise is the same as the step of the plan evaluation, and the check is carried out again before and after the formal exercise to prevent the non-compliance of the switching conditions caused by the state change of the database. The drilling process comprises the step of executing the switching of the master and slave libraries. After the replacement of the main and the standby is detected, the HADR state detection is required to accord with the exchange of the original disaster recovery to the main and the standby.
The content of the pre-exercise check of the disaster-switching plan is also the same as the step of the disaster-switching plan evaluation. The exercise process includes the step of executing a standby takeover. The check after exercise is to detect whether the service after the standby warehouse is taken over is normal.
The technical scheme of desktop drilling switching is realized based on a Linux LVM snapshot mode. The operation object of desktop drilling switching is a standby library; the contents checked before switching comprise database connection state, host connection state, switching state check, database DB_DIR path acquisition, database log path, and database table space container path. File system checking, LVM checking, snapshot volume size and threshold checking.
The step of the exercise process comprises: stopping the backup library instance, creating a snapshot by the backup library host, dynamically monitoring the snapshot LV utilization rate, starting the backup library instance, stopping the backup library HADR, converting the backup library into a standard mode, stopping the backup library instance, and performing umount on the related file system by the umount file system, wherein the original LV rolls back, and rolling back all the related LV logical volumes.
At the moment, the standby library can accept application connection, read and write the exercise data, and enter a business test stage. After verification is completed, the system deletes test verification data during exercise through an environment recovery step, and recovers to the original state.
The environment recovery step comprises a mount file system, a backup library instance is started, and a backup library HADR is started. Check if the HADR status is normal.
In this embodiment, the disaster recovery switching flow of the planning exercise plan is performed as the following sub-steps:
examination before planning exercise: step 3, the operation flow of the switching evaluation of the planning drilling switching plan is the same as that of the switching evaluation operation flow of the planning drilling switching plan in the step 3;
planning the exercise process: invoking db2 takeover HADR on database $dbname to command master-slave class switching;
examination after exercise: checking the HADR STATE, wherein the HADR_STATE STATE is one of HADR_STATE PEER, DISCONNECTED PEER, REMOTE_CATCHUP_PENDING and REMOTE_CATCHUP, and the roles of database production and disaster recovery are exchanged at the moment, so that the roles of database disaster recovery pairs are exchanged automatically;
and (3) service verification: the database user verifies that the switched database can meet the service use;
checking before back cutting exercise;
a back-cutting exercise process;
checking after back cutting exercise;
verifying production business;
the specific methods of the pre-back-cut exercise examination, the back-cut exercise process and the post-back-cut exercise examination are the same as those of the pre-plan exercise examination, the pre-plan exercise process and the post-exercise examination.
After the drilling is finished, the database of the production end is verified again to meet the service use.
The disaster recovery switching flow substeps of the disaster switching plan are as follows:
starting disaster switching announcement; checking before disaster switching exercise, and adding a condition for verifying that a database at a production end cannot be connected to the step of disaster switching plan switching evaluation; taking over the backup library: invoking the db2 takeover HADR on database $dbname by force command; and (5) service verification.
The technical scheme of desktop drilling switching is realized based on a Linux LVM snapshot mode, an operation object of desktop drilling switching is a standby library, and the switching flow substeps are as follows:
examination before table exercise: the checking contents comprise database connection state, host connection state, switching state checking, obtaining database DB_DIR path, database log path and database table space container path. File system checking, LVM checking, snapshot volume size and threshold checking. Consistent with the content of the plan switching evaluation;
the step of the exercise process comprises: stopping the backup library instance, creating a snapshot by the backup library host, dynamically monitoring the snapshot LV utilization rate, starting the backup library instance, stopping the backup library HADR, converting the backup library into a standard mode, stopping the backup library instance, and performing umount on the related file system by the umount file system, wherein the original LV rollback is performed by rolling back all the related LV logical volumes; at the moment, the standby library can accept application connection, read and write the exercise data, and enter a business test stage. After verification is completed, the system deletes test verification data during exercise through an environment recovery step, and recovers to the original state. The environment recovery step comprises a mount file system, a backup library instance is started, and a backup library HADR is started. Check if the HADR status is normal.
Specifically, the B2 HADR database desktop exercise process: before starting desktop exercise, checking the connection state of the disaster recovery database; checking the switching state to obtain three groups of paths; checking a file system; LVM inspection; checking the size and the threshold value of the snapshot volume; judging whether the exercise condition is met; when the exercise condition is met, the exercise is started to be executed, and the standby library instance is stopped; when the execution of the backup library example is successful, the backup library host creates a snapshot point; when the snapshot point is successfully established, the snapshot LV utilization rate is dynamically monitored, and a backup library instance is started; stopping preparing the HADR; converting the standby library into a standard mode; stopping the backup library instance; original LV rollback; an umount file system; stopping the backup library instance; waiting for service verification to be completed; starting environment recovery; a Mount file system; stopping preparing a warehouse; HADR status checking; judging whether rechecking is needed or not when the exercise condition is not met, checking and repairing the disaster recovery warehouse environment when rechecking is needed, and returning to the checking before desktop exercise; when no recheck is necessary, the ending step is entered.
According to the database disaster recovery switching exercise method, the disaster recovery pairs are arranged and evaluated by selecting the type of the plan, when the plan is evaluated to pass, disaster recovery switching exercise is carried out on the arrangement result, the safety of disaster recovery exercise is fully considered, the data safety of a production system is ensured to the greatest extent, the influence on the data consistency due to the operation such as stopping and switching of a database in the disaster recovery exercise is avoided, and therefore various errors easily occurring in the existing exercise process are solved, risks are avoided, and the disaster recovery exercise work is safer, more reliable and more efficient; the method and the device ensure that the production and disaster recovery databases can be switched normally during the disaster recovery switching exercise, avoid various error problems caused by misoperation and other factors in the manual switching process, reduce RTO, reduce service interruption time, ensure that RPO meets design requirements and ensure that data is not lost.
Fig. 5 is a schematic block diagram of a database disaster recovery switching exercise device 300 according to an embodiment of the present invention. As shown in fig. 5, the present invention further provides a database disaster recovery switching exercise device 300 corresponding to the above database disaster recovery switching exercise method. The database disaster recovery switching exercise device 300 includes a unit for performing the database disaster recovery switching exercise method described above, and may be configured in a server. Specifically, referring to fig. 5, the database disaster recovery switching exercise device 300 includes an adding unit 301, an identifying unit 302, an arranging unit 303, an evaluating unit 304, and an exercise unit 305.
An adding unit 301, configured to add asset information on the production and disaster recovery side of the DB2 database; the identifying unit 302 is configured to identify a disaster recovery pair according to the feature information of the DB2 primary and secondary side; an arrangement unit 303, configured to select a plan type, and arrange the exercise plan in combination with the disaster recovery pair to obtain an arrangement result; an evaluation unit 304, configured to perform a plan evaluation on the arrangement result; and the exercise unit 305 is configured to perform disaster recovery switching exercise on the arrangement result when the plan evaluation passes.
In one embodiment, as shown in fig. 6, the identifying unit 302 includes a dividing subunit 3021, a querying subunit 3022, and a disaster recovery pair identifying subunit 3023.
A dividing subunit 3021, configured to divide the platform, version, and database name of the DB2 database according to the same information, so as to form a plurality of groups of databases; a query subunit 3022 configured to query HADR information of each database in each set of databases; and a disaster recovery pair identification subunit 3023, configured to identify a disaster recovery pair according to the HADR information.
In one embodiment, as shown in fig. 7, the orchestration unit 303 includes a type selection subunit 3031, a filling subunit 3032, a policy selection subunit 3033, and an addition subunit 3034.
A type selection subunit 3031, configured to select a plan type according to disaster recovery switching exercise requirements of a user in different scenarios, where the plan type includes a planning exercise plan, a disaster plan, and a desktop exercise plan; a filling subunit 3032, configured to fill in a plan name, a plan description, an RPO index, and an RTO index; a policy selection subunit 3033, configured to select a disaster tolerance pair for adding a requirement switching, and select a policy in the drilling process according to a requirement; the adding subunit 3034 is configured to store the layout topological graph according to the built-in initial start node, the built-in end node and the built-in intermediate node in the original layout step, and according to the sequence of switching the actual service needs, add the disaster tolerance pair switched by the requirement, so as to obtain the layout result.
In an embodiment, the evaluation unit 304 is configured to perform a handover evaluation and an environment evaluation on the arrangement result.
In one embodiment, as shown in fig. 8, the exercise unit 305 includes a step selection subunit 3051 and an operation subunit 3052.
A step selecting subunit 3051, configured to select a disaster recovery switching operation step of a corresponding type according to a plan type of disaster recovery switching corresponding to the arrangement result; and an operation subunit 3052, configured to perform a disaster recovery switching operation according to the execution sequence of the arrangement result, where the disaster recovery switching operation step is divided into a pre-exercise inspection, an exercise process, and a post-exercise inspection.
It should be noted that, as those skilled in the art can clearly understand, the specific implementation process of the database disaster recovery switching exercise device 300 and each unit may refer to the corresponding description in the foregoing method embodiment, and for convenience and brevity of description, the description is omitted here.
The database disaster recovery switching exercise apparatus 300 described above may be implemented in the form of a computer program that can be run on a computer device as shown in fig. 9.
Referring to fig. 9, fig. 9 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device 500 may be a server, where the server may be a stand-alone server or may be a server cluster formed by a plurality of servers.
With reference to FIG. 9, the computer device 500 includes a processor 502, memory, and a network interface 505 connected by a system bus 501, where the memory may include a non-volatile storage medium 503 and an internal memory 504.
The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. The computer program 5032 includes program instructions that, when executed, cause the processor 502 to perform a database disaster recovery switching exercise method.
The processor 502 is used to provide computing and control capabilities to support the operation of the overall computer device 500.
The internal memory 504 provides an environment for the execution of a computer program 5032 in the non-volatile storage medium 503, which computer program 5032, when executed by the processor 502, causes the processor 502 to perform a database disaster recovery switching exercise method.
The network interface 505 is used for network communication with other devices. It will be appreciated by those skilled in the art that the structure shown in fig. 9 is merely a block diagram of a portion of the structure associated with the present application and does not constitute a limitation of the computer device 500 to which the present application is applied, and that a particular computer device 500 may include more or fewer components than shown, or may combine certain components, or have a different arrangement of components.
Wherein the processor 502 is configured to execute a computer program 5032 stored in a memory to implement the steps of:
adding asset information of DB2 database production and disaster recovery sides; identifying disaster tolerance pairs according to the characteristic information of the DB2 main and standby ends; selecting a plan type, and arranging the drill plan by combining the disaster tolerance pair to obtain an arranging result; carrying out plan evaluation on the arrangement result; and when the plan evaluation passes, performing disaster recovery switching exercise on the arrangement result.
Wherein the asset information includes database information and host information; the database information comprises a port, a database name and an instance name; the host information includes host IP, access IP, host port, and host connection accounting information.
In an embodiment, when the step of identifying the disaster recovery pair according to the feature information of the DB2 primary/secondary side is implemented by the processor 502, the following steps are specifically implemented:
dividing the platform, version and database name of the DB2 database according to the same information to form a plurality of groups of databases; querying the HADR information of each database in each group of databases; and identifying disaster recovery pairs according to the HADR information.
In one embodiment, when the processor 502 performs the planning of the exercise program in combination with the disaster recovery pair to obtain the planning result, the following steps are specifically implemented:
Selecting a plan type according to disaster tolerance switching exercise requirements of a user in different scenes, wherein the plan type comprises a planning exercise plan, a disaster plan and a desktop exercise plan; filling in a plan name, a plan description, an RPO index and an RTO index; selecting disaster tolerance pairs added with demand switching, and selecting strategies in the drilling process according to the demands; and according to the built-in initial starting node, the built-in initial ending node and the built-in intermediate node of the original arrangement step, adding disaster tolerance pairs switched according to the sequence of switching actual service requirements, and storing the arrangement topological graph to obtain an arrangement result.
In one embodiment, when the step of performing the plan evaluation on the layout result is implemented by the processor 502, the following steps are specifically implemented:
and carrying out switching evaluation and environment evaluation on the arrangement result.
The switching evaluation is to evaluate whether the exercise switching can be performed or not according to the type of the plan and the actual running condition of the main and standby environments of the database, account authority and main and standby data synchronous delay conditions required by disaster recovery switching, and if the conditions are not met, specific reasons for the non-compliance are given, and a solution is prompted; the environment evaluation is to compare the host environment and host resources of the production and disaster recovery databases and judge whether the performance problem of the operation of the disaster recovery database is possibly caused after the switching.
In one embodiment, when the processor 502 performs the disaster recovery switching exercise step on the arrangement result when the plan evaluation passes, the following steps are specifically implemented:
selecting a disaster recovery switching operation step of a corresponding type according to the disaster recovery switching plan type corresponding to the arrangement result; and carrying out disaster recovery switching operation according to the execution sequence of the arrangement result, wherein the disaster recovery switching operation steps are divided into pre-exercise inspection, exercise process and post-exercise inspection.
It should be appreciated that in embodiments of the present application, the processor 502 may be a central processing unit (Central Processing Unit, CPU), the processor 502 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSPs), application specific integrated circuits (Application Specific Integrated Circuit, ASICs), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. Wherein the general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
Those skilled in the art will appreciate that all or part of the flow in a method embodying the above described embodiments may be accomplished by computer programs instructing the relevant hardware. The computer program comprises program instructions, and the computer program can be stored in a storage medium, which is a computer readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the flow steps of the embodiments of the method described above.
Accordingly, the present invention also provides a storage medium. The storage medium may be a computer readable storage medium. The storage medium stores a computer program which, when executed by a processor, causes the processor to perform the steps of:
adding asset information of DB2 database production and disaster recovery sides; identifying disaster tolerance pairs according to the characteristic information of the DB2 main and standby ends; selecting a plan type, and arranging the drill plan by combining the disaster tolerance pair to obtain an arranging result; carrying out plan evaluation on the arrangement result; and when the plan evaluation passes, performing disaster recovery switching exercise on the arrangement result.
Wherein the asset information includes database information and host information; the database information comprises a port, a database name and an instance name; the host information includes host IP, access IP, host port, and host connection accounting information.
In an embodiment, when the processor executes the computer program to implement the step of identifying the disaster recovery pair according to the feature information of the DB2 primary-standby end, the method specifically includes the following steps:
dividing the platform, version and database name of the DB2 database according to the same information to form a plurality of groups of databases; querying the HADR information of each database in each group of databases; and identifying disaster recovery pairs according to the HADR information.
In one embodiment, when the processor executes the computer program to implement the selecting a plan type and combines the disaster recovery pair to perform drilling plan layout to obtain a layout result, the processor specifically implements the following steps:
selecting a plan type according to disaster tolerance switching exercise requirements of a user in different scenes, wherein the plan type comprises a planning exercise plan, a disaster plan and a desktop exercise plan; filling in a plan name, a plan description, an RPO index and an RTO index; selecting disaster tolerance pairs added with demand switching, and selecting strategies in the drilling process according to the demands; and according to the built-in initial starting node, the built-in initial ending node and the built-in intermediate node of the original arrangement step, adding disaster tolerance pairs switched according to the sequence of switching actual service requirements, and storing the arrangement topological graph to obtain an arrangement result.
In one embodiment, when the processor executes the computer program to implement the step of performing the plan evaluation on the layout result, the processor specifically implements the following steps:
and carrying out switching evaluation and environment evaluation on the arrangement result.
The switching evaluation is to evaluate whether the exercise switching can be performed or not according to the type of the plan and the actual running condition of the main and standby environments of the database, account authority and main and standby data synchronous delay conditions required by disaster recovery switching, and if the conditions are not met, specific reasons for the non-compliance are given, and a solution is prompted; the environment evaluation is to compare the host environment and host resources of the production and disaster recovery databases and judge whether the performance problem of the operation of the disaster recovery database is possibly caused after the switching.
In one embodiment, when the processor executes the computer program to implement the disaster recovery switching exercise step for the arrangement result when the plan evaluation passes, the processor specifically implements the following steps:
selecting a disaster recovery switching operation step of a corresponding type according to the disaster recovery switching plan type corresponding to the arrangement result; and carrying out disaster recovery switching operation according to the execution sequence of the arrangement result, wherein the disaster recovery switching operation steps are divided into pre-exercise inspection, exercise process and post-exercise inspection.
The storage medium may be a U-disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk, or other various computer-readable storage media that can store program codes.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the elements and steps of the examples have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the several embodiments provided by the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of each unit is only one logic function division, and there may be another division manner in actual implementation. For example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed.
The steps in the method of the embodiment of the invention can be sequentially adjusted, combined and deleted according to actual needs. The units in the device of the embodiment of the invention can be combined, divided and deleted according to actual needs. In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The integrated unit may be stored in a storage medium if implemented in the form of a software functional unit and sold or used as a stand-alone product. Based on such understanding, the technical solution of the present invention is essentially or a part contributing to the prior art, or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a terminal, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention.
While the invention has been described with reference to certain preferred embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made and equivalents will be apparent to those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.
Claims (9)
1. The database disaster recovery switching exercise method is characterized by comprising the following steps:
adding asset information of DB2 database production and disaster recovery sides;
identifying disaster tolerance pairs according to the characteristic information of the DB2 main and standby ends;
selecting a plan type, and arranging the drill plan by combining the disaster tolerance pair to obtain an arranging result;
carrying out plan evaluation on the arrangement result;
when the plan evaluation passes, disaster recovery switching exercise is performed on the arrangement result;
wherein, selecting the plan type, and arranging the drill plan in combination with the disaster recovery pair to obtain an arranging result comprises:
selecting a plan type according to disaster tolerance switching exercise requirements of a user in different scenes, wherein the plan type comprises a planning exercise plan, a disaster plan and a desktop exercise plan;
Filling in a plan name, a plan description, an RPO index and an RTO index;
selecting disaster tolerance pairs added with demand switching, and selecting strategies in the drilling process according to the demands;
and according to the built-in initial starting node, the built-in initial ending node and the built-in intermediate node of the original arrangement step, adding disaster tolerance pairs switched according to the sequence of switching actual service requirements, and storing the arrangement topological graph to obtain an arrangement result.
2. The database disaster recovery switching exercise method of claim 1, wherein the asset information includes database information and host information; the database information comprises a port, a database name and an instance name; the host information includes host IP, access IP, host port, and host connection accounting information.
3. The database disaster recovery switching exercise method according to claim 2, wherein the identifying the disaster recovery pair according to the feature information of the DB2 primary-standby terminal includes:
dividing the platform, version and database name of the DB2 database according to the same information to form a plurality of groups of databases;
querying the HADR information of each database in each group of databases;
and identifying disaster recovery pairs according to the HADR information.
4. The database disaster recovery switching exercise method of claim 1, wherein said performing a plan evaluation on said orchestration result comprises:
And carrying out switching evaluation and environment evaluation on the arrangement result.
5. The database disaster recovery switching exercise method according to claim 4, wherein the switching evaluation is to evaluate whether exercise switching can be performed or not according to the type of the plan and the actual running condition of the database active-standby environment, and if not, specific reasons for the non-compliance are given and a solution is prompted; the environment evaluation is to compare the host environment and host resources of the production and disaster recovery databases and judge whether the performance problem of the operation of the disaster recovery database is possibly caused after the switching.
6. The database disaster recovery switching exercise method of claim 1, wherein when the plan evaluation passes, performing disaster recovery switching exercise on the arrangement result comprises:
selecting a disaster recovery switching operation step of a corresponding type according to the disaster recovery switching plan type corresponding to the arrangement result;
and carrying out disaster recovery switching operation according to the execution sequence of the arrangement result, wherein the disaster recovery switching operation steps are divided into pre-exercise inspection, exercise process and post-exercise inspection.
7. Database disaster recovery switches exercise device, its characterized in that includes:
the adding unit is used for adding asset information of the DB2 database production and disaster recovery side;
the identification unit is used for identifying disaster recovery pairs according to the characteristic information of the DB2 main and standby ends;
the arrangement unit is used for selecting the type of the plan and arranging the drill plan in combination with the disaster tolerance pair so as to obtain an arrangement result;
the evaluation unit is used for carrying out plan evaluation on the arrangement result;
the drilling unit is used for performing disaster recovery switching drilling on the arrangement result when the plan evaluation passes;
wherein, selecting the plan type, and arranging the drill plan in combination with the disaster recovery pair to obtain an arranging result comprises:
selecting a plan type according to disaster tolerance switching exercise requirements of a user in different scenes, wherein the plan type comprises a planning exercise plan, a disaster plan and a desktop exercise plan;
filling in a plan name, a plan description, an RPO index and an RTO index;
selecting disaster tolerance pairs added with demand switching, and selecting strategies in the drilling process according to the demands;
and according to the built-in initial starting node, the built-in initial ending node and the built-in intermediate node of the original arrangement step, adding disaster tolerance pairs switched according to the sequence of switching actual service requirements, and storing the arrangement topological graph to obtain an arrangement result.
8. A computer device, characterized in that it comprises a memory on which a computer program is stored and a processor which, when executing the computer program, implements the method according to any of claims 1-6.
9. A storage medium storing a computer program which, when executed by a processor, implements the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310474940.3A CN116185723B (en) | 2023-04-28 | 2023-04-28 | Database disaster recovery switching exercise method, device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310474940.3A CN116185723B (en) | 2023-04-28 | 2023-04-28 | Database disaster recovery switching exercise method, device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116185723A CN116185723A (en) | 2023-05-30 |
| CN116185723B true CN116185723B (en) | 2023-08-08 |
Family
ID=86452718
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310474940.3A Active CN116185723B (en) | 2023-04-28 | 2023-04-28 | Database disaster recovery switching exercise method, device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116185723B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103530735A (en) * | 2013-10-23 | 2014-01-22 | 北京邮电大学 | Assessment method for daily operation and maintenance management capacity of disaster recovery center |
| CN106095614A (en) * | 2016-05-27 | 2016-11-09 | 上海新炬网络信息技术有限公司 | A kind of data base's DR test managing and control system |
| CN108446207A (en) * | 2017-02-16 | 2018-08-24 | 腾讯科技（深圳）有限公司 | Computer system redundancy ability appraisal procedure, apparatus and system |
| CN109460322A (en) * | 2018-11-14 | 2019-03-12 | 西安瑞蓝创软件科技有限公司 | The standby switching drilling system of calamity based on flow scheduling engine technique and method |
| CN111190769A (en) * | 2019-12-27 | 2020-05-22 | 柏科数据技术（深圳）股份有限公司 | Disaster recovery technology for automatic drilling |
| CN114780301A (en) * | 2022-06-22 | 2022-07-22 | 深圳市木浪云科技有限公司 | Disaster recovery method and system supporting multi-cloud production environment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11403132B2 (en) * | 2017-07-11 | 2022-08-02 | Red Hat, Inc. | Managing tasks in a cloud computing environment using multiple orchestration tools |
-
2023
- 2023-04-28 CN CN202310474940.3A patent/CN116185723B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103530735A (en) * | 2013-10-23 | 2014-01-22 | 北京邮电大学 | Assessment method for daily operation and maintenance management capacity of disaster recovery center |
| CN106095614A (en) * | 2016-05-27 | 2016-11-09 | 上海新炬网络信息技术有限公司 | A kind of data base's DR test managing and control system |
| CN108446207A (en) * | 2017-02-16 | 2018-08-24 | 腾讯科技（深圳）有限公司 | Computer system redundancy ability appraisal procedure, apparatus and system |
| CN109460322A (en) * | 2018-11-14 | 2019-03-12 | 西安瑞蓝创软件科技有限公司 | The standby switching drilling system of calamity based on flow scheduling engine technique and method |
| CN111190769A (en) * | 2019-12-27 | 2020-05-22 | 柏科数据技术（深圳）股份有限公司 | Disaster recovery technology for automatic drilling |
| CN114780301A (en) * | 2022-06-22 | 2022-07-22 | 深圳市木浪云科技有限公司 | Disaster recovery method and system supporting multi-cloud production environment |
Non-Patent Citations (1)
| Title |
|---|
| Souvik Basu.SAGE-PRoPHET: A Security Aided and Group Encounter based PRoPHET Routing Protocol for Dissemination of Post Disaster Situational Data.ICDCN '15: Proceedings of the 16th International Conference on Distributed Computing and Networking.2015,1-10. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116185723A (en) | 2023-05-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109901949B (en) | Application disaster recovery system and method for double-activity data center | |
| US8495019B2 (en) | System and method for providing assured recovery and replication | |
| US7971094B1 (en) | Method, system and apparatus for creating and executing a failover plan on a computer network | |
| WO2021103499A1 (en) | Multi-active data center-based traffic switching method and device | |
| CN107480014B (en) | High-availability equipment switching method and device | |
| JPH06103209A (en) | Information process system and method of information process system management | |
| CN107766502A (en) | A kind of Oracle RAC databases disaster tolerance switches drilling method | |
| CN110088744A (en) | A kind of database maintenance method and its system | |
| CN108199901B (en) | Hardware repair reporting method, system, device, hardware management server and storage medium | |
| CN112153134A (en) | Disaster tolerance drilling method, device, equipment and storage medium of disaster tolerance cloud host | |
| CN116185723B (en) | Database disaster recovery switching exercise method, device, computer equipment and storage medium | |
| CN110209556B (en) | Disaster tolerance testing method, payment method, device, medium and service equipment | |
| WO2018076696A1 (en) | Data synchronization method and out-of-band management device | |
| TWI774060B (en) | Device, method and computer program product for fault elimination of a multilayer system | |
| CN111404737B (en) | Disaster recovery processing method and related device | |
| CN111124724B (en) | Node fault testing method and device of distributed block storage system | |
| CN107291575B (en) | Processing method and equipment for data center fault | |
| CN115599600A (en) | Disaster recovery switching method and device, storage medium and electronic equipment | |
| CN113608959B (en) | Method, system, terminal and storage medium for positioning fault hard disk | |
| CN113238950A (en) | System and method for testing distributed system, storage medium and electronic equipment | |
| CN117118986B (en) | Block chain-based fault tolerance verification method, device, equipment and medium | |
| CN110413686B (en) | Data writing method, device, equipment and storage medium | |
| CN114490712A (en) | Service state determination system and method for PostgreSQL database | |
| CN117056122A (en) | Business-level disaster recovery exercise method, device, computer equipment and storage medium | |
| US8234465B1 (en) | Disaster recovery using mirrored network attached storage |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |