◉ In terms of disaster recovery, can Xinchang virtualization extend clusters like VMware? Or must it rely on load balancing and disaster recovery software to achieve virtual machine disaster recovery effects?*The question comes from community member @loveoct10th, a system engineer at a commercial bank in a certain city. The following sharing is from community peers for your reference.
@yyf123, System Engineer at Weihai Commercial Bank:
Whether Xinchang virtualization can extend clusters like VMware, or if it must rely on load balancing and disaster recovery software to achieve virtual machine disaster recovery effects, does not depend on the virtualization technology itself, but rather on the business scenario and the limitations of its own technical architecture.
My understanding of the term “extended cluster” mainly refers to cross-center virtualization clusters. Using this method also requires support from storage disaster recovery design and large layer two network planning design. The biggest challenges of cross-data center clusters are twofold: first, from the storage perspective, after a storage failure at any center, the other center must have a complete set of data from both centers. Therefore, storage must be designed for dual-active operation. Second, from the business network perspective, it must solve the problem of how to provide services when a virtual machine drifts from one data center to another while keeping the IP address unchanged.
Using extended clusters can theoretically allow virtual machines to automatically be taken over by other physical servers when a physical server running the virtual machine fails (shutdown and reboot may cause service interruption), which can meet the bank’s disaster recovery level six target requirements (RPO=0, RTO in minutes). However, in practice, it is constrained by the stability, latency, and large layer two network structure of the underlying network, posing significant challenges to traditional data centers and making maintenance difficult, thus not widely adopted.
Using load balancing and database disaster recovery software can not only approximate the effects of extended clusters but also have moderate maintenance difficulty, although the workload is relatively large. Load balancing is mainly used to solve application disaster recovery issues, ensuring continuity at the application level. In practice, a DNS + load balancing solution is generally used. The basic principle of database disaster recovery software replication is that each center has a set of virtualization clusters, and each usually runs a set of databases for replication. When the primary center fails, the backup center’s database starts to take over the business, and this solution requires DNS support for database access. This solution uses traditional network technology to solve disaster recovery issues.
@Fresh feel, Cloud Platform Operation and Maintenance Management Position at Beiyin Financial Technology Co., Ltd:
I have not encountered Xinchang virtualization products to implement VMware’s extended clusters. However, this does not rule out that such products have corresponding capabilities, and disaster recovery is not solely achieved through load balancing and disaster recovery software. The mechanisms implemented by different Xinchang virtualization products vary, and it is necessary to look at the specific support solutions of each Xinchang virtualization product. Many Xinchang virtualization products I have encountered are striving to provide similar disaster recovery and high availability solutions. When selecting a virtualization product that meets the needs, it is advisable to carefully evaluate the capabilities and characteristics of each product, and virtualization vendors will also provide solution suggestions and network design based on customer needs.
@Effort to Move Bricks, System Operation and Maintenance Engineer at a Joint-Stock Bank：
Currently, mainstream Xinchang virtualization products are developed with reference to VMware, soVMware’s main functions are also present in Xinchang virtualization, and extended clusters are one of the main functions. Normal virtualization includes two main parts: one is the host (corresponding toVMware’s ESXI), and the other is the management platform (corresponding toVMware’s vCenter). The ability to extend clusters relies on the management platform. Our bank frequently has resource demands, and cluster extension has been done many times. As long as the compatibility of the host and FC is ensured, and the x86 architecture and Kunpeng are placed in different clusters, expansion is basically not a problem.
What do you think?Feel free to discussWelcome to click the original text at the end of the article to read and discuss in the community
If you find this article useful, pleaseshare, like or click“♡” so that more peers can see it
Recommended materials/articles:
-
VMware Virtualization Xinchang for Small and Medium Banks: Replacement Strategies, Selection Methods, Unified Management (Summary of Peer Consensus)
-
Comparison of VMware Replacement Routes in Manufacturing: Virtualization Software Alternatives vs. Hyper-Converged Architecture
-
Manufacturing Enterprises Adopting IaaS Cloud Platforms to Replace VMware: Advantages and Disadvantages Analysis, Migration Difficulties, and Solutions
-
Discussion on Key Application VMware Virtualization Replacement in Urban Commercial Banks: Strategies, Alternative Paths, Key Selection Points
-
Trends in the Application of High-End Equipment Manufacturing Enterprises Migrating from Original VMware Virtualization to Cloud-Native Platforms
Welcome to follow the community’s “Virtualization” technology theme , which will continuously update quality materials and articles. Address:http://www.talkwithtrend.com/Topic/23
Download the twt community client APP
Long press to recognize the QR code to download
Or search for “twt” in the app store
Long press the QR code to follow the public account
*The content published by this public account only represents the author’s views and does not represent the community’s position.