It's been a little while since my last update on the Veeam Backup & Replication integration for Home Assistant.
Back in August, version 0.5.0 brought VBR 13.1 support and a fairly significant expansion of what the integration could monitor and automate.
Since then, both of the Veeam Home Assistant integrations have continued to grow.
Today:
-
Veeam Backup & Replication for Home Assistant is at 0.8.0
-
Veeam Backup for Microsoft 365 for Home Assistant is at 0.4.1
-
The underlying Veeam Backup & Replication Python SDK supports VBR 13.1
-
The underlying Veeam Backup for Microsoft 365 Python SDK supports VB365 8.6
So rather than reintroducing the projects, I wanted to take a look at what's actually new.
Veeam Backup & Replication: 0.5.0 → 0.8.0
The 0.5.0 release was primarily about bringing the integration forward to VBR 13.1.
Since then, the focus has shifted from API compatibility to exposing more of the things Veeam administrators actually care about.
VBR 12.x compatibility
Version 0.6.0 fixed a number of compatibility problems with VBR 12.x and API 1.2-rev1.
That included issues with proxies, null enum values, and some parsing failures that could cause otherwise valid API responses to fail.
This was an important one because supporting the newest VBR version shouldn't mean breaking environments that haven't upgraded yet.
Security and malware detection
The biggest addition in 0.8.0 is probably the new Security device.
The integration can now expose malware detection information from Veeam, including a Home Assistant event when malware is detected.
The Security device also includes information from Veeam's Security & Compliance Analyzer.
This opens up some interesting automation possibilities.
For example, a malware detection event can become a high-priority Home Assistant notification rather than something that only gets discovered the next time someone opens the Veeam console.
SOBR move and copy sessions
0.8.0 also adds visibility into Scale-out Backup Repository move and copy sessions that are awaiting action.
More importantly, the integration exposes an action to settle those sessions.
That means Home Assistant isn't just monitoring the state anymore — it can interact with Veeam when an operation requires action.
Connected Agent Recovery Appliances
Connected Recovery Appliances are now exposed as well, including an event when an appliance connects.
This is another example of moving beyond the traditional "did my backup job succeed?" model and exposing the surrounding Veeam infrastructure.
Job targets
Every job now has a Target sensor.
It's a small addition, but useful when building dashboards or automations where you want the job's destination represented directly alongside its status and other job information.
Veeam Backup for Microsoft 365: 0.2.0 → 0.4.1
The Microsoft 365 integration has also grown substantially since its original announcement.
Version 0.4.0 was a particularly large release.
Server health
The integration can now report the health of the Veeam Backup for Microsoft 365 server itself using the API's health endpoint.
So instead of only monitoring jobs and repositories, Home Assistant can also tell you whether the Veeam server components, mainly its PSQL DB and NATS server are healthy.
Backup proxies
VB365 backup proxies can now be monitored through Home Assistant.
This brings another important piece of the backup infrastructure into the same monitoring system.
Microsoft 365 organizations
The integration now understands the Microsoft 365 organizations being protected.
For each organization, Home Assistant can expose information about:
-
Protected users
-
Protected groups
-
Protected sites
-
Protected teams
There's also a Synchronize button to initiate organization synchronization.
Version 0.4.1 further improved this by reading organizations from the API's extended view.
Repository maintenance
For VB365 8.6 and later, repository maintenance sessions are now exposed, including controls for those sessions.
This is one of the places where the integration is taking advantage of the newer API rather than simply replicating the functionality that existed when the integration was first released.
Latest job sessions
Each job can now expose its latest session.
That gives Home Assistant a much more useful view of what actually happened during the most recent execution rather than only exposing the job's configuration.
Live job updates
The integration also now follows the VB365 API v8 event feed.
That means job-related state can be updated from events rather than waiting for the next polling cycle.
This is a pretty significant architectural improvement because it allows Home Assistant to react to VB365 events as they happen.
From backup monitoring to backup automation
This is really where the project has ended up.
The original goal was simple: make Veeam backup status visible in Home Assistant.
But as more of the Veeam environment becomes available, Home Assistant can start acting as an automation layer around the backup infrastructure.
A few examples:
-
Alert immediately when Veeam detects malware
-
Announce a backup failure through a Home Assistant Assist satellite
-
Notify when a backup proxy goes offline
-
Monitor repository maintenance
-
Track Microsoft 365 protection counts
-
React when a Recovery Appliance connects
-
Surface Veeam server health alongside the rest of the home lab
-
Build a single dashboard covering both VBR and VB365
And because these are Home Assistant entities and events, you're not limited to the notification mechanisms built into the integration.
You can use whatever Home Assistant already supports.
What's next?
There is still a lot more that can be exposed.
Veeam's APIs contain considerably more information than anyone probably wants to turn into Home Assistant entities, so the challenge is deciding what is actually useful for monitoring and automation. Additionally, every new Veeam release adds new APIs and data points that weren’t previously available.
The direction I'm most interested in is continuing to move beyond simply exposing API data and making that data useful for automation.
If you're running either integration, I'd be particularly interested in hearing what you're actually doing with it.
Are you using it for backup alerts? Dashboards? Home Assistant Assist? Automated remediation? Something I haven't thought of?
Let me know.
Projects
Veeam Backup & Replication for Home Assistant
GitHub — ha-veeam-br
Veeam Backup for Microsoft 365 for Home Assistant
GitHub — ha-veeam-365
Veeam Backup & Replication Python SDK
GitHub — veeam-br
Veeam Backup for Microsoft 365 Python SDK
GitHub — veeam-365
The integrations are community projects and are not official Veeam products.
