AMD based Cluster to Intel based cluster DR

Abdo Lv1Posted Jan-02-2026 02:09

Hello, Is it possible to have main site cluster based on Intel CPUs and DR based on AMD ?

Muhammad Abid has solved this question and earned 10 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Yes, a primary cluster based on Intel CPUs and a DR cluster based on AMD CPUs is possible. This setup works well for disaster recovery scenarios as long as both clusters use compatible hypervisor versions and CPU compatibility/feature masking is applied.

However, live migration between Intel and AMD clusters is not supported. This design is suitable for cold or warm DR, where virtual machines are started at the DR site only during a failover event.
Is this answer helpful?
Abdo Lv1Posted Jan-04-2026 04:46
  
No — Sangfor HCI disaster recovery (DR) does not support cross‑CPU vendor clusters. Both the production site and the DR site must use the same CPU vendor family (Intel ↔ Intel or AMD ↔ AMD) to ensure VM compatibility, live migration, and replication consistency. Mixing Intel and AMD clusters is not supported for DR failover or replication scenarios
Muhammad Abid Lv2Posted Jan-05-2026 14:30
  
Yes, a primary cluster based on Intel CPUs and a DR cluster based on AMD CPUs is possible. This setup works well for disaster recovery scenarios as long as both clusters use compatible hypervisor versions and CPU compatibility/feature masking is applied.

However, live migration between Intel and AMD clusters is not supported. This design is suitable for cold or warm DR, where virtual machines are started at the DR site only during a failover event.
Newbie412265 Lv1Posted Jan-07-2026 23:18
  
thanks for the info.
Newbie140813 Lv1Posted Jan-12-2026 15:44
  


A hybrid primary/DR cluster configuration utilizing heterogeneous CPU architectures—specifically Intel-based primary hosts and AMD-based disaster recovery hosts—is architecturally feasible. This design is predicated upon maintaining hypervisor version compatibility across both clusters and implementing rigorous CPU feature masking or compatibility modes to ensure consistent instruction set exposure to guest virtual machines.
Critical technical constraints apply:
1- Cross-architectural vMotion/Hyper-V Live Migration is unsupported.
2- VM Compatibility Policies are Required.
3-Storage and Network Abstraction is Essential.
4-Failover is Restart-Based.
Recommended Implementation Pattern:
  • Deploy a primary cluster with Intel CPUs (e.g., Cascade Lake/Ice Lake).
  • Establish a secondary DR cluster with AMD CPUs (e.g., Zen 3/4), configured with equivalent EVC/compatibility mode.
  • Utilize hypervisor-aware replication (e.g., VMware SRM, Hyper-V Replica, Zerto) or storage-based replication to maintain VM synchrony.
  • Validate VM hardware compatibility through automated recovery plans and regular DR testing.

This approach provides infrastructure diversification, mitigating supply chain and silicon-level fault risks, while adhering to the operational constraints of heterogeneous CPU environments in a failover context.

I Can Help:

Change

Board Leaders

NyxZale...

Weekly Sharers

Newbie5...

Weekly Questioners