Skip to main content

Good day,

What caused this error?

This is a hyper-V backup job for a linux vm, worked excellent for days, for 3 months now, what happened all of a sudden?

I retried, same error after 20% then fail. 

I restarted the veeam server, now attempting backup again. It has been stuck on 20% for like 15 minutes now.

Where did this come from all of a sudden and how do i fix?

This is a common error and one that cannot just be explained since it worked then came up.  You would need to dive in to the logs which can be a cumbersome process and they are located here on the VBR server - C:\ProrgramData\Veeam\Backup\Jobname

If this continues to happen I would suggest a ticket with Support to get them to analyze the logs as they have much better tools.


This is a common error and one that cannot just be explained since it worked then came up.  You would need to dive in to the logs which can be a cumbersome process and they are located here on the VBR server - C:\ProrgramData\Veeam\Backup\Jobname

If this continues to happen I would suggest a ticket with Support to get them to analyze the logs as they have much better tools.

Ok, thanks.


This is a common error and one that cannot just be explained since it worked then came up.  You would need to dive in to the logs which can be a cumbersome process and they are located here on the VBR server - C:\ProrgramData\Veeam\Backup\Jobname

If this continues to happen I would suggest a ticket with Support to get them to analyze the logs as they have much better tools.

Ok, thanks.

Not a problem.  Let us know how you get on.


Just an piece of logs below( I will allow this job to run on schedule for the last time, if fails, i will contact veeam support):

 

>06.11.2024 08:37:53.979] <36> 000U] Info (3) CTransportSvcAgentManager] Checking whether agent 'ad687800-086d-462c-9e16-61d9ae377ff6' is alive on host 'server1.local' with timeout.

>06.11.2024 08:37:53.979] <36> 000U] Info (3) CTransportSvcAgentManager] Agent has been stopped, id 'ad687800-086d-462c-9e16-61d9ae377ff6'

>06.11.2024 08:37:53.979] <36> 000U] Info (3) CProxyRpcInvoker] RpcInvoker 33554938] was disposed

>06.11.2024 08:37:53.979] <36> 000U] Error (3) Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown. (Veeam.Backup.AgentProvider.AgentClosedException)

>06.11.2024 08:37:53.979] <36> 000U] Error (3) at Veeam.Backup.AgentProvider.CClientAgentProtocol.WaitUntilWorking(Int32 timeout)


Unsure based on that what the issue is and support can definitely help more with the logs.


Hi @SysEng -

Agree with Chris...prob best to work with Support. Some thoughts on what could be causing the issue → my guess from the error/log info shared is maybe the Veeam Services on the Host are stopping maybe caused by network port conflict, or there’s simply a loss of communication to the Host/services. You can check on DNS, network issues, cable/NIC problems to the Host. Those are just a couple “easy” suggestions to take a look at as you’re waiting for Support.

Let us know what they say.

Best.


I resolved this by creating a new backupset, and deleting old from disk


Glad you got it resolved.


Great to hear you resolved the issue.


Comment