CN108154343B - Emergency processing method and system for enterprise-level information system - Google Patents
Emergency processing method and system for enterprise-level information system Download PDFInfo
- Publication number
- CN108154343B CN108154343B CN201711428180.3A CN201711428180A CN108154343B CN 108154343 B CN108154343 B CN 108154343B CN 201711428180 A CN201711428180 A CN 201711428180A CN 108154343 B CN108154343 B CN 108154343B
- Authority
- CN
- China
- Prior art keywords
- enterprise
- application
- information system
- environment
- level information
- 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
- 238000003672 processing method Methods 0.000 title claims abstract description 12
- 238000000034 method Methods 0.000 claims abstract description 91
- 230000008569 process Effects 0.000 claims abstract description 74
- 238000004519 manufacturing process Methods 0.000 claims abstract description 50
- 238000013515 script Methods 0.000 claims description 22
- 238000007726 management method Methods 0.000 claims description 21
- 238000013468 resource allocation Methods 0.000 claims description 7
- 238000004883 computer application Methods 0.000 abstract description 2
- 238000011084 recovery Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 2
- 238000012098 association analyses Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000013439 planning Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000009472 formulation Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- CXVGEDCSTKKODG-UHFFFAOYSA-N sulisobenzone Chemical compound C1=C(S(O)(=O)=O)C(OC)=CC(O)=C1C(=O)C1=CC=CC=C1 CXVGEDCSTKKODG-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/101—Collaborative creation, e.g. joint development of products or services
Landscapes
- Business, Economics & Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Marketing (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention discloses an emergency processing method and system for an enterprise-level information system, wherein the method comprises the following steps: acquiring roles of enterprise-level information system objects in a production environment and a guarantee environment and application emergency guarantee rules, wherein the application emergency guarantee rules are rules based on dependency relationship among enterprise-level information system application processes; and switching the enterprise information system from the production environment to the guarantee environment according to the starting priority of the application process when the enterprise information system fails according to the acquired role and the application emergency guarantee rule. The system comprises an acquisition module and a failover module. The invention considers the starting priority among the application processes determined by the dependency relationship among the application processes, so that the enterprise information system can automatically follow the starting priority of the application processes to ensure the service continuity when carrying out fault switching, and the method has high efficiency and is more convenient. The invention can be widely applied to the field of computer application.
Description
Technical Field
The invention relates to the field of computer application, in particular to an emergency processing method and system for an enterprise-level information system.
Background
The international latest standard ISO22301 of Business Continuity Management (BCM) was newly released by the international organization for standardization (ISO) on 5/15/2012. As its predecessor, the internationally recognized BCM standard BS 25999 issued by BSI has been formally replaced by ISO22301 in month 9 of 2012.
In 1979, SunGard established the first disaster recovery center in Philadelphia, USA, and people focused on IT, such as data backup and system backup, of enterprises; later, the IT backup is developed into Disaster Recovery Planning (DRP), and the contents of disaster recovery plans, resource requirements, disaster recovery center management and the like are added into the IT backup, so that a guarantee concept for a production operation center is formed; then, people gradually turn disaster recovery from an IT perspective to a business perspective, and use the business to measure disaster recovery targets (such as according to the importance of the business and the tolerable recovery time of the business), besides IT support, business impact analysis, strategy formulation, business recovery plans, personnel architecture, communication guarantee, third-party cooperation mechanisms and the like are added to the disaster recovery, and the disaster recovery system becomes a Business Continuity Planning (BCP); after the 911 event, disaster recovery takes into account, in addition to business-oriented, emergency response, crisis clearance, and supply chain crisis management.
In a large enterprise-level application system architecture, how to use a standby system for emergency disposal after a disaster (i.e., a failure) to ensure the continuity of a service becomes a major concern. The traditional large-scale enterprise-level application system architecture is based on a pure hardware system, mostly adopts a mode of manually switching to a fault environment to ensure the continuity of services, but the mode does not consider the starting priority among application processes, can only realize simple application starting, and can only gradually start corresponding applications in a manual mode when the fault environment needs to start more application processes, so that the efficiency is low and the convenience is not high.
Disclosure of Invention
To solve the above technical problems, the present invention aims to: the emergency processing method of the enterprise-level information system is high in efficiency and convenient.
Another object of the present invention is to: an efficient and convenient emergency processing system for enterprise-level information systems is provided.
The technical scheme adopted by the invention is as follows:
an emergency processing method for an enterprise-level information system comprises the following steps:
acquiring roles of enterprise-level information system objects in a production environment and a guarantee environment and application emergency guarantee rules, wherein the application emergency guarantee rules are rules based on dependency relationship among enterprise-level information system application processes;
and switching the enterprise information system from the production environment to the guarantee environment according to the starting priority of the application process when the enterprise information system fails according to the acquired role and the application emergency guarantee rule.
Further, the step of obtaining roles of the enterprise-level information system object in the production environment and the security environment and applying the emergency security rule specifically includes:
defining a production environment and roles and resource allocation in a guarantee environment according to business objects needing to be guaranteed by an enterprise-level information system;
making an application emergency guarantee rule according to the dependency relationship among the application processes of the enterprise information system;
and acquiring roles in a production environment and a guarantee environment and applying emergency guarantee rules.
Further, the step of formulating the application emergency guarantee rule according to the dependency relationship among the application processes of the enterprise-level information system specifically includes:
acquiring an enterprise-level information system architecture model;
analyzing the internal application dependency relationship of the enterprise-level information system architecture server;
analyzing the external application dependency relationship between enterprise-level information system architecture servers;
and formulating an application emergency guarantee rule according to the internal application dependency relationship of the server and the external application dependency relationship between the servers, and determining an emergency switching triggering condition and time length.
Further, the step of switching the enterprise-level information system from the production environment to the security environment according to the start priority of the application process when the enterprise-level information system fails according to the acquired role and the application emergency guarantee rule specifically includes:
judging whether the enterprise-level information system has a fault and meets the emergency switching triggering condition, if so, executing the operation of the next step, otherwise, keeping the enterprise-level information system in the production environment;
selecting one mode from an automatic switching mode and a manual switching mode as a fail-over mode;
and switching the enterprise information system from the production environment to the guarantee environment according to the starting priority of the application process according to the selected fault switching mode.
Further, the step of switching the enterprise-level information system from the production environment to the security environment according to the starting priority of the application process according to the selected failover mode specifically includes:
starting internal application of the security environment server according to the internal application dependency relationship of the enterprise-level information system architecture server;
and starting the external application between the environment-protecting servers according to the external application dependency relationship between the enterprise-level information system architecture servers.
Further, the step of starting the internal application of the security environment server according to the internal application dependency relationship of the enterprise-level information system architecture server specifically includes:
starting cluster application for guaranteeing the environment;
starting a management node service for guaranteeing the environment;
a managed service is initiated that secures the environment.
Further, the step of starting and ensuring the external application between the environment servers according to the external application dependency relationship between the enterprise-level information system architecture servers specifically includes:
starting an environment guaranteeing application system;
starting a data cache server of the environment application system;
starting a basic platform service, a queue and a retrieval service server for ensuring the environment application system;
and starting a main service, an accessory service and a report service server of the environment application system.
Further, the step of obtaining the enterprise-level information system architecture model specifically includes:
manually inputting a model script of an enterprise-level information system architecture model and distributing the input model script to corresponding nodes of a security environment;
or importing a model script of the enterprise-level information system architecture model and distributing the imported model script to corresponding nodes of the assurance environment.
The other technical scheme adopted by the invention is as follows:
an emergency processing system for an enterprise-level information system, comprising the following modules:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring roles of enterprise-level information system objects in a production environment and a guarantee environment and application emergency guarantee rules, and the application emergency guarantee rules are rules based on dependency relationships among application processes of the enterprise-level information system;
and the fault switching module is used for switching the enterprise information system from the production environment to the guarantee environment according to the starting priority of the application process when the enterprise information system has a fault according to the acquired role and the application emergency guarantee rule.
Further, the acquiring module specifically includes:
the system comprises a definition unit, a service management unit and a service management unit, wherein the definition unit is used for defining the production environment and the role and resource allocation in the guarantee environment according to the service objects needing to be guaranteed by the enterprise-level information system;
the application emergency guarantee rule making unit is used for making application emergency guarantee rules according to the dependence relationship among the application processes of the enterprise information system;
and the acquisition unit is used for acquiring roles in the production environment and the guarantee environment and applying the emergency guarantee rule.
The method has the beneficial effects that: the method comprises the steps of acquiring roles of enterprise-level information system objects in a production environment and a guarantee environment and applying emergency guarantee rules, and switching the enterprise-level information system from the production environment to the guarantee environment according to the starting priority of application processes when the enterprise-level information system fails according to the acquired roles and the application emergency guarantee rules, wherein the application emergency guarantee rules are rules based on the dependency relationship among the application processes of the enterprise-level information system, the starting priority among the application processes determined by the dependency relationship among the application processes is considered, so that when the enterprise-level information system fails, the starting priority of the application processes can be automatically followed to guarantee the service continuity, when the application processes are started in a more failure environment, the corresponding applications do not need to be started step by step in a manual mode, and the method is high in efficiency and more convenient.
The system of the invention has the beneficial effects that: the enterprise information system fault switching method comprises an acquisition module and a fault switching module, wherein an application emergency guarantee rule is a rule based on the dependency relationship among application processes of the enterprise information system, and the starting priority among the application processes determined by the dependency relationship among the application processes is considered, so that when the enterprise information system carries out fault switching, the business continuity can be guaranteed by automatically following the starting priority of the application processes, corresponding applications do not need to be started step by step in a manual mode when the application processes need to be started in a fault environment, and the method is high in efficiency and more convenient.
Drawings
FIG. 1 is an overall flow diagram of an emergency processing method of an enterprise-level information system of the present invention;
FIG. 2 is a block diagram of an emergency processing system for an enterprise-level information system in accordance with the present invention;
FIG. 3 is a flowchart of example 1 of the present invention;
FIG. 4 is a flowchart of example 2 of the present invention;
FIG. 5 is a flowchart of example 3 of the present invention;
FIG. 6 is a flowchart of embodiment 4 of the present invention;
FIG. 7 is a flowchart of embodiment 5 of the present invention.
Detailed Description
Referring to fig. 1, an emergency processing method of an enterprise-level information system includes the following steps:
acquiring roles of enterprise-level information system objects in a production environment and a guarantee environment and application emergency guarantee rules, wherein the application emergency guarantee rules are rules based on dependency relationship among enterprise-level information system application processes;
and switching the enterprise information system from the production environment to the guarantee environment according to the starting priority of the application process when the enterprise information system fails according to the acquired role and the application emergency guarantee rule.
In an enterprise-level information system architecture, complex dependency relationships exist among application processes, and the relationship determines the starting priority of a single server or a process across servers. The invention carries out fault switching according to the application emergency guarantee rule based on the dependency relationship among the application processes, so that the starting priority of the application processes can be followed during the fault switching, the application service can be successfully taken over, and the service continuity is guaranteed.
Further, as a preferred embodiment, the step of obtaining roles of the enterprise-level information system object in the production environment and the security environment and applying the emergency security rule specifically includes:
defining a production environment and roles and resource allocation in a guarantee environment according to business objects needing to be guaranteed by an enterprise-level information system;
making an application emergency guarantee rule according to the dependency relationship among the application processes of the enterprise information system;
and acquiring roles in a production environment and a guarantee environment and applying emergency guarantee rules.
Further, as a preferred embodiment, the step of formulating the application emergency guarantee rule according to the dependency relationship among the application processes of the enterprise-level information system specifically includes:
acquiring an enterprise-level information system architecture model;
analyzing the internal application dependency relationship of the enterprise-level information system architecture server;
analyzing the external application dependency relationship between enterprise-level information system architecture servers;
and formulating an application emergency guarantee rule according to the internal application dependency relationship of the server and the external application dependency relationship between the servers, and determining an emergency switching triggering condition and time length.
The emergency switching triggering condition refers to a set switching parameter (such as the number of running processes, the name of the processes, a running log keyword, and the like) that needs to be met by the application process for emergency switching. The client agent software can be used for acquiring running log keywords, process names, process numbers and the like (namely set switching parameters required to be met by emergency switching) generated by the enterprise-level information system and feeding back information to a management platform of the system. The duration refers to the interval time between fault detection of the enterprise information system.
Further, as a preferred embodiment, the step of switching the enterprise-level information system from the production environment to the security environment according to the start priority of the application process when the enterprise-level information system fails according to the acquired role and the application emergency guarantee rule specifically includes:
judging whether the enterprise-level information system has a fault and meets the emergency switching triggering condition, if so, executing the operation of the next step, otherwise, keeping the enterprise-level information system in the production environment;
selecting one mode from an automatic switching mode and a manual switching mode as a fail-over mode;
and switching the enterprise information system from the production environment to the guarantee environment according to the starting priority of the application process according to the selected fault switching mode.
The enterprise-level information system failure means that hardware or software of the enterprise-level information system fails (i.e., common software and hardware failures). And the emergency switching triggering condition is specific to the application process of the enterprise-level information system server, and the condition that the emergency switching triggering condition is met indicates that the application process of the enterprise-level information system is abnormal.
Further, as a preferred embodiment, the step of switching the enterprise-level information system from the production environment to the security environment according to the start priority of the application process according to the selected failover mode specifically includes:
starting internal application of the security environment server according to the internal application dependency relationship of the enterprise-level information system architecture server;
and starting the external application between the environment-protecting servers according to the external application dependency relationship between the enterprise-level information system architecture servers.
Further, as a preferred embodiment, the step of starting the internal application of the provisioning environment server according to the internal application dependency relationship of the enterprise-level information system architecture server specifically includes:
starting cluster application for guaranteeing the environment;
starting a management node service for guaranteeing the environment;
a managed service is initiated that secures the environment.
Further, as a preferred embodiment, the step of starting and ensuring the external application between the environment servers according to the external application dependency relationship between the enterprise-level information system architecture servers specifically includes:
starting an environment guaranteeing application system;
starting a data cache server of the environment application system;
starting a basic platform service, a queue and a retrieval service server for ensuring the environment application system;
and starting a main service, an accessory service and a report service server of the environment application system.
Further, as a preferred embodiment, the step of obtaining the enterprise-level information system architecture model specifically includes:
manually inputting a model script of an enterprise-level information system architecture model and distributing the input model script to corresponding nodes of a security environment;
or importing a model script of the enterprise-level information system architecture model and distributing the imported model script to corresponding nodes of the assurance environment.
The model script comprises server information and key application process information in an enterprise-level information system architecture.
Referring to fig. 2, an emergency processing system of an enterprise-level information system includes the following modules:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring roles of enterprise-level information system objects in a production environment and a guarantee environment and application emergency guarantee rules, and the application emergency guarantee rules are rules based on dependency relationships among application processes of the enterprise-level information system;
and the fault switching module is used for switching the enterprise information system from the production environment to the guarantee environment according to the starting priority of the application process when the enterprise information system has a fault according to the acquired role and the application emergency guarantee rule.
Further as a preferred embodiment, the obtaining module specifically includes:
the system comprises a definition unit, a service management unit and a service management unit, wherein the definition unit is used for defining the production environment and the role and resource allocation in the guarantee environment according to the service objects needing to be guaranteed by the enterprise-level information system;
the application emergency guarantee rule making unit is used for making application emergency guarantee rules according to the dependence relationship among the application processes of the enterprise information system;
and the acquisition unit is used for acquiring roles in the production environment and the guarantee environment and applying the emergency guarantee rule.
The invention will be further explained and explained with reference to the drawings and the embodiments in the description.
Example 1
Referring to fig. 3, a first embodiment of the present invention:
the invention aims to provide an emergency processing method of an enterprise-level information system when a standby system for guaranteeing the environment is used for emergency disposal after a large enterprise-level information system has a disaster, so as to provide a switching judgment basis and corresponding operation management for the automatic and quick starting of the application of the enterprise-level information system.
The method comprises a dependency relationship judging function and a process starting priority judging function based on the enterprise information system architecture application processes.
Taking an enterprise-level information system as an example of a business system, as shown in fig. 3, the emergency processing method specifically includes the following steps:
(1) defining roles of a production machine and a guarantee machine: defining the production environment (namely a production machine) and the role and resource allocation in the guarantee environment (namely a guarantee machine) according to the business system object needing to be guaranteed, and executing the step (2) after the definition is successful;
(2) formulating a business application emergency guarantee rule: establishing a guarantee rule according to the dependence relationship among the application processes of the service system, and defining an emergency switching triggering condition and time length;
(3) and switching the service to the guarantee environment: and when the business system in the production environment breaks down and meets the switching triggering condition, switching the business system from the production environment to the guarantee environment according to the starting priority of the application process.
Example 2
Referring to fig. 4, a second embodiment of the present invention:
compared with the embodiment 1, the embodiment adds the step of judging whether to switch automatically or not, so that a user can flexibly select one of a manual switching mode and an automatic switching mode as a fault switching mode according to needs, and the method is more flexible and convenient. In the embodiment, the mode of judging the fault switching is divided into a manual switching mode and an automatic switching mode, wherein the manual switching mode is implemented by a system administrator through a corresponding management operation interface; and the automatic switching mode is a default mode, and the system automatically executes the fault switching.
Example 3
Referring to fig. 5, a third embodiment of the present invention:
taking an enterprise-level information system as an example of a business system, when a business application guarantee rule is formulated, a business system architecture model is imported, and internal association analysis and external association analysis are performed on the business system architecture model according to the business system architecture, and the specific process includes:
1) importing a business system architecture model: and importing a business system architecture mode through a platform management interface of the guarantee environment, and editing and arranging the business system architecture mode according to the requirement.
There are two ways to import the business system architecture model: a. a system administrator manually inputs a model script with a corresponding format through a system management interface (for example, for a WINDOWS system, the format of the model script is in a bat; for a LINUX system, the format of the model script is in a sch) and distributes the input model script to corresponding nodes of a guarantee environment; b. model scripts in a corresponding format are imported in batches through a system management interface (for example, the format of the model scripts is bat for WINDOWS systems, and the format of the model scripts is sch for LINUX systems), and the imported model scripts are distributed to corresponding nodes of the guarantee environment. The model script includes server information and key application process information within the business system architecture.
2) And analyzing the internal application dependency relationship of the business system architecture server. Multiple types of business system application subprocesses are usually operated in a single server, and the operation sequence of the subprocesses is determined by the characteristics of a business system.
3) And analyzing the external application dependency relationship among a plurality of servers of the business system architecture. Each application server in the service system bears different roles, and the roles are generally classified according to the functions of foreground display, background operation, data caching and the like, so that various roles can be intelligently sequenced and arranged according to a service system architecture model.
Compared with the traditional business system emergency guarantee scheme, the method for establishing the emergency guarantee environment based on the business system architecture model analysis is adopted, the emergency guarantee environment can be established more accurately and clearly, and the guarantee of 'failure non-perception' is provided for the production environment.
Example 4
Referring to fig. 6, a fourth embodiment of the present invention:
in this embodiment, a process of starting an internal application of a security environment server according to an internal application dependency relationship of a system architecture server when a system failure is detected and an emergency handover trigger condition is satisfied is described.
As shown in fig. 6, the internal application process of starting the safeguard environment server mainly includes the following steps:
(a) starting cluster application (such as weblogic cluster application) for guaranteeing the environment;
(b) starting a management node service for guaranteeing the environment;
(c) a managed service is initiated that secures the environment.
According to the internal application dependency relationship, the management node service and the managed service which guarantee the environment are started in sequence, and the managed service can be started only if the management node service is started successfully.
Example 5
Referring to fig. 7, a fifth embodiment of the present invention:
this embodiment describes a process of starting external applications between the environment-protecting servers according to the external application dependency relationship between the system architecture servers when the system is detected to have a fault and the emergency handover trigger condition is satisfied.
As shown in fig. 6, the process of starting the external application between the security environment servers mainly includes the following steps:
(a) starting an environment guaranteeing application system;
(b) starting a data caching (coherence) server of the security environment application system;
(c) starting a basic platform service (PsAdminserver) for ensuring an environment application system, a queue mq and a retrieval service sr server;
(d) and starting a main service, an accessory service and a report service server of the environment application system.
According to the external application dependency relationship among the system architecture servers, the three cluster application servers, namely a data cache (coherence) server, a system basic platform service (PsAdminserver), a queue mq, a retrieval service sr server, a main service, an accessory service and a report service server, have a starting sequence, and the starting of the next cluster application server can be carried out only if the previous cluster application server is successfully started, wherein the specific sequence is as follows: data cache (coherence) server start- [ O-H-S-A-S-A-S-A-service, queue mQ-A-service, a-A-service, a-A-server start-A-server (coherence-A-A.
Compared with the traditional emergency guarantee mode purely based on a hardware system, the invention provides the emergency processing method and the system of the enterprise information system based on the decision function of the dependency relationship among the application processes on the starting priority of a single server or the process of a cross-server, and the judgment of the starting priority of the application processes (namely, the prerequisite classification and judgment) is carried out based on the dependency relationship among the application processes of the enterprise information system architecture, so that the situation is guaranteed to follow the starting priority of the application processes during fault switching, the application service is successfully taken over, and the service continuity is guaranteed.
While the preferred embodiments of the present invention have been illustrated and described, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.
Claims (7)
1. An emergency processing method for an enterprise-level information system is characterized in that: the method comprises the following steps:
acquiring roles of enterprise-level information system objects in a production environment and a guarantee environment and application emergency guarantee rules, wherein the application emergency guarantee rules are rules based on dependency relationship among enterprise-level information system application processes;
switching the enterprise information system from a production environment to a guarantee environment according to the starting priority of the application process when the enterprise information system fails according to the acquired role and the application emergency guarantee rule;
the step of obtaining roles of the enterprise-level information system objects in the production environment and the security environment and applying the emergency security rules specifically includes:
defining a production environment and roles and resource allocation in a guarantee environment according to business objects needing to be guaranteed by an enterprise-level information system;
the method for formulating the application emergency guarantee rule according to the dependency relationship among the application processes of the enterprise information system specifically comprises the following steps: acquiring an enterprise-level information system architecture model; analyzing the internal application dependency relationship of the enterprise-level information system architecture server; analyzing the external application dependency relationship between enterprise-level information system architecture servers; an application emergency guarantee rule is formulated according to the internal application dependency relationship of the server and the external application dependency relationship between the servers, and the emergency switching triggering condition and the emergency switching triggering duration are determined;
and acquiring roles in a production environment and a guarantee environment and applying emergency guarantee rules.
2. The method of claim 1, wherein the emergency processing comprises: the step of switching the enterprise-level information system from the production environment to the security environment according to the starting priority of the application process when the enterprise-level information system fails according to the acquired role and the application emergency guarantee rule specifically includes:
judging whether the enterprise-level information system has a fault and meets the emergency switching triggering condition, if so, executing the operation of the next step, otherwise, keeping the enterprise-level information system in the production environment;
selecting one mode from an automatic switching mode and a manual switching mode as a fail-over mode;
and switching the enterprise information system from the production environment to the guarantee environment according to the starting priority of the application process according to the selected fault switching mode.
3. The method of claim 2, wherein the emergency processing comprises: the step of switching the enterprise-level information system from the production environment to the guarantee environment according to the starting priority of the application process according to the selected fault switching mode specifically comprises the following steps:
starting internal application of the security environment server according to the internal application dependency relationship of the enterprise-level information system architecture server;
and starting the external application between the environment-protecting servers according to the external application dependency relationship between the enterprise-level information system architecture servers.
4. The method of claim 3, wherein the emergency processing comprises: the step of starting the internal application of the environment-guaranteeing server according to the internal application dependency relationship of the enterprise-level information system architecture server specifically includes:
starting cluster application for guaranteeing the environment;
starting a management node service for guaranteeing the environment;
a managed service is initiated that secures the environment.
5. The method of claim 3, wherein the emergency processing comprises: the step of starting and ensuring the external application between the environment servers according to the external application dependency relationship between the enterprise-level information system architecture servers specifically comprises:
starting an environment guaranteeing application system;
starting a data cache server of the environment application system;
starting a basic platform service, a queue and a retrieval service server for ensuring the environment application system;
and starting a main service, an accessory service and a report service server of the environment application system.
6. An emergency handling method for an enterprise-level information system according to any one of claims 3-5, wherein: the step of obtaining the enterprise-level information system architecture model specifically includes:
manually inputting a model script of an enterprise-level information system architecture model and distributing the input model script to corresponding nodes of a security environment;
or importing a model script of the enterprise-level information system architecture model and distributing the imported model script to corresponding nodes of the assurance environment.
7. An emergency processing system for an enterprise-level information system, comprising: the system comprises the following modules:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring roles of enterprise-level information system objects in a production environment and a guarantee environment and application emergency guarantee rules, and the application emergency guarantee rules are rules based on dependency relationships among application processes of the enterprise-level information system;
the fault switching module is used for switching the enterprise-level information system from a production environment to a guarantee environment according to the starting priority of the application process when the enterprise-level information system has a fault according to the acquired role and the application emergency guarantee rule;
the acquisition module specifically includes:
the system comprises a definition unit, a service management unit and a service management unit, wherein the definition unit is used for defining the production environment and the role and resource allocation in the guarantee environment according to the service objects needing to be guaranteed by the enterprise-level information system;
the application emergency guarantee rule making unit is used for making application emergency guarantee rules according to the dependence relationship among the application processes of the enterprise information system, and the application emergency guarantee rule making unit specifically comprises the following steps: acquiring an enterprise-level information system architecture model; analyzing the internal application dependency relationship of the enterprise-level information system architecture server; analyzing the external application dependency relationship between enterprise-level information system architecture servers; an application emergency guarantee rule is formulated according to the internal application dependency relationship of the server and the external application dependency relationship between the servers, and the emergency switching triggering condition and the emergency switching triggering duration are determined;
and the acquisition unit is used for acquiring roles in the production environment and the guarantee environment and applying the emergency guarantee rule.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711428180.3A CN108154343B (en) | 2017-12-26 | 2017-12-26 | Emergency processing method and system for enterprise-level information system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711428180.3A CN108154343B (en) | 2017-12-26 | 2017-12-26 | Emergency processing method and system for enterprise-level information system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108154343A CN108154343A (en) | 2018-06-12 |
| CN108154343B true CN108154343B (en) | 2022-01-14 |
Family
ID=62462909
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711428180.3A Active CN108154343B (en) | 2017-12-26 | 2017-12-26 | Emergency processing method and system for enterprise-level information system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108154343B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112882921B (en) * | 2019-11-29 | 2024-04-05 | 北京百度网讯科技有限公司 | Fault simulation method and device |
| CN112766712A (en) * | 2021-01-15 | 2021-05-07 | 国家海洋信息中心 | Ocean emergency scheduling method and system and electronic equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7039402B1 (en) * | 2003-08-05 | 2006-05-02 | Nortel Networks Limited | Disaster recovery for very large GSM/UMTS HLR databases |
| CN101414277A (en) * | 2008-11-06 | 2009-04-22 | 清华大学 | Need-based increment recovery disaster-containing system and method based on virtual machine |
| CN101437175A (en) * | 2007-11-15 | 2009-05-20 | 华为技术有限公司 | Method, apparatus and system for processing disaster-tolerating switch |
| CN103324715A (en) * | 2013-06-20 | 2013-09-25 | 交通银行股份有限公司 | Disaster recovery backup system availability detection method and device |
| CN103617269A (en) * | 2013-12-05 | 2014-03-05 | 中国联合网络通信集团有限公司 | Disaster tolerance pipe connecting method and disaster tolerance pipe connecting system |
| CN106600010A (en) * | 2016-12-02 | 2017-04-26 | 国家电网公司 | Intelligent emergency processing information system based on scene adaptation |
| CN106713409A (en) * | 2016-10-21 | 2017-05-24 | 中国电信集团系统集成有限责任公司 | SaaS-based cloud disaster recovery system and method |
-
2017
- 2017-12-26 CN CN201711428180.3A patent/CN108154343B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7039402B1 (en) * | 2003-08-05 | 2006-05-02 | Nortel Networks Limited | Disaster recovery for very large GSM/UMTS HLR databases |
| CN101437175A (en) * | 2007-11-15 | 2009-05-20 | 华为技术有限公司 | Method, apparatus and system for processing disaster-tolerating switch |
| CN101414277A (en) * | 2008-11-06 | 2009-04-22 | 清华大学 | Need-based increment recovery disaster-containing system and method based on virtual machine |
| CN103324715A (en) * | 2013-06-20 | 2013-09-25 | 交通银行股份有限公司 | Disaster recovery backup system availability detection method and device |
| CN103617269A (en) * | 2013-12-05 | 2014-03-05 | 中国联合网络通信集团有限公司 | Disaster tolerance pipe connecting method and disaster tolerance pipe connecting system |
| CN106713409A (en) * | 2016-10-21 | 2017-05-24 | 中国电信集团系统集成有限责任公司 | SaaS-based cloud disaster recovery system and method |
| CN106600010A (en) * | 2016-12-02 | 2017-04-26 | 国家电网公司 | Intelligent emergency processing information system based on scene adaptation |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108154343A (en) | 2018-06-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109656742B (en) | Node exception handling method and device and storage medium | |
| CN106406993A (en) | Timed task management method and system | |
| CN105760240A (en) | Distributed task processing method and device | |
| CN102857371B (en) | A kind of dynamic allocation management method towards group system | |
| US11327794B2 (en) | Periodic task execution in an automated context | |
| US11061669B2 (en) | Software development tool integration and monitoring | |
| CN107729213B (en) | Background task monitoring method and device | |
| CN108845954A (en) | Method for testing pressure, system and storage medium | |
| CN113220431A (en) | Cross-cloud distributed data task scheduling method, device and storage medium | |
| CN105096014A (en) | Method and system for recording work operation condition remotely | |
| EP3457668B1 (en) | Clustering in unified communication and collaboration services | |
| CN108154343B (en) | Emergency processing method and system for enterprise-level information system | |
| CN105988886A (en) | Fault processing method and device in operation and maintenance process | |
| US20190146839A1 (en) | Distributed data platform resource allocator | |
| CN113220480B (en) | Distributed data task cross-cloud scheduling system and method | |
| CN110209497A (en) | Method and system for dynamically expanding and shrinking host resources | |
| CN102868594B (en) | Method and device for message processing | |
| CN115509714A (en) | Task processing method and device, electronic equipment and storage medium | |
| CN115941441A (en) | System link automation monitoring operation and maintenance method, system, equipment and medium | |
| CN113419921A (en) | Task monitoring method, device, equipment and storage medium | |
| CN113037871A (en) | Conference call recovery method, device, system, electronic equipment and readable storage medium | |
| CN110764882B (en) | Distributed management method, distributed management system and device | |
| CN113301177A (en) | Domain name anti-blocking method and device | |
| US10606714B2 (en) | Stopping central processing units for data collection based on event categories of events | |
| CN106487561A (en) | The method and system that a kind of server service updates |
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 |