CN104660386A - DB2 disaster recovery high-availability improving method based on Itanium platform - Google Patents
DB2 disaster recovery high-availability improving method based on Itanium platform Download PDFInfo
- Publication number
- CN104660386A CN104660386A CN201510094233.7A CN201510094233A CN104660386A CN 104660386 A CN104660386 A CN 104660386A CN 201510094233 A CN201510094233 A CN 201510094233A CN 104660386 A CN104660386 A CN 104660386A
- Authority
- CN
- China
- Prior art keywords
- server
- cluster
- hadr
- master server
- standby
- 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.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
-
- 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
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention discloses a DB2 disaster recovery high-availability improving method based on an Itanium platform and belongs to a disaster recovery scheme. The technical scheme is as follows: databases are established by using shared storage by the aid of Inspur cluster management software K-HA, a K-HA server cluster is established, and main servers in the K-HA server cluster correspond to standby servers; when one main server system in the server cluster has a failure, server cluster resources are switched to another main server automatically; change data of the main servers are synchronously copied to the standby servers by the aid of the HADR characteristic of DB2; when the databases of the main servers have failures, the standby servers quickly take over loads; workloads of the databases are copied to the independent standby servers, so that when the main servers have local hardware failures or disastrous site failures, the workloads cannot be interrupted. According to the method, a high-reliability and high-availability database environment is established, and dual protection is performed on hardware layers and software layers of production databases respectively.
Description
Technical field
The present invention relates to a kind of Disaster Tolerant Scheme, specifically a kind of method based on improving DB2 disaster tolerance high availability under Itanium platform.
Background technology
In the world today, the service of many enterprises for providing 7*24 hour from client all over the world, they wish the reliable of the computing system 100% of oneself.
Intel Anthem (Itanium) processor aims at and requires that harsh enterprise and technology are applied and design.Based on the platform of Intel Itanium-2 CPU with lower cost, provide leading performance, and select space widely than proprietary RISC technology, enterprise and mechanism can be helped maximally to improve its investment repayment.Intel Itanium-2 CPU obtains the support of the extensive ecosystem, comprise, by the leading hardware vendor of family more than 40, there are outstanding open-ended open standard 64 solutions, such as Windows Server 2003, HP-UX and Linux etc. more than 5 sections of operating systems, and hundreds of application and instrument.In addition, Intel Itanium processor also provides outstanding binary compatibility for existing Intel Anthem Framework Software, and then user can be made to obtain powerful investment protection.Intel Itanium-2 CPU family supports 32 Intel Architecture (IA-32) application, and the release along with 32 Intel Architecture (IA-32) execution level technology is strengthened further.
DB2 is a series of Relational DBMSs that IBM produces, and respectively at different operating system UNIX, Windows Access, ORACLE platform is served.DB2 for Linux, UNIX, and Windows are very advanced in database field, can provide the reliability of technical grade.From DB2 UDB V8.2, DB2 introduces two new features--disaster recovery (HADR, full name High Availability Disaster Recovery, High-availability Data Replication mechanism) and automatic client machine heavy-route function, they are the option realizing high availability for client provides more.Under normal circumstances, the two-server of HADR, they keep phase mutually synchronization at database level.Wherein the application program of master server and terminal use alternately and receive affairs, and standby server directly receives the affairs in the log buffer district of primary server and is applied to itself, thus keeps synchronous with master server.When master server failure, standby server just quickly adapter operating load (in most of the cases, being less than 30 seconds change-over time).Like this, by being copied on independent website by the operating load of database, thus ensure that service can not be interrupted when there is local hardware fault or calamitous site disasters.
Tide cluster management software K-HA is a software for realizing the high availability promoting hardware system.K-HA backs up the physical node of construction system and the application program etc. of key business, realizes automatic detection and the transfer of the system failure of core business, eliminates Single Point of Faliure, ensures continuation and the high availability of core business.This characteristic can carry out the adjustment of monitoring resource scope like a cork for oneself actual environment.By using tide cluster management software K-HA, one can also be allowed to run and the application program of automation team simultaneously on responsible Linux and inspur-K1, thus the judgement greatly simplified problem and analysis.
How being combined by K-HA and DB2 HADR, establish the database environment of a highly reliable and high availability, is those skilled in the art's problems in the urgent need to address.
Summary of the invention
Technical assignment of the present invention is to provide a kind of method based on improving DB2 disaster tolerance high availability under Itanium platform.The method adopting K-HA and DB2 HADR to combine, establishes the database environment of a highly reliable and high availability, has carried out duplicate protection respectively to the hardware layer of Production database and software layer.
Technical assignment of the present invention realizes in the following manner,
A kind of method based on improving DB2 disaster tolerance high availability under Itanium platform, by tide cluster management software K-HA, use shared storage creation database, set up the K-HA server cluster of a set of two-shipper High Availabitity environment, the corresponding standby server of master server in K-HA server cluster; When one of them master server system failure of server cluster, server cluster resource automatically switches to another master server; By the HADR characteristic of DB2, the change delta data of master server is synchronously copied to standby server; When the database failure of master server, standby server is takeover load rapidly; By being copied on independent standby server by the operating load of database, make when master server generation local hardware fault or calamitous site disasters, operating load can not interrupt.
Master server in server cluster uses shares storage creation database, and master server all installs tide cluster management software K-HA, all master servers and standby server is all provided with DB2 software and creates example.
Build server cluster between master server, the shared resource of server cluster has: virtual IP address, mounting disc, DB2 database.
Process step is as follows:
(1), all master servers and standby server be all provided with DB2 software and create example;
(2), master server all installs tide cluster management software K-HA, and start the service of K-HA;
(3), configure the IP of 2 different segments respectively to each master server, be used as public network IP and the heartbeat IP of this master server successively;
(4), use SAN storage management software, distribute to each master server and share storage;
(5), shared storage is used, creation database on master server;
(6), according to K-HA user's service manual, between master server, build server cluster, then successfully start server cluster; So far, K-HA and DB2 Disaster Tolerant Scheme is built complete;
(7), wherein a master server end carry out the configuration of HADR primary, and back up DB2 database;
(8), on standby server, carry out recovery DB2 test database, and carry out HADR standby configuration;
(9), on standby server start HADR with standby role, start successfully, master server in step (7) a metallic starts HADR with primary role; So far, DB2 HADR Disaster Tolerant Scheme is built complete;
(10), stop server cluster, the script resource of amendment server cluster, is revised as the script starting or stoping DB2 and starts or stops DB2 HADR; So far, the Disaster Tolerant Scheme that K-HA and DB2 HADR is formed is built complete;
(11), when DB2 HADR application failure, retain K-HA and DB2 Disaster Tolerant Scheme, continue externally to provide service, ensure that the high availability of database;
(12), when K-HA cluster resource fault, utilize the feature of DB2 HADR, continue externally to provide service, ensure that the high availability of database.
In step (6), select lv monitoring resource, floating ip monitoring in monitoring Energy Resources Service.
A kind of method based on improving DB2 disaster tolerance high availability under Itanium platform of the present invention has the following advantages:
1, by tide cluster management software K-HA, use shared storage creation database, thus establish a set of two-shipper High Availabitity environment, improve the high availability of hardware system;
2, when one of them master server fault, cluster resource automatically switches to another master server, so namely eliminates Single Point of Faliure, ensure that Production database can impregnablely continue externally to provide service;
3, by the HADR characteristic of DB2, the change delta data of master server is synchronously copied to standby server, prevention data is lost;
4, when the database failure of master server, standby server incites somebody to action takeover load rapidly, like this, by the operating load of database is copied on independent standby server, make can not interrupt when master server generation local hardware fault or calamitous site disasters, for part and complete station fault provide high-availability solution.
Accompanying drawing explanation
Below in conjunction with accompanying drawing, the present invention is further described.
Accompanying drawing 1 is a kind of structural topology figure of method based on improving DB2 disaster tolerance high availability under Itanium platform;
Accompanying drawing 2 is a kind of tide cluster management software K-HA workflow diagram of method based on improving DB2 disaster tolerance high availability under Itanium platform.
Embodiment
With reference to Figure of description and specific embodiment, a kind of method based on improving DB2 disaster tolerance high availability under Itanium platform of the present invention is described in detail below.
Embodiment 1:
A kind of method based on improving DB2 disaster tolerance high availability under Itanium platform of the present invention, a kind of method based on improving DB2 disaster tolerance high availability under Itanium platform, by tide cluster management software K-HA, use shared storage creation database, set up the K-HA server cluster of a set of two-shipper High Availabitity environment, the corresponding standby server of master server in K-HA server cluster; When one of them master server system failure of server cluster, server cluster resource automatically switches to another master server; By the HADR characteristic of DB2, the change delta data of master server is synchronously copied to standby server; When the database failure of master server, standby server is takeover load rapidly; By being copied on independent standby server by the operating load of database, make when master server generation local hardware fault or calamitous site disasters, operating load can not interrupt.
Master server in server cluster uses shares storage creation database, and master server all installs tide cluster management software K-HA, all master servers and standby server is all provided with DB2 software and creates example.
Build server cluster between master server, the shared resource of server cluster has: virtual IP address, mounting disc, DB2 database.
Embodiment 2:
A kind of method based on improving DB2 disaster tolerance high availability under Itanium platform of the present invention, a kind of method based on improving DB2 disaster tolerance high availability under Itanium platform, by tide cluster management software K-HA, use shared storage creation database, set up the K-HA server cluster of a set of two-shipper High Availabitity environment, the corresponding standby server of master server in K-HA server cluster; When one of them master server system failure of server cluster, server cluster resource automatically switches to another master server; By the HADR characteristic of DB2, the change delta data of master server is synchronously copied to standby server; When the database failure of master server, standby server is takeover load rapidly; By being copied on independent standby server by the operating load of database, make when master server generation local hardware fault or calamitous site disasters, operating load can not interrupt.
Master server in server cluster uses shares storage creation database, and master server all installs tide cluster management software K-HA, all master servers and standby server is all provided with DB2 software and creates example.
Build server cluster between master server, the shared resource of server cluster has: virtual IP address, mounting disc, DB2 database.
Process step is as follows:
(1), all master servers and standby server be all provided with DB2 software and create example;
(2), master server all installs tide cluster management software K-HA, and start the service of K-HA;
(3), configure the IP of 2 different segments respectively to each master server, be used as public network IP and the heartbeat IP of this master server successively;
(4), use SAN storage management software, distribute to each master server and share storage;
(5), shared storage is used, creation database on master server;
(6), according to K-HA user's service manual, between master server, build server cluster, then successfully start server cluster; So far, K-HA and DB2 Disaster Tolerant Scheme is built complete;
(7), wherein a master server end carry out the configuration of HADR primary, and back up DB2 database;
(8), on standby server, carry out recovery DB2 test database, and carry out HADR standby configuration;
(9), on standby server start HADR with standby role, start successfully, master server in step (7) a metallic starts HADR with primary role; So far, DB2 HADR Disaster Tolerant Scheme is built complete;
(10), stop server cluster, the script resource of amendment server cluster, is revised as the script starting or stoping DB2 and starts or stops DB2 HADR; So far, the Disaster Tolerant Scheme that K-HA and DB2 HADR is formed is built complete;
(11), when DB2 HADR application failure, retain K-HA and DB2 Disaster Tolerant Scheme, continue externally to provide service, ensure that the high availability of database;
(12), when K-HA cluster resource fault, utilize the feature of DB2 HADR, continue externally to provide service, ensure that the high availability of database.
In step (6), select lv monitoring resource, floating ip monitoring in monitoring Energy Resources Service.
Embodiment 3:
A kind of method based on improving DB2 disaster tolerance high availability under Itanium platform of the present invention, a kind of method based on improving DB2 disaster tolerance high availability under Itanium platform, by tide cluster management software K-HA, use shared storage creation database, set up the K-HA server cluster of a set of two-shipper High Availabitity environment, the corresponding standby server of master server in K-HA server cluster; When one of them master server system failure of server cluster, server cluster resource automatically switches to another master server; By the HADR characteristic of DB2, the change delta data of master server is synchronously copied to standby server; When the database failure of master server, standby server is takeover load rapidly; By being copied on independent standby server by the operating load of database, make when master server generation local hardware fault or calamitous site disasters, operating load can not interrupt.
Master server in server cluster uses shares storage creation database, and master server all installs tide cluster management software K-HA, all master servers and standby server is all provided with DB2 software and creates example.
Build server cluster between master server, the shared resource of server cluster has: virtual IP address, mounting disc, DB2 database.
As shown in Figure 1, process step is as follows:
(1), all master servers and standby server be all provided with DB2INST software and create example;
(2), master server K1_Node1 and K1_Node2 all installs tide cluster management software K-HA, and start the service of K-HA;
(3), configure the IP of 2 different segments respectively to each master server, be used as public network IP and the heartbeat IP of this master server successively;
(4), use SAN storage management software, distribute to each master server and share storage;
(5), shared storage is used, creation database on master server;
(6), according to K-HA user's service manual, between master server, build server cluster, then successfully start server cluster; So far, K-HA and DB2 Disaster Tolerant Scheme is built complete;
(7), wherein master server K1_Node1 end carry out the configuration of HADR primary, and back up DB2 database;
(8), on standby server K1_Node3, carry out recovery DB2 test database, and carry out HADR standby configuration;
(9), on standby server K1_Node3 start HADR with standby role, start successfully, master server K1_Node1 starts HADR with primary role; So far, DB2 HADR Disaster Tolerant Scheme is built complete;
(10), stop server cluster, the script resource of amendment server cluster, is revised as the script starting or stoping DB2 and starts or stops DB2 HADR; So far, the 3 node Disaster Tolerant Scheme that K-HA and DB2 HADR is formed are built complete;
(11), when DB2 HADR application failure, retain K-HA and DB2 Disaster Tolerant Scheme, continue externally to provide service, ensure that the high availability of database;
(12), when K-HA cluster resource fault, utilize the feature of DB2 HADR, continue externally to provide service, ensure that the high availability of database.
In step (6), select lv monitoring resource, floating ip monitoring in monitoring Energy Resources Service.
By embodiment above, described those skilled in the art can be easy to realize the present invention.But should be appreciated that the present invention is not limited to above-mentioned embodiment.On the basis of disclosed execution mode, described those skilled in the art can the different technical characteristic of combination in any, thus realizes different technical schemes.
Claims (5)
1. one kind based on the method improving DB2 disaster tolerance high availability under Itanium platform, it is characterized in that by tide cluster management software K-HA, use shared storage creation database, set up the K-HA server cluster of a set of two-shipper High Availabitity environment, the corresponding standby server of master server in K-HA server cluster; When one of them master server system failure of server cluster, server cluster resource automatically switches to another master server; By the HADR characteristic of DB2, the change delta data of master server is synchronously copied to standby server; When the database failure of master server, standby server is takeover load rapidly; By copying on independent standby server by the operating load of database, when master server generation local hardware fault or calamitous site disasters, operating load can not interrupt.
2. a kind of method based on improving DB2 disaster tolerance high availability under Itanium platform according to claim 1, it is characterized in that the master server in server cluster uses shared storage creation database, and master server all installs tide cluster management software K-HA, all master servers and standby server are all provided with DB2 software and create example.
3. a kind of method based on improving DB2 disaster tolerance high availability under Itanium platform according to claim 2, it is characterized in that building server cluster between master server, the shared resource of server cluster has: virtual IP address, mounting disc, DB2 database.
4. a kind of method based on improving DB2 disaster tolerance high availability under Itanium platform according to claim 3, is characterized in that process step is as follows:
(1), all master servers and standby server be all provided with DB2 software and create example;
(2), master server all installs tide cluster management software K-HA, and start the service of K-HA;
(3), configure the IP of 2 different segments respectively to each master server, be used as public network IP and the heartbeat IP of this master server successively;
(4), use SAN storage management software, distribute to each master server and share storage;
(5), shared storage is used, creation database on master server;
(6), according to K-HA user's service manual, between master server, build server cluster, then successfully start server cluster; So far, K-HA and DB2 Disaster Tolerant Scheme is built complete;
(7), wherein a master server end carry out the configuration of HADR primary, and back up DB2 database;
(8), on standby server, carry out recovery DB2 test database, and carry out HADR standby configuration;
(9), on standby server start HADR with standby role, start successfully, master server in step (7) a metallic starts HADR with primary role; So far, DB2 HADR Disaster Tolerant Scheme is built complete;
(10), stop server cluster, the script resource of amendment server cluster, is revised as the script starting or stoping DB2 and starts or stops DB2 HADR; So far, the Disaster Tolerant Scheme that K-HA and DB2 HADR is formed is built complete;
(11), when DB2 HADR application failure, retain K-HA and DB2 Disaster Tolerant Scheme, continue externally to provide service;
(12), when K-HA cluster resource fault, utilize the feature of DB2 HADR, continue externally to provide service.
5. a kind of method based on improving DB2 disaster tolerance high availability under Itanium platform according to claim 4, is characterized in that in step (6), selects lv monitoring resource, floating ip monitoring in monitoring Energy Resources Service.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510094233.7A CN104660386A (en) | 2015-03-03 | 2015-03-03 | DB2 disaster recovery high-availability improving method based on Itanium platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510094233.7A CN104660386A (en) | 2015-03-03 | 2015-03-03 | DB2 disaster recovery high-availability improving method based on Itanium platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104660386A true CN104660386A (en) | 2015-05-27 |
Family
ID=53251126
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510094233.7A Pending CN104660386A (en) | 2015-03-03 | 2015-03-03 | DB2 disaster recovery high-availability improving method based on Itanium platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104660386A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105162873A (en) * | 2015-09-22 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | High available method and system of K1 servers |
| CN105183591A (en) * | 2015-09-07 | 2015-12-23 | 浪潮(北京)电子信息产业有限公司 | High-availability cluster implementation method and system |
| CN105959172A (en) * | 2016-07-19 | 2016-09-21 | 浪潮(北京)电子信息产业有限公司 | Cluster system redundant network management method and platform |
| CN106130763A (en) * | 2016-06-24 | 2016-11-16 | 平安科技（深圳）有限公司 | Server cluster and be applicable to the database resource group method for handover control of this cluster |
| CN108200124A (en) * | 2017-12-12 | 2018-06-22 | 武汉烽火众智数字技术有限责任公司 | A kind of High Availabitity application architecture and construction method |
| CN108234271A (en) * | 2017-10-25 | 2018-06-29 | 国云科技股份有限公司 | A kind of cloud platform service network IP management methods |
| CN110019505A (en) * | 2017-09-15 | 2019-07-16 | 中兴通讯股份有限公司 | A kind of data center's DR test method, apparatus, equipment and storage medium |
| CN110392884A (en) * | 2017-02-23 | 2019-10-29 | 易享信息技术有限公司 | The selfreparing Database Systems of automation and the method for realizing it |
| CN113114777A (en) * | 2021-04-22 | 2021-07-13 | 善理通益信息科技(深圳)有限公司 | Disaster recovery method and device for multi-node high-availability cluster |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103186348A (en) * | 2011-12-27 | 2013-07-03 | 杭州信核数据科技有限公司 | Storage system and data reading-writing method thereof |
-
2015
- 2015-03-03 CN CN201510094233.7A patent/CN104660386A/en active Pending
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103186348A (en) * | 2011-12-27 | 2013-07-03 | 杭州信核数据科技有限公司 | Storage system and data reading-writing method thereof |
Non-Patent Citations (2)
| Title |
|---|
| BRUCE JACKSON等: ""DB2 10.1 HADR 多备机"", 《HTTPS://WWW.IBM.COM/DEVELOPERWORKS/CN/DATA/LIBRARY/LONG/DM-1206HADRMULTIPLESTANDBY/INDEX.HTML》 * |
| MONTY WRIGHT: ""用DB2 9.5 实现高可用性"", 《HTTPS://WWW.IBM.COM /DEVELOPERWORKS/CN/DATA/LIBRARY/ TECHARTICLES/ DM-0807WRIGHT/INDEX. HTML》 * |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105183591A (en) * | 2015-09-07 | 2015-12-23 | 浪潮(北京)电子信息产业有限公司 | High-availability cluster implementation method and system |
| CN105162873A (en) * | 2015-09-22 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | High available method and system of K1 servers |
| CN106130763A (en) * | 2016-06-24 | 2016-11-16 | 平安科技（深圳）有限公司 | Server cluster and be applicable to the database resource group method for handover control of this cluster |
| CN105959172B (en) * | 2016-07-19 | 2019-01-18 | 浪潮(北京)电子信息产业有限公司 | A kind of the redundant network management method and platform of group system |
| CN105959172A (en) * | 2016-07-19 | 2016-09-21 | 浪潮(北京)电子信息产业有限公司 | Cluster system redundant network management method and platform |
| CN110392884A (en) * | 2017-02-23 | 2019-10-29 | 易享信息技术有限公司 | The selfreparing Database Systems of automation and the method for realizing it |
| CN110392884B (en) * | 2017-02-23 | 2023-08-08 | 硕动力公司 | Automatic self-repairing database system and method for realizing same |
| CN110019505A (en) * | 2017-09-15 | 2019-07-16 | 中兴通讯股份有限公司 | A kind of data center's DR test method, apparatus, equipment and storage medium |
| CN108234271A (en) * | 2017-10-25 | 2018-06-29 | 国云科技股份有限公司 | A kind of cloud platform service network IP management methods |
| CN108200124A (en) * | 2017-12-12 | 2018-06-22 | 武汉烽火众智数字技术有限责任公司 | A kind of High Availabitity application architecture and construction method |
| CN108200124B (en) * | 2017-12-12 | 2021-02-12 | 武汉烽火众智数字技术有限责任公司 | High-availability application program architecture and construction method |
| CN113114777A (en) * | 2021-04-22 | 2021-07-13 | 善理通益信息科技(深圳)有限公司 | Disaster recovery method and device for multi-node high-availability cluster |
| CN113114777B (en) * | 2021-04-22 | 2022-07-01 | 善理通益信息科技(深圳)有限公司 | Disaster recovery method and device for multi-node high-availability cluster |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104660386A (en) | DB2 disaster recovery high-availability improving method based on Itanium platform | |
| US11249815B2 (en) | Maintaining two-site configuration for workload availability between sites at unlimited distances for products and services | |
| US10084858B2 (en) | Managing continuous priority workload availability and general workload availability between sites at unlimited distances for products and services | |
| CN107707393B (en) | Multi-active system based on Openstack O version characteristics | |
| US10055300B2 (en) | Disk group based backup | |
| CN109151045B (en) | Distributed cloud system and monitoring method | |
| AU2006297144B2 (en) | Application of virtual servers to high availability and disaster recovery solutions | |
| US9727273B1 (en) | Scalable clusterwide de-duplication | |
| US10482104B2 (en) | Zero-data loss recovery for active-active sites configurations | |
| US7689862B1 (en) | Application failover in a cluster environment | |
| US8539087B2 (en) | System and method to define, visualize and manage a composite service group in a high-availability disaster recovery environment | |
| EP3896570A1 (en) | Systems and methods for server cluster application virtualization | |
| US10430217B2 (en) | High availability using dynamic quorum-based arbitration | |
| US20070094659A1 (en) | System and method for recovering from a failure of a virtual machine | |
| US9015520B2 (en) | Data transfer and recovery | |
| US11841781B2 (en) | Methods and systems for a non-disruptive planned failover from a primary copy of data at a primary storage system to a mirror copy of the data at a cross-site secondary storage system | |
| CN111130835A (en) | Data center dual-active system, switching method, device, equipment and medium | |
| CN104486131B (en) | A kind of fault detect of DB2 database based on Itanium platform and switching method | |
| CN113821376B (en) | Cloud disaster recovery-based integrated backup disaster recovery method and system | |
| CN103793296A (en) | Method for assisting in backing-up and copying computer system in cluster | |
| CN104794012A (en) | Switching technique based on disaster recovery | |
| Bartkowski et al. | High availability and disaster recovery options for DB2 for Linux, UNIX, and Windows | |
| US20230252045A1 (en) | Life cycle management for standby databases | |
| US8656211B2 (en) | Avoiding failover identifier conflicts | |
| CN115905181A (en) | Database high-availability architecture design method, system and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20150527 |