PaaS middleware disaster recovery method, disaster recovery device, disaster recovery equipment and storage medium

Abstract

The embodiment of the present invention provides a PaaS middleware disaster recovery method, disaster recovery device, disaster recovery equipment and storage medium. By determining the primary site, detecting that the middleware type of the backup site meets the preset conditions, and connecting the primary and backup sites; configuring disaster recovery parameters for the entity objects of the middleware types of the respective primary and backup sites, generating a data synchronization strategy according to the disaster recovery parameters, and synchronizing the data of the entity objects of each middleware type of the primary site to the entity objects of each middleware type of the corresponding backup site according to the synchronization strategy. The present invention also provides a PaaS middleware disaster recovery device, disaster recovery equipment and storage medium. In some implementation processes, the method has the technical effect that the business disaster recovery is no longer tightly coupled with the business, and an additional specific commercial software and hardware technology platform is required in the business disaster recovery, thereby saving the disaster recovery cost.

Description

Technical Field

[0001] The embodiments of the present invention relate to, but are not limited to, the fields of communication and information, and specifically, relate to, but are not limited to, a PaaS middleware disaster recovery method, a disaster recovery device, a disaster recovery equipment, and a storage medium. Background Art

[0002] In the 5G era, the communication network itself is developing in the direction of SDN / NFV, and the management capabilities of the communication network management system are also expanding. The amount of various business and management information data generated by the network is exploding, and the corresponding system high availability and data disaster recovery are particularly important. Distributed, virtualized, and cloud-based are standard architecture technologies for system capability expansion. Various applications are deployed in the form of microservices and containers on the virtualized and cloud-based Platform as a Service (PaaS), making full use of the capabilities of various middleware public service objects provided by the platform. This has become the basic management architecture specification for telecommunications 5G, and disaster recovery technology also needs to keep pace with the times to meet the disaster recovery requirements of this infrastructure.

[0003] In the related technologies, there are disaster recovery solutions for backup and recovery of business APP based on PaaS and disaster recovery solutions for the underlying storage layer based on PaaS. In the disaster recovery solution for backup and recovery of business APP based on PaaS, the business APP needs to participate in the disaster recovery process throughout the process. While ensuring the transparent advantage of white box that the impact of the disaster recovery process on the business is visible and can be intervened, it also causes the tight coupling of disaster recovery and business. The disaster recovery operation invades the business APP, affecting the stability and performance indicators of the business APP operation. The consistency of the data in the disaster recovery process requires many business APPs to ensure it at the same time, which brings extremely high business complexity. The disaster recovery solution based on the underlying storage layer of PaaS needs to be bound to the replication technology of the dedicated commercial disaster recovery software or the magnetic array hardware brand, which is relatively costly. Summary of the invention

[0004] The PaaS middleware disaster recovery method, disaster recovery device, disaster recovery equipment and storage medium provided by the embodiments of the present invention mainly solve the technical problem that disaster recovery processing for business must be tightly coupled with the business, disaster recovery operations invade the business APP, affecting the stability and performance indicators of business operation, or need to be bound to dedicated commercial disaster recovery software or magnetic array hardware brand replication technology.

[0005] In order to solve the above technical problems, an embodiment of the present invention provides a disaster recovery method for a middleware of a platform as a service (PaaS), comprising:

[0006] Determine that the first site is the first active site, detect that the middleware type of the first site and the number of entity objects of the middleware type of the first site are consistent with the middleware type of the second site and the number of entity objects of the middleware type of the second site, and when the middleware type versions of the first site and the second site are compatible or consistent, connect the first site and the second site; the second site is a standby site;

[0007] Performing disaster recovery parameter configuration on at least one middleware type entity object of the first site and the second site, wherein the disaster recovery parameters include: quality of service QoS priority, and communication address;

[0008] Generate a first synchronization strategy according to the disaster recovery parameters;

[0009] The data of the entity object of the middleware type of the first site is synchronized to the entity object of the middleware type corresponding to the second site according to the first synchronization strategy.

[0010] The embodiment of the present invention also provides a disaster recovery device for a middleware of a platform as a service (PaaS), the disaster recovery device comprising: an access module, a configuration module, a control module and a synchronization coordination module;

[0011] The access module is used to determine that the first site is the first active site, and when it is detected that the middleware type of the first site and the number of entity objects of the middleware type of the first site are consistent with the middleware type of the second site and the number of entity objects of the middleware type of the second site, and the middleware type versions of the first site and the second site are compatible or consistent, connect the first site and the second site; the second site is a standby site;

[0012] The configuration module is used to configure disaster recovery parameters for at least one middleware-type entity object of the first site and the second site, wherein the disaster recovery parameters include: quality of service QoS priority, communication address, and send the disaster recovery parameters to the control module and the synchronization execution module;

[0013] The control module is configured to receive the disaster recovery parameters, generate a first synchronization strategy according to the disaster recovery parameters, and send the first synchronization strategy to the synchronization execution module;

[0014] The synchronization execution module is used to receive the disaster recovery parameters and the first synchronization strategy, and synchronize the data of the middleware-type entity object of the first site to the middleware-type entity object corresponding to the second site according to the first synchronization strategy.

[0015] An embodiment of the present invention further provides a disaster recovery device, the device comprising a processor, a memory and a communication bus;

[0016] The communication bus is used to realize the connection and communication between the processor and the memory;

[0017] The processor is used to execute one or more computer programs stored in the memory to implement the steps of the disaster recovery method for the middleware of the Platform as a Service PaaS.

[0018] An embodiment of the present invention also provides a computer-readable storage medium, which stores one or more programs. The one or more programs can be executed by one or more processors to implement the steps of the disaster recovery method of the middleware of the Platform as a Service PaaS as described above.

[0019] According to the PaaS middleware disaster recovery method, disaster recovery device, disaster recovery equipment and storage medium provided by the embodiment of the present invention, by determining that the first site is the first main site, detecting that the middleware type of the main site and the number of entity objects of the middleware type of the main site are consistent with the middleware type of the second site as the backup site and the number of entity objects of the middleware type of the second site, and when the middleware type versions of the main and backup sites are compatible or consistent, the main and backup sites are connected. Disaster recovery parameters are configured for at least one entity object of the middleware type of the main and backup sites, wherein the disaster recovery parameters include: quality of service QoS priority, communication address, and then a first synchronization strategy is generated according to the disaster recovery parameters; according to the first synchronization strategy, the data of the entity object of the middleware type of the main site is synchronized to the entity object of the middleware type corresponding to the backup site. In some implementation processes, technical effects including but not limited to not tightly coupling the business APP when processing business disaster recovery, the disaster recovery process and the business will not affect each other, and are not bound to or dependent on a specific commercial software and hardware technology platform can be achieved.

[0020] Other features and corresponding beneficial effects of the present invention are described in the latter part of the specification, and it should be understood that at least part of the beneficial effects become obvious from the description in the specification of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 A basic flow chart of a disaster recovery method for a platform as a service (PaaS) middleware according to a first embodiment of the present invention;

[0022] Figure 2 This is an interface display diagram of the control display station of the first embodiment of the present invention;

[0023] Figure 3 A detailed flow chart of a disaster recovery method for a middleware of a platform as a service (PaaS) according to a second embodiment of the present invention;

[0024] Figure 4This is a detailed flow chart of a disaster recovery method for a middleware of a Platform as a Service (PaaS) according to Embodiment 3 of the present invention;

[0025] Figure 5 A schematic diagram of the composition of a disaster recovery device of a platform as a service (PaaS) middleware according to a fourth embodiment of the present invention;

[0026] Figure 6 The figure is a schematic diagram of the structure of the disaster recovery device according to the fifth embodiment of the present invention. DETAILED DESCRIPTION

[0027] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the following is a further detailed description of the embodiments of the present invention through specific implementation methods combined with the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0028] Embodiment 1:

[0029] In order to solve the technical problems of business disaster recovery being tightly coupled with business or requiring additional specific commercial software and hardware technology platforms, the present invention provides a disaster recovery method for middleware of Platform as a Service PaaS. The disaster recovery method for middleware of Platform as a Service PaaS proposed by the present invention is described below in conjunction with an embodiment.

[0030] See also Figure 1 , Figure 1 A basic flow chart of a disaster recovery method for a platform as a service (PaaS) middleware provided in the first embodiment of the present invention. The disaster recovery method for a platform as a service (PaaS) middleware includes:

[0031] S101: Determine that a first site is a first active site, detect that a middleware type of a second site meets a preset condition, and connect the first site to the second site.

[0032] In this embodiment, the first site includes: at least one middleware type and entity objects of the middleware type. Each middleware type may include 1 to n entity objects, the number of entity objects is n, and n is generally a natural number greater than zero. The first site is the first main site, and the second site is the backup site. The first site is a local site, and the second site is a remote site. The second site includes multiple middleware types and entity objects of the middleware type, each of which may include 1 to m entity objects, the number of entity objects is m, and m is generally a natural number greater than zero. The middleware type of the first site and the middleware type of the second site include at least one of the following: Posetgre database, ElasticSearch database, FTP service, Redis service, Kafak service, LDAP service, Zookeeper, PVC shared file. The detected middleware type of the second site meets the preset conditions, specifically the middleware type of the first site, the number of entity objects of the middleware type of the first site is consistent with the middleware type of the second site, and the number of entity objects of the middleware type of the second site is consistent, and the middleware type versions of the first site and the second site are compatible or consistent.

[0033] Preferably, the operation and maintenance personnel or users can input access parameters through the operation interface to access the opposite site and set the identity role of the site, such as setting the identity role of the own site as the primary site. Then, the preset condition information of the opposite site is obtained through the access address of the opposite site, and compared with the system condition information of the local site. If all matches are met, the access is successful; the primary and backup relationship is established, that is, the first site and the second site are connected.

[0034] S102: Configure disaster recovery parameters for at least one middleware-type entity object of each of the first site and the second site.

[0035] In this embodiment, the disaster recovery parameters include: quality of service QoS priority, communication address. The communication address is the communication address corresponding to the interaction data of each entity object of the first site and the second site. The communication address can be a unique identifier of all entity objects of middleware types contained in the system on the first site. The disaster recovery parameters can also include at least one of the following: synchronization cycle, timeout parameter. Preferably, the operation and maintenance personnel can select a certain entity object of the first site or the second site on the disaster recovery management console configuration interface that displays the entity objects of the first site and the second site to configure or view the disaster recovery parameters.

[0036] In this embodiment, step S101 is only used as an example before step S102. In actual application, the order of steps is not limited and the steps can be performed simultaneously. Alternatively, the disaster recovery parameters can be configured first and then the first site and the second site can be connected.

[0037] S103: Generate a first synchronization strategy according to the disaster recovery parameters.

[0038] In some embodiments, a first synchronization strategy is generated based on disaster recovery parameters. When the preset disaster recovery parameters include: QoS priority, communication address, the generated first synchronization strategy is to generate a data synchronization priority strategy for each entity object based on the QoS priority and the communication address corresponding to the interaction data of each entity object of the first site and the second site, to ensure that high-priority entity objects synchronize data first, and low-priority entity data are queued for synchronization or suspended for synchronization. The synchronization strategy includes at least one of the following: priority arrangement order, allocation of synchronization channels. It can be that one channel is used for synchronization from high to low priority; it can also be that high-priority critical business data occupies an exclusive channel for priority synchronization, and low-priority statistical business data queues and reuses one channel for synchronization or gives up the channel for suspension of synchronization.

[0039] In some embodiments, when the configured disaster recovery parameters include: a preset QoS priority, a communication address, a preset synchronization cycle, and a preset timeout parameter, the generated first synchronization strategy includes: according to the set QoS priority of each entity object, the set communication address corresponding to the interaction data of each entity object of the first site and the second site, and the preset synchronization cycle, if the connection between the middleware entity object of the first site and the middleware entity object of the second site fails to connect within a preset time, a data synchronization priority strategy is generated for each entity object, and the connection is reconnected a preset number of times. When the preset timeout time is reached, the middleware entity object is restarted. After the connection is successful, the data of the high-priority entity object is synchronized first according to the preset priority and the preset synchronization cycle, and the low-priority entity data is queued for synchronization or the synchronization is suspended.

[0040] In some embodiments, the method further includes: upon detecting a second preset event, stopping the step of generating the first synchronization strategy according to the disaster recovery parameters; wherein the second preset event includes at least one of the following: version upgrade of at least one type of middleware; maintenance upgrade of the first site; maintenance upgrade of the second site. It is also possible that upon detecting that a version upgrade of some middleware among all types of middleware is detected, but both the primary and backup sites are in normal status and have not been maintained or upgraded, the synchronization strategy generated by the disaster recovery parameters of some types of middleware is stopped, and the synchronization strategy is generated according to the disaster recovery parameters of other types of middleware.

[0041] In some embodiments, before generating the first synchronization strategy according to the disaster recovery parameters, it may also include: collecting relevant states during the operation of the entity objects of the middleware type; wherein the relevant states include at least one of the following: the hardware operation state required for the operation of each middleware type, and the operation state of each middleware type itself. The hardware operation state required for the operation of each middleware type includes at least one of the following: network bandwidth, CPU occupancy, memory utilization, and IO resource utilization; generating the first synchronization strategy according to the disaster recovery parameters includes: adjusting the data synchronization priority and / or data synchronization channel of the entity objects of each middleware type according to the relevant state. Preferably, when the collected relevant state exceeds the preset index, within the preset time, the operation and maintenance personnel are notified to intervene in the processing by email or SMS, and the abnormal state and prompt information are displayed on the user interface to guide the operation and maintenance personnel to troubleshoot according to the processing suggestions. The user interface may be the same interface as the display configuration interface of the disaster recovery control platform, or it may not be the same interface. When they are not the same interface, the display configuration interface of the disaster recovery control platform is visible to the operation and maintenance personnel. When it is not the same interface, key encryption can also be used. When the operation and maintenance personnel log in to the disaster recovery control platform, the user-visible interface is first displayed, and then a setting button on the interface is clicked to enter the decryption key, and / or a fixed place on the interface is clicked, and / or the decryption key of the required configuration interface is directly entered to enter the configuration interface controllable by the operation and maintenance personnel.

[0042] S104: Synchronize data of the entity object of the middleware type of the first site to the entity object of the middleware type corresponding to the second site according to the first synchronization strategy.

[0043] In some embodiments, when the disaster recovery parameters include: QoS priority, communication address, the generated first synchronization strategy is to generate a data synchronization priority strategy for each entity object based on the QoS priority and the communication address corresponding to the interaction data of each entity object of the first site and the second site, and synchronize the data of the middleware type entity object of the first site to the entity object of the middleware type corresponding to the second site according to the first synchronization strategy. Ensure that high-priority entity objects synchronize data first, and low-priority entity data are queued for synchronization or suspended for synchronization. The synchronization strategy includes at least one of the following: priority arrangement order, allocation of synchronization channels. It can be that high-priority critical business data has exclusive channel priority synchronization, and low-priority statistical business data queues to reuse a channel for synchronization or gives up the channel for suspension of synchronization.

[0044] In some embodiments, when the disaster recovery parameters include: a preset QoS priority, a communication address, and a preset synchronization period, the generated first synchronization strategy includes: based on the set QoS priority of each entity object, the set communication address corresponding to the interaction data of each entity object of the first site and the second site, and the preset synchronization period, a data synchronization priority strategy for each entity object is generated, and according to the first synchronization strategy, the data of the middleware type entity object of the first site is synchronized to the middleware type entity object corresponding to the second site.

[0045] Disaster recovery data can be synchronized in real time or periodically. In the middleware entity objects with real-time synchronization, data is synchronized from the primary site to the backup site through message flow and takes effect in real time. In the middleware entity objects with periodic synchronization, data is synchronized from the primary site to the backup site through import, export or object snapshot according to the set synchronization period and takes effect periodically. Ensure that high-priority entity objects synchronize data first, and low-priority entity data is queued for synchronization or suspended for synchronization.

[0046] In some embodiments, when synchronizing the data of the entity object of the middleware type of the first site to the entity object of the middleware type corresponding to the second site according to the first synchronization strategy, it can also include: collecting the synchronization status of the data of each entity object of the first site and the second site during the synchronization process, and when a first preset event occurs in the synchronization status, adjusting the first synchronization strategy to the second synchronization strategy, and synchronizing the data of the entity object of the middleware type of the first site to the entity object of the middleware type corresponding to the second site through the second synchronization strategy. The synchronization status includes at least one of the following: the synchronization bandwidth occupancy rate of at least one middleware entity object, the efficiency of data synchronization of each middleware entity object, the link connection status of the first site and the second site, the network connection status, and the connection timeout of the entity object of the middleware type of the primary and backup sites. When the first preset event occurs in the synchronization status, adjusting the first synchronization strategy to the second synchronization strategy includes at least one of the following:

[0047] When it is detected that the data synchronization efficiency of at least one entity object among all entity objects of the middleware type is reduced, the second synchronization strategy includes: pausing data synchronization of other entity objects with a priority lower than that of the at least one entity object; and / or; when it is detected that the synchronization bandwidth occupancy rate is low, adding a synchronization channel for at least one entity object, and / or, adding a synchronization thread for at least one entity object;

[0048] When the link connection state between the first site and the second site is disconnected, the second synchronization strategy includes: displaying a preset operation interface; the operation interface can be used to manually complete data synchronization of the middleware-type entity object from the first site to the second site.

[0049] When it is detected that at least one of all the synchronized data of the second site is out of sync with the real-time data of the first site or has a synchronization error, the second synchronization strategy includes: restarting the entity object of the middleware type corresponding to the at least one data, and then performing at least one data synchronization. Wherein restarting the entity object of the middleware type corresponding to the at least one data may also include: reconnecting the middleware entity objects of the first site and the second site, and restarting the entity object of the middleware type corresponding to the at least one data when the connection fails to be established after a preset number of connections.

[0050] When it is detected that too much entity object data is accumulated in the multiplexed channel or the exclusive channel during the synchronization process, the second synchronization strategy includes: suspending the synchronization of entity objects with lower priority than the over-backlogged entity object, and calling the suspended idle channel to synchronize the over-backlogged entity object data.

[0051] In some embodiments, the data of the entity objects of the middleware type of the first site are synchronized to the entity objects of the middleware type corresponding to the second site according to the first synchronization strategy, and then it may also include: the first site and the second site exchange roles, so that the first site is the second backup site and the second site is the second primary site, and data synchronization according to the first synchronization strategy is stopped; the unsynchronized data cache of the entity objects of the middleware type of the first primary site is cleared; a third synchronization strategy is generated according to the disaster recovery parameters of the reconfiguration of each middleware type entity object; according to the third synchronization strategy, the data of the entity objects of the middleware type of the second primary site are synchronized to the entity objects of the middleware type corresponding to the second backup site.

[0052] Wherein, before synchronizing the data of the entity objects of the middleware type of the second main site to the entity objects of the middleware type corresponding to the second backup site according to the third synchronization strategy, the relevant status of the entity objects of each middleware type of the second main site during operation may also be included; wherein the relevant status includes at least one of the following: the hardware operation status required for the operation of each middleware type, and the operation status of each middleware type itself. Wherein the hardware operation status required for the operation of each middleware type includes at least one of the following: network bandwidth, CPU occupancy, memory utilization, and IO resource utilization; generating the third synchronization strategy according to the disaster recovery parameters includes: adjusting the data synchronization priority and / or data synchronization channel of the entity objects of each middleware type according to the relevant status. Wherein, preferably, when the collected relevant status exceeds the preset indicator, within the preset time, the operation and maintenance personnel are notified to intervene in the processing by email or SMS, and the abnormal status and prompt information are displayed on the user interface to guide the operation and maintenance personnel to troubleshoot according to the processing suggestions.

[0053] When synchronizing the data of the middleware-type entity object of the second primary site to the middleware-type entity object corresponding to the second backup site according to the third synchronization strategy, it may also include: collecting the synchronization status of the data of each entity object of the primary and backup sites during the synchronization process, and when a first preset event occurs in the synchronization status, switching the third synchronization strategy to the second synchronization strategy.

[0054] In some embodiments, the data of the entity object of the middleware type of the first site is synchronized to the entity object of the middleware type corresponding to the second site according to the first synchronization strategy, and then it can also include: displaying the status of the synchronization of the data of the entity objects of the middleware type of the first site and the second site on the control display console; displaying the disaster recovery parameters of each middleware entity object; displaying the relevant status of the entity object of the middleware type during operation; displaying the link connection status of the first site and the second site; displaying the data content of each entity object, etc.

[0055] The control display console can also display the connection status of the operation interface when the first site and the second site are connected, and display the data synchronization status of the entity objects of the middleware type of the first site and the second site in real time when collecting relevant status or synchronization status; and display the relevant status of the entity objects of the middleware type during operation. After the disaster recovery parameters are set, the disaster recovery parameters of each middleware entity object are displayed on the disaster recovery management console interface. The related status of each middleware type displayed can be displayed in the form of a list, and the operation interface can also include an operation bar for manual switching of the primary and backup sites, and an operation bar for automatic switching of the primary and backup sites; an operation bar can also be set for each entity object of the middleware type, and the operation bar includes at least one of the following: an operation bar for configuration parameters, an operation bar for automatic synchronization, and an operation bar for manual execution.

[0056] The display interface of the disaster recovery management console can be as follows Figure 2 As shown, the status of disaster recovery operation can be intuitively grasped globally, including the link status between the primary and backup sites, the disaster recovery parameters of each middleware entity object and the life management process entry of disaster recovery, the health and alarm status of system operation, the operation status and progress of each middleware data synchronization, etc. It can also be used for user and / or operation and maintenance personnel operations, and can flexibly start and stop the disaster recovery of the middleware according to the granularity of the middleware instance as needed.

[0057] The PaaS middleware disaster recovery method provided by the embodiment of the present invention determines the primary site, detects that the middleware type of the backup site meets the preset conditions, and connects the primary and backup sites; configures disaster recovery parameters for the entity objects of the middleware types of the primary and backup sites, generates a data synchronization strategy based on the disaster recovery parameters, and synchronizes the data of the entity objects of each middleware type of the primary site to the entity objects of each middleware type of the corresponding backup site according to the synchronization strategy. Business disaster recovery is no longer tightly coupled with the business, and additional specific commercial software and hardware technology platforms are required in business disaster recovery, thereby saving disaster recovery costs.

[0058] Embodiment 2:

[0059] The PaaS middleware disaster recovery method of the present invention realizes that business disaster recovery is no longer tightly coupled with the business, and business disaster recovery requires additional specific commercial software and hardware technology platforms, saving disaster recovery costs. For ease of understanding, the PaaS middleware disaster recovery method of the present invention is explained below in conjunction with an application scenario.

[0060] Figure 3 A detailed flow chart of a PaaS middleware disaster recovery method provided in the second embodiment of the present invention, wherein the PaaS middleware disaster recovery method includes:

[0061] S301: Determine that a first site is a first active site, detect that a middleware type of a second site meets a preset condition, and connect the first site to the second site.

[0062] In this embodiment, the first site includes: at least one middleware type and entity objects of the middleware type. Each middleware type may include 1 to n entity objects, the number of entity objects is n, and n is generally a natural number greater than zero. The second site is the first standby site, and the second site includes multiple middleware types and entity objects of the middleware type, each middleware type may include 1 to m entity objects, the number of entity objects is m, and m is generally a natural number greater than zero. Among them, the middleware type of the first site and the middleware type of the second site include at least one of the following: Posetgre database, ElasticSearch database, FTP service, Redis service, Kafak service, LDAP service, Zookeeper, PVC shared file. Whether the detected intermediate type of the second site meets the preset conditions is specifically whether the middleware type of the first site, the number of entity objects of the middleware type of the first site are consistent with the middleware type of the second site, and the number of entity objects of the middleware type of the second site, and whether the middleware type versions of the first site and the second site are compatible or consistent.

[0063] S302: Configure disaster recovery parameters for at least one middleware-type entity object of each of the first site and the second site.

[0064] In this embodiment, the disaster recovery parameters include: Quality of Service (QoS) priority, and communication address. The communication address is a communication address corresponding to the interaction data of each entity object of the first site and the second site.

[0065] S303: Collect relevant states of the entity objects of the middleware type during operation.

[0066] The relevant status includes at least one of the following: the hardware status required for the operation of each middleware type, and the operation status of each middleware type itself. The hardware status required for the operation of each middleware type includes at least one of the following: network bandwidth, CPU occupancy, memory utilization, and IO resource utilization.

[0067] S304: Generate a first synchronization strategy according to the disaster recovery parameters and related states.

[0068] In this embodiment, a first synchronization strategy is generated based on disaster recovery parameters and related states. The disaster recovery parameters include: QoS priority, communication address. The synchronization strategy includes: priority arrangement order, allocation of synchronization channels. The generated first synchronization strategy is to generate a data synchronization priority strategy for each entity object based on the QoS priority and the corresponding communication address of the interaction data of each entity object of the first site and the second site, and collect the relevant states during the operation of the entity objects of the middleware type, adjust the data synchronization priority and / or data synchronization channel of the entity objects of each middleware type, and generate the first synchronization strategy to ensure that high-priority entity objects synchronize data first, and low-priority entity data are delayed to queue for synchronization or pause synchronization. It can be that high-priority critical business data has exclusive channel priority synchronization, and low-priority statistical business data queues to reuse a channel for synchronization or gives up the channel for synchronization.

[0069] S305: Synchronize the data of the entity object of the middleware type of the active site to the standby site according to the first synchronization strategy.

[0070] The PaaS middleware disaster recovery method provided by the embodiment of the present invention establishes a disaster recovery relationship between the primary and backup sites, configures the disaster recovery parameters of the middleware entity objects of the primary and backup sites, collects the relevant status of the entity objects of the middleware type during operation, and then generates a first synchronization strategy based on the disaster recovery parameters and the relevant status to synchronize the data of the entity objects of the primary site to the backup site, thereby achieving more flexible synchronization of various middleware entity object business data and achieving the best health state for business disaster recovery. It can better meet the telecom-level PaaS system operation scenarios---for example, operators uniformly provide cloud platform virtualization infrastructure, equipment vendors provide network element equipment, and divide the deployment scenarios for disaster recovery according to the equipment vendor's support for services, greatly improving the convenience and flexibility of deployment, and also significantly reducing the cost of disaster recovery deployment.

[0071] Embodiment three:

[0072] The PaaS middleware disaster recovery method of the present invention realizes that business disaster recovery is no longer tightly coupled with the business, and business disaster recovery requires additional specific commercial software and hardware technology platforms, saving disaster recovery costs. For ease of understanding, the PaaS middleware disaster recovery method of the present invention is explained below in conjunction with an application scenario.

[0073] Figure 4 A detailed flow chart of a PaaS middleware disaster recovery method provided in the second embodiment of the present invention, wherein the PaaS middleware disaster recovery method includes:

[0074] S401, receiving the communication address information of the standby site input by the user, detecting that the middleware type of the standby site meets the preset conditions, connecting to the primary and standby sites, and collecting the relevant status of the entity object of the middleware type during operation.

[0075] In this embodiment, the PaaS platform and business system have been installed locally and remotely, the business of each middleware has been verified to be able to operate normally, and the two places have been divided and determined as the disaster recovery main and backup site roles and network information. The user logs in to the disaster recovery management console, enters the disaster recovery communication address and information of the other end, and then accesses the site. In the process of accessing the matching disaster recovery relationship, it is necessary to match and detect the middleware type, entity quantity, version, and main and backup roles of the main and backup sites. Only after they meet the access conditions can the backup site be successfully accessed. The middleware type includes at least one of the following: Posetgre database, ElasticSearch database, FTP service, Redis service, Kafak service, LDAP service, Zookeeper, PVC shared files. Each middleware type can include 1 to n entity objects, and the number of entity objects is n, and n is generally a natural number greater than zero. The related status includes at least one of the following: the hardware operation status required for the operation of each middleware type, and the operation status of each middleware type itself. The hardware operation status required for the operation of each middleware type includes at least one of the following: network bandwidth, CPU occupancy, memory utilization, and IO resource utilization.

[0076] S402: Configure disaster recovery parameters for at least one middleware-type entity object of each of the primary and backup sites.

[0077] In this embodiment, the disaster recovery parameters include: Quality of Service (QoS) priority, communication address, synchronization period, and timeout parameter. The communication address is the communication address corresponding to the interactive data of each entity object of the first site and the second site.

[0078] S403: Generate a first synchronization strategy according to the disaster recovery parameters and related states.

[0079] In this embodiment, the generated first synchronization strategy includes: according to the set QoS priority of each entity object, the set communication address corresponding to the interaction data of each entity object of the first site and the second site, and the preset synchronization period, if the connection between the middleware entity object of the first site and the middleware entity object of the second site fails to be connected within the preset time, generate a data synchronization priority strategy for each entity object, reconnect a preset number of times, and when the preset timeout time is reached, restart the middleware entity object, and after the connection is successful, synchronize data for high-priority entity objects first according to the preset priority and the preset synchronization period, and postpone the synchronization of low-priority entity data or suspend the synchronization.

[0080] S404: Synchronize data of the entity object of the middleware type of the first site to the entity object of the middleware type corresponding to the second site according to the first synchronization strategy.

[0081] If the connection between the middleware entity object of the first site and the middleware entity object of the second site fails within the preset time, a data synchronization priority strategy is generated for each entity object, and the connection is reconnected for a preset number of times. When the preset timeout period is reached, the middleware entity object is restarted. After the connection is successful, the data of the high-priority entity object is synchronized first according to the preset priority and the preset synchronization period, and the low-priority entity data is queued for synchronization or suspended. In the real-time synchronized middleware entity objects, data is synchronized from the primary site to the backup site through message flow and takes effect in real time. In the periodically synchronized middleware entity objects, data is synchronized from the primary site to the backup site through import and export or object snapshot according to the set synchronization period and takes effect periodically.

[0082] S405: Collect the synchronization status of the data of each entity object of the primary and backup sites during the synchronization process.

[0083] The synchronization status includes at least one of the following: the synchronization bandwidth occupancy rate of at least one middleware entity object, the data synchronization efficiency of each middleware entity object, the link connection status between the first site and the second site, the network connection status, and the entity object connection timeout of the middleware type of the primary and backup sites.

[0084] S406: When a first preset event occurs in the synchronization state, the first synchronization strategy is adjusted to a second synchronization strategy.

[0085] In this embodiment, when a first preset event occurs in the synchronization state, adjusting the first synchronization strategy to the second synchronization strategy includes at least one of the following:

[0086] When it is detected that the data synchronization efficiency of at least one entity object among all entity objects of the middleware type is reduced, the second synchronization strategy includes: pausing data synchronization of other entity objects with a priority lower than that of the at least one entity object; and / or; when it is detected that the synchronization bandwidth occupancy rate is low, adding a synchronization channel for at least one entity object, and / or, adding a synchronization thread for at least one entity object;

[0087] When the link connection state between the first site and the second site is disconnected, the second synchronization strategy includes: displaying a preset operation interface; the operation interface can be used to manually complete data synchronization of the middleware type entity object from the first site to the second site.

[0088] When it is detected that at least one of all the synchronized data of the second site is out of sync with the real-time data of the first site or has a synchronization error, the second synchronization strategy includes: restarting the entity object of the middleware type corresponding to the at least one data, and then performing at least one data synchronization. Wherein restarting the entity object of the middleware type corresponding to the at least one data may also include: reconnecting the middleware entity objects of the first site and the second site, and restarting the entity object of the middleware type corresponding to the at least one data when the connection fails to be established after a preset number of connections.

[0089] When it is detected that too much entity object data is accumulated in the multiplexed channel or the exclusive channel during the synchronization process, the second synchronization strategy includes: suspending the synchronization of entity objects with lower priority than the entity object with too much backlog, and calling the idle channel after the suspension to synchronize the entity object data with too much backlog. After this step, S404-S406 are repeatedly executed until the middleware data reaches the optimal state of synchronization, or until the business stops running, or the primary and backup sites are exchanged.

[0090] S407 , the primary and backup sites are swapped, S403 - S406 are stopped, and disaster recovery parameters of entity objects of each middleware type are reconfigured.

[0091] In this embodiment, the primary and backup sites can be swapped manually by the user after logging into the disaster recovery management console, or when a disaster occurs, the disaster recovery console system can automatically determine and initiate the primary and backup switching operation. When the various preset conditions for automatic switching are met, the disaster recovery system determines that the primary site has been offline and stopped, then triggers the system automatic switching process, and switches the business to the backup site to take over and continue to run. After the primary and backup sites are swapped, it is necessary to clear the cached business data that has not been synchronized in each middleware entity object in the original primary site, and switch to the data benchmark of the newly upgraded primary site as the data disaster recovery standard baseline for the business data on the new backup site.

[0092] The disaster recovery parameters of the entity objects of each middleware type that are reconfigured may be pre-configured or manually configured through a disaster recovery management console. The disaster recovery parameters may include preset data priority, communication address, and may also include: preset data priority, communication address, preset timeout period, preset synchronization period. The disaster recovery parameters of each middleware type that are reconfigured may also be the disaster recovery parameters configured before the primary and backup sites are interchanged.

[0093] S408: Generate a third synchronization strategy according to the reconfigured disaster recovery parameters.

[0094] S409: Synchronize the data of the middleware-type entity object of the swapped active site to the middleware-type entity object corresponding to the role-swapped standby site according to the third synchronization strategy.

[0095] In this embodiment, before synchronizing the data of the entity objects of the middleware type of the second main site to the entity objects of the middleware type corresponding to the second backup site according to the third synchronization strategy, the relevant status of the entity objects of each middleware type in the second main site during operation may also be included; wherein the relevant status includes at least one of the following: the hardware operation status required for the operation of each middleware type, and the operation status of each middleware type itself. The hardware operation status required for the operation of each middleware type includes at least one of the following: network bandwidth, CPU occupancy, memory utilization, and IO resource utilization; generating the third synchronization strategy based on the disaster recovery parameters includes: adjusting the data synchronization priority and / or data synchronization channel of the entity objects of each middleware type according to the relevant status. Preferably, when the collected relevant status exceeds the preset indicator, the operation and maintenance personnel are notified to intervene in the processing by email or SMS within the preset time, and the abnormal status and prompt information are displayed on the user interface to guide the operation and maintenance personnel to troubleshoot according to the processing suggestions.

[0096] When synchronizing the data of the middleware-type entity object of the second primary site to the middleware-type entity object corresponding to the second backup site according to the third synchronization strategy, it may also include: collecting the synchronization status of the data of each entity object of the primary and backup sites during the synchronization process, and when a first preset event occurs in the synchronization status, switching the third synchronization strategy to the second synchronization strategy.

[0097] The PaaS middleware disaster recovery method provided by the embodiment of the present invention receives the communication address information of the standby site input by the user, detects that the middleware type of the standby site meets the preset conditions, connects to the primary and standby sites, collects the relevant status of the entity object of the middleware type during the operation process, performs disaster recovery parameter configuration on at least one entity object of the middleware type of the primary and standby sites, sets the QoS priority of each entity object, sets the communication address corresponding to the interactive data of each entity object of the first site and the second site, and sets the preset synchronization period. If the middleware entity object of the first site and the middleware entity object of the second site are not connected within the preset time during the connection process, generates the data synchronization priority strategy of each entity object, reconnects the preset number of times, restarts the middleware entity object when the preset timeout time is reached, and after the connection is successful, synchronizes the data of the high-priority entity object first according to the preset priority and the preset synchronization period, and queuing or suspending the synchronization of the low-priority entity data. In the synchronization process, collect the synchronization status of the data of each entity object of the primary and standby sites during the synchronization process. When the first preset event occurs in the synchronization state, adjust the first synchronization strategy to the second synchronization strategy, and synchronize the data according to the second synchronization strategy. After the manual or automatic exchange of the primary and standby sites, stop the original step of synchronizing the middleware data, use the data benchmark of the newly promoted primary site as the data disaster recovery standard baseline for the business data on the new standby site, and synchronize the data of each middleware entity object of the new primary site to the standby site according to the configured disaster recovery parameters. Decoupling from specific services is achieved, and disaster recovery is only performed on the middleware instances used by the business. Middleware disaster recovery can be flexibly started and stopped according to the granularity of the middleware instances as needed, and data synchronization of middleware entity objects in disaster recovery can be continuously fine-tuned and optimized to ensure that disaster recovery reaches the best state. It can better meet the operation scenarios of telecom-level PaaS systems - for example, operators uniformly provide cloud platform virtualization infrastructure, equipment vendors provide network element equipment, and disaster recovery is carried out according to the division of labor deployment scenarios supported by equipment vendors. The convenience and flexibility of deployment are greatly improved, and the cost of disaster recovery deployment is also greatly reduced.

[0098] Embodiment 4:

[0099] In order to solve the technical problems of business disaster recovery being tightly coupled with business or requiring additional specific commercial software and hardware technology platforms, the present invention provides a disaster recovery device for the middleware of Platform as a Service PaaS. The disaster recovery device for the middleware of Platform as a Service PaaS proposed by the present invention is described below in conjunction with an embodiment.

[0100] See also Figure 5 , Figure 5A schematic diagram of the composition of a disaster recovery device of a platform as a service (PaaS) middleware provided in the fourth embodiment of the present invention, wherein the disaster recovery device comprises: an access module 501, a configuration module 502, a control module 503 and a synchronization coordination module 504;

[0101] The access module 501 is used to determine that the first site is the first main site, and the first site includes: at least one middleware type and an entity object of the middleware type; when it is detected that the middleware type of the first site and the number of entity objects of the middleware type of the first site are consistent with the middleware type of the second site and the number of entity objects of the middleware type of the second site, and the middleware type versions of the first site and the second site are compatible or consistent, the first site and the second site are connected; the second site is a standby site;

[0102] The configuration module 502 is used to configure disaster recovery parameters for at least one middleware type entity object of the first site and the second site, the disaster recovery parameters including: quality of service QoS priority, communication address, and send the disaster recovery parameters to the control module 503 and the synchronous execution module 504;

[0103] The control module 503 is used to receive the disaster recovery parameters, generate a first synchronization strategy according to the disaster recovery parameters, and send the first synchronization strategy to the synchronization execution module 504;

[0104] The synchronization execution module 504 is used to receive the disaster recovery parameters and the first synchronization strategy, and synchronize the data of the middleware type entity object of the first site to the middleware type entity object corresponding to the second site according to the first synchronization strategy.

[0105] In this embodiment, the first site includes: at least one middleware type and entity objects of the middleware type. Each middleware type may include 1 to n entity objects, the number of entity objects is n, and n is generally a natural number greater than zero. The second site is the first standby site, and the second site includes multiple middleware types and entity objects of the middleware type, each middleware type may include 1 to m entity objects, the number of entity objects is m, and m is generally a natural number greater than zero. The middleware type of the first site and the middleware type of the second site include at least one of the following: Posetgre database, ElasticSearch database, FTP service, Redis service, Kafak service, LDAP service, Zookeeper, PVC shared file. The detected middleware type of the second site meets the preset conditions, specifically whether the middleware type of the first site, the number of entity objects of the middleware type of the first site and the middleware type of the second site are consistent with the middleware type of the second site, and whether the middleware type versions of the first site and the second site are compatible or consistent. The second site is a standby site.

[0106] Preferably, the operation and maintenance personnel or users can access the peer site by inputting access parameters through the operation interface of the disaster recovery management console 506, and set the identity role of the site, such as setting the identity role of the own site as the primary. Then, the preset condition information of the peer site is obtained through the access address of the peer site, and compared with the system condition information of the local site. If all matches are met, the access is successful and the primary-backup relationship is established.

[0107] The disaster recovery parameters of the first site and the second site configured by the configuration module 502 also include at least one of the following: synchronization period, timeout parameter. Preferably, the operation and maintenance personnel can select a certain entity object of the first site or the second site in the configuration interface of the disaster recovery management console 506 to configure or view the disaster recovery parameters. The communication address in the disaster recovery parameters is the communication address corresponding to the interactive data of each entity object of the first site and the second site.

[0108] In this embodiment, the control module 503 generates a first synchronization strategy based on disaster recovery parameters. When the disaster recovery parameters include: QoS priority, communication address, the generated first synchronization strategy is to generate a data synchronization priority strategy for each entity object based on the QoS priority and the corresponding communication address of the interaction data of each entity object of the first site and the second site, to ensure that high-priority entity objects synchronize data first, and low-priority entity data are queued for synchronization or suspended for synchronization. The synchronization strategy includes at least one of the following: priority arrangement order, allocation of synchronization channels. It can be that high-priority critical business data has exclusive channel priority synchronization, and low-priority statistical business data queues to reuse a channel for synchronization or gives up the channel for synchronization suspension. When the disaster recovery parameters include: preset QoS priority, communication address, preset synchronization cycle, preset timeout parameters, the generated first synchronization strategy includes: according to the set QoS priority of each entity object, the set communication address corresponding to the interaction data of each entity object of the first site and the second site, the preset synchronization cycle, if the connection between the middleware entity object of the first site and the middleware entity object of the second site fails to connect within the preset time, generate a data synchronization priority strategy for each entity object, reconnect a preset number of times, when the preset timeout time is reached, restart the middleware entity object, and after the connection is successful, synchronize data for high-priority entity objects first according to the preset priority and preset synchronization cycle, and postpone the synchronization of low-priority entity data or suspend the synchronization.

[0109] In this embodiment, the disaster recovery device may further include: a collection module 505; the collection module 505 is used to collect relevant states during the operation of the entity object of the middleware type; the relevant states include at least one of the following: the hardware operation state required for the operation of the middleware type, the operation state of the middleware type itself; and send the relevant states to the control module;

[0110] The relevant status includes at least one of the following: the hardware operating status required for the operation of each middleware type, and the operating status of each middleware type itself. The hardware operating status required for the operation of each middleware type includes at least one of the following: network bandwidth, CPU occupancy, memory utilization, and IO resource utilization. Preferably, when the collected relevant status exceeds the preset indicator, the operation and maintenance personnel are notified to intervene in the processing by email or SMS within the preset time, and the abnormal status and prompt information are displayed on the user interface to guide the operation and maintenance personnel to troubleshoot according to the processing suggestions.

[0111] The control module 503 is further configured to receive relevant status and generate a first synchronization strategy according to the disaster recovery parameters and the relevant status; the first synchronization strategy includes: adjusting the data synchronization priority of the entity object of the middleware type according to the relevant status.

[0112] Specifically, the control module 503 adjusts the data synchronization priority and / or data synchronization channel of the entity objects of each middleware type according to the relevant status.

[0113] In this embodiment, the collection module 505 of the disaster recovery device can also be used to collect the synchronization status of the data of the middleware type entity object during the synchronization process when the synchronization execution module synchronizes the data of the middleware type entity object of the first site and the second site according to the first synchronization strategy, and send the synchronization status to the control module; wherein the synchronization status includes at least one of the following: the synchronization bandwidth occupancy rate of at least one middleware entity object, the data synchronization efficiency of each middleware entity object, the link connection status of the first site and the second site, the network connection status, and the connection timeout of the middleware type entity object of the primary and backup sites.

[0114] The control module 503 is further configured to adjust the first synchronization strategy to a second synchronization strategy and send the second synchronization strategy to the synchronization execution module 504 when a preset event occurs in the synchronization state;

[0115] The synchronization execution module 504 is further configured to synchronize the data of the entity object of the middleware type at the first site to the entity object of the middleware type corresponding to the second site through a second synchronization strategy.

[0116] Specifically, when the control module 503 detects that the received synchronization state has a first preset event, adjusting the first synchronization strategy to the second synchronization strategy includes at least one of the following:

[0117] When it is detected that the data synchronization efficiency of at least one entity object among all entity objects of the middleware type is reduced, the second synchronization strategy includes: pausing data synchronization of other entity objects with a priority lower than that of the at least one entity object; and / or; when it is detected that the synchronization bandwidth occupancy rate is low, adding a synchronization channel for at least one entity object, and / or, adding a synchronization thread for at least one entity object;

[0118] When the link connection state between the first site and the second site is disconnected, the second synchronization strategy includes: displaying a preset operation interface; the operation interface can be used to manually complete data synchronization of the middleware-type entity object from the first site to the second site.

[0119] When it is detected that at least one of all the synchronized data of the second site is out of sync with the real-time data of the first site or has a synchronization error, the second synchronization strategy includes: restarting the entity object of the middleware type corresponding to the at least one data, and then performing at least one data synchronization. Wherein restarting the entity object of the middleware type corresponding to the at least one data may also include: reconnecting the middleware entity objects of the first site and the second site, and restarting the entity object of the middleware type corresponding to the at least one data when the connection fails to be established after a preset number of connections.

[0120] When it is detected that too much entity object data is accumulated in the multiplexed channel or the exclusive channel during the synchronization process, the second synchronization strategy includes: suspending the synchronization of entity objects with lower priority than the over-backlogged entity object, and calling the suspended idle channel to synchronize the over-backlogged entity object data.

[0121] The control module 503 can receive the health performance index parameters and state parameters of the disaster recovery function of the main site collected by the collection module 505, and according to the priority setting of the middleware entity object, combined with the resource utilization index of the network bandwidth / CPU / memory / IO, generate a data synchronization strategy according to the intelligent algorithm and send it to the synchronization execution module 504 to control and adjust the priority of data synchronization, ensure that the high-priority key business data has priority synchronization in the exclusive channel, and the low-priority statistical business data queues to reuse a channel for synchronization or let the channel suspend synchronization, and monitor the health performance index of the middleware entity object in real time. If it is detected that the performance load exceeds the standard or the middleware disaster recovery business processing is abnormal, it is necessary to send an alarm in time, and notify the operation and maintenance personnel to intervene and handle it by email or SMS. At the same time, the abnormal state and prompt information are displayed in the user interface to guide the operation and maintenance personnel to troubleshoot according to the processing suggestions. According to the received operation status indicators, the data synchronization strategy of the middleware entity object in the disaster recovery can be continuously fine-tuned and optimized to ensure that the disaster recovery reaches the best state.

[0122] The synchronization execution module 504 can synchronize data according to the synchronization strategy. When the disaster recovery parameters include the quality of service QoS priority, communication address, synchronization cycle and timeout parameters, for the middleware entity objects that need real-time synchronization, the data is synchronized from the primary site to the backup site through the message flow to take effect in real time. For the middleware entity objects that need periodic synchronization, the data is synchronized from the primary site to the backup site through import and export or object snapshot according to the set synchronization cycle to take effect periodically.

[0123] During the synchronization process, the acquisition module collects the running status. When abnormal situations such as network interruption, service withdrawal, timeout restart, network congestion and excessive data backlog are found, the control module 503 generates a synchronization strategy based on the intelligent algorithm and sends it to the synchronization execution module to adjust the synchronization mode. For abnormal errors, retry and redo are used to restore synchronous replication, or restart the middleware entity object reset process or dynamically adjust the data synchronization priority channel and queue and suspend low-priority data synchronization, dynamically adjust the synchronization thread, allocate exclusive or reused synchronization channels, ensure that high-priority data is synchronized first, and low-priority data is queued for synchronization, and meet the priority indicators of disaster recovery business data. If the middleware entity object cannot recover by itself under various strategies, an alarm is reported to notify the operation and maintenance personnel to intervene in troubleshooting.

[0124] In this embodiment, the device may also include a disaster recovery management console 506, through which the disaster recovery of entity objects of the middleware type can be flexibly started and stopped as needed according to the granularity of the middleware instance. It is a portal and entry for disaster recovery management, integrating the management of the access module 501, the management of the configuration module 502, and the intelligent control function, and can intuitively grasp the overall status of disaster recovery operation: including displaying the link status between the primary and standby sites, the disaster recovery parameters of each middleware entity object, and the entry of the life management process of disaster recovery, the health and alarm status of the system operation, and the operation status and progress of each middleware data synchronization.

[0125] The data disaster recovery synchronization of middleware objects can be performed in batches or on demand with one click. During the maintenance and upgrade of the business version or site, the disaster recovery synchronization replication process needs to be interrupted to avoid uncontrollable abnormal data synchronization. The disaster recovery management console 506 provides a one-click batch stop of the disaster recovery synchronization process of all middleware entity objects, and data replication is suspended. At the same time, the control module scheduling process and the indicator collection process related to the collection module are stopped to avoid the false triggering of abnormal alarm reporting.

[0126] During the operation of disaster recovery, various abnormal situations may occur, such as abnormal network interruption and site power outage, which may cause data disorder or large differences between the primary and backup sites. There are also scenarios where the on-site site is upgraded from a single site to a primary and backup disaster recovery site. In this scenario, the manual forced synchronization function provided by the disaster recovery console can be used to complete the full synchronization of data between the primary and backup sites, and quickly achieve consistency of business disaster recovery data between the primary and backup sites. After the manual synchronization is completed, the consistency of the primary and backup data is guaranteed in real time according to the data increment in the automatic incremental synchronization process.

[0127] The PaaS middleware disaster recovery device provided by the embodiment of the present invention accesses the primary and backup sites through the access module, configures at least one entity object of the middleware type of the primary and backup sites to configure disaster recovery parameters, and sends the disaster recovery parameters to the control module and the synchronization execution module. The control module receives the disaster recovery parameters, generates a first synchronization strategy according to the disaster recovery parameters, and sends the first synchronization strategy to the synchronization execution module. The synchronization execution module receives the disaster recovery parameters and the first synchronization strategy, and synchronizes the data of the entity object of the middleware type in the primary site to the entity object of the middleware type corresponding to the backup site according to the first synchronization strategy. This makes the business disaster recovery no longer tightly coupled with the business, and the business disaster recovery requires additional specific commercial software and hardware technology platforms, saving disaster recovery costs.

[0128] Embodiment 5

[0129] This embodiment also provides a disaster recovery device. Figure 6 As shown, it includes a processor 601, a memory 602 and a communication bus 603, wherein:

[0130] The communication bus 603 is used to realize the connection and communication between the processor 601 and the memory 602;

[0131] The processor 601 is used to execute one or more computer programs stored in the memory 602 to implement at least one step in the disaster recovery method of the middleware of the Platform as a Service (PaaS) in any one of the above-mentioned embodiments 1 to 3.

[0132] The present embodiment also provides a computer-readable storage medium, which includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). Computer-readable storage media include, but are not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and can be accessed by a computer.

[0133] The computer-readable storage medium in this embodiment can be used to store one or more computer programs, and the one or more computer programs stored therein can be executed by a processor to implement at least one step in the disaster recovery method of the middleware of the Platform as a Service PaaS in any one of the above-mentioned Examples 1 to 3.

[0134] In the embodiment of the present invention, by establishing a disaster recovery relationship between the primary and backup sites, configuring the disaster recovery parameters of the middleware entity objects of the primary and backup sites, collecting the relevant status of the entity objects of the middleware type during operation, and then generating the first synchronization strategy based on the disaster recovery parameters and the relevant status to synchronize the data of the entity objects of the primary site to the backup site, it is possible to synchronize the business data of various middleware entity objects more flexibly and achieve the best health state of business disaster recovery. It can better meet the operation scenarios of the telecom-level PaaS system---for example, the operator uniformly provides the cloud platform virtualization infrastructure, the equipment vendor provides the network element equipment, and the division of labor deployment scenarios for disaster recovery are carried out according to the business supported by the equipment vendor, which greatly improves the convenience and flexibility of deployment, and also significantly reduces the cost of disaster recovery deployment.

[0135] It can be seen that those skilled in the art should understand that all or some of the steps, systems, and functional modules / units in the above disclosed methods can be implemented as software (which can be implemented with computer program code executable by a computing device), firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component can have multiple functions, or a function or step can be performed by several physical components in cooperation. Some or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit.

[0136] In addition, it is well known to those skilled in the art that communication media generally contain computer readable instructions, data structures, computer program modules or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery media. Therefore, the present invention is not limited to any specific hardware and software combination.

Claims

1. A disaster recovery method for middleware of Platform as a Service (PaaS), characterized in that: The disaster recovery method includes: Determine that the first site is the first main site, detect that the middleware type of the first site and the number of entity objects of the middleware type of the first site are consistent with the middleware type of the second site and the number of entity objects of the middleware type of the second site, and when the middleware type versions of the first site and the second site are compatible or consistent, connect the first site and the second site; the second site is a backup site; the middleware type of the first site and the middleware type of the second site include at least one of the following: Posetgre database, ElasticSearch database, FTP service, Redis service, Kafak service, LDAP service, Zookeeper, PVC shared file; Performing disaster recovery parameter configuration on at least one middleware type entity object of the first site and the second site, wherein the disaster recovery parameters include: quality of service QoS priority, and communication address; Generate a first synchronization strategy according to the disaster recovery parameters; The data of the entity object of the middleware type of the first site is synchronized to the entity object of the middleware type corresponding to the second site according to the first synchronization strategy.

2. The disaster recovery method according to claim 1, characterized in that: The disaster recovery parameters also include at least one of the following: a synchronization period and a timeout parameter.

3. The disaster recovery method according to claim 1, characterized in that: Generating the first synchronization strategy according to the disaster recovery parameter includes: Collecting relevant states of the entity object of the middleware type of the first site during operation; the relevant states include at least one of the following: the operating state of the hardware required for the operation of the middleware type, and the operating state of the middleware type itself; The related status is received, and the first synchronization strategy is generated according to the disaster recovery parameter and the related status; the first synchronization strategy includes: adjusting the priority of data synchronization of the entity object of the middleware type according to the related status.

4. The disaster recovery method according to claim 1, characterized in that: When synchronizing the data of the entity object of the middleware type of the first site to the entity object of the middleware type corresponding to the second site according to the first synchronization strategy, it also includes: collecting the synchronization status of the data during synchronization; When a first preset event occurs in the synchronization state, adjusting the first synchronization strategy to a second synchronization strategy; The data of the entity object of the middleware type of the first site is synchronized to the entity object of the middleware type corresponding to the second site through the second synchronization strategy.

5. The disaster recovery method according to claim 4, characterized in that: The synchronization status includes at least one of the following: synchronization bandwidth occupancy rate of the at least one middleware, data synchronization efficiency of entity objects of the middleware type, link connection status between the first site and the second site; When a first preset event occurs in the synchronization state, adjusting the first synchronization strategy to the second synchronization strategy includes at least one of the following: When it is detected that the data synchronization efficiency of at least one entity object among all entity objects of the middleware type is reduced, the second synchronization strategy includes: pausing data synchronization of other entity objects whose priority is lower than that of the at least one entity object; and / or; when it is detected that the synchronization bandwidth occupancy rate is low, adding a synchronization channel for the at least one entity object, and adding a synchronization thread for the at least one entity object; When the link connection state is disconnected, the second synchronization strategy includes: displaying a preset operation interface; When it is detected that at least one data among all the synchronized data of the second site is not synchronized with the real-time data of the first site or is synchronized incorrectly, the second synchronization strategy includes: restarting the entity object of the middleware type corresponding to the at least one data, and then synchronizing the at least one data.

6. The disaster recovery method according to any one of claims 1 to 5, characterized in that: The method further includes: detecting a second preset event and stopping generating the first synchronization strategy according to the disaster recovery parameter; the second preset event includes at least one of the following: Version upgrade of the middleware type; The first site is maintained and upgraded; The second site is maintained and upgraded.

7. The disaster recovery method according to any one of claims 1 to 5, characterized in that: Synchronize the data of the entity object of the middleware type of the first site to the entity object of the middleware type corresponding to the second site according to the first synchronization strategy, and then include: the first site and the second site exchange roles, so that the first site is the second backup site, the second site is the second main site, and stop synchronizing data according to the first synchronization strategy; clear the unsynchronized data cache of the entity object of the middleware type of the first main site; A third synchronization strategy is generated according to the disaster recovery parameters; and data of the middleware-type entity object of the second active site is synchronized to the middleware-type entity object corresponding to the second standby site according to the third synchronization strategy.

8. The disaster recovery method according to claim 5, characterized in that: According to the first synchronization strategy, the data of the middleware type entity object of the first site is synchronized to the middleware type entity object corresponding to the second site, and then it also includes: displaying the disaster recovery parameters of each middleware entity object; displaying the relevant status of the middleware type entity object during operation, and displaying the link connection status of the first site and the second site.

9. A disaster recovery device for a middleware of a platform as a service (PaaS), the disaster recovery device comprising: Access module, configuration module, control module and synchronous execution module; The access module is used to determine that the first site is the first main site, detect that the middleware type of the first site and the number of entity objects of the middleware type of the first site are consistent with the middleware type of the second site and the number of entity objects of the middleware type of the second site, and connect the first site and the second site when the middleware type versions of the first site and the second site are compatible or consistent; the second site is a backup site; the middleware type of the first site and the middleware type of the second site include at least one of the following: Posetgre database, ElasticSearch database, FTP service, Redis service, Kafak service, LDAP service, Zookeeper, PVC shared file; The configuration module is used to configure disaster recovery parameters for at least one middleware-type entity object of the first site and the second site, wherein the disaster recovery parameters include: quality of service QoS priority, communication address, and send the disaster recovery parameters to the control module and the synchronization execution module; The control module is used to receive the disaster recovery parameters, generate a first synchronization strategy according to the disaster recovery parameters, and send the first synchronization strategy to the synchronization execution module; The synchronization execution module is used to receive the disaster recovery parameters and the first synchronization strategy, and synchronize the data of the middleware-type entity object of the first site to the middleware-type entity object corresponding to the second site according to the first synchronization strategy.

10. The disaster recovery device according to claim 9, characterized in that: The disaster recovery device further includes: a collection module; The acquisition module is used to acquire relevant states during the operation of the entity object of the middleware type; the relevant states include at least one of the following: the operating state of the hardware required for the operation of the middleware type, the operating state of the middleware type itself; and send the relevant states to the control module; The control module is also used to receive the relevant status and generate the first synchronization strategy according to the disaster recovery parameters and the relevant status; the first synchronization strategy includes: adjusting the data synchronization priority of the entity object of the middleware type according to the relevant status.

11. The disaster recovery device according to claim 9, characterized in that: The disaster recovery device further includes: a collection module; the collection module is used to collect the synchronization status of the data during the synchronization process when the synchronization execution module synchronizes the data of the entity objects of the middleware type of the first site and the second site according to the first synchronization strategy, and send the synchronization status to the control module; The control module is further configured to adjust the first synchronization strategy to a second synchronization strategy and send the second synchronization strategy to the synchronization execution module when a first preset event occurs in the synchronization state; The synchronization execution module is further used to synchronize the data of the entity object of the middleware type of the first site to the entity object of the middleware type corresponding to the second site through the second synchronization strategy.

12. A disaster recovery device, characterized in that: The device includes a processor, a memory and a communication bus; The communication bus is used to realize the connection and communication between the processor and the memory; The processor is used to execute one or more computer programs stored in the memory to implement the steps of the disaster recovery method for the middleware of the Platform as a Service (PaaS) according to any one of claims 1 to 8.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to implement the steps of the disaster recovery method for the middleware of the Platform as a Service PaaS as described in any one of claims 1 to 8.

Images