How do I connect an Additional IP in Proxmox on OVH?

Additional IP networking and the gateway depend on the OVHcloud server range. The OVHcloud networking guide covers routing and vRack IP blocks for HG/Scale. There, the first, penultimate and last block addresses are reserved for network, gateway and broadcast; do not apply gateway or MAC rules to other ranges without checking. We review the assigned network before configuration.

Does Proxmox on OVHcloud make sense as Single Node?

Yes - especially for smaller setups, Single Node on Bare Metal is very reasonable. What matters is backups, monitoring and an update runbook to keep operations stable.

Do I need 3 nodes for HA?

For true HA with stable quorum, 3+ nodes is the standard. Two nodes only work with an additional quorum concept and are operationally more demanding.

What does Proxmox on OVH cost?

Proxmox itself has no license cost; costs depend on bare metal sizing, storage concept and your operating model (setup vs managed). We calculate transparently via sizing + SLA + backup/monitoring.

Is a 2-node cluster on OVH sensible?

You can run 2 nodes, but for quorum/HA you typically need an external quorum element (QDevice) or clear operational rules. We recommend 2 nodes more for "cluster management/live migration light" than for "true HA".

What is vRack and why do I need it?

vRack is OVHcloud's private Layer-2 network to privately connect dedicated servers and other OVH services. Perfect for cluster/storage communication without public internet.

Can I connect Dedicated and Public Cloud privately?

Yes - OVH explicitly shows the configuration between Public Cloud and Dedicated via vRack. This is helpful if you have bastion/tools in Public Cloud but workloads on Bare Metal.

Which network separation does Proxmox need?

At minimum Management separated from Corosync/Cluster. If Ceph is added, you need your own storage network - at OVH typically achievable cleanly via vRack/VLAN design.

What typical mistakes happen with vRack?

IP/VLAN plan is done "on the fly", MTU/segmentation not considered, and then cluster/storage runs over public IPs. We build the network plan first, then the cluster.

ZFS or Ceph - which is better?

Single Node: usually ZFS. HA Cluster: Ceph can make sense if network/disks fit - otherwise "simpler" shared storage or ZFS+replication strategy is often more economical.

Does Proxmox + Ceph work well on OVH Bare Metal?

Yes, but only with proper design: dedicated storage network, enough SSD/NVMe, clear failure domain. If budget/network doesn't fit, we'd rather recommend a more robust, simpler-to-operate setup.

How does installation on OVH work?

Provisioning Bare Metal → Proxmox installation → Network design (incl. vRack) → Storage → Backup/Monitoring. Important: Hostname/IP planning must be final beforehand (reluctant to change later in cluster).

How do you prevent split-brain/quorum problems?

Through 3+ nodes, clean Corosync network, stable latencies and clear maintenance processes. With 2 nodes you need additional quorum strategy.

How do you secure management access?

Bastion/VPN instead of public GUI. Plus firewall rules, logging and defined emergency access.

Can I grow from Single Node to Cluster later?

Yes - many start as Single Node and expand later. What's important is setting clean standards from the start (naming, IP plan, backup, monitoring).

Single Node: Maintenance window. Cluster: node-by-node rolling update with tests.

How do you handle backups and restore tests?

Automated backups + regular restore tests. The restore test is the actual quality proof, not just "backup exists".

How do we migrate from VMware to Proxmox on OVH?

We plan the migration in phases: Inventory → Test import → Performance check → final cutover with rollback option. The biggest lever is almost always: decide storage/network cleanly beforehand.

Do you offer support/hour packages for OVH Proxmox?

Yes. Proxmox support is billed by effort, and hour packages of 10, 25 or 50 hours are available; for ongoing operations we offer Managed Proxmox (SLA, monitoring, updates, backups).

Proxmox on OVHcloud: setup, HA, and operations

We design single nodes and HA clusters on suitable OVHcloud bare-metal servers, including vRack, storage, backup, and optional managed operations.

Cost Control
vRack Network
Full Control

Free Initial Assessment Support & Hour Packages

Reviews

IT Beratung Service Consulting Soforthilfe

Companies worldwide trust WZ-IT

Read client reviews

Proxmox × OVHcloud

Why Proxmox on OVHcloud?

Enterprise virtualization without vendor lock-in on OVHcloud Bare Metal - with vRack for professional network design.

Cost
Proxmox VE is open source and needs no mandatory license; a subscription (per CPU socket) is optional.
vRack
Private Layer-2 network connects all servers like in the same rack - including public cloud integration.
EU & GDPR
OVHcloud data centers in the EU. French company, European data sovereignty.
Performance
Dedicated hardware = consistent performance. Wide server range from entry to high-end.
Typical Use Cases
Private Cloud · Legacy VMs · VDI · Kubernetes Nodes · Dev/Staging/Prod

Architecture

Architecture Options

Which architecture fits your requirements? We help with the decision.

Single Node

Option 1: Single Node Proxmox on OVH Dedicated

Simple setup & management
Full dedicated hardware
Predictable monthly costs
Ideal for SMB & dev/test

One dedicated server for smaller workloads or cost focus. Dedicated resources, simple setup, clear responsibility.

Recommended for HA

Option 2: Proxmox Cluster on OVH Bare Metal (HA)

VM restart after node failure
Live migration without a VM restart
Move guests before maintenance
Coordinate quorum and storage

From three nodes: HA restarts guests after a node failure. Live migration moves running VMs without a restart. Quorum, storage and spare capacity are prerequisites.

Hybrid

Option 3: Hybrid - OVH Public Cloud + Dedicated

Flexible access
Private L2 via vRack
Jump server in cloud
Workloads on dedicated

Management/bastion in OVH Public Cloud, workloads on dedicated servers. vRack connects both worlds.

A single node needs backups, restore tests and monitoring; a failure requires recovery through backup/restore. Expansion into a cluster is possible as requirements grow. HA clusters enable automatic failover on node failure and maintenance during operation.

vRack

Network design with vRack and Additional IP

What we set up on OVHcloud: network, cluster and high availability as well as backup, updates and monitoring.

vRack

vRack connects compatible servers through a private Layer 2 network. Additional IP networking and the gateway are checked for the specific server range. As of October 2026.

vRack (Private Layer-2)
OVH's isolated private network connects dedicated servers and public cloud like in the same rack. Ideal for cluster communication and storage traffic.
OVHcloud: vRack OVHcloud: Proxmox networking
Connect Public Cloud + Dedicated
vRack enables direct L2 connection between OVH Public Cloud instances and bare metal servers - without internet detour.
Separated Networks
Best practice: Management, cluster/Corosync and storage on separate VLANs for security and performance.

Network separation

Best Practice: Separated Networks via vRack VLANs

Management
Web GUI, SSH, API access
Cluster/Corosync
Heartbeat, quorum, cluster sync
Storage (optional)
Ceph, NFS, iSCSI traffic

Cluster & High Availability

Proxmox Cluster Manager and HA Manager enable automatic failover on node failures. We configure this for you.

Cluster Setup
pvecm, naming concept, network requirements
HA Manager
Automatic failover of VMs and containers
Quorum & Split-Brain
3-node recommendation, QDevice for 2-node setups
ZFS (local)
VM live migration can transfer local disks. HA can use ZFS replication; a node failure may lose changes made since the last replication.
Proxmox: Live Migration Proxmox: ZFS Replication
Ceph (Verteilt)
Shared storage, HA-friendly, self-healing. More complex, requires dedicated network via vRack. Recommended for HA clusters.

Backup, Updates, Monitoring

Professional operations mean: automation, monitoring, documented processes.

Backup Strategy
Proxmox Backup Server (PBS), defined RPO/RTO, immutable & offsite backups, regular restore tests
Update Management
Rolling updates, documented runbooks, coordinated maintenance windows, rollback plans
Monitoring & Alerting
Host/VM/storage metrics, backup job monitoring, alerting on issues, capacity planning

Process

Project Process

How we work - transparent and structured.

01
Assessment
Analysis of existing workloads, network, storage and requirements
02
Architecture & Sizing
Planning the optimal configuration for your requirements
03
Build
Setup of cluster/single node, vRack network, storage and backup
04
Test
Failover tests, restore tests, live migration validation
05
Migration
Cutover of existing workloads with minimal downtime
06
Operations & Support
Ongoing maintenance, monitoring and support as needed

Support

Support & Operating Models

Setup with handover, shared operations or fully managed: you decide what stays with your team.

Managed Proxmoxfrom €179.90 excl. VAT / node and monthWe handle complete operations: monitoring, updates, backups, support - you focus on your business.

Fully Managed

Monitoring
Updates
Backups
Support

Free Initial Assessment Proxmox maintenance and operations Configure a non-binding request

Payment

Bank transfer

Other routes

One-time Setup

We set up your Proxmox server/cluster, document everything and hand over to your team.

View Proxmox setup →Billed by time

Co-Managed

Your team handles daily operations, we support with updates, troubleshooting and expansions.

€120 excl. VAT / hour · Hour packages from €1,200 excl. VATDescribe the task →For professional secrecy holders

Operate Proxmox in the Section 203 Managed Cloud

If Proxmox processes client, patient or other professional secrets, WZ-IT plans the application, infrastructure, access, backups and ongoing operations within a purpose-built operating model.

View the Section 203 Managed Cloud →

Frequently Asked Questions

Proxmox on OVHcloud - Answers to Your Questions

TopicsBasics Network & vRack Storage Installation & Setup Operations & Migration Support

Basics

Network & vRack

Storage

Installation & Setup

Operations & Migration

Support

Knowledge

Proxmox proof from real projects

Customer feedback on virtualization, backup, VPN, security and ongoing cluster operations.

Networking & Provisioning

WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.

Steve KirchnerManaging Director, nextGYM GmbH

View project

International

Built in Germany's Ruhr Valley. Running worldwide.

WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.