Error: The system cannot find the path specified. Failed to

[dlapointe]

Hi,

I have the same issue here after updating to 9.5 U4

It worked for me as well by changing the "checkpoint file location". However we use CSV volumes so I had to change the location from:
C:\clusterstorage\volume9\dlapVM
to:
C:\clusterstorage\volume9\dlapVM\Snapshots

Works fine now..

[dlapointe]

Do any of you guys have an official fix for this?

We are afraid of updating our Veeam server to U4 in our hyper-v environment containing over 2000+ VMs.

Imagine having to edit snapshot location of 2k vms...lol

[Dima P.]

Hi folks,

For those of you who faced this error after installing Update 4 please follow this KB article - KB 2890 (fix is included).

P.S. If you see such behavior with previous versions of Veeam B&R please raise support case as most likely that a regular VSS issue that needs to be treated differently.

[Ctek]

Thanks!

[ejenner]

The path in the hotfix KB doesn't exist on my B&R server. So I searched for Veeam.Backup.Core.dll and replaced all instances with the updated version. Not sure if that is going to do more harm than good? Will find out by tomorrow morning.

"3.Navigate to the Veeam installation folder on the Veeam Backup Server (by default it is C:\Program Files\Veeam\Backup and Replication\Backup)"

[ejenner]

the hotfix fix worked for me.

Just not sure about that path specified in step 3.

[Mike Resseler]

EJ,

Most likely you haven't used the default installation parameters? Because that default path should be correct.
But glad the problem is solved though

[ejenner]

I think the only change I made during the installation was to put it on the D: drive. But that shouldn't have created a new entirely different path?

[Mike Resseler]

EJ,

It does, since you have chosen a specific path. It probably will become: D:\Program Files\Veeam\Backup and Replication\Backup (or even something else if you have customized it further)

[ejenner]

Ok, I accept what you're saying is most likely correct... but that's pretty unusual for an application to change the installation path because the drive letter changed?

[Mike Resseler]

Actually, that is not entirely true. When you want to install to an alternative location (not the default), many applications allow you to change the entire path. So once you type in a different drive letter, you have the possibility to change it entirely. If you type in D: only, then it will be under that root. There are many applications that work like that I'm afraid and is always something you need to take into account each time you change the default path of a workload.

[ejenner]

I just swapped the 'C:' for a 'D:' at the beginning of the path in the box. I left the remaining part as it was. But this is splitting hairs, I got it to work by searching for the .dll and updating all the instances I found. It's been perfect ever since.

[Mike Resseler]

If you just switched C and D, then the path should have been D:\Program Files\Veeam\Backup and Replication\Backup. So that would mean something went wrong. Anyway, you are right. The problem is solved so...

[GladstoneRC]

I had the same error, but for only 3 of our 120 vm's. I changed the snapshot path to be case sensitive and the backups worked. Exact same location but with capitals.

[posvanc]

Solved for my VMs too, thx a lot.

1. i dont have snapshots yet!
2. i changed path to VMname\snapshot
3. click Apply (no restart - only update preferences in HYV manager)
4. go to Veeam console - Retry Job - ... oh it works again !!

Great job. Thx a lot.

[powersjo]

Here's what I want you to do:
- open VM settings (e.g. busoDEV01) in Hyper-V Manager
- select "Checkpoint File Location" -> "Browse...". -> select the path "F:\Virtual Machines\Snapshots".
(currently the wrong path "F:\virtual machines" is selected there)

This solved my problem, thanks!

[chanklish]

followed this but still same issue

[Dima P.]

Hello chanklish,

Any chance you have a case ID to share? Thanks!

[chtn]

Hello at all.

Our problem was solved together with Veeam Support!

Here the solution of the Veeam Support:

Here's what I want you to do:
- open VM settings (e.g. busoDEV01) in Hyper-V Manager
- select "Checkpoint File Location" -> "Browse...". -> select the path "F:\Virtual Machines\Snapshots".
(currently the wrong path "F:\virtual machines" is selected there)

So we adjusted the path "Checkpoint File Location".

Then restart the Veeam Backup job.

And the problems are solved

Thanks

Five years later, this just fixed an issue for me, where backups for ALL VM's on ONE specific host were failing after an outage due to an extended power outage forced us to shutdown ALL of our Hyper-V hosts for about two hours. Changing the path to explicitly list the Snapshots folder as the destination did the trick. Interestingly, VM's on other hosts which did NOT experience the backup failure were not set with the path including the Snapshot folder. Weird. I left them alone.

Thanks!