Bare Metal & VPS
Bare Metal & VPS
This domain checks whether you can map a workload to the right OVHcloud server product and then configure it correctly. Questions focus on dedicated server ranges, VPS ranges, the split of responsibility, and the options that change how a machine is addressed, protected and recovered.
Dedicated servers
OVHcloud dedicated servers are sold in ranges that trade CPU, memory, disk type and bandwidth against each other: Rise and Advance for entry and mid-range workloads, Scale for balanced production, High Grade for redundancy and enterprise components, and Infrastructure for hosting and virtualisation. Bandwidth is quoted as guaranteed versus burst, and higher ranges add redundant power supplies and hardware RAID.
VPS
VPS ranges (Value, Essential, Comfort, Elite) scale vCores, RAM and disk, with Elite adding NVMe. A VPS is a virtual machine on a shared hypervisor: OVHcloud owns the hardware, hypervisor and network; you own the OS upward and patch it yourself.
Options that matter
- Failover and additional IPs, configured inside the OS, not by OVHcloud.
- vRack attachment for private Layer 2 networking between services.
- Backup storage, Windows licences, and reverse DNS set per IP.
- Rescue mode (netboot) for recovery and VPS snapshots for fast rollback.
Worked example
A team needs a virtualisation host with dual power supplies, 10 Gbps and private connectivity to an existing rack. Rise and Advance lack the redundancy, so the answer is a High Grade or Infrastructure server, plus vRack, plus a failover IP if the public address must move between hosts. The reasoning chain is: redundancy requirement → High Grade; throughput → bandwidth option; private Layer 2 → vRack.
Traps
A VPS snapshot is not a backup: it lives with the server and disappears with it. Rescue-mode changes are lost after reboot unless written to disk. Adding a failover IP without OS configuration leaves it unreachable. "Guaranteed" bandwidth is not the same as burst.