← Back to news 27.06.2026

New Veeam connector: turning backups into provable recoverability

isidaten now connects directly to Veeam Backup & Replication. Backup jobs, sessions and repositories flow automatically into the central object base, turning the mere existence of backups into provable recovery evidence.

Having a backup is one thing. Being able to prove in an audit that recovery actually works and is tied to your business-critical systems is another. That is exactly where the new Veeam connector from isidaten comes in: it pulls the real backup status from Veeam Backup & Replication straight into the GRC platform, instead of leaving it in a separate console.

What the connector synchronizes

Through the integration with Veeam Backup & Replication, isidaten automatically pulls in, without manual exports:

  • Backup jobs: which systems are protected and on what schedule.
  • Sessions: whether the latest backup runs succeeded or failed.
  • Managed servers & repositories: where the data lives and through which infrastructure it is backed up.

What changes in practice

A failed backup job used to be a line in a report nobody reads until it is too late. With the connector it becomes visible in the risk picture of the affected asset. If a system classified as critical has not been backed up successfully for days, that shows up right where its protection requirement and recovery time are recorded. A technical status message becomes governance information.

Why this is more than another connector

On the central object base of isidaten, a protected system becomes the same object as in the risk register, in business continuity management and in asset management. A backup job is no longer isolated information in the Veeam console, but part of the bigger picture: which asset is protected, with what protection requirement, and does the backup status match the required recovery time?

What the auditor wants to see

An auditor rarely just asks whether backups exist. They ask whether a specific critical system can be restored within the defined recovery time, and they want it evidenced. Exactly that link between asset, protection requirement, backup status and recovery time lives on a single object base with the connector, instead of being spread across four tools.

The link to NIS2 and BCM

Business continuity is no longer optional. Anyone in scope of NIS2 must not only organize recoverability but prove it. With the Veeam connector, that evidence is created where the backups actually run, instead of being assembled from screenshots and status emails before an audit.

Learn more about the available connectors on our integrations page, or book a demo.

Questions about this update?

Talk to us – we are happy to show you this feature in a demo.