20.12.2021 · For Server edition of Veeam Agent for Microsoft Windows, you can specify guest processing options. Veeam Agent for Microsoft Windows offers the following guest processing options: Application-aware processing. You can create transactionally consistent backups of servers running applications that support Microsoft VSS.
Although installing the guest interaction proxy worked and Veeam was also able to use the VM as a hot-add proxy, it failed to connect to the persistent agent via the guest interaction proxy. At the end is was the format of the user which caused the problem.
With the persistent agent Veeam doesn't have to deploy it for every job run; less firewall configuration and better security. BertrandFR wrote: Awesome share @ ...
20.04.2021 · By default, Veeam Backup & Replication uses the same credentials for all VMs in the job. If some VM requires a different user account, click Credentials and enter custom credentials for the VM.; If you have added Microsoft Windows VMs to the job, specify which guest interaction proxy Veeam Backup & Replication can use to deploy the non-persistent runtime …
13.12.2021 · The VeeamInstallerSvc.msi is pre-installed manually or with 3rd party deployment tools (whatever you use for your software deployments). Or you add it to your VM templates. If you can open the ports for automatic installation, then …
16.11.2021 · If you want to perform guest processing in a highly secure way, you can install persistent agent components (Guest Helper and Log Shipping Service) on protected VMs. Persistent agent components installed on protected VMs require very limited and clearly defined ports to communicate with Veeam Backup & Replication.
27.04.2021 · On the right of the Guest interaction proxy field, click Choose. Leave Automatic selection to let Veeam Backup & Replication automatically select the guest interaction proxy. Select Use the selected guest interaction proxy servers only to explicitly define which servers will perform the guest interaction proxy role.
22.02.2021 · At least the logs show which way is used. In our case we see the following: Failed to inject guest runtime using guest interaction proxy, failing over to backup server. Failed to inventory guest system: Veeam Guest Agent is not started. The non-persistent way is also not working as the Admin Shares aren't available.
Although installing the guest interaction proxy worked and Veeam was also able to use the VM as a hot-add proxy, it failed to connect to the persistent ...