Error: Object reference not set to an instance of an object

[darkhelmetnl]

A couple days ago I started getting errors with my Veeam backup within a minute of starting the job. Stating: Error: Object reference not set to an instance of an object.
It comes right after VSS Snaphot -> Finalizing -> Error
I backup from Windows 10 2004, with the latest version of Veeam available (4.0.1.2169).

My target is a NAS that I have used as a target for a while.
I tried a new destination on the NAS, I tried reconfiguring the backup job, but to no effect.

A bit of Google only pointed to different types of environments with VMware etc.
Anything I can try?

Case #04423492

[Vitaliy S.]

Hi,

This error is too generic, so it's hard to say what is causing it, so our support team is your best bet here. On a side note, you said that you've tried reconfiguring the job, but do you see the same error message for newly created jobs on the agent?

Thanks!

[Mildur]

I have this problem too with one specific agent.
I will open soon a case.

[suspect0]

Having the same issue with an agent backup. There were duplicate DNS entries and I deleted the one DNS entry. Rescanned the agent, the repo, reinstalled the agent, rebooted the computer. Still getting the same error

[darkhelmetnl]

I traced my issue back to corrupted backup storage location. Somehow the files got corrupted.

I also had to reinstall Veeam Agent. After pointing to a new location, the backup is running fine again

[Mildur]

Thanks for sharing this information. I will try this on my agent too.

[Dima P.]

darkhelmetnl,

I traced my issue back to corrupted backup storage location. Somehow the files got corrupted.

I wonder if periodic health check option disabled? I believe our data corruption guard should catch such issues when it's enabled to perform health check perdiodically. Cheers!