I have a performance problem on the hosts (VMware / Storage) to perform backup routines on VMs. Should I use agent?

[sandroalves]

Hi,

I have serious problems during the agentless backup routine, which changes the status of the VMs to (very slow) in VMware.

In some cases the disk of the VM that is attacked in the proxy during the protection process remains attached for a long time and in some cases it hangs.

we know that using an agent is not recommended for several reasons, but in other solutions it was the solution I found.

In addition to using VM resources (Guest), is there any other negative point in using agents to protect VMs? Example: Speed ​​in restoration for example.

Does using agent affect licensing?

Is there any specific recommendation for using an agent, such as VMs with very large disks?

Thanks.

[HannesK]

Hello,
it sounds that your infrastructure is slow. So changing the way of backup will probably not help.

In some cases the disk of the VM that is attacked in the proxy during the protection process remains attached for a long time and in some cases it hangs.

sounds you are using virtual proxies with Hot-Add. What about direct-SAN backup or backup from storage snapshots?

Example: Speed ​​in restoration for example.

file level or application restore is the same. for full VM / disk restore you loose change block tracking restore. Instant recovery to VMware also needs conversion from "physical" to VMware. I would not go that way. I would fix the backup speed issue.

Does using agent affect licensing?

if you use V10: no

such as VMs with very large disks?

what is "very large" for you? 5TB, 30TB, 50TB? In general, there is nothing to configure in Veeam Agent for Windows about disk size.

Best regards,
Hannes