Backup & Virtualization
Veeam Backup
Backup job and restore-verification status from Veeam Backup Enterprise Manager syncs onto CI backup-evidence fields, and a failed job opens an incident automatically. Restore is on the roadmap, not available in this release.
InboundData residency: EU
Request a demoWhat it does
- Failed backup job → incident (category backup_failure)
- Successful or warned job → CI backup_state (current or stale, judged against a configurable RPO window) and last_backup_at
- SureBackup restore verification → CI last_restore_test_at
- Runs against Veeam Backup Enterprise Manager's own on-prem/self-hosted server, so no third-party EU residency question applies
- Restore is declared in the manifest for the roadmap view; there is no restore implementation in this release — deferred to a future release behind per-action consent
- Outbound incident-acknowledgement push is also declared for the roadmap and not yet wired
- Extensible to Acronis via a parallel adapter reusing the same normalized shapes — not shipped yet
Data residency
Veeam Backup Enterprise Manager is the tenant's own on-prem/self-hosted server; no third-party sub-processor is involved.
Event mappings
| External event | Maps to | What happens |
|---|---|---|
| job.result.Failed | incident | Failed Veeam backup job → incident (category backup_failure) |
| job.result.Success | ci | Successful backup job → CI backup_state=current, last_backup_at set |
| job.result.Warning | ci | Backup job with warnings → CI backup_state current/stale by RPO |
| restorePoint.verified | ci | SureBackup restore verification → CI last_restore_test_at set |
What you configure
- Enterprise Manager base URL
- Credential reference (stored as a secret)
- RPO window in hours (default 24 — a successful backup older than this reads as stale)
- TLS verification (default on)
Setup overview
Point the integration at your Enterprise Manager REST endpoint and store the credential as a secret. Set your RPO window so backup_state reflects your actual recovery objective.
Related features
See TENSOR running on your own estate.
30 minutes, screen-shared, no slides. Bring the process you are least sure we handle and we will start there.