Skip to main content

Veeam | Support and Updates

Veeam, Veeam Support, v9, Veeam support

Updated over 3 weeks ago

Overview 💥

Liongard currently supports two versions of the Veeam Inspector. Each Inspector corresponds to specific versions of the Veeam Service Provider Console (VSPC) and Veeam Agent:

  • The Veeam Availability Console (Service Provider Console v3) Inspector is designed for partners running Veeam Availability Console (Service Provider Console) using Veeam agents v3 and below.

  • The Veeam Service Provider Console v4 Inspector is designed for partners running Veeam Service Provider Console using Veeam agents v4 and above.

Inspector Name

Compatible Veeam Agent Versions

API Compatibility

Inspector Status

Veeam Availability Console (Service Provider Console v3) Inspector

v3 and below

API versions used by VSPC v3

Legacy – Functional but approaching end-of-life

Veeam Service Provider Console v4 Inspector

v4 and above

REST API v3.5.x

Active – Recommended Inspector

‼️ Compatibility Note (December 2025)

Veeam Service Provider Console v9+ introduces REST API v3.6, which is not compatible with Liongard’s current v4 Inspector. Upgrading to VSPC v9 will cause the Inspector to fail.


Why This Happens 🤔

1️⃣ Veeam API Version Changes

  • VSPC v9 transitioned from REST API v3.5.x → v3.6, introducing breaking changes.

  • Liongard’s Veeam Service Provider Console v4 Inspector is built for API v3.5.x only, and does not understand the new response structures and endpoints.

2️⃣ Deprecated V3 Inspector

  • The Veeam Availability Console (v3) Inspector may still function if:

    • Agents have been upgraded to v4+

    • VSPC remains on supported builds

  • However, Liongard will deprecate support once Veeam ends support for v3 agents.

3️⃣ Unsupported API Calls

Examples of failures seen with VSPC v9:

  • Expected page results to be an array, got undefined…

  • Authentication errors

  • Empty/invalid responses on:

    • /api/v3/protectedWorkloads/fileServers

    • /api/v3/backupServers

    • /api/v3/tenants


Current Support Matrix 🧑‍🏫

Veeam Console Compatibility Table

VSPC Version

REST API Version

Supported by Liongard Inspector?

Notes

v4 – v8.1

v3.5.x

Supported

Full Inspector functionality

v9+

v3.6

Not Supported

Inspector will fail to authenticate/parse data

Agent Compatibility

Veeam Agent Version

Compatible Inspector

v3 or below

v3 Inspector : Veeam Availability Console Inspector

v4 or above

v4 Inspector : Veeam Service Provider Console


Updating Veeam Inspectors 👨‍💻

Liongard strongly recommends upgrading all environments to the Veeam Service Provider Console v4 Inspector, provided your VSPC is not running version 9.

✅ Step-by-Step Process

  1. Verify VSPC Version

    • Ensure your console is running VSPC v4 – v8.1

    • If you are on v9, stop here — the Inspector will not work.

  2. Verify Agent Versions

    • All Veeam Agents must be v4 or above.

  3. Deploy the v4 Inspector

    • Deploy the Veeam Service Provider Console v4 Inspector to all environments meeting agent requirements.

  4. Disable Legacy Inspectors

    • Disable the v3 Inspector once v4 Inspector is successfully deployed.

    • Historical data is retained even after disabling the Inspector for the certain period of time.

  5. Re-link Assets & Configurations

    • Relate or bundle prior Veeam Configurations/Flexible Assets with the new v4 Inspector’s assets.

    • Ensures continuity for reports, metrics, and alerts.


What If You Already Upgraded to VSPC v9? 😇

If your partner already upgraded to v9:

Symptom

Cause

Required Action

Authentication failures

API 3.6 format mismatch

Roll back to VSPC v8.1 OR disable Inspector

Missing workloads, tenants, backup servers

API endpoint changes

Inspector not compatible

“Expected page results to be an array…”

API schema mismatch

Unsupported — no fix available

A temporary workaround is to disable the Inspector to prevent repeated failures until support for this version is released.


Troubleshooting Checklist 📝

Before opening a ticket, confirm the following:

✔ Console Version

  • VSPC is not v9+.

✔ Agent Version Consistency

  • All agents meet requirements for the Inspector deployed.

✔ Credentials

  • Using a VSPC admin account with API access.

✔ Network Access

  • Liongard agent machine can reach:

    • VSPC REST API port (default 1280)

    • Required authentication endpoints

✔ SSL/TLS

  • Confirm valid certificates if SSL is enforced.


When to Contact Liongard Support 🦁

Open a Liongard Support Ticket if:

  • Your VSPC instance is within v4–v8.1, but the v4 Inspector still fails.

  • You have logs or errors you want Liongard to review.

Recommended to include in your ticket:

  • VSPC version.

  • API version.

  • Inspector error logs.

  • Screenshot of failing endpoints.

  • Recent VSPC upgrade history.


References 🤩


Third-Party Links Disclaimer 🚨

Liongard documentation may reference external vendor sites and third-party resources. These links are provided for convenience. Liongard does not control or guarantee the accuracy, availability, or security of external sites. Use third-party tools and documentation at your discretion.

Did this answer your question?