Load Veeam Backup and Replication data to DuckDB

Veeam Backup & Replication REST API is an interface for managing backup infrastructure and operations. Everything needed to build a working Veeam Backup and Replication → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Veeam Backup and Replication to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Veeam Backup and Replication to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Veeam Backup and Replication API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Veeam Backup and Replication API at a glance

These values come from the Veeam Backup and Replication API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Veeam Backup and Replication API?

The newer REST API uses Bearer authentication, where the access token is provided in the Authorization header as 'Bearer <access_token>'. It requires the 'x-api-version' header (e.g., '1.3-rev1') on all requests.

1. Get your credentials

The Veeam Backup & Replication REST API does not use static API keys. Authentication is session-based. For the modern VBR REST API (v13+), you must use OAuth 2.0. 1) Send a POST request to the token endpoint with your username and password in the body. 2) For domain credentials, ensure the backslash is URL-encoded (e.g., DOMAIN%5Cuser). 3) Receive an access token and refresh token in the response. 4) Include the access token in the Authorization header (Bearer ) for all subsequent requests. For Enterprise Manager REST API, use Basic HTTP Authentication by Base64 encoding your username:password and sending it in the Authorization header to the /sessionMngr/ endpoint to obtain a session ID.

2. Add them to .dlt/secrets.toml

Copy
[sources.veeam_backup_and_replication_source]
vbr_username = "your_username"
vbr_password = "your_password"
vbr_api_url = "https://your-vbr-server:9419"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Veeam Backup and Replication data can I load into DuckDB?

These are the Veeam Backup and Replication endpoints dlt can load into DuckDB:

---

How do I load only new Veeam Backup and Replication records?

The Veeam Backup and Replication API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "backup_servers", "endpoint": {
    "path": "api/query?type=backupServer&format=Entities",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Veeam Backup and Replication pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /sessionMngr and /oauth2/token from the Veeam Backup and Replication API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def veeam_backup_and_replication_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://<hostname>:9419/api",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "backup_servers", "endpoint": {"path": "api/query?type=backupServer&format=Entities"}},
            {"name": "jobs", "endpoint": {"path": "api/query?type=job&format=Entities"}}
        ],
    }
    yield from rest_api_resources(config)


def load_veeam_backup_and_replication_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="veeam_backup_and_replication_pipeline",
        destination="duckdb",
        dataset_name="veeam_backup_and_replication_data",
    )
    load_info = pipeline.run(veeam_backup_and_replication_source())
    print(load_info)


if __name__ == "__main__":
    load_veeam_backup_and_replication_to_duckdb()

Run it with python veeam_backup_and_replication_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Veeam Backup and Replication data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("veeam_backup_and_replication_pipeline").dataset()
df = data.query_service.df()
print(df.head())

SQL:

Copy
SELECT * FROM veeam_backup_and_replication_data.query_service LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Veeam Backup and Replication to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Veeam Backup and Replication loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Veeam Backup and Replication data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack