CN111355988B - Business disaster recovery method, equipment and readable storage medium - Google Patents
Business disaster recovery method, equipment and readable storage medium Download PDFInfo
- Publication number
- CN111355988B CN111355988B CN202010244923.7A CN202010244923A CN111355988B CN 111355988 B CN111355988 B CN 111355988B CN 202010244923 A CN202010244923 A CN 202010244923A CN 111355988 B CN111355988 B CN 111355988B
- Authority
- CN
- China
- Prior art keywords
- resource module
- module
- resource
- service
- disaster recovery
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/266—Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0668—Management of faults, events, alarms or notifications using network fault recovery by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/24—Monitoring of processes or resources, e.g. monitoring of server load, available bandwidth, upstream requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
- H04N21/262—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists
- H04N21/26208—Content or additional data distribution scheduling, e.g. sending additional data at off-peak times, updating software modules, calculating the carousel transmission frequency, delaying a video stream transmission, generating play-lists the scheduling operation being performed under constraints
Abstract
The invention discloses a service disaster recovery method, equipment and a readable storage medium, wherein the method comprises the following steps: after the target resource module is detected to be abnormal, determining a normal designated resource module from the resource pool; disaster recovery of the service data of the target resource module to the specified resource module; and responding to the service of the target resource module by utilizing the resource pool management program of the specified resource module and combining the service data. Therefore, after the method is applied, the media service is taken over by the appointed resource module after the target resource module is abnormal without human intervention, the whole process can be automatically processed, the interruption time of the media service can be effectively reduced, the corresponding media service can still be provided after the target resource module is abnormal, and the user experience can be improved.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a service disaster recovery method, a device, and a readable storage medium.
Background
Resource services often need to meet disaster recovery scenarios. For example, media services of a cloud platform need to meet disaster recovery scenarios: due to an artificial or non-artificial reason, a certain media resource is abnormal, and a user wants that a service in use is not influenced or influenced as little as possible. However, in the current media service of the cloud platform, when a certain media resource is abnormal, the service provided by the media resource to the outside is interrupted. At present, the exception handling of the media resources is often performed by outputting an alarm, and after the alarm is obtained, relevant personnel perform manual handling, which results in long recovery time of relevant services. During the period, the service used by the user cannot be continued, and the user experience is influenced.
In summary, how to effectively solve the problems such as resource abnormality is a technical problem that needs to be solved urgently by those skilled in the art.
Disclosure of Invention
The invention aims to provide a service disaster recovery method, equipment and a readable storage medium, wherein when media resources are detected to be abnormal, service is taken over in a disaster recovery mode, so that the service is not influenced by abnormal resource modules, the service can be ensured not to be interrupted, and user experience can be improved.
In order to solve the technical problems, the invention provides the following technical scheme:
a service disaster recovery method comprises the following steps:
after the target resource module is detected to be abnormal, determining a normal designated resource module from the resource pool;
disaster recovery is carried out on the service data of the target resource module to the specified resource module;
and responding and processing the service of the target resource module by utilizing the resource pool management program of the specified resource module and combining the service data.
Preferably, the determining a normal designated resource module from the resource pool includes:
judging whether available resources exist in a local resource pool to which the target resource module belongs;
if yes, selecting or creating the specified resource module in the local resource pool;
if not, selecting or creating the appointed resource module from the resource pool to which the target resource module does not belong.
Preferably, selecting or creating the specified resource module in the local resource pool includes:
if the available resource modules exist in the local resource pool, determining the designated resource module in the available resource modules;
and if the optional resource module does not exist in the local resource pool, creating the appointed resource module in the local resource pool.
Preferably, determining the designated resource module from the selectable resource modules includes:
acquiring the resource utilization rate of each selectable resource module;
and taking the selectable resource module with the lowest resource utilization rate as the specified resource module.
Preferably, the step of disaster-backing the service data of the target resource module to the designated resource module, where the designated resource module belongs to the local resource pool, includes:
if the target resource module is a video module, disaster recovery is carried out on video decoding information and video coding information to the specified resource module; wherein the video decoding information includes: the number of video decoding paths, and the decoding format, resolution, frame rate, code rate and receiving address of each path; the video coding information includes: the number of video coding paths, and the coding format, resolution, frame rate, code rate and sending address of each path;
if the target resource module is an audio module, disaster recovery is carried out on audio decoding information and audio coding information to the specified resource module; wherein the audio decoding information includes: the number of audio decoding paths, and the decoding format, the number of sound channels and the receiving address of each path; the audio coding information includes: the number of audio coding paths, and the coding format, the number of sound channels and the sending address of each path.
Preferably, the step of disaster-backing the service data of the target resource module to the designated resource module, where the designated resource module does not belong to the local resource pool, includes:
if the target resource module is a video module, disaster recovery is carried out on video decoding information and video coding information to the specified resource module; wherein the video decoding information comprises: the number of video decoding paths, and the decoding format, resolution, frame rate and code rate of each path; the video coding information includes: the number of video coding paths, and the coding format, resolution, frame rate and code rate of each path;
if the target resource module is an audio module, disaster recovery is carried out on audio decoding information and audio coding information to the specified resource module; wherein the audio decoding information includes: the number of audio decoding paths, and the decoding format and the number of sound channels of each path; the audio encoding information includes: the number of audio coding paths, and the coding format and the number of sound channels of each path.
Preferably, after detecting that the target resource module is abnormal, before performing response processing on the media service of the target resource module by using the specified resource module and combining the service data, the method includes:
and stopping receiving and transmitting the code stream of the target resource module.
A business disaster recovery device, comprising:
a memory for storing a computer program;
and the processor is used for realizing the steps of the business disaster recovery method when the computer program is executed.
A readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the above-described service disaster recovery method.
According to the method provided by the embodiment of the invention, after the abnormality of the target resource module is detected, the normal designated resource module is determined from the resource pool; disaster recovery of the service data of the target resource module to the specified resource module; and responding and processing the service of the target resource module by utilizing the resource pool management program of the specified resource module and combining the service data.
In the method, when the abnormality of the target resource module is detected, a normal specified resource module is determined from a resource pool, and then the service data of the target resource module is disaster-prepared to the specified resource module. The resource pool management program of the appointed resource module can respond to the service of the target resource module based on the service data, namely, the appointed resource module can manage the service of the target resource module. Therefore, when the target resource module is abnormal, the appointed resource module takes over the service without human intervention, the whole process can be automatically processed, the service interruption can be avoided, the corresponding service can be still provided after the target resource module is abnormal, and the user experience can be improved.
Accordingly, embodiments of the present invention further provide a service disaster recovery device and a readable storage medium corresponding to the service disaster recovery method, which have the above technical effects and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the prior art descriptions will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a flowchart of an implementation of a service disaster recovery method according to an embodiment of the present invention;
FIG. 2 is a diagram illustrating allocation of media resources according to an embodiment of the present invention;
fig. 3 is a schematic diagram illustrating that the same resource module takes over a media service in the embodiment of the present invention;
fig. 4 is a schematic diagram illustrating taking over of media services between different media resources according to an embodiment of the present invention;
fig. 5 is a schematic diagram illustrating a disaster recovery to another normal media resource pool management program after an abnormal media resource pool management program according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a service disaster recovery device in an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a service disaster recovery device in an embodiment of the present invention;
fig. 8 is a schematic diagram of a service disaster recovery framework according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the disclosure, reference will now be made in detail to the embodiments of the disclosure as illustrated in the accompanying drawings. It should be apparent that the described embodiments are only some embodiments of the present invention, and not all embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, belong to the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a flowchart of a service disaster recovery method in an embodiment of the present invention, where the method may be applied to a resource pool management device (or a separate service disaster recovery device), and the method includes the following steps:
s101, after the target resource module is detected to be abnormal, determining a normal designated resource module from the resource pool.
The target resource module may be regarded as a resource module of a certain service (such as a media service, a conference service, a video playing service, a live broadcast service, and the like) supported by a chip set formed by one or more chips. For example, when the target resource module is a resource module corresponding to the media service, the target resource module may be specifically classified as a video module or an audio module corresponding to the category of the media service; the video module is a module for coding and decoding a video service, and the audio module is a module for coding and decoding an audio service (i.e. a voice service), i.e. the target resource module may be specifically an audio module or a video module; when the target resource module is a resource module corresponding to the conference service, the target resource module can be specifically a conference module; when the target resource module is a module corresponding to a video playing service, the target resource module may be a tv program module, a movie module, or a short video module.
Whether the target resource module is abnormal or not can be determined in a heartbeat mode mutually probing with the target resource module, or the service of the target resource module is monitored, and when the service is interrupted or not responded after time-out, the target resource module is considered to be abnormal.
After the target resource module is determined to be abnormal, a normal appointed resource module can be determined from the resource pool so as to take over the service of the target resource module.
When the designated resource module is determined, the determination can be made from the local resource pool to which the target resource module belongs, or can be made from other resource pools to which the non-target resource module belongs. Specifically, the target resource module and the designated resource module may belong to the same resource pool of the same operator, or may belong to resource pools of different operators, respectively; when the resource module belongs to one operator, the resource module is appointed to belong to a local resource pool; when not belonging to the same operator, the designated resource module does not belong to the local resource pool.
Preferably, in practical application, the specified resource module can be preferentially determined from the local media pool, so that the complexity of service taking over can be reduced. The specific implementation process comprises the following steps:
step one, judging whether available resources exist in a local resource pool to which a target resource module belongs;
step two, if yes, selecting or creating a designated resource module in the local resource pool;
and step three, if not, selecting or creating the appointed resource module from the resource pool to which the non-target resource module belongs.
For convenience of description, the above three steps will be described in combination.
First, it can be determined whether there are available resources in the resource pool (i.e. local resource pool) of the operator corresponding to the target resource module. Specifically, whether available resources exist can be known by receiving the resource report information of each resource module. The available resource may be a chip capable of creating a normal resource module, or may also be a created and normal resource module, and the resource module further has a capability of taking over a service of the target resource module.
Preferably, in order to facilitate management (such as disaster recovery, service capacity expansion, and the like), the registration and resource report of the resource modules corresponding to the resource pools corresponding to different operators may be received by using a communication structure of the same standard.
When available resources exist in the local resource pool, the specified resource module can be directly created or selected. Specifically, selecting or creating the specified resource module in the local resource pool may specifically include the following manners:
mode 1: if the available resource modules exist in the local media pool, determining the appointed resource module in the available resource modules;
mode 2: and if the local media resources have no available resource module, creating a specified resource module in the local resource pool.
Namely, when the selectable resource modules exist, the appointed resource module can be directly determined from the selectable resource modules; the creation step of the resource module can be omitted.
Preferably, in order to implement load balancing, when a plurality of selectable resource modules exist in a local media resource, resource utilization rates (such as CPU utilization rates or remaining storage resources) of the selectable resource modules may be obtained; and taking the selectable resource module with the lowest resource utilization rate as the designated resource module. Thus, the pressure overload of a single resource module can be avoided, and the service performance is further prevented from being influenced.
When there are no resources available in the local resource pool, a specified resource module may be created or selected across operators at this time. The process of determining the designated resource module from the resource pools of other operators is similar to the process of determining the designated resource module from the local resource pool, and is not described in detail herein.
It should be noted that the specific type of the specified resource module that is newly determined corresponds to the specific type of the target resource module. Namely, when the target resource module is a video module, the designated resource module should also be the video module; when the target resource module is an audio module, then the specified resource module should also be an audio module.
By way of example: referring to fig. 3, in the same media resource, when an abnormality occurs in the video module a and the audio module C that are in use, service data such as media encoding and decoding parameters and the like on the original video module a and the original audio module C are preferentially disaster-backed onto the video module B and the audio module D on the internal normal chip, respectively, so that the video module B takes over the media service of the video module a, and the audio module D takes over the media service of the video module C.
Referring to fig. 4, if there is an abnormality in the video module a and the audio module C in the currently used media resource-1 and there is no disaster-tolerant resource in the media resource-1, service data of the video module a and the audio module C are disaster-tolerant to the video module E and the audio module F of the media resource-2 that are in a normal state and are currently idle, respectively, so that the video module E takes over the media service of the video module a, and the audio module F takes over the media service of the audio module C.
And S102, disaster recovery of the service data of the target resource module to the specified resource module.
After the appointed resource module is determined, the service data of the target resource module can be disaster-prepared to the appointed resource module, so that the appointed resource module can take over the media service of the target resource module.
The service data is related data content corresponding to the specific service supported by the target resource module. For example, if the specific service supported by the target resource module is a conference service, the service data corresponds to conference data, a conference protocol, current conference participating terminal information, and the like; if the specific service supported by the target resource module is a video playing service, the service data includes video resources (such as video data of movies and television shows), and currently played or downloaded user side information.
In order to ensure that the media service takes over successfully, in this embodiment, different processing modes are provided for the service disaster with respect to the difference of the resources to which the specified resource module belongs. That is, for the designated resource module in the local resource, the designated resource module and the target resource module belong to the same local area network, and the port and the IP providing the service to the outside can be kept consistent. Therefore, the designated resource module belongs to the local media resource, and the IP address of the target resource module, such as the sending address and the receiving address in the video/audio codec, can be continuously used on the designated resource module during the disaster recovery service data. The following describes in detail the process of disaster recovery service data in the same resource pool, taking a video module and an audio module as examples:
if the target resource module is a video module, disaster recovery is carried out on video decoding information and video coding information to a specified resource module; wherein the video decoding information includes: the number of video decoding paths, and the decoding format, resolution, frame rate, code rate and receiving address of each path; the video coding information includes: the number of video coding paths, and the coding format, resolution, frame rate, code rate and sending address of each path;
if the target resource module is an audio module, disaster recovery is carried out on the audio decoding information and the audio coding information to the specified resource module; wherein the audio decoding information includes: the number of audio decoding paths, and the decoding format, the number of sound channels and the receiving address of each path; the audio encoding information includes: the number of audio coding paths, and the coding format, the number of sound channels and the sending address of each path.
When the designated resource module does not belong to the local resource pool, the service take-over may fail by directly using the IP and the port of the target resource module on the designated resource module. Therefore, when the designated resource module does not belong to the local media resource, and when disaster recovery service data is generated, the IP address and the port of the disaster recovery data need to be removed, and the IP corresponding to the designated resource media is processed separately. The following describes in detail the process of disaster recovery service data of different resource pools, taking a video module and an audio module as examples:
if the target resource module is a video module, disaster recovery is carried out on video decoding information and video coding information to a specified resource module; wherein the video decoding information includes: the number of video decoding paths, and the decoding format, resolution, frame rate and code rate of each path; the video coding information includes: the number of video coding paths, and the coding format, resolution, frame rate and code rate of each path;
if the target resource module is an audio module, disaster recovery is carried out on the audio decoding information and the audio coding information to the specified resource module; wherein the audio decoding information includes: the number of audio decoding paths, and the decoding format and the number of sound channels of each path; the audio encoding information includes: the number of audio coding paths, and the coding format and the number of sound channels of each path. In particular, in order to enable the designated resource module to take over the media service of the target resource module of different operators, the corresponding device or service may also be notified in the service plane, and the IP and port of the service of the target resource module are changed to the IP and port corresponding to the designated resource module.
Preferably, to avoid dirty data or false response, after detecting that the target resource module is abnormal, the receiving and sending of the code stream of the target resource module may be stopped before performing response processing on the media service of the target resource module by using the specified resource module in combination with the service data.
S103, responding and processing the service of the target resource module by utilizing the resource pool management program of the specified resource module and combining the service data.
After the disaster recovery of the service data is completed, the service of the target resource module can be taken over by using the resource pool management program of the specified resource module and combining the service data.
Preferably, in practical applications, in the case of sufficient resources, a disaster recovery resource module (equivalent to the above specified resource module) may be preset for each resource module in the running state, and in the running process of the resource module, the step of step S102 is continuously performed, and once the resource module is detected to be abnormal, the corresponding disaster recovery resource module is directly started to take over the service, so as to further increase the service taking over speed.
Preferably, disaster recovery may be performed on the resource pool manager, so that when the resource pool manager is abnormal, other resource pool managers take over the service of the abnormal resource pool manager. The following description is made in a specific active/standby scenario with a resource pool management program corresponding to a media resource module:
wherein, the specific main and standby scenes are as follows: that is, there are two resource pool managers, one master and one slave, which then point to the same resource, which may be one or more. Under normal conditions, the resource module is controlled by the main resource pool program, and after the main resource pool program is abnormal, the standby resource pool program takes over and controls the resource module. In this process, since the ID of the master and the ID of the slave are identical to the external public IP address, the resource pool BB of the slave can receive the subsequent data operation (such as starting, stopping, increasing the code stream, decreasing the code stream, etc.) and continue to process the data operation.
For example, the resource pool management program is a media resource pool management program, and the media resource pool management program controls a media resource module, please refer to fig. 5, where a user is using the media resource module (the module is currently controlled by the management program — AA), and at this time, the AA is abnormal (such as program crash or power failure of the device in which the AA is located), and then the AA is taken over by another standby board program — BB. Although BB and AA programs (or operating environments) are different, the external identity ID and public IP address of the programs are the same (BB migrates the IP after sensing that the AA is abnormal), so that the situation that after the AA is switched to the BB, the message originally sent to the AA can be normally sent to the BB now can be ensured, namely the BB receives and processes the message originally needed to be sent to the AA. For example, if the hypervisor AA is abnormal, the user wants to use a new media resource module, the user only needs to operate normally, and the hypervisor BB executes the operation.
According to the method provided by the embodiment of the invention, after the abnormality of the target resource module is detected, the normal designated resource module is determined from the resource pool; disaster recovery of the service data of the target resource module to the specified resource module; and responding and processing the service of the target resource module by utilizing the resource pool management program of the specified resource module and combining the service data.
In the method, when the abnormality of the target resource module is detected, a normal specified resource module is determined from a resource pool, and then the service data of the target resource module is disaster-prepared to the specified resource module. The resource pool management program of the appointed resource module can respond to the service of the target resource module based on the service data, namely, the appointed resource module can manage the service of the target resource module. Therefore, when the target resource module is abnormal, the appointed resource module takes over the service without human intervention, the whole process can be automatically processed, the service interruption can be avoided, the corresponding service can be still provided after the target resource module is abnormal, and the user experience can be improved.
In order to better understand and apply the service disaster recovery method provided by the embodiment of the present invention, a specific application framework is described in detail below by taking application to cloud platform disaster recovery management as an example.
The service disaster recovery method provided by the embodiment of the present invention can be applied to disaster recovery management of a cloud platform (for example, the service disaster recovery method provided by the embodiment of the present invention can be executed by a management host (not shown in the figure) in a service disaster recovery framework shown in fig. 8, and a media resource pool management program can be an independent software or an embedded hardware device). Specifically, the cloud platform may include media deployment, media resource allocation, and service disaster recovery. The media deployment comprises registration of different media resource modules and resource reporting; the media resource allocation comprises an allocation policy of the resource; the service disaster recovery comprises the backup of a resource board on the same media resource, the backup between different media resource modules and the backup between media resource management programs.
The process of resource registration comprises the following steps: the media resource module sends a registration request to the resource pool management program by using a negotiated communication mode, and takes an ID for identifying the unique identity of the media resource module; after the successful registration, the smooth link is ensured between the media resource module and the resource pool management program in a mutual heartbeat probing manner; even if an abnormal chain breakage occurs, the media resource module initiatively initiates a new registration to the resource pool manager again.
The process of resource reporting comprises the following steps: the media resource module reports the resource types supported by the media resource module according to a unified communication structure, which operator environment the media resource module is in at present, and how many audio and video resources and the like are left at present; the reporting opportunity must be after registration is successful.
Referring to fig. 2, the resource allocation policy may specifically be: obtaining the operator type from the database according to the identity ID of the user or the accessed IP address, and then preferentially selecting a media resource module belonging to the same operator from all currently accessed media resources; if the media resource modules of the same operator are multiple, selecting a media resource module with a lower utilization rate according to the current cpu and memory load conditions of the media resource modules; if the media resource of the same operator is not found or the media resource of the same operator is used up, a media resource with lower utilization rate is continuously selected in other media resource pools according to the CPU and the memory load condition. One media resource module is a chip running a certain media service, or a chip group formed by a plurality of chips.
Corresponding to the above method embodiment, an embodiment of the present invention further provides a service disaster recovery device, and a service disaster recovery device described below and a service disaster recovery method described above may be referred to correspondingly.
Referring to fig. 6, the service disaster recovery device includes:
a memory D1 for storing a computer program;
a processor D2, configured to implement the steps of the service disaster recovery method of the foregoing method embodiment when executing the computer program.
Specifically, please refer to fig. 7, which is a schematic structural diagram of a service disaster recovery device provided in this embodiment, the service disaster recovery device may generate a relatively large difference due to different configurations or performances, and may include one or more processors (CPUs) 322 (e.g., one or more processors), a memory 332, and one or more storage media 330 (e.g., one or more mass storage devices) for storing an application 342 or data 344. Memory 332 and storage media 330 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 330 may include one or more modules (not shown), each of which may include a series of instructions operating on a data processing device. Further, the central processor 322 may be configured to communicate with the storage medium 330, and execute a series of instruction operations in the storage medium 330 on the service disaster recovery device 301.
The disaster recovery device 301 may also include one or more power sources 326, one or more wired or wireless network interfaces 350, one or more input-output interfaces 358, and/or one or more operating systems 341. For example, windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, etc.
The steps in the service disaster recovery method described above can be implemented by the structure of the service disaster recovery device.
Corresponding to the above method embodiment, the embodiment of the present invention further provides a readable storage medium, and a readable storage medium described below and a service disaster recovery method described above may be referred to correspondingly.
A readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the steps of the service disaster recovery method of the above-mentioned method embodiments.
The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, an optical disk, or other various readable storage media capable of storing program codes.
Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the technical solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
Claims (7)
1. A service disaster recovery method is characterized by comprising the following steps:
the method comprises the steps that registration and resource report of resource modules corresponding to resource pools corresponding to different operators are received by using a communication structure with the same standard;
running a resource pool management program and each resource module to detect the link connection state through heartbeat signals, if abnormal link breakage occurs, confirming that the resource module is an abnormal target resource module, and receiving re-registration of the target resource module;
after the target resource module is detected to be abnormal, determining a normal appointed resource module from a resource pool; the target resource module and the appointed resource module are hardware resource modules consisting of hardware components, and the specific type of the appointed resource module corresponds to the specific type of the target resource module;
disaster recovery is carried out on the service data of the target resource module to the specified resource module; the service data refers to relevant data required by the service supported by the target resource module;
utilizing a resource pool management program of the appointed resource module and combining the service data to respond and process the service of the target resource module;
wherein, the determining the normal appointed resource module from the resource pool comprises: judging whether available resources exist in a local resource pool to which the target resource module belongs; if yes, selecting or creating the specified resource module in the local resource pool; if not, selecting or creating the appointed resource module from a resource pool to which the target resource module does not belong;
selecting or creating the specified resource module in the local resource pool, including: if the optional resource module exists in the local resource pool, determining the appointed resource module in the optional resource module; if the optional resource module is not in the local resource pool, creating the appointed resource module in the local resource pool;
when the specified resource module belongs to the local resource pool, disaster-backing the service data of the target resource module to the specified resource module, specifically: adopting a port and an IP which are the same as the target resource module and provide services to the outside to disaster-prepare the service data of the target resource module to the specified resource module;
when the specified resource module does not belong to the local resource pool, disaster recovery of the service data of the target resource module is performed on the specified resource module, specifically: and eliminating the port and the IP of the target resource module for providing service to the outside, independently processing the IP corresponding to the specified resource module, and disaster-backing the service data of the target resource module to the specified resource module.
2. The service disaster recovery method of claim 1, wherein determining the designated resource module among the selectable resource modules comprises:
acquiring the resource utilization rate of each selectable resource module;
and taking the selectable resource module with the lowest resource utilization rate as the specified resource module.
3. The service disaster recovery method according to claim 1, wherein the specified resource module belongs to the local resource pool, and the disaster recovery of the service data of the target resource module to the specified resource module comprises:
if the target resource module is a video module, disaster recovery is carried out on video decoding information and video coding information to the specified resource module; wherein the video decoding information comprises: the number of video decoding paths, and the decoding format, resolution, frame rate, code rate and receiving address of each path; the video coding information includes: the number of video coding paths, and the coding format, resolution, frame rate, code rate and sending address of each path;
if the target resource module is an audio module, disaster recovery is carried out on audio decoding information and audio coding information to the specified resource module; wherein the audio decoding information includes: the number of audio decoding paths, the decoding format, the number of sound channels and the receiving address of each path; the audio coding information includes: the number of audio coding paths, and the coding format, the number of sound channels and the sending address of each path.
4. The service disaster recovery method according to claim 1, wherein the designated resource module does not belong to the local resource pool, and the disaster recovery of the service data of the target resource module to the designated resource module comprises:
if the target resource module is a video module, disaster recovery is carried out on video decoding information and video coding information to the specified resource module; wherein the video decoding information includes: the number of video decoding paths, and the decoding format, resolution, frame rate and code rate of each path; the video coding information includes: the number of video coding paths, and the coding format, resolution, frame rate and code rate of each path;
if the target resource module is an audio module, disaster recovery is carried out on audio decoding information and audio coding information to the specified resource module; wherein the audio decoding information includes: the number of audio decoding paths, and the decoding format and the number of sound channels of each path; the audio encoding information includes: the number of audio coding paths, and the coding format and the number of sound channels of each path.
5. The service disaster recovery method according to claim 1, wherein after detecting an abnormality of a target resource module, before performing response processing on a media service of the target resource module by using the specified resource module in combination with the service data, the method comprises:
and stopping receiving and transmitting the code stream of the target resource module.
6. A service disaster recovery device, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the service disaster recovery method according to any one of claims 1 to 5 when executing the computer program.
7. A readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the service disaster recovery method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010244923.7A CN111355988B (en) | 2020-03-31 | 2020-03-31 | Business disaster recovery method, equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010244923.7A CN111355988B (en) | 2020-03-31 | 2020-03-31 | Business disaster recovery method, equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111355988A CN111355988A (en) | 2020-06-30 |
| CN111355988B true CN111355988B (en) | 2022-11-11 |
Family
ID=71197597
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010244923.7A Active CN111355988B (en) | 2020-03-31 | 2020-03-31 | Business disaster recovery method, equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111355988B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101799776A (en) * | 2010-02-25 | 2010-08-11 | 上海华为技术有限公司 | Fault processing method of multi-core processor, multi-core processor and communication device |
| CN102325192A (en) * | 2011-09-30 | 2012-01-18 | 上海宝信软件股份有限公司 | Cloud computing implementation method and system |
| CN110333930A (en) * | 2019-04-29 | 2019-10-15 | 中国联合网络通信集团有限公司 | Digital Platform system |
Family Cites Families (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101072417B (en) * | 2006-05-09 | 2010-12-08 | 中兴通讯股份有限公司 | Device and method for realizing A interface flexible configuration for second-generation CDMA system |
| CN101930284B (en) * | 2009-06-23 | 2014-04-09 | 腾讯科技（深圳）有限公司 | Method, device and system for implementing interaction between video and virtual network scene |
| JP2011170680A (en) * | 2010-02-19 | 2011-09-01 | Nec Corp | Fault tolerant server |
| CN103580883B (en) * | 2012-07-19 | 2018-09-11 | 南京中兴软件有限责任公司 | A kind of business disaster recovery method and system |
| CN104144070B (en) * | 2013-05-10 | 2018-04-10 | 中国电信股份有限公司 | Cloud call center system and its dynamic disaster recovery method, kernel scheduling equipment |
| US10116514B1 (en) * | 2015-03-30 | 2018-10-30 | Amdocs Development Limited | System, method and computer program for deploying an orchestration layer for a network based on network function virtualization (NFV) |
| CN103973478A (en) * | 2014-01-28 | 2014-08-06 | 国网信通亿力科技有限责任公司 | Disaster preparation system and disaster preparation method for power grid information based on resource pool technology |
| CN104158693B (en) * | 2014-08-27 | 2018-04-13 | 乐视网信息技术（北京）股份有限公司 | The disaster-tolerant backup method and system of data service |
| CA2901223C (en) * | 2014-11-17 | 2017-10-17 | Jiongjiong Gu | Method for migrating service of data center, apparatus, and system |
| CN105302792B (en) * | 2015-07-29 | 2017-12-26 | 国网山东省电力公司电力科学研究院 | A kind of voice platform framework method of adjustment |
| CN109274537B (en) * | 2018-10-25 | 2022-12-27 | 深圳供电局有限公司 | Continuous network virtualization platform system |
| CN109714190A (en) * | 2018-11-28 | 2019-05-03 | 四川商通实业有限公司 | A kind of load balancing based on application level and failure transfer system and its method |
| CN110795280A (en) * | 2019-09-11 | 2020-02-14 | 杭州衣科信息技术有限公司 | Remote double-activity disaster recovery system based on mysql asynchronous and bidirectional |
-
2020
- 2020-03-31 CN CN202010244923.7A patent/CN111355988B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101799776A (en) * | 2010-02-25 | 2010-08-11 | 上海华为技术有限公司 | Fault processing method of multi-core processor, multi-core processor and communication device |
| CN102325192A (en) * | 2011-09-30 | 2012-01-18 | 上海宝信软件股份有限公司 | Cloud computing implementation method and system |
| CN110333930A (en) * | 2019-04-29 | 2019-10-15 | 中国联合网络通信集团有限公司 | Digital Platform system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111355988A (en) | 2020-06-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109729143B (en) | Deploying a network-based cloud platform on a terminal device | |
| US10838890B2 (en) | Acceleration resource processing method and apparatus, and network functions virtualization system | |
| US9037899B2 (en) | Automated node fencing integrated within a quorum service of a cluster infrastructure | |
| US20170373931A1 (en) | Method for updating network service descriptor nsd and apparatus | |
| WO2016022405A1 (en) | Providing higher workload resiliency in clustered systems based on health heuristics | |
| JP2006114040A (en) | Failover scope for node of computer cluster | |
| CN110764963B (en) | Service exception handling method, device and equipment | |
| CN109802986B (en) | Equipment management method, system, device and server | |
| CN109542659A (en) | Using more activating methods, equipment, data center's cluster and readable storage medium storing program for executing | |
| US10120779B1 (en) | Debugging of hosted computer programs | |
| US20090164565A1 (en) | Redundant systems management frameworks for network environments | |
| CN111459749A (en) | Prometous-based private cloud monitoring method and device, computer equipment and storage medium | |
| CN111708560A (en) | Automatic deployment method and device of database high-availability management system | |
| CN111858007A (en) | Task scheduling method and device based on message middleware | |
| CN112398689A (en) | Network recovery method and device, storage medium and electronic equipment | |
| CN113852506A (en) | Fault processing method and device, electronic equipment and storage medium | |
| US7260596B1 (en) | Distributed service provider | |
| CN112698992B (en) | Disaster recovery management method and related device for cloud cluster | |
| CN111355988B (en) | Business disaster recovery method, equipment and readable storage medium | |
| CN113489601A (en) | Anti-destruction method and device based on video networking autonomous cloud network architecture | |
| CN112416594A (en) | Micro-service distribution method, electronic equipment and computer storage medium | |
| KR101883671B1 (en) | Method and management server for dtitributing node | |
| CN111414247A (en) | Server switching method, device, management node and storage medium | |
| CN106453118B (en) | Flow control method and flow control system | |
| CN113190347A (en) | Edge cloud system and task management method |
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 |