CN111211930A - Block chain service disaster-tolerant backup containerized deployment method - Google Patents
Block chain service disaster-tolerant backup containerized deployment method Download PDFInfo
- Publication number
- CN111211930A CN111211930A CN201911426170.5A CN201911426170A CN111211930A CN 111211930 A CN111211930 A CN 111211930A CN 201911426170 A CN201911426170 A CN 201911426170A CN 111211930 A CN111211930 A CN 111211930A
- Authority
- CN
- China
- Prior art keywords
- block chain
- service
- cluster
- baas
- kubernets
- 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.)
- Granted
Links
Images
Classifications
-
- 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/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
- G06F16/1824—Distributed file systems implemented using Network-attached Storage [NAS] architecture
- G06F16/183—Provision of network file services by network file servers, e.g. by using NFS, CIFS
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Abstract
The invention discloses a block chain service disaster recovery backup containerized deployment method. The method comprises the following steps: two sets of kubernets cluster environments are built, and ingress-controllers are deployed respectively; the master-slave copy of the database of the block chain BaaS service in the two clusters keeps consistency; deploying NAS network storage services; calling a kubernets client to deploy a block chain through the BaaS service of one cluster, and defining that each block chain link corresponds to one service and one pod; mapping the data disk of each block chain node pod to the NAS storage through the PVC binding PV; when the service of one cluster is abnormal, the block chain service can be quickly recovered in another cluster. The invention realizes the deployment and management of the operation and maintenance block chain on kubernets by the block chain BaaS service, solves the problems that the BaaS cannot provide the service and the data of the block chain link points with the state deployed on the kubernets is lost when one cluster environment is subjected to an unexpected disaster, and effectively improves the disaster tolerance capability of the block chain service.
Description
Technical Field
The invention relates to a block chain technology and a container technology, in particular to a method for block chain service remote disaster recovery backup and service migration based on kubernets deployment.
Background
The blockchain is a novel decentralized distributed account book technology, digital currency transactions or other data can be safely stored, and the blockchain is characterized in that information stored on the blockchain cannot be forged and tampered, a blockchain consensus algorithm drives each node on the blockchain to participate in a transaction verification process, the transactions on the blockchain are guaranteed to be credible, each node on the blockchain maintains a public account book for storing balance and intelligent contract data of all users on a blockchain network, and any node does not allow the modification of the account book maintained by the node to be acknowledged by other nodes, so that the public account book cannot be forged and tampered.
The container is a lightweight operating system level virtualization, and can enable an application and a dependent item thereof to run in a resource isolation process. The components necessary to run the application will be packaged as a mirror image and can be reused. When the mirror image is executed, the mirror image runs in an isolation environment and does not share the memory, the CPU and the disk of the host machine, so that the condition that the process in the container cannot monitor any process outside the container is ensured.
The blockchain technology is a very popular emerging technology, and due to the characteristics of decentralization and non-falsification of blockchains, in a traditional deployment mode, when a blockchain service of one environment is abnormal and needs to be migrated to another environment for providing service, the migration of the blockchain environment can cause some configuration parameters of a common node to be changed so as to normally operate.
Disclosure of Invention
The invention aims to provide a method for block chain service remote disaster recovery backup and service migration based on kubernets deployment aiming at pain points of the existing block chain service which are difficult to migrate for backup, and can help the block chain service to conveniently and rapidly backup disaster recovery and service migration.
The purpose of the invention is realized by the following technical scheme: a block chain service disaster recovery backup containerized deployment method comprises the following steps:
1) building two sets of kubernets cluster environments of A (main) and B (standby);
2) respectively deploying ingress-controllers in A, B environments, wherein applications in the two clusters can communicate by exposing IP ports to each other through the ingress;
3) respectively deploying block chain BaaS service components in A, B two clusters, wherein A, B database storage related services of BaaS in the two clusters establish a master-slave copy relationship through an ingress tcp four-layer agent, and database data consistency of block chain BaaS service is guaranteed;
4) deploying NAS network storage services;
5) calling a kubernets client to deploy a block chain through a block chain BaaS service of the A cluster, defining that each block chain link corresponds to one service and corresponds to one pod, and recording the service and related data corresponding to each node by a BaaS database;
6) mapping the data disk of each block chain node pod to the NAS storage deployed in the step 4) through PVC binding PV, and recording mounting information of a relevant volume by a BaaS service database;
7) when sensing abnormal service state of the A cluster block chain, the B cluster can initiate a block chain migration function in the BaaS service in the B cluster, the B cluster rebuilds the block chain in the B cluster through the block chain link data information in the database common to the two clusters, and mounts the block chain link data to the common NAS persistent storage service, so that the block chain account data is not lost.
Further, in step 1), the A, B two kubernets cluster may be two isolated cluster environments, or two cluster environments located in different rooms at different locations.
Further, the A, B two kubernets cluster in step 2) may expose related services to each other through proxy for communication.
Further, in the step 3), block chain BaaS services are deployed in A, B two clusters respectively, wherein A, B database storage related services of BaaS in the two clusters establish a master-slave copy relationship through an ingress tcp four-layer agent, so that consistency of operation and maintenance data of a block chain and a block chain link point in a block chain BaaS platform in the two clusters is ensured.
Further, in step 4), both clusters use the same NAS persistent storage, where persistent data of the blockchain node deployed in the cluster a can also be accessed in the cluster B.
Further, each node of the block chain deployed by the BaaS service on kubernets in step 5) corresponds to a service and a pod resource, the data corresponding to the resource is recorded in a database of the block chain BaaS service, and the block chain nodes access and communicate with each other through a service name.
Further, the data of the block chain node in the step 6) is mounted in the NAS file system, and A, B is accessible to both clusters.
The invention has the beneficial effects that: according to the invention, the block chain service platform and the components are respectively arranged in two sets of kubernets cluster environments in a containerized manner, the master-slave copy of the databases of the block chain BaaS service in the two clusters keeps consistency, the block chain link point persistence data arranged in one cluster by the block chain service platform is externally hung in a distributed file system, and when the service of one cluster is abnormal, the block chain service can be quickly recovered in the other cluster. For traditional cloud server and physical server deployment, the deployment mode is adopted to reduce the dependence of the service on environmental hardware and an operating system, and the cluster deployment in a machine room in different places has the characteristics of resisting block chain service abnormity caused by accidents such as power failure, network failure and the like, and has the characteristics of multiple activities in different places and disaster recovery backup.
Drawings
Fig. 1 is a diagram of a two kubernets cluster blockchain service architecture.
Detailed Description
The present invention will be described in detail below with reference to the drawings and specific embodiments, and the objects and effects of the present invention will become more apparent.
As shown in fig. 1, a block chain service disaster recovery backup containerization deployment method provided by the present invention includes:
1) building two sets of kubernets cluster environments of A (main) and B (standby);
2) respectively deploying ingress-controllers in A, B environments, wherein applications in the two clusters can communicate by exposing IP ports to each other through the ingress;
3) respectively deploying block chain BaaS service components in A, B two clusters, wherein A, B database storage related services of BaaS in the two clusters establish a master-slave copy relationship through an ingress tcp four-layer agent, and database data consistency of block chain BaaS service is guaranteed;
4) deploying NAS network storage services;
5) calling a kubernets client to deploy a block chain through a block chain BaaS service of the A cluster, defining that each block chain link corresponds to one service and one pod, and recording the service and related data corresponding to each node by a BaaS database;
6) mapping the data disk of each block chain node pod to the NAS storage deployed in the step 4) through PVC binding PV, and recording mounting information of a relevant volume by a BaaS service database;
7) when sensing abnormal service state of the A cluster block chain, the B cluster can initiate a block chain migration function in the BaaS service in the B cluster, reestablishing the block chain in the B cluster through the block chain link data information in a database common to the two clusters and mounting the block chain link data to a common NAS persistent storage service, so that the block chain account data is not lost;
further, in step 1), the A, B two kubernets cluster may be two isolated cluster environments, or two cluster environments located in different rooms at different locations.
Further, the A, B two kubernets cluster in step 2) may expose related services to each other through proxy for communication.
Further, in the step 3), block chain BaaS services are deployed in A, B two clusters respectively, wherein A, B database storage related services of BaaS in the two clusters establish a master-slave copy relationship through an ingress tcp four-layer agent, so that consistency of operation and maintenance data of a block chain and a block chain link point in a block chain BaaS platform in the two clusters is ensured.
Further, in step 4), both clusters use the same NAS persistent storage, where persistent data of the blockchain node deployed in the cluster a can also be accessed in the cluster B.
Further, each node of the block chain deployed by the BaaS service on kubernets in step 5) corresponds to a service and a pod resource, the data corresponding to the resource is recorded in a database of the block chain BaaS service, and the block chain nodes access and communicate with each other through a service name.
Further, the data of the block chain node in the step 6) is mounted in the NAS file system, and A, B is accessible to both clusters.
The following describes embodiments using a particular blockchain service cross-cluster migration example:
simulating the migration process of a blockchain service across kubernets cluster, as shown in fig. 1, the input of the steps is two: firstly, deleting deployment, pods and service resources of block chains in kubernets in the cluster A; and secondly, after the BaaS service in the B cluster detects the BaaS service abnormality of the A cluster, initiating block chain migration operation.
And B, reading the migrated block chain and block chain link point information from the database by the BaaS service in the cluster B, constructing deployment, posts and service, reading the mounting volume information, binding the mounting volume information to the previous data volume, starting the block chain, and recovering the block chain to serve the outside.
The foregoing is only a preferred embodiment of the present invention, and although the present invention has been disclosed in the preferred embodiments, it is not intended to limit the present invention. Those skilled in the art can make numerous possible variations and modifications to the present teachings, or modify equivalent embodiments to equivalent variations, without departing from the scope of the present teachings, using the methods and techniques disclosed above. Therefore, any simple modification, equivalent change and modification made to the above embodiments according to the technical essence of the present invention are still within the scope of the protection of the technical solution of the present invention, unless the contents of the technical solution of the present invention are departed.
Claims (8)
1. A block chain service disaster recovery backup containerized deployment method is characterized by comprising the following steps:
1) building two sets of kubernets cluster environments of A (main) and B (standby);
2) respectively deploying ingress-controllers in A, B two environments, and exposing services to each other by the two clusters through the ingress;
3) respectively deploying block chain BaaS services in A, B two clusters, wherein A, B database storage related services of the BaaS in the two clusters establish a master-slave copy relationship through an ingress tcp four-layer agent;
4) deploying NAS network storage services;
5) calling a kubernets client to deploy a block chain through the BaaS service of the A cluster, defining that each block chain link corresponds to one service and one pod, and recording the service and related data corresponding to each node by a BaaS database;
6) mapping the data disk of each block chain node pod to the NAS storage deployed in the step 4) through PVC binding PV, and recording mounting information of a relevant volume by a BaaS service database;
7) when the cluster B senses that the cluster A is abnormal in state and cannot provide services to the outside, the BaaS service in the cluster B can initiate a block chain migration function to migrate the block chain in the A kubernets to the B kubernets.
2. The method as claimed in claim 1, wherein A, B two kubernets cluster in step 1) can be two isolated cluster environments, or two cluster environments located in different rooms at different locations.
3. The method as claimed in claim 1, wherein A, B two kubernets clusters in step 2) can communicate with each other by exposing related services through ingress agents.
4. The method as claimed in claim 1, wherein the database data accessed by the BaaS services located in A, B two clusters in step 3) are consistent.
5. The method as claimed in claim 1, wherein in step 4), both clusters are stored in the same NAS network.
6. The method as claimed in claim 1, wherein each node of the blockchain deployed by the BaaS service on kubernets in step 5) corresponds to a service and a pod, and the nodes access and communicate with each other through a service name.
7. The method according to claim 1, wherein the data of the blockchain node in step 6) is mounted in the NAS file system, and A, B is accessible to both clusters.
8. The method as claimed in claim 1, wherein in step 7), when the B cluster senses that the a cluster is in an abnormal state and cannot provide a service to the outside, the BaaS service in the B cluster may initiate a block chain migration function to migrate the block chain in a kubernets to B kubernets, and since the database records service related information bound to block chain link points, the block chain service may be rapidly restored on the B kubernets cluster, and the block chain nodes in the B cluster may perform communication consensus through the same service name.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911426170.5A CN111211930B (en) | 2019-12-31 | 2019-12-31 | Block chain service disaster-tolerant backup containerized deployment method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911426170.5A CN111211930B (en) | 2019-12-31 | 2019-12-31 | Block chain service disaster-tolerant backup containerized deployment method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111211930A true CN111211930A (en) | 2020-05-29 |
| CN111211930B CN111211930B (en) | 2022-08-26 |
Family
ID=70787893
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911426170.5A Active CN111211930B (en) | 2019-12-31 | 2019-12-31 | Block chain service disaster-tolerant backup containerized deployment method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111211930B (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708659A (en) * | 2020-06-10 | 2020-09-25 | 中国—东盟信息港股份有限公司 | Method for constructing cloud native disaster tolerance architecture based on kubernets |
| CN111752759A (en) * | 2020-06-30 | 2020-10-09 | 重庆紫光华山智安科技有限公司 | Kafka cluster fault recovery method, device, equipment and medium |
| CN112000516A (en) * | 2020-08-12 | 2020-11-27 | 上海英方软件股份有限公司 | NAS quasi-real-time backup system and method |
| CN112015517A (en) * | 2020-08-05 | 2020-12-01 | 北京链飞未来科技有限公司 | Dynamic migration method and system for block link points based on k8s cluster |
| CN112667348A (en) * | 2020-12-19 | 2021-04-16 | 前海飞算科技(深圳)有限公司 | MySQL containerization method and system and computer equipment |
| CN113032105A (en) * | 2021-04-20 | 2021-06-25 | 金蝶软件（中国）有限公司 | Kubernetes cluster access control method, system and related equipment |
| CN113391952A (en) * | 2021-06-07 | 2021-09-14 | 北京同创永益科技发展有限公司 | Automatic backup method based on LVM snapshot in cloud native environment |
| CN113407384A (en) * | 2021-07-05 | 2021-09-17 | 杭州趣链科技有限公司 | Method and device for transmitting peer node instruction, proxy server and storage medium |
| CN113590265A (en) * | 2021-08-02 | 2021-11-02 | 杭州云象网络技术有限公司 | Method, medium, device and system for migrating alliance chain cluster environment |
| CN113821381A (en) * | 2021-11-18 | 2021-12-21 | 深圳电通信息技术有限公司 | Block chain node resource backup and off-line node resource transfer method and storage medium |
| CN114301972A (en) * | 2021-12-17 | 2022-04-08 | 杭州谐云科技有限公司 | Block chain link point hierarchical deployment method and system based on cloud edge cooperation |
| CN114465873A (en) * | 2022-01-21 | 2022-05-10 | 无锡软美信息科技有限公司 | Method and storage medium for blockchain exception node discovery and repair |
| CN114679467A (en) * | 2022-03-23 | 2022-06-28 | 中国联合网络通信集团有限公司 | Multi-block chain cooperative service method, block chain service system and cooperative service system |
| CN116489224A (en) * | 2023-06-19 | 2023-07-25 | 中国联合网络通信集团有限公司 | Multi-cloud container scheduling method, device, equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776126A (en) * | 2016-11-30 | 2017-05-31 | 郑州云海信息技术有限公司 | A kind of disaster tolerance system and method |
| CN108512935A (en) * | 2018-04-16 | 2018-09-07 | 腾讯科技（深圳）有限公司 | data service system, method, server and computer readable storage medium |
| CN109344000A (en) * | 2018-08-16 | 2019-02-15 | 北京京东尚科信息技术有限公司 | Block chain network service platform restores tool and its fault handling method, storage medium |
| CN109472617A (en) * | 2018-09-25 | 2019-03-15 | 仲恺农业工程学院 | Distribution of Aquatic Products tracing system and method based on block chain |
| US20190318338A1 (en) * | 2018-04-13 | 2019-10-17 | International Business Machines Corporation | Network node management on a blockchain |
| CN110377459A (en) * | 2019-06-28 | 2019-10-25 | 苏州浪潮智能科技有限公司 | A kind of disaster tolerance system, disaster tolerance processing method, monitoring node and backup cluster |
| CN110417896A (en) * | 2019-07-31 | 2019-11-05 | 中国工商银行股份有限公司 | The system and method for block chain dynamic group net based on cloud |
| CN110569670A (en) * | 2019-09-17 | 2019-12-13 | 上海保险交易所股份有限公司 | Encryption and design method of enterprise annuity based on block chain |
-
2019
- 2019-12-31 CN CN201911426170.5A patent/CN111211930B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106776126A (en) * | 2016-11-30 | 2017-05-31 | 郑州云海信息技术有限公司 | A kind of disaster tolerance system and method |
| US20190318338A1 (en) * | 2018-04-13 | 2019-10-17 | International Business Machines Corporation | Network node management on a blockchain |
| CN108512935A (en) * | 2018-04-16 | 2018-09-07 | 腾讯科技（深圳）有限公司 | data service system, method, server and computer readable storage medium |
| CN109344000A (en) * | 2018-08-16 | 2019-02-15 | 北京京东尚科信息技术有限公司 | Block chain network service platform restores tool and its fault handling method, storage medium |
| CN109472617A (en) * | 2018-09-25 | 2019-03-15 | 仲恺农业工程学院 | Distribution of Aquatic Products tracing system and method based on block chain |
| CN110377459A (en) * | 2019-06-28 | 2019-10-25 | 苏州浪潮智能科技有限公司 | A kind of disaster tolerance system, disaster tolerance processing method, monitoring node and backup cluster |
| CN110417896A (en) * | 2019-07-31 | 2019-11-05 | 中国工商银行股份有限公司 | The system and method for block chain dynamic group net based on cloud |
| CN110569670A (en) * | 2019-09-17 | 2019-12-13 | 上海保险交易所股份有限公司 | Encryption and design method of enterprise annuity based on block chain |
Non-Patent Citations (2)
| Title |
|---|
| 王健等: "基于区块链和连续双向拍卖机制的微电网直接交易模式及策略", 《中国电机工程学报》 * |
| 王海庆等: "基于K3s的边缘计算在泛在电力物联网的技术研究", 《科技资讯》 * |
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708659A (en) * | 2020-06-10 | 2020-09-25 | 中国—东盟信息港股份有限公司 | Method for constructing cloud native disaster tolerance architecture based on kubernets |
| CN111752759B (en) * | 2020-06-30 | 2022-07-08 | 重庆紫光华山智安科技有限公司 | Kafka cluster fault recovery method, device, equipment and medium |
| CN111752759A (en) * | 2020-06-30 | 2020-10-09 | 重庆紫光华山智安科技有限公司 | Kafka cluster fault recovery method, device, equipment and medium |
| CN112015517A (en) * | 2020-08-05 | 2020-12-01 | 北京链飞未来科技有限公司 | Dynamic migration method and system for block link points based on k8s cluster |
| CN112015517B (en) * | 2020-08-05 | 2024-03-29 | 北京链飞未来科技有限公司 | Block chain node dynamic migration method and system based on k8s cluster |
| CN112000516A (en) * | 2020-08-12 | 2020-11-27 | 上海英方软件股份有限公司 | NAS quasi-real-time backup system and method |
| CN112000516B (en) * | 2020-08-12 | 2023-03-24 | 上海英方软件股份有限公司 | NAS quasi-real-time backup system and method |
| CN112667348A (en) * | 2020-12-19 | 2021-04-16 | 前海飞算科技(深圳)有限公司 | MySQL containerization method and system and computer equipment |
| CN112667348B (en) * | 2020-12-19 | 2021-10-29 | 飞算数智科技(深圳)有限公司 | MySQL containerization method and system and computer equipment |
| CN113032105A (en) * | 2021-04-20 | 2021-06-25 | 金蝶软件（中国）有限公司 | Kubernetes cluster access control method, system and related equipment |
| CN113032105B (en) * | 2021-04-20 | 2023-11-17 | 金蝶软件（中国）有限公司 | Kubernetes cluster access control method, system and related equipment |
| CN113391952A (en) * | 2021-06-07 | 2021-09-14 | 北京同创永益科技发展有限公司 | Automatic backup method based on LVM snapshot in cloud native environment |
| CN113407384B (en) * | 2021-07-05 | 2022-04-12 | 杭州趣链科技有限公司 | Method and device for transmitting peer node instruction, proxy server and storage medium |
| CN113407384A (en) * | 2021-07-05 | 2021-09-17 | 杭州趣链科技有限公司 | Method and device for transmitting peer node instruction, proxy server and storage medium |
| CN113590265A (en) * | 2021-08-02 | 2021-11-02 | 杭州云象网络技术有限公司 | Method, medium, device and system for migrating alliance chain cluster environment |
| CN113821381A (en) * | 2021-11-18 | 2021-12-21 | 深圳电通信息技术有限公司 | Block chain node resource backup and off-line node resource transfer method and storage medium |
| CN113821381B (en) * | 2021-11-18 | 2022-07-08 | 深圳电通信息技术有限公司 | Block chain node resource backup and off-line node resource transfer method and storage medium |
| CN114301972A (en) * | 2021-12-17 | 2022-04-08 | 杭州谐云科技有限公司 | Block chain link point hierarchical deployment method and system based on cloud edge cooperation |
| CN114465873A (en) * | 2022-01-21 | 2022-05-10 | 无锡软美信息科技有限公司 | Method and storage medium for blockchain exception node discovery and repair |
| CN114465873B (en) * | 2022-01-21 | 2023-09-01 | 无锡软美信息科技有限公司 | Method and storage medium for blockchain exception node discovery and repair |
| CN114679467A (en) * | 2022-03-23 | 2022-06-28 | 中国联合网络通信集团有限公司 | Multi-block chain cooperative service method, block chain service system and cooperative service system |
| CN116489224B (en) * | 2023-06-19 | 2023-08-22 | 中国联合网络通信集团有限公司 | Multi-cloud container scheduling method, device, equipment and storage medium |
| CN116489224A (en) * | 2023-06-19 | 2023-07-25 | 中国联合网络通信集团有限公司 | Multi-cloud container scheduling method, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111211930B (en) | 2022-08-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111211930B (en) | Block chain service disaster-tolerant backup containerized deployment method | |
| US9747179B2 (en) | Data management agent for selective storage re-caching | |
| US20220326886A1 (en) | Distributed data storage techniques for edge devices | |
| US8055937B2 (en) | High availability and disaster recovery using virtualization | |
| CN107391758B (en) | Database switching method, device and equipment | |
| US8539087B2 (en) | System and method to define, visualize and manage a composite service group in a high-availability disaster recovery environment | |
| CN111555913A (en) | Simulation method, system, electronic device and storage medium for simulating real network environment based on virtualization | |
| EP3513296B1 (en) | Hierarchical fault tolerance in system storage | |
| US7702757B2 (en) | Method, apparatus and program storage device for providing control to a networked storage architecture | |
| JP2007511008A (en) | Hybrid real-time data replication | |
| CN103368767A (en) | Method and system for efficient application management in a cloud with failures | |
| CN108259175A (en) | A kind of distribution routing algorithm method of servicing and system | |
| CN111597197B (en) | Data reconciliation method and device between databases, storage medium and electronic equipment | |
| CN112214351A (en) | Backup data recovery method and device, electronic equipment and storage medium | |
| CN112311646B (en) | Hybrid cloud based on super-fusion system and deployment method | |
| CN111949444A (en) | Data backup and recovery system and method based on distributed service cluster | |
| CN112698992A (en) | Disaster recovery management method and related device for cloud cluster | |
| CN109189327A (en) | The compression processing method and device of block chain data | |
| CN110705712A (en) | Artificial intelligence basic resource and technology open platform for third-party social service | |
| CN106095618A (en) | The method and system of data manipulation | |
| Riabko et al. | Cluster fault tolerance model with migration of virtual machines | |
| CN116016028B (en) | Method, system, medium and equipment for creating multiple network interfaces for Pod based on IPvlan | |
| CN116389233A (en) | Container cloud management platform active-standby switching system, method and device and computer equipment | |
| EP3884648B1 (en) | Geo-replicated iot hub | |
| CN113010600B (en) | Data management system, method, related device and medium based on block chain |
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 |