









We are moving production e-commerce workloads away from our current OVHcloud VPS after repeated automated-backup/snapshot incidents and more than two months without a durable resolution.
The key issue for us is not only the latest outage. It is the pattern: our first known incident was on 2026-04-15, and the first related ticket was around 2026-04-16. Since then we repeatedly reported that the automated backup / snapshot problem and VPS unavailability were not resolved. In practice, OVHcloud kept closing subsequent tickets as "resolved" while the underlying issue remained. We have now been dealing with this for over two months without a complete RCA or durable fix.
Context:
Latest major incident:
On 2026-06-19 our shops were unavailable for about 5 hours while OVH Manager showed backup in progress. Recovery required OVH's legacy API console abortSnapshot POST endpoint, not a normal Manager action:
https://api.eu.ovhcloud.com/console-old/#/vps/{serviceName}/abortSnapshot~POST
OVH later wrote in the ticket that the backup had been running from 2026-06-18 23:57:29 and that on 2026-06-19 at 05:06:45 libvirt was killed and the VPS rebooted after abortSnapshot cancelled the backup.
We rejected OVH's proposed resolution and CS16036806 is still open.
What remains unresolved:
I am posting this as a factual incident report and to ask whether others have seen similar OVHcloud VPS automated-backup or snapshot freezes. From our perspective, this OVH VPS / automated backup setup is not suitable for business-critical e-commerce workloads until OVH provides a clear RCA and a durable fix.
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。