Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown.

Issue/Error: When we try to backup the VM in veeam backup server, we gets  exception like below,

Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown.

Root Cause:

When backup jobs starts and proxy will assign automatically, but assigned proxy doesn't have access for the disk, so unable to access the disk and got failed.

Fig 1 : Backup proxies for HD1 and 2 don't have access permission.

Fig 1 : Backup proxy for HD 2 doesn't have access permission.

Solution:

1. Assign the proxies which has right permission.(Change the proxies to manual in backup job settings and and assign it)

2. Check the proxies that has same IP range as you Hyper-V/Vcenter node, so access using proxies will not get any issues.

Find PID for VEEAM backup job

Kill veeam backup job using Process ID

Issue: Sometimes veeam backup job won't complete (hung) in particular time and it does not backup any data, so when we try to stop the job and it won't help us and will remain in stopping state. So killing the backup job is only option using PID.

So we can find the corresponding backup job's PID using their log file.


Solution: The default log path C:\ProgramData\Veeam\Backup and you can find .LOG file with the below format.

JOB.<JOB_NAME>.backup.log  Filter those files with modified date and pick the latest date log file and Search PID: Kill the job using taskkill option. Note: When backup job starts meanwhile in background there are a lot of MSSQL transaction will  start for the backup job, If you kill the backup job using PID it may lead to corrupt backup job, try using your own risk. So mostly this is not a recommended way to stop the running backup jobs.