> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/automate-protect-and-extend/integrations-and-apis/veeam.md).

# Veeam Integration with VergeOS

## Overview

Veeam Backup & Replication (VBR) 13.1 and later includes a native VergeOS integration, letting you protect workloads running on VergeOS — both in the provider (the root system) and inside individual tenants — with Veeam's backup and recovery platform.

For the network configuration the deployed components need — including extending the provider's External network into tenants — see [Configuring Network Access for Veeam Backup & Replication Workers](/knowledge-base/backup-dr/veeam-worker-networking.md) in the Knowledge Base.

## How It Works

The integration is built on the VergeOS **oVirt-engine package**, which exposes a VergeOS system through an oVirt-compatible API. In the Veeam console, you select **VergeOS** under Virtualization Platforms and add the system to the inventory as a **VergeOS Manager**. Each tenant you want to protect is added the same way, as its own VergeOS Manager with its own engine ID.

```mermaid
graph TB
    VBR["Veeam Backup & Replication<br/>(backup server, 13.1+)"]
    subgraph Provider["Provider (Root system)"]
        Engine["oVirt engine<br/>(VergeOS oVirt-engine package)"]
    end
    subgraph Tenant["Tenant: VeeamTenant1"]
        TEngine["oVirt engine<br/>(own engine ID)"]
    end
    VBR -->|"added to inventory as a VergeOS Manager"| Engine
    VBR -->|"added to inventory as a VergeOS Manager"| TEngine

    style Provider fill:#e8f5e9,stroke:#2e7d32
    style Tenant fill:#fff3e0,stroke:#e65100
```

Once a VergeOS Manager is in the inventory, Veeam deploys and manages the rest itself. The main components involved:

* **Backup server** — the machine running Veeam Backup & Replication; the configuration, administration, and management core of the backup infrastructure.
* **Workers** — auxiliary Linux-based VMs that Veeam deploys on the protected system to process backup workloads and move data to and from backup repositories.
* **Backup repositories** — the storage locations where backups land.

## Installing the oVirt-engine Package

The oVirt-engine package is an optional VergeOS package (listed as "oVirt API compatibility") delivered through the standard update system:

1. From the top menu, navigate to **System** > **Updates**.
2. In the **Packages** list, locate the **ovirt-engine** package. Optional packages that aren't yet installed show *-- Optional --* in the Branch column.
3. Click the cloud download icon next to **ovirt-engine**. Once queued, its Version column reads `Not Installed→<version>`.
4. Run the update from the left menu — **Download** (if needed), then **Install**. After the install, a **Reboot** is required, just like a normal VergeOS update: nodes update one at a time with workloads migrated automatically, so there's no system downtime when adequate resources are available. See [Updating VergeOS](/run-the-platform/system-administration/running-updates.md) for the full update flow.

## Requirements

* **VergeOS 26.1.7 or later** — the first release whose oVirt-engine package is supported by Veeam — with the **oVirt-engine** package enabled
* **Veeam Backup & Replication 13.1 or later** — the first release with the VergeOS integration
* Review Veeam's [Considerations and Limitations](https://helpcenter.veeam.com/docs/vbr/userguide/ovirt_limitations_rhv.html?ver=13) for what the integration does and doesn't support

## Documentation and Resources

* [Configuring Network Access for Veeam Backup & Replication Workers](/knowledge-base/backup-dr/veeam-worker-networking.md) - Step-by-step networking guide in the VergeOS Knowledge Base, covering provider-only and tenant deployments
* [Veeam Backup & Replication User Guide — oVirt KVM Integration](https://helpcenter.veeam.com/docs/vbr/userguide/ovirt_overview.html?ver=13) - Veeam's integration overview
* [Veeam Backup & Replication User Guide — Infrastructure Components](https://helpcenter.veeam.com/docs/vbr/userguide/ovirt_infrastructure_components.html?ver=13) - Veeam's component reference

## Support

If you encounter issues with the Veeam integration or have questions about implementation:

* [Veeam Support](https://www.veeam.com/support.html) - Official support from Veeam
* [VergeOS Support](/support-and-services.md) - Technical assistance for VergeOS environments


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verge.io/automate-protect-and-extend/integrations-and-apis/veeam.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.