DHBS (dual hot-backup system) and method thereof based on SOA (service-oriented architecture) and cloud storage

Abstract

The invention discloses a DHBS based on SOA and cloud storage, which is characterized in that the framework of the DHBS is based on an SOA model. The DHBS comprises a console system serving as a cloud service terminal, and at least one substation monitoring system serving as a client, wherein the console system is in data connection with the substation monitoring system; the console system comprises at least one cloud storage service terminal and a data memory; the substation monitoring system comprises a host, a slave and lower intelligent monitoring equipment; the host and the slave are connected with the lower computer monitoring equipment through a bus; each of the host and the slave is provided with a data memory; and the host and the slave are in data connection with the cloud storage service terminal. The DHBS and the method thereof based on SOA and cloud storage avoid the risk problem of single point of failure when using a disk array, overcome the defects of weak real-time data replication and complicated synchronized data recovery between servers in common software hot backup, improve the whole switching time to millisecond level which only spends 50 ms-100 ms.

Description

technical field [0001] The invention relates to a dual-computer hot backup system and a dual-machine hot backup method realized based on SOA and cloud storage. Background technique [0002] At present, there are two main forms of dual-machine hot backup: one is the hardware level, and the other is the software level. [0003] The standard solution for general hardware-level dual-machine hot backup is based on storage sharing. For this approach, two servers are used and shared storage devices (disk array cabinets or storage area network SAN) are used. During the working process, the two servers will provide external services with a virtual IP address, and the service request will be sent to one of the servers according to the different working methods. [0004] For this solution, there are the following problems: [0005] 1. Increased investment in expensive storage equipment. [0006] 2. There is a risk of a single point of failure. If the host fails, it can still be swi...

AI Technical Summary

Problems solved by technology

[0005]1. Increased investment in expensive storage equipment

[0006]2. There is a risk of a single point of failure. If the host fails, it can still be switched over to take over, but the actual risk is transferred from the host to the shared disk. Once the disk array fails, it will cause The whole system cannot work, and more seriously, data will be lost

[0007]3. Point-in-time recovery is not possible, and data deleted by the host will be deleted from the disk array, and the data cannot be recovered

[0008]4. One of them is in backup state for a long time, wasting resources

[0013]3. There is no transaction mechanism, because the replication is carried out at the file and disk layer, whether the replication is successful or not will not affect the database transaction operation, so there may be incomplete data changes In this case, there is a considerable risk

[0014]4. The slave machine is in the backup state for a long time, wasting resources

Images