Agents are run centrally from Veeam Backup & Replication, with jobs or policies set up by a Backup Administrator or someone with a custom role.
Read more: Veeam Help Center
In the Ultra Transcenders books
Each book explains managed mode in context, with comparison tables and the common traps.
Terms in this definition
- Set
Secret permission in Key Vault for writing secrets; some older material refers to it as Create.
- Custom role
Built from the preset permissions that the built-in Microsoft Entra roles also use, and assignable to the whole tenant, an administrative unit or one object. Each user it is assigned to needs Microsoft Entra ID P1; Azure custom roles are a separate thing.
Related terms
- application backup policy
In managed mode, the backup server holds this policy, which tells Veeam Plug-ins what database data to protect and when, how and to where. Transport jobs on the database servers then deliver it to a repository.
- failover cluster
Veeam Agent for Microsoft Windows, running in managed mode, can protect a whole Windows Server Failover Cluster as one object; in the job you pick the Server or Failover cluster type.
- standalone mode
Installed by hand on the database server, the Veeam Plug-In is driven here by the database administrator using the database's own tools. Managed mode is the alternative, where the backup administrator uses application backup policies instead.
- Veeam Plug-in management infrastructure
The set of components needed to deploy and manage Veeam Plug-ins centrally in managed mode: the backup server, the machines running the plug-ins, a distribution server and the backup storage.