Runtime Coordination Process

To perform guest processing tasks, Veeam Backup & Replication does not deploy persistent agents inside VMs. Instead, it uses a runtime coordination process. The runtime process is non-persistent — it is deployed on every VM added to the job when the job starts and removed as soon as the job finishes. Use of the runtime process helps avoid agent-related drawbacks such as pre-installing, troubleshooting and updating.

Veeam Backup & Replication can deploy the runtime process on VMs in two ways:

  • For VMs running Microsoft Windows, the runtime process is deployed using guest interaction proxies. For more information, see Guest Interaction Proxy.
  • For VMs running OSes other than Microsoft Windows, for example, Linux, the runtime process is deployed from the backup server.

Runtime Coordination Process Note:

If there are no guest interaction proxies or guest interaction proxies fail for some reason, Veeam Backup & Replication will deploy the runtime process on Microsoft Windows VMs from the backup server.

When you start a job with guest processing tasks enabled, Veeam Backup & Replication performs the following operations:

  1. Veeam Backup & Replication defines the machines that will perform the guest interaction proxy role.
  2. Veeam Backup & Replication obtains IP addresses from Hyper-V Integration Services installed on VMs. If Veeam Backup & Replication fails to connect to the VM guest OS over the network, it obtains IP addresses over PowerShell Direct. PowerShell Direct is used for VMs that reside on Microsoft Hyper-V Server 2016 or later and run Microsoft Windows 10 or Microsoft Windows Server 2016 or later. Veeam Backup & Replication requires Microsoft PowerShell 2.0 or later to work over PowerShell Direct.

Veeam Backup & Replication deploys the runtime process on VMs:

    • [For Microsoft Windows VMs] The guest interaction proxy connects to VMs and deploys the runtime process on them.
    • [For VMs running other OSes] The backup server connects to VMs and deploys the runtime process on them.
  1. The job session proceeds as usual.
  2. When the job session completes, Veeam Backup & Replication deletes the runtime process on VMs.

Runtime Coordination Process 

If a network connection breaks during the job session, Veeam Backup & Replication makes attempts to re-establish the connection:

  • If a network connection between the backup server/guest interaction proxy and VM guest OS breaks, Veeam Backup & Replication makes one attempt to reconnect.
  • If a network connection between the backup server and guest interaction proxy breaks, Veeam Backup & Replication makes 10 attempts to reconnect.

If attempts are unsuccessful, guest processing tasks fail. The job proceeds with the scenario defined in the job settings. For example, if you have instructed a backup job to try application processing but ignore failures, Veeam Backup & Replication will not perform guest processing tasks but will proceed with the VM backup.

Related Topics

I want to report a typo

There is a misspelling right here:


I want to let the Veeam Documentation Team know about that.