Skip to main content

Hi 

Not sure if this is the right place I have tried R&D forums.

I use Veeam for Windows free backing up endpoints to NAS drives.

I have a clients endpoint that's has been running fine for a long time but now gets stuck at 40% and in the end fails with Application Failed. Its stuck in backing up the C drive

I have tried all the obvious, updated to latest, reinstalled, deleted job and recreated the database but still seeing the issue. 

Run chkdsk not issues with disk

Anyone seen this before?

Hi, can you please define what you mean by “clients” if you meant you have a customer, you’re violating the EULA of the free edition. Just wanted to make you aware.

 

Have a look at the logs (c:\programdata) and gather the error information from the Veeam subdirectory that contains your agent backup job.


Hello ​@simonneal72 ,

has the C: drive and the drive the backup is saved enough free space?

Did you have a look at the Windows system logs?


Application Failed is very generic. I'd recommend checking the job logs located under “C:\ProgramData\Veeam\Endpoint” and that should give you more context of the failure 


Hello,

I’ve encountered a similar issue in the past.

20/02/2025 14:54:41 :: Error: Failed to connect to agent 'proveeam01', EP '192.168.x.x:2503'. A connection attempt failed because the connected component did not respond correctly after a period of time, or the established connection failed because the connected host did not respond 192.168.x.x:2503

20/02/2025 14:06:06 :: Error: Application error
20/02/2025 14:08:36 :: Processing finished with errors at 20/02/2025 14:08:36

 

In my case, it happened with agent backups communicating over a VPN. The problem was related to the firewall. 

You can share with us the logs to better assist. However, in your case, I recommend opening a support ticket so they can assist you further.


Hi 

The issue was --vdisk_corrupted error.

I ran chkdsk repair a few times as per https://forums.veeam.com/veeam-agent-for-windows-f33/vdisk-corrupted-solved-t91675.html

Even though Chkdsk was not reporting errors, it fixed it.

 

Thanks


My trust in this disk would be shattered….

I would move all data from it and see that I get either a new disk or delete and redefine the virtual disk.

In most cases this is only the beginning of the problems with this disk.


Comment