From: Andrei Boros <andrei@srr.ro>
To: pve-user@lists.proxmox.com
Subject: Re: Question about Disaster Recovery Architecture Between Two Datacenters
Date: Thu, 18 Jun 2026 13:09:34 +0300 [thread overview]
Message-ID: <ddf05a00-d7d0-de83-c6af-6953fa095851@srr.ro> (raw)
In-Reply-To: <DU0PR03MB92537C52578027E0513C139DCDE32@DU0PR03MB9253.eurprd03.prod.outlook.com>
By SAN do you mean block storage connected via FibreChannel?
On 2026-06-18 12:38 PM, Iván Méndez Cairós wrote:
> Hello,
>
> We would like to know whether the following Disaster Recovery scenario can be implemented with Proxmox VE and what would be the recommended architecture.
>
> Our environment consists of:
>
>
> * A primary datacenter with more than three Proxmox VE hosts connected to a SAN storage array.
> * A secondary datacenter with equivalent infrastructure (Proxmox VE hosts and a storage array).
> * Storage replication from the primary array to the secondary array.
> * Both datacenters are connected through a LAN network with very low latency and sufficient bandwidth, so network performance is not a concern.
>
> Our objective is to ensure business continuity in the event of a complete failure of the primary datacenter.
>
> In such a scenario, we would like the virtual machines to be started in the secondary datacenter with as much automation as possible and with minimal manual intervention.
>
> We would appreciate your guidance regarding the following points:
>
>
> 1. Does Proxmox VE officially support this type of architecture?
> 2. Would you recommend a stretched cluster across both datacenters, or two independent Proxmox clusters?
> 3. What are the requirements regarding quorum, fencing, HA, networking, and storage?
> 4. Is it possible for Proxmox HA to automatically start the virtual machines in the secondary datacenter if the primary datacenter becomes completely unavailable?
> 5. What are the main limitations or considerations for this design?
> 6. What would be the recommended Proxmox architecture and best practices to achieve an automated Disaster Recovery solution in this scenario?
>
> Any recommendations, documentation, or real-world deployment examples would be greatly appreciated.
>
> Thank you very much for your assistance.
>
> Best regards,
> Iván Méndez
> Systems Administrator
>
--
*ing. Andrei Boros*
Serviciul IT&C
*Radio Romania*
|Tel: +40-21-303-1870
+40-745-115721
Email: andrei@srr.ro <mailto:andrei@srr.ro>|
prev parent reply other threads:[~2026-06-18 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 9:38 Question about Disaster Recovery Architecture Between Two Datacenters Iván Méndez Cairós
2026-06-18 10:09 ` Andrei Boros [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=ddf05a00-d7d0-de83-c6af-6953fa095851@srr.ro \
--to=andrei@srr.ro \
--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.