Skip to main content
Question

OpenSUSE support in 13.1.2 missing

  • Nov 12, 2026 9:59 AM UTC
  • 4 comments
  • 24 views

I updated my backup-server to 13.1.2.57 (from 13.1.1.18) yesterday … today an agent-backup-job for an OpenSUSE 16.0 vm failes with "Warning : Skipping dbackup.bct-tech.local: operating system is not supported".
What the heck is that? It’s not mentioned in the release-notes, that machine-components where updated without a problem and now this? Honestly? Did an ai-agent run on that and another one doing the code-review?

My swear-filter is on … i have to stop here … :-)

4 comments

JMeixner
Forum|alt.badge.img+18
  • On the path to Greatness
  • Nov 12, 2026 10:10 AM UTC

Hello,
support for OpenSuse was ended with V13.
https://www.veeam.com/kb4784

 

The helcenter speaks about SLES only, too.

Perhaps the agent on the OpenSuse machine was not updated with the former upgrade to 13.1.1.18?


regnor
Forum|alt.badge.img+14
  • Veeam MVP
  • Nov 12, 2026 10:11 AM UTC

Hi ​@Klaus Strebel BCT! Actually the support for OpenSUSE has already been removed with v13 which makes we wonder why you run into this now. 

https://www.veeam.com/kb4784

You can continue backing up your system with the v6.3 agent in standalone mode and should also still be able to point it to a V13.1 VBR. Only upgrading and managing it won’t be possible with V13 and above.


Well, the last change of that artical was from September 30th and as there is no change history, so i can’t tell if this “fuck on openSUSE” was in when the upgrade to 13.1 was run …
Anyway, i cant’t understand this decision … SLES and openSUSE are build from the same tree and differences are not that big :-(.

Guess there a two main problems: keeping up with kernel-updates (openSUSE is a bit quicker in this topic … thow even NVidia and VMware can do that ;-)) and money, Veeam seems to support only platforms with payed support.


JMeixner
Forum|alt.badge.img+18
  • On the path to Greatness
  • Nov 13, 2026 2:10 PM UTC

Well, we have no influence over Veeam’s product policy here; this is purely a user community.

However, I can imagine that it is significantly easier to provide support for products that come with paid support and are properly maintained by their manufacturers, rather than dealing with all sorts of developer-led or open-source variants.