From: "Max R. Carrara" <m.carrara@proxmox.com>
To: "Iván Méndez Cairós" <imendez@integratyc.com>,
"pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>
Subject: Re: Question about Proxmox VE stretched cluster between two datacenters
Date: Thu, 11 Jun 2026 13:34:55 +0200 [thread overview]
Message-ID: <DJ66SP6PK2W3.1J2RDR3AX2Z1U@proxmox.com> (raw)
In-Reply-To: <DU0PR03MB9253472140E7300C554AEAD0CD1B2@DU0PR03MB9253.eurprd03.prod.outlook.com>
On Thu Jun 11, 2026 at 12:17 PM CEST, Iván Méndez Cairós wrote:
> Hello everyone,
>
> We would like to know if it is possible to implement a stretched cluster with Proxmox VE in the following scenario:
>
> * Two datacenters (Production and Backup/DR)
> * Same infrastructure on both sites
> * Dedicated virtualization servers on both datacenters
> * Dedicated storage arrays on both datacenters
> * High Availability between both sites
> * Automatic failover between datacenters
>
> The idea is that, if the main datacenter goes down completely, the backup datacenter automatically continues providing the services without manual intervention.
>
> Is this possible with Proxmox VE?
> If so, what would be the recommended architecture or best practices for this kind of deployment?
>
> Thank you very much.
>
> Best regards,
>
> Iván
Hi Iván!
Yes, that is indeed possible with Proxmox VE + Ceph. PVE tightly
integrates Ceph, resulting in a fully hyper-converged infrastructure
(HCI). The "stretch cluster" is what you want, and we do in fact have a
guide on that:
https://pve.proxmox.com/wiki/Stretch_Cluster
Note that in a HCI cluster storage and compute aren't separated as with
"traditional" setups, so you generally wouldn't have dedicated
virtualization servers and dedicated storage arrays. You probably know
this already, but I wanted to mention it nevertheless.
More on HCI here:
https://pve.proxmox.com/wiki/Hyper-converged_Infrastructure
So, to address your points individually:
> * Two datacenters (Production and Backup/DR)
Done with Ceph with appropriate CRUSH rules, but you do need a third
location for a tie-breaker node (see the stretch cluster guide above).
What's also possible is having three datacenters instead, but I assume
that's not within your budget. ;)
> * Same infrastructure on both sites
Yeah, that works excellently with the stretch cluster setup.
There are no restrictions when it comes to hardware, network topology,
etc., so how *exactly* you define your infrastructure is up to you.
> * Dedicated virtualization servers on both datacenters
> * Dedicated storage arrays on both datacenters
As mentioned earlier, storage and compute aren't separated anymore; all
nodes work as compute and storage nodes. That means no "storage boxes"
etc.
This might seem a bit strange / unfamiliar to some, but the main benefit
is that you can scale up super easily. Ceph performs better the more
nodes and OSDs you add and, with appropriate configuration (CRUSH rules
etc.), ensures that your data is replicated across both datacenters.
The exact configuration is up to you, but the stretch cluster guide does
show how you can have two replicas per location -- meaning that each
datacenter contains two copies of your data.
> * High Availability between both sites
> * Automatic failover between datacenters
Done with our HA Manager: https://pve.proxmox.com/wiki/High_Availability
So yes, if one datacenter were to go down for some reason, the other one
would just continue chugging along, no manual intervention required.
That should answer all of your questions, I think. Hope that helps!
Best regards,
Max
prev parent reply other threads:[~2026-06-11 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 10:17 Question about Proxmox VE stretched cluster between two datacenters Iván Méndez Cairós
2026-06-11 11:34 ` Max R. Carrara [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DJ66SP6PK2W3.1J2RDR3AX2Z1U@proxmox.com \
--to=m.carrara@proxmox.com \
--cc=imendez@integratyc.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.