SLES 16 support for on-prem

Nick D'Angelo 45 Reputation points
2026-10-28T12:48:17.9966667+00:00

I have a recently upgraded SLES 16 system that was working under SLES 15 on-prem. I see that SLES 16 is supported under Azure VMs and needs the 6.97 Mobility Agent, but nothing for on-prem is listed past SLES 15 or Mobility Agent 9.66. I did attempt to get the updated kernels from the Github repo and see if they would work on 9.66. Kernel drivers install fine and services start, but I end up hitting a wall with the Mobility Agent not supporting SLES 16.

The error in the svagents_curr_2662.log file:

#~> (10-28-2026 12:28:30): ERROR 386168 140384072124096 9 Failed to acquire OS information with error Un Supported SuSE release Flavour version..

Is there a timeline for an updated Mobility Agent release or a workaround I can do to get the system replicating again?

Azure Site Recovery
Azure Site Recovery

An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rukshan edirisinghe 2,365 Reputation points
    2026-10-29T03:16:23.16+00:00

    Hi @Nick D'Angelo

    Your log matches what the docs say right now. The VMware/physical-to-Azure support matrix lists SUSE Linux Enterprise Server only up to 15 SP7 (mobility service 9.66, Modernized experience). SLES 16 isn't listed for on-premises machines yet, so the 9.66 agent refusing the OS ("Un Supported SuSE release") is expected. Swapping in newer kernel drivers won't get past that check. Microsoft also hasn't published a date for on-prem SLES 16 support.

    Practical options while you wait:

    1. Protect it outside Site Recovery for now. Back up the SLES 16 server with your existing backup tool, so you aren't left without a recovery copy.
    2. If DR is mandatory now, keep a SLES 15 SP7 instance for this workload until support arrives. SP7 is fully supported with 9.66.
    3. Watch the update rollups. New OS support arrives with new mobility service versions. Check the Site Recovery "What's new" page and the support matrix for the next agent release, then upgrade the agent from the configuration server or appliance.
    4. Don't leave the half-installed agent running. Disable replication for this machine so the portal doesn't keep reporting a failed state.

    If you have a Microsoft account team or a support plan, ask them for the expected timeline. Only the product team can confirm dates.

    Is this server on VMware, or is it a physical machine?

    If this clears up where things stand, please consider accepting it as the answer. If a new mobility agent version appears and still rejects SLES 16, let me know and I'll be happy to keep helping.

    Reference:

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.